Bug 456837 - Crash and then Wont Start even after Reinstall
Summary: Crash and then Wont Start even after Reinstall
Status: RESOLVED DOWNSTREAM
Alias: None
Product: krita
Classification: Applications
Component: * Unknown (show other bugs)
Version: unspecified
Platform: Kubuntu Linux
: NOR critical
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-07-17 21:17 UTC by Artillery
Modified: 2022-07-18 14:42 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Artillery 2022-07-17 21:17:43 UTC
SUMMARY
***
Have been using Krita for a few weeks after a System Reinstall. All was great until Krita Crashed. I have tried Removing and reinstalling but Krita wont start up and I cant use it at all now.
***


STEPS TO REPRODUCE
I dont know what caused this. Krita was working for weeks with no problem then crashed and wont launch now.  
Tried removing and reinstalling, still wont launch and reports error message

OBSERVED RESULT
CRASh

EXPECTED RESULT
Launch

SOFTWARE/OS VERSIONS
Kubuntu 21.10
Linux/KDE Plasma: 


ADDITIONAL INFORMATION
Application: krita (krita), signal: Segmentation fault

[KCrash Handler]
#4  0x00007f64cc9c3c7f in deepin_platform_plugin::DHighDpi::logicalDpi(QXcbScreen*) () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libdxcb.so
#5  0x00007f64d285d915 in ?? () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#6  0x00007f64d280c715 in QWindowSystemInterface::handleScreenAdded(QPlatformScreen*, bool) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#7  0x00007f64cc86f358 in QXcbConnection::initializeScreens() () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#8  0x00007f64cc846600 in QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, char const*) () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#9  0x00007f64cc849d30 in QXcbIntegration::QXcbIntegration(QStringList const&, int&, char**) () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#10 0x00007f64cc9bda34 in deepin_platform_plugin::DPlatformIntegration::DPlatformIntegration(QStringList const&, int&, char**) () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libdxcb.so
#11 0x00007f64cc9bd134 in DPlatformIntegrationPlugin::create(QString const&, QStringList const&, int&, char**) () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libdxcb.so
#12 0x00007f64d282b4ef in QGuiApplicationPrivate::createPlatformIntegration() () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#13 0x00007f64d282cb08 in QGuiApplicationPrivate::createEventDispatcher() () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#14 0x00007f64d2456e47 in QCoreApplicationPrivate::init() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007f64d282fa86 in QGuiApplicationPrivate::init() () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#16 0x00007f64d2830a58 in QGuiApplication::QGuiApplication(int&, char**, int) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#17 0x00007f64d3fb6669 in KisOpenGLModeProber::probeFormat(KisOpenGL::RendererConfig const&, bool) () from /lib/x86_64-linux-gnu/libkritaui.so.17
#18 0x00007f64d3f9ef69 in KisOpenGL::selectSurfaceConfig(KisOpenGL::OpenGLRenderer, KisConfig::RootSurfaceFormat, bool) () from /lib/x86_64-linux-gnu/libkritaui.so.17
#19 0x0000561fee4220dc in ?? ()
#20 0x00007f64d1d65fd0 in __libc_start_call_main (main=main@entry=0x561fee421b60, argc=argc@entry=1, argv=argv@entry=0x7fff84465ef8) at ../sysdeps/nptl/libc_start_call_main.h:58
#21 0x00007f64d1d6607d in __libc_start_main_impl (main=0x561fee421b60, argc=1, argv=0x7fff84465ef8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff84465ee8) at ../csu/libc-start.c:409
#22 0x0000561fee426055 in ?? ()
[Inferior 1 (process 6137) detached]
Comment 1 Tiar 2022-07-18 01:13:14 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.
Comment 2 Artillery 2022-07-18 11:48:35 UTC
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?
Comment 3 Tiar 2022-07-18 12:42:04 UTC
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.
Comment 4 Artillery 2022-07-18 14:42:23 UTC
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.