Bug 197178 - kalarm does not open, does not start up. The crashed has caused the signal 6 (SIGARBT)
Summary: kalarm does not open, does not start up. The crashed has caused the signal 6 ...
Status: CLOSED DUPLICATE of bug 194745
Alias: None
Product: kalarm
Classification: Applications
Component: sound (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: David Jarvie
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-19 18:50 UTC by Christian Ortega
Modified: 2010-09-02 10:44 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Ortega 2009-06-19 18:50:39 UTC 
Version:           2.1.7 (using KDE 4.2.3)
OS:                Linux
Installed from:    Fedora RPMs

crash without backtrace. The comand line show this:

[user@athlonxp ~]$ kalarm
<unknown program name>(16586)/ main: Unknown resource type:  "alarms"
ASSERT: "s_instance == 0" in file /builddir/build/BUILD/phonon-4.3.1/xine/backend.cpp, line 74
<unknown program name>(16583)/: Communication problem with  "kalarm" , it probably crashed.
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" "

[user@athlonxp ~]$ KCrash: Application 'kalarm' crashing...
sock_file=/home/Christian/.kde/socket-athlonxp/kdeinit4__0
kalarm: Fatal IO error: client killed
Unable to start Dr. Konqi



It seems that this problem began after doing some updates from Fedora's updates repositories this week, but I am not sure..
Comment 1 Dario Andres 2009-06-19 22:48:29 UTC 
Thanks. This was fixed recently.

*** This bug has been marked as a duplicate of bug 194745 ***