[plasmashell] [Bug 358761] New: Not sure if Plasma or Kwin_x11

2016-01-30 Thread pmanousis via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358761

Bug ID: 358761
   Summary: Not sure if Plasma or Kwin_x11
   Product: plasmashell
   Version: 5.5.4
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: pmanou...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.4)

Qt Version: 5.5.1
Operating System: Linux 4.1.15-8-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Whenever I try to use a launcher icon to start an application, I see the title
bars vanish! I more or less start kwin_x11 again, either using Alt + F2 or in
the most case using a Konsole terminal. If I close the Konsole terminal window
with exit, although the kwin_x11 was put in the background (using '&'),
whenever I try to start an application, I get the same error. If I have the
Konsole running, all are fine!

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe134cee7c0 (LWP 25545))]

Thread 11 (Thread 0x7fe11fc37700 (LWP 25547)):
#0  0x7fe12e208c1d in poll () at /lib64/libc.so.6
#1  0x7fe13314f422 in  () at /usr/lib64/libxcb.so.1
#2  0x7fe13315100f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7fe1223ba3c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fe12e90032f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fe12da120a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7fe12e21104d in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7fe11dc05700 (LWP 25551)):
#0  0x7fe12e208c1d in poll () at /lib64/libc.so.6
#1  0x7fe12a8e9e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fe12a8e9f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fe12eb32d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fe12ead9d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fe12e8fb61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fe131c0ddf8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fe12e90032f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fe12da120a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fe12e21104d in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7fe10a99f700 (LWP 25591)):
#0  0x7fe12e1e2ded in nanosleep () at /lib64/libc.so.6
#1  0x7fe12e20a9d4 in usleep () at /lib64/libc.so.6
#2  0x7fe10f62a9d0 in  () at /usr/lib64/dri/fglrx_dri.so
#3  0x7fe10ecf9512 in  () at /usr/lib64/dri/fglrx_dri.so
#4  0x7fe10ecf9565 in  () at /usr/lib64/dri/fglrx_dri.so
#5  0x7fe12da120a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7fe12e21104d in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7fe1090bc700 (LWP 25629)):
#0  0x7fe12e204ced in read () at /lib64/libc.so.6
#1  0x7fe12a92ab60 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fe12a8e in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fe12a8e9df8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7fe12a8e9f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7fe12eb32d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7fe12ead9d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7fe12e8fb61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7fe131c0ddf8 in  () at /usr/lib64/libQt5Qml.so.5
#9  0x7fe12e90032f in  () at /usr/lib64/libQt5Core.so.5
#10 0x7fe12da120a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7fe12e21104d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7fe103658700 (LWP 25631)):
#0  0x7fe12a92bd10 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fe12a8e94a0 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fe12a8e9d80 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fe12a8e9f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fe12eb32d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fe12ead9d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fe12e8fb61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fe131c0ddf8 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7fe12e90032f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fe12da120a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7fe12e21104d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7fe101dd6700 (LWP 25656)):
#0  0x7fe12da1605f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  

[akregator] [Bug 356230] Ugly icon in System Tray

2016-01-30 Thread Ondřej Kučera via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356230

--- Comment #2 from Ondřej Kučera  ---
Still present in 5.1.1.

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

[systemsettings] [Bug 356219] Keyboard layout switched randomly when switching between applications

2016-01-30 Thread Ondřej Kučera via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356219

Ondřej Kučera  changed:

   What|Removed |Added

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

--- Comment #1 from Ondřej Kučera  ---
I haven't noticed this behavior for at least a few days (maybe even weeks), so
it seems fixed in 5.5.4. I've always suspected that it might have been somehow
connected to https://bugs.kde.org/show_bug.cgi?id=356220 which is also already
fixed (but maybe it's a coincidence).

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

[kdevelop] [Bug 358506] Fix-it hint for missing include should suggest QCamelCase include

2016-01-30 Thread Milian Wolff via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358506

Milian Wolff  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kdev
   ||elop/6ca8995de6fcf6874c63dc
   ||5c6c9ef98d71c41cc4

--- Comment #5 from Milian Wolff  ---
Git commit 6ca8995de6fcf6874c63dc5c6c9ef98d71c41cc4 by Milian Wolff.
Committed on 30/01/2016 at 17:40.
Pushed by mwolff into branch '5.0'.

Ignore case when searching for missing include files.

This way we can also offer the Qt camelcase includes.

M  +5-9languages/clang/duchain/unknowndeclarationproblem.cpp

http://commits.kde.org/kdevelop/6ca8995de6fcf6874c63dc5c6c9ef98d71c41cc4

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


[kdepimlibs] [Bug 353326] Korganizer crashed when trying to add a new event.

2016-01-30 Thread eric via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=353326

--- Comment #5 from eric  ---
Does kaddressbook still crash when the vCard (a few postings above this one) is
imported _after_ first removing the "BDAY" line in the vCard-file (and maybe
also other lines with a date)?

There are similar reports about synchronizing/importing contacts from different
sources or adding a new contact manually that results in a crash. See for
example my bug report: https://bugs.kde.org/show_bug.cgi?id=358696

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


[krita] [Bug 357880] Update G'Mic Filter to latest from Github (right mouse button no longer needed in interactive mode)

2016-01-30 Thread Boudewijn Rempt via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357880

--- Comment #15 from Boudewijn Rempt  ---
Everything built... But mscv2015 still doesn't build a working gmic, so I still
need Tobias' hack-around.

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


[krita] [Bug 358769] HCG color model support

2016-01-30 Thread acterhd via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358769

acterhd  changed:

   What|Removed |Added

  Attachment #96924|0   |1
is obsolete||

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


[krita] [Bug 358769] HCG color model support

2016-01-30 Thread acterhd via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358769

--- Comment #5 from acterhd  ---
Also, I fixed bug with HSV2 day ago.

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


[plasmashell] [Bug 358790] New: Plasma 5 crashed when closing konqueror window

2016-01-30 Thread Cezar Tigaret via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358790

Bug ID: 358790
   Summary: Plasma 5 crashed when closing konqueror window
   Product: plasmashell
   Version: 5.4.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: cezar.tiga...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.15-8-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Simply closed a konqueror window; I use four virtual desktops and a dual screen
display; all konqueror windows were on the same virtual desktop, but the window
I closed before the crash happened was on a different screen. 

Before closing it, have tried to use mouse gestures to attach the window as a
tab to another konqueror window, having forgotten that this doesn't seem to
work when using the breeze window decoration. Not sure this is relevant to the
crash, though...

All konqueror windows are used as web browser.

Using openSUSE Leap 42.1

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa350e8e800 (LWP 10846))]

Thread 17 (Thread 0x7fa332fc5700 (LWP 10864)):
#0  0x7fa346af221e in  () at /usr/lib64/libglib-2.0.so.0
#1  0x7fa346af444b in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fa346af4d80 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fa346af4f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fa34ad3cd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fa34ace3d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fa34ab0561a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fa34ddf0df8 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7fa34ab0a32f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fa345f3c754 in  () at /usr/X11R6/lib64/libGL.so.1
#10 0x7fa349c1c0a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7fa34a41b04d in clone () at /lib64/libc.so.6

Thread 16 (Thread 0x7fa325b4e700 (LWP 10865)):
#0  0x7fa34a40eced in read () at /lib64/libc.so.6
#1  0x7fa345f3b73c in  () at /usr/X11R6/lib64/libGL.so.1
#2  0x7fa3425dfbf7 in  () at /usr/lib64/tls/libnvidia-tls.so.304.131
#3  0x7fa346b35b60 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7fa346af4999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#5  0x7fa346af4df8 in  () at /usr/lib64/libglib-2.0.so.0
#6  0x7fa346af4f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#7  0x7fa34ad3cd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#8  0x7fa34ace3d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#9  0x7fa34ab0561a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#10 0x7fa34ddf0df8 in  () at /usr/lib64/libQt5Qml.so.5
#11 0x7fa34ab0a32f in  () at /usr/lib64/libQt5Core.so.5
#12 0x7fa345f3c754 in  () at /usr/X11R6/lib64/libGL.so.1
#13 0x7fa349c1c0a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7fa34a41b04d in clone () at /lib64/libc.so.6

Thread 15 (Thread 0x7fa31700 (LWP 10868)):
#0  0x7fa34a40eced in read () at /lib64/libc.so.6
#1  0x7fa345f3b73c in  () at /usr/X11R6/lib64/libGL.so.1
#2  0x7fa3425dfbf7 in  () at /usr/lib64/tls/libnvidia-tls.so.304.131
#3  0x7fa346b35b60 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7fa346af4999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#5  0x7fa346af4df8 in  () at /usr/lib64/libglib-2.0.so.0
#6  0x7fa346af4f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#7  0x7fa34ad3cd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#8  0x7fa34ace3d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#9  0x7fa34ab0561a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#10 0x7fa34ddf0df8 in  () at /usr/lib64/libQt5Qml.so.5
#11 0x7fa34ab0a32f in  () at /usr/lib64/libQt5Core.so.5
#12 0x7fa345f3c754 in  () at /usr/X11R6/lib64/libGL.so.1
#13 0x7fa349c1c0a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7fa34a41b04d in clone () at /lib64/libc.so.6

Thread 14 (Thread 0x7fa31df77700 (LWP 10869)):
#0  0x7fa349c2005f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fa3505a586b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7fa3505a5899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7fa345f3c754 in  () at /usr/X11R6/lib64/libGL.so.1
#4  0x7fa349c1c0a4 in start_thread () at /lib64/libpthread.so.0
#5  

[krita] [Bug 358691] Vector Selection crash

2016-01-30 Thread cheteron via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358691

--- Comment #3 from cheteron  ---
No, i can't repeat this with new doc

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


[telepathy] [Bug 356220] Keyboard layout not being switched using a keyboard shortcut

2016-01-30 Thread Ondřej Kučera via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356220

Ondřej Kučera  changed:

   What|Removed |Added

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

--- Comment #10 from Ondřej Kučera  ---
It works properly now in 15.12.1.

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

[Bluedevil] [Bug 358753] unauthorized device autoconnects

2016-01-30 Thread arne anka via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358753

--- Comment #5 from arne anka  ---
but according to the log snippet, the pairing request is handled through
bluedevil -- wouldn't it be possible to use that as a distinguishing feature?
incoming/pending pairing request of unknown device -> "pairing requested"
denied -> "pairing denied" (if it takes longer to disconnect again/update the
listing)
accepted -> as is

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


[Baloo] [Bug 358794] New: Crash of baloo when deleting file

2016-01-30 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358794

Bug ID: 358794
   Summary: Crash of baloo when deleting file
   Product: Baloo
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: m...@vhanda.in
  Reporter: michael.wag...@gmx.at
CC: pinak.ah...@gmail.com

Application: baloo_file (5.15.0)

Qt Version: 5.4.2
Operating System: Linux 4.2.0-25-generic x86_64
Distribution: Ubuntu 15.10

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

When deleting a file using dolphin, baloo_file was reported as crashed.
Using kubuntu 15.10 with latest updates.

ii  libbaloocore4 4:4.14.3-0ubuntu5
 amd64Core funcationality for Baloo
ii  libbaloofiles44:4.14.3-0ubuntu5
 amd64Files funcationality for Baloo
ii  libbalooxapian4   4:4.14.3-0ubuntu5
 amd64Xapian funcationality for Baloo
ii  libkf5baloowidgets-bin4:15.08.2-0ubuntu1   
 amd64Wigets for use with Baloo - binaries
ii  libkf5baloowidgets5:amd64 4:15.08.2-0ubuntu1   
 amd64Wigets for use with Baloo

The crash can be reproduced sometimes.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation
fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  __memcpy_sse2_unaligned () at
../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:36
#7  0x7f39fd184f90 in QByteArray::QByteArray(char const*, int) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f39fd8366ce in Baloo::PostingDB::get(QByteArray const&) () from
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#9  0x7f39fd846c19 in Baloo::WriteTransaction::commit() () from
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#10 0x7f39fd83ebc2 in Baloo::Transaction::commit() () from
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#11 0x00428555 in Baloo::MetadataMover::removeFileMetadata(QString
const&) ()
#12 0x7f39fd391617 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00431d65 in Baloo::PendingFileQueue::removeFileIndex(QString
const&) ()
#14 0x00426776 in Baloo::PendingFileQueue::processCache() ()
#15 0x7f39fd391617 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7f39fd39e178 in QTimer::timerEvent(QTimerEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7f39fd392603 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x7f39fd360efc in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x7f39fd3b709d in QTimerInfoList::activateTimers() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7f39fd3b75d9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x7f39f9974ff7 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7f39f9975250 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7f39f99752fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x7f39fd3b827f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x7f39fd35e75a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x7f39fd3662cc in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x00415aec in main ()

Reported using DrKonqi

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


[plasmashell] [Bug 358795] New: KDE freeze up

2016-01-30 Thread Paul Gresham via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358795

Bug ID: 358795
   Summary: KDE freeze up
   Product: plasmashell
   Version: 5.5.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: p6...@yahoo.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.3)

Qt Version: 5.5.1
Operating System: Linux 4.3.3-303.fc23.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:  I was not doing anything this
time.  This crash has happened several times before when I was working with the
kmail and kcontact applications.  But this last time, I was just on the home
screen after booting up.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f489e1c3940 (LWP 2818))]

Thread 8 (Thread 0x7f487e295700 (LWP 2821)):
#0  0x7f4895ba9fdd in poll () at /lib64/libc.so.6
#1  0x7f489c061272 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7f489c062ee7 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7f488021fda9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7f48967b23de in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7f4894eed60a in start_thread () at /lib64/libpthread.so.0
#6  0x7f4895bb5a4d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f48775ef700 (LWP 2822)):
#0  0x7fff93ef7bbf in clock_gettime ()
#1  0x7f4895bc3cc6 in clock_gettime () at /lib64/libc.so.6
#2  0x7f4896862956 in qt_gettime() () at /lib64/libQt5Core.so.5
#3  0x7f48969e7949 in QTimerInfoList::updateCurrentTime() () at
/lib64/libQt5Core.so.5
#4  0x7f48969e7eb5 in QTimerInfoList::timerWait(timespec&) () at
/lib64/libQt5Core.so.5
#5  0x7f48969e92ae in timerSourcePrepare(_GSource*, int*) () at
/lib64/libQt5Core.so.5
#6  0x7f48910cf70d in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#7  0x7f48910d009b in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#8  0x7f48910d027c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#9  0x7f48969e9ecb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#10 0x7f4896990eca in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#11 0x7f48967ad434 in QThread::exec() () at /lib64/libQt5Core.so.5
#12 0x7f489aaf8b45 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#13 0x7f48967b23de in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#14 0x7f4894eed60a in start_thread () at /lib64/libpthread.so.0
#15 0x7f4895bb5a4d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f486ae40700 (LWP 2823)):
#0  0x7fff93ef7bbf in clock_gettime ()
#1  0x7f4895bc3cc6 in clock_gettime () at /lib64/libc.so.6
#2  0x7f4896862956 in qt_gettime() () at /lib64/libQt5Core.so.5
#3  0x7f48969e7949 in QTimerInfoList::updateCurrentTime() () at
/lib64/libQt5Core.so.5
#4  0x7f48969e7eb5 in QTimerInfoList::timerWait(timespec&) () at
/lib64/libQt5Core.so.5
#5  0x7f48969e92ae in timerSourcePrepare(_GSource*, int*) () at
/lib64/libQt5Core.so.5
#6  0x7f48910cf70d in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#7  0x7f48910d009b in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#8  0x7f48910d027c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#9  0x7f48969e9ecb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#10 0x7f4896990eca in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#11 0x7f48967ad434 in QThread::exec() () at /lib64/libQt5Core.so.5
#12 0x7f489aaf8b45 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#13 0x7f48967b23de in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#14 0x7f4894eed60a in start_thread () at /lib64/libpthread.so.0
#15 0x7f4895bb5a4d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f48693e5700 (LWP 2824)):
#0  0x7f4895ba5bcd in read () at /lib64/libc.so.6
#1  0x7f4891113390 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#2  0x7f48910cfc64 in g_main_context_check () at /lib64/libglib-2.0.so.0
#3  0x7f48910d0110 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#4  0x7f48910d027c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#5  0x7f48969e9ecb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#6  0x7f4896990eca in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#7  0x7f48967ad434 in QThread::exec() () at /lib64/libQt5Core.so.5
#8  0x7f489aaf8b45 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#9  0x7f48967b23de in QThreadPrivate::start(void*) () 

[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3

2016-01-30 Thread Valdas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=353203

--- Comment #47 from Valdas  ---
If I comment in "startkde" like this:

# At this point all environment variables are set, let's send it to the DBus
session server to update the activation environment
#if which dbus-update-activation-environment >/dev/null 2>/dev/null ; then
#dbus-update-activation-environment --systemd --all
#else
/usr/lib/x86_64-linux-gnu/libexec/ksyncdbusenv
#fi


then issue remains.

I must mention: during that pause I can "Alt+F2" then type "firefox" with
following Enter and then with "Alt+Tab" I can see started Firefox window in
Application switcher visualization.

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


[frameworks-kactivities] [Bug 358516] KActivities: Database can not be opened in WAL mode. Check the SQLite version (required >3.7.0).

2016-01-30 Thread vst via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358516

--- Comment #8 from vst  ---
Checked, the same. I created your suggested directory on /boot which is plain
ext4 on disk.
I rebooted the pc, did the symlink from a vt, then launched kde. So it was as
clean as it could be.

[vst@host ~]$ ls -l .local/share/kactivitymanagerd
lrwxrwxrwx 1 root root 16 Jan 30 .local/share/kactivitymanagerd ->
/boot/kamd_share
[vst@host ~]$ ls -ld /boot/kamd_share/
drwxr-xr-x 3 vst users 4096 Jan 30 /boot/kamd_share/
[vst@host ~]$ tree /boot/kamd_share/
/boot/kamd_share/
└── resources
└── database

1 directory, 1 file
[vst@host ~]$ sqlite3 /boot/kamd_share/resources/database
SQLite version 3.10.2 2016-01-20 15:27:19
Enter ".help" for usage hints.
sqlite> .tables
Error: database disk image is malformed
sqlite>

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

[konsole] [Bug 345403] "Terminal Size" setting in profile ignored

2016-01-30 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=345403

--- Comment #30 from jeremy9...@gmail.com ---
Thank you very very much Roman Gilg (subdiff) !

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


[plasmashell] [Bug 358789] New: Plasmashell hangs and uses up CPU when I try to launch any application

2016-01-30 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358789

Bug ID: 358789
   Summary: Plasmashell hangs and uses up CPU when I try to launch
any application
   Product: plasmashell
   Version: 5.4.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: wodenc...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

I've had this problem for awhile now that has made the Plasma environment
unusable for me.

Whenever I log into Plasma and try to launch an application from the start
menu, Plasma (and the whole desktop, except for the mouse) completely hang, and
never un-hang.

>From the tty, looking at process monitor shows plasmashell using up 100% CPU of
a thread.

Here is the stack trace from the process, as retrieved by dgb (looks like I am
missing some debug symbols but not sure which package I need to install):
:~$ cat gdb_plasmashell.txt 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7ff7110c84d4 in ?? () from /usr/lib/x86_64-linux-gnu/libGL.so.1
#0  0x7ff7110c84d4 in ?? () from /usr/lib/x86_64-linux-gnu/libGL.so.1
#1  0x7ff70d0e1be8 in ?? () from
/usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.358.16
#2  0x7ff70d0a36a3 in ?? () from
/usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.358.16
#3  0x7ff70d0c3d78 in ?? () from
/usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.358.16
#4  0x7ff70d0c41e0 in ?? () from
/usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.358.16
#5  0x7ff7110b8403 in ?? () from /usr/lib/x86_64-linux-gnu/libGL.so.1
#6  0x7ff707c96122 in QGLXContext::swapBuffers (this=0x346f980,
surface=0x2770ba0) at qglxintegration.cpp:529
#7  0x7ff715af5e26 in QOpenGLContext::swapBuffers (this=0x347f410,
surface=) at kernel/qopenglcontext.cpp:992
#8  0x7ff7187cdec9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#9  0x7ff7187d329c in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#10 0x7ff7155c02be in QThreadPrivate::start (arg=0x3471a00) at
thread/qthread_unix.cpp:337
#11 0x7ff7146af6aa in start_thread (arg=0x7ff62f0e1700) at
pthread_create.c:333
#12 0x7ff714ed8eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Here's some background info:
Ubuntu Unity environment works ok, using sddm (Plasma fails using sddm)
Using latest NVidia 358.16 Unix driver from the official NVidia site.

:~$ uname -r
4.4.0-040400-generic

:~$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=15.10
DISTRIB_CODENAME=wily
DISTRIB_DESCRIPTION="Ubuntu 15.10"

I've tried deleting the .kde, .cache and .config folders as well and that also
did not fix the problem.

Is there any other info you need from me, or do you guys have any idea why I am
experiencing this problem?

Reproducible: Always

Steps to Reproduce:
1. Log in to Plasma
2. Start an Application from the Start Menu (any application)
3. I am hung

Actual Results:  
plasmashell consuming lots of CPU, everything on the desktop except for the
mouse cursor is frozen. Does not unfreeze.

Expected Results:  
Started the application.

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


[Bluedevil] [Bug 358753] unauthorized device autoconnects

2016-01-30 Thread David Rosca via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358753

--- Comment #4 from David Rosca  ---
(In reply to arne anka from comment #3)
> but maybe to show a dedicated name for that pairing phase, different from
> "connected" would be helpful?

But there is no way to distinguish it, BlueZ just reports connected.

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


[kmail2] [Bug 358792] Search string is untranslatable

2016-01-30 Thread André Marcelo Alvarenga via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358792

--- Comment #1 from André Marcelo Alvarenga  ---
Created attachment 96932
  --> https://bugs.kde.org/attachment.cgi?id=96932=edit
Screenshot

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

[kmail2] [Bug 358792] New: Search string is untranslatable

2016-01-30 Thread André Marcelo Alvarenga via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358792

Bug ID: 358792
   Summary: Search string is untranslatable
   Product: kmail2
   Version: 5.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: folders
  Assignee: kdepim-b...@kde.org
  Reporter: alvare...@kde.org

See screenshot.

This "folder" is created when I run Find Messages... action to search in
messages.

Reproducible: Always

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


[Bluedevil] [Bug 358753] unauthorized device autoconnects

2016-01-30 Thread David Rosca via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358753

--- Comment #6 from David Rosca  ---
Sorry but no, it would be only guessing.

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


[kdev-python] [Bug 358563] Possible infinite loop in UnsureType::toString()

2016-01-30 Thread Sven Brauch via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358563

Sven Brauch  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |WAITINGFORINFO

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


[kmail2] [Bug 358785] When forwarding a email as message/rfc822 attachment in a signed unencrypted email, header filtering leads to invalid signatures

2016-01-30 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358785

--- Comment #1 from tremp...@dasganma.tk ---
A third possible workaround: don't sign the forwarded message, or include it in
a separate multipart/signed part so that at least it is obvious that the
forwarded message has been modified but the text written by me is intact.

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


[digikam] [Bug 358193] Color labels exported from LightRoom not recognized by digiKam

2016-01-30 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358193

--- Comment #9 from caulier.gil...@gmail.com ---
Screenshot of import done :

https://www.flickr.com/photos/digikam/24711388405/in/dateposted-public/

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


[neon] [Bug 358786] New: [Ark] Drop KHTML build dependency

2016-01-30 Thread Elvis Angelaccio via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358786

Bug ID: 358786
   Summary: [Ark] Drop KHTML build dependency
   Product: neon
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: unstable packaging
  Assignee: n...@kde.org
  Reporter: elvis.angelac...@kdemail.net

So... let's inaugurate this project Neon :)

I see that the Ark 15.12 (unstable?) package still has a build dependency on
libkf5khtml-dev.
However, KHTML was dropped upstream as of this commit [1], before the 15.12
release.

[1]:
https://quickgit.kde.org/?p=ark.git=commit=f2090934229ec25c16bdf84e808dfe7cee8a1cd1

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


[plasmashell] [Bug 358788] New: Plasma crashed

2016-01-30 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358788

Bug ID: 358788
   Summary: Plasma crashed
   Product: plasmashell
   Version: 5.4.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: pedron.alexan...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.2)

Qt Version: 5.4.2
Operating System: Linux 4.2.0-25-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:
- What I was doing when the application crashed: I was looking for new
wallpapers in the desktop manager. Suddendly, it crashed.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f43ea5db800 (LWP 1394))]

Thread 18 (Thread 0x7f43d5c33700 (LWP 1396)):
#0  0x7f43e4d878dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f43e8dcebd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f43e8dd074f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f43d7f7da39 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
#4  0x7f43e547a2be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f43e45696aa in start_thread (arg=0x7f43d5c33700) at
pthread_create.c:333
#6  0x7f43e4d92eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 17 (Thread 0x7f43cebe9700 (LWP 1462)):
#0  0x7f43e4d8349d in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f43e1b774e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f43e1b33cd4 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f43e1b34190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f43e1b342fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f43e56b129b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f43e565775a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f43e54753d4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f43e7c9df85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#9  0x7f43e547a2be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f43e45696aa in start_thread (arg=0x7f43cebe9700) at
pthread_create.c:333
#11 0x7f43e4d92eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 16 (Thread 0x7f43c4939700 (LWP 1468)):
#0  0x7f43e1b33d52 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f43e1b34250 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f43e1b342fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f43e56b129b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f43e565775a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f43e54753d4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f43e7c9df85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f43e547a2be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f43e45696aa in start_thread (arg=0x7f43c4939700) at
pthread_create.c:333
#9  0x7f43e4d92eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 15 (Thread 0x7f43bd831700 (LWP 1471)):
#0  0x7f43e1b33800 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f43e1b3411b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f43e1b342fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f43e56b129b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f43e565775a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f43e54753d4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f43e7c9df85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f43e547a2be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f43e45696aa in start_thread (arg=0x7f43bd831700) at
pthread_create.c:333
#9  0x7f43e4d92eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 14 (Thread 0x7f43b7df7700 (LWP 1475)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f43ea029114 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f43ea029159 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f43e45696aa in 

[krita] [Bug 358734] [Hard] Incorrect 2nd square HSV color picker (checked by HCG color model)

2016-01-30 Thread acterhd via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358734

--- Comment #11 from acterhd  ---
How bug is working? First, need implement HCG sliders to Krita.
After you can test HSV2. If moves in wrong direction - you found bug.

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


[konsole] [Bug 345403] "Terminal Size" setting in profile ignored

2016-01-30 Thread Kurt Hindenburg via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=345403

--- Comment #29 from Kurt Hindenburg  ---
Git commit 55f02e5b8e3e2395050940c33c97306311192e18 by Kurt Hindenburg.
Committed on 30/01/2016 at 17:09.
Pushed by hindenburg into branch 'master'.

Allow profile's termainal size to work again

When Konsole Settings -> 'Use current window size on next startup' is
disabled, use the Profile's terminal size for new windows.

Many thanks to Roman Gilg (subdiff gmail com) for research and patch.

