[dolphin] [Bug 360152] New: Dolphin crash on file move

[adimeymuc via KDE Bugzilla]

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

Bug ID: 360152
   Summary: Dolphin crash on file move
   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: adimey...@gmail.com

Application: dolphin (15.12.1)

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:
Trying to move a file (may have been accessed  by different applicaton [rsync]
in background)

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f673ce427c0 (LWP 2606))]

Thread 5 (Thread 0x7f6725e6d700 (LWP 2607)):
#0  0x7f673c6f2c1d in poll () at /lib64/libc.so.6
#1  0x7f672f629422 in  () at /usr/lib64/libxcb.so.1
#2  0x7f672f62b00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f67281ee3c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f67367d132f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f67322160a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f673c6fb04d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f6714445700 (LWP 2622)):
#0  0x7f673221a05f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f671af16a13 in  () at /usr/lib64/dri/radeonsi_dri.so
#2  0x7f671af16197 in  () at /usr/lib64/dri/radeonsi_dri.so
#3  0x7f67322160a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f673c6fb04d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f6712a15700 (LWP 2741)):
#0  0x7f673c6f2c1d in poll () at /lib64/libc.so.6
#1  0x7f6731681e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f6731681f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f6736a03d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f67369aad53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f67367cc61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f67367d132f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f67322160a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7f673c6fb04d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f670b975700 (LWP 15239)):
[KCrash Handler]
#6  0x7f67367cf47a in QThreadStorageData::finish(void**) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f67367d05ae in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f67367d1351 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f67322160a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f673c6fb04d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f673ce427c0 (LWP 2606)):
#0  0x7f673221a05f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f672f629669 in  () at /usr/lib64/libxcb.so.1
#2  0x7f672f62ad5f in  () at /usr/lib64/libxcb.so.1
#3  0x7f672f62ae72 in xcb_wait_for_reply () at /usr/lib64/libxcb.so.1
#4  0x7f67281e80ba in QXcbConnection::sync() () at
/usr/lib64/libQt5XcbQpa.so.5
#5  0x7f6728206b3e in  () at /usr/lib64/libQt5XcbQpa.so.5
#6  0x7f6728206dd7 in  () at /usr/lib64/libQt5XcbQpa.so.5
#7  0x7f6737b3e7f3 in  () at /usr/lib64/libQt5Widgets.so.5
#8  0x7f6737b3ec94 in  () at /usr/lib64/libQt5Widgets.so.5
#9  0x7f6737b5dd7f in QWidgetPrivate::syncBackingStore() () at
/usr/lib64/libQt5Widgets.so.5
#10 0x7f6737b71e94 in QWidget::event(QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#11 0x7f6737cad3db in QMenu::event(QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#12 0x7f6737b31e7c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#13 0x7f6737b36cc8 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#14 0x7f67369ace95 in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#15 0x7f67369af057 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#16 0x7f6736a048f3 in  () at /usr/lib64/libQt5Core.so.5
#17 0x7f6731681c84 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#18 0x7f6731681ed8 in  () at /usr/lib64/libglib-2.0.so.0
#19 0x7f6731681f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#20 0x7f6736a03d6c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#21 0x7f67369aad53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#22 0x7f6737ca7a20 in QMenu::exec(QPoint const&, QAction*) () at
/usr/lib64/libQt5Widgets.so.5
#23 0x7f673ca15812 in  () at /usr/lib64/libkdeinit5_dolphin.so
#24 0x7f673ca16dcd in  () at 

[kdeplasma-addons] [Bug 353091] Cannot specify own periods for timer widget

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #3 from Simone Gaiarin  ---
Thanks. I've missed the tooltip informations

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

[kmymoney4] [Bug 360129] CSV Importer doesn't recognize sell operation

[NSLW via KDE Bugzilla]

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

--- Comment #6 from NSLW  ---
*Besides wouldn't it be good if KMyMoney would ask only once to identify
unrecognized operation type?

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

[Breeze] [Bug 360151] Frequent segfault when a PyQt application exits.

[Rex Dieter via KDE Bugzilla]

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

Rex Dieter  changed:

   What|Removed |Added

Product|plasmashell |Breeze
   Target Milestone|1.0 |---
  Component|general |QStyle
   Assignee|k...@davidedmundson.co.uk|hugo.pere...@free.fr
 CC||rdie...@math.unl.edu

--- Comment #1 from Rex Dieter  ---
triaging to breeze (qt5) theme

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

[kdebugdialog] [Bug 360150] Can't copy .m4a files from my phone

[Laurent Montel via KDE Bugzilla]

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

Laurent Montel  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #1 from Laurent Montel  ---
kdebugdialog ??
Please reassign to correct component

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

[plasmashell] [Bug 360151] New: Frequent segfault when a PyQt application exits.

[Antony Lee via KDE Bugzilla]

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

Bug ID: 360151
   Summary: Frequent segfault when a PyQt application exits.
   Product: plasmashell
   Version: 5.5.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: anntzer@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

