Ubuntu
kdepim package

kmail crashes very oftenly on SPARC (other KDE apps crash too, but not so often)

Bug #26625 reported by Debian Bug Importer
12
Affects Status Importance Assigned to Milestone
kdepim (Debian)
Fix Released
Unknown
kdepim (Ubuntu)
Invalid
High
Kubuntu Bugs

Bug Description

Automatically imported from Debian bug report #342215 http://bugs.debian.org/342215

See original description
Revision history for this message
Debian Bug Importer (debzilla) wrote :

Automatically imported from Debian bug report #342215 http://bugs.debian.org/342215

Revision history for this message
Debian Bug Importer (debzilla) wrote :
Download full text (4.4 KiB)

Message-ID: <email address hidden>
Date: Tue, 06 Dec 2005 07:41:00 -0300
From: Martin Marques <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: kmail crashes very oftenly on SPARC (other KDE apps crash too,
 but not so often)

Package: kmail
Version: 4:3.4.2-2
Severity: critical
Justification: causes serious data loss

Since I upgraded KDE to 3.4.x, I'm getting unpleasant crashes on various KDE applications
but the most serious, because of the frecuency in which it happens is kmail.

The worst part is that, as kmail is compiled without debuging symbols, I can't debug
much on what's happening, and all I have are the signals with which it dies (4 "Illegal
Instruction", and 11 "Invalid memory reference").

*** KMail got signal 11 (Crashing)
KCrash: Application 'kmail' crashing...

And this doesn't happen when doing something especifically. For example, if I type to fast
when composing, it sometimes crashes. Also I got crashes when configuring kmail or filters.

Just a moment ago konsole died with no reason, and I wasn't even doing anything with it.

KCrash: Application 'konsole' crashing...