If there are no further issues, I'll commit to 15.12 branch (should go
.2 release).

REVIEW: 126924

M  +24   -7src/Application.cpp
M  +2-1src/Application.h

http://commits.kde.org/konsole/55f02e5b8e3e2395050940c33c97306311192e18

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


[kdenlive] [Bug 352489] 15.13 git master: MLT processing threads>1 causes (re)positioning playhead to not work any longer

2016-01-30 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=352489

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

   What|Removed |Added

Summary|Kdenlive 15.08.0|15.13 git master: MLT
   |git20150908.0238|processing threads>1 causes
   |(re)positioning playhead|(re)positioning playhead to
   |does not work   |not work any longer

--- Comment #10 from wegwerf-1-...@gmx.de ---
Issue is still present with recent git master on fast machines, such as core
i7's. Updating the bug tittle to correctly reflect the cause of this issue.

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


[kmail2] [Bug 351494] signed messages with attachements take twice the place

2016-01-30 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=351494

tremp...@dasganma.tk changed:

   What|Removed |Added

 CC||tremp...@dasganma.tk

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


[kdevelop] [Bug 358787] deadlock between background parser and code completion

2016-01-30 Thread Milian Wolff via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358787

Milian Wolff  changed:

   What|Removed |Added

   Target Milestone|--- |5.0.0
 Ever confirmed|0   |1
   Keywords||release_blocker
   Priority|NOR |VHI
 Status|UNCONFIRMED |CONFIRMED

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


[kde] [Bug 358791] New: No way to switch keyboard layouts in KDE 4.10.5 except to use configuration file.

2016-01-30 Thread Alexey Zhuravliov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358791

Bug ID: 358791
   Summary: No way to switch keyboard layouts in KDE 4.10.5 except
to use configuration file.
   Product: kde
   Version: unspecified
  Platform: Slackware Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: alexz...@ukrpack.net

There was a way to place a keyboard layout indicator to the lower right corner
in KDE 3 but not in KDE 4.

I have found a way to do it by adding a configuration file but there seems to
be no way to do it inside KDE. The remedy is: you have to create a file called
*00-keyboard.conf* in the directory */etc/X11/xorg.conf.d* containing:
-- 00-keyboard.conf 
Section "InputClass"
Identifier "system-keyboard"
Option "XkbLayout" "us,ru"
Option "XkbOptions" "grp:ctrl_shift_toggle"
EndSection
- End of 00-keyboard.conf -
The languages here are US-English and Russian and the keys switching the layout
are Control and Shift. After creating the file and launching X Window you will
get a nice indicator in the lower right corner with letters showing witch
keyboard layout is chosen (us or ru) it also lets you choosing layouts with
your mouse.

The information was on the site of Archlinux ,namely at the address
https://wiki.archlinux.org/index.php/Keyboard_configuration_in_Xorg#Using_X_configuration_files
. You can also find several other hints on how to switch keyboard layouts in X
Window there.

It's very annoying not to be able to pick a layout for your native language.
People using just one language just may not understand how frustrating it can
be not to be able to use another keyboard layout.

Reproducible: Always




My system:
Slackware Linux 14.1
KDE 4.10.5
Kernel 3.10.17

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


[Bluedevil] [Bug 358753] unauthorized device autoconnects

2016-01-30 Thread arne anka via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358753

--- Comment #3 from arne anka  ---
i see, thanks for the info.
but maybe to show a dedicated name for that pairing phase, different from
"connected" would be helpful?

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


[kde] [Bug 358791] No way to switch keyboard layouts in KDE 4.10.5 except to use configuration file.

2016-01-30 Thread Alexey Zhuravliov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358791

Alexey Zhuravliov  changed:

   What|Removed |Added

   Keywords||usability

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


[dolphin] [Bug 358793] New: Trying to copying files

2016-01-30 Thread Boki via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358793

Bug ID: 358793
   Summary: Trying to copying files
   Product: dolphin
   Version: 15.12.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: superdodgebal...@live.fr

Application: dolphin (15.12.1)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-1-pae i686
Distribution: "openSUSE Tumbleweed (20160126) (i586)"

-- Information about the crash:
- What I was doing when the application crashed:
i was copying files for sending them to another folder.
I got 2 windows opened. One with the goal one with the download folder. It is
not the first time it happened.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Делфин (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0xb3165800 (LWP 10131))]

Thread 7 (Thread 0xb15c8b40 (LWP 10132)):
#0  0x in __kernel_vsyscall ()
#1  0x in poll () at /lib/libc.so.6
#2  0x in  () at /usr/lib/libxcb.so.1
#3  0x in xcb_wait_for_event () at /usr/lib/libxcb.so.1
#4  0x in  () at /usr/lib/libQt5XcbQpa.so.5
#5  0x in  () at /usr/lib/sse2/libQt5Core.so.5
#6  0x in start_thread () at /lib/libpthread.so.0
#7  0x in clone () at /lib/libc.so.6

Thread 6 (Thread 0xafec4b40 (LWP 10133)):
#0  0x in __kernel_vsyscall ()
#1  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libpthread.so.0
#2  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libc.so.6
#3  0x in  () at /usr/lib/libQt5Script.so.5
#4  0x in  () at /usr/lib/libQt5Script.so.5
#5  0x in start_thread () at /lib/libpthread.so.0
#6  0x in clone () at /lib/libc.so.6

Thread 5 (Thread 0xad08bb40 (LWP 10134)):
#0  0x in __kernel_vsyscall ()
#1  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libpthread.so.0
#2  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libc.so.6
#3  0x in  () at /usr/lib/dri/swrast_dri.so
#4  0x in  () at /usr/lib/dri/swrast_dri.so
#5  0x in start_thread () at /lib/libpthread.so.0
#6  0x in clone () at /lib/libc.so.6

Thread 4 (Thread 0xac88ab40 (LWP 10135)):
#0  0x in __kernel_vsyscall ()
#1  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libpthread.so.0
#2  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libc.so.6
#3  0x in  () at /usr/lib/dri/swrast_dri.so
#4  0x in  () at /usr/lib/dri/swrast_dri.so
#5  0x in start_thread () at /lib/libpthread.so.0
#6  0x in clone () at /lib/libc.so.6

Thread 3 (Thread 0xab7a3b40 (LWP 10136)):
#0  0x in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#2  0x in  () at /usr/lib/libglib-2.0.so.0
#3  0x in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#4  0x in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/sse2/libQt5Core.so.5
#5  0x in
QEventLoop::processEvents(QFlags) () at
/usr/lib/sse2/libQt5Core.so.5
#6  0x in QEventLoop::exec(QFlags) () at
/usr/lib/sse2/libQt5Core.so.5
#7  0x in QThread::exec() () at /usr/lib/sse2/libQt5Core.so.5
#8  0x in QThread::run() () at /usr/lib/sse2/libQt5Core.so.5
#9  0x in  () at /usr/lib/sse2/libQt5Core.so.5
#10 0x in start_thread () at /lib/libpthread.so.0
#11 0x in clone () at /lib/libc.so.6

Thread 2 (Thread 0xaa62ab40 (LWP 11426)):
[KCrash Handler]
#7  0x in QMutex::lock() () at /usr/lib/sse2/libQt5Core.so.5
#8  0x in  () at /usr/lib/sse2/libQt5Core.so.5
#9  0x in  () at /usr/lib/sse2/libQt5Core.so.5
#10 0x in start_thread () at /lib/libpthread.so.0
#11 0x in clone () at /lib/libc.so.6

Thread 1 (Thread 0xb3165800 (LWP 10131)):
#0  0x in __kernel_vsyscall ()
#1  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libpthread.so.0
#2  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libc.so.6
#3  0x in  () at /usr/lib/libxcb.so.1
#4  0x in  () at /usr/lib/libxcb.so.1
#5  0x in xcb_wait_for_reply () at /usr/lib/libxcb.so.1
#6  0x in xcb_query_pointer_reply () at /usr/lib/libxcb.so.1
#7  0x in  () at /usr/lib/libQt5XcbQpa.so.5
#8  0x in  () at /usr/lib/libQt5XcbQpa.so.5
#9  0x in QCursor::pos(QScreen const*) () at
/usr/lib/sse2/libQt5Gui.so.5
#10 0x in QCursor::pos() () at /usr/lib/sse2/libQt5Gui.so.5
#11 0x in QMenu::popup(QPoint const&, QAction*) () at
/usr/lib/libQt5Widgets.so.5
#12 0x in QMenu::internalDelayedPopup() () at
/usr/lib/libQt5Widgets.so.5
#13 0x in QMenu::timerEvent(QTimerEvent*) () at

[konsole] [Bug 351960] Missing Comment in desktop file

2016-01-30 Thread Kurt Hindenburg via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=351960

Kurt Hindenburg  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kons
   ||ole/c595d0cd864d273ce5b3e94
   ||2150a43a808b51870
 Status|UNCONFIRMED |RESOLVED

--- Comment #5 from Kurt Hindenburg  ---
Git commit c595d0cd864d273ce5b3e942150a43a808b51870 by Kurt Hindenburg.
Committed on 30/01/2016 at 19:58.
Pushed by hindenburg into branch 'master'.

Add 'Comment' lines to desktop files

I simpflied the text for most of these from the reviewboard patch

REVIEW:125943

M  +2-0desktop/konsolehere.desktop
M  +2-0desktop/konsolepart.desktop
M  +2-0desktop/konsolerun.desktop
M  +2-0desktop/terminalemulator.desktop

http://commits.kde.org/konsole/c595d0cd864d273ce5b3e942150a43a808b51870

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


[plasmashell] [Bug 358772] New: Sound applet isn't update if pulseaudio restart

2016-01-30 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358772

Bug ID: 358772
   Summary: Sound applet isn't update if pulseaudio restart
   Product: plasmashell
   Version: 5.5.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: picotmath...@gmail.com

When restarting pulseaudio, if I am going to systemsettings/multimedia, the now
PulseAudio Jack Sink is recognized here. But the sound icon in system stray is
still red and If I click on, window is empty. And Volume on Keyboard don't
works.

Reproducible: Always

Steps to Reproduce:
1.Start a session without Pulseaudio
2.Start Jack
3.Start PulseAudio Jack Module

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


[dragonplayer] [Bug 357795] dragon no longer allows files to be given on the command line

2016-01-30 Thread Rex Dieter via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357795

Rex Dieter  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
  Latest Commit||http://commits.kde.org/drag
   ||on/ee333a83457450df771b458c
   ||299dce43a5500a35
 Resolution|--- |FIXED

--- Comment #4 from Rex Dieter  ---
Git commit ee333a83457450df771b458c299dce43a5500a35 by Rex Dieter, on behalf of
Harald Sitter.
Committed on 30/01/2016 at 15:08.
Pushed by rdieter into branch 'Applications/15.12'.

when parsing user input urls, default to assume local files

The invocation

> dragon foo.mkv

should yield file://$PWD/foo.mkv. Processed as a URL foo.mkv can either be
a relative path or a FQDN though. Since we don't support scheme-less url
notiation for this use case and people are far more likely to use the
invocation argument for local files we can safely coerce QUrl to default
to assume file:// rather than http://

> dragon foo.mkv => file://$PWD/foo.mkv
> dragon http://foo.mkv => http://foo.mkv

M  +5-1src/app/main.cpp

http://commits.kde.org/dragon/ee333a83457450df771b458c299dce43a5500a35

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


[okular] [Bug 358634] Hang waiting for print server to get page shape

2016-01-30 Thread Albert Astals Cid via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358634

Albert Astals Cid  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE
 CC||aa...@kde.org

--- Comment #2 from Albert Astals Cid  ---


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

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


[kscreenlocker] [Bug 358101] Keyboard layout button is too small to show the icons/text.

2016-01-30 Thread sederic via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358101

sederic  changed:

   What|Removed |Added

 CC||sebastian.end...@online.de

--- Comment #5 from sederic  ---
I see the same and sometimes the text is outside the button (when switching
from "de(us)" to "de").

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


[kscreenlocker] [Bug 353855] Media controls should be shown on lock screen.

2016-01-30 Thread sederic via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=353855

sederic  changed:

   What|Removed |Added

 CC||sebastian.end...@online.de

--- Comment #1 from sederic  ---
+1

This would be nice...

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


[kdevelop] [Bug 355356] Function "Adapt signature" doesn't work correct (renaming argument) for constructor of class

2016-01-30 Thread Milian Wolff via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=355356

Milian Wolff  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kdev
   ||elop/95e7dd4e07adcd3cd29a2d
   ||998fb4076b80746c11
 Status|CONFIRMED   |RESOLVED

--- Comment #3 from Milian Wolff  ---
Git commit 95e7dd4e07adcd3cd29a2d998fb4076b80746c11 by Milian Wolff.
Committed on 30/01/2016 at 15:51.
Pushed by mwolff into branch '5.0'.

Do not add return type to constructors in signature assistant.

M  +6-4languages/clang/codegen/adaptsignatureaction.cpp
M  +11   -3languages/clang/codegen/adaptsignatureassistant.cpp
M  +8-0languages/clang/tests/test_assistants.cpp

http://commits.kde.org/kdevelop/95e7dd4e07adcd3cd29a2d998fb4076b80746c11

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


[krita] [Bug 358769] HCG color model support

2016-01-30 Thread acterhd via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358769

--- Comment #2 from acterhd  ---
Created attachment 96924
  --> https://bugs.kde.org/attachment.cgi?id=96924=edit
HCG color model support version 2.2

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


[kdevelop] [Bug 355356] Function "Adapt signature" doesn't work correct (renaming argument) for constructor of class

2016-01-30 Thread Milian Wolff via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=355356

--- Comment #4 from Milian Wolff  ---
@ Piotr: Regarding the whitespace changes, when you have setup the source
formatter, it should use the correct style. If that is not the case, please
report a new bug for that.

Thanks

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


[kdev-python] [Bug 358563] Possible infinite loop in UnsureType::toString()

2016-01-30 Thread Sven Brauch via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358563

--- Comment #7 from Sven Brauch  ---
Created attachment 96925
  --> https://bugs.kde.org/attachment.cgi?id=96925=edit
potential fix for this bug

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


[marble] [Bug 358779] dgml is missing an option center the map (lonlat) [patch]

2016-01-30 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358779

--- Comment #1 from boris.sh.1983+kde.bugzi...@gmail.com ---
Created attachment 96928
  --> https://bugs.kde.org/attachment.cgi?id=96928=edit
[PATCH] lonlat from dgml

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


[frameworks-kcoreaddons] [Bug 358594] file changes are not updated in konqueror and dolphin.

2016-01-30 Thread Mehmet Topsakal via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358594

Mehmet Topsakal  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #3 from Mehmet Topsakal  ---
This was not on NSF share. Somehow I cannot reproduce the problem too. Indeed I
carefully checked before reporting this bug. I will check further.

Thanks.

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


[kalarm] [Bug 346060] KAlarm calculates deferred alarm time wrongly

2016-01-30 Thread David Jarvie via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=346060

--- Comment #1 from David Jarvie  ---
I'm sorry this bug has been overlooked. If possible, can you provide more
information on this:

- You say that in KDE you have two time zones. How are these set? (In System
Settings, you can only set one time zone, and that sets it for the system.)

- What time zone is set in KAlarm (in the KAlarm menu, go to Settings ->
Configure KAlarm -> Time & Date).

- What do you mean by pressing OK in the main alarm window? Did you bring up
the alarm edit dialog after deferring the alarm, edit it and click OK?

- Can you please attach a copy of KAlarm's calendar (usually in
~/.kde/share/apps/kalarm/calendar.ics), after deferring the alarm. Please say
what time is then shown for the alarm in KAlarm's main window.

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


[krita] [Bug 357880] Update G'Mic Filter to latest from Github (right mouse button no longer needed in interactive mode)

2016-01-30 Thread Boudewijn Rempt via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357880

--- Comment #14 from Boudewijn Rempt  ---
On Linux, yes -- I'm now doing a Windows build. I did contact Tobias, but he
hasn't shared his mingw dll with me yet -- guess he's just as overloaded as I
am :-)

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


[kalarm] [Bug 344902] kalarm uses gregorian calendar system for day number when adding reoccurring events in jalali calendar system

2016-01-30 Thread David Jarvie via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=344902

David Jarvie  changed:

   What|Removed |Added

   Severity|normal  |wishlist

--- Comment #5 from David Jarvie  ---
I'm changing the category of this bug to a wishlist item, since without either
a change to the iCalendar specification, or changing KAlarm to not use
iCalendar (which would be a very major change), it is not possible to implement
Jalali recurrences.

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


[krita] [Bug 325052] JJ: Isolate layer mode

2016-01-30 Thread Bollebib via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=325052