At the exit of various PyQt5 scripts, python segfaults fairly frequently.  This
is *not* (solely, at least) a PyQt related issue, as I cannot reproduce it when
using an XFCE session, and the PyQt main developer cannot reproduce it on MacOS
(https://www.riverbankcomputing.com/pipermail/pyqt/2016-February/037011.html).

Reproducible: Always

Steps to Reproduce:
Run the following Python script (PyQt 5.5.1, python2 or python3):
```
from PyQt5.QtWidgets import *
class Main(QMainWindow):
def fail(self):
QInputDialog.getItem(self, "foo", "bar", ["baz"])
raise Exception
app = QApplication([])
main = Main()
main.fail()
app.exec_()
```

Actual Results:  
After selecting a value and raising a (normal) exception, the application
segfaults (not always, but more than half of the time).

Expected Results:  
The application should exit with status 1 (failed with exception).

a gdb backtrace (without any debug informations, sorry):
```
(gdb) bt
#0  0x7505c01b in ?? () from /usr/lib/libQt5Core.so.5
#1  0x7505b29b in
QPropertyAnimation::updateState(QAbstractAnimation::State,
QAbstractAnimation::State) () from /usr/lib/libQt5Core.so.5
#2  0x75053679 in QAbstractAnimation::stop() () from
/usr/lib/libQt5Core.so.5
#3  0x7505a387 in QPropertyAnimation::~QPropertyAnimation() () from
/usr/lib/libQt5Core.so.5
#4  0x7fffdd8118b3 in ?? () from /usr/lib/qt/plugins/styles/breeze.so
#5  0x7528884b in QObjectPrivate::deleteChildren() () from
/usr/lib/libQt5Core.so.5
#6  0x752925d0 in QObject::~QObject() () from /usr/lib/libQt5Core.so.5
#7  0x7fffdd812913 in ?? () from /usr/lib/qt/plugins/styles/breeze.so
#8  0x7528884b in QObjectPrivate::deleteChildren() () from
/usr/lib/libQt5Core.so.5
#9  0x752925d0 in QObject::~QObject() () from /usr/lib/libQt5Core.so.5
#10 0x7fffdd813179 in ?? () from /usr/lib/qt/plugins/styles/breeze.so
#11 0x7528884b in QObjectPrivate::deleteChildren() () from
/usr/lib/libQt5Core.so.5
#12 0x752925d0 in QObject::~QObject() () from /usr/lib/libQt5Core.so.5
#13 0x7fffdd812a50 in ?? () from /usr/lib/qt/plugins/styles/breeze.so
#14 0x7528884b in QObjectPrivate::deleteChildren() () from
/usr/lib/libQt5Core.so.5
#15 0x752925d0 in QObject::~QObject() () from /usr/lib/libQt5Core.so.5
#16 0x7fffdd7eb0e9 in ?? () from /usr/lib/qt/plugins/styles/breeze.so
#17 0x7528a1a7 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#18 0x7528abbf in QObject::destroyed(QObject*) () from
/usr/lib/libQt5Core.so.5
#19 0x7529214a in QObject::~QObject() () from /usr/lib/libQt5Core.so.5
#20 0x7fffdd802b57 in ?? () from /usr/lib/qt/plugins/styles/breeze.so
#21 0x75250235 in ?? () from /usr/lib/libQt5Core.so.5
#22 0x75248732 in ?? () from /usr/lib/libQt5Core.so.5
#23 0x75248959 in ?? () from /usr/lib/libQt5Core.so.5
#24 0x75292618 in QObject::~QObject() () from /usr/lib/libQt5Core.so.5
#25 0x752478c0 in QFactoryLoader::~QFactoryLoader() () from
/usr/lib/libQt5Core.so.5
#26 0x75bb8439 in ?? () from /usr/lib/libQt5Widgets.so.5
#27 0x77382c38 in __run_exit_handlers () from /usr/lib/libc.so.6
#28 0x77382c85 in exit () from /usr/lib/libc.so.6
#29 0x7736d717 in __libc_start_main () from /usr/lib/libc.so.6
#30 0x00400b99 in _start ()
```

This occurs both with the breeze and oxygen themes (which I tried as they are
mentioned in the backtrace), but not under XFCE.

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

[okular] [Bug 359932] Okular is very slow at opening some EPUB's

[Albert via KDE Bugzilla]

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

--- Comment #5 from Albert  ---
the files are obviously there, but somewhere along the way either okular or
libepub add a kUrl path that causes the files to be lost in the process (ie..
instead of finding the file "cover-image.png" in the root of the epub, it tries
to find it in some path added by kURL in either libepub's implementation or
okular's)

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

[okular] [Bug 359932] Okular is very slow at opening some EPUB's

[Albert via KDE Bugzilla]

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

--- Comment #4 from Albert  ---
Created attachment 97705
  --> https://bugs.kde.org/attachment.cgi?id=97705=edit
okular-frameworks-git log from konsole

>Have you tried the attached epub in okular ?
indeed, running latest git okular-frameworks-git r7262.154c98f-1 (Sat Mar  5
22:50:10 CST 2016) from konsole, see attached file
all the libepub missing files are the same as on the link mentioned

running the patched version from the link provides a few more details:
libepub (II):   cover.xhtmlstylesheet.css - No such file
libepub (II):   cover.xhtmlcover-image.jpg - No such file
libepub (II):   cover.xhtmlcover-image.jpg - No such file
libepub (II):   title_page.xhtmlstylesheet.css - No such file
libepub (II):   title_page.xhtmlcover-image.jpg - No such file
libepub (II):   title_page.xhtmlcover-image.jpg - No such file
libepub (II):   ch1.xhtmlstylesheet.css - No such file
libepub (II):   ch1.xhtmlcover-image.jpg - No such file
libepub (II):   ch1.xhtmlcover-image.jpg - No such file
libepub (II):   ch2.xhtmlstylesheet.css - No such file
libepub (II):   ch2.xhtmlcover-image.jpg - No such file
libepub (II):   ch2.xhtmlcover-image.jpg - No such file
libepub (II):   ch3.xhtmlstylesheet.css - No such file
libepub (II):   ch3.xhtmlcover-image.jpg - No such file
libepub (II):   ch3.xhtmlcover-image.jpg - No such file


and as mentioned in the link, the structure of the epub (if you open in ark for
example) is what throws off either libepub or okular (or both)

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

[krita] [Bug 359934] Practiced zooming and panning after first download, stuck in pan mode

[Ireannia via KDE Bugzilla]

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

Ireannia  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #4 from Ireannia  ---
Thank you!

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

[kdebugdialog] [Bug 360150] New: Can't copy .m4a files from my phone

[Edward Goudge via KDE Bugzilla]

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

Bug ID: 360150
   Summary: Can't copy .m4a files from my phone
   Product: kdebugdialog
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mon...@kde.org
  Reporter: egou...@hotmail.com

Recorded some live music on my phone. It plays OK if I go to Apps, Tools, My
files and touch Voice.m4a. If I connect the phone to my Linux computer I
can find my way to the music file, and I can "Copy" it OK, however, I can't
paste it anywhere. I get the following message: Unknown error code 150. Bad
parameters. Please send a full Bug report to your address.

Reproducible: Always

Steps to Reproduce:
1. Described above
2.
3.

Actual Results:  
Complete failure

Expected Results:  
Copied the file to my computer, then convert the file to mp3 or other normal
format.

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

[kdenlive] [Bug 360149] Template titles no longer working in version 15.xx

[Alan Hagge via KDE Bugzilla]

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

Alan Hagge  changed:

   What|Removed |Added

   Keywords||regression, reproducible
 CC||nospam...@gmail.com

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

[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU

[Alexander Potashev via KDE Bugzilla]

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

--- Comment #62 from Alexander Potashev  ---
Created attachment 97704
  --> https://bugs.kde.org/attachment.cgi?id=97704=edit
command line output

David, I applied your patch to qtdeclarative-5.5.1 and reproduced the crash.
Please see the command line output in the attachment.

Below is the stacktrace, but I think it's did not change:

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

Thread 7 (Thread 0x7f7d94dcd700 (LWP 6882)):
#0  0x7f7da31f1aed in poll () from /lib64/libc.so.6
#1  0x7f7da72e1a92 in _xcb_conn_wait () from /usr/lib64/libxcb.so.1
#2  0x7f7da72e367f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f7d962d3159 in QXcbEventReader::run() () from
/usr/lib64/libQt5XcbQpa.so.5
#4  0x7f7da38d2246 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f7da29fc314 in start_thread () from /lib64/libpthread.so.0
#6  0x7f7da31fa6dd in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f7d8dbcb700 (LWP 6915)):
#0  0x7f7d9f2f9879 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f7d9f2b6bf0 in g_main_context_acquire () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f7d9f2b7a35 in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f7d9f2b7c8c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f7da3ad364b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#5  0x7f7da3a7eabb in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#6  0x7f7da38ccdfc in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#7  0x7f7da6147138 in QQmlThreadPrivate::run() () from
/usr/lib64/libQt5Qml.so.5
#8  0x7f7da38d2246 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#9  0x7f7da29fc314 in start_thread () from /lib64/libpthread.so.0
#10 0x7f7da31fa6dd in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f7d840bf700 (LWP 6933)):
#0  0x7f7da31f1aed in poll () from /lib64/libc.so.6
#1  0x7f7d9f2b7b74 in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f7d9f2b7c8c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f7da3ad364b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f7da3a7eabb in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f7da38ccdfc in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f7da6147138 in QQmlThreadPrivate::run() () from
/usr/lib64/libQt5Qml.so.5
#7  0x7f7da38d2246 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#8  0x7f7da29fc314 in start_thread () from /lib64/libpthread.so.0
#9  0x7f7da31fa6dd in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f7d82603700 (LWP 6940)):
#0  0x7f7d9f2f9894 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f7d9f2b71b0 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f7d9f2b7a90 in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f7d9f2b7c8c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f7da3ad364b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#5  0x7f7da3a7eabb in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#6  0x7f7da38ccdfc in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#7  0x7f7da6147138 in QQmlThreadPrivate::run() () from
/usr/lib64/libQt5Qml.so.5
#8  0x7f7da38d2246 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#9  0x7f7da29fc314 in start_thread () from /lib64/libpthread.so.0
#10 0x7f7da31fa6dd in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f7d7a85b700 (LWP 6983)):
#0  0x7f7da32069bf in __libc_enable_asynccancel () from /lib64/libc.so.6
#1  0x7f7da31f1ae2 in poll () from /lib64/libc.so.6
#2  0x7f7d9f2b7b74 in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f7d9f2b7c8c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f7da3ad364b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#5  0x7f7da3a7eabb in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#6  0x7f7da38ccdfc in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#7  0x7f7da6b04712 in QQuickPixmapReader::run() () from
/usr/lib64/libQt5Quick.so.5
#8  0x7f7da38d2246 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#9  0x7f7da29fc314 in start_thread () from /lib64/libpthread.so.0
#10 0x7f7da31fa6dd in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f7ce757b700 (LWP 7154)):
#0  0x7f7d9f2f9894 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f7d9f2b7b1e in g_main_context_iterate.isra () from

[kdenlive] [Bug 360149] New: Template titles no longer working in version 15.xx

[Alan Hagge via KDE Bugzilla]

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

Bug ID: 360149
   Summary: Template titles no longer working in version 15.xx
   Product: kdenlive
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: nospam...@gmail.com

With kdenlive 0.9.10 and below, I found template titles to be extremely useful
for inserting quick title information on a screen.  However, template titles do
not seem to be functional in the 15.xx releases (I'm currently using
15.13.0+git20160305.84c724b3-0ubuntu0~sunab~wily1 from the sunab svn
repository, but it has not functioned with any 15.xx release that I've tried).

The symptom is that if I open an existing template title, it shows up in the
Project Bin area, but right-clicking and choosing "Clip Properties" to modify
the text does not bring up any dialog at all.  It's basically treated as a
standard clip, where double-clicking on it brings up the Title Clip editor.

I use the function so frequently that right now I'm forced to use the 0.9.10
release.  I'm hoping that this will be an easy bug to quash, but that it just
hasn't been reported yet.

Reproducible: Always

Steps to Reproduce:
1. Open a new project
2. Use the title editor to create and save a template title
3. Load the template title via the Project Bin
4. Right click on the template title and select Clip Properties

Actual Results:  
Nothing.  No dialog box appears.

Expected Results:  
Dialog with Text box should appear to enter template text.

See
https://userbase.kde.org/Kdenlive/Manual/Titles#Template_Titles_-_User-Defined

No workaround that I have found.  Only option is to create individual titles,
which is a LOT more effort.

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

[okular] [Bug 359932] Okular is very slow at opening some EPUB's

[layus]

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

--- Comment #3 from Guillaume Maudoux (layus)  ---
It seems to me that it is unrelated. My log shows nothing like "cannot XXX".
What log are you referring to ?
And the attached epub has a very simple structure, and there seem to be no
error in libepub.

Have you tried the attached epub in okular ?

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

[Baloo] [Bug 352260] Baloo crashes when finding a new file

[Matthew Dawson via KDE Bugzilla]

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

--- Comment #4 from Matthew Dawson  ---
So, LMDB is failing with error MDB_BAD_TXN, with a message of "Transaction must
abort, has a child, or is invalid".  Having got an debug version of Baloo
installed, it turns out this gets printed earlier:

ASSERT failure in PositionDB::put: "MDB_MAP_FULL: Environment mapsize limit
reached", file
/var/tmp/portage/kde-frameworks/baloo-5.19.0/work/baloo-5.19.0/src/engine/positiondb.cpp,
line 80 
KCrash: Attempting to start /usr/bin/baloo_file from kdeinit
sock_file=/run/user/1000/kdeinit5__0
KCrash: Application 'baloo_file' crashing...
Aborted

For me, I have 6.5T worth of data in over 2 million files, so I'm not surprised
I broke a limit.  Would a system to recover from this error and resize the
database be ok?

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

[plasmashell] [Bug 360147] illegible notification that disappear without a chance to find them again

[arne anka via KDE Bugzilla]

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

arne anka  changed:

   What|Removed |Added

   Platform|Other   |Debian unstable

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

[plasmashell] [Bug 360148] New: after login no wallpapers but all black

[arne anka via KDE Bugzilla]

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

Bug ID: 360148
   Summary: after login no wallpapers but all black
   Product: plasmashell
   Version: 5.4.3
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Image Wallpaper
  Assignee: notm...@gmail.com
  Reporter: kde-b...@ginguppin.de
CC: plasma-b...@kde.org

since a few weeks, after almost every login (equals boot, since i log in once
after boot and shut down when done) the wallpapers are gone.

saved windows are restored, panel is there as well, and so far everything seems
to work, just that's there now wallpaper on any of my two monitors.

killing and starting plasmashell again makes the wallpapers appear again.

so far i have been unable to even find something related in any log.

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

[plasmashell] [Bug 360147] illegible notification that disappear without a chance to find them again

[arne anka via KDE Bugzilla]

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

--- Comment #1 from arne anka  ---
Created attachment 97703
  --> https://bugs.kde.org/attachment.cgi?id=97703=edit
screenshot showing illegible notification popup

instead of that piece of the panel's systray, there should be the actual
message and all the fancy stuff of a notification popup

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

[plasmashell] [Bug 360147] New: illegible notification that disappear without a chance to find them again

[arne anka via KDE Bugzilla]

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

Bug ID: 360147
   Summary: illegible notification that disappear without a chance
to find them again
   Product: plasmashell
   Version: 5.4.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Notifications
  Assignee: mklape...@kde.org
  Reporter: kde-b...@ginguppin.de
CC: plasma-b...@kde.org

most notably network-manager produces frequently notification popups that are
illegible since they simply show a piece of the windows behind it instead of
the actual message.

before they may (may not) render correctly, the popup disappears again and i am
unable to find them to at least check what it was about.

see attached screenshot for an example.

Reproducible: Sometimes

Steps to Reproduce:
1. happens very frequently
2.
3.

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

[konsole] [Bug 360146] Konsole crash while searching history

[Matthew Dawson via KDE Bugzilla]

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

--- Comment #1 from Matthew Dawson  ---
Oh, I forgot to mention it crashed at:
buffer[i] = _fileMap[loc + i];   with i == 0
Since loc was < 0, I assumed the crash had a clear cause.  The assert to catch
it a few files up was missed as I'm compiled with QT_NO_DEBUG set.

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

[konsole] [Bug 360146] New: Konsole crash while searching history

[Matthew Dawson via KDE Bugzilla]

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

Bug ID: 360146
   Summary: Konsole crash while searching history
   Product: konsole
   Version: 15.12.2
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: matt...@mjdsystems.ca

Application: konsole (15.12.2)
 (Compiled from sources)
Qt Version: 5.5.1
Operating System: Linux 4.3.3-gentoo x86_64
Distribution: "Gentoo Base System release 2.2"

-- Information about the crash:
While searching through my history for "..", konsole crashed.  Just before I
had tried searching for ".." and it had landed me in a different part of my
history I didn't care about, so I scrolled back and tried again.  That time
konsole crashed.

-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
81T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7f93f860a880 (LWP 9630))]

Thread 2 (Thread 0x7f93e7572700 (LWP 9633)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f93efa1152b in cnd_wait (mtx=0xcf6c80, cond=0xcf6ca8) at
/usr/src/debug/media-libs/mesa-11.1.2/mesa-11.1.2/include/c11/threads_posix.h:159
#2  pipe_semaphore_wait (sema=0xcf6c80) at
/usr/src/debug/media-libs/mesa-11.1.2/mesa-11.1.2/src/gallium/auxiliary/os/os_thread.h:259
#3  radeon_drm_cs_emit_ioctl (param=param@entry=0xcf6930) at
/usr/src/debug/media-libs/mesa-11.1.2/mesa-11.1.2/src/gallium/winsys/radeon/drm/radeon_drm_winsys.c:653
#4  0x7f93efa110f8 in impl_thrd_routine (p=) at
/usr/src/debug/media-libs/mesa-11.1.2/mesa-11.1.2/include/c11/threads_posix.h:87
#5  0x7f94040a5552 in start_thread (arg=0x7f93e7572700) at
pthread_create.c:333
#6  0x7f940bda796d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f93f860a880 (LWP 9630)):
[KCrash Handler]
#6  0x7f940b9e3b5c in Konsole::HistoryFile::get (loc=-2628, size=2628,
buffer=, this=0xfa1f50) at
/usr/src/debug/kde-apps/konsole-15.12.2/konsole-15.12.2/src/History.cpp:163
#7  Konsole::HistoryScrollFile::getCells (this=0xfa1f10, lineno=, colno=, count=, res=) at
/usr/src/debug/kde-apps/konsole-15.12.2/konsole-15.12.2/src/History.cpp:262
#8  0x7f940ba15465 in Konsole::Screen::copyLineToStream
(this=this@entry=0xbe3b30, line=line@entry=-6399987, start=,
count=219, count@entry=-1, decoder=decoder@entry=0x7ffe90b74920,
appendNewLine=appendNewLine@entry=true, preserveLineBreaks=true,
trimTrailingSpaces=false) at
/usr/src/debug/kde-apps/konsole-15.12.2/konsole-15.12.2/src/Screen.cpp:1239
#9  0x7f940ba15608 in Konsole::Screen::writeToStream (this=0xbe3b30,
decoder=0x7ffe90b74920, startIndex=, endIndex=,
preserveLineBreaks=true, trimTrailingSpaces=false) at
/usr/src/debug/kde-apps/konsole-15.12.2/konsole-15.12.2/src/Screen.cpp:1184
#10 0x7f940ba31f2a in Konsole::SearchHistoryTask::executeOnScreenWindow
(this=this@entry=0x11c1930, session=..., window=...) at
/usr/src/debug/kde-apps/konsole-15.12.2/konsole-15.12.2/src/SessionController.cpp:1882
#11 0x7f940ba323f1 in Konsole::SearchHistoryTask::execute (this=0x11c1930)
at
/usr/src/debug/kde-apps/konsole-15.12.2/konsole-15.12.2/src/SessionController.cpp:1802
#12 0x7f940ba2fa0f in Konsole::SessionController::beginSearch
(this=0x1084580, text=..., direction=1) at
/usr/src/debug/kde-apps/konsole-15.12.2/konsole-15.12.2/src/SessionController.cpp:1274
#13 0x7f940875436b in QtPrivate::QSlotObjectBase::call (a=0x7ffe90b74bb0,
r=0x1084580, this=) at
../../src/corelib/kernel/qobject_impl.h:124
#14 QMetaObject::activate (sender=sender@entry=0xdceb90,
signalOffset=,
local_signal_index=local_signal_index@entry=32766, argv=argv@entry=0xb218b0) at
kernel/qobject.cpp:3698
#15 0x7f9408754e12 in QMetaObject::activate (sender=sender@entry=0xdceb90,
m=m@entry=0x7f940bcb0e40 ,
local_signal_index=32766, local_signal_index@entry=0, argv=0xb218b0,
argv@entry=0x7ffe90b74bb0) at kernel/qobject.cpp:3578
#16 0x7f940ba6d515 in Konsole::IncrementalSearchBar::searchChanged
(this=this@entry=0xdceb90, _t1=...) at
/usr/src/debug/kde-apps/konsole-15.12.2/konsole-15.12.2_build/src/moc_IncrementalSearchBar.cpp:251
#17 0x7f940b9e8718 in Konsole::IncrementalSearchBar::notifySearchChanged
(this=0xdceb90) at
/usr/src/debug/kde-apps/konsole-15.12.2/konsole-15.12.2/src/IncrementalSearchBar.cpp:150
#18 0x7f940875436b in QtPrivate::QSlotObjectBase::call (a=0x7ffe90b74cc0,
r=0xdceb90, this=) at
../../src/corelib/kernel/qobject_impl.h:124
#19 QMetaObject::activate (sender=sender@entry=0x1021630,
signalOffset=,
local_signal_index=local_signal_index@entry=32766, argv=argv@entry=0xb218b0) at
kernel/qobject.cpp:3698
#20 0x7f9408754e12 in QMetaObject::activate (sender=sender@entry=0x1021630,

