[plasmashell] [Bug 455476] Plasma panel changes size to 34px and/or flickers while moved between screen edges

2022-06-17 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=455476

Fushan Wen  changed:

   What|Removed |Added

 CC||qydwhotm...@gmail.com

--- Comment #1 from Fushan Wen  ---
Can reproduce flickering but not the size issue.

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

[kwin] [Bug 454086] External USB-C display stop working after upgrading to 5.24.90

2022-06-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=454086

logan.cla...@gmail.com changed:

   What|Removed |Added

 CC||logan.cla...@gmail.com

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

[yakuake] [Bug 440825] open at mouse location not working under Wayland

2022-06-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=440825

logan.cla...@gmail.com changed:

   What|Removed |Added

 CC||logan.cla...@gmail.com

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

[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11

2022-06-17 Thread Natalie Clarius
https://bugs.kde.org/show_bug.cgi?id=442380

--- Comment #92 from Natalie Clarius  ---
... and disabling systemd boot fixed it.

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

[Powerdevil] [Bug 392798] Power button actions should be handled from lock screen

2022-06-17 Thread Jin Liu
https://bugs.kde.org/show_bug.cgi?id=392798

Jin Liu  changed:

   What|Removed |Added

 CC||ad.liu@gmail.com

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

[systemsettings] [Bug 455477] New: Can't set 1280x720 (wayland)

2022-06-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=455477

Bug ID: 455477
   Summary: Can't set 1280x720 (wayland)
   Product: systemsettings
   Version: 5.25.0
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: simad...@gmail.com
  Target Milestone: ---

Application: systemsettings (5.25.0)

Qt Version: 5.15.4
Frameworks Version: 5.95.0
Operating System: Linux 5.18.3-zen1-1-zen x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 5.25.0 [KCrashBackend]

-- Information about the crash:
Can't set 1280x720 (wayland).
Native resolution 1920x1080.

The crash can be reproduced every time.

-- Backtrace:
Application: Параметры системы (systemsettings), signal: Segmentation fault

[KCrash Handler]
#4  0x7ff3262833c4 in KScreen::Mode::id() const () at
/usr/lib/libKF5Screen.so.7
#5  0x7ff32631f1db in  () at /usr/lib/qt/plugins/kcms/kcm_kscreen.so
#6  0x7ff35fd9a268 in  () at /usr/lib/libQt5QmlModels.so.5
#7  0x7ff35fd948b4 in  () at /usr/lib/libQt5QmlModels.so.5
#8  0x7ff36263be43 in  () at /usr/lib/libQt5Qml.so.5
#9  0x7ff362572ae0 in
QV4::QObjectWrapper::setProperty(QV4::ExecutionEngine*, QObject*,
QQmlPropertyData*, QV4::Value const&) () at /usr/lib/libQt5Qml.so.5
#10 0x7ff3625732a6 in
QV4::QObjectWrapper::setQmlProperty(QV4::ExecutionEngine*, QQmlContextData*,
QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, QV4::Value const&)
() at /usr/lib/libQt5Qml.so.5
#11 0x7ff362576337 in QV4::QObjectWrapper::virtualPut(QV4::Managed*,
QV4::PropertyKey, QV4::Value const&, QV4::Value*) () at /usr/lib/libQt5Qml.so.5
#12 0x7ff36254ec5c in QV4::Object::virtualResolveLookupSetter(QV4::Object*,
QV4::ExecutionEngine*, QV4::Lookup*, QV4::Value const&) () at
/usr/lib/libQt5Qml.so.5
#13 0x7ff36258dcbf in  () at /usr/lib/libQt5Qml.so.5
#14 0x7ff362597d64 in  () at /usr/lib/libQt5Qml.so.5
#15 0x7ff36253b7a6 in QV4::Function::call(QV4::Value const*, QV4::Value
const*, int, QV4::ExecutionContext const*) () at /usr/lib/libQt5Qml.so.5
#16 0x7ff36268fb0d in QQmlJavaScriptExpression::evaluate(QV4::CallData*,
bool*) () at /usr/lib/libQt5Qml.so.5
#17 0x7ff362652de1 in QQmlBoundSignalExpression::evaluate(void**) () at
/usr/lib/libQt5Qml.so.5
#18 0x7ff362653d5c in  () at /usr/lib/libQt5Qml.so.5
#19 0x7ff36267656f in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*,
void**) () at /usr/lib/libQt5Qml.so.5
#20 0x7ff3648bdd7d in  () at /usr/lib/libQt5Core.so.5
#21 0x7ff35eca8853 in QQuickComboBox::activated(int) () at
/usr/lib/libQt5QuickTemplates2.so.5
#22 0x7ff35ec2a60a in  () at /usr/lib/libQt5QuickTemplates2.so.5
#23 0x7ff3648be251 in  () at /usr/lib/libQt5Core.so.5
#24 0x7ff35ec1ea5a in QQuickAbstractButtonPrivate::handleRelease(QPointF
const&) () at /usr/lib/libQt5QuickTemplates2.so.5
#25 0x7ff35ec39ab9 in QQuickControl::mouseReleaseEvent(QMouseEvent*) () at
/usr/lib/libQt5QuickTemplates2.so.5
#26 0x7ff362c3c1c9 in QQuickItem::event(QEvent*) () at
/usr/lib/libQt5Quick.so.5
#27 0x7ff365578a7c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#28 0x7ff36488db28 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#29 0x7ff362c4cd93 in
QQuickWindowPrivate::deliverMouseEvent(QQuickPointerMouseEvent*) () at
/usr/lib/libQt5Quick.so.5
#30 0x7ff362c4d7f2 in
QQuickWindowPrivate::deliverPointerEvent(QQuickPointerEvent*) () at
/usr/lib/libQt5Quick.so.5
#31 0x7ff364d55d15 in QWindow::event(QEvent*) () at /usr/lib/libQt5Gui.so.5
#32 0x7ff365578a7c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#33 0x7ff36488db28 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#34 0x7ff363749cae in QQuickWidget::mouseReleaseEvent(QMouseEvent*) () at
/usr/lib/libQt5QuickWidgets.so.5
#35 0x7ff3655af677 in QWidget::event(QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#36 0x7ff365578a7c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#37 0x7ff36557e289 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#38 0x7ff36488db28 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#39 0x7ff36557c287 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) ()
at /usr/lib/libQt5Widgets.so.5
#40 0x7ff3655cd345 in  () at /usr/lib/libQt5Widgets.so.5
#41 0x7ff3655cf0ee in  () at /usr/lib/libQt5Widgets.so.5
#42 0x7ff365578a7c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#43 0x7ff36488db28 in QCoreApplication::notifyInternal2(QObj

[plasmashell] [Bug 455184] Allow to set a video as desktop background

2022-06-17 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=455184
Bug 455184 depends on bug 454984, which changed state.

Bug 454984 Summary: Allow to set an animated image as desktop background
https://bugs.kde.org/show_bug.cgi?id=454984

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

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

[plasmashell] [Bug 454984] Allow to set an animated image as desktop background

2022-06-17 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=454984

Fushan Wen  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Depends on|455193  |
 Status|ASSIGNED|RESOLVED
   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=455193

--- Comment #3 from Fushan Wen  ---
Git commit 6e43d469811222f889eed71ad96e0073ddfbba65 by Fushan Wen.
Committed on 17/06/2022 at 11:26.
Pushed by fusionfuture into branch 'master'.

wallpapers/image: add animated image support
FIXED-IN: 5.26

M  +24   -2wallpapers/image/imagepackage/contents/ui/main.qml
A  +60   -0   
wallpapers/image/imagepackage/contents/ui/mediacomponent/AnimatedImageComponent.qml
[License: GPL(v2.0+)]
A  +41   -0   
wallpapers/image/imagepackage/contents/ui/mediacomponent/BaseMediaComponent.qml
[License: GPL(v2.0+)]
D  +0-64  
wallpapers/image/imagepackage/contents/ui/mediacomponent/ImageComponent.qml
A  +45   -0   
wallpapers/image/imagepackage/contents/ui/mediacomponent/StaticImageComponent.qml
[License: GPL(v2.0+)]
M  +1-0wallpapers/image/plugin/CMakeLists.txt
M  +2-0wallpapers/image/plugin/imageplugin.cpp
A  +20   -0wallpapers/image/plugin/utils/backgroundtype.h [License:
GPL(v2.0+)]
M  +51   -3wallpapers/image/plugin/utils/mediaproxy.cpp
M  +16   -1wallpapers/image/plugin/utils/mediaproxy.h

https://invent.kde.org/plasma/plasma-workspace/commit/6e43d469811222f889eed71ad96e0073ddfbba65


Referenced Bugs:

https://bugs.kde.org/show_bug.cgi?id=455193
[Bug 455193] When kwin_x11 is running, animated wallpapers will cause heavy
(video) memory leak when QT_XCB_GL_INTEGRATION=xcb_glx
-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 455193] When kwin_x11 is running, animated wallpapers will cause heavy (video) memory leak when QT_XCB_GL_INTEGRATION=xcb_glx

2022-06-17 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=455193

Fushan Wen  changed:

   What|Removed |Added

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


Referenced Bugs:

https://bugs.kde.org/show_bug.cgi?id=454984
[Bug 454984] Allow to set an animated image as desktop background
-- 
You are receiving this mail because:
You are watching all bug changes.

[amarok] [Bug 455371] CD Reports 0 Tracks in Amarok

2022-06-17 Thread Heiko Becker
https://bugs.kde.org/show_bug.cgi?id=455371

--- Comment #3 from Heiko Becker  ---
> $dpkg -l | grep audiocd
> ii  kio-audiocd   4:19.12.3-0ubuntu1
> amd64transparent audio CD access for applications using the KDE
> Platform
> 
> I can't find it by the original name, is this the right one?

That seems to be the right one, audiocd-kio is the upstream name. I currently
don't have a CD or a drive with me, but can you try navigating to audiocd:/ in
dolphin or konqueror? If the tracks show up there, it's likely Amarok's fault,
if not, the bug is probably in audiocd-kio.

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

[plasma-nm] [Bug 448153] Unable to access the VPN network in double authentication mode (anyConnect SAML/SSO)

2022-06-17 Thread Ehren Bendler
https://bugs.kde.org/show_bug.cgi?id=448153

--- Comment #2 from Ehren Bendler  ---
That said, external browser use is a tough edge case.

One has to have:
1) The latest OpenConnect, built against a recent version of OpenSSL/GnuTLS
2) A recent version of the AnyConnect server
3) The *server* has to be setup to allow/force external browsers
4) The applet has to be built with the callback added

I can't work on that since my company does not have #3.

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

[kwin] [Bug 449839] Allow closing the selected window with Control-w in the overview effect

2022-06-17 Thread zerocostabstraction
https://bugs.kde.org/show_bug.cgi?id=449839

zerocostabstraction  changed:

   What|Removed |Added

 CC||david.vuckov...@gmail.com

