[Gutsy] Gnome panel freezes after scheduled filesystem chek on login

Bug #176903 reported by Gert Kulyk
2
Affects Status Importance Assigned to Milestone
gnome-panel (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-panel

Everytime after a scheduled fsck.ext3 run on boot, the first login into gnome-session results in an unresponsive panel, mouse-clicking-events are ignored while mouse cursor is still responsive. Killing gnome-panel via terminal (started via ALT-F2) resolves this.

Additional Information concerning my configuration:

Stock gutsy gnome (fresh install just after final gutsy-release, not migrated from prior ubuntu-versions) with all current updates, using metacity, running on a HP NX 6110 Laptop with synaptics touchpad as primary mouse device.

Filesystem of root and home-partition: ext3, pass values in fstab: 1 (root) and 2 (home).

The problem I face is, that I cannot find any useful information in the logs, neither in ~/.xsession-errors nor in syslog.
Any Idea why this is happening?

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file 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
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

Changed in gnome-panel:
status: Incomplete → Invalid
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.