[konsole] [Bug 360142] tried updating sources/ check for updates

[Mark Rudeseal via KDE Bugzilla]

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

--- Comment #2 from Mark Rudeseal  ---
ok, I found the reason for the failures.   

I am using google chrome, google has misreported something.
 I did not fix the error, I just unchecked the box in software sources that
google had put in. (http://dl.google.com/linux/chrome/db/ stable main)

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

[digikam] [Bug 360017] build error: opencv_contrib is required but was not found

[Thomas Eschenbacher via KDE Bugzilla]

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

Thomas Eschenbacher  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Resolution|DOWNSTREAM  |---
 Status|RESOLVED|REOPENED

--- Comment #4 from Thomas Eschenbacher  ---
I have to re-open that topic.
I found out that all that trouble was caused by digikam itself!

The big bug is that the bootstrap.linux script contains the parameter
-DENABLE_OPENCV3=OFF in the cmake command line, _HARD CODED_ !!!  and _after_
including the user defineable parameter list ADDITIONAL_CMAKE_FLAGS. So adding
-DENABLE_OPENCV3=ON to ADDITIONAL_CMAKE_FLAGS in bootstrap.local is pretty
useless!

Please fix the bootstrap.linux script to allow overriding _all_ the hardcoded
settings and adjust the comments in bootstrap.local !

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

[kmymoney4] [Bug 360129] CSV Importer doesn't recognize sell operation

[allan via KDE Bugzilla]

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

--- Comment #4 from allan  ---
After your step 10 above, the CSV Importer window displays the first
transaction as an Invalid Transaction Type, because the importer does not
understand Polish, so it gives you the opportunity to select what type of
activity 'Sprzedaż' really is, in KMyMoney language.  In the drop-down, you
need to select Sell Shares, this being one of the activity types that match the
values - quantity, price, amount - that are in that transaction.  You should
see now that the Type is Sell.  As this transaction type involves money, you
next need to enter the name of the checking/brokerage account you wish to use. 
The next transaction follows a similar path, with 'Kupno' as the activity type.
 So, for this you need to select Buy Shares.  The remaining transactions follow
the same course.

I notice that the Buy transactions imported show as unbalanced, with a missing
assignment of 6,00.  It rather looks as though the fee is getting the wrong
sign, which I'll need to have a look into.

If any of that is unclear, please let me know.  If you think the handbook needs
expanding, also, please say how.

Allan

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

[cantor] [Bug 348128] The sage backend does not starts with sage 6.7

[via KDE Bugzilla]

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

mathc...@outlook.com changed:

   What|Removed |Added

 CC||mathc...@outlook.com

--- Comment #21 from mathc...@outlook.com ---
I had the same problem on ubuntu 14.04, and to save the trouble of rebuilding
Cantor I created the following shell script and set it as Cantor's sage path:

echo "┌┐"
echo "│ Sage Version 6.8, Release Date: 2015-07-26 │"
sage "$@"

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

[plasmashell] [Bug 342763] Crash In Task Manager Item Changed

[Erick Osorio via KDE Bugzilla]

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

--- Comment #167 from Erick Osorio  ---
I'm in OpenSUSE Leap 
Qt 5.5.1
Plasma 5.5.5

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

[plasmashell] [Bug 342763] Crash In Task Manager Item Changed

[Erick Osorio via KDE Bugzilla]

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

--- Comment #166 from Erick Osorio  ---
Created attachment 97702
  --> https://bugs.kde.org/attachment.cgi?id=97702=edit
task manager's settings

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

[systemsettings] [Bug 360145] New: Capslock key misbehaves when using colemak layout

[Jesse via KDE Bugzilla]

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

Bug ID: 360145
   Summary: Capslock key misbehaves when using colemak layout
   Product: systemsettings
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_keyboard_layout
  Assignee: ary...@gmail.com
  Reporter: je...@fastmail.net

When using the Colemak layout, the capslock key is supposed to become a
backspace key.  The key does work as backspace, but also retains its capslock
function.  The end result is both a backspace, and also now capslock has been
toggled.  This was tested on a thinkpad t410.

When setting the layout with the command "setxkbmap us -variant colemak" the
capslock key works as expected.  It is only when setting the layout within kde
that the error occurs.

Reproducible: Always

Steps to Reproduce:
1. Configure Desktop -> Input devices -> Layout
2. Enable Colemak US variant layout
3. Press the capslock key

Actual Results:  
Backspace and capslock are activated

Expected Results:  
Only backspace should activate

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

[konsole] [Bug 360072] Option "manage profiles" doesn't work, doesn't do anything

[Anthony via KDE Bugzilla]

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

Anthony  changed:

   What|Removed |Added

 CC||bugnotificati...@storio.io

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

[krita] [Bug 360139] Inherit Alpha isn't working

[wolthera via KDE Bugzilla]

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

wolthera  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||griffinval...@gmail.com
 Resolution|--- |INVALID

--- Comment #1 from wolthera  ---
>From irc we figured out it was the group pass-trhough messing things up.

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

[valgrind] [Bug 359871] Incorrect mask handling in ppoll

[Ivo Raisr via KDE Bugzilla]

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

Ivo Raisr  changed:

   What|Removed |Added

  Attachment #97643|0   |1
is obsolete||
  Attachment #97688|0   |1
is obsolete||

--- Comment #19 from Ivo Raisr  ---
Created attachment 97701
  --> https://bugs.kde.org/attachment.cgi?id=97701=edit
combined patch for ppoll and pselect on Linux and Solaris

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

[okular] [Bug 359932] Okular is very slow at opening some EPUB's

[Albert via KDE Bugzilla]

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

--- Comment #2 from Albert  ---
the referenced path does allow the ebooks to be opened faster, but the log is
still full of missing path/file errors

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

[okular] [Bug 359932] Okular is very slow at opening some EPUB's

[Albert via KDE Bugzilla]

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

Albert  changed:

   What|Removed |Added

 CC||kdebug-specta...@yahoo.com

--- Comment #1 from Albert  ---
this happens with epubs with weird directory structures for the most part as
per:
https://git.reviewboard.kde.org/r/125500/
has a patch that fixes the loading problem in maybe half the cases, but some
epubs still manage to freeze.  on the log it will also show several "cannot
find [path to file]/filename" errors (mainly with locating images/css).
it looks like the main issue is with libepub which is not maintained, not
handling the paths correctly.  the patch submitter above mentions "
non-canonical path in libepub. I fixed it in my fork of library" but that fork
is nowhere to be found.

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

[frameworks-plasma] [Bug 351777] plasmashell crashed might due to applet actions is nullptr

[Michael Marley via KDE Bugzilla]

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

Michael Marley  changed:

   What|Removed |Added

 CC||mich...@michaelmarley.com

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

[calligraflow] [Bug 321567] Connecting shapes does not have arrows

[David E . Narvaez via KDE Bugzilla]

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

David E. Narvaez  changed:

   What|Removed |Added

 CC||david.narv...@computer.org

--- Comment #1 from David E. Narvaez  ---
In Version 2.9.11, I pick the arrow end in the tool options when connecting
shapes and it does not add the the arrow.

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

[kig] [Bug 359805] strange loss of drawing precision when drawing circles

[Maurizio Paolini via KDE Bugzilla]

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

--- Comment #5 from Maurizio Paolini  ---
Created attachment 97700
  --> https://bugs.kde.org/attachment.cgi?id=97700=edit
patch proposal

This patch adds toScreenF methods alongside toScreen and uses it to create a
QRectF instead of a QRect in CircleImp::draw

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

[valgrind] [Bug 359871] Incorrect mask handling in ppoll

[Ivo Raisr via KDE Bugzilla]

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

--- Comment #18 from Ivo Raisr  ---
Thank you for a quick turnaround. I think this should work.
As regards the scalar test, if you are not able to get it working with high
confidence then we should probably leave it alone.
I will combine patches for Linux and Solaris together and commit them.

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

[kdeplasma-addons] [Bug 360120] Show Desktop Applet corrupts panel when added to it (spacing issues)

[Viorel-Cătălin Răpițeanu via KDE Bugzilla]

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

Viorel-Cătălin Răpițeanu  changed:

   What|Removed |Added

 CC||rapiteanu.cata...@gmail.com

--- Comment #1 from Viorel-Cătălin Răpițeanu  ---
I'm affected by this issue as well. I'm using the same version and the same
distribution as perrantrevan.

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

[kmymoney4] [Bug 360129] CSV Importer doesn't recognize sell operation

[allan via KDE Bugzilla]

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

allan  changed:

   What|Removed |Added

 CC||agande...@gmail.com

--- Comment #3 from allan  ---
This does work for me, but I'll need to get back to you later with a bit more
detail about what is required.
Allan

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

[systemsettings] [Bug 360144] New: Activities KCM: Activity configuration window cannot be focussed

[Jonathan Marten via KDE Bugzilla]

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

Bug ID: 360144
   Summary: Activities KCM: Activity configuration window cannot
be focussed
   Product: systemsettings
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: j...@keelhaul.me.uk

When running the "kcm_activities" module (through systemsetting5 or using
"kcmshell5 kcm_activities", the first "Activities" tab lists all of the
configured activities.  To the right of each of them is a "configure" (spanner)
and a "remove" (cross) button.

Clicking on the "configure" button appears to do nothing.  In reality it has
opened an "Activity settings" window, but behind the initial window and
unfocussed.  Moveing the initial window aside reveals this window, but it will
not take focus and will not accept any interaction apart from the title bar
buttons.

The message "kcmshell5[setFocus]: GeneralTab: Set focus called" is printed on
stderr.


Reproducible: Always

Steps to Reproduce:
1.  Run "kcmshell5 kcm_activities" or open the appropriate module via
systemsettings5.
2.  Click on the "configure" button of any activity.
3.  Move the initial window aside.


Actual Results:  
Hidden and unfocussable window appears as described.


Expected Results:  
It should be possible to focus and interact with the window that opens.


Actual systemsettings5 version: "systemsettings 5.6.90"

Not sure whether the bug classification is correct, but there is no component
here for "kcm_activities" and no appropriate component under plasmashell
either.

Window behaviour settings: Policy = Focus Follows Mouse - Mouse Precedence
Delay focus by = 0ms
Focus stealing prevention = Low
Raising windows = Raise on hover, delayed 550ms

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

[kdenlive] [Bug 360084] 15.13.0 git master - Audio is not synced with video during playback -- video plays faster (sample clip included)

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #3 from Jean-Baptiste Mardelle  ---
Hi Jesse,

Interesting. Kdenlive crashed if you were using a custom project profile as
default project profile. I just fixed it in git, please try if you can..
Otherwise open your kdenlive config file:

$HOME/.config/kdenliverc

and search for the line:
default_profile= (...)  (should show a path to customprofile0)

Just completely delete that line, save and restart Kdenlive

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

[kdenlive] [Bug 360133] 15.13 git master: effect group initially shows disabled state but is enable.

[via KDE Bugzilla]

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

--- Comment #2 from wegwerf-1-...@gmx.de ---
Jean-Baptiste, thank you very much for the quick fix. I've tested it and it
works also over here.

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

[kdenlive] [Bug 360143] 15.13.0 git master - Consider disabling automatic Affine transition when inserting title clips. No longer needed by default?

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

Summary|15.13.0 git master - Affine |15.13.0 git master -
   |transition no longer needed |Consider disabling
   |for Title clip by default?  |automatic Affine transition
   ||when inserting title clips.
   ||No longer needed by
   ||default?

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

[kdenlive] [Bug 360143] New: 15.13.0 git master - Affine transition no longer needed for Title clip by default?

[Jesse via KDE Bugzilla]

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

Bug ID: 360143
   Summary: 15.13.0 git master - Affine transition no longer
needed for Title clip by default?
   Product: kdenlive
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: jesse.dub...@gmail.com

When you insert a title clip into the timeline, the affine transition is
automatically put below it. With the composite tracks now working properly (and
I don't see any issues anymore in quality between the title clips with
composite tracks vs title clips with affine transition) do the title clips need
to have the Affine transition added by default?

Consider removing automatic insertion of Affine transition when inserting a
title clip. Main reason being it doesn't seem to behave normally with other
clips. Might be a little confusing to the user.

Reproducible: Always




Suggested while using Kdenlive latest git master build, Kubuntu 15.10 x64, KDE
Frameworks 15.18.0 via kubuntu backports ppa.

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

[kdenlive] [Bug 360143] 15.13.0 git master - Affine transition no longer needed for Title clip by default?

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

 CC||jesse.dub...@gmail.com

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

[konsole] [Bug 360142] tried updating sources/ check for updates

[Mark Rudeseal via KDE Bugzilla]

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

--- Comment #1 from Mark Rudeseal  ---
Created attachment 97699
  --> https://bugs.kde.org/attachment.cgi?id=97699=edit
what I see after using Konsole, muon updater/ and muon package manager, when
trying to check for updates

W: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/Release 
Unable to find expected entry 'main/binary-i386/Packages' in Release file
(Wrong sources.list entry or malformed file)

E: Some index files failed to download. They have been ignored, or old ones
used instead.

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

[konsole] [Bug 360142] New: tried updating sources/ check for updates

[Mark Rudeseal via KDE Bugzilla]

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

Bug ID: 360142
   Summary: tried updating sources/ check for updates
   Product: konsole
   Version: 15.08.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: xtremedevi...@yahoo.com

W: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/Release 
Unable to find expected entry 'main/binary-i386/Packages' in Release file
(Wrong sources.list entry or malformed file)

E: Some index files failed to download. They have been ignored, or old ones
used instead.


Reproducible: Always

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

[muon] [Bug 360141] New: muon software mirror update fails, no matter what mirror I choose

[Mark Rudeseal via KDE Bugzilla]

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

Bug ID: 360141
   Summary: muon software mirror update fails, no matter what
mirror I choose
   Product: muon
   Version: 5.4.2
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: muon
  Assignee: echidna...@kubuntu.org
  Reporter: xtremedevi...@yahoo.com
CC: aleix...@kde.org, sit...@kde.org

tried to check for updates in both muon updater and muon package manager.
during the sources check, it stops and reports failed. I tried different mirror
sources and even reinstalling Kubuntu 15:10 and still the error persists

Reproducible: Always

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

[kdenlive] [Bug 360096] 15.13.0 git master - Monitor doesn't show video when switching to another tab, then back (video example included)

[Jesse via KDE Bugzilla]

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

--- Comment #2 from Jesse  ---
Ugh, gotta love the issues that can't be reproduced on the dev's end.

No sir, just a single monitor, set to 1920 x 1080, 60hz refresh rate.

I just tested a fresh install using the latest mlt .deb builds from Olivier
Banus' ppa, and the latest Kdenlive git .deb builds from the
Kubuntu-ci/unstable ppa. Same issue. :/

I'm also running two Nvidia GTX 660 graphics cards and the Nvidia 352.63
proprietary driver (the graphics cards are not SLI'd; Kubuntu is using the top
one closes to the cpu on the motherboard, and ignoring the bottom one).

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

[kwin] [Bug 360140] Fall apart effect not working

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #1 from Thomas Lübking  ---
please attach the output of
   qdbus org.kde.KWin /KWin supportInformation

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

[kdenlive] [Bug 360084] 15.13.0 git master - Audio is not synced with video during playback -- video plays faster (sample clip included)

[Jesse via KDE Bugzilla]

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

--- Comment #2 from Jesse  ---
Hey JB. Thanks for looking into this. The default profile is 1920x1080, 24fps.
When I added the clip to the Project Bin, it asked to convert it to a custom
2048 x 1152 23.98fps.

I tried opening the clip on a fresh install of Kdenlive with the latest mlt
.deb builds from olivier banus' ppa (MLT 6.1.0, build 2016.03.03), but it gave
me an error this time: "Cannot open file
/home/jesse/.local/share/kdenlive/profiles/customprofile0". I checked the
folder path, and discovered there's no file folder "profiles" in
/home/jesse/.local/share/kdenlive...

The plot thickens. Any suggestions?

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

[kwin] [Bug 360137] Low performance when moving mouse cursor over task manager tabs in panel

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #3 from Thomas Lübking  ---
> the cursor jumps for 1 to 1.5 seconds
The cursor should be done in hardware and painted directly into the scanout
buffer.

Does any other item in the panel cause this?

Let's say I simply completely distrust QML.
Please edit
/usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/main.qml and
comment 

// toolTipItem: toolTipDelegate

and 

//ToolTipDelegate {
//id: toolTipDelegate

//visible: false
//}

restart plasmashell and check again.

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

[kdenlive] [Bug 360138] User interface completely broken

[Barade via KDE Bugzilla]

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

--- Comment #1 from Barade  ---
Btw. it renders only 5 minutes of the project although I selected "Render the
whole project" and its a clip which is 13 minutes long. Its an FLV clip I
imported. I am trying to render the selected zone now which is as long as the
project.

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

[kwin] [Bug 360140] New: Fall apart effect not working

[via KDE Bugzilla]

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

Bug ID: 360140
   Summary: Fall apart effect not working
   Product: kwin
   Version: 5.5.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: effects-window-management
  Assignee: kwin-bugs-n...@kde.org
  Reporter: hid...@gmx.de

The fall apart effect is not working

Reproducible: Always

Steps to Reproduce:
1. Enable the "Fall apart" effect (in the Desktop effects menu)
2. Close a window

Actual Results:  
Window closes normaly

Expected Results:  
The window should be falling apart

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

[kwin] [Bug 360140] Fall apart effect not working

[via KDE Bugzilla]

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

hid...@gmx.de changed:

   What|Removed |Added

 CC||hid...@gmx.de

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

[kio] [Bug 349531] dolphin 15.04.0 tries to start gwenview but it really doesn't

[Luca Olivetti via KDE Bugzilla]

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

--- Comment #10 from Luca Olivetti  ---
Well, there shouldn't be but there is.

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

[krita] [Bug 359272] Krita2.9.11: Instant crash on clicking Brush Editor scratch pad(no crash with fresh configuration)

[via KDE Bugzilla]

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

gitcheg...@gmail.com changed:

   What|Removed |Added

 CC||gitcheg...@gmail.com

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

[krita] [Bug 360139] New: Inherit Alpha isn't working

[via KDE Bugzilla]

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

Bug ID: 360139
   Summary: Inherit Alpha isn't working
   Product: krita
   Version: 2.9.11
  Platform: unspecified
OS: MS Windows
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: adjustment layers
  Assignee: krita-bugs-n...@kde.org
  Reporter: eduardelric...@gmail.com

Inherit alpha isn't working, I have tried to put them in groups, as the lower
layer, not even with only two layers

Reproducible: Always

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

[kdenlive] [Bug 360138] User interface completely broken

[Barade via KDE Bugzilla]

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

Barade  changed:

   What|Removed |Added

   Platform|Other   |Fedora RPMs
   Severity|normal  |critical
 OS|unspecified |Linux

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

[kdenlive] [Bug 360138] New: User interface completely broken

[Barade via KDE Bugzilla]

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

Bug ID: 360138
   Summary: User interface completely broken
   Product: kdenlive
   Version: unspecified
  Platform: Other
OS: unspecified
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: barade.bar...@web.de

Hello, I cannot move the audio the volume keyframes. Selecting them on the
track does not work. Moving them a bit leads to a complete removal.

I cant move titles from one track to another. Besides kdenlive does not seem to
store a project as it is. Clips are completely messed up when I load a project.

There seem to be a lot of bugs in this version.
It is version 15.12.2 on Fedora and I cant use kdenlive this way anymore. I
will use different tool now.

Reproducible: Always

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

[kwin] [Bug 360137] Low performance when moving mouse cursor over task manager tabs in panel

[Bernd Steinhauser via KDE Bugzilla]

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

--- Comment #2 from Bernd Steinhauser  ---
Created attachment 97698
  --> https://bugs.kde.org/attachment.cgi?id=97698=edit
glxinfo

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

[kwin] [Bug 360137] Low performance when moving mouse cursor over task manager tabs in panel

[Bernd Steinhauser via KDE Bugzilla]

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

--- Comment #1 from Bernd Steinhauser  ---
Created attachment 97697
  --> https://bugs.kde.org/attachment.cgi?id=97697=edit
qdbus-qt5 org.kde.KWin /KWin org.kde.KWin.supportInformation

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

[kdenlive] [Bug 360133] 15.13 git master: effect group initially shows disabled state but is enable.

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kden
   ||live/0f554780fecb07f823dbcb
   ||29a083bba39893a2e3
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Jean-Baptiste Mardelle  ---
Git commit 0f554780fecb07f823dbcb29a083bba39893a2e3 by Jean-Baptiste Mardelle.
Committed on 05/03/2016 at 19:18.
Pushed by mardelle into branch 'master'.

Fix effect group icon on creation

M  +0-1src/effectstack/collapsiblegroup.cpp

http://commits.kde.org/kdenlive/0f554780fecb07f823dbcb29a083bba39893a2e3

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

[kio] [Bug 350668] Dolphin Crash when transfer of files from external media finishes

[David Faure via KDE Bugzilla]

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

--- Comment #2 from David Faure  ---
Does this still happen?

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

[kio] [Bug 349531] dolphin 15.04.0 tries to start gwenview but it really doesn't

[David Faure via KDE Bugzilla]

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

--- Comment #9 from David Faure  ---
I see no relation between kwallet and file associations.
File associations (which file is opened in which app) is NOT configured in
~/.kde, BTW, but in ~/.config/mimeapps.list and/or
~/.local/share/applications/mimeapps.list

Debugging why an app doesn't start is best done by looking at the logs in
~/.xsession-errors*

Sorry for the delay though, I guess this doesn't apply anymore :(

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

[kdeplasma-addons] [Bug 360120] Show Desktop Applet corrupts panel when added to it (spacing issues)

[Arthur Țițeică via KDE Bugzilla]

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

Arthur Țițeică  changed:

   What|Removed |Added

 CC||arthur.tite...@gmail.com

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

[Breeze] [Bug 360136] New: mimetype icon missing for DjVu files.

[Paul via KDE Bugzilla]

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

Bug ID: 360136
   Summary: mimetype icon missing for DjVu files.
   Product: Breeze
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: pip@gmx.com
CC: kain...@gmail.com

Breeze "breeze5-icons-5.19.0-1.1" does not contain a mimetype icon for DjVu
files.

image/vnd.djvu
image/x-djvu

For reference, typical icon:
https://commons.wikimedia.org/wiki/File:Djvu_icon.svg

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

[kde] [Bug 360135] New: Az Adobe Reader megnyitása után a KWin összeomlott

[Regényi Örs via KDE Bugzilla]

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

Bug ID: 360135
   Summary: Az Adobe Reader megnyitása után a KWin összeomlott
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: logonye...@gmail.com

Application: kwin_x11 (5.2.2)

Qt Version: 5.4.1
Operating System: Linux 3.19.0-21-generic i686
Distribution: Ubuntu 15.04

-- Information about the crash:
A Firefoxban egy PDF-re mutató linkre kattintottam, ami megnyílt az Adobe
Readerben, de az ablak nem reagált a kattintásokra. Aztán kaptam egy
hibaüzenetet arról, hogy a KWin összeomlott, és onnantól az ablak már reagált a
kattintásaimra.

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb1b33780 (LWP 1821))]

Thread 5 (Thread 0xaff32b40 (LWP 1828)):
#0  0xb7774be0 in __kernel_vsyscall ()
#1  0xb76623db in poll () at ../sysdeps/unix/syscall-template.S:81
#2  0xb493c120 in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb492d014 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb492d439 in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb04d12f5 in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
#6  0xb495440a in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#7  0xb4a711aa in start_thread (arg=0xaff32b40) at pthread_create.c:333
#8  0xb766cfde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122

Thread 4 (Thread 0xaf5ffb40 (LWP 1829)):
#0  0xb767a051 in __libc_enable_asynccancel () at ../nptl/cancellation.c:30
#1  0xb765c741 in read () at ../sysdeps/unix/syscall-template.S:81
#2  0xb4972515 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb492ca82 in g_main_context_check () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb492cfaa in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb492d156 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#6  0xb492d1b0 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#7  0xb495440a in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#8  0xb4a711aa in start_thread (arg=0xaf5ffb40) at pthread_create.c:333
#9  0xb766cfde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122

Thread 3 (Thread 0xae2a3b40 (LWP 1855)):
#0  0xb7774be0 in __kernel_vsyscall ()
#1  0xb76652d1 in select () at ../sysdeps/unix/syscall-template.S:81
#2  0xb635cf8e in qt_safe_select (nfds=25, fdread=0xa127800, fdwrite=0xa127a0c,
fdexcept=0xa127c18, orig_timeout=0x0) at kernel/qcore_unix.cpp:75
#3  0xb635e903 in select (timeout=, exceptfds=,
writefds=, readfds=, nfds=,
this=) at kernel/qeventdispatcher_unix.cpp:320
#4  QEventDispatcherUNIXPrivate::doSelect (this=0xa127720, flags=...,
timeout=0x0) at kernel/qeventdispatcher_unix.cpp:196
#5  0xb635eeb6 in QEventDispatcherUNIX::processEvents (this=0xa1195d0,
flags=...) at kernel/qeventdispatcher_unix.cpp:607
#6  0xb6302d93 in QEventLoop::processEvents (this=0xae2a3254, flags=...) at
kernel/qeventloop.cpp:128
#7  0xb63031fa in QEventLoop::exec (this=0xae2a3254, flags=...) at
kernel/qeventloop.cpp:204
#8  0xb60d540d in QThread::exec (this=0xa127528) at thread/qthread.cpp:503
#9  0xb4dca50f in ?? () from /usr/lib/i386-linux-gnu/libQt5Qml.so.5
#10 0xb60da7eb in QThreadPrivate::start (arg=0xa127528) at
thread/qthread_unix.cpp:337
#11 0xb4a711aa in start_thread (arg=0xae2a3b40) at pthread_create.c:333
#12 0xb766cfde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122

