Bug 440668 – crash in Computer:

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 440668 - crash in Computer:


Summary:	crash in Computer:


Status:	RESOLVED DUPLICATE of bug 406462

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-05-23 11:20 UTC by A S Alam
Modified:	2007-05-30 09:05 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description A S Alam 2007-05-23 11:20:42 UTC

Version: 2.19.2

What were you doing when the application crashed?



Distribution: Fedora release 6.93 (Rawhide)
Gnome Release: 2.19.2 2007-05-19 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3173.fc8 #1 SMP Fri May 18 17:35:17 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome

Memory status: size: 101974016 vsize: 101974016 resident: 36548608 share: 25157632 rss: 36548608 rss_rlim: 4294967295
CPU usage: start_time: 1179919186 rtime: 167 utime: 155 stime: 12 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208416544 (LWP 6907)]
0x00d3e402 in __kernel_vsyscall ()

+ Trace 135661

Thread 1 (Thread -1208416544 (LWP 6907))

#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 /lib/libglib-2.0.so.0
#9 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#10 ??
from /lib/libglib-2.0.so.0
#11 g_main_loop_run
from /lib/libglib-2.0.so.0
#12 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#13 main
at nautilus-main.c line 548
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 8e242d0
** Message: volume = 0
** Message: drive = 9241240
** Message: volume = 910e570
** (nautilus:6907): WARNING **: 'computer:///Filesystem.desktop' ਫਾਇਲ ਲਿਖਣ ਵਿੱਚ ਗਲਤੀ: ਕਾਰਵਾਈ ਦੀ ਇਜ਼ਾਜ਼ਤ ਨਹੀਂ ਹੈ
** (nautilus:6907): WARNING **: 'computer:///Filesystem.desktop' ਫਾਇਲ ਲਿਖਣ ਵਿੱਚ ਗਲਤੀ: ਕਾਰਵਾਈ ਦੀ ਇਜ਼ਾਜ਼ਤ ਨਹੀਂ ਹੈ
Cannot access memory at address 0x60103
Cannot access memory at address 0x60103
--------------------------------------------------

Comment 1 A S Alam 2007-05-23 11:21:59 UTC

Checking properities of USB Pen drive, during close the Properties box, it crashed

Comment 2 palfrey 2007-05-23 13:45:28 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.
Thanks in advance!

Comment 3 A S Alam 2007-05-24 05:20:17 UTC

Can you please provide more detail what else Element required in Report?

thanks

Comment 4 palfrey 2007-05-24 11:27:47 UTC

If you can reproduce this bug, then we need you to install the debugging packages for gtk+ and glib (see http://live.gnome.org/GettingTraces/DistroSpecificInstructions for how to do this), and then get us a better stacktrace (see http://live.gnome.org/GettingTraces/Details#obtain-a-stacktrace for how to do this).

Comment 5 A S Alam 2007-05-25 06:41:32 UTC

ok, now I have gtk, glibc, glibc2, natilus debuginfo package installed in Fedora machine.
--------------
Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.19.2 2007-05-19 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3173.fc8 #1 SMP Fri May 18 17:35:17 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome

Memory status: size: 102514688 vsize: 102514688 resident: 36798464 share: 25403392 rss: 36798464 rss_rlim: 4294967295
CPU usage: start_time: 1180075066 rtime: 167 utime: 149 stime: 18 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208662304 (LWP 2511)]
0x00ccd402 in __kernel_vsyscall ()

+ Trace 135945

Thread 1 (Thread -1208662304 (LWP 2511))

#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 g_idle_dispatch
at gmain.c line 4096
#10 IA__g_main_context_dispatch
at gmain.c line 2061
#11 g_main_context_iterate
at gmain.c line 2694
#12 IA__g_main_loop_run
at gmain.c line 2898
#13 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#14 main
at nautilus-main.c line 548
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
--- Hash table keys for warning below:
--> file:///home/aalam
(nautilus:3070): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 8b62e90
** Message: volume = 8c81120
** Message: drive = 89660b0
** Message: volume = 0
Cannot access memory at address 0x60103
Cannot access memory at address 0x60103
--------------------------------------------------

Comment 6 palfrey 2007-05-25 10:49:53 UTC

(In reply to comment #5)
> ok, now I have gtk, glibc, glibc2, natilus debuginfo package installed in
> Fedora machine.

Ah. Forgot about the Fedora package naming... you need specifically the gtk2-debuginfo and glib2-debuginfo packages. You've installed the 1.x versions of glib and gtk.

Comment 7 A S Alam 2007-05-25 10:59:36 UTC

yes, only GTK2 package was missing, other were following:
--------
glib2-debuginfo
gtk2-debuginfo
nautilus-debuginfo

--------
Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.19.2 2007-05-19 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3173.fc8 #1 SMP Fri May 18 17:35:17 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome

Memory status: size: 102227968 vsize: 102227968 resident: 37310464 share: 25550848 rss: 37310464 rss_rlim: 4294967295
CPU usage: start_time: 1180090580 rtime: 174 utime: 159 stime: 15 cutime:40 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208994080 (LWP 5522)]
0x00193402 in __kernel_vsyscall ()

+ Trace 135975

Thread 1 (Thread -1208994080 (LWP 5522))

#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 g_idle_dispatch
at gmain.c line 4096
#10 IA__g_main_context_dispatch
at gmain.c line 2061
#11 g_main_context_iterate
at gmain.c line 2694
#12 IA__g_main_loop_run
at gmain.c line 2898
#13 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#14 main
at nautilus-main.c line 548
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = b0975fc0
** Message: volume = 8a26090
** Message: drive = 86b00b0
** Message: volume = 0
warning: the debug information found in "/usr/lib/debug//usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-jpeg.so.debug" does not match "/usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-jpeg.so" (CRC mis
Cannot access memory at address 0x60103
Cannot access memory at address 0x60103
--------------------------------------------------

Comment 8 palfrey 2007-05-25 11:19:45 UTC

Stacktrace still isn't very good. Can you reproduce this while running Nautilus under gdb? See http://live.gnome.org/GettingTraces/Details#gdb-not-yet-running for details how to do this.

Comment 9 A S Alam 2007-05-30 05:09:48 UTC

ok, one more try with kde desktop and run nautilus with gdb,

(Press Close button after see properties of Mounted device
-------------------
[aalam@alamPunjabi pa-213]$ gdb nautilus
GNU gdb Red Hat Linux (6.6-14.fc7rh)
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) run
Starting program: /usr/bin/nautilus
[Thread debugging using libthread_db enabled]
[New Thread -1208391968 (LWP 8697)]
[New Thread -1211204720 (LWP 8704)]
[Detaching after fork from child process 8705. (Try `set detach-on-fork off'.)]
[Thread -1211204720 (LWP 8704) exited]
seahorse nautilus module initialized
Initializing gnome-mount extension
[New Thread -1211204720 (LWP 8710)]
[New Thread -1221698672 (LWP 8711)]
[New Thread -1232188528 (LWP 8712)]
[New Thread -1242678384 (LWP 8713)]
[New Thread -1253168240 (LWP 8714)]
[New Thread -1263658096 (LWP 8715)]
[New Thread -1274147952 (LWP 8716)]
[New Thread -1284637808 (LWP 8717)]
[New Thread -1295127664 (LWP 8718)]
[Detaching after fork from child process 8720.]
[Thread -1211204720 (LWP 8710) exited]
[Thread -1221698672 (LWP 8711) exited]
[Detaching after fork from child process 8722.]
[Thread -1242678384 (LWP 8713) exited]
[Thread -1263658096 (LWP 8715) exited]
[Thread -1274147952 (LWP 8716) exited]

** (nautilus:8697): WARNING **: Didn't get any signs from mapping-daemon


(nautilus:8697): libgnomevfs-WARNING **: module '/usr/lib/gnome-vfs-2.0/modules/libmapping.so' returned a NULL handle
[Thread -1232188528 (LWP 8712) exited]
[Thread -1284637808 (LWP 8717) exited]
[Thread -1253168240 (LWP 8714) exited]
[New Thread -1253168240 (LWP 8724)]
[New Thread -1284637808 (LWP 8725)]
[New Thread -1232188528 (LWP 8726)]
[Thread -1295127664 (LWP 8718) exited]
[Thread -1253168240 (LWP 8724) exited]
[Thread -1284637808 (LWP 8725) exited]
[Thread -1232188528 (LWP 8726) exited]
[New Thread -1232188528 (LWP 8727)]
[New Thread -1253168240 (LWP 8728)]
** 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
** 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
** 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
** 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
** 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
** 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
** 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
** 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
** Message: drive = 0
** Message: volume = 0
[Thread -1253168240 (LWP 8728) exited]
[Thread -1232188528 (LWP 8727) exited]
[New Thread -1232188528 (LWP 8753)]
[Thread -1232188528 (LWP 8753) exited]
[New Thread -1232188528 (LWP 8754)]
[New Thread -1253168240 (LWP 8755)]
** 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
** 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
** 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
[Thread -1232188528 (LWP 8754) exited]
[Thread -1253168240 (LWP 8755) exited]
[New Thread -1253168240 (LWP 8799)]
[New Thread -1232188528 (LWP 8803)]
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = b21ddb00
** Message: volume = 9c610d0
** Message: drive = 981e970
** Message: volume = 0
[Thread -1253168240 (LWP 8799) exited]
[Thread -1232188528 (LWP 8803) exited]
[New Thread -1232188528 (LWP 8812)]
[Thread -1232188528 (LWP 8812) exited]
[New Thread -1232188528 (LWP 8813)]
[Thread -1232188528 (LWP 8813) exited]

Program received signal SIGSEGV, Segmentation fault.

+ Trace 136753

Thread NaN (LWP 8697)

#0 IA__gtk_widget_get_toplevel
at gtkwidget.c line 6670
#1 gtk_widget_get_screen_unchecked
at gtkwidget.c line 5967
#2 IA__gtk_widget_has_screen
at gtkwidget.c line 6040
#3 recompute_idle_func
at gtkentry.c line 3190
#4 gdk_threads_dispatch
at gdk.c line 470
#5 g_idle_dispatch
at gmain.c line 4096
#6 IA__g_main_context_dispatch
at gmain.c line 2061
#7 g_main_context_iterate
at gmain.c line 2694
#8 IA__g_main_loop_run
at gmain.c line 2898
#9 IA__gtk_main
at gtkmain.c line 1142
#10 main
at nautilus-main.c line 548

Comment 10 palfrey 2007-05-30 09:05:06 UTC

That's a much better trace. We can now confirm that this is a duplicate of Bug 406462. If you're running a version of gtk later than 2.10.9, can you please add a comment saying which version on Bug 406462. Thanks!

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