Hello,
I have been having a problem lately, Krita crashes when I try to create a new document. I am using Xubuntu and this is the error message I get when I run Krita from the terminal:
http://pastie.org/8050772
This only started recently, it used to work fine before. The problem started when I tried to install another compositing manager (compton) using this guide:
http://ubuntuforums.org/showthread.php?t=2144468
Although I don't use Compton, Krita has stopped working. I unistalled it using apt-get purge krita but the problem persists after reinstalling as well.
Any help would be appreciated.
Thanks.

No idea... The terminal output doesn't show any real errors either...

Is there anything else I could do that might reveal the source of the problem?

Try installing the debug packages for krita and calligra, then run in gdb to see whether you can get a good stacktrace.

That's a 500+mb installation, I'll have to do it once I get home. Thank you for your answer though.

After installing the calligra-dbg package, I ran krita in gdb, this is what it returned. I wonder if I did it correctly though.
http://pastie.org/8054147
I hope this is useful.

Can you type "bt" on the gdb prompt after Krita crashes?

Typing bt on the gdb prompt after the crash simply states "No stack."

Then it actually isn't a crash in krita... I'm stymied now, I haven't heard of something like this happening and I have no idea what is going on.

One thing... Did you enable opengl in Krita?

I did not. But just in case I ran krita --graphicssytem raster with the same result. When I ran krita --graphicssystem opengl the kde crash handler opened and generated a log in the developer information tab. I don't know if it is useful but I'll paste it anyway.
http://pastie.org/8054648.

Hm, that is a bug in your distro packaging: the shiva filters use openctl, which uses llvm, which is also used by your mesa graphics driver and it's built the right way for mesa, and the wrong way for openctl... You can remove the /usr/lib/kde4/kritashivafilters.so file (as root) to avoid this problem.

That didn't fix the problem. I just reinstalled my OS. I hope this doesn't happen again, whatever it was.
Thank you very much for taking the time to help, I really appreciate it.

You're welcome! It remains a mystery, but I hope you can have fun painting again

Hello
I appear to have the same problem. Krita was working fine last night, but it won't run at all today. I'm using Mint 15 with cinnamon. Nvidia 304 drivers (also tried 310), and I did have opengl enabled. I have since deleted the kritarc file, but that didn't help. I also added the lime PPA, and that didn't help either.

I can't create a new or open an existing document. I think I run Mint's update manager this morning, but I can't remember if I did or not.

Heres the output from terminal

john@johnDesktop ~ $ krita
Compiled for arch: ::Vc::SSE41Impl
Features supported:
"SSE2" --- yes
"SSE3" --- yes
"SSSE3" --- yes
"SSE4.1" --- yes
"SSE4.2" --- no
"SSE4a" --- no
"AVX " --- no
QCoreApplication::postEvent: Unexpected null receiver
QCoreApplication::postEvent: Unexpected null receiver
The program 'krita' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAtom (invalid Atom parameter)'.
(Details: serial 2752 error_code 5 request_code 20 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
CRITICAL: According to statistics of the KisTileDataStore some tiles have leaked from the Krita control!
CRITICAL: Tiles in memory: 2 Total tiles: 2
KCrash: Application 'krita' crashing...
Fatal Error: Accessed global static 'KGlobalPrivate *globalData()' after destruction. Defined at ../../kdecore/kernel/kglobal.cpp:127
Unable to start Dr. Konqi
john@johnDesktop ~ $


Any help would be greatly appreciated