I'm using the newest version available from the website (2.9.2 git c31b787) I can open a file and pan it around, even paint on it without problems. However, as soon as I try to pick a color from the image, or try to synthesize one in the Advanced Color Selector, Krita crashes. At first I thought it was my computer, as this has been a recent occurrence, but I have now tested it on another computer and can reproduce it as well. I tried creating a new file to test if it was a problem from the file I was working on, and I can't reproduce it all the time (but it still happens more often than not). On the file I'm working on however, I can reproduce it 100% of the time. Reproducible: Always Steps to Reproduce: 1. Open Krita 2. Open a File 3. Pick a color from the image or try to create one from the Advanced Color Selector Actual Results: Krita Crashes Expected Results: The new color should be up and available for use. (I can provide the file I'm working on if you need it or think it can help track the bug down.) I'm not sure how to get a stack trace from Krita, but I was able to "debug" it using my Visual Studio. This is the exception that pops up: Unhandled exception at 0x0000000063FFB9CE (QtCore4.dll) in krita.exe: 0xC0000005: Access violation reading location 0xFFFFFFFFFFFFFFFF. And this is the Call Stack: http://pastebin.com/Tn1eJcaR
Hi Orianna, Thanks for the report, I'll look into it. I haven't managed to reproduce the bug yet. Could you make the file that allows to reproduce it always available? Either as an attachment to this bug, or you mail it me: boud@kde.org. Thanks!
Oh -- and does this happen no matter which color selectors are selected?
Hi! Sorry for the delay! I've tried changing the color selector options around, but it still happens. I've also noticed as of late that sometimes it doesn't crash right away, but only after a few color picks. But the number of color picks seems to be random. Back when I reported, it would crash as soon as I picked the first color without fail, but now sometimes it takes a few tries to make it crash.
Hi Joana, Are you using the 64 or 32 bits version of Krita?
I am having the same problem. KDE Sabayon 64 bit fully upgraded. Nvidia graphics card. Wacom graphics tablet Using 16bit float color
Hi Douglas, If you can reproduce the bug on Linux, do you get a backtrace report that you could add to the bug report? Since I cannot reproduce the issue, I cannot get a backtrace and cannot fix it.
Created attachment 97974 [details] attachment-3830-0.html I can try. How do you get a backtrace from Krita? Also it is hard because I can't cause the crash at will but it is still a problem. It crashed yesterday from color selection at 16 bit float color on the square color picker. On Sat, Mar 19, 2016 at 3:59 PM, Boudewijn Rempt via KDE Bugzilla < bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=346967 > > Boudewijn Rempt <boud@valdyas.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Resolution|--- |WAITINGFORINFO > Status|UNCONFIRMED |NEEDSINFO > > --- Comment #6 from Boudewijn Rempt <boud@valdyas.org> --- > Hi Douglas, > > If you can reproduce the bug on Linux, do you get a backtrace report that > you > could add to the bug report? Since I cannot reproduce the issue, I cannot > get a > backtrace and cannot fix it. > > -- > You are receiving this mail because: > You are on the CC list for the bug. >
Created attachment 97976 [details] attachment-4172-0.html Legacy integer arithmetics implementation ################################### # Adding a tablet device: Wacom Intuos PT M Pen stylus Device Type: "Stylus" # Axes limits data X: 0 21600 Y: 0 13500 Z: 0 0 Pressure: 0 2048 Rotation: -900 899 T. Pres: 0 0 ################################### # Adding a tablet device: Wacom Intuos PT M Pen eraser Device Type: "XFreeEraser" # Axes limits data X: 0 21600 Y: 0 13500 Z: 0 0 Pressure: 0 2048 Rotation: 0 1 T. Pres: 0 0 libpng warning: iCCP: too many profiles libpng warning: iCCP: too many profiles libpng warning: iCCP: too many profiles libpng warning: iCCP: too many profiles Object::connect: No such signal QToolButton::triggered() Object::connect: (sender name: 'bnRaise') Object::connect: No such signal QToolButton::triggered() Object::connect: (sender name: 'bnLower') krita(3605)/KZip KZip::openArchive: Invalid ZIP file. Unexpected end of file. Could not open store on bundle "/home/britta/.kde4/share/apps/krita/bundles/essential_illustration_brushes_v3_extended_by_fox_orian-d1xs95k.bundle" krita(3605) KoResourceServer<T, Policy>::loadResources: Loading resource "/home/britta/.kde4/share/apps/krita/bundles/essential_illustration_brushes_v3_extended_by_fox_orian-d1xs95k.bundle" failed Could not load META-INF/manifest.xml krita(3605) KoResourceServer<T, Policy>::loadResources: Loading resource "/home/britta/.kde4/share/apps/krita/bundles/Wolthera_workspace-set.bundle" failed krita(3605)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "No such object path '/modules/ktimezoned'" krita(3605)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned WARNING: KisImageConfig: requested config synchronization from nonGUI thread! Skipping... WARNING: KisImageConfig: requested config synchronization from nonGUI thread! Skipping... WARNING: KisImageConfig: requested config synchronization from nonGUI thread! Skipping... OpenGL version 1.1 or higher is present. OpenGL version 1.2 or higher is present. OpenGL version 1.3 or higher is present. OpenGL version 1.4 or higher is present. OpenGL version 1.5 or higher is present. OpenGL version 2.0 or higher is present. OpenGL version 2.1 or higher is present. OpenGL version 3.0 or higher is present. OpenGL version 3.1 or higher is present. OpenGL version 3.2 or higher is present. OpenGL version 3.3 or higher is present. OpenGL version 4.0 or higher is present. krita(3605)/koffice (lib komain) KoRuler::createGuideToolConnection: No guides tool found, skipping connection krita(3605)/koffice (lib komain) KoRuler::createGuideToolConnection: No guides tool found, skipping connection krita(3605) CanvasData::activateToolActions: "InteractionTool" : action "object_order_raise" conflicts with canvas action "rotate_canvas_right" shortcut: "Ctrl+]" krita(3605) CanvasData::activateToolActions: "InteractionTool" : action "object_order_lower" conflicts with canvas action "rotate_canvas_left" shortcut: "Ctrl+[" krita(3605) CanvasData::activateToolActions: "InteractionTool" : action "object_order_raise" conflicts with canvas action "rotate_canvas_right" shortcut: "Ctrl+]" krita(3605) CanvasData::activateToolActions: "InteractionTool" : action "object_order_lower" conflicts with canvas action "rotate_canvas_left" shortcut: "Ctrl+[" Segmentation fault On Sat, Mar 19, 2016 at 7:21 PM, Douglas via KDE Bugzilla < bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=346967 > > --- Comment #7 from Douglas <magick.crow@gmail.com> --- > I can try. How do you get a backtrace from Krita? Also it is hard because > I can't cause the crash at will but it is still a problem. It crashed > yesterday from color selection at 16 bit float color on the square color > picker. > > On Sat, Mar 19, 2016 at 3:59 PM, Boudewijn Rempt via KDE Bugzilla < > bugzilla_noreply@kde.org> wrote: > > > https://bugs.kde.org/show_bug.cgi?id=346967 > > > > Boudewijn Rempt <boud@valdyas.org> changed: > > > > What |Removed |Added > > > > > ---------------------------------------------------------------------------- > > Resolution|--- |WAITINGFORINFO > > Status|UNCONFIRMED |NEEDSINFO > > > > --- Comment #6 from Boudewijn Rempt <boud@valdyas.org> --- > > Hi Douglas, > > > > If you can reproduce the bug on Linux, do you get a backtrace report that > > you > > could add to the bug report? Since I cannot reproduce the issue, I cannot > > get a > > backtrace and cannot fix it. > > > > -- > > You are receiving this mail because: > > You are on the CC list for the bug. > > > > -- > You are receiving this mail because: > You are on the CC list for the bug. >
Created attachment 97977 [details] attachment-4971-0.html Youtube video of crash. Please tell me when you are done with it so I can remove the video. Thanks. https://youtu.be/jSq-wNCJ-fk On Sat, Mar 19, 2016 at 7:24 PM, Douglas via KDE Bugzilla < bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=346967 > > --- Comment #8 from Douglas <magick.crow@gmail.com> --- > Legacy integer arithmetics implementation > ################################### > # Adding a tablet device: Wacom Intuos PT M Pen stylus > Device Type: "Stylus" > # Axes limits data > X: 0 21600 > Y: 0 13500 > Z: 0 0 > Pressure: 0 2048 > Rotation: -900 899 > T. Pres: 0 0 > ################################### > # Adding a tablet device: Wacom Intuos PT M Pen eraser > Device Type: "XFreeEraser" > # Axes limits data > X: 0 21600 > Y: 0 13500 > Z: 0 0 > Pressure: 0 2048 > Rotation: 0 1 > T. Pres: 0 0 > libpng warning: iCCP: too many profiles > libpng warning: iCCP: too many profiles > libpng warning: iCCP: too many profiles > libpng warning: iCCP: too many profiles > Object::connect: No such signal QToolButton::triggered() > Object::connect: (sender name: 'bnRaise') > Object::connect: No such signal QToolButton::triggered() > Object::connect: (sender name: 'bnLower') > krita(3605)/KZip KZip::openArchive: Invalid ZIP file. Unexpected end of > file. > Could not open store on bundle > > "/home/britta/.kde4/share/apps/krita/bundles/essential_illustration_brushes_v3_extended_by_fox_orian-d1xs95k.bundle" > > krita(3605) KoResourceServer<T, Policy>::loadResources: Loading resource > > > "/home/britta/.kde4/share/apps/krita/bundles/essential_illustration_brushes_v3_extended_by_fox_orian-d1xs95k.bundle" > failed > Could not load META-INF/manifest.xml > krita(3605) KoResourceServer<T, Policy>::loadResources: Loading resource > > "/home/britta/.kde4/share/apps/krita/bundles/Wolthera_workspace-set.bundle" > failed > krita(3605)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned > initialize() D-Bus call failed: "No such object path > '/modules/ktimezoned'" > > krita(3605)/kdecore (K*TimeZone*): No time zone information obtained from > ktimezoned > WARNING: KisImageConfig: requested config synchronization from nonGUI > thread! Skipping... > WARNING: KisImageConfig: requested config synchronization from nonGUI > thread! Skipping... > WARNING: KisImageConfig: requested config synchronization from nonGUI > thread! Skipping... > > OpenGL version 1.1 or higher is present. > > OpenGL version 1.2 or higher is present. > > OpenGL version 1.3 or higher is present. > > OpenGL version 1.4 or higher is present. > > OpenGL version 1.5 or higher is present. > > OpenGL version 2.0 or higher is present. > > OpenGL version 2.1 or higher is present. > > OpenGL version 3.0 or higher is present. > > OpenGL version 3.1 or higher is present. > > OpenGL version 3.2 or higher is present. > > OpenGL version 3.3 or higher is present. > > OpenGL version 4.0 or higher is present. > > krita(3605)/koffice (lib komain) KoRuler::createGuideToolConnection: No > guides tool found, skipping connection > > krita(3605)/koffice (lib komain) KoRuler::createGuideToolConnection: No > guides tool found, skipping connection > > krita(3605) CanvasData::activateToolActions: "InteractionTool" : action > "object_order_raise" conflicts with canvas action "rotate_canvas_right" > shortcut: "Ctrl+]" > krita(3605) CanvasData::activateToolActions: "InteractionTool" : action > "object_order_lower" conflicts with canvas action "rotate_canvas_left" > shortcut: "Ctrl+[" > krita(3605) CanvasData::activateToolActions: "InteractionTool" : action > "object_order_raise" conflicts with canvas action "rotate_canvas_right" > shortcut: "Ctrl+]" > krita(3605) CanvasData::activateToolActions: "InteractionTool" : action > "object_order_lower" conflicts with canvas action "rotate_canvas_left" > shortcut: "Ctrl+[" > Segmentation fault > > On Sat, Mar 19, 2016 at 7:21 PM, Douglas via KDE Bugzilla < > bugzilla_noreply@kde.org> wrote: > > > https://bugs.kde.org/show_bug.cgi?id=346967 > > > > --- Comment #7 from Douglas <magick.crow@gmail.com> --- > > I can try. How do you get a backtrace from Krita? Also it is hard > because > > I can't cause the crash at will but it is still a problem. It crashed > > yesterday from color selection at 16 bit float color on the square color > > picker. > > > > On Sat, Mar 19, 2016 at 3:59 PM, Boudewijn Rempt via KDE Bugzilla < > > bugzilla_noreply@kde.org> wrote: > > > > > https://bugs.kde.org/show_bug.cgi?id=346967 > > > > > > Boudewijn Rempt <boud@valdyas.org> changed: > > > > > > What |Removed |Added > > > > > > > > > ---------------------------------------------------------------------------- > > > Resolution|--- |WAITINGFORINFO > > > Status|UNCONFIRMED |NEEDSINFO > > > > > > --- Comment #6 from Boudewijn Rempt <boud@valdyas.org> --- > > > Hi Douglas, > > > > > > If you can reproduce the bug on Linux, do you get a backtrace report > that > > > you > > > could add to the bug report? Since I cannot reproduce the issue, I > cannot > > > get a > > > backtrace and cannot fix it. > > > > > > -- > > > You are receiving this mail because: > > > You are on the CC list for the bug. > > > > > > > -- > > You are receiving this mail because: > > You are on the CC list for the bug. > > > > -- > You are receiving this mail because: > You are on the CC list for the bug. >
To get a backtrace if the crash dialog doesn't popup automatically, you need to start krita with gdb. In a terminal, type gdb krita press enter on the gdb prompt, type run Reproduce the crash, switch back to the terminal where gdb is running and type thread apply all bt and attach the full output here.
Created attachment 98013 [details] attachment-3911-0.html It will not fully start up with way. I get the intro window and a blank krita program window. (gdb) run The program being debugged has been started already. Start it from the beginning? (y or n) y Starting program: /usr/bin/krita warning: File "/lib64/libthread_db-1.0.so" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-loa d". warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available. Legacy integer arithmetics implementation [New LWP 4816] [New LWP 4817] [New LWP 4818] [New LWP 4819] [LWP 4818 exited] [New LWP 4820] [New LWP 4821] [New LWP 4822] [LWP 4822 exited] [LWP 4821 exited] [LWP 4819 exited] [LWP 4816 exited] [LWP 4817 exited] [New LWP 4823] [New LWP 4824] [LWP 4820 exited] libpng warning: iCCP: too many profiles libpng warning: iCCP: too many profiles libpng warning: iCCP: too many profiles libpng warning: iCCP: too many profiles [New LWP 4825] [New LWP 4826] Object::connect: No such signal QToolButton::triggered() Object::connect: (sender name: 'bnRaise') Object::connect: No such signal QToolButton::triggered() Object::connect: (sender name: 'bnLower') [New LWP 4827] [LWP 4827 exited] [New LWP 4828] Program received signal SIG33, Real-time event 33. [Switching to LWP 4825] 0x00007ffff0108e7f in pthread_cond_wait () from /lib64/libpthread.so.0 (gdb) thread apply all bt Thread 14 (LWP 4828): #0 0x00007fffef8b1d22 in ?? () from /lib64/libz.so.1 #1 0x00007fffef8b3a0d in inflate () from /lib64/libz.so.1 #2 0x00007ffff6080ab8 in KGzipFilter::uncompress() () from /usr/lib64/libkdecore.so.5 #3 0x00007ffff6082776 in KFilterDev::readData(char*, long long) () from /usr/lib64/libkdecore.so.5 #4 0x00007ffff5c03bf6 in QIODevice::read(char*, long long) () from /usr/lib64/qt4/libQtCore.so.4 #5 0x00007ffff5c04616 in QIODevice::readAll() () from /usr/lib64/qt4/libQtCore.so.4 #6 0x00007ffff612c7ff in KZipFileEntry::data() const () from /usr/lib64/libkdecore.so.5 #7 0x00007fffdab502a7 in ?? () from /usr/lib64/kde4/plugins/imageformats/kimg_kra.so #8 0x00007ffff67d488f in QImageReader::read(QImage*) () from /usr/lib64/qt4/libQtGui.so.4 #9 0x00007ffff67d4e58 in QImageReader::read() () from /usr/lib64/qt4/libQtGui.so.4 #10 0x00007ffff67c68e3 in QImage::load(QString const&, char const*) () from /usr/lib64/qt4/libQtGui.so.4 #11 0x00007ffff67c69fd in QImage::QImage(QString const&, char const*) () from /usr/lib64/qt4/libQtGui.so.4 #12 0x00007fffc977d81e in ?? () from /usr/lib64/kde4/kritaimagedocker.so #13 0x00007ffff5b7632f in ?? () from /usr/lib64/qt4/libQtCore.so.4 #14 0x00007ffff010351c in ?? () from /lib64/libpthread.so.0 #15 0x00007ffff52fb1ad in clone () from /lib64/libc.so.6 Thread 12 (LWP 4826): #0 0x00007ffff52f35a3 in select () from /lib64/libc.so.6 #1 0x00007ffff5ca0741 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timeval const*) () from /usr/lib64/qt4/libQtCore.so.4 #2 0x00007ffff5ca5e3c in QEventDispatcherUNIXPrivate::doSelect(QFlags<QEventLoop::ProcessEventsFlag>, timeval*) () from /usr/lib64/qt4/libQtCore.so.4 #3 0x00007ffff5ca62d3 in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #4 0x00007ffff5c74e51 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #5 0x00007ffff5c75165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #6 0x00007ffff5b73b19 in QThread::exec() () from /usr/lib64/qt4/libQtCore.so.4 #7 0x00007ffff5c567e3 in ?? () from /usr/lib64/qt4/libQtCore.so.4 #8 0x00007ffff5b7632f in ?? () from /usr/lib64/qt4/libQtCore.so.4 #9 0x00007ffff010351c in ?? () from /lib64/libpthread.so.0 #10 0x00007ffff52fb1ad in clone () from /lib64/libc.so.6 Thread 11 (LWP 4825): #0 0x00007ffff0108e7f in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x00007ffff5b76824 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/qt4/libQtCore.so.4 #2 0x00007ffff6ca4097 in ?? () from /usr/lib64/qt4/libQtGui.so.4 #3 0x00007ffff5b7632f in ?? () from /usr/lib64/qt4/libQtCore.so.4 #4 0x00007ffff010351c in ?? () from /lib64/libpthread.so.0 #5 0x00007ffff52fb1ad in clone () from /lib64/libc.so.6 ---Type <return> to continue, or q <return> to quit--- Thread 10 (LWP 4824): #0 0x00007ffff0108e7f in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x00007ffff5b76824 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/qt4/libQtCore.so.4 #2 0x00007ffff5b72b63 in QSemaphore::tryAcquire(int, int) () from /usr/lib64/qt4/libQtCore.so.4 #3 0x00007ffff29b79aa in KisTileDataSwapper::run() () from /usr/lib64/libkritaimage.so.14 #4 0x00007ffff5b7632f in ?? () from /usr/lib64/qt4/libQtCore.so.4 #5 0x00007ffff010351c in ?? () from /lib64/libpthread.so.0 #6 0x00007ffff52fb1ad in clone () from /lib64/libc.so.6 Thread 9 (LWP 4823): #0 0x00007ffff0108e7f in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x00007ffff5b76824 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/qt4/libQtCore.so.4 #2 0x00007ffff5b7275b in QSemaphore::acquire(int) () from /usr/lib64/qt4/libQtCore.so.4 #3 0x00007ffff299d19e in ?? () from /usr/lib64/libkritaimage.so.14 #4 0x00007ffff299d5bd in ?? () from /usr/lib64/libkritaimage.so.14 #5 0x00007ffff5b7632f in ?? () from /usr/lib64/qt4/libQtCore.so.4 #6 0x00007ffff010351c in ?? () from /lib64/libpthread.so.0 #7 0x00007ffff52fb1ad in clone () from /lib64/libc.so.6 Thread 1 (LWP 4815): #0 0x00007ffff0102e70 in ?? () from /lib64/libpthread.so.0 #1 0x00007ffff52c8a46 in setuid () from /lib64/libc.so.6 #2 0x00007fffea58fea4 in QCA::init(QCA::MemoryMode, int) () from /usr/lib64/libqca.so.2 #3 0x00007ffff1ca0816 in ?? () from /usr/lib64/libkoodf.so.14 #4 0x00007ffff1c86c32 in KoStore::createStore(QString const&, KoStore::Mode, QByteArray const&, KoStore::Backend, bool) () from /usr/lib64/libkoodf.so.14 #5 0x00007ffff786b9f3 in ?? () from /usr/lib64/libkritaui.so.14 #6 0x00007ffff7866cef in KisApplication::checkAutosaveFiles() () from /usr/lib64/libkritaui.so.14 #7 0x00007ffff786914c in KisApplication::start() () from /usr/lib64/libkritaui.so.14 #8 0x0000000000402770 in ?? () #9 0x00007ffff5226a94 in __libc_start_main () from /lib64/libc.so.6 #10 0x0000000000402ef9 in _start () On Mon, Mar 21, 2016 at 1:09 PM, Boudewijn Rempt via KDE Bugzilla < bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=346967 > > --- Comment #10 from Boudewijn Rempt <boud@valdyas.org> --- > To get a backtrace if the crash dialog doesn't popup automatically, you > need to > start krita with gdb. > > In a terminal, type > > gdb krita > > press enter > > on the gdb prompt, type run > > Reproduce the crash, switch back to the terminal where gdb is running and > type > > thread apply all bt > > and attach the full output here. > > -- > You are receiving this mail because: > You are on the CC list for the bug. >
Hi Douglas, I'm afraid that this still doesn't have the crash information I need :-( Make sure krita isn't running anymore when starting it in the debugger.
Created attachment 98400 [details] attachment-6268-0.html Glad you wrote back. I got the debugger working but I deleted your email about what to do by mistake. I could not find my bug report on the bug tracker (You might want to make that easier). So what do I need to do again? On Fri, Apr 15, 2016 at 8:36 AM, Boudewijn Rempt via KDE Bugzilla < bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=346967 > > --- Comment #12 from Boudewijn Rempt <boud@valdyas.org> --- > Hi Douglas, > > I'm afraid that this still doesn't have the crash information I need :-( > Make > sure krita isn't running anymore when starting it in the debugger. > > -- > You are receiving this mail because: > You are on the CC list for the bug. >
You don't need the mail, just click on the link for the bug, and there it is :-)
Created attachment 98401 [details] attachment-8442-0.html There are 56117 lines and it overflows the text buffer. How do I output it and send it to you? On Fri, Apr 15, 2016 at 8:58 AM, Boudewijn Rempt via KDE Bugzilla < bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=346967 > > --- Comment #14 from Boudewijn Rempt <boud@valdyas.org> --- > You don't need the mail, just click on the link for the bug, and there it > is > :-) > > -- > You are receiving this mail because: > You are on the CC list for the bug. >
You can go to the bugzilla web interface and add it as an attachement.
Created attachment 98403 [details] attachment-14143-0.html That is not the problem. How do I get it out of GDB? Can you pipe somehow? On Fri, Apr 15, 2016 at 9:30 AM, Boudewijn Rempt via KDE Bugzilla < bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=346967 > > --- Comment #16 from Boudewijn Rempt <boud@valdyas.org> --- > You can go to the bugzilla web interface and add it as an attachement. > > -- > You are receiving this mail because: > You are on the CC list for the bug. >
Two things. I got the dump and I found out why Krita will not start in the debugger. It fails to fully start up when it tries to load an autosave file. So no autosave files and it starts up just fine! Guess this should be a new bug report. http://www.pasteall.org/68156
Ah, this is the infamous recursive color selector bug that Dmitry fixed for 3.0.