Bug 428215 - libgnome-menu.so.2: undefined symbol: g_directory_monitor_cancel
Summary: libgnome-menu.so.2: undefined symbol: g_directory_monitor_cancel
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-menus
Version: rawhide
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-01-09 23:38 UTC by sangu
Modified: 2008-01-12 01:28 UTC (History)
0 users

Fixed In Version: 2.21.3-2.fc9
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-01-12 01:28:43 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description sangu 2008-01-09 23:38:07 UTC
$ alacarte
Description of problem:
Traceback (most recent call last):
  File "/usr/bin/alacarte", line 22, in <module>
    from Alacarte.MainWindow import MainWindow
  File "/usr/lib/python2.5/site-packages/Alacarte/MainWindow.py", line 19, in
<module>
    import gtk, gtk.glade, gmenu, gobject, gnomevfs, gnome.ui
ImportError: /usr/lib/libgnome-menu.so.2: undefined symbol:
g_directory_monitor_cancel

$ ldd -r /usr/lib/libgnome-menu.so.2
undefined symbol: g_directory_monitor_cancel	(/usr/lib/libgnome-menu.so.2)
undefined symbol: g_directory_monitor_get_type	(/usr/lib/libgnome-menu.so.2)
	linux-gate.so.1 =>  (0x00110000)
	libgio-2.0.so.0 => /lib/libgio-2.0.so.0 (0x00121000)
	libgobject-2.0.so.0 => /lib/libgobject-2.0.so.0 (0x0018d000)
	libgmodule-2.0.so.0 => /lib/libgmodule-2.0.so.0 (0x001ce000)
	libdl.so.2 => /lib/libdl.so.2 (0x001d2000)
	libglib-2.0.so.0 => /lib/libglib-2.0.so.0 (0x001d7000)
	libc.so.6 => /lib/libc.so.6 (0x002b1000)
	libselinux.so.1 => /lib/libselinux.so.1 (0x00414000)
	/lib/ld-linux.so.2 (0xb7fc4000)


Version-Release number of selected component (if applicable):
2.21.3-1.fc9

How reproducible:
always

Steps to Reproduce:
1. alacarte
2.
3.
  
Actual results:


Expected results:


Additional info:
glib2-2.15.1-1.fc9


Note You need to log in before you can comment on or make changes to this bug.