Created attachment 989339 [details] backtrace Description of problem: Krita crashes when trying to save file Version-Release number of selected component (if applicable): 2.8.7 How reproducible: Everytime Steps to Reproduce: 1. Open new document with Krita 2. File -> Save -> Okay 3. Crash Actual results: Crash on Save Expected results: File should be saved without any crashes Additional info: another bug i noticed is that the units don't update themselves when i select a different one while creating a new document.
This is Krita on Gnome Desktop
Can someone look into this issue please? You just cant save with the default settings
Thread 1 (Thread 0x7ff1558b98c0 (LWP 27373)): [KCrash Handler] #5 0x00007ff0f145082d in opj_event_msg () at /lib64/libopenjpeg.so.1 #6 0x00007ff0f1457d55 in opj_encode () at /lib64/libopenjpeg.so.1 #7 0x00007ff0f1676986 in jp2Converter::buildFile(KUrl const&, KisSharedPtr<KisPaintLayer>, JP2ConvertOptions const&) () at /usr/lib64/kde4/kritajp2export.so #8 0x00007ff0f1674736 in jp2Export::convert(QByteArray const&, QByteArray const&) () at /usr/lib64/kde4/kritajp2export.so #9 0x00007ff1547321a8 in CalligraFilter::ChainLink::invokeFilter(CalligraFilter::ChainLink const*) () at /lib64/libkomain.so.13 #10 0x00007ff15472b4e5 in KoFilterChain::invokeChain() () at /lib64/libkomain.so.13 Try saving as something other than jpeg? The provided backtrace is missing some debuginfo too (the backtrace is missing line numbers)
Created attachment 1004825 [details] backtrace Saving in other formats work fine. I think Krita uses jpeg by default. About the log, that's all KDE Crash Handler gave, I Saved the backtrace because i dont have a KDE bugzilla account. Ill attach a fresh one here. More info: Running Via Terminal: [user@littleboy ~]$ krita Legacy integer arithmetics implementation ################################### # Adding a tablet device: Wacom Bamboo One S Pen stylus Device Type: "Stylus" # Axes limits data X: 0 14720 Y: 0 9225 Z: 0 0 Pressure: 0 2048 Rotation: -900 899 T. Pres: 0 0 ################################### # Adding a tablet device: Wacom Bamboo One S Pen eraser Device Type: "XFreeEraser" # Axes limits data X: 0 14720 Y: 0 9225 Z: 0 0 Pressure: 0 2048 Rotation: 0 1 T. Pres: 0 0 QCoreApplication::postEvent: Unexpected null receiver krita(22437) KoResourceServer<T>::loadResources: Loading resource "/usr/share/kde4/apps/krita/paintoppresets/Sketch_line.kpp" failed krita(22437) KoResourceServer<T>::loadResources: Loading resource "/usr/share/kde4/apps/krita/paintoppresets/Hatch_noisy.kpp" failed krita(22437) KoResourceServer<T>::loadResources: Loading resource "/usr/share/kde4/apps/krita/paintoppresets/Hairy_Squared.kpp" failed QCoreApplication::postEvent: Unexpected null receiver libpng warning: iCCP: Not recognizing known sRGB profile that has been edited libpng warning: iCCP: Not recognizing known sRGB profile that has been edited libpng warning: iCCP: too many profiles libpng warning: iCCP: too many profiles libpng warning: iCCP: too many profiles libpng warning: iCCP: too many profiles connect failed: No such file or directory krita(22437)/kdeui (kdelibs): No such XML file "/home/user/.kde/share/apps/" KCrash: Application 'krita' crashing... KCrash: Attempting to start /usr/libexec/kde4/drkonqi from kdeinit KCrash: Connect sock_file=/home/user/.kde/socket-littleboy/kdeinit4__0 [1]+ Stopped krita [user@littleboy ~]$ QSocketNotifier: Invalid socket 23 and type 'Read', disabling...
Krita should save in it's native .kra format by default (not jpeg2000)
(In reply to Rex Dieter from comment #5) > Krita should save in it's native .kra format by default (not jpeg2000) Yup, i dont understand why it chooses jpeg2000 over .kra Same situation after fresh install
That's a largely useless backtrace too. at some point, the kde crash handler should give you the option of installing debuginfo (you should :) ) Otherwise, you can do it by hand: debuginfo-install calligra-krita calligra-core
Re: file format Even if you choose a file name with .kra extention? My file save dialog includes: Name: Filter: All supported formats and has checkbox (checked): automatically select file name extention (.kra) Is yours the same?
(In reply to Rex Dieter from comment #8) > Re: file format > > Even if you choose a file name with .kra extention? > > My file save dialog includes: > > Name: > Filter: All supported formats > and has checkbox (checked): automatically select file name extention (.kra) > > Is yours the same? Ah i dont get you. From File->Save/Save-As I just get to choose where i want to save the file, and choose the selected format. By default it goes to Jpeg2000 and it gives a pop-up "JPEG2000 Export Options" asking me about the compression and No. of Resolutions(6-default). On choosing .kra, i get no options whatsoever, it saves fine. Im on Gnome btw(latest)
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.