[kate] [Bug 363273] Kate sometimes loses edit panel when switching sessions

[Nick Coghlan via KDE Bugzilla]

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

--- Comment #1 from Nick Coghlan  ---
This seems to have now progressed to Kate simply not creating the edit panel
when opening an existing session, even on a fresh login. This problem then
persists even if opening a new session. (I've turned off SELinux and the
behaviour persists, so it isn't anything related to that).

Running Kate from a console window, I get this output:

==
$ kate &
$ QObject::connect: invalid null parameter
QObject::connect: invalid null parameter
QObject::connect: Cannot connect (null)::returnPressed() to
KUrlRequester::returnPressed()
QObject::connect: Cannot connect (null)::returnPressed(QString) to
KUrlRequester::returnPressed(QString)
Attempted to re-run an already running session.
QObject::connect: invalid null parameter
QObject::connect: invalid null parameter
QObject::connect: Cannot connect (null)::returnPressed() to
KUrlRequester::returnPressed()
QObject::connect: Cannot connect (null)::returnPressed(QString) to
KUrlRequester::returnPressed(QString)
Attempted to re-run an already running session.
Attempted to re-run an already running session.
==

The first "Attempted to re-run..." is from choosing a session at start-up, the
second pair is from an attempt to switch sessions.

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

[dolphin] [Bug 350082] missing some icons

[michael via KDE Bugzilla]

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

michael  changed:

   What|Removed |Added

 CC||reeves...@gmail.com

--- Comment #4 from michael  ---
This appears to be fixed by commit 44d4d2ea715719a08c639541530a5b330647297d
which was not back-ported to 15.12.3.

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

[plasmashell] [Bug 363422] New: Plasma crash on login.

[Adam Shrader via KDE Bugzilla]

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

Bug ID: 363422
   Summary: Plasma crash on login.
   Product: plasmashell
   Version: 5.6.4
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: ashrader...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.6.4)

Qt Version: 5.6.0
Frameworks Version: 5.22.0
Operating System: Linux 4.5.4-1-default x86_64
Distribution: "openSUSE Tumbleweed (20160422) (x86_64)"

-- Information about the crash:
This crash occurs on login. I have a dual monitor setup and when this occurs
the desktop is mirrored on each screen. I have an NVIDIA card I can use
nvidia-settings to get the desktop to span the two screen but I get visual
artifacts on the icon text on the desktop. Everything else works as expected.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/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 0x7fa30d8f48c0 (LWP 3290))]

Thread 11 (Thread 0x7fa2f7bcd700 (LWP 3292)):
#0  0x7fa306dd99cd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa30bd103f2 in _xcb_conn_wait (__timeout=-1, __nfds=1,
__fds=0x7fa2f7bccc00) at /usr/include/bits/poll2.h:46
#2  0x7fa30bd103f2 in _xcb_conn_wait (c=c@entry=0xd4f580,
cond=cond@entry=0xd4f5c0, vector=vector@entry=0x0, count=count@entry=0x0) at
xcb_conn.c:459
#3  0x7fa30bd11fc7 in xcb_wait_for_event (c=0xd4f580) at xcb_in.c:693
#4  0x7fa2fa552969 in QXcbEventReader::run() (this=0xd5b930) at
qxcbconnection.cpp:1325
#5  0x7fa3074ceb29 in QThreadPrivate::start(void*) (arg=0xd5b930) at
thread/qthread_unix.cpp:340
#6  0x7fa3065db454 in start_thread (arg=0x7fa2f7bcd700) at
pthread_create.c:333
#7  0x7fa306de23fd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7fa2f5ba0700 (LWP 3293)):
#0  0x7fa306dd99cd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa3034863f4 in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7fa2e8003ba0, timeout=, context=0x7fa2e8000990) at
gmain.c:4135
#2  0x7fa3034863f4 in g_main_context_iterate
(context=context@entry=0x7fa2e8000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3835
#3  0x7fa3034864fc in g_main_context_iteration (context=0x7fa2e8000990,
may_block=may_block@entry=1) at gmain.c:3901
#4  0x7fa3076e4c5b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fa2e80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#5  0x7fa30769079a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fa2f5b9fce0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7fa3074c9f2c in QThread::exec() (this=this@entry=0x7fa3086dcd00
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:503
#7  0x7fa30846d7b5 in QDBusConnectionManager::run() (this=0x7fa3086dcd00
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:181
#8  0x7fa3074ceb29 in QThreadPrivate::start(void*) (arg=0x7fa3086dcd00
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:340
#9  0x7fa3065db454 in start_thread (arg=0x7fa2f5ba0700) at
pthread_create.c:333
#10 0x7fa306de23fd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7fa2e700 (LWP 3296)):
#0  0x7fa306dd99cd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa3034863f4 in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7fa2e4002e70, timeout=, context=0x7fa2e4000990) at
gmain.c:4135
#2  0x7fa3034863f4 in g_main_context_iterate
(context=context@entry=0x7fa2e4000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3835
#3  0x7fa3034864fc in g_main_context_iteration (context=0x7fa2e4000990,
may_block=may_block@entry=1) at gmain.c:3901
#4  0x7fa3076e4c5b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fa2e40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#5  0x7fa30769079a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fa2efffecf0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7fa3074c9f2c in QThread::exec() (this=this@entry=0xe2a0c0) at
thread/qthread.cpp:503
#7  0x7fa30a7daf35 in QQmlThreadPrivate::run() (this=0xe2a0c0) at
/usr/src/debug/qtdeclarative-opensource-src-5.6.0/src/qml/qml/ftw/qqmlthread.cpp:141
#8  0x7fa3074ceb29 in QThreadPrivate::start(void*) (arg=0xe2a0c0) at
thread/qthread_unix.cpp:340
#9  0x7fa3065db454 in start_thread (arg=0x7fa2e700) at
pthread_create.c:333
#10 

[kcharselect] [Bug 298010] Missing Unicode blocks; ordering should be improved

[Chris via KDE Bugzilla]

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

Chris  changed:

   What|Removed |Added

 CC||emailofch...@gmail.com

--- Comment #16 from Chris  ---
KCharSelect is pretty out of date, it's too bad. It also needs emoji support,
which GNOME Character Map has. I feel strange using gucharmap on my Plasma
desktop, but it's my only option right now.

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

[krunner] [Bug 363421] New: krunner crash/restart when starting iceweasel from alt-F2

[Arthur Marsh via KDE Bugzilla]

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

Bug ID: 363421
   Summary: krunner crash/restart when starting iceweasel from
alt-F2
   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:
After restarting lxdm and the plasma session following library upgrades,
krunner crashed when successfully starting iceweasel.

-- 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 0x7f3c06def7c0 (LWP 29246))]

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

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

Thread 10 (Thread 0x7f3bfb6c0700 (LWP 29254)):
#0  0x0030004dbdad in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x003002c8d740 in g_wakeup_acknowledge (__nbytes=16,
__buf=0x7f3bfb6bfbe0, __fd=) at
/usr/include/x86_64-linux-gnu/bits/unistd.h:44
#2  0x003002c8d740 in g_wakeup_acknowledge (wakeup=0x7f3c15b0) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gwakeup.c:210
#3  0x003002c49e84 in g_main_context_check
(context=context@entry=0x7f3bf4000990, max_priority=2147483647,
fds=fds@entry=0x7f3bf4003070, 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=0x7f3bf4000990, 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=0x7f3bf4000990,
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=0x7f3bf40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#7  0x003017683daa in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f3bfb6bfde0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#8  0x0030174a0864 in QThread::exec() (this=) at
thread/qthread.cpp:503
#9  0x0030556d5105 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#10 0x0030174a580e in QThreadPrivate::start(void*) (arg=0x275b9c0) at
thread/qthread_unix.cpp:331
#11 0x003000c07454 in start_thread (arg=0x7f3bfb6c0700) at
pthread_create.c:334
#12 0x0030004e8e5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7f3bf11f6700 (LWP 29393)):
#0  0x003000c0d04f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x0030174a6aab in QWaitCondition::wait(QMutex*, unsigned long)
(time=18446744073709551615, this=0x25be770) at
thread/qwaitcondition_unix.cpp:136
#2  0x0030174a6aab in QWaitCondition::wait(QMutex*, unsigned long)
(this=, mutex=0x257ffe0, time=18446744073709551615) at
thread/qwaitcondition_unix.cpp:208
#3  0x7f3bf94c1dbf in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7f3bf94c5fe8 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7f3bf94c0f8d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at

[ksysguard] [Bug 363420] New: After ending a process, selection jumps to top of list.

[via KDE Bugzilla]

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

Bug ID: 363420
   Summary: After ending a process, selection jumps to top of
list.
   Product: ksysguard
   Version: 5.6.4
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: ksysguard
  Assignee: ksysguard-b...@kde.org
  Reporter: lnx...@westlot.net

After a process is killed, the process list and selection jumps back to the top
of the list.

Reproducible: Always

Steps to Reproduce:
1. Scroll down to process you want to kill.
2. Select (highlight) process.
3. Right click and end process any way allowed (end or select signal)

Actual Results:  
Process is ended as expected and view is moved back to the top of the list and
first process listed is selected (highlighted).

Expected Results:  
Process is ended as expected and view remains at current position with either
next or previous process in list selected (either is acceptable).

This is annoying, as I always want to make sure the process was killed.  Every
time I use ksysguard, I have to scroll back down, sometimes way down, to make
sure the process ended properly.

This has been going on for quite some time now, but if I recall correctly,
ksysguard used to not jump back to the top like this.

I'm setting this to Major severity as it's a major PITA every time I use
ksysguard.

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

[unknown] [Bug 363419] New: "Reached target shutdown" message seen, but laptop won't turn off, just hangs and needs the pc's button.

[Ego via KDE Bugzilla]

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

Bug ID: 363419
   Summary: "Reached target shutdown" message seen, but laptop
won't turn off, just hangs and needs the pc's button.
   Product: unknown
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: eliodise...@gmail.com

This is about a fresh Kubuntu 16.04 install on a new laptop (asus x540sa).
After pressing the shutdown button in the start menu; the shutdown procedure
starts and in the final splash screen the system just hangs. Tried a second
time by pressing Esc once the splash screen showed up and I saw that it reaches
the line "Reached target shutdown" and just stops there, no matter how long I
leave it there the machine won't turn off.

I also tried an Ubuntu 16.04 fresh install on the same machine and it hanged
too at the final splash screen where the moving dots stopped. Then I tried with
Esc only to see the exact same line in the end.

The issue seems to affect lately quite many users as shown by the google
results of the past month / week or so.

I have also tried shutting down from the console with shutdown -and all the
parameters after that suggested online- and sudo poweroff but unfortunately
they didn't do the trick. The exact same situation occurred.

Unmounting the swap as suggested online doesn't work.

Also rebooting the system is not working either due to the same issue.

So right now the only way for me to poweroff the machine is to press the power
button on the keyboard continuously.

Reproducible: Always

Steps to Reproduce:
1.Install OS
2.Do something, anything
3.Try to shutdown or reboot

Actual Results:  
The computer is not shutting down: "Reached target shutdown" and hangs there.

Expected Results:  
Powering off the machine.

For what it's worth, losing the lid won't suspend the system, but using the
menu button for suspension will do it.

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

[knode] [Bug 363410] knode doesn't respect X-Archive:encrypt in the header

[Peter Gückel via KDE Bugzilla]

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

--- Comment #1 from Peter Gückel  ---
I think this is probably not a bug.

I notice that when I post to fedora.testers, my address appears in cleartext,
but when I post to fedora.kde, it is encrypted !!!

Explain, please.

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

[konqueror] [Bug 363378] css background shorthand parser error

[Michael Pyne via KDE Bugzilla]

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

--- Comment #4 from Michael Pyne  ---
Actually never mind. I'm not sure what seemed to break this but it's happening
before your changes were merged in so I don't think it's that.

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

[konqueror] [Bug 363378] css background shorthand parser error

[Michael Pyne via KDE Bugzilla]

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

Michael Pyne  changed:

   What|Removed |Added

 CC||mp...@kde.org

--- Comment #3 from Michael Pyne  ---
Can you double-check that this change it doesn't break other valid CSS? For
instance the test case given in Mozilla's developer notes for
background-position breaks even after I revert my proposed changes to the CSS
parser. See
https://developer.mozilla.org/en-US/docs/Web/CSS/background-position, the
output was working in previous KHTML commits.

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

коррупционные правонарушения

[Артём]

Уважаемые коллеги! актуальные вопросы проверки деловых партнеров, бизнес 
разведки и экономической безопасности.


деловая разведка.PDF
Description: Binary data

[krunner] [Bug 363418] New: krunner

[Martin Ferros via KDE Bugzilla]

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

Bug ID: 363418
   Summary: krunner
   Product: krunner
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: m...@vhanda.in
  Reporter: loos...@gmail.com

Application: krunner (5.5.5)

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

-- Information about the crash:
- What I was doing when the application crashed:
open yasts, when i open aplications sometimes krunner stop working

The crash can be reproduced sometimes.

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

Thread 20 (Thread 0x7f9ce7e72700 (LWP 1473)):
#0  0x7f9cf7f25bbd in poll () at /lib64/libc.so.6
#1  0x7f9cf742e422 in  () at /usr/lib64/libxcb.so.1
#2  0x7f9cf743000f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f9cea5f53c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f9cf862032f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f9cf5fbc0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f9cf7f2dfed in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7f9cd9c49700 (LWP 1487)):
#0  0x7f9cf7f25bbd in poll () at /lib64/libc.so.6
#1  0x7f9cf5421e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f9cf5421f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f9cf8852d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f9cf87f9d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f9cf861b61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f9cfaf1de18 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f9cf862032f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f9cf5fbc0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f9cf7f2dfed in clone () at /lib64/libc.so.6

Thread 18 (Thread 0x7f9cc380e700 (LWP 17560)):
#0  0x7f9cf5fc003f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f9cf862134b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f9cd27f165f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f9cd27f543a in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f9cd27ef6cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f9cd27f3005 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f9cf862032f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f9cf5fbc0a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7f9cf7f2dfed in clone () at /lib64/libc.so.6

Thread 17 (Thread 0x7f9cc300d700 (LWP 17561)):
#0  0x7f9cf5fc003f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f9cf862134b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f9cd27f165f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f9cd27f543a in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f9cd27ef6cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f9cd27f5481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f9cd27ef6cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7f9cd27f3005 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7f9cf862032f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f9cf5fbc0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f9cf7f2dfed in clone () at /lib64/libc.so.6

Thread 16 (Thread 0x7f9cc280c700 (LWP 17562)):
#0  0x7f9cf5fc003f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f9cf862134b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f9cd27f165f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f9cd27f543a in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f9cd27ef6cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f9cd27f5481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f9cd27ef6cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7f9cd27f3005 in ThreadWeaver::Thread::run() () at

[Baloo] [Bug 363417] New: Baloo crashes with Dolphin and Amarok

[magpiper via KDE Bugzilla]

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

Bug ID: 363417
   Summary: Baloo crashes with Dolphin and Amarok
   Product: Baloo
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: m...@vhanda.in
  Reporter: magpi...@gmail.com
CC: pinak.ah...@gmail.com

Application: baloo_file (5.21.0)
 (Compiled from sources)
Qt Version: 5.5.1
Operating System: Linux 4.1.20-11-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
Preview images of graphic files. Often when orgainizing files within Amarok

The crash can be reproduced sometimes.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation
fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5481638780 (LWP 1921))]

