[kde] [Bug 366071] Crash on drag titlebar items

[via KDE Bugzilla]

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

z...@sietecfast.com changed:

   What|Removed |Added

   Keywords||accessibility

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

[kde] [Bug 366071] New: Crash on drag titlebar items

[via KDE Bugzilla]

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

Bug ID: 366071
   Summary: Crash on drag titlebar items
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: z...@sietecfast.com

Application: kcmshell5 (5.7.0)

Qt Version: 5.6.1
Frameworks Version: 5.24.0
Operating System: Linux 4.6.4-1-default x86_64
Distribution: "openSUSE Tumbleweed (20160718) (x86_64)"

-- Information about the crash:
Was dragging the close button to the far left instead of right always crashes
when attempting to go all the way left.  Possibly an array out of bounds trying
to to go a non-existing entry??

The crash can be reproduced sometimes.

-- Backtrace:
Application: System Settings Module (kcmshell5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fbe05a708c0 (LWP 18893))]

Thread 6 (Thread 0x7fbdc59a6700 (LWP 19286)):
#0  0x7fbe053e00a3 in select () at /lib64/libc.so.6
#1  0x7fbe02a8030f in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /usr/lib64/libQt5Core.so.5
#2  0x7fbe02a81db4 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#3  0x7fbe02a822ca in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fbe02a2c76a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fbe028523b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fbe013d11e5 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fbe028572d8 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fbdff83c474 in start_thread () at /lib64/libpthread.so.0
#9  0x7fbe053e73ed in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7fbdcd63e700 (LWP 19285)):
#0  0x7fbe053e00a3 in select () at /lib64/libc.so.6
#1  0x7fbe02a8030f in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /usr/lib64/libQt5Core.so.5
#2  0x7fbe02a81db4 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#3  0x7fbe02a822ca in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fbe02a2c76a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fbe028523b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fbe013d11e5 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fbe028572d8 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fbdff83c474 in start_thread () at /lib64/libpthread.so.0
#9  0x7fbe053e73ed in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7fbdd66c8700 (LWP 19101)):
#0  0x7fbe02a81f80 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#1  0x7fbe02a822ca in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#2  0x7fbe02a2c76a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#3  0x7fbe028523b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#4  0x7fbe013d11e5 in  () at /usr/lib64/libQt5Qml.so.5
#5  0x7fbe028572d8 in  () at /usr/lib64/libQt5Core.so.5
#6  0x7fbdff83c474 in start_thread () at /lib64/libpthread.so.0
#7  0x7fbe053e73ed in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fbdee379700 (LWP 18927)):
#0  0x7fbe053e00a3 in select () at /lib64/libc.so.6
#1  0x7fbe02a8030f in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /usr/lib64/libQt5Core.so.5
#2  0x7fbe02a81db4 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#3  0x7fbe02a822ca in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fbe02a2c76a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fbe028523b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fbe046f59b5 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7fbe028572d8 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fbdff83c474 in start_thread () at /lib64/libpthread.so.0
#9  0x7fbe053e73ed in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fbdf2031700 (LWP 18908)):
#0  0x7fbe053dea1d in poll () at /lib64/libc.so.6
#1  0x7fbe000b4410 in  () at /usr/lib64/libxcb.so.1
#2  0x7fbe000b61a9 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7fbdf459c7b9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fbe028572d8 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fbdff83c474 in start_thread () at /lib64/libpthread.so.0
#6  0x7fbe053e73ed in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fbe05a708c0 (LWP 18893)):
[KCrash Handler]
#6  0x7fbe028c5fb0 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7fbe029d7dd4 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fbe029d88b9 

[plasmashell] [Bug 366070] New: Plasma sometimes crashes when monitor is switched back on

[Scott Alfter via KDE Bugzilla]

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

Bug ID: 366070
   Summary: Plasma sometimes crashes when monitor is switched back
on
   Product: plasmashell
   Version: 5.5.5
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: sc...@alfter.us
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)
 (Compiled from sources)
Qt Version: 5.5.1
Operating System: Linux 4.4.6-gentoo x86_64
Distribution: "NAME=Gentoo"

-- Information about the crash:
- What I was doing when the application crashed:
Turned the monitor back on after having turned it off earlier

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

Thread 7 (Thread 0x7f96a9749700 (LWP 4447)):
#0  0x7f96b65683ed in poll () from /lib64/libc.so.6
#1  0x7f96ba582ac2 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f96ba58472f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f96ab27dc89 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f96b6c1c2a2 in ?? () from /usr/lib64/libQt5Core.so.5
#5  0x7f96b5d79434 in start_thread () from /lib64/libpthread.so.0
#6  0x7f96b657150d in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f96a250f700 (LWP 4472)):
#0  0x7f96b65683ed in poll () from /lib64/libc.so.6
#1  0x7f96b2393f2c in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f96b239403c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f96b6e185ac in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f96b6dc97ba in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f96b6c17834 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f96b94215f5 in ?? () from /usr/lib64/libQt5Qml.so.5
#7  0x7f96b6c1c2a2 in ?? () from /usr/lib64/libQt5Core.so.5
#8  0x7f96b5d79434 in start_thread () from /lib64/libpthread.so.0
#9  0x7f96b657150d in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f969ab72700 (LWP 4488)):
#0  0x7f96b65683ed in poll () from /lib64/libc.so.6
#1  0x7f96b2393f2c in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f96b239403c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f96b6e185ac in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f96b6dc97ba in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f96b6c17834 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f96b94215f5 in ?? () from /usr/lib64/libQt5Qml.so.5
#7  0x7f96b6c1c2a2 in ?? () from /usr/lib64/libQt5Core.so.5
#8  0x7f96b5d79434 in start_thread () from /lib64/libpthread.so.0
#9  0x7f96b657150d in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f9699335700 (LWP 4507)):
#0  0x7f96b2390f8d in ?? () from /usr/lib64/libglib-2.0.so.0
#1  0x7f96b239340b in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f96b2393e58 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f96b239403c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f96b6e185ac in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#5  0x7f96b6dc97ba in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#6  0x7f96b6c17834 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#7  0x7f96b94215f5 in ?? () from /usr/lib64/libQt5Qml.so.5
#8  0x7f96b6c1c2a2 in ?? () from /usr/lib64/libQt5Core.so.5
#9  0x7f96b5d79434 in start_thread () from /lib64/libpthread.so.0
#10 0x7f96b657150d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f9693995700 (LWP 4526)):
#0  0x7f96b5d7f00f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f96bb81e924 in ?? () from /usr/lib64/libQt5Script.so.5
#2  0x7f96bb81e969 in ?? () from /usr/lib64/libQt5Script.so.5
#3  0x7f96b5d79434 in start_thread () from /lib64/libpthread.so.0
#4  0x7f96b657150d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f9690d02700 (LWP 4527)):
#0  0x7f96b65643cd in read () from /lib64/libc.so.6
#1  0x7f96b23d66c0 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f96b23939dc in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f96b2393ed0 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7f96b239403c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f96b6e185ac in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#6  0x7f96b6dc97ba in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#7  0x7f96b6c17834 in 

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[Michael Butash via KDE Bugzilla]

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

--- Comment #160 from Michael Butash  ---
I did the same thing yesterday upgrading to neon 5.7.2 with libqt 5.7.0, and
shutting off the displays for a while, then coming back didn't cause it to
freak out as it normally did.  This was only once though so far.  I'm going to
shut down displays when going to bed, almost always by morning it's be wacky
and requiring a reboot to normalize.

Seems like once the displays were detached, a quick on and off wouldn't cause
symptoms always, but more like if displays were gone, and some event occurred,
it began spiraling downhill fast.

Sadly my taskbar still can't seem to stay in the proper display still, and
attempting to move it just jumbled all my wallpaper orders, but here's hoping
multi-monitor is less infuriating soon in kde!

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

[kdenlive] [Bug 366069] New: Keyboard commands ALT+ and ALT+ get stuck on Guides

[Steve via KDE Bugzilla]

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

Bug ID: 366069
   Summary: Keyboard commands ALT+ and ALT+ get stuck
on Guides
   Product: kdenlive
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: ste...@humanint.com

>From Git today 16.11.70
Most of the time, the timeline cursor gets stuck on a guide when I am
navigating through a project.
I am using ALT+ and ALT+

Sometimes it does work, most of the time it doesn't. 
I haven't noticed it getting stuck on clip boundaries or transitions.

When the error happens, I can click past it with the mouse.



Reproducible: Sometimes

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

[KScreen] [Bug 366067] Impartial kscreen config for setup leads to partially configured desktop on hitting 'Apply'

[jamese via KDE Bugzilla]

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

--- Comment #4 from jamese  ---
Plasma 5.7.2, Qt 5.7, Neon/User packages.

I'll try to grab some debugging info when it happens again based on
https://community.kde.org/Solid/Projects/ScreenManagement

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

[KScreen] [Bug 366067] Impartial kscreen config for setup leads to partially configured desktop on hitting 'Apply'

[jamese via KDE Bugzilla]

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

--- Comment #3 from jamese  ---
Created attachment 100281
  --> https://bugs.kde.org/attachment.cgi?id=100281=edit
Photo of Laptop Screen when it's split down the middle

The left part of the screen is moved to the right, the other half is on the
left. Panel is at top on purpose.
The location of the split is based on where the external screens are joined
above the Laptop Screen.

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

[kdenlive] [Bug 366068] Can not right-click a guideline and choose "Delete Guide"

[Steve via KDE Bugzilla]

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

--- Comment #1 from Steve  ---
This is from Git today 16.11.70

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

[kdenlive] [Bug 366068] New: Can not right-click a guideline and choose "Delete Guide"

[Steve via KDE Bugzilla]

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

Bug ID: 366068
   Summary: Can not right-click a guideline and choose "Delete
Guide"
   Product: kdenlive
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: ste...@humanint.com

"Delete Guide" is greyed-out 

If I assign a shortcut to Delete Guide and then get my timeline cursor exactly
on the guide I can then delete it with the keyboard but not the mouse.

Right Clicking on the timeline ruler and selecting Delete All Guides does work.


Reproducible: Always

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

[KScreen] [Bug 366067] Impartial kscreen config for setup leads to partially configured desktop on hitting 'Apply'

[jamese via KDE Bugzilla]

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

--- Comment #2 from jamese  ---
Created attachment 100280
  --> https://bugs.kde.org/attachment.cgi?id=100280=edit
Kscreen config for setup when displays correctly configure

This config includes the "mode" entry. It has the same filename as the config
without the mode entry.

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

[KScreen] [Bug 366067] Impartial kscreen config for setup leads to partially configured desktop on hitting 'Apply'

[jamese via KDE Bugzilla]

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

--- Comment #1 from jamese  ---
Created attachment 100279
  --> https://bugs.kde.org/attachment.cgi?id=100279=edit
Possibly impartial Kscreen config leading to bug ?

This is the config that was active at the time of the bug. The 'mode' entries
are not present for the two external screens

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

[KScreen] [Bug 366067] New: Impartial kscreen config for setup leads to partially configured desktop on hitting 'Apply'

[jamese via KDE Bugzilla]

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

Bug ID: 366067
   Summary: Impartial kscreen config for setup leads to partially
configured desktop on hitting 'Apply'
   Product: KScreen
   Version: 5.7.2
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: se...@kde.org
  Reporter: james.el...@gmail.com

I've got a DisplayPort 1.2 / MST setup, same is in the unrelated Bug #362570.
There are two DP1.2 screens above the laptop screen, the laptop is placed below
and in the middle of the two external screens. The left screen DP1-2 is the
last in the MST chain, the right is the primary screen in the chain.

Often when I configure the screens for this setup in Display Settings, the 2
external screens appear greyed out in the Display Settings area and are not
marked as "Enabled". When I Enable them, position them and then hit "Apply" the
external screens remain blank and the Laptop Screen is split down the middle
(probably due to the positioning in Display Settings). 
No widgets or applications are usable when this happens but the mouse cursor
remains movable.

The only way to resurrect the Desktop is by switching to a another run level,
moving the offending ~/.local/share/kscreen config file (or all of them) and
then restarting sddm, then logging in again. At this point the screen
configuration proceeds OK.
Obviously restarting SDDM causes all running applications to close including
running virtual machines which means I now close all applications and shutdown
virtual machines before trying to configure this screen setup to avoid issues
with the VMs.

In the other run level, I check the config file being used by kscreen and it
appears that the two external screens are missing the "mode" entry, which
contain refresh and size values.  If I was a user that didn't know about
runlevels I'd probably hard reset the laptop.


Makes me think that the config is being partially applied or being applied
without refresh, width and height values.


See upcoming attachments and some debug output. This happened with Kubuntu
16.04 packages as well (now using Neon/User)

I can switch to an HDMI / Displayport hybrid setup and see if this can
reproduced as it would help to isolate the issue.



Reproducible: Sometimes

Steps to Reproduce:
1. Plug in Display Port  1.2 / MST screens, external screens don't
automatically configure
2. Position and Enable external screens
3. Hit Apply, laptop screens split down the middle and is unresponsive

Actual Results:  
Switched to runlevel 1 and remove kscreen config, then restart sddm to
reconfigured screens

Expected Results:  
External screens should be configured and appear with most recent panel
configuration, laptop screen should not split down the middle.

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

[kdenlive] [Bug 366066] New: Timeline minimum width is too long on Dual-Monitors

[Steve via KDE Bugzilla]

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

Bug ID: 366066
   Summary: Timeline minimum width is too long on Dual-Monitors
   Product: kdenlive
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: ste...@humanint.com

>From GIT today 16.11.70

After I save/close/and reopen a project, the timeline widget (found under
view/timeline) sizes to a minimum of bigger than 1 monitor.

If I disable the second monitor, the timeline widget will allow resizing
smaller than the monitor.

Using 2 monitors, after i open the project and it will not fit on 1 monitor, I
can disable the timeline widget (view/timeline) and resize the project to fit
on 1 monitor. Re-enable the timeline and the project auto resizes larger than 1
monitor.


Reproducible: Always

Steps to Reproduce:
Start with a 2 monitor setup
1. Add a 24 minute video clip to the timeline
2. Save the project and close kdenlive
3. open kdenlive and the project

Actual Results:  
The kdenlive window will not allow resize to fit on 1 monitor

Expected Results:  
kdenlive should allow me to resize the width very small

The work around is to disable the second monitor and use only 1 monitor. The
drawback is the project monitor widget is very small for a multitrack view.

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

[rsibreak] [Bug 365599] high cpu usage of plasmashell when rsibreak is running

[via KDE Bugzilla]

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

--- Comment #10 from code...@gmail.com ---
 This is my rsibreakrc:

[General]
AutoStart=false
LastRunBigLeft=3586
LastRunTimeStamp=2016,7,25,9,7,43
LastRunTinyLeft=1786

[General Settings]
BigDuration=1
BigInterval=60
DisableAccel=false
Effect=0
Graylevel=80
HideLockButton=false
HideMinimizeButton=false
HidePostponeButton=false
ImageFolder=/home/thinhnt
Patience=30
PostponeBreakDuration=5
SearchRecursiveCheck=false
ShowSmallImagesCheck=true
SlideInterval=10
TinyDuration=20
TinyInterval=10
UseNoIdleTimer=true
UsePlasmaReadOnly=true

[Notification Messages]
dont_show_welcome_again_for_001=false

[Popup Settings]
UseFlash=true
UsePopup=true

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[jamese via KDE Bugzilla]

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

--- Comment #159 from jamese  ---
As an addition to my recent update, Installed the plasma 5.7.2 update on the
weeked in Neon/User and played around plugging/unplugging screens on
Displayport 1.2 / MST setup and haven't been able to reproduce beyond one
initially duplicated panel which seems to have been left from my other
multi-screen setup.
I'd tentatively say 5.7.2 goes a long way to fix this but not 100% sure yet :D

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

[plasmashell] [Bug 344969] Shortcut configuration for Folder View actions not handled by standard keys

[Leslie Zhai via KDE Bugzilla]

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

--- Comment #40 from Leslie Zhai  ---
Hi rmbg,

It needs a configuration place for Shift+Del and F2 as suggested here
https://git.reviewboard.kde.org/r/128444/ and I am learning 'Folder View
settings page' without changing Qt...

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

[konqueror] [Bug 331707] Moving a file to trash is extremely slow

[Leslie Zhai via KDE Bugzilla]

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

--- Comment #9 from Leslie Zhai  ---
Hi Eike and David,

It is very difficult for me to reproduce this issue and also described here
https://bugs.kde.org/show_bug.cgi?id=344969#c29

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

[konqueror] [Bug 331707] Moving a file to trash is extremely slow

[Leslie Zhai via KDE Bugzilla]

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

Leslie Zhai  changed:

   What|Removed |Added

 CC||fa...@kde.org

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

[konqueror] [Bug 331707] Moving a file to trash is extremely slow

[Leslie Zhai via KDE Bugzilla]

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

Leslie Zhai  changed:

   What|Removed |Added

 CC||h...@kde.org,
   ||xiangzha...@gmail.com

--- Comment #8 from Leslie Zhai  ---
Hi Janek and vindicator,


https://quickgit.kde.org/?p=plasma-desktop.git=blobdiff=618d9a51b1e62ae064248abe6ffeb4cf3b08f31a=ae886bad540178a7c7b874ffed8eda4018de2f6a=1b37262d13b40193eb755af9c3a9bff2d2bcec1a=containments%2Fdesktop%2Fplugins%2Ffolder%2Ffoldermodel.cpp

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

[konsole] [Bug 336310] Blinking cursor doesn't blink when scrolled up

[via KDE Bugzilla]

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

--- Comment #3 from kdeb...@toeai.com ---
(In reply to Christoph Feck from comment #2)
> TerminalDisplay::imageToWidget() doesn't take scroll position into account.

If you've tracked down the cause, could you at least mark this CONFIRMED?

It's still a problem on 16.04.2

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

[plasmashell] [Bug 366065] New: sequence of 3 mouse clicks unexpectedly opens desktop icons because focus is not lost

[via KDE Bugzilla]

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

Bug ID: 366065
   Summary: sequence of 3 mouse clicks unexpectedly opens desktop
icons because focus is not lost
   Product: plasmashell
   Version: 5.6.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Folder
  Assignee: h...@kde.org
  Reporter: kdeb...@toeai.com
CC: plasma-b...@kde.org

Observed on up-to-date Manjaro 64-bit

Reproducible: Always

Steps to Reproduce:
1. Put a link to an application on the Desktop, or any other openable file.
2. Make sure you're in Folder View layout so you can see it.
3. Right-click the icon.
4. Move the mouse away onto a blank area of the desktop and left-click twice. 
(Does not require a fast double-click: only that you don't move the mouse
between the clicks.)

Actual Results:  
Icon does not lose focus on 1st left-click.  Application launches on 2nd
left-click.

Expected Results:  
Icon should lose focus on 1st left-click.  Application should not be launched.

My terminology may be wrong, since I realize there is a distinction between
focus and selection, but it's a distinction I don't have a good grasp of.

Seems similar to Bug 348587.

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

[plasmashell] [Bug 360219] Right Click opens files

[via KDE Bugzilla]

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

kdeb...@toeai.com changed:

   What|Removed |Added

 CC||kdeb...@toeai.com

--- Comment #18 from kdeb...@toeai.com ---
Possibly related:  Today on Manjaro w/ plasma 5.6.5 I had desktop icons in
folder view layout launching with just a single right-click.  No menu displayed
- just instantly launched the application.  I realize this is somewhat
different from the bug reported above, but it's similar and I couldn't
reproduce it after logging out and back in, so I won't file a separate report.

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

[kcharselect] [Bug 242333] bookmarks for character sets

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

   Assignee|lai...@kde.org  |cf...@kde.org

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

[plasmashell] [Bug 365014] All windows hide on repeating desktop click

[Sean V Kelley via KDE Bugzilla]

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

Sean V Kelley  changed:

   What|Removed |Added

 CC||sea...@posteo.de

--- Comment #18 from Sean V Kelley  ---
Same issue for me on Arch:
Qt 5.7.0-1
KDE 5.7.2
Plasma 5.7.2

Sean

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

[plasmashell] [Bug 366064] New: Alternative Shortcut for "Activate Appliction Menu Widget" Is Lost

[Mikiya Okuno via KDE Bugzilla]

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

Bug ID: 366064
   Summary: Alternative Shortcut for "Activate Appliction Menu
Widget" Is Lost
   Product: plasmashell
   Version: 5.7.2
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Application Menu (Kicker)
  Assignee: h...@kde.org
  Reporter: mikiya.ok...@gmail.com
CC: plasma-b...@kde.org

Alternative shortcut for "Activate Appliction Menu Widget" is lost on various
situations, such as log-out and log-in.

Reproducible: Always

Steps to Reproduce:
1. Open system settings -> Shortcuts -> Global Keyboard Shortcuts -> Plasma and
set alternative global for "Activate Appliction Menu Widget".
2. Log out Plasma session, then login again.
3. See the shortcut is lost.

Actual Results:  
The shortcut is lost.

Expected Results:  
The shortcut is available.

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

[kwin] [Bug 366063] New: Window switcher does not start with specific key combination

[Mikiya Okuno via KDE Bugzilla]

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

Bug ID: 366063
   Summary: Window switcher does not start with specific key
combination
   Product: kwin
   Version: 5.7.2
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: effects-various
  Assignee: kwin-bugs-n...@kde.org
  Reporter: mikiya.ok...@gmail.com

I change LEFT ALT to LEFT CTRL using Xmodmap. I register CTRL+TAB as "walk
through window". The key combination LEFT CTRL (originally LEFT ALT) + TAB
switches window to the previous one, but it doesn't display window switcher.
Although, RIGHT CTRL + TAb displays window switcher properly.

Reproducible: Always

Steps to Reproduce:
1. Use xmodmap to change LEFT ALT to LEFT CTRL.
2. Register CTRL+TAB as "walk through window".
3. Press LEFT CTRL (originally LEFT ALT) + TAB.

Actual Results:  
Switches window to the previous one, but it doesn't display window switcher.

Expected Results:  
Display window switcher.

shell> cat .Xmodmap
clear lock
clear control
clear mod1

keycode 64 = Control_L NoSymbol Control_L
keycode  66 = Control_L NoSymbol Control_L

add mod1 = Alt_L Meta_L
add control = Control_L Control_R

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

[kdenlive] [Bug 365445] Improve timeline track controllers

[farid via KDE Bugzilla]

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

farid  changed:

   What|Removed |Added

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

--- Comment #10 from farid  ---
thanks jb.

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

[kdenlive] [Bug 366026] [git] crash when deleting track

[farid via KDE Bugzilla]

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

farid  changed:

   What|Removed |Added

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

--- Comment #4 from farid  ---
i just built a version and it seems fixed. probably something commited in the
hours since i reported the bug. 

cheers

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

[plasmashell] [Bug 366062] New: Icons for Electron apps are too large in the System Tray

[via KDE Bugzilla]

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

Bug ID: 366062
   Summary: Icons for Electron apps are too large in the System
Tray
   Product: plasmashell
   Version: 5.7.2
  Platform: Other
   URL: https://github.com/MarshallOfSound/Google-Play-Music-D
esktop-Player-UNOFFICIAL-/issues/1350#issuecomment-234
810164
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: tha...@gmail.com

For most Electron apps, their icons in the System Tray are oversized, resulting
in them being unrecognizable colourful squares. The provided URL shows one
example of this issue, in which two other examples are also linked to.

Reproducible: Always

Steps to Reproduce:
1. Install an Electron app in KDE Plasma 5
2. Observe its oversized System Tray icon

Actual Results:  
System Tray icon for Electron app is too large.

Expected Results:  
System tray icon for Electron app is standard size.

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

[kdenlive] [Bug 366026] [git] crash when deleting track

[Steve via KDE Bugzilla]

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

Steve  changed:

   What|Removed |Added

 CC||ste...@humanint.com

--- Comment #3 from Steve  ---
It crashed for me also when editing. I tried deleting the top video of 3
tracks. I'm rendering now, but will try an empty new project to see what
happens. I believe I had it muted and disabled video. Lock was not set.

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

[plasmashell] [Bug 366022] KDE KickOff Application Launcher crashes when typing to search for applications

[Frabcisco Cribari via KDE Bugzilla]

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

Frabcisco Cribari  changed:

   What|Removed |Added

 Status|RESOLVED|VERIFIED

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

[kmymoney4] [Bug 345655] Rounding problems between checking and investment account

[Jack via KDE Bugzilla]

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

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #40 from Jack  ---
This has actually been instructive for me - that reconciliation error I have
seen has always been in investment accounts, and I certainly have increased
precision in many of the equities.  Now I'll have to watch for it to happen
again, and see if I actually do have similar rounding problems that have simply
never been large enough to be obvious in any of the visible transaction
amounts.

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

[kdenlive] [Bug 366061] Request for feature : Drop shadow

[stiven guillaume via KDE Bugzilla]

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

stiven guillaume  changed:

   What|Removed |Added

Summary|Request for feature |Request for feature : Drop
   ||shadow

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

[kdenlive] [Bug 366061] New: Request for feature

[stiven guillaume via KDE Bugzilla]

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

Bug ID: 366061
   Summary: Request for feature
   Product: kdenlive
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: stiven.guilla...@gmail.com

Hello,
I'm using Kdenlive to make sciences videos, and i think an effect to generate
drop shadow should be a great innovation.
For the moment, i modifiy all my picture on gimp. Long, long and long job :)
Thank you very much.

Reproducible: Couldn't Reproduce

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

[digikam] [Bug 365262] GUI Theme Colors hard to see: always use Fusion widget style under OSX and Windows

[via KDE Bugzilla]

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

--- Comment #6 from caulier.gil...@gmail.com ---
Git commit b3d2ac7c1b24dd3f54f12d328addfabf1f0a8dc4 by Gilles Caulier.
Committed on 24/07/2016 at 22:51.
Pushed by cgilles into branch 'master'.

Fix foreground text color to be more readable in digiKam corlor scheme with
Fusion widgets style under OSX and Windows
Do not populate color schemes from desktop where we will not have any control
of readability.
Related: bug 365411
FIXED-IN: 5.1.0

M  +1-1data/colorschemes/graycard.colors
M  +1-1data/colorschemes/sunsetcolor.colors
M  +0-6libs/widgets/mainview/thememanager.cpp

http://commits.kde.org/digikam/b3d2ac7c1b24dd3f54f12d328addfabf1f0a8dc4

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

[digikam] [Bug 365411] Tooltips unreadable

[via KDE Bugzilla]

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

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

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||5.1.0
  Latest Commit||http://commits.kde.org/digi
   ||kam/b3d2ac7c1b24dd3f54f12d3
   ||28addfabf1f0a8dc4
 Status|UNCONFIRMED |RESOLVED

--- Comment #4 from caulier.gil...@gmail.com ---
Git commit b3d2ac7c1b24dd3f54f12d328addfabf1f0a8dc4 by Gilles Caulier.
Committed on 24/07/2016 at 22:51.
Pushed by cgilles into branch 'master'.

Fix foreground text color to be more readable in digiKam corlor scheme with
Fusion widgets style under OSX and Windows
Do not populate color schemes from desktop where we will not have any control
of readability.
Related: bug 365262
FIXED-IN: 5.1.0

M  +1-1data/colorschemes/graycard.colors
M  +1-1data/colorschemes/sunsetcolor.colors
M  +0-6libs/widgets/mainview/thememanager.cpp

http://commits.kde.org/digikam/b3d2ac7c1b24dd3f54f12d328addfabf1f0a8dc4

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

[clazy] [Bug 365940] Warn when using non-owning smart pointers as associative container key

[Sergio Martins via KDE Bugzilla]

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

Sergio Martins  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
  Latest Commit||http://commits.kde.org/claz
   ||y/82804b42907232c3c163028b5
   ||d42fe61b29cf5e9
 Resolution|--- |FIXED

--- Comment #1 from Sergio Martins  ---
Git commit 82804b42907232c3c163028b5d42fe61b29cf5e9 by Sergio Martins.
Committed on 24/07/2016 at 22:52.
Pushed by smartins into branch 'master'.

new check: mutable-container-key

Looks for associative containers that have a key which value can
change. QPointer or QWeakPointer are examples of such types

