New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Krita doesn't start #2010

Closed
ghost opened this Issue May 21, 2016 · 5 comments

Comments

Projects
None yet
3 participants
@ghost

ghost commented May 21, 2016

Qubes OS version (e.g., R3.1):

R3.1

Affected TemplateVMs (e.g., fedora-23, if applicable):

debian-8 and fedora-23


Expected behavior:

Krita starts without problems.

Actual behavior:

The AppVM is started, Krita's icon begin to bounce and Krita shows up in the window panel. But nothing happens, and after some time the icon and entry in the window panel disappears.

Steps to reproduce the behavior:

  1. Install Krita (debian-8: krita, fedora-23: calligra-krita)
  2. Try to start Krita from an AppVM.

General notes:


Related issues:

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong May 21, 2016

Member

"Krita is a raster graphics editor based on the KDE Platform."

Member

andrewdavidwong commented May 21, 2016

"Krita is a raster graphics editor based on the KDE Platform."

@mfc

This comment has been minimized.

Show comment
Hide comment
@mfc

mfc May 22, 2016

Member

I was not able to confirm in debian-8, I have no problem running it (didn't try fedora-23).

maybe try running it from the command line and see what errors come out? you can also send the run command from dom0 if you think there may be Qubes-specific errors.

Member

mfc commented May 22, 2016

I was not able to confirm in debian-8, I have no problem running it (didn't try fedora-23).

maybe try running it from the command line and see what errors come out? you can also send the run command from dom0 if you think there may be Qubes-specific errors.

@mfc mfc added the worksforme label May 22, 2016

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek May 22, 2016

Member

Same for me, on fedora-23. But: started in from terminal, not menu entry. Because unrelated bug in my testing environment prevented creating menu entries at all...

Member

marmarek commented May 22, 2016

Same for me, on fedora-23. But: started in from terminal, not menu entry. Because unrelated bug in my testing environment prevented creating menu entries at all...

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong May 23, 2016

Member

@dumbl3d0re: Please try starting from the command line, and let us know.

Member

andrewdavidwong commented May 23, 2016

@dumbl3d0re: Please try starting from the command line, and let us know.

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost May 23, 2016

It works now apparently, both by starting it from terminal and the menu. Seems that I'd to reboot Qubes to get it to work.

ghost commented May 23, 2016

It works now apparently, both by starting it from terminal and the menu. Seems that I'd to reboot Qubes to get it to work.

@ghost ghost closed this May 23, 2016

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment