Your message dated Tue, 10 May 2022 22:13:04 +0300
with message-id <[email protected]>
and subject line Re: Bug#931688: smbclient: Unable to initialize messaging 
context
has caused the Debian Bug report #931688,
regarding smbclient: Unable to initialize messaging context
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.)


-- 
931688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931688
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: smbclient
Version: 2:4.9.5+dfsg-5
Severity: normal

Dear Maintainer,

after the upgrade to Debian Buster I get the

'Unable to initialize messaging context"

error message. This messages causes the Amanda Backup (package:
amanda-client and amanda-server) to stop working.

Is it a bug in the smbclient?

Output:

backup@chronos:~$ /usr/bin/smbclient  //192.168.0.250/ftp -U backup
WARNING: The "syslog" option is deprecated
Unable to initialize messaging context
WARNING: The "syslog" option is deprecated
Enter A2GB\backup's password:
Try "help" to get a list of possible commands.
smb: \> quit

Amanda Debian Bug reported with the number 931622 but it seems to be a
smbclient problem.

Greetings
Tobias
-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages smbclient depends on:
ii  dpkg          1.19.7
ii  libarchive13  3.3.3-4
ii  libbsd0       0.9.1-2
ii  libc6         2.28-10
ii  libpopt0      1.16-12
ii  libreadline7  7.0-5
pn  libsmbclient  <none>
ii  libtalloc2    2.1.14-2
ii  libtevent0    0.9.37-1
ii  samba-common  2:4.9.5+dfsg-5
pn  samba-libs    <none>

smbclient recommends no packages.

Versions of packages smbclient suggests:
ii  cifs-utils       2:6.8-2
pn  heimdal-clients  <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 2:4.13.13+dfsg-1

On Wed, 18 Sep 2019 11:41:12 +0200 =?windows-1252?Q?L.P.H._van_Belle?= 
<[email protected]> wrote:
I got a quick update from the samba list.
Is it a bug in the smbclient?
Yes, Its a confirmed bug. Just found upstream bug report: https://bugzilla.samba.org/show_bug.cgi?id=13925

This issue seems to be gone in the bullseye version of samba (4.13.13+).
Closing this bugreport now.

Thanks,

/mjt

--- End Message ---

Reply via email to