Your message dated Sat, 15 Feb 2020 17:52:42 +0100 with message-id <12899567.f54Hu2rLGo@thyrus> and subject line Re: Bug#924507: ksplashqml: hits its hard timeout of 30 seconds has caused the Debian Bug report #924507, regarding ksplashqml: hits its hard timeout of 30 seconds to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 924507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924507 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: ksplashqml: hits its hard timeout of 30 seconds
- From: Bernhard Übelacker <bernhardu@mailbox.org>
- Date: Wed, 13 Mar 2019 19:44:56 +0100
- Message-id: <60746125-76b1-8050-e4e4-33d0b51d4204@mailbox.org>
Package: plasma-workspace Version: 4:5.14.5.1-1 Severity: normal Tags: patch upstream Dear Maintainer, I found that the splash screen takes longer than some month ago and did some investigations that led to following two upstream bugs I reported. Bug 405444 - ksplashqml hits its hard timeout of 30 seconds because of failing qdbus call kinit Bug 405446 - ksplashqml hits its hard timeout of 30 seconds because setStage(6) is needed twice Because of the near buster release they might be evaluated independent of upstream for its use in buster to avoid bad user impressions. The first one probably just manifests on faster systems when the dbus interface of ksplashqml is not yet up. The second one might need two setStage(6) calls to arrive when we maybe just receive one. Both changes reduced the time ksplashqml is shown at my system from 30 to 5 seconds. Kind regards, Bernhard https://bugs.kde.org/show_bug.cgi?id=405444 https://bugs.kde.org/show_bug.cgi?id=405446
--- End Message ---
--- Begin Message ---
- To: Bernhard Übelacker <bernhardu@mailbox.org>, 924507-done@bugs.debian.org
- Subject: Re: Bug#924507: ksplashqml: hits its hard timeout of 30 seconds
- From: Pino Toscano <pino@debian.org>
- Date: Sat, 15 Feb 2020 17:52:42 +0100
- Message-id: <12899567.f54Hu2rLGo@thyrus>
- Reply-to: 924507@bugs.debian.org
- In-reply-to: <60746125-76b1-8050-e4e4-33d0b51d4204@mailbox.org>
- References: <60746125-76b1-8050-e4e4-33d0b51d4204@mailbox.org>
Source: plasma-workspace Source-Version: 4:5.17.5-1 In data mercoledì 13 marzo 2019 19:44:56 CET, Bernhard Übelacker ha scritto: > Package: plasma-workspace > Version: 4:5.14.5.1-1 > Severity: normal > Tags: patch upstream > > Dear Maintainer, > > I found that the splash screen takes longer than some month ago and did > some investigations that led to following two upstream bugs I reported. > > Bug 405444 - ksplashqml hits its hard timeout of 30 seconds because of failing qdbus call kinit > Bug 405446 - ksplashqml hits its hard timeout of 30 seconds because setStage(6) is needed twice > > Because of the near buster release they might be evaluated independent of > upstream for its use in buster to avoid bad user impressions. > > The first one probably just manifests on faster systems when the > dbus interface of ksplashqml is not yet up. > > The second one might need two setStage(6) calls to arrive when we > maybe just receive one. > > Both changes reduced the time ksplashqml is shown at my > system from 30 to 5 seconds. > > Kind regards, > Bernhard > > > https://bugs.kde.org/show_bug.cgi?id=405444 > https://bugs.kde.org/show_bug.cgi?id=405446 The bug was fixed upstream in plasma-workspace 5.15.4 -- hence closing with the first version after it available in Debian (4:5.17.5-1). Thanks, -- Pino ToscanoAttachment: signature.asc
Description: This is a digitally signed message part.
--- End Message ---