August 2024 - openSUSE Users - openSUSE Mailing Lists

Tumbleweed Gnome-sudoku: error Vulkan: Loader Message: setup_loader_term_phys_devs
by David C. Rankin 16 Aug '24

16 Aug '24

Devs, All, After the latest TW dup, there is an error written to stderr from gnome-sudoku: (gnome-sudoku:38804): Gdk-CRITICAL **: 01:19:21.227: Vulkan: Loader Message: setup_loader_term_phys_devs: Failed to detect any valid GPUs in the current config Anybody have a clue what Vulkan is looking for that it isn't finding -- and how do I fix it? Is this mesa related? -- David C. Rankin, J.D.,P.E.

2 8

Can't install hw-probe on OpenSuSE 15.4
by Marc Chamberlin 16 Aug '24

16 Aug '24

I want to install an run hw-probe on my OpenSuSE 15.4 system and ran into troubles. So I am in need of a guru to help me. Here is what I dod and the responses I got - quasar:/etc/X11 # zypper addrepo https://download.opensuse.org/repositories/hardware/openSUSE_Leap_15.4/ hardware Adding repository 'hardware' ....................................................................[done] Repository 'hardware' successfully added URI : https://download.opensuse.org/repositories/hardware/openSUSE_Leap_15.4/ Enabled : Yes GPG Check : Yes Autorefresh : No Priority : 99 (default priority) Repository priorities are without effect. All enabled repositories share the same priority. quasar:/etc/X11 # zypper install hw-probe Error building the cache: [hardware|https://download.opensuse.org/repositories/hardware/openSUSE_Leap_…] Valid metadata not found at specified URL History: - [hardware|https://download.opensuse.org/repositories/hardware/openSUSE_Leap_…] Repository type can't be determined. Warning: Skipping repository 'hardware' because of the above error. Retrieving repository 'snappy' metadata ........................................................[error] Repository 'snappy' is invalid. [snappy|https://download.opensuse.org/repositories/system:/snappy/openSUSE_L…] Valid metadata not found at specified URL History: - [snappy|https://download.opensuse.org/repositories/system:/snappy/openSUSE_L…] Repository type can't be determined. Please check if the URIs defined for this repository are pointing to a valid repository. Warning: Skipping repository 'snappy' because of the above error. Some of the repositories have not been refreshed because of an error. Loading repository data... Warning: Repository 'Update repository of openSUSE Backports' metadata expired since 2024-02-05 05:25:26 PST. Warning: Repository 'Update Repository (Non-Oss)' metadata expired since 2024-04-30 04:05:04 PDT. Warning: Repository metadata expired: Check if 'autorefresh' is turned on (zypper lr), otherwise manually refresh the repository (zypper ref). If this does not solve the issue, it could be that you are using a broken mirror or the server has actually discontinued to support the repository. Reading installed packages... 'hw-probe' not found in package names. Trying capabilities. No provider of 'hw-probe' found. Resolving package dependencies... Nothing to do. quasar:/etc/X11 # zypper lr Repository priorities are without effect. All enabled repositories share the same priority. # | Alias | Name | Enabled | GPG Check | Refresh ---+---------------------------------------+------------------------------------------------------------+---------+-----------+-------- 1 | download.nvidia.com-$releasever | nVidia Graphics Drivers | Yes | (r ) Yes | Yes 2 | ftp.gwdg.de-openSUSE_Leap_$releasever | Packman Repository | Yes | (r ) Yes | Yes 3 | hardware | hardware | Yes | ( p) Yes | No 4 | openSUSE-Leap-15.4-1 | openSUSE-Leap-15.4-1 | No | ---- | ---- 5 | repo-backports-debug-update | Update repository of openSUSE Backports (Debug) | No | ---- | ---- 6 | repo-backports-update | Update repository of openSUSE Backports | Yes | (r ) Yes | Yes 7 | repo-debug | Debug Repository | No | ---- | ---- 8 | repo-debug-non-oss | Debug Repository (Non-OSS) | No | ---- | ---- 9 | repo-debug-update | Update Repository (Debug) | No | ---- | ---- 10 | repo-debug-update-non-oss | Update Repository (Debug, Non-OSS) | No | ---- | ---- 11 | repo-non-oss | Non-OSS Repository | Yes | (r ) Yes | Yes 12 | repo-oss | Main Repository | Yes | (r ) Yes | Yes 13 | repo-sle-debug-update | Update repository with updates from SUSE Linux Enterpris-> | No | ---- | ---- 14 | repo-sle-update | Update repository with updates from SUSE Linux Enterpris-> | Yes | (r ) Yes | Yes 15 | repo-source | Source Repository | No | ---- | ---- 16 | repo-update | Main Update Repository | Yes | (r ) Yes | Yes 17 | repo-update-non-oss | Update Repository (Non-Oss) | Yes | (r ) Yes | Yes 18 | snappy | snappy | Yes | (r ) Yes | Yes quasar:/etc/X11 # zypper ref Repository 'nVidia Graphics Drivers' is up to date. Repository 'Packman Repository' is up to date. Retrieving repository 'hardware' metadata ......................................................................................[error] Repository 'hardware' is invalid. [hardware|https://download.opensuse.org/repositories/hardware/openSUSE_Leap_…] Valid metadata not found at specified URL History: - [hardware|https://download.opensuse.org/repositories/hardware/openSUSE_Leap_…] Repository type can't be determined. Please check if the URIs defined for this repository are pointing to a valid repository. Skipping repository 'hardware' because of the above error. Repository 'Update repository of openSUSE Backports' is up to date. Repository 'Non-OSS Repository' is up to date. Repository 'Main Repository' is up to date. Repository 'Update repository with updates from SUSE Linux Enterprise 15' is up to date. Repository 'Main Update Repository' is up to date. Repository 'Update Repository (Non-Oss)' is up to date. Retrieving repository 'snappy' metadata ........................................................................................[error] Repository 'snappy' is invalid. [snappy|https://download.opensuse.org/repositories/system:/snappy/openSUSE_L…] Valid metadata not found at specified URL History: - [snappy|https://download.opensuse.org/repositories/system:/snappy/openSUSE_L…] Repository type can't be determined. Please check if the URIs defined for this repository are pointing to a valid repository. Skipping repository 'snappy' because of the above error. Some of the repositories have not been refreshed because of an error. Marc.... --

8 26

Re: [opensuse] ZFS on SuSE-anyone, Distributed File System...
by Verner Kjærsgaard 16 Aug '24

16 Aug '24

Michael Folsom skrev: > Hi: > > Quick question - what are the advantages of ZFS over XFS? > > I'm not trying to start a flame war but as a happy XFS user wonder > what ZFS has to offer> > > Later - > > > Mike > > On Tue, Jun 10, 2008 at 2:35 PM, Verner Kjærsgaard <vk(a)os-academy.dk> wrote: >> Hi list, >> >> - has anyone tried SUN's ZFS on SuSE? Can it be done, is it at all feasible? >> >> - or another Distributed file system. I may need a file system, that will allow me to add storage ad hoc. >> >> Any hints, links? >> >> As always, thanks! >> >> -- >> -------------------------------------------- >> Med venlig hilsen/best regards >> Verner Kjærsgaard >> Novell Certified Linux Professional 10035701 >> www.os-academy.dk +45 56964223 >> -- >> To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org >> For additional commands, e-mail: opensuse+help(a)opensuse.org >> > I really don't know, if any? Are they not two different beasts? I tried looking for info about XFS, any good links, homepage? -- -------------------------------------------- Med venlig hilsen/best regards Verner Kjærsgaard Novell Certified Linux Professional 10035701 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

4 3

[opensuse] boot32.efi for 64 bits processor and Leap
by jdd 16 Aug '24

16 Aug '24

Hello, We see more and more often very small but powerfull computers, atom multicore 64 bits, but with UEFI 32 bits firmware. I have one now ("It Works TW891" paid 129€ - 32Gb ssd + 2Gb ram, runs almost perfectly windows 10 32bits or Debian 64bits). these computers can be installed with 64 bits distros, but they need absolutely a 32 bits loader. Right now I on ly know of the hybrid debian 32/64bits dvd to be able to install. Notice that *only the loader* have to be 32bits, the generic name being boot32.efi copying a generic loader to the Leap EFI folder allows booting, and probably installing (I couldn't make all the tests), but the generic one gives only a grub prompt, not handy. Could it be possible to add to the Leap isos this 32 bits loader? only this one have to be 32bits, AFAIK nothing else have to be changed. thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 9

TW dup to local repo packages tried to remove 53 kde3 packages -- what to check?
by David C. Rankin 16 Aug '24

16 Aug '24

Devs, All, I created a signed local repo with patched Nvidia packages for the G04 driver. My intent was simply to: # zypper -r mynvidiarepo dup To move all Nvidia packages to the versions in my repo. When I did, zypper proposed updating the 7 driver packages, but then also proposed removing most of the kde3 desktop (53 packages). I'm at a loss to why zypper would propose the removal of unrelated packages when simply trying to update Nvidia drivers. My first thought was there must have been some problem with the .spec and dependencies -- but I can't imaging what that would be. Where would I start to look for why zypper proposed the removal of the kde3 packages on change of versions for the Nvidia drivers? To work around this problem, I simply rsynced the repo to my laptop and then did a: # zypper in *.rpm Which worked fine and didn't suggest uninstalling anything. So what's the difference in dup or in for the package removals? (I would have copied the zypper dup output -- but the dkms driver build scrolled everything out of the xterm buffer :( Thoughts? -- David C. Rankin, J.D.,P.E.

2 6

Accessing ext4 from Windows
by Roger Oberholtzer 15 Aug '24

15 Aug '24

Perhaps a bit off subject. I'm not sure. But I figure there are folk here using ext4 file systems, so... I have a new requirement to be able to read/write ext4 file systems from Windows. It's like this: we have a data collection system that collects data to a mix of ext4 and vfat disks. For whatever reasons. We have usually accessed all of these from a Linux system where file system support is really great. Unfortunately, the powers that be have decided to set up a system that is Windows-only. Sigh. I have tried installing openSUSE Leap 15.6 in WSL 2. It actually works great. My motivation was that I should be able to mount the ext4 partition via wsl, and then access it in Windows. See, for example, https://windowsreport.com/ext4-windows-11/. That is sort of true if by 'access' you mean in Windows Explorer only. That is not a workable solution. I need access in programs and shell scripts. I then tried a product like Linux Reader. It is geared towards file recovery. Why anyone would use a Windows computer to try to recover files on an ext4 system is a real mystery. It also seemed to caution that it really wanted to be a read-only thing. Not a confidence booster. And not what I need. Finally, I tried Paragon Software's ext4 for Windows. It seems to be properly read/write and, generally looks great. But then I see that I cannot access SQLite databases that are on these disks. SQLite (general programs and database browsers) all complain that the database is locked. We had this issue when, from Linux, accessing databases on CIFS mounted drivers. That was sorted by adding nobrl to the CIFS mount command on Linux. It's a known issue. So this method was close, but no cigar. A support question is pending as I cannot think I am the first person who wanted to access an SQLite database this way. So my question here is if anyone has any experience with Windows software that lets one mount ext4 file systems read/write. It has to work from programs and shell scripts, not just in a file system browser GUI. -- Roger Oberholtzer

5 7

Can download.opensuse.org/ add a cookie to save my view preferences (no. of lines to show)?
by David C. Rankin 14 Aug '24

14 Aug '24

Admins, The interface at download.opensuse.org is growing on me, but the frustrating part is I have to set the drop-down for number of files to show each time to 100, etc.. Can we add a cookie to save that info. It we are dealing with the additional overhead of the interface -- it may as well work for us. This is a cookie I would actually welcome :) -- David C. Rankin, J.D.,P.E.

3 3

Using iptables along with firewalld
by Curtis J Blank 14 Aug '24

14 Aug '24

I'm running Tumbleweed and using firewalld. If I want to block some incoming IP addresses and I add iptables reject rules will that work to block them? I do a iptables -L and iptables appears to be available. I have my reasons for wanting to use iptables for this blocking.

5 11

Styling Qt5 Apps with qt5ct - simple text file edits work fine
by David C. Rankin 14 Aug '24

14 Aug '24

All, Dropping a note for anyone who has Qt5 apps running not under Plasma. Take for example keepassxc. The default dark style is fine, but if you install anything that adjusts the Qt5 style, it will revert to white and is quite blinding. One workaround is to install qt5ct (Qt5 Configuration Tool) which does come with a few themes. Only problem, the darker theme has hideous alternating row colors in keepassxc. (configured with darker colors and fusion qss) Thankfully the colors for everything are in a simple text file that you can change to suit your needs. The install will put the themes color files in: /usr/share/qt5ct/colors/xxxxxxx.conf (where xxxxxxx is the name for the color theme) You can simply copy a theme to modify from /usr/share/qt5ct/colors to your user config location in: ~/.config/qt5ct/colors/ You can then modify it to your hearts content. Use a color picker like kcolorchooser or the one in qimp or the gtk-color-chooser to find the color you wish to change in a Qt5 app, then just edit your copy of the .conf file (rename it too to some name you want for your theme). Then simply run qt5ct and select the color theme from the drop-down and hit "Apply". For the darker.conf theme hideous alternating row colors, simply change #ff5c5b5a to #ff434343 and things will look at LOT better. Change in all 3 lines (active, disabled, inactive). If you make sure that is the only color in the line (#ff5c5b5a is), you can simple use sed to fix it: sed -i 's/5c5b5a/434343/' ~/.config/qt5ct/colors/yourtheme.conf done. Hopefully this helps someone else faced with unbearable Qt5 color themes when running a Qt5 app not under plasma. -- David C. Rankin, J.D.,P.E.

1 0

[opensuse] How to make sure that each vNIC in guest is always associated with a correct VLAN?
by Martin T 14 Aug '24

14 Aug '24

Hi, I have six virtual bridges in xen host machine and following virtual machine configuration file section defining the vifs: vif = [ 'bridge=br10', 'bridge=br20', 'bridge=br30', 'bridge=br40', 'bridge=br50', 'bridge=br60' ] This means that in the guest(openSUSE Leap 42.1) I have six vNICs(eth0 - eth5). Can I be sure that eth0 is always connected to br10, eth1 to br20, etc? Or should I specify a MAC address for each vNIC created like this: vif = [ 'bridge=br10, mac=00:14:5E:11:C6:F1', 'bridge=br20, mac=00:14:5E:11:C6:F2', 'bridge=br30, mac=00:14:5E:11:C6:F3', 'bridge=br40, mac=00:14:5E:11:C6:F4', 'bridge=br50, mac=00:14:5E:11:C6:F5', 'bridge=br60, mac=00:14:5E:11:C6:F6' ] .. and then configure udev rules which make sure that interface associated with MAC 00:14:5E:11:C6:F1 and br10 is always named eth0, interface associated with MAC 00:14:5E:11:C6:F2 and br20 is always named eth1, etc? Or maybe there is a better way using /etc/sysconfig/network/ifcfg-* files? thanks, Martin -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 5