Discussion:
[ksplash] [Bug 391805] New: Splashscreen always visible for 30 seconds. Plasma is ready much earlier.
Add Reply
Arek Guzinski
2018-03-13 10:10:12 UTC
Reply
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=391805

Bug ID: 391805
Summary: Splashscreen always visible for 30 seconds. Plasma is
ready much earlier.
Product: ksplash
Version: 5.12.3
Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: ***@kde.org
Reporter: ***@ag.de1.cc
Target Milestone: ---

Every time i log in to plasma, the splash screen is visible for exactly 30
seconds (i assume thats the timeout).
However plasma is ready after a few seconds.

$ top -b > log
shows that there is barely any CPU activity after 8 seconds.

$ when i log in via ssh and killall ksplashqml prematurely, plasma looks
perfectly ready.

I created a new user and logged in: same problem.

On another (much slower) Computer with the same package versions, ksplashqml
disappears after about 15 seconds, likely because plasma is ready...

https://bugs.kde.org/show_bug.cgi?id=380495 sounded like it might be related,
so i tried the patch: no change


This has been going on for a while now.. perhaps since 5.12.0

Now i'm out of ideas where to look :/
What would, under normal circumstances, tell ksplashqml to quit?
--
You are receiving this mail because:
You are watching all bug changes.
Kai Uwe Broulik
2018-03-13 12:08:31 UTC
Reply
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=391805

Kai Uwe Broulik <***@privat.broulik.de> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@privat.broulik.de,
| |plasma-***@kde.org
Assignee|***@kde.org |***@davidedmundson.co.uk
Product|ksplash |plasmashell
Target Milestone|--- |1.0
Component|general |general
--
You are receiving this mail because:
You are watching all bug changes.
David Edmundson
2018-03-13 13:05:04 UTC
Reply
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=391805
Post by Arek Guzinski
What would, under normal circumstances, tell ksplashqml to quit?
Plasma signalling it's ready (along with some other modules)

Can you include output of ~/.local/share/sddm/xorg-session.log after logging
in.
--
You are receiving this mail because:
You are watching all bug changes.
David Edmundson
2018-03-13 13:22:22 UTC
Reply
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=391805

David Edmundson <***@davidedmundson.co.uk> changed:

What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WAITINGFORINFO
Status|UNCONFIRMED |NEEDSINFO

--- Comment #2 from David Edmundson <***@davidedmundson.co.uk> ---
Marking as needsinfo, please reset status to unconfirmed after attaching log
--
You are receiving this mail because:
You are watching all bug changes.
Arek Guzinski
2018-03-13 13:39:27 UTC
Reply
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=391805
Can you include output of ~/.local/share/sddm/xorg-session.log after logging in.
I would, if there was something to include.
$ ls -l ~/.local/share/sddm/xorg-session.log
-rw------- 1 arek arek 0 Mär 13 14:29
/home/arek/.local/share/sddm/xorg-session.log

same on my laptop btw. (where it's working properly)

are there any other logs that could help?
--
You are receiving this mail because:
You are watching all bug changes.
Arek Guzinski
2018-03-13 13:48:03 UTC
Reply
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=391805

Arek Guzinski <***@ag.de1.cc> changed:

What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |UNCONFIRMED

--- Comment #4 from Arek Guzinski <***@ag.de1.cc> ---
just saw your comment about the status.. interpreting it as "set now"..

I noticed one strange thing (althought my guess is it's probably unrelated):
when i log in as myself, the rotating thingie below the plasma-icon disappers
after ~8 sec. For the new user, it keeps rotating the full 30 sec until the
end.
--
You are receiving this mail because:
You are watching all bug changes.
Nate Graham
2018-03-13 15:40:13 UTC
Reply
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=391805

Nate Graham <***@kde.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@kde.org
--
You are receiving this mail because:
You are watching all bug changes.
Arek Guzinski
2018-05-07 05:40:15 UTC
Reply
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=391805

--- Comment #5 from Arek Guzinski <***@ag.de1.cc> ---
Bug no longer occurs in 5.12.5 :)

As for formalaties: should I set the status to closed, or should that be done
by the assignee/maintainer/whoever after some investigation into what might
have fixed it? Are there any guidelines?
--
You are receiving this mail because:
You are watching all bug changes.
Nate Graham
2018-05-07 16:20:53 UTC
Reply
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=391805

Nate Graham <***@kde.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|UNCONFIRMED |RESOLVED

--- Comment #6 from Nate Graham <***@kde.org> ---
You can do it yourself. It's easy enough to re-open a bug. :)

I'll do it for you this time since I'm already commenting here.
--
You are receiving this mail because:
You are watching all bug changes.
Loading...