Thread 2 (Thread 0xab04ab40 (LWP 1866)):
#0  0xb7774be0 in __kernel_vsyscall ()
#1  0xb4a7625c in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187
#2  0xb7679cf6 in __pthread_cond_wait (cond=0xb59208f0, mutex=0xb59208d8) at
forward.c:149
#3  0xb57de784 in ?? () from /usr/lib/i386-linux-gnu/libQt5Script.so.5
#4  0xb57de7cc in ?? () from /usr/lib/i386-linux-gnu/libQt5Script.so.5
#5  0xb4a711aa in start_thread (arg=0xab04ab40) at pthread_create.c:333
#6  0xb766cfde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122

Thread 1 (Thread 0xb1b33780 (LWP 1821)):
[KCrash Handler]
#7  0x in ?? ()
#8  0xb7371eeb in KWin::Workspace::constrainedStackingOrder (this=0xa071330) at
../layers.cpp:506
#9  0xb7372912 in KWin::Workspace::updateStackingOrder
(this=this@entry=0xa071330, propagate_new_clients=) at
../layers.cpp:119
#10 0xb7372daf in updateStackingOrder (propagate_new_clients=,
this=0xa071330) at ../layers.cpp:612
#11 KWin::Workspace::blockStackingUpdates (this=0xa071330, block=false) at
../layers.cpp:613
#12 0xb7358c02 in ~StackingUpdatesBlocker (this=,
__in_chrg=) at ../workspace.h:606
#13 KWin::Client::destroyClient (this=0xa3b7f00) at 

[Touchpad-KCM] [Bug 359460] Synaptic touchpad wrong settings and limits

[Mykola Krachkovsky via KDE Bugzilla]

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

--- Comment #7 from Mykola Krachkovsky  ---
I'm able to change values, but Q[Double]SpinBox limits don't allow me to enter
standard touchpad value, like 106 for VertScrollDelta (allowed maximum for
Scrolling Distance Vertical is 10) and digits after numeric dot are lost. At
the same time Circular Scrolling Angle allows only integral values, so default
value 0.1 is impossible to be set.