Thread 2 (Thread 0x7f533662a700 (LWP 9808)):
#0  0x7f547f143c8d in read () from /lib64/libc.so.6
#1  0x7f547bbc7b60 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f547bb86999 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f547bb86df8 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7f547bb86f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f547fd75d8b in QEventDispatcherGlib::processEvents
(this=0x7f5330002d30, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#6  0x7f547fd1cd53 in QEventLoop::exec (this=this@entry=0x7f5336629d20,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#7  0x0041531b in Baloo::FileContentIndexer::run (this=0x193a160) at
/usr/src/debug/baloo-5.21.0/src/file/filecontentindexer.cpp:73
#8  0x7f547fb40382 in QThreadPoolThread::run (this=0x1b733b0) at
thread/qthreadpool.cpp:93
#9  0x7f547fb4332f in QThreadPrivate::start (arg=0x1b733b0) at
thread/qthread_unix.cpp:331
#10 0x7f547e1820a4 in start_thread () from /lib64/libpthread.so.0
#11 0x7f547f14ffed in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f5481638780 (LWP 1921)):
[KCrash Handler]
#6  0x7f547ce7225c in mdb_get (txn=0x7f547fb8e0c8
, dbi=7, key=0x7ffddf874920,
data=0x7ffddf874930) at mdb.c:5286
#7  0x7f54804114cd in Baloo::IdTreeDB::get (this=this@entry=0x7ffddf8749a0,
docId=docId@entry=0) at /usr/src/debug/baloo-5.21.0/src/engine/idtreedb.cpp:82
#8  0x7f548040edc0 in Baloo::DocumentUrlDB::getId
(this=this@entry=0x7ffddf874a10, docId=0, fileName=...) at
/usr/src/debug/baloo-5.21.0/src/engine/documenturldb.cpp:186
#9  0x7f5480420949 in Baloo::Transaction::documentId
(this=this@entry=0x7ffddf874a90, path=...) at
/usr/src/debug/baloo-5.21.0/src/engine/transaction.cpp:121
#10 0x0041d453 in Baloo::MetadataMover::removeMetadata
(this=this@entry=0x197c340, tr=tr@entry=0x7ffddf874a90, url=...) at
/usr/src/debug/baloo-5.21.0/src/file/metadatamover.cpp:74
#11 0x0041de02 in Baloo::MetadataMover::moveFileMetadata
(this=0x197c340, from=..., to=...) at
/usr/src/debug/baloo-5.21.0/src/file/metadatamover.cpp:53
#12 0x7f547fd4e73f in call (a=0x7ffddf874c00, r=0x7ffddf875360,
this=0x194b7c0) at ../../src/corelib/kernel/qobject_impl.h:124
#13 QMetaObject::activate (sender=sender@entry=0x1983fe0,
signalOffset=, local_signal_index=local_signal_index@entry=7,
argv=argv@entry=0x7ffddf874c00) at kernel/qobject.cpp:3698
#14 0x7f547fd4f2e7 in QMetaObject::activate (sender=sender@entry=0x1983fe0,
m=m@entry=0x638bc0 ,
local_signal_index=local_signal_index@entry=7, argv=argv@entry=0x7ffddf874c00)
at kernel/qobject.cpp:3578
#15 0x0041e75a in KInotify::moved (this=this@entry=0x1983fe0, _t1=...,
_t2=...) at /usr/src/debug/baloo-5.21.0/build/src/file/moc_kinotify.cpp:330
#16 0x004228f9 in KInotify::slotEvent (this=,
socket=) at
/usr/src/debug/baloo-5.21.0/src/file/kinotify.cpp:421
#17 0x7f547fd4e73f in call (a=0x7ffddf874ec0, r=0x1983fe0, this=0x1958700)
at ../../src/corelib/kernel/qobject_impl.h:124
#18 QMetaObject::activate (sender=sender@entry=0x1954190,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7ffddf874ec0) at kernel/qobject.cpp:3698
#19 0x7f547fd4f2e7 in QMetaObject::activate (sender=sender@entry=0x1954190,
m=m@entry=0x7f548016d780 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffddf874ec0)
at kernel/qobject.cpp:3578
#20 0x7f547fdd08ee in QSocketNotifier::activated
(this=this@entry=0x1954190, _t1=13) at .moc/moc_qsocketnotifier.cpp:134
#21 0x7f547fd5ba89 in QSocketNotifier::event (this=0x1954190,
e=0x7ffddf875030) at kernel/qsocketnotifier.cpp:260
#22 0x7f547fd1f18d in QCoreApplication::notify (this=,
receiver=, event=) at
kernel/qcoreapplication.cpp:1038
#23 0x7f547fd1ee95 in QCoreApplication::notifyInternal
(this=0x7ffddf8752d0, 

[krita] [Bug 363416] New: *Sometimes* crashes on loading files via drag and drop

[Lake via KDE Bugzilla]

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

Bug ID: 363416
   Summary: *Sometimes* crashes on loading files via drag and drop
   Product: krita
   Version: 3.0 Release Candidate
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: File formats
  Assignee: krita-bugs-n...@kde.org
  Reporter: winter.w...@yahoo.com

Windows 7

Dragging and dropping a file from my pictures directory window (IE browser)
causes a crash immediately after the file is loaded. All the .jpgs and .pngs I
have tried work (and I tried a bunch of them), but I have had crashes trying to
open .xcf .psd and .kra . One of the files that caused a crash was a Krita
auto-generated autosave file. Nearly every file that has caused a crash has
also, at a different time, been opened successfully via this method. One of the
.psd files that caused a crash was only 196KB (and no other files were open in
Krita).

Problem signature:
  Problem Event Name:APPCRASH
  Application Name:krita.exe
  Application Version:0.0.0.0
  Application Timestamp:0409
  Fault Module Name:libkritalibbrush.dll
  Fault Module Version:0.0.0.0
  Fault Module Timestamp:00d388c0
  Exception Code:c005
  Exception Offset:8e00
  OS Version:6.1.7601.2.1.0.256.48
  Locale ID:1033
  Additional Information 1:0a9e
  Additional Information 2:0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:0a9e
  Additional Information 4:0a9e372d3b4ad19135b953a78882e789

Reproducible: Sometimes

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

[KScreen] [Bug 356884] kscreen messes with original xrandr config, does not respect saved config, and apply defined config only on the second try.

[via KDE Bugzilla]

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

slartibar...@gmail.com changed:

   What|Removed |Added

 CC||slartibar...@gmail.com

--- Comment #21 from slartibar...@gmail.com ---
same here with nvidia card and 2 monitors (dvi, hdmi).
Suggested workaround of Allan does indeed work

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

[Discover] [Bug 363392] The GUI is always misbehaving

[Aleix Pol via KDE Bugzilla]

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

--- Comment #3 from Aleix Pol  ---
Thank you :) feel free to direct them to me or this bug report if there's any
questions.

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

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

[Lake via KDE Bugzilla]

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

Bug ID: 363415
   Summary: (File) Toolbar doesn't display correctly
   Product: krita
   Version: 3.0 Release Candidate
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: winter.w...@yahoo.com

Adding "Reset Zoom" to the (file) toolbar results in an invisible button being
added to the toolbar. It still works, but it is a blank square now. Also the
option to change the text of a toolbar item is gone now (maybe on purpose?).

I should also mention that, after installing 3.0 , I went to reconfigure my
toolbar (it had been reset) but I couldn't remember that "reset toolbar" was
the one I wanted; so I added everything that sounded like it might work. A lot
of the buttons came up as invisible square spaces on the toolbar, and - despite
there being enough room on my toolbar - it seemed that some of the buttons
didn't even get placed in the toolbar.

I felt a little bad, finding so many bugs when you guys are so close to
release; I considered just ignoring it; but in the end, I'm not helping by
keeping it to myself. So: here it is and best of luck on the release!

Reproducible: Always

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

[Discover] [Bug 363392] The GUI is always misbehaving

[Marco via KDE Bugzilla]

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

--- Comment #2 from Marco  ---
(In reply to Aleix Pol from comment #1)
> This issue has been fixed, please ask Kubuntu to release the latest stable
> packages.

Thank you, I requested this to the kubuntu team in launchpad.

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

[krita] [Bug 363414] New: Assistants refuse to be moved/viewed/made

[Lake via KDE Bugzilla]

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

Bug ID: 363414
   Summary: Assistants refuse to be moved/viewed/made
   Product: krita
   Version: 3.0 Release Candidate
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Tools
  Assignee: krita-bugs-n...@kde.org
  Reporter: winter.w...@yahoo.com

I just had a strange error involving the assistant tool in the release
candidate:
I sketched on the canvas (7 layers) and then placed two vanishing points.
Unhappy with their placement, I attempted to move them by grabbing their little
dotted feet and then their nifty new label, but nothing worked. Placing new
vanishing points no longer worked, either. Curious, I took out the infinite
ruler assistant and tried to place it in many places - but the only place it
worked was on the lower left hand quadrant (pretty far from the two vanishing
points). I managed to place another there, but I still could not place more in
the upper right  quadrant. It was the same with the ellipse assistant, until I
placed the first part in the lower part and the next point in the upper
portion. After that, the assistants seemed to reset and now I have a big mess
of them on my screen and can move them. Drawing on the screen is not creating
any noticeable errors, but somehow during this my canvas has doubled in size to
the right! I recently posted another error regarding assistants at
https://bugs.kde.org/show_bug.cgi?id=363385 , so I am assuming they are
related, but I don't know what's going on.

Good luck!

Reproducible: Didn't try

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

[systemsettings] [Bug 363413] New: although setting "switching control"=Desktop, remembers layout through different activities

[Herr Schmidt via KDE Bugzilla]

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

Bug ID: 363413
   Summary: although setting "switching control"=Desktop,
remembers layout through different activities
   Product: systemsettings
   Version: 5.4.3
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: wettererschein...@bb-goettingen.de

I want to have two activities A and B. A has with several Desktops / virtual
workspaces (Arbeitsflächen), each one using a certain keyboard layout.
Activity B should only have one workspace/Desktop containing a certain set of
Plasma widgets+Software and should have a certain fixed keyboard layout.

First Problem:
Workspaces and activities seem both to be global: Whenever I change the amount
and settings of Workspaces while in A, after switching to B I will find the
changed number and settings as well. Result is, that I will always keep the
last keyboard layout from the workspace I used last in A.

Second problem:
This is confusing especially as it is possible to make the workspaces in B look
different than those in A (like wallpaper) without changing something in A.
This provokes the assumption, that the activities are autonomous regarding  the
workspaces as well. But in truth it seems to be a mixup of
B-workspaces-settings and global/A-workspaces settings. This is not intuitive.
Especially as there are different ways of changing something about the
workspaces which is not selfexplaining.
I don't understand, wether the workspaces in A are the same instances like
those in B or not. 

Reproducible: Always



Expected Results:  
I would expect the activities to be autonomous regarding workspaces and
keyboard layouts as well (unless I choose the option: global).

Regarding the system settings I would expect the setting to be visually devided
by activity. E.g. in KSystemsettings>Workspaces a switch on top where you can
switch to which activity the settings should apply.

And I would expect to keep the last used keyboard layout inside a specific
workspace in B when I switch from A to B.

Thanks for your great work!

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

[digikam] [Bug 363412] New: Tree structure is not getting read

[Frank Hommes via KDE Bugzilla]

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

Bug ID: 363412
   Summary: Tree structure is not getting read
   Product: digikam
   Version: 5.0.0
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Metadata
  Assignee: digikam-de...@kde.org
  Reporter: frea...@gmx.net

There are very few of my files where the tree structure is not read by digikam.
There are 3 tags on one file. The structure is right with two of them but not
with the 3rd.
I checked, that the right data is saved in the files with exiftools.
It happens with a tag which looks like this:
Last Keyword XMP: Tätigkeit/Feierlichkeiten/Weihnachten/1. Weihnachtsfeiertag
Categories: TätigkeitFeierlichkeitenWeihnachten1.
Weihnachtsfeiertag
Tags List: Tätigkeit/Feierlichkeiten/Weihnachten/1. Weihnachtsfeiertag
Hierarchical Subject: Tätigkeit|Feierlichkeiten|Weihnachten|1.
Weihnachtsfeiertag
Catalog Sets: Tätigkeit|Feierlichkeiten|Weihnachten|1. Weihnachtsfeiertag
Subject: 1. Weihnachtsfeiertag
Keywords: 1. Weihnachtsfeiertag

In DIgikam it's just shown as:
Tags/1/Weihnachtsfeiertag

Can reproduce it with DIgikam 4.12 and digikam 5.0 beta 6.

Reproducible: Always

Steps to Reproduce:
1. Read the image file...
2.
3.

Actual Results:  
Tags/1/Weihnachtsfeiertag

Expected Results:  
Tags/ Tätigkeit/Feierlichkeiten/Weihnachten/1. Weihnachtsfeiertag

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

[frameworks-kinit] [Bug 358813] kdeinit5 crash after logout

[Alexander Miroshnichenko via KDE Bugzilla]

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

--- Comment #11 from Alexander Miroshnichenko  ---
$ echo $DISPLAY
:0

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

[digikam] [Bug 361922] Data lost

[via KDE Bugzilla]

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

Version|unspecified |5.0.0

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

[digikam] [Bug 361922] Data lost

[via KDE Bugzilla]

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
 CC||caulier.gil...@gmail.com
   Version Fixed In||5.0.0

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

[kontact] [Bug 363411] New: Kmail crashed when printing a mail

[Pim Bollen via KDE Bugzilla]

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

Bug ID: 363411
   Summary: Kmail crashed when printing a mail
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: kdebugzi...@tuxpower.nl

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

-- Information about the crash:
- What I was doing when the application crashed:
Printed a mail, printing succeede but kmail (kontact) crashed.

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc8c2cd5800 (LWP 2091))]

Thread 9 (Thread 0x7fc8a3b18700 (LWP 2158)):
#0  0x7fc8ba2ab03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc8bda51686 in WTF::TCMalloc_PageHeap::scavengerThread() () at
/usr/lib64/libQtWebKit.so.4
#2  0x7fc8bda516b9 in  () at /usr/lib64/libQtWebKit.so.4
#3  0x7fc8ba2a70a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fc8c023400d in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7fc8a3217700 (LWP 2438)):
#0  0x7fc8ba2ab03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc8bd7c3e7d in JSC::BlockAllocator::blockFreeingThreadMain() () at
/usr/lib64/libQtWebKit.so.4
#2  0x7fc8bda791e6 in WTF::wtfThreadEntryPoint(void*) () at
/usr/lib64/libQtWebKit.so.4
#3  0x7fc8ba2a70a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fc8c023400d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7fc84aa75700 (LWP 3392)):
#0  0x7fc8c022bbdd in poll () at /lib64/libc.so.6
#1  0x7fc8b9cdbbe4 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fc8b9cdbcec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fc8c09af0de in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#4  0x7fc8c0980e6f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#5  0x7fc8c0981165 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7fc8c087e0bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x7fc8c088079f in  () at /usr/lib64/libQtCore.so.4
#8  0x7fc8ba2a70a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fc8c023400d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7fc83a295700 (LWP 3533)):
#0  0x7fc8ba2ab03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc83a2fcd79 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#2  0x7fc83a2fd819 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#3  0x7fc8ba2a70a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fc8c023400d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7fc839a94700 (LWP 3534)):
#0  0x7fc8ba2ab03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc83a2fcd79 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#2  0x7fc83a2fd819 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#3  0x7fc8ba2a70a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fc8c023400d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7fc839293700 (LWP 3535)):
#0  0x7fc8ba2ab03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc83a2fcd79 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#2  0x7fc83a2fd819 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#3  0x7fc8ba2a70a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fc8c023400d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fc823fff700 (LWP 3539)):
#0  0x7fc8c0227cad in read () at /lib64/libc.so.6
#1  0x7fc8affb2f45 in  () at /usr/lib64/tls/libnvidia-tls.so.340.96
#2  0x7fc8b9d1c750 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fc8b9cdb714 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fc8b9cdbb7b in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7fc8b9cdbf0a in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0
#6  0x7fc82b345946 in  () at /usr/lib64/libgio-2.0.so.0
#7  0x7fc8b9d00b85 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7fc8ba2a70a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fc8c023400d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fc8237fe700 (LWP 3540)):
#0  0x7fc8c022bbdd in poll () at /lib64/libc.so.6
#1  0x7fc8b9cdbbe4 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fc8b9cdbcec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fc8b9cdbd29 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7fc8b9d00b85 in  () at /usr/lib64/libglib-2.0.so.0

[i18n] [Bug 363062] Wrong German translation of Levels menu item and dialog

[Frederik Schwarzer via KDE Bugzilla]

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

Frederik Schwarzer  changed:

   What|Removed |Added

 CC||schwar...@kde.org

--- Comment #1 from Frederik Schwarzer  ---
The problem is, that we do not have a domain expert in our team. I could now
fix the issues mentioned here (and I will in a week or two) but Krita could be
in a way better state, if some domain expert would join the joys of translating
KDE. :)

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

[knode] [Bug 363410] New: knode doesn't respect X-Archive:encrypt in the header

[Peter Gückel via KDE Bugzilla]

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

Bug ID: 363410
   Summary: knode doesn't respect X-Archive:encrypt in the header
   Product: knode
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: pguec...@gmail.com

Using knode-4.14.10-24.fc24 on Fedora 24

In past versions (fedora 23, 22 etc) I used to put X-Archive : encrypt into the
header configuration under posting news in the program setup. I don't know
about other news servers, but gmane supports this header and encrypts the email
address.

Now, in Fedora 24, the email address is no longer encrypted. The X-Face, also
entered in the header configuration section, is, however, honoured.

I have checked the gmane site and there is no mention that this feature is no
longer supported; to the contrary, they have a page indicating this feature.

It seems to me that there is something in knode that no longer allows email
encryption.

Reproducible: Always

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

[digikam] [Bug 361922] Data lost

[via KDE Bugzilla]

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

--- Comment #1 from swatilodh...@gmail.com ---
This issue is no more reproducible. Data retains on switching between SQLite
and MySQL.

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

[marble] [Bug 324872] Position Marker configurator won't save colors

[Tom Hardy via KDE Bugzilla]

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

--- Comment #2 from Tom Hardy  ---
Still there using version 1.12.20 (1.13 development version) under frameworks.

Can anyone either confirm or give it worksforme?

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

[kmail2] [Bug 346390] Cannot add list of contacts to BCC in mail

[via KDE Bugzilla]

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

marian.trenkwal...@gmail.com changed:

   What|Removed |Added

 CC||marian.trenkwal...@gmail.co
   ||m

--- Comment #11 from marian.trenkwal...@gmail.com ---
I can confirm this buggy behaviour on KMail Version 5.1.3.

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

[krita] [Bug 362948] [PERITAB] Krita crashes if I touch the tablet with the pen

[Sarah via KDE Bugzilla]

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

--- Comment #9 from Sarah  ---
Created attachment 99139
  --> https://bugs.kde.org/attachment.cgi?id=99139=edit
Krita debug file when attempting to use Trust Tablet TB7300

Krita debug file when attempting to use Trust Tablet TB7300 on latest 3.0
release. Thanks! <3 :D

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

[krita] [Bug 362948] [PERITAB] Krita crashes if I touch the tablet with the pen

[Sarah via KDE Bugzilla]

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

Sarah  changed:

   What|Removed |Added

 CC||slg...@hotmail.co.uk

--- Comment #8 from Sarah  ---
(In reply to Boudewijn Rempt from comment #7)
> Okay, so you didn't get a backtrace when testing the -dbg build?

Hello.  I think I have the same sort of problem. I use a Trust TB7300 (so old
it's not even sold anymore but old faithful still works! But I understand you
probably might not be able to do testing yourself <3) 

It didn't work on 2.7-2.9 releases but the Version: 3.1 Alpha (git be 28b 1b)
it works! YAY! I tried the most recent 'bleeding' release announced on FB
18/05/16. Again it works fine until I touch the pen to the tablet whereupon
Krita immediately crashes. My partner found out how to do a bug report and I
will attach it to this message just as soon as I work out how to.

Thanks for making such a wonderful art programme which has meant I can pursue
my hobby btw! It really is wonderful!

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

[kmail2] [Bug 362579] Segfault when selecting multiple adresses from contact list

[via KDE Bugzilla]

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

marian.trenkwal...@gmail.com changed:

   What|Removed |Added

 CC||marian.trenkwal...@gmail.co
   ||m

--- Comment #1 from marian.trenkwal...@gmail.com ---
Created attachment 99138
  --> https://bugs.kde.org/attachment.cgi?id=99138=edit
backtrace

I have this bug too. But only if I select multiple contacts from a Group.

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

[Akonadi] [Bug 362699] Back end MySQL table PimItemTable shows entries with remoteID = NULL

[Christoph Pospiech via KDE Bugzilla]

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

--- Comment #2 from Christoph Pospiech  ---
I just observed another 5 occurrences of RemoteID = NULL. I did some forensic
analysis. Hopefully the following observations help to pin down the problem.
1. Since I am running the akonadi database with my own MySQL server, I could
use phpMyAdmin to do some queries, starting from "SELECT * FROM `pimitemtable`
WHERE `remoteId` is NULL;"
I found that all these entries had a collectionID pointing to the trash can.
2. Apparently they were created by moving entries from an IMAP trash can to the
main trash can. The IMAP server was davmail 4.7.1-2416-1, used as an interface
to outlook.
3. There were three more entries put to the trash can by Kmail directly
- these had a non-NULL RemoteID.
4. Emptying the trash can made the entries with RemoteID = NULL go away
(no surprise, given what I said before).
5. I had a more emails in outlook that I could dispose. I repeated the
following experiment two times.
a. Inside outlook (running in a Win7 VM), put these emails into trash (one or
two at a time).
b. Wait for davmail to replicate the outlook trash into Kmail.
c. Run "SELECT * FROM `pimitemtable` WHERE `remoteId` is NULL;" and note the
result.
d. Move the emails from IMAP trash to main trash.
e. Rerun "SELECT * FROM `pimitemtable` WHERE `remoteId` is NULL;" and note the
difference.
=> One out of three emails disposed that way created a pimitemtable entry with
RemoteID = NULL.
=> This trash can scenario may not be the only one creating this effect. But it
is the least dangerous as these emails are to be disposed anyway - so no harm
done !

Hope this helps !
Christoph Pospiech

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

[kdenlive] [Bug 363032] git master: volume effect looses its setting when applied to track

[Riskable via KDE Bugzilla]

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

Riskable  changed:

   What|Removed |Added

 CC||riska...@youknowwhat.com

--- Comment #1 from Riskable  ---
I am also having this exact problem.  Super easy to reproduce...  Just try
using the keyframe feature on the volume effect to add a bunch of keyframes and
then move them around after re-selecting the track.  It'll get screwed up every
time.

Also, not sure if this is related but you used to be able to grab little
handles on the track itself to control the volume of keyframes (each keyframe
got a handle).  That seems to be missing in the latest development version as
of 5/22/2016.

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

[krita] [Bug 358147] Crash when trying to open or create a file

[Lake via KDE Bugzilla]

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

--- Comment #10 from Lake  ---
Build krita-3.0-RC-1-master-c9522ba-x86 works like a charm. Nice job!

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

[krita] [Bug 363385] Assistant tool doesn't turn invisible, calculates incorrectly.

[Lake via KDE Bugzilla]

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

--- Comment #2 from Lake  ---
I used the terms "perspective assistants" and "perspective points" but I am
referring to the "vanishing point" tool. Sorry if that made the post a little
unclear. Tested it with the krita-3.0-RC-1-master-c9522ba-x86 build; it
persists.

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

[kdenlive] [Bug 363409] git master - a little cleanup on new tabs-on-top layout

[Jesse via KDE Bugzilla]

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

--- Comment #2 from Jesse  ---
Created attachment 99137
  --> https://bugs.kde.org/attachment.cgi?id=99137=edit
Proposed edited tabs.

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

[kdenlive] [Bug 363409] git master - a little cleanup on new tabs-on-top layout

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

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

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

[kdenlive] [Bug 363409] New: git master - a little cleanup on new tabs-on-top layout

[Jesse via KDE Bugzilla]

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

Bug ID: 363409
   Summary: git master - a little cleanup on new tabs-on-top
layout
   Product: kdenlive
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: jesse.dub...@gmail.com

I really like that the tabs are on top. Looks super nice! I'd noticed, though,
that the dividing lines seem somewhat unorganized or flush together. I made a
mock-up of what it currently is, and what I might suggest adjusting it to.

Reproducible: Always




Suggestion made while using Kdenlive 16.07.70 master git build from
ppa:kdenlive/kdenlive-master.

Kubuntu 16.04 x64, plasma desktop 5.6.4

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

[kdenlive] [Bug 363409] git master - a little cleanup on new tabs-on-top layout

[Jesse via KDE Bugzilla]

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

--- Comment #1 from Jesse  ---
Created attachment 99136
  --> https://bugs.kde.org/attachment.cgi?id=99136=edit
Tabs as they currently are.

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

[Discover] [Bug 363392] The GUI is always misbehaving

[Aleix Pol via KDE Bugzilla]

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

Aleix Pol  changed:

   What|Removed |Added

 Resolution|--- |DOWNSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Aleix Pol  ---
This issue has been fixed, please ask Kubuntu to release the latest stable
packages.

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

[kolourpaint] [Bug 363353] version 4.14.1 No toolbar/toolbox

[Uli via KDE Bugzilla]

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

--- Comment #2 from Uli  ---
Thank you very much, Martin, for your help!

In the screenshot you can see that: instead of "settings" figure "No 
text". Anyway, "toolbars shown" is available, and the toolbox is checked.

In the SoftwareManager, a review said, after installing kdelibs-bin, and 
2 more kdelibs5 packages, KolourPaint was finally running!
I tried this, and the menu figured no longer "No text".

Strange: if you get KolourPaint from Linux Mint 13, you gotta download 
almost 70 MBytes, but if you get it from Linux Mint 17, it's just 5 MB!
So, with Synaptic Package Manager I installed most of the packages 
required from Mint 13, and now everything works fine!!!

Conclusion: This appears to be a bug of KolourPaint, but it isn't.
It is a bug of Synaptic Package Manager or Mint 17; it just does not 
install enough packages in Mint 17 for KolourPaint.


On 05/21/2016 01:02 AM, Martin Koller via KDE Bugzilla wrote:
> https://bugs.kde.org/show_bug.cgi?id=363353
>
> Martin Koller  changed:
>
> What|Removed |Added
> 
>   Status|UNCONFIRMED |RESOLVED
>   Resolution|--- |FIXED
>   CC||kol...@aon.at
>
> --- Comment #1 from Martin Koller  ---
> Use Menu -> Settings -> Toollbars Shown and check "Tool Box"
>

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

[kate] [Bug 363406] 64-bit kate installs in 'Program Files (x86)' (reserved for 32-bit programs)

[Kåre Särs via KDE Bugzilla]

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

Kåre Särs  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 CC||kare.s...@iki.fi
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Kåre Särs  ---
Thanks for the report.

Newer installers compiled from released tar files can be found here:
http://download.kde.org/unstable/kate/

If you install over an older installation somehow the installation directory
gets inherited from the old installation. Could that be the case here?

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

[kdenlive] [Bug 363408] New: Segfault when clicking "Analyse" in Auto Mask effect

[via KDE Bugzilla]

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

Bug ID: 363408
   Summary: Segfault when clicking "Analyse" in Auto Mask effect
   Product: kdenlive
   Version: 16.04.0
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: james.wilf...@gmail.com

Using kdenlive 16.04.1 from ppa.launchpad.net on kubuntu 16.04.

Steps to reproduce:

1. Add a clip
2. Add "Auto Mask" to the clip
3. Click "Analyse" button

Result: Segfault.

Backtrace obtained with gdb:

$ gdb kdenlive
GNU gdb (Ubuntu 7.11-0ubuntu1) 7.11
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from kdenlive...Reading symbols from
/usr/lib/debug/.build-id/6e/82e04389daf1b043946d780b15f36d63fde46a.debug...done.
done.
(gdb) run
Starting program: /usr/bin/kdenlive
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe33a4700 (LWP 8912)]
[New Thread 0x7fffc3bb4700 (LWP 8913)]
[New Thread 0x7fffbd06d700 (LWP 8914)]
[New Thread 0x7fffb7fff700 (LWP 8915)]
[New Thread 0x7fffb77fe700 (LWP 8916)]
Removing cache at "/home/james/.cache/kdenlive-thumbs.kcache"
[New Thread 0x7fffb5a9b700 (LWP 8917)]
[Thread 0x7fffb5a9b700 (LWP 8917) exited]
[New Thread 0x7fffb5a9b700 (LWP 8918)]
OpenGL vendor:  "Intel Open Source Technology Center"
OpenGL renderer:  "Mesa DRI Intel(R) Haswell Desktop "
OpenGL ARG_SYNC:  true
OpenGL OpenGLES:  false
[New Thread 0x7fffa7fff700 (LWP 8920)]
OpenGL vendor:  "Intel Open Source Technology Center"
OpenGL renderer:  "Mesa DRI Intel(R) Haswell Desktop "
OpenGL ARG_SYNC:  true
OpenGL OpenGLES:  false
[New Thread 0x7fffa77fe700 (LWP 8921)]
[New Thread 0x7fffa6ffd700 (LWP 8922)]
[New Thread 0x7fffa67fc700 (LWP 8923)]
[New Thread 0x7fffa5ffb700 (LWP 8924)]
QXcbConnection: XCB error: 8 (BadMatch), sequence: 30289, resource id:
60823908, major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 30315, resource id:
60823908, major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 30337, resource id:
60823908, major code: 130 (Unknown), minor code: 3
KSambaShare: Could not find smb.conf!
[New Thread 0x7fff8fffd700 (LWP 8926)]
[Thread 0x7fff8fffd700 (LWP 8926) exited]
[New Thread 0x7fff8fffd700 (LWP 8927)]
[Thread 0x7fff8fffd700 (LWP 8927) exited]
[New Thread 0x7fff8fffd700 (LWP 8928)]
[New Thread 0x7fff8e70f700 (LWP 8929)]
[New Thread 0x7fff8d696700 (LWP 8930)]
[New Thread 0x7fff8ce95700 (LWP 8931)]
[New Thread 0x7fff7bffe700 (LWP 8932)]
[New Thread 0x7fff7b7fd700 (LWP 8933)]
[New Thread 0x7fff7affc700 (LWP 8934)]
[New Thread 0x7fff7a7fb700 (LWP 8935)]
[Thread 0x7fff8fffd700 (LWP 8928) exited]
[Thread 0x7fff7bffe700 (LWP 8932) exited]
[Thread 0x7fff7b7fd700 (LWP 8933) exited]
[Thread 0x7fff7affc700 (LWP 8934) exited]
[Thread 0x7fff8ce95700 (LWP 8931) exited]
[Thread 0x7fff8d696700 (LWP 8930) exited]
[Thread 0x7fff8e70f700 (LWP 8929) exited]
Removing cache at "/home/james/.cache/kdenlive-thumbs.kcache"
 // / processing file open
 // / processing file open: validate
Opening a document with version  0.94  /  0.94
 // / processing file validate ok
[Thread 0x7fffa5ffb700 (LWP 8924) exited]
[Thread 0x7fffb5a9b700 (LWP 8918) exited]
[Thread 0x7fffa67fc700 (LWP 8923) exited]
[Thread 0x7fffa77fe700 (LWP 8921) exited]
[New Thread 0x7fffa77fe700 (LWP 8937)]
[Thread 0x7fffa77fe700 (LWP 8937) exited]
[New Thread 0x7fffa77fe700 (LWP 8938)]
[New Thread 0x7fffa67fc700 (LWP 8939)]
[New Thread 0x7fffb5a9b700 (LWP 8940)]
[New Thread 0x7fffa5ffb700 (LWP 8941)]
[New Thread 0x7fff95952700 (LWP 8942)]
[New Thread 0x7fff95151700 (LWP 8943)]
[New Thread 0x7fff94950700 (LWP 8944)]
[New Thread 0x7fff9014e700 (LWP 8945)]
[Thread 0x7fffa77fe700 (LWP 8938) exited]
[Thread 0x7fff9014e700 (LWP 8945) exited]
[Thread 0x7fffa67fc700 (LWP 8939) exited]
[New Thread 0x7fffa67fc700 (LWP 8946)]
[Thread 0x7fffa67fc700 (LWP 8946) exited]
[New Thread 0x7fffa67fc700 (LWP 8947)]
[New Thread 0x7fff9014e700 (LWP 8948)]
***
FOUND GUIDES:  0
**
"Creating audio thumbnails (1/1)"
[New Thread 0x7fffa77fe700 (LWP 8949)]
[Thread 0x7fffa67fc700 (LWP 8947) exited]
[Thread 

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

[Harald Sitter via KDE Bugzilla]

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

Harald Sitter  changed:

   What|Removed |Added

   Target Milestone|0.9 |4.8
   Assignee|sit...@kde.org  |dvra...@kde.org
 CC||romain.per...@gmail.com,
   ||sit...@kde.org,
   ||tdfisc...@kde.org
  Component|general |general
Product|phonon-backend-vlc  |phonon-backend-gstreamer

--- Comment #6 from Harald Sitter  ---
You aren't using the phonon vlc backend actually.

>From the debug output it looks a lot like what is happening is that this file:
> /home/user/Music/Tribal INK/Surrounded by Freaks/04 - Refugee.mp3
has bogus metadata such that the length is incorrectly detected which makes
gstreamer want to transition to the next source too late:
> PHONON-GST remaining time 320 
> PHONON-GST waiting for 0 
this ultimately means that gstreamer only realized the track is about to end
320 milliseconds before the actual end, which is not enough time for Amarok to
hand us the next source, which is why we didn't wait for the source. In the end
the lack of a new track triggered a change to stop, which happend concurrently
to amarok giving us the next source.

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

[plasmashell] [Bug 362692] Positioning of drop-down list in 'audio volume' incorrect

[via KDE Bugzilla]

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

--- Comment #2 from slartibar...@gmail.com ---
still there in 5.6.4,
using intel and nvidia graphics

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

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

[Thomas Pfeiffer via KDE Bugzilla]

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

Thomas Pfeiffer  changed:

   What|Removed |Added

 CC||thomas.pfeif...@kde.org
  Flags|VisualDesign+   |

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

[Touchpad-KCM] [Bug 362800] Touchpad setting "Disable taps and scrolling only" ignored

[Rajeesh K V via KDE Bugzilla]

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

Rajeesh K V  changed:

   What|Removed |Added

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

--- Comment #6 from Rajeesh K V  ---
You're welcome, Mark.
I think libinput is declared as feature complete. Libinput aims to simplify
input handling and a side-effect of it is providing good defaults instead of
making many configuration options available, which previous drivers like
synaptics did. You could try to contact libinput upstream if you'd like to
pursue further. Closing this report.

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

[kdenlive] [Bug 363407] Crashes on open project or include video in new project

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #1 from Jean-Baptiste Mardelle  ---
Where did you get your Kdenlive packages ? 
Can you check the Kdenlive version in Help > About Kdenlive > Version

For Ubuntu users, we recommand to use packages from our PPA, check:
https://kdenlive.org/download-ubuntu

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

[dolphin] [Bug 362045] Running dolphin from CLI (sudo dolphin) shows NO icons (folders, toolbar, or otherwise)!

[michael via KDE Bugzilla]

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

michael  changed:

   What|Removed |Added

 CC||reeves...@gmail.com

--- Comment #4 from michael  ---
The problem isn't specific to dolphin. Kate is also affected by this. It seems
to be related to the qt5/frameworks transition.

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

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

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #1 from Jean-Baptiste Mardelle  ---
Git commit 36f4ffbf05eddc991e6fb25006be1720c904112c by Jean-Baptiste Mardelle.
Committed on 22/05/2016 at 18:16.
Pushed by mardelle into branch 'master'.

Fix crash on loading title in Title Editor

M  +0-1src/titler/titledocument.cpp
M  +3-0src/titler/titlewidget.cpp

http://commits.kde.org/kdenlive/36f4ffbf05eddc991e6fb25006be1720c904112c

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

[kdenlive] [Bug 363407] New: Crashes on open project or include video in new project

[valentin via KDE Bugzilla]

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

Bug ID: 363407
   Summary: Crashes on open project or include video in new
project
   Product: kdenlive
   Version: 16.04.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: v...@yahoo.com

A project made in version 15.12.3 crashes on open on version 16.04. Trying to
include video in a new project crashes program as well.
Ubuntu 16.04, nvidia

Reproducible: Always

Steps to Reproduce:
1. open project
2. after few seconds program terminated abnormally before to load timeline,
etc.
3.

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

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

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

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

[kate] [Bug 363406] New: 64-bit kate installs in 'Program Files (x86)' (reserved for 32-bit programs)

[via KDE Bugzilla]

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

Bug ID: 363406
   Summary: 64-bit kate installs in 'Program Files (x86)'
(reserved for 32-bit programs)
   Product: kate
   Version: unspecified
  Platform: Windows CE
OS: MS Windows
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: 44thats44o...@gmail.com

The 64-bit version of kate (obtained from here:
ftp://kate-editor.org/haumann/Kate-2016.04-alpha_x86_64.exe) installs in
'C:\Program Files (x86)\Kate'. 'Program Files (x86)' is reserved for 32-bit/x86
programs, 64-bit programs just go in 'Program Files'.

Reproducible: Always

Steps to Reproduce:
Install the 64-bit version of kate on Windows
(ftp://kate-editor.org/haumann/Kate-2016.04-alpha_x86_64.exe)

Actual Results:  
Kate is installed in 'Program Files (x86)'

Expected Results:  
Kate should install in 'Program Files'

This version: ftp://kate-editor.org/haumann/Kate-setup-2016.04.24-dev.exe seems
to also be a 64-bit version of kate for Windows, though it installs in Program
Files (x86)\Kate\bin

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

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

[Frederik Schwarzer via KDE Bugzilla]

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

Frederik Schwarzer  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||schwar...@kde.org
 Status|UNCONFIRMED |CONFIRMED

--- Comment #7 from Frederik Schwarzer  ---
I uploaded the patch given in #3 to the reviewboard.
https://git.reviewboard.kde.org/r/127989/

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

[Touchpad-KCM] [Bug 362800] Touchpad setting "Disable taps and scrolling only" ignored

[Mark via KDE Bugzilla]

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

--- Comment #5 from Mark  ---
I apologize for double-posting in such quick succession but I wanted to report
that I replaced libinput with synaptics as you described and all is working as
expected again.  Thank you again for your assistance.  I suppose I'll keep an
eye on libinput's development and switch back again once these features are
supported.

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

[Touchpad-KCM] [Bug 362800] Touchpad setting "Disable taps and scrolling only" ignored

[Mark via KDE Bugzilla]

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

--- Comment #4 from Mark  ---
Thanks for such a fast response Rajeesh.  This may not be the best place to
ask, but is libinput in its feature-incomplete state not a suitable replacement
for the synaptics driver at this time?  I haven't yet tried using the synaptics
driver to work around my problem, but I'll try it and post the results.  Thank
you again for your help.

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

[kwin] [Bug 363079] artifacts, mostly seen with firefox and eclipse

[via KDE Bugzilla]

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

--- Comment #21 from je.joa...@yahoo.se ---
The effect seem to be mostly visible in the Windows, but sometimes the toolbar,
system watch and tray is also affected by it as well.

Regards,

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

[frameworks-baloo] [Bug 363377] baloo_file segmentation fault since upgrade to Kubuntu 16.04

[Alexander Potashev via KDE Bugzilla]

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

Alexander Potashev  changed:

   What|Removed |Added

Version|unspecified |5.18.0
 CC||aspotas...@gmail.com
Product|Baloo   |frameworks-baloo
  Component|General |Engine

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

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

[Frederik Schwarzer via KDE Bugzilla]

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

Frederik Schwarzer  changed:

   What|Removed |Added

 CC||oliverthe...@gmail.com

--- Comment #6 from Frederik Schwarzer  ---
*** Bug 363405 has been marked as a duplicate of this bug. ***

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

[kreversi] [Bug 363405] KReversi crashed on startup - symbols downloaded from launchpad for WW

[Frederik Schwarzer via KDE Bugzilla]

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

Frederik Schwarzer  changed:

   What|Removed |Added

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

--- Comment #1 from Frederik Schwarzer  ---


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

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

[frameworks-baloo] [Bug 363342] Baloo crashes when writing/generating file

[Alexander Potashev via KDE Bugzilla]

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

Alexander Potashev  changed:

   What|Removed |Added

Product|Baloo   |frameworks-baloo
  Component|General |general
 CC||aspotas...@gmail.com
Version|unspecified |5.16.0

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

[frameworks-kfilemetadata] [Bug 363299] Everytime after KDE loads, Baloo reports in tty1 that it exit normally, but then it crashes.

[Alexander Potashev via KDE Bugzilla]

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

Alexander Potashev  changed:

   What|Removed |Added

Product|Baloo   |frameworks-kfilemetadata
  Component|General |general
 CC||aspotas...@gmail.com
Version|unspecified |5.22.0

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

[kwin] [Bug 363079] artifacts, mostly seen with firefox and eclipse

[via KDE Bugzilla]

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

--- Comment #20 from je.joa...@yahoo.se ---
Have only seen the artifact when firefox and/or eclipse and/or "configure
desktop" windows are started. It is likely visible with more applications as
well, but these are for sure. Not 100% sure but think it has also occurred when
the KWallet popup was displayed directly after starting up.

In the video clip, the entire image is blurry for a short time because of the
camera focusing. But the other artifacts are as they appear on the display.

Have not yet seen the artifact when only the desktop is displayed and I can't
see it when firefox and eclipse are started but the windows are minimized.
Minimizing all the windows during an ongoing distortion seem to stop it.

Noticed also, that when minimizing there is sometimes some sort of ghosting
effect that is visible until that area of the display is repainted again. For
instance, moving mouse pointer or another window over it removes it. Added a
photo of this as well.

Yes touchpad is probably another issue.

Regards,

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

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

[via KDE Bugzilla]

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

object...@yandex.ru changed:

   What|Removed |Added

  Flags||VisualDesign+
 CC||object...@yandex.ru

--- Comment #25 from object...@yandex.ru ---
Same problem arch, plasma 5.6.4.
Fixible by using xf86-video-intel with mesa-libgl.

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

[kreversi] [Bug 363405] New: KReversi crashed on startup - symbols downloaded from launchpad for WW

[oliver stieber via KDE Bugzilla]

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

Bug ID: 363405
   Summary: KReversi crashed on startup - symbols downloaded from
launchpad for WW
   Product: kreversi
   Version: 2.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: i...@lysator.liu.se
  Reporter: oliverthe...@gmail.com
CC: kde-games-b...@kde.org

Application: kreversi (2.0)
KDE Platform Version: 4.14.13
Qt Version: 4.8.6
Operating System: Linux 4.2.0-34-generic x86_64
Distribution: Ubuntu 15.10

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

installed from synaptic
started kreversi from applications
crashed on startup

-- couldn't find debug sysbols, so searched for them on google and installed
from https://launchpad.net/ubuntu/+source/kreversi

-- Backtrace:
Application: KReversi (kreversi), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb228d52840 (LWP 1165))]

Thread 3 (Thread 0x7fb215685700 (LWP 1166)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fb224649b5a in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x7fb224649b89 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x7fb221b386aa in start_thread (arg=0x7fb215685700) at
pthread_create.c:333
#4  0x7fb225df5e9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fb194263700 (LWP 1167)):
#0  0x7fb2214a7869 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fb221462789 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fb22146311b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb2214632fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fb2272e720e in QEventDispatcherGlib::processEvents
(this=0x7fb18c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#5  0x7fb2272b50d1 in QEventLoop::processEvents
(this=this@entry=0x7fb194262d40, flags=...) at kernel/qeventloop.cpp:149
#6  0x7fb2272b5445 in QEventLoop::exec (this=this@entry=0x7fb194262d40,
flags=...) at kernel/qeventloop.cpp:204
#7  0x7fb2271a44f9 in QThread::exec (this=this@entry=0x201a330) at
thread/qthread.cpp:538
#8  0x7fb227295133 in QInotifyFileSystemWatcherEngine::run (this=0x201a330)
at io/qfilesystemwatcher_inotify.cpp:265
#9  0x7fb2271a6d1c in QThreadPrivate::start (arg=0x201a330) at
thread/qthread_unix.cpp:349
#10 0x7fb221b386aa in start_thread (arg=0x7fb194263700) at
pthread_create.c:333
#11 0x7fb225df5e9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fb228d52840 (LWP 1165)):
[KCrash Handler]
#6  QScopedPointer::data
(this=) at
../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:135
#7  qGetPtrHelper (p=...) at
../../include/QtCore/../../src/corelib/global/qglobal.h:2580
#8  QObject::d_func (this=) at
../../include/QtCore/../../src/corelib/kernel/qobject.h:115
#9  QObject::setProperty (this=0x0, name=name@entry=0x41da03
"isBoardShowingLabels", value=...) at kernel/qobject.cpp:3719
#10 0x00411e6f in KReversiView::updateBoard (this=this@entry=0x1fd9000)
at ../kreversiview.cpp:176
#11 0x004124a6 in KReversiView::setGame (this=this@entry=0x1fd9000,
game=game@entry=0x0) at ../kreversiview.cpp:75
#12 0x00412968 in KReversiView::KReversiView (this=0x1fd9000, game=0x0,
parent=, provider=) at ../kreversiview.cpp:45
#13 0x0041a513 in KReversiMainWindow::KReversiMainWindow
(this=0x1d96e70, parent=0x0, startDemo=, __in_chrg=, __vtt_parm=) at ../mainwindow.cpp:81
#14 0x0040e2ea in main (argc=, argv=) at
../main.cpp:64

