Bug 461952 – 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 461952 - crash in File Browser:


Summary:	crash in File Browser:


Status:	RESOLVED DUPLICATE of bug 449488

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-07-30 21:08 UTC by kredba
Modified:	2007-09-11 13:56 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description kredba 2007-07-30 21:08:51 UTC

Version: 2.18.3

What were you doing when the application crashed?



Distribution: Unknown
Gnome Release: 2.18.3 2007-07-28 (David Kredba, kredba@math.cas.cz)
BugBuddy Version: 2.18.1

System: Linux 2.6.21.5-LFS-1 #1 SMP Fri Jul 6 23:40:28 CEST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 26066944 vsize: 26066944 resident: 10182656 share: 7684096 rss: 10182656 rss_rlim: 4294967295
CPU usage: start_time: 1185829584 rtime: 28 utime: 25 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome-2.18.3/bin/nautilus'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1228011840 (LWP 1502)]
0xb7eee410 in __kernel_vsyscall ()

+ Trace 151694

Thread 1 (Thread -1228011840 (LWP 1502))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 libgnomeui_segv_handle
at gnome-ui-init.c line 872
#3 <signal handler called>
#4 PyErr_Restore
at Python/errors.c line 47
#5 PyErr_SetObject
at Python/errors.c line 57
#6 PyErr_SetString
at Python/errors.c line 70
#7 sys_getframe
at Python/sysmodule.c line 655
#8 PyCFunction_Call
at Objects/methodobject.c line 108
#9 PyEval_EvalFrameEx
at Python/ceval.c line 3564
#10 PyEval_EvalCodeEx
at Python/ceval.c line 2831
#11 function_call
at Objects/funcobject.c line 517
#12 PyObject_Call
at Objects/abstract.c line 1860
#13 call_function_tail
at Objects/abstract.c line 1891
#14 PyObject_CallFunction
at Objects/abstract.c line 1915
#15 PyErr_WarnEx
#16 _log_func
#17 IA__g_logv
at gmessages.c line 474
#18 IA__g_log
at gmessages.c line 517
#19 IA__g_return_if_fail_warning
#20 IA__g_object_new
at gobject.c line 792
#21 nautilus_module_add_type
at nautilus-module.c line 253
#22 nautilus_module_init
at nautilus-module.c line 160
#23 nautilus_application_startup
at nautilus-application.c line 400
#24 main
at nautilus-main.c line 533
#0 __kernel_vsyscall

Comment 1 André Klapper 2007-09-11 13:56:00 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 449488 ***