Summary: | kde-plasma/plasma-workspace-5.11.5 failure to login | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Norman Back <gentoo3> |
Component: | Current packages | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED INVALID | ||
Severity: | major | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Norman Back
2018-01-23 18:22:11 UTC
Please paste the exact content of your ~/.xinitrc. startkde alone is not enough. https://wiki.gentoo.org/wiki/KDE#No_display_manager cat ~/.xinitrc cat: /home/norman/.xinitrc: No such file or directory Does that mean you tyke startkde all the time? You've never had a proper user session. No this was a working system before the upgrade. (If reverted to a backup which I'm now using). I login using sddm-greeter. Regarding ~/.xinitrc, the wiki says "The following solution is limited to ConsoleKit" I'm using systemd. The working backup systems xorg-session.log contains: startkde: Starting up... 2018-01-23T17:58:52 Checking update-file '/usr/share/kconf_update/disable_kmix.upd' for new updates 2018-01-23T17:58:52 disable_kmix.upd: Found new update 'PlasmaVolume_DisableKMixAutostart' 2018-01-23T17:58:52 disable_kmix.upd: Skipping update 'PlasmaVolume_DisableKMixAutostart' 2018-01-23T17:58:52 Checking update-file '/usr/share/kconf_update/fonts_akregator.upd' for new updates 2018-01-23T17:58:52 fonts_akregator.upd: Found new update 'Plasma_Fonts_Akregator' 2018-01-23T17:58:52 fonts_akregator.upd: Skipping update 'Plasma_Fonts_Akregator' 2018-01-23T17:58:52 fonts_akregator.upd: File 'akregatorrc' does not exist or empty, skipping 2018-01-23T17:58:52 Checking update-file '/usr/share/kconf_update/fonts_global.upd' for new updates 2018-01-23T17:58:52 Checking update-file '/usr/share/kconf_update/fonts_kate.upd' for new updates 2018-01-23T17:58:52 fonts_kate.upd: Found new update 'Plasma_Fonts_Kate' 2018-01-23T17:58:52 fonts_kate.upd: Skipping update 'Plasma_Fonts_Kate' 2018-01-23T17:58:52 fonts_kate.upd: File 'kateschemarc' does not exist or empty, skipping 2018-01-23T17:58:52 Checking update-file '/usr/share/kconf_update/gtkbreeze5.5.upd' for new updates 2018-01-23T17:58:52 Checking update-file '/usr/share/kconf_update/katomic-levelset.upd' for new updates 2018-01-23T17:58:52 Checking update-file '/usr/share/kconf_update/kcalcrc.upd' for new updates 2018-01-23T17:58:52 Checking update-file '/usr/share/kconf_update/kde4breeze.upd' for new updates 2018-01-23T17:58:52 Checking update-file '/usr/share/kconf_update/kgthemeprovider-migration.upd' for new updates 2018-01-23T17:58:52 Checking update-file '/usr/share/kconf_update/klickety.upd' for new updates 2018-01-23T17:58:52 Checking update-file '/usr/share/kconf_update/knavalbattle.upd' for new updates 2018-01-23T17:58:52 Checking update-file '/usr/share/kconf_update/krdb_libpathwipe.upd' for new updates 2018-01-23T17:58:52 Checking update-file '/usr/share/kconf_update/krunnerplugins.upd' for new updates 2018-01-23T17:58:52 Checking update-file '/usr/share/kconf_update/kscreenlocker.upd' for new updates 2018-01-23T17:58:52 kscreenlocker.upd: Found new update '0.1-autolock' 2018-01-23T17:58:52 kscreenlocker.upd: Skipping update '0.1-autolock' 2018-01-23T17:58:52 Checking update-file '/usr/share/kconf_update/okular.upd' for new updates 2018/01/23 17:58:53 socat[2873] E connect(5, AF=1 "/run/user/1000/kwallet5.socket", 32): No such file or directory OK.
I've restored from backup to a time before the latest stabilization of kde-plasma/plasma-workspace-5.11.5 and associated kde packages.
Added some entries to /etc/portage/package.mask
>=kde-plasma/plasma-workspace-wallpapers-5.11
>=kde-plasma/kwallet-pam-5.11
>=kde-plasma/libkscreen-5.11
>=kde-plasma/breeze-gtk-5.11
>=kde-plasma/kwayland-integration-5.11
>=kde-plasma/kdecoration-5.11
>=kde-plasma/polkit-kde-agent-5.11
>=kde-plasma/kgamma-5.11
>=kde-plasma/ksshaskpass-5.11
>=kde-plasma/kwrited-5.11
>=kde-plasma/kactivitymanagerd-5.11
>=kde-plasma/user-manager-5.11
>=kde-plasma/plasma-pa-5.11
>=kde-plasma/milou-5.11
>=kde-plasma/kde-cli-tools-5.11
>=kde-plasma/plasma-sdk-5.11
>=kde-plasma/kinfocenter-5.11
>=kde-plasma/kscreen-5.11
>=kde-plasma/kde-gtk-config-5.11
>=kde-plasma/oxygen-5.11
>=kde-plasma/kscreenlocker-5.11
>=kde-plasma/sddm-kcm-5.11
>=kde-plasma/breeze-5.11
>=kde-plasma/bluedevil-5.11
>=kde-plasma/systemsettings-5.11
>=kde-plasma/plasma-integration-5.11
>=kde-plasma/kwin-5.11
>=kde-plasma/libksysguard-5.11
>=kde-plasma/ksysguard-5.11
>=kde-plasma/plasma-workspace-5.11
>=kde-plasma/khotkeys-5.11
>=kde-plasma/powerdevil-5.11
>=kde-plasma/plasma-desktop-5.11
>=kde-plasma/kdeplasma-addons-5.11
>=kde-plasma/kmenuedit-5.11
>=kde-plasma/plasma-meta-5.11
=kde-frameworks/networkmanager-qt-5.40.0-r1
=net-libs/signon-ui-0.15-r1
to prevent then being emerged again.
Then eix-sync, emerge -DuNavt world , reboot and logged in OK.
I would be happy to help pinpoint the specific kde package but need some guidance on the correct approach.
kde-plasma/plasma-workspace-5.11.5 has RDEPEND systemd? ( sys-apps/dbus[user-session] ) but if I enable USE user-session for sys-apps/dbus, emerge -1 sys-apps/dbus in preparation for kde-plasma/plasma-workspace-5.11.5 and reboot (without emerging kde-plasma/plasma-workspace-5.11.5), login fails with "Could not sync environment to dbus" Which USE flags are enabled on sys-auth/pambase? (In reply to Michael Palimaka (kensington) from comment #8) > Which USE flags are enabled on sys-auth/pambase? cracklib nullok sha512 systemd -consolekit -debug -elogind -gnome-keyring -minimal -mktemp -pam_krb5 -pam_ssh -passwdqc -securetty -selinux See also Bug 645680 This issue is now resolved. I had sys-auth/consolekit in the world file. After many searches I eventually found https://forums.gentoo.org/viewtopic-t-1041644-start-0.html After emerge --deselect sys-auth/consolekit emerge --depclean -av removed sys-auth/consolekit I was then able to disable the masks I had set and emerge kde-plasma/plasma-workspace-5.11.5 Maybe enabling the use flag user-session should block sys-auth/consolekit when the systemd use flag is enabled. Thanks for the follow-up. USE=consolekit is masked in systemd profiles, that should be enough to protect users from themselves. Masking consolekit makes not much sense as having it installed does not do any harm by itself - unless it is activated at runtime. Not using the systemd profile will always make you more self-reliant. (In reply to Andreas Sturmlechner from comment #12) > Thanks for the follow-up. USE=consolekit is masked in systemd profiles, that > should be enough to protect users from themselves. Masking consolekit makes > not much sense as having it installed does not do any harm by itself - > unless it is activated at runtime. > > Not using the systemd profile will always make you more self-reliant. I am using the systemd profile, as shown in my emerge --info above. I did not have USE=consolekit anywhere. Consolekit was in my world file (probably a hangover when I migrated from openrc to systemd), so although nothing required it, emerge --depclean did not remove it. |