[krita] [Bug 364174] crash on exit

2016-06-13 Thread basse via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364174

--- Comment #3 from basse  ---
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

2016-05-19 Thread basse via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363296

--- Comment #2 from basse  ---
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

2016-05-19 Thread basse via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363296

--- Comment #1 from basse  ---
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

2016-05-19 Thread basse via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363296

basse  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

2016-05-19 Thread basse via KDE Bugzilla
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-linux-gnu/libQt5Core.so.5
#10 0x7f7d295959f0 in ?? () from

[krita] [Bug 361911] Overriding hotkeys won't work (conflict of new hotkey with old one)

2016-04-22 Thread basse via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361911

basse  changed:

   What|Removed |Added

 CC||bastian.salm...@gmail.com

--- Comment #1 from basse  ---
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

2016-04-22 Thread basse via KDE Bugzilla
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?

2016-04-22 Thread basse via KDE Bugzilla
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

2016-04-22 Thread basse via KDE Bugzilla
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

2016-04-14 Thread basse via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361762

basse  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

2016-04-14 Thread basse via KDE Bugzilla
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.