Hello, I'm sorry, that I made a new thread again.

I' can start until now krita only from the terminal, and I get often this kind of error messages, I'm using 2.8.x alpha...

I have also some problems, sometimes in brush-behaviors sometimes krita is crashing on my lubuntu 13.10 ...

what should I do?

This are some messages!

Code: Select all

QCoreApplication::postEvent: Unexpected null receiver
QCoreApplication::postEvent: Unexpected null receiver
X Error: BadAtom (invalid Atom parameter) 5
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x0
X Error: BadAtom (invalid Atom parameter) 5
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x0
WARNING (KoResourceItemChooser::updatePreview): the resource "2B pencil Grain 2 b" has created a non-rgb32 image thumbnail. It may not work properly.
WARNING (KoResourceItemChooser::updatePreview): the resource "2B pencil Grain 2 b" has created a non-rgb32 image thumbnail. It may not work properly.
connect failed: Datei oder Verzeichnis nicht gefunden
krita(1857)/kdeui (kdelibs): No such XML file "/home/geri/.kde/share/apps/"
Object::disconnect: Unexpected null parameter
Object::disconnect: Unexpected null parameter
Object::disconnect: Unexpected null parameter
Object::disconnect: Unexpected null parameter
WARINING: there is no intersection point  in the basic smoothing algoriths

I Think I will go back to 2.7.2

yeah, you chose a pretty bad time to start using the krita-lime ppa. A big part was just recoded(this is probably for the best), and that is leading to a lot of bugs popping up. Cutting edge is a two-edged blade, it also has unusual bugs and things breaking suddenly

In any case, these are not error messages, but mostly us developers talking to ourselves... Treat it as a small window into our minds... Let's see:

> QCoreApplication::postEvent: Unexpected null receiver
> QCoreApplication::postEvent: Unexpected null receiver

Qt (the base framework we're using) is whining a bit. Probably something isn't setup in the order that it should be, but what's going on is hard to discover, and it's not something in Krita, but lower-down the stack.

> X Error: BadAtom (invalid Atom parameter) 5
> Major opcode: 20 (X_GetProperty)
> Resource id: 0x0
> X Error: BadAtom (invalid Atom parameter) 5
> Major opcode: 20 (X_GetProperty)
> Resource id: 0x0

You don't have per-display X11 color management setup, probably. X11 complains like this if we try to discover whether you have...

> WARNING (KoResourceItemChooser::updatePreview): the resource "2B pencil Grain 2 b" has created a non-rgb32 image thumbnail. It may not work properly.
> WARNING (KoResourceItemChooser::updatePreview): the resource "2B pencil Grain 2 b" has created a non-rgb32 image thumbnail. It may not work properly.

Slightly more interesting: this paintop preset has an icon that's in a different format from expected. Not that it'll have any impact on painting, but, yeah, we need to redo the icon.

> connect failed: Datei oder Verzeichnis nicht gefunden

No idea... Since it's in German, it probably doesn't come from Krita directly.

> krita(1857)/kdeui (kdelibs): No such XML file "/home/geri/.kde/share/apps/"

I don't get this one myself: it looks like there's a plugin that tries to find a definition file for shortcuts and cannot find it. Might be interesting to follow-up on.

> Object::disconnect: Unexpected null parameter
> Object::disconnect: Unexpected null parameter
> Object::disconnect: Unexpected null parameter
> Object::disconnect: Unexpected null parameter

Not interesting: we're trying to make sure something that doesn't exist yet doesn't get told about something that doesn't need to happen yet. There's a huge amount of setup going on in Krita on startup and it's really difficult to order that properly. It's like trying to get choir with a thousand singers to start at exactly the same moment -- treating a little synchronicity aberration as an error would mean stopping the choral before it properly begins every time.

> WARINING: there is no intersection point in the basic smoothing algoriths

This is just an internal message for Dmitry to check his line smoothing algorithm. It needs to be removed before we release 2.8. The result is not an error, but the conditions that cause it are interesting when it comes to improving Krita.

Now... For a real shocker. Run 'kdebugdialog'. Type 'krita' in the search field. Enable all check boxes. Then run krita from the command line. We developers, we're garrulous...