Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1050929: telegram-desktop: System window decorations disabled on Wayland after 4.9.3
55 views
Skip to first unread message
z411
Aug 31, 2023, 9:40:05 AM8/31/23
to
Package: telegram-desktop
Version: 4.9.3+ds-1
Severity: normal
Dear Maintainer,
I use KDE Plasma under Wayland and I've always used the window system
decorations option in order to make my desktop visually consistent.
But after updating to 4.9.3, this option has suddenly disappeared. I
asked upstream and they said the option was still there but it was most
probably disabled by the package maintainer, so I come here to humbly ask
to re-enable it if possible.
* What led up to the situation?
Updating from 4.8.1 to 4.9.3 under Plasma+Wayland
* What was the outcome of this action?
The "Use system window decorations" option is now disabled
* What outcome did you expect instead?
Being able to use the option, it's been there before the update
Thank you for your time.
-- Package-specific info:
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.4.0-3-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages telegram-desktop depends on:
ii libabsl20220623 20220623.1-3
ii libavcodec60 7:6.0-6
ii libavfilter9 7:6.0-6
ii libavformat60 7:6.0-6
ii libavutil58 7:6.0-6
ii libc6 2.37-7
ii libgcc-s1 13.2.0-2
ii libglib2.0-0 2.77.2-1
ii libglibmm-2.68-1 2.77.0-1
ii libhunspell-1.7-0 1.7.2+really1.7.2-10
ii libjpeg62-turbo 1:2.1.5-2
ii libkf5coreaddons5 5.107.0-1
ii liblz4-1 1.9.4-1
ii libminizip1 1:1.2.13.dfsg-3
ii libopenal1 1:1.23.1-3
ii libopus0 1.4-1
ii libqrcodegencpp1 1.8.0-1.1
ii libqt5core5a [qtbase-abi-5-15-10] 5.15.10+dfsg-3
ii libqt5gui5 5.15.10+dfsg-3
ii libqt5network5 5.15.10+dfsg-3
ii libqt5svg5 5.15.10-2
ii libqt5widgets5 5.15.10+dfsg-3
ii librlottie0-1 0.1+dfsg-4
ii libsigc++-3.0-0 3.4.0-7
ii libsrtp2-1 2.5.0-3
ii libssl3 3.0.10-1
ii libstdc++6 13.2.0-2
ii libswresample4 7:6.0-6
ii libswscale7 7:6.0-6
ii libvpx7 1.12.0-1
ii libx11-6 2:1.8.6-1
ii libxcb-keysyms1 0.4.0-1+b2
ii libxcb-record0 1.15-1
ii libxcb-screensaver0 1.15-1
ii libxcb1 1.15-1
ii libxcomposite1 1:0.4.5-1
ii libxdamage1 1:1.1.6-1
ii libxext6 2:1.3.4-1+b1
ii libxfixes3 1:6.0.0-2
ii libxrandr2 2:1.5.2-2+b1
ii libxtst6 2:1.2.3-1.1
ii libxxhash0 0.8.1-1
ii libyuv0 0.0~git20230616.a366ad7-1
ii qt5-image-formats-plugins 5.15.10-2
ii zlib1g 1:1.2.13.dfsg-3
Versions of packages telegram-desktop recommends:
pn fonts-open-sans <none>
pn libwebkit2gtk-4.0-37 | libwebkit2gtk-4.1-0 <none>
telegram-desktop suggests no packages.
Versions of packages telegram-desktop is related to:
ii xdg-desktop-portal 1.16.0-3
ii xdg-desktop-portal-kde [xdg-desktop-portal-backend] 5.27.7-1
-- no debconf information
Version: 4.9.3+ds-1
Severity: normal
Dear Maintainer,
I use KDE Plasma under Wayland and I've always used the window system
decorations option in order to make my desktop visually consistent.
But after updating to 4.9.3, this option has suddenly disappeared. I
asked upstream and they said the option was still there but it was most
probably disabled by the package maintainer, so I come here to humbly ask
to re-enable it if possible.
* What led up to the situation?
Updating from 4.8.1 to 4.9.3 under Plasma+Wayland
* What was the outcome of this action?
The "Use system window decorations" option is now disabled
* What outcome did you expect instead?
Being able to use the option, it's been there before the update
Thank you for your time.
-- Package-specific info:
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.4.0-3-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages telegram-desktop depends on:
ii libabsl20220623 20220623.1-3
ii libavcodec60 7:6.0-6
ii libavfilter9 7:6.0-6
ii libavformat60 7:6.0-6
ii libavutil58 7:6.0-6
ii libc6 2.37-7
ii libgcc-s1 13.2.0-2
ii libglib2.0-0 2.77.2-1
ii libglibmm-2.68-1 2.77.0-1
ii libhunspell-1.7-0 1.7.2+really1.7.2-10
ii libjpeg62-turbo 1:2.1.5-2
ii libkf5coreaddons5 5.107.0-1
ii liblz4-1 1.9.4-1
ii libminizip1 1:1.2.13.dfsg-3
ii libopenal1 1:1.23.1-3
ii libopus0 1.4-1
ii libqrcodegencpp1 1.8.0-1.1
ii libqt5core5a [qtbase-abi-5-15-10] 5.15.10+dfsg-3
ii libqt5gui5 5.15.10+dfsg-3
ii libqt5network5 5.15.10+dfsg-3
ii libqt5svg5 5.15.10-2
ii libqt5widgets5 5.15.10+dfsg-3
ii librlottie0-1 0.1+dfsg-4
ii libsigc++-3.0-0 3.4.0-7
ii libsrtp2-1 2.5.0-3
ii libssl3 3.0.10-1
ii libstdc++6 13.2.0-2
ii libswresample4 7:6.0-6
ii libswscale7 7:6.0-6
ii libvpx7 1.12.0-1
ii libx11-6 2:1.8.6-1
ii libxcb-keysyms1 0.4.0-1+b2
ii libxcb-record0 1.15-1
ii libxcb-screensaver0 1.15-1
ii libxcb1 1.15-1
ii libxcomposite1 1:0.4.5-1
ii libxdamage1 1:1.1.6-1
ii libxext6 2:1.3.4-1+b1
ii libxfixes3 1:6.0.0-2
ii libxrandr2 2:1.5.2-2+b1
ii libxtst6 2:1.2.3-1.1
ii libxxhash0 0.8.1-1
ii libyuv0 0.0~git20230616.a366ad7-1
ii qt5-image-formats-plugins 5.15.10-2
ii zlib1g 1:1.2.13.dfsg-3
Versions of packages telegram-desktop recommends:
pn fonts-open-sans <none>
pn libwebkit2gtk-4.0-37 | libwebkit2gtk-4.1-0 <none>
telegram-desktop suggests no packages.
Versions of packages telegram-desktop is related to:
ii xdg-desktop-portal 1.16.0-3
ii xdg-desktop-portal-kde [xdg-desktop-portal-backend] 5.27.7-1
-- no debconf information
Nicholas Guriev
Sep 2, 2023, 9:50:04 AM9/2/23
to
Hello,
On Thu, 31 Aug 2023 09:18:21 -0400 z411 <z4...@omaera.org> wrote:
> I use KDE Plasma under Wayland and I've always used the window system
> decorations option in order to make my desktop visually consistent.
>
> But after updating to 4.9.3, this option has suddenly disappeared. I
> asked upstream and they said the option was still there but it was most
> probably disabled by the package maintainer, so I come here to humbly ask
> to re-enable it if possible.
Set the QT_QPA_PLATFORM environment variable to "xcb" value before running
Telegram Desktop. And the setting will reappear because of XWayland.
In genuine Wayland there is no such thing as system decorations.
$ QT_QPA_PLATFORM=xcb telegram-desktop
For some reason, that's not default anymore.
On Thu, 31 Aug 2023 09:18:21 -0400 z411 <z4...@omaera.org> wrote:
> I use KDE Plasma under Wayland and I've always used the window system
> decorations option in order to make my desktop visually consistent.
>
> But after updating to 4.9.3, this option has suddenly disappeared. I
> asked upstream and they said the option was still there but it was most
> probably disabled by the package maintainer, so I come here to humbly ask
> to re-enable it if possible.
Telegram Desktop. And the setting will reappear because of XWayland.
In genuine Wayland there is no such thing as system decorations.
$ QT_QPA_PLATFORM=xcb telegram-desktop
For some reason, that's not default anymore.
z411
Sep 4, 2023, 8:50:04 PM9/4/23
to
Thanks for the reply. I'm not sure if I understand.
On Sat, 02 Sep 2023 16:39:47 +0300 Nicholas Guriev <n.gu...@bsl.dev>
wrote:> Set the QT_QPA_PLATFORM environment variable to "xcb" value
it had the option for system decorations. The icon also worked, for some
reason it doesn't work now.
The latest official release (4.9.3) also works on Wayland with system
decorations, and the 4.8.1 Debian package works as well. Even with
QT_QPA_PLATFORM=wayland. It even shows some warnings related to Wayland
and xeyes shows me it's not running under XWayland. Please correct me if
I'm wrong.
> In genuine Wayland there is no such thing as system decorations.
As far as I understand, there is, there's the xdg-decoration-v1 protocol
supported by KWin and Sway which they use to draw system decorations on
Wayland windows.
Again, please correct me if I'm wrong.
Cheers.
On Sat, 02 Sep 2023 16:39:47 +0300 Nicholas Guriev <n.gu...@bsl.dev>
wrote:> Set the QT_QPA_PLATFORM environment variable to "xcb" value
before running
> Telegram Desktop. And the setting will reappear because of XWayland.
Telegram already used Wayland before this (as do all Qt5/Qt6 apps) and
> Telegram Desktop. And the setting will reappear because of XWayland.
it had the option for system decorations. The icon also worked, for some
reason it doesn't work now.
The latest official release (4.9.3) also works on Wayland with system
decorations, and the 4.8.1 Debian package works as well. Even with
QT_QPA_PLATFORM=wayland. It even shows some warnings related to Wayland
and xeyes shows me it's not running under XWayland. Please correct me if
I'm wrong.
> In genuine Wayland there is no such thing as system decorations.
supported by KWin and Sway which they use to draw system decorations on
Wayland windows.
Again, please correct me if I'm wrong.
Cheers.
Nicholas Guriev
Sep 12, 2023, 7:40:04 AM9/12/23
to
Hello!
On Mon, 4 Sep 2023 21:35:22 -0300 z411 <z4...@omaera.org> wrote:
> Telegram already used Wayland before this (as do all Qt5/Qt6 apps) and
> it had the option for system decorations. The icon also worked, for some
> reason it doesn't work now.
Since version 4.8.3 Telegram Desktop needs Qt6 for complete Wayland
integration. Although, our package is build against Qt5 yet. Some plugins that
tdesktop relies on were not built against the latest Qt, and migration was
postponed.
> The latest official release (4.9.3) also works on Wayland with system
> decorations, and the 4.8.1 Debian package works as well. Even with
> QT_QPA_PLATFORM=wayland. It even shows some warnings related to Wayland
> and xeyes shows me it's not running under XWayland. Please correct me if
> I'm wrong.
>
> > In genuine Wayland there is no such thing as system decorations.
>
> As far as I understand, there is, there's the xdg-decoration-v1 protocol
> supported by KWin and Sway which they use to draw system decorations on
> Wayland windows.
You are right but this protocol is an optional part of Wayland. KWin in KDE
Plasma implements the protocol, Mutter in GNOME does not.
For now, I will block the native Wayland integration and the coming update will
prefer Xwayland because of unresolved glitches. The default window frame looks
not as intended, it has no context menu, and it can double while switching the
checkbox "Use system window frame" in the Settings.
Of course, you always can force native Wayland but at your own risk. I will
also add a patch restoring the checkbox in all modes.
On Mon, 4 Sep 2023 21:35:22 -0300 z411 <z4...@omaera.org> wrote:
> Telegram already used Wayland before this (as do all Qt5/Qt6 apps) and
> it had the option for system decorations. The icon also worked, for some
> reason it doesn't work now.
integration. Although, our package is build against Qt5 yet. Some plugins that
tdesktop relies on were not built against the latest Qt, and migration was
postponed.
> The latest official release (4.9.3) also works on Wayland with system
> decorations, and the 4.8.1 Debian package works as well. Even with
> QT_QPA_PLATFORM=wayland. It even shows some warnings related to Wayland
> and xeyes shows me it's not running under XWayland. Please correct me if
> I'm wrong.
>
> > In genuine Wayland there is no such thing as system decorations.
>
> As far as I understand, there is, there's the xdg-decoration-v1 protocol
> supported by KWin and Sway which they use to draw system decorations on
> Wayland windows.
Plasma implements the protocol, Mutter in GNOME does not.
For now, I will block the native Wayland integration and the coming update will
prefer Xwayland because of unresolved glitches. The default window frame looks
not as intended, it has no context menu, and it can double while switching the
checkbox "Use system window frame" in the Settings.
Of course, you always can force native Wayland but at your own risk. I will
also add a patch restoring the checkbox in all modes.
z411
Sep 13, 2023, 8:00:04 PM9/13/23
to
Hi, thanks again for your reply.
On Tue, 12 Sep 2023 14:25:21 +0300 Nicholas Guriev <nich...@guriev.su>
wrote:
upstream maintainers and he was suspicious of the Qt5 dependency.
> You are right but this protocol is an optional part of Wayland. KWin in KDE
> Plasma implements the protocol, Mutter in GNOME does not.
Yes, I am aware. I've been using Kwin/KDE for a full year on Wayland
with almost no issues (its implementation of the protocol is great) so I
was surprised this became an issue suddenly - but now that you mention
Qt6, it all makes sense.
> Of course, you always can force native Wayland but at your own risk. I will
> also add a patch restoring the checkbox in all modes.
That would be great. I didn't experience any issues with Wayland so far
even in its current state so it'd be great if you could restore the
checkbox for now until the transition to Qt6 is complete.
As this is not really a bug but a side effect of an ongoing transition
please feel free to close this report. Thank you for the explanation.
On Tue, 12 Sep 2023 14:25:21 +0300 Nicholas Guriev <nich...@guriev.su>
wrote:
> Since version 4.8.3 Telegram Desktop needs Qt6 for complete Wayland
> integration. Although, our package is build against Qt5 yet. Some plugins that
> tdesktop relies on were not built against the latest Qt, and migration was
> postponed.
I see, so it has to do with Qt6 after all. I spoke with one of the
> integration. Although, our package is build against Qt5 yet. Some plugins that
> tdesktop relies on were not built against the latest Qt, and migration was
> postponed.
upstream maintainers and he was suspicious of the Qt5 dependency.
> You are right but this protocol is an optional part of Wayland. KWin in KDE
> Plasma implements the protocol, Mutter in GNOME does not.
with almost no issues (its implementation of the protocol is great) so I
was surprised this became an issue suddenly - but now that you mention
Qt6, it all makes sense.
> Of course, you always can force native Wayland but at your own risk. I will
> also add a patch restoring the checkbox in all modes.
even in its current state so it'd be great if you could restore the
checkbox for now until the transition to Qt6 is complete.
As this is not really a bug but a side effect of an ongoing transition
please feel free to close this report. Thank you for the explanation.
0 new messages