[kwin] [Bug 490915] New: kwin_wayland crashed with SIGSEV in KWin::EffectWindow::isNormalWindow
https://bugs.kde.org/show_bug.cgi?id=490915 Bug ID: 490915 Summary: kwin_wayland crashed with SIGSEV in KWin::EffectWindow::isNormalWindow Classification: Plasma Product: kwin Version: 6.1.3 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-crash Assignee: kwin-bugs-n...@kde.org Reporter: trilader+kdeb...@gmail.com Target Milestone: --- Created attachment 172063 --> https://bugs.kde.org/attachment.cgi?id=172063=edit kwin_wayland stacktrace crashing in KWin::EffectWindow::isNormalWindow SUMMARY As the title suggests, kwin_wayland crashed. I think I was interacting with an XWayland application (possibly git gui) when it crashed. This is the first time I've seen this crash and it hasn't happened since then (which was on Friday 2024-07-26). SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.9.10-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 7950X3D 16-Core Processor Memory: 62,0 GiB of RAM Graphics Processor: AMD Radeon RX 5500 XT Manufacturer: ASUS ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 469458] kioslave5 crashes in parseMP4Tag when displaying m4a files in Dolphin
https://bugs.kde.org/show_bug.cgi?id=469458 --- Comment #7 from Daniel Schulte --- I'm pretty sure I found the issue. At least on my machine it doesn't happen anymore with the fix and before I could reproduce it every time I opened my ~/music folder in Dolphin. I've created a merge request for the fix at https://invent.kde.org/network/kio-extras/-/merge_requests/281 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 469458] kioslave5 crashes in parseMP4Tag when displaying m4a files in Dolphin
https://bugs.kde.org/show_bug.cgi?id=469458 --- Comment #6 from Daniel Schulte --- For me it still crashes with 5.107.0 on ArchLinux. Except only on the music library now. The crash with the file open dialog showing my home directory seem resolved (or I moved/deleted the offending file thee, not sure about which). Current system information: Operating System: Arch Linux KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 6.4.1-arch2-1 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Xeon® CPU E3-1245 v5 @ 3.50GHz Memory: 31,1 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series Manufacturer: Supermicro Product Name: Super Server System Version: 0123456789 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 469458] kioslave5 crashes in parseMP4Tag when displaying m4a files in Dolphin
https://bugs.kde.org/show_bug.cgi?id=469458 --- Comment #5 from Daniel Schulte --- Created attachment 160086 --> https://bugs.kde.org/attachment.cgi?id=160086=edit Crash report from kioslave5 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 469458] kioslave5 crashes in parseMP4Tag when displaying m4a files in Dolphin
https://bugs.kde.org/show_bug.cgi?id=469458
Daniel Schulte changed:
What|Removed |Added
CC||trilader+kdeb...@gmail.com
--- Comment #2 from Daniel Schulte ---
I also have this issue (on ArchLinux). The following is the report generated by
Dr.Konqi while running version 5.106.
kioslave5 crashes when opening a folder containing my music library in Dolphin,
or when opening my home folder in Kates "Open File" dialog. Interestingly it is
not crashing when opening my home folder in Dolphin. File previews are enabled
(and it doesn't crash with them disabled). The file in question in both cases
is an ext4 filesystem, on an internal SSD drive for my home and on a normal HDD
for my music library.
I tried to convince gdb to give me the name of the failing file by following
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/Debugging_IOSlaves
and attaching to the thumbnail kio process but I've not had any luck as the
types are incomplete (I think some TagLib stuff was optimized out too much or
the ArchLinux debug information aren't complete enough).
```
Application: kioslave5 (kioslave5), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7f557419e514 in () at /usr/lib/libtag.so.1
#7 0x7f557419f436 in TagLib::MP4::Atoms::find(char const*, char const*,
char const*, char const*) () at /usr/lib/libtag.so.1
#8 0x7f557419f4e2 in TagLib::MP4::File::hasMP4Tag() const () at
/usr/lib/libtag.so.1
#9 0x7f55837940ca in parseMP4Tag (file=...) at
/usr/src/debug/kio-extras/kio-extras-23.04.1/thumbnail/audiocreator.cpp:101
#10 AudioCreator::create(KIO::ThumbnailRequest const&)
(this=this@entry=0x55f37e5054a0, request=...) at
/usr/src/debug/kio-extras/kio-extras-23.04.1/thumbnail/audiocreator.cpp:179
#11 0x7f558f6348c9 in
ThumbnailProtocol::createThumbnail(ThumbCreatorWithMetadata*, QString const&,
int, int, QImage&) (this=this@entry=0x7ffccde07f50,
thumbCreator=thumbCreator@entry=0x55f37e5053c0, filePath=..., width=128,
height=height@entry=128, thumbnail=...) at
/usr/src/debug/kio-extras/kio-extras-23.04.1/thumbnail/thumbnail.cpp:851
#12 0x7f558f63a5d5 in ThumbnailProtocol::get(QUrl const&)
(this=0x7ffccde07f50, url=) at
/usr/src/debug/kio-extras/kio-extras-23.04.1/thumbnail/thumbnail.cpp:256
#13 0x7f558f508a64 in KIO::WorkerSlaveBaseBridge::get(QUrl const&)
(this=0x55f37e4f4c40, url=) at
/usr/src/debug/kio/kio-5.106.0/src/core/workerbase_p.h:71
#14 0x7f558f505156 in KIO::SlaveBase::dispatch(int, QByteArray const&)
(this=0x55f37e4f4c40, command=67, data=...) at
/usr/src/debug/kio/kio-5.106.0/src/core/slavebase.cpp:1257
#15 0x7f558f4fd2ae in KIO::SlaveBase::dispatchLoop() (this=0x55f37e4f4c40)
at /usr/src/debug/kio/kio-5.106.0/src/core/slavebase.cpp:342
#16 0x7f558f6362c2 in kdemain(int, char**) (argc=,
argv=) at
/usr/src/debug/kio-extras/kio-extras-23.04.1/thumbnail/thumbnail.cpp:121
#17 0x55f37d84b1fd in main(int, char**) (argc=5, argv=0x7ffccde08b98) at
/usr/src/debug/kio/kio-5.106.0/src/kioslave/kioslave.cpp:145
[Inferior 1 (process 7388) detached]
```
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))
https://bugs.kde.org/show_bug.cgi?id=461316 --- Comment #36 from Daniel Schulte --- (In reply to Silvan Calarco from comment #34) > I also used to have the problems reported by Daniel but in my case it seems > they stopped happening since Qt update to 5.15.7 (with KDE patches applied > to qtbase and qtdeclarative modules). > Currently I didn't have any issues at all in the last 5 days on two > computers (with Intel and AMD/ATI chipsets) where they happened once every > 1-2 days. I also run many times Oleg's reproducer without any issue. It may > just be a coincidence, BTW I also updated Mesa to 22.2.3 and KDE Plasma to > 5.26.3, are you all using such releases? I'm running these version except that all the Qt Packages have the KDE patches, as that is what ArchLinux ships at the moment. For me the v3 reproducer works. I'm, thinking of putting a check in there to see if KWin is still alive before sending the next notification and quit if not. Maybe it's somewhat consistent how many notifications it takes for KWin to crash. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))
https://bugs.kde.org/show_bug.cgi?id=461316 --- Comment #33 from Daniel Schulte --- Not sure how much of this is just a coincidence or if it is actually related: Before I had the "KWin just quits" issue I had problems where KWin sometimes just "forgot to update a window", meaning a window starts flickering between some old window states instead of rendering new ones. The issue was "fixable" by toggling compositing off and on again (using Ctrl+Shift+F12 by default I think). I had that issue for a few years but never really investigated as just pressing the keys was an easy work around for me. How often this happened varied from once every few days to multiple times an hour, though subjectively it was occurring more often lately than a year ago. At the beginning of November I changed my default browser from Chrome to Firefox and that issue didn't happen anymore for a few days so I thought maybe it was a wired interaction between Chrome and KWin. Then this issue started happening. What both issues/behaviors have in common is that I noticed that usually there are notifications being shown when it happens. The "old issue" with stuck rendering showed the notifications just fine and also still updated a small (maybe 30 px?) region around the notification popup. With this issue I saw a notification pop up appear as a black rectangle and then KWin crashing (and sometimes also Plasmashell hanging after the KWin restart). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))
https://bugs.kde.org/show_bug.cgi?id=461316 Daniel Schulte changed: What|Removed |Added CC||trilader+kdeb...@gmail.com --- Comment #7 from Daniel Schulte --- I also have encountered this (quite a lot) in the last days (since I updated to 5.26.x). Sometimes I need to `kwin_x11 --replace` multiple times a day - sometimes I also then need to `pkill plasmashell && kstart5 plasmashell` as it becomes non-responsive. Messages I've seen so far: The X11 connection broke: I/O error (code 1) X connection to :0 broken (explicit kill or server shutdown) The X11 connection broke: I/O error (code 1) XIO: fatal IO error 22 (Invalid argument) on X server ":0" after 171015 requests (171015 known processed) with 0 events remaining. The X11 connection broke: I/O error (code 1) XIO: fatal IO error 2 (No such file or directory) on X server ":0" after 78026 requests (78026 known processed) with 0 events remaining. There are more which I don't have anything saved for as they are from re-running kwin_x11 from a terminal. There isn't anything interesting in dmesg or Xorg.0.log. System information: Operating System: Arch Linux KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.7 Kernel Version: 6.0.6-arch1-1 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Xeon® CPU E3-1245 v5 @ 3.50GHz Memory: 31,1 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series Manufacturer: Supermicro Product Name: Super Server System Version: 0123456789 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 442492] X11: Konsole resizes the window to default size when minimizing/restoring the window
https://bugs.kde.org/show_bug.cgi?id=442492 --- Comment #2 from Daniel Schulte --- I'm not sure this really is a duplicate. I just closed all konsole processes and then deleted ~/.config/konsolerc and this issue still happens when I started konsole again. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 442492] New: X11: Konsole resizes the window to default size when minimizing/restoring the window
https://bugs.kde.org/show_bug.cgi?id=442492 Bug ID: 442492 Summary: X11: Konsole resizes the window to default size when minimizing/restoring the window Product: konsole Version: 21.08.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: trilader+kdeb...@gmail.com Target Milestone: --- SUMMARY Minimizing/Restoring a Konsole window on X11 resets the window size to the initial size even though it shouldn't. In a previous version (whatever was before 2021.08.) this wasn't the case. This doesn't happen if the option "Remember window size" is set, which I don't have as I like new windows to always have the same size. STEPS TO REPRODUCE 1. Use Konsole on X11 with the "Remember window size" unchecked. Resize the window to a size different from the initial size set in the profile (in my case 80x24), e.g., 100x50. 2. Minimize the window (either via the task manager in the panel or the minimize button on the window). 3. Restore the window (via the task manager). OBSERVED RESULT The window gets restored and resizes to the default size. While doing that it shows the "Size: 80x25" resize notification. EXPECTED RESULT The window stays at the size it was before it was minimized. In this case 100x50. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 425433] New: HTML Preview is slow (for some messages)
https://bugs.kde.org/show_bug.cgi?id=425433 Bug ID: 425433 Summary: HTML Preview is slow (for some messages) Product: kmail2 Version: 5.15.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: trilader+kdeb...@gmail.com Target Milestone: --- SUMMARY For some messages rendering the HTML preview is slow. After selecting the message it takes about 2.2 seconds (measured with stopwatch) before the message content is visible. If switching between messages the old message content is displayed while the message list already shows the new message as selected. For some messages it's faster but still takes around a second. The same message in Thunderbird load with no noticeable delay. STEPS TO REPRODUCE 1. Open/switch to a message from a sender which is set to display as HTML by default 2. Wait.. 3. See that it took some time to display it. OBSERVED RESULT Rendering the HTML message is slow. EXPECTED RESULT It should be fast :-) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION I can supply messages to test with. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365246] windows in Icon-only Task manager and Task manager won't show in the right screens
https://bugs.kde.org/show_bug.cgi?id=365246 Daniel Schulte <trilader+kdeb...@gmail.com> changed: What|Removed |Added CC||trilader+kdeb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361159] Problems with audio playback when mouse cursor is on second screen
https://bugs.kde.org/show_bug.cgi?id=361159 Daniel Schulte <trilader+kdeb...@gmail.com> changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #2 from Daniel Schulte <trilader+kdeb...@gmail.com> --- I was able to fix the issue a while ago and just remembered about this bug report. Turns out KDE had nothing to do with it. It was an issue with the xorg-video-intel driver and my system. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 361066] [Feature Request] GTK+ 3.20 support
https://bugs.kde.org/show_bug.cgi?id=361066 Daniel Schulte <trilader+kdeb...@gmail.com> changed: What|Removed |Added CC||trilader+kdeb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361159] Problems with audio playback when mouse cursor is on second screen
https://bugs.kde.org/show_bug.cgi?id=361159 --- Comment #1 from Daniel Schulte <trilader+kdeb...@gmail.com> --- I have found a way to reproduce this on my system. 1. Move mouse cursor to second monitor 2. Executre "xset dpms force standby" 3. Wake the monitors up by wiggling the mouse a bit. 4. Audio problems start happening. To fix it repeat 1-3 on the primary monitor. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361159] New: Problems with audio playback when mouse cursor is on second screen
https://bugs.kde.org/show_bug.cgi?id=361159 Bug ID: 361159 Summary: Problems with audio playback when mouse cursor is on second screen Product: plasmashell Version: 5.6.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: trilader+kdeb...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org When I move the mouse cursor to my second screen (on the right of the primary one) or near the edge of the primary monitor any currently running audio playback gets "stuttery". That is there are some clicks and distortions. When near the screen edge or on the second screen plasmashells virtual memory usage cycles between 200MB and 10GB. I think the audio problems could be caused by the allocation and subsequent freeing of a large-ish ammout of virtual memory in a short time Reproducible: Always Steps to Reproduce: I don't really know how to reproduce this. What I noticed is, that this bug occurs after the screens were switched off for a while. It is fixed by relogging or rebooting. Distribution: Arch Plasma: 5.6.0 KDE-Applications: 5.20.0 Kernel: 4.5.0 Pulseaudio: 8.0 Sound Card: Intel HD Audio widh ACL888-VD codec Graphics Card: Intel HD Graphics P530 CPU: Intel Skylake Xeon E31245v5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356937] Xembed icons have black background
https://bugs.kde.org/show_bug.cgi?id=356937 Daniel Schulte <trilader+kdeb...@gmail.com> changed: What|Removed |Added CC||trilader+kdeb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355463] xembedsniproxy always crash when login
https://bugs.kde.org/show_bug.cgi?id=355463 Daniel Schulte <trilader+kdeb...@gmail.com> changed: What|Removed |Added CC||trilader+kdeb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
