January 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1206768] New: system:snappy: GPG key is 7 days from expiration
by bugzilla_noreply＠suse.com 02 Jan '23

02 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206768 Bug ID: 1206768 Summary: system:snappy: GPG key is 7 days from expiration Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: screening-team-bugs(a)suse.de Reporter: stigpro(a)outlook.fr QA Contact: screening-team-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 863758 --> http://bugzilla.opensuse.org/attachment.cgi?id=863758&action=edit GPG Key expiration warning Doing `zypper refresh -f system_snappy` returns the joined message -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1206703] Sound stops working for MSI GS66 after kernel 5.14.21-150400.24.38 update
by bugzilla_noreply＠suse.com 01 Jan '23

01 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206703 http://bugzilla.opensuse.org/show_bug.cgi?id=1206703#c20 --- Comment #20 from Onur K��k <onur(a)delipenguen.net> --- I have tried with kernels 6.1.1-lp153.2.ge71748d (backport), 5.14.21-150400.2.gbf9e90f (home:tiwai:bsc1206703) and 5.14.21-150400.2.1.g466d6ae (home:tiwai:bsc1206703-2) all the kernels worked fine for me. Note I have verified snd-soc-core is not from updates. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206770] New: Screensaver does not turn off screen as set
by bugzilla_noreply＠suse.com 01 Jan '23

01 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206770 Bug ID: 1206770 Summary: Screensaver does not turn off screen as set Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When locking a GNOME session, the screen becomes black, but the screens does not turn off. The settings for energy and screen are set to turn off the screen after 5 minutes, but that does not happen. Messages related to DPMS: Jan 01 19:46:30 i7g4x4a /usr/lib/gdm/gdm-x-session[2672]: (II) AMDGPU(0): DPMS capabilities: StandBy Suspend Off Jan 01 19:46:31 i7g4x4a /usr/lib/gdm/gdm-x-session[2672]: (==) AMDGPU(0): DPMS enabled Jan 01 19:46:31 i7g4x4a /usr/lib/gdm/gdm-x-session[2672]: (II) Initializing extension DPMS Monitor hardware is "EIZO SX2462W", and graphics card used is "AMD Radeon 560" ("ATI Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X]") using driver amdgpu. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206410] New: systemd 252.3 regression - gpt-auto-generator cannot mount LUKS-encrypted /home
by bugzilla_noreply＠suse.com 01 Jan '23

01 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206410 Bug ID: 1206410 Summary: systemd 252.3 regression - gpt-auto-generator cannot mount LUKS-encrypted /home Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: opensuse(a)arnavion.dev QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- systemd 252.3-1.1 I have a LUKS-encrypted /home partition and use systemd-gpt-auto-generator to automount it instead of via crypttab / fstab entries. I updated my system from systemd v252.2 to v252.3 just now, and after a reboot was dropped in emergency shell because /home was not being auto-mounted. `systemctl status home.mount` said that `mount` failed with "unknown filesystem cryptsetup_LUKS", suggesting that systemd was trying to mount the partition directly instead of `cryptsetup open`'ing it first and mounting the `/dev/mapper/` node. Indeed, an Arch user also hit it and reported it at https://github.com/systemd/systemd/issues/25727 . There, upstream mentions a fix that can be cherry-picked. Would TW maintainers be willing to do that for the TW package? (I worked around it by manually creating the units that the generator should've created - home.unit and systemd-cryptsetup(a)home.service - under /etc/systemd/system, using another TW machine that I hadn't updated yet as reference.) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

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

01 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206500 http://bugzilla.opensuse.org/show_bug.cgi?id=1206500#c14 Martin Schmidt <martin.schmidt(a)io-warnemuende.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.schmidt@io-warnemuen | |de.de --- Comment #14 from Martin Schmidt <martin.schmidt(a)io-warnemuende.de> --- Happy new year! This bug is not restricted to a login procedure. It can be provoced with: dbus-update-activation-environment --verbose --systemd --all This command produces a long list of environment variables including bash-functions. The error message is: dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.InvalidArgs: Invalid environment assignments Dropping the option "--systemd" supresses the error. Also, unsetting the bash-functions (two line variables containing a newline) removes the error. The error appeared first after applying a long list of recommended patches as "online update" with yast. It is not easy to roll them back. Cheers, Martin -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206759] New: Audio output rerouted to different HDMI output after monitor suspend
by bugzilla_noreply＠suse.com 01 Jan '23

01 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206759 Bug ID: 1206759 Summary: Audio output rerouted to different HDMI output after monitor suspend Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: Michael.Zapf(a)mizapf.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This observation occurs with the recent update to 6.1.1. When my monitor goes into suspend and wakes up again, audio output is routed to the DisplayPort where the monitor is connected to instead of the HDMI port where my AV receiver is connected to. That is, after a monitor suspend/wakeup, I'm getting all audio output from the monitor's built-in speakers instead of the 5.1 audio system. This does not occur with 6.0.12. Also, since 6.1.1, the HDMI/DP ports are not enumerated as "HDMI 3" or "HDMI 4" but only as "HDMI/DisplayPort". However, I need to have control what HDMI output to use. Have a look at the screenshots: Settings for 6.0.12: http://www.mizapf.eu/files/audio_6.0.12.png Initial settings for 6.1.1 (after booting): http://www.mizapf.eu/files/audio_6.1.1_start.png Setting for 6.1.1 after DPMS suspend/wakeup: http://www.mizapf.eu/files/audio_6.1.1_wakeup.png -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1206683] New: kernel-default 6.1.0-1.1 freezes up 2 different machines
by bugzilla_noreply＠suse.com 01 Jan '23

01 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 Bug ID: 1206683 Summary: kernel-default 6.1.0-1.1 freezes up 2 different machines Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: scott.bradnick(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have 2 systems: 1) Intel Celeron J4115 and Intel GeminiLake [UHD Graphics 600] (driver: i915) 2) Intel Core i7-9850H and Intel CoffeeLake-H GT2 [UHD Graphics 630] along with NVIDIA TU117GLM [Quadro T1000 Mobile] #1 boots to a lightdm login but within 30s-1m of logging in, locks up completely with whatever was last on the screen frozen there and the mouse cursor missing. I'm not sure if it'd just lock up w/o me logging in - I'll try that next time. #2 seems to go through 99% of its boot process, then just as it would kick over to lightdm, it doesn't do anything but freeze up w/ something in the history of the boot process (what looks like dmesg output, the format at least). It boots w/ "splash=silent" and "quiet" REMOVED. #2 generally runs off NVIDIA's latest .run and all was fine prior, I could attempt to possibly use prime-select when booted to the previous kernel and use the iGPU to see if it freezes similarly to #1, but I haven't gotten too adventurous yet. Both work just fine on 6.0.12-1.1 and while I'm kicking around the idea of getting 6.1.1 from https://build.opensuse.org/package/show/Kernel:stable/kernel-default I haven't delved into that either. I'm happy to provide logs and more info, not sure if the freezing/hard lockups will make that impossible. -- You are receiving this mail because: You are on the CC list for the bug.

1 45

[Bug 864785] withlock does not always lock properly
by bugzilla_noreply＠suse.com 01 Jan '23

01 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=864785 http://bugzilla.opensuse.org/show_bug.cgi?id=864785#c4 Bernhard Wiedemann <bwiedemann(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |IN_PROGRESS Version|13.2 Milestone 0 |Current --- Comment #4 from Bernhard Wiedemann <bwiedemann(a)suse.com> --- Submitted a nice fix upstream: https://github.com/poeml/withlock/pull/5 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206575] BUG: kernel NULL pointer dereference
by bugzilla_noreply＠suse.com 01 Jan '23

01 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206575 https://bugzilla.suse.com/show_bug.cgi?id=1206575#c2 --- Comment #2 from Bernhard Wiedemann <bwiedemann(a)suse.com> --- I am running 5.14.21-150400.24.33-default for 11d now without the bug. But the old bug happened only after 35d without me doing anything, so there will always be a newer kernel already when it happens that rarely. Could it be related to my chronyd interacting with the clock more often, because it is part of pool.ntp.org? # cat /sys/devices/system/clocksource/clocksource0/current_clocksource tsc # cat /sys/devices/system/clocksource/clocksource0/available_clocksource tsc hpet acpi_pm -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1193599] intel_dp_detect [i915]] *ERROR* LSPCON init failed on port D
by bugzilla_noreply＠suse.com 01 Jan '23

01 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1193599 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(opendreas(a)gmail.c | |om) | -- You are receiving this mail because: You are on the CC list for the bug.

1 0