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 456948 - crash in Open Folder: properties of mounted dv...
crash in Open Folder: properties of mounted dv...
Status: RESOLVED DUPLICATE of bug 406462
Product: nautilus
Classification: Core
Component: general
2.19.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-07-14 20:57 UTC by kmberrychem
Modified: 2007-07-26 19:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description kmberrychem 2007-07-14 20:57:21 UTC 
Version: 2.19.5

What were you doing when the application crashed?
properties of mounted dvd


Distribution: Fedora release 7.89 (Rawhide)
Gnome Release: 2.19.5 2007-07-08 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:37:32 EDT 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 136572928 vsize: 136572928 resident: 24506368 share: 15327232 rss: 24506368 rss_rlim: 4294967295
CPU usage: start_time: 1184390419 rtime: 6261 utime: 5286 stime: 975 cutime:290 cstime: 78 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 -1208723696 (LWP 11637)]
(no debugging symbols found)
0x009b9402 in __kernel_vsyscall ()

+ Trace 148047

Thread 1 (Thread -1208723696 (LWP 11637))

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


----------- .xsession-errors (155402 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
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Pedro Villavicencio 2007-07-14 22:16:52 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that 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. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 André Klapper 2007-07-26 19:11:16 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 ***