--- Comment #2 from zerocostabstraction  ---
Why not (In reply to Nate Graham from comment #1)
> Would be nice, yeah.

Not sure if this requires a different feature request, but would "right click
to pin" like on the old Display All Windows fit in here too?

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

[kwin] [Bug 435404] Window decorations freeze after resuming hibernated session

2022-06-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=435404

imax@tha-imax.de changed:

   What|Removed |Added

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

--- Comment #2 from imax@tha-imax.de ---
I haven't noticed this bug in a while now. It seems to be fixed! Thanks!

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

[kwin] [Bug 453109] Allow scrolling in the overview to switch between virtual desktops

2022-06-17 Thread zerocostabstraction
https://bugs.kde.org/show_bug.cgi?id=453109

zerocostabstraction  changed:

   What|Removed |Added

 CC||david.vuckov...@gmail.com

--- Comment #4 from zerocostabstraction  ---
(In reply to Prajna Sariputra from comment #2)
> (In reply to Nate Graham from comment #1)
> > Scroll where? Over the activities bar? Or anywhere?
> 
> In GNOME it's practically anywhere, although I personally wouldn't mind if
> it's going to be limited to just the activities bar (assuming that's
> referring to the virtual desktop previews at the top).

Personally I'm not seeing much value if it's only on the activities bar.
Currently, scrolling doesn't do anything. So, save for technical limitations, I
think scrolling anywhere is the better solution, UX wise. 

Personally, I can think of 2 use cases. One is someone wishing to quickly
switch to the next workspace, or a specific workspace, without having to aim
for the right workspace. The other is browsing through windows, closing, or
focusing what piques their interest.  

The way I think about the first situation it is that the cursor is going to be
at a completely random position when the overview is triggered. Therefore, if
we assume that most of the time it's not going on be on the activity/workspace
bar, the user will have to aim the cursor at it. At which point they could just
aim on the workspace they wants to focus. They'd reach the destination faster.

The second usage, the user is going to want to focus a window at some point.
Meaning they aim at the top bar, scroll, then aim the at the window they want
to focus.

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

[kwin] [Bug 450268] Magic Lamp / Slide effects duration speed should always be controlled by global option

2022-06-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=450268

--- Comment #4 from guimarcalsi...@gmail.com ---
(In reply to Sebastian E. from comment #3)
> I guess the reason for those independent duration settings was that the
> magic lamp and slide animations interrupt workflow. The overall animation
> speed might be nice, but maybe you don't want to wait a second for the
> desktop to switch or a window to be restored. At least I don't want to, so I
> now had to set global animation speed to almost instant, because the choices
> available for the desktop switching animation also lack "none". Huge
> improvement!

The user already has the option of disabling those effects entirely if they
interrupt their workflow, so, for that usecase, the setting to independently
control animation speed is redundant.

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

[plasmashell] [Bug 455478] New: Plasma panel gets stuck on the screen if you activate krunner or spectacle while in edit mode

2022-06-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=455478

Bug ID: 455478
   Summary: Plasma panel gets stuck on the screen if you activate
krunner or spectacle while in edit mode
   Product: plasmashell
   Version: 5.25.0
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Keywords: needs_verification
  Severity: minor
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: azazazazazazaz.20...@gmail.com
CC: niccolo.venera...@gmail.com
  Target Milestone: 1.0

Created attachment 149858
  --> https://bugs.kde.org/attachment.cgi?id=149858&action=edit
Picture with 2 screenshots with 1 plasma panel stuck

STEPS TO REPRODUCE
1. Enter edit mode (of a plasma panel)
2. Drag the panel away from the side of the screen, but don't release the mouse
button (keep the panel in that position)
3. Activate krunner or spectacle

OBSERVED RESULT
The panel remains stuck on the screen and maximized apps use the whole screen
and render below the panel (even if the panel is set as always visible where
maximized apps don't cover the panel).

EXPECTED RESULT
Panel should return to the side of the screen where it used to be before the
edit

SOFTWARE/OS VERSIONS 
Operating System: Arch Linux
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.4
Graphics Platform: Wayland

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

[kwin] [Bug 455479] New: [FeatureRequest] Move top level window to another workspace or monitor by dragging from the preview

2022-06-17 Thread zerocostabstraction
https://bugs.kde.org/show_bug.cgi?id=455479

Bug ID: 455479
   Summary: [FeatureRequest] Move top level window to another
workspace or monitor by dragging from the preview
   Product: kwin
   Version: 5.25.0
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: effects-overview
  Assignee: kwin-bugs-n...@kde.org
  Reporter: david.vuckov...@gmail.com
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
This is inspired by the GNOME Overview. The top bar, where the workspaces with
their previews are drawn, currently serves only to focus a workspace. So the
workflow to drag a window from workspace A to workspace C, while currently
focused on workspace B is to:
1. Click on workspace A
2. Reopen the overview
or
Use the Desktop Grid. 

STEPS TO REPRODUCE
1. Open overview
2. Try to drag the previewed window in workspace
3. 

OBSERVED RESULT

Nothing happens.

EXPECTED RESULT

The window, that is being previewed (so far I have noticed that it is always
just 1 window) gets dragged to wherever I want it to.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
Operating System: openSUSE Tumbleweed 20220613
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.2
Kernel Version: 5.18.2-1-default (64-bit)
Graphics Platform: Wayland

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

[kwin] [Bug 427501] kwin remembers which desktop windows are on but not which activity

2022-06-17 Thread Julien Delquié
https://bugs.kde.org/show_bug.cgi?id=427501

Julien Delquié  changed:

   What|Removed |Added

 CC||julien@gmail.com

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

[plasma-pa] [Bug 455401] BUG - HDMI Audio for motherboards internal audio no longer exists

2022-06-17 Thread Ben
https://bugs.kde.org/show_bug.cgi?id=455401

--- Comment #17 from Ben  ---
Created attachment 149859
  --> https://bugs.kde.org/attachment.cgi?id=149859&action=edit
DMESG OUTPUT - splash=silent quiet security=apparmor drm.debug=0x1e
log_buf_len=16MB - Kernel Version 5.18.2-1-default (64-bit)

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

[kwin] [Bug 455480] New: [FeatureRequest] Windows dragged over display borders cannot be placed in a different workspace

2022-06-17 Thread zerocostabstraction
https://bugs.kde.org/show_bug.cgi?id=455480

Bug ID: 455480
   Summary: [FeatureRequest] Windows dragged over display borders
cannot be placed in a different workspace
   Product: kwin
   Version: 5.25.0
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: effects-overview
  Assignee: kwin-bugs-n...@kde.org
  Reporter: david.vuckov...@gmail.com
  Target Milestone: ---

SUMMARY

The title is a mouthful. Let me explain. Currently, I'm focused on workspace 1,
on monitor A. I want to take my window, to monitor B, workspace 4. So what I do
is drag windows across the monitor, into the top-bar where the workspaces are.
The window on my cursor gets smaller and everything, but the window is then
placed in workspace 1, on monitor B. I can then drag it to workspace 4, and it
displays where I want to. 

STEPS TO REPRODUCE
1. Enter overview
2. Drag window to the workspace bar on the other monitor
3. 

OBSERVED RESULT

Window doesn't show up in the non focused workspace on the other monitor, but
on the focused workspace.

EXPECTED RESULT

Window is placed to the workspace I dragged it too, achieving the same
functionality on a single monitor and multi monitor setups. 

Operating System: openSUSE Tumbleweed 20220613
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.2
Kernel Version: 5.18.2-1-default (64-bit)
Graphics Platform: Wayland


ADDITIONAL INFORMATION

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

[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11

2022-06-17 Thread Julien Delquié
https://bugs.kde.org/show_bug.cgi?id=442380

Julien Delquié  changed:

   What|Removed |Added

 CC||julien@gmail.com

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

[kwin] [Bug 455481] New: KWIN crash

2022-06-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=455481

Bug ID: 455481
   Summary: KWIN crash
   Product: kwin
   Version: 5.24.4
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: jo...@muehlencord.de
  Target Milestone: ---

Application: kwin_x11 (5.24.4)

Qt Version: 5.15.3
Frameworks Version: 5.92.0
Operating System: Linux 5.15.0-37-generic x86_64
Windowing System: X11
Distribution: Ubuntu 22.04 LTS
DrKonqi: 5.24.4 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed: switching application by
keyboard. KWIN crashes and restarts automatically

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6  __pthread_kill_implementation (no_tid=0, signo=6, threadid=140223081200064)
at ./nptl/pthread_kill.c:44
#7  __pthread_kill_internal (signo=6, threadid=140223081200064) at
./nptl/pthread_kill.c:78
#8  __GI___pthread_kill (threadid=140223081200064, signo=signo@entry=6) at
./nptl/pthread_kill.c:89
#9  0x7f883f964476 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#10 0x7f883f94a7f3 in __GI_abort () at ./stdlib/abort.c:79
#11 0x7f883270d144 in _iris_batch_flush (batch=0x557af03ea8b8,
file=, line=) at
../src/gallium/drivers/iris/iris_batch.c:1105
#12 0x7f88333767ef in iris_fence_flush (ctx=0x557af03ea3b0,
out_fence=0x557af0d0a300, flags=) at
../src/gallium/drivers/iris/iris_fence.c:267
#13 0x7f8832973832 in fence_sync (ctx=0x7f883007a010, condition=37143,
flags=0) at ../src/mesa/main/syncobj.c:294
#14 0x7f88425c0264 in KWin::WindowThumbnailItem::updateOffscreenTexture()
(this=0x7f88340577a0) at ./src/scripting/thumbnailitem.cpp:432
#15 0x7f8840adc783 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffd7df435f0, r=0x7f88340577a0, this=0x557af12d1290) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#16 doActivate(QObject*, int, void**) (sender=0x557af0292980,
signal_index=3, argv=0x7ffd7df435f0) at kernel/qobject.cpp:3886
#17 0x7f8842597b78 in KWin::Scene::paintScreen(QRegion const&, QRegion
const&, QRegion*, QRegion*, KWin::RenderLoop*, QMatrix4x4 const&)
(this=0x557af0292980, damage=, repaint=...,
updateRegion=0x7ffd7df43790, validRegion=0x7ffd7df43788, renderLoop=, projection=...) at ./src/scene.cpp:282
#18 0x7f884265a170 in KWin::SceneOpenGL::paint(KWin::AbstractOutput*,
QRegion const&, QList const&, KWin::RenderLoop*)
(this=0x557af0292980, output=0x0, damage=..., toplevels=,
renderLoop=0x557af00b6aa0) at ./src/scenes/opengl/scene_opengl.cpp:259
#19 0x7f88424fa071 in KWin::Compositor::composite(KWin::RenderLoop*)
(this=0x557aeff63890, renderLoop=0x557af00b6aa0) at ./src/composite.cpp:633
#20 0x7f8842503a06 in KWin::X11Compositor::composite(KWin::RenderLoop*)
(this=0x557aeff63890, renderLoop=) at ./src/composite.cpp:844
#21 0x7f8840adc783 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffd7df43a90, r=0x557aeff63890, this=0x557af02dfae0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#22 doActivate(QObject*, int, void**) (sender=0x557af00b6aa0,
signal_index=5, argv=0x7ffd7df43a90) at kernel/qobject.cpp:3886
#23 0x7f8840ad5a97 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=, m=m@entry=0x7f8842753300
,
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffd7df43a90)
at kernel/qobject.cpp:3946
#24 0x7f88424b9b16 in KWin::RenderLoop::frameRequested(KWin::RenderLoop*)
(this=, _t1=) at
./obj-x86_64-linux-gnu/src/kwin_autogen/EWIEGA46WW/moc_renderloop.cpp:206
#25 0x7f8842586177 in KWin::RenderLoopPrivate::dispatch()
(this=0x557af00a19a0) at ./src/renderloop.cpp:150
#26 0x7f8840adc783 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffd7df43bb0, r=0x557af00b6aa0, this=0x557af0098230) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#27 doActivate(QObject*, int, void**) (sender=0x557af00a19b8,
signal_index=3, argv=0x7ffd7df43bb0) at kernel/qobject.cpp:3886
#28 0x7f8840ad5a97 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=, m=m@entry=0x7f8840d43300
, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7ffd7df43bb0) at kernel/qobject.cpp:3946
#29 0x7f8840ae07ee in QTimer::timeout(QTimer::QPrivateSignal)
(this=, _t1=...) at .moc/moc_qtimer.cpp:205
#30 0x7f8840ad232f in QObject::event(QEvent*) (this=0x557af00a19b8,
e=0x7ffd7df43d30) at kernel/qobject.cpp:1336
#31 0x7f884007d713 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x557af00a19b8, e=0x7ffd7df43d30) at
kernel/qapplication.cpp:3637
#32 0x7f8840aa4e2a in QCoreApp

[plasmashell] [Bug 455482] New: Secondary monitor loses wallpaper and windows after suspend, primary monitor is fine

2022-06-17 Thread zerocostabstraction
https://bugs.kde.org/show_bug.cgi?id=455482

Bug ID: 455482
   Summary: Secondary monitor loses wallpaper and windows after
suspend, primary monitor is fine
   Product: plasmashell
   Version: 5.25.0
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: david.vuckov...@gmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

SUMMARY

I've got 2 monitors of varying sizes, here's my kscreendoctor output:

Output: 1 Dell Inc. DELL P2419H/9VPQX63 enabled connected  DisplayPort Modes:
0:1920x1080@60*! 1:1680x1050@60 2:1600x900@60 3:1280x1024@75 4:1280x1024@60
5:1440x900@60 6:1280x800@60 7:1152x864@75 8:1280x720@60 9:1024x768@75
10:1024x768@60 11:800x600@75 12:800x600@60 13:640x480@75 14:640x480@60
15:720x400@70 16:1368x768@-1501773 Geometry: 2560,0 1920x1080 Scale: 1
Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown 
Output: 2 HannStar Display Corp HQ272PQD/123456789012 enabled connected primary
HDMI Modes: 0:2560x1440@60*! 1:2560x1080@60 2:2560x1080@60 3:2560x1080@50
4:1920x1200@60 5:1920x1080@60 6:1920x1080@60 7:1920x1080@60 8:1920x1080@50
9:1600x1200@60 10:1680x1050@60 11:1400x1050@60 12:1280x1024@75 13:1280x1024@60
14:1440x900@60 15:1280x960@60 16:1280x800@60 17:1152x864@75 18:1280x720@60
19:1280x720@60 20:1280x720@60 21:1280x720@50 22:1440x576@50 23:1024x768@75
24:1024x768@70 25:1024x768@60 26:832x624@75 27:800x600@75 28:800x600@72
29:800x600@60 30:800x600@56 31:720x576@50 32:720x480@60 33:720x480@60
34:720x480@60 35:720x480@60 36:720x480@60 37:640x480@75 38:640x480@73
39:640x480@67 40:640x480@60 41:640x480@60 42:640x480@60 43:720x400@70
44:1600x900@2058702 Geometry: 0,0 2560x1440 Scale: 1 Rotation: 1 Overscan: 0
Vrr: incapable RgbRange: unknown primaryy

Every day, I put this setup to sleep using the "Sleep" button in Kickoff menu.
Sometimes, I use my power button, that's setup to do the same. After waking up
the machine, I am greeted by nothing but pitch black on my secondary monitor. 
The cursor showed up, but there's no wallpaper. Effects show up, but the
previews are also pitch black. All my windows move to my primary monitor,
however I can easily place them back to the secondary monitor. 

Windows show up just fine the secondary monitor, but the wallpaper doesn't. I
have no panels there, so I don't know what else disappears. 

Restarting the plasma shell with plasmashell --replace fixes this issue. Of
course I'm then forced to rearrange my windows again. 

STEPS TO REPRODUCE
1. Suspend/sleep the computer
2. Wake up and login
3. 

OBSERVED RESULT

Missing wallpaper, windows get thrown to the other monitor. 

EXPECTED RESULT

Windows and my wallpaper stay where they after after waking up from sleep. 

Operating System: openSUSE Tumbleweed 20220613
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.2
Kernel Version: 5.18.2-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 1800X Eight-Core Processor
Memory: 15.6 GiB of RAM
Graphics Processor: AMD Radeon RX Vega
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B450 AORUS ELITE

I will try to reproduce the issue in a bit, and report back with the logs.

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

[kwin] [Bug 455481] KWIN crash

2022-06-17 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=455481

David Edmundson  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |UPSTREAM
 CC||k...@davidedmundson.co.uk

--- Comment #1 from David Edmundson  ---
#11 0x7f883270d144 in _iris_batch_flush (batch=0x557af03ea8b8,
file=, line=) at
../src/gallium/drivers/iris/iris_batch.c:1105
Please can you report this to mesa.

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

[plasmashell] [Bug 455482] Secondary monitor loses wallpaper and windows after suspend, primary monitor is fine

2022-06-17 Thread zerocostabstraction
https://bugs.kde.org/show_bug.cgi?id=455482

--- Comment #1 from zerocostabstraction  ---
(In reply to zerocostabstraction from comment #0)
> SUMMARY
> 
> I've got 2 monitors of varying sizes, here's my kscreendoctor output:
> 
> Output: 1 Dell Inc. DELL P2419H/9VPQX63 enabled connected  DisplayPort
> Modes: 0:1920x1080@60*! 1:1680x1050@60 2:1600x900@60 3:1280x1024@75
> 4:1280x1024@60 5:1440x900@60 6:1280x800@60 7:1152x864@75 8:1280x720@60
> 9:1024x768@75 10:1024x768@60 11:800x600@75 12:800x600@60 13:640x480@75
> 14:640x480@60 15:720x400@70 16:1368x768@-1501773 Geometry: 2560,0 1920x1080
> Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown 
> Output: 2 HannStar Display Corp HQ272PQD/123456789012 enabled connected
> primary HDMI Modes: 0:2560x1440@60*! 1:2560x1080@60 2:2560x1080@60
> 3:2560x1080@50 4:1920x1200@60 5:1920x1080@60 6:1920x1080@60 7:1920x1080@60
> 8:1920x1080@50 9:1600x1200@60 10:1680x1050@60 11:1400x1050@60
> 12:1280x1024@75 13:1280x1024@60 14:1440x900@60 15:1280x960@60 16:1280x800@60
> 17:1152x864@75 18:1280x720@60 19:1280x720@60 20:1280x720@60 21:1280x720@50
> 22:1440x576@50 23:1024x768@75 24:1024x768@70 25:1024x768@60 26:832x624@75
> 27:800x600@75 28:800x600@72 29:800x600@60 30:800x600@56 31:720x576@50
> 32:720x480@60 33:720x480@60 34:720x480@60 35:720x480@60 36:720x480@60
> 37:640x480@75 38:640x480@73 39:640x480@67 40:640x480@60 41:640x480@60
> 42:640x480@60 43:720x400@70 44:1600x900@2058702 Geometry: 0,0 2560x1440
> Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown primaryy
> 
> Every day, I put this setup to sleep using the "Sleep" button in Kickoff
> menu. Sometimes, I use my power button, that's setup to do the same. After
> waking up the machine, I am greeted by nothing but pitch black on my
> secondary monitor.  The cursor showed up, but there's no wallpaper. Effects
> show up, but the previews are also pitch black. All my windows move to my
> primary monitor, however I can easily place them back to the secondary
> monitor. 
> 
> Windows show up just fine the secondary monitor, but the wallpaper doesn't.
> I have no panels there, so I don't know what else disappears. 
> 
> Restarting the plasma shell with plasmashell --replace fixes this issue. Of
> course I'm then forced to rearrange my windows again. 
> 
> STEPS TO REPRODUCE
> 1. Suspend/sleep the computer
> 2. Wake up and login
> 3. 
> 
> OBSERVED RESULT
> 
> Missing wallpaper, windows get thrown to the other monitor. 
> 
> EXPECTED RESULT
> 
> Windows and my wallpaper stay where they after after waking up from sleep. 
> 
> Operating System: openSUSE Tumbleweed 20220613
> KDE Plasma Version: 5.25.0
> KDE Frameworks Version: 5.94.0
> Qt Version: 5.15.2
> Kernel Version: 5.18.2-1-default (64-bit)
> Graphics Platform: Wayland
> Processors: 16 × AMD Ryzen 7 1800X Eight-Core Processor
> Memory: 15.6 GiB of RAM
> Graphics Processor: AMD Radeon RX Vega
> Manufacturer: Gigabyte Technology Co., Ltd.
> Product Name: B450 AORUS ELITE
> 
> I will try to reproduce the issue in a bit, and report back with the logs.

Okay, I couldn't reproduce it without turning off the screens while doing it.
So to add to my steps to reproduce. I turn off the secondary monitor, click
sleep, turn off my primary (turn off in this case means pressing the physical
off button on the monitor) and end up with the situation described above.

I ran plasmashell in a tmux window so I hope this is of any use, if not please
tell me how to get better logs:

file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:69:
TypeError: Cannot read property 'configuration' of null
file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:20:
TypeError: Cannot read property 'configuration' of null
file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:21:
TypeError: Cannot read property 'configuration' of null
file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:22:
TypeError: Cannot read property 'configuration' of null
file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:23:
TypeError: Cannot read property 'configuration' of null
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:322:17:
QML Label: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:322:17:
QML Label: Binding loop detected for property "width"
requesting unexisting screen 1
requesting unexisting screen 1
requesting unexisting screen 0
requesting unexisting screen 0
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:322:17:
QML Label: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:322:17:
QML Label: Binding loop detected for property "width"
requesting unexisting screen 0
requesting unexisting screen 0
file:///usr/share/plasma/plasmoids/org.k

[plasmashell] [Bug 455483] New: Feature Request: Floating panel improvements

2022-06-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=455483

Bug ID: 455483
   Summary: Feature Request: Floating panel improvements
   Product: plasmashell
   Version: 5.25.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: joshuag1...@outlook.com
CC: niccolo.venera...@gmail.com
  Target Milestone: 1.0

Created attachment 149860
  --> https://bugs.kde.org/attachment.cgi?id=149860&action=edit
Image showing the space between the launcher and panel

I have some improvements i'd like to suggest for the floating panel. (if i have
this in the wrong place please let me know)

When a window is maximized the idea of the panel filling the space around it is
nice but it uses way too much space. It would be nice to see the panel go to
the same place and size as if it was not a floating panel (if that makes sense)
as opposed to just coloring the space around it. This ensures that the panel is
not using/wasting space on the screen when an app is fullscreen and also
ensures that the panel still looks how it is expected to look. 

It would also look much better if things like the calendar, application
launcher and status and notification windows were to touch and align themselves
with the panel when they are opened. Hence making them floating as well (so the
application launcher for example would be in contact with the top of the panel
and there would be a space between the launcher and screen edge like with
panel. (I have attached an image so you can see the space i am talking about)

These are just my initial thoughts an opinions really but i think it would
really help integrate the floating panel and make it look like it fits in
better.

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

[kmail2] [Bug 455484] New: Kmail crash while closing and reopening

2022-06-17 Thread Philip McGrath
https://bugs.kde.org/show_bug.cgi?id=455484

Bug ID: 455484
   Summary: Kmail crash while closing and reopening
   Product: kmail2
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: phi...@philipmcgrath.com
  Target Milestone: ---

Application: kmail (5.19.3 (21.12.3))

Qt Version: 5.15.3
Frameworks Version: 5.92.0
Operating System: Linux 5.17.5-76051705-generic x86_64
Windowing System: Wayland
Distribution: Ubuntu 22.04 LTS
DrKonqi: 5.24.4 [KCrashBackend]

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

I tried to close Kmail and reopen it (because some mail seems to be stuck in my
outbox).

- Custom settings of the application:

I'm using the Plasma Wayland session, if that's relevant.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault

[KCrash Handler]
#4  0x7fb8b6442599 in QScopedPointer >::operator-> (this=0x8) at
../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:118
#5  qGetPtrHelper > > (ptr=...) at
../../include/QtCore/../../src/corelib/global/qglobal.h:1143
#6  QAction::d_func (this=0x0) at
../../include/QtWidgets/../../src/widgets/kernel/qaction.h:63
#7  QAction::setText (this=this@entry=0x0, text=...) at kernel/qaction.cpp:714
#8  0x7fb8bedecb3a in KMMainWidget::updateFolderMenu (this=0x7fb7dc13d460)
at ./src/kmmainwidget.cpp:4038
#9  0x7fb8bedf7a85 in KMMainWidget::setupActions (this=0x7fb7dc13d460) at
./src/kmmainwidget.cpp:3400
#10 0x7fb8bedfdcf9 in KMMainWidget::KMMainWidget
(this=this@entry=0x7fb7dc13d460, parent=parent@entry=0x55b5043defa0,
aGUIClient=aGUIClient@entry=0x55b5043df018,
actionCollection=actionCollection@entry=0x55b500da5460, config=...) at
./src/kmmainwidget.cpp:248
#11 0x7fb8beda610f in KMMainWin::KMMainWin (this=this@entry=0x55b5043defa0,
__in_chrg=, __vtt_parm=) at
./src/kmmainwin.cpp:49
#12 0x7fb8bedb7707 in KMKernel::openReader (this=,
onlyCheck=, startInTray=) at
./src/kmkernel.cpp:565
#13 0x7fb8bedbcc37 in KMKernel::action (this=0x7fffa79d5910,
mailto=, check=, startInTray=,
to=..., cc=..., bcc=..., subj=..., body=..., messageFile=..., attachURLs=...,
customHeaders=..., replyTo=..., inReplyTo=..., identity=...) at
./src/kmkernel.cpp:1276
#14 0x7fb8bedbe590 in KMKernel::handleCommandLine (this=,
noArgsOpensReader=noArgsOpensReader@entry=true, args=..., workingDir=...) at
./src/kmkernel.cpp:476
#15 0x55b4f3a7ee76 in KMailApplication::activate (this=,
args=..., workingDir=...) at ./src/main.cpp:100
#16 0x7fb8bef0e137 in
KontactInterface::PimUniqueApplication::qt_static_metacall (_c=,
_id=, _a=0x7fffa79d4de0, _o=0x7fffa79d58f0) at
./obj-x86_64-linux-gnu/src/KF5KontactInterface_autogen/EWIEGA46WW/moc_pimuniqueapplication.cpp:87
#17 KontactInterface::PimUniqueApplication::qt_static_metacall
(_o=_o@entry=0x7fffa79d58f0, _c=_c@entry=QMetaObject::InvokeMetaMethod,
_id=_id@entry=1, _a=_a@entry=0x7fffa79d4de0) at
./obj-x86_64-linux-gnu/src/KF5KontactInterface_autogen/EWIEGA46WW/moc_pimuniqueapplication.cpp:79
#18 0x7fb8bef0e233 in KontactInterface::PimUniqueApplication::qt_metacall
(this=0x7fffa79d58f0, _c=QMetaObject::InvokeMetaMethod, _id=1,
_a=0x7fffa79d4de0) at
./obj-x86_64-linux-gnu/src/KF5KontactInterface_autogen/EWIEGA46WW/moc_pimuniqueapplication.cpp:124
#19 0x7fb8b4fc959b in QDBusConnectionPrivate::deliverCall (this=, object=, msg=..., metaTypes=..., slotIdx=)
at ../../include/QtCore/../../src/corelib/tools/qvarlengtharray.h:190
#20 0x7fb8b4fcd2b7 in QDBusConnectionPrivate::activateCall
(this=this@entry=0x7fb8480052b0, object=0x7fffa79d58f0, flags=81, msg=...) at
./src/dbus/qdbusintegrator.cpp:911
#21 0x7fb8b4fcd87d in QDBusConnectionPrivate::activateCall (msg=...,
flags=, object=, this=0x7fb8480052b0) at
./src/dbus/qdbusintegrator.cpp:853
#22 QDBusConnectionPrivate::activateObject (this=0x7fb8480052b0, node=...,
msg=..., pathStartPos=) at ./src/dbus/qdbusintegrator.cpp:1521
#23 0x7fb8b4fcfdac in QDBusActivateObjectEvent::placeMetaCall
(this=0x55b4f72d1500) at ./src/dbus/qdbusintegrator.cpp:1617
#24 0x7fb8b598440e in QObject::event (this=0x7fffa79d58f0,
e=0x55b4f72d1500) at kernel/qobject.cpp:1314
#25 0x7fb8b6446713 in QApplicationPrivate::notify_helper (this=, receiver=0x7fffa79d58f0, e=0x55b4f72d1500) at
kernel/qapplication.cpp:3637
#26 0x7fb8b5956e2a in QCoreApplication::notifyInternal2
(receiver=0x7fffa79d58f0, event=0x55b4f72d1500) at
kernel/qcoreapplication.cpp:1064
#27 0x7fb8b5959f17 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x55b4f4e91210) at
kernel/qcoreapplication.cpp:1821
#28 0x7fb8b59b0a57 in postEventSourceDispatch (s=0x55b4f4eb9fd0) at
kernel/qeventdispatcher_glib.cpp:277
#29 0x

[plasmashell] [Bug 455323] Ugly margins around de-floated floating panel with any maximized windows

2022-06-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=455323

joshuag1...@outlook.com changed:

   What|Removed |Added

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

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

[plasmashell] [Bug 455483] Feature Request: Floating panel improvements

2022-06-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=455483

joshuag1...@outlook.com changed:

   What|Removed |Added

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

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

[kwin] [Bug 453993] new desktopgrid opening/closing animation is jittering/unsmooth

2022-06-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=453993

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

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

[kwin] [Bug 455422] Desktop grid effects flickers on one screen depending on which VD it's opened

2022-06-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=455422

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #9 from Nate Graham  ---


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

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

[krita] [Bug 446146] Reloading a brush takes noticeably longer than before

2022-06-17 Thread Dmitry Kazakov
https://bugs.kde.org/show_bug.cgi?id=446146

--- Comment #5 from Dmitry Kazakov  ---
Git commit cb85d92790e36e2007be62ba58cfb2b47cec2364 by Dmitry Kazakov.
Committed on 17/06/2022 at 12:19.
Pushed by dkazakov into branch 'master'.

Don't include thumbnails into normal SQL queries

It makes the queries too slow to operate. Instead, the thumbnails are
now fetched using a separate query via resource_id.

It increases the speed of KisAllResourcesModel::resetQuery() from
400ms to 0ms (with a lot of bundles active)

M  +0-1libs/resources/KisResourceModel.cpp
M  +27   -1libs/resources/KisResourceQueryMapper.cpp
M  +0-1libs/resources/KisTagResourceModel.cpp

https://invent.kde.org/graphics/krita/commit/cb85d92790e36e2007be62ba58cfb2b47cec2364

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

[krita] [Bug 446146] Reloading a brush takes noticeably longer than before

2022-06-17 Thread Dmitry Kazakov
https://bugs.kde.org/show_bug.cgi?id=446146

--- Comment #6 from Dmitry Kazakov  ---
Git commit 9936558e9e9978046d42de1af2f08de1b7b3c178 by Dmitry Kazakov.
Committed on 17/06/2022 at 12:19.
Pushed by dkazakov into branch 'master'.

Add an index for resource signature

We need this index to be able to group-by (name,filename,md5)
efficiently. This index makes the query in the KisResourceModel
execute almost instantly.

This patch increases the schema version from 0.0.16 to 0.0.17!

M  +30   -4libs/resources/KisResourceCacheDb.cpp
M  +1-0libs/resources/sql.qrc
A  +1-0libs/resources/sql/create_index_resources_signature.sql

https://invent.kde.org/graphics/krita/commit/9936558e9e9978046d42de1af2f08de1b7b3c178

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

[krita] [Bug 446146] Reloading a brush takes noticeably longer than before

2022-06-17 Thread Dmitry Kazakov
https://bugs.kde.org/show_bug.cgi?id=446146

Dmitry Kazakov  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/grap
   ||hics/krita/commit/c6c6f0d82
   ||44353a259096410800dba339b53
   ||6e4e

--- Comment #7 from Dmitry Kazakov  ---
Git commit c6c6f0d8244353a259096410800dba339b536e4e by Dmitry Kazakov.
Committed on 17/06/2022 at 12:19.
Pushed by dkazakov into branch 'master'.

Don't reset the query when reloading a resource

We don't have to call reset query here, because reloading a resource
doesn't change any database content.

M  +7-2libs/resources/KisResourceModel.cpp

https://invent.kde.org/graphics/krita/commit/c6c6f0d8244353a259096410800dba339b536e4e

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

[krita] [Bug 446146] Reloading a brush takes noticeably longer than before

2022-06-17 Thread Dmitry Kazakov
https://bugs.kde.org/show_bug.cgi?id=446146

--- Comment #8 from Dmitry Kazakov  ---
Git commit a536585328ee4a9778d62b8d859635490383b554 by Dmitry Kazakov.
Committed on 17/06/2022 at 13:34.
Pushed by dkazakov into branch 'krita/5.1'.

Don't include thumbnails into normal SQL queries

It makes the queries too slow to operate. Instead, the thumbnails are
now fetched using a separate query via resource_id.

It increases the speed of KisAllResourcesModel::resetQuery() from
400ms to 0ms (with a lot of bundles active)

M  +0-1libs/resources/KisResourceModel.cpp
M  +27   -1libs/resources/KisResourceQueryMapper.cpp
M  +0-1libs/resources/KisTagResourceModel.cpp

https://invent.kde.org/graphics/krita/commit/a536585328ee4a9778d62b8d859635490383b554

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

[krita] [Bug 446146] Reloading a brush takes noticeably longer than before

2022-06-17 Thread Dmitry Kazakov
https://bugs.kde.org/show_bug.cgi?id=446146

Dmitry Kazakov  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap
   |hics/krita/commit/c6c6f0d82 |hics/krita/commit/33698b4b8
   |44353a259096410800dba339b53 |c5e5ebcbedf9a5655a0599dad6c
   |6e4e|02e8

--- Comment #9 from Dmitry Kazakov  ---
Git commit 33698b4b8c5e5ebcbedf9a5655a0599dad6c02e8 by Dmitry Kazakov.
Committed on 17/06/2022 at 13:34.
Pushed by dkazakov into branch 'krita/5.1'.

Don't reset the query when reloading a resource

We don't have to call reset query here, because reloading a resource
doesn't change any database content.

M  +7-2libs/resources/KisResourceModel.cpp

https://invent.kde.org/graphics/krita/commit/33698b4b8c5e5ebcbedf9a5655a0599dad6c02e8

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

[krita] [Bug 446146] Reloading a brush takes noticeably longer than before

2022-06-17 Thread Dmitry Kazakov
https://bugs.kde.org/show_bug.cgi?id=446146

--- Comment #10 from Dmitry Kazakov  ---
Git commit af1722234b5c3579169e82378a63bd43d309ef0e by Dmitry Kazakov.
Committed on 17/06/2022 at 13:34.
Pushed by dkazakov into branch 'krita/5.1'.

Add an index for resource signature

We need this index to be able to group-by (name,filename,md5)
efficiently. This index makes the query in the KisResourceModel
execute almost instantly.

This patch increases the schema version from 0.0.16 to 0.0.17!

M  +30   -4libs/resources/KisResourceCacheDb.cpp
M  +1-0libs/resources/sql.qrc
A  +1-0libs/resources/sql/create_index_resources_signature.sql

https://invent.kde.org/graphics/krita/commit/af1722234b5c3579169e82378a63bd43d309ef0e

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

[kwin] [Bug 449839] Allow closing the selected window with Control-w in the overview effect

2022-06-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=449839

--- Comment #3 from Nate Graham  ---
Another bug report for that would be best, yeah.

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

[krita] [Bug 447298] Closing documents takes significantly longer than before

2022-06-17 Thread Dmitry Kazakov
https://bugs.kde.org/show_bug.cgi?id=447298

Dmitry Kazakov  changed:

   What|Removed |Added

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

--- Comment #8 from Dmitry Kazakov  ---
I think this bug can now be closed as resolved, since the document is now
closed in a fraction of a blink. There is still a small delay (about 300ms) on
deactivation/activation of bundles, but that is a different bug.

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

[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11

2022-06-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=442380

Nate Graham  changed:

   What|Removed |Added

Summary|Session restore does not|With systemd boot, session
   |remember which windows were |restore does not remember
   |on which virtual desktop on |which windows were on which
   |X11 |virtual desktop on X11
Version|5.24.2  |5.25.0

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

[systemsettings] [Bug 455469] Setting virtual desktop name to empty crashes entire system

2022-06-17 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=455469

Patrick Silva  changed:

   What|Removed |Added

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

--- Comment #1 from Patrick Silva  ---


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

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

[kwin] [Bug 422319] virtual desktop locks up systems if desktop names are removed in Virtual Desktops System Settings Module

2022-06-17 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=422319

Patrick Silva  changed:

   What|Removed |Added

 CC||zolbere...@gmail.com

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

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

[kwin] [Bug 455485] New: [FeatureRequest] Missing pin window option like the old Display All Windows had

2022-06-17 Thread zerocostabstraction
https://bugs.kde.org/show_bug.cgi?id=455485

Bug ID: 455485
   Summary: [FeatureRequest] Missing pin window option like the
old Display All Windows had
   Product: kwin
   Version: 5.25.0
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: effects-overview
  Assignee: kwin-bugs-n...@kde.org
  Reporter: david.vuckov...@gmail.com
  Target Milestone: ---

SUMMARY

Right click to pin a window to all workspaces would be nice. Like in the old
effect


STEPS TO REPRODUCE
1. Open overview
2. Press right click
3. 

OBSERVED RESULT

Clicked window isn't pinned

EXPECTED RESULT

Clicked window is pinned to all workspaces

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.

[kwin] [Bug 455404] Window vanishes when dragging window to another screen

2022-06-17 Thread galder
https://bugs.kde.org/show_bug.cgi?id=455404

--- Comment #4 from galder  ---
same here,
I couldn't reproduce.
Operating System: Kubuntu 21.10
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.2
Kernel Version: 5.13.0-51-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz
Memory: 15.5 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1060/PCIe/SSE2

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

[Spectacle] [Bug 455455] [wayland] Application icon appears beside mouse when taking a silent screenshot

2022-06-17 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=455455

Patrick Silva  changed:

   What|Removed |Added

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

--- Comment #1 from Patrick Silva  ---


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

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

[frameworks-kglobalaccel] [Bug 454937] On Wayland, launch feedback always triggers for global-shortcut-launched apps that have `StartupNotify=false` in their desktop file

2022-06-17 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=454937

Patrick Silva  changed:

   What|Removed |Added

 CC||indecisiveautomator@gmail.c
   ||om

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

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

[kwin] [Bug 455404] Window vanishes when dragging window to another screen

2022-06-17 Thread galder
https://bugs.kde.org/show_bug.cgi?id=455404

--- Comment #5 from galder  ---
sorry this issue for Wayland.
ignore my message :)

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

[kwin] [Bug 455473] Kwin does not remember window sizes on opening

2022-06-17 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=455473

Patrick Silva  changed:

   What|Removed |Added

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

--- Comment #1 from Patrick Silva  ---


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

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

[kwin] [Bug 437089] On Wayland, Windows that were closed when maximized will open in the maximized position, but not the maximized state

2022-06-17 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=437089

Patrick Silva  changed:

   What|Removed |Added

 CC||tro...@free.fr

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

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

[kwin] [Bug 455404] Window vanishes when dragging window to another screen

2022-06-17 Thread postix
https://bugs.kde.org/show_bug.cgi?id=455404

--- Comment #6 from postix  ---
(In reply to galder from comment #5)
> sorry this issue for Wayland.
> ignore my message :)

Can you please test this on Wayland?

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

[kwin] [Bug 455486] New: Dragging window always swaps workspaces

2022-06-17 Thread zerocostabstraction
https://bugs.kde.org/show_bug.cgi?id=455486

Bug ID: 455486
   Summary: Dragging window always swaps workspaces
   Product: kwin
   Version: 5.25.0
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: effects-desktop-grid
  Assignee: kwin-bugs-n...@kde.org
  Reporter: david.vuckov...@gmail.com
  Target Milestone: ---

SUMMARY

Workspaces are swapped every time, meaning I can't use display grid to change
the workspace of a window.

STEPS TO REPRODUCE
1. Open Desktop Grid Effect
2. Attempt to drag window to different workspace 
3. 

OBSERVED RESULT

Workspace is swapped

EXPECTED RESULT

The window I clicked on is moved to a different workspace

Operating System: openSUSE Tumbleweed 20220613
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.2
Kernel Version: 5.18.2-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 1800X Eight-Core Processor
Memory: 15.6 GiB of RAM
Graphics Processor: AMD Radeon RX Vega
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B450 AORUS ELITE

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

[frameworks-kirigami] [Bug 453959] SwipeListItem actions no longer visible in NeoChat's settings page

2022-06-17 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=453959

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

--- Comment #3 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/frameworks/kirigami/-/merge_requests/574

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

[kwin] [Bug 455486] Dragging window always swaps workspaces

2022-06-17 Thread smit
https://bugs.kde.org/show_bug.cgi?id=455486

smit  changed:

   What|Removed |Added

 CC||smit1...@gmail.com

--- Comment #1 from smit  ---
This started happening since new qml rewrite

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

[plasmashell] [Bug 455487] New: Starting an empty session, plasmashell keeps crashing until I open a program

2022-06-17 Thread Julien Delquié
https://bugs.kde.org/show_bug.cgi?id=455487

Bug ID: 455487
   Summary: Starting an empty session, plasmashell keeps crashing
until I open a program
   Product: plasmashell
   Version: 5.25.0
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: julien@gmail.com
  Target Milestone: 1.0

SUMMARY

When I open a session on X11, without any saved session, plasmashell keeps
crashing until I open a program (for example Konsole).
This issue does not happen at all using Wayland.

