Bug 2179620 - [abrt] gnome-control-center: _gtk_widget_is_sensitive(): gnome-control-center killed by SIGSEGV
Summary: [abrt] gnome-control-center: _gtk_widget_is_sensitive(): gnome-control-center...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-control-center
Version: 38
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: GNOME SIG Unassigned
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:23ba0b1f48ed8a0a176b3e21fd5...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-19 08:21 UTC by kabaem.chris+redhatbugzilla
Modified: 2024-05-21 14:32 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-05-21 14:32:18 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: limits (1.29 KB, text/plain)
2023-03-19 08:21 UTC, kabaem.chris+redhatbugzilla
no flags Details
File: core_backtrace (111.38 KB, text/plain)
2023-03-19 08:21 UTC, kabaem.chris+redhatbugzilla
no flags Details
File: dso_list (182 bytes, text/plain)
2023-03-19 08:21 UTC, kabaem.chris+redhatbugzilla
no flags Details
File: mountinfo (3.92 KB, text/plain)
2023-03-19 08:21 UTC, kabaem.chris+redhatbugzilla
no flags Details
File: os_info (756 bytes, text/plain)
2023-03-19 08:22 UTC, kabaem.chris+redhatbugzilla
no flags Details
File: environ (1.42 KB, text/plain)
2023-03-19 08:22 UTC, kabaem.chris+redhatbugzilla
no flags Details
File: backtrace (236.10 KB, text/plain)
2023-03-19 08:22 UTC, kabaem.chris+redhatbugzilla
no flags Details
File: open_fds (4.11 KB, text/plain)
2023-03-19 08:22 UTC, kabaem.chris+redhatbugzilla
no flags Details
File: exploitable (81 bytes, text/plain)
2023-03-19 08:22 UTC, kabaem.chris+redhatbugzilla
no flags Details
File: cpuinfo (2.81 KB, text/plain)
2023-03-19 08:22 UTC, kabaem.chris+redhatbugzilla
no flags Details
File: maps (3.98 KB, text/plain)
2023-03-19 08:22 UTC, kabaem.chris+redhatbugzilla
no flags Details
File: proc_pid_status (1.39 KB, text/plain)
2023-03-19 08:22 UTC, kabaem.chris+redhatbugzilla
no flags Details

Description kabaem.chris+redhatbugzilla 2023-03-19 08:21:51 UTC
Description of problem:
I opened the settings app, went to "Display" and back to "Wi-Fi" and pressed Escape multiple times. After that the settings app crashed.

Version-Release number of selected component:
gnome-control-center-44~rc-1.fc38

Additional info:
reporter:       libreport-2.17.8
journald_cursor: s=cc2f811a59554a5ebdec0c383276a6e9;i=7b42;b=f2545554e2aa4fa9a80218031c47588e;m=a3ec771;t=5f73bac21d3d9;x=8fd8af4ea1361e8d
uid:            1000
executable:     /usr/bin/gnome-control-center
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-gnome-gnome\x2ddisplay\x2dpanel-3228.scope
crash_function: _gtk_widget_is_sensitive
reason:         gnome-control-center killed by SIGSEGV
package:        gnome-control-center-44~rc-1.fc38
cmdline:        /usr/bin/gnome-control-center display
backtrace_rating: 4
rootdir:        /
runlevel:       N 5
type:           CCpp
comment:        I opened the settings app, went to "Display" and back to "Wi-Fi" and pressed Escape multiple times. After that the settings app crashed.
kernel:         6.2.6-300.fc38.x86_64

Truncated backtrace:
Thread no. 1 (16 frames)
 #0 _gtk_widget_is_sensitive at ../gtk/gtkwidgetprivate.h:482
 #1 gtk_shortcut_controller_run_controllers at ../gtk/gtkshortcutcontroller.c:382
 #2 gtk_shortcut_controller_handle_event at ../gtk/gtkshortcutcontroller.c:475
 #3 gtk_event_controller_handle_event at ../gtk/gtkeventcontroller.c:362
 #4 gtk_widget_run_controllers at ../gtk/gtkwidget.c:4565
 #5 gtk_widget_event at ../gtk/gtkwidget.c:4759
 #7 gtk_propagate_event_internal.isra.0 at ../gtk/gtkmain.c:1961
 #8 gtk_main_do_event at ../gtk/gtkmain.c:1703
 #9 surface_event at ../gtk/gtkwindow.c:4748
 #10 _gdk_marshal_BOOLEAN__POINTERv at gdk/gdkmarshalers.c:302
 #11 gdk_surface_event_marshallerv at ../gdk/gdksurface.c:463
 #12 _g_closure_invoke_va at ../gobject/gclosure.c:895
 #15 gdk_surface_handle_event.isra.0 at ../gdk/gdksurface.c:2956
 #19 g_main_context_iterate.isra.0 at ../glib/gmain.c:4276
 #20 g_main_context_iteration at ../glib/gmain.c:4343
 #21 g_application_run at ../gio/gapplication.c:2573


Potential duplicate: bug {crossver_id}

Comment 1 kabaem.chris+redhatbugzilla 2023-03-19 08:21:55 UTC
Created attachment 1951779 [details]
File: limits

Comment 2 kabaem.chris+redhatbugzilla 2023-03-19 08:21:56 UTC
Created attachment 1951780 [details]
File: core_backtrace

Comment 3 kabaem.chris+redhatbugzilla 2023-03-19 08:21:58 UTC
Created attachment 1951781 [details]
File: dso_list

Comment 4 kabaem.chris+redhatbugzilla 2023-03-19 08:21:59 UTC
Created attachment 1951782 [details]
File: mountinfo

Comment 5 kabaem.chris+redhatbugzilla 2023-03-19 08:22:01 UTC
Created attachment 1951783 [details]
File: os_info

Comment 6 kabaem.chris+redhatbugzilla 2023-03-19 08:22:03 UTC
Created attachment 1951784 [details]
File: environ

Comment 7 kabaem.chris+redhatbugzilla 2023-03-19 08:22:04 UTC
Created attachment 1951785 [details]
File: backtrace

Comment 8 kabaem.chris+redhatbugzilla 2023-03-19 08:22:06 UTC
Created attachment 1951786 [details]
File: open_fds

Comment 9 kabaem.chris+redhatbugzilla 2023-03-19 08:22:07 UTC
Created attachment 1951787 [details]
File: exploitable

Comment 10 kabaem.chris+redhatbugzilla 2023-03-19 08:22:09 UTC
Created attachment 1951788 [details]
File: cpuinfo

Comment 11 kabaem.chris+redhatbugzilla 2023-03-19 08:22:10 UTC
Created attachment 1951789 [details]
File: maps

Comment 12 kabaem.chris+redhatbugzilla 2023-03-19 08:22:11 UTC
Created attachment 1951790 [details]
File: proc_pid_status

Comment 13 Phil Hale 2023-04-27 20:01:18 UTC
I run 4 x monitors off of [AMD/ATI] Oland [Radeon HD 8570 / R5 430 OEM / R7 240/340 / Radeon 520 OEM] cards.  Periodically two of the monitors will "loose signal" and go into sleep mode and not wake up.  I then launch the Displays Configuration tool and attempt to "wake them up" by switching the monitors in question to a different resolution.  Doing that today caused the Displays configuration tool to crash.  I had to remote into the box and do a reboot.


reporter:       libreport-2.17.9
journald_cursor: s=54c9b106cb674be5a6d1825f99794984;i=e5885f;b=959daf6c909544aab8434a9dc8a25c65;m=617b61bba;t=5fa56ab4b8b99;x=387192c80dd2d270
uid:            1000
executable:     /usr/bin/gnome-control-center
cmdline:        /usr/bin/gnome-control-center display
kernel:         6.2.12-300.fc38.x86_64
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-gnome-gnome\x2ddisplay\x2dpanel-84446.scope
type:           CCpp
package:        gnome-control-center-44.1-1.fc38
crash_function: _gtk_widget_is_sensitive
rootdir:        /
runlevel:       N 5
backtrace_rating: 4
reason:         gnome-control-center killed by SIGSEGV
comment:        I run 4 x monitors off of [AMD/ATI] Oland [Radeon HD 8570 / R5 430 OEM / R7 240/340 / Radeon 520 OEM] cards.  Periodically two of the monitors will "loose signal" and go into sleep mode and not wake up.  I then launch the Displays Configuration tool and attempt to "wake them up" by switching the monitors in question to a different resolution.  Doing that today caused the Displays configuration tool to crash.  I had to remote into the box and do a reboot.

Comment 14 Thomas Jungblut 2023-07-04 10:12:44 UTC
freshly installed fedora 38, browsing in the settings app causes it to crash


reporter:       libreport-2.17.9
type:           CCpp
reason:         gnome-control-center killed by SIGSEGV
journald_cursor: s=529e37a011134c8c87b5a1c27f3548b3;i=e34;b=90edebb666304241b915ab73ad3c23a1;m=c331100;t=5ffa65a6e4082;x=e9a449f7cf995596
executable:     /usr/bin/gnome-control-center
cmdline:        /usr/bin/gnome-control-center
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-gnome-org.gnome.Settings-4395.scope
rootdir:        /
uid:            1000
kernel:         6.2.9-300.fc38.x86_64
package:        gnome-control-center-44.0-1.fc38
runlevel:       N 5
dso_list:       /usr/bin/gnome-control-center gnome-control-center-44.0-1.fc38.x86_64 (Fedora Project) 1681422439
backtrace_rating: 4
crash_function: _gtk_widget_is_sensitive
comment:        freshly installed fedora 38, browsing in the settings app causes it to crash

Comment 15 Victor Torres 2023-07-08 13:01:15 UTC
se conectó una pantalla a la computadora, el mouse se quedó en la pantalla uno (externo) y no pasaba a la aplicación de configuracion


reporter:       libreport-2.17.11
executable:     /usr/bin/gnome-control-center
cmdline:        /usr/bin/gnome-control-center display
type:           CCpp
comment:        se conectó una pantalla a la computadora, el mouse se quedó en la pantalla uno (externo) y no pasaba a la aplicación de configuracion
kernel:         6.3.8-200.fc38.x86_64
runlevel:       N 5
journald_cursor: s=9770024c3d444cec8f05121b27760db9;i=237b5;b=487293341207436298a3cb6bdd4c7e1e;m=11d9824c0;t=5ffdb86fa7b31;x=1d771d238796bd15
rootdir:        /
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-org.gnome.Settings.SearchProvider
uid:            1000
reason:         gnome-control-center killed by SIGSEGV
package:        gnome-control-center-44.3-1.fc38
backtrace_rating: 4
crash_function: _gtk_widget_is_sensitive

Comment 16 Tim Kane 2023-07-16 06:07:17 UTC
I don't remember it happening


reporter:       libreport-2.17.11
kernel:         6.3.12-200.fc38.x86_64
backtrace_rating: 4
runlevel:       N 5
journald_cursor: s=7fadfc0ed0f746fbb6d69d52d1ee2973;i=42b43;b=a8094d45070a4dd1abe23bf9c2696ba4;m=3e91b47;t=600818e49bc12;x=16880ad235544d03
reason:         gnome-control-center killed by SIGSEGV
package:        gnome-control-center-44.3-1.fc38
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-gnome-gnome\x2dpower\x2dpanel-4285.scope
uid:            1000
rootdir:        /
crash_function: _gtk_widget_is_sensitive
comment:        I don't remember it happening
cmdline:        /usr/bin/gnome-control-center power
executable:     /usr/bin/gnome-control-center
type:           CCpp

Comment 17 Vincent Gerris 2023-09-06 14:16:24 UTC
run chrome, run meet, share screen. wait - will take a while usually, like 5-10 minutes.


reporter:       libreport-2.17.11
type:           CCpp
reason:         gnome-control-center killed by SIGSEGV
journald_cursor: s=479e1f92ecd545b4ac4bdddac49ab65c;i=1ff2e5;b=c8823e8edce54d30a21fe57145962309;m=3957dbe0;t=604200f713245;x=7856b03ce4434732
executable:     /usr/bin/gnome-control-center
cmdline:        /usr/bin/gnome-control-center wifi
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-gnome-gnome\x2dwifi\x2dpanel-24192.scope
rootdir:        /
uid:            1000
kernel:         6.4.12-200.fc38.x86_64
package:        gnome-control-center-44.3-1.fc38
runlevel:       N 5
dso_list:       /usr/bin/gnome-control-center gnome-control-center-44.3-1.fc38.x86_64 (Fedora Project) 1691995520
backtrace_rating: 4
crash_function: _gtk_widget_is_sensitive
comment:        run chrome, run meet, share screen. wait - will take a while usually, like 5-10 minutes.

Comment 18 Steevithak 2023-09-29 16:37:30 UTC
1. Clicked the upper right system status bar tray to get the settings menu
2. Clicked the gear icon to open settings program
3. Clicked Power to get power settings
4. Clicked Screen Blank so I increase or turn off auto screen blank
Gnome desktop froze, after a few seconds setting program vanished
Gnome desktop starting working again
Problem report popup appeared


reporter:       libreport-2.17.11
type:           CCpp
reason:         gnome-control-center killed by SIGSEGV
journald_cursor: s=b6855a36d6424a81a84ee1564aabf9d8;i=6b49a;b=9d877ff4f6ca4b3d86b5c5d6a32fc4f9;m=22cbd029a;t=60681e74055f8;x=45db8df165b22022
executable:     /usr/bin/gnome-control-center
cmdline:        /usr/bin/gnome-control-center
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-gnome-org.gnome.Settings-11238.scope
rootdir:        /
uid:            1000
kernel:         6.5.5-200.fc38.x86_64
package:        gnome-control-center-44.3-1.fc38
runlevel:       N 5
backtrace_rating: 4
crash_function: _gtk_widget_is_sensitive

Comment 19 breier 2023-10-20 10:18:47 UTC
I opened "printers" from global search, 2 seconds later I realised it was not what I wanted so I pressed ESC.
Half a second later I realised ESC should not close the Window so I proceeded to press Alt+F4, but as soon as I pressed Alt the application crashed.


reporter:       libreport-2.17.11
type:           CCpp
reason:         gnome-control-center killed by SIGSEGV
journald_cursor: s=246cbd0750484ef9bb8fb18f461478e7;i=13f37d;b=170e8ba9fa9a4e469ff8b92a1cc33816;m=1bd33a7de0;t=6082311852770;x=ba7cac6cbe90cf14
executable:     /usr/bin/gnome-control-center
cmdline:        /usr/bin/gnome-control-center printers
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-org.gnome.Settings.SearchProvider
rootdir:        /
uid:            1000
kernel:         6.5.6-200.fc38.x86_64
package:        gnome-control-center-44.3-1.fc38
runlevel:       N 5
dso_list:       /usr/bin/gnome-control-center gnome-control-center-44.3-1.fc38.x86_64 (Fedora Project) 1692006252
backtrace_rating: 4
crash_function: _gtk_widget_is_sensitive

Comment 20 Aoife Moloney 2024-05-07 16:01:15 UTC
This message is a reminder that Fedora Linux 38 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21.
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
'version' of '38'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 38 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 21 Fedora Admin user for bugzilla script actions 2024-05-07 16:01:21 UTC
This component is maintained by the GNOME project. Issues with it should be reported directly to GNOME at https://gitlab.gnome.org/GNOME/.

This issue should only be kept open if it:

1. Relates to Fedora packaging or integration with other Fedora components
2. Is required for Fedora release processes, such as blocker bugs and freeze exceptions

If this issue isn't needed for either of these two reasons, please:

 * create an issue with GNOME
 * add a link to the GNOME issue here
 * close this issue as CLOSED/UPSTREAM

Thank you!

Comment 22 Aoife Moloney 2024-05-21 14:32:18 UTC
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

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.