Segfault with bad atom error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gpointing-device-settings (Debian) |
Fix Released
|
Unknown
|
|||
gpointing-device-settings (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gpointing-
Sorry for the poor backtrace, I can't find the appropriate debug packages :/
Starting program: /usr/bin/
[Thread debugging using libthread_db enabled]
[New Thread 0x7fffeee77710 (LWP 3636)]
An X error occurred. The error was BadAtom (invalid Atom parameter).
An X error occurred. The error was BadAtom (invalid Atom parameter).
An X error occurred. The error was BadAtom (invalid Atom parameter).
An X error occurred. The error was BadAtom (invalid Atom parameter).
An X error occurred. The error was BadAtom (invalid Atom parameter).
An X error occurred. The error was BadAtom (invalid Atom parameter).
An X error occurred. The error was BadAtom (invalid Atom parameter).
Program received signal SIGSEGV, Segmentation fault.
0x00007fffef2dd2f5 in ?? ()
from /usr/lib/
(gdb) bt
#0 0x00007fffef2dd2f5 in ?? ()
from /usr/lib/
#1 0x0000000000401c19 in ?? ()
#2 0x0000000000402141 in ?? ()
#3 0x00007ffff480dd8e in __libc_start_main (main=<value optimised out>,
argc=<value optimised out>, ubp_av=<value optimised out>,
init=<value optimised out>, fini=<value optimised out>,
rtld_
at libc-start.c:226
#4 0x0000000000401b09 in ?? ()
#5 0x00007fffffffe278 in ?? ()
#6 0x000000000000001c in ?? ()
#7 0x0000000000000001 in ?? ()
#8 0x00007fffffffe544 in ?? ()
#9 0x0000000000000000 in ?? ()
tags: | added: patch |
Changed in gpointing-device-settings (Debian): | |
status: | Unknown → Fix Released |
Forgot to mention, this is from the current maverick release as of 27/9/2010