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
This bug is no longer applicable. KAlarm no longer uses ktimezoned with Qt5
because it now uses QTimeZone.
--
David Jarvie.
KDE developer, KAlarm author.
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
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.
of Akonadi
will only affect those particular functions.
--
David Jarvie.
KDE developer, KAlarm author.
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.
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
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.
>
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
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,
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.
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
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
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
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
in KAlarm, the bug
actually lies in the relevant Akonadi library package.
--
David Jarvie.
KDE developer.
KAlarm author -- http://www.astrojar.org.uk/kalarm
it under Gnome or other
desktops.
--
David Jarvie.
KDE developer.
KAlarm author -- http://www.astrojar.org.uk/kalarm
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
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
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
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
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
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.
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
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
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
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
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,
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
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
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
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
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
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
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
.
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
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
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
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
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
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
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
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
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
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,
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
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
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
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
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
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
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
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
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
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]
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
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
57 matches
Mail list logo
