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 495569 - crash in Open Folder: I tried to open a folder...
crash in Open Folder: I tried to open a folder...
Status: RESOLVED DUPLICATE of bug 440988
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-10 12:40 UTC by rslemos
Modified: 2007-11-15 08:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Attachments
Stacktrace with debugging symbols (8.26 KB, text/plain)
2007-11-14 23:43 UTC, rslemos
Details

Description rslemos 2007-11-10 12:40:35 UTC
Version: 2.18.3

What were you doing when the application crashed?
I tried to open a folder with icons (/usr/share/icons/Nuovo).


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Industrial
Icon Theme: Nuovo

Memory status: size: 74973184 vsize: 74973184 resident: 25952256 share: 13684736 rss: 25952256 rss_rlim: 4294967295
CPU usage: start_time: 1194698379 rtime: 124 utime: 116 stime: 8 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6e1c6b0 (LWP 21250)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6e1c6b0 (LWP 21250))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 ??
  • #5 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
** 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-11-13 12:07:34 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 rslemos 2007-11-14 23:43:28 UTC
Created attachment 99119 [details]
Stacktrace with debugging symbols

I installed the following Debian packages:

libglib2.0-0-dbg (2.14.1-5)
libgnomeui-0-dbg (2.18.1-2)
libgnomevfs2-0-dbg (1:2.20.0-3)
libgtk2.0-0-dbg (2.12.1-1)
libpango1.0-0-dbg (1.18.3-1)
nautilus-dbg (2.18.3-3)

After a reboot, I tried again to view the properties of a single file.
Comment 3 rslemos 2007-11-15 00:04:18 UTC
Comment on attachment 99119 [details]
Stacktrace with debugging symbols

Sorry. Wrong bug report. I should be directed to 440988 instead. Really really sorry.
Comment 4 André Klapper 2007-11-15 08:59:24 UTC
yepp, this is a duplicate of bug 440988. no need to be sorry though :)
Comment 5 André Klapper 2007-11-15 08:59:35 UTC

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