[opensuse-factory] Cannot run programs as root from kde3 or 4 menu
Hi, my kde4 is up to date and now I cannot get any programs that run as root to start from the menu. The kde4 run command doesn't prompt for root password nor does any menu item that is supposed to run as root i.e. yast2. The only way I can get yast2 for example, to start is in kde3 from the run command after entering the root password. I can't get yast2 sw_single to start in kde4 konsole after issuing the su command it just hangs but zypper works. Kde3s konsole works as expected and both yast2 and yast2 sw_single work as expected. sudo /sbin/yast2 starts the ncurses version in a user konsole in kde3, I haven't tried sudo in kde4. Any clues as to what package could have caused this? Regards Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Dnia wtorek 09 czerwiec 2009 o 15:12:06 Dave Plater napisał(a):
Hi, my kde4 is up to date and now I cannot get any programs that run as root to start from the menu. The kde4 run command doesn't prompt for root password nor does any menu item that is supposed to run as root i.e. yast2. The only way I can get yast2 for example, to start is in kde3 from the run command after entering the root password. I can't get yast2 sw_single to start in kde4 konsole after issuing the su command it just hangs but zypper works. Kde3s konsole works as expected and both yast2 and yast2 sw_single work as expected. sudo /sbin/yast2 starts the ncurses version in a user konsole in kde3, I haven't tried sudo in kde4. Any clues as to what package could have caused this? Regards Dave P To start GUI applications as root, login in terminal as root using "su -". Then type root password and application name to run. -- Pozdrawiam / Best regards, Mariusz Fik, openSUSE Community Member
Mariusz Fik wrote:
Dnia wtorek 09 czerwiec 2009 o 15:12:06 Dave Plater napisał(a):
Hi, my kde4 is up to date and now I cannot get any programs that run as root to start from the menu. The kde4 run command doesn't prompt for root password nor does any menu item that is supposed to run as root i.e. yast2. The only way I can get yast2 for example, to start is in kde3 from the run command after entering the root password. I can't get yast2 sw_single to start in kde4 konsole after issuing the su command it just hangs but zypper works. Kde3s konsole works as expected and both yast2 and yast2 sw_single work as expected. sudo /sbin/yast2 starts the ncurses version in a user konsole in kde3, I haven't tried sudo in kde4. Any clues as to what package could have caused this? Regards Dave P
To start GUI applications as root, login in terminal as root using "su -". Then type root password and application name to run.
As I stated in my original message that works I never use sudo only su, my problem is menu items set to run as root no longer ask for the root password and don't run. Regards Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Dave Plater wrote:
Hi, my kde4 is up to date and now I cannot get any programs that run as root to start from the menu. The kde4 run command doesn't prompt for root password nor does any menu item that is supposed to run as root i.e. yast2. The only way I can get yast2 for example, to start is in kde3 from the run command after entering the root password. I can't get yast2 sw_single to start in kde4 konsole after issuing the su command it just hangs but zypper works. Kde3s konsole works as expected and both yast2 and yast2 sw_single work as expected. sudo /sbin/yast2 starts the ncurses version in a user konsole in kde3, I haven't tried sudo in kde4. Any clues as to what package could have caused this? Regards Dave P
More info on my problem, in kde4, I managed to get the password prompt in the run command by entering the full path /sbin/yast2 and then entered the root password but I only had yast2 control center without root privileges. Regards Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Dave Plater wrote:
Dave Plater wrote:
Hi, my kde4 is up to date and now I cannot get any programs that run as root to start from the menu. The kde4 run command doesn't prompt for root password nor does any menu item that is supposed to run as root i.e. yast2. The only way I can get yast2 for example, to start is in kde3 from the run command after entering the root password. I can't get yast2 sw_single to start in kde4 konsole after issuing the su command it just hangs but zypper works. Kde3s konsole works as expected and both yast2 and yast2 sw_single work as expected. sudo /sbin/yast2 starts the ncurses version in a user konsole in kde3, I haven't tried sudo in kde4. Any clues as to what package could have caused this? Regards Dave P
More info on my problem, in kde4, I managed to get the password prompt in the run command by entering the full path /sbin/yast2 and then entered the root password but I only had yast2 control center without root privileges. Regards Dave P
Yast2 software management will not run from kde4 at all. Yast2 control center starts from a root konsole but I can't start software management from control center either. The log hangs at:- 2009-06-09 15:36:27 <1> Arbuthnot(4317) [ui] YUI.cc(YUI):62 Creating UI with threads Any ideas what to file a bug report against? Yast2 software management runs under kde3. Regards Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Tuesday 09 June 2009 08:43:27 Dave Plater wrote:
Yast2 software management will not run from kde4 at all. Yast2 control center starts from a root konsole but I can't start software management from control center either. The log hangs at:- 2009-06-09 15:36:27 <1> Arbuthnot(4317) [ui] YUI.cc(YUI):62 Creating UI with threads Any ideas what to file a bug report against? Yast2 software management runs under kde3. Regards Dave P
Dave, I have fought this from 2 different directions. See my post (this list) of earlier today: Passwordless Access to Apps for Admins: sudo or kdesu for 11.2/kde4. Check your .kde4/share/config/kdesurc and make sure it doesn't contain anything other than: 18:01 alchemy:~> cat .kde4/share/config/kdesurc [Passwords] Keep=true If it does, kdesu will behave very strange. With this setting I can access yast2, just by clicking on the yast icon and I get the prompt for the password: http://www.3111skyline.com/download/openSUSE_bugs/kde4/screenshots/kdesu-yas... OK.jpeg However, it is annoying to be constantly prompted for the root password for every admin task and there should be some way of configuring kdesu to check group policies, etc.. so that access is given to those that need it (ME in particular). I do use sudo from the command line and I had resisted to temptation to set super-user to sudo for kde4 hoping to find a way to make kdesu work, but the only way I have to giving myself root access to all admin tasks without being prompted for a password is to use the old kwriteconfig had typed into a terminal as a normal user that modifies your .kde4/share/config/kdesurc. After setting up sudo as normal, issuing: kwriteconfig --file kdesurc --group super-user-command --key super-user- command sudo Modifies kdesurc as follows: 20:57 alchemy:~> cat .kde4/share/config/kdesurc [Passwords] Keep=true [super-user-command] super-user-command=sudo In this configuration, you get root access to all of your admin tasks (except in kde control center where I think the code is still completely missing...) I don't know what the "right" answer is. Everyone says not to use sudo, but nobody has fixed kdesu. A rather sticky wicket... -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
David C. Rankin wrote:
On Tuesday 09 June 2009 08:43:27 Dave Plater wrote:
Yast2 software management will not run from kde4 at all. Yast2 control center starts from a root konsole but I can't start software management from control center either. The log hangs at:- 2009-06-09 15:36:27 <1> Arbuthnot(4317) [ui] YUI.cc(YUI):62 Creating UI with threads Any ideas what to file a bug report against? Yast2 software management runs under kde3. Regards Dave P
Dave,
I have fought this from 2 different directions. See my post (this list) of earlier today: Passwordless Access to Apps for Admins: sudo or kdesu for 11.2/kde4.
Check your .kde4/share/config/kdesurc and make sure it doesn't contain anything other than:
18:01 alchemy:~> cat .kde4/share/config/kdesurc [Passwords] Keep=true
davepl@Arbuthnot:~> cat .kde4/share/config/kdesurc [Passwords] Keep=false
If it does, kdesu will behave very strange. With this setting I can access yast2, just by clicking on the yast icon and I get the prompt for the password:
http://www.3111skyline.com/download/openSUSE_bugs/kde4/screenshots/kdesu-yas... OK.jpeg
However, it is annoying to be constantly prompted for the root password for every admin task and there should be some way of configuring kdesu to check group policies, etc.. so that access is given to those that need it (ME in particular).
I do use sudo from the command line and I had resisted to temptation to set super-user to sudo for kde4 hoping to find a way to make kdesu work, but the only way I have to giving myself root access to all admin tasks without being prompted for a password is to use the old kwriteconfig had typed into a terminal as a normal user that modifies your .kde4/share/config/kdesurc. After setting up sudo as normal, issuing:
kwriteconfig --file kdesurc --group super-user-command --key super-user- command sudo
Modifies kdesurc as follows:
20:57 alchemy:~> cat .kde4/share/config/kdesurc [Passwords] Keep=true
[super-user-command] super-user-command=sudo
In this configuration, you get root access to all of your admin tasks (except in kde control center where I think the code is still completely missing...) I don't know what the "right" answer is. Everyone says not to use sudo, but nobody has fixed kdesu. A rather sticky wicket...
I have even at some stage left the keep password box checked and suffered no problems, it just carries on prompting for the password. I don't mind this behaviour, I usually have a root console and yast2 control center open all the time. Do you have a factory system running at all? Regards Dave P. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Dave Plater wrote:
David C. Rankin wrote:
On Tuesday 09 June 2009 08:43:27 Dave Plater wrote:
Yast2 software management will not run from kde4 at all. Yast2 control center starts from a root konsole but I can't start software management from control center either. The log hangs at:- 2009-06-09 15:36:27 <1> Arbuthnot(4317) [ui] YUI.cc(YUI):62 Creating UI with threads Any ideas what to file a bug report against? Yast2 software management runs under kde3. Regards Dave P
Dave,
I have fought this from 2 different directions. See my post (this list) of earlier today: Passwordless Access to Apps for Admins: sudo or kdesu for 11.2/kde4.
Check your .kde4/share/config/kdesurc and make sure it doesn't contain anything other than:
18:01 alchemy:~> cat .kde4/share/config/kdesurc [Passwords] Keep=true
davepl@Arbuthnot:~> cat .kde4/share/config/kdesurc [Passwords] Keep=false
If it does, kdesu will behave very strange. With this setting I can access yast2, just by clicking on the yast icon and I get the prompt for the password:
http://www.3111skyline.com/download/openSUSE_bugs/kde4/screenshots/kdesu-yas... OK.jpeg
However, it is annoying to be constantly prompted for the root password for every admin task and there should be some way of configuring kdesu to check group policies, etc.. so that access is given to those that need it (ME in particular).
I do use sudo from the command line and I had resisted to temptation to set super-user to sudo for kde4 hoping to find a way to make kdesu work, but the only way I have to giving myself root access to all admin tasks without being prompted for a password is to use the old kwriteconfig had typed into a terminal as a normal user that modifies your .kde4/share/config/kdesurc. After setting up sudo as normal, issuing:
kwriteconfig --file kdesurc --group super-user-command --key super-user- command sudo
Modifies kdesurc as follows:
20:57 alchemy:~> cat .kde4/share/config/kdesurc [Passwords] Keep=true
[super-user-command] super-user-command=sudo
In this configuration, you get root access to all of your admin tasks (except in kde control center where I think the code is still completely missing...) I don't know what the "right" answer is. Everyone says not to use sudo, but nobody has fixed kdesu. A rather sticky wicket...
Just to say your modification of kdesurc works and I only had to enter root password once and the next time I tried to start yast2 control center I wasn't prompted for a password. Doing the mod to kdesurc also resulted in my problem disappearing. I have a sneaky suspicion that there was no empty eol at the end of the file but I need to earn some money and will try and get the problem back when I have finished. Regards Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Dave Plater wrote:
Hi, my kde4 is up to date and now I cannot get any programs that run as root to start from the menu. The kde4 run command doesn't prompt for root password nor does any menu item that is supposed to run as root i.e. yast2. The only way I can get yast2 for example, to start is in kde3 from the run command after entering the root password. I can't get yast2 sw_single to start in kde4 konsole after issuing the su command it just hangs but zypper works. Kde3s konsole works as expected and both yast2 and yast2 sw_single work as expected. sudo /sbin/yast2 starts the ncurses version in a user konsole in kde3, I haven't tried sudo in kde4. Any clues as to what package could have caused this? Regards Dave P
Run yast2 sw_single as root with "strace -s 256 -f yast2 sw_single" and see if it hangs at the same place mine does. I have had this error since the last zypper dup a few days before Milestone1 became available and it's still there on all boxes at Milestone 2 ++. I have an unresolved open bug 487060 on this. It's not only yast2, it's other applications also like VirtualBox and qjackctl. The strange thing is I can "ssh -X" in over the network and run them as root without problems. There are also bugs 458230 and 400834 that have flavours of this. <STUFF DELETED> [pid 27779] read(14, "", 2048) = 0 [pid 27779] close(14) = 0 [pid 27779] futex(0x13d576c, FUTEX_WAIT_PRIVATE, 1, NULL Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Dave Plater wrote:
Hi, my kde4 is up to date and now I cannot get any programs that run as root to start from the menu. The kde4 run command doesn't prompt for root password nor does any menu item that is supposed to run as root i.e. yast2. The only way I can get yast2 for example, to start is in kde3 from the run command after entering the root password. I can't get yast2 sw_single to start in kde4 konsole after issuing the su command it just hangs but zypper works. Kde3s konsole works as expected and both yast2 and yast2 sw_single work as expected. sudo /sbin/yast2 starts the ncurses version in a user konsole in kde3, I haven't tried sudo in kde4. Any clues as to what package could have caused this? Regards Dave P
Opened bug http://bugzilla.novell.com/show_bug.cgi?id=511480 Regards Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Dave Plater wrote:
Hi, my kde4 is up to date and now I cannot get any programs that run as root to start from the menu. The kde4 run command doesn't prompt for root password nor does any menu item that is supposed to run as root i.e. yast2. The only way I can get yast2 for example, to start is in kde3 from the run command after entering the root password. I can't get yast2 sw_single to start in kde4 konsole after issuing the su command it just hangs but zypper works. Kde3s konsole works as expected and both yast2 and yast2 sw_single work as expected. sudo /sbin/yast2 starts the ncurses version in a user konsole in kde3, I haven't tried sudo in kde4. Any clues as to what package could have caused this? Regards Dave P
I hate these mysteries. I rebooted for about the 4th time into kde3 then logged out and into kde4, which I have done more times than I can remember while trying to debug the problem and everything now works in kde4, which I'm pretty certain it did after my update. The only thing I changed was kdesurc which I added David's suggestion to enable keeping the root password. I have changed it back to what it was and I will see if the problem reoccurs. Regards Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Dave Plater wrote:
Hi, my kde4 is up to date and now I cannot get any programs that run as root to start from the menu. The kde4 run command doesn't prompt for root password nor does any menu item that is supposed to run as root i.e. yast2. The only way I can get yast2 for example, to start is in kde3 from the run command after entering the root password. I can't get yast2 sw_single to start in kde4 konsole after issuing the su command it just hangs but zypper works. Kde3s konsole works as expected and both yast2 and yast2 sw_single work as expected. sudo /sbin/yast2 starts the ncurses version in a user konsole in kde3, I haven't tried sudo in kde4. Any clues as to what package could have caused this? Regards Dave P
I'm no unix expert unfortunately so I need help to find out where this problem came from. The only thing I changed that fixed the problem was editing ~/.kde4/share/config/kdesurc. I have returned the file to it's original state and even tried removing the blank eol (0x0D) at the end of the file. The only other thing I did to my system was added relatime to my fstab, is it possible this created the problem? I can no longer recreate the bug. I am almost certain it didn't start after my last update. Regards Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (4)
-
Dave Plater -
David C. Rankin -
Mariusz Fik -
Sid Boyce