Bug 532942 – crash in File Browser:

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 532942 - crash in File Browser:


Summary:	crash in File Browser:


Status:	RESOLVED DUPLICATE of bug 522534

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-05-13 11:40 UTC by ridu_chin
Modified:	2008-05-13 11:58 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description ridu_chin 2008-05-13 11:40:02 UTC

Version: 2.20.0

What were you doing when the application crashed?
 


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-486 #1 Thu Mar 27 17:00:17 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: gommapiumalooks
Icon Theme: Kamel

Memory status: size: 74616832 vsize: 74616832 resident: 27222016 share: 15798272 rss: 27222016 rss_rlim: 4294967295
CPU usage: start_time: 1210676039 rtime: 799 utime: 407 stime: 392 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 0xb6bfc720 (LWP 2752)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 197618

Thread 1 (Thread 0xb6bfc720 (LWP 2752))

#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 ??
#7 ??
#8 ??
#9 ??
#10 ??
from /usr/lib/libglib-2.0.so.0
#11 ??
#12 ??
#13 ??
#14 ??
from /usr/lib/libglib-2.0.so.0
#15 ??
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
connection_message_func(): Callback
CALLBACK: full-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
** (nautilus:2752): WARNING **: Hit unhandled case 24 (Operación no permitida) in fm_report_error_loading_directory
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
/home/javi/.themes/gommapiumalooks/gtk-2.0/gtkrc:234: error: invalid string constant "clearlooks-panelbg", expected valid string constant
--------------------------------------------------

Comment 1 Gianluca Borello 2008-05-13 11:58:11 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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