Bug 1064578 - [abrt] upower: _g_log_abort(): upowerd killed by SIGTRAP
Summary: [abrt] upower: _g_log_abort(): upowerd killed by SIGTRAP
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: upower
Version: 22
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:23caf0fd8726463490c338b4c0e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-12 21:59 UTC by piio
Modified: 2016-07-19 10:59 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-07-19 10:59:55 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (29.74 KB, text/plain)
2014-02-12 21:59 UTC, piio 		no flags Details
File: cgroup (144 bytes, text/plain)
2014-02-12 21:59 UTC, piio 		no flags Details
File: core_backtrace (9.37 KB, text/plain)
2014-02-12 21:59 UTC, piio 		no flags Details
File: dso_list (4.16 KB, text/plain)
2014-02-12 21:59 UTC, piio 		no flags Details
File: environ (71 bytes, text/plain)
2014-02-12 21:59 UTC, piio 		no flags Details
File: limits (1.29 KB, text/plain)
2014-02-12 21:59 UTC, piio 		no flags Details
File: maps (12.77 KB, text/plain)
2014-02-12 21:59 UTC, piio 		no flags Details
File: open_fds (416 bytes, text/plain)
2014-02-12 21:59 UTC, piio 		no flags Details
File: proc_pid_status (755 bytes, text/plain)
2014-02-12 21:59 UTC, piio 		no flags Details
File: var_log_messages (1.12 KB, text/plain)
2014-02-12 21:59 UTC, piio 		no flags Details
View All

Description piio 2014-02-12 21:59:16 UTC 
Version-Release number of selected component:
upower-0.99.0-2.fc21

Additional info:
reporter:       libreport-2.1.12
backtrace_rating: 4
cmdline:        /usr/libexec/upowerd
crash_function: _g_log_abort
executable:     /usr/libexec/upowerd
kernel:         3.14.0-0.rc2.git0.2.fc21.i686+PAE
runlevel:       unknown
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (9 frames)
 #0 _g_log_abort at gmessages.c:308
 #3 up_polkit_init at up-polkit.c:255
 #4 g_type_create_instance at gtype.c:1868
 #5 g_object_new_internal at gobject.c:1723
 #8 up_polkit_new at up-polkit.c:273
 #9 up_daemon_init at up-daemon.c:1115
 #10 g_type_create_instance at gtype.c:1868
 #11 g_object_new_internal at gobject.c:1723
 #14 up_daemon_new at up-daemon.c:1308
Comment 1 piio 2014-02-12 21:59:21 UTC 
Created attachment 862551 [details]
File: backtrace
Comment 2 piio 2014-02-12 21:59:23 UTC 
Created attachment 862552 [details]
File: cgroup
Comment 3 piio 2014-02-12 21:59:25 UTC 
Created attachment 862553 [details]
File: core_backtrace
Comment 4 piio 2014-02-12 21:59:27 UTC 
Created attachment 862554 [details]
File: dso_list
Comment 5 piio 2014-02-12 21:59:29 UTC 
Created attachment 862555 [details]
File: environ
Comment 6 piio 2014-02-12 21:59:31 UTC 
Created attachment 862556 [details]
File: limits
Comment 7 piio 2014-02-12 21:59:33 UTC 
Created attachment 862557 [details]
File: maps
Comment 8 piio 2014-02-12 21:59:35 UTC 
Created attachment 862558 [details]
File: open_fds
Comment 9 piio 2014-02-12 21:59:37 UTC 
Created attachment 862559 [details]
File: proc_pid_status
Comment 10 piio 2014-02-12 21:59:42 UTC 
Created attachment 862560 [details]
File: var_log_messages
Comment 11 Jaroslav Reznik 2015-03-03 15:28:40 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Comment 12 Fedora End Of Life 2016-07-19 10:59:55 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.
Note You need to log in before you can comment on or make changes to this bug.