Bug 498852 – crash in Home Folder: Abfragen der Eigenschaft...

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 498852 - crash in Home Folder: Abfragen der Eigenschaft...


Summary:	crash in Home Folder: Abfragen der Eigenschaft...


Status:	RESOLVED DUPLICATE of bug 440988

Product:	nautilus
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-11-21 22:34 UTC by solarisx
Modified:	2007-11-22 16:47 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description solarisx 2007-11-21 22:34:08 UTC

What were you doing when the application crashed?
Abfragen der Eigenschaften einer avi Datei am Desktop.


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks-DarkNice
Icon Theme: Amaranth

Memory status: size: 73170944 vsize: 73170944 resident: 23470080 share: 15269888 rss: 23470080 rss_rlim: 4294967295
CPU usage: start_time: 1195642605 rtime: 1881 utime: 1749 stime: 132 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6ccc8c0 (LWP 4730)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 179171

Thread 1 (Thread 0xb6ccc8c0 (LWP 4730))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 libgnomeui_segv_handle
at gnome-ui-init.c line 872
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/i686/cmov/libc.so.6
#6 abort
from /lib/i686/cmov/libc.so.6
#7 IA__g_logv
#8 IA__g_log
#9 IA__g_assert_warning
#10 ??
from /usr/lib/libgtk-x11-2.0.so.0
#11 ??
from /usr/lib/libgtk-x11-2.0.so.0
#12 ??
from /usr/lib/libgtk-x11-2.0.so.0
#13 ??
#14 ??
from /usr/lib/libgtk-x11-2.0.so.0
#15 ??
from /usr/lib/libgtk-x11-2.0.so.0
#16 ??
from /usr/lib/libgtk-x11-2.0.so.0
#17 ??
#18 ??
#19 ??
#20 ??
#21 ??
#22 ??
#23 ??
#24 ??
#25 ??
#26 ??
#27 ??
#28 ??
#29 ??
#30 ??
#31 ??
#32 ??
#33 ??
#34 ??
#35 ??
#36 ??
#37 ??
#38 ??
#39 ??
from /usr/lib/libgtk-x11-2.0.so.0
#40 ??
#41 ??
#42 ??
#43 ??
#44 ??
#45 ??
#46 ??
#47 ??
from /usr/lib/libgtk-x11-2.0.so.0
#48 ??
#49 ??
#50 ??
#51 ??
#52 ??
#53 ??
#54 g_sequence_sort_changed_iter
#0 __kernel_vsyscall



----------- .xsession-errors (38267 sec old) ---------------------
** (nm-applet:4792): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.19" is not allowed to own the service "org.freedesktop.Networ
** (nm-applet:4792): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.19" is not allowed to own the service "org.freedesktop.Networ
** (nm-applet:4792): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.19" is not allowed to own the service "org.freedesktop.Networ
** (nm-applet:4792): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.19" is not allowed to own the service "org.freedesktop.Networ
** (nm-applet:4792): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.19" is not allowed to own the service "org.freedesktop.Networ
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Christoph Wolk 2007-11-22 16:47:09 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 is a Debian specific bug, and Debian is working on providing a fix for
this problem.

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