Bug 247351 - Korganizer-mobile crashes on startup
Summary: Korganizer-mobile crashes on startup
Status: CLOSED FIXED
Alias: None
Product: KOrganizer Mobile
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Maemo 5 Linux
: VHI major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-11 11:27 UTC by Bernhard E. Reiter
Modified: 2010-08-19 09:48 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
terminal output of crash (31.12 KB, text/plain)
2010-08-11 11:27 UTC, Bernhard E. Reiter
Details
terminal output of crash with more kdebug levels enabled. (42.86 KB, text/plain)
2010-08-11 17:36 UTC, Bernhard E. Reiter
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bernhard E. Reiter 2010-08-11 11:27:25 UTC
Created attachment 50002 [details]
terminal output of crash 

Version:           unspecified (using Devel) 
OS:                other

It is unclear, why it crashes. Björn Ricks also experiences this issue with the
same version. He reports that korganizer-mobile starts if there is no account
configured.

Tag 20100730 started up fine and showed appointements before updating. to me.
Tag 20100805-1 crashes.

Reproducible: Always

Steps to Reproduce:
Start korganizer-mobile (via icon or command line) while having an account configured.


Expected Results:  
No crash.
Comment 1 Bernhard E. Reiter 2010-08-11 11:43:57 UTC
running korganizer-mobile with gdb:
~ $ . ./setpath
~ $ gdb /usr/bin/korganizer-mobile
GNU gdb (GDB) 6.8.50.20090417-debian
Copyright (C) 2009 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 "arm-linux-gnueabi".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
(no debugging symbols found)
(gdb) run --graphicssystem raster
Starting program: /usr/bin/korganizer-mobile --graphicssystem raster
[..]
(no debugging symbols found)

Program received signal SIGILL, Illegal instruction.
0x40915794 in ?? () from /usr/lib/libkcal.so.4
0x40915794:     add     r3, r3, #1      ; 0x1
(gdb) bt
#0  0x40915794 in ?? () from /usr/lib/libkcal.so.4
#1  0x40915820 in ?? () from /usr/lib/libkcal.so.4
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Comment 2 Bernhard E. Reiter 2010-08-11 17:36:27 UTC
Created attachment 50020 [details]
terminal output of crash with more kdebug levels enabled.
Comment 3 Volker Krause 2010-08-16 10:46:38 UTC
Could you please check if this still happens with the 0813 tag? The backtrace indicates libkcal being involved, which is no longer in use in the new tag or recent snapshot builds.

To actually fix this in 0805, I'd need a full backtrace.
Comment 4 Bernhard E. Reiter 2010-08-17 16:05:05 UTC
Just for completeness with tag 20100730-3 (from today)
I also get crashes with korganizer-mobile now.
(Tested with fresh config.)

For a while I could use korganizer, but data was not synced to it, I believe.
Now it always crashes when starting.

Program received signal SIGILL, Illegal instruction.
0x40917794 in ?? () from /usr/lib/libkcal.so.4
0x40917794:     add     r3, r3, #1      ; 0x1
(gdb) bt
#0  0x40917794 in ?? () from /usr/lib/libkcal.so.4
#1  0x40917820 in ?? () from /usr/lib/libkcal.so.4
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) c
Comment 5 Bernhard E. Reiter 2010-08-17 16:19:47 UTC
I was wrong, I accidently did not test 20100730-3, but 0805. :(
Scratch my last comment and sorry for the noise.
Comment 6 Bernhard E. Reiter 2010-08-19 09:47:30 UTC
Verified with 
kmail-mobile            4:4.5~20100813.1163254-1maemo1.1164259
libqt4-experimental-gui                4.7.0~git20100816-0maemo1
that korganizer starts up fine now.
Comment 7 Bernhard E. Reiter 2010-08-19 09:48:28 UTC
I'd say we do not fix for 20100805 tag (as long as this is not becoming
a possible candidate anymore).