http://bugzilla.suse.com/show_bug.cgi?id=943757 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- Found By|--- |Development -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=943757 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|yast storage with ncurses |yast storage with ncurses |does not due to nokogiri |does not start due to |error message |nokogiri error message -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=943757 http://bugzilla.suse.com/show_bug.cgi?id=943757#c3 Martin Vidner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #3 from Martin Vidner --- To reproduce: # /usr/lib/YaST2/bin/y2base ./hello.rb ncurses # https://bugzilla.suse.com/show_bug.cgi?id=943757 require "yast" include Yast::UIShortcuts $stderr.puts "Hello, stderr! 1" # This succeeds module Yast import "UI" UI.OpenDialog(PushButton("Hello, World!")) $stderr.puts "Hello, stderr! 2" # Bad file descriptor @ io_write UI.UserInput UI.CloseDialog end I thought that we did redirect to the log, but it turns out that since 2008 ncurses redirects stdout and stderr to /dev/null, even with some suspicious flags (defaulting to O_RDONLY) which may never have worked: https://github.com/libyui/libyui-ncurses/blob/8f861f5ccb77a72fdcc17e909f2811... open( log.c_str(), O_APPEND | O_CREAT, 0666 ); -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=943757 http://bugzilla.suse.com/show_bug.cgi?id=943757#c5 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Assignee|yast2-maintainers@suse.de |yast-internal@suse.de --- Comment #5 from Lukas Ocilka --- Looks like it was done bu this commit, but that mostly fixes just the formatting https://github.com/libyui/libyui-ncurses/commit/9a033491a3126270b310e9a0106c... Katarina has moved this to a separate function in 2007 https://github.com/libyui/libyui-ncurses/blob/master/ChangeLog#L854 And this was the commit https://github.com/libyui/libyui-ncurses/commit/dd18ea2a3fca3864d43aff710a6d... --> P2 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=943757 http://bugzilla.suse.com/show_bug.cgi?id=943757#c6 Ancor Gonzalez Sosa changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ancor@suse.com --- Comment #6 from Ancor Gonzalez Sosa --- Talking about ruby-based solutions, this works. But it's more an experiment than a reliable fix. I would rather try to replace $stderr by a proper IO object, instead of hijacking #puts and #print (since there are also #printf, #putc, #write...) require "yast" include Yast::UIShortcuts $stderr.puts "Hello, stderr! 1" $stderr.define_singleton_method(:puts) do |*args| if args.empty? Yast.y2error($/) else Yast.y2error(args.join($/)) end end $stderr.define_singleton_method(:print) do |*args| if args.empty? Yast.y2error($_) else Yast.y2error(args.map(&:to_s).join($,) + $\.to_s) end end module Yast import "UI" UI.OpenDialog(PushButton("Hello, World!")) # Al this messages works as expected (logging to YaST logs) $stderr.puts "Hello, stderr! 2" $stderr.puts "Halo", "stderr!", "2" $stderr.print "Hola, ! 2" $stderr.print "Ahoj", "stderr!", "2" UI.UserInput UI.CloseDialog end -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=943757 http://bugzilla.suse.com/show_bug.cgi?id=943757#c8 --- Comment #8 from Stefan Hundhammer --- It's been a long time... ;-) I faintly remember that redirecting all stderr output to the y2log tends to mess up the y2log badly as there are different levels of buffering all over the place. libyui has its own thread-safe logger with its own logging buffer. If some other output is writing to the same file handle, but bypassing that thread-safe log buffer, the output will become mixed, disregarding things like output lines (and of course the y2log line header with the timestamp, PID, source file, function, source line number). IIRC we used that for a short while and then became frustrated quickly because the logs were messed up in the most critical moments. There is no easy way around this; IIRC I tried to come up with a strategy to route that output through the thread-safe libyui logger, but if a process simply writes to a file handle, there is no reliable way to do this. Another approach might be to simply open yet another file dedicated to stderr output. Of course that implies taking care of log rotation etc.; that's probably the reason why back then we had decided to redirect it to /dev/null. That output just wasn't that important. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=943757 Stefan Hundhammer changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(shundhammer@suse. | |com) | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=943757 http://bugzilla.suse.com/show_bug.cgi?id=943757#c11 Martin Vidner changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(mvidner@suse.com) | --- Comment #11 from Martin Vidner --- I have checked RedirectToLog, adding O_WRONLY to the flags works. I think that it is enough to continue discarding the output. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=943757 http://bugzilla.suse.com/show_bug.cgi?id=943757#c13 Martin Vidner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #13 from Martin Vidner --- The tests have been merged, the bug is thus resolved. Thanks everyone! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=943757 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| maint:planned:update | -- You are receiving this mail because: You are on the CC list for the bug.