[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1076729: marked as done (libwayland: breaks plasma desktop start after last upgrade to version 1.23.0-1)

Your message dated Mon, 05 Aug 2024 17:43:55 +0200
with message-id <2E2C9A5C-CF88-46F9-A2D2-58ABCFBE8F60@coucouf.fr>
and subject line Re: Bug#1076729: libwayland: breaks plasma desktop start after last upgrade to version 1.23.0-1
has caused the Debian Bug report #1076729,
regarding libwayland: breaks plasma desktop start after last upgrade to version 1.23.0-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1076729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076729
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: libwayland-bin
Version: 1.22.0-2.1+b1
Severity: normal
X-Debbugs-Cc: antdev66@gmail.com

Dear Maintainer,
after updating the packages:
- libwayland-bin
- libwayland-client0
- libwayland-cursor0
- libwayland-dev
- libwayland-egl1
- libwayland-server0
from version 1.22.0-2.1+b1 -> 1.23.0-1, reboot and entering the credentials on
sddm for login, plasmashell no longer starts and the system remains frozen with
only the mouse cursor visible, it is not possible to interrupt cleanly but you
need to reboot.
Downgrading these packages to previous version, everything works again, so I
put these packages in hold, waiting to resolve.
Thanks,
Antonio


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (700, 'unstable'), (520, 'stable-security'), (500, 'stable-updates'), (500, 'stable'), (100, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.9.10-1-liquorix-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libwayland-bin depends on:
ii  libc6      2.39-4
ii  libexpat1  2.6.2-1
ii  libxml2    2.12.7+dfsg-3+b1

libwayland-bin recommends no packages.

libwayland-bin suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
control: reassign -1 kwin-wayland
control: notfound -1 wayland/1.23.0-1
control: found -1 kwin-wayland/4:5.27.11-1

Hi Vincent,


Le 5 août 2024 12:42:42 GMT+02:00, Vincent Lefevre <vincent@vinc17.net> a écrit :
>This bug was closed, but has not been marked as fixed in
>libwayland-client0, so that the current version is still
>regarded as buggy, as reported by apt-listbugs:

[…]

>If this is regarded as a bug in libwayland-client0, this bug should
>still remain open until it is fixed *in wayland*. Otherwise it should
>be reassigned to kwin-wayland.

Let's say the bug it primarily and kwin and reassign/close it accordingly so we don't block the migration of wayland to testing.

We unbroke things by rebuilding kwin which was more of a workaround.

The real fix should be this merge request [1] in extra-cmake-modules to ensure that kwin doesn't re-export symbols generated by wayland-scanner for use in Wayland clients. It's planed for inclusion in KDE Frameworks 6.5 which should ship anytime soon.


[1] uhttps://invent.kde.org/frameworks/extra-cmake-modules/-/merge_requests/447


Happy hacking,
--
Aurélien

--- End Message ---
Reply to: