January 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1114273] New: Broadband connection established but all packages dropped
by bugzilla_noreply＠novell.com 10 Jan '23

10 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1114273 Bug ID: 1114273 Summary: Broadband connection established but all packages dropped Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dpbasti(a)wp.pl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I tested https://bugzilla.opensuse.org/show_bug.cgi?id=1104571 on 2018.10.31 Tumbleweeed. The same result as on Leap15. All RX and all TX packages are dropped Connection is established, signal strength is good, IP is obtained, Routing is set to default gw received from 4g modem, DNS servers are also received. Cannot even ping gateway. The same setup works as soon as I boot Ubuntu with no different settings in NetworkManager. wwan0: flags=4291<UP,BROADCAST,RUNNING,NOARP,MULTICAST> mtu 1500 inet 10.111.71.20 netmask 255.255.255.248 broadcast 10.111.71.23 inet6 fe80::73fb:926a:b538:f135 prefixlen 64 scopeid 0x20<link> ether 7a:c6:53:8c:bf:03 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 1280 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 42 dropped 0 overruns 0 carrier 0 collisions 0 -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1200457] New: iscsi.service cannot start at microos
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1200457 Bug ID: 1200457 Summary: iscsi.service cannot start at microos 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: matwey.kornilov(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, I am running microOS 20220611 with open-iscsi-2.1.7-90.1.x86_64. When I try to start iscsi.service the following error appears: Jun 12 19:16:09 localhost.localdomain systemd[1]: Starting Login and scanning of iSCSI devices... Jun 12 19:16:09 localhost.localdomain iscsiadm[1009]: iscsiadm: Maybe you are not root? Jun 12 19:16:09 localhost.localdomain iscsiadm[1009]: iscsiadm: Could not lock discovery DB: /etc/iscsi/lock.write: No such file or directory Jun 12 19:16:09 localhost.localdomain iscsiadm[1009]: iscsiadm: No records found Jun 12 19:16:09 localhost.localdomain iscsiadm[1017]: iscsiadm: Maybe you are not root? Jun 12 19:16:09 localhost.localdomain iscsiadm[1017]: iscsiadm: Could not lock discovery DB: /etc/iscsi/lock.write: No such file or directory Jun 12 19:16:09 localhost.localdomain iscsiadm[1017]: iscsiadm: No records found Jun 12 19:16:09 localhost.localdomain iscsiadm[1018]: iscsiadm: Could not get list of targets from firmware. (err 21) Jun 12 19:16:09 localhost.localdomain systemd[1]: Finished Login and scanning of iSCSI devices. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1187195] New: pulseaudio battery drain
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1187195 Bug ID: 1187195 Summary: pulseaudio battery drain Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: dpbasti(a)wp.pl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- pulsaudio consumes half of total power needed by system powertow run on dell xps17 shows 17W drain of pulsaudio. If input is set to capture mode (enough to enable mic capture in alsamixer) pulsaudio then consumes even double of that. For reference the whole Fedora 34 desktop consumes about 6W on the same machine ! -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1206503] Steam Big Picture Segmentation Fault
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206503 https://bugzilla.suse.com/show_bug.cgi?id=1206503#c3 Martin Li��ka <martin.liska(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS Assignee|rguenther(a)suse.com |martin.liska(a)suse.com --- Comment #3 from Martin Li��ka <martin.liska(a)suse.com> --- Bisected the issue and I've just asked the libstdc++ maintainer if it's expected or not. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206710] Disk encryption password now requested only once
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206710 https://bugzilla.suse.com/show_bug.cgi?id=1206710#c3 Michael Chang <mchang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mchang(a)suse.com --- Comment #3 from Michael Chang <mchang(a)suse.com> --- Unlike the SDB article where that key files needs to be in the root partition and attached onto initrd, the feature requires no additional persistent storage other than your brain cells. The grub can be instructed by /etc/crypttab to handover the password users have just typed to systemd-cryptsetup on the fly to the initramfs before root file system is mounted and then gets destroyed as linux kernel relinquished the initrd memory. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206697] Wireless network disappears on Raspberry Pi 4B after kernel-default 6.0.12
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206697 David Mair <dmair(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dmair(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206791] New: drbd: fix build error against kernel v6.1.1
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206791 Bug ID: 1206791 Summary: drbd: fix build error against kernel v6.1.1 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: High Availability Assignee: ha-bugs(a)suse.de Reporter: heming.zhao(a)suse.com QA Contact: qa-bugs(a)suse.de CC: zzhou(a)suse.com Depends on: 1204596 Found By: --- Blocker: --- kernel v6.1.2 block layer APIs changed and was blocking drbd building. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1206758] xhci_hcd periodically not ready on resume
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206758 https://bugzilla.suse.com/show_bug.cgi?id=1206758#c18 --- Comment #18 from Pablo Sanchez <pablo(a)blueoakdb.com> --- Hmmmmm, seems it stopped working. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205349] New: Audio (speaker) does not work on HP Pavillon all-in-one 24
by bugzilla_noreply＠suse.com 09 Jan '23

09 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1205349 Bug ID: 1205349 Summary: Audio (speaker) does not work on HP Pavillon all-in-one 24 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: sunshine232196(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- No speaker audio (headphones works well) on my HP Pavilion All-in-One 24. Clicking noises on and off. Ive gathered enough information but I can put all the pieces together. Im not sure if its something devs here can fix or if its a feature that has to be implemented from intel. When configuring from Yast Sound I get `The kernel module snd-sof-pci-intel-cnl for sound support. Could not be loaded.` Here are two recent comments in HP forums, in one of them they give details how to install the RealTek driver but I kept getting the `kernel headers not found` problem (even though I had them installed). https://h30434.www3.hp.com/t5/Notebook-Audio/Linux-no-sound-from-speakers/t… and https://h30434.www3.hp.com/t5/Notebook-Audio/No-sound-from-internal-speaker… Operating System: openSUSE Tumbleweed 20221110 KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.7 Kernel Version: 6.0.7-1-default (64-bit) Graphics Platform: X11 Processors: 6 �� Intel�� Core�� i5-9400T CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel�� UHD Graphics 630 Manufacturer: HP Product Name: HP Pavilion All-in-One 24-xa0xxx lspci (below) -------------------------------------------------------- 00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07) 00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-S GT2 [UHD Graphics 630] 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10) 00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10) 00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10) 00:14.5 SD Host controller: Intel Corporation Device a375 (rev 10) 00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10) 00:17.0 SATA controller: Intel Corporation Cannon Lake PCH SATA AHCI Controller (rev 10) 00:1c.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #5 (rev f0) 00:1c.5 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #6 (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #9 (rev f0) 00:1f.0 ISA bridge: Intel Corporation H370 Chipset LPC/eSPI Controller (rev 10) 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10) 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) 00:1f.5 Serial bus controller: Intel Corporation Cannon Lake PCH SPI Controller (rev 10) 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter 03:00.0 Non-Volatile memory controller: SK hynix BC511 -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1206500] After update: when ssh'ing to other 15.4: Invalid environment assignments
by bugzilla_noreply＠suse.com 09 Jan '23

09 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206500 http://bugzilla.opensuse.org/show_bug.cgi?id=1206500#c15 Giacomo Comes <comes(a)naic.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |comes(a)naic.edu --- Comment #15 from Giacomo Comes <comes(a)naic.edu> --- I was investigating this problem and here is what I found. you can reproduce the bug with three shell commands: In a bash shell define a function: dummy() { : ; } export the function: export -f dummy at this point bash has defined an environment variable called: BASH_FUNC_dummy%% Now run: dbus-update-activation-environment --systemd --all you will get the error message: dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.InvalidArgs: Invalid environment assignments I think the error is due to the fact that BASH_FUNC_dummy%% is an illegal enviromnet variable name. bash creates them internally with such strange name probably to differentiate exported functions name from normal exported variables. The fix should be for dbus-update-activation-environment to discard environment variable with forbidden characters in their name (or, to put it in another way, ignore exported functions names) -- You are receiving this mail because: You are on the CC list for the bug.

1 0