GNOME Bugzilla – Bug 441051
crash in Gimmie: one click! over "Linux" ...
Last modified: 2007-05-26 01:15:40 UTC
What were you doing when the application crashed? one click! over "Linux" :( Distribution: Debian lenny/sid Gnome Release: 2.18.1 2007-04-25 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.21-1-amd64 #1 SMP Fri May 18 23:28:21 CEST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Pharago Icon Theme: humility-icons-MERGE 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 --------------------- ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 LoadPlugin: failed to initialize shared library /home/sergio/.mozilla/plugins/libflashplayer.so [/home/sergio/.mozilla/plugins/libflashplayer.so: wrong ELF class: ELFCLASS32] ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave play stio: Failed writing default: cannot open audio device ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave play stio: Failed writing default: cannot open audio device ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave play stio: Failed writing default: cannot open audio device -------------------------------------------------- Traceback (most recent call last):
+ Trace 135901
self._show()
self.topic_win = self.topic.get_topic_window()
self.topic_window = TopicMenu(self)
TopicView.__init__(self, topic)
self.sidebar = Sidebar(topic)
self.add_sources()
for source in self.topic.get_sidebar_source_list():
self.do_reload()
source_list.append(AdministrationSource())
self.system_settings_menu_source = self.system_settings_menu_tree.get_toplevel_flat_source()
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 421732 ***