El 19/7/25 a las 2:20, Philip Webb escribió:
use strace to see where it fails (for example strace -f -o /tmp/output bash -c startx)A few weeks ago, a weekly update resulted in KDE failing to start ; as it needed to be updated anyway, I have been using Fluxbox instead. During the past few days, I removed all the old KDE pkgs, did an update of all the Qt pkgs which were installed & re-installed all the previous KDE pkgs in their new versions, so that I now have Qt 5.15.17 + 6.9.1 , KDE Frameworks 6.13.0 , Plasma 6.3.5 + Apps 25.04.2 .I use OpenRC with 'startx' + '.xinitrc' : for Fluxbox, the latter is simply 'startfluxbox' , for KDE, it's 'exec dbus-launch --exit-with-session startplasma-x11', which worked with the old version of KDE & is recommended in Gentoo Wiki. Now when I enter 'startx', I get a black screen + a movable mouse-pointer, but nothing else, & have to restart the machine & return to Fluxbox. There is an error msg : "$DISPLAY is not set or can't connect to server". Gentoo Wiki seems to recommend using 'sddm' instead of 'startx', which it describes at "the old method". I have 'elogind' 2.55.17 installed. I've looked at the logs in /var/log , but can't see anything relevant. Can anyone suggest what may have gone wrong ? Might it be advisable to use 'sddm' in future ? ========================,,============================================ SUPPORT ___________//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT `-O----------O---' purslowatcadotinterdotnet
OpenPGP_0x57E64E0B7FC3BEDF.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
