https://bugs.kde.org/show_bug.cgi?id=422948
--- Comment #69 from Wolfgang Bauer <wba...@tmo.at> --- (In reply to Martin Schnitkemper from comment #68) > I can not say, since when the notification-problem exist. I just discovered > it since the "play a sound"-event is configured in the same systemsettings > panel than the other events, but I didn't used them so far. > > After I discovered the startup sound problem, I configured in addition the > "log to a file"-event to verify, if it is just a sound problem or a general > problem with the notifications. And I can confirm now, that the problem > affects every event, that should be triggered on startup. I configured the > same events on logout, and on every logout I got an entry in the logfile, > written by KNotify, but never on login. Same happen with the "show a > message in a popup". The special code in plasmashell that plays the login sound only supports playing a sound. It completely ignores the other options. Otherwise these notification settings are handled by knotifications, which supports things like logging or showing a message too. The point is that what you noticed is not really a bug per se (rather a missing feature), and totally unrelated to the original problem. > If that leads into a racing condition, than this concept is unusable for any > other event too, since it doesn't work. If it works on logout, why not on > logon? The specific problem here is that on login things are still being started and not everything may be running yet. That said, I don't know if that would still be a problem, but I do remember reading something like this in some other bug report about problems with the startup/login sound which led to the current solution of using Phonon directly instead of notifications. -- You are receiving this mail because: You are watching all bug changes.
