[plasma-pa] [Bug 353437] Plasma-PA audio levels for applications

[Safa Alfulaij via KDE Bugzilla]

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

--- Comment #3 from Safa Alfulaij  ---
Here you are: http://i.imgur.com/iQqgzOP.png
And some apps running: http://i.imgur.com/RxFwO1d.png

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

[dolphin] [Bug 278236] Cannot drag file onto chromium upload form input

[Bhushan Shah via KDE Bugzilla]

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

Bhushan Shah  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 CC||bhus...@gmail.com
 Resolution|FIXED   |---

--- Comment #13 from Bhushan Shah  ---
Reopening based on last comments.

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

[clazy] [Bug 359306] New: new check idea: avoid using Q_FOREACH to iterate over QMap/QHash keys and retrieve values inside loop

[Nyall Dawson via KDE Bugzilla]

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

Bug ID: 359306
   Summary: new check idea: avoid using Q_FOREACH to iterate over
QMap/QHash keys and retrieve values inside loop
   Product: clazy
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: nyall.daw...@gmail.com
CC: smart...@kde.org

Eg:

QMap map;

Q_FOREACH( const QString& key, map.keys() )
{
   QString val = map.value(key);
   ...
}

It's inefficient, and it'd be nice to catch this and suggest using
QMap::iterator/QHash::Iterator to iterate over both the keys and values at the
same time to avoid the unnecessary lookup.



Reproducible: Always

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

[plasma-pa] [Bug 353437] Plasma-PA audio levels for applications

[Mykola Krachkovsky via KDE Bugzilla]

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

--- Comment #2 from Mykola Krachkovsky  ---
Where? Don't see changes: still only stack of playback devices, no any
tabs.

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

[konsole] [Bug 354082] high cpu usage for screen redrawing with qt5.5

[Viktor Kuzmin via KDE Bugzilla]

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

--- Comment #11 from Viktor Kuzmin  ---
Bug still exists. I'm using gentoo ~x64. I've tried both konsole-4 and latest
konsole. My test is to launch top in konsole and to constantly make text
selection. konsole-4 eats less then 5% of cpu while latest konsole eats more
then 50% cpu.

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

[krita] [Bug 359298] New: crash while use Genius MX-712 tablet (click, move pen, while focus on Krita window)

[Snuux via KDE Bugzilla]

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

Bug ID: 359298
   Summary: crash while use Genius MX-712 tablet (click, move pen,
while focus on Krita window)
   Product: krita
   Version: 2.9.11
  Platform: MS Windows
   URL: http://imgur.com/a/aTVuE
OS: MS Windows
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: tablet support
  Assignee: krita-bugs-n...@kde.org
  Reporter: sn...@yandex.ru

http://imgur.com/a/aTVuE - Debugging info

While doing action move/click/etc with stylus of Genius mx-712 tablet, Krita
instantly crashes. If use mouse - Krita work fine.

In Corel Painter and Photoshop all works fine...

P.S. Same result on stable version 2.9

Reproducible: Always

Steps to Reproduce:
1. Open Krita
2. Move or Click on window (No matter, create (open) already file or no)

Actual Results:  
Krita crashes

Expected Results:  
Do actions, that I want

Use this tablet driver: 
Link on page: http://www.geniusnet.com/Genius/wSite/ct?xItem=16837=174
Link on download file:
http://download.geniusnet.com/2013/Tablet/20121102_Driver%20V5.01.rar
Link on screenshot: http://take.ms/Wlp5G

Windows version: Windows 10 x64.

Ready to provide additional information.

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

[drkonqi] [Bug 355807] Dialog to mark report as related does nothing

[Dennis Schridde via KDE Bugzilla]

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

Dennis Schridde  changed:

   What|Removed |Added

 CC||devuran...@gmx.net

--- Comment #3 from Dennis Schridde  ---
Created attachment 97160
  --> https://bugs.kde.org/attachment.cgi?id=97160=edit
ksmserver-20160210-093312.kcrash.txt

Since I replaced my old, DIV-connected monitor (HannsG HW223D, 1680x1050) with
a new one connected via HDMI (LG 29UM67, 2560x1080), ksmserver was crashing
whenever the monitor went to standby and later back on. Today is the first time
that not ksmserver, but plasmashell (and apparently some others, like kwin_x11
and yakuake) crashed.

I am using Qt 5.5.1, KF 5.18.0, KA 5.12.1, Plasma 5.5.4, Linux 4.4.1,
X.Org-Server 1.18.1.

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

[plasmashell] [Bug 357085] Unplug VGA output then plug again and plasmashell segfaults

[Dennis Schridde via KDE Bugzilla]

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

Dennis Schridde  changed:

   What|Removed |Added

 CC||devuran...@gmx.net

--- Comment #13 from Dennis Schridde  ---
Created attachment 97161
  --> https://bugs.kde.org/attachment.cgi?id=97161=edit
ksmserver-20160210-093312.kcrash.txt

Since I replaced my old, DIV-connected monitor (HannsG HW223D, 1680x1050) with
a new one connected via HDMI (LG 29UM67, 2560x1080), ksmserver was crashing
whenever the monitor went to standby and later back on. Today is the first time
that not just ksmserver, but also plasmashell and severals others, like
kwin_x11 and yakuake, crashed.

I am using Qt 5.5.1, KF 5.18.0, KA 5.12.1, Plasma 5.5.4, Linux 4.4.1,
X.Org-Server 1.18.1.

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

[drkonqi] [Bug 355807] Dialog to mark report as related does nothing

[Dennis Schridde via KDE Bugzilla]

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

--- Comment #4 from Dennis Schridde  ---
(In reply to Dennis Schridde from comment #3)
Sorry, that was the original bugreport, I was trying to create using DrKonqi...

My actual comment on this issue is just a "same here", using Qt 5.5.1, KF
5.18.0, KA 5.12.1, Plasma 5.5.4.

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

[plasma-nm] [Bug 350188] When trying to connect via plasma-nm to a openconnect - connection, the dialog starts flickering until i hit enter -> then crash

[yves duenow via KDE Bugzilla]

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

--- Comment #5 from yves duenow  ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

It works now :) thanks

Am 17. Dezember 2015 15:18:40 MEZ, schrieb Jan Grulich via KDE Bugzilla
:
>https://bugs.kde.org/show_bug.cgi?id=350188
>
>--- Comment #4 from Jan Grulich  ---
>Is this still reproducible with latest Plasma 5.5.1 release? Having
>this
>version is important as there are most recent Openconnect fixes.
>
>--
>You are receiving this mail because:
>You reported the bug.
>You are on the CC list for the bug.

- --
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
-BEGIN PGP SIGNATURE-
Version: APG v1.1.1

iQJdBAEBCgBHBQJWvZNgQBxZdmVzIET8bm93IChZdmVzIET8bm93IEAgRlROLU5l
dC5PcmcpIDxZdmVzLkR1ZW5vd0BmdG4tbmV0Lm9yZz4ACgkQLx3N1yc1jqIkxg//
XMEFfdGtCDTjbgC83HwzyTsJKa4Nowoh1u/h7gxvKvAsmTgkY9zebbloV/LYMgfe
F93wMo1sW7EimnFnQDqnWpwaslXDEN/aGcRlbnL+1hOWzrZ1l59bOxUx+NhIfe4C
5+YigSCWguND0MDi/WIXPkLGjNaTtZS0kC9FoPqUTbujHudk86jzflAj+96QH+bJ
pjhhqtP1jn5TfY6sGqeI/vXzffxbJrv2K/cEZ5pimGdF4cLyzPSEjuuM3sauemqq
NKLQ3zL0FJcsbzvwvgQWwAWBqTrjbhSIjSb19qdAx9k6AWYAeuu4NlsJy5DTKg7f
dV837SeEQ4/FAFlkYkK2I/EE6xuHcd5eoEMgbINFE0MBZ5NwB/zB9lCzaklEmGm4
SIy+Lf3ztTa45bd9xOnd6lszPnr3YYkIflOGzzL/RV8hFJD6SjpOb24pl6fhmKOl
EOolClNBSKec2cBMrPcDhBshEEkrW/mfs18qFynj6n4fdgqiSWf+H+89Hl3OFw0t
bonhYn3y4UXnvgcs/+6JySl0F4PuxdhqE/HJTr7uxMXjgXlEn46YIXcXxPnNiWID
t5EvPC9+E42UeBOOoqMc9D9+hijqzlol+Exsp+DeNBRdHXNO8HdJ8jE9Lcg2olL2
LN/zO9MYAm+ld2kjYSh4Y34/2peYjZXH6fHjIR+qez4=
=h78/
-END PGP SIGNATURE-

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

[plasmashell] [Bug 359299] New: Plasma, KWin, ksmserver, yakuake and more crash when HDMI monitor goes to standby

[Dennis Schridde via KDE Bugzilla]

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

Bug ID: 359299
   Summary: Plasma, KWin, ksmserver, yakuake and more crash when
HDMI monitor goes to standby
   Product: plasmashell
   Version: 5.5.4
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: devuran...@gmx.net
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.4)

Qt Version: 5.5.1
Operating System: Linux 4.4.1-gentoo x86_64
Distribution: "Gentoo Base System release 2.2"

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

1. The monitor went to standby.
2. A while later (ranging from a few seconds to several hours) I turned it on
again by moving the mouse.
3. I find Plasma, KWin, ksmserver, yakuake and others crashed.

This is reproducible every time and has happened several times already.

This is a duplicate of bug #357085, but due to DrKonqi bug #355807, I cannot
conveniently attach this information there.

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

Thread 9 (Thread 0x7f6bf2091700 (LWP 3184)):
#0  0x7f6bfe3c890d in poll () from /lib64/libc.so.6
#1  0x7f6c023a4a72 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f6c023a6627 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f6bf312b719 in QXcbEventReader::run (this=0x1b4e5d0) at
qxcbconnection.cpp:1229
#4  0x7f6bfeab0822 in QThreadPrivate::start (arg=0x1b4e5d0) at
thread/qthread_unix.cpp:331
#5  0x7f6bfdbd942c in start_thread () from /lib64/libpthread.so.0
#6  0x7f6bfe3d180d in clone () from /lib64/libc.so.6

Thread 8 (Thread 0x7f6bebbd9700 (LWP 3188)):
#0  postEventSourcePrepare (s=0x7f6be40012d0, timeout=0x7f6bebbd8ba4) at
kernel/qeventdispatcher_glib.cpp:255
#1  0x7f6bfb9da76c in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f6bfb9db0cb in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f6bfb9db2ac in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f6bfec9682b in QEventDispatcherGlib::processEvents
(this=0x7f6be40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f6bfec4ab0a in QEventLoop::exec (this=this@entry=0x7f6bebbd8d60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f6bfeaac384 in QThread::exec (this=this@entry=0x1c34720) at
thread/qthread.cpp:503
#7  0x7f6c01263875 in QQmlThreadPrivate::run (this=0x1c34720) at
qml/ftw/qqmlthread.cpp:141
#8  0x7f6bfeab0822 in QThreadPrivate::start (arg=0x1c34720) at
thread/qthread_unix.cpp:331
#9  0x7f6bfdbd942c in start_thread () from /lib64/libpthread.so.0
#10 0x7f6bfe3d180d in clone () from /lib64/libc.so.6

Thread 7 (Thread 0x7f6bd49c9700 (LWP 3212)):
#0  0x7f6bfdbdef4f in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x7f6be9171c93 in cnd_wait (mtx=0x1e5e8f0, cond=0x1e5e918) at
/var/tmp/portage/media-libs/mesa-11.1.1/work/mesa-11.1.1/include/c11/threads_posix.h:159
#2  pipe_semaphore_wait (sema=0x1e5e8f0) at
/var/tmp/portage/media-libs/mesa-11.1.1/work/mesa-11.1.1/src/gallium/auxiliary/os/os_thread.h:259
#3  radeon_drm_cs_emit_ioctl (param=param@entry=0x1e5e5a0) at
/var/tmp/portage/media-libs/mesa-11.1.1/work/mesa-11.1.1/src/gallium/winsys/radeon/drm/radeon_drm_winsys.c:653
#4  0x7f6be9171417 in impl_thrd_routine (p=) at
/var/tmp/portage/media-libs/mesa-11.1.1/work/mesa-11.1.1/include/c11/threads_posix.h:87
#5  0x7f6bfdbd942c in start_thread () from /lib64/libpthread.so.0
#6  0x7f6bfe3d180d in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f6bd0c31700 (LWP 3218)):
#0  0x7f6bfb9da6e8 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#1  0x7f6bfb9db0cb in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f6bfb9db2ac in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f6bfec9682b in QEventDispatcherGlib::processEvents
(this=0x7f6bcc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f6bfec4ab0a in QEventLoop::exec (this=this@entry=0x7f6bd0c30d60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f6bfeaac384 in QThread::exec (this=this@entry=0x203b490) at
thread/qthread.cpp:503
#6  0x7f6c01263875 in QQmlThreadPrivate::run (this=0x203b490) at
qml/ftw/qqmlthread.cpp:141
#7  0x7f6bfeab0822 in QThreadPrivate::start (arg=0x203b490) at
thread/qthread_unix.cpp:331
#8  0x7f6bfdbd942c in start_thread () from /lib64/libpthread.so.0
#9  0x7f6bfe3d180d in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f6bcb391700 (LWP 3231)):
#0  0x7f6bfe3c890d in poll () from /lib64/libc.so.6
#1  0x7f6bfb9db19c in ?? () 

[plasmashell] [Bug 357085] Unplug VGA output then plug again and plasmashell segfaults

[Dennis Schridde via KDE Bugzilla]

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

--- Comment #14 from Dennis Schridde <devuran...@gmx.net> ---
Created attachment 97162
  --> https://bugs.kde.org/attachment.cgi?id=97162=edit
ksmserver-20160212-084655.kcrash.txt

Due to DrKonqi bug #355807 I had to submit the information about the current
crash as bug #359299.

The information from the attachment is again a crash log of ksmserver, which
crashed at the same time as plasmashell (whose crash log can be found in bug
#359299).

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

[plasma-nm] [Bug 350188] When trying to connect via plasma-nm to a openconnect - connection, the dialog starts flickering until i hit enter -> then crash

[Jan Grulich via KDE Bugzilla]

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

Jan Grulich  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|UNCONFIRMED |RESOLVED

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

[plasmashell] [Bug 359300] New: Switching 2nd Monitor on/off

[Bas via KDE Bugzilla]

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

Bug ID: 359300
   Summary: Switching 2nd Monitor on/off
   Product: plasmashell
   Version: 5.4.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: b...@digitalnomad.de
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.2)

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

-- Information about the crash:
- What I was doing when the application crashed:
- Lenovo Thinkpad x250 + docking station
- after boot, second monitoris not available
- System Settings > Display & Monitor > switching the 2nd screen off and on
again
- Plasma crashes

The crash can be reproduced every time.

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

Thread 8 (Thread 0x7f4aa25ea700 (LWP 1232)):
#0  0x7f4ab18a88dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f4ab58efbd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f4ab58f174f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f4aa4934a39 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
#4  0x7f4ab1f9b2be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f4ab108a6aa in start_thread (arg=0x7f4aa25ea700) at
pthread_create.c:333
#6  0x7f4ab18b3eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7f4a9bdfa700 (LWP 1298)):
#0  0x7f4ab18a88dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f4aae6551ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f4aae6552fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f4ab21d229b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f4ab217875a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f4ab1f963d4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f4ab47bef85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f4ab1f9b2be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f4ab108a6aa in start_thread (arg=0x7f4a9bdfa700) at
pthread_create.c:333
#9  0x7f4ab18b3eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f4a90ae5700 (LWP 1301)):
#0  0x7f4ab18a88dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f4aae6551ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f4aae6552fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f4ab21d229b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f4ab217875a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f4ab1f963d4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f4ab47bef85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f4ab1f9b2be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f4ab108a6aa in start_thread (arg=0x7f4a90ae5700) at
pthread_create.c:333
#9  0x7f4ab18b3eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f4a8a26a700 (LWP 1313)):
#0  0x7f4ab18a449d in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f4aae6984e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f4aae654cd4 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f4aae655190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f4aae6552fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f4ab21d229b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f4ab217875a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f4ab1f963d4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f4ab47bef85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#9  0x7f4ab1f9b2be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f4ab108a6aa in start_thread (arg=0x7f4a8a26a700) at
pthread_create.c:333
#11 0x7f4ab18b3eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f4a88971700 (LWP 1315)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f4ab6b4a114 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  

[drkonqi] [Bug 359301] New: DrKonqi refuses to report bugs against ksmserver

[Dennis Schridde via KDE Bugzilla]

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

Bug ID: 359301
   Summary: DrKonqi refuses to report bugs against ksmserver
   Product: drkonqi
   Version: 5.5.4
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: devuran...@gmx.net

Due to bug #357085, ksmserver crashes a lot. Every time after re-establishing
the session (i.e. restarting kwin_x11), I see a DrKonqi window with the crash
report about ksmserver. Always "the generated crash information is useful", but
also always the "Report Bug" button is greyed out. This only appears to happen
with ksmserver, but not with plasmashell, as today the crash report window for
plasmashell appeared at the same time and allowed me to generate bug #359299 in
the regular drkonqi-assisted way without any trouble.

I am using Qt 5.5.1, KF 5.18.0, KA 5.12.1, Plasma 5.5.4.

Reproducible: Always

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

[Akonadi] [Bug 359304] New: Akonadi crashed while not using any PIM application

[Samuele Kaplun via KDE Bugzilla]

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

Bug ID: 359304
   Summary: Akonadi crashed while not using any PIM application
   Product: Akonadi
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: IMAP resource
  Assignee: chrig...@fastmail.fm
  Reporter: samuele.kap...@cern.ch
CC: kdepim-b...@kde.org, vkra...@kde.org

Application: akonadi_imap_resource (4.89.0)

Qt Version: 5.5.1
Operating System: Linux 4.3.0-040300-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:
- What I was doing when the application crashed:
Kontact was open in background and suddenly I have received the notification
that Akonadi crashed.

-- Backtrace:
Application: Risorsa Akonadi (akonadi_imap_resource), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc1bfbd6840 (LWP 12173))]

Thread 4 (Thread 0x7fc1bdaef700 (LWP 12192)):
#0  0x7fc1ce4f48dd in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7fc1c9c9abd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fc1c9c9c74f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fc1bf8157e9 in QXcbEventReader::run (this=0xa6a240) at
qxcbconnection.cpp:1229
#4  0x7fc1cee01a6e in QThreadPrivate::start (arg=0xa6a240) at
thread/qthread_unix.cpp:331
#5  0x7fc1c9eb96aa in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#6  0x7fc1ce4ffeed in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 3 (Thread 0x7fc1b631e700 (LWP 3758)):
#0  0x7fc1c9180869 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fc1c913c1ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc1c913c2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc1cf03950b in QEventDispatcherGlib::processEvents
(this=0x7fc1a4014470, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7fc1cefe050a in QEventLoop::exec (this=this@entry=0x7fc1b631dd80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7fc1cedfcac4 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7fc1cee01a6e in QThreadPrivate::start (arg=0xb971b0) at
thread/qthread_unix.cpp:331
#7  0x7fc1c9eb96aa in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#8  0x7fc1ce4ffeed in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 2 (Thread 0x7fc1a700 (LWP 31313)):
#0  0x7fc1ce4f049d in read () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7fc1c917f4e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc1c913bcd4 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc1c913c190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fc1c913c2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fc1cf03950b in QEventDispatcherGlib::processEvents
(this=0x7fc1b00afb40, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#6  0x7fc1cefe050a in QEventLoop::exec (this=this@entry=0x7fc1afffed80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#7  0x7fc1cedfcac4 in QThread::exec (this=) at
thread/qthread.cpp:503
#8  0x7fc1cee01a6e in QThreadPrivate::start (arg=0xb3b7e0) at
thread/qthread_unix.cpp:331
#9  0x7fc1c9eb96aa in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#10 0x7fc1ce4ffeed in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 1 (Thread 0x7fc1bfbd6840 (LWP 12173)):
[KCrash Handler]
#6  0x7fc1ce42e267 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#7  0x7fc1ce42feca in abort () from /lib/x86_64-linux-gnu/libc.so.6
#8  0x7fc1cea69b7d in __gnu_cxx::__verbose_terminate_handler() () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x7fc1cea679c6 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x7fc1cea67a11 in std::terminate() () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#11 0x7fc1cea67c29 in __cxa_throw () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#12 0x7fc1cd70a7ac in Akonadi::Protocol::DataStream::operator>>
(this=0x7ffc6ef76a50, str=...) at ../../../src/private/datastream_p_p.h:209
#13 0x7fc1cd6fc813 in Akonadi::Protocol::deserialize (device=) at ../../../src/private/protocol.cpp:627
#14 0x7fc1d1ca47ab in Akonadi::SessionPrivate::dataReceived (this=0xb28d90)
at ../../../../akonadi/src/core/session.cpp:239
#15 0x7fc1cf0118ea in QMetaObject::activate (sender=0xb2f1a0,
signalOffset=, local_signal_index=,
argv=) at kernel/qobject.cpp:3713
#16 0x7fc1cf0118ea in QMetaObject::activate (sender=sender@entry=0xb07538,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x0) at kernel/qobject.cpp:3713
#17 0x7fc1cf0120e7 in 

[clazy] [Bug 359305] New: false positives in container-anti-pattern

[Nyall Dawson via KDE Bugzilla]

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

Bug ID: 359305
   Summary: false positives in container-anti-pattern
   Product: clazy
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: nyall.daw...@gmail.com
CC: smart...@kde.org

I'm just testing the new container-anti-pattern check and I get false positives
for code like:

 Q_FOREACH ( int id, someMap.keys() )
  {
   
  }

and 

someMap.keys().toSet()

I believe these are both false positives 



Reproducible: Always

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

[plasma-pk-updates] [Bug 359308] New: Dark text on dark background

[Fabian Vogt via KDE Bugzilla]

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

Bug ID: 359308
   Summary: Dark text on dark background
   Product: plasma-pk-updates
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jgrul...@redhat.com
  Reporter: fab...@ritter-vogt.de

When using a dark plasma theme, the state string is almost unreadable, see the
attached screenshot.

Reproducible: Always

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

[plasmashell] [Bug 359310] New: Remember scroll position when going back in FolderView popup

[Kai Uwe Broulik via KDE Bugzilla]

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

Bug ID: 359310
   Summary: Remember scroll position when going back in FolderView
popup
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Folder
  Assignee: h...@kde.org
  Reporter: k...@privat.broulik.de
CC: plasma-b...@kde.org

When using FolderView in a popup and you navigate to a subdirectory you can go
back pressing the Back button on your mouse anytime. It should remember the
scroll position in the previous view if you go back.

Perhaps there even needs to be means to always go back, ie. have the "Up"
button sticky or something like that

Reproducible: Always

Steps to Reproduce:
1. Place Folder in your panel
2. Click it, scroll down, navigate to sub folder (I have "Folders first"
disabled)
3. Press back mouse button

Actual Results:  
The view goes back and is scrolled to the top, makes quickly traversing
multiple subfolders painful

Expected Results:  
The view remembers the scroll position and is where I left it

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

[kdelibs] [Bug 359315] New: KNotify Crash during notifications

[EMR_Kde via KDE Bugzilla]

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

Bug ID: 359315
   Summary: KNotify Crash during notifications
   Product: kdelibs
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: knotify
  Assignee: ogoff...@kde.org
  Reporter: emre...@gmail.com

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

-- Information about the crash:
Anytime a notification is fired, KNotify crashes. I don't know why. I have two
SuSE systems and it doesn't happen on the laptop. The only thing I am thinking
is use of BlueTooth and audacious (which I compiled from scratch).

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

Thread 2 (Thread 0x7f7439ece700 (LWP 29478)):
#0  0x7f744a1f4c5d in poll () at /lib64/libc.so.6
#1  0x7f744785ebe4 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f744785ecec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f744a9770de in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#4  0x7f744a948e6f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#5  0x7f744a949165 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7f744a8460bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x7f744a92a783 in  () at /usr/lib64/libQtCore.so.4
#8  0x7f744a84879f in  () at /usr/lib64/libQtCore.so.4
#9  0x7f744827b0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f744a1fd08d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f744d00c800 (LWP 29477)):
[KCrash Handler]
#5  0x7f744a23bfe6 in __strcmp_ssse3 () at /lib64/libc.so.6
#6  0x7f742e594fee in QMetaType::registerNormalizedType(QByteArray const&,
void (*)(void*), void* (*)(void const*), void (*)(void*), void* (*)(void*, void
const*), int, QFlags, QMetaObject const*) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f742ea94f57 in  () at /usr/lib64/libQt5Gui.so.5
#8  0x7f744ce928ea in call_init.part () at /lib64/ld-linux-x86-64.so.2
#9  0x7f744ce929d3 in _dl_init_internal () at /lib64/ld-linux-x86-64.so.2
#10 0x7f744ce96b08 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2
#11 0x7f744ce927a4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2
#12 0x7f744ce962fb in _dl_open () at /lib64/ld-linux-x86-64.so.2
#13 0x7f74459d502b in dlopen_doit () at /lib64/libdl.so.2
#14 0x7f744ce927a4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2
#15 0x7f74459d55dd in _dlerror_run () at /lib64/libdl.so.2
#16 0x7f74459d50c1 in dlopen@@GLIBC_2.2.5 () at /lib64/libdl.so.2
#17 0x7f7438d4359f in  () at /usr/lib64/libvlccore.so.7
#18 0x7f7438d2cd5d in  () at /usr/lib64/libvlccore.so.7
#19 0x7f7438d2d057 in  () at /usr/lib64/libvlccore.so.7
#20 0x7f7438d2d2c9 in  () at /usr/lib64/libvlccore.so.7
#21 0x7f7438d2d534 in  () at /usr/lib64/libvlccore.so.7
#22 0x7f7438d2da87 in  () at /usr/lib64/libvlccore.so.7
#23 0x7f7438cc549d in libvlc_InternalInit () at /usr/lib64/libvlccore.so.7
#24 0x7f7438a96623 in libvlc_new () at /usr/lib64/libvlc.so.5
#25 0x7f7438fc7ec9 in  () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_vlc.so
#26 0x7f7438fad728 in  () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_vlc.so
#27 0x7f7438fae1eb in qt_plugin_instance () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_vlc.so
#28 0x7f744a92e641 in QPluginLoader::instance() () at
/usr/lib64/libQtCore.so.4
#29 0x7f74394c4f8b in  () at /usr/lib64/kde4/plugins/phonon_platform/kde.so
#30 0x7f74394c5773 in  () at /usr/lib64/kde4/plugins/phonon_platform/kde.so
#31 0x7f744c5e9c76 in  () at /usr/lib64/libphonon.so.4
#32 0x7f744c5ea317 in Phonon::Factory::backend(bool) () at
/usr/lib64/libphonon.so.4
#33 0x7f744c5ea8e3 in  () at /usr/lib64/libphonon.so.4
#34 0x7f744c5e29b9 in  () at /usr/lib64/libphonon.so.4
#35 0x7f744c5e0896 in  () at /usr/lib64/libphonon.so.4
#36 0x0040e771 in _start ()

Reported using DrKonqi

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

[i18n] [Bug 359318] kwebkitpart: "Verknüpfung- kopieren"

[Wolfgang Bauer via KDE Bugzilla]

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

--- Comment #2 from Wolfgang Bauer  ---
(In reply to Wolfgang Bauer from comment #1)
> Sollte wohl eher "Verknüpfungs kopieren" heißen, denke ich...

Sorry, "Verknüpfungs kopieren" natürlich. ;-)

Also das '-' sollte meiner Meinung nach mit einem 's' ersetzt werden.

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

[kpat] [Bug 359309] New: freecell: error in counting moves

[charles via KDE Bugzilla]

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

Bug ID: 359309
   Summary: freecell: error in counting moves
   Product: kpat
   Version: 3.6
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: co...@kde.org
  Reporter: w123-2...@gmx.de
CC: kde-games-b...@kde.org

freecell -> new deal 
Suppose n cards will go to the final stack (upper right) without any user
interaction right in the beginning.
If n > 1, then only n-1 moves are counted (eqivalent: the second move goes
uncounted)
If you use "undo" and then do these steps manually, counting is correct.

Reproducible: Always

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

[clazy] [Bug 359305] false positives in container-anti-pattern

[Nyall Dawson via KDE Bugzilla]

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

Nyall Dawson  changed:

   What|Removed |Added

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

--- Comment #2 from Nyall Dawson  ---
Ah, ok. I get it now... Thanks for the pointers!

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

[kdeconnect] [Bug 359311] New: SMS truncated

[Josef Kufner via KDE Bugzilla]

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

Bug ID: 359311
   Summary: SMS truncated
   Product: kdeconnect
   Version: unspecified
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: plasmoid
  Assignee: albertv...@gmail.com
  Reporter: j...@frozen-doe.net

When a new SMS arrives, its text is truncated to few first words. It sould be
nice if the whole text can be shown by clicking the notification.

Reproducible: Always

Steps to Reproduce:
1. Receive SMS with more than few words.
2. Try to read notification on desktop.

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

[kdeconnect] [Bug 359313] New: Show notification count on plasmoid icon

[Josef Kufner via KDE Bugzilla]

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

Bug ID: 359313
   Summary: Show notification count on plasmoid icon
   Product: kdeconnect
   Version: unspecified
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: plasmoid
  Assignee: albertv...@gmail.com
  Reporter: j...@frozen-doe.net

Plasmoid icon does not change when there is a notification. It would be nice to
have a number of notifications over the icon. Or at least change the icon a
little bit.

Reproducible: Always

Steps to Reproduce:
1. Receive new notification
2. Look at plasmoid icon.
3. Nothing happens.

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

[clazy] [Bug 359305] false positives in container-anti-pattern

[Sergio Martins via KDE Bugzilla]

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

--- Comment #1 from Sergio Martins  ---
Your first example allocates once (due to keys() call), and it should allocate
0.
Use instead: for (auto it = someMap.cbegin(), end = someMap.cend(); it != end;
++it)

Your second example allocates twice (due to keys call) and it should allocate
once, construct the set manually instead.

This is what happens when you call keys():
template 
Q_OUTOFLINE_TEMPLATE QList QHash::keys() const
{
QList res;
res.reserve(size());
const_iterator i = begin();
while (i != end()) {
res.append(i.key());
++i;
}
return res;
}

You would be iterating twice instead of iterating the map directly.
I can update the README and make it more clear.

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

[i18n] [Bug 359318] kwebkitpart: "Verknüpfung- kopieren"

[Wolfgang Bauer via KDE Bugzilla]

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

--- Comment #1 from Wolfgang Bauer  ---
Sollte wohl eher "Verknüpfungs kopieren" heißen, denke ich...

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

[i18n] [Bug 359318] New: kwebkitpart: "Verknüpfung- kopieren"

[Wolfgang Bauer via KDE Bugzilla]

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

Bug ID: 359318
   Summary: kwebkitpart: "Verknüpfung- kopieren"
   Product: i18n
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: de
  Assignee: kde-i18n...@kde.org
  Reporter: wba...@tmo.at

#: src/webview.cpp:694
msgid "Copy Link "
msgstr "Verknüpfung- kopieren"


Reproducible: Always

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

[konsole] [Bug 354082] high cpu usage for screen redrawing with qt5.5

[Sven Brauch via KDE Bugzilla]

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

Sven Brauch  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #12 from Sven Brauch  ---
I also have not noticed improvements with this. it might be related to the
theme, I'll check.

I will set this to confirmed as several users are affected and I can clearly
link this issue to infinality on two machines.

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

[kdeconnect] [Bug 359312] New: Show notifications when reconnected

[Josef Kufner via KDE Bugzilla]

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

Bug ID: 359312
   Summary: Show notifications when reconnected
   Product: kdeconnect
   Version: unspecified
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: j...@frozen-doe.net

When WiFi on the phone is configured to disconnect when sleeping, KDE Connect
cannot maintain permanent connection. This is ok, but it brings a bit more
requirements on reconnecting.

When SMS arrives, the phone wakes up and reconnects to WiFi and then KDE
Connect reconnects too. Also the notifications are synchronized as expected.
But since the SMS arrived before the connection was restored, the notification
does not pop up on the desktop. KDE Connect should detect new notifications
after reconnecting, not only when notification is created.

Reproducible: Always

Steps to Reproduce:
0. Set wifi in your phone to sleep when not in charger.
1. Let phone sleep and wifi disconnect (it takes few minutes).
2. Receive SMS.
3. Plasmoid reconnects to phone.
4. SMS notification is in the plasmoid's list, but there is no notification
about the new notification.

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

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

[Alex Richardson via KDE Bugzilla]

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

--- Comment #19 from Alex Richardson  ---
Git commit bba0f034c4bdfdf9375b7532d134ef05214ce51b by Alex Richardson.
Committed on 12/02/2016 at 12:48.
Pushed by arichardson into branch '5.0'.

Don't add HintedType instances to UnsureType if the target type exists

But only do this if the HintedType also has the same context, otherwise
they might be invalidated at separate times and removing one of them
removes the still valid other HintedType.

If we don't deduplicate here we still get UnsureTypes which have lots
of entries like this:

found potential duplicates when adding N6Python10HintedTypeE int(index =
774764) ->
67278 - int of type N8KDevelop13StructureTypeE
102814 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type
N6Python10HintedTypeE
139700 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type
N6Python10HintedTypeE
140778 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type
N6Python10HintedTypeE
191576 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type
N6Python10HintedTypeE
206348 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type
N6Python10HintedTypeE
346692 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type
N6Python10HintedTypeE
351636 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type
N6Python10HintedTypeE
362174 (aka 351724: int of type N6Python10UnsureTypeE) - int of type
N6Python10HintedTypeE
386886 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type
N6Python10HintedTypeE
408898 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type
N6Python10HintedTypeE
533652 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type
N6Python10HintedTypeE
540306 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type
N6Python10HintedTypeE
573586 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type
N6Python10HintedTypeE
614644 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type
N6Python10HintedTypeE
618548 (aka 66042: bool of type N8KDevelop12IntegralTypeE) - bool of type
N6Python10HintedTypeE
648374 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type
N6Python10HintedTypeE
665250 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type
N6Python10HintedTypeE
709684 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type
N6Python10HintedTypeE
750432 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type
N6Python10HintedTypeE
89504 (aka 66548: str of type N8KDevelop13StructureTypeE) - str of type
N6Python10HintedTypeE
765024 (aka 90024: str of type N6Python10UnsureTypeE) - str of type
N6Python10HintedTypeE
774764 (aka 403436: int of type N6Python10UnsureTypeE) - int of type
N6Python10HintedTypeE

REVIEW: 127039

M  +6-0duchain/types/hintedtype.cpp
M  +2-0duchain/types/hintedtype.h
M  +38   -8duchain/types/unsuretype.cpp

http://commits.kde.org/kdev-python/bba0f034c4bdfdf9375b7532d134ef05214ce51b

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

[khelpcenter] [Bug 359316] do not show the documentation of k3b even I have looked for a package.

[Luigi Toscano via KDE Bugzilla]

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

--- Comment #2 from Luigi Toscano  ---
kdepim-doc has nothing to do with k3b.

Can you please add more details about the system? There is no KDE 4.4.1 in Mint
17.3. Please state the versions of k3b and khelpcenter (and the other details
in the about dialog, like version of kdelibs), and also the versions of all the
packages related to k3b
(quick way: paste the output of
dpkg -l '*k3b*'
)

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

[kdelibs] [Bug 359315] KNotify Crash during notifications

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---
Already reported as bug 359131.

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

[Akonadi] [Bug 335435] KMail System crash nach Eingabe Empfängerzeile

[Thomas Fischer via KDE Bugzilla]

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

Thomas Fischer  changed:

   What|Removed |Added

 CC||fisc...@unix-ag.uni-kl.de
 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1

--- Comment #3 from Thomas Fischer  ---
I may have encountered the same bug. My backtrace is slightly more informative:

Thread 1 (Thread 0x7f519cca1840 (LWP 6478)):
[KCrash Handler]
#6  0x in ?? ()
#7  0x7f51a20f1351 in ?? () from /usr/lib64/libxapian-1.3.so.4
#8  0x7f51a1ffce91 in
Xapian::Query::Internal::postlist_sub_or_like(Xapian::Internal::OrContext&,
QueryOptimiser*, double) const () from /usr/lib64/libxapian-1.3.so.4
#9  0x7f51a1ffe603 in ?? () from /usr/lib64/libxapian-1.3.so.4
#10 0x7f51a1ffe603 in ?? () from /usr/lib64/libxapian-1.3.so.4
#11 0x7f51a1ffe963 in ?? () from /usr/lib64/libxapian-1.3.so.4
#12 0x7f51a20f0495 in ?? () from /usr/lib64/libxapian-1.3.so.4
#13 0x7f51a20f5e3e in ?? () from /usr/lib64/libxapian-1.3.so.4
#14 0x7f51a1fedfde in Xapian::Enquire::Internal::get_mset(unsigned int,
unsigned int, unsigned int, Xapian::RSet const*, Xapian::MatchDecider const*)
const () from /usr/lib64/libxapian-1.3.so.4
#15 0x7f51a1fee38c in Xapian::Enquire::get_mset(unsigned int, unsigned int,
unsigned int, Xapian::RSet const*, Xapian::MatchDecider const*) const () from
/usr/lib64/libxapian-1.3.so.4
#16 0x7f51ae26f5ee in Akonadi::Search::PIM::ContactCompleter::complete
(this=this@entry=0x7ffd728dbb90) at
/var/tmp/portage/kde-apps/akonadi-search-15.12.1/work/akonadi-search-15.12.1/lib/contactcompleter.cpp:71
#17 0x7f51b5d49260 in KPIM::AddresseeLineEditPrivate::searchInBaloo
(this=this@entry=0x19840b0) at
/var/tmp/portage/kde-apps/libkdepim-15.12.1/work/kdepim-15.12.1/libkdepim/src/addressline/addresslineedit/addresseelineedit_p.cpp:224
#18 0x7f51b5d494f7 in
KPIM::AddresseeLineEditPrivate::slotTriggerDelayedQueries (this=0x19840b0) at
/var/tmp/portage/kde-apps/libkdepim-15.12.1/work/kdepim-15.12.1/libkdepim/src/addressline/addresslineedit/addresseelineedit_p.cpp:458
#19 0x7f51b5d4b079 in QtPrivate::FunctorCall,
QtPrivate::List<>, void, void (KPIM::AddresseeLineEditPrivate::*)()>::call(void
(KPIM::AddresseeLineEditPrivate::*)(), KPIM::AddresseeLineEditPrivate*, void**)
(arg=, o=, f=) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:501
#20 QtPrivate::FunctionPointer::call, void>
(arg=, o=, f=) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:520
#21 QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*,
void**, bool*) (which=, this_=, r=, a=, ret=) at
/usr/include/qt5/QtCore/qobject_impl.h:143
#22 0x7f51badfea53 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
#23 0x7f51bae0bcb8 in QTimer::timerEvent(QTimerEvent*) () from
/usr/lib64/libQt5Core.so.5
#24 0x7f51bae00043 in QObject::event(QEvent*) () from
/usr/lib64/libQt5Core.so.5
#25 0x7f51bbb0d69c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/libQt5Widgets.so.5
#26 0x7f51bbb12b10 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#27 0x7f51badd6d8d in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib64/libQt5Core.so.5
#28 0x7f51bae23d6d in QTimerInfoList::activateTimers() () from
/usr/lib64/libQt5Core.so.5
#29 0x7f51bae24279 in ?? () from /usr/lib64/libQt5Core.so.5
#30 0x7f51af7f58fd in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#31 0x7f51af7f5be0 in ?? () from /usr/lib64/libglib-2.0.so.0
#32 0x7f51af7f5c8c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#33 0x7f51bae24787 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#34 0x7f51badd59aa in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#35 0x7f51baddcd8c in QCoreApplication::exec() () from
/usr/lib64/libQt5Core.so.5
#36 0x00404579 in main (argc=1, argv=0x7ffd728dc548) at
/var/tmp/portage/kde-apps/kdepim-15.12.1/work/kdepim-15.12.1/kmail/main.cpp:151


I am using Gentoo Linux with Akonadi 15.12.1 (compiled with debug settings).
The used version of xapian is 1.3.3 (package revision r2 in Gentoo). I'll test
version 1.3.4 to see if there is a difference.
I am reopening this bug report if that is ok for you ...

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

[calligrastage] [Bug 359307] New: Animation Dialog Flickers when trying to preview an animation

[Third via KDE Bugzilla]

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

Bug ID: 359307
   Summary: Animation Dialog Flickers when trying to preview an
animation
   Product: calligrastage
   Version: 2.9.11
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: usability
  Assignee: t.zachm...@zagge.de
  Reporter: applesjar...@gmail.com

Mouse hover on an animation on the dialog while the automatic animation preview
is on causes the dialog to flicker.

Reproducible: Always

Steps to Reproduce:
1. Select an object e.g. text
2. Open animation tab
3. Open Add new animation Dialog
4. Mouse over to any animation of choice (with automatic animation preview
enabled)

Actual Results:  
The object flickers and the animation dialog flickers

Expected Results:  
preview the animation until the animation preview finishes

OS: Arch Linux
DE: Gnome

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

[korganizer] [Bug 359314] New: Folder property "Block reminders locally" doesn't work (at least for google calendars)

[Enrico Tagliavini via KDE Bugzilla]

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

Bug ID: 359314
   Summary: Folder property "Block reminders locally" doesn't work
(at least for google calendars)
   Product: korganizer
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: reminder daemon (korgac)
  Assignee: korganizer-de...@kde.org
  Reporter: enrico.tagliav...@gmail.com

Version of Korganizer (it's missing in the drop down list): 4.14.10
KDE Development Platform version: 4.14.14
OS: Fedora 22 fully up to date as of the time of this writing

Calendar is a Google calendar

Reproducible: Always

Steps to Reproduce:
1. Add a google calendar of type Google Calendar
2. Right click on its folder in the bottom left corner of the main interface of
korganizer and select Folder properties...
3. Check the "Block reminders locally" option

Actual Results:  
wait for the correct time and notice the reminder (being it email or display)
is actually dispatched

Expected Results:  
no notification should be shown for any reminder set in this calendar

The only workaround is to disable reminders by right clicking in the systray
icon, but this applies to all calendars, not only the one I want to ignore.

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

[kdeconnect] [Bug 359294] KDE Connect don't load translated string

[Albert Vaca via KDE Bugzilla]

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

Albert Vaca  changed:

   What|Removed |Added

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

--- Comment #2 from Albert Vaca  ---
We changed a typo in the english string, so the localization teams will have to
set the translation again. Until that happens, it is expected to see the
english string instead.

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

[khelpcenter] [Bug 359316] New: do not show the documentation of k3b even I have looked for a package.

[via KDE Bugzilla]

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

Bug ID: 359316
   Summary: do not show the documentation of k3b even I have
looked for a package.
   Product: khelpcenter
   Version: unspecified
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kde-doc-engl...@kde.org
  Reporter: hornung.l...@web.de

If I want have a look to the documentation of K3b, it shows a site
"Documentation not found". I have checked the possibilities of solution. To
install the package kdepim-doc was not the solution. In the Userbase is a
documentation available. Should it be so? Or its only forgotten?

Reproducible: Always

Steps to Reproduce:
1. Help -> Handbook of K3b
2.
3.

Actual Results:  
It shows the site "documentation not found"

Expected Results:  
It shows the documentation of K3b

I use 3 KDE-Programmes (and the necessary components of KDE 4.4.1) with Linux
Mint 17.3 Cinnamon and german Language-packs. With the documentation of the
other 2 programmes I have not any problem.

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

[khelpcenter] [Bug 359316] do not show the documentation of k3b even I have looked for a package.

[via KDE Bugzilla]

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

--- Comment #1 from hornung.l...@web.de ---
Created attachment 97164
  --> https://bugs.kde.org/attachment.cgi?id=97164=edit
screencapture

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

[frameworks-kinit] [Bug 352760] Desktop File setting 'system tray' causes error

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---


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

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

[systemsettings] [Bug 355711] System Settings crashed during exit processing.

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||claudio.canevarolo@cms-snc.
   ||it

--- Comment #23 from Christoph Feck  ---
*** Bug 359221 has been marked as a duplicate of this bug. ***

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

[systemsettings] [Bug 359221] Kde crash when closa Sistem settin

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---


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

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

[clazy] [Bug 359306] new check idea: avoid using Q_FOREACH to iterate over QMap/QHash keys and retrieve values inside loop

[Sergio Martins via KDE Bugzilla]

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

Sergio Martins  changed:

   What|Removed |Added

   Assignee|unassigned-b...@kde.org |smart...@kde.org

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

[clazy] [Bug 359306] new check idea: avoid using Q_FOREACH to iterate over QMap/QHash keys and retrieve values inside loop

[Sergio Martins via KDE Bugzilla]

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

Sergio Martins  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

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

[plasma-pk-updates] [Bug 359308] Dark text on dark background

[Fabian Vogt via KDE Bugzilla]

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

--- Comment #1 from Fabian Vogt  ---
Created attachment 97163
  --> https://bugs.kde.org/attachment.cgi?id=97163=edit
Dark font on dark background

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

[plasmashell] [Bug 359317] New: Two empty icon spaces show on the system tray

[via KDE Bugzilla]

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

Bug ID: 359317
   Summary: Two empty icon spaces show on the system tray
   Product: plasmashell
   Version: 5.5.4
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: 12949...@opayq.com

Two blank spaces show up on the system tray. They seem to show up one by one
some time after starting up, not at the same time. I haven't noticed anything
specific that causes this.

The first empty space seems to be related to same bug as
https://bugs.kde.org/show_bug.cgi?id=359139 and
https://bugs.kde.org/show_bug.cgi?id=358778 and the same workaround makes it
disappear. This one also appears on System Tray Settings -> Entries as an empty
entry and be hidden like an actual icon.

The second doesn't appear on the list and when right-clicked shows the System
Tray Settings/Panel Options Menu. It cannot be made to disappear in the ways
mentioned before.

Reproducible: Always

Steps to Reproduce:
1.Login into KDE,
2.Use the computer normally

Actual Results:  
Two blank spaces show up one by one on the system tray.

Expected Results:  
The the expected icons show up without empty space between them.

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

[ksystraycmd] [Bug 344168] there is no ksystray for plasma5

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||emre...@gmail.com

--- Comment #26 from Christoph Feck  ---
*** Bug 352760 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 359317] Two empty icon spaces show on the system tray

