date:20211027

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

Bug ID: 444519
   Summary: System Settings crash upon opening Window Decoration
Module
   Product: kde-cli-tools
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: aleix...@kde.org
  Reporter: ryu.ketsu...@outlook.com
  Target Milestone: ---

Application: kcmshell5 (5.23.80)

Qt Version: 5.15.2
Frameworks Version: 5.88.0
Operating System: Linux 5.14.11-2-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.23.80 [KCrashBackend]

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

Just trying to change configurations for window decorations on System Settings

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings Module (kcmshell5), signal: Segmentation fault

[KCrash Handler]
#4  0x7f10886be8d1 in
QVector::realloc(int,
QFlags) () from /lib/libbreezecommon5.so.5
#5  0x7f10886be558 in
QVector::append(Breeze::BoxShadowRenderer::Shadow
const&) () from /lib/libbreezecommon5.so.5
#6  0x7f10886bd29d in Breeze::BoxShadowRenderer::addShadow(QPoint const&,
int, QColor const&) () from /lib/libbreezecommon5.so.5
#7  0x7f108870d27b in Breeze::Decoration::createShadowObject
(this=this@entry=0x55cfeed87110, strengthScale=) at
/usr/src/debug/breeze-5.23.80git.20211024T011602~945ba0cc-ku.4.2.x86_64/kdecoration/breezedecoration.cpp:778
#8  0x7f108870da07 in Breeze::Decoration::updateShadow
(this=0x55cfeed87110) at
/usr/src/debug/breeze-5.23.80git.20211024T011602~945ba0cc-ku.4.2.x86_64/kdecoration/breezedecoration.cpp:761
#9  0x7f1088705420 in Breeze::Decoration::reconfigure
(this=this@entry=0x55cfeed87110) at
/usr/src/debug/breeze-5.23.80git.20211024T011602~945ba0cc-ku.4.2.x86_64/kdecoration/breezedecoration.cpp:397
#10 0x7f10887061ad in Breeze::Decoration::init (this=0x55cfeed87110) at
/usr/src/debug/breeze-5.23.80git.20211024T011602~945ba0cc-ku.4.2.x86_64/kdecoration/breezedecoration.cpp:238
#11 0x7f1088f22f6f in
KDecoration2::Preview::PreviewButtonItem::createButton (this=0x55cfeee85db0) at
/usr/src/debug/kwin5-5.23.80git.20211027T114900~1626d7a51a-ku.22.1.x86_64/src/kcmkwin/kwindecoration/declarative-plugin/previewbutton.cpp:101
#12 0x7f10a1476322 in QQmlObjectCreator::finalize (this=0x55cfee9cf800,
interrupt=...) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-ku.1.1.x86_64/src/qml/qml/qqmlobjectcreator.cpp:1414
#13 0x7f10a140ca95 in QQmlIncubatorPrivate::incubate (this=0x55cfeecc1d20,
i=...) at /usr/include/qt5/QtCore/qscopedpointer.h:116
#14 0x7f10a140d08d in QQmlEnginePrivate::incubate (this=0x55cfee9c07a0,
i=..., forContext=) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-ku.1.1.x86_64/src/qml/qml/qqmlincubator.cpp:89
#15 0x7f109fdac12c in QQmlDelegateModelPrivate::object
(this=0x55cfeed200f0, group=QQmlListCompositor::Default, index=0,
incubationMode=) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-ku.1.1.x86_64/src/qmlmodels/qqmldelegatemodel.cpp:1299
#16 0x7f10a1948cf6 in QQuickItemViewPrivate::createItem
(this=this@entry=0x55cfeed31d70, modelIndex=modelIndex@entry=0,
incubationMode=incubationMode@entry=QQmlIncubator::AsynchronousIfNested) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-ku.1.1.x86_64/src/quick/items/qquickitemview.cpp:2349
#17 0x7f10a193acbd in QQuickGridViewPrivate::addVisibleItems
(this=0x55cfeed31d70, fillFrom=-0, fillTo=0, bufferFrom=,
bufferTo=, doBuffer=false) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-ku.1.1.x86_64/src/quick/items/qquickgridview.cpp:520
#18 0x7f10a1949d90 in QQuickItemViewPrivate::refill (this=0x55cfeed31d70,
from=-0, to=0) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-ku.1.1.x86_64/src/quick/items/qquickitemview.cpp:1801
#19 0x7f10a194fa88 in QQuickItemView::componentComplete
(this=0x55cfeed1fa40) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-ku.1.1.x86_64/src/quick/items/qquickitemview.cpp:1496
#20 0x7f10a1476322 in QQmlObjectCreator::finalize (this=0x55cfee9f6650,
interrupt=...) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-ku.1.1.x86_64/src/qml/qml/qqmlobjectcreator.cpp:1414
#21 0x7f10a140ca95 in QQmlIncubatorPrivate::incubate (this=0x55cfee93f370,
i=...) at /usr/include/qt5/QtCore/qscopedpointer.h:116
#22 0x7f10a140d08d in QQmlEnginePrivate::incubate (this=0x55cfee9c07a0,
i=..., forContext=) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-ku.1.1.x86_64/src/qml/qml/qqmlincubator.cpp:89
#23 0x7f10a14069cb in QQmlComponent::create (this=,
incubator=..., context=, forContext=) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-ku.1.1.x86_64/src/qml/qml/qqmlcomponent.cpp:1178
#24 0x7f10a1c8b8da in KDeclarative::QmlObject::completeInitialization

[kinfocenter] [Bug 443042] Information in the info center is not aligned.

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

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

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

[kdenlive] [Bug 431141] Wrong fps shown in error message

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #4 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

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

[kdenlive] [Bug 440029] Selecting clip by keyboard does not activate the effect stack

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #3 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

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

[kdenlive] [Bug 430932] Improve behavior of selection tool

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #3 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

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

[kdenlive] [Bug 425012] Color shifting / image degradation when importing clip or extracting frame

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #18 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

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

[frameworks-kwindowsystem] [Bug 443160] Cannot move cursor to absolute left of screen

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

--- Comment #4 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[kdenlive] [Bug 442235] Replacement of one effect by another in the latest version.

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

--- Comment #4 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[krusader] [Bug 444518] New: Support SPIR-V disassembly viewing in KrViewer

2021-10-27 Thread Dzmitry

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

Bug ID: 444518
   Summary: Support SPIR-V disassembly viewing in KrViewer
   Product: krusader
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: krviewer
  Assignee: krusader-bugs-n...@kde.org
  Reporter: kv...@fastmail.com
CC: krusader-bugs-n...@kde.org
  Target Milestone: ---

SUMMARY

It would be very useful to be able to see SPIR-V files
(https://www.khronos.org/spir/) in textual disassembly in the viewer.
`spirv-dis` comes in SPIRV-Tools, and Krusader could locate the path to it and
use it.


STEPS TO REPRODUCE
1. Hit F3 on a file with `.spv` extension

OBSERVED RESULT
File is displayed as raw.

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
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.

[kmymoney] [Bug 396016] KMYMoney GPG option is grayed out even though GPG installed

2021-10-27 Thread Nigel

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

--- Comment #26 from Nigel  ---
Created attachment 142958
  --> https://bugs.kde.org/attachment.cgi?id=142958=edit
Screenshot of processes

I see these processes when I try to do an online update

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

[kmymoney] [Bug 396016] KMYMoney GPG option is grayed out even though GPG installed

2021-10-27 Thread Nigel

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

--- Comment #25 from Nigel  ---
I see these processes:

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

[frameworks-kjs] [Bug 444003] kjsapitest segmentation fault (UB)

2021-10-27 Thread James Beddek

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

James Beddek  changed:

   What|Removed |Added

Summary|kjsfunctionstest|kjsapitest segmentation
   |segmentation fault  |fault (UB)

--- Comment #11 from James Beddek  ---
See below for where that Clang change introduced segfaults like mine,
determined to be from UB.

https://reviews.llvm.org/D99790#2678384

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

[frameworks-kjs] [Bug 444003] kjsfunctionstest segmentation fault

2021-10-27 Thread James Beddek

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

--- Comment #10 from James Beddek  ---
I did a bisect of Clang/LLVM as the tests pass on 12.0.1, but not 13.0.0. That
led me to this commit:
https://github.com/llvm/llvm-project/commit/0aa0458f1429372038ca6a4edc7e94c96cd9a753

Which has issues with thunks: https://reviews.llvm.org/D100388

That is seemingly in progress but has no progress in many months.

Below is the "kjsapitest" test ran with ubsan and Clang 12.0.1:

/home/telans/src/kde/kjs/src/kjs/object.cpp:247:27: runtime error: member call
on misaligned address 0x0003 for type 'KJS::JSValue', which requires 8
byte alignment
0x0003: note: pointer points here

SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior
/home/telans/src/kde/kjs/src/kjs/object.cpp:247:27 in
UndefinedBehaviorSanitizer:DEADLYSIGNAL
==2158002==ERROR: UndefinedBehaviorSanitizer: SEGV on unknown address
0x0003 (pc 0x7f92776b4c1f bp 0x7fff485b9990 sp 0x7fff485b9680 T2158002)
==2158002==The signal is caused by a READ memory access.
==2158002==Hint: address points to the zero page.
#0 0x7f92776b4c1f in KJS::JSObject::put(KJS::ExecState*, KJS::Identifier
const&, KJS::JSValue*, int) /home/telans/src/kde/kjs/src/kjs/object.cpp:247:27
#1 0x7f9277685633 in KJS::ErrorPrototype::ErrorPrototype(KJS::ExecState*,
KJS::ObjectPrototype*, KJS::FunctionPrototype*)
/home/telans/src/kde/kjs/src/kjs/error_object.cpp:53:5
#2 0x7f92776c5d13 in KJS::Interpreter::initGlobalObject()
/home/telans/src/kde/kjs/src/kjs/interpreter.cpp:385:38
#3 0x7f92776c40c7 in KJS::Interpreter::init()
/home/telans/src/kde/kjs/src/kjs/interpreter.cpp:270:5
#4 0x7f92776c44aa in KJS::Interpreter::Interpreter()
/home/telans/src/kde/kjs/src/kjs/interpreter.cpp:231:5
#5 0x7f92784701c6 in KJSInterpreter::KJSInterpreter()
/home/telans/src/kde/kjs/src/kjs/api/kjsinterpreter.cpp:99:27
#6 0x23cd61 in KJSApiTest::objectConstruction()
/home/telans/src/kde/kjs/autotests/kjsapitest.cpp:48:20
#7 0x240059 in KJSApiTest::qt_static_metacall(QObject*, QMetaObject::Call,
int, void**)
/home/telans/src/kde/kjs/build/autotests/kjsapitest_autogen/include/kjsapitest.moc:96:21
#8 0x7f92783244fe in QMetaMethod::invoke(QObject*, Qt::ConnectionType,
QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument) const
/usr/src/debug/dev-qt/qtcore-5.15.2-r10/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/corelib/kernel/qmetaobject.cpp:2303:13
#9 0x7f927841ed5c in QMetaMethod::invoke(QObject*, Qt::ConnectionType,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument) const
/usr/src/debug/dev-qt/qttest-5.15.2-r10/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd_build/src/testlib/../../include/QtCore/../../../qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/corelib/kernel/qmetaobject.h:122:16
#10 0x7f927841ed5c in QTest::TestMethods::invokeTestOnData(int) const
/usr/src/debug/dev-qt/qttest-5.15.2-r10/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/testlib/qtestcase.cpp:938:41
#11 0x7f927841f7d7 in QTest::TestMethods::invokeTest(int, char const*,
QTest::WatchDog*) const
/usr/src/debug/dev-qt/qttest-5.15.2-r10/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/testlib/qtestcase.cpp:1166:17
#12 0x7f9278420709 in QTest::TestMethods::invokeTests(QObject*) const
/usr/src/debug/dev-qt/qttest-5.15.2-r10/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/testlib/qtestcase.cpp:1507:33
#13 0x7f9278420d54 in QTest::qRun()
/usr/src/debug/dev-qt/qttest-5.15.2-r10/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/testlib/qtestcase.cpp:1934:14
#14 0x7f9278420a1d in QTest::qExec(QObject*, int, char**)
/usr/src/debug/dev-qt/qttest-5.15.2-r10/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/testlib/qtestcase.cpp:1842:15
#15 0x23fdf3 in main
/home/telans/src/kde/kjs/autotests/kjsapitest.cpp:283:1
#16 0x7f92779967fc in __libc_start_main
/usr/src/debug/sys-libs/glibc-2.33-r7/glibc-2.33/csu/../csu/libc-start.c:332:16
#17 0x21af89 in _start
/usr/src/debug/sys-libs/glibc-2.33-r7/glibc-2.33/csu/../sysdeps/x86_64/start.S:120

