Bug 394839 – crash in Computer: Had just tried out qt th...

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 394839 - crash in Computer: Had just tried out qt th...


Summary:	crash in Computer: Had just tried out qt th...


Status:	RESOLVED DUPLICATE of bug 356181

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

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

URL:
Whiteboard:

Duplicates:	394838 (view as bug list)
Depends on:
Blocks:

Reported:	2007-01-09 22:32 UTC by spock
Modified:	2007-02-14 18:03 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description spock 2007-01-09 22:32:39 UTC

What were you doing when the application crashed?
Had just tried out qt theme, and tried to go to next theme in list


Distribution: Mandriva Linux release 2007.0 (Official) for i586
Gnome Release: 2.16.0 2006-09-04 (Mandriva)
BugBuddy Version: 2.16.0

Memory status: size: 86237184 vsize: 0 resident: 86237184 share: 0 rss: 28131328 rss_rlim: 0
CPU usage: start_time: 1168381759 rtime: 0 utime: 231 stime: 0 cutime:214 cstime: 0 timeout: 17 it_real_value: 0 frequency: 17

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/libthread_db.so.1".
(no debugging symbols found)
`shared object read from target memory' has disappeared; keeping its symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1228138176 (LWP 6504)]
(no debugging symbols found)
0xbfffe410 in __kernel_vsyscall ()

+ Trace 100848

Thread 1 (Thread -1228138176 (LWP 6504))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/i686/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
#5 gdk_x11_drawable_get_xdisplay
from /usr/lib/libgdk-x11-2.0.so.0
#6 gdk_events_pending
from /usr/lib/libgdk-x11-2.0.so.0
#7 gdk_events_pending
from /usr/lib/libgdk-x11-2.0.so.0
#8 gdk_add_client_message_filter
from /usr/lib/libgdk-x11-2.0.so.0
#9 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#10 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#11 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#12 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#13 POA_Nautilus_MetafileMonitor__init
#14 __libc_start_main
from /lib/i686/libc.so.6
#15 ??

Comment 1 André Klapper 2007-01-11 12:58:24 UTC

Thanks for taking the time to report this bug.
Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash.

Could you please help fixing this by installing some debugging packages [1], start Nautilus as normal, and try to reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance!

[1] Please install debug packages for nautilus, glib2, gtk2, pango, gnome-vfs2, libgnome, and libgnomeui.

More details can be found here: http://live.gnome.org/GettingTraces

Comment 2 André Klapper 2007-01-11 12:59:11 UTC

*** Bug 394838 has been marked as a duplicate of this bug. ***

Comment 3 André Klapper 2007-02-14 18:03:33 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 356181 ***