[Bug 1564317] Re: Successful return code on encoding error
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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564317 Title: Successful return code on encoding error To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1564317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870514] Re: update containerd:amd64 1.3.3-0 stops docker daemon
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1870514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835188] Re: firewalld attempts to use parameter that requires a newer iptables version
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: unrecognized option '--wadit=2' 0 The current version of firewalld fixed that, by looking for the error message as well: https://github.com/firewalld/firewalld/commit/2e929389eb15b12e96f18e5fe3dc5ae31639e8dd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835188 Title: firewalld attempts to use parameter that requires a newer iptables version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firewalld/+bug/1835188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835188] [NEW] firewalld attempts to use parameter that requires a newer iptables version
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 was supported on an older version, but that might be with Fedora patches) This seems to originate from firewalld-0.4.4.6/src/firewall/core/ipXtables.py, line 337. If this runs firewalld fails to create the rules when starting, resulting in wither no rules loaded, or the policies loaded, without any rules, which blocks SSH. It is not clear when this gets triggered, with several servers deployed with the same Ansible script, some have this issue, some work fine. The unit file was overwriten as per this to get it to start in the first place: https://github.com/firewalld/firewalld/issues/414 The warning that accompanies the failed rule loading is: ``` WARNING: '/sbin/iptables-restore --wait=2 -n' failed: /sbin/iptables-restore: unrecognized option '--wait=2'#012iptables-restore: line 93 failed ``` iptables version: 1.6.1-2ubuntu2 firewalld version: 0.4.4.6-1 ** Affects: firewalld (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835188 Title: firewalld attempts to use parameter that requires a newer iptables version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firewalld/+bug/1835188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835188] Re: firewalld attempts to use parameter that requires a newer iptables version
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://bugs.launchpad.net/bugs/1835188 Title: firewalld attempts to use parameter that requires a newer iptables version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firewalld/+bug/1835188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 378783] Re: xdg-open *.desktop opens text editor
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: gvfs Status: Expired => New ** Changed in: gvfs Remote watch: GNOME Bug Tracker #343896 => None -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/378783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 378783] Re: xdg-open *.desktop opens text editor
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 manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/378783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1223308] Re: package hylafax-server 3:6.0.6-4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
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 post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hylafax/+bug/1223308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564317] Re: Successful return code on encoding error
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564317 Title: Successful return code on encoding error To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1564317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564317] Re: Successful return code on encoding error
@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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564317 Title: Successful return code on encoding error To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1564317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564317] Re: Successful return code on encoding error
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: - $ html2text test.html; echo $? Input recoding failed due to invalid input sequence. Unconverted part of text follows. “Test”) 0 Expected output: (substitute 1 for any appropriate failure code) -- $ html2text test.html; echo $? Input recoding failed due to invalid input sequence. Unconverted part of text follows. “Test”) 1 This seem to have been introduced by 611-recognize-input-encoding.patch - OS: Ubuntu 14.04 - Package: html2text-1.3.2a-17 + OS: Ubuntu 14.04 / Ubuntu 16.04 + Package: html2text-1.3.2a-17 / html2text-1.3.2a-18 -- 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: Successful return code on encoding error To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1564317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564317] Re: Successful return code on encoding error
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. https://bugs.launchpad.net/bugs/1564317 Title: Successful return code on encoding error To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1564317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564317] Re: Successful return code on encoding error
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://bugs.launchpad.net/ubuntu/+source/html2text/+bug/1564317/+attachment/4619089/+files/htmltext-encoding-error-code.patch -- 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: Successful return code on encoding error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/html2text/+bug/1564317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564317] Re: Successful return code on encoding error
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.patch 2016-03-31 18:25:56.277593065 +0200
@@ -271,7 +271,7 @@
+ }
+ if (!result)
+ {
-+ continue;
++ exit(2);
+ }
+
+if (number_of_input_urls != 1) {
--- 630-recode-output-to-locale-charset.patch.orig 2016-03-31
18:25:11.939150917 +0200
+++ 630-recode-output-to-locale-charset.patch 2016-03-31 18:26:08.926289750
+0200
@@ -75,7 +75,7 @@
+ result = recode(output_stream, output_encoding, "UTF-8");
+ if (!result)
+ {
-+ continue;
++ exit(2);
+ }
+ }
+ output_stream.clear();
--
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:
Successful return code on encoding error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/html2text/+bug/1564317/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564317] Re: Successful return code on encoding error
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 better solution would be to keep track of whether an error occurred in the loop and then change the final return value based on that. (Requiring changes to add a variable declaration, and on lines 482, 510, 555, 582 and 595) (Line numbers are from the patched Wily version) -- 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: Successful return code on encoding error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/html2text/+bug/1564317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564317] Re: Successful return code on encoding error
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: Successful return code on encoding error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/html2text/+bug/1564317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564317] [NEW] Successful return code on encoding error
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 invalid input sequence. Unconverted part of text follows. “Test”) 0 Expected output: (substitute 1 for any appropriate failure code) -- $ html2text test.html; echo $? Input recoding failed due to invalid input sequence. Unconverted part of text follows. “Test”) 1 This seem to have been introduced by 611-recognize-input-encoding.patch OS: Ubuntu 14.04 Package: html2text-1.3.2a-17 ** Affects: html2text (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Sample file" https://bugs.launchpad.net/bugs/1564317/+attachment/4618069/+files/test.html ** 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: - $ html2text test.html; echo $? Input recoding failed due to invalid input sequence. Unconverted part of text follows. “Test”) 0 Expected output: (substitute 1 for any appropriate failure code) -- $ html2text test.html; echo $? Input recoding failed due to invalid input sequence. Unconverted part of text follows. “Test”) 1 This seem to have been introduced by 611-recognize-input-encoding.patch + + OS: Ubuntu 14.04 + Package: html2text-1.3.2a-17 -- 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: Successful return code on encoding error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/html2text/+bug/1564317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1022287] Re: negative compression ratio if list a big gzip file
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 size... The extra fields go into the header though, instead of the trailer, which means that it can't be correctly populated for data piped through gzip, since the size is not known when the header is written... (This also seems to be the suggestion here: https://lists.gnu.org/archive/html/bug-gzip/2010-08/msg9.html ) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1022287 Title: negative compression ratio if list a big gzip file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1022287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
