GNOME Bugzilla – Bug 463669
crash in Main Menu: Je descendait un élément...
Last modified: 2007-08-08 09:01:34 UTC
Version: 0.11.3 What were you doing when the application crashed? Je descendait un élément dans un menu en cliquant de nombreuses fois sur le bouton "descendre" Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:21:43 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 372523008 vsize: 372523008 resident: 41611264 share: 21643264 rss: 41611264 rss_rlim: 18446744073709551615 CPU usage: start_time: 1186326060 rtime: 1297 utime: 1216 stime: 81 cutime:40 cstime: 11 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/alacarte' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496267040 (LWP 7225)] (no debugging symbols found) 0x000000352120d945 in waitpid () from /lib64/libpthread.so.0
+ Trace 152971
Thread 1 (Thread 46912496267040 (LWP 7225))
----------- .xsession-errors --------------------- Listening on LPF/wlan0/00:13:d3:85:45:58 Sending on LPF/wlan0/00:13:d3:85:45:58 Sending on Socket/fallback DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7 DHCPOFFER from 192.168.1.1 DHCPREQUEST on wlan0 to 255.255.255.255 port 67 DHCPACK from 192.168.1.1 bound to 192.168.1.2 -- renewal in 39179 seconds. No post-connection command specified. CONNECTION FAILED. disconnect: /sbin/iwconfig wlan0 mode managed key off ap off essid off Application options saved. Kernel socket closed. ICE default IO error handler doing an exit(), pid = 6232, errno = 0 "/usr/bin/alacarte": not in executable format: File format not recognized --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 430074 ***