[kalarm] [Bug 486187] cant activate rtc wakeup
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 the problem: systemd-run --user --collect --unit kalarm --property=AmbientCapabilities=CAP_WAKE_ALARM -- kalarm You may possibly need to quit KAlarm first and then restart it after running the command (or perhaps it will only work if executed while KAlarm is running). It would be very helpful if you could report whether this does fix the problem, and if so whether KAlarm needs to be running when it is executed. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 484978] alarms triggered at wrong time
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 are watching all bug changes.
[kalarm] [Bug 484978] alarms triggered at wrong time
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. daily, monthly) of recurrence? Are there any other patterns to when it happens? -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 484851] Kalarm fails to play any audio
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.
[kalarm] [Bug 484537] On wayland, Setting display scaling to 150% make KAlarm window getting clipped
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 watching all bug changes.
[kalarm] [Bug 484537] On wayland, Setting display scaling to 150% make KAlarm window getting clipped
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 the display. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 484503] KAlarm play audio feature stopped working
https://bugs.kde.org/show_bug.cgi?id=484503 David Jarvie changed: What|Removed |Added Version Fixed In||24.02.2 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/pim/ ||kalarm/-/commit/768ed33a7e5 ||3e19d192885df985532900d8159 ||09 --- Comment #2 from David Jarvie --- An error message is now displayed when something goes wrong with playing a file. Because user visible (translatable) strings are frozen for KDE Gear 24.02 releases, the message if the audio format is unsupported has had to be set to "file or data corrupt". This message will be improved to mention unsupported format in the KDE Gear 24.05 release, when user visible strings are allowed to be changed. Commit https://invent.kde.org/pim/kalarm/-/commit/768ed33a7e53e19d192885df985532900d815909 in 24.02 branch. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 484503] KAlarm play audio feature stopped working
https://bugs.kde.org/show_bug.cgi?id=484503 David Jarvie changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from David Jarvie --- The opus file format doesn't seem to be supported by the audio library which KAlarm now uses (libcanberra). This library has replaced the use of Phonon by KAlarm because the way that KAlarm needs to use it (multithreaded) made Phonon unreliable and the source of quite a few bugs. There should be an error message when an audio file can't be played - this needs to be added. The only solution for now for playing an opus file is to convert it to another format for KAlarm to use. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 469757] kAlarm does not function if icon not present in system tray
https://bugs.kde.org/show_bug.cgi?id=469757 David Jarvie changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 463388] Alarm windows on startup often produce screen errors like flickering areas
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 try to edit them, the window title bar includes "read only" to indicate this. If you want to create a new alarm from them, use the "Copy alarm" function, which opens the alarm edit dialogue with a copy of the alarm which can be edited. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 481334] KAlarm crashes during notification test when volume override is activated
https://bugs.kde.org/show_bug.cgi?id=481334 David Jarvie changed: What|Removed |Added CC||x12345678...@outlook.com --- Comment #11 from David Jarvie --- *** Bug 480789 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 480789] crash in exit
https://bugs.kde.org/show_bug.cgi?id=480789 David Jarvie changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from David Jarvie --- The crash seems to be in some audio library function. It is likely that this has the same cause as bug 481334. *** This bug has been marked as a duplicate of bug 481334 *** -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 481334] KAlarm crashes during notification test when volume override is activated
https://bugs.kde.org/show_bug.cgi?id=481334 David Jarvie changed: What|Removed |Added CC||pallasw...@proton.me --- Comment #10 from David Jarvie --- *** Bug 480874 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 480874] Kalarm crashed when alarm should have gone off
https://bugs.kde.org/show_bug.cgi?id=480874 David Jarvie changed: What|Removed |Added Product|Phonon |kalarm Status|REPORTED|RESOLVED CC||djar...@kde.org Resolution|--- |DUPLICATE Assignee|unassigned-b...@kde.org |djar...@kde.org Component|general |sound --- Comment #2 from David Jarvie --- *** This bug has been marked as a duplicate of bug 481334 *** -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 452962] KAlarm crashes when stopping a sound alarm test
https://bugs.kde.org/show_bug.cgi?id=452962 David Jarvie changed: What|Removed |Added Version|unspecified |3.4.0 Component|general |sound Status|REPORTED|RESOLVED CC||djar...@kde.org Assignee|unassigned-b...@kde.org |djar...@kde.org Resolution|--- |FIXED Product|Phonon |kalarm Version Fixed In||22.04.1 Latest Commit||https://invent.kde.org/pim/ ||kalarm/commit/30d5a943393d6 ||47bb7471d571d25a326e217ec04 -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 417733] Sound doesn't work in KAlarm
https://bugs.kde.org/show_bug.cgi?id=417733 David Jarvie changed: What|Removed |Added Version Fixed In||24.02.1 Latest Commit||https://invent.kde.org/pim/ ||kalarm/-/commit/dd4bab1a364 ||2c0ec860ffada450d4d41dd8508 ||0f Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #5 from David Jarvie --- Phonon has now been replaced with libcanberra for playing sound files. This should hopefully be more reliable and resolve this issue. This fix will be in KAlarm version 3.7.1, which will be released in KDE Gear 24.02.1 (commit dd4bab1a3642c0ec860ffada450d4d41dd85080f). Unfortunately, because the final Qt5 based KDE Gear release (23.08.5) has now been issued, this fix will not be available for Qt5 based versions of KAlarm. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 481334] KAlarm crashes during notification test when volume override is activated
https://bugs.kde.org/show_bug.cgi?id=481334 David Jarvie changed: What|Removed |Added Latest Commit||https://invent.kde.org/pim/ ||kalarm/-/commit/dd4bab1a364 ||2c0ec860ffada450d4d41dd8508 ||0f Product|Phonon |kalarm Resolution|--- |FIXED Version Fixed In||24.02.1 Assignee|unassigned-b...@kde.org |djar...@kde.org Component|general |sound Status|REPORTED|RESOLVED --- Comment #9 from David Jarvie --- Thank you Harald. Phonon has now been replaced with libcanberra for playing sound files in the thread. This should fix the crash. This fix will be in KAlarm version 3.7.1, which will be released in KDE Gear 24.02.1 (commit dd4bab1a3642c0ec860ffada450d4d41dd85080f). Unfortunately, because the final Qt5 based KDE Gear release (23.08.5) has now been issued, this fix will not be available for Qt5 based versions of KAlarm. -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 481334] KAlarm crashes during notification test when volume override is activated
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 thread safe might explain why there have always been bug reports about KAlarm audio alarms. This needs investigation. -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 481334] KAlarm crashes during notification test when volume override is activated
https://bugs.kde.org/show_bug.cgi?id=481334 David Jarvie changed: What|Removed |Added Platform|Debian stable |Neon CC||djar...@kde.org --- Comment #5 from David Jarvie --- The crashes and error messages which I have reported in comment 4 were all on KDE Neon running a nearly up to date Qt6/KF6 system. The Phonon package versions for Qt6 are: libphonon4qt6-dev4:4.12.0+p22.04+vunstable+git20240123.0113-0 phonon4qt6-backend-vlc 0.12.0+p22.04+vunstable+git20240123.0141-0 qt6-phonon 4:4.12.0+p22.04+vunstable+git20240123.0113-0 qt6-phonon-backend-vlc 0.12.0+p22.04+vunstable+git20240123.0141-0 qt6-phonon-dev 4:4.12.0+p22.04+vunstable+git20240123.0113-0 -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 481334] KAlarm crashes during notification test when volume override is activated
https://bugs.kde.org/show_bug.cgi?id=481334 David Jarvie changed: What|Removed |Added Component|general |general CC||myr...@kde.org, ||romain.per...@gmail.com, ||sit...@kde.org Product|kalarm |Phonon Assignee|djar...@kde.org |unassigned-b...@kde.org --- Comment #4 from David Jarvie --- The crash occurs in Phonon::MediaObject::play(). (This isn't evident from the stack trace, but I've established this using debug statements.) I've seen the same crash (and error message) both when the volume override is used, and when the volume is not set. There have been other crashes in Phonon::MediaObject::play(), which output the following various messages on the terminal. The audio file in every case was the same one (Oxygen-Im-Error-On-Connection.ogg). Assertion 'c->state == PA_CONTEXT_CONNECTING' failed at ../src/pulse/context.c:917, function on_connection(). Aborting. Assertion 'io->ifd >= 0' failed at ../src/pulsecore/iochannel.c:287, function pa_iochannel_creds_supported(). Aborting. ERROR:../src/pulse/glib-mainloop.c:394:glib_defer_enable: assertion failed: (!e->dead) Bail out! ERROR:../src/pulse/glib-mainloop.c:394:glib_defer_enable: assertion failed: (!e->dead) Because all these crashes occur in system libraries, I think the bug must lie in a library, so I'm transferring this bug report to the highest level library involved, i.e. Phonon. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 481334] KAlarm crashes during notification test when volume override is activated
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). One way of building it is using a KDE Neon developer's edition which contains all (or most of) the developer versions of the KDE, Qt and other libraries needed to build KDE applications including KAlarm. In Neon, the KDE package kdesrc-build can be used to do the build. -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 480874] Kalarm crashed when alarm should have gone off
https://bugs.kde.org/show_bug.cgi?id=480874 David Jarvie changed: What|Removed |Added Assignee|djar...@kde.org |unassigned-b...@kde.org CC||myr...@kde.org, ||romain.per...@gmail.com, ||sit...@kde.org Product|kalarm |Phonon Component|general |general --- Comment #1 from David Jarvie --- It looks like it crashed while setting an audio file as the audio source to play for the alarm which was being triggered. The KAlarm code location of the crash is presumably kalarm/src/messagedisplayhelper.cpp line 1039. This appears to be a Phonon bug, so reassigning the bug to Phonon. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 480789] crash in exit
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 it crashes? Does it crash when no audio alarm is playing? -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 481334] KAlarm crashes during notification test when volume override is activated
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 system file it is). Please confirm that you select "New Audio Alarm" to create the alarm. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 481166] When entering VTODOs into KALARM's ICAL calender they are ignored
https://bugs.kde.org/show_bug.cgi?id=481166 David Jarvie changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #9 from David Jarvie --- I'm well aware of the benefits of how UNIX tools can work together to do more complex tasks, which for example allows versatility in scripting. But GUI applications as they currently exist generally don't lend themselves to this, due in part I'm sure to the need for user interaction using a mouse. Certainly, I would classify KAlarm as a non-UNIX type tool since it has been developed with its design tailored to a specific type of use and assumptions, which doesn't make it easy to expand it into a more general tool. Specifically, it is designed to use ICAL in a restricted way, and never with the aim of allowing it to expand to handle the full range of ICAL alarm functionality. It's interesting to have your ideas - thank you. Even if some are out of scope for KAlarm's intended use, others do provide some ideas for future development. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 481166] When entering VTODOs into KALARM's ICAL calender they are ignored
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 complexity, and therefore more maintenance overhead, which I don't think are desirable for the application as it is designed. Specific comments are below. > (My answers rest on https://github.com/KDE/kalarm/tree/master/src I don't know the status of that repository. The correct one is at https://invent.kde.org/pim/kalarm . > The "Related To" property (see > https://www.rfc-editor.org/rfc/rfc5545#section-3.8.4.5). > > KAlarm would then generate a dependent object (child), referencing back to > the parent object in the r/o ICS of the other application. > > With any luck »kcal« already has implemented it, and might even has a > complete view of all calendars within KAlarm, so that it just works … > > In effect the child would have access to changes of the parent, especially > deletion or start/end changes (for relative alarms) and any need to write > anything back into the shared ICS would vanish … I think that for simplicity, I'd prefer to treat read-only calendars as they are currently. They lack functionality in certain respects, but I would regard this as "user beware", since they are not a common usage. > RFC 5545 not only allows but advocates that VEVENT/VTODO can each have > multiple VALARMs with absolute or relative time specifications triggering > at different points in time (and actually each VALARM can have its own > summary and description, which is useful for some use-cases (example see > below)). > > KAlarm should be capable to cope with this and the ICAL library may already > is … The ical library does cope with this. However, KAlarm always creates a separate VEVENT for each alarm, and this is a fundamental assumption in its design. It would add considerable complexity to cater for a read-write calendar containing events with multiple alarms but again because this can only happen with calendars created by other applications, which is not the usual use case, I would be against catering for multiple independent alarms in the same VEVENT. Multiple alarms in a VEVENT or VTODO could be catered for an import function instead, which would split such instances into multiple VEVENTs or VTODOs, so as to conform to what KAlarm is designed to use. If a user tried to configure KAlarm to access a calendar containing such instances, the user could be prompted to import it, with a warning that otherwise, some alarms would be ignored. > I can imagine many use-cases where KAlarm and the other application act as > peers, both writing changes back with collision avoidance done by some > outside mechanism. For KDEPIM applications, that would require reverting to using Akonadi as the backend interface. This is out of the question since the use of Akonadi in KAlarm version 2 resulted in continual difficult to fix bugs, which is why a new direct file interface was developed for KAlarm version 3. > Finally I see some asymmetric use-cases where KAlarm is ancillary as a > reminder manager for a calendaring application. > The calendaring application is the owner/manager of the events and todos – > and the place for editing them. > KAlarm allows fine-tuned managing of the reminders and has r/o access to the > calendar of the other application. > > Technically I hope "Related To" works as solution. > > From the user's point of view: > When a "Related To" alarm is edited, the GUI shows the summary and > description of the event/todo as read-only together with some hint of the > managing application (typically indicated in the ICAL file) and the > external calendar and an indication that the event itself must be managed > there, whereas KAlarm only manages the reminder. The timing, summary > (name), and description (message) of the alarm proper can still be edited > by the user as normal. This is all out of scope, as explained in my first paragraph. The rest of what you suggest is also out of scope. If users want to use KAlarm to manage their alarms in place of their calendaring applications (can't they find calendaring applications which handle alarms?), they will need to import them or set them up manually in KAlarm. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 481166] When entering VTODOs into KALARM's ICAL calender they are ignored
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. Currently, if the user configures KAlarm to access in read-write mode a calendar which has been created by another application, KAlarm will write its own custom properties into the VEVENTs and VALARMs in order, for example, to track when recurrences were last triggered by it. If alarms are subsequently created or edited, they also will contain KAlarm custom properties. If the user also accesses the calendar file from another application such as KOrganizer, the KAlarm specific data may or may not survive, so this could alter how KAlarm functions for these alarms. Having thought about what you've said, I realise that KAlarm could handle alarms within VTODOs similarly to those in VEVENTs, and update them with its own custom properties to keep track. There isn't any need to copy VTODO alarms into VEVENTs - they can just stay in the VTODOs, and KAlarm would simply ignore the todo-specific data. Consideration would need to be given to: 1) How to handle VTODOs with multiple alarms. Currently, KAlarm stores each user-configured alarm in a separate VEVENT (although it often creates multiple VALARM instances within the VEVENT to handle different aspects of what to the user is a single alarm: for example, a display alarm which also plays a sound would contain a VALARM for display and a VALARM for sound, but there are other less obvious reasons to have multiple VALARMs). This scheme would not be able to handle two completely separate alarms in a VTODO (and indeed doesn't handle two completely separate alarms in a VEVENT either). 2) When a VTODO alarm is edited in KAlarm, should it be saved as a replacement VTODO? I presume yes. 3) It isn't just snooze information which currently isn't stored for read-only calendars. Also, data on the last triggered recurrence would be needed in order for read-only alarms to operate in the same way as read-write ones. I suppose that snooze data could perhaps be stored in KAlarm's default calendar, and if when the snooze expired the original read-only alarm or calendar was no longer available, the snooze would be ignored and the snooze data deleted. I'm less sure about keeping recurrence trigger data in the default calendar, since that is much longer lasting, but in principle it could also be done (as long as it is deleted if the read-only alarm or calendar becomes unavailable). 4) I don't understand what you are proposing about D-BUS events/notifications. Do you mean events/notifications not sent to KAlarm? If so, what types? Also, if you're saying that this stuff wouldn't work on KDE, then I don't think it really belongs in a KDE application. You can see descriptions of all the KAlarm custom properties in DESIGN-kalarmcalendar.html in the top level of the KAlarm source directory. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 481166] When entering VTODOs into KALARM's ICAL calender they are ignored
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 options displayed) to allow ordinary (i.e. non-technical) users to schedule alarms. Most users only use it with its default calendars, and not with any calendars created by other applications. The fact that KOrganizer reminders have been messed up in recent times is unfortunate, but I don't want KAlarm to be amended or expanded in any way in order to be used as an adjunct to KOrganizer to provide its reminder functionality. It's up to KOrganizer to sort out its own deficiencies. For these reasons, I don't see it as important to provide KAlarm with the ability to read VTODOs, but I wouldn't object. It would be important to first of all decide on how reading calendars containing VTODOs should fit into KAlarm's user interface. As I said previously, I would see it as being via some sort of import function, but I don't know whether that would satisfy your goal of users not being surprised when VTODOs are ignored if KAlarm is told to use a calendar which it didn't create itself. Bear in mind that if VTODOs were edited in KAlarm, or if they contained recurrences, they would need to be rewritten as VEVENTs (and of course, functions specific to todos would be not show in KAlarm). -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 481132] According documentation »kalarm« allows calendar directories where each event is a single ICS file – in practice it doesn't
https://bugs.kde.org/show_bug.cgi?id=481132 David Jarvie changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/pim/ ||kalarm/-/commit/268ecdf9300 ||a900a6b9cd0908ae670ec342b59 ||e9 Version Fixed In||23.08.5 --- Comment #1 from David Jarvie --- The local directory calendar functionality was removed some time ago in KAlarm version 3.0 (KDE Applications 20.08), when KAlarm ceased to use Akonadi for calendar storage. The description of the local directory calendar has now been removed from the documentation for KDE Gear 23.08.5 (commit 268ecdf9300a900a6b9cd0908ae670ec342b59e9) and 24.02 (commit 936f9adf949e8b273ebaadf4bb1e12ab0f945994). Note that the link to the KAlarm documentation in your bug report actually shows an out of date version of the documentation. The last released revision of the documentation was for KAlarm version 3.6. I've raised a bug report https://bugs.kde.org/show_bug.cgi?id=481176 to get the website updated. -- You are receiving this mail because: You are watching all bug changes.
[docs.kde.org] [Bug 481176] New: KAlarm stable documentation shows old version
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 Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-doc-engl...@kde.org Reporter: djar...@kde.org Target Milestone: --- SUMMARY The stable KAlarm documentation at https://docs.kde.org/stable5/en/kalarm/kalarm/index.html is out of date. It currently shows a version from May 2022 which applied up to KDE Gear 23.04.3, but the document was subsequently updated in the KDE Gear 23.08 release. It has also now had another update for the 23.08.5 release. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 481166] When entering VTODOs into KALARM's ICAL calender they are ignored
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 scope of KAlarm, whose purpose is to provide reminders. Adding todo functionality would almost certainly need significant user interface changes in addition to logic changes. It might be possible to add import (read-only) support for VTODO. This would need to convert them to VEVENT. I don't know how practical this would be, and I don't think the work would be justified unless there was evidence that people would actually use that facility. Of course, if you wanted to implement something yourself along these lines, I'd be happy to consider incorporating that into KAlarm, and could point the way to how to go about it. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 481053] kalarm CLI options wrongly transfered to »--edit-new-display« and actual alarm
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 for 23.08.5. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 481053] kalarm CLI options wrongly transfered to »--edit-new-display« and actual alarm
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 can't patch and build yourself, you'll have to wait for KDE Gear release 23.08.5 (based on Qt5, due on 15 February) or 24.02 (based on Qt6, due on 28 February), although I don't know when or if OpenSUSE will issue these releases. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 481053] kalarm CLI options wrongly transfered to »--edit-new-display« and actual alarm
https://bugs.kde.org/show_bug.cgi?id=481053 David Jarvie changed: What|Removed |Added Latest Commit||https://invent.kde.org/pim/ ||kalarm/-/commit/f701adfeb00 ||eff4dd234e81a937381359d407c ||c5 Status|REPORTED|RESOLVED Resolution|--- |FIXED Version Fixed In||24.02 --- Comment #2 from David Jarvie --- Now fixed for KAlarm version 3.6.4 in KDE Gear 23.08.5 (commit a05422923b625f9cf5f1d6f167e6a6d0b3e60b7f) and KAlarm version 3.7.0 in KDE Gear 24.02 (commit f3dd19a8e2b900a36ca2433e59f6ae9c93ae42da). Thanks for reporting this. There was a slip-up when originally implementing the --name option. -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 476208] New: ecm_install_icons doesn't work with Breeze
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: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: ecm-bugs-n...@kde.org
Reporter: djar...@kde.org
Target Milestone: ---
ecm_install_icons cmake command installs Breeze icons in the wrong locations.
Breeze uses a different directory structure from other icon themes, so for
ecm_install_icons to work with Breeze, it would have to detect that the icon
theme is Breeze and modify its behaviour accordingly. I don't know whether it
is reasonable to expect ECM to do this, or whether it is really a Breeze issue,
but the result is faulty installation.
The only solution that I'm aware of is to make CMakeLists.txt install the
Breeze icons at hard-coded locations.
For example, Breeze expects 22x22 action icons to be installed at:
${KDE_INSTALL_ICONDIR}/breeze/actions/22/
whereas other icon themes (e.g. oxygen) use:
${KDE_INSTALL_ICONDIR}/oxygen/22x22/actions/
This fault occurs for both KF5 and KF6:
SOFTWARE/OS VERSIONS
KDE Frameworks Version: 5.240.0 / 5.103.0
Qt Version: 6.6.0 / 5.15.8
--
You are receiving this mail because:
You are watching all bug changes.
[Skanlite] [Bug 472393] Scanner fails to open
https://bugs.kde.org/show_bug.cgi?id=472393 David Jarvie changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #5 from David Jarvie --- It now seems to work on the first attempt. Skanlite hasn't been updated on my system since my original report, so maybe something else changed which has fixed things? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 475008] KF6TextEditTextToSpeechConfig.cmake is not provided by any package
https://bugs.kde.org/show_bug.cgi?id=475008 David Jarvie changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from David Jarvie --- It turns out that the missing file is in the package kf6-ktextaddons-dev. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 475008] New: KF6TextEditTextToSpeechConfig.cmake is not provided by any package
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 OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages Unstable Edition Assignee: neon-b...@kde.org Reporter: djar...@kde.org CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- The package kpim6-kpimtextedit-dev contains KPim6TextEditConfig.cmake, which requires KF6TextEditTextToSpeechConfig.cmake as a dependency when building software. The latter file doesn't seem to be provided by any package - the only candidate I can find would be libkf6pimtextedittexttospeech-dev, but there is no package called kpim6-kpimtextedittexttospeech-dev which seems to be the package name which would normally be expected to provide the file. Should the packages kpim6-kpimtextedittexttospeech and kpim6-kpimtextedittexttospeech-dev be added to Neon? Output from cmake is: CMake Error at /usr/share/cmake-3.27/Modules/CMakeFindDependencyMacro.cmake:76 (find_package): By not providing FindKF6TextEditTextToSpeech.cmake in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by KF6TextEditTextToSpeech, but CMake did not find one. Could not find a package configuration file provided by KF6TextEditTextToSpeech (requested version 1.5.2) with any of the following names: KF6TextEditTextToSpeechConfig.cmake kf6textedittexttospeech-config.cmake Add the installation prefix of KF6TextEditTextToSpeech to CMAKE_PREFIX_PATH or set KF6TextEditTextToSpeech_DIR to a directory containing one of the above files. If KF6TextEditTextToSpeech provides a separate development package or SDK, be sure it has been installed. Call Stack (most recent call first): /usr/lib/x86_64-linux-gnu/cmake/KPim6TextEdit/KPim6TextEditConfig.cmake:42 (find_dependency) /usr/share/cmake-3.27/Modules/CMakeFindDependencyMacro.cmake:76 (find_package) /usr/lib/x86_64-linux-gnu/cmake/KPim6IdentityManagementWidgets/KPim6IdentityManagementWidgetsConfig.cmake:41 (find_dependency) SOFTWARE/OS VERSIONS Neon KDE Frameworks package Version: 23.08.1+p22.04+vunstable+git20230927.0228-0 -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 472393] Scanner fails to open
https://bugs.kde.org/show_bug.cgi?id=472393 David Jarvie changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from David Jarvie --- I've discovered that Skanlite only fails to find my printer on its first run after rebooting (I don't know if logging out and back in would have the same result). On subsequent invocations, it finds the printer OK. However, in the message box which is displayed on the first run which says that no devices have been discovered, if I click on the button to scan for devices again, it still fails to find anything. It's only when I close Skanlite and start it again that it finds the device. -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 472393] Scanner fails to open
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.
[kwin] [Bug 472938] Crash in KWin::X11Window::buttonPressEvent() when accessing the window menu / trying to move to another virtual desktop
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 receiving this mail because: You are watching all bug changes.
[phonon-backend-vlc] [Bug 474091] KAlarm crashes when a repeated alarm runs for a long time and other alarms are queued up behind it
https://bugs.kde.org/show_bug.cgi?id=474091 David Jarvie changed: What|Removed |Added Product|kalarm |phonon-backend-vlc Version|unspecified |0.11.3 Assignee|djar...@kde.org |unassigned-b...@kde.org Component|general |general CC||bcooks...@kde.org, ||f...@kde.org, ||j...@videolan.org, ||myr...@kde.org, ||sit...@kde.org --- Comment #3 from David Jarvie --- When testing, I've seen similar crashes after playing the sound file 10 or 20 times, and I even had it crash once the first time it tried to play the sound file. I'm also using VLC, but under X11, not Wayland. It used to work, so I think the bug must lie either in Phonon or somewhere in the VLC library or pulse audio, so I'm reassigning the bug to Phonon. Crash trace when it crashed before playing the sound file even once: KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kalarm path = /home/david/kde/usr/bin pid = 35904 KCrash: Arguments: /home/david/kde/usr/bin/kalarm ==35904== ==35904== Process terminating with default action of signal 11 (SIGSEGV) ==35904==at 0x6F76A7C: __pthread_kill_implementation (pthread_kill.c:44) ==35904==by 0x6F76A7C: __pthread_kill_internal (pthread_kill.c:78) ==35904==by 0x6F76A7C: pthread_kill@@GLIBC_2.34 (pthread_kill.c:89) ==35904==by 0x6F22475: raise (raise.c:26) ==35904==by 0x51E40CC: KCrash::defaultCrashHandler(int) (in /usr/lib/x86_64-linux-gnu/libKF5Crash.so.5.109.0) ==35904==by 0x6F2251F: ??? (in /usr/lib/x86_64-linux-gnu/libc.so.6) ==35904==by 0x890AD5E: ??? (in /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-15.99.so) ==35904==by 0x89155DB: pa_iochannel_read_with_ancil_data (in /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-15.99.so) ==35904==by 0x892A360: ??? (in /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-15.99.so) ==35904==by 0x892B28E: ??? (in /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-15.99.so) ==35904==by 0x7475915: ??? (in /usr/lib/x86_64-linux-gnu/libpulse-mainloop-glib.so.0.0.6) ==35904==by 0x86CED3A: g_main_context_dispatch (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7200.4) ==35904==by 0x8724257: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7200.4) ==35904==by 0x86CC3E2: g_main_context_iteration (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7200.4) ==35904==by 0x6A64287: QEventDispatcherGlib::processEvents(QFlags) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.15.10) ==35904==by 0x6A0972A: QEventLoop::exec(QFlags) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.15.10) ==35904==by 0x6A11CC3: QCoreApplication::exec() (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.15.10) ==35904==by 0x190F5F: main (main.cpp:75) ==35904== Segmentation fault (core dumped) -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 474091] KAlarm crashes when a repeated alarm runs for a long time and other alarms are queued up behind it
https://bugs.kde.org/show_bug.cgi?id=474091 David Jarvie changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 474091] KAlarm crashes when a repeated alarm runs for a long time and other alarms are queued up behind it
https://bugs.kde.org/show_bug.cgi?id=474091 --- Comment #1 from David Jarvie --- Can you confirm that when you say an "alarm running on repeat", you mean on audio repeat (not a recurrence sub-repetition). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446874] Crash in QSGOpaqueTextureMaterialShader::updateState()
https://bugs.kde.org/show_bug.cgi?id=446874 --- Comment #53 from David Jarvie --- I have submitted a Debian bug report requesting a backport fix: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050723 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472543] Crash when closing a window
https://bugs.kde.org/show_bug.cgi?id=472543 --- Comment #5 from David Jarvie --- Reported to Debian at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050723 -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 473792] Unnecessary warning about lack of high-accuracy timing (for alarm times far into the future)
https://bugs.kde.org/show_bug.cgi?id=473792 David Jarvie changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Version Fixed In||23.08.1 Latest Commit||https://invent.kde.org/pim/ ||kalarm/-/commit/65031e6e03c ||802a9e3669ee34c95e6d919cfff ||8e --- Comment #1 from David Jarvie --- You're correct in thinking that no warning should be shown for alarms >10 minutes ahead. That was the intention, but it was coded wrongly. Fixed now for version 3.6.1 in KDE Gear 23.08.1, commit 65031e6e03c802a9e3669ee34c95e6d919cfff8e. Thank you for reporting this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472938] Crash in KWin::X11Window::buttonPressEvent() when accessing the window menu / trying to move to another virtual desktop
https://bugs.kde.org/show_bug.cgi?id=472938 David Jarvie changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from David Jarvie --- Unfortunately by the time I'd gone through all the crash reporting process, I couldn't remember exactly what I'd done apart from clicking the window menu button. So although it seems unlikely that I'd have clicked a tooltip, I can't be certain. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472938] New: Crash when accessing the window menu / trying to move to another virtual desktop
https://bugs.kde.org/show_bug.cgi?id=472938 Bug ID: 472938 Summary: Crash when accessing the window menu / trying to move to another virtual desktop Classification: Plasma Product: kwin Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: djar...@kde.org Target Milestone: --- SUMMARY I clicked the window menu button, and was trying to move the window to another virtual desktop. I can't remember at which stage it crashed (after the initial click, or after selecting a virtual desktop). SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian 12 KDE Plasma Version: kwin-x11 version 5.27.5-3 KDE Frameworks Version: 22.12.3 Qt Version: 5.15.8 ADDITIONAL INFORMATION Application: KWin (kwin_x11), signal: Segmentation fault PID: 3402 (kwin_x11) UID: 1000 (david) GID: 1000 (david) Signal: 11 (SEGV) Timestamp: Wed 2023-08-02 22:17:49 BST (47s ago) Command Line: /usr/bin/kwin_x11 --replace Executable: /usr/bin/kwin_x11 Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_x11.service Unit: user@1000.service User Unit: plasma-kwin_x11.service Slice: user-1000.slice Owner UID: 1000 (david) Boot ID: 67317cca0c90407b8b7431afba2c966e Machine ID: 9f4447b33097490eaac20e4b4d721a04 Hostname: stewjar Storage: /var/lib/systemd/coredump/core.kwin_x11.1000.67317cca0c90407b8b7431afba2c966e.3402.169101106900.zst (present) Size on Disk: 7.9M Message: Process 3402 (kwin_x11) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.12-1~deb12u1.amd64 Module libudev.so.1 from deb systemd-252.12-1~deb12u1.amd64 Stack trace of thread 3402: #0 0x7f5bfa8aec24 __GI___pthread_sigmask (libc.so.6 + 0x8fc24) #1 0x7f5bfa85b1b9 __GI___sigprocmask (libc.so.6 + 0x3c1b9) #2 0x7f5bfdbfbe9b _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 0x4e9b) #3 0x7f5bfdbfcb3e _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b3e) #4 0x7f5bfa85afd0 __restore_rt (libc.so.6 + 0x3bfd0) #5 0x7f5bfbd412b0 _ZNK7QWindow6parentEv (libQt5Gui.so.5 + 0x1412b0) #6 0x7f5bfbd2a561 _ZNK15QPlatformWindow6parentEv (libQt5Gui.so.5 + 0x12a561) #7 0x7f5bf60eab6a _ZN10QXcbWindow4hideEv (libQt5XcbQpa.so.5 + 0x5cb6a) #8 0x7f5bfbd47e9f _ZN14QWindowPrivate10setVisibleEb (libQt5Gui.so.5 + 0x147e9f) #9 0x7f5bfaf9feb8 _ZN14QWidgetPrivate11hide_helperEv (libQt5Widgets.so.5 + 0x19feb8) #10 0x7f5bfafa4b28 _ZN14QWidgetPrivate10setVisibleEb (libQt5Widgets.so.5 + 0x1a4b28) #11 0x7f5bfafa0438 _ZN14QWidgetPrivate12close_helperENS_9CloseModeE (libQt5Widgets.so.5 + 0x1a0438) #12 0x7f5bfafcb7fd n/a (libQt5Widgets.so.5 + 0x1cb7fd) #13 0x7f5bfb8b135e _ZN23QCoreApplicationPrivate34sendThroughApplicationEventFiltersEP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b135e) #14 0x7f5bfaf62fe8 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162fe8) #15 0x7f5bfb8b16f8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b16f8) #16 0x7f5bfd62ee83 _ZN4KWin9X11Window16buttonPressEventEjiij (libkwin.so.5 + 0x22ee83) #17 0x7f5bfd62f3fa _ZN4KWin9X11Window11windowEventEP19xcb_generic_event_t (libkwin.so.5 + 0x22f3fa) #18 0x7f5bfd62f782 _ZN4KWin9Workspace14workspaceEventEP19xcb_generic_event_t (libkwin.so.5 + 0x22f782) #19 0x7f5bfb8aec7f _ZN24QAbstractEventDispatcher17filterNativeEventERK10QByteArrayPvPl (libQt5Core.so.5 + 0x2aec7f) #20 0x7f5bf60d440f _ZN14QXcbConnection14handleXcbEventEP19xcb_generic_event_t (libQt5XcbQpa.so.5 + 0x4640f) #21 0x7f5bf60d5ab6 _ZN14QXcbConnection16processXcbEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5XcbQpa.so.5 + 0x47ab6) #22 0x7f5bf60fbec3 n/a (libQt5XcbQpa.so.5 + 0x6dec3) #23 0x7f5bf95d47a9 g_main_context_dispatch (libglib-2.0.so.0 + 0x547a9) #24 0x7f5bf95d4a38 n/a (libglib-2.0.so.0 + 0x54a38) #25 0x7f5bf95d4acc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc) #26 0x7f5bfb909836 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x309836) #27 0x7f5bfb8b017b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE
[neon] [Bug 472838] New: libkf5pimtextedittexttospeech-dev package doesn't contain a cmake config file
https://bugs.kde.org/show_bug.cgi?id=472838 Bug ID: 472838 Summary: libkf5pimtextedittexttospeech-dev package doesn't contain a cmake config file Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages Unstable Edition Assignee: neon-b...@kde.org Reporter: djar...@kde.org CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- The package libkf5pimtextedittexttospeech-dev doesn't contain KF5TextEditTextToSpeechConfig.cmake (or any other .cmake file). I'm trying to build an app with kdesrc-build which requires this, so the build fails. libkf5textedittexttospeech is required by libkf5pimtextedit5. The only -dev package for *textedittexttospeech is libkf5pimtextedittexttospeech-dev, so logically it needs to contain the missing .cmake file. SOFTWARE/OS VERSIONS Up to date (today) Neon unstable. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472543] New: Crash when closing a window
https://bugs.kde.org/show_bug.cgi?id=472543 Bug ID: 472543 Summary: Crash when closing a window Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: djar...@kde.org Target Milestone: 1.0 SUMMARY The screen went black when I closed a window, after which plasma restarted. Application: Plasma (plasmashell), signal: Segmentation fault PID: 3068 (plasmashell) UID: 1000 (david) GID: 1000 (david) Signal: 11 (SEGV) Timestamp: Sun 2023-07-23 19:40:01 BST (10s ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (david) Boot ID: f06577e8ff68477684e14634690517d7 Machine ID: 9f4447b33097490eaac20e4b4d721a04 Hostname: stewjar Storage: /var/lib/systemd/coredump/core.plasmashell.1000.f06577e8ff68477684e14634690517d7.3068.169013760100.zst (present) Size on Disk: 18.5M Message: Process 3068 (plasmashell) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.12-1~deb12u1.amd64 Module libudev.so.1 from deb systemd-252.12-1~deb12u1.amd64 Stack trace of thread 3068: #0 0x7f531caa9d3c __pthread_kill_implementation (libc.so.6 + 0x8ad3c) #1 0x7f531ca5af32 __GI_raise (libc.so.6 + 0x3bf32) #2 0x7f531f0ceb46 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b46) #3 0x7f531ca5afd0 __restore_rt (libc.so.6 + 0x3bfd0) #4 0x7f531caa9d3c __pthread_kill_implementation (libc.so.6 + 0x8ad3c) #5 0x7f531ca5af32 __GI_raise (libc.so.6 + 0x3bf32) #6 0x7f531ca5afd0 __restore_rt (libc.so.6 + 0x3bfd0) #7 0x7f531cb20539 syscall (libc.so.6 + 0x101539) #8 0x7f531cccdd9b _ZN10QSemaphore7acquireEi (libQt5Core.so.5 + 0xcdd9b) #9 0x7f531cee8e99 n/a (libQt5Core.so.5 + 0x2e8e99) #10 0x7f531cee229f _ZN7QObject9destroyedEPS_ (libQt5Core.so.5 + 0x2e229f) #11 0x7f531cee7254 _ZN7QObjectD2Ev (libQt5Core.so.5 + 0x2e7254) #12 0x7f531dac2c99 _ZN19QDBusServiceWatcherD0Ev (libQt5DBus.so.5 + 0x70c99) #13 0x7f531cedb28e _ZN14QObjectPrivate14deleteChildrenEv (libQt5Core.so.5 + 0x2db28e) #14 0x7f531cee7054 _ZN7QObjectD2Ev (libQt5Core.so.5 + 0x2e7054) #15 0x7f530ff0ab13 n/a (org.kde.plasma.private.systemtray.so + 0x41b13) #16 0x7f531cedb28e _ZN14QObjectPrivate14deleteChildrenEv (libQt5Core.so.5 + 0x2db28e) #17 0x7f531cee7054 _ZN7QObjectD2Ev (libQt5Core.so.5 + 0x2e7054) #18 0x7f530fef3fb3 n/a (org.kde.plasma.private.systemtray.so + 0x2afb3) #19 0x7f531cedb28e _ZN14QObjectPrivate14deleteChildrenEv (libQt5Core.so.5 + 0x2db28e) #20 0x7f531cee7054 _ZN7QObjectD2Ev (libQt5Core.so.5 + 0x2e7054) #21 0x7f530fef0629 n/a (org.kde.plasma.private.systemtray.so + 0x27629) #22 0x7f531cedb28e _ZN14QObjectPrivate14deleteChildrenEv (libQt5Core.so.5 + 0x2db28e) #23 0x7f531cee7054 _ZN7QObjectD2Ev (libQt5Core.so.5 + 0x2e7054) #24 0x7f530feebd79 n/a (org.kde.plasma.private.systemtray.so + 0x22d79) #25 0x7f531ca5d4dd __run_exit_handlers (libc.so.6 + 0x3e4dd) #26 0x7f531ca5d61a __GI_exit (libc.so.6 + 0x3e61a) #27 0x7f531bdff7af _XDefaultIOError (libX11.so.6 + 0x467af) #28 0x7f531bdffa9f _XIOError (libX11.so.6 + 0x46a9f) #29 0x7f531bdfdd60 n/a (libX11.so.6 + 0x44d60) #30 0x7f531bdeb38f XNextRequest (libX11.so.6 + 0x3238f) #31 0x7f53142d8eb6 n/a (KF5WindowSystemX11Plugin.so + 0x16eb6) #32 0x7f53142d14ef n/a (KF5WindowSystemX11Plugin.so + 0xf4ef) #33 0x7f53142d9981 n/a (KF5WindowSystemX11Plugin.so + 0x17981) #34 0x7f531e932700 n/a (libKF5WindowSystem.so.5 + 0x2b700) #35 0x7f531e92e090 _ZN11KWindowInfoC1Ey6QFlagsIN3NET8PropertyEES0_INS1_9Property2EE (libKF5WindowSystem.so.5 + 0x27090) #36 0x7f530ffdc766 n/a (libtaskmanager.so.6abi1 + 0x6f766) #37 0x7f530ffe0e68 _ZNK11TaskManager17XWindowTasksModel4dataERK11QModelIndexi
[Skanlite] [Bug 472393] New: Scanner fails to open
https://bugs.kde.org/show_bug.cgi?id=472393 Bug ID: 472393 Summary: Scanner fails to open Classification: Applications Product: Skanlite Version: 22.12.3 Platform: Debian stable OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kare.s...@iki.fi Reporter: djar...@kde.org Target Milestone: --- SUMMARY I have a Samsung Xpress M2885FW printer, but when I run Skanlite, it always displays the error message "Opening the selected scanner failed". However, xsane finds it and successfully scans. Before Skanlite displays the error message, it very briefly shows some other error message, but it disappears too quickly to be readable. Running Skanlite from the command line doesn't show any error message either. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian 12 (bookworm) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 libsane1 version: 1.2.1 -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 470477] Cannot create alarms
https://bugs.kde.org/show_bug.cgi?id=470477 --- Comment #9 from David Jarvie --- There don't seem to be any backports for Debian 10, so you would need to update your system to Debian 11 or 12. Alternatively, it is possible to build KAlarm from source using the kdesrc-build package, but I wouldn't recommend that unless you already have some knowledge or experience of building software from source. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 470477] Cannot create alarms
https://bugs.kde.org/show_bug.cgi?id=470477 David Jarvie changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #7 from David Jarvie --- Marking as fixed because this issue has been fixed in KAlarm version 3 and later, due to Akonadi no longer being used. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 463388] Alarm windows on startup often produce screen errors like flickering areas
https://bugs.kde.org/show_bug.cgi?id=463388 --- Comment #1 from David Jarvie --- Which desktop environment are you using (eg. KDE Plasma / Gnome / XFCE), and which version? Screen errors after KAlarm windows are closed are almost certainly due to the window manager - KAlarm (or any other application) has no control over what happens once its windows are closed. I'm not sure about why buttons sometimes cannot be clicked. This might also be due to some window manager issue. When the Edit button is clicked, does anything happen (if so, what), or is the Edit button simply not clickable? -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 470451] 3 feature requests for KAlarm: "today selector", "see past alarms", "defer presets"
https://bugs.kde.org/show_bug.cgi?id=470451 David Jarvie changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/pim/ ||kalarm/-/commit/18a71dbe37c ||631ad4a820af87766b5e5dbdceb ||9d --- Comment #3 from David Jarvie --- Your first and third requests, for a control for "today" in the date picker, and a dropdown containing presets for delay interval in the Defer dialogue, have now been implemented, and will be in KAlarm version 3.6, in KDE Apps 20.08. Commits ef7c3e328a7f42f00acd94b75b51ad9d503e6a8e and 18a71dbe37c631ad4a820af87766b5e5dbdceb9d. Showing past alarms in the date picker would require significant work, since although KAlarm does archive past alarms, it doesn't access them once stored. The amount of work required to enable this to happen is too great, so I'm afraid that I'll have to rule this out. If you wanted to implement this yourself, of course, feel free! -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 468640] KAlarm crashes after being up for a while, seems to suffer heavy lag a lot of the time
https://bugs.kde.org/show_bug.cgi?id=468640 David Jarvie changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Version Fixed In||23.04.3 Latest Commit||https://invent.kde.org/pim/ ||kalarm/-/commit/ef7c3e328a7 ||f42f00acd94b75b51ad9d503e6a ||8e --- Comment #7 from David Jarvie --- I've now implemented a workaround to fix the bug, which will clear the memory leak whenever all alarm windows are closed. Note that if you always keep at least one alarm displayed, this fix will not work. The proper fix would be in KCalendarCore library, as explained in comment 6, but that has not yet been approved. As also stated, the future Qt6 based version will not have this bug. The workaround will be in KAlarm version 3.5.6 in KDE Apps 23.04.3, and is implemented by commit ef7c3e328a7f42f00acd94b75b51ad9d503e6a8e. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 469757] kAlarm does not function if icon not present in system tray
https://bugs.kde.org/show_bug.cgi?id=469757 --- Comment #3 from David Jarvie --- On my system, KAlarm quits when the main window is closed in these circumstances (as it is supposed to do). Strange... KAlarm is not designed to run as a daemon, so when the application is closed, there is no background task to trigger alarms. If that is what you require, you will need to look for an alternative to KAlarm. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 470477] Cannot create alarms
https://bugs.kde.org/show_bug.cgi?id=470477 --- Comment #6 from David Jarvie --- This problem is clearly due to Akonadi. It is because of its unreliability that KAlarm (since version 3, released in 2020 in KDE Apps 20.08) no longer uses Akonadi. Upgrading would be the most reliable way to fix the issue. In the meantime, I suggest trying the following. In each case, quit KAlarm first before running the fix. In a terminal window, run the commands akonadictl vacuum akonadictl fsck If that doesn't fix things, run the commands akonadictl stop rm ~/.config/akonadi_*kalarm*rc rm ~/.config/akonadi/*_kalarm* If that still doesn't fix things, all I can think of is to completely wipe Akonadi's configuration. WARNING: this should only be done if you don't use any other KDE PIM applications which use Akonadi, such as KMail, KOrganizer, KNotes (and possibly others), since those applications could lose data. It would be wise to back up all files and directories before deleting them, so that you can reinstate them afterwards if things go wrong. To wipe the Akonadi configuration, akonadictl stop rm -rf ~/.config/akonadi* rm -rf ~/.local/share/akonadi* -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 470451] 3 feature requests for KAlarm: "today selector", "see past alarms", "defer presets"
https://bugs.kde.org/show_bug.cgi?id=470451 --- Comment #1 from David Jarvie --- Thanks for your suggestions. 1) Do you have any suggestions as to what form the "today" control could take, and where it should be positioned? 2) This would need some thought as to how desirable (i.e. to avoid confusion) or practical it is. 3) I think that choosing a few more or less arbitrary values for a preset list would be likely to only work for some users, and make others feel frustrated, so any preset list would need to be configurable by the user. While possible, it could take a significant amount of work to implement. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 469757] kAlarm does not function if icon not present in system tray
https://bugs.kde.org/show_bug.cgi?id=469757 --- Comment #1 from David Jarvie --- Is KAlarm still running after removing it from the system tray? Bear in mind that if "Show in system tray" is selected, closing the main window will leave KAlarm running (in the system tray), but if "Show in system tray" is NOT selected, closing the main window will cause KAlarm to quit. So to keep using it while not showing it in the system tray, you have to leave it running in the same way as other applications, so if you're using a task manager in the panel, it will show there. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 470477] Cannot create alarms
https://bugs.kde.org/show_bug.cgi?id=470477 --- Comment #3 from David Jarvie --- A possible fix is to right click on the alarm calendar in the calendar view panel, and ensure that "Use as default for active alarms" is selected. However, if the calendar is already selected as default, or if it still doesn't work after doing that, I suggest deleting and re-adding the alarm calendar as follows: 1) Select the active alarm calendar in the calendar view panel, and click Show Details. Note the File location. 2) Remove it from KAlarm's database by clicking Remove. (Note that this doesn't delete your actual alarm calendar file.) 3) Add the calendar again by clicking Add. In the dialog, enter the file location noted in step 1, select Active Alarms, enter "Active Alarms" as the name, and do not select read only. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 470477] Cannot create alarms
https://bugs.kde.org/show_bug.cgi?id=470477 --- Comment #1 from David Jarvie --- In the calendar view (menu View -> Show Calendars), are any Active Alarms calendars shown? If so, right click on the calendar and select Show Details. Please report its Permissions, Status and Default calendar setting. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 468640] KAlarm crashes after being up for a while, seems to suffer heavy lag a lot of the time
https://bugs.kde.org/show_bug.cgi?id=468640 --- Comment #6 from David Jarvie --- It turns out that every time an alarm is displayed, a copy of the alarm is stored by the KCalendarCore library from KDE Frameworks. The library currently does not provide any way of disabling this unwanted behaviour. I have raised a merge request for a change which would allow this to be disabled. Until that change is approved, the only way to avoid this bug is to quit KAlarm from time to time, and restart it. To quit KAlarm, you need to use the File -> Quit menu option when there are no alarm windows displayed. Alternatively, you can open a terminal window and enter the command 'killall kalarm' (without the quotes), and the alarm windows will be redisplayed when you restart it. The problem feature in KCalendarCore will be removed when KDE migrates to Qt6, so this bug should be resolved then in any case. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 468640] KAlarm crashes after being up for a while, seems to suffer heavy lag a lot of the time
https://bugs.kde.org/show_bug.cgi?id=468640 David Jarvie changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #4 from David Jarvie --- I can see that there is a small memory leak when alarms trigger. This will not matter initially, but after a large number of alarms, it could start to slow KAlarm and eventually cause it to crash. The leak is in memory allocated by setCustomProperties(), and needs further investigation to find out why. Hopefully this will be fixed for the next release. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 468640] KAlarm crashes after being up for a while, seems to suffer heavy lag a lot of the time
https://bugs.kde.org/show_bug.cgi?id=468640 --- Comment #2 from David Jarvie --- That crash occurs in the Pulse Audio library, which doesn't give any clue as to what's going wrong in KAlarm. Can you provide any other crash traces from when no alarm is underway? -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 463388] Alarm windows on startup often produce screen errors like flickering areas
https://bugs.kde.org/show_bug.cgi?id=463388 David Jarvie changed: What|Removed |Added Component|Akonadi |general -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 405323] Suggestion & question: Backups
https://bugs.kde.org/show_bug.cgi?id=405323 David Jarvie changed: What|Removed |Added Component|kalarmd |general -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 405313] kalarm freezes in gnome
https://bugs.kde.org/show_bug.cgi?id=405313 David Jarvie changed: What|Removed |Added Component|kalarmd |Akonadi -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 297214] okteta "hangs" at start doing timezone related operations over and over
https://bugs.kde.org/show_bug.cgi?id=297214 --- Comment #12 from David Jarvie --- As far as I can see, since the time this bug was reported okteta has had no direct calls to KDateTime or KTimeZone, and the dependency on these classes was via KDirModel in kio. On the assumption that frameworks/kio no longer links to kdelibs4support, okteta will no longer use KDateTime directly or indirectly, so this bug will not occur any more. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 424204] Feature request: Send sound output to device other than default
https://bugs.kde.org/show_bug.cgi?id=424204 --- Comment #3 from David Jarvie --- Keeping a note here to help in coding this feature in future: A list of audio devices is given by Phonon::BackendCapabilities::availableAudioOutputDevices(). I've still to find out how KAlarm could be added to System Settings sound configuration. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 463278] "Time from now" alarms are unexpectedly imprecise
https://bugs.kde.org/show_bug.cgi?id=463278 David Jarvie changed: What|Removed |Added Latest Commit||https://invent.kde.org/pim/ ||kalarm/-/commit/e89af958226 ||1714442766b3390e3d60f81b601 ||57 Version Fixed In||23.04 Resolution|INTENTIONAL |FIXED --- Comment #7 from David Jarvie --- A warning will now be shown if a time-from-now value of less than 10 minutes is specified. This will be in KAlarm version 3.5.5 in KDE Gear 23.04. Commit e89af9582261714442766b3390e3d60f81b60157. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 463310] Attempting to change fields by hitting tab does not work when entering alarm time
https://bugs.kde.org/show_bug.cgi?id=463310 David Jarvie changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/pim/ ||kalarm/-/commit/dd73bd6c3b6 ||ee77f3c40ca057bf52ebada39a0 ||38 Version Fixed In||22.12.1 --- Comment #1 from David Jarvie --- This is now fixed by commit dd73bd6c3b6ee77f3c40ca057bf52ebada39a038, and will be in KAlarm version 3.5.4 in KDE Gear 22.12.1. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 463278] "Time from now" alarms are unexpectedly imprecise
https://bugs.kde.org/show_bug.cgi?id=463278 --- Comment #5 from David Jarvie --- It would require a significant redesign to trigger alarms at times other than on a minute boundary. Given that this would be very much a minority requirement, the most that I could contemplate doing would be to add a warning when a short time from now interval was selected. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 463278] "Time from now" alarms are unexpectedly imprecise
https://bugs.kde.org/show_bug.cgi?id=463278 --- Comment #3 from David Jarvie --- KAlarm was never intended as a high accuracy timer, but rather as an application to help people organise their lives and remember to do things. I can see that if you expect it to act as a stopwatch you will get a surprise, but the fact that if you set a specific time for an alarm (as opposed to time from now) you can only enter a minutes value and not seconds gives a hint as to its accuracy limitations. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 463284] Sharing remote caldav between several kalarm instances
https://bugs.kde.org/show_bug.cgi?id=463284 David Jarvie changed: What|Removed |Added Severity|normal |wishlist Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #1 from David Jarvie --- KAlarm accesses remote calendars only using remote file access protocols, and it doesn't implement other protocols. Because it is primarily a personal reminder application, as opposed to a group one, other remote protocols seem unlikely to be required by many users. KAlarm used to use Akonadi, the KDE PIM data interface, to access calendar data, and this could potentially have been used for caldav access, but it caused so many bugs that it was eventually abandoned in favour of simple file access. This has had the extra benefit of keeping things simpler. So unfortunately for you, it is unlikely that remote protocols such as caldav will be implemented. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 463278] "Time from now" alarms are unexpectedly imprecise
https://bugs.kde.org/show_bug.cgi?id=463278 David Jarvie changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #1 from David Jarvie --- KAlarm does not provide sub-minute accuracy. All alarms are scheduled to (approximately) minute boundaries. You need to use an alternative application if you need reminders more accurate than to the nearest (rounded down) minute. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 461713] Unexpected behavior occurs when certain alarm types are set to trigger within an hour of Daylight Savings Time ending.
https://bugs.kde.org/show_bug.cgi?id=461713 David Jarvie changed: What|Removed |Added Version Fixed In||22.12 Latest Commit||https://invent.kde.org/pim/ ||kalarm/-/commit/3d26729783c ||3da588a3bed9107d62c31b4100a ||38 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #2 from David Jarvie --- This is now fixed by commit 3d26729783c3da588a3bed9107d62c31b4100a38. It will be in KAlarm version 3.5.3 in KDE Gear 22.12. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 461713] Unexpected behavior occurs when certain alarm types are set to trigger within an hour of Daylight Savings Time ending.
https://bugs.kde.org/show_bug.cgi?id=461713 David Jarvie changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from David Jarvie --- Thank you for your detailed bug report. Investigation into the cause shows that there is a basic bug (in the KADateTime class code) in the handling of times which repeat after a daylight savings -> standard time shift. The result of the bug is that after an alarm triggers during this time window, the evaluation of the alarm's next trigger time erroneously calculates the same time again, instead of a day later. This then leads to the alarm being continually triggered, as you have seen. It will take some work to fix this properly, but a fix should be ready for the next release in KDE Gear 22.12. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 455377] Akonadi/Kalarm Constant Disk Access & High CPU Usage + Creates 700,000 Files
https://bugs.kde.org/show_bug.cgi?id=455377 --- Comment #5 from David Jarvie --- I have suspected in the past that sometimes KAlarm does not show up in the system tray when it should. I suspect that this may have been due to some glitch in Plasma, although I could never confirm this. In KDE 22.08, I haven't seen this issue, so it may have been fixed by now. I suggest that if KAlarm is running, i.e. if 'kalarm --tray' shows in the task list, that you kill it, and then start up KAlarm again. Then in its Preferences dialog (Settings -> Configure KAlarm), in the View tab, deselect Show in System Tray. It should then run normally but not in the system tray. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 460389] After 08.10.2020 Kalarm, Korganizer, Calendar dont work correctly.
https://bugs.kde.org/show_bug.cgi?id=460389 --- Comment #26 from David Jarvie --- Try the KDE kdepim-users mailing list for help on this. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 460389] After 08.10.2020 Kalarm, Korganizer, Calendar dont work correctly.
https://bugs.kde.org/show_bug.cgi?id=460389 --- Comment #24 from David Jarvie --- It may be called kontact. You need to raise a new bug report for kontact (if that's the correct product name) about that issue. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 460389] After 08.10.2020 Kalarm, Korganizer, Calendar dont work correctly.
https://bugs.kde.org/show_bug.cgi?id=460389 --- Comment #21 from David Jarvie --- Unfortunately how to get a consistent working system again is a distro issue, not a KDE issue. If you can't sort it out, you need to ask for help on ArchLinux/Manjaro mailing lists. The KDE bug reporting system can't help with this. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 460389] After 08.10.2020 Kalarm, Korganizer, Calendar dont work correctly.
https://bugs.kde.org/show_bug.cgi?id=460389 --- Comment #17 from David Jarvie --- The error message which you report in comment 14 shows that the libicu package either is not installed or is the wrong version. This shows that other packages than libical have been changed when you downgraded libical. You need to ensure that ONLY libical is changed when you downgrade it. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 460389] After 08.10.2020 Kalarm, Korganizer, Calendar dont work correctly.
https://bugs.kde.org/show_bug.cgi?id=460389 --- Comment #15 from David Jarvie --- When you downgraded libical, no other packages should have been changed. There are evidently missing dependencies, which should not have happened when just libical was supposed to have been changed. I'm not familiar with the package system on Manjaro/ArchLinux, so I can't help with how to do it correctly, but it looks like you must have used a wrong command or something. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 460389] After 08.10.2020 Kalarm, Korganizer, Calendar dont work correctly.
https://bugs.kde.org/show_bug.cgi?id=460389 --- Comment #13 from David Jarvie --- Just to be sure that I understand you correctly, please confirm that you downgraded the libical package to version 3.0.14, and that the faults still occurred. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 460442] Unable to use KAlarm because "no writable active calendar is enabled"
https://bugs.kde.org/show_bug.cgi?id=460442 David Jarvie changed: What|Removed |Added CC||ali_d...@gmx.com --- Comment #7 from David Jarvie --- *** Bug 460389 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 460389] After 08.10.2020 Kalarm, Korganizer, Calendar dont work correctly.
https://bugs.kde.org/show_bug.cgi?id=460389 David Jarvie changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #11 from David Jarvie --- This is due to a bug in libical version 3.0.15. This should be reported on the Manjaro bug reporting system. A downgrade to libical version 3.0.14 will fix the issue. *** This bug has been marked as a duplicate of bug 460442 *** -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 460442] Unable to use KAlarm because "no writable active calendar is enabled"
https://bugs.kde.org/show_bug.cgi?id=460442 David Jarvie changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #6 from David Jarvie --- Thank you for confirming that libical version 3.0.15 causes the bug. It would be a good idea to report this problem on the ArchLinux bug reporting system, to ask for a downgrade to 3.0.14. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 460389] After 08.10.2020 Kalarm, Korganizer, Calendar dont work correctly.
https://bugs.kde.org/show_bug.cgi?id=460389 David Jarvie changed: What|Removed |Added CC||kdepim-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 460389] After 08.10.2020 Kalarm, Korganizer, Calendar dont work correctly.
https://bugs.kde.org/show_bug.cgi?id=460389 --- Comment #4 from David Jarvie --- There are no attachments for this bug report. Can you please try to attach the images again. I think that the bug is likely to be the same as Bug 460442, but without seeing your images it's difficult to be sure. Please see my comments in https://bugs.kde.org/show_bug.cgi?id=460442#c1. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 460442] Unable to use KAlarm because "no writable active calendar is enabled"
https://bugs.kde.org/show_bug.cgi?id=460442 --- Comment #1 from David Jarvie --- I don't get this issue on my system, which is an up to date KDE Neon development installation. I extracted the calendar file contents from your report to create a calendar file, and that also works correctly in KAlarm for me. None of the code in KAlarm relating to calendar reading/writing has changed recently. Since KAlarm works for me using the current version of libkf5calendarcore, the KDE library which it uses to access calendar data, it could be that libical, the 3rd party library used by libkf5calendarcore to access iCalendar data, is responsible for what you see. This bug seems to be specific to ArchLinux (see also https://bugs.kde.org/show_bug.cgi?id=460389 which may be the same issue). If so, this also points to a third party library issue. What version of libical (possibly libical3) is installed on your system? -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 460389] After 08.10.2020 Kalarm, Korganizer, Calendar dont work correctly.
https://bugs.kde.org/show_bug.cgi?id=460389 --- Comment #2 from David Jarvie --- Please describe what is incorrect about KAlarm's startup. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 459901] Kalarm crashes after boot and defer
https://bugs.kde.org/show_bug.cgi?id=459901 David Jarvie changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Version Fixed In||22.08.2 Latest Commit||https://invent.kde.org/pim/ ||kalarm/-/commit/97e71e60e1f ||7deac26547adb4decfe3531d2b3 ||76 --- Comment #4 from David Jarvie --- I haven't been able to reproduce the crash, but it looks as if session restoration of KAlarm hasn't fully worked. Your last comment 3 seems to confirm this - it looks as if it only fully initialises after autostart occurs 30 seconds later. If session restoration had worked properly, the crash wouldn't have happened no matter how soon you clicked defer. I've made a fix which I feel reasonably confident should work, but please test again after you have updated to KDE Gear 22.08.2 or later, and reopen the bug if it still crashes. The fix is in KAlarm version 3.5.2 which will be released in KDE Gear 22.08.2, commit 97e71e60e1f7deac26547adb4decfe3531d2b376. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 459901] Kalarm crashes after boot and defer
https://bugs.kde.org/show_bug.cgi?id=459901 --- Comment #1 from David Jarvie --- Can you please attach your KAlarm config file. It should be located at ~/.config/kalarmrc Also, can you confirm whether there is a KAlarm main window visible when the crash occurs. If not, is KAlarm running in the system tray? -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 459931] KAlarm crushed after running
https://bugs.kde.org/show_bug.cgi?id=459931 David Jarvie changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|RESOLVED --- Comment #1 from David Jarvie --- Unfortunately the crash doesn't contain any information which would help to identify why the crash occurred (all the information relates to the Qt library, and none to any KAlarm code. I therefore have to close the bug report. If you are able to provide any more information as to how to reproduce the crash, please do so and reopen the bug. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 454981] improvement of recurring alarms
https://bugs.kde.org/show_bug.cgi?id=454981 David Jarvie changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kholidays] [Bug 457176] New: No API documentation for HolidayRegion::rawHolidaysWithAstroSeasons()
https://bugs.kde.org/show_bug.cgi?id=457176 Bug ID: 457176 Summary: No API documentation for HolidayRegion::rawHolidaysWithAstroSeasons() Product: frameworks-kholidays Version: 5.96.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: djar...@kde.org Target Milestone: --- There is nothing in the API documentation to indicate what HolidayRegion::rawHolidaysWithAstroSeasons() is for, as compared to HolidayRegion::rawHolidays() - the API description for the two methods is identical. The name rawHolidaysWithAstroSeasons doesn't mean anything to me, so a description is necessary. Looking at the autotest/testholidayregion.cpp code, it seems, counter-intuitively, that rawHolidaysWithAstroSeasons() is functionally equivalent to the deprecated holidays() function. Rather, I would have expected that rawHolidays() would now be equivalent to holidays(). Please include descriptions for rawHolidaysWithAstroSeasons() and rawHolidays() which makes clear what each is actually for. SOFTWARE/OS VERSIONS KDE Frameworks Version: 5.97.0 -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 456845] Volume problem with repeated playback of sound files
https://bugs.kde.org/show_bug.cgi?id=456845 David Jarvie changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Version Fixed In||22.08 Latest Commit||https://invent.kde.org/pim/ ||kalarm/-/commit/45f4df183eb ||af94bbdf42652d8fc843056e26a ||be Summary|Problems with repeated |Volume problem with |playback of sound files |repeated playback of sound ||files --- Comment #1 from David Jarvie --- This has now been fixed by commit 45f4df183ebaf94bbdf42652d8fc843056e26abe for KAlarm version 2.5.0, which will be released in KDE Gear 22.08. Thank you for reporting this bug! -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 455377] Akonadi/Kalarm Constant Disk Access & High CPU Usage + Creates 700,000 Files
https://bugs.kde.org/show_bug.cgi?id=455377 David Jarvie changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||20.08 Status|REPORTED|RESOLVED --- Comment #3 from David Jarvie --- I'm glad you've been able to solve your problems by using the workaround. Re-setting the bug status to fixed, since it's fixed in later versions. -- You are receiving this mail because: You are watching all bug changes.
