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 391924 - crash in Screen Resolution:
crash in Screen Resolution:
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-01-02 16:09 UTC by surfraz
Modified: 2007-01-02 18:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description surfraz 2007-01-02 16:09:29 UTC 
Version: 2.16.1

What were you doing when the application crashed?



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

Memory status: size: 70037504 vsize: 0 resident: 70037504 share: 0 rss: 9994240 rss_rlim: 0
CPU usage: start_time: 1167754153 rtime: 0 utime: 14 stime: 0 cutime:14 cstime: 0 timeout: 0 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 -1225663888 (LWP 5827)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 98741

Thread 1 (Thread -1225663888 (LWP 5827))

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


Luca Cavalli





          2007-01-02 18:16:37 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 ***