So last night the updater app said something about updating some packages, little did I know that about 2000+ packages were being installed, somehow I messed up the repos and I jumped from Leap 42.3 to Tumbleweed.
Now I’m having some issues.
I can only boot on a previous kernel 4.4.92-31-default correctly, otherwise the latest one installed by Tumbleweed 4.14.0-1.8 crashes at boot with a ACPI error. I also have a nVidia GT210 graphics card and so I use the nvidia G03 driver.
The icons on new KDE Plasma are missing on Desktop and the text under them is jagged. Please see attached screenshots.
Can you guys help me sort my repos and correctly set up my machine.
Here are my repos and other details
Repository priorities are without effect. All enabled repositories share the same priority.
# | Alias | Name | Enabled | GPG Check | Refresh
1 | Packman_Tumbleweed | Packman Tumbleweed | Yes | (r ) Yes | Yes
2 | Python_42.3 | Python_42.3 | No | ---- | ----
3 | Tumbleweed NON-OSS | Tumbleweed NON-OSS | Yes | (r ) Yes | No
4 | Tumbleweed OSS | Tumbleweed OSS | Yes | (r ) Yes | No
5 | Tumbleweed Update OSS | Tumbleweed Update OSS | Yes | (r ) Yes | No
6 | download.opensuse.org-oss | Main Repository (OSS) | No | ---- | ----
7 | download.opensuse.org-oss_1 | Main Update Repository | No | ---- | ----
8 | http-download.opensuse.org-03a89f56 | isv:ownCloud:desktop | No | ---- | ----
9 | http-download.opensuse.org-31685a96 | openSUSE:Factory | No | ---- | ----
10 | http-download.opensuse.org-d5d4464c | openSUSE:Leap:42.3:Update | No | ---- | ----
11 | http-download.opensuse.org-f11bf96c | home:pbek:QOwnNotes | No | ---- | ----
12 | nVidia_Tumbleweed | nVidia Tumbleweed | No | ---- | ----
13 | nvidia | nvidia | Yes | (r ) Yes | Yes
So, first off, what do you want to use, Tumbleweed, or 42.3?
Be aware that the nvidia support using the TW repositories is G04 only.
If you want to stick with 42.3 then, boot from the previous kernel, change all repositories back to those for 42.3, log out and then perform a “zypper dup” from the command line; that should restore your 42.3 system.
If you want to use TW then, boot from the previous kernel, remove the nvidia drivers so you are using the OSS drivers. Ensure only TW repositories are enabled, excluding nvidia, log out and then perform a “zypper dup” from the command line; that should give you a working TW system.
For TW any future updates you perform must be by “zypper dup” from the command line, no other way.
That would largely depend upon the video card and applications you are using, it’s a hard one to answer. Ask half a dozen different people and you’ll probably get different replies… My own experience:
I’m running an older 8600GTS card using the Nouveau OSS drivers and don’t have any issues.
I also have another machine with a newer GT710 card, that also worked OK with the OSS driver, although I’m currently using the G04 driver with it as the card runs a few degrees C cooler.
The general consensus seems to be if it’s a newer card and applications are graphics intensive, the proprietary drivers are better.
If you do use the OSS drivers then hardware acceleration is provided by a separate package “Mesa-dri-nouveau”, this is marked as “experimental” with quite a “scary” warning. Again, I’m using it with the 8600GTS without problem. I’d be inclined to not use it initially, then add the package and see how it goes, only removing it if you think it’s causing problems. Without it any openGL rendering will be done by software emulation, thus increasing the CPU utilisation.
With regard to the repositories you listed in the first post, use only 1, 3, 4, and 5 when you perform the zypper dup. If you need the owncloud and qownnotes repos ensure they’re compatible with TW and add them back after you have a working TW installed.
On Fri, 24 Nov 2017 14:36:02 +0000, robertot5 wrote:
> I would like TW, I think!
> Are there any issues or major differences between the nvidia and the OSS
> nvidia GPU driver?
Just as a reference point: I have a box with an Nvidia GTX630 - similar
hardware to yours - that ran with G03 Nvidia drivers. It’s solid with
the nouveau drivers, even the Mesa-dri-nouveau works well despite the
Did you solve this issue? It happens to me as well in Tumbleweed.
When I call kde SystemSettings, a window without icons shows up. I can regenerate the icons by clicking on “icons”
and “Apply”, but they last only for that session. When I quit systemSettings, the icons are gone again. Any ideas?
Thanks, but it makes no difference. I’m running kde5 but not plasma. I use another windowmanager.
When I launch KDESystemSettings it appears with no icons. Well… there is ONE icon only, all other services show up with their
names only. I may click on icons and apply the desired icon theme (the system thinks it’s applied, “apply” is greyed out, but
I can choose another icon theme and click “apply”), but they disappear again when I kill KDESystemSettings.
Any help is welcome.
Ok, so you don’t use Plasma, but what do you mean with “kde5”?
Some KDE applications?
I use another windowmanager.
And which one?
Why are you asking in this thread then, which was about problems with Plasma?
When I launch KDESystemSettings it appears with no icons.
That’s “normal” if the icons are not in the used icon theme.
Qt5 tries to adapt to the used desktop’s settings. If you run it on an unsupported desktop, it probably uses “hicolor” which doesn’t contain them.
It may help to install qt5ct and configure another icon theme there.
But if you don’t use Plasma, systemsettings5 will be not very useful to you either, as that mainly contains the (Plasma) desktop’s settings…
The same applies to other KDE and Qt5 applications though.
When I did a zypper dup today, the same thing happened as the last time I did zypper dup. I was able to fix it before, and the same fix worked today. For some reason, my mesa libraries were downgraded–so I was prepared. Is there a reason thus happened again?