[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3

[David Faure]

https://bugs.kde.org/show_bug.cgi?id=353203

David Faure  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #55 from David Faure  ---
This issue seems to have become a catch-all for all sorts of different issues
on different systems with different KF5 versions for different reasons, over
many different years...

The problems with KService, which is what this issue was supposed to be about,
ar fixed by now (for quite some time).

Please open different bug reports for different issues.

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

[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=353203

esi...@gmail.com changed:

   What|Removed |Added

 CC||esi...@gmail.com

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

[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=353203

pos...@posteo.eu changed:

   What|Removed |Added

 CC||pos...@posteo.eu

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

[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3

[Alan Mimms via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353203

Alan Mimms  changed:

   What|Removed |Added

 CC||al...@unforgettable.com

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

[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3

[Valdas via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353203

--- Comment #54 from Valdas  ---
 My findings: I'm freshly installed Kubuntu 16.04 and I was experienced no
delay in login until I was paired system with my phone (using Bluetooth). Now
that delay comes back.
 Maybe my experience related to another bug?

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

[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3

[microcai via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353203

--- Comment #53 from microcai  ---
if you have problem with dbus-update-activation-environment, then you must be
using ArchLinux and you must have dbus-daemon activated by systemd user
instance. please check if you had once refer to the Arch wiki and tweaked the
dbus user daemon activation mechanism. revert to upstream method then 
dbus-update-activation-environment won't block anymore.

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

[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3

[AnAkkk via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353203

AnAkkk  changed:

   What|Removed |Added

 CC|anakin...@gmail.com |

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

[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3

[Søren Holm via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353203

--- Comment #52 from Søren Holm  ---
This bug has - for kubuntu 16.04 - been completely solved until a few days ago.
Can anyone confirm that?

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

[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3

[Søren Holm via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353203

--- Comment #51 from Søren Holm  ---
Removing dbus-update-activation-environment from startkde did not solve it or
me. skipping "--systemd" was no luck either.

Interestingly enough, the first login running completely without
dbus-update-activation-environment but with
/usr/lib/x86_64-linux-gnu/libexec/ksyncdbusenv instead work well for ONE login.
After that it made no difference.

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

[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3

[Søren Holm via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353203

Søren Holm  changed:

   What|Removed |Added

 CC||s...@sgh.dk

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

[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3

[Valdas via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353203

--- Comment #50 from Valdas  ---
If I remove "--systemd" then after login screen I get graphical window (like
messagebox) with text "Could not sync environment to dbus.", and if click "OK"
then graphics freezes and KDE not loads (but I still can switch in to text
console by Alt+Ctrl+F1).

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

[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3

[microcai via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353203

--- Comment #49 from microcai  ---
you should not remove  dbus-update-activation-environment --systemd --all

just remove --systemd

leave it as dbus-update-activation-environment  --all

the all problem solved.

if you delete the call to dbus-update-activation-environment then it will still
delay 25 seconds.

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

[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3

[Andreas T via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353203

--- Comment #48 from Andreas T  ---
I'm on Ubuntu 15.10 and startkde does not contain a call to
dbus-update-activation-environment - there is only a call to ksyncdbusenv. So I
don't think that this is the root cause of the delay on startup :(

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

[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3

[Valdas via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353203

--- Comment #47 from Valdas  ---
If I comment in "startkde" like this:

# At this point all environment variables are set, let's send it to the DBus
session server to update the activation environment
#if which dbus-update-activation-environment >/dev/null 2>/dev/null ; then
#dbus-update-activation-environment --systemd --all
#else
/usr/lib/x86_64-linux-gnu/libexec/ksyncdbusenv
#fi


then issue remains.

I must mention: during that pause I can "Alt+F2" then type "firefox" with
following Enter and then with "Alt+Tab" I can see started Firefox window in
Application switcher visualization.

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

[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3

[David Faure via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353203

--- Comment #46 from David Faure  ---
microcai, can you create a different bug report for this, and assign it to
jan.steff...@gmail.com who introduced the use of
dbus-update-activation-environment in commit
90081cb0483ffc3ad46af3b99de171ed38716ac0 (plasma-workspace git repo) ?

Everyone else: if you comment out the call to
dbus-update-activation-environment from your startkde, does the issue go away?
If yes, we can close this, if not, then there are two separate issues.

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

[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3

[microcai via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353203

microcai  changed:

   What|Removed |Added

 CC||microcai...@gmail.com

--- Comment #45 from microcai  ---
guys, the exact reason is in startkde

dbus-update-activation-environment --systemd --all

this line. blocks 25~ and then print

dbus-update-activation-environment: warning: error sending to systemd:
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus security
policy blocked the reply, the reply timeout expired, or the network connection
was broken.

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

[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353203

--- Comment #44 from OlafLostViking  ---
I can not confirm that completely. While it seems to be true that the login is
faster (but no guarantees for now ;-) ), a lot of autostarted programs (be it
by explicit autostart or by session restoration) now take this time to finally
start up. The desktop/plasmashell is (partly?) there and seems to be useable,
but a lot of the programs are just starting much later (and in case of programs
showing dialogs, pop up all together - like a restored kontact with open mails
or the CopyAgent from copy.com).

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

[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3

[Mister Ypsilon via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353203

--- Comment #43 from Mister Ypsilon  ---
After upgrading Frameworks to version 5.17, the problem went away for me. Login
is super fast now, like 3-5 seconds.

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

[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353203

--- Comment #40 from raphael.cazen...@gmail.com ---
@David V, i use on both computer the driver for Intel. Your observation seems
disburting.
@ Tom Canavan, good to see the issue is gone for you :), you mention an update.
To be useful for other distros, can you tell more about wich packages got
updated on your Fedora and the from to version ? Thanks

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

[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3

[Tom Canavan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353203

--- Comment #41 from Tom Canavan  ---
Created attachment 96023
  --> https://bugs.kde.org/attachment.cgi?id=96023=edit
Diff to show fedora packages that were updated after the update on Dec 12, 2015

Output of diff -y --suppress-common-lines to show fedora packages updated by
the update on Dec. 12, 2015

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

[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3

[Tom Canavan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353203

--- Comment #42 from Tom Canavan  ---
@raphael.cazenave
I think I spoke too soon.  The update helped, but it didn't solve the problem
completely.  After the update, I rebooted and logged in 3 times and each time,
it logged me in in about 6-10 seconds.  Then I went away for awhile and came
back.  booted and it took 2:30 to log in and I got that
"autoStart2Done timedout, this is a BUG!" message in /~.xsession-errors again. 
This last time, it logged me in in 1:50 seconds and I did NOT get the error. 
Strange.  It seems to happen a little differently each time I log in.  But at
least it doesn't seem to hang completely like it did before.  (knock on wood). 
I'm posting a file to show the fedora packages that were updated.  Hope this
helps.

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

[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3

[Tom Canavan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353203

Tom Canavan  changed:

   What|Removed |Added

 CC||tmscana...@centurytel.net

--- Comment #38 from Tom Canavan  ---
FWIW, this is happening also Fedora 23.  I am using kf5-plasma-5.16.0-4.

Symptoms are,  It's down to a matter of luck whether plasma shows me my panel
with icons and the icons on the desktop.  It has gone on for at least two
minutes sometimes. After that I usually give up and reboot Sometimes everything
will show up after a couple minutes, and sometimes it will not. Sometimes if I
let it go long enough, things will show up little by little.  Like he said,
about 50/50 chance

I am getting the "autoStart2Done timedout, this is a BUG!"
message in /~.xsession-errors.

I am using Intel onboard graphics and only one monitor on my tower system.  So
whatever it is, it is probably not limited to Nvidia graphics.

I could post copies of this stuff, but it is rather long. 
This is a rather serious problem and costs a lot of time. Hope this helps.

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