GNOME Bugzilla – Bug 110497
Nautilus crashes with Segmentation fault when closing xawtv.
Last modified: 2004-12-22 21:47:04 UTC
Package: nautilus Severity: critical Version: 2.2.1 Synopsis: Nautilus crashes with Segmentation fault when closing xawtv. Bugzilla-Product: nautilus Bugzilla-Component: Desktop BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: Steps to reproduce the problem: 1. 2. 3. Actual Results: Expected Results: How often does this happen? Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 1088008512 (LWP 4728)] [New Thread 1167306032 (LWP 4745)] [New Thread 1158913328 (LWP 4744)] [New Thread 1150520624 (LWP 4743)] [New Thread 1142127920 (LWP 4742)] [New Thread 1133735216 (LWP 4741)] [New Thread 1125342512 (LWP 4740)] [New Thread 1116949808 (LWP 4739)] [New Thread 1099664688 (LWP 4738)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...0xffffe002 in ?? ()
+ Trace 35820
Thread 1 (Thread 1088008512 (LWP 4728))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-04-10 17:45 ------- The original reporter (Istvan-Attila.Andras@gis.ericsson.se) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
I'm starting to suspect that this is a gtk+ problem--we're getting similar stack trace from many different packages. If you could find out any more about this bug (e.g. exact ways to trigger it that is easily reproducible) and add any of that info to bug 105745, it'd be greatly appreciated. *** This bug has been marked as a duplicate of 105745 ***