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 482523 - crash in File Browser: Properties of DVD disc.
crash in File Browser: Properties of DVD disc.
Status: RESOLVED DUPLICATE of bug 485771
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-02 09:56 UTC by lukasz.goralczyk
Modified: 2007-10-19 02:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description lukasz.goralczyk 2007-10-02 09:56:17 UTC 
Version: 2.18.3

What were you doing when the application crashed?
Properties of DVD disc.


Distribution: Gentoo Base System release 1.12.10
Gnome Release: 2.18.3 2007-07-25 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-gentoo-r8 #1 SMP PREEMPT Tue Oct 2 11:00:19 CEST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: ThinIce
Icon Theme: Gion

Memory status: size: 343240704 vsize: 343240704 resident: 35954688 share: 21569536 rss: 35954688 rss_rlim: 18446744073709551615
CPU usage: start_time: 1191318914 rtime: 171 utime: 150 stime: 21 cutime:0 cstime: 0 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)
0x00002afe7d4c7c2f in waitpid () from /lib/libpthread.so.0

+ Trace 167081

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 strcmp
    from /lib/libc.so.6
  • #4 ??
  • #5 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #6 ??
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #9 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #11 ??
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #14 gtk_list_store_remove
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_list_store_clear
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 ??
  • #17 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #18 ??
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #21 nautilus_file_emit_changed
  • #22 nautilus_directory_emit_change_signals
  • #23 nautilus_file_changed
  • #24 ??
  • #25 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #26 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #27 ??
    from /usr/lib/libglib-2.0.so.0
  • #28 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #29 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 main 


----------- .xsession-errors (6 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
--------------------------------------------------
Comment 1 André Klapper 2007-10-03 11:05: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 lukasz.goralczyk 2007-10-03 13:47:23 UTC 
Hello,

OK, I will see what can I do, but, at the moment, I think not too much, as I'm using Gentoo and including debugging information isn't easy (ie. I would have to rebuild all the packages). But thanks for takeing time to answer this bug report (it was the first time I have done it with automatic bug reporting tool, I didn't know it works that way).

Regards,
Łukasz.
Comment 3 André Klapper 2007-10-19 02:02:36 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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