Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash on start on Wayland #747

Open
jriddell opened this issue Jun 16, 2017 · 6 comments
Open

Crash on start on Wayland #747

jriddell opened this issue Jun 16, 2017 · 6 comments

Comments

@jriddell
Copy link
Member

@jriddell jriddell commented Jun 16, 2017

Using KDE neon Dev Unstable ISO from today Calamares crashes if you try to start it when running a Wayland session.

This is probably because Wayland doesn't like stuff running as root.

@adriaandegroot

This comment has been minimized.

Copy link
Contributor

@adriaandegroot adriaandegroot commented Jun 17, 2017

Wayland's stance "no GUI application may be setuid" is really annoying for applications that need to be (for various reasons) root. pkgexec is not sufficient as a workaround.

This is a workaround:

    sudo touch /etc/foo
    SUDO_EDITOR=konsole sudoedit /etc/foo
    (in resulting konsole) calamares -d

If Wayland continues its no-possible-root stance, then there's not much else to do than either declare Cala X11-only (the easy way out) or start the long and tedious process of moving the bits that need root into helper processes.

@demmm

This comment has been minimized.

Copy link
Contributor

@demmm demmm commented Jun 17, 2017

Calamares has been used in KaOS for about a year now in Wayland sessions, with no issues as reported above. Does the crash occur on starting with pkgexec? Here it is always started with sudo calamares -d

@adriaandegroot

This comment has been minimized.

Copy link
Contributor

@adriaandegroot adriaandegroot commented Jun 19, 2017

@demmm Can you do "sudo xterm" (assuming xterm is installed in your distro)? There has been much discussion about Wayland + setuid-root applications, and the general line is "they won't work." But that's with current(-ish) Wayland.

@jriddell xhost + ; sudo calamares -d does do the trick on that KDE Neon release

@demmm

This comment has been minimized.

Copy link
Contributor

@demmm demmm commented Jun 19, 2017

@adriaandegroot
sudo xtern runs fine in a Wayland session. Just in case needed, latest versions used, Qt 5.9.0, Frameworks 5.35.0, Plasma 5.10.2.

@adriaandegroot adriaandegroot added this to the v3.2.0 milestone Aug 8, 2017
@stikonas

This comment has been minimized.

Copy link
Contributor

@stikonas stikonas commented Aug 15, 2017

You can start root apps on Wayland too. E.g. KDE Partition Manager can successfully run on wayland as it sets the following environmental variables DBUS_SESSION_BUS_ADDRESS, KDE_FULL_SESSION, QT_WAYLAND_FORCE_DPI, QT_QPA_PLATFORM, XDG_RUNTIME_DIR

See https://cgit.kde.org/partitionmanager.git/tree/src/util/guihelpers.cpp#n67 for implementation details.

@abucodonosor

This comment has been minimized.

Copy link
Contributor

@abucodonosor abucodonosor commented Sep 18, 2017

That seems to be sort Distro issues too also ..

@adriaandegroot adriaandegroot modified the milestones: v3.2.0, v3.2.1 May 10, 2018
@adriaandegroot adriaandegroot modified the milestones: v3.2.1, v3.2.2 May 28, 2018
@adriaandegroot adriaandegroot removed this from the v3.2.2 milestone Sep 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.