Bug 2093731 - zbarimg does not read a Code 128 barcode
Summary: zbarimg does not read a Code 128 barcode
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: zbar
Version: 42
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-05 17:21 UTC by Cristian Ciupitu
Modified: 2025-06-04 10:39 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-05-16 07:39:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Code 128 barcode (268 bytes, image/png)
2022-06-05 17:21 UTC, Cristian Ciupitu
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github mchehab zbar issues 250 0 None open zbarimg does not read a Code 128 barcode 2023-04-24 16:09:39 UTC

Description Cristian Ciupitu 2022-06-05 17:21:40 UTC
Created attachment 1886898 [details]
Code 128 barcode

Description of problem:
zbarimg does not read a Code 128 barcode

Version-Release number of selected component (if applicable):
zbar-0.23.90-1.fc36.x86_64

How reproducible:
Every time

Steps to Reproduce:
1. zbarimg barcode.png 

Actual results:
scanned 0 barcode symbols from 1 images in 0 seconds


WARNING: barcode data was not detected in some image(s)
Things to check:
  - is the barcode type supported? Currently supported symbologies are:
	. EAN/UPC (EAN-13, EAN-8, EAN-2, EAN-5, UPC-A, UPC-E, ISBN-10, ISBN-13)
	. DataBar, DataBar Expanded
	. Code 128
	. Code 93
	. Code 39
	. Codabar
	. Interleaved 2 of 5
	. QR code
	. SQ code
	. PDF 417
  - is the barcode large enough in the image?
  - is the barcode mostly in focus?
  - is there sufficient contrast/illumination?
  - If the symbol is split in several barcodes, are they combined in one image?
  - Did you enable the barcode type?
    some EAN/UPC codes are disabled by default. To enable all, use:
    $ zbarimg -S*.enable <files>
    Please also notice that some variants take precedence over others.
    Due to that, if you want, for example, ISBN-10, you should do:
    $ zbarimg -Sisbn10.enable <files>


Expected results:
(Code 128) 755897201062022179.73

Additional info:

Comment 1 Gwyn Ciesla 2022-06-07 14:48:51 UTC
This is the version in updates-testing, yes? Can you provide a file that reproduces this?

Comment 2 Cristian Ciupitu 2022-06-08 09:39:34 UTC
Didn't I provide the version and also an attachment with the barcode?

Comment 3 David Auer 2023-04-23 15:28:46 UTC
I can confirm this bug, even after adding a white border around the code and with "-S*.enable" it is not recognized.
Maybe it's worth a short reporting it upstream: https://github.com/mchehab/zbar/issues

Name         : zbar
Version      : 0.23.90
Release      : 7.fc38

Comment 4 Aoife Moloney 2024-05-07 15:46:18 UTC
This message is a reminder that Fedora Linux 38 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '38'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 38 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 5 Aoife Moloney 2024-05-21 14:13:59 UTC
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 6 Cristian Ciupitu 2024-05-25 14:34:35 UTC
Still not working with zbar-0.23.93-3.fc40.x86_64

Comment 7 Aoife Moloney 2025-04-25 10:02:56 UTC
This message is a reminder that Fedora Linux 40 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '40'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 40 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 8 Aoife Moloney 2025-05-16 07:39:57 UTC
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13.

Fedora Linux 40 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 9 Cristian Ciupitu 2025-06-04 10:39:31 UTC
It's still not working with zbar-0.23.93-6.fc42.x86_64


Note You need to log in before you can comment on or make changes to this bug.