[krita] [Bug 368094] New: [PARBLO A610] pen pressure doesn't work

[Dmitry via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368094

Bug ID: 368094
   Summary: [PARBLO A610] pen pressure doesn't work
   Product: krita
   Version: 3.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: tablet support
  Assignee: krita-bugs-n...@kde.org
  Reporter: die...@yandex.ru

My graphic tablet is PARBLO A610. 
I use pen to launch program and create new file.
And I can use the pen to drawing but it's pressure doesn't works. I tried
several brushes and result was the same.

Reproducible: Always

Steps to Reproduce:
1. Launch the program and create new file.
2. Select the brush that has pressure option (e.g. basic_tip_dafault).
2. Start drawing with a tablet pen performing a different pressure.

Actual Results:  
Solid lines, regardless of the pressure.

Expected Results:  
The width and/or transparency of the drawn line changes depending on the pen
pressure.

Krita 2.9.11 has the same bug. But I can avoid it when launch the program and
create/open file by using tablet pen.

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

[kde] [Bug 253547] Regression: since 4.5.2, KDE downloads multimedia files instead of letting applications stream them

[Dmitry via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=253547

Dmitry  changed:

   What|Removed |Added

 CC||nrn...@gmail.com

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

[krita] [Bug 363284] [UGEE] Krita connects strokes with previous ones

[Dmitry via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363284

--- Comment #19 from Dmitry  ---
Hmm. Interesting. If you keep drawing in krita 3.0 after the bug, cursor will
start following the pen with a huge lag, then it will follow it more and more
smoothly and finally krita will stop connecting strokes. The only problem with
that (besides it being super weird :)) is that the bug will be reset after
relaunch (works with all documents in one session though).

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

[krita] [Bug 363284] [UGEE] Krita connects strokes with previous ones

[Dmitry via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363284

--- Comment #17 from Dmitry  ---
Ok. I'll try to do sth about it.

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

[krita] [Bug 363284] [UGEE] Krita connects strokes with previous ones

[Dmitry via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363284

--- Comment #15 from Dmitry  ---
Or you need me to donate you a ugee device? I'm afraid i can't do this as i
don't have (after buying 2150) money myself :(

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

[krita] [Bug 363284] [UGEE] Krita connects strokes with previous ones

[Dmitry via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363284

--- Comment #14 from Dmitry  ---
Most of them share one driver anyway

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

[krita] [Bug 363284] [UGEE] Krita connects strokes with previous ones

[Dmitry via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363284

--- Comment #13 from Dmitry  ---
Maybe we should find someone with ugee tablet (not monitor) and ask him if
he/she is having problems? That way you guys could afford a way cheaper ugee
device.

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

[krita] [Bug 361515] [UGEE] Brush Cursor Doesn't Follow Ugee Tablet Pen on Hover

[Dmitry via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361515

Dmitry  changed:

   What|Removed |Added

 CC||dudk...@gmail.com

--- Comment #4 from Dmitry  ---
Hi! I'm also a ugee 2150 owner (and my cursor also doesn't follow). May i ask
you if faint lines between strokes are appearing in krita 2.9 or 3.0 (or both).
I'm asking this because krita draws lines between my strokes in 3.0 version.

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

[krita] [Bug 363284] [UGEE] Krita connects strokes with previous ones

[Dmitry via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363284

--- Comment #9 from Dmitry  ---
I'm sorry if i sounded rude. I'm not rushing you, i just hope you won't put
this bug on the shelf. I can use 2.9 for now - it's not big deal.

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

[krita] [Bug 363284] [UGEE] Krita connects strokes with previous ones

[Dmitry via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363284

--- Comment #7 from Dmitry  ---
It works perfectly fine in Krita 2.9. It’s a 3.0 regression. Please help me!

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

[krita] [Bug 363284] [UGEE] Krita connects strokes with previous ones

[Dmitry via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363284

--- Comment #6 from Dmitry  ---
It works fine with krita 2.9 though...

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

[KScreen] [Bug 345225] External monitors not activated after resuming from sleep

[Dmitry via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=345225

Dmitry  changed:

   What|Removed |Added

 CC||sho...@gmail.com

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

[krita] [Bug 363284] Krita connects strokes with previous ones

[Dmitry via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363284

--- Comment #4 from Dmitry  ---
Btw, I know it's a different bug, but my cursor doesn't update while i move my
pen over the screen.

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

[krita] [Bug 363284] Krita connects strokes with previous ones

[Dmitry via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363284

--- Comment #3 from Dmitry  ---
Created attachment 99082
  --> https://bugs.kde.org/attachment.cgi?id=99082=edit
Tablet log

Interestingly in this log first 2 strokes aren't connected (at least on my
screen), but all the next strokes are connected

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

[krita] [Bug 363284] Krita connects strokes with previous ones

[Dmitry via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363284

--- Comment #1 from Dmitry  ---
Created attachment 99075
  --> https://bugs.kde.org/attachment.cgi?id=99075=edit
Screenshot showing the bug

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

[krita] [Bug 363284] New: Krita connects strokes with previous ones

[Dmitry via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363284

Bug ID: 363284
   Summary: Krita connects strokes with previous ones
   Product: krita
   Version: 3.0 Release Candidate
  Platform: Windows CE
   URL: http://imgur.com/hwiH5E7
OS: MS Windows
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: OpenGL Canvas
  Assignee: krita-bugs-n...@kde.org
  Reporter: dudk...@gmail.com

Hi! I'm using Ugee 2150 (yeah i know it's not wacom, but i don't have 2000$ for
a cintiq and still wanna use krita's awesomeness :) ) on krita 3.0 rc1 and it
connects all strokes with previous ones (it doesn't do this with mouse). You
can see the result in the screenshot.

Reproducible: Always

Steps to Reproduce:
1.Get Ugee 2150 :)  (maybe other Ugee tablets as well?)
2.Draw something in Krita
3.Voila!

Actual Results:  
Krita connected my strokes!

Expected Results:  
Well, krita shouldn't have connected my strokes.

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

[konsole] [Bug 354082] high cpu usage for screen redrawing with qt5.5

[Dmitry via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=354082

Dmitry  changed:

   What|Removed |Added

 CC||nrn...@gmail.com

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

[plasmashell] [Bug 361077] New: Plasmashell crashes while walking through activities in reverse order

[Dmitry via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361077

Bug ID: 361077
   Summary: Plasmashell crashes while walking through activities
in reverse order
   Product: plasmashell
   Version: 5.6.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: ivad...@gmail.com

Plasmashell crashes every time I try to walk through activities in reverse
order. The assigned keyboard combo is CTRL+ALT+UP.

Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5ce7a05800 (LWP 4493))]

Thread 9 (Thread 0x7f5cd087f700 (LWP 4494)):
#0  0x7f5ce0eaec3d in poll () from /usr/lib/libc.so.6
#1  0x7f5ce5eacae2 in ?? () from /usr/lib/libxcb.so.1
#2  0x7f5ce5eae757 in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7f5cd219ca99 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#4  0x7f5ce159dde8 in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7f5ce06b1424 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7f5ce0eb7cbd in clone () from /usr/lib/libc.so.6

Thread 8 (Thread 0x7f5ccabd4700 (LWP 4495)):
#0  0x7f5ce0eaec3d in poll () from /usr/lib/libc.so.6
#1  0x7f5cdd332f7c in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f5cdd33308c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f5ce17c6cab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f5ce176f6fa in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f5ce1598fe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f5ce2559a55 in ?? () from /usr/lib/libQt5DBus.so.5
#7  0x7f5ce159dde8 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f5ce06b1424 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f5ce0eb7cbd in clone () from /usr/lib/libc.so.6

Thread 7 (Thread 0x7f5cc9394700 (LWP 4496)):
#0  0x7f5ce0eaec3d in poll () from /usr/lib/libc.so.6
#1  0x7f5cdd332f7c in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f5cdd33308c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f5ce17c6cab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f5ce176f6fa in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f5ce1598fe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f5ce493b915 in ?? () from /usr/lib/libQt5Qml.so.5
#7  0x7f5ce159dde8 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f5ce06b1424 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f5ce0eb7cbd in clone () from /usr/lib/libc.so.6

Thread 6 (Thread 0x7f5cb992f700 (LWP 4497)):
#0  0x7f5cdd332932 in g_main_context_check () from
/usr/lib/libglib-2.0.so.0
#1  0x7f5cdd332f20 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f5cdd33308c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f5ce17c6cab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f5ce176f6fa in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f5ce1598fe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f5ce493b915 in ?? () from /usr/lib/libQt5Qml.so.5
#7  0x7f5ce159dde8 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f5ce06b1424 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f5ce0eb7cbd in clone () from /usr/lib/libc.so.6

Thread 5 (Thread 0x7f5cb3fff700 (LWP 4498)):
#0  0x7f5ce0eaec3d in poll () from /usr/lib/libc.so.6
#1  0x7f5cdd332f7c in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f5cdd33308c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f5ce17c6cab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f5ce176f6fa in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f5ce1598fe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f5ce493b915 in ?? () from /usr/lib/libQt5Qml.so.5
#7  0x7f5ce159dde8 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f5ce06b1424 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f5ce0eb7cbd in clone () from /usr/lib/libc.so.6

Thread 4 (Thread 0x7f5cb29c1700 (LWP 4499)):
#0  0x7f5ce06b703f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f5ce7196134 in ?? () from /usr/lib/libQt5Script.so.5
#2  0x7f5ce7196179 in ?? () from /usr/lib/libQt5Script.so.5
#3  0x7f5ce06b1424 in start_thread () from /usr/lib/libpthread.so.0
#4  0x7f5ce0eb7cbd in clone () from /usr/lib/libc.so.6

Thread 3 (Thread 0x7f5c2abe9700 (LWP 4501)):
#0  0x7f5cdd332519 in g_main_context_prepare () from
/usr/lib/libglib-2.0.so.0
#1  0x7f5cdd332eab in ?? () from /usr/lib/libglib-2.0.so.0
#2  

[plasmashell] [Bug 346521] plasmashell often but not always crashes when switching between windows or starting a new program

[Dmitry via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=346521

Dmitry  changed:

   What|Removed |Added

 CC||ivad...@gmail.com

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

[kdevelop] [Bug 360780] New: Can't click on any item from the 'quick open...' drop-down list

[Dmitry via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360780

Bug ID: 360780
   Summary: Can't click on any item from the 'quick open...'
drop-down list
   Product: kdevelop
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI: all modes
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: ivad...@gmail.com

The drop-down list vanishes whenever I try to click on the result from the
'quick open...' or the 'Outline' (kdevelop 4.90.92)

Reproducible: Always

Steps to Reproduce:
1. Search something on the 'Quick open...'
2. Click on any item

Actual Results:  
The drop-down list vanishes and nothing happens

Expected Results:  
Kdevelop should show the selected source file or function

I've installed this version from AUR (kdevelop-git 4.90.92.r23354.7ce96e2-1)

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

[frameworks-kio] [Bug 359103] New: FTP: wrong non-ASCII file names

[Dmitry via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359103

Bug ID: 359103
   Summary: FTP: wrong non-ASCII file names
   Product: frameworks-kio
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: fa...@kde.org
  Reporter: dmitry.ashka...@gmail.com
CC: kdelibs-b...@kde.org

Hello!

When I create file with non-ASCII name in Dolphin in remote ftp server, this
file has wrong name. The ftp server is pure-ftpd. The problem is that ftp.so
(on behalf of Dolphin) doesn't check UTF-8 support. ftp.so should check UTF-8
support by sending FEAT command (one time after login) and if server returns
UTF8 feature then ftp.so should send OPTS UTF8 ON to the server.

Thank you

Reproducible: Always

Steps to Reproduce:
1. Set up pure-ftpd server with utf-8 support (--with-rfc2640)
2. Create file with non-ASCII name using filezilla (because it enables UTF-8
correctly and 100% uses UTF-8)
3. Use dolphin to see that file has unreadable name (because pure-ftpd converts
name from UTF-8 supposing that the client doesn't support UTF-8)

Actual Results:  
File name is not UTF-8

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

[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup

[Dmitry via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=346961

--- Comment #42 from Dmitry  ---
On my laptop with embedded monitor + hdmi tv it was crashing with kscreen too.

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

[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup

[Dmitry via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=346961

--- Comment #40 from Dmitry  ---
BTW: sometimes plasma and/or kwin crash on display configuration switch with
xrandr workaround. I've just added this into the script right after the xrandr
command:

sleep 1
kwin_x11
plasmashell

kwin and plasma works as a singleton, so this does nothing if they didn't
crashed and starts if kwin or plasma crashed after switch.

PS: still waiting for kscreen fixes... =(

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

[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

[Dmitry via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=354130

--- Comment #9 from Dmitry  ---
I'm shocked! Critical bug about broken a part of main main functionality still
unconfirmed for two months!

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

[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup

[Dmitry via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=346961

--- Comment #29 from Dmitry  ---
(In reply to gene smith from comment #28)
> Well, guess I spoke too soon. Today the problem happened again on KDE
> startup. Will try it set to run script on "Pre-KDE startup" for a while and
> see if that makes a difference.

You'right it should start as soon as possible. Also it's better to disable
kscreen daemon in kde system settings / startup / services.

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

[kdelibs] [Bug 355275] kdelibs upgrade - Kopete crashes after closing a window

[Dmitry via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355275

--- Comment #40 from Dmitry  ---
Created attachment 96122
  --> https://bugs.kde.org/attachment.cgi?id=96122=edit
New crash information added by DrKonqi

kopete (1.7.3) on KDE Platform 4.14.14 using Qt 4.8.7

- What I was doing when the application crashed:

I've been closing a chat window. It seems that app crashes after closing any
window.

-- Backtrace (Reduced):
#7  0x7f8802e46a75 in QObject::disconnect(QObject const*, char const*,
QObject const*, char const*) () from /usr/lib/libQtCore.so.4
#8  0x7f87fb5eb4a9 in KParts::PartManager::~PartManager() () from
/usr/lib/libkparts.so.4
#9  0x7f87fb5eb679 in KParts::PartManager::~PartManager() () from
/usr/lib/libkparts.so.4
#10 0x7f8802e498b1 in QObjectPrivate::deleteChildren() () from
/usr/lib/libQtCore.so.4
#11 0x7f8802e4bf54 in QObject::~QObject() () from /usr/lib/libQtCore.so.4

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

[kdelibs] [Bug 355275] kdelibs upgrade - Kopete crashes after closing a window

[Dmitry via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355275

Dmitry  changed:

   What|Removed |Added

 CC||ivad...@gmail.com

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

[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup

[Dmitry via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=346961

--- Comment #25 from Dmitry  ---
The most reliable solution at this moment is to create an .sh script like this:
$ cat ~/bin/display.sh 
#!/bin/bash
xrandr --output HDMI1 --primary --auto --pos 0x265 --output VGA1 --auto
--rotation left --pos 1920x0
And place it to autostart.

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