[krita] [Bug 408015] Global menu doesn't work

[Antonio Rojas]

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

--- Comment #1 from Antonio Rojas  ---
Seems to happen with Qt 5.13 only, works fine in Qt 5.12. Rebuilding with 5.13
has no effect

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

[plasmashell] [Bug 407957] Plasmashell crashes when connecting to wireless network

[bugzilla_noreply]

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

--- Comment #5 from ger...@teclogix.co.za ---
HI,

My KDE Plasma Version is version 5.15.4

Qt version: 5.12.2

Gerrit van der Waldt
IT Support Engineer
[https://user-generated.getmailspring.com/asset/MmM0NTU1NWMtYmJkMS00NWNkLTlhNjctZWJkNTk3ZDNhOGQxL3NpZy1pbml0aWFsLnBuZw.png?t=1558073306665&msw=249&msh=33]
E // ger...@teclogix.co.za
P // 0820736901
W // http://www.teclogix.co.za
On May 27 2019, at 9:14 am, David Edmundson  wrote:
https://bugs.kde.org/show_bug.cgi?id=407957

David Edmundson  changed:

What |Removed |Added

Resolution|--- |WAITINGFORINFO
Status|REPORTED |NEEDSINFO

--- Comment #4 from David Edmundson  ---
KDE Plasma Version: newest


What is "newest"? This is a plotter bug, I fixed some recently.

You can find out in kinfocenter

--
You are receiving this mail because:
You reported the bug.

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

[krita] [Bug 405747] Samsung Notebook 9 Pro/Pen S Pen (By Wacom) Eraser Button Not Working When Pressed In Proximity

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #17 from Boudewijn Rempt  ---
Have you checked with the 4.2.0 beta we released last week? See
https://krita.org/en/item/krita-4-2-0-beta-released/

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

[krita] [Bug 408015] Global menu doesn't work

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org

--- Comment #2 from Boudewijn Rempt  ---
That sounds like it's a regression in Qt then, not in Krita. We don't do
anything special in any case.

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

[frameworks-ktexteditor] [Bug 408016] New: Deletes previous line when hitting backspace at start of line

[Kai Uwe Broulik]

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

Bug ID: 408016
   Summary: Deletes previous line when hitting backspace at start
of line
   Product: frameworks-ktexteditor
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: k...@privat.broulik.de
  Target Milestone: ---

Since latest updates when I hit backspace in Kate at the beginning of a line,
the entire line above it is deleted, affects Kate and Kwrite, so presumably a
severe ktexteditor issue.

STEPS TO REPRODUCE
1. Write "Test" in a file and hit return so the cursor is now on a new line
2. Hit backspace

OBSERVED RESULT
The "Test" line is deleted

EXPECTED RESULT
The cursor moves to the end of the "Test" line


SOFTWARE/OS VERSIONS
KDE Applications Version: 19.07.70 (git)
KDE Frameworks Version: 5.59.0 (git)
Qt Version: 5.12.0

ADDITIONAL INFORMATION
No, I'm not in VI mode :)

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

[frameworks-ktexteditor] [Bug 408016] Deletes previous line when hitting backspace at start of line

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||loh@googlemail.com

--- Comment #1 from Kai Uwe Broulik  ---
Git bisect suggests bcba8991413622ecec690a2c4ee033f47ef680a5 "Review
del/backspace" as culprit

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

[digikam] [Bug 408017] New: Thumbnails disappear after workflow initiated

[Chris Prior]

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

Bug ID: 408017
   Summary: Thumbnails disappear after workflow initiated
   Product: digikam
   Version: 6.0.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: BatchQueueManager-Workflow
  Assignee: digikam-bugs-n...@kde.org
  Reporter: cmpr...@gmail.com
  Target Milestone: ---

SUMMARY
I have a workflow to create a jpeg reduced size copy of the files I have loaded
in Digikam in raw (cr2) format.
Once the workflow has run, the thumbnails disappear. I have checked the file
systems and the cr2 files are still in the designated folder. Also, the
pictures can be seen if I select 'table' view.
Other thumbnails are still visible for folders where the workflow has not been
run.

STEPS TO REPRODUCE
1. Select all files in folder
2. Run workflow (convert to jpeg, resize and save in different folder)
3. Thumbnails no longer appear

OBSERVED RESULT
Thumbnails missing

EXPECTED RESULT
Thumbnails still visible

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Gentoo 4.19.37, gcc 8.3.0
(available in About System)
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.57.0
Qt Version: 5.12.3

ADDITIONAL INFORMATION
Worked fine in previous version of digikam

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

[frameworks-baloo] [Bug 408018] New: Application: Baloo File Extractor (baloo_file_extractor), signal: Aborted

[guy]

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

Bug ID: 408018
   Summary: Application: Baloo File Extractor
(baloo_file_extractor), signal: Aborted
   Product: frameworks-baloo
   Version: 5.58.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Baloo File Daemon
  Assignee: baloo-bugs-n...@kde.org
  Reporter: guy.car...@gmail.com
  Target Milestone: ---

SUMMARY
every time I boot up my Fedora30 I'm getting an error that Baloo File Extractor
Crashed

STEPS TO REPRODUCE
1. boot up Fedora30


SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Fedora30 KDE plasma
(available in About System)
KDE Plasma Version:   plasm a-workspace-common-5.15.5-1.fc30.x86_64
KDE Frameworks Version:   kde-settings-30.0-1.fc30.noarch
Qt Version:  qt5

ADDITIONAL INFORMATION

Application: Baloo File Extractor (baloo_file_extractor), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f289c4bf800 (LWP 2472))]

Thread 3 (Thread 0x7f288e9b6700 (LWP 2493)):
#0  0x7f289e350dde in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#1  0x7f289e351270 in ?? () from /lib64/libglib-2.0.so.0
#2  0x7f289e351313 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f289f782413 in QEventDispatcherGlib::processEvents
(this=0x7f288b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#4  0x7f289f72c2bb in QEventLoop::exec (this=this@entry=0x7f288e9b5d70,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#5  0x7f289f585675 in QThread::exec (this=this@entry=0x7f28a074d060
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#6  0x7f28a06c9f4a in QDBusConnectionManager::run (this=0x7f28a074d060
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:178
#7  0x7f289f5867c6 in QThreadPrivate::start (arg=0x7f28a074d060 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:361
#8  0x7f289ec7f5a2 in start_thread () from /lib64/libpthread.so.0
#9  0x7f289f203163 in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f288f1cd700 (LWP 2488)):
#0  0x7f289f1f83f7 in poll () from /lib64/libc.so.6
#1  0x7f289e2d738a in ?? () from /lib64/libxcb.so.1
#2  0x7f289e2d8ffa in xcb_wait_for_event () from /lib64/libxcb.so.1
#3  0x7f288f3c8908 in QXcbEventQueue::run (this=0x55a0d4df65f0) at
qxcbeventqueue.cpp:228
#4  0x7f289f5867c6 in QThreadPrivate::start (arg=0x55a0d4df65f0) at
thread/qthread_unix.cpp:361
#5  0x7f289ec7f5a2 in start_thread () from /lib64/libpthread.so.0
#6  0x7f289f203163 in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f289c4bf800 (LWP 2472)):
[KCrash Handler]
#6  0x7f289f13feb5 in raise () from /lib64/libc.so.6
#7  0x7f289f12a895 in abort () from /lib64/libc.so.6
#8  0x7f289ee46ca3 in mdb_assert_fail (env=0x55a0d4f0b830,
expr_txt=expr_txt@entry=0x7f289ee4902f "rc == 0",
func=func@entry=0x7f289ee49978 <__func__.7120> "mdb_page_dirty",
line=line@entry=2127, file=0x7f289ee49010 "mdb.c") at mdb.c:1542
#9  0x7f289ee3b9c5 in mdb_page_dirty (mp=,
txn=0x55a0d4f0d3b0) at mdb.c:2114
#10 mdb_page_dirty (txn=0x55a0d4f0d3b0, mp=) at mdb.c:2114
#11 0x7f289ee3cc56 in mdb_page_alloc (num=num@entry=1,
mp=mp@entry=0x7ffdf65aa558, mc=) at mdb.c:2308
#12 0x7f289ee3ce93 in mdb_page_touch (mc=mc@entry=0x7ffdf650) at
mdb.c:2495
#13 0x7f289ee3ead7 in mdb_cursor_touch (mc=mc@entry=0x7ffdf650) at
mdb.c:6523
#14 0x7f289ee41bed in mdb_cursor_put (mc=mc@entry=0x7ffdf650,
key=key@entry=0x7ffdf65aae80, data=data@entry=0x7ffdf65aae90,
flags=flags@entry=0) at mdb.c:6657
#15 0x7f289ee449f8 in mdb_put (txn=0x55a0d4f0d3b0, dbi=7,
key=0x7ffdf65aae80, data=0x7ffdf65aae90, flags=0) at mdb.c:9022
#16 0x7f28a07873b8 in Baloo::IdTreeDB::put(unsigned long long,
QVector) () from /lib64/libKF5BalooEngine.so.5
#17 0x7f28a07ac1d0 in Baloo::WriteTransaction::removeDocument(unsigned long
long) () from /lib64/libKF5BalooEngine.so.5
#18 0x7f28a079e657 in Baloo::Transaction::removeDocument(unsigned long
long) () from /lib64/libKF5BalooEngine.so.5
#19 0x55a0d3ef599a in Baloo::App::processNextFile (this=0x7ffdf65ab7e0) at
/usr/src/debug/kf5-baloo-5.58.0-1.fc30.x86_64/src/file/extractor/app.cpp:106
#20 0x7f289f763dc6 in QtPrivate::QSlotObjectBase::call (a=0x7ffdf65ab1e0,
r=, this=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394
#21 QSingleShotTimer::timerEvent (this=0x55a0d5753220) at kernel/qtimer.cpp:318
#22 0x7f289f7583c5 in QObject::event (this=0x55a0d5753220, e=) at kernel/qobject.cpp:1282
#23 0x7f28a0086ad6 in QApplicationPrivate::notify_helper
(this=this@entry=0x55a0d4dd6100, receiver=receiver

[kalarm] [Bug 408006] Errors at startup

[David Jarvie]

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

David Jarvie  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
Summary|please read the thread  |Errors at startup
 Resolution|--- |DUPLICATE

--- Comment #2 from David Jarvie  ---


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

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

[kalarm] [Bug 407544] KAlarm 19.04 doesn't work at all

[David Jarvie]

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

David Jarvie  changed:

   What|Removed |Added

 CC||anticorporatedemocrat@zoho.
   ||eu

--- Comment #4 from David Jarvie  ---
*** Bug 408006 has been marked as a duplicate of this bug. ***

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

[digikam] [Bug 408017] Thumbnails disappear after workflow initiated

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
This was a bug in digiKam-6.0.0, this is fixed from digiKam-6.1.0. The
versioning hides the original image. As a workaround you can activate the
display of original image in the setup under versioning. Better, you are using
a recent version of digiKam.

Maik

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

[plasmashell] [Bug 389999] Multiple instances of the same notification

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from Kai Uwe Broulik  ---
Most likely fixed by the new notification system.

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

[plasmashell] [Bug 385880] Global Menu: does not work under wayland and causes a black screen when trying to enter its setting

[Bart Ribbers]

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

Bart Ribbers  changed:

   What|Removed |Added

  Flags||Wayland+
 CC||bribb...@disroot.org

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

[digikam] [Bug 408017] Thumbnails disappear after workflow initiated

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #2 from Maik Qualmann  ---


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

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

[digikam] [Bug 405137] Original items visible in Thumbnails view

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||cmpr...@gmail.com

--- Comment #11 from Maik Qualmann  ---
*** Bug 408017 has been marked as a duplicate of this bug. ***

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

[krita] [Bug 407597] Save is very slow - git 7bc375b

[Manga Tengu]

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

--- Comment #6 from Manga Tengu  ---
I don't remember who told me he just fixed it when I talked about it on IRC.
However in dc14cb2 I can comfirm save went fast again.

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

[krita] [Bug 407597] Save is very slow - git 7bc375b

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #7 from Boudewijn Rempt  ---
Setting to resolved then.

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

[kwin] [Bug 385522] Present Windows: Don't darken all windows and denote selection some other way than restoring original lightness

[bugzilla_noreply]

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

--- Comment #34 from antonio.guadag...@gmail.com ---
(In reply to Saverio Brancaccio from comment #33)
> Sirs, considering all the comments here, it is clear this windows dimming is
> wrong. For sure it's clear that it must be removed or at least regulated
> through a simple setting... Now my questions are:
> 1) When this issue will be adressed? Discussions are going on from 2017!
> 2) Who is the developer responsible for this functionality?
> 3) What does think the developer about fixing the issue?
> 
> Thanks

