@Till, before installing the "alien", "build-essential" and "lsb" packages, I reverted the VM to a previous snapshot (which is "clean"). I did this before every attempt at installing the printer.
In the attempt where I installed these packages manually (and their dependencies), system-config-printer succeeded in installing the driver. In the other attempts it hanged.
There was also one attempt where I installed "alien" and "build-essential", but not "lsb", and it didn't work.
Was the VM that you used for testing in a "after installation" state?
If not, could you, or anybody, else test this fix right after installing Ubuntu in a VM or an actual machine?
This way we would know if this is really an issue or if it's just a problem with VirtualBox (which it may be).
(Sorry, I can't test this in a real computer because I have only one working computer right now, and I don't want to reinstall the system).
Relative to THIS bug ("system-config-printer crashes..."), it's fixed! It doesn't crash anymore with the fix.
The issue I reported would be a new bug (if confirmed).
@Till, before installing the "alien", "build-essential" and "lsb" packages, I reverted the VM to a previous snapshot (which is "clean"). I did this before every attempt at installing the printer. config- printer succeeded in installing the driver. In the other attempts it hanged.
In the attempt where I installed these packages manually (and their dependencies), system-
There was also one attempt where I installed "alien" and "build-essential", but not "lsb", and it didn't work.
Was the VM that you used for testing in a "after installation" state?
If not, could you, or anybody, else test this fix right after installing Ubuntu in a VM or an actual machine?
This way we would know if this is really an issue or if it's just a problem with VirtualBox (which it may be).
(Sorry, I can't test this in a real computer because I have only one working computer right now, and I don't want to reinstall the system).
Relative to THIS bug ("system- config- printer crashes..."), it's fixed! It doesn't crash anymore with the fix.
The issue I reported would be a new bug (if confirmed).