Red Hat Bugzilla – Bug 569969
"No system tray detected on this system"
Last modified: 2010-07-26 22:44:35 EDT
abrt 1.0.7 detected a crash.
Attached file: backtrace
cmdline: python /usr/bin/hp-systray -x
comment: I set the HP-Systray to start automatically on login using the "Startup Applications Preferences" tool provided by Fedora for the Gnome Desktop.
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
How to reproduce
1. Set HP-Systray to start automaticaly on login
2. log in to the Gnome Desktop
3. hp-lip-gui crashes w/ an error about there not being a tray to load into
Created attachment 397409 [details]
*** This bug has been marked as a duplicate of bug 543286 ***
Jim: please copy exactly what the error message says into this bug report.
In a message box that pops up, I have:
No system tray detected on this system.
Unable to start, exiting.
(copied and pasted)
I did notice in checking this that if I go into Gnome Start-up Applications tool, activate this for automatically starting, then log out and back in, I do not get the error.
If I shut the box completely down and re-start it with this activated as a start-up application, I get the message.
I did not notice this part of what's going on previously. Not certain it makes any difference anyway. Just something I noticed.
This is coming from ui4/systemtray.py. It's talking about the 'notification area' on the panel.
It's already waited for 10s to see if a system tray becomes available, and it still hasn't. My guess is it just needs to wait longer until the notification area applet starts up.
*** Bug 579277 has been marked as a duplicate of this bug. ***
Jim, can you try this build of hplip ?
Download the appropriate rpms into empty directory and install them as root:
yum localinstall --nogpgcheck *.rpm
It works!! :)
Up and going from a restart of the box. No error messages, no flashing abrt. Everything appears normal.
Nuts. It's still doing it. Occasionally anyway.
I powered (shut down) my laptop down when I went home yesterday. This morning when I booted up, I had the message back, but no crash notification from abrt.
I powered the computer completely back down and and brought it up a second time. hplip started without issue.
Jim, how long does it take your desktop to start up? Can you time it?
Hope you just meant w/ a stopwatch. I don't know how to write a script for that.
It ooks like 1 min 23 sec from the moment I click the login button after keying
in my password to where the hplip systray icon shows in the system tray.
When I first booted the box this AM after it was powered off all night, I received the error. When I powered down and brought it back up just now to time it, it worked fine.
I guess the slight difference it makes in having everything warmed up is affecting the timing just enough to make it work?
hplip-3.10.5-1.fc13 has been submitted as an update for Fedora 13.
hplip-3.10.5-1.fc12 has been submitted as an update for Fedora 12.
hplip-3.10.5-1.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update hplip'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/hplip-3.10.5-1.fc12
hplip-3.10.5-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
hplip-3.10.5-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.