Bug 544887 – crash in File Browser: start

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


Summary:	crash in File Browser: start


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-07-26 20:20 UTC by 747
Modified:	2008-07-27 09:55 UTC

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

Description 747 2008-07-26 20:20:35 UTC

Version: 2.20.0

What were you doing when the application crashed?
start


Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-2-686 #1 SMP Fri Jun 27 03:23:20 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Industrial
Icon Theme: SphereCrystal

Memory status: size: 77672448 vsize: 77672448 resident: 25931776 share: 15503360 rss: 25931776 rss_rlim: 4294967295
CPU usage: start_time: 1217103487 rtime: 315 utime: 301 stime: 14 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6b70710 (LWP 3113)]
(no debugging symbols found)
0xb7fb7424 in __kernel_vsyscall ()

+ Trace 203862

Thread 1 (Thread 0xb6b70710 (LWP 3113))

#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 ---------------------
CALLBACK: full-authentication!!!
** (nautilus:3113): WARNING **: Hit unhandled case 31 (Anulowano operację) in fm_report_error_loading_directory
** (nautilus:3113): WARNING **: Hit unhandled case 46 (Przekroczono czas oczekiwania) in fm_report_error_loading_directory
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
** (nautilus:3113): WARNING **: Hit unhandled case 38 (Usługa nie jest dostępna) in fm_report_error_loading_directory
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-07-27 09:55:33 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 522534 ***