Bug 475680 - Crash in my HuaWei Tablet
Summary: Crash in my HuaWei Tablet
Status: RESOLVED DUPLICATE of bug 472705
Alias: None
Product: krita
Classification: Applications
Component: Tablets (tablet issues are only very rarely bugs in Krita!) (show other bugs)
Version: 5.2.0
Platform: Other Android 12.x
: NOR crash
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-10-16 06:23 UTC by 2622805406
Modified: 2023-10-27 13:31 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Crash when change colors and other operations can also make krita crash (3.01 MB, video/mp4)
2023-10-16 06:23 UTC, 2622805406 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description 2622805406 2023-10-16 06:23:59 UTC 
Created attachment 162342 [details]
Crash when change colors and other operations can also make krita crash

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Change colors
2. Or change workspace
3. Crash

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Huawei tablet ,HarmonyOs 4.0.0.115 /Andorid 12
Comment 1 wolthera 2023-10-18 10:32:26 UTC 
Hey, is it possible for you to get a backtrace, with gdb or the like?

Right now, we don't know if it is actually caused by the tablet, or a different kind of bug, and I myself can pick colors without crashing.
Comment 2 AppTest 2023-10-27 02:06:54 UTC 
This sounds like another case of the random crashing that's been reported happening with 5.2 Android: https://bugs.kde.org/show_bug.cgi?id=472705
Comment 3 wolthera 2023-10-27 13:31:59 UTC 
Ah, I hadn't seen this was an android bug, yes that makes it a duplicate.

Thanks!

*** This bug has been marked as a duplicate of bug 472705 ***