This is very annoying.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (800, 'testing'), (500, 'stable'), (50, 'unstable'), (40, 'experimental')
Architecture: sparc (sparc64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-2-sparc64
Locale: LANG=es_AR, LC_CTYPE=es_AR (charmap=ISO-8859-1)

Versions of packages kmail depends on:
ii kdebase-kio-plugins 4:3.4.2-4 core I/O slaves for KDE
ii kdelibs4c2 4:3.4.2-4 core libraries for all KDE applica
ii kdepim-kio-plugins 4:3.4.2-2 KDE pim I/O Slaves
ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi
ii libaudio2 1.7-3 The Network Audio System (NAS). (s
ii libc6 2.3.5-8 GNU C Library: Shared libraries an
ii libfontconfig1 2.3.2-1 generic font configuration library
ii libfreetype6 2.1.7-2.4 FreeType 2 font engine, shared lib
ii libgcc1 1:4.0.2-2 GCC support library
ii libice6 6.8.2.dfsg.1-7 Inter-Client Exchange library
ii libidn11 0.5.18-1 GNU libidn library, implementation
ii libjpeg62 6b-10 The Independent JPEG Group's JPEG
ii libkcal2b 4:3.4.2-2 KDE calendaring library
ii libkdepim1a 4:3.4.2-2 KDE PIM library
ii libkleopatra0a 4:3.4.2-2 KDE GnuPG interface libraries
ii libkmime2 4:3.4.2-2 KDE MIME interface library
ii libkpimidentities1 4:3.4.2-2 KDE PIM user identity information
ii libksieve0 4:3.4.2-2 KDE mail/news message filtering li
ii libmimelib1c2 4:3.4.2-2 KDE mime library
ii libpng12-0 1.2.8rel-5 PNG library - runtime
ii libqt3-mt 3:3.3.5-1 Qt GUI Library (Threaded runtime v
ii libsm6 6.8.2.dfsg.1-7 X Window System Session Management
...

Read more...

Revision history for this message
In , Steve Langasek (vorlon) wrote : usertags for RC bugs on non-RC archs

# use usertags so we can keep track of bugs that should be considered
# RC if and when these architectures become release candidates again
user <email address hidden>
severity 198075 important
usertag 198075 rc-m68k
severity 338433 important
usertag 338433 rc-m68k
severity 338707 important
severity 321435 important
merge 321435 338707
usertag 321435 rc-s390
severity 326905 important
usertag 326905 rc-m68k
severity 342757 important
usertag 342757 rc-sparc
severity 342758 important
usertag 342758 rc-sparc
severity 342760 important
usertag 342760 rc-sparc
severity 342215 important
usertag 342215 rc-sparc
severity 334239 important
usertag 334239 rc-m68k
severity 338443 important
usertag 338443 rc-m68k
severity 322027 important
usertag 322027 rc-m68k
severity 338297 important
usertag 338297 rc-m68k
severity 343460 important
usertag 343460 rc-arm
severity 333708 important
usertag 333708 rc-sparc
severity 330635 important
usertag 330635 rc-m68k
severity 332630 important
usertag 332630 rc-s390
severity 330159 important
usertag 330159 rc-arm
# libassa never built on s390, so this never should have been serious AFAICT
severity 332513 important
thanks

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
<email address hidden> http://www.debian.org/

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Tue, 27 Dec 2005 03:20:04 -0800
From: Steve Langasek <email address hidden>
To: <email address hidden>
Subject: usertags for RC bugs on non-RC archs

--YuJye9aIuN0w6xGV
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

# use usertags so we can keep track of bugs that should be considered
# RC if and when these architectures become release candidates again
user <email address hidden>
severity 198075 important
usertag 198075 rc-m68k
severity 338433 important
usertag 338433 rc-m68k
severity 338707 important
severity 321435 important
merge 321435 338707
usertag 321435 rc-s390
severity 326905 important
usertag 326905 rc-m68k
severity 342757 important
usertag 342757 rc-sparc
severity 342758 important
usertag 342758 rc-sparc
severity 342760 important
usertag 342760 rc-sparc
severity 342215 important
usertag 342215 rc-sparc
severity 334239 important
usertag 334239 rc-m68k
severity 338443 important
usertag 338443 rc-m68k
severity 322027 important
usertag 322027 rc-m68k
severity 338297 important
usertag 338297 rc-m68k
severity 343460 important
usertag 343460 rc-arm
severity 333708 important
usertag 333708 rc-sparc
severity 330635 important
usertag 330635 rc-m68k
severity 332630 important
usertag 332630 rc-s390
severity 330159 important
usertag 330159 rc-arm
# libassa never built on s390, so this never should have been serious AFAICT
severity 332513 important
thanks

--=20
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
<email address hidden> http://www.debian.org/

--YuJye9aIuN0w6xGV
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDsSNkKN6ufymYLloRAjHOAJsFqFozBAGZ5/sXmOgt2j/l35ceYQCgr+uM
rZshzYzCSnvL4xERDW69RKo=
=xzwF
-----END PGP SIGNATURE-----

--YuJye9aIuN0w6xGV--

Revision history for this message
In , Adam Porter (alphapapa) wrote : Still happening?

tags 342215 moreinfo
thanks

Is this still happening? Please try upgrading your KDE packages in general.
I suspect this was not a problem with KMail, but a problem with KDE or other
libraries. I've seen crashes like this in the past that were caused by, for
example, running a version of KMail from testing while using kdelibs from
unstable. If so, I don't think this is exactly a KMail bug.

Frode M. Døving (frode)
Changed in kdepim:
assignee: jr → kubuntu-team
Revision history for this message
Barry deFreese (bddebian) wrote :

Afaik desktop is not supported on Sparc in Ubuntu so I am rejecting this. If I am incorrect, please re-open. Thank you.

Changed in kdepim:
status: Unconfirmed → Rejected
Revision history for this message
In , Julien Cristau (jcristau) wrote : Upgrading sparc-specific bugs to RC severity

# these bugs are release-critical on sparc, which means RC now that
# sparc is a release candidate architecture again.
severity 326922 serious
severity 337169 serious
severity 342215 critical
kthxbye

Revision history for this message
In , Steve Langasek (vorlon) wrote : severity of 342215 is grave

# Automatically generated email from bts, devscripts version 2.9.20
 # does not mention "data loss" in the report
severity 342215 grave

Revision history for this message
In , Christopher Martin (chrsmrtn-gmail) wrote :

Hi,

Can you confirm that the crashes you reported still afflict the latest
KDE 3.5.3? It's been seven months since the report, and we've had no
other reports of KMail crashes on sparc since.

Thanks,
Christopher Martin

> Since I upgraded KDE to 3.4.x, I'm getting unpleasant crashes on
> various KDE applications but the most serious, because of the
> frecuency in which it happens is kmail.
>
> The worst part is that, as kmail is compiled without debuging
> symbols, I can't debug much on what's happening, and all I have are
> the signals with which it dies (4 "Illegal Instruction", and 11
> "Invalid memory reference").
>
> *** KMail got signal 11 (Crashing)
> KCrash: Application 'kmail' crashing...
>
> And this doesn't happen when doing something especifically. For
> example, if I type to fast when composing, it sometimes crashes. Also
> I got crashes when configuring kmail or filters.
>
> Just a moment ago konsole died with no reason, and I wasn't even
> doing anything with it.
>
> KCrash: Application 'konsole' crashing...
>
> This is very annoying.

Revision history for this message
In , Martin Marques (martin-bugs) wrote :

Sorry, but can't test at this moment. To upgrade to that version, I would have to update to xorg, which is broken for SPARC. :-(

On Sun, 23 Jul 2006 11:36:15 -0400, Christopher Martin <email address hidden> wrote:
> Hi,
>
> Can you confirm that the crashes you reported still afflict the latest
> KDE 3.5.3? It's been seven months since the report, and we've had no
> other reports of KMail crashes on sparc since.
>
> Thanks,
> Christopher Martin
>
>> Since I upgraded KDE to 3.4.x, I'm getting unpleasant crashes on
>> various KDE applications but the most serious, because of the
>> frecuency in which it happens is kmail.
>>
>> The worst part is that, as kmail is compiled without debuging
>> symbols, I can't debug much on what's happening, and all I have are
>> the signals with which it dies (4 "Illegal Instruction", and 11
>> "Invalid memory reference").
>>
>> *** KMail got signal 11 (Crashing)
>> KCrash: Application 'kmail' crashing...
>>
>> And this doesn't happen when doing something especifically. For
>> example, if I type to fast when composing, it sometimes crashes. Also
>> I got crashes when configuring kmail or filters.
>>
>> Just a moment ago konsole died with no reason, and I wasn't even
>> doing anything with it.
>>
>> KCrash: Application 'konsole' crashing...
>>
>> This is very annoying.
 --
---------------------------------------------------------
Lic. Martín Marqués | SELECT 'mmarques' ||
Centro de Telemática | '@' || 'unl.edu.ar';
Universidad Nacional | DBA, Programador,
    del Litoral | Administrador
---------------------------------------------------------

Revision history for this message
In , Christopher Martin (chrsmrtn-gmail) wrote :

severity 342215 important
stop

OK, until we get some reasonable confirmation that the bug is still
present, I'm lowering to 'important'.

Cheers,
Christopher Martin

On Sunday 23 July 2006 18:23, you wrote:
> Sorry, but can't test at this moment. To upgrade to that version, I
> would have to update to xorg, which is broken for SPARC. :-(
>
> On Sun, 23 Jul 2006 11:36:15 -0400, Christopher Martin
 <email address hidden> wrote:
> > Hi,
> >
> > Can you confirm that the crashes you reported still afflict the
> > latest KDE 3.5.3? It's been seven months since the report, and
> > we've had no other reports of KMail crashes on sparc since.
> >
> > Thanks,
> > Christopher Martin
> >
> >> Since I upgraded KDE to 3.4.x, I'm getting unpleasant crashes on
> >> various KDE applications but the most serious, because of the
> >> frecuency in which it happens is kmail.
> >>
> >> The worst part is that, as kmail is compiled without debuging
> >> symbols, I can't debug much on what's happening, and all I have
> >> are the signals with which it dies (4 "Illegal Instruction", and
> >> 11 "Invalid memory reference").
> >>
> >> *** KMail got signal 11 (Crashing)
> >> KCrash: Application 'kmail' crashing...
> >>
> >> And this doesn't happen when doing something especifically. For
> >> example, if I type to fast when composing, it sometimes crashes.
> >> Also I got crashes when configuring kmail or filters.
> >>
> >> Just a moment ago konsole died with no reason, and I wasn't even
> >> doing anything with it.
> >>
> >> KCrash: Application 'konsole' crashing...
> >>
> >> This is very annoying.
>
> --
> ---------------------------------------------------------
> Lic. Martín Marqués | SELECT 'mmarques' ||
> Centro de Telemática | '@' || 'unl.edu.ar';
> Universidad Nacional | DBA, Programador,
> del Litoral | Administrador
> ---------------------------------------------------------

Revision history for this message
In , Jonas Schwarz (jonas-vtx) wrote : kmail crashes very oftenly on SPARC (other KDE apps crash too, but not so often)

For me this is not only a problem with kmail, but with kde, I had the
same problems with konsole.

I posted a message on the debian-sparc mailing list, but it didn't help.

my report:
http://lists.debian.org/debian-sparc/2005/11/msg00012.html

another report:
http://lists.debian.org/debian-sparc/2005/12/msg00001.html

Revision history for this message
In , Jonas Schwarz (jonas-vtx) wrote :

I decided to try an upgrade Yesterday, and now I am happily running KDE 3.5.3
with no crash since then. I encourage every user who encouter this problem to
try to upgrade.

Maybe we should wait until we have more reports before closing this Bug.

Revision history for this message
In , Sune Vuorela (debian-pusling) wrote : Closing old kdepim moreinfo bugs

Version: 4:3.5.3-1

These have been tagged moreinfo for months without any more info provided.
Closing.

/Sune

--
Do you know how could I overclock the file?

The point is that you must reset a fan to receive from a wordprocessor to the
46-inch ISA SIMM.

Bug Watch Updater (bug-watch-updater)
Changed in kdepim:
status: Needs Info → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.