January 2025 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1011891] Add *.timer of snapper to preset list
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1011891 Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1235020] Hard freeze workqueue lockup mediatek bluetooth
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1235020 https://bugzilla.suse.com/show_bug.cgi?id=1235020#c7 --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- Could you check 6.12.8 kernel in OBS Kernel:stable repo? https://download.opensuse.org/repositories/Kernel:/stable/standard/ It contains a few Mediatek BT patches and those might address your problem. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1235020] Hard freeze workqueue lockup mediatek bluetooth
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1235020 https://bugzilla.suse.com/show_bug.cgi?id=1235020#c6 --- Comment #6 from Andrea Ippolito <andrea.ippo(a)gmail.com> --- (In reply to Takashi Iwai from comment #5) > Thanks! So it's triggered at btusb_disconnect() -> hci_unregister_dev(), > and likely the same issue as bsc#1231599. > > The Mediatek driver in the upstream is still in a bad shape, unfortunately. > We applied a revert but this doesn't seem covering the all issues. No problem, thanks to you for looking into it! Is there anything else I can help with? I know this is missing steps to reproduce but TBH I don't think I was doing anything special at the time, actually I'm not even sure my only BT device (a pair of earbuds) was out of the charging case and connected at the time this happened! In any case I will try and pay more attention next time this happens and update here, although TBH I hope you already have a clue about what could be the problem :-) Every time this happens it completely kills productivity (and potentially causes loss of work, too :( ) Have a nice day :) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201579] doxygen varies output from readdir order
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1201579 https://bugzilla.suse.com/show_bug.cgi?id=1201579#c15 --- Comment #15 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1201579) was mentioned in https://build.opensuse.org/request/show/1234687 Factory / doxygen -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1160629] doxygen: include patch with fix for QCH generation with kdeclarative & others
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1160629 https://bugzilla.suse.com/show_bug.cgi?id=1160629#c6 --- Comment #6 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1160629) was mentioned in https://build.opensuse.org/request/show/1234687 Factory / doxygen -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1062303] trackerbug: packages do not build reproducibly from randomness
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1062303 https://bugzilla.suse.com/show_bug.cgi?id=1062303#c51 --- Comment #51 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1062303) was mentioned in https://build.opensuse.org/request/show/1234687 Factory / doxygen -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1235020] Hard freeze workqueue lockup mediatek bluetooth
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1235020 https://bugzilla.suse.com/show_bug.cgi?id=1235020#c5 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(andrea.ippo@gmail | |.com) | --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- Thanks! So it's triggered at btusb_disconnect() -> hci_unregister_dev(), and likely the same issue as bsc#1231599. The Mediatek driver in the upstream is still in a bad shape, unfortunately. We applied a revert but this doesn't seem covering the all issues. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1235020] Hard freeze workqueue lockup mediatek bluetooth
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1235020 https://bugzilla.suse.com/show_bug.cgi?id=1235020#c4 --- Comment #4 from Andrea Ippolito <andrea.ippo(a)gmail.com> --- (In reply to Takashi Iwai from comment #3) > (In reply to Andrea Ippolito from comment #1) > > There are also entries like: > > > > Jan 02 18:19:35 andromeda kernel: Oops: general protection fault, probably > > for non-canonical address 0xdead000000000108: 0000 [#1] PREEMPT SMP NOPTI > > That's crucial info, please give the full output including this stack trace. Hi Takashi, sorry for not explaining this well. That line was an excerpt from a pastebin I linked in my initial post: https://pastebin.com/n3m1S8B7 That paste however was a stripped down version of the journal, where I removed previous events. In case the full boot is needed, you will find it here: https://pastebin.com/zy6fWF0V relevant timestamps are in the title (command: sudo journalctl -b -5 > 2025-01-02-workqueue-lockup-timestamps-18:19:35-18:20:33.txt) Thanks a lot in advance! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233824] New: [s390x] gnome-remote-desktop RDP-server does not start on s390x
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1233824 Bug ID: 1233824 Summary: [s390x] gnome-remote-desktop RDP-server does not start on s390x Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: martin.sirringhaus(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I can't get RDP to work on s390x, so I tried the same steps on a x86_64 VM and on s390x: ``` sudo zypper in -y gnome-remote-desktop freerdp-server # You probably have to do `su -` here first for this one: sudo -u gnome-remote-desktop winpr-makecert \ -silent -rdp -path ~gnome-remote-desktop rdp-tls # Set RDP_USER and RDP_PASS to whatever you want sudo grdctl --system rdp set-credentials "$RDP_USER" "$RDP_PASS" sudo grdctl --system rdp set-tls-key /var/lib/gnome-remote-desktop/rdp-tls.key sudo grdctl --system rdp set-tls-cert /var/lib/gnome-remote-desktop/rdp-tls.crt sudo grdctl --system rdp enable sudo systemctl --now enable gnome-remote-desktop.service ``` On both systems I get basically the same output for this: ``` # grdctl --system status Init TPM credentials failed because No TPM device found, using GKeyFile as fallback. Overall: Unit status: active RDP: Status: enabled Port: 3389 TLS certificate: /var/lib/gnome-remote-desktop/rdp-tls.crt TLS fingerprint: 1f:76:bb:d3:bd:42:fd:51:af:e7:89:64:e1:00:c2:78:d9:16:20:63:2b:08:84:ac:38:4e:79:48:c9:4a:07:db TLS key: /var/lib/gnome-remote-desktop/rdp-tls.key Username: (hidden) ``` `systemctl start gnome-remote-desktop` works fine on both systems, telling me that the service is up and running. On my VM, however, I get ``` Nov 27 14:04:03 localhost.localdomain systemd[1]: Starting GNOME Remote Desktop... Nov 27 14:04:03 localhost.localdomain gnome-remote-de[4244]: Init TPM credentials failed because No TPM device found, using GKeyFile as fallback Nov 27 14:04:03 localhost.localdomain systemd[1]: Started GNOME Remote Desktop. Nov 27 14:04:04 localhost.localdomain gnome-remote-de[4244]: RDP server started localhost:~ # ss -punta | grep gnome tcp LISTEN 0 10 *:3389 *:* users:(("gnome-remote-de",pid=4244,fd=9)) ``` whereas on s390x, I get: ``` Nov 27 12:47:41 firefox.prg2.suse.org systemd[1]: Starting GNOME Remote Desktop... Nov 27 12:47:41 firefox.prg2.suse.org gnome-remote-de[15170]: Init TPM credentials failed because No TPM device found, using GKeyFile as fallback Nov 27 12:47:41 firefox.prg2.suse.org systemd[1]: Started GNOME Remote Desktop. firefox:~ # ss -punta | grep gnome firefox:~ # ``` Setting G_MESSAGES_DEBUG=all didn't reveal anything, either. Basically, all RDP-related output is missing on s390x. No additional info (that is not also logged on x86_64 with this env-variable). The RDP-server simply doesn't start up on s390x without any errors or logging. -- You are receiving this mail because: You are on the CC list for the bug.

1 35

[Bug 1234405] devel:microos/libeconf: Bug libeconf 0.7.5 causes systemd/sddm/pam/libc crash and prevents login
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234405 https://bugzilla.suse.com/show_bug.cgi?id=1234405#c17 --- Comment #17 from pallas wept <pallaswept(a)proton.me> --- (In reply to Stefan Schubert from comment #16) > I have tested, but there is no difference. Thanks Stefan. I tested the above procedure from JS and I also cannot reproduce their fault: > sudo touch /etc/environment.d/a.conf /etc/environment.d/b.conf > sudo echo hi hi > su Pallas:/home/pallaswept # I guess JS will need to look at their system to help to reproduce this. -- You are receiving this mail because: You are on the CC list for the bug.

1 0