GNOME Bugzilla – Bug 130779
crash after changing video resolution
Last modified: 2004-12-22 21:47:04 UTC
Package: acme Severity: normal Version: 2.2.1 Synopsis: crash after changing video resolution Bugzilla-Product: acme Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: After switching video cards, experimenting with resolution settings. Crash after restarting X. Steps to reproduce the problem: 1. it seemed random 2. 3. Actual Results: Expected Results: How often does this happen? seen once after several changes of resolution 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 1087985344 (LWP 5777)] [New Thread 1167313712 (LWP 5879)] [New Thread 1158921008 (LWP 5876)] [New Thread 1150528304 (LWP 5875)] [New Thread 1142135600 (LWP 5874)] [New Thread 1133742896 (LWP 5871)] [New Thread 1125350192 (LWP 5868)] [New Thread 1116957488 (LWP 5867)] [New Thread 1099873072 (LWP 5866)] (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)...0xffffe002 in ?? ()
+ Trace 43066
Thread 8 (Thread 1116957488 (LWP 5867))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-01-07 09:37 ------- The original reporter (Robert.T.Neece@nasa.gov) 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, hadess@hadess.net.
The stack trace looks corrupted, but this may be a duplicate of bug 111147, the FAMCLOSE() related crash. Reporter, if you continue to experience this crash, can you try to get a better stack trace. See http://bugzilla.gnome.org/getting-traces.cgi for more information. Thanks
Yeah, it's a dup of bug 111147.
*** This bug has been marked as a duplicate of 111147 ***