| Summary: | Crash in QHttp2Connection::handleDATA | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | alessandrodimartino3 |
| Component: | generic-crash | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED DOWNSTREAM | ||
| Severity: | crash | CC: | arojas, kde, sitter, stephen.greenham, valshin.ruslan, yannsel |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 6.4.2 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | https://crash-reports.kde.org/organizations/kde/issues/214127/events/3c9e150e94014dae8eab09fca96a24ec/ | ||
| Attachments: |
New crash information added by DrKonqi
console log with env variable as requested log with all qt logging enabled reduced log |
||
|
Description
alessandrodimartino3
2025-07-10 08:45:37 UTC
Created attachment 183119 [details]
New crash information added by DrKonqi
DrKonqi auto-attaching complete backtrace.
I am curious how this folder came to be > "/home/alex/.local/share/flatpak/exports/share/plasma/desktoptheme/default/translucent/" flatpak doesn't export desktopthemes as far as I know Oo Can you also upload the folder to the bug report please. Secondly you'll probably need to enable debug logging by opening a terminal and then running > QT_LOGGING_RULES=qt.network.*=true plasmashell --replace this will restart plasma from the terminal and hopefully spit out some debug info for the relevant functions. Then try to trigger the crash and attach the output from the terminal here. Created attachment 183121 [details]
console log with env variable as requested
There is no plasma folder in flatpak exports, not sure why that is referenced there as i don't think i've used a flatpak that explicitly interacts with plasma themes That was less useful than expected :(
Let's try with the massive debug option:
> QT_LOGGING_RULES=*=true plasmashell --replace
Created attachment 183124 [details]
log with all qt logging enabled
The log is massive of course so i only included the last 1000 or so lines, let me know if i should include more
Still not very enlightening. Let's shrink the log volume a bit again. > QT_LOGGING_RULES="*=true;qt.quick*=false;qt.scenegraph*=false;qt.gui*=false;qt.qml*=false;qt.accessibility*=false;qt.qpa*=false;qt.pointer*=false;qt.rhi*=false" plasmashell --replace --no-respawn It may also be good to run plasma underneath valgrind and see what that has to say: > valgrind plasmashell --replace --no-respawn Please also try to rename ~/.cache to something else so we can exclude cache problems. Created attachment 183125 [details]
reduced log
Here is the full log, took a while for the crash to happen but it still did even after renaming the cache folder. Running valgrind is taking a while, will add that too when it's done
*** Bug 506858 has been marked as a duplicate of this bug. *** *** Bug 506865 has been marked as a duplicate of this bug. *** Fixed in qt6-base 6.9.1-4 *** Bug 506869 has been marked as a duplicate of this bug. *** |