Bug 463388

Summary:	Alarm windows on startup often produce screen errors like flickering areas
Product:	[Applications] kalarm	Reporter:	petrowanton <petrowanton>
Component:	general	Assignee:	David Jarvie <djarvie>
Status:	RESOLVED NOT A BUG
Severity:	normal
Priority:	NOR
Version First Reported In:	3.5.1
Target Milestone:	---
Platform:	Mint (Ubuntu based)
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description petrowanton 2022-12-23 11:38:35 UTC

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1.  Alarm windows on startup often produce screen errors like flickering areas when closed, until another window covers the area by maximizing the window. Sometimes the buttons can not be clicked.
2. 
3. 
passed alarms are not editable, inspite of using the "edit" button.

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

Comment 1 David Jarvie 2023-06-23 23:03:51 UTC

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?

Comment 2 petrowanton 2023-08-28 13:30:41 UTC

Hello,

thanks for your reply.

Screen errors have not occurred for a few days after I reported them.
I assume that this is due to several updates. I make updates as soon as they are available.
at this moment everything works fine.

I would like to see automatic line breaks. The windows automatically become as wide as the longest sentence in the text.

best regards

Am 24.06.23 um 01:03 schrieb David Jarvie:
> https://bugs.kde.org/show_bug.cgi?id=463388
>
> --- Comment #1 from David Jarvie <djarvie@kde.org> ---
> Which desktop environment are you using (eg. KDE Plasma / Gnome / XFCE), and
> which version?

XFCE Desktop: Xfce 4.18.1 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.18.0 vt: 7
            dm: LightDM 1.26.0 Distro: MX-21.3_x64 Wildflower April 23  2023


>
> 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.

ok...

>
> I'm not sure about why buttons sometimes cannot be clicked. This might also be
> due to some window manager issue.
ok...
>
> When the Edit button is clicked, does anything happen (if so, what), or is the
> Edit button simply not clickable?
it - the whole window - was simply not clickable. no reaction to any
mousebutton or keyboardinput. I had to xkill the windows.

Comment 3 David Jarvie 2024-03-02 22:27:43 UTC

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.

Comment 4 David Jarvie 2024-07-08 18:24:46 UTC

It is currently up to the user to control the width of alarm windows by entering line breaks where desired. If KAlarm automatically restricted the width of alarm windows, some users might not actually want this, and there is no way for KAlarm to know what the user actually wants.