GNOME Bugzilla – Bug 462632
crash in Gimmie: opening my "home" folder...
Last modified: 2007-09-14 21:58:12 UTC
What were you doing when the application crashed? opening my "home" folder. I have firefox, and kopete open. 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-lowlatency #2 SMP PREEMPT Thu Jun 7 20:23:03 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: UbuntuStudio Icon Theme: UbuntuStudio 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 (197 sec old) --------------------- Resource id: 0x0 Failed to open device Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply! kbuildsycoca running... Reusing existing ksycoca kio (KService*): WARNING: The desktop entry file /usr/share/applications/DefaultPlugins.desktop has Type=Link instead of "Application" or "Service" kio (KService*): WARNING: Invalid Service : /usr/share/applications/DefaultPlugins.desktop kio (KSycoca): ERROR: No database available! kbuildsycoca running... Reusing existing ksycoca kio (KService*): WARNING: The desktop entry file /usr/share/applications/DefaultPlugins.desktop has Type=Link instead of "Application" or "Service" kio (KService*): WARNING: Invalid Service : /usr/share/applications/DefaultPlugins.desktop kio (KSycoca): ERROR: No database available! Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply! Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply! -------------------------------------------------- Traceback (most recent call last):
+ Trace 152196
path = urllib.splittype(uri)[1]
match = _typeprog.match(url)
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 ***