Notification from KDE write daemon
 

Sometimes (5 times this week) I get 30 or more "Notifications from KDE write daemon" rolling up the right of screen. The messages vary from incident to incident, although "klogd" figures strongly; some are empty,some contain only computer name, some contain I think Hex numbers, some are verbose but to me meaningless.
Unfortunately I can't record them, because they're mobile, and I have to restart to do anything. although "klogd" figures strongly.
I found this 'flooding' on Google, but the language was too far beyond my linux vocab to benefit from, and failed to find reference on these forums, so.. any suggestions would be much appreciated.

I have a screenshot here, of one incident;

If I can do a copy paste I shall, but the process makes that tricky.

I would venture a guess that you are running KPPP, and are using a USB modem, and that for some reason, KPPP or pppd is sending that debug/backtrace message.

Not sure why; and if you detect no functionality problems before or after the message, I'd look at KPPP or pppd websites and/or bugzilla forums to see if it's a known issue, and otherwise ignore it until a problem manifests itself..

It might be simply that excessive debugging is enabled on pppd and/or KPPP and it's reporting something for the heck of it.

I get semi-infrequent "Launching Knotify" messages on my taskbar from *something* within KDE, but I too have no clue what's sending the messages.

Sasha

widda, are you having functionality issues as well, or just the messages?

Sasha, perhaps you should post a question regarding your Knotify messages :p

Forrest

I would if the thread would add up to more than merely a question. Currently (let me rephrase) the message amounts to no more than a taskbar item, like one would get when opening up any application, and it reads "Launching Knotify". There's no associated window that can be raised: only the taskbar item.

IIRC, it normally happens during my already-reported issue I have been having with `kdesu konqueror` (which doesn't work) and which is already documented in at least 2 threads here on LQ.

Further, I experience no functionality problems (other than the `kdesu konqueror` problems) and I attribute the situation, in large part, to KDE 4.x being buggy as hell.

Finally, I'm running Slack64-current, so I'm waiting until Slack-stable comes out before I pursue it further, though IMO it's a KDE thing, not a Slackware thing.

Sasha :)

forresst: yes, functionality seriously reduced by notification obscuring 2-fifths of screen, including obscuring the taskbar control to kill the notification!.
It hasn't happened for a week.

one more kde write daemon message, (and one tar-unwrapping progress bar persisting through reboots even after x-ing it off) since which screen several times becomes unresponsive to mouse click (i.e. hangs?)

The first hang started while first-time using of the Basket Notes program's screencapture tool, altho the program had been smooth before that.

Would be great if someone could interpret the kde daemon message, and even point me to a better way of responding to them than pestering for each one.

Thanks to the many folks who've helped so many get a grip on the system.

What I see in that backtrace (not the un-tarring window) is mention of [usb-core] and that's the only thing I can see that is common to the FIRST backtrace you provided in your first post to this thread.

What it means exactly, I haven't a clue, and I suspect that MOST people also will have no clue what it means exactly, unless they are experienced kernel programmers or experienced KDE programmers/debuggers.

Simply based on the fact that USB is mentioned again, let me ask:

Q: Is there any USB device involved here, common to each scenario when the trouble occurs? Like maybe a USB flash drive or USB hard disk (or as speculated earlier, a USB modem?), perhaps even a USB disk where the file being un-tarred, is located? Or are you running the OS off of a USB drive?

Sorry, but I'm just throwing out ideas here, to try to help you narrow down to a particular device or subsystem that is producing the malfunction. As to WHY the malfunction is happening, I'm just not qualified to try to diagnose.

Two suggestions:

1-- Check out kde.org and sift through the User Guide and FAQ/troubleshooting sections. There are a couple sections dealing with KDE error messages and/or Knotify messages and the like. Maybe there's a clue there.

and

2-- After Googling for any hint at all of others experiencing a similar issue, file a bug report with KDE, and/or otherwise contact the bug team at KDE and ask for help. (You may also want to search the Mandriva places on the 'net too, since you're apparently running Mandriva -- there may be similar reports there; Mandriva may have done their own patches or whatever, or various packages, and maybe they have a clue why this is happening.)

3-- If there's a USB device(s) involved on your machine, which you can do without for some testing (like a modem), then unplug it/them, and try un-tarring, or whatever else generally causes the problem, and see if it still happens.

Unless you can get the help of an experienced programmer/debugger, or someone who has experienced the EXACT same situation, it's a lot of trial and error, and maybe bug report(s)


Best of success,
Sasha

Sasha, thanks for your time.
The common usb device is indeed the wireless broadband modem.

I'll take yr advice, and also look at the BasketNotes program on Ggle, tho I doubt that it was involved in previous occurrences.

Widda

here's more signs from the daemon.
and one from kde, probably trying vainly to help me with disappearance of minimised pages from my taskbar.

another of my futile researches is "what's an x windows server?"
Maybe I'm a fish asking "what's this 'water' I keep hearing about?"