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 481490 - crash in File Browser: The app hang after I clo...
crash in File Browser: The app hang after I clo...
Status: RESOLVED DUPLICATE of bug 406462
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-29 03:04 UTC by obueno
Modified: 2007-10-25 12:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description obueno 2007-09-29 03:04:32 UTC 
Version: 2.18.3

What were you doing when the application crashed?
The app hang after I close the properties windows of a mounted dvd


Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.18.3 2007-08-31 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-gentoo-r2 #1 SMP Sat Aug 18 01:47:10 PET 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Human
Icon Theme: Human2

Memory status: size: 328286208 vsize: 328286208 resident: 68218880 share: 30146560 rss: 68218880 rss_rlim: 18446744073709551615
CPU usage: start_time: 1190778981 rtime: 10587 utime: 9446 stime: 1141 cutime:3937 cstime: 423 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47671036681872 (LWP 22476)]
0x00002b5b45d2faef in waitpid () from /lib/libpthread.so.0

+ Trace 166322

Thread 1 (Thread 47671036681872 (LWP 22476))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 gtk_widget_get_toplevel
    from /usr/lib/libgtk-x11-2.0.so.0
  • #4 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 gtk_widget_has_screen
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #8 ??
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #10 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 main
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (472783 sec old) ---------------------
(10:43:24) yahoo: Key: 4  	Value: l_puchuri
(10:43:24) yahoo: Key: 1002  	Value: 1
(10:43:24) yahoo: Key: 5  	Value: obueno
(10:43:24) yahoo: Key: 13  	Value: 1
(10:43:24) yahoo: Key: 14  	Value:  
(10:43:24) yahoo: Key: 1  	Value: l_puchuri
(10:43:24) yahoo: Key: 49  	Value: TYPING
(10:43:27) yahoo: 90 bytes to read, rxlen is 110
(10:43:27) yahoo: Yahoo Service: 0x06 Status: 1
(10:43:27) yahoo: Key: 4  	Value: l_puchuri
(10:43:27) yahoo: Key: 206  	Value: 2
(10:43:27) yahoo: Key: 1002  	Value: 1
(10:43:27) yahoo: Key: 64  	Value: 0
(
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 André Klapper 2007-10-03 11:00:57 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 the application 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-10-25 12:35:12 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 406462 ***