[Breeze] [Bug 355540] Tooltips color wrong in gtk applications

[郭云鹤]

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

--- Comment #14 from Guo Yunhe (郭云鹤)  ---
(In reply to scionicspectre from comment #13)
> I feel like the ideal solution would be to whitelist Oxygen and any other
> GTK themes that actually support KDE color schemes and ignore the rest when
> the 'Apply colors to non-Qt applications' option is checked. Then, when the
> Breeze theme generation script is mainlined possibly have that activated
> instead when Breeze is selected.
> 
> Whether that is easily detectable/implementable is another matter. Still,
> it's clear that with our approach to color themes in GTK going forward, the
> current approach won't work as intended.
> 
> In the meantime, you should untick that checkbox if you're using Breeze.
> That may be why 'unconfirmed' makes sense since this isn't necessarily a bug
> in the theme itself, but relates more closely to the Color KCM.

Your solution is good. But I still doult if here are some improvements can be
done in Breeze GTK theme itself.

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

[plasmashell] [Bug 363488] plasmashell freezes unpredictable

[Kott via KDE Bugzilla]

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

--- Comment #1 from Kott  ---
Well. I tried to clean ~/.cache. I tried to run fresh clean profile. It
freezes.
What should I do else?

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

[plasmashell] [Bug 363488] New: plasmashell freezes unpredictable

[Kott via KDE Bugzilla]

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

Bug ID: 363488
   Summary: plasmashell freezes unpredictable
   Product: plasmashell
   Version: 5.6.4
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: k...@kott.no-ip.biz
CC: bhus...@gmail.com, plasma-b...@kde.org

I've changed my distro from OS 13.2 with Qt 5.6 and plasma-workspace 5.6.0
(from repos) to OS Tumbleweed mostly due often freezes in plasmashell.
When there (on Tumblewwed) was Qt 5.5.x and even plasma 5.6.x there weren't any
freezes. Now it has Qt 5.6 and plasma 5.6.4, freezes came back...
I cannot realize the reasons or any what cause them, it simple freeze
occasional in random time without any user action.

Reproducible: Sometimes

Steps to Reproduce:
1. Run plasma5-workspace.
2. Do something, or do nothing, just wait.


Actual Results:  
3. Plasma panel and desktop stops responding to mouse clicks.

Expected Results:  
plasmashell should work

NAME=openSUSE
VERSION="Tumbleweed"
VERSION_ID="20160520"
PRETTY_NAME="openSUSE Tumbleweed (20160520) (x86_64)"

Linux Kot 4.5.4-1-default #1 SMP PREEMPT Wed May 11 15:23:21 UTC 2016 (db90c25)
x86_64 x86_64 x86_64 GNU/Linux

NVIDIA Driver Version: 364.19

Name: libQt5Core5
Version : 5.6.0

Name: plasma5-workspace
Version : 5.6.4

gdb trace:
http://pastebin.com/kmuTyNeP

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

[plasmashell] [Bug 362941] Java Process Is Unresponsive In System Tray - Jitsi

[via KDE Bugzilla]

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

kdebugs.anon...@yahoo.com changed:

   What|Removed |Added

 CC||kdebugs.anon...@yahoo.com

--- Comment #2 from kdebugs.anon...@yahoo.com ---
I am experiencing EXACLTY the same problem as vindica...@live.com with Jitsi
2.8.5426on openSUSE Leap 42.1.  I installed Jitsi from the Stable Builds
repository at:
https://download.jitsi.org/jitsi/rpm/

This is very frustrating because I depend on Jitsi heavily, and KTP is not a
suitable replacement, because it lacks SIP support.

My kded5 version is 5.21.0-12.1

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

[kdeconnect] [Bug 363439] No visible way of activating "findmyphone"

[Albert Vaca via KDE Bugzilla]

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

--- Comment #6 from Albert Vaca  ---
As I told you, this feature is not in its final form.  However, since Ubuntu is
already distributing it for some reason,  I'm thinking about releasing it as it
is. 

Note this won't be as feature-complete as dedicated solutions, at least for
now. We don't do any gps location detection or something fancy like that, just
ringing your phone so you can go and pick it up.

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

[kreversi] [Bug 341777] Kreversi crash at startup.

[Karl Krelove via KDE Bugzilla]

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

--- Comment #9 from Karl Krelove  ---
It seems to resolve the problem for me.

Karl

> -Original Message-
> From: Frederik Schwarzer via KDE Bugzilla
> [mailto:bugzilla_nore...@kde.org]
> Sent: Tuesday, May 24, 2016 12:55 PM
> To: kkrelo...@gmail.com
> Subject: [kreversi] [Bug 341777] Kreversi crash at startup.
> 
> https://bugs.kde.org/show_bug.cgi?id=341777
> 
> --- Comment #8 from Frederik Schwarzer  ---
> @oliver: Can you confirm that installing kde-games-core-declarative
> fixes the issue?
> 
> --
> You are receiving this mail because:
> You are on the CC list for the bug.


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

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

[krita] [Bug 363487] New: brush lags behind when making quick or long strokes

[William Kensinger via KDE Bugzilla]

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

Bug ID: 363487
   Summary: brush lags behind when making quick or long strokes
   Product: krita
   Version: 3.0 Release Candidate
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: will89...@gmail.com

Pretty much exactly what it says in the title. For whatever reason, Krita 3.0
RC1's  brushes simply don't seem to perform as quickly as 2.9.11's for me. 

Attempting to sketch in this version is clumsy to the point of near-unusability
for me, as the brush is a half-second to a full second behind whatever my hand
is doing. Drawing a line across the canvas results in waiting more than a
second for the line to catch up to the brush. 

The canvas in question is here 2970x1620, so it's not like it's excessively
large or anything.

>From what I've seen, the issue appears to effect inking and sketching brushes a
lot more than painting and mixing brushes, so I think it might possibly have
something to do with brush size variance. Additionally, the issue appears to
get much worse when working within multiple nested group layers, resulting in
even small movements lagging behind for anywhere from a 1/2 second to more than
a second.

Please, let me know if there's any additional information I could provide to
help get this bug fixed!

Reproducible: Always

Steps to Reproduce:
1. Select brush
2. Attempt to paint quickly on canvas
3. Witness brush lag

Actual Results:  
Did not draw swiftly and resposively.

Expected Results:  
Draw swiftly and resposively.

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

[muon] [Bug 306344] KNSBackend crash when switching views in MSC

[fortytwo via KDE Bugzilla]

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

fortytwo  changed:

   What|Removed |Added

 CC||gms2...@hotmail.de

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

[muon] [Bug 282923] Muon crash after trying to check for updates

[fortytwo via KDE Bugzilla]

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

fortytwo  changed:

   What|Removed |Added

 CC||gms2...@hotmail.de

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

[muon] [Bug 326193] Muon Software Center Crashes KDE-4.11

[fortytwo via KDE Bugzilla]

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

fortytwo  changed:

   What|Removed |Added

 CC||gms2...@hotmail.de

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

[muon] [Bug 291262] Logitheque Muon issue

[fortytwo via KDE Bugzilla]

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

fortytwo  changed:

   What|Removed |Added

 CC||gms2...@hotmail.de

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

[kdenlive] [Bug 363478] git master: existing play/pause action is lost, please add it back

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #1 from Jean-Baptiste Mardelle  ---
I think the "Play" action in fact behaves as Play/Pause. So assigning a
shortcut or button to it should allow you to do both actions, like spacebar
currently does

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

[kdenlive] [Bug 363479] git master: doesn't show any monitor overlays

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Jean-Baptiste Mardelle  ---
Yes, that was due a bug deleting some interface actions when customizing the
toolbars.
However everything goes back to normal if you restart Kdenlive. I have now
fixed the monitor context menu to not loose its options, but there might be
other menus / actions disappearing, let me know if you encounter further
problems.

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

[kdenlive] [Bug 363480] git master: "preview profile" setting in "Project Settings" dialog isn't part of the "Settings" tab but instead of the overall dialog

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/kden
   ||live/92236e3281caf6acf9e6aa
   ||4fbe2f60970b230667

--- Comment #1 from Jean-Baptiste Mardelle  ---
Git commit 92236e3281caf6acf9e6aa4fbe2f60970b230667 by Jean-Baptiste Mardelle.
Committed on 24/05/2016 at 23:05.
Pushed by mardelle into branch 'master'.

Fix preview profile in project settings dialog incorrect layout

M  +1-1src/project/dialogs/projectsettings.cpp
M  +64   -64   src/ui/projectsettings_ui.ui

http://commits.kde.org/kdenlive/92236e3281caf6acf9e6aa4fbe2f60970b230667

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

[Akonadi] [Bug 354056] Deleted emails stay, but greyed out

[via KDE Bugzilla]

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

--- Comment #39 from naworsk...@gmail.com ---
(In reply to Kim Lilliestierna from comment #38)
> This has been resolved in the latest kmail version (5.1.3) and  kde
> framework (5.18.0)

For me the problem persists in Kubuntu 16.04.
Versions:
kmail2/kontact 5.13
Akonadi 5.1.51
KDE Frameworks: 5.18.0

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

[kinfocenter] [Bug 347344] KInfoCenter crashes after click Energy Information

[Kai Uwe Broulik via KDE Bugzilla]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #33 from Kai Uwe Broulik  ---
While the underlying Qt bug is not fixed (the cursor shape changing causing a
crash on teardown) it was only exhibited by faulty behavior on our side. Thanks
for your feedback! Closing then.

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

[kdevelop] [Bug 343236] Crash after closing while loading project [CMakeCondition::isTrue]

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

Summary|Crash after closing while   |Crash after closing while
   |loading project |loading project
   ||[CMakeCondition::isTrue]

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

[kdevelop] [Bug 363269] Crash when projects contains *.txt file that is actually a binary file

[Milian Wolff via KDE Bugzilla]

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

Milian Wolff  changed:

   What|Removed |Added

 Resolution|--- |BACKTRACE
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #4 from Milian Wolff  ---
you are missing the attachement, I think. I cannot see it at least.

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

[konsole] [Bug 306062] konsolepart should provide default shortcut for increasing/decreasing font size

[via KDE Bugzilla]

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

--- Comment #11 from andydecle...@gmail.com ---
(In reply to Jekyll Wu from comment #4)
> So when I made the change, I didn't see enlarging/shrinking font size in a
> terminal as frequent operation.  Actually I still don't understand why .
> Could you give some use cases as explanation for that *frequent* need ?

I variously use my laptop up close in person, and from afar while it's plugged
into a television across the room. As it is, I have to use Konsole instead of
Yakuake when using from afar, due to this font size regression, and I am
constantly accidentally showing and hiding Yakuake.

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

[kcalcore] [Bug 363460] Crash in korganizer prevents Kontact from starting

[clivej via KDE Bugzilla]

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

--- Comment #1 from clivej  ---
This seems to be related to my Kolab account.  When I remove it, Kontact runs
fine, as soon as I add it back, korganizer crashes.

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

[kate] [Bug 344074] Tabs not movable

[Alain Laporte via KDE Bugzilla]

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

Alain Laporte  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #9 from Alain Laporte  ---
*** This bug has been confirmed by popular vote. ***

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

[dolphin] [Bug 363349] Video duration in Details Mode

[Alain Laporte via KDE Bugzilla]

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

Alain Laporte  changed:

   What|Removed |Added

 CC||alain@laporte.paris

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

[kdevelop] [Bug 363486] Crash when creating project from CMakeLists.txt

[Marius Trandafir via KDE Bugzilla]

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

Marius Trandafir  changed:

   What|Removed |Added

 CC||marius.tranda...@live.com

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

[Breeze] [Bug 355540] Tooltips color wrong in gtk applications

[via KDE Bugzilla]

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

--- Comment #13 from scionicspec...@gmail.com ---
I feel like the ideal solution would be to whitelist Oxygen and any other GTK
themes that actually support KDE color schemes and ignore the rest when the
'Apply colors to non-Qt applications' option is checked. Then, when the Breeze
theme generation script is mainlined possibly have that activated instead when
Breeze is selected.

Whether that is easily detectable/implementable is another matter. Still, it's
clear that with our approach to color themes in GTK going forward, the current
approach won't work as intended.

In the meantime, you should untick that checkbox if you're using Breeze. That
may be why 'unconfirmed' makes sense since this isn't necessarily a bug in the
theme itself, but relates more closely to the Color KCM.

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

[kdevelop] [Bug 363486] New: Crash when creating project from CMakeLists.txt

[Marius Trandafir via KDE Bugzilla]

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

Bug ID: 363486
   Summary: Crash when creating project from CMakeLists.txt
   Product: kdevelop
   Version: 4.6.0
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: trandafir_marius_valen...@yahoo.co.uk

Application: kdevelop (4.6.0)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.19.0-32-generic x86_64
Distribution: Linux Mint 17.3 Rosa

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

I was trying to import LLVM + Clang + LLDB using CMakeLists.txt.
The crash happened when the source files were parsed.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f65a5e6b7c0 (LWP 18580))]

Thread 10 (Thread 0x7f65895dd700 (LWP 18581)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f659edccffb in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x7f659edcd039 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x7f65a198b182 in start_thread (arg=0x7f65895dd700) at
pthread_create.c:312
#4  0x7f65a262e47d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 9 (Thread 0x7f6508207700 (LWP 18582)):
#0  0x7f65a262112d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f659c9f0fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f659c9f10ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f65a3a5a7be in QEventDispatcherGlib::processEvents
(this=0x7f6508c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#4  0x7f65a3a2c0af in QEventLoop::processEvents
(this=this@entry=0x7f6508206de0, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f65a3a2c3a5 in QEventLoop::exec (this=this@entry=0x7f6508206de0,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7f65a3928c5f in QThread::exec (this=this@entry=0x1e11910) at
thread/qthread.cpp:537
#7  0x7f65a3a0d823 in QInotifyFileSystemWatcherEngine::run (this=0x1e11910)
at io/qfilesystemwatcher_inotify.cpp:265
#8  0x7f65a392b32f in QThreadPrivate::start (arg=0x1e11910) at
thread/qthread_unix.cpp:349
#9  0x7f65a198b182 in start_thread (arg=0x7f6508207700) at
pthread_create.c:312
#10 0x7f65a262e47d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 8 (Thread 0x7f64f700 (LWP 18583)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x7f65a392b7f4 in wait (time=1000, this=0x32920b0) at
thread/qwaitcondition_unix.cpp:84
#2  QWaitCondition::wait (this=, mutex=0x329a7b0, time=1000) at
thread/qwaitcondition_unix.cpp:158
#3  0x7f659fa5fe52 in ?? () from /usr/lib/libkdevplatformlanguage.so.7
#4  0x7f65a392b32f in QThreadPrivate::start (arg=0x329a790) at
thread/qthread_unix.cpp:349
#5  0x7f65a198b182 in start_thread (arg=0x7f64f700) at
pthread_create.c:312
#6  0x7f65a262e47d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 7 (Thread 0x7f64d7fff700 (LWP 18616)):
#0  0x7f65a262112d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f659c9f0fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f659c9f10ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f65a3a5a7be in QEventDispatcherGlib::processEvents
(this=0x7f64d8003110, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#4  0x7f65a3a2c0af in QEventLoop::processEvents
(this=this@entry=0x7f64d7ffede0, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f65a3a2c3a5 in QEventLoop::exec (this=this@entry=0x7f64d7ffede0,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7f65a3928c5f in QThread::exec (this=this@entry=0x46af760) at
thread/qthread.cpp:537
#7  0x7f65a3a0d823 in QInotifyFileSystemWatcherEngine::run (this=0x46af760)
at io/qfilesystemwatcher_inotify.cpp:265
#8  0x7f65a392b32f in QThreadPrivate::start (arg=0x46af760) at
thread/qthread_unix.cpp:349
#9  0x7f65a198b182 in start_thread (arg=0x7f64d7fff700) at
pthread_create.c:312
#10 0x7f65a262e47d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 6 (Thread 0x7f64ddd00700 (LWP 18625)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f6599c9881d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f6599c98859 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f65a198b182 in start_thread (arg=0x7f64ddd00700) at
pthread_create.c:312
#4  0x7f65a262e47d in clone () at

[plasma-nm] [Bug 363485] VPN connections display the tun device in use.

[via KDE Bugzilla]

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

--- Comment #1 from hid...@gmx.de ---
Created attachment 99164
  --> https://bugs.kde.org/attachment.cgi?id=99164=edit
Screenshot illustrating the problem

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

[plasma-nm] [Bug 363485] New: VPN connections display the tun device in use.

[via KDE Bugzilla]

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

Bug ID: 363485
   Summary: VPN connections display the tun device in use.
   Product: plasma-nm
   Version: 5.6.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: applet
  Assignee: jgrul...@redhat.com
  Reporter: hid...@gmx.de
CC: lu...@kde.org

When using VPN connections, plasma-nm also displays the tunnel device that is
used (see screenshot). I did not check whether the problem also occurs with
connections that use a tap-device.

Reproducible: Always

Steps to Reproduce:
1. Activate a VPN connection that uses a tun-device.

Actual Results:  
Additionaly to the activated connection the applet displays a connection for
the tun-device (e.g. tun0). Disconnecting this connection breaks the VPN
without clearing routes, so that its not possible to access the internet
anymore.

Expected Results:  
Only one entry should be displayed.

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

[plasmashell] [Bug 363484] New: Locale settings not recognized by krusader

[via KDE Bugzilla]

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

Bug ID: 363484
   Summary: Locale settings not recognized by krusader
   Product: plasmashell
   Version: 5.6.4
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: slartibar...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

My locale settings are setup as follows:
$ locale
LANG=en_US.utf8
LC_CTYPE="en_US.utf8"
LC_NUMERIC=nds_DE.UTF-8
LC_TIME=de_DE
LC_COLLATE=nds_DE.UTF-8
LC_MONETARY=nds_DE.UTF-8
LC_MESSAGES="en_US.utf8"
LC_PAPER="en_US.utf8"
LC_NAME="en_US.utf8"
LC_ADDRESS="en_US.utf8"
LC_TELEPHONE="en_US.utf8"
LC_MEASUREMENT=nds_DE.UTF-8
LC_IDENTIFICATION="en_US.utf8"
LC_ALL=

I also want to start some programs using a different locale, which i typically
do like this:
LC_TIME=de_DE.UTF8 dolphin 
or
LC_TIME=de_DE.UTF8 thunderbird

Krusader does not respect the LC_TIME setting as wanted and shows en_US style
timestamps in its main panels
It does, however, switch over to the german timestamp style if i start it like
this:
LC_ALL=de_DE.UTF8 krusader 
but then, the whole user-interface of krusader is in german.

Please fix this bug or provide an alternative ISO-8601 timestamp format as a
default

Reproducible: Always

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

[kdenlive] [Bug 363404] git master: trying to load a saved title crashes Kdenlive

[via KDE Bugzilla]

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

wegwerf-1-...@gmx.de changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from wegwerf-1-...@gmx.de ---
This is fixed, thank you very much, Jean-Baptiste!

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

[krita] [Bug 363415] (File) Toolbar doesn't display correctly

[Lake via KDE Bugzilla]

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

--- Comment #2 from Lake  ---
In version 2.9.11 , it will display the text name or the nick name you set for
it (maybe an icon, too - never tried it). So, the button originally said "reset
zoom" which I renamed to something shorter. In 3.0 , it doesn't show anything
or give an option to nick name it (the "change icon" and "change text" buttons
are not under the "current actions" list anymore) - your only option for
options without a default icon seems to be an empty box.

Here's a side by side comparison of what I'm talking about:
http://i.imgur.com/bPwidPp.jpg
The dark skinned one is 3.0 - the light skinned one is 2.9.11 .

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

[Spectacle] [Bug 363483] New: Problematic defaults, could be much better, thanks

[Ganton via KDE Bugzilla]

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

Bug ID: 363483
   Summary: Problematic defaults, could be much better, thanks
   Product: Spectacle
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: ku...@gmx.com

Dear Sirs:

Thanks. Spectacle doesn't work like other KDE programs, which lead to
inconsistencies and bad reviews. Advanced users could be able to modify
settings, but default Spectacle settings could work like other KDE programs.

The default settings that Spectacle has worsens reviews:
"To capture this moment, I used Spectacle, the new KDE tool for screenshots,
and boy is it bad. It is configured by default to grab the mouse cursor but not
the window decorations [window titlebar, borders], and you must drop-down the
save button to get to the Save As option. Also, it does not prompt on file
overwrites. Purely pointless, as they say. Why. How about some consistency,
chaps? "
"[...] PAM! Spectacle would not remember the last save location". 
-- http://www.dedoimedo.com/computers/kubuntu-xerus.html

‎Nonetheless, Spectacle has good work in it, keep up the good work! Thanks!

Reproducible: Always

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

[kdevelop] [Bug 298511] Change returned type of static function in it's definition (cpp file) made remove word "static" in it's declaration (header)

[Milian Wolff via KDE Bugzilla]

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

--- Comment #9 from Milian Wolff  ---
Git commit b37f668452c3727b6a9835096d1a11f74bdb8e54 by Milian Wolff.
Committed on 24/05/2016 at 21:02.
Pushed by mwolff into branch '5.0'.

Keep contexts alive when referenced by a problem.

This fixes the signature assistant when invoked from the header.
Now that we update the .cpp file when the header is changed, we
lost the declarations therein if e.g. the function return type got
changed. That then leads to issues in the signature assistant which
relies on the DUChain data.

I wonder whether we can find a more reliable way to store this data
to remove such kind of hacks... Problably we will have to work with
upstream clang and add FixIts for the signature assistant there
somehow...
Related: bug 358479

Differential Revision: https://phabricator.kde.org/D1140

M  +4-0languages/clang/codegen/adaptsignatureassistant.cpp
M  +37   -7languages/clang/duchain/builder.cpp
M  +15   -0languages/clang/tests/test_assistants.cpp

http://commits.kde.org/kdevelop/b37f668452c3727b6a9835096d1a11f74bdb8e54

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

[umbrello] [Bug 60452] missing keywords for declaring operations and variables

[Ralf Habacker via KDE Bugzilla]

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

--- Comment #11 from Ralf Habacker  ---
Git commit 0340c1bc39464f235ad883536f5e071b2e0beb0c by Ralf Habacker.
Committed on 24/05/2016 at 21:01.
Pushed by habacker into branch 'master'.

Refactor out data type property widget related code from attribute and
operation dialog into class UMLDatatypeWidget.

This makes it easier to implemented further data type widget related
extensions.

M  +1-0umbrello/CMakeLists.txt
M  +4-44   umbrello/dialogs/umlattributedialog.cpp
M  +3-8umbrello/dialogs/umlattributedialog.h
M  +4-57   umbrello/dialogs/umloperationdialog.cpp
M  +2-2umbrello/dialogs/umloperationdialog.h
A  +166  -0umbrello/dialogs/widgets/umldatatypewidget.cpp [License: GPL
(v2+)]
A  +44   -0umbrello/dialogs/widgets/umldatatypewidget.h [License: GPL
(v2+)]

http://commits.kde.org/umbrello/0340c1bc39464f235ad883536f5e071b2e0beb0c

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

[kdevelop] [Bug 358479] update signature assistant broken

[Milian Wolff via KDE Bugzilla]

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

--- Comment #1 from Milian Wolff  ---
Git commit b37f668452c3727b6a9835096d1a11f74bdb8e54 by Milian Wolff.
Committed on 24/05/2016 at 21:02.
Pushed by mwolff into branch '5.0'.

Keep contexts alive when referenced by a problem.

This fixes the signature assistant when invoked from the header.
Now that we update the .cpp file when the header is changed, we
lost the declarations therein if e.g. the function return type got
changed. That then leads to issues in the signature assistant which
relies on the DUChain data.

I wonder whether we can find a more reliable way to store this data
to remove such kind of hacks... Problably we will have to work with
upstream clang and add FixIts for the signature assistant there
somehow...
Related: bug 298511

Differential Revision: https://phabricator.kde.org/D1140

M  +4-0languages/clang/codegen/adaptsignatureassistant.cpp
M  +37   -7languages/clang/duchain/builder.cpp
M  +15   -0languages/clang/tests/test_assistants.cpp

http://commits.kde.org/kdevelop/b37f668452c3727b6a9835096d1a11f74bdb8e54

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

[kate] [Bug 363482] Toolview vsizing can lead to widget clipping in the Search & Replace view

[RJVB via KDE Bugzilla]

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

--- Comment #2 from RJVB  ---
Created attachment 99163
  --> https://bugs.kde.org/attachment.cgi?id=99163=edit
Widget clipping under X11 with the Breeze style

I first thought this glitch was related to the sizing/misalignment issues that
occur with the Mac native theme, but clearly that's not the case.

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

[kate] [Bug 363482] Toolview vsizing can lead to widget clipping in the Search & Replace view

[RJVB via KDE Bugzilla]

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

--- Comment #1 from RJVB  ---
Created attachment 99162
  --> https://bugs.kde.org/attachment.cgi?id=99162=edit
Clipped widgets on OS X with the native Macintosh QPA and widget style

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

[kate] [Bug 363482] New: Toolview vsizing can lead to widget clipping in the Search & Replace view

[RJVB via KDE Bugzilla]

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

Bug ID: 363482
   Summary: Toolview vsizing can lead to widget clipping in the
Search & Replace view
   Product: kate
   Version: unspecified
  Platform: Compiled Sources
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: search
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: rjvber...@gmail.com

The toolview area under the edit view and statusbar can be sized vertically
which is useful for certain toolviews. Not all tools are equally robust
however; the Search & Replace toolview doesn't set a minimal vertical size that
allows all widgets to be drawn at their normal size. See the attached
screenshots.


Reproducible: Always

Steps to Reproduce:
1. Open Kate5
2. Activate the Search & Replace view, in the advanced mode ("Search in",
Filter:, Exclude:)
3. Downsize the toolview area to its minimal height

Actual Results:  
See the screenshots. The widgets in the advanced view get clipped.

Expected Results:  
The minimal height should be dictated by the visible widgets

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

[KBibTeX] [Bug 351199] kbibtex crashes on startup when using git revision 600c246

[Gandalf Lechner via KDE Bugzilla]

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

Gandalf Lechner  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #12 from Gandalf Lechner  ---
Thanks a lot, this indeed fixed the crash! :-)

Now kbibtex starts fine; the only problem is that it seems not to be able to
load pdf previews (which worked fine in the 0.6 version). It says "Don't know
how to show mimetype application/pdf" ... but that is probably an unrelated
issue.

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

[krunner] [Bug 352785] Krunner is slow making it unusable

[Facundo Aguilera via KDE Bugzilla]

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

Facundo Aguilera  changed:

   What|Removed |Added

 CC||budin...@gmail.com

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

[kdenlive] [Bug 358390] Main Toolbar improvement suggestion: make main top menu a "Menu" button in the main toolbar (graphical mock-up included)

[Jesse via KDE Bugzilla]

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

--- Comment #6 from Jesse  ---
Thanks for the suggestion Paul. I'll definitely do that from now on. :)

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

[plasmashell] [Bug 363337] Recent docs/history shortcuts in kicker/kickoff fail when clicked with "Could not find any application or handler..." error

[David Faure via KDE Bugzilla]

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

--- Comment #10 from David Faure  ---
Git commit 9c1c48161416a2dd70fdb1dfeb92ed0b7dde75d9 by David Faure.
Committed on 24/05/2016 at 19:48.
Pushed by dfaure into branch 'master'.

Give clearer error message when KRun(URL) is given a URL without scheme.

M  +4-3src/widgets/krun.cpp

http://commits.kde.org/kio/9c1c48161416a2dd70fdb1dfeb92ed0b7dde75d9

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

[i18n] [Bug 355167] No french translation when I drop a file/folder onto itself in dolphin

[Neros via KDE Bugzilla]

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

--- Comment #2 from Neros  ---
@Raphaël Jakse: I agree.

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

[KBibTeX] [Bug 351199] kbibtex crashes on startup when using git revision 600c246

[Thomas Fischer via KDE Bugzilla]

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

Thomas Fischer  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |WAITINGFORINFO

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

[KBibTeX] [Bug 351199] kbibtex crashes on startup when using git revision 600c246

[Thomas Fischer via KDE Bugzilla]

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

Thomas Fischer  changed:

   What|Removed |Added

  Latest Commit||75b13672d7f3e300e5fedd4433e
   ||68f6ce2d05100

--- Comment #11 from Thomas Fischer  ---
The problem may have been caused by the premature establishment of signal-slot
connections in the FilterBar class. I rearranged this code section in the
lastest commit:
http://commits.kde.org/kbibtex/75b13672d7f3e300
Please test if the crash has been fixed.

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

[kdialog] [Bug 355571] Can't select a folder with an accent in its path in the left panel

[Neros via KDE Bugzilla]

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

--- Comment #2 from Neros  ---
This bug is only true when kdialog is opened with Chromium.

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

[plasma-pa] [Bug 355166] Plasmashell crashes because of plasma-pa when I click on settings a second time

[Neros via KDE Bugzilla]

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

Neros  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #6 from Neros  ---
This bug is fixed for a while.

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

[Planet KDE] [Bug 359327] Exiting game a in Steam Big Picture Mode gets semi-windowed BPM

[Neros via KDE Bugzilla]

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

Neros  changed:

   What|Removed |Added

 CC||cont...@neros.fr

--- Comment #3 from Neros  ---
I can confirm the behavior too. Running on Arch.

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

[kdelibs] [Bug 363431] kontact crashes when closing

[Herr Schmidt via KDE Bugzilla]

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

--- Comment #4 from Herr Schmidt  ---
Dear Allan Winter,

thanks for the patch and your help! Unluckily I don't know how to use
it. What will it do?

And I wanted to link to the other problems in this installation as they
might be connected(?).

* akonadi-backend-mysql: errors in selftest 5,16,17; maybe connection to
severe unstability of my system? Debian Bug#825224
* dolphin 15.08.3: Crashes randomly and frequently Debian Bug#808244
* Search emails in Kmail/Kontact gives no results although it should.
* kdeinit5 sometimes crashes before log out.
* Krunner crashes regularly (segmentation fault) with no visible reason
as well. I have to restart it manually. Sometimes even the starter and
the control bar crash leaving me unoperable. No Bug report yet as there
are no debug symbols available.
* VLC does'nt start related somehow to the Qt Interface plus purge VLC
wants to uninstall essential KDE stuff. Debian Bug#825140

Thanks alot again! I am a little bit in a despair by now.
Maria

Allen Winter via KDE Bugzilla:
> https://bugs.kde.org/show_bug.cgi?id=363431
> 
> --- Comment #3 from Allen Winter  ---
> I just attached a patch that might fix this crash.  I am unable to reproduce
> the crash, however.
> 
> Herr Schmidt, maybe you can test it ?
>

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

[kdenlive] [Bug 343322] Workspace layout is not remembered / saved to project KF5

[Hendric Stattmann via KDE Bugzilla]

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

--- Comment #28 from Hendric Stattmann  ---
Just gave it a try with kdenlive-16.04.1-1.4.x86_64 (Packman package on
OpenSUSE Tumbleweed). Seems to work fine now!

Kind regards,
Hendric

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

[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar

[via KDE Bugzilla]

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

--- Comment #26 from robsp...@fastmail.fm ---
What do you mean with "fixable by using xf86-video-intel and mesa-libgl"? I am
running Intel HD4400 graphics and still the problem occurs.

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

[kdenlive] [Bug 363480] New: git master: "preview profile" setting in "Project Settings" dialog isn't part of the "Settings" tab but instead of the overall dialog

[via KDE Bugzilla]

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

Bug ID: 363480
   Summary: git master: "preview profile" setting in "Project
Settings" dialog isn't part of the "Settings" tab but
instead of the overall dialog
   Product: kdenlive
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: wegwerf-1-...@gmx.de

In the "Project Settings" dialog, the "Preview profile" configuration UI
elements do not belong to the "Settings" tab as it is (probably) to be
expected. Instead, these UI elements belong to the overall dialog. Thus, when
switching tabs, the preview profile setting is always shown. Instead, it should
only be shown for the "Settings" tab, but not for "Metadata" in particular, but
even not for "Project Files" too.

Reproducible: Always

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

[kdenlive] [Bug 360174] Segmentation fault when using title clips

[via KDE Bugzilla]

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

--- Comment #17 from wegwerf-1-...@gmx.de ---
I actually tripped onto 363404 just two days ago or so, so I knew immediately
when you wrote that you get the crash not on exiting the titler but instead on
loading a previously saved titler.

As for the bug history I would also opt for closing it unless the original
reporter can reproduce it even with the fixes in place.

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

[kdenlive] [Bug 363481] New: git master: preview render progress estimation is 99h and way off...

[via KDE Bugzilla]

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

Bug ID: 363481
   Summary: git master: preview render progress estimation is 99h
and way off...
   Product: kdenlive
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: wegwerf-1-...@gmx.de

The title says it all: when a preview rendering runs, the e.t.a. shows 99h
albeit rendering may take around half an hour or at least less than one hour.
But definitely not 99h hours, unless Kdenlive can predict some unpleasant
future I'm not aware of yet... ;)

Reproducible: Always

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

[kdenlive] [Bug 360174] Segmentation fault when using title clips

[Hendric Stattmann via KDE Bugzilla]

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

--- Comment #16 from Hendric Stattmann  ---
Dear wegferf,

You are so right! I mistakenly ran into this bug, instead of 363404. 
Therefore, if no other objection arises, this bug here can be closed.

I am also very happy to see that a fix was committed for 363404 as well, so I
can start editing my footage again soon.

With regards,
Hendric

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

[kdenlive] [Bug 363479] New: git master: doesn't show any monitor overlays

[via KDE Bugzilla]

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

Bug ID: 363479
   Summary: git master: doesn't show any monitor overlays
   Product: kdenlive
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: wegwerf-1-...@gmx.de

With the recent git master and after I had deleted my old kdenliveui.rc the
monitors don't show any (enabled) overlays anymore. In addition, the monitor
context/hamburger menus have lost all options for showing/hiding overlays,
except for overlay audio waveform.

Reproducible: Always

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

[krita] [Bug 363470] Krita crashes after drag specific *.kra over the canvas to insert as layers

[Raghavendra kamath via KDE Bugzilla]

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

Raghavendra kamath  changed:

   What|Removed |Added

 CC||raghavendr.ra...@gmail.com

--- Comment #4 from Raghavendra kamath  ---
I can reproduce this with the file that David shared.

here is a back trace from Dr. qonqi


Application: Krita (krita), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f78b6e51840 (LWP 29425))]

Thread 13 (Thread 0x7f789544a700 (LWP 29427)):
#0  0x7f78ae79d68d in poll () from /usr/lib/libc.so.6
#1  0x7f78a9bc3fd6 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f78a9bc40ec in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f78af5d86eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f78af58046a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f78af3a72f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f78aa9dfa65 in ?? () from /usr/lib/libQt5DBus.so.5
#7  0x7f78af3ac1d8 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f78ab091474 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f78ae7a669d in clone () from /usr/lib/libc.so.6

Thread 12 (Thread 0x7f788281a700 (LWP 29428)):
#0  0x7f78ab09709f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f78af3ad08b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f78af3a5d53 in QSemaphore::acquire(int) () from
/usr/lib/libQt5Core.so.5
#3  0x7f78b59d965d in KisTileDataPooler::waitForWork (this=0x7f78b5eb7ce0
<(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>) at
/home/raghu/kf5/src/krita/libs/image/tiles3/kis_tile_data_pooler.cc:165
#4  KisTileDataPooler::run (this=0x7f78b5eb7ce0 <(anonymous
namespace)::Q_QGS_s_instance::innerFunction()::holder>) at
/home/raghu/kf5/src/krita/libs/image/tiles3/kis_tile_data_pooler.cc:187
#5  0x7f78af3ac1d8 in ?? () from /usr/lib/libQt5Core.so.5
#6  0x7f78ab091474 in start_thread () from /usr/lib/libpthread.so.0
#7  0x7f78ae7a669d in clone () from /usr/lib/libc.so.6

Thread 11 (Thread 0x7f7882019700 (LWP 29429)):
#0  0x7f78ae7764fd in nanosleep () from /usr/lib/libc.so.6
#1  0x7f78af457e0d in ?? () from /usr/lib/libQt5Core.so.5
#2  0x7f78af3ab598 in QThread::msleep(unsigned long) () from
/usr/lib/libQt5Core.so.5
#3  0x7f78b59f4e7a in KisTileDataSwapper::run (this=0x7f78b5eb7d20
<(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder+64>) at
/home/raghu/kf5/src/krita/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:97
#4  0x7f78af3ac1d8 in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7f78ab091474 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7f78ae7a669d in clone () from /usr/lib/libc.so.6

Thread 10 (Thread 0x7f7881818700 (LWP 29432)):
#0  0x7f78ab09709f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f78af3ad08b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f78b04dc139 in ?? () from /usr/lib/libQt5Widgets.so.5
#3  0x7f78af3ac1d8 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7f78ab091474 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7f78ae7a669d in clone () from /usr/lib/libc.so.6

Thread 9 (Thread 0x7f7857fff700 (LWP 29565)):
#0  0x7f78ab097448 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f78af3acfc6 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f78af3a8644 in ?? () from /usr/lib/libQt5Core.so.5
#3  0x7f78af3ac1d8 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7f78ab091474 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7f78ae7a669d in clone () from /usr/lib/libc.so.6

Thread 8 (Thread 0x7f784d5fc700 (LWP 29566)):
#0  0x7f78ab097448 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f78af3acfc6 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f78af3a8644 in ?? () from /usr/lib/libQt5Core.so.5
#3  0x7f78af3ac1d8 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7f78ab091474 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7f78ae7a669d in clone () from /usr/lib/libc.so.6

Thread 7 (Thread 0x7f784edff700 (LWP 29567)):
#0  0x7f78ab097448 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f78af3acfc6 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f78af3a8644 in ?? () from /usr/lib/libQt5Core.so.5
#3  0x7f78af3ac1d8 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7f78ab091474 in start_thread () from /usr/lib/libpthread.so.0
#5  

[kdenlive] [Bug 363478] New: git master: existing play/pause action is lost, please add it back

[via KDE Bugzilla]

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

Bug ID: 363478
   Summary: git master: existing play/pause action is lost, please
add it back
   Product: kdenlive
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: wegwerf-1-...@gmx.de

So far, Kdenlive offered separate actions for "play zone", "play/pause", and
"pause". With recent git master, the action "play/pause" has been removed.
Please bring back "play/pause" which is quite useful, especially when working
with a ShuttlePro jog dial: this combined action requires only a single
physical button and physical buttons are rather limited in number on the
ShuttlePro.

Reproducible: Always

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

[kate] [Bug 363477] New: the vim mode is not working with kate after enable it

[Yakun Li via KDE Bugzilla]

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

Bug ID: 363477
   Summary: the vim mode is not working with kate after enable it
   Product: kate
   Version: 5.0.0
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Vi Input Mode
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: liyakun...@gmail.com

the vim mode is not working with kate after enable it

Reproducible: Always



Expected Results:  
The expected result is that I can use vim command to work like in kde4

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

[krita] [Bug 340948] Crash when undoing a 16 bits float to 8 bits color space conversion

[Raghavendra kamath via KDE Bugzilla]

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

Raghavendra kamath  changed:

   What|Removed |Added

 CC||raghavendr.ra...@gmail.com

--- Comment #8 from Raghavendra kamath  ---
I am on arch linux plasma 5 , with an updated build from git.
the image dimension is 5260x7440

I convert an already existing 16 bit document to 16 bit float , then converted
it to 8 bit , and then hit undo, it didn't crash for me.

It did take a long while and used all the 16 gb memeory and some swap while 
the process, 
I tried it several tried it didn't crash for me

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

[kdenlive] [Bug 360174] Segmentation fault when using title clips

[via KDE Bugzilla]

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

--- Comment #15 from wegwerf-1-...@gmx.de ---
Hendric, from your description  you seem to talk about a completely different
bug, this one in particular: https://bugs.kde.org/show_bug.cgi?id=363404 This
one has already been fixed.

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

[kdenlive] [Bug 360174] Segmentation fault when using title clips

[Hendric Stattmann via KDE Bugzilla]

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

--- Comment #14 from Hendric Stattmann  ---
Created attachment 99161
  --> https://bugs.kde.org/attachment.cgi?id=99161=edit
This is the title file I tried to open.

This is how I can reproduce the bug:
1) Open Kdenlive with an empty project
2) In the Project Bin, click on "Add title clip", title clip editor opens
3) Click on the "open file" icon, "file open" dialog appears
4) Select file to open, click OK
-> Crash.

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

