Another (probably interresting?) info : the terminal output of my actual installation ( Mint 14 KDE, buntu 12.10 ) where Krita master launch :

Code: Select all

deevad@worstation ~ $ 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
X Error: BadAtom (invalid Atom parameter) 5
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x0
X Error: BadWindow (invalid Window parameter) 3
  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: No such file or directory

CRITICAL: Your video driver forbids disabling VSync!
CRITICAL: Try toggling some VSync- or VBlank-related options in your driver configuration dialog.
CRITICAL: NVIDIA users can do:
CRITICAL: sudo nvidia-settings  >  (tab) OpenGL settings > Sync to VBlank  ( unchecked )


WARNING: We didn't manage to switch off VSync on your graphics adapter.
WARNING: It means either your hardware or driver doesn't support it,
WARNING: or we just don't know about this hardware. Please report us a bug
WARNING: with the output of 'glxinfo' for your card.

WARNING: Trying to workaround it by disabling Double Buffering.
WARNING: You may see some flickering when painting with some tools. It doesn't
WARNING: affect the quality of the final image, though.

krita(15267)/kdeui (kdelibs): No such XML file "/home/deevad/.kde/share/apps/"
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 12 (X_ConfigureWindow)
  Resource id:  0x5200159

(( note ; this 4 lines above repeat a lot of time ))

(( then on closing the apps ))

X Error: RenderBadPicture (invalid Picture parameter) 143
  Extension:    139 (RENDER)
  Minor opcode: 7 (RenderFreePicture)
  Resource id:  0x520027e
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 4 (X_DestroyWindow)
  Resource id:  0x5200159
QCoreApplication::postEvent: Unexpected null receiver
QCoreApplication::postEvent: Unexpected null receiver
QGLContext::makeCurrent(): Cannot make invalid context current.
QGLContext::makeCurrent(): Cannot make invalid context current.
QGLContext::makeCurrent(): Cannot make invalid context current.
QGLContext::makeCurrent(): Cannot make invalid context current.
QGLContext::makeCurrent(): Cannot make invalid context current.
QGLContext::makeCurrent(): Cannot make invalid context current.
QGLContext::makeCurrent(): Cannot make invalid context current.


Note : I corrected the Vsync according the output infos, and don't have the 'CRITICAL ' lines now.

I started this thread, and unfortunately, I've run into the same problem again. Krita won't start beyond the file creation dialog.

Please, do report the issue in Ubuntu's bug tracker. It's not a bug in Krita, but an Ubuntu-specific issue that is giving lots of KDE applications grief.

If you have a launchpad account, you can write the two items here in 'affect me' mode :
- https://bugs.launchpad.net/ubuntu/+sour ... ug/1195007
- https://bugs.launchpad.net/ubuntu/+sour ... ug/1178843

'affect me' button is on the top , after clicking the green sentence :



[edit] I just saw :
Scott Kitterman (kitterman) wrote 3 hours ago: #13
Fix released to raring-updates. Changed in qt4-x11 (Ubuntu Raring):
status: Fix Committed → Fix Released

Time to update ... And please gives feedback if the fix works, as I can't test here now I'm back on KDE.

I can confirm that it is indeed fixed in xubuntu 13.04. Just ran the update.
Glad that it's finally fixed, hope it stays that way now

Wow... The patch that caused the bug is... Very interesting. A bit scary, too. But I'm glad it's fixed now.

Good news Arsalan !
@boud: oh yes ... I read the cause ; https://launchpad.net/ubuntu/raring/+so ... 0ubuntu9.2

Sorry for being a noob but am I correct in thinking that this means the patch should be installed by running the software updater?
Because apparently my software is all up to date (xubuntu 13.04) and Krita is still crashing when I create or open a document.

Thanks for your help.

timthefish wrote: [...] this means the patch should be installed by running the software updater?

Not a nooby question, I forgot to mention it. Yes, certainly the patch get pushed but I didn't checked it myself on a running system because I moved back to 12.10 and KDE to continue painting when the bug happened ( I only checked on watching the online commit on launchpad ).

When you run Krita from terminal , ( write 'krita' on it ) , does you have also the 'Bad windows error' appearing ?

Maybe your system updates are holding back package for unknown reasons too.
Updating on the terminal can help to figure about it :

Code: Select all

sudo apt-get update
sudo apt-get upgrade


Requesting the package with the fix can also be a solution :

Code: Select all

sudo apt-get install qt4-x11

When I start Krita from the terminal I get:

Code: Select all

$ krita
Compiled for arch: ::Vc::SSE2Impl
Features supported:
    "SSE2"    ---    yes
    "SSE3"    ---    no
    "SSSE3"    ---    no
    "SSE4.1"    ---    no
    "SSE4.2"    ---    no
    "SSE4a"    ---    no
    "AVX "    ---    no
krita(5183)/koffice (lib pigment) KoColorConversionSystem::insertColorSpace: Cannot add node for  "YCBCR (8-bit integer/channel)" , since there are no profiles available
krita(5183)/koffice (lib pigment) KoColorConversionSystem::insertColorSpace: Cannot add node for  "YCBCR (16-bit integer/channel)" , since there are no profiles available
krita(5183)/koffice (lib pigment) KoColorConversionSystem::insertColorSpace: Cannot add node for  "YCBCR (32-bit float/channel)" , since there are no profiles available
Object::connect: No such signal KisResourceServerProvider::notifyBrushBlacklistCleanup()
krita(5183)/koffice (lib kopageapp) KoOdfLoadingContext::KoOdfLoadingContext: could not parse manifest document


Then when I create a new file I get:

Code: Select all

krita(5256)/kdeui (KAction) KActionCollection::setComponentData: this does not work on a KActionCollection containing actions!
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 2296 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.)
krita(5256) KoResourceTagging::writeXMLFile: Cannot write meta information to ' "/home/tim/.kde/share/apps/krita/tags.xml" '.
krita(5256) KoResourceTagging::writeXMLFile: Cannot write meta information to ' "/home/tim/.kde/share/apps/krita/tags.xml" '.
krita(5256) KoResourceTagging::writeXMLFile: Cannot write meta information to ' "/home/tim/.kde/share/apps/krita/tags.xml" '.
krita(5256) KoResourceTagging::writeXMLFile: Cannot write meta information to ' "/home/tim/.kde/share/apps/krita/tags.xml" '.
krita(5256) KoResourceTagging::writeXMLFile: Cannot write meta information to ' "/home/tim/.kde/share/apps/krita/tags.xml" '.
krita(5256) KoResourceTagging::writeXMLFile: Cannot write meta information to ' "/home/tim/.kde/share/apps/krita/tags.xml" '.
krita(5256) KoResourceTagging::writeXMLFile: Cannot write meta information to ' "/home/tim/.kde/share/apps/krita/tags.xml" '.
CRITICAL: According to statistics of the KisTileDataStore some tiles have leaked from the Krita control!
CRITICAL: Tiles in memory: 2 Total tiles: 2


If I try

Code: Select all

sudo apt-get install qt4-x11

I get

Code: Select all

Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package qt4-x11 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'qt4-x11' has no installation candidate


Also i must have enabled raring-backports at some point. Could this be the issue?

Thanks!

Can you provide a full list of all the repositories you are using on your system please?

Will /etc/apt/sources.list do?

Code: Select all

# deb cdrom:[Xubuntu 13.04 _Raring Ringtail_ - Release amd64 (20130423.1)]/ raring main multiverse restricted universe

# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://nz.archive.ubuntu.com/ubuntu/ raring main restricted
deb-src http://nz.archive.ubuntu.com/ubuntu/ raring main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://nz.archive.ubuntu.com/ubuntu/ raring-updates main restricted
deb-src http://nz.archive.ubuntu.com/ubuntu/ raring-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://nz.archive.ubuntu.com/ubuntu/ raring universe
deb-src http://nz.archive.ubuntu.com/ubuntu/ raring universe
deb http://nz.archive.ubuntu.com/ubuntu/ raring-updates universe
deb-src http://nz.archive.ubuntu.com/ubuntu/ raring-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://nz.archive.ubuntu.com/ubuntu/ raring multiverse
deb-src http://nz.archive.ubuntu.com/ubuntu/ raring multiverse
deb http://nz.archive.ubuntu.com/ubuntu/ raring-updates multiverse
deb-src http://nz.archive.ubuntu.com/ubuntu/ raring-updates multiverse

## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.

deb http://security.ubuntu.com/ubuntu raring-security main restricted
deb-src http://security.ubuntu.com/ubuntu raring-security main restricted
deb http://security.ubuntu.com/ubuntu raring-security universe
deb-src http://security.ubuntu.com/ubuntu raring-security universe
deb http://security.ubuntu.com/ubuntu raring-security multiverse
deb-src http://security.ubuntu.com/ubuntu raring-security multiverse

## Uncomment the following two lines to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
# deb http://archive.canonical.com/ubuntu raring partner
# deb-src http://archive.canonical.com/ubuntu raring partner

## This software is not part of Ubuntu, but is offered by third-party
## developers who want to ship their latest software.
deb http://extras.ubuntu.com/ubuntu raring main
deb-src http://extras.ubuntu.com/ubuntu raring main
deb http://nz.archive.ubuntu.com/ubuntu/ raring-backports main restricted universe multiverse


Also I have used and then removed both the krita-lime ppa and the kubuntu backports ppa when trying to get krita to work (maybe a bad idea).

If I'm the only one still having issues don't worry about it, I was going to change distro soon anyway and krita in openbox works fine for me .

Yep, that is fine.

Rather unusually, qt4-x11 does not come from the main repositories - perhaps it came from the Krita Lime PPA instead?
My guess is the installed version of Krita you have comes from the Lime PPA, while Qt comes from the mainline repositories now.

I'm not sure what to do given the state of your system at the moment though - it depends on where your Krita comes from, and what other Qt applications you are using.

Im fairly certain I removed the Krita-lime version of krita but probably not qt4-x11 (if that did come with it). Krita is the only KDE application i use howevever I have a few other Qt applications (retext, texmaker, ipython) which open fine.

Okay. In that case, as you have mixed packages it is probably best to wait until you reinstall your system - as that will fix the issue in the process. Without knowing the exact state of the installed Qt packages it is hard to say which need to be downgraded / upgraded / reinstalled.