May 2023 - openSUSE Support - openSUSE Mailing Lists

Emacs and (color) emoji
by Achim Gratz 21 Jun '23

21 Jun '23

One of my Linux machines w/ Tumbleweed (which were both using the same base installation, but have probably diverged a bit during the years of using them for different tasks) shows color emoji in Emacs, while the other doesn't. I can't find out which package and/or configuration is responsible for that, any ideas? Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf rackAttack: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

3 3

how to trust opensuse keys? new RSA 4096 bit keys, how to double check?
by cagsm 06 Jun '23

06 Jun '23

Support, how to trust opensuse keys? new RSA 4096 bit keys, how to double check? e.g. when test driving new dup for 15.5: > # sudo zypper -vvv --releasever=15.5 ref .... Checking whether to refresh metadata for Update repository of openSUSE Backports Retrieving: http://download.opensuse.org/update/leap/15.5/backports/repodata/repomd.xml ........................................................................................................................[done (195 B/s)] Retrieving: http://download.opensuse.org/update/leap/15.5/backports/repodata/repomd.xml… .....................................................................................................................[done (63 B/s)] Retrieving: http://download.opensuse.org/update/leap/15.5/backports/repodata/repomd.xml… .....................................................................................................................[done (63 B/s)] Retrieving: http://download.opensuse.org/update/leap/15.5/backports/repodata/repomd.xml ..................................................................................................................................[done] New repository or package signing key received: Repository: Update repository of openSUSE Backports Key Fingerprint: F044 C2C5 07A1 262B 538A AADD 8A49 EB03 25DB 7AE0 Key Name: openSUSE:Backports OBS Project <openSUSE:Backports@build.opensuse.org> Key Algorithm: RSA 4096 Key Created: Wed 10 May 2023 04:46:12 PM CEST Key Expires: Sun 09 May 2027 04:46:12 PM CEST Rpm Name: gpg-pubkey-25db7ae0-645bae34 Note: Signing data enables the recipient to verify that no modifications occurred after the data were signed. Accepting data with no, wrong or unknown signature can lead to a corrupted system and in extreme cases even to a system compromise. Note: A GPG pubkey is clearly identified by its fingerprint. Do not rely on the key's name. If you are not sure whether the presented key is authentic, ask the repository provider or check their web site. Many providers maintain a web page showing the fingerprints of the GPG keys they are using. Do you want to reject the key, trust temporarily, or trust always? [r/t/a/?] (r): -------------------------- I never understood how to actually test and lookup these keys and where to make sense of them and how to react in such cases questions of zypper or questions of yast software modules when adding additional repos and many more such situations. i used to understand that one needs to check via other means other channels and look for these keys fingerprints etc published on some official projects and companies websites and all. but this is all in such a messed up and not fully established state, at least thats what i make of it. all i find is like a corporate suse (not opensuse) sigining keys page for example. > <https://www.suse.com/support/security/keys/> this needs to become much better i say. maybe nobody of the userbase care these days everybody just clicks and downloads and executes :( please make this a wholesome and good experience and dont miseducate the userbase into just not understanding and knowing anything about security, trust chains etc anyone care to elaborate how to actually double check on opensuse binaries and repos and their security and all. it all boils down to keys, to the root source of authority of a project et al also are old keys signing the newer keys and building chains and successions and so on? ty

7 15

bugs@lists.opensuse.org dead?
by mh＠mike.franken.de 04 Jun '23

04 Jun '23

Hi, is bugs(a)lists.opensuse.org dead? The last mail I got from the bugs mailing list is "Message-ID: <bug-1210334-21960(a)http.bugzilla.opensuse.org/>" received on 12.04., 07:22. Thx and bye. Michael.

5 7

[support] installation initrds larger than subsequent
by Felix Miata 01 Jun '23

01 Jun '23

Long ago I noticed on Leap at least that the initial installed initrd is significantly larger than rebuilds or those for newer kernels. I'd like to know why, so I thought I could find (a) .conf file(s) on a boot from installation media. No such luck, NAICT. There are few small files in */usr/lib/dracut/dracut.conf.d/, but they don't really look like they're big enough, or contain the right kind of content, to be responsible: 113 multipath.conf 112 50-sg3_utils.conf 147 dm-parts.conf /etc/dracut.conf.d/ doesn't exist, and neither /etc/dracut.conf. multipath.conf only has comment and: install_items+=" /usr/lib/tmpfiles.d/multipath.conf " dm-parts.conf only has comment and: install_items+=" /usr/lib/udev/rules.d/11-dm-parts.rules " 50-sg3_utils.conf only has comment and: install_items+=" /usr/lib/udev/rules.d/54-before-scsi-sg3_id.rules " How can I find out what is responsible for making them significantly bigger? -- 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 3

hibernating when lid closes
by Peter Münster 30 May '23

30 May '23

Hi, I have installed Leap 15.4 on a laptop with KDE-desktop. Unfortunately PowerDevil blocks the "handle-lid-switch", so the "HandleLidSwitch=hibernate" in /etc/systemd/logind.conf does not work. How could I get hibernation on the lid close event please? Is it possible somewhere, to configure PowerDevil to not block the event? TIA for any hints, -- Peter

6 10

Issue with CUPS and printer disappearing.
by Larry Len Rainey 29 May '23

29 May '23

1 0

15.4 - main update repostiry expired today - ?
by cagsm 29 May '23

29 May '23

Repository 'Main Update Repository' metadata expired since 2023-05-27 --------------------------- sudo zypper lu Loading repository data... Warning: Repository 'Main Update Repository' metadata expired since 2023-05-27 Warning: Repository metadata expired: Check if 'autorefresh' is turned on (zypper lr), otherwise manualy 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... No updates found. ---------------------- zypper lr 1 Alias : repo-update Name : Main Update Repository URI : http://download.opensuse.org/update/leap/15.4/oss Enabled : Yes GPG Check : (r ) Yes Priority : 99 (default priority) Autorefresh : On Keep Packages : Off Type : rpm-md GPG Key URI : Path Prefix : / Parent Service : Keywords : update Repo Info Path : /etc/zypp/repos.d/repo-update.repo MD Cache Path : /var/cache/zypp/raw/repo-update ---------------------------- everything is ref and online and live and date time correct what happen?

6 5

Video Intel awaking w wrong Brightness level
by Marco Calistri 28 May '23

28 May '23

Hello, I've been able to set a specific brightness intensity at evry boot, by using an /etc/init.d/after.local script, but anytime my system awakes from suspended mode, the brightness resets to a very high intensity. from dmesg I see: [ 3.128757] i915 0000:00:02.0: [drm] Skipping intel_backlight registration [ 33.797331] ideapad_acpi VPC2004:00: Keyboard backlight control not available [28383.336476] video LNXVIDEO:00: Restoring backlight state How could I resolve this? Which file is used by Tumbleweed for an after suspend brightness adjustment? Thanks and regards, -- Marco Calistri Build: openSUSE Tumbleweed 20230213 Kernel: 6.1.10-1-default - XFCE: (4.18.1)

4 33

[opensuse-support] kernel vs. nouveau bug? report where?
by Felix Miata 24 May '23

24 May '23

I had the following bug report ready to submit, but I checked Fedora 38, and same problem there. Original Summary: absent both plymouth, and video= on linu lines, vtty[1-6] framebuffers produce vast raster right and bottom borders on the larger resolution of two displays To reproduce: 1-connect two unequal native resolution displays to a Tesla or Firmi GPU 2-don't have plymouth in use (I don't ever have it installed, so don't know whether it impacts) 3-don't include e.g. video=1440x900@60 directive on Grub's linu lines 4-boot TW 5-switch to a vtty, e.g. Ctrl-Alt-F3 Actual behavior: 1-Both displays utilize the resolution (same pixel grid) of the lower resolution display 2-Lower resolution display behaves as expected (light text on black background) 3-Higher resolution display uses same pixels as lower resolution display, with light text on black background, leaving right side and bottom raster instead of black Expected behavior: 1-Both displays utilize the resolution (same pixel grid) of the lower resolution display 2-Lower resolution display behaves as expected 3-Entire higher resolution display's background is black instead of portions in raster Workaround: add e.g. video=1440x900@60 to Grub's linu lines, which causes both displays to use the same nominal mode on the full display space. Typical other linu line options: noresume consoleblank=0 net.ifnames=0 ipv6.disable=1 preempt=full mitigations=none My Tesla has HDMI and DVI outputs, tested with 1920x1200 and 1680x1050 displays. My Fermi has dual DisplayPort, tested with 2560x1440 and 1680x1050 displays. Occurs with 6.3.2 and 6.2.12 kernel-default, *and* with 6.2.15 on Fedora 38. Does not occur with 6.1.12 kernel-default on NVidia, or with AMD Caicos (Terascale2) GPU, or with Intel Eaglelake GPU. Tested only on legacy booting (no UEFI support). Others might describe what I call "raster" as multicolored snow. Is there a Nouveau bug tracker to take this to, or does it need to goto bugzilla.kernel.org, or ??? Should I submit the report on BOO anyway? -- 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 1

LUKS support beyond PBKDF2?
by cagsm 19 May '23

19 May '23

Support, leap 15.4, full disk encryption (FDE), luks I suppose. I am not an expert (TM). reading this recent article: <https://mjg59.dreamwidth.org/66429.html> comes up with the question if ones distro supports stuff beyond PBKDF2, e.g. argon2id anyone? thanks for keeping opensuse utmost secure and safe.

3 6

No more videos on zdf.de
by Axel Braun 17 May '23

17 May '23

Hello everybody, since recently (dont ask me exactly since when) I cant stream video from german television https://www.zdf.de/live-tv anymore. No video format is supported by your device (the orther channel - daserste.de - is working well) Tried upgrading from ffmpeg-4 to -6 but no success. A bunch of openh264 libs is installed as well. Any idea what to try? Thanks Axel

4 6

Re: New Tumbleweed snapshot 20230512 released!
by Robert Webb 15 May '23

15 May '23

On Sat, 13 May 2023 18:00:44 +0000, Dominique Leuenberger <dimstar(a)suse.de> wrote *To factory(a)lists.opensuse.org*, Message-ID: <168400084471.21846.15478725920013160203@localhost>: > [...] > Packages changed: > [...] > ==== pipewire ==== > Version update (0.3.69 -> 0.3.70) > Subpackages: gstreamer-plugin-pipewire libpipewire-0_3-0 pipewire-alsa pipewire-lang pipewire-libjack-0_3 pipewire-modules-0_3 pipewire-pulseaudio pipewire-spa-plugins-0_2 pipewire-spa-tools pipewire-tools > > - Make pipewire-alsa conflict with alsa-plugins-pulse as both > provide /etc/alsa/conf.d/99-*-default.conf > [...] Making them duke it out. Zypper reacts with: # zypper dup [...] Problem: the to be installed pipewire-alsa-0.3.70-1.1.x86_64 conflicts with 'alsa-plugins-pulse' provided by the installed alsa-plugins-pulse-1.2.7.1-4.4.x86_64 Solution 1: deinstallation of alsa-plugins-pulse-1.2.7.1-4.4.x86_64 Solution 2: deinstallation of pipewire-alsa-0.3.69-2.1.x86_64 Solution 3: keep obsolete pipewire-alsa-0.3.69-2.1.x86_64 Choose from above solutions by number or cancel [1/2/3/c/d/?] (c): c Which one should be uninstalled? -- Robert Webb

3 4

Zypper dup: problem with libsox3, sox
by Robert Webb 12 May '23

12 May '23

I tried to 'zypper dup' from openSUSE Tumbleweed 20230508 to current (20230510): Computing distribution upgrade... 2 Problems: Problem: problem with the installed libsox3-14.4.2-1599.7.pm.137.x86_64 Problem: problem with the installed sox-14.4.2-1599.7.pm.137.x86_64 Problem: problem with the installed libsox3-14.4.2-1599.7.pm.137.x86_64 Solution 1: install libsox3-14.4.2-6.1.x86_64 from vendor openSUSE replacing libsox3-14.4.2-1599.7.pm.137.x86_64 from vendor http://packman.links2linux.de Solution 2: keep obsolete libsox3-14.4.2-1599.7.pm.137.x86_64 Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c/d/?] (c): s Problem: problem with the installed sox-14.4.2-1599.7.pm.137.x86_64 Solution 1: install sox-14.4.2-6.1.x86_64 from vendor openSUSE replacing sox-14.4.2-1599.7.pm.137.x86_64 from vendor http://packman.links2linux.de Solution 2: keep obsolete sox-14.4.2-1599.7.pm.137.x86_64 Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c/d/?] (c): c (4) Thu May 11 12:52:45 PDT 2023 There was nothing in the New Tumbleweed snapshot announcements nor the known defects reports about libsox3 or sox. What to do? Switch vendors? -- Robert Webb

