[KScreen] [Bug 366721] Connecting an external monitor causes the laptop screen to go black with only the mouse cursor visible

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #1 from Simone Gaiarin  ---
Removing the kscreen configuration files doesn't solve the problem.

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

[KScreen] [Bug 366721] New: Connecting an external monitor causes the laptop screen to go black with only the mouse cursor visible

[Simone Gaiarin via KDE Bugzilla]

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

Bug ID: 366721
   Summary: Connecting an external monitor causes the laptop
screen to go black with only the mouse cursor visible
   Product: KScreen
   Version: git
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: se...@kde.org
  Reporter: simg...@gmail.com

It seems that plasma doesn't build the desktop on that screen. Tested with KDE
Neon live image developer edition stable.

Configuration:
- External monitor set as primary

Reproducible: Always

Steps to Reproduce:
1.Connect external monitor (dock)
2.
3.

Actual Results:  
Black screen on laptop with mouse only

Expected Results:  
To have the plasma desktop

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

[KScreen] [Bug 364044] Second screen in docking station keeps black after suspend

[Simone Gaiarin via KDE Bugzilla]

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

Simone Gaiarin  changed:

   What|Removed |Added

 CC||simg...@gmail.com

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

[KScreen] [Bug 351390] Corrupted kscreen config breaks KDE startup process

[Simone Gaiarin via KDE Bugzilla]

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

Simone Gaiarin  changed:

   What|Removed |Added

 CC||simg...@gmail.com

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

[frameworks-solid] [Bug 366720] New: stat() on faulty nfs mountpoints causes all KDE applications to deadlock (kill -9 required)

[Emmanuel Lepage Vallée via KDE Bugzilla]

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

Bug ID: 366720
   Summary: stat() on faulty nfs mountpoints causes all KDE
applications to deadlock (kill -9 required)
   Product: frameworks-solid
   Version: 5.24.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: lu...@kde.org
  Reporter: elv1...@gmail.com
CC: kdelibs-b...@kde.org

Mounting NFS shares using the kernel module can cause hard (infinite) lock when
the network is unstable. This is because, by default, the file system is
configured to retry until things work. However, this cause in itself the
network to be flooded and make congestion worst.

This is well documented and isn't a KDE issue. However, this has to be taken
into account by KDE and it isn't. As KDEINIT5 can stat these mountpoint and
lock itself to oblivion, everything talking to KDEINIT also lock. So, in the
end, everything lock and killall -9  from ctrl+alt+f1 is required.

I think what trigger the lock is the open/save file dialog or dolphin sidebar
with the fs list. 

To reproduce, mount an nfs (v3) share using the "mount -t nfs" command and
shutdown the server. This will also happen when copying big files over slow
wifi (TCP retry amplification problem).

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

[digikam] [Bug 345245] Digikam hangs on startup

[Ingo Dettmar via KDE Bugzilla]

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

Ingo Dettmar  changed:

   What|Removed |Added

 CC||ingo.dett...@gmail.com

--- Comment #6 from Ingo Dettmar  ---
I have the same issue in 5.0.0. and 5.1.0 on Windows 10. After a while of
normal use, Digikam will not start anymore. After removal and reinstallation it
will work again.

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

[plasmashell] [Bug 366622] crash (Segmentation fault) when I try to run application from classical application menu

[Bhushan Shah via KDE Bugzilla]

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

Bhushan Shah  changed:

   What|Removed |Added

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

--- Comment #1 from Bhushan Shah  ---


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

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

[frameworks-baloo] [Bug 366005] Plasma crashed on search

[Bhushan Shah via KDE Bugzilla]

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

Bhushan Shah  changed:

   What|Removed |Added

 CC||isushi...@gmail.com

--- Comment #1 from Bhushan Shah  ---
*** Bug 366622 has been marked as a duplicate of this bug. ***

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

[kdenlive] [Bug 351381] Video preview of clips with transitions in project monitor area is extremely slow

[via KDE Bugzilla]

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

--- Comment #8 from h.k.gh...@gmail.com ---
(In reply to Wegwerf from comment #7)
> The new features are in the beta branch (which is rougly the same as the
> master branch at this time.

I'll take a look. Is this easily un-doable, as in remove the repo later and
then down-grade back to the stable version? Any suggestion(s) before I
potentially mess up my current install?

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

[abakus] [Bug 366648] *** Removed by KDE Sysadmin due to abuse ***

[Ben Cooksley via KDE Bugzilla]

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

Ben Cooksley  changed:

   What|Removed |Added

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

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

[abakus] [Bug 366647] panipat ki ladaie !!$-$/_\+1.8.0.0.6.8.1.7.2.0.8`@@ SBCGLOBAL Email support Number phone Aus Can UK USA$#%^&*()*&^%$%%^&*(*&^%$##$$%^&*((&^%$#$%^&**&^%$

[Ben Cooksley via KDE Bugzilla]

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

Ben Cooksley  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
Summary|*** Removed by KDE Sysadmin |panipat ki ladaie
   |due to abuse ***|!!$-$/_\+1.8.0.0.6.8.1.7.2.
   ||0.8`@@ SBCGLOBAL Email
   ||support Number phone Aus
   ||Can UK
   ||USA$#%^&*()*&^%$%%^&*(*&^%$
   ||##$$%^&*((&^%$#$%^&**&^%$
 Resolution|--- |INVALID

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

[plasmashell] [Bug 365875] Crash when copy from one USB drive to another

[Mike via KDE Bugzilla]

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

Mike  changed:

   What|Removed |Added

 CC||ingzack...@gmail.com

--- Comment #3 from Mike  ---
I got almost the same issue when coping files from usb to anywhere

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

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

[Chris Holland via KDE Bugzilla]

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

Chris Holland  changed:

   What|Removed |Added

 CC||zrenf...@gmail.com

--- Comment #27 from Chris Holland  ---
Not sure if this helps, but it appears the parent parent 0x4028bae window is
raised. Running `xwininfo -tree -root` shows:

  Root window id: 0x4aa (the root window) (has no name)
  Parent window id: 0x0 (none)
 190 children:
 ...
 0x4028bae (has no name): ()  1920x1080+0+0  +0+0
1 child:
0x4028baf (has no name): ()  1920x1080+0+0  +0+0
   1 child:
   0x5200010 "Desktop — Plasma": ("plasmashell" "plasmashell") 
1920x1080+0+0  +0+0



xev -root shows something when the desktop is "raised". There's an extra
"ConfigureNotify event, " and "_NET_CLIENT_LIST_STACKING" when the desktop is
clicked.

Test Case:
Konsole Window is always on top. Then run 3 commands in different tabs.
xev -root > test.log
watch -n 0.5 -c "echo \"\\n\" >> test.log"
tail -f test.log
Then open another window (which will disappear) and click back and forth
(minimize and reveal the window if it's taking forever).



ClientMessage event, serial 22, synthetic YES, window 0x5200010,
message_type 0x172 (_NET_ACTIVE_WINDOW), format 32

PropertyNotify event, serial 22, synthetic NO, window 0x4aa,
atom 0x172 (_NET_ACTIVE_WINDOW), time 394727465, state PropertyNewValue

PropertyNotify event, serial 22, synthetic NO, window 0x4aa,
atom 0x172 (_NET_ACTIVE_WINDOW), time 394727466, state PropertyNewValue

ClientMessage event, serial 22, synthetic YES, window 0x5200010,
message_type 0x14f (_NET_WM_STATE), format 32

ClientMessage event, serial 22, synthetic YES, window 0x5200010,
message_type 0x14f (_NET_WM_STATE), format 32

ConfigureNotify event, serial 22, synthetic NO, window 0x4aa,
event 0x4aa, window 0x4028bae, (0,0), width 1920, height 1080,
border_width 0, above 0x40ce2be, override NO

PropertyNotify event, serial 22, synthetic NO, window 0x4aa,
atom 0x1a7 (_NET_CLIENT_LIST_STACKING), time 394727473, state
PropertyNewValue

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

[dolphin] [Bug 366719] New: no thumbnails previews for .kra files in kubuntu 16.04 in dolphin

[Gingle via KDE Bugzilla]

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

Bug ID: 366719
   Summary: no thumbnails previews for .kra files in kubuntu 16.04
in dolphin
   Product: dolphin
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: kok...@hotmail.com

Im using kubuntu 16.04  if it helps, my kubuntu 16.04 came with Dolphin
15.12.3, and kde5 5.5.5,  
the Bug is In dolphin preview settings there still isn't a option to allow
thumbnail previews for krita documents.I read somewhere on docs krita
installation.org that since april 2016 that dolphin would be able to show .ora
and .kra files by default.i even installed kdegraphics-thumbnailers kio-extras
, maybe kubuntu was released before april 2016 ?i dont know what else to do at
this point, but it seems this is definatley some sort of bug with kde 

Reproducible: Always

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

[kdenlive] [Bug 353294] Motion Blur when moving Title Clip position, rotation, etc. in project?

[Jesse via KDE Bugzilla]

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

--- Comment #3 from Jesse  ---
Wegwerf, no sir, the playback is fine in these tests. Rather, the issue is that
there is no motion blur quality similar to what we see in film when motion is
inherent with 24fps, 48hz shutter speed, etc.

When I look at Blender, for example, motion blur is very evident in moving
text. It looks like it should as if it was filmed with a video camera.

In Kdenlive, it's very jittery and movement of titles looks unprofessional.
I'll post some videos soon comparing the two.

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

[plasmashell] [Bug 346740] Shortcuts for several tray icons break plasmashell

[court via KDE Bugzilla]

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

--- Comment #63 from court  ---
I forgot to add that there's no weird behaviors, just broken images.

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

[plasmashell] [Bug 346740] Shortcuts for several tray icons break plasmashell

[court via KDE Bugzilla]

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

court  changed:

   What|Removed |Added

 CC||courthic...@gmail.com

--- Comment #62 from court  ---
This is extra broken in 5.7. System tray icons are broken and a bunch of icons
that are also in the application dashboard. Ones that I have broken are
Clementine, Private Internet Access application (downloaded straight from
them), I made a custom launcher for Xonotic and it's a .svg file that's broken,
KRDC, bmon, SSH AskPass, and xfburn. I hope that's useful information. These
icons have been broken for 5.7.0 to 5.7.3

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

[plasmashell] [Bug 366718] New: Dragging url and hovering a task does not reveal hovered window

[Chris Holland via KDE Bugzilla]

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

Bug ID: 366718
   Summary: Dragging url and hovering a task does not reveal
hovered window
   Product: plasmashell
   Version: 5.7.3
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: zrenf...@gmail.com
CC: plasma-b...@kde.org

~/.xsession-erros spams
`file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/MouseHandler.qml:84:
TypeError: Cannot read property 'm' of null`

which is the first line of:

if (!plasmoid.configuration.separateLaunchers &&
tasks.dragSource.m.IsLauncher === true
 && above != null && above.m.IsLauncher !== true && above ==
ignoredItem) {
return;
} else {
ignoredItem = null;
}

I have seperate launchers unchecked in my config. If I check it, it works.

Reproducible: Always

Steps to Reproduce:
1. Uncheck "seperate launchers"

Actual Results:  
Does not reveal window + spam errors

Expected Results:  
reveal window

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

[konsole] [Bug 366712] konsole freezes after creating a new tab when being in a delete directory

[rindeal]

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

Jan Chren (rindeal)  changed:

   What|Removed |Added

Version|15.12.3 |16.04.3

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

[konsole] [Bug 366712] konsole freezes after creating a new tab when being in a delete directory

[rindeal]

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

--- Comment #2 from Jan Chren (rindeal)  ---
Created attachment 100570
  --> https://bugs.kde.org/attachment.cgi?id=100570=edit
full backtrace

Konsole 16.04.3
KDE Frameworks 5.23.0
Qt 5.6.1 (built against 5.6.1)

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

[plasmashell] [Bug 365828] add firefox icon to kde panel (comes up blank)

[Tony via KDE Bugzilla]

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

Tony  changed:

   What|Removed |Added

 CC||jodr...@live.com

--- Comment #3 from Tony  ---
Fixed/not happening in KDE Neon, plasma 5.7.90, framework 5.25.0.

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

[kdenlive] [Bug 363568] no tab to select blue or green

[Larry Engel via KDE Bugzilla]

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

--- Comment #2 from Larry Engel  ---
thank you

--- bugzilla_nore...@kde.org wrote:

From: Wegwerf via KDE Bugzilla 
To: larryen...@justice.com
Subject: [kdenlive] [Bug 363568] no tab to select blue or green
Date: Fri, 12 Aug 2016 16:26:27 +

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

Wegwerf  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WAITINGFORINFO
 CC||wegwerf-1-...@gmx.de

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

[kdesvn] [Bug 366717] New: Crashes while trying to check out

[EMR_Kde via KDE Bugzilla]

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

Bug ID: 366717
   Summary: Crashes while trying to check out
   Product: kdesvn
   Version: 1.6.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: kdesvn-bugs-n...@kde.org
  Reporter: emre...@gmail.com

Application: kdesvn (1.6.0)
KDE Platform Version: 4.14.18
Qt Version: 4.8.6
Operating System: Linux 4.1.27-27-xen x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
I selected file->open, selected the file:// repository, dug into some
subdirectories, selected a directory in the left pane, clicked the "Check Out"
toolbar button, clicked OK in the resulting dialog box to check out the sub
directory.

The crash can be reproduced every time.

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

Thread 3 (Thread 0x7f8311497700 (LWP 10554)):
#0  0x7f8324b0bbfd in poll () at /lib64/libc.so.6
#1  0x7f8324134e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f8324134f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f832763efde in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#4  0x7f8327610d4f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#5  0x7f8327611045 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7f832750e4df in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x7f83275f2653 in  () at /usr/lib64/libQtCore.so.4
#8  0x7f8327510bbf in  () at /usr/lib64/libQtCore.so.4
#9  0x7f832481a0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f8324b1402d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f830bfff700 (LWP 10562)):
#0  0x7f8324b0bbfd in poll () at /lib64/libc.so.6
#1  0x7f8324134e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f8324134f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f832763efde in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#4  0x7f8327610d4f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#5  0x7f8327611045 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7f832750e4df in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x7f83275f2653 in  () at /usr/lib64/libQtCore.so.4
#8  0x7f8327510bbf in  () at /usr/lib64/libQtCore.so.4
#9  0x7f832481a0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f8324b1402d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f8327b3d780 (LWP 10551)):
[KCrash Handler]
#6  0x7f8324a640c7 in raise () at /lib64/libc.so.6
#7  0x7f8324a65478 in abort () at /lib64/libc.so.6
#8  0x7f8316700cee in  () at /usr/lib64/libsvn_subr-1.so.0
#9  0x7f831601a1be in svn_client.checkout_internal () at
/usr/lib64/libsvn_client-1.so.0
#10 0x7f831601a64c in svn_client_checkout3 () at
/usr/lib64/libsvn_client-1.so.0
#11 0x7f8316ba1e4c in  () at /usr/lib64/libsvnqt.so.7
#12 0x7f8316e6eea4 in  () at /usr/lib64/kde4/kdesvnpart.so
#13 0x7f8316e6f306 in  () at /usr/lib64/kde4/kdesvnpart.so
#14 0x7f8316e63ee9 in  () at /usr/lib64/kde4/kdesvnpart.so
#15 0x7f83276260fa in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/libQtCore.so.4
#16 0x7f83269a6652 in QAction::triggered(bool) () at
/usr/lib64/libQtGui.so.4
#17 0x7f83269a8003 in QAction::activate(QAction::ActionEvent) () at
/usr/lib64/libQtGui.so.4
#18 0x7f8326d5a902 in  () at /usr/lib64/libQtGui.so.4
#19 0x7f8326d5aa2c in QAbstractButton::mouseReleaseEvent(QMouseEvent*) ()
at /usr/lib64/libQtGui.so.4
#20 0x7f8326e1196a in QToolButton::mouseReleaseEvent(QMouseEvent*) () at
/usr/lib64/libQtGui.so.4
#21 0x7f83269fbc5a in QWidget::event(QEvent*) () at
/usr/lib64/libQtGui.so.4
#22 0x7f83269ac79c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQtGui.so.4
#23 0x7f83269b2e1a in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQtGui.so.4
#24 0x7f8325a6be9a in KApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libkdeui.so.5
#25 0x7f832761218d in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQtCore.so.4
#26 0x7f83269b2613 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at
/usr/lib64/libQtGui.so.4
#27 0x7f8326a23ceb in  () at /usr/lib64/libQtGui.so.4
#28 0x7f8326a2275c in QApplication::x11ProcessEvent(_XEvent*) () at
/usr/lib64/libQtGui.so.4
#29 0x7f8326a495f2 in  () at /usr/lib64/libQtGui.so.4
#30 0x7f8324134c84 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#31 

[plasmashell] [Bug 366707] Dual monitor, desktop crash while moving panel.

[Tony via KDE Bugzilla]

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

Tony  changed:

   What|Removed |Added

Product|kde |plasmashell
  Component|general |Panel
Version|unspecified |5.7.3
   Target Milestone|--- |1.0

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

[kde] [Bug 366707] Dual monitor, desktop crash while moving panel.

[Tony via KDE Bugzilla]

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

Tony  changed:

   What|Removed |Added

   Platform|unspecified |Neon Packages

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

[plasmashell] [Bug 366716] New: jump list actions don't work with quick launch plasmoid's launchers

[Alex L via KDE Bugzilla]

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

Bug ID: 366716
   Summary: jump list actions don't work with quick launch
plasmoid's launchers
   Product: plasmashell
   Version: 5.7.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: alexlon...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

When you right click on a launcher in one of the following place:
- task manager
- application launcher
- Dolphin
- folder view plasmoid
in the menu are listed the jump list actions if available.
In the quick launch plasmoid they are not listed.

Reproducible: Always

Steps to Reproduce:
1. add quick launch plasmoid
2. add a launcher with at least one jump list action defined, i.e. Kmail
(action: new message)
3. right click on that launcher
4. check that actions are not listed

Actual Results:  
Jump list actions are not listed in right click menu

Expected Results:  
Jump list actions listed like in all the other places launcher are

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

[plasmashell] [Bug 366715] New: quick launch plasmoid doesn't support drag and drop to add new launchers

[Alex L via KDE Bugzilla]

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

Bug ID: 366715
   Summary: quick launch plasmoid doesn't support drag and drop to
add new launchers
   Product: plasmashell
   Version: 5.7.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: alexlon...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

To add new launchers to quick launch plasmoid you have to right click > add new
launcher and select it from the list of installed applications.
It would be really better to be able to select (multiple) launchers / .desktop
files, drag and drop them into the quick launch plasmoid like for the task
manager plasmoid.

Reproducible: Always

Steps to Reproduce:
1. add quick launch plasmoid
2. try to drag and drop a .desktop launcher into it

Actual Results:  
dragging the .desktop file(s) into the quick launch plasmoid doesn't add it
(them)

Expected Results:  
when I drag and drop launcher(s) / .desktop file(s) into quick launch plasmoid
it(them) should be added to the quick launch plasmoid

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

[kde-cli-tools] [Bug 366714] New: program zooms out whenever i approach the canvas with my tablet pen

[malinda yuhas via KDE Bugzilla]

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

Bug ID: 366714
   Summary: program zooms out whenever i approach the canvas with
my tablet pen
   Product: kde-cli-tools
   Version: unspecified
  Platform: Mac OS X Disk Images
OS: OS X
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: aleix...@kde.org
  Reporter: malindayu...@gmail.com

as i attempt to put my pen onto the canvas to draw the program will zoom out by
half and then more. I'll zoom back into the program but it does it again, &
sometimes will change my mouse pointer into a zoom icon, leaving it stuck in
zoom

Reproducible: Always

Steps to Reproduce:
1.open krita with mac ox
2. start new file
3. approach canvas with pen

Actual Results:  
zoom out

Expected Results:  
not zoomed out

it's super annoying, the bug will sometimes keep the cursor from even going
into the canvas, making the mouse disappear and crash the system.

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

[kdenlive] [Bug 362204] Does not work on wayland

[Ian Dogulas Scott via KDE Bugzilla]

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

--- Comment #4 from Ian Dogulas Scott  ---
Created attachment 100569
  --> https://bugs.kde.org/attachment.cgi?id=100569=edit
Screenshot of kdenlive running in sway

This is what Kdenlive looks like for me under Wayland. Obviously it is not
rendering properly. This is with the latest version of Kdenlive on an
up-to-date Arch Linux system.

If it is relevant, my system has Intel integrated graphics (specifically an Ivy
Bridge).

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

[digikam] [Bug 365725] Menus in Ubuntu Unity 16.04 is show twice. This is when Unity is tweaked to show menus in the windows titlebar instead of the menu bar.

[via KDE Bugzilla]

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

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

   What|Removed |Added

Version|5.0.0   |5.1.0

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

[digikam] [Bug 365725] Menus in Ubuntu Unity 16.04 is show twice. This is when Unity is tweaked to show menus in the windows titlebar instead of the menu bar.

[dajomu via KDE Bugzilla]

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

--- Comment #4 from dajomu  ---
I have just finished installing Ubuntu 16.04.1 and digikam 5.1. I have the same
problem with duplicate menu's as shown in the picture in my bug-report.

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

[frameworks-ktexteditor] [Bug 318387] After moving to end and holding the up arrow, the cursor gets stuck at a tag.

[Buovjaga via KDE Bugzilla]

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

Buovjaga  changed:

   What|Removed |Added

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

--- Comment #3 from Buovjaga  ---
(In reply to Shlomi Fish from comment #2)
> Created attachment 100568 [details]
> Smaller test case - ctrl+End and holding the up arrow gets stuck

Repro with test case.

Arch Linux 64-bit
Kate 16.04.3
KDE Frameworks 5.24.0
Qt 5.7.0
xcb-wm

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

[krita] [Bug 366713] New: Was painting and suddenly Krita crashed (GDB backtrace)

[wolthera via KDE Bugzilla]

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

Bug ID: 366713
   Summary: Was painting and suddenly Krita crashed (GDB
backtrace)
   Product: krita
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: griffinval...@gmail.com

I was painting, and then suddenly Krita crashed... As I have been running krita
only in gdb lately, I got a backtrace:

Thread 1 "krita" received signal SIGSEGV, Segmentation fault.
KisPaintDevice::extent (this=0x0)
at /home/krita/kde/src/krita/libs/image/kis_paint_device.cc:1091
1091return m_d->currentStrategy()->extent();
(gdb) thread apply all backtrace

Thread 26474 (Thread 0x7fff70d5b700 (LWP 9705)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7555e738 in QWaitCondition::wait(QMutex*, unsigned long) ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#2  0x7555a467 in ?? ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#3  0x7555dc89 in ?? ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#4  0x7fffeef376fa in start_thread (arg=0x7fff70d5b700)
at pthread_create.c:333
#5  0x74c59b5d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 26473 (Thread 0x7fff907fc700 (LWP 9704)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7555e738 in QWaitCondition::wait(QMutex*, unsigned long) ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#2  0x7555a467 in ?? ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#3  0x7555dc89 in ?? ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#4  0x7fffeef376fa in start_thread (arg=0x7fff907fc700)
at pthread_create.c:333
#5  0x74c59b5d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 26472 (Thread 0x7fff7e33c700 (LWP 9703)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 ()
---Type  to continue, or q  to quit---
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7555e738 in QWaitCondition::wait(QMutex*, unsigned long) ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#2  0x7555a467 in ?? ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#3  0x7555dc89 in ?? ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#4  0x7fffeef376fa in start_thread (arg=0x7fff7e33c700)
at pthread_create.c:333
#5  0x74c59b5d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 26471 (Thread 0x7fff7155c700 (LWP 9702)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7555e738 in QWaitCondition::wait(QMutex*, unsigned long) ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#2  0x7555a467 in ?? ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#3  0x7555dc89 in ?? ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#4  0x7fffeef376fa in start_thread (arg=0x7fff7155c700)
at pthread_create.c:333
#5  0x74c59b5d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 26056 (Thread 0x7fff90ffd700 (LWP 9230)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7555e738 in QWaitCondition::wait(QMutex*, unsigned long) ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
---Type  to continue, or q  to quit---
#2  0x7555a467 in ?? ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#3  0x7555dc89 in ?? ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#4  0x7fffeef376fa in start_thread (arg=0x7fff90ffd700)
at pthread_create.c:333
#5  0x74c59b5d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 26055 (Thread 0x7fff8e840700 (LWP 9229)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7555e738 in QWaitCondition::wait(QMutex*, unsigned long) ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#2  0x7555a467 in ?? ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#3  0x7555dc89 in ?? ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#4  0x7fffeef376fa in start_thread (arg=0x7fff8e840700)
at pthread_create.c:333
#5  0x74c59b5d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 26054 (Thread 0x7fff7f6d6700 (LWP 9228)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7555e738 in QWaitCondition::wait(QMutex*, unsigned 

[KAccounts] [Bug 366635] kaccounts-mobile from workspace depends on applications & kdepim modules

[Michael Pyne via KDE Bugzilla]

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

Michael Pyne  changed:

   What|Removed |Added

   Assignee|mp...@kde.org   |kde-telepathy-b...@kde.org
Version|Git |git-latest
Product|kdesrc-build|KAccounts
  Component|project metadata|general

--- Comment #1 from Michael Pyne  ---
You might also look into the --print-modules option if you just want to know
which modules will be built, and why kdesrc-build is including them in the
build set.

Either way if there's a bug here, it's properly in kaccounts-mobile (in that it
should be meeting all dependency requirements if it is to be in KDE Workspace).
As long as its KDE dependencies are accurately listed (even if they break some
policies) then there is no bug as far as project metadata is concerned.

For what it's worth I've also added kaccounts-mobile to my "ignore-modules"
line for kde/workspace and I could add it as an example in the sample
configuration file if there's interest.

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

[konsole] [Bug 366712] konsole freezes after creating a new tab when being in a delete directory

[rindeal]

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

--- Comment #1 from Jan Chren (rindeal)  ---
if I attach strace prior to triggering the bug, konsole changes behaviour and
reports that it failed to run the shell with a message "directory not found"

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

[konsole] [Bug 366712] New: konsole freezes after creating a new tab when being in a delete directory

[rindeal]

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

Bug ID: 366712
   Summary: konsole freezes after creating a new tab when being in
a delete directory
   Product: konsole
   Version: 15.12.3
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: tabbar
  Assignee: konsole-de...@kde.org
  Reporter: dev.rindeal+bugs.kde@gmail.com

konsole freezes

Reproducible: Always

Steps to Reproduce:
1. run konsole
2. `mkdir dir && cd dir && sh -c "cd ..;rmdir dir"`
3. Ctrl+Shift+T

Actual Results:  
Konsole freezes and is unresponsive to user input, `kill -TERM` still work
though

Expected Results:  
konsole creates a new tab with PWD set to a default dir

simple backtrace:

```
#0  0x7f7d2938b5ad in read () from /lib64/libc.so.6
#1  0x7f7d26038769 in read () at /usr/include/bits/unistd.h:44
#2  forkfd_wait () at io/../../3rdparty/forkfd/forkfd.c:818
#3  0x7f7d26035890 in waitForDeadChild () at io/qprocess_unix.cpp:950
#4  0x7f7d25fea197 in _q_startupNotification () at io/qprocess.cpp:1165
#5  0x7f7d26034a06 in waitForStarted () at io/qprocess_unix.cpp:691
#6  0x7f7d25fe9e52 in waitForStarted () at io/qprocess.cpp:1804
#7  0x7f7d29019a0d in start () at
/tmp/portage/kde-apps/konsole-15.12.3/work/konsole-15.12.3/src/Pty.cpp:254
#8  0x7f7d29022f8e in run () at
/tmp/portage/kde-apps/konsole-15.12.3/work/konsole-15.12.3/src/Session.cpp:481
#9  0x7f7d290260ea in call () at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:501
#10 call, void> () at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:520
#11 impl () at /usr/include/qt5/QtCore/qobject_impl.h:143
#12 0x7f7d260af0f8 in call () at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#13 activate () at kernel/qobject.cpp:3715
#14 0x7f7d260af67f in activate () at kernel/qobject.cpp:3595
#15 0x7f7d29061d30 in imageSizeInitialized () at
/tmp/portage/kde-apps/konsole-15.12.3/work/konsole-15.12.3_build/src/moc_Emulation.cpp:473
#16 0x7f7d2906350d in qt_static_metacall () at
/tmp/portage/kde-apps/konsole-15.12.3/work/konsole-15.12.3_build/src/moc_Emulation.cpp:218
#17 0x7f7d260af20f in activate () at kernel/qobject.cpp:3730
#18 0x7f7d260af67f in activate () at kernel/qobject.cpp:3595
#19 0x7f7d260b980c in timeout () at .moc/qtimer.moc:124
#20 0x7f7d260b98dd in timerEvent () at kernel/qtimer.cpp:313
#21 0x7f7d260ae10a in event () at kernel/qobject.cpp:1237
#22 0x7f7d268aff8a in notify_helper () at kernel/qapplication.cpp:3804
#23 0x7f7d268b45f2 in notify () at kernel/qapplication.cpp:3163
#24 0x7f7d2608a98b in notifyInternal2 () at
kernel/qcoreapplication.cpp:1015
#25 0x7f7d260d02e2 in sendEvent () at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:225
#26 activateTimers () at kernel/qtimerinfo_unix.cpp:637
#27 0x7f7d260d0862 in timerSourceDispatch () at
kernel/qeventdispatcher_glib.cpp:176
#28 0x7f7d2026c0ab in g_main_dispatch () at
/tmp/portage/dev-libs/glib-2.46.2-r3/work/glib-2.46.2/glib/gmain.c:3154
#29 g_main_context_dispatch () at
/tmp/portage/dev-libs/glib-2.46.2-r3/work/glib-2.46.2/glib/gmain.c:3769
#30 0x7f7d2026c266 in g_main_context_iterate () at
/tmp/portage/dev-libs/glib-2.46.2-r3/work/glib-2.46.2/glib/gmain.c:3840
#31 0x7f7d2026c309 in g_main_context_iteration () at
/tmp/portage/dev-libs/glib-2.46.2-r3/work/glib-2.46.2/glib/gmain.c:3901
#32 0x7f7d260d0c34 in processEvents () at
kernel/qeventdispatcher_glib.cpp:417
#33 0x7f7d16eb193a in processEvents () at
eventdispatchers/qeventdispatcher_glib.cpp:115
#34 0x7f7d26089644 in processEvents () at kernel/qeventloop.cpp:128
#35 0x7f7d26089a0c in exec () at kernel/qeventloop.cpp:204
#36 0x7f7d26090937 in exec () at kernel/qcoreapplication.cpp:1285
#37 0x7f7d263a1b5a in exec () at kernel/qguiapplication.cpp:1607
#38 0x7f7d268ada33 in exec () at kernel/qapplication.cpp:2979
#39 0x7f7d29672629 in kdemain () at
/tmp/portage/kde-apps/konsole-15.12.3/work/konsole-15.12.3/src/main.cpp:125
#40 0x0040088d in main () at
/tmp/portage/kde-apps/konsole-15.12.3/work/konsole-15.12.3_build/src/konsole_dummy.cpp:3
```

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

[kdesrc-build] [Bug 366631] kdesrc-build.kde.org still referenced throughout codebase

[Michael Pyne via KDE Bugzilla]

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

Michael Pyne  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
  Latest Commit||http://commits.kde.org/kdes
   ||rc-build/fdd9b2c7ccadb3f35b
   ||57b519a11e3740e62e1215
   Version Fixed In||16.08
 Resolution|--- |FIXED

--- Comment #3 from Michael Pyne  ---
Git commit fdd9b2c7ccadb3f35b57b519a11e3740e62e1215 by Michael Pyne.
Committed on 12/08/2016 at 20:46.
Pushed by mpyne into branch 'master'.

Update documentation links to point to maintained branch.
FIXED-IN:16.08

M  +1-1README
M  +1-1kdesrc-buildrc-kf5-sample
M  +1-1kdesrc-buildrc-sample
M  +3-3modules/ksb/Application.pm

http://commits.kde.org/kdesrc-build/fdd9b2c7ccadb3f35b57b519a11e3740e62e1215

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

[dolphin] [Bug 366711] New: Moving Files -> Dolphin crashes (Duplicate of 365772 and/or 364039)

[via KDE Bugzilla]

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

Bug ID: 366711
   Summary: Moving Files -> Dolphin crashes (Duplicate of 365772
and/or 364039)
   Product: dolphin
   Version: 15.12.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: holzpf...@posteo.de

Application: dolphin (15.12.3)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-34-generic x86_64
Distribution: Ubuntu 16.04.1 LTS

-- Information about the crash:
Note: this is a duplicate to 365772 and/or 364039. The bug-reporting GUI
wouldn't let me attach my bug report to them or mark mine as possible
duplicates (someone with more knowledge please report THIS bug as a duplicate.
Thanks!

- What I was doing when the application crashed:
moving files from one partition to another

- Unusual behavior I noticed:
launches an "acces to file was denied" error before crashing

The crash can be reproduced every time.

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

Thread 3 (Thread 0x7fe68315f700 (LWP 4540)):
#0  0x7fe6a35e89cd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fe695c12f45 in ?? () from
/usr/lib/nvidia-340/tls/libnvidia-tls.so.340.96
#2  0x7fe699e24740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fe699de0e84 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fe699de1340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fe699de14ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7fe69e3f5a9b in QEventDispatcherGlib::processEvents
(this=0x7fe67c0008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#7  0x7fe69e39cdea in QEventLoop::exec (this=this@entry=0x7fe68315ecc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#8  0x7fe69e1b98a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#9  0x7fe69e1be84e in QThreadPrivate::start (arg=0x1bd58c0) at
thread/qthread_unix.cpp:331
#10 0x7fe69a96c6fa in start_thread (arg=0x7fe68315f700) at
pthread_create.c:333
#11 0x7fe6a35f8b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fe68c4c2700 (LWP 4539)):
#0  0x7fe6a35ece8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fe697c9dc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fe697c9f8d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fe68ee46629 in QXcbEventReader::run (this=0x16eea00) at
qxcbconnection.cpp:1253
#4  0x7fe69e1be84e in QThreadPrivate::start (arg=0x16eea00) at
thread/qthread_unix.cpp:331
#5  0x7fe69a96c6fa in start_thread (arg=0x7fe68c4c2700) at
pthread_create.c:333
#6  0x7fe6a35f8b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fe68f37f900 (LWP 4538)):
[KCrash Handler]
#6  QObjectPrivate::setParent_helper (this=0xff00ff, o=o@entry=0x0) at
kernel/qobject.cpp:1956
#7  0x7fe69e3d6039 in QObject::setParent (this=,
parent=parent@entry=0x0) at kernel/qobject.cpp:1933
#8  0x7fe69f8e00e2 in KCompositeJob::removeSubjob (this=,
job=0x26133a0) at ../../../src/lib/jobs/kcompositejob.cpp:71
#9  0x7fe6a16cbf76 in KIO::CopyJobPrivate::slotResultErrorCopyingFiles
(this=this@entry=0x2607630, job=job@entry=0x26133a0) at
../../../src/core/copyjob.cpp:1415
#10 0x7fe6a16cca41 in KIO::CopyJobPrivate::slotResultCopyingFiles
(this=0x2607630, job=0x26133a0) at ../../../src/core/copyjob.cpp:1283
#11 0x7fe69e3cdfca in QMetaObject::activate (sender=sender@entry=0x26133a0,
signalOffset=, local_signal_index=local_signal_index@entry=3,
argv=argv@entry=0x7ffcb19c6390) at kernel/qobject.cpp:3713
#12 0x7fe69e3ce7d7 in QMetaObject::activate (sender=sender@entry=0x26133a0,
m=m@entry=0x7fe69fb31520 ,
local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffcb19c6390)
at kernel/qobject.cpp:3578
#13 0x7fe69f8e06c2 in KJob::result (this=this@entry=0x26133a0,
_t1=_t1@entry=0x26133a0) at ./moc_kjob.cpp:555
#14 0x7fe69f8e1281 in KJob::finishJob (this=this@entry=0x26133a0,
emitResult=emitResult@entry=true) at ../../../src/lib/jobs/kjob.cpp:109
#15 0x7fe69f8e129a in KJob::emitResult (this=this@entry=0x26133a0) at
../../../src/lib/jobs/kjob.cpp:295
#16 0x7fe6a17021be in KIO::FileCopyJob::slotResult (this=0x26133a0,
job=0x1e15fc0) at ../../../src/core/filecopyjob.cpp:563
#17 0x7fe6a17031b8 in KIO::FileCopyJob::qt_static_metacall
(_o=_o@entry=0x26133a0, _c=_c@entry=QMetaObject::InvokeMetaMethod,
_id=_id@entry=1, _a=_a@entry=0x7ffcb19c6570) at ./moc_filecopyjob.cpp:116
#18 0x7fe69e3cdfca in 

