[Bug 753723] New: Piping into grep fails with EPIPE
https://bugzilla.novell.com/show_bug.cgi?id=753723 https://bugzilla.novell.com/show_bug.cgi?id=753723#c0 Summary: Piping into grep fails with EPIPE Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: ManuelStol@operamail.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- Created an attachment (id=482857) --> (http://bugzilla.novell.com/attachment.cgi?id=482857) strace of (echo "foobar" | grep "foo") User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.34 (KHTML, like Gecko) konqueror/4.8.1 Safari/534.34 Piping stdout into grep fails with an EPIPE. Reproducible: Always Steps to Reproduce: 1. Open a terminal (xterm, konsole) as a normal user. 2. type: echo "foobar" | grep "foo" Actual Results: No output to stdout due to an EPIPE error. Expected Results: The lines that match the grep pattern. - This doesn't happen when opening a terminal as root nor when switching to root with 'su -'. - Neither grep nor egrep work. - When replacing grep with sed, piping works as expected. - Tried it with konsole, xterm and linux 32-bit terminal. - I've been updating my system since openSUSE 11.4. - I've re-intalled the grep rpm. - YaST does not start on a 64bit system, as grep is used in /usr/lib/YaST2/bin/yast2-funcs Workaround: Start YaST with '--qt' or '--gtk'. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=753723 https://bugzilla.novell.com/show_bug.cgi?id=753723#c1 --- Comment #1 from Manuel Stol <ManuelStol@operamail.com> 2012-03-23 03:29:03 UTC --- Created an attachment (id=482858) --> (http://bugzilla.novell.com/attachment.cgi?id=482858) strace of (echo "foobar" | sed "s/foo/XXX/") -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=753723 https://bugzilla.novell.com/show_bug.cgi?id=753723#c2 --- Comment #2 from Manuel Stol <ManuelStol@operamail.com> 2012-03-25 10:23:29 UTC --- - I'm using 'secure' permissions. PERMISSION_SECURITY="secure local" in '/etc/sysconfig/security' As POLKIT_DEFAULT_PRIVS is unset, PolicyKit uses 'restrictive' privilege settings. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=753723 https://bugzilla.novell.com/show_bug.cgi?id=753723#c3 --- Comment #3 from Manuel Stol <ManuelStol@operamail.com> 2012-04-10 13:02:47 UTC --- Changing the file permissions or PolicyKit privilege settings did not help. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=753723 https://bugzilla.novell.com/show_bug.cgi?id=753723#c4 Manuel Stol <ManuelStol@operamail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Critical |Major --- Comment #4 from Manuel Stol <ManuelStol@operamail.com> 2012-04-10 13:06:46 UTC --- When I add a new user, this new user does not have the 'piping to grep' problem. So my user settings must be borked. Can anyone tell me how to debug this? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=753723 https://bugzilla.novell.com/show_bug.cgi?id=753723#c5 Manuel Stol <ManuelStol@operamail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #5 from Manuel Stol <ManuelStol@operamail.com> 2012-04-10 18:55:08 UTC --- Resolved. For over a decade I used the following in my profile: " # Do not grep devices! The keyboard becomes unusable when grepping on it. export GREP_OPTIONS="--devices=skip" " It looks that in the latest Linux kernel piping is/uses a FIFO device. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com