[plasmashell] [Bug 361097] impossible rename file with long filename in desktop (with folder view)

[painless roaster via KDE Bugzilla]

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

--- Comment #7 from painless roaster  ---
Try next patch in attachment, please.
This patch resolve issues:
 - dynamic resize of height (only if need add height)
 - initial size

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

[plasmashell] [Bug 361097] impossible rename file with long filename in desktop (with folder view)

[painless roaster via KDE Bugzilla]

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

--- Comment #6 from painless roaster  ---
Created attachment 99044
  --> https://bugs.kde.org/attachment.cgi?id=99044=edit
FolderView rename patch - version 2

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

[kmymoney4] [Bug 363197] New: Crash on change of Brokerage account from type:Checking to type:Cash

[via KDE Bugzilla]

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

Bug ID: 363197
   Summary: Crash on change of Brokerage account from
type:Checking to type:Cash
   Product: kmymoney4
   Version: 4.7.2
  Platform: MacPorts Packages
OS: OS X
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: nicholas.maggipi...@gmail.com

Application: kmymoney (4.7.2)
KDE Platform Version: 4.14.3
Qt Version: 4.8.7
Operating System: Darwin 15.4.0 x86_64
Distribution (Platform): MacPorts Packages

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

Trying to change the "Brokerage" portion of an Investment account to type CASH
instead of CHECKING.

-- Backtrace:
Application: KMyMoney (kmymoney), signal: Segmentation fault: 11
(lldb) process attach --pid 82676
Process 82676 stopped
* thread #1: tid = 0x1fea93, 0x7fff8fc27582 libsystem_kernel.dylib`__wait4
+ 10, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP
frame #0: 0x7fff8fc27582 libsystem_kernel.dylib`__wait4 + 10
libsystem_kernel.dylib`__wait4:
->  0x7fff8fc27582 <+10>: jae0x7fff8fc2758c; <+20>
0x7fff8fc27584 <+12>: movq   %rax, %rdi
0x7fff8fc27587 <+15>: jmp0x7fff8fc217f2; cerror
0x7fff8fc2758c <+20>: retq   

Executable module set to
"/Applications/MacPorts/KDE4/kmymoney.app/Contents/MacOS/kmymoney".
Architecture set to: x86_64h-apple-macosx.
(lldb) set set term-width 200
(lldb) thread info
thread #1: tid = 0x1fea93, 0x7fff8fc27582 libsystem_kernel.dylib`__wait4 +
10, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP

(lldb) bt all
* thread #1: tid = 0x1fea93, 0x7fff8fc27582 libsystem_kernel.dylib`__wait4
+ 10, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP
  * frame #0: 0x7fff8fc27582 libsystem_kernel.dylib`__wait4 + 10
frame #1: 0x00010ae6c7fe libkdeui.5.dylib`KCrash::startProcess(int,
char const**, bool) + 286
frame #2: 0x00010ae6b99b
libkdeui.5.dylib`KCrash::defaultCrashHandler(int) + 1179
frame #3: 0x7fff8fcf452a libsystem_platform.dylib`_sigtramp + 26
frame #4: 0x00010b80f145
QtGui`QSortFilterProxyModel::parent(QModelIndex const&) const + 85
frame #5: 0x00010b7bcbb5 QtGui`QTreeView::indexRowSizeHint(QModelIndex
const&) const + 133
frame #6: 0x00010b7bd02b QtGui`QTreeViewPrivate::itemHeight(int) const
+ 107
frame #7: 0x00010b7bd1de QtGui`QTreeViewPrivate::updateScrollBars() +
206
frame #8: 0x00010b7c99cd QtGui`QTreeView::updateGeometries() + 477
frame #9: 0x00010b2f7670 QtGui`QWidget::event(QEvent*) + 1248
frame #10: 0x00010b66c81d QtGui`QFrame::event(QEvent*) + 221
frame #11: 0x00010b6f4733
QtGui`QAbstractScrollArea::viewportEvent(QEvent*) + 115
frame #12: 0x00010b77d989
QtGui`QAbstractItemView::viewportEvent(QEvent*) + 1593
frame #13: 0x00010b7bfaf1 QtGui`QTreeView::viewportEvent(QEvent*) + 225
frame #14: 0x00010b6f4f35
QtGui`QAbstractScrollAreaFilter::eventFilter(QObject*, QEvent*) + 37
frame #15: 0x00010c2f1f3c
QtCore`QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*,
QEvent*) + 124
frame #16: 0x00010b2a2cab
QtGui`QApplicationPrivate::notify_helper(QObject*, QEvent*) + 235
frame #17: 0x00010b2a5a4b QtGui`QApplication::notify(QObject*, QEvent*)
+ 6651
frame #18: 0x00010c2f1c36
QtCore`QCoreApplication::notifyInternal(QObject*, QEvent*) + 118
frame #19: 0x00010b2f2166
QtGui`QWidgetPrivate::sendPendingMoveAndResizeEvents(bool, bool) + 342
frame #20: 0x00010b2f61ea QtGui`QWidgetPrivate::show_helper() + 42
frame #21: 0x00010b2f6ec1 QtGui`QWidget::setVisible(bool) + 977
frame #22: 0x00010b2f65bf QtGui`QWidgetPrivate::showChildren(bool) +
319
frame #23: 0x00010b2f620a QtGui`QWidgetPrivate::show_helper() + 74
frame #24: 0x00010b2f6ec1 QtGui`QWidget::setVisible(bool) + 977
frame #25: 0x00010b2f65bf QtGui`QWidgetPrivate::showChildren(bool) +
319
frame #26: 0x00010b2f620a QtGui`QWidgetPrivate::show_helper() + 74
frame #27: 0x00010b2f6ec1 QtGui`QWidget::setVisible(bool) + 977
frame #28: 0x00010b2dd9fd QtGui`QStackedLayout::setCurrentIndex(int) +
349
frame #29: 0x00010b6d7f2e QtGui`QTabWidgetPrivate::_q_showTab(int) + 78
frame #30: 0x00010c30a817 QtCore`QMetaObject::activate(QObject*,
QMetaObject const*, int, void**) + 2471
frame #31: 0x00010b6d0b63 QtGui`QTabBar::setCurrentIndex(int) + 387
frame #32: 0x00010b6d46b1
QtGui`QTabBar::mouseReleaseEvent(QMouseEvent*) + 545
frame #33: 0x00010aeffba1
libkdeui.5.dylib`KTabBar::mouseReleaseEvent(QMouseEvent*) + 353
frame #34: 0x00010b2f7460 QtGui`QWidget::event(QEvent*) + 720
frame #35: 0x00010b6d2527 

[ksysguard] [Bug 261255] some dead processes stay in the list

[Mathieu Jobin via KDE Bugzilla]

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

Mathieu Jobin  changed:

   What|Removed |Added

 CC||opensou...@somekool.net

--- Comment #27 from Mathieu Jobin  ---
this is still valid as of ksysguard 5.6.4-1
running arch linux packages

closing and reopening ksysguard clears the list

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

[frameworks-kinit] [Bug 358593] kdeinit5 create /tmp/xauth-xxx-_y with inappropriate permission.

[Rex Dieter via KDE Bugzilla]

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

Rex Dieter  changed:

   What|Removed |Added

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

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

[kwin] [Bug 363196] New: kwin crashes at least once as soon as I do anything with the desktop

[Peter Nehem via KDE Bugzilla]

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

Bug ID: 363196
   Summary: kwin crashes at least once as soon as I do anything
with the desktop
   Product: kwin
   Version: 5.6.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: pne...@gmx.com

Application: kwin_x11 (5.6.4)

Qt Version: 5.6.0
Frameworks Version: 5.22.0
Operating System: Linux 4.5.4-1-ck x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:
I was bringing up the browser, or clicking on an icon, it really doesn;t matter
what I do, just moving the cursor on the desk top will cause kwin to crash. 
 I downloaded all the qt debugging files and just recompiled kwin and loaded it
through pacman, reboot and here is the error.

- Unusual behavior I noticed: Almost aways the same error or in same place if
that is the right term to use. Usually I just restart the application and it
will run fine for the session or it may crash again and in htop i'll notice
entries that read /usr/bin/kwin_x11 ---crashes 1

--Other Notes:
I've only just recomplied kwin, please let me know if I need to recomplied and
other modules.

THanks

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1aa8d30840 (LWP 810))]

Thread 6 (Thread 0x7f1a8c59f700 (LWP 824)):
#0  0x7f1aa855368d in poll () from /usr/lib/libc.so.6
#1  0x7f1aa600eae2 in ?? () from /usr/lib/libxcb.so.1
#2  0x7f1aa6010757 in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7f1a8d474a79 in QXcbEventReader::run (this=0xf7e070) at
qxcbconnection.cpp:1313
#4  0x7f1aa62d21d8 in QThreadPrivate::start (arg=0xf7e070) at
thread/qthread_unix.cpp:340
#5  0x7f1aa881d474 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7f1aa855c69d in clone () from /usr/lib/libc.so.6

Thread 5 (Thread 0x7f1a81b40700 (LWP 832)):
#0  0x7f1aa8555353 in select () from /usr/lib/libc.so.6
#1  0x7f1aa64f9fef in qt_safe_select (nfds=8,
fdread=fdread@entry=0x7f1a7c000a98, fdwrite=fdwrite@entry=0x7f1a7c000d28,
fdexcept=fdexcept@entry=0x7f1a7c000fb8, orig_timeout=orig_timeout@entry=0x0) at
kernel/qcore_unix.cpp:75
#2  0x7f1aa64fb9dc in QEventDispatcherUNIX::select (timeout=0x0,
exceptfds=0x7f1a7c000fb8, writefds=0x7f1a7c000d28, readfds=0x7f1a7c000a98,
nfds=, this=0x7f1a7c0008e0) at
kernel/qeventdispatcher_unix.cpp:320
#3  QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f1a7c000900,
flags=..., flags@entry=..., timeout=timeout@entry=0x0) at
kernel/qeventdispatcher_unix.cpp:196
#4  0x7f1aa64fbeca in QEventDispatcherUNIX::processEvents
(this=0x7f1a7c0008e0, flags=...) at kernel/qeventdispatcher_unix.cpp:607
#5  0x7f1aa64a646a in QEventLoop::exec (this=this@entry=0x7f1a81b3fd50,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f1aa62cd2f3 in QThread::exec (this=this@entry=0x7f1a9f70cd20
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:503
#7  0x7f1a9f499a65 in QDBusConnectionManager::run (this=0x7f1a9f70cd20
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:181
#8  0x7f1aa62d21d8 in QThreadPrivate::start (arg=0x7f1a9f70cd20 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:340
#9  0x7f1aa881d474 in start_thread () from /usr/lib/libpthread.so.0
#10 0x7f1aa855c69d in clone () from /usr/lib/libc.so.6

Thread 4 (Thread 0x7f1a7b7fe700 (LWP 836)):
#0  0x7f1aa8555353 in select () from /usr/lib/libc.so.6
#1  0x7f1aa64f9fef in qt_safe_select (nfds=13,
fdread=fdread@entry=0x7f1a6c000a98, fdwrite=fdwrite@entry=0x7f1a6c000d28,
fdexcept=fdexcept@entry=0x7f1a6c000fb8, orig_timeout=orig_timeout@entry=0x0) at
kernel/qcore_unix.cpp:75
#2  0x7f1aa64fb9dc in QEventDispatcherUNIX::select (timeout=0x0,
exceptfds=0x7f1a6c000fb8, writefds=0x7f1a6c000d28, readfds=0x7f1a6c000a98,
nfds=, this=0x7f1a6c0008e0) at
kernel/qeventdispatcher_unix.cpp:320
#3  QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f1a6c000900,
flags=..., flags@entry=..., timeout=timeout@entry=0x0) at
kernel/qeventdispatcher_unix.cpp:196
#4  0x7f1aa64fbeca in QEventDispatcherUNIX::processEvents
(this=0x7f1a6c0008e0, flags=...) at kernel/qeventdispatcher_unix.cpp:607
#5  0x7f1aa64a646a in QEventLoop::exec (this=this@entry=0x7f1a7b7fdd60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f1aa62cd2f3 in QThread::exec (this=this@entry=0x108cf70) at
thread/qthread.cpp:503
#7  0x7f1aa0530915 in QQmlThreadPrivate::run (this=0x108cf70) at

[krunner] [Bug 363195] New: Error reported when attempting to open a mail message from krunner

[Robert via KDE Bugzilla]

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

Bug ID: 363195
   Summary: Error reported when attempting to open a mail message
from krunner
   Product: krunner
   Version: 4.11.9
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: m...@vhanda.in
  Reporter: sam...@yahoo.com

When I hit enter to open a mail message in Krunner I the message doesn't open
and I get a dialog box telling me to file a bug report about it. The precise
error message is:

"Internal Error Please send a full bug report at http://bugs.kde.org Unable to
fetch item from backend (collection -1) : Unable to retrieve item from
resource: Cannot fetch item in offline mode."
Not sure why it says it's in offline mode, I'm connected to the Internet while
I'm doing this.

Three additional errors appear in the notifier in the system tray:
"Examining Finished" "akonadi://?item=10610"
"AOL Mail (Samnis)" "AOL mail (Samnis): Cannot fetch item in offline mode."
"/var/tmp/kdecache-logomachist/krun/5622_0_"

There was a fourth notifier error message that appeared the first few times I
reproduced this, but I didn't catch what it was and now I'm only seeing three
errors. 

Reproducible: Always

Steps to Reproduce:
1. Press Alt + F2 to get the krunner box.
2. Type something that brings up an email on the dropdown menu.
3. Hit enter to open the email.

Actual Results:  
After the error messages appeared? Nothing.

Expected Results:  
I believe it was supposed to open the email in Kmail.

I'm running Linux 3.14.16-gentoo.

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

[kdenlive] [Bug 363194] KDenLive Crashes When Deleting Effect or Transition

[via KDE Bugzilla]

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

bryanwors...@hotmail.com changed:

   What|Removed |Added

   Platform|unspecified |Ubuntu Packages

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

[kdenlive] [Bug 363194] KDenLive Crashes When Deleting Effect or Transition

[via KDE Bugzilla]

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

bryanwors...@hotmail.com changed:

   What|Removed |Added

Product|kde |kdenlive
  Component|general |Effects & Transitions

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

[kde] [Bug 363194] New: KDenLive Crashes When Deleting Effect or Transition

[via KDE Bugzilla]

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

Bug ID: 363194
   Summary: KDenLive Crashes When Deleting Effect or Transition
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: bryanwors...@hotmail.com

Application: kdenlive (16.07.70)

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

-- Information about the crash:
KDenLive crashes when attempting to delete an applied Effect or Transition.
Happens everytime and with all Effects.

The crash can be reproduced every time.

-- Backtrace:
Application: Kdenlive (kdenlive), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f07371158c0 (LWP 1999))]

Thread 21 (Thread 0x7f0723423700 (LWP 2000)):
#0  0x7f0730786e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f072b36dc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f072b36f8d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f0725de5629 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f073119984e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f072f0936fa in start_thread (arg=0x7f0723423700) at
pthread_create.c:333
#6  0x7f0730792b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 20 (Thread 0x7f06ff21b700 (LWP 2001)):
#0  0x7f0730786e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f070628b64c in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
#2  0x7f072f0936fa in start_thread (arg=0x7f06ff21b700) at
pthread_create.c:333
#3  0x7f0730792b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 19 (Thread 0x7f06fb5ed700 (LWP 2002)):
#0  0x7f0730786e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f072d65631c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f072d65642c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f07313d0a9b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f0731377dea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f07311948a4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f0731f4d3c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f073119984e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f072f0936fa in start_thread (arg=0x7f06fb5ed700) at
pthread_create.c:333
#9  0x7f0730792b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 18 (Thread 0x7f06f9c43700 (LWP 2004)):
#0  0x7f0730786e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f072d65631c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f072d65642c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f07313d0a9b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f0731377dea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f07311948a4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f0731f4d3c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f073119984e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f072f0936fa in start_thread (arg=0x7f06f9c43700) at
pthread_create.c:333
#9  0x7f0730792b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 17 (Thread 0x7f06b7fff700 (LWP 2016)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f073119aaeb in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f073578a92e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#3  0x7f073578b1b3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7f073119984e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f072f0936fa in start_thread (arg=0x7f06b7fff700) at
pthread_create.c:333
#6  0x7f0730792b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 16 (Thread 0x7f06b77fe700 (LWP 2017)):
#0  0x7f0730786e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f072d65631c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f072d65642c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f07313d0a9b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f0731377dea in

[kleopatra] [Bug 363148] Deselecting Signing check box in Advanced Settings - Certificate Usage results in General Error in Kleopatra

[Stefan via KDE Bugzilla]

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

Stefan  changed:

   What|Removed |Added

 CC||luke1...@gmx.de

--- Comment #1 from Stefan  ---
Could confirm the issue here --- Win 10, Kleopatra 2.2.0.

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

[kleopatra] [Bug 363193] New: Decryption failed when trying to import S/MIME certificate backed-up from Firefox

[Stefan via KDE Bugzilla]

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

Bug ID: 363193
   Summary: Decryption failed when trying to import S/MIME
certificate backed-up from Firefox
   Product: kleopatra
   Version: 2.2.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: aheine...@intevation.de
  Reporter: luke1...@gmx.de
CC: kdepim-b...@kde.org, m...@kde.org

When trying to import an S/MIME certificate backed-up from Firefox using a long
passphrase, importing the p12 file in Kleopatra fails with the error:
Decryption failed.

This is bad in two ways:
a) it should just work (using long passphrases is advertised)
b) the error message doesn't point to the actual problem at all - the user
might not at all get the idea that a too long passphrase is the problem

The issue might be related to https://bugs.kde.org/show_bug.cgi?id=362640 but
I'm not too sure, especially since this is an entire different use-case and
error message.

Reproducible: Always

Steps to Reproduce:
1. Get an S/MIME certificate in Firefox (normal case, when creating a
certificate via the webbrowser - for instance via CAcert).
2. In Firefox: Tools -> Options -> Advanced -> View Certificates
3. Select your certificate -> Backup...
4. Enter a filename where to store the p12-file
5. Enter the master password, if required
6. Use the following password to encrypt the p12-file:
0f9guf9dhgsadi90sdg0ßfd0hdgj0df
7. In Kleopatra: File -> Import certificate...
8. Select the p12-file saved earlier
9. Enter the password: 0f9guf9dhgsadi90sdg0ßfd0hdgj0df
10. Enter a random passphrase to protect the imported object - for instance
test1234 and confirm it once more

Actual Results:  
Error shows up:
Title: Certificate Import Failed - Kleopatra
An error occurred while trying to import the certificate [filename].p12:
Decryption failed

Expected Results:  
Import of certificate succeeds.

The error doesn't occur, when using a shorter password to create the backup of
the certificate from Firefox.

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

[kmymoney4] [Bug 351874] QIF import of investment buys and sells mishandles commissions

[Jeff via KDE Bugzilla]

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

--- Comment #13 from Jeff  ---
>  With your suggested change, to remove the sign reversal, when the 
> transaction imports, the result shows as a deposit of $8.77 (positive).  

In order for that 8.77 to properly become a payment instead of a deposit, I
have to restore the statement reader to its 6/28/2015 version as well as remove
the negative sign on the line in the QIF reader (and to make it all work, place
a negative sign on the "buy" case in the QIF importer). It then imports with a
warning triangle, but simply hitting "Edit" followed by the "Enter" fixes the
math and the warning goes away.  To remove the warning and have the whole thing
work would probably take some different change to the statement reader that I
have not pursued. (I'm guessing the 6/28/2015 statement reader has some
extraneous .abs() when it sets up the split and the transaction editor does
not, which is why the editor fixes it.)  

As I recall from my quick look, the current master branch version of the
statement reader makes assumptions about buys and sells and basically ignores
the signs on the incoming data. So you could change all the signs in the QIF
importer and the ledger results would not change.

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

[kdenlive] [Bug 362997] Audio Spectrum Widget causes Segmentation Fault

[Jacob Kauffmann via KDE Bugzilla]

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

Jacob Kauffmann  changed:

   What|Removed |Added

 Resolution|FIXED   |WORKSFORME

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

[kdenlive] [Bug 362997] Audio Spectrum Widget causes Segmentation Fault

[Jacob Kauffmann via KDE Bugzilla]

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

Jacob Kauffmann  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |FIXED

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

[kdenlive] [Bug 362997] Audio Spectrum Widget causes Segmentation Fault

[Jacob Kauffmann via KDE Bugzilla]

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

Jacob Kauffmann  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Jacob Kauffmann  ---
Today when I sat down to use my computer, the regular Kdenlive opened up
normally again, and I can once again use the Audio Spectrum widget. I did NOT
update before it started working again, although I have updated since and it is
still working. Hopefully the backtrace proves that I'm not crazy, but it seems
that this issue has magically resolved itself. I would still be happy to help
in any way I can if more info on this issue is ever needed.

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

[i18n] [Bug 363181] Time formats on en_IE

[Albert Astals Cid via KDE Bugzilla]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |UPSTREAM

--- Comment #3 from Albert Astals Cid  ---
I don't know if it's a bug or not, but in case it is, it comes from Qt so you
should open a bug there.

I've created a sample program that the only thing it does is ask QTime to print
13:30 and the output is

tsdgeos@xps:~/test$ LANG=en_GB ./test
"13:30"
tsdgeos@xps:~/test$ LANG=en_IE ./test
"1:30 P.M."

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

[phonon-backend-vlc] [Bug 363192] New: Amarok & VLC both seek track when starting playing. Sometimes seek to the end of the file and moves on to the next one

[Abderrahman Najjar via KDE Bugzilla]

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

Bug ID: 363192
   Summary: Amarok & VLC both seek track when starting playing.
Sometimes seek to the end of the file and moves on to
the next one
   Product: phonon-backend-vlc
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: sit...@kde.org
  Reporter: abderrahman.naj...@gmail.com
CC: bcooks...@kde.org, f...@kde.org, j...@videolan.org,
myr...@kde.org

Alright, firstly I don't know the source of this bug. I filed it under Amarok,
but the dev there told me it's not related to Amarok

I suspect that the underlying libvlc used in the backend is the root cause

If VLC is running with a file in play (paused or resuming), then Amarok will
behave wrongly. Amarok will skip tracks in the playlist (actually it's seeking
to the end of the file, then the player moves on to the next song which then
again it finds itself at the end of the file which means it has to move to the
next one and so on), till it reaches a random track on that playlist that it'll
play fully.

In VLC meanwhile, sometimes the next played file will seek randomly to a point
in the video (but not to the end. Most of the time it skips the first 2 minutes
or so).

This behavior in Amarok stops when I press "Stop" in VLC. It doesn't matter if
Amarok was running first, or was started during VLC's playback (or if Amarok
had a file loaded 'paused' or not).

I've changed Amarok back to the GStreamer backend (but in System Settings it's
still set to prefer VLC). The problem still persists.

I've captured Amarok's debug output, not sure if it's much of a help:
https://paste.kde.org/pza1te60q

Please point me to the right direction if this isn't a Phonon bug

pacman -Qs phonon 
local/phonon-qt4 4.9.0-1
local/phonon-qt4-gstreamer 4.9.0-1
local/phonon-qt4-vlc 0.9.0-1
local/phonon-qt5 4.9.0-1
local/phonon-qt5-gstreamer 4.9.0-1
local/phonon-qt5-vlc 0.9.0-1

local/vlc 2.2.3-2
local/amarok 2.8.0-9



Reproducible: Always

Steps to Reproduce:
1. Open a video file in VLC
2. Try playing a song in Amarok
3. Amarok will keep skipping tracks

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

[ksmserver] [Bug 343518] Plasma doesn't restore everything after a reboot

[Piotr Mierzwinski via KDE Bugzilla]

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

--- Comment #50 from Piotr Mierzwinski  ---
(In reply to Wolfgang Bauer from comment #48)
> (In reply to Piotr Mierzwinski from comment #47)
> > None of the tested by me applications are not restored after
> > relogin/restart.
> 
> Where's the problem then?
Problem is that applications mentioned in next sentence are not restored after
relogin. 

> I suppose there is a typo in there... ;-)
Sorry for typo. English grammar is not my strength, se better would be when
"are" has been replaced with "were" or usage: "there are not restored".

> > I tested: Firefox, Thunderbird and new Opera. I think all
> > of them are based on GTK2. 
> 
> Actually not.
> At least Firefox can be build against GTK3 since a while and I think at
> least some distributions do that (openSUSE not, yet).
OK. About Firefox you are right. I retested it again and I can say that in
Antergos Firefox is built using GTK3.

> So this might just be your point of regression...
The regression is that none of GTK2 and GTK3 applications there are not
restored. This is regression comparing to previous Plasma, because In ver.
5.5.x it was working. I tested  Kubuntu 16.04. BTW in Plasma 5 provided by this
distribution applications based on KF are not restored. I'm not going to evolve
this topic. Anyway they plan update to Plasma 5.6.x.

> No idea about the others though.
But I'm sure that the last two were built using GTK2. My test was following. I
changed "Style of GNOME application" in "System Settings" and just restarted
all tested applications.

> > All tested by me KF applications (konsole,
> > kwrite, dolphin) are restored correctly (including virtual desktop number).
> 
> This proves IMHO that your problem is unrelated to *this* bug report, or the
> other one I marked this as duplicate of, which is about a problem in Qt5 as
> explained.
Subject is "Plasma doesn't restore everything after a reboot". So maybe is too
general. Author reported this bug wrote about problem with Konsole, Dolphin,
Kate and restoring them including their opened tabs. After several posts
someone started typing about most general problems with restoring other
applications. Never mind.
So maybe my problem is only partially related to reported problem.

> > In Plasma 5.5.4 (ksmserver probably has the same version) Firefox and
> > Thunderbird were restored correctly.
> 
> There has been no change to ksmserver (except see above), so another prove
> that this is not the same bug.
So where is placed the bug? In Plasma 5.5.4 GTK applications are restored
correctly and in 5.6.4 don't.
>From my perspective it looks like some informations necessary to restore GTK
based applications are not saved into ksmserverrc. Even after hardcoded them in
this file, they exist only till first relogin/restart. After that they
disappear. How it might be explained?

> > Looking what you are saying: 'I have heard of other users having problems
> > with Firefox in this regard since upgrading Plasma to 5.6 (or the beta).". I
> > also other persons also saying about problems, so maybe this is plasma 5.6.x
> > (ksmserver) bug.
> 
> As mentioned, ksmserver hasn't been changed between 5.5 and 5.6.
> Except for this:
> https://quickgit.kde.org/?p=plasma-workspace.
> git=commit=5f0ca1305db4a925dbdbf927f541497be334feff
So I'm asking again. What happened? Developers of couple distributions made
some mistake?
In the past I tested also KaOS with Plasma 5.4.x and later after update to
Plasma 5.6.x. Testing the newest KaOS I observe the same issue like in
Antergos. KaOS doesn't base on Arch packages instead of Antergos.
I wonder what will bring Plasma 5.6.4 (currently tested) in Kubuntu 16.04. I
mean of course issue of restoring GTK and KF5 applications.

> According to the commit message it shouldn't be a problem though...
For me it is hard to say if XSM technology could affect on restoring GTK
applications. I don't know what testes made author this fix after applying it
in code.
I mean simple test: whether GTK and KF applications are restored or not.
I and others can say only that it stopped work.

> If you are able to build plasma/ksmserver from source, I would recommend to
> do so with this patch reverted and see if it works then.
This is the easiest way to prove/not prove that author of this patch didn't
retest your fix properly.
Yes. I'm able to build plasma-workspace package, what contains ksmserver. Maybe
I will make such test in the future.

> > And if for you and for Paolo Carlini it is working then to who should to
> > report the bug?
> 
> Good question, I don't know really.
> Maybe GTK3, or the applications affected.
As I mentioned issue is related to GTK2 (new Opera, thunderbird) and GTK3
(Firefox).

> Or, as it might be a ksmserver bug after all (I never ruled that out), file
> a *new* bug report here.
Some time ago (May 4th) I just reported it here in bug: 362671 (no answer).
I reported it also in Antergos forum (with no 

[plasmashell] [Bug 361074] Memory leak with normal CPU usage, every hour or so

[Jagadguru via KDE Bugzilla]

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

--- Comment #5 from Jagadguru  ---
I am having the same problem with Plasma 5.5.5 see attachment above.

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

[plasmashell] [Bug 361074] Memory leak with normal CPU usage, every hour or so

[Jagadguru via KDE Bugzilla]

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

Jagadguru  changed:

   What|Removed |Added

 CC||jguru...@gmail.com

--- Comment #4 from Jagadguru  ---
Created attachment 99041
  --> https://bugs.kde.org/attachment.cgi?id=99041=edit
plasma shell memory leak

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

[frameworks-kinit] [Bug 358593] kdeinit5 create /tmp/xauth-xxx-_y with inappropriate permission.

[Albert Astals Cid via KDE Bugzilla]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/kini
   ||t/dece8fd89979cd1a86c03bcac
   ||eef6e9221e8d8cd
 Resolution|--- |FIXED

--- Comment #3 from Albert Astals Cid  ---
Git commit dece8fd89979cd1a86c03bcaceef6e9221e8d8cd by Albert Astals Cid, on
behalf of taro yamada.
Committed on 17/05/2016 at 22:08.
Pushed by aacid into branch 'master'.

Fix permissions of /tmp/xauth-xxx-_y

M  +1-0src/kdeinit/kinit.cpp

http://commits.kde.org/kinit/dece8fd89979cd1a86c03bcaceef6e9221e8d8cd

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

[kmymoney4] [Bug 351874] QIF import of investment buys and sells mishandles commissions

[allan via KDE Bugzilla]

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

--- Comment #12 from allan  ---
(In reply to Jeff from comment #9)
> That line:
> 
> tr.m_amount = -amount;
> 
> is the one I changed in my patch to fix my problem for "sells".  Need remove
> the negative sign.

Sorry, but I'm a bit puzzled here.  With your suggested change, to remove the
sign reversal, when the transaction imports, the result shows as a deposit of
$8.77 (positive).  Throughout the import, the negative sign is maintained, as
far as I can see.  So, I don't see "The cash account should decrease by 8.77." 
Why don't I see the result you are expecting?

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

[i18n] [Bug 363181] Time formats on en_IE

[via KDE Bugzilla]

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

--- Comment #2 from gbonner...@gmail.com ---
Sorry, everywhere that uses the KDE configuration from Formats, in System
Settings. So Plasma, Dolphin etc.

It's not a bug per se, in that the time displays as the locale configuration
tells it to (and is consistent with the preview in Formats). It's just that the
default locale configuration for Formats is incorrect.

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

[kde] [Bug 363140] World-readable X11 Cookie, easy key logger

[Pier Luigi Fiorini via KDE Bugzilla]

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

--- Comment #10 from Pier Luigi Fiorini  ---
sddm should set the XAUTHORITY env var, you might consider changing kdeinit to
use that instead

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

[Breeze] [Bug 360304] Missing animations cions

[andreas via KDE Bugzilla]

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

--- Comment #7 from andreas  ---
as konqueror is not really maintained I will remove the only for konqueror
needed file so you get the "old" k geared icon back.

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

[kde] [Bug 363140] World-readable X11 Cookie, easy key logger

[Albert Astals Cid via KDE Bugzilla]

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

Albert Astals Cid  changed:

   What|Removed |Added

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

--- Comment #9 from Albert Astals Cid  ---
Right i read the code of sddm too quickly and thought it was using a QFile to
create the .XAuthority file.

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

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

[frameworks-kinit] [Bug 358593] kdeinit5 create /tmp/xauth-xxx-_y with inappropriate permission.

[Albert Astals Cid via KDE Bugzilla]

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

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

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

[krita] [Bug 359642] [UC-LOGIC] Tablet Pressure sensitivity not working

[AndeOn via KDE Bugzilla]

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

--- Comment #9 from AndeOn  ---
Hi, Dmitry!

It works now!  The Proof in video below :)

https://youtu.be/mq2vFfSGIms

Thank you for create the support to UC-Logic tablets.

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

[i18n] [Bug 363181] Time formats on en_IE

[Albert Astals Cid via KDE Bugzilla]

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

Albert Astals Cid  changed:

   What|Removed |Added

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

--- Comment #1 from Albert Astals Cid  ---
"Time displays as 1:30pm" 

Where?

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

[kdenlive] [Bug 358703] git 16.04: cannot reorder track & bin clip effects in effects stack

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #2 from Jean-Baptiste Mardelle  ---
Git commit 24173546d73294b3bd88f8fd4551ef7ce23970d1 by Jean-Baptiste Mardelle.
Committed on 17/05/2016 at 21:28.
Pushed by mardelle into branch 'master'.

Allow reordering of bin clip effects

M  +30   -0src/bin/bin.cpp
M  +2-0src/bin/bin.h
M  +23   -0src/bin/bincommands.cpp
M  +13   -0src/bin/bincommands.h
M  +2-2src/effectstack/effectstackview2.cpp
M  +2-0src/effectstack/effectstackview2.h
M  +1-1src/mainwindow.cpp
M  +27   -0src/mltcontroller/clipcontroller.cpp
M  +6-0src/mltcontroller/clipcontroller.h

http://commits.kde.org/kdenlive/24173546d73294b3bd88f8fd4551ef7ce23970d1

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

[kde] [Bug 363140] World-readable X11 Cookie, easy key logger

[Pier Luigi Fiorini via KDE Bugzilla]

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

--- Comment #8 from Pier Luigi Fiorini  ---
sddm creates ~/.Xauthority with xauth, but you are talking of another file
here.
this indeed might be a duplicate of 358593 as it sounds a lot like the file
referenced there.

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

[kmenuedit] [Bug 345100] The menu editor doesn't properly save new icons for submenus

[idmazay via KDE Bugzilla]

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

idmazay  changed:

   What|Removed |Added

 CC|d-ma...@yandex.ru   |

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

[Breeze] [Bug 359863] Icons "krusader_user" and "krusader_root" look too similar.

[andreas via KDE Bugzilla]

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

--- Comment #3 from andreas  ---
Created attachment 99038
  --> https://bugs.kde.org/attachment.cgi?id=99038=edit
krusader_user

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

[kde] [Bug 363140] World-readable X11 Cookie, easy key logger

[Albert Astals Cid via KDE Bugzilla]

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

Albert Astals Cid  changed:

   What|Removed |Added

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

--- Comment #7 from Albert Astals Cid  ---
That bug is only for the tmp file for not for  .Xauthority ?

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

[dolphin] [Bug 363191] New: Dolphin s'est planté à la suite d'une copie de documents sur une clé.

[via KDE Bugzilla]

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

Bug ID: 363191
   Summary: Dolphin s'est planté à la suite d'une copie de
documents sur une clé.
   Product: dolphin
   Version: 15.12.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: wi...@tutanota.com

Application: dolphin (15.12.3)

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

-- Information about the crash:
- What I was doing when the application crashed:
I was copying files on an USB Key.

- Unusual behavior I noticed:
The App crashs and closes the window

- Custom settings of the application:

The crash can be reproduced sometimes.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7a10dae900 (LWP 2237))]

Thread 3 (Thread 0x7f7a0e06c700 (LWP 2238)):
#0  0x7f7a25019e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f7a196cac62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f7a196cc8d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f7a109f0629 in QXcbEventReader::run (this=0x1094270) at
qxcbconnection.cpp:1253
#4  0x7f7a1fbeb84e in QThreadPrivate::start (arg=0x1094270) at
thread/qthread_unix.cpp:331
#5  0x7f7a1c3996fa in start_thread (arg=0x7f7a0e06c700) at
pthread_create.c:333
#6  0x7f7a25025b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f79ff59e700 (LWP 2241)):
#0  0x7f7a1b80d853 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f7a1b80e24b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f7a1b80e42c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f7a1fe22a9b in QEventDispatcherGlib::processEvents
(this=0x7f79f80008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f7a1fdc9dea in QEventLoop::exec (this=this@entry=0x7f79ff59dcc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f7a1fbe68a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7f7a1fbeb84e in QThreadPrivate::start (arg=0x11f5b70) at
thread/qthread_unix.cpp:331
#7  0x7f7a1c3996fa in start_thread (arg=0x7f79ff59e700) at
pthread_create.c:333
#8  0x7f7a25025b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f7a10dae900 (LWP 2237)):
[KCrash Handler]
#6  0x7f7a2452b064 in KNotification::flags (this=this@entry=0x181d130) at
../../src/knotification.cpp:233
#7  0x7f7a24548ee7 in NotifyByAudio::onAudioFinished (this=0x1925300) at
../../src/notifybyaudio.cpp:140
#8  0x7f7a2454f5b5 in NotifyByAudio::qt_static_metacall
(_o=_o@entry=0x1925300, _c=_c@entry=QMetaObject::InvokeMetaMethod,
_id=_id@entry=0, _a=_a@entry=0x7ffe8ba69660) at moc_notifybyaudio.cpp:83
#9  0x7f7a1fdfafca in QMetaObject::activate (sender=0x1c46fd0,
signalOffset=, local_signal_index=,
argv=) at kernel/qobject.cpp:3713
#10 0x7f7a20e3e6ad in ?? () from
/usr/lib/x86_64-linux-gnu/libphonon4qt5.so.4
#11 0x7f7a1fdfbea1 in QObject::event (this=0x1c46fd0, e=) at
kernel/qobject.cpp:1239
#12 0x7f7a208cf05c in QApplicationPrivate::notify_helper
(this=this@entry=0x1067170, receiver=receiver@entry=0x1c46fd0,
e=e@entry=0x195d860) at kernel/qapplication.cpp:3716
#13 0x7f7a208d4516 in QApplication::notify (this=0x7ffe8ba69d40,
receiver=0x1c46fd0, e=0x195d860) at kernel/qapplication.cpp:3499
#14 0x7f7a1fdcc62b in QCoreApplication::notifyInternal
(this=0x7ffe8ba69d40, receiver=0x1c46fd0, event=event@entry=0x195d860) at
kernel/qcoreapplication.cpp:965
#15 0x7f7a1fdcea26 in QCoreApplication::sendEvent (event=0x195d860,
receiver=) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:224
#16 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
event_type=event_type@entry=0, data=0x1065600) at
kernel/qcoreapplication.cpp:1593
#17 0x7f7a1fdcef08 in QCoreApplication::sendPostedEvents
(receiver=receiver@entry=0x0, event_type=event_type@entry=0) at
kernel/qcoreapplication.cpp:1451
#18 0x7f7a1fe22673 in postEventSourceDispatch (s=0x113fa50) at
kernel/qeventdispatcher_glib.cpp:271
#19 0x7f7a1b80e127 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x7f7a1b80e380 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7f7a1b80e42c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7f7a1fe22a7f in QEventDispatcherGlib::processEvents (this=0x113f930,
flags=...) at kernel/qeventdispatcher_glib.cpp:418
#23 0x7f7a1fdc9dea in QEventLoop::exec 

[kstars] [Bug 363190] New: bad date format in observer planner

[christian via KDE Bugzilla]

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

Bug ID: 363190
   Summary: bad date format in observer planner
   Product: kstars
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: alpha...@free.fr

The month of the date shown in the observation planner, at right to location is
incorrect. 

Reproducible: Always

Steps to Reproduce:
1.open observation planner window
2.
3.

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

[kmenuedit] [Bug 345100] The menu editor doesn't properly save new icons for submenus

[via KDE Bugzilla]

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

andrew.walke...@ntlworld.com changed:

   What|Removed |Added

 CC||andrew.walke...@ntlworld.co
   ||m

--- Comment #8 from andrew.walke...@ntlworld.com ---
Having this problem in Kubuntu 16.04

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

[krita] [Bug 359642] [UC-LOGIC] Tablet Pressure sensitivity not working

[Dmitry Kazakov via KDE Bugzilla]

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

--- Comment #8 from Dmitry Kazakov  ---
Hi, AndeOn!

Could you please check this build? Now your tablet should be recognized:

http://files.kde.org/krita/3/linux/krita-3.0-RC-1-master-6f75b0f-x86_64.appimage

If not, please attach the new output of the command in comment 4.

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

[plasma-nm] [Bug 363188] Wrong WWAN icon after connection loss

[via KDE Bugzilla]

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

johan.claudebreunin...@gmail.com changed:

   What|Removed |Added

 CC||johan.claudebreuninger@gmai
   ||l.com

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

[kmymoney4] [Bug 351874] QIF import of investment buys and sells mishandles commissions

[Jeff via KDE Bugzilla]

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

--- Comment #11 from Jeff  ---
> I wonder how you test if OFX imports are correct? Is your test based only on 
> fact that KMM doesn't show you warning signs in ledger?

This wasn't addressed to me, but I will chime in. I know OFX imports work
because I have 2 investment accounts that I trade in quite frequently (daily to
weekly), 2 more that I trade in fairly often (monthly), and 4 more that get
updates every few months. I know the imports are working because my stock and
cash balances in KMM match the balances at the brokers.

> Summarizing it: It didn't work for you in general case and corner case. Now 
> it works for you in general case but still not in corner case :)

I believe that is correct. But I didn't do extensive testing before I backed
your change out of my copy.

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

[plasma-nm] [Bug 363188] Wrong WWAN icon after connection loss

[via KDE Bugzilla]

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

--- Comment #1 from johan.claudebreunin...@gmail.com ---
Created attachment 99037
  --> https://bugs.kde.org/attachment.cgi?id=99037=edit
Connected to the WWAN but icon showing "network available"

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

[plasma-nm] [Bug 363188] New: Wrong WWAN icon after connection loss

[via KDE Bugzilla]

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

Bug ID: 363188
   Summary: Wrong WWAN icon after connection loss
   Product: plasma-nm
   Version: 5.6.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: applet
  Assignee: jgrul...@redhat.com
  Reporter: johan.claudebreunin...@gmail.com
CC: lu...@kde.org

When the WWAN modem connection is briefly disconnected, the icon in the network
manager applet changes to the blue "network available" icon (sometimes the blue
WiFi icon appears, sometimes the blue WWAN icon) and won't switch back to the
black icon showing link quality and informations when the connection is
established again.

Reproducible: Always

Steps to Reproduce:
1. Plug in WWAN modem
2. Lose the connection
3. Wrong icon after the connection is back

Actual Results:  
Same problem

Expected Results:  
The network manager applet should show signal quality and network type as it is
doing with WiFi.

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

[gwenview] [Bug 357548] Gwenview crashes when I activate 100% zoom by either middle click or toolbar button

[via KDE Bugzilla]

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

sir7emp...@gmail.com changed:

   What|Removed |Added

 CC||sir7emp...@gmail.com

--- Comment #10 from sir7emp...@gmail.com ---
Having the same crash and it seems I'm not the only one with the amount of
duplicates being marked. Here's the system info:

root@localhost:~> uname -a
Linux Polaris 4.5.3-1-default #1 SMP PREEMPT Thu May 5 05:03:39 UTC 2016
(d29747f) x86_64 x86_64 x86_64 GNU/Linux

root@localhost:~> lsb_release -a
LSB Version:   
core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x86_64:core-3.2-x86_64:core-4.0-x86_64:desktop-4.0-amd64:desktop-4.0-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch
Distributor ID: openSUSE
Description:openSUSE Tumbleweed (20160422) (x86_64)
Release:20160422
Codename:   Tumbleweed

Qt version: 5.5.1
Gwenview version: 15.12.3

Backtrace:

Application: Gwenview (gwenview), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6a0c689980 (LWP 4597))]

