[krita] [Bug 366735] New: Brush tip switches when resizing

2016-08-13 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366735

Bug ID: 366735
   Summary: Brush tip switches when resizing
   Product: krita
   Version: git master
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: port...@bk.ru

When i select a brush, and then change it's size via widget in toolbar, the
brush suddenly changes it's brush tip. 
The point seems to be that Krita for some reason remembered, that some time ago
I selected one of tags in brush tip selector in brush editor dialog; and now,
when I change brush size, it recalls that and selects first brush tip with that
tag.

I checked ~/.config/kritarc and found

[SelectedTags]
kis_brushes=Comics
kis_paintoppresets=Expressionism

The "Comics" is that tag, first brushtip with which krita tends to select each
time I change brush size.
When I remove "kis_brushes=" line and restart Krita, everything goes back to
normal.

Reproducible: Always

Steps to Reproduce:
1. Select a brush preset.
2. Paint with it a bit
3. Go to brush editor, under "brush tip"
4. Select some tag other than "All"
5. Select one of brush tips.
6. Paint with resulting brush a bit.
7. Switch to another brush preset. Note that it paints as expected.
8. Change brush size by using widget in toolbar, for example
9. Paint with brush

Actual Results:  
Brush continues to paint with the same brush tip

Expected Results:  
Brush starts to paint with first brushtip from tag you selected in step 4.

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 366030] Ratio sensor seems to be applied after rotation under some conditions

2016-07-24 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366030

--- Comment #2 from Ilya V. Portnov  ---
Created attachment 100265
  --> https://bugs.kde.org/attachment.cgi?id=100265=edit
Brush preset which was used for test

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 366030] Ratio sensor seems to be applied after rotation under some conditions

2016-07-24 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366030

--- Comment #1 from Ilya V. Portnov  ---
Created attachment 100264
  --> https://bugs.kde.org/attachment.cgi?id=100264=edit
Here you can see some parallelograms where rectangles are expected to be seen

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 366030] New: Ratio sensor seems to be applied after rotation under some conditions

2016-07-24 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366030

Bug ID: 366030
   Summary: Ratio sensor seems to be applied after rotation under
some conditions
   Product: krita
   Version: git master
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: port...@bk.ru

For test, i'm using simple brush with "predefined" brush tip, which is just
filled square.
The preset is defined so that:
* rotation depends on drawing angle
* ratio depends on "fuzzy stroke".

I think that rotation should be applied after ratio; so, if you take a square,
then apply "ratio" = 0.5, then rotate it, you will get a rotated rectangle. 
But if you first rotate the square, and next apply ratio, you will get a
parallelogram. I think this is not what intended.

Will attach a screenshot.

Reproducible: Always


Actual Results:  
brush draws series of parallelograms.

Expected Results:  
brush draws series of rotated rectangles.

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 363756] Empty "Tool options" docker after upgrade

2016-05-31 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363756

--- Comment #1 from Ilya V. Portnov  ---
Created attachment 99289
  --> https://bugs.kde.org/attachment.cgi?id=99289=edit
Screenshot of empty "tool options" docker

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 363756] New: Empty "Tool options" docker after upgrade

2016-05-31 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363756

Bug ID: 363756
   Summary: Empty "Tool options" docker after upgrade
   Product: krita
   Version: git master
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Dockers
  Assignee: krita-bugs-n...@kde.org
  Reporter: port...@bk.ru

I just did fresh "git pull" and "make install" after a pair of weeks; when I
started krita, I saw empty "tool options" docker (will attach screenshot).
Switching to another workspace did not help; neither did restarting of krita.
What helps is to switch from brush to another tool and than switch to brush
again.
But if I restart krita, the docker is empty again.

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 362821] Brush editor dialog: bad layout on HiDPI

2016-05-15 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362821

--- Comment #3 from Ilya V. Portnov  ---
I currently do not have krita building environment on the laptop where i have
hidpi display. Will this commit be included in one of next lime ppa build or
appimages? Or is it debug-only?

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 362525] Advanced color selector configuration dialog unusable on HiDPI

2016-05-08 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362525

Ilya V. Portnov  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #9 from Ilya V. Portnov  ---
Created https://bugs.kde.org/show_bug.cgi?id=362821.

As for this bug, i think we should mark it as fixed.

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 362821] New: Brush editor dialog: bad layout on HiDPI

2016-05-08 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362821

Bug ID: 362821
   Summary: Brush editor dialog: bad layout on HiDPI
   Product: krita
   Version: 3.0 Beta
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: port...@bk.ru

Similar to bug #362525. Will attach a screenshot. Curve editing area is not
expanding when I resize the dialog.

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 362821] Brush editor dialog: bad layout on HiDPI

2016-05-08 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362821

--- Comment #1 from Ilya V. Portnov  ---
Created attachment 98844
  --> https://bugs.kde.org/attachment.cgi?id=98844=edit
Brush editor screenshot

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 362525] Advanced color selector configuration dialog unusable on HiDPI

2016-05-05 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362525

--- Comment #7 from Ilya V. Portnov  ---
Advanced color selector configuration dialog became much better with today
update from lime ppa. Thanks!

I also have (maybe related) similar problem with brush settings dialog on
hidpi. Should I create separate ticket for that?

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 362525] Advanced color selector configuration dialog unusable on HiDPI

2016-05-04 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362525

--- Comment #5 from Ilya V. Portnov  ---
I currently do not have krita building environment on the laptop where i have
hidpi display. Will this commit be included in one of next lime ppa build or
appimages?

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 362533] Tremolous lines when drawing with pencil (hidpi related?)

2016-05-01 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362533

--- Comment #7 from Ilya V. Portnov  ---
Created attachment 98729
  --> https://bugs.kde.org/attachment.cgi?id=98729=edit
Tablet log from lowdpi desktop (debian unstable, git master, 1920x1280)

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 362533] Tremolous lines when drawing with pencil (hidpi related?)

2016-05-01 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362533

--- Comment #6 from Ilya V. Portnov  ---
Created attachment 98728
  --> https://bugs.kde.org/attachment.cgi?id=98728=edit
Tablet log from lowdpi laptop (kubuntu, 1366x768)

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 362533] Tremolous lines when drawing with pencil (hidpi related?)

2016-05-01 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362533

--- Comment #5 from Ilya V. Portnov  ---
Created attachment 98727
  --> https://bugs.kde.org/attachment.cgi?id=98727=edit
Tablet log while drawing fuzzy lines (kubuntu, hidpi laptop)

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 362533] Tremolous lines when drawing with pencil (hidpi related?)

2016-05-01 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362533

--- Comment #4 from Ilya V. Portnov  ---
Created attachment 98725
  --> https://bugs.kde.org/attachment.cgi?id=98725=edit
Another better situation (kubuntu 16.04, 1366x768 laptop)

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 362533] Tremolous lines when drawing with pencil (hidpi related?)

2016-05-01 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362533

--- Comment #3 from Ilya V. Portnov  ---
Created attachment 98724
  --> https://bugs.kde.org/attachment.cgi?id=98724=edit
A better situation (krita from git master, debian unstable, 1920x1800 display)

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 362533] Tremolous lines when drawing with pencil (hidpi related?)

2016-05-01 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362533

--- Comment #2 from Ilya V. Portnov  ---
Created attachment 98723
  --> https://bugs.kde.org/attachment.cgi?id=98723=edit
Fuzzy lines 2 (smoothing disabled)

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 362533] New: Tremolous lines when drawing with pencil (hidpi related?)

2016-05-01 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362533

Bug ID: 362533
   Summary: Tremolous lines when drawing with pencil (hidpi
related?)
   Product: krita
   Version: 3.0 Beta
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: port...@bk.ru

If I draw many straight lines in a row with thin pencil brush, they are a bit
tremolous.
Reproduces on krita3-testing from lime ppa and latest appimage.
This is a laptop with 2880x1620.

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 361600] Cannot delete custom tag and the last brush added.

2016-05-01 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361600

Ilya V. Portnov  changed:

   What|Removed |Added

 CC||port...@bk.ru

--- Comment #6 from Ilya V. Portnov  ---
It seems this affects me too (if i got properly that is the same bug).
Steps to reproduce:
In the profiles docker, click Tag/delete this tag.
Tag seems to be removed.
Restart krita.
Go to tags list, and voilà — the tag is here again.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 362525] Advanced color selector configuration dialog unusable on HiDPI

2016-05-01 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362525

--- Comment #3 from Ilya V. Portnov  ---
Created attachment 98720
  --> https://bugs.kde.org/attachment.cgi?id=98720=edit
Colors history page

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 362525] Advanced color selector configuration dialog unusable on HiDPI

2016-05-01 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362525

--- Comment #2 from Ilya V. Portnov  ---
Created attachment 98719
  --> https://bugs.kde.org/attachment.cgi?id=98719=edit
Image colors page

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 362525] Advanced color selector configuration dialog unusable on HiDPI

2016-05-01 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362525

--- Comment #1 from Ilya V. Portnov  ---
Created attachment 98718
  --> https://bugs.kde.org/attachment.cgi?id=98718=edit
Shaders page

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 362525] New: Advanced color selector configuration dialog unusable on HiDPI

2016-05-01 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362525

Bug ID: 362525
   Summary: Advanced color selector configuration dialog unusable
on HiDPI
   Product: krita
   Version: 3.0 Beta
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: color selectors
  Assignee: krita-bugs-n...@kde.org
  Reporter: port...@bk.ru

I have a laptop with 2880x1620 screen resolution, and configuration dialog for
Advanced color selector is almost unusable here. Will attach screenshots (sorry
for russian l10n, i think you will understand which pages of dialog these are).
This is krita3-testing from lime PPA on newly-installed Kubuntu 16.04.

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.


[konsole] [Bug 358212] Konsole crashes at start

2016-04-27 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358212

--- Comment #4 from Ilya V. Portnov  ---
Similarly, stopped reproducing after KDE restart.

Qt: 5.5.1
KDE Frameworks: 5.18.0
Konsole: 15.12.3

-- 
You are receiving this mail because:
You are watching all bug changes.


[konsole] [Bug 358212] Konsole crashes at start

2016-04-27 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358212

--- Comment #3 from Ilya V. Portnov  ---
Just reproduced on Ubuntu recently updated to 16.04:

Application: Konsole (konsole), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f40fd925940 (LWP 28608))]

Thread 2 (Thread 0x7f40fb501700 (LWP 28609)):
#0  0x7f410f3c4e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f4107eb8c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f4107eba8d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f40fd22c629 in QXcbEventReader::run (this=0x13a91a0) at
qxcbconnection.cpp:1253
#4  0x7f410bd6784e in QThreadPrivate::start (arg=0x13a91a0) at
thread/qthread_unix.cpp:331
#5  0x7f410788d6fa in start_thread (arg=0x7f40fb501700) at
pthread_create.c:333
#6  0x7f410f3d0b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f40fd925940 (LWP 28608)):
[KCrash Handler]
#6  0x7f410f2ff418 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7f410f30101a in __GI_abort () at abort.c:89
#8  0x7f410f34172a in __libc_message (do_abort=do_abort@entry=2,
fmt=fmt@entry=0x7f410f458c7f "*** %s ***: %s terminated\n") at
../sysdeps/posix/libc_fatal.c:175
#9  0x7f410f3e289c in __GI___fortify_fail (msg=,
msg@entry=0x7f410f458c10 "buffer overflow detected") at fortify_fail.c:37
#10 0x7f410f3e08a0 in __GI___chk_fail () at chk_fail.c:28
#11 0x7f410f3e27e7 in __fdelt_chk (d=) at fdelt_chk.c:25
#12 0x7f410bedccf7 in QProcessPrivate::waitForStarted (this=0x16123e0,
msecs=3) at io/qprocess_unix.cpp:821
#13 0x7f410f02c13d in Konsole::Pty::start(QString const&, QStringList
const&, QStringList const&) () from
/usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.15
#14 0x7f410f0381d2 in Konsole::Session::run() () from
/usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.15
#15 0x7f410bf76e4f in QtPrivate::QSlotObjectBase::call (a=0x7ffd60ee9030,
r=0x160fcd0, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#16 QMetaObject::activate (sender=0x1610810, signalOffset=,
local_signal_index=, argv=) at
kernel/qobject.cpp:3698
#17 0x7f410bf76fca in QMetaObject::activate (sender=sender@entry=0x16b94d0,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x0) at kernel/qobject.cpp:3713
#18 0x7f410bf777d7 in QMetaObject::activate (sender=sender@entry=0x16b94d0,
m=m@entry=0x7f410c18eb20 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at
kernel/qobject.cpp:3578
#19 0x7f410bf8360b in QSingleShotTimer::timeout (this=0x16b94d0) at
.moc/qtimer.moc:123
#20 QSingleShotTimer::timerEvent (this=0x16b94d0) at kernel/qtimer.cpp:318
#21 0x7f410bf77e53 in QObject::event (this=0x16b94d0, e=) at
kernel/qobject.cpp:1261
#22 0x7f410c83b05c in QApplicationPrivate::notify_helper
(this=this@entry=0x139a270, receiver=receiver@entry=0x16b94d0,
e=e@entry=0x7ffd60ee9460) at kernel/qapplication.cpp:3716
#23 0x7f410c840516 in QApplication::notify (this=0x7ffd60ee97d0,
receiver=0x16b94d0, e=0x7ffd60ee9460) at kernel/qapplication.cpp:3499
#24 0x7f410bf4862b in QCoreApplication::notifyInternal
(this=0x7ffd60ee97d0, receiver=0x16b94d0, event=event@entry=0x7ffd60ee9460) at
kernel/qcoreapplication.cpp:965
#25 0x7f410bf9d89d in QCoreApplication::sendEvent (event=0x7ffd60ee9460,
receiver=) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:224
#26 QTimerInfoList::activateTimers (this=0x13ceca0) at
kernel/qtimerinfo_unix.cpp:637
#27 0x7f410bf9ddd9 in timerSourceDispatch (source=) at
kernel/qeventdispatcher_glib.cpp:177
#28 idleTimerSourceDispatch (source=) at
kernel/qeventdispatcher_glib.cpp:224
#29 0x7f4107156127 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x7f4107156380 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#31 0x7f410715642c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#32 0x7f410bf9ea7f in QEventDispatcherGlib::processEvents (this=0x13c4d20,
flags=...) at kernel/qeventdispatcher_glib.cpp:418
#33 0x7f410bf45dea in QEventLoop::exec (this=this@entry=0x7ffd60ee96a0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#34 0x7f410bf4de8c in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1229
#35 0x7f410f6bad92 in kdemain () from
/usr/lib/x86_64-linux-gnu/libkdeinit5_konsole.so
#36 0x7f410f2ea830 in __libc_start_main (main=0x400710 , argc=1,
argv=0x7ffd60ee9918, init=, fini=,
rtld_fini=, stack_end=0x7ffd60ee9908) at ../csu/libc-start.c:291
#37 0x00400749 in _start ()

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 361973] File open/save/export dialogs broken

