Your message dated Mon, 12 Jun 2017 18:44:45 +0200
with message-id <[email protected]>
and subject line Re: Bug#864270: libgcrypt20: Since the update pushed to
stretch today the library seemingly broke gnome-based filemanagers like caja,
nemo and nautilus.
has caused the Debian Bug report #864270,
regarding libgcrypt20: Since the update pushed to stretch today the library
seemingly broke gnome-based filemanagers like caja, nemo and nautilus.
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 [email protected]
immediately.)
--
864270: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864270
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libgcrypt20
Version: 1.7.6-2
Severity: important
Dear Maintainer,
Today June 5th of 2017 a library update was pushed into stretch, it seems
that libgcrypt20 is a core part for running some gnome-based desktops, after
the update caja, nautilus & nemo applications stop responding after init, the
superuser can start and use them flawlessly but when a normal user tries to
open a window to work it stops responding, not just the window but the entire
caja process freezes, I've reproduced this in my main laptop and 2 other
computers running Debian Stretch & MATE 1.16 just upgrade those 2 libraries to
see the effects.
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_MX.UTF-8, LC_CTYPE=es_MX.UTF-8 (charmap=UTF-8),
LANGUAGE=es_MX:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On 2017-06-12 Omar Jair Purata Funes <[email protected]> wrote:
> On 2017-06-08 Andreas Metzler <[email protected]> wrote:
[...]
>> So this bug requires using a combination of caja 1.16.2-2 and
>> libgcrypt20 1.7.6-2, i.e. both caja 1.16.2-2 with libgcrypt20 1.7.6-1
>> and caja 1.16.6-1 with libgcrypt20 1.7.6-2 work?
[...]
> In simple words, yes, bug is now fixed completely, I already upgraded both
> computers and broken caja "repaired" itself.
Let us close the bug then.
--- End Message ---
