[Touch-packages] [Bug 1504127] Re: lsb_release throws exception if stdout is closed

2016-09-30 Thread Dimitri John Ledkov
Hello, there is no need to continuously to reproduce this, as it is a standard python interpret feature to catch SIGPIPE, raise BrokenPipeError on interpreter exit, and print a message about it to stderr. It is an error condition in python's opinion, and it does say so. In my opinion, this is

[Touch-packages] [Bug 1504127] Re: lsb_release throws exception if stdout is closed

2016-03-07 Thread bugproxy
--- Comment From santh...@in.ibm.com 2016-03-07 09:01 EDT--- Hi , The issue still exists in ubuntu16.04. o/p: uname -r o/p: 4.4.0-8-generic ( cat /etc/os-release /proc/version; lsb_release -is ) | grep -iq Ubuntu Exception ignored in: <_io.TextIOWrapper name='' mode='w'

[Touch-packages] [Bug 1504127] Re: lsb_release throws exception if stdout is closed

2016-01-12 Thread Steve Langasek
Demonstration of the bug which involves no bash: $ sh -c 'lsb_release -is | false' Exception ignored in: <_io.TextIOWrapper name='' mode='w' encoding='UTF-8'> BrokenPipeError: [Errno 32] Broken pipe $ -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1504127] Re: lsb_release throws exception if stdout is closed

2016-01-12 Thread Guo, Liang Chang
Steve, thank you very much for chasing the bug down to lsb_release. There is still no change that this exception occurs only on Ubuntu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lsb in Ubuntu.