Description of problem: Version-Release number of selected component (if applicable): Kmail 5.2.0 How reproducible: Steps to Reproduce: 1. Kmail starts normally 2. Exit 3. Try to restart Kmail: Fails to appear at all. Will attach an strace of that failure.
Created attachment 7773 [details] strace of Kmail failing to appear
Similar problem reported at https://bugs.kde.org/show_bug.cgi?id=360031 - to which I have attached same strace Attachment.
See Also: (none) => https://bugs.kde.org/show_bug.cgi?id=360031
N.B. If - after failure to appear - Logout/Login is done, Kmail then does start normally.
Keywords: (none) => 6sta1, UPSTREAM
CC: (none) => marja11Assignee: bugsquad => mageia
CC: (none) => bequimao.de
Same problem with Kmail 5.2.3 - whose Help/Version shows: . KDE Frameworks 5.24 . Qt 5.6.1 . xcb windowing system in July 22 64-bit clasical ISO Plasma login. (Real h/w on nVidia GTS250 non-EFI non-GTP Desktop) Kmail will not restart after initial Start/Exit.
However, on *32-bit* Mga6-RC on real non=EFI non=GPT h/w Samsung NC110 netbook - Plasma login - Kmail 5.2.3 *will* re-start after initial start/exit...
I have never seen this issue since kontact/kmail started working. I doubt that it depends on any hardware or 32/64 bit. Do you use IMAP accounts? Do you see anything when you enter as user # journalctl -b | grep akonadi You may test KMail with a newly created user, which should work now. Best regards, Ulrich
> Do you use IMAP accounts? No - only POP3. > Do you see anything when you enter as user > # journalctl -b | grep akonadi No: $ journalctl -b | grep akonadi [mab@localhost ~]$ su - root Password: [root@localhost ~]# journalctl -b | grep akonadi [root@localhost ~]# journalctl -b | grep akonadi > You may test KMail with a newly created user, Not possible to use newly-created user at the moment, due to system problem with e.g. /etc.shadow.lock (Bug 16733)
(In reply to Maurice Batey from comment #7) > > > You may test KMail with a newly created user, > > Not possible to use newly-created user at the moment, due to system > problem with e.g. /etc.shadow.lock (Bug 16733) Thanks, Works here. The only issue, I had to exclude an empty panel. I think it was resolved with the pam update. See bug 17504 Comment #57. Ulrich
>> You may test KMail with a newly created user, > Not possible to use newly-created user at the moment, due to system problem > with e.g. /etc.shadow.lock (Bug 16733) Having overcome the latter problem, the 2nd user can now restart KMail after initial Start/Quit. However, the first user still cannot do that. I am appending an strace of the attempt.
Created attachment 8329 [details] strace of attempt to restart Kmail Herewith strace of attempt to re-start Kmail after earlier Start/Quit.
Assignee: mageia => kde
is this bug still valid on current cauldron ?
CC: (none) => mageia
No such problem with latest Kmail (5.4.3) - though it is displaying another problem (instability), on which I am keeping an eye (hoping subsequent updates will iron that out).
thank you for the feedback => closing
Status: NEW => RESOLVEDResolution: (none) => FIXED
> it is displaying another problem (instability), on which I am keeping an eye > (hoping subsequent updates will iron that out). Have seen similar reports, linked with use of nVidia 'nouveau' driver instead of proprietary driver. Will check that out with a new install of Mageia-6-rc tomorrow (assuming can acquire proprietary driver this time...)