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 432459 - crash in Screen Resolution: System->Preferences->Scr...
crash in Screen Resolution: System->Preferences->Scr...
Status: RESOLVED DUPLICATE of bug 356520
Product: gnome-control-center
Classification: Core
Component: Display
2.16.x
Other All
: High critical
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-04-23 02:33 UTC by npeelman
Modified: 2007-04-23 16:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description npeelman 2007-04-23 02:33:17 UTC 
Version: 2.16.1

What were you doing when the application crashed?
System->Preferences->Screen Resolution on multi-monitor system.


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

Memory status: size: 34398208 vsize: 0 resident: 34398208 share: 0 rss: 10178560 rss_rlim: 0
CPU usage: start_time: 1177287923 rtime: 0 utime: 30 stime: 0 cutime:28 cstime: 0 timeout: 2 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 -1224562064 (LWP 5756)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 129895

Thread 1 (Thread -1224562064 (LWP 5756))

  • #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


Jens Granseuer





          2007-04-23 16:28:18 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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