New installation of Slackware64-Current literally takes 4 to 5 minutes to exit (logout) of session. Happens in Xfce as well as KDE (Plasma5). Anyone with a new install of -Current have the same issue and solved it?

Ok I exaggerated. It only takes about 1 minute but still annoying.

Here is a clue that happens in system console after exiting:
waiting for X server to shut down xfsettingsd: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
(II) Server terminated successfully (0). Closing log file.

Either dbus or policykit related? Some of the output in /var/log/messages:
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activating service name='org.freedesktop.UPower' requested by ':1.117' (uid=0 pid=3871 comm="xfce4-session ") (using servicehelper)
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Successfully activated service 'org.freedesktop.UPower'
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activating service name='org.freedesktop.PolicyKit1' requested by ':1.160' (uid=0 pid=4248 comm="/usr/libexec/upowerd ") (using servicehelper)
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activated service 'org.freedesktop.PolicyKit1' failed: Launch helper exited with unknown return code 127
Dec 29 06:30:43 T460S kernel: [ 2266.462026] traps: upowerd[4248] trap int3 ip:7fac77c06855 sp:7ffe13de3e00 error:0 in libglib-2.0.so.0.6200.4[7fac77bce000+7d000]
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activating service name='org.freedesktop.PolicyKit1' requested by ':1.118' (uid=0 pid=3871 comm="xfce4-session ") (using servicehelper)
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activated service 'org.freedesktop.PolicyKit1' failed: Launch helper exited with unknown return code 127
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activating service name='org.freedesktop.UPower' requested by ':1.117' (uid=0 pid=3871 comm="xfce4-session ") (using servicehelper)
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Successfully activated service 'org.freedesktop.UPower'
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activating service name='org.freedesktop.PolicyKit1' requested by ':1.162' (uid=0 pid=4266 comm="/usr/libexec/upowerd ") (using servicehelper)
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activated service 'org.freedesktop.PolicyKit1' failed: Launch helper exited with unknown return code 127
Dec 29 06:30:43 T460S kernel: [ 2266.508907] traps: upowerd[4266] trap int3 ip:7ffad0e45855 sp:7ffd7f5d02a0 error:0 in libglib-2.0.so.0.6200.4[7ffad0e0d000+7d000]
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activating service name='org.freedesktop.PolicyKit1' requested by ':1.118' (uid=0 pid=3871 comm="xfce4-session ") (using servicehelper)
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activated service 'org.freedesktop.PolicyKit1' failed: Launch helper exited with unknown return code 127
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activating service name='org.freedesktop.UPower' requested by ':1.117' (uid=0 pid=3871 comm="xfce4-session ") (using servicehelper)
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Successfully activated service 'org.freedesktop.UPower'
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activating service name='org.freedesktop.PolicyKit1' requested by ':1.164' (uid=0 pid=4284 comm="/usr/libexec/upowerd ") (using servicehelper)
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activated service 'org.freedesktop.PolicyKit1' failed: Launch helper exited with unknown return code 127
Dec 29 06:30:43 T460S kernel: [ 2266.562858] traps: upowerd[4284] trap int3 ip:7f2a5ac92855 sp:7ffc81af2860 error:0 in libglib-2.0.so.0.6200.4[7f2a5ac5a000+7d000]
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activating service name='org.freedesktop.PolicyKit1' requested by ':1.118' (uid=0 pid=3871 comm="xfce4-session ") (using servicehelper)
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activated service 'org.freedesktop.PolicyKit1' failed: Launch helper exited with unknown return code 127
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activating service name='org.freedesktop.UPower' requested by ':1.117' (uid=0 pid=3871 comm="xfce4-session ") (using servicehelper)
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Successfully activated service 'org.freedesktop.UPower'

Ok I exaggerated. It only takes about 1 minute but still annoying.

Here is a clue that happens in system console after exiting:
waiting for X server to shut down xfsettingsd: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
(II) Server terminated successfully (0). Closing log file.

