https://bugzilla.novell.com/show_bug.cgi?id=389241 User mmeeks@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=389241#c2 Michael Meeks <mmeeks@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|YaST2 |GNOME Summary|busy cursor displayed forever |yast2: busy cursor displayed forever --- Comment #2 from Michael Meeks <mmeeks@novell.com> 2008-05-13 06:06:04 MST --- We do the right (toolkit / built-in) startup notification completion stuff in yast2-gtk. So this looks like a generic gnome-su problem.
From an strace -f of the control-center running as root we see:
transaction setup; cf. http://standards.freedesktop.org/startup-notification-spec/startup-notificat... 10789 1210678929.888359 writev(3, [{"\1\0\n\0\335\6\200\5L\0\0\0\234\377\234\377\1\0\1\0\0\0\0\0\0\0\0\0\0\n\0\0\1\0\0\0\0\0B\0\31\0\v\0L\0\0\0\0\0@\0!\10\0\0\335\6\200\5\210\1\0\0new: ID=y2controlcen\31\0\v\0L\0\0\0\0\0@\0!\10\0\0\335\6\200\5\207\1\0\0ter-gnome/gnomesu/10\31\0\v\0L\0\0\0\0\0@\0!\10\0\0\335\6\200\5\207\1\0\000789-2-t60p_TIME43961\31\0\v\0L\0\0\0\0\0@\0!\10\0\0\335\6\200\5\207\1\0\0008828 SCREEN=0 NAME=J\31\0\v\0L\0\0\0\0\0@\0!\10\0\0\335\6\200\5\207\1\0\0oystick DESCRIPTION=\31\0\v\0L\0\0\0\0\0@\0!\10\0\0\335\6\200\5\207\1\0\0Starting\\ Joystick B\31\0\v\0L\0\0\0\0\0@\0!\10\0\0\335\6\200\5\207\1\0\0IN=gnomesu ICON=yast\31\0\v\0L\0\0\0\0\0@\0!\10\0\0\335\6\200\5\207\1\0\0-joystick\0 ICON=yast\4\0\2\0\335\6\200\5", 400}], 1) = 400 ie. it is doing startup-notification on gnomesu - even though we are root already ;-) and then: 11016 1210678929.904792 execve("/usr/bin/gnomesu", ["gnomesu", "--", "/sbin/yast2", "joystick"], [/* 87 vars */] <unfinished ...> launching the joystick capplet. But of course, this is a special case for gnomesu: we are already root: thus I speculate that (though gnomesu connects to X in this case), it doesn't cleanly complete the startup notification. Of course - why we are launching gnomesu when we are root already is unclear to me ;-) - is it possible that we are also clobbering DESKTOP_STARTUP_ID in gnome-su in this case ? Anyhow - a Gnome bug I think. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.