Hide Forgot
Created attachment 452674 [details] Screenshot showing missing panel applets Description of problem: I've been experiencing a really annoying bug with Gnome since F14 Beta was released where panel applets such as the stock clock, workspace switcher, window selector (and quite a few others) randomly disappear from the panel. Logging in and out sometimes brings them back, but lately only a reboot or three seems to fix things. Version-Release number of selected component (if applicable): Name : gnome-desktop Arch : x86_64 Version : 2.32.0 Release : 1.fc14 Name : gnome-panel Arch : x86_64 Version : 2.32.0.2 Release : 2.fc14 Name : gnome-applets Arch : x86_64 Epoch : 1 Version : 2.32.0 Release : 1.fc14 How reproducible: Sporadically. Steps to Reproduce: 1. Log in and start Gnome. Actual results: Stock clock, workspace switcher, window selector applets are missing. Expected results: All panel applets are displayed. Additional info: Attached is a screenshot showing exactly what I mean. In the panel at the top you'll see a space where the stock clock applet should be and in the bottom right there's another gap where I place the window selector applet.
Created attachment 452678 [details] Another screenshot with missing applet After three reboots I was able to get the clock applet back, but as you'll see from the attached screenshot the the window selector (bottom left) applet is still missing.
are you using stock metacity, compiz, or metacity with compositing? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Ah sorry, I should have mentioned. I'm using compiz. This did start happening before I even installed compiz/desktop-effects though. I'll try disabling compiz and see if I can still reproduce.
I've switched to standard desktop effects and over 8 reboots I could only reproduce this once (missing window selector applet). Is there any other information I can provide to help track this down?
possibly, but i'm not sure what, it seems rather erratic and I'm not aware of anyone experiencing anything similar. I suspect it's some kind of graphics driver issue rather than gnome-desktop exactly. can you provide X logs? https://fedoraproject.org/wiki/How_to_debug_Xorg_problems -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
When you reproduce the failure, if you manually start the applet from the command-line, do they crash? In the example you posted about the window selector applet, if you right-click the panel and attempt to manually add the applet, does it work?
oh, good point - can you tell if the applets are just crashing, or if it's a visual issue (they're there but invisible)? do you have this same issue with a fresh install? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I've actually been experiencing a similar bug on Fedora 13. Occasionally some panel applets don't show up when I log in and I have to run 'killall gnome-panel' once or twice to restart the panel and get them back. I've only seen this bug while running compiz, but then I rarely turn off desktop effects. If I can reproduce this bug, I'll see if I can provide more information.
Should this bug be reassigned to a different component than gnome-panel? Or is it too early to tell? We only have a few working days left before the change deadline and apparently need some developer attention to this bug.
(In reply to comment #9) > Should this bug be reassigned to a different component than gnome-panel? Or is > it too early to tell? We only have a few working days left before the change > deadline and apparently need some developer attention to this bug. If we can't further isolate this issue, and it doesn't occur after a fresh install, I recommend we remove this from the F14Blocker list soon. Outstanding questions that we need guidance on ... 1) When reproduced, are you able to manually start applets from the command-line 2) Does this problem occur with any frequency on a fresh install (with a new $HOME) 3) When reproduced, does the use of desktop-effects/compiz influence the outcome
Same situation as Theodore here. I'm experiencing this on F13 as well, i386. Especially the system tray and clock seem to be disappearing more often, launchers not so much. Without compiz enabled it never happened here. I'm not sure if we're experiencing the same issue or just have the same symptoms, but that's also happening on F13. Absolutely not reproducible. (In reply to comment #6) > When you reproduce the failure, if you manually start the applet from the > command-line, do they crash? In the example you posted about the window > selector applet, if you right-click the panel and attempt to manually add the > applet, does it work? They seem to be there, just invisible. I can add new applets easily without any crashes, just not put them where the invisible applets should be. Maybe a compiz issue?
Apologies for the lack of response from me, I've been busy working in a studio without access to a Linux machine. I'll take a proper read through all the comments in a few hours and post the requested additional information.
stickster: we need feedback to our most recent questions to determine where the bug lies, but since it seems quite specific to this reporter, we're likely to drop it from the blocker list. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I was able to reproduce this rather quickly with the following steps: 1. Create a new user and log in to Gnome. 2. Reboot. 3. Log in as new user. After repeating steps 2 and 3 a few times I was able to reproduce: missing "trashapplet" in the bottom right-hand corner. Running "/usr/libexec/trashapplet" in a terminal just hangs and doesn't bring the applet back. > When you reproduce the failure, if you manually start > the applet from the command-line, do they crash? In > the example you posted about the window selector applet, > if you right-click the panel and attempt to manually add > the applet, does it work? See above. In that instance I was able to add an additional "trashapplet" which showed up on the panel okay. > oh, good point - can you tell if the applets are just > crashing, or if it's a visual issue (they're there but > invisible)? do you have this same issue with a fresh > install? I can't say for sure, but since there are no abrt reports, I'm guessing they're not actually crashing. I'm possibly wrong here, but I'd say it's a visual thing rather than the applets actually crashing. I'll attach my (compressed) "/var/log/Xorg.0.log" just in case that might still be useful.
Created attachment 453329 [details] /var/log/Xorg.0.log
I forgot to mention in comment #14 that after logging in as the test user for the first time I enabled compiz. (In reply to comment #13) > stickster: we need feedback to our most recent questions to determine where the > bug lies, but since it seems quite specific to this reporter, we're likely to > drop it from the blocker list. I could give a fresh install a try at the weekend, but I'm guessing that'd probably be too late...
This seems to be a compiz issue from reading through the comments. FWIW, we've had compiz bugs along these lines in the past (some weird layer order bug or something). Reassigning. Given it's most likely a compiz issue, I don't think it's really blocker material either. Has anyone on the testing team tried to reproduce?
I've used compiz for a while a few times recently and haven't seen this, I suspect it also involves the GL driver. But I agree it's not a blocker if it's compiz only. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I agree. For extra discussion at the blocker meeting, I think this qualifies as a local site configuration issue and is in accordance with the release criteria (see the blocker bug FAQ at https://fedoraproject.org/wiki/Blocker_Bug_FAQ#What_about_hardware_and_local_configuration_dependent_issues.3F) ... Many bugs are not universal: they only affect certain hardware or software components, or certain configurations or combinations of hardware and software components. When a bug causes a criterion not to be met in some but not all cases, the teams involved in the release process will make a judgement as to whether the impact of the bug is severe enough to consider the release as a whole not to meet the release criteria. This judgement will be based on multiple factors: * The amount of users, overall, the issue is estimated likely to affect * The ease with which the issue can be worked around by documentable configuration changes * The difficulty involved in fixing the issue: whether there is a significant chance that attempting to fix the issue could cause more serious problems
I can confirm I've been having the same symptoms with F13 running compiz using radeon KMS driver. It started happening a couple of months ago, I think it was probably due to an update to F13. I rarely reboot so doesn't affect me often.
Sorry, should have added the applets do start but are not visible. eg. with hamster the key shortcut still brings the text entry box up. Kill and restart the applet fixes the issue.
reporter has an intel but Martin has radeon, so either they're seeing different but similar bugs, or the bug here is really outside of the graphics drivers. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
This was discussed at the 2010-10-15 blocker review meeting. We agreed it does not constitute a blocker as compiz is not part of the default desktop configuration, so it doesn't hit the criteria. It's also not an NTH issue as it can easily be resolved with an update. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Understood. Cheers for looking into it! With any luck we'll see a fix from upstream sometime in the not too distant. ;)
Experiencing this as well in F14 with Compiz. It's easily fixable temporarily by killing and restarting Compiz. Nonetheless a very annoying bug and many people *do* use Compiz. Is anyone actively chasing this up? Anything we can do to help?
I also have this same bug on Fedora 14 i686 with compiz enabled. Maybe I'm wrong but it almost looks like it started after creation of another user and enabling compiz for him. I can't be sure so I'll try doing some tests. Applets are hidden. First time this appeared I got empty space where clock/date should be so I just added to that place another clock/date applet. After reboot I got now two same clock/date applets. User session control also disappears and sometimes both clock/date and user session control.
I just logged out a couple of times and first time I logged out and logged in user session control in top right appeared but network manager and sound volume control disappeared. So I logged out again and logged into different user and found everything in place. Back in my first user also everything fixed. Will continue to probe it.
OK, so I logged as that second user and switched users back and forth. Second user lost network manager applet but the first user has it appeared. So this is something user related also?
Compiz disabled in both users. After switching back and forth between users and found that network manager applet is now missing in second user but not in first I logged out from second user and check will it appear after logging in. It didn't. I'll reboot to see how will things work then. After reboot, the error still is there even with compiz disabled in both users. That would mean this isn't compiz issue, right? If someone has only one normal user and doesn't experience this issue he should test it after adding another user but with compiz not enabled. I can't delete my second user cause I need it.
I could be wrong, but I'm pretty sure the network applet is only supposed to appear for one user, compiz or not. At least, that's how it's always been for me.
"the network applet is only supposed to appear for one user" should really be "the network applet is already broken for multiple users". Reference bug #456046 Agreed it is best to ignore NM for the purposes of this bug and only look at the other applets which fail to appear occasionally.
Maybe it's just me, but the issue seems to have disappeared since I started using compiz for GDM. You can do that with setting the gconf key /apps/gdm/simple-greeter/wm_use_compiz to true. May be random, but I can't reproduce it since I started using that.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping