mouse and keyboard settings crashed when clicking close (without any changes done)

Bug #759123 reported by Terje Andersen
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lxinput (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: lxinput

opened it via the launcher menu, then pressed close - it disappeared and the crash-dialog came. No changes was made - I just realized I had opened the wrong settings program, therefore clicked close.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: lxinput 0.3.0-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
Date: Tue Apr 12 21:36:55 2011
ExecutablePath: /usr/bin/lxinput
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202)
ProcCmdline: lxinput
ProcEnviron:
 LANGUAGE=nb_NO:nb:en_GB:en
 LANG=nb_NO.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f519b618ef2 <XkbUseExtension+834>: mov %rdx,0x40(%rax)
 PC (0x7f519b618ef2) ok
 source "%rdx" ok
 destination "0x40(%rax)" (0x00000041) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: lxinput
StacktraceTop:
 XkbUseExtension () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XkbSetAutoRepeatRate () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? ()
 __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
Title: lxinput crashed with SIGSEGV in XkbUseExtension()
UpgradeStatus: Upgraded to natty on 2011-03-21 (22 days ago)
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare

Revision history for this message
Terje Andersen (terander) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #725194, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.