GNOME Bugzilla – Bug 355254
Crashes when changing screen resolution
Last modified: 2007-04-22 20:23:24 UTC
Version: 2.16.0 What were you doing when the application crashed? Changing screen resolution!! Distribution: Gentoo Base System version 1.12.4 Gnome Release: 2.16.0 2006-09-10 (Gentoo) BugBuddy Version: 2.16.0 Memory status: size: 137220096 vsize: 0 resident: 137220096 share: 0 rss: 38014976 rss_rlim: 0 CPU usage: start_time: 1157883010 rtime: 0 utime: 543 stime: 0 cutime:531 cstime: 0 timeout: 12 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/totem' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1227819344 (LWP 21390)] [New Thread -1331078240 (LWP 21397)] [New Thread -1312674912 (LWP 21396)] [New Thread -1304282208 (LWP 21395)] [New Thread -1294001248 (LWP 21394)] [New Thread -1281508448 (LWP 21393)] [New Thread -1272833120 (LWP 21392)] [New Thread -1257940064 (LWP 21391)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 72035
Thread 1 (Thread -1227819344 (LWP 21390))
How did you change the screen resolution?
I change the screen resolution while totem playing some realmedia file, and totem report the Segmentation fault. I use gcc 4.1.1 compile totem and xine-libs.
Again, which tool did you use to change the resolution?
gnome-display-properties
*** Bug 356365 has been marked as a duplicate of this bug. ***
Can't reproduce using GStreamer.
Should be fixed by this commit to xine-lib HEAD. Reopen if not. RCS file: /cvsroot/xine/xine-lib/src/post/goom/xine_goom.c,v Working file: xine_goom.c <snip> ---------------------------- revision 1.63 date: 2006/10/23 21:13:44; author: hadess; state: Exp; lines: +12 -1 - unregister configuration callbacks when disposing of the class should fix http://bugzilla.gnome.org/show_bug.cgi?id=355254
*** Bug 364759 has been marked as a duplicate of this bug. ***
*** Bug 426114 has been marked as a duplicate of this bug. ***
*** Bug 430966 has been marked as a duplicate of this bug. ***