[plasmashell] [Bug 391805] Splashscreen always visible for 30 seconds. Plasma is ready much earlier.

2018-03-13 Thread Kai Uwe Broulik
https://bugs.kde.org/show_bug.cgi?id=391805

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de,
   ||plasma-b...@kde.org
   Assignee|l.lu...@kde.org |k...@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.

[plasmashell] [Bug 391805] Splashscreen always visible for 30 seconds. Plasma is ready much earlier.

2018-03-13 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=391805

--- Comment #1 from David Edmundson  ---
>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.

[plasmashell] [Bug 391805] Splashscreen always visible for 30 seconds. Plasma is ready much earlier.

2018-03-13 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=391805

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #2 from David Edmundson  ---
Marking as needsinfo, please reset status to unconfirmed after attaching log

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

[plasmashell] [Bug 391805] Splashscreen always visible for 30 seconds. Plasma is ready much earlier.

2018-03-13 Thread Arek Guzinski
https://bugs.kde.org/show_bug.cgi?id=391805

--- Comment #3 from Arek Guzinski  ---
> 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.

[plasmashell] [Bug 391805] Splashscreen always visible for 30 seconds. Plasma is ready much earlier.

2018-03-13 Thread Arek Guzinski
https://bugs.kde.org/show_bug.cgi?id=391805

Arek Guzinski  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |UNCONFIRMED

--- Comment #4 from Arek Guzinski  ---
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.

[plasmashell] [Bug 391805] Splashscreen always visible for 30 seconds. Plasma is ready much earlier.

2018-03-13 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=391805

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[plasmashell] [Bug 391805] Splashscreen always visible for 30 seconds. Plasma is ready much earlier.

2018-05-06 Thread Arek Guzinski
https://bugs.kde.org/show_bug.cgi?id=391805

--- Comment #5 from Arek Guzinski  ---
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.

[plasmashell] [Bug 391805] Splashscreen always visible for 30 seconds. Plasma is ready much earlier.

2018-05-07 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=391805

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #6 from Nate Graham  ---
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.

[plasmashell] [Bug 391805] Splashscreen always visible for 30 seconds. Plasma is ready much earlier.

2018-03-13 Thread Kai Uwe Broulik
https://bugs.kde.org/show_bug.cgi?id=391805

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de,
   ||plasma-b...@kde.org
   Assignee|l.lu...@kde.org |k...@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.

[plasmashell] [Bug 391805] Splashscreen always visible for 30 seconds. Plasma is ready much earlier.

2018-03-13 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=391805

--- Comment #1 from David Edmundson  ---
>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.

[plasmashell] [Bug 391805] Splashscreen always visible for 30 seconds. Plasma is ready much earlier.

2018-03-13 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=391805

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #2 from David Edmundson  ---
Marking as needsinfo, please reset status to unconfirmed after attaching log

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

[plasmashell] [Bug 391805] Splashscreen always visible for 30 seconds. Plasma is ready much earlier.

2018-03-13 Thread Arek Guzinski
https://bugs.kde.org/show_bug.cgi?id=391805

--- Comment #3 from Arek Guzinski  ---
> 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.

[plasmashell] [Bug 391805] Splashscreen always visible for 30 seconds. Plasma is ready much earlier.

2018-03-13 Thread Arek Guzinski
https://bugs.kde.org/show_bug.cgi?id=391805

Arek Guzinski  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |UNCONFIRMED

--- Comment #4 from Arek Guzinski  ---
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.

[plasmashell] [Bug 391805] Splashscreen always visible for 30 seconds. Plasma is ready much earlier.

2018-03-13 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=391805

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[plasmashell] [Bug 391805] Splashscreen always visible for 30 seconds. Plasma is ready much earlier.

2018-05-06 Thread Arek Guzinski
https://bugs.kde.org/show_bug.cgi?id=391805

--- Comment #5 from Arek Guzinski  ---
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.

[plasmashell] [Bug 391805] Splashscreen always visible for 30 seconds. Plasma is ready much earlier.

2018-05-07 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=391805

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #6 from Nate Graham  ---
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.