juin 17 15:54:34 pasokon.maison plasmashell[6924]: ASSERT: "from.isValid()" in
file
/var/tmp/portage/dev-qt/qtcore-5.15.4-r3/work/qtbase-everywhere-src-5.15.4/src/corelib/itemmodels/qconcatenatetablesproxymodel.cpp,
line 623
juin 17 15:54:34 pasokon.maison plasmashell[6924]: 25 --
exe=/usr/bin/plasmashell
juin 17 15:54:34 pasokon.maison plasmashell[6924]: 13 -- platform=xcb
juin 17 15:54:34 pasokon.maison plasmashell[6924]: 11 -- display=:0
juin 17 15:54:34 pasokon.maison plasmashell[6924]: 20 -- appname=plasmashell
juin 17 15:54:34 pasokon.maison plasmashell[6924]: 17 -- apppath=/usr/bin
juin 17 15:54:34 pasokon.maison plasmashell[6924]: 9 -- signal=6
juin 17 15:54:34 pasokon.maison plasmashell[6924]: 9 -- pid=6924
juin 17 15:54:34 pasokon.maison plasmashell[6924]: 18 -- appversion=5.25.0
juin 17 15:54:34 pasokon.maison plasmashell[6924]: 19 -- programname=Plasma
juin 17 15:54:34 pasokon.maison plasmashell[6924]: 31 --
bugaddress=sub...@bugs.kde.org
juin 17 15:54:34 pasokon.maison plasmashell[6924]: 12 -- startupid=0
juin 17 15:54:34 pasokon.maison plasmashell[6924]: KCrash: crashing...
crashRecursionCounter = 2
juin 17 15:54:34 pasokon.maison plasmashell[6924]: KCrash: Application Name =
plasmashell path = /usr/bin pid = 6924
juin 17 15:54:34 pasokon.maison plasmashell[6924]: KCrash: Arguments:
/usr/bin/plasmashell --no-respawn
juin 17 15:54:34 pasokon.maison kwin_x11[5654]: QMetaProperty::read: Unable to
handle unregistered datatype 'KWin::SessionState' for property
'KWin::EffectsHandlerImplX11::sessionState'
juin 17 15:54:34 pasokon.maison kwin_x11[5654]: qt.qpa.xcb: QXcbConnection: XCB
error: 3 (BadWindow), sequence: 24256, resource id: 31457306, major code: 18
(ChangeProperty), minor code: 0
juin 17 15:54:34 pasokon.maison kwin_x11[5654]: qt.qpa.xcb: QXcbConnection: XCB
error: 3 (BadWindow), sequence: 24257, resource id: 4194315, major code: 15
(QueryTree), minor code: 0
juin 17 15:54:34 pasokon.maison kwin_x11[5654]: qt.qpa.xcb: QXcbConnection: XCB
error: 3 (BadWindow), sequence: 24280, resource id: 4194325, major code: 15
(QueryTree), minor code: 0
juin 17 15:54:34 pasokon.maison plasmashell[6924]: KCrash: Attempting to start
/usr/lib64/libexec/drkonqi
juin 17 15:54:34 pasokon.maison kded5[5653]: Service 
"org.kde.StatusNotifierHost-6924" unregistered
juin 17 15:54:34 pasokon.maison systemd[615]: plasma-ksystemstats.service:
Consumed 2.979s CPU time.
juin 17 15:54:35 pasokon.maison plasma_waitforname[6732]:
org.kde.knotifications: WaitForName: Service was not registered within timeout
juin 17 15:54:35 pasokon.maison dbus-daemon[1396]: [session uid=1000 pid=1396]
Activated service 'org.kde.KSplash' failed: Process org.kde.KSplash exited with
status 1
juin 17 15:54:35 pasokon.maison kstart5[7033]: Omitting both --window and
--windowclass arguments is not recommended
juin 17 15:54:35 pasokon.maison systemd[615]: Started konsole.
juin 17 15:54:35 pasokon.maison kwin_x11[5654]: qt.qpa.xcb: QXcbConnection: XCB
error: 3 (BadWindow), sequence: 24883, resource id: 31457289, major code: 18
(ChangeProperty), minor code: 0


STEPS TO REPRODUCE
1. Open a session (empty session)

OBSERVED RESULT

Plasmashell keeps crashing and no panel is displayed until I launch a program
(e.g. Konsole).
Plasmashell keeps crashing again if I close the last program running in the
session.

EXPECTED RESULT

Plasmashell does not crash and I can see the panel.

SOFTWARE/OS VERSIONS
Operating System: Gentoo Linux 2.8
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.4
Kernel Version: 5.18.5-gentoo-x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-9700K CPU @ 3.60GHz
Memory: 31.3 Gio of RAM
Graphics Processor: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2

ADDITIONAL INFORMATION

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

[krita] [Bug 455135] Flatten image + Zoom in/out = crash

2022-06-17 Thread Dmitry Kazakov
https://bugs.kde.org/show_bug.cgi?id=455135

Dmitry Kazakov  changed:

   What|Removed |Added

 CC||dimul...@gmail.com
   Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com

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

[krita] [Bug 455135] Flatten image + Zoom in/out = crash

2022-06-17 Thread Dmitry Kazakov
https://bugs.kde.org/show_bug.cgi?id=455135

Dmitry Kazakov  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/grap
   ||hics/krita/commit/40784a06a
   ||162ed5319d2f6fa178dd847f64c
   ||6a95
 Status|CONFIRMED   |RESOLVED

--- Comment #5 from Dmitry Kazakov  ---
Git commit 40784a06a162ed5319d2f6fa178dd847f64c6a95 by Dmitry Kazakov.
Committed on 17/06/2022 at 14:21.
Pushed by dkazakov into branch 'master'.

Fix the link in KisReferenceImagesDecoration after image flattening

KisReferenceImagesDecoration tracks the layers of the image to always
have the pointer to the decorations layer in cache. We should also
update this link on image flattening.

M  +12   -0libs/ui/KisReferenceImagesDecoration.cpp
M  +1-0libs/ui/KisReferenceImagesDecoration.h

https://invent.kde.org/graphics/krita/commit/40784a06a162ed5319d2f6fa178dd847f64c6a95

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

[krita] [Bug 455135] Flatten image + Zoom in/out = crash

2022-06-17 Thread Dmitry Kazakov
https://bugs.kde.org/show_bug.cgi?id=455135

Dmitry Kazakov  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap
   |hics/krita/commit/40784a06a |hics/krita/commit/b40aa0070
   |162ed5319d2f6fa178dd847f64c |dc52079d681172d20c251b02dee
   |6a95|6efc

--- Comment #6 from Dmitry Kazakov  ---
Git commit b40aa0070dc52079d681172d20c251b02dee6efc by Dmitry Kazakov.
Committed on 17/06/2022 at 14:22.
Pushed by dkazakov into branch 'krita/5.1'.

Fix the link in KisReferenceImagesDecoration after image flattening

KisReferenceImagesDecoration tracks the layers of the image to always
have the pointer to the decorations layer in cache. We should also
update this link on image flattening.

M  +12   -0libs/ui/KisReferenceImagesDecoration.cpp
M  +1-0libs/ui/KisReferenceImagesDecoration.h

https://invent.kde.org/graphics/krita/commit/b40aa0070dc52079d681172d20c251b02dee6efc

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

[kwin] [Bug 455268] Can't drag only a single window from one virtual desktop to another

2022-06-17 Thread Fabian Vogt
https://bugs.kde.org/show_bug.cgi?id=455268

Fabian Vogt  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---
 CC||fab...@ritter-vogt.de

--- Comment #11 from Fabian Vogt  ---
While that patch fixes it for dragging windows with the mouse cursor, it's
still broken when using the touchscreen here, always dragging all windows of
that virtual desktop.

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

[plasmashell] [Bug 455372] Windows snap to taskbar edges

2022-06-17 Thread Jeremi Campagna
https://bugs.kde.org/show_bug.cgi?id=455372

--- Comment #4 from Jeremi Campagna  ---
The issue is still present in 5.25 and framework 5.95

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

[ark] [Bug 454320] Trying to decrypt password protected rar fails.

2022-06-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=454320

2wxsy5823...@opayq.com changed:

   What|Removed |Added

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

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

[ark] [Bug 455467] Ark attempts to unpack a .rar file despite unrar not being installed. Gives a generic error instead of requesting the unrar package to be installed.

2022-06-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=455467

2wxsy5823...@opayq.com changed:

   What|Removed |Added

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

--- Comment #1 from 2wxsy5823...@opayq.com ---
(See also Bug 454320 Comment 2)

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

[kdenlive] [Bug 452377] Cannot find python3, please install it on your system.

2022-06-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=452377

panv...@gmail.com changed:

   What|Removed |Added

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

--- Comment #14 from panv...@gmail.com ---
Hey everyone, thanks for all the help.
I guess I'm giving up. I'm gonna try Kdenlive once more when I have Windows11.
Changing it to resolved..

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

[kwin] [Bug 455404] Window vanishes when dragging window to another screen

2022-06-17 Thread galder
https://bugs.kde.org/show_bug.cgi?id=455404

--- Comment #7 from galder  ---
Unfortunately when I try to use my compiled version of 5.25.0 in Kubuntu 21.10.
I cant login in wayland from sddm.
I got black screens. Probably related to my custom setup. Anyway Ill try with
the normal wayland session and then replace plasma desktop
that was working.

source ~/kde/build/plasma-desktop/prefix.sh
~/kde/usr/bin/plasmashell --replace

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

[kwin] [Bug 455488] New: Desktop grid moves full desktop instead of single windows

2022-06-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=455488

Bug ID: 455488
   Summary: Desktop grid moves full desktop instead of single
windows
   Product: kwin
   Version: 5.25.0
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: compositing
  Assignee: kwin-bugs-n...@kde.org
  Reporter: barbolan...@gmail.com
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Have serveral windows open in a virtual desktop
2. Use desktop grid and click on a single windows
3. Try to move a single window to another virtual desktop

OBSERVED RESULT
Instead of moving a single windows the whole virtual desktop is switched

EXPECTED RESULT
A single window should be moved to a new virtual desktop

SOFTWARE/OS VERSIONS

Linux/KDE Plasma:  Kde Neon 
(available in About System)
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.95.0
Qt Version: 5.14.5

ADDITIONAL INFORMATION

Kernel version: 5.13.0-51- generic (64 bits)
Graphics platform: X11
Graphics processor: AMD Radeon Vega 8 Graphics

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

[krita] [Bug 452739] Outline drag previews for the rectangle and ellipse tools constantly stutter around from their actual effective position, especially at high zoom levels

2022-06-17 Thread Dmitry Kazakov
https://bugs.kde.org/show_bug.cgi?id=452739

Dmitry Kazakov  changed:

   What|Removed |Added

 CC||dimul...@gmail.com
   Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com

--- Comment #4 from Dmitry Kazakov  ---
The problem in the implementation of m_moveCenter functionality, which doesn't
work well with rounding of the corners

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

[kwin] [Bug 455489] New: Window Open/Close Animation cannot trigger right away when just switching to another virtual desktop

2022-06-17 Thread Angelo Fallaria
https://bugs.kde.org/show_bug.cgi?id=455489

Bug ID: 455489
   Summary: Window Open/Close Animation cannot trigger right away
when just switching to another virtual desktop
   Product: kwin
   Version: 5.25.0
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: effects-various
  Assignee: kwin-bugs-n...@kde.org
  Reporter: ba.falla...@gmail.com
  Target Milestone: ---

Created attachment 149861
  --> https://bugs.kde.org/attachment.cgi?id=149861&action=edit
Shows the animations not playing for a few seconds after switching virtual
desktops

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

When I switch to another virtual desktop, the window open/close animations do
not trigger when I open/close a window for around three seconds after
switching. They only start to trigger once I'm in the virtual desktop for more
than three seconds. This is inconvenient as I switch between virtual desktops
all the time in my workflow.

STEPS TO REPRODUCE
1. Set a Window Open/Close Animation in Desktop Effects settings
1. Switch from one virtual desktop to another
2. Open/close a window within ~2-3 seconds from switching

OBSERVED RESULT

Windows do not trigger their open/close animations, as if no open/close
animation was set in the settings.

EXPECTED RESULT

Windows trigger their open/close animations as usual.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Artix Linux 5.18.3-zen1-1-zen (64-bit)
(available in About System)
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.4

ADDITIONAL INFORMATION

Graphics Platform: Wayland
Mesa version: 22.1.1-2
CPU/GPU: Ryzen 7 5700G

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

[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11

2022-06-17 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=442380

--- Comment #93 from David Edmundson  ---
The DBus call to kwin to say which session to use fails.

In my logs I see ksmserver make the call before:

Jun 17 15:36:56 david-desktop systemd[922]: plasma-kwin_x11.service: D-Bus name
org.kde.KWin now owned by :1.10


In fact we see plasma-restoresession.service super duper early - could explain
som kwallet issues.

It's set to be:
"After=graphical-session.target" which I didn't think should count as up until
p-w.target is

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

[kwin] [Bug 455435] KWin crashes if a shader effect is applied to the desktop-switcher overlay [Wayland-only]

2022-06-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=455435

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||5.25.1
 CC||n...@kde.org

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

[systemsettings] [Bug 455490] New: [wayland] Can't activate Overview effect with screen edge on display with a focused fullscreen app

2022-06-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=455490

Bug ID: 455490
   Summary: [wayland] Can't activate Overview effect with screen
edge on display with a focused fullscreen app
   Product: systemsettings
   Version: 5.25.0
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: indecisiveautoma...@gmail.com
  Target Milestone: ---

SUMMARY
On a display that has a focused fullscreen application, such as a fullscreen
YouTube video on a fullscreen game, the Overview effect cannot be activated
using a screen edge if that application is the one currently in focus. It can
be activated using a screen edge on another display, such as a display above
another, but not from the screen edge where there is a fullscreen application.
If another application is in focus, such as one on another display, then the
Overview effect screen edge will activate correctly as well.

This was not the case in previous Plasma releases.


STEPS TO REPRODUCE
1. Fullscreen an application on a display with an Overview effect hot corner
2. Attempt to activate hot corner
3. Blue effect will appear in the screen edge but the Overview effect will not
activate

OBSERVED RESULT
Screen Edge Overview effect cannot be activated on that display if a fullscreen
application is in focus  


EXPECTED RESULT
Screen Edge Overview effect should always be able to be activated like in
previous Plasma releases


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.18.3-zen1-1-zen (64bit)
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.4

ADDITIONAL INFORMATION

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

[kwin] [Bug 455491] New: Corner bug still affecting Konsole when using transparent and blurred background

2022-06-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=455491

Bug ID: 455491
   Summary: Corner bug still affecting Konsole when using
transparent and blurred background
   Product: kwin
   Version: 5.25.0
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: decorations
  Assignee: kwin-bugs-n...@kde.org
  Reporter: m.orl...@gmail.com
  Target Milestone: ---

Created attachment 149862
  --> https://bugs.kde.org/attachment.cgi?id=149862&action=edit
Example of corner glitch in Konsole

SUMMARY
When using transparent and blurred background in Konsole, there's the same
graphical glitch as in Bug 395725 behind rounded corners.

STEPS TO REPRODUCE
1. Open Konsole color scheme settings.
2. Enable transparent background and blur.

OBSERVED RESULT
There's a glitch behind Konsole rounded corners (see attachment).

EXPECTED RESULT
The corners in Konsole should be round, as they are with other apps.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.4

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

[krita] [Bug 452739] Outline drag previews for the rectangle and ellipse tools constantly stutter around from their actual effective position, especially at high zoom levels

2022-06-17 Thread Dmitry Kazakov
https://bugs.kde.org/show_bug.cgi?id=452739

Dmitry Kazakov  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/grap
   ||hics/krita/commit/4f0137a12
   ||0cb6cfdfaba19a3ea7d12537a1c
   ||32a4

--- Comment #5 from Dmitry Kazakov  ---
Git commit 4f0137a120cb6cfdfaba19a3ea7d12537a1c32a4 by Dmitry Kazakov.
Committed on 17/06/2022 at 14:49.
Pushed by dkazakov into branch 'master'.

Fix dizzy outline in rectangle and ellipse tools

We don't have to apply `m_dragCenter` offset after adjusting
the rectangle endpoints.

M  +1-7libs/ui/tool/kis_tool_rectangle_base.cpp

https://invent.kde.org/graphics/krita/commit/4f0137a120cb6cfdfaba19a3ea7d12537a1c32a4

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

[krita] [Bug 452739] Outline drag previews for the rectangle and ellipse tools constantly stutter around from their actual effective position, especially at high zoom levels

2022-06-17 Thread Dmitry Kazakov
https://bugs.kde.org/show_bug.cgi?id=452739

Dmitry Kazakov  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap
   |hics/krita/commit/4f0137a12 |hics/krita/commit/82766ef02
   |0cb6cfdfaba19a3ea7d12537a1c |5ded4b3345a67eed57bf0370980
   |32a4|530f

--- Comment #6 from Dmitry Kazakov  ---
Git commit 82766ef025ded4b3345a67eed57bf0370980530f by Dmitry Kazakov.
Committed on 17/06/2022 at 14:50.
Pushed by dkazakov into branch 'krita/5.1'.

Fix dizzy outline in rectangle and ellipse tools

We don't have to apply `m_dragCenter` offset after adjusting
the rectangle endpoints.

M  +1-7libs/ui/tool/kis_tool_rectangle_base.cpp

https://invent.kde.org/graphics/krita/commit/82766ef025ded4b3345a67eed57bf0370980530f

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

[kate] [Bug 446355] Esc key closes terminal panel when Vim is open in Insert mode when using Git.

2022-06-17 Thread silopolis
https://bugs.kde.org/show_bug.cgi?id=446355

silopolis  changed:

   What|Removed |Added

 CC||silopo...@gmail.com
 Status|RESOLVED|REPORTED
 Resolution|NOT A BUG   |---

--- Comment #3 from silopolis  ---
Hi,

Running 22.04.1 on Debian Testing I had a similar behavior.

As this was apparently already set. I thought I had to add `vim.nox` to the
list too but didn't seem to work (I didn't restart kate). Then tried a couple
of things each time launching a new Kate... And it seems to me that it was only
when I unchecked and checked back the `Hide Konsole on Esc` box and applied
that it finally behaved as intended.

In the end the original Kate instance finally worked, without restarting, and
back with the original settings !

TY
J

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

[plasmashell] [Bug 455492] New: [wayland] Application Dashboard no longer has highlighted background

2022-06-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=455492

Bug ID: 455492
   Summary: [wayland]  Application Dashboard no longer has
highlighted background
   Product: plasmashell
   Version: 5.24.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Application Menu (Kicker)
  Assignee: plasma-b...@kde.org
  Reporter: indecisiveautoma...@gmail.com
  Target Milestone: 1.0

SUMMARY
When mousing over an application in the Application Dashboard it no longer has
a hovered background when the mouse is over it to show you which application is
currently highlighted.


STEPS TO REPRODUCE
1. Open Application Dashboard
2. Hover over an application
3. No highlighted background

OBSERVED RESULT
No background on application icons when they're hovered over


EXPECTED RESULT
Applications should have a background when the mouse is over them


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.18.3-zen1-1-zen (64bit)
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.4

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 455492] [wayland] Application Dashboard no longer has highlighted background

2022-06-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=455492

indecisiveautoma...@gmail.com changed:

   What|Removed |Added

Version|5.24.5  |5.25.0

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

[plasmashell] [Bug 455276] Menu doesn't open sometimes (pressing Win key). Also happens with tray icons and other panel popups

2022-06-17 Thread Julien Delquié
https://bugs.kde.org/show_bug.cgi?id=455276

Julien Delquié  changed:

   What|Removed |Added

 CC||julien@gmail.com

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

[plasmashell] [Bug 455276] Menu doesn't open sometimes (pressing Win key). Also happens with tray icons and other panel popups

2022-06-17 Thread Julien Delquié
https://bugs.kde.org/show_bug.cgi?id=455276

--- Comment #4 from Julien Delquié  ---
Same here :
juin 17 16:52:21 pasokon.maison plasmashell[8995]: kf.plasma.quick: Couldn't
create KWindowShadow for PlasmaQuick::Dialog(0x562c5d66cbd0)
juin 17 16:52:21 pasokon.maison plasmashell[8995]: kf.plasma.quick: Couldn't
create KWindowShadow for PlasmaQuick::Dialog(0x562c5d66cbd0)
juin 17 16:52:21 pasokon.maison plasmashell[8995]: kf.plasma.quick: Couldn't
create KWindowShadow for PlasmaQuick::Dialog(0x562c5d66cbd0)
juin 17 16:52:24 pasokon.maison plasmashell[8995]: kf.plasma.quick: Couldn't
create KWindowShadow for PlasmaQuick::Dialog(0x562c5d66cbd0)
juin 17 16:52:24 pasokon.maison plasmashell[8995]: kf.plasma.quick: Couldn't
create KWindowShadow for PlasmaQuick::Dialog(0x562c5d66cbd0)
juin 17 16:52:24 pasokon.maison plasmashell[8995]: kf.plasma.quick: Couldn't
create KWindowShadow for PlasmaQuick::Dialog(0x562c5d66cbd0)
juin 17 16:52:26 pasokon.maison plasmashell[8995]: kf.plasma.quick: Couldn't
create KWindowShadow for PlasmaQuick::Dialog(0x562c5d66cbd0)
juin 17 16:52:26 pasokon.maison plasmashell[8995]: kf.plasma.quick: Couldn't
create KWindowShadow for PlasmaQuick::Dialog(0x562c5d66cbd0)
juin 17 16:52:26 pasokon.maison plasmashell[8995]: kf.plasma.quick: Couldn't
create KWindowShadow for PlasmaQuick::Dialog(0x562c5d66cbd0)

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

[plasmashell] [Bug 455493] New: Wallpaper doesn't display preview when clicking on images

2022-06-17 Thread Neil Padgett
https://bugs.kde.org/show_bug.cgi?id=455493

Bug ID: 455493
   Summary: Wallpaper doesn't display preview when clicking on
images
   Product: plasmashell
   Version: 5.25.0
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Image Wallpaper
  Assignee: plasma-b...@kde.org
  Reporter: neilpadgett...@gmail.com
CC: notm...@gmail.com, qydwhotm...@gmail.com
  Target Milestone: 1.0

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
Clicking wallpaper thumbnails in "Configure Desktop and Wallpaper" does not
show preview on the desktop. Have to click OK/Apply to see new wallpaper (just
like previous versions of Plasma).

STEPS TO REPRODUCE
1. Open "Configure Desktop and Wallpaper"
2. Click any thumbnail
3. Plasma 5.25 should then instantly preview that wallpaper on the Desktop

OBSERVED RESULT
Wallpaper does not update/preview.

EXPECTED RESULT
Wallpaper should update/preview on Desktop. Before clicking OK/Apply to accept
change.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: openSUSE Tumbleweed 20220614
(available in About System)
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

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

[kwin] [Bug 455353] Regression: filtering is per screen instead of global

2022-06-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=455353

Nate Graham  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/plas
   ||ma/kwin/commit/13e3630127b3
   ||2c7a052528174d8b7220c4dd71b
   ||1
   Version Fixed In||5.25.1
 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED

--- Comment #2 from Nate Graham  ---
Git commit 13e3630127b32c7a052528174d8b7220c4dd71b1 by Nate Graham, on behalf
of Marco Martin.
Committed on 17/06/2022 at 14:55.
Pushed by ngraham into branch 'master'.

effects/windowview: Search on all screens

use a property of the effect itself to store the search text
so all the views will search for the same thing at the same time.
FIXED-IN: 5.25.1

M  +10   -2src/effects/windowview/qml/main.qml
M  +3-0src/effects/windowview/windowvieweffect.h

https://invent.kde.org/plasma/kwin/commit/13e3630127b32c7a052528174d8b7220c4dd71b1

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

[frameworks-kiconthemes] [Bug 445804] kiconthemes 5.88.0 inconsistent icon changes

2022-06-17 Thread firewalker
https://bugs.kde.org/show_bug.cgi?id=445804

--- Comment #25 from firewalker  ---
Still present in 5.95.0

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

[plasmashell] [Bug 454984] Allow to set an animated image as desktop background

2022-06-17 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=454984

Fushan Wen  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/plas
   ||ma/plasma-workspace/commit/
   ||6e43d469811222f889eed71ad96
   ||e0073ddfbba65
   Version Fixed In||5.26

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

[kwin] [Bug 455353] Regression: filtering is per screen instead of global

2022-06-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=455353

Nate Graham  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
   |ma/kwin/commit/13e3630127b3 |ma/kwin/commit/62282a91cc41
   |2c7a052528174d8b7220c4dd71b |8ab7abf2ac240b3dbb154504f1f
   |1   |e

--- Comment #3 from Nate Graham  ---
Git commit 62282a91cc418ab7abf2ac240b3dbb154504f1fe by Nate Graham, on behalf
of Marco Martin.
Committed on 17/06/2022 at 15:12.
Pushed by ngraham into branch 'Plasma/5.25'.

effects/windowview: Search on all screens

use a property of the effect itself to store the search text
so all the views will search for the same thing at the same time.
FIXED-IN: 5.25.1


(cherry picked from commit 13e3630127b32c7a052528174d8b7220c4dd71b1)

M  +10   -2src/effects/windowview/qml/main.qml
M  +3-0src/effects/windowview/windowvieweffect.h

https://invent.kde.org/plasma/kwin/commit/62282a91cc418ab7abf2ac240b3dbb154504f1fe

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

[systemsettings] [Bug 455444] Custom Shortcuts are gone in 5.25 on Wayland

2022-06-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=455444

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #3 from Nate Graham  ---
Custom Shortcuts are unreliable on Wayland so we have hidden the page by
default for Wayland users. You can add any shortcuts you'd like using the
Shortcuts page instead.

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

[systemsettings] [Bug 455015] KWin scripts no longer checkable/uncheckable

2022-06-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=455015

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||5.25.1

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

[systemsettings] [Bug 455444] Custom Shortcuts are gone in 5.25 on Wayland

2022-06-17 Thread Fabio Lenherr
https://bugs.kde.org/show_bug.cgi?id=455444

--- Comment #4 from Fabio Lenherr  ---
How would I go about doing that? I have found no way to connect a command to a
shortcut with the regular shortcuts page.
There is a custom shortcuts service page, but it doesn't offer any
configuration other than changing the hotkey for already created commands.
This seems a bit strange, all custom shortcuts were fine for me. 
Now I have to start X11 just to add and edit, while using them is still
possible on wayland.

I urge you to reconsider this decision.

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

[kwin] [Bug 455494] New: [wayland] Clicking an item in an unfocused window requires two clicks, one to focus the window and the other for the action

2022-06-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=455494

Bug ID: 455494
   Summary: [wayland] Clicking an item in an unfocused window
requires two clicks, one to focus the window and the
other for the action
   Product: kwin
   Version: 5.25.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: indecisiveautoma...@gmail.com
  Target Milestone: ---

SUMMARY
This does not apply for every window, but for some windows such as System
Settings, if it's unfocused, clicking on an item in the System Settings such as
one of the buttons or menu items requires two clicks. The first click focuses
the window and the second click is needed to perform the action. So when
clicking on the "Appearance"  option in the unfocused System Settings window,
the first click focuses the window and you have to click again to actually open
the "Appearance" menu. This even applies to things like the scrollbar, which
are particularly jarring.

This does not apply for all applications however. Some such as Dolphin and
System Settings work fine. However a number of KDE apps exhibit this behaviour
(System Settings, Info Center, Discover). Xwayland apps also seem to
consistently exhibit this, a number of games running under Xwayland will need
an extra click.


STEPS TO REPRODUCE
1. Open System Settings (I am using this purely as an example because I know it
happens with this one, but it is not exclusive to System Settings)
2. Unfocus the window
3. Refocus it by attempting to click on an item in the System Settings
4. The window will regain focus but the option you clicked will not do anything
until you click again.

OBSERVED RESULT
Some unfocused KDE applications need a second click to perform an action and
their action is not performed in the same click that gives them focus. 


EXPECTED RESULT
Clicking on a window should focus it and perform the action the mouse was
clicking on.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.18.3-zen1-1-zen (64bit)
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.4

ADDITIONAL INFORMATION
Have not tried X11

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

[plasmashell] [Bug 448479] [Systemd, Wayland] kwallet-pam no longer unlocks wallet on login

2022-06-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=448479

Nate Graham  changed:

   What|Removed |Added

Summary|kwallet-pam no longer works |[Systemd, Wayland]
   |on Wayland  |kwallet-pam no longer
   ||unlocks wallet on login

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

[plasmashell] [Bug 433223] [Systemd, X11] KWallet doesn't unlock automatically when user logs in

2022-06-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=433223

Nate Graham  changed:

   What|Removed |Added

Summary|[Systemd]KWallet doesn't|[Systemd, X11] KWallet
   |unlock automatically when   |doesn't unlock
   |user logs in|automatically when user
   ||logs in

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

[plasmashell] [Bug 433223] [Systemd, X11] KWallet doesn't unlock automatically when user logs in

2022-06-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=433223

Nate Graham  changed:

   What|Removed |Added

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

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

[plasmashell] [Bug 448479] [Systemd, Wayland] kwallet-pam no longer unlocks wallet on login

2022-06-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=448479

Nate Graham  changed:

   What|Removed |Added

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

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

[systemsettings] [Bug 455136] Granular control over which apps and packages auto-update

2022-06-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=455136

--- Comment #2 from harsim...@rtunerfjqq.com ---
(In reply to Nate Graham from comment #1)
> We already have the ability to automatically install *all* updates (not just
> security updates) when they come in.
> 
> A configurable update check interval (which would affect the frequency of
> automatic updates) is tracked at Bug 416193.


As a workaround, will this work? To receive security updates automatically, I
unmark/uncheck the non-security repositories in
Discover -> Settings 

[  ] Focal (main) - neon
[  ] Focal (main) Sources - neon
[  ] Focal (main restricted universe multiverse) - preinstalled-pool
[  ] Focal (main restricted universe multiverse) 
[x] Focal security (main restricted universe multiverse) 
[  ] Focal (main restricted universe multiverse) 
[  ] Focal updates (main restricted universe multiverse) 

But once a month, it will look like this:

[x] Focal (main) - neon
[x] Focal (main) Sources - neon
[x] Focal (main restricted universe multiverse) - preinstalled-pool
[x] Focal (main restricted universe multiverse) 
[x] Focal security (main restricted universe multiverse) 
[x] Focal (main restricted universe multiverse) 
[x] Focal updates (main restricted universe multiverse) 


Now my problem are the bunch of flatpaks installed that are being updated ASAP.
I only want my Chromium and Firefox flatpaks to automatically update, not the
not so security vulnera

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

[systemsettings] [Bug 455444] Custom Shortcuts are gone in 5.25 on Wayland

2022-06-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=455444

--- Comment #5 from Nate Graham  ---
You make a script file and then assign a global shortcut to run it. It's a
little clumsy, I know. We will improve it in the future.

Ultimately having two systems to do the same thing is silly, and on Wayland
we've decided to focus on only one to de-confuse the UI.

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

[kwin] [Bug 454086] External USB-C display stop working after upgrading to 5.24.90

2022-06-17 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=454086

Bug Janitor Service  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|ASSIGNED

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

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

[kwin] [Bug 454086] External USB-C display stop working after upgrading to 5.24.90

2022-06-17 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=454086

--- Comment #32 from Zamundaaa  ---
Unfortunately the kernel doesn't seem to do any logging for when the buffers
are still on the wrong GPU, but this MR should finally fix the problem

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

[kwin] [Bug 455404] Window vanishes when dragging window to another screen

2022-06-17 Thread galder
https://bugs.kde.org/show_bug.cgi?id=455404

--- Comment #8 from galder  ---
just tested in wayland.
the window disappears in wayland 5.24.4 and 5.25.0.  x11 is fine.

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

[plasmashell] [Bug 453554] turning one monitor off kills the panel configuration of the second monitor

2022-06-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=453554

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||5.25
 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #7 from Nate Graham  ---
Cool, thanks! Can you file a new bug report for the new issue?

Out of curiosity, does the wallpaper show up after 10 seconds or so?

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

[kscreenlocker] [Bug 454074] Clock missing on lock screen

2022-06-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=454074

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||5.25
   Keywords||regression

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

[kde] [Bug 455495] New: Volume is the same for all devices

2022-06-17 Thread David
https://bugs.kde.org/show_bug.cgi?id=455495

Bug ID: 455495
   Summary: Volume is the same for all devices
   Product: kde
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: david.cortes.riv...@gmail.com
  Target Milestone: ---

SUMMARY
Volume used to be remember on a per-device basis. After the last KDE updates,
it isn't anymore.

STEPS TO REPRODUCE
1. If using a laptop, connect some headphones or speakers so as to have at
least two volume sources. If a non-laptop, try having an HDMI screen with audio
or similar plus some speakers.
2. Change the general volume from its default value.
3. Disconnect the currently active sound device (e.g. the headphones) so as to
make it switch to a different output source (e.g. the built-in speakers).

OBSERVED RESULT
Volume remains as it was set for the earlier audio device, but now applied to
the new device, for which the same value is unlikely to be optimal.

EXPECTED RESULT
It should remember that the audio device to which it switched had a different
volume the last time it was used. Different audio devices have very different
meanings for different volume levels. You can make people hurt their ears
badly.

SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.2
Kernel Version: 5.18.0-1-amd64 (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 2700 Eight-Core Processor
Memory: 15.6 GiB of RAM
Graphics Processor: AMD VEGA10

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

[kwin] [Bug 455404] Window vanishes when dragging window to another screen

2022-06-17 Thread galder
https://bugs.kde.org/show_bug.cgi?id=455404

--- Comment #9 from galder  ---
about my environment in wayland. I don't think is using nvidia dedicated gpu
like it does in X11.
But I believe this is issue nvidia issue with current kubuntu 21.10 version.
So I don't know if my tests are valid for Wayland.

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

[kwin] [Bug 455496] New: Touchpad gestures don't work at all

2022-06-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=455496

Bug ID: 455496
   Summary: Touchpad gestures don't work at all
   Product: kwin
   Version: 5.25.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: el...@seznam.cz
  Target Milestone: ---

SUMMARY
***
After update from Plasma 5.24 to Plasma 5.25 I tried all touchpad gestures, but
none of them works.
***

Really don't know how to reproduce it on different computer. Is there some
package I might be missing? Or can I attach relevant configuration?

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux Unstable
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.4
Kernel Version: 5.18.5-1-MANJARO (64-bit)
Graphics Platform: X11

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

<    1   2   3   4   5   >