gnome-panel doesn't respond

Bug #328378 reported by Andrey Zhekov
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gnome-panel (Ubuntu)
Incomplete
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-panel

Ubuntu Jaunty alpha 4

Gnome 2.25.90

After clicking on the clock applet it shows me the calendar and..... that's all.... the gnome-panel doesn't react on my actions. I can only switch between the windows of the opened apps with Alt-TAB

Revision history for this message
Andrey Zhekov (x3ro.daemon) wrote :
description: updated
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in gnome-panel:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Andrey Zhekov (x3ro.daemon) wrote :
Revision history for this message
Andrey Zhekov (x3ro.daemon) wrote :

The wright Backtrace, sorry for the previous:

Revision history for this message
Martijn vdS (martijn) wrote :

That backtrace is still not OK, but I've been trying for almost an hour, and I can't seem to get a good one either.

I think the problem is either with threading (in the panel itself, or libedataserver1.2-11) or the gnome-keyring calls it does (that's where most traces end up). I keep seeing "connection refused" calls to the g-k-d socket. The environment variables don't match the real gnome-keyring PID for some reason.

Revision history for this message
marmuta (marmuta) wrote :

Gnome-panel locks up here too and I had added a backtrace at
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/203527/comments/79.
I probably should have added it here, but I missed this bug before, sorry.

Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue likely bug #327347

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.