--- Comment #11 from Bollebib  ---
(In reply to Boudewijn Rempt from comment #10)
> WISHGROUP: Larger Usability Fixes
> 
> This really needs to be discussed with Dmitry again because we cannot figure
> out the actual use-case.

talk to me on IRC if you like

I did explain the usecase  in this comment thread

It's to have a permanent isolate layer going,so you can jump through your
layers while searching for something.

Another usecase is if you have an animation on different layers,you can go up
and down the stack to check if the flow is correct. This is something I have
needed when I worked on skullgirls. They want their animations in a PSD ,so the
only way to do this was put the layers in sequence . 

But to still be able to work on them even after you put them in layerstack
,isolatat layer mode would be useful. Regardles if krita has animation,this is
an actual usecase I have had to use for several months.

Besides that it's just easier to flip through layers and compare without
needing to input shortcuts all the time. 
I'm a heavy isolate layer user,but it's easier to just activate it and flip
through layers ,then deactivate. Then to press the shortcut,siwtch layer,press
shortcut again,switch layer,etc X20

expecially for MANY layers this becomes a huge issue.

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


[ark] [Bug 356968] Ark plugin extracthere makes Dolphin crash after drag and drop

2016-01-30 Thread Elvis Angelaccio via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356968

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||mattcou...@gmail.com

--- Comment #1 from Elvis Angelaccio  ---
*** Bug 358597 has been marked as a duplicate of this bug. ***

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


[ark] [Bug 356968] Ark plugin extracthere makes Dolphin crash after drag and drop

2016-01-30 Thread Elvis Angelaccio via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356968

--- Comment #2 from Elvis Angelaccio  ---
@summerson96: I see you already installed debug symbols for KIO. Could you
please install them also for Ark? (it's the ark-debuginfo package on openSUSE).

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


[kate] [Bug 358526] Freeze and glitches when changing KDE color scheme

2016-01-30 Thread Milian Wolff via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358526

Milian Wolff  changed:

   What|Removed |Added

Version|4.90.91 |Git
  Component|UI: toplevel window |part
   Target Milestone|5.0.0   |---
   Assignee|kdevelop-bugs-n...@kde.org  |kwrite-bugs-n...@kde.org
Product|kdevelop|kate

--- Comment #3 from Milian Wolff  ---
I can reproduce this lag with Kate itself, so reassigning there. I'll also have
a look at that now.

Perf already shows that some excessive repainting is obviously at fault here:

16.54% 0.34%  kate libKF5TextEditor.so.5.19.0 [.]
KateRenderer::paintTextLine

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


[kdevplatform] [Bug 358776] New: per-project tab colors not updated on palette change

2016-01-30 Thread Milian Wolff via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358776

Bug ID: 358776
   Summary: per-project tab colors not updated on palette change
   Product: kdevplatform
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: shell
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: m...@milianw.de

See also https://bugs.kde.org/show_bug.cgi?id=358526

When the global system palette is changed from dark to bright or vice versa,
the text color of the per-project tab is not updated, leading to unreadable
white-on-white or dark-on-dark text of tabs

Reproducible: Always

Steps to Reproduce:
1. open tab with per-project color enabled
2. change system style from breeze to breeze-dark or vice versa

Actual Results:  
tab text is unreadable

Expected Results:  
colors are recalculated on the ApplicationPaletteChange event and text stays
readable.

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


[kate] [Bug 358526] Freeze and glitches when changing KDE color scheme

2016-01-30 Thread Milian Wolff via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358526

Milian Wolff  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/ktex
   ||teditor/8c6a18964e0c0684d5e
   ||c068e686ed41aeb0fd657
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #4 from Milian Wolff  ---
Git commit 8c6a18964e0c0684d5ec068e686ed41aeb0fd657 by Milian Wolff.
Committed on 30/01/2016 at 16:03.
Pushed by mwolff into branch 'master'.

Only update the palette once for the change event belonging to qApp.

This fixes the massive freeze that occurs when the global color
palette is changed. Note that the qApp event filter includes change
events to many objects, but we only want to update once.

M  +2-3src/utils/kateglobal.cpp

http://commits.kde.org/ktexteditor/8c6a18964e0c0684d5ec068e686ed41aeb0fd657

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


[kate] [Bug 358526] Freeze and glitches when changing KDE color scheme

2016-01-30 Thread Milian Wolff via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358526

--- Comment #5 from Milian Wolff  ---
Reported https://bugs.kde.org/show_bug.cgi?id=358776 for the unreadable text
issue.

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


[Powerdevil] [Bug 344456] Plasma 5 desktop does not suspend with only upower, no systemd

2016-01-30 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=344456

--- Comment #36 from andreas.sturmlech...@gmail.com ---
Please check your consolekit setup w/ '$ ck-list-sessions' from inside your
plasma session.

Make sure your system-login file is valid:
https://wiki.gentoo.org/wiki/KDE/Plasma_5_upgrade#Missing_shutdown.2C_reboot.2C_suspend_and_hibernate_buttons_when_using_OpenRC

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


[kdenlive] [Bug 358782] New: 15.13 git master: cannot delete custom effects

2016-01-30 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358782

Bug ID: 358782
   Summary: 15.13 git master: cannot delete custom effects
   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

"Delete effect" in the context menu of a custom effect in the effects list has
(pun intented) no effect; the effect cannot be deleted.

Reproducible: Always

Steps to Reproduce:
1. Create a new custom effect.
2. Choose "delete effect" from the context menu on the new custom effect.


Actual Results:  
Nothing happens. The custom effect does not get deleted.

Expected Results:  
Custom effect is deleted.

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


[kdenlive] [Bug 358784] 15.13 git master: clips with fades using custom effects made from Fade to/from Black not properly shown in timeline

2016-01-30 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358784

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

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

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


[digikam] [Bug 331864] Merge Tags with same name when moving to same hierarchy level

2016-01-30 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=331864

jon33...@yahoo.co.uk changed:

   What|Removed |Added

 CC||jon33...@yahoo.co.uk

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


[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755

2016-01-30 Thread Niels Ole Salscheider via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358750

--- Comment #22 from Niels Ole Salscheider  ---
Or even better, use eglGetPlatformDisplayEXT to get a display for the right
platform (if available).

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


[konsole] [Bug 358763] New: Typing tilde character is difficult

2016-01-30 Thread Kari Ikonen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358763

Bug ID: 358763
   Summary: Typing tilde character is difficult
   Product: konsole
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: keyboard
  Assignee: konsole-de...@kde.org
  Reporter: mr.kari.iko...@gmail.com

When trying to type tilde (~), thus "ALTGR + [^"~]" combo to type it, konsole
often stucks into some strange accent mode, thus tilde appears with accent,
which of course causes that it doesn't work.

This is rather inconvenient, since getting away from this stuck mode requires
some random hitting of keys, until it magically unstucks itself.

I first thought this would be something caused by Virtualbox (since I first
time encountered issue there), but today I confirmed that same issue occurs in
normal non-virtual linux installation also.


Reproducible: Sometimes

Steps to Reproduce:
1. Try to type tilde (~), thus press ALTGR + [^"~] -keys
2.Occasionally only strange accented tilde appears (which is naturally not
working as tilde)
3.

Actual Results:  
Strange accented tilde character appears instead of tilde.


Expected Results:  
ALTGR + [^"~] produces ~

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


[krita] [Bug 358738] Krita crashes when opening any file or creating new one

2016-01-30 Thread Boudewijn Rempt via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358738

Boudewijn Rempt  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/call
   ||igra/75b56f6f1310982e062091
   ||f80039e916d9adade3
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Boudewijn Rempt  ---
Git commit 75b56f6f1310982e062091f80039e916d9adade3 by Boudewijn Rempt.
Committed on 30/01/2016 at 11:03.
Pushed by rempt into branch 'calligra/2.9'.

M  +2-1krita/ui/tool/kis_tool_paint.cc

http://commits.kde.org/calligra/75b56f6f1310982e062091f80039e916d9adade3

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


[frameworks-plasma] [Bug 358765] New: Scrolling in default apps is very slow

2016-01-30 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358765

Bug ID: 358765
   Summary: Scrolling in default apps is very slow
   Product: frameworks-plasma
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: libplasma
  Assignee: notm...@gmail.com
  Reporter: chermnykh2...@gmail.com

Scrolling in apps is very slow. https://youtu.be/7X6lZOdRM3s

Reproducible: Always

Steps to Reproduce:
1.  open folder in dolphin / apps menu / kwin effects settings
2.  scroll the mouse wheel

Actual Results:  
Laggy fonts, slow scrolling


kf5 5.18.0-1
plasma 5.5.4-1
OS: Arch Linux 
Kernel: x86_64 Linux 4.3.3-3-ARCH

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


[krita] [Bug 358734] [Hard] Incorrect 2nd square HSV color picker (checked by HCG color model)

2016-01-30 Thread acterhd via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358734

acterhd  changed:

   What|Removed |Added

  Attachment #96920|0   |1
is obsolete||

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


[kdenlive] [Bug 358784] New: 15.13 git master: clips with fades using custom effects made from Fade to/from Black not properly shown in timeline

2016-01-30 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358784

Bug ID: 358784
   Summary: 15.13 git master: clips with fades using custom
effects made from Fade to/from Black not properly
shown in timeline
   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

When applying a fade to/from black effect to a clip in the timeline in form of
a custom effect, then Kdenlive does not show any fade in/out indications.

Reproducible: Always

Steps to Reproduce:
1. Save Fade from Black as custom effect.
2. Apply to clip in timeline.


Actual Results:  
Clip in timeline has no fade from black indication.

Expected Results:  
Clip in timeline should have fade from black indication.

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


[krita] [Bug 358769] HCG color model support

2016-01-30 Thread acterhd via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358769

acterhd  changed:

   What|Removed |Added

 CC||acte...@gmail.com

--- Comment #1 from acterhd  ---
Created attachment 96922
  --> https://bugs.kde.org/attachment.cgi?id=96922=edit
HCG color model selector source

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


[krita] [Bug 358769] New: HCG color model support

2016-01-30 Thread acterhd via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358769

Bug ID: 358769
   Summary: HCG color model support
   Product: krita
   Version: 2.9.10
  Platform: Other
OS: other
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Dockers
  Assignee: krita-bugs-n...@kde.org
  Reporter: acte...@gmail.com

I already made support for HCG (2.9.10), just accept changes. 

Reproducible: Always

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


[kwin] [Bug 322496] quick tile indicator: window flashes when indicator fades out

2016-01-30 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=322496

Thomas Lübking  changed:

   What|Removed |Added

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

--- Comment #3 from Thomas Lübking  ---
essentially the same bug: we need to get rid of the requirement to elevate the
dragged client, the this bug disappears implicitly.

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

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

[kdev-python] [Bug 358770] New: no declarations created for arguments after *

2016-01-30 Thread Sven Brauch via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358770

Bug ID: 358770
   Summary: no declarations created for arguments after *
   Product: kdev-python
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language support
  Assignee: m...@svenbrauch.de
  Reporter: m...@svenbrauch.de

Example code:
def __init__(self, name: str, paths: CheriPaths, *, sourceDir="", buildDir="",
installDir: Path=None, gitUrl=""): pass

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


[kdev-python] [Bug 358770] no declarations created for arguments after *

2016-01-30 Thread Sven Brauch via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358770

Sven Brauch  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

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


[kde] [Bug 358771] New: Plasma crashed when changed the icon theme

2016-01-30 Thread Elvis Blanco via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358771

Bug ID: 358771
   Summary: Plasma crashed when changed the icon theme
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: elvisblanco1...@aol.com

Application: akonadi_migration_agent (4.89.0)
 (Compiled from sources)
Qt Version: 5.5.1
Operating System: Linux 4.2.0-25-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:
- Unusual behavior I noticed:
Plasma crashes everytime  i try to chhange the icon theme. Not a big deal but
it might be awful for some people

The crash can be reproduced every time.

-- Backtrace:
Application: Akonadi Agent (akonadi_migration_agent), signal: Segmentation
fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f945b970840 (LWP 1417))]

Thread 2 (Thread 0x7f94598a3700 (LWP 1446)):
#0  0x7f946a2218dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f9465b8dbd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f9465b8f74f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f945b5c97e9 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f946ab2ea6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f946576a6aa in start_thread (arg=0x7f94598a3700) at
pthread_create.c:333
#6  0x7f946a22ceed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f945b970840 (LWP 1417)):
[KCrash Handler]
#6  0x7f9465775af0 in _xend () at
../sysdeps/unix/sysv/linux/x86/elision-unlock.c:33
#7  __lll_unlock_elision (lock=0x7f94535f0008, private=128) at
../sysdeps/unix/sysv/linux/x86/elision-unlock.c:29
#8  0x7f946b509cfa in KSharedDataCache::clear() () from
/usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#9  0x7f946908fa46 in KIconLoader::reconfigure(QString const&, QStringList
const&) () from /usr/lib/x86_64-linux-gnu/libKF5IconThemes.so.5
#10 0x7f946908fcb3 in KIconLoader::newIconLoader() () from
/usr/lib/x86_64-linux-gnu/libKF5IconThemes.so.5
#11 0x7f946908fd9e in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5IconThemes.so.5
#12 0x7f946ad3e8ea in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7f9469086b1e in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5IconThemes.so.5
#14 0x7f9469091e5b in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5IconThemes.so.5
#15 0x7f946d8ce963 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#16 0x7f946ad3f7b1 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7f946bd409dc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x7f946bd45ea6 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x7f946ad0fd7b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7f946ad12176 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x7f946ad660e3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x7f946524aff7 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7f946524b250 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x7f946524b2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x7f946ad664ef in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x7f946ad0d50a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x7f946ad155ec in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#28 0x7f946d4f8e66 in Akonadi::AgentBase::init(Akonadi::AgentBase*) () from
/usr/lib/x86_64-linux-gnu/libKF5AkonadiAgentBase.so.5
#29 0x00416b48 in int
Akonadi::AgentBase::init(int, char**) ()
#30 0x7f946a146a40 in __libc_start_main (main=0x416210 , argc=3,
argv=0x7ffe24205f18, init=, fini=,
rtld_fini=, stack_end=0x7ffe24205f08) at libc-start.c:289
#31 0x00416399 in _start ()

