Bug#1050723: plasma-workspace: plasmashell crashes when closing a window
Package: plasma-workspace Version: 4:5.27.5-2 Severity: normal Tags: upstream Dear Maintainer, The screen went black and the taskbar disappeared when I closed a window, after which plasmashell restarted. A crash trace showed a segmentation fault. This happens fairly regularly, not always after closing a window. This was reported on the KDE bug system at https://bugs.kde.org/show_bug.cgi?id=472543. It has since been fixed - see https://bugs.kde.org/show_bug.cgi?id=446874#c14. It looks as if it may require some change which was implemented in KDE Frameworks 5.104 as well - see https://bugs.kde.org/show_bug.cgi?id=446874#c22. It would be good if the fix could be backported to Debian stable. -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-11-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages plasma-workspace depends on: ii dbus-user-session [default-dbus-session-bus]1.14.8-2~deb12u1 ii drkonqi 5.27.5-2 ii frameworkintegration5.103.0-1 ii gdb 13.1-3 ii init-system-helpers 1.65.2 ii iso-codes 4.15.0-1 ii kactivitymanagerd 5.27.5-2 ii kded5 5.103.0-1 ii kinit 5.103.0-1 ii kio 5.103.0-1 ii kpackagetool5 5.103.0-1 ii kwin-common 4:5.27.5-3 ii libappstreamqt2 0.16.1-2 ii libc6 2.36-9+deb12u1 ii libcolorcorrect54:5.27.5-2 ii libcrypt1 1:4.4.33-2 ii libfontconfig1 2.14.1-4 ii libfreetype62.12.1+dfsg-5 ii libgcc-s1 12.2.0-14 ii libgps283.22-4.1+b1 ii libice6 2:1.0.10-1 ii libicu7272.1-3 ii libkf5activities5 5.103.0-1 ii libkf5activitiesstats1 5.103.0-1 ii libkf5archive5 5.103.0-1 ii libkf5authcore5 5.103.0-1 ii libkf5baloo55.103.0-2 ii libkf5bookmarks55.103.0-1 ii libkf5calendarevents5 5.103.0-1 ii libkf5completion5 5.103.0-1 ii libkf5config-bin5.103.0-2 ii libkf5configcore5 5.103.0-2 ii libkf5configgui55.103.0-2 ii libkf5configwidgets55.103.0-1 ii libkf5coreaddons5 5.103.0-1 ii libkf5crash55.103.0-1 ii libkf5dbusaddons5 5.103.0-1 ii libkf5declarative5 5.103.0-1 ii libkf5globalaccel-bin 5.103.0-1 ii libkf5globalaccel5 5.103.0-1 ii libkf5guiaddons55.103.0-1 ii libkf5holidays5 1:5.103.0-1 ii libkf5i18n5 5.103.0-1 ii libkf5iconthemes5 5.103.0-1 ii libkf5idletime5 5.103.0-2 ii libkf5jobwidgets5 5.103.0-1 ii libkf5kcmutils5 5.103.0-3 ii libkf5kexiv2-15.0.0 22.12.3-1 ii libkf5kiocore5 5.103.0-1 ii libkf5kiofilewidgets5 5.103.0-1 ii libkf5kiogui5 5.103.0-1 ii libkf5kiowidgets5 5.103.0-1 ii libkf5networkmanagerqt6 5.103.0-1 ii libkf5newstuff5 5.103.0-1 ii libkf5newstuffcore5 5.103.0-1 ii libkf5newstuffwidgets5 5.103.0-1 ii libkf5notifications5
Bug#822061: kalarm: KF5 version requires plasma-workspace to work properly
This bug is no longer applicable. KAlarm no longer uses ktimezoned with Qt5 because it now uses QTimeZone. -- David Jarvie. KDE developer, KAlarm author.
Bug#932347: kalarm: Multiple akonadi_kalarm_resource processes are spawned on kalarm start and consume lot of CPU
Note that from version 20.08 onwards (i.e. Bullseye or later), kalarm no longer uses Akonadi for calendar access, so this problem can no longer occur. -- David Jarvie. KDE developer, KAlarm author.
Bug#836873: kalarm: The Akonadi personal information management service is not operational
Note that from version 20.08 onwards (i.e. Bullseye or later), kalarm no longer uses Akonadi for calendar access, so this problem no longer exists. Akonadi is now only used for functions such as migration of resources from previous versions, birthday import and email functions. Failure of Akonadi will only affect those particular functions. -- David Jarvie. KDE developer, KAlarm author.
Bug#1021938: kalarm: .local/share/kalarm/expired.ics is not a valid iCalendar file
This is due to a regression in libical version 3.0.15. It is fixed in libical 3.0.16 (which is in unstable). See https://bugs.kde.org/show_bug.cgi? id=460442. -- David Jarvie. KDE developer, KAlarm author.
Bug#1004424: kalarm: Package information shows invalid homepage
Package: kalarm Version: 4:20.08.3-1 Severity: minor Dear Maintainer, The Debian package information for kalarm shows the homepage for the project as www.astrojar.org.uk. From version 20.08.0, that homepage has no longer been shown in the upstream package information (see the application's Help -> About), and in fact the web page no longer exists and is therefore invalid. Analogous to other KDE PIM applications, the homepage should be https://invent.kde.org/pim/kalarm. -- System Information: Debian Release: 11.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-11-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kalarm depends on: ii akonadi-server 4:20.08.3-3 ii kdepim-runtime 4:20.08.3-1 ii kio5.78.0-5 ii libc6 2.31-13+deb11u2 ii libgcc-s1 10.2.1-6 ii libkf5akonadicontact5 [libkf5akonadicontact5-20.08]4:20.08.3-1 ii libkf5akonadicore5abi2 [libkf5akonadicore5-20.08] 4:20.08.3-3 ii libkf5akonadimime5 [libkf5akonadimime5-20.08] 4:20.08.3-1 ii libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-20.08]4:20.08.3-3 ii libkf5alarmcalendar5abi1 [libkf5alarmcalendar5-20.08] 4:20.08.3-1 ii libkf5authcore55.78.0-2 ii libkf5calendarcore5abi25:5.78.0-2 ii libkf5calendarutils5 [libkf5calendarutils5-20.08] 4:20.08.3-1 ii libkf5codecs5 5.78.0-2 ii libkf5completion5 5.78.0-3 ii libkf5configcore5 5.78.0-4 ii libkf5configgui5 5.78.0-4 ii libkf5configwidgets5 5.78.0-2 ii libkf5contacts55:5.78.0-2 ii libkf5coreaddons5 5.78.0-4 ii libkf5crash5 5.78.0-3 ii libkf5dbusaddons5 5.78.0-2 ii libkf5globalaccel-bin 5.78.0-3 ii libkf5globalaccel5 5.78.0-3 ii libkf5guiaddons5 5.78.0-3 ii libkf5holidays51:5.78.0-2 ii libkf5i18n55.78.0-2 ii libkf5identitymanagement5 [libkf5identitymanagement5-20.0 20.08.3-1 ii libkf5itemmodels5 5.78.0-2 ii libkf5jobwidgets5 5.78.0-2 ii libkf5kiocore5 5.78.0-5 ii libkf5kiofilewidgets5 5.78.0-5 ii libkf5kiowidgets5 5.78.0-5 ii libkf5mailtransport5 [libkf5mailtransport5-20.08] 20.08.3-1 ii libkf5mailtransportakonadi5 [libkf5mailtransportakonadi5- 20.08.3-1 ii libkf5mime5abi1 [libkf5mime5-20.08]20.08.3-1 ii libkf5notifications5 5.78.0-2 ii libkf5pimcommon5abi2 [libkf5pimcommon5-20.08] 4:20.08.3-1 ii libkf5pimtextedit5abi2 [libkf5pimtextedit5-20.08] 20.08.3-1 ii libkf5textwidgets5 5.78.0-2 ii libkf5widgetsaddons5 5.78.0-2 ii libkf5windowsystem55.78.0-2 ii libkf5xmlgui5 5.78.0-2 ii libphonon4qt5-44:4.11.1-4 ii libqt5core5a 5.15.2+dfsg-9 ii libqt5dbus55.15.2+dfsg-9 ii libqt5gui5 5.15.2+dfsg-9 ii libqt5network5 5.15.2+dfsg-9 ii libqt5widgets5 5.15.2+dfsg-9 ii libqt5x11extras5 5.15.2-2 ii libstdc++6 10.2.1-6 ii perl 5.32.1-4+deb11u2 ii phonon4qt5 4:4.11.1-4 kalarm recommends no packages. kalarm suggests no packages.
KDE PIM version for testing
Is it the intention to update the KDE PIM version in testing to at least 20.08.3 before Bullseye is released as the stable version? The reason I ask is that there is a very serious bug in the current version of KAlarm in testing, which is fixed in 20.08.3 (see https://bugs.kde.org/show_bug.cgi?id=427722). If it's going to be updated, there is no need for me to raise a bug report. Thanks, -- David Jarvie. KDE developer, KAlarm author.
Bug#968281: I cannot export alarms in Kalarm
This bug description looks like https://bugs.kde.org/show_bug.cgi?id=374337. This was fixed in KDE Applications 16.12.1. (The version you are reporting about is an earlier version, 16.04.3.) -- David Jarvie. KDE developer, KAlarm author.
Bug#967929: kalarm: Doen't instal properly. It nedd instalation of Akonadi, kdepim-runtime, Kderun, etc...
I can confirm that kdepim-runtime is essential for this and previous versions of KAlarm to be able to operate. Note for future reference that this should no longer be such a hard requirement for KDE release 20.08 onward. -- David Jarvie KAlarm author, KDE developer
Bug#921032: kalarm: Window frame is missing, after alarm appears when full-screen application is running
In order to ensure that the alarm window appears on top of a full screen application, KAlarm uses a Qt mechanism to bypass the window manager. This has the side effect of removing the window frame. Without this, the alarm might be shown under the full screen application and therefore be invisible. So this is not a bug. The bug which prevented the defer dialog from being accessible when a full screen application is running has now been fixed for the next KDE release, 19.12.1, by git commit https://cgit.kde.org/kalarm.git/commit/?id=870c2a6173d83b1989e948bdfb97cf0c2f9bb886 -- David Jarvie. KDE developer. KAlarm author -- http://www.astrojar.org.uk/kalarm
Bug#941430: Kalarm sound, image alarms never worked, and then text alarms stopped working
KAlarm image alarms have now been fixed for the forthcoming KDE Applications 19.12 release, by commit https://cgit.kde.org/kalarm.git/commit/?h=release/19.12=2e2b77207eb1e4b631da94633484d0695e1dc0cd -- David Jarvie. KDE developer. KAlarm author -- http://www.astrojar.org.uk/kalarm
Bug#932347: kalarm: Multiple akonadi_kalarm_resource processes are spawned on kalarm start and consume lot of CPU
This seems likely to be the same bug as https://bugs.kde.org/show_bug.cgi?id=403124, which has now been fixed for the KDE Applications 19.08 release. The fix is to remove any duplicate Akonadi resources (i.e. which use the same calendar file) at KAlarm startup. The user is also now prevented from manually creating duplicate resources via KAlarm's interface. See the KDE bug report for details of the git commits which fix this issue. -- David Jarvie. KDE developer. KAlarm author -- http://www.astrojar.org.uk/kalarm
Bug#926385: kalarm does not show details of errors, for the error about missing akonadi
Note that the error message and the button "Details" are provided automatically by the Akonadi library if Akonadi fails to start up. AFAIK, you would see exactly the same display in any other Akonadi-dependent application if Akonadi failed to start. So, although you see the fault in KAlarm, the bug actually lies in the relevant Akonadi library package. -- David Jarvie. KDE developer. KAlarm author -- http://www.astrojar.org.uk/kalarm
Bug#853150: kalarm.autostart.desktop missing OnlyShowIn=KDE
There is a fix for this issue in KDE Applications 16.08.1 (see https://cgit.kde.org/kdepim.git/commit/?h=Applications/16.08=cc2d8bb39417b186bfe40470eba921a64ef6c6c8) Adding OnlyShowIn=KDE is the wrong solution, since that could prevent KAlarm from starting even when the user wants to use it under Gnome or other desktops. -- David Jarvie. KDE developer. KAlarm author -- http://www.astrojar.org.uk/kalarm
Bug#822061: kalarm: KF5 version requires plasma-workspace to work properly
Package: kalarm Version: 4:15.12.1-1 Severity: important Dear Maintainer, KAlarm requires the kded module ktimezoned in order to use any time zone other than UTC. If ktimezoned is not present, kalarm outputs the following error message on startup: "Time zones are not accessible: KAlarm will use the UTC time zone. (The KDE time zone service is not available: check that ktimezoned is installed." Without ktimezoned, it won't function properly for virtually all users. ktimezoned (provided by the plugin file kded_ktimezoned.so) is part of the plasma-workspace package. With the current package contents, kalarm should therefore depend on plasma-workspace. It might be preferable to split plasma-workspace so that kalarm can depend on a smaller package. I don't know whether that is feasible.
Re: [debian-kde] Re: plasma desktop hangs
On Monday 02 July 2012 16:20:27 chymian wrote: I followed your advice and opened up a new thread: http://forum.kde.org/viewtopic.php?f=67t=106640 Just a word of warning - many KDE developers do not read forums. Unless you know that the forum you posted to is read by developers, you should raise issues either on the appropriate KDE mailing list (see http://lists.kde.org) or if it's a bug, at https://bugs.kde.org. -- David Jarvie. KDE developer. KAlarm author -- http://www.astrojar.org.uk/kalarm -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201207060902.17316.djar...@kde.org
Re: [debian-kde] Re: kalarm broken by mysql upgrade?
On Thu, June 21, 2012 9:29 pm, Andreas v. Heydwolff wrote: On 2012-06-21 01:10, David Jarvie wrote: That package is for use with kdepim 4.4. I'm confused as to which package versions you are using, since KAlarm 4.4 is not able to use Akonadi - Akonadi resources for KAlarm were only implemented in kdepim 4.8. Earlier versions of KAlarm do not use Akonadi at all. Thanks, David and Xavier, for the help and clarification, and sorry for the confusion I created. It seems that the *.ics files were updated and slightly modified when I was using a self compiled kalarm 2.9, and the Debian version 4.4.11 to which I reverted later when the kalarm crashes were resolved could not handle them. I finally moved all files out of the dir and started from scratch, extraced all DESCRIPTION fields with a sed/cut script and manually created new alarms. Problem solved. Good, I'm glad you got it sorted out. There is always a potential problem, in KAlarm as in other applications, if you try to use configuration or data files when stepping back to an older version of the application. In the case of KAlarm, if it finds that a calendar file has been written by a later version (and only if there has been a format change between the two versions) it takes the precaution of making the file read-only to ensure that data is not lost for the newer version of KAlarm which created the files. Your experience makes me wonder whether a warning should be displayed if this happens, together with offering the option of making the files read-write regardless. -- David Jarvie. KDE developer. KAlarm author - http://www.astrojar.org.uk/kalarm -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/fcde65224b228fde3b64fdcab2dc729b.squir...@www.sensical.net
Re: Re: kalarm broken by mysql upgrade?
On Fri, June 22, 2012 11:29 am, Xavier Brochard wrote: David Jarvie wrote: On Wednesday 20 June 2012 18:05:04 Andreas v. Heydwolff wrote: On 2012-06-20 17:47, David Jarvie wrote: On Wed, June 20, 2012 12:54 am, Xavier Brochard wrote: Andreas v. Heydwolff wrote: You are missing Kalarm akonadi resources. Indeed they are not installed. I am not sure which package they belong to. Kalarm see http://packages.debian.org/sid/i386/kalarm/filelist Actually, the KAlarm Akonadi resources are in the kdepim-runtime package. But which one in the list would show up as the kalarm resource in Akonadi (please follow link)? http://packages.debian.org/sid/amd64/kdepim-runtime/filelist That package is for use with kdepim 4.4. I'm confused as to which package versions you are using, since KAlarm 4.4 is not able to use Akonadi - Akonadi resources for KAlarm were only implemented in kdepim 4.8. Earlier versions of KAlarm do not use Akonadi at all. Time to fill a bug report... Kalarm from KDE 4.8.x can't work without Akonadi resource, yes? It can't work without an Akonadi resource IF it's built to use Akonadi. The same applies to many other kdepim 4.8 applications. All of them depend on having kdepim-runtime 4.8 installed in order to work. Note that the kdepim Debian packages are still at version 4.4. The problem here was that KAlarm 4.8/9 was compiled from source instead of being installed from a package. When Debian kdepim 4.8/4.9 packages become available, I'm sure our packagers will take care to ensure that this problem won't occur. So I don't think it is a bug. -- David Jarvie. KDE developer. KAlarm author - http://www.astrojar.org.uk/kalarm -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/85e16b8758a9b26dbc55a7f078bf85cf.squir...@www.sensical.net
Re: kalarm broken by mysql upgrade?
On Wed, June 20, 2012 12:54 am, Xavier Brochard wrote: Andreas v. Heydwolff wrote: You are missing Kalarm akonadi resources. Indeed they are not installed. I am not sure which package they belong to. Kalarm see http://packages.debian.org/sid/i386/kalarm/filelist Actually, the KAlarm Akonadi resources are in the kdepim-runtime package. -- David Jarvie. KDE developer. KAlarm author - http://www.astrojar.org.uk/kalarm -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/01abf2717f09aa6fad30578edc87d2e1.squir...@www.sensical.net
Re: [debian-kde] Re: kalarm broken by mysql upgrade?
On Wednesday 20 June 2012 18:05:04 Andreas v. Heydwolff wrote: On 2012-06-20 17:47, David Jarvie wrote: On Wed, June 20, 2012 12:54 am, Xavier Brochard wrote: Andreas v. Heydwolff wrote: You are missing Kalarm akonadi resources. Indeed they are not installed. I am not sure which package they belong to. Kalarm see http://packages.debian.org/sid/i386/kalarm/filelist Actually, the KAlarm Akonadi resources are in the kdepim-runtime package. But which one in the list would show up as the kalarm resource in Akonadi (please follow link)? http://packages.debian.org/sid/amd64/kdepim-runtime/filelist That package is for use with kdepim 4.4. I'm confused as to which package versions you are using, since KAlarm 4.4 is not able to use Akonadi - Akonadi resources for KAlarm were only implemented in kdepim 4.8. Earlier versions of KAlarm do not use Akonadi at all. -- David Jarvie. KDE developer. KAlarm author -- http://www.astrojar.org.uk/kalarm -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201206210010.31885.djar...@kde.org
Bug#671619: Bug has been fixed upstream
This bug has already been fixed upstream (see https://bugs.kde.org/show_bug.cgi?id=271580). The fix was done after KDE 4.4.11 was released, so it is unlikely to be released as a new kdepim version. The latest kdepim/kalarm 4.4 branch sources should be obtained from git to get the fix (or get the git commit mentioned in the KDE bug report). -- David Jarvie. KDE developer. KAlarm author -- http://www.astrojar.org.uk/kalarm signature.asc Description: This is a digitally signed message part.
Bug#532731: kalarm: crashes on desktop startup
This bug report is the same as the KDE bug report https://bugs.kde.org/show_bug.cgi?id=194745. It is almost certainly due to KAlarm trying to redisplay an alarm which has a sound file associated. It's unlikely to be related to which window manager is being used. Can the reporter please go to the KDE bug report and attach to it the file ~/.kde/share/apps/kalarm/displaying.ics. This may help to track this one down. After that, deleting the file should fix the problem at least temporarily. -- David Jarvie. KAlarm author maintainer. http://www.astrojar.org.uk/kalarm -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524503: [kalarm] D-Bus sayMessage call failed
This is an upstream bug in KAlarm. It has now been fixed for KDE 4.2.3 (KDE SVN commit 955833). -- David Jarvie. KAlarm author and maintainer. http://www.astrojar.org.uk/kalarm -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514612: Remove kmix as a suggested dependency for kalarm
Package: kalarm Version: 4:4.2.0-1 Severity: normal KAlarm no longer refers to kmix in its source code in KDE4 - it now uses phonon instead. So the kalarm package should no longer suggest kmix as a dependency. -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages kalarm depends on: ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime [ snip - not relevant ] kalarm recommends no packages. Versions of packages kalarm suggests: ii kmix 4:3.5.9-2 sound mixer applet for KDE ii kttsd 4:3.5.9-2 a Text-to-Speech system for KDE -- no debconf information -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514612: Remove kmix as a suggested dependency for kalarm
Just to make it absolutely clear, KDE3 kalarm packages should still suggest kmix as before. The change to remove kmix applies only to KDE4 versions. -- David Jarvie. KAlarm author and maintainer. http://www.astrojar.org.uk/kalarm -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#490576: kalarm: Wrong homepage listed in package
On Tuesday 03 February 2009 13:29:21 Xavier Vello wrote: The svn packaging for kde3 has the right homepage field, see http://svn.debian.org:80/viewsvn/pkg-kde/trunk/packages/kdepim/ If a kdepim3 upload were to be made, the fix would be uploaded. In that case, I'm happy for the bug to be closed. -- David Jarvie. KAlarm author and maintainer. http://www.astrojar.org.uk/kalarm -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#490576: kalarm: Wrong homepage listed in package
I'm obviously not asking for a special kdepim3 upload just for this. But presumably there could be kdepim3 updates in the future (after lenny becomes stable), and if so I'd like to see a fix for this bug incorporated at that point. I don't know enough about Debian's bugfix handling procedures to know what's the best way to achieve this - I must leave this up to you. -- David Jarvie. KAlarm author and maintainer. http://www.astrojar.org.uk/kalarm -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#490576: kalarm: Wrong homepage listed in package
I don't agree with closing this bug since the KDE3 package (which is currently the only option in stable/testing/unstable) still has the error. The KDE3 package will presumably remain available for quite a while to come. -- David Jarvie. KAlarm author and maintainer. http://www.astrojar.org.uk/kalarm -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#490576: kalarm: Wrong homepage listed in package
Package: kalarm Version: 4:3.5.9-2 Severity: minor The homepage listed in the package description for kalarm should be http://www.astrojar.org.uk/kalarm. The listed home page in the package description (http://kontact.kde.org) is for Kontact, which doesn't include KAlarm. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages kalarm depends on: ii kdelibs4c2a4:3.5.9.dfsg.1-4 core libraries and binaries for al ii libacl12.2.47-2 Access control list shared library ii libart-2.0-2 2.3.20-2 Library of functions for 2D graphi ii libarts1c2a1.5.9-2 aRts sound system core components ii libattr1 1:2.4.41-1Extended attribute shared library ii libaudio2 1.9.1-2 Network Audio System - shared libr ii libc6 2.7-10GNU C Library: Shared libraries ii libfam02.7.0-13.3Client library to control the FAM ii libfontconfig1 2.6.0-1 generic font configuration library ii libfreetype6 2.3.6-1 FreeType 2 font engine, shared lib ii libgcc11:4.3.1-2 GCC support library ii libice62:1.0.4-1 X11 Inter-Client Exchange library ii libidn11 1.8+20080606-1GNU libidn library, implementation ii libjpeg62 6b-14 The Independent JPEG Group's JPEG ii libkcal2b 4:3.5.9-2 KDE calendaring library ii libkdepim1a4:3.5.9-2 KDE PIM library ii libkmime2 4:3.5.9-2 KDE MIME interface library ii libkpimidentities1 4:3.5.9-2 KDE PIM user identity information ii libktnef1 4:3.5.9-2 Library for handling KTNEF email a ii libpng12-0 1.2.27-1 PNG library - runtime ii libqt3-mt 3:3.3.8b-5Qt GUI Library (Threaded runtime v ii libsm6 2:1.0.3-2 X11 Session Management library ii libstdc++6 4.3.1-2 The GNU Standard C++ Library v3 ii libx11-6 2:1.1.4-2 X11 client-side library ii libxcursor11:1.1.9-1 X cursor management library ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar ii libxft22.1.12-3 FreeType-based font drawing librar ii libxi6 2:1.1.3-1 X11 Input extension library ii libxinerama1 2:1.0.3-2 X11 Xinerama extension library ii libxrandr2 2:1.2.2-2 X11 RandR extension library ii libxrender11:0.9.4-2 X Rendering Extension client libra ii libxt6 1:1.0.5-3 X11 toolkit intrinsics library ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime kalarm recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Packages for 3.5.9 amd64/i386
On Sun 2 March 2008 22:24:44 Ana Guerrero wrote: Hi, KDE 3.5.9 has not been uploaded to unstable yet due to problems with Qt3. It is not sure when it will be uploaded but in the meantime, you can find packages of KDE 3.5.9 for both i386 and amd64 at: deb http://people.debian.org/~ana/kde359/ ./ Not all the modules are yet uploaded, but I will try to upload the rest tomorrow. This packages are 99% sure the same packages that will be uploaded to unstable, so you can upgrade safely. Anyway, do not expect big changes... See: http://www.kde.org/announcements/changelogs/changelog3_5_8to3_5_9.php Although there are lots of changes in kdepim which aren't listed in that changelog - see http://techbase.kde.org/index.php?title=Projects/PIM/Features_3.5.9 -- David Jarvie. KAlarm author and maintainer. http://www.astrojar.org.uk/kalarm -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
kmilo not working on Lenny
I can't get kmilo to respond in any way to the volume and mute keys on my Lenovo 3000 N200 laptop (which uses the generic kmilo module). It works OK using (K)Ubuntu Gutsy on the same computer. It's not clear what configuration is needed. The mute and volume up/down keys produce the standard codes defined in /usr/share/hotkey-setup/key-constants, so there doesn't appear to be a keyboard mapping problem. On Ubuntu the keys (via kmilo) produce an OSD display when they are pressed, but nothing shows on Debian. Kmilo is set to run in the KDE service manager. Any hints as to what else to look at? P.S. I'm aware of the bugs in the generic module - there are fixes available now from the KDE source repository. -- David Jarvie. KAlarm author and maintainer. http://www.astrojar.org.uk/kalarm -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kmilo not working on Lenny
On Wednesday 02 January 2008 18:47:06 David Jarvie wrote: I can't get kmilo to respond in any way to the volume and mute keys on my Lenovo 3000 N200 laptop (which uses the generic kmilo module). It works OK using (K)Ubuntu Gutsy on the same computer. It's not clear what configuration is needed. The mute and volume up/down keys produce the standard codes defined in /usr/share/hotkey-setup/key-constants, so there doesn't appear to be a keyboard mapping problem. On Ubuntu the keys (via kmilo) produce an OSD display when they are pressed, but nothing shows on Debian. Kmilo is set to run in the KDE service manager. Any hints as to what else to look at? Found the solution - using xev the keycodes turn out to be different under X, and xmodmap is needed. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=396622. -- David Jarvie. KAlarm author and maintainer. http://www.astrojar.org.uk/kalarm -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#449155: kalarm: fails to trigger some date-only alarms
Package: kalarm Version: 4:3.5.8-1 Severity: important KAlarm in kdepim 3.5.8 has a significant regression from 3.5.7, so that recurring date-only alarms can fail to trigger at all (after the initial occurrence). This seems to happen particularly if suspend and resume is used on the system. This has now been fixed in KDE SVN (revision 732115). Please ensure that the Debian package is updated with that fix. -- David Jarvie. KAlarm author and maintainer. http://www.astrojar.org.uk/kalarm -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#293919: kalarm: time wrap (alarm in 4294966895 minutes)
I think I saw this bug occasionally during testing of KAlarm. The KDE 3.5.7 version of KAlarm added a check for negative numbers and prevents them being displayed as large positive numbers. So from KDE 3.5.7 onwards, this bug should never happen any more. -- David Jarvie. KAlarm author maintainer. http://www.astrojar.org.uk/kalarm
Re: Kmail: Replying to encapsulated messages in a email list digest.
On Friday 09 March 2007 13:57:08 Curt Howland wrote: I have been taken to task for breaking threads in a mailing list, because I receive the digest. Nothing I have found to do has been able to reply to a particular encapsulated message, thus preserving the in-reply-to header entry. Unfortunately, I have not found any combination of selection and reply-to that does anything other than give me a subject of Re: Debian user digest #whatever and the text of the digested subject lines of the contained messages. Any pointer would be greatfully received. To split up a digest email into its separate messages, pipe the message through the following command: formail +1 -ds Use the List-Id: header to select which emails to pipe through this filter. -- David Jarvie. KAlarm author and maintainer. http://www.astrojar.org.uk/kalarm -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [SOLVED] Define KDEHOME
On Sunday 26 November 2006 16:42, Kevin Krammer wrote: On Sunday 26 November 2006 16:11, Oliver Meißner-Knippschild wrote: Currently, I edit startke to set KDEHOME, KDEDIRS, etc, and it would be nice to move that stuff into a separate file so that I don't have to edit startkde each time I update. I build from KDE source rather than use the Debian packages, so perhaps that could make a difference. is only the startkde-environment using those scripts or does it contain system-wide scripts? When are those files in /usr/env sourced and by which processes would that be done? Only used by startkde. Just search for env, around line 160 in startkde This is executed *AFTER* KDEHOME is set in startkde. How can setting KDEHOME in an env/ directory work in that case? Since KDE can handle a list of prefix directories, it can also handle env/ subdir in each of them. Can be used to do user specific extensions, etc AFAICS the only prefix directories it looks in are the directories in the KDE executable path, but replacing the bin suffix with env. -- David Jarvie
Re: Kmail and spamassasin bayes rule.
On Wednesday 30 August 2006 00:17, Raúl Sánchez Siles wrote: Hello: intro After some thiking I finally decided to move from Thunderbird to Kmail. This was some months ago. After some problems with the mail solved by kmailcvt and others[1] I made kmail work with no problems. Then I tried to configure spamassasin so that kmail could manage spam. After testing some time, I noticed that I was quite happy with the TB simple bayes spam filter. I know that there are also some simple bayes filter that work with kmail (e.g.: bogofilter) but I thought that since SA is well known to be the best and the most used spam filter I decided for it. /intro I have it configured and runs quite well, but it seems for me that the bayes training (sa-learn) is not working properly. As the wizard defines I have a rule for spam and another for ham. both at the end of the filter pipeline so they are never run automatically, instead of that I have some icons on the main bar for that. The spam rule action is this: sa-learn -L --spam --no-sync The ham rule action is this: sa-learn -L --ham --no-sync After some training I have the impression that this is not working properly and my suspicion is that kmail is not passing the whole e-mail to sa-learn so that it could learn the tokens. The reason is the --no-sync option which stores what is learned outside the main spamassassin database. You need to manually run 'sa-learn --sync' from time to time, to incorporate the learned results into the spamassassin database. You could instead remove the --no-sync options, but that would slow down the spam filtering operations so is not a good idea if you receive much mail. -- David Jarvie.
Re: Error starting second X session after Xorg upgrade
On Tuesday 25 July 2006 21:04, D. Michael 'Silvan' McIntyre wrote: On Tuesday 25 July 2006 2:34 pm, D. Michael 'Silvan' McIntyre wrote: It's broken, with no trace in its server's config for how I ever had it set up in the first place. I wonder how that happened? Because I'm an idiot. I was looking at the server, not the terminal. The inittab in question is on the terminal, stupid. (Which is probably only broken because I've reverted to a stock kdmrc on the server, which leaves out the necessary options to make it play nice with the terminal.) 6:23:respawn:/usr/bin/X11/X :0 vt6 -query my.server 7:23:respawn:/usr/bin/X11/X :1 vt7 -query my.server 8:23:respawn:/usr/bin/X11/X :2 vt8 -query my.server You can leave off the -query bit. Of course this realization does nothing to explain why there is no longer an entry for tty7 in either of the more recently upgraded boxes' inittabs. Was it never there to start with? Maybe. I'm stretched pretty thin lately. I would expect the above to work if you stick it in your /etc/inittab. Adding a new session to KDM to load KDE out of /opt is another matter i haven't really considered. I tried adding the following lines to /etc/inittab: 7:45:respawn:/usr/bin/X11/X :0 vt7 8:45:respawn:/usr/bin/X11/X :1 vt8 but they just activate X sessions (i.e. nothing is visible except the moire pattern shown when X starts up) on VT7 and VT8 - kdm is not activated. I tried again to modify kdmrc to make it work on VT7 and VT8, and managed to get the login screen to appear on both, but on VT8, .xsession-errors shows that when I try to log in, it attempts to run the KDE session on display :0 rather than the expected :1. Any ideas on how to fix this? -- David Jarvie -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Error starting second X session after Xorg upgrade
Until I upgraded Xorg a couple of weeks ago, I was able to use the command startx -e /opt/kde3.5/bin/startkde -- :1 to start up a second KDE X session while KDE was running on the first X display. Since the upgrade, X starts up but immediately fails with the error xterm: bad command line option xterm followed by an xterm usage message. I presume the xterm in question is the one which is always displayed as the console when I run a second KDE session, but I can't work out where it is invoked. I'm running a home-compiled KDE 3.5.3. Any pointers to where xterm is run from and where the error is occurring would be very welcome. (I've tried and failed previously to set up kdmrc to allow a normal KDM login on the second X display - that would be an acceptable alternative to getting startx to work.) -- David Jarvie. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: khelpcenter build index cache of application manuals
On Friday 9 June 2006 8:30, Arias Hung wrote: What's the deal? Anyone know or can point me to the 'official' way of building the application manual index so I can once and for all pull up the khelpcenter help for the application i'm looking for help in? I don't know how to overcome the error you're getting. But you should still be able to use the application manuals without building the index. Just skip that step, and things should work. -- David Jarvie. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kmail 3.5.2-1+b1 Hangups
On Saturday 06 May 2006 17:41, Chris wrote: Anyone know what could be causing kmail to hang up intermittantly for at least 30 seconds before responding. I have quite a few local mail directories with more than 1000 mails, but that shouldn't really be a problem, should it? One thing you could try would be to delete any search folders. I don't know whether the fault has been fixed yet, but the existence of search folders used to cause problems similar to yours. -- David Jarvie. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
libglib2 error with aRts
I run a self-compiled KDE (using the latest vanilla KDE sources) on etch. Recently, aRts sound has not worked since an upgrade to libglib2.0-0. The console error message when I try to open a sound file is: ***MEMORY-ERROR***: [13057]: GSlice: failed to allocate 248 bytes (alignment: 256): Invalid argument When I tried downgrading to libglib2.0-0_2.8.6, aRts worked again, but because that breaks other packages, I have reinstalled the current libglib2.0-02.10.2-1, even though aRts fails. How can I make aRts work with the new libglib2.0-0? I have tried recompiling aRts more than once, but it doesn't help. Presumably the official Debian arts package works, so it must be possible to fix this. If there is a better list to post this question on, please let me know. -- David Jarvie. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343643: kalarm: Error loading calendar due to expired.ics
I just noticed this bug report. Do you still have the file /home/eike/.kde/share/apps/kalarm/expired.ics which caused the error? If so, please attach it. Did you do as instructed, i.e. fix or delete the file, but nonetheless the error kept reappearing? -- David Jarvie. KAlarm author and maintainer. http://www.astrojar.org.uk/linux/kalarm.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
branches/KDE/3.4/kdepim/debian
SVN commit 410340 by djarvie:
Improve KAlarm description
M +12 -3 branches/KDE/3.4/kdepim/debian/control
--- branches/KDE/3.4/kdepim/debian/control #410339:410340
@@ -72,10 +72,19 @@
Depends: ${shlibs:Depends}
Suggests: kmix (= 4:3.1.0)
Description: KDE alarm message and command scheduler
- KAlarm is a personal alarm message, command and email scheduler. It lets you
- set up personal alarm messages which pop up on the screen at the chosen
- time, or you can schedule commands to be executed or emails to be sent.
+ KAlarm provides a graphical interface to schedule personal timed events -
+ pop-up alarm messages, command execution and sending emails. There is a
+ range of options for configuring recurring events.
.
+ A pop-up alarm can show either a simple text message, or the contents of a
+ text or image file, It can optionally play a sound file. You can choose its
+ appearance, and set reminders. Among KAlarm's other facilities, you can set
+ up templates to allow KAlarm to be used as a 'tea timer'.
+ .
+ As an alternative to using the graphical interface, alarms can be scheduled
+ from the command line or via DCOP calls from other programs. KAlarm is
+ KDE-based, but will also run on other desktops.
+ .
This package is part of the official KDE pim module.
Package: kandy
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
trunk/KDE/kdepim/debian
SVN commit 409351 by djarvie:
Improve KAlarm description, suggest kttsd
M +14 -5 trunk/KDE/kdepim/debian/control
--- trunk/KDE/kdepim/debian/control #409350:409351
@@ -70,12 +70,21 @@
Section: kde
Architecture: any
Depends: ${shlibs:Depends}
-Suggests: kmix (= 4:3.1.0)
-Description: KDE alarm message and command scheduler
- KAlarm is a personal alarm message, command and email scheduler. It lets you
- set up personal alarm messages which pop up on the screen at the chosen
- time, or you can schedule commands to be executed or emails to be sent.
+Suggests: kmix (= 4:3.1.0), kttsd
+Description: KDE alarm message, command and email scheduler
+ KAlarm provides a graphical interface to schedule personal timed events -
+ pop-up alarm messages, command execution and sending emails. There is a
+ range of options for configuring recurring events.
.
+ A pop-up alarm can show either a simple text message, or the contents of a
text
+ or image file, It can optionally be spoken, or play a sound file. You can
+ choose its appearance, and set reminders. Among KAlarm's other facilities,
+ you can set up templates to allow KAlarm to be used as a 'tea timer'.
+ .
+ As an alternative to using the graphical interface, alarms can be scheduled
+ from the command line or via DCOP calls from other programs. KAlarm is
+ KDE-based, but will also run on other desktops.
+ .
This package is part of the official KDE pim module.
Package: kandy
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
trunk/KDE/kdepim/debian
SVN commit 409353 by djarvie: Remove obsolete module D trunk/KDE/kdepim/debian/kdepim-doc-html.doc-base.kcontrol-kalarmd -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
kdepim/debian
CVS commit by djarvie: Remove doc/kcontrol/kalarmd (module removed). Remove libkalarmd.so (no longer a shared library). M +0 -3 kalarm.install 1.10 --- kdepim/debian/kalarm.install #1.9:1.10 @@ -1,6 +1,4 @@ debian/tmp/usr/bin/kalarm debian/tmp/usr/bin/kalarmd -debian/tmp/usr/lib/libkalarmd.so.0 -debian/tmp/usr/lib/libkalarmd.so.0.0.0 debian/tmp/usr/share/applications/kde/kalarm.desktop debian/tmp/usr/share/applnk/.hidden/kalarmd.desktop @@ -10,5 +8,4 @@ debian/tmp/usr/share/autostart/kalarmd.autostart.desktop debian/tmp/usr/share/doc/kde/HTML/en/kalarm -debian/tmp/usr/share/doc/kde/HTML/en/kcontrol/kalarmd debian/tmp/usr/share/icons/crystalsvg/16x16/actions/kalarm.png debian/tmp/usr/share/icons/crystalsvg/16x16/apps/kalarm.png
kdepim/debian/man
CVS commit by djarvie: --login option removed. Update program description. M +1 -3 kalarmd.man 1.2 --- kdepim/debian/man/kalarmd.man #1.1:1.2 @@ -1,5 +1,5 @@ .TH KALARMD 1 .SH NAME -kalarmd \- KDE alarm daemon +kalarmd \- KAlarm alarm daemon .SH SYNOPSIS .B kalarmd @@ -11,6 +11,4 @@ .SH PROGRAM OPTIONS .TP -.B --login -Application is being auto-started at KDE session start. .so kdeopt.man .SH SEE ALSO
kdepim/debian
CVS commit by djarvie:
Add kmix as suggested package for KAlarm
M +1 -0 control 1.97
--- kdepim/debian/control #1.96:1.97
@@ -71,4 +71,5 @@
Architecture: any
Depends: ${shlibs:Depends}
+Suggests: kmix (= 4:3.1.0)
Description: KDE alarm message and command scheduler
KAlarm is a personal alarm message, command and email scheduler. It lets you
