Bug#981420: libglib2.0-0: gnome-keyring unable to unlock login keyring
Hello Simon, Thank you for your efforts! > Do you have the dbus-user-session package installed? I had to install it. Indeed, it helps - now gnome-keyring is working fine with latest package version of libglib. > If you rely on the ability to have a separate D-Bus session bus per > X11 display for the same uid, then you can't use dbus-user-session > permanently, because it represents a different model where each uid has > only one instance of the D-Bus session bus. For my "testing" setup it is ok. But I'm asking myself - is it only gnome-keyring affected or this "security hardening" could break other GNOME/MATE parts? dbus-x11 is a strict dependency of mate-session-manager/gnome-session-bin, while dbus-user-session is not even suggested... -- Best Regards, Charles Malaheenee
Bug#981420: libglib2.0-0: gnome-keyring unable to unlock login keyring
Hello Simon, Thank you for the attention to this bug! Our DE is Mate. Probably, the problem is related to the mix of components ? Here is the output (I do not remember to have to change the permissions of gnome-keyring-daemon): ls -l /usr/bin/gnome-keyring-daemon -rwxr-xr-x 1 root root 1143712 Mar 11 2020 /usr/bin/gnome-keyring-daemon getcap /usr/bin/gnome-keyring-daemon /usr/bin/gnome-keyring-daemon cap_ipc_lock=ep In journalctl there are a lot messages from systemd or dbus-daemon, like "dbus-daemon[970]: [session uid=1000 pid=968] Successfully activated service 'org.mate.panel.applet.ClockAppletFactory'" or "systemd[902]: Started Sound Service." Concerning gnome-keyring-daemon, here is the output of journalctl for all possible package versions: (version 2.66.4-3, bug appears) Jan 30 14:26:13 big-pc gnome-keyring-daemon[920]: couldn't connect to dbus session bus: Cannot spawn a message bus when setuid Jan 30 14:26:13 big-pc gnome-keyring-daemon[920]: couldn't connect to dbus session bus: Cannot spawn a message bus when setuid Jan 30 14:26:14 big-pc gnome-keyring-daemon[920]: couldn't connect to dbus session bus: Cannot spawn a message bus when setuid Jan 30 14:26:14 big-pc gnome-keyring-daemon[920]: The SSH agent was already initialized Jan 30 14:26:14 big-pc gnome-keyring-daemon[920]: The PKCS#11 component was already initialized Jan 30 14:26:39 big-pc gnome-keyring-daemon[920]: couldn't connect to dbus session bus: Cannot spawn a message bus when setuid (version 2.66.4-1, no bug) Jan 31 18:13:23 big-pc gnome-keyring-daemon[2054]: The Secret Service was already initialized Jan 31 18:13:23 big-pc gnome-keyring-daemon[2054]: The SSH agent was already initialized Jan 31 18:13:23 big-pc gnome-keyring-daemon[2054]: The PKCS#11 component was already initialized (version 2.66.4-3+revert981420targeted, no bug) Jan 31 18:31:57 big-pc gnome-keyring-daemon[924]: GLib-GIO: Not suppressing use of DBUS_SESSION_BUS_ADDRESS because not setuid, even though AT_SECURE Jan 31 18:31:57 big-pc gnome-keyring-daemon[924]: The Secret Service was already initialized Jan 31 18:31:57 big-pc gnome-keyring-daemon[924]: The SSH agent was already initialized Jan 31 18:31:57 big-pc gnome-keyring-daemon[924]: The PKCS#11 component was already initialized (version 2.66.4-3+revert981420dbus, no bug) Jan 31 18:36:50 big-pc gnome-keyring-daemon[920]: The Secret Service was already initialized Jan 31 18:36:50 big-pc gnome-keyring-daemon[920]: The SSH agent was already initialized Jan 31 18:36:50 big-pc gnome-keyring-daemon[920]: The PKCS#11 component was already initialized (version 2.66.4-3+revert981420dbus, no bug) Jan 31 18:39:09 big-pc gnome-keyring-daemon[905]: The Secret Service was already initialized Jan 31 18:39:09 big-pc gnome-keyring-daemon[905]: The SSH agent was already initialized Jan 31 18:39:09 big-pc gnome-keyring-daemon[905]: The PKCS#11 component was already initialized Hope this helps. -- Best Regards, Charles Malaheenee
Bug#978131: qemu-system-x86: Segfault when starting a VM
Package: qemu-system-x86 Version: 1:5.2+dfsg-2 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: malahee...@gmx.fr Dear Maintainer, Not sure is it related with qemu itself, but suddenly a launch of a VM through libvirt fails with a standard error message: virsh # start board.debian.malaheenee.ca error: Failed to start domain board.debian.malaheenee.ca error: internal error: qemu unexpectedly closed the monitor The syslog has a "segfault" message: Dec 26 06:57:45 big-pc kernel: [ 564.377369] qemu-system-x86[2278]: segfault at 28 ip 55e80f667dfc sp 7ffeb92c06e0 error 6 in qemu- system-x86_64[55e80f476000+4df000] Dec 26 06:57:45 big-pc kernel: [ 564.377382] Code: 00 48 8d 3d 7e 50 31 00 48 8b 08 31 c0 e8 cc bc ff ff 4c 8b 2d 15 ec 71 00 e9 42 ff ff ff 48 8d 3d 92 26 45 00 e8 c4 bb ff ff 40 28 01 00 00 00 e9 73 fc ff ff 48 8d 35 19 bb 3b 00 48 8d 3d Initially I thought it is because of the kernel, because last week it worked (that's why the kernel is 5.9.0-4-amd64). I can do more test if needed. Best regards, Charles -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 'testing'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-4-amd64 (SMP w/4 CPU threads) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages qemu-system-x86 depends on: ii ipxe-qemu 1.0.0+git-20190125.36a4c85-5 ii libaio1 0.3.112-9 ii libc6 2.31-6 ii libcapstone4 4.0.2-3 ii libfdt1 1.6.0-1 ii libgcc-s1 10.2.1-3 ii libglib2.0-0 2.66.4-1 ii libgnutls30 3.7.0-3 ii libibverbs1 32.0-1+b1 ii libjpeg62-turbo 1:2.0.5-1.1 ii libnettle83.6-2 ii libnuma1 2.0.12-1+b1 ii libpixman-1-0 0.40.0-1 ii libpmem1 1.10-1 ii libpng16-16 1.6.37-3 ii librdmacm132.0-1+b1 ii libsasl2-22.1.27+dfsg-2 ii libseccomp2 2.5.1-1 ii libslirp0 4.4.0-1 ii libudev1 247.2-2 ii liburing1 0.7-3 ii libusb-1.0-0 2:1.0.24-2 ii libvdeplug2 4.0.1-2 ii libxendevicemodel14.14.0+88-g1d1d1f5391-2 ii libxenevtchn1 4.14.0+88-g1d1d1f5391-2 ii libxenforeignmemory1 4.14.0+88-g1d1d1f5391-2 ii libxengnttab1 4.14.0+88-g1d1d1f5391-2 ii libxenmisc4.144.14.0+88-g1d1d1f5391-2 ii libxenstore3.04.14.0+88-g1d1d1f5391-2 ii libxentoolcore1 4.14.0+88-g1d1d1f5391-2 ii qemu-system-common1:5.2+dfsg-2 ii qemu-system-data 1:5.2+dfsg-2 ii seabios 1.14.0-2 ii zlib1g1:1.2.11.dfsg-2 Versions of packages qemu-system-x86 recommends: pn ovmf pn qemu-system-gui ii qemu-utils 1:5.2+dfsg-2 Versions of packages qemu-system-x86 suggests: pn qemu-block-extra ii qemu-system-data [sgabios] 1:5.2+dfsg-2 ii samba 2:4.13.3+dfsg-1 pn vde2 -- no debconf information
Bug#916279: qemu-system-common
Hello! Just for diversity - English text :) dpkg: error processing archive /tmp/apt-dpkg-install-3L8qhF/00-qemu-system-common_1%3a3.1+dfsg-1_amd64.deb (--unpack): trying to overwrite '/usr/share/doc-base/qemu-system-doc', which is also in package qemu-system-data 1:2.12+dfsg-3 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /tmp/apt-dpkg-install-3L8qhF/00-qemu-system-common_1%3a3.1+dfsg-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) As temporary solution - rollback to 2.12. -- Best Regards, Charles Malaheenee
Bug#826579: onboard: Failed to start without gir1.2-atspi-2.0
Package: onboard
Version: 1.2.0-1
Severity: grave
Tags: newcomer
Justification: renders package unusable
Dear Maintainer,
As described in title, without installed 'gir1.2-atspi-2.0' onboard fails to
start with python error like this:
Traceback (most recent call last):
File "/usr/bin/onboard", line 35, in
from Onboard.OnboardGtk import OnboardGtk as Onboard
File "/usr/lib/python3/dist-packages/Onboard/OnboardGtk.py", line 35, in
require_gi_versions()
File "/usr/lib/python3/dist-packages/Onboard/Version.py", line 28, in
require_gi_versions
gi.require_version('Atspi', '2.0')
File "/usr/lib/python3/dist-packages/gi/__init__.py", line 102, in
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Atspi not available
We suggest to move 'gir1.2-atspi-2.0' from 'Recommends' to 'Depends'.
Best regards,
Malahenee
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: i386 (i686)
Foreign Architectures: amd64
Kernel: Linux 4.5.0-2-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages onboard depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.26.0-1
ii gir1.2-appindicator3-0.1 0.4.92-4
ii gir1.2-gdkpixbuf-2.0 2.34.0-1
ii gir1.2-glib-2.0 1.48.0-2
ii gir1.2-gtk-3.0 3.20.6-1
ii gir1.2-pango-1.0 1.40.1-1
ii iso-codes3.68-1
ii libc62.22-9
ii libcairo-gobject21.14.6-1+b1
ii libcairo21.14.6-1+b1
ii libcanberra0 0.30-3
ii libdconf10.26.0-1
ii libgcc1 1:6.1.1-4
ii libgdk-pixbuf2.0-0 2.34.0-1
ii libglib2.0-0 2.48.1-1
ii libgtk-3-0 3.20.6-1
ii libhunspell-1.4-01.4.1-2
ii libpango-1.0-0 1.40.1-1
ii libpangocairo-1.0-0 1.40.1-1
ii librsvg2-common 2.40.15-1
ii libstdc++6 6.1.1-4
ii libx11-6 2:1.6.3-1
ii libxi6 2:1.7.6-1
ii libxkbfile1 1:1.0.9-2
ii libxtst6 2:1.2.2-1+b1
ii onboard-common 1.2.0-1
ii python3 3.5.1-3
ii python3-cairo1.10.0+dfsg-5+b1
ii python3-dbus 1.2.4-1
ii python3-gi-cairo 3.20.1-1
pn python3.5:any
Versions of packages onboard recommends:
ii gir1.2-atspi-2.0 2.20.2-1
pn onboard-data
ii xdg-utils 1.1.1-1
Versions of packages onboard suggests:
pn mousetweaks
-- no debconf information
Bug#773495: docker.io: Build new version with security patches
Package: docker.io Version: 1.3.2~dfsg1-1 Severity: grave Tags: upstream security Justification: user security hole Dear Maintainers, Long time ago there was a new version - 1.4 (and now 1.4.1) with several security corrections - http://docs.docker.com/v1.4/release-notes/. I suggest to build it ASAP. Best regards, Malaheenee -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_CA.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages docker.io depends on: ii adduser 3.113+nmu3 ii init-system-helpers 1.22 ii iptables 1.4.21-2+b1 ii libapparmor1 2.9.0-3 ii libc62.19-13 ii libdevmapper1.02.1 2:1.02.90-2 ii libsqlite3-0 3.8.7.2-1 ii perl 5.20.1-3 Versions of packages docker.io recommends: pn aufs-toolsnone ii ca-certificates 20141019 pn cgroupfs-mount | cgroup-lite none ii git 1:2.1.3-1 ii xz-utils 5.1.1alpha+20120614-2+b3 Versions of packages docker.io suggests: pn btrfs-tools none pn debootstrap none pn lxc none pn rinsenone -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738664: initramfs-tools: remove all kernels while purge
Package: initramfs-tools
Version: 0.115
Severity: critical
Tags: upstream
Justification: breaks the whole system
Dear Maintainer,
When I try to purge iniramfs-tools in jessie/sid, it also removes all installed
kernels without standard warnings (like sysvinit):
---
sudo aptitude purge initramfs-tools
Les paquets suivants seront ENLEVÉS :
initramfs-tools{p} [0.115]
0 paquets mis à jour, 0 nouvellement installés, 1 à enlever et 0 non mis à
jour.
Il est nécessaire de télécharger 0 o d'archives. Après dépaquetage, 334 ko
seront libérés.
Les paquets suivants ont des dépendances non satisfaites :
linux-image-3.12-1-686-pae : Dépend: initramfs-tools (= 0.110~) mais il ne
sera pas installé. ou
linux-initramfs-tool qui est un paquet
virtuel
Les actions suivantes permettront de résoudre ces dépendances :
Supprimer les paquets suivants :
1) linux-image-3.12-1-686-pae
2) linux-image-686-pae
Accepter cette solution ? [Y/n/q/?] y
Les paquets suivants seront ENLEVÉS :
initramfs-tools{p} [0.115] libuuid-perl{u} [0.05-1] linux-base{u} [3.5]
linux-image-3.12-1-686-pae{a} [3.12.9-1]
linux-image-686-pae{a} [3.12+55]
0 paquets mis à jour, 0 nouvellement installés, 5 à enlever et 0 non mis à
jour.
Il est nécessaire de télécharger 0 o d'archives. Après dépaquetage, 108 Mo
seront libérés.
Voulez-vous continuer ? [Y/n/?] n
---
I think that is very dangerous for simple users - after deleting strange
packages their systems fails to boot.
Best regards,
Malaheenee
-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 3.0M Feb 11 18:44 /boot/initrd.img-3.12-1-686-pae
-- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.12-1-686-pae
root=UUID=0ae21b3d-1e37-4de4-bbc5-69fe18afec37 ro quiet
-- resume
RESUME=UUID=a08ed0d9-d715-400e-8bfb-6a7f600130c8
-- /proc/filesystems
ext3
ext2
ext4
fuseblk
-- lsmod
Module Size Used by
cpuid 12583 0
usb_storage43324 0
cpufreq_conservative13872 2
pci_stub 12397 1
vboxpci22738 0
vboxnetadp 25431 0
vboxnetflt 27112 0
vboxdrv 236389 3 vboxnetadp,vboxnetflt,vboxpci
rfcomm 32155 14
bnep 17184 2
uinput 17068 1
loop 21960 0
fuse 68789 1
btusb 21248 0
bluetooth 195092 22 bnep,btusb,rfcomm
hid_generic12369 0
usbhid 39650 0
hid76882 2 hid_generic,usbhid
joydev 16847 0
uvcvideo 69768 0
videobuf2_vmalloc 12720 1 uvcvideo
videobuf2_memops 12471 1 videobuf2_vmalloc
videobuf2_core 34683 1 uvcvideo
videodev 90700 2 uvcvideo,videobuf2_core
media 17840 2 uvcvideo,videodev
sg 25573 0
sr_mod 21563 0
cdrom 34540 1 sr_mod
iTCO_wdt 12727 0
iTCO_vendor_support12585 1 iTCO_wdt
coretemp 12734 0
psmouse76428 0
snd_hda_codec_si305412662 1
serio_raw 12737 0
pcspkr 12531 0
evdev 17136 23
lpc_ich16616 0
ata_generic12450 0
snd_hda_codec_realtek40686 1
arc4 12480 2
firewire_ohci 34856 0
radeon 1193388 2
iwl394553405 0
snd_hda_intel 34991 6
iwlegacy 45729 1 iwl3945
mac80211 389428 2 iwl3945,iwlegacy
snd_hda_codec 126872 3
snd_hda_codec_realtek,snd_hda_codec_si3054,snd_hda_intel
ata_piix 25240 0
snd_hwdep 12906 1 snd_hda_codec
ttm55501 1 radeon
drm_kms_helper 35231 1 radeon
mfd_core 12537 1 lpc_ich
firewire_core 51080 1 firewire_ohci
r852 17265 0
sm_common 16469 1 r852
nand 47833 2 r852,sm_common
nand_ecc 12447 1 nand
nand_ids8209 1 nand
mtd36923 2 nand,sm_common
crc_itu_t 12331 1 firewire_core
r592 17143 0
ehci_pci 12432 0
uhci_hcd 26364 0
memstick 13432 1 r592
ehci_hcd 43678 1 ehci_pci
sdhci_pci 17643 0
sdhci 26483 1 sdhci_pci
mmc_core 79303 2 sdhci,sdhci_pci
cfg80211 343711 3 iwl3945,iwlegacy,mac80211
snd_pcm69546 4 snd_hda_codec_si3054,snd_hda_codec,snd_hda_intel
drm 194291 4 ttm,drm_kms_helper,radeon
snd_page_alloc 12882 2 snd_pcm,snd_hda_intel
usbcore 138045 7
btusb,uhci_hcd,uvcvideo,usb_storage,ehci_hcd,ehci_pci,usbhid
asus_laptop22309 0
i2c_algo_bit
