[xdg-desktop-portal-kde] [Bug 488282] New: xdg-desktop-portal-kde crashed since ~30seconds after login
https://bugs.kde.org/show_bug.cgi?id=488282 Bug ID: 488282 Summary: xdg-desktop-portal-kde crashed since ~30seconds after login Classification: Plasma Product: xdg-desktop-portal-kde Version: git-stable-Plasma/6.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: m...@sr.team CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org Target Milestone: --- Created attachment 170311 --> https://bugs.kde.org/attachment.cgi?id=170311&action=edit coredump SUMMARY `xdg-desktop-portal-kde` crashed since ~30 seconds after login and kill kwin after crash. Affected only Wayland session. STEPS TO REPRODUCE 1. Install KDE 6.0.90 2. Enter to wayland session 3. Wait ~30 seconds OBSERVED RESULT xdg-desktop-portal-kde crashed and kill kwin on crash EXPECTED RESULT System work SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.9.1 (available in About System) KDE Plasma Version: 6.0.90 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION Reproduced with NVIDIA and AMD GPUs ``` PID: 165056 (xdg-desktop-por) UID: 1000 (sr_team) GID: 1000 (sr_team) Signal: 6 (ABRT) Timestamp: Mon 2024-06-10 03:59:20 EEST (8min ago) Command Line: /usr/lib/xdg-desktop-portal-kde Executable: /usr/lib/xdg-desktop-portal-kde Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-xdg-desktop-portal-kde.service Unit: user@1000.service User Unit: plasma-xdg-desktop-portal-kde.service Slice: user-1000.slice Owner UID: 1000 (sr_team) Boot ID: 484f6b337a8a4a7f8476bee80d631845 Machine ID: 3db28c0c46bea980806f9557c65e Hostname: srbox Storage: /var/lib/systemd/coredump/core.xdg-desktop-por.1000.484f6b337a8a4a7f8476bee80d631845.165056.171798116000.zst (present) Size on Disk: 2.8M Message: Process 165056 (xdg-desktop-por) of user 1000 dumped core. Stack trace of thread 165056: #0 0x7ed32eaa8e44 n/a (libc.so.6 + 0x94e44) #1 0x7ed32ea50a30 raise (libc.so.6 + 0x3ca30) #2 0x7ed32ea384c3 abort (libc.so.6 + 0x244c3) #3 0x7ed32f08c6b7 n/a (libQt6Core.so.6 + 0x8c6b7) #4 0x7ed32f08ce5b _ZNK14QMessageLogger5fatalEPKcz (libQt6Core.so.6 + 0x8ce5b) #5 0x7ed32f6daa45 n/a (libQt6Gui.so.6 + 0xdaa45) #6 0x7ed32f77af38 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt6Gui.so.6 + 0x17af38) #7 0x7ed32f148d75 _ZN23QCoreApplicationPrivate4initEv (libQt6Core.so.6 + 0x148d75) #8 0x7ed32f77afce _ZN22QGuiApplicationPrivate4initEv (libQt6Gui.so.6 + 0x17afce) #9 0x7ed3300f70f6 _ZN19QApplicationPrivate4initEv (libQt6Widgets.so.6 + 0xf70f6) #10 0x64af45e383b0 n/a (xdg-desktop-portal-kde + 0x273b0) #11 0x7ed32ea39c88 n/a (libc.so.6 + 0x25c88) #12 0x7ed32ea39d4c __libc_start_main (libc.so.6 + 0x25d4c) #13 0x64af45e388e5 n/a (xdg-desktop-portal-kde + 0x278e5) Stack trace of thread 165069: #0 0x7ed32eb1c39d __poll (libc.so.6 + 0x10839d) #1 0x7ed32cd208fd n/a (libglib-2.0.so.0 + 0xbe8fd) #2 0x7ed32ccbdf95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95) #3 0x7ed32f3a28dd _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3a28dd) #4 0x7ed32f14f10e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x14f10e) #5 0x7ed32f23a4e0 _ZN7QThread4execEv (libQt6Core.so.6 + 0x23a4e0) #6 0x7ed331175dfe n/a (libQt6DBus.so.6 + 0x2ddfe) #7 0x7ed32f2c96e7 n/a (libQt6Core.so.6 + 0x2c96e7) #8 0x7ed32eaa6ded n/a (libc.so.6 + 0x92ded) #9 0x7ed32eb2a0dc n/a (libc.so.6 + 0x1160dc) ELF object binary architecture: AMD x86-64 ``` -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 488282] xdg-desktop-portal-kde crashed since ~30seconds after login
https://bugs.kde.org/show_bug.cgi?id=488282 --- Comment #2 from SR_team --- (In reply to Nate Graham from comment #1) > Thank you for the bug report! Unfortunately I can't reproduce the crash > myself on current git master, and the backtrace is incomplete and missing > debug symbols for the following lines that we need to figure out exactly > what's going wrong. > > Could you please install debug symbols and attach a new symbolicated > backtrace generated by using `coredumpctl gdb` in a terminal window? See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl > for details about how to do this. > > Thanks again! I tried to create a reproducible example and realized that this ticket was wrong. xdg-desktop-portal-kde crashes because kwin stops, but kwin terminates with a SIGTERM signal - this is not a crash. Can you suggest how I can track down why kwin terminated? Kwin backtrace: ``` [Thread 0x7c96bea006c0 (LWP 27137) exited] Thread 1 "kwin_wayland" received signal SIGINT, Interrupt. 0x7c96dcb1c910 in ppoll () from /usr/lib/libc.so.6 Thread 16 (Thread 0x7c96a56006c0 (LWP 27132) "eDP-1"): #0 0x7c96dcaa34e9 in ?? () from /usr/lib/libc.so.6 #1 0x7c96dcaa5ed9 in pthread_cond_wait () from /usr/lib/libc.so.6 #2 0x7c96dccd5e61 in __gthread_cond_wait (__cond=, __mutex=) at /usr/src/debug/gcc/gcc-build/x86_64-pc-linux-gnu/libstdc++-v3/include/x86_64-pc-linux-gnu/bits/gthr-default.h:878 #3 std::__condvar::wait (this=, __m=...) at /usr/src/debug/gcc/gcc-build/x86_64-pc-linux-gnu/libstdc++-v3/include/bits/std_mutex.h:171 #4 std::condition_variable::wait (this=, __lock=...) at /usr/src/debug/gcc/gcc/libstdc++-v3/src/c++11/condition_variable.cc:41 #5 0x7c96dfbef34e in ?? () from /usr/lib/libkwin.so.6 #6 0x7c96dfbeac66 in ?? () from /usr/lib/libkwin.so.6 #7 0x7c96dcaac34b in ?? () from /usr/lib/libc.so.6 #8 0x7c96dcaac3c9 in pthread_once () from /usr/lib/libc.so.6 #9 0x7c96dfbeb040 in ?? () from /usr/lib/libkwin.so.6 #10 0x7c96dd23aff5 in ?? () from /usr/lib/libQt6Core.so.6 #11 0x7c96dd2c96e7 in ?? () from /usr/lib/libQt6Core.so.6 #12 0x7c96dcaa6ded in ?? () from /usr/lib/libc.so.6 #13 0x7c96dcb2a0dc in ?? () from /usr/lib/libc.so.6 Thread 15 (Thread 0x7c96a60006c0 (LWP 27131) "kwin_way:gdrv0"): #0 0x7c96dcaa34e9 in ?? () from /usr/lib/libc.so.6 #1 0x7c96dcaa5ed9 in pthread_cond_wait () from /usr/lib/libc.so.6 #2 0x7c96cdc9d4ae in ?? () from /usr/lib/dri/radeonsi_dri.so #3 0x7c96cdc7b25c in ?? () from /usr/lib/dri/radeonsi_dri.so #4 0x7c96cdc9d3dd in ?? () from /usr/lib/dri/radeonsi_dri.so #5 0x7c96dcaa6ded in ?? () from /usr/lib/libc.so.6 #6 0x7c96dcb2a0dc in ?? () from /usr/lib/libc.so.6 Thread 14 (Thread 0x7c96a6a006c0 (LWP 27130) "kwin_w:traceq0"): #0 0x7c96dcaa34e9 in ?? () from /usr/lib/libc.so.6 #1 0x7c96dcaa5ed9 in pthread_cond_wait () from /usr/lib/libc.so.6 #2 0x7c96cdc9d4ae in ?? () from /usr/lib/dri/radeonsi_dri.so #3 0x7c96cdc7b25c in ?? () from /usr/lib/dri/radeonsi_dri.so #4 0x7c96cdc9d3dd in ?? () from /usr/lib/dri/radeonsi_dri.so #5 0x7c96dcaa6ded in ?? () from /usr/lib/libc.so.6 #6 0x7c96dcb2a0dc in ?? () from /usr/lib/libc.so.6 Thread 13 (Thread 0x7c96a74006c0 (LWP 27129) "kwin_way:gdrv0"): #0 0x7c96dcaa34e9 in ?? () from /usr/lib/libc.so.6 #1 0x7c96dcaa5ed9 in pthread_cond_wait () from /usr/lib/libc.so.6 #2 0x7c96cdc9d4ae in ?? () from /usr/lib/dri/radeonsi_dri.so #3 0x7c96cdc7b25c in ?? () from /usr/lib/dri/radeonsi_dri.so #4 0x7c96cdc9d3dd in ?? () from /usr/lib/dri/radeonsi_dri.so #5 0x7c96dcaa6ded in ?? () from /usr/lib/libc.so.6 #6 0x7c96dcb2a0dc in ?? () from /usr/lib/libc.so.6 Thread 12 (Thread 0x7c96a7e006c0 (LWP 27128) "kwin_w:traceq0"): #0 0x7c96dcaa34e9 in ?? () from /usr/lib/libc.so.6 #1 0x7c96dcaa5ed9 in pthread_cond_wait () from /usr/lib/libc.so.6 #2 0x7c96cdc9d4ae in ?? () from /usr/lib/dri/radeonsi_dri.so #3 0x7c96cdc7b25c in ?? () from /usr/lib/dri/radeonsi_dri.so #4 0x7c96cdc9d3dd in ?? () from /usr/lib/dri/radeonsi_dri.so #5 0x7c96dcaa6ded in ?? () from /usr/lib/libc.so.6 #6 0x7c96dcb2a0dc in ?? () from /usr/lib/libc.so.6 Thread 11 (Thread 0x7c96b0a006c0 (LWP 27126) "pw-data-loop"): #0 0x7c96dcb2a4e2 in epoll_wait () from /usr/lib/libc.so.6 #1 0x7c96bfe90197 in ?? () from /usr/lib/spa-0.2/support/libspa-support.so #2 0x7c96bfe81a21 in ?? () from /usr/lib/spa-0.2/support/libspa-support.so #3 0x7c96bf576103 in ?? () from /usr/lib/libpipewire-0.3.so.0 #4 0x7c96dcaa6ded in ?? () from /usr/lib/libc.so.6 #5 0x7c96dcb2a0dc in ?? () from /usr/lib/libc.so.6 Thread 10 (Thread 0x7c96b18006c0 (LWP 27125) "QQmlThread"): #0 0x7c96dcb1c3
[xdg-desktop-portal-kde] [Bug 488282] xdg-desktop-portal-kde crashed since ~30seconds after login
https://bugs.kde.org/show_bug.cgi?id=488282 SR_team changed: What|Removed |Added Resolution|BACKTRACE |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #4 from SR_team --- The distributive-related issue was resolved after the release of version 6.1 in the stable repository -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 481977] Spectacle crashes in NVIDIA driver code on startup after upgrade to plasma 6
https://bugs.kde.org/show_bug.cgi?id=481977 SR_team changed: What|Removed |Added CC||m...@sr.team -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 481977] Spectacle crashes in NVIDIA driver code on startup after upgrade to plasma 6
https://bugs.kde.org/show_bug.cgi?id=481977
--- Comment #12 from SR_team ---
Same issue
System: ArchLinux, KDE 6
GPU: NVIDIA RTX4070, driver 550.54.14 (closed source)
backtrace:
```
119 char *XDisplayString(Display *dpy) { return (DisplayString(dpy)); }
(gdb) bt
#0 XDisplayString (dpy=0x0) at
/usr/src/debug/libx11/libX11-1.8.7/src/Macros.c:119
#1 0x7fffdc449a1d in __vaDriverInit_1_13 () at
/usr/lib/dri/nvidia_drv_video.so
#2 0x7625427c in va_openDriver (driver_name=,
dpy=0x559554a0) at ../libva/va/va.c:478
#3 va_new_opendriver (dpy=0x559554a0) at ../libva/va/va.c:714
#4 vaInitialize (minor_version=0x7fffca94, major_version=0x7fffca90,
dpy=0x559554a0) at ../libva/va/va.c:743
#5 vaInitialize (dpy=0x559554a0, major_version=0x7fffca90,
minor_version=0x7fffca94) at ../libva/va/va.c:727
#6 0x77cc9dfa in VaapiUtils::openDevice(int*, QByteArray const&)
[clone .constprop.0] (fd=, path=...) at
/usr/src/debug/kpipewire/kpipewire-6.0.1.1/src/vaapiutils.cpp:165
#7 0x77cc6945 in VaapiUtils::supportsH264 (path=...,
this=0x7fffcc80) at
/usr/src/debug/kpipewire/kpipewire-6.0.1.1/src/vaapiutils.cpp:86
#8 VaapiUtils::VaapiUtils (this=0x7fffcc80, this=) at
/usr/src/debug/kpipewire/kpipewire-6.0.1.1/src/vaapiutils.cpp:37
#9 0x77cc6ce2 in PipeWireBaseEncodedStream::suggestedEncoders
(this=this@entry=0x559550a0) at
/usr/src/debug/kpipewire/kpipewire-6.0.1.1/src/pipewirebaseencodedstream.cpp:180
#10 0x77cc730e in PipeWireBaseEncodedStream::PipeWireBaseEncodedStream
(this=0x559550a0, parent=, this=,
parent=)
at
/usr/src/debug/kpipewire/kpipewire-6.0.1.1/src/pipewirebaseencodedstream.cpp:50
#11 0x77cc74ce in PipeWireRecord::PipeWireRecord
(this=this@entry=0x559550a0, parent=parent@entry=0x0, this=,
parent=)
at /usr/src/debug/kpipewire/kpipewire-6.0.1.1/src/pipewirerecord.cpp:59
#12 0x556134f8 in VideoPlatformWayland::VideoPlatformWayland(QObject*)
[clone .constprop.0] (this=this@entry=0x7fffd4008500, parent=0x0)
at
/usr/src/debug/spectacle/spectacle-24.02.0/src/Platforms/VideoPlatformWayland.cpp:78
#13 0x55613a67 in std::make_unique () at
/usr/include/c++/13.2.1/bits/unique_ptr.h:1070
#14 loadVideoPlatform () at
/usr/src/debug/spectacle/spectacle-24.02.0/src/Platforms/PlatformLoader.cpp:93
#15 SpectacleCore::SpectacleCore(QObject*) [clone .constprop.0]
(this=0x7fffd090, parent=0x0) at
/usr/src/debug/spectacle/spectacle-24.02.0/src/SpectacleCore.cpp:120
#16 0x555811e6 in main (argc=, argv=) at
/usr/src/debug/spectacle/spectacle-24.02.0/src/Main.cpp:103
```
core dump: https://nc.sr.team/s/XnXSm7taKaeoSb6
! saved with warning: `warning: Memory read failed for corefile section, 4096
bytes at 0xff60.`
P.S. Screen sharing via pipewire (obs, browser) work fine.
--
You are receiving this mail because:
You are watching all bug changes.
[KPipeWire] [Bug 481977] Spectacle crashes in NVIDIA driver code on startup after upgrade to plasma 6
https://bugs.kde.org/show_bug.cgi?id=481977
--- Comment #14 from SR_team ---
(In reply to Noah Davis from comment #13)
> Moved to KPipeWire since that's what all the backtraces seem to indicate
> where the bug is.
KMail have same crash, but it not contain KPipeWire in backtrace:
```
Thread 22 "Chrome_InProcGp" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffa74006c0 (LWP 500908)]
XDisplayString (dpy=0x0) at /usr/src/debug/libx11/libX11-1.8.7/src/Macros.c:119
119 char *XDisplayString(Display *dpy) { return (DisplayString(dpy)); }
(gdb) bt
#0 XDisplayString (dpy=0x0) at
/usr/src/debug/libx11/libX11-1.8.7/src/Macros.c:119
#1 0x7fffcc702a1d in __vaDriverInit_1_13 () at
/usr/lib/dri/nvidia_drv_video.so
#2 0x7fffe1b3927c in va_openDriver (driver_name=,
dpy=0x7fff600712d0) at ../libva/va/va.c:478
#3 va_new_opendriver (dpy=0x7fff600712d0) at ../libva/va/va.c:714
#4 vaInitialize (minor_version=0x7fffa73febf0, major_version=0x7fffa73febe4,
dpy=0x7fff600712d0) at ../libva/va/va.c:743
#5 vaInitialize (dpy=0x7fff600712d0, major_version=0x7fffa73febe4,
minor_version=0x7fffa73febf0) at ../libva/va/va.c:727
#6 0x706e8f01 in InitializeVaDriver_Locked () at
../../../../../qtwebengine-everywhere-src-6.6.2/src/3rdparty/chromium/media/gpu/vaapi/vaapi_wrapper.cc:858
#7 InitializeOnce () at
../../../../../qtwebengine-everywhere-src-6.6.2/src/3rdparty/chromium/media/gpu/vaapi/vaapi_wrapper.cc:899
#8 Initialize () at
../../../../../qtwebengine-everywhere-src-6.6.2/src/3rdparty/chromium/media/gpu/vaapi/vaapi_wrapper.cc:782
#9 0x706f06f3 in VASupportedProfiles () at
../../../../../qtwebengine-everywhere-src-6.6.2/src/3rdparty/chromium/media/gpu/vaapi/vaapi_wrapper.cc:1200
#10 0x706f56bc in NoDestructor<> () at
../../../../../qtwebengine-everywhere-src-6.6.2/src/3rdparty/chromium/base/no_destructor.h:88
#11 Get () at
../../../../../qtwebengine-everywhere-src-6.6.2/src/3rdparty/chromium/media/gpu/vaapi/vaapi_wrapper.cc:1177
#12 Get () at
../../../../../qtwebengine-everywhere-src-6.6.2/src/3rdparty/chromium/media/gpu/vaapi/vaapi_wrapper.cc:1176
#13 media::VaapiWrapper::PreSandboxInitialization () at
../../../../../qtwebengine-everywhere-src-6.6.2/src/3rdparty/chromium/media/gpu/vaapi/vaapi_wrapper.cc:3141
#14 0x73d42ea8 in content::InProcessGpuThread::Init () at
./../../../../../qtwebengine-everywhere-src-6.6.2/src/3rdparty/chromium/content/gpu/in_process_gpu_thread.cc:76
#15 0x71ef7885 in base::Thread::ThreadMain () at
./../../../../../qtwebengine-everywhere-src-6.6.2/src/3rdparty/chromium/base/threading/thread.cc:403
#16 0x71f08b2a in ThreadFunc () at
./../../../../../qtwebengine-everywhere-src-6.6.2/src/3rdparty/chromium/base/threading/platform_thread_posix.cc:101
#17 0x7fffed8a955a in start_thread (arg=) at
pthread_create.c:447
#18 0x7fffed926a3c in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
```
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 477762] New: Application launcher stop works since some time
https://bugs.kde.org/show_bug.cgi?id=477762 Bug ID: 477762 Summary: Application launcher stop works since some time Classification: Plasma Product: plasmashell Version: 5.90.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: m...@sr.team CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 Created attachment 163643 --> https://bugs.kde.org/attachment.cgi?id=163643&action=edit demo SUMMARY After few clicks, application launcher may stop work. After re-adding widget or switch to alternative, it may work some time, but breaks later STEPS TO REPRODUCE 1. Flood click on widget or flood by pressing Super-key OBSERVED RESULT Application launcher may stop works EXPECTED RESULT Application launcher always opens SOFTWARE/OS VERSIONS Linux kernel: 6.6.3 KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.1 GPU: Nvidia ADDITIONAL INFORMATION Multi-monitor setup. Each monitor have widget. When one widget broken, other widgets may work Tested on panels: - floating panel with fill space - floating panel with fit space - always visible panel with fit space - auto-hide panel with fit space -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477729] Certain entries missing from Desktop context menu but present in Dolphin context menu
https://bugs.kde.org/show_bug.cgi?id=477729 SR_team changed: What|Removed |Added CC||m...@sr.team -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477762] Application launcher stop works since some time
https://bugs.kde.org/show_bug.cgi?id=477762
--- Comment #2 from SR_team ---
> Maybe there are some packaging issues? I think the kde-unstable repo for
> arch linux hasn't finished all the updates to beta1 when you posted this.
It's load sources like that:
```
pkgver=5.90.0
_dirver=$(echo $pkgver | cut -d. -f1-3)
source=(https://download.kde.org/unstable/plasma/$_dirver/$pkgname-$pkgver.tar.xz{,.sig})
```
So it must be clear sources from KDE site.
Also, I check SHA256 from package sources with archives from KDE site, and it's
match
> Could you try this again after updating your system?
Ok, I try it later
> Also, could you provide complete system logs when this happens? Thanks!
Sorry, but no - I rolled back to Plasma 5, and do not have logs from Plasma 6
now
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 477762] Application launcher stop works since some time
https://bugs.kde.org/show_bug.cgi?id=477762 --- Comment #4 from SR_team --- > Ah I meant that some dependencies might have not gotten updates when you > posted.. No, package updated yesterday, I installed and test it today. Sources for 5.90.0 at download.kde.org do not changed in this time -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477762] Application launcher stop works since some time
https://bugs.kde.org/show_bug.cgi?id=477762 --- Comment #6 from SR_team --- (In reply to fanzhuyifan from comment #5) > (In reply to SR_team from comment #4) > > > Ah I meant that some dependencies might have not gotten updates when you > > > posted.. > > > > No, package updated yesterday, I installed and test it today. Sources for > > 5.90.0 at download.kde.org do not changed in this time > > Sorry for not making myself clear. I meant that the *packages on > kde-unstable* might not have been up to date. > True, beta1 was released on 11/29, but the Arch packages for those don't > update instantly. The maintainers were > packaging and pushing those to kde-unstable one by one, or batch by batch. > During the process, you might have > updated in your system at a time where some packages were beta1, but some > packages were still at alpha, which > might cause a lot of problems. > > Of course, this is assuming you installed beta1 from the kde-unstable repo. > Is this how you installed plasma beta1? There are now some updates that were sent this evening (UTC). But these are just applications. Plasma itself was updated before my installation - in the evening of 11/29 and in the morning of 11/30 (UTC) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477762] Application launcher stop opening when clicked while using an NVIDIA GPU
https://bugs.kde.org/show_bug.cgi?id=477762 --- Comment #9 from SR_team --- I runed just plasmashell from Plasma 6 in Plasma 5 session via distrobox (`distrobox-enter -n neon -- kstart plasmashell`), and this bug not reproduced -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477762] Application launcher stop opening when clicked while using an NVIDIA GPU
https://bugs.kde.org/show_bug.cgi?id=477762 --- Comment #10 from SR_team --- Created attachment 163790 --> https://bugs.kde.org/attachment.cgi?id=163790&action=edit System logs Add system logs. `.local/share/sddm/wayland-session.log` is empty. So add only systemd logs -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477762] Application launcher stop opening when clicked while using an NVIDIA GPU
https://bugs.kde.org/show_bug.cgi?id=477762 --- Comment #12 from SR_team --- (In reply to Nate Graham from comment #11) > Cannot reproduce on Plasma 6 either. But it's not a Plasma or a KWin issue; > the issue is with your icon theme as some files seem to be missing. Thanks, you right. I checked plasma styles and some files from `libplasma` package are missing - reinstall package resolved this. P.S. Package do not changed in repos, maybe it's problem with FS of my drive -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477762] Application launcher stop opening when clicked while using an NVIDIA GPU
https://bugs.kde.org/show_bug.cgi?id=477762 --- Comment #13 from SR_team --- (In reply to SR_team from comment #12) > (In reply to Nate Graham from comment #11) > > Cannot reproduce on Plasma 6 either. But it's not a Plasma or a KWin issue; > > the issue is with your icon theme as some files seem to be missing. > > > Thanks, you right. I checked plasma styles and some files from `libplasma` > package are missing - reinstall package resolved this. > > P.S. Package do not changed in repos, maybe it's problem with FS of my drive I reinstalled all system packages and bug reproduced for me. I use PC and Nvidia is main GPU without iGPU -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 461538] Right Click not working for some tasks, but working in default task manager for all
https://bugs.kde.org/show_bug.cgi?id=461538 SR_team changed: What|Removed |Added CC||m...@sr.team -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 461538] Right Click not working for some tasks, but working in default task manager for all
https://bugs.kde.org/show_bug.cgi?id=461538 --- Comment #3 from SR_team --- Fixed for my in master tree (test with `657e24395190cd2654d2a15576421c16575f1816` commit) -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 481977] Spectacle crashes in NVIDIA driver code on startup after upgrade to plasma 6
https://bugs.kde.org/show_bug.cgi?id=481977 --- Comment #17 from SR_team --- (In reply to Nicolas Fella from comment #16) > This is caused by the libva-vdpau-driver package on Arch. Removing that > should fix it I replaced with `libva-nvidia-driver` - now spectacle and kmail works for me. Thanks -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 481977] Spectacle crashes in NVIDIA driver code on startup after upgrade to plasma 6
https://bugs.kde.org/show_bug.cgi?id=481977 SR_team changed: What|Removed |Added CC|m...@sr.team | -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 482169] System Monitor in Plasma 6 crashes on clicking "Show Details Sidebar"
https://bugs.kde.org/show_bug.cgi?id=482169 SR_team changed: What|Removed |Added CC||m...@sr.team -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 482169] System Monitor in Plasma 6 crashes on clicking "Show Details Sidebar"
https://bugs.kde.org/show_bug.cgi?id=482169 --- Comment #11 from SR_team --- Same issue. OS: ArchLinux, core 6.7.9-zen GPU: NVIDIA, 550.54.14 Plasma version: 6.0.2 Frameworks: 6.0.0 Qt: 6.6.2 Coredump: https://nc.sr.team/s/KCqcozY9pGbFDEC Backtrace: ``` QQuickItem::parentItem (this=0x0) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/items/qquickitem.cpp:2629 Downloading source file /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/items/qquickitem.cpp 2629return d->parentItem; (gdb) (gdb) bt #0 QQuickItem::parentItem (this=0x0) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/items/qquickitem.cpp:2629 #1 0x7fffeaf81e13 in QQuickSelectionRectanglePrivate::updateSelectionMode (this=0x597aa0a0) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quicktemplates/qquickselectionrectangle.cpp:496 #2 0x7fffeaf8373b in operator() (__closure=0x597ab4f0) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quicktemplates/qquickselectionrectangle.cpp:542 #3 QtPrivate::FunctorCall, QtPrivate::List<>, void, QQuickSelectionRectangle::QQuickSelectionRectangle(QQuickItem*):: >::call (arg=, f=...) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:137 #4 QtPrivate::Functor, 0>::call, void> (arg=, f=...) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:339 #5 QtPrivate::QCallableObject, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x597ab4e0, r=, a=, ret=) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:522 #6 0x76190ca9 in QtPrivate::QSlotObjectBase::call (a=0x7fff7358, r=0x597a9fc0, this=0x597ab4e0, this=, r=, a=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobjectdefs_impl.h:433 #7 doActivate (sender=0x597a9fc0, signal_index=17, argv=0x7fff7358) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobject.cpp:4039 #8 0x7fffeb788d4b in QQuickItemPrivate::setEffectiveEnableRecur (this=0x59653340, scope=0x0, newEffectiveEnable=) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/items/qquickitem.cpp:6571 #9 0x7fffeb788d4b in QQuickItemPrivate::setEffectiveEnableRecur (this=0x59652e30, scope=0x0, newEffectiveEnable=) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/items/qquickitem.cpp:6571 #10 0x7fffeb788d4b in QQuickItemPrivate::setEffectiveEnableRecur (this=0x584f6dd0, scope=0x0, newEffectiveEnable=) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/items/qquickitem.cpp:6571 #11 0x7fffeb788d4b in QQuickItemPrivate::setEffectiveEnableRecur (this=0x588f6ab0, scope=0x0, newEffectiveEnable=) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/items/qquickitem.cpp:6571 #12 0x7fffeb788d4b in QQuickItemPrivate::setEffectiveEnableRecur (this=0x58008000, scope=0x0, newEffectiveEnable=) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/items/qquickitem.cpp:6571 #13 0x7fffeb77f6f4 in QQuickItem::setParentItem (this=0x7fffbc0021e0, parentItem=) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/items/qquickitem.cpp:2721 #14 0x7fffeb7ae1f9 in QQuickLoaderPrivate::setInitialState (obj=0x7fffbc0021e0, this=0x57eddda0) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/items/qquickloader.cpp:639 #15 QQuickLoaderIncubator::setInitialState (this=this@entry=0x584483d0, o=0x7fffbc0021e0) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/items/qquickloader.cpp:622 #16 0x772aedfa in QQmlIncubatorPrivate::incubate (this=this@entry=0x7fffbc002400, i=...) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/qml/qml/qqmlincubator.cpp:321 #17 0x772af4a6 in QQmlEnginePrivate::incubate (this=0x557c48f0, i=, forContext=) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/qml/qml/qqmlincubator.cpp:53 #18 0x7725fb86 in QQmlComponent::create (this=, incubator=..., context=, forContext=) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/qml/qml/qqmlcomponent.cpp:1437 #19 0x7fffeb7a8b46 in QQuickLoaderPrivate::_q_sourceLoaded (this=0x57eddda0) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/items/qquickloader.cpp:741 #20 0x7fffeb7add6d in QQuickLoader::setActive (this=0x57ef41b0, newVal=) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/items/qquickloader.cpp:315 #21 0x77231298 in QQmlPropertyData::writeProperty (this=, target=, value=, flags=...) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/qml/qml/qqmlpropertydata_p.h:298 #22 0x77246591 in
[kwin] [Bug 455526] Blur glitches started to appear in wayland again
https://bugs.kde.org/show_bug.cgi?id=455526 SR_team changed: What|Removed |Added CC||m...@sr.team --- Comment #44 from SR_team --- (In reply to Vlad Zahorodnii from comment #42) > Git commit 36960d8572221c696289232d0ab55c02ecfa5324 by Vlad Zahorodnii. > Committed on 18/08/2023 at 15:08. > Pushed by vladz into branch 'master'. > > plugins/blur: Rewrite it > > Given how the blur effect works, if a pixel changes, the surrounding > pixels may have to be repainted as well. Currently, it's achieved by > expanding the damage in the BlurEffect::prePaintWindow() function. > However, it means that the blur effect should see both surface and > buffer damage in the pre paint pass. > > Unfortunately, after refactoring surface and buffer damage tracking, > kwin no longer provides the buffer damage in the pre paint pass (it does > so for good reasons). This broke the blur effect. As an example, you may > see visual glitches when moving the software cursor over blurred areas > of a window. > > In order to fix this issue, the blur effect has to cache background > behind every window to avoid blurring already blurred areas. > > This change implements a background cache. Unfortunately, since the > blur effect's code has become very difficult to change over the years, > this change rewrites the relevant parts of the blur effect. > > With the proposed design, the blur effect is going to maintain cached > background for every window + offscreen render targets. It may have > issues with animated windows, however in practice, it seems to behave > good enough. However, if it becomes pressing matter, we can move from > simplistic design in this patch to somewhat more sophisticated design > that involves textures with rounded up size. > > M +0-6src/libkwineffects/kwinglutils.cpp > M +0-7src/libkwineffects/kwinglutils.h > M +0-1src/plugins/blur/CMakeLists.txt > M +370 -452 src/plugins/blur/blur.cpp > M +46 -38 src/plugins/blur/blur.h > M +0-2src/plugins/blur/blur.qrc > D +0-310 src/plugins/blur/blurshader.cpp > D +0-100 src/plugins/blur/blurshader.h > D +0-9src/plugins/blur/shaders/copy.frag > D +0-13 src/plugins/blur/shaders/copy_core.frag > M +2-3src/plugins/blur/shaders/downsample.frag > M +2-3src/plugins/blur/shaders/downsample_core.frag > M +2-4src/plugins/blur/shaders/noise.frag > M +2-4src/plugins/blur/shaders/noise_core.frag > M +2-3src/plugins/blur/shaders/upsample.frag > M +2-3src/plugins/blur/shaders/upsample_core.frag > M +7-2src/plugins/blur/shaders/vertex.vert > M +7-2src/plugins/blur/shaders/vertex_core.vert > > https://invent.kde.org/plasma/kwin/-/commit/ > 36960d8572221c696289232d0ab55c02ecfa5324 This fix for plasma 6. Branch 5.27 was affected to bug (tested on 5.27.8) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 430894] Confirmation prompt displayed every time a file is opened on a NextCloud webdav share
https://bugs.kde.org/show_bug.cgi?id=430894 SR_team changed: What|Removed |Added CC||m...@sr.team -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 375951] locally integrated menus
https://bugs.kde.org/show_bug.cgi?id=375951 SR_team changed: What|Removed |Added CC||m...@sr.team -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
https://bugs.kde.org/show_bug.cgi?id=424485 SR_team changed: What|Removed |Added CC||m...@sr.team -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 482169] System Monitor in Plasma 6 crashes on clicking "Show Details Sidebar"
https://bugs.kde.org/show_bug.cgi?id=482169 SR_team changed: What|Removed |Added CC|m...@sr.team | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448918] Wrong vsync by kwin_wayland on nvidia multi monitor
https://bugs.kde.org/show_bug.cgi?id=448918 SR_team changed: What|Removed |Added CC||m...@sr.team -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436627] Mouse gestures don't work in Wayland
https://bugs.kde.org/show_bug.cgi?id=436627 SR_team changed: What|Removed |Added CC||m...@sr.team -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 409392] NetworkManager widget freezes on VPN connection issues, freezing/blocking Plasma
https://bugs.kde.org/show_bug.cgi?id=409392 SR_team changed: What|Removed |Added CC||m...@sr.team -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 437814] Poor connectivity freezes plasmashell
https://bugs.kde.org/show_bug.cgi?id=437814 SR_team changed: What|Removed |Added CC||m...@sr.team -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440386] High CPU use of kwin_wayland when video playing in firefox
https://bugs.kde.org/show_bug.cgi?id=440386 SR_team changed: What|Removed |Added CC||m...@sr.team -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440386] High CPU use of kwin_wayland when video playing in firefox
https://bugs.kde.org/show_bug.cgi?id=440386 SR_team changed: What|Removed |Added Version|5.22.4 |5.23.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409040] Framerate decreases rapidly in Wayland on nVidia with proprietary drivers
https://bugs.kde.org/show_bug.cgi?id=409040 SR_team changed: What|Removed |Added CC||m...@sr.team -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409040] Framerate decreases rapidly in Wayland on nVidia with proprietary drivers
https://bugs.kde.org/show_bug.cgi?id=409040 --- Comment #8 from SR_team --- > maybe this is related to the sync between them? Maybe. When I run something on an external GPU, but with window on built-in screen, I also have CPU overhead in kwin_wayland. P.S. It not nvidia-specific bug. I have this bug on laptop with a GTX1650 and a Ryzen 5 3750H, and on laptop with a RX6600 and a Ryzen 7 5800H -- You are receiving this mail because: You are watching all bug changes.
