- openSUSE Support

Repositories and priority
by Marco Calistri 13 Feb '24

13 Feb '24

Hello! File /usr/lib64/gstreamer-1.0/libgstresindvd.so from install of gstreamer-plugins-bad-1.22.9-3.1.x86_64 (Repository principale (OSS)) conflicts with file from package gstreamer-plugins-bad-orig-addon-1.22.6-33.2.x86_64 (@System) File /usr/lib64/gstreamer-1.0/libgstsiren.so from install of gstreamer-plugins-bad-1.22.9-3.1.x86_64 (Repository principale (OSS)) conflicts with file from package gstreamer-plugins-bad-orig-addon-1.22.6-33.2.x86_64 (@System) How should I avoid to receive this kind of warnings during the update process? sudo zypper lr -E -P # | Alias | Name | Enabled | GPG Check | Refresh | Priority ---+----------------------------------+-------------------------------------------+---------+-----------+---------+--------- 3 | Packman | Packman | Sì | (r ) Sì | Sì | 80 6 | download.opensuse.org-tumbleweed | Repository principale degli aggiornamenti | Sì | (r ) Sì | Sì | 90 1 | Google_Chrome_repository | Google_Chrome_repository | Sì | (r ) Sì | Sì | 99 2 | Hamradio | Hamradio | Sì | (r ) Sì | Sì | 99 4 | download.opensuse.org-non-oss | Repository principale (NON-OSS) | Sì | (r ) Sì | Sì | 99 5 | download.opensuse.org-oss | Repository principale (OSS) | Sì | (r ) Sì | Sì | 99 15 | nordvpn | nordvpn | Sì | (r ) Sì | Sì | 99 20 | skype-stable | skype (stable) | Sì | (r ) Sì | Sì | 99 I wish to keep Packman at higher priority, now I don't know what OSS Vs. @System means in the warning. Could you please be so kind to explain? Thanks! -- Marco Calistri Build: openSUSE Tumbleweed 20240209 Kernel: 6.7.2-1-default - XFCE: (4.18.3) Uptime: 10:00:01 up 5 days 19:50, 1 user, carico medio: 1,90, 2,46, 1,91

5 9

openssl error during TW update.
by Stakanov 08 Feb '24

08 Feb '24

Did anybody see this too? What to do after dup finished, for now we ignored. (Machine is not in my hands BTW). error: unpacking of archive failed on file /etc/ssl/engdef.d;65c51121: cpio: File from package already exists as a directory in system error: openssl-3-3.1.4-3.2.x86_64: install failed error: openssl-3-3.1.4-2.1.x86_64: erase skipped ( 596/4177) Installazione di: openssl-3-3.1.4-3.2.x86_64 ........................................................................................... [errore] Installazione di openssl-3-3.1.4-3.2.x86_64 fallita: Errore: Subprocess failed. Error: RPM non riuscito: Il comando è terminato con stato 1.

2 2

btrfsck error found:
by -pj 07 Feb '24

07 Feb '24

Hi, passing: btrfsck --check --force /dev/mapper/system-root finds the following errors in the filesystem. ERROR: errors found in fs roots found 117460205568 bytes used, error(s) found total csum bytes: 110505304 total tree bytes: 1844690944 total fs tree bytes: 1645625344 total extent tree bytes: 60227584 btree space waste bytes: 440188035 file data blocks allocated: 291454246912 referenced 283273138176 Thinkcentre-M57p:~ # I am wondering how to proceed with this.

4 9

Musescore does not play score anymore
by Freek de Kruijf 06 Feb '24

06 Feb '24

I can edit a song with musescore OK. When entering a note the note is not played anymore nor gives pressing the menu item to play the score any sound. Only the line indicating the position in the score appears, but it does not move. I use openSUSE Tumbleweed fully updated. -- fr.gr. member openSUSE Freek de Kruijf

2 1

How to use maven plugin package
by Obs Geeko 06 Feb '24

06 Feb '24

Hello, Newbie question. I saw in TW repo there are some maven plugin packages, for example: - maven-resources-plugin - maven-compiler-plugin - maven-jar-plugin - maven-surefire-plugin May I ask how to use them? After installing these package, I used `mvn package -o` in my simple maven project, trying to use these local packages, but got error: "The POM for org.apache.maven.plugins:maven-resources-plugin:jar:3.3.1 is missing, no dependency information available". It seems it tried to use remote maven repo. ` # cd /usr/share/maven/lib/ # ln -s ../../java/maven-resources-plugin/maven-resources-plugin.jar maven-resources-plugin.jar ` also doens't work. May I ask how to use package instead of remote repo ones? Thank you.

