gnome-panel crashes (and reloads) when launching applications

Bug #643332 reported by Leonor Palmeira
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-panel (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Dear all,

my gnome-panel crashes whenever I launch an application through it (and restarts) and does not launch any application. I suspect this comes from not being able to find the correct /path for the given application. Indeed, for my personal gnome-panel icons, if I change the path in the Properties to the full path of the application, the application is launched smoothly without crashing gnome-panel.

My $PATH includes all necessary paths, including /usr/bin.

Any idea on how to fix this, as I am totally unable to launch any application through the gnome menu...

I did a recent upgrade from 9.10 to 10.04 LTS, so it might be Lucid Lynx bug.

Thanks,
Leonor.

Revision history for this message
Leonor Palmeira (leonor-palmeira) wrote :

In my .xsession-errors, I get the following line at each attempt to launch an application through the gnome-menu:

gnome-panel: symbol lookup error: /usr/lib/libgdk-x11-2.0.so.0: undefined symbol: g_desktop_app_info_get_filename

Revision history for this message
Leonor Palmeira (leonor-palmeira) wrote :

/usr/lib/libgdk-x11-2.0.so.0 is a link to /usr/lib/libgdk-x11-2.0.so.0.2000.1, so:

cd /usr/lib
sudo rm libgdk-x11-2.0.so.0

Click on the gnome-panel to launch some application (say Firefox). This will crash gnome-panel, but gnome-panel will be unable to reload. Re-link the lib with:

sudo ln -s libgdk-x11-2.0.so.0.2000.1 libgdk-x11-2.0.so.0

The panel is now fully functional, but not if I login again (even without rebooting).
Any ideas on how to fix this in the long-run. I have seen similar problems with gnome-panel, but am not able to fix it.

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

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in gnome-panel (Ubuntu):
importance: Undecided → Medium
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

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