You are not logged in.
Can you try downgrading plasma-framework and kactivities-frameworks to 5.2 (one by one) to see which one is the culprit? The kio-extras conflict is already fixed in AUR and is unrelated to this (kio-trash was moved from kio-extras to kio)
Last edited by arojas (2014-10-09 06:23:25)
Offline
now i have a black desktop in which i can launch applications with krunner (alt+f2) but no wallpaper, no panels and nos widgets.
(sorry for my bad english)
you can just launch dolphin or any file-manager ( like thunar or anything else) to show your desktop folder, and look for hidden files (alt+. for dolphin, ctl+h for thunar) or simply run a terminal emulator like konsole.
laptop LENOVO Ideapad Z570 i7 / 6GO RAM/GeForce 540
ARCHLINUX+KDE frameworks 5.3 (working great !)
Offline
Short questions:
I'm a newbie to KDE5 and using Gnome3 at the moment. As I want to try out KDE5 (no rush) i guess it is best to wait until it is ready.
But when will that be. Not in terms of arch-pkgs, but KDE in general. I understand that there a various components interacting, but i struggle to sort out how it is working. As far i understood that kde-frameworks is already out and stable (5.0/5.1/5.2). Also plasma is already out and stable (5.02). Applications are not named according to the rest but are based on year.month.
Does it make sense to switch before they run on plasma5/kf5?
And: is the wiki about kde/kde5 still up to date?
Thx
Offline
The thing is with KDE5 that I think nobody from devs really wants it. They argue about less stability with Plasma 5. For now plasma 5 is not even in kde-unstable so it is hard to detect when Plasma 5 will be in at least in testing but I guess it won't be soon.
Offline
Can you try downgrading plasma-framework and kactivities-frameworks to 5.2 (one by one) to see which one is the culprit? The kio-extras conflict is already fixed in AUR and is unrelated to this (kio-trash was moved from kio-extras to kio)
Results:
plasma-framework 5.2.0-1 and kactivities-frameworks 5.2.0-4 = Works
plasma-framework 5.3.0-1 and kactivities-frameworks 5.2.0-4 = Broken
plasma-framework 5.2.0-1 and kactivities-frameworks 5.3.0-1 = Works
clfarron4 wrote:now i have a black desktop in which i can launch applications with krunner (alt+f2) but no wallpaper, no panels and nos widgets.
(sorry for my bad english)you can just launch dolphin or any file-manager ( like thunar or anything else) to show your desktop folder, and look for hidden files (alt+. for dolphin, ctl+h for thunar) or simply run a terminal emulator like konsole.
That doesn't answer my question in response to @Jodell's suggestion.
Also, I don't remember saying that quote. You, @Tuxador, said that.
Last edited by clfarron4 (2014-10-09 08:48:28)
Claire is fine.
Problems? I have dysgraphia, so clear and concise please.
My public GPG key for package signing
My x86_64 package repository
Offline
Although the official wiki for pacman suggests to file a bug report, I thought the forum could give me some ideas as I'm pretty much a newbie to Arch and KDE.
I've been using KDE4 for about a month and I decide to try out plasma frameworks 5 by installing kf5, kf5-aids and plasma-desktop (used yaourt)
Everything worked absolutely fine until i did a yaourt -Syua and got a list of updates followed by this:
kio: /usr/bin/ktrash5 exists in filesystem
kio: /usr/lib/qt/plugins/kcm_trash.so exists in filesystem
kio: /usr/share/kservices5/kcmtrash.desktop exists in filesystem
kio: /usr/share/kservices5/trash.protocol exists in filesystem
Errors occurred, no packages were upgraded.
(pacman -Syu also gave the same output)
Stupid that I was, I did --force update on pacman -Syu (I know that's not to be done and I won't next time ) and the next time I booted up I got the following screen:
Except the panels and the desktop every application works just fine. Even desktop effects and other effects work smoothly. Nothing crashes as such. But the panels and widgets are missing as seen in the screenshot.
I definitely have done wrong in using --force but can somebody help me as to what I should do?
I re-installed kdebase (KDE4) which seemed to work fine except a few launchers that wouldn't show up properly on the panels.
So I went ahead and re-installed kf5, kf5-aids and plasma-desktop again. That did not help at all. The problem remains the same. I have also tried resetting KDE (renaming .kde4 etc), I've tried rebuilding cache as suggested on KDE Archwiki (using kbuildsycoca4 --noincremental) .
I have other Desktop Environments that remain unaffected.
Any help would be great. Please let know if output of any command is needed. Thanks in advance
I'm ready to learn anything good that you're ready to teach me:)
Offline
Well, I can tell you that I didn't force the installation of anything and I'm experiencing the same thing after today's update, I'm still not sure which package caused it.
Last edited by LucetLux (2014-10-09 14:15:07)
Offline
So anything that you did or would consider doing to fix it?
I'm ready to learn anything good that you're ready to teach me:)
Offline
Already under discussion: https://bbs.archlinux.org/viewtopic.php?id=184439
Offline
Here's a thread that I started (before I saw this discussion): Let's keep it sorted there: (Or let me know if I should delete it)
https://bbs.archlinux.org/viewtopic.php?id=188113
moderator comment: Note that I have merged these threads
Last edited by ewaller (2014-10-09 14:57:48)
I'm ready to learn anything good that you're ready to teach me:)
Offline
Downgrade plasma-framework to 5.2.0 and hold the update for now. Plasma 5.1 will be released on Tuesday and works fine with KF 5.3
Offline
Moderator: Merging threads.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Online
Downgrade plasma-framework to 5.2.0 and hold the update for now. Plasma 5.1 will be released on Tuesday and works fine with KF 5.3
Thanks that worked!
Now I have a different issue that I was experiencing before that update broke plasmashell, I wanted to set up my second monitor and I noticed that plasma 5 doesn't have a config module for that, so I tried using kscreen from kde4, this proved to be a mistake, as when I logged back in I noticed some UI elements looked "inflated", even after removing kscreen, cleaning the config, reinstalling kde5 packages I don't seem to be able find a way to fix this.
The problem is that as I said some UI element look bigger, as if they were at a higher DPI or something like that, but fonts are regular sized, it is kind of weird, it is also very noticeable on the SDDM greeter, in which the buttons look gigantic, I can't be entirely sure if this was caused by kscreen, but it started happening right after using it.
Offline
Downgrade plasma-framework to 5.2.0 and hold the update for now. Plasma 5.1 will be released on Tuesday and works fine with KF 5.3
Thanks. This works. Although I've noticed that I cannot right-click on the desktop anymore and am unable to run any application through Krunner. There's a little tearing that I've observed. Disabling vsync helps although there's a little sluggish movement when a lot of applications are open. I guess all these issues are related to version differences. But everything else is pretty stable for now. Expecting all of this to work properly with plasma 5.1 (as is quoted by arojas). Thanks again.
I'm ready to learn anything good that you're ready to teach me:)
Offline
Everything worked absolutely fine until i did a yaourt -Syua and got a list of updates followed by this:
kio: /usr/bin/ktrash5 exists in filesystem kio: /usr/lib/qt/plugins/kcm_trash.so exists in filesystem kio: /usr/share/kservices5/kcmtrash.desktop exists in filesystem kio: /usr/share/kservices5/trash.protocol exists in filesystem Errors occurred, no packages were upgraded.
This bit is because of those files moving from kio-extras to kio, and actually didn't cause the black desktop. It is the plasma-framework package that is causing the broken desktop.
Claire is fine.
Problems? I have dysgraphia, so clear and concise please.
My public GPG key for package signing
My x86_64 package repository
Offline
thank you for the temporary fix, can't wait for tueday !!!
laptop LENOVO Ideapad Z570 i7 / 6GO RAM/GeForce 540
ARCHLINUX+KDE frameworks 5.3 (working great !)
Offline
More on my issue, http://puu.sh/c5Zjc/165fe8ac01.png , as you can probably see the icons look really big, whereas the text is normal, the same goes for the customization button on the top right corner, the spacing between the icons in the notifications area is also inflated, and what is less noticeable, the gray lines marking the different applications on the taskbar are also a lot thicker. I have since my last post completely removed every single kde5 package, deleted all the config I could find related to kde both in my local folder as well as in /usr/share and I still couldn't get this fixed.
Edit: Okay, I found that if I restart plasmashell it goes back to normal, until I log out and log back in again, I'm kind of confused.
Last edited by LucetLux (2014-10-09 22:55:00)
Offline
nskool wrote:Everything worked absolutely fine until i did a yaourt -Syua and got a list of updates followed by this:
kio: /usr/bin/ktrash5 exists in filesystem kio: /usr/lib/qt/plugins/kcm_trash.so exists in filesystem kio: /usr/share/kservices5/kcmtrash.desktop exists in filesystem kio: /usr/share/kservices5/trash.protocol exists in filesystem Errors occurred, no packages were upgraded.
This bit is because of those files moving from kio-extras to kio, and actually didn't cause the black desktop. It is the plasma-framework package that is causing the broken desktop.
Yeah...I kinda got that after your post #80. Thanks for explaining again though. Again a question: Shouldn't such movements be handled internally. What caused pacman to show those conflicts and fail the updates? (Meaning what part of the move (kio-extras to kio) was pacman not aware of?)
Last edited by nskool (2014-10-09 21:41:54)
I'm ready to learn anything good that you're ready to teach me:)
Offline
Again a question: Shouldn't such movements be handled internally. What caused pacman to show those conflicts and fail the updates? (Meaning what part of the move (kio-extras to kio) was pacman not aware of?)
kio-extras is in the AUR, kio is in extra. That's why pacman can't see it.
Claire is fine.
Problems? I have dysgraphia, so clear and concise please.
My public GPG key for package signing
My x86_64 package repository
Offline
kio-extras is in the AUR, kio is in extra. That's why pacman can't see it.
Oh...right...got it now...thanks a lot.:)
I'm ready to learn anything good that you're ready to teach me:)
Offline
From the upstream developers:
[10 Oct 14 16:15] <arojas> Warning: corona package invalid
[10 Oct 14 16:15] <notmart> some internal packages became plugins...
[10 Oct 14 16:15] <notmart> here we go
[10 Oct 14 16:15] <arojas> Invalid home screen package
[10 Oct 14 16:16] <notmart> yeah, they used to be hardcoded inside libplasma/libplasmaquick, now are plugins from plasma-framework (and yeah, gives pain)
[10 Oct 14 16:16] <notmart> with just the plugins built from 5.1 and transplanted, it should work, but yeah difficult to package
[10 Oct 14 16:17] <arojas> so probably better to just wait for 5.1
[10 Oct 14 16:17] <notmart> (that's the effect of having an unrelased private library in the middle, but mea culpa on that)
[10 Oct 14 16:17] <notmart> yes
[10 Oct 14 16:17] <notmart> sorry about that
So there seems to be no easy way to fix this in 5.0.x, add plasma-framework to IgnorePkg until Plasma 5.1 is out.
Offline
Will it be possible to install KDE 5 next to KDE 4? After plasma 5.1 release for example?
Offline
Will it be possible to install KDE 5 next to KDE 4? After plasma 5.1 release for example?
Next to KDE4 workspace, no. Next to KDE4 applications, yes.
Offline
fatino wrote:Will it be possible to install KDE 5 next to KDE 4? After plasma 5.1 release for example?
Next to KDE4 workspace, no. Next to KDE4 applications, yes.
Edited: with further reading I figured out the answer to my question and so removed it.
There is a feature which is set to go in KDE Plasma 5.1 which I would find very useful. I'm probably going to try to switch to Plasma 5.1 once it is released.
Last edited by davidm (2014-10-11 03:14:38)
Offline
About my issue, if somebody cares, it fixed itself, I have absolutely no idea how or why, it wasn't an update, it wasn't me deleting settings or reinstalling stuff, it just fixed itself, just like that... I love it when that happens.
Offline