urfkilld crashed with SIGSEGV in g_main_context_dispatch()

Bug #1357657 reported by John Lenton
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
urfkill (Ubuntu)
New
Undecided
Unassigned

Bug Description

got this the first time i logged in after booting today

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: urfkill 0.6.0~20140708.110711.a0581f3-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-8.13-generic 3.16.0
Uname: Linux 3.16.0-8-generic x86_64
ApportVersion: 2.14.5-0ubuntu4
Architecture: amd64
Date: Sat Aug 16 07:56:11 2014
ExecutablePath: /usr/lib/x86_64-linux-gnu/urfkill/urfkilld
InstallationDate: Installed on 2014-04-27 (110 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcCmdline: /usr/lib/x86_64-linux-gnu/urfkill/urfkilld
ProcEnviron:
 PATH=(custom, no user)
 TERM=linux
SegvAnalysis:
 Segfault happened at: 0x7f4086d41e13 <_IO_vfprintf_internal+7443>: repnz scas %es:(%rdi),%al
 PC (0x7f4086d41e13) ok
 source "%es:(%rdi)" (0x00000020) not located in a known VMA region (needed readable region)!
 destination "%al" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: urfkill
StacktraceTop:
 ?? ()
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
SystemImageInfo:
 current build number: 0
 device name:
 channel: daily
 last update: Unknown
Title: urfkilld crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: Upgraded to utopic on 2014-06-02 (74 days ago)
UserGroups:

Revision history for this message
John Lenton (chipaca) 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 this software better. This particular crash has already been reported and is a duplicate of bug #1357576, 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.

information type: 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.