August 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1202245] New: System hang while editing APN settings on nm-connection-editor
by bugzilla_noreply＠suse.com 08 Aug '22

08 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202245 Bug ID: 1202245 Summary: System hang while editing APN settings on nm-connection-editor Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: stigpro(a)outlook.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:103.0) Gecko/20100101 Firefox/103.0 Build Identifier: When changing the APN when using `nm-connection-editor`, system systematically fully hangs Reproducible: Always Steps to Reproduce: 1. Have a `ModemManager`-compatible modem and have ModemManager.service enabled 2. Open `nm-connection-editor` (installable via `NetworkManager-connection-editor`) 3. Use the `+` and choose `Mobile Broadband` 4. Pass through the wizard choosing an ISP and arrive on the editing page 5. Use the `Change...` button Actual Results: Spawning the wizard makes the whole system deadlock requiring a force-reset of the system Expected Results: The wizard is re-ran and works as expected by changing the APN NetworkManager 1.38.2 ModemManager 1.18.6 NetworkManager-connection-editor 1.28.0 Snapshot 20220805 DE : Plasma 5.25.4 (Wayland) WM : kwin Suspecting a wayland/KDE issue, see attached logs -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1195463] New: smb not starting after patch openSUSE-SLE-15.3-2022-283=1
by bugzilla_noreply＠suse.com 08 Aug '22

08 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1195463 Bug ID: 1195463 Summary: smb not starting after patch openSUSE-SLE-15.3-2022-283=1 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor Assignee: suse-beta(a)cboltz.de Reporter: ralf.koelmel(a)kit.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 855811 --> http://bugzilla.opensuse.org/attachment.cgi?id=855811&action=edit smb systemd service output and apparmor extract smb service is not starting after applying recent samba patch openSUSE-SLE-15.3-2022-283=1 . It seems that the changes causes the apparmor "permission" problems. -- You are receiving this mail because: You are on the CC list for the bug.

1 26

[Bug 1202201] New: gpg2 2.3.7-1.1 doesn't properly detect Yubikey OpenPGP keys
by bugzilla_noreply＠suse.com 08 Aug '22

08 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202201 Bug ID: 1202201 Summary: gpg2 2.3.7-1.1 doesn't properly detect Yubikey OpenPGP keys Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: db(a)mail25.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After updating gpg2 from 2.3.6-2.2 to 2.3.7-1.1 Yubikey OpenPGP keys aren't properly detected anymore. I use it for SSH and this happens on 3 similar machines running Tumbleweed with the latest snapshot (20220805) and with 2 identical Yubikeys. The only configuration that I set is: >> # cat ~/.gnupg/gpg-agent.conf >> enable-ssh-support >> default-cache-ttl 600 >> max-cache-ttl 7200 ---gpg2-2.3.7-1.1--- --after plugging in the Yubikey-- >> # sudo journalctl -f >> rugp. 07 21:53:33 pc kernel: usb 1-4: new full-speed USB device number 4 using xhci_hcd >> rugp. 07 21:53:33 pc kernel: usb 1-4: New USB device found, idVendor=1050, idProduct=0407, bcdDevice= 5.43 >> rugp. 07 21:53:33 pc kernel: usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 >> rugp. 07 21:53:33 pc kernel: usb 1-4: Product: YubiKey OTP+FIDO+CCID >> rugp. 07 21:53:33 pc kernel: usb 1-4: Manufacturer: Yubico >> rugp. 07 21:53:33 pc kernel: input: Yubico YubiKey OTP+FIDO+CCID as /devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-4/1-4:1.0/0003:1050:0407.0009/input/input28 >> rugp. 07 21:53:33 pc kernel: hid-generic 0003:1050:0407.0009: input,hidraw3: USB HID v1.10 Keyboard [Yubico YubiKey OTP+FIDO+CCID] on usb-0000:03:00.0-4/input0 >> rugp. 07 21:53:33 pc kernel: hid-generic 0003:1050:0407.000A: hiddev97,hidraw4: USB HID v1.10 Device [Yubico YubiKey OTP+FIDO+CCID] on usb-0000:03:00.0-4/input1 >> rugp. 07 21:53:33 pc mtp-probe[7041]: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-4" >> rugp. 07 21:53:34 pc mtp-probe[7041]: bus: 1, device: 4 was not an MTP device >> rugp. 07 21:53:34 pc systemd[2023]: Reached target Smart Card. >> rugp. 07 21:53:34 pc mtp-probe[7069]: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-4" >> rugp. 07 21:53:34 pc mtp-probe[7069]: bus: 1, device: 4 was not an MTP device >> # ssh-add -l >> The agent has no identities. >> # gpg --card-status >> Reader ...........: 1050:0407:X:0 >> Application ID ...: D2760001240100000006137939780000 >> Application type .: OpenPGP >> Version ..........: 1.0 >> Manufacturer .....: ? >> Serial number ....: 13793978 >> Name of cardholder: [not set] >> Language prefs ...: [not set] >> Salutation .......: >> URL of public key : [not set] >> Login data .......: [not set] >> Signature PIN ....: not forced >> Max. PIN lengths .: -1 -2 0 >> PIN retry counter : 0 0 0 >> Signature counter : 0 >> Signature key ....: [none] >> Encryption key....: [none] >> Authentication key: [none] >> General key info..: [none] ---gpg2-2.3.6-2.2--- --after installing gpg2-2.3.6 (https://download.opensuse.org/history/20220802/tumbleweed/repo/oss/x86_64/g…), rebooting and inserting the Yubikey-- >> # sudo journalctl -f >> rugp. 07 22:03:11 pc kernel: usb 1-4: new full-speed USB device number 3 using xhci_hcd >> rugp. 07 22:03:11 pc kernel: usb 1-4: New USB device found, idVendor=1050, idProduct=0407, bcdDevice= 5.43 >> rugp. 07 22:03:11 pc kernel: usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 >> rugp. 07 22:03:11 pc kernel: usb 1-4: Product: YubiKey OTP+FIDO+CCID >> rugp. 07 22:03:11 pc kernel: usb 1-4: Manufacturer: Yubico >> rugp. 07 22:03:11 pc kernel: input: Yubico YubiKey OTP+FIDO+CCID as /devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-4/1-4:1.0/0003:1050:0407.0007/input/input27 >> rugp. 07 22:03:11 pc kernel: hid-generic 0003:1050:0407.0007: input,hidraw6: USB HID v1.10 Keyboard [Yubico YubiKey OTP+FIDO+CCID] on usb-0000:03:00.0-4/input0 >> rugp. 07 22:03:11 pc kernel: hid-generic 0003:1050:0407.0008: hiddev99,hidraw7: USB HID v1.10 Device [Yubico YubiKey OTP+FIDO+CCID] on usb-0000:03:00.0-4/input1 >> rugp. 07 22:03:11 pc mtp-probe[4432]: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-4" >> rugp. 07 22:03:11 pc mtp-probe[4432]: bus: 1, device: 3 was not an MTP device >> rugp. 07 22:03:11 pc systemd[1]: Reached target Smart Card. >> rugp. 07 22:03:11 pc systemd[2002]: Reached target Smart Card. >> rugp. 07 22:03:11 pc mtp-probe[4445]: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-4" >> rugp. 07 22:03:11 pc mtp-probe[4445]: bus: 1, device: 3 was not an MTP device >> # ssh-add -l >> 256 SHA256:**REDACTED** cardno:13 793 978 (ED25519) >> # gpg --card-status >> Reader ...........: 1050:0407:X:0 >> Application ID ...: D2760001240100000006137939780000 >> Application type .: OpenPGP >> Version ..........: 3.4 >> Manufacturer .....: Yubico >> Serial number ....: 13793978 >> Name of cardholder: [not set] >> Language prefs ...: [not set] >> Salutation .......: >> URL of public key : [not set] >> Login data .......: [not set] >> Signature PIN ....: not forced >> Key attributes ...: ed25519 cv25519 ed25519 >> Max. PIN lengths .: 127 127 127 >> PIN retry counter : 3 0 3 >> Signature counter : 4 >> KDF setting ......: off >> UIF setting ......: Sign=off Decrypt=off Auth=off >> Signature key ....: **REDACTED** >> created ....: 2022-05-23 17:27:13 >> Encryption key....: **REDACTED** >> created ....: 2022-05-23 17:27:13 >> Authentication key: **REDACTED** >> created ....: 2022-05-23 17:27:13 >> General key info..: [none] -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1202137] Python packlage loader does not find application in standard path
by bugzilla_noreply＠suse.com 08 Aug '22

08 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1202137 https://bugzilla.suse.com/show_bug.cgi?id=1202137#c4 --- Comment #4 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-RU-2022:10085-1: An update that has one recommended fix can now be installed. Category: recommended (moderate) Bug References: 1202137 CVE References: JIRA References: Sources used: openSUSE Backports SLE-15-SP4 (src): urlscan-0.9.9-bp154.2.3.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1184817] System becomes unstable and unusable when using wired network
by bugzilla_noreply＠suse.com 08 Aug '22

08 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1184817 https://bugzilla.suse.com/show_bug.cgi?id=1184817#c24 teo teo <php4fan(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(teo8976(a)gmail.com | |) | --- Comment #24 from teo teo <php4fan(a)gmail.com> --- I hope it is the right thing to do to clear the needinfo flag, since I've answered to the question, but my answer is "I don't know" and that's all I have and all I can have in the foreseeable future (I got yelled at in the past for forgetting to clear the needinfo flag when answering questions, so, hope I'm not doing it wrong the other way around) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1184817] System becomes unstable and unusable when using wired network
by bugzilla_noreply＠suse.com 08 Aug '22

08 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1184817 https://bugzilla.suse.com/show_bug.cgi?id=1184817#c23 --- Comment #23 from teo teo <php4fan(a)gmail.com> --- > Let me repeat Miroslav's question: does the problem persist with the latest system? I don't know, I have stopped using wired network again because: - I was having issue 1201557 for a while and at some point I thought it might be this same issue (but then that one did not go away by stopping using ethernet network, so I don't know) - I was also having 1200336, which never for a single moment I thought or think could be related, (I'm not saying it can't be) but was also forced me to stop using ethernet. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201994] Xen DomU unable to emulate audio device
by bugzilla_noreply＠suse.com 08 Aug '22

08 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1201994 https://bugzilla.suse.com/show_bug.cgi?id=1201994#c3 --- Comment #3 from James Fehlig <jfehlig(a)suse.com> --- (In reply to Erwin Pacua from comment #2) > (In reply to James Fehlig from comment #1) > > The message is from qemu, and it is only a deprecation warning. '-soundhw > > ac97' still works, but '-device AC97' is preferred. Is it not working for > > you? > > That is correct. Neither '-soundhw ac97' or '-device AC97' works. The only > difference is that with '-soundhw', xl complains and failed to start the > domU while with '-device AC97', domU runs but without an emulated sound > card. That is happening on all my vms (fedora, ubuntu, windows xp/7/10). That's odd. It works fine for me. With '-soundhw ac97' I see the warning in qemu-dm-<vm-name>.log, but either form gives me a sound card in the VM. E.g. from within my linux VM # hwinfo --sound 15: PCI 05.0: 0401 Multimedia audio controller [Created at pci.386] Unique ID: CvwD.Wvt18xt+7v7 SysFS ID: /devices/pci0000:00/0000:00:05.0 SysFS BusID: 0000:00:05.0 Hardware Class: sound Model: "Red Hat QEMU Virtual Machine" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x2415 "82801AA AC'97 Audio Controller" SubVendor: pci 0x1af4 "Red Hat, Inc." SubDevice: pci 0x1100 "QEMU Virtual Machine" Revision: 0x01 Driver: "snd_intel8x0" Driver Modules: "snd_intel8x0" I/O Ports: 0xc000-0xc3ff (rw) I/O Ports: 0xc600-0xc6ff (rw) IRQ: 36 (2 events) Module Alias: "pci:v00008086d00002415sv00001AF4sd00001100bc04sc01i00" Driver Info #0: Driver Status: snd_intel8x0 is active Driver Activation Cmd: "modprobe snd_intel8x0" Config Status: cfg=new, avail=yes, need=no, active=unknown In the configurations where the VM actually starts, you don't see a sound card at all in the VM? > name = "fedora" > type = "hvm" > xen_platform_pci = 1 > memory = 3000 > maxmem = 3000 > vcpus = 2 > soundhw = "ac97" > opengl = 0 > vga = "stdvga" > vnc = 1 > spice = 1 > spicehost = "127.0.0.1" > spiceport = 2006 > spicedisable_ticketing = 1 > spicevdagent = 1 > spice_image_compression = "off" > vif = [ 'bridge=xenbr20, mac=00:16:3e:4e:f9:29, model=e1000' ] > disk = [ > '/home/erwinp/xen/images/x86_64/linux/fedora35/fedora35.img,raw,xvda,rw', > ] > on_poweroff = "destroy" > serial = "pty" > boot = "c" My config is very similar to this one, with things such as 'vif' and 'disk' the only difference. > And here's the output when I tried to fire up one of them > > [root@pc1:/etc/xen/vm]# xl list > Name ID Mem VCPUs State > Time(s) > Domain-0 0 4000 4 r----- > 2057.3 > Xenstore 1 31 1 -b---- > 0.2 > [root@pc1:/etc/xen/vm]# > [root@pc1:/etc/xen/vm]# xl create fedora.cfg > Parsing config from fedora.cfg > libxl: warning: libxl_dm.c:1220:libxl__suse_node_to_path: replacing > '/home/erwinp/xen/images/x86_64/linux/fedora35/fedora35.img' with > '/dev/loop0' from /local/domain/0/backend/vbd/13/51712/node, just for > qemu-xen > libxl: error: libxl_dm.c:3173:device_model_spawn_outcome: Domain 13:domain > 13 device model: spawn failed (rc=-3) So apparently spawning qemu failed... > libxl: error: libxl_dm.c:3393:device_model_postconfig_done: Domain 13:Post > DM startup configs failed, rc=-3 > libxl: error: libxl_create.c:1869:domcreate_devmodel_started: Domain > 13:device model did not start: -3 > libxl: error: libxl_aoutils.c:652:libxl__kill_xs_path: Device Model already > exited > libxl: error: libxl_domain.c:1202:libxl__destroy_domid: Domain > 13:Non-existant domain > libxl: error: libxl_domain.c:1156:domain_destroy_callback: Domain 13:Unable > to destroy guest > libxl: error: libxl_domain.c:1083:domain_destroy_cb: Domain 13:Destruction > of domain failed > [root@pc1:/etc/xen/vm]# > [root@pc1:/etc/xen/vm]# > [root@pc1:/etc/xen/vm]# cat /var/log/xen/qemu-dm-fedora.log > char device redirected to /dev/pts/8 (label serial0) > qemu-system-i386: warning: '-soundhw ac97' is deprecated, please use > '-device AC97' instead > audio: warning: Using timer based audio emulation but no failure message in the log. Maybe more debug info from xl (try 'xl -vvv create fedora.cfg'), another peek at /var/log/xen/qemu-dm-fedora.log, and scanning syslog for any messages from dom0 kernel, xen scripts, etc. will give us some hints. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185084] VUL-0: CVE-2021-21373: nim: "nimble refresh" falls back to a non-TLS URL in case of error
by bugzilla_noreply＠suse.com 08 Aug '22

08 Aug '22

1 0

[Bug 1192712] VUL-1: CVE-2021-41259: nim: null byte accepted in getContent function, leading to URI validation bypass
by bugzilla_noreply＠suse.com 08 Aug '22

08 Aug '22

1 0

[Bug 1202147] New: tukit D-Bus API can't parse fields with comma
by bugzilla_noreply＠suse.com 08 Aug '22

08 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202147 Bug ID: 1202147 Summary: tukit D-Bus API can't parse fields with comma Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: iforster(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Using the Snapshot.List D-Bus API call from the prerelease version of transactional-update (4.0.0~rc4) reveals that the interface is designed improperly: The queried fields must not contain any comma, otherwise the returned string can't be parsed correctly any more. Example: busctl call org.opensuse.tukit /org/opensuse/tukit/Snapshot org.opensuse.tukit.Snapshot List "s" "number,description,default" would return a list such as "2334,Hello, this is a test!,no" -- You are receiving this mail because: You are on the CC list for the bug.

1 3