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 351069 - crash on Mouse
crash on Mouse
Status: RESOLVED DUPLICATE of bug 322514
Product: gnome-control-center
Classification: Core
Component: Mouse
2.15.x
Other All
: High critical
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-08-12 18:22 UTC by thanate
Modified: 2006-08-13 08:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description thanate 2006-08-12 18:22:12 UTC
What were you doing when the application crashed?
trying to start mouse preference


Distribution: Debian testing/unstable
Gnome Release: 2.15.91 2006-08-11 (GARNOME)
BugBuddy Version: 2.15.90

Memory status: size: 22642688 vsize: 0 resident: 22642688 share: 0 rss: 11649024 rss_rlim: 0
CPU usage: start_time: 1155406886 rtime: 0 utime: 45 stime: 0 cutime:38 cstime: 0 timeout: 7 it_real_value: 0 frequency: 0

Backtrace was generated from '/home/boat/garnome/bin/gnome-mouse-properties'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1226553664 (LWP 7311)]
0xb706a20e in __waitpid_nocancel () from /lib/tls/libpthread.so.0

Thread 1 (Thread -1226553664 (LWP 7311))

  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 867
  • #2 <signal handler called>
  • #3 IA__g_logv
  • #4 IA__g_log
    at gmessages.c line 517
  • #5 IA__g_return_if_fail_warning
  • #6 cursor_theme_changed
    at gnome-mouse-properties.c line 484
  • #7 main
    at gnome-mouse-properties.c line 956
  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0

Comment 1 Fabio Bonelli 2006-08-13 08:18:18 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 322514 ***