Bug 314173 – Nautilus crashes when I click a link

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 314173 - Nautilus crashes when I click a link


Summary:	Nautilus crashes when I click a link


Status:	RESOLVED NOTGNOME

Product:	nautilus
Classification:	Core
Component:	File and Folder Operations
Version:	2.11.x
Hardware:	Other Linux

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2005-08-22 15:11 UTC by Vidar Braut Haarr
Modified:	2005-08-23 14:16 UTC

See Also:
GNOME target:	---
GNOME version:	2.11/2.12

Description Vidar Braut Haarr 2005-08-22 15:11:24 UTC

Distribution/Version: Ubuntu

1. Create a link to a folder somewhere.
2. Click it.

Results: Nautilus crashes and restarts.

I have -dbg packages for nautilus, gtk, glib, gnomevfs and gnome-applets installed.

I've tried getting stack information with GDB, but I haven't been able to get
alot .. A kind soul helped me at freenode/gnome, and this is what I did and got:

1. > gdb /usr/bin/nautilus `pidof nautilus`
2. gdb> continue
3. Produce crash.
4. gdb> thread apply all bt [1]
5. gdb> continue
6. gdb> thread apply all bt [2]
7. gdb> continue
8. Nautilus shuts down and restarts.

1: Produced the following output:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1236534352 (LWP 11230)]
0xb644568b in ?? ()
(gdb) thread apply all bt

+ Trace 62587

Thread 5 (Thread -1236534352 (LWP 11230))

#0 __kernel_vsyscall
#1 __read_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 XWriteBitmapFile
from /usr/lib/libX11.so.6
#3 _X11TransRead
from /usr/lib/libX11.so.6
#4 _XRead
from /usr/lib/libX11.so.6
#5 _XReply
from /usr/lib/libX11.so.6
#6 XSync
from /usr/lib/libX11.so.6
#7 IA__gdk_flush
at gdkevents-x11.c line 2472
#8 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#9 <signal handler called>
#10 ??
#11 ??
#12 ??
#13 ??
#14 ??
#15 ??
#16 ??
#17 ??
#18 ??
#19 ??
#20 ??
#21 ??
#22 ??
#23 ??
#24 ??
#25 ??
#26 ??
#27 ??
#28 _dl_runtime_resolve
from /lib/ld-linux.so.2
#29 ??
#30 ??
#31 ??
#32 ??
#33 ??
#34 ??
#35 ??
#36 ??
#37 ??
#38 ??
#39 ??
#40 ??
#41 ??
#42 ??
#43 ??
#44 ??
#45 ??
#46 ??
#47 ??
#48 ??
#49 ??
#50 ??
#51 ??
#52 ??
#53 ??
#54 ??
#55 ??
#56 ??
#57 ??
#58 ??
#59 ??
#60 ??
#61 ??
#62 ??
#63 ??
#64 ??
#65 ??
#66 ??
#67 ??
#68 ??
#69 ??
#70 ??
#71 ??
#72 ??
#73 ??
#74 ??
#75 ??
#76 ??
#77 ??
#78 ??
#79 ??
#80 ??
#81 ??
#82 ??
#83 ??
#84 ??
#85 ??
#86 ??
#87 ??
#88 ??
#89 ??
#90 ??
#91 ??
#92 ??
#93 ??
#94 ??
#95 ??
#96 ??
#97 ??
#98 ??
#99 ??
#100 ??
#101 ??
#102 ??
#103 ??
#104 ??
#105 ??
#106 ??
#107 ??
#108 ??
#109 ??
#110 ??
#111 ??
#112 ??
#113 gnome_vfs_read_cancellable
at gnome-vfs-cancellable-ops.c line 133
#0 __kernel_vsyscall

Comment 1 Christian Kirbach 2005-08-23 12:48:47 UTC

Thanks for the bug report. Unfortunately, that stack trace is not very useful in 
determining the cause of the crash. Can you get us one with debugging symbols? 
Please see http://live.gnome.org/GettingTraces for more information on how to do 
so.

Comment 2 Vidar Braut Haarr 2005-08-23 12:59:40 UTC

Those are the steps I followed. If it would help, I'd meet with you on IRC where
you could instruct me as to how to get better stack traces ?

Comment 3 Christian Kirbach 2005-08-23 13:48:09 UTC

drop by in irc channel #bugs (and/or #gnome) on irc.gnome.org and ask 
_patiently_. people can usually assist.

Comment 4 Vidar Braut Haarr 2005-08-23 14:16:45 UTC

With the help of seb128 and vuntz on #bugs, we determined this to be a libswfdec
bug.

Resolving NOTGNOME.