May 2021 - openSUSE Support - openSUSE Mailing Lists

by Carlos E. R.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 How do I report that https://meet.opensuse.org/ is not working for me? My camera doesn't work. It worked early March. The camera works fine on other tools, like vlc or WhatsApp. Same issue with https://meet.jit.si/. I don't see a contact link in any of the two. - -- Cheers Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYIHa3hwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV+DoAn36+4ToqGmcLLKBayRVc p1MxVJCRAJ4n3qbS8+KOcMKqySQL7mnFmp1ejA== =eQu5 -----END PGP SIGNATURE-----

1 month

5
12
0 0

No IPv6 address in TW

by Bjoern Voigt

My Tumbleweed system does not get a public IPv6 address. The reason is unknown, but it must be a configuration problem, because all other dual boot OS, TW in rescue mode and even the KVM VMs get an IPv6 address on the same hardware. The router is OpenWrt based and seems to work fine. I already tried to copy the network configuration from the rescue system. I use a Wicked based network configuration, set up with YaST. For privacy reasons I replaced some numbers with "xx". # wicked ifstatus br0 br0 up link: #16, state up, mtu 1454 type: bridge, hwaddr xx:xx:xx:xx:xx:xx config: compat:suse:/etc/sysconfig/network/ifcfg-br0 leases: ipv4 dhcp granted leases: ipv6 dhcp requesting addr: ipv4 192.168.xxx.xxx/24 [dhcp] route: ipv4 default via 192.168.xxx.xxx proto dhcp # cat /etc/sysconfig/network/ifcfg-br0 BOOTPROTO='dhcp' STARTMODE='auto' ZONE='home' BRIDGE='yes' BRIDGE_PORTS='eno1' BRIDGE_STP='on' BRIDGE_FORWARDDELAY='2' # ip -6 addr show br0 16: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1454 qdisc noqueue state UP group default qlen 1000 inet6 fe80::406e:b2ff:fe1d:ae7/64 scope link valid_lft forever preferred_lft forever # systemctl status wickedd-dhcp6.service ● wickedd-dhcp6.service - wicked DHCPv6 supplicant service Loaded: loaded (/usr/lib/systemd/system/wickedd-dhcp6.service; enabled; vendor preset: disabled) Active: active (running) since Mon 2021-05-31 11:37:15 CEST; 53min ago Main PID: 26380 (wickedd-dhcp6) Tasks: 1 (limit: 4915) CPU: 48ms CGroup: /system.slice/wickedd-dhcp6.service └─26380 /usr/libexec/wicked/bin/wickedd-dhcp6 --systemd --foreground May 31 11:37:15 mybox systemd[1]: Starting wicked DHCPv6 supplicant service... May 31 11:37:15 mybox systemd[1]: Started wicked DHCPv6 supplicant service. May 31 11:38:46 mybox wickedd-dhcp6[26380]: br0: Request to acquire DHCPv6 lease with UUID xxxxxxxx-xxxx-xxxx-xxxx-00001a0> May 31 11:47:16 mybox wickedd-dhcp6[26380]: br0: Request to release DHCPv6 lease using UUID xxxxxxxx-xxxx-xxxx-xxxx-00001a> May 31 11:47:33 mybox wickedd-dhcp6[26380]: br0: Request to acquire DHCPv6 lease with UUID xxxxxxxx-xxxx-xxxx-xxxx-0000200> May 31 12:20:04 mybox wickedd-dhcp6[26380]: br0: Request to release DHCPv6 lease using UUID xxxxxxxx-xxxx-xxxx-xxxx-000020> May 31 12:24:43 mybox wickedd-dhcp6[26380]: br0: Request to acquire DHCPv6 lease with UUID xxxxxxxx-xxxx-xxxx-xxxx-0000340> # ping6 www.heise.de ping6: connect: Network is unreachable # sysctl net.ipv6.conf.all.disable_ipv6 net.ipv6.conf.all.disable_ipv6 = 0 # sysctl net.ipv6.conf.all.forwarding net.ipv6.conf.all.forwarding = 1 Any ideas? Greetings, Björn

