indicator-keyboard-service crashed with SIGSEGV in __pthread_mutex_unlock_usercnt()

Bug #1222848 reported by Dimitri John Ledkov
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
indicator-keyboard (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

dunno

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic x86_64
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
Date: Fri Sep 6 23:10:39 2013
ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-keyboard-service
InstallationDate: Installed on 2012-01-12 (605 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130318)
MarkForUpload: True
ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-keyboard-service --use-gtk --use-bamf
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, user)
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f25c04b7033 <__pthread_mutex_unlock_usercnt+3>: mov 0x10(%rdi),%edi
 PC (0x7f25c04b7033) ok
 source "0x10(%rdi)" (0x7475700073754254) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: indicator-keyboard
StacktraceTop:
 __pthread_mutex_unlock_usercnt (mutex=0x7475700073754244, decr=decr@entry=1) at pthread_mutex_unlock.c:37
 __GI___pthread_mutex_unlock (mutex=<optimised out>) at pthread_mutex_unlock.c:297
 g_mutex_unlock (mutex=<optimised out>) at /build/buildd/glib2.0-2.37.6/./glib/gthread-posix.c:232
 g_main_loop_run (loop=0x1529fb0) at /build/buildd/glib2.0-2.37.6/./glib/gmain.c:3908
 indicator_keyboard_service_main ()
Title: indicator-keyboard-service crashed with SIGSEGV in __pthread_mutex_unlock_usercnt()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dip kvm libvirtd lpadmin plugdev sambashare sbuild sudo

Revision history for this message
Dimitri John Ledkov (xnox) wrote :
information type: Private → Public
Changed in indicator-keyboard (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __pthread_mutex_unlock_usercnt (mutex=0x7475700073754244, decr=decr@entry=1) at pthread_mutex_unlock.c:37
 __GI___pthread_mutex_unlock (mutex=<optimized out>) at pthread_mutex_unlock.c:297
 g_mutex_unlock (mutex=<optimized out>) at /build/buildd/glib2.0-2.37.6/./glib/gthread-posix.c:232
 g_main_loop_run (loop=0x1529fb0) at /build/buildd/glib2.0-2.37.6/./glib/gmain.c:3908
 indicator_keyboard_service_up (self=<optimized out>) at main.c:373

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in indicator-keyboard (Ubuntu):
status: New → Confirmed
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.