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 485997 - crash in Open Folder:
crash in Open Folder:
Status: RESOLVED DUPLICATE of bug 508751
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 486029 486030 486059 486060 486061 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-10-12 11:31 UTC by tom quas
Modified: 2008-08-26 11:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description tom quas 2007-10-12 11:31:36 UTC
Version: 2.20.0

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.20.0 2007-09-21 (Debian)
BugBuddy Version: 2.20.0

System: Linux 2.6.21 #1 PREEMPT Fri Jul 13 14:34:28 CEST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 76775424 vsize: 76775424 resident: 23277568 share: 17145856 rss: 23277568 rss_rlim: 4294967295
CPU usage: start_time: 1192167182 rtime: 234 utime: 203 stime: 31 cutime:6 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 0xb6b9e6c0 (LWP 6847)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6b9e6c0 (LWP 6847))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 _gdk_keymap_key_is_modifier
    from /usr/lib/libgdk-x11-2.0.so.0
  • #7 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #8 ??
  • #9 ??
  • #10 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (6966 sec old) ---------------------
(gnome-terminal:6855): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
Window manager warning: Received request to set _NET_FRAME_EXTENTS on 0x520066d which is on a screen we are not managing
/usr/lib/bug-buddy/gecko: No such file or directory.
/usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/libpng12.so.0/libpng12.so.0: no version information available (required by /usr/lib/libcairo.so.2)
[YourKit Java Profiler 7.0.2] Using JVMTI (1.6.0_02-b05;Sun Microsystems Inc.;mixed mode, sharing;Linux;32 bit JVM)
[YourKit Java Profiler 7.0.2] Profiler agent is listening on port 10001...
[YourKit Java Profiler 7.0.2] *** HINT ***: To get profiling results, connect to the application from the profiler UI
Window manager warning: Log level 16: Failed to set text from markup due to error parsing markup: Error on line 1 char 145: Element 'markup' was closed, but the currently open element is 'b'
Window manager warning: Received request to set _NET_FRAME_EXTENTS on 0x3000379 which is on a screen we are not managing
Window manager warning: Received request to set _NET_FRAME_EXTENTS on 0x300037c which is on a screen we are not managing
Window manager warning: Received request to set _NET_FRAME_EXTENTS on 0x3000426 which is on a screen we are not managing
[YourKit Java Profiler 7.0.2] Using JVMTI (1.6.0_02-b05;Sun Microsystems Inc.;mixed mode, sharing;Linux;32 bit JVM)
[YourKit Java Profiler 7.0.2] Profiler agent is listening on port 10001...
[YourKit Java Profiler 7.0.2] *** HINT ***: To get profiling results, connect to the application from the profiler UI
--------------------------------------------------
Comment 1 Christian Kirbach 2007-10-13 00:27:16 UTC
*** Bug 486060 has been marked as a duplicate of this bug. ***
Comment 2 Christian Kirbach 2007-10-13 00:27:23 UTC
*** Bug 486029 has been marked as a duplicate of this bug. ***
Comment 3 Christian Kirbach 2007-10-13 00:27:28 UTC
*** Bug 486030 has been marked as a duplicate of this bug. ***
Comment 4 Christian Kirbach 2007-10-13 00:27:34 UTC
*** Bug 486059 has been marked as a duplicate of this bug. ***
Comment 5 Christian Kirbach 2007-10-13 00:27:39 UTC
*** Bug 486061 has been marked as a duplicate of this bug. ***
Comment 6 Christian Kirbach 2007-10-13 00:27:59 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 7 Cosimo Cecchi 2008-05-31 11:05:00 UTC
I believe this could be a duplicate of bug 508751.
Comment 8 Cosimo Cecchi 2008-08-26 11:07:19 UTC

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