Bug 1013561 - [abrt] ModemManager-0.6.2.0-1.fc19: g_type_instance_get_private: Process /usr/sbin/modem-manager was killed by signal 11 (SIGSEGV) [NEEDINFO]
Summary: [abrt] ModemManager-0.6.2.0-1.fc19: g_type_instance_get_private: Process /usr...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: ModemManager
Version: 19
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8d38d6f978a3f196fa0a17b0116...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-30 10:44 UTC by Rahul Barai
Modified: 2015-02-17 17:25 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 17:25:09 UTC
Type: ---
Embargoed:
rahulbarai85: needinfo?


Attachments (Terms of Use)
File: backtrace (25.22 KB, text/plain)
2013-09-30 10:44 UTC, Rahul Barai
no flags Details
File: cgroup (155 bytes, text/plain)
2013-09-30 10:44 UTC, Rahul Barai
no flags Details
File: core_backtrace (7.54 KB, text/plain)
2013-09-30 10:44 UTC, Rahul Barai
no flags Details
File: dso_list (4.02 KB, text/plain)
2013-09-30 10:44 UTC, Rahul Barai
no flags Details
File: environ (92 bytes, text/plain)
2013-09-30 10:44 UTC, Rahul Barai
no flags Details
File: exploitable (82 bytes, text/plain)
2013-09-30 10:44 UTC, Rahul Barai
no flags Details
File: limits (1.29 KB, text/plain)
2013-09-30 10:44 UTC, Rahul Barai
no flags Details
File: maps (18.63 KB, text/plain)
2013-09-30 10:45 UTC, Rahul Barai
no flags Details
File: open_fds (1.21 KB, text/plain)
2013-09-30 10:45 UTC, Rahul Barai
no flags Details
File: proc_pid_status (900 bytes, text/plain)
2013-09-30 10:45 UTC, Rahul Barai
no flags Details
File: var_log_messages (9.46 KB, text/plain)
2013-09-30 10:45 UTC, Rahul Barai
no flags Details

Description Rahul Barai 2013-09-30 10:44:23 UTC
Version-Release number of selected component:
ModemManager-0.6.2.0-1.fc19

Additional info:
reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        /usr/sbin/modem-manager
crash_function: g_type_instance_get_private
executable:     /usr/sbin/modem-manager
kernel:         3.11.1-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 g_type_instance_get_private at gtype.c:4559
 #1 find_modem_for_device at mm-manager.c:402
 #2 supports_callback at mm-manager.c:676
 #3 mm_plugin_base_supports_task_complete at mm-plugin-base.c:335
 #8 emit_probe_result at mm-plugin-base.c:619

Comment 1 Rahul Barai 2013-09-30 10:44:28 UTC
Created attachment 805087 [details]
File: backtrace

Comment 2 Rahul Barai 2013-09-30 10:44:32 UTC
Created attachment 805088 [details]
File: cgroup

Comment 3 Rahul Barai 2013-09-30 10:44:36 UTC
Created attachment 805089 [details]
File: core_backtrace

Comment 4 Rahul Barai 2013-09-30 10:44:39 UTC
Created attachment 805090 [details]
File: dso_list

Comment 5 Rahul Barai 2013-09-30 10:44:43 UTC
Created attachment 805091 [details]
File: environ

Comment 6 Rahul Barai 2013-09-30 10:44:47 UTC
Created attachment 805092 [details]
File: exploitable

Comment 7 Rahul Barai 2013-09-30 10:44:55 UTC
Created attachment 805093 [details]
File: limits

Comment 8 Rahul Barai 2013-09-30 10:45:00 UTC
Created attachment 805094 [details]
File: maps

Comment 9 Rahul Barai 2013-09-30 10:45:05 UTC
Created attachment 805096 [details]
File: open_fds

Comment 10 Rahul Barai 2013-09-30 10:45:11 UTC
Created attachment 805099 [details]
File: proc_pid_status

Comment 11 Rahul Barai 2013-09-30 10:45:16 UTC
Created attachment 805101 [details]
File: var_log_messages

Comment 12 Rahul Barai 2013-09-30 11:00:14 UTC
Modem Manager is sometimes working, sometimes failing. Wireless and mobile broadband is not showing in nm applet, wired option is present.
 
# lsusb command is giving this output -> Bus 002 Device 004: ID 12d1:140c Huawei Technologies Co., Ltd. E180v.
and 
# usb-devices command is giving this output -> 
T:  Bus=02 Lev=02 Prnt=02 Port=06 Cnt=02 Dev#=  4 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=12d1 ProdID=140c Rev=00.00
S:  Manufacturer=HUAWEI Technology
S:  Product=HUAWEI Mobile
C:  #Ifs= 6 Cfg#= 1 Atr=e0 MxPwr=500mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I:  If#= 1 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=qmi_wwan
I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I:  If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I:  If#= 4 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
I:  If#= 5 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage.

Comment 13 Fedora End Of Life 2015-01-09 20:02:22 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 14 Fedora End Of Life 2015-02-17 17:25:09 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.