closing
** Changed in: skippy (Ubuntu)
Status: Incomplete => Fix Released
--
Changing keysym causes segfault
https://bugs.launchpad.net/bugs/30129
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu
this particular bug appears to be OK on feisty.
--
Changing keysym causes segfault
https://launchpad.net/bugs/30129
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Cannot reproduce on x86, with 'nvidia' and 0.5.1rc1-6 on Feisty. I think
it's functioning correctly and at any rate, it doesn't crash and I get
no errors in 'dmesg'. (I'm not implying though that it's not a problem
for you )
--
Changing keysym causes segfault
https://launchpad.net/bugs/30129
--
--the rest of the file--
(gdb) backtrace
No stack.
(gdb) thread apply all backtrace
(gdb) q
--
Changing keysym causes segfault
https://launchpad.net/bugs/30129
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
It still fails, I have created a backtrace (which seems to provide
nothing useful) as described on the wiki page.
--
Changing keysym causes segfault
https://launchpad.net/bugs/30129
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Is this still a problem with dapper's release or edgy? If yes, can you
please get a backtrace (see http://wiki.ubuntu.com/DebuggingProgramCrash
). Thanks in advance.
** Changed in: skippy (Ubuntu)
Status: Unconfirmed => Needs Info
--
Changing keysym causes segfault
https://launchpad.net/b
