January 2025 - openSUSE Support - openSUSE Mailing Lists

RAID device naming
by Felix Miata 19 Jan '25

19 Jan '25

I have 3 computers using RAID1. When booted to Leap, all devices equate to: /dev/mdX names, while booted to TW or Slowroll: /dev/md12X All 3 use the same format in /etc/mdadm.conf, e.g.: HOMEHOST <ignore> DEVICE containers partitions ARRAY /dev/mdX metadata=1.0 name=hostname:filesystemlabel UUID=… Each installation on each machine uses one identical file for /etc/mdadm.conf. Leap example: # mdadm -D /dev/md0 /dev/md0: Version : 1.0 Creation Time : Tue Aug 28 00:35:21 2018 Raid Level : raid1 Array Size : 8834944 (8.43 GiB 9.05 GB) Used Dev Size : 8834944 (8.43 GiB 9.05 GB) Raid Devices : 2 Total Devices : 2 Persistence : Superblock is persistent Intent Bitmap : Internal Update Time : Sat Jan 18 04:01:09 2025 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Consistency Policy : bitmap Name : hostname:filesystemlabel UUID : … Events : 1789 Number Major Minor RaidDevice State 3 8 21 0 active sync /dev/sdb5 2 8 5 1 active sync /dev/sda5 # How can I get TW to do as Leap does, and use the names in mdadm.conf? Are --homehost= and/or --prefer= needed to be used somehow with manage to change something recorded on each device as shown by mdadm -D? -- 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

1 0

USA FEMA online .pdf forms support?
by Felix Miata 17 Jan '25

17 Jan '25

Do we have an Acrobat equivalent in openSUSE repos to fill out online PDF files from <https://www.fema.gov/flood-insurance/find-form/policyholders>? "It's the Proof of Loss - Building & Contents" form there that I need to fill out and submit. I was able to fetch it, but Chromium won't load it[1], while the mail-in form loads fine: <https://www.fema.gov/sites/default/files/documents/fema_hpcc-proof-of-loss-…> [1] Instead of loading the actual online submittal form, it loads a message that claims <http://www.adobe.com/go/reader_download> offers a version of Acrobat for Linux, but the only Linux listed there is for Android. -- 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

8 10

Re: ruby 3.3-3.6-1.1 x86-64
by Carlos E. R. 16 Jan '25

16 Jan '25

On 2025-01-16 18:42, Aristides Lorlesse Gómez wrote: > Buenos dias la pantalla precedente es una captura del error que obtengo > al intentar actualizar OpenSuse. Ese error impide efectuar cualquier > actualización del sistema. He buscado en la red posible soluciones y no > hay información al respecto. Disculpa, pero esta lista de correo funciona en inglés. Hay otra lista en español, en "users-es(a)lists.opensuse.org". Puedo traducir tu mensaje al inglés, pero la foto que has puesto está también en español y la gente no lo va a entender. Por otra parte, puesto que estás usando Tumbleweed, la única forma aceptada de actualizar el sistema es usar el comando "zypper dup" en un terminal como root (o con sudo). Por último, una petición. Tratamos de evitar enviar fotos o ficheros pesados a la lista, puesto que obligamos a todo el mundo a descargarlas. En su lugar, la costumbre es subir la foto en https://paste.opensuse.org/ y poner el enlace en la lista. También se puede usar el comando "susepaste". --- Translation --- > Good morning, the above screen is a screenshot of the error I get when I try to upgrade OpenSuse. This error prevents me from performing any system update. I have searched the net for possible solutions and there is no information about it. Excuse me, but this mailing list works in English. There is another list in Spanish, at “users-es(a)lists.opensuse.xn--org-9o0a. I can translate your message to English, but the picture you posted is also in Spanish and people will not understand it. On the other hand, since you are using Tumbleweed, the only accepted way to upgrade the system is to use the command “zypper dup” in a terminal as root (or with sudo). Finally, a request. We try to avoid sending photos or large files to the list, since we force everyone to download them. Instead, the custom is to upload the photo at https://paste.opensuse.org/ and put the link on the list. You can also use the “susepaste” command. Translated with DeepL.com (free version) -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)

1 0

Dependency nightmare ?
by Jörn Dreyer 16 Jan '25

16 Jan '25

Hello, I have a problem with a project that uses cmake as build system. The Makefiles can be generated either by the ninja generator(default if available) or by the Unix Makefile generator. So I wanted to deinstall ninja for a test using yast, but ran into a dependency problem: All qt6*-devel packages depend on ninja and meson! Why? I would understand if cmake would depend on ninja/meson, but development packages that contain header files and libraries? Looking at the qt6-*-devel packages for the dependencies, ninja/meson is not listed there. I tried to rebuild the rpmdb but withoutr changes. What could be the reason for this problem? Regards Jörn

2 1

Re: New Tumbleweed snapshot 20250112 released!
by Ianseeks 16 Jan '25

16 Jan '25

Hi, I can't seem to get passed the deletion phase of this snapshot. It identified 651 deletions/575 installations to perform. It started with the deletions and so far I've had to press "i" to every deletion as i get this error on every attempt to delete "error: package libpystring0_0-1.1.4-1.1.x86_64 is not installed Removal of (175620)libpystring0_0-1.1.4-1.1.x86_64(@System) failed: Error: Subprocess failed. Error: RPM failed: Command exited with status 1. Abort, retry, ignore? [a/r/i] (a): i" I got to the 70th deletion failure and gave up. Is my only option to press "i" to every failure until it starts working? Could this down to me running "zypper clean" a few days ago when i ran out of space? regards Ian -- openSUSE Tumbleweed 20250109 kwin 6.2.5 kmail2 6.3.0 (24.12.0) - akonadiserver 6.3.0 (24.12.0) - Kernel: 6.12.8-2- default - kernel-firmware-radeon 20241220