UndefinedBehaviorSanitizer can not provide additional info.
SUMMARY: UndefinedBehaviorSanitizer: SEGV
/home/telans/src/kde/kjs/src/kjs/object.cpp:247:27 in
KJS::JSObject::put(KJS::ExecState*, KJS::Identifier const&, KJS::JSValue*, int)
==2158002==ABORTING

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

[systemsettings] [Bug 444517] New: Font preview kerning is broken

2021-10-27 Thread Nagy Tibor

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

Bug ID: 444517
   Summary: Font preview kerning is broken
   Product: systemsettings
   Version: 5.23.2
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_fontinst
  Assignee: plasma-b...@kde.org
  Reporter: xnagyti...@gmail.com
  Target Milestone: ---

Created attachment 142957
  --> https://bugs.kde.org/attachment.cgi?id=142957=edit
Screenshot

SUMMARY
The preview panel at the Font Management KCM doesn't properly kern its preview
text. This makes the preview text look slightly crooked.

I attached a screenshot that compares this preview with an another KDE app
(Krita) that does proper kerning just for reference.

STEPS TO REPRODUCE
1. Get Liberation Sans from your package manager. Also reproducible with other
well-kerned fonts like Bitstream Vera Sans, DejaVu Sans, Noto Sans, Ubuntu
font, etc.
2. Open Font Management and select Liberation Sans.
3. Right click the preview -> Change Preview Text...
4. Enter "VAVA" as the preview text -> OK.
5. Notice how the negative kerning offsets are not applied between the "V" and
"A" characters. Liberation Sans defines a -152 unit offset at 2048 units/em
resolution between these character pairs.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.23
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.3
Graphics Platform: X11

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

[plasmashell] [Bug 444511] Re-arranging icons in Kickoff's favorites page causes them to overlap

2021-10-27 Thread Patrick Silva

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

Patrick Silva  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com
 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #2 from Patrick Silva  ---


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

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

[plasmashell] [Bug 443975] Dragging favorites icons in the application launcher causes overlapping

2021-10-27 Thread Patrick Silva

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

Patrick Silva  changed:

   What|Removed |Added

 CC||sbmich...@tuta.io

--- Comment #35 from Patrick Silva  ---
*** Bug 444511 has been marked as a duplicate of this bug. ***

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

[krita] [Bug 444516] New: Crash while painting

2021-10-27 Thread David REVOY

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

Bug ID: 444516
   Summary: Crash while painting
   Product: krita
   Version: nightly build (please specify the git hash!)
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: i...@davidrevoy.com
  Target Milestone: ---

Hi, Here is a (random) crash while painting with a recent Krita Plus build;
appimage. Version: 5.0.0-beta2 (git 188e619). A very solid appimage; first
crash in last days. I collected a backtrace; but I'm not sure if it is a
revelant one. 
I hope it will help!
~~~

[New Thread 0x7fff2a37a700 (LWP 284671)]
[New Thread 0x7fff2ab7b700 (LWP 284672)]
[New Thread 0x7fff0bfff700 (LWP 284673)]
[New Thread 0x7fff2beab700 (LWP 284674)]
[New Thread 0x7fff2b6aa700 (LWP 284675)]
[Thread 0x7fff0bfff700 (LWP 284673) exited]
[Thread 0x7fff2a37a700 (LWP 284671) exited]
[Thread 0x7fff2beab700 (LWP 284674) exited]
[Thread 0x7fff2ab7b700 (LWP 284672) exited]
[Thread 0x7fff2b6aa700 (LWP 284675) exited]
[New Thread 0x7fff2b6aa700 (LWP 284676)]
[New Thread 0x7fff2ab7b700 (LWP 284677)]
[New Thread 0x7fff2beab700 (LWP 284680)]
[New Thread 0x7fff2a37a700 (LWP 284682)]
[New Thread 0x7fff29b79700 (LWP 284683)]
[New Thread 0x7fff0bfff700 (LWP 284684)]
[Thread 0x7fff2a37a700 (LWP 284682) exited]
[Thread 0x7fff2ab7b700 (LWP 284677) exited]
[Thread 0x7fff29b79700 (LWP 284683) exited]
[Thread 0x7fff2beab700 (LWP 284680) exited]
[Thread 0x7fff0bfff700 (LWP 284684) exited]
[Thread 0x7fff2b6aa700 (LWP 284676) exited]
[New Thread 0x7fff2b6aa700 (LWP 284685)]
[New Thread 0x7fff0bfff700 (LWP 284686)]
[New Thread 0x7fff2beab700 (LWP 284687)]
[New Thread 0x7fff29b79700 (LWP 284688)]
--Type  for more, q to quit, c to continue without paging--

Thread 1 "AppRun" received signal SIGSEGV, Segmentation fault.
0x75d958f8 in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
from /tmp/.mount_krita-mLAbBL/usr/bin/../lib/libQt5Widgets.so.5
(gdb) thread apply all bt

Thread 30894 (Thread 0x7fff29b79700 (LWP 284688)):
#0  futex_abstimed_wait_cancelable (private=,
abstime=0x7fff29b78ba0, clockid=, expected=0,
futex_word=0x7ffee0a40a64) at ../sysdeps/nptl/futex-internal.h:320
#1  __pthread_cond_wait_common (abstime=0x7fff29b78ba0, clockid=, mutex=0x7ffee0a40a10, cond=0x7ffee0a40a38) at pthread_cond_wait.c:520
#2  __pthread_cond_timedwait (cond=0x7ffee0a40a38, mutex=0x7ffee0a40a10,
abstime=0x7fff29b78ba0) at pthread_cond_wait.c:656
#3  0x750e0d64 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/tmp/.mount_krita-mLAbBL/usr/bin/../lib/libQt5Core.so.5
#4  0x750e10f6 in QWaitCondition::wait(QMutex*, unsigned long) () from
/tmp/.mount_krita-mLAbBL/usr/bin/../lib/libQt5Core.so.5
#5  0x750ddb28 in ?? () from
/tmp/.mount_krita-mLAbBL/usr/bin/../lib/libQt5Core.so.5
#6  0x750d942e in ?? () from
/tmp/.mount_krita-mLAbBL/usr/bin/../lib/libQt5Core.so.5
#7  0x7fffef5b1609 in start_thread (arg=) at
pthread_create.c:477
#8  0x74d41293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 30893 (Thread 0x7fff2beab700 (LWP 284687)):
#0  futex_abstimed_wait_cancelable (private=,
abstime=0x7fff2beaaba0, clockid=, expected=0,
futex_word=0x7ffee000d180) at ../sysdeps/nptl/futex-internal.h:320
#1  __pthread_cond_wait_common (abstime=0x7fff2beaaba0, clockid=, mutex=0x7ffee000d130, cond=0x7ffee000d158) at pthread_cond_wait.c:520
#2  __pthread_cond_timedwait (cond=0x7ffee000d158, mutex=0x7ffee000d130,
abstime=0x7fff2beaaba0) at pthread_cond_wait.c:656
#3  0x750e0d64 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/tmp/.mount_krita-mLAbBL/usr/bin/../lib/libQt5Core.so.5
#4  0x750e10f6 in QWaitCondition::wait(QMutex*, unsigned long) () from
/tmp/.mount_krita-mLAbBL/usr/bin/../lib/libQt5Core.so.5
#5  0x750ddb28 in ?? () from
/tmp/.mount_krita-mLAbBL/usr/bin/../lib/libQt5Core.so.5
#6  0x750d942e in ?? () from
/tmp/.mount_krita-mLAbBL/usr/bin/../lib/libQt5Core.so.5
#7  0x7fffef5b1609 in start_thread (arg=) at
pthread_create.c:477
#8  0x74d41293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 30892 (Thread 0x7fff0bfff700 (LWP 284686)):
#0  futex_abstimed_wait_cancelable (private=,
abstime=0x7fff0bffeba0, clockid=, expected=0,
futex_word=0x7ffee0a3ae40) at ../sysdeps/nptl/futex-internal.h:320
#1  __pthread_cond_wait_common (abstime=0x7fff0bffeba0, clockid=, mutex=0x7ffee0a3adf0, cond=0x7ffee0a3ae18) at pthread_cond_wait.c:520
#2  __pthread_cond_timedwait (cond=0x7ffee0a3ae18, mutex=0x7ffee0a3adf0,
abstime=0x7fff0bffeba0) at pthread_cond_wait.c:656
#3  0x750e0d64 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/tmp/.mount_krita-mLAbBL/usr/bin/../lib/libQt5Core.so.5
#4  0x750e10f6 in QWaitCondition::wait(QMutex*, unsigned long) () from

[xdg-desktop-portal-kde] [Bug 444515] New: If file already exists and the user clicks cancel, force the focus on the filename

2021-10-27 Thread Antti Savolainen

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

Bug ID: 444515
   Summary: If file already exists and the user clicks cancel,
force the focus on the filename
   Product: xdg-desktop-portal-kde
   Version: 5.23.2
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: jgrul...@redhat.com
  Reporter: antti.s...@gmail.com
  Target Milestone: ---

SUMMARY
Demonstrative video: https://youtu.be/kvAM-iy67QY
It would be a nice usability fix if the focus would go on the recommended
filename when the user refuses to overwrite the file. This would allow the user
to immediately start typing the new desired filename without fumbling for the
mouse.

STEPS TO REPRODUCE
1. Enter the file save dialog
2. Have the file be something that is already in the folder
3. Try to save the file
4. In the "Overwrite file?" dialog click cancel

OBSERVED RESULT
The focus is still on the save button

EXPECTED RESULT
The filepicker should move focus on the filename and highligh it.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
(available in About System)
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2

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

[plasmashell] [Bug 444514] Double Arrow Icon on Symbolic Links with Desktop Huge Icon Size

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

qydwhotm...@gmail.com changed:

   What|Removed |Added

 CC||qydwhotm...@gmail.com

--- Comment #1 from qydwhotm...@gmail.com ---
Can reproduce

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

[plasmashell] [Bug 444514] New: Double Arrow Icon on Symbolic Links with Desktop Huge Icon Size

2021-10-27 Thread diminombre

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

Bug ID: 444514
   Summary: Double Arrow Icon on Symbolic Links with Desktop Huge
Icon Size
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Desktop Containment
  Assignee: notm...@gmail.com
  Reporter: diminom...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 142956
  --> https://bugs.kde.org/attachment.cgi?id=142956=edit
screenshot overlay symbolic link arrow

SUMMARY


STEPS TO REPRODUCE
1. Set Desktop Icon Size to "Huge"
2. Create some Symbolic Link

OBSERVED RESULT
3. See double "symbolic link arrow"


EXPECTED RESULT
Only 1 symbolic link arrow


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon 5.23 User Edition
KDE Plasma Version: 5.23.1
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION

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

[kwin] [Bug 444513] New: Initially full screen windows only shown on screen 0

2021-10-27 Thread Thiago Macieira

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

Bug ID: 444513
   Summary: Initially full screen windows only shown on screen 0
   Product: kwin
   Version: 5.23.0
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: multi-screen
  Assignee: kwin-bugs-n...@kde.org
  Reporter: thi...@kde.org
  Target Milestone: ---

SUMMARY
When an application creates a window that is initially full screen, it gets
shown only on screen 0, regardless of where the geometry or screen setting was.
If the window was not created/mapped full screen, but made full screen after
shown, it is located in the correct screen.

STEPS TO REPRODUCE
1. Connect a second monitor and extend it (to the right for me)
2. Press Ctrl+Alt+Del to show the Leave window

This can also be done with mpv -screen=1 -fs=yes

OBSERVED RESULT
Both Leave windows are on screen 0 (to the left for me) and screen 1 is still
usable. You can notice this because they're darker than usual and you can Alt+
or Meta+drag one of them to the other screen and you'll see another window
below it.

EXPECTED RESULT
One Leave window is displayed in each screen. In the mpv case, it's displayed
in the screen that was requested.

SOFTWARE/OS VERSIONS
OpenSUSE Tumbleweed 20211021
KDE Plasma Version: 5.23.0
KDE Frameworks Version: 5.87.0
Qt Version: 5.12.2 + kde patches

ADDITIONAL INFORMATION
This did not happen with kwin 5.22.5.

Using xprop, you can tell that one of the Leave windows has this property:
WM_NORMAL_HINTS(WM_SIZE_HINTS):
user specified location: 3840, 0
user specified size: 3840 by 2160
program specified resize increment: 2 by 2
program specified base size: -2 by -2
window gravity: Static

And yet it was displayed at location 0,0.

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

[dolphin] [Bug 443540] Dolphin glitch after packing directory to 7z

2021-10-27 Thread OLoKo64

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

OLoKo64  changed:

   What|Removed |Added

 CC||seastroke_pu...@aleeas.com

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

[dolphin] [Bug 443540] Dolphin glitch after packing directory to 7z

2021-10-27 Thread OLoKo64

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

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

dolphin (21.08.1) using Qt 5.15.2

- What I was doing when the application crashed:
Compressing a file with 7z LZMA2
- Unusual behavior I noticed:
The application kept saying the compression was happening when it already
finished. Cancelling the compression made the application crash.
- Custom settings of the application:
None.

-- Backtrace (Reduced):
#5  0x7f609a81c59c in KJob::kill(KJob::KillVerbosity) () from
/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#6  0x7f609a81c59c in KJob::kill(KJob::KillVerbosity) () from
/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
[...]
#10 0x7f609960d73e in QObject::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f609a0ce6b3 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x7f60995e016a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5

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

[partitionmanager] [Bug 428974] KDE Partition Manager keeps on asking for authentication even if the user presses "cancel"

2021-10-27 Thread Andrius Štikonas

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

Andrius Štikonas  changed:

   What|Removed |Added

 CC||antti.s...@gmail.com

--- Comment #12 from Andrius Štikonas  ---
*** Bug 444512 has been marked as a duplicate of this bug. ***

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

[partitionmanager] [Bug 444512] Unable to close partitionmanager if you do not know the password

2021-10-27 Thread Andrius Štikonas

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

Andrius Štikonas  changed:

   What|Removed |Added

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

--- Comment #1 from Andrius Štikonas  ---
It's not endless loop. It's once per command that partitionmanager tries to run
while doing initial scan. That said it's still not user friendly but a bit
tricky to fix due to how authentication is invoked by polkit.

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

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

[partitionmanager] [Bug 444512] New: Unable to close partitionmanager if you do not know the password

2021-10-27 Thread Antti Savolainen

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

Bug ID: 444512
   Summary: Unable to close partitionmanager if you do not know
the password
   Product: partitionmanager
   Version: 21.08.2
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: andr...@stikonas.eu
  Reporter: antti.s...@gmail.com
  Target Milestone: ---

SUMMARY
Demonstrative video: https://youtu.be/aSk18rl273U
If the partitionmanager is started without knowing the password, it is not
possible to close it

STEPS TO REPRODUCE
1. Open partitionmanager
2. Try to close it with just the GUI options that you have available

OBSERVED RESULT
You're stuck in an endless loop

EXPECTED RESULT
The program should close after 3 consecutive attempts or when cancel is clicked

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
(available in About System)
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2

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

[plasmashell] [Bug 444511] Re-arranging icons in Kickoff's favorites page causes them to overlap

2021-10-27 Thread Michael SB

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

--- Comment #1 from Michael SB  ---
Created attachment 142954
  --> https://bugs.kde.org/attachment.cgi?id=142954=edit
Imgur Link to video demo of the steps to reproduce the bug

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

[plasmashell] [Bug 444511] New: Re-arranging icons in Kickoff's favorites page causes them to overlap

2021-10-27 Thread Michael SB

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

Bug ID: 444511
   Summary: Re-arranging icons in Kickoff's favorites page causes
them to overlap
   Product: plasmashell
   Version: 5.23.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: k...@davidedmundson.co.uk
  Reporter: sbmich...@tuta.io
CC: mikel5...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

SUMMARY
When dragging and dropping icons of programs pinned to the Favorites page of
Kickoff menu, the icons start to overlap. It's currently reproducible every
time on my end.

STEPS TO REPRODUCE
I have added a screen recording to illustrate the steps to reproduce.
Basically just drag and drop icons pinned on the favorites page of Kickoff
menu.

OBSERVED RESULT
Icons overlap after dragging and dropping.

EXPECTED RESULT
Icons get re-arranged in the desired order without overlapping.

Operating System: openSUSE Tumbleweed 20211025
KDE Plasma Version: 5.23.1
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Kernel Version: 5.14.14-1-default (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 4600H with Radeon Graphics
Memory: 7.8 GiB of RAM

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

[plasmashell] [Bug 444400] Plasma crashes when laptop screen is re-enabled

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

marcin.ba...@gmail.com changed:

   What|Removed |Added

 CC||marcin.ba...@gmail.com

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

[plasmashell] [Bug 444400] Plasma crashes when laptop screen is re-enabled

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

--- Comment #2 from marcin.ba...@gmail.com ---
Created attachment 142953
  --> https://bugs.kde.org/attachment.cgi?id=142953=edit
New crash information added by DrKonqi

plasmashell (5.23.1) using Qt 5.15.2

- What I was doing when the application crashed:
The same situation after the last update to:
Operating System: openSUSE Tumbleweed 20211025
KDE Plasma Version: 5.23.1
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Kernel Version: 5.14.14-1-default (64-bit)
Graphics Platform: X11
Processors: 12 × Intel® Core™ i7-8750H CPU @ 2.20GHz
Memory: 31.2 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1060/PCIe/SSE2

-- Backtrace (Reduced):
#6  QQuickItemPrivate::addToDirtyList() (this=this@entry=0x55b58ab6eb40) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.5.x86_64/src/quick/items/qquickitem.cpp:6203
#7  0x7fe3d501914e in
QQuickItemPrivate::dirty(QQuickItemPrivate::DirtyType) (this=0x55b58ab6eb40,
type=type@entry=QQuickItemPrivate::ChildrenUpdateMask) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.5.x86_64/src/quick/items/qquickitem.cpp:6188
#8  0x7fe3d5030224 in forceUpdate(QQuickItem*) (item=0x55b58a87c1a0) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.5.x86_64/src/quick/items/qquickitem.h:468
#9  0x7fe3d503024f in forceUpdate(QQuickItem*) (item=0x55b58993ccc0) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.5.x86_64/src/quick/items/qquickwindow.cpp:497
#10 0x7fe3d503024f in forceUpdate(QQuickItem*) (item=0x55b599d1d5c0) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.5.x86_64/src/quick/items/qquickwindow.cpp:497

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

[plasmashell] [Bug 444385] Right-click on GTK icon in systray leads to fast random mouse clicks events

2021-10-27 Thread David Edmundson

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

--- Comment #13 from David Edmundson  ---
Faerbit as you were already compiling things, could you test that patch. 
I've had to guess at the causes from the clues above, so I can't be 100% sure
it fixes your problem.

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

[kwin] [Bug 444510] New: Mouse cursor acts weird with flat acceleration profile in plasma-wayland

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

Bug ID: 444510
   Summary: Mouse cursor acts weird with flat acceleration profile
in plasma-wayland
   Product: kwin
   Version: 5.23.2
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: input
  Assignee: kwin-bugs-n...@kde.org
  Reporter: n8thefus...@gmail.com
  Target Milestone: ---

SUMMARY
In plasma-wayland with the flat acceleration profile the mouse cursor will not
move accurately when moving the cursor to the top left corner when a software
cursor is in use (such as in video games).

STEPS TO REPRODUCE
1. Ensure the flat acceleration profile is chosen
2. Launch a game, minetest for example.
3. In minetest, click the "new" button, then the "create" button, and then the
"Play Game" button
4. Try to move cursor slowly from the center to the top left corner of the
screen

OBSERVED RESULT
The cursor does not accurately represent my hand movement when moving to the
top left corner.

EXPECTED RESULT
The cursor should accurately represent my hand movement everywhere.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.23.2
(available in About System)
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87
Qt Version: 5.15.2

ADDITIONAL INFORMATION
I tested this with KDE Neon Testing Edition dated 2021-10-26 and got the same
result.
The problem only occurs with the flat accleration profile on wayland. It does
not happen with the adaptive accleration profile nor does it happen on the X11
session.

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

[plasmashell] [Bug 444385] Right-click on GTK icon in systray leads to fast random mouse clicks events

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

--- Comment #12 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1149

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

[Breeze] [Bug 444509] New: Add icon for QMPlay2 to Breeze icon set

2021-10-27 Thread Michael SB

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

Bug ID: 444509
   Summary: Add icon for QMPlay2 to Breeze icon set
   Product: Breeze
   Version: 5.23.1
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: sbmich...@tuta.io
CC: kain...@gmail.com
  Target Milestone: ---

As stated in the title, adding an icon for QMPlay2 - Qt Media Player 2.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed
KDE Plasma Version: Plasma 5.23.1
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2

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

[plasmashell] [Bug 444389] Wayland: panel/taskbar crash after display sleep

2021-10-27 Thread gfunk

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

--- Comment #9 from gfunk  ---
(In reply to David Edmundson from comment #8)
> It's fine, you don't need any more symbols.

> I have made a patch for this in 5.23.2 that I hope addresses this problem.
> Please reopen if not.

:o If it's resolved in the next set of patches I'll be both impressed and
grateful, thanks!

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

[ktouch] [Bug 422088] Can't type name in welcome window under Wayland

2021-10-27 Thread Ariel

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

Ariel  changed:

   What|Removed |Added

 CC||arieldell...@outlook.com

--- Comment #7 from Ariel  ---
Same here KDE Plasma 5.23.2 on ArchLinux.

A workaround that worked for me:

  QT_QPA_PLATFORM=xcb ktouch

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

[krunner] [Bug 427921] Text input is unusable

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

--- Comment #11 from alexmatee...@yahoo.com ---
It's working now with 5.23

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

[plasmashell] [Bug 427925] Application menu displays wrong entries on hovering a new entry

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

--- Comment #11 from alexmatee...@yahoo.com ---
Works now with 5.23. No idea when exactly it was fixed.

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

[Spectacle] [Bug 442875] Spectacle always opens its window when a screenshot is taken

2021-10-27 Thread Antonio Prcela

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

Antonio Prcela  changed:

   What|Removed |Added

 CC||antonio.prc...@gmail.com

--- Comment #1 from Antonio Prcela  ---
https://bugs.kde.org/show_bug.cgi?id=443060

seems to bi similar to this

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

[kdeconnect] [Bug 398931] Use phone's fingerprint reader for authentification

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

--- Comment #6 from pub...@redaril.me ---
I was about to file a feature request about this, then noticed someone already
did that a year ago.

In the latest Nate's blog post
(https://pointieststick.com/2021/10/22/this-week-in-kde-fingerprint-reader-and-nvidia-gbm-support)
he's announcing Plasma 5.24 will finally be compatible with fingerprint
devices. As a mainly desktop computers user, it's hard to have such a device,
while I always carry with me my phone. It'd be very handy to use my device's
fingerprint sensor for fingerprint authentication.

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

[kdeconnect] [Bug 398931] Use phone's fingerprint reader for authentification

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

pub...@redaril.me changed:

   What|Removed |Added

 CC||pub...@redaril.me

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

[digikam] [Bug 444501] Face detection, write name tags (metadata) to file - Changes date and time on photo

2021-10-27 Thread dajomu

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

--- Comment #2 from dajomu  ---
Hi,

my apologies, I think that the fault is in Google photos (GP). I was sure that
GP sorted images by creation date, but it seems like they read modified date
instead. It is really annoying.
Issue is not with digikam but rather GP.

Can digikam sort images by modified date?
Can digikam change modified date as a batch process? I would like to set
modified date to creation date so that GP sort the files properly.

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

[plasmashell] [Bug 444132] Sometimes can't type in kickoff search box (on primary display) when mouse pointer is on secondary display

2021-10-27 Thread Gusted

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

--- Comment #3 from Gusted  ---
(In reply to Noah Davis from comment #2)
> Wayland or X11?

X11

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

[frameworks-kio] [Bug 440721] 5.84.0: test suite is failing and some uunits are blocking

2021-10-27 Thread kloczek

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

--- Comment #1 from kloczek  ---
Looks like 5.87.0 is afiling in more units

+ cd kio-5.87.0
+ xvfb-run -a /usr/bin/make -O -j12 V=1 VERBOSE=1 -C x86_64-redhat-linux-gnu
test ARGS=--output-on-failure 'ARGS=--output-on-failure \
-E
"^(kiocore-mimetypefinderjobtest|kiogui-openurljobtest|kiowidgets-jobguitest|kiofilewidgets-kurlnavigatortest|kiofilewidgets-kfilecustomdialogtest|kiocore-kmountpointtest|kiocore-jobtest|kiowidgets-kdirlistertest|kiowidgets-kdirmodeltest|kiofilewidgets-kfileplacesmodeltest|kiocore-ktcpsockettest)"'
make: Entering directory
'/home/tkloczko/rpmbuild/BUILD/kio-5.87.0/x86_64-redhat-linux-gnu'
Running tests...
/usr/bin/ctest --force-new-ctest-process --output-on-failure \
-E
"^(kiocore-mimetypefinderjobtest|kiogui-openurljobtest|kiowidgets-jobguitest|kiofilewidgets-kurlnavigatortest|kiofilewidgets-kfilecustomdialogtest|kiocore-kmountpointtest|kiocore-jobtest|kiowidgets-kdirlistertest|kiowidgets-kdirmodeltest|kiofilewidgets-kfileplacesmodeltest|kiocore-ktcpsockettest)"
Test project /home/tkloczko/rpmbuild/BUILD/kio-5.87.0/x86_64-redhat-linux-gnu
  Start  1: appstreamtest
 1/59 Test  #1: appstreamtest    Passed   
0.03 sec

[..]

95% tests passed, 3 tests failed out of 59

Total Test time (real) =  96.64 sec

The following tests FAILED:
 25 - applicationlauncherjob_servicetest (Failed)
 42 - kiowidgets-kurifiltertest-colon-separator (Failed)
 43 - kiowidgets-kurifiltertest-space-separator (Failed)
Errors while running CTest

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

[digikam] [Bug 444492] Few Ideas : send to WordPress 5 ou Drupal 9

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

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

   What|Removed |Added

  Component|general |Plugin-WebService-WishForNe
   ||wTools
Summary|Few Ideas   |Few Ideas : send to
   ||WordPress 5 ou Drupal 9
Version|unspecified |7.4.0
 CC||caulier.gil...@gmail.com

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

[plasmashell] [Bug 444132] Sometimes can't type in kickoff search box (on primary display) when mouse pointer is on secondary display

2021-10-27 Thread Noah Davis

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

--- Comment #2 from Noah Davis  ---
Wayland or X11?

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

[dolphin] [Bug 435806] Hitting F3 in split view always closes right pane, even when it has the focus

2021-10-27 Thread Antonio Prcela

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

Antonio Prcela  changed:

   What|Removed |Added

 CC||antonio.prc...@gmail.com

--- Comment #5 from Antonio Prcela  ---
Settings -> Behavior -> uncheck "Turning off split view closes active pane"
:)

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

[dolphin] [Bug 444508] New: Dolphin doesn't exit cleanly after opening terminal

2021-10-27 Thread Maciej Stanczew

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

Bug ID: 444508
Summary: Dolphin doesn't exit cleanly after opening terminal
Product: dolphin
Version: 21.08.2
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: maciej.stancze...@gmail.com
CC: kfm-de...@kde.org
Target Milestone: ---

SUMMARY
After using Open Terminal feature, Dolphin process (and some kioslave5
processes) will not exit cleanly. Instead, they'll remain in process list
indefinitely.

STEPS TO REPRODUCE
1. Open Dolphin
2. From the menu choose Open Terminal (Konsole in my case)
3. Close the newly opened terminal (optional, doesn't have effect on
reproduction)
4. Close Dolphin
5. Check in process list (e.g. in ps or System Activity) that Dolphin exited

OBSERVED RESULT
Dolphin is still present in process list.

EXPECTED RESULT
Dolphin process should fully exit.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
The issue doesn't happen if step #2 is skipped: closing Dolphin after *not*
using Open Terminal makes the process exit cleanly.
It also doesn't reproduce when opening the Terminal panel (the one at the
bottom of Dolphin window).

I'm pretty sure this is a regression introduced in fix for bug #441072. Before
this fix, Dolphin used kinit for opening the terminal, and it didn't hang after
closing.
I first saw this issue with Arch package of Dolphin in version 21.08.0-2, which
is base 21.08.0 with the patch from bug #441072 applied:
https://github.com/archlinux/svntogit-packages/commit/ed9afe2a441db57a5a85dc0fa4601ab9205ff6a9
https://invent.kde.org/system/dolphin/-/commit/27bfcde4efaf936243fc41e4a61d0cac32105ef6.patch

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

[plasmashell] [Bug 444415] On wayland, panel shadow doesn't show where system tray is

2021-10-27 Thread Michael D

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

--- Comment #3 from Michael D  ---
It does seem to be caused by switching from 1440p to 1080p, back to 1440p, but
I can't consistently reproduce it. The output of "kscreen-doctor -o" before and
after the shadow disappears is the same:

kscreen-doctor -o
Output: 1 Chimei Innolux Corporation eDP-1-unknown disabled connected  Panel
Modes: 0:1680x1050@60 1:1280x1024@60 2:1440x900@60 3:1280x800@60 4:1280x720@60
5:1024x768@60 6:800x600@60 7:640x480@60 8:1920x1080@60*! Geometry: 2559,0
1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown 
Output: 2 Lenovo Group Limited P24h-10/U4P1 enabled connected primary
Unknown Modes: 0:1920x1200@60 1:1920x1080@60 2:1920x1080@60 3:1920x1080@60
4:1920x1080@50 5:1600x1200@60 6:1680x1050@60 7:1600x900@60 8:1280x1024@60
9:1440x900@60 10:1280x800@60 11:1280x720@60 12:1280x720@60 13:1280x720@60
14:1280x720@50 15:1024x768@60 16:800x600@60 17:720x480@60 18:720x480@60
19:720x480@60 20:720x480@60 21:720x480@60 22:640x480@60 23:640x480@60
24:640x480@60 25:720x400@70 26:2560x1440@60*! Geometry: 0,0 2560x1440 Scale: 1
Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown primary

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

[valgrind] [Bug 435732] memcheck/tests/leak_cpp_interior fails with gcc11

2021-10-27 Thread Paul Floyd

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

--- Comment #5 from Paul Floyd  ---
The doesn't reproduce with g++11 (FreeBSD Ports Collection) 11.2.0

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

[frameworks-kio] [Bug 439865] kf5.kio.core: couldn't create slave: "Meldung von klauncher: Unbekanntes Protokoll „g“.\n"

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

--- Comment #5 from Ralf Habacker  ---
(In reply to Ralf Habacker from comment #3)
> (In reply to Ahmad Samir from comment #2)
> > Is klauncher available on windows? IIRC kate explicitly runs on windows by
> > forking the slaved (probably setting KDE_FORK_SLAVES=1).

This problem is independent from klauncher.

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

[dolphin] [Bug 442774] Dolphin crashed after click on stop button of notification indicating the progress of compression to 7zip archive

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

Seqularise  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=444507

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

[dolphin] [Bug 444507] Dolphin crashes after extracting with ark

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

Seqularise  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=442774

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

[kdenlive] [Bug 444505] Clip speed effect is after searching for missing clips paths in kdenlive 19.12.3

2021-10-27 Thread smihael

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

--- Comment #1 from smihael  ---
Don't use snap package as it is broken in a different way. In snap,
rendering won't start as per
https://askubuntu.com/questions/1344526/kdenlive-snap-version-doesnt-render-in-ubuntu-18-04
and
https://www.reddit.com/r/kdenlive/comments/gu0wz4/rendering_anything_gets_stuck_on_waiting/.
Use official kdenlive PPA (
https://launchpad.net/~kdenlive/+archive/ubuntu/kdenlive-stable) or
AppImage instead.

On Wed, 27 Oct 2021 at 21:24, smihael  wrote:

> https://bugs.kde.org/show_bug.cgi?id=444505
>
> Bug ID: 444505
>Summary: Clip speed effect is after searching for missing clips
> paths in kdenlive 19.12.3
>Product: kdenlive
>Version: 19.12.3
>   Platform: Ubuntu Packages
> OS: Linux
> Status: REPORTED
>   Severity: normal
>   Priority: NOR
>  Component: Effects & Transitions
>   Assignee: vpi...@kde.org
>   Reporter: smih...@gmail.com
>   Target Milestone: ---
>
> SUMMARY
>
> STEPS TO REPRODUCE
> 1. Add video clip (e.g. ~/Videos/vid.ogv) to timeline, right click and
> change
> speed using the context menu (to e.g. 80%)
> 2. Save project and exit kdenlive
> 3. Move clip to a different location (e.g. mv ~/Videos/vid.ogv
> ~/Videos/Project1/vid.ogv)
> 4. Reopen kdenlive project. A warning about missing clips will show up,
> giving
> an option to search recursively for missing clips.
>
> OBSERVED RESULT
>
> After clip(s) have been found, clip speed effect is lost.
>
> WORKAROUND
>
> Manually editing .kdenlive file (search and replace vid.ogv to
> Project1/vid.ogv.
>
> In newer versions (tested with 21.08.2 snap) this works as intended.
> Version
> 19.12.3 is however still the newest version in Ubuntu 20.04 LTS
> repositories.
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[dolphin] [Bug 444507] New: Dolphin crashes after extracting with ark

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

Bug ID: 444507
   Summary: Dolphin crashes after extracting with ark
   Product: dolphin
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: seqular...@outlook.com
CC: kfm-de...@kde.org
  Target Milestone: ---

Application: dolphin (21.11.70)
 (Compiled from sources)
Qt Version: 5.15.3
Frameworks Version: 5.88.0
Operating System: Linux 5.14.14-zen1-1-zen x86_64
Windowing System: Wayland
Distribution: Arch Linux
DrKonqi: 5.23.80 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
1. open directory with archive in dolphin
2. extract files through context menu

 - Observed result:
Dolphin crashes, notification appears about crash, dolphin reopens in directort
with archive

The crash can be reproduced every time.

-- Backtrace:
Application: Dolphin (dolphin), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = {}}
[KCrash Handler]
#6  0x7fa3d006fd22 in raise () from /usr/lib/libc.so.6
#7  0x7fa3d0059862 in abort () from /usr/lib/libc.so.6
#8  0x7fa3d04a7abe in qt_message_fatal (message=...,
context=...) at global/qlogging.cpp:1914
#9  QMessageLogger::fatal (this=this@entry=0x7ffdfc68bf38,
msg=msg@entry=0x7fa3d07c3030 "ASSERT: \"%s\" in file %s, line %d") at
global/qlogging.cpp:893
#10 0x7fa3d04a6dd0 in qt_assert (assertion=assertion@entry=0x5582122ea485
"dirs.size() > 0", file=file@entry=0x5582122ea090
"/build/dolphin/src/dolphin/src/dolphintabwidget.cpp", line=line@entry=180) at
global/qglobal.cpp:3358
#11 0x55821225a951 in DolphinTabWidget::openDirectories (this=, dirs=..., splitView=) at
/build/packages/sources-debug/dolphin/src/dolphintabwidget.cpp:180
#12 0x5582122c8d29 in DolphinMainWindow::openDirectories (splitView=false,
dirs=..., this=0x558212a99020) at
/build/packages/sources-debug/dolphin/src/dolphinmainwindow.cpp:250
#13 DolphinMainWindow::openDirectories (splitView=false, dirs=...,
this=0x558212a99020) at
/build/packages/sources-debug/dolphin/src/dolphinmainwindow.cpp:255
#14 MainWindowAdaptor::openDirectories (splitView=false, dirs=...,
this=) at
/build/packages/sources-debug/build/src/dolphinmainwindowadaptor.cpp:51
#15 MainWindowAdaptor::qt_static_metacall (_o=, _id=, _a=0x7ffdfc68c100, _c=) at
/build/packages/sources-debug/build/src/dolphinmainwindowadaptor.moc:130
#16 0x5582122c8f91 in MainWindowAdaptor::qt_static_metacall
(_a=0x7ffdfc68c100, _id=3, _c=QMetaObject::InvokeMetaMethod, _o=0x5582129c89e0)
at /build/packages/sources-debug/build/src/dolphinmainwindowadaptor.moc:120
#17 MainWindowAdaptor::qt_metacall (this=0x5582129c89e0,
_c=QMetaObject::InvokeMetaMethod, _id=3, _a=0x7ffdfc68c100) at
/build/packages/sources-debug/build/src/dolphinmainwindowadaptor.moc:179
#18 0x7fa3d17b4320 in QDBusConnectionPrivate::deliverCall (this=, object=, msg=..., metaTypes=..., slotIdx=)
at ../../include/QtCore/../../src/corelib/tools/qvarlengtharray.h:190
#19 0x7fa3d17b7de3 in QDBusConnectionPrivate::activateCall
(this=this@entry=0x7fa3c4003c00, object=0x5582129c89e0, flags=flags@entry=1361,
msg=...) at qdbusintegrator.cpp:904
#20 0x7fa3d17b8801 in QDBusConnectionPrivate::activateCall (msg=...,
flags=1361, object=, this=0x7fa3c4003c00) at
qdbusintegrator.cpp:853
#21 QDBusConnectionPrivate::activateObject (this=0x7fa3c4003c00, node=...,
msg=..., pathStartPos=) at qdbusintegrator.cpp:1497
#22 0x7fa3d17bac68 in QDBusActivateObjectEvent::placeMetaCall
(this=0x55821378bc90) at qdbusintegrator.cpp:1617
#23 0x7fa3d0708d90 in QObject::event (this=0x558212a99020,
e=0x55821378bc90) at kernel/qobject.cpp:1314
#24 0x7fa3d1e3804e in KXmlGuiWindow::event (this=0x558212a99020,
ev=0x55821378bc90) at
/build/packages/sources-debug/kxmlgui/src/kxmlguiwindow.cpp:219
#25 0x7fa3d11e5d22 in QApplicationPrivate::notify_helper (this=, receiver=0x558212a99020, e=0x55821378bc90) at
kernel/qapplication.cpp:3632
#26 0x7fa3d06daae8 in QCoreApplication::notifyInternal2
(receiver=0x558212a99020, event=0x55821378bc90) at
kernel/qcoreapplication.cpp:1064
#27 0x7fa3d06dded9 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x5582129e83b0) at
kernel/qcoreapplication.cpp:1821
#28 0x7fa3d0737234 in postEventSourceDispatch (s=0x558212a0cb40) at
kernel/qeventdispatcher_glib.cpp:277
#29 0x7fa3cc6b44dc in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#30 0x7fa3cc708749 in ?? () from /usr/lib/libglib-2.0.so.0
#31 0x7fa3cc6b1bc1 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#32 0x7fa3d0736866 in QEventDispatcherGlib::processEvents
(this=0x5582129c33a0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#33

[valgrind] [Bug 444495] dhat/tests/copy fails on s390x

2021-10-27 Thread Paul Floyd

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

Paul Floyd  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||pjfl...@wanadoo.fr
 Resolution|--- |FIXED

--- Comment #4 from Paul Floyd  ---
Patch committed

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

[frameworks-kio] [Bug 439865] kf5.kio.core: couldn't create slave: "Meldung von klauncher: Unbekanntes Protokoll „g“.\n"

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

--- Comment #4 from Ralf Habacker  ---
(In reply to Ralf Habacker from comment #3)
> (In reply to Ahmad Samir from comment #2)
> > Is klauncher available on windows? IIRC kate explicitly runs on windows by
> > forking the slaved (probably setting KDE_FORK_SLAVES=1).

I remember Ahmad was going to look at it, but I haven't heard from him since.

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

[frameworks-kio] [Bug 439865] kf5.kio.core: couldn't create slave: "Meldung von klauncher: Unbekanntes Protokoll „g“.\n"

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

Ralf Habacker  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=426448

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

[kmymoney] [Bug 426448] kmymoney build from binary factory could not create slave on Windows

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

Ralf Habacker  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=439865

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

[kate] [Bug 444506] New: Syntax highlighting on nested parentheses is incorrect

2021-10-27 Thread Gusted

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

Bug ID: 444506
   Summary: Syntax highlighting on nested parentheses is incorrect
   Product: kate
   Version: 21.08.2
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: kwrite
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: postmaster+...@gusted.xyz
  Target Milestone: ---

SUMMARY

The syntax highlighting is incorrect when nested parentheses are present.

STEPS TO REPRODUCE
1. Open up a file that has the `.html` extension type.
2. Paste the following content into the text editor:
```


  

body {
background-color: hsl(0, 0%, calc(95% - 3%)) !important;
}

  
  
  

```
3. Ensure that you have HTML syntax highlighting.

OBSERVED RESULT
`hsl(` is colored purple(breeze dark color scheme). 
The first next following parentheses `3%))` is colored.
^
EXPECTED RESULT
`hsl(` is colored purple(breeze dark color scheme). 
The correct next following corresponding parentheses `3%))` should be colored.
 ^
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.14.14-arch1-1
(available in About System)
KDE Plasma Version: 5.23.1
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2

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

[kdev-python] [Bug 444484] Crash in stylechecker (due to stale ReferencedDUChainTopContext)

2021-10-27 Thread Sven Brauch

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

Sven Brauch  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #1 from Sven Brauch  ---
Thanks for the report. Looking at this code, I agree that several things are
wrong.

If we get around to fixing kdev-python for Python 3.10, we should definitely
have a look here as well...

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

[kdenlive] [Bug 444505] New: Clip speed effect is after searching for missing clips paths in kdenlive 19.12.3

2021-10-27 Thread smihael

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

Bug ID: 444505
   Summary: Clip speed effect is after searching for missing clips
paths in kdenlive 19.12.3
   Product: kdenlive
   Version: 19.12.3
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: smih...@gmail.com
  Target Milestone: ---

SUMMARY

STEPS TO REPRODUCE
1. Add video clip (e.g. ~/Videos/vid.ogv) to timeline, right click and change
speed using the context menu (to e.g. 80%)
2. Save project and exit kdenlive
3. Move clip to a different location (e.g. mv ~/Videos/vid.ogv
~/Videos/Project1/vid.ogv)
4. Reopen kdenlive project. A warning about missing clips will show up, giving
an option to search recursively for missing clips.

OBSERVED RESULT

After clip(s) have been found, clip speed effect is lost.

WORKAROUND

Manually editing .kdenlive file (search and replace vid.ogv to
Project1/vid.ogv.

In newer versions (tested with 21.08.2 snap) this works as intended. Version
19.12.3 is however still the newest version in Ubuntu 20.04 LTS repositories.

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

[krita] [Bug 444504] Can't save a brush preset with brush tip from ABR file in Krita 5.0 without a safe assert

2021-10-27 Thread Tiar

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

Tiar  changed:

   What|Removed |Added

   Keywords||regression, release_blocker
   Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com

--- Comment #1 from Tiar  ---
Assigning to Dmitry because he and Halla are working on embedding resources.
I'm not sure how the preset can even work with ABR file, since when this code
is triggered, I don't think anything gets saved, so I would assume the filename
of the brush tip as well, but maybe there is some failsafe solution.

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

[plasmashell] [Bug 444385] Right-click on GTK icon in systray leads to fast random mouse clicks events

2021-10-27 Thread David Edmundson

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

David Edmundson  changed:

   What|Removed |Added

   Keywords||regression
   Priority|NOR |VHI

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

[krita] [Bug 444504] New: Can't save a brush preset with brush tip from ABR file in Krita 5.0 without a safe assert

2021-10-27 Thread Tiar

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

Bug ID: 444504
   Summary: Can't save a brush preset with brush tip from ABR file
in Krita 5.0 without a safe assert
   Product: krita
   Version: git master (please specify the git hash!)
  Platform: Mint (Ubuntu based)
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Resource Management
  Assignee: krita-bugs-n...@kde.org
  Reporter: tamtamy.tym...@gmail.com
  Target Milestone: ---

SUMMARY
If you try to save a new brush preset with a brush tip coming from an ABR file,
there is a safe assert: SAFE ASSERT (krita): "resource->isSerializable() &&
"embedding non-serializable resources is not yet implemented"" in file
/home/tymon/kritadev/krita/libs/image/brushengine/kis_paintop_preset.cpp, line
270

The resource saves, and it's even usable, until you remove the ABR file with
brush tips.
The same goes if you try to put it into a bundle: first safe assert, then you
can see it gets imported, but only works if you have the ABR file as well.

STEPS TO REPRODUCE
1. Download a, ABR file
2. Make a new brush preset with a brush tip from that file
3. Try to save it as a new brush preset

OBSERVED RESULT
SAFE ASSERT:
SAFE ASSERT (krita): "resource->isSerializable() && "embedding non-serializable
resources is not yet implemented"" in file
/home/tymon/kritadev/krita/libs/image/brushengine/kis_paintop_preset.cpp, line
270

EXPECTED RESULT
No safe assert, everything is saved correctly.

SOFTWARE/OS VERSIONS
Krita

 Version: 5.1.0-prealpha (git b58801a7ae)
 Languages: en_US, en, en_US, en, en_US, en, pl_PL, pl, pl_PL, pl
 Hidpi: true

Qt

  Version (compiled): 5.11.1
  Version (loaded): 5.11.1

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

[plasmashell] [Bug 444385] Right-click on GTK icon in systray leads to fast random mouse clicks events

2021-10-27 Thread David Edmundson

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

David Edmundson  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #11 from David Edmundson  ---
Of course: KWindowSystem::lastInputSerial does nothing on x11 and as the
connection persists that lambda will keep firing.

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

[www.kde.org] [Bug 444503] New: the kde website has an error in the peertube link

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

Bug ID: 444503
   Summary: the kde website has an error in the peertube link
   Product: www.kde.org
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kde-...@kde.org
  Reporter: golfy...@texto-plano.xyz
  Target Milestone: ---

SUMMARY
the kde website has an error in the peertube link

STEPS TO REPRODUCE
1. Go to http://kde.org
2. Go to the corner of the page 
3. Click on the Peertube icon
4. Dont load the URL

OBSERVED RESULT

Dont load the link


EXPECTED RESULT

that the link loads correctly


SOFTWARE/OS VERSIONS
Windows: 
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.

[ark] [Bug 440663] Ark opens a new instance of Dolphin after compression/extraction via Dolphin

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

Seqularise  changed:

   What|Removed |Added

 CC||seqular...@outlook.com

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

[kmymoney] [Bug 426448] kmymoney build from binary factory could not create slave on Windows

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

Ralf Habacker  changed:

   What|Removed |Added

Summary|kmymoney build from binary  |kmymoney build from binary
   |factory could not create|factory could not create
   |slave   |slave on Windows

--- Comment #2 from Ralf Habacker  ---
(In reply to Jack from comment #1)
> Is this still an issue 

yes, the reason is currently unknown.

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

[plasmashell] [Bug 444502] New: Wayland: auto-hiding panel flickering

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

Bug ID: 444502
   Summary: Wayland: auto-hiding panel flickering
   Product: plasmashell
   Version: 5.23.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: gudv...@gmail.com
  Target Milestone: 1.0

Created attachment 142951
  --> https://bugs.kde.org/attachment.cgi?id=142951=edit
Issue recording

SUMMARY

Sometimes panel that set as "Auto hide" starts flickering when I remove mouse
while it tries to hide.

Then it doesn't stop flickering until I make couple of "hover-release" cycles.

It seems like it raises and hiddens by itself while I move mouse cursor
elsewhere on the screen. If I don't move cursor for a while it doesn't flicker.

STEPS TO REPRODUCE
1. Add auto-hiding panel
2. Use Wayland session for a while

OBSERVED RESULT

Panel starts flickering


EXPECTED RESULT

Usable wayland session without epilepsy-enabled panels.


SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Kernel Version: 5.14.14-arch1-1 (64-bit)
Graphics Platform: Wayland
Graphics Processor: AMD VEGAM 

ADDITIONAL INFORMATION

I'd like to make a video

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

[plasmashell] [Bug 444132] Sometimes can't type in kickoff search box (on primary display) when mouse pointer is on secondary display

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

postmaster+...@gusted.xyz changed:

   What|Removed |Added

 CC||postmaster+...@gusted.xyz

--- Comment #1 from postmaster+...@gusted.xyz ---
Hey, since a few days I also seems to be affected by this bug. The steps to
reproduce are spot-on, a minor thing that noticed me that the text will be
typed into the kickoff search box from the secondary display. As well that once
this bug has happens, that it won't "recover" from this bug, until you reboot
again.

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

[Smb4k] [Bug 442187] Smb4K 3.1.0 still has frustrating, old usability glitches and bugs (explained in description). Kills usability.

2021-10-27 Thread flan_suse

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

--- Comment #18 from flan_suse  ---
(In reply to Alexander Reinholdt from comment #17)

> Is that also your experience?

Not always. I'm trying to find a clear pattern, but it's more random than I
first assumed. :(

It can happen when the Main Window is minimized (or hidden to tray), but
sometimes it will not happen.

At first I thought it was unique to non-bookmarked shares, but it can happen to
any share.

I'm going to try some more tests on my end.

If you discover a pattern or hint, I can try to re-produce it on my end as
well. (I'm using two different PCs, one with Intel Iris Xe GPU and the other
with Nvidia GPU, and Smb4K behaves the same way on both computers.)

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

[kwin] [Bug 443990] Kwin memory leak

2021-10-27 Thread Andrew Udvare

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

Andrew Udvare  changed:

   What|Removed |Added

 CC||audv...@gmail.com

--- Comment #8 from Andrew Udvare  ---
Are you getting endless messages in DBus? Maybe related:

Oct 27 14:25:06 limelight dbus-daemon[2019]: [system] Rejected: destination has
a full message queue, 0 matched rules; type="error", sender="(unset)" ((bus))
interface="(unset)" member="(unset)" error
name="org.freedesktop.DBus.Error.ServiceUnknown" requested_reply="1"
destination=":1.39" (uid=1000 pid=2627 comm="/usr/bin/kwin_x11 ")
Oct 27 14:25:06 limelight dbus-daemon[2019]: [system] Rejected: destination has
a full message queue, 0 matched rules; type="error", sender="(unset)" ((bus))
interface="(unset)" member="(unset)" error
name="org.freedesktop.DBus.Error.ServiceUnknown" requested_reply="1"
destination=":1.39" (uid=1000 pid=2627 comm="/usr/bin/kwin_x11 ")
Oct 27 14:25:06 limelight dbus-daemon[2019]: [system] Rejected: destination has
a full message queue, 0 matched rules; type="error", sender="(unset)" ((bus))
interface="(unset)" member="(unset)" error
name="org.freedesktop.DBus.Error.ServiceUnknown" requested_reply="1"
destination=":1.39" (uid=1000 pid=2627 comm="/usr/bin/kwin_x11 ")
Oct 27 14:25:06 limelight dbus-daemon[2019]: [system] Rejected: destination has
a full message queue, 0 matched rules; type="error", sender="(unset)" ((bus))
interface="(unset)" member="(unset)" error
name="org.freedesktop.DBus.Error.ServiceUnknown" requested_reply="1"
destination=":1.39" (uid=1000 pid=2627 comm="/usr/bin/kwin_x11 ")
Oct 27 14:25:06 limelight dbus-daemon[2019]: [system] Rejected: destination has
a full message queue, 0 matched rules; type="error", sender="(unset)" ((bus))
interface="(unset)" member="(unset)" error
name="org.freedesktop.DBus.Error.ServiceUnknown" requested_reply="1"
destination=":1.39" (uid=1000 pid=2627 comm="/usr/bin/kwin_x11 ")
Oct 27 14:25:06 limelight dbus-daemon[2019]: [system] Rejected: destination has
a full message queue, 0 matched rules; type="error", sender="(unset)" ((bus))
interface="(unset)" member="(unset)" error
name="org.freedesktop.DBus.Error.ServiceUnknown" requested_reply="1"
destination=":1.39" (uid=1000 pid=2627 comm="/usr/bin/kwin_x11 ")
Oct 27 14:25:06 limelight dbus-daemon[2019]: [system] Rejected: destination has
a full message queue, 0 matched rules; type="error", sender="(unset)" ((bus))
interface="(unset)" member="(unset)" error
name="org.freedesktop.DBus.Error.ServiceUnknown" requested_reply="1"
destination=":1.39" (uid=1000 pid=2627 comm="/usr/bin/kwin_x11 ")
Oct 27 14:25:06 limelight dbus-daemon[2019]: [system] Rejected: destination has
a full message queue, 0 matched rules; type="error", sender="(unset)" ((bus))
interface="(unset)" member="(unset)" error
name="org.freedesktop.DBus.Error.ServiceUnknown" requested_reply="1"
destination=":1.39" (uid=1000 pid=2627 comm="/usr/bin/kwin_x11 ")
Oct 27 14:25:06 limelight dbus-daemon[2019]: [system] Rejected: destination has
a full message queue, 0 matched rules; type="error", sender="(unset)" ((bus))
interface="(unset)" member="(unset)" error
name="org.freedesktop.DBus.Error.ServiceUnknown" requested_reply="1"
destination=":1.39" (uid=1000 pid=2627 comm="/usr/bin/kwin_x11 ")
Oct 27 14:25:06 limelight dbus-daemon[2019]: [system] Rejected: destination has
a full message queue, 0 matched rules; type="error", sender="(unset)" ((bus))
interface="(unset)" member="(unset)" error
name="org.freedesktop.DBus.Error.ServiceUnknown" requested_reply="1"
destination=":1.39" (uid=1000 pid=2627 comm="/usr/bin/kwin_x11 ")

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

[plasma-nm] [Bug 444500] GlobalProtect SAML request/response ignored

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

--- Comment #1 from jdbar...@isi.edu ---
The saml handshake decoded from base 64:



https://testingurl.oktapreview.com/app/panw_globalprotect/ex*d6/sso/saml;>




  document.getElementById('myform').submit();




and the SAML request itself:

https://vpn.host.net:443/SAML20/SP/ACS;
Destination="https://testingurl.oktapreview.com/app/panw_globalprotect/ex*1d6/sso/saml;
ID="_46**53c" IssueInstant="2021-10-27T18:14:30Z"
ProtocolBinding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
Version="2.0">https://vpn.host.net:443/SAML20/SP

[digikam] [Bug 444501] Face detection, write name tags (metadata) to file - Changes date and time on photo

2021-10-27 Thread Maik Qualmann

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

Maik Qualmann  changed:

   What|Removed |Added

   Severity|major   |normal
 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
digiKam certainly does not change the date metadata in images; when it comes to
the file date, it can be specified in the digiKam setup under metadata that it
is restored. Otherwise we need an image before and after a write of the face
metadata.

Maik

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

[digikam] [Bug 444501] New: Face detection, write name tags (metadata) to file - Changes date and time on photo

2021-10-27 Thread dajomu

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

Bug ID: 444501
   Summary: Face detection, write name tags (metadata) to file -
Changes date and time on photo
   Product: digikam
   Version: 7.3.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Faces-Detection
  Assignee: digikam-bugs-n...@kde.org
  Reporter: dajo...@gmail.com
  Target Milestone: ---

SUMMARY

I am running digikam 7.3 and did a face detection, enabled write name tags to
photo metadata. After tagging several faces I run face recognition and digikam
started to change date and time on photos. I did not discover this immediately.
Since I upload photos to google photos I saw that old photos appeared as taken
in October 2021. Checking the photos, surely the date and time had changed.
There must be something seriously wrong on how digikam processes face
detection/recognition/writing name tags to photos. Not sure what exactly is
causing this and I do not know how to investigate either. 

STEPS TO REPRODUCE
1. Enable writing name tags to photo
2. run detect faces
3. train algorithm by adding nametags
4. run recognize faces

OBSERVED RESULT
photo time and date should change, maybe

EXPECTED RESULT
no change other than adding name tags to photo

SOFTWARE/OS VERSIONS
Windows: 
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.

[plasmashell] [Bug 444385] Right-click on GTK icon in systray leads to fast random mouse clicks events

2021-10-27 Thread vindicator

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

--- Comment #10 from vindicator  ---
? I saw no acknowledgement of the issue, including whether or not the suspected
commit relates to the bug, and I was lending my experience with the issue AND
including log output, whether it affirms the commit or may point elsewhere.

I had no idea my submission would be a hindrance.
Carry-on and ignore if you already know what's up.

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

[krunner] [Bug 444366] KRunner: `desktop console` / `wm console` no longer run anything

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

--- Comment #9 from Alexander Lohnau  ---
Git commit 46eb52dcd8a525b0be3b4a52fdda0dfa19da5dfc by Alexander Lohnau.
Committed on 27/10/2021 at 17:59.
Pushed by alex into branch 'Plasma/5.23'.

interactiveconsole: Allow specifying mode from command line parameter

This is needed for the runner, which has two different keywords for the two
scripting modes


(cherry picked from commit 63bea079c5d614e612ae5e2cafd7f6e8b1aae5a9)

M  +4-3interactiveconsole/interactiveconsole.cpp
M  +3-3interactiveconsole/interactiveconsole.h
M  +22   -1interactiveconsole/main.cpp

https://invent.kde.org/plasma/plasma-workspace/commit/46eb52dcd8a525b0be3b4a52fdda0dfa19da5dfc

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

[gcompris] [Bug 444497] Mining for gold - repeated tapping increases score indefinitely

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

anim...@gmail.com changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/educ
   ||ation/gcompris/commit/24b56
   ||426312eead4c5dcd392fb7ec910
   ||a1388985
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from anim...@gmail.com ---
Git commit 24b56426312eead4c5dcd392fb7ec910a1388985 by Timothée Giet.
Committed on 27/10/2021 at 17:57.
Pushed by timotheegiet into branch 'master'.

mining, fix repetitive click on nugget

M  +2-1src/activities/mining/Mining.qml

https://invent.kde.org/education/gcompris/commit/24b56426312eead4c5dcd392fb7ec910a1388985

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

[krunner] [Bug 444366] KRunner: `desktop console` / `wm console` no longer run anything

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

--- Comment #8 from Alexander Lohnau  ---
Git commit 63bea079c5d614e612ae5e2cafd7f6e8b1aae5a9 by Alexander Lohnau.
Committed on 27/10/2021 at 17:01.
Pushed by alex into branch 'master'.

interactiveconsole: Allow specifying mode from command line parameter

This is needed for the runner, which has two different keywords for the two
scripting modes

M  +4-3interactiveconsole/interactiveconsole.cpp
M  +3-3interactiveconsole/interactiveconsole.h
M  +22   -1interactiveconsole/main.cpp

https://invent.kde.org/plasma/plasma-workspace/commit/63bea079c5d614e612ae5e2cafd7f6e8b1aae5a9

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

[gcompris] [Bug 444497] Mining for gold - repeated tapping increases score indefinitely

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

anim...@gmail.com changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 CC||anim...@gmail.com
 Ever confirmed|0   |1

--- Comment #1 from anim...@gmail.com ---
Thank you for the report, I'm fixing it now so it will be fixed in next
release.

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

[plasma-nm] [Bug 444500] New: GlobalProtect SAML request/response ignored

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

Bug ID: 444500
   Summary: GlobalProtect SAML request/response ignored
   Product: plasma-nm
   Version: 5.22.5
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jgrul...@redhat.com
  Reporter: jdbar...@isi.edu
  Target Milestone: ---

SUMMARY
Globalprotect servers that ask for SAML login do not interactively request
additional information.

STEPS TO REPRODUCE
1. Create connection with openconnect gp plugin for server that requires a SAML
auth
2. Attempt connect
3. Authentication always fails because SAML requests appear to be ignored

OBSERVED RESULT

POST
https://vpn.host.net/global-protect/prelogin.esp?tmp=tmp=4100=Linux
Attempting to connect to server ip.v4.host.addr:443
Connected to ip.v4.host.addr:443
SSL negotiation with vpn.host.net
Connected to HTTPS on vpn.host.net with ciphersuite
(TLS1.2)-(ECDHE-SECP256R1)-(RSA-SHA256)-(AES-256-GCM)
Got HTTP response: HTTP/1.1 200 OK
Date: Fri, 15 Oct 2021 21:17:58 GMT
Content-Type: application/xml; charset=UTF-8
Content-Length: 2104
Connection: keep-alive
ETag: "167860b854d7"
Pragma: no-cache
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Expires: Thu, 19 Nov 1981 08:52:00 GMT
X-FRAME-OPTIONS: DENY
Set-Cookie: PHPSESSID=e39b5e7553f960ebf2f91de23ff3bc5d; secure; HttpOnly
Set-Cookie: PHPSESSID=e39b5e7553f960ebf2f91de23ff3bc5d; secure; HttpOnly
Set-Cookie: PHPSESSID=e39b5e7553f960ebf2f91de23ff3bc5d; secure; HttpOnly
Set-Cookie: PHPSESSID=e39b5e7553f960ebf2f91de23ff3bc5d; secure; HttpOnly
Set-Cookie: PHPSESSID=e39b5e7553f960ebf2f91de23ff3bc5d; secure; HttpOnly
Set-Cookie: PHPSESSID=e39b5e7553f960ebf2f91de23ff3bc5d; secure; HttpOnly
Set-Cookie: PHPSESSID=e39b5e7553f960ebf2f91de23ff3bc5d; secure; HttpOnly
Set-Cookie: PHPSESSID=e39b5e7553f960ebf2f91de23ff3bc5d; secure; HttpOnly
Set-Cookie: PHPSESSID=e39b5e7553f960ebf2f91de23ff3bc5d; secure; HttpOnly
Set-Cookie: PHPSESSID=e39b5e7553f960ebf2f91de23ff3bc5d; secure; HttpOnly
Set-Cookie: PHPSESSID=e39b5e7553f960ebf2f91de23ff3bc5d; secure; HttpOnly
Set-Cookie: PHPSESSID=e39b5e7553f960ebf2f91de23ff3bc5d; path=/; secure;
httponly
Set-Cookie: PHPSESSID=e39b5e7553f960ebf2f91de23ff3bc5d; secure; HttpOnly
Strict-Transport-Security: max-age=31536000;
X-XSS-Protection: 1; mode=block;
X-Content-Type-Options: nosniff
Content-Security-Policy: default-src 'self'; script-src 'self' 'unsafe-inline';
img-src * data:; style-src 'self' 'unsafe-inline';
HTTP body length:  (2104)
SAML POST authentication is required via external script.
When SAML authentication is complete, specify destination form field by
appending :field_name to login URL.
Failed to parse server response
Response was:

Success

false


login through Okta
Username
Password
1
yes0
POST
600
0PG...
... very long stuff ...
...DQo=US




EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
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.

[krunner] [Bug 444366] KRunner: `desktop console` / `wm console` no longer run anything

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

Alexander Lohnau  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
   |ma/plasma-desktop/commit/44 |ma/plasma-desktop/commit/e8
   |23d3b0ab69323ab21b8e1f6e701 |80214da9c1cd7536cbce82395b8
   |4ce7de57ca9 |58811aff2c8

--- Comment #7 from Alexander Lohnau  ---
Git commit e880214da9c1cd7536cbce82395b858811aff2c8 by Alexander Lohnau.
Committed on 27/10/2021 at 17:55.
Pushed by alex into branch 'Plasma/5.23'.

plasma-desktop runner: Fix showing interactive plasma/kwin console

The D-Bus methods do not exist anymore, instead the standalone executable
should be called.


(cherry picked from commit 4423d3b0ab69323ab21b8e1f6e7014ce7de57ca9)

M  +1-0runners/plasma-desktop/CMakeLists.txt
M  +19   -76   runners/plasma-desktop/plasma-desktop-runner.cpp
M  +0-4runners/plasma-desktop/plasma-desktop-runner.h

https://invent.kde.org/plasma/plasma-desktop/commit/e880214da9c1cd7536cbce82395b858811aff2c8

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

[krunner] [Bug 444366] KRunner: `desktop console` / `wm console` no longer run anything

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

Alexander Lohnau  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
  Latest Commit||https://invent.kde.org/plas
   ||ma/plasma-desktop/commit/44
   ||23d3b0ab69323ab21b8e1f6e701
   ||4ce7de57ca9
 Resolution|--- |FIXED

--- Comment #6 from Alexander Lohnau  ---
Git commit 4423d3b0ab69323ab21b8e1f6e7014ce7de57ca9 by Alexander Lohnau.
Committed on 27/10/2021 at 17:03.
Pushed by alex into branch 'master'.

plasma-desktop runner: Fix showing interactive plasma/kwin console

The D-Bus methods do not exist anymore, instead the standalone executable
should be called.

M  +1-0runners/plasma-desktop/CMakeLists.txt
M  +19   -76   runners/plasma-desktop/plasma-desktop-runner.cpp
M  +0-4runners/plasma-desktop/plasma-desktop-runner.h

https://invent.kde.org/plasma/plasma-desktop/commit/4423d3b0ab69323ab21b8e1f6e7014ce7de57ca9

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

[krunner] [Bug 444366] KRunner: `desktop console` / `wm console` no longer run anything

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

--- Comment #5 from Alexander Lohnau  ---
Git commit dbf103451b6b2e6de2a87af706029d2d0759bb1e by Alexander Lohnau.
Committed on 27/10/2021 at 17:18.
Pushed by alex into branch 'master'.

Update docs for plasma interactive console

M  +8-2content/docs/plasma/kwin/_index.md
M  +9-3content/docs/plasma/scripting/_index.md

https://invent.kde.org/documentation/develop-kde-org/commit/dbf103451b6b2e6de2a87af706029d2d0759bb1e

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

[kontact] [Bug 444058] Need to add domain exemption from scam detection

2021-10-27 Thread Laurent Montel

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

Laurent Montel  changed:

   What|Removed |Added

 Status|REOPENED|ASSIGNED

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

[kontact] [Bug 444058] Need to add domain exemption from scam detection

2021-10-27 Thread Laurent Montel

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

Laurent Montel  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Ever confirmed|0   |1
 Status|NEEDSINFO   |REOPENED

--- Comment #6 from Laurent Montel  ---
(In reply to Aaron Williams from comment #5)
> What is triggering it is there are a number of email threads where numerical
> IP addresses are used in URLs, i.e. for specific lab equipment, etc. This is
> why I think being able to disable this scam detection for email from a
> particular domain would be useful. I would include the email, except it
> includes internal corporate information.

I will do it.
I will start on it tomorrow.

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

[kdeconnect] [Bug 444499] New: notify user about "android overcharging protection" and allow disabling it from desktop

2021-10-27 Thread johnathan

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

Bug ID: 99
   Summary: notify user about "android overcharging protection"
and allow disabling it from desktop
   Product: kdeconnect
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: testing1237...@yahoo.com
  Target Milestone: ---

Created attachment 142950
  --> https://bugs.kde.org/attachment.cgi?id=142950=edit
overchaging protection on android

SUMMARY
android 11 has this feature called "overcharging protection" and it kicks in by
default in the night because it expects you to "keep the phone plugged in for
the duration of the night" but i plug it in and i expect a fast 20-30 minutes
fast charge.
problem is the kde connect on my linux desktop does not show that that the
phone is being slowly charged and that i am forced to check the phone screen to
disable this.
i believe the kde connect widget can have this state shown with the charging
label and a button to disable it.


STEPS TO REPRODUCE
1.   check if android 11 has charging protection enabled 
2.  plug in the phone to charge late at night
3.  notice kde connect on desktop does not differentiate regular charging fro
this slow charging

OBSERVED RESULT
kde connect should inform user about the phone being slowly charged and an
option to disable/enable it from the widget/remote places

EXPECTED RESULT


Operating System: KDE neon 5.23
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.3
Kernel Version: 5.11.0-38-generic (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i7-4600U CPU @ 2.10GHz
Memory: 7.7 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4400

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

[plasmashell] [Bug 444498] Make it possible to copy highlighted search results with "Ctrl+C" in Kickoff

2021-10-27 Thread WS

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

WS  changed:

   What|Removed |Added

Summary|Make it possible to copy|Make it possible to copy
   |highlighted search results  |highlighted search results
   |with "Ctrl+C"   |with "Ctrl+C" in Kickoff

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

[plasmashell] [Bug 444498] New: Make it possible to copy highlighted search results with "Ctrl+C"

2021-10-27 Thread WS

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

Bug ID: 98
   Summary: Make it possible to copy highlighted search results
with "Ctrl+C"
   Product: plasmashell
   Version: 5.23.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: k...@davidedmundson.co.uk
  Reporter: ws@outlook.com
CC: mikel5...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

SUMMARY

Kickoff is a convenient way to make small and simple calculations without
having to open a calculator. You can just type "10/5" and the first result is
5, while you can right-click on the result to copy it to clipboard, it would be
way more convenient to be able to copy the highlighted option by simply using
Ctr+C. Using Kickoff search function is already keyboard-heavy swapping to a
mouse just to copy is rather clunky.

STEPS TO REPRODUCE
1. Open Kickoff
2. Type a simple equation, like 10/5
3. Highlight the result
4. Try to copy with "Ctrl+C"

OBSERVED RESULT

Nothing is copied to the clipboard. Requires the user to right-click the result
and select "Copy to Clipboard"

EXPECTED RESULT

Using "Ctrl+C" on a highlighted result should copy it to the clipboard

SOFTWARE/OS VERSIONS

Operating System: openSUSE Tumbleweed 20211021
KDE Plasma Version: 5.23.0
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2

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

[kdenlive] [Bug 414006] Spacer tool is prohibitively slow with many timeline clips

2021-10-27 Thread Egor

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

Egor  changed:

   What|Removed |Added

 CC||e.vakhromt...@gmail.com

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

[gcompris] [Bug 444497] New: Mining for gold - repeated tapping increases score indefinitely

2021-10-27 Thread sasquacz

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

Bug ID: 97
   Summary: Mining for gold - repeated tapping increases score
indefinitely
   Product: gcompris
   Version: unspecified
  Platform: Android
OS: Android 11.x
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jaz...@gmail.com
  Reporter: sasquacz+...@gmail.com
  Target Milestone: ---

Created attachment 142949
  --> https://bugs.kde.org/attachment.cgi?id=142949=edit
Video of bug

SUMMARY
On Android, in the Mining for gold, repeated tapping increases score
indefinitely. See the attached video. 

STEPS TO REPRODUCE
1. Open Mining for gold
2. Zoom to the gold nugget
3. Tap multiple times on the nugget

OBSERVED RESULT
Score is increasing indefinitely instead of 1 point per found nugget. 


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
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.

[plasmashell] [Bug 443975] Dragging favorites icons in the application launcher causes overlapping

2021-10-27 Thread Joseph DeGarmo

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

--- Comment #34 from Joseph DeGarmo  ---
It appears to have finally been fixed.

On Wed, Oct 27, 2021 at 9:41 AM Patrick Silva 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=443975
>
> --- Comment #33 from Patrick Silva  ---
> On Arch Linux, package plasma-desktop 5.23.2-2 fixes the bug on X11.
> But there is a bug possibly related to this fix on Wayland, see bug 89.
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[krunner] [Bug 444366] KRunner: `desktop console` / `wm console` no longer run anything