Possible duplicates by query: bug 358565.

Reported using DrKonqi

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


[krita] [Bug 357880] Update G'Mic Filter to latest from Github (right mouse button no longer needed in interactive mode)

2016-01-30 Thread Boudewijn Rempt via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357880

Boudewijn Rempt  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/krit
   ||a/e53f5f454fa238510e2626b77
   ||1a8ef6b2d9deb23
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #11 from Boudewijn Rempt  ---
Git commit e53f5f454fa238510e2626b771a8ef6b2d9deb23 by Boudewijn Rempt.
Committed on 30/01/2016 at 14:15.
Pushed by rempt into branch 'master'.

Update g'mic to 1.6.9-pre

M  +10960 -5306 plugins/extensions/gmic/3rdparty/gmic/CImg.h
A  +49226 -0plugins/extensions/gmic/3rdparty/gmic/gimp_update169.gmic
M  +4938 -4262 plugins/extensions/gmic/3rdparty/gmic/gmic.cpp
M  +215  -194  plugins/extensions/gmic/3rdparty/gmic/gmic.h
M  +3-1plugins/extensions/gmic/CMakeLists.txt
M  +2-0plugins/extensions/gmic/Category.h
M  +2-1plugins/extensions/gmic/Command.cpp
M  +1-0plugins/extensions/gmic/Command.h
C  +6-37   plugins/extensions/gmic/Component.cpp [from:
plugins/extensions/gmic/Component.h - 050% similarity]
M  +6-5plugins/extensions/gmic/Component.h
M  +3-1plugins/extensions/gmic/kis_gmic_blacklister.h
M  +20   -28   plugins/extensions/gmic/kis_gmic_filter_model.cpp
M  +5-4plugins/extensions/gmic/kis_gmic_filter_model.h
M  +0-1plugins/extensions/gmic/kis_gmic_updater.cpp
M  +5-14   plugins/extensions/gmic/kis_gmic_widget.cpp

http://commits.kde.org/krita/e53f5f454fa238510e2626b771a8ef6b2d9deb23

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


