[kdenlive] [Bug 364082] Crash on start when no binary nvidia driver is available

[Evert Vorster via KDE Bugzilla]

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

--- Comment #6 from Evert Vorster  ---
I'm more than a little curious here. 

You say you are running nvidia binaries fine, but when running the free drivers
you are initializing an intel chip? 
Does glxgears run, or also crash?

-Evert-

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

[plasmashell] [Bug 364612] Launchers on only icon task manager disappear when launching them

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/plas
   ||ma-workspace/64a2fbb60d255d
   ||3ef3768ce464e21a4ada416b76
 Resolution|--- |FIXED

--- Comment #1 from Eike Hein  ---
Git commit 64a2fbb60d255d3ef3768ce464e21a4ada416b76 by Eike Hein.
Committed on 22/06/2016 at 05:46.
Pushed by hein into branch 'Plasma/5.7'.

Trigger launcher re-filter also when a startup task is removed.

If the window never comes, the launcher would remain hidden otherwise;
also, if a startup times out before a window appears, we get an ugly
gap when using launch-in-place behavior (i.e. on Icontasks).

M  +4-2libtaskmanager/tasksmodel.cpp

http://commits.kde.org/plasma-workspace/64a2fbb60d255d3ef3768ce464e21a4ada416b76

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

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

[via KDE Bugzilla]

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

sq...@web.de changed:

   What|Removed |Added

 CC||sq...@web.de

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

[frameworks-plasma] [Bug 364622] Plasmoid.icon can not render SVG icon

[Leslie Zhai via KDE Bugzilla]

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

--- Comment #1 from Leslie Zhai  ---
Spectacle shown as: https://twitter.com/xiangzhai/status/745477968273637380

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

[frameworks-plasma] [Bug 364622] New: Plasmoid.icon can not render SVG icon

[Leslie Zhai via KDE Bugzilla]

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

Bug ID: 364622
   Summary: Plasmoid.icon can not render SVG icon
   Product: frameworks-plasma
   Version: 5.23.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: libplasmaquick
  Assignee: notm...@gmail.com
  Reporter: xiangzha...@gmail.com

Kickoff, plasma-desktop/applets/kickoff, is able to set its icon,
package/contents/ui/ConfigGeneral.qml, but from 5.23.0, it is unable to render
*.svg icon, 5.21.0 still worked!

Reproducible: Always

Steps to Reproduce:
1. right click on kickoff
2. click configuration
3. change the icon to a *.svg file

Actual Results:  
PlasmaCore.IconItem is blank

Expected Results:  
it is able to render SVG

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

[kdenlive] [Bug 351512] Freeze when importing clips without a clip monitor

[farid via KDE Bugzilla]

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

farid  changed:

   What|Removed |Added

 CC||snd.no...@gmail.com

--- Comment #8 from farid  ---
Can't reproduce in 16.04.2. Please mark as solved.

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

[kdenlive] [Bug 358173] 15.13.0 git master - Folder icons in Project Bin are not the same size as Clips. Doesn't look uniform.

[farid via KDE Bugzilla]

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

farid  changed:

   What|Removed |Added

 CC||snd.no...@gmail.com

--- Comment #2 from farid  ---
In 16.04.2 I actually kind of like it as it is. In tree view the folders are
small and clips can be resized and in icon view you can have them the same
size. Don't you think? If you think it works please mark this as solved.

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

[kdenlive] [Bug 360138] User interface completely broken

[farid via KDE Bugzilla]

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

farid  changed:

   What|Removed |Added

 CC||snd.no...@gmail.com

--- Comment #2 from farid  ---
Please test latest version and close report if possible.

cheers

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

[kdenlive] [Bug 360039] Movie from hell crashes kdenlive

[farid via KDE Bugzilla]

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

farid  changed:

   What|Removed |Added

 CC||snd.no...@gmail.com

--- Comment #1 from farid  ---
Don't think this is a kdenlive bug.c ould you test with newer version and mark
as solved?

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

[kdenlive] [Bug 348938] 15.04.1 Unusable - extremely slow timeline

[farid via KDE Bugzilla]

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

--- Comment #3 from farid  ---
Have you tested with latest version 16.04.2? Can you reproduce? If not please
mark as solved.

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

[kdenlive] [Bug 361090] Audio thumbnail incorrect

[farid via KDE Bugzilla]

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

farid  changed:

   What|Removed |Added

 CC||snd.no...@gmail.com

--- Comment #13 from farid  ---
Can this issue be marked as solved?

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

[kdenlive] [Bug 364278] kdenlive crashes whilst starting

[farid via KDE Bugzilla]

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

farid  changed:

   What|Removed |Added

 CC||snd.no...@gmail.com

--- Comment #1 from farid  ---
This could be related to movit. Do you have gpu processing on? See here:

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

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

[kdenlive] [Bug 364559] Changing project settings and saving crashes the software

[farid via KDE Bugzilla]

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

farid  changed:

   What|Removed |Added

 CC||snd.no...@gmail.com

--- Comment #2 from farid  ---
I am using 16.04.2 and I cannot reproduce. Do you have GPU processing turned on
in the settings by any chance?

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

[kdenlive] [Bug 350717] kdenlive segfaults when syncing large files

[farid via KDE Bugzilla]

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

farid  changed:

   What|Removed |Added

 CC||snd.no...@gmail.com

--- Comment #3 from farid  ---
Hi,

Have you tried this with latest 16.04.2 series to see if it still happens?

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

[kdenlive] [Bug 348671] another problem with markers

[farid via KDE Bugzilla]

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

farid  changed:

   What|Removed |Added

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

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

[kaffeine] [Bug 272463] Program Guide shows multiple entries

[Mauro Carvalho Chehab via KDE Bugzilla]

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

--- Comment #9 from Mauro Carvalho Chehab  ---
Created attachment 99656
  --> https://bugs.kde.org/attachment.cgi?id=99656=edit
Don't accept duplicated EPG events

Please test the attached patch. It adds a logic that should avoid adding two
conflicted events on the same channel. Try to run it on debug mode and see if
it will fix the issue.

PS.: this patch is a little bit lazy when comparing two channels... it is just
using "==" instead of verifying each fields. Maybe such logic may require
changes and compare field by field (e. g. compare the chanel name, network ID
and/or channel number).

The patch is against the latest Kaffeine version on git.

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

[dolphin] [Bug 364621] New: Dolphin crashes when one drags a device into the file window

[Carlos Quiros via KDE Bugzilla]

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

Bug ID: 364621
   Summary: Dolphin crashes when one drags a device into the file
window
   Product: dolphin
   Version: unspecified
  Platform: Slackware Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: cqui...@qlands.com

Application: dolphin (16.04.2)

Qt Version: 5.6.1
Frameworks Version: 5.23.0
Operating System: Linux 4.4.13 x86_64
Distribution (Platform): Slackware Packages

-- Information about the crash:
It happens every time. If you drag a device like OS or a hard drive into the
min Dolphin window it crashes.

The crash can be reproduced every time.

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

Thread 3 (Thread 0x7f4196c39700 (LWP 6172)):
#0  0x7f41b796b30d in poll () at /lib64/libc.so.6
#1  0x7f41b24d8954 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f41b24d8a5c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f41b879256b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f41b873e2ca in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f41b85772cc in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f41b857beb9 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f41b45a3684 in start_thread () at /lib64/libpthread.so.0
#8  0x7f41b7976efd in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f41a5c10700 (LWP 6171)):
#0  0x7f41b7966e3d in read () at /lib64/libc.so.6
#1  0x7f41b251a5d0 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f41b24d8484 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f41b24d88f8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f41b24d8a5c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f41b879256b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f41b873e2ca in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f41b85772cc in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f41b8ba1295 in  () at /usr/lib64/libQt5DBus.so.5
#9  0x7f41b857beb9 in  () at /usr/lib64/libQt5Core.so.5
#10 0x7f41b45a3684 in start_thread () at /lib64/libpthread.so.0
#11 0x7f41b7976efd in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f41c05217c0 (LWP 6169)):
[KCrash Handler]
#6  0x in  ()
#7  0x7f41b8765758 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f41b876681d in QMimeData::data(QString const&) const () at
/usr/lib64/libQt5Core.so.5
#9  0x7f41be83e1e1 in KIO::isClipboardDataCut(QMimeData const*) () at
/usr/lib64/libKF5KIOWidgets.so.5
#10 0x7f41be86273e in  () at /usr/lib64/libKF5KIOWidgets.so.5
#11 0x7f41be862a91 in  () at /usr/lib64/libKF5KIOWidgets.so.5
#12 0x7f41b876b801 in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#13 0x7f41b995be8c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#14 0x7f41b9961016 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#15 0x7f41b873fff8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#16 0x7f41b8741dda in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#17 0x7f41b8792143 in  () at /usr/lib64/libQt5Core.so.5
#18 0x7f41b24d8787 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#19 0x7f41b24d89b8 in  () at /usr/lib64/libglib-2.0.so.0
#20 0x7f41b24d8a5c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#21 0x7f41b879254f in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#22 0x7f41b873e2ca in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#23 0x7f41b874638d in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#24 0x7f41c010aea6 in kdemain () at /usr/lib64/libkdeinit5_dolphin.so
#25 0x7f41b78907d0 in __libc_start_main () at /lib64/libc.so.6
#26 0x00400af9 in _start ()

Reported using DrKonqi

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

[konsole] [Bug 364616] konsole crashes while typing inside nano editor

[via KDE Bugzilla]

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

orionbe...@gmail.com changed:

   What|Removed |Added

Version|15.12.3 |16.04.1

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

[konsole] [Bug 364616] konsole crashes while typing inside nano editor

[via KDE Bugzilla]

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

--- Comment #1 from orionbe...@gmail.com ---
I am adding that i updated konsole to version 16.04.1 and the bug is still
there.

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

[kdenlive] [Bug 364082] Crash on start when no binary nvidia driver is available

[Yueqi Li via KDE Bugzilla]

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

--- Comment #5 from Yueqi Li  ---
Removing cache at "/home/leo/.cache/kdenlive-thumbs.kcache"
 // / processing file open
 // / processing file open: validate
klauncher not running... launching kdeinit
kdeinit5: preparing to launch 'libkdeinit5_klauncher'
kdeinit5: Launched KLauncher, pid = 2422, result = 0
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kdeinit5: opened connection to :0
kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so'
from launcher.
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so'
OpenGL vendor:  "Intel Open Source Technology Center"
OpenGL renderer:  "Mesa DRI Intel(R) Haswell Mobile "
OpenGL ARG_SYNC:  true
OpenGL OpenGLES:  false
[New Thread 0x7fffa2cd7700 (LWP 2425)]

Thread 1 "kdenlive" received signal SIGSEGV, Segmentation fault.
0x72457630 in QOpenGLContext::shareGroup() const ()
   from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe2cb5700 (LWP 2411)]
[New Thread 0x7fffd997c700 (LWP 2412)]
[New Thread 0x7fffd917b700 (LWP 2413)]
[New Thread 0x7fffd897a700 (LWP 2414)]
[New Thread 0x7fffcbfff700 (LWP 2415)]
[Thread 0x7fffd897a700 (LWP 2414) exited]
[New Thread 0x7fffd897a700 (LWP 2416)]
[New Thread 0x7fffab0f6700 (LWP 2417)]
[New Thread 0x7fffaa0f5700 (LWP 2418)]
[New Thread 0x7fffa9818700 (LWP 2419)]
Removing cache at "/home/leo/.cache/kdenlive-thumbs.kcache"
 // / processing file open
 // / processing file open: validate
klauncher not running... launching kdeinit
kdeinit5: preparing to launch 'libkdeinit5_klauncher'
kdeinit5: Launched KLauncher, pid = 2422, result = 0
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kdeinit5: opened connection to :0
kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so'
from launcher.
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so'
OpenGL vendor:  "Intel Open Source Technology Center"
OpenGL renderer:  "Mesa DRI Intel(R) Haswell Mobile "
OpenGL ARG_SYNC:  true
OpenGL OpenGLES:  false
[New Thread 0x7fffa2cd7700 (LWP 2425)]

Thread 1 "kdenlive" received signal SIGSEGV, Segmentation fault.
0x72457630 in QOpenGLContext::shareGroup() const ()
   from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
(gdb) thread apply all bt

Thread 11 (Thread 0x7fffa2cd7700 (LWP 2425)):
#0  0x714ffe8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fffee42531c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fffee42542c in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x72135a9b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x720dcdea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x71ef98a4 in QThread::exec() ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x71efe84e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fffefe2d6fa in start_thread (arg=0x7fffa2cd7700)
at pthread_create.c:333
#8  0x7150bb5d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7fffa9818700 (LWP 2419)):
#0  0x714ffe8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fffee42531c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fffee42542c in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0

#3  0x72135a7f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x720dcdea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x71ef98a4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x72caa3c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x71efe84e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fffefe2d6fa in start_thread (arg=0x7fffa9818700) at
pthread_create.c:333
#9  0x7150bb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7fffaa0f5700 (LWP 2418)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x71effa26 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x71efb4d3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x71efe84e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fffefe2d6fa in start_thread (arg=0x7fffaa0f5700) at
pthread_create.c:333
#5  0x7150bb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 

[kate] [Bug 364620] New: Changes made to syntax file is not loaded

[via KDE Bugzilla]

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

Bug ID: 364620
   Summary: Changes made to syntax file is not loaded
   Product: kate
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: syntax
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: gillesgalip...@gmail.com

The changes made to the file /usr/share/kde4/apps/katepart/syntax/bash.xml are
not loaded when restarting kate.

I also tried downloading the most recent syntax (Settings -> Kate config ->
Open/Save -> File types -> Download syntax-highlighting files) and copy the
bash.xml to the new folder created (~/.local/share/katepart5/syntax) but still
does not load the change made to the file.

Environment:
Ubuntu 16.04
Kate 15.12.3 Using:
KDE Frameworks 5.18.0
Qt 5.5.1 (built against 5.5.1)
The xcb windowing system

Reproducible: Always

Steps to Reproduce:
1. Open syntax file /usr/share/kde4/apps/katepart/syntax/bash.xml with sudo
access
2. Edit the language / general / keywords as follow: weakDeliminator="^%_-"
additionalDeliminator="`$#"
3. Restart kate and open a bash script
4. Double click on a string starting with "$" or on text surrounded by square
or curly braces

Actual Results:  
The special characters are not considered as delimiter; they are also
highlighted

Expected Results:  
The special characters should not be highlighted

This is working fine with the same syntax file on my Ubuntu 14.04 workstation

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

[kate] [Bug 364620] Changes made to syntax file are not loaded

[via KDE Bugzilla]

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

gillesgalip...@gmail.com changed:

   What|Removed |Added

Summary|Changes made to syntax file |Changes made to syntax file
   |is not loaded   |are not loaded

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

[systemsettings] [Bug 364619] New: kcm_grub2 editor stopped working in Fedora 24

[George Seaton via KDE Bugzilla]

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

Bug ID: 364619
   Summary: kcm_grub2 editor stopped working in Fedora 24
   Product: systemsettings
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: george.sea...@inbox.com

Application: kcmshell4 (4.14.19)
KDE Platform Version: 4.14.20
Qt Version: 4.8.7
Operating System: Linux 4.5.7-300.fc24.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:
trying to start kcm_grub2  grub2 editor in Fedora 24

- Unusual behavior I noticed:
On initial startup utility window opens but is completely blank.
seems to be dbus errors

The crash can be reproduced every time.

-- Backtrace:
Application: KDE Control Module (kcmshell4), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x7f95e5ae76f5 in raise () at /lib64/libc.so.6
#7  0x7f95e5ae92fa in abort () at /lib64/libc.so.6
#8  0x7f95e28c0d04 in _dbus_abort () at /lib64/libdbus-1.so.3
#9  0x7f95e28b773c in  () at /lib64/libdbus-1.so.3
#10 0x7f95e28a7c82 in dbus_message_new_method_call () at
/lib64/libdbus-1.so.3
#11 0x7f95e7df22c8 in QDBusMessagePrivate::toDBusMessage(QDBusMessage
const&, QFlags, QDBusError*) () at
/lib64/libQtDBus.so.4
#12 0x7f95e7ded8ba in QDBusConnectionPrivate::sendWithReply(QDBusMessage
const&, int, int) () at /lib64/libQtDBus.so.4
#13 0x7f95e7defbd7 in QDBusConnectionPrivate::findMetaObject(QString
const&, QString const&, QString const&, QDBusError&) () at
/lib64/libQtDBus.so.4
#14 0x7f95e7dfcc4b in QDBusInterfacePrivate::QDBusInterfacePrivate(QString
const&, QString const&, QString const&, QDBusConnection const&) () at
/lib64/libQtDBus.so.4
#15 0x7f95e7dfcd95 in QDBusInterface::QDBusInterface(QString const&,
QString const&, QString const&, QDBusConnection const&, QObject*) () at
/lib64/libQtDBus.so.4
#16 0x7f95e8eb7047 in KCMShell::isRunning() () at
/lib64/libkdeinit4_kcmshell4.so
#17 0x7f95e8eb890f in kdemain () at /lib64/libkdeinit4_kcmshell4.so
#18 0x7f95e5ad3731 in __libc_start_main () at /lib64/libc.so.6
#19 0x55e1fe6dc8e9 in _start ()

Reported using DrKonqi

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

[plasmashell] [Bug 364577] Return plasma 5.6 login and splash screen in 5.7

[David Edmundson via KDE Bugzilla]

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

--- Comment #3 from David Edmundson  ---
Though to be clear the fact that you "*really* hate them" is not a valid reason
for a bug report nor the reason for the revert.

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

[plasmashell] [Bug 364577] Return plasma 5.6 login and splash screen in 5.7

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

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

[plasmashell] [Bug 347940] The clock notification remain outdated even after a timezone update

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |RESOLVED
 CC||k...@davidedmundson.co.uk

--- Comment #1 from David Edmundson  ---
The tooltip deliberately doesn't show the same time as the clock because that
would be pointless.

It shows any other timezones you have configured in the digital clock applet.

Could you check it is doing something wrong, 
and if so attach a screenshot and reopen this bug.

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

[plasmashell] [Bug 364451] Login screen and logout/shutdown, lock screens inconsistent

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
 CC||k...@davidedmundson.co.uk

--- Comment #1 from David Edmundson  ---
Login screen is reverted.

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

[kdenlive] [Bug 360882] git master - dialog boxes are missing button icons and features on non-KDE desktops. (video example included)

[via KDE Bugzilla]

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

gleto...@gmail.com changed:

   What|Removed |Added

 CC||gleto...@gmail.com

--- Comment #5 from gleto...@gmail.com ---
Happens on gentoo as well.

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

[plasmashell] [Bug 364618] New: Introduce event delay when minimizing/maximizing windows

[kthiele via KDE Bugzilla]

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

Bug ID: 364618
   Summary: Introduce event delay when minimizing/maximizing
windows
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: ksthiele+kdeb...@gmail.com
CC: plasma-b...@kde.org

When you open a minimized window you can minimize it mid air, I think it would
be better if was waiting for the animation to finish and then the user's clicks
are counted again. It could irritate the user if he accidentally clicks an
application window in the task bar twice and it could also help the CPU cycles
and battery in case someone opens and closes a window constantly. Furthermore
it can hide some regressions which may make the user think KDE is slow when an
app is running on full speed in the background..

Reproducible: Always

Steps to Reproduce:
1. Click to open window from task manager
2. click it again in mid opening animation
3. it minimizes again

Actual Results:  
it stays closed

Expected Results:  
The application should have finished the animation and meanwhile ignore all
incoming requests to minimize the window.

I think it would be similar to Windows (7) then?

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

[kwin] [Bug 359531] [wayland] add support for xdg_shell should stop gtk3 applications from crashing

[Reuben Peterkin via KDE Bugzilla]

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

Reuben Peterkin  changed:

   What|Removed |Added

 CC||reube...@yahoo.com

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

[k3b] [Bug 349160] k3b crashed when adding a directory to a project

[via KDE Bugzilla]

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

ssoxy...@hotmail.com changed:

   What|Removed |Added

 CC||ssoxy...@hotmail.com

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

[gwenview] [Bug 364617] New: Gwenview crashes on opening an EPS file after plasma 5 update

[via KDE Bugzilla]

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

Bug ID: 364617
   Summary: Gwenview crashes on opening an EPS file after plasma 5
update
   Product: gwenview
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: bog...@hlevca.com
CC: myr...@kde.org

Application: gwenview (16.04.2)

Qt Version: 5.6.1
Frameworks Version: 5.23.0
Operating System: Linux 4.6.0-1-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

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

Just a simple opening of the file produces this crash. 
Tehre is no more information that can be added to this. The crash is
reproducible every time.

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

Thread 4 (Thread 0x7fbacdf9d700 (LWP 18767)):
#0  0x7fbadeeabbbd in poll () at /lib64/libc.so.6
#1  0x7fbad6d93422 in  () at /usr/lib64/libxcb.so.1
#2  0x7fbad6d9500f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7fbad02d4579 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fbadf5aaa29 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fbad912b0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7fbadeeb3fed in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fbac7fff700 (LWP 18768)):
#0  0x7fbadeeabbbd in poll () at /lib64/libc.so.6
#1  0x7fbad8c0ee64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fbad8c0ef7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fbadf7bd34b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fbadf76afcb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fbadf5a5f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fbadeb65225 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7fbadf5aaa29 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fbad912b0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fbadeeb3fed in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fbabbf82700 (LWP 18769)):
#0  0x7fbad912f3e8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fbadf5ab5e8 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fbadf5a79e0 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7fbadf5aaa29 in  () at /usr/lib64/libQt5Core.so.5
#4  0x7fbad912b0a4 in start_thread () at /lib64/libpthread.so.0
#5  0x7fbadeeb3fed in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fbae4480840 (LWP 18766)):
[KCrash Handler]
#6  0x7fbae3be71e4 in
Gwenview::ImageMetaInfoModel::setExiv2Image(Exiv2::Image const*) () at
/usr/lib64/libgwenviewlib.so.5
#7  0x7fbae3bb1234 in
Gwenview::Document::setExiv2Image(std::auto_ptr) () at
/usr/lib64/libgwenviewlib.so.5
#8  0x7fbae3bafa81 in  () at /usr/lib64/libgwenviewlib.so.5
#9  0x7fbae3bb7259 in  () at /usr/lib64/libgwenviewlib.so.5
#10 0x7fbadf796ba1 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#11 0x7fbadf5a2a03 in QFutureWatcherBase::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#12 0x7fbae0e4ae9c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#13 0x7fbae0e4f4fa in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#14 0x7fbadf76cfb5 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#15 0x7fbadf76ed9a in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#16 0x7fbadf7bdca3 in  () at /usr/lib64/libQt5Core.so.5
#17 0x7fbad8c0ec84 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#18 0x7fbad8c0eed8 in  () at /usr/lib64/libglib-2.0.so.0
#19 0x7fbad8c0ef7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#20 0x7fbadf7bd32c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#21 0x7fbadf76afcb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#22 0x7fbadf772eb6 in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#23 0x0042d47c in  ()
#24 0x7fbadedf0b05 in __libc_start_main () at /lib64/libc.so.6
#25 0x0042d757 in _start ()

Reported using DrKonqi

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

[plasmashell] [Bug 342186] Global shortcuts do not work to control activity switching

[Marco Parillo via KDE Bugzilla]

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

Marco Parillo  changed:

   What|Removed |Added

 CC||marco_pari...@hotmail.com

--- Comment #22 from Marco Parillo  ---
On Kubuntu YY (to become 16.10) KInfocenter reports Plasma 5.6.5 and 
Frameworks 5.23. I could create a new activity from the 'Hamburger' menu, then
use the Other tab to assign ctrl+meta+a, and click Create. When I go back to
the Activity, the shortcut for switching to the activity is lost.

On Manjaro (fully updated) KInfocenter reports Plasma 5.6.4 and  Frameworks
5.22. I could create a new activity from the 'Hamburger' menu, then use the
Other tab to assign ctrl+meta+a, and click Create. When I go back to the
Activity, the shortcut for switching to the activity is still stored in the
Other tab, but the shortcut seems to not actually switch activities.

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

[konsole] [Bug 358628] Konsol crashes when opening new tab

[João Vidal da Silva via KDE Bugzilla]

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

--- Comment #1 from João Vidal da Silva  ---
I have not much to add except that it has been happening to me: konsole left
idle for some time (some hours), then I come and open a new tab and it freezes.
I couldn't find any error messages though. How do you do it _lp_?

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

[konsole] [Bug 358628] Konsol crashes when opening new tab

[João Vidal da Silva via KDE Bugzilla]

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

João Vidal da Silva  changed:

   What|Removed |Added

 CC||joao.vidal.si...@gmail.com

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

[plasmashell] [Bug 364613] plasma crashes upon hotplug of external display on modern intel graphics

[via KDE Bugzilla]

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

--- Comment #2 from databasede...@gmail.com ---
Additionally, it seems that there's a correlation between the resolution of the
monitor as well.  My main monitor (4k) crashes it every time.  the TV sets that
are 2k (aka 1080p) seem to crash only 50% of the time.

It feels like a bug in kscreen, just because I've had all manners of other
display issues at 4K and that `rm -rf ~/.local/share/kscreen/*` seemed to
resolve some screen layout issues in the past.  But this is a WAG.

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

[konsole] [Bug 364616] New: konsole crashes while typing inside nano editor

[via KDE Bugzilla]

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

Bug ID: 364616
   Summary: konsole crashes while typing inside nano editor
   Product: konsole
   Version: 15.12.3
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: orionbe...@gmail.com

Application: konsole (15.12.3)
 (Compiled from sources)
Qt Version: 5.5.1
Operating System: Linux 4.4.6-gentoo x86_64
Distribution (Platform): Gentoo Packages

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

I was typing a message in the nano editor, called by a mutt session. This has
been happening since i was forced to switch to Plasma 5 a couple of weeks ago:
My konsole sessions die sooner or later while i type inside nano. I have not
been able to identify a specific sequence of characters before the crash. I
often switch between several keyboard layouts while typing, in case that may be
related.

Note that the crash always happens *while* i type something, never while i am
off doing something else. This is a difference from all the reported possibly
related bugs, and it is why i file it separately.

This is a show-stopper for me since konsole is my workhorse application, and
this bug takes it down along with all its tabs!

The crash can be reproduced every time.

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

Thread 2 (Thread 0x7fcfab30b700 (LWP 32310)):
#0  0x7fcfc61b71cd in poll () from /lib64/libc.so.6
#1  0x7fcfbefcbac2 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7fcfbefcd72f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7fcfad466cb9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fcfc2bf4ed2 in ?? () from /usr/lib64/libQt5Core.so.5
#5  0x7fcfbeba9444 in start_thread () from /lib64/libpthread.so.0
#6  0x7fcfc61c018d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fcfb3dc17c0 (LWP 32309)):
[KCrash Handler]
#6  0x7fcfc2d9f860 in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib64/libQt5Core.so.5
#7  0x7fcfad5408f5 in ?? () from
/usr/lib64/qt5/plugins/platforminputcontexts/libcomposeplatforminputcontextplugin.so
#8  0x7fcfad540dcb in ?? () from
/usr/lib64/qt5/plugins/platforminputcontexts/libcomposeplatforminputcontextplugin.so
#9  0x7fcfad46c0a6 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#10 0x7fcfad464ade in QXcbConnection::handleXcbEvent(xcb_generic_event_t*)
() from /usr/lib64/libQt5XcbQpa.so.5
#11 0x7fcfad4668fb in QXcbConnection::processXcbEvents() () from
/usr/lib64/libQt5XcbQpa.so.5
#12 0x7fcfc2dc862a in QObject::event(QEvent*) () from
/usr/lib64/libQt5Core.so.5
#13 0x7fcfc35f66bc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/libQt5Widgets.so.5
#14 0x7fcfc35fbba8 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#15 0x7fcfc2d9f87d in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib64/libQt5Core.so.5
#16 0x7fcfc2da2613 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib64/libQt5Core.so.5
#17 0x7fcfc2dec8a3 in ?? () from /usr/lib64/libQt5Core.so.5
#18 0x7fcfbcffbc6d in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#19 0x7fcfbcffbf50 in ?? () from /usr/lib64/libglib-2.0.so.0
#20 0x7fcfbcffbffc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#21 0x7fcfc2dec917 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#22 0x7fcfc2d9e4da in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#23 0x7fcfc2da57bc in QCoreApplication::exec() () from
/usr/lib64/libQt5Core.so.5
#24 0x7fcfc649ad92 in kdemain () from /usr/lib64/libkdeinit5_konsole.so
#25 0x7fcfc60f7620 in __libc_start_main () from /lib64/libc.so.6
#26 0x004007c9 in _start ()

Possible duplicates by query: bug 364135, bug 362919, bug 362415, bug 362408,
bug 361934.

Reported using DrKonqi

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

[krfb] [Bug 363217] VNC connection to KDE5 is not possible

[Bron Mach via KDE Bugzilla]

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

Bron Mach  changed:

   What|Removed |Added

 CC||bugzilla_m...@shaw.ca

--- Comment #4 from Bron Mach  ---
With Kubuntu 15.04 and 15.10 it was possible for a remote client to attach to
an existing desktop session using Krfb's "Unattended Access" and xrdp.

With the update to Kubuntu 16.04, there are no screen updates on the client
after login when using Krfb. The client only sees a static "snapshot" of the
desktop from ~3 hours ago.

krfb 4:15.12.3-0ubuntu1
plasma-desktop 4:5.6.4-0ubuntu1~ubuntu16.04~ppa3

Is there an easy way to gather Krfb logs?

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

[plasmashell] [Bug 342186] Global shortcuts do not work to control activity switching

[soee via KDE Bugzilla]

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

--- Comment #21 from soee  ---
Created attachment 99655
  --> https://bugs.kde.org/attachment.cgi?id=99655=edit
2 activities with shortcutsassigned

As you can see on the screen, i have 2 activities defined with shorcuts for
each of them (it was hard to assign them from activities inspector but i did it
through shortcuts module). This shortcuts dont have any effect though.

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

[digikam] [Bug 363697] Album visible even after deletion

[via KDE Bugzilla]

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

--- Comment #4 from swatilodh...@gmail.com ---
Yes. I agree with you.
DB doesn't work well in case of deletion/moving.

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

[plasmashell] [Bug 342186] Global shortcuts do not work to control activity switching

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED
 CC||k...@davidedmundson.co.uk

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

[digikam] [Bug 363697] Album visible even after deletion

[Johannes Hirte via KDE Bugzilla]

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

--- Comment #3 from Johannes Hirte  ---
As my report is marked as a duplicate of this, please see my description there:
https://bugs.kde.org/show_bug.cgi?id=364614

It't not only the album shouldn't be visible anymore after deletion, the whole
db management seems to be broken in case of moving/deleting items.

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

[plasmashell] [Bug 342186] Global shortcuts do not work to control activity switching

[soee via KDE Bugzilla]

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

soee  changed:

   What|Removed |Added

 CC||kont...@soee.pl

--- Comment #20 from soee  ---
Activities shortcuts does nto work on Neon - Plamsma 5.6.5 and Frameworks 5.23.
I think this was broken somewhere in Frameworks 5.23 as on Kubutnu it wrked
pretty well (Plasma 5.6.4 + Frameworks 5.22).

Please reopen this bug.

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

[plasmashell] [Bug 364613] plasma crashes upon hotplug of external display on modern intel graphics

[via KDE Bugzilla]

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

--- Comment #1 from databasede...@gmail.com ---
I should note that this crash is very easy to reproduce reliably.  There have
been maybe one or two times I've undocked/docked out of 100 in the last month
where plasmashell didn't crash.

I use KDE exclusively, and would love to help fix this bug.  Please feel free
to get in touch and I'll help in any way you need.

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

[kaffeine] [Bug 272463] Program Guide shows multiple entries

[via KDE Bugzilla]

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

--- Comment #8 from hu...@gmx.de ---
Created attachment 99654
  --> https://bugs.kde.org/attachment.cgi?id=99654=edit
EPG example 2

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

[kaffeine] [Bug 272463] Program Guide shows multiple entries

[via KDE Bugzilla]

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

--- Comment #7 from hu...@gmx.de ---
Created attachment 99653
  --> https://bugs.kde.org/attachment.cgi?id=99653=edit
EPG example1

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

[krita] [Bug 363373] bezier curve selection tool in release v3.0

[Michael via KDE Bugzilla]

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

Michael  changed:

   What|Removed |Added

 CC||miabr...@gmail.com

--- Comment #6 from Michael  ---
https://phabricator.kde.org/D1970

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

[kaffeine] [Bug 272463] Program Guide shows multiple entries

[via KDE Bugzilla]

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

--- Comment #6 from hu...@gmx.de ---
There are also double entries with same times but different descriptions, as
you can see on the screenshots. 
TVs can handle it somehow.

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

[plasmashell] [Bug 355463] xembedsniproxy always crash when login

[Vadym Krevs via KDE Bugzilla]

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

--- Comment #35 from Vadym Krevs  ---
And that is with the latest plasma 5.7 beta ...
$ rpm -qf /usr/bin/xembedsniproxy
plasma5-workspace-5.6.95-215.1.x86_64

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

[plasmashell] [Bug 355463] xembedsniproxy always crash when login

[Vadym Krevs via KDE Bugzilla]

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

--- Comment #34 from Vadym Krevs  ---
Happens all the time to me on openSUSE Leap 42.1 as soon as google chrome is
started. Here is the backtrace:

Program received signal SIGSEGV, Segmentation fault.
SNIProxy::getImageNonComposite (this=this@entry=0xe25720) at
/usr/src/debug/plasma-workspace-5.6.95/xembed-sni-proxy/sniproxy.cpp:273
273 /usr/src/debug/plasma-workspace-5.6.95/xembed-sni-proxy/sniproxy.cpp:
No such file or directory.
(gdb) info threads
  Id   Target Id Frame 
  3Thread 0x7f1fca974700 (LWP 1697) "QXcbEventReader" 0x7f1fd31c1bbd in
poll () at ../sysdeps/unix/syscall-template.S:81
  2Thread 0x7f1fbca9b700 (LWP 1709) "QDBusConnection" 0x7f1fd31c1bbd in
poll () at ../sysdeps/unix/syscall-template.S:81
* 1Thread 0x7f1fd58eb780 (LWP 1694) "xembedsniproxy"
SNIProxy::getImageNonComposite (this=this@entry=0xe25720) at
/usr/src/debug/plasma-workspace-5.6.95/xembed-sni-proxy/sniproxy.cpp:273
(gdb) thread apply allbt
(gdb) thread apply all bt

Thread 3 (Thread 0x7f1fca974700 (LWP 1697)):
#0  0x7f1fd31c1bbd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f1fd5045422 in _xcb_conn_wait (__timeout=-1, __nfds=1,
__fds=0x7f1fca973d40) at /usr/include/bits/poll2.h:46
#2  0x7f1fd5045422 in _xcb_conn_wait (c=c@entry=0xd981e0,
cond=cond@entry=0xd98220, vector=vector@entry=0x0, count=count@entry=0x0) at
xcb_conn.c:459
#3  0x7f1fd504700f in xcb_wait_for_event (c=0xd981e0) at xcb_in.c:693
#4  0x7f1fccef1579 in QXcbEventReader::run() (this=0xda2ba0) at
qxcbconnection.cpp:1325
#5  0x7f1fd38c0a29 in QThreadPrivate::start(void*) (arg=0xda2ba0) at
thread/qthread_unix.cpp:341
#6  0x7f1fd2ed00a4 in start_thread (arg=0x7f1fca974700) at
pthread_create.c:309
#7  0x7f1fd31c9fed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f1fbca9b700 (LWP 1709)):
#0  0x7f1fd31c1bbd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f1fcfe46e64 in g_main_context_iterate (priority=2147483647, n_fds=5,
fds=0x7f1fb800fd00, timeout=-1, context=0x7f1fb8000990) at gmain.c:4103
#2  0x7f1fcfe46e64 in g_main_context_iterate
(context=context@entry=0x7f1fb8000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3803
#3  0x7f1fcfe46f7c in g_main_context_iteration (context=0x7f1fb8000990,
may_block=1) at gmain.c:3869
#4  0x7f1fd3ad332c in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f1fb80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:417
#5  0x7f1fd3a80fcb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f1fbca9ae20, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7f1fd38bbf5a in QThread::exec() (this=this@entry=0x7f1fd5721d00
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:500
#7  0x7f1fd54b9225 in QDBusConnectionManager::run() (this=0x7f1fd5721d00
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:189
#8  0x7f1fd38c0a29 in QThreadPrivate::start(void*) (arg=0x7f1fd5721d00
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:341
#9  0x7f1fd2ed00a4 in start_thread (arg=0x7f1fbca9b700) at
pthread_create.c:309
#10 0x7f1fd31c9fed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f1fd58eb780 (LWP 1694)):
#0  0x0040c00f in SNIProxy::getImageNonComposite() const
(this=this@entry=0xe25720) at
/usr/src/debug/plasma-workspace-5.6.95/xembed-sni-proxy/sniproxy.cpp:273
#1  0x0040c2c4 in SNIProxy::update() (this=0xe25720) at
/usr/src/debug/plasma-workspace-5.6.95/xembed-sni-proxy/sniproxy.cpp:214
#2  0x004093ac in FdoSelectionManager::nativeEventFilter(QByteArray
const&, void*, long*) (this=0x7ffe7feb3470, eventType=...,
message=0x7f1fc4003d60, result=)
at
/usr/src/debug/plasma-workspace-5.6.95/xembed-sni-proxy/fdoselectionmanager.cpp:154
#3  0x7f1fd3a80260 in
QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*)
(this=, eventType=..., message=message@entry=0x7f1fc4003d60,
result=result@entry=0x7ffe7feb2ee8)
at kernel/qabstracteventdispatcher.cpp:460
#4  0x7f1fcceef924 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*)
(this=this@entry=0xd969f0, event=event@entry=0x7f1fc4003d60) at
qxcbconnection.cpp:1091
#5  0x7f1fccef197b in QXcbConnection::processXcbEvents() (this=0xd969f0) at
qxcbconnection.cpp:1723
#6  0x7f1fd3aae156 in QObject::event(QEvent*) (this=0xd969f0, e=) at kernel/qobject.cpp:1256
#7  0x7f1fd3a8307c in QCoreApplication::notify(QObject*, QEvent*)
(event=, receiver=) at
kernel/qcoreapplication.cpp:1090
#8  0x7f1fd3a8307c in QCoreApplication::notify(QObject*, QEvent*)
(this=, receiver=, event=) at
kernel/qcoreapplication.cpp:1076
#9  0x7f1fd3a82fb5 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0xd969f0, 

[digikam] [Bug 363697] Album visible even after deletion

[via KDE Bugzilla]

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

--- Comment #2 from swatilodh...@gmail.com ---
*** Bug 364614 has been marked as a duplicate of this bug. ***

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

[digikam] [Bug 364614] images/albums not deleted in database when deleting/moving in digikam

[via KDE Bugzilla]

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

swatilodh...@gmail.com changed:

   What|Removed |Added

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

--- Comment #2 from swatilodh...@gmail.com ---


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

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

[digikam] [Bug 364614] images/albums not deleted in database when deleting/moving in digikam

[via KDE Bugzilla]

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

swatilodh...@gmail.com changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||swatilodh...@gmail.com
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from swatilodh...@gmail.com ---


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

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

[digikam] [Bug 363697] Album visible even after deletion

[via KDE Bugzilla]

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

swatilodh...@gmail.com changed:

   What|Removed |Added

 CC||johannes.hirte@datenkhaos.d
   ||e

--- Comment #1 from swatilodh...@gmail.com ---
*** Bug 364614 has been marked as a duplicate of this bug. ***

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

[digikam] [Bug 364614] images/albums not deleted in database when deleting/moving in digikam

[via KDE Bugzilla]

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

swatilodh...@gmail.com changed:

   What|Removed |Added

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

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

[kaffeine] [Bug 272463] Program Guide shows multiple entries

[Mauro Carvalho Chehab via KDE Bugzilla]

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

--- Comment #5 from Mauro Carvalho Chehab  ---


(In reply to marian.trenkwalder from comment #2)
> me too
> the start time of the double entries are different.
> eg:
> Start;Duration;Title
> 14.04.2012 20:14; 00:50;Lie to me
> 14.04.2012 20:15; 00;50;Lie to me
> 
> both entries explain the same.

What I suspect is that this event has his time schedule shifted. So, Kaffeine
got the event's first timestamp. Some time after, the new timestamp event
arrived. As there's no field that uniquely identifies the event, a new entry
was added with the second timestamp.

It is not too easy to fix this.  One way would be to check if a new event would
conflict with another event on the same channel, but the hardest part would be
to test if the logic is working, because we either need to be able to produce a
test MPEG-TS or have a record of a TS where such change happened.

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

[krunner] [Bug 352385] Baloo filesearch crashes Plasma

[Shmerl via KDE Bugzilla]

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

--- Comment #6 from Shmerl  ---
My env:

OS: Debian testing (x86_64).
plasma-desktop: 5.6.4.
baloo-kf5: 5.22.

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

[krunner] [Bug 352385] Baloo filesearch crashes Plasma

[Shmerl via KDE Bugzilla]

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

Shmerl  changed:

   What|Removed |Added

 CC||shm...@mykolab.com

--- Comment #5 from Shmerl  ---
Looks like I have a similar issue. krunner crashes randomly with some input
(like "konsole") but it doesn't happen consistently. Once it crashes, it's not
starting up anymore (until relogin). When run from the terminal, I get:

Trying to use rootObject before initialization is completed, whilst using
setInitializationDelayed. Forcing completion

And nothing else happens.

balooctl status
Baloo File Indexer is running
Indexer state: Indexing file content
Indexed 13684 / 35742 files
Current size of index is 173.55 MiB

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

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

[Bernd Steinhauser via KDE Bugzilla]

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

--- Comment #28 from Bernd Steinhauser  ---
Just to give you some numbers, I let this system run for approximately one day.
During this time, plasmashell (in two threads) on average consumed 20% of one
CPU.
It was then on rank 1, right before Xorg with approx. 15%.

The third process would go to kwin, but that was already only at 2%.

I still have no idea what exactly plasmashell is doing. Help to find out would
be appreciated, because I don't think that this would be normal, to me the
numbers appear to be too high.

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

[dolphin] [Bug 364615] New: after mass rename, ctrl+z (undo) should revert ALL folders/files names

[Dr . Chapatin via KDE Bugzilla]

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

Bug ID: 364615
   Summary: after mass rename, ctrl+z (undo) should revert ALL
folders/files names
   Product: dolphin
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: yy...@gmx.com

Currently only ONE file/folder name is reverted.

Reproducible: Always

Steps to Reproduce:
1. select two or more folders/files
2. press F2 to mass rename and apply a new name to the files/folders
3. press ctrl+z to undo mass rename process

Actual Results:  
Only ONE folder/file name is reverted.

Expected Results:  
I think the correct behavior is revert ALL folder/file names.
If the user renames hundreds or thousands of folders/files to any wrong name a
third app is required to revert all wrong names.

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

[amarok] [Bug 364602] Amorak crashes on startup (OpenSUSE 13.2 -- MATE Desktop Environment 1.8.1)

[Mike Kienenberger via KDE Bugzilla]

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

--- Comment #2 from Mike Kienenberger  ---
Sorry.  I had hit install symbols but hadn't noticed that there were still a
bunch missing.

I've managed to find the debuginfo packages for everything but two lines. 
Here's the new backtrace:

Application: Amarok (amarok), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#5  0x7fd89419aada in __strcmp_sse2_unaligned () at /lib64/libc.so.6
#6  0x7fd86cec8fee in QMetaType::registerNormalizedType(QByteArray const&,
void (*)(void*), void* (*)(void const*), void (*)(void*), void* (*)(void*, void
const*), int, QFlags, QMetaObject const*) (length=22,
typeName=0x286d9f8 ) at
kernel/qmetatype.cpp:806
#7  0x7fd86cec8fee in QMetaType::registerNormalizedType(QByteArray const&,
void (*)(void*), void* (*)(void const*), void (*)(void*), void* (*)(void*, void
const*), int, QFlags, QMetaObject const*)
(normalizedTypeName=..., deleter=deleter@entry=0x7fd86d67f930
::Delete(void*)>, creator=creator@entry=0x7fd86d67fab0
::Create(void const*)>, destructor=destructor@entry=0x7fd86d67f890
::Destruct(void*)>, constructor=constructor@entry=0x7fd86d67f8a0
::Construct(void*, void const*)>, size=size@entry=16,
flags=flags@entry=..., metaObject=metaObject@entry=0x0) at
kernel/qmetatype.cpp:896
#8  0x7fd86d3c8f57 in _GLOBAL__sub_I_qpaintbuffer.cpp(void)
(defined=QtPrivate::MetaTypeDefinedHelper::Defined, dummy=0x, normalizedTypeName=...) at
../../src/corelib/kernel/qmetatype.h:1603
#9  0x7fd86d3c8f57 in _GLOBAL__sub_I_qpaintbuffer.cpp(void)
(defined=QtPrivate::MetaTypeDefinedHelper::Defined, dummy=0x, typeName=0x7fd86d75b9de
"QPaintBufferCacheEntry") at ../../src/corelib/kernel/qmetatype.h:1628
#10 0x7fd86d3c8f57 in _GLOBAL__sub_I_qpaintbuffer.cpp(void) () at
painting/qpaintbuffer.cpp:2081
#11 0x7fd86d3c8f57 in _GLOBAL__sub_I_qpaintbuffer.cpp(void) () at
../../src/corelib/kernel/qmetatype.h:1509
#12 0x7fd86d3c8f57 in _GLOBAL__sub_I_qpaintbuffer.cpp(void) () at
../../src/corelib/kernel/qmetatype.h:1649
#13 0x7fd86d3c8f57 in _GLOBAL__sub_I_qpaintbuffer.cpp(void) () at
../../src/corelib/kernel/qmetatype.h:1698
#14 0x7fd86d3c8f57 in _GLOBAL__sub_I_qpaintbuffer.cpp(void) () at
painting/qpaintbuffer.cpp:2107
#15 0x7fd86d3c8f57 in _GLOBAL__sub_I_qpaintbuffer.cpp(void)
(this=) at painting/qpaintbuffer.cpp:2111
#16 0x7fd86d3c8f57 in _GLOBAL__sub_I_qpaintbuffer.cpp(void)
(__priority=65535, __initialize_p=1) at painting/qpaintbuffer.cpp:2111
#17 0x7fd86d3c8f57 in _GLOBAL__sub_I_qpaintbuffer.cpp(void) () at
painting/qpaintbuffer.cpp:2207
#18 0x7fd8973218ea in call_init.part () at /lib64/ld-linux-x86-64.so.2
#19 0x7fd8973219d3 in _dl_init_internal () at /lib64/ld-linux-x86-64.so.2
#20 0x7fd897325b08 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2
#21 0x7fd8973217a4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2
#22 0x7fd8973252fb in _dl_open () at /lib64/ld-linux-x86-64.so.2
#23 0x7fd88d61202b in dlopen_doit () at /lib64/libdl.so.2
#24 0x7fd8973217a4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2
#25 0x7fd88d6125dd in _dlerror_run () at /lib64/libdl.so.2
#26 0x7fd88d6120c1 in dlopen@@GLIBC_2.2.5 () at /lib64/libdl.so.2
#27 0x7fd87317759f in module_Load (p_this=p_this@entry=0x141c1a8,
path=path@entry=0x144b0b0 "/usr/lib64/vlc/plugins/gui/libqt4_plugin.so",
p_handle=p_handle@entry=0x7fffa3ad79e8, lazy=) at
posix/plugin.c:60
#28 0x7fd873160d5d in module_InitDynamic (obj=0x141c1a8, path=0x144b0b0
"/usr/lib64/vlc/plugins/gui/libqt4_plugin.so", fast=) at
modules/bank.c:586
#29 0x7fd873161057 in AllocatePluginDir (st=,
relpath=, abspath=, bank=) at
modules/bank.c:529
#30 0x7fd873161057 in AllocatePluginDir (bank=0x7fffa3ad7c40,
maxdepth=1828714504, absdir=0x0, reldir=0x144a710 "gui") at modules/bank.c:490
#31 0x7fd8731612c9 in AllocatePluginDir (bank=0x7fffa3ad7c40,
maxdepth=1828714504, maxdepth@entry=5, absdir=0x0, absdir@entry=0x144e000
"/usr/lib64/vlc/plugins", reldir=0x0) at modules/bank.c:494
#32 0x7fd873161534 in AllocatePluginPath (p_this=p_this@entry=0x141c1a8,
path=0x144e000 "/usr/lib64/vlc/plugins", mode=mode@entry=CACHE_USE) at
modules/bank.c:403
#33 0x7fd873161a87 in module_LoadPlugins (p_this=0x141c1a8) at
modules/bank.c:330
#34 0x7fd873161a87 in module_LoadPlugins (obj=obj@entry=0x141c1a8) at
modules/bank.c:186
#35 0x7fd8730f949d in libvlc_InternalInit (p_libvlc=0x141c1a8, i_argc=11,
ppsz_argv=0x7fffa3ad7dc0) at libvlc.c:159
#36 0x7fd872eca623 in libvlc_new () 

[digikam] [Bug 364258] Upgrade to 5.0 (beta6) : tags and location data of photos are lost

[Jens B . Benecke via KDE Bugzilla]

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

--- Comment #6 from Jens B. Benecke  ---
> If you copy this file at this place all will start as expected.

Do you expect a normal user (= non-geek, non-programmer) to know that?
Then this is a usability issue, not a technical one. But an important one.
Or is Digikam not meant to be used by non-geeks?

> In all cases, the migration option is not the right way to process.

How should a user know? He can't. So prevent the migration from being abused in
this case. Users should not be able to perform tasks that destroy data,
otherwise they lose their trust in the application.

> But, starting with a new fresh DK setup and configure the collections and the 
> place where the database is stored will normally not touch the DB content and 
> all will be available as with 4.x release. 

OK, but - again - (how) do you expect a normal user (= non-geek,
non-programmer) to know that? From a usability perspective, Digikam5 should
proactively offer to import all Digikam4 settings, collections and so on - no
matter where they were saved previously. Nobody wants to research how to do
this manually, even if it is possible.

Please don't get me wrong, I like Digikam a lot and I want it to be successful.
This is why these things are so important to me.

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

[frameworks-sonnet] [Bug 361409] Support: XDG Base Directory Specification

[Silvio Frischknecht via KDE Bugzilla]

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

--- Comment #1 from Silvio Frischknecht  ---
Created attachment 99652
  --> https://bugs.kde.org/attachment.cgi?id=99652=edit
suggested patch to search using QStandardPath

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

[digikam] [Bug 364614] New: images/albums not deleted in database when deleting/moving in digikam

[Johannes Hirte via KDE Bugzilla]

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

Bug ID: 364614
   Summary: images/albums not deleted in database when
deleting/moving in digikam
   Product: digikam
   Version: 5.0.0
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Database
  Assignee: digikam-de...@kde.org
  Reporter: johannes.hi...@datenkhaos.de

the bug is reported against digikam master

Images and albums are not deleted within the database (mysql) when they're
(re-)moved. Following example:

One collection (digikam5-test) with one album (dir1) and one picture
(crop_10a-fixed.png). 

the Albums table contains two entries: 
id 1; relativePath /
id 2;  relativePath /dir1

the Images table has one entry:
id 1; album 2; name crop_10a-fixed.png; status 1

Now creating a new album dir2 and moving the picture there:

the Albums table contains three entries: 
id 1; relativePath /
id 2;  relativePath /dir1
id 3; relativePath /dir2

the Images table has two entries:
id 1; album NULL; name crop_10a-fixed.png; status 3
id 2; album 2; name crop_10a-fixed.png; status 1

Now deleting album 2 with the picture:

the Albums table still contains three entries: 
id 1; relativePath /
id 2;  relativePath /dir1
id 3; relativePath /dir2

the Images table has still two entries:
id 1; album NULL; name crop_10a-fixed.png; status 3
id 2; album NULL; name crop_10a-fixed.png; status 3

The image and the directory (dir2) are deleted within the filesystem. The
images is also gone in digikam. I think the reason for this is status 3 or
album NULL. The album (dir2) is still shown in digikam with no content.  When
selecting it, digikam shows the error when started on commandline:
digikam.database: Folder does not exist or is not readable: 
"/home/pictures/digikam5-test/dir2"

So at least the handling of deleted albums is broken. But the whole handling of
deleted items looks broken to me. Why are they kept for all time within the db?
A picture or album removed from the collection has to be removed from the db
too. A moved item has to be updated, not inserted new. At moment, the database
is growing with orphaned items nobody will ever need again.

I didn't had the problems with still shown albums after deletion with digikam4.
But I think the problem of newly created db entries with every move of an item
already existed there.

Reproducible: Always

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

[valgrind] [Bug 364413] pselect sycallwrapper mishandles NULL sigmask

[Mark Wielaard via KDE Bugzilla]

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

--- Comment #3 from Mark Wielaard  ---
I made a typo which caused:

...checking makefile consistency
none/tests/Makefile.am:1: error: pselect_sigmask_null.vgtest is missing in
EXTRA_DIST
none/tests/Makefile.am:1: error: pselect_signask_null.vgtest is in EXTRA_DIST
but doesn't exist

Fixed with valgrind svn r15894
Bug 364413 followup - fix signask -> sigmask typo in EXTRA_DIST

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

[kwalletmanager] [Bug 362805] KF5Wallet can't open previuosly created wallet with error code -9

[Maximiliano Curia via KDE Bugzilla]

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

Maximiliano Curia  changed:

   What|Removed |Added

 CC||m...@debian.org

--- Comment #17 from Maximiliano Curia  ---
With the addtion of the test case in:
https://quickgit.kde.org/?p=kwallet.git=commitdiff=7e7644b608e22a13e110284ed6c5426c1b493b43

It's clear now that the blowfish backend doesn't work in big endian, as shown
in the buildds logs for mips and powerpc in Debian:
https://buildd.debian.org/status/package.php?p=kwallet-kf5

Adding back the include:
#include 

and changing the checks for #if Q_BYTE_ORDER == Q_LITTLE_ENDIAN
(effectively reverting the blowfish backend to the state in 
https://quickgit.kde.org/?p=kwallet.git=blob=e09d5422dfb404f2f15e74d693b24bb6cd8e1689=87e774825b779ba846315a8b2ffe6479dd9f9814=src%2Fruntime%2Fkwalletd%2Fbackend%2Fblowfish.cc)
makes the test pass in little and big endian machines.

This changes nothing for little endian machines. And in big endian machines it
should fix the blowfish backend.

Happy hacking,

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

[amarok] [Bug 364602] Amorak crashes on startup (OpenSUSE 13.2 -- MATE Desktop Environment 1.8.1)

[Myriam Schweingruber via KDE Bugzilla]

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

Myriam Schweingruber  changed:

   What|Removed |Added

 Resolution|--- |BACKTRACE
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Myriam Schweingruber  ---
Unfortunately your backtrace has no debugging symbols, please install those and
provide a new and more complete backtrace. See also
https://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

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

[amarok] [Bug 364589] amarok stop after a song

[Myriam Schweingruber via KDE Bugzilla]

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

Myriam Schweingruber  changed:

   What|Removed |Added

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

--- Comment #1 from Myriam Schweingruber  ---
This is a problem with gstreamer, not Amarok, and it was solved by using a
newer phonon-backend-gstreamer that uses the gstreamer 1.x libraries.
You should check with your distribution, they should provide you with these
packages since quite some time already.

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

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

[phonon-backend-gstreamer] [Bug 290706] amarok crashes after trying to start playing song [@ Phonon::Gstreamer::Pipeline::cb_setupSource]

[Myriam Schweingruber via KDE Bugzilla]

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

Myriam Schweingruber  changed:

   What|Removed |Added

 CC||fab8...@gmail.com

--- Comment #139 from Myriam Schweingruber  ---
*** Bug 364589 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 364613] New: plasma crashes upon hotplug of external display on modern intel graphics

[via KDE Bugzilla]

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

Bug ID: 364613
   Summary: plasma crashes upon hotplug of external display on
modern intel graphics
   Product: plasmashell
   Version: 5.6.4
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: databasede...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.6.4)

Qt Version: 5.6.0
Frameworks Version: 5.22.0
Operating System: Linux 4.5.7-200.fc23.x86_64 x86_64
Distribution (Platform): Fedora RPMs

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

I docked my laptop, plugged in an external mini-displayport cable connected to
a Samsung 4K monitor.  Upon doing so, the screen flickered a few times, and
plasma crashed with the attached trace.

Since I have access to a variety of recently built Lenovo laptops in the
Thinkpad T series, I tested this case out on a few systems. The T430 was the
last one that *didn't* crash.  The T440p, T440 and T450s all crash when
connecting an external monitor.

The only correlation I found is to the newer intel integrated GPUs which
contain eDRAM as part of the integrated silicon.  See below chart for
comparison. (please excuse terrible Confluence-like formatting, I'll try to
clean it up for the report.)

|| Laptop Model || Processor || Intel Graphics  || Problem? || 
   Intel URL 
||
| T510   |  i5-560M   |   HD Graphics|No |
http://ark.intel.com/products/49653/Intel-Core-i5-560M-Processor-3M-Cache-2_66-GHz
 |
| T420   |  i5-2450M  | HD Graphics 3000 |no |
http://ark.intel.com/products/53452/Intel-Core-i5-2450M-Processor-3M-Cache-up-to-3_10-GHz
  |
| T430   |  i5-3210M  | HD Graphics 4000 |no |
http://ark.intel.com/products/65708/Intel-Core-i5-3210M-Processor-3M-Cache-up-to-3_10-GHz-BGA
  |
| T440   |  i5-4200U  | HD Graphics 4400 |   yes |
http://ark.intel.com/products/75459/Intel-Core-i5-4200U-Processor-3M-Cache-up-to-2_60-GHz
  |
| T440p  |  i7-4600M  | HD Graphics 4600 |   yes |
http://ark.intel.com/products/76349/Intel-Core-i7-4600M-Processor-4M-Cache-up-to-3_60-GHz
  |
| T450s  |  i7-5600U  | HD Graphics 5500 |   yes |
http://ark.intel.com/products/85215/Intel-Core-i7-5600U-Processor-4M-Cache-up-to-3_20-GHz
  |

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
84T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7f5ebefe5940 (LWP 1907))]

Thread 17 (Thread 0x7f5eb5900700 (LWP 1928)):
#0  0x7f5ecdcbfb1d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f5ed2e59272 in poll (__timeout=-1, __nfds=1, __fds=0x7f5eb58ffb80)
at /usr/include/bits/poll2.h:46
#2  _xcb_conn_wait (c=c@entry=0x55f0adf0bb10, cond=cond@entry=0x55f0adf0bb50,
vector=vector@entry=0x0, count=count@entry=0x0) at xcb_conn.c:459
#3  0x7f5ed2e5aee7 in xcb_wait_for_event (c=0x55f0adf0bb10) at xcb_in.c:693
#4  0x7f5eb7b53349 in QXcbEventReader::run (this=0x55f0adf16230) at
qxcbconnection.cpp:1313
#5  0x7f5ece8d1d48 in QThreadPrivate::start (arg=0x55f0adf16230) at
thread/qthread_unix.cpp:340
#6  0x7f5eccffc61a in start_thread (arg=0x7f5eb5900700) at
pthread_create.c:334
#7  0x7f5ecdccb59d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 16 (Thread 0x7f5ea700 (LWP 1932)):
#0  g_mutex_unlock (mutex=0x7f5ea8000990) at gthread-posix.c:1350
#1  0x7f5ec936f7b0 in g_main_context_prepare
(context=context@entry=0x7f5ea8000990, priority=priority@entry=0x7f5eafffeb10)
at gmain.c:3507
#2  0x7f5ec93700bb in g_main_context_iterate
(context=context@entry=0x7f5ea8000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3820
#3  0x7f5ec937029c in g_main_context_iteration (context=0x7f5ea8000990,
may_block=may_block@entry=1) at gmain.c:3901
#4  0x7f5eceafaa4b in QEventDispatcherGlib::processEvents
(this=0x7f5ea80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#5  0x7f5eceaa34ca in QEventLoop::exec (this=this@entry=0x7f5eafffec50,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f5ece8ccf34 in QThread::exec (this=this@entry=0x7f5ecf306040
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:503
#7  0x7f5ecf2924b5 in QDBusConnectionManager::run (this=0x7f5ecf306040
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:181
#8  0x7f5ece8d1d48 in QThreadPrivate::start (arg=0x7f5ecf306040 <(anonymous

[valgrind] [Bug 364413] pselect sycallwrapper mishandles NULL sigmask

[Mark Wielaard via KDE Bugzilla]

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

Mark Wielaard  changed:

   What|Removed |Added

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

--- Comment #2 from Mark Wielaard  ---
valgrind svn 15893

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

[krita] [Bug 345282] [WACOM CINTIQ] Cursor offset problem

[Boudewijn Rempt via KDE Bugzilla]

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

--- Comment #13 from Boudewijn Rempt  ---
Hi Stephen,

Could you please still attach a tablet log? We need to figureo ut where the
discrepancy is coming from!

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

[plasmashell] [Bug 364612] Launchers on only icon task manager disappear when launching them

[via KDE Bugzilla]

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

d...@kaosx.us changed:

   What|Removed |Added

 CC||d...@kaosx.us

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

[plasmashell] [Bug 364612] New: Launchers on only icon task manager disappear when launching them

[loopset via KDE Bugzilla]

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

Bug ID: 364612
   Summary: Launchers on only icon task manager disappear when
launching them
   Product: plasmashell
   Version: 5.6.95
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: miguellozanogonza...@openmailbox.org
CC: plasma-b...@kde.org

When i click on some icon fixed in the panel, and it takes much time to start,
the icon disappears and, after a while ( a few seconds) it appears. It don't
happen in all apps, only ones that take time to start (like firefox...)

Reproducible: Sometimes

Steps to Reproduce:
1.Click on a launcher  on the panel
2.The icon for a moment vanishes
3.

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

[korganizer] [Bug 353531] Wrong shown events that end the next day.

[szymon . pysz]

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

szymon.p...@gmail.com  changed:

   What|Removed |Added

 CC||szymon.p...@gmail.com

--- Comment #7 from szymon.p...@gmail.com  ---
Any progress??!?!?!

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

[kdenlive] [Bug 364584] Title clips: Shadow offset is not centered at x/y 0,0

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #4 from Jean-Baptiste Mardelle  ---
Git commit 3e4c0cfb7f8c8379a598dc86998e1a50ef147b28 by Jean-Baptiste Mardelle.
Committed on 21/06/2016 at 19:31.
Pushed by mardelle into branch 'master'.

Fix shadow offset in title editor

M  +2-4src/effectstack/graphicsscenerectmove.cpp

http://commits.kde.org/kdenlive/3e4c0cfb7f8c8379a598dc86998e1a50ef147b28

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

[kdenlive] [Bug 364584] Title clips: Shadow offset is not centered at x/y 0,0

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #3 from Jean-Baptiste Mardelle  ---
Git commit c9fbd3f56709ae578e2fb80a1948f4f892129334 by Jean-Baptiste Mardelle.
Committed on 21/06/2016 at 19:30.
Pushed by mardelle into branch 'Applications/16.04'.

Fix shadow offset in title editor

M  +2-4src/effectstack/graphicsscenerectmove.cpp

http://commits.kde.org/kdenlive/c9fbd3f56709ae578e2fb80a1948f4f892129334

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

[krita] [Bug 349443] Icons in brush presets docker sometimes are deformed after switching to another tag

[Sven Langkamp via KDE Bugzilla]

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

Sven Langkamp  changed:

   What|Removed |Added

 CC||sven.langk...@gmail.com
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Sven Langkamp  ---
Is fixed already.

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

[krita] [Bug 364022] Tool options don't load on startup

[Sven Langkamp via KDE Bugzilla]

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

Sven Langkamp  changed:

   What|Removed |Added

 CC||port...@bk.ru

--- Comment #5 from Sven Langkamp  ---
*** Bug 363756 has been marked as a duplicate of this bug. ***

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

[krita] [Bug 363756] Empty "Tool options" docker after upgrade

[Sven Langkamp via KDE Bugzilla]

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

Sven Langkamp  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||sven.langk...@gmail.com
 Status|UNCONFIRMED |RESOLVED

--- Comment #8 from Sven Langkamp  ---


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

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

[Akonadi] [Bug 363390] Akonadi randomly crashes

[s0nny via KDE Bugzilla]

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

s0nny  changed:

   What|Removed |Added

 CC||m.demarc...@gmail.com

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

[Akonadi] [Bug 363390] Akonadi randomly crashes

[s0nny via KDE Bugzilla]

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

--- Comment #1 from s0nny  ---
Created attachment 99651
  --> https://bugs.kde.org/attachment.cgi?id=99651=edit
New crash information added by DrKonqi

akonadi_imap_resource (4.14) on KDE Platform 4.14.2 using Qt 4.8.6

Akonadi crash every 5 minutes. Please fix ASAP because this is really annoying.

-- Backtrace (Reduced):
#6  0x7f56ab03e9bd in KIMAP::SearchJob::handleResponse(KIMAP::Message
const&) () from /usr/lib/libkimap.so.4
#7  0x7f56ab02f94b in
KIMAP::SessionPrivate::responseReceived(KIMAP::Message const&) () from
/usr/lib/libkimap.so.4
#8  0x7f56ad46ee11 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x7f56ac7a648c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#10 0x7f56ac7acfa8 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4

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

