touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #08346
[Bug 1354514] [NEW] ModemManager crashed with SIGSEGV in g_simple_async_result_complete()
Public bug reported:
Crashes regularly when I am trying to connect to / disconnect from a
mobile network.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: modemmanager 1.0.0-2ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic i686
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: i386
CrashCounter: 1
Date: Fri Aug 8 15:45:20 2014
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/sbin/ModemManager
InstallationDate: Installed on 2010-03-20 (1602 days ago)
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
ProcCmdline: /usr/sbin/ModemManager
ProcEnviron:
PATH=(custom, no user)
TERM=linux
SegvAnalysis:
Segfault happened at: 0x0: Cannot access memory at address 0x0
PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: modemmanager
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
g_simple_async_result_complete () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
Title: ModemManager crashed with SIGSEGV in g_simple_async_result_complete()
UpgradeStatus: Upgraded to trusty on 2013-09-29 (313 days ago)
UserGroups:
** Affects: modemmanager (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-crash i386 need-i386-retrace trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1354514
Title:
ModemManager crashed with SIGSEGV in g_simple_async_result_complete()
Status in “modemmanager” package in Ubuntu:
New
Bug description:
Crashes regularly when I am trying to connect to / disconnect from a
mobile network.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: modemmanager 1.0.0-2ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic i686
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: i386
CrashCounter: 1
Date: Fri Aug 8 15:45:20 2014
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/sbin/ModemManager
InstallationDate: Installed on 2010-03-20 (1602 days ago)
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
ProcCmdline: /usr/sbin/ModemManager
ProcEnviron:
PATH=(custom, no user)
TERM=linux
SegvAnalysis:
Segfault happened at: 0x0: Cannot access memory at address 0x0
PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: modemmanager
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
g_simple_async_result_complete () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
Title: ModemManager crashed with SIGSEGV in g_simple_async_result_complete()
UpgradeStatus: Upgraded to trusty on 2013-09-29 (313 days ago)
UserGroups:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1354514/+subscriptions
Follow ups
-
[Bug 1354514] Re: ModemManager crashed with SIGSEGV in interface_disabling_step()
From: Bug Watch Updater, 2014-10-30
-
[Bug 1354514] Re: ModemManager crashed with SIGSEGV in interface_disabling_step()
From: Launchpad Bug Tracker, 2014-08-25
-
[Bug 1354514] Re: ModemManager crashed with SIGSEGV in interface_disabling_step()
From: Bug Watch Updater, 2014-08-13
-
[Bug 1354514] Re: ModemManager crashed with SIGSEGV in interface_disabling_step()
From: Bug Watch Updater, 2014-08-11
-
[Bug 1354514] Re: ModemManager crashed with SIGSEGV in interface_disabling_step()
From: Marius B. Kotsbak, 2014-08-11
-
[Bug 1354514] ThreadStacktrace.txt
From: Apport retracing service, 2014-08-08
-
[Bug 1354514] StacktraceSource.txt
From: Apport retracing service, 2014-08-08
-
[Bug 1354514] Stacktrace.txt
From: Apport retracing service, 2014-08-08
-
[Bug 1354514]
From: Apport retracing service, 2014-08-08
-
[Bug 1354514] [NEW] ModemManager crashed with SIGSEGV in g_simple_async_result_complete()
From: Dmitry Shachnev, 2014-08-08
References