June 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1212840] New: colord-gtk segfault when turning monitors on again
by bugzilla_noreply＠suse.com 29 Jun '23

29 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212840 Bug ID: 1212840 Summary: colord-gtk segfault when turning monitors on again Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: All OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: mkubecek(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- (tracking only, issue identified and fixed in upstream bug tracker) upstream tracker link: https://github.com/hughsie/colord-gtk/issues/22 On a system with two DisplayPort attached monitors, turning them off and on again results in a reproducible crash of darktable application. The segfault is caused by a bug in colord-gtk which has been fixed in upstream by commit 8a395709fa0c9: https://github.com/hughsie/colord-gtk/commit/8a395709fa0c9 Going to submit a SR today. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1212675] [Build 20230623] openQA test fails in login_test: system now logs in automatically
by bugzilla_noreply＠suse.com 29 Jun '23

29 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212675 https://bugzilla.suse.com/show_bug.cgi?id=1212675#c1 Jia Zhaocong <zcjia(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zcjia(a)suse.com --- Comment #1 from Jia Zhaocong <zcjia(a)suse.com> --- https://openqa.opensuse.org/tests/3391741#step/login_test/6 shows that "Automatic Login" is by default off which is different from previous runs. In the VM environment, I can't toggle this option, and it causes "accounts-daemon" to coredump. On my physical machine, I can't toggle this option either: "SetAutomaticLogin call failed: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying". -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212815] kitty doesn't start on SLED
by bugzilla_noreply＠suse.com 29 Jun '23

29 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212815 https://bugzilla.suse.com/show_bug.cgi?id=1212815#c2 Adam Majer <amajer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Other Graphical |Packages |Applications | Product|SUSE Linux Enterprise |openSUSE Backports |Desktop 15 SP4 | QA Contact| |packagehub-bugs(a)suse.com Group|SUSE Enterprise Partner | Version|unspecified |SLE-15-SP4 --- Comment #2 from Adam Majer <amajer(a)suse.com> --- (In reply to Scott Bradnick from comment #1) > > ModuleNotFoundError: No module named 'importlib.resources' > > `zypper in python3-importlib_resources` will fix it. That's quite the old > version of kitty and certainly predates my involvement with it. Seems like > it should have a "Recommends: python3-importlib-resources", but possilbly > the tester already had that library and it went un-noticed. My .spec for > kitty doesn't include it and if I try to remove > python311-importlib-resources (granted, in TW, where it's current) it wants > to take 2 other packages with it. > > Personally, I'm not sure we should expect a current Kitty in SLE ~ it now > involves (a very recent) "go" which [possibly?] wouldn't be quick/easy to > backport on any type of regular basis. The package has BuildRequires: python3-importlib_resources but is missing the requires ;). This requirement is also missing in Factory, btw, so maybe when you update it in Factory to have all Requires that are needed, you can also send it to Backports for Leap/SLE users. Regarding Golang, we are shipping the version that would be required. isc cat SUSE:SLE-15:Update go go.spec | grep Version Version: 1.20 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207852] INDI 2.0 breaks Stellarium and PHD2
by bugzilla_noreply＠suse.com 29 Jun '23

29 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1207852 https://bugzilla.suse.com/show_bug.cgi?id=1207852#c9 Paolo Stivanin <pstivanin(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #9 from Paolo Stivanin <pstivanin(a)suse.com> --- fixed with https://build.opensuse.org/request/show/1095893 -- 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 29 Jun '23

29 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212627 https://bugzilla.suse.com/show_bug.cgi?id=1212627#c8 --- Comment #8 from Adam Majer <amajer(a)suse.com> --- (In reply to Jonathan Kang from comment #7) > (In reply to Adam Majer from comment #6) > > Created attachment 867859 [details] > > fails after NetworkManager > > > > With additional changes, > > > > # /etc/systemd/system/sshd.service.d/01-after-network.conf > > [Unit] > > After=NetworkManager-wait-online.service > > > > [Service] > > Restart=always > > RestartSec=5s > > RestartPreventExitStatus= > > > > SSHD comes up *most of the time* while still failing sometimes. That is, > > Network Maanger signals via NetworkManager-wait-online.service that it is > > complete, but the IP address is still not available for bind by SSHD. I've > > attached a log that shows exactly this. > > > sshd[1225]: error: Bind to port 22 on 2a01:4f8:c012:9cdf:0:aead:1:aead failed: Cannot assign requested address > > sshd waits for an ipv6 address, is this intentional? In this logs you > provided, when sshd starts, there is already an ipv4 address available. But > there is no ipv6 address assigned yet. The IPv4 address is non-routable and configured via DHCP, and the only public address available is the IPv6. It's configured manually, so it's not like there is a long wait for RA or something, ipv6.method: manual ipv6.dns: 2a01:4ff:ff00::add:1,2a01:4ff:ff00::add:2 ipv6.dns-search: -- ipv6.dns-options: -- ipv6.dns-priority: 0 ipv6.addresses: 2a01:4f8:c012:9cdf::1/64, 2a01:4f8:c012:9cdf:0:aead:1:aead/64 ipv4.method: auto ipv4.dns: -- ipv4.dns-search: -- ipv4.dns-options: -- ipv4.dns-priority: 0 ipv4.addresses: -- In the "old days", all network interfaces should be configured as much as possible before the rest of the system is signaled that network is ready. So, passive configuration via RA for IPv6 would be out-of-scope for this wait but everything else should be blocking. Static IP assignments should definitely be all assigned prior to signaling network setup is successful. Basically, I would expect all configured network interfaces to be up and configured completely before proceeding. It's not OR condition here but AND. Optionally things could proceed after some timeout, like 2 or 3 minutes, if we are waiting for external resources that may be failing (eg. DHCP) Finally, an answer here that "it would work if you just listen on wildcard address" is not really a good answer here. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212019] Thunderbolt USB audio disconnecting with Kernel 6.3.4
by bugzilla_noreply＠suse.com 29 Jun '23

29 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212019 https://bugzilla.suse.com/show_bug.cgi?id=1212019#c10 --- Comment #10 from Michael Pujos <pujos.michael(a)gmail.com> --- I'm testing the possibility that the 135mv undervolt that I apply to my laptop CPU is causing this issue and will report. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212257] CIFS mount with DFS crashing the system
by bugzilla_noreply＠suse.com 29 Jun '23

29 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212257 https://bugzilla.suse.com/show_bug.cgi?id=1212257#c9 --- Comment #9 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Luiz Angelo Daros de Luca from comment #8) > I got a kdump but crash couldn't open it (it looks like this bug > https://www.spinics.net/linux/fedora/redhat-crash-utility/msg10076.html) It's bug 1190434. You can build the crash package with crash-debuginfo-compressed.patch removed and it'll work. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190434] crash is unable to find debuginfo of usrmerged kernel
by bugzilla_noreply＠suse.com 29 Jun '23

29 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1190434 https://bugzilla.suse.com/show_bug.cgi?id=1190434#c30 --- Comment #30 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to David Mair from comment #27) > The following error: > > > WARNING: invalid linux_banner pointer: 65762078756e694c > > crash: /var/tmp/vmlinux.xz_CSsIpp and /var/crash/2023-05-02-00:13/vmcore > > do not match! > > Occurs due to this: I already analyzed that in comment 25. The cause for that it that it tries to use the wrong BFD for reading the symbol, so instead of the address it gets the value: > With the patch applied it unconditionally runs check_gnu_debuglink even if the loaded BFD has symbols. This is invalid! > > The file pointed to by gnu_debuglink does not have text or data included, only debug info. It is not a full replacement for the previously loaded vmlinux. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212680] [leap] openQA test fails in updates_packagekit_gpk due to error messages "could not get updates" and syslog like 'gtk_widget_hide: assertion 'GTK_IS_WIDGET (widget)' failed'
by bugzilla_noreply＠suse.com 28 Jun '23

28 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212680 https://bugzilla.suse.com/show_bug.cgi?id=1212680#c2 Jia Zhaocong <zcjia(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zcjia(a)suse.com Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #2 from Jia Zhaocong <zcjia(a)suse.com> --- After some investigation, this test failure is not related with the GTK warning. The package upgrade is performed successfully, the error message is from a previous gpk-update-viewer window. The test is changed by https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/17331 -- 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 28 Jun '23

28 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212627 https://bugzilla.suse.com/show_bug.cgi?id=1212627#c7 Jonathan Kang <songchuan.kang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo? --- Comment #7 from Jonathan Kang <songchuan.kang(a)suse.com> --- (In reply to Adam Majer from comment #6) > Created attachment 867859 [details] > fails after NetworkManager > > With additional changes, > > # /etc/systemd/system/sshd.service.d/01-after-network.conf > [Unit] > After=NetworkManager-wait-online.service > > [Service] > Restart=always > RestartSec=5s > RestartPreventExitStatus= > > SSHD comes up *most of the time* while still failing sometimes. That is, > Network Maanger signals via NetworkManager-wait-online.service that it is > complete, but the IP address is still not available for bind by SSHD. I've > attached a log that shows exactly this. > sshd[1225]: error: Bind to port 22 on 2a01:4f8:c012:9cdf:0:aead:1:aead failed: Cannot assign requested address sshd waits for an ipv6 address, is this intentional? In this logs you provided, when sshd starts, there is already an ipv4 address available. But there is no ipv6 address assigned yet. -- You are receiving this mail because: You are on the CC list for the bug.

1 0