11:42 p.m.
When Kmail crashes, as it often does, it just goes "poof". Regardless
of if run directly or via Kontact. With or without kdepim-debuginfo,
and even if run from Konsole.
As of tonight it crashed once, and now just won't open messages I
click on, with no visible errors.
--
Fedora 9 : sulphur is good for the skin
( www.pembo13.com )
7:38 a.m.
On Sat March 21 2009, Arthur Pemberton wrote:
When Kmail crashes, as it often does, it just goes "poof".
Regardless
of if run directly or via Kontact. With or without kdepim-debuginfo,
and even if run from Konsole.
As of tonight it crashed once, and now just won't open messages I
click on, with no visible errors.
I've had this happen with individual messages. One message would be
problematic, and it was a real pain to get around (I'd have to find a way to
mark it read without entering the folder or some such...) I can't say what
fixed the issue, but, I would guess it may have been an update.
Parenthetically, I'd gotten to the point where I was beginning to cast about
for alternatives to Kmail, even though it's feature set makes it my favored
email client. I even set up Evolution on a recent VM just to see if it had
improved (it hadn't - so many little things in Kmail that makes it extremely
configurable and fast are missing in Evolution). Several issues I've brought
up on the list were beginning to drive me crazy, such as the extremely long
indexing operation that went on everytime I entered a new folder (up to over
ten seconds at one point, and I have about 30 folders in any given
installation)... Suddenly, all these problem appear to have vanished. Kmail
has stopped crashing, browsing from folder to folder has become nearly
instantaneous, etc... I wish I could offer more, but, I haven't any idea why
this has improved so dramatically...I will say that on this particular
machine, I recently moved my drives from an older dual-core CPU with one GB of
ram, to a much newer quad-core with 4 GB - it this is the sole reason for my
Kmail issues going away, that says one thing. I'll have to check my other
machines later to see if that's the case.
--
Claude Jones
Brunswick, MD, USA
9:44 a.m.
On Monday 23 March 2009 12:38:59 Claude Jones wrote:
I've had this happen with individual messages. One message would
be
problematic, and it was a real pain to get around (I'd have to find a way
to mark it read without entering the folder or some such...) I can't say
what fixed the issue, but, I would guess it may have been an update.
FWIW, I had this problem with a particular message. The big problem was that
every time I tried to start it the cursor was on the bad message. The way I
got around the problem was to edit ~/.kde/share/config/kmailrc, [Behaviour]
section, setting ActionEnterFolder=SelectFirstNew - which puts me onto a
different message. Then I read all messages in the folder apart from the bad
one, and used the Folder context menu to mark all messages read.
Anne
--
New to KDE4? - get help from http://userbase.kde.org
Just found a cool new feature? Add it to UserBase
11:57 a.m.
On Monday 23 March 2009 16:44:57 Anne Wilson wrote:
On Monday 23 March 2009 12:38:59 Claude Jones wrote:
> I've had this happen with individual messages. One message would be
> problematic, and it was a real pain to get around (I'd have to find a way
> to mark it read without entering the folder or some such...) I can't say
> what fixed the issue, but, I would guess it may have been an update.
FWIW, I had this problem with a particular message. The big problem was that
every time I tried to start it the cursor was on the bad message. The way I
got around the problem was to edit ~/.kde/share/config/kmailrc, [Behaviour]
section, setting ActionEnterFolder=SelectFirstNew - which puts me onto a
different message. Then I read all messages in the folder apart from the bad
one, and used the Folder context menu to mark all messages read.
Anne
There should be no such thing as a "bad message which causes kmail to crash. Which
means that this is a bug. Which means it should be reported. If you haven't removed
the "bad message" don't. Please report this upstream.
Eli
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
2 p.m.
On Monday 23 March 2009 16:57:52 Eli Wapniarski wrote:
On Monday 23 March 2009 16:44:57 Anne Wilson wrote:
> On Monday 23 March 2009 12:38:59 Claude Jones wrote:
> > I've had this happen with individual messages. One message would be
> > problematic, and it was a real pain to get around (I'd have to find a
> > way to mark it read without entering the folder or some such...) I
> > can't say what fixed the issue, but, I would guess it may have been an
> > update.
>
> FWIW, I had this problem with a particular message. The big problem was
> that every time I tried to start it the cursor was on the bad message.
> The way I got around the problem was to edit ~/.kde/share/config/kmailrc,
> [Behaviour] section, setting ActionEnterFolder=SelectFirstNew - which
> puts me onto a different message. Then I read all messages in the folder
> apart from the bad one, and used the Folder context menu to mark all
> messages read.
>
> Anne
There should be no such thing as a "bad message which causes kmail to
crash. Which means that this is a bug. Which means it should be reported.
If you haven't removed the "bad message" don't. Please report this
upstream.
IIRC I discovered later that the problem was not in the message itself, but a
problem with the GPG signature of the message. I don't recall the details,
but GPG was choking on it. It has only happened once and that was a long,
long time ago.
Anne
--
New to KDE4? - get help from http://userbase.kde.org
Just found a cool new feature? Add it to UserBase
2:52 p.m.
On Monday 23 March 2009 15:44:57 Anne Wilson wrote:
FWIW, I had this problem with a particular message. The big problem was
that every time I tried to start it the cursor was on the bad message. The
way I got around the problem was to edit ~/.kde/share/config/kmailrc,
[Behaviour] section, setting ActionEnterFolder=SelectFirstNew - which puts
me onto a different message. Then I read all messages in the folder apart
from the bad one, and used the Folder context menu to mark all messages
read.
Anne
Did you file a bug report on bugs.kde.org? (it is still possible to create
useful backtraces even if the crash handler dialog does not appear).
--
Regards
Lorenzo Villani http://www.linkedin.com/in/lorenzovillani
Mobile: (+39) 34 00 88 42 49 Blog: http://people.binaryhelix.net/lvillani
GPG KeyID: 1024D/513BDC5C -- F348 B0B4 43C4 B4BB 0D8B 3612 72FE 265D 513B DC5C
SSH (RSA) Fingerprint: 0e:4d:d2:3f:4a:f0:9e:f9:a5:e6:26:05:71:a0:3c:ce
IRC Nicknames: FreeNode (irc.freenode.net:6667): lvillani
2:57 p.m.
On Monday 23 March 2009 19:52:29 Lorenzo Villani wrote:
On Monday 23 March 2009 15:44:57 Anne Wilson wrote:
> FWIW, I had this problem with a particular message. The big problem was
> that every time I tried to start it the cursor was on the bad message.
> The way I got around the problem was to edit ~/.kde/share/config/kmailrc,
> [Behaviour] section, setting ActionEnterFolder=SelectFirstNew - which
> puts me onto a different message. Then I read all messages in the folder
> apart from the bad one, and used the Folder context menu to mark all
> messages read.
>
> Anne
Did you file a bug report on bugs.kde.org? (it is still possible to create
useful backtraces even if the crash handler dialog does not appear).
No - I tend to file bugs only if I know I can reproduce them. Once I had
fixed that specific message problem it never happened again. I'm totally
convinced that it was a gpg problem, mal-formed key or something.
Anne
--
New to KDE4? - get help from http://userbase.kde.org
Just found a cool new feature? Add it to UserBase
7:34 p.m.
On Mon, Mar 23, 2009 at 2:57 PM, Anne Wilson <cannewilson(a)googlemail.com> wrote:
No - I tend to file bugs only if I know I can reproduce them. Once I
had
fixed that specific message problem it never happened again. I'm totally
convinced that it was a gpg problem, mal-formed key or something.
Which is why I posted here. KMail just goes "poof" when it crashes. No
console output. No known log files. No KCrash.
I can't file a bug saying that Kmail vanishes, sometimes.
--
Fedora 9 : sulphur is good for the skin
( www.pembo13.com )
12:18 a.m.
On Tuesday 24 March 2009 02:34:21 Arthur Pemberton wrote:
On Mon, Mar 23, 2009 at 2:57 PM, Anne Wilson
<cannewilson(a)googlemail.com> wrote:
> No - I tend to file bugs only if I know I can reproduce them. Once I had
> fixed that specific message problem it never happened again. I'm totally
> convinced that it was a gpg problem, mal-formed key or something.
Which is why I posted here. KMail just goes "poof" when it crashes. No
console output. No known log files. No KCrash.
I can't file a bug saying that Kmail vanishes, sometimes.
Yes you can. Indicate that you are willing to attach, of course if there isn't
anything confidential to in the folder to send the email file to them for their
inspeciton.
Eli
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
12:40 a.m.
On Tue, Mar 24, 2009 at 12:18 AM, Eli Wapniarski
<eli(a)orbsky.homelinux.org> wrote:
On Tuesday 24 March 2009 02:34:21 Arthur Pemberton wrote:
> On Mon, Mar 23, 2009 at 2:57 PM, Anne Wilson <cannewilson(a)googlemail.com>
> wrote:
> > No - I tend to file bugs only if I know I can reproduce them. Once I
> > had
> > fixed that specific message problem it never happened again. I'm
> > totally
> > convinced that it was a gpg problem, mal-formed key or something.
>
> Which is why I posted here. KMail just goes "poof" when it crashes. No
> console output. No known log files. No KCrash.
>
> I can't file a bug saying that Kmail vanishes, sometimes.
Yes you can. Indicate that you are willing to attach, of course if there
isn't anything confidential to in the folder to send the email file to them
for their inspeciton.
Eli
I haven't found a single email which I can use to replicate the problem 100%
--
Fedora 9 : sulphur is good for the skin
( www.pembo13.com )
2:03 a.m.
On Tuesday 24 March 2009 07:40:02 Arthur Pemberton wrote:
On Tue, Mar 24, 2009 at 12:18 AM, Eli Wapniarski
<eli(a)orbsky.homelinux.org> wrote:
> On Tuesday 24 March 2009 02:34:21 Arthur Pemberton wrote:
>> On Mon, Mar 23, 2009 at 2:57 PM, Anne Wilson <cannewilson(a)googlemail.com>
>> wrote:
>> > No - I tend to file bugs only if I know I can reproduce them. Once I
>> > had
>> > fixed that specific message problem it never happened again. I'm
>> > totally
>> > convinced that it was a gpg problem, mal-formed key or something.
>>
>> Which is why I posted here. KMail just goes "poof" when it crashes.
No
>> console output. No known log files. No KCrash.
>>
>> I can't file a bug saying that Kmail vanishes, sometimes.
>
> Yes you can. Indicate that you are willing to attach, of course if there
> isn't anything confidential to in the folder to send the email file to them
> for their inspeciton.
>
> Eli
I haven't found a single email which I can use to replicate the problem 100%
Communicate with the developers. If you don't it won't get fixed. Ask for
guidence to allow them to help you get the info they need. Be instant.
Look, as an aside (ok... a long aside), I know that you already know this, and that
I'm preaching to the choir, but opensource is a collaborative effort by the entire
community. Complaints and praises, bug reports, feature requests, shortcomings, winfalls,
etc. Its the only way that this particular enterprise works. If we aren't willing to
accept communications no matter how important or trivial it might seem this enterprise
fails. While we get a lovely sandbox for developers to try to showoff, if the end product
is not useful and therefore not used, well then so what. It becomes a practise in navel
gazing and now lets all get abused by Microsoft's non existant technical support.
Which of course 75% of the software on our computers will be pirated because, lets be
honest who has $20,000 (maybe I'm exagerating - but only just a little) to lay down on
OSes, Productivity Software, Games, Hardware, etc. Without the back and forth
communications however annoying or frustrating it may be, how do you expect the end result
to improve to remain stable, to remain reliable and secure.
Whether any developer likes it or not once its in the public domain its out there. It
becomes a service and people expect the software to work. And if it doesn't, well
then, of course, anyone and everyone is free to go elsewhere. The thing is, as everyone is
well aware of the statistics, they do. Because most users aren't willing to put up
with the rudeness that many developers exhibit when they are "interupted" by
another annoying bug report. I'm sure that everyone has gotten more than just a little
upset when someone has broken your focus while concentration on a challenging problem. I
tend not accept the rudeness and get rude right back. Things settle down, everybody has
vented and we roll up our sleeves and get the job done.
I'm a little bit old fashioned. I believe that striving for excellence has to be more
than just words. It doesn't mean perfect. It means lets get it do what its supposed to
do the best that we can. And if at first you don't succeed, try and try again.
Especially with things as worthwhile as opensource software and Linux.
Communicate with the developers. See what if anything they have to say. Its important.
Eli Wapniarski
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
9:49 a.m.
Hi Arthur,
On Monday 23 March 2009 20:34:21 Arthur Pemberton wrote:
Which is why I posted here. KMail just goes "poof" when it
crashes. No
console output. No known log files. No KCrash.
Could you *always* run kmail from an open konsole tab? I suspect that you may
be running into a binary incompatibility problem. If that is the case, a
message on konsole tab should appear stating that a certain symbol is not
found. Note that some shared libraries are loaded only on demand (because
something in a particular message requires the functionality). If kmail still
goes "poof", but no message appaears on the konsole tab, it will likely
require some help from strace, but we shall see.
Regards,
Ravi
2:54 p.m.
Forget my previous message. I'm so tired that I didn't notice the follow-up :)
--
Regards
Lorenzo Villani http://www.linkedin.com/in/lorenzovillani
Mobile: (+39) 34 00 88 42 49 Blog: http://people.binaryhelix.net/lvillani
GPG KeyID: 1024D/513BDC5C -- F348 B0B4 43C4 B4BB 0D8B 3612 72FE 265D 513B DC5C
SSH (RSA) Fingerprint: 0e:4d:d2:3f:4a:f0:9e:f9:a5:e6:26:05:71:a0:3c:ce
IRC Nicknames: FreeNode (irc.freenode.net:6667): lvillani
5511
days inactive
5514
days old
12 comments
6 participants
participants (6)
-
Anne Wilson -
Arthur Pemberton -
Claude Jones -
Eli Wapniarski -
Lorenzo Villani -
Ravi