[Bug 389241] New: busy cursor displayed forever
https://bugzilla.novell.com/show_bug.cgi?id=389241 Summary: busy cursor displayed forever Product: openSUSE 11.0 Version: Beta 2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: sbrabec@novell.com QAContact: jsrain@novell.com Found By: --- How to reproduce: 1. Have a GNOME installation of 11.0 beta2. 2. Run YaST from the GNOME menu. After password confirmation, the main menu appears (no busy cursor at all). 3. Then launch any module. Module appears. 4. Moving the cursor outside of the YaST window to the background (nautilus), busy cursor is displayed. 5. Close the module. Module disappears. 6. Moving the cursor outside of the YaST window to the background (nautilus), busy cursor is still displayed. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=389241 Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |mmeeks@novell.com -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=389241 User mmeeks@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=389241#c1 --- Comment #1 from Michael Meeks <mmeeks@novell.com> 2008-05-13 05:59:30 MST --- Yep - clearly startup notification is failing for some (strange) reason; possibly related to the fact that 'gnomesu' is forked again even when we are root - and it doesn't create a window, or cancel the startup notification [ I guess ]. -- 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.
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.
https://bugzilla.novell.com/show_bug.cgi?id=389241 User rpmcruz@alunos.dcc.fc.up.pt added comment https://bugzilla.novell.com/show_bug.cgi?id=389241#c3 Ricardo Cruz <rpmcruz@alunos.dcc.fc.up.pt> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rpmcruz@alunos.dcc.fc.up.pt --- Comment #3 from Ricardo Cruz <rpmcruz@alunos.dcc.fc.up.pt> 2008-05-23 10:45:24 MDT --- Michael: perhaps this be assigned to the default guys? Possibly, I guess we could just get rid of the busy cursor from y2controlcenter-gnome... :-/ Yast tools are very fast to launch anyway... -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=389241 User rpmcruz@alunos.dcc.fc.up.pt added comment https://bugzilla.novell.com/show_bug.cgi?id=389241#c4 Ricardo Cruz <rpmcruz@alunos.dcc.fc.up.pt> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |odi@ct.heise.de --- Comment #4 from Ricardo Cruz <rpmcruz@alunos.dcc.fc.up.pt> 2008-05-26 11:23:33 MDT --- *** Bug 394526 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=394526 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=389241 User mmeeks@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=389241#c5 Michael Meeks <mmeeks@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mmeeks@novell.com |bnc-team-gnome@forge.provo.novell.com QAContact|jsrain@novell.com |qa@suse.de --- Comment #5 from Michael Meeks <mmeeks@novell.com> 2008-05-27 04:51:26 MDT --- good point; I forgot to do that ;-) -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=389241 Rodrigo Moya <rodrigo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rodrigo@novell.com AssignedTo|bnc-team-gnome@forge.provo.novell.com |jpr@novell.com Priority|P5 - None |P4 - Low Status Whiteboard| |gnome-usability -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=389241 User rpmcruz@alunos.dcc.fc.up.pt added comment https://bugzilla.novell.com/show_bug.cgi?id=389241#c6 Ricardo Cruz <rpmcruz@alunos.dcc.fc.up.pt> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sreeves@novell.com --- Comment #6 from Ricardo Cruz <rpmcruz@alunos.dcc.fc.up.pt> 2008-09-04 07:26:28 MDT --- It seems Scott here as been reviewing these application-browser / control-center bugs... -- 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.
participants (1)
-
bugzilla_noreply＠novell.com