Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 390453

Summary: kde-base/kmail-4.7.3 crashes on startup
Product: Gentoo Linux Reporter: Peter Ruskin <aoyu93>
Component: [OLD] KDEAssignee: Gentoo KDE team <kde>
Status: RESOLVED UPSTREAM    
Severity: normal CC: buchner.johannes, dschridde+gentoobugs, frp.bissey, kensington
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Peter Ruskin 2011-11-13 22:33:37 UTC
KMail crashes on startup, even after I deleted the ~kde4 directory.  The message is "Failed to fetch the resource collection."
Comment 1 Andreas K. Hüttel archtester gentoo-dev 2011-11-13 22:49:50 UTC
(In reply to comment #0)
> KMail crashes on startup, even after I deleted the ~kde4 directory.  The
> message is "Failed to fetch the resource collection."

OK, thx. 
* Is the akonadi service running? (Check with akonaditray for example)
* Is KMail just terminating or is it a real crash? Does drKonqui start and display a backtrace?
Comment 2 Peter Ruskin 2011-11-14 00:20:59 UTC
# akonaditray
QSystemTrayIcon::setVisible: No Icon set
akonaditray(13678)/libakonadi Akonadi::AgentManagerPrivate::createDBusInterface: AgentManager failed to get a valid AgentManager DBus interface. Error is: 1 "org.freedesktop.DBus.Error.NameHasNoOwner" "Could not get owner of name 'org.freedesktop.Akonadi.Control': no such name" 

After I click the message box "Failed to fetch the resource collection.", kmail terminates.  There is no drKonqui instance.

Early kde-4 versions worked and imported my 3.5 settings.  I've not had kmail working since its akonadi requirement.  That's why I tried again after deleting the ~/.kde4 folder.
Comment 3 Franz Trischberger 2011-11-14 06:59:30 UTC
akonadi stores its data in ~/.local/share/akonadi, some config-files are in ~/.config/akonadi. Does renaming/removing those dirs make kmail start up?
Comment 4 Peter Ruskin 2011-11-14 08:38:29 UTC
Thanks. Removing ~/.local/share/akonadi directory makes no difference.
Comment 5 Peter Ruskin 2011-11-14 08:49:09 UTC
akonadiserver.error:
Control process died, committing suicide! 

akonadi_control.error:
D-Bus session bus went down - quitting
Comment 6 François Bissey 2011-12-09 02:57:55 UTC
Actually I got it to work by telling kmail to look under
.local/share/local-mail/
which existed for its "resource collection" and it stopped crashing.
Now I am trying to get it to send email....
Comment 7 Ian Delaney (RETIRED) gentoo-dev 2011-12-31 08:46:08 UTC
would you believe I have a workaround for this from a linux magazine; a one off.
It seems kmail "at first launch will terminate with a 'Failed to fetch the resource collection' error. KMail doesn't have a default incoming mail directory configured. causing this error.  The workaround involves using Akonadi to specify a maildir location for KMail.  To do this, launch the Akonadi configuration tool and point the Local folders to ~/.kde4/share/apps/kmail2"

Only ever get 1 of these
Comment 8 Johannes Huber (RETIRED) gentoo-dev 2012-01-02 16:39:10 UTC
*** Bug 397397 has been marked as a duplicate of this bug. ***
Comment 9 Dennis Schridde 2012-02-04 15:44:34 UTC
(In reply to comment #6)
> Actually I got it to work by telling kmail to look under
> .local/share/local-mail/
> which existed for its "resource collection" and it stopped crashing.
Confirming workaround.

"Personal Calendar" and "Invitations" also have no file configured, though that does only cause annoying "unable to fetch from backend" messages, but no crashes.
"Personal Contacts" and "Notes" have default directories(!) configured.
Comment 10 Dennis Schridde 2012-02-04 22:58:47 UTC
(In reply to comment #9)
> "Personal Calendar" and "Invitations" also have no file configured, though that
> does only cause annoying "unable to fetch from backend" messages, but no
> crashes.
Those messages have another cause and were not fixed by adding the files to Personal Calendar and Invitations. Since the dialogue boxes don't describe who is telling me this, I can't know the cause.
Comment 11 Andreas K. Hüttel archtester gentoo-dev 2012-04-13 21:14:08 UTC
I fear we can't do much here. This was a typical upgrade problem, caused by the switch to more akonadi modules in kdepim... Once you have fixed it, things should be ok. 

If you want, you can report it upstream (but probably now it's too late).