[plasma-browser-integration] [Bug 488653] plasma-browser-integration-host crashes in Firefox 127.0 after upgrade to Plasma 6.1
https://bugs.kde.org/show_bug.cgi?id=488653 --- Comment #45 from Alexander Kowalski --- (In reply to Fabian Vogt from comment #44) > (In reply to Bug Janitor Service from comment #43) > > A possibly relevant merge request was started @ > > https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/4697 > > Can you try ^? No errors with sanitizers and no crashes with 'standard' build options either so far. For all I can tell as someone with no experience with this codebase at all going just by what I have seen so far it also seems like a reasonable solution for at least this bug. If something does come up after all I will report back, but I hope that won't be necessary. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 488653] plasma-browser-integration-host crashes in Firefox 127.0 after upgrade to Plasma 6.1
https://bugs.kde.org/show_bug.cgi?id=488653 --- Comment #41 from Alexander Kowalski --- Created attachment 173651 --> https://bugs.kde.org/attachment.cgi?id=173651&action=edit AddressSanitizer error message (In reply to Fabian Vogt from comment #40) > (In reply to Alexander Kowalski from comment #39) > > Created attachment 173213 [details] > > AddressSanitizer error message > > > > I recompiled plasma-workspace and plasma-browser-integration with debug > > information and sanitizers enabled and was able to get this error message > > for a heap-use-after-free. > > https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/4586 might > fix this, can you try with that applied? Unfortunately the only difference I see is that the line numbers have shifted a little bit due to application of the merge request. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 488653] plasma-browser-integration-host crashes in Firefox 127.0 after upgrade to Plasma 6.1
https://bugs.kde.org/show_bug.cgi?id=488653 --- Comment #39 from Alexander Kowalski --- Created attachment 173213 --> https://bugs.kde.org/attachment.cgi?id=173213&action=edit AddressSanitizer error message I recompiled plasma-workspace and plasma-browser-integration with debug information and sanitizers enabled and was able to get this error message for a heap-use-after-free. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 488653] plasma-browser-integration-host crashes in Firefox 127.0 after upgrade to Plasma 6.1
https://bugs.kde.org/show_bug.cgi?id=488653 --- Comment #38 from Alexander Kowalski --- Created attachment 173198 --> https://bugs.kde.org/attachment.cgi?id=173198&action=edit New distinct possibly related backtrace I have a new backtrace that looks different from the previous ones and seems like it could be related. For some reason the date and time written into the file name is two days ago although I opened it from a notification I got about an hour ago, so if that time is correct I have no idea if anything specific happened at the same time. (When I got the notification, Firefox was not even running or starting, I was just updating packages.) -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 488653] plasma-browser-integration-host crashes in Firefox 127.0 after upgrade to Plasma 6.1
https://bugs.kde.org/show_bug.cgi?id=488653 --- Comment #36 from Alexander Kowalski --- (In reply to Fabian Vogt from comment #30) > (In reply to Lassi Väätämöinen from comment #29) > > (In reply to Lassi Väätämöinen from comment #28) > > > > > Tried it, but the issue did not reproduce after Firefox restart... of > > > course. > > > > > > Not sure if this is of any relevance, I saw the first crash when I had > > > issues with Nextcloud sync in the Nextcloud desktop app. > > > > > > Now not happening anymore since 15:00 today. > > Got 306 coredumps before that, but not reproduced during Valgrind debugging. > > That actually confirms even more that it's cause by the waylandtasksmodel, > as that is by default not accessible when using valgrind due to kwin access > controls. To disable those, kwin_wayland needs to be started with > KWIN_WAYLAND_NO_PERMISSION_CHECKS=1. > You can add that to /etc/environment or > > cat < >/run/user/1000/systemd/user/plasma-kwin_wayland.service.d/override.conf > [Service] > Environment=KWIN_WAYLAND_NO_PERMISSION_CHECKS=1 > EOF > > and log out and in again. Is it possible that there are other interfering factors? I tried running it under valgrind with the environment variable set for kwin_wayland but it still won't crash like that while relatively consistently crashing otherwise. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 488653] plasma-browser-integration-host crashes in Firefox 127.0 after upgrade to Plasma 6.1
https://bugs.kde.org/show_bug.cgi?id=488653 Alexander Kowalski changed: What|Removed |Added CC||alexander.kowalski@mailbox. ||org --- Comment #7 from Alexander Kowalski --- Created attachment 171190 --> https://bugs.kde.org/attachment.cgi?id=171190&action=edit Another traceback for this crash or a similar one with Plasma 6.1.1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 416690] Why move to deleted folder? on mount directory.
https://bugs.kde.org/show_bug.cgi?id=416690 Alexander Kowalski changed: What|Removed |Added CC||alexander.kowalski@mailbox. ||org --- Comment #7 from Alexander Kowalski --- Created attachment 148270 --> https://bugs.kde.org/attachment.cgi?id=148270&action=edit Screen recording I just noticed the recent activity here (compared to my comment on bug 391380 at least) and while I am still not absolutely sure that this is a duplicate of that one, the description in the new comments sounds very much like that to me, I can still reproduce this issue reliably using the latest version and I also found out what the cause was back then, just no easy and reliable fix (see comment there). I made a recording of encountering the issue, the only time-critical step is changing between the views fast enough that the terminal does not keep up (this does not require split views, happens with other navigation too). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 391380] Folder change not always in sync with terminal component
https://bugs.kde.org/show_bug.cgi?id=391380 Alexander Kowalski changed: What|Removed |Added CC||alexan...@kowalski.pw --- Comment #5 from Alexander Kowalski --- This bug has a side effect that regularly happens to me and has been annoying me for years: When I leave a directory, let's call it "dir", but the working directory of the shell does not change and I then delete the directory, that will be interpreted as a directory change to "dir (deleted)" in the terminal and that will sync, so the directory view navigates to "dir (deleted)" showing no contents and an error message that the directory does not exist. I am not sure how I manage to trigger this as often as I do, but I assume it is because I probably often have the directory and its parent directory both open in a split view and then at some point while working in the parent directory when I want to delete the directory I quickly change to its view to close it and that makes the shell go in there, but the closing follows too quickly to make it leave again. I took some time to debug this issue and it seems to occur because there is a significant (about 0.5 to 1 s on my system I would guess) delay between the call to `sendCdToTerminal` that sends the cd command to the shell and the execution of the slot `slotKonsolePartCurrentDirectoryChanged` which is caused by the shell changing its directory (all references are to src/panels/terminal/terminalpanel.cpp of the code currently on the git master branch). This can at least partially be fixed by not doing the check for `dir == m_konsolePartCurrentDirectory` at the beginning of `sendCdToTerminal` and instead always sending the cd command because `m_konsolePartCurrentDirectory` is incorrect if the slot has not yet been executed after the previous call. However, as far as I can tell, when quickly navigating between directories how often and when exactly the slot is called is somewhat unreliable and with this change only, some entries might be left in `m_sendCdToTerminalHistory`. If you then change to one of those directories in the terminal, the directory view does not follow. It would be quite nice if someone could at least fix this sufficiently that what I described in the first paragraph does not happen any more, but I can not see an easy way to make it work correctly under all circumstances right now. (But I also have absolutely no experience working on dolphin or any KDE software for that matter.) Also, it seems to me that bug 421337 is a duplicate of this bug and possibly bug 416690 as well, although I am not so sure about that one. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404292] Digital clock settings option for toggling between 12 and 24 hour clock format is broken
https://bugs.kde.org/show_bug.cgi?id=404292 Alexander Kowalski changed: What|Removed |Added CC||alexan...@kowalski.pw --- Comment #4 from Alexander Kowalski --- *** Bug 404413 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404413] 'Use 24-hour Clock' option now ineffective in Digital Clock plasmoid
https://bugs.kde.org/show_bug.cgi?id=404413 Alexander Kowalski changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Alexander Kowalski --- *** This bug has been marked as a duplicate of bug 404292 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404413] New: 'Use 24-hour Clock' option now ineffective in Digital Clock plasmoid
https://bugs.kde.org/show_bug.cgi?id=404413 Bug ID: 404413 Summary: 'Use 24-hour Clock' option now ineffective in Digital Clock plasmoid Product: plasmashell Version: 5.15.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: alexan...@kowalski.pw Target Milestone: 1.0 SUMMARY Since updating to 5.15.0, the 'Use 24-hour Clock' option in the Digital Clock plasmoid's settings does not work anymore and the clock always shows 12h format in en_US locale. STEPS TO REPRODUCE 1. Choose locale with 12h format. 2. Open settings of Digital Clock plasmoid 3. Check the 'Use 24-hour Clock' checkbox and apply settings OBSERVED RESULT The time is shown in 12h AM/PM format. EXPECTED RESULT The time is shown in 24h format. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.15.0 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.1 ADDITIONAL INFORMATION This is a regression from the last stable release. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 393404] New: Brightness can not be restored automatically if user activity resumes too soon after dimming
https://bugs.kde.org/show_bug.cgi?id=393404 Bug ID: 393404 Summary: Brightness can not be restored automatically if user activity resumes too soon after dimming Product: Powerdevil Version: 5.12.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: alexan...@kowalski.pw Target Milestone: --- When I move my mouse immediately after noticing that my laptop screen went black, it stays black, even if I keep moving it or move it again slightly later. Only if I wait for a short time (< 5s) first, the screen brightness is restored correctly. This is perfectly reproducible every time (as long as I react quickly enough). This is possibly a bug in kidletime, but I do not know enough about either to tell for certain. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 297390] When wide characters appear on a line, Konsole cuts off half a letter
https://bugs.kde.org/show_bug.cgi?id=297390 Alexander Kowalski changed: What|Removed |Added CC|alexan...@kowalski.pw | -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 343369] Menu in QtQuickControls Combo Box on Breeze Dark Theme Unreadable
https://bugs.kde.org/show_bug.cgi?id=343369 Alexander Kowalski changed: What|Removed |Added CC|alexan...@kowalski.pw | -- You are receiving this mail because: You are watching all bug changes.
