Bug 302619 - kmail does not run at start due to akonadi.
Summary: kmail does not run at start due to akonadi.
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.8.2
Platform: Unlisted Binaries Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-27 08:56 UTC by Angelo GIRARDI
Modified: 2017-01-07 21:55 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Angelo GIRARDI 2012-06-27 08:56:21 UTC
Since akonadi has been implemented (previous versions of kde and current), when you start kmail as root user (kdesu) under normal user, it no more possible to run kmail.

I used kdesu-kmail to have access to service mail without having to logout, shutdown the XServer and than start root and kde and kmail.


Reproducible: Always

Steps to Reproduce:
1. Login as normal user without root priviligies
2. Start kde
3. Create a link to application with :
    [Desktop Entry]
   Comment[en_US]=
   Comment=
   Encoding=UTF-8
   Exec='/usr/bin/kmail'
   GenericName[en_US]=
   GenericName=
   Icon=kmail
   MimeType=
   Name[en_US]=SU E kMail
   Name=SU E kMail
   Path=
   StartupNotify=false
   Terminal=false
   TerminalOptions=
   Type=Application
   X-DBUS-ServiceName=
   X-DBUS-StartupType=multi
   X-DCOP-ServiceType=none
   X-KDE-SubstituteUID=true
   X-KDE-Username=root

4. Run the link
Actual Results:  
Cannot launch kmail as root from common user

Expected Results:  
Launch kmail from normal user with root priviligies.

Nothing
Comment 1 Denis Kurz 2016-09-24 18:10:58 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 21:55:32 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.