Bug#986265: Fixed Upstream
It looks like this bug was fixed in Plasma 6. I had some time to try Plasma 6 and was unable to reproduce this bug. I plan to close this report when it arrives in unstable/sid.
Bug#1028543: lutris: Application not shown in GNOME's application launcher without /usr/games in $PATH.
Package: lutris Version: 0.5.12-1 Followup-For: Bug #1028543 X-Debbugs-Cc: jlsan...@protonmail.com I also ran into this problem recently (being unable to start lutris). This gitlab issue seems somewhat relevant[1]. I think the actual bug is caused by gdm3. After finding your bug report, I was able to find out that /usr/games was also missing from my $PATH under certain circumstances. The circumstances were running a wayland kde plasma session that was launched through GDM on a Debian system where games are in /usr/games. I was also unable to start five-or-more or gnome-chess, as those are also located in /usr/games. However, I am able to start lutris under GNOME through GDM; my PATH appears to be set properly: `/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games`. Whereas SDDM handles the PATH environment variable properly, something about specifically launching the plasma wayland session (or sway) through GDM leads to PATH being set to: `/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin`. The issue persists on a fresh install of Debian 12 bookworm. I still do not know why this happens, but I assume it is related to GDM's handling of wayland sessions. Jaycee 1: https://gitlab.gnome.org/GNOME/gdm/-/issues/692 -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-5-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 lutris depends on: ii cabextract1.9-3 ii curl 7.88.1-1 ii fluid-soundfont-gs3.1-5.3 ii gir1.2-gtk-3.03.24.36-4 ii gir1.2-webkit2-4.12.38.5-1 ii mesa-utils8.5.0-1 ii p7zip 16.02+dfsg-8 ii psmisc23.6-1 ii python3 3.11.2-1 ii python3-dbus 1.3.2-4+b1 ii python3-distro1.8.0-1 ii python3-gi3.42.2-3+b1 ii python3-lxml 4.9.2-1+b1 ii python3-magic 2:0.4.26-3 ii python3-pil 9.4.0-1.1+b1 ii python3-requests 2.28.1+dfsg-1 ii python3-setproctitle 1.3.1-1+b2 ii python3-yaml 6.0-3+b2 ii unzip 6.0-28 ii x11-xserver-utils 7.7+9+b1 Versions of packages lutris recommends: ii gvfs-backends1.50.3-1 ii libwine-development 7.22~repack-2 ii python3-evdev1.6.1+dfsg-1+b1 ii winetricks 20220411-1 Versions of packages lutris suggests: pn gamemode ii gamescope 3.11.49-1 -- no debconf information
Bug#988696: connman does not respect /etc/network/interfaces when upgrading from buster to bullseye and more general considerations
On Thursday, September 23rd, 2021 at 1:05 PM, Michael Biebl wrote: > Am 23.09.21 um 21:35 schrieb Jaycee Santos: > > Is there a reason why to choose gnome-network-manager over something like > > nm-tray for LXDE? > > I think nm-tray (being based on Qt5) is a reasonable choice for LXQT (which > is also Qt5 based). LXDE on the other hand uses GTK, so I think > network-manager-gnome is a better fit there. (both disk footprint and memory > usage wise) Ah. My apologies. I thought nm-applet was provided by nm-tray. I was wrong. I did not know that nm-applet was part of network-manager-gnome! So I agree with network-manager-gnome being a better fit for LXDE. Apparently, I was already using it. Jaycee
Bug#988696: connman does not respect /etc/network/interfaces when upgrading from buster to bullseye and more general considerations
On Wed, Sep 22, 2021 at 10:21:10PM +0200, Ervin Dine wrote: > I have not had any problems with conman in my LXDE Debian 11 install > but if I may give my suggestion, gnome-network-manager works fine with > LXDE and it has more features. Why not bundle that instead of conman? > Conman does not even have an icon in the status bar where you can > toggle wifi on and off or choose another connection. Is there a reason why to choose gnome-network-manager over something like nm-tray for LXDE? Jaycee
Bug#991474: calamares-settings-debian: security.d.o apt sources entry should point to bullseye-security
Package: calamares-settings-debian Version: 11.0.4-1 Severity: serious X-Debbugs-Cc: jlsan...@protonmail.com sources-final has deb http://security.debian.org/debian-security/ $RELEASE-updates main deb-src http://security.debian.org/debian-security/ $RELEASE-updates main should be deb http://security.debian.org/debian-security/ $RELEASE-security main deb-src http://security.debian.org/debian-security/ $RELEASE-security main https://www.debian.org/releases/testing/amd64/release-notes/ch-upgrading.en.html#bullseye-security -- System Information: Debian Release: 11.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-7-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 calamares-settings-debian depends on: ii calamares3.2.36-1 ii cryptsetup 2:2.3.5-1 ii dconf-gsettings-backend [gsettings-backend] 0.38.0-2 ii keyutils 1.6.1-2 ii qml-module-qtquick-window2 5.15.2+dfsg-6 ii qml-module-qtquick2 5.15.2+dfsg-6 calamares-settings-debian recommends no packages. calamares-settings-debian suggests no packages. -- no debconf information
Bug#990446: installation-reports: Bullseye RC 2 Installer Success
Package: installation-reports Severity: normal X-Debbugs-Cc: jlsan...@protonmail.com Boot method: USB Image version: https://cdimage.debian.org/cdimage/bullseye_di_rc2/amd64/iso-cd/debian-bullseye-DI-rc2-amd64-netinst.iso Date: Machine: (Custom Built) AMD Ryzen 7 2700, NVIDIA GeForce GTX 1080, ASUS PRIME X-470 PRO, CORSAIR DRAM CMK16GX4M2B3000C15, SAMSUNG SSD 860 EVO MZ-76E250 Partitions: FilesystemType 1K-blocksUsed Available Use% Mounted on udev devtmpfs 8125444 0 8125444 0% /dev tmpfs tmpfs 16366641800 1634864 1% /run /dev/mapper/fyme--pc--vg-root ext4 237240120 4147636 220968532 2% / tmpfs tmpfs 8183320 103260 8080060 2% /dev/shm tmpfs tmpfs 5120 4 5116 1% /run/lock /dev/sda2 ext2481642 63960392697 15% /boot /dev/nvme0n1p1vfat 98304 34358 63946 35% /boot/efi tmpfs tmpfs 16366645216 1631448 1% /run/user/1000 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect media: [O] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Installation went smoothly! No regressions for me at least. I went with an encrypted LVM installation as that's what I usually use. The previous installation on this SSD was already encrypted. To avoid wearing out my SSD, I canceled/skipped the overwrite process before the encrypted partition was created. I forgot to tell the installer to _not_ use an EFI partition on a separate drive, so it overwrote it (see /dev/nvme0n1p1 partition above) without taking into account the OS (another Bullseye installation) that was on it. (I prefer to have an EFI partition on the same drive as the OS). As for tasksel options, I stuck with the default options (GNOME desktop) but also selected SSH server. Likewise with Bullseye Installer RC 1, I had no trouble starting GNOME or gdm. -- Package-specific info: == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="11 (bullseye) - installer build 20210606" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux fyme-pc 5.10.0-7-amd64 #1 SMP Debian 5.10.40-1 (2021-05-28) x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Root Complex [1022:1450] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8747] lspci -knn: 00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) I/O Memory Management Unit [1022:1451] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8747] lspci -knn: 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] lspci -knn: 00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] lspci -knn: DeviceName: Onboard IGD lspci -knn: 00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] lspci -knn: 00:03.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] lspci -knn: 00:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] lspci -knn: 00:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B [1022:1454] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] lspci -knn: 00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD]
Bug#988910: unblock: flent/2.0.0-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: jlsan...@protonmail.com
Please unblock package flent
[ Reason ]
Fixes bug #987656, by updating Recommends to include python3-qtpy.
[ Impact ]
Without this change, users who rely on flent-gui will not be able
to launch it (nothing happens, users may assume it has crashed).
[ Tests ]
Install flent and make sure it pulls in python3-qtpy.
Verify that starting flent-gui loads the GUI.
[ Risks ]
Trivial; only Recommends has been changed.
[ Checklist ]
[x] all changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in testing
[ Other info ]
(Anything else the release team should know.)
unblock flent/2.0.0-3
diff -Nru flent-2.0.0/debian/changelog flent-2.0.0/debian/changelog
--- flent-2.0.0/debian/changelog2021-02-11 09:59:11.0 -0800
+++ flent-2.0.0/debian/changelog2021-04-27 11:30:58.0 -0700
@@ -1,3 +1,10 @@
+flent (2.0.0-3) unstable; urgency=medium
+
+ * debian/control: change 'recommends' from python3-pyqt5 to python3-qtpy
+to reflect upstream dependency change. (Closes: #987656).
+
+ -- Toke Høiland-Jørgensen Tue, 27 Apr 2021 18:30:58 +
+
flent (2.0.0-2) unstable; urgency=medium
* debian/patches/fix-glob.patch: backport upstream fix for plot name globbing
diff -Nru flent-2.0.0/debian/control flent-2.0.0/debian/control
--- flent-2.0.0/debian/control 2021-02-11 09:59:11.0 -0800
+++ flent-2.0.0/debian/control 2021-04-27 11:30:58.0 -0700
@@ -19,7 +19,7 @@
Package: flent
Architecture: all
Depends: ${python3:Depends}, ${misc:Depends}, ${sphinxdoc:Depends}
-Recommends: python3-matplotlib, python3-pyqt5, fping | ping, irtt
+Recommends: python3-matplotlib, python3-qtpy, fping | ping, irtt
Suggests: netperf (>= 2.6.0)
Description: FLExible Network Tester for bufferbloat testing and more
The FLExible Network Tester: Python wrapper to run multiple simultaneou
Bug#988501: upgrade-reports: Buster (10.9) to Bullseye Success
Package: upgrade-reports Severity: normal X-Debbugs-Cc: jlsan...@protonmail.com My previous release is: Buster (10.9) I am upgrading to: Bullseye Archive date: Fri, 14 May 2021 08:14:35 + Upgrade date: Fri, 14 May 2021 01:11:51 -0700 uname -a before upgrade: uname -a after upgrade: Linux debm2 5.10.0-6-amd64 #1 SMP Debian 5.10.28-1 (2021-04-09) x86_64 GNU/Linux Method: Used 'apt upgrade --without-new-pkgs' then 'apt full-upgrade' following Bullseye release notes draft. Contents of /etc/apt/sources.list: deb http://deb.debian.org/debian bullseye main contrib non-free deb-src http://deb.debian.org/debian bullseye main contrib non-free deb http://deb.debian.org/debian bullseye-updates main contrib non-free deb-src http://deb.debian.org/debian bullseye-updates main contrib non-free deb http://security.debian.org/debian-security/ bullseye-security main contrib non-free deb-src http://security.debian.org/debian-security/ bullseye-security main contrib non-free # See https://wiki.debian.org/SourcesList for more information. #deb http://deb.debian.org/debian buster main contrib non-free #deb-src http://deb.debian.org/debian buster main contrib non-free #deb http://deb.debian.org/debian buster-updates main contrib non-free #deb-src http://deb.debian.org/debian buster-updates main contrib non-free #deb http://security.debian.org/debian-security/ buster/updates main contrib non-free #deb-src http://security.debian.org/debian-security/ buster/updates main contrib non-free - Were there any non-Debian packages installed before the upgrade? If so, what were they? No - Was the system pre-update a pure buster system? If not, which packages were not from buster? Yes - Did any packages fail to upgrade? No - Were there any problems with the system after upgrading? No Further Comments/Problems: None
Bug#988180: installation-reports: Bullseye RC 1 Installer Success
Package: installation-reports Severity: normal X-Debbugs-Cc: jlsan...@protonmail.com Boot method: USB Image version: https://cdimage.debian.org/cdimage/bullseye_di_rc1/amd64/iso- cd/debian-bullseye-DI-rc1-amd64-netinst.iso Date: Fri, 07 May 2021 04:54:20 + Machine: (Custom Built) AMD Ryzen 7 2700, NVIDIA GeForce GTX 1080, ASUS PRIME X-470 PRO, CORSAIR DRAM CMK16GX4M2B3000C15, SAMSUNG SSD 860 EVO MZ-76E250 Partitions: FilesystemType 1K-blocksUsed Available Use% Mounted on udev devtmpfs 8125460 0 8125460 0% /dev tmpfs tmpfs 16366681640 1635028 1% /run /dev/mapper/DESKTOP--DR34H3M--vg-root ext4 237240120 4612048 220504120 3% / tmpfs tmpfs 8183324 80692 8102632 1% /dev/shm tmpfs tmpfs 5120 4 5116 1% /run/lock /dev/sda2 ext2481642 63940392717 15% /boot /dev/sda1 vfat5232445364517880 2% /boot/efi tmpfs tmpfs 1636664 112 1636552 1% /run/user/1000 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect media: [O] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: I went with an encrypted LVM installation as that's what I usually use. I already have an existing Debian Buster install on a separate SSD so I configured the installer to not use the EFI partition on that drive. (I prefer to have it on the same drive as the OS). I stuck with the default tasksel options (GNOME desktop), and the installation went very smoothly. I do get the usual firmware missing warnings when booting (see below), but there was no trouble starting GNOME or gdm. I do experience some degraded performance, but it is usable for most tasks that don't require GPU acceleration. It isn't optimal, but I have a working environment to install the proprietary driver from here. jaycee@DESKTOP-DR34H3M:~$ sudo dmesg | grep firmware [1.324095] nouveau :09:00.0: firmware: failed to load nvidia/gp104/nvdec/scrubber.bin (-2) [1.324099] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware [1.324111] nouveau :09:00.0: firmware: failed to load nvidia/gp104/acr/bl.bin (-2) [1.324113] nouveau :09:00.0: acr: firmware unavailable [1.324115] nouveau :09:00.0: pmu: firmware unavailable [1.324164] nouveau :09:00.0: gr: firmware unavailable [1.324169] nouveau :09:00.0: sec2: firmware unavailable -- Package-specific info: == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="11 (bullseye) - installer build 20210415" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux DESKTOP-DR34H3M 5.10.0-6-amd64 #1 SMP Debian 5.10.28-1 (2021-04-09) x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Root Complex [1022:1450] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8747] lspci -knn: 00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) I/O Memory Management Unit [1022:1451] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8747] lspci -knn: 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] lspci -knn: 00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] lspci -knn: DeviceName: Onboard IGD lspci -knn: 00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] lspci -knn: 00:03.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc.
Bug#987656: flent-gui fails to start (ModuleNotFoundError: No module named 'qtpy')
Package: flent
Version: 2.0.0-2
Severity: important
X-Debbugs-Cc: jlsan...@protonmail.com
flent-gui fails to start. I expected a window to appear but nothing happens.
Running 'flent --gui --verbose --debug-error' outputs the following:
Started Flent 2.0.0 using Python 3.9.2.
ERROR: Unable to find a usable Qt version.
Traceback (most recent call last):
File "/usr/share/flent/flent/gui.py", line 68, in
import qtpy
ModuleNotFoundError: No module named 'qtpy'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/share/flent/flent/__init__.py", line 55, in run_flent
from flent.gui import run_gui
File "/usr/share/flent/flent/gui.py", line 93, in
raise RuntimeError("Unable to find a usable Qt version.")
RuntimeError: Unable to find a usable Qt version.
After doing a quick search for 'qtpy', I came across the python3-qtpy
package and installed it. flent-gui now starts as expected.
-- System Information:
Debian Release: 11.0
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-6-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 flent depends on:
ii libjs-sphinxdoc 3.4.3-2
ii python3 3.9.2-3
Versions of packages flent recommends:
ii iputils-ping [ping] 3:20210202-1
ii irtt 0.9.0-2+b14
ii python3-matplotlib 3.3.4-1
ii python3-pyqt55.15.2+dfsg-3
Versions of packages flent suggests:
ii netperf 2.7.0-0.1
-- no debconf information
Bug#971956: (No Subject)
Is it possible to also mention the bullet point on this page? https://wiki.debian.org/CUPSDriverlessPrinting#vendor "USB print queues previously set up with vendor drivers (HP, Brother, Canon, Samsung etc) will amost certainly cease to work, so they become candidates for deletion. In fact, a user could consider removing the vendor software completely as it doesn't provide any useful function unless it is intended to switch between IPP-over-USB and vendor drivers." Jaycee
Bug#986265: plasma-widgets-addons: Undo widget removal fails when timer finished notification is not dismissed
Package: plasma-widgets-addons Version: 4:5.21.3-1 Severity: normal X-Debbugs-Cc: jlsan...@protonmail.com When removing the Timer widget, a notification is shown with a button to undo the action. If that timer recently sent a notification, like "Timer finished," clicking the undo button fails to restore the widget. Steps to reproduce: 1. Add a Timer widget to the desktop 2. Set the timer to one second by using the scroll wheel on the seconds digit 3. Click on the timer to start the countdown 4. When the countdown is complete, remove the widget from the desktop 5. Click on the undo button on the notification Workaround for current users: If a user accidentally removes the timer widget shortly after it finishes counting down and wishes to restore it, dismiss the "Timer finished" notification (if any) _before_ clicking the undo button. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-5-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 plasma-widgets-addons depends on: ii kdeplasma-addons-data 4:5.21.3-1 ii kio 5.78.0-4 ii kpackagetool5 5.78.0-3 ii libc6 2.31-11 ii libkf5archive5 5.78.0-2 ii libkf5completion5 5.78.0-3 ii libkf5configcore5 5.78.0-4 ii libkf5configgui55.78.0-4 ii libkf5coreaddons5 5.78.0-4 ii libkf5i18n5 5.78.0-2 ii libkf5kiocore5 5.78.0-4 ii libkf5kiogui5 5.78.0-4 ii libkf5kiowidgets5 5.78.0-4 ii libkf5newstuffcore5 5.78.0-4 ii libkf5notifications55.78.0-2 ii libkf5plasma5 5.78.0-3 ii libkf5purpose-bin 5.78.0-2 ii libkf5service-bin 5.78.0-2 ii libkf5service5 5.78.0-2 ii libkf5unitconversion5 5.78.0-2 ii libkf5widgetsaddons55.78.0-2 ii libkf5windowsystem5 5.78.0-2 ii libkf5xmlgui5 5.78.0-2 ii libqt5core5a5.15.2+dfsg-5 ii libqt5dbus5 5.15.2+dfsg-5 ii libqt5gui5 5.15.2+dfsg-5 ii libqt5qml5 5.15.2+dfsg-5 ii libqt5quick55.15.2+dfsg-5 ii libqt5webengine55.15.2+dfsg-3 ii libqt5webenginecore55.15.2+dfsg-3 ii libqt5widgets5 5.15.2+dfsg-5 ii libstdc++6 10.2.1-6 ii plasma-dataengines-addons 4:5.21.3-1 ii plasma-framework5.78.0-3 ii plasma-workspace4:5.21.3-1 ii qml-module-org-kde-draganddrop 5.78.0-2 ii qml-module-org-kde-kcoreaddons 5.78.0-2 ii qml-module-org-kde-kio 5.78.0-2 ii qml-module-org-kde-purpose 5.78.0-2 ii qml-module-qtgraphicaleffects 5.15.2-2 ii qml-module-qtquick-controls 5.15.2-2 ii qml-module-qtquick-layouts 5.15.2+dfsg-5 ii qml-module-qtquick-window2 5.15.2+dfsg-5 ii qml-module-qtquick2 5.15.2+dfsg-5 ii qml-module-qtwebengine 5.15.2+dfsg-3 ii qml-module-qtwebkit 5.212.0~alpha4-11 Versions of packages plasma-widgets-addons recommends: ii ksysguard 4:5.20.5-2 Versions of packages plasma-widgets-addons suggests: pn quota -- no debconf information
Bug#981235: deja-dup: Does not check if encryption passphrase matches previous ones when making a fresh full backup
Package: deja-dup Version: 38.3-1 Severity: important Dear Maintainer, The current version of deja-dup in buster is affected by https://wiki.gnome.org/Apps/DejaDup/PassphraseProblems2019. When deja-dup decides to make a full backup after a while, it asks for an encryption passphrase. However, duplicity does not verify whether or not the passphrase is the same as the one used in previous backups. This can lead to a mismatching backup chain. Backups may be jeopardized if one happens to make a typo when deja-dup makes a fresh backup once in a while. The GNOME Wiki page states that deja-dup addressed the passphrase verification problem in its 39.1 release. Is it possible to have this fixed in buster? -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-13-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages deja-dup depends on: ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2 ii duplicity0.7.18.2-1 ii libatk1.0-0 2.30.0-2 ii libc62.28-10 ii libglib2.0-0 2.58.3-2+deb10u2 ii libgoa-1.0-0b3.30.1-2 ii libgoa-backend-1.0-1 3.30.1-2 ii libgtk-3-0 3.24.5-1 ii libnautilus-extension1a 3.30.5-2 ii libpackagekit-glib2-18 1.1.12-5 ii libpango-1.0-0 1.42.4-8~deb10u1 ii libpeas-1.0-01.22.0-4 ii libsecret-1-00.18.7-1 Versions of packages deja-dup recommends: ii gvfs-backends 1.38.1-5 ii packagekit 1.1.12-5 ii policykit-10.105-25 Versions of packages deja-dup suggests: pn python-boto pn python-cloudfiles pn python-swiftclient -- no debconf information
Bug#971569: (No Subject)
After updating the BIOS of the ThinkPad X220 from 8DET56WW (1.26) to 8DET76WW (1.46), this behavior no longer occurs. The screen now returns to its pre-dim brightness level when the screen is unblanked under wayland. This was a false report; not a bug with gnome-settings-daemon.
Bug#971569: mutter: Laptop display stays dimmed after blanking screen under wayland
Package: mutter Version: 3.38.0-2 Severity: normal X-Debbugs-Cc: jlsan...@protonmail.com On a Thinkpad X220, I have GNOME set to dim the screen when inactive, with blank screen enabled. When the screen is blanked after inactivity (display turns off), interacting with the laptop turns on the screen but does not reset the brightness level. (It stays dimmed and the brightness slider does not match the brightness level of the display.) The user would have to adjust the brightness (each time the laptop screen is blanked) or connect the laptop to power, to free the display from the dimmed state. This is reproducible when using GNOME/mutter under Wayland _and_ on battery power with "Dim Screen When Inactive" enabled. This does not happen when plugged in. I have not been able to reproduce this bug when running GNOME/mutter under Xorg. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 mutter depends on: ii adwaita-icon-theme3.38.0-1 ii gnome-settings-daemon-common 3.38.0-2 ii gsettings-desktop-schemas 3.38.0-2 ii libc6 2.31-3 ii libgles2 1.3.2-1 ii libglib2.0-0 2.66.0-2 ii libmutter-7-0 3.38.0-2 ii libwayland-server01.18.0-2~exp1.1 ii libx11-6 2:1.6.12-1 ii libxcomposite11:0.4.5-1 ii mutter-common 3.38.0-2 ii zenity3.32.0-5 mutter recommends no packages. Versions of packages mutter suggests: ii gnome-control-center 1:3.38.0-2 ii xdg-user-dirs 0.17-2 -- no debconf information
Bug#970894: gnome-clocks: Backport newer version
Package: gnome-clocks Version: 3.30.1-2 Severity: wishlist Dear Maintainer, The gnome-clocks' timer does not work as intended under Wayland when the application is minimized or in a separate gnome-shell workspace. The timer fails to go off unless it is in view. This is presumably fixed in an upstream version[0][1][2]. If time allows, a backport of a newer version would be greatly appreciated. * What led up to the situation? Opening gnome-clocks 3.30.1 (debian10/buster/stable version), and setting a timer for at least one minute. * What exactly did you do (or not do) that was effective (or ineffective)? While using GNOME under Wayland, minimizing gnome-clocks or moving to a separate gnome-shell workspace and keeping gnome-clocks minimized or staying in a different workspace while the timer has completely count down to zero. (Timer works as intended under Xorg). * What was the outcome of this action? gnome-clocks does not send a notification or play a sound when the timer reaches zero. * What outcome did you expect instead? gnome-clocks to display a notification and play a sound when the timer reaches zero. 0: https://bugzilla.redhat.com/show_bug.cgi?id=1525025#c9 1: https://bugzilla.gnome.org/show_bug.cgi?id=791535 2: https://gitlab.gnome.org/GNOME/gnome-clocks/-/merge_requests/8 -- System Information: Debian Release: 10.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-10-amd64 (SMP w/16 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-clocks depends on: ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2 ii geoclue-2.0 2.5.2-1 ii libc62.28-10 ii libcairo21.16.0-4 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libgeoclue-2-0 2.5.2-1 ii libgeocode-glib0 3.26.1-1 ii libglib2.0-0 2.58.3-2+deb10u2 ii libgnome-desktop-3-173.30.2.1-2 ii libgsound0 1.0.2-4 ii libgtk-3-0 3.24.5-1 ii libgweather-3-15 3.28.2-2 gnome-clocks recommends no packages. gnome-clocks suggests no packages. -- no debconf information
Bug#898768: gnome-twitch: Segfault everytime you try to watch a stream
Package: gnome-twitch
Version: 0.3.1-1
Followup-For: Bug #898768
Dear Maintainer,
This bug is still present in Debian stretch (as of version 9.8).
Because of this, gnome-twitch is _still_ unusable in stable.
Is it possible to bring the patch to stable?
Thank you for your time!
Jaycee
-- System Information:
Debian Release: 9.8
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-8-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gnome-twitch depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.26.0-2+b1
ii libc62.24-11+deb9u4
ii libgdk-pixbuf2.0-0 2.36.5-2+deb9u2
ii libglib2.0-0 2.50.3-2
ii libgtk-3-0 3.22.11-1
ii libjson-glib-1.0-0 1.2.6-1
ii libpeas-1.0-01.20.0-1+b1
ii libsoup2.4-1 2.56.0-2+deb9u2
ii libwebkit2gtk-4.0-37 2.18.6-1~deb9u1
ii libx11-6 2:1.6.4-3+deb9u1
Versions of packages gnome-twitch recommends:
ii gnome-twitch-player-backend-gstreamer-cairo 0.3.1-1
gnome-twitch suggests no packages.
-- no debconf information
[22:43:32] Message - GNOME-Twitch : {GtApp} Startup
[22:43:32] Message - GNOME-Twitch : {GtApp} Loading chat settings
[22:43:32] Message - GNOME-Twitch : {GtApp} Activate
[22:43:38] Message - GNOME-Twitch : {GtPlayer} Can't open channel, no backend
loaded
libdc1394 error: Failed to initialize libdc1394
[22:43:41] Message - GNOME-Twitch : {GtPlayer} Loaded player backend 'GStreamer
Cairo player backend'
[22:43:41] Message - GNOME-Twitch : {GtPlayerBackendGstreamerCairo} Init
[22:43:41] Warning - GNOME-Twitch : cannot set NULL uri
[22:43:41] Message - GNOME-Twitch : {GtPlayer} Opening stream 'overwatchleague'
with quality 'source'
[22:43:41] Warning - GNOME-Twitch : {GtTwitch} Received unsuccessful response
from url 'http://api.twitch.tv/api/channels/overwatchleague/access_token' with
code '400' and body '{"error":"Bad Request","status":400,"message":"Requests
must be made over SSL"}'
[22:43:41] Warning - GNOME-Twitch : {GtTwitch} Error getting stream access
token for channel='overwatchleague'
[22:43:41] Critical - GNOME-Twitch : gt_twitch_all_streams: assertion 'token !=
NULL' failed
[22:43:41] Warning - GNOME-Twitch : {GtPlayer} Error opening stream
[22:43:42] Message - GNOME-Twitch : {GtIrc} Connecting with nick='',
host='irc.chat.twitch.tv' and port='80'
[22:43:42] Message - GNOME-Twitch : {GtIrc} Joining with
channel='#overwatchleague'