[kdesrc-build] [Bug 366631] kdesrc-build.kde.org still referenced throughout codebase

[Michael Pyne via KDE Bugzilla]

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

Michael Pyne  changed:

   What|Removed |Added

 Status|UNCONFIRMED |ASSIGNED
 Ever confirmed|0   |1

--- Comment #2 from Michael Pyne  ---
I will update the trunk4 links to go to the KF5-based documentation (I've
verified they all still work). However the remaining link to the
kdesrc-build.kde.org site in the --help output is deliberate since that is a
pre-generated manpage (as far as I know we don't host manpages in groff-ready
format on docs.kde.org).

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

[frameworks-ktexteditor] [Bug 318387] After moving to end and holding the up arrow, the cursor gets stuck at a tag.

[Shlomi Fish via KDE Bugzilla]

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

--- Comment #2 from Shlomi Fish  ---
Created attachment 100568
  --> https://bugs.kde.org/attachment.cgi?id=100568=edit
Smaller test case - ctrl+End and holding the up arrow gets stuck

This is a smaller test case - Ctrl+End and holding the up arrow gets stuck.
Tested on mageia x86-64 v6 and on Fedora 24 x86-64 - can reproduce in both on
Xfce.

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

[digikam] [Bug 366683] Reverse Geottaging doesn't work on manually modified coordinates

