Hello, Am Fri, Dec 11, 2020 at 10:48:42PM +0100 schrieb Matteo F. Vescovi: > Hi again! > > On 2020-12-09 at 22:06 (+03), Nicholas Guriev wrote: > > I daresay the bug you reported relates to screensaver integration that > > revealed today[1]. But if a workaround with QT_QPA_PLATFORM=wayland does > > not work for you, it could be something else. Can you please describe > > the crash more comprehensive and attach logs and terminal output of > > telegram-desktop to identify the issue? > > > > [1]: https://bugs.debian.org/976894 > > Actually, installing the qtwayland5 package (as stated in #976894) and > setting the reported variable did the trick. > > I've just set severity and merging accordingly.
from a user point of view the behavior the package isn't working, or in other words, the package isn't usable that makes this issue grave by definition of severities. In my eyes it's not useful to keep this broken package in testing because using an uncomfortable work around make the binary "work". Doing so makes the usage of severities quite obsolete. For me it doesn't look like the binary is segfaulting, at least there is no message about that. This happen even if I update to the most recent version of telegram-desktop from unstable (2.2.0+ds-4+b1) which pulls in some newer rdeps due the QT updates some days ago. > carsten@i5:~ $ telegram-desktop > Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use > QT_QPA_PLATFORM=wayland to run on Wayland anyway. > error: : cannot open > error: : cannot open > error: : cannot open > qt.svg: Error while inflating gzip file: SVG format check failed > qt.svg: Error while inflating gzip file: SVG format check failed > The X11 connection broke (error 2). Did the X11 server die? > carsten@i5:~ $ A doable compromise could be to extend the Exec entries in the desktop file. It should not harm non Gnome + Wayland users. https://github.com/telegramdesktop/tdesktop/issues/8506#issuecomment-683176286 So I hereby suggest to set the severity back to grave and add a tag help if needed, that would be a clear statement that the package has a problem. The world isn't going down if the package is kicked out of testing. If a newer upstream version is fixing the whole problem than the package should get an update in Debian too. Regards Carsten
