Bug 830439 - image upside down, thinkpad x220 table
image upside down, thinkpad x220 table
Product: Fedora
Classification: Fedora
Component: v4l-utils (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Hans de Goede
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-06-09 11:22 EDT by Florian Ludwig
Modified: 2013-07-31 20:32 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-07-31 20:32:15 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
lsusb -v (67.80 KB, text/plain)
2012-06-09 11:22 EDT, Florian Ludwig
no flags Details

  None (edit)
Description Florian Ludwig 2012-06-09 11:22:23 EDT
Created attachment 590619 [details]
lsusb -v

Description of problem:
The image of the webcam is upside down

Version-Release number of selected component (if applicable):
libv4l.x86_64                       0.8.8-1.fc17

How reproducible:
1. buy thinkpad x220 tablet
2. install fedora
3. start cheese
Actual results:
Image is upside down

Expected results:
Image not upside down

Additional info:
It seems libv4 got some quirk that thinks the webcam is installed upside down and so rotates the image. But - at least in my model - that assumption is wrong and the image ends up upside down.


I think it worked before some upgrade.

lsusb -v is attached. My guess is that the webcam is "04f2:b217"
Comment 1 Hans de Goede 2012-06-11 16:01:30 EDT
Hi Florian,

I'm going to send you a private mail with the email address of the current upside-down quirk list maintainer, the problem with the x220 is that there are some models which need us to flip the image in software, and some which don't (like yours). We've been unable to exactly figure out how to determine what sort of model we're dealing with.

Once you've my mail, please send a mail to the upstream maintainer explaining your problem, he will likely reply with a request for a bunch of info. You can speedup the process by doing:

lsusb -v > lsusb.log
sudo dmidecude > dmi.log

And sending the 2 log files along with your first mail. Please CC me on the mail.


Comment 2 Gregor Jasny 2012-06-11 16:19:18 EDT
Hello Florian,

After you habe generated the DMI and USB data (there's a typo, it should read dmidecode) could you try to upgrade your BIOS (and Firmware) with the latest version provided by Lenovo?

Comment 3 Fedora End Of Life 2013-07-03 18:34:15 EDT
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 4 Fedora End Of Life 2013-07-31 20:32:19 EDT
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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 please feel free to reopen this bug against that version.

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

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