I am restoring my KMail details from Lenny with KDE 3.5.10 to Squeeze with TDE 3.5.13, patched with Slávek's patches.
I have copied .kde/share/apps/kmail from my backup to .trinity/share/apps/kmail. It wasn't a success.
The klauncher didn't do anything. (At least, it probably did, but I have no way of knowing what!!)
I then launched it by various methods, which are self explanatory. Finally, I launched it from the menu, and got the backtrace (or lack of it) below.
It's pretty obvious that I have copied something across during the restauration that has gummed up the works. But how do I find out what? Or should I simply delete all the files that are there and start again, but if so, how?
I gummed up kdm-trinity as well, but have managed to sort that out via Google. This one I am failing with.
Once I get this installation going I'll try to be trouble-free, or at least quiet, for some time! :-(
root@Tux-II:/home/lisi# kmail Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed WeaverThreadLogger: thread (ID: 3) suspended. WeaverThreadLogger: thread (ID: 2) suspended. WeaverThreadLogger: thread (ID: 1) suspended. WeaverThreadLogger: thread (ID: 4) suspended. root@Tux-II:/home/lisi# Weaver dtor: destroying inventory. WeaverThreadLogger: thread (ID: 1) destroyed. WeaverThreadLogger: thread (ID: 2) destroyed. WeaverThreadLogger: thread (ID: 3) destroyed. WeaverThreadLogger: thread (ID: 4) destroyed. Weaver dtor: done ^C root@Tux-II:/home/lisi# su lisi lisi@Tux-II:~$ kmail bash: kmail: command not found lisi@Tux-II:~$ whereis kmail kmail: /opt/trinity/bin/kmail lisi@Tux-II:~$ /opt/trinity/bin/kmail No protocol specified kmail: cannot connect to X server :0 lisi@Tux-II:~$ --------------------------------------------------
root@Tux-II:/home/lisi# kmail bash: kmail: command not found root@Tux-II:/home/lisi# /opt/trinity/bin/kmail Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed WeaverThreadLogger: thread (ID: 1) suspended. WeaverThreadLogger: thread (ID: 3) suspended. WeaverThreadLogger: thread (ID: 2) suspended. WeaverThreadLogger: thread (ID: 4) suspended. root@Tux-II:/home/lisi# QObject::disconnect: Unexpected null parameter QObject::connect: Cannot connect (null)::activePartChanged( KParts::Part * ) to KHTMLPart::slotActiveFrameChanged( KParts::Part * ) Weaver dtor: destroying inventory. WeaverThreadLogger: thread (ID: 1) destroyed. WeaverThreadLogger: thread (ID: 2) destroyed. WeaverThreadLogger: thread (ID: 3) destroyed. WeaverThreadLogger: thread (ID: 4) destroyed. Weaver dtor: done
----------------------------------------
This backtrace appears to be of no use. This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.
On Monday 24 of September 2012 01:03:29 Lisi Reisz wrote:
I am restoring my KMail details from Lenny with KDE 3.5.10 to Squeeze with TDE 3.5.13, patched with Slávek's patches.
I have copied .kde/share/apps/kmail from my backup to .trinity/share/apps/kmail. It wasn't a success.
The klauncher didn't do anything. (At least, it probably did, but I have no way of knowing what!!)
I then launched it by various methods, which are self explanatory. Finally, I launched it from the menu, and got the backtrace (or lack of it) below.
It's pretty obvious that I have copied something across during the restauration that has gummed up the works. But how do I find out what? Or should I simply delete all the files that are there and start again, but if so, how?
I gummed up kdm-trinity as well, but have managed to sort that out via Google. This one I am failing with.
Once I get this installation going I'll try to be trouble-free, or at least quiet, for some time! :-(
root@Tux-II:/home/lisi# kmail Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed WeaverThreadLogger: thread (ID: 3) suspended. WeaverThreadLogger: thread (ID: 2) suspended. WeaverThreadLogger: thread (ID: 1) suspended. WeaverThreadLogger: thread (ID: 4) suspended. root@Tux-II:/home/lisi# Weaver dtor: destroying inventory. WeaverThreadLogger: thread (ID: 1) destroyed. WeaverThreadLogger: thread (ID: 2) destroyed. WeaverThreadLogger: thread (ID: 3) destroyed. WeaverThreadLogger: thread (ID: 4) destroyed. Weaver dtor: done ^C root@Tux-II:/home/lisi# su lisi lisi@Tux-II:~$ kmail bash: kmail: command not found lisi@Tux-II:~$ whereis kmail kmail: /opt/trinity/bin/kmail lisi@Tux-II:~$ /opt/trinity/bin/kmail No protocol specified kmail: cannot connect to X server :0 lisi@Tux-II:~$
root@Tux-II:/home/lisi# kmail bash: kmail: command not found root@Tux-II:/home/lisi# /opt/trinity/bin/kmail Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed WeaverThreadLogger: thread (ID: 1) suspended. WeaverThreadLogger: thread (ID: 3) suspended. WeaverThreadLogger: thread (ID: 2) suspended. WeaverThreadLogger: thread (ID: 4) suspended. root@Tux-II:/home/lisi# QObject::disconnect: Unexpected null parameter QObject::connect: Cannot connect (null)::activePartChanged( KParts::Part * ) to KHTMLPart::slotActiveFrameChanged( KParts::Part * ) Weaver dtor: destroying inventory. WeaverThreadLogger: thread (ID: 1) destroyed. WeaverThreadLogger: thread (ID: 2) destroyed. WeaverThreadLogger: thread (ID: 3) destroyed. WeaverThreadLogger: thread (ID: 4) destroyed. Weaver dtor: done
This backtrace appears to be of no use. This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.
Lisi,
in the configuration files from KDE 3.5.10 may be used .kde/share and /usr/share. It is necessary to change these settings to .trinity/share and /opt/trinity/share.
Note: The identities for KMail are in .trinity/share/config/emailidentities.
Slávek --
On Sunday 23 September 2012 3:24:38 pm Slávek Banko wrote:
On Monday 24 of September 2012 01:03:29 Lisi Reisz wrote:
I am restoring my KMail details from Lenny with KDE 3.5.10 to Squeeze with TDE 3.5.13, patched with Slávek's patches.
I have copied .kde/share/apps/kmail from my backup to .trinity/share/apps/kmail. It wasn't a success.
The klauncher didn't do anything. (At least, it probably did, but I have no way of knowing what!!)
I then launched it by various methods, which are self explanatory. Finally, I launched it from the menu, and got the backtrace (or lack of it) below.
It's pretty obvious that I have copied something across during the restauration that has gummed up the works. But how do I find out what? Or should I simply delete all the files that are there and start again, but if so, how?
I gummed up kdm-trinity as well, but have managed to sort that out via Google. This one I am failing with.
Once I get this installation going I'll try to be trouble-free, or at least quiet, for some time! :-(
root@Tux-II:/home/lisi# kmail Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed WeaverThreadLogger: thread (ID: 3) suspended. WeaverThreadLogger: thread (ID: 2) suspended. WeaverThreadLogger: thread (ID: 1) suspended. WeaverThreadLogger: thread (ID: 4) suspended. root@Tux-II:/home/lisi# Weaver dtor: destroying inventory. WeaverThreadLogger: thread (ID: 1) destroyed. WeaverThreadLogger: thread (ID: 2) destroyed. WeaverThreadLogger: thread (ID: 3) destroyed. WeaverThreadLogger: thread (ID: 4) destroyed. Weaver dtor: done ^C root@Tux-II:/home/lisi# su lisi lisi@Tux-II:~$ kmail bash: kmail: command not found lisi@Tux-II:~$ whereis kmail kmail: /opt/trinity/bin/kmail lisi@Tux-II:~$ /opt/trinity/bin/kmail No protocol specified kmail: cannot connect to X server :0 lisi@Tux-II:~$
Looks like you logged in as root, su to lisi. user lisi will not be able to connect to X server. not sure if that is the only issue.
When I want to let a user, other than the one that is logged in, I use xhost to grqant access to the X server.
'xhost +local:<user>'
hopefully on topic.
root@Tux-II:/home/lisi# kmail bash: kmail: command not found root@Tux-II:/home/lisi# /opt/trinity/bin/kmail Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed WeaverThreadLogger: thread (ID: 1) suspended. WeaverThreadLogger: thread (ID: 3) suspended. WeaverThreadLogger: thread (ID: 2) suspended. WeaverThreadLogger: thread (ID: 4) suspended. root@Tux-II:/home/lisi# QObject::disconnect: Unexpected null parameter QObject::connect: Cannot connect (null)::activePartChanged( KParts::Part * ) to KHTMLPart::slotActiveFrameChanged( KParts::Part * ) Weaver dtor: destroying inventory. WeaverThreadLogger: thread (ID: 1) destroyed. WeaverThreadLogger: thread (ID: 2) destroyed. WeaverThreadLogger: thread (ID: 3) destroyed. WeaverThreadLogger: thread (ID: 4) destroyed. Weaver dtor: done
This backtrace appears to be of no use. This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.
Lisi,
in the configuration files from KDE 3.5.10 may be used .kde/share and /usr/share. It is necessary to change these settings to .trinity/share and /opt/trinity/share.
Note: The identities for KMail are in .trinity/share/config/emailidentities.
Slávek
On Monday 24 September 2012 00:24:38 Slávek Banko wrote:
On Monday 24 of September 2012 01:03:29 Lisi Reisz wrote:
I am restoring my KMail details from Lenny with KDE 3.5.10 to Squeeze with TDE 3.5.13, patched with Slávek's patches.
in the configuration files from KDE 3.5.10 may be used .kde/share and /usr/share. It is necessary to change these settings to .trinity/share and /opt/trinity/share.
Note: The identities for KMail are in .trinity/share/config/emailidentities.
Thanks, Slávek. I have followed this advice, and things are now better. TDE will open properly, and so at last will KMail. But I have still not got my folders and data.
Last time I tried to run Trinity on Squeeze on my desktop, I gave up and went back to Lenny and KDE 3.5.10 precisely because of this problem. I can't afford to lose the whole bang shoot. Identities I can re-enter, connection details I can re-enter. The folder structure and emails are important to me.
Sadly, retreat back to Lenny is no longer realistically an option.
I have for now retreated back to my old computer. I am doing an online course and being cut off from emails for days is not really an option.
So any data I have managed to transfer across will have to be retransferred.
Have I got to the end of the line?
Lisi
Dne út 25. září 2012 Lisi napsal(a):
Thanks, Slávek. I have followed this advice, and things are now better. TDE will open properly, and so at last will KMail. But I have still not got my folders and data.
Last time I tried to run Trinity on Squeeze on my desktop, I gave up and went back to Lenny and KDE 3.5.10 precisely because of this problem. I can't afford to lose the whole bang shoot. Identities I can re-enter, connection details I can re-enter. The folder structure and emails are important to me.
Sadly, retreat back to Lenny is no longer realistically an option.
I have for now retreated back to my old computer. I am doing an online course and being cut off from emails for days is not really an option.
So any data I have managed to transfer across will have to be retransferred.
Have I got to the end of the line?
Lisi
By the time I passed from Lenny + KDE 3.5.10 to Squeeze + TDE 3.5.12, I simply rename folder ".kde" to ".trinity" and replaced references ".kde" and "/usr/share" in the configuration files in ".trinity".
Slavek --
On Tuesday 25 September 2012 17:07:58 Lisi wrote:
On Monday 24 September 2012 00:24:38 Slávek Banko wrote:
On Monday 24 of September 2012 01:03:29 Lisi Reisz wrote:
I am restoring my KMail details from Lenny with KDE 3.5.10 to Squeeze with TDE 3.5.13, patched with Slávek's patches.
in the configuration files from KDE 3.5.10 may be used .kde/share and /usr/share. It is necessary to change these settings to .trinity/share and /opt/trinity/share.
Note: The identities for KMail are in .trinity/share/config/emailidentities.
Thanks, Slávek. I have followed this advice, and things are now better. TDE will open properly, and so at last will KMail. But I have still not got my folders and data.
Last time I tried to run Trinity on Squeeze on my desktop, I gave up and went back to Lenny and KDE 3.5.10 precisely because of this problem. I can't afford to lose the whole bang shoot. Identities I can re-enter, connection details I can re-enter. The folder structure and emails are important to me.
Sadly, retreat back to Lenny is no longer realistically an option.
I have for now retreated back to my old computer. I am doing an online course and being cut off from emails for days is not really an option.
So any data I have managed to transfer across will have to be retransferred.
Have I got to the end of the line?
Lisi
Istr that the default location for the 'root' kmail folder has changed in TDE; in KDE it was ~/Mail but iirc it has been moved to somewhere in the ~/.trinity folder. I had to edit ~/.trinity/share/config/kmailrc to set it back to ~/Mail (as this was an NFS mount on my server and I didn't want to have to change it).
Have a look in the kmailrc file - search for the string "[General]" and then check to see where 'folders[$e]' is pointing.
LeeE
On 25 September 2012 19:53, leee leee@spatial.plus.com wrote:
On Tuesday 25 September 2012 17:07:58 Lisi wrote:
On Monday 24 September 2012 00:24:38 Slávek Banko wrote:
On Monday 24 of September 2012 01:03:29 Lisi Reisz wrote:
I am restoring my KMail details from Lenny with KDE 3.5.10 to Squeeze with TDE 3.5.13, patched with Slávek's patches.
in the configuration files from KDE 3.5.10 may be used .kde/share and /usr/share. It is necessary to change these settings to .trinity/share and /opt/trinity/share.
Note: The identities for KMail are in .trinity/share/config/emailidentities.
Thanks, Slávek. I have followed this advice, and things are now better. TDE will open properly, and so at last will KMail. But I have still not got my folders and data.
So any data I have managed to transfer across will have to be retransferred.
Istr that the default location for the 'root' kmail folder has changed in TDE; in KDE it was ~/Mail but iirc it has been moved to somewhere in the ~/.trinity folder. I had to edit ~/.trinity/share/config/kmailrc to set it back to ~/Mail (as this was an NFS mount on my server and I didn't want to have to change it).
Have a look in the kmailrc file - search for the string "[General]" and then check to see where 'folders[$e]' is pointing.
folders[$e]=$HOME/Mail
In view of Tim's warning, dare I try to open KMail yet?
Thanks, Lisi
:-))
Several....
The fact that I am paranoid does not mean that they are not out to get me!
Lisi
Hi again!
On 29 September 2012 23:00, Lisi Reisz lisi.reisz@gmail.com wrote:
On 25 September 2012 19:53, leee leee@spatial.plus.com wrote:
On Tuesday 25 September 2012 17:07:58 Lisi wrote:
On Monday 24 September 2012 00:24:38 Slávek Banko wrote:
On Monday 24 of September 2012 01:03:29 Lisi Reisz wrote:
I am restoring my KMail details from Lenny with KDE 3.5.10 to Squeeze with TDE 3.5.13, patched with Slávek's patches.
then check to see where 'folders[$e]' is pointing.
folders[$e]=$HOME/Mail
The email, to which this is a reply, had been sitting there waiting to be sent, and I clicked send a little too automatically just now. I actually wrote it many hours ago and I have since tried to open KMail.
Although it is clearly finding the right folder, it is not opening. I get the following error message: ----------------------------------------------------
Problem with mail indices - KMail
There is a problem with the mail index of the following folders, the indices will now be regenerated.
This can happen because the index files are out of date, missing or corrupted.
Contact your administrator if this happens frequently.
Some information, like status flags might get lost. ___________________________
Debian inbox SouthWalesLUG Shopping _________________________
Since both Werner (on a previous occasion) and every reference I followed up in Google said that indices could be removed and would regenerate, I have been trying to delete them and get KMail to regenerate them. I have used Werner's
rm -rf *.index
command - several times , for good measure. I have been through my Debian, inbox, SouthWalesLUG and Shopping folders individually. I am now going manually through everything. I know that there were index files, but have not so far found a single one on my manual trawl.
This is ridiculous. So near and yet so far...
Since indices are clearly the problem, one way or another, and everyone seems to agree that indices can be deleted and will then regenerate, this _must_ be soluble.
Has any of you helpful people any idea what I could try next? (Apart from finishing the very slow hand-trawl through.)
Lisi
On Saturday 29 September 2012 23:33:40 Lisi Reisz wrote:
Hi again!
On 29 September 2012 23:00, Lisi Reisz lisi.reisz@gmail.com wrote:
On 25 September 2012 19:53, leee leee@spatial.plus.com wrote:
On Tuesday 25 September 2012 17:07:58 Lisi wrote:
On Monday 24 September 2012 00:24:38 Slávek Banko wrote:
On Monday 24 of September 2012 01:03:29 Lisi Reisz wrote:
I am restoring my KMail details from Lenny with KDE 3.5.10 to Squeeze with TDE 3.5.13, patched with Slávek's patches.
then check to see where 'folders[$e]' is pointing.
folders[$e]=$HOME/Mail
The email, to which this is a reply, had been sitting there waiting to be sent, and I clicked send a little too automatically just now. I actually wrote it many hours ago and I have since tried to open KMail.
Although it is clearly finding the right folder, it is not opening. I get the following error message:
Problem with mail indices - KMail
There is a problem with the mail index of the following folders, the indices will now be regenerated.
This can happen because the index files are out of date, missing or corrupted.
Contact your administrator if this happens frequently.
Some information, like status flags might get lost. ___________________________
Debian inbox SouthWalesLUG Shopping _________________________
Since both Werner (on a previous occasion) and every reference I followed up in Google said that indices could be removed and would regenerate, I have been trying to delete them and get KMail to regenerate them. I have used Werner's
rm -rf *.index
command - several times , for good measure. I have been through my Debian, inbox, SouthWalesLUG and Shopping folders individually. I am now going manually through everything. I know that there were index files, but have not so far found a single one on my manual trawl.
This is ridiculous. So near and yet so far...
Since indices are clearly the problem, one way or another, and everyone seems to agree that indices can be deleted and will then regenerate, this _must_ be soluble.
Has any of you helpful people any idea what I could try next? (Apart from finishing the very slow hand-trawl through.)
Lisi
Hmm... strange problem - I've had the index rebuilding message, after doing something similar to what you've done, but the indexes were simply rebuilt; I didn't have to delete anything and don't recall have problems opening any of the sub-folders under the top level 'Local Folders'.
As you've already deleted the *.index files then perhaps you should also delete the *.index.ids & *.index.sorted files too.
Have you checked the ownership and permissions of all the files & folders in your ~/Mail folder? If you've done everything i.e. backing up and any copying under the same user then it shouldn't be an issue but as it's quite an odd problem it needs to be checked.
LeeE
Lisi, Try deleting index files recursively, e.g. using find command, piped through xargs. Sorry for top-psting (k9 mail on android tablet...) Werner
Lisi Reisz lisi.reisz@gmail.com schrieb:
Hi again!
On 29 September 2012 23:00, Lisi Reisz lisi.reisz@gmail.com wrote:
On 25 September 2012 19:53, leee leee@spatial.plus.com wrote:
On Tuesday 25 September 2012 17:07:58 Lisi wrote:
On Monday 24 September 2012 00:24:38 Slávek Banko wrote:
On Monday 24 of September 2012 01:03:29 Lisi Reisz wrote:
I am restoring my KMail details from Lenny with KDE 3.5.10 to
Squeeze
with TDE 3.5.13, patched with Slávek's patches.
then check to see where 'folders[$e]' is pointing.
folders[$e]=$HOME/Mail
The email, to which this is a reply, had been sitting there waiting to be sent, and I clicked send a little too automatically just now. I actually wrote it many hours ago and I have since tried to open KMail.
Although it is clearly finding the right folder, it is not opening. I get the following error message:
Problem with mail indices - KMail
There is a problem with the mail index of the following folders, the indices will now be regenerated.
This can happen because the index files are out of date, missing or corrupted.
Contact your administrator if this happens frequently.
Some information, like status flags might get lost. ___________________________
Debian inbox SouthWalesLUG Shopping _________________________
Since both Werner (on a previous occasion) and every reference I followed up in Google said that indices could be removed and would regenerate, I have been trying to delete them and get KMail to regenerate them. I have used Werner's
rm -rf *.index
command - several times , for good measure. I have been through my Debian, inbox, SouthWalesLUG and Shopping folders individually. I am now going manually through everything. I know that there were index files, but have not so far found a single one on my manual trawl.
This is ridiculous. So near and yet so far...
Since indices are clearly the problem, one way or another, and everyone seems to agree that indices can be deleted and will then regenerate, this _must_ be soluble.
Has any of you helpful people any idea what I could try next? (Apart from finishing the very slow hand-trawl through.)
Lisi
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On 30 September 2012 15:04, Werner Joss werner@hoernerfranzracing.de wrote:
Lisi, Try deleting index files recursively, e.g. using find command, piped through xargs. Sorry for top-psting (k9 mail on android tablet...) Werner
And I can't sort it out for you because I am using Gmail. :-( I really don't like the Gmail interface. :-( It's great, though, for POP3 and an archive!
I think that I have done that in the last few hours, but I'll try again. Plus a whole lot of other things. Since they didn't work I shan't document them But then I shall just have to give up on this approach. I need to regain my old box to put Fedora and Slackware on for the course I am doing, and rapidly dropping further and further behind. I'll get myself back to square one (ouch again), try the tarring method suggested earlier in this thread, and if that fails, just give up and use a new instance of KMail. I am sad that this should be necessary when I have all the emails and folders, but there is obviously something that is causing this problem somewhere in the Mail folder.
Addendum some hours later: I shall not do this immediately because I am falling seriously behind on this course that I am doing. So I shall mothball the computer with my precious mails on, and use the monitor, keyboard and mouse, currently attached to it, to use my netbook as a desktop for now so that I can install and de-install to my heart's (and course's) content.
Thanks so much for all the help so far. Lisi
On 30 September 2012 21:51, Lisi Reisz lisi.reisz@gmail.com wrote:
On 30 September 2012 15:04, Werner Joss werner@hoernerfranzracing.de wrote:
Lisi, Try deleting index files recursively, e.g. using find command, piped
through
xargs. Sorry for top-psting (k9 mail on android tablet...) Werner
I just can't leave this alone. :-(
Does this error message shed any light?
lisi@Tux-II:~$ kmail WeaverThreadLogger: thread (ID: 1) suspended. WeaverThreadLogger: thread (ID: 4) suspended. WeaverThreadLogger: thread (ID: 3) suspended. WeaverThreadLogger: thread (ID: 2) suspended. kmail: /build/buildd/kdepim-trinity-3.5.13/kmail/kmmsgbase.cpp:1273: off_t KMMsgBase::getLongPart(KMMsgBase::MsgPartType) const: Assertion `sizeOfLong == l' failed. *** KMail got signal 6 (Crashing) KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kmail path = <unknown> pid = 2561 lisi@Tux-II:~$
Thanks so much for all the help so far.
Lisi
Has any of you helpful people any idea what I could try next? (Apart from finishing the very slow hand-trawl through.)
I just noticed that KMail on KDE3 has "Import mail" command in File menu and it allows to import KMail's mail directory. Maybe this is a stupid question, but have you tried this?
Jan
On 2 October 2012 15:38, Janek S. fremenzone@poczta.onet.pl wrote:
Has any of you helpful people any idea what I could try next? (Apart from finishing the very slow hand-trawl through.)
I just noticed that KMail on KDE3 has "Import mail" command in File menu and it allows to import KMail's mail directory. Maybe this is a stupid question, but have you tried this?
Stupid people need stupid questions... I hang my head. Unfortunately, I can't now try it because KMail-trinity now crashes as soon as I try to open it. I need to get back somehow to square one with it. But when I do, I shall immediately try your suggestion - and kick myself hard again.
(The obvious thing to try first is reinstate the default in kmailrc.)
Thanks so much Jan,
Lisi
Stupid people need stupid questions... I hang my head. Unfortunately, I can't now try it because KMail-trinity now crashes as soon as I try to open it. I need to get back somehow to square one with it. But when I do, I shall immediately try your suggestion - and kick myself hard again.
(The obvious thing to try first is reinstate the default in kmailrc.)
If I were in your situation I would try to remove all KMail's config files: ~/.trinity/share/apps/kmail/* ~/itrinity/share/config/emaildefaults ~/itrinity/share/config/emailidentities ~/itrinity/share/config/kmailrc* ~/Mail (or any other directory that contains your emails). By removing I mean of course moving them to different location, so they can be restored. I would hope that KMail will simple recreate those files and then you could try to import emails from old KDE3 directory.
I don't claim that this will work, but that's what I would try.
Jan
On Tuesday 02 October 2012 18:13:30 Janek S. wrote:
Stupid people need stupid questions... I hang my head. Unfortunately, I can't now try it because KMail-trinity now crashes as soon as I try to open it. I need to get back somehow to square one with it. But when I do, I shall immediately try your suggestion - and kick myself hard again.
(The obvious thing to try first is reinstate the default in kmailrc.)
If I were in your situation I would try to remove all KMail's config files: ~/.trinity/share/apps/kmail/* ~/itrinity/share/config/emaildefaults ~/itrinity/share/config/emailidentities ~/itrinity/share/config/kmailrc* ~/Mail (or any other directory that contains your emails). By removing I mean of course moving them to different location, so they can be restored. I would hope that KMail will simple recreate those files and then you could try to import emails from old KDE3 directory.
I don't claim that this will work, but that's what I would try.
Sadly, I had already done something different by the time I read this. But if I could grab you and kiss you down the internet I would! I have nearly everything intact. I am having to do a bit of moving around and the settings need redoing, but I have my folders, my filters, so far as I can see all my emails - in other words, maybe not as good as it could have been but entirely acceptable and _far_ better than I was trying to get resigned to!
Many, many thanks, and of course repeated heartfelt thanks to the rest of you who gave me so much help, Lisi