Bug 138665 - Mail/ over NFS + WLAN disconnect/reconnect = KMail crash
Summary: Mail/ over NFS + WLAN disconnect/reconnect = KMail crash
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.9.5
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-11 09:44 UTC by Benoît Jacob
Modified: 2012-08-19 10:48 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Benoît Jacob 2006-12-11 09:44:36 UTC
Version:           1.9.5 (using KDE 3.5.5, Gentoo)
Compiler:          Target: i686-pc-linux-gnu
OS:                Linux (i686) release 2.6.17-gentoo-r8

I have the following setup:

- a NFS server on which I store my precious data, like my Mail/ directory.

- a laptop mounting the NFS share at startup, say as /data, with the following symlink:

~user/Mail/ ----> /data/user/Mail/

KMail runs very fine on the laptop... except that when the WLAN disconnects and then reconnects, KMail crashes.

No KCrash assistant shows up, KMail just disappears.

When I run KMail from the console, the only output is:
*** KMail got signal 15 (Exiting)

Note 1: the crash doesn't occur on WLAN disconnect, it occurs on the subsequent reconnect.

Note 2: the WLAN disconnect was simulated by turning off the WLAN switch on my laptop. But I guess a "natural" WLAN disconnect would give the same result. And I know my WLAN disconnects frequently, so that crash is a real issue for me!
Comment 1 Björn Ruberg 2010-01-01 22:55:27 UTC
Well, kmail wants that opened files remain ... open and accessable. Making kmail handle loosing the network files is probably a quite hard task. I propose using IMAP for your task.
Comment 2 Myriam Schweingruber 2012-08-19 10:48:16 UTC
Thank you for your report. Kmail1 is currently unmaintained and the code has changed sufficiently in Kmail2 so the backtraces are not really useful anymore. Should you experience the same crash in Kmail 4.8.5 or later, please open a new report for Kmail2. Thank you for your understanding