1 month, 3 weeks

2
3
0 0

Filesystems Confusion

by Robin Klitscher

After long resisting the idea, I hope to switch from ext4 to btrfs for my next installation, Leap 15.3. The openSUSE norm is btrfs for / and xfs for /home, each in separate partitions, right? But, in contrast as I understand it, it seems Fedora’s default is for a single btrfs partition for both. Why the difference? That is, why a separate /home in Leap? And why xfs rather than btrfs anyway? And a supplementary question. What are the implications if I wanted to use additional data partition(s) besides /home? Should they be in btrfs? Or xfs? Or doesn’t it matter? -- Robin K Wellington "Harbour City" New Zealand

1 month, 3 weeks

5
9
0 0

[Leap15] How often should zypper dup run on 15.3?

by Bob Williams

I have recently upgraded from Leap 15.2 to 15.3. The upgrade was straightforward. Should I run zypper dup from time to time, or will updated packages for Leap 15.3 be notified on the opensuse-updates list? -- Bob Williams System: Linux 5.3.18-lp152.50-default Desktop: KDE Frameworks: 5.71.0, Qt: 5.12.7 and Plasma: 5.18.5 https://useplaintext.email/

1 month, 3 weeks

5
7
0 0

nvidia driver broken after update to 5.12.4-1-default

by Anthony Agelastos

Greetings: This morning I recently updated my Tumbleweed to the latest (5.12.4-1-default kernel) and when I boot into it, my resolution is stuck on 1024x768. I did some sleuthing and it looks like the Nvidia drivers are in a weird state (see below). I did some looking around and couldn't find a bug or forum entry for this so I thought I'd start here. Does anyone have any suggestions? Thank you for your help with this. {{{ > nvidia-smi Failed to initialize NVML: Driver/library version mismatch }}} Kind regards, Anthony

2 months

3
5
0 0

At startup, systemd tries to Resume from Hibernation (which is disabled)

by J Leslie Turriff

Looking at the messages that come up during boot, I see a 30 second delay while systemd tries to Resume from Hibernation. Looking at the Services settings in YaST, I see that all services related to this are disabled. How do I tell systemd not to attempt this during boot? (Does this happen when initrd is active, or after switching to real /?) | From YaST => System => Services: | │systemd-hibernate │Manually │Inactive (Dead) │Hibernate │ | │systemd-hybrid-sleep │Manually │Inactive (Dead) │Hybrid Suspend+Hibernate │ | │systemd-suspend │Manually │Inactive (Dead) │Suspend │ | | From journalctl: | May 18 21:48:39 pinto systemd[1]: dev-mapper-cr_ata\x2dST1000DM010\x2d2EP102_Z9AFBY9T\x2dpart3.device: Job dev-mapper-cr_ata\x2dST1000DM010\x2d2EP102_Z9AFBY9T\x> | May 18 21:48:39 pinto systemd[1]: Timed out waiting for device dev-mapper-cr_ata\x2dST1000DM010\x2d2EP102_Z9AFBY9T\x2dpart3.device. | May 18 21:48:39 pinto systemd[1]: Dependency failed for Resume from hibernation using device /dev/mapper/cr_ata-ST1000DM010-2EP102_Z9AFBY9T-part3. | May 18 21:48:39 pinto systemd[1]: systemd-hibernate-resume(a)dev-mapper-cr_ata\x2dST1000DM010\x2d2EP102_Z9AFBY9T\x2dpart3.service: Job systemd-hibernate-resume@de> | May 18 21:48:39 pinto systemd[1]: dev-mapper-cr_ata\x2dST1000DM010\x2d2EP102_Z9AFBY9T\x2dpart3.device: Job dev-mapper-cr_ata\x2dST1000DM010\x2d2EP102_Z9AFBY9T\x> | | From /etc/crypttab: | swap UUID=618ca366-638c-4bf8-bd86-917f0eac83db /dev/urandom | # cr_ata-ST1000DM010-2EP102_Z9AFBY9T-part3 UUID=618ca366-638c-4bf8-bd86-917f0eac83db /dev/urandom Leslie -- openSUSE Leap 15.2 x86_64

2 months

3
4
0 0

system crashed during upgrade--HELP

by Doug McGarrett

OpenSUSE TW. System crashed during the second part of upgrade, where files were reporting "done." Crash occurred at 966/2162 Installing shim _15 + git47-222222222.2.x86_64 Rebooted to blank (black) screen with message as follows: GNU GRUB VERSION 2.04 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completion. Anywhere else TAB lists possible device file completetions. grub _ Is it possible to save this, and if so, how? Have left computer in this condition awaiting answer. --doug

2 months

11
30
0 0

gs problem with libpcre2

by Jogchum Reitsma

Hi, Running TW, (latest snapshot of today), gs bails out with gs gs: error while loading shared libraries: libpcre2-8.so.0: failed to map segment from shared object I've had this problem for a while (first mentioned it here as "convert fila to open libpcre2-8.so.0" on April 26), but several snapshots later the problem is still there. I've done a forced update of both gs and libpcre, but same result.. Anyone experiencing this? regards, Jogchum

2 months, 1 week

7
11
0 0

GTK program failing und Plasma Desktop /Leap 15.2

by Axel Braun

Hi, I'm currently working on the packaging of the Tryton 6 client (Python3- program) for openSUSE. When starting the client on a newly installed Leap 15.2/KDE I get the error: (process:6087): Gtk-ERROR **: 14:19:55.149: Can't create a GtkStyleContext without a display connection Trace/breakpoint trap (core dumped) I have found a similar error discussed on stack overflow, but w/o solution. python3-gobject and python3-gobject-cairo are installed. Any idea what might be missing on Leap 15.2? This works on TW! Thanks Axel

2 months, 1 week

2
2
0 0

A stop job is running ......

by Robin Klitscher

If this has been asked before, I’ve missed it and apologise. It’s certainly been asked elsewhere, though with no clear answer. Frequently, but not always, when closing (or rebooting) Leap 15.2, the shutdown stalls for 90 seconds with a message “A stop job is running for Session 2 of user <xxxx>”, together with a register counting down from 1 minute 30 seconds. When the countdown reaches zero the shutdown completes. There’s no other diagnostic information. I can’t invoke a terminal at that point to establish what’s what. But I have captured what could be useful info with systemctl -b -<x> across boots/shutdowns. Case 1. Excerpt from journal, “clean” shutdown, no significant delay: May 09 13:58:02 Corgi systemd[1]: Started Session 2 of user robin. May 09 15:08:45 Corgi systemd[1]: Stopping Session 2 of user robin. May 09 15:08:45 Corgi systemd-logind[1108]: Session 2 logged out. Waiting for processes to exit. May 09 15:08:48 Corgi systemd[1]: Stopped Session 2 of user robin. Case 2. Excerpt from journal, shutdown with "stop job running" and 90-sec delay: May 09 15:09:52 Corgi systemd[1]: Started Session 2 of user robin. May 09 15:15:51 Corgi systemd[1]: Stopping Session 2 of user robin. May 09 15:15:51 Corgi systemd-logind[1064]: Session 2 logged out. Waiting for processes to exit. May 09 15:17:21 Corgi systemd[1]: Stopped Session 2 of user robin. The timestamps of the last two lines in Case 1 show an inconsequential 3 second delay. Those for Case 2 show the full 90 second wait, seeming also to finger systemd-logind as the culprit. The most common suggestion in other forums is to reduce the default for DefaultTimeoutStopSec in /etc/systemd/system.conf from 90 seconds to 10. This works, but it only addresses the symptom, not the cause. Assuming the problem does lie somehow with systemd-logind on shutdown, is there something else I can do to fix it? Anyone? -- Robin K Wellington "Harbour City" New Zealand

2 months, 1 week

6
9
0 0

2021

2020

2019

2018

openSUSE Support May 2021