[via KDE Bugzilla]

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

--- Comment #1 from 12949...@opayq.com ---
Created attachment 97165
  --> https://bugs.kde.org/attachment.cgi?id=97165=edit
System tray screenshot

System tray screenshot showing both the blank spaces.

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

[frameworks-kdelibs4support] [Bug 359320] New: formatDateTime(..., KLocale::FancyShortDate, ... ) should take LC_TIME into account

[Arek Guzinski via KDE Bugzilla]

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

Bug ID: 359320
   Summary: formatDateTime(..., KLocale::FancyShortDate, ... )
should take LC_TIME into account
   Product: frameworks-kdelibs4support
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: ker...@ag.de1.cc

This is related to my bugreport for akregator 
https://bugs.kde.org/show_bug.cgi?id=359191 (theres a screenshot too), which
turned out to belong to a frameworks component. I hope this is the correct
component (probably not...), but after trying to find out which component
exactly this belongs to for about 40 minutes, i had enough and took my best
guess

with the following env...
LANGUAGE=en_US:de
LC_TIME=de_DE.UTF-8

akregator shows the time as "MM/DD/ hh:mm AM/PM", as opposed to "DD.MM.
hh:mm", which is what i would expect with LC_TIME=de_DE.UTF-8.

What i would expect , vs what i get is (examples)
Expected   | What i get
Yesterday 14:35 |  Yesterday 02:35 PM
29.01.2016 19:20  |   01/29/2016 07:20  PM

so in my opinion the function should translate the words based on LANGUAGE (as
it does), but the numeric part based on LC_TIME, as this would be consistent
with the Interface language being english and the date/time format being german

as a workaround, LANGUAGE=en_GB:de makes things a bit better for me

Reproducible: Always

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

[krita] [Bug 359255] OSX Japanese env: Krita3.0 prealpha assert on startup

[via KDE Bugzilla]

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

--- Comment #6 from guruguru...@outlook.jp ---
I think you need to add Japanese in OSX's System Preferences > Language & Text,
then put Japanese to the top of the preferred language list.(If I drag
"English" to the top of the list, crash does not happen)

For reference, similar "OSX Japanese locale crash" issue in other software.  
https://bugzilla.gnome.org/show_bug.cgi?id=683147
https://github.com/translate/virtaal/issues/3109

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

[okular] [Bug 359319] New: Can't open files with space in filename

[naraesk via KDE Bugzilla]

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

Bug ID: 359319
   Summary: Can't open files with space in filename
   Product: okular
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: m...@naraesk.eu

I cannot open file via clicking on them or via console if the filename or path
contains a space. There is just a popup "Could not open". However, if the file
is opened by file → open there isn't any problem at all.

See also: https://forum.kde.org/viewtopic.php?f=251=130914

I'm using the frameworks branch of okular. The bug was introduced with one of
the latest commits.
The bug was introduced with one of the latest commits.

Reproducible: Always

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

[klipper] [Bug 348390] (KF 5.10) sometimes Klipper does not activate selected entry

[Diego via KDE Bugzilla]

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

Diego  changed:

   What|Removed |Added

 CC||diego...@zoho.com

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

[plasmashell] [Bug 359046] Panel covers bottom part of maximized window after monitor is plugged out and in again

[sudden6 via KDE Bugzilla]

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

sudden6  changed:

   What|Removed |Added

 CC||thereisntausefuladdressleft
   ||@yahoo.com

--- Comment #10 from sudden6  ---
I can confirm this behaviour on a Thinkpad T440p with an external Monitor
connected (1920x1080, VGA).
The panel sometimes overlaps fullscreen windows.

OS: openSUSE Leap 42.1
Kernel: 4.3.0
X.org: 1.17.2
Mesa: 11.0.8 with Intel Haswell

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

[systemsettings] [Bug 359322] New: fontinst: improve family and style filter (serif, bold, italic, …)

[Christian Stadelmann via KDE Bugzilla]

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

Bug ID: 359322
   Summary: fontinst: improve family and style filter (serif,
bold, italic, …)
   Product: systemsettings
   Version: 5.5.4
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: kcm_fontinst
  Assignee: unassigned-b...@kde.org
  Reporter: dah5a...@genodeftest.de

Filtering on family does only work if font name includes the property.

Reproducible: Always

Steps to Reproduce:
1. open kcmshell5 fontinst
2. look through fonts, note some serif fonts
3. search for "serif" in "Family" and "Style"
4. compare outputs

Actual Results:  
Searching for "serif" doesn't match all serif fonts. Instead only fonts are
displayed where the font name matches "serif"

Expected Results:  
Searching for "serif" should present all serif fonts.

This issue also applies to mono(space), sans( serif), …

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

[plasmashell] [Bug 359302] New: KDE Plasma Shell randomly crashing frequently on openSuSE Tumbleweed

[via KDE Bugzilla]

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

Bug ID: 359302
   Summary: KDE Plasma Shell randomly crashing frequently on
openSuSE Tumbleweed
   Product: plasmashell
   Version: 5.5.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: tl_web...@outlook.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.3)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-3-default x86_64
Distribution: "openSUSE Tumbleweed (20160209) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Crash seems to occur randomly regardless of what I was doing. But seem to crash
more often when I carry out any of the following actions:
- Switch Virtual Desktop (I have 3 virtual desktops)
- Moving in/out of VirtualBox window running openSUSE (Note: I am running
openSUSE Tumbleweed inside a VirtualBox VM running under Windows 7).

The crash can be reproduced every time.

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

Thread 12 (Thread 0x7fd9cf182700 (LWP 3850)):
#0  0x7fd9def9eb7d in recvmsg () at /lib64/libc.so.6
#1  0x7fd9e3e6c4c7 in  () at /usr/lib64/libxcb.so.1
#2  0x7fd9e3e6a6a1 in  () at /usr/lib64/libxcb.so.1
#3  0x7fd9e3e6c007 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#4  0x7fd9d12d1e29 in  () at /usr/lib64/libQt5XcbQpa.so.5
#5  0x7fd9df68594f in  () at /usr/lib64/libQt5Core.so.5
#6  0x7fd9de79c4a4 in start_thread () at /lib64/libpthread.so.0
#7  0x7fd9def9dbdd in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7fd9c7fff700 (LWP 3855)):
#0  0x7fd9def9122d in read () at /lib64/libc.so.6
#1  0x7fd9db6cc290 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fd9db689dc4 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fd9db68a238 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7fd9db68a39c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7fd9df8aa52b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7fd9df85463a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7fd9df680b1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7fd9e29509a5 in  () at /usr/lib64/libQt5Qml.so.5
#9  0x7fd9df68594f in  () at /usr/lib64/libQt5Core.so.5
#10 0x7fd9de79c4a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7fd9def9dbdd in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7fd9b9fd2700 (LWP 3868)):
#0  0x7fd9de7a207f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fd9c4acc133 in  () at /usr/lib64/dri/swrast_dri.so
#2  0x7fd9c4acbfb7 in  () at /usr/lib64/dri/swrast_dri.so
#3  0x7fd9de79c4a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fd9def9dbdd in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7fd9b97d1700 (LWP 3869)):
#0  0x7fd9de7a207f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fd9c4acc133 in  () at /usr/lib64/dri/swrast_dri.so
#2  0x7fd9c4acbfb7 in  () at /usr/lib64/dri/swrast_dri.so
#3  0x7fd9de79c4a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fd9def9dbdd in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7fd9b8fd0700 (LWP 3870)):
#0  0x7fd9de7a207f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fd9c4acc133 in  () at /usr/lib64/dri/swrast_dri.so
#2  0x7fd9c4acbfb7 in  () at /usr/lib64/dri/swrast_dri.so
#3  0x7fd9de79c4a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fd9def9dbdd in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7fd9b87cf700 (LWP 3871)):
#0  0x7fd9de7a207f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fd9c4acc133 in  () at /usr/lib64/dri/swrast_dri.so
#2  0x7fd9c4acbfb7 in  () at /usr/lib64/dri/swrast_dri.so
#3  0x7fd9de79c4a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fd9def9dbdd in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7fd9b2935700 (LWP 3874)):
#0  0x7fd9df8a9974 in  () at /usr/lib64/libQt5Core.so.5
#1  0x7fd9db6898bd in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fd9db68a1c3 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fd9db68a39c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fd9df8aa52b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fd9df85463a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fd9df680b1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fd9e29509a5 in  () at /usr/lib64/libQt5Qml.so.5
#8  

