Bug 84978
Summary: | workspace switcher doesn't correctly load space names on login | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Ian Macdonald <ian> |
Component: | libwnck | Assignee: | Mark McLoughlin <markmc> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-08-24 22:14:27 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ian Macdonald
2003-02-24 16:45:11 UTC
*** Bug 87567 has been marked as a duplicate of this bug. *** If I run 'gconftool-2 -R /apps/metacity/workspace_names', this shows the names of the workspaces correctly, so they *are* getting saved. Indeed, right-clicking on the desktop shows all of the names correctly in the menu. So, it seems it's just the workspace switcher applet that doesn't load them correctly at log-in time. They are also correct in the per-window menu? (top left corner in default theme?) This sounds more like a known bug, then. It happens if the workspace switcher starts before metacity does, I think, or something like that. Then metacity hasn't yet provided the space names. There may be a bugzilla.gnome.org bug for it already. Yes, the menu is correct. I tested your theory by removing the workspace switcher from the panel and re-adding it, which should theoretically have forced it to reread the file and pick up the names, but it didn't. It might be better to "killall gnome-panel" instead of just removing/readding that applet, as the libwnck code doesn't get unloaded on removing it most likely. Though it could definitely be a different problem. 'killall gnome-panel' doesn't fix it either, I'm afraid. Long since resolved, it seems |