https://bugs.kde.org/show_bug.cgi?id=500808
David Jarvie changed:
What|Removed |Added
Resolution|--- |UNMAINTAINED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=500808
--- Comment #3 from David Jarvie ---
Qt 5 is no longer supported for KAlarm. All releases are (since a year ago)
based on Qt 6. Testing on an up to date Qt 6 based KDE Neon system (which is
based on Ubuntu Jammy but with very recent Qt 6 development
https://bugs.kde.org/show_bug.cgi?id=499440
David Jarvie changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=499859
David Jarvie changed:
What|Removed |Added
Component|Akonadi |general
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=499859
--- Comment #7 from David Jarvie ---
I've also realised that kalarm frequently exits with an error from
KAlarmApp::activateInstance() before it does the session restoration. The only
difference from your experience is that I haven't seen a c
https://bugs.kde.org/show_bug.cgi?id=499859
David Jarvie changed:
What|Removed |Added
CC||martin.schnitkemper@nexgo.d
https://bugs.kde.org/show_bug.cgi?id=499859
--- Comment #3 from David Jarvie ---
There have been no changes to kalarm between 24.12.1 and 24.12.2 which would in
any way affect session restoration, so it seems that it must be some external
software change which has triggered the crash. When I
https://bugs.kde.org/show_bug.cgi?id=499859
--- Comment #2 from David Jarvie ---
This crash has also been described in
https://bugs.kde.org/show_bug.cgi?id=497742#c10. (Note that Bug 497742 is about
an unrelated issue.)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=497742
--- Comment #11 from David Jarvie ---
The crash reported in Comment 7 and Comment 8 is not related to the original
bug report. It is in fact the same crash as reported in Bug 499859. If you
(Martin) have any further comments on your crash, enter them
https://bugs.kde.org/show_bug.cgi?id=497742
--- Comment #9 from David Jarvie ---
Can you please attach a copy of your KAlarm calendar file, which will be
~/.local/share/kalarm/calendar.ics unless you have changed it's location. Feel
free to edit it to change any message texts for privacy o
https://bugs.kde.org/show_bug.cgi?id=498753
David Jarvie changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Version Fixed In
https://bugs.kde.org/show_bug.cgi?id=480874
--- Comment #4 from David Jarvie ---
This new crash report does not contain enough information to investigate.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=498753
David Jarvie changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=497742
David Jarvie changed:
What|Removed |Added
Resolution|UPSTREAM|---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=498753
--- Comment #1 from David Jarvie ---
Which version of KAlarm are you running?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=497742
--- Comment #5 from David Jarvie ---
Kalarm version 3.11 (KDE Gear 25.04) will allow the user to select either the
VLC or MPV audio backend (assuming that the distro builds both backends for
KAlarm).
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=497960
David Jarvie changed:
What|Removed |Added
Resolution|--- |FIXED
Version Fixed In
https://bugs.kde.org/show_bug.cgi?id=497742
--- Comment #3 from David Jarvie ---
KAlarm used to use Phonon to play audio, but there were always some crash
reports, which eventually turned out to be due to Phonon not being thread safe.
Canberra was then adopted in KAlarm version 3.8.0 (KDE Gear
https://bugs.kde.org/show_bug.cgi?id=497708
David Jarvie changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=497708
David Jarvie changed:
What|Removed |Added
Component|general |sound
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=497742
David Jarvie changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution
https://bugs.kde.org/show_bug.cgi?id=457176
David Jarvie changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=495664
--- Comment #2 from David Jarvie ---
The config file doesn't exist on the laptop. I did a 'find' for any file whose
name starts with skanlite, in both ~/.local and ~/.config, and no results were
found.
I did find the config file on my d
https://bugs.kde.org/show_bug.cgi?id=495664
Bug ID: 495664
Summary: Skanlite fails with message "opening the selected
scanner failed"
Classification: Applications
Product: Skanlite
Version: 22.12.3
Platform: Debian stab
https://bugs.kde.org/show_bug.cgi?id=493128
David Jarvie changed:
What|Removed |Added
Version Fixed In||24.08.2
Resolution
https://bugs.kde.org/show_bug.cgi?id=489963
--- Comment #6 from David Jarvie ---
Please also attach a copy of your KAlarm configuration file, ~/.config/kalarmrc
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=489963
--- Comment #5 from David Jarvie ---
After unchecking the checkbox 'Start at login' and then quitting KAlarm or
logging out before quitting KAlarm, KAlarm should no longer start at login
UNLESS you start KAlarm again. Every time KAlarm is s
https://bugs.kde.org/show_bug.cgi?id=486187
David Jarvie changed:
What|Removed |Added
Version Fixed In||24.08.2
Resolution
https://bugs.kde.org/show_bug.cgi?id=486187
--- Comment #2 from David Jarvie ---
Looking at this again, I realise that kernel timers are not relevant after all.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=484978
David Jarvie changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=492425
David Jarvie changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=489963
--- Comment #4 from David Jarvie ---
See Bug 492636 for further information.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=492636
David Jarvie changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=489963
--- Comment #3 from David Jarvie ---
*** Bug 492636 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=489963
--- Comment #2 from David Jarvie ---
Is KAlarm listed in the Autostart section in KDE System Settings?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=489961
--- Comment #7 from David Jarvie ---
You are the first user to complain about this in over 20 years, so I'm not
going to change the defaults unless more people complain.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=489213
David Jarvie changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/pim
https://bugs.kde.org/show_bug.cgi?id=489597
David Jarvie changed:
What|Removed |Added
Resolution|--- |FIXED
Version Fixed In
https://bugs.kde.org/show_bug.cgi?id=489899
David Jarvie changed:
What|Removed |Added
Version Fixed In||24.08
Component|general
https://bugs.kde.org/show_bug.cgi?id=484851
David Jarvie changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/pim
https://bugs.kde.org/show_bug.cgi?id=484503
--- Comment #3 from David Jarvie ---
KAlarm has now been converted to use the VLC library to play sound files, which
will fix this bug properly. The fix will be in KAlarm version 3.9, which will
be in the KDE Gear 24.08 release.
Commit
https
https://bugs.kde.org/show_bug.cgi?id=489597
David Jarvie changed:
What|Removed |Added
Component|general |sound
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=489961
David Jarvie changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=489899
--- Comment #6 from David Jarvie ---
To help find the cause for this, can you please do the following:
1) Quit KAlarm (use menu option File -> Quit).
2) Open a terminal window and run KAlarm from there (type "kalarm" and then
Enter).
https://bugs.kde.org/show_bug.cgi?id=489963
David Jarvie changed:
What|Removed |Added
Summary|Start at long turned on |Start at login turned on
https://bugs.kde.org/show_bug.cgi?id=489961
--- Comment #1 from David Jarvie ---
What do you mean by "ringing"?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=489899
--- Comment #3 from David Jarvie ---
Ideally a developer would be able to test with multiple distributions, but time
is limited and keeping more than one development distro up to date would mean
that I wouldn't have time to do actual development
https://bugs.kde.org/show_bug.cgi?id=463388
David Jarvie changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=488738
David Jarvie changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=489597
--- Comment #3 from David Jarvie ---
Canberra has a gstreamer backend, but because Canberra hasn't been updated in
12 years, at least one of the gstreamer calls is obsolete:
gst_element_factory_make("decodebin2", NULL)
GStr
https://bugs.kde.org/show_bug.cgi?id=489899
--- Comment #1 from David Jarvie ---
I tried both a wav and ogg file, with your repeat settings, on my KDE Neon
system, but it worked correctly, with no error message. I tried naming the file
the same as in your screenshot, but it also worked correctly
https://bugs.kde.org/show_bug.cgi?id=489597
David Jarvie changed:
What|Removed |Added
CC||sit...@kde.org
--- Comment #1 from David Jarvie
https://bugs.kde.org/show_bug.cgi?id=484537
David Jarvie changed:
What|Removed |Added
Resolution|--- |UPSTREAM
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=489213
--- Comment #4 from David Jarvie ---
I tested the wav file in both a display alarm and an audio alarm, and it works
on my KDE Neon system in both cases. It also works when I press the "test the
sound" play button.
Random thoughts:
The wav
https://bugs.kde.org/show_bug.cgi?id=489547
David Jarvie changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=489547
--- Comment #1 from David Jarvie ---
I wonder if this problem is a KAlarm bug, or something else. I don't see why
the screen lock status would have any effect on alarms being triggered. To
check this, could you please try two things:
1) Set
https://bugs.kde.org/show_bug.cgi?id=489213
--- Comment #1 from David Jarvie ---
If possible, can you please attach the .wav file so that I can test with it. If
it's too big, a truncated version which also shows the same fault would be
fine.
--
You are receiving this mail because:
Yo
https://bugs.kde.org/show_bug.cgi?id=488738
--- Comment #1 from David Jarvie ---
Unfortunately the crash trace does not contain any references to KAlarm code,
so it is not possible to determine the cause without more information. It looks
as if it crashes while in the initial stages of Qt/KDE
https://bugs.kde.org/show_bug.cgi?id=488488
David Jarvie changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=486187
--- Comment #1 from David Jarvie ---
The RTC wake-up code using kernel timers was contributed by somebody else who I
don't have a contract for, and unfortunately I can't test it on my system.
Running the following command might fix t
https://bugs.kde.org/show_bug.cgi?id=484978
--- Comment #4 from David Jarvie ---
Does it always go wrong?
If the archived alarms file ~/.local/share/kalarm/expired.ics contains the
alarm which triggered at the wrong time, can you please attach it.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=484978
--- Comment #2 from David Jarvie ---
Does this happen for all alarms, or only some?
If only some, does it happen for recurring alarms or single occurrence alarms,
or both?
If it only happens for recurring alarms, does it happen for all types (e.g
https://bugs.kde.org/show_bug.cgi?id=484851
--- Comment #1 from David Jarvie ---
What audio format are the files which you have tested?
Is it the same version of KAlarm in the Manjaro VM?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=484537
--- Comment #3 from David Jarvie ---
I don't mean drag the title bar. On my Neon, I can position the cursor anywhere
in the middle of the window and drag it so that the buttons become visible.
--
You are receiving this mail because:
You are wat
https://bugs.kde.org/show_bug.cgi?id=484537
--- Comment #1 from David Jarvie ---
When I use Wayland on Neon, I can drag the edit alarm window when holding the
left mouse button down. This is the same behaviour as for the konsole "Edit
Current Profile" window which is also too big for t
https://bugs.kde.org/show_bug.cgi?id=484503
David Jarvie changed:
What|Removed |Added
Version Fixed In||24.02.2
Status|ASSIGNED
https://bugs.kde.org/show_bug.cgi?id=484503
David Jarvie changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=469757
David Jarvie changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=463388
--- Comment #3 from David Jarvie ---
When you say that passed alarms are not editable, I assume that you mean
expired alarms (i.e. no longer active). These are stored read-only in the
archived alarms calendar, and are not allowed to be changed. If you
https://bugs.kde.org/show_bug.cgi?id=481334
David Jarvie changed:
What|Removed |Added
CC||x12345678...@outlook.com
--- Comment #11 from
https://bugs.kde.org/show_bug.cgi?id=480789
David Jarvie changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=481334
David Jarvie changed:
What|Removed |Added
CC||pallasw...@proton.me
--- Comment #10 from David
https://bugs.kde.org/show_bug.cgi?id=480874
David Jarvie changed:
What|Removed |Added
Product|Phonon |kalarm
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=452962
David Jarvie changed:
What|Removed |Added
Version|unspecified |3.4.0
Component|general
https://bugs.kde.org/show_bug.cgi?id=417733
David Jarvie changed:
What|Removed |Added
Version Fixed In||24.02.1
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=481334
David Jarvie changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/pim
https://bugs.kde.org/show_bug.cgi?id=481334
--- Comment #7 from David Jarvie ---
As far as I can see, libcanberra can only play from a preset selection of event
sounds, and not what KAlarm requires, which is to be able to play any audio
file which the user selects. The fact that Phonon is not
https://bugs.kde.org/show_bug.cgi?id=481334
David Jarvie changed:
What|Removed |Added
Platform|Debian stable |Neon
CC
https://bugs.kde.org/show_bug.cgi?id=481334
David Jarvie changed:
What|Removed |Added
Component|general |general
CC
https://bugs.kde.org/show_bug.cgi?id=481334
--- Comment #3 from David Jarvie ---
I have now managed to reproduce the crash sometimes.
Have you ever seen it crash when the volume override is NOT set?
I don't know whether KAlarm can be built using QtCreator. The build uses cmake
(not qmake)
https://bugs.kde.org/show_bug.cgi?id=480874
David Jarvie changed:
What|Removed |Added
Assignee|djar...@kde.org |unassigned-b...@kde.org
CC
https://bugs.kde.org/show_bug.cgi?id=480789
--- Comment #1 from David Jarvie ---
It doesn't look similar to bug 468640 (unless you can provide further
information on KAlarm's behaviour to show that it is).
Is an audio alarm playing when it crashes? If so, is that the case every time
https://bugs.kde.org/show_bug.cgi?id=481334
--- Comment #1 from David Jarvie ---
The crash is in the Pulse Audio libraries. When I try it on my Debian Bookworm
system, it doesn't crash.
Does this crash depend on which audio file you select? If so, please attach the
file (or say which s
https://bugs.kde.org/show_bug.cgi?id=481166
David Jarvie changed:
What|Removed |Added
Resolution|--- |INTENTIONAL
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=481166
--- Comment #7 from David Jarvie ---
Many of your proposals go beyond the intended scope of KAlarm, and if
implemented would expand its function from being a stand-alone personal alarm
application to something more general. This would add more code
https://bugs.kde.org/show_bug.cgi?id=481166
--- Comment #5 from David Jarvie ---
Yes, KAlarm is for both technical and non-technical users, but to serve the
latter, it needs a simple interface. More advanced users can expand the range
of displayed options, and use such things as command alarms
https://bugs.kde.org/show_bug.cgi?id=481166
--- Comment #3 from David Jarvie ---
As stated in its handbook, KAlarm is designed as a personal message, email and
command scheduler. It is not designed for group use. It aims to present a
simple interface (unless the user chooses to expand the
https://bugs.kde.org/show_bug.cgi?id=481132
David Jarvie changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=481176
Bug ID: 481176
Summary: KAlarm stable documentation shows old version
Classification: Websites
Product: docs.kde.org
Version: unspecified
Platform: Other
OS: Linux
Sta
https://bugs.kde.org/show_bug.cgi?id=481166
--- Comment #1 from David Jarvie ---
By design, KAlarm stores all its alarms in VEVENT, and in order to provide all
its functionality it uses quite a few custom properties in VEVENT and VALARM.
Giving full support to VTODO would be outside the current
https://bugs.kde.org/show_bug.cgi?id=481053
--- Comment #6 from David Jarvie ---
The KDE 22.12 branch was effectively closed when 23.04 was created, so I
wouldn't be willing to apply the fix to it. I'm afraid the options are to apply
a patch to the OpenSUSE repository or to wait f
https://bugs.kde.org/show_bug.cgi?id=481053
--- Comment #4 from David Jarvie ---
Versions already released by KDE cannot be modified other than by patching the
source and rebuilding yourself (or by persuading OpenSUSE to issue a patched
version, which I assume they are unlikely to do). If you
https://bugs.kde.org/show_bug.cgi?id=481053
David Jarvie changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/pim
https://bugs.kde.org/show_bug.cgi?id=476208
Bug ID: 476208
Summary: ecm_install_icons doesn't work with Breeze
Classification: Frameworks and Libraries
Product: extra-cmake-modules
Version: unspecified
Platform: Neon
OS: Li
https://bugs.kde.org/show_bug.cgi?id=472393
David Jarvie changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=475008
David Jarvie changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=475008
Bug ID: 475008
Summary: KF6TextEditTextToSpeechConfig.cmake is not provided by
any package
Classification: KDE Neon
Product: neon
Version: unspecified
Platform: Neon
https://bugs.kde.org/show_bug.cgi?id=472393
David Jarvie changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=472393
--- Comment #2 from David Jarvie ---
I run Debian stable, so it's likely to be quite some time before I can try
version 23.08 unfortunately.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=472938
--- Comment #5 from David Jarvie ---
I'm afraid that I can't find any clear instructions as to how to install debug
symbols on Debian. I also have only seen the crash once, so it wouldn't
necessarily help in any case.
--
You are rece
1 - 100 of 666 matches
Mail list logo
