RE: [suse-kde] KMail won't start (segfault)
-----Original Message----- From: Patrick [mailto:penguin0601@earthlink.net] Sent: Tuesday, November 19, 2002 3:36 PM
[...]
Have you tried renaming your /home/<user>/.kde directory to something else and letting the whole thing be created new to see if that takes care of the problem?
I renamed the /home/kmclauchlan/.kde directory, got out, restarted Linux and KDE, and tried KMail. RESULT: KMail started with the "Welcome" pane where my inbox would normally appear, which is expected result, since all the KDE configuration is now default, and my old Mail directory is still renamed and safely hidden. So KMail created new, empty, default directories. FURTHER RESULT: Then I quit the program... segfault! Ever since then, if I try to open the program, it churns for a while and then segfaults without ever opening, much the way it did before. My Outlook inbox now has 3910 messages, unsorted. The previous year of e-mail (70,000+ messages that I received in KMail up to the beginning of November when this segfault began) is tied up as numbered message files in the maildir directories that KMail won't open anymore. I'm going to have to give up soon, and let Outlook re-take ownership of my mail. The Exchange Server administrator is telling me that he is no longer willing for me to leave 4,000 messages on his server. Once I let Outlook sort and file them, and delete originals from the server, they'll be basically unreachable by linux mail if I ever get KMail working again. I've been hoping to get KMail fixed before I had to give in and let Outlook suck me back into Bill Gates' clutches. This is yucky. Sa-a-ave me from the Borg! :-) /kevin
Did you try removing the tmp kde files in /tmp along with the .mcop files in your /home directory. It could be some wanky tmp file that's causing it to behave like this. * KMcLauchlan@chrysalis-its.com (KMcLauchlan@chrysalis-its.com) [021120 11:24]: -> -> ->> -----Original Message----- ->> From: Patrick [mailto:penguin0601@earthlink.net] ->> Sent: Tuesday, November 19, 2002 3:36 PM -> ->[...] ->> Have you tried renaming your ->> /home/<user>/.kde ->> directory to something else and letting the whole thing be ->> created new ->> to see if that takes care of the problem? -> ->I renamed the /home/kmclauchlan/.kde directory, ->got out, restarted Linux and KDE, and tried KMail. -> ->RESULT: KMail started with the "Welcome" pane where -> my inbox would normally appear, which is -> expected result, since all the KDE configuration -> is now default, and my old Mail directory is -> still renamed and safely hidden. So KMail created -> new, empty, default directories. -> ->FURTHER RESULT: Then I quit the program... segfault! -> Ever since then, if I try to open the program, -> it churns for a while and then segfaults without -> ever opening, much the way it did before. -> -> ->My Outlook inbox now has 3910 messages, unsorted. ->The previous year of e-mail (70,000+ messages that I ->received in KMail up to the beginning of November ->when this segfault began) is tied up as numbered ->message files in the maildir directories ->that KMail won't open anymore. -> ->I'm going to have to give up soon, and let Outlook ->re-take ownership of my mail. ->The Exchange Server administrator is telling me that ->he is no longer willing for me to leave 4,000 ->messages on his server. Once I let Outlook sort and ->file them, and delete originals from the server, ->they'll be basically unreachable by linux ->mail if I ever get KMail working again. ->I've been hoping to get KMail fixed before I had to ->give in and let Outlook suck me back into Bill Gates' ->clutches. ->This is yucky. Sa-a-ave me from the Borg! :-) -> ->/kevin -- Ben Rosenberg ---===---===---===--- mailto:ben@whack.org Tell me what you believe.. I tell you what you should see.
On Wednesday 20 November 2002 14:47, Ben Rosenberg wrote:
Did you try removing the tmp kde files in /tmp along with the .mcop files in your /home directory. It could be some wanky tmp file that's causing it to behave like this.
FINALLY! That seems to have done it. (It must have been the stuff in /tmp, because the .mcop had already been renamed/moved.) Blessings on your house! :-) Follow-up question: So... in general, is it safe to delete ANY file that's in /tmp? Does anybody legitimately put stuff in /tmp that needs to survive from session to session? /kevin
Kevin McLauchlan writes: [...]
So... in general, is it safe to delete ANY file that's in /tmp?
From the LPI Linux Certification in a Nutshell Guide: "The /tmp directory is for the storage of temporary files. The contents are deleted on every system boot."
But I don't know if this is always the case.
Does anybody legitimately put stuff in /tmp that needs to survive from session to session?
I wouldn't. There are other places, such as /var and /var/tmp. (Or so says my guide - I don't profess to be an expert.) There's also ~/. And from an old linuxgazette article: "the file permissions [for /tmp]: drwxrwxrwt 10 root root 3072 May 18 21:09 /tmp/ We can see that everyone can write to this directory: everyone can create, rename or delete files and directories here. There is one limitation: the `sticky bit' is switched on. (Notice the t at the end of the first column.) This means a user can only delete or rename files owned by himself. This prohibits users peskering each other by removing the other one's temporary files." -K -- Kevin Pfeiffer International University Bremen
K Pfeiffer wrote:
Kevin McLauchlan writes: [...]
From the LPI Linux Certification in a Nutshell Guide: "The /tmp directory is for the storage of temporary files. The contents are deleted on every system boot."
But I don't know if this is always the case.
You can set that delete-tmp-on-reboot option using YaST. The old yast has it in the edit rc.config menu The new one has it as one of the sysconfig (?) options.
There is one limitation: the `sticky bit' is switched on. (Notice the t at the end of the first column.) This means a user can only delete or rename files owned by himself. This prohibits users peskering each other by removing the other one's temporary files."
-K
-- opinions personal, facts suspect. http://home.arcor.de/36bit/samba.html
participants (5)
-
Andrew Williams -
Ben Rosenberg -
K Pfeiffer -
Kevin McLauchlan -
KMcLauchlan＠chrysalis-its.com