Bug 894128

Summary: [abrt] ModemManager-0.6.0.0-2.fc18: custom_init_response: Process /usr/sbin/modem-manager was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: mjlad <alsubaie2000>
Component: ModemManagerAssignee: Dan Williams <dcbw>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: dcbw, ddrazyk, momedn
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:3a170f67bd8f6f1ca89081caa8c4c35f9c9462eb
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 14:41:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description mjlad 2013-01-10 19:46:16 UTC
Version-Release number of selected component:
ModemManager-0.6.0.0-2.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/sbin/modem-manager
crash_function: custom_init_response
executable:     /usr/sbin/modem-manager
kernel:         3.6.10-4.fc18.i686
remote_result:  NOTFOUND
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #1 custom_init_response at mm-plugin-base.c:980
 #2 handle_response at mm-at-serial-port.c:134
 #3 mm_serial_port_close at mm-serial-port.c:970
 #4 supports_task_dispose at mm-plugin-base.c:401
 #6 g_hash_table_remove_node at ghash.c:484
 #7 g_hash_table_remove_internal at ghash.c:1274
 #8 cancel_supports_port at mm-plugin-base.c:1432
 #9 supports_info_free at mm-manager.c:461
 #10 g_hash_table_remove_node at ghash.c:484
 #11 g_hash_table_remove_internal at ghash.c:1274

Comment 1 mjlad 2013-01-10 19:46:28 UTC
Created attachment 676509 [details]
File: backtrace

Comment 2 mjlad 2013-01-10 19:46:37 UTC
Created attachment 676510 [details]
File: cgroup

Comment 3 mjlad 2013-01-10 19:46:45 UTC
Created attachment 676511 [details]
File: core_backtrace

Comment 4 mjlad 2013-01-10 19:46:55 UTC
Created attachment 676512 [details]
File: dso_list

Comment 5 mjlad 2013-01-10 19:47:07 UTC
Created attachment 676513 [details]
File: environ

Comment 6 mjlad 2013-01-10 19:47:15 UTC
Created attachment 676514 [details]
File: limits

Comment 7 mjlad 2013-01-10 19:47:26 UTC
Created attachment 676515 [details]
File: maps

Comment 8 mjlad 2013-01-10 19:47:33 UTC
Created attachment 676516 [details]
File: open_fds

Comment 9 mjlad 2013-01-10 19:47:44 UTC
Created attachment 676517 [details]
File: proc_pid_status

Comment 10 mjlad 2013-01-10 19:47:51 UTC
Created attachment 676518 [details]
File: var_log_messages

Comment 11 Dominik Drazyk 2013-06-18 18:56:16 UTC
Inserted Huawei EM770W mpci-e modem.

reporter:       libreport-2.1.4
backtrace_rating: 4
cmdline:        /usr/sbin/modem-manager
crash_function: custom_init_response
executable:     /usr/sbin/modem-manager
kernel:         3.9.5-201.fc18.x86_64
package:        ModemManager-0.6.0.0-3.fc18
reason:         Process /usr/sbin/modem-manager was killed by signal 11 (SIGSEGV)
runlevel:       N 5
uid:            0

Comment 12 Momed 2013-10-18 22:46:02 UTC
modem disconnect

reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        /usr/sbin/modem-manager
crash_function: custom_init_response
executable:     /usr/sbin/modem-manager
kernel:         3.6.10-4.fc18.i686
package:        ModemManager-0.6.0.0-2.fc18
reason:         Process /usr/sbin/modem-manager was killed by signal 11 (SIGSEGV)
type:           CCpp
uid:            0

Comment 13 Fedora End Of Life 2013-12-21 10:18:48 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 2014-02-05 14:41:40 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.