Bug 546657 – crash in Computer:

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 546657 - crash in Computer:


Summary:	crash in Computer:


Status:	RESOLVED DUPLICATE of bug 386858

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.20.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-08-06 19:03 UTC by vero.bugenne
Modified:	2008-08-07 08:12 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description vero.bugenne 2008-08-06 19:03:18 UTC

Version: 2.20.0

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-amd64 #1 SMP Wed Jul 30 18:46:19 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Lush
Icon Theme: Lush

Memory status: size: 439128064 vsize: 439128064 resident: 13119488 share: 10555392 rss: 13119488 rss_rlim: 18446744073709551615
CPU usage: start_time: 1218048973 rtime: 10 utime: 4 stime: 6 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7fa2fee17780 (LWP 9471)]
[New Thread 0x42f4a950 (LWP 9517)]
(no debugging symbols found)
0x00007fa2f9e37394 in __lll_lock_wait () from /lib/libpthread.so.0

+ Trace 204737

Thread 2 (Thread 0x42f4a950 (LWP 9517))

#0 waitpid
from /lib/libpthread.so.0
#1 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#2 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#3 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#4 <signal handler called>
#5 gnome_vfs_uri_unref
from /usr/lib/libgnomevfs-2.so.0
#6 g_list_foreach
from /usr/lib/libglib-2.0.so.0
#7 gnome_vfs_uri_list_unref
from /usr/lib/libgnomevfs-2.so.0
#8 gnome_vfs_uri_list_free
from /usr/lib/libgnomevfs-2.so.0
#9 ??
from /usr/lib/libgnomevfs-2.so.0
#10 ??
from /usr/lib/libgnomevfs-2.so.0
#11 ??
from /usr/lib/libgnomevfs-2.so.0
#12 ??
from /usr/lib/libglib-2.0.so.0
#13 ??
from /usr/lib/libglib-2.0.so.0
#14 start_thread
from /lib/libpthread.so.0
#15 clone
from /lib/libc.so.6
#16 ??



----------- .xsession-errors ---------------------
kdeinit4: preparing to launch /usr/lib/kde4/libexec/klauncher
kdeinit4: preparing to launch /usr/bin/kded4
kdeinit4: preparing to launch /usr/bin/kbuildsycoca4
kbuildsycoca4 running...
** (nm-applet:9494): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.98" is not allowed to own the service "org.freedesktop.Networ
kbuildsycoca4(9715) KBuildSycoca::checkDirTimestamps: timestamp changed: "/etc/xdg/menus/debian-menu.menu"
kbuildsycoca4(9715) kdemain: Reusing existing ksycoca
** (nm-applet:9494): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.98" is not allowed to own the service "org.freedesktop.Networ
kbuildsycoca4(9715) KConfigGroup::readXdgListEntry: List entry MimeType in "/usr/share/applications/wine.desktop" is not compliant with XDG standard (missing trailing semicolon). 
kbuildsycoca4(9715) KConfigGroup::readXdgListEntry: List entry Categories in "/usr/share/applications/avidemux-gtk.desktop" is not compliant with XDG standard (missing trailing semicolon). 
kbuildsycoca4(9715) KConfigGroup::readXdgListEntry: List entry MimeType in "/usr/share/applications/avidemux-gtk.desktop" is not compliant with XDG standard (missing trailing semicolon). 
--------------------------------------------------

Comment 1 A. Walton 2008-08-07 08:12:44 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 386858 ***