Reported using DrKonqi

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

[kwin] [Bug 363079] artifacts, mostly seen with firefox and eclipse

[via KDE Bugzilla]

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

--- Comment #19 from je.joa...@yahoo.se ---
Created attachment 99134
  --> https://bugs.kde.org/attachment.cgi?id=99134=edit
When firefox is minimized, earlier frame from animation is still visible

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

[kmymoney4] [Bug 275043] Assignment of recipient by MEMO-Tag when importing data

[Jack via KDE Bugzilla]

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

--- Comment #1 from Jack  ---
Isn't this now possible?  Perhaps this bug was just missed when the feature was
added.

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

[korganizer] [Bug 359148] unable to add korganizer events to digital clock widget

[Karl Ove Hufthammer via KDE Bugzilla]

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

Karl Ove Hufthammer  changed:

   What|Removed |Added

 CC||k...@huftis.org

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

[kwin] [Bug 363079] artifacts, mostly seen with firefox and eclipse

[via KDE Bugzilla]

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

--- Comment #18 from je.joa...@yahoo.se ---
Created attachment 99133
  --> https://bugs.kde.org/attachment.cgi?id=99133=edit
xorg.0.log 20-intel.conf uxa

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

[plasmashell] [Bug 363230] The sound rises to the maximum in KDE to receive system notifications

[Aurelien Gateau via KDE Bugzilla]

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

Aurelien Gateau  changed:

   What|Removed |Added

  Component|general |Notifications
Product|colibri |plasmashell
   Target Milestone|--- |1.0
Version|unspecified |5.4.3
   Assignee|agat...@kde.org |mklape...@kde.org
 CC||plasma-b...@kde.org

--- Comment #1 from Aurelien Gateau  ---
This bug is not about Colibri, reassigning.

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

[konsole] [Bug 360010] Crash after running a script that runs konsole -e

[via KDE Bugzilla]

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

--- Comment #1 from ziri...@live.com ---
Created attachment 99132
  --> https://bugs.kde.org/attachment.cgi?id=99132=edit
New crash information added by DrKonqi

konsole (15.12.3) using Qt 5.5.1

- What I was doing when the application crashed:
I wasn't running a separate script, but crash reporter insisted the bug was the
same, so just appending mine to this bug.

All I was doing was running two terminals in tabs. One with an SSH connection
active, but both were idling at the time it crashed.

-- Backtrace (Reduced):
#6  poll_for_reply (c=c@entry=0x8cda10, request=request@entry=75022,
reply=reply@entry=0x7ffc597caab8, error=error@entry=0x7ffc597caba8) at
xcb_in.c:428
#7  0x7f34716afd74 in wait_for_reply (c=c@entry=0x8cda10,
request=request@entry=75022, e=e@entry=0x7ffc597caba8) at xcb_in.c:515
#8  0x7f34716afed2 in xcb_wait_for_reply64 (c=c@entry=0x8cda10,
request=75022, e=e@entry=0x7ffc597caba8) at xcb_in.c:560
#9  0x7f347308b1f0 in _XReply (dpy=dpy@entry=0x8cc7c0,
rep=rep@entry=0x7ffc597cac20, extra=extra@entry=0, discard=discard@entry=0) at
xcb_io.c:596
#10 0x7f34662940e2 in XIQueryDevice (dpy=0x8cc7c0, deviceid=4,
ndevices_return=0x7ffc597cac9c) at XIQueryDevice.c:60

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

[konsole] [Bug 360010] Crash after running a script that runs konsole -e

[via KDE Bugzilla]

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

ziri...@live.com changed:

   What|Removed |Added

 CC||ziri...@live.com

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

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

[Eike Hein via KDE Bugzilla]

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

--- Comment #6 from Eike Hein  ---
Kicker doesn't do any protocol stuff though, it just hands KService URLs to
KRun.

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

[kdenlive] [Bug 361819] git master: changing bin effect parameters does not mark project as changed

[via KDE Bugzilla]

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

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

   What|Removed |Added

Summary|git 16.04: changing bin |git master: changing bin
   |effect parameters does not  |effect parameters does not
   |mark project as changed |mark project as changed

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

[kdenlive] [Bug 361822] git master: resetting effect does not work for bin effects

[via KDE Bugzilla]

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

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

   What|Removed |Added

Summary|git 16.04: resetting effect |git master: resetting
   |does not work for bin   |effect does not work for
   |effects |bin effects

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

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

[via KDE Bugzilla]

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

Bug ID: 363404
   Summary: git master: trying to load a saved title crashes
Kdenlive
   Product: kdenlive
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: wegwerf-1-...@gmx.de

When trying to load a previously saved title in a new title, Kdenlive crashes.
It suffices to save a simple title with just a text, and then reloading it in a
new title.

Before the segfault I see this:

Invalid URL: QUrl("/home/x/Videos/kdenlive/titles")
Thread 1 "kdenlive" received signal SIGSEGV, Segmentation fault.
0x7395bef3 in QGraphicsItem::sceneBoundingRect() const () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5

Running Kdenlive under gdb gives this backtrace (only the first few lines
given):
#0  0x7395bef3 in QGraphicsItem::sceneBoundingRect() const () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
No symbol table info available.
#1  0x00839c1d in TitleWidget::displayBackgroundFrame() ()
No symbol table info available.
#2  0x00841ce9 in TitleWidget::adjustFrameSize() ()
No symbol table info available.
#3  0x008408d1 in TitleWidget::setXml(QDomDocument const&) ()
No symbol table info available.
#4  0x0083fd62 in TitleWidget::loadTitle(QUrl) ()
No symbol table info available.
#5  0x0097cba9 in TitleWidget::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) ()
No symbol table info available.
#6  0x720e3fca in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
No symbol table info available.


Reproducible: Always

Steps to Reproduce:
1. Start a new Kdenlive project.
2. Add a new title clip.
3. In the title editor: add some text.
4. In the title editor: save title
5. Close title editor.
6. Add another new title clip.
7. In the title editor: load the previously saved title.

Actual Results:  
Kdenlive crashes with a segmentation fault.

Expected Results:  
Previously saved title is correctly reloaded without crashing.

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

[okular] [Bug 362856] [Frameworks] Wrong render resolution, possibly caused by Plasma 5 "Scale Display"

[Yi Yang via KDE Bugzilla]

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

--- Comment #12 from Yi Yang  ---
Relevant documentations:
relevant flags: http://doc.qt.io/qt-5/qt.html
QScreen and QPixmap with their new addition in Qt 5.5 or 5.6:
http://doc.qt.io/qt-5/qscreen.html
http://doc.qt.io/qt-5/qpixmap.html

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

[okular] [Bug 362856] [Frameworks] Wrong render resolution, possibly caused by Plasma 5 "Scale Display"

[Yi Yang via KDE Bugzilla]

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

--- Comment #11 from Yi Yang  ---
By reading more documents and doing more experiments, things are now clear.

Qt 5.6 introduces a new option, called "High DPI Scaling", which is both
controllable form environment variables and application-wise options
(Qt::AA_EnableHighDpiScaling and Qt::AA_DisbleHighDpiScaling). This gives us
solution A: temporarily force Qt::AA_DisbleHighDpiScaling. This solution does
uglify menus and icons, though.

The more complex solution B needs more code refactoring. The key is to realize
that you are using "device-independent geometry" while the pixmap inside
QPixmap are using real physical values. You need to get this magical value from
QScreen::devicePixelRatio() and set them to QPixmap::setDevicePixelRatio().
This step might be simplified by "Qt::AA_UseHighDpiPixmaps". I'm not sure, the
documentation here isn't clear.

But the even harder part is you need to rewrite the image rotation and cropping
code, since now you are cropping the image to (widget size *
devicePixelRatio()). It's a bit tricky and many code in different locations
made the assumption that widget size = the pixmap size in it, which no longer
holds and thus broken code is scattered everywhere.

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

[Powerdevil] [Bug 350365] Battery monitor in tray randomly shows there is no battery

[Tim Taylor via KDE Bugzilla]

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

Tim Taylor  changed:

   What|Removed |Added

 CC||tim.taylor+bugzilla.bugs.kd
   ||e@gmail.com

--- Comment #5 from Tim Taylor  ---
I also have this issue on my HP ProBook 5320m running Kubuntu 16.04. I didn't
notice it when running 15.10.

In addition to the low level tools successfully reading the battery status, the
KDE login screen also shows the battery status correctly. But when I log in,
sometimes (not always) the system tray says no battery found. But then if I log
out, the login screen still shows the correct battery info again.

The system tray monitor is obviously doing something different to the login
screen - the latter works reliably but the former does not.

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

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

[Rik Mills via KDE Bugzilla]

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

--- Comment #5 from Rik Mills  ---
Previously, Chakra with plasma 5.6.3 and frameworks 5.21 was unaffected, as
should be the case if a FW 5.21 problem.

After: 

https://chakraos.org/news/index.php?/archives/178-Plasma-5.6.4,-Applications-16.04.1-and-Frameworks-5.22.0-available-in-Chakra.html

upgrade to plasma 5.6.4 and frameworks 5.22, 

can confirm Chakra also shows this bug.

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

[Akonadi] [Bug 361157] Akonadi does not work properly after Update to KDE FW 5.20, Plasma 5.6 and Qt5.6 on Opensuse Leap 42.1

[Daniel Vrátil via KDE Bugzilla]

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

Daniel Vrátil  changed:

   What|Removed |Added

 CC||dvra...@kde.org

--- Comment #19 from Daniel Vrátil  ---
Ok, so I gather that the Akonadi service is not starting for you. I recommend
you run Akonadi from terminal (akonadictl start) and look at the output, that
usually tells where the problem is.

You can increase the debugging level by running

QT_LOGGING_RULES="* = true
qt.* = false" akonadictl start

(note the newline after true, that's not a typo)

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

[plasmashell] [Bug 355587] Manually control number of rows/columns in system tray

[Bob Wya via KDE Bugzilla]

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

--- Comment #8 from Bob Wya  ---
(In reply to Martin Klapetek from comment #3)
> I think this https://git.reviewboard.kde.org/r/125773/ could/would fix it.
> 
> Are you able to test patches? Could you test this one?

I've tested the patch - along with setting my systemtray icons to a fixed size
(16x16) - in the systemtray plasmoid.

I don't normally run with a Vertical Panel (since KDE4 / Plasma 5 have not
supported this configuration very well). Now I've got to say it's become a
totally viable option!! It's possible to match the look 'n' feel of a Windows
vertical panel (which previously looked far better).

Should this bug have the VisualDesign + set? The vertical panel configuration
thread - was a hot topic in the VDG subforum - when Plasma 5 was being worked
on!!

Personally I really like my new look desktop. It's now possible to have much
thinner panels - without the systemtray icons looking dumbly oversized.

Screenshots can be supplied - if anyone is interested...

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

[plasmashell] [Bug 363403] New: Plasma gets very slow in system tray, WIFI, Bluetooth hang it, task manager does not respond to clicks

[Michal Papis via KDE Bugzilla]

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

Bug ID: 363403
   Summary: Plasma gets very slow in system tray, WIFI, Bluetooth
hang it, task manager does not respond to clicks
   Product: plasmashell
   Version: 5.6.4
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: mpa...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.6.4)

Qt Version: 5.6.0
Frameworks Version: 5.22.0
Operating System: Linux 4.5.4-1-default x86_64
Distribution: "openSUSE Tumbleweed (20160422) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Disabled Bluetooth in the applet from system tray

- Unusual behavior I noticed:
The whole bar gets very slow, it does not respond to clicks, it does not allow
network after sleep, bluetooth gets disconected, clicking anything freezes the
interface for some time, the applets stay visible for this time, only after
they disapear everything starts working again.

The crash can be reproduced sometimes.

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

Thread 9 (Thread 0x7fc4fa602700 (LWP 25704)):
#0  0x7fc50a7459cd in poll () at /lib64/libc.so.6
#1  0x7fc50f67c3f2 in  () at /usr/lib64/libxcb.so.1
#2  0x7fc50f67dfc7 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7fc4fc956969 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fc50ae3ab29 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fc509f47454 in start_thread () at /lib64/libpthread.so.0
#6  0x7fc50a74e3fd in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7fc4f89f3700 (LWP 25706)):
#0  0x7fc506e35739 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fc506df1e7c in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fc506df2398 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fc506df24fc in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fc50b050c5b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fc50affc79a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fc50ae35f2c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fc50bdd97b5 in  () at /usr/lib64/libQt5DBus.so.5
#8  0x7fc50ae3ab29 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fc509f47454 in start_thread () at /lib64/libpthread.so.0
#10 0x7fc50a74e3fd in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7fc4f2fc3700 (LWP 25716)):
#0  0x7fc506e35752 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fc506df1a10 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fc506df2323 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fc506df24fc in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fc50b050c5b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fc50affc79a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fc50ae35f2c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fc50e146f35 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7fc50ae3ab29 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fc509f47454 in start_thread () at /lib64/libpthread.so.0
#10 0x7fc50a74e3fd in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7fc4e1b46700 (LWP 25788)):
#0  0x7fc506e35739 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fc506df1460 in g_main_context_acquire () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fc506df22c5 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fc506df24fc in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fc50b050c5b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fc50affc79a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fc50ae35f2c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fc50e146f35 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7fc50ae3ab29 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fc509f47454 in start_thread () at /lib64/libpthread.so.0
#10 0x7fc50a74e3fd in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7fc4dbfff700 (LWP 25813)):
#0  0x7fc50a7419ad in read () at /lib64/libc.so.6
#1  0x7fc506e34490 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fc506df1f24 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fc506df2398 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7fc506df24fc in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7fc50b050c5b in
QEventDispatcherGlib::processEvents(QFlags) ()
at 

[kwin] [Bug 363079] artifacts, mostly seen with firefox and eclipse

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #17 from Thomas Lübking  ---
Thanks, that may contain "tearing" not sure, could be the recording, but the
key problem is that briefly a black frame appears.
Since this also happens w/ xrender compositing, it's not the buffer_age usage
of kwin - is the problem constrained to the (firefox) window or does it cover
the entire screen as soon as (firefox) is up?

Reg. uxa ./. your touchpad: there should be no direct relation whatsoever, but
uxa may cause more CPU load, making the system less responsive in general.
Removing the file should restore the status quo ante, but you need to restart
X11 in addition, of course ;-)

Can you please attach Xorg.0.log from a session where the intel conf snippet
was still present? (to verify the impact)

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

[Akonadi] [Bug 361485] crash on initial start with mysql 5.7 on ubuntu 16.04

[Daniel Vrátil via KDE Bugzilla]

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

Daniel Vrátil  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||http://commits.kde.org/akon
   ||adi/213e7f9d97e4f072615
   ||63abfebfe932e39a1
   Version Fixed In||16.04.2

--- Comment #8 from Daniel Vrátil  ---
Git commit 213e7f9d97e4f07261563abfebfe932e39a1 by Daniel Vrátil.
Committed on 22/05/2016 at 13:21.
Pushed by dvratil into branch 'Applications/16.04'.

Fix MySQL 5.7 support

This implements support for various versions of Oracle MySQL and MariaDB,
adding a special case for MySQL >= 5.7.4 (which removed --force command
line option) and MySQL >= 5.7.6 (which deprecated mysql_db_install and
recommends mysqld --initialize instead)

Also improves debug output during initialization.
FIXED-IN: 16.04.2

M  +7-0src/server/storage/dbconfig.cpp
M  +4-0src/server/storage/dbconfig.h
M  +91   -22   src/server/storage/dbconfigmysql.cpp
M  +7-1src/server/storage/dbconfigmysql.h

http://commits.kde.org/akonadi/213e7f9d97e4f07261563abfebfe932e39a1

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

[krita] [Bug 363284] [UGEE] Krita connects strokes with previous ones

[Eli Spizzichino via KDE Bugzilla]

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

Eli Spizzichino  changed:

   What|Removed |Added

 CC||scr...@gmail.com

--- Comment #11 from Eli Spizzichino  ---
Hello to all,
I'm in the process of buying the same tablet, and having it to work well in
krita will be important, so I was wondering if it would help if I ship it to
one of you to help debug and get it back?

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

[plasmashell] [Bug 355587] Manually control number of rows/columns in system tray

[Bob Wya via KDE Bugzilla]

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

--- Comment #7 from Bob Wya  ---
(In reply to Rog131 from comment #6)
> Kubuntu forums has an example how to edit the Layout.js to get smaller icons
> to the vertical system tray:
> https://www.kubuntuforums.net/showthread.php?69658-Reduce-icon-size-in-
> vertical-panel=384036=1#post384036

Boom!! IMHO that should exposed in the (rather anaemic) system tray
configuration gui...
Thanks :-)

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

[krita] [Bug 358147] Crash when trying to open or create a file

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Resolution|LATER   |FIXED

--- Comment #9 from Boudewijn Rempt  ---
Please try the latest 3.0 builds -- the ones from
https://www.kickstarter.com/projects/krita/krita-2016-lets-make-text-and-vector-art-awesome/posts/1582415
-- because those are able to detect the opengl version correctly again.

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

[QtCurve] [Bug 362907] kwin_x11 crashes in QtCurve::Style::disconnectDBus()

[beojan via KDE Bugzilla]

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

beojan  changed:

   What|Removed |Added

 CC||beo...@gmail.com

--- Comment #2 from beojan  ---
I'm using KF5.22 and Qt 5.6.0. KWin doesn't crash but other programs (e.g.
kactivitymanagerd) do crash at startup, in disconnectDBus as in this bug.

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

[krita] [Bug 363374] Save formats

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org

--- Comment #3 from Boudewijn Rempt  ---
Is this still the case with the builds I made on Friday May 20?

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

[Akonadi] [Bug 362138] Akonadi server crashes when opening Kmail

[Daniel Vrátil via KDE Bugzilla]

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

Daniel Vrátil  changed:

   What|Removed |Added

 CC||dvra...@kde.org

--- Comment #1 from Daniel Vrátil  ---
There seems to be something wrong with your environment and setup:

1) Environment variable XDG_DATA_DIRS is set to
'/usr/share//usr/share/xsessions/plasma:/usr/local/share/:/usr/share/' 

The first should say /usr/share/xsessions/plasma IMO

2) Error on realpath() on '/var/lib/mysql-files' (Error 2 - No such file or
directory)

No idea what that's about, but that looks like a MySQL issue.

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

