Bug 510507 – crash in Open Folder:

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 510507 - crash in Open Folder:


Summary:	crash in Open Folder:


Status:	RESOLVED DUPLICATE of bug 355018

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-01-18 22:44 UTC by thinbegin
Modified:	2008-01-19 01:23 UTC

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

Description thinbegin 2008-01-18 22:44:53 UTC

Version: 2.18.3

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.20.2 2007-11-29 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-486 #1 Mon Nov 12 07:53:08 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Amaranth
Icon Theme: Amaranth

Memory status: size: 77598720 vsize: 77598720 resident: 28622848 share: 16392192 rss: 28622848 rss_rlim: 4294967295
CPU usage: start_time: 1200672298 rtime: 3026 utime: 2519 stime: 507 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 0xb6de06b0 (LWP 3432)]
[New Thread 0xb4d23b90 (LWP 5214)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 185892

Thread 1 (Thread 0xb6de06b0 (LWP 3432))

#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 strcmp
from /lib/i686/cmov/libc.so.6
#7 ??
#8 ??
#0 __kernel_vsyscall



----------- .xsession-errors (13299 sec old) ---------------------
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo contex
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-01-19 01:23:24 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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