[frameworks-kglobalaccel] [Bug 341959] kwin shortcuts don't work when using meta + shift +

[darx via KDE Bugzilla]

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

darx  changed:

   What|Removed |Added

 CC|d...@sent.com   |

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

[plasmashell] [Bug 359282] Plasma Crash on search

[Ben Klopfenstein via KDE Bugzilla]

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

--- Comment #2 from Ben Klopfenstein  ---
I have managed to cause plasma to hang for a while (15 seconds or
more) by typing into the Application Launcher, but I only actually got
the crash once.

It might be relevant that I have 4 screens and 4 panels, each with an
application launcher. I'm on OpenSuse Tumbleweed, and for the last few
days when I come in in the morning, Plasmashell is chewing up ~ 24 GB
of memory (my system has 32) and slightly more than 1 CPU core. I'm
not sure if these problems are related, but they seem to have started
occurring at the same time.

On Thu, Feb 11, 2016 at 12:45 PM, David Edmundson via KDE Bugzilla
 wrote:
> https://bugs.kde.org/show_bug.cgi?id=359282
>
> David Edmundson  changed:
>
>What|Removed |Added
> 
>  Resolution|--- |WAITINGFORINFO
>  Status|UNCONFIRMED |NEEDSINFO
>
> --- Comment #1 from David Edmundson  ---
> Can you reproduce the problem if you do it again?
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[systemsettings] [Bug 359326] New: plantage app configuration système

[via KDE Bugzilla]

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

Bug ID: 359326
   Summary: plantage app configuration système
   Product: systemsettings
   Version: 5.4.1
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: bho...@gmail.com

Application: systemsettings5 (5.4.1)

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

-- Information about the crash:
- What I was doing when the application crashed:
ouvrir configuration du systeme
clicker sur apparence des applications
clicker sur décoration des fenetres > plantage

plantage certainement du a une nouvelle deco , mais je ne sais pas la quelle.

The crash can be reproduced every time.

-- Backtrace:
Application: Configuration du système (systemsettings5), signal: Segmentation
fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f12a459c800 (LWP 2243))]

Thread 5 (Thread 0x7f1291c87700 (LWP 2244)):
#0  0x7f12a0d408dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f129ea50bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f129ea5274f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f1294a51a39 in QXcbEventReader::run (this=0x13737a0) at
qxcbconnection.cpp:1105
#4  0x7f12a14332be in QThreadPrivate::start (arg=0x13737a0) at
thread/qthread_unix.cpp:337
#5  0x7f129d361754 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#6  0x7f129e1db6aa in start_thread (arg=0x7f1291c87700) at
pthread_create.c:333
#7  0x7f12a0d4beed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f128236f700 (LWP 2247)):
#0  __libc_enable_asynccancel () at
../sysdeps/unix/sysv/linux/x86_64/cancellation.S:65
#1  0x7f12a0d408d2 in poll () at ../sysdeps/unix/syscall-template.S:81
#2  0x7f129dcbc1ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f129dcbc2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f12a166a29b in QEventDispatcherGlib::processEvents
(this=0x7f127c0008f0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f12a161075a in QEventLoop::exec (this=this@entry=0x7f128236ece0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f12a142e3d4 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7f129fdb7f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f12a14332be in QThreadPrivate::start (arg=0x13638b0) at
thread/qthread_unix.cpp:337
#9  0x7f129d361754 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#10 0x7f129e1db6aa in start_thread (arg=0x7f128236f700) at
pthread_create.c:333
#11 0x7f12a0d4beed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f127a7e7700 (LWP 2248)):
#0  0x7f129dd00869 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f129dcbb9a1 in g_main_context_query () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f129dcbc167 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f129dcbc2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f12a166a29b in QEventDispatcherGlib::processEvents
(this=0x7f12740008f0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f12a161075a in QEventLoop::exec (this=this@entry=0x7f127a7e6ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f12a142e3d4 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7f129fdb7f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f12a14332be in QThreadPrivate::start (arg=0x1e71900) at
thread/qthread_unix.cpp:337
#9  0x7f129d361754 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#10 0x7f129e1db6aa in start_thread (arg=0x7f127a7e7700) at
pthread_create.c:333
#11 0x7f12a0d4beed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f1273fff700 (LWP 2249)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f12a143455b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x2699310) at
thread/qwaitcondition_unix.cpp:136
#2  QWaitCondition::wait (this=, mutex=0x2692520,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:208
#3  0x7f12a0073b3e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7f12a00743c3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f12a14332be in QThreadPrivate::start (arg=0x26924a0) at
thread/qthread_unix.cpp:337
#6  0x7f129d361754 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#7  0x7f129e1db6aa in start_thread (arg=0x7f1273fff700) at
pthread_create.c:333
#8  0x7f12a0d4beed in clone () at

[frameworks-kglobalaccel] [Bug 341959] kwin shortcuts don't work when using meta + shift +

[darx via KDE Bugzilla]

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

--- Comment #57 from darx  ---
Ok, so it's not this either.

Fact is, 'KDE Shortcuts' don't work.  Add they haven't consistently since KDE4.
 Full stop.

That there's a 1000 reasons, and a 1000 bugs filed, helps noone.  Neither does
kicking it upstream to Qt5 where it gets ignored some more.  All it does it
hurts KDE and its users.

This will never get fixed/addressed unless/until some capable dev 'owns' KDE
Shortcuts again.

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

[kleopatra] [Bug 358666] Short dates are used everywhere in the UI

[Andre Heinecke via KDE Bugzilla]

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

Andre Heinecke  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Andre Heinecke  ---
Kleopatra uses QLocale::ShortFormat for dates. You should see the same date
format in other KDE Applications and you can configure this in your system.

Just try it out from the command line:
LC_ALL=de_DE.UTF-8 kleopatra
should show different formats then
LC_ALL=C kleopatra

I think this is the correct behavior respecting the users settings.

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

[bugs.kde.org] [Bug 340420] Make it easier to file issue reports

[Arek Guzinski via KDE Bugzilla]

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

Arek Guzinski  changed:

   What|Removed |Added

 CC||ker...@ag.de1.cc

--- Comment #9 from Arek Guzinski  ---
While i agree that finding the product works well for a specific application,
it does not for bugs that appear in multiple applications (aka bugs in the
frameworks). This is made even worse by having kde 4&5 stuff mixed together.

I propose the following changes:

add a checkbox "show deprecated products"
and/or
add columns to the table, which show in which version of kde it is used

add the Line "If you are unsure, choose kde" at the bottom of the table. This
way it will be visible, after trying to find the right product, but not
encourage people to use it every time.
I remember that i did not file at least one bug in the past, because i could
not find the right product and did not see the "kde" category.

If you click the "search" link from
https://bugs.kde.org/enter_bug.cgi?product=productname , the product should be
preselected.

sometimes i knew which api call causes a problem (through debug output, stack
trace, alook into the applications source code, etc..). However, finding to
which part of frameworks it belongs, is not that easy. it would be great if you
could search for an api call. Or simply find the product name in the api
reference.

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

[i18n] [Bug 359318] kwebkitpart: "Verknüpfung- kopieren"

[Frederik Schwarzer via KDE Bugzilla]

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

Frederik Schwarzer  changed:

   What|Removed |Added

 CC||schwar...@kde.org

--- Comment #3 from Frederik Schwarzer  ---
Hehe, zumindest hast du gerade sehr gut gezeigt, wie schnell sich kleinere
Tippfehlerchen einschleichen. :D

Danke für den Hinweis, das schaue ich mir heute Abend an.

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

[Baloo] [Bug 359325] New: Baloo crashes on log-in again

[via KDE Bugzilla]

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

Bug ID: 359325
   Summary: Baloo crashes on log-in again
   Product: Baloo
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: m...@vhanda.in
  Reporter: basu12...@gmail.com
CC: pinak.ah...@gmail.com

Application: baloo_file (5.16.0)

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

-- Information about the crash:
- What I was doing when the application crashed:
I reported that baloo crashed inmediatly after log-in into plasma. I can
confirm that the situation happens every time.

The crash can be reproduced every time.

-- 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 0x7faa9c2ef780 (LWP 2390))]

Thread 2 (Thread 0x7fa95007f700 (LWP 4377)):
#0  0x7faa99e2dc1d in poll () at /lib64/libc.so.6
#1  0x7faa9686de64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7faa9686df7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7faa9aa58d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7faa9a9ffd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x00422845 in Baloo::FileContentIndexer::run() ()
#6  0x7faa9a823382 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7faa9a82632f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7faa98e680a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7faa99e3604d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7faa9c2ef780 (LWP 2390)):
[KCrash Handler]
#6  0x7faa97b5925c in mdb_get () at /usr/lib64/liblmdb-0.9.14.so
#7  0x7faa9b0f192d in Baloo::IdTreeDB::get(unsigned long long) () at
/usr/lib64/libKF5BalooEngine.so.5
#8  0x7faa9b0eeca0 in Baloo::DocumentUrlDB::getId(unsigned long long,
QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5
#9  0x7faa9b1003e9 in Baloo::Transaction::documentId(QByteArray const&)
const () at /usr/lib64/libKF5BalooEngine.so.5
#10 0x0042a923 in
Baloo::MetadataMover::removeMetadata(Baloo::Transaction*, QString const&) ()
#11 0x0042a9dd in Baloo::MetadataMover::removeFileMetadata(QString
const&) ()
#12 0x7faa9aa3173f in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#13 0x00434405 in Baloo::PendingFileQueue::removeFileIndex(QString
const&) ()
#14 0x00428bc6 in Baloo::PendingFileQueue::processCache() ()
#15 0x7faa9aa3173f in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#16 0x7faa9aa3ef22 in QTimer::timerEvent(QTimerEvent*) () at
/usr/lib64/libQt5Core.so.5
#17 0x7faa9aa328bc in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#18 0x7faa9aa0218d in QCoreApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Core.so.5
#19 0x7faa9aa01e95 in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#20 0x7faa9aa5877d in QTimerInfoList::activateTimers() () at
/usr/lib64/libQt5Core.so.5
#21 0x7faa9aa58aa1 in  () at /usr/lib64/libQt5Core.so.5
#22 0x7faa9686dc84 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#23 0x7faa9686ded8 in  () at /usr/lib64/libglib-2.0.so.0
#24 0x7faa9686df7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#25 0x7faa9aa58d6c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#26 0x7faa9a9ffd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#27 0x7faa9aa078f6 in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#28 0x00417d92 in main ()

