Bug 350685 – crash on Computer

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 350685 - crash on Computer


Summary:	crash on Computer


Status:	RESOLVED FIXED

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

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

URL:
Whiteboard:

Duplicates:	350686 351162 351608 351819 352652 (view as bug list)
Depends on:
Blocks:

Reported:	2006-08-10 03:08 UTC by Rouslan Solomakhin (Руслан Соломахин)
Modified:	2006-08-24 09:38 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Attachments
Patch To Fix The Bug (420 bytes, patch) 2006-08-15 21:22 UTC, Rouslan Solomakhin (Руслан Соломахин)	none	Details \| Review

Description Rouslan Solomakhin (Руслан Соломахин) 2006-08-10 03:08:13 UTC

What were you doing when the application crashed?
I was opening file /home/smoketester/Examples/kubuntu-leaflet.png.


Distribution: Ubuntu 6.06 (dapper)
Gnome Release: 2.15.91 2006-08-08 (JHBuild)
BugBuddy Version: 2.15.90

Memory status: size: 47652864 vsize: 0 resident: 47652864 share: 0 rss: 17838080 rss_rlim: 0
CPU usage: start_time: 1155179128 rtime: 0 utime: 292 stime: 0 cutime:262 cstime: 0 timeout: 30 it_real_value: 0 frequency: 93

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1224657216 (LWP 5290)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 70165

Thread 1 (Thread -1224657216 (LWP 5290))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 libgnomeui_segv_handle
at gnome-ui-init.c line 867
#3 <signal handler called>
#4 free
from /lib/tls/i686/cmov/libc.so.6
#5 IA__g_free
at gmem.c line 187
#6 nautilus_recent_add_file
at nautilus-recent.c line 76
#7 activate_callback
at fm-directory-view.c line 8464
#8 file_list_file_ready_callback
at nautilus-file.c line 5949
#9 ready_callback_call
at nautilus-directory-async.c line 1237
#10 nautilus_directory_async_state_changed
at nautilus-directory-async.c line 1849
#11 nautilus_directory_call_when_ready_internal
at nautilus-directory-async.c line 1319
#12 vfs_file_call_when_ready
at nautilus-vfs-file.c line 66
#13 nautilus_file_call_when_ready
at nautilus-file.c line 5548
#14 nautilus_file_list_call_when_ready
at nautilus-file.c line 5982
#15 fm_directory_view_activate_files
at fm-directory-view.c line 8735
#16 icon_container_activate_callback
at fm-icon-view.c line 1689
#17 IA__g_cclosure_marshal_VOID__POINTER
at gmarshal.c line 601
#18 IA__g_closure_invoke
at gclosure.c line 490
#19 signal_emit_unlocked_R
at gsignal.c line 2438
#20 IA__g_signal_emit_valist
at gsignal.c line 2197
#21 IA__g_signal_emit
at gsignal.c line 2241
#22 activate_selected_items
at nautilus-icon-container.c line 5353
#23 item_event_callback
at nautilus-icon-container.c line 4996
#24 eel_marshal_BOOLEAN__BOXED
at eel-marshal.c line 82
#25 IA__g_closure_invoke
at gclosure.c line 490
#26 signal_emit_unlocked_R
at gsignal.c line 2438
#27 IA__g_signal_emit_valist
at gsignal.c line 2207
#28 IA__g_signal_emit
at gsignal.c line 2241
#29 emit_event
at eel-canvas.c line 2521
#30 button_press_event
at nautilus-icon-container.c line 3199
#31 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 83
#32 g_type_class_meta_marshal
at gclosure.c line 567
#33 IA__g_closure_invoke
at gclosure.c line 490
#34 signal_emit_unlocked_R
at gsignal.c line 2476
#35 IA__g_signal_emit_valist
at gsignal.c line 2207
#36 IA__g_signal_emit
at gsignal.c line 2241
#37 gtk_widget_event_internal
at gtkwidget.c line 3901
#38 IA__gtk_propagate_event
at gtkmain.c line 2187
#39 IA__gtk_main_do_event
at gtkmain.c line 1421
#40 gdk_event_dispatch
at gdkevents-x11.c line 2320
#41 IA__g_main_context_dispatch
at gmain.c line 2043
#42 g_main_context_iterate
at gmain.c line 2675
#43 IA__g_main_loop_run
at gmain.c line 2879
#44 IA__gtk_main
at gtkmain.c line 1000
#45 main
at nautilus-main.c line 366
#0 __kernel_vsyscall

Comment 1 Kjartan Maraas 2006-08-10 11:51:20 UTC

*** Bug 350686 has been marked as a duplicate of this bug. ***

Comment 2 Christian Kirbach 2006-08-10 14:45:49 UTC

detailed and unique trace

Comment 3 Christian Kirbach 2006-08-13 17:49:19 UTC

*** Bug 351162 has been marked as a duplicate of this bug. ***

Comment 4 Rouslan Solomakhin (Руслан Соломахин) 2006-08-15 17:02:53 UTC

I am willing to do some manual work to get rid of this bug, if someone provides me guidiance on gdb. Thanks!

Comment 5 Rouslan Solomakhin (Руслан Соломахин) 2006-08-15 17:06:53 UTC

Starting nautilus from command line outputs:

(nautilus:14906): libgnomevfs-WARNING **: Failed to activate daemon: The name org.gnome.GnomeVFS.Daemon was not provided by any .service files

Comment 6 Rouslan Solomakhin (Руслан Соломахин) 2006-08-15 17:13:53 UTC

(In reply to comment #5)

"ln -s <smoketesting-prefix>/share/dbus-1/services/gnome-vfs-daemon.service /usr/share/dbus-1/services/gnome-vfs-daemon.service" fixes the libgnomevfs-WARNING, but the crash is still reproducable.

Comment 7 Rouslan Solomakhin (Руслан Соломахин) 2006-08-15 21:22:10 UTC

Created attachment 70983 [details] [review]
Patch To Fix The Bug

Segfault occurs because of the call "g_free(recent_data.app_exec)", where "recent_data.app_exec" was being assigned a literal string value. The fix works by allocating a new string in memory.

Comment 8 Baptiste Mille-Mathias 2006-08-16 10:53:24 UTC

*** Bug 351608 has been marked as a duplicate of this bug. ***

Comment 9 Alexander Larsson 2006-08-17 10:11:07 UTC

Commited. Thanks.

Comment 10 Priit Laes (IRC: plaes) 2006-08-18 06:10:59 UTC

*** Bug 351819 has been marked as a duplicate of this bug. ***

Comment 11 Baptiste Mille-Mathias 2006-08-24 09:38:29 UTC

*** Bug 352652 has been marked as a duplicate of this bug. ***