Bug#962285: Reproducible on KDE, not on LXQT
I can still reproduce this bug with ScreenGrab 2.5.0 on KDE, but not on LXQT.
Bug#960451: fixed in meteo-qt 2.1-1
Hello Yao Wei, Version in testing is fine, however version in stable is totally broken. Do you think it may be uploaded to stable? Regards, Pols12 Le 07/01/2021 à 15:57, Debian Bug Tracking System a écrit : This is an automatic notification regarding your Bug report which was filed against the meteo-qt package: #960451: meteo-qt: Cannot connect to server anymore: version≥1.5 is needed It has been closed by Debian FTP Masters (reply to Yao Wei (魏銘廷) ). Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Debian FTP Masters (reply to Yao Wei (魏銘廷) ) by replying to this email.
Bug#960451: meteo-qt: Cannot connect to server anymore: version≥1.5 is needed
Package: meteo-qt Version: 1.5-1 Severity: important Dear Maintainer, Because of changes in OpenWeatherMap API, meteo-qt is unusable. This has been fixed upstream in v1.5 release. See https://github.com/dglent/meteo-qt/issues/94 Is it possible to backport v1.5 or higher in Debian stable? Else, meteo-qt is totally useless. Thanks, Pols12 -- System Information: Debian Release: 10.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_CRAP Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages meteo-qt depends on: ii python33.7.3-1 ii python3-lxml 4.3.2-1 ii python3-pyqt5 5.11.3+dfsg-1+b3 ii python3-sip4.19.14+dfsg-2 Versions of packages meteo-qt recommends: ii meteo-qt-l10n 1.0.0-1 meteo-qt suggests no packages. -- no debconf information
Bug#833719: Bug #833719 Firefox NS_ERROR_NET_INADEQUATE_SECURITY
Same issue with firefox-esr 52.7.3esr-1 and libnss3 2:3.33-1 since I’ve updated Firefox (from 52.1 I believe) Updating libnss3 to 2:3.36.1-1 seems to solve this issue.
