urfkilld crashed with SIGSEGV in g_main_context_dispatch()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
urfkill (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
may be related with bug #1357373 since aport triggerred right after the previous networkmanager one?
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: urfkill 0.6.0~20140708.
ProcVersionSign
Uname: Linux 3.16.0-9-generic x86_64
ApportVersion: 2.14.5-0ubuntu4
Architecture: amd64
Date: Sun Aug 17 12:10:47 2014
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2014-04-24 (115 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcCmdline: /usr/lib/
ProcEnviron:
PATH=(custom, no user)
TERM=linux
SegvAnalysis:
Segfault happened at: 0x7f101306ce13 <_IO_vfprintf_
PC (0x7f101306ce13) 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_
?? () from /lib/x86_
g_main_loop_run () from /lib/x86_
?? ()
SystemImageInfo: Error: [Errno 2] Aucun fichier ou dossier de ce type: 'system-image-cli'
Title: urfkilld crashed with SIGSEGV in g_main_
UpgradeStatus: Upgraded to utopic on 2014-07-31 (17 days ago)
UserGroups:
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.