[krusader] [Bug 371582] [2.5.0] Wrong representation of files and paths with Russian names (ru_RU.UTF-8)

2016-10-24 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371582

--- Comment #8 from Sergey  ---
In Konqueror and other browsers files are displayed correctly. They also were
displayed correctly in 2.4.0_beta3-r2 version of Krusader. The only problem is
with Krusader-2.5.0. The problem may also be related to fresh Gentoo ebuild of
Krusader I have. IDK.

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


[krusader] [Bug 371582] [2.5.0] Wrong representation of files and paths with Russian names (ru_RU.UTF-8)

2016-10-24 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371582

--- Comment #6 from Sergey  ---
The output of locale is the following:
# locale
LANG=ru_RU.UTF-8
LC_CTYPE="ru_RU.UTF-8"
LC_NUMERIC=C
LC_TIME="ru_RU.UTF-8"
LC_COLLATE="ru_RU.UTF-8"
LC_MONETARY="ru_RU.UTF-8"
LC_MESSAGES=C
LC_PAPER="ru_RU.UTF-8"
LC_NAME="ru_RU.UTF-8"
LC_ADDRESS="ru_RU.UTF-8"
LC_TELEPHONE="ru_RU.UTF-8"
LC_MEASUREMENT="ru_RU.UTF-8"
LC_IDENTIFICATION="ru_RU.UTF-8"
LC_ALL=

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


[krusader] [Bug 371582] [2.5.0] Wrong representation of files and paths with Russian names (ru_RU.UTF-8)

2016-10-24 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371582

--- Comment #5 from Sergey  ---
Created attachment 101750
  --> https://bugs.kde.org/attachment.cgi?id=101750=edit
A real screenshot from my Plasms 5 desktop

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


[krusader] [Bug 371582] [2.5.0] Wrong representation of files and paths with Russian names (ru_RU.UTF-8)

2016-10-24 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371582

--- Comment #4 from Sergey  ---
In general. It's not relayted to archives. I've just migrated to 2.5.0 and
suddenly started to see this problem. I'll give you a real screenshot, not a
wrong copypaste from some forum which I thought did look like.

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


[krusader] [Bug 371582] [2.5.0] Wrong representation of files and paths with Russian names (ru_RU.UTF-8)

2016-10-24 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371582

--- Comment #1 from Sergey  ---
Comment on attachment 101745
  --> https://bugs.kde.org/attachment.cgi?id=101745
Wrong representation of non-English filenames and directories

Wrong pic.

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


[krusader] [Bug 371582] [2.5.0] Wrong representation of files and paths with Russian names (ru_RU.UTF-8)

2016-10-24 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371582

--- Comment #2 from Sergey  ---
Sorry, I posted wrong picture from the other forum. In reality filenames are
look like this: "��".

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

[krusader] [Bug 371582] New: [2.5.0] Wrong representation of files and paths with Russian names (ru_RU.UTF-8)

2016-10-24 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371582

Bug ID: 371582
   Summary: [2.5.0] Wrong representation of files and paths with
Russian names (ru_RU.UTF-8)
   Product: krusader
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: m...@fork.pl
  Reporter: energumenos...@gmail.com

Created attachment 101745
  --> https://bugs.kde.org/attachment.cgi?id=101745=edit
Wrong representation of non-English filenames and directories

See picture what I have instead of normal Russian names in all non-English
files and directories.

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


[plasmashell] [Bug 371198] Clock applets show wrong and different times

2016-10-20 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371198

--- Comment #5 from Sergey  ---
here is result of

int main(int argc, char *argv[])
{
QCoreApplication a(argc, argv);

qDebug() << QDateTime::currentDateTime();
qDebug() << QDateTime::currentDateTimeUtc();
}


QDateTime(2016-10-20 19:24:17.652 +05 Qt::TimeSpec(LocalTime))
QDateTime(2016-10-20 14:24:17.652 UTC Qt::TimeSpec(UTC))

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


[plasmashell] [Bug 371198] Clock applets show wrong and different times

2016-10-20 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371198

Sergey  changed:

   What|Removed |Added

 CC||rion...@gmail.com

--- Comment #4 from Sergey  ---
The same for me with Asia/Yekaterinburg.
I tried small Qt5 application
qDebug() << QDateTime::currentDateTime();
and it showed correct time. So I believe the problem is in some kde/plasma
subsystem.

Ubuntu 16.04 + kubuntu-ppa

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


[krunner] [Bug 353547] krunner uses 726GiB (Gigabytes!) of virtual memory - mapped the baloo index ~3000 times

2016-10-16 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=353547

Sergey  changed:

   What|Removed |Added

 CC||rion...@gmail.com

--- Comment #10 from Sergey  ---
The same for me. kde-5.8.1
plasmashell takes 261G of virtual memory.
maps file says almost everything is mapped to
/home/rion/.local/share/baloo/index

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


[konsole] [Bug 370211] New: Crash on tab attach

2016-10-06 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=370211

Bug ID: 370211
   Summary: Crash on tab attach
   Product: konsole
   Version: 16.08.1
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: rion...@gmail.com

Application: konsole (16.08.1)
 (Compiled from sources)
Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.8.0-gentoo x86_64
Distribution: "Gentoo Base System release 2.3"

-- Information about the crash:
1. Detached tab from one console.
2. Detached another tab from the same console
3. Opened a new empty tab in window from p.2
4. Drag'n'drop tab from p.2 to detached Window from p.1

-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5437c0 (LWP 4700))]

Thread 2 (Thread 0x7f5dda9c3700 (LWP 4703)):
#0  0x7f5dee632d6d in poll () from /lib64/libc.so.6
#1  0x7f5de60cffdc in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f5de60d00ec in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f5deb298ecb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f5deb248d3a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f5deb0a7e14 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f5deec225c5 in QDBusConnectionManager::run() () from
/usr/lib64/libQt5DBus.so.5
#7  0x7f5deb0ac2bc in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#8  0x7f5de7b61434 in start_thread () from /lib64/libpthread.so.0
#9  0x7f5dee63bded in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f5437c0 (LWP 4700)):
[KCrash Handler]
#6  0x7f5debd5a94d in QAction::~QAction() () from
/usr/lib64/libQt5Widgets.so.5
#7  0x7f5debdac51d in QWidgetAction::~QWidgetAction() () from
/usr/lib64/libQt5Widgets.so.5
#8  0x7f5dec9e1828 in KSelectAction::~KSelectAction() () from
/usr/lib64/libKF5WidgetsAddons.so.5
#9  0x7f5ded344b29 in KCodecAction::~KCodecAction() () from
/usr/lib64/libKF5ConfigWidgets.so.5
#10 0x7f5deb278305 in QObjectPrivate::deleteChildren() () from
/usr/lib64/libQt5Core.so.5
#11 0x7f5deb279249 in QObject::~QObject() () from
/usr/lib64/libQt5Core.so.5
#12 0x7f5dee2c9989 in Konsole::SessionController::~SessionController() ()
from /usr/lib64/libkonsoleprivate.so.16
#13 0x7f5dee2c99c9 in Konsole::SessionController::~SessionController() ()
from /usr/lib64/libkonsoleprivate.so.16
#14 0x7f5deb278305 in QObjectPrivate::deleteChildren() () from
/usr/lib64/libQt5Core.so.5
#15 0x7f5deb279249 in QObject::~QObject() () from
/usr/lib64/libQt5Core.so.5
#16 0x7f5dee2edb09 in Konsole::ViewManager::~ViewManager() () from
/usr/lib64/libkonsoleprivate.so.16
#17 0x7f5deb278305 in QObjectPrivate::deleteChildren() () from
/usr/lib64/libQt5Core.so.5
#18 0x7f5debda4c14 in QWidget::~QWidget() () from
/usr/lib64/libQt5Widgets.so.5
#19 0x7f5dedb6c841 in KMainWindow::~KMainWindow() () from
/usr/lib64/libKF5XmlGui.so.5
#20 0x7f5dee924eae in Konsole::MainWindow::~MainWindow() () from
/usr/lib64/libkdeinit5_konsole.so
#21 0x7f5deb272938 in QObject::event(QEvent*) () from
/usr/lib64/libQt5Core.so.5
#22 0x7f5debda93bb in QWidget::event(QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#23 0x7f5debea397b in QMainWindow::event(QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#24 0x7f5dedb6ece7 in KMainWindow::event(QEvent*) () from
/usr/lib64/libKF5XmlGui.so.5
#25 0x7f5dedbb3675 in KXmlGuiWindow::event(QEvent*) () from
/usr/lib64/libKF5XmlGui.so.5
#26 0x7f5debd63fbc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/libQt5Widgets.so.5
#27 0x7f5debd694c6 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#28 0x7f5deb249eca in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib64/libQt5Core.so.5
#29 0x7f5deb24bf1a in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib64/libQt5Core.so.5
#30 0x7f5deb298e33 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /usr/lib64/libQt5Core.so.5
#31 0x7f5de60cfde7 in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#32 0x7f5de60d0040 in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#33 0x7f5de60d00ec in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#34 0x7f5deb298eaf in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#35 0x7f5deb248d3a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#36 0x7f5deb25082c in QCoreApplication::exec() () from
/usr/lib64/libQt5Core.so.5
#37 

[valgrind] [Bug 362934] [AsusWRT] Arm v7 illegal instruction

2016-09-16 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362934

--- Comment #2 from Sergey  ---
I could only point you to this info:
https://wikidevi.com/wiki/ASUS_RT-AC87U   => the SOC is BCM4709A0
https://wikidevi.com/wiki/Broadcom

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


[kate] [Bug 366141] Search and Replace regression after upgrade from KDE-4 to Plasma-5

2016-07-27 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366141

--- Comment #8 from Sergey  ---
Thank you, disabling "Search and Replace" plugin in options solved my issue.
IDK why it marked as enabled in Kate options. Everything work as expected now.

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


[kate] [Bug 366141] Search and Replace regression after upgrade from KDE-4 to Plasma-5

2016-07-26 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366141

--- Comment #5 from Sergey  ---
Video how did it look like before:
https://www.youtube.com/watch?v=7kDLd7bYJkA
It was easy there to type CTRL+F, to find smth, then to click on small green
button on the right and after click on this small button "down arrow" (instead
of big and UGLY "Search and Replace" button in new Kate and Plasma-5) there was
Replace field which appeared right after clicking on this small nice button.
There were no 2 fields with "Find". And "Replace" filed was easily removable
too. As well as "Search and replace dialog" was also easy removable too.
Please, move changes back as it was. Current version is unworkable at all.

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


[kate] [Bug 366141] Search and Replace regression after upgrade from KDE-4 to Plasma-5

2016-07-26 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366141

--- Comment #4 from Sergey  ---
Suggstion is to leave the same behaviour as it was in KDE-4 in some of the
previous versions of either kate or its plugin. Current behaviour is
REGRESSION. There were no problems in that respect before upgrade to glitchy
Plasm-5 (with a pile of bugs and regressions).

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


[kate] [Bug 366141] Search and Replace regression after upgrade from KDE-4 to Plasma-5

2016-07-26 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366141

--- Comment #2 from Sergey  ---
Created attachment 100319
  --> https://bugs.kde.org/attachment.cgi?id=100319=edit
Screenshot005

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


[kate] [Bug 366141] Search and Replace regression after upgrade from KDE-4 to Plasma-5

2016-07-26 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366141

Sergey  changed:

   What|Removed |Added

 CC||energumenos...@gmail.com

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


[kate] [Bug 366141] Search and Replace regression after upgrade from KDE-4 to Plasma-5

2016-07-26 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366141

--- Comment #1 from Sergey  ---
Created attachment 100318
  --> https://bugs.kde.org/attachment.cgi?id=100318=edit
Screenshot004

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


[kate] [Bug 366141] New: Search and Replace regression after upgrade from KDE-4 to Plasma-5

2016-07-26 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366141

Bug ID: 366141
   Summary: Search and Replace regression after upgrade from KDE-4
to Plasma-5
   Product: kate
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: energumenos...@gmail.com

First of all, I don't like redesign of Kate and changes in Find and Replace
button placement/behaviour. But it also became buggy. Search smth with CTRL+F
in Kate (See screenshot004.png), input some text to find, then click on button
"Search and Replace". And surprise! You'll have to input text again! See
screenshot005 below. There were no such bugs in Kate in KDE:4 and there was
better overall design too.

Reproducible: Always

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


[plasmashell] [Bug 366140] Date is to the left of the Time on Digital Clock instead of under it, font is too big too

2016-07-26 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366140

Sergey  changed:

   What|Removed |Added

 CC||energumenos...@gmail.com

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


[plasmashell] [Bug 366140] Date is to the left of the Time on Digital Clock instead of under it, font is too big too

2016-07-26 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366140

--- Comment #2 from Sergey  ---
Created attachment 100316
  --> https://bugs.kde.org/attachment.cgi?id=100316=edit
Screenshot02

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


[plasmashell] [Bug 366140] Date is to the left of the Time on Digital Clock instead of under it, font is too big too

2016-07-26 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366140

--- Comment #1 from Sergey  ---
Created attachment 100315
  --> https://bugs.kde.org/attachment.cgi?id=100315=edit
Screenshot01

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


[valgrind] [Bug 362935] [AsusWRT] Assertion 'sizeof(TTEntryC) <= 88' failed

2016-07-05 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362935

--- Comment #2 from Sergey  ---
Just tried the latest r15901 on a slightly different platform (ASUS RT-AC87U)
and with different executable.
Result is the same:

admin@RT-AC87U-0C18:/tmp/home/root# valgrind ssh
==704== Memcheck, a memory error detector
==704== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==704== Using Valgrind-3.12.0.SVN and LibVEX; rerun with -h for copyright info
==704== Command: ssh
==704== 