4 8

Problem compiling kernel module for nvidia after dup of Tumbleweed
by Andrea Croci 08 May '23

08 May '23

Dear Community, I'm running OpenSUSE Tumbleweed and I have added the repository for Cuda from the Nvidia Website <https://developer.nvidia.com/cuda-downloads?target_os=Linux&target_arch=x86…>. I also added the "official" nvidia-repository for OpenSUSE <https://download.nvidia.com/opensuse/tumbleweed>, which however is for Leap, not for Tumbleweed. I installed Cuda, which pulled the nvidia-drivers "nvidia-computeG05", "nvidia-gfxG05-kmp-default" and "nvidia-glG05" of the 530 family. Everything was working fine. I recently did a zypper dup. After rebooting, the window manager doesn't start and I'm sent to a console login. The X log tells me, among other things: [ 65.945] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the [ 65.945] (EE) NVIDIA: system's kernel log for additional error messages and [ 65.945] (EE) NVIDIA: consult the NVIDIA README for details. [ 65.945] (EE) No devices detected. [ 65.945] (EE) Fatal server error: [ 65.945] (EE) no screens found(EE) [ 65.945] (EE) dmesg and journalctl have no trace of anything related to nvidia. I tried to look for why the nvidia-driver (graphics card Nvidia GTX 750 Ti) doesn't load, I found that there is no "nvidia*.ko" in the directory /lib/modules/6.3.1-1-default/updates/. I tried to reinstall the drivers in order to see if it would recompile the kernel module against the new kernel, but I got the first error message (please let me know if attaching text files to this list is not appropriate and if you would like it pasted online somewhere instead). I thought that may be because the cuda-repository for Leap is no longer at the same kernel version as Tumbleweed and disabled it. Trying to reinstall the above mentioned nvidia-drivers found only the family 470 and offered me, among other options, to downgrade "x11-video-nvidiaG05-530.30.02-0.x86_64" to "x11-video-nvidiaG05-470.182.03-53.1.x86_64", which I accepted. During the recompilation of the kernel module I got the errors in Error2.txt, which are very similar to the errors I got the first time. I'm out of clue as to what to try next and would appreciate any help. Thank you

2 5

Network Manager and my 'Use Case'
by Charles Rinnoch 01 May '23

01 May '23

Hi All I am currently using Wicked for network connection, but very much aware that this appears to be deprecated and likely to be taken out of the next version of Leap, so I have been looking at Network Manager and hit against some issues. I run several machines on a network with a NAS for shared storage. I import a home drive image with NFS to /import/home and soft link several individual user images into /home to allow user logon to a personal environment on each of several computers on the network. So far, so good - it works really well for my small setup for several years across all Leap 15.x. Moreover, a switch between Wicked and Network Manager is sufficiently slick that I can have some user IDs on the laptop only and use available wifi away from home via Network Manager. Problems come when I try to use Network Manager for the setup at home, in that Network Manager is not invoked [by systemd?] at the same point as Wicked is. So that leaves the NFS shares unconnected when the logon screen becomes available [ie the ID's on NFS don't show up] and it appears that Network Manager is more a per user subsystem for which you need to log in in order to get the connections you want. Now, I can work around this by logging in as root and doing 'mount -a' and there appears to be some options in fstab to make this work, so I am not totally stuck. Thus, my question for anyone who has confronted similar: Is there a 'best' or 'recommended ' way to address this issue and get the NFS shares available with Network Manager before the logon screen displays. Thanks in advance, any and all help on this appreciated CR

13 83