[kwin] [Bug 482142] drag in drop files in Google Chrome renders Chrome unusable
https://bugs.kde.org/show_bug.cgi?id=482142 Étienne changed: What|Removed |Added CC||tinou...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482871] New: Panel never hides with custom window manager on X11 (neither with autohide nor dodge window)
https://bugs.kde.org/show_bug.cgi?id=482871 Bug ID: 482871 Summary: Panel never hides with custom window manager on X11 (neither with autohide nor dodge window) Classification: Plasma Product: plasmashell Version: 6.0.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: tinou...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY Running a custom window manager on X11 (following Archlinux Wiki systemd procedure): a panel never hides itself, neither in autohide mode nor in dodge windows. STEPS TO REPRODUCE 1. mask/stop plasma-kwin_x11 service 2. create/enable/start a custom user service to launch a window manager 3. set dock to autohide OBSERVED RESULT The dock never hides itself. EXPECTED RESULT The dock should be able to hide itself (and to dodge windows when using another window manager) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux (available in About System) KDE Plasma Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION It works in the same setup when running kwin. It also works when running kwin with a custom composite manager (tested with compfy and picom) where the dock fades away appropriately. Not-working when using another simple window manager instead (tested with a custom EWMH compatible dwm and a default up-to-date icewm). Latte-dock, in plasma 5, did not have this issue (dodge windows was working fine). Cannot say for pure plasma 5 dock in this setup (never tested). -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 476154] KDE Connect crashed after disconnecting bluetooth device
https://bugs.kde.org/show_bug.cgi?id=476154 --- Comment #2 from Étienne --- Created attachment 162795 --> https://bugs.kde.org/attachment.cgi?id=162795=edit New crash information added by DrKonqi kdeconnectd (23.08.2) using Qt 5.15.11 Using pipewire and pipewire-pulse Bluetooth audio device connected (bose TWS in AAC) I had JamesDSP open, with eq I disconnected the bluetooth device And the "crash" notification appeared. -- Backtrace (Reduced): #7 0x7fa60ffd00b8 in context_get_card_info_callback (pd=pd@entry=0x55c72b06a6f0, command=command@entry=2, tag=tag@entry=1748, t=t@entry=0x55c72b015920, userdata=userdata@entry=0x55c72afbf2d0) at ../pulseaudio/src/pulse/introspect.c:990 #8 0x7fa60d5bae72 in run_action (pd=0x55c72b06a6f0, r=0x55c72b0b8140, command=2, ts=0x55c72b015920) at ../pulseaudio/src/pulsecore/pdispatch.c:291 #9 0x7fa60d5bc0ac in pa_pdispatch_run (pd=0x55c72b06a6f0, packet=packet@entry=0x55c72af65e40, ancil_data=ancil_data@entry=0x55c72b06ade8, userdata=userdata@entry=0x55c72aefd2b0) at ../pulseaudio/src/pulsecore/pdispatch.c:344 #10 0x7fa60ffbe244 in pstream_packet_callback (p=, packet=0x55c72af65e40, ancil_data=0x55c72b06ade8, userdata=0x55c72aefd2b0) at ../pulseaudio/src/pulse/context.c:364 #11 0x7fa60d5c0f95 in do_read (p=p@entry=0x55c72b06ab50, re=re@entry=0x55c72b06acd0) at ../pulseaudio/src/pulsecore/pstream.c:1023 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 476154] KDE Connect crashed after disconnecting bluetooth device
https://bugs.kde.org/show_bug.cgi?id=476154 Étienne changed: What|Removed |Added CC||tinou...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463666] New: Crash at startup
https://bugs.kde.org/show_bug.cgi?id=463666 Bug ID: 463666 Summary: Crash at startup Classification: Plasma Product: plasmashell Version: 5.26.4 Platform: Archlinux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tinou...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.26.4) Qt Version: 5.15.7 Frameworks Version: 5.101.0 Operating System: Linux 6.1.1-zen1-1-zen x86_64 Windowing System: X11 Distribution: "Arch Linux" DrKonqi: 5.26.4 [KCrashBackend] -- Information about the crash: Custom window manager used, launched with systemd (user). Kwin service is masked. latte-dock is used. Crashes at startup but I only see the notification. I click "restart app" and it eventually works. If there is a window opened too soon (before it starts correctly) it crashes non stop (at each "restart" from the notification). This might very well be related to my window manager (a heavily modified dwm). Any suggestion on what to look for in it would be appreciated :) The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7fd23c4d548a in QQuickItemGrabResult::render() () from /usr/lib/libQt5Quick.so.5 #5 0x7fd23a8bda51 in ?? () from /usr/lib/libQt5Core.so.5 #6 0x7fd23c447b71 in QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) () from /usr/lib/libQt5Quick.so.5 #7 0x7fd23c3f7f96 in ?? () from /usr/lib/libQt5Quick.so.5 #8 0x7fd23c3fcea4 in ?? () from /usr/lib/libQt5Quick.so.5 #9 0x7fd23a6e42ea in ?? () from /usr/lib/libQt5Core.so.5 #10 0x7fd23a09f8fd in ?? () from /usr/lib/libc.so.6 #11 0x7fd23a121a60 in ?? () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7fd227fff6c0 (LWP 7279) "QQmlThread"): #1 0x7fd238f16ee3 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #2 0x7fd238f6dae8 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7fd238f15132 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7fd23a8d7c6f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fd23a88573c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7fd23a6e721f in QThread::exec() () from /usr/lib/libQt5Core.so.5 #7 0x7fd23bec0370 in ?? () from /usr/lib/libQt5Qml.so.5 #8 0x7fd23a6e42ea in ?? () from /usr/lib/libQt5Core.so.5 #9 0x7fd23a09f8fd in ?? () from /usr/lib/libc.so.6 #10 0x7fd23a121a60 in ?? () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7fd2354ca6c0 (LWP 7250) "QDBusConnection"): #1 0x7fd238f6dbef in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fd238f15132 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7fd23a8d7c4c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7fd23a88573c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fd23a6e721f in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7fd23bba3cba in ?? () from /usr/lib/libQt5DBus.so.5 #7 0x7fd23a6e42ea in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7fd23a09f8fd in ?? () from /usr/lib/libc.so.6 #9 0x7fd23a121a60 in ?? () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7fd235a8fac0 (LWP 7249) "plasmashell"): #1 0x7fd23a09ecd0 in pthread_cond_wait () from /usr/lib/libc.so.6 #2 0x7fd23a6eb784 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #3 0x7fd23c4023d0 in ?? () from /usr/lib/libQt5Quick.so.5 #4 0x7fd23c452519 in QQuickWindow::event(QEvent*) () from /usr/lib/libQt5Quick.so.5 #5 0x7fd23b578b1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #6 0x7fd23a88cf98 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #7 0x7fd23ad335a8 in QPlatformWindow::windowEvent(QEvent*) () from /usr/lib/libQt5Gui.so.5 #8 0x7fd23b57d001 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #9 0x7fd23a88cf98 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #10 0x7fd23a8d7493 in QTimerInfoList::activateTimers() () from /usr/lib/libQt5Core.so.5 #11 0x7fd23a8d7ad2 in ?? () from /usr/lib/libQt5Core.so.5 #12 0x7fd238f1687b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #13 0x7fd238f6dc89 in ?? () from /usr/lib/libglib-2.0.so.0 #14 0x7fd238f15132 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #15 0x7fd23a8d7c4c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #16 0x7fd23a88573c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #17 0x7fd23a890269 in
[valgrind] [Bug 409429] False positives at unexpected location due to failure to recognize cmpeq as a dependency breaking idiom
https://bugs.kde.org/show_bug.cgi?id=409429
Étienne Dupuis changed:
What|Removed |Added
CC||svart.ridd...@gmail.com
--- Comment #4 from Étienne Dupuis ---
The following function allows detection of whether valgrind has the bug or not,
when compiled with clang + AVX2 enabled:
[[clang::optnone]]
static bool checkValgrindBug409429Fixed()
{
if (RUNNING_ON_VALGRIND) {
alignas(32) uint8_t m[32];
__m256i r = *reinterpret_cast(m);
*reinterpret_cast<__m256i *>(m) = _mm256_cmpeq_epi8(r, r);
if ((m[0] != 0xFF) || VALGRIND_COUNT_ERRORS)
return false;
}
return true;
}
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 338365] New client request to fetch valgrind version
https://bugs.kde.org/show_bug.cgi?id=338365
Étienne Dupuis changed:
What|Removed |Added
CC||svart.ridd...@gmail.com
--- Comment #6 from Étienne Dupuis ---
Recently, I stumbled upon https://bugs.kde.org/show_bug.cgi?id=409429. The
issue can be workarounded by manually installing a more recent version of
valgrind on all my runners, and telling my coworkers to do the same on their
development platforms.
I would have liked to include, at the beginning of my executable something like
if (RUNNING_ON_VALGRIND && (VALGRIND_RUNNING_VERSION < 0x316))
abort("Valgrind >= 3.16 required, otherwise expect false positive!");
The patch provided in this ticket would have made that possible.
Thanks for your time!
--
You are receiving this mail because:
You are watching all bug changes.
