Hi Hans,
Thanks for reporting this and including the terminal output — that's
very helpful. I can see krita ran through its database migration phase
before being terminated with "Killed krita" at the end.
There's an important detail to clarify: your bug title says "krita hangs
on start," but the actual symptom in the output is "Killed krita." A
hang means the app stays open but frozen; Killed means the system
terminated it (most commonly by the OOM killer when memory is
exhausted). These are fundamentally different issues.
To help narrow this down, could you please run the following and paste
the output:
1. Check if this was an OOM kill:
dmesg | grep -i "kill\|oom\|out of memory" | tail -20
If that returns nothing, also try:
dmesg -T | grep -i "krita" | tail -10
2. Check your current memory state:
free -h
3. Try running krita again with verbose output to confirm whether it
hangs or gets killed each time:
krita 2>&1 | tee /tmp/krita-output.txt; echo "Exit code: $?"
4. Also let us know:
- How much free RAM you had at the time (from output #2)
- Whether krita ever shows its window before disappearing, or disappears
immediately
- Whether this happens consistently on every launch, or was a one-time
occurrence
This will tell us whether we're looking at a memory pressure issue, a
genuine hang, or something else entirely.
Thanks for your help!
** Changed in: krita (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to krita in Ubuntu.
https://bugs.launchpad.net/bugs/2149899
Title:
krita hangs on start
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krita/+bug/2149899/+subscriptions
--
kubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
