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#1022149: ktimetracker total data loss
This looks of it could be the same issue as bug 1021938, which is due to a regression in libical version 3.0.15. -- David Jarvie KAlarm author, KDE developer
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.
Bug#993322: firehol: Firehol delays system startup
On Tue, 31 Aug 2021 11:55:02 +0200 Jerome BENOIT wrote: > >> Is you configuration waiting for any iface (see WAIT_FOR_IFACE (/etc/ default/ > > firehol)) ? > > > > Yes, it waits for my Ethernet interface: > > > > WAIT_FOR_IFACE="enp2s0" > > > > This is consistent with the log file you sent. > > If you do not really need to wait for the IFACE, try to empty the list. > > On my laptop box which is configure only for the unique Wifi IFACE, > I mange firehol with a simple ifupdown script (interfaces(1)) > so that I can empty the above list. > > Please let us know if this can fix your issue. I've removed the WAIT_FOR_IFACE statement from /etc/default/firehol, and set up a script /etc/network/if-up.d/firehol to execute a 'firehol restart' command. This has eliminated the boot process delay, and Firehol initialises correctly. Thank you. David.
Bug#993322: firehol: Firehol delays system startup
On Tue, 31 Aug 2021 08:53:55 +0200 Jerome BENOIT wrote: > Did the same happen with your previous firehol package ? I didn't have this issue with Firehol on my previous system. That system was quite old - Debian 8 (Jessie). It has only happened since installing Bullseye. > Is you configuration waiting for any iface (see WAIT_FOR_IFACE (/etc/default/ firehol)) ? Yes, it waits for my Ethernet interface: WAIT_FOR_IFACE="enp2s0"
Bug#993322: firehol: Firehol delays system startup
Package: firehol Version: 3.1.7+ds-2 Severity: normal Dear Maintainer, At each system boot, Firehol takes a full minute to initialise, and makes the boot process hang for some of that time. Looking at the system log (attached), it isn't obvious why Firehol takes just over 1 minute to complete, or why nothing seems to happen between 19:49:40 and 19:50:08, during which a console message is displayed saying that the boot process is waiting for Firehol to finish. The command 'firehol restart' takes very little time to complete once the system is up and running. This indicates that something is wrong at boot time, and that Firehol is presumably waiting for something else to complete. I would have expected Firehol to initialise quickly during boot, and not to hang the boot process. I attach the journalctl output, from Firehol start to Firehol completion: -- System Information: Debian Release: 11.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-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 firehol depends on: ii firehol-common 3.1.7+ds-2 ii init-system-helpers 1.60 ii lsb-base 11.1.0 Versions of packages firehol recommends: ii fireqos 3.1.7+ds-2 Versions of packages firehol suggests: ii firehol-doc3.1.7+ds-2 pn firehol-tools pn ulogd2 -- Configuration Files: /etc/default/firehol changed: START_FIREHOL=YES WAIT_FOR_IFACE="enp2s0" FIREHOL_ESTABLISHED_ACTIVATION_ACCEPT=0 /etc/firehol/firehol.conf changed: version 6 stewjar=192.168.178.100 local="192.168.178.101 192.168.178.102 192.168.178.103" m2885fw=192.168.178.90 interface4 enp2s0 ethernet # The default policy is DROP. You can be more polite with REJECT. # Prefer to be polite on your own clients to prevent timeouts. policy drop # Protect from the internet. protection strong # The following means that this machine can REQUEST anything via enp2s0. client all accept # Specific services that this machine needs to request via enp2s0. client multicast accept client dhcp accept # Services that this machine offers to local network. server ping accept src "$local" server ssh accept src "$local" server cups accept src "$local" # Samsung M2885FW printer (needs both client and server) # The script 'scanner-enable' must be run after Firehol, to fix # iptables entries to allow SNMP to work properly. client snmp accept dst $m2885fw server snmp accept src $m2885fw server samba accept # The following enp2s0 server ports are not known by FireHOL: # tcp/45485 tcp/49074 tcp/7741 udp/32768 udp/32769 udp/517 udp/518 udp/5353 udp/7741 udp/972 # TODO: If you need any of them, you should define new services. # (see Adding Services at the web site - http://firehol.sf.net). interface usb0 usb policy accept Aug 30 19:49:07 desktop systemd[1]: Starting Set console font and keymap... Aug 30 19:49:07 desktop systemd[1]: Starting Firehol stateful packet filtering firewall for humans... Aug 30 19:49:07 desktop systemd[1]: Starting Tell Plymouth To Write Out Runtime Data... Aug 30 19:49:07 desktop systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped. Aug 30 19:49:07 desktop systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped. Aug 30 19:49:07 desktop systemd[1]: Received SIGRTMIN+20 from PID 174 (plymouthd). Aug 30 19:49:07 desktop systemd[1]: Finished Tell Plymouth To Write Out Runtime Data. Aug 30 19:49:07 desktop systemd[1]: Finished Set console font and keymap. Aug 30 19:49:07 desktop systemd[1]: Finished Flush Journal to Persistent Storage. Aug 30 19:49:07 desktop systemd[1]: Starting Create Volatile Files and Directories... Aug 30 19:49:07 desktop systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped. Aug 30 19:49:07 desktop systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. Aug 30 19:49:07 desktop systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped. Aug 30 19:49:07 desktop systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. Aug 30 19:49:07 desktop systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped. Aug 30 19:49:07 desktop systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. Aug 30 19:49:08 desktop systemd[1]: Finished Create Volatile Files and Directories. Aug 30
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.
Bug#685725: Bug still exists in Wheezy
Just to confirm that this bug still happens in Wheezy. stunnel4 3:4.53-1.1 postfix 2.9.6-2 -- David Jarvie. KDE developer. KAlarm author -- http://www.astrojar.org.uk/kalarm -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#713042: linux-image-3.2.0-4-686-pae: USB webcam turns on but fails to work (regression)
I thought wrongly that all my packages were up to date after installing Wheezy, which was when I reported the bug. I've now updated to 3.2.46-1 and the bug is indeed fixed. Sorry for the noise. -- David Jarvie. KDE developer. KAlarm author -- http://www.astrojar.org.uk/kalarm -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685725: Reordering services at bootup doesn't fix the problem
I tried reordering the postfix and stunnel services at bootup, by renaming /etc/rc*.d/S21stunnel4 to /etc/rc*.d/S23stunnel4. This makes no difference to the problem. Mails to be sent still get deferred until I execute '/etc/init.d/stunnel4 restart'. -- David Jarvie. KDE developer. KAlarm author -- http://www.astrojar.org.uk/kalarm -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685725: stunnel4: When postfix is used with stunnel, stunnel needs to be restarted before mails will send
Package: stunnel4 Version: 3:4.29-1 Severity: normal I have to use stunnel with postfix in order to achieve TLS wrapper mode for sending mails. Each time after booting, mails get deferred instead of sent. This continues to happen until I run '/etc/init.d/stunnel4 restart'. From then on, mails are sent successfully. The stunnel4 and postfix startup scripts are installed as S21stunnel4 and S22postfix. Perhaps the solution would be to change the stunnel4 script to S23stunnel4 instead, so as to change the order of their startup? (I haven't yet tried this, so I don't know.) My postfix configuration file is as follows. /etc/postfix/main.cf: smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) biff = no append_dot_mydomain = no readme_directory = no #=Options for using stunnel wrapper for TLS=== smtp_use_tls = no smtp_enforce_tls = no relayhost = [127.0.0.1]:11125 #=End stunnel Options=== smtp_sasl_auth_enable = yes smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd smtp_sasl_security_options = smtp_sasl_auth_soft_bounce = no myhostname = abcdefg alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases mydestination = abcdefg, localhost.localdomain, localhost mynetworks = 127.0.0.0/8 [:::127.0.0.0]/104 [::1]/128 mailbox_command = procmail -a $EXTENSION mailbox_size_limit = 0 recipient_delimiter = inet_interfaces = all inet_protocols = ipv4 -- System Information: Debian Release: 6.0.5 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'proposed-updates') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-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/dash Versions of packages stunnel4 depends on: ii adduser3.112+nmu2add and remove users and groups ii libc6 2.11.3-3 Embedded GNU C Library: Shared lib ii libssl0.9.80.9.8o-4squeeze13 SSL shared libraries ii libwrap0 7.6.q-19 Wietse Venema's TCP wrappers libra ii netbase4.45 Basic TCP/IP networking system ii openssl0.9.8o-4squeeze13 Secure Socket Layer (SSL) binary a ii perl-modules 5.10.1-17squeeze3 Core Perl modules stunnel4 recommends no packages. Versions of packages stunnel4 suggests: pn logcheck-database none (no description available) -- Configuration Files: /etc/default/stunnel4 changed: ENABLED=1 FILES=/etc/stunnel/*.conf OPTIONS= PPP_RESTART=0 /etc/stunnel/stunnel.conf changed: ; Sample stunnel configuration file by Michal Trojnara 2002-2009 ; Some options used here may not be adequate for your particular configuration ; Please make sure you understand them (especially the effect of the chroot jail) ; Certificate/key is needed in server mode and optional in client mode cert = /etc/stunnel/stunnel.pem ;key = /etc/ssl/certs/stunnel.pem ; Protocol version (all, SSLv2, SSLv3, TLSv1) sslVersion = SSLv3 ; Some security enhancements for UNIX systems - comment them out on Win32 chroot = /var/lib/stunnel4/ setuid = stunnel4 setgid = stunnel4 ; PID is created inside the chroot jail pid = /stunnel4.pid ; Some performance tunings socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 ;compression = zlib ; Workaround for Eudora bug ;options = DONT_INSERT_EMPTY_FRAGMENTS ; Authentication stuff ;verify = 2 ; Don't forget to c_rehash CApath ; CApath is located inside chroot jail ;CApath = /certs ; It's often easier to use CAfile ;CAfile = /etc/stunnel/certs.pem ; Don't forget to c_rehash CRLpath ; CRLpath is located inside chroot jail ;CRLpath = /crls ; Alternatively you can use CRLfile ;CRLfile = /etc/stunnel/crls.pem ; Some debugging stuff useful for troubleshooting ;debug = 7 ;output = /var/log/stunnel4/stunnel.log ; Use it for client mode ;client = yes ; Service-level configuration ;[https] ;accept = 443 ;connect = 80 ;TIMEOUTclose = 0 [smtp-tls-wrapper] accept = 11125 client = yes connect = relay.provider.net:465 ; vim:ft=dosini -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.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#510213: acpi-support: Hibernate doesn't work on Lenovo 3000 N200
On Wed, July 29, 2009 4:38 pm, Moritz Muehlenhoff wrote: On Tue, Feb 17, 2009 at 09:00:30AM +0100, Bart Samwel wrote: David Jarvie wrote: It turns out that executing the following command before suspending or hibernating makes things work correctly: modprobe -r ehci_hcd Note that without this command, neither suspend nor hibernate work, and they don't work under a KDE 4 desktop any more either. Hmmm. In that case this is a kernel bug! I'll reassign it. David, does this error still persist with 2.6.30 from unstable? You can install it directly into testing. I haven't had any problem with this recently - I'm currently running stable (which is up to date). So it seems to be fixed. -- David Jarvie. KDE developer. KAlarm author maintainer. http://www.astrojar.org.uk/kalarm -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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-bugs-dist-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-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#510213: acpi-support: Hibernate doesn't work on Lenovo 3000 N200
It turns out that executing the following command before suspending or hibernating makes things work correctly: modprobe -r ehci_hcd Note that without this command, neither suspend nor hibernate work, and they don't work under a KDE 4 desktop any more either. -- David Jarvie -- To UNSUBSCRIBE, email to debian-bugs-dist-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-bugs-dist-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-bugs-dist-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-bugs-dist-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-bugs-dist-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-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#510213: acpi-support: Hibernate doesn't work on Lenovo 3000 N200
Package: acpi-support Version: 0.109-10 Severity: important Hibernate, under a KDE3 desktop, usually doesn't work. This problem was intermittent for some months, but now it happens virtually every time (probably for the last couple of weeks). Here is a bash trace when I ran /etc/acpi/hibernate.sh manually from a terminal window. As can be seen, it seems to be a D-Bus issue. + . /etc/default/acpi-support ++ SUSPEND_METHODS='dbus-pm dbus-hal pm-utils' ++ ACPI_SLEEP=true ++ ACPI_HIBERNATE=true ++ ACPI_SLEEP_MODE=mem ++ MODULES= ++ MODULES_WHITELIST= ++ SAVE_VBE_STATE=true ++ VBESTATE=/var/lib/acpi-support/vbestate ++ POST_VIDEO=true ++ USE_DPMS=true ++ HIBERNATE_MODE=shutdown ++ LOCK_SCREEN=true ++ STOP_SERVICES= ++ RESTART_IRDA=false ++ SKIP_INTERFACES='dummy qemu' + . /usr/share/acpi-support/power-funcs ++ umask 022 ++ PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11 ++ POWERSTATE=/var/lib/acpi-support/powerstate ++ HDPARM='/sbin/hdparm -q' ++ LIDSTATE=/var/lib/acpi-support/lidstate + . /usr/share/acpi-support/device-funcs + . /usr/share/acpi-support/policy-funcs ++ . /usr/share/acpi-support/power-funcs +++ umask 022 +++ PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/bin/X11 +++ POWERSTATE=/var/lib/acpi-support/powerstate +++ HDPARM='/sbin/hdparm -q' +++ LIDSTATE=/var/lib/acpi-support/lidstate + . /usr/share/acpi-support/key-constants ++ KEY_RESERVED=0 ++ KEY_ESC=1 ++ KEY_1=2 ++ KEY_2=3 ++ KEY_3=4 ++ KEY_4=5 ++ KEY_5=6 ++ KEY_6=7 ++ KEY_7=8 ++ KEY_8=9 ++ KEY_9=10 ++ KEY_0=11 ++ KEY_MINUS=12 ++ KEY_EQUAL=13 ++ KEY_BACKSPACE=14 ++ KEY_TAB=15 ++ KEY_Q=16 ++ KEY_W=17 ++ KEY_E=18 ++ KEY_R=19 ++ KEY_T=20 ++ KEY_Y=21 ++ KEY_U=22 ++ KEY_I=23 ++ KEY_O=24 ++ KEY_P=25 ++ KEY_LEFTBRACE=26 ++ KEY_RIGHTBRACE=27 ++ KEY_ENTER=28 ++ KEY_LEFTCTRL=29 ++ KEY_A=30 ++ KEY_S=31 ++ KEY_D=32 ++ KEY_F=33 ++ KEY_G=34 ++ KEY_H=35 ++ KEY_J=36 ++ KEY_K=37 ++ KEY_L=38 ++ KEY_SEMICOLON=39 ++ KEY_APOSTROPHE=40 ++ KEY_GRAVE=41 ++ KEY_LEFTSHIFT=42 ++ KEY_BACKSLASH=43 ++ KEY_Z=44 ++ KEY_X=45 ++ KEY_C=46 ++ KEY_V=47 ++ KEY_B=48 ++ KEY_N=49 ++ KEY_M=50 ++ KEY_COMMA=51 ++ KEY_DOT=52 ++ KEY_SLASH=53 ++ KEY_RIGHTSHIFT=54 ++ KEY_KPASTERISK=55 ++ KEY_LEFTALT=56 ++ KEY_SPACE=57 ++ KEY_CAPSLOCK=58 ++ KEY_F1=59 ++ KEY_F2=60 ++ KEY_F3=61 ++ KEY_F4=62 ++ KEY_F5=63 ++ KEY_F6=64 ++ KEY_F7=65 ++ KEY_F8=66 ++ KEY_F9=67 ++ KEY_F10=68 ++ KEY_NUMLOCK=69 ++ KEY_SCROLLLOCK=70 ++ KEY_KP7=71 ++ KEY_KP8=72 ++ KEY_KP9=73 ++ KEY_KPMINUS=74 ++ KEY_KP4=75 ++ KEY_KP5=76 ++ KEY_KP6=77 ++ KEY_KPPLUS=78 ++ KEY_KP1=79 ++ KEY_KP2=80 ++ KEY_KP3=81 ++ KEY_KP0=82 ++ KEY_KPDOT=83 ++ KEY_103RD=84 ++ KEY_ZENKAKUHANKAKU=85 ++ KEY_102ND=86 ++ KEY_F11=87 ++ KEY_F12=88 ++ KEY_RO=89 ++ KEY_KATAKANA=90 ++ KEY_HIRAGANA=91 ++ KEY_HENKAN=92 ++ KEY_KATAKANAHIRAGANA=93 ++ KEY_MUHENKAN=94 ++ KEY_KPJPCOMMA=95 ++ KEY_KPENTER=96 ++ KEY_RIGHTCTRL=97 ++ KEY_KPSLASH=98 ++ KEY_SYSRQ=99 ++ KEY_RIGHTALT=100 ++ KEY_LINEFEED=101 ++ KEY_HOME=102 ++ KEY_UP=103 ++ KEY_PAGEUP=104 ++ KEY_LEFT=105 ++ KEY_RIGHT=106 ++ KEY_END=107 ++ KEY_DOWN=108 ++ KEY_PAGEDOWN=109 ++ KEY_INSERT=110 ++ KEY_DELETE=111 ++ KEY_MACRO=112 ++ KEY_MUTE=113 ++ KEY_VOLUMEDOWN=114 ++ KEY_VOLUMEUP=115 ++ KEY_POWER=116 ++ KEY_KPEQUAL=117 ++ KEY_KPPLUSMINUS=118 ++ KEY_PAUSE=119 ++ KEY_KPCOMMA=121 ++ KEY_HANGUEL=122 ++ KEY_HANJA=123 ++ KEY_YEN=124 ++ KEY_LEFTMETA=125 ++ KEY_RIGHTMETA=126 ++ KEY_COMPOSE=127 ++ KEY_STOP=128 ++ KEY_AGAIN=129 ++ KEY_PROPS=130 ++ KEY_UNDO=131 ++ KEY_FRONT=132 ++ KEY_COPY=133 ++ KEY_OPEN=134 ++ KEY_PASTE=135 ++ KEY_FIND=136 ++ KEY_CUT=137 ++ KEY_HELP=138 ++ KEY_MENU=139 ++ KEY_CALC=140 ++ KEY_SETUP=141 ++ KEY_SLEEP=142 ++ KEY_WAKEUP=143 ++ KEY_FILE=144 ++ KEY_SENDFILE=145 ++ KEY_DELETEFILE=146 ++ KEY_XFER=147 ++ KEY_PROG1=148 ++ KEY_PROG2=149 ++ KEY_WWW=150 ++ KEY_MSDOS=151 ++ KEY_COFFEE=152 ++ KEY_DIRECTION=153 ++ KEY_CYCLEWINDOWS=154 ++ KEY_MAIL=155 ++ KEY_BOOKMARKS=156 ++ KEY_COMPUTER=157 ++ KEY_BACK=158 ++ KEY_FORWARD=159 ++ KEY_CLOSECD=160 ++ KEY_EJECTCD=161 ++ KEY_EJECTCLOSECD=162 ++ KEY_NEXTSONG=163 ++ KEY_PLAYPAUSE=164 ++ KEY_PREVIOUSSONG=165 ++ KEY_STOPCD=166 ++ KEY_RECORD=167 ++ KEY_REWIND=168 ++ KEY_PHONE=169 ++ KEY_ISO=170 ++ KEY_CONFIG=171 ++ KEY_HOMEPAGE=172 ++ KEY_REFRESH=173 ++ KEY_EXIT=174 ++ KEY_MOVE=175 ++ KEY_EDIT=176 ++ KEY_SCROLLUP=177 ++ KEY_SCROLLDOWN=178 ++ KEY_KPLEFTPAREN=179 ++ KEY_KPRIGHTPAREN=180 ++ KEY_F13=183 ++ KEY_F14=184 ++ KEY_F15=185 ++ KEY_F16=186 ++ KEY_F17=187 ++ KEY_F18=188 ++ KEY_F19=189 ++ KEY_F20=190 ++ KEY_F21=191 ++ KEY_F22=192 ++ KEY_F23=193 ++ KEY_F24=194 ++ KEY_PLAYCD=200 ++ KEY_PAUSECD=201 ++ KEY_PROG3=202 ++ KEY_PROG4=203 ++ KEY_SUSPEND=205 ++ KEY_CLOSE=206 ++ KEY_PLAY=207 ++ KEY_FASTFORWARD=208 ++ KEY_BASSBOOST=209 ++ KEY_PRINT=210 ++ KEY_HP=211 ++ KEY_CAMERA=212 ++ KEY_SOUND=213 ++ KEY_QUESTION=214 ++ KEY_EMAIL=215 ++ KEY_CHAT=216 ++ KEY_SEARCH=217 ++ KEY_CONNECT=218 ++ KEY_FINANCE=219 ++ KEY_SPORT=220 ++ KEY_SHOP=221 ++ KEY_ALTERASE=222 ++ KEY_CANCEL=223 ++ KEY_BRIGHTNESSDOWN=224 ++
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]
Bug#459237: acpid: video is omitted from MODULES
Package: acpid Version: 1.0.4-7.1 Severity: normal On my Lenovo 3000 N200 laptop, /etc/default/acpid had the following MODULES line when I installed a fresh Lenny system: MODULES=battery ac processor button fan thermal In order to allow the laptop's video brightness buttons to work, it also needs to include 'video' in the list of MODULES. Otherwise, the pressing a brightness button does not register as an ACPI event. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') 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 acpid depends on: ii libc6 2.7-5 GNU C Library: Shared libraries ii lsb-base 3.1-24 Linux Standard Base 3.1 init scrip acpid recommends no packages. -- no debconf information -- 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
Bug#390890: upgrade deletes toolbar customizations
This bug should not be closed - it definitely still exists. It is in fact a design limitation in the KDE libraries which causes the bug, and is not specific to KMail - it applies to all applications which use the standard KDE toolbar configuration mechanism. -- David Jarvie. KAlarm author maintainer. http://www.astrojar.org.uk/kalarm
Bug#277908: knotes: Systray icon does not have transparent background
There is a similar bug report for KAlarm on Gentoo (KDE bug report 122988, http://bugs.kde.org/show_bug.cgi?id=122988). There, the icon background colour is whatever is currently set as the KDE window background colour. It would be interesting to know if the KNotes icon similarly changes colour if you change the window background colour setting. If the two bugs are actually related, it would suggest that some underlying KDE configuration bug is the cause. -- David Jarvie. KAlarm author maintainer. http://www.astrojar.org.uk/kalarm
Bug#277908: knotes: Systray icon does not have transparent background
The bug which showed up for KAlarm turns out to be caused by a bug in the QtCurve style. You should check whether the same or similar bug is causing the KNotes icon to display wrongly, by changing to a different style. -- 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#405589: kalarm manpages out of date
Package: kalarm Version: 4:3.5.5.dfsg.1-4 Severity: normal Tags: patch The files debian/man/kalarm.man and debian/man/kalarmd.man in the kdepim source package are out of date. KAlarm has had several new command line options added since the current package files were generated, and kalarmd has had its one command line option renamed. Additionally, the descriptions need amendment. I attach new versions which correspond with the current KDE 3.5 branch SVN sources. David Jarvie. KAlarm author maintainer. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-dj Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages kalarm depends on: ii kdelibs4c2a4:3.5.5a.dfsg.1-5 core libraries and binaries for al ii libacl12.2.41-1 Access control list shared library ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libarts1c2a1.5.5-1 aRts sound system core components ii libattr1 2.4.32-1 Extended attribute shared library ii libaudio2 1.8-2 The Network Audio System (NAS). (s ii libc6 2.3.6.ds1-8 GNU C Library: Shared libraries ii libfam02.7.0-11 Client library to control the FAM ii libfontconfig1 2.4.1-2 generic font configuration library ii libfreetype6 2.2.1-5 FreeType 2 font engine, shared lib ii libgcc11:4.1.1-19GCC support library ii libice61:1.0.1-2 X11 Inter-Client Exchange library ii libidn11 0.6.5-1 GNU libidn library, implementation ii libjpeg62 6b-13 The Independent JPEG Group's JPEG ii libkcal2b 4:3.5.5.dfsg.1-4 KDE calendaring library ii libkdepim1a4:3.5.5.dfsg.1-4 KDE PIM library ii libkmime2 4:3.5.5.dfsg.1-4 KDE MIME interface library ii libkpimidentities1 4:3.5.5.dfsg.1-4 KDE PIM user identity information ii libktnef1 4:3.5.5.dfsg.1-4 Library for handling KTNEF email a ii libpng12-0 1.2.15~beta5-1PNG library - runtime ii libqt3-mt 3:3.3.7-1 Qt GUI Library (Threaded runtime v ii libsm6 1:1.0.1-3 X11 Session Management library ii libstdc++6 4.1.1-19 The GNU Standard C++ Library v3 ii libx11-6 2:1.0.3-4 X11 client-side library ii libxcursor11.1.7-4 X cursor management library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxft22.1.8.2-8 FreeType-based font drawing librar ii libxi6 1:1.0.1-4 X11 Input extension library ii libxinerama1 1:1.0.1-4.1 X11 Xinerama extension library ii libxrandr2 2:1.1.0.2-5 X11 RandR extension library ii libxrender11:0.9.1-3 X Rendering Extension client libra ii libxt6 1:1.0.2-2 X11 toolkit intrinsics library ii zlib1g 1:1.2.3-13compression library - runtime kalarm recommends no packages. .TH KALARM 1 .SH NAME kalarm \- Personal alarm message, command and email scheduler for KDE .SH SYNOPSIS .B kalarm .I [Qt-options] [KDE-options] [options] [message] .SH DESCRIPTION \fBKAlarm\fP 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. .SH PROGRAM OPTIONS .TP .B -a, --ack-confirm Prompt for confirmation when alarm is acknowledged. .TP .B -A, --attach \fIurl\fB Attach file to email (repeat as needed). .TP .B --auto-close Auto-close alarm window after --late-cancel period. .TP .B --bcc Blind copy email to self. .TP .B -b, --beep Beep when message is displayed. .TP .B -c, --color \fIcolor\fB Message background color (name or hex 0xRRGGBB). .TP .B -C, --colorfg \fIcolor\fB Message foreground color (name or hex 0xRRGGBB). .TP .B --calendarURL \fIurl\fB URL of calendar file. .TP .B --cancelEvent \fIeventID\fB Cancel alarm with the specified event ID. .TP .B -d, --disable Disable the alarm. .TP .B -e, --exec \fIcommandline\fB Execute a shell command line. .TP .B --edit \fIeventID\fB Display the alarm edit dialog to edit the specified alarm. .TP .B -n, --edit-new Display the alarm edit dialog to edit a new alarm. .TP .B --edit-new-preset \fItemplateName\fB Display the alarm edit dialog, preset with a template. .TP .B -f, --file \fIurl\fB File to display. .TP .B -F, --from-id \fIID\fB KMail identity to use as sender of email. .TP .B --handleEvent \fIeventID\fB Trigger or cancel alarm with the specified event ID. .TP .B -i, --interval \fIperiod\fB Interval between alarm
Bug#367935: checkinstall's temporary script is deleted by installwatch and installation therefore fails
The bug has occurred again. I built Qt 4 (downloaded from KDE's SVN qt-copy), and then tried to install it with this command: checkinstall --pkgname=qt4x make install_qmake install_mkspecs sub-src-install_subtargets sub-tools-install_subtargets install_htmldocs It's a pretty big package to install, but it happens to produce the bug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#367935: checkinstall's temporary script is deleted by installwatch and installation therefore fails
On Wednesday 07 June 2006 06:42, Felipe Sateler wrote: What is the install command you are using? Can you easily reproduce this bug? I tried reinstalling checkinstall-1.5.3-3, and now it seems to work without my patch. It previously failed consistently for a period of weeks, and I have no idea why it now works when previously it didn't (unless either there is something in the rand calls which is time sensitive, or another library has changed). It used to fail even with a simple test script containing something like mkdir -p /var/tmp/abcde. However, I still think that my patch (or something else with a similar effect) is a sensible precaution, since it eliminates any possibility that checkinstall and installwatch can use the same temporary directory, and therefore prevents the problem I described. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#367935: checkinstall's temporary script is deleted by installwatch and installation therefore fails
Package: checkinstall
Version: 1.5.3-3
Severity: grave
Tags: patch
Justification: renders package unusable
Checkinstall creates a script in a temporary directory for execution
by installwatch. Installwatch also uses a temporary directory, which
it removes if it already exists. Checkinstall and installwatch both
use the same algorithm to create a temporary directory name, with the
result that they both use the same temporary directory, so that
installwatch deletes the directory containing checkinstall's script.
There is then nothing for installwatch to execute, resulting in a
failure message:
/usr/bin/installwatch: line 345:
/var/tmp/KIKjLRhMLrIpmlArapqN/installscript.sh: No such file or directory
This can be fixed with certainty by making the temporary directory names
used by checkinstall and installwatch different lengths, as in the
following patch.
=
--- /usr/bin/checkinstall 2004-04-12 13:58:38.0 +0100
+++ checkinstall2006-05-18 19:08:37.0 +0100
@@ -656,7 +656,7 @@
# Find a safe TMP_DIR
-TMP_DIR=${BASE_TMP_DIR}/`awk 'BEGIN { srand(); for (i=1;i21;i++) { a=95;
while (a 90 a 97) { a=65+int(50*rand())}; printf(%c, a) } }'`
+TMP_DIR=${BASE_TMP_DIR}/`awk 'BEGIN { srand(); for (i=1;i22;i++) { a=95;
while (a 90 a 97) { a=65+int(50*rand())}; printf(%c, a) } }'`
[ -e $TMP_DIR ] rm -rf $TMP_DIR
if [ -e $TMP_DIR ]; then
echo
=
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-k7
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Versions of packages checkinstall depends on:
ii file4.17-1 Determines file type using magic
ii installwatch0.7.0beta4-1 Track installation of local softwa
checkinstall recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#367966: checkinstall package has disappeared from testing
Package: checkinstall Version: 1.5.3-3 Severity: normal checkinstall no longer exists in the 'testing' distribution, yet is in both 'stable' and 'unstable'. It should be reinstated in 'testing'. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-k7 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages checkinstall depends on: ii file4.17-1 Determines file type using magic ii installwatch0.7.0beta4-1 Track installation of local softwa checkinstall recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#367077: installwatch: Segmentation faults on mkdir, cp
Package: installwatch Version: 0.6.3-2 Severity: grave Justification: renders package unusable Whenever I run checkinstall, I get a segmentation fault when it invokes installwatch. It used to work until around 2 - 4 weeks ago. This fault renders checkinstall useless. The output on the console is, for example: Copying documentation directory... /var/tmp/pBcFXBogLSoZdCkGjJOn/installscript.sh: line 14: 22439 Segmentation fault mkdir -p /usr/share/doc/qt41 The fault occurs even if the directory being created by mkdir already exists. I tried creating a little script and manually running installwatch. The commands 'mkdir' and 'cp' both fail with a segmentation fault, whereas 'echo' doesn't. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-k7 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages installwatch depends on: ii libc6 2.3.6-7GNU C Library: Shared libraries installwatch recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#361270: Upgrade of initramfs-tools made kernel unbootable with lilo
Package: initramfs-tools Version: 0.59b Severity: critical Justification: breaks the whole system Upgrading initramfs-tools yesterday caused the current kernel 2.6.15-1 to become unbootable, apparently because the upgrade process regenerated initrd.img-2.6.15-1-k7. The upgrade process should have warned me to rerun lilo. Note that I normally use kernel 2.6.15-1-k7, rather than 2.6.12 listed below, but due to 2.6.15 being unbootable I had to boot into 2.6.12. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-k7 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages initramfs-tools depends on: ii busybox 1:1.01-4 Tiny utilities for small and embed ii cpio 2.6-11 GNU cpio -- a program to manage ar ii klibc-utils 1.2.4-1small statically-linked utilities ii module-init-tools 3.2.2-2tools for managing Linux kernel mo ii udev 0.088-2/dev/ and hotplug management daemo initramfs-tools recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#361270: Upgrade of initramfs-tools made kernel unbootable with lilo
On Friday 07 April 2006 16:41, maximilian attems wrote: update-initramfs runs lilo, have you also grub around, I don't use grub, but as you will see below, it is installed. (I have had to use it in the past for system recovery when my commercial boot manager corrupted the MBR.) please post output of: dpkg -l grub ||/ Name Version Description +++-=-=-== ii grub 0.97-5GRand Unified Bootloader ls -l /sbin/grub /boot/grub/menu.lst -rw-r--r-- 1 root root 4014 Feb 15 06:50 /boot/grub/menu.lst -rwxr-xr-x 1 root root 137644 Feb 14 21:23 /sbin/grub please post the error message you see at your 2.6.15 boot? I don't remember what it said beyond being a kernel panic - it was early in the boot sequence, at the place where it usually fails if lilo hasn't been run when it should have been. I can't find messages from that boot attempt in any of the log files in /var/log, and I have since run lilo, so I won't be able to replicate it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#361270: Upgrade of initramfs-tools made kernel unbootable with lilo
On Friday 07 April 2006 20:30, maximilian attems wrote: On Fri, Apr 07, 2006 at 08:51:12PM +0100, David Jarvie wrote: if grub is around lilo isn't run. if you really want lilo remove grub from your system and update-initramfs will call lilo. ... i'll document the fact that if you use lilo you shouldn't have grub around in README.Debian. If both lilo and grub are installed, I can understand not running lilo automatically, but surely there should at the very least be a warning prompt about the possible need to run lilo. (And I mean a prompt requiring a response, so that it can't be overlooked when you're doing a bit upgrade of the system.) Essentially, if lilo is installed, make sure the upgrader knows that the system might not boot without further action. The same issue has hit me more than once recently - not just with initramfs-tools upgrades. A mere warning in README.Debian isn't enough given that it could make a system unbootable. Regards, David. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#361270: Upgrade of initramfs-tools made kernel unbootable with lilo
On Friday 07 April 2006 21:44, maximilian attems wrote: kernel-package wants to drop ability to run lilo on the postinstall. grub is the _default_. update-initramfs can easily check for an lilo.conf and warn in those cases. A warning (preferably in the form of a prompt which must be acknowledged) would be fine as far as I'm concerned. I've never been entirely happy about kernel-package offering to replace the MBR or run lilo directly, since my MBR is not written by either lilo or grub. Regards, David. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#306190: acknowledged by developer (filer failed to respond)
I sent you all the information you asked for at the time, in private emails (because you mailed me privately to ask). I attach the most relevant one which should enable you to test out the bug. ---BeginMessage--- On Sun, 24 Apr 2005 16:45, Ben Pfaff wrote: David Jarvie [EMAIL PROTECTED] writes: You failed to provide plenty of critical information, such as what is in configure.in or, preferably, what package this is so I can go look at this. I am not clairvoyant, so I will need this information to provide any help. I wasn't sure how much you would need, so I hoped you would tell me. Try the example source package http://www.astrojar.org.uk/linux/download/kalarm-1.2.6.kde2.tar.bz2 . The package omits Makefile.cvs which you can create in its top level directory: =Makefile.cvs=== all: @echo This Makefile is only for the CVS repository @echo This will be deleted before making the distribution @echo @if test ! -d admin; then \ echo admin directory is missing! ;\ exit 1 ;\ fi $(MAKE) -f admin/Makefile.common cvs .SILENT: =end Makefile.cvs=== If you delete config.h.in, you should find that it not recreated by 'make -f Makefile.cvs' using the current version of autoconf. ---End Message---
Bug#351623: Fix doesn't work for me
I had the same problem since the latest kernel update. I did a 'reiserfsck --clean-attributes' and changed /etc/fstab to add 'noattrs' options, but on at least one reiserfs partition, I'm still getting lots of the same errors. That partition is reiser v3.5 format, while my other reiserfs partitions are v3.6. I haven't yet noticed any problems on the v3.6 partitions, although I didn't get very many before, so they may yet happen. Downgrade to 2.6.12 kernel seems the only answer for now. -- David Jarvie. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#348264: kernel-package: make-kpkg --append-to-version build fails with not in control info
Package: kernel-package Version: 9.008.4 Severity: normal Building linux-source-2.6.12-10 as root with the following commands: make xconfig make-kpkg clean make-kpkg --append-to-version w4l --stem linux kernel_image produces the following error: dpkg-gencontrol -DArchitecture=i386 -isp \ -plinux-image-2.6.12w4l -Pdebian/tmp-image/ dpkg-gencontrol: error: package linux-image-2.6.12w4l not in control info make[1]: *** [real_stamp_image] Error 255 make[1]: Leaving directory `/usr/src/linux-2.6.12-10' make: *** [kernel-image-deb] Error 2 I got it to build by editing debian/control, adding a new entry Package: linux-image-2.6.12w4l which was a copy of the entry Package: linux-image-2.6.12-1-386 but with the package name changed. There doesn't seem to be a way of building the package without manually editing debian/control. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12w4l Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages kernel-package depends on: ii dpkg 1.13.11.0.1package maintenance system for Deb ii dpkg-dev 1.13.11package building tools for Debian ii gcc [c-compiler] 4:4.0.2-2 The GNU C compiler ii gcc-2.95 [c-compiler] 1:2.95.4-22The GNU C compiler ii gcc-3.3 [c-compiler] 1:3.3.6-10 The GNU C compiler ii gcc-4.0 [c-compiler] 4.0.2-5The GNU C compiler ii make 3.80+3.81.b4-1 The GNU version of the make util ii perl 5.8.7-10 Larry Wall's Practical Extraction Versions of packages kernel-package recommends: ii bzip2 1.0.2-11 high-quality block-sorting file co ii libc6-dev [libc-dev] 2.3.5-8GNU C Library: Development Librari -- no debconf information -- 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]
Bug#314351: initscripts: bootclean.sh seems broken
I tried rearranging the order of the arguments to find, and find . -maxdepth 0 -perm -002 works without error. So the fix appears to be very simple. -- David Jarvie. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#316930: Updatedb doesn't run 'find' at the nice priority set in updatedb.conf
Package: findutils Version: 4.2.22-1 My /etc/updatedb.conf contains (among other things): LOCALUSER=root export LOCALUSER NICE=19 export NICE and when updatedb is run by cron from /etc/cron.daily/find, it runs at the expected nice priority of 19. However, when updatedb runs 'find', find's nice level is 0, not 19. Running /etc/cron.daily/find manually as root produces the same result. The output from running it manually and then checking the status with 'ps -eo %p %P %n %a' was: 28410 4824 0 /bin/sh /etc/cron.daily/find 28412 28410 19 /bin/sh /usr/bin/updatedb 28420 28412 19 /bin/sh /usr/bin/updatedb 28422 28412 19 /usr/bin/sort -z -f 28423 28412 19 /usr/lib/locate/frcode -0 28426 28420 0 /usr/bin/find / -ignore_readdir_race ( -fstype NFS -o -fstype nfs -o -fstyp I'm running Debian testing i386, with kernel 2.6.8, with libc6 2.3.2.ds1-22. This bug really makes my system slow down until find finishes - it would be really useful to have it fixed. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#306190: autoconf wrapper fails to run autoheader
Package: autoconf
Version: 2.59a-3
I maintain a source package for an application which uses a KDE-derived build
system. When I run 'make -f Makefile.cvs', it executes the makefile below
(truncated after the autoheader command). However, the autoheader command
fails to produce either any error message or config.h.in. Using version
2.59-8 of autoconf, this worked correctly.
I am running Debian Sarge, i386, all packages up-to-date. The following
packages are also installed on my system: autoconf2.13 2.13-49 and
automake1.6 1.6.3-11.
==Makefile called by Makefile.cvs==
SHELL=/bin/sh
cvs:
@if grep '$$(top_srcdir)/acinclude.m4:' Makefile.am /dev/null; then \
echo *** Creating acinclude.m4 ;\
rm -f acinclude.m4 configure.files ;\
$(MAKE) -f Makefile.am top_srcdir=. acinclude.m4 ;\
fi
@echo !!! If you get recursion errors from autoconf, it is advisable
to set the
@echo environment variable M4 to something including
\--nesting-limit=500\
@if test -r configure.in.in; then \
rm -f subdirs configure.in ;\
echo *** Creating list of subdirectories ;\
$(MAKE) -f Makefile.am top_srcdir=. subdirs ;\
echo *** Creating configure.in ;\
$(MAKE) -f Makefile.am top_srcdir=. configure.in ;\
fi
@echo *** Creating aclocal.m4
@aclocal
@echo *** Creating configure
@autoconf
@if test -r configure.in.in ; then \
perl -pi -e 'print if test \x\$$with_fast_perl\ = \xyes\ ;\
then\n perl -i.bak \$$ac_aux_dir/conf.change.pl \$$CONFIG_STATUS\
|| mv \$$CONFIG_STATUS.bak \$$CONFIG_STATUS;\
\n rm -f \$$CONFIG_STATUS.bak;\nfi\
\n if /^\s*chmod\s+.*\+x\s+.*CONFIG_STATUS/;' configure ;\
fi
@if grep '} \$$ac_kw foo' configure /dev/null 21; then perl -p -i
-e s/ac_kw foo/ac_kw int foo/ configure; fi
#David's hack for autoconf bug when $INSTALL is set
@perl -pi -e 'if (/\[\/\$$\]\*. INSTALL=/) { print $$_ ; $$_ =
\\) ;;\n; }' configure
@if egrep ^AM_CONFIG_HEADER configure.in /dev/null 21; then \
echo *** Creating config.h template ;\
autoheader ;\
fi
==end Makefile called by Makefile.cvs==
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
