May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1160672] mingw*-runtime + winpthreads does not build reproducibly
by bugzilla_noreply＠suse.com 22 May '24

22 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1160672 https://bugzilla.suse.com/show_bug.cgi?id=1160672#c1 --- Comment #1 from Jan Engelhardt <jengelh(a)inai.de> --- dzpwt? dfqwt? dstut? I don't see any of those names in the *filesystem*. Unlike bug #1137320 about wine, the build log for windows:mingw:win32/mingw32-runtime.openSUSE_Factory.x86_64 even reports same-result:: Retried build at Mon May 20 17:09:40 2024 returned same result, skipped What is noticable though: $ nm /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libwinpthread.dll.a libwinpthread_1_dll_d000138.o: 0000000000000000 i .idata$4 0000000000000000 i .idata$5 0000000000000000 i .idata$7 0000000000000000 I libwinpthread_1_dll_iname libwinpthread_1_dll_d000000.o: 0000000000000000 i .idata$2 0000000000000000 i .idata$4 0000000000000000 i .idata$5 0000000000000000 I _head_libwinpthread_1_dll U libwinpthread_1_dll_iname .dll.a files are generated by ld; iff there is any randomness to the fake .o names, that would be on binutils: $ echo 'void foo() {} void bar() {}' >x.c $ x86_64-w64-mingw32-gcc -shared x.c -Wl,--out-implib x.dll.a -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222534] No wired network after hibernation
by bugzilla_noreply＠suse.com 22 May '24

22 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1222534 https://bugzilla.suse.com/show_bug.cgi?id=1222534#c4 Jonathan Kang <songchuan.kang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jonzn4suse(a)hotmail.com Flags| |needinfo?(jonzn4suse@hotmai | |l.com) --- Comment #4 from Jonathan Kang <songchuan.kang(a)suse.com> --- Please provide a detailed NetworkManager logs. To collect those, add the following to /etc/NetworkManager/conf.d/logging-trace.conf, restart NetworkManager, reproduce this issue, and find the output of `journalctl -b`. > [logging] > level=trace -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1160672] mingw*-runtime + winpthreads does not build reproducibly
by bugzilla_noreply＠suse.com 22 May '24

22 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1160672 Bernhard Wiedemann <bwiedemann(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jengelh(a)inai.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1223003] jrnl utility give error AttributeError: '_PasswordRetriever' object has no attribute 'encode' when encryption is enabled
by bugzilla_noreply＠suse.com 22 May '24

22 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223003 https://bugzilla.suse.com/show_bug.cgi?id=1223003#c1 Malcolm Lewis <malcolmlewis(a)linuxmail.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS CC| |andrea.manzini(a)suse.com Flags| |needinfo?(andrea.manzini@su | |se.com) --- Comment #1 from Malcolm Lewis <malcolmlewis(a)linuxmail.org> --- (In reply to Andrea Manzini from comment #0) > --- to reproduce on Tumbleweed: > > # zypper install jrnl > > The following 12 NEW packages are going to be installed: > jrnl python311-ansiwrap python311-colorama python311-markdown-it-py > python311-mdurl python311-parsedatetime > python311-Pygments python311-pytz python311-pytz-deprecation-shim > python311-rich python311-textwrap3 python311-tzlocal > > > $ rpm -qi jrnl > Name : jrnl > Version : 4.0.1 > Release : 1.4 > Architecture: noarch > Install Date: gio 18 apr 2024, 08:14:47 > Group : Unspecified > Size : 514138 > License : GPL-3.0-only > Signature : RSA/SHA512, ven 29 mar 2024, 17:09:55, Key ID 35a2f86e29b700a4 > Source RPM : jrnl-4.0.1-1.4.src.rpm > Build Date : sab 19 ago 2023, 16:03:40 > Build Host : reproducible > Packager : https://bugs.opensuse.org > Vendor : openSUSE > URL : https://jrnl.sh > Summary : Collect your thoughts and notes without leaving the command > line > Description : > Simple journal application for the command line. You can use it to > easily create, search, and view journal entries. Journals are stored > as human-readable plain text, and can also be encrypted using AES > encryption. > Distribution: openSUSE Tumbleweed > > --- remove any previous configuration > $ rm -rf $HOME/.config/jrnl > > --- create a new journal choosing Yes when asked to encrypt the data > $ jrnl > Path to your journal file (leave blank for > /home/andrea/.local/share/jrnl/journal.txt): > Do you want to encrypt your journal? (You can always change this later) > [y/N] y > ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓ > ┃ Journal will be encrypted ┃ > ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛ > Do you want jrnl to use colors when displaying entries? (You can always > change this later) [Y/n] > ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓ > ┃ jrnl configuration created at /home/andrea/.config/jrnl/jrnl.yaml ┃ > ┃ For advanced features, read the docs at https://jrnl.sh ┃ > ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛ > ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓ > ┃ Journal 'default' created at /home/andrea/.local/share/jrnl/journal.txt ┃ > ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛ > ┏━ Error ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓ > ┃ AttributeError ┃ > ┃ '_PasswordRetriever' object has no attribute 'encode' ┃ > ┃ ┃ > ┃ This is probably a bug. Please file an issue at: ┃ > ┃ https://github.com/jrnl-org/jrnl/issues/new/choose ┃ > ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛ > > > --- any subsequent journal entry will give the same error > $ jrnl foobar > ┏━ Error ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓ > ┃ AttributeError ┃ > ┃ '_PasswordRetriever' object has no attribute 'encode' ┃ > ┃ ┃ > ┃ This is probably a bug. Please file an issue at: ┃ > ┃ https://github.com/jrnl-org/jrnl/issues/new/choose ┃ > ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛ > > --- note: the bug is not present in upstream, installing the package with > pipx works, so most likely the issue is on the package dependencies So your issue has been reopened upstream. The work around at present is to uninstall python311-keyring-keyutils, create the encrypted file and password to be saved into the keyring. After that all should be good. You can re-install python311-keyring-keyutils. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224152] MicroOS + systemd-boot: boot menu title does not match Tumbleweed snapshot number
by bugzilla_noreply＠suse.com 22 May '24

22 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224152 https://bugzilla.suse.com/show_bug.cgi?id=1224152#c1 Gary Ching-Pang Lin <glin(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aplanas(a)suse.com, | |glin(a)suse.com Assignee|bootloader-maintainers@suse |lnussel(a)suse.com |.de | --- Comment #1 from Gary Ching-Pang Lin <glin(a)suse.com> --- Reassign the bug to the sdbootutil maintainer. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1223858] Cannot mount kerberized nfs4 share with kernel 5.14.21-150500.55.59-default
by bugzilla_noreply＠suse.com 22 May '24

22 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223858 https://bugzilla.suse.com/show_bug.cgi?id=1223858#c12 --- Comment #12 from Neil Brown <nfbrown(a)suse.com> --- *** Bug 1224340 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224309] libreoffice failing to build with ICU 75
by bugzilla_noreply＠suse.com 21 May '24

21 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224309 https://bugzilla.suse.com/show_bug.cgi?id=1224309#c2 Martin Schreiner <martin.schreiner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #2 from Martin Schreiner <martin.schreiner(a)suse.com> --- In progress. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1223352] X11 sessions do not unlock after locking for inactivity
by bugzilla_noreply＠suse.com 21 May '24

21 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223352 https://bugzilla.suse.com/show_bug.cgi?id=1223352#c4 --- Comment #4 from epp(a)mcom.com --- Created attachment 875006 --> https://bugzilla.suse.com/attachment.cgi?id=875006&action=edit Photo of display with X11 session not unlocking after inactivity -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1223352] X11 sessions do not unlock after locking for inactivity
by bugzilla_noreply＠suse.com 21 May '24

21 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223352 https://bugzilla.suse.com/show_bug.cgi?id=1223352#c3 --- Comment #3 from epp(a)mcom.com --- (In reply to Stefan Dirsch from comment #2) > Could this please retested with current TW, please? TW 20240520: Yes, still occurs. Attaching photo of display. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222346] snapperd can't work
by bugzilla_noreply＠suse.com 21 May '24

21 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1222346 https://bugzilla.suse.com/show_bug.cgi?id=1222346#c6 --- Comment #6 from Wenruo Qu <wqu(a)suse.com> --- I'm wondering if snapper is not handling rescan correctly. Yes, qgroup is very heavy, but that's so far the only way to get accurate accounting numbers, considering how many tricks we put to get super fast snapshotting. All the super fast snapshotting has put a lot of complexity to qgroups. Not to mention the extra complexity from multi-level qgroups, utilized by snapper. But for the RESCAN_WAIT returns immeidately problem, I think it's something from the snapper side. Snapper should check if qgroup is even enabled and rescan is running. Or RESCAN_WAIT ioctl immediately return 0 if qgroup rescan is not running nor qgroup is enabled. Any clue how snapper triggers qgroup rescan? Did it check if qgroup is enabled or handles qgroup rescan return value correctly? -- You are receiving this mail because: You are on the CC list for the bug.

1 0