April 2024 - openSUSE Support - openSUSE Mailing Lists

PackageKit
by Ianseeks 12 Apr '24

12 Apr '24

Hi Is packagekit needed on tumbleweed? Since the upgrade to plasma 6, it runs as soon as I log in, where can i turn it off because I can't do a zypper dup until its finished. I can't find any reference to it in yast (cron) or systemsettings? Not had any emails for a few days now, is the system down? regards Ian openSUSE Tumbleweed 20240404 kwin 6.0.3 kmail2 6.0.1 (24.02.1) - akonadiserver 6.0.1 (24.02.1) - Kernel: 6.8.2-1- default - kernel-firmware-radeon 20240322

6 7

Problem with nvidia module?!
by Jörn Dreyer 12 Apr '24

12 Apr '24

Hello, since the last weekend i'm experiencing problems with my laptop that has an NVIDIA 1650 Ti together with an integrated AMD Radeon RX 6. The systems starts up normaly after a power cycle. I can login but now the problems start: 1) The start of the graphical desktop (KDE) is very slow. It takes about 2 minutes. 2) Only the internal screen comes up, the external monitor goes into power saving mode. 3) Sometimes the mouse moves very slowly, so the system is unusable. The last day's it helped to reinstall the nvidia driver but today this did not solve the problem. In the log file I found errors like this: [[drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset. Error code: -22 [[drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0 After the last update I run rpmconfigcheck and fixed the outstanding changes. But the problem did not go away. Did anybody observe similar problems? Regards Jörn

1 1

Why?: zypper "Will try to download it." for a package on the / filesystem
by Felix Miata 10 Apr '24

10 Apr '24

EXAMPLE scenario: # ll total 574 drwxrwxr-x 2 root root 1024 Apr 9 21:13 . drwx------ 23 root root 6144 Apr 9 21:11 .. -rw-rw-r-- 1 moz vtt 579202 Mar 19 21:56 filecommander-2.50-vgit_1842_tumbleweed.x86_64.rpm # inxi -S System: Host: p5bse Kernel: 6.6.24-1-longterm arch: x86_64 bits: 64 Console: pty pts/0 Distro: openSUSE Tumbleweed 20240407 # zypper -v --no-refresh in ./filecommander-2.50-vgit_1842_tumbleweed.x86_64.rpm Autorefresh disabled. Verbosity: 2 Non-option program arguments: './filecommander-2.50-vgit_1842_tumbleweed.x86_64.rpm' './filecommander-2.50-vgit_1842_tumbleweed.x86_64.rpm' looks like an RPM file. Will try to download it. Initializing Target Loading repository data... Reading installed packages... Selecting 'filecommander-2.50-vgit_1842_tumbleweed.x86_64' from repository 'Plain RPM files cache' for installation. Resolving package dependencies... Force resolution: No The following package is going to be upgraded: filecommander 2.50-vgit_1829_tumbleweed -> 2.50-vgit_1842_tumbleweed 1 package to upgrade. Overall download size: 565.6 KiB. Already cached: 0 B. After the operation, additional 8.3 KiB will be used. Backend: classic_rpmtrans Continue? [y/n/v/...? shows all options] (y): n # Why does zypper "download" a package on the / filesystem before installing it? Does it really "download" it? If so, what does "download" mean to a zypper transaction? Would the answer differ if the rpm is on an nfs mount? Can one configure a repo pointing to . to dispense with this apparently inexplicable activity? Is this a bug? -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata

2 2

symbol lookup error in fwupdmgr something so... tumbleweed slowroll update
by cagsm 08 Apr '24

08 Apr '24

Support, just updated a tumbleweed slowroll machine, and now fwupmgr shows a symbol lookup error in /ib64/libfwupd.so.2 - undefined symbol: g_once_init_leave_pointer fwupd: 1.9.15 release 1.1.3.1 fwupd has been installed in the end of march, but fwupd-efi and fwupd-bash-completion has been updated installed today. fwupdate just worked fine (refresh) just a moment ago before i zypper dup to the latest slowroll and rebooted thereafter. ty

4 10

Anything changed in rules for nft?
by Freek de Kruijf 05 Apr '24

05 Apr '24

I have my own set of nft rules for a special purpose. This set worked perfect since 2021. However today I am using the newest Tumbleweed and I get error messages when starting this set with nft. The set is: add table ip filter add chain ip filter INPUT { type filter hook input priority 0; policy drop; } add chain ip filter FORWARD { type filter hook forward priority 0; policy drop; } add chain ip filter OUTPUT { type filter hook output priority 0; policy accept; } add chain ip filter reject_func add rule ip filter INPUT iifname "lo" counter accept add rule ip filter INPUT ct state established counter accept add rule ip filter INPUT ip protocol icmp ct state related counter accept add rule ip filter INPUT udp dport 5353 pkttype multicast counter accept add rule ip filter OUTPUT oifname "lo" counter accept add rule ip filter reject_func ip protocol tcp counter reject with tcp reset add rule ip filter reject_func ip protocol udp counter reject add rule ip filter reject_func counter reject with icmp type prot-unreachable The error message is: /etc/network/ruleset-init.nft:8:26-33: Error: Could not process rule: No such file or directory add rule ip filter INPUT ct state established counter accept ^^^^^^^^ /etc/network/ruleset-init.nft:9:43-50: Error: Could not process rule: No such file or directory add rule ip filter INPUT ip protocol icmp ct state related counter accept ^^^^^^^^ Are there any changes in the syntax of nft rules? -- fr.gr. member openSUSE Freek de Kruijf

2 3