2016-04-25 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361973

--- Comment #13 from Ilya V. Portnov  ---
I think it depends somehow on DE running. Maybe KDE sets XDG_DATA_DIRS somehow.
On my configuration XDG_DATA_DIRS is not set and everything works somehow.
It may be also important that I install krita by running make install with
custom installation directory (smth like /home/portnov/soft/krita).

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 361973] File open/save/export dialogs broken

2016-04-24 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361973

--- Comment #11 from Ilya V. Portnov  ---
Well, following is pretty simple patch against git master which resolves the
bug in my case:

diff --git a/krita/main.cc b/krita/main.cc
index 7f79ddf..d1752dc 100644
--- a/krita/main.cc
+++ b/krita/main.cc
@@ -112,7 +112,7 @@ extern "C" int main(int argc, char **argv)
 KisApplication app(key, argc, argv);

 #ifdef Q_OS_LINUX
-qputenv("XDG_DATA_DIRS",
QFile::encodeName(KoResourcePaths::getApplicationRoot() + "share") + ":" +
qgetenv("XDG_DATA_DIRS"));
+//qputenv("XDG_DATA_DIRS",
QFile::encodeName(KoResourcePaths::getApplicationRoot() + "share") + ":" +
qgetenv("XDG_DATA_DIRS"));
 #else
 qputenv("XDG_DATA_DIRS",
QFile::encodeName(KoResourcePaths::getApplicationRoot() + "share"));
 #endif

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 361973] File open/save/export dialogs broken

2016-04-20 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361973

--- Comment #10 from Ilya V. Portnov  ---
"Suspected" part of that commit is

+#ifdef Q_OS_LINUX
+qputenv("XDG_DATA_DIRS",
QFile::encodeName(KoResourcePaths::getApplicationRoot() + "/share") + ":" +
qgetenv("XDG_DATA_DIRS"));
+#else
+qputenv("XDG_DATA_DIRS",
QFile::encodeName(KoResourcePaths::getApplicationRoot() + "/share"));
+#endif
+//qDebug() << "Setting XDG_DATA_DIRS" << qgetenv("XDG_DATA_DIRS");

In my environment, I have XDG_DATA_DIRS not set.

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 361973] File open/save/export dialogs broken

2016-04-20 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361973

--- Comment #9 from Ilya V. Portnov  ---
So, I finally run git bisect, and the result is:

5ef533050cd4206353b44fecd4f06edd6e94e729 is the first bad commit
commit 5ef533050cd4206353b44fecd4f06edd6e94e729
Author: Boudewijn Rempt 
Date:   Wed Apr 6 20:57:52 2016 +0200

Find all the languages so the language chooser is shown

Make sure that on all platforms the local xdg_data_dirs is part
of the environment variable, the one that is bin'../share or
MacOS/../share.

And remove the kauthorized stuff as well. Nobody is going to disable
anything in the help menu in krita in any kind of kiosk situation.

:04 04 1daab4b1c7328743631461c0f7dc61e61905
b89d6b0304263dda7fc9a7ccb4fc14c3f248b00e M  libs

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 361973] File open/save/export dialogs broken

2016-04-20 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361973

--- Comment #8 from Ilya V. Portnov  ---
Git revision bae990e... is "good", file dialog works in it.
It seems I have to do git bisect, but building krita each time takes so much
time... :/

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 361973] File open/save/export dialogs broken

2016-04-20 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361973

--- Comment #6 from Ilya V. Portnov  ---
I can't say exactly which dialog is used - it may be Qt's or KDE's one.

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 361973] File open/save/export dialogs broken

2016-04-20 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361973

--- Comment #5 from Ilya V. Portnov  ---
This is "self-made" desktop environment. I use XMonad as WM, some KDE apps and
some GTK apps. Also, I have XDG_CURRENT_DESKTOP=KDE.

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 361973] File open/save/export dialogs broken

2016-04-19 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361973

--- Comment #3 from Ilya V. Portnov  ---
Created attachment 98467
  --> https://bugs.kde.org/attachment.cgi?id=98467=edit
Full stderr log

Attaching full log from stdout 

The desktop environment is not KDE, but Dolphin (5) launches and works very
well, and shows all thumbnails.

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 361973] File open/save/export dialogs broken

2016-04-19 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361973

--- Comment #2 from Ilya V. Portnov  ---
Fragment of stderr output:

("image/webp", "image/x-r16", "image/x-xbitmap", "image/openraster",
"text/x-qml", "image/tiff", "application/x-extension-exr", "image/png",
"image/vnd.adobe.photoshop", "image/x-gimp-brush", "text/csv",
"image/vnd.microsoft.icon", "image/x-portable-bitmap", "image/bmp",
"application/x-krita", "image/x-portable-pixmap", "image/jpeg",
"image/x-gimp-brush-animated", "image/x-exr", "image/x-tga", "image/x-xpixmap",
"image/x-portable-graymap", "application/x-spriter", "image/jp2", "image/x-r8")
No file found for ".xml" , even though update-mime-info said it would exist.
Either it was just removed, or the directory doesn't have executable
permission...

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 361973] File open/save/export dialogs broken

2016-04-19 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361973

--- Comment #1 from Ilya V. Portnov  ---
Created attachment 98466
  --> https://bugs.kde.org/attachment.cgi?id=98466=edit
Export file dialog example

Selected directory actually contains a lot of files in different formats.

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 361973] New: File open/save/export dialogs broken

2016-04-19 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361973

Bug ID: 361973
   Summary: File open/save/export dialogs broken
   Product: krita
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: File formats
  Assignee: krita-bugs-n...@kde.org
  Reporter: port...@bk.ru

Compiled from git master today.
Debian testing/unstable.

When I call File -> Open, Save, Export, the file dialog:
1. Does not show anything in file list pane, whatever I select in "files type"
combobox.
2. Shows only some file types available for export to.

Reproducible: Always

Steps to Reproduce:
1. Launch krita
2. draw something
3. go to file -> export or file -> save

-- 
You are receiving this mail because:
You are watching all bug changes.


[konsole] [Bug 358212] New: Konsole crashes at start

2016-01-19 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358212

Bug ID: 358212
   Summary: Konsole crashes at start
   Product: konsole
   Version: 2.14.2
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: port...@bk.ru

Application: konsole (2.14.2)
KDE Platform Version: 4.14.14
Qt Version: 4.8.7
Operating System: Linux 4.0.0-1-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
- What I was doing when the application crashed:

I just started konsole and it crashed.

This is debian updated to unstable recently.

-- Backtrace:
Application: Konsole (konsole), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x7fd38f2aa107 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#7  0x7fd38f2ab4e8 in __GI_abort () at abort.c:89
#8  0x7fd38f2e8204 in __libc_message (do_abort=do_abort@entry=2,
fmt=fmt@entry=0x7fd38f3d8a2b "*** %s ***: %s terminated\n") at
../sysdeps/posix/libc_fatal.c:175
#9  0x7fd38f36b4c7 in __GI___fortify_fail (msg=msg@entry=0x7fd38f3d89c2
"buffer overflow detected") at fortify_fail.c:31
#10 0x7fd38f3696e0 in __GI___chk_fail () at chk_fail.c:28
#11 0x7fd38f36b437 in __fdelt_chk (d=) at fdelt_chk.c:25
#12 0x7fd38d93f3f7 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#13 0x7fd38eff4031 in Konsole::Pty::start(QString const&, QStringList
const&, QStringList const&) () from /usr/lib/libkonsoleprivate.so
#14 0x7fd38efffc08 in Konsole::Session::run() () from
/usr/lib/libkonsoleprivate.so
#15 0x7fd38f000f85 in ?? () from /usr/lib/libkonsoleprivate.so
#16 0x7fd38d97b38c in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#17 0x7fd38d97b38c in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#18 0x7fd38d9846ba in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#19 0x7fd38d97f953 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#20 0x7fd38ccb07bc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#21 0x7fd38ccb72d8 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#22 0x7fd38e41d71a in KApplication::notify(QObject*, QEvent*) () from
/usr/lib/libkdeui.so.5
#23 0x7fd38d96636d in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#24 0x7fd38d997ffb in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#25 0x7fd38d995069 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#26 0x7fd3882e1fe7 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x7fd3882e2240 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x7fd3882e22ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x7fd38d99598d in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#30 0x7fd38cd58396 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#31 0x7fd38d964ec1 in
QEventLoop::processEvents(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#32 0x7fd38d965225 in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#33 0x7fd38d96aca9 in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#34 0x7fd38f636ed9 in kdemain () from
/usr/lib/kde4/libkdeinit/libkdeinit4_konsole.so
#35 0x7fd38f296b45 in __libc_start_main (main=0x4006d0, argc=1,
argv=0x7ffdc6779818, init=, fini=,
rtld_fini=, stack_end=0x7ffdc6779808) at libc-start.c:287
#36 0x004006fe in _start ()

Possible duplicates by query: bug 327574, bug 323830, bug 322782, bug 318896,
bug 315194.

Reported using DrKonqi

-- 
You are receiving this mail because:
You are watching all bug changes.


[konsole] [Bug 358212] Konsole crashes at start

2016-01-19 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358212

--- Comment #2 from Ilya V. Portnov  ---
Problem is gone (at least, for some time) after restarting KDE.

-- 
You are receiving this mail because:
You are watching all bug changes.


[konsole] [Bug 358212] Konsole crashes at start

2016-01-19 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358212

Ilya V. Portnov  changed:

   What|Removed |Added

 CC||port...@bk.ru

-- 
You are receiving this mail because:
You are watching all bug changes.


[konsole] [Bug 358212] Konsole crashes at start

2016-01-19 Thread Ilya V . Portnov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358212

--- Comment #1 from Ilya V. Portnov  ---
Created attachment 96737
  --> https://bugs.kde.org/attachment.cgi?id=96737=edit
New crash information added by DrKonqi

konsole (2.14.2) on KDE Platform 4.14.14 using Qt 4.8.7

- What I was doing when the application crashed:

For some reason konsole started to crash at each launch. Before that, it worked
ok for some time.

-- Backtrace (Reduced):
#6  0x7f31969bb107 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#7  0x7f31969bc4e8 in __GI_abort () at abort.c:89
[...]
#9  0x7f3196a7c4c7 in __GI___fortify_fail (msg=msg@entry=0x7f3196ae99c2
"buffer overflow detected") at fortify_fail.c:31
#10 0x7f3196a7a6e0 in __GI___chk_fail () at chk_fail.c:28
#11 0x7f3196a7c437 in __fdelt_chk (d=) at fdelt_chk.c:25

-- 
You are receiving this mail because:
You are watching all bug changes.