Ask Your Question
0

Grub Customizer will from CLI but not GUI

asked 2016-12-05 02:27:15 -0500

graceful gravatar image

updated 2016-12-05 02:28:02 -0500

I'm able to get grub-customizer to lauch from CLI but not GUI.

edit retag flag offensive close merge delete

Comments

Same here: I installed it from the Software Center, but neither the CLI nor the GUI launch successfully. I can only get as far as the admin authentication prompt.

CLI stdout:

No protocol specified
Unable to init server: Could not connect: Connection refused

(grub-customizer:25172): Gtk-WARNING **: cannot open display: :0
e-inquirer gravatar imagee-inquirer ( 2016-12-05 23:30:00 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2016-12-06 00:39:52 -0500

graceful gravatar image

updated 2016-12-06 00:46:52 -0500

Yup,

Apparently, the Wayland stupidity-policy er I mean security-policy won't allow any gui application to have root privileges. I gave-up on Wayland and dropped back to X at the greeter, since this DESTROYED my workflow.

https://bugzilla.redhat.com/show_bug....

The above bug report suggested the following:

John Dulaney 2015-10-30 11:31:38 EDT

Policy decisions aside, if the decision to go with letting gui applications have root access is made, then I think that the fix should be made in libwayland itself, and not left up to the individual compositors. It seems that this would be something you would want to have across the board, no matter if you're running Gnome, Weston, or (like I am), a tiling compositor that isn't in Fedora (yet).


I think this is the sano fix since it solves the problem at a common bottleneck, instead of creating two problems that have to be solved seperately.

edit flag offensive delete link more

Question Tools

1 follower

Stats

Asked: 2016-12-05 02:27:15 -0500

Seen: 186 times

Last updated: Dec 06 '16