[krita] [Bug 360601] [INTEL] Canvas doesn't update but is not black either

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #10 from Boudewijn Rempt  ---
Ah... If that's the case, then there's nothing we can do. I guess the only
possible solution is to use the 32 bits builds, because those can work with the
32 bits drivers that might still be available.

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

[krita] [Bug 363284] [UGEE] Krita connects strokes with previous ones

[Boudewijn Rempt via KDE Bugzilla]

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

--- Comment #10 from Boudewijn Rempt  ---
It also needs to an actual Ugee tablet -- the log doesn't really tell me what's
wrong in this case. It looks okay to me. And if we change the code, we need to
test the result with actual hardware (and then we need to test with the brands
we do support: Wacom, Huion and Yiynova).

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

[plasmashell] [Bug 363402] New: Switching activities regularly crashes plasmashell in high memory loads

[via KDE Bugzilla]

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

Bug ID: 363402
   Summary: Switching activities regularly crashes plasmashell in
high memory loads
   Product: plasmashell
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: cmdrkot...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

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

-- Information about the crash:
- What I was doing when the application crashed:
I have 100Mb of 16Gb free and about a gig in swap (was stitching google maps in
krita on a 24000x15000 canvas). Chromium spans two monitors on the second
activity, and krita is on the first. I was grabbing screenshots and dumping
them into krita. Plasmashell crashes every three to four activity switches or
so.  Under regular memory conditions, this does not happen.
fwiw, I switch using the switch activity shortcut (meta+tab).

The crash can be reproduced sometimes.

-- Backtrace:
Application: Plasma (plasmashell), 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 0x7fd6fe3068c0 (LWP 11200))]

Thread 19 (Thread 0x7fd6ea38b700 (LWP 11202)):
#0  0x7fd6f89b6e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fd6fcac5c62 in  () at /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fd6fcac78d7 in xcb_wait_for_event () at
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fd6ecb45629 in QXcbEventReader::run() (this=0xddcae0) at
qxcbconnection.cpp:1253
#4  0x7fd6f90b984e in QThreadPrivate::start(void*) (arg=0xddcae0) at
thread/qthread_unix.cpp:331
#5  0x7fd6f818b6fa in start_thread (arg=0x7fd6ea38b700) at
pthread_create.c:333
#6  0x7fd6f89c2b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 18 (Thread 0x7fd6e35eb700 (LWP 11205)):
#0  0x7fd6f89b29cd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fd6f57296c0 in g_wakeup_acknowledge (__nbytes=16,
__buf=0x7fd6e35eaae0, __fd=) at
/usr/include/x86_64-linux-gnu/bits/unistd.h:44
#2  0x7fd6f57296c0 in g_wakeup_acknowledge (wakeup=0x7fd6e40015b0) at
/build/glib2.0-t9oPgV/glib2.0-2.48.0/./glib/gwakeup.c:210
#3  0x7fd6f56e5e04 in g_main_context_check
(context=context@entry=0x7fd6dc000990, max_priority=2147483647,
fds=fds@entry=0x7fd6dc003070, n_fds=n_fds@entry=1) at
/build/glib2.0-t9oPgV/glib2.0-2.48.0/./glib/gmain.c:3632
#4  0x7fd6f56e62c0 in g_main_context_iterate
(context=context@entry=0x7fd6dc000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-t9oPgV/glib2.0-2.48.0/./glib/gmain.c:3837
#5  0x7fd6f56e642c in g_main_context_iteration (context=0x7fd6dc000990,
may_block=may_block@entry=1) at
/build/glib2.0-t9oPgV/glib2.0-2.48.0/./glib/gmain.c:3901
#6  0x7fd6f92f0a9b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fd6dc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#7  0x7fd6f9297dea in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fd6e35eace0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#8  0x7fd6f90b48a4 in QThread::exec() (this=) at
thread/qthread.cpp:503
#9  0x7fd6fb97d3c5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#10 0x7fd6f90b984e in QThreadPrivate::start(void*) (arg=0xed0590) at
thread/qthread_unix.cpp:331
#11 0x7fd6f818b6fa in start_thread (arg=0x7fd6e35eb700) at
pthread_create.c:333
#12 0x7fd6f89c2b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 17 (Thread 0x7fd6da36b700 (LWP 11206)):
#0  0x7fd6f8191749 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7fd6e08bcd04 in  () at /usr/lib/nvidia-361/libGLX_nvidia.so.0
#2  0x7fd6db0b2ef6 in  () at /usr/lib/nvidia-361/libnvidia-glcore.so.361.42
#3  0x7fd6e08bc31c in  () at /usr/lib/nvidia-361/libGLX_nvidia.so.0
#4  0x7fd6f818b6fa in start_thread (arg=0x7fd6da36b700) at
pthread_create.c:333
#5  0x7fd6f89c2b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 16 (Thread 0x7fd6d1f63700 (LWP 11208)):
#0  0x7fd6f89b6e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fd6f56e631c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7fd6cc002e70, timeout=, context=0x7fd6cc000990) at
/build/glib2.0-t9oPgV/glib2.0-2.48.0/./glib/gmain.c:4135
#2  0x7fd6f56e631c in g_main_context_iterate
(context=context@entry=0x7fd6cc000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at

[Akonadi] [Bug 362699] Back end MySQL table PimItemTable shows entries with remoteID = NULL

[Daniel Vrátil via KDE Bugzilla]

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

Daniel Vrátil  changed:

   What|Removed |Added

 CC||dvra...@kde.org

--- Comment #1 from Daniel Vrátil  ---
Entries with a null RemoteID are a perfectly valid case. It means that the item
has been created in Akonadi and is waiting for the owning resource to store it
in the remote storage (e.g. IMAP server, maildir, Google Contacts addressbook,
.etc.).

The issue you are most likely referring to is that you have data stored in
Akonadi that were not synchronized to the remote storage. This is indeed a
known issue, we currently lack any mechanism that would be try to "upload"
those entities again if the initial upload failed for any reason (this is not
affected by network connectivity or shutting down computer before the item is
uploaded). A solution is being worked on though.

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

[plasmashell] [Bug 363249] Desktop switcher in "icon" mode

[FabiB via KDE Bugzilla]

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

--- Comment #1 from FabiB  ---
in other words a icon/desktop widget that runs
qdbus org.kde.kglobalaccel /component/kwin
org.kde.kglobalaccel.Component.invokeShortcut ShowDesktopGrid
on click

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

[kwin] [Bug 363079] artifacts, mostly seen with firefox and eclipse

[via KDE Bugzilla]

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

--- Comment #16 from je.joa...@yahoo.se ---
Created attachment 99131
  --> https://bugs.kde.org/attachment.cgi?id=99131=edit
video_clip

video may be upside down, directors fault :)

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

[plasmashell] [Bug 363401] New: Battery widget crashes plasma

[John via KDE Bugzilla]

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

Bug ID: 363401
   Summary: Battery widget  crashes plasma
   Product: plasmashell
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: azhc...@gmx.us
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

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

-- Information about the crash:
- What I was doing when the application crashed:clicked on the battery widget 
plasma crashed.show low charge

The crash can be reproduced every time.

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

Thread 9 (Thread 0xb16b6b40 (LWP 1675)):
#0  0xb771fc31 in __kernel_vsyscall ()
#1  0xb4d49f8f in poll () at ../sysdeps/unix/syscall-template.S:84
#2  0xb70c041d in ?? () from /usr/lib/i386-linux-gnu/libxcb.so.1
#3  0xb70c259b in xcb_wait_for_event () from
/usr/lib/i386-linux-gnu/libxcb.so.1
#4  0xb17f3273 in QXcbEventReader::run (this=0x830cfa8) at
qxcbconnection.cpp:1253
#5  0xb502743b in QThreadPrivate::start (arg=0x830cfa8) at
thread/qthread_unix.cpp:331
#6  0xb4bfc2b5 in start_thread (arg=0xb16b6b40) at pthread_create.c:333
#7  0xb4d5416e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114

Thread 8 (Thread 0xb0172b40 (LWP 1709)):
#0  0xb442f406 in g_mutex_unlock () from /lib/i386-linux-gnu/libglib-2.0.so.0
#1  0xb43e850b in g_main_context_prepare () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#2  0xb43e8f64 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb43e9194 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb5256b14 in QEventDispatcherGlib::processEvents (this=0xaf800470,
flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0xb51fb953 in QEventLoop::processEvents (this=0xb01721d4, flags=...) at
kernel/qeventloop.cpp:128
#6  0xb51fbdaa in QEventLoop::exec (this=0xb01721d4, flags=...) at
kernel/qeventloop.cpp:204
#7  0xb5021f1d in QThread::exec (this=0x83933c0) at thread/qthread.cpp:503
#8  0xb6892aff in QQmlThreadPrivate::run (this=0x83933c0) at
qml/ftw/qqmlthread.cpp:141
#9  0xb502743b in QThreadPrivate::start (arg=0x83933c0) at
thread/qthread_unix.cpp:331
#10 0xb4bfc2b5 in start_thread (arg=0xb0172b40) at pthread_create.c:333
#11 0xb4d5416e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114

Thread 7 (Thread 0xab536b40 (LWP 1710)):
#0  0xb771fc31 in __kernel_vsyscall ()
#1  0xb4c01a8c in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/i386/pthread_cond_wait.S:187
#2  0xb4d608cd in __pthread_cond_wait (cond=0x849c0e0, mutex=0x849c0c8) at
forward.c:149
#3  0xae7ecbba in ?? () from /usr/lib/i386-linux-gnu/dri/r600_dri.so
#4  0xae7ec185 in ?? () from /usr/lib/i386-linux-gnu/dri/r600_dri.so
#5  0xb4bfc2b5 in start_thread (arg=0xab536b40) at pthread_create.c:333
#6  0xb4d5416e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114

Thread 6 (Thread 0xa95f2b40 (LWP 1711)):
#0  0xb43e8bc8 in g_main_context_dispatch () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#1  0xb43e90c9 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#2  0xb43e9194 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb5256b14 in QEventDispatcherGlib::processEvents (this=0xa8c00470,
flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0xb51fb953 in QEventLoop::processEvents (this=0xa95f21d4, flags=...) at
kernel/qeventloop.cpp:128
#5  0xb51fbdaa in QEventLoop::exec (this=0xa95f21d4, flags=...) at
kernel/qeventloop.cpp:204
#6  0xb5021f1d in QThread::exec (this=0x856c168) at thread/qthread.cpp:503
#7  0xb6892aff in QQmlThreadPrivate::run (this=0x856c168) at
qml/ftw/qqmlthread.cpp:141
#8  0xb502743b in QThreadPrivate::start (arg=0x856c168) at
thread/qthread_unix.cpp:331
#9  0xb4bfc2b5 in start_thread (arg=0xa95f2b40) at pthread_create.c:333
#10 0xb4d5416e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114

Thread 5 (Thread 0xa826db40 (LWP 1712)):
#0  0xb442f3dd in g_mutex_lock () from /lib/i386-linux-gnu/libglib-2.0.so.0
#1  0xb43e903d in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#2  0xb43e9194 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb5256b14 in QEventDispatcherGlib::processEvents (this=0x85db700,
flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0xb51fb953 in QEventLoop::processEvents (this=0xa826d1d4, flags=...) at
kernel/qeventloop.cpp:128
#5  0xb51fbdaa in QEventLoop::exec (this=0xa826d1d4, flags=...) at
kernel/qeventloop.cpp:204
#6  0xb5021f1d in QThread::exec (this=0x85e7918) at thread/qthread.cpp:503
#7  0xb6892aff in QQmlThreadPrivate::run