valgrind: m_transtab.c:2459 (vgPlain_init_tt_tc): Assertion 'sizeof(TTEntryC)
<= 88' failed.
Segmentation fault

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


[kxkb] [Bug 364855] after few switches from us to ru keyboard layout it does not switch any more until I press some buttons in "keyboard" setup window, like "default" and set input lang's again.

2016-06-29 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364855

--- Comment #1 from Sergey  ---
Sorry I am migrated now on Cinnamon Linux Mint 18 so I can not provide any more
info about these bug.

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


[Keyboard status applet] [Bug 364855] after few switches from us to ru keyboard layout it does not switch any more until I press some buttons in "keyboard" setup window, like "default" and set input l

2016-06-28 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364855

Sergey  changed:

   What|Removed |Added

 CC||zor198...@yandex.ru

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


[Keyboard status applet] [Bug 364855] New: after few switches from us to ru keyboard layout it does not switch any more until I press some buttons in "keyboard" setup window, like "default" and set in

2016-06-28 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364855

Bug ID: 364855
   Summary: after few switches from us to ru keyboard layout it
does not switch any more until I press some buttons in
"keyboard" setup window, like "default" and set input
lang's again.
   Product: Keyboard status applet
   Version: unspecified
  Platform: OpenMandriva RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gun...@schmi-dt.de
  Reporter: zor198...@yandex.ru

after few switches from us to ru keyboard layout it does not switch any more
until I press some buttons in "keyboard" setup window, like "default" and set
input lang's again.

Reproducible: Always

Steps to Reproduce:
1. Setup 2 keyboard input lang's en + ru default profile via kde "keyboard"
applet
2. Try to switch in between input languages layouts.
3. See how it stops switching between layouts after few switches I believe 3-5
switches is enough to see it. I use open mandriva beta 2 freshly released. Can
be fixed for another 3-5 switches if you run kde "keyboard" then press any
button or reset everything to "defaults" and then set up same configuration
again so you proceed to step 1 again ;D

Actual Results:  
System tray input methods switcher freezes upon 1 random language en or ru and
can't change input language any more.

Expected Results:  
I expect it works fine and switch language layouts! Damn it! :D fix asap!

plasma 5.6.5
frameworks 5.23.0
qt 5.6.1
kernel 4.6.2--desktop-3omv
system x86-64

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


[kwin] [Bug 360033] Cannot enable compositing with OpenGL GLX

2016-05-31 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360033

--- Comment #43 from Sergey  ---
After applying patch from comment
https://bugs.kde.org/show_bug.cgi?id=360033#c28 compositing has started to work
like in good old times of KDE4.

$ kwin_x11 --replace
OpenGL vendor string:   NVIDIA Corporation
OpenGL renderer string: GeForce 7600 GS/PCIe/SSE2
OpenGL version string:  2.1.2 NVIDIA 304.131
OpenGL shading language version string: 1.20 NVIDIA via Cg compiler
Driver: NVIDIA
Driver version: 304.131
GPU class:  NV40/G70
OpenGL version: 2.1.2
GLSL version:   1.20
X server version:   1.17.4
Linux kernel version:   3.18.34
Requires strict binding:no
GLSL shaders:   limited
Texture NPOT support:   yes
Virtual Machine:no
Module 'org.kde.kwin.decoration' does not contain a module identifier directive
- it cannot be protected from external registrations.
QXcbConnection: XCB error: 8 (BadMatch), sequence: 2083, resource id: 65011718,
major code: 42 (SetInputFocus), minor code: 0
OpenGL vendor string:   NVIDIA Corporation
OpenGL renderer string: GeForce 7600 GS/PCIe/SSE2
OpenGL version string:  2.1.2 NVIDIA 304.131
OpenGL shading language version string: 1.20 NVIDIA via Cg compiler
Driver: NVIDIA
Driver version: 304.131
GPU class:  NV40/G70
OpenGL version: 2.1.2
GLSL version:   1.20
X server version:   1.17.4
Linux kernel version:   3.18.34
Requires strict binding:no
GLSL shaders:   limited
Texture NPOT support:   yes
Virtual Machine:no
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2473, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2483, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2484, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2485, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2486, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2487, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QMetaProperty::read: Unable to handle unregistered datatype
'KWayland::Server::SurfaceInterface*' for property 'KWin::Toplevel::surface'

$ qdbus org.kde.KWin /KWin supportInformation
KWin Support Information:
The following information should be used when requesting support on e.g.
http://forum.kde.org.
It provides information about the currently running instance, which options are
used,
what OpenGL driver and which effects are running.
Please post the information provided underneath this introductory text to a
paste bin service
like http://paste.kde.org instead of pasting into support threads.

==

Version
===
KWin version: 5.6.4
Qt Version: 5.5.1
Qt compile version: 5.5.1
XCB compile version: 1.11.1

Operation Mode: X11 only

Build Options
=
KWIN_BUILD_DECORATIONS: yes
KWIN_BUILD_TABBOX: yes
KWIN_BUILD_ACTIVITIES: yes
HAVE_INPUT: yes
HAVE_DRM: yes
HAVE_GBM: yes
HAVE_X11_XCB: yes
HAVE_EPOXY_GLX: yes
HAVE_WAYLAND_EGL: yes

X11
===
Vendor: The X.Org Foundation
Vendor Release: 11704000
Protocol Version/Revision: 11/0
SHAPE: yes; Version: 0x11
RANDR: yes; Version: 0x14
DAMAGE: yes; Version: 0x11
Composite: yes; Version: 0x4
RENDER: yes; Version: 0xb
XFIXES: yes; Version: 0x50
SYNC: yes; Version: 0x31
GLX: yes; Version: 0x0

Decoration
==
Plugin: org.kde.kwin.aurorae
Theme: __aurorae__svg__my-glowglass-lite-black
Blur: 1
onAllDesktopsAvailable: true
alphaChannelSupported: true
closeOnDoubleClickOnMenu: false
decorationButtonsLeft: 0, 2
decorationButtonsRight: 6, 3, 4, 5
borderSize: 3
gridUnit: 14
font: DejaVu Sans,12,-1,5,50,0,0,0,0,0
smallSpacing: 3
largeSpacing: 14

Options
===
focusPolicy: 0
nextFocusPrefersMouse: false
clickRaise: true
autoRaise: false
autoRaiseInterval: 0
delayFocusInterval: 0
shadeHover: false
shadeHoverInterval: 250
separateScreenFocus: false
placement: 4
focusPolicyIsReasonable: true
borderSnapZone: 10
windowSnapZone: 10
centerSnapZone: 0
snapOnlyWhenOverlapping: false
rollOverDesktops: true
focusStealingPreventionLevel: 1
legacyFullscreenSupport: false
operationTitlebarDblClick: 5000
operationMaxButtonLeftClick: 5000
operationMaxButtonMiddleClick: 5015
operationMaxButtonRightClick: 5014
commandActiveTitlebar1: 

[kwin] [Bug 360033] Cannot enable compositing with OpenGL GLX

2016-05-31 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360033

--- Comment #42 from Sergey  ---
I have the latest x11-drivers/nvidia-drivers-304.131-r4 for this card (Geforce
7 series). Also, I have a glitch of incorrect placement of Plasma startup
window right after login from SDDM. It disappears right after start of Plasma
but it's placement is incorrect. It should be in the center, but it's in the
top-left corner. I'm talking about this window (in the center on the video):
https://youtu.be/Y1NAZGsQtjQ?t=2m11s
Maybe it will help to investigate a problem.

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


[kwin] [Bug 360033] Cannot enable compositing with OpenGL GLX

2016-05-31 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360033

--- Comment #41 from Sergey  ---
My hardware is the following:
CPU: Phenom II X4 810
GPU: NVIDIA GeForce 7600 GS/PCIe/SSE2 512MB
RAM: 12GB

I had no problems in KDE4. Games like OpenRA are still working in Plasma 5, so
it's not a problem of video card/drivers. 
[code]
$ mv ~/.config/kwinrc ~/.config/kwinrc.bak

$ kwin_x11 --replace
OpenGL vendor string:   NVIDIA Corporation
OpenGL renderer string: GeForce 7600 GS/PCIe/SSE2
OpenGL version string:  2.1.2 NVIDIA 304.131
OpenGL shading language version string: 1.20 NVIDIA via Cg compiler
Driver: NVIDIA
Driver version: 304.131
GPU class:  NV40/G70
OpenGL version: 2.1.2
GLSL version:   1.20
X server version:   1.17.4
Linux kernel version:   3.18.34
Requires strict binding:no
GLSL shaders:   limited
Texture NPOT support:   yes
Virtual Machine:no
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(1, 0, 0, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 0, 1, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(1, 1, 1, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.44882, 0.14882, 0.14882,
1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.50064, 0.80064, 0.50064,
1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.05054, 0.05054, 0.35054,
1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(1, 1, 1, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.3, 0, 0, 0.6)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 0.4, 0, 0.6)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 0, 0.5, 0.6)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.3, 0.4, 0.5, 0.6)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.134646, 0.044646,
0.044646, 0.6)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.200256, 0.320256,
0.200256, 0.6)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.02527, 0.02527, 0.17527,
0.6)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.360172, 0.390172,
0.420172, 0.6)
kwin_core: ShaderManager self test failed
kwin_core: Failed to initialize compositing, compositing disabled
QXcbConnection: XCB error: 3 (BadWindow), sequence: 710, resource id: 1185,
major code: 3 (GetWindowAttributes), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 711, resource id: 1185,
major code: 14 (GetGeometry), minor code: 0 
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1772, resource id: 65011718,
major code: 42 (SetInputFocus), minor code: 0   
OpenGL vendor string:   NVIDIA Corporation  
OpenGL renderer string: GeForce 7600 GS/PCIe/SSE2   
OpenGL version string:  2.1.2 NVIDIA 304.131
OpenGL shading language version string: 1.20 NVIDIA via Cg compiler 
Driver: NVIDIA  
Driver version: 304.131 
GPU class:  NV40/G70
OpenGL version: 2.1.2   
GLSL version:   1.20
X server version:   1.17.4
Linux kernel version:   3.18.34
Requires strict binding:no
GLSL shaders:   limited
Texture NPOT support:   yes
Virtual Machine:no
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(1, 0, 0, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 0, 1, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(1, 1, 1, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.44882, 0.14882, 0.14882,
1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.50064, 0.80064, 0.50064,
1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.05054, 0.05054, 0.35054,
1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(1, 1, 1, 1)
Pixel was QVector4D(0, 0, 0, 0) expected 

[kwin] [Bug 360033] Cannot enable compositing with OpenGL GLX

2016-05-31 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360033

Sergey  changed:

   What|Removed |Added

 CC||energumenos...@gmail.com

--- Comment #40 from Sergey  ---
I have the same problem with compositor not working on the following versions
of Plasma: 5.5.5-r1 and 5.6.4.

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


[krita] [Bug 363744] basic stabiliser don't work at wacom CTL-480 and another UI bugs (hiDPI, 3840x2160)

2016-05-31 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363744

Sergey  changed:

   What|Removed |Added

 CC||kolo...@gmail.com

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


[krita] [Bug 363744] New: basic stabiliser don't work at wacom CTL-480 and another UI bugs (hiDPI, 3840x2160)

2016-05-31 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363744

Bug ID: 363744
   Summary: basic stabiliser don't work at wacom CTL-480 and
another UI bugs (hiDPI, 3840x2160)
   Product: krita
   Version: 3.0
  Platform: MS Windows
   URL: https://youtu.be/PAUtnNMdTfY
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: kolo...@gmail.com

my english is bad...

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-23 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362821

Sergey  changed:

   What|Removed |Added

 CC||kolo...@gmail.com

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


[valgrind] [Bug 362935] New: [AsusWRT] Assertion 'sizeof(TTEntryC) <= 88' failed

2016-05-11 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362935

Bug ID: 362935
   Summary: [AsusWRT] Assertion 'sizeof(TTEntryC) <= 88' failed
   Product: valgrind
   Version: 3.12 SVN
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: sknau...@gmail.com

When I tried to verify whether bug 362934 was fixed in upstream, I integrated
SVN trunk valgrind as of 11.05.2016 into AsusWRT-Merlin 380.58. Again the only
change is in configure script: armv7*) -> arm*).

Now valgrind fails with assertion:

admin@RT-AC5300-0810:/tmp/home/root# valgrind qharvestd -F
-c/tmp/qharvestd.conf
==802== Memcheck, a memory error detector
==802== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==802== Using Valgrind-3.12.0.SVN and LibVEX; rerun with -h for copyright info
==802== Command: qharvestd -F -c/tmp/qharvestd.conf
==802== 

valgrind: m_transtab.c:2459 (vgPlain_init_tt_tc): Assertion 'sizeof(TTEntryC)
<= 88' failed.
Segmentation fault

admin@RT-AC5300-0810:/tmp/home/root# cat /proc/cpuinfo
Processor   : ARMv7 Processor rev 0 (v7l)
processor   : 0
BogoMIPS: 2798.38

processor   : 1
BogoMIPS: 2798.38

Features: swp half thumb fastmult edsp 
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part: 0xc09
CPU revision: 0

Hardware: Northstar Prototype
Revision: 
Serial  : 

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


[valgrind] [Bug 362934] New: [AsusWRT] Arm v7 illegal instruction

2016-05-11 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362934

Bug ID: 362934
   Summary: [AsusWRT] Arm v7 illegal instruction
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: sknau...@gmail.com

I integrated valgrind 3.11.0 into AsusWRT-Merlin 380.58. I tried to use it on
RT-AC87U and RT-AC5300 routers (they are using different toolchains).

When I try to check arbitrary program with Valgrind, it prints:

admin@RT-AC5300-0810:/tmp/home/root# valgrind qharvestd -F
-c/tmp/qharvestd.conf
==1063== Memcheck, a memory error detector
==1063== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==1063== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==1063== Command: qharvestd -F -c/tmp/qharvestd.conf
==1063== 
==1063== 
==1063== Process terminating with default action of signal 4 (SIGILL)
==1063==  Illegal opcode at address 0x3807472C
==1063==at 0x4000930: _start (in /lib/ld-uClibc.so.0)
==1063== 
==1063== HEAP SUMMARY:
==1063== in use at exit: 0 bytes in 0 blocks
==1063==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==1063== 
==1063== All heap blocks were freed -- no leaks are possible
==1063== 
==1063== For counts of detected and suppressed errors, rerun with: -v
==1063== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Illegal instruction

Almost the same with cachegrind:
admin@RT-AC5300-0810:/tmp/home/root# valgrind  --tool=cachegrind qharvestd -F
-c/tmp/qharvestd.conf
==1061== Cachegrind, a cache and branch-prediction profiler
==1061== Copyright (C) 2002-2015, and GNU GPL'd, by Nicholas Nethercote et al.
==1061== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==1061== Command: qharvestd -F -c/tmp/qharvestd.conf
==1061== 
--1061-- Warning: Cannot auto-detect cache config, using defaults.
--1061--  Run with -v to see.
==1061== 
==1061== Process terminating with default action of signal 4 (SIGILL)
==1061==  Illegal opcode at address 0x38047DF8
==1061==at 0x4000930: _start (in /lib/ld-uClibc.so.0)
==1061== 
==1061== I   refs:  0
==1061== I1  misses:0
==1061== LLi misses:0
==1061== I1  miss rate: 0.00%
==1061== LLi miss rate: 0.00%
==1061== 
==1061== D   refs:  0  (0 rd   + 0 wr)
==1061== D1  misses:0  (0 rd   + 0 wr)
==1061== LLd misses:0  (0 rd   + 0 wr)
==1061== D1  miss rate: 0.0% (0.0% + 0.0%  )
==1061== LLd miss rate: 0.0% (0.0% + 0.0%  )
==1061== 
==1061== LL refs:   0  (0 rd   + 0 wr)
==1061== LL misses: 0  (0 rd   + 0 wr)
==1061== LL miss rate:  0.0% (0.0% + 0.0%  )
Illegal instruction

admin@RT-AC5300-0810:/tmp/home/root# cat /proc/cpuinfo
Processor   : ARMv7 Processor rev 0 (v7l)
processor   : 0
BogoMIPS: 2798.38

processor   : 1
BogoMIPS: 2798.38

Features: swp half thumb fastmult edsp 
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part: 0xc09
CPU revision: 0

Hardware: Northstar Prototype
Revision: 
Serial  : 


The only change I introduced in the source code is in configure script: armv7*)
-> arm*). Without this change configure fails.

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


[kate] [Bug 362458] Kate crashed, when in open file dialog try to create folder

2016-04-29 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362458

--- Comment #1 from Sergey  ---
Also bug reproduced in kwrite, but not reproduced in kdevelop.

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


[kate] [Bug 362458] New: Kate crashed, when in open file dialog try to create folder

2016-04-29 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362458

Bug ID: 362458
   Summary: Kate crashed, when in open file dialog try to create
folder
   Product: kate
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: li...@mail.by

Application: kate (15.08.3)

Qt Version: 5.5.1
Operating System: Linux 4.4.6-201.fc22.x86_64 x86_64
Distribution: "Fedora release 22 (Twenty Two)"

-- Information about the crash:
What I was doing when the application crashed:
1. Choose File -> Open...
2. In opened dialog (kde based) press right mouse button on file list
3. In popup menu choose Create -> New Folder ...
Kate crashed

The crash can be reproduced every time.