[kdenlive] [Bug 360174] Segmentation fault when using title clips

[Hendric Stattmann via KDE Bugzilla]

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

--- Comment #13 from Hendric Stattmann  ---
Bonsoir Jean-Baptiste,

I can feel your pain! I know how frustrating it is to have a problem that was
believed to be solved to pop up again... Anyway, here is the gdb output:
http://pastebin.com/n6vdv6WK

Have fun!
Hendric

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

[krunner] [Bug 363476] New: krunner crashed when starting konsole

[Arthur Marsh via KDE Bugzilla]

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

Bug ID: 363476
   Summary: krunner crashed when starting konsole
   Product: krunner
   Version: 5.5.4
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: m...@vhanda.in
  Reporter: arthur.ma...@internode.on.net

Application: krunner (5.5.4)

Qt Version: 5.5.1
Operating System: Linux 4.6.0+ x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
- What I was doing when the application crashed:
attempted to start konsole with alt-F2 - krunner crashed and konsole didn't
start

The crash can be reproduced sometimes.

-- Backtrace:
Application: krunner (krunner), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7f511171b7c0 (LWP 29172))]

Thread 12 (Thread 0x7f5111058700 (LWP 29173)):
#0  0x0030004dfdcd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x00300380a382 in _xcb_conn_wait (__timeout=-1, __nfds=1,
__fds=0x7f5111057d00) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2  0x00300380a382 in _xcb_conn_wait (c=c@entry=0x10ca470,
cond=cond@entry=0x10ca4b0, vector=vector@entry=0x0, count=count@entry=0x0) at
../../src/xcb_conn.c:459
#3  0x00300380bff7 in xcb_wait_for_event (c=0x10ca470) at
../../src/xcb_in.c:693
#4  0x7f51114b7789 in QXcbEventReader::run() (this=0x10dd4c0) at
qxcbconnection.cpp:1230
#5  0x0030174a580e in QThreadPrivate::start(void*) (arg=0x10dd4c0) at
thread/qthread_unix.cpp:331
#6  0x003000c07454 in start_thread (arg=0x7f5111058700) at
pthread_create.c:334
#7  0x0030004e8e5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7f5107b57700 (LWP 29181)):
#0  0x003000c0d04f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f510b243693 in  () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#2  0x7f510b242db7 in  () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#3  0x003000c07454 in start_thread (arg=0x7f5107b57700) at
pthread_create.c:334
#4  0x0030004e8e5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7f5105fec700 (LWP 29187)):
#0  0x00301749dd8f in QMutex::unlock() (currentValue=,
newValue=0x0, expectedValue=0x1, _q_value=@0x1467048: 0x0) at
../../include/QtCore/../../src/corelib/arch/qatomic_x86.h:259
#1  0x00301749dd8f in QMutex::unlock() (currentValue=,
newValue=0x0, expectedValue=, _q_value=@0x1467048: 0x0) at
../../include/QtCore/../../src/corelib/thread/qgenericatomic.h:175
#2  0x00301749dd8f in QMutex::unlock() (currentValue=,
newValue=0x0, expectedValue=, this=this@entry=0x1467048) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:278
#3  0x00301749dd8f in QMutex::unlock() (current=,
this=this@entry=0x1467048) at thread/qmutex.h:85
#4  0x00301749dd8f in QMutex::unlock() (this=this@entry=0x1467048) at
thread/qmutex.cpp:264
#5  0x0030176dbff1 in postEventSourcePrepare(GSource*, gint*)
(this=) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:138
#6  0x0030176dbff1 in postEventSourcePrepare(GSource*, gint*)
(this=, __in_chrg=) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:132
#7  0x0030176dbff1 in postEventSourcePrepare(GSource*, gint*)
(this=0x1467020) at
../../include/QtCore/5.5.1/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:240
#8  0x0030176dbff1 in postEventSourcePrepare(GSource*, gint*)
(s=0x7f5112d0, timeout=timeout@entry=0x7f5105febc24) at
kernel/qeventdispatcher_glib.cpp:254
#9  0x003002c4992d in g_main_context_prepare
(context=context@entry=0x7f510990, priority=priority@entry=0x7f5105febcb0)
at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3442
#10 0x003002c4a2cb in g_main_context_iterate
(context=context@entry=0x7f510990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3820
#11 0x003002c4a4ac in g_main_context_iteration (context=0x7f510990,
may_block=may_block@entry=1) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3901
#12 0x0030176dca5b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f5108c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#13 0x003017683daa in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f5105febde0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#14 0x0030174a0864 in QThread::exec() (this=) at
thread/qthread.cpp:503
#15 0x0030556d5105 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#16 0x0030174a580e in QThreadPrivate::start(void*) (arg=0x1466ee0) at
thread/qthread_unix.cpp:331
#17 

[libkface] [Bug 358910] OpenCV 3.1 support for libkface

[Taurnil via KDE Bugzilla]

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

Taurnil  changed:

   What|Removed |Added

 CC||taurnil.oro...@gmail.com

--- Comment #2 from Taurnil  ---
Also ran into this problem using libkface-16.04.1. After realizing I needed
opencv_contrib-3.1.0 because I have libkface use -DENABLE_OPENCV3=1 I needed to
recompile opencv-3.1.0 with those contribs.  Here is the compile output without
the patch mentioned above;

Building libkface version 16.04.1
+ running "default_pre_build"
+ validating "/usr/src/libkface-16.04.1"
+ creating building dir "/usr/src/libkface-16.04.1"
+ Removing old source directory first!
+ Unpacking "/var/spool/lunar/libkface-16.04.1.tar.xz" in "/usr/src"
+ building "libkface" version "16.04.1" in /usr/src/libkface-16.04.1
+ CC_EXT="ccache "
+ CXX_EXT="ccache "
+ CC="gcc"
+ CXX="g++"
+ CPP="cpp"
+ CFLAGS=" -O2 -march=native -pipe"
+ CXXFLAGS=" -O2 -march=native -pipe"
+ CPPFLAGS=" -D_FORTIFY_SOURCE=2"
+ LDFLAGS=" -s"
+ Enabled wrapper script usage
+ running "default_cmake_build"
+ running "default_cmake_config"
+ MODULE_PREFIX="/usr"
+ running "Out of source build is required; configuring"
-- The C compiler identification is GNU 5.3.0
-- The CXX compiler identification is GNU 5.3.0
-- Check for working C compiler: /var/lib/lunar/compilers/gcc
-- Check for working C compiler: /var/lib/lunar/compilers/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /var/lib/lunar/compilers/g++
-- Check for working CXX compiler: /var/lib/lunar/compilers/g++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
--
--
-- Starting CMake configuration for: libkface
-- Looking for __GLIBC__
-- Looking for __GLIBC__ - found
-- Performing Test _OFFT_IS_64BIT
-- Performing Test _OFFT_IS_64BIT - Success
-- First try at finding OpenCV...
-- Great, found OpenCV on the first try.
-- OpenCV Root directory is: /usr/share/OpenCV
-- OpenCV: Found version 3.1.0 (required: 3.0.0)
-- OpenCV headers: /usr/include/opencv;/usr/include
-- OpenCV libs   :
opencv_core;opencv_face;opencv_highgui;opencv_objdetect;opencv_imgproc
-- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY
-- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY - Success
-- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY
-- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY - Success
-- Performing Test COMPILER_HAS_DEPRECATED_ATTR
-- Performing Test COMPILER_HAS_DEPRECATED_ATTR - Success

-- 
-- The following REQUIRED packages have been found:

 * ECM (required version >= 1.1.0)
 * Qt5Core
 * Qt5Widgets
 * Qt5Sql
 * Qt5Xml
 * Qt5Gui
 * Qt5 (required version >= 5.2.0)
 * OpenCV

-- Configuring done
-- Generating done
-- Build files have been written to: /usr/src/libkface-16.04.1/libkface-oosb
+ running "default_make"
Scanning dependencies of target extract_funnel_data
[  4%] Generating face-funnel.data
[  4%] Built target extract_funnel_data
Scanning dependencies of target KF5KFace_automoc
[  8%] Automatic moc for target KF5KFace
Generating moc_databasecorebackend.cpp
[  8%] Built target KF5KFace_automoc
Scanning dependencies of target KF5KFace
[ 12%] Building CXX object
src/CMakeFiles/KF5KFace.dir/detection/opencvfacedetector.cpp.o
[ 16%] Building CXX object
src/CMakeFiles/KF5KFace.dir/recognition-opencv-lbph/lbphfacemodel.cpp.o
In file included from
/usr/src/libkface-16.04.1/libkface-oosb/src/libopencv.h:59:0,
 from
/usr/src/libkface-16.04.1/src/recognition-opencv-lbph/lbphfacemodel.h:35,
 from
/usr/src/libkface-16.04.1/src/recognition-opencv-lbph/lbphfacemodel.cpp:30:
/usr/include/opencv2/face.hpp:308:18: warning: 'virtual void
cv::face::FaceRecognizer::predict(cv::InputArray,
cv::Ptr, int) const' was hidden
[-Woverloaded-virtual]
 CV_WRAP virtual void predict(InputArray src, Ptr
collector, const int state = 0) const = 0;
  ^
In file included from
/usr/src/libkface-16.04.1/src/recognition-opencv-lbph/lbphfacemodel.h:44:0,
 from
/usr/src/libkface-16.04.1/src/recognition-opencv-lbph/lbphfacemodel.cpp:30:
/usr/src/libkface-16.04.1/src/recognition-opencv-lbph/facerec_borrowed.h:136:10:
warning:   by 'KFaceIface::LBPHFaceRecognizer::predict' [-Woverloaded-virtual]
 void predict(cv::InputArray _src, int , double ) const;
  ^
[ 20%] Building CXX object
src/CMakeFiles/KF5KFace.dir/recognition-opencv-lbph/opencvlbphfacerecognizer.cpp.o
In file included from
/usr/src/libkface-16.04.1/libkface-oosb/src/libopencv.h:59:0,
 from

[kopete] [Bug 363053] Building kopete-16.04.0 with GCC-6.1.0 fails with "error: could not convert 'false' from 'bool' to 'const Kopete::MetaContact*'"

[via KDE Bugzilla]

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

--- Comment #4 from nsane...@gmail.com ---
(In reply to Luca Beltrame from comment #3)
> Please submit this patch through reviewboard.kde.org if possible. Patches
> through Bugzilla are likely to get lost.

Done:

https://git.reviewboard.kde.org/r/128006/

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

[krita] [Bug 345282] [WACOM CINTIQ] Cursor offset problem

[stephen via KDE Bugzilla]

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

stephen  changed:

   What|Removed |Added

 CC||phario...@gmail.com

--- Comment #7 from stephen  ---
Using a Wacom Cintiq 12wx as the second monitor

In the NVIDIA Control panel, if you select "Adjust desktop size and position"
then select the wacom monitor, if you tick the "Override the scaling mode set
by games and programs"

for a couple of seconds, the cursor is correctly positioned until for some
unknown reason, that option becomes un-ticked and you get the offset when the
pen is over the canvas again

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

[kreversi] [Bug 341777] Kreversi crash at startup.

[Frederik Schwarzer via KDE Bugzilla]

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

--- Comment #8 from Frederik Schwarzer  ---
@oliver: Can you confirm that installing kde-games-core-declarative fixes the
issue?

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

[krita] [Bug 361596] Crash when opening color space browser

[Friedrich W . H . Kossebau via KDE Bugzilla]

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

Friedrich W. H. Kossebau  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/krit |http://commits.kde.org/call
   |a/972a6eedfdd3fd4fe0e01c9fd |igra/59db91b27e001ed445e31c
   |466d7ad7761758a |a84920f034530244eb

--- Comment #5 from Friedrich W. H. Kossebau  ---
Git commit 59db91b27e001ed445e31ca84920f034530244eb by Friedrich W. H.
Kossebau, on behalf of Boudewijn Rempt.
Committed on 24/05/2016 at 15:30.
Pushed by kossebau into branch 'master'.
Related: bug 16

M  +13   -13   libs/pigment/KoColorSpace.cpp

http://commits.kde.org/calligra/59db91b27e001ed445e31ca84920f034530244eb

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

[grantlee] [Bug 363475] support i18n date formating (short form missing)

[Sandro Knauß via KDE Bugzilla]

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

Sandro Knauß  changed:

   What|Removed |Added

Summary|support i18n date formating |support i18n date formating
   ||(short form missing)

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

[grantlee] [Bug 363475] New: support i18n date formating

[Sandro Knauß via KDE Bugzilla]

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

Bug ID: 363475
   Summary: support i18n date formating
   Product: grantlee
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: steve...@gmail.com
  Reporter: skna...@kde.org

Using i18n support together with date formatting do not work, to select the
short/long datetime representation.
What I want is something like:
{{ _(adate) }} = Dienstag, 24.Mai 2016 15:51:32  
{{ _(adate|short) }} = 24.05.16 15:51

you only get the long representation for a date.

django suggests:
{{ value|date:"SHORT_DATE_FORMAT" }}

do not work too.

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

[krita] [Bug 344602] krita crashed while I tried to smooth path.

[Friedrich W . H . Kossebau via KDE Bugzilla]

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

Friedrich W. H. Kossebau  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/krit |http://commits.kde.org/call
   |a/af0b46495c8696fbeff89569b |igra/2bd10dab6b3c18af407df3
   |a391205adaf547b |829d6af61a56d0a58e

--- Comment #3 from Friedrich W. H. Kossebau  ---
Git commit 2bd10dab6b3c18af407df3829d6af61a56d0a58e by Friedrich W. H.
Kossebau, on behalf of Boudewijn Rempt.
Committed on 24/05/2016 at 14:13.
Pushed by kossebau into branch 'master'.

If we assert here, the user loses data, it's better to not set
the point in that case.

M  +4-2libs/flake/KoPathPoint.cpp

http://commits.kde.org/calligra/2bd10dab6b3c18af407df3829d6af61a56d0a58e

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

[krita] [Bug 363143] Crash while editing pattern fill of a vector object

[Friedrich W . H . Kossebau via KDE Bugzilla]

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

Friedrich W. H. Kossebau  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/krit |http://commits.kde.org/call
   |a/d8af54319129a0e505f1831e1 |igra/7070fa835cb079d4118ed3
   |f460c340af17b52 |f8cb4bd559ce328905

--- Comment #2 from Friedrich W. H. Kossebau  ---
Git commit 7070fa835cb079d4118ed3f8cb4bd559ce328905 by Friedrich W. H.
Kossebau, on behalf of Boudewijn Rempt.
Committed on 24/05/2016 at 16:38.
Pushed by kossebau into branch 'master'.

The ImageCollection is shared among all shapes, so on deleting a
shape, it shouldn't be deleted.

M  +0-1libs/flake/KoPatternBackground.cpp

http://commits.kde.org/calligra/7070fa835cb079d4118ed3f8cb4bd559ce328905

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

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

[Bruno de Souza Lino via KDE Bugzilla]

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

Bruno de Souza Lino  changed:

   What|Removed |Added

Version|3.0 Beta|3.0 Release Candidate

--- Comment #9 from Bruno de Souza Lino  ---
Confirmed to also exist on the appimage linux rc1 version of it.

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

[krita] [Bug 362623] double clicking on the canvas while hand tool is active changes the tool to shape handling tool

[Friedrich W . H . Kossebau via KDE Bugzilla]

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

Friedrich W. H. Kossebau  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/krit |http://commits.kde.org/call
   |a/c51dd6585857ff37602a729c3 |igra/61fb4955aba8f2dbc592b0
   |66188cdba059be9 |e9cf6d64f2c69729fe

--- Comment #4 from Friedrich W. H. Kossebau  ---
Git commit 61fb4955aba8f2dbc592b0e9cf6d64f2c69729fe by Friedrich W. H.
Kossebau, on behalf of Boudewijn Rempt.
Committed on 24/05/2016 at 16:38.
Pushed by kossebau into branch 'master'.

M  +6-0libs/flake/tools/KoPanTool.cpp
M  +3-0libs/flake/tools/KoPanTool.h

http://commits.kde.org/calligra/61fb4955aba8f2dbc592b0e9cf6d64f2c69729fe

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

[krita] [Bug 360895] Use the selection color to mark the current active tool in the toolbox

[Friedrich W . H . Kossebau via KDE Bugzilla]

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

Friedrich W. H. Kossebau  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/krit |http://commits.kde.org/call
   |a/441a6fa591cc71470712208c3 |igra/a372129071c6e10d01e9ab
   |6dd3e2937e6afd5 |2164e7b41147466d3a

--- Comment #3 from Friedrich W. H. Kossebau  ---
Git commit a372129071c6e10d01e9ab2164e7b41147466d3a by Friedrich W. H.
Kossebau, on behalf of Boudewijn Rempt.
Committed on 24/05/2016 at 14:18.
Pushed by kossebau into branch 'master'.

Use the highlight color for the selected tool

This also 'fixes' the setting of the highlight color in
the toolbar, we should be taking the app's palette, not the
one set on the current widget.

M  +2-0libs/widgets/KoToolBox.cpp
M  +15   -0libs/widgets/KoToolBoxButton.cpp
M  +1-0libs/widgets/KoToolBoxButton_p.h

http://commits.kde.org/calligra/a372129071c6e10d01e9ab2164e7b41147466d3a

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

[krita] [Bug 363470] Krita crashes after drag specific *.kra over the canvas to insert as layers

[Camille Bissuel via KDE Bugzilla]

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

Camille Bissuel  changed:

   What|Removed |Added

 CC||welc...@nylnook.com

--- Comment #3 from Camille Bissuel  ---
I can reproduce always under Antergos and Krita3 compiled today from Git

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

[systemsettings] [Bug 363474] New: Problems running multiple monitors

[Lester Caine via KDE Bugzilla]

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

Bug ID: 363474
   Summary: Problems running multiple monitors
   Product: systemsettings
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: les...@lsces.co.uk

Application: systemsettings (4.11.20)
KDE Platform Version: 4.14.9
Qt Version: 4.8.6
Operating System: Linux 3.16.7-35-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Trying to drag screen back to full size after it has reset itself to 1024x768
folloing a kvm switch of the attached monitor. Has done this several times now
which there had never been a problem with pre 13.2 setups.

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9270d62800 (LWP 2015))]

Thread 2 (Thread 0x7f92543df700 (LWP 2295)):
#0  0x7f9266f3403f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f926b5b78cb in  () at /usr/lib64/libQtScript.so.4
#2  0x7f926b5b7909 in  () at /usr/lib64/libQtScript.so.4
#3  0x7f9266f300a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f926dd1d00d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f9270d62800 (LWP 2015)):
[KCrash Handler]
#5  0x7f92543ee6f0 in KScreen::Mode::id() const () at
/usr/lib64/libkscreen.so.1
#6  0x7f925464cef1 in  () at /usr/lib64/kde4/kcm_kscreen.so
#7  0x7f926e47f1fa in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/libQtCore.so.4
#8  0x7f92546500d2 in  () at /usr/lib64/kde4/kcm_kscreen.so
#9  0x7f925465021b in  () at /usr/lib64/kde4/kcm_kscreen.so
#10 0x7f926e47f1fa in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/libQtCore.so.4
#11 0x7f926f74f04e in QAbstractSlider::valueChanged(int) () at
/usr/lib64/libQtGui.so.4
#12 0x7f926f540827 in QSlider::mouseMoveEvent(QMouseEvent*) () at
/usr/lib64/libQtGui.so.4
#13 0x7f926f154d35 in QWidget::event(QEvent*) () at
/usr/lib64/libQtGui.so.4
#14 0x7f926f10576c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQtGui.so.4
#15 0x7f926f10bdea in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQtGui.so.4
#16 0x7f926fe24e0a in KApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libkdeui.so.5
#17 0x7f926e46b2ad in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQtCore.so.4
#18 0x7f926f10b5e3 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at
/usr/lib64/libQtGui.so.4
#19 0x7f926f17cc9b in  () at /usr/lib64/libQtGui.so.4
#20 0x7f926f17b70c in QApplication::x11ProcessEvent(_XEvent*) () at
/usr/lib64/libQtGui.so.4
#21 0x7f926f1a25c2 in  () at /usr/lib64/libQtGui.so.4
#22 0x7f9266c63a04 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#23 0x7f9266c63c48 in  () at /usr/lib64/libglib-2.0.so.0
#24 0x7f9266c63cec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#25 0x7f926e4980be in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#26 0x7f926f1a2676 in  () at /usr/lib64/libQtGui.so.4
#27 0x7f926e469e6f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#28 0x7f926e46a165 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#29 0x7f926e46f5b9 in QCoreApplication::exec() () at
/usr/lib64/libQtCore.so.4
#30 0x0040b4bb in  ()
#31 0x7f926dc59b05 in __libc_start_main () at /lib64/libc.so.6
#32 0x0040b50c in _start ()

Reported using DrKonqi

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

[kinfocenter] [Bug 347344] KInfoCenter crashes after click Energy Information

[Luís Silva via KDE Bugzilla]

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

--- Comment #32 from Luís Silva  ---
Fixed on Fedora 23 also!

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

[kdelibs] [Bug 296810] KMultiTabBar: Does not correctly handle Mac font sizes

[RJVB via KDE Bugzilla]

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

RJVB  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
 CC||rjvber...@gmail.com

--- Comment #16 from RJVB  ---
https://git.reviewboard.kde.org/r/128005/

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

[krita] [Bug 362869] Shortcuts not working after Configure Krita

[Camille Bissuel via KDE Bugzilla]

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

Camille Bissuel  changed:

   What|Removed |Added

 CC||welc...@nylnook.com

--- Comment #4 from Camille Bissuel  ---
Sorry, the video is corrupted for me too, also with Firefox…

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

[krita] [Bug 351434] [AMD] Visibility of Liquify transformations of transform mask depends on view scaling size

[Camille Bissuel via KDE Bugzilla]

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

Camille Bissuel  changed:

   What|Removed |Added

 CC||welc...@nylnook.com

--- Comment #8 from Camille Bissuel  ---
I can reproduce it always on my linux station with open source amdgpu drivers,
specially at bigger zoom level, and with Wash mode. Quite unresponsive also.

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

[kdevelop] [Bug 363473] KDevelop should use a different tab bar widget for tabbed documents

[RJVB via KDE Bugzilla]

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

--- Comment #4 from RJVB  ---
Created attachment 99160
  --> https://bugs.kde.org/attachment.cgi?id=99160=edit
KDevelop5's tabbed document bar using the "wrong" tabbar widget and "lots" of
files open. Who's who?

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

[kdevelop] [Bug 363473] KDevelop should use a different tab bar widget for tabbed documents

[RJVB via KDE Bugzilla]

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

--- Comment #3 from RJVB  ---
Created attachment 99159
  --> https://bugs.kde.org/attachment.cgi?id=99159=edit
Xcode preferences window showing the modern tab bar style

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

[kdevelop] [Bug 363473] KDevelop should use a different tab bar widget for tabbed documents

[RJVB via KDE Bugzilla]

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

--- Comment #2 from RJVB  ---
Created attachment 99158
  --> https://bugs.kde.org/attachment.cgi?id=99158=edit
OS X Terminal.app preferences dialog showing appropriate use of the tabbar
widget

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

[kdevelop] [Bug 363473] KDevelop should use a different tab bar widget for tabbed documents

[RJVB via KDE Bugzilla]

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

--- Comment #1 from RJVB  ---
Created attachment 99157
  --> https://bugs.kde.org/attachment.cgi?id=99157=edit
KDevelop5 (background) and Kate5 (foreground) showing "wrong" and "right" tab
bar types when using the native Mac OS X qpa & theme

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

[kdevelop] [Bug 363473] New: KDevelop should use a different tab bar widget for tabbed documents

[RJVB via KDE Bugzilla]

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

Bug ID: 363473
   Summary: KDevelop should use a different tab bar widget for
tabbed documents
   Product: kdevelop
   Version: git master
  Platform: Compiled Sources
OS: OS X
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: documentview
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: rjvber...@gmail.com

KDevelop currently (still) uses a tab bar style which on OS X is rendered using
an inappropriate widget. This widget is intended only for use in dialogs where
the number of tabs is fixed and limited, like in the screenshot of
Terminal.app's preferences dialog. Even Apple themselves use the widget type
less and less (cf. the screenshot of the Xcode preferences, v6.2, not even the
latest).

Not only is this style choice inappropriate when the goal is to follow Apple's
HIG and blend in as well as possible, it's also inefficient as the tabs will
quickly start truncating their text (= the filename) when the bar runs out of
horizontal space. And for some reason the scroll widget which usually appears
when the tab bar becomes too wide doesn't appear, presumably because the bar
width never exceeds the available space.

Reproducible: Always


Actual Results:  
See screenshots

Expected Results:  
As Kate5 does; see the screenshot containing Kate's tab bar.

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

[krita] [Bug 356997] Krita crashes when I try to draw on the preview field for "Tangent Normal"

[Dmitry Kazakov via KDE Bugzilla]

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

Dmitry Kazakov  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/krit
   ||a/18343baa19e296fb8c80464bb
   ||c8d1fccd231ef69
 Status|CONFIRMED   |RESOLVED

--- Comment #6 from Dmitry Kazakov  ---
Git commit 18343baa19e296fb8c80464bbc8d1fccd231ef69 by Dmitry Kazakov.
Committed on 24/05/2016 at 16:08.
Pushed by dkazakov into branch 'master'.

Fix default preset for TangentNormal brush

The preset has wrong paintop id: 'tangennormal' instead of 'tangentnormal'

Fixes T2539

M  +---plugins/paintops/defaultpresets/tangentnormal.kpp

http://commits.kde.org/krita/18343baa19e296fb8c80464bbc8d1fccd231ef69

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

[krita] [Bug 362487] [Huion 610] Cursor is misaligned with brush/tools

[via KDE Bugzilla]

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

--- Comment #14 from zeuse...@gmail.com ---
If you want to try the v7.0 driver :
https://www.dropbox.com/s/2swb9h4l8s7tk55/h610-pro-win.rar?dl=1
Btw I noticed another bug with the v12.2.14 driver this time, the pen buttons
(right & middle click) aren't recognized by krita.

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

[dolphin] [Bug 363472] New: Crash...

[Danail via KDE Bugzilla]

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

Bug ID: 363472
   Summary: Crash...
   Product: dolphin
   Version: 15.12.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: dido.ka...@gmail.com

Application: dolphin (15.12.3)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-22-generic x86_64
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
- What I was doing when the application crashed: I wanted to see information
about a file in the context menu. The crash happened when the cursor passed
over Activities.

The crash can be reproduced every time.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7f1495dae900 (LWP 6790))]

Thread 4 (Thread 0x7f1492f0b700 (LWP 6791)):
#0  0x7f14a97b9e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f149de99c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f149de9b8d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f149588f629 in QXcbEventReader::run (this=0x25e74e0) at
qxcbconnection.cpp:1253
#4  0x7f14a438b84e in QThreadPrivate::start (arg=0x25e74e0) at
thread/qthread_unix.cpp:331
#5  0x7f149f654754 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#6  0x7f14a0b396fa in start_thread (arg=0x7f1492f0b700) at
pthread_create.c:333
#7  0x7f14a97c5b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f1489c01700 (LWP 6793)):
#0  0x7f149ffae41d in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f14a45c2a9b in QEventDispatcherGlib::processEvents
(this=0x7f14840008f0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#2  0x7f14a4569dea in QEventLoop::exec (this=this@entry=0x7f1489c00c00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#3  0x7f14a43868a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#4  0x7f14a438b84e in QThreadPrivate::start (arg=0x2a6c360) at
thread/qthread_unix.cpp:331
#5  0x7f149f654754 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#6  0x7f14a0b396fa in start_thread (arg=0x7f1489c01700) at
pthread_create.c:333
#7  0x7f14a97c5b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f1483fff700 (LWP 6812)):
[KCrash Handler]
#6  QVector::isEmpty (this=) at
../../include/QtCore/../../src/corelib/tools/qvector.h:84
#7  QThreadStorageData::finish (p=p@entry=0xf8) at
thread/qthreadstorage.cpp:169
#8  0x7f14a438a9f5 in QThreadPrivate::finish (arg=arg@entry=0x2d8bbd0) at
thread/qthread_unix.cpp:351
#9  0x7f14a438b86f in __pthread_cleanup_class::~__pthread_cleanup_class
(this=, __in_chrg=) at
/usr/include/pthread.h:561
#10 QThreadPrivate::start (arg=0x2d8bbd0) at thread/qthread_unix.cpp:290
#11 0x7f149f654754 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#12 0x7f14a0b396fa in start_thread (arg=0x7f1483fff700) at
pthread_create.c:333
#13 0x7f14a97c5b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f1495dae900 (LWP 6790)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f149de99eb9 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f149de9b617 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f149de9b721 in xcb_wait_for_reply () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#4  0x7f14958b1266 in QXcbCursor::queryPointer (c=0x25968e0,
rootWin=rootWin@entry=0x0, pos=pos@entry=0x7ffc4c279530,
keybMask=keybMask@entry=0x0) at qxcbcursor.cpp:619
#5  0x7f14958b1318 in QXcbCursor::pos (this=0x25edb50) at
qxcbcursor.cpp:639
#6  0x7f14a4ac8fd8 in QCursor::pos (screen=) at
kernel/qcursor.cpp:182
#7  0x7f14a4ac90b1 in QCursor::pos () at kernel/qcursor.cpp:206
#8  0x7f14a51ed971 in QMenu::popup (this=0x2da7c50, p=...,
atAction=atAction@entry=0x0) at widgets/qmenu.cpp:2103
#9  0x7f14a51ef9b1 in QMenu::internalDelayedPopup (this=0x2e4ca90) at
widgets/qmenu.cpp:3257
#10 0x7f14a459be53 in QObject::event (this=this@entry=0x2e4ca90,
e=e@entry=0x7ffc4c279ac0) at kernel/qobject.cpp:1261
#11 0x7f14a50b1cdb in QWidget::event (this=this@entry=0x2e4ca90,
event=event@entry=0x7ffc4c279ac0) at kernel/qwidget.cpp:9105
#12 0x7f14a51f4a83 in QMenu::event (this=0x2e4ca90, e=0x7ffc4c279ac0) at
widgets/qmenu.cpp:2654
#13 0x7f14a506f05c in QApplicationPrivate::notify_helper
(this=this@entry=0x25bbfa0, receiver=receiver@entry=0x2e4ca90,
e=e@entry=0x7ffc4c279ac0) at kernel/qapplication.cpp:3716
#14 0x7f14a5074516 in 