Possible duplicates by query: bug 359292, bug 359276, bug 359239, bug 358962,
bug 358585.

Reported using DrKonqi

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

[plasmashell] [Bug 359324] New: plasmashell often hangs randomly, sometimes with broken window preview

[sudden6 via KDE Bugzilla]

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

Bug ID: 359324
   Summary: plasmashell often hangs randomly, sometimes with
broken window preview
   Product: plasmashell
   Version: 5.5.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: thereisntausefuladdressl...@yahoo.com
CC: bhus...@gmail.com, plasma-b...@kde.org

plasmashell hangs at least every hour for an unknown reason. Kwin is still
running and working as expected, I can move windows, switch through them with
Alt+Tab and run commands from krunner (Alt+F2). I can't click anything on the
panel, it simply doesn't react. Sometimes as plasmashell hangs it shows a
broken preview in the taskbar, but I don't have a screenshot of this.

To workaround this I can kill plasmashell and restart it and it continues to
work for a time.

If I run plasmashell in a konsole window, the output doesn't show anything
directly related with the hang. But I get errors like:

QXcbConnection: XCB error: 2 (BadValue), sequence: 8291, resource id:
140509189, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 8370, resource id:
125829124, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 2 (BadValue), sequence: 8439, resource id: 18874372,
major code: 142 (Unknown), minor code: 3

If I move the mouse pointer over a tab in the taskbar.

I made a core dump with gcore, but I'm not sure if I should upload it.
(compressed 13,2MB, uncompressed 3,2GB).


Reproducible: Sometimes




OS: openSUSE Tumbleweed (20160209) (x86_64)
Kernel: 4.4.0
plasmashell 5.5.3
X.Org X Server 1.18.0
OpenGL renderer string: Gallium 0.4 on AMD KAVERI (DRM 2.43.0, LLVM 3.7.0)
OpenGL core profile version string: 4.1 (Core Profile) Mesa 11.1.1
OpenGL core profile shading language version string: 4.10

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

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

[darx via KDE Bugzilla]

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

--- Comment #10 from darx  ---
Still an issue in plasma5-workspace  v5.5.4

Not having the option to see/view a lockup/high-load of single cores makes this
widget not useful on multicore devices -- especially important if running VMs,
where specific cores are dedicated to specific tasks.

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

[krita] [Bug 351059] Krita crashes while using Brush tool, issues with genius tablet driver

[Boudewijn Rempt via KDE Bugzilla]

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

