#14745 closed bug (not reproducible)
Deskbar non-functional, red network indicator, and apps launch but never appear on desktop
Reported by: | vidrep | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | Applications/Deskbar | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
After updating to hrev52625 x86_64, the Deskbar fails to work when clicking on the leaf. Attempting to launch any app appears to fail (nothing happens). Team Monitor cannot be invoked with Ctrl-Alt-Del. Mouse pointer is working, and opening folders and navigating appears to be unaffected. I did note that the Network icon in the taskbar is red. Pushing the power button to initiate shutdown brings up a series of dialogs to kill the various apps which I tried to launch as well as each of the running servers. Syslog(s) attached.
Attachments (3)
Change History (14)
by , 6 years ago
Attachment: | previous_syslog added |
---|
by , 6 years ago
comment:1 by , 6 years ago
comment:2 by , 6 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:3 by , 6 years ago
Those lines are early bootloader output that is sometimes captured and sometimes not for various reasons. If that was the problem, your system would not have booted at all.
I'm not sure why this is assigned to me...
comment:4 by , 6 years ago
Owner: | changed from | to
---|
comment:6 by , 6 years ago
Still happening on hrev52715 x86_64. I have attached another syslog which may give a clue.
by , 6 years ago
comment:7 by , 6 years ago
Summary: | Deskbar non-functional and apps fail to launch → Deskbar non-functional, red network indicator, and apps launch but never appear on desktop |
---|
comment:8 by , 6 years ago
Component: | - General → Applications/Deskbar |
---|
comment:10 by , 6 years ago
Resolution: | → not reproducible |
---|---|
Status: | assigned → closed |
comment:11 by , 5 years ago
Remove milestone for tickets with status = closed and resolution != fixed
The previous_syslog contains the following lines which seem out of place and may give a clue: