On Wed, Feb 4, 2009 at 4:18 PM, Greg Freemyer wrote:

On Wed, Feb 4, 2009 at 3:26 PM, Will Stephenson wrote:

...

On Wednesday 04 February 2009 20:58:34 Greg Freemyer wrote:

...

I'm using kmail from the factory KDE 4.2 repository.

I just setup kmail to use imap to work with my gmail account.

The setup went smooth enough, but I've had kmail segfault about 5 times in the 15 minutes or so of real usage I've had.

Am I wasting my time in this experiment, or do people have this working?

I've been using KMail with gmail imap in both KDE 3 and KDE 4 versions without problems. Would you mind installing the debuginfo packages listed at http://en.opensuse.org/Bugs:KDE (or at the very least kdepim4-debuginfo) and report a bug assigned to me with the resulting backtraces, and/or tell me what you're doing to make it segfault? Then I can route it to the upstream maintainer, who is an openSUSE user and very responsive.

Will

Will,

I'll keep testing, but I did install the debuginfo's. But now it seems to be working better. Still very non-responsive.

The big issue may be that my gmail account is pretty big. I bet I have 50,000 or so emails in it.

So kmail is trying to pull all of those emails / folders. When it was crashing, I was highlighting a message subject for which the body was not displaying and clicking delete. Or I was moving a similar email to the gmail - all_mail folder.

I had seg faults in both of those scenarios.

If I do get another seg fault I file the bugzilla for you.

Will, I stepped away from my desk for an hour or so. When I came back I saw a seg fault, but no back trace. == Unable to create a valid backtrace. 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. == I had the debuginfo's installed and I exited and restarted kmail after installing them. I had not logged out / logged in. Is there something else I need to do get a good backtrace? FYI: I also just upgraded to kde4-kmail-4.2.0-86.6, but I was already at 4.2.0-85 before. Greg -- Greg Freemyer Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Wed, Feb 4, 2009 at 5:53 PM, Will Stephenson wrote:

On Wednesday 04 February 2009 23:44:37 Greg Freemyer wrote:

...

Will,

I stepped away from my desk for an hour or so.

When I came back I saw a seg fault, but no back trace.

== Unable to create a valid backtrace.

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. ==

I had the debuginfo's installed and I exited and restarted kmail after installing them. I had not logged out / logged in.

Is there something else I need to do get a good backtrace?

FYI: I also just upgraded to kde4-kmail-4.2.0-86.6, but I was already at 4.2.0-85 before.

The number after the dash is autoincremented by the Build Service whenever it rebuilds, even when it's just due to a dependency up the chain rebuilding, so it's pretty information-free.

To get a good backtrace, you can either go through your packages that you have debuginfo now and ensure that the version number exactly matches that of the actual package (including the bit after the dash ;)), that might work, or you can run kmail in gdb. Install that, then

# gdb --args kmail --nofork .... (lots of gdb startup blurb)

...

run

.... (wait for a crash)

...

bt

.... (lots of backtrace output, this is the useful stuff I need)

...

quit

IF kmail doesn't crash and you need to get rid of gdb for some reason, just quit kmail, and quit gdb. Or interrupt kmail with a ctrl-c in the shell where gdb is running, 'detach' and 'quit'.

I hope that's not too technical.

Will

rpm -qa | grep debuginfo kdebase4-runtime-debuginfo-4.2.0-76.5 kdepimlibs4-debuginfo-4.2.0-1.15 kdebase4-workspace-debuginfo-4.2.0-184.11 kdelibs4-debuginfo-4.2.0-84.1

I used to be programmer, so it is interesting to pop into gdb. But I think something is still wrong: === gdb --args kmail --nofork GNU gdb (GDB; openSUSE 11.1) 6.8.50.20081120-cvs Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-suse-linux". For bug reporting instructions, please see: http://bugs.opensuse.org/... (no debugging symbols found) (gdb) run Starting program: /usr/bin/kmail --nofork (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) ... === Kmail start up and runs, but it still looks like I don't have any debug info for a trace. I do have the following installed: libqt4-debuginfo-4.4.3-38.1 Is the above expected? Greg -- Greg Freemyer Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Wed, Feb 4, 2009 at 6:21 PM, Will Stephenson wrote:

On Thursday 05 February 2009 00:01:27 Greg Freemyer wrote:

...

(no debugging symbols found)

gdb will print this every time it encounters a library for which it has no debug symbols. You've only installed the debuginfo for the most likely candidates, so this is normal.

...

...

rpm -qa | grep debuginfo

kdebase4-runtime-debuginfo-4.2.0-76.5 kdepimlibs4-debuginfo-4.2.0-1.15 kdebase4-workspace-debuginfo-4.2.0-184.11 kdelibs4-debuginfo-4.2.0-84.1 libqt4-debuginfo-4.4.3-38.1

rpm -q kdebase4-runtime kdepimlibs4-debuginfo kdebase4-workspace-debuginfo kdelibs4-debuginfo libqt4-debuginfo

too and check the numbers match. Oh and kdepim4-debuginfo is the most important of all. I'm sorry if that wasn't clear.

Will

I assumed that is one one of the ones in the list at http://en.opensuse.org/Bugs:KDE Not so. I have everything in sync and kmail running from gdb. I'll see if it is still running in the morning. Greg -- Greg Freemyer Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Will, Someone at Novell (Suse) bumped this to high priority / critical several days ago. Is there any activity? Greg On Thu, Feb 5, 2009 at 2:19 PM, Greg Freemyer wrote:

Done,

See https://bugzilla.novell.com/show_bug.cgi?id=473015

Will, Someone at Novell (Suse) bumped this to high priority / critical several days ago. Is there any activity? FYI: I just added a backtrace from kmail seg faulting while in imap disconnected mode. Still using my gmail mailbox as the imap server. Greg -- Greg Freemyer Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Wed, Feb 4, 2009 at 3:32 PM, Pete Connolly wrote:

On Wednesday 04 Feb 2009 19:58:34 Greg Freemyer wrote:

...

All,

I'm using kmail from the factory KDE 4.2 repository.

I just setup kmail to use imap to work with my gmail account.

The setup went smooth enough, but I've had kmail segfault about 5 times in the 15 minutes or so of real usage I've had.

Am I wasting my time in this experiment, or do people have this working?

Thanks Greg HI Greg

I'm using kmail 4.2.0-86.5 with 4 disconnected IMAP accounts and 1 pop3 one with no problems, although I had a few issues just prior to the 4.2 release. I'm using imap.googlemail.com as the incoming IMAP server on port 993, with SSL enabled and the authentication method set to 'Clear Text'. Outgoing mail is to smtp.googlemail.com via SSL on port 465 and this works well.

I do get problems with synching once in a while where gmail tells me certain folders don't exist, or I don't have rights to access them. Sometimes I can't authenticate but these all seem to be transient server side errors.

If you'd like to compare any version of installed rpms, drop me a line. It's certainly possible for it to work, but it might just need a tweak or two.

Cheers

Pete

I suspect the "disconnected" mode may be the secret. I'm not using that. I'll install the debuginfo packages and file a bug. Then try it in disconnected mode. Thanks Greg -- Greg Freemyer Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org