https://bugs.kde.org/show_bug.cgi?id=405446
Bug ID: 405446
Summary: ksplashqml hits its hard timeout of 30 seconds because
setStage(6) is needed twice
Product: ksplash
Version: 5.14.5
Platform: Debian testing
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: bernha...@mailbox.org
Target Milestone: ---
Created attachment 118782
--> https://bugs.kde.org/attachment.cgi?id=118782&action=edit
ksplashqml: Quit on first call to setStage with stage == 6.
As far as I see the dbus interface setStage is called with 6 different strings.
These get stored in m_stages and an setStage overload is called with the number
of elements in m_stages.
When setStage is called with parameter stage==6 another it gets not into the
closing path immediately because another setStage call is needed for some
reason.
I could not find a reason for the need of this second setStage call and
therefore
want to ask if the assignment has really to be done before the check "m_stage
== 6"?
With this I get the ksplashqml appearance of less than 5 seconds instead of 30.
The second attached patch was used to get some logging from ksplashqml.
Operating System: Debian GNU/Linux
KDE Plasma Version: 5.14.5
Qt Version: 5.11.3
KDE Frameworks Version: 5.54.0
Kernel Version: 4.19.0-2-amd64
OS Type: 64-bit
Processors: 16 × AMD Ryzen 7 1700 Eight-Core Processor
Memory: 15.5 GiB of RAM
--
You are receiving this mail because:
You are watching all bug changes.