-- Backtrace:
Application: Kate (kate), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#5  0x7f13a5c7cce3 in KNewFileMenuPrivate::_k_slotActionTriggered(QAction*)
() from /lib64/libKF5KIOFileWidgets.so.5
#6  0x7f13a5c81220 in KNewFileMenu::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () from /lib64/libKF5KIOFileWidgets.so.5
#7  0x7f13a02b129a in QMetaObject::activate(QObject*, int, int, void**) ()
from /lib64/libQt5Core.so.5
#8  0x7f13a18bdd0f in QActionGroup::triggered(QAction*) () from
/lib64/libQt5Widgets.so.5
#9  0x7f13a18be989 in QActionGroup::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () from /lib64/libQt5Widgets.so.5
#10 0x7f13a02b129a in QMetaObject::activate(QObject*, int, int, void**) ()
from /lib64/libQt5Core.so.5
#11 0x7f13a18ba7d2 in QAction::triggered(bool) () from
/lib64/libQt5Widgets.so.5
#12 0x7f13a18bcc58 in QAction::activate(QAction::ActionEvent) () from
/lib64/libQt5Widgets.so.5
#13 0x7f13a1a3f5a2 in
QMenuPrivate::activateCausedStack(QList const&, QAction*,
QAction::ActionEvent, bool) () from /lib64/libQt5Widgets.so.5
#14 0x7f13a1a4585c in QMenuPrivate::activateAction(QAction*,
QAction::ActionEvent, bool) () from /lib64/libQt5Widgets.so.5
#15 0x7f13a1a497a0 in QMenu::mouseReleaseEvent(QMouseEvent*) () from
/lib64/libQt5Widgets.so.5
#16 0x7f13a1907418 in QWidget::event(QEvent*) () from
/lib64/libQt5Widgets.so.5
#17 0x7f13a1a4a1e3 in QMenu::event(QEvent*) () from
/lib64/libQt5Widgets.so.5
#18 0x7f13a18c441c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#19 0x7f13a18c9fe9 in QApplication::notify(QObject*, QEvent*) () from
/lib64/libQt5Widgets.so.5
#20 0x7f13a028273b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#21 0x7f13a18c8ef2 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () from
/lib64/libQt5Widgets.so.5
#22 0x7f13a1921cdd in QWidgetWindow::handleMouseEvent(QMouseEvent*) () from
/lib64/libQt5Widgets.so.5
#23 0x7f13a1923f3b in QWidgetWindow::event(QEvent*) () from
/lib64/libQt5Widgets.so.5
#24 0x7f13a18c441c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#25 0x7f13a18c98e6 in QApplication::notify(QObject*, QEvent*) () from
/lib64/libQt5Widgets.so.5
#26 0x7f13a028273b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#27 0x7f13a111aeb1 in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
() from /lib64/libQt5Gui.so.5
#28 0x7f13a111cb75 in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
() from /lib64/libQt5Gui.so.5
#29 0x7f13a1100918 in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() from /lib64/libQt5Gui.so.5
#30 0x7f138cb5f0b0 in userEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5XcbQpa.so.5
#31 0x7f139b8d4a8a in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#32 0x7f139b8d4e20 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#33 0x7f139b8d4ecc in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#34 0x7f13a02d8eaf in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#35 0x7f13a027feca in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#36 0x7f13a1a445a0 in QMenu::exec(QPoint const&, QAction*) () from
/lib64/libQt5Widgets.so.5
#37 0x7f13a5c3c7cc in KDirOperator::activatedMenu(KFileItem const&, QPoint
const&) () from /lib64/libKF5KIOFileWidgets.so.5
#38 0x7f13a5c38c55 in KDirOperator::Private::_k_openContextMenu(QPoint
const&) () from /lib64/libKF5KIOFileWidgets.so.5
#39 0x7f13a5c3fa2c in KDirOperator::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () from /lib64/libKF5KIOFileWidgets.so.5
#40 

[gcompris] [Bug 357575] Lines in "Click and draw" activity are drawn askew

2016-01-06 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357575

Sergey  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/gcom
   ||pris/b0cd46b60bea1272aedb47
   ||072de4a6f55f96616c

--- Comment #1 from Sergey  ---
Git commit b0cd46b60bea1272aedb47072de4a6f55f96616c by Sergey Popov.
Committed on 06/01/2016 at 19:45.
Pushed by sergobot into branch 'master'.

Fix bug with ugly lines in Click and draw activity
REVIEW:126649

M  +3-0src/activities/drawnumber/drawnumber.js

http://commits.kde.org/gcompris/b0cd46b60bea1272aedb47072de4a6f55f96616c

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


[gcompris] [Bug 357575] New: Lines in "Click and draw" activity are drawn askew

2016-01-05 Thread Sergey via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357575

Bug ID: 357575
   Summary: Lines in "Click and draw" activity are drawn askew
   Product: gcompris
   Version: git master
  Platform: Archlinux Packages
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: bruno.coud...@gcompris.net
  Reporter: sergo...@protonmail.com

When I finish drawing in "Click and draw" activity appears an image which makes
the drawing more understandable but my lines are drawn on the image, not
borders.
This issue is very noticeably in the second, the third, the fifth and the sixth
levels.

Reproducible: Always

Steps to Reproduce:
1. Draw lines by clicking on blue points.
2. Once you finish that, an image appears and lines don't fit it correctly.

Actual Results:  
I have mentioned above.

Expected Results:  
Lines fit the image correctly.

Tested on Archlinux and Android but the bug exists on all the supported
platforms and OSes.

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