[KScreen] [Bug 361953] When monitors are not vertically aligned, some windows are wrongly vertically placed

[Simon Andric via KDE Bugzilla]

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[Discover] [Bug 347496] Tray icon doesn't unhide when there are new updates available

[Aleix Pol via KDE Bugzilla]

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

Aleix Pol  changed:

   What|Removed |Added

 CC||elvis.angelac...@kdemail.ne
   ||t

--- Comment #9 from Aleix Pol  ---
*** Bug 363442 has been marked as a duplicate of this bug. ***

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

[Discover] [Bug 363442] Discover doesn't show Plasma notifications when new updates are available

[Aleix Pol via KDE Bugzilla]

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

Aleix Pol  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Aleix Pol  ---
I'm not really sure what's the reason, will need to investigate..

*** This bug has been marked as a duplicate of bug 347496 ***

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

[Discover] [Bug 363434] stuck on appstreamurl resolve

[Aleix Pol via KDE Bugzilla]

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

Aleix Pol  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/disc
   ||over/0cae97133cdc7eb666cb05
   ||9e69eba12adc8176f6
 Resolution|--- |FIXED

--- Comment #1 from Aleix Pol  ---
Git commit 0cae97133cdc7eb666cb059e69eba12adc8176f6 by Aleix Pol.
Committed on 24/05/2016 at 15:38.
Pushed by apol into branch 'master'.

Show a message if the opened resource wasn't found and get to the initial view

M  +7-0discover/DiscoverMainWindow.cpp
M  +1-2discover/DiscoverMainWindow.h
M  +1-0discover/autotests/CMakeLists.txt
A  +10   -0discover/autotests/missingResource.qml [License: UNKNOWN]  *
M  +15   -0discover/qml/Main.qml

The files marked with a * at the end have a non valid license. Please read:
http://techbase.kde.org/Policies/Licensing_Policy and use the headers which are
listed at that page.


http://commits.kde.org/discover/0cae97133cdc7eb666cb059e69eba12adc8176f6

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

[kcalc] [Bug 339670] KCalc's GUI layout glitch

[RJVB via KDE Bugzilla]

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

RJVB  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #36 from RJVB  ---
https://git.reviewboard.kde.org/r/128004/

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

[krita] [Bug 363443] [UGEE] Pen pressure not recognised

[via KDE Bugzilla]

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

--- Comment #2 from j...@oss-ltd.com ---
In the initial bug report above, it can be seen that Krita is identifying the
valuators for the device as Rel instead of Abs.
It was suggested that I should change the mode of the display tablet to
Absolute instead of Relative.  In the process of trying to identify how this
should be done, I have found more information that may help.

As can be seen in the additional comment above, xinput shows the device to be
recognised at IDs of 11 and 12.  I am not sure why the device is listed with
two separate IDs, however...

Running:

xinput list --long 11
UC-Logic 19" Tablet Monito  id=11   [slave  pointer  (2)]
Reporting 4 classes:
Class originated from: 11. Type: XIButtonClass
Buttons supported: 6
Button labels: None None None None None None
Button state:
Class originated from: 11. Type: XIValuatorClass
Detail for Valuator 0:
  Label: None
  Range: -2274.00 - 2047.00
  Resolution: 1000 units/m
  Mode: absolute
  Current value: 826.00
Class originated from: 11. Type: XIValuatorClass
Detail for Valuator 1:
  Label: None
  Range: 0.00 - 2047.00
  Resolution: 1000 units/m
  Mode: absolute
  Current value: 1135.00
Class originated from: 11. Type: XIValuatorClass
Detail for Valuator 2:
  Label: None
  Range: 0.00 - 1023.00
  Resolution: 1000 units/m
  Mode: absolute
  Current value: 0.00

xinput list --long 12

UC-Logic 19" Tablet Monito  id=12   [slave  pointer  (2)]
Reporting 7 classes:
Class originated from: 12. Type: XIButtonClass
Buttons supported: 13
Button labels: "Button Left" "Button Middle" "Button Right"
"Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz
Wheel Right" "Button Side" "Button Extra" "Button Unknown" "Button Unknown"
"Button Unknown" "Button Unknown"
Button state:
Class originated from: 12. Type: XIValuatorClass
Detail for Valuator 0:
  Label: Rel X
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
Class originated from: 12. Type: XIValuatorClass
Detail for Valuator 1:
  Label: Rel Y
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
Class originated from: 12. Type: XIValuatorClass
Detail for Valuator 2:
  Label: Rel Horiz Wheel
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
Class originated from: 12. Type: XIValuatorClass
Detail for Valuator 3:
  Label: Rel Vert Wheel
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
Class originated from: 12. Type: XIScrollClass
Scroll info for Valuator 2
  type: 2 (horizontal)
  increment: 1.00
  flags: 0x0
Class originated from: 12. Type: XIScrollClass
Scroll info for Valuator 3
  type: 1 (vertical)
  increment: -1.00
  flags: 0x2 ( preferred )

So, the device at ID 11 is absolute, but the device at ID 12 is relative.

Additionally, I checked in the Xorg.0.log file and found that the
absolute/relative detection was also showing in there, but there is a bug that
is being triggered too.

>From the relevant section of the log file below, it looks like the device is
detected OK to start with, but when adding it as an extended input device, a
bug is triggered (see 26.308).  Is this bug caused by the inclusion of the
inverted commas in the tablet name (...19"...)?  Is this error causing the
problem with the tablet recognition?

[26.296] (II) config/udev: Adding input device UC-Logic 19" Tablet Monito
(/dev/input/event6)
[26.296] (**) UC-Logic 19" Tablet Monito: Applying InputClass "evdev tablet
catchall"
[26.296] (**) UC-Logic 19" Tablet Monito: Applying InputClass "Tablet on
WizardPen"
[26.296] (II) LoadModule: "wizardpen"
[26.296] (II) Loading /usr/lib/xorg/modules/input/wizardpen_drv.so
[26.296] (II) Module wizardpen: vendor="X.Org Foundation"
[26.296]compiled for 1.15.1, module version = 0.8.1
[26.296]Module class: X.Org XInput Driver

[kcalcore] [Bug 362724] enable calendar

[Benni Hill via KDE Bugzilla]

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

Benni Hill  changed:

   What|Removed |Added

 CC||kor...@koranzen.net

--- Comment #2 from Benni Hill  ---
*** Bug 356193 has been marked as a duplicate of this bug. ***

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

[korganizer] [Bug 356193] Korganizer crashes while toggling calendars

[Benni Hill via KDE Bugzilla]

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

Benni Hill  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||be...@mytum.de
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Benni Hill  ---


*** This bug has been marked as a duplicate of bug 362724 ***

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

[kcalcore] [Bug 362724] enable calendar

[Benni Hill via KDE Bugzilla]

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

Benni Hill  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 CC||be...@mytum.de
 Ever confirmed|0   |1
Product|kontact |kcalcore
  Component|general |general

--- Comment #1 from Benni Hill  ---
I can confirm this with KOrganizer 5.1.3 and libkf5calendarcore5
(4:15.12.3-0ubuntu1) from Kubuntu 16.04.
I get the crash every time when I re-enable a certain (remote) calendar. It
doesn't happen with two other calendars (remote and local).
Here is a more detailed backtrace:

Thread 1 (Thread 0x7f359341e940 (LWP 15470)):
[KCrash Handler]
#6  QVector::reserve (this=, asize=asize@entry=0) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h:366
#7  0x7f35b5dbf894 in KCalCore::Calendar::setupRelations (this=0xa314b0,
forincidence=...) at
/build/kcalcore-UNmYX_/kcalcore-15.12.3/src/calendar.cpp:1032
#8  0x7f35b5dfdbac in KCalCore::MemoryCalendar::addIncidence
(this=0xa314b0, incidence=...) at
/build/kcalcore-UNmYX_/kcalcore-15.12.3/src/memorycalendar.cpp:305
#9  0x7f35b148ae9e in Akonadi::CalendarBasePrivate::internalInsert
(this=this@entry=0xa23de0, item=...) at
/build/akonadi-calendar-xcFDuH/akonadi-calendar-15.12.3/src/calendarbase.cpp:158
#10 0x7f35b14986f8 in Akonadi::ETMCalendarPrivate::itemsAdded
(this=this@entry=0xa23de0, items=...) at
/build/akonadi-calendar-xcFDuH/akonadi-calendar-15.12.3/src/etmcalendar.cpp:295
#11 0x7f35b1499a22 in
Akonadi::ETMCalendarPrivate::onRowsInsertedInFilteredModel (this=0xa23de0,
index=..., start=, end=) at
/build/akonadi-calendar-xcFDuH/akonadi-calendar-15.12.3/src/etmcalendar.cpp:450
#12 0x7f35b39e8e4f in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7f35b3a65324 in QAbstractItemModel::rowsInserted(QModelIndex const&,
int, int, QAbstractItemModel::QPrivateSignal) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7f35b3962776 in QAbstractItemModel::endInsertRows() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7f35b39856eb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7f35b3987f44 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7f35b398b929 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
[...]

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

[krita] [Bug 363225] Sometimes the pen inputs events are locked in "clicking" state on the Krita interface, and the interface become unusable

[Camille Bissuel via KDE Bugzilla]

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

--- Comment #8 from Camille Bissuel  ---
A variant without touch events :
1/ pan on the canvas with the middle mouse button
2/ while panning with the mouse, let the pen enter tablet detection over the
interface
3/ pen cursor is locked in an "always panning" state until I trigger a right
click or middle click  with the pen

So… my guess is that an extremely unusual behaviour with mouse and pen (pan
with mouse + the pen enter detection on the interface), is now common with
touch events now Krita use them on the canvas : for example it's easy to
accidentally trigger a touch event with left hand while removing the pen from
detection to grab the mouse, do some click, and come back to the tablet over
the interface (because it's on borders) so pen enter detection while the canvas
is slightly panning or zooming with left hand.

Is it possible to stop any "hold" event (pan, zoom, drag) when the pen enter
detection ?

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

[kmail2] [Bug 362803] Can't change KMail Message List font size with custom font settings.

[Jordan Pilat via KDE Bugzilla]

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

Jordan Pilat  changed:

   What|Removed |Added

 CC||jrpilat+kdeb...@gmail.com

--- Comment #4 from Jordan Pilat  ---
This happens for me as well, running KMail 5.1.3

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