https://bugs.kde.org/show_bug.cgi?id=353203
David Faure changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=353203
esi...@gmail.com changed:
What|Removed |Added
CC||esi...@gmail.com
--
You are receiving this m
https://bugs.kde.org/show_bug.cgi?id=353203
pos...@posteo.eu changed:
What|Removed |Added
CC||pos...@posteo.eu
--
You are receiving this m
https://bugs.kde.org/show_bug.cgi?id=353203
Alan Mimms changed:
What|Removed |Added
CC||al...@unforgettable.com
--
You are receiving this
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?
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 twe
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 watc
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.
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-envir
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 becaus
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 i
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-act
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 ar
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/nu
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 (plasm
https://bugs.kde.org/show_bug.cgi?id=353203
microcai changed:
What|Removed |Added
CC||microcai...@gmail.com
--- Comment #45 from microcai
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 tak
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.
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. T
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&action=edit
Diff to show fedora packages that were updated after the update on Dec 12, 2015
Output of diff -y --suppress-common-lines to sh
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,
https://bugs.kde.org/show_bug.cgi?id=353203
--- Comment #39 from Tom Canavan ---
This problem seems to be fixed after the updates Sat. Dec. 12. Login is very
quick. About 6 seconds. I am no longer getting the "autoStart2Done timedout,
this is a BUG!" message in /~.xsession-errors. Seems the
https://bugs.kde.org/show_bug.cgi?id=353203
Andreas T changed:
What|Removed |Added
CC||a.tetz...@gmx.de
--
You are receiving this mail be
https://bugs.kde.org/show_bug.cgi?id=353203
Tom Canavan changed:
What|Removed |Added
CC||tmscana...@centurytel.net
--- Comment #38 from To
24 matches
Mail list logo
