Comments

22 Comments

So, do you know why I'm here?

Let me to infor you: AFTER the last update my screen looks like a 950x600 on a fullhd monitor.

1) I though about an nvidia driver issue, then tried to launch the previous kernel 4.10 (instead of the last one, 4.11)

2) same results. Then in the terminal i tried "glxinfo -B" and discovered that instead of the nvidia driver I was on Gallium

3) Then I googled for a solution and found this: https://devtalk.nvidia.com/default/topic/996408/quadro-k620-on-fedora-25-unable-to-load-the-nvidia-drm-/?offset=10 At some point someone posted that a workaround is to put selinux in permissive mode

4) I tried and it works

5) From the same post I jump here just to discover that the issue with the nvidia driver was WELL KNOWN and beautifully ignored.

What was the purpose? Do you want so much a giant middle finger in your face?

"This update has been pushed to stable".... yes, from a bunch of idiots.

LGTM

LGTM

So, what will happen here? Are we waiting to jump on 5.6.3 directly or what?

LGTM

LGTM

LGTM

It works.

LGTM

works for me as well

It works.

It works.

Works for me too.

Mmm... again the package plasma-desktop-5.4.1-2.fc22 cannot be installed due to broken dependencies, in detail: Error: package plasma-desktop-5.4.1-2.fc22.x86_64 requires libKF5Baloo.so.1()(64bit), but none of the providers can be installed.


[valerio@valerio-casa ~]$ dnf provides libKF5Baloo.so.1 Last metadata expiration check performed 19 days, 0:20:18 ago on Wed Aug 26 00:53:18 2015. kf5-baloo-libs-5.9.0-1.fc22.i686 : Runtime libraries for kf5-baloo Repo : fedora kf5-baloo-libs-5.9.2-1.fc22.i686 : Runtime libraries for kf5-baloo Repo : updates


However I cannot install that package because: Error: cannot install both kf5-baloo-libs-5.9.2-1.fc22.x86_64 and kf5-baloo-libs-5.13.0-1.fc22.x86_64


If I try to remove the last of those, it pull out a lot of other packages. Any workaround or suggestions?

Plasma 5.4 works good in my F22. Just two notes: 1) I manually downloaded the package sddm-breeze because was not installed automatically. I discovered that when tried to modify the login screen settings. 2) plasma-pa was not automatically installed. I guess it was intentional (maybe some user of ALSA?), but I put it in the notes as well.