Either dbus or policykit related? Some of the output in /var/log/messages:
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activating service name='org.freedesktop.UPower' requested by ':1.117' (uid=0 pid=3871 comm="xfce4-session ") (using servicehelper)
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Successfully activated service 'org.freedesktop.UPower'
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activating service name='org.freedesktop.PolicyKit1' requested by ':1.160' (uid=0 pid=4248 comm="/usr/libexec/upowerd ") (using servicehelper)
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activated service 'org.freedesktop.PolicyKit1' failed: Launch helper exited with unknown return code 127
Dec 29 06:30:43 T460S kernel: [ 2266.462026] traps: upowerd[4248] trap int3 ip:7fac77c06855 sp:7ffe13de3e00 error:0 in libglib-2.0.so.0.6200.4[7fac77bce000+7d000]
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activating service name='org.freedesktop.PolicyKit1' requested by ':1.118' (uid=0 pid=3871 comm="xfce4-session ") (using servicehelper)
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activated service 'org.freedesktop.PolicyKit1' failed: Launch helper exited with unknown return code 127
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activating service name='org.freedesktop.UPower' requested by ':1.117' (uid=0 pid=3871 comm="xfce4-session ") (using servicehelper)
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Successfully activated service 'org.freedesktop.UPower'
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activating service name='org.freedesktop.PolicyKit1' requested by ':1.162' (uid=0 pid=4266 comm="/usr/libexec/upowerd ") (using servicehelper)
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activated service 'org.freedesktop.PolicyKit1' failed: Launch helper exited with unknown return code 127
Dec 29 06:30:43 T460S kernel: [ 2266.508907] traps: upowerd[4266] trap int3 ip:7ffad0e45855 sp:7ffd7f5d02a0 error:0 in libglib-2.0.so.0.6200.4[7ffad0e0d000+7d000]
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activating service name='org.freedesktop.PolicyKit1' requested by ':1.118' (uid=0 pid=3871 comm="xfce4-session ") (using servicehelper)
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activated service 'org.freedesktop.PolicyKit1' failed: Launch helper exited with unknown return code 127
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activating service name='org.freedesktop.UPower' requested by ':1.117' (uid=0 pid=3871 comm="xfce4-session ") (using servicehelper)
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Successfully activated service 'org.freedesktop.UPower'
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activating service name='org.freedesktop.PolicyKit1' requested by ':1.164' (uid=0 pid=4284 comm="/usr/libexec/upowerd ") (using servicehelper)
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activated service 'org.freedesktop.PolicyKit1' failed: Launch helper exited with unknown return code 127
Dec 29 06:30:43 T460S kernel: [ 2266.562858] traps: upowerd[4284] trap int3 ip:7f2a5ac92855 sp:7ffc81af2860 error:0 in libglib-2.0.so.0.6200.4[7f2a5ac5a000+7d000]
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activating service name='org.freedesktop.PolicyKit1' requested by ':1.118' (uid=0 pid=3871 comm="xfce4-session ") (using servicehelper)
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activated service 'org.freedesktop.PolicyKit1' failed: Launch helper exited with unknown return code 127
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Activating service name='org.freedesktop.UPower' requested by ':1.117' (uid=0 pid=3871 comm="xfce4-session ") (using servicehelper)
Dec 29 06:30:43 T460S dbus-daemon[1139]: [system] Successfully activated service 'org.freedesktop.UPower'

More clues from the system console when logging out ogf KDE:
aiting for X server to shut down xfsettingsd: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
(II) Server terminated successfully (0). Closing log file.

qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 13319, resource id: 41943889, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 13979, resource id: 10485793, major code: 18 (ChangeProperty), minor code: 0
ksmserver failed to complete logout
kdeinit5: terminate KDE.
klauncher: Exiting on signal 15
klauncher: Exiting on signal 1
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 14200, resource id: 56623111, major code: 15 (QueryTree), minor code: 0
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 14205, resource id: 56623111, major code: 18 (ChangeProperty), minor code: 0
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
bluedevil: Destroyed
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QProcess: Destroyed while process ("ksplashqml") is still running.
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
startkde: Starting up...
startkde: Shutting down...
startkde: Done.
kde.xembedsniproxy: could not register SNI: "The name org.kde.StatusNotifierWatcher was not provided by any .service files"
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
xinit: connection to X server lost

waiting for X server to shut down hp-systray: Fatal IO error: client killed
The X11 connection broke (error 1). Did the X11 server die?
The X11 connection broke (error 1). Did the X11 server die?
The X11 connection broke (error 1). Did the X11 server die?
The X11 connection broke (error 1). Did the X11 server die?
The X11 connection broke (error 1). Did the X11 server die?
The X11 connection broke: I/O error (code 1)
XIO: fatal IO error 4 (Interrupted system call) on X server ":0"
after 97 requests (97 known processed) with 0 events remaining.
The X11 connection broke (error 1). Did the X11 server die?
Application::crashHandler() called with signal 11; recent crashes: 1
malloc_consolidate(): invalid chunk size
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kwin_x11 path = /usr/bin pid = 5392
KCrash: Arguments: /usr/bin/kwin_x11 -session 101e11ae134175000157762776800000014250003_1577630581_593087
The X11 connection broke: I/O error (code 1)
XIO: fatal IO error 2 (No such file or directory) on X server ":0"
after 4708 requests (4684 known processed) with 0 events remaining.
The X11 connection broke: I/O error (code 1)
XIO: fatal IO error 2 (No such file or directory) on X server ":0"
after 4708 requests (4684 known processed) with 0 events remaining.
file:///usr/share/plasma/plasmoids/org.kde.plasma.clipboard/contents/ui/ClipboardPage.qml:107:13: Unable to assign [undefined] to QAbstractItemModel*
(II) Server terminated successfully (0). Closing log file.
The X11 connection broke (error 1). Did the X11 server die?

Have you removed and/or added packages as listed in the change logs since your -current .iso was downloaded?
BTW, shouldn't this topic be in the Slackware Forum?

Thanks for your reply cwizardone.

To answer your questions:
The initial install was with *64-current snapshot on 12-6-19 (kernel version 5.4.2) which was upgraded with Alien Bob's multilib and Plasma5 (December release) packages. My initial struggle was getting a simple User account to authenticate. Security policies for user accounts have apparently changed significantly and as I found out the hard way at least part of this is password complexity. I resolved the user authentication by unlocking the user account password as root (passwd -u username) so there was no password and then having the user set the password to fulfill the new policy requirements of password complexity.

In an effort to resolve/debug (*fix*) the aforementioned authentication issue I also did the following updates:
I created an updated iso of the *64-current 12-28-19 (kernel version 5.4.6) snapshot and upgraded only the kernel and the the aaa_base packages. That said the delayed logout has been there since the initial 12-6-19 install.

Yes I understand that *these* partial upgrades are a 'no-no'. I will eventually do a complete upgrade (or possibly a complete start-from-scratch-reinstall). I was hoping I might avoid that (i.e.the reinstall) and hear from someone else on the forum that had similar experience and found a solution.

1 members found this post helpful.

Yes you are correct that this should be in the Slackware forum. I will post a new thread there with the link to this one. Thanks again cwizardone.

1 members found this post helpful.

What's the current status? I myself am having this problem as well. I notice that the upower in -current is 0.9.23, but it appears that 0.99.11 is the most current, and is far newer than 0.9.23. It will have to wait until another day for me to test it out, but leaving this here in case anybody can confirm that newer upower versions are the way to go.

1 members found this post helpful.

The problem was caused by an incomplete upgrade, but the thread does not mention this:

When you upgrade an installation of slackware-current, always make sure that you read and understand the ChangeLog.txt entries. Look for " Added." and "Removed." entries and act on those.
Merely using "upgradepkg" will eventually break any slackware-current system. For a stable release (14.2), that is a different story.

2 members found this post helpful.

Herpa derp, missed that one.

Yes Alien Bob - It was an issue with an incomplete upgrade but I failed to mention that the incompleteness was a feature (tongue-in-cheek) with slackpkg+ not completing the download of all packages. Now it could be that the packages you cite above were the culprits - I really can't say. The lesson here for at least me is to do a full download of a repository (using lftp, wget, rsync etc.) - and then manually install the packages. This is especially true when specifying either of the following two mirrors:

http://slackware.uk/people/alien-kde/current/latest/
https://slackware.nl/alien-kde/current/latest/

From my location in San Diego, CA the BW for the latter mirror (.nl) is not recommended. It might be great in the Netherlands.

slackpkg+ is a great tool for doing 'current' upgrades from mirrors like http://mirrors.slackware.com since the BW to/from sites like this are solid and the traffic is minimal. For large amounts of data use the recommended 'rsync' to get a complete repository in lieu of slackpkg+ not giving you warnings about completing the transaction request.

It might be worth doing something like I'm doing and just maintaining a local mirror (I keep it for the 64bit versions of 14.2 and -current) using Alien Bob's mirror-slackware-current.sh script. I then setup a cron job to go off at 5am every morning to sync the mirrors if there's any updates. You can then keep your /etc/slackpkg/mirrors.conf file to a local mirror and have your updates be super fast.

Gee thanks bassmadrigal. Would you mind sharing a copy of your crontab (for syncing your repo's) and a couple pointers on what you need to do to configure it? I am not that familiar with cron though I know that all my installs run crond by default. It must be a system requirement.

Sure!

First get Alien Bob's mirror-slackware-current.sh.

Next, figure out where you want your local mirror. I have a whole slew of harddrives under /share, so I chose one of the drives mounted under that. All the scripts and conf files will be located in that area if you don't want to modify things substantially. Then you'll set up a conf file for the mirror-slackware-current.sh script to point to that mirror. Mine contains (make sure you replace the red with your info):

I mirror both 14.2 and -current, so I don't add the RELEASE into the conf, but if you only intend to mirror one of them, you can add the release of "14.2" or "current".

Since I mirror both, I setup a script (update-mirrors.sh) that will sync both releases and save the output to logfiles.

Then in my normal user's crontab (since I didn't do any of the above as root and my normal user has full access to the mirror files). You can edit it with crontab -e (although, I think by default this uses vi/vim, which I have overridden with nano, so if you run into issues you can run EDITOR=nano crontab -e to use nano as your editor).

This will run the update-mirrors.sh script at 5am every day. If you want to tweak the time, the first 0 is the minutes and the second character, 5, is the number of hours into the day (the 3 block is the day of the month, 4th is for month of the year, and the 5th is for the day of the week). So if you wanted it to run at 3:45PM, you would have it be:

There's more examples in man crontab.

2 members found this post helpful.

This is great stuff bassmadrigal! Thank you for posting this. I am definitely going to give this a shot.

I have been using AlienBob's mirror script to keep a local repository of -current for several months now. It is a very handy script and should be easily modified to keep a Slackware 14.2 repository current - though I am not sure this is warranted since slackpkg should adequately handle keeping my 14.2 install current and with much lower traffic.

That said I am having some doubts about slackpkg. For example just this morning I had issues upgrading my multilib packages. The following commands should do the trick but they didn't:

#slackpkg update
#slackpkg upgrade multilib

Instead I had to download (lftp) a new multilib repository and manually install the packages. I am not sure what is going on here since /etc/slackpkg/slackpkgplus.conf looks to be configured correctly with a good MIRROR - i.e. MIRRORPLUS['multilib']=http://slackware.uk/people/alien/multilib/current/

It might be a while before I can try out your cron scripts. I first need to address another issue re-building my nvidia-kernel package with the latest 5.4.13 kernel. This is a big pain since I have to rebuild these nvidia-kernel and nvidia-driver packages every time I install a new kernel. Not sure I will ever use/buy another nvidia GPU because of this!

Since you regularly upgrade your -current, I am curious how often do you upgrade your kernel. Are you currently running the 5.4.X ?