[Bug 1535458] Re: [15.10 REGRESSION] Randomly wrongly detects files as binary

teo1978 teo8976 at gmail.com
Tue Mar 8 22:38:55 UTC 2016


*** This bug is a duplicate of bug 1547466 ***
    https://bugs.launchpad.net/bugs/1547466

Are you sure this is the same as 1547466 ??

1547466 describes mode switching to binary in the middle of the file.

What I observe  is that some text files are treated as binary. I never
get an output like the one described in 1547466, where you get some
matches as expected and then the output gets interrupted in the middle
of the file with the phrase "binary file xxx matches". I always get
either the expected text-mode output for the whole file or only the
"binary match" phrase. The same files always produce the same output,
consistently.

To me this looks a lot like https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=799956 and not much like issue 1547466.

Every single file that exhibits the issue that I have examined is ISO-8859-15. I have only looked at a few randomly. And a few that don't exhibit the issue which I have looked at randomly are all UTF-8. (to look at it I use Gedit and do a Save As; the encoding the file is in is, or is supposed to be, selected by default).
However, I have created an ISO-8859-15 file from scratch from Gedit and it does not reproduce the issue.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grep in Ubuntu.
https://bugs.launchpad.net/bugs/1535458

Title:
  [15.10 REGRESSION] Randomly wrongly detects files as binary

Status in grep package in Ubuntu:
  Confirmed

Bug description:
  I have a folder with a bunch of subfolder and several hundred or
  thousands files, most of them PHP files (obviously text).

  I often use grep recursively, like this:
    $ grep -R somepattern *

  Since the upgrade from 15.04 to 15.10, it often happens that a lot of text files are wrongly treated as binary. That means that, when a match is found, instead of getting the normal output which would show the file name and the matching line (with the matching substring highlighted), I get the bogus message:
    binary file whatever.php matches

  Just to be clear: in one invocation of grep -R, I get mixed output
  with a lot of matches shown in the expected way and quit e a few
  matches shown in the wrong way, even though ALL matching files are
  text files.

  
  This worked as expected before the upgrade from 15.04 and 15.10.

  
  This is a HUGE issue that makes it impossible to do everyday developing work.

  
  Until you fix it, please f***ing roll back grep to the previous version, because this sh** is unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: grep 2.21-2
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 18 22:43:51 2016
  InstallationDate: Installed on 2013-10-11 (829 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: grep
  UpgradeStatus: Upgraded to wily on 2016-01-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1535458/+subscriptions



More information about the foundations-bugs mailing list