Bug 374522 – crash in Screen Resolution: Fiddling with X on TV-ou...

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 374522 - crash in Screen Resolution: Fiddling with X on TV-ou...


Summary:	crash in Screen Resolution: Fiddling with X on TV-ou...


Status:	RESOLVED DUPLICATE of bug 356520

Product:	gnome-control-center
Classification:	Core
Component:	Display
Version:	2.16.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-11-13 00:36 UTC by waisted
Modified:	2006-11-13 10:34 UTC

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

Description waisted 2006-11-13 00:36:26 UTC

Version: 2.16.1

What were you doing when the application crashed?
Fiddling with X on TV-out (PVR-350). The desktop on my PC-monitor looks good, but on the TV its B/W (probably due to some PAL-settings). Im running IVTV 7.1 and a strange ivtvdev_drv from http://www.hellion.org.uk/ivtv/debian/ so its probably not a crash caused by the resolution-settings app but a combination of multiple screens with different resolutions and trying to use this app. ...i think ;)


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 31158272 vsize: 0 resident: 31158272 share: 0 rss: 9535488 rss_rlim: 0
CPU usage: start_time: 1163378029 rtime: 0 utime: 18 stime: 0 cutime:17 cstime: 0 timeout: 1 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gnome-display-properties'

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

+ Trace 85946

Thread 1 (Thread -1225045392 (LWP 5083))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 gtk_tree_model_get_valist
from /usr/lib/libgtk-x11-2.0.so.0
#5 gtk_tree_model_get
from /usr/lib/libgtk-x11-2.0.so.0
#6 _start
#0 __kernel_vsyscall

Comment 1 André Klapper 2006-11-13 10:34:59 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 356520 ***