[Desktop-packages] [Bug 378783] Re: xdg-open *.desktop opens text editor

2018-07-20 Thread Gert van den Berg
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 Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/378783

Title:
  xdg-open *.desktop opens text editor

Status in gvfs:
  New
Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: xdg-utils

  In order to reproduce it execute "xdg-open *.desktop" (choose any
  .desktop file, e.g. one from /usr/share/applications). Actually your
  favorite text editor will open the file. Expected result: It'll be
  executed.

  Because of this bug, desktop entries with the new "#!/usr/bin/env xdg-
  open" shebang feature were opened in the text editor when executed
  from command line.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/378783/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 378783] Re: xdg-open *.desktop opens text editor

2018-07-20 Thread Gert van den Berg
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 Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/378783

Title:
  xdg-open *.desktop opens text editor

Status in gvfs:
  New
Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: xdg-utils

  In order to reproduce it execute "xdg-open *.desktop" (choose any
  .desktop file, e.g. one from /usr/share/applications). Actually your
  favorite text editor will open the file. Expected result: It'll be
  executed.

  Because of this bug, desktop entries with the new "#!/usr/bin/env xdg-
  open" shebang feature were opened in the text editor when executed
  from command line.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/378783/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1564317] Re: Successful return code on encoding error

2017-03-16 Thread Gert van den Berg
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 Desktop
Packages, which is subscribed to html2text in Ubuntu.
https://bugs.launchpad.net/bugs/1564317

Title:
  Successful return code on encoding error

Status in One Hundred Papercuts:
  New
Status in html2text package in Ubuntu:
  Confirmed

Bug description:
  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 / Ubuntu 16.04
  Package: html2text-1.3.2a-17 / html2text-1.3.2a-18

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1564317/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1564317] Re: Successful return code on encoding error

2017-03-10 Thread Gert van den Berg
@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 Desktop
Packages, which is subscribed to html2text in Ubuntu.
https://bugs.launchpad.net/bugs/1564317

Title:
  Successful return code on encoding error

Status in One Hundred Papercuts:
  New
Status in html2text package in Ubuntu:
  Confirmed

Bug description:
  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 / Ubuntu 16.04
  Package: html2text-1.3.2a-17 / html2text-1.3.2a-18

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1564317/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1564317] Re: Successful return code on encoding error

2017-03-02 Thread Gert van den Berg
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 Desktop
Packages, which is subscribed to html2text in Ubuntu.
https://bugs.launchpad.net/bugs/1564317

Title:
  Successful return code on encoding error

Status in One Hundred Papercuts:
  New
Status in html2text package in Ubuntu:
  New

Bug description:
  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 / Ubuntu 16.04
  Package: html2text-1.3.2a-17 / html2text-1.3.2a-18

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1564317/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1564317] Re: Successful return code on encoding error

2016-04-04 Thread Gert van den Berg
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 Desktop
Packages, which is subscribed to html2text in Ubuntu.
https://bugs.launchpad.net/bugs/1564317

Title:
  Successful return code on encoding error

Status in One Hundred Papercuts:
  New
Status in html2text package in Ubuntu:
  New

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1564317/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1564317] Re: Successful return code on encoding error

2016-03-31 Thread Gert van den Berg
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 Desktop
Packages, which is subscribed to html2text in Ubuntu.
https://bugs.launchpad.net/bugs/1564317

Title:
  Successful return code on encoding error

Status in html2text package in Ubuntu:
  New

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/html2text/+bug/1564317/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1564317] Re: Successful return code on encoding error

2016-03-31 Thread Gert van den Berg
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 Desktop
Packages, which is subscribed to html2text in Ubuntu.
https://bugs.launchpad.net/bugs/1564317

Title:
  Successful return code on encoding error

Status in html2text package in Ubuntu:
  New

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/html2text/+bug/1564317/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1564317] Re: Successful return code on encoding error

2016-03-31 Thread Gert van den Berg
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 Desktop
Packages, which is subscribed to html2text in Ubuntu.
https://bugs.launchpad.net/bugs/1564317

Title:
  Successful return code on encoding error

Status in html2text package in Ubuntu:
  New

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/html2text/+bug/1564317/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1564317] Re: Successful return code on encoding error

2016-03-31 Thread Gert van den Berg
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 Desktop
Packages, which is subscribed to html2text in Ubuntu.
https://bugs.launchpad.net/bugs/1564317

Title:
  Successful return code on encoding error

Status in html2text package in Ubuntu:
  New

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/html2text/+bug/1564317/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1564317] [NEW] Successful return code on encoding error

2016-03-31 Thread Gert van den Berg
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 Desktop
Packages, which is subscribed to html2text in Ubuntu.
https://bugs.launchpad.net/bugs/1564317

Title:
  Successful return code on encoding error

Status in html2text package in Ubuntu:
  New

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/html2text/+bug/1564317/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp