July 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1212915] wine-staging 8.11 segfault
by bugzilla_noreply＠suse.com 03 Jul '23

03 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212915 https://bugzilla.suse.com/show_bug.cgi?id=1212915#c3 --- Comment #3 from Marcus Meissner <meissner(a)suse.com> --- i applied the patches we have in Emulators/wine to Emulators:Wine/wine too now, lets see if it helps. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212629] All USB ports and attached devices are abruptly disconnected, and data is lost.
by bugzilla_noreply＠suse.com 03 Jul '23

03 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212629 https://bugzilla.suse.com/show_bug.cgi?id=1212629#c7 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |oneukum(a)suse.com --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- The log contains: [ 790.313485] xhci_hcd 0000:02:00.3: xHCI host not responding to stop endpoint command [ 790.313514] xhci_hcd 0000:02:00.3: xHCI host controller not responding, assume dead [ 790.313556] xhci_hcd 0000:02:00.3: HC died; cleaning up So it looks like a USB host issue. Is it a built-in USB or a docking station? In anyway, tossed to Oliver, as this seems to be a USB driver problem. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212627] NetworkManager: network interface not configured before SSH daemon is started
by bugzilla_noreply＠suse.com 03 Jul '23

03 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212627 https://bugzilla.suse.com/show_bug.cgi?id=1212627#c13 --- Comment #13 from Jonathan Kang <songchuan.kang(a)suse.com> --- (In reply to Adam Majer from comment #12) > > setting may-fail to false, seem to fix my problem. Thanks! > > The question is then, shouldn't manually defined settings automatically > default to may-fail=no, if there is no specific value set in this field? By default, NetworkManager set this property for each new connection to TRUE. This is a safe default for all kinds of connections. Setting this to FALSE may cause infinite waiting for scenarios where users don't have an IPv6 address. > > I assume this probably should be discussed with upstream when may-fail > should default to false and when to true. The current case when it always > defaults to true is ... confusing. I think this is more of a problem about NetworkManager deciding it's time to quit NetworkManager-wait-online when it got an IPv4 address(without internet access), but at that time the manual IPv6 address is still in the process of pending/configuring. It sure is a good idea to talk to upstream developers and see what they think about this issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212942] Unable to start VM virtiofsd died unexpectedly
by bugzilla_noreply＠suse.com 03 Jul '23

03 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212942 Charles Arnold <carnold(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|virt-bugs(a)suse.de |kvm-bugs(a)suse.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212474] Nautilus: Segmentation fault (core dumped) with libpython3_11-1_0-x86-64-v3 (works with non-v3 optimized library)
by bugzilla_noreply＠suse.com 03 Jul '23

03 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212474 https://bugzilla.suse.com/show_bug.cgi?id=1212474#c23 --- Comment #23 from Daniel Garcia <daniel.garcia(a)suse.com> --- I've been debugging and trying different approximations to detect what's happening here and I've discovered something. Looks like the python-nautilus extension looks for the libpython.so [1] in the default libdir and is using a different version from the loaded v3. I've tested building with the PYTHON_LIBPATH pointing to the v3 and in that case it works. Now I just need to patch to make it sure that it picks the correct version depending on the installed libpython. [1] https://gitlab.gnome.org/GNOME/nautilus-python/-/blob/master/src/nautilus-p… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212775] go1.16 fails to build with new update kernel-sources 6.4
by bugzilla_noreply＠suse.com 03 Jul '23

03 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212775 https://bugzilla.suse.com/show_bug.cgi?id=1212775#c10 --- Comment #10 from Michal Suchanek <msuchanek(a)suse.com> --- There is a minimal reproducer in the kernel.org but that does not require go. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212852] python310 ( 3.10.12) update breaks python-bleach (6.0.0)
by bugzilla_noreply＠suse.com 03 Jul '23

03 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212852 https://bugzilla.suse.com/show_bug.cgi?id=1212852#c3 Ana Guerrero <ana.guerrero(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|IN_PROGRESS |RESOLVED --- Comment #3 from Ana Guerrero <ana.guerrero(a)suse.com> --- Resolved. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212775] go1.16 fails to build with new update kernel-sources 6.4
by bugzilla_noreply＠suse.com 03 Jul '23

03 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212775 Michal Suchanek <msuchanek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.kernel.org | |/show_bug.cgi?id=217624 CC| |msuchanek(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212926] tmpfiles suse.conf conflicts with lockdev.conf
by bugzilla_noreply＠suse.com 03 Jul '23

03 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212926 https://bugzilla.suse.com/show_bug.cgi?id=1212926#c1 Franck Bui <fbui(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(lnussel(a)suse.com) CC| |fbui(a)suse.com, | |lnussel(a)suse.com --- Comment #1 from Franck Bui <fbui(a)suse.com> --- Ludwig, it seems that /run/lock shouldn't be defined by lockdev.conf. Maybe it does so for supporting lockdev on systems without systemd but /run/lock is a common location used for other purposes too hence defining it in a "low-level" package, such as filesystem, makes more sense. systemd currently keeps the definition for historical reasons but I think filesystem makes more sense. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212929] Subvolume layout should not depend on whether snapshots are enabled during installation
by bugzilla_noreply＠suse.com 03 Jul '23

03 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212929 https://bugzilla.suse.com/show_bug.cgi?id=1212929#c2 Arvin Schnell <aschnell(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(aschnell(a)suse.com | |) | --- Comment #2 from Arvin Schnell <aschnell(a)suse.com> --- AFAIU the suggestion is not to remove to @ subvolume but to install into @/.snapshot/1/subvolume (the @ is missing in comment #0). That sound like a good idea. -- You are receiving this mail because: You are on the CC list for the bug.

1 0