[krita] [Bug 364022] Tool options don't load on startup

[Sven Langkamp via KDE Bugzilla]

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

Sven Langkamp  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/krit
   ||a/9318485a49543d06835d914b2
   ||44e8a6983d52052
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from Sven Langkamp  ---
Git commit 9318485a49543d06835d914b244e8a6983d52052 by Sven Langkamp.
Committed on 21/06/2016 at 19:18.
Pushed by langkamp into branch 'master'.

Directly connect toolmanager to mainwindow for the tool options widgets
Fixes the initialisation of the option widget docker/popup

M  +0-5libs/flake/KoCanvasControllerWidget.cpp
M  +0-7libs/flake/KoCanvasControllerWidget.h
M  +2-8libs/flake/KoToolManager.cpp
M  +4-0libs/flake/KoToolManager.h
M  +1-0libs/ui/KisMainWindow.cpp
M  +0-1libs/ui/KisViewManager.cpp

http://commits.kde.org/krita/9318485a49543d06835d914b244e8a6983d52052

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

[krunner] [Bug 364611] New: krunner crashes suddenly

[Miguel Camargo via KDE Bugzilla]

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

Bug ID: 364611
   Summary: krunner crashes suddenly
   Product: krunner
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: m...@vhanda.in
  Reporter: esloqueti...@gmail.com

Application: krunner (5.7.90)

Qt Version: 5.7.0
Frameworks Version: 5.24.0
Operating System: Linux 4.6.2-1-default x86_64
Distribution: "openSUSE Tumbleweed (20160613) (x86_64)"

-- Information about the crash:
krunner crashes randomly often.

The crash can be reproduced every time.

-- Backtrace:
Application: krunner (krunner), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f77619aa8c0 (LWP 2078))]

Thread 13 (Thread 0x7f774b6ec700 (LWP 2079)):
#0  0x7f775d3d39cd in poll () at /lib64/libc.so.6
#1  0x7f775c8c83f2 in _xcb_conn_wait (__timeout=-1, __nfds=1,
__fds=0x7f774b6ebc00) at /usr/include/bits/poll2.h:46
#2  0x7f775c8c83f2 in _xcb_conn_wait (c=c@entry=0x12c32b0,
cond=cond@entry=0x12c32f0, vector=vector@entry=0x0, count=count@entry=0x0) at
xcb_conn.c:479
#3  0x7f775c8ca147 in xcb_wait_for_event (c=0x12c32b0) at xcb_in.c:693
#4  0x7f774da4a629 in  () at /usr/lib64/libQt5XcbQpa.so.5
#5  0x7f775dacc3ef in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f775afd4454 in start_thread () at /lib64/libpthread.so.0
#7  0x7f775d3dc3fd in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7f77495b0700 (LWP 2080)):
#0  0x7f775d3d39cd in poll () at /lib64/libc.so.6
#1  0x7f7758ead3f4 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f7758ead4fc in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f775dced10b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f775dc9713a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f775dac77d4 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f775f7d7c45 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7f775dacc3ef in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f775afd4454 in start_thread () at /lib64/libpthread.so.0
#9  0x7f775d3dc3fd in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7f7742cb7700 (LWP 2091)):
#0  0x7f775d3cf9ad in read () at /lib64/libc.so.6
#1  0x7f7758eef490 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f7758eacf24 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f7758ead398 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f7758ead4fc in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f775dced10b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f775dc9713a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f775dac77d4 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f77603b8e25 in  () at /usr/lib64/libQt5Qml.so.5
#9  0x7f775dacc3ef in  () at /usr/lib64/libQt5Core.so.5
#10 0x7f775afd4454 in start_thread () at /lib64/libpthread.so.0
#11 0x7f775d3dc3fd in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7f7723995700 (LWP 3196)):
#0  0x7f775afda06f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f775dacd2bb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f77379a7c9f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f77379abc18 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f77379a6e8d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f77379abc72 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f77379a6e8d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7f77379a980f in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7f775dacc3ef in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f775afd4454 in start_thread () at /lib64/libpthread.so.0
#10 0x7f775d3dc3fd in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7f7723194700 (LWP 3197)):
[KCrash Handler]
#6  0x7f775d328908 in raise () at /lib64/libc.so.6
#7  0x7f775d329d5a in abort () at /lib64/libc.so.6
#8  0x7f775dab2ea1 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f75b29d687b in QtWebEngineCore::initialize() () at
/usr/lib64/libQt5WebEngineCore.so.5
#10 0x7f775dc97f77 in qAddPreRoutine(void (*)()) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f77617fd5aa in call_init.part () at /lib64/ld-linux-x86-64.so.2
#12 0x7f77617fd6bb in _dl_init () at /lib64/ld-linux-x86-64.so.2
#13 0x7f7761801c10 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2
#14 

[kwin] [Bug 364498] I've to type kwin --replace many times after KDE plasma or else crashed

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |BACKTRACE
  Component|activities  |aurorae

--- Comment #4 from Thomas Lübking  ---
> Plugin: org.kde.kwin.aurorae
> Theme: __aurorae__svg__Yosemite

run "kcmshell5 kwindecoration" and switch to breeze.
Report back whether that helped and if you can, still provide a backtrace of
the crashes (this is very likely a dupe)

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

[cantor] [Bug 363560] Sage backend is not working with Sage 7.2 version

[jackdyson31 via KDE Bugzilla]

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

jackdyson31  changed:

   What|Removed |Added

 CC||jackdyso...@gmail.com

--- Comment #5 from jackdyson31  ---
Hi Filipe,

I don't suppose something similar can be done for the 14.04 versions can there
?

my "fixes" broke the automated tex output for it ...

best,

Jack

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

[kdenlive] [Bug 364608] Git master 2016-06-21 - Delete button on group of effects does nothing

[Evert Vorster via KDE Bugzilla]

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

Evert Vorster  changed:

   What|Removed |Added

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

--- Comment #2 from Evert Vorster  ---
Awesome, thanks!

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

[kdenlive] [Bug 364608] Git master 2016-06-21 - Delete button on group of effects does nothing

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #1 from Jean-Baptiste Mardelle  ---
Git commit e17eb1f7921caf32eb59c838505737e5c2208137 by Jean-Baptiste Mardelle.
Committed on 21/06/2016 at 18:28.
Pushed by mardelle into branch 'master'.

Fix deletion of effect group

M  +3-1src/timeline/customtrackview.cpp

http://commits.kde.org/kdenlive/e17eb1f7921caf32eb59c838505737e5c2208137

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

[akregator] [Bug 357277] Akregator crashed when opening a link in a news feed

[Andreas C via KDE Bugzilla]

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

Andreas C  changed:

   What|Removed |Added

 CC||achatzievgena...@outlook.co
   ||m

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

[akregator] [Bug 357277] Akregator crashed when opening a link in a news feed

[Andreas C via KDE Bugzilla]

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

--- Comment #1 from Andreas C  ---
Created attachment 99650
  --> https://bugs.kde.org/attachment.cgi?id=99650=edit
New crash information added by DrKonqi

kontact (4.14.10) on KDE Platform 4.14.18 using Qt 4.8.6

- What I was doing when the application crashed:
Reading new feeds in Kontact Aggregator. Happen only at KDE feeds

-- Backtrace (Reduced):
#6  0x7f9f4980f3a7 in QtMIMETypeSniffer::~QtMIMETypeSniffer() () from
/usr/lib64/libQtWebKit.so.4
#7  0x7f9f487e7a5c in
WebCore::JSNodeOwner::isReachableFromOpaqueRoots(JSC::Handle,
void*, JSC::SlotVisitor&) () from /usr/lib64/libQtWebKit.so.4
#8  0x7f9f4990aa9a in JSC::WeakBlock::visit(JSC::HeapRootVisitor&) () from
/usr/lib64/libQtWebKit.so.4
#9  0x7f9f4991833b in
JSC::MarkedSpace::visitWeakSets(JSC::HeapRootVisitor&) () from
/usr/lib64/libQtWebKit.so.4
#10 0x7f9f4990d785 in JSC::Heap::markRoots(bool) () from
/usr/lib64/libQtWebKit.so.4

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

[kwin] [Bug 340489] All windows in KDE 5 starts glitching after some usage time

[Filip via KDE Bugzilla]

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

--- Comment #44 from Filip  ---
^ Probably not the same - that was about flickering. I tried the third solution
anyway and am still getting these diagonal glitches and system slowness along
with it.

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

[kwin] [Bug 364498] I've to type kwin --replace many times after KDE plasma or else crashed

[Michel via KDE Bugzilla]

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

--- Comment #3 from Michel  ---
I found 

qdbus org.kde.KWin /KWin supportInformation
KWin Support Information:
The following information should be used when requesting support on e.g.
http://forum.kde.org.
It provides information about the currently running instance, which options are
used,
what OpenGL driver and which effects are running.
Please post the information provided underneath this introductory text to a
paste bin service
like http://paste.kde.org instead of pasting into support threads.

==

Version
===
KWin version: 5.5.5
Qt Version: 5.5.1
Qt compile version: 5.5.1
XCB compile version: 1.11.1

Operation Mode: X11 only

Build Options
=
KWIN_BUILD_DECORATIONS: yes
KWIN_BUILD_TABBOX: yes
KWIN_BUILD_ACTIVITIES: yes
HAVE_INPUT: yes
HAVE_DRM: yes
HAVE_GBM: yes
HAVE_X11_XCB: yes
HAVE_EPOXY_GLX: yes
HAVE_WAYLAND_EGL: yes

X11
===
Vendor: The X.Org Foundation
Vendor Release: 11803000
Protocol Version/Revision: 11/0
SHAPE: yes; Version: 0x11
RANDR: yes; Version: 0x14
DAMAGE: yes; Version: 0x11
Composite: yes; Version: 0x4
RENDER: yes; Version: 0xb
XFIXES: yes; Version: 0x50
SYNC: yes; Version: 0x31
GLX: yes; Version: 0x0