[via KDE Bugzilla]

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

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

   What|Removed |Added

   Version Fixed In||5.2.0

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

[digikam] [Bug 366683] Reverse Geottaging doesn't work on manually modified coordinates

[Olivier Becquaert via KDE Bugzilla]

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

Olivier Becquaert  changed:

   What|Removed |Added

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

--- Comment #2 from Olivier Becquaert  ---
It Finally works after shutdown and open again DIGIKAM.

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

[kdenlive] [Bug 362902] Kdenlive crashes when adding volume effect from audio and preview it

[Jared Sackett via KDE Bugzilla]

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

--- Comment #8 from Jared Sackett  ---
(In reply to Myriam Schweingruber from comment #5)
> Sadly the backtrace doesn't contain debugging symbols, so it is not of much
> use. Please install those and provide a better backtrace. See also
> https://techbase.kde.org/Development/Tutorials/Debugging/
> How_to_create_useful_crash_reports

I've looked all over on how to install debugging symbols on arch linux, but am
coming up empty. The list of required packages is for Ubuntu (or similar)
distros, and Arch doesn't have many equivalents (such as kdenlive-dbg). I've
looked into compiling it from source, but have had no luck there. If someone
more experienced with Arch than I could help me install the debugging symbols,
I would love to provide a backtrace.

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

[kdenlive] [Bug 362902] Kdenlive crashes when adding volume effect from audio and preview it

[Jared Sackett via KDE Bugzilla]

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

Jared Sackett  changed:

   What|Removed |Added

 Ever confirmed|0   |1

--- Comment #7 from Jared Sackett  ---
*** This bug has been confirmed by popular vote. ***

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

[digikam] [Bug 366621] Crash when performing Transformation resize operation

[Maik Qualmann via KDE Bugzilla]

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

--- Comment #19 from Maik Qualmann  ---
Git commit 65fa04ca097d4ff695690886a9f2be459b4279a9 by Maik Qualmann.
Committed on 12/08/2016 at 19:29.
Pushed by mqualmann into branch 'master'.

fix crash by big memory allocation for DImg on 64bit

M  +4-4libs/dimg/dimg.cpp
M  +1-1libs/dimg/dimg.h
M  +1-1libs/dimg/loaders/dimgloader.cpp

http://commits.kde.org/digikam/65fa04ca097d4ff695690886a9f2be459b4279a9

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

[kmail2] [Bug 366709] Dialogs when importing old KMail filters need more context

[Tristan Miller via KDE Bugzilla]

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

--- Comment #4 from Tristan Miller  ---
Sorry, I don't understand your question.  Are you asking about the version of
KMail that I'm using?  It's 4.14.10.  (Isn't this KMail2?  When I first started
it, it claimed that it was, and offered to migrate my old settings.)

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

[kmail2] [Bug 366709] Dialogs when importing old KMail filters need more context

[Laurent Montel via KDE Bugzilla]

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

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #3 from Laurent Montel  ---
4.14.0?

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

[kmail] [Bug 106635] attachment compression should support gzip, bzip2, compress, not only zip

[Tristan Miller via KDE Bugzilla]

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

--- Comment #8 from Tristan Miller  ---
Confirming feature is still missing in KMail 4.14.10.  Please reassign this
report to KMail2.

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

[kmail2] [Bug 340602] KMail puts PGP/MIME signed attachments twice into the same mail (doubling mailsize)

[Tristan Miller via KDE Bugzilla]

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

Tristan Miller  changed:

   What|Removed |Added

 CC||psychon...@nothingisreal.co
   ||m

--- Comment #7 from Tristan Miller  ---
Confirming this severe bug still exists in KMail 4.14.10.

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

[kate] [Bug 365171] [PATCH] Python syntax highlighting: not working correctly for escape sequences

[Lukas Sommer via KDE Bugzilla]

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

Lukas Sommer  changed:

   What|Removed |Added

  Attachment #99902|0   |1
is obsolete||

--- Comment #3 from Lukas Sommer  ---
Created attachment 100567
  --> https://bugs.kde.org/attachment.cgi?id=100567=edit
python.xml

The documentation has been fixed.

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

[KScreen] [Bug 366468] When set screens to be not vertically aligned kscreen breaks

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #3 from Simone Gaiarin  ---
Tested with KDE Neon live image branch stable and the bug seems to not be
present.

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

[kmail2] [Bug 366710] New: Can't add filter to toolbar

[Tristan Miller via KDE Bugzilla]

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

Bug ID: 366710
   Summary: Can't add filter to toolbar
   Product: kmail2
   Version: 4.14.10
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: psychon...@nothingisreal.com

In KMail2 it is not possible to add a filter to the toolbar.  (Same as Bug
190827 in KMail 1.)

Reproducible: Always

Steps to Reproduce:
1. Settings->Configure Filters…
2. Create a new filter named Foobar. In the Advanced tab, make sure that
"Additionally add this filter tothe toolbar" is checked.
3. OK
4. Settings->Configure Toolbars…
5. Toolbar->Main Toolbar 
6. Select "Filter Foobar" from the "Available actions" list
7. Press the right-arrow button to add the filter to the "Current actions"
list.
8. Apply

Actual Results:  
9. The icon for the Foobar filter does not appear in the toolbar.

Expected Results:  
9. The icon for the Foobar filter should appear in the toolbar.

-- 
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

[via KDE Bugzilla]

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

--- Comment #176 from bar...@failpoint.pl ---
It happens after every reboot https://youtu.be/OF1EN2GcnNA (plasma 5.7.3)

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

[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started

[Twilight Sparkle via KDE Bugzilla]

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

--- Comment #19 from Twilight Sparkle  ---
(In reply to caulier.gilles from comment #16)
> The end of the trace is very very strange... Typically we see only these
> message (and limited ones) at end of digiKam session, not at startup...
> 
> Gilles Caulier

That's because I closed digikam before saving the trace.  I've redone the trace
and left digikam running.

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

[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started

[Twilight Sparkle via KDE Bugzilla]

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

--- Comment #18 from Twilight Sparkle  ---
Created attachment 100566
  --> https://bugs.kde.org/attachment.cgi?id=100566=edit
Log using debug view

Line 22 is where the trace was when the first error box appeared.  

Also I screwed up on previous post, I meant  debugview but wrote wintrace.  :-P

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

[kmail2] [Bug 366709] Dialogs when importing old KMail filters need more context

[Tristan Miller via KDE Bugzilla]

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

--- Comment #2 from Tristan Miller  ---
Created attachment 100565
  --> https://bugs.kde.org/attachment.cgi?id=100565=edit
Select Folder prompt

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

[kmail2] [Bug 366709] Dialogs when importing old KMail filters need more context

[Tristan Miller via KDE Bugzilla]

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

--- Comment #1 from Tristan Miller  ---
Created attachment 100564
  --> https://bugs.kde.org/attachment.cgi?id=100564=edit
Select Account prompt

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

[kmail2] [Bug 366709] New: Dialogs when importing old KMail filters need more context

[Tristan Miller via KDE Bugzilla]

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

Bug ID: 366709
   Summary: Dialogs when importing old KMail filters need more
context
   Product: kmail2
   Version: 4.14.10
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: psychon...@nothingisreal.com

When importing old KMail filters via Settings->Configure Filters->Import->KMail
filters, KMail2 may occasionally pop up "Select Account" or "Select Folder"
dialogs (see attached) asking for the user to provide some missing information.
 However, the only context provided to the user is the name of the filter.  In
many cases this is not enough information for the user to make a decision. 
Users cannot be expected to remember exactly what any given filter does.  And
even if they do, some filters have multiple actions that reference several
different folders, so there is no way of knowing which action KMail2 is
prompting them about.

Please redesign the dialog prompts so that they display all the original
details of the imported filter.  Or if this is too complicated, just dispense
with the prompts, and provide the user with a selectable/saveable report of
missing information so that he or she can manually fix these filters after the
import process is complete.

Reproducible: Always

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

[kdenlive] [Bug 366479] kdenlive-git crashes when I click Render button in my project

[Anton Gubarkov via KDE Bugzilla]

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

Anton Gubarkov  changed:

   What|Removed |Added

 Resolution|FIXED   |INVALID

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

[kdenlive] [Bug 366479] kdenlive-git crashes when I click Render button in my project

[Anton Gubarkov via KDE Bugzilla]

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

Anton Gubarkov  changed:

   What|Removed |Added

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

--- Comment #4 from Anton Gubarkov  ---
I use latest MLT (from git). I do have movit enabled. The error occured due to
outdated kde framework (not sure wich part of it). I rebuilt the kde-framework
and the error no longer occurs.
I close as INVALID

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

[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started

[via KDE Bugzilla]

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

--- Comment #17 from caulier.gil...@gmail.com ---
Twilight,

I think you will have more trace with debugview tool, especially from operating
system.

Gilles Caulier

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

[kdeconnect] [Bug 357783] Add option to suspend to ram/ turn off pc remotely

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #1 from Simone Gaiarin  ---
Any plan to implement this?

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

[kdenlive] [Bug 353822] kdenlive 15.08.01 crashes when I add a jpg to the project bin (when using movit)

[Anton Gubarkov via KDE Bugzilla]

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

Anton Gubarkov  changed:

   What|Removed |Added

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

--- Comment #4 from Anton Gubarkov  ---
Movit works for me for quite some time on MESA/Haswell OpenGL (doesn't work
with GLES).

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

[plasma-nm] [Bug 366708] New: Set default network priority not to zero

[Simone Gaiarin via KDE Bugzilla]

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

Bug ID: 366708
   Summary: Set default network priority not to zero
   Product: plasma-nm
   Version: 5.7.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: lu...@kde.org
  Reporter: simg...@gmail.com
CC: jgrul...@redhat.com

With the current implementation of plasma-nm it's possible to set different
priorities to different networks, it would be useful to have the default
priority set to a value different to zero (something like 50), so that it's
possible to create a new connection with lower priority than all the other
networks.

Use case:
I create a share network connection and I want to automatically connect to it
when I'm at work. Since it's a shared wireless network connection, this will be
available everywhere. Of course I don't want to automatically connect to it in
every place. To avoid this I need to raise the priority of every new network
I'll connect to.

Solution:
If the default priority for every new network is 50, I can create the shared
network connection and set a priority of 40, so that I'll automatically connect
to it only when I'm at work without changing the priority of all the other
networks.

Reproducible: Always

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

[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started

[via KDE Bugzilla]

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

--- Comment #16 from caulier.gil...@gmail.com ---
The end of the trace is very very strange... Typically we see only these
message (and limited ones) at end of digiKam session, not at startup...

Gilles Caulier

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

[konsole] [Bug 333023] Closing multiple tabs warning

[via KDE Bugzilla]

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

devia...@gmail.com changed:

   What|Removed |Added

 CC||devia...@gmail.com

--- Comment #3 from devia...@gmail.com ---
For me, is issue is also very annoying. I lose current directories as well as
connection with the terminal of programs running "in detached mode", and the
character encoding settings.

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

[konsole] [Bug 366706] New: Crash in Konsole::TerminalDisplay::updateCursor when closing session

[Martin Sandsmark via KDE Bugzilla]

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

Bug ID: 366706
   Summary: Crash in Konsole::TerminalDisplay::updateCursor when
closing session
   Product: konsole
   Version: master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: martin.sandsm...@kde.org

#0  0x7fa3fbf31c61 in Konsole::TerminalDisplay::updateCursor
(this=this@entry=0xbf730c0)
at /home/sandsmark/pkg/konsole-git/src/konsole/src/TerminalDisplay.cpp:1753
#1  0x7fa3fbf31ce0 in Konsole::TerminalDisplay::focusOutEvent
(this=0xbf730c0)
at /home/sandsmark/pkg/konsole-git/src/konsole/src/TerminalDisplay.cpp:1699
#2  0x7fa3f971230f in QWidget::event(QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#3  0x7fa3fbf3bc4a in Konsole::TerminalDisplay::event (this=0xbf730c0,
event=0x7601dd60)
at /home/sandsmark/pkg/konsole-git/src/konsole/src/TerminalDisplay.cpp:3231
#4  0x7fa3f96cae3c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#5  0x7fa3f96d25b1 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#6  0x7fa3f89eac80 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#7  0x7fa3f96cffe1 in QApplicationPrivate::setFocusWidget(QWidget*,
Qt::FocusReason) ()
   from /usr/lib/libQt5Widgets.so.5
#8  0x7fa3f970c72c in QWidget::clearFocus() () from
/usr/lib/libQt5Widgets.so.5
#9  0x7fa3f970db28 in QWidget::~QWidget() () from
/usr/lib/libQt5Widgets.so.5
#10 0x7fa3f97fd3a9 in QLabel::~QLabel() () from /usr/lib/libQt5Widgets.so.5
#11 0x7fa3fbf30116 in Konsole::TerminalDisplay::~TerminalDisplay
(this=0xbf730c0, __in_chrg=)
at /home/sandsmark/pkg/konsole-git/src/konsole/src/TerminalDisplay.cpp:452
#12 0x7fa3fbf30289 in Konsole::TerminalDisplay::~TerminalDisplay
(this=0xbf730c0, __in_chrg=)
at /home/sandsmark/pkg/konsole-git/src/konsole/src/TerminalDisplay.cpp:454
#13 0x7fa3f8a17380 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#14 0x7fa3f971210b in QWidget::event(QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#15 0x7fa3fbf3bc4a in Konsole::TerminalDisplay::event (this=0xbf730c0,
event=0xcb25b40)
at /home/sandsmark/pkg/konsole-git/src/konsole/src/TerminalDisplay.cpp:3231
#16 0x7fa3f96cae3c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#17 0x7fa3f96d25b1 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#18 0x7fa3f89eac80 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#19 0x7fa3f89ed3fd in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) ()
   from /usr/lib/libQt5Core.so.5
#20 0x7fa3f8a3f173 in ?? () from /usr/lib/libQt5Core.so.5
#21 0x7fa3f27dedd7 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#22 0x7fa3f27df040 in ?? () from /usr/lib/libglib-2.0.so.0
#23 0x7fa3f27df0ec in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#24 0x7fa3f8a3f57f in
QEventDispatcherGlib::processEvents(QFlags) ()
   from /usr/lib/libQt5Core.so.5
#25 0x7fa3f89e90da in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#26 0x7fa3f89f15cc in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#27 0x7fa3fc56dcf2 in kdemain (argc=, argv=)
at /home/sandsmark/pkg/konsole-git/src/konsole/src/main.cpp:172
#28 0x7fa3fc1c82d1 in __libc_start_main () from /usr/lib/libc.so.6
#29 0x00400729 in _start ()

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

[kde] [Bug 366707] New: Dual monitor, desktop crash while moving panel.

[Tony via KDE Bugzilla]

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

Bug ID: 366707
   Summary: Dual monitor, desktop crash while moving panel.
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: jodr...@live.com

Application: plasmashell (5.7.90)

Qt Version: 5.7.0
Frameworks Version: 5.25.0
Operating System: Linux 4.6-6.1-liquorix-amd64 x86_64
Distribution: KDE neon User Edition 5.7

-- Information about the crash:
- What I was doing when the application crashed:
I was trying to move/drag a default panel from 1 screen to another.

- Unusual behavior I noticed:
You need to drag it in 1 fast swop 1 screen to another.
If the panel gets stuck on either side of a screen while still dragging the
desktop will crash.
If you stopped dragging the panel while a part of it is shown on both screens
the desktop will crash.

- Custom settings of the application:
None, i deleted .cache and .config from my home folder, logout and in, tried
again the problems persists. 

I must add that one of the monitors is a pretty old one, DELL 1503FP with a max
res of 1024x768, the other is AOC 2243W a 1080p monitor.

The crash can be reproduced every time.

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

Thread 14 (Thread 0x7f1f87fff700 (LWP 5600)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f2062d92adb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x3d3b0c0) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, mutex=0x3cc10d0,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#3  0x7f2066030f5d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7f2066031835 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f2062d91c28 in QThreadPrivate::start (arg=0x3cc1050) at
thread/qthread_unix.cpp:344
#6  0x7f2061e5a6fa in start_thread (arg=0x7f1f87fff700) at
pthread_create.c:333
#7  0x7f2062691b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7f1f8580a700 (LWP 5531)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f2062d92adb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x39e36f0) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, mutex=0x38e5e30,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#3  0x7f2066030f5d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7f2066031835 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f2062d91c28 in QThreadPrivate::start (arg=0x38e5db0) at
thread/qthread_unix.cpp:344
#6  0x7f2061e5a6fa in start_thread (arg=0x7f1f8580a700) at
pthread_create.c:333
#7  0x7f2062691b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7f1f8f3f7700 (LWP 5509)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f2062d92adb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x244ade0) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, mutex=0x29d7060,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#3  0x7f2066030f5d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7f2066031835 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f2062d91c28 in QThreadPrivate::start (arg=0x29d6fe0) at
thread/qthread_unix.cpp:344
#6  0x7f2061e5a6fa in start_thread (arg=0x7f1f8f3f7700) at
pthread_create.c:333
#7  0x7f2062691b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7f1f8700 (LWP 5508)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f2062d92adb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x2c99d00) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, mutex=0x1f53a70,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#3  0x7f2066030f5d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7f2066031835 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f2062d91c28 in QThreadPrivate::start (arg=0x1f539f0) at
thread/qthread_unix.cpp:344
#6  0x7f2061e5a6fa in start_thread (arg=0x7f1f8700) at
pthread_create.c:333
#7  0x7f2062691b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7f1f9cb13700 (LWP 5507)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at

[konsole] [Bug 366706] Crash in Konsole::TerminalDisplay::updateCursor when closing session

[Martin Sandsmark via KDE Bugzilla]

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

Martin Sandsmark  changed:

   What|Removed |Added

   Assignee|konsole-de...@kde.org   |martin.sandsm...@kde.org

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

[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started

[Twilight Sparkle via KDE Bugzilla]

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

--- Comment #15 from Twilight Sparkle  ---
Created attachment 100563
  --> https://bugs.kde.org/attachment.cgi?id=100563=edit
Log using wintrace tool

I did a log as well following the previous post directions.

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

[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started

[via KDE Bugzilla]

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

--- Comment #14 from caulier.gil...@gmail.com ---
Thanks for the feedback.

Typically, there is no interaction with memory card device under Windows, as
KDE::Solid API dedicated for that as under Linux do not work under Windows.

We plan to add separated code to handle USB device notifications.

Other problem is to test here under windows : there is no real computer with
Windows, only a virtual machine. So the results can be different.

Gilles Caulier

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

[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started

[Twilight Sparkle via KDE Bugzilla]

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

Twilight Sparkle  changed:

   What|Removed |Added

 CC||twisterddfsl83...@gmail.com

--- Comment #13 from Twilight Sparkle  ---
With 5.00 and 5.10 I've experienced this same problem.

It does not go away after a reboot.

Win 7 64 bit.

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

[kdenlive] [Bug 364470] Odwróć wycinek

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WAITINGFORINFO

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

[kdenlive] [Bug 364428] git master 2016-06-17 - Speed and freeze effects do not work together....

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #3 from Wegwerf  ---
Cannot reproduce with recent 16.07.90 and MLT 6.2.0+. Freezing works when
applied to a timewarped effect; freezing only applies to video though, but that
should not be an issue, as I don't think freezing a single audio frame will be
of much use...? Evert, can you please retest using recent Kdenlive beta and
recent MLT?

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

[kdenlive] [Bug 361003] git master - add feathering of edges for "Crop, Scale and Tilt" effect?

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED
 CC||wegwerf-1-...@gmx.de

--- Comment #1 from Wegwerf  ---
This is an upstream issue, affecting the source of the cropping effect, which
is either MLT or frei0r. Please report with these projects. Thank you very much
for your cooperation.

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

[kwin] [Bug 366689] kwin_wayland segfault ... error 4 in libQt5Qml.so.5.7.0

[James via KDE Bugzilla]

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

--- Comment #4 from James  ---
I'm not sure about aurorae decorations, but I opened system settings in 
regular X Windows KDE, selected Workspace Theme / Look And Feel, and selected
"Breeze" instead of "Oxygen".  Then I logged-out of KDE and logged-out of my
virtual terminal - which terminates most of my  session processes - then
logged-in again at the virtual terminal, and ran startplasmacompositor.  KDE
opened with the new window decoration colors, but otherwise I get the same
exact freeze and shutdown as before.  Checking the system log, I see the same
segfaults for kwin_wayland and kactivitymanagerd, except that this time I also
see

systemd-coredump[12180]: Process 12168 (drkonqi) of user 1000 dumped core.

Stack trace of thread 12168:
#0  0x7fd18d66e04f raise (libc.so.6)
#1  0x7fd18d66f47a abort (libc.so.6)
#2  0x7fd18ddf44a1 _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5)
#3  0x7fd1816e858e _ZN14QXcbConnectionC1EP19QXcbNativeInterfacebjPKc
(libQt5XcbQpa.so.5)
#4  0x7fd1816eb74e _ZN15QXcbIntegrationC1ERK11QStringListRiPPc
(libQt5XcbQpa.so.5)
#5  0x7fd1819ab32d n/a (libqxcb.so)
#6  0x7fd18e52104d
_ZN27QPlatformIntegrationFactory6createERK7QStringRK11QStringListRiPP
#7  0x7fd18e52f252 _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv
(libQt5Gui.s
#8  0x7fd18e52fced _ZN22QGuiApplicationPrivate21createEventDispatcherEv
(libQt5Gui.so.5)
#9  0x7fd18dfee3bf _ZN23QCoreApplicationPrivate4initEv (libQt5Core.so.5)
#10 0x7fd18e5317af _ZN22QGuiApplicationPrivate4initEv (libQt5Gui.so.5)
#11 0x7fd18ecccae9 _ZN19QApplicationPrivate4initEv (libQt5Widgets.so.5)
#12 0x0041c659 n/a (drkonqi)
#13 0x7fd18d65b291 __libc_start_main (libc.so.6)
#14 0x0041d6e9 _start (drkonqi)

But then, there is no similar kernel log message about a drkonqi segfault, as
there is for kwin_wayland and  kactivitymanagerd.

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

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

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #5 from Wegwerf  ---
Stefan, can you re-check with current beta 16.07.90? Thank you for your efforts
in advance?

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

[kdenlive] [Bug 364556] Title editor moves titles around when reopening titles

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
 CC||wegwerf-1-...@gmx.de

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

[kdenlive] [Bug 364568] "Edit clip" is disabled in the project bin

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Wegwerf  ---
This has been recently fixed in the current beta 16.07.90 and should reach you
at least as 16.08.0.

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

[kdenlive] [Bug 363568] no tab to select blue or green

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WAITINGFORINFO
 CC||wegwerf-1-...@gmx.de

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

[kdenlive] [Bug 364270] mlt crash by trying to get libssh2_scp_recv2 from libucrl

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |RESOLVED

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

[kdenlive] [Bug 348148] video speed adjustment changes clip truncation

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

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

--- Comment #4 from Wegwerf  ---
Cannot reproduce with recent Kdenlive 16.04.2/beta 16.07.90, MLT 6.2.0+ and the
new timewarp-based speed effect. This seems to be fixed.

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

[kdenlive] [Bug 364012] git master: optimization for loading existing preview render chunks may conflict with change clip invalidation

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

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

--- Comment #4 from Wegwerf  ---
Fixed.

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

[valgrind] [Bug 364948] Add IBM ISA 3.0 support, patch set 5

[Julian Seward via KDE Bugzilla]

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

--- Comment #9 from Julian Seward  ---
Thanks for the changes.  Both patches look OK to me.   Land.

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

[kdenlive] [Bug 363951] Keeps randomly crashing (segfault) by just using it every couple of minutes

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WAITINGFORINFO

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

[kdenlive] [Bug 360169] Rendering with rescale throws audio off sync

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #1 from Wegwerf  ---
eezaque, can you please test with recent stable Kdenlive 16.04.2 (or recent
beta 16.07.90) and MLT 6.2.0+? Is the audio sync problem still present?

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

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

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #1 from Wegwerf  ---
Cannot reproduce with recent beta 16.07.90. Can you please try the beta or
16.04.2 and MLT 6.2.0+ to see if you still see a crash?

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

[kdenlive] [Bug 363370] Handles to resize Automask are missing on first frame

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Wegwerf  ---
Cannot reproduce with recent beta 16.07.90. Handles properly appear.

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

[kdenlive] [Bug 363246] Git master: Insert/overwrite actions just insert/overwrite a blank space instead of audio and video.

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

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

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

[kdenlive] [Bug 363324] git master: Ctrl+C + Ctrl+V comands on a grouped separated audio/video clip ("Strict" mode) don't perform the action

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
 CC||wegwerf-1-...@gmx.de

--- Comment #1 from Wegwerf  ---
I can confirm seeing this even on recent beta.

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

[kdenlive] [Bug 363300] Ability to call a user script/command after a successful render

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
 CC||wegwerf-1-...@gmx.de

--- Comment #1 from Wegwerf  ---
Kdenlive has a post-rendering action option, see Configure Notifications > Run
Command. See also:
https://thediveo-e.blogspot.de/2016/06/kdenlive-adding-meta-data-and-cover-art.html

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

[kdenlive] [Bug 363247] git master: Shift + R on a disabled video/audio clip creates only video with audio embedded clips

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

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

[kdenlive] [Bug 363271] Decreasing track height should also decrease track toggle buttons, not remove them.

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Wegwerf  ---
Fixed.

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

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

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #1 from Wegwerf  ---
bryanworsley, can you please test using stable Kdenlive 16.04.2 (or recent beta
16.07.90) and MLT 6.2.0+? Does the crash still happen? I'm on Kubuntu 16.04 LTS
too, but cannot reproduce. I work productively using git master and recent
beta, never seeing the crash you did experience.

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

[kleopatra] [Bug 365931] Kleopatra only shows Knight Rider Progress bar and no real progress

[Andre Heinecke via KDE Bugzilla]

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

Andre Heinecke  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kleo
   ||patra/fab9fd5f804bdb54db16a
   ||1e51b3528b6036d0364
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Andre Heinecke  ---
Git commit fab9fd5f804bdb54db16a1e51b3528b6036d0364 by Andre Heinecke.
Committed on 12/08/2016 at 16:05.
Pushed by aheinecke into branch 'master'.

Fix progress handling (for gnupg >= 2.1.15)

We finally have a solution for progress that works with Qt
data types and how kleopatra passes data to GnuPG. This
requires GpgME 1.7.0 and GnuPG 2.1.15 to work.

This also simplifies progress handling for that case as we
can finally use current and total values and GnuPG no longer
overflows in progress messages since 2.1.14.

M  +1-1CMakeLists.txt
M  +4-17   src/crypto/gui/newresultpage.cpp
M  +14   -11   src/crypto/task.cpp
M  +2-2src/crypto/task.h
M  +46   -26   src/crypto/taskcollection.cpp

http://commits.kde.org/kleopatra/fab9fd5f804bdb54db16a1e51b3528b6036d0364

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

[kdenlive] [Bug 363036] git master: Timeline zone bar issues

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
 CC||wegwerf-1-...@gmx.de

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

[kdenlive] [Bug 362630] when you insert a clip in the timeline, by the mouse in insert mode, all the clips in the timeline move forward

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

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

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

[kdenlive] [Bug 361396] Splitting audio allows timeline corruption

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

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

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

[kdenlive] [Bug 362882] Audio track doesn't plays while video track playing.

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
 CC||wegwerf-1-...@gmx.de

--- Comment #1 from Wegwerf  ---
Egor, this sounds like an issue with the project-internal audio mix
transitions. You can easily fix it by loading your project into current beta
Kdenlive 16.07.90 or upcoming 16.08.0. Then please insert a new track (audio or
video doesn't matter) anywhere. Next, remove it. This will rebuild all internal
audio mixers (as well as track compositors). I've fixed my own projects with
audio problems this way.

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

[kdenlive] [Bug 358223] Rotoscoping effect crashes kdenlive when played

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

 CC||andri...@gmail.com

--- Comment #9 from Wegwerf  ---
*** Bug 359232 has been marked as a duplicate of this bug. ***

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