Bug 697550 - [abrt] ModemManager-0.4-4.git20100720.fc14: handle_probe_response: Process /usr/sbin/modem-manager was killed by signal 11 (SIGSEGV)
Summary: [abrt] ModemManager-0.4-4.git20100720.fc14: handle_probe_response: Process /u...
Keywords:
Status: CLOSED DUPLICATE of bug 783947
Alias: None
Product: Fedora
Classification: Fedora
Component: ModemManager
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:865217d7060c4e3c61c9edbb250...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-18 15:05 UTC by virus
Modified: 2012-03-21 15:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-21 15:22:57 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (6.63 KB, text/plain)
2011-04-18 15:05 UTC, virus
no flags Details

Description virus 2011-04-18 15:05:22 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: /usr/sbin/modem-manager
component: ModemManager
crash_function: handle_probe_response
executable: /usr/sbin/modem-manager
kernel: 2.6.35.6-45.fc14.i686
package: ModemManager-0.4-4.git20100720.fc14
rating: 4
reason: Process /usr/sbin/modem-manager was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1302765297
uid: 0

How to reproduce
-----
1.i was trying to connect to my bsnl 3g modem
2.
3.

Comment 1 virus 2011-04-18 15:05:26 UTC
Created attachment 492911 [details]
File: backtrace

Comment 2 virus 2011-04-18 15:18:34 UTC
Package: ModemManager-0.4-4.git20100720.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.i was trying to connect to my bsnl 3g modem
2.
3.

Comment 3 Dan Williams 2011-07-18 22:51:32 UTC
Does the bug go away with the latest testing update?

https://admin.fedoraproject.org/updates/ModemManager-0.4.998-1.git20110706.fc14

Comment 4 abrt-bot 2012-03-21 15:22:57 UTC
Backtrace analysis found this bug to be similar to bug #783947, closing as duplicate.

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 783947 ***


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