Red Hat Bugzilla – Bug 205382
Programs don't start when menu items are clicked.
Last modified: 2008-03-18 14:34:28 EDT
Description of problem:
All new programs fails to start. When a system menu item, or shortcut icon on
panel, is clicked the program fails to show. A new item appears on the windows
list, with label Starting Terminal. After approximately 10 seconds, the window
list item disappears. It doesn't appear in the window list either. Nor is it
possible to Alt-Tab to it.
This happens irregulary, and I've not been able to figure out what triggers it.
When the system is just booted, starting new programs always work. Before some
kind of transition all programs could be started normally, but after the
transition no programs can be started. The transition takes place after an
appearently random amount of time.
Version-Release number of selected component (if applicable):
I'm not sure which components are in question here. However, the system is
updated with yum (yum -y update) using standard repositeries.
Steps to Reproduce:
1. Start a new program, for eksampel System menu->Places->Home folder.
2. See window list panel be updated: "Starting Home Folder".
3. Wait 10 seconds.
Window list item ("Starting Home Folder") disappears. Home Folder application
Home Folder application be started.
Always fine after reboot. No remarks in /var/log/messages og /var/log/Xorg.log.
ps aux does not list the programs which I've tried to start. Opening new browser
windows from Firefox (Ctrl-N) works.
I don't know what component is in question. Feel free to reclassify this bug.
"Starting Terminal" was just an example. Should be "Starting [Application]"
Is your hostname changing maybe?
I doubt my hostname changes. I use DHCP and run my own DNS-server which is
authorative for this IP-range (192.168.1.xxx). No PTR-record exits for the IP in
question, so I've seen nothing but dhcppc1 as hostname.
We no longer support Fedora Core 5 and I am currently trying to get my open bug
count down to a more manageable state. I'm going to close this bug as WONTFIX.
If this issue is still a concern for you, would you mind trying to reproduce on
a supported version of Fedora and reopening?
(this is a mass message)