connmand crashed with SIGSEGV in connman_network_get_bool()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
connman (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: connman
I tried to connect to Internet with Nokia N900 at home.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: connman 0.69-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.38-6-generic x86_64
Architecture: amd64
Date: Sat Mar 12 12:58:33 2011
ExecutablePath: /usr/sbin/connmand
IpRoute:
192.168.1.1 dev wlan0 scope link
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.132
default dev gprs0 scope link
MachineType: SAMSUNG ELECTRONICS CO., LTD. X120/X170
ProcCmdline: connmand -c
ProcEnviron: PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f1dc4830030 <connman_
PC (0x7f1dc4830030) ok
source "0x1bc(%rbp)" (0x000001bc) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: connman
StacktraceTop:
connman_
disconnected_
g_timeout_dispatch (source=
g_main_dispatch (context=
g_main_
Title: connmand crashed with SIGSEGV in connman_
UpgradeStatus: Upgraded to natty on 2011-02-04 (36 days ago)
UserGroups:
dmi.bios.date: 10/13/2009
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 04CX.M005.
dmi.board.name: X120/X170
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: X120/X170
dmi.product.
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
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 #733458, 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.