[krita] [Bug 396803] New: fail to add ffmpeg as path
https://bugs.kde.org/show_bug.cgi?id=396803 Bug ID: 396803 Summary: fail to add ffmpeg as path Product: krita Version: 4.1.1 Platform: Other OS: other Status: UNCONFIRMED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: pi6265...@gmail.com Target Milestone: --- Created attachment 114090 --> https://bugs.kde.org/attachment.cgi?id=114090=edit rendering animation to video so i have a: 64 bit operating system 8 GB intel Graph of i7 i am having problems adding ffmpeg to the log system but weirdly enough when i try to render it makes the video that has 1 sec animation(more specifically is pitch black). i though it was the version of my krita that was 3.1.1 and i updated it to 4.1.1 (which is prettier and simpler) but i still have the same issue also i tried every tutorial on how to install ffmpeg can someone help me please? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396803] fail to add ffmpeg as path
https://bugs.kde.org/show_bug.cgi?id=396803 --- Comment #1 from ash --- (In reply to ash from comment #0) > Created attachment 114090 [details] > rendering animation to video > > so i have a: > 64 bit operating system > 8 GB > intel Graph of i7 > > i am having problems adding ffmpeg to the log system but weirdly enough when > i try to render it makes the video that has 1 sec animation(more > specifically is pitch black). > > i though it was the version of my krita that was 3.1.1 and i updated it to > 4.1.1 (which is prettier and simpler) but i still have the same issue > > also i tried every tutorial on how to install ffmpeg > > can someone help me please? oh i manage to added! Microsoft Windows [Version 10.0.17134.165] (c) 2018 Microsoft Corporation. All rights reserved. C:\Users\User>ffmpeg -version ffmpeg version N-91510-gd134b8d85f Copyright (c) 2000-2018 the FFmpeg developers built with gcc 7.3.1 (GCC) 20180722 configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-bzlib --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom --enable-libmfx --enable-amf --enable-ffnvcodec --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth libavutil 56. 18.102 / 56. 18.102 libavcodec 58. 21.106 / 58. 21.106 libavformat58. 17.101 / 58. 17.101 libavdevice58. 4.101 / 58. 4.101 libavfilter 7. 26.100 / 7. 26.100 libswscale 5. 2.100 / 5. 2.100 libswresample 3. 2.100 / 3. 2.100 libpostproc55. 2.100 / 55. 2.100 but it doesnt render the video yet -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396803] fail to add ffmpeg as path
https://bugs.kde.org/show_bug.cgi?id=396803 ash changed: What|Removed |Added Attachment #114090|0 |1 is obsolete|| --- Comment #2 from ash --- Created attachment 114097 --> https://bugs.kde.org/attachment.cgi?id=114097=edit this after the update -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396803] fail to add ffmpeg as path
https://bugs.kde.org/show_bug.cgi?id=396803 --- Comment #6 from ash --- (In reply to Boudewijn Rempt from comment #4) > Setting to needsinfo, since we cannot figure this out without more > information. so looks like i downloaded the night build instead of the official version so i redo the installation with the new file C:\WINDOWS\system32>ffmpeg -version ffmpeg version 4.0.2 Copyright (c) 2000-2018 the FFmpeg developers built with gcc 7.3.1 (GCC) 20180722 configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-bzlib --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom --enable-libmfx --enable-amf --enable-ffnvcodec --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth libavutil 56. 14.100 / 56. 14.100 libavcodec 58. 18.100 / 58. 18.100 libavformat58. 12.100 / 58. 12.100 libavdevice58. 3.100 / 58. 3.100 libavfilter 7. 16.100 / 7. 16.100 libswscale 5. 1.100 / 5. 1.100 libswresample 3. 1.100 / 3. 1.100 libpostproc55. 1.100 / 55. 1.100 C:\WINDOWS\system32> is rendering but the mp4 videos appear black i think that since the animation is a loop of 2 seconds(walk cycle) it doesn't render well frames can i fix this? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396803] fail to add ffmpeg as path
https://bugs.kde.org/show_bug.cgi?id=396803 --- Comment #5 from ash --- (In reply to Boudewijn Rempt from comment #4) > Setting to needsinfo, since we cannot figure this out without more > information. sorry i havent reply so about the ffmpeg i am sure i download from the website https://www.ffmpeg.org/ i have upgrade my krita to 4.1.1 if is a nightly build should i unistall (remove) the ffmpeg and find the official one? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396803] fail to add ffmpeg as path
https://bugs.kde.org/show_bug.cgi?id=396803 ash changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #8 from ash --- (In reply to Scott Petrovic from comment #7) > Are you trying to watch this with windows media player? That has pretty bad > video support, so I wouldn't be surprised if that just shows a black screen. > I would either get a program like VLC, or you could also just drag the video > in a browser like Chrome. Does the video still show black then? it works!! thank you so much! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 406868] New: baloo_file_extractor fails MTimeDB::del with MDB_BAD_TXN, constant high CPU use
https://bugs.kde.org/show_bug.cgi?id=406868
Bug ID: 406868
Summary: baloo_file_extractor fails MTimeDB::del with
MDB_BAD_TXN, constant high CPU use
Product: frameworks-baloo
Version: 5.57.0
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Baloo File Daemon
Assignee: baloo-bugs-n...@kde.org
Reporter: a...@heyquark.com
Target Milestone: ---
Created attachment 119620
--> https://bugs.kde.org/attachment.cgi?id=119620=edit
screenshot from htop showing the large CPU and vmem use, as well as which
processes are responsible
SUMMARY
The baloo_file_extractor and tags.so [kdeinit5] processes on my machine seem to
be always running and using large (though not 100%) amounts of CPU, and a full
256G of vmem (htop screencap attached). The journald logs are filled with the
following:
Apr 25 12:38:54 sylveon kdeinit5[1097]: (QUrl("tags:/"), QUrl("tags:/"))
Apr 25 12:38:54 sylveon kdeinit5[1097]: (QUrl("tags:/"), QUrl("tags:/"))
Apr 25 12:38:54 sylveon kdeinit5[1097]: ()
which repeats many, many times. It always follows the same pattern: 2 QUrls and
then an empty. The following messages are mixed in, then repeated many times
after the kdeinit5 messages stop:
Apr 25 12:38:55 sylveon baloo_file_extractor[1458]: org.kde.baloo.engine:
MTimeDB::del 0 3391499450514944 MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
Apr 25 12:38:55 sylveon baloo_file_extractor[1458]: org.kde.baloo.engine:
Transaction::commit MDB_BAD_TXN: Transaction must abort, has a child, or is
invalid
The transaction ID (I assume that's what the number starting in 33 is?) seems
to remain constant. After a few hundred of each message, they'll stop for
roughly 30 seconds, and then another batch come through.
STEPS TO REPRODUCE
I honestly don't know. I ran a full system update after the recent batch of KDE
Applications updates and now this happens every time I boot my machine - it was
working fine before. I'm happy to dump config files and databases and whatever
else is needed.
OBSERVED RESULT
baloo_file_extractor constantly uses large amounts of vmem and cpu, filling the
system logs with error messages
EXPECTED RESULT
baloo_file_extractor doesn't do that.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Antegros, kernel 5.0.9-arch1-1-ARCH
KDE Plasma Version: 5.15.4
KDE Frameworks Version: 5.57.0
Qt Version: 5.12.3
ADDITIONAL INFORMATION
This is my first time filing a bug with a large project like KDE, hopefully
this is okay! As I said before, more than happy to provide other information; I
really had no idea where to start with this.
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-baloo] [Bug 406868] baloo_file_extractor fails MTimeDB::del with MDB_BAD_TXN, constant high CPU use
https://bugs.kde.org/show_bug.cgi?id=406868 --- Comment #3 from Ash --- (In reply to Dan from comment #1) > Hi Ash, I think I may have experienced the same problem as you, and I wonder > if you may need to increase your inotify watch limit. See here? > > https://askubuntu.com/questions/1137733/baloo-running-amok-kubuntu-19-04/ > 1137997#1137997 Hey Dan! Thanks for the suggestion, but sadly that didn't change anything for me. I grepped through my journalctl logs and didn't see any mention of inotify, so perhaps we're experiencing different bugs. Thanks to the comments on that question though, I was able to disable baloo, which has at least given me a temporary fix to rescue my battery life ;) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391606] Undoing file removal causes an "Internal error in copyOrMove, should never happen" error
https://bugs.kde.org/show_bug.cgi?id=391606 Ash changed: What|Removed |Added CC||a...@heyquark.com --- Comment #13 from Ash --- This is still happening, any movement on that patch? Might also suggest a new error message. OS: Arch Linux KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417082] New: Files on desktop can open multiple context menus at once on Wayland
https://bugs.kde.org/show_bug.cgi?id=417082 Bug ID: 417082 Summary: Files on desktop can open multiple context menus at once on Wayland Product: plasmashell Version: 5.17.5 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: a...@heyquark.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 125636 --> https://bugs.kde.org/attachment.cgi?id=125636=edit Screenshot showing multiple context menus open after right-clicking on desktop icon SUMMARY On Wayland, when right-clicking files on the desktop to open a context menu, multiple context menus appear, with only the topmost one responding to interaction. If a window has focus, the first menu appears in the top-left with window decorations (similar to https://bugs.kde.org/show_bug.cgi?id=387597 ). I suspect these are both the same underlying issue, so I'm reporting them together - happy to change that! STEPS TO REPRODUCE 1. Have some files in ~/Desktop, and have the desktop layout set to "Folder View" 2. With all applications minimised or unfocused, right-click on a desktop icon 3. Right-click on a still-exposed part of the icon (or another icon entirely) 4. Right-click on an empty portion of the desktop or focus a window to dismiss any context menus. 5. With a window focused, right-click on a desktop icon OBSERVED RESULT With no focused windows: Multiple context menus appear, overlapping. Only the topmost/most recent one can be interacted with. Actions that would usually close a context menu (left-clicking on the desktop or icons) are ineffective, and choosing an item in the menu only dismisses one at a time. With a focused window: The window loses focus, and a context menu appears in the top-left corner with window decorations, like in https://bugs.kde.org/show_bug.cgi?id=387597 . Further context menus can be opened by right-clicking icons, but these do not appear with window decorations. EXPECTED RESULT The second right-click anywhere on the desktop or icons closes the active context menu, instead of opening another one - this is the behaviour of empty desktop space. In the case where the menu opens with window decorations, it should instead appear at the position of the mouse, without decorations. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon User 5.17 KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.13.2 Also reproduced on Linux/KDE Plasma: Arch Linux (rolling, up to date 2020-02-03) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION Left-clicking on the desktop while one of these rouge context menus is open causes a "Delete" option to appear under "Move to Wastebin". Since a file isn't selected in this state, I'm not really game to see what it does. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417082] Files on desktop can open multiple context menus at once on Wayland
https://bugs.kde.org/show_bug.cgi?id=417082 --- Comment #1 from Ash --- Created attachment 125637 --> https://bugs.kde.org/attachment.cgi?id=125637=edit Screenshot showing context menu with window decorations after clicking with a focused window -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 415164] ctrl+alt+(left|right) conflict on yakuake
https://bugs.kde.org/show_bug.cgi?id=415164 Ash <25rbmfs...@liamekaens.com> changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||25rbmfs...@liamekaens.com Ever confirmed|0 |1 --- Comment #4 from Ash <25rbmfs...@liamekaens.com> --- I can confirm that downgrading from konsole 19.12.2 to 19.04.3 eliminates the conflict. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 398908] Dolphin uses up huge amounts of memory
https://bugs.kde.org/show_bug.cgi?id=398908 Ash changed: What|Removed |Added CC||ashleysom...@gmail.com --- Comment #63 from Ash --- Weighing in here with another "me too". We use Plasma 5 with latest KDE and latest Dolphin on a VM at work. The VM has 8 NFS4 shares permanently mounted. If we leave a Dolphin window open overnight, the memory usage creeps up from approx 500mb used to 32GB (100%) and other applications and services start crashing due to lack of memory. While the memory usage is climbing, the CPU usage also gradually increases from 1% to 100% usage, and stays at 100% usage until I close all open Dolphin windows. On a different VM with no NFS mounts, this problem does not occur. We were having the same problem with Kate, but after disabling the "Filesystem" plugin, the problem no longer occurs with Kate. Note, we do also have Docker installed, others suggested it might be a culprit but I don't think it is related in this case. We disabled the docker daemon overnight one time and the problem with Dolphin still occurred. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 398908] Dolphin uses up huge amounts of memory
https://bugs.kde.org/show_bug.cgi?id=398908 --- Comment #67 from Ash --- This Bug is still present in Plasma 5.18.5 and KDE Frameworks 5.70. I tried what Andrei suggested, I built a modified libKF5Solid with the overlays feature removed, and then opened Dolphin to leave it running for 48 hours over the weekend. Unfortunately in my case, it did not fix it. The Dolphin process grew to over 7.8GB memory used, and 100% (of one core) CPU usage for at least the last 24 hours. I believe in this case it is not related to Docker overlays, but more likely related to the multiple NFS4 mounts on the system. I have a different VM with same Ubuntu OS and very similar software stack, it has only one (different) NFS4 mount, and it is not affected by this bug. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 398908] MimeTypeFinderJob can use huge amounts of memory reading unnecessary data
https://bugs.kde.org/show_bug.cgi?id=398908 --- Comment #104 from Ash --- I agree with Knut Hildebrandt The original bug which was reported, the one which I am experiencing, and commented on (#63), is not fixed. A _different_ memory leak was found, and fixed, (changing the title of this bug to reflect that was a nice touch) but the bug matching the description of the original report is not fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444641] New: Crash wl_display@1: error 1: invalid arguments for org_kde_plasma_window@207.get_icon
https://bugs.kde.org/show_bug.cgi?id=444641 Bug ID: 444641 Summary: Crash wl_display@1: error 1: invalid arguments for org_kde_plasma_window@207.get_icon Product: plasmashell Version: 5.22.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: a...@heyquark.com Target Milestone: 1.0 Created attachment 143019 --> https://bugs.kde.org/attachment.cgi?id=143019=edit systemd logs at time of crash, see 12:46:44 and 12:46:56 SUMMARY Shell and Wayland apps crashed twice in quick succession while I was working. Logs say wl_display@1: error 1: invalid arguments for org_kde_plasma_window@207.get_icon. STEPS TO REPRODUCE Unsure. Was using Firefox (XWayland) and Ghidra (Java, I think Wayland-native?) across two virtual desktops when the shell crashed. I pressed Meta to open the menu and it crashed again. OBSERVED RESULT Plasma crashes with wl_display@1: error 1: invalid arguments for org_kde_plasma_window@207.get_icon. EXPECTED RESULT Plasma doesn't crash. SOFTWARE/OS VERSIONS Operating System: Fedora 34 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.14.13-200.fc34.x86_64 (64-bit) Graphics Platform: Wayland Processors: 24 × Intel® Xeon® CPU E5-2620 v3 @ 2.40GHz Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon HD 7700 Series ADDITIONAL INFORMATION Logs attached - they're kinda log, crashes occur at 12:46:44 and 12:46:56. I closed all my windows and it seems stable again. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 451945] New: Add haptics after the hold timeout has been reached
https://bugs.kde.org/show_bug.cgi?id=451945 Bug ID: 451945 Summary: Add haptics after the hold timeout has been reached Product: kdeconnect Version: 22.03.80 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: ios-application Assignee: lucas.w...@tuta.io Reporter: ryancarlfrank...@gmail.com Target Milestone: --- SUMMARY When using the hold feature on the "Remote Input" feature, there is currently no feedback given after the threshold for holding the cursor, meaning it's more of a guess for if you will click or hold. To fix, it'd just be a small vibration once the 0.5s (feels like around that) timeout has been reached to indicate a click and drag will take place -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452215] Touching edge of screen can focus windows behind a fullscreen application
https://bugs.kde.org/show_bug.cgi?id=452215 --- Comment #1 from Ash --- Created attachment 147924 --> https://bugs.kde.org/attachment.cgi?id=147924=edit Video showing touch and effect -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452215] New: Touching edge of screen can focus windows behind a fullscreen application
https://bugs.kde.org/show_bug.cgi?id=452215 Bug ID: 452215 Summary: Touching edge of screen can focus windows behind a fullscreen application Product: plasmashell Version: 5.24.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: a...@heyquark.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY Touching the very edge of a touchscreen device can bring forward windows that are behind other, fullscreen windows, and are partially offscreen. STEPS TO REPRODUCE 1. Open any application and move it so the window is partially offscreen. 2. Open a fullscreen-capable application (e.g. Firefox) and enter fullscreen (F11). 3. Touch the very edge of the screen, where your windowed application is overlapping it. OBSERVED RESULT The windowed application is focused. EXPECTED RESULT No applications switch focus and the fullscreen application responds to the touch. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 35 (available in About System) KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Tested on Wayland session with a HiDPI screen (2240x1400@150%) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 451736] New: Scrolling does not reflect the user's scrolling direction
https://bugs.kde.org/show_bug.cgi?id=451736 Bug ID: 451736 Summary: Scrolling does not reflect the user's scrolling direction Product: kdeconnect Version: 22.03.80 Platform: Manjaro OS: iOS Status: REPORTED Severity: minor Priority: NOR Component: ios-application Assignee: lucas.w...@tuta.io Reporter: ryancarlfrank...@gmail.com Target Milestone: --- SUMMARY On the "Remote input" section of the KDE Connect app, there is a scroll wheel for moving up and down, however, sliding up on the app has the opposite effect to scrolling with a normal mouse (Hardware > input > mouse > invert scrolling direction off/default). Sliding up on the app does the same thing as moving the wheel of the mouse down STEPS TO REPRODUCE 1. Open the remote input page on KDE connect 2. Scroll up/down OBSERVED RESULT Scrolling is the opposite way around to scrolling on a normal mouse EXPECTED RESULT Scrolling should be inverted, where sliding up does the same as moving the wheel up SOFTWARE/OS VERSIONS KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 451737] New: Using KDE Connect as a "laptop"
https://bugs.kde.org/show_bug.cgi?id=451737 Bug ID: 451737 Summary: Using KDE Connect as a "laptop" Product: kdeconnect Version: 22.03.80 Platform: Manjaro OS: iOS Status: REPORTED Severity: wishlist Priority: NOR Component: ios-application Assignee: lucas.w...@tuta.io Reporter: ryancarlfrank...@gmail.com Target Milestone: --- SUMMARY The KDE Connect app should be able to replace both the keyboard and trackpad of a laptop. Currently, the remote input is similar to a trackpad, however, a version similar to a real trackpad (multi-touch gestures etc.) would be helpful. Additionally, being able to quickly switch to keyboard input would help, as the feature is almost always rendered useless if the keyboard must be used for most inputs -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452786] WAYLAND - Secondary monitors show black screen, no wallpaper, no panels, and no windows. Only cursor.
https://bugs.kde.org/show_bug.cgi?id=452786 --- Comment #2 from Ash --- With respect, I don't think this is a duplicate of #353975 In that older bug, users are reporting it happening on both X11 and Wayland, where in my case it happens only in Wayland sessions, the screens are fine in X11. Additionally, in #353975 users describe the panels frozen but windows are still visible and able to move on the second monitor, but in this bug the panels are not visible, and windows are not visible in the second monitor (see the attached video). In #353975 it is suspected the cause is a crashed plasmashell, where restarting the plasmashell can fix the problem. However in this bug, the plasmashell is not crashed. Killing and restarting plasmashell does not affect the display of the monitors. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452786] New: WAYLAND - Secondary monitors show black screen, no wallpaper, no panels, and no windows. Only cursor.
https://bugs.kde.org/show_bug.cgi?id=452786 Bug ID: 452786 Summary: WAYLAND - Secondary monitors show black screen, no wallpaper, no panels, and no windows. Only cursor. Product: kwin Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: ashleysom...@gmail.com Target Milestone: --- Created attachment 148260 --> https://bugs.kde.org/attachment.cgi?id=148260=edit webp version of video STEPS TO REPRODUCE 1. Update to latest 5.4.24-unstable on KDE-neon unstable repos 2. Have second monitor attached and configured 3. Log into Wayland session OBSERVED RESULT My primary monitor is fine, but the secondary monitors to the left and the right are not showing my desktop background, my panels, or any windows. It shows the mouse fine. The monitors are outputting the correct resolution, and the correct rotation and offset as can be seen by the mouse pointer icon. Both monitors were working well yesterday. This morning I pulled in some updates, and restarted my session, and now I'm seeing this. Video of bug: https://i.redd.it/7q58klefjmu81.gif SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.24.4.git+unstable KDE Frameworks Version: 5.93.0.git+unstable (Note, if this bug is filed against the wrong product, please re-assign it). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452786] WAYLAND - Secondary monitors show black screen, no wallpaper, no panels, and no windows. Only cursor.
https://bugs.kde.org/show_bug.cgi?id=452786 Ash changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #3 from Ash --- I've updated to plasma 5.24.5 from Neon unstable repo this morning, and testing again, this bug is no longer occurring for me. I'm guessing this was some kind of version mismatch issue when I last updated, and it has rectified itself now when I've updated. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 430465] Add Crop option in annotation tool
https://bugs.kde.org/show_bug.cgi?id=430465 Ash changed: What|Removed |Added CC||ashleysom...@gmail.com --- Comment #14 from Ash --- It appears this feature was added to the kImageAnnotator library, but I still don't see a crop feature in Spectacle. Is it not shipped yet, or is there some secret to enable it? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 456968] KDE Wallet Manager window is blank
https://bugs.kde.org/show_bug.cgi?id=456968 Ash changed: What|Removed |Added CC||ashleysom...@gmail.com --- Comment #12 from Ash --- Same problem. I had this issue last month on one of my PCs, but it resolved itself. Now it has reappeared again, on another PC. ``` Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) libkf5wallet-bin:amd64 < 5.97.0+p20.04+tunstable+git20220907.0317-0 > Broken libkf5wallet-bin:amd64 Depends on libqca-qt5-2:amd64 < 2.3.4+p20.04+tunstable+git20220806.0051-0 > (>= 2.3.4+p20.04+tunstable+git20220830.0119) Removing libkf5wallet-bin:amd64 because I can't find libqca-qt5-2:amd64 Investigating (0) kwalletcli:amd64 < 3.02-1build1 > Broken kwalletcli:amd64 Depends on libkf5wallet-bin:amd64 < 5.97.0+p20.04+tunstable+git20220907.0317-0 > Considering libkf5wallet-bin:amd64 as a solution to kwalletcli:amd64 0 Removing kwalletcli:amd64 rather than change libkf5wallet-bin:amd64 Done Done ``` -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460329] VRR flicker possibly caused due to forced vsync and/or latency
https://bugs.kde.org/show_bug.cgi?id=460329 Ash changed: What|Removed |Added Summary|VRR flicker possibly caused |VRR flicker possibly caused |due to vsync latency|due to forced vsync and/or ||latency -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460329] VRR flicker possibly caused due to forced vsync and/or latency
https://bugs.kde.org/show_bug.cgi?id=460329 --- Comment #2 from Ash --- (In reply to Bug Janitor Service from comment #1) > Thank you for the bug report! > > Please note that Plasma 5.25.5 is not supported for much longer by KDE; > supported versions are 5.24, and 5.26 or newer. > > If at all possible please upgrade to a supported version and verify that the > bug is still happening there. I will try out 5.26 soon. I had tried 5.25.5 last week alongside my GNOME install of EndeavourOS before the new release to see if the issue had resolved since earlier versions. I may add Plasma alongside my current install again. If a fresh install is recommended I may make a fresh install or resize my main partition, as I don't want to nuke my main install. I could also try a different distro to test further. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460329] VRR flicker possibly caused due to forced vsync and/or latency
https://bugs.kde.org/show_bug.cgi?id=460329 --- Comment #3 from Ash --- Installed Plasma 5.26 on EndeavourOS like I had before with 5.25.5 along with having all packages up-to-date and here's some results I gathered for X11 and Wayland along with GNOME 42.5 in Wayland using RADV. My display has FreeSync enabled and defaults are used in each DE (1080p 144Hz used) along with VRR options enabled. - - - Plasma - X11 VRR enabled in X11 AMD config. Default display/compositor settings used. Halo MCC - Proton Flicker even with vsync and 120 FPS cap. Terraria - Native Flicker mostly gone. Half-Life 2 - Native Flicker without vsync. DOOM (2016) - Proton, Vulkan Flicker without vsync. Using the mouse in the pause menu causes an FPS drop as low as 2. Final Fantasy X HD - Proton Severe menu flicker when moving the mouse and some flicker in-game with vsync on and off. The game is limited to 60. - - - Plasma - Wayland VRR set to automatic. Default display/compositor settings used. Halo MCC - Proton Flicker even with vsync and 120 FPS cap and only slightly better. Terraria - Native No flicker at all. Half-Life 2 - Native Flicker mostly gone and only really seen during level loading. DOOM (2016) - Proton, Vulkan No flicker Using the mouse in the pause menu causes an FPS drop but not always. Final Fantasy X HD - Proton Severe menu flicker when moving the mouse and some flicker in-game with vsync on and off. The game is limited to 60. - - - GNOME - Wayland Mutter VRR patch and VRR enabled in control center. Halo MCC - Proton No menu flicker, very stable. Only the slightest flicker with anything above a 120 FPS cap when loaded in or with a rare FPS drop. Terraria - Native No flicker at all. Half-Life 2 - Native No flicker at all. DOOM (2016) - Proton, Vulkan No flicker. Using the mouse in the pause menu causes an FPS drop but not always. Final Fantasy X HD - Proton No flicker at all. - - - GNOME seems to be the best experience, which is a shame since I prefer using Plasma. Halo MCC seems the most sensitive when using Plasma. Flicker is also present in Halo MCC's menus on Plasma overall. The DOOM pause menu issue seems more likely to be a Proton or RADV issue. FPS was very steady using Wayland except for the flickering in Plasma, only fluctuating heavily using X11 in Half-Life 2 without vsync. No flicker when using the desktop itself in either DE. I would assume there's some latency causing the issue or something else that I'm not facing in GNOME. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 460022] New: I tried to render my krita animation but it wouldn't let me do so. i had tried everything, using and downloading the right file, redownload krita, all.
https://bugs.kde.org/show_bug.cgi?id=460022 Bug ID: 460022 Summary: I tried to render my krita animation but it wouldn't let me do so. i had tried everything, using and downloading the right file, redownload krita, all. Classification: Applications Product: krita Version: 5.1.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: ashantijones0...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: (x) macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446654] Feature Request: mirror a panel on all monitors
https://bugs.kde.org/show_bug.cgi?id=446654 Ash changed: What|Removed |Added Platform|Manjaro |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416501] Compositing prevents laptop to wake up from sleep state
https://bugs.kde.org/show_bug.cgi?id=416501 Ash changed: What|Removed |Added CC||djaz...@gmail.com --- Comment #9 from Ash --- Well this sounds rather familiar. We are having the same issue here. https://bbs.archlinux.org/viewtopic.php?id=283968 This is my current setup and is a desktop PC: OS: EndeavourOS x86_64 Kernel: 6.2.8-arch1-1 Display: Acer XZ271 (1920x1080 @ 144Hz) DE: KDE Plasma 5.27.3 WM: KWin (Wayland) CPU: AMD Ryzen 7 1700 (16) @ 4 GHz GPU: AMD Radeon RX 6700 XT (vulkan-radeon 23.0.1) It seems repeatable on X11 and Wayland. I can only think of it relating to power management, kwin or the lock screen, as KDE Plasma seems to be a repeating factor. I have had the issue for the past month having come from GNOME, which was fine. I even on the rare occasion have my CPU clock strangely where they fluctuate if I am able to get back in even though I have a fixed 4GHz manual clock. In this situation, input and audio becomes laggy until I restart the system. I had reset and updated my BIOS today on my ASUS Crosshair VI and will keep an eye out. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 480118] New: KdeConnect on PC Crashes every time phone is unlocked.
https://bugs.kde.org/show_bug.cgi?id=480118 Bug ID: 480118 Summary: KdeConnect on PC Crashes every time phone is unlocked. Classification: Applications Product: kdeconnect Version: 23.08.4 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: ashleysom...@gmail.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- Application: kdeconnectd (23.08.4) Qt Version: 5.15.12 Frameworks Version: 5.114.0 Operating System: Linux 6.5.0-14-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.04.3 LTS DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: Similar to a lot of other recently submitted issues, possibly duplicate. The crash can be reproduced every time. -- Backtrace: Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault [KCrash Handler] #4 0x7f2f058d187e in Device::reloadPlugins() () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.23 #5 0x7f2f058d1aa1 in Device::pairingHandler_pairingSuccessful() () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.23 #6 0x7f2f042f4db4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f2f058c2519 in PairingHandler::acceptPairing() () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.23 #8 0x7f2f042f4db4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f2f0585c350 in KNotification::activate(unsigned int) () from /lib/x86_64-linux-gnu/libKF5Notifications.so.5 #10 0x7f2f0585efc9 in ?? () from /lib/x86_64-linux-gnu/libKF5Notifications.so.5 #11 0x7f2f042f4db4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f2f05862b83 in KNotificationPlugin::actionInvoked(int, int) () from /lib/x86_64-linux-gnu/libKF5Notifications.so.5 #13 0x7f2f0587154b in ?? () from /lib/x86_64-linux-gnu/libKF5Notifications.so.5 #14 0x7f2f042f4db4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f2f0587bf15 in ?? () from /lib/x86_64-linux-gnu/libKF5Notifications.so.5 #16 0x7f2f0587ca03 in ?? () from /lib/x86_64-linux-gnu/libKF5Notifications.so.5 #17 0x7f2f054f7feb in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #18 0x7f2f042ea85e in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f2f04f6c783 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f2f042bd30a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f2f042c0407 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f2f043171a7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7f2f02bc7d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7f2f02c1d258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7f2f02bc53e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7f2f043167f8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7f2f042bbc2b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7f2f042c41d4 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x55e8d4855001 in ?? () #30 0x7f2f03829d90 in __libc_start_call_main (main=main@entry=0x55e8d4854bd0, argc=argc@entry=1, argv=argv@entry=0x7ffd681cb3b8) at ../sysdeps/nptl/libc_start_call_main.h:58 #31 0x7f2f03829e40 in __libc_start_main_impl (main=0x55e8d4854bd0, argc=1, argv=0x7ffd681cb3b8, init=, fini=, rtld_fini=, stack_end=0x7ffd681cb3a8) at ../csu/libc-start.c:392 #32 0x55e8d4855285 in ?? () [Inferior 1 (process 4227) detached] The reporter indicates this bug may be a duplicate of or related to bug 478265, bug 475960, bug 478768, bug 479595, bug 479610. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 475054] kdeconnectd crashes in Device::reloadPlugins
https://bugs.kde.org/show_bug.cgi?id=475054 Ash changed: What|Removed |Added CC||ashleysom...@gmail.com --- Comment #10 from Ash --- *** Bug 480118 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 480118] KdeConnect on PC Crashes every time phone is unlocked.
https://bugs.kde.org/show_bug.cgi?id=480118 --- Comment #2 from Ash --- *** This bug has been marked as a duplicate of bug 475054 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 480118] KdeConnect on PC Crashes every time phone is unlocked.
https://bugs.kde.org/show_bug.cgi?id=480118 Ash changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Ash --- *** This bug has been marked as a duplicate of bug 475960 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 475960] Kde connect crash each time
https://bugs.kde.org/show_bug.cgi?id=475960 Ash changed: What|Removed |Added CC||ashleysom...@gmail.com --- Comment #6 from Ash --- *** Bug 480118 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 479595] Daemon crashes after update and restart
https://bugs.kde.org/show_bug.cgi?id=479595 Ash changed: What|Removed |Added CC||ashleysom...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481791] QT6 applications on wayland crash with "wl_pointer" has no event 10
https://bugs.kde.org/show_bug.cgi?id=481791 --- Comment #2 from Ash --- This article shows the high-resolution scroll event support was added in Wayland 1.21: https://www.phoronix.com/news/Wayland-1.21-Released libwayand-client0 libwayland-server0 on my installation are both on 1.22.0-0xneon+22.04+jammy+release+build21 qt6-wayland is on 6.6.2-0xneon+22.04+jammy+release+build18 I've confirmed libqt6waylandclient is dynamically linked to libwayand-client0 v1.22.0-0 Support for high-resolution scroll was added to QT6 during the v6.5 development phase back in 2022, so its been in there a while: https://github.com/qt/qtwayland/commit/f1e71327d462d2dae0b46677bbc478afb0d1b2f7 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481791] QT6 applications on wayland crash with "wl_pointer" has no event 10
https://bugs.kde.org/show_bug.cgi?id=481791 --- Comment #4 from Ash --- Created attachment 166078 --> https://bugs.kde.org/attachment.cgi?id=166078=edit Output with WL_DEBUG=1 Added attachment, running Konsole v24.02.0 with WL_DEBUG=1 Log records the application opening, I move the mouse around the Konsole window for about 1 second, then I scroll the scrollwheel wheel down, the application immediately crashes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481791] QT6 applications on wayland crash with "wl_pointer" has no event 10
https://bugs.kde.org/show_bug.cgi?id=481791 --- Comment #1 from Ash --- Note, I suspect this is a neon build/packaging error, or a QT6 bug. But I posted here because to see if anyone can help me debug exactly where the issue is coming from. I haven't tried with QT6 v6.7.0 yet, only using the v6.6.2 release from neon "release" channel. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481791] QT6 applications on wayland crash with "wl_pointer" has no event 10
https://bugs.kde.org/show_bug.cgi?id=481791 --- Comment #5 from Ash --- (In reply to Ash from comment #4) > Created attachment 166078 [details] > Output with WL_DEBUG=1 > > Added attachment, running Konsole v24.02.0 with WL_DEBUG=1 > Log records the application opening, I move the mouse around the Konsole > window for about 1 second, then I scroll the scrollwheel wheel down, the > application immediately crashes. Typo in previous comment, I ran with WAYLAND_DEBUG=1, not WL_DEBUG. Correct debug variable can be seen in the log file. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481791] New: QT6 applications on wayland crash with "wl_pointer" has no event 10
https://bugs.kde.org/show_bug.cgi?id=481791 Bug ID: 481791 Summary: QT6 applications on wayland crash with "wl_pointer" has no event 10 Classification: Plasma Product: kwin Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: ashleysom...@gmail.com Target Milestone: --- SUMMARY Using Plasma 6 that recently landed on KDE Neon "Release" distribution channel. KWin version = 4:6.0.0-0xneon+22.04+jammy+release+build65 QT6 version = 6.6.2-0xneon+22.04+jammy+release+build75 Libinput version = 1.20.0-1ubuntu0.3 Using a logitech MX Ergo mouse with the logitech unifying receiver, and the hid_logitech_hidpp kernel driver. The driver emits "high resolution scroll" events when the scroll wheel is used. "wl_pointer" is a Wayland protocol interface. Event 10 is the "high resolution" scroll event (aka Axis 120 event) STEPS TO REPRODUCE 1. Install QT6 from Neon "release" channel (based on Ubuntu 22.04) 2. Install Plasma6 from Neon "release" channel (based on Ubuntu 22.04) 3. Launch into a Plasma Wayland Session 4. Open any QT6 application (eg, konsole v24.02, or dolphin v24.02) 5. Scroll the wheel on any logitech HID++ mouse OBSERVED RESULT QT6 application crashes, Error printed to console: --- interface 'wl_pointer' has no event 10 The Wayland connection experienced a fatal error: Bad address --- EXPECTED RESULT Applications should not crash when receiving a high resolution scroll event. SOFTWARE/OS VERSIONS Linux: 6.5.0-21 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 DISCUSSION: This occurs only on QT6 applications. GTK3 and GTK4 apps work fine, and QT5 applications work fine. This occurs only in Plasma6 Wayland session. Plasma6 X11 is fine, and Gnome 45 Wayland session is fine. I suspect there is a wayland protocol mismatch between the Wayland server (kwin-wayland) and the wayland client (Qt6). Perhaps the version of QT6.6.2 in Neon "release" channel is compiled against an older libwayland-client, not sure. This shouldn't be an issue though, because kwin _does_ check the client protocol version before sending the event: https://github.com/KDE/kwin/blob/8029c5c7acd004bd26fd539d3948c1ecf758abab/src/wayland/pointer.cpp#L280 I have even attempted to work around this issue by filtering high-resolution scroll events in libinput using the quirks line: AttrEventCodeDisable=REL_WHEEL_HI_RES;REL_HWHEEL_HI_RES; I have confirmed using libinput tools this event is now disabled, but Plasma Kwin-wayland still receives high resolution scroll events and sends them to the wayland client. So either kwin is bypassing libpinput and receiving libev kernel events, or using its own libinput config without the event codes disabled? That is the extent of my digging on that. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481791] QT6 applications on wayland crash with "wl_pointer" has no event 10
https://bugs.kde.org/show_bug.cgi?id=481791 Ash changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #6 from Ash --- This seems to be resolved now. Yesterday I updated some packages to newer releases on the neon "release" channel. These included: * kf6-kguiaddons=6.0.0-0xneon+22.04+jammy+release+build4 * kf6-purpose=6.0.0-0xneon+22.04+jammy+release+build9 * kwin-common=4:6.0.0-0xneon+22.04+jammy+release+build66 * kwin-data=4:6.0.0-0xneon+22.04+jammy+release+build66 * kwin-wayland=4:6.0.0-0xneon+22.04+jammy+release+build66 * libkwineffects14=4:6.0.0-0xneon+22.04+jammy+release+build66 * libkwinglutils=4:6.0.0-0xneon+22.04+jammy+release+build66 After that, general QT6 applications like Konsole and Dolphin were _no longer_ crashing on scroll inputs. But KDE Plasma components (panels, panel widgets, app launcher, networks popup) were all still crashing on scroll input. Then early this morning I just updated some more new package releases that appeared on the neon "release" channel. This included: * libplasma6=6.0.0-0xneon+22.04+jammy+release+build8 * kf6-plasma-framework=6.0.0-0xneon+22.04+jammy+release+build8 * plasma-framework6=6.0.0-0xneon+22.04+jammy+release+build8 Now I no longer see any crash on scroll input in KDE Plasma components. So I suppose this has resolved itself, this can be closed. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481791] QT6 applications on wayland crash with "wl_pointer" has no event 10
https://bugs.kde.org/show_bug.cgi?id=481791 --- Comment #9 from Ash --- Yep, I can confirm I was still having this error in xdg-desktop-portal-kde windows (file open, in firefox and chrome) even after my last comment. Also since https://bugs.kde.org/show_bug.cgi?id=481972 is now fixed, this issue is now resolved. -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 374510] Creating albums on flickr with line breaks in their descriptions fails [patch]
https://bugs.kde.org/show_bug.cgi?id=374510 --- Comment #3 from Richard Ash <rich...@audacityteam.org> --- Confirmed fixed in 5.4.0 -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 374442] Exporting images with line breaks in their captions to flickr fails
https://bugs.kde.org/show_bug.cgi?id=374442 --- Comment #6 from Richard Ash <rich...@audacityteam.org> --- Confirmed fixed in 5.4.0 -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 374442] New: Exporting images with line breaks in their captions to flickr fails
https://bugs.kde.org/show_bug.cgi?id=374442 Bug ID: 374442 Summary: Exporting images with line breaks in their captions to flickr fails Product: kipiplugins Version: 5.3.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Flickr Assignee: kde-imag...@kde.org Reporter: rich...@audacityteam.org Target Milestone: --- I can export images from Digikam 5.3.0 to flickr without issue if they have no caption (used for the Flickr description field), or if they have a caption which consists of a single line of text. However if I have a line break in the caption (typed by pressing enter in the caption field) then the upload always fails with the "Invalid signature" error code from Flickr. Also reproduced with a build of 5.4.0 from git. I did some debugging and testing: * Digikam presents the caption to the plugin as a plain text QString with the line break represented by a line feed character (0xOA). * Flickr's API documentation for the description just says "A description of the photo. May contain some limited HTML." with no detail on what the limits are. https://www.flickr.com/services/api/upload.api.html I tried a few different things to see if I could hit on a solution: * If the newline character is stripped out, then the upload succeeds (so nothing else is wrong). * If the newline is replaced by a CRLF pair, then the same error occurs * If the newline is replaced by a CR (only) then the same error occurs * If the newline is replaced by the HTML tag then the upload succeeds (signature must be OK), but the tag is removed, resulting in a one-line caption with the words either side of the break run together. My suspicion (but I can't prove it) is that the description text is getting altered before the server-side signature check, which means it doesn't pass - but without knowing what to, we can't get the right signature! -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 374441] New: Export original file to Flickr [patch]
https://bugs.kde.org/show_bug.cgi?id=374441 Bug ID: 374441 Summary: Export original file to Flickr [patch] Product: kipiplugins Version: 5.3.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Flickr Assignee: kde-imag...@kde.org Reporter: rich...@audacityteam.org Target Milestone: --- Created attachment 103134 --> https://bugs.kde.org/attachment.cgi?id=103134=edit Patch to add option to upload the original file to Flickr The same missing feature that prompted #212106 has re-appeared in Digikam 5.3 (I upgraded from 4.4 to 5.3 so not sure exactly where it got lost). The problem is that when uploading to flickr, all images are re-compressed as (lossy) JPEGs, even if they are already in JPEG format. I want to upload the JPEG files I have, so that Flickr Pro acts as one of my backup locations. I have re-done Stanislav Ochotnicky's patch against current (5.4.0) git and this is working. The same limitations as before apply, chiefly that it doesn't do anything intelligent if you try to upload and image in a format which Flickr doesn't support. This is not however an issue for most users. -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 374442] Exporting images with line breaks in their captions to flickr fails
https://bugs.kde.org/show_bug.cgi?id=374442 --- Comment #1 from Richard Ash <rich...@audacityteam.org> --- Flickr discussion topic on the "how do we get new lines" question here: https://www.flickr.com/groups/api/discuss/72157674855445343/ -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 374510] New: Creating albums on flickr with line breaks in their descriptions fails
https://bugs.kde.org/show_bug.cgi?id=374510 Bug ID: 374510 Summary: Creating albums on flickr with line breaks in their descriptions fails Product: kipiplugins Version: 5.4.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Flickr Assignee: kde-imag...@kde.org Reporter: rich...@audacityteam.org Target Milestone: --- Created attachment 103177 --> https://bugs.kde.org/attachment.cgi?id=103177=edit Patch to remove new lines from album descriptions as well. This is the same bug as #374442, but with photosets instead of photos. Patch supplied to apply the same work-around as for #374442 for the moment. -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 374442] Exporting images with line breaks in their captions to flickr fails
https://bugs.kde.org/show_bug.cgi?id=374442 --- Comment #4 from Richard Ash <rich...@audacityteam.org> --- I wondered if this was responsible for other people's issues. I've been using the line-feed substitution as a work-around. Can confirm that the fix in Git works for me. What is annoying is that in 4.4.0 this worked fine, but I can't see any relevant difference in the code, except that 4.4.0 used kurl instead of QUrl and wasn't (I don't think) working in UTF-8. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384059] New: Album > Reread metadata from images does not work correctly
https://bugs.kde.org/show_bug.cgi?id=384059 Bug ID: 384059 Summary: Album > Reread metadata from images does not work correctly Product: digikam Version: 5.5.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tags-Captions Assignee: digikam-bugs-n...@kde.org Reporter: rich...@audacityteam.org Target Milestone: --- Whilst I was on holiday, I went through some images on my laptop, adding captions (no tags) to them and deleting some. I now want to transfer the images back to my main desktop PC, taking the new captions with me. The two machines do not share a database, both use the default sqlite database. Images are from-camera JPEGs. Album 1: 1. I verified on the laptop (source machine) that captions had been written to all the configured fields in the file (default list including Xmp.tiff.ImageDescription and Xmp.dc.description). 2. I then copied the image files using scp to the desktop PC 3. I started Digikam and let it scan for new items (set to happen at startup) 4. I went to the newly copied album, and did "Album > Reread metadata from images". In the past I have used this to read in the captions from the file data. 5. It didn't work, and neither did the same entry on the Item menu. The "completed" message popped up so quickly and with no disk activity that I don't think it actually checked the images at all. Certainly much quicker than generating a thumbnail. 6.Opening the metadata editor window at this point showed all the fields filled in with the caption, but even after clicking OK, the image thumbnail and captions tab of the right-hand side bar had no caption available. 7. After much cursing, I tried selecting one image, and using the "More > Read metadata from file to Database" button in the captions tab of the right-hand side bar. This worked, read the file and populated the thumbnail / sidebar. Manually working through each file in the album got the information into the database. So this has a work-around, but a painful one for any number of images. Album 2: I went to repeat this, but found the other two albums have not had the captions written to the files on the source machine. So I am stuck even earlier: - No amount of Album > Write Metadata to Images writes it out - Again the completed notification is instant, far faster than disk access times on this machine. - More > Write Metadata to each file button in the right-hand side bar is greyed out - I have tried turning lazy synchronisation off, no change. - I tried altering the preferences so that an XMP sidecar is written as well as to the image file, but no sidecar files are written! - If I edit the caption again and then click Apply the changed caption is written out, but this means manually altering (no-op) every single caption by hand (as they are different to each other). A potential work-around exists but is very labour intensive. I think I am correct to say that when I completed editing captions on this album (with lazy sync turned on) I just quit Digikam, without manually telling it to sync changes, where as I synced changes by hand on Album 1. Does this mean that sync-pending-changes-on-exit is broken as well? I am in the process of updating to Digikam 5.6.0 to see if anything changes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438097] [AnimationEffect] kwin_wayland sometimes crashes when xwayland tries to display a popup
https://bugs.kde.org/show_bug.cgi?id=438097
Ash Blake changed:
What|Removed |Added
CC||telepath...@tutanota.com
--- Comment #14 from Ash Blake ---
Created attachment 141780
--> https://bugs.kde.org/attachment.cgi?id=141780=edit
Backtrace from 5.22.90
This is a backtrace from Plasma 5.22.90 from the Arch Linux kde-unstable repo,
with the KWin package rebuilt from source to provide debug symbols.
The crash happened randomly while using Jetbrains IntelliJ IDEA.
My effects setup is mostly default, I only enabled the new Overview effect.
Effect list:
- kwin4_effect_windowaperture
- kwin4_effect_squash
- kwin4_effect_sessionquit
- kwin4_effect_morphingpopups
- kwin4_effect_maximize
- kwin4_effect_logout
- kwin4_effect_login
- kwin4_effect_fullscreen
- kwin4_effect_frozenapp
- kwin4_effect_fadingpopups
- kwin4_effect_fade
- kwin4_effect_dialogparent
- zoom
- slidingpopups
- slide
- screenshot
- desktopgrid
- colorpicker
- presentwindows
- overview
- highlightwindow
- blur
- contrast
- startupfeedback
- screenedge
- screentransform
- kscreen
I analysed the core dump with GDB - the crash happened in kwin4_effect_fade.
Redacted log from the gdb session (at the innermost stack frame):
(gdb) set print pretty on
(gdb) set print object on
(gdb) p *this
$1 = (KWin::ScriptedEffect) {
...
members of KWin::ScriptedEffect:
...
m_effectName = {
d = 0x55f534b8f590
},
...
}
(gdb) p this->m_effectName->d
$3 = (QString::Data *) 0x55f534b8f590
(gdb) set $data_start = (char*)this->m_effectName->d +
this->m_effectName->d->offset
(gdb) set $len = this->m_effectName->d->size
(gdb) set $i = 0
(gdb) while $i < 2*$len
>printf "%c", *($data_start + $i)
>set $i = $i + 2
>end
kwin4_effect_fade
When the crash happens again, I'll check if it was the same effect.
If so, I'll disable it and test some more.
Some information about that EffectWindow pointer:
(gdb) p *(entry.i->key)
$45 = {
= {},
members of KWin::EffectWindow:
static staticMetaObject = {
d = {
superdata = {
direct = 0x7f9fae97c740
},
stringdata = 0x7f9fafda5ae0 ,
data = 0x7f9fafda55a0 ,
static_metacall = 0x7f9fafd8ced0
,
relatedMetaObjects = 0x0,
extradata = 0x0
}
},
d = {
d = 0x20a0282
}
}
(gdb) p &(entry.i->key->d)
$33 = (QScopedPointer > *) 0x55f53571a4d0
(gdb) p entry.i->key->d.d
$34 = (KWin::EffectWindow::Private *) 0x20a0282
(gdb) p *(entry.i->key->d.d)
Cannot access memory at address 0x20a0282
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 438097] [AnimationEffect] kwin_wayland sometimes crashes when xwayland tries to display a popup
https://bugs.kde.org/show_bug.cgi?id=438097 --- Comment #25 from Ash Blake --- This is pretty weird. I just tried running IDEA in KWin only, started from a TTY. The file descriptor amount does not skyrocket, and everything is stable. It also works fine in nested KWin inside a Plasma session. Seems like some other Plasma component is causing KWin to leak file descriptors. I tried killing various combinations of Plasma processes, and it looks like killing plasmashell, xdg-desktop-portal, and xdg-desktop-portal-kde helps. KWin does not leak file descriptors anymore, and it does not crash. I guess plasmashell and xdg-desktop-portal-kde could be trying to read some information about the popup window, but failure might not be handled correctly and new pipe descriptors get created over and over during each retry attempt until KWin crashes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438010] kwin crashes when clicking on MPV with a pen
https://bugs.kde.org/show_bug.cgi?id=438010 --- Comment #12 from Ash Blake --- I attached GDB to KWin and checked where the null pointer came from in TabletToolV2InterfacePrivate::targetResource(). m_surface was not null, but later resourceMap().value(*client) returned 0x0. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438097] [AnimationEffect] kwin_wayland sometimes crashes when xwayland tries to display a popup
https://bugs.kde.org/show_bug.cgi?id=438097 --- Comment #37 from Ash Blake --- (In reply to Vlad Zahorodnii from comment #36) > Created attachment 141876 [details] > Potential solution (untested) > > If you apply the attached patch, does the issue go away? Yes, I just tested it with 1000 windows and there are no leaked descriptors. In the strace output, there are now close() calls for every FD. When using a Jetbrains IDE everything works fine as well. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438010] kwin crashes when clicking on MPV with a pen
https://bugs.kde.org/show_bug.cgi?id=438010 Ash Blake changed: What|Removed |Added CC||telepath...@tutanota.com --- Comment #10 from Ash Blake --- Created attachment 141879 --> https://bugs.kde.org/attachment.cgi?id=141879=edit Backtrace from current git master I can reproduce this as well, with a Huion tablet. I don't know how to make GDB show line numbers for functions called via std::bind, so here's the disassembly of the part around frame #1: ... 0x7f0e976df57f <+95>:mov%ebp,%esi 0x7f0e976df581 <+97>:call 0x7f0e97625150 <_ZN14KWaylandServer21TabletToolV2Interface10sendButtonEjb@plt> => 0x7f0e976df586 <+102>: add$0x8,%rsp 0x7f0e976df58a <+106>: mov$0x1,%eax 0x7f0e976df58f <+111>: pop%rbx ... Looks like this happened in kwin/src/input.cpp:1862 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438097] [AnimationEffect] kwin_wayland sometimes crashes when xwayland tries to display a popup
https://bugs.kde.org/show_bug.cgi?id=438097 --- Comment #32 from Ash Blake --- Created attachment 141875 --> https://bugs.kde.org/attachment.cgi?id=141875=edit A Python script that parses strace output for FD information I wrote a script to parse strace output and abbreviate it, displaying only close() calls and recvmsg() calls, but filtered by cmsg_type=SCM_RIGHTS and abbreviated so that only the cmsg_data part containing newly received file descriptors is visible. After terminating the script with Ctrl+C, it will display all the file descriptors that have been received by the KWin process, but not closed. This is the output in a bug-free situation (the reproducing program was ran with a burst size of 20 and window lifetime of 100ms, which does not trigger the bug) $ sudo strace -e trace=recvmsg,close -p `pidof kwin_wayland` 2>&1 | python process_strace.py close(5670) = 0 recvmsg(44,...,cmsg_data=[5670],...) = 152 close(5670) = 0 recvmsg(48,...,cmsg_data=[5670, 5675],...) = 16 recvmsg(44,...,cmsg_data=[5670],...) = 152 close(5670) = 0 recvmsg(48,...,cmsg_data=[5670, 5675],...) = 16 recvmsg(44,...,cmsg_data=[5670],...) = 152 close(5670) = 0 recvmsg(48,...,cmsg_data=[5670, 5675],...) = 16 recvmsg(44,...,cmsg_data=[5670],...) = 152 close(5670) = 0 recvmsg(48,...,cmsg_data=[5670, 5675],...) = 16 recvmsg(44,...,cmsg_data=[5670],...) = 152 close(5670) = 0 recvmsg(48,...,cmsg_data=[5670, 5675],...) = 16 recvmsg(44,...,cmsg_data=[5670],...) = 152 close(5670) = 0 recvmsg(48,...,cmsg_data=[5670, 5675],...) = 16 recvmsg(44,...,cmsg_data=[5670],...) = 152 close(5670) = 0 recvmsg(48,...,cmsg_data=[5670, 5675],...) = 16 recvmsg(44,...,cmsg_data=[5670],...) = 152 close(5670) = 0 recvmsg(48,...,cmsg_data=[5670, 5675],...) = 16 recvmsg(44,...,cmsg_data=[5670],...) = 152 close(5670) = 0 recvmsg(48,...,cmsg_data=[5670, 5675],...) = 16 recvmsg(44,...,cmsg_data=[5670],...) = 152 close(5670) = 0 recvmsg(48,...,cmsg_data=[5670, 5675],...) = 16 recvmsg(44,...,cmsg_data=[5670],...) = 152 close(5670) = 0 recvmsg(48,...,cmsg_data=[5670, 5675],...) = 16 recvmsg(44,...,cmsg_data=[5670],...) = 152 close(5670) = 0 recvmsg(48,...,cmsg_data=[5670, 5675],...) = 16 recvmsg(44,...,cmsg_data=[5670],...) = 152 close(5670) = 0 recvmsg(48,...,cmsg_data=[5670, 5675],...) = 16 recvmsg(44,...,cmsg_data=[5670],...) = 152 close(5670) = 0 recvmsg(48,...,cmsg_data=[5670, 5675],...) = 16 recvmsg(44,...,cmsg_data=[5670],...) = 152 close(5670) = 0 recvmsg(48,...,cmsg_data=[5670, 5675],...) = 16 recvmsg(44,...,cmsg_data=[5670],...) = 152 close(5670) = 0 recvmsg(48,...,cmsg_data=[5670, 5675],...) = 16 recvmsg(44,...,cmsg_data=[5670],...) = 152 close(5670) = 0 recvmsg(48,...,cmsg_data=[5670, 5675],...) = 16 recvmsg(44,...,cmsg_data=[5670],...) = 152 close(5670) = 0 recvmsg(48,...,cmsg_data=[5670],...) = 84 recvmsg(48,...,cmsg_data=[5670],...) = 8 recvmsg(44,...,cmsg_data=[5670],...) = 152 close(5670) = 0 recvmsg(48,...,cmsg_data=[5670, 5675],...) = 16 recvmsg(44,...,cmsg_data=[5670],...) = 152 close(5670) = 0 recvmsg(48,...,cmsg_data=[5670, 5675],...) = 16 ^CThese descriptors were left open: 5670, 5675 The mentioned descriptors have been however closed shortly after. This is the output with also 20 windows, but a lifetime of 16ms: $ sudo strace -e trace=recvmsg,close -p `pidof kwin_wayland` 2>&1 | python process_strace.py recvmsg(44,...,cmsg_data=[5696],...) = 152 close(5696) = 0 recvmsg(48,...,cmsg_data=[5696, 5697],...) = 16 recvmsg(44,...,cmsg_data=[5696],...) = 152 close(5696) = 0 recvmsg(48,...,cmsg_data=[5696, 5697],...) = 16 recvmsg(44,...,cmsg_data=[5700],...) = 152 close(5700) = 0 recvmsg(48,...,cmsg_data=[5700, 5701],...) = 16 recvmsg(44,...,cmsg_data=[5700],...) = 152 close(5700) = 0 recvmsg(44,...,cmsg_data=[5700],...) = 152 close(5700) = 0 recvmsg(48,...,cmsg_data=[5700, 5701],...) = 16 recvmsg(44,...,cmsg_data=[5702],...) = 152 close(5702) =
[kwin] [Bug 438010] kwin crashes when clicking on MPV with a pen
https://bugs.kde.org/show_bug.cgi?id=438010 --- Comment #11 from Ash Blake --- I rebuilt libwayland with debug symbols. Resource was a null pointer: #0 wl_resource_post_event (resource=0x0, opcode=17) at ../wayland-1.19.0/src/wayland-server.c:248 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438097] [AnimationEffect] kwin_wayland sometimes crashes when xwayland tries to display a popup
https://bugs.kde.org/show_bug.cgi?id=438097 --- Comment #34 from Ash Blake --- (In reply to Vlad Zahorodnii from comment #33) > Thanks for the great analysis, Ash! This is definitely very strange. At > quick glance, I don't see how file descriptors can be leaked in kwin. Well, it doesn't seem to be KWin that leaks them. It happens along the way in libwayland. This one is perhaps more useful - same test as above, but only one window gets created with a 16ms lifetime. It appears this is actually enough to induce the bug, and patterns are more visible. close(4071) = 0 recvmsg(44,...,cmsg_data=[4071],...) = 152 close(4071) = 0 recvmsg(44,...,cmsg_data=[4034],...) = 152 close(4034) = 0 recvmsg(48,...,cmsg_data=[4034, 4035],...) = 16 recvmsg(44,...,cmsg_data=[4071],...) = 152 close(4071) = 0 recvmsg(48,...,cmsg_data=[4071, 4079],...) = 16 recvmsg(44,...,cmsg_data=[4150],...) = 152 close(4150) = 0 recvmsg(48,...,cmsg_data=[4150, 4608],...) = 16 recvmsg(44,...,cmsg_data=[4610],...) = 152 close(4610) = 0 recvmsg(48,...,cmsg_data=[4610, 4611],...) = 16 recvmsg(44,...,cmsg_data=[4612],...) = 152 close(4612) = 0 recvmsg(48,...,cmsg_data=[4612, 4615],...) = 16 recvmsg(44,...,cmsg_data=[4618],...) = 152 close(4618) = 0 recvmsg(48,...,cmsg_data=[4618, 4619],...) = 16 recvmsg(44,...,cmsg_data=[4620],...) = 152 close(4620) = 0 recvmsg(48,...,cmsg_data=[4620, 4621],...) = 16 ^CThese descriptors were left open: 4034, 4035, 4071, 4079, 4150, 4608, 4610, 4611, 4612, 4615, 4618, 4619, 4620, 4621 KWin does close every descriptor it receives. However, sometimes the process does not receive one descriptor, but two - and KWin itself is not aware of the second one, nor is it supposed to. This is the bug-free scenario (100ms lifetime): close(4622) = 0 recvmsg(44,...,cmsg_data=[4622],...) = 152 close(4622) = 0 recvmsg(48,...,cmsg_data=[4622, 5710],...) = 16 recvmsg(44,...,cmsg_data=[4622],...) = 152 close(4622) = 0 recvmsg(48,...,cmsg_data=[4622, 5710],...) = 16 recvmsg(44,...,cmsg_data=[4622],...) = 152 close(4622) = 0 recvmsg(48,...,cmsg_data=[4622, 5710],...) = 16 recvmsg(44,...,cmsg_data=[4622],...) = 152 close(4622) = 0 recvmsg(48,...,cmsg_data=[4622, 5710],...) = 16 recvmsg(44,...,cmsg_data=[4622],...) = 152 close(4622) = 0 recvmsg(48,...,cmsg_data=[4622, 5710],...) = 16 recvmsg(44,...,cmsg_data=[4622],...) = 152 close(4622) = 0 recvmsg(48,...,cmsg_data=[4622, 5710],...) = 16 recvmsg(44,...,cmsg_data=[4622],...) = 152 close(4622) = 0 recvmsg(48,...,cmsg_data=[4622, 5710],...) = 16 ^CThese descriptors were left open: 4622, 5710 (And those two descriptors got closed shortly after) Here the same thing happens, however things happen slowly enough so that the descriptor can get reused, hence the fd amount is not rising. It seems like this is not KWin's fault, but it's Wayland that is doing something weird when marshaling those descriptors. org_kde_plasma_window_get_icon is supposed to accept one file descriptor, and plasmashell does give it exactly one descriptor. Things get messed up along the way, and this is not an issue anywhere in the KDE code. While researching the topic of SCM_RIGHTS, I stumbled upon this link: https://gist.github.com/kentonv/bc7592af98c68ba2738f4436920868dc This part sounds like it could be a problem here: > However, as always, recvmsg() calls on the receiving end don't necessarily > map 1:1 to sendmsg() calls. Messages can be coalesced or split. Sounds like things can get mixed up when messages are getting sent fast enough. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438010] kwin crashes when clicking on MPV with a pen
https://bugs.kde.org/show_bug.cgi?id=438010 --- Comment #13 from Ash Blake --- This happened because there was no check if the resource is valid before calling sendButton. I created a merge request: https://invent.kde.org/plasma/kwin/-/merge_requests/1461 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442852] Fast user switching is broken since 5.23 beta
https://bugs.kde.org/show_bug.cgi?id=442852 Ash Blake changed: What|Removed |Added CC||telepath...@tutanota.com --- Comment #2 from Ash Blake --- This is a regression from commit 714ce4045e0cbbba1d440b2fcb6f547f2680799f in plasma-workspace. The property m which exposed the model has been removed from UserDelegate, but it wasn't unused. In SessionManagementScreen, userListCurrentModelData was supposed to be pointing at userListView.currentItem.m which is now undefined. The only usage of userListCurrentModelData is in LockScreenUi.qml:436, where the TypeError occurs. Reverting that commit makes user switching work again. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442852] Fast user switching is broken since 5.23 beta
https://bugs.kde.org/show_bug.cgi?id=442852 --- Comment #4 from Ash Blake --- Proposed fix that also fixes the original warnings: https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1081 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439873] Switching users isn't working on Wayland
https://bugs.kde.org/show_bug.cgi?id=439873 --- Comment #11 from Ash Blake --- Created attachment 141939 --> https://bugs.kde.org/attachment.cgi?id=141939=edit Another backtrace, crash in DrmPipeline::populateAtomicValues Another crash on VT switch. obj pointed to an unreadable location. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438010] kwin crashes when clicking on MPV with a pen
https://bugs.kde.org/show_bug.cgi?id=438010 Ash Blake changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/kwin/commit/242de4373706 ||324696a9bfe48b1ac9e2f7e2caa ||2 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #14 from Ash Blake --- Git commit 242de4373706324696a9bfe48b1ac9e2f7e2caa2 by Ash Blake. Committed on 26/09/2021 at 09:02. Pushed by apol into branch 'master'. tablet: Check if client is supported before sending tool button M +3-0src/input.cpp https://invent.kde.org/plasma/kwin/commit/242de4373706324696a9bfe48b1ac9e2f7e2caa2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439873] Switching users isn't working on Wayland
https://bugs.kde.org/show_bug.cgi?id=439873
--- Comment #13 from Ash Blake ---
And with the crash from the getProp call in KWin::DrmPipeline::setSyncMode,
m_crtc has been a null pointer in at least two backtraces
(gdb) p *m_pipeline
$2 = {
m_output = 0x5592ffd79a3b,
m_gpu = 0x5597a695a010,
m_connector = 0x18,
m_crtc = 0x0,
m_primaryPlane = 0x0,
m_primaryBuffer = {
value = 0x3ff0,
d = 0x3ff0
},
m_oldTestBuffer = {
value = 0x408e,
d = 0x0
},
m_legacyNeedsModeset = false,
m_cursor = {
pos = {
xp = 0,
yp = 1072693248
},
hotspot = {
xp = 0,
yp = 1083047936
},
buffer = {
value = 0x403d,
d = 0x408e0800
},
dirtyBo = false,
dirtyPos = false
},
m_allObjects = {
d = 0x0
},
m_formats = {
d = 0x403d
},
m_lastFlags = 0
}
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 439873] Switching users isn't working on Wayland
https://bugs.kde.org/show_bug.cgi?id=439873
--- Comment #12 from Ash Blake ---
(In reply to Ash Blake from comment #11)
> Created attachment 141939 [details]
The contents of m_gpu look odd - cursor size of 262147x458757, insanely high
file descriptor and some suspicious looking addresses.
It seems like DrmGpu got destroyed, but it still got used somehow.
(gdb) p *m_gpu
$11 = {
...
m_backend = 0x7000700060007,
m_eglBackend = {
wp = {
d = 0x7000600070005,
value = 0x6000700020007
}
},
m_devNode = {
d = 0x3000100020003
},
m_cursorSize = {
wd = 262147,
ht = 458757
},
m_fd = 262145,
m_deviceId = 1970354902204420,
m_atomicModeSetting = 6,
m_useEglStreams = false,
m_gbmDevice = 0x7000100050007,
m_eglDisplay = 0x700070003,
m_presentationClock = 327687,
m_socketNotifier = 0x7000700070007,
m_addFB2ModifiersSupported = 5,
m_planes = {
d = 0x7000100030007
},
m_crtcs = {
d = 0x556bab5abab0
},
m_connectors = {
d = 0x556bab6581b0
},
m_pipelines = {
d = 0x556bab56b5b0
},
m_drmOutputs = {
d = 0x556babd27990
},
m_outputs = {
d = 0x556babe865c0
},
m_leaseOutputs = {
d = 0x7f08040086f0
},
m_leaseDevice = 0x556bab56b330
}
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 439873] Switching users isn't working on Wayland
https://bugs.kde.org/show_bug.cgi?id=439873 --- Comment #16 from Ash Blake --- This crash is also quite unpredictable, sometimes I can switch a lot of times between two sessions with no crash, and sometimes it will crash on the first try. Usually if the crash already occurs in one of the sessions, it will then keep reoccuring whenever switching away from it and back. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439873] Switching users isn't working on Wayland
https://bugs.kde.org/show_bug.cgi?id=439873 --- Comment #15 from Ash Blake --- (In reply to Zamundaaa from comment #14) > Sounds a lot like https://bugs.kde.org/show_bug.cgi?id=442677 It really does, but I already have the commit that fixed that bug in my KWin build. Seems like there's some other problem that causes the same crash on VT switches, and there's also this weird crash in KWin::DrmObject::getProp that happens sometimes too. If I notice crashes in some other places, I'll upload those backtraces too. The getProp crash case is particularly weird. At a quick glance it seems that the crtc in a pipeline could not suddenly end up null under normal circumstances, as there doesn't seem to be a method that changes a DrmPipeline's m_crtc after initialization. Maybe the memory for it was freed and used by something else, but something still used the pointer to the deleted pipeline? I guess a situation like this could cause all kinds of crashes in various places. I'll try setting up breakpoints on destructors of various drm-related objects and keeping track of the objects' addresses to compare them after a crash happens to check if that is the case. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439873] Switching users isn't working on Wayland
https://bugs.kde.org/show_bug.cgi?id=439873 --- Comment #27 from Ash Blake --- (In reply to Zamundaaa from comment #21) > The patch should "fix" that but I'd still like to find the actual source of > the problem. The stability has definitely improved with that patch, but some crashes still happened, way less often than before. Now I also applied the patches from MR 1467 and I can't trigger a crash anymore, and I don't see "DrmGpu::findWorkingCombination failed to find any functional combinations!" anymore in the logs. Looks like these two merge requests resolve this bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438097] [AnimationEffect] kwin_wayland sometimes crashes when xwayland tries to display a popup
https://bugs.kde.org/show_bug.cgi?id=438097 --- Comment #16 from Ash Blake --- Okay, it crashed again. The backtrace looks the same as the last one. The crash is again in kwin4_effect_fade: (gdb) p this $3 = (KWin::ScriptedEffect * const) 0x55f805fa1440 (gdb) set $data_start = (char*)this->m_effectName->d + this->m_effectName->d->offset (gdb) set $len = this->m_effectName->d->size (gdb) set $i = 0 (gdb) while $i < 2*$len >printf "%c", *($data_start + $i) >set $i = $i + 2 >end kwin4_effect_fade I'll test the Glide window open/close animation now, as it's a native one and may behave differently. I suppose there's no point in testing Scale as it's a scripted effect and it will probably have the same problem Fade has. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438097] [AnimationEffect] kwin_wayland sometimes crashes when xwayland tries to display a popup
https://bugs.kde.org/show_bug.cgi?id=438097
--- Comment #15 from Ash Blake ---
Additional information about that EffectWindow, as I forgot it's actually an
instance of EffectWindowImpl and didn't dump members of the latter.
Both the toplevel and sw pointers lead to inaccessible memory addresses.
(gdb) p *(KWin::EffectWindowImpl *)entry.i->key
...
members of KWin::EffectWindowImpl:
static staticMetaObject = {
d = {
superdata = {
direct = 0x7f9fafdb2900
},
stringdata = 0x7f9fb01ae880 ,
data = 0x7f9fb01ae840 ,
static_metacall = 0x7f9faff9e1a0
,
relatedMetaObjects = 0x0,
extradata = 0x0
}
},
toplevel = 0x239043d,
sw = 0x20a0282,
dataMap = {
{
d = 0x239043d,
e = 0x239043d
}
},
managed = false,
waylandClient = false,
x11Client = false
...
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 438097] [AnimationEffect] kwin_wayland sometimes crashes when xwayland tries to display a popup
https://bugs.kde.org/show_bug.cgi?id=438097 Ash Blake changed: What|Removed |Added Version|5.22.1 |5.22.90 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438097] [AnimationEffect] kwin_wayland sometimes crashes when xwayland tries to display a popup
https://bugs.kde.org/show_bug.cgi?id=438097
--- Comment #17 from Ash Blake ---
This time, however, it seems EffectWindow was not completely destroyed.
Unlike in the last crash, the data inside EffectWindow is not complete garbage.
For instance, the addresses in toplevel and EffectWindow::Private pointers look
more sensible, dataMap contains valid pointers to QHashData::shared_null, and
x11Client is true.
(gdb) p *(EffectWindowImpl*)(entry.i->key)
$10 = {
= {
= {},
members of KWin::EffectWindow:
static staticMetaObject = {
...
},
d = {
d = 0x55f806b0fa80
}
},
members of KWin::EffectWindowImpl:
static staticMetaObject = {
...
},
toplevel = 0x55f80706bcf0,
sw = 0x0,
dataMap = {
{
d = 0x7fb16aa6e5c0 ,
e = 0x7fb16aa6e5c0
}
},
managed = true,
waylandClient = false,
x11Client = true
}
Inspection of toplevel:
(gdb) p *(Toplevel*)$ew.toplevel
{
= {},
members of KWin::Toplevel:
static staticMetaObject = {
...
},
m_frameGeometry = {
x1 = 640,
y1 = 547,
x2 = 1030,
y2 = 654
},
m_clientGeometry = {
x1 = 640,
y1 = 547,
x2 = 1030,
y2 = 654
},
m_bufferGeometry = {
x1 = 640,
y1 = 547,
x2 = 1030,
y2 = 654
},
m_visual = 59,
bit_depth = 24,
info = 0x55f806a48670,
ready_for_painting = true,
m_internalFBO = {
value = 0x0,
d = 0x0
},
m_internalImage = ,
m_internalId = {
data1 = 3760014763,
data2 = 36097,
data3 = 19896,
data4 = "\246\035\236h\342\216t\223"
},
m_client = {
m_window = 18875715,
m_destroy = false,
m_logicGeometry = {
x1 = 0,
y1 = 0,
x2 = -1,
y2 = -1
}
},
is_shape = false,
effect_window = 0x0,
m_shadow = 0x0,
resource_name = {
d = 0x55f806b26260
},
resource_class = {
d = 0x55f805f58430
},
m_clientMachine = 0x55f806442ca0,
m_wmClientLeader = 18874376,
opaque_region = {
d = 0x7fb16b3071e0
},
m_shapeRegion = {
d = 0x55f806cc0a30
},
m_shapeRegionIsValid = true,
m_output = 0x55f805b4d020,
m_skipCloseAnimation = false,
m_surfaceId = 0,
m_surface = 0x0,
m_screenScale = 1,
m_opacity = 1,
m_stackingOrder = 5
}
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 438097] [AnimationEffect] kwin_wayland sometimes crashes when xwayland tries to display a popup
https://bugs.kde.org/show_bug.cgi?id=438097 --- Comment #18 from Ash Blake --- I didn't get a crash so far, but I revisited the previous coredump, as it seems weird that the EffectWindow was at least a bit intact this time. Disassembly of the current instruction and the one before it: 0x7fb16c02e4c2 <...postPaintScreenEv+1682> mov(%rdi),%rax > 0x7fb16c02e4c5 <...postPaintScreenEv+1685> call *0x90(%rax) The RDI register contained the address of the EffectWindow, same as in entry.key EffectWindow::addLayerRepaint is virtual, so the address of the actual function EffectWindowImpl::addLayerRepaint has to be read from the vtable. (In this case) the first few bytes of EffectWindow should contain a vtable ptr, which is then read into RAX by 'mov (%rdi),%rax'. The EffectWindowImpl::addLayerRepaint function pointer is then expected to exist at RAX + 0x90. It looks like the vtable pointer points to an invalid location: (gdb) p/x $rax $23 = 0x55f806f2e (gdb) x/x $rax 0x55f806f2e:Cannot access memory at address 0x55f806f2e And vtable+0x90 is also unreadable: (gdb) x/x $rax+0x90 0x55f806fbe:Cannot access memory at address 0x55f806fbe In the coredump from yesterday, the situation is the same: 0x7f9fafd984c2 <...postPaintScreenEv+1682> mov(%rdi),%rax > 0x7f9fafd984c5 <...postPaintScreenEv+1685> call *0x90(%rax) (gdb) p/x $rax $1 = 0x55f06b86305a (gdb) x/x $rax 0x55f06b86305a: Cannot access memory at address 0x55f06b86305a (gdb) x/x $rax+0x90 0x55f06b8630ea: Cannot access memory at address 0x55f06b8630ea Yesterday the EffectWindow was destroyed completely, and the member variables looked pretty much random. In today's crash it seems like the EffectWindow was in the process of getting deleted, as some of the member variables looked intact. The vtable however already got corrupted, which made the call result in a segfault. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438097] [AnimationEffect] kwin_wayland sometimes crashes when xwayland tries to display a popup
https://bugs.kde.org/show_bug.cgi?id=438097 --- Comment #19 from Ash Blake --- Created attachment 141801 --> https://bugs.kde.org/attachment.cgi?id=141801=edit Code completion popup window IDs in the debug console Update: It appears that the crashes are highly correlated with the amount of popup windows opened in total during a session of coding. Each new popup causes an increment in the hexadecimal window ID and the window's caption (win1, win2, win3, etc.) seen in the KWin debug console. For me, the crash happens somewhere around win300. I reproduced the crash three times in a row by typing a name of some object then repeatedly mashing dot and backspace keys, so that the autocompletion popups flash rapidly. Because the window IDs increase so quickly and the problem happens around a similar amount of open popup windows, could this be some sort of overflow problem? Maybe this could explain the weird corruption described in my previous two comments, where some fields of the EffectWindow even looked sensible, but the vtable located at the beginning of memory allocated for the EffectWindow was completely ruined. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438097] [AnimationEffect] kwin_wayland sometimes crashes when xwayland tries to display a popup
https://bugs.kde.org/show_bug.cgi?id=438097 --- Comment #20 from Ash Blake --- This short script can be used to trigger a crash: #!/bin/bash win_id=$(sort <(xdotool search --name "Content window") <(xdotool search --class "jetbrains-idea") | uniq -d) sleep 10 while : do xdotool key --window $win_id period sleep 0.1 xdotool key --window $win_id BackSpace done After opening a project in IDEA and typing something like 'System' in a line, run the script and switch back to the IntelliJ IDEA window. For me, with automated keymashing it takes 420-450 popups to crash the Wayland session. On X11, it's completely stable even though the window identifiers also rapidly increase. I terminated the test after around 1000 popups. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442659] GTK3 Window decoration assets generated by kde-gtk-config are now all blank with Breeze window decoration
https://bugs.kde.org/show_bug.cgi?id=442659 Ash Blake changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/kde-gtk-config/commit/c1 ||0dff60289e8aa7b1989c49280b5 ||5711daaf14e Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #8 from Ash Blake --- Git commit c10dff60289e8aa7b1989c49280b55711daaf14e by Ash Blake. Committed on 02/10/2021 at 17:09. Pushed by ngraham into branch 'master'. kwin_bridge: Load DecorationButton without the "button" keyword Plugin keywords have been deprecated. Breeze and Oxygen no longer use the "button" keyword when registering their button plugins, so loading them now fails and blank assets get generated. Attempt loading DecorationButton without using the keyword, and if this fails, try the deprecated keyword like in the KWin commit 6f110bca. M +12 -2kded/kwin_bridge/dummydecorationbridge.cpp https://invent.kde.org/plasma/kde-gtk-config/commit/c10dff60289e8aa7b1989c49280b55711daaf14e -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439873] Switching users isn't working on Wayland
https://bugs.kde.org/show_bug.cgi?id=439873 Ash Blake changed: What|Removed |Added Attachment #141922|0 |1 is obsolete|| --- Comment #17 from Ash Blake --- Created attachment 141950 --> https://bugs.kde.org/attachment.cgi?id=141950=edit Debugging session with both good and bad VT switches This is an annotated log from the debugging session with backtraces of each pipeline destruction, including the addresses of said pipelines. For convenience, you can also view it with basic formatting here: https://gist.github.com/telepathine/01bd060e5df3ece55f6b46bb63a78078 It features both the successful case and the failed one, which differs quite notably in the pipeline destruction department - one pipeline gets deleted three times, then that address happens to be reused as for some reason some DrmOutput still has it. This leads to a segfault originating from KWin::DrmPipeline::setSyncMode later on. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439873] Switching users isn't working on Wayland
https://bugs.kde.org/show_bug.cgi?id=439873 --- Comment #19 from Ash Blake --- (In reply to Ash Blake from comment #18) > and these multiple deletions may be normal Unfortunately, there is something wrong anyways even though it is not multiple deletion. Right before the crash, a pipeline that was involved in it got created and then deleted exactly three times in a row, so this is the same situation as previously but it turns out the destruction behaviour is actually normal. updateOutputs should not have received a deleted pipeline from findWorkingCombination though, so something is wrong here. Construction: $28 = (KWin::DrmPipeline * const) 0x56548a2aebd0 #0 KWin::DrmPipeline::DrmPipeline(KWin::DrmGpu*, KWin::DrmConnector*, KWin::DrmCrtc*, KWin::DrmPlane*) (this=this@entry=0x56548a2aebd0, gpu=0x565489679430, conn=0x565489e91be0, crtc=crtc@entry=0x5654896e4eb0, primaryPlane=primaryPlane@entry=0x5654896be1b0) at /home/ash/kde/src/kwin/src/plugins/platforms/drm/drm_pipeline.cpp:37 #1 0x7f0549d5e49c in operator()(KWin::DrmCrtc*, KWin::DrmPlane*) const (__closure=__closure@entry=0x7ffe8d5e8660, crtc=0x5654896e4eb0, primaryPlane=0x5654896be1b0) at /home/ash/kde/src/kwin/src/plugins/platforms/drm/drm_gpu.cpp:364 Destruction: $29 = (KWin::DrmPipeline * const) 0x56548a2aebd0 #0 KWin::DrmPipeline::~DrmPipeline() (this=0x56548a2aebd0, __in_chrg=) at /usr/include/c++/11.1.0/bits/atomic_base.h:479 #1 0x7f0549d5e99e in operator()(KWin::DrmCrtc*, KWin::DrmPlane*) const (__closure=__closure@entry=0x7ffe8d5e8660, crtc=, primaryPlane=0x7ffe8d5e85a8) at /home/ash/kde/src/kwin/src/plugins/platforms/drm/drm_gpu.cpp:373 Relevant lines from the segfault backtrace, with yet another exact point of crash: #0 QSharedPointer::deref(QtSharedPointer::ExternalRefCountData*) (dd=0x56540002) at /usr/include/qt/QtCore/qsharedpointer_impl.h:454 #1 QSharedPointer::deref() (this=) at /usr/include/qt/QtCore/qsharedpointer_impl.h:453 #2 QSharedPointer::~QSharedPointer() (this=, __in_chrg=) at /usr/include/qt/QtCore/qsharedpointer_impl.h:310 #3 QSharedPointer::operator=(QSharedPointer const&) (other=, other=..., this=0x56548a2aebf8) at /usr/include/qt/QtCore/qsharedpointer_impl.h:333 #4 KWin::DrmPipeline::present(QSharedPointer const&) (this=0x56548a2aebd0, buffer=...) at /home/ash/kde/src/kwin/src/plugins/platforms/drm/drm_pipeline.cpp:81 #5 0x7f0549d55bb8 in KWin::DrmOutput::present(QSharedPointer const&, QRegion) (this=this@entry=0x565489e97d50, buffer=..., damagedRegion=...) at /home/ash/kde/src/kwin/src/plugins/platforms/drm/drm_output.cpp:394 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439873] Switching users isn't working on Wayland
https://bugs.kde.org/show_bug.cgi?id=439873 --- Comment #18 from Ash Blake --- (In reply to Ash Blake from comment #17) Nevermind, I totally forgot allocation could just happen at the same address after deleting something there and these multiple deletions may be normal. I'll redo it, also tracking construction this time. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439873] Switching users isn't working on Wayland
https://bugs.kde.org/show_bug.cgi?id=439873 --- Comment #22 from Ash Blake --- Created attachment 141955 --> https://bugs.kde.org/attachment.cgi?id=141955=edit KWin DRM log messages (In reply to Zamundaaa from comment #21) > You likely have some lines with something like "Atomic test for > CommitMode::Commit failed! Invalid Argument" and a bunch of numbers below it > in your ~/.local/share/sddm/wayland-session.log when KWin crashes. Could you > have a look at what the exact error messages are? For some reason they weren't in the log anymore, so I just ran in a TTY: $ (QT_LOGGING_RULES="kwin_wayland_drm.*=true" kwin_wayland 2>&1) > kwin_wayland_drm.log Are these fine or should I get logs from the full Plasma session? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439873] Switching users isn't working on Wayland
https://bugs.kde.org/show_bug.cgi?id=439873 --- Comment #23 from Ash Blake --- Created attachment 141956 --> https://bugs.kde.org/attachment.cgi?id=141956=edit KWin DRM log from another machine (AMD GPU) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438097] [AnimationEffect] kwin_wayland sometimes crashes when xwayland tries to display a popup
https://bugs.kde.org/show_bug.cgi?id=438097 --- Comment #27 from Ash Blake --- The file descriptor flood comes from PlasmaWindow::Private::iconChangedCallback (kwayland/src/client/plasmawindowmanagement.cpp:655, master branch). This can be easily verified by catching pipe2 in the plasmashell process - the backtrace will show this function. Occurences of pipe2 in the strace output for plasmashell correlate with the amount of KWin's file descriptors. After calling the org_kde_plasma_window_get_icon interface, the FDs get copied over to KWin's process using Wayland's proxy magic, which seems to be using the sendmsg and recvmsg syscalls with SCM_RIGHTS ancillary messages, which enable passing open descriptors between processes. The function which gets called after marshaling the FDs by the Wayland's proxy thingy is PlasmaWindowInterfacePrivate::org_kde_plasma_window_get_icon (kwayland-server/src/server/plasmawindowmanagement_interface.cpp:437) Things get really odd now. Both of those functions look fine to me - it doesn't look like either the server side or the client side would leave a descriptor open after finishing its work. I walked through both the icon read and write in GDB, and everything was seemingly handled correctly for the cases I observed. Despite no errors, many of these supposedly closed descriptors did still appear in /proc/$KWIN_PID/fd. I have no idea what could be going on. For a test, I replaced org_kde_plasma_window_get_icon with a function that only calls close(fd). Somehow, the KWin process still had rapidly increasing amounts of FDs, even though this time it was just supposed to close them ASAP. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439873] Switching users isn't working on Wayland
https://bugs.kde.org/show_bug.cgi?id=439873 --- Comment #26 from Ash Blake --- Created attachment 141964 --> https://bugs.kde.org/attachment.cgi?id=141964=edit KWin DRM log messages from full Plasma session I got some of these errors in my wayland-session.log now. They're different, all of them are 'permission denied' -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439873] Switching users isn't working on Wayland
https://bugs.kde.org/show_bug.cgi?id=439873 Ash Blake changed: What|Removed |Added CC||telepath...@tutanota.com --- Comment #7 from Ash Blake --- (In reply to Nate Graham from comment #4) > On Wayland, I get to the login screen, but logging into the other user > fails; after I enter the other user's password and click the login button I > get kicked back to the lock screen of my existing session. This works for me, the new user's session starts every time. However, either the old user's session or the new user's session will crash when switching. I have kwin_wayland coredumps from both users and I'll upload the backtraces soon. (In reply to Nate Graham from comment #6) > Maybe the bug is that it didn't succeed in logging *me* into that user? (In reply to Nate Graham from comment #5) > ~/kde/usr/bin/ksmserver It probably failed to log in as the other user because you tried to run the same development KDE session, and the other user wouldn't be able to read and execute anything in your home directory. startplasma-wayland won't run, so the new user will only be running the systemd user daemon and whatever stuff it started. Give konqi execute access to your home directory so he can cd into it, and make him the group of $HOME/kde so he can read and execute things in there: $ setfacl -m u:konqi:x $HOME $ chown -R $USER:konqi $HOME/kde -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439873] Switching users isn't working on Wayland
https://bugs.kde.org/show_bug.cgi?id=439873 --- Comment #8 from Ash Blake --- Created attachment 141922 --> https://bugs.kde.org/attachment.cgi?id=141922=edit Backtrace (git master) The old user's and new user's backtraces look the same. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439873] Switching users isn't working on Wayland
https://bugs.kde.org/show_bug.cgi?id=439873 --- Comment #9 from Ash Blake --- Created attachment 141923 --> https://bugs.kde.org/attachment.cgi?id=141923=edit Screen recording showing the problem -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438097] [AnimationEffect] kwin_wayland sometimes crashes when xwayland tries to display a popup
https://bugs.kde.org/show_bug.cgi?id=438097 --- Comment #23 from Ash Blake --- Created attachment 141807 --> https://bugs.kde.org/attachment.cgi?id=141807=edit Outputs of lsof -p $KWIN_PID taken every second, from the test start to KWin crash Additional logs for #22 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438097] [AnimationEffect] kwin_wayland sometimes crashes when xwayland tries to display a popup
https://bugs.kde.org/show_bug.cgi?id=438097 --- Comment #21 from Ash Blake --- This time KWin didn't crash completely, but entered a weird state. Plasmashell stopped working, but most of the applications were still running, including IDEA. I stopped the test, because if it continued it would most likely result in a crash. It is not possible to restart plasmashell right now, nor launch any new program. These errors appeared in wayland-session.log when plasmashell crashed: file descriptor expected, object (308), message get_icon(7h) error in client communication (pid 496515) QMetaProperty::read: Unable to handle unregistered datatype 'KWin::SessionState' for property 'KWin::EffectsHandlerImpl::sessionState' wl_display@1: error 1: invalid arguments for org_kde_plasma_window@308.get_icon This appeared in terminal when trying to restart plasmashell: wl_display@1: error 1: invalid arguments for wl_shm@81.create_pool The Wayland connection experienced a fatal error: Invalid argument And around the same time, this appeared in wayland-session.log: file descriptor expected, object (81), message create_pool(nhi) error in client communication (pid 498931) QMetaProperty::read: Unable to handle unregistered datatype 'KWin::SessionState' for property 'KWin::EffectsHandlerImpl::sessionState' While typing this message, Firefox and a bunch of other things have crashed. The following got logged to wayland-session.log: file descriptor expected, object (30), message add(hu) error in client communication (pid 499807) wl_display@1: error 1: invalid arguments for zwp_linux_buffer_params...@30.add [266 00:35:02.451499] [glfw error 65544]: Wayland: fatal display error: Invalid argument file descriptor expected, object (30), message add(hu) error in client communication (pid 499827) wl_display@1: error 1: invalid arguments for zwp_linux_buffer_params...@30.add [266 00:35:06.638735] [glfw error 65544]: Wayland: fatal display error: Invalid argument file descriptor expected, object (30), message add(hu) error in client communication (pid 499851) file descriptor expected, object (30), message add(hu) error in client communication (pid 499907) file descriptor expected, object (30), message add(hu) error in client communication (pid 499954) wl_display@1: error 1: invalid arguments for zwp_linux_buffer_params...@30.add [266 00:35:18.863341] [glfw error 65544]: Wayland: fatal display error: Invalid argument file descriptor expected, object (63), message add(hu) error in client communication (pid 499370) file descriptor expected, object (7), message create_pool(nhi) error in client communication (pid 500198) file descriptor expected, object (7), message create_pool(nhi) error in client communication (pid 500233) kwin_core: Could not trust "/usr/bin/plasma-browser-integration-host" sha "" "" This is followed by 6649 repetitions of this line: failed to accept: Too many open files -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438097] [AnimationEffect] kwin_wayland sometimes crashes when xwayland tries to display a popup
https://bugs.kde.org/show_bug.cgi?id=438097 --- Comment #22 from Ash Blake --- Created attachment 141806 --> https://bugs.kde.org/attachment.cgi?id=141806=edit Screencast demonstrating the rising amount of open files by KWin Regarding the previous error about too many open files: This screencast shows the count of open files during the popup window test. It is steadily rising, and does not decrease after stopping the test, nor after quitting IntelliJ IDEA completely. If the test gets stopped at, say, 1000 open fds, after resuming it a crash happens pretty quickly. The screencast ends when KWin crashes, which happens after around 1400 file descriptors get opened. In the following message I will attach a .tar.gz archive containing the output of lsof -p $KWIN_PID taken every second since starting the test. The offending descriptors are mostly pipes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438097] [AnimationEffect] kwin_wayland sometimes crashes when xwayland tries to display a popup
https://bugs.kde.org/show_bug.cgi?id=438097 --- Comment #24 from Ash Blake --- Created attachment 141808 --> https://bugs.kde.org/attachment.cgi?id=141808=edit Timelapse of lsof count, after increasing the open fd limit to 8192 This shows the test running for much longer (5 minutes), after max file descriptors for KWin were increased. It could run for a bit longer as fds were not exhausted yet. The interesting thing is how again plasmashell crashed early. This proves that things just go crazy after the file descriptor limit is exhausted, and there is no direct problem in AnimationEffect. KWin crashes in that place, but the real problem is the file descriptor leak and all kinds of chaotic behaviour it can cause. Are there any logs I can provide to help debug this issue? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438097] [AnimationEffect] kwin_wayland sometimes crashes when xwayland tries to display a popup
https://bugs.kde.org/show_bug.cgi?id=438097 --- Comment #29 from Ash Blake --- Created attachment 141874 --> https://bugs.kde.org/attachment.cgi?id=141874=edit A C program that reproduces the bug I figured out which behaviour of the Jetbrains IDEs causes the bug to occur and I wrote a program that replicates it, so the bug can be reproduced reliably and without the need to install any software. This program will repeatedly create a specified amount of windows, waiting some time before destroying the current window and creating the next one. After that, it will wait a specified amount of time and repeat the whole thing. The amount of windows and the time constants are optional program arguments. The default settings are supposed to replicate a realistic scenario that could happen during the IDE usage. They are as follows: - (arg1) burst size: 2 - (arg2) window lifetime (ms): 16 - (arg3) post-burst wait time (ms): 3000 The short burst length of 2 was motivated by observing the popup windows flicker without any content sometimes, before the actual popup appeared. On my machine, this burst size and window lifetime causes the KWin's file descriptor count to increase by 3 each repetition, same as when a popup is opened normally in a Jetbrains IDE. Of course, if such settings do not cause bug reproduction in your environment, start by increasing the burst size. If the bug still isn't reproduced with a high amount of created windows, start decreasing the window lifetime. Some observations: 1. If the window lifetime is large enough to reliably observe the window's icon appearing on the taskbar, this bug does not occur. On my machine, a window lifetime of 60ms is the minimum one that does not cause KWin's file descriptor amount to notably rise at any point in time, even with a burst size of 9 windows. 2. Window lifetimes less or equal to 4ms will cause KWin to lag, up to the point of a complete freeze (which resolves during the wait time). Of course this is a terribly unrealistic scenario and no application would ever do that, but watch out when testing. Compilation: $ gcc reproduce_438097.c -lX11 -o reproduce_438097 Usage $ ./reproduce_438097 [burst size] [window lifetime] [post-burst wait time] -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438097] [AnimationEffect] kwin_wayland sometimes crashes when xwayland tries to display a popup
https://bugs.kde.org/show_bug.cgi?id=438097 --- Comment #30 from Ash Blake --- > The short burst length of 2 was motivated by observing the popup windows > flicker without any content sometimes, before the actual popup appeared. Post scriptum: in fact, when GDB is attached to plasmashell in non-stop mode and a breakpoint is set in PlasmaWindow::Private::iconChangedCallback with commands specified so that it does not pause execution, for instance: break PlasmaWindow::Private::iconChangedCallback commands silent printf "hello\n" end , we can observe the string "hello" appearing twice when a single popup window appears, and also twice when a single popup disappears, suggesting there was another window that appeared for several miliseconds before getting destroyed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438097] [AnimationEffect] kwin_wayland sometimes crashes when xwayland tries to display a popup
https://bugs.kde.org/show_bug.cgi?id=438097 --- Comment #31 from Ash Blake --- (In reply to Ash Blake from comment #30) > break PlasmaWindow::Private::iconChangedCallback > commands > silent > printf "hello\n" > end Oops, forgot a continue there. break PlasmaWindow::Private::iconChangedCallback commands silent printf "hello\n" cont end -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 457106] New: It's not a man's working hours that is important, it is how he spends his leisure time
https://bugs.kde.org/show_bug.cgi?id=457106 Bug ID: 457106 Summary: It's not a man's working hours that is important, it is how he spends his leisure time Product: Active Window Control Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: zrenf...@gmail.com Reporter: lash5...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- It's not a man's working hours that is important, it is how he spends his leisure time -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 457106] It's not a man's working hours that is important, it is how he spends his leisure time
https://bugs.kde.org/show_bug.cgi?id=457106 Ash Lee changed: What|Removed |Added URL||https://bjusew31.xyz/ -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 368584] The main layer in PDF not seen
https://bugs.kde.org/show_bug.cgi?id=368584 --- Comment #2 from Ash <ashz...@yahoo.com> --- Thank you; I have just posted it there — https://bugs.freedesktop.org/show_bug.cgi?id=97768 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 368584] New: The main layer in PDF not seen
https://bugs.kde.org/show_bug.cgi?id=368584 Bug ID: 368584 Summary: The main layer in PDF not seen Product: okular Version: unspecified Platform: unspecified URL: https://dl.dropboxusercontent.com/u/58231097/189.pdf OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: ashz...@yahoo.com Archive.org generates PDFs which have layers. Some are not seen in Okular. I attach a PDF you cannot read in Okular, but it looks fine in any browser plugin or other PDF viewer. Here is a sample PDF: https://dl.dropboxusercontent.com/u/58231097/189.pdf Reproducible: Always Steps to Reproduce: 1. Download the PDF: https://dl.dropboxusercontent.com/u/58231097/189.pdf 2. Open it in Okular 3. Open it in anything else reading PDFs Actual Results: I cannot read the text layer of the PDF in Okular Expected Results: The text layer should be readable, like in any other PDF viewer. Best wishes to KDE and Okular! -- You are receiving this mail because: You are watching all bug changes.