Decoration
==
Plugin: org.kde.kwin.aurorae
Theme: __aurorae__svg__Yosemite
Blur: 1
onAllDesktopsAvailable: false
alphaChannelSupported: true
closeOnDoubleClickOnMenu: false
decorationButtonsLeft: 0, 2
decorationButtonsRight: 6, 3, 4, 5
borderSize: 3
gridUnit: 10
font: Noto Sans,10,-1,0,50,0,0,0,0,0
smallSpacing: 2
largeSpacing: 10

Options
===
focusPolicy: 0
nextFocusPrefersMouse: false
clickRaise: true
autoRaise: false
autoRaiseInterval: 0
delayFocusInterval: 0
shadeHover: false
shadeHoverInterval: 250
separateScreenFocus: false
placement: 4
focusPolicyIsReasonable: true
borderSnapZone: 10
windowSnapZone: 10
centerSnapZone: 0
snapOnlyWhenOverlapping: false
rollOverDesktops: true
focusStealingPreventionLevel: 1
legacyFullscreenSupport: false
operationTitlebarDblClick: 5000
operationMaxButtonLeftClick: 5000
operationMaxButtonMiddleClick: 5015
operationMaxButtonRightClick: 5014
commandActiveTitlebar1: 0
commandActiveTitlebar2: 30
commandActiveTitlebar3: 2
commandInactiveTitlebar1: 4
commandInactiveTitlebar2: 30
commandInactiveTitlebar3: 2
commandWindow1: 7
commandWindow2: 8
commandWindow3: 8
commandWindowWheel: 31
commandAll1: 10
commandAll2: 3
commandAll3: 14
keyCmdAllModKey: 16777251
showGeometryTip: false
condensedTitle: false
electricBorderMaximize: true
electricBorderTiling: true
electricBorderCornerRatio: 0.25
borderlessMaximizedWindows: false
killPingTimeout: 5000
hideUtilityWindowsForInactive: true
inactiveTabsSkipTaskbar: false
autogroupSimilarWindows: false
autogroupInForeground: true
compositingMode: 1
useCompositing: true
compositingInitialized: true
hiddenPreviews: 1
unredirectFullscreen: false
glSmoothScale: 2
colorCorrected: false
xrenderSmoothScale: false
maxFpsInterval: 1666
refreshRate: 0
vBlankTime: 600
glStrictBinding: true
glStrictBindingFollowsDriver: true
glCoreProfile: false
glPreferBufferSwap: 101
glPlatformInterface: 1

Screen Edges

desktopSwitching: false
desktopSwitchingMovingClients: false
cursorPushBackDistance: 1x1
timeThreshold: 150
reActivateThreshold: 350
actionTopLeft: 0
actionTop: 0
actionTopRight: 0
actionRight: 0
actionBottomRight: 0
actionBottom: 0
actionBottomLeft: 0
actionLeft: 0

Screens
===
Multi-Head: no
Active screen follows mouse:  no
Number of Screens: 1

Screen 0:
-
Name: eDP1
Geometry: 0,0,1366x768
Refresh Rate: 60.0031


Compositing
===
Compositing is active
Compositing Type: OpenGL
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 520 (Skylake GT2) 
OpenGL version string: 3.0 Mesa 11.2.0
OpenGL platform interface: GLX
OpenGL shading language version string: 1.30
Driver: Intel
GPU class: Unknown
OpenGL version: 3.0
GLSL version: 1.30
Mesa version: 11.2
X server version: 1.18.3
Linux kernel version: 4.4
Direct rendering: Requires strict binding: yes
GLSL shaders:  yes
Texture NPOT support:  yes
Virtual Machine:  no
OpenGL 2 Shaders are used
Painting blocks for vertical retrace:  no

Loaded Effects:
---
zoom
slidingpopups
kwin4_effect_login
slide
screenshot
kwin4_effect_translucency
kwin4_effect_windowaperture
minimizeanimation
desktopgrid
kwin4_effect_maximize
kwin4_effect_fade
presentwindows
highlightwindow
kwin4_effect_dialogparent
blur
contrast
logout
startupfeedback
screenedge
kscreen

Currently Active Effects:
-
blur
contrast

Effect Settings:

zoom:
zoomFactor: 1.2
mousePointer: 0
mouseTracking: 0
enableFocusTracking: false
followFocus: true
focusDelay: 350
moveFactor: 20
targetZoom: 1

slidingpopups:
fadeInTime: 150
fadeOutTime: 250

kwin4_effect_login:

slide:

screenshot:

kwin4_effect_translucency:

kwin4_effect_windowaperture:

minimizeanimation:

[Discover] [Bug 364610] Program description overflowing text label at the carousel of featured apps.

[Martín Cortina via KDE Bugzilla]

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

--- Comment #2 from Martín Cortina  ---
Created attachment 99649
  --> https://bugs.kde.org/attachment.cgi?id=99649=edit
Description of "Krita" app looks fine instead

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

[Discover] [Bug 364610] Program description overflowing text label at the carousel of featured apps.

[Martín Cortina via KDE Bugzilla]

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

--- Comment #1 from Martín Cortina  ---
Created attachment 99648
  --> https://bugs.kde.org/attachment.cgi?id=99648=edit
Description overflowing outer box

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

[Discover] [Bug 364610] New: Program description overflowing text label at the carousel of featured apps.

[Martín Cortina via KDE Bugzilla]

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

Bug ID: 364610
   Summary: Program description overflowing text label at the
carousel of featured apps.
   Product: Discover
   Version: 5.6.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: hellraise...@gmail.com

On Discover's main screen, the carousel widget shows four "featured" apps, each
having a background picture, perhaps an icon, and a description.

Two distinct behaviors can be observed:
 * "Krita" app seems ok. You can see the background picture, the name of the
app, and a single lined description that is being ellipticized within the
bounds of the outer box.

 * "ImagePlugin-Enhance", "VLC Media Player" and "KDE Marble" apps are not
showing ok. Descriptions are overflowing from the outer box, as they're not
being ellipticized. Instead, the entire description of each package is being
shown, which is probably not the expected behavior.


Reproducible: Always

Steps to Reproduce:
1. Open Discover and pay attention at the carousel of featured apps.

Actual Results:  
Krita app looks fine, the other apps do not. (I'll be attaching a screenshot if
possible)

Expected Results:  
All descriptions should fit withing their respective boxes

OS Distribution: Kubuntu
lsb_release -a output:
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04 LTS
Release:16.04
Codename:   xenial

Information from Discover's About box:
Version: 5.6.2
Using:
* KDE Frameworks 5.18.0
* Qt 5.5.1 (built against 5.5.1)
* The xcb windowing system

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

[krusader] [Bug 364609] New: copy location/path bar (feature request)

[via KDE Bugzilla]

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

Bug ID: 364609
   Summary: copy location/path bar (feature request)
   Product: krusader
   Version: 2.4.0-beta3 "Single Step"
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: m...@fork.pl
  Reporter: j22...@gmail.com

The tool "Copy current item to clipboard" copies the full path of a file to
clipboard, including the name of the file, for example:
"/home/user/data/pics/russia/day02/motherland.jpg"

 It would be great to have an option like that but without the file name, for
example:
"/home/user/data/pics/russia/day02"

I would like to request something which should be extremely easy to implement.

In TotalCommander, I was used to copy the location (full  path) of a directory
from the location/path bar. This is great for many occasions when you need to
go to a specific location (which you already have open in krusader) while using
another software. For example, you are working with many photos which you are
browsing within a krusader tab which shows the
"/home/user/data/pics/russia/day02" directory. You finish editing them and want
to send some of them by email. I open the email program and press "attach"
button, which opens always in Desktop folder, so every time I have to navigate
to "/home/user/data/pics/russia/day02" directory to actually select and attach
the pictures.
Another example: when you download a file or want to save a brand new file
which you just started, you press "save" (eg in your word processor) and when
the save dialog opens you have to, again, navigate until you see the directory
which in general I already have opened in Krusader.

It is possible to do in Krusader, but it's cumbersome because takes many
unnecessary steps:
- left-click into the location bar
- it does not automatically select the text, so you have to select it 
- but when you press right-click to "copy", it deselects the text!!

So the only way to do it is
1- left-click into the location bar
2- CTRL-A to select all
3- CTRL-C to copy to clipboard

whereas it could be (as in TotalCommander)
1- left-click into the location bar (it auto-selects the text)
2- right-click to copy

I would simply right-click into the path bar, wait one second (then all the
text into the location bar gets selected, so I then copy with right-click or
CTRL+C 

Reproducible: Always

Steps to Reproduce:
1. left-click into the location bar
2. select all text
3. CTRL+C to copy

Actual Results:  
Copying the location bar takes step which are not intuitive (eg the selected
text is de-selected when right-clicking to copy)

Expected Results:  
it would be great if the location could be copied to clipboard very easily. If
possible with a command like "Copy current item to clipboard" (which can be
placed as button in the Main Menu).
Otherwise it should be less cumbersome to copy with mouse or keyboard from the
location menu. One suggested way is the TotalCommander way:
1- click into the location bar and this automatically selects all the text of
the location bar (ie full path of the directory)
2- either CTRL-C or right-click to copy to clipboard

I have Linux Mint 17.3 KDE

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

[kwin] [Bug 364498] I've to type kwin --replace many times after KDE plasma or else crashed

[Michel via KDE Bugzilla]

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

--- Comment #2 from Michel  ---
Hi Thomas,

Thanks to answer

The kwin_x11 or kwin-x11 commands are not present on my system

How to get the output of "qdbus org.kde.KWin /KWin supportInformation?

Thanks

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

[juk] [Bug 359346] Scrobbling to last.fm is broken

[Marcos Paulo Serafim via KDE Bugzilla]

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

Marcos Paulo Serafim  changed:

   What|Removed |Added

 CC||mpsera...@gmail.com

--- Comment #2 from Marcos Paulo Serafim  ---
Created attachment 99647
  --> https://bugs.kde.org/attachment.cgi?id=99647=edit
Check if KWallet is enabled and create a QNetworkManager if not created.

In my environment the KWallet::Wallet::folderDoesNotExist does not check if the
KWallet is enabled and returns a wrong value about it.
The Scrobbler code only creates the QNetworkManager if the getAuthToken is
called.

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

[kate] [Bug 267508] No sort by custom option in document view in kate 3.6.0

[Buovjaga via KDE Bugzilla]

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

Buovjaga  changed:

   What|Removed |Added

Version|unspecified |16.04.1
 CC||todven...@suomi24.fi
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #11 from Buovjaga  ---
Still missing.

Arch Linux 64-bit
Kate 16.04.2
KDE Frameworks 5.22.0
Qt 5.6.1
xcb wm

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

[kate] [Bug 342322] bidi text with parentheses enclosing Hebrew: both parentheses face the same direction

[Buovjaga via KDE Bugzilla]

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

Buovjaga  changed:

   What|Removed |Added

Version|3.13.2  |16.04.1
   Severity|normal  |minor

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