#568225 apt-listchanges: crashes after sensible-browser exits with failure

Package:
apt-listchanges
Source:
apt-listchanges
Submitter:
Date:
2023-09-25 14:09:07 UTC
Severity:
normal
#568225#5
Date:
2010-02-03 09:33:32 UTC
From:
To:
Luen muutoslokeja... Valmis
terminate called after throwing an instance of 'std::length_error'
  what():  basic_string::assign
Traceback (most recent call last):
  File "/usr/bin/apt-listchanges", line 229, in <module>
    main()
  File "/usr/bin/apt-listchanges", line 193, in main
    frontend.display_output(changes)
  File "/usr/share/apt-listchanges/apt_listchanges.py", line 240, in display_output
    raise OSError('Subprocess ' + shellcommand + ' exited with status ' + str(status))
OSError: Subprocess sensible-browser /tmp/tmpusvJvH.html exited with status -6
Puretaan malleja paketeteista: 100 %


I have no idea why the browser failed, but apt-listchanges should not crash
as a result.
#568225#10
Date:
2011-12-19 06:22:08 UTC
From:
To:
    Trying to use iceweasel as browser failed today, worked yesterday.
Chromium can't be used because it won't allow itself to be run as root.

Aborted
Traceback (most recent call last):
  File "/usr/bin/apt-listchanges", line 237, in <module>
    main()
  File "/usr/bin/apt-listchanges", line 201, in main
    frontend.display_output(changes)
  File "/usr/share/apt-listchanges/apt_listchanges.py", line 240, in
display_output
    raise OSError('Subprocess ' + shellcommand + ' exited with status '
+ str(status))
OSError: Subprocess iceweasel /tmp/tmpqqr8Mk.html exited with status 134
#568225#17
Date:
2023-09-25 13:53:54 UTC
From:
To:
Hmm.

A program should stop with an error when it encounters an error
condition  (a) which is unexpected, (b) it doesn't know how to recover
from, and (c) action by the user is probably necessary to fully resolve
(in fact, (c) is a bonus; (a) and (b) are probably sufficient to justify
stopping). So I don't think apt-listchanges is wrong to exit here.
Perhaps, though, it should just print an error message and exit with a
non-zero exit status rather than generating a Traceback.

What do you think?
#568225#20
Date:
2023-09-25 14:07:12 UTC
From:
To:
Just realized replies aren't sent to submitters by default. Resending.

On Mon, 25 Sep 2023 09:53:54 -0400 Jonathan Kamens <jik@kamens.us> wrote:

 > Hmm.
 >
 > A program should stop with an error when it encounters an error
 > condition  (a) which is unexpected, (b) it doesn't know how to recover
 > from, and (c) action by the user is probably necessary to fully resolve
 > (in fact, (c) is a bonus; (a) and (b) are probably sufficient to justify
 > stopping). So I don't think apt-listchanges is wrong to exit here.
 > Perhaps, though, it should just print an error message and exit with a
 > non-zero exit status rather than generating a Traceback.
 >
 > What do you think?
 >