Bug 530749 – crash in Computer: saving a file created wi...

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 530749 - crash in Computer: saving a file created wi...


Summary:	crash in Computer: saving a file created wi...


Status:	RESOLVED DUPLICATE of bug 483884

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-04-30 15:42 UTC by sebastien.zola
Modified:	2008-04-30 18:49 UTC

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

Description sebastien.zola 2008-04-30 15:42:58 UTC

Version: 2.20.0

What were you doing when the application crashed?
saving a file created with GIMP


Distribution: Slackware Slackware 12.0.0
Gnome Release: 2.20.0 2007-10-14 (GNOME.Org)
BugBuddy Version: 2.20.1

System: Linux 2.6.21.5-smp #4 SMP Mon Feb 11 17:13:56 CST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome

Memory status: size: 120504320 vsize: 120504320 resident: 38453248 share: 12488704 rss: 38453248 rss_rlim: 4294967295
CPU usage: start_time: 1209470740 rtime: 11679 utime: 10721 stime: 958 cutime:1 cstime: 21 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 -1228097328 (LWP 19513)]
0xb70c7b01 in ?? () from /lib/libpthread.so.0

+ Trace 196531

Thread 1 (Thread -1228097328 (LWP 19513))

#0 ??
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 run_bug_buddy
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#4 check_if_gdb
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 google_breakpad::ExceptionHandler::InternalWriteMinidump
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#6 google_breakpad::ExceptionHandler::HandleException
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#7 <signal handler called>
#8 nautilus_icon_factory_possibly_free_cached_icon
#9 g_hash_table_foreach_remove_or_steal
from /usr/lib/libglib-2.0.so.0
#10 nautilus_icon_factory_sweep
#11 g_timeout_dispatch
from /usr/lib/libglib-2.0.so.0
#12 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#13 g_main_context_iterate
from /usr/lib/libglib-2.0.so.0
#14 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#15 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#16 main
#0 ??
from /lib/libpthread.so.0



----------- .xsession-errors (153256 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Gianluca Borello 2008-04-30 18:49:37 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 483884 ***