I just wanted to make it clear that this discussion started in 2013 and not
only in 2017.

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

Six years have passed and we are still here with these discussion where it
seems that on the other side there is someone who does not want to understand
...

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

[krita] [Bug 408019] New: Crash after a drag'n'drop of a group of layers from one subwindows to another

[David REVOY]

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

Bug ID: 408019
   Summary: Crash after a drag'n'drop of a group of layers from
one subwindows to another
   Product: krita
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Layer Stack
  Assignee: krita-bugs-n...@kde.org
  Reporter: i...@davidrevoy.com
  Target Milestone: ---

Hi,
A 'freeze then crash' I had in a consistent way while drag'n'drop of a group of
layers from one subwindows to another.
I could get a (gdb) backtrace: 

GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from krita...done.
Starting program: /home/deevad/sources/krita/inst/bin/krita 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffdedd9700 (LWP 14676)]
[New Thread 0x7fffd3b23700 (LWP 14677)]
[Thread 0x7fffdedd9700 (LWP 14676) exited]
[New Thread 0x7fffdedd9700 (LWP 14678)]
[Thread 0x7fffdedd9700 (LWP 14678) exited]
[New Thread 0x7fffdedd9700 (LWP 14679)]
[Thread 0x7fffdedd9700 (LWP 14679) exited]
[New Thread 0x7fffdedd9700 (LWP 14680)]
Set style "fusion"
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
[New Thread 0x7fffbb0e0700 (LWP 14681)]
QObject::startTimer: Timers cannot have negative intervals
[New Thread 0x7fffb9aa6700 (LWP 14682)]
[New Thread 0x7fffb92a5700 (LWP 14683)]
/home/deevad/sources/krita/inst/lib/x86_64-linux-gnu/krita-python-libs/krita
added to PYTHONPATH
QObject::connect: Cannot connect (null)::stateChanged(QScroller::State) to
KoToolBoxScrollArea::slotScrollerStateChange(QScroller::State)
[New Thread 0x7fffa62bf700 (LWP 14684)]
qrc:/touchstrip.qml:3:1: module "org.krita.sketch.components" is not installed
qrc:/touchstrip.qml:2:1: module "org.krita.sketch" is not installed
qrc:/touchstrip.qml:3:1: module "org.krita.sketch.components" is not installed
qrc:/touchstrip.qml:2:1: module "org.krita.sketch" is not installed
[New Thread 0x7fffa4cbb700 (LWP 14687)]
[New Thread 0x7fff9700 (LWP 14688)]
[New Thread 0x7fff9ec0a700 (LWP 14689)]
[New Thread 0x7fff9e409700 (LWP 14690)]
[New Thread 0x7fff9dc08700 (LWP 14692)]
[New Thread 0x7fff9d407700 (LWP 14693)]
[New Thread 0x7fff9cc06700 (LWP 14694)]
[New Thread 0x7fff83fff700 (LWP 14695)]
[Thread 0x7fff9e409700 (LWP 14690) exited]
[Thread 0x7fff9dc08700 (LWP 14692) exited]
[Thread 0x7fff9ec0a700 (LWP 14689) exited]
[Thread 0x7fff9d407700 (LWP 14693) exited]
[Thread 0x7fff9cc06700 (LWP 14694) exited]
[Thread 0x7fff83fff700 (LWP 14695) exited]
[New Thread 0x7fff83fff700 (LWP 14696)]
[Thread 0x7fff83fff700 (LWP 14696) exited]
[New Thread 0x7fff83fff700 (LWP 14697)]
[New Thread 0x7fff9cc06700 (LWP 14698)]
[New Thread 0x7fff9d407700 (LWP 14699)]
[New Thread 0x7fff9dc08700 (LWP 14700)]
[New Thread 0x7fff80ffd700 (LWP 14705)]
[New Thread 0x7fff77fff700 (LWP 14706)]
[New Thread 0x7fff777fe700 (LWP 14707)]
[New Thread 0x7fff76ffd700 (LWP 14708)]
[Thread 0x7fff9cc06700 (LWP 14698) exited]
[Thread 0x7fff9d407700 (LWP 14699) exited]
[Thread 0x7fff83fff700 (LWP 14697) exited]
[Thread 0x7fff9dc08700 (LWP 14700) exited]
[Thread 0x7fff80ffd700 (LWP 14705) exited]
[Thread 0x7fff77fff700 (LWP 14706) exited]
[Thread 0x7fff777fe700 (LWP 14707) exited]
[Thread 0x7fff76ffd700 (LWP 14708) exited]
[New Thread 0x7fff76ffd700 (LWP 14709)]
[Thread 0x7fff76ffd700 (LWP 14709) exited]
[New Thread 0x7fff76ffd700 (LWP 14713)]
[New Thread 0x7fff777fe700 (LWP 14714)]
[New Thread 0x7fff77fff700 (LWP 14715)]
[New Thread 0x7fff80ffd700 (LWP 14716)]
[New Thread 0x7fff9d20a700 (LWP 14717)]
[New Thread 0x7fff83fff700 (LWP 14718)]
[New Thread 0x7fff767fc700 (LWP 14719)]
[New Thread 0x7fff75

[krita] [Bug 408019] Crash after a drag'n'drop of a group of layers from one subwindows to another

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org

--- Comment #1 from Boudewijn Rempt  ---
Does this always happen, or only sometimes? I tried to reproduce with a simple
image, but didn't manage yet.

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

[krita] [Bug 408019] Crash after a drag'n'drop of a group of layers from one subwindows to another

[David REVOY]

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

--- Comment #2 from David REVOY  ---
Here is how I can reproduce and get a consistent crash on git~master and
appimage (Note: Krita needs to be in 'subwindows' mode):

1. Open Krita, Create a new blank document
1. Download
https://www.peppercarrot.com/extras/temp/2015-02-09_philosophy_04-open-source.kra,
open it in same instance of Krita.
2. Window → Tile (to put the two documents side by side)
3. Drag'n'Drop the layer group "2019_refactor" to the canvas of the blank
document.

Here it produces a crash on mouse release. True, it is not happening with a
regular group (with only paint layers in it) I saw it only now too and I
thought it was the case when I reported, sorry about that.

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

[krita] [Bug 408019] Crash after a drag'n'drop of a group of layers from one subwindows to another

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #3 from Boudewijn Rempt  ---
Yes, with that file I can confirm the issue.

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

[clazy] [Bug 408020] New: Suggest to use addRow instead of newRow+sprintf

[Giuseppe D'Angelo]

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

Bug ID: 408020
   Summary: Suggest to use addRow instead of newRow+sprintf
   Product: clazy
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: dange...@gmail.com
CC: smart...@kde.org
  Target Milestone: ---

Data-driven tests with QTest can use either newRow or addRow to add a new
testdata row. Each data row has a unique data-tag used in logs, testrunners
etc.

Sometimes this data-tag is generated procedurally:

  QTest::newRow(qPrintable(QString("Testing %1").arg(foo))) << foo;

However there's a better solution: QTest::addRow, which natively supports
printf syntax:

  QTest::addRow("Testing %d", foo) << foo;

The idea is that this check should see if newRow is being used with qPrintable
/ QString::asprintf / etc. and suggest addRow instead.

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

[clazy] [Bug 408021] New: Warn if code contains the constant 0x9e3779b9 (hand-rolled boost::hash_combine)

[Giuseppe D'Angelo]

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

Bug ID: 408021
   Summary: Warn if code contains the constant 0x9e3779b9
(hand-rolled boost::hash_combine)
   Product: clazy
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: dange...@gmail.com
CC: smart...@kde.org
  Target Milestone: ---

Check if the code contains the constant "0x9e3779b9".

It's VERY likely someone is hand-rolling QtPrivate::QHashCombine /
boost::hash_combine. Suggest to use those instead.

E.g.
https://codereview.qt-project.org/c/qt/qtbase/+/263115/4/src/network/ssl/qsslerror.cpp#b367

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

[krita] [Bug 408022] New: Unstable vector gradient controller on lines with zero width bounding box

[Ahab Greybeard]

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

Bug ID: 408022
   Summary: Unstable vector gradient controller on lines with zero
width bounding box
   Product: krita
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Tools/Vector
  Assignee: krita-bugs-n...@kde.org
  Reporter: ahab.greybe...@hotmail.co.uk
  Target Milestone: ---

SUMMARY
This bug is present in all versions from 4.1.7 to the latest Nightly
krita-4.3.0-prealpha-fc51481-x86_64.appimage   

If a vertical or horizontal vector line is drawn and then selected and its line
stroke style edited in the Tool Options docker and then set to Gradient, the
yellow gradient controller handles appear.
If the yellow end points are moved at all, they suddenly go to infinity.
This can be recovered by selecting a stroke style of Solid.

If a line that is not vertical or horizontal is drawn, it does not have this
bug.
The reason for this (or a related factor) seems to be that the bounding box for
a line initially drawn as vertical or horizontal has a zero width bounding box,
whereas as an initially non vertical/horizontal line has a bounding box of
finite width.
If an intially drawn vertical/horizontal line is rotated, its bounding box is
still zero width and so it still exhibits the bug.
If an intially non-vertical/horizontal line is rotated to be
horizontal/vertical, it still has a finite bounding box width and so does not
exhibit this bug.

STEPS TO REPRODUCE
See Summary

OBSERVED RESULT
See Summary

EXPECTED RESULT
It shouldn't do that.

SOFTWARE/OS VERSIONS
Krita

 Version: 4.3.0-prealpha (git fc51481)
 Languages: en_GB, en
 Hidpi: true

Qt

  Version (compiled): 5.12.2
  Version (loaded): 5.12.2

ADDITIONAL INFORMATION
A workaround for this is to draw a long thin rectangle (instead of a line) and
set its stroke to No Fill and its fill to Gradient.
Another (but crude) workaround is to draw an initially non-vertical/horizontal
line and then to adjust its bounding box to make it apparently 'zero width',
after which it becomes vertical/horizontal and has a well behaved gradient
controller.

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

[krita] [Bug 408023] New: New altered brush presets should keep parent's tags

[bugzilla_noreply]

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

Bug ID: 408023
   Summary: New altered brush presets should keep parent's tags
   Product: krita
   Version: 4.1.7
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: corne...@gmail.com
  Target Milestone: ---

SUMMARY
When adapting an existing brush that has tags assigned to it for proper
management, the new brush will not inherit the old brushes tags. This forces
the user to go through the tedious steps of finding the new brush in the "All"
brushes preset in order to get it back to the tag where it belongs.

STEPS TO REPRODUCE
1. In the Brush Presets Docker, select a tag, then pick a brush.
2. Edit the brush presets (this is not needed to test the behaviour).
3. Click "Save New Brush Preset" and save the brush.

OBSERVED RESULT
Notice the new brush is not automatically added to the tag you are currently
using.

EXPECTED RESULT
It would be much nicer to have the new brush added to the tag you are working
with, as 9 times out of 10, this is where you will want the modification of the
old brush to appear anyway. And if not, then removing the tag from the brush is
faster than having to locate the brush and add the tag. 

In practice, the flow of the process of quickly creating new custom brush
presets on the fly is greatly diminished as every new brush must be hunted down
and herded back to where it belongs. It will take less than 20 seconds but will
feel like hitting an annoying obstacle that interrupts the painting process.

Even better, but no doubt more work to implement, would be having the ability
to see the brush's tags while editing and being able to alter them as part of
the editing process. This would be particularly handy when using brushes in
multiple sets (tags).

SOFTWARE/OS VERSIONS
Windows: windows 10
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9

[Cyp]

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

Cyp  changed:

   What|Removed |Added

 CC||cyp...@gmail.com

--- Comment #23 from Cyp  ---
I'm seeing this with valgrind-3.15.0, even though the release notes say RdRand
is now supported.

The system is compiled with -march=native on an “Intel(R) Core(TM) i7-3770K CPU
@ 3.50GHz”.

--

$ valgrind scribus
==26338== Memcheck, a memory error detector
==26338== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==26338== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info
==26338== Command: scribus
==26338== 
vex amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF0 0xB9 0x1 0x0 0x0 0x0
0x89 0x3
vex amd64->IR:   REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR:   VEX=0 VEX.L=0 VEX.n=0x0 ESC=0F
vex amd64->IR:   PFX.66=0 PFX.F2=0 PFX.F3=0
==26338== valgrind: Unrecognised instruction at address 0x8769603.
==26338==at 0x8769603: _rdrand32_step (immintrin.h:138)
==26338==by 0x8769603: qt_random_cpu (qrandom.cpp:114)
==26338==by 0x8769603: QRandomGenerator::SystemGenerator::generate(unsigned
int*, unsigned int*) (qrandom.cpp:370)
==26338==by 0x87BC11A: fillRange (qrandom.h:143)
==26338==by 0x87BC11A: generate (qrandom.h:87)
==26338==by 0x87BC11A: qt_create_qhash_seed() (qhash.cpp:299)
==26338==by 0x87BC1D4: qt_initialize_qhash_seed (qhash.cpp:325)
==26338==by 0x87BC1D4: qt_initialize_qhash_seed() (qhash.cpp:322)
==26338==by 0x87BC7C9: QHashData::detach_helper(void (*)(QHashData::Node*,
void*), void (*)(QHashData::Node*), int, int) (qhash.cpp:502)
==26338==by 0x87CFDB9: QHash::Node>::detach_helper() [clone .isra.191] (qhash.h:599)
==26338==by 0x87D5FFB: detach (qhash.h:275)
==26338==by 0x87D5FFB: find (qhash.h:901)
==26338==by 0x87D5FFB: take (qcache.h:154)
==26338==by 0x87D5FFB: prepareEngine_helper(QRegExpPrivate*)
(qregexp.cpp:3853)
…

--

http://www.valgrind.org/docs/manual/dist.news.html
Release 3.15.0 (12 April 2019)
* amd64 (x86_64): the RDRAND and F16C insn set extensions are now supported.

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

[krita] [Bug 408024] New: copy paste

[bugzilla_noreply]

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

Bug ID: 408024
   Summary: copy paste
   Product: krita
   Version: 4.1.7
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Tools/Selection
  Assignee: krita-bugs-n...@kde.org
  Reporter: roosa.so...@gmail.com
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. FUCK
2. THIS
3. PROGRAM

OBSERVED RESULT
nothing fucking works

EXPECTED RESULT
I tryed my all to do the simplest thing. but ou boy ou boy you cant copy and
paste or move anything you allredy put down... If u like to animate moveing
hand... welp too bad you have to know how to make it exactly the same without
copy paste or moveing what you allredy put down. FUCK THAT!  

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
this is the first program I have not totaly hated becouse it is simpler to use
then many others. I was planing on just finding it on my own look some videos
to find it... NOTHING! and yes it might be on me for not looking it up 24/7 but
I gave up after 4h. I think program sould be redy to use . wasn't expecting
needing to do research for hours.

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

[krita] [Bug 408024] copy paste

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
 CC||b...@valdyas.org
 Status|REPORTED|RESOLVED

--- Comment #1 from Boudewijn Rempt  ---
This is not a user-feedback forum, but a bug tracker. You have not reported a
bug, therefore I am closing this ticket.

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

[konsole] [Bug 408025] New: Konsole command frozen.

[bugzilla_noreply]

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

Bug ID: 408025
   Summary: Konsole command frozen.
   Product: konsole
   Version: 19.04.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: tgour...@protonmail.ch
  Target Milestone: ---

SUMMARY
For checking for any faults in the system by using the command line: sudo eopkg
check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall
Yields nothing. It asks for password then nothing continues.

STEPS TO REPRODUCE
1. Open Konsole
2. copy & paste sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo
eopkg it --reinstall

OBSERVED RESULT
Nothing

EXPECTED RESULT
Checking / Reparing files

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Solus
(available in About System)
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.58.0
Qt Version: 5.12.3

ADDITIONAL INFORMATION
Command from
https://bugs.kde.org/enter_bug.cgi?format=guided&product=konsole&version=19.04.1

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

[kmymoney] [Bug 408026] New: Crash during CSV import

[Thomas Baumgart]

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

Bug ID: 408026
   Summary: Crash during CSV import
   Product: kmymoney
   Version: 5.0.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: importer
  Assignee: kmymoney-de...@kde.org
  Reporter: tbaumg...@kde.org
  Target Milestone: ---

SUMMARY
When switching CSV profiles KMyMoney may crash during next import

STEPS TO REPRODUCE
1. Import CSV file with profile that contains a number column assignment of
e.g. 6
2. Import CSV file with the same profile where the file only has 3 columns and
re-assign the columns (number not assigned)

OBSERVED RESULT
KMyMoney crashes during import.

EXPECTED RESULT
KMyMoney should import the file w/o crash

ADDITIONAL INFORMATION
The problem is, that the index for the UI is handled correctly, but the column
assignment in the underlying profile still contains the old column assignment
of 6 which produces a value out of bounds.

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

[yakuake] [Bug 377063] yakuake doesn't respect the display scaling when calculating the yakuake window height

[George Moutsopoulos]

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

George Moutsopoulos  changed:

   What|Removed |Added

 CC||gmou...@yahoo.co.uk

--- Comment #7 from George Moutsopoulos  ---
QT_SCREEN_SCALE_FACTORS=1; yakuake
comment https://bugs.kde.org/show_bug.cgi?id=389448#c9

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

[yakuake] [Bug 388217] Yakuake height incorrect if desktop scaling is enabled

[George Moutsopoulos]

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

George Moutsopoulos  changed:

   What|Removed |Added

 CC||gmou...@yahoo.co.uk

--- Comment #5 from George Moutsopoulos  ---
QT_SCREEN_SCALE_FACTORS=1; yakuake
comment https://bugs.kde.org/show_bug.cgi?id=389448#c9

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

[libkgapi] [Bug 408027] New: no more sync from contacts.google.com to kaddressbook

[Philippe ROUBACH]

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

Bug ID: 408027
   Summary: no more sync from contacts.google.com to kaddressbook
   Product: libkgapi
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: contacts
  Assignee: dvra...@kde.org
  Reporter: philippe.roub...@free.fr
  Target Milestone: ---

SUMMARY

no more sync from contacts.google.com to kaddressbook

STEPS TO REPRODUCE
1. add a contact in google contacts android
2. this contact is well added in contacts.google.com
3. 

OBSERVED RESULT

this contact is not added in kaddressbook after one day!

EXPECTED RESULT

this contact is added in kaddressbook

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.58.0
Qt Version: 5.12.3

ADDITIONAL INFORMATION
kde apps 19.04.1
kaddressbook 5.11.1

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

[yakuake] [Bug 389448] Width and height of the window doesn't set correctly on HiDPI screen after upgrade to plasma 5.12

[George Moutsopoulos]

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

George Moutsopoulos  changed:

   What|Removed |Added

 CC||gmou...@yahoo.co.uk

--- Comment #15 from George Moutsopoulos  ---
comment https://bugs.kde.org/show_bug.cgi?id=389448#c9
works for me

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

[kmymoney] [Bug 408026] Crash during CSV import

[Thomas Baumgart]

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

Thomas Baumgart  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kmy
   ||money/09fc41b4b872e0a5ec4ce
   ||2b955f99c04ae975d91
 Status|REPORTED|RESOLVED
   Version Fixed In||5.0.5
 Resolution|--- |FIXED

--- Comment #1 from Thomas Baumgart  ---
Git commit 09fc41b4b872e0a5ec4ce2b955f99c04ae975d91 by Thomas Baumgart.
Committed on 28/05/2019 at 11:52.
Pushed by tbaumgart into branch '5.0'.

Reset column assignment when out of bounds

In case the column assignment is cleared using the clear all button, the
profile is not updated because there is no change in index in combobox
widget and the connected slot for profile update will never be called.

This change makes sure that in such a case (previous assignment is out
of bounds for the current file) the assignment is reset before it is
used. This avoids the out-of-bounds crash later on.
FIXED-IN: 5.0.5

M  +5-0kmymoney/plugins/csv/import/bankingwizardpage.cpp

https://commits.kde.org/kmymoney/09fc41b4b872e0a5ec4ce2b955f99c04ae975d91

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

[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9

[Tom Hughes]

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

--- Comment #24 from Tom Hughes  ---
That's badly written - they are not supported but this bug is resolved by
making valgrind's emulation of the cpuid instruction remove the bit which
claims support for them.

So an application which tests for rdrand before using it will now work but one
which just assumes it can use it will still fail.

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

[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9

[Tom Hughes]

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

--- Comment #25 from Tom Hughes  ---
So actually there is a later commit which does actually implement RDRAND but
only  for AVX2 capable CPUs which yours is not. My other point remains correct,
that we won't advertise RDRAND on any machine where we don't support it.

The reason by the way that we only do it for AVX2 capable CPUs is that we only
support a limited set of CPU profiles and the next one down is:

  Intel(R) Core(TM) i5-2300 CPU @ 2.80GHz

which is not RDRAND capable.

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

[krita] [Bug 408028] New: Objects on Duplicated Vector Layer can't be edited

[Ahab Greybeard]

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

Bug ID: 408028
   Summary: Objects on Duplicated Vector Layer can't be edited
   Product: krita
   Version: nightly build (please specify the git hash!)
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Layers/Vector
  Assignee: krita-bugs-n...@kde.org
  Reporter: ahab.greybe...@hotmail.co.uk
  Target Milestone: ---

SUMMARY
This bug occurs in all versions from 4.1.7 onwards but seems worse in the 4.2.0
pre-alpha appimages and the latest 4.3.0 pre-alpha nightly build.

If a vector layer is Duplicated (not copy/pasted), the duplicated layer objects
can't have their properties edited (in Tool Options, e.g. stroke and fill
style) and if moved, the bounding box is moved but the on-screen image is not
altered. After a Save and Open, this bug no longer happens.

STEPS TO REPRODUCE
See above

OBSERVED RESULT
See above

EXPECTED RESULT
It should be possible to edit selected vector shapes in a duplicated layer.

SOFTWARE/OS VERSIONS
Krita

 Version: 4.3.0-prealpha (git fc51481)
 Languages: en_GB, en
 Hidpi: true

Qt

  Version (compiled): 5.12.2
  Version (loaded): 5.12.2

ADDITIONAL INFORMATION
In 4.1.7, this bug could be cleared by turning off/on both the original and
duplicated layer. Also, in 4.1.7, the vector object could be moved, after which
the bug did not happen.

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

[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9

[Julian Seward]

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

--- Comment #26 from Julian Seward  ---
(In reply to Tom Hughes from comment #25)
> So actually there is a later commit which does actually implement RDRAND but
> only  for AVX2 capable CPUs which yours is not.

I think Mark just fixed it to work on AVX-only capable CPUs too.  See
bug 408009.

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

[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9

[Julian Seward]

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

--- Comment #27 from Julian Seward  ---
That doesn't invalidate Tom's comment though: you should always test
with CPUID at run time for the presence of any particular instruction
set extension, before using it.  Especially for recent or obscure
extensions.

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

[kwin] [Bug 408029] New: Scrolling in evince when window does not have focus does not work (Xinput2-related)

[Ralf Jung]

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

Bug ID: 408029
   Summary: Scrolling in evince when window does not have focus
does not work (Xinput2-related)
   Product: kwin
   Version: 5.14.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: p...@ralfj.de
  Target Milestone: ---

SUMMARY
When scrolling in an evince window that does not have focus, nothing happens.

STEPS TO REPRODUCE
1. Open evince, make it cover half the screen.
2. Put some other window on the other half and give it focus.
3. Hover the mouse over the evince window without clicking, and turn the scroll
wheel.

OBSERVED RESULT
Nothing happens.


EXPECTED RESULT
It should scroll.

SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux 10
KDE Plasma Version: 5.14.5
Qt Version: 5.11.3
KDE Frameworks Version: 5.54.0
Kernel Version: 4.19.0-5-amd64
OS Type: 64-bit

ADDITIONAL INFORMATION
First reported against evince/GTK at
https://gitlab.gnome.org/GNOME/gtk/issues/949. However, after discovering that
setting GDK_CORE_DEVICE_EVENTS=1 in the environment works around the issue,
they concluded that this has something to do with KWin not supporting Xinput2
(?).

Curiously, when I use two-finger scrolling on my touchpad to scroll, evince
*does* scroll properly. It's only mouse wheel scrolling that gets "lost", and
only when the evince window does not have focus.

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

[kwin] [Bug 385522] Present Windows: Don't darken all windows and denote selection some other way than restoring original lightness

[Saverio Brancaccio]

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

--- Comment #35 from Saverio Brancaccio  ---
Considering the number of votes (only 2 since 2017) on this issue, I suppose
it's not an interesting feature to fix. 
Therefore, I reported a suggestion on a 3rd party site to have at least an
extension that performs the function in subject:
https://github.com/Zren/plasma-applet-presentwindows
The author is the same of the video I already reported here in a previous
message: 
https://www.youtube.com/watch?v=QEHC43zMIMc

Regards.

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

[krita] [Bug 408028] Objects on Duplicated Vector Layer can't be edited

[bugzilla_noreply]

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

tus...@vista.aero changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 CC||tus...@vista.aero
 Ever confirmed|0   |1

--- Comment #1 from tus...@vista.aero ---
Can confirm this on master.

PS: "Duplicate" means "Duplicate Layer or Mask" in the layers docker context
menu.

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

[kwin] [Bug 385522] Present Windows: Don't darken all windows and denote selection some other way than restoring original lightness

[Kishore Gopalakrishnan]

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

--- Comment #36 from Kishore Gopalakrishnan  ---
(In reply to Saverio Brancaccio from comment #35)
> Considering the number of votes (only 2 since 2017) on this issue, I suppose
> it's not an interesting feature to fix. 
> Therefore, I reported a suggestion on a 3rd party site to have at least an
> extension that performs the function in subject:
> https://github.com/Zren/plasma-applet-presentwindows
> The author is the same of the video I already reported here in a previous
> message: 
> https://www.youtube.com/watch?v=QEHC43zMIMc
> 
> Regards.

As far as I understand, that extension doesn't do anything about the dimming.
It just adds a button to trigger the 'Present Windows' shortcut.

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

[lattedock] [Bug 399149] Wine application with latte-dock master and plasma 5.14 beta always uses cpu

[Alexandre Pereira]

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

--- Comment #69 from Alexandre Pereira  ---
(In reply to Michail Vourlakos from comment #68)
> (In reply to Alexandre Pereira from comment #67)
> > (In reply to Michail Vourlakos from comment #66)
> >
> 
> is it possible to test again with latest master?
> I have just made a commit that could reduce cpu usage from windows tracking
> vastly

Hi,

I just tried it, before with latest "release version" ( on archlinux ) and then
using the aur git package: same results.

Still, using latte-dock with a kwin rules using the title as rule, will make
latte-dock use about 5% cpu for each window ( in this case i tested with 3
windows, so about 15% cpu usage ).

Removing kwin rule bounded by title ( but still with rules inforced, but only
by class and executable ) made latte-dock go to 0-1% cpu usage.

Strange is, kwin rule by title with a window that is constantly changing
titles, makes latte-dock high cpu usage, but not plasmashell.

I have been using latte-dock with this workaround: renamed the wine executables
and then made rules based on the executables name ( and not make any
specification about the titles in the rules ).

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

[krita] [Bug 408028] Objects on Duplicated Vector Layer can't be edited

[bugzilla_noreply]

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

--- Comment #2 from tus...@vista.aero ---
(In reply to tusooa from comment #1)
> Can confirm this on master.
> 
> PS: "Duplicate" means "Duplicate Layer or Mask" in the layers docker context
> menu.

Update: the display problem will disappear after some time, but movements
afterwards
will still trigger the display problem.

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

[plasmashell] [Bug 404594] Plasma crash when opening calendar from panel

[apache]

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

--- Comment #4 from apache  ---
During Manjaro update I have this errors:

kholidays: /usr/include/KF5/KHolidays/KHolidays/AstroSeasons is in file system
kholidays: /usr/include/KF5/KHolidays/KHolidays/Holiday is in file system
kholidays: /usr/include/KF5/KHolidays/KHolidays/HolidayRegion is in file system
kholidays: /usr/include/KF5/KHolidays/KHolidays/LunarPhase is in file system
kholidays: /usr/include/KF5/KHolidays/KHolidays/SunRiseSet is in file system
kholidays: /usr/include/KF5/KHolidays/KHolidays/Zodiac is in file system
kholidays: /usr/include/KF5/KHolidays/kholidays/astroseasons.h is in file
system
kholidays: /usr/include/KF5/KHolidays/kholidays/holiday.h is in file system
kholidays: /usr/include/KF5/KHolidays/kholidays/holidayregion.h is in file
system
kholidays: /usr/include/KF5/KHolidays/kholidays/kholidays_export.h is in file
system
kholidays: /usr/include/KF5/KHolidays/kholidays/lunarphase.h is in file system
kholidays: /usr/include/KF5/KHolidays/kholidays/sunriseset.h is in file system
kholidays: /usr/include/KF5/KHolidays/kholidays/zodiac.h is in file system
kholidays: /usr/include/KF5/kholidays_version.h is in file system
kholidays: /usr/lib/cmake/KF5Holidays/KF5HolidaysConfig.cmake is in file system
kholidays: /usr/lib/cmake/KF5Holidays/KF5HolidaysConfigVersion.cmake is in file
system
kholidays: /usr/lib/cmake/KF5Holidays/KF5HolidaysQchTargets.cmake is in file
system
kholidays: /usr/lib/cmake/KF5Holidays/KF5HolidaysTargets-noconfig.cmake is in
file system
kholidays: /usr/lib/cmake/KF5Holidays/KF5HolidaysTargets.cmake is in file
system
kholidays: /usr/lib/libKF5Holidays.so is in file system
kholidays: /usr/lib/libKF5Holidays.so.5 is in file system
kholidays: /usr/lib/qt/mkspecs/modules/qt_KHolidays.pri is in file system
kholidays: /usr/lib/qt/qml/org/kde/kholidays/libkholidaysdeclarativeplugin.so
is in file system
kholidays: /usr/lib/qt/qml/org/kde/kholidays/qmldir is in file system
kholidays: /usr/share/doc/qt/KF5Holidays.qch is in file system
kholidays: /usr/share/doc/qt/KF5Holidays.tags is in file system
kholidays: /usr/share/locale/ar/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/be/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/bg/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/br/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/bs/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/ca/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/ca@valencia/LC_MESSAGES/libkholidays5_qt.qm is in
file system
kholidays: /usr/share/locale/cs/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/cy/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/da/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/de/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/el/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/en_GB/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/eo/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/es/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/et/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/eu/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/fa/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/fi/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/fr/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/fy/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/ga/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/gl/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/he/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/hi/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/hne/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/hu/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/ia/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/id/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/is/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/it/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/ja/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/kk/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/km/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays: /usr/share/locale/ko/LC_MESSAGES/libkholidays5_qt.qm is in file
system
kholidays:

[yakuake] [Bug 377063] yakuake doesn't respect the display scaling when calculating the yakuake window height

[Ariel Rosenfeld]

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

Ariel Rosenfeld  changed:

   What|Removed |Added

 CC||ariel.rosenfeld.750@gmail.c
   ||om

--- Comment #8 from Ariel Rosenfeld  ---
(In reply to George Moutsopoulos from comment #7)
> QT_SCREEN_SCALE_FACTORS=1; yakuake
> comment https://bugs.kde.org/show_bug.cgi?id=389448#c9

I can confirm the fix works

The QT documentation states that QT_SCREEN_SCALE_FACTORS should not be used as
they bypass edid detection

QT_AUTO_SCREEN_SCALE_FACTOR and QT_SCALE_FACTOR are the correct variables for
HIDPI but unfortunately they are disabled in startkde which also sets the
scaling to the manual set scaling in the display scaling configuration

so to summarize i changed the veriable

QT_SCREEN_SCALE_FACTORS="DVI-I-0=1.2;DVI-I-1=1.2;DP-0=1.2;DP-1=1.2;DP-2=1.2;DP-3=1.2;HDMI-0=1.2;DP-4=1.2;DP-5=1.2;"

to 

QT_SCREEN_SCALE_FACTORS="1"

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

[lattedock] [Bug 399149] Wine application with latte-dock master and plasma 5.14 beta always uses cpu

[Michail Vourlakos]

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

--- Comment #70 from Michail Vourlakos  ---
(In reply to Alexandre Pereira from comment #69)
> (In reply to Michail Vourlakos from comment #68)
> > (In reply to Alexandre Pereira from comment #67)
> > > (In reply to Michail Vourlakos from comment #66)
> > >
> > 
> > is it possible to test again with latest master?
> > I have just made a commit that could reduce cpu usage from windows tracking
> > vastly
> 
> Hi,
> 
> I just tried it, before with latest "release version" ( on archlinux ) and
> then using the aur git package: same results.
> 
> Still, using latte-dock with a kwin rules using the title as rule, will make
> latte-dock use about 5% cpu for each window ( in this case i tested with 3
> windows, so about 15% cpu usage ).
> 
> Removing kwin rule bounded by title ( but still with rules inforced, but
> only by class and executable ) made latte-dock go to 0-1% cpu usage.
> 
> Strange is, kwin rule by title with a window that is constantly changing
> titles, makes latte-dock high cpu usage, but not plasmashell.
> 
> I have been using latte-dock with this workaround: renamed the wine
> executables and then made rules based on the executables name ( and not make
> any specification about the titles in the rules ).

are you sure that the AUR git version is containing yesterday commits?

https://phabricator.kde.org/source/latte-dock/history/master/

because in this commit there is a fix for batch kwin signaling for window title
changes...

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

[plasmashell] [Bug 407701] Most apps end up in "System Services" category

[Ilya Bizyaev]

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

--- Comment #3 from Ilya Bizyaev  ---
I use Firefox from openSUSE's mozilla repository:
https://build.opensuse.org/project/show/mozilla

My plasmanotifyrc has these contents:
```
[Applications][telegramdesktop]
Seen=true

[DoNotDisturb]
Until=2019,5,21,23,28,0
```

I indeed don't seem to have other non-KDE apps that are configured to send
notifications, so if notifyrc files are fixed then it's ok.

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

[neon] [Bug 407941] Unable to make the service... executable, aborting execution trying to run AppImage

[Nate Graham]

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

--- Comment #2 from Nate Graham  ---
Are you sure this could be related to the Neon packaging? Seems more like a
code issue TBH.

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

[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9

[Tom Hughes]

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

--- Comment #28 from Tom Hughes  ---
That latest change isn't actually committed yet ;-)

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

[kwin] [Bug 385522] Present Windows: Don't darken all windows and denote selection some other way than restoring original lightness

[pemartins]

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

--- Comment #37 from pemartins  ---
Some points for consideration:
1. This issue exists since it was implemented, 6 years ago or whatever. I have
no idea how the dimness was implemented in the first place because it's
obviously a bad job, it's worst than finding Waldo:
https://i.imgur.com/cARsxD7.jpg
2. This issue can be fixed faster than it takes to type any of the posts in
this thread, change the 0.3 to 0.9 and it's done. Nevertheless it's been going
on for years.
3. It was mentioned that this only had a couple of votes or something. It
literally takes longer to count that couple of votes than to change a 3 to a 9.
4. A fix for this issue was posted some time ago. A good fix as shown on
comments 14 and 27 above.
5. How are we still talking about this?

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

[plasmashell] [Bug 387590] Contradicting touchpad enabled/disabled notification after mouse plugged in and out quickly

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[KEXI] [Bug 408012] Editing number of allowable characters in any field cell leads to deletion of all data in table

[Jarosław Staniek]

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

Jarosław Staniek  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 OS|Linux   |All
 Status|REPORTED|CONFIRMED
 CC||stan...@kde.org

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

[kwin] [Bug 385522] Present Windows: Don't darken all windows and denote selection some other way than restoring original lightness

[hvm]

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

--- Comment #38 from hvm  ---
(In reply to pemartins from comment #37)
> Some points for consideration:
> 1. This issue exists since it was implemented, 6 years ago or whatever. I
> have no idea how the dimness was implemented in the first place because it's
> obviously a bad job, it's worst than finding Waldo:
> https://i.imgur.com/cARsxD7.jpg
> 2. This issue can be fixed faster than it takes to type any of the posts in
> this thread, change the 0.3 to 0.9 and it's done. Nevertheless it's been
> going on for years.
> 3. It was mentioned that this only had a couple of votes or something. It
> literally takes longer to count that couple of votes than to change a 3 to a
> 9.
> 4. A fix for this issue was posted some time ago. A good fix as shown on
> comments 14 and 27 above.
> 5. How are we still talking about this?

Exactly. All good points and I'd also like to add that this is the kind of
issue where it's difficult to figure out what is even wrong. 

I've been using KDE since the 2000s and I've never realised why I never really
used the present windows feature, not until recently when I thought about it
with my more recent experience in UX.

My point is that the amount of votes or whatever (I don't even know how you
vote) is not necessarily relevant to how needed the change is.

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

[KEXI] [Bug 408012] Editing Max Length property of table field requires data removal

[Jarosław Staniek]

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

Jarosław Staniek  changed:

   What|Removed |Added

Summary|Editing number of allowable |Editing Max Length property
   |characters in any field |of table field requires
   |cell leads to deletion of   |data removal
   |all data in table   |

--- Comment #1 from Jarosław Staniek  ---
Confirmed, thanks. 

Manual workaround for any KEXI version:

1. Close your KEXI database and back up it.
2. Open the sqliteman app or equivalent one. 
Note: You can do the same with sqlite3 console app if you have skills. You can
do the same with MySQL Admin or PostgreSQL Admin for server KEXI databases.
3. For given table T run this query to find out its id: select o_id from
kexi__objects where o_name='T'. Note down the o_id number.
4. For that o_id value (e.g. 217) and for given length (e.g. 1000) and field
name (e.g. 'c') run this query: update kexi__fields set f_length=1000 where
t_id=217 and f_name='c'
5. Repeat steps 3 and 4 for any number of tables and fields you need. You can
use skip the "and f_name='c'" part of the query to set all fields in the table
to give length.
Note: This operation does not truncate or extend length of actual data, you
need to do that separately using other queries. This makes implementation of
the task more complex than it looks: actual data modification may be needed.

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

[KEXI] [Bug 408012] Editing Max Length property of table field requires data removal

[Jarosław Staniek]

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

Jarosław Staniek  changed:

   What|Removed |Added

URL||https://phabricator.kde.org
   ||/T10999

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

[plasmashell] [Bug 408030] New: Plasma crash after supend/resume to other screen setup

[Klaus Vink Slott]

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

Bug ID: 408030
   Summary: Plasma crash after supend/resume to other screen setup
   Product: plasmashell
   Version: 5.8.7
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: kl...@vink-slott.dk
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.7)

Qt Version: 5.6.2
Frameworks Version: 5.32.0
Operating System: Linux 4.4.179-99-default x86_64
Distribution: "openSUSE Leap 42.3"

-- Information about the crash:
- What I was doing when the application crashed:
Suspended my labtop in dock with 2 monitors connected. Undocked and resumed
with only laptop screen.

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

Thread 17 (Thread 0x7fc6c37ff700 (LWP 16490)):
#0  0x7fc7aa27230d in poll () at /lib64/libc.so.6
#1  0x7fc79fedb081 in  () at /usr/lib64/libpulse.so.0
#2  0x7fc79fecc74c in pa_mainloop_poll () at /usr/lib64/libpulse.so.0
#3  0x7fc79feccdbe in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0
#4  0x7fc79fecce70 in pa_mainloop_run () at /usr/lib64/libpulse.so.0
#5  0x7fc79fedafe6 in  () at /usr/lib64/libpulse.so.0
#6  0x7fc79f8733f8 in  () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so
#7  0x7fc7a9a78724 in start_thread () at /lib64/libpthread.so.0
#8  0x7fc7aa27ae8d in clone () at /lib64/libc.so.6

Thread 16 (Thread 0x7fc6d7ffe700 (LWP 16399)):
#0  0x7fc7aa27230d in poll () at /lib64/libc.so.6
#1  0x7fc7a6922314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fc7a692242c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fc7aab7f16b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fc7aab2cbbb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fc7aa967f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fc7adc613d8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fc7aa96c9e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fc7a9a78724 in start_thread () at /lib64/libpthread.so.0
#9  0x7fc7aa27ae8d in clone () at /lib64/libc.so.6

Thread 15 (Thread 0x7fc6c9568700 (LWP 16377)):
#0  0x7fc7a9a7d0ff in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc7aa96d65b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fc6efbe042f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7fc6efbe3dea in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7fc6efbde45b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7fc6efbe3e32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7fc6efbde45b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7fc6efbe3e32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7fc6efbde45b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7fc6efbe3e32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#10 0x7fc6efbde45b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#11 0x7fc6efbe3e32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#12 0x7fc6efbde45b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#13 0x7fc6efbe3e32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#14 0x7fc6efbde45b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#15 0x7fc6efbe3e32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#16 0x7fc6efbde45b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#17 0x7fc6efbe3e32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#18 0x7fc6efbde45b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#19 0x7fc6efbe1a46 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#20 0x7fc7aa96c9e9 in  () at /usr/lib64/libQt5Core.so.5
#21 0x7fc7a9a78724 in start_thread () at /lib64/libpthread.so.0
#22 0x7fc7aa27ae8d in clone () at /lib64/libc.so.6

Thread 14 (Thread 0x7fc6c9d69700 (LWP 16376)):
#0  0x7fc7a9a7d0ff in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc7aa96d65b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5

[frameworks-knotifications] [Bug 408031] New: Plasma 5.16 Notifications - Button hover tooltip shows erroneous ampersand

[Eric Adams]

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

Bug ID: 408031
   Summary: Plasma 5.16 Notifications - Button hover tooltip shows
erroneous ampersand
   Product: frameworks-knotifications
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: esa1...@gmail.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

Created attachment 120357
  --> https://bugs.kde.org/attachment.cgi?id=120357&action=edit
Screenshot showing the tooltip with ampersand present

SUMMARY
The tooltip shown when hovering over the notifications settings button from the
system tray begins with an ampersand. See attached screenshot.

STEPS TO REPRODUCE
1. Click arrow to show full tray
2. Click Notifications
3. Hover over the settings icon to the right

OBSERVED RESULT
Tooltip shows an ampersand character

EXPECTED RESULT
Ampersand is not present in tooltip text

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 19.10
KDE Plasma Version: 5.15.90
KDE Frameworks Version: 5.58.0
Qt Version: 5.12.2
Kernel Version: 5.0.0-15-generic
OS Type: 64-bit
Processors: 12 × Intel® Core™ i7-8750H CPU @ 2.20GHz
Memory: 15.3 GiB of RAM 

ADDITIONAL INFORMATION
See attached screenshot.

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

[plasmashell] [Bug 387590] Contradicting touchpad enabled/disabled notification after mouse plugged in and out quickly

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

   Version Fixed In||5.16.0
  Latest Commit||https://commits.kde.org/pla
   ||sma-desktop/999b619bc5c87c4
   ||c0a08f97e3e422562b5f72fff
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Kai Uwe Broulik  ---
Git commit 999b619bc5c87c4c0a08f97e3e422562b5f72fff by Kai Uwe Broulik.
Committed on 28/05/2019 at 14:05.
Pushed by broulik into branch 'Plasma/5.16'.

[Touchpad KCM] Revoke touchpad enabled/disabled notification before sending a
new one
FIXED-IN: 5.16.0

Differential Revision: https://phabricator.kde.org/D21439

M  +5-1kcms/touchpad/src/kded/kded.cpp
M  +4-0kcms/touchpad/src/kded/kded.h

https://commits.kde.org/plasma-desktop/999b619bc5c87c4c0a08f97e3e422562b5f72fff

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

[krita] [Bug 408032] New: [duplicate layer] Krita can't move or transform right after duplicating a layer.

[David REVOY]

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

Bug ID: 408032
   Summary: [duplicate layer] Krita can't move or transform right
after duplicating a layer.
   Product: krita
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Layer Stack
  Assignee: krita-bugs-n...@kde.org
  Reporter: i...@davidrevoy.com
  Target Milestone: ---

Hi,

Krita can't move or transform right after duplicating a layer (Ctrl+J). This
bug makes it difficult to duplicate quickly a painted part of the picture
(flowers, snow flake, textures patch) and duplicate/move it around. 

Step to reproduce:
==
1. Open a new document, create a empty paint layer.
2. Paint a medium-sized dot on it.
3. Switch to the move tool (shortcut: T).
4. Duplicate your layer (Ctrl+J)
5. Try to move the new dot immediately.

Result:
===
Krita does nothing, if you repeat the drag action on canvas three times, it
will work at the third or fourth time. But it might be a timer, because it
works after waiting four good seconds too.

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

[plasmashell] [Bug 407701] Most apps end up in "System Services" category

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #4 from Nate Graham  ---
Yep, this is effectively fixed as of the next versions of all our apps.

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

[calligrawords] [Bug 408033] New: [Feature request] Show word count for selected words

[Thiago Sueto]

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

Bug ID: 408033
   Summary: [Feature request] Show word count for selected words
   Product: calligrawords
   Version: 3.1.0
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: usability
  Assignee: calligra-words-bugs-n...@kde.org
  Reporter: herzensch...@gmail.com
  Target Milestone: ---

Calligra doesn't show word count dynamically, that is, it doesn't display the
amount of selected words.
It could be shown in the status bar or on the statistics docker.

This is a critical feature for translators, editors and proofreaders, e.g. word
counting is the first step for stipulating the price for a document and its
respective service, and the correct size for certain document elements.

The total number of words in a document is not sufficient for various use-cases
in those fields. For instance, in my use-case, since I work with academic
articles, I need to be able to easily count words in the abstract, and since
references aren't always revised, in such cases I need to select all pertinent
text before the references in order to properly count the total amount of words
according to the service I provide, possibly even including parts of the text
that come after the references as well.

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

[kate] [Bug 285396] installation driver nvidia (nvidia.fr)

[Luis Antonio Fessel]

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

Luis Antonio Fessel  changed:

   What|Removed |Added

 CC||luis_fes...@yahoo.com.br

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

[kate] [Bug 285396] installation driver nvidia (nvidia.fr)

[Luis Antonio Fessel]

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

--- Comment #2 from Luis Antonio Fessel  ---
Created attachment 120358
  --> https://bugs.kde.org/attachment.cgi?id=120358&action=edit
File created by the KDE error system

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

[kate] [Bug 285396] installation driver nvidia (nvidia.fr)

[Luis Antonio Fessel]

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

Luis Antonio Fessel  changed:

   What|Removed |Added

 Status|RESOLVED|REPORTED
 Resolution|INTENTIONAL |---

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

[KDE Config Driver Manager] [Bug 285396] installation driver nvidia (nvidia.fr)

[Luis Antonio Fessel]

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

Luis Antonio Fessel  changed:

   What|Removed |Added

Product|kate|KDE Config Driver Manager
   Assignee|kwrite-bugs-n...@kde.org|sit...@kde.org
  Component|general |general

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

[Breeze] [Bug 407527] Breeze icons needed for kcachegrind, kxstitch, knights, and smb4k

[Jonathan Riddell]

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

--- Comment #7 from Jonathan Riddell  ---
Kigo too 
https://commits.kde.org/breeze-icons/bbad25f74061a00214bdff52ea84d0b1cb6fe650

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

[kwin] [Bug 385522] Present Windows: Don't darken all windows and denote selection some other way than restoring original lightness

[Saverio Brancaccio]

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

--- Comment #39 from Saverio Brancaccio  ---

(In reply to pemartins from comment #37)
> Some points for consideration:
> 1. This issue exists since it was implemented, 6 years ago or whatever. I
> have no idea how the dimness was implemented in the first place because it's
> obviously a bad job, it's worst than finding Waldo:
> https://i.imgur.com/cARsxD7.jpg
> 2. This issue can be fixed faster than it takes to type any of the posts in
> this thread, change the 0.3 to 0.9 and it's done. Nevertheless it's been
> going on for years.
> 3. It was mentioned that this only had a couple of votes or something. It
> literally takes longer to count that couple of votes than to change a 3 to a
> 9.
> 4. A fix for this issue was posted some time ago. A good fix as shown on
> comments 14 and 27 above.
> 5. How are we still talking about this?

At this point, 
1) what is the meaning of the votes on bugs here?
2) Solving this bug making tweakings in a text config file like kwinrc is not
an acceptable solution for a normal user of a GUI system like KDE. Other Kwin
effects have a GUI setting, introducing a GUI setting also for PresentWindows
effect is a correct way to solve the bug from a system integration point of
view.

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

[kile] [Bug 408034] New: Block comment introduces # instead of %

[Juan González García]

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

Bug ID: 408034
   Summary: Block comment introduces # instead of %
   Product: kile
   Version: 2.9.92
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: editor
  Assignee: michel.lud...@kdemail.net
  Reporter: jgonzalezgarc.i...@aragon.es
  Target Milestone: ---

SUMMARY

When commenting a block of source using default Ctrl+D, Kile 2.9.91 on Linux
Lite introduces # characters instead of % characters.

STEPS TO REPRODUCE
1. Introduce some Latex code
2. Select a block and press Ctrl+D

OBSERVED RESULT

# characters are introduced as comment character instead of %
EXPECTED RESULT


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Linux Lite 4.4 - XFCE
(available in About System)
KDE Plasma Version: - 
KDE Frameworks Version: 5.44.0
Qt Version: 5.9.5

ADDITIONAL INFORMATION

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

[okular] [Bug 408011] Running Okular on LinuxMint 19.1 Cinnamon Printer Properties Paper Size will not print 'Letter' but reverts to 'A4' when trying to print documents. Landscape setting works though

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org
 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Nate Graham  ---
This was fixed in a later version. The one provided by Linux Mint is very old.

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

[kwin] [Bug 408035] New: Plastik decoration theme doesn't react to border size changes

[Vlad Zagorodniy]

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

Bug ID: 408035
   Summary: Plastik decoration theme doesn't react to border size
changes
   Product: kwin
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: aurorae
  Assignee: kwin-bugs-n...@kde.org
  Reporter: vladz...@gmail.com
  Target Milestone: ---

The title is self-explanatory.

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

[kwin] [Bug 408035] Plastik decoration theme doesn't react to border size changes

[Vlad Zagorodniy]

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

Vlad Zagorodniy  changed:

   What|Removed |Added

  Flags||ReviewRequest+
 Status|REPORTED|CONFIRMED
URL||https://phabricator.kde.org
   ||/D21462
 Ever confirmed|0   |1

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

[okular] [Bug 407998] Okular scales down pages when printing

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO
 CC||n...@kde.org

--- Comment #1 from Nate Graham  ---
What version of Okular are you using? 1.7.x has a scale mode chooser under the
"PDF Options" tab in the print dialog.

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

[neon] [Bug 407986] Update hotspot to version 1.2

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[krunner] [Bug 407994] KRunner calc does not work with small numbers

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||n...@kde.org
 Status|REPORTED|RESOLVED

--- Comment #1 from Nate Graham  ---


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

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

[krunner] [Bug 406384] AppStream runner reduces KRunner performance and causes calculator runner to not show any results approximately 60% of the time

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||noga.d...@gmail.com

--- Comment #10 from Nate Graham  ---
*** Bug 407994 has been marked as a duplicate of this bug. ***

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

[Qt/KDE Flatpak Runtime] [Bug 408010] kbuildsycoca5 doesn't ever rebuild in Flatpak

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[kwin] [Bug 408036] New: Plastik doesn't unset resize borders for maximized clients

[Vlad Zagorodniy]

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

Bug ID: 408036
   Summary: Plastik doesn't unset resize borders for maximized
clients
   Product: kwin
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: aurorae
  Assignee: kwin-bugs-n...@kde.org
  Reporter: vladz...@gmail.com
  Target Milestone: ---

The title is self-explanatory.

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

[KEXI] [Bug 408012] Editing Max Length property of table field requires data removal

[Jarosław Staniek]

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

--- Comment #2 from Jarosław Staniek  ---
"DB Browser for SQLite" also works for the above workaround:
https://sqlitebrowser.org/dl/

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

[kwin] [Bug 408036] Plastik doesn't unset resize borders for maximized clients

[Vlad Zagorodniy]

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

Vlad Zagorodniy  changed:

   What|Removed |Added

 Ever confirmed|0   |1
URL||https://phabricator.kde.org
   ||/D21462
 Status|REPORTED|CONFIRMED
  Flags||ReviewRequest+

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

[frameworks-baloo] [Bug 389848] baloo_file crashes in mdb_put() in LMDB

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||plasmapel...@yahoo.co.uk

--- Comment #84 from Nate Graham  ---
*** Bug 408008 has been marked as a duplicate of this bug. ***

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

[frameworks-baloo] [Bug 408008] baloo_file_extractor crashes on login

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED
 CC||n...@kde.org

--- Comment #1 from Nate Graham  ---


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

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

[Discover] [Bug 407636] New Home Button does not behave like a button

[Björn Feber]

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

Björn Feber  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/dis
   ||cover/66f3bec028254c3551a98
   ||d9d7933e9269b361611
   Version Fixed In||5.16.0

--- Comment #2 from Björn Feber  ---
Git commit 66f3bec028254c3551a98d9d7933e9269b361611 by Björn Feber.
Committed on 28/05/2019 at 15:03.
Pushed by bfeber into branch 'Plasma/5.16'.

Use onClicked for Home button

Summary:
FIXED-IN: 5.16.0

Buttons should use onClicked instead of onPressed.

Test Plan: Click on the Home button. It now behaves correctly.

Reviewers: #plasma, #vdg, ngraham, apol

Reviewed By: #vdg, ngraham, apol

Subscribers: ngraham, #vdg, plasma-devel, #plasma

Tags: #plasma

Differential Revision: https://phabricator.kde.org/D21436

M  +1-1discover/qml/DiscoverDrawer.qml

https://commits.kde.org/discover/66f3bec028254c3551a98d9d7933e9269b361611

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

[gwenview] [Bug 408005] gwenview does not open (all) GeoTIFFs

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

--- Comment #1 from Nate Graham  ---
9 MB is above the attachment size limit anyway, but feel free to post a link to
a location where it can be found.

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

[frameworks-kdeclarative] [Bug 407999] Fragile comparison to i18n("None")

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 CC||n...@kde.org
 Ever confirmed|0   |1

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

[Breeze] [Bug 407527] Breeze icons needed for kcachegrind, kxstitch, knights, and smb4k

[Jonathan Riddell]

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

--- Comment #8 from Jonathan Riddell  ---
kfourinline
https://commits.kde.org/breeze-icons/25aeb1f8e91ea50f0033481396ca3fe1b496610c

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

[kwin] [Bug 408029] Scrolling in evince when window does not have focus does not work (Xinput2-related)

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

--- Comment #1 from Nate Graham  ---
Are you using Libinput as your input driver?

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

[konsole] [Bug 408025] Konsole command frozen.

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||n...@kde.org
 Resolution|--- |NOT A BUG

--- Comment #1 from Nate Graham  ---
This is a problem with the command itself, not Konsole.

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

[frameworks-baloo] [Bug 408018] Application: Baloo File Extractor (baloo_file_extractor), signal: Aborted

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org
 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Nate Graham  ---


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

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

[frameworks-baloo] [Bug 389848] baloo_file crashes in mdb_put() in LMDB

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||guy.car...@gmail.com

--- Comment #85 from Nate Graham  ---
*** Bug 408018 has been marked as a duplicate of this bug. ***

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

[kmplot] [Bug 407980] kmplot expression editor with constants does not scale after setting higher value in force font dpi in system settings

[Yuri Chornoivan]

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

Yuri Chornoivan  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kmp
   ||lot/95f701c92c17b2c7d6da2b1
   ||76ba7129514b08322
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Yuri Chornoivan  ---
Git commit 95f701c92c17b2c7d6da2b176ba7129514b08322 by Yuri Chornoivan.
Committed on 28/05/2019 at 15:13.
Pushed by yurchor into branch 'Applications/19.04'.

Use layouts for QDialogs to make KmPlot adopt the sizes

Summary:
As it was pointed out "KDialog had its own layout, and when porting to QDialog,
a layout needs to be added"

Test Plan:
1. Open KmPlot, choose "Catesian Plot".
2. Enter something (e.g. "x^2").
3. Click on the Equation Editor button at the right of the input field.
4. Try to resize the window (all interface items are movable now).
5. Press the Constant Editor button.
6. Try to resize the window (all interface items are movable now).
7. Close the windows.
8. Try to choose any item from the "Tools" menu.
9. Try to resize the window (all interface items should be movable).

Reviewers: #kde_edu, cfeck

Reviewed By: cfeck

Subscribers: kde-edu

Tags: #kde_edu

Differential Revision: https://phabricator.kde.org/D21428

M  +2-3kmplot/calculator.cpp
M  +3-1kmplot/equationeditor.cpp
M  +3-4kmplot/functiontools.cpp
M  +3-1kmplot/kconstanteditor.cpp
M  +1-1kmplot/kgradientdialog.cpp
M  +3-5kmplot/ksliderwindow.cpp
M  +4-1kmplot/parameteranimator.cpp

https://commits.kde.org/kmplot/95f701c92c17b2c7d6da2b176ba7129514b08322

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

[kwin] [Bug 408029] Scrolling in evince when window does not have focus does not work (Xinput2-related)

[Ralf Jung]

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

--- Comment #2 from Ralf Jung  ---
How do I figure that out?  I think I left most everything at the default value.

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

[kwin] [Bug 408029] Scrolling in evince when window does not have focus does not work (Xinput2-related)

[Nate Graham]

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

--- Comment #3 from Nate Graham  ---
just search for whether or not Libinput is installed. That should be enough.

apt search libinput | grep -i installed

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

[Discover] [Bug 408037] New: Discover checks for updates before installing local package

[Thiago Sueto]

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

Bug ID: 408037
   Summary: Discover checks for updates before installing local
package
   Product: Discover
   Version: 5.15.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: lei...@leinir.dk
  Reporter: herzensch...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

SUMMARY
When double-clicking e.g. a .deb file and Qapt, Synaptic, Muon or any other
package manager application are not installed, Discover is used to install the
package.

However, Discover's current behavior (as of 5.15.4) is to check for updates
first when opened, regardless of the way it is run.

This delays the installation of local packages, and depending on the internet
connection, number of updates or simply a slow computer, this delay can be
quite considerable.
I don't know if it's necessary to update the package database for installing
local packages? 

Wouldn't it be possible to disable this check for updates whenever a local
package is detected, and to start the check afterwards only in the case the
user clicks on Applications or the update section?

Or perhaps add a toggle for whether or not Discover checks for updates when
it's run, and keep its default behavior.

STEPS TO REPRODUCE
1. Open a local package using Discover;
2. Click Install before Discover finishes checking for updates; 

OBSERVED RESULT
Discover will check for updates first, and only after being finished will it
ask for the user password using a KAuth window after the user clicks Install.

EXPECTED RESULT
Discover does not check for updates first, allowing to ask for the user
password using a KAuth window soon after running Discover and clicking Install.

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 19.04
KDE Plasma Version: 5.15.4
KDE Frameworks Version: 5.56.0
Qt Version: 5.12.2
Kernel Version: 5.0.0-15-generic
OS Type: 64-bit

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

[kwin] [Bug 408029] Scrolling in evince when window does not have focus does not work (Xinput2-related)

[Ralf Jung]

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

--- Comment #4 from Ralf Jung  ---
Looks like it is:

libinput-bin/testing,unstable,now 1.12.6-2 amd64 [installed,automatic]
libinput10/testing,unstable,now 1.12.6-2 amd64 [installed,automatic]
xserver-xorg-input-libinput/testing,unstable,now 0.28.2-2 amd64
[installed,automatic]

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

[kmail2] [Bug 407685] Tries to use http proxy for imap

[Jonathan Marten]

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

Jonathan Marten  changed:

   What|Removed |Added

 Status|REPORTED|ASSIGNED
 Ever confirmed|0   |1

--- Comment #3 from Jonathan Marten  ---
https://phabricator.kde.org/D21463
https://phabricator.kde.org/D21464

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

[kwin] [Bug 408029] Scrolling in evince when window does not have focus does not work (Xinput2-related)

[Nate Graham]

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

--- Comment #5 from Nate Graham  ---
Thanks for the info.

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