December 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1204063] Kernel 5.19.8 appears to be missing lpuart earlycon and console
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1204063 Miroslav Bene�� <mbenes(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mbenes(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205818] New: Issues with barrierc KVM client since latest libX11 update
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205818 Bug ID: 1205818 Summary: Issues with barrierc KVM client since latest libX11 update Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: martin.wilck(a)suse.com QA Contact: gfx-bugs(a)suse.de Found By: --- Blocker: --- The latest update of libX11 (1.8.2-1.1 �� 1.8.2-2.1) makes barrierc (a replacement of the KVM software synergy) very fragile. I observe 2 kinds off issues: The following event happend 3 times in less than an hour. It causes barrier to abort: > Nov 28 15:31:34 apollon.suse.de barrierc[4774]: Barrier 2.4.0-release: [2022-11-28T15:31:34] FATAL: X display has unexpectedly disconnected > Nov 28 15:52:14 apollon.suse.de barrierc[9342]: Barrier 2.4.0-release: [2022-11-28T15:52:14] FATAL: X display has unexpectedly disconnected > Nov 28 15:54:57 apollon.suse.de barrierc[12917]: Barrier 2.4.0-release: [2022-11-28T15:54:57] FATAL: X display has unexpectedly disconnected Moreover, I observed two coredumps of barrierc. All in all, the barrier client (which used to be very stable for me for years) has crashed 5 times in one hour. It's probably caused by this update: * Sat Nov 26 2022 Stefan Dirsch <sndirsch(a)suse.com> - U_Fix-797755-Allow-X-IfEvent-to-reenter-libX11.patch * fixed Firefox freezes (regression since 1.8.2) (boo#1205778) Excerpt from gdb session: > [New LWP 6298] > [New LWP 6299] > [New LWP 6300] > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib64/libthread_db.so.1". > Core was generated by `barrierc -d INFO artemis.local:24800'. > Program terminated with signal SIGABRT, Aborted. > #0 0x00007f80dea957ec in __pthread_kill_implementation () from /lib64/libc.so.6 > [Current thread is 1 (Thread 0x7f80dee40740 (LWP 6298))] > Missing separate debuginfos, use: zypper install glibc-debuginfo-2.36-7.1.x86_64 libXau6-debuginfo-1.0.10-1.1.x86_64 libXcursor1-debuginfo-1.2.1-1.4.x86_64 libXext6-debuginfo-1.3.5-1.1.x86_64 libXfixes3-debuginfo-6.0.0-2.5.x86_64 libXi6-debuginfo-1.8-1.5.x86_64 libXinerama1-debuginfo-1.1.5-1.1.x86_64 libXrandr2-debuginfo-1.5.3-1.1.x86_64 libXrender1-debuginfo-0.9.11-1.1.x86_64 libXtst6-debuginfo-1.2.4-1.1.x86_64 libgcc_s1-debuginfo-12.2.1+git537-1.1.x86_64 libopenssl1_1-debuginfo-1.1.1s-1.1.x86_64 libstdc++6-debuginfo-12.2.1+git537-1.1.x86_64 libxcb1-debuginfo-1.15-1.4.x86_64 libz1-debuginfo-1.2.12-2.1.x86_64 > Thread 3 (Thread 0x7f80de0ea6c0 (LWP 6300)): > #0 0x00007f80deb0bb7f in poll () from /lib64/libc.so.6 > #1 0x0000563abf9e05c7 in poll (__timeout=<optimized out>, __nfds=<optimized out>, __fds=0x563ac098cd20) at /usr/include/bits/poll2.h:39 > #2 ArchNetworkBSD::pollSocket (this=<optimized out>, pe=0x7f80d8000b90, num=1, timeout=<optimized out>) at /usr/src/debug/barrier-2.4.0-1.7.x86_64/src/lib/arch/unix/ArchNetworkBSD.cpp:330 > #3 0x0000563abfa12cbd in SocketMultiplexer::service_thread (this=0x563ac09094f0) at /usr/src/debug/barrier-2.4.0-1.7.x86_64/src/lib/net/SocketMultiplexer.cpp:189 > #4 operator() (__closure=<optimized out>) at /usr/src/debug/barrier-2.4.0-1.7.x86_64/src/lib/net/SocketMultiplexer.cpp:60 > #5 std::__invoke_impl<void, SocketMultiplexer::SocketMultiplexer()::<lambda()>&> (__f=...) at /usr/include/c++/12/bits/invoke.h:61 > #6 std::__invoke_r<void, SocketMultiplexer::SocketMultiplexer()::<lambda()>&> (__fn=...) at /usr/include/c++/12/bits/invoke.h:154 > #7 std::_Function_handler<void(), SocketMultiplexer::SocketMultiplexer()::<lambda()> >::_M_invoke(const std::_Any_data &) (__functor=...) at /usr/include/c++/12/bits/std_function.h:290 > #8 0x0000563abfa1ac2f in std::function<void ()>::operator()() const (this=0x563ac0909800) at /usr/include/c++/12/bits/std_function.h:591 > #9 Thread::threadFunc(std::function<void ()> const&) (func=...) at /usr/src/debug/barrier-2.4.0-1.7.x86_64/src/lib/mt/Thread.cpp:140 > #10 operator() (__closure=0x563ac0909800) at /usr/src/debug/barrier-2.4.0-1.7.x86_64/src/lib/mt/Thread.cpp:33 > #11 std::__invoke_impl<void, Thread::Thread(const std::function<void()>&)::<lambda()>&> (__f=...) at /usr/include/c++/12/bits/invoke.h:61 > #12 std::__invoke_r<void, Thread::Thread(const std::function<void()>&)::<lambda()>&> (__fn=...) at /usr/include/c++/12/bits/invoke.h:154 > #13 std::_Function_handler<void(), Thread::Thread(const std::function<void()>&)::<lambda()> >::_M_invoke(const std::_Any_data &) (__functor=...) at /usr/include/c++/12/bits/std_function.h:290 > #14 0x0000563abf9dcff0 in std::function<void ()>::operator()() const (this=0x563ac0909100) at /usr/include/c++/12/bits/std_function.h:591 > #15 ArchMultithreadPosix::doThreadFunc (thread=0x563ac09090f0, this=0x7fffc6a7b418) at /usr/src/debug/barrier-2.4.0-1.7.x86_64/src/lib/arch/unix/ArchMultithreadPosix.cpp:687 > #16 ArchMultithreadPosix::threadFunc (vrep=0x563ac09090f0) at /usr/src/debug/barrier-2.4.0-1.7.x86_64/src/lib/arch/unix/ArchMultithreadPosix.cpp:669 > #17 0x00007f80dea9398d in start_thread () from /lib64/libc.so.6 > #18 0x00007f80deb1a380 in clone3 () from /lib64/libc.so.6 > > Thread 2 (Thread 0x7f80de8eb6c0 (LWP 6299)): > #0 0x00007f80dea4375a in sigtimedwait () from /lib64/libc.so.6 > #1 0x00007f80dea42cbc in sigwait () from /lib64/libc.so.6 > #2 0x0000563abf9dcd53 in ArchMultithreadPosix::threadSignalHandler () at /usr/src/debug/barrier-2.4.0-1.7.x86_64/src/lib/arch/unix/ArchMultithreadPosix.cpp:744 > #3 0x00007f80dea9398d in start_thread () from /lib64/libc.so.6 > #4 0x00007f80deb1a380 in clone3 () from /lib64/libc.so.6 > > Thread 1 (Thread 0x7f80dee40740 (LWP 6298)): > #0 0x00007f80dea957ec in __pthread_kill_implementation () from /lib64/libc.so.6 > #1 0x00007f80dea42816 in raise () from /lib64/libc.so.6 > --Type <RET> for more, q to quit, c to continue without paging-- > #2 0x00007f80dea2b81c in abort () from /lib64/libc.so.6 > #3 0x00007f80dea2b72b in __assert_fail_base.cold () from /lib64/libc.so.6 > #4 0x00007f80dea3ac46 in __assert_fail () from /lib64/libc.so.6 > #5 0x00007f80deeff784 in poll_for_event (dpy=dpy@entry=0x563ac0909ca0, queued_only=0) at /usr/src/debug/libX11-1.8.2/src/xcb_io.c:278 > #6 0x00007f80deeff846 in poll_for_response (dpy=dpy@entry=0x563ac0909ca0) at /usr/src/debug/libX11-1.8.2/src/xcb_io.c:310 > #7 0x00007f80def049f2 in _XReadEvents (dpy=0x563ac0909ca0) at /usr/src/debug/libX11-1.8.2/src/xcb_io.c:527 > #8 _XReadEvents (dpy=0x563ac0909ca0) at /usr/src/debug/libX11-1.8.2/src/xcb_io.c:454 > #9 0x00007f80deeeb0ed in XIfEvent (dpy=0x563ac0909ca0, event=0x7fffc6a7add0, predicate=0x563abf9f54f0 <XWindowsUtil::propertyNotifyPredicate(_XDisplay*, _XEvent*, char*)>, arg=0x7fffc6a7ad30 "\004") at /usr/src/debug/libX11-1.8.2/src/IfEvent.c:70 > #10 0x0000563abf9fbe16 in XWindowsUtil::getCurrentTime (display=0x563ac0909ca0, window=16777220) at /usr/src/debug/barrier-2.4.0-1.7.x86_64/src/lib/platform/XWindowsUtil.cpp:1494 > #11 0x0000563abfa000c2 in XWindowsClipboard::wasOwnedAtTime (time=916230, this=0x563ac092f950) at /usr/src/debug/barrier-2.4.0-1.7.x86_64/src/lib/platform/XWindowsClipboard.cpp:1211 > #12 XWindowsClipboard::wasOwnedAtTime (time=916230, this=0x563ac092f950) at /usr/src/debug/barrier-2.4.0-1.7.x86_64/src/lib/platform/XWindowsClipboard.cpp:1193 > #13 XWindowsClipboard::addRequest (property=434, time=916230, target=494, requestor=8388611, owner=<optimized out>, this=0x563ac092f950) at /usr/src/debug/barrier-2.4.0-1.7.x86_64/src/lib/platform/XWindowsClipboard.cpp:135 > #14 XWindowsScreen::handleSystemEvent (this=<optimized out>, event=...) at /usr/src/debug/barrier-2.4.0-1.7.x86_64/src/lib/platform/XWindowsScreen.cpp:1304 > #15 0x0000563abf9da0ca in EventQueue::dispatchEvent (this=0x7fffc6a7b500, event=...) at /usr/src/debug/barrier-2.4.0-1.7.x86_64/src/lib/base/EventQueue.cpp:282 > #16 0x0000563abf9e178a in EventQueue::loop (this=0x7fffc6a7b500) at /usr/src/debug/barrier-2.4.0-1.7.x86_64/src/lib/base/EventQueue.cpp:128 > #17 0x0000563abf9ecaf6 in ClientApp::mainLoop (this=0x7fffc6a7b2c0) at /usr/src/debug/barrier-2.4.0-1.7.x86_64/src/lib/barrier/ClientApp.cpp:476 > #18 0x0000563abf9e4e7f in App::daemonMainLoop (this=0x7fffc6a7b2c0) at /usr/src/debug/barrier-2.4.0-1.7.x86_64/src/lib/barrier/App.cpp:136 > #19 daemonMainLoopStatic (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/barrier-2.4.0-1.7.x86_64/src/lib/barrier/ClientApp.cpp:498 > #20 0x0000563abf9dc8c6 in ArchDaemonUnix::daemonize (this=<optimized out>, name=<optimized out>, func=0x563abf9e4db0 <daemonMainLoopStatic(int, char const**)>) at /usr/src/debug/barrier-2.4.0-1.7.x86_64/src/lib/arch/unix/ArchDaemonUnix.cpp:131 > #21 0x0000563abf9e8c05 in ClientApp::runInner (this=0x7fffc6a7b2c0, argc=4, argv=0x7fffc6a7b8f8, outputter=0x0, startup=0x563abf9e2b50 <standardStartupStatic(int, char**)>) at /usr/src/debug/barrier-2.4.0-1.7.x86_64/src/lib/barrier/ClientApp.cpp:531 > #22 0x0000563abf9d9820 in App::run (argv=0x7fffc6a7b8f8, argc=4, this=0x7fffc6a7b2c0) at /usr/src/debug/barrier-2.4.0-1.7.x86_64/src/./lib/barrier/App.h:91 > #23 main (argc=4, argv=0x7fffc6a7b8f8) at /usr/src/debug/barrier-2.4.0-1.7.x86_64/src/cmd/barrierc/barrierc.cpp:49 > > > (gdb) l > 268 PendingRequest *req = dpy->xcb->pending_requests; > 269 xcb_generic_event_t *event = dpy->xcb->next_event; > 270 uint64_t event_sequence = X_DPY_GET_LAST_REQUEST_READ(dpy); > 271 widen(&event_sequence, event->full_sequence); > 272 if(!req || XLIB_SEQUENCE_COMPARE(event_sequence, <, req->sequence) > 273 || (event->response_type != X_Error && event_sequence == req->sequence)) > 274 { > 275 uint64_t request = X_DPY_GET_REQUEST(dpy); > 276 if (XLIB_SEQUENCE_COMPARE(event_sequence, >, request)) > 277 { > 278 throw_thread_fail_assert("Unknown sequence " > 279 "number while " > 280 "processing queue", > 281 xcb_xlib_threads_sequence_lost); > 282 } > > (gdb) p dpy->xcb->pending_requests > $6 = (PendingRequest *) 0x0 > (gdb) p *dpy->xcb->next_event > $4 = {response_type = 28 '\034', pad0 = 0 '\000', sequence = 14698, pad = {16777220, 496, 916232, 0, 0, 0, 0}, full_sequence = 145770} > (gdb) p dpy->last_request_read > $5 = 145768 > (gdb) p dpy->request > $7 = 145769 One can see that the assertion in line 278 fails because dpy->xcb->next_event->full_sequence = 145770 is larger than dpy->request = 145769. No idea how this came to pass. The 2nd core dump shows exactly the same stack. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1205778] Firefox sometimes hangs when copy / pasting with libx11 1.8.2
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205778 https://bugzilla.suse.com/show_bug.cgi?id=1205778#c13 --- Comment #13 from Stefan Dirsch <sndirsch(a)suse.com> --- https://build.opensuse.org/request/show/1040299 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205778] Firefox sometimes hangs when copy / pasting with libx11 1.8.2
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205778 https://bugzilla.suse.com/show_bug.cgi?id=1205778#c12 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(christophe(a)krop.f | |r) | --- Comment #12 from Stefan Dirsch <sndirsch(a)suse.com> --- I'll be on vacation from 2022-12-08 until 2023-01-02. Since I would like to avoid having a broken Tumbleweed for the next 4 weeks, I'm doing a radical change now. ------------------------------------------------------------------- Mon Dec 5 13:40:36 UTC 2022 - Stefan Dirsch <sndirsch(a)suse.com> - going back to version 1.7.5 for now to get rid of regressions, which were introduced by trying to get thread-safe in libX11 itself - re-introduced U_fix-a-memory-leak-in-XRegisterIMInstantiateCallback.patch which was not yet in 1.7.5 We can discuss things in January again. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205714] GNOME terminal freezes when maximized
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

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

1 0

[Bug 1199316] [doc] 4.37.1 General firewall configuration
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1199316 https://bugzilla.suse.com/show_bug.cgi?id=1199316#c2 Jana Halackova <jsindelarova(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED CC| |jsindelarova(a)suse.com Resolution|--- |FIXED --- Comment #2 from Jana Halackova <jsindelarova(a)suse.com> --- Fixed by https://github.com/SUSE/doc-sle/commit/999a98e93763d6bc1cc6b3a079a7b73d9d0f… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205149] %kernel_module_package_buildreqs needs to require suse-kernel-rpm-scriptlets
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205149 https://bugzilla.suse.com/show_bug.cgi?id=1205149#c11 --- Comment #11 from Ludwig Nussel <lnussel(a)suse.com> --- wip https://build.opensuse.org/project/show/home:lnussel:branches:network -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205818] Issues with barrierc KVM client since latest libX11 update
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205818 http://bugzilla.opensuse.org/show_bug.cgi?id=1205818#c30 --- Comment #30 from Martin Wilck <martin.wilck(a)suse.com> --- But there's no sign of X crashing or erroring out around the above message. If I can enable useful debugging, please teach me. > Dec 05 13:34:03 apollon.suse.de gnome-shell[3968]: Window manager warning: WM_TRANSIENT_FOR window 0x260620f for 0x2606272 window over> > Dec 05 13:34:08 apollon.suse.de barrierc[4485]: Barrier 2.4.0-release: [2022-12-05T13:34:08] FATAL: X display has unexpectedly disconn> > Dec 05 13:34:20 apollon.suse.de gnome-shell[3968]: Object St.Button (0x55cf4c2c03d0), has been already disposed �� impossible to get an> > Dec 05 13:34:20 apollon.suse.de gnome-shell[3968]: == Stack trace for context 0x55cf480ab190 == > Dec 05 13:34:20 apollon.suse.de gnome-shell[3968]: #0 55cf4923c478 i resource:///org/gnome/shell/ui/windowPreview.js:566 (e710f5c2> -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205818] Issues with barrierc KVM client since latest libX11 update
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205818 http://bugzilla.opensuse.org/show_bug.cgi?id=1205818#c29 --- Comment #29 from Martin Wilck <martin.wilck(a)suse.com> --- That message comes from barrier's X IO error handler XWindowsScreen::ioErrorHandler(Display*) https://github.com/debauchee/barrier/blob/653e4badeb88f61de901581667d4465d7… > // set the X I/O error handler so we catch the display disconnecting > m_impl->XSetIOErrorHandler(&XWindowsScreen::ioErrorHandler); https://github.com/debauchee/barrier/blob/653e4badeb88f61de901581667d4465d7… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205149] %kernel_module_package_buildreqs needs to require suse-kernel-rpm-scriptlets
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205149 https://bugzilla.suse.com/show_bug.cgi?id=1205149#c10 --- Comment #10 from Ludwig Nussel <lnussel(a)suse.com> --- No, the failing packages just lack "BuildRequires: %kernel_module_package_buildreqs" and need to be fixed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0