GNOME Bugzilla – Bug 545042
crash in Deskbar: pressed the "Bottom Butt...
Last modified: 2008-07-27 21:48:05 UTC
What were you doing when the application crashed? pressed the "Bottom Button" in "Searches" Tab Distribution: Ubuntu 8.04 (hardy) Gnome Release: 2.22.2 2008-06-03 (Ubuntu) BugBuddy Version: 2.22.0 System: Linux 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 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 (61 sec old) --------------------- aplay: main:546: audio open error: Device or resource busy ALSA lib pcm_dmix.c:874:(snd_pcm_dmix_open) unable to open slave aplay: main:546: audio open error: Device or resource busy ALSA lib pcm_dmix.c:874:(snd_pcm_dmix_open) unable to open slave aplay: main:546: audio open error: Device or resource busy ALSA lib pcm_dmix.c:874:(snd_pcm_dmix_open) unable to open slave aplay: main:546: audio open error: Device or resource busy ALSA lib pcm_dmix.c:874:(snd_pcm_dmix_open) unable to open slave aplay: main:546: audio open error: Device or resource busy ALSA lib pcm_dmix.c:874:(snd_pcm_dmix_open) unable to open slave aplay: main:546: audio open error: Device or resource busy ALSA lib pcm_dmix.c:874:(snd_pcm_dmix_open) unable to open slave aplay: main:546: audio open error: Device or resource busy ALSA lib pcm_dmix.c:874:(snd_pcm_dmix_open) unable to open slave aplay: main:546: audio open error: Device or resource busy -------------------------------------------------- Traceback (most recent call last):
+ Trace 203946
self.module_list.move_module_to_bottom(iter)
self.move_after(iter, self.get_iter(self._bottom_enabled_path))
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 488665 ***