[lattedock] [Bug 410629] Folder view doesn't work when docked vertically.
https://bugs.kde.org/show_bug.cgi?id=410629 --- Comment #5 from basse --- well what do you know, that (whatever it was) worked. thank you. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 410629] Folder view doesn't work when docked vertically.
https://bugs.kde.org/show_bug.cgi?id=410629 --- Comment #1 from basse --- Created attachment 121953 --> https://bugs.kde.org/attachment.cgi?id=121953=edit horizontal image -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 410629] New: Folder view doesn't work when docked vertically.
https://bugs.kde.org/show_bug.cgi?id=410629 Bug ID: 410629 Summary: Folder view doesn't work when docked vertically. Product: lattedock Version: 0.9.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: bastian.salm...@gmail.com Target Milestone: --- Created attachment 121952 --> https://bugs.kde.org/attachment.cgi?id=121952=edit vertical image After updating to 0.9.1 folder views on dock stopped working if dock is placed vertically, (on left for example). Tooltip says the icon is there, but it's not visible, and the view doesn't open. Works fine if I move the dock to bottom or top. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.04 KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.60.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 397669] Broken behaviour NerdFont glyphs
https://bugs.kde.org/show_bug.cgi?id=397669 --- Comment #18 from basse --- (In reply to Wolfgang Bauer from comment #17) > (In reply to basse from comment #14) > > I just upgraded to Kubuntu 19.04, and noticed the font rendering issue too. > > > > (see attachement konsolevim.png) Konsole version is 18.12.3 > > The mentioned fix is in *konsole* 19.04(.0), not in Kubuntu 19.04. > > According to your comment Kubuntu 19.04 apparently ships with konsole > 18.12.3, so you'd need to ask them to backport it. ah.. of course :) sorry about that. well, I can wait.. it will be in backports eventually. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 397669] Broken behaviour NerdFont glyphs
https://bugs.kde.org/show_bug.cgi?id=397669 basse changed: What|Removed |Added CC||bastian.salm...@gmail.com --- Comment #14 from basse --- Created attachment 119586 --> https://bugs.kde.org/attachment.cgi?id=119586=edit konsole vim I just upgraded to Kubuntu 19.04, and noticed the font rendering issue too. (see attachement konsolevim.png) Konsole version is 18.12.3 before upgrade, these glyphs were rendering as a whole, but slightly smaller, and positioned too "high" .. now, position and size looks alright, but it's cut of. (Font is "Hack"), program in screenshot Vim (SpaceVim) .b -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389543] kwin / compositor crash when alt-tabbing
https://bugs.kde.org/show_bug.cgi?id=389543 --- Comment #1 from basse <bastian.salm...@gmail.com> --- a little more information, this has been starting to in 17.10... I am not sure exactly on which version of plasma, but before 17.10 it was ok. also, I am running dual monitor setup, but this happens also when I'm using only one monitor. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389543] New: kwin / compositor crash when alt-tabbing
https://bugs.kde.org/show_bug.cgi?id=389543 Bug ID: 389543 Summary: kwin / compositor crash when alt-tabbing Product: kwin Version: 5.11.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: bastian.salm...@gmail.com Target Milestone: --- Application: kwin_x11 (5.11.5) Qt Version: 5.9.1 Frameworks Version: 5.41.0 Operating System: Linux 4.13.0-32-generic x86_64 Distribution: Ubuntu 17.10 -- Information about the crash: - What I was doing when the application crashed: browsing in google chrome, and hit alt-tab to switch to another application. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1b8596b940 (LWP 1412))] Thread 5 (Thread 0x7f1b5292e700 (LWP 17957)): #0 0x7f1b8291ab25 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f1b828c2e3a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f1b826e23ca in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f1b826e729d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f1b7e3017fc in start_thread (arg=0x7f1b5292e700) at pthread_create.c:465 #5 0x7f1b85304b5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f1b535ef700 (LWP 1565)): #0 0x7f1b7e308072 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f1b81b5afb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f1b7e308072 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f1b81b5af68, cond=0x7f1b81b5af90) at pthread_cond_wait.c:502 #2 0x7f1b7e308072 in __pthread_cond_wait (cond=0x7f1b81b5af90, mutex=0x7f1b81b5af68) at pthread_cond_wait.c:655 #3 0x7f1b81866bd4 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f1b81866c19 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f1b7e3017fc in start_thread (arg=0x7f1b535ef700) at pthread_create.c:465 #6 0x7f1b85304b5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f1b61b01700 (LWP 1523)): #0 0x7f1b852f8a4b in __GI_ppoll (fds=0x7f1b58000d38, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f1b82919151 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f1b8291a86e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f1b828c2e3a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f1b826e23ca in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f1b7ce09f45 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f1b826e729d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f1b7e3017fc in start_thread (arg=0x7f1b61b01700) at pthread_create.c:465 #8 0x7f1b85304b5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f1b63b68700 (LWP 1427)): #0 0x7f1b8291a7b5 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f1b828c2e3a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f1b826e23ca in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f1b7bfcae45 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #4 0x7f1b826e729d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f1b7e3017fc in start_thread (arg=0x7f1b63b68700) at pthread_create.c:465 #6 0x7f1b85304b5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f1b8596b940 (LWP 1412)): [KCrash Handler] #6 0x7f1b74794bd0 in () at /usr/lib/nvidia-384/libnvidia-glcore.so.384.111 #7 0x7f1b7485b063 in () at /usr/lib/nvidia-384/libnvidia-glcore.so.384.111 #8 0x7f1b7485f864 in () at /usr/lib/nvidia-384/libnvidia-glcore.so.384.111 #9 0x7f1b74868a84 in () at /usr/lib/nvidia-384/libnvidia-glcore.so.384.111 #10 0x7f1b74427a5e in () at /usr/lib/nvidia-384/libnvidia-glcore.so.384.111 #11 0x7f1b7d4b231f in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x7f1b7d4b3555 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #13 0x7f1b7d4b8cac in QSGBatchRenderer::Renderer::render() () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #14 0x7f1b7d4a966d in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #15
[krita] [Bug 387477] New: Crash on startup
https://bugs.kde.org/show_bug.cgi?id=387477 Bug ID: 387477 Summary: Crash on startup Product: krita Version: git master Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: bastian.salm...@gmail.com Target Milestone: --- Created attachment 109134 --> https://bugs.kde.org/attachment.cgi?id=109134=edit gdb backtrace log Since yesterday self compiled Krita has been crashing upon startup.. Today I decided to clean my sources if that's the problem, so I cloned the whole repo again.. compiled fine, but same thing when running it. Kubuntu 17.10, Nvidia 840m (384.90 driver) I attached backtrace. .b -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 387180] Saving a new copy of a brush doesn't keep tags
https://bugs.kde.org/show_bug.cgi?id=387180 basse <bastian.salm...@gmail.com> changed: What|Removed |Added Summary|Saving a new copy of a |Saving a new copy of a |brush doens't keep tags |brush doesn't keep tags -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 387180] New: Saving a new copy of a brush doens't keep tags
https://bugs.kde.org/show_bug.cgi?id=387180 Bug ID: 387180 Summary: Saving a new copy of a brush doens't keep tags Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: bastian.salm...@gmail.com Target Milestone: --- If you use the save new brush dialog, and save over the old one you modified, it correctly seems to replace the old one in preset dialog, but you loose all the tags you assigned before. .b -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376580] crash after working little while
https://bugs.kde.org/show_bug.cgi?id=376580 --- Comment #10 from basse <bastian.salm...@gmail.com> --- (In reply to Boudewijn Rempt from comment #9) > Could you please check whether this fixes it? It's just a hunch, but could > cause the backtrace. Though it's still weird I don't get it. I updated and recompiled.. still happening. must be something in my build environment then.. I'm using this to build it: cmake ~/kf5/src/krita -DCMAKE_INSTALL_PREFIX=~/kf5/inst -DCMAKE_BUILD_TYPE=RelWithDebInfo -DBUILD_TESTING=OFF then I run it with this: export XDG_DATA_DIRS=~/kf5/inst/share:$XDG_DATA_DIRS ~/kf5/inst/bin/krita nothing too special... I'm running it on Kubuntu 16.10, Qt 5.6.1.. maybe I try to just clean everything out, download whole new git and let's see.. .b -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376580] crash after working little while
https://bugs.kde.org/show_bug.cgi?id=376580 --- Comment #6 from basse <bastian.salm...@gmail.com> --- Created attachment 104960 --> https://bugs.kde.org/attachment.cgi?id=104960=edit traceback -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376580] crash after working little while
https://bugs.kde.org/show_bug.cgi?id=376580 --- Comment #5 from basse <bastian.salm...@gmail.com> --- I did a "make clean" and "make" ... still getting the crash. attaching latest trace. anything else I could provide you with? .b -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376580] crash after working little while
https://bugs.kde.org/show_bug.cgi?id=376580 --- Comment #4 from basse <bastian.salm...@gmail.com> --- Hi.. sorry haven't noticed the comment until now.. and yes I build Krita myself. so what is your recommendation? "make clean" ? here's one line again.. from console.. QMetaType::registerType: Binary compatibility break -- Size mismatch for type 'KisGridConfig' [1034]. Previously registered size 84, now registering size 68. KCrash: crashing... crashRecursionCounter = 2 so I guess it's still the same.. .b -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376580] crash after working little while
https://bugs.kde.org/show_bug.cgi?id=376580 --- Comment #2 from basse <bastian.salm...@gmail.com> --- couple of more crashes just now.. this time I was testing how the whole perspective assistant thing works.. I set up some assistant lines and tried to figure out how to move the points after I had placed them... so I wasn't even doing much... and then just noticed Krita is not responsive, and down we went again. backtrace, well looks to be the same, so I'm not posting. what is grid-config? .b -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376580] New: crash after working little while
https://bugs.kde.org/show_bug.cgi?id=376580 Bug ID: 376580 Summary: crash after working little while Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: bastian.salm...@gmail.com Target Milestone: --- Created attachment 104073 --> https://bugs.kde.org/attachment.cgi?id=104073=edit gdb bt full lately I've ran into issue Krita crashing without no apparent reason. still trying to figure out what it is exactly, but sofar seems quite random.. I decided to post a backtrace of one occurance.. if it would magicallly just show what happened :) I opened Krita. Created new document. Painted a bit.. erased canvas, painted more.. switched presets... tried mirror mode.. and bam! mirror mode worked on other run just fine. so it's not necessarily that. I'm running Krita compiled from git .. Kubuntu 16.10, Nvidia 367 drivers .b -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 277502] All versions of version set always displayed in Album view
https://bugs.kde.org/show_bug.cgi?id=277502 basse <bastian.salm...@gmail.com> changed: What|Removed |Added CC||bastian.salm...@gmail.com --- Comment #15 from basse <bastian.salm...@gmail.com> --- just updated to Digikam 5.4.0 and this problem still exists. if in image editor I set click "save" just _v1 version is created/updated, and original image is preserved, and hidden in thumbnail view.. so this works. but if I click "save version", a new _v? version is saved, and version tab looks updated nicely.. but, in thumbnail view all versions are always displayed. clicking the little show/hides in version tab doesn't seem to do anything when there are more than one _v. I'm on Kubuntu, running ppa version, but I tried the appmage too with same results. 1 .b -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364174] crash on exit
https://bugs.kde.org/show_bug.cgi?id=364174 --- Comment #3 from basse <bastian.salm...@gmail.com> --- Created attachment 99480 --> https://bugs.kde.org/attachment.cgi?id=99480=edit cmakecache -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363296] Creating animated brush tip crashes Krita
https://bugs.kde.org/show_bug.cgi?id=363296 --- Comment #2 from basse <bastian.salm...@gmail.com> --- Created attachment 99085 --> https://bugs.kde.org/attachment.cgi?id=99085=edit file from which I tried to make the brush out of it's badly drawn popcorn ;) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363296] Creating animated brush tip crashes Krita
https://bugs.kde.org/show_bug.cgi?id=363296 --- Comment #1 from basse <bastian.salm...@gmail.com> --- Created attachment 99084 --> https://bugs.kde.org/attachment.cgi?id=99084=edit backtrace -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363296] Creating animated brush tip crashes Krita
https://bugs.kde.org/show_bug.cgi?id=363296 basse <bastian.salm...@gmail.com> changed: What|Removed |Added Version|unspecified |git master -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363296] New: Creating animated brush tip crashes Krita
https://bugs.kde.org/show_bug.cgi?id=363296 Bug ID: 363296 Summary: Creating animated brush tip crashes Krita Product: krita Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: bastian.salm...@gmail.com Application: krita () Qt Version: 5.5.1 Operating System: Linux 4.4.0-22-generic x86_64 Distribution: Ubuntu 16.04 LTS -- Information about the crash: - What I was doing when the application crashed: I'm trying to create an animated brush tip that I could spray around (image hose like, big spacing). So I have my image with brush frames in separate layers, I go to brush settings -> tip -> predefined and hit "Stamp". I give it a name, select "Animated" from "Style" and "Random" from "Selection", and when I hit OK I get a crash. couple of times before I managed to make krita save it, but there are some strange things in those too.. like Random isn't really random, when you first click it's always the same image from the sequence. and if I go and paint away with long spacing sometimes two images end up on top of each other. but, now, it's just crashing. I attach my image, brush and backtrace. .b The crash can be reproduced every time. -- Backtrace: Application: krita (krita), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7d2ab1b8c0 (LWP 17010))] Thread 4 (Thread 0x7f7cf4f67700 (LWP 17012)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f7d28999aeb in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f7d2899271b in QSemaphore::acquire(int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f7d26515b9e in KisTileDataPooler::waitForWork (this=0x7f7d269a8400 <(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>) at /home/basse/kf5/src/krita/libs/image/tiles3/kis_tile_data_pooler.cc:165 #4 0x7f7d26516351 in KisTileDataPooler::run (this=0x7f7d269a8400 <(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>) at /home/basse/kf5/src/krita/libs/image/tiles3/kis_tile_data_pooler.cc:187 #5 0x7f7d2899884e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f7d230ad6fa in start_thread (arg=0x7f7cf4f67700) at pthread_create.c:333 #7 0x7f7d28098b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f7cf4766700 (LWP 17013)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f7d28999aeb in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f7d289929c6 in QSemaphore::tryAcquire(int, int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f7d26531163 in KisTileDataSwapper::waitForWork (this=) at /home/basse/kf5/src/krita/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:86 #4 0x7f7d2653135a in KisTileDataSwapper::run (this=0x7f7d269a8440 <(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder+64>) at /home/basse/kf5/src/krita/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:92 #5 0x7f7d2899884e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f7d230ad6fa in start_thread (arg=0x7f7cf4766700) at pthread_create.c:333 #7 0x7f7d28098b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f7cf3f65700 (LWP 17014)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f7d28999aeb in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f7d2969f72a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #3 0x7f7d2899884e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f7d230ad6fa in start_thread (arg=0x7f7cf3f65700) at pthread_create.c:333 #5 0x7f7d28098b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f7d2ab1b8c0 (LWP 17010)): [KCrash Handler] #6 KisCustomBrushWidget::slotAddPredefined (this=0x16647a50) at /home/basse/kf5/src/krita/plugins/paintops/libpaintop/kis_custom_brush_widget.cpp:149 #7 0x7f7d0677d395 in KisCustomBrushWidget::qt_static_metacall (_o=, _c=, _id=, _a=) at /home/basse/kf5/build/krita/plugins/paintops/libpaintop/moc_kis_custom_brush_widget.cpp:164 #8 0x7f7d28ba7fca in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f7d28ba7fca in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linu
[krita] [Bug 361911] Overriding hotkeys won't work (conflict of new hotkey with old one)
https://bugs.kde.org/show_bug.cgi?id=361911 basse <bastian.salm...@gmail.com> changed: What|Removed |Added CC||bastian.salm...@gmail.com --- Comment #1 from basse <bastian.salm...@gmail.com> --- confirmed.. setting to "None" doesn't work. and trying to set to key that already is used doesn't work. furthermore, I set Crop to "shift-c" which works fine, but then I cannot set it back to default because Krita complains that "c" is already used with curve segment... so now I'm stuck with shift-c :) .b -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362076] New: Advanced and Artistic color pickers slow / cpu hungry when used with mouse/wacom
https://bugs.kde.org/show_bug.cgi?id=362076 Bug ID: 362076 Summary: Advanced and Artistic color pickers slow / cpu hungry when used with mouse/wacom Product: krita Version: git master Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: bastian.salm...@gmail.com When using (lmb + drag around) advanced/artistic color selectors with mouse or wacom (usb connected) the update is very slow and the pointer on color lags behind. faster you move slower it gets. also my fans start to blow and cpu usage goes to 90-100%. when used with laptops touchpad it works just fine, no slowdowns. also, the popup palette that comes when you right click on canvas, color selector there works fine and fast always. Reproducible: Always Steps to Reproduce: 1. click and drag around in color selector dialog 2. 3. Actual Results: slow Expected Results: fast with Krita 2.9 this worked normally. so it's a bug introduced with qt5. my system specs: Kubuntu 15.10 GeForce 840M/PCIe/SSE2, (3.52 drivers) Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362066] New: Tabs visible in canvas-only mode, no way to hide those?
https://bugs.kde.org/show_bug.cgi?id=362066 Bug ID: 362066 Summary: Tabs visible in canvas-only mode, no way to hide those? Product: krita Version: git master Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: usability Assignee: krita-bugs-n...@kde.org Reporter: bastian.salm...@gmail.com There is no way to hide image tabs when in Canvas-Only mode. Would be great if that option was added in Krita Canvas-Only settings. .b Reproducible: Always Steps to Reproduce: 1. hit 2. 3. Actual Results: other ui elements will be hidden, tabs still visible Expected Results: tabs would be hidden too configuration doesn't have option for tabs -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362064] New: Saving as template creates only .desktop
https://bugs.kde.org/show_bug.cgi?id=362064 Bug ID: 362064 Summary: Saving as template creates only .desktop Product: krita Version: git master Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: bastian.salm...@gmail.com when saving image as template Krita creates .desktop file in ~/.local/share/krita/templates/[groupname]/ but forgets to save the actual .kra file into .source subdirectory. so you have to manually save it there or otherwise Krita will complain missing .kra when using the template. .b Reproducible: Always Steps to Reproduce: 1. create image 2. save as template 3. create new image using this new template Actual Results: error dialog pops up complaining about missing .kra file for the template Expected Results: no errors, just create new image with your template setup here's the desktop entry that was created... but no kra anywhere. [Desktop Entry] Icon=.icon/A4Paperi.png Name=A4 Paperi Type=Link URL[$e]=.source/A4Paperi.kra X-KDE-Hidden=false -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361762] Image Split autosave doesn't ask for location and forgets to add dot into extension
https://bugs.kde.org/show_bug.cgi?id=361762 basse <bastian.salm...@gmail.com> changed: What|Removed |Added Platform|Other |Compiled Sources -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361762] New: Image Split autosave doesn't ask for location and forgets to add dot into extension
https://bugs.kde.org/show_bug.cgi?id=361762 Bug ID: 361762 Summary: Image Split autosave doesn't ask for location and forgets to add dot into extension Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: bastian.salm...@gmail.com when you do Image Split, and you have autosave on it doesn't ask where to save, instead it puts everything to your $home. also, it forgets to add . into extension, so you end up with bunch of filenames like: stars_1png, stars_2png, stars_3png ... and, between every save if you use something like png of jpeg files, the dialog with image settings pop up, so you have to keep on clicking "ok". with Reproducible: Always Steps to Reproduce: 1. choose Image Split 2. check autosave and select png/jpg 3. hit apply Actual Results: bunch of wrongly named files in $home, lot of clicking Expected Results: ask once where to save and what image settings and then just do it i noticed that spriter format, lscm works a bit better, doesn't ask that much, saves to $home, and you get filenames a bit better like: stars_1*.scml, stars_2*.scml, stars_3*.scml ... don't know if the asterisk should be there tho... -- You are receiving this mail because: You are watching all bug changes.
