|
Bugzilla – Full Text Bug Listing |
| Summary: | yast2: busy cursor displayed forever | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.2 | Reporter: | Stanislav Brabec <sbrabec> |
| Component: | GNOME | Assignee: | Vincent Untz <vuntz> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Minor | ||
| Priority: | P5 - None | CC: | forgotten_h13THG8RK1, odi, sreeves, vuntz |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | gnome-usability | ||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Stanislav Brabec
2008-05-12 09:08:36 UTC
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 ]. 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-notification-latest.txt 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. 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... *** Bug 394526 has been marked as a duplicate of this bug. *** good point; I forgot to do that ;-) It seems Scott here as been reviewing these application-browser / control-center bugs... This bug report has been open for awhile; let's clean up the dust. I vote to do away with the StartupNotify line from /usr/share/applications/YaST2/*.desktop. The tools open in a snap anyway; let's contact the yast2 guys? yast2 guys, long report short, gnome-su and StartupNotify in .desktop files are not best friends. Would it be an acceptable solution to remove that line? (In reply to comment #8) > yast2 guys, long report short, gnome-su and StartupNotify in .desktop files are > not best friends. Would it be an acceptable solution to remove that line? I'm afraid that would bring bug #304964 back to life ... bug 304964 seems more tolerable, but okay, changing component back to gnome... Err, I thought I fixed this already in libgnomesu (see libgnomesu-startup-notification.patch)? Is this still valid in 11.2? I can't reproduce here... You're correct; it is indeed working fine. |