Bug 1298835 - [abrt] xfce4-power-manager: strlen(): xfce4-power-manager-settings killed by SIGSEGV
Summary: [abrt] xfce4-power-manager: strlen(): xfce4-power-manager-settings killed by ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xfce4-power-manager
Version: 23
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mukundan Ragavan
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:6fb33ef7b4c032a6ea4036eb675...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-15 08:55 UTC by laolux
Modified: 2016-12-20 17:54 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-20 17:54:46 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (40.00 KB, text/plain)
2016-01-15 08:55 UTC, laolux
no flags Details
File: cgroup (200 bytes, text/plain)
2016-01-15 08:55 UTC, laolux
no flags Details
File: core_backtrace (9.17 KB, text/plain)
2016-01-15 08:55 UTC, laolux
no flags Details
File: dso_list (9.88 KB, text/plain)
2016-01-15 08:56 UTC, laolux
no flags Details
File: environ (2.58 KB, text/plain)
2016-01-15 08:56 UTC, laolux
no flags Details
File: exploitable (82 bytes, text/plain)
2016-01-15 08:56 UTC, laolux
no flags Details
File: limits (1.29 KB, text/plain)
2016-01-15 08:56 UTC, laolux
no flags Details
File: maps (50.54 KB, text/plain)
2016-01-15 08:56 UTC, laolux
no flags Details
File: mountinfo (3.64 KB, text/plain)
2016-01-15 08:56 UTC, laolux
no flags Details
File: namespaces (85 bytes, text/plain)
2016-01-15 08:56 UTC, laolux
no flags Details
File: open_fds (983 bytes, text/plain)
2016-01-15 08:56 UTC, laolux
no flags Details
File: proc_pid_status (1.02 KB, text/plain)
2016-01-15 08:56 UTC, laolux
no flags Details
File: var_log_messages (28 bytes, text/plain)
2016-01-15 08:56 UTC, laolux
no flags Details

Description laolux 2016-01-15 08:55:51 UTC
Version-Release number of selected component:
xfce4-power-manager-1.5.2-1.fc23

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        xfce4-power-manager-settings
crash_function: strlen
executable:     /usr/bin/xfce4-power-manager-settings
global_pid:     5573
kernel:         4.3.3-300.fc23.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 strlen at ../sysdeps/x86_64/strlen.S:106
 #1 get_device_description at xfpm-power-common.c:267
 #2 update_sideview_icon at xfpm-settings.c:1787
 #3 update_device_details at xfpm-settings.c:1949
 #9 g_object_notify_by_spec_internal at gobject.c:1154
 #10 g_object_notify at gobject.c:1202
 #16 g_object_notify_by_spec_internal at gobject.c:1154
 #17 g_object_notify at gobject.c:1202
 #18 up_device_glue_proxy_g_properties_changed at up-device-glue.c:2706
 #19 ffi_call_unix64 at ../src/x86/unix64.S:76

Comment 1 laolux 2016-01-15 08:55:56 UTC
Created attachment 1115046 [details]
File: backtrace

Comment 2 laolux 2016-01-15 08:55:57 UTC
Created attachment 1115047 [details]
File: cgroup

Comment 3 laolux 2016-01-15 08:55:58 UTC
Created attachment 1115048 [details]
File: core_backtrace

Comment 4 laolux 2016-01-15 08:56:00 UTC
Created attachment 1115049 [details]
File: dso_list

Comment 5 laolux 2016-01-15 08:56:01 UTC
Created attachment 1115050 [details]
File: environ

Comment 6 laolux 2016-01-15 08:56:03 UTC
Created attachment 1115051 [details]
File: exploitable

Comment 7 laolux 2016-01-15 08:56:04 UTC
Created attachment 1115052 [details]
File: limits

Comment 8 laolux 2016-01-15 08:56:06 UTC
Created attachment 1115053 [details]
File: maps

Comment 9 laolux 2016-01-15 08:56:07 UTC
Created attachment 1115054 [details]
File: mountinfo

Comment 10 laolux 2016-01-15 08:56:09 UTC
Created attachment 1115055 [details]
File: namespaces

Comment 11 laolux 2016-01-15 08:56:10 UTC
Created attachment 1115056 [details]
File: open_fds

Comment 12 laolux 2016-01-15 08:56:11 UTC
Created attachment 1115057 [details]
File: proc_pid_status

Comment 13 laolux 2016-01-15 08:56:13 UTC
Created attachment 1115058 [details]
File: var_log_messages

Comment 14 Mukundan Ragavan 2016-01-21 00:28:23 UTC
What were you doing when this happened?

Cam you provide me with steps to reproduce this?

Comment 15 Fedora End Of Life 2016-11-24 14:57:47 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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 16 Fedora End Of Life 2016-12-20 17:54:46 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.