Bug 504965 – 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 504965 - 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:	2007-12-22 01:30 UTC by xAD
Modified:	2007-12-23 18:47 UTC

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

Description xAD 2007-12-22 01:30:09 UTC

Version: 2.18.3

What were you doing when the application crashed?



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

System: Linux 2.6.23.8 #1 PREEMPT Sat Nov 17 05:33:33 CET 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome-icon-theme-2.18.0

Memory status: size: 86454272 vsize: 86454272 resident: 28999680 share: 17203200 rss: 28999680 rss_rlim: 4294967295
CPU usage: start_time: 1198286281 rtime: 1140 utime: 1063 stime: 77 cutime:0 cstime: 1 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 0xb6ce76b0 (LWP 4785)]
0xb75eb321 in waitpid () from /lib/libpthread.so.0

+ Trace 182590

Thread 1 (Thread 0xb6ce76b0 (LWP 4785))

#0 waitpid
from /lib/libpthread.so.0
#1 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#2 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#3 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#4 <signal handler called>
#5 strcmp
from /lib/libc.so.6
#6 changed_group_callback
at fm-properties-window.c line 1646
#7 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#8 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#9 ??
from /usr/lib/libgobject-2.0.so.0
#10 ??
#11 ??
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors (8 sec old) ---------------------
:images/transmitting-high-signal.png
|idle-high-signal.png
 wlan0: 6732845   13007    0    0    0     0          0         0  3238460   17561    0    0    0     0       0          0
not rec
:images/idle-high-signal.png
|transmitting-high-signal.png
 wlan0: 6733414   13012    0    0    0     0          0         0  3239336   17567    0    0    0     0       0          0
:images/transmitting-high-signal.png
|both-high-signal.png
 wlan0: 6734041   13014    0    0    0     0          0         0  3240227   17571    0    0    0     0       0          0
not rec
 wlan0: 6734415   13016    0    0    0     0          0         0  3240714   17574    0    0    0   xscreensaver: 0: unrecognised ClientMessage "_NET_WM_STATE" received
xscreensaver: 0: for window 0xc02417 (nautilus / Nautilus)
xscreensaver: -1: unrecognised ClientMessage "_NET_WM_STATE" received
xscreensaver: -1: for window 0xc02417 ((null) / (null))
--------------------------------------------------

Comment 1 Cosimo Cecchi 2007-12-23 18:47:44 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 ***