[krita] [Bug 364850] (Qt 5.7) If any docker is in focus e.g. layer docker , canvas zoom function with mouse scrollwheel is gone. The contents of the dockers is scrolled instead of canvas zoom
https://bugs.kde.org/show_bug.cgi?id=364850 supaiku <supa...@protonmail.ch> changed: What|Removed |Added CC||supa...@protonmail.ch --- Comment #19 from supaiku <supa...@protonmail.ch> --- Can someone tell if this issue got fixed with Qt 5.9? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374562] Random crash when moving/transforming a layer
https://bugs.kde.org/show_bug.cgi?id=374562
--- Comment #12 from supaiku <supa...@protonmail.ch> ---
Hello Dmitry!
I tried it with your the new AppImage and it has gotten a lot harder to provoke
the crash... I'm not even sure if it's the same crash, but I could still crash
Krita by repeatedly pressing STRG+T and moving the mouse while occasionally
pressing B (Brush) and E (Erase) to draw when the Transform is in progress.
The console output until it crashed (the last line is German, but it says
segfault):
$ ./krita-3.1.3-alpha.1-x86_64.appimage
OpenGL Info
Vendor: Intel Open Source Technology Center
Renderer: Mesa DRI Intel(R) Haswell Desktop
Version: 3.0 Mesa 17.0.2
Shading language: 1.30
Requested format: QSurfaceFormat(version 3.0, options QFlags(0x4),
depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1,
alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior 2,
swapInterval 0, profile 2)
Current format:QSurfaceFormat(version 3.0, options QFlags(0x4),
depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8,
alphaBufferSize 0, stencilBufferSize 8, samples -1, swapBehavior 2,
swapInterval 0, profile 0)
Version: 3 . 0
Supports deprecated functions true
krita has opengl true
Setting XDG_DATA_DIRS
"/tmp/.mount_hy1bWf/usr/bin/../share:./share/:/usr/share:/usr/share:/usr/local/share"
Available translations QSet("is", "uz@cyrillic", "ja", "sk", "se", "oc", "fy",
"mk", "en_GB", "vi", "en_US", "ms", "cs", "uk", "de", "af", "zh_TW", "ca",
"th", "nl", "kk", "br", "gl", "zh_CN", "sv", "nn", "ta", "uz", "pt_BR", "xh",
"ne", "mr", "it", "cy", "ru", "ro", "ug", "eu", "hu", "ast", "fa", "el", "da",
"nb", "eo", "fi", "et", "ga", "lt", "pl", "hi", "fr", "ar", "sl", "es", "bg",
"hr", "be", "wa", "ia", "ca@valencia", "ko", "bs", "pa", "hne", "tg", "lv",
"sq", "tr", "nds", "mai", "km", "he", "pt")
Available domain translations QSet("is", "uz@cyrillic", "ja", "sk", "se", "oc",
"fy", "mk", "en_GB", "vi", "en_US", "ms", "cs", "uk", "de", "af", "zh_TW",
"ca", "th", "nl", "kk", "br", "gl", "zh_CN", "sv", "nn", "ta", "uz", "pt_BR",
"xh", "ne", "mr", "it", "cy", "ru", "ro", "ug", "eu", "hu", "ast", "fa", "el",
"da", "nb", "eo", "fi", "et", "ga", "lt", "pl", "hi", "fr", "ar", "sl", "es",
"bg", "hr", "be", "wa", "ia", "ca@valencia", "ko", "bs", "pa", "hne", "tg",
"lv", "sq", "tr", "nds", "mai", "km", "he", "pt")
Override language: ""
libpng warning: iCCP: too many profiles
libpng warning: iCCP: too many profiles
libpng warning: iCCP: too many profiles
libpng warning: iCCP: too many profiles
QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
libpng warning: iCCP: too many profiles
QLayout: Attempting to add QLayout "" to QWidget "KritaShape/KisToolLine",
which already has a layout
SAFE ASSERT (krita): "m_d->lastKnownValue.isNull() || result ==
m_d->lastKnownValue" in file
/krita-3.1.3-alpha.1/libs/flake/KoDerivedResourceConverter.cpp, line 70
SAFE ASSERT (krita): "m_d->lastKnownValue.isNull() || result ==
m_d->lastKnownValue" in file
/krita-3.1.3-alpha.1/libs/flake/KoDerivedResourceConverter.cpp, line 70
Speicherzugriffsfehler (Speicherabzug geschrieben)
But for me SAFE_ASSERT doesn't sounds like it would terminate the program,
right? If it helps I can compile the latest and attach gdb for a better stack
trace.
I also made a video performing the steps as mentioned above until it crashed:
https://mega.nz/#!S0R0iJDZ!37cilwpVWacefPmk3D4FZ1a5o8OelTo7eOgZZXruGys
It is important to go all out and at all cost to not wait for any operation to
finish! :p
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 371199] Dragging windows on my left screen causes them to jump down to the bottom
https://bugs.kde.org/show_bug.cgi?id=371199 supaiku <supa...@protonmail.ch> changed: What|Removed |Added CC||supa...@protonmail.ch --- Comment #15 from supaiku <supa...@protonmail.ch> --- >From my observation it does not happen when the window uses client side decoration. I tested it with Chromium with and without client-side decoration. When the Breeze decoration is enabled I experience the bug as reported. But when it's off I don't experience the issue anymore. So I tested it with Lollypop (GTK+ music player) and I can drag it without any problems as well. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374562] Random crash when moving/transforming a layer
https://bugs.kde.org/show_bug.cgi?id=374562 --- Comment #10 from supaiku <supa...@protonmail.ch> --- May be noteworthy, that it (subjectively) only happens when I'm transforming a Layer inside a Group Layer. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374562] Random crash when moving/transforming a layer
https://bugs.kde.org/show_bug.cgi?id=374562 --- Comment #9 from supaiku <supa...@protonmail.ch> --- Hey, I located another crash with a different stacktrace and I'm sure that's a completely different issue, but it's also related to Layer Transform. Whenever it happened, I was about to apply the transform by hitting enter. *** Error in `/home/supaiku/hacking/krita-install/bin/krita': malloc(): memory corruption (fast): 0x1f579cef *** === Backtrace: = /usr/lib/libc.so.6(+0x70c4b)[0x7fffec249c4b] /usr/lib/libc.so.6(+0x76fe6)[0x7fffec24ffe6] /usr/lib/libc.so.6(+0x79411)[0x7fffec252411] /usr/lib/libc.so.6(__libc_malloc+0x54)[0x7fffec253d44] /usr/lib/libQt5Core.so.5(_ZN11QMetaObject8activateEP7QObjectiiPPv+0x2a0)[0x7fffed0cd9b0] /home/supaiku/hacking/krita-install/bin/../lib64/libkritaimage.so.16(_ZN24KisQueuesProgressUpdater15sigStartTickingEv+0x29)[0x762fe111] /home/supaiku/hacking/krita-install/bin/../lib64/libkritaimage.so.16(_ZN24KisQueuesProgressUpdater14updateProgressEiRK7QString+0xf6)[0x761410a0] /home/supaiku/hacking/krita-install/bin/../lib64/libkritaimage.so.16(_ZN18KisUpdateScheduler14progressUpdateEv+0x11b)[0x7613e221] /home/supaiku/hacking/krita-install/bin/../lib64/libkritaimage.so.16(_ZN18KisUpdateScheduler13processQueuesEv+0x1b8)[0x7613f2ac] /home/supaiku/hacking/krita-install/bin/../lib64/libkritaimage.so.16(_ZN18KisUpdateScheduler9endStrokeE12QWeakPointerI9KisStrokeE+0x57)[0x7613eb3b] /home/supaiku/hacking/krita-install/bin/../lib64/libkritaimage.so.16(_ZN8KisImage9endStrokeE12QWeakPointerI9KisStrokeE+0x42)[0x7615e18e] /home/supaiku/hacking/krita-install/lib64/kritaplugins/kritatooltransform.so(+0x310d5)[0x7fffa43d70d5] /home/supaiku/hacking/krita-install/lib64/kritaplugins/kritatooltransform.so(+0x2fdea)[0x7fffa43d5dea] /home/supaiku/hacking/krita-install/lib64/kritaplugins/kritatooltransform.so(+0xca487)[0x7fffa4470487] /usr/lib/libQt5Core.so.5(_ZN11QMetaObject8activateEP7QObjectiiPPv+0x639)[0x7fffed0cdd49] /home/supaiku/hacking/krita-install/bin/../lib64/libkritaimage.so.16(_ZN8KisImage21sigStrokeEndRequestedEv+0x29)[0x762fac9d] /home/supaiku/hacking/krita-install/bin/../lib64/libkritaimage.so.16(_ZN8KisImage16requestStrokeEndEv+0x18)[0x7615e2ea] /home/supaiku/hacking/krita-install/bin/../lib64/libkritaui.so.16(+0x586422)[0x776e2422] /home/supaiku/hacking/krita-install/bin/../lib64/libkritaui.so.16(_ZN18KisShortcutMatcher30tryRunSingleActionShortcutImplIN2Qt3KeyE6QEventEEbT_PT0_RK4QSetIS2_E+0x1a4)[0x776eb2fc] /home/supaiku/hacking/krita-install/bin/../lib64/libkritaui.so.16(_ZN18KisShortcutMatcher10keyPressedEN2Qt3KeyE+0x5f)[0x776e9593] /home/supaiku/hacking/krita-install/bin/../lib64/libkritaui.so.16(_ZN15KisInputManager15eventFilterImplEP6QEvent+0x2f4)[0x776d58d6] /home/supaiku/hacking/krita-install/bin/../lib64/libkritaui.so.16(_ZN15KisInputManager11eventFilterEP7QObjectP6QEvent+0x1da)[0x776d55e0] [New Thread 0x7fff8574f700 (LWP 26970)] /usr/lib/libQt5Core.so.5(_ZN23QCoreApplicationPrivate29sendThroughObjectEventFiltersEP7QObjectP6QEvent+0x111)[0x7fffed0a21a1] /usr/lib/libQt5Widgets.so.5(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x75)[0x7fffedf88325] /usr/lib/libQt5Widgets.so.5(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x1c2e)[0x7fffedf9152e] [New Thread 0x7fff79ffd700 (LWP 26971)] /home/supaiku/hacking/krita-install/bin/../lib64/libkritaui.so.16(_ZN14KisApplication6notifyEP7QObjectP6QEvent+0x45)[0x7776cb11] /usr/lib/libQt5Core.so.5(_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent+0x110)[0x7fffed0a2440] /usr/lib/libQt5Widgets.so.5(+0x1b7e1b)[0x7fffedfece1b] /usr/lib/libQt5Widgets.so.5(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x9c)[0x7fffedf8834c] /usr/lib/libQt5Widgets.so.5(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x261)[0x7fffedf8fb61] /home/supaiku/hacking/krita-install/bin/../lib64/libkritaui.so.16(_ZN14KisApplication6notifyEP7QObjectP6QEvent+0x45)[0x7776cb11] /usr/lib/libQt5Core.so.5(_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent+0x110)[0x7fffed0a2440] /usr/lib/libQt5Gui.so.5(_ZN22QGuiApplicationPrivate15processKeyEventEPN29QWindowSystemInterfacePrivate8KeyEventE+0xe8)[0x7fffed5ec4b8] /usr/lib/libQt5Gui.so.5(_ZN22QGuiApplicationPrivate24processWindowSystemEventEPN29QWindowSystemInterfacePrivate17WindowSystemEventE+0x115)[0x7fffed5f18a5] /usr/lib/libQt5Gui.so.5(_ZN29QWindowSystemInterfacePrivate24processWindowSystemEventEPNS_17WindowSystemEventE+0x45)[0x7fffed5ce2b5] /usr/lib/libQt5Gui.so.5(_ZN22QWindowSystemInterface19handleShortcutEventEP7QWindowmi6QFlagsIN2Qt16KeyboardModifierEEjjjRK7QStringbt+0x128)[0x7fffed5d1568] /usr/lib/libQt5Gui.so.5(_ZN22QGuiApplicationPrivate15processKeyEventEPN29QWindowSystemInterfacePrivate8KeyEventE+0x134)[0x7fffed5ec504] /usr/lib/libQt5Gui.so.5(_ZN22QGuiApplicationPrivate24processWindowSystemEventEPN29QWindowSystemInterfacePrivate17WindowSystemEventE+0x115)[0x7fffed5f18a5] /usr/lib/libQt5Gu
[krita] [Bug 374562] Random crash when moving/transforming a layer
https://bugs.kde.org/show_bug.cgi?id=374562 --- Comment #8 from supaiku <supa...@protonmail.ch> --- I forgot to add, that I got a lot of prints of: krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to endPrimaryAction while being mode 0 ! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374562] Random crash when moving/transforming a layer
https://bugs.kde.org/show_bug.cgi?id=374562 --- Comment #7 from supaiku <supa...@protonmail.ch> --- I found a reliable way to provoke a crash. Today it happened again on the client mentioned above, while using the transform tool, BUT this time someone could tell me exactly what was pressed. He was using the transform tool and pressed B. So I fired up Krita on my Arch Linux and played on an empty canvas with the tranform tool. 1. STRG + T 2. Rotate a bit... 3. Press B / E randomly 4. Alternate between 3. and 4. 5. Eventually Krita closes. I could reproduce it again and again. So I compiled Krita from source and attached gdb. (Note: I'm using a different graphics driver than the client, but I guess the cause is the same) Here's the stacktrace: Thread 1 "krita" received signal SIGSEGV, Segmentation fault. 0x7fffec250258 in malloc_consolidate () from /usr/lib/libc.so.6 (gdb) bt #0 0x7fffec250258 in malloc_consolidate () from /usr/lib/libc.so.6 #1 0x7fffec250e40 in _int_free () from /usr/lib/libc.so.6 #2 0x7fffd6c5cdc4 in ?? () from /usr/lib/libdrm_intel.so.1 #3 0x7fffd6c5d01e in ?? () from /usr/lib/libdrm_intel.so.1 #4 0x7fffd724b3c9 in ?? () from /usr/lib/xorg/modules/dri/i965_dri.so #5 0x7fffd6fbe3ac in ?? () from /usr/lib/xorg/modules/dri/i965_dri.so #6 0x775d7194 in Sync::syncStatus (syncObject=0x1ca63bb0) at /home/supaiku/hacking/krita-git/libs/ui/opengl/kis_opengl_canvas2_p.h:109 #7 0x775d8d2e in KisOpenGLCanvas2::isBusy (this=0x18c516f0) at /home/supaiku/hacking/krita-git/libs/ui/opengl/kis_opengl_canvas2.cpp:423 #8 0x773adc5c in KisCanvas2::slotDoCanvasUpdate (this=0x18c26008) at /home/supaiku/hacking/krita-git/libs/ui/canvas/kis_canvas2.cpp:664 #9 0x7783f39f in KisCanvas2::qt_static_metacall (_o=0x18c26008, _c=QMetaObject::InvokeMetaMethod, _id=23, _a=0x7fffd240) at /home/supaiku/hacking/build-krita-git-Desktop-Debug/libs/ui/kritaui_automoc.dir/moc_kis_canvas2_LX4NUNHD4DUJWF.cpp:202 #10 0x7fffed0cdd49 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #11 0x762fe72f in KisSignalCompressor::timeout (this=0x18c57320) at /home/supaiku/hacking/build-krita-git-Desktop-Debug/libs/image/kritaimage_automoc.dir/moc_kis_signal_com_NQZINSG4MKTJFA.cpp:144 #12 0x7617441b in KisSignalCompressor::start (this=0x18c57320) at /home/supaiku/hacking/krita-git/libs/image/kis_signal_compressor.cpp:63 #13 0x773ade32 in KisCanvas2::updateCanvasWidgetImpl (this=0x18c26008, rc=...) at /home/supaiku/hacking/krita-git/libs/ui/canvas/kis_canvas2.cpp:687 #14 0x773ade61 in KisCanvas2::updateCanvas (this=0x18c26008) at /home/supaiku/hacking/krita-git/libs/ui/canvas/kis_canvas2.cpp:692 #15 0x7fff9c3e2d61 in KisToolTransform::deactivate (this=0x18f0b2f0) at /home/supaiku/hacking/krita-git/plugins/tools/tool_transform2/kis_tool_transform.cc:825 #16 0x75191670 in KoToolManager::Private::disconnectActiveTool (this=0x16e84110) at /home/supaiku/hacking/krita-git/libs/flake/KoToolManager.cpp:608 #17 0x751918bc in KoToolManager::Private::switchTool (this=0x16e84110, tool=0x18d65430, temporary=false) at /home/supaiku/hacking/krita-git/libs/flake/KoToolManager.cpp:635 #18 0x75191b1d in KoToolManager::Private::switchTool (this=0x16e84110, id=..., temporary=false) at /home/supaiku/hacking/krita-git/libs/flake/KoToolManager.cpp:663 #19 0x7518f60b in KoToolManager::switchToolRequested (this=0x754e70d0 <_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder>, id=...) at /home/supaiku/hacking/krita-git/libs/flake/KoToolManager.cpp:316 #20 0x7518e51f in ShortcutToolAction::actionTriggered (this=0x190a4a90) at /home/supaiku/hacking/krita-git/libs/flake/KoToolManager_p.cpp:262 #21 0x7525629f in ShortcutToolAction::qt_static_metacall (_o=0x190a4a90, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffd610) at /home/supaiku/hacking/build-krita-git-Desktop-Debug/libs/flake/kritaflake_automoc.dir/moc_KoToolManager__CHRU4NQGN3E7OY.cpp:320 #22 0x7fffed0cdd49 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #23 0x7fffedf81c92 in QAction::triggered(bool) () from /usr/lib/libQt5Widgets.so.5 #24 0x7fffedf843f0 in QAction::activate(QAction::ActionEvent) () from /usr/lib/libQt5Widgets.so.5 #25 0x7fffedf84d6c in QAction::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #26 0x7fffedf8834c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #27 0x7fffedf8fb61 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #28 0x7776cb11 in KisApplication::notify (this=0x7fffdf30, receiver=0x190a4a90, event=0x7fffd9d0) at /home/supaiku/hacking/krita-git/libs/ui/KisApplication.cpp:532 #29 0x7fffed0a2440 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/l
[krita] [Bug 374562] Random crash when moving/transforming a layer
https://bugs.kde.org/show_bug.cgi?id=374562 --- Comment #5 from supaiku <supa...@protonmail.ch> --- Hi Boudewijn Rempt, I already ditched 16.04 in favor of 16.10 and the lime ppa. It is - subjectively - much more stable. Though some occasional crashes are still there. Same question as z-uo: Where are the debug symbols? The ppa only contains krita and krita-testing. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374562] Random crash when moving/transforming a layer
https://bugs.kde.org/show_bug.cgi?id=374562 --- Comment #1 from supaiku <supa...@protonmail.ch> --- I forgot to mention that the typical workspace has 100+ layers and uses up to 1GB+ memory. The memory of the workstation is (according to memtest) not faulty. The graphics card in use is a Radeon R7 using the open source driver. In the last hour there were some more crashes, dmesg alternates between these outputs... krita[14619] general protection ip:7f88ee9755a1 sp:7ffc2c5416a0 error:0 in libc-2.23.so[7f88ee8f7000+1c] or krita[11677]: segfault at 50 ip 7f528bd129b2 sp 7ffd7edda310 error 4 in libkritaimage.so.16.0.0[7f528bbf7000+501000] or the one from first post: krita[9200]: segfault at 1000f ip 7ff4db6d046f sp 7ffcb7bc7cc0 error 4 in libc-2.23.so[7ff4db64f000+1c] Any ideas? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374562] New: Random crash when moving/transforming a layer
https://bugs.kde.org/show_bug.cgi?id=374562 Bug ID: 374562 Summary: Random crash when moving/transforming a layer Product: krita Version: 3.1.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: supa...@protonmail.ch Target Milestone: --- On a client Krita crashes several times a day, seemingly random. But most often related to Move/Transform Layer operations. On Ubuntu 16.04 LTS using the Krita 3.1.1 Snap. I don't know how a Snap application is supposed to be debugged or where it logs to. dmesg only reports: krita[9200]: segfault at 1000f ip 7ff4db6d046f sp 7ffcb7bc7cc0 error 4 in libc-2.23.so[7ff4db64f000+1c] I know that's pretty useless, but maybe it's familiar for someone? Any ideas how to track down the cause? Maybe I should let the client use a source build Krita... -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365678] Massive flicker and repaint problems with Neon 5.7 on remote X
https://bugs.kde.org/show_bug.cgi?id=365678 supaiku <supa...@protonmail.ch> changed: What|Removed |Added CC||supa...@protonmail.ch --- Comment #18 from supaiku <supa...@protonmail.ch> --- Any news? I'm experiencing it on my laptop as well and see the same output as Jan-Marek Glogowski. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369492] Krita config is lost on snap update
https://bugs.kde.org/show_bug.cgi?id=369492 --- Comment #2 from supaiku <supa...@protonmail.ch> --- Don't know how to edit, but anyway. Whenever the snap is updated, Krita loads from a new ~/snap/something/.local/share/krita directory. It's not really user-friendly and quiet annoying to have to copy the old one to the new location. I don't know if Snap can be configured to share the configs between updates. But the way it is now, it's totally broken from a user perspective. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369492] Krita config is lost on snap update
https://bugs.kde.org/show_bug.cgi?id=369492 supaiku <supa...@protonmail.ch> changed: What|Removed |Added Version|unspecified |3.0.1 --- Comment #1 from supaiku <supa...@protonmail.ch> --- Damn, hit enter too early. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369492] New: Krita config is lost on snap updates
https://bugs.kde.org/show_bug.cgi?id=369492 Bug ID: 369492 Summary: Krita config is lost on snap updates Product: krita Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: supa...@protonmail.ch Whenever the Krita snap is updated, Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369492] Krita config is lost on snap update
https://bugs.kde.org/show_bug.cgi?id=369492 supaiku <supa...@protonmail.ch> changed: What|Removed |Added Summary|Krita config is lost on |Krita config is lost on |snap updates|snap update -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 367685] New: Toggle application launcher on meta key
https://bugs.kde.org/show_bug.cgi?id=367685 Bug ID: 367685 Summary: Toggle application launcher on meta key Product: kwin Version: git master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: supa...@protonmail.ch It's finally there - the meta key support! Thanks for that, Martin. I ran the Neon unstable git iso from 21.08.16 and noticed that the application launcher only opens when the meta key is pressed, but doesn't close when pressed again. This behaviour is a bit unexpected. Reproducible: Always Steps to Reproduce: 1. Press meta key 2. Application launcher opens 3. Press again Actual Results: It stays open. Expected Results: The application launcher should toggle. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 364927] New: Add default shortcuts for window resizing
https://bugs.kde.org/show_bug.cgi?id=364927 Bug ID: 364927 Summary: Add default shortcuts for window resizing Product: kwin Version: 5.6.95 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: supa...@protonmail.ch Many popular Desktops like GNOME and Windows have shortcuts to resize the active window. Most of the time seen in the form of: META + ARROW to move the window and resize it. https://help.gnome.org/users/gnome-help/stable/shell-keyboard-shortcuts.html.en I know KWin can do all of this, but no shortcuts are mapped out of the box. So why not adopt this behaviour and make it default. Something like: META + Left/Right -> Moves the active window to the left/right (analog to mouse dragging) META + Up -> Maximize the active window That's the most crucial I think. My suggestion clashes with the window zoom, so either break it or instead of META let's use something like CTRL + ALT + Arrow. Why bother? Because all other Desktops spoiled me and I think many users would appreciate it. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 357110] New: krunner polutes log
https://bugs.kde.org/show_bug.cgi?id=357110 Bug ID: 357110 Summary: krunner polutes log Product: krunner Version: 5.5.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: m...@vhanda.in Reporter: supa...@protonmail.ch Everything typed in krunner is logged. This quickly escalates and does not yield any useful information. It's literally spam. Reproducible: Always Steps to Reproduce: 1. journalctl -f 2. Alt + F2 3. Start typing Actual Results: Krunner is logging like crazy. Expected Results: Don't log at all if not debug compiled. -- You are receiving this mail because: You are watching all bug changes.
