from:"hexchain"

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

--- Comment #5 from hexchain  ---
In Weston, WezTerm exits with an error when maximizing:

22:56:01.832  ERROR  wezterm_gui > running message loop:
Error while flushing display: Broken pipe (os error 32); terminating

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

[kwin] [Bug 479943] On Wayland, maximizing WezTerm is glitchy when the Maximize effect is enabled

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

--- Comment #4 from hexchain  ---
You'll need the latest nightly version. The last released version does not work
on Wayland under KWin 6, due to a bug in its GUI toolkit:
https://github.com/wez/wezterm/issues/3996

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

[kwin] [Bug 479943] On Wayland, maximizing WezTerm is glitchy when the Maximize effect is enabled

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

--- Comment #2 from hexchain  ---
Created attachment 164982
  --> https://bugs.kde.org/attachment.cgi?id=164982=edit
WezTerm maximize animation

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

[kwin] [Bug 479943] On Wayland, maximizing WezTerm is glitchy when the Maximize effect is enabled

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

--- Comment #1 from hexchain  ---
Created attachment 164980
  --> https://bugs.kde.org/attachment.cgi?id=164980=edit
Wayland debug log

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

[kwin] [Bug 479943] New: On Wayland, maximizing WezTerm is glitchy when the Maximize effect is enabled

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

Bug ID: 479943
   Summary: On Wayland, maximizing WezTerm is glitchy when the
Maximize effect is enabled
Classification: Plasma
   Product: kwin
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@hexchain.org
  Target Milestone: ---

SUMMARY
Please see the attached screencast.

STEPS TO REPRODUCE
1. Download WezTerm nightly (the last released version does not work on Wayland
under KWin 6, due to a bug in its GUI tookit)
2. Start WezTerm, and maximize.

OBSERVED RESULT
I don't know how to describe it, sorry. Please see the attachment.

EXPECTED RESULT
The window should maximize normally.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 5.249.0
Qt Version: 6.7.0
Kernel Version: 6.7.0-arch3-1 (64-bit)
Graphics Platform: Wayland
Graphics Processor: AMD Radeon Graphics

KWin fd2e77317f99b159bb023420051be17383520bae

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

[kwin] [Bug 476870] Enter key not released after toggling WCG in a terminal

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

hexchain  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|REPORTED|RESOLVED

--- Comment #1 from hexchain  ---
I cannot reproduce this anymore with KWin
fd2e77317f99b159bb023420051be17383520bae.

Toggling WCG does not make the screen flash anymore, but toggling HDR does.
Either way, the Enter key no longer appears to be held down in both cases.

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

[kwin] [Bug 479558] krfb-virtualmonitor causes kwin_wayland to crash

2024-01-16 Thread hexchain

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

hexchain  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED

--- Comment #5 from hexchain  ---
I guess that commit should be a fix for the other bug 475296, not this one?

I can still reproduce this bug (with the same backtrace) in KWin ed339de953.

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

[kwin] [Bug 479250] Screen randomly freezes for a short while when opening tabbox/overview

2024-01-15 Thread hexchain

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

hexchain  changed:

   What|Removed |Added

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

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

[dolphin] [Bug 478866] With Qt 6.7, every QDockWidget panel is enabled in every new window

2024-01-11 Thread hexchain

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

hexchain  changed:

   What|Removed |Added

 CC||k...@hexchain.org

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

[frameworks-qqc2-desktop-style] [Bug 464069] Graphical Corruption Around Certain Widgets with fractional scale factor

2024-01-09 Thread hexchain

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

--- Comment #21 from hexchain  ---
Created attachment 164778
  --> https://bugs.kde.org/attachment.cgi?id=164778=edit
Text rendering problems in systemsettings

The change fixed all the artifacts around controls (thanks!), but some texts
still show rendering problems.

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

[kwin] [Bug 479558] New: krfb-virtualmonitor causes kwin_wayland to crash

2024-01-08 Thread hexchain

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

Bug ID: 479558
   Summary: krfb-virtualmonitor causes kwin_wayland to crash
Classification: Plasma
   Product: kwin
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@hexchain.org
  Target Milestone: ---

SUMMARY
Launching krfb-virtualmonitor causes kwin_wayland to crash. This is similar to
475296 but the backtrace looks very different, hence opening another bug.

STEPS TO REPRODUCE
Launch krfb-virtualmonitor, e.g.: krfb-virtualmonitor --name test --scale 1
--port 9876 --password 12345678 --resolution 1920x1080

OBSERVED RESULT
krfb-virtualmonitor crashes first and takes kwin_wayland along with it.

Backtrace for KWin:

#0  KWin::ClientConnection::client() const (this=0x563b91c21d00) at
/home/hexchain/kde/src/kwin/src/wayland/clientconnection.cpp:119
#1  0x7f96a8722087 in
KWin::Display::getConnection(wl_client*)::$_0::operator()(KWin::ClientConnection*)
const (c=0x563b91c21d00, this=) at
/home/hexchain/kde/src/kwin/src/wayland/display.cpp:203
#2 
__gnu_cxx::__ops::_Iter_pred::operator()::const_iterator>(QList::const_iterator)
(__it=..., this=) at
/usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/13.2.1/../../../../include/c++/13.2.1/bits/predefined_ops.h:318
#3  std::__find_if::const_iterator,
__gnu_cxx::__ops::_Iter_pred
>(QList::const_iterator,
QList::const_iterator,
__gnu_cxx::__ops::_Iter_pred,
std::random_access_iterator_tag)
(__first=..., __last=..., __pred=...) at
/usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/13.2.1/../../../../include/c++/13.2.1/bits/stl_algobase.h:2102
#4  std::__find_if::const_iterator,
__gnu_cxx::__ops::_Iter_pred
>(QList::const_iterator,
QList::const_iterator,
__gnu_cxx::__ops::_Iter_pred)
(__first=..., __last=..., __pred=...)
at
/usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/13.2.1/../../../../include/c++/13.2.1/bits/stl_algobase.h:2117
#5  std::find_if::const_iterator,
KWin::Display::getConnection(wl_client*)::$_0>(QList::const_iterator,
QList::const_iterator,
KWin::Display::getConnection(wl_client*)::$_0) (__first=..., __last=...,
__pred=...)
at
/usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/13.2.1/../../../../include/c++/13.2.1/bits/stl_algo.h:3923
#6  KWin::Display::getConnection(wl_client*) (this=0x563b90632510,
client=0x563b917ac260) at
/home/hexchain/kde/src/kwin/src/wayland/display.cpp:202
#7  0x7f96a872aafd in
KWin::FilteredDisplayPrivate::globalFilterCallback(wl_client const*, wl_global
const*, void*) (client=0x563b917ac260, global=0x563b9063d4d0,
data=0x563b90632610) at
/home/hexchain/kde/src/kwin/src/wayland/filtered_display.cpp:24
#8  0x7f96a756486c in wl_global_is_visible (global=0x563b9063d4d0,
client=0x563b917ac260) at ../../src/wayland/src/wayland-server.c:952
#9  display_get_registry (client=0x563b917ac260, resource=,
id=) at ../../src/wayland/src/wayland-server.c:1046
#10 0x7f96a3f534f6 in ffi_call_unix64 () at ../src/x86/unix64.S:104
#11 0x7f96a3f4ff5e in ffi_call_int (cif=cif@entry=0x7ffd40a7c860,
fn=, rvalue=, avalue=,
closure=closure@entry=0x0) at ../src/x86/ffi64.c:673
#12 0x7f96a3f52b73 in ffi_call (cif=cif@entry=0x7ffd40a7c860, fn=, rvalue=rvalue@entry=0x0, avalue=avalue@entry=0x7ffd40a7c930) at
../src/x86/ffi64.c:710
#13 0x7f96a7568923 in wl_closure_invoke (closure=0x563b91d24dd0,
flags=, target=, opcode=1, data=)
at ../../src/wayland/src/connection.c:1031
#14 0x7f96a75636bc in wl_client_connection_data (fd=,
mask=, data=0x563b917ac260) at
../../src/wayland/src/wayland-server.c:438
#15 0x7f96a7566732 in wl_event_loop_dispatch (loop=0x563b9066dda0,
timeout=) at ../../src/wayland/src/event-loop.c:1104
#16 0x7f96a8721b19 in KWin::Display::dispatchEvents() (this=) at /home/hexchain/kde/src/kwin/src/wayland/display.cpp:117
#17 0x7f96a57beaa9 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffd40a7cf00, r=0x563b90632510, this=0x563b90c85280, this=,
r=, a=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0-beta1/src/corelib/kernel/qobjectdefs_impl.h:469
#18 doActivate(QObject*, int, void**) (sender=0x563b90ad18c0,
signal_index=3, argv=0x7ffd40a7cf00) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0-beta1/src/corelib/kernel/qobject.cpp:4044
#19 0x7f96a57c7a2a in QSocketNotifier::activated(QSocketDescriptor,
QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) (_t3=...,
_t2=, _t1=..., this=0x563b90ad18c0) at
/usr/src/debug/qt6-base/build/src/corelib/Core_autogen/include/moc_qsocketnotifier.cpp:193
#20 QSocketNotifier::event(QEvent*) (this=0x563b90ad18c0, e=0x7ffd40a7d010) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0-beta1/src/corelib/kernel/qsocketnotifier.cpp:327
#21 0x7f96a697bf4b in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x563

[kwin] [Bug 479094] kwin wayland randomly freezes completely when opening task switcher / alt tab

2024-01-03 Thread hexchain

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

--- Comment #7 from hexchain  ---
The same issue happened to me twice: the first while moving the mouse pointer
to the taskbar, and the other when I invoked the Tab Box.

System information:
Software: Plasma 5.91.0, Qt 6.7 beta 1
GPU: AMD Radeon 680M (Rembrandt)
EGL info:
OpenGL core profile vendor: AMD
OpenGL core profile renderer: AMD Radeon Graphics (radeonsi, rembrandt, LLVM
16.0.6, DRM 3.54, 6.6.9-arch1-1)
OpenGL core profile version: 4.6 (Core Profile) Mesa 23.3.2-arch1.2
OpenGL core profile shading language version: 4.60

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

[kwin] [Bug 479094] kwin wayland randomly freezes completely when opening task switcher / alt tab

2024-01-03 Thread hexchain

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

hexchain  changed:

   What|Removed |Added

 CC||k...@hexchain.org

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

[kwin] [Bug 479250] Screen randomly freezes for a short while when opening tabbox/overview

2024-01-01 Thread hexchain

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

hexchain  changed:

   What|Removed |Added

Summary|Screen randomly freezes for |Screen randomly freezes for
   |a short while when opening  |a short while when opening
   |tabbox  |tabbox/overview

--- Comment #3 from hexchain  ---
The same kind of freeze can also be observed when opening the overview.

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

[kwin] [Bug 479250] Screen randomly freezes for a short while when opening tabbox

2024-01-01 Thread hexchain

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

--- Comment #2 from hexchain  ---
This is on an AMD Remberant (integrated Radeon 680M) laptop.

OpenGL core profile vendor: AMD
OpenGL core profile renderer: AMD Radeon Graphics (radeonsi, rembrandt, LLVM
16.0.6, DRM 3.54, 6.6.8-arch1-1)
OpenGL core profile version: 4.6 (Core Profile) Mesa 23.3.2-arch1.1
OpenGL core profile shading language version: 4.60

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

[kwin] [Bug 479250] New: Screen randomly freezes for a short while when opening tabbox

2024-01-01 Thread hexchain

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

Bug ID: 479250
   Summary: Screen randomly freezes for a short while when opening
tabbox
Classification: Plasma
   Product: kwin
   Version: 5.91.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@hexchain.org
  Target Milestone: ---

SUMMARY
On Wayland with the latest beta, KWin randomly freezes when opening the tabbox.

STEPS TO REPRODUCE
1. Move the mouse cursor continuously (e.g. in a circle)
2. At the same time, press Alt+Tab (hold down the Alt key for a short moment
before releasing to ensure the tab box displays)

OBSERVED RESULT
The screen freezes for a moment before the Tab Box shows up.

EXPECTED RESULT
The screen should not freeze at all.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.91.0
KDE Frameworks Version: 5.247.0
Qt Version: 6.7.0
Kernel Version: 6.6.8-arch1-1 (64-bit)
Graphics Platform: Wayland

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

[frameworks-qqc2-desktop-style] [Bug 464069] Graphical Corruption Around Certain Widgets with fractional scale factor

2023-12-20 Thread hexchain

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

--- Comment #17 from hexchain  ---
(In reply to Nate Graham from comment #15)
> Doesn't DPR change automatically with the scale factor, though?

Yes, but IIUC this issue is about the graphical glitches that occur without
runtime DPR changes, right?

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

[frameworks-qqc2-desktop-style] [Bug 464069] Graphical Corruption Around Certain Widgets with fractional scale factor

2023-12-18 Thread hexchain

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

--- Comment #14 from hexchain  ---
I don't think so. This issue occurs without changing DPR.

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

[drkonqi] [Bug 478306] New: Core excavator is not compatible with my pam_namespace setup

2023-12-09 Thread hexchain

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

Bug ID: 478306
   Summary: Core excavator is not compatible with my pam_namespace
setup
Classification: Applications
   Product: drkonqi
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: k...@hexchain.org
  Target Milestone: ---

SUMMARY
I have a pam_namespace configuration in place to make /tmp private for each
user[1]. After a crash, drkonqi tries to excavate the core file with a
privileged helper process, but the core ends up in the root mount namespace,
and being inaccessible by the user process:

# ls -l /proc/self/ns/mnt
lrwxrwxrwx 1 root root 0 Dec  9 23:09 /proc/self/ns/mnt -> 'mnt:[4026531841]'
# ls -l /tmp/drkonqi-coredump-excavator.qemVAY
total 916492
-rw-r--r-- 1 hexchain root 938487808 Dec  9 22:56 core

% ls -l /proc/self/ns/mnt
lrwxrwxrwx 1 hexchain hexchain 0 Dec  9 23:10 /proc/self/ns/mnt ->
mnt:[4026533106]
% ls -l /tmp/drkonqi*
total 88
-rw-r--r-- 1 hexchain hexchain 87467 Dec  9 13:14 sentry_payload.json

Is it possible to make drkonqi compatible with such kind of setup?

STEPS TO REPRODUCE
1. Set up pam_namespace; see [1].
2. Let kwin_wayland crash

OBSERVED RESULT
drkonqi-polkit-helper[131080]: Core dump excavation complete 0
QProcess::NormalExit "/tmp/drkonqi-coredump-excavator.qemVAY/core"
drkonqi[130864]: true QDBusError("", "")
"/tmp/drkonqi-coredump-excavator.qemVAY/core"
drkonqi[130864]: Failed to move excavated core to target location
QFileInfo(/tmp/drkonqi-coredump-excavator.qemVAY/core)
"/tmp/drkonqi-core.gXtwZR/core"

EXPECTED RESULT
drkonqi should be able to successfully fetch the core.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.1
Kernel Version: 6.6.5-arch1-1 (64-bit)
Graphics Platform: Wayland

drkonqi at c90d3a58

ADDITIONAL INFORMATION

[1] The configuration looks like this:

/etc/security/namespace.init:
```
#!/bin/sh
# It receives polydir path as $1, the instance path as $2,
# a flag whether the instance dir was newly created (0 - no, 1 - yes) in $3,
# and user name in $4.

if [ "$1" = "/tmp" ]; then
user="$4"
mkdir -p /tmp/{.X11,.XIM,.ICE,.font}-unix
chown $user:$user /tmp/{.X11,.XIM,.ICE,.font}-unix
chmod +t /tmp/{.X11,.XIM,.ICE,.font}-unix
fi

exit 0
```

/etc/security/namespace.conf:
```
/tmp/tmp/user-private/  user:create root
```

/etc/pam.d/system-login:
```
# append this line:
sessionoptional   pam_namespace.so
```

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

[kwin] [Bug 477916] New: Black screen after switching VT

2023-12-02 Thread hexchain

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

Bug ID: 477916
Summary: Black screen after switching VT
Classification: Plasma
Product: kwin
Version: 5.90.0
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kwin-bugs-n...@kde.org
Reporter: k...@hexchain.org
Target Milestone: ---

SUMMARY
KWin sometimes shows a black screen (or fades into black from the desktop),
with only a mouse cursor, after switching back from another VT/user session.
The mouse cursor seems to be still reactive to what's under it, but the screen
is black. It seems that triggering DPMS to turn off and on the screen
(kscreen-doctor -d off) can rescue KWin from this situation.

It usually happens when invoking the "Switch User" action from KRunner, logging
in to another user, and then switching back. Using the Switch User button from
Kickoff may also trigger this issue, but seems to be less frequent.

According to reports in the KWin matrix room, it doesn't seem to be limited to
Wayland:
https://matrix.to/#/!xdwRmYgjAuZSEhsheE:kde.org/$WilUfLA1WHQJ5rbCuIaq0c8kHO8edGUSxqrIf6Eymf4?via=libera.chat=matrix.org=kde.org

STEPS TO REPRODUCE
1. Switch to another user session
2. Switch back

OBSERVED RESULT
The screen is black or starts to fade into black.

EXPECTED RESULT
The screen should not be black.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.1
Graphics Platform: Wayland

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

[kwin] [Bug 420859] Cursor theme/size changes do not take effect for Qt5 and XWayland software until session is restarted

2023-12-02 Thread hexchain

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

hexchain  changed:

   What|Removed |Added

 CC||k...@hexchain.org

--- Comment #27 from hexchain  ---
Also seems to happen in KWin 6 for me.

Operating System: Arch Linux 
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.1
Graphics Platform: Wayland

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

[kwin] [Bug 477430] New: Cannot turn off Night Light after enabling HDR while it is active

2023-11-23 Thread hexchain

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

Bug ID: 477430
   Summary: Cannot turn off Night Light after enabling HDR while
it is active
Classification: Plasma
   Product: kwin
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@hexchain.org
  Target Milestone: ---

SUMMARY
If HDR is turned on while Night Light is active, there doesn't seem to be a way
to deactivate it. Also, sometimes it looks like the color filter has been
applied twice (more red-ish).

STEPS TO REPRODUCE
1. Activate Night Light
2. Turn on HDR

OBSERVED RESULT
The screen looks a bit redish, but turning off Night Light has no effect.

EXPECTED RESULT
Night Light should continue to function as usual.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.81.80
KDE Frameworks Version: 5.245.0
Qt Version: 6.6.0
Kernel Version: 6.6.2-arch1-1 (64-bit)
Graphics Platform: Wayland

KWin git master at 477102f6bcce675d549081ce6dae0bcceb6a7241

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

[kwin] [Bug 465671] KWin Wayland hangs for a second while launching browser with Junction

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

--- Comment #5 from hexchain  ---
This is no longer happening for me with KWin git master
(835d6f4bc68a7e88b486daeec6712570a3a237a4).

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

[plasmashell] [Bug 474740] Panel popups sometimes appear at the center of the screen after (un)plugging external display until plasmashell is restarted

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

--- Comment #8 from hexchain  ---
I can't reproduce the original panel positioning issue anymore, and plasmashell
crashes a lot less when connecting/disconnecting an external monitor.

When it does crash, the stack trace also looks very different:
https://fars.ee/OO0f

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

[kwin] [Bug 476870] Enter key not released after toggling WCG in a terminal

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

hexchain  changed:

   What|Removed |Added

   Keywords||qt6

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

[kwin] [Bug 476868] Enabling WCG or applying ICC "increases" window transparency

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

hexchain  changed:

   What|Removed |Added

   Keywords||qt6

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

[kwin] [Bug 476870] New: Enter key not released after toggling WCG in a terminal

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

Bug ID: 476870
   Summary: Enter key not released after toggling WCG in a
terminal
Classification: Plasma
   Product: kwin
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@hexchain.org
  Target Milestone: ---

SUMMARY
When toggling WCG in a terminal with kscreen-doctor, after pressing Enter to
execute the command, the screen flashes (as expected), but the terminal does
not seem to receive a release event for the Enter key.

STEPS TO REPRODUCE
1. Open a terminal (Konsole Wayland or WezTerm XWayland) and type
"kscreen-doctor output..wcg.enable" (or "disable" depending on its
current state)
2. Press enter

OBSERVED RESULT
The screen flashes, and after returning to normal the terminal prints the
command prompt continuously as if the Enter key is held down.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.81.0
KDE Frameworks Version: 5.245.0
Qt Version: 6.6.0
Kernel Version: 6.6.0-arch1-1 (64-bit)
Graphics Platform: Wayland

kwin is at 835d6f4bc68a7e88b486daeec6712570a3a237a4.

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

[kwin] [Bug 476868] Enabling WCG or applying ICC "increases" window transparency

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

--- Comment #1 from hexchain  ---
Created attachment 163067
  --> https://bugs.kde.org/attachment.cgi?id=163067=edit
Konsole on about:blank, with ICC

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

[kwin] [Bug 476868] New: Enabling WCG or applying ICC "increases" window transparency

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

Bug ID: 476868
   Summary: Enabling WCG or applying ICC "increases" window
transparency
Classification: Plasma
   Product: kwin
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@hexchain.org
  Target Milestone: ---

Created attachment 163066
  --> https://bugs.kde.org/attachment.cgi?id=163066=edit
Konsole on about:blank, without ICC

SUMMARY
I've noticed that after enabling WCG or applying an ICC, semi-transparent
windows like Konsole appeared more transparent than they previously were.

Please see the screenshots.


STEPS TO REPRODUCE
1. Enable WCG or apply an ICC

OBSERVED RESULT
Semi-transparent windows, like Konsole, appear clearer.

EXPECTED RESULT
The transparency level should look the same.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.81.0
KDE Frameworks Version: 5.245.0
Qt Version: 6.6.0
Kernel Version: 6.6.0-arch1-1 (64-bit)
Graphics Platform: Wayland

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

[konsole] [Bug 474621] Characters shift position within words; restored on selection and style change boundaries

2023-11-08 Thread hexchain

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

--- Comment #4 from hexchain  ---
This issue no longer reproduces for me.

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

[plasmashell] [Bug 475834] Glitched text/artifacts when using 150% scale factor

2023-10-20 Thread hexchain

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

--- Comment #5 from hexchain  ---
Is it a duplicate? I don't see this issue in Plasma 5 though.

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

[plasmashell] [Bug 475834] Glitched text/artifacts when using 150% scale factor

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

--- Comment #3 from hexchain  ---
Created attachment 162428
  --> https://bugs.kde.org/attachment.cgi?id=162428=edit
System Settings - Touchscreen

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

[plasmashell] [Bug 475834] Glitched text/artifacts when using 150% scale factor

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

--- Comment #2 from hexchain  ---
Created attachment 162427
  --> https://bugs.kde.org/attachment.cgi?id=162427=edit
System Settings - Display

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

[plasmashell] [Bug 475834] Glitched text/artifacts when using 150% scale factor

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

--- Comment #1 from hexchain  ---
Created attachment 162426
  --> https://bugs.kde.org/attachment.cgi?id=162426=edit
KRunner

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

[plasmashell] [Bug 475834] New: Glitched text/artifacts when using 150% scale factor

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

Bug ID: 475834
   Summary: Glitched text/artifacts when using 150% scale factor
Classification: Plasma
   Product: plasmashell
   Version: master
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: k...@hexchain.org
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Created attachment 162425
  --> https://bugs.kde.org/attachment.cgi?id=162425=edit
Network applet

SUMMARY
When using a 150% scale factor, some texts and controls seem to render
incorrectly: some characters look stretched or compressed, and straight borders
of control may look distorted. It happens a lot less frequently with 175% and
does not seem to occur at all with 200%.

This is not only seen in Plasma Shell, it also occurs in e.g. KRunner,
Spectacle, and System Settings. My guess is that it only happens with QtQuick
interfaces, not QtWidget ones, such as KWrite. It also doesn't happen in Plasma
5.

STEPS TO REPRODUCE
Change the scale factor to 150% and navigate around.

OBSERVED RESULT
Some texts look strange. Sometimes the hovering state of an item can also
affect the text inside.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.80
KDE Frameworks Version: 5.240.0
Qt Version: 6.6.0
Kernel Version: 6.5.7-arch1-1 (64-bit)
Graphics Platform: Wayland

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

[plasmashell] [Bug 474740] Panel popups sometimes appear at the center of the screen after (un)plugging external display until plasmashell is restarted

2023-10-15 Thread hexchain

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

hexchain  changed:

   What|Removed |Added

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

--- Comment #6 from hexchain  ---
Now I "can't" reproduce, because plasmashell crashes every time when I
plug/unplug the external monitor...

Backtrace: https://fars.ee/-O4y

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

[plasmashell] [Bug 422969] Global menu: GTK3 apps has wrong menu item types

2023-10-05 Thread hexchain

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

hexchain  changed:

   What|Removed |Added

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

--- Comment #5 from hexchain  ---
I think it still happens in 5.27, please see the attached screenshots.

GTK global menu doesn't quite work under Wayland so Audacity is launched with
GDK_BACKEND=x11.

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

[plasmashell] [Bug 422969] Global menu: GTK3 apps has wrong menu item types

2023-10-05 Thread hexchain

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

--- Comment #4 from hexchain  ---
Created attachment 162100
  --> https://bugs.kde.org/attachment.cgi?id=162100=edit
Audacity global menu

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

[plasmashell] [Bug 422969] Global menu: GTK3 apps has wrong menu item types

2023-10-05 Thread hexchain

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

--- Comment #3 from hexchain  ---
Created attachment 162099
  --> https://bugs.kde.org/attachment.cgi?id=162099=edit
Audacity in-app menu (checkbox items)

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

[plasmashell] [Bug 474740] Panel popups appear at the center of the screen after (un)plugging external display until plasmashell is restarted

2023-09-21 Thread hexchain

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

hexchain  changed:

   What|Removed |Added

Summary|Kickoff appears at the  |Panel popups appear at the
   |center of the screen after  |center of the screen after
   |(un)plugging external   |(un)plugging external
   |display until plasmashell   |display until plasmashell
   |is restarted|is restarted

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

[plasmashell] [Bug 474740] Kickoff appears at the center of the screen after (un)plugging external display until plasmashell is restarted

2023-09-21 Thread hexchain

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

hexchain  changed:

   What|Removed |Added

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

--- Comment #3 from hexchain  ---
I can reproduce this on another similar configuration:

Internal: 2880x1800, 1.75x, primary, disabled when the external screen is
present
External: 1920x1080, 1x, primary

And yes, when this happens it seems all panel popups appear in the center of
the screen. I've tested Sticky Note and everything inside Status and
Notifications.

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

[plasmashell] [Bug 474740] New: Kickoff appears at the center of the screen after (un)plugging external display

2023-09-20 Thread hexchain

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

Bug ID: 474740
   Summary: Kickoff appears at the center of the screen after
(un)plugging external display
Classification: Plasma
   Product: plasmashell
   Version: master
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: plasma-b...@kde.org
  Reporter: k...@hexchain.org
CC: mikel5...@gmail.com, noaha...@gmail.com
  Target Milestone: 1.0

SUMMARY
Laptop connects to a monitor through DP, with the following configuration:

Internal: 2880x1800, 1.75x, primary, disabled when the external screen is
present
External: 3840x2160, 1.5x, primary

There is a panel on the bottom edge of the screen and a Kickoff applet on the
panel at the leftmost position. Normally, the menu would open at the bottom
left corner. However, after plugging or unplugging the cable, the menu will
appear at the center of the screen. Restarting plasmashell restores its
position.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.80
KDE Frameworks Version: 5.240.0
Qt Version: 6.6.0 (beta 4)
Kernel Version: 6.5.3-arch1-1 (64-bit)
Graphics Platform: Wayland

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

[plasmashell] [Bug 474642] New: Tray items cannot be activated

2023-09-17 Thread hexchain

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

Bug ID: 474642
   Summary: Tray items cannot be activated
Classification: Plasma
   Product: plasmashell
   Version: master
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: k...@hexchain.org
CC: mate...@gmail.com
  Target Milestone: 1.0

SUMMARY
With the current master branch, both left and right-clicking on SNI tray items,
and right-clicking on Plasmoid items do not work anymore.

The following logs appear after clicking (left or right) any SNI item:

plasmashell[615435]:
file:///home/hexchain/kde/usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/items/StatusNotifierItem.qml:64:
Error: Unable to determine callable overload.  Candidates are:

And after right-clicking a Plasmoid item:

plasmashell[615435]:
file:///home/hexchain/kde/usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/items/PlasmoidItem.qml:67:
Error: Unable to determine callable overload.  Candidates are:


Operating System: Arch Linux 
KDE Plasma Version: 5.27.80
KDE Frameworks Version: 5.240.0
Qt Version: 6.6.0
Graphics Platform: Wayland

plasma-workspace: b1d532d163a8bfef9c75b5094f772bcf194d6282
plasma-framework: 0a92d9c63d9b3fb8b521d32c22a04c08467c9668

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

[konsole] [Bug 474621] New: Selection makes characters shift position

2023-09-17 Thread hexchain

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

Bug ID: 474621
   Summary: Selection makes characters shift position
Classification: Applications
   Product: konsole
   Version: master
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: k...@hexchain.org
  Target Milestone: ---

Created attachment 161673
  --> https://bugs.kde.org/attachment.cgi?id=161673=edit
Screen recording of the issue

SUMMARY
With the current master branch, Characters move when making a selection.

Please see the attached screen recording.

STEPS TO REPRODUCE
Select some texts in Konsole.

Versions:
Operating System: Arch Linux 
KDE Plasma Version: 5.27.80
KDE Frameworks Version: 5.240.0
Qt Version: 6.6.0
Kernel Version: 6.5.3-arch1-1 (64-bit)
Graphics Platform: Wayland

Display info: 3840x2160, scale 160% (Also happens with other scale factors,
such as 150% and 200%)

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

[kwin] [Bug 468295] 5.27.4 Night color remains on at sunrise, can't disable

2023-07-25 Thread hexchain

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

--- Comment #10 from hexchain  ---
The output when night color should be active but it isn't:
~ % qdbus org.kde.KWin /ColorCorrect GetAll org.kde.kwin.ColorCorrect
available: true
currentTemperature: 6500
enabled: true
inhibited: false
mode: 2
previousTransitionDateTime: 1690236000
previousTransitionDuration: 6
running: true
scheduledTransitionDateTime: 1690298220
scheduledTransitionDuration: 6
targetTemperature: 6500
~ % date +%s
1690298743

After changing one of the color temperature sliders once without saving:
% qdbus org.kde.KWin /ColorCorrect GetAll org.kde.kwin.ColorCorrect
available: true
currentTemperature: 4500
enabled: true
inhibited: false
mode: 2
previousTransitionDateTime: 1690298220
previousTransitionDuration: 6
running: true
scheduledTransitionDateTime: 1690322400
scheduledTransitionDuration: 6
targetTemperature: 4500


The following reproducer worked for me:

1. Set switching times to custom times, and begin time to a few minutes later;
2. Set transition duration to 1 minute;
3. Apply. Night color should be inactive at this point;
4. Lock screen and press Esc to enter DPMS;
5. Wait till begin time + a few minutes later;
6. Wake up the screen and notice that night color isn't active as it should be.

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

[kwin] [Bug 468295] 5.27.4 Night color remains on at sunrise, can't disable

2023-06-18 Thread hexchain

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

hexchain  changed:

   What|Removed |Added

 CC||k...@hexchain.org

--- Comment #6 from hexchain  ---
Same issue. I think if the screen is off (DPMS) when it reaches the Night Color
switching time, the switching wouldn't happen.

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

[kwin] [Bug 470746] New: Discrete mouse wheel movements do not always generate axis event when scrolling speed is low

2023-06-07 Thread hexchain

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

Bug ID: 470746
   Summary: Discrete mouse wheel movements do not always generate
axis event when scrolling speed is low
Classification: Plasma
   Product: kwin
   Version: 5.27.5
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: input
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@hexchain.org
  Target Milestone: ---

SUMMARY
When scrolling speed is reduced to a value less than the default, mouse wheel
movements will generate inconsistent wl_pointer axis events for Wayland
clients.

This seems to affect scrolling in WezTerm, Qt5/6/GTK3 list views, Firefox
(Wayland), and Chromium tab strip. 

STEPS TO REPRODUCE
1. Reset the "scrolling speed" of the current mouse to its default (5th tick on
the slider)
2. Start wev from a terminal, move the wheel while hovering the window, and
observe the output.
3. Reduce the scrolling speed
4. Repeat step 2

OBSERVED RESULT
When the scrolling speed is at its default value, wl_pointer axis events with
the following values can be observed:
15, 15, 15, 15, ...

When it is lower than the default, one of the following repeat sequences can be
seen (x = empty frame):
- x, 22, 11, ...
- x, 15, ...
- x, x, x, 18, x, x, 13, x, x, 13, ...
- x (repeat 9 times), 15, ...

EXPECTED RESULT
I'm not sure what the expected (correct) outcome should be, but I guess every
wheel movement should generate an axis event with the same value.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Kernel Version: 6.3.5-arch1-1 (64-bit)
Graphics Platform: Wayland

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

[Spectacle] [Bug 469184] 23.04 version lost "blur factor" feature

2023-05-31 Thread hexchain

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

hexchain  changed:

   What|Removed |Added

 CC||k...@hexchain.org

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

[plasmashell] [Bug 470155] New: Task manager keeps screencast running even if the tooltip is hidden

2023-05-23 Thread hexchain

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

Bug ID: 470155
   Summary: Task manager keeps screencast running even if the
tooltip is hidden
Classification: Plasma
   Product: plasmashell
   Version: 5.27.5
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Task Manager and Icons-Only Task Manager
  Assignee: plasma-b...@kde.org
  Reporter: k...@hexchain.org
  Target Milestone: 1.0

SUMMARY
After bringing a window forward by clicking on a task manager item and leaving
the mouse pointer there, plasmashell does not show a window thumbnail tooltip,
but the underlying screencast session keeps running.

STEPS TO REPRODUCE
1. Open some windows. Ideally, also open qpwgraph to visualize PipeWire
connections
2. Move the mouse pointer to the task manager, click on an item to open another
window, and leave the pointer there

OBSERVED RESULT
The thumbnail window may briefly appear, but in qpwgraph, the screencast
connection exists until the mouse pointer moves away.

EXPECTED RESULT
The screencast connection may need to be closed as soon as the window thumbnail
disappears.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Kernel Version: 6.3.3-arch1-1 (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION
In my system, this running screencast connection triggers a lot of logs in the
journal like these:

kwin_wayland[1312]: kwin_screencast: Dropping a screencast frame because the
compositor is slow

Makes me think that it affects system performance to some extent, but neither
kwin_wayland nor pipewire uses any noticeable CPU or GPU time (but why does it
think the compositor is too slow?).

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

[plasmashell] [Bug 465933] Dark System Tray popup and Notifications have weird corners

2023-04-11 Thread hexchain

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

--- Comment #4 from hexchain  ---
I think it happens more frequently if the panel opacity is set to "Translucent"
instead of "Adaptive".

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

[krunner] [Bug 467957] New: "Switch user" action creates a popup below the KRunner window

2023-03-30 Thread hexchain

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

Bug ID: 467957
   Summary: "Switch user" action creates a popup below the KRunner
window
Classification: Plasma
   Product: krunner
   Version: 5.27.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: k...@hexchain.org
CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de
  Target Milestone: ---

Created attachment 157715
  --> https://bugs.kde.org/attachment.cgi?id=157715=edit
KRunner window on top of the popup dialog

SUMMARY
When invoking the "Switch User" action from KRunner, a popup is created below
the KRunner window, making it unable to be interacted with.


STEPS TO REPRODUCE
Execute "Switch User" in KRunner.

OBSERVED RESULT
The KRunner window stays on top of the popup dialog.

EXPECTED RESULT
The KRunner window should either disappear or stay behind.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.2.8-arch1-1 (64-bit)
Graphics Platform: Wayland

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

[plasmashell] [Bug 466320] kpipewire_logging: Window not available PipeWireSourceItem_QML_1025

2023-03-25 Thread hexchain

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

hexchain  changed:

   What|Removed |Added

 CC||k...@hexchain.org
Version|5.27.1  |5.27.3

--- Comment #2 from hexchain  ---
I think it happens when hovering on and moving across task manager items, even
if the window thumbnail isn't displayed.

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

[kwin] [Bug 459373] Maximized XWayland apps leave pixel gaps when using a fractional scaling factor

2023-03-05 Thread hexchain

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

--- Comment #28 from hexchain  ---
I have a panel on the left screen edge. When an XWayland window is already
maximized, changing the panel width or changing the scale factor a little bit
(e.g. 175 to 170 or 180 and vice versa) makes gaps disappear. But they come
back after re-maximizing the window.

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

[plasmashell] [Bug 465933] Dark System Tray popup and Notifications have weird corners

2023-02-21 Thread hexchain

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

--- Comment #3 from hexchain  ---
Yes, it also happens with other widget popups, such as system monitor sensors.
But I have 3 such widgets and only one of them has these corners.

Changing the color scheme or Plasma theme makes these corners disappear for the
current session.

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

[plasmashell] [Bug 465933] Systray popup and notifications have weird corner

2023-02-17 Thread hexchain

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

--- Comment #1 from hexchain  ---
Created attachment 156373
  --> https://bugs.kde.org/attachment.cgi?id=156373=edit
Panel systray popup

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

[plasmashell] [Bug 465933] New: Systray popup and notifications have weird corner

2023-02-17 Thread hexchain

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

Bug ID: 465933
   Summary: Systray popup and notifications have weird corner
Classification: Plasma
   Product: plasmashell
   Version: 5.27.0
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: k...@hexchain.org
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Created attachment 156372
  --> https://bugs.kde.org/attachment.cgi?id=156372=edit
Notification popup

SUMMARY
The systray popup and notifications have a rectangular background on rounded
corners.

STEPS TO REPRODUCE
Expand the popup, or send a notification.

OBSERVED RESULT
The corner has a rectangular background.

EXPECTED RESULT
The corner should be rounded.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.0
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.12-arch1-1 (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION
The screen is 3840x2160 with 200% scale.

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

[kwin] [Bug 465671] KWin Wayland hangs for a second while launching browser with Junction

2023-02-16 Thread hexchain

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

--- Comment #3 from hexchain  ---
Is it possible to make the sycoca build process async? For example, if the
timestamp mismatches when querying, then query against the stale database until
it is rebuilt.

Or, is it possible (or desirable) to make KService a standalone DBus service?
Currently, every application using KApplicationTrader::query has to scan all
desktop files sometimes. That sounds like a lot of duplicated effort.

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

[kwin] [Bug 465671] New: KWin Wayland hangs for a second while launching browser with Junction

2023-02-13 Thread hexchain

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

Bug ID: 465671
   Summary: KWin Wayland hangs for a second while launching
browser with Junction
Classification: Plasma
   Product: kwin
   Version: 5.26.90
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@hexchain.org
  Target Milestone: ---

Created attachment 156194
  --> https://bugs.kde.org/attachment.cgi?id=156194=edit
reproducer.js

SUMMARY
When using Junction (non-flatpak) to start the browser, the whole desktop
freezes for less than a second before the browser shows up. This does not
happen when it's running inside Flatpak.

I've nailed down the problem and attached a simple reproducer script.

STEPS TO REPRODUCE
1. Execute the script with GJS: gjs test.js

OBSERVED RESULT
Upon executing the script, the whole screen freezes for about a second.
This can be verified with some animated/moving things, e.g. glxgears or simply
moving the mouse.

In the journal, kwin_wayland prints some warnings from kf.services:

kwin_wayland[1398775]: kf.service.services: The desktop entry file
"/usr/share/applications/qemu.desktop" has Type= "Application" but no Exec line
kwin_wayland[1398775]: kf.service.sycoca: Invalid Service : 
"/usr/share/applications/qemu.desktop"
kwin_wayland[1398775]: kf.service.sycoca: The menu spec file ( "" ) contains a
Layout or DefaultLayout tag without the mandatory Merge tag inside. Please fix
it.

EXPECTED RESULT
The screen should not freeze.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.26.90
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.10-arch1-1 (64-bit)
Graphics Platform: Wayland

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

[kwin] [Bug 465186] New: The new tiling editor sometimes does not open

2023-02-02 Thread hexchain

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

Bug ID: 465186
   Summary: The new tiling editor sometimes does not open
Classification: Plasma
   Product: kwin
   Version: 5.26.90
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Custom Tiling
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@hexchain.org
CC: notm...@gmail.com
  Target Milestone: ---

SUMMARY
Occasionally the tiling editor stops working. When Meta+T is pressed, kwin
prints the following log:

Failed to load QUrl("file:///usr/share/kwin/effects/tileseditor/qml/main.qml"):
(file:///usr/share/kwin/effects/tileseditor/qml/main.qml:15:1: module
"org.kde.KWin.Effect.WindowView" is not installed
import org.kde.KWin.Effect.WindowView 1.0
^)

When this happens, I usually find it useful to go into System Settings ->
Workspace Behavior -> Desktop Effects and disable/enable Tiling Editor. But it
may not always work, and I would then try to toggle other "Window Management"
effects.

Not sure how to reproduce, it just happens randomly.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.26.90
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Kernel Version: 6.1.8-arch1-1 (64-bit)
Graphics Platform: Wayland

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

[xdg-desktop-portal-kde] [Bug 460918] Screenshot only contains bottom-left quarter in 200% scaled Wayland session

2023-02-02 Thread hexchain

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

--- Comment #7 from hexchain  ---
I see where the problem is. In your screenshot, the area is set to "Current
Screen", which makes the portal call
org.kde.kwin.Screenshot.screenshotScreen(fd, bool). Inside this method in KWin,
the screenshot flag is initialized with ScreenShotNativeResolution, and the
result buffer is scaled according to dpr.

If the area is "Full Screen", the portal will call screenshotFullscreen(fd,
bool), which does not have the native resolution flag, so the result buffer
will be the same as the logical size.

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

[xdg-desktop-portal-kde] [Bug 460918] Screenshot only contains bottom-left quarter in 200% scaled Wayland session

2023-02-01 Thread hexchain

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

--- Comment #6 from hexchain  ---
Created attachment 155868
  --> https://bugs.kde.org/attachment.cgi?id=155868=edit
The buggy screenshot

This is what I have with xdg-desktop-portal-kde 5.26.90.

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

[kwin] [Bug 464591] Fcitx IME candidate list has wrong position/size in some Qt6 apps on HiDPI Wayland

2023-02-01 Thread hexchain

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

--- Comment #6 from hexchain  ---
The issue with Qt 6.5 (oversized candidate window) seems to be fcitx5-qt having
problems when fractional scaling is present. I've opened a bug report for it:
https://github.com/fcitx/fcitx5-qt/issues/38

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

[kwin] [Bug 464591] Fcitx IME candidate list has wrong position/size in some Qt6 apps on HiDPI Wayland

2023-01-31 Thread hexchain

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

--- Comment #5 from hexchain  ---
(In reply to hexchain from comment #4)
> Qt6 in kde-unstable has been updated to 6.5.0beta2 today (and I just
> realized it was beta1, not beta3 - sorry for the confusion!) and Fcitx's
> candidate list is back to normal (no longer 2x stretched).
> 
> The other issue with Telegram still exists.

For some reason, the issue with Qt 6.5.0beta* is happening again. I was not
sure why it become normal that day.

As a side note, I've done some tests with both KWin 5.26 and 5.27 in nested
mode, and it didn't happen in 5.26 (in qdbusviewer6, the candidate window size
is correct).

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

[xdg-desktop-portal-kde] [Bug 460918] Screenshot only contains bottom-left quarter in 200% scaled Wayland session

2023-01-31 Thread hexchain

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

--- Comment #4 from hexchain  ---
In Plasma 5.26.90, taking a screenshot through xdg-portal-test-kde (either
inside or outside flatpak) on a 3840x2160 200% screen gives me a picture of the
whole screen but scaled down to 1080p. Is this the correct/intended behavior?

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

[kwin] [Bug 459778] Screen occasionally freezes "EGL_BAD_SURFACE" errors when launching application while using the Klassy window decoration

2023-01-30 Thread hexchain

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

--- Comment #50 from hexchain  ---
Can confirm it still happens in KWin 5.26.0. Same EGL_BAD_SURFACE error, but
this time C-A-F1~6 also stops working for about a minute, with the following
warning in the journal appearing twice:

kwin_wayland_drm: No drm events for gpu "/dev/dri/card0" within last 30 seconds

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

[kwin] [Bug 453147] amdgpu: GPU reset crash loop

2023-01-29 Thread hexchain

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

hexchain  changed:

   What|Removed |Added

 CC||k...@hexchain.org

--- Comment #6 from hexchain  ---
I also have a GPU hang/reset similar to 459872 (possibly a kernel or hardware
issue, https://gitlab.freedesktop.org/drm/amd/-/issues/2068). KWin cannot
recover from the reset and keeps printing the following warning, followed by
some graphics information:

> kwin_scene_opengl: A graphics reset not attributable to the current GL 
> context occurred.

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

[kwin] [Bug 464591] Fcitx IME candidate list has wrong position/size in some Qt6 apps on HiDPI Wayland

2023-01-29 Thread hexchain

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

hexchain  changed:

   What|Removed |Added

 Attachment #155469|0   |1
is obsolete||

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

[kwin] [Bug 464591] Fcitx IME candidate list has wrong position/size in some Qt6 apps on HiDPI Wayland

2023-01-29 Thread hexchain

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

--- Comment #4 from hexchain  ---
Qt6 in kde-unstable has been updated to 6.5.0beta2 today (and I just realized
it was beta1, not beta3 - sorry for the confusion!) and Fcitx's candidate list
is back to normal (no longer 2x stretched).

The other issue with Telegram still exists.

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

[kwin] [Bug 459373] Maximized XWayland apps leave some pixels on the right border with fractional scale factor

2023-01-26 Thread hexchain

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

hexchain  changed:

   What|Removed |Added

 CC||k...@hexchain.org

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

[frameworks-kguiaddons] [Bug 463199] "After taking screenshot: Copy to clipboard" does not work anymore on Wayland

2023-01-25 Thread hexchain

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

--- Comment #15 from hexchain  ---
Tried to do some debugging on this issue with some added output to KGuiAddons:
https://gist.github.com/hexchain/06e71deb8b29f661fee646fe0096a499

Spectacle prints the following output after a screenshot is taken (and nothing
is copied to the clipboard):
kb enter
using normal mechanism fw: QWindow(0x0) , fw->isVisible: false , keyboard has
focus: true
kb leave

If I remove the whole "if" block of the "normal mechanism", Spectacle is then
able to copy the image to the clipboard. With WAYLAND_DEBUG the output also
matches what you expected in #c11.

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

[kwin] [Bug 464591] Fcitx IME candidate list has wrong position/size in some Qt6 apps on HiDPI Wayland

2023-01-25 Thread hexchain

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

--- Comment #3 from hexchain  ---
Sorry, should be 6.4.2.

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

[plasmashell] [Bug 464674] Wallpaper size changes after toggling external display

2023-01-23 Thread hexchain

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

hexchain  changed:

   What|Removed |Added

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

--- Comment #2 from hexchain  ---
Short answer: yes, it doesn't seem to happen on X11.

Long story: I've created a new user to try to reproduce this bug. I believe
these are the steps to make it happen (some might not be necessary, though):

1. Log into a Wayland session and set both screens to 200% scale
2. Disable the internal screen, only enable the external one
3. Disconnect the external display
4. Change the wallpaper on the internal screen
5. Log out and log in
6. Open some applications and lock the screen
7. Toggle the external display
8. Unlock, and minimize all windows

It could be highly dependent on the monitor's behavior when powered on. If it
is hard to reproduce on your side, I can try to add some logs to kwin and/or
plasmashell.

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

[plasmashell] [Bug 464674] New: Wallpaper size changes after toggling external display

2023-01-22 Thread hexchain

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

Bug ID: 464674
   Summary: Wallpaper size changes after toggling external display
Classification: Plasma
   Product: plasmashell
   Version: 5.26.90
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: k...@hexchain.org
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Created attachment 155522
  --> https://bugs.kde.org/attachment.cgi?id=155522=edit
Desktop state after toggling the monitor

SUMMARY
On my laptop, after turning the monitor off and on, the desktop wallpaper on
the external display appears as if it is shown on the internal screen: scaled
and cropped to a smaller display size, only covering the top left part of the
screen, and the remaining space is filled with black color. Changing the
wallpaper also only changes the image area. I've attached a screenshot to
demonstrate the situation.

This only happens when there are other foreground windows, or when the session
is locked. It doesn't happen if it is a bare desktop before turning off the
screen.

Restarting plasma-plasmashell.service brings it back to normal.

Setup: Wayland, laptop (internal screen on eDP-1, 2880x1800, 200%, usually
turned off when a monitor is present) connected to a monitor (DP-2, 3840x2160,
200%) through a USB-C cable

The monitor does not disconnect when turned off but shortly disconnects (for ~2
seconds) when turned on. I've tried to simulate this by quickly
unplugging/re-plugging the cable, but failed.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.26.90
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Kernel Version: 6.1.7-arch1-1 (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION
I don't think this has ever happened in 5.26.

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

[xdg-desktop-portal-kde] [Bug 464549] Portal crash when Telegram flatpak posts a notification

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

--- Comment #2 from hexchain  ---
With this patch applied it does not crash anymore. But the notification still
does not show up, maybe that's another issue.

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

[Breeze] [Bug 464632] New: No transparency and lingering hover effect on window menus when transparency is enabled

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

Bug ID: 464632
   Summary: No transparency and lingering hover effect on window
menus when transparency is enabled
Classification: Plasma
   Product: Breeze
   Version: 5.26.90
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: QStyle
  Assignee: plasma-b...@kde.org
  Reporter: k...@hexchain.org
CC: noaha...@gmail.com, uhh...@gmail.com
  Target Milestone: ---

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

SUMMARY
When transparency is enabled in Application Style, the window menu is not
transparent as it should be, and the hover effect stays around on menu items.

STEPS TO REPRODUCE
1. Turn on Breeze transparency
2. Navigate a window menu

OBSERVED RESULT
Please see the attached screen recording.

EXPECTED RESULT
The window menu should be transparent, and the hovering effect should disappear
after the mouse leaves menu items.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.26.90
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Kernel Version: 6.1.7-arch1-1 (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION
This is not a regression, it was around in 5.26 (maybe earlier).

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

[kwin] [Bug 464591] Fcitx IME candidate list has wrong position/size in some Qt6 apps on HiDPI Wayland

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

--- Comment #1 from hexchain  ---
Created attachment 155469
  --> https://bugs.kde.org/attachment.cgi?id=155469=edit
IME window size in qdbusviewer6

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

[kwin] [Bug 464591] New: Fcitx IME candidate list has wrong position/size in some Qt6 apps on HiDPI Wayland