Arch Linux User Repository

@Rhinoceros - thanks, bud. i may reserve the next bump though. i'm getting a segfault in kded5 when the system update completes, so I'm going to have to dig in to the code and check what exactly is being called on completion. it could be unrelated, or it could be a qt5 package that still needs to be updated, but i have to take a look. it's definitely connected to qt5packagekit, though (you can see the reference in the stack trace).

Application: kded5 (kded5), signal: Segmentation fault

[KCrash Handler]
#4  0x00007fc329994828 in PackageKit::Transaction::role() const () at /usr/lib/libpackagekitqt5.so.1
#5  0x00007fc329bbf50e in  () at /usr/lib/qt/plugins/kded_apperd.so
#6  0x00007fc329bbf78f in  () at /usr/lib/qt/plugins/kded_apperd.so
#7  0x00007fc35d2bda51 in  () at /usr/lib/libQt5Core.so.5
#8  0x00007fc329988aba in PackageKit::Daemon::transactionListChanged(QStringList const&) () at /usr/lib/libpackagekitqt5.so.1
#9  0x00007fc35d2bdc00 in  () at /usr/lib/libQt5Core.so.5
#10 0x00007fc3299a13a9 in  () at /usr/lib/libpackagekitqt5.so.1
#11 0x00007fc3299a2393 in  () at /usr/lib/libpackagekitqt5.so.1
#12 0x00007fc35dd2b45f in  () at /usr/lib/libQt5DBus.so.5
#13 0x00007fc35d2b0be0 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5
#14 0x00007fc35df78b1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#15 0x00007fc35d28cf98 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5
#16 0x00007fc35d28daa3 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5
#17 0x00007fc35d2d3e68 in  () at /usr/lib/libQt5Core.so.5
#18 0x00007fc35c06787b in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
#19 0x00007fc35c0be299 in  () at /usr/lib/libglib-2.0.so.0
#20 0x00007fc35c066132 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#21 0x00007fc35d2d7c4c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#22 0x00007fc35d28573c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#23 0x00007fc35d290269 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5
#24 0x0000565191020040 in  ()
#25 0x00007fc35ca35290 in  () at /usr/lib/libc.so.6
#26 0x00007fc35ca3534a in __libc_start_main () at /usr/lib/libc.so.6
#27 0x00005651910200c5 in  ()
[Inferior 1 (process 1388) detached]

@jghodd Happy to do that. I haven't noticed anything myself, but sounds like a good idea. BTW you are a co-maintainer, so I'm totally happy with you bumping this in the future.

@Rhinoceros - it might be time to increment the revision number to 2 to force new builds. i'm seeing some anomalous behaviour which seems to have disappeared after a rebuild (it actually took down thunderbird, ibus, notifications and megasync suddenly, simultaneously, and unexpectedly). the odd behaviour may be related to one of the dependencies, several of which have been updated recently (dbus and dbus-related packages, and notification packages). i see no reason to address the source code itself, although there are a number of build warnings that could be addressed, but a rebuild, so far, seems to have resolved the weirdnesses.

Thanks @Thulinma. Great to hear! Thank you! Also, GitHub issues are now working. I didn't know how it worked, but I always assumed it was when devs didn't want to be bothered! :D

Yes, I see similar behaviour to @emacsomancer. I had been trying to find a way to trigger the problem all the time, but I can't even get it to work now. I'll keep at it and see if I can isolate a 100% reproducible situation.

@Thulinma: It usually doesn't surface straight away, but not long after a reboot, interactions with (or even near - say with another systray application) pull up the kalu menu, even if they shouldn't. And the menu can only be made to disappear by making a selection (I usually click on "About" as a workaround). I think it is definitely a Plasma issue, and an issue with the latest version of Plasma - it didn't happen before the anniversary edition.

@Rhinoceros Yeah, I plan to maintain the package from here on forward, at least until the original author reappears (if ever). Disabling issues was not intentional - that may have been a think github did for me without me realizing. I'll re-enable it!

I have not seen this issue yet - can somebody describe it in a way I can reproduce it? Or is it Plasma-specific? (I do not use Plasma myself at all - so that would explain why I don't see it, in that case...)

Sorry @emacsomancer and @Healing_Hands, yes, I am seeing this occasionally now too. I'm not sure if @thulinma is still interested in further upstream maintenance. That was be much appreciated if possible! (I noticed they had disabled "issues" in the Github repo.)

@Healing_Hands: it's sporadic too. restarts seem to help for a time, but it comes back. I think it may not be specific to kalu, so perhaps something about the new version of plasma more generally?

@emacsomancer I have the same Problem, so I don't think it's a configuration issue.