Bug 199654 - after login to kde kalarm have crashed (sig 11)
Summary: after login to kde kalarm have crashed (sig 11)
Status: CLOSED NOT A BUG
Alias: None
Product: kalarm
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: David Jarvie
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-10 12:21 UTC by christian
Modified: 2010-09-02 12:25 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description christian 2009-07-10 12:21:37 UTC
Version:            (using KDE 4.2.4)
Compiler:          gcc 4.4? 
OS:                Linux
Installed from:    Fedora RPMs

Here is I get from kde crashhandler:

Program: Kalarm (kalarm), signal SIGSEGV
[Current thread is 1 (Thread 0xb7f78780 (LWP 2466))]

Thread 2 (Thread 0xb66eeb70 (LWP 2472)):
#0  0x00b7a424 in __kernel_vsyscall ()
#1  0x009bfee1 in select () from /lib/libc.so.6
#2  0x06b49605 in ?? () from /usr/lib/libQtCore.so.4
#3  0x06a7b21e in ?? () from /usr/lib/libQtCore.so.4
#4  0x00a93935 in start_thread () from /lib/libpthread.so.0
#5  0x009c782e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb7f78780 (LWP 2466)):
[KCrash Handler]
#6  0x080bdcef in _start ()
Comment 1 Carlos Licea 2009-07-10 14:12:21 UTC
This is nov a very useful report. Please install debugging symbols (so that we can know exactly what happened) and try to reproduce the crash.
Comment 2 Dario Andres 2009-07-10 16:57:24 UTC
Also, does this happen every time ? Do you do something special that causes the crash or not ?
Thanks
Comment 3 David Jarvie 2009-07-11 15:23:37 UTC
Can you please attach the file ~/.kde/share/apps/kalarm/displaying.ics (or possibly ~/.kde4/share/....)
Comment 4 christian 2009-07-12 00:06:31 UTC
This was in the file ~/.kde/share/apps/kalarm/displaying.ic !

BEGIN:VCALENDAR

PRODID:-//K Desktop Environment//NONSGML KAlarm 2.1.6//EN

VERSION:2.0

END:VCALENDAR
Comment 5 robert 2009-08-01 15:48:37 UTC
I'm getting a crash when starting kalarm (logon or otherwise) and a pending alarm had a sound associated with it:

$ kalarm
<unknown program name>(9208)/ main: Unknown resource type:  "alarms" 
$ QObject: Cannot create children for a parent that is in a different thread.
(Parent is Phonon::Xine::MediaObject(0xb532c9c0), parent's thread is
AudioThread(0x9dffbd0), current thread is QThread(0x9adc260)
KCrash: Application 'kalarm' crashing...
sock_file=/home/rstory/.kde/socket-vspx.vb.futz.org/kdeinit4__0
E: core-util.c: Assertion 'pa_close(fds[0]) == 0' failed at
pulsecore/core-util.c:2107, function pa_close_pipe(). Aborting.
Unable to start Dr. Konqi



my Fedora bug report: https://bugzilla.redhat.com/show_bug.cgi?id=514535

and a few other distros:

https://bugs.launchpad.net/ubuntu/+source/phonon/+bug/383321
http://lists.kde.org/?l=kde-multimedia&m=124492170708937&w=2
http://osdir.com/ml/debian-bugs-dist/2009-06/msg03082.html
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=523332
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=532731
Comment 6 Dario Andres 2009-08-01 16:41:17 UTC
@robert: I think your issue is a different one (more related to sound/Phonon and PulseAudio). If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports ; install the proper debuginfo packages, and post a complete backtrace in a *NEW* report ? (you probably need to install the "kalarm-debuginfo" and "phonon-debuginfo" packages )Thanks
Comment 7 robert 2009-08-01 18:45:36 UTC
Dario: you were right.. my problem has already been fixed (https://bugs.kde.org/show_bug.cgi?id=194745).. thanks..
Comment 8 David Jarvie 2009-08-02 00:18:47 UTC
Christian - In order to investigate this crash, we need a proper crash trace, for which you need to install the debug packages for kdepim and kdelibs. Also, can you please answer comment #2 by Dario.

For more information on producing a useful crash trace, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Comment 9 David Jarvie 2009-11-01 02:41:05 UTC
Closing as invalid because there is not sufficient information to investigate the bug - the crash trace has no useful information and there are few details about the circumstances of the crash.