~/.session-errors includes no interesting information...

OK, this was the first time I did a backtrace but it seems not to work
(the appropriate gdbsym package was installed before):

gdb gnome-screensaver 2>&1 | tee gdb-gnome-screensaver.txt
GNU gdb 6.4.90-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...Using host libthread_db library 
"/lib/tls/i686/cmov/libthread_db.so.1".

(gdb) handle SIG33 pass nostop noprint
Signal        Stop      Print   Pass to program Description
SIG33         No        No      Yes             Real-time event 33
(gdb) set pagination 0
(gdb) break gdk_x_error
Function "gdk_x_error" not defined.
Make breakpoint pending on future shared library load? (y or [n]) 
(gdb) run
Starting program: /usr/bin/gnome-screensaver 
[Thread debugging using libthread_db enabled]
[New Thread -1222248784 (LWP 16663)]

Program exited normally.
(gdb) The program 'gnome-screensaver' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 4596 error_code 2 request_code 135 minor_code 15)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
backtrace
No stack.
(gdb)

-- 
Lock Screen not working anymore
https://launchpad.net/bugs/68123

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to