On Sun, 2018-11-04 at 17:14 -0800, Samuel Sieb wrote:
> On 11/4/18 10:02 AM, Patrick O'Callaghan wrote:
> > I always assumed that the only reason for g-c-c to exist was so that
> > users of other DEs could access Gnome settings. If it can only run
> > under Gnome that rather defeats the purpose I w
On 11/4/18 10:02 AM, Patrick O'Callaghan wrote:
I always assumed that the only reason for g-c-c to exist was so that
users of other DEs could access Gnome settings. If it can only run
under Gnome that rather defeats the purpose I would think.
I'm pretty sure its primary purpose is to control th
On Sun, 2018-11-04 at 08:39 -0500, Tom Horsley wrote:
> On Sun, 04 Nov 2018 12:11:08 +
> Patrick O'Callaghan wrote:
>
> > I tried to run gnome-control-center under KDE to look at some Gnome-
> > related settings, and got this:
> >
> > $ gnome-control-center
> >
> > ERROR:../shell/cc-shell-m
On Sun, 04 Nov 2018 12:11:08 +
Patrick O'Callaghan wrote:
> I tried to run gnome-control-center under KDE to look at some Gnome-
> related settings, and got this:
>
> $ gnome-control-center
>
> ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility:
> assertion failed: (va
I tried to run gnome-control-center under KDE to look at some Gnome-
related settings, and got this:
$ 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 appli
