Hi Jochen,
On Mon, Jun 30, 2025 at 08:13:31PM +0200, Jochen Sprickerhof wrote:
I tried to reproduce your bug but for me zbarcam works without
problem. Can you give some more information about the camera you used?
It's one of the built-in cameras on a TravelMate Spin B311R-31
$ sudo lshw
(snip)
*-usb:0
description: Video
product: 5MP World Facing
vendor: Chicony Electronics Co.,Ltd.
physical id: 2
bus info: usb@1:2
version: 62.27
serial: 0001
capabilities: usb-2.01
configuration: driver=uvcvideo maxpower=500mA
speed=480Mbit/s
*-usb:1
description: Video
product: HD User Facing
vendor: SunplusIT Inc
physical id: 7
bus info: usb@1:7
version: 0.04
capabilities: usb-2.01
configuration: driver=uvcvideo maxpower=500mA
speed=480Mbit/s
(snip)
Anything other information that may be relevant?
Also:
* Kim Alvefur <z...@zash.se> [2025-06-27 23:49]:
Output of `strace -o zbar.trace zbarcam` below.
This does not include threads, can you you run it again with -ff?
See attached.
* Kim Alvefur <z...@zash.se> [2025-06-28 00:18]:
Output of `zbarcam --verbose`:
_zbar_video_open: opened camera device /dev/video0 (fd=5)
_zbar_v4l2_probe: 5MP World Facing: 5MP World Fac on usb-0000:00:15.0-2 driver
uvcvideo (version 6.12.29)
_zbar_v4l2_probe: capabilities: CAPTURE READWRITE STREAMING
v4l2_reset_crop: crop bounds: 2560 x 1920 @ (0, 0)
I wonder if this due to the image size.
* Kim Alvefur <z...@zash.se> [2025-06-27 23:49]:
Package: zbar-tools
Version: 0.23.93-8
Severity: grave
Given that zbar-tools is more then zbarcam and that it works for me,
would you be ok with downgrading this to important?
Sure.
I imagine this could also be something in the kernel rather than in zbar-tools
but I haven't looked into that yet.
--
Cool Northern Regards,
Kim "Zash" Alvefur
