Camera upside-down ASUS laptop

[glitchdot]

Hello, I am new user of MX Linux and I enjoy in it a lot. I run it on Asus laptop and have built-in camera. I encountered a small problem with the camera. When I run guvcview it works perfect, but in Firefox and Viber the camera image is upside-down.

I've done some research and found solution for Viber by changing Exec in /usr/share/applications/viber.desktop

Code: Select all

 Exec=sh -c 'export LIBV4LCONTROL_FLAGS=2 && LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libv4l/v4l1compat.so /opt/viber/Viber' 

Now camera output in viber is normal.

After that I tried similar solution for firefox /usr/share/applications/firefox.desktop

Code: Select all

Exec=sh -c 'export LIBV4LCONTROL_FLAGS=2 && LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libv4l/v4l1compat.so firefox' 

Code: Select all

Exec=sh -c 'export LIBV4LCONTROL_FLAGS=2 && LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libv4l/v4l1compat.so /opt/firefox/firefox' 

None of this changes solved the problem

Also tried Video4Linux Control Panel, but it seems every parameter changes work, except Horizontal and Vertical Flip.

Here is my sys. specifications:

Code: Select all

System:    Host: Filip Kernel: 4.19.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3 
           Distro: MX-18.1_x64 Continuum Feb 9  2019 
Machine:   Type: Laptop System: ASUSTeK product: K53SV v: 1.0 serial: <root required> 
           Mobo: ASUSTeK model: K53SV v: 1.0 serial: <root required> BIOS: American Megatrends v: K53SV.320 
           date: 11/11/2011 
Battery:   ID-1: BAT0 charge: 29.1 Wh condition: 33.7/47.5 Wh (71%) 
CPU:       Topology: Dual Core model: Intel Core i5-2410M bits: 64 type: MT MCP L2 cache: 3072 KiB 
           Speed: 798 MHz min/max: 800/2900 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 4: 798 
Graphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics driver: i915 v: kernel 
           Device-2: NVIDIA GF108M [GeForce GT 540M] driver: N/A 
           Display: x11 server: X.Org 1.19.2 driver: intel resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 18.2.6 
Audio:     Device-1: Intel 6 Series/C200 Series Family High Definition Audio driver: snd_hda_intel 
           Sound Server: ALSA v: k4.19.0-1-amd64 
Network:   Device-1: Qualcomm Atheros AR9285 Wireless Network Adapter driver: ath9k 
           IF: wlan0 state: up mac: 74:2f:68:3b:6d:87 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 
           IF: eth0 state: down mac: 14:da:e9:09:0f:73 
           Device-3: Atheros AR3011 Bluetooth type: USB driver: btusb 
Drives:    Local Storage: total: 465.76 GiB used: 154.50 GiB (33.2%) 
           ID-1: /dev/sda vendor: Seagate model: ST9500423AS size: 465.76 GiB 
Partition: ID-1: / size: 19.77 GiB used: 8.43 GiB (42.6%) fs: ext4 dev: /dev/sda2 
           ID-2: /home size: 191.47 GiB used: 33.07 GiB (17.3%) fs: ext4 dev: /dev/sda4 
           ID-3: swap-1 size: 8.11 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda1 
Sensors:   System Temperatures: cpu: 48.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Info:      Processes: 203 Uptime: 2h 36m Memory: 7.70 GiB used: 1.17 GiB (15.2%) Shell: bash inxi: 3.0.29 

[Stevo]

What about if you run those two commands in a terminal and then run firefox from it?

[glitchdot]

What about if you run those two commands in a terminal and then run firefox from it?

It's still upside-down.

[Stevo]

It appears that it's widespread for those type of laptops, and a bug has recently been filed against it for webrtc, which FF is using to acess the camera. If it gets fixed in webrtc, that should make its way into Firefox.

https://bugs.chromium.org/p/webrtc/issu ... l?id=10328

The bug should also appear in Chromium-based browsers--I don't think Pale Moon has the webrtc code in it, though...that's one of the things they remove.

[glitchdot]

I've tried various different browsers, commands doesn't work for Chromium and Firefox based browsers, and other browsers not based on these two (Palemoon, Netsurf, Slimjet) couldn't access camera at all.

Because it's not extremely big problem, I guess I will wait for webrtc bug fix.