You are not logged in.
fettouhi wrote:Fregtux wrote:I've this issue too. In that post they say to use this revert:
https://git.reviewboard.kde.org/r/112073/
Did you try it? Does it solve the issue?
I'm not quite sure I understand the fix mentioned in the above link?
You have to do this:
https://git.reviewboard.kde.org/r/11207 … dex_header
that is change in plasma-desktop.desktop from:
X-DBUS-StartupType=unique
to
X-DBUS-StartupType=multi
That fixed it for me . I'm on 64 bit btw.
Last edited by fettouhi (2013-08-20 17:49:39)
Offline
Offline
Manuel de la Fuente wrote:I have a worse problem: after updating to KDE 4.11, my Plasma crashes every time at boot. I tried to downgrade to kdebase-plasma 4.10.5, but the issue persisted. I need to execute plasma-desktop in Konsole manually after it crashes to start Plasma again, and then it works normally, but I need to do that every time at boot.
I had the same problem, so I found a workaround (gentoo forums).
Edit /usr/share/autostart/plasma-desktop.desktop and change:
Exec=plasma-desktop
for
Exec=sleep .1 && plasma-desktopplasma-desktop will wait 0.1 seconds and then it'll start.
Regards.
I had the same problem and this seems to have fixed it for me.
changing /usr/share/autostart/plasma-desktop.desktop to
X-DBUS-StartupType=multi
didn't fix it for me. I have in i686 32bit System. On my mother's laptop 64bit I don't have the exact problem but the fading effect when loggin in doesn't work and for a short moment I get a black screen. Then everthing works normaly.
Offline
So are there two different solution based on arch installation architecture? Is it strange, doesn't it?
ASUS P8P67 EVO | i7-2600k |RAM 16GB DDR 3 Vengeance@1600MHz | AMD 7950 Sapphire Dual-X | SSD: Samsung 830 250GB | HD: Western Digital Caviar Blue 1TB
Offline
Fregtux wrote:fettouhi wrote:I'm not quite sure I understand the fix mentioned in the above link?
You have to do this:
https://git.reviewboard.kde.org/r/11207 … dex_header
that is change in plasma-desktop.desktop from:
X-DBUS-StartupType=unique
to
X-DBUS-StartupType=multi
That fixed it for me . I'm on 64 bit btw.
This worked on both i686 and x64 for me.
Offline
Fixed in kdebase-workspace 4.11.0-2
Offline
Thank you for the quick fix! You're the best!
No other problems with 4.11 so far on my end.
Offline
Fixed in kdebase-workspace 4.11.0-2
I don't agree, the bug is not fixed by " kdebase-workspace 4.11.0-2" when a i686 installation of archlinux is used, plasma-desktop still crashs on kde boot,
the only solution ( for now ) is this workaround :
edit the file /usr/share/autostart/plasma-desktop.desktop
and replace the line:
Exec=plasma-desktop
by this :
Exec=sleep 10 && plasma-desktop
"Exec=sleep 3 && plasma-desktop" can also work but it is safe to add more delay like "sleep 10"
please edit the title of this thread and remove the mention "solved" because it's not the case
Last edited by Potomac (2013-08-21 12:43:01)
Offline
I don't agree, the bug is not fixed by " kdebase-workspace 4.11.0-2" when a i686 installation of archlinux is used, plasma-desktop still crashs on kde boot,
That's what happens when you mix different issues in the same thread. This thread was originally about the startup delay, and that is fixed in 4.11.0-2. The crash is a completely different issue, and is still not fixed upstream.
Online
That's what happens when you mix different issues in the same thread. This thread was originally about the startup delay, and that is fixed in 4.11.0-2. The crash is a completely different issue, and is still not fixed upstream.
+1, if you feel like following up the crash issue Potomac, it is probably more effective and will lead to a more focused discussion if you start a separate thread and link to this thread for background info
Offline
Fixed in kdebase-workspace 4.11.0-2
All hail to the KDE Master! Thank you for your usual quickness!
Offline
No more black screen after ksplash! Thanks
ASUS P8P67 EVO | i7-2600k |RAM 16GB DDR 3 Vengeance@1600MHz | AMD 7950 Sapphire Dual-X | SSD: Samsung 830 250GB | HD: Western Digital Caviar Blue 1TB
Offline
I confirm Potomac comment #33 that i686 was not fixed. Same crash, same sleep fix.
Offline
I confirm Potomac comment #33 that i686 was not fixed. Same crash, same sleep fix.
I confirm too.
The 'sleep 10' workaround doesn't work for me.
Last edited by karlzt (2013-08-22 23:00:34)
----------------------------------------------------------------------------
It is a miracle that curiosity survives formal education. - Einstein
Black holes are nothing but gigantic galactic segfaults
Offline
I confirm that the problem persist in KDE 4.11 i686 and not fixed with kdebase-workspace 4.11.0-2
Plasma crashes every time at boot, for now alt+F2, run plasma workspace and select Netbook workspace type and apply. then select desktop type again and apply and work fine for now. sleep 10 not working for me.
Last edited by Tamux (2013-08-22 20:17:28)
Offline
@Tamux
Alt-F2 run plasma-desktop is enough for me.
Last edited by karlzt (2013-08-22 21:24:12)
----------------------------------------------------------------------------
It is a miracle that curiosity survives formal education. - Einstein
Black holes are nothing but gigantic galactic segfaults
Offline
Does the bug report reflect this? There is little chance of it getting fixed if you just report the problem in a [solved] thread. That is, you might get lucky... but why count on luck?
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
@cfr: I don't agree, the bug is not fixed. Some users continue with login problems.
@scarpino: please edit the title of this thread and remove the mention "solved" because it's not the case
@karlzt (Alt-F2 run plasma-desktop is enough for me): yes !!, more practical, is enough for me too.
Offline
I don't see what you disagree with.
It needs to go in the bug report or, if there is more than one bug, a different bug report. Reporting it in a thread marked [solved] is unlikely to lead to a fix.
Asking scarpino to change the title is pointless - scarpino is not the OP.
I suspect the bug causing the problem experienced by the OP and mentioned by scarpino as fixed *is* fixed. The bug causing the problem others are experiencing is not. A separate bug report (if there isn't one already) is needed or an upstream report if that's where the issue lies.
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline