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

            Bug ID: 465855
           Summary: Kalk instantly crashes in KDE Plasma 5.27.0
    Classification: Applications
           Product: Kalk
           Version: 23.01.0
          Platform: Archlinux
                OS: Linux
            Status: REPORTED
          Severity: crash
          Priority: NOR
         Component: General
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]
  Target Milestone: ---

SUMMARY
Prior to KDE Plasma 5.27.0 I had no issue with launching flatpak Kalk. I
updated last night and now I cannot launch Kalk anymore. The first error is
complaining about network (which I don't see why Kalk would need) and then when
I granted it network it fails for another reason.

This might be due to a conflict with the new Discover KCM flatpak permissions
and Flatseal?

Putting severity urgent as I rely on kalk daily and have to use my phone
currently lol.

When launching in Konsole this is printed:

without network permission, which I used to not give prior to 5.27.0
Warning: fallback to QtQuick software backend.
Qt: Session management error: Could not open network socket
QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
...........
this is printed about 50 times
..........

after giving network permission

Warning: fallback to QtQuick software backend.
QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
...........
this is printed about 50 times
..........

STEPS TO REPRODUCE
1. Update to KDE Plasma 5.27.0 and have flatpak-kcm maybe?
2. Try to launch flatpak Kalk

OBSERVED RESULT
Application does not launch

EXPECTED RESULT
Application launches.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.0
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.10.hardened1-1-hardened (64-bit)

flatpak 1:1.15.2-1
flatpak-kcm 5.27.0-1
bubblewrap 0.7.0-1

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

Reply via email to