This is an on/off bug with cheese.
I seem to have the same issue … but was able to make it work defining the device path:
cheese -d /dev/video1
(your path may be different)
It is on uefi
Can you post your mkinitcpio.conf, grub configuration, and Plymouth service status?
“mkinitcpio.conf”
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES=(piix ide_disk reiserfs)
MODULES=""
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS=(base)
#
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS=(base udev autodetect block filesystems)
#
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS=(base udev block filesystems)
#
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS=(base udev block mdadm encrypt filesystems)
#
## This setup loads an lvm2 volume group on a usb device.
# HOOKS=(base udev block lvm2 filesystems)
#
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block keyboard keymap plymouth resume filesystems"
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"
#COMPRESSION="zstd"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()
“grub”
GRUB_DEFAULT=saved
GRUB_TIMEOUT=5
GRUB_TIMEOUT_STYLE=hidden
GRUB_DISTRIBUTOR="Manjaro"
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash apparmor=1 security=apparmor resume=UUID=ccd7f4f6-7963-482a-a149-318725528154 udev.log_priority=3"
GRUB_CMDLINE_LINUX=""
# If you want to enable the save default function, uncomment the following
# line, and set GRUB_DEFAULT to saved.
GRUB_SAVEDEFAULT=true
# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
# Uncomment to enable booting from LUKS encrypted devices
#GRUB_ENABLE_CRYPTODISK=y
# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console
# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command 'videoinfo'
GRUB_GFXMODE=auto
# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep
# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true
# Uncomment and set to the desired menu colors. Used by normal and wallpaper
# modes only. Entries specified as foreground/background.
GRUB_COLOR_NORMAL="light-gray/black"
GRUB_COLOR_HIGHLIGHT="green/black"
# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/usr/share/grub/background.png"
GRUB_THEME="/usr/share/grub/themes/manjaro/theme.txt"
# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"
here is my configuration file. Sometimes the animation will be displayed when shutting down, but it has not been displayed except for the first time
It probably needs early kms to work. We probably need to make a package to enable it automatically.
2 Likes
I talked to fast, the Gnome shell material shell extension package is not in fault. I think it is another extension or another program who I had installed who was the cause.
Sorry.
Otherwise, everything is Ok for me. 
The bug in gnome-layout-switcher with windows layout is now fixed.
Why Wayland by default on Gnome?
Wayland do not work properly with some browsers, can’t copy text from some aplications, VM do not work properly, and so.
So , why Wayland by default if is not ready yet?
BTW: I disabled Wayland to stay on X11 but after each kernel update it return to Wayland…
Thanks
- xorg is eol
- some things work better on wayland
- touch screens
- VMware client screen scaling
- fractional scaling
- gnome-shell animations
- touchpad gestures
- screen tearing
- on screen keyboard in gdm
- wider adoption of wayland accelerates the development. If nobody is using it, issues don’t get solved
Thank you for reporting, this needs to be addressed. The idea is that switching between wayland and xorg should be easy.
2 Likes
Thank you very much for your prompt response.
I really tried Wayland after realizing that installing the new iso on my Wayland diary driver was the default. However I have had many problems with VM, not even let me use the guest, with browsers, what I use is firefox and brave, in brave I lose many things, Wayland does not even respect the personal settings of the browser.
Starting from the fact that my PC has CPU and AMD graphics, apparently it’s not very friendly with my hardware, possibly with Nvidia’s proprietary hardware and driver it works better, I don’t know but it’s just a guess by me.
A quick example, in brave I can’t copy text, not even select it.
Thanks again.
That leaves me thinking: “Wayland for touch screens” works better?
Possibly if we think about adapting it to phones, tablets or touch screen computers, but I think that will be the minority in the case of the use of Wayland in a daily use desktop PC like mine.
Just a thought.
Once again I thank and congratulate the team for their excellent work with Manjaro.
Edit: I’m using the testing branch
Touch screens is somewhat of a minor point here. The big one is that Xorg is legacy software with rapindly diminishing support. Some use cases still benefit from it (remote help like teamviewer, games, nvidia hardware, some virtual machines), but overall it just gives better experience than Xorg. And if distros besides Fedora start actively using it, it’s going to improve faster.
1 Like
Thanks again @Chrysostomus
Fedora/Red Hat is trying to take a very big turn for the better, with a lot of investment and well-developed changes, but for me although it is an excellent platform, there are still things that require too much intervention by the user to use it in daily use.
Don’t you think Wayland is still a bit immature to set it as default?
I agree that X11 is a bit old and everything we already know about X11 but it works, however, I have seen that Wayland tries it, but still does not take safe steps for daily use without the need for user intervention and for the use of quite a few applications, there is still a lot of territory to cover.
I understand the differences between X11 and Wayland, at least what is necessary. I don’t use my PC for gaming or own Nvidia card, I work with video processing, subtitle editing for movies, shared resources like samba, ssh, sftp, remote desktop to my external servers, and so.
There are things, like dragging files from one place to another, copying, pasting, and the like, that still do not work well and that does not allow me to work well.
I don’t use a laptop for my day to day, I have a desktop PC with AMD hardware. Kyria and Lysia have been the most productive and one of the best experiences I have had, even using the testing branches.
I leave you this opinion / question, not as a criticism, on the contrary, I hope it serves as feedback and I can clarify which path I should take, for now Wayland, in my humble opinion, is a great development, but in the process of development .
It leaves me thinking of very new users, who will not find a user-friendly path. I do not want Ubuntu or Pop OS to continue to profit from what other distributions are not doing to adopt more migration towards Linux, such as a direct installation and an operational operating system without any or minimal user intervention.
Thank you very much for reading and helping me.
2 Likes
Your opinion is appreciated, and especially you noticing the issue with updates. Thank you! Our goal is to make it trivial for users to make the choice about it themselves, and updates overwriting the configuration is not intended behavior.
5 Likes
I looked into the issue. For me it does not overwrite the configuration file, but creates a pacnew file like it is supposed to. The PKGBUILD also has the configuration file in backup array. So, it might be that the issue was already fixed with the latest gdm update? 
1 Like
@Chrysostomus: I have still the problem with libreoffice-fresh 7.0.3-2 under Manjaro Gnome 20.2-rc. See news here.
I’m waiting stable version to see if the problem still exist.
After the latest update testing channel, it keep the Xorg default, so seems is fixed. Have no new kernel update yet, so I let you know if I find some issue when the kernel is updated.
Thanks.