Bug 466287 - Timers cannot have negative intervals crash on startup
Summary: Timers cannot have negative intervals crash on startup
Status: ASSIGNED
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: nightly build (please specify the git hash!)
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-23 05:08 UTC by Ralek Kolemios
Modified: 2023-08-07 16:10 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Backtrace of the hit (2.28 KB, text/plain)
2023-02-23 18:30 UTC, amyspark 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ralek Kolemios 2023-02-23 05:08:39 UTC 
In the latest several nightly master releases, Krita crashes on startup. The output it gives when run in terminal is this:

> krita.lib.pigment: Replacing color space factory "LABA" "L*a*b* (16-bit integer/channel, unmanaged)" with "LABA" "L*a*b*/Alpha (16-bit integer/channel)"
> krita.lib.pigment: Replacing color space factory "RGBA" "RGB (8-bit integer/channel, unmanaged)" with "RGBA" "RGB/Alpha (8-bit integer/channel)"
> krita.lib.pigment: Replacing color space factory "RGBA16" "RGB (16-bit integer/channel, unmanaged)" with "RGBA16" "RGB/Alpha (16-bit integer/channel)"
> QObject::startTimer: Timers cannot have negative intervals
> /tmp/.mount_krita-MpqDCc/usr/lib/krita-python-libs/krita added to PYTHONPATH


I have tested from 0e85ce2a to the latest d92f026c
Comment 1 amyspark 2023-02-23 10:36:37 UTC 
I've seen it for quite a long time, I'll assign and see what's going on. However, this is not a crash, just a complaint from inside the Qt runtime.
Comment 2 Ralek Kolemios 2023-02-23 10:40:22 UTC 
Not sure what is causing the crash at startup then, as that's the entire console output. It acts similarly to the bug from not too long ago with the X11 window system, where it wouldn't even make it to the splash screen.
Comment 3 Freya Lupen 2023-02-23 18:07:27 UTC 
If I remember correctly, the QTimer warning is coming from here: https://invent.kde.org/graphics/krita/-/commit/19ba224692a52b1d5799fda308bed4b02ff38f7a
Comment 4 amyspark 2023-02-23 18:30:50 UTC 
Created attachment 156657 [details]
Backtrace of the hit
Comment 5 amyspark 2023-02-23 18:31:48 UTC 
Halla, is this workaround still needed? Both bugs are closed (if dubiously) in upstream.
Comment 6 amyspark 2023-02-24 01:44:04 UTC 
Update: I tried defining locally`-no-feature-bearermanagement` to remove the affected component, since it's already deprecated in Qt5 and removed in Qt6. However, that breaks build because PyQt5 itself hard expects that component to be present to build its API.
Comment 7 Halla Rempt 2023-02-24 12:45:21 UTC 
I don't know whether it's still needed. It really was an obscure bug...
Comment 8 amyspark 2023-03-06 13:17:25 UTC 
I'll try and remove the bearer management support from Qt and PyQt5. That'll enable us to drop the workaround.
Comment 9 Halla Rempt 2023-03-06 13:48:25 UTC 
We'd still have to have the workaround for distribution packages, though.
Comment 10 amyspark 2023-03-06 15:46:25 UTC 
I know. There's a macro that Qt exposes when the bearer management isn't built and that we can use. PyQt5, for some reason, has never made use of it so that's why it needs extra work, otherwise it'll build everything and fail at SIP binding creation.