Hi!
Ich habe (unter Fedora 3) kalarm-1.1.6.kde3.tar.bz2 installieren wollen unter Gnome, bzw. erst die neuere Version, dann versuchsweise wieder die ältere, was aber irgenwie nicht klappt/e, es kam und kommt die Fehlermeldung :
Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208108832 (LWP 13453)]
[KCrash handler]
#4 0x0048dab9 in free () from /lib/tls/libc.so.6
#5 0x081353b9 in icalmemory_add_tmp_buffer (buf=0x5537e4) at icalmemory.c:94
#6 0x08134ea8 in icalproperty_get_name (prop=0x83660e8) at icalproperty.c:792
#7 0x0812404e in KCal::ICalFormatImpl::readCustomProperties ()
#8 0x081243f7 in KCal::ICalFormatImpl::readAlarm ()
#9 0x08124f38 in KCal::ICalFormatImpl::readIncidence ()
#10 0x08125724 in KCal::ICalFormatImpl::readEvent ()
#11 0x0812605f in KCal::ICalFormatImpl:
opulate ()
#12 0x0811e8fe in KCal::ICalFormat::fromString ()
#13 0x0811de3a in KCal::ICalFormat::load ()
#14 0x0812cb2c in KCal::FileStorage::load ()
#15 0x0811a1fa in KCal::CalendarLocal::load ()
#16 0x08098e95 in AlarmCalendar::load ()
#17 0x08099dbd in AlarmCalendar:pen ()
#18 0x080a5aea in KAlarmApp::initCheck ()
#19 0x080a92bb in KAlarmApp::newInstance ()
#20 0x00af062a in KUniqueApplication:rocessDelayed ()
from /usr/lib/libkdecore.so.4
#21 0x00af07f7 in KUniqueApplication::qt_invoke ()
from /usr/lib/libkdecore.so.4
#22 0x080a6da5 in KAlarmApp::qt_invoke ()
#23 0x0525a3a0 in QObject::activate_signal ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#24 0x0558b59d in QSignal::signal () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#25 0x052730dd in QSignal::activate () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#26 0x0527a19b in QSingleShotTimer::event ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#27 0x051fb849 in QApplication::internalNotify ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#28 0x051fb9da in QApplication::notify ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#29 0x00a403b8 in KApplication::notify () from /usr/lib/libkdecore.so.4
#30 0x051efbbe in QEventLoop::activateTimers ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#31 0x051abbde in QEventLoop:rocessEvents ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#32 0x05210e75 in QEventLoop::enterLoop ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#33 0x05210dce in QEventLoop::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#34 0x051faa4b in QApplication::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#35 0x08077d5f in main ()
++++++++++++++++++++++++++++++
Unter KDE läuft das Programm.
Ich habe die normalen Installationschritte ausgeführt, wie sie in der Install-Datei standen, vielleicht habe ich aber etwas wichtiges übersehen oder nicht verstanden (mein Englisch ist nicht ganz so toll und ich bin ein Newbie). Ich kopiere mal die Ausschnitte aus der Datei hierher die etwas mit der Nutzung unter einem anderen Desktop zu tun haben, weil ich sonst nicht wüßte woran es liegen könnte. Gruß, Natja
Setting up on non-KDE desktops
==============================
Although KAlarm is a KDE application and requires the KDE libraries to be
installed on your system, you can still use it while running other desktops or
window managers.
In order to have alarms monitored and displayed automatically from one login session to the next, the alarm daemon (which monitors the alarm list and tells KAlarm to display each alarm when it becomes due) must be run automatically when you graphically log in or otherwise start X. If you are running the KDE
desktop, the KAlarm installation process sets this up for you.
If you want to use KAlarm with Gnome or another non-KDE window manager, you have two alternatives: 1) If your desktop environment/window manager performs session restoration,
ensure that the alarm daemon (kalarmd) is included in the session restoration, and that after login or restarting X the alarm daemon is running with a '-session' command line option, e.g.
kalarmd -session 117f000002000100176495700000008340018
You can use the 'ps' command to check this. 2) If you cannot use session restoration to start the alarm daemon correctly,
you must configure the following command to be run whenever you graphically log in or start X: kalarmd --login
If your desktop environment or window manager has a facility to configure programs to be run at login, you can use that facility. Otherwise, you need to add the command to an appropriate script which is run after X is started. If you can specify an order to start the applications, start kalarm first, then kalarmd.
If you can send me details on how to set up the daemon for any particular window manager, I will include these in the next version of KAlarm.
Ich habe (unter Fedora 3) kalarm-1.1.6.kde3.tar.bz2 installieren wollen unter Gnome, bzw. erst die neuere Version, dann versuchsweise wieder die ältere, was aber irgenwie nicht klappt/e, es kam und kommt die Fehlermeldung :
Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208108832 (LWP 13453)]
[KCrash handler]
#4 0x0048dab9 in free () from /lib/tls/libc.so.6
#5 0x081353b9 in icalmemory_add_tmp_buffer (buf=0x5537e4) at icalmemory.c:94
#6 0x08134ea8 in icalproperty_get_name (prop=0x83660e8) at icalproperty.c:792
#7 0x0812404e in KCal::ICalFormatImpl::readCustomProperties ()
#8 0x081243f7 in KCal::ICalFormatImpl::readAlarm ()
#9 0x08124f38 in KCal::ICalFormatImpl::readIncidence ()
#10 0x08125724 in KCal::ICalFormatImpl::readEvent ()
#11 0x0812605f in KCal::ICalFormatImpl:
opulate ()#12 0x0811e8fe in KCal::ICalFormat::fromString ()
#13 0x0811de3a in KCal::ICalFormat::load ()
#14 0x0812cb2c in KCal::FileStorage::load ()
#15 0x0811a1fa in KCal::CalendarLocal::load ()
#16 0x08098e95 in AlarmCalendar::load ()
#17 0x08099dbd in AlarmCalendar:
pen ()#18 0x080a5aea in KAlarmApp::initCheck ()
#19 0x080a92bb in KAlarmApp::newInstance ()
#20 0x00af062a in KUniqueApplication:
rocessDelayed ()from /usr/lib/libkdecore.so.4
#21 0x00af07f7 in KUniqueApplication::qt_invoke ()
from /usr/lib/libkdecore.so.4
#22 0x080a6da5 in KAlarmApp::qt_invoke ()
#23 0x0525a3a0 in QObject::activate_signal ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#24 0x0558b59d in QSignal::signal () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#25 0x052730dd in QSignal::activate () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#26 0x0527a19b in QSingleShotTimer::event ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#27 0x051fb849 in QApplication::internalNotify ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#28 0x051fb9da in QApplication::notify ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#29 0x00a403b8 in KApplication::notify () from /usr/lib/libkdecore.so.4
#30 0x051efbbe in QEventLoop::activateTimers ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#31 0x051abbde in QEventLoop:
rocessEvents ()from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#32 0x05210e75 in QEventLoop::enterLoop ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#33 0x05210dce in QEventLoop::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#34 0x051faa4b in QApplication::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#35 0x08077d5f in main ()
++++++++++++++++++++++++++++++
Unter KDE läuft das Programm.
Ich habe die normalen Installationschritte ausgeführt, wie sie in der Install-Datei standen, vielleicht habe ich aber etwas wichtiges übersehen oder nicht verstanden (mein Englisch ist nicht ganz so toll und ich bin ein Newbie). Ich kopiere mal die Ausschnitte aus der Datei hierher die etwas mit der Nutzung unter einem anderen Desktop zu tun haben, weil ich sonst nicht wüßte woran es liegen könnte. Gruß, Natja
Setting up on non-KDE desktops
==============================
Although KAlarm is a KDE application and requires the KDE libraries to be
installed on your system, you can still use it while running other desktops or
window managers.
In order to have alarms monitored and displayed automatically from one login session to the next, the alarm daemon (which monitors the alarm list and tells KAlarm to display each alarm when it becomes due) must be run automatically when you graphically log in or otherwise start X. If you are running the KDE
desktop, the KAlarm installation process sets this up for you.
If you want to use KAlarm with Gnome or another non-KDE window manager, you have two alternatives: 1) If your desktop environment/window manager performs session restoration,
ensure that the alarm daemon (kalarmd) is included in the session restoration, and that after login or restarting X the alarm daemon is running with a '-session' command line option, e.g.
kalarmd -session 117f000002000100176495700000008340018
You can use the 'ps' command to check this. 2) If you cannot use session restoration to start the alarm daemon correctly,
you must configure the following command to be run whenever you graphically log in or start X: kalarmd --login
If your desktop environment or window manager has a facility to configure programs to be run at login, you can use that facility. Otherwise, you need to add the command to an appropriate script which is run after X is started. If you can specify an order to start the applications, start kalarm first, then kalarmd.
If you can send me details on how to set up the daemon for any particular window manager, I will include these in the next version of KAlarm.