[kdenlive] [Bug 455834] Kdenlive 22.04.2 crashes on trying to load recent project
https://bugs.kde.org/show_bug.cgi?id=455834 --- Comment #6 from Murdo Maclachlan --- Apologies for not getting back on this sooner. I'm currently on version 23.08.4 and haven't experienced this crash for some time. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 455834] Kdenlive 22.04.2 crashes on trying to load recent project
https://bugs.kde.org/show_bug.cgi?id=455834 Murdo Maclachlan changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Murdo Maclachlan --- (In reply to farid from comment #1) > Are you still experiencing this? Hard to say (and sorry for being late to get back on this) - as in the original bug report, it's difficult to reproduce, and I don't use kdenlive *all that* often. I did manage to produce a crash today from attempting the same scenario that caused it before, but the UI was hanging a bit as the project was loaded, so I can't say if it was definitely the same crash or not, especially since the crash reporter couldn't generate a traceback for it. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 455834] New: Kdenlive 22.04.2 crashes on trying to load recent project
https://bugs.kde.org/show_bug.cgi?id=455834
Bug ID: 455834
Summary: Kdenlive 22.04.2 crashes on trying to load recent
project
Product: kdenlive
Version: 22.04.2
Platform: Slackware Packages
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: Video Display & Export
Assignee: j...@kdenlive.org
Reporter: murdomaclach...@duck.com
Target Milestone: ---
Created attachment 150084
--> https://bugs.kde.org/attachment.cgi?id=150084=edit
The crash log as generated by the auto bug reporter
SUMMARY
I opened Kdenlive and went into the recent projects menu under "File". The
program had automatically loaded my most recent project, but I wanted to load
the least recent of those in the recent projects menu. Upon selecting that
project, Kdenlive immediately crashed.
I think the automatically-loaded project might still have been loading a few
clips when I tried to load the older one. Upon retrying, I successfully loaded
the older project and also noted it had a modified clip, if that's relevant.
After a few tries, I was unable to reproduce the crash.
STEPS TO REPRODUCE
1. Load Kdenlive, with the most recent project automatically opened
2. Try to load a different project from the recent projects menu (possibly
specifically the oldest one there)
However, I was unable to reproduce this. If it has to do with the other project
still loading clips, as I suspect it might, one may have to navigate the menu
very quickly to reproduce it.
OBSERVED RESULT
Kdenlive crashes instantly.
EXPECTED RESULT
The older project is loaded.
SOFTWARE/OS VERSIONS
Linux: 5.18.5 (x86_64)
Distrobution: Slackware 15.0 (post 15.0 -current)
KDE Plasma Version: 5.25.1
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.4
ADDITIONAL INFORMATION
A couple of side notes:
The auto bug reporter failed to submit the bug report with the following error
response:
{
"code" : 1000,
"documentation" : "https://bugzilla.readthedocs.org/en/5.0/api/;,
"error" : true,
"message" : "You may not search, or create saved searches, without any
search terms."
}
It also automatically detected my windowing system as X11 even though I'm
running Plasma Wayland.
--
You are receiving this mail because:
You are watching all bug changes.
[Spectacle] [Bug 432260] Spectacle fails to create rectangular and active window screenshots on Wayland with multiple screens
https://bugs.kde.org/show_bug.cgi?id=432260 Murdo Maclachlan changed: What|Removed |Added CC||murdomaclach...@duck.com --- Comment #33 from Murdo Maclachlan --- I noticed this bug is marked resolved, however I still get this issue on Wayland with Plasma 5.25 (Slackware Current). The workaround "QT_QPA_PLATFORM=wayland spectacle" does work for me (interestingly, "spectacle -platform 'wayland;xcb'" did not work), but a workaround isn't a fix. Additionally, when running with the workaround in console, the output gives the following complaint: "qt.qpa.wayland: Wayland does not support QWindow::requestActivate()". I don't know enough about Wayland or Qt to know if that's related, though. -- You are receiving this mail because: You are watching all bug changes.
