Your message dated Mon, 8 Jan 2024 23:17:09 +0300
with message-id <[email protected]>
and subject line Re: Bug#1009998: gvfs-backends: Unable to access
smb://host/sharing on any file manager after upgrade
has caused the Debian Bug report #1009998,
regarding gvfs-backends: Unable to access smb://host/sharing on any file
manager after upgrade
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.)
--
1009998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009998
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gvfs-backends
Version: 1.50.0-1
Severity: grave
Tags: a11y
Justification: renders package unusable
X-Debbugs-Cc: [email protected]
Dear Maintainer,
When try access smb://host/sharing on all file systens managers the system
report fails when mount Windows sharing. Invalid argument.
This sharing is accessible via smbclient //host/sharing.
This problem started after upgrading the package.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.16.0-6-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND,
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8),
LANGUAGE=pt_BR:pt:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gvfs-backends depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.40.0-3
ii gvfs 1.50.0-1
ii gvfs-common 1.50.0-1
ii gvfs-daemons 1.50.0-1
ii gvfs-libs 1.50.0-1
ii libarchive13 3.6.0-1
ii libavahi-client3 0.8-5
ii libavahi-common3 0.8-5
ii libavahi-glib1 0.8-5
ii libc6 2.33-7
ii libcdio-cdda2 10.2+2.0.0-1+b2
ii libcdio-paranoia2 10.2+2.0.0-1+b2
ii libcdio19 2.1.0-3
ii libgcrypt20 1.10.1-2
ii libgdata22 0.18.1-2
ii libglib2.0-0 2.72.1-1
ii libgoa-1.0-0b 3.44.0-1
ii libgphoto2-6 2.5.27-1
ii libgphoto2-port12 2.5.27-1
ii libgudev-1.0-0 237-2
ii libimobiledevice6 1.3.0-6+b1
ii libmtp9 1.1.19-1
ii libnfs13 4.0.0-1
ii libplist3 2.2.0-6+b1
ii libpolkit-gobject-1-0 0.105-33
ii libsmbclient 2:4.16.0+dfsg-6
ii libsoup-3.0-0 3.0.6-1
ii libusb-1.0-0 2:1.0.26-1
ii libxml2 2.9.13+dfsg-1
ii psmisc 23.4-2
Versions of packages gvfs-backends recommends:
ii gnome-keyring 40.0-3
Versions of packages gvfs-backends suggests:
ii bluez-obexd 5.64-1
ii samba-common 2:4.16.0+dfsg-6
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2:4.18.3+dfsg-1
On Thu, 3 Nov 2022 08:17:17 +0300 Michael Tokarev <[email protected]> wrote:
[ https://bugs.debian.org/1009998 ]
Ok. This bug has been open for quite some time. And I'm confused now.
Is the reported issue still an issue? If it is, what's the issue, exactly?
There are several problems here, and at least some of them has been resolved.
It's been more than year since last activity in this bug report,
and I see no reason to keep it open.
Closing with more or less arbitrary version.
If you think it is incorrect and there are issues still, please
feel free to re-open this bug report and provide more details.
Thanks,
/mjt
--- End Message ---
