Yesterday, KDE 4.11 reached the stable repositories of Arch Linux, and as always, I updated and rebooted my system. However, upon logging in again I ran into something unexpected: Plasma Desktop died within seconds and it left me on a black screen with just the mouse pointer.
The worst thing was that, since I literally hadn't had a single problem updating for months Arch (I think I remember the last one was April 2012), I lost the habit of caching old packages and had deleted them before rebooting, so I couldn't do downgrade. Luckily, I also had LXDE in case of doubts and I was able to log in to search for solutions on the Internet. I found the package of plasma 4.10 in an outdated repo, but despite installing it it did not help. Other ideas did not give better results either. No matter what i did, Plasma it kept dying within seconds of loading.
I had already resigned myself to spending time in LXDE, until in the official forum of Arch Linux a user who had the same problem gave me the solution. Everything is as simple as editing the file /usr/share/autostart/plasma-desktop.desktop and replacing this line:
Exec=plasma-desktop
For this:
Exec=sleep 10 && plasma-desktop
And that's it, PlasmaDesktop it will work as usual again.
Via | Arch Linux Official Forum
Image | deviantART
Uff, with those winds .. thank goodness I haven't updated yet .. 🙂
You have 64-bit Arch. According to what they say in the forum, this only happens with the Arch of 32 bits. Someone who had a 64 upgraded and nothing happened; in fact, it even tried to cause the error but failed.
I have an arch 64b and it also happened to me, and that I just installed it again last week, but the truth is that it was so new it gave me laziness to see what happened because it had already happened before that in a major update it petara plasma, so what I did was delete ~ / .kde4 and let the system load everything again and it worked without problems ... although the one you offer sounds more interesting because it would not lose the customizations xD
Even so, if you keep hitting, it's a plan B to keep in mind ... just in case, get the respective bkup from ~ / .kde4 obviously
I did that too and for some reason it just made everything worse, it didn't directly boot the desktop and it kept me coming back to the KDM over and over.
Hello Manuel:
Could you tell me what you use to get your KDE desktop?
That is, theme, sources, background, etc ...
I really like the result you have achieved.
Thank you very much.
Hahaha, that desktop is not mine, I took it from the images that were already uploaded to the blog. I am very lazy to customize my desktops and I use a default KDE only with the wallpaper changed. xD
The truth is, I don't know who this is, because of the URL of the image it seems to be from a post from October 2012, but no idea which one. : S
Look, I already found it, it's from a deviantART user:
http://gomezhyuuga.deviantart.com/art/Gaia10-KDE-Plasma-Theme-180131334
I will add the link as a source to the article.
It's great 😀
LOL!
Well, in the end you found it.
Thank you so much!!
this is what is sometimes not understood. because if it is in a stable repo and we update these things happen. It seems that they only pack and go try ...
What an ugly desk, pink. I'm going to put it on my girlfriend the same. hehehe
Look at the answer I gave to VXF.
Well, if I have had problems with the update, systemd-journal triggered my cpu, and when I ran it, the following message appeared:
alsa-sink.c: ALSA woke us up to write new data to the device, but actually there is nothing to write!
I also solved it by Deleting the .kde4 folder and (in case it happens to someone) to improve the performance and decrease the temperature of my audio card (Alsa that occupies kde and pulseaudio for some strange reason raise their temperature) I did the following:
I logged in as root, and then I edited:
nano /etc/pulse/default.pa
and look for the line:
load-module module-udev-detect
At the end of it, we put tsched = 0, it would look like this:
load-module module-udev-detect tsched = 0
With that we tell pulseaudio not to use the timer scheduler, which is the cause of this problem. One reboot and voila!
This is where I learned the above:
http://hackingthesystem4fun.blogspot.mx/2011/04/problemas-de-sonido-con-pulseaudio-el.html
Greetings all.
Your problem looks a lot like another one that was also reported on the Arch Linux forum. There they say that deactivating Nepomuk solves it (I don't use Nepomuk):
https://bbs.archlinux.org/viewtopic.php?id=168524
Now I understand: Nepomuk and other services were reactivated when I renamed the .kde4 directory and that may have been what worsened the problem I already had.
In effect, the kde configuration is reset and works as if you had just installed it, that is, without any user configuration
I know, that's why I did it, what I didn't think was that it could generate more problems instead of solving them.
: Or I updated to 4.11 when I was in testing (if I didn't have much to do that day and I felt a bit kamikaze xD), and I haven't had the slightest problem or had to change anything that has to do with KDE.
I just saw what you put from Arch 64bit; just to contribute that in Arch of 64 if it worked without problems, at least in my case 😀!
This problem has been happening since Beta 1 of KDE 4.11 came out
When one logs in, the desktop crashes.
I use Fedora 19 with KDE 4.11 64 bits. I log in and it takes a few seconds for the desktop to show up. And by the way, don't use the Smoosh Task plasmoid, when you configure the plasmoid, it also crashes the kde desktop.
Updated smoothly thanks to your advice.
Excellent. 🙂
Chakra rules \ o /
Chakra already has 4.11 in stable?
not yet
It's in testing, but it works great 😀
I'm still doubtful whether to put the backports ppa in kubuntu and update or wait for it to come out in the official repos: s
In openSUSE Tumbleweed update, I just had an error with screen colors, go into an old kernel and go back to the current kernel and running excellent.
You also have to delete the .kde4 folder.
You notice a great speed in the applications 😀
If I'm honest, I haven't noticed anything different. 😛
If you are more fluent in opening applications and desktop effects.
I think they already fixed the bug in the notifications app that was duplicating.
It only has one bug, it is when maximizing or minimizing the applications the borders do not appear immediately, they take a little time and appear.
Does it happen on all distros or does it only happen on Arch? I say it from the title, it seems that it is for KDE in general, but in the article they only talk about Arch.
It is a general bug from KDE 4.11. So far I have known cases in Arch, Gentoo, SUSE and Fedora. In the article I only talk about Arch because I am telling my particular case and that is the distro I use.
Personally, I didn't notice any of these flaws, I've been using it since beta 1, which had the odd bug that was being corrected, but nothing about plasma. I use the 64 bit version
I wanted to try KDE (in Archlinux) but I don't know if it was that I didn't find it very much to my liking, maybe there is a Manual because I didn't like the menu that it brings by default. And I had to change the lyrics but I still felt that it was missing because I passed my old XFCE. What catches my attention ah improved a lot kde honestly last how poor was the 3.5. Personally, I think what I missed is that it has too many configurations hahaha.
I comment that I have not had any problem updating on Arch x64. All in order..
Sometimes it gives me the feeling of a little lageos but I think it was NetBeans.
I think that the ideal would be to try smaller and smaller numbers so as not to have to wait so long. regards
Yes, you're right, in fact I lowered the time to 1 second (if you are the same McKlain from the Arch forums, I see that you have an even less time); but hey, this serves as a generic solution. 🙂
The excitement and adrenaline to the maximum of the bledding edge, combined with the hyperkinetic and reckless irresponsible attitude of the Arch programmers and their users, forced guinea pigs and like cherry on the cake the monumental bugs of KDE and we have as a result the most popular extreme sport on Linux: update the system.
Aaaaaaaaaaaammmmmmmmmeeeeeeeeeeeeennnnnnnnnn.
Hahahaha, but in openSUSE tumbleweed is more stable and current 😀
I updated without problems in openSUSE tumbleweed 😉
Arch is a silk, he is impeccable when you know what you do, the problem is the FUCKING KDE
Better, to use Slackware.
If you like it, of course, but the subject is not the base system - like Kubuntu, for example - but KDE that the years go by and it continues with the same shitty problems as always doing true honor to the catchphrase that users of Windows touched in their self-respect by our arrogance when they say: "Linux is an end in itself instead of being a means, it does not serve me", and it is very, very true.
In the special case of KDE, the same thing always happens with each jump between major versions, which inevitably suggests:
1. The skinny - in some incomprehensible way - still don't know the problems the KDE suite has _with all the distros_ when upgrading between versions.
2. they don't give a damn about leaving a fine-tuned system that works well for everyday use and doesn't have these problems when upgrading
3. They are very poorly organized - which does not close me - and they lack a Quality Control and User Experience group (yes, well, all pompous and in capital letters) that ensures that these problems described by @Manuel do not happen anymore .
For something is that I am in GTK limbo, since in KDE, the problems to make it look beautiful frustrates them and in the case of Slackware, GTK applications look great thanks to the Plasma GTK package that is included, and in true, the lightness is notorious.
In Arch, I prefer to use LXDE or MATE as they are better environments for a distro that is always on the razor's edge.
Anyway: Depending on what paradigm you have, you have the freedom to choose between Windows, OSX, GNU / Linux and / or BSD.
Slack is one of my favorite distributions, but one of its critical points is precisely its update. In Arch there is great support from developers through its page and its forums so that its users do not have any problems, if they want an extreme sport update Slack but not in a virtual machine ..
Hahaha, so so !? To the Hell with Slack!
CALL ME !!
In kubuntu 13.10 nothing happened to me 😛
I just updated my 64bit archlinux, and I have not had any problems with kde 4.11… is it hardware issues? I don't think so, salu2
Most of the time the problem is this: http://newstuff.kde.org/
With what we fall into the same of Ubuntu, Windows and MacOS: everything is "fine", you will not have any problem always use the system _as it is delivered_ (claa ...), from the moment you start making changes that they were not contemplated by the developers of the system. You start to play with the entropy of stability (this added to the inherent bugs of all software) which ends in situations like the ones mentioned here.
In the particular case of KDE, the GHNS problem is when, for example, we install new themes or plasmoids or badly assembled or packaged icon packs that:
Option 1) They seem to work normally but the reality is that it is defective software with bugs and for some reason they run in the version that we are using of KDE, such as KDE's own errors that allow its execution and that when corrected in versions later and as GHNS is already installed, it directly exploits KDE.
Option 2) the new version of KDE ships with a regression or with a new known bug that, as it affects only 3% of possible users, decides to kick their fix forward: well gentlemen, we are that 3%, we are affected by that dark regression no one can find out why KDE X subsystem fails
Option 3) We install a GHNS that seems to work fine until we log out, from that moment on it will be an odyssey to have a usable KDE desktop again so we end up creating a new user, changing permissions, moving data, etc. etc. (who did not go through this trauma ... more than once !?)
In the best of cases this type of error is solved by moving / deleting / renaming the file (s) ~ / .kde {4} / share / config / plasma {rc, *}, in the worst of the In some cases, we end up flipping the machine, gnu + linux, free software and the whole comic against the wall, and luckily we don't have an ax on us because otherwise we film The New Texas Massacre for free. (I have not reached that far, if to catch terrible rages but I know someone who literally flipped his laptop against the wall when something similar happened to him).
Anyway, it's software, worse still, it's KDE: a lottery.
And that is what makes KDE devs much more putable, because KDE is really a marvel, when it works it is a little clock, but they care ZERO / NADA / ZERO dedicating themselves to stabilize the system and close bugs that have been reported for years, they have addiction to developing new things and having others take charge of making them work.
I have been working on eOS for 4 days -which in fact I am taking advantage of to know in depth- waiting for the new Chakra ISO after a violent crash that caught me without backups of / ni ~ / .kde4.
Never again will Backup be my middle name from now on.
They will have updated and optimized nepomuk but it was my turn to activate it to test it and cpu & ram to the max… .. It is true that they are like 700 gb to update… Akonadi if I use it and without problems.
700 GB ?! o_O
Well, Tete foreveralone reporting that since Funtoo x86_64 I had no problem updating, 0 problems, I didn't even have to delete .kde4 or anything: v, however I know 1 Gentoo user who had problems, and several Archers, and yes, I have a folder where I throw all the shit that I don't want to throw in the trash, and the new version of dolphin does not take anything to open that folder full of files compared to the previous one, nepomuk is less configurable, now you cannot set how much ram Use it, but it's going soooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo good
Hdp, using Funtoo, I envy you !!!
Well not so much. Of the source-based ones I played a week with Source Mage, I used a little more Gentoo and finally I flirted with Funtoo but in the end I couldn't bear to keep compiling everything continuously.
However Funtoo… ahh, the distribution between source-based distributions!
If one day the ratio of processor amount needed to compile * compilation speed / hw resources and power needed to compile is somewhat reasonable headlong to Funtoo without hesitation.
Enjoy your shiny new KDE 4.11 on Funtoo! (guacho!)
The same happened to me. But I fixed it with Alt + F2, typing plasma-desktop and changing the plasma theme. For some reason the default theme hangs at startup. At least in my case with 32-bit Arch.
Well, I updated just two hours ago and everything works normal, better said, better. 😀
Is that in the end you left wheezy for good?
In my case this fix has not worked for me, I continue with the error when starting, at the moment every time I start my KDE I do ALT + F2 and I run plasma-desktop to recover the desktop 🙁
Hello, how are you, I liked the desk that you put in the image, how did you make it look like this?
good contribution
I recently installed OpenSuse 13.1 with Kde Desktop but after updating a bit ...
It gave me a problem because the desktop does not start the same as before
How could i solve it
Someone already happened to him, could you help me
Send me a message if you know how, urge me
and thanks
I just installed opensuse 13.1 64 bits and was updating a bit and then when I rebooted the normal desktop was no longer there. I tried what is in this blog but it did not work for me
I would like to know how to fix it.