Bug 595071 - [abrt] crash in NetworkManager-gnome-1:0.8.0-6.git20100408.fc12: __strnlen: Process /usr/bin/nm-applet was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in NetworkManager-gnome-1:0.8.0-6.git20100408.fc12: __strnlen: P...
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 12
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:89d6ed19b08022d75d8e0d83a9d...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-23 09:38 UTC by Alexander von Zuev
Modified: 2010-12-03 14:26 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-12-03 14:26:51 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (13.53 KB, text/plain)
2010-05-23 09:38 UTC, Alexander von Zuev
no flags Details

Description Alexander von Zuev 2010-05-23 09:38:33 UTC
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: nm-applet --sm-disable
component: NetworkManager
crash_function: __strnlen
executable: /usr/bin/nm-applet
global_uuid: 89d6ed19b08022d75d8e0d83a9dfdf78dd28f054
package: NetworkManager-gnome-1:0.8.0-6.git20100408.fc12
rating: 4
reason: Process /usr/bin/nm-applet was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

Comment 1 Alexander von Zuev 2010-05-23 09:38:36 UTC
Created attachment 415931 [details]
File: backtrace

Comment 2 Jirka Klimes 2010-05-24 15:17:15 UTC
Reporter: Are you able to reproduce the bug? What was you doing when the crash appeared?

Weird; looks like a memory corruption somewhere, because abs_filename=0xb is apparently wrong.

#2  0x00411037 in _nl_make_l10nflist (l10nfile_list=0x559c40, 
    dirlist=0x5209f0 "/usr/share/locale", dirlist_len=18, mask=0, 
    language=0xbfd759a0 "ru_RU.UTF-8", territory=0x0, codeset=0x0, 
    normalized_codeset=0x0, modifier=0x0, 
    filename=0xbfd759c0 "LC_MESSAGES/nm-applet.mo", do_allocate=0)
    at l10nflist.c:213
        abs_filename = 0xb <Address 0xb out of bounds>
        last = 0x0
        retval = 0x0
        cp = <value optimized out>
        entries = <value optimized out>
        cnt = <value optimized out>

Comment 3 Bug Zapper 2010-11-03 14:22:12 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 

Comment 4 Bug Zapper 2010-12-03 14:26:51 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.

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.