Your message dated Mon, 31 Aug 2026 21:11:49 +0200
with message-id
<caaajcmyu7jd2koaawujgtpywf-qzcg_7z0yqha0qw50vt2t...@mail.gmail.com>
and subject line Re: libwbxml2-0: Bad Request (0x40) while using MultiSync 0.90
has caused the Debian Bug report #502616,
regarding libwbxml2-0: Bad Request (0x40) while using MultiSync 0.90
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.)
--
502616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502616
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libwbxml2-0
Version: 0.9.2-6
Severity: important
I am using the most recent version of the package, that is version 0.9.2-6
of libwbxml. I still get the same error message as in bug 475305, upon trying
to sync my nokia 6085 using MultiSync 0.90.
I use Ubuntu 8.10. Any cure for that?
-- System Information:
Debian Release: lenny/sid
APT prefers intrepid-updates
APT policy: (500, 'intrepid-updates'), (500, 'intrepid-security'), (500,
'intrepid'), (500, 'hardy-proposed')
Architecture: i386 (i686)
Kernel: Linux 2.6.27-7-server (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libwbxml2-0 depends on:
ii libc6 2.8~20080505-0ubuntu7 GNU C Library: Shared libraries
ii libexpat1 2.0.1-4 XML parsing C library - runtime li
ii libpopt0 1.14-4 lib for parsing cmdline parameters
ii zlib1g 1:1.2.3.3.dfsg-12ubuntu1 compression library - runtime
libwbxml2-0 recommends no packages.
libwbxml2-0 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
There have been many changes to Debian since this bug was originally
reported. If you are still experiencing this issue with Debian 13 (or
with Debian 12 or Testing or Unstable), please report a new bug.
Thank you,
Jeremy Bícha
--- End Message ---
