GNOME Bugzilla – Bug 471168
crash in Gimmie: I had just clicked the "...
Last modified: 2007-08-28 15:17:11 UTC
What were you doing when the application crashed? I had just clicked the "Disconnect" button in Amarok. I was disconnecting my iPod nano after transferring some tracks to it. The tracks hadn't quite finished tranferring, so Amarok prompted me as to whether I wanted to wait for the files to finish, or stop it immediately. I opted to finish, the nano was disconnected, and then this bug reporting dialog appeared. Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-11 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-16-generic #2 SMP Thu Jun 7 19:00:28 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: Human Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 ----------- .xsession-errors (110 sec old) --------------------- /etc/gdm/Xsession: Beginning session setup... SESSION_MANAGER=local/atticus:/tmp/.ICE-unix/5711 Window manager warning: "" found in configuration database is not a valid value for keybinding "toggle_shaded" Initializing gnome-mount extension evolution-alarm-notify-Message: Setting timeout for 32036 1188345600 1188313564 evolution-alarm-notify-Message: Tue Aug 28 18:00:00 2007 evolution-alarm-notify-Message: Tue Aug 28 09:06:04 2007 modinfo: could not find module fglrx modinfo: could not find module nvidia_legacy modinfo: could not find module nvidia_new (gnome-panel:5780): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -7 and height 24 sh: mpg123: not found -------------------------------------------------- Traceback (most recent call last):
+ Trace 158559
signal = self.event_mapping[event]
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 417686 ***