2 1

Problem: nothing provides 'group(tor)'
by -pj 06 Feb '24

06 Feb '24

Having this problem: :~>zypper dup [sudo] password for root: Refreshing service 'NVIDIA'. Refreshing service 'openSUSE'. Loading repository data... Reading installed packages... Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... 2 Problems: Problem: nothing provides 'group(tor)' needed by the to be installed torsocks-2.4.0-1.5.x86_64 Problem: nothing provides 'group(tor)' needed by the to be installed tor-0.4.8.10-1.2.x86_64 Problem: nothing provides 'group(tor)' needed by the to be installed torsocks-2.4.0-1.5.x86_64 Solution 1: deinstallation of torsocks-2.4.0-1.4.x86_64 Solution 2: keep obsolete torsocks-2.4.0-1.4.x86_64 Solution 3: break torsocks-2.4.0-1.5.x86_64 by ignoring some of its dependencies Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c/d/?] (c): Is this something that RPM 4.19 is related to in their discussion?

2 1

Tumbleweed, since last update SDDM password input problem (and only there)
by Stakanov 05 Feb '24

05 Feb '24

Hello, I had a hard time to login until I found out the following goes on in my system: In the input mask, the letter is shown, but it is evidenced, if I input a second letter, it will cancel the first input. So I have to: input the letter, advance with the right arrow cursor to de-select, then input the second then the arrow, and so on .....This is limited to the SDDM password field only. This since the last update of 4000 packages. Any clue what could cause this behavior? I am using fcitx in KDE Plasma but this should not influence SDDM. I cannot imagine any reason either, why the rpm update should have influenced the SDDM password input. Hence I am puzzled which function I might have activated unwittingly and how to get rid of it. Thank you for every feedback.

1 0

nice surprise - old nvidia (G04) working with kernel 6.7 on tumbleweed
by Matthew 03 Feb '24

03 Feb '24

Hello, Just thought I'd share that the old (legacy) nvidia drivers/kernel modules (G04 version, see list below for more info) are building, loading, and working (for me) on Tumbleweed using the 6.7.* kernel series. So if you are still running legacy nvidia hardware and have locked your kernel into a version from the 5.9 series (because the 6.6.series were known not to work), you might give the latest version a try (6.7.2-1-default, as of when I wrote this). %> zypper se -i nvidia ... i+ | nvidia-computeG04 | NVIDIA driver for computing with GPGPU | package i+ | nvidia-gfxG04-kmp-default | NVIDIA graphics driver kernel module for GeForce 400 series and newer | package i+ | nvidia-glG04 | NVIDIA OpenGL libraries for OpenGL acceleration | package i+ | x11-video-nvidiaG04 | NVIDIA graphics driver for GeForce 400 series and newer | package Hope this is useful info, Matthew

2 1

Blank Login window fields and descriptors:
by -pj 30 Jan '24

30 Jan '24

Hi, after an update to Tumbleweed snapshot 20240125, the Login window entry field key character input and identification field listings are blank. In fact everything is blank for that matter including the user image. KDE Plasma Version: 5.27.10 KDE frameworks Version: 5.114.0 Qt Version: 5.15.12 Kernel Version: 6.7.1-1-pae (32-bit) Graphics Platform: X11 - Here's a picture of the current login window: https://paste.opensuse.org/pastes/c19b6215f700 Any thoughts on what or which package(s) caused this issue? Still able to login after entering password. -Regards

15 58

Where to report this problem, KDE or Bugzilla?
by -pj 30 Jan '24

30 Jan '24

Hi, After suspending then unsuspending the machine here. Prior open application titlebars are faded (grey in color) and path/location information on the title bar (left side) are a /barely/ legible faded grey in color as well. In order to see the active titlebar description correctly again, I have to open a new instance of the application or any application for that matter. This is going on with applications ranging from Kate to Firefox to KeepassXC. What is going on here? I am using only the default themes and colors found in the KDE desktop appearance options. Minimize and maximizing the window/s itself has no correction to the titlebars display. -Thanks

2 3