Bug 1752022 - [abrt] xfce4-settings: is_end(): xfce4-keyboard-settings killed by SIGSEGV
Summary: [abrt] xfce4-settings: is_end(): xfce4-keyboard-settings killed by SIGSEGV
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xfce4-settings
Version: 30
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:d960cece1652363403588a60660...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-13 13:15 UTC by Sergio
Modified: 2020-05-26 17:05 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-26 17:05:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (35.92 KB, text/plain)
2019-09-13 13:15 UTC, Sergio
no flags Details
File: cgroup (331 bytes, text/plain)
2019-09-13 13:15 UTC, Sergio
no flags Details
File: core_backtrace (16.46 KB, text/plain)
2019-09-13 13:15 UTC, Sergio
no flags Details
File: cpuinfo (986 bytes, text/plain)
2019-09-13 13:15 UTC, Sergio
no flags Details
File: dso_list (9.85 KB, text/plain)
2019-09-13 13:15 UTC, Sergio
no flags Details
File: environ (1.07 KB, text/plain)
2019-09-13 13:15 UTC, Sergio
no flags Details
File: exploitable (82 bytes, text/plain)
2019-09-13 13:15 UTC, Sergio
no flags Details
File: limits (1.29 KB, text/plain)
2019-09-13 13:15 UTC, Sergio
no flags Details
File: maps (57.18 KB, text/plain)
2019-09-13 13:15 UTC, Sergio
no flags Details
File: mountinfo (3.21 KB, text/plain)
2019-09-13 13:15 UTC, Sergio
no flags Details
File: open_fds (738 bytes, text/plain)
2019-09-13 13:15 UTC, Sergio
no flags Details
File: proc_pid_status (1.31 KB, text/plain)
2019-09-13 13:15 UTC, Sergio
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Xfce 15958 0 None None None 2019-09-14 12:36:04 UTC

Description Sergio 2019-09-13 13:15:15 UTC
Description of problem:
It happened yesterday, so I think I was editing a keyboard shortcut (changing the URL after a web browser command) and so I set the same shortcut as before.
Then a dialog popped-up asking which command I wanted to use, the old or the new, I clicked the new one and... now I'm not quite sure if the settings manager crashed right there
or if the window went back to the main window (that is an internal crash anyway as it's supposed to stay in the keyboard shortcuts window).
But eventually the GUI crashed and abrt popped-up.

This is an operation that usually works, but sometimes Xfce crashes and I feel it's related with having an old computer and doing things quickly.
Mostly is Thunar crashing when dealing with thumbnails.

Version-Release number of selected component:
xfce4-settings-4.14.1-1.fc30

Additional info:
reporter:       libreport-2.10.1
backtrace_rating: 4
cmdline:        xfce4-keyboard-settings --socket-id=58720942
crash_function: is_end
executable:     /usr/bin/xfce4-keyboard-settings
journald_cursor: s=950fb7e409774778901f839c81a04a32;i=119201;b=e494d5f3737d444998da1495c4909ae0;m=13fd7c9b;t=59261cf81f058;x=b706f206af04ba46
kernel:         5.2.13-200.fc30.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 is_end at ../glib/gsequence.c:202
 #1 g_sequence_iter_is_end at ../glib/gsequence.c:1405
 #2 iter_is_valid at gtkliststore.c:392
 #3 gtk_list_store_remove at gtkliststore.c:1203
 #4 xfce_keyboard_settings_edit_button_clicked at xfce-keyboard-settings.c:1164
 #5 _g_closure_invoke_va at ../gobject/gclosure.c:873
 #8 gtk_button_do_release at gtkbutton.c:1845
 #10 gtk_real_button_released at gtkbutton.c:1963
 #11 _g_closure_invoke_va at ../gobject/gclosure.c:873
 #14 multipress_released_cb at gtkbutton.c:666

Comment 1 Sergio 2019-09-13 13:15:19 UTC
Created attachment 1614874 [details]
File: backtrace

Comment 2 Sergio 2019-09-13 13:15:20 UTC
Created attachment 1614875 [details]
File: cgroup

Comment 3 Sergio 2019-09-13 13:15:22 UTC
Created attachment 1614876 [details]
File: core_backtrace

Comment 4 Sergio 2019-09-13 13:15:23 UTC
Created attachment 1614877 [details]
File: cpuinfo

Comment 5 Sergio 2019-09-13 13:15:25 UTC
Created attachment 1614878 [details]
File: dso_list

Comment 6 Sergio 2019-09-13 13:15:26 UTC
Created attachment 1614879 [details]
File: environ

Comment 7 Sergio 2019-09-13 13:15:27 UTC
Created attachment 1614880 [details]
File: exploitable

Comment 8 Sergio 2019-09-13 13:15:28 UTC
Created attachment 1614881 [details]
File: limits

Comment 9 Sergio 2019-09-13 13:15:31 UTC
Created attachment 1614882 [details]
File: maps

Comment 10 Sergio 2019-09-13 13:15:33 UTC
Created attachment 1614883 [details]
File: mountinfo

Comment 11 Sergio 2019-09-13 13:15:34 UTC
Created attachment 1614884 [details]
File: open_fds

Comment 12 Sergio 2019-09-13 13:15:35 UTC
Created attachment 1614885 [details]
File: proc_pid_status

Comment 13 Mukundan Ragavan 2019-09-14 12:36:05 UTC
Reported upstream.

Comment 14 Ben Cotton 2020-04-30 21:08:23 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
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 '30'.

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 30 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 15 Ben Cotton 2020-05-26 17:05:36 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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.