Bug 982136
| Summary: | [abrt] ModemManager-0.6.2.0-1.fc19: supports_port: Process /usr/sbin/modem-manager was killed by signal 11 (SIGSEGV) | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Emmanuel Touzery <emmanuel.touzery> | ||||||||||||||||||||||
| Component: | ModemManager | Assignee: | Dan Williams <dcbw> | ||||||||||||||||||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||||||
| Version: | 19 | CC: | adam, albertod17, brpocock, christoph.wickert, d3trax, danielpalenski, dcbw, fedorabugs, fnord, frank.schletz, giuseppemfusco, lutchass, matthew.hooper, mbriza, me, motoskov, santosdleandro, sheeshmohsin, stressfreechozeme, two.oes | ||||||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||||||||
| Whiteboard: | abrt_hash:1ade39fa2192ff867a7f64d66ebe41fbd7a6f651 | ||||||||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||||||
| Last Closed: | 2015-02-17 15:57:41 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
Emmanuel Touzery
2013-07-08 08:51:15 UTC
Created attachment 770358 [details]
File: backtrace
Created attachment 770359 [details]
File: cgroup
Created attachment 770360 [details]
File: core_backtrace
Created attachment 770361 [details]
File: dso_list
Created attachment 770362 [details]
File: environ
Created attachment 770363 [details]
File: limits
Created attachment 770364 [details]
File: maps
Created attachment 770365 [details]
File: open_fds
Created attachment 770366 [details]
File: proc_pid_status
Created attachment 770367 [details]
File: var_log_messages
Connected my Android phone with a USB cable. reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/sbin/modem-manager crash_function: supports_port executable: /usr/sbin/modem-manager kernel: 3.9.9-302.fc19.x86_64 package: ModemManager-0.6.2.0-1.fc19 reason: Process /usr/sbin/modem-manager was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 0 Unknown, I don't use modem manager reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/sbin/modem-manager crash_function: supports_port executable: /usr/sbin/modem-manager kernel: 3.10.3-300.fc19.x86_64 package: ModemManager-0.6.2.0-1.fc19 reason: Process /usr/sbin/modem-manager was killed by signal 11 (SIGSEGV) runlevel: N 3 uid: 0 unplugged galaxy note 2 from usb while ristretto image viewer was focus application reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/sbin/modem-manager crash_function: supports_port executable: /usr/sbin/modem-manager kernel: 3.11.0-3.fc20.x86_64 package: ModemManager-0.6.2.0-1.fc19 reason: Process /usr/sbin/modem-manager was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 0 I plugged in my Samsung Galaxy Note phone into the system, then the crash report came. reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/sbin/modem-manager crash_function: supports_port executable: /usr/sbin/modem-manager kernel: 3.10.10-200.fc19.x86_64 package: ModemManager-0.6.2.0-1.fc19 reason: Process /usr/sbin/modem-manager was killed by signal 11 (SIGSEGV) reported_to: uReport: BTHASH=9534108c172e36e74ebd61f3d249cc18266cdddb runlevel: N 5 uid: 0 after the system work initerrupdamente 144 hours and I perform an update in offline mode. reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/sbin/modem-manager crash_function: supports_port executable: /usr/sbin/modem-manager kernel: 3.10.5-201.fc19.x86_64 package: ModemManager-0.6.2.0-1.fc19 reason: Process /usr/sbin/modem-manager was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 0 I don't know what happened, an error report just popped out. reporter: libreport-2.1.9 backtrace_rating: 3 cmdline: /usr/sbin/modem-manager crash_function: supports_port executable: /usr/sbin/modem-manager kernel: 3.11.6-200.fc19.x86_64 package: ModemManager-0.6.2.0-1.fc19 reason: Process /usr/sbin/modem-manager was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 0 I recently installled the internal Qualcom Gobi 2000 3G modem of my Thinkpad by downloading the firmware and installing gobi_loader. After a reboot, the modem was reported operational, bt when I wanted to use it, modem-manager crashed. reporter: libreport-2.1.9 backtrace_rating: 3 cmdline: /usr/sbin/modem-manager crash_function: supports_port executable: /usr/sbin/modem-manager kernel: 3.11.9-200.fc19.x86_64 package: ModemManager-0.6.2.0-1.fc19 reason: Process /usr/sbin/modem-manager was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 0 Another user experienced a similar problem: nothing special reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/sbin/modem-manager crash_function: supports_port executable: /usr/sbin/modem-manager kernel: 3.11.10-200.fc19.x86_64 package: ModemManager-0.6.2.0-1.fc19 reason: modem-manager killed by SIGSEGV runlevel: N 5 type: CCpp uid: 0 Another user experienced a similar problem: Plugged in my Samsung Galaxy Note 3 to move files and it crashed. reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: /usr/sbin/modem-manager crash_function: supports_port executable: /usr/sbin/modem-manager kernel: 3.14.4-100.fc19.x86_64 package: ModemManager-0.6.2.0-1.fc19 reason: modem-manager killed by SIGSEGV runlevel: N 5 type: CCpp uid: 0 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. 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. |