Thread 2 (Thread 0x7f69f52b8700 (LWP 4598)):
#0  0x7f6a070f707d in poll () from /lib64/libc.so.6
#1  0x7f69ff1813f2 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f69ff182fc7 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f69f6fe1dd9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f6a077ea91f in QThreadPrivate::start (arg=0x251bdb0) at
thread/qthread_unix.cpp:331
#5  0x7f6a015e1424 in start_thread () from /lib64/libpthread.so.0
#6  0x7f6a070ffadd in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f6a0c689980 (LWP 4597)):
[KCrash Handler]
#6  Unroll3BytesSkip1SwapSwapFirst (info=0x2af0f50, wIn=0x7ffdab24ff40,
accum=0x30e7000 ,
Stride=1529275) at cmspack.c:296
#7  0x7f6a05f7311b in PrecalculatedXFORM (p=0x2af0f50, in=,
out=, Size=1529275, Stride=1529275) at cmsxform.c:319
#8  0x7f6a0bda7658 in Gwenview::RasterImageView::updateFromScaler
(this=0x2b4c910, zoomedImageLeft=-237, zoomedImageTop=-39, image=...) at
/usr/src/debug/gwenview-15.12.3/lib/documentview/rasterimageview.cpp:322
#9  0x7f6a079e8cc7 in QtPrivate::QSlotObjectBase::call (a=0x7ffdab250180,
r=0x2b4c910, this=) at
../../src/corelib/kernel/qobject_impl.h:124
#10 QMetaObject::activate (sender=sender@entry=0x2728620,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7ffdab250180) at kernel/qobject.cpp:3698
#11 0x7f6a079e9637 in QMetaObject::activate (sender=sender@entry=0x2728620,
m=m@entry=0x7f6a0c04b7e0 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffdab250180)
at kernel/qobject.cpp:3578
#12 0x7f6a0be07231 in Gwenview::ImageScaler::scaledRect
(this=this@entry=0x2728620, _t1=-237, _t2=-39, _t3=...) at
/usr/src/debug/gwenview-15.12.3/build/lib/moc_imagescaler.cpp:135
#13 0x7f6a0bdc7304 in Gwenview::ImageScaler::scaleRect
(this=this@entry=0x2728620, rect=...) at
/usr/src/debug/gwenview-15.12.3/lib/imagescaler.cpp:132
#14 0x7f6a0bdc7a4f in Gwenview::ImageScaler::doScale (this=0x2728620) at
/usr/src/debug/gwenview-15.12.3/lib/imagescaler.cpp:122
#15 0x7f6a0bdc7b05 in Gwenview::ImageScaler::setDestinationRegion
(this=, region=...) at
/usr/src/debug/gwenview-15.12.3/lib/imagescaler.cpp:102
#16 0x7f6a0bda6274 in
Gwenview::RasterImageViewPrivate::setScalerRegionToVisibleRect (this=0x2b5b140)
at /usr/src/debug/gwenview-15.12.3/lib/documentview/rasterimageview.cpp:151
#17 Gwenview::RasterImageView::updateBuffer (this=this@entry=0x2b4c910,
region=...) at
/usr/src/debug/gwenview-15.12.3/lib/documentview/rasterimageview.cpp:443
#18 0x7f6a0be0963b in Gwenview::RasterImageView::qt_static_metacall
(_o=_o@entry=0x2b4c910, _c=_c@entry=QMetaObject::InvokeMetaMethod,
_id=_id@entry=7, _a=_a@entry=0x7ffdab250450) at
/usr/src/debug/gwenview-15.12.3/build/lib/moc_rasterimageview.cpp:109
#19 0x7f6a079e8e3a in QMetaObject::activate (sender=sender@entry=0x2f40870,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x0) at kernel/qobject.cpp:3713
#20 0x7f6a079e9637 in QMetaObject::activate (sender=sender@entry=0x2f40870,
m=m@entry=0x7f6a07dff8c0 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at
kernel/qobject.cpp:3578
#21 0x7f6a07a64420 in QTimer::timeout (this=this@entry=0x2f40870) at
.moc/moc_qtimer.cpp:197
#22 0x7f6a079f4f98 in QTimer::timerEvent (this=0x2f40870, e=) at kernel/qtimer.cpp:247
#23 0x7f6a079e9bdb in QObject::event (this=0x2f40870, e=) at
kernel/qobject.cpp:1261
#24 0x7f6a0906887c in QApplicationPrivate::notify_helper
(this=this@entry=0x2501b70, receiver=receiver@entry=0x2f40870,
e=e@entry=0x7ffdab2507c0) at kernel/qapplication.cpp:3716
#25 0x7f6a0906d986 in QApplication::notify (this=0x7ffdab250ae0,

[kwin] [Bug 362955] (Auto)Suspending compositing sometimes results in stale non-composited picture

[Soukyuu via KDE Bugzilla]

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

--- Comment #4 from Soukyuu  ---
Created attachment 99036
  --> https://bugs.kde.org/attachment.cgi?id=99036=edit
Support information while the issue is present

Not sure if this one is useful

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

[kwin] [Bug 362955] (Auto)Suspending compositing sometimes results in stale non-composited picture

[Soukyuu via KDE Bugzilla]

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

--- Comment #3 from Soukyuu  ---
Ok, it just happened again. Once it's triggered, any action suspending
compositing triggers it again. Once I noticed it, I tried to start mpv with -vo
x11, and it also makes the issue re-appear. Restarting kwin using kwin_x11
--replace does fix it.

I guess the initial trigger is what is bugging it up - this time it was mpv -vo
opengl-hq again.

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

[frameworks-plasma] [Bug 355410] the scroll speed of QML scroll area is too slow with Libinput

[via KDE Bugzilla]

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

prettyvani...@posteo.at changed:

   What|Removed |Added

 CC||prettyvani...@posteo.at

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

[kipiplugins] [Bug 363162] dngconverter crashes when converting any RAW file

[Maik Qualmann via KDE Bugzilla]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #3 from Maik Qualmann  ---
Copy the icon in your home directory. See here:

https://bugs.kde.org/show_bug.cgi?id=354364#c29

Maik

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

[partitionmanager] [Bug 363050] Respect minCapacity when creating new filesystems in small unformatted partitions

[Andrius Štikonas via KDE Bugzilla]

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

Andrius Štikonas  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/part
   ||itionmanager/65d80dd405ad40
   ||fc029a05080baaf1bda4d74611
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Andrius Štikonas  ---
Git commit 65d80dd405ad40fc029a05080baaf1bda4d74611 by Andrius Štikonas.
Committed on 17/05/2016 at 18:33.
Pushed by stikonas into branch 'master'.

Respect minCapacity when creating new filesystem in small unallocated partition

M  +1-0src/gui/sizedialogbase.cpp

http://commits.kde.org/partitionmanager/65d80dd405ad40fc029a05080baaf1bda4d74611

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

[plasmashell] [Bug 362944] plasma-desktop installs same file as kde-l10n 16.04

[Rex Dieter via KDE Bugzilla]

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

Rex Dieter  changed:

   What|Removed |Added

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

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

[kmymoney4] [Bug 362139] CSV Importer asks the same question twice during profile deletion

[NSLW via KDE Bugzilla]

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

--- Comment #11 from NSLW  ---
(In reply to allan from comment #10)
> (In reply to NSLW from comment #9)
> > (In reply to allan from comment #7)
> 
> > > I think I've traced it, possibly,  to the recent fee patch.
> > > In investprocessing.cpp(), at circa line 1723 -
> > > tr.m_amount = tr.m_amount.abs() - m_trInvestData.fee.abs();
> > > appears to drop the sign.
> > 
> > I'm glad you did it and gave feedback. I apologize if something is broken
> > for you lately with CSV imports. 
> 
> I don't have any problem, as I was using a test file, not live data.
> 
> > I would like to help fixing that. Could you
> > send your problematic, anonymized CSV test file and explain me what result
> > you expect after importing?
> > As I understand, you've got two CashDividends: one negative and one
> > positive. Frankly I don't get it, shouldn't CashDividends be always
> > positive, as it its you who gets the cash?
> 
> The test file is one I've used for several years, and originally I obtained
> it from another user.  At that time, I was developing the CSV investment
> handling and I found the file quite useful, as the data was not the usual
> straight-forward simple investment transactions.  I cannot now remember if
> the CashDividend with the negative amount was an original entry, or whether
> I modified it for the purpose.  My "justification/rationale" for the entry
> was that it was documenting a refund of an erroneous earlier transaction.  I
> suppose a "miscexp" would be similar (or perhaps not).  The file was from a
> US broker, who did produce some odd methods in his files.  As it's quite
> small, here it is below.
> 
> "Trade Date","Settlement Date","Type","Description 1 ","Description
> 2","Symbol/CUSIP","Quantity","Price ($)","Amount ($)"
> "","2/24/2010","DividendAndInterest","Div","description","NECZX","","","504.
> 72"
> 
> "","3/28/2010","Other","Div","description",""NECZX"","","","-504.72"

If it's some kind of "refund of an erroneous earlier transaction" then in my
opinion it's not CashDividend. I read more on dividends on folowing websites:
http://www.investopedia.com/terms/c/cashdividend.asp?o=40186=dir=999=investopediaSiteSearch=investopedia.com
http://www.investopedia.com/ask/answers/011215/how-are-dividends-usually-paid-out.asp
http://www.investopedia.com/walkthrough/corporate-finance/5/dividends/cash-payment.aspx?o=40186=dir=999=investopediaSiteSearch=investopedia.com

and I cannot find any real life situation where stockholder would pay money to
corporation under term dividend. Are you sure this case is real world case?

BTW. Do you've got more test files for CSV imports?

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

[kmymoney4] [Bug 351874] QIF import of investment buys and sells mishandles commissions

[NSLW via KDE Bugzilla]

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

--- Comment #10 from NSLW  ---
(In reply to Jack from comment #5)
> I import to investment accounts from OFX frequently, and it works just fine.
> (Well, mostly, but my problems are mainly in what my broker provides, not
> how KMM handles it, and I've complained about it in the past on the mailing
> list.)  I can probably provide some example files, but I'd have to choose
> carefully for ones that  don't show any of the problems.

I wonder how you test if OFX imports are correct? Is your test based only on
fact that KMM doesn't show you warning signs in ledger?

My problem with CSV was that buy and sell amounts with commissions were wrong
but warning sing was shown only for sell transactions. I patched CSV code in
such way that no warning sign was shown, but both buy and sell amounts still
were wrong. In my opinion, I tried every combination in CSV code to make
amounts right but I failed, so statement reader was to blame. 

I'm going to code on weekend, so your OFX file would help me embrace it all at
one time.


(In reply to Jeff from comment #6)
> There is still a problem with the QIF import with your change.  My test file
> also tested the case where the commission was greater than the proceeds from
> the sale (which can happen when trading options.)  Your fix changed a "sell"
> trade that actually cost money into one that brought in money. The example
> in my test file was the "sell" of the "NFLX Aug 18 2012 110.0 Call". The
> price is 0.02, times 100 shares = 2.00. The commission is 10.77.  So income
> of 2.00, outgo of 10.77 makes the total -8.77 (as shown in the U and T
> values in the QIF file).  The cash account should decrease by 8.77. Your
> change turned that into a positive 8.77, and increased the cash account. 
> This is admittedly a corner case, and I think I am the only KMM user that
> trades options because I have made a bunch of other changes to the KMM code
> to support that.

Now I see that too and it needs to be fixed. As you've said it's corner case
and I didn't take it into account.
Summarizing it: It didn't work for you in general case and corner case. Now it
works for you in general case but still not in corner case :)


(In reply to allan from comment #7)
> The OFX specification 2.0.3 includes -
> "CHAPTER 13 INVESTMENTS
> OFX supports download of security information and detailed investment
> account statements including
> transactions, open orders, balances, and positions.
> " plus a lot more in detail.
> Allan

Thanks for the info. It looks like I was searching in the wrong area.

Regards
Łukasz

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

[gwenview] [Bug 363187] New: Gwenview crashes on launch

[Terence Petersen-Ajbro via KDE Bugzilla]

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

Bug ID: 363187
   Summary: Gwenview crashes on launch
   Product: gwenview
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: terence.aj...@gmail.com
CC: myr...@kde.org

Application: gwenview (15.12.3)

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

-- Information about the crash:
The app crashes every time I start it except when selecting a file or folder
and opening the file or folder with Gwenview.

The crash can be reproduced every time.

-- Backtrace:
Application: Gwenview (gwenview), signal: Bus error
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd6915c99c0 (LWP 3696))]

Thread 2 (Thread 0x7fd68f372700 (LWP 3697)):
#0  0x7fd69ff19e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fd698e0ec62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fd698e108d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fd69109d629 in QXcbEventReader::run (this=0x12ba480) at
qxcbconnection.cpp:1253
#4  0x7fd6a060f84e in QThreadPrivate::start (arg=0x12ba480) at
thread/qthread_unix.cpp:331
#5  0x7fd69b4216fa in start_thread (arg=0x7fd68f372700) at
pthread_create.c:333
#6  0x7fd69ff25b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fd6915c99c0 (LWP 3696)):
[KCrash Handler]
#6  mdb_node_search (mc=mc@entry=0x1b4d460, key=key@entry=0x7fff3812ca70,
exactp=exactp@entry=0x0) at mdb.c:5112
#7  0x7fd6937927cb in mdb_cursor_set (mc=mc@entry=0x1b4d460,
key=key@entry=0x7fff3812ca70, data=data@entry=0x0, op=op@entry=MDB_SET_RANGE,
exactp=exactp@entry=0x0) at mdb.c:5901
#8  0x7fd6937910bd in mdb_cursor_get (mc=0x1b4d460,
key=key@entry=0x7fff3812ca70, data=data@entry=0x0, op=op@entry=MDB_SET_RANGE)
at mdb.c:6133
#9  0x7fd698be9a8e in Baloo::PostingDB::fetchTermsStartingWith
(this=this@entry=0x7fff3812cac0, term=...) at
../../../src/engine/postingdb.cpp:128
#10 0x7fd698bf1dcd in Baloo::Transaction::fetchTermsStartingWith
(this=this@entry=0x7fff3812cb30, term=...) at
../../../src/engine/transaction.cpp:168
#11 0x7fd69eb4b617 in Baloo::TagListJob::start (this=0x1b4adf0) at
../../../src/lib/taglistjob.cpp:59
#12 0x7fd6a147271e in KJob::exec (this=this@entry=0x1b4adf0) at
../../../src/lib/jobs/kjob.cpp:197
#13 0x7fd6a46703a0 in Gwenview::BalooSemanticInfoBackend::refreshAllTags
(this=0x1352110) at
/build/gwenview-iJ9mAT/gwenview-15.12.3/lib/semanticinfo/baloosemanticinfobackend.cpp:68
#14 0x7fd6a4670313 in Gwenview::BalooSemanticInfoBackend::allTags
(this=0x1352110) at
/build/gwenview-iJ9mAT/gwenview-15.12.3/lib/semanticinfo/baloosemanticinfobackend.cpp:60
#15 0x7fd6a466eb01 in Gwenview::TagModel::createAllTagsModel
(parent=, backEnd=0x1352110) at
/build/gwenview-iJ9mAT/gwenview-15.12.3/lib/semanticinfo/tagmodel.cpp:122
#16 0x0048010f in Gwenview::StartMainPagePrivate::setupSearchUi
(this=0x1932da0) at
/build/gwenview-iJ9mAT/gwenview-15.12.3/app/startmainpage.cpp:88
#17 Gwenview::StartMainPage::showEvent (this=0x192fe50, event=0x7fff3812d020)
at /build/gwenview-iJ9mAT/gwenview-15.12.3/app/startmainpage.cpp:255
#18 0x7fd6a1af5f88 in QWidget::event (this=this@entry=0x192fe50,
event=event@entry=0x7fff3812d020) at kernel/qwidget.cpp:9044
#19 0x7fd6a1bf4b5e in QFrame::event (this=0x192fe50, e=0x7fff3812d020) at
widgets/qframe.cpp:540
#20 0x7fd6a1ab305c in QApplicationPrivate::notify_helper
(this=this@entry=0x12a2c60, receiver=receiver@entry=0x192fe50,
e=e@entry=0x7fff3812d020) at kernel/qapplication.cpp:3716
#21 0x7fd6a1ab8516 in QApplication::notify (this=0x7fff3812d640,
receiver=0x192fe50, e=0x7fff3812d020) at kernel/qapplication.cpp:3499
#22 0x7fd6a07f062b in QCoreApplication::notifyInternal
(this=0x7fff3812d640, receiver=receiver@entry=0x192fe50,
event=event@entry=0x7fff3812d020) at kernel/qcoreapplication.cpp:965
#23 0x7fd6a1af2a86 in QCoreApplication::sendEvent (event=0x7fff3812d020,
receiver=0x192fe50) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:224
#24 QWidgetPrivate::show_helper (this=0x1932bb0) at kernel/qwidget.cpp:7822
#25 0x7fd6a1af2656 in QWidgetPrivate::show_recursive (this=)
at kernel/qwidget.cpp:7693
#26 0x7fd6a1af2776 in QWidgetPrivate::showChildren
(this=this@entry=0x13cb9b0, spontaneous=spontaneous@entry=false) at
kernel/qwidget.cpp:8189
#27 0x7fd6a1af280f in QWidgetPrivate::show_helper
(this=this@entry=0x13cb9b0) at kernel/qwidget.cpp:7769
#28 0x7fd6a1af55fd in QWidget::setVisible (this=0x13b3140,
visible=) at kernel/qwidget.cpp:8108
#29 0x7fd6a1af2788 in 

[krita] [Bug 363021] [HUION] No pressure sensitivity on Huion 1060 Plus

[Quiralta via KDE Bugzilla]

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

--- Comment #8 from Quiralta  ---
No prob! Maybe it took a while to re-register the tablet, (sometimes re-plugin
also does the job) don't forget to keep evdev from upgrading until there is a
fix for it, Apparently libinput is also coming with tablet support next xorg
update, thus there may be another choice.

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

[Spectacle] [Bug 362241] Rectangular Region option does not preview and does not save an image after 15.12.3-2 -> 16.04.0-1

[Ron Willhoite via KDE Bugzilla]

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

--- Comment #6 from Ron Willhoite  ---
Has been working for me, on Arch Linux. I haven't tried other distros.

Name: spectacle
Version : 16.04.1-1
Description : KDE screenshot capture utility
Architecture: x86_64
Build Date  : Fri 06 May 2016 08:31:23 PM EDT
Install Date: Tue 10 May 2016 05:14:31 PM EDT

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

[kate] [Bug 363186] New: PHP syntax highlighting problem in comments

[郭云鹤]

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

Bug ID: 363186
   Summary: PHP syntax highlighting problem in comments
   Product: kate
   Version: 5.0.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: syntax
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: guoyunhebr...@gmail.com

http://imgur.com/F9kmCjn

When type author in comments, like:

/**
 * Classname
 *
 * @author Guo Yunhe 
 */

The email address seems highlighted as HTML tags.

Reproducible: Always

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

[krita] [Bug 363021] [HUION] No pressure sensitivity on Huion 1060 Plus

[via KDE Bugzilla]

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

rnd...@nm.ru changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |INVALID
 Status|NEEDSINFO   |RESOLVED

--- Comment #7 from rnd...@nm.ru ---
Turns out krita works fine now and i have no clue why. Since my test and post
in the morning i did not reboot nor did anything else. Pressure did not work in
Krita in the morning, but worked in gimp. Firing up MyPaint just now - pressure
worked. Figured i will try Krita one last time before i start deleting settings
and compiling - and now it works in Kirta too! So i guess this was the same
problem after all.

Sorry for wasting everyone's time and thanks for pointing me to the right
direction.

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

[kfile] [Bug 363185] file selection dialog very slow when samba shares are not present

[Romain Bazile via KDE Bugzilla]

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

--- Comment #1 from Romain Bazile  ---
I think this could be linked to the file dialog trying to connect to the shares
to evaluate the free space available in those places.

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

[kfile] [Bug 363185] New: file selection dialog very slow when samba shares are not present

[Romain Bazile via KDE Bugzilla]

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

Bug ID: 363185
   Summary: file selection dialog very slow when samba shares are
not present
   Product: kfile
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: grom...@hotmail.com

I have two samba shares defined in my /etc/fstab:
//192.168.0.69/DataHere/run/media/username/DataHere cifs
credentials=/home/username/.sambacreds,x-systemd.automount,uid=username 0 0
//192.168.0.70/DataThere  /run/media/username/DataThere cifs
credentials=/home/username/.sambacreds,x-systemd.automount,uid=username 0 0

Whenever I start my computer and those two shares are not on my network (for
example at work vs at home), the file dialog selection becomes very slow and
almost unusable.
This means when I want to do "save as" from Firefox or Thunderbird, or any
other program (LibreOffice or Kate also), the dialog is very slow, either when
I want to navigate through the folders, select a file, or change the name.

When I'm connected to those samba shares, the dialog works flawlessly and is
fast.

I will do more tests to see if suspend/waking the computer helps with the issue
or worsen it, or with moving the computer back and forth between the two
places.

Reproducible: Always

Steps to Reproduce:
1. Define samba shares in /etc/fstab
2. Make sure they are not present on the network
3. Open a save file or open file dialog (from Firefox or Kate)

Actual Results:  
File selection dialog is very slow, and unresponsive for several dozens of
seconds

Expected Results:  
File selection dialog should be fast

I'm using an Arch Linux Derivative, Manjaro, up to date as of today (2016 May
17).

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

[plasmashell] [Bug 362944] plasma-desktop installs same file as kde-l10n 16.04

[Jonathan Riddell via KDE Bugzilla]

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

Jonathan Riddell  changed:

   What|Removed |Added

 CC||ivan.cu...@kde.org

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

[plasmashell] [Bug 362944] plasma-desktop installs same file as kde-l10n 16.04

[Jonathan Riddell via KDE Bugzilla]

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

--- Comment #5 from Jonathan Riddell  ---
https://git.reviewboard.kde.org/r/127943/

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

[neon] [Bug 363173] spectacle not installed by default

[Jonathan Riddell via KDE Bugzilla]

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

Jonathan Riddell  changed:

   What|Removed |Added

 CC||j...@jriddell.org
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Jonathan Riddell  ---
is installed now, brings in purpose which brings in lots of things so I moved
purpose depends to suggests to lighten that for now

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

[amarok] [Bug 363176] Enabling the script console crashes amarok

[via KDE Bugzilla]

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

pub...@wernig.net changed:

   What|Removed |Added

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

--- Comment #3 from pub...@wernig.net ---
(In reply to Myriam Schweingruber from comment #2)
> Did you make sure the folder is writeable and tried again?
After chmod 777 /usr/share/apps/amarok/scriptconsole the error does not occur
anymore.
But obviously there is absolutely no reason why amarok should be writing
something there.
What are the permissions of  /usr/share/apps/amarok/scriptconsole on your
system?

> Strangely the
> folder this tries to write to is in /usr/.. , while it should be in your
> home folder at ~/.kde/.. , so there is something wrong in your installation.
Maybe so. Do you see any chance to find out what that is? There is no directory
called "scriptconsole" in ~/.kde4/share/apps/amarok ... oh wait! 
After I created the directory ~/.kde4/share/apps/amarok/scriptconsole by hand,
amarok does not crash anymore, but in fact the script console opens ... so it's
a missing directory :-)

But that would still be a bug, right? It shouldn't really crash, but just
create the directory.

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

[kio] [Bug 362762] Unable to create io-slave: Could not find the 'kio_kamera' plugin.

[Benoit Grégoire via KDE Bugzilla]

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

Benoit Grégoire  changed:

   What|Removed |Added

 CC||beno...@coeus.ca

--- Comment #2 from Benoit Grégoire  ---
Same here.  As an easy way to trigger the problem, open the "Digital Camera"
config module.  From the command line that is:  

kcmshell5 kamera

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

[krita] [Bug 363110] Insecure download for pre-built Krita (especially the beta version)

[_Vi]

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

--- Comment #5 from Vitaly "_Vi" Shukela  ---
One more idea: include magnet links. A file downloaded from magnet link
(obtained securely, of course) should be secure.

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

[kwin] [Bug 361940] In focus follows mouse mode, the window under the pointer sometimes does not have focus

[matejcik via KDE Bugzilla]

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

--- Comment #20 from matejcik  ---
(In reply to Thomas Lübking from comment #19)
> > FocusStealingPreventionLevel=2
> The focus moves despite the medium FSP? Or does this cause a flashing taks
> item?

both, it doesn't seem to be deterministic
setting to High or Extreme prevents the focus loss and only causes flashing
taskbar. on Low and Medium, either can happen.

> > DelayFocusInterval=0
> Wild guess, what if you raise this to, say, 100ms?

yes, this seems to help, i'm not able to reproduce the problem anymore.
(not deliberately anyway. i'll see if it crops up again while i'm working, but
it seems to be a workable solution)

for the record, xfwm4 has the focus delay feature too, and even on the lowest
setting the problem doesn't appear. but i don't know whether it's actually zero
or some small nonzero number

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

[kdevelop] [Bug 363180] The qmljs parser crashes in QmlJS::getDeclaration

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

 CC||steckde...@yahoo.fr

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

[kwin] [Bug 361940] In focus follows mouse mode, the window under the pointer sometimes does not have focus

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #19 from Thomas Lübking  ---
> FocusStealingPreventionLevel=2
The focus moves despite the medium FSP? Or does this cause a flashing taks
item?

> DelayFocusInterval=0
Wild guess, what if you raise this to, say, 100ms?

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

[kdevelop] [Bug 363184] New: reinstate building the default make target in project subdirs

[RJVB via KDE Bugzilla]

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

Bug ID: 363184
   Summary: reinstate building the default make target in project
subdirs
   Product: kdevelop
   Version: git master
  Platform: Compiled Sources
OS: All
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Buildtools: Make
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: rjvber...@gmail.com

KDevelop 4.x has a convenient feature where you can issue a build command (via
hotkey, context menu or the toplevel menu) with  a project's subdirectory
selected in the project manager. If the project uses Makefiles and one exists
in that particular directory, only the default target at that level would be
built. The implementation as far as I understand it from feedback in the Build
view is extremely simple: 

1) chdir into the target subdir
2) call make

Reproducible: Always

Steps to Reproduce:
1. Open a project that uses Unix Makefiles
2. Select a directory containing a Makefile (as indicated by the different
folder icon)
3. Issue a build command

Actual Results:  
KDevelop 4.7.3 will build only the source under the selected subdir, possibly
after building any dependencies from elsewhere in the project (depending on
whether that's required and the required information is available, which is
usually the case for CMake-based projects)

KDevelop 5 (4.90x) simply builds the full project

Expected Results:  
KDevelop 4.7 has the preferred behaviour, which is also the behaviour I'd
expect from a GUI IDE.

As pointed out on the mailing list, it is still possible to select a target in
the subdir of interest and build that. There are however several reasons why
the possibility of building a default target would be convenient - in addition
to the aforementioned fact that it's what you'd expect from a point-and-click
interface where you select an item and tell it to build :

1) building a target requires the targets to be visible, which is done via a
small icon at the top of the project manager
2) it isn't always that trivial to know what the default target is (or else
what specific target to build after a point edit), even in projects you
authored yourself after a certain time has passed
3) this is all the more true for autoconf based projects which tend to have
sometimes incredibly long lists of targets - per subdirectory.
4) finding the target of choice in a long scroll list isn't a very efficient
process, ditto for finding source files (IOW, long lists of build targets, say
more than 5 or 6 are best kept hidden).

As mentioned above, there shouldn't be any need for advanced parsing to
determine the default target. Executing the make command in the selected
directory should give the expected behaviour automatically (or else produce a
sufficiently clear error message).
The implementation thus seems something that doesn't require intimate knowledge
of KDevelop's internal architecture, and something I should be able to do in
parallel to my other occupations. 

I think I'd just need some pointers to figure out:
- the classes and/or files that require changes (cmake, qmake, custom make
project managers, which others, or is there a subclassed generic interface that
could provide the feature?)
- how to obtain the selected subdir in the method that handles the build
action.

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

[krunner] [Bug 363182] New: krunner crashes when starting iceweasel after starting plasma desktop

[Arthur Marsh via KDE Bugzilla]

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

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

Application: krunner (5.5.4)

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

-- Information about the crash:
Restarted plasma desktop after kernel and other upgrades/reboot, used alt-F2 to
start iceweasel, which started but krunner crashed. 2 krunner process remain
but don't respond to alt-F2.

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

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

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

Thread 10 (Thread 0x7fa4fa5ee700 (LWP 4032)):
#0  0x0030004dbdad in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x003002c8d740 in g_wakeup_acknowledge (__nbytes=16,
__buf=0x7fa4fa5edbe0, __fd=) at
/usr/include/x86_64-linux-gnu/bits/unistd.h:44
#2  0x003002c8d740 in g_wakeup_acknowledge (wakeup=0x7fa515b0) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gwakeup.c:210
#3  0x003002c49e84 in g_main_context_check
(context=context@entry=0x7fa4f4000990, max_priority=2147483647,
fds=fds@entry=0x7fa4f4003070, n_fds=n_fds@entry=1) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3632
#4  0x003002c4a340 in g_main_context_iterate
(context=context@entry=0x7fa4f4000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3837
#5  0x003002c4a4ac in g_main_context_iteration (context=0x7fa4f4000990,
may_block=may_block@entry=1) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3901
#6  0x0030176dca5b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fa4f40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#7  0x003017683d6a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fa4fa5edde0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#8  0x0030174a0854 in QThread::exec() (this=) at
thread/qthread.cpp:503
#9  0x003047cd5105 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#10 0x0030174a57fe in QThreadPrivate::start(void*) (arg=0x2a6fbf0) at
thread/qthread_unix.cpp:331
#11 0x003000c07454 in start_thread (arg=0x7fa4fa5ee700) at
pthread_create.c:334
#12 0x0030004e8e5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7fa4f0380700 (LWP 4954)):
#0  0x003000c0d04f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x0030174a6a9b in QWaitCondition::wait(QMutex*, unsigned long)
(time=18446744073709551615, this=0x2a8e370) at
thread/qwaitcondition_unix.cpp:136
#2  0x0030174a6a9b in QWaitCondition::wait(QMutex*, unsigned long)
(this=, mutex=0x290c710, time=time@entry=18446744073709551615)
at thread/qwaitcondition_unix.cpp:208
#3  0x7fa4f83f002b in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked(ThreadWeaver::Thread*)
(this=this@entry=0x2a5e150, th=) at ../../src/weaver.cpp:594
#4  0x7fa4f83f0ddf in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,

[i18n] [Bug 363181] New: Time formats on en_IE

[via KDE Bugzilla]

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

Bug ID: 363181
   Summary: Time formats on en_IE
   Product: i18n
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: aa...@kde.org
  Reporter: gbonner...@gmail.com

Really simple, and I'd submit a patch somewhere if I could figure out what file
this is contained in. Time formats on en_IE locale should default to 24-hour
like they do on every other OS, but at present they default to 12-hour.

Reproducible: Always

Steps to Reproduce:
1. Set formats to en_IE

Actual Results:  
Time displays as 1:30pm

Expected Results:  
Time displays as 13:30

I believe (but am not certain) that this affects several English locales other
than en_IE, such as en_AU, en_NZ etc., which I'm almost certain also usually
default to 24-hour but in KDE currently default to 12-hour.

Current workaround is to override time to en_GB

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

[calligrawords] [Bug 363071] calligra words

[Rex Dieter via KDE Bugzilla]

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

Rex Dieter  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REOPENED|RESOLVED

--- Comment #3 from Rex Dieter  ---
OK, I'll dup bug #345240  , the symptoms are the same, but I'm guessing this is
some gcc6'ism, where soprano can't find it's own plugins for some reason.

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

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

[calligrawords] [Bug 345240] Crash when open Calligra Word

[Rex Dieter via KDE Bugzilla]

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

Rex Dieter  changed:

   What|Removed |Added

 CC||guillaume@sfr.fr

--- Comment #24 from Rex Dieter  ---
*** Bug 363071 has been marked as a duplicate of this bug. ***

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

[calligrawords] [Bug 363071] calligra words

[Rex Dieter via KDE Bugzilla]

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

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@math.unl.edu
 Resolution|DOWNSTREAM  |---
 Ever confirmed|0   |1
 Status|RESOLVED|REOPENED

--- Comment #2 from Rex Dieter  ---
No it's not. I can reproduce this too, simply starting calligra and trying to
open the blank template.  That said, the crash seems to be happening down in
soprano somewhere.

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

[amarok] [Bug 354669] Most actions using Iphone IOS app crashes Amarok

[Myriam Schweingruber via KDE Bugzilla]

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

Myriam Schweingruber  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED

--- Comment #7 from Myriam Schweingruber  ---
Closing correctly

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

[amarok] [Bug 363176] Enabling the script console crashes amarok

[Myriam Schweingruber via KDE Bugzilla]

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

Myriam Schweingruber  changed:

   What|Removed |Added

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

--- Comment #2 from Myriam Schweingruber  ---
Did you make sure the folder is writeable and tried again? Strangely the folder
this tries to write to is in /usr/.. , while it should be in your home folder
at ~/.kde/.. , so there is something wrong in your installation.
FWIW: I can't reproduce this here with current git master, which should be very
similar to 2.8.90

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

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

[Raman Gupta via KDE Bugzilla]

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

--- Comment #56 from Raman Gupta  ---
Same issue here. Fedora 23 desktop setup, three monitors, one large one in the
middle and two smaller ones to the left and right. On reboot, KDE always resets
all three monitors to the same resolution, and stacks them (so they show the
screen output mirrored).

Repeatable on every reboot. I have made the config file .local/share/kscreen/
read-only and the issue still happens.

This is relatively new (a few months) -- this setup used to work fine in the
KDE 4.x days and early KDE 5.x days.

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

[Akonadi] [Bug 360792] akonadi_davgroupware_resource crashes constandly

[Tim Eberhardt via KDE Bugzilla]

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

--- Comment #4 from Tim Eberhardt  ---
Created attachment 99035
  --> https://bugs.kde.org/attachment.cgi?id=99035=edit
crash dump

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

[Akonadi] [Bug 360792] akonadi_davgroupware_resource crashes constandly

[Tim Eberhardt via KDE Bugzilla]

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

Tim Eberhardt  changed:

   What|Removed |Added

 CC||tim.eberha...@tu-bs.de

--- Comment #3 from Tim Eberhardt  ---
Can confirm this.

openSUSE Tumbleweed, KDE from Factory repository
Applications 16.04
Frameworks 5.22

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

[kdeplasma-addons] [Bug 348591] System Load Viewer widget in panel can't show individual cores/cpus

[scsi via KDE Bugzilla]

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

scsi  changed:

   What|Removed |Added

 CC||scsic...@gmail.com

--- Comment #13 from scsi  ---
I have two notebook and install same version of kde on gentoo. One can show
individual core and the other can not. I don't know what is different  between
them. If anybody how to find the solution to the one which can not show
individual core information.

thanks

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

[kwin] [Bug 361940] In focus follows mouse mode, the window under the pointer sometimes does not have focus

[matejcik via KDE Bugzilla]

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

--- Comment #18 from matejcik  ---
I tried xfwm4 as a window manager inside KDE and could not reproduce the issue.
I didn't manage to run mutter this way, but i don't see this issue on my GNOME3
desktop.

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

[krita] [Bug 360666] over write dialog is not shown when saving a file with preexisting file name. the file gets overwritten without alerting and data of existing file is lost

[Jonathan Marten via KDE Bugzilla]

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

Jonathan Marten  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |CONFIRMED

--- Comment #9 from Jonathan Marten  ---
https://git.reviewboard.kde.org/r/127944/

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

[kmymoney4] [Bug 351874] QIF import of investment buys and sells mishandles commissions

[Jeff via KDE Bugzilla]

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

--- Comment #9 from Jeff  ---
That line:

tr.m_amount = -amount;

is the one I changed in my patch to fix my problem for "sells".  Need remove
the negative sign.

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

[neon] [Bug 363169] display-im6.q16 installed by default

[Jonathan Riddell via KDE Bugzilla]

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

Jonathan Riddell  changed:

   What|Removed |Added

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

--- Comment #3 from Jonathan Riddell  ---
overridden it in neon-settings

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

[krita] [Bug 359642] [UC-LOGIC] Tablet Pressure sensitivity not working

[Dmitry Kazakov via KDE Bugzilla]

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

--- Comment #7 from Dmitry Kazakov  ---
Git commit a73c0de6d19094a262185f7e88c08cb710d4f5a6 by Dmitry Kazakov.
Committed on 17/05/2016 at 13:23.
Pushed by dkazakov into branch 'master'.

A testing patch for the UC-LOGIC devices

The patch hasn't been tested on a real device yet. Just push it
to make package building easier.

M  +4-0libs/ui/input/wintab/qxcbconnection_xi2.cpp

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

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

[Breeze] [Bug 356544] ktorrent icon

[Alex L via KDE Bugzilla]

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

Alex L  changed:

   What|Removed |Added

 CC||alexlon...@gmail.com

--- Comment #9 from Alex L  ---
Do you clean Plasma's cache?
I had the same issue but now it's gone.

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

[kwin] [Bug 361940] In focus follows mouse mode, the window under the pointer sometimes does not have focus

[matejcik via KDE Bugzilla]

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

--- Comment #17 from matejcik  ---
Created attachment 99034
  --> https://bugs.kde.org/attachment.cgi?id=99034=edit
kwinrc of config

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

[kompare] [Bug 362440] can not choose files to compare

[Laptander via KDE Bugzilla]

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

Laptander  changed:

   What|Removed |Added

 CC||dev-laptan...@yandex.ru

--- Comment #1 from Laptander  ---
I can confirm.
First time you start application, you are able to choose files in dialog.
But when you want to compare another files while main window of application
exists, you cannot see files in dialog.
You can still type file name manually in name field, if you remember how file
is named.
I suspect that wrong filter (or how it is called) is used. It displays only
catalogs, but not files.

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

[kdevelop] [Bug 363044] Crash when parsing javascript/python files [DeclarationBuilder::inferArgumentsFromCall]

[Jonathan Verner via KDE Bugzilla]

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

--- Comment #3 from Jonathan Verner  ---
I've filed a new bug with the "new" crash here: bug #363180

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

[kdevelop] [Bug 363180] The qmljs parser crashes in QmlJS::getDeclaration

[Jonathan Verner via KDE Bugzilla]

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

--- Comment #2 from Jonathan Verner  ---
Created attachment 99033
  --> https://bugs.kde.org/attachment.cgi?id=99033=edit
File which crashes kdevelop

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

[kdevelop] [Bug 363180] The qmljs parser crashes in QmlJS::getDeclaration

[Jonathan Verner via KDE Bugzilla]

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

--- Comment #1 from Jonathan Verner  ---
Created attachment 99032
  --> https://bugs.kde.org/attachment.cgi?id=99032=edit
first 100 and last 100 frames from backtrace

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

[kdevelop] [Bug 363180] New: The qmljs parser crashes in QmlJS::getDeclaration

[Jonathan Verner via KDE Bugzilla]

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

Bug ID: 363180
   Summary: The qmljs parser crashes in QmlJS::getDeclaration
   Product: kdevelop
   Version: 4.7.3
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Language Support: QML/JavaScript
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: jonathan.ver...@gmail.com

When parsing the attached file, kdevelop immediately crashes with the attached
backtrace (the backtrace has 65000 frames so I am attaching only the first and
last 100 and pasting only the first few here):

#0  0x71979a91 in ?? () from /usr/lib/libkdevplatformlanguage.so.8
No symbol table info available.
#1  0x71978af6 in
KDevelop::IndexedQualifiedIdentifier::IndexedQualifiedIdentifier() ()
   from /usr/lib/libkdevplatformlanguage.so.8
No symbol table info available.
#2  0x719c50f8 in
KDevelop::PersistentSymbolTable::getDeclarations(KDevelop::IndexedQualifiedIdentifier
const&) const () from /usr/lib/libkdevplatformlanguage.so.8
No symbol table info available.
#3  0x719c5f09 in
KDevelop::PersistentSymbolTable::getFilteredDeclarations(KDevelop::IndexedQualifiedIdentifier
const&, Utils::StorableSet const&) const ()
   from /usr/lib/libkdevplatformlanguage.so.8
No symbol table info available.
#4  0x7195704d in ?? () from /usr/lib/libkdevplatformlanguage.so.8
No symbol table info available.
#5  0x719575a8 in bool
KDevelop::TopDUContext::applyAliases(KDevelop::QualifiedIdentifier
const&, KSharedPtr const&,
KDevelop::TopDUContext::FindDeclarationsAcceptor&, KDevelop::CursorInRevision
const&, bool, KDevelop::TopDUContext::ApplyAliasesBuddyInfo*, unsigned int)
const () from /usr/lib/libkdevplatformlanguage.so.8
No symbol table info available.
#6  0x719509f4 in
KDevelop::TopDUContext::findDeclarationsInternal(KDevVarLengthArray const&, KDevelop::CursorInRevision const&, TypePtr
const&, KDevVarLengthArray&, KDevelop::TopDUContext
const*, QFlags, unsigned int) const () from
/usr/lib/libkdevplatformlanguage.so.8
No symbol table info available.
#7  0x719433e1 in
KDevelop::DUContext::findDeclarations(KDevelop::Identifier const&,
KDevelop::CursorInRevision const&, KDevelop::TopDUContext const*,
QFlags) const
() from /usr/lib/libkdevplatformlanguage.so.8
No symbol table info available.
#8  0x7fff2ec43eab in QmlJS::getDeclaration (id=...,
context=context@entry=0x7fff08106830,
searchInParent=searchInParent@entry=true)
at /home/jonathan/zdroj/kde/src/kdev-qmljs/duchain/helper.cpp:57
declarations = {{p = {static shared_null = {ref = {_q_value = 1}, alloc
= 0, begin = 0,
end = 0, sharable = 1, array = {0x0}}, d = 0x7fff08dbfcc0}, d =
0x7fff08dbfcc0}}
lock = {m_lock = 0x1517d20, m_locked = true, m_timeout = 0}
#9  0x7fff2ec44831 in QmlJS::getInternalContext (declaration=...)
at /home/jonathan/zdroj/kde/src/kdev-qmljs/duchain/helper.cpp:230
baseClass = {static null = {}, static shared_null =
{ref = {_q_value = 1},
alloc = 0, size = 0, data = 0x62109a ,
clean = 0, simpletext = 0,
righttoleft = 0, asciiCache = 0, capacity = 0, reserved = 0, array
= {0}},
  static shared_empty = {ref = {_q_value = 2446}, alloc = 0, size = 0,
data = 0x7521191a , clean = 0,
simpletext = 0,
righttoleft = 0, asciiCache = 0, capacity = 0, reserved = 0, array
= {0}},
  d = 0x7fff08dbfce0, static codecForCStrings = 0x0}
structureType = 
integralType = 
lock = {m_lock = 0x1517d20, m_locked = true, m_timeout = 0}
functionType = 
#10 0x7fff2ec44839 in QmlJS::getInternalContext (declaration=...)
at /home/jonathan/zdroj/kde/src/kdev-qmljs/duchain/helper.cpp:230
baseClass = {static null = {}, static shared_null =
{ref = {_q_value = 1},
alloc = 0, size = 0, data = 0x62109a ,
clean = 0, simpletext = 0,
righttoleft = 0, asciiCache = 0, capacity = 0, reserved = 0, array
= {0}},
  static shared_empty = {ref = {_q_value = 2446}, alloc = 0, size = 0,
data = 0x7521191a , clean = 0,
simpletext = 0,
righttoleft = 0, asciiCache = 0, capacity = 0, reserved = 0, array
= {0}},
  d = 0x7fff08dbfc20, static codecForCStrings = 0x0}
structureType = 
integralType = 
lock = {m_lock = 0x1517d20, m_locked = true, m_timeout = 0}
functionType = 




Reproducible: Always

Steps to Reproduce:
1. Open the attached file assign.js

-- 
You are receiving this mail because:
You are watching all 

[Breeze] [Bug 356544] ktorrent icon

[via KDE Bugzilla]

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

--- Comment #8 from tuk...@gmail.com ---
I'm running Debian testing which is fairly up-to-date, and updated all my
system's packages yesterday. The issue persists here.

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

[neon] [Bug 363169] display-im6.q16 installed by default

[Jonathan Riddell via KDE Bugzilla]

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

--- Comment #2 from Jonathan Riddell  ---
it's installed by cups-filters too so I don't think there's any getting rid of
it

we can add an override somewhere to set NoDisplay=true

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

[kdevelop] [Bug 363044] Crash when parsing javascript/python files [DeclarationBuilder::inferArgumentsFromCall]

[Jonathan Verner via KDE Bugzilla]

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

--- Comment #2 from Jonathan Verner  ---
O.K., I updated kdevelop to 4.7.3 and built kdev-qmljs from git commit
3f9a3d8453ae29cf7fa8a753010806398f08fa0c and now I cannot reproduce this
(however, kdevelop crashes with a different backtrace so I can't confirm that
the bug is no longer present)

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

[dolphin] [Bug 363179] New: While renaming long-name object, the Home button returns to start of line, not name

[Laptander via KDE Bugzilla]

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

Bug ID: 363179
   Summary: While renaming long-name object, the Home button
returns to start of line, not name
   Product: dolphin
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: dev-laptan...@yandex.ru

When name of file or folder is long enough, dolphin devides it to several
lines. Actually, file name do not contain "\n" (new line) symbol.
When you are renaming such files, you often want to add something to the
beginning of file name. But pressing Home button returns cursor to the
beginning of last line, not to the beginning of a whole file name.

Reproducible: Always

Steps to Reproduce:
1. Create a file with long name, which will be devided to several lines by
dolphin.
2. Select this file and press f2 or choose rename from context menu.
3. Press Home button.

Actual Results:  
Cursor will be pointing to start of the last line.

Expected Results:  
Cursor should be pointing to start of file neme (on first line).

Dolphin version 16.04.1

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

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[via KDE Bugzilla]

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

--- Comment #7 from swpal...@gmail.com ---
Replacing the message, "Seems that your system has no keys suitable for
encryption. Please set-up at least an encryption key, then try again." with
something more user-friendly is important.  The current message is only
meaningful to system administrators, not end users.

The dialog should have a button to launch a key generation wizard.

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

[krita] [Bug 360666] over write dialog is not shown when saving a file with preexisting file name. the file gets overwritten without alerting and data of existing file is lost

[Boudewijn Rempt via KDE Bugzilla]

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

--- Comment #8 from Boudewijn Rempt  ---
Okay, so this _is_ is a kf5 bug, not a krita bug.

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

[kde] [Bug 363140] World-readable X11 Cookie, easy key logger

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #6 from Christoph Feck  ---


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

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

[krita] [Bug 359642] [UC-LOGIC] Tablet Pressure sensitivity not working

[Dmitry Kazakov via KDE Bugzilla]

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

--- Comment #6 from Dmitry Kazakov  ---
Here is a proposed patch to fix this problem. Now we should make new builds and
test on that tablet. If the problem is fixed, the patch should be backported
upstream to Qt

https://phabricator.kde.org/P39

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