containerd seems to have similar issues from Kubernetes... (I need to
check if a bug exists for that as well)
kubelet.go:2049] [failed to "KillContainer" for "ceph-exporter" with
KillContainerError: "rpc error: code = Unknown desc = failed to kill container
\"373f6f3fc02b903a49b6d5e330366944e9c
Some issue on 24.04:
root@noble ~ # curl -s https://launchpadlibrarian.net/250515419/test.html |
html2text; echo $?
Input recoding failed due to invalid input sequence. Unconverted part of text
follows.
“Test�?)
0
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This also took Docker down on 18.04 with the update for USN-4653-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870514
Title:
update containerd:amd64 1.3.3-0 stops docker daemon
To manage notific
That code path fails to detect that neither --wait or -w is supported, since
iptables-restore returns a successful return code on invalid parameters and
firewalld uses the return code to detect whether it works:
# echo "#foo" | /sbin/iptables-restore --wadit=2; echo $?
/sbin/iptables-restore: unr
Public bug reported:
firewalld from Ubuntu 18.04 LTS sometimes attempts to use the `--wait`
option to iptables-restore, which is only valid on iptables 1.8.x and
newer and not on 1.6.1, as bundled with bionic. (At least according to
the man page, the comments in the firewalld code implies that it
Mostly when firewalld fails with that error, a restart will fix it (It
seems to only hit that code path sometimes), however if it is a headless
box, that restart might be tricky.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Gnome bug was migrated to Gitlab (over at
https://gitlab.gnome.org/GNOME/glib/issues/54 ) and the bug number
changed as a result. Currently the close bug (due to being migrated)
seems to result in it being set expired all the time.
** Changed in: gvfs
Importance: Low => Undecided
** Changed in
Upstream bug URL changed to
https://gitlab.gnome.org/GNOME/glib/issues/54
Unable to edit it...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/378783
Title:
xdg-open *.desktop opens text editor
To m
Similar issue when upgrading to 18.04's current beta.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1223308
Title:
package hylafax-server 3:6.0.6-4 failed to install/upgrade: subprocess
installed
I haven't reported it to Debian, I did not have a test system to confirm
that it is present there as well (I'm quite sure it would be present, it
is the same package source) (And https://www.debian.org/Bugs/Reporting
for manual reporting seems quite scary...)
--
You received this bug notification
@Roland: Incorrect upstream, that is python-html2text /
python3-html2text. This is from http://www.mbayer.de/html2text/ (And
that won't have the issue, since it was introduced in Debian's UTF-8
patch) (Debian might also be affected though)
--
You received this bug notification because you are a m
Also affects 1.3.2a-18 on Ubuntu 16.04.
** Description changed:
When running html2text on a file with incorrect encoding (e.g. indicated
as us-ascii, but actually UTF-8), it fails with an error message but
returns a successful result code (0).
Actual output:
-
$ htm
Note: This is probably also present in Debian, since it seems like the
Ubuntu package is mostly unmodified.
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
My attempt at an actual patch.
The other method, of actually changing all the error handling to save
that there have been an error and returning the code at the end might
still make sense for later.
** Patch added: "Patch to modify patches to return an error code on recoding
errors"
https://
Diffs for patch files: (for simple fix - return 2 for recoding error,
don't attempt to continue to other files) (The problem seems to be
present to at least the precise version)
--- 611-recognize-input-encoding.patch.orig 2016-03-31 18:25:01.914598768
+0200
+++ 611-recognize-input-encoding.pa
The simplest fix is to replace the "continue" in the recode error
handlers with "exit(1)" (Patched html2text.C lines 595 and 555). (Using
a different value for encoding errors might be useful)
This makes the error handling consistent with other cases, like failing
to open a file. (See line 482)
A
Quick method to test:
sudo apt-get install html2text
curl -s https://launchpadlibrarian.net/250515419/test.html | html2text; echo $?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564317
Title:
Succ
Public bug reported:
When running html2text on a file with incorrect encoding (e.g. indicated
as us-ascii, but actually UTF-8), it fails with an error message but
returns a successful result code (0).
Actual output:
-
$ html2text test.html; echo $?
Input recoding failed due to inv
See page 7 of https://www.ietf.org/rfc/rfc1952.txt (ISIZE is the
relevant field)
It is an limitation of the gzip file format...
It is also documented in the gzip man page under "BUGS", with a (slow)
workaround...
One way to fix it might be to define an "extra field" with a larger
original file s
19 matches
Mail list logo
