https://bugs.kde.org/show_bug.cgi?id=514212

            Bug ID: 514212
           Summary: segfault/crash when choosing "New Display Alarm" since
                    upgrade to ktextaddons 1.9.0
    Classification: Applications
           Product: kalarm
      Version First 3.12.0.89
       Reported In:
          Platform: Arch Linux
                OS: Linux
            Status: REPORTED
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

SUMMARY
After upgrading from ktextaddons 1.8.0-2 to 1.9.0-1 I could no longer add new
display alarms.  When I clicked New Display Alarm in the application menu or
from the taskbar, kalarm would crash and tell the console there was a
segmentation fault.  I downgraded ktextaddons to 1.8.0-2 and could once again
add display alarms as usual.  This did not affect other alarm types or
deferring existing display alarms.

STEPS TO REPRODUCE
1. run kalarm 3.12.0 with ktextaddons 1.9.0 installed 
2. open either the application menu or the taskbar menu
3. select New Alarm → New Display Alarm

OBSERVED RESULT
kalarm crash.  segfault reported if run from terminal.

EXPECTED RESULT
New Display Alarm window appears over the main kalarm window

SOFTWARE/OS VERSIONS
Linux Version: 6.18.3-arch1-1 (64-bit) 
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.10.1
Graphics Platform: Wayland

ADDITIONAL INFORMATION
As I'm disabled I presently don't have the time to find and install debug
symbols for every single thing involved in kalarm's display alarm window.  I
found the package that can be introduced or removed to introduce or remove the
segfault, as changing nothing but the version of ktextaddons decides whether it
will happen, independent of any other updates or downgrades.  I haven't changed
the text display options in the New Display Alarm window since the defaults
that came with the original installation of kalarm 23.04.2-1 when I first set
up this particular home drive.  If having trouble reproducing, try using the
settings that were default in April 2023.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to