| View previous topic :: View next topic |
| Author |
Message |
brendlefly62
Apprentice
Joined: 19 Dec 2009
Posts: 156
|
 Posted: Sat Aug 17, 2024 10:37 pm Post subject: [solved] startx and wayland dbus-launch ok, but sddm crashes |
 |
|
I've seen several posts that start with similar symptoms -- I get good Plasma sessions started with either x11 via cmdline startx or wayland via cmdline dbus-launch as outlined below and in wgetpaste info linked at the bottom of this OP,
but sddm crashes when I try to boot into that display manager in the default runlevel -- (error summary: Failed to take control of "/dev/tty1", more below) --
Here are a couple of the threads I reviewed, but those fixes did not apply to my situation. Advice?
https://forums.gentoo.org/viewtopic-p-8826208.html?sid=6f6d51ac8036b6e5b5567a142a05f427
https://forums.gentoo.org/viewtopic-p-8836059.html?sid=aa060205b198a8f3b7e322dcc22f63d5
I recently got a nucbox based on intel's N97 cpu, and I've been working to set it up as stable plasma desktop
| Code: | Operating System: Gentoo Linux 2.15
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.116.0
Qt Version: 5.15.14
Kernel Version: 6.6.38-gentoo-x86_64-joetoo (64-bit)
Graphics Platform: X11 ##[when started with "$ startx" and ~/.xinitrc contains "exec dbus-launch --exit-with-session startplasma-x11"
Graphics Platform: Wayland ##[when started with "$ dbus-launch --exit-with-session startplasma-wayland"
Processors: 4 × Intel® N97
Memory: 11.4 GiB of RAM
Graphics Processor: Mesa Intel® Graphics |
| Code: | # eselect profile list | grep '*'
[27] default/linux/amd64/23.0/desktop/plasma (stable) *
# grep -i keywords /etc/portage/make.conf
ACCEPT_KEYWORDS="amd64"
|
And I have stable kde-plasma/plasma-meta installed, but I've been struggling to get it running right when launched by the sddm display-manager | Code: | # eix plasma-meta
[I] kde-plasma/plasma-meta
Available versions:
(5) 5.27.11-r1{gpkg:2}
(6) ~6.1.4
...
Installed versions: 5.27.11-r1(5){gpkg:2}(12:30:29 PM 08/12/2024)(bluetooth browser-integration colord crash-handler crypt cups desktop-portal discover display-manager elogind grub gtk handbook kwallet legacy-systray pulseaudio sddm smart wallpapers -accessibility -firewall -flatpak -networkmanager -plymouth -sdk -systemd -thunderbolt) |
After validating Gentoo wiki articles including
https://wiki.gentoo.org/wiki/Desktop_environment
https://wiki.gentoo.org/wiki/KDE
https://wiki.gentoo.org/wiki/Intel#Kernel
https://wiki.gentoo.org/wiki/X_server
I think I have my kernel set up as advised, but every time I log in, sddm's greeter takes about 40 sec to get the session started, and that lasts about one minute before it crashes...
| Code: | $ grep EE /var/log/sddm.log
[16:42:34.300] (EE) HELPER: Failed to take control of "/dev/tty1" ("root"): Operation not permitted |
I decided to go way back to basics and validate as much as possible, like I used to do years ago, with --
https://wiki.gentoo.org/wiki/Xorg/Guide
I got twm and xterm installed and got a good graphical session running. So I moved on to try
-- plasma(x11) session works with startx ~/.xinitrc contains | Code: | | exec dbus-launch --exit-with-session startplasma-x11 |
and this works
-- plasma(wayland) started from the cmdline with | Code: | | dbus-launch --exit-with-session startplasma-wayland |
and this also works
So, I have tried adding display-manager back into my default runlevel -- but it still keeps crashing with the error above. I've tried choosing Plasma(x11) and Plasma(wayland) sessions when entering user's password on sddm greeter -- but both crash. I have not tried other display-manager options. I have sddm working on two other ~amd64 desktops running Plasma 6.
Here is /etc/conf.d/display-manager
| Code: | # cat /etc/conf.d/display-manager
# We always try and start the DM on a static VT. The various DMs normally
# default to using VT7. If you wish to use the display-manager init
# script, then you should ensure that the VT checked is the same VT your
# DM wants to use.
# We do this check to ensure that you haven't accidentally configured
# something to run on the VT in your /etc/inittab file so that
# you don't get a dead keyboard.
CHECKVT=7
# What display manager do you use ?
# [ xdm | greetd | gdm | sddm | gpe | lightdm | entrance ]
# NOTE: If this is set in /etc/rc.conf, that setting will override this one.
#DISPLAYMANAGER="xdm"
DISPLAYMANAGER="sddm"
rc_need="elogind" |
I've tried both plasma(x11) and plasma(wayland) choices from the sddm greeter -- but both crash.
elogind is in the default runlevel and I added rc_need="elogind" to /etc/conf.d/display-manager ...
I also re-emerged xorg-server with suid and tried the plasma(x11) session again ... no joy.
Here is /etc/X11/xorg.conf.d/20-modesetting.conf https://paste.gentoo.zip/ctM0ZgI0
Here is /var/log/sddm.log https://paste.gentoo.zip/PB7DwJqI
Here is the output of $ emerge --info https://paste.gentoo.zip/kOwQPyr7
Last edited by brendlefly62 on Tue Jan 28, 2025 11:30 pm; edited 1 time in total |
|
| Back to top |
|
 |
alamahant
Advocate
Joined: 23 Mar 2019
Posts: 3948
|
| Posted: Sun Aug 18, 2024 9:35 am Post subject: |
|
|
Two options:
Either make sure elogind is enabled @boot and running or rebuild xorg-server with USE="suid"
Its all about rootless X.
Also please remove
from display-manager file in /etc/conf.d
Not really necessary.
I am not sure about wayland but I guess you need elogind.
_________________
 |
|
| Back to top |
|
|
brendlefly62
Apprentice
Joined: 19 Dec 2009
Posts: 156
|
| Posted: Sun Aug 18, 2024 11:56 am Post subject: |
|
|
Thanks, alamahant.
Since you said "either/or," I assume you mean "not both" - I guess I'd prefer "rootless X" so, since I already had xorg-server built with suid, I have now recompiled xorg-server with USE= -suid, and as you advised, I removed the rc_need line from /etc/conf.d/display-manager.
I interpret "elogind enabled @boot" to be satisfied where I have it in the default runlevel. (In this post, https://forums.gentoo.org/viewtopic-p-8826208.html?sid=6f6d51ac8036b6e5b5567a142a05f427 NeddySeagoon had said the boot runlevel is too early).
However, with these changes, the display-manager still crashes. 
More specifically --
* I see the normal boot proceeding in console output
* then I get the sddm greeter full-screen graphical dialog with a box for my user's password (and I have "Plasma(x11)" selected in the lower left corner) -- I enter the user's password in the box
* then the sddm greeter disappears and I can see a regular text login prompt on the tty console (this stays this way for about 45 sec) and then I get the breeze splash screen with KDE logo and spinning gear
* then the full-screen graphical desktop pops in and I can use it for about 60 seconds, and then it crashes, leaving a black screen with single under-score cursor in the upper left
The full sddm.log is in the wgetpaste link below, the error message is (EE) HELPER: Failed to take control of "/dev/tty1" ("root"): Operation not permitted
I notice that if, during the 45sec pause at tty screen login prompt, I log in as user, the crash error one minute after graphics come up looks like this -- (EE) HELPER: Failed to take control of "/dev/tty1" ("<myusername>"): Operation not permitted
| Code: | mynucbox /var/log # grep -i '(ee)' sddm.log
[07:32:56.016] (EE) HELPER: Failed to take control of "/dev/tty1" ("root"): Operation not permitted
[07:32:56.043] (EE) HELPER: Failed to take control of "/dev/tty1" ("root"): Operation not permitted
[07:32:56.111] (EE) HELPER: Failed to take control of "/dev/tty1" ("root"): Operation not permitted
[07:32:56.189] (EE) HELPER: Failed to take control of "/dev/tty1" ("root"): Operation not permitted
[07:32:56.271] (EE) HELPER: Failed to take control of "/dev/tty1" ("root"): Operation not permitted
[07:32:56.354] (EE) HELPER: Failed to take control of "/dev/tty1" ("root"): Operation not permitted
[07:40:01.396] (EE) HELPER: Failed to take control of "/dev/tty1" ("joe"): Operation not permitted
[07:40:01.418] (EE) HELPER: Failed to take control of "/dev/tty1" ("joe"): Operation not permitted
[07:40:01.483] (EE) HELPER: Failed to take control of "/dev/tty1" ("joe"): Operation not permitted
[07:40:01.554] (EE) HELPER: Failed to take control of "/dev/tty1" ("joe"): Operation not permitted
[07:40:01.616] (EE) HELPER: Failed to take control of "/dev/tty1" ("joe"): Operation not permitted
[07:40:01.684] (EE) HELPER: Failed to take control of "/dev/tty1" ("joe"): Operation not permitted |
Here is the full sddm.log -- https://paste.gentoo.zip/W11VkRT1
Here is rc-status --
| Code: | # rc-status --all
Runlevel: sysinit
devfs [ started ]
sysfs [ started ]
cgroups [ started ]
kmod-static-nodes [ started ]
systemd-tmpfiles-setup-dev [ started ]
dmesg [ started ]
udev [ started ]
udev-trigger [ started ]
Runlevel: default
dbus [ started ]
net.wlan0 [ started ]
sysklogd [ started ]
dhcpcd [ started ]
mysql [ started ]
net.eth0 [ started ]
netmount [ started ]
php-fpm [ started ]
chronyd [ started ]
distccd [ started ]
sshd [ started ]
apache2 [ started ]
cronie [ started ]
gpm [ started ]
elogind [ started ]
display-manager [ crashed ] <====
rsyncd [ started ]
local [ started ]
Runlevel: shutdown
savecache [ stopped ]
killprocs [ stopped ]
mount-ro [ stopped ]
Runlevel: boot
termencoding [ started ]
keymaps [ started ]
hwclock [ started ]
modules [ started ]
fsck [ started ]
root [ started ]
mtab [ started ]
swap [ started ]
localmount [ started ]
systemd-tmpfiles-setup [ started ]
sysctl [ started ]
bootmisc [ started ]
save-keymaps [ started ]
procfs [ started ]
binfmt [ started ]
loopback [ started ]
save-termencoding [ started ]
seedrng [ started ]
hostname [ started ]
Runlevel: nonetwork
local [ started ]
Dynamic Runlevel: hotplugged
Dynamic Runlevel: needed/wanted
display-manager-setup [ started ]
Dynamic Runlevel: manual
|
|
|
| Back to top |
|
|
alamahant
Advocate
Joined: 23 Mar 2019
Posts: 3948
|
| Posted: Sun Aug 18, 2024 1:25 pm Post subject: |
|
|
Check if downgrading to
| Code: |
emerge -1av =x11-misc/sddm-0.18.1-r8
|
helps.
SDDM keeps trying to use /dev/tty1 whereas it should have picked another available one.
_________________
|
|
| Back to top |
|
|
brendlefly62
Apprentice
Joined: 19 Dec 2009
Posts: 156
|
| Posted: Mon Aug 19, 2024 2:39 pm Post subject: |
|
|
| Thanks, alamahant. I will try that when I return from travel next week. |
|
| Back to top |
|
|
majoron
Apprentice
Joined: 12 Oct 2005
Posts: 243
Location: Frankfurt
|
| Posted: Mon Jan 27, 2025 12:59 pm Post subject: |
|
|
I have a similar problem. Same error.
Also the plasma desktop starts manually with
| Code: | | dbus-run-session startplasma-wayland |
I wanted to try sddm-0.18 but is no longer in portage (I only see 0.21). Before doing archaeological work to find the old ebuild, did that work?
_________________
Computers are like air conditioners, they stop working properly if you open Windows |
|
| Back to top |
|
|
brendlefly62
Apprentice
Joined: 19 Dec 2009
Posts: 156
|
| Posted: Tue Jan 28, 2025 11:29 pm Post subject: |
|
|
Hi, majoron. At the time, I was away, and by the time I returned to the project, I also could no longer find sddm-0.18 available. So I did not get to try that.
On the system I described in August, I built sddm-0.21 with USE=" X elogind" and I built xorg-server-21.1.15 with USE="elogind ... -suid" and I have elogind-255.5-r1 in the boot runlevel (contrary to advice from NeddySeagoon, but as advised by alamahant) -- and this works.
However on a system I built more recently, I also compiled sddm-0.21 with USE=" X elogind" and xorg-server-21.1.15 with USE="elogind ... -suid" but while elogind-255.5-r1 is installed, I do not have elogind assigned to any runlevel - and this also works. I am not certain whether to credit the upgrade of xorg-server or sddm.
Thanks for bringing me back to this. I'll go back and mark the thread [solved] |
|
| Back to top |
|
|
majoron
Apprentice
Joined: 12 Oct 2005
Posts: 243
Location: Frankfurt
|
| Posted: Wed Jan 29, 2025 1:49 pm Post subject: |
|
|
brendlefly62,
thank you for the feedback.
I have the same packages with the same versions and use flags, but in my case it does not work.
_________________
Computers are like air conditioners, they stop working properly if you open Windows |
|
| Back to top |
|
|
brendlefly62
Apprentice
Joined: 19 Dec 2009
Posts: 156
|
|
| Back to top |
|
|
majoron
Apprentice
Joined: 12 Oct 2005
Posts: 243
Location: Frankfurt
|
| Posted: Wed Jan 29, 2025 3:41 pm Post subject: |
|
|
Thank you for the pointers.
I think I went thru all that. But of course I could have missed some thing.
My system is a Lenovo X1 carbon gen 12. It has an Intel Core Ultra 7 165U and Iris Arc Graphics.
In the first place I missed a proper kernel config for the Xe driver. It is now solved but I need kernel 6.10.12 (I couldn't find any other valid version in the repo).
I also tried with Lightdm and it fails similarly to sddm what makes me puzzled. Maybe is elogind?
I'll review the wiki articles again anyway.
_________________
Computers are like air conditioners, they stop working properly if you open Windows |
|
| Back to top |
|
|
|
Desktop Environments
