[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 147409] New: kalarmd tries to start several times after logging
From:       Wolfgang Zerrmayr <wolfi_z () web ! de>
Date:       2007-07-01 3:15:03
Message-ID: 20070701051500.147409.wolfi_z () web ! de
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=147409         
           Summary: kalarmd tries to start several times after logging in
                    but crashes each time
           Product: kalarm
           Version: unspecified
          Platform: SuSE RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: kalarmd
        AssignedTo: software astrojar org uk
        ReportedBy: wolfi_z web de


Version:           KDE 3.5.1 (using KDE KDE 3.5.1)
Installed from:    SuSE RPMs
OS:                Linux

Backtrace:

System configuration startup check disabled.

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
# repeated several times
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1236711760 (LWP 4520)]
(no debugging symbols found)
 # repeated several times  
(no debugging symbols found)
[KCrash handler]
#6  0xb7e8fa55 in KCal::Recurrence::setFloats ()
   from /opt/kde3/lib/libkcal.so.2
#7  0xb7e8fb46 in KCal::Recurrence::setStartDateTime ()
   from /opt/kde3/lib/libkcal.so.2
#8  0xb7e8ff26 in KCal::Incidence::setDtStart ()
   from /opt/kde3/lib/libkcal.so.2
#9  0x080d5307 in ?? ()
#10 0xbfa2efe0 in ?? ()
#11 0x0825f910 in ?? ()
#12 0x00000000 in ?? ()

Description:

Kalarm should start up automatically. It tries to do so, but it crashes each time.
Killing kalarm and kalarmd and then restarting it manually does not fix the issue.
System is SuSE 10.1 with all automatic updates. The same problem seems to appear on \
10.2 also. It apparently is related to an update of a library or whatever, since it \
does not exist on a freshly built 10.1 or 10.2 system without updates.


[prev in list] [next in list] [prev in thread] [next in thread]