M  +1-0CMakeLists.txt
A  +5-0checks/level0/README-mutable-container-key.md
A  +72   -0checks/level0/mutable-container-key.cpp [License: LGPL
(v2+)]
A  +39   -0checks/level0/mutable-container-key.h [License: LGPL (v2+)]
M  +11   -11   tests/clazy/test_requested_checks.sh.expected
A  +7-0tests/mutable-container-key/config.json
A  +26   -0tests/mutable-container-key/main.cpp [License: UNKNOWN]  *
A  +5-0tests/mutable-container-key/main.cpp.expected

The files marked with a * at the end have a non valid license. Please read:
http://techbase.kde.org/Policies/Licensing_Policy and use the headers which are
listed at that page.


http://commits.kde.org/clazy/82804b42907232c3c163028b5d42fe61b29cf5e9

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

[plasmashell] [Bug 366060] New: CPU 100% while moving files.

[Govannon via KDE Bugzilla]

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

Bug ID: 366060
   Summary: CPU 100% while moving files.
   Product: plasmashell
   Version: 5.6.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: wizard7...@gwi.net
CC: bhus...@gmail.com, plasma-b...@kde.org

Whenever I try to move files, the CPU goes to 100% for about 5 minutes.

Reproducible: Always

Steps to Reproduce:
1.Move files within Dolphin to either another folder or to the trash.
2.
3.

Actual Results:  
CPU 100% for about five minutes.

Expected Results:  
Should move the files without trouble for a short amount of time.

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

[krita] [Bug 366001] [Cintiq] Krita crashes on second brush stroke on a newly opened document.

[andyvandalsem via KDE Bugzilla]

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

--- Comment #3 from andyvandalsem  ---
Hi Boudewijn. Thanks for the update. This was happening on my work machine so
I'll check it out on Monday when I'm back in the office. I know a bug report
probably isn't the right place for this but I just wanted to say I think you
guys are doing great work on Krita. I'm a really big fan. :)

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

[gwenview] [Bug 350632] Crashed while rotating the image

[Yasin Zähringer via KDE Bugzilla]

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

--- Comment #12 from Yasin Zähringer  ---
Created attachment 100278
  --> https://bugs.kde.org/attachment.cgi?id=100278=edit
test photo

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

[gwenview] [Bug 343796] Most of operations are disabled when opening files from remote url.

[mva]

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

--- Comment #3 from Vadim A. Misbakh-Soloviov (mva)  ---
NB: `urlKind(currentUrl())` (which `currentUrlIsRasterImage()` calls to detect
return value) returns 8 every time for remote links, whether it jpg or png or
whatever. While KIND_RASTER_IMAGE (another argument to check against) returns
16.
That's why all of that functions become inactive.

So, I have two notes for developers:

1) why do you disable that actions (including "save as") for non-raster images
at all (even if we forgot about that broken thing)? Why can't we "save as"
opened svg/eps/whatever file?