--- Comment #8 from Boudewijn Rempt  ---
Does the 3.0 alpha still crash? That has an updated tablet handling
implementation. Otherwise, without someone donating test hardware, there's not
so much we can do :-(

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

[kdeconnect] [Bug 336043] SFTP: Should be able to browse external SD cards via SFTP too

[akhilesh via KDE Bugzilla]

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

akhilesh  changed:

   What|Removed |Added

 CC||akhil...@openmailbox.org

--- Comment #37 from akhilesh  ---
I experience this bug as well.

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

[krita] [Bug 359298] crash while use Genius MX-712 tablet (click, move pen, while focus on Krita window)

[Snuux via KDE Bugzilla]

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

Snuux  changed:

   What|Removed |Added

 CC||sn...@yandex.ru

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

[ark] [Bug 359323] Ark should preview XML files in a text viewer, not a web browser

[Elvis Angelaccio via KDE Bugzilla]

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

Elvis Angelaccio  changed:

   What|Removed |Added

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

--- Comment #1 from Elvis Angelaccio  ---
Hi, this has been fixed since the Application 15.12 release. Ark now always
previews XML files in the Kate part.

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

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

[ark] [Bug 201162] XML document preview doesn't work

[Elvis Angelaccio via KDE Bugzilla]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||k...@dhardy.name

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

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

[ark] [Bug 359323] Ark should preview XML files in a text viewer, not a web browser

[Diggory Hardy via KDE Bugzilla]

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

--- Comment #2 from Diggory Hardy  ---
Awesome. Great that someone took on Ark development!

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

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

[darx via KDE Bugzilla]

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

darx  changed:

   What|Removed |Added

 CC||d...@sent.com

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

[frameworks-kglobalaccel] [Bug 341959] kwin shortcuts don't work when using meta + shift +

[darx via KDE Bugzilla]

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

darx  changed:

   What|Removed |Added

 CC||d...@sent.com

--- Comment #55 from darx  ---
Where was this 'fixed'?

Still a problem here, and elsewhere
(https://marc.info/?l=kde=145469233519878=2)

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

[i18n] [Bug 359318] kwebkitpart: "Verknüpfung- kopieren"

[Frederik Schwarzer via KDE Bugzilla]

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

Frederik Schwarzer  changed:

   What|Removed |Added

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

--- Comment #4 from Frederik Schwarzer  ---
SVN commit 1452545 by schwarzer:

Fix translation.

Thanks Wolfgang Bauer for the report.


 M  +5 -5  kwebkitpart.po  


WebSVN link: http://websvn.kde.org/?view=rev=1452545

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

[frameworks-kglobalaccel] [Bug 341959] kwin shortcuts don't work when using meta + shift +

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #56 from Thomas Lübking  ---
No, it's not.

See comment #33 on the fixing commit; it's in kglobalaccel 5.16.

The linked mailing list post apparently describes bug #353781 which is a Qt5
bug.
The invocation of a global shortcut has nothing to do with the active window
(except for window rules to suppress them, but that's not it either)

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

[krita] [Bug 359298] crash while use Genius MX-712 tablet (click, move pen, while focus on Krita window)

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||b...@valdyas.org
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Boudewijn Rempt  ---
Hi,

Thank you for your report. We're already tracking the issue here:
https://bugs.kde.org/show_bug.cgi?id=351059. Some users report that the 3.0
alpha is working for them, could you check?

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

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

[krita] [Bug 351059] Krita crashes while using Brush tool, issues with genius tablet driver

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||sn...@yandex.ru

--- Comment #9 from Boudewijn Rempt  ---
*** Bug 359298 has been marked as a duplicate of this bug. ***

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

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

[André Fettouhi via KDE Bugzilla]

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

Bug ID: 359327
   Summary: Exiting game a in Steam Big Picture Mode gets
semi-windowed BPM
   Product: Planet KDE
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ranveeraggar...@gmail.com
  Reporter: a.fetto...@gmail.com

I'm running Steam on my Arch Linux 64 bit box with a i7-2600k board and GTX 580
card and the latest Nvidia drivers (as of this writing I'm using 361.28). As my
desktop I'm using KDE Plasma 5 also latest stable version available. I bought a
Steam Controller a couple of months and I've been using it as my main
controller with Steam Big Picture Mode. I've noticed with every game I run that
if start the game from BPM that when I exit the game BPM is no longer in
fullscreen and the statusbar is suddenly visible below and I have to click in
the icon in the statusbar to make it go fullscreen. Not a huge issue but
annoying.

Reproducible: Always

Steps to Reproduce:
1. Start Steam
2. Start Big Picture Mode
3. Start a game
4. Exit game

Actual Results:  
BPM was in a semi-windowed mode with KDE statusbar visible.

Expected Results:  
BPM should fullscreen after exit of game.

Has been also reported on Steam Linux's github page and they suggested that it
I file it here as well. See link below:

https://github.com/ValveSoftware/steam-for-linux/issues/4313

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

[frameworks-kglobalaccel] [Bug 341959] kwin shortcuts don't work when using meta + shift +

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #60 from Thomas Lübking  ---
qed.

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

[frameworks-kglobalaccel] [Bug 341959] kwin shortcuts don't work when using meta + shift +

[pgnet via KDE Bugzilla]

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

pgnet  changed:

   What|Removed |Added

 CC|pgnet.dev+...@gmail.com |

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

[frameworks-kglobalaccel] [Bug 341959] kwin shortcuts don't work when using meta + shift +

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #58 from Thomas Lübking  ---
"Fact is" that you made a pretty bold statement without the least knowledge,
understanding or ability to read context and are now approaching a pretty poor
aggressive attempt to bail out, yet just re-expose your defects: That bug is,
as written, a bug in Qt5 - it has nothing to do with KDE nor even with
shortcuts; Qt5 deals synthetic events wrongly by accounting the HW modifier
state instead of the logic one. That those synthetic events are triggered by a
shortcut in the particular case is completely irrelevant.

I suggest to shut up now until you can make informed comments instead of
continuing that self embarrassment.

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

[frameworks-kglobalaccel] [Bug 341959] kwin shortcuts don't work when using meta + shift +

[darx via KDE Bugzilla]

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

darx  changed:

   What|Removed |Added

 CC||d...@sent.com

--- Comment #59 from darx  ---
You're funny!

Good luck with your broken POS.

p.s.

Try ESL ...

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

[apper] [Bug 359330] New: Series of "Update Error" messages every few hours (sometimes more often)

[via KDE Bugzilla]

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

Bug ID: 359330
   Summary: Series of "Update Error" messages every few hours
(sometimes more often)
   Product: apper
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dantt...@gmail.com
  Reporter: 12949...@opayq.com

Every few hours (sometimes more often) appear a series of Update Error messages
with the following text: 
"The task was forcibly canceled The[sic] Task was canceled successfully and no
packages were changed. The backend did not exit cleanly."

This is always repeated three times but it seems a new message appears when the
first one disappears, so there may be more than 3 error messages emitted at the
same time.

When this happens I am still able to refresh the repositories and update
packages with zypper, so there doesn't seem to be any problem accessing the
repositories.

The software update still shows available updates and updates packages without
any problem.

Reproducible: Always

Steps to Reproduce:
1. Using the computer normally, without worrying about updates.

Actual Results:  
Often Update Errorr messages appear.

Expected Results:  
Apper working in the background without errors or error messages.

Version 0.9.2, according to apper's about dialogue

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

[frameworks-plasma] [Bug 357895] Regression: KDE Plasma with KF 5.18 crash, if mouse repeatedly hovers over TaskManager

[via KDE Bugzilla]

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

fortymilesh...@gmail.com changed:

   What|Removed |Added

 CC||fortymilesh...@gmail.com

--- Comment #37 from fortymilesh...@gmail.com ---
This appears to occur when you hover over and the preview fades in, then mouse
stops hovering before it completely fades in.

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

[kdeplasma-addons] [Bug 359328] New: Plasma 5 weather applet does not truncate "Weather forecast from..." link, looks distorted on hidpi text scaling

[via KDE Bugzilla]

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

Bug ID: 359328
   Summary: Plasma 5 weather applet does not truncate "Weather
forecast from..." link, looks distorted on hidpi text
scaling
   Product: kdeplasma-addons
   Version: 5.5.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: plasma-b...@kde.org
  Reporter: johnsc...@aol.com

On the bottom of the weather widget dialog, the link "Weather forecast from..."
on the bottom does not truncate.
Therefore, when hidpi text is applied, the text looks distorted.
Here is a screenshot:
https://i.imgur.com/X5smq49.png

Reproducible: Always

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

[ksystraycmd] [Bug 344168] there is no ksystray for plasma5

[Juan Simón via KDE Bugzilla]

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

Juan Simón  changed:

   What|Removed |Added

 CC|deced...@gmail.com  |

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

[kdeplasma-addons] [Bug 359329] New: Dialog for adding OWM weather applet location should be wrapped when using text scaling

[via KDE Bugzilla]

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

Bug ID: 359329
   Summary: Dialog for adding OWM weather applet location should
be wrapped when using text scaling
   Product: kdeplasma-addons
   Version: 5.5.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: General
  Assignee: plasma-b...@kde.org
  Reporter: johnsc...@aol.com

When using text scaling in the hidpi settings, see the weather applet settings
When you add a location using OWM, the example given:
"e.g. http://www.openweathermap.org/city/2946447 for Bonn, Germany."
This line is cut off. See the screenshot below.
This should be wrapped for hi resolution text settings.
An obvious workaround would be to drag the dialog wider.

Screenshot:
https://i.imgur.com/0J4ZtgG.png

Reproducible: Always

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

[Baloo] [Bug 333774] Add fine tuning to baloo indexing process

[akhilesh via KDE Bugzilla]

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

akhilesh  changed:

   What|Removed |Added

 CC||akhil...@openmailbox.org

--- Comment #4 from akhilesh  ---
I face this bug too, it's horrible. Running "balooctl check" reproduces this
issue everytime.

This bug does not happen with GTK based desktops when using synapse(updatedb?).
I assume if that has the ability to index all the files without lagging, then
so should baloo.

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

[calligrawords] [Bug 359293] Some text is hidden - usually top paragraph.

[Camilla Boemann via KDE Bugzilla]

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

Camilla Boemann  changed:

   What|Removed |Added

 CC||c...@boemann.dk

--- Comment #1 from Camilla Boemann  ---
What version are you using, because this bug should be fixed for almost a year
now

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

[kdenlive] [Bug 359219] 15.13.0 git master - Timeline track header clean-up: (1) center track titles by default? (2) Change mouse-click behavior of track titles?

[via KDE Bugzilla]

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

--- Comment #6 from wegwerf-1-...@gmx.de ---
Lives actually seem to left justify according to your screenshot.

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

[systemsettings] [Bug 359326] plantage app configuration système

[via KDE Bugzilla]

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

bho...@gmail.com changed:

   What|Removed |Added

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

--- Comment #1 from bho...@gmail.com ---
remove windows decoration files Bailero did the trick :
rm -fr ~/.local/share/aurorae/themes/Bailero
so an issue with this windows decoration (downloaded from system configurator) 
?

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

[kdenlive] [Bug 359219] 15.13.0 git master - Timeline track header clean-up: (1) center track titles by default? (2) Change mouse-click behavior of track titles?

[via KDE Bugzilla]

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

--- Comment #5 from wegwerf-1-...@gmx.de ---
@Jesse, thank you very much for the screenshot ... now I see we are talking
about completely different types of track titles: your screenshots show terse
track titles, such as v1, v2, etc.

However, I was talking about descriptive, meaningful titles, such as "Company
Logo", "Title", "Paper", "Screencast", "Presenter", "Voice Over", etc.

I see that centering terse titles may look appealing, but if you do that to
descriptive titles as I use them throughout my project it looks awful when
centered. I have around five to eight, nine tracks in my projects, so I need
descriptive titles. And quickly reading centered text doesn't work as well as
quickly reading left justified text in western languages.

Furthermore, I don't see why gradient effects for track headers should make
software appear more polished, in fact, my own impression is that gradients in
track titles show lack of professionalism in UI design. But just my own two
cents.

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

[frameworks-kglobalaccel] [Bug 341959] kwin shortcuts don't work when using meta + shift +

[Andrew Rodland via KDE Bugzilla]

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

--- Comment #61 from Andrew Rodland  ---
Does it really matter whose bug it is? If Qt5 isn't a usable platform for doing
such simple things, then KDE 5 either shouldn't have used Qt5, or shouldn't
have been released as stable until the thing actually worked. Shortcuts were
broken for over a year after the "stable" release of KDE 4, and now they've
been broken for a year and a half since the "stable" release of KDE 5. And it's
not an isolated thing — every time a component is rewritten to use the
framework de jour, it comes back less functional and with more bugs. And then
it's released anyway despite all of the regressions. It's a miserably
dysfunctional system.

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

[digikam] [Bug 234546] Preview fails for some images [patch]

[Maik Qualmann via KDE Bugzilla]

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

Maik Qualmann  changed:

   What|Removed |Added

Summary|Preview fails for some  |Preview fails for some
   |images  |images [patch]

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

[kaddressbook] [Bug 357374] Huge Skype and Google Talk icons in Contacts panel view

[Laurent Montel via KDE Bugzilla]

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

Laurent Montel  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/kdep
   ||im-apps-libs/b11fcb0639921d
   ||f8353345e006cef463ec01c382
 Resolution|--- |FIXED
   Version Fixed In||5.1.3

--- Comment #5 from Laurent Montel  ---
Git commit b11fcb0639921df8353345e006cef463ec01c382 by Montel Laurent.
Committed on 12/02/2016 at 19:58.
Pushed by mlaurent into branch 'master'.

Fix Bug 357374 - Huge Skype and Google Talk icons in Contacts panel view
FIXED-IN: 5.1.3

M  +1-1kaddressbookgrantlee/src/formatter/grantleecontactformatter.cpp

http://commits.kde.org/kdepim-apps-libs/b11fcb0639921df8353345e006cef463ec01c382

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

[ktorrent] [Bug 358826] scientific notation in percentage completion and problems with the .desktop file

[Omar Plummer via KDE Bugzilla]

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

Omar Plummer  changed:

   What|Removed |Added

 CC||omarplummer@imergetechnolog
   ||ies.com

--- Comment #1 from Omar Plummer  ---
Seen here as well, on:

Ktorrent 5.0dev (built from git)
KDE Frameworks 5.19.0 (built from git)
Qt 5.6.0 (built from git)

If can confirm that if I edit the file
$KF5/share/applications/org.kde.ktorrent.desktop and change the line:

Exec=ktorrent %i -caption %c %u

to

Exec=ktorrent %i %c %u

I am then able to start ktorrent from krunner and from the menu.

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

[amarok] [Bug 357634] Cover Art does not update while playing

[sederic via KDE Bugzilla]

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

--- Comment #7 from sederic  ---
Amarok does also not inform dbus about this change. Maybe this is the
mistake...

Interesting is, that sometimes (or always?) the album cover for the track
appears in the playlist (on the right side)

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

[krita] [Bug 351059] Krita crashes while using Brush tool, issues with genius tablet driver

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||3.0
 Resolution|--- |FIXED

--- Comment #11 from Boudewijn Rempt  ---
Okay, then I'll close this bug. 2.9 won't in all likelihood get any more
updates since we're really focusing on getting 3.0 out now.

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

[plasmashell] [Bug 359340] New: thumbnail crash

[Paolo Achdjian via KDE Bugzilla]

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

Bug ID: 359340
   Summary: thumbnail crash
   Product: plasmashell
   Version: 5.5.4
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: pachdj...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.4)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-aufs-r1 x86_64
Distribution: "Gentoo Base System release 2.2"

-- Information about the crash:
Every time that I pass the mouse over the task bar on the bottom, plasma try to
create a thumbnail but it crashes every time.
I try to change the rendering backend, but the result is always the same. Also
the backtrace is the same.
My distribution is a gentoo.

The crash can be reproduced every time.

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

Thread 7 (Thread 0x7f808248d700 (LWP 9626)):
#0  0x7f8090e69abd in poll () from /lib64/libc.so.6
#1  0x7f8095049b22 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f809504bde9 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f80839b8969 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f80915490e2 in QThreadPrivate::start (arg=0x12ef920) at
thread/qthread_unix.cpp:331
#5  0x7f8090679494 in start_thread () from /lib64/libpthread.so.0
#6  0x7f8090e72afd in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f807b3ea700 (LWP 9638)):
#0  0x7f8090e69abd in poll () from /lib64/libc.so.6
#1  0x7f808ce3db5c in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f808ce3dc6c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f8091739dcb in QEventDispatcherGlib::processEvents
(this=0x7f80740008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f80916ebd2a in QEventLoop::exec (this=this@entry=0x7f807b3e9de0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f8091544ab4 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7f8093ea30b5 in ?? () from /usr/lib64/libQt5Qml.so.5
#7  0x7f80915490e2 in QThreadPrivate::start (arg=0x13a2360) at
thread/qthread_unix.cpp:331
#8  0x7f8090679494 in start_thread () from /lib64/libpthread.so.0
#9  0x7f8090e72afd in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f8072551700 (LWP 9639)):
#0  0x7f8090e69abd in poll () from /lib64/libc.so.6
#1  0x7f808ce3db5c in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f808ce3dc6c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f8091739dcb in QEventDispatcherGlib::processEvents
(this=0x7f806c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f80916ebd2a in QEventLoop::exec (this=this@entry=0x7f8072550de0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f8091544ab4 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7f8093ea30b5 in ?? () from /usr/lib64/libQt5Qml.so.5
#7  0x7f80915490e2 in QThreadPrivate::start (arg=0x14a5280) at
thread/qthread_unix.cpp:331
#8  0x7f8090679494 in start_thread () from /lib64/libpthread.so.0
#9  0x7f8090e72afd in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f8070df5700 (LWP 9640)):
#0  0x7f8090e69abd in poll () from /lib64/libc.so.6
#1  0x7f808ce3db5c in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f808ce3dc6c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f8091739dcb in QEventDispatcherGlib::processEvents
(this=0x7f80640008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f80916ebd2a in QEventLoop::exec (this=this@entry=0x7f8070df4de0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f8091544ab4 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7f8093ea30b5 in ?? () from /usr/lib64/libQt5Qml.so.5
#7  0x7f80915490e2 in QThreadPrivate::start (arg=0x15a0050) at
thread/qthread_unix.cpp:331
#8  0x7f8090679494 in start_thread () from /lib64/libpthread.so.0
#9  0x7f8090e72afd in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f806b3d8700 (LWP 9641)):
#0  0x7f809067f0bf in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f8096317082 in ?? () from /usr/lib64/libQt5Script.so.5
#2  0x7f8096317209 in ?? () from /usr/lib64/libQt5Script.so.5
#3  0x7f8090679494 in start_thread () from /lib64/libpthread.so.0
#4  0x7f8090e72afd in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f7fe3fff700 (LWP 9642)):
#0  0x7f808ce902f9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f808ce3db42 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f808ce3dc6c in g_main_context_iteration () from

[plasma-nm] [Bug 359334] Connection editor with Oxygen theme is unusable

[andreas via KDE Bugzilla]

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

andreas  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

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