!OntAZuxrATLyTkCyID:matrix.org

Manjaro KDE

290 Members
Support for Manjaro KDE desktop53 Servers

Load older messages


SenderMessageTime
16 Oct 2021
@zdl:matrix.org@zdl:matrix.org left the room.06:14:40
@bloodaxenor:matrix.orgBloodaxe
In reply to @strit:matrix.org
Install libpamac-flatpak-plugin and then enable it in Pamac settings -> Third Party.
Yup, that did the trick! Tnx πŸ˜„
09:17:35
@prof.p:matrix.sp-codes.deπ™Ώπš›πš˜πš. 𝙿

Hello, anybody got KeePassXC Auto-Type Sequence working under current Manjaro Plasma in a Wayland session?

According to their website I've enabled the command line option -platform xcb and also tried setting the environment variable QT_QPA_PLATFORM=xcb but with no avail.

However, I cann see the message in the CLI

qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x5637b6a7e560) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x5637b74071c0) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents

but I don't understand this or what I could do to overcome this. So my question is if anybody got KeePassXC Auto-Type Sequence working under current Manjaro Plasma in a Wayland session and by which tricks/means...

Plasma version: 5.22.5
KDE Framework version: 5.86.0
Qt-Version: 5.15.2
Kernel: 5.14.10-1 MANJARO (64 bit)
KeePassXC version: 2.6.6

09:51:20
@prof.p:matrix.sp-codes.deπ™Ώπš›πš˜πš. 𝙿 *

Hello, anybody got KeePassXC Auto-Type Sequence working under current Manjaro Plasma in a Wayland session?

According to their website I've enabled the command line option -platform xcb and also tried setting the environment variable QT_QPA_PLATFORM=xcb but with no avail.

However, I cann see the message in the CLI

qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x5637b6a7e560) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x5637b74071c0) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents

but I don't understand this or what I could do to overcome this. So my question is if anybody got KeePassXC Auto-Type Sequence working under current Manjaro Plasma in a Wayland session and by which tricks/means...

Plasma version: 5.22.5
KDE Framework version: 5.86.0
Qt-Version: 5.15.2
Kernel: 5.14.10-1 MANJARO (64 bit)
KeePassXC version: 2.6.6

09:51:47
@strit:matrix.orgStritSounds like KeypassX does not support Wayland.10:05:07
@prof.p:matrix.sp-codes.deπ™Ώπš›πš˜πš. 𝙿Quote from the URL I've provided: "[...Wayland...] To use Auto-Type in this environment, you must set QT_QPA_PLATFORM=xcb or start KeePassXC with the -platform xcb command-line flag."10:08:05
@prof.p:matrix.sp-codes.deπ™Ώπš›πš˜πš. 𝙿So I understand it ought to work!?10:08:13
@strit:matrix.orgStritWell, in that case, you canj inform them that it does not work on Plasma wayland. πŸ˜› 10:15:07
@prof.p:matrix.sp-codes.deπ™Ώπš›πš˜πš. 𝙿 "
There is no workaround. If you are trying to Auto-Type to a window controlled by the wayland compositor then Auto-Type will not be possible. We are working on a proof of concept wayland Auto-Type method though.
"
10:34:04
@prof.p:matrix.sp-codes.deπ™Ώπš›πš˜πš. 𝙿https://github.com/keepassxreboot/keepassxc/issues/6452#issuecomment-82748538610:34:11
@strit:matrix.orgStritSo their documentation is wrong. Good to know. πŸ˜‰ 10:38:07
@prof.p:matrix.sp-codes.deπ™Ώπš›πš˜πš. 𝙿What a pitty. Which password manager with autotype are you using?10:40:19
@prof.p:matrix.sp-codes.deπ™Ώπš›πš˜πš. 𝙿* What a pitty. Which password manager with autotype are you using?10:40:27
@strit:matrix.orgStritI'm using Bitwarden.10:43:54
@strit:matrix.orgStrit(browser extension only though)10:44:09
@prof.p:matrix.sp-codes.deπ™Ώπš›πš˜πš. 𝙿

" Wayland has taken the stance of "Wayland is not a compositor" and has ceded that responsibility to the various desktop environments. This creates the situation where each desktop env has its own set of extended protocols and internal interface api (and maybe even permissions) to poll for information that was openly available via X11 server in the past. This includes window titles and switching between windows. Wayland has taken the stance that every client is isolated and should have no knowledge of any other client. This means keepassxc cannot "find out" about other windows unless the compositor exposes that information in some other fashion.

So this isn't really a "why can't you do this in wayland" discussion because that is not where you do this anyway. Wayland is just a protocol for drawing windows and sending/receiving inputs to the compositor."

10:49:05
@prof.p:matrix.sp-codes.deπ™Ώπš›πš˜πš. 𝙿https://github.com/keepassxreboot/keepassxc/issues/2281#issuecomment-92233293210:49:15
@strit:matrix.orgStritYep. That's one of the main differences. The window managers need to manage compositing with wayland too now.10:50:47
@prof.p:matrix.sp-codes.deπ™Ώπš›πš˜πš. 𝙿This should be a high prio item. Wayland is default on many distros nowadays...10:51:51
@strit:matrix.orgStritWell, not really "many". But the number is climbing.11:15:50
17 Oct 2021
@m210119754703:matrix.orgm210119754703 joined the room.12:05:55
@04m6o782ef35p70_peko:matrix.org@04m6o782ef35p70_peko:matrix.org left the room.13:14:23
18 Oct 2021
@comrade_equinox:matrix.orgZoxide joined the room.16:37:07
20 Oct 2021
@muttsan:matrix.orgmuttsan joined the room.05:17:19
@dedalus_diggle:matrix.org@dedalus_diggle:matrix.org left the room.08:11:56
@freshgum-bubbles:halogen.cityfreshgum changed their display name from freshgum bubbles to freshgum.19:04:16
@freshgum-bubbles:halogen.cityfreshgum changed their profile picture.19:16:45
21 Oct 2021
@iudexcc:matrix.orgiudex changed their display name from iudexrt to iudex.20:48:11
@iudexcc:matrix.orgiudex changed their profile picture.20:48:37
22 Oct 2021
@thermionic:matrix.org@thermionic:matrix.org left the room.18:24:38

There are no newer messages yet.


Back to Room List