2) MimeTypeUtils->mimeTypeKind (lib/mimetypeutils.cpp line 130) gets
"application/octet-stream" as an argument (although, that is pretty strange,
since at least few servers I checked returns image/* content-type headers), and
after all checks it returns it's "default" value (KIND_FILE). So, that's why
`contextManager->currentUrlIsRasterImage` (lib/contextmanager.cpp line 263)
returns false.

So, as proper fix I'd suggest to:
1) get rid of all that mime checks for at least "save as" and related actions.
2) debug MimeUtils why the hell it gets octet-stream, and not the real mimetype
(to keep intended behaviour for rotating/etc actions for raster images only,
although, I personally would like ability to rotate vector images too :D).

For users:
As temporary solution, I'd suggest you to apply that patch (with patch -p1):
===  cut  ===
--- a/lib/contextmanager.cpp2016-07-25 03:59:24.704428867 +0700
+++ b/lib/contextmanager.cpp2016-07-25 03:59:02.582209995 +0700
@@ -263,7 +263,7 @@

 bool ContextManager::currentUrlIsRasterImage() const
 {
-return MimeTypeUtils::urlKind(currentUrl()) ==
MimeTypeUtils::KIND_RASTER_IMAGE;
+return MimeTypeUtils::urlKind(currentUrl()) !=
MimeTypeUtils::KIND_UNKNOWN;
 }

 QUrl ContextManager::urlToSelect() const
 /cut ===

(in Gentoo — just put it in /etc/portage/patches/kde-apps/gwenview/ with any
name and ".patch" suffix)

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

[kmymoney4] [Bug 366043] KMyMoney crashes along with KNotify when searching for transactions

[Rob V via KDE Bugzilla]

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

--- Comment #2 from Rob V  ---
Didn't even notice Fedora had switched the widget theme. I switched back to
Oxygen and can confirm that exactly the same occurs. Specifically, KNotify
crashes a second or two after clicking Tools > Consistency Check. The
consistency check windows then works absolutely fine. The KMyMoney crash
then occurs by clicking Edit > Find Transaction > Date tab. I initially
thought it crashed at random after switching to that tab, but have now
narrowed it down to opening the datepicker widget and clicking the year.
Sometimes just clicking to enter a year causes a crash, other times it is
after pressing enter to navigate to that year.

rvalk...@gmail.com

On 24 July 2016 at 22:00, Thomas Baumgart via KDE Bugzilla <
bugzilla_nore...@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=366043
>
> --- Comment #1 from Thomas Baumgart  ---
> The backtrace does not show any reference to KMyMoney specific code
> (except the
> first routine in frame #39). Does the problem also show if you use the
> Oxygen
> theme?
>
> --
> You are receiving this mail because:
> You reported the bug.
>

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

[rsibreak] [Bug 365599] high cpu usage of plasmashell when rsibreak is running

[Albert Astals Cid via KDE Bugzilla]

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

--- Comment #9 from Albert Astals Cid  ---
Sorry but i do not really understand your messages, it seems to me you're
saying one thing and then in the next sentence a different thing.

Could you attach the rsibreakrc that makes you have high cpu usage to see if i
can reproduce it?

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

[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM

[via KDE Bugzilla]

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

dwtebr...@gmail.com changed:

   What|Removed |Added

 CC||dwtebr...@gmail.com

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

[plasmashell] [Bug 344706] KMenu won't show sometimes (multi-monitor setup)

[via KDE Bugzilla]

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

dwtebr...@gmail.com changed:

   What|Removed |Added

 CC||dwtebr...@gmail.com

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

[plasmashell] [Bug 356937] Xembed icons have black background

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

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

--- Comment #15 from Viorel-Cătălin Răpițeanu  ---
I haven't seen this issue anymore.
I believe that this can be closed as resolved.

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

[kdenlive] [Bug 366059] New: Audio-only (wav) exports extremely slow with GPU / Movit / GLSL enabled

[Peter via KDE Bugzilla]

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

Bug ID: 366059
   Summary: Audio-only (wav) exports extremely slow with GPU /
Movit / GLSL enabled
   Product: kdenlive
   Version: 16.04.0
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: pe...@corrosivetruths.org

Audio-only (wav) exports / renders are extremely slow when GPU acceleration /
movit / glsl are enabled, as soon as you turn them off the render speed of
audio-only jumps up considerably.

A good way to prove this is to take a short video, generate a script for an
audio only export, run the script, take the glsl.=1out of the script and re-run
it. Note the change in running speed. The problem is also evident if you simply
render a wave from inside kdenlive, and then do the same thing after disabliing
gpu rendering.

Feels like melt is rendering the whole frame and then discarding the video
rather than ignoring the video because its audio-only.

This also happened when I use flac audio-only (video_off=1 f=flac acodec=flac
vn=1) - despite the explicit video_off and vn settings, the slowness was still
apparent, once again as soon as I removed glsl.=1 from the generated script.

The bug exists both in 16.04 and the latest git version.

Reproducible: Always

Steps to Reproduce:
1. Drag a movie clip into a fresh project with movit enabled
2. Generate an audio-only (wav) script
3. Run the script

Actual Results:  
Very slow rendering, almost real-time.

Expected Results:  
Speedy audio-only render, much much faster than real-time.

Removing glsl.=1 from the generated script makes it run a gazillion times
faster.

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

[akregator] [Bug 366058] New: Lost ability to filter by unread or new messages

[David Hart via KDE Bugzilla]

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

Bug ID: 366058
   Summary: Lost ability to filter by unread or new messages
   Product: akregator
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: dc.h...@slowlyboiledfrog.com

Fedora 24
Akregator=5.2.3

Up until this version there was a selector that enabled you to filter by
unread, all and new messages. It was really very useful. I cannot find any way
to replicate this behavior.

Thanks - Akregator does a great job. I have hundreds of feeds and it is the
prime source of my popular blog.

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

[plasmashell] [Bug 365570] Systray icons are big and pixelated after update to 5.7.1

[Mike Goodwin via KDE Bugzilla]

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

--- Comment #15 from Mike Goodwin  ---
@cher...@aip.de 

If you're using Fedora, I persuaded rdeiter to patch it at the package level.
In which case, you won't see it in Fedora.

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

[digikam] [Bug 366036] Sidecar file is not written when image is symlink to write-protected directory

[Simon via KDE Bugzilla]

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

--- Comment #9 from Simon  ---
Maik: So what is the behaviour after your commit: Does digikam handle 
symlinked images like unique images (so unique database entry, e.g. 
tags) or just as pointers to the real image (so all symlinks pointing to 
the same file have the same database information)? Thanks for clarification.


On 24/07/16 22:05, Maik Qualmann via KDE Bugzilla wrote:
> https://bugs.kde.org/show_bug.cgi?id=366036
>
> --- Comment #8 from Maik Qualmann  ---
> Also Darktable created not a sidecar file and prints a exiv2 exception.
>
> Maik
>

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

[kmymoney4] [Bug 366043] KMyMoney crashes along with KNotify when searching for transactions

[Thomas Baumgart via KDE Bugzilla]

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

--- Comment #1 from Thomas Baumgart  ---
The backtrace does not show any reference to KMyMoney specific code (except the
first routine in frame #39). Does the problem also show if you use the Oxygen
theme?

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

[plasmashell] [Bug 366057] creation/modification of .desktop application links is broken

[via KDE Bugzilla]

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

--- Comment #1 from kdeb...@toeai.com ---
Created attachment 100276
  --> https://bugs.kde.org/attachment.cgi?id=100276=edit
screenshot of error message

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

[plasmashell] [Bug 366057] New: creation/modification of .desktop application links is broken

[via KDE Bugzilla]

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

Bug ID: 366057
   Summary: creation/modification of .desktop application links is
broken
   Product: plasmashell
   Version: 5.6.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: kdeb...@toeai.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Observed on current Manjaro - multiple computers.  There are various problems
even beyond what I describe, but until the basics are fixed, it's not worth
describing.  Apologies if I've selected the wrong component - I'm not sure how
all these things work together.

Reproducible: Always

Steps to Reproduce:
0. Delete ~/.local/share/applications directory as if you'd started with a new
profile.  Close and re-open dolphin just to be sure.
1. Right-click in a folder and click Create New -> Link to Application...
2. Press OK.  File is created: "Link to Application.desktop"
3. Right-click file and select Properties.
4. Click blank icon and select an icon, e.g. the smiley face.  Click OK.

Actual Results:  
Get message box popup: "Sorry -- Dolphin" : "Could not save properties.  You do
not have sufficient access to write to /home/[user
name]/.local/share/applications/p."

At this time there is no .local/share/applications directory.  After you press
OK, it will be created, along with a file named simply "p", the contents of
which are:
[Desktop Entry]
Icon=face-smile


Expected Results:  
I don't know the rationale behind the .local/share/applications directory, so I
don't know what to expect, but it does seem rather worthless to create that 'p'
file, and doesn't make sense why, if you go on to change the .desktop file you
originally made (try changing the icon again), it creates an additional more
detailed "n.desktop" file.  It seems like any file that does end up in there,
for whatever reason, should have the .desktop extension and that one file in
there for each file out of there should be more than plenty, and that the icon
I select should show up on the .desktop file I created (it doesn't), not just
on some "p" or "n.desktop" file in a hidden settings directory.   If you open
"Link to Application.desktop" in kate it still says Icon=exec.  You can modify
that manually, and it will work.  Deleted the silly .local/share/applications
directory and things work just fine, as long as you don't mind manually
creating .desktop files.

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

[kmymoney4] [Bug 345655] Rounding problems between checking and investment account

[Thomas Baumgart via KDE Bugzilla]

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

--- Comment #39 from Thomas Baumgart  ---
OK, so editing transactions solves the problem on a per-transaction basis
(which was implemented by the fix). In order to resolve the problem with the
red background for the online balance you need to edit all transaction with a
denominator > 100  (seems you have some of those according to the list you
provided) and not only the one with 62500 which I picked randomly from your
list..

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

[drkonqi] [Bug 366056] New: drqonki chrashing after attempting to send a bug

[Stanislav N via KDE Bugzilla]

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

Bug ID: 366056
   Summary: drqonki chrashing after attempting to send a bug
   Product: drkonqi
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: stanis...@nevolin.info

I tried to send a bug about kwin crashing, but drkonqi crashed itself.

Reproducible: Didn't try




Application: drkonqi (drkonqi), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb822a3e940 (LWP 9216))]

Thread 3 (Thread 0x7fb7fe648700 (LWP 9257)):
#0  0x7fb81f3ffd50 in timerSourcePrepareHelper(GTimerSource*, int*) () at
/lib64/libQt5Core.so.5
#1  0x7fb81f3ffe75 in timerSourcePrepare(_GSource*, int*) () at
/lib64/libQt5Core.so.5
#2  0x7fb81be12f7d in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#3  0x7fb81be1396b in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#4  0x7fb81be13b5c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#5  0x7fb81f40024b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#6  0x7fb81f3af5ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#7  0x7fb81f20e343 in QThread::exec() () at /lib64/libQt5Core.so.5
#8  0x7fb822b10559 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#9  0x7fb81f21299a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#10 0x7fb81cac75ca in start_thread () at /lib64/libpthread.so.0
#11 0x7fb81e605ead in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fb805f62700 (LWP 9234)):
#0  0x7fb81e5fa32d in poll () at /lib64/libc.so.6
#1  0x7fb818a78f80 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7fb818a7ab79 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7fb809b22da9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7fb81f21299a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7fb81cac75ca in start_thread () at /lib64/libpthread.so.0
#6  0x7fb81e605ead in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fb822a3e940 (LWP 9216)):
[KCrash Handler]
#6  0x7fb8213ebf54 in KNotification::flags() const () at
/lib64/libKF5Notifications.so.5
#7  0x7fb82140b797 in NotifyByAudio::onAudioFinished() () at
/lib64/libKF5Notifications.so.5
#8  0x7fb821410e45 in NotifyByAudio::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () at /lib64/libKF5Notifications.so.5
#9  0x7fb81f3d8b92 in QMetaObject::activate(QObject*, int, int, void**) ()
at /lib64/libQt5Core.so.5
#10 0x7fb81cd255d5 in Phonon::MediaObject::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () at /lib64/libphonon4qt5.so.4
#11 0x7fb81f3d9bd9 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5
#12 0x7fb81fc43c0c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#13 0x7fb81fc490ef in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQt5Widgets.so.5
#14 0x7fb81f3b07aa in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#15 0x7fb81f3b284f in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /lib64/libQt5Core.so.5
#16 0x7fb81f4001b3 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () at /lib64/libQt5Core.so.5
#17 0x7fb81be13703 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#18 0x7fb81be13ab0 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#19 0x7fb81be13b5c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#20 0x7fb81f40022f in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#21 0x7fb81f3af5ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#22 0x7fb81fe49380 in QDialog::exec() () at /lib64/libQt5Widgets.so.5
#23 0x7fb8218fbcdb in KMessageBox::createKMessageBox(QDialog*,
QDialogButtonBox*, QIcon const&, QString const&, QStringList const&, QString
const&, bool*, QFlags, QString const&, QMessageBox::Icon)
() at /lib64/libKF5WidgetsAddons.so.5
#24 0x7fb8218fc826 in KMessageBox::createKMessageBox(QDialog*,
QDialogButtonBox*, QMessageBox::Icon, QString const&, QStringList const&,
QString const&, bool*, QFlags, QString const&) () at
/lib64/libKF5WidgetsAddons.so.5
#25 0x7fb8218fd5aa in KMessageBox::questionYesNoCancelInternal(QDialog*,
QString const&, QString const&, KGuiItem const&, KGuiItem const&, KGuiItem
const&, QString const&, QFlags) () at
/lib64/libKF5WidgetsAddons.so.5
#26 0x55a079971662 in ReportAssistantDialog::closeEvent(QCloseEvent*) ()
#27 0x7fb81fc89940 in QWidget::event(QEvent*) () at
/lib64/libQt5Widgets.so.5
#28 0x7fb81fc43c0c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at 

[korganizer] [Bug 366055] kOrganizer 5.1.3: Incidents inviting "myself" are invisible

[Gunter Ohrner via KDE Bugzilla]

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

--- Comment #1 from Gunter Ohrner  ---
Addendum: This can easily cause you to lose track of incidents / appointments
you created yourself... And that might be anything from embarrassing to
annoying or worse...

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

[korganizer] [Bug 366055] New: kOrganizer 5.1.3: Incidents inviting "myself" are invisible

[Gunter Ohrner via KDE Bugzilla]

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

Bug ID: 366055
   Summary: kOrganizer 5.1.3: Incidents inviting "myself" are
invisible
   Product: korganizer
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: monthview
  Assignee: korganizer-de...@kde.org
  Reporter: kdeb...@customcdrom.de

I encountered this problem with a kMail identity with alias addresses.

In my concrete case, a distribution / mailing list address was defined as an
alias address for my personal address in kMail settings -> identities -> Edit
-> eMail aliases.

I entered a new incident and invited this distribution list (in this case
a...@example.com) and confirmed the editor.

The invitations were sent correctly, but the indicent was not visible in my own
(!) calendar. I always use the month view, but I don't expect it's specific to
this.

Only after removing the mail alias from my mail identity - which caused
kOrganizer to crash, btw. - the incident automagically appeared in the month
view.

Reproducible: Always

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

[krita] [Bug 366028] Krita will not recognize pen pressure from my wacom intuos tablet.

[via KDE Bugzilla]

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

--- Comment #2 from imdahlstr...@gmail.com ---
I forgot to mention all other programs have pressure sensitivity, and it
works fine there (autodesk sketchbook, artrage lite). I will try to
reinstall my tablet drivers later.

On Sun, Jul 24, 2016 at 6:01 AM, wolthera via KDE Bugzilla <
bugzilla_nore...@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=366028
>
> wolthera  changed:
>
>What|Removed |Added
>
> 
>  Resolution|--- |WAITINGFORINFO
>  Status|UNCONFIRMED |NEEDSINFO
>  CC||griffinval...@gmail.com
>
> --- Comment #1 from wolthera  ---
> Hi, we don't know why this happens.
>
> On windows 10, we do know that sometimes windows 10 garbles your tablet
> drivers
> during updates. So if you could check if 1) other programs do have pressure
> sensitvity and 2) reinstalling the tablet driver does anything, then we
> can say
> if this is a Krita issue or not.
>
> If the above check out, can you make a tablet log for us?
>
> https://docs.krita.org/KritaFAQ#What_if_your_tablet_is_not_recognized_by_Krita.3F
>
> --
> You are receiving this mail because:
> You reported the bug.
>

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

[kmail2] [Bug 359425] CSS from HTML mail interfers with header layout

[Dominik George via KDE Bugzilla]

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

--- Comment #5 from Dominik George  ---
Created attachment 100274
  --> https://bugs.kde.org/attachment.cgi?id=100274=edit
Legitimate mail breaking KMail UI

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

[kmail2] [Bug 359425] CSS from HTML mail interfers with header layout

[Dominik George via KDE Bugzilla]

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

--- Comment #4 from Dominik George  ---
Created attachment 100273
  --> https://bugs.kde.org/attachment.cgi?id=100273=edit
Broken KMail with legitimate mail

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

[kmail2] [Bug 359425] CSS from HTML mail interfers with header layout

[Dominik George via KDE Bugzilla]

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

--- Comment #3 from Dominik George  ---
Today, I found that the bug persists in KMail 5.2.3 (I cannot select that in
the version field above…) and it got worse.

Today, I stumbled over a legitimate HTML mail messing up the whole UI.

Find attached the mail that caused it and a screenshot/

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

[kmail2] [Bug 359425] CSS from HTML mail interfers with header layout

[Dominik George via KDE Bugzilla]

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

Dominik George  changed:

   What|Removed |Added

Version|4.14.10 |unspecified
 CC||n...@naturalnet.de
   Severity|normal  |grave

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

[plasmashell] [Bug 366054] New: plasma crashed after rapid clicks on system tray icons

[Aram via KDE Bugzilla]

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

Bug ID: 366054
   Summary: plasma crashed after rapid clicks on system tray icons
   Product: plasmashell
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: aramgrigor...@protonmail.ch
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

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

-- Information about the crash:
clicked on device notifier icon in the system tray when no storage device was
pluged. then rapidly clicked on bluetooth icon several times and it didnt open
the etry for bluetooth and crashed.

The crash can be reproduced sometimes.

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

Thread 15 (Thread 0x7f0aee72f700 (LWP 1866)):
#0  0x7f0afe1d0bfd in poll () at /lib64/libc.so.6
#1  0x7f0b03124422 in  () at /usr/lib64/libxcb.so.1
#2  0x7f0b0312600f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f0af08803c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f0afe8cb32f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f0afd9da0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f0afe1d902d in clone () at /lib64/libc.so.6

Thread 14 (Thread 0x7f0ae79d1700 (LWP 1873)):
#0  0x7f0afeafdc9a in  () at /usr/lib64/libQt5Core.so.5
#1  0x7f0afa8ad4ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f0afa8add80 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f0afa8adf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f0afeafdd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f0afeaa4d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f0afe8c661a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f0b01bdae18 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7f0afe8cb32f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f0afd9da0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f0afe1d902d in clone () at /lib64/libc.so.6

Thread 13 (Thread 0x7f0ada527700 (LWP 1904)):
#0  0x7f0afe1d in read () at /lib64/libc.so.6
#1  0x7f0afa8eeb60 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f0afa8ad999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f0afa8addf8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f0afa8adf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f0afeafdd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f0afeaa4d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f0afe8c661a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f0b01bdae18 in  () at /usr/lib64/libQt5Qml.so.5
#9  0x7f0afe8cb32f in  () at /usr/lib64/libQt5Core.so.5
#10 0x7f0afd9da0a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7f0afe1d902d in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7f0ad8ca3700 (LWP 1905)):
#0  0x7f0afe1d in read () at /lib64/libc.so.6
#1  0x7f0afa8eeb60 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f0afa8ad999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f0afa8addf8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f0afa8adf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f0afeafdd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f0afeaa4d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f0afe8c661a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f0b01bdae18 in  () at /usr/lib64/libQt5Qml.so.5
#9  0x7f0afe8cb32f in  () at /usr/lib64/libQt5Core.so.5
#10 0x7f0afd9da0a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7f0afe1d902d in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7f0ad31cf700 (LWP 1906)):
#0  0x7f0afd9de03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f0b043a986b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f0b043a9899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f0afd9da0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f0afe1d902d in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7f0a4bfff700 (LWP 1907)):
#0  0x7f0afa8efd14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f0afa8ade0e in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f0afa8adf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f0afeafdd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at 

[digikam] [Bug 366036] Sidecar file is not written when image is symlink to write-protected directory

[Maik Qualmann via KDE Bugzilla]

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

--- Comment #8 from Maik Qualmann  ---
Also Darktable created not a sidecar file and prints a exiv2 exception.

Maik

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

[digikam] [Bug 366036] Sidecar file is not written when image is symlink to write-protected directory

[Maik Qualmann via KDE Bugzilla]

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

--- Comment #7 from Maik Qualmann  ---
In digiKam4.x was the writing from metadata about symlinks incorrectly. The
real image path was not resolved correctly. Therefore, the change in digiKam5.

Maik

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

[frameworks-ki18n] [Bug 365917] ki18n fails to link on musl libc due to _nl_msg_cat_cntr

[Chusslove Illich via KDE Bugzilla]

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

Chusslove Illich  changed:

   What|Removed |Added

 CC||caslav.i...@gmx.net,
   ||fa...@kde.org

--- Comment #2 from Chusslove Illich  ---
The patch seems fine to me, but this is also the question of which conventions
we follow for this type of configuration in CMake, and that I'm not so sure
about. So for the moment I'll just add someone who knows better, or knows who
knows better, to CC.

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

[kdenlive] [Bug 366026] [git] crash when deleting track

[farid via KDE Bugzilla]

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

--- Comment #2 from farid  ---
it crashes every time i delete a track. i don't even create a project or import
a file... just deleting a track crashes it.

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

[digikam] [Bug 366036] Sidecar file is not written when image is symlink to write-protected directory

[Maik Qualmann via KDE Bugzilla]

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

--- Comment #6 from Maik Qualmann  ---
I now see the Comment 4. But the behavior of digiKam4.x was a mistake. DigiKam
requires the sidecar in the same folder as the original image.

Maik

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

[gwenview] [Bug 343796] Most of operations are disabled when opening files from remote url.

[mva]

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

--- Comment #2 from Vadim A. Misbakh-Soloviov (mva)  ---
NB: it seems, it is a `contextManager()->currentUrlIsRasterImage();` fault:
if I change call to it (in app/imegaopscontextmanager.cpp) to just "true", then
all the actions becomes active.

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

[digikam] [Bug 366036] Sidecar file is not written when image is symlink to write-protected directory

[Maik Qualmann via KDE Bugzilla]

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

Maik Qualmann  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||5.1.0
  Latest Commit||http://commits.kde.org/digi
   ||kam/19446b5d9a7bb63164232df
   ||e9db3135b629337b7

--- Comment #5 from Maik Qualmann  ---
Git commit 19446b5d9a7bb63164232dfe9db3135b629337b7 by Maik Qualmann.
Committed on 24/07/2016 at 19:32.
Pushed by mqualmann into branch 'master'.

write sidecar file in the same folder as image also over symlink
FIXED-IN: 5.1.0

M  +4-4libs/dmetadata/metaengine.cpp
M  +1-1libs/dmetadata/metaengine_p.cpp

http://commits.kde.org/digikam/19446b5d9a7bb63164232dfe9db3135b629337b7

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

[kdenlive] [Bug 358484] movit library brightens rendered video

[Peter via KDE Bugzilla]

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

--- Comment #2 from Peter  ---
This hasn't been an issue for some time.

Please close this.

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

[digikam] [Bug 366036] Sidecar file is not written when image is symlink to write-protected directory

[Thomas Reifenberger via KDE Bugzilla]

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

--- Comment #4 from Thomas Reifenberger  ---
> Regarding the behaviour: Digikam does treat symlinks like "real files", 
> e.g. every symlink has its own set of tags in the database.
This is the behavior I would consider correct. Being able to use symlinks that
are treated as normal files is an essential part of my workflow (tm):

I use git with git-annex to manage my photos. The raw files are added via
git-annex (and therefore replaced by symlinks to read-only files in read-only
directories), while the sidecar files remain normal files managed by pure git.
The raw files are never supposed to be changed anymore, while the metadata is
kept under version control independent of a single tool (I use darktable for
raw processing and digikam for almost everything else)

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

[plasmashell] [Bug 366053] New: Let me rearrange launchers on the task manager panel

[Chris via KDE Bugzilla]

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

Bug ID: 366053
   Summary: Let me rearrange launchers on the task manager panel
   Product: plasmashell
   Version: master
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: emailofch...@gmail.com
CC: plasma-b...@kde.org

I can't tell what sorting method is used for the launchers on the panel, and I
see no option to change it. It would be nice if I could choose the order
myself, as you can on the Windows taskbar or on the OS X dock.

Reproducible: Always

Steps to Reproduce:
1. Unlock widgets?
2. Try to click and drag a launcher to a different spot within the group of
launchers.

Actual Results:  
Nothing happens.

Expected Results:  
I should be able to swap their positions and/or move one between two others.

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

[systemsettings] [Bug 353825] Login by x2go in Plasma 5 crashes KCMInit

[Richard Homonnai via KDE Bugzilla]

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

Richard Homonnai  changed:

   What|Removed |Added

 CC||ch...@rpgfiction.net

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

[dolphin] [Bug 366052] New: Please provide a function "Add current location as a Favorite", and add a shortcut to it

[Narayan via KDE Bugzilla]

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

Bug ID: 366052
   Summary: Please provide a function "Add current location as a
Favorite", and add a shortcut to it
   Product: dolphin
   Version: 4.14.2
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: split view
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: raindrops.from...@gmail.com

Currently, the user can add a new entry to Places (Favorite).
But this dialog is not "aware" of the current location loaded in the active
pane+tab. Thus the user has to copy the complete URI from the active pane, and
then paste it in the Places dialog.  This is too tedious.

Desired:
The "Add entry" dialog should automatically load the current location that is
loaded in the active pane+tab. 

Further, it should be possible to set a shortcut to load this favorite in the
active pane+tab.

Reproducible: Always

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

[dolphin] [Bug 366051] New: Allow user to allocate a keyboard shortcut to Actions

[Narayan via KDE Bugzilla]

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

Bug ID: 366051
   Summary: Allow user to allocate a keyboard shortcut to Actions
   Product: dolphin
   Version: 4.14.2
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: split view
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: raindrops.from...@gmail.com

At present, we cannot set shortcuts for Actions. 

For example, I would like to do bulk renaming of the selected items with
KRename. 
This action is already available in the context menu.but it cannot be assigned
a shortcut.

Please provide this facility.

Reproducible: Always

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

[digikam] [Bug 366036] Sidecar file is not written when image is symlink to write-protected directory

[via KDE Bugzilla]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com

--- Comment #2 from caulier.gil...@gmail.com ---
The sidecar must be paced at the same dir than image. It's the logic current
used (and always used in digiKam through Exiv2.)

Note : currently, the full qualied name of image file is used, including the
file extension.
example : foo.nef will have foo.nef.xmp, which will be suitable with the same
file name and other extension as jpeg (foo.jpg.xmp). There is an entry in
bugzilla to be able to customized that, but it's not yet implemented.

Gilles Caulier

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

[digikam] [Bug 366036] Sidecar file is not written when image is symlink to write-protected directory

[Simon via KDE Bugzilla]

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

--- Comment #3 from Simon  ---
Regarding the behaviour: Digikam does treat symlinks like "real files", 
e.g. every symlink has its own set of tags in the database. In my 
opinion it would make more sense to treat them as links internally too. 
So any operation on the link in the database is actually done on the 
original (operations on the image itself are anyway always on the original).


On 24/07/16 20:44, Maik Qualmann via KDE Bugzilla wrote:
> https://bugs.kde.org/show_bug.cgi?id=366036
>
> Maik Qualmann  changed:
>
> What|Removed |Added
> 
>   CC||metzping...@gmail.com
>
> --- Comment #1 from Maik Qualmann  ---
> I think the sidecar should be stored in the image folder. In this case, the
> "subdir" folder. And the "subdir" must be writable. I think the behavior of
> digikam4.x was wrong. Gilles, what do you think?
>
> Maik
>

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

[kwin] [Bug 347946] Task Manager tooltip reveal/move animations flickering and showing redraw artifacts when happening alongside window highlight effect

[Oswald Buddenhagen via KDE Bugzilla]

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

Oswald Buddenhagen  changed:

   What|Removed |Added

 CC||o...@kde.org

--- Comment #4 from Oswald Buddenhagen  ---
i have no problem with the tooltip, but the described behavior applies to the
popup menu for choosing among grouped windows.

and the guess about the blur effect seems to be spot-on.

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

[plasmashell] [Bug 341934] Highlight windows option hides tooltip

[Oswald Buddenhagen via KDE Bugzilla]

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

Oswald Buddenhagen  changed:

   What|Removed |Added

 CC||o...@kde.org

--- Comment #24 from Oswald Buddenhagen  ---
it appears that the popup menu for choosing among grouped windows suffers from
the same problem (kwin 5.7.0, plasma 5.6.5 (debian being funny)).

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

[dolphin] [Bug 366050] New: There is no keyboard shortcut to switch between panes and tabs

[Narayan via KDE Bugzilla]

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

Bug ID: 366050
   Summary: There is no keyboard shortcut to switch between panes
and tabs
   Product: dolphin
   Version: 4.14.2
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: split view
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: raindrops.from...@gmail.com

There should be separate keyboard shortcutrs to switch between left/right tabs
and between tabs.

Suggested shortcuts:
1. TAB to switch  (toggle) between the left/right panes.
2. CTRL+1, CTRL+2, etc to jump to a particular tab.
3. CTRL+PageUp and CTRL+PageDown to move to the left/right tab.

Reproducible: Always

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

[digikam] [Bug 366036] Sidecar file is not written when image is symlink to write-protected directory

[Maik Qualmann via KDE Bugzilla]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
I think the sidecar should be stored in the image folder. In this case, the
"subdir" folder. And the "subdir" must be writable. I think the behavior of
digikam4.x was wrong. Gilles, what do you think?

Maik

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

[dolphin] [Bug 366049] New: The label of the tabs changes randomly when we switch between left-and-right panes

[Narayan via KDE Bugzilla]

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

Bug ID: 366049
   Summary: The label of the tabs changes randomly when we switch
between left-and-right panes
   Product: dolphin
   Version: 4.14.2
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: split view
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: raindrops.from...@gmail.com

The very purpose of having dual pane is to transfer the folders/files from one
pane to the opposite pane.
And the tabs enable us to load different locations in the panes. 
Typically, the left pane is the source pane and the right pane is the
destination pane. 

This is the logic for loading specific locations in each tab.

But the Dolphin does not follow this logic: 
Each tab has two labels (one for the left pane, the other for the right pane.)

When we switch between the  panes, the URI loaded in the active tab changes.
But the labels in the other tabs do NOT change.

This is extremely confusing.
The solution lies in following one of the following alternate designs:
Option-1: Each pane should have a separate set of tabs. When we change the
width of the pane, the tabs of that pane must re-size to fit within the
available width.

Option-2: Keep the common tabs, but each tab should show the locations for both
panes.
For example, a tab could show "Home| Downloads", which means that if this tab
is selected, it will load the "Home" folder in the left pane and "Downloads"
folder in the right pane. 
(The pipe symbol "|" is used as separator.)

Reproducible: Always

Steps to Reproduce:
1. Launch a few tabs.
2. Select the tab#1. Switch to left pane, and load a folder. Then switch to the
right pane, and load another folder.
2. Select Tab#2. repeat the selection of two different folders in the left and
right panes.
(take care to select a different set compared to tab#1)
3. Repeat for tab#3.
4. Now select any tab, and then select the left/right pane. Watch the text in
the current tab.


Actual Results:  
Each tab remembers the folders that were loaded in the left and right panes.
But the user does not remember these bewildering combinations.


Expected Results:  
Each tab should display a dual folder locations (for the left and right panes).
OR make a separate set of tabs for each pane.

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

[kmymoney4] [Bug 345655] Rounding problems between checking and investment account

[via KDE Bugzilla]

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

--- Comment #38 from sven.kel...@gmail.com ---
fur the purpose of "mocking away the rounding error" I used more digits. I
reversed it for this transaction to the actual values and the rounding seems to
be OK.
The precision of this transaction also changed in the xml to xxx/100 
But it does not change the red bar in the ledger.

ps: there are likely more transactions like this for the same reason, but I
could not find another "62500".

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

[digikam] [Bug 365411] Tooltips unreadable

[via KDE Bugzilla]

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

--- Comment #3 from caulier.gil...@gmail.com ---
Git commit 6f4044ca14169beb9e0c94bc102e0074f09b9224 by Gilles Caulier.
Committed on 24/07/2016 at 18:31.
Pushed by cgilles into branch 'master'.

for Windows and OSX, always use Fusion widgets style to prevent color scheme
problems.
Related: bug 365262
FIXED-IN: 5.1.0

M  +6-0libs/settings/applicationsettings.cpp
M  +2-0libs/settings/applicationsettings_miscs.cpp
M  +1-0libs/settings/applicationsettings_p.cpp
M  +1-0showfoto/main/showfoto.cpp
M  +7-1showfoto/main/showfotosettings.cpp
M  +10   -1showfoto/setup/showfotosetupmisc.cpp
M  +13   -0utilities/setup/setupmisc.cpp

http://commits.kde.org/digikam/6f4044ca14169beb9e0c94bc102e0074f09b9224

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

[plasmashell] [Bug 365569] After update to KF5.24 systemtray is missing its icons (and functionalities)

[via KDE Bugzilla]

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

andreas.sturmlech...@gmail.com changed:

   What|Removed |Added

 CC||andreas.sturmlechner@gmail.
   ||com

--- Comment #15 from andreas.sturmlech...@gmail.com ---
Yes, this should definitely be fixed.

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

[digikam] [Bug 365262] GUI Theme Colors hard to see: always use Fusion widget style under OSX and Windows

[via KDE Bugzilla]

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

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

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||5.1.0
 Status|CONFIRMED   |RESOLVED
  Latest Commit||http://commits.kde.org/digi
   ||kam/6f4044ca14169beb9e0c94b
   ||c102e0074f09b9224

--- Comment #5 from caulier.gil...@gmail.com ---
Git commit 6f4044ca14169beb9e0c94bc102e0074f09b9224 by Gilles Caulier.
Committed on 24/07/2016 at 18:31.
Pushed by cgilles into branch 'master'.

for Windows and OSX, always use Fusion widgets style to prevent color scheme
problems.
Related: bug 365411
FIXED-IN: 5.1.0

M  +6-0libs/settings/applicationsettings.cpp
M  +2-0libs/settings/applicationsettings_miscs.cpp
M  +1-0libs/settings/applicationsettings_p.cpp
M  +1-0showfoto/main/showfoto.cpp
M  +7-1showfoto/main/showfotosettings.cpp
M  +10   -1showfoto/setup/showfotosetupmisc.cpp
M  +13   -0utilities/setup/setupmisc.cpp

http://commits.kde.org/digikam/6f4044ca14169beb9e0c94bc102e0074f09b9224

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

[plasmashell] [Bug 356937] Xembed icons have black background

[Mircea Kitsune via KDE Bugzilla]

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

--- Comment #14 from Mircea Kitsune  ---
The issue seems to have been solved for me in the latest versions of Plasma 5.
I haven't seen it for quite a few months with Skype.

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

[konsole] [Bug 366048] "Do not ask again" doesn't apply to "Close Window" button

[via KDE Bugzilla]

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

d_the_m...@yahoo.co.uk changed:

   What|Removed |Added

 CC||d_the_m...@yahoo.co.uk

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

[konsole] [Bug 366048] New: "Do not ask again" doesn't apply to "Close Window" button

[via KDE Bugzilla]

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

Bug ID: 366048
   Summary: "Do not ask again" doesn't apply to "Close Window"
button
   Product: konsole
   Version: 16.04.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: d_the_m...@yahoo.co.uk

When a process is running in Konsole, closing the window brings up a dialog to
confirm if window should be closed. The option to make Konsole not ask me again
does not apply to the "Close Window" button.

Reproducible: Always

Steps to Reproduce:
1. Start Konsole
2. Run `top`
3. Close Konsole window.
4. Message dialog is shown saying "There is a process running in this window.
Do you still want to quit?". Check "Do not ask again". Click "Close Window".
5. Repeat steps 1-3. 

Actual Results:  
Notice how it didn't remember the option to close the window without a
confirmation, i.e. the confirmation dialog is shown again.

Expected Results:  
The confirmation dialog should not show anymore. The window should just close
killing whatever process was running in the terminal.

This has been happening for at least a year (I always have latest Konsole
version).

PS: Thanks for this great terminal :)

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

[plasmashell] [Bug 366047] New: sni proxy scaling not always appropriate

[Oswald Buddenhagen via KDE Bugzilla]

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

Bug ID: 366047
   Summary: sni proxy scaling not always appropriate
   Product: plasmashell
   Version: 5.6.5
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: XembedSNIProxy
  Assignee: plasma-b...@kde.org
  Reporter: o...@kde.org

the sni proxy apparently scales the embedded window's contents, presumably to
make them visually fit into the surroundings. however, if the window contains
sharp edges and/or text, the scaling can be rather unhelpful. an example of
such an application is gnome-mail-notification, which shows a fairly tiny icon
with the number of new messages.

i suggest to provide a per-app option to disable scaling which is not an
integral multiple, and just centering the icon instead.
i'm not quite sure how to integrate it gui-wise, though. i suppose one could
react to alt-rightclick, as that's a window manager gesture which is otherwise
meaningless in this context.


Reproducible: Always

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

[dolphin] [Bug 366046] New: The tabs are not aligned with the panes below

[Narayan via KDE Bugzilla]

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

Bug ID: 366046
   Summary: The tabs are not aligned with the panes below
   Product: dolphin
   Version: 4.14.2
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: split view
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: raindrops.from...@gmail.com

Dolphin has dual panes, and each of the pane has separate tabs.
But the tabs are of random width, and it is impossible to say which tabs are
for the left pane and which are for the right pane.

For the sale of example, let us name the tabs of left panes as L1, L2, L3 and
the tabs for the right pane as R1, R2, R3.

The GUI should always show all the tabs belonging to a pane within the width of
that pane.

For example, assume that I have dragged the vertical partition between L and R
panes to the right side, so that now the L pane takes up 75% of the screen
width. In this case, L1, L2 and L3 tabs should take up 75% of the screen width;
and R1, R2 and R3 tabs should take up 25% of the screen width.

When I drag the partition between the two panes to the left/right, the width of
the tabs also must be re-adjusted continuously.

But this does not happen.

Reproducible: Always

Steps to Reproduce:
1. Create a few tabs in left pane.
2. Switch to the right pane, and create a few tabs.
3. Look at the tabs: 

Actual Results:  
There is no clear demarcation between tabs of the left pane and tabs of the
right pane.

Expected Results:  
The tabs belonging to the left pane must be accommodated within the width of
the left pane.
Similarly, the tabs belonging to the right pane must be accommodated within the
width of the right pane.

When the partition between left and right panes is moved, the width of the tabs
must be adjusted so that their combined width never exceeds the pane's width.

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

[plasmashell] [Bug 365792] Folder View widget cannot show hidden files, filters hide everything

[Eike Hein via KDE Bugzilla]

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

--- Comment #4 from Eike Hein  ---
Git commit f93e46bbb7849907c647f7e7dfc59c7fd3e3d09d by Eike Hein.
Committed on 24/07/2016 at 17:54.
Pushed by hein into branch 'Plasma/5.7'.

Fix changes of the filter pattern not being applied immediately.

Adds missing invalidateFilter call to prop setter.

M  +2-0containments/desktop/plugins/folder/foldermodel.cpp

http://commits.kde.org/plasma-desktop/f93e46bbb7849907c647f7e7dfc59c7fd3e3d09d

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

[dolphin] [Bug 366045] New: There is no keyboard shortcut to copy/move selected items to the opposite pane

[Narayan via KDE Bugzilla]

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

Bug ID: 366045
   Summary: There is no keyboard shortcut to copy/move selected
items to the opposite pane
   Product: dolphin
   Version: 4.14.2
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: split view
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: raindrops.from...@gmail.com

Dolphin is a dual-pane file manager. Yet its dual pane system is not exploited
yet.
How's that for a file manager that prides itself on Usability??

Usually F5 and F6 are used to copy/move the selected items to opposite pane.
CTRL+F5 and CTRL+F6 are used to copy/move silently (without dialog).

Reproducible: Always

Steps to Reproduce:
1. Select some files/folders
2. Try to copy/move them to the opposite pane
3. We don't have any keyboard shortcut to do this fast.

Actual Results:  
The only way is to drag-n-drop them with mouse.

Expected Results:  
Let F5 copy the selected items to opposite pane.
Let F6 move the selected items to opposite pane.
Let CTRL+F5 copy the selection silently (without dialog).
Let CTRL+F6 move the selection silently (without dialog).

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

[plasmashell] [Bug 356937] Xembed icons have black background

[Oswald Buddenhagen via KDE Bugzilla]

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

Oswald Buddenhagen  changed:

   What|Removed |Added

 CC||o...@kde.org

--- Comment #13 from Oswald Buddenhagen  ---
not sure if this has the same root cause, but it sure sounds related:
the somewhat dynamic gnome-mail-notification tray icon dissolves into a blurry
mess over time. it appears that it expects the proxy window to be pre-cleared
for it.

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

[kalarm] [Bug 339375] kalarm process has high cpu consumption

[I Hamsa via KDE Bugzilla]

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

I Hamsa  changed:

   What|Removed |Added

 CC||i.ha...@gmail.com

--- Comment #4 from I Hamsa  ---
This or similar problem still exists for me (Gentoo packages). It happens once
in a while (not every time), with no apparent pattern.

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

[kmail2] [Bug 359964] "Kmailleaks", or what to improve to make Kmail more privacy friendly.

[Thomas Pfeiffer via KDE Bugzilla]

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

Thomas Pfeiffer  changed:

   What|Removed |Added

 CC||thomas.pfeif...@kde.org

--- Comment #8 from Thomas Pfeiffer  ---
The User Agent does indeed reveal more information about the sender's system
than necessary (why would one need to know which application in which version
on which operating system was used to send an email?).
Is there anything that speaks against leaving the User-Agent string completely
out by default, or maybe reducing it to just "KMail"?
Most email clients do send user-agent information by default, but since the
sender's user agent does not really have practical relevance in an email (in
contrast to a web browser where the server uses it to apply  workarounds for
specific browsers' shortcomings, for example), we could just be better then
others in that regard.

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

[plasmashell] [Bug 357443] black/invisible squares on systray and top left of screen after kwin restarted

[Oswald Buddenhagen via KDE Bugzilla]

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

Oswald Buddenhagen  changed:

   What|Removed |Added

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

--- Comment #5 from Oswald Buddenhagen  ---
clicking the area in the systray where the proxied application is shown causes
the proxy windows to be "re-absorbed". that's of course quite a challenge, as
these windows are usually placed somewhat exactly at this place (they are
always a few pixels off, and sometimes there is almost no overlap - probably
related to the preceding kwin crash and the resulting re-layouting).

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

[clazy] [Bug 365880] Build with trunk LLVM/Clang is broken

[Sergio Martins via KDE Bugzilla]

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

Sergio Martins  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/claz
   ||y/75e04706edbdf5a22488d02fa
   ||abbe4905fd50b88
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Sergio Martins  ---
Git commit 75e04706edbdf5a22488d02faabbe4905fd50b88 by Sergio Martins.
Committed on 24/07/2016 at 17:23.
Pushed by smartins into branch 'master'.

Fix build with clang 4.0

M  +1-0MacroUtils.cpp
M  +6-6clazy_stl.h

http://commits.kde.org/clazy/75e04706edbdf5a22488d02faabbe4905fd50b88

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

[kscreenlocker] [Bug 366044] New: The lock screen clock is always in the AM/PM format.

[I Hamsa via KDE Bugzilla]

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

Bug ID: 366044
   Summary: The lock screen clock is always in the AM/PM format.
   Product: kscreenlocker
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: i.ha...@gmail.com
CC: bhus...@gmail.com, mgraess...@kde.org

The lock screen clock is always in the AM/PM format. 

Reproducible: Always

Steps to Reproduce:
1. Lock the screen, observe the clock.

Actual Results:  
8.50 pm

Expected Results:  
20:50

Tried to change the locale, to no avail.

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