| Summary: | Crash and then Wont Start even after Reinstall | ||
|---|---|---|---|
| Product: | [Applications] krita | Reporter: | Artillery <artilleryvoo> |
| Component: | * Unknown | Assignee: | Krita Bugs <krita-bugs-null> |
| Status: | RESOLVED DOWNSTREAM | ||
| Severity: | critical | CC: | tamtamy.tymona |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Artillery
2022-07-17 21:17:43 UTC
Your crash log shows that you're using deepin and the crash happens because of some weirdness between/with deepin and displays. You can try to uninstall deepin and try Krita, or you can try using Krita's appimage, because then Krita will be using its own Qt instead of the system one. Check out bug 433634 for context and some more potential solutions in the comments. This is the first time I ever even heard of Deepin! Is that something to do with Kubuntu? I might use something else if its causing problems. What do you reccommend is best for Krita? Ive been using Krita for about 6 months and this is the only time this has happened. I was working fine until this Crash now wont start at all., even after reinstalling After removing Krita it seems to leave config files behind tho. Is there a way to remove everything so that you can start fresh? Deepin is something that is installed on your system (I'm not sure why, have you installed anything recently? You might want to try `apt policy deepin-*` and `apt-cache rdepends deepin-*` to see what you have installed and what depends on deepin), so even removing the configuration files for Krita won't help, I think. Resources (brushes etc.) are in `~/.local/share/krita`, and configuration files in `~/.config/`. You can try removing it if nothing too important depends on it. You might want to try asking for help on Kubuntu forums, they might know what's up with deepin being there. In any case, deepin Might be interfering with things written in Qt... which actually most KDE's software is, and you're using Kubuntu, so there is a chance you'll encounter it again. Regarding the appimage, this is what I was told: "on systems that have QT_PLUGIN_PATH globally set, the appimage will try to load the global Qt plugins and likely crash. if QT_PLUGIN_PATH isn't set, the appimage won't load the deepin qt platform plugin". So you might want to try doing "echo $QT_PLUGIN_PATH" to see if it's empty or not. And if it's empty, the appimage will likely work well. Thanks Tiar, echo $QT_PLUGIN_PATH came back as empty so hopefully appImage will work ok. I think I might have found the Deepin culprit. I installed a color picker app called 'Deepin Picker' and shortly after I started having the problem with Krita. It seems to have installed a ton of Deepin Apps too. I Removed it but Krita still not launching from system app and there's still a ton of Deepin Stuff installed. I cant be sure if that app DeepinPicker installed all these but it everything was fine up until I installed it, so it looks mighty suspicious. apt-cache rdepends deepin-* deepin-boot-maker Reverse Depends: deepin-calculator Reverse Depends: deepin-deb-installer Reverse Depends: deepin-gettext-tools Reverse Depends: deepin-icon-theme Reverse Depends: deepin-image-viewer Reverse Depends: multimedia-graphics multimedia-photography deepin-menu Reverse Depends: deepin-terminal deepin-movie Reverse Depends: deepin-music Reverse Depends: deepin-notifications Reverse Depends: deepin-screenshot deepin-picker Reverse Depends: deepin-screen-recorder Reverse Depends: deepin-screenshot Reverse Depends: deepin-screen-recorder deepin-screen-recorder deepin-shortcut-viewer Reverse Depends: deepin-screenshot deepin-sound-theme Reverse Depends: deepin-terminal Reverse Depends: deepin-voice-recorder Reverse Depends: multimedia-recording <deepin-system-settings-module-account> artillery@artillery-x:~$ apt-cache rdepends deepin-* deepin-boot-maker Reverse Depends: deepin-calculator Reverse Depends: deepin-deb-installer Reverse Depends: deepin-gettext-tools Reverse Depends: deepin-icon-theme Reverse Depends: deepin-image-viewer Reverse Depends: multimedia-graphics multimedia-photography deepin-menu Reverse Depends: deepin-terminal deepin-movie Reverse Depends: deepin-music Reverse Depends: deepin-notifications Reverse Depends: deepin-screenshot deepin-picker Reverse Depends: deepin-screen-recorder Reverse Depends: deepin-screenshot Reverse Depends: deepin-screen-recorder deepin-screen-recorder deepin-shortcut-viewer Reverse Depends: deepin-screenshot deepin-sound-theme Reverse Depends: deepin-terminal Reverse Depends: deepin-voice-recorder Reverse Depends: multimedia-recording <deepin-system-settings-module-account> Sent with Proton Mail secure email. ------- Original Message ------- On Monday, July 18th, 2022 at 13:42, Tiar <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=456837 > > --- Comment #3 from Tiar tamtamy.tymona@gmail.com --- > > Deepin is something that is installed on your system (I'm not sure why, have > you installed anything recently? You might want to try `apt policy deepin-*` > and `apt-cache rdepends deepin-*` to see what you have installed and what > depends on deepin), so even removing the configuration files for Krita won't > help, I think. > > Resources (brushes etc.) are in `~/.local/share/krita`, and configuration files > in `~/.config/`. > > You can try removing it if nothing too important depends on it. You might want > to try asking for help on Kubuntu forums, they might know what's up with deepin > being there. > > In any case, deepin Might be interfering with things written in Qt... which > actually most KDE's software is, and you're using Kubuntu, so there is a chance > you'll encounter it again. > > Regarding the appimage, this is what I was told: "on systems that have > QT_PLUGIN_PATH globally set, the appimage will try to load the global Qt > plugins and likely crash. if QT_PLUGIN_PATH isn't set, the appimage won't load > the deepin qt platform plugin". So you might want to try doing "echo > $QT_PLUGIN_PATH" to see if it's empty or not. And if it's empty, the appimage > will likely work well. > > -- > You are receiving this mail because: > You reported the bug. |