[SOLVED] QDBusAbstractAdaptor errors on exit from X/Plasma in Slackware64-current

emmet · 03-21-2022, 05:48 PM

I'm seeing these errors in the console when I exit X Windows.

Code:

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*
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*

I normally only ever have cause to exit X Windows when I'm doing a slackpkg upgrade-all that involves upgrading KDE or core libraries or the kernel.

I think the error messages started after I installed kernel 5.16.14. I first saw these errors when I dropped down to the console to install 5.16.15, but I figured at the time that maybe the cause was not having restarted kde after an intervening qt5 upgrade. But the error messages have persisted since. I am as of yet unaware of any deleterious effect other than the error messages themselves.

emmet · 03-22-2022, 03:36 PM

Today, when I dropped out of X Windows to update the kernel to 5.17.0, the QDBusAbstractAdaptor error messages were conspicuous in their absence. I did nothing and the problem went away.

I suppose I should have mentioned that I run at runlevel 3, so that's what all the "dropped out of X Windows" is about.

Something changed, of course. There were persistent error messages until there weren't. So, what was it that changed? Well, yesterday I ran the Mon Mar 21 07:31:06 UTC 2022 slackware64-current update, which contained a single package upgrade: l/qt5-5.15.3_20220318_e507d3e5-x86_64-1.txz. This feeds into my earlier stated hypothesis that the error messages and their underlying cause arose from the previous qt5 upgrade in the Wed Mar 16 01:46:29 UTC 2022 slackware64-current update.

The most recent qt5 update, which seems to have solved my issue, is described as a rebuild to correct the omission of liblocationlabsplugin.so and to correct a syntax error in a shell script. So it may be that the error messages were somehow reflective of the problems in the previous qt5 build or, alternately, my problem arose because I did the Wed Mar 16 01:46:29 UTC 2022 upgrade, via slackpkg, from within KDE, i.e. while running apps that were using the qt5 libraries.

It would be nice to know which of the above suppositions was the real cause, or if it was something else altogether which has so far eluded me, but whichever may be true, I suppose my problem is solved.