Bug 161715 - configure change crashed krita - now krita crashes X server upon opening tif
Summary: configure change crashed krita - now krita crashes X server upon opening tif
Status: RESOLVED NOT A BUG
Alias: None
Product: krita
Classification: Applications
Component: General (other bugs)
Version First Reported In: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2008-05-06 21:40 UTC by Elle Stone
Modified: 2017-09-12 02:42 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Elle Stone 2008-05-06 21:40:04 UTC
Version:           1.6.3-5 (using KDE 3.5.9)
Installed from:    Debian testing/unstable Packages
OS:                Linux

I was experimenting with using krita to resize 16-bit tifs (probably not relevant).  I was poking around the "configure krita" options (sorry, don't remember which ones, can't go back to check at this point) and clicked on OK to save the changes I made.  Krita immediately crashed and took the X server down along with it.  I restarted the computer and regained my desktop.  When I opened krita, and then attempted to open a 16-bit tif, the X server crashed again.  I restarted the computer, completely uninstalled krita (using synaptic), and then reinstalled krita, thinking that the configure options would go back to their defaults.  But upon attempting to open a (different) 16-bit tif with krita, the X server crashed again.

My apologies, I probably haven't given you enough information to reproduce this problem.  But I thought I'd go ahead and report it anyway, in case someone else has the same problem.
Comment 1 Elle Stone 2008-05-08 18:41:49 UTC
I finally have krita running again.  In addition to "completely removing" krita using synaptic, I also used konqueror to search for all files containing "krita" in their names, and put them all into the trash, THEN restarted the computer, THEN reinstalled krita.  Now krita complained that it couldn't start because it was missing all its icc profiles.  

So I reinstalled EVERY kde-related program I could find in synaptic and now, finally, I can start krita again and even open a tif without crashing the x-server.  Maybe it should be a little easier to get krita back to a default state.  Or maybe I just don't know the right procedure.  

Why doesn't kde/krita look for icc profiles in /usr/share/colors/icc???  
Comment 2 Cyrille Berger 2008-05-09 09:40:17 UTC
Because the standard [1] says /usr/share/color/icc . If that was just a typo in the bug report, please open a new entry, because krita (1.6 and 2.0) should find the profiles there, and 2.0 even install them in that directory.

[1] http://www.oyranos.com/wiki/index.php?title=OpenIccDirectoryProposal
Comment 3 Elle Stone 2008-05-09 13:17:54 UTC
Hi, Cyrille, it was a typo on my part - I meand "color" - sorry.  And I found/fixed the problem.  Krita was NOT seeing my icc profiles in /usr/share/color/icc UNTIL I did "sudo chown -R elle /usr/share/color/icc".  Probably what I needed to have done instead was relax permissions and leave ownership to root.  But apparently krita (and digikam) didn't have access to the /usr/share/color/icc folder until I chowned it over to myself.  Now all is well.  Thanks! for responding.  Is this permissions/ownership problem peculiar to debian in general, or linux in general, or just my installation?
Comment 4 Dominik Tritscher 2008-10-26 16:15:43 UTC
I don't see a way to reproduce that bug. I tried several settings, especially all xserver related (like OpenGL), but neither krita nor the xserver died.
Do you still experience this problem with a more recent Krita version (like from the beta series)?
If so, please provide more detailed instructions on how to reproduce that but.
Otherwise I would recommend to close the report, as no one managed to reproduce.
Comment 5 Dominik Tritscher 2008-12-07 12:44:57 UTC
As there seems to be no way to reproduce that bug, I close it for now. Please feel free to reopen, if more information become available.
Comment 6 Velshae Y Harris 2017-09-12 02:42:15 UTC
....