[Bug 990371] YaST SCR.Execute(path(".target.bash_output"), "COMMAND") fills up disk if COMMAND outputs endlessly on stdout or stderr
http://bugzilla.suse.com/show_bug.cgi?id=990371 http://bugzilla.suse.com/show_bug.cgi?id=990371#c4 --- Comment #4 from Carlos Lange <carlosflange@gmail.com> --- (In reply to Johannes Meixner from comment #3) Thank you for your detailed explanation, Johannes. It is quite clear to me now that this is an HPLIP only problem. I tried to reproduce the problem on my other machine running hp-setup version 3.15.11 by removing the PPDs. hp-setup first tried to use standard Ghostscript PPDs, but after removing those, the GUI stops with an error in the graphical window itself and no output in stdout. It is only in the newest version (3.16.5) that hp-setup makes 2 mistakes: 1- it offers the user option to run hp-plugin, but it does so in the CLI only, instead of the GUI 2- it repeats the question incessantly when in script mode (not in actual CLI mode), filling up the disk. I will submit the bug to http://hplipopensource.com/hplip-web/support.html I leave it to the YaST maintainer to decide about the point three in Johannes' list, since it is much broader than this HPLIP issue. If preferred, I can open a new bug report. I definitely think disk fill-up should be prevented, if possible, because the whole system starts misbehaving in strange ways and it takes a while until one can find the cause before the system freezes. Feel free to close this one. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com