Version: unspecified (using KDE 4.7.4) OS: Linux When I log in, I get the following error dialog: Fetch Job Error - Plasma Desktop Shell Unknown error. (Unable to fetch item from backend.) I have to close the dialog or Plasma won't respond to other input. Reproducible: Didn't try Steps to Reproduce: Log in Actual Results: The error dialog comes up Expected Results: No error I just upgraded from 4.7.3 to 4.7.4. (Ubuntu 11.10 Oneiric)
can you provide a screenshot of your desktop when this happens? also, can you provide a list of plasmoid widgets you are using? thanks.
Is there a way to get a full list of plasmoids? I'm just using KUbuntu's defaults, so ooking from left to right, in the panel at the bottom of the screen I see: Application launcher, Activity manager, Virtual desktop, Task manager, Show desktop, Notifications, System tray, Network management, and Digital clock.
Created attachment 68254 [details] Image of the error dialog
This is a wild guess, but based on the one time i saw this error. What happens if you switch off all akonadi & nepomuk related stuff?
Then Kontact gets very unhappy.
Same here with 4.8 from Archlinux but I have a dual screen. This error not appends on my other computer with only one screen.
This is happening here - only since I upgraded to 4.8.2 on OpenSuse 12.1. Only got a single display. Tempted to wipe all the KDE4 conf files, it's surely a plasma widget that's broken.
i can confirm wiping the .kde config files resolved the issue, back to defaults tho!
I've seen this happening on my Fedora box, but not on my arch one. It should have something to do with some impatient applet that does not want to wait until i've unlocked KWallet... The two potential culprits I can think off are Lionmail (installed from git, I know..) and opendesktop to which I've logged on at some point (and find it hard to log out from again, but that's another story).
*** Bug 304498 has been marked as a duplicate of this bug. ***
I have a similar dialog. Earlier it was identical, now it has instead the following: Unknown error. (Unable to fetch item from backend (collection 32, resource -1)) The window title was marked as Korganizer alert service (my translation from Finnish).
I have the same error but at KDE logout, the dialog icon is an enveloppe, title is "Fetch Job" and the message is "Unknown error.", too concise for me. Thanks for the help,
Created attachment 73344 [details] Screenshot of error message
Setting status to confirmed.
I just upgraded from 4.8.3. to 4.8.5 and I don't see this bug any more. Maybe it's been fixed?
(In reply to comment #15) > I just upgraded from 4.8.3. to 4.8.5 and I don't see this bug any more. > Maybe it's been fixed? Thank you for the feedback. Please feel free to reopen if you can reproduce this with KDE 4.9.1 or newer.
I was too optimistic. This error message is back. The first time Iogged on to KDE after upgrading from 4.8.3 to 4.8.5, no error message appeared, but now I've logged in the second time and the old error message is there again. Please reopen this bug, thanks!
Please check your kmail configuration. It looks like it tries to fetch mail from a wrongly configured server.
I'll get back to this issue when I've been upgraded to 4.9.1 or newer, thanks.
Exactly this error on logout (http://bugsfiles.kde.org/attachment.cgi?id=73344) in OpenSuSE 12.2 Factory, KDE 4.9.4. Dual display. I propose to reopen... How to debug this?
Sometimes this is related to akonadi after OS upgrade (in my Case openSUSE 12.1->12.2). Easy fix is to remove the cache i.e. $HOME/.local/share/akonadi. Whether it is safe removal for you - see the notes from http://blogs.kde.org/node/4503. Perhaps the product in this bug could be changed to akonadi or it is distribution related (but reported issues come both from openSUSE and Kubuntu). Or my case is only similar to the reporter's case.
Same here on opensuse 12.2. I managed to clear the error with advice from Will Stephenson at Suse. Right click on clock, "Digital clock settings", Calendar page, "Display events", uncheck that. I have 2 other logins on the same machine and they don't get this error when the "Display Events" is checked.
I see no reason to keep this open as a KOrganizer bug. If it still happens for you then it needs to be re-classified as an Akonadi bug.