3 5

Journal Log spammed after machine wakeup:
by -pj 14 Jan '25

14 Jan '25

Hi, another question for you here if I may🫥. I am using openSUSE Tumbleweed 20250112 on machine here. With I think, it is now a type AMD RX640 GPU: 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Lexa [Radeon 540X/550X/630 / RX 640 / E9171 MCM] [1002:6987] (rev c1) Subsystem: Dell Device [1028:1713] Kernel driver in use: amdgpu Kernel modules: amdgpu I have recently started to use *Kernel:stable standard* on machine because of some negative behavior noticed after machine wakeup. uname -r :< 6.12.9-1.g0ae2136-default I have issued a couple of bug reports trying to work through this issue so far. ENOMEM dmesg entry bugzilla bug :< 1235540 WQ_MEM_RECLAIM journal entry bugzilla bug :< 1235668 After wakeup now the log appears to be filled with 27000 lines of :< [drm] scheduler comp_1.1.0 is not ready, skipping messages. Small sample of journal- Jan 14 12:30:32 hightower-i5-6600k kernel: [drm] scheduler comp_1.1.1 is not ready, skipping Jan 14 12:30:32 hightower-i5-6600k kernel: [drm] scheduler comp_1.3.1 is not ready, skipping Jan 14 12:30:32 hightower-i5-6600k kernel: [drm] scheduler comp_1.1.0 is not ready, skipping Jan 14 12:30:32 hightower-i5-6600k kernel: [drm] scheduler comp_1.1.1 is not ready, skipping Jan 14 12:30:32 hightower-i5-6600k kernel: [drm] scheduler comp_1.3.1 is not ready, skipping Jan 14 12:30:32 hightower-i5-6600k kernel: [drm] scheduler comp_1.1.0 is not ready, skipping Ending sample of journal- I have seen this similar report on GitLab :< https://gitlab.freedesktop.org/drm/amd/-/issues/3746 The machine in question *there*, locks up hard. This machine has frozen (separate screen, application in separate workspace whites out, freezes for a bit of time. but no *hard lock* requiring powercycle as of yet. How to best proceed with this? Is a bug report in order? -Regards

1 0

This should really not happen on Leap.....
by Axel Braun 14 Jan '25

14 Jan '25

[1] -------- [1] Bild

3 3

Questions about Kernel versions available via OBS:
by -pj 13 Jan '25

13 Jan '25

Hi, I am using openSUSE Tumbleweed 20250109 here, on a machine. I recently asked about the possibity to backport a patch for amdgpu. I was told that "This should have been already included in 6.12.9. Please check the kernel in OBS Kernel:stable repo." When I check the current kernel version on machine here: :~> uname -a Linux hightower-i5-6600k 6.12.8-2-default #1 SMP PREEMPT_DYNAMIC Mon Jan 6 06:45:37 UTC 2025 (90b0f5b) x86_64 x86_64 x86_64 GNU/Linux It appears the 6.12.8-2-default kernel is indeed not as new as the 6.12.9. kernel available in OBS Kernel:stable repo. My questions for you are, I thought Tumbleweed is using the most current kernel by default (as far as openSUSE goes). Why is it not? Is Leap using the newest kernel? If OBS kernel:stable 6.12.9 is installed, what happens in the future when 'zypper dup' is used? Is there even another kernel in OBS for openSUSE Tumbleweed that contains more amdgpu patches and even more other various patches that I could possibly use, like a backport type kernel or something? -Regards

3 11

Re: This should really not happen on Leap.....
by Axel Braun 12 Jan '25

12 Jan '25

Am Sonntag, 12. Januar 2025, 22:00:36 Mitteleuropäische Normalzeit schrieb Robert Kocher: [pls reply to list, so everybody can read....] > I agree! > > And i wonder how long it will last, until it is corrected! The error > appears since several days now! > > Are there any news about this? No, but running 'zypper up' works flawless (although some GTK-packages are not installed, without this message). However, as posted, this should not happen for Leap - 'my' Leap users are already stuck with this message! Axel

1 0

dmesg error snippet:< workqueue: Failed to create worker thread:
by -pj 09 Jan '25

09 Jan '25

Hi, openSUSE Tumbleweed here. I noticed the following 'dmesg' output: [49125.219751] [ T141229] workqueue: Failed to create a worker thread: -ENOMEM [49128.254152] [ T2] SLUB: Unable to allocate memory on CPU 1 (of node 0) on node 0, gfp=0xcc0(GFP_KERNEL) [49128.254157] [ T2] cache: task_struct, object size: 10752, buffer size: 10752, default order: 3, min order: 2 [49128.254159] [ T2] node 0: slabs: 976, objs: 2920, free: 0 A web search led me to :< https://kernel.org/doc/html/latest/core-api/workqueue.html This above is a lengthy in depth article for me to comprehend right now. I read this shorter easier for me to understand article :< https://github.com/zephyrproject-rtos/zephyr/issues/61819 What are your thoughts about this message? Is there an openSUSE article that pertains to this more than the articles I have linked above? Is this a bug? Or is this a common error message to see? -Regards

3 9