[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave

2016-01-30 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354724

--- Comment #40 from Thomas Lübking  ---
Please file a review request (attaching the frameworks group), the bug is
assigned to Seli and I'm not sure anybody but us reads it.
I can already say that it lacks a QT_VERSION test.

About the Qt side, one might want to consider using a Qt::ApplicationAttribute
instead?
"Qt::AA_DoNotKludgeSessionSaving"?

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

[dolphin] [Bug 358649] Middle button on toolbar "GoUp" no longer functions

2016-01-30 Thread Frank Reininghaus via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358649

--- Comment #3 from Frank Reininghaus  ---
(In reply to Terry Barnaby from comment #2)
> Ok, will try and submit a bug/feature request in kf5. Any idea which of the
> many areas of kf5 this would be attributed to (frameworks-package ?)

I'm afraid this is not an easy question to answer. I think the cleanest
solution might be to include this functionality in Qt.

kdelibs 4.x had a class KAction that extends the functionality of QAction. This
class has a "triggered" signal that tells the receiver about the mouse button
that was used, and also about keyboard modifiers such as Shift:

http://api.kde.org/4.x-api/kdelibs-apidocs/kdeui/html/classKAction.html#a47c884a5a7b9b2284553fd5552a8

KToolBar::eventFilter(QObject * watched, QEvent * event) watched all events
that are delivered to the tool buttons and invoked the corresponding KAction's
triggered signal with the correct mouse button.

Like some other kdelibs classes, KAction was deprecated in KF5 and replaced by
the corresponding Qt class QAction. In principle, this is good because it
removes duplicated code and makes it easier to use and maintain, but
unfortunately, QAction only has a "triggered" signal that tells that the
toolbar button was clicked, but now with which button:

http://doc.qt.io/qt-5/qaction.html#triggered

Funnily enough, the code that filters middle-click mouse events and tries to
create a "triggered" signal with mouse button information still exists in
KToolBar in KF5 (kxmlgui framework), but it does not work and generates error
messages because QAction does not have a matching signal. It would in principle
still work in KF5 if a KAction (which is deprecated, but still exists in
kdelibs4support) was used. Dolphin and many other apps use KStandardAction to
create most actions though, and it creates QAction objects in KF5.

Un-deprecating KAction in KF5 and using it in KStandardAction would be a
solution, but I'm not sure how likely this is to happen. It might be better to
add this functionality to QAction, and also move the code that handles middle
clicks from KToolBar to QToolBar. This might not be easy either because one
could argue that the KAction API that has two different "triggered" signals is
a bit odd.

Maybe I will try to start a discussion on the KDE Frameworks mailing list about
this, but I cannot make any promises. Even if a way to merge this functionality
into Qt is found, it might take a long time until this functionality is
available for users.

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


[kmail2] [Bug 348752] Kmail2 4.18.4 - does not get mail on startup as it used to.

2016-01-30 Thread Ian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=348752

Ian  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |MOVED

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


[frameworks-knotifications] [Bug 358625] klarm crashed when opening from systray

2016-01-30 Thread David Jarvie via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358625

David Jarvie  changed:

   What|Removed |Added

 CC||kdelibs-b...@kde.org
   Assignee|djar...@kde.org |mklape...@kde.org
Product|kalarm  |frameworks-knotifications
  Component|general |general

--- Comment #2 from David Jarvie  ---
This looks like a bug in KStatusNotifierItem, so reassigning to
frameworks-knotifications.

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


[frameworks-knotifications] [Bug 358625] kalarm crashed when opening from systray

2016-01-30 Thread David Jarvie via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358625

David Jarvie  changed:

   What|Removed |Added

Summary|klarm crashed when opening  |kalarm crashed when opening
   |from systray|from systray
 CC||djar...@kde.org

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


[krita] [Bug 358734] [Hard] Incorrect 2nd square HSV color picker (checked by HCG color model)

2016-01-30 Thread acterhd via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358734

acterhd  changed:

   What|Removed |Added

  Attachment #96921|0   |1
is obsolete||

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


[krunner] [Bug 358774] New: Malformed URL

2016-01-30 Thread sivaram via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358774

Bug ID: 358774
   Summary: Malformed URL
   Product: krunner
   Version: 5.5.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: filesearch
  Assignee: m...@vhanda.in
  Reporter: sivaram.g...@gmail.com

When ever I try to search a file or folder in krunner menu , it lits a lot of
empty rows with only  help icon(?), when I click the row, Displays the pop up
Malformed url, 
I reindexed my folder multiple times by 
disabling and enabling the balooctl, 
and manually indexing using balooctl index 
Could not solve the problem
balooctl status returns
Indexer state: Idle
Indexed 35793 / 35793 files
Current size of index is 42.73 MiB


Reproducible: Always

Steps to Reproduce:
1. Press Alt+F2
2.Type a file/folder to be searched, empty list will be shown with help icon.
3.

Actual Results:  
Malformed URL

Expected Results:  
File/folder to be displayed on the list, cicking on them should open it.

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


[kshisen] [Bug 358773] New: kshisen shows as stuck when obvious moves remain

2016-01-30 Thread chili555 via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358773

Bug ID: 358773
   Summary: kshisen shows as stuck when obvious moves remain
   Product: kshisen
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: schwar...@kde.org
  Reporter: wrwes...@gmail.com
CC: kde-games-b...@kde.org

Created attachment 96923
  --> https://bugs.kde.org/attachment.cgi?id=96923=edit
Screenshot showing 'stuck.'

The version is from the Ubuntu package: Version: 4:15.08.2-0ubuntu1. As per the
attachment, the game reports 'stuck' when a move remains as shown by the
cursor.

Ubuntu 15.10
x86_64
4.2.0-25-generic

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


[krita] [Bug 358769] HCG color model support

2016-01-30 Thread acterhd via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358769

--- Comment #3 from acterhd  ---
Here you can found info about HCG color model. 
https://github.com/acterhd/hcg-color

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


[krita] [Bug 358734] [Hard] Incorrect 2nd square HSV color picker (checked by HCG color model)

2016-01-30 Thread acterhd via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358734

acterhd  changed:

   What|Removed |Added

  Attachment #96902|0   |1
is obsolete||

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


[kdenlive] [Bug 358777] New: Unlock threads - currently locked to 1-n where n is cores

2016-01-30 Thread Peter via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358777

Bug ID: 358777
   Summary: Unlock threads - currently locked to 1-n where n is
cores
   Product: kdenlive
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: pe...@corrosivetruths.org

When rendering, you are given the option of selecting a number of Encoder
threads. This is by default at 1, and can be increased up to n where n is
cores.

However, the ever popular x264's default is cores * 1.5 by default. It will use
this if you pass threads=0 to it.

So I believe the number of threads should be unlocked to allow a user to
specify any value and I think the default behaviour should be to have it set as
0 so that the encoder will (more often than 1 is appropriate) pick a sensible
number of threads to use.

Reproducible: Always

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


[kdenlive] [Bug 358695] 15.13 git master: in rendering dialog, allow for both processing and MLT threads

2016-01-30 Thread Peter via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358695

Peter  changed:

   What|Removed |Added

 CC||pe...@corrosivetruths.org

--- Comment #2 from Peter  ---
It would be neat-o if this was disabled when a project has non-thread safe
filters enabled in the project.

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


[plasmashell] [Bug 358076] Crash after try of getting context menu from one of system tray application by RMB

2016-01-30 Thread Piotr Mierzwinski via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358076

Piotr Mierzwinski  changed:

   What|Removed |Added

 CC||piotr.mierzwin...@gmail.com
Summary|Crash after try of getting  |Crash after try of getting
   |context menu from one of|context menu from one of
   |system try application by   |system tray application by
   |RMB |RMB

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


[kdenlive] [Bug 358782] 15.13 git master: cannot delete custom effects

2016-01-30 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358782

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

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

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


[okular] [Bug 334708] Accessing QPrinter to get the page size name is blocking if default printer is not connected

2016-01-30 Thread Albert Astals Cid via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=334708

Albert Astals Cid  changed:

   What|Removed |Added

 CC||dgilb...@redhat.com

--- Comment #16 from Albert Astals Cid  ---
*** Bug 358634 has been marked as a duplicate of this bug. ***

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


[okular] [Bug 358755] okular crash when opening a file inside gnu screen

2016-01-30 Thread Albert Astals Cid via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358755

Albert Astals Cid  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO
 CC||aa...@kde.org

--- Comment #1 from Albert Astals Cid  ---
Can you install debug symbols of kdelibs and give us the backtrace again?

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


[ark] [Bug 358597] Dolphin Crash on file drag and drop, in ark plugin extracthere

2016-01-30 Thread Matthew Courts via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358597

--- Comment #6 from Matthew Courts  ---
Elvis,
I found an update available for ark this morning, when looking for the debug
packages.  The update has resolved the issue for me.

I updated ark to version: 15.12.0-3.1

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


[clazy] [Bug 358740] Utils::isInitializedExternally: getSingleDecl fails to account for multiple declarations

2016-01-30 Thread Sergio Martins via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358740

--- Comment #1 from Sergio Martins  ---
Git commit 66b4e64dff863ce67195e82f081b3a6afd786e27 by Sergio Martins.
Committed on 30/01/2016 at 15:32.
Pushed by smartins into branch 'master'.

inefficient-qlist: Add test-case for a bug report

M  +5-1tests/inefficient-qlist/main.cpp

http://commits.kde.org/clazy/66b4e64dff863ce67195e82f081b3a6afd786e27

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


[krita] [Bug 358769] HCG color model support

2016-01-30 Thread acterhd via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358769

acterhd  changed:

   What|Removed |Added

  Attachment #96922|0   |1
is obsolete||

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


[krita] [Bug 358734] [Hard] Incorrect 2nd square HSV color picker (checked by HCG color model)

2016-01-30 Thread acterhd via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358734

--- Comment #10 from acterhd  ---
Need add support before: 
https://bugs.kde.org/show_bug.cgi?id=358769

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


[kdev-python] [Bug 358563] Possible infinite loop in UnsureType::toString()

2016-01-30 Thread Sven Brauch via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358563

--- Comment #6 from Sven Brauch  ---
I found a possibly related issue, could you maybe apply the patch below and see
if you can still reproduce your problem?

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


[kdevelop] [Bug 357615] C file parsed as a C++ file

2016-01-30 Thread Milian Wolff via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357615

--- Comment #11 from Milian Wolff  ---
Sergey, can you look into this issue?

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


[plasmashell] [Bug 358778] Blank space in system tray after upgrade 5.4.3 > 5.5.4

2016-01-30 Thread Petr Vorel via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358778

--- Comment #2 from Petr Vorel  ---
Created attachment 96927
  --> https://bugs.kde.org/attachment.cgi?id=96927=edit
Screenshot of the systemtray settings

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


[kdenlive] [Bug 358780] New: 15.13 git master: "expand clip" gives no user feedback for errors or during time-consuming expansion

2016-01-30 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358780

Bug ID: 358780
   Summary: 15.13 git master: "expand clip" gives no user feedback
for errors or during time-consuming expansion
   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 "expand clip" functionality is simply great, it adds so much value to
Kdenlive. However, my impression is that it needs some polish in order to avoid
the false impression that it doesn't work at all. In particular, I miss these
two these two aspects:

1. error feedback when expand clip is unable to expand a clip -- currently,
there is no error feedback at all and this left me often wondering what went
wrong.

2. (in) progress feedback while MLT crunches on more demanding clips --
currently, there is no feedback at all, so the user doesn't know whether
Kdenlive is still working. Especially as there is no error feedback either,
Kdenlive leaves users in the dark as to what is happening.

For instance, often Kdenlive is unable to expand a clip -- one cause for
expansion not working may be that the required tracks are already occupied by
clips at the range covered by the expanding clip. However, as there is no
feedback the user has no way to understand what to do when expansion fails.

I only found out by trial and error that library playlist clips usually expand
correctly when I put them to the end of the project timeline, a region where
there is enough space also track-wise to expand.

In addition, Kdenlive doesn't report back when there are not enough tracks to
expand a clip. Of course, it would be great if Kdenlive then could ask back to
add enough tracks and after confirmation then do the necessary changes and
expansion.

Reproducible: Always

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


[plasmashell] [Bug 358778] Blank space in system tray after upgrade 5.4.3 > 5.5.4

2016-01-30 Thread Petr Vorel via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358778

--- Comment #3 from Petr Vorel  ---
The blank space disappears when I uncheck 'Application status' in the system
tray settings.

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


  1   2   3   >