Bug 1097707 - [abrt] network-manager-applet: _g_log_abort(): nm-applet killed by SIGABRT
Summary: [abrt] network-manager-applet: _g_log_abort(): nm-applet killed by SIGABRT
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: network-manager-applet
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:1f73e315b7757ca4216d13f6416...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-14 11:43 UTC by kero89
Modified: 2023-09-14 02:07 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 20:37:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (20.51 KB, text/plain)
2014-05-14 11:43 UTC, kero89
no flags Details
File: cgroup (172 bytes, text/plain)
2014-05-14 11:43 UTC, kero89
no flags Details
File: core_backtrace (13.33 KB, text/plain)
2014-05-14 11:43 UTC, kero89
no flags Details
File: dso_list (10.19 KB, text/plain)
2014-05-14 11:43 UTC, kero89
no flags Details
File: environ (1.33 KB, text/plain)
2014-05-14 11:43 UTC, kero89
no flags Details
File: limits (1.29 KB, text/plain)
2014-05-14 11:43 UTC, kero89
no flags Details
File: maps (50.67 KB, text/plain)
2014-05-14 11:43 UTC, kero89
no flags Details
File: open_fds (736 bytes, text/plain)
2014-05-14 11:43 UTC, kero89
no flags Details
File: proc_pid_status (941 bytes, text/plain)
2014-05-14 11:43 UTC, kero89
no flags Details
File: var_log_messages (791 bytes, text/plain)
2014-05-14 11:43 UTC, kero89
no flags Details

Description kero89 2014-05-14 11:43:00 UTC
Version-Release number of selected component:
network-manager-applet-0.9.9.0-9.git20140123.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        nm-applet
crash_function: _g_log_abort
executable:     /usr/bin/nm-applet
kernel:         3.14.3-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (7 frames)
 #2 _g_log_abort at gmessages.c:255
 #5 get_existing_secrets_cb at applet.c:3140
 #6 keyring_find_secrets_cb at applet-agent.c:429
 #7 g_simple_async_result_complete at gsimpleasyncresult.c:777
 #8 on_search_secrets at secret-methods.c:98
 #9 g_simple_async_result_complete at gsimpleasyncresult.c:777
 #10 complete_in_idle_cb at gsimpleasyncresult.c:789

Comment 1 kero89 2014-05-14 11:43:06 UTC
Created attachment 895452 [details]
File: backtrace

Comment 2 kero89 2014-05-14 11:43:09 UTC
Created attachment 895453 [details]
File: cgroup

Comment 3 kero89 2014-05-14 11:43:11 UTC
Created attachment 895454 [details]
File: core_backtrace

Comment 4 kero89 2014-05-14 11:43:14 UTC
Created attachment 895455 [details]
File: dso_list

Comment 5 kero89 2014-05-14 11:43:16 UTC
Created attachment 895456 [details]
File: environ

Comment 6 kero89 2014-05-14 11:43:18 UTC
Created attachment 895457 [details]
File: limits

Comment 7 kero89 2014-05-14 11:43:23 UTC
Created attachment 895458 [details]
File: maps

Comment 8 kero89 2014-05-14 11:43:25 UTC
Created attachment 895459 [details]
File: open_fds

Comment 9 kero89 2014-05-14 11:43:28 UTC
Created attachment 895460 [details]
File: proc_pid_status

Comment 10 kero89 2014-05-14 11:43:30 UTC
Created attachment 895461 [details]
File: var_log_messages

Comment 11 Jirka Klimes 2014-05-15 15:23:56 UTC
Logs:
mai 13 22:21:31 hosting /etc/gdm/Xsession[3401]: nm-applet-Message: No keyring secrets found for Bbox-C32BA0/802-11-wireless-security; asking user.
mai 13 22:21:31 hosting /etc/gdm/Xsession[3401]: (nm-applet:3634): GLib-CRITICAL **: g_hash_table_iter_next: assertion 'ri->version == ri->hash_table->version' failed
mai 13 22:21:31 hosting /etc/gdm/Xsession[3401]: (nm-applet:3634): nm-applet-CRITICAL **: get_device_class_from_connection: assertion 'applet != NULL' failed
mai 13 22:21:31 hosting /etc/gdm/Xsession[3401]: nm-applet:ERROR:applet.c:3140:get_existing_secrets_cb: assertion failed: (dclass)

Do you happen to know how to reproduce the crash?

Comment 12 Fedora End Of Life 2015-05-29 11:50:37 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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 20 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 13 Fedora End Of Life 2015-06-29 20:37:04 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.

Comment 14 Red Hat Bugzilla 2023-09-14 02:07:51 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


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