that I have no permission to install which makes sense since I am not root unlike
before it was asking for the root password.

I'm sorry but I don't understand what you're trying to say. From what I read from your post, you tried the salix installer and it somehow didn't work (no details why or when), then you tried the slackware installer and it worked with cgdisk and then you tried the salix installer again and it worked with cgdisk too. Is that right?Atip wrote:Checked with Slackware and it seems to be OK to work with cgdisk.
Made another installation to my GPT SATA drive this time selecting the partition of my choice with cgdisk.
In Type I selected Linux 8300, >Write and the installer found the parttion where I am in now.
This has been solved almost two weeks ago. It's mentioned earlier in this thread and has nothing to do with root/user password. You need to upgrade salix-codecs-installer first.Atip wrote:salix-codecs-installer is asking for my users password only to come back later
that I have no permission to install which makes sense since I am not root unlike
before it was asking for the root password.
Sorry for the confusion. When I was first confronted with cgdisk showing my partitons asgapan wrote:I'm sorry but I don't understand what you're trying to say. From what I read from your post, you tried the salix installer and it somehow didn't work (no details why or when), then you tried the slackware installer and it worked with cgdisk and then you tried the salix installer again and it worked with cgdisk too. Is that right?Atip wrote:Checked with Slackware and it seems to be OK to work with cgdisk.
Made another installation to my GPT SATA drive this time selecting the partition of my choice with cgdisk.
In Type I selected Linux 8300, >Write and the installer found the parttion where I am in now.
No problem with gnome-player.GStreamer backend error
Internal data stream error.
or
Internal data flow error.
That is shown if you run pkexec from the command line. Unfortunately it doesn't work in any other way, so it's impossible to use it through menus.sjox wrote:Hi!
I have a question to the "gksu/ktsuss" problem.
If you try for example "pkexec /usr/sbin/gslapt" it will work.
But first you have to generate a file "org.freedesktop.policykit.pkexec.policy" in "/usr/share/polkit-1/actions"
(it is explained https://bbs.archlinux.org/viewtopic.php?pid=999012)
Unfortunately it works only in terminal!
What can i do to generate a pretty authorization-gui as shown here: http://www.freedesktop.org/software/pol ... xec.1.html
Not really. This is just another wheel reinvention. sudo works fine for this and can be tweaked to allow/disallow anyone or anything, so there is nothing to gain. Another major issue is that a policykit action has to be created for every single application you would want to run as root. If slackware does not make that decision, we never will because we depend on slackware for those kind of things. And I believe that slackware will never do such a thing.sjox wrote:Does Salix wish to use pkexec anyway? (http://askubuntu.com/questions/78352/wh ... ksu-gksudo)
Thanks
gnsu/gksu works flawless but you have to type in your userpassword.mimosa wrote:Have you tried gnsu? That is how 14.1 is intended to do this. It should work with gksu too, in that I believe the latter is now just a symllink to gnsu.
Alright, it realy doesn't matter in practice and sudo ist tried and tested!gapan wrote:This is just another wheel reinvention. sudo works fine for this and can be tweaked to allow/disallow anyone or anything,