Description of problem: I had a compaq presario c700 with broken display connected trough vga cable to a lcd TV. I try to record my desktop with simplescreenrecorder, qt4-recordmydesktop and ffmpeg with Strange results, i only can think i something in Plasma as a test with ffmpeg in icewm works fine inxi -F System: Host: cefiro Kernel: 5.10.60-desktop-2.mga8 i686 bits: 32 Desktop: KDE Plasma 5.20.4 Distro: Mageia 8 mga8 Machine: Type: Laptop System: Hewlett-Packard product: Compaq Presario C700 Notebook PC v: F.34 serial: <superuser required> Mobo: Hewlett-Packard model: 30D9 v: 83.21 serial: <superuser required> BIOS: Hewlett-Packard v: F.34 date: 09/25/2008 Battery: ID-1: BAT0 charge: 4.8 Wh condition: 4.8/4.8 Wh (100%) CPU: Info: Dual Core model: Intel Pentium Dual T2370 bits: 64 type: MCP L2 cache: 1024 KiB Speed: 798 MHz min/max: 800/1733 MHz Core speeds (MHz): 1: 798 2: 798 Graphics: Device-1: Intel Mobile GM965/GL960 Integrated Graphics driver: i915 v: kernel Device-2: Chicony integrated USB webcam type: USB driver: uvcvideo Display: x11 server: Mageia X.org 1.20.12 driver: intel,v4l resolution: 1360x768~60Hz OpenGL: renderer: Mesa DRI Intel 965GM (CL) v: 2.1 Mesa 21.1.7 Audio: Device-1: Intel 82801H HD Audio driver: snd_hda_intel Sound Server: ALSA v: k5.10.60-desktop-2.mga8 Network: Device-1: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter driver: ath5k IF: wlp1s0 state: up mac: 00:23:4e:4f:6d:6a Device-2: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter driver: 8139too IF: enp2s1 state: unknown speed: 100 Mbps duplex: full mac: 00:1e:ec:eb:b4:39 Drives: Local Storage: total: 465.76 GiB used: 28.45 GiB (6.1%) ID-1: /dev/sda vendor: Toshiba model: MK5076GSX size: 465.76 GiB Partition: ID-1: / size: 48.96 GiB used: 8.78 GiB (17.9%) fs: ext4 dev: /dev/sda1 ID-2: /home size: 411.55 GiB used: 19.64 GiB (4.8%) fs: xfs dev: /dev/sda3 Swap: ID-1: swap-1 type: partition size: 4 GiB used: 25.4 MiB (0.6%) dev: /dev/sda5 Sensors: System Temperatures: cpu: 55.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 177 Uptime: 34m Memory: 1.96 GiB used: 1.29 GiB (65.7%) Shell: Bash inxi: 3.2.01
Command used ffmpeg -f x11grab -r 30 -s 1360x768 -i :0.0 video-name.avi https://sendvid.com/yrp482v6 https://sendvid.com/psb7axvs The videos are in processing at the moment of write this
Instead of specifying the display as :0.0, try ... ffmpeg -f x11grab -r 30 -s 1360x768 -i $DISPLAY video-name.avi
CC: (none) => davidwhodgins
(In reply to Dave Hodgins from comment #2) > Instead of specifying the display as :0.0, try ... > ffmpeg -f x11grab -r 30 -s 1360x768 -i $DISPLAY video-name.avi The result is the same as https://sendvid.com/psb7axvs (once you can see it) I perform exactly the same actions as in https://sendvid.com/yrp482v6 (icewn video), but for strange reason is like i don't open firefox and only record the window of konsole were i run the command. I got even weirdest result in tools like kazaam, as it produce a video like i open konsole and run the ffmpeg command but i did't
I found a post in stackoverflow (https://stackoverflow.com/a/44921300) that say that x11grab should be replaced with xcbgrab but maybe our ffmpeg not have that support fmpeg version 4.3.2 Copyright (c) 2000-2021 the FFmpeg developers built with gcc 10 (Mageia 10.3.0-1.mga8) configuration: --prefix=/usr --enable-shared --enable-pic --libdir=/usr/lib --shlibdir=/usr/lib --incdir=/usr/include --disable-stripping --enable-postproc --enable-gpl --enable-pthreads --enable-libtheora --enable-libvorbis --disable-encoder=vorbis --enable-libvpx --enable-runtime-cpudetect --enable-libaom --enable-libdc1394 --enable-librtmp --enable-libspeex --enable-libfreetype --enable-libgsm --enable-libcelt --enable-libopus --disable-libopencv --enable-libopenjpeg --enable-libvidstab --enable-libtwolame --enable-libxavs --enable-frei0r --enable-libmodplug --enable-libass --enable-gnutls --enable-libcdio --enable-libpulse --enable-libv4l2 --enable-avresample --enable-opencl --enable-libmp3lame --enable-sndio --enable-libdav1d --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-version3 --enable-libx264 --enable-libx265 --enable-libvo-amrwbenc --enable-libxvid
(In reply to katnatek from comment #4) > I found a post in stackoverflow (https://stackoverflow.com/a/44921300) that > say that x11grab should be replaced with xcbgrab but maybe our ffmpeg not > have that support Maybe bad info in ffmpeg from https://johnvansickle.com/ffmpeg the option still is x11grab
(In reply to katnatek from comment #3) > (In reply to Dave Hodgins from comment #2) > > Instead of specifying the display as :0.0, try ... > > ffmpeg -f x11grab -r 30 -s 1360x768 -i $DISPLAY video-name.avi > > The result is the same as https://sendvid.com/psb7axvs (once you can see it) > Now you can see it
Assigning to the maintainer of ffmpeg
Assignee: bugsquad => smelror
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=25671
(In reply to Dave Hodgins from comment #7) > Assigning to the maintainer of ffmpeg Recent search by my card give me a solution in https://bugs.mageia.org/show_bug.cgi?id=16986#c14 (i forgot that, this is other lap) I apply the change to xorg.conf and i could record my desktop with simplescreenrecorder (later i will test with ffmpeg) so the intel driver is apparently the guilty
Source RPM: (none) => x11-driver-video-intel-2.99.917-63.mga8.src.rpmSee Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=16986
This change also works Section "Device" Identifier "device1" VendorName "Intel Corporation" BoardName "Intel 810 and later" Driver "intel" Option "DPMS" Option "TearFree" "true" Option "AccelMethod" "uxa" Option "Backlight" "intel_backlight" EndSection
(In reply to katnatek from comment #9) > This change also works > > Section "Device" > Identifier "device1" > VendorName "Intel Corporation" > BoardName "Intel 810 and later" > Driver "intel" > Option "DPMS" > Option "TearFree" "true" > Option "AccelMethod" "uxa" > Option "Backlight" "intel_backlight" > EndSection But it stuck on suspend and resume so i only recommend https://bugs.mageia.org/show_bug.cgi?id=16986#c14
For newcomers to this bug, also see some mitigation at https://wiki.mageia.org/en/Mageia_8_Errata#KDE_Plasma
Keywords: (none) => IN_ERRATA8CC: (none) => fri
Errata entry rephrased and now in separate header: https://wiki.mageia.org/en/Mageia_8_Errata#Recording_your_desktop
Is this also valid in MGA9 or why did this land in MGA9 Errata?
(In reply to sturmvogel from comment #13) > Is this also valid in MGA9 or why did this land in MGA9 Errata? I'll test, is in my TODO, please add to errata, i will edit ore remove when i done the test
(In reply to sturmvogel from comment #13) > Is this also valid in MGA9 or why did this land in MGA9 Errata? The bad news: Not only still valid, the workaround of https://bugs.mageia.org/show_bug.cgi?id=16986#c14, not works I will do more test, i just test simplescreenrecorder
Looks like the Compositor is the guilty this time, i disable the compositor and close the session and open again and the desktop can be recorded, i do more check with other xorg configurations
Additional note for the records: When switching from MGA6 to MGA7 the same occured when using XFCE4. When switching off composite, the screen could be recorded. With composite active, only the desktop was recorded, but no window above it. Selecting a certain window in simplescreenrecorder instead of the whole desktop made this window be recorded, but no dropdown window was recorded. When several recordings were done during the same session, every further recording always showed the same scene as during the first recording. Maybe the buffer could not be re-written. Looks like every window manager coming along with composite / transparency effects does not work properly due to this error
CC: (none) => ubuntu
(In reply to Markus Robert Keßler from comment #17) The "funny" for me is that i get the lottery with the laptop hardware, i make a test in my desktop system and screen recording works well even with the compositor enabled XD
Updated Mageia 9 Errata
Source RPM: x11-driver-video-intel-2.99.917-63.mga8.src.rpm => x11-driver-video-intel,plasmaKeywords: (none) => IN_ERRATA9
We stopped supporting Mageia 8 almost 8 months ago https://blog.mageia.org/en/2023/12/30/mageia-8-end-of-life/ That means we also stopped fixing Mageia 8 bugs and that this bug report needs to be closed, regardless of whether it was fixed for Mageia 8 or not. If this particular bug did not get fixed for Mageia 8, then we do regret that. If this issue is still present in Mageia 9 or cauldron, then please reopen this report, write a comment and adjust the "Version:" field. If you are not yet a member of one or our teams, then please consider becoming one. https://wiki.mageia.org/en/Contributing Mageia is a community project, meaning that we, the users, make Mageia together. The more active contributors we have, the more bug reports will get fixed. Besides, being active in a team can be very rewarding. It was and is certainly rewarding to me :-D
Status: NEW => RESOLVEDResolution: (none) => OLD
Sadly still valid but look with other cause and workaround and that is why is in Erratas for 9
Version: 8 => 9Resolution: OLD => (none)Status: RESOLVED => REOPENED