GNOME Bugzilla – Bug 472028
crash in Gimmie: Opening a pdf file with ...
Last modified: 2007-08-31 08:19:13 UTC
What were you doing when the application crashed? Opening a pdf file with Adobe Acrobat from within my home folder. Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70000000 Selinux: No Accessibility: Disabled GTK+ Theme: Murrina-IndustrialSM Icon Theme: Cassandra 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 --------------------- (gnome-panel:7469): Wnck-WARNING **: Unhandled action type (nil) ALSA lib pcm.c:2106:(snd_pcm_open_conf) Cannot open shared library /usr/lib/alsa-lib/libasound_module_pcm_pulse.so ALSA lib pcm.c:2106:(snd_pcm_open_conf) Cannot open shared library /usr/lib/alsa-lib/libasound_module_pcm_pulse.so ALSA lib pcm.c:2106:(snd_pcm_open_conf) Cannot open shared library /usr/lib/alsa-lib/libasound_module_pcm_pulse.so (gnome-panel:7469): Wnck-WARNING **: Unhandled action type (nil) (gnome-panel:7469): Wnck-WARNING **: Unhandled action type (nil) ALSA lib pcm.c:2106:(snd_pcm_open_conf) Cannot open shared library /usr/lib/alsa-lib/libasound_module_pcm_pulse.so ALSA lib pcm.c:2106:(snd_pcm_open_conf) Cannot open shared library /usr/lib/alsa-lib/libasound_module_pcm_pulse.so /home/thad/.gtkrc-2.0:2: error: scanner: unterminated string constant - e.g. `style' (gnome-panel:7469): Wnck-WARNING **: Unhandled action type (nil) (gnome-panel:7469): Wnck-WARNING **: Unhandled action type (nil) -------------------------------------------------- Traceback (most recent call last):
+ Trace 159219
self.recent_items[recent_item.get_uri()] = recent_item
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 417988 ***