I have no libinput driver for xorg.

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

[kig] [Bug 359805] strange loss of drawing precision when drawing circles

[Rex Dieter via KDE Bugzilla]

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

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@math.unl.edu

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

[telepathy] [Bug 354384] No visible way to add/configure link-local XMPP account

[Éric Brunet via KDE Bugzilla]

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

Éric Brunet  changed:

   What|Removed |Added

 CC||eric.bru...@lps.ens.fr

--- Comment #1 from Éric Brunet  ---
Yes, this is annoying. I just want to chat on the local network, but I cannot
make it work.

I managed to create an account from the command line with

mc-tool add salut/local-xmpp "Personnes à proximité" string:first-name="Éric"
string:last-name="Brunet"

and then

mc-tool enable salut/local_xmpp/account0

I did this on two computers on the same local network (both fedora 23 linux).
We could see each other on the contact list, but were unable to chat. When
clicking on the other contact, a chat window appears, I can type some text, but
it doesn't reach the other person.

A funny point is that the computer still manage to exchange a little bit of
information: when the chat window is opened, if the other contact changes its
status, it is reported back in the chat window.

So the question is: did I create correctly the Salut accounts ? Why is it not
working ?

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

[kalarm] [Bug 360134] New: Crash on wakeup, connecting to external monitor

[Pasi via KDE Bugzilla]

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

Bug ID: 360134
   Summary: Crash on wakeup, connecting to external monitor
   Product: kalarm
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: djar...@kde.org
  Reporter: kde.track.pasi...@xoxy.net

Application: kalarm (2.11.4-5ak)

Qt Version: 5.5.1
Operating System: Linux 4.4.3-1-default x86_64
Distribution: "openSUSE Tumbleweed (20160303) (x86_64)"

-- Information about the crash:
Was waking the laptop from sqleep, connected external monitor. May be the same
"no monitor crash" of Qt which has troubled KDE lately (and made me to switch
to Gnome after n years of KDE...). 

(OpenSUSE tumbleweed, running gnome, but does have KDE and Qt 5.5.1)

-- Backtrace:
Application: KAlarm (kalarm), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6b8397a940 (LWP 5198))]

Thread 4 (Thread 0x7f6b621db700 (LWP 5199)):
#0  0x7f6b7b00649d in poll () at /lib64/libc.so.6
#1  0x7f6b74f64432 in  () at /usr/lib64/libxcb.so.1
#2  0x7f6b74f66007 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f6b63f03e29 in QXcbEventReader::run() (this=0xacc790) at
qxcbconnection.cpp:1229
#4  0x7f6b7b90d94f in QThreadPrivate::start(void*) (arg=0xacc790) at
thread/qthread_unix.cpp:331
#5  0x7f6b751814a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f6b7b00eded in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f6b58254700 (LWP 5206)):
#0  0x7f6b7b00649d in poll () at /lib64/libc.so.6
#1  0x7f6b74840294 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f6b7484039c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f6b7bb3252b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f6b58c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f6b7badc61a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f6b58253c90, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#5  0x7f6b7b908b1c in QThread::exec() (this=) at
thread/qthread.cpp:503
#6  0x7f6b7b90d94f in QThreadPrivate::start(void*) (arg=0xd08c30) at
thread/qthread_unix.cpp:331
#7  0x7f6b751814a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7f6b7b00eded in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f6b4f568700 (LWP 5399)):
#0  0x7f6b74883554 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f6b7483f940 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f6b748401c3 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f6b7484039c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f6b7bb3252b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f6b480008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f6b7badc61a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f6b4f567c90, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7f6b7b908b1c in QThread::exec() (this=) at
thread/qthread.cpp:503
#7  0x7f6b7b90d94f in QThreadPrivate::start(void*) (arg=0xb394d0) at
thread/qthread_unix.cpp:331
#8  0x7f6b751814a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f6b7b00eded in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f6b8397a940 (LWP 5198)):
[KCrash Handler]
#6  0x7f6b7c6114b0 in QScreen::handle() const (this=0x0) at
kernel/qscreen.cpp:112
#7  0x7f6b63f22359 in QXcbBackingStore::resize(QSize const&, QRegion
const&) (this=0x10478a0, size=...) at qxcbbackingstore.cpp:440
#8  0x7f6b7cd98726 in QWidgetBackingStore::doSync()
(this=this@entry=0x1047950) at kernel/qwidgetbackingstore.cpp:1063
#9  0x7f6b7cd99d54 in QWidgetBackingStore::sync() (this=0x1047950) at
kernel/qwidgetbackingstore.cpp:1032
#10 0x7f6b7cdb6e1f in QWidgetPrivate::syncBackingStore() (this=0x10472e0)
at kernel/qwidget.cpp:1907
#11 0x7f6b7cde664d in QWidgetWindow::handleResizeEvent(QResizeEvent*)
(this=this@entry=0x10461f0, event=event@entry=0x7fff4bcd84e0) at
kernel/qwidgetwindow.cpp:710
#12 0x7f6b7cde93a3 in QWidgetWindow::event(QEvent*) (this=0x10461f0,
event=0x7fff4bcd84e0) at kernel/qwidgetwindow.cpp:232
#13 0x7f6b7cd8c8cc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=this@entry=0xab14e0, receiver=receiver@entry=0x10461f0,
e=e@entry=0x7fff4bcd84e0) at kernel/qapplication.cpp:3716
#14 0x7f6b7cd919d6 in QApplication::notify(QObject*, QEvent*)
(this=0xaabf80, receiver=0x10461f0, e=0x7fff4bcd84e0) at
kernel/qapplication.cpp:3499
#15 0x7f6b7badecd3 in QCoreApplication::notifyInternal(QObject*, QEvent*)
(this=0xaabf80, receiver=receiver@entry=0x10461f0,
event=event@entry=0x7fff4bcd84e0) at kernel/qcoreapplication.cpp:965
#16 0x7f6b7c5eaa01 in

[systemsettings] [Bug 360130] System Settings crashes after opening "Look of workspace"

[Piotr Mierzwinski via KDE Bugzilla]

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

Piotr Mierzwinski  changed:

   What|Removed |Added

Summary|System Settings crashing|System Settings crashes
   |after opening "Look of  |after opening "Look of
   |workspace"  |workspace"

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

[systemsettings] [Bug 360130] System Settings crashing after opening "Look of workspace"

[Piotr Mierzwinski via KDE Bugzilla]

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

Piotr Mierzwinski  changed:

   What|Removed |Added

 CC||piotr.mierzwin...@gmail.com
Summary|Crash after open System |System Settings crashing
   |Settings adn selectin "Look |after opening "Look of
   |of workspace"   |workspace"

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

[kdenlive] [Bug 360133] New: 15.13 git master: effect group initially shows disabled state but is enable.

[via KDE Bugzilla]

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

Bug ID: 360133
   Summary: 15.13 git master: effect group initially shows
disabled state but is enable.
   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 creating a group for an effect, then the effect group initially shows the
"stroked-eye" state, this is disabled state. However, the effects are all
enabled and effective. Only after toggling the group state, the effects are
properly synchronized with the group state.

However, a user would probably expect the effect group to be enabled when
created from an enabled effect; and otherwise disabled if the effect was
disabled.

Reproducible: Always

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

[systemsettings] [Bug 359945] Touchpad scroll delta is limited by max. 10

[Christian Trippe via KDE Bugzilla]

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

Christian Trippe  changed:

   What|Removed |Added

 CC||christiande...@web.de

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

[telepathy] [Bug 360128] Cannot import Kopete logs

[Martin Klapetek via KDE Bugzilla]

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

Martin Klapetek  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Klapetek  ---


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

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

[telepathy] [Bug 356320] Kopete history logs import not work.

[Martin Klapetek via KDE Bugzilla]

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

Martin Klapetek  changed:

   What|Removed |Added

 CC||ondrej.kuc...@centrum.cz

--- Comment #1 from Martin Klapetek  ---
*** Bug 360128 has been marked as a duplicate of this bug. ***

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

[telepathy] [Bug 360125] Messages not saved in the history when using OTR

[Martin Klapetek via KDE Bugzilla]

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

Martin Klapetek  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Klapetek  ---


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

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

[frameworks-kwallet] [Bug 360121] KDE wallet asking for password multiple times when going online

[Martin Klapetek via KDE Bugzilla]

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

Martin Klapetek  changed:

   What|Removed |Added

  Component|contactlist |general
   Assignee|kde-telepathy-b...@kde.org  |va...@kde.org
 CC||kdelibs-b...@kde.org,
   ||mklape...@kde.org
Product|telepathy   |frameworks-kwallet
   Target Milestone|Future  |---

--- Comment #3 from Martin Klapetek  ---
Thanks for the report, this actually looks like a problem with KWallet itself.

The "KDE Wallet Migration Agent" belongs to it and KTp cannot influence
if that shows up or not.

That said, I noticed this behavior as well recently.

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

[dolphin] [Bug 360132] Dolphin doesn't update the folder name for title and taskbar entries

[Sudhir Khanger via KDE Bugzilla]

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

--- Comment #1 from Sudhir Khanger  ---
Created attachment 97696
  --> https://bugs.kde.org/attachment.cgi?id=97696=edit
screenshot shows Git as folder name when current folder is Desktop

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

[dolphin] [Bug 360132] New: Dolphin doesn't update the folder name for title and taskbar entries

[Sudhir Khanger via KDE Bugzilla]

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

Bug ID: 360132
   Summary: Dolphin doesn't update the folder name for title and
taskbar entries
   Product: dolphin
   Version: 15.12.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: sud...@sudhirkhanger.com

Dolphin will sometime stick to one directory name. It will not change the name
unless it is restarted.

Reproducible: Always


Actual Results:  
Dolphin title entry doesn't change as you move across folder

Expected Results:  
Dolphin should show the name folder it is in as its title and taskbar entry

Please see the attached screenshot. I am in Desktop folder but it shows Git as
title and taskbar entry.

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

[kmymoney4] [Bug 360129] CSV Importer doesn't recognize sell operation

[NSLW via KDE Bugzilla]

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

--- Comment #2 from NSLW  ---
Created attachment 97695
  --> https://bugs.kde.org/attachment.cgi?id=97695=edit
Column Assignment

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

[kmymoney4] [Bug 360129] CSV Importer doesn't recognize sell operation

[NSLW via KDE Bugzilla]

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

--- Comment #1 from NSLW  ---
Created attachment 97694
  --> https://bugs.kde.org/attachment.cgi?id=97694=edit
CSV Test File

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

[k3b] [Bug 360131] New: writing total data volume written wrong displayed (CD-RW, 700 MB)

[Armin Mohring via KDE Bugzilla]

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

Bug ID: 360131
   Summary: writing total data volume written wrong displayed
(CD-RW, 700 MB)
   Product: k3b
   Version: 2.0.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Burning/Hardware
  Assignee: k...@kde.org
  Reporter: armin_mohr...@web.de
CC: mich...@jabster.pl, tr...@kde.org

If I use a CD-RW (700 MB max free space) and create a data project, then the
following error occurs.
If I write the data, the status bar (progress in x MB) stops before the full MB
size.

Reproducible: Always

Steps to Reproduce:
1. Start K3B
2. Create data project
3. USE CD-RW
4. Start writing
5. Watch status bar (progress of x of y total data volume written)

Actual Results:  
Status bar stops *before* status bar stop at full data volume. 

Expected Results:  
Status bar stops at full data volume.
I think it is a display error.

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

[systemsettings] [Bug 360130] New: Crash after open System Settings adn selectin "Look of workspace"

[Piotr Mierzwinski via KDE Bugzilla]

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

Bug ID: 360130
   Summary: Crash after open System Settings adn selectin "Look of
workspace"
   Product: systemsettings
   Version: 5.5.95
  Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: piotr.mierzwin...@gmail.com

Application: systemsettings5 (5.5.95)

Qt Version: 5.6.0
Frameworks Version: Unknown
Operating System: Linux 4.4.4-desktop-1.mga6 x86_64
Distribution: "Mageia 6"

-- Information about the crash:
- What I was doing when the application crashed:
I've opened System Settings, selected "Look of workspace" and after ~2 sec. it
crashed.

-- Backtrace:
Application: Ustawienia systemowe (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb96587e800 (LWP 21579))]

Thread 4 (Thread 0x7fb954336700 (LWP 21580)):
#0  0x7fb961f4ff5d in poll () at /lib64/libc.so.6
#1  0x7fb95ff03ac2 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7fb95ff05697 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7fb956866809 in QXcbEventReader::run() (this=0xb103c0) at
qxcbconnection.cpp:1313
#4  0x7fb962641649 in QThreadPrivate::start(void*) (arg=0xb103c0) at
thread/qthread_unix.cpp:340
#5  0x7fb95f69065d in start_thread () at /lib64/libpthread.so.0
#6  0x7fb961f5bdad in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fb94bfff700 (LWP 21581)):
#0  0x7fb95f1b3a64 in g_mutex_unlock () at /lib64/libglib-2.0.so.0
#1  0x7fb95f170409 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7fb95f17051c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7fb962856a4b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fb9440008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#4  0x7fb96280234a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fb94bffeda0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#5  0x7fb96263ca3c in QThread::exec() (this=this@entry=0x7fb965a2dd40
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:503
#6  0x7fb9659bd3e5 in QDBusConnectionManager::run() (this=0x7fb965a2dd40
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:181
#7  0x7fb962641649 in QThreadPrivate::start(void*) (arg=0x7fb965a2dd40
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:340
#8  0x7fb95f69065d in start_thread () at /lib64/libpthread.so.0
#9  0x7fb961f5bdad in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fb942e7a700 (LWP 21586)):
#0  0x7fb95f1b3a64 in g_mutex_unlock () at /lib64/libglib-2.0.so.0
#1  0x7fb95f16fa30 in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#2  0x7fb95f170343 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#3  0x7fb95f17051c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#4  0x7fb962856a4b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fb93c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#5  0x7fb96280234a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fb942e79db0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7fb96263ca3c in QThread::exec() (this=) at
thread/qthread.cpp:503
#7  0x7fb960fda835 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#8  0x7fb962641649 in QThreadPrivate::start(void*) (arg=0xf3b5e0) at
thread/qthread_unix.cpp:340
#9  0x7fb95f69065d in start_thread () at /lib64/libpthread.so.0
#10 0x7fb961f5bdad in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fb96587e800 (LWP 21579)):
[KCrash Handler]
#6  0x7fb941dd9eb2 in QQuickStyleItem::updatePaintNode(QSGNode*,
QQuickItem::UpdatePaintNodeData*) (this=) at
/usr/lib64/qt5/include/QtQuick/5.6.0/QtQuick/private/qquickitem_p.h:877
#7  0x7fb941dd9eb2 in QQuickStyleItem::updatePaintNode(QSGNode*,
QQuickItem::UpdatePaintNodeData*) (this=0x10a2050, node=0x0) at
Private/qquickstyleitem.cpp:1830
#8  0x7fb96129f460 in QQuickWindowPrivate::updateDirtyNode(QQuickItem*) ()
at /lib64/libQt5Quick.so.5
#9  0x7fb96129fc50 in QQuickWindowPrivate::updateDirtyNodes() () at
/lib64/libQt5Quick.so.5
#10 0x7fb9612a0bee in QQuickWindowPrivate::syncSceneGraph() () at
/lib64/libQt5Quick.so.5
#11 0x7fb961270e56 in QSGGuiThreadRenderLoop::renderWindow(QQuickWindow*)
() at /lib64/libQt5Quick.so.5
#12 0x7fb961272420 in
QSGGuiThreadRenderLoop::exposureChanged(QQuickWindow*) () at
/lib64/libQt5Quick.so.5
#13 0x7fb963746c5b in QWindow::event(QEvent*) (this=0x102f0a0,
ev=) at kernel/qwindow.cpp:2096
#14 0x7fb9612a9c65 in QQuickWindow::event(QEvent*) () at
/lib64/libQt5Quick.so.5
#15 0x7fb963d5440c in 

[kmymoney4] [Bug 360129] New: CSV Importer doesn't recognize sell operation

[NSLW via KDE Bugzilla]

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

Bug ID: 360129
   Summary: CSV Importer doesn't recognize sell operation
   Product: kmymoney4
   Version: 4.7.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: csvimporter
  Assignee: kmymoney-de...@kde.org
  Reporter: lukasz.wojnilow...@gmail.com

CSV Importer doesn't recognize sell operation during import. It recognizes Buy
operation though.

Reproducible: Always

Steps to Reproduce:
1. Create your investing bank account,
2. File->Import->CSV... 
3. choose Investing, give name to new CSV Importer template
4. Press Choose File  and point my "test file.csv" (see attachment)
5. Field Separator: comma ; Text separator double quotes  and go next,
6. assign columns accordingly (see attachment) and go next
7. at rows range just go next, 
8. window appears to accept new securities so press just ok.
9. set Decimal Separator: comma
10. press Import CSV

Actual Results:  
CSV Importer doesn't recognize my sell operation and asks what kind of
operation is this.

Expected Results:  
Recognize sell operation.

1) My locale is pl_PL
2) Buy operations are recognized, but only if their name is "Kupno" (Polish
word for buy) and not "Buy"
3) Sell operations aren't recognized no matter if the name is  "Sprzedaż"
(Polish word for sell), "Sell" or "sell"
4) My CSV file is UTF-8

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

[trojita] [Bug 360020] color inconsistencies combining defaults with program colors

[Jan Kundrát via KDE Bugzilla]

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

--- Comment #25 from Jan Kundrát  ---
Git commit 4557439352a85ac9ff9abbaf52cdb0e23fb9d156 by Jan Kundrát.
Committed on 05/03/2016 at 16:17.
Pushed by gerrit into branch 'master'.

Use Qt5's features for QLineEdit actions

Our LineEdit started as a class offering a clear button at the right
edge even on styles where this is not available. A feature like this
however got added to Qt in version 5.2, so it makes sense to start using
it instead.

This change makes it possible to deprecate the QSS usage, and therefore
fixes the style issues on (some) dark themes or dynamic palette changes.

The Qt's features do not work on QToolButton level, but on a QAction
level. This means that we have to open the QMenu manually.

The copyright info change reflects the fact that the history code was
contributed by Thomas in 2013. I'm leaving Glad in that file because he
still started doing this button UI thingy.

Change-Id: I818da0646a0fe6ed6c346c81e70ac6d2ffa0c9fd

M  +32   -69   src/Gui/LineEdit.cpp
M  +0-6src/Gui/LineEdit.h
M  +8-18   src/Gui/MessageListWidget.cpp
M  +1-1src/Gui/MessageListWidget.h

http://commits.kde.org/trojita/4557439352a85ac9ff9abbaf52cdb0e23fb9d156

--- Comment #26 from Jan Kundrát  ---
Git commit db916b2a18990cb487195462ff6ab991f20ad6b5 by Jan Kundrát.
Committed on 05/03/2016 at 16:17.
Pushed by gerrit into branch 'master'.

MessageView: Specify color roles without a QPalette detour

By specifying just the desired color roles instead of going through the
QPalette and doing that thing with colors, it seems that dynamic scheme
changes are now supported.

Change-Id: I0ab8fc0935fa91f67056cca5ecfee56424ce7e62

M  +4-4src/Gui/MessageView.cpp

http://commits.kde.org/trojita/db916b2a18990cb487195462ff6ab991f20ad6b5

--- Comment #27 from Jan Kundrát  ---
Git commit 0107f850027ee5c190b710dff68c6767b271be55 by Jan Kundrát.
Committed on 05/03/2016 at 16:17.
Pushed by gerrit into branch 'master'.

Rely on systemwide palette for QWebView

This works well enough on this particular machine (a random snapshot of
Qt 5.6), so I'm optimistic that it might even work just fine all the way
back to Qt 5.2.

Change-Id: I894701c56f9e42118b516f9262ccab86f2136908

M  +0-9src/Gui/EmbeddedWebView.cpp

http://commits.kde.org/trojita/0107f850027ee5c190b710dff68c6767b271be55

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

[trojita] [Bug 360020] color inconsistencies combining defaults with program colors

[Jan Kundrát via KDE Bugzilla]

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

--- Comment #25 from Jan Kundrát  ---
Git commit 4557439352a85ac9ff9abbaf52cdb0e23fb9d156 by Jan Kundrát.
Committed on 05/03/2016 at 16:17.
Pushed by gerrit into branch 'master'.

Use Qt5's features for QLineEdit actions

Our LineEdit started as a class offering a clear button at the right
edge even on styles where this is not available. A feature like this
however got added to Qt in version 5.2, so it makes sense to start using
it instead.

This change makes it possible to deprecate the QSS usage, and therefore
fixes the style issues on (some) dark themes or dynamic palette changes.

The Qt's features do not work on QToolButton level, but on a QAction
level. This means that we have to open the QMenu manually.

The copyright info change reflects the fact that the history code was
contributed by Thomas in 2013. I'm leaving Glad in that file because he
still started doing this button UI thingy.

Change-Id: I818da0646a0fe6ed6c346c81e70ac6d2ffa0c9fd

M  +32   -69   src/Gui/LineEdit.cpp
M  +0-6src/Gui/LineEdit.h
M  +8-18   src/Gui/MessageListWidget.cpp
M  +1-1src/Gui/MessageListWidget.h

http://commits.kde.org/trojita/4557439352a85ac9ff9abbaf52cdb0e23fb9d156

--- Comment #26 from Jan Kundrát  ---
Git commit db916b2a18990cb487195462ff6ab991f20ad6b5 by Jan Kundrát.
Committed on 05/03/2016 at 16:17.
Pushed by gerrit into branch 'master'.

MessageView: Specify color roles without a QPalette detour

By specifying just the desired color roles instead of going through the
QPalette and doing that thing with colors, it seems that dynamic scheme
changes are now supported.

Change-Id: I0ab8fc0935fa91f67056cca5ecfee56424ce7e62

M  +4-4src/Gui/MessageView.cpp

http://commits.kde.org/trojita/db916b2a18990cb487195462ff6ab991f20ad6b5

--- Comment #27 from Jan Kundrát  ---
Git commit 0107f850027ee5c190b710dff68c6767b271be55 by Jan Kundrát.
Committed on 05/03/2016 at 16:17.
Pushed by gerrit into branch 'master'.

Rely on systemwide palette for QWebView

This works well enough on this particular machine (a random snapshot of
Qt 5.6), so I'm optimistic that it might even work just fine all the way
back to Qt 5.2.

Change-Id: I894701c56f9e42118b516f9262ccab86f2136908

M  +0-9src/Gui/EmbeddedWebView.cpp

http://commits.kde.org/trojita/0107f850027ee5c190b710dff68c6767b271be55

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

[trojita] [Bug 360020] color inconsistencies combining defaults with program colors

[Jan Kundrát via KDE Bugzilla]

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

--- Comment #25 from Jan Kundrát  ---
Git commit 4557439352a85ac9ff9abbaf52cdb0e23fb9d156 by Jan Kundrát.
Committed on 05/03/2016 at 16:17.
Pushed by gerrit into branch 'master'.

Use Qt5's features for QLineEdit actions

Our LineEdit started as a class offering a clear button at the right
edge even on styles where this is not available. A feature like this
however got added to Qt in version 5.2, so it makes sense to start using
it instead.

This change makes it possible to deprecate the QSS usage, and therefore
fixes the style issues on (some) dark themes or dynamic palette changes.

The Qt's features do not work on QToolButton level, but on a QAction
level. This means that we have to open the QMenu manually.

The copyright info change reflects the fact that the history code was
contributed by Thomas in 2013. I'm leaving Glad in that file because he
still started doing this button UI thingy.

Change-Id: I818da0646a0fe6ed6c346c81e70ac6d2ffa0c9fd

M  +32   -69   src/Gui/LineEdit.cpp
M  +0-6src/Gui/LineEdit.h
M  +8-18   src/Gui/MessageListWidget.cpp
M  +1-1src/Gui/MessageListWidget.h

http://commits.kde.org/trojita/4557439352a85ac9ff9abbaf52cdb0e23fb9d156

--- Comment #26 from Jan Kundrát  ---
Git commit db916b2a18990cb487195462ff6ab991f20ad6b5 by Jan Kundrát.
Committed on 05/03/2016 at 16:17.
Pushed by gerrit into branch 'master'.

MessageView: Specify color roles without a QPalette detour

By specifying just the desired color roles instead of going through the
QPalette and doing that thing with colors, it seems that dynamic scheme
changes are now supported.

Change-Id: I0ab8fc0935fa91f67056cca5ecfee56424ce7e62

M  +4-4src/Gui/MessageView.cpp

http://commits.kde.org/trojita/db916b2a18990cb487195462ff6ab991f20ad6b5

--- Comment #27 from Jan Kundrát  ---
Git commit 0107f850027ee5c190b710dff68c6767b271be55 by Jan Kundrát.
Committed on 05/03/2016 at 16:17.
Pushed by gerrit into branch 'master'.

Rely on systemwide palette for QWebView

This works well enough on this particular machine (a random snapshot of
Qt 5.6), so I'm optimistic that it might even work just fine all the way
back to Qt 5.2.

Change-Id: I894701c56f9e42118b516f9262ccab86f2136908

M  +0-9src/Gui/EmbeddedWebView.cpp

http://commits.kde.org/trojita/0107f850027ee5c190b710dff68c6767b271be55

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

[telepathy] [Bug 360128] New: Cannot import Kopete logs

[Ondřej Kučera via KDE Bugzilla]

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

Bug ID: 360128
   Summary: Cannot import Kopete logs
   Product: telepathy
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: log-viewer
  Assignee: kde-telepathy-b...@kde.org
  Reporter: ondrej.kuc...@centrum.cz

When selecting "Logs -> Import Kopete Logs" from the menu, I only get an
information window saying "No Kopete logs found."
The logs are where they should be, as far as I know, that is in
~/.kde4/share/apps/kopete/logs/JabberProtocol.
It might be a good idea to provide a way for the user to manually select the
directory where to look for the Kopete history when the automatic detection
fails.

Reproducible: Always

Steps to Reproduce:
1. Have Kopete history in ~/.kde4/share/apps/kopete/logs/JabberProtocol.
2. Select "Logs -> Import Kopete Logs" from the Log Viewer menu.


Actual Results:  
The Kopete history isn't found.

Expected Results:  
The Kopete history is imported.

Version 15.12.2

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

[Touchpad-KCM] [Bug 359460] Synaptic touchpad wrong settings and limits

[Rajeesh K V via KDE Bugzilla]

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

--- Comment #6 from Rajeesh K V  ---
(In reply to Mykola Krachkovsky from comment #0)

> Actual Results:  
> UI units (mm) are just written to touchpad settings. Default touchpad values
> coudn't be set using UI. 

Are you unable to set the scrolling distance parameters in UI? Do you also have
libinput driver (xorg-x11-drv-libinput or equivalent) installed?

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

[telepathy] [Bug 360126] New: Account not selected when using "Previous Conversations"

[Ondřej Kučera via KDE Bugzilla]

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

Bug ID: 360126
   Summary: Account not selected when using "Previous
Conversations"
   Product: telepathy
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: log-viewer
  Assignee: kde-telepathy-b...@kde.org
  Reporter: ondrej.kuc...@centrum.cz

Selecting "Conversation -> Previous Conversations" from the chat window menu
merely opens the KDE IM Log Viewer application. I then have to manually look
for the person with whom I'm having the conversation.

Reproducible: Always

Steps to Reproduce:
1. Start a conversation with someone.
2. Select "Conversation -> Previous Conversations" from the chat window menu.


Actual Results:  
KDE IM Log Viewer application is opened without any contextual information.

Expected Results:  
The item corresponding to the conversation in the chat window is selected, so
that I immediately see the history I'm looking for.

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

[telepathy] [Bug 360125] New: Messages not saved in the history when using OTR

[Ondřej Kučera via KDE Bugzilla]

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

Bug ID: 360125
   Summary: Messages not saved in the history when using OTR
   Product: telepathy
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: OTR
  Assignee: kde-telepathy-b...@kde.org
  Reporter: ondrej.kuc...@centrum.cz
CC: ziem...@gmail.com

When using OTR for chatting with a contact, no messages are saved to the
history. I suppose this is done deliberately and I can even see the reasoning.
Still it would be nice to have an option in the settings that I know what I'm
doing and that I indeed do want to save even messages from an OTR session. (I
trust my ability to protect the data on my hard drive generally much more than
I trust the people I'm chatting with to do the same. If they use a different
client which saves even OTR sessions, it's more likely the data are unsafe on
their computer than on mine.)

Reproducible: Always

Steps to Reproduce:
1. Start an OTR session to chat with somebody.
2. Check the history to see there are no messages from the session.


Actual Results:  
Messages are not saved in the history.

Expected Results:  
Messages are saved in the history (at least optionally).

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

[konsole] [Bug 360124] New: konsole does not scale to the window when used within `sandbox -X`

[Jacek Wielemborek via KDE Bugzilla]

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

Bug ID: 360124
   Summary: konsole does not scale to the window when used within
`sandbox -X`
   Product: konsole
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: d33...@gmail.com

sandbox is a way to keep GUI applications from interfering with each other.

Reproducible: Always

Steps to Reproduce:
1. install Konsole 15.12.1 under Fedora 23, as well as policycoreutils-sandbox
and selinux-policy-sandbox
2. run sandbox -X konsole

Actual Results:  
konsole window doesn't take all space

Expected Results:  
should take all space

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

[kmymoney4] [Bug 303026] This transaction has a missing assignment of XXX 0.01

[NSLW via KDE Bugzilla]

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

NSLW  changed:

   What|Removed |Added

 CC||lukasz.wojnilow...@gmail.co
   ||m

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

[telepathy] [Bug 360123] New: Cannot deny a contact request from a spam account

[Ondřej Kučera via KDE Bugzilla]

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

Bug ID: 360123
   Summary: Cannot deny a contact request from a spam account
   Product: telepathy
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kde-telepathy-b...@kde.org
  Reporter: ondrej.kuc...@centrum.cz

A few months ago, I was contacted by an obviously spam account
(doofy7...@swissjabber.org). When I deny the request, not only that the contact
list application crashes, the request isn't really denied (even though the icon
disappears from System Tray). When going offline and back online again, I once
again receive the request.

Reproducible: Always

Steps to Reproduce:
1. Receive a contact request from a new contact.
2. Right-click on the icon in the System Tray.
3. Click on "Request from " and then in the sub-menu on "Deny".

Actual Results:  
1. The icon in the System Tray disappears.
2. I am notified that I denied the request.
3. The contact list application crashes:
Mar 05 09:35:24 lexie systemd-coredump[1719]: Process 1566 (ktp-contactlist) of
user 1000 dumped core.
4. The request isn't really denied. Upon next connection, the request appears
again.

Expected Results:  
1. The request is denied.
2. The contact list application doesn't crash.

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

[dolphin] [Bug 356235] Dolphin unable to change file associations

[Rog131 via KDE Bugzilla]

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

Rog131  changed:

   What|Removed |Added

 CC||samrog...@hotmail.com

--- Comment #7 from Rog131  ---
Same as  Bug 354179 - File associations cannot be changed if already defined in
$XDG_CONFIG_HOME/mimeapps.list  - https://bugs.kde.org/show_bug.cgi?id=354179

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

[telepathy] [Bug 360122] New: Password for a jabber account is never remembered

[Ondřej Kučera via KDE Bugzilla]

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

Bug ID: 360122
   Summary: Password for a jabber account is never remembered
   Product: telepathy
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: contactlist
  Assignee: kde-telepathy-b...@kde.org
  Reporter: ondrej.kuc...@centrum.cz

I have two jabber accounts. For one of them, the password is remembered (via
KDE wallet). For the other one, I'm asked for the password every time Telepathy
tries to connect. Checking "Save password" has no effect. This is especially
annoying when on a less reliable connection where it can mean I'm asked for the
password several times an hour.

Reproducible: Always

Steps to Reproduce:
1. Go online
2. Enter the password and check "Save password".


Actual Results:  
The password is never saved (for this account).

Expected Results:  
The password is saved and I'm not asked for it in the future.

Version: 15.12.2

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

[systemsettings] [Bug 346614] audio levels reset when testing

[Bart Vaes via KDE Bugzilla]

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

Bart Vaes  changed:

   What|Removed |Added

 CC||vaesb...@telenet.be

--- Comment #4 from Bart Vaes  ---
Almost a year later and today I noticed this behaviour is still present...the
very hard (loud) way !

If there's a way to set the audio level with setVolume(..) maybe you can first
check what the current level is with getVolume(..) ? And if it's below 50% or
so crank it up ?

At least set it back to whatever value it was when the test is over - if you
really must set it to 100% to begin with.

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