Bug 1645855 - gnome-control-center dumps core
Summary: gnome-control-center dumps core
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-control-center
Version: 31
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Pete Walter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-04 12:10 UTC by Patrick O'Callaghan
Modified: 2020-04-08 14:26 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-27 23:12:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Patrick O'Callaghan 2018-11-04 12:10:27 UTC
Description of problem:
On running gnome-control-center under KDE, I get a core dump immediately.

Version-Release number of selected component (if applicable):
gnome-control-center-3.30.2-1.fc29.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Run gnome-control-center under KDE
2.Immediate core dump
3.

Actual results:
Core dump

Expected results:
Successful run

Additional info:
Console output:
$ gnome-control-center 

(gnome-control-center:12420): dbind-WARNING **: 12:02:42.073: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
failed to open /usr/lib64/dri/hybrid_drv_video.so
Not using hybrid_drv_video.so
failed to open /usr/lib64/dri/hybrid_drv_video.so
Not using hybrid_drv_video.so
**
ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid)
Aborted (core dumped)

If run under sudo:
$ sudo gnome-control-center 
failed to open /usr/lib64/dri/hybrid_drv_video.so
Not using hybrid_drv_video.so
failed to open /usr/lib64/dri/hybrid_drv_video.so
Not using hybrid_drv_video.so
sys:1: Warning: cannot register existing type 'GstQtQuick2VideoSink'
sys:1: Warning: g_type_add_interface_static: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed
sys:1: Warning: g_once_init_leave: assertion 'result != 0' failed

(gst-plugin-scanner:12771): GStreamer-CRITICAL **: 12:06:29.782: gst_element_register: assertion 'g_type_is_a (type, GST_TYPE_ELEMENT)' failed
**
ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid)
Aborted

Comment 1 josef radinger 2018-11-17 14:20:50 UTC
the same here with xfce


[cheese@localhost ~]$ gnome-control-center
**
ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid)
Aborted (core dumped)

and i assume that this is what disales online-accounts in evolution under xfce, too

Comment 2 Dennis Gilmore 2019-03-07 19:15:14 UTC
trying to adjust online accounts in Xfce I get 
$ gnome-control-center online-accounts
**
ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid)
Aborted (core dumped)

this is in Fedora 29 and Fedora 30

Comment 3 josef radinger 2019-06-28 10:08:35 UTC
still happens with fedora30:
gnome-control-center 

**
ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid)
Aborted (core dumped)

or

gnome-control-center online-accounts
**
ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid)
Aborted (core dumped)

Comment 4 josef radinger 2019-06-28 10:19:09 UTC
i can start gnome-control-center, when i do the following:

XDG_CURRENT_DESKTOP=GNOME gnome-control-center

Comment 5 Patrick O'Callaghan 2019-06-28 10:28:13 UTC
(In reply to josef radinger from comment #4)
> i can start gnome-control-center, when i do the following:
> 
> XDG_CURRENT_DESKTOP=GNOME gnome-control-center

Yes, I actually noticed this a few months ago but neglected to update the report. However I would class this as a workaround. The bug as such still exists in gnome-control-center-3.32.2-1.fc30.x86_64.

Comment 6 Ben Cotton 2019-10-31 18:57:36 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-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 '29'.

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 29 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 7 Ben Cotton 2019-11-27 23:12:49 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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 8 Patrick O'Callaghan 2020-04-01 15:36:35 UTC
(In reply to Ben Cotton from comment #7)
> Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.

Bug is still present in F31. Workaround of setting 
XDG_CURRENT_DESKTOP=GNOME still works.

Comment 9 Antoine Martin 2020-04-08 14:26:58 UTC
> XDG_CURRENT_DESKTOP=GNOME still works.
FWIW: when running inside an xpra session, the workaround does not help, it still crashes hard.


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