Bug 448180

Summary:	kded5 doesn't delete modules on logout
Product:	[Frameworks and Libraries] frameworks-kded	Reporter:	popov895 <popov895>
Component:	general	Assignee:	David Faure <faure>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	kdelibs-bugs-null, popov895
Priority:	NOR
Version First Reported In:	5.90.0
Target Milestone:	---
Platform:	Other
OS:	Other
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description popov895 2022-01-09 20:40:11 UTC

SUMMARY

When logging out, kded5 either doesn't delete loaded modules at all (which happens most often) or only deletes a few of all loaded ones. When kded5 is killed manually, it only deletes all modules if it receives a SIGHUP signal.

I can only confirm this issue on KDE neon, I don't know how things are on other distributions.

See https://bugs.kde.org/show_bug.cgi?id=445376#c9.

SOFTWARE/OS VERSIONS

Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.23.80
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.3
Kernel Version: 5.11.0-44-generic (64-bit)
Graphics Platform: X11

Comment 1 popov895 2022-01-10 17:16:33 UTC

Same on openSUSE Tumbleweed

SOFTWARE/OS VERSIONS

Operating System: openSUSE Tumbleweed 20220107
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2
Kernel Version: 5.15.12-1-default (64-bit)
Graphics Platform: X11

Comment 2 popov895 2022-01-10 18:49:17 UTC

I also found that on logout on openSUSE Tumbleweed kded5 gets SIGUSR2, but on KDE neon it gets SIGHUP and/or SIGTERM.

Comment 3 popov895 2022-01-10 20:31:04 UTC

(In reply to popov895 from comment #2)
> on logout on openSUSE Tumbleweed kded5 gets SIGUSR2
Sorry I was wrong, it receives SIGUSR2 not only on logout.

Comment 4 popov895 2022-01-11 08:21:33 UTC


*** This bug has been marked as a duplicate of bug 97716 ***