Brave’s issues should be resolved… now Brave users can downgrade Brave with a working version
2 Likes
Still getting issues, I uninstalled it So i can update it. But when I try to install it again through the official community repository I get the following errors:
invalid or corrupted package (PGP signature):
Preparing...
Synchronizing package databases...
Warning: manjaro-hello: local (0.6.7-2) is newer than extra (0.6.6-6)
Resolving dependencies...
Checking inter-conflicts...
Download of brave-browser (1.27.109-1) started
Download of brave-browser (1.27.109-1) finished
Checking keyring...
Checking integrity...
Error: brave-browser: signature from "Stefano Capitani <stefano@manjaro.org>" is invalid
Removing invalid files and retrying...
Resolving dependencies...
Checking inter-conflicts...
Download of brave-browser (1.27.109-1) started
Download of brave-browser (1.27.109-1) finished
Checking keyring...
Checking integrity...
Error: brave-browser: signature from "Stefano Capitani <stefano@manjaro.org>" is invalid
Failed to commit transaction:
invalid or corrupted package (PGP signature):
Brave working version:
stable 1.26.74
beta 1.27.84
try to do
sudo pacman-mirrors -f5 && sudo pacman -Syyuu
5 Likes
For now the only two problems I had were:
1- clamav was not updated using the sudo freshclam command, now it could be updated (so I calculate it would have been a problem with the clamav server.
2- catfish does not work throw the following error:
1 Like
this worked for me. thank you.
Can confirm same here
…Or use yay -Syu --combinedupgrade to exclude your current brave package to upgrade to a broken brave package.
try to use the desktop file of the previous version (which I took from a backup I had), also, edit the one of the new version as “/ usr / bin / catfish% f” does not work either
I updated today and gdm crashed because of this:
gdm.service: Failed to locate executable /usr/lib/gdm-wait-for-drm: No such file or directory
gdm.service: Failed at step EXEC spawning /usr/lib/gdm-wait-for-drm: No such file or directory
The binary /usr/lib/gdm-wait-for-drm is there, but gdm says it is not there.
journalctl --unit=gdm --boot=0
journalctl --unit=gdm --boot=0
-- Journal begins at Sat 2021-04-24 15:22:48 CEST, ends at Thu 2021-07-29 01:04:00 CEST. --
Jul 29 01:03:27 manjaro systemd[580]: gdm.service: Failed to locate executable /usr/lib/gdm-wait-for-drm: No such file or directory
Jul 29 01:03:27 manjaro systemd[580]: gdm.service: Failed at step EXEC spawning /usr/lib/gdm-wait-for-drm: No such file or directory
Jul 29 01:03:27 manjaro systemd[1]: Starting GNOME Display Manager...
Jul 29 01:03:27 manjaro systemd[1]: gdm.service: Control process exited, code=exited, status=203/EXEC
Jul 29 01:03:27 manjaro systemd[1]: gdm.service: Failed with result 'exit-code'.
Jul 29 01:03:27 manjaro systemd[1]: Failed to start GNOME Display Manager.
Jul 29 01:03:27 manjaro systemd[1]: gdm.service: Scheduled restart job, restart counter is at 1.
Jul 29 01:03:27 manjaro systemd[1]: Stopped GNOME Display Manager.
Jul 29 01:03:27 manjaro systemd[1]: Starting GNOME Display Manager...
Jul 29 01:03:27 manjaro systemd[592]: gdm.service: Failed to locate executable /usr/lib/gdm-wait-for-drm: No such file or directory
Jul 29 01:03:27 manjaro systemd[592]: gdm.service: Failed at step EXEC spawning /usr/lib/gdm-wait-for-drm: No such file or directory
Jul 29 01:03:27 manjaro systemd[1]: gdm.service: Control process exited, code=exited, status=203/EXEC
Jul 29 01:03:27 manjaro systemd[1]: gdm.service: Failed with result 'exit-code'.
Jul 29 01:03:27 manjaro systemd[1]: Failed to start GNOME Display Manager.
Jul 29 01:03:27 manjaro systemd[1]: gdm.service: Scheduled restart job, restart counter is at 2.
Jul 29 01:03:27 manjaro systemd[1]: Stopped GNOME Display Manager.
Jul 29 01:03:27 manjaro systemd[1]: Starting GNOME Display Manager...
Jul 29 01:03:27 manjaro systemd[597]: gdm.service: Failed to locate executable /usr/lib/gdm-wait-for-drm: No such file or directory
Jul 29 01:03:27 manjaro systemd[597]: gdm.service: Failed at step EXEC spawning /usr/lib/gdm-wait-for-drm: No such file or directory
Jul 29 01:03:27 manjaro systemd[1]: gdm.service: Control process exited, code=exited, status=203/EXEC
Jul 29 01:03:27 manjaro systemd[1]: gdm.service: Failed with result 'exit-code'.
Jul 29 01:03:27 manjaro systemd[1]: Failed to start GNOME Display Manager.
Jul 29 01:03:27 manjaro systemd[1]: gdm.service: Scheduled restart job, restart counter is at 3.
Jul 29 01:03:27 manjaro systemd[1]: Stopped GNOME Display Manager.
Jul 29 01:03:27 manjaro systemd[1]: Starting GNOME Display Manager...
Jul 29 01:03:27 manjaro systemd[598]: gdm.service: Failed to locate executable /usr/lib/gdm-wait-for-drm: No such file or directory
Jul 29 01:03:27 manjaro systemd[598]: gdm.service: Failed at step EXEC spawning /usr/lib/gdm-wait-for-drm: No such file or directory
Jul 29 01:03:27 manjaro systemd[1]: gdm.service: Control process exited, code=exited, status=203/EXEC
Jul 29 01:03:27 manjaro systemd[1]: gdm.service: Failed with result 'exit-code'.
Jul 29 01:03:27 manjaro systemd[1]: Failed to start GNOME Display Manager.
Jul 29 01:03:27 manjaro systemd[1]: gdm.service: Scheduled restart job, restart counter is at 4.
Jul 29 01:03:27 manjaro systemd[1]: Stopped GNOME Display Manager.
Jul 29 01:03:27 manjaro systemd[1]: Starting GNOME Display Manager...
Jul 29 01:03:27 manjaro systemd[599]: gdm.service: Failed to locate executable /usr/lib/gdm-wait-for-drm: No such file or directory
Jul 29 01:03:27 manjaro systemd[599]: gdm.service: Failed at step EXEC spawning /usr/lib/gdm-wait-for-drm: No such file or directory
Jul 29 01:03:27 manjaro systemd[1]: gdm.service: Control process exited, code=exited, status=203/EXEC
Jul 29 01:03:27 manjaro systemd[1]: gdm.service: Failed with result 'exit-code'.
Jul 29 01:03:27 manjaro systemd[1]: Failed to start GNOME Display Manager.
Jul 29 01:03:28 manjaro systemd[1]: gdm.service: Scheduled restart job, restart counter is at 5.
Jul 29 01:03:28 manjaro systemd[1]: Stopped GNOME Display Manager.
Jul 29 01:03:28 manjaro systemd[1]: gdm.service: Start request repeated too quickly.
Jul 29 01:03:28 manjaro systemd[1]: gdm.service: Failed with result 'exit-code'.
Jul 29 01:03:28 manjaro systemd[1]: Failed to start GNOME Display Manager.
Jul 29 01:03:28 manjaro systemd[1]: gdm.service: Triggering OnFailure= dependencies.
Jul 29 01:03:28 manjaro systemd[1]: gdm.service: Failed to enqueue OnFailure= job, ignoring: Unit plymouth-quit.service not found.
cat /lib/systemd/system/gdm.service
[Unit]
Description=GNOME Display Manager
# replaces the getty
Conflicts=getty@tty1.service
After=getty@tty1.service
# replaces plymouth-quit since it quits plymouth on its own
Conflicts=
After=
# Needs all the dependencies of the services it's replacing
# pulled from getty@.service and
# (except for plymouth-quit-wait.service since it waits until
# plymouth is quit, which we do)
After=rc-local.service plymouth-start.service systemd-user-sessions.service
# GDM takes responsibility for stopping plymouth, so if it fails
# for any reason, make sure plymouth still stops
OnFailure=plymouth-quit.service
[Service]
ExecStart=/usr/bin/gdm
KillMode=mixed
Restart=always
IgnoreSIGPIPE=no
BusName=org.gnome.DisplayManager
EnvironmentFile=-/etc/locale.conf
ExecReload=/bin/kill -SIGHUP $MAINPID
KeyringMode=shared
ExecStartPre=/usr/lib/gdm-wait-for-drm
[Install]
Alias=display-manager.service
ls /usr/lib/gdm*
/usr/lib/gdm-host-chooser /usr/lib/gdm-wait-for-drm
/usr/lib/gdm-runtime-config /usr/lib/gdm-wayland-session
/usr/lib/gdm-session-worker /usr/lib/gdm-x-session
/usr/lib/gdm-simple-chooser
inxi -Fazy
System:
Kernel: 5.10.52-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-5.10-x86_64
root=UUID=c2477149-41ea-47fb-897e-40c856451c4e ro rootflags=subvol=@ quiet
udev.log_priority=3 nvidia-drm.modeset=1 mitigations=off nowatchdog
Desktop: GNOME 40.3 tk: GTK 3.24.30 wm: gnome-shell dm: GDM 40.0
Distro: Manjaro Linux base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: F2A55-M LK2 v: Rev X.0x serial: <filter>
UEFI: American Megatrends v: 6308 date: 11/25/2014
CPU:
Info: Quad Core model: AMD A8-5600K APU with Radeon HD Graphics bits: 64
type: MCP arch: Piledriver family: 15 (21) model-id: 10 (16) stepping: 1
microcode: 6001119 cache: L2: 2 MiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
bogomips: 28958
Speed: 1403 MHz min/max: 1400/3600 MHz boost: enabled Core speeds (MHz):
1: 1403 2: 1406 3: 1402 4: 1407
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 status: Vulnerable: __user pointer sanitization and
usercopy barriers only; no swapgs barriers
Type: spectre_v2 status: Vulnerable, STIBP: disabled
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: ZOTAC driver: nvidia
v: 470.57.02 alternate: nouveau,nvidia_drm bus-ID: 01:00.0
chip-ID: 10de:1c82 class-ID: 0300
Display: x11 server: X.Org 1.20.11 compositor: gnome-shell driver:
loaded: nvidia display-ID: :1 screens: 1
Screen-1: 0 s-res: 1920x1200 s-dpi: 96 s-size: 508x318mm (20.0x12.5")
s-diag: 599mm (23.6")
Monitor-1: DP-0 res: 1920x1200 hz: 60 dpi: 94 size: 518x324mm (20.4x12.8")
diag: 611mm (24.1")
OpenGL: renderer: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
v: 4.6.0 NVIDIA 470.57.02 direct render: Yes
Audio:
Device-1: AMD FCH Azalia vendor: ASUSTeK driver: snd_hda_intel v: kernel
bus-ID: 00:14.2 chip-ID: 1022:780d class-ID: 0403
Device-2: NVIDIA GP107GL High Definition Audio vendor: ZOTAC
driver: snd_hda_intel v: kernel bus-ID: 01:00.1 chip-ID: 10de:0fb9
class-ID: 0403
Sound Server-1: ALSA v: k5.10.52-1-MANJARO running: yes
Sound Server-2: JACK v: 0.125.0 running: no
Sound Server-3: PulseAudio v: 14.2 running: yes
Sound Server-4: PipeWire v: 0.3.32 running: no
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK P8 series driver: r8169 v: kernel port: d000 bus-ID: 04:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: enp4s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 5.68 TiB used: 3.9 TiB (68.7%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Apacer model: AS350 240GB
size: 223.57 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
type: SSD serial: <filter> rev: 3PE0 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD10EZEX-08WN4A0
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s
type: HDD rpm: 7200 serial: <filter> rev: 1A01 scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 vendor: Toshiba model: DT01ACA100
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s
type: HDD rpm: 7200 serial: <filter> rev: A750 scheme: GPT
ID-4: /dev/sdd maj-min: 8:48 vendor: Western Digital model: WD40EZRZ-00GXCB0
size: 3.64 TiB block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s
type: HDD rpm: 5400 serial: <filter> rev: 0A80 scheme: GPT
Partition:
ID-1: / raw-size: 68.36 GiB size: 68.36 GiB (100.00%)
used: 39.28 GiB (57.5%) fs: btrfs dev: /dev/sda4 maj-min: 8:4
ID-2: /boot/efi raw-size: 100 MiB size: 99.8 MiB (99.78%)
used: 686 KiB (0.7%) fs: vfat dev: /dev/sda3 maj-min: 8:3
ID-3: /home raw-size: 68.36 GiB size: 68.36 GiB (100.00%)
used: 39.28 GiB (57.5%) fs: btrfs dev: /dev/sda4 maj-min: 8:4
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 11.72 GiB used: 0 KiB (0.0%) priority: -2
file: /swap/swapfile
Sensors:
System Temperatures: cpu: 35.0 C mobo: 34.0 C gpu: nvidia temp: 35 C
Fan Speeds (RPM): cpu: 0 fan-1: 1171 gpu: nvidia fan: 47%
Power: 12v: N/A 5v: N/A 3.3v: 3.31 vbat: 3.31
Info:
Processes: 300 Uptime: 9m wakeups: 0 Memory: 7.73 GiB used: 2.54 GiB (32.9%)
Init: systemd v: 248 target: graphical.target tool: systemctl Compilers:
gcc: 11.1.0 clang: 12.0.1 Packages: 1861 apt: 0 pacman: 1852 lib: 474
flatpak: 9 Shell: Zsh v: 5.8 running-in: gnome-terminal inxi: 3.3.06
EDIT: Skipping and ignoring Update for GDM solved it for now.
I looked into into the files catfish old version and the one that’s upto date both the same.
Nevermind
Another stable release, last release was just 5 days ago. I wish the updates comes with more delay for bug huntig.
When I looked up my backup files for the catfish
issue I did that on one of my ExtHDs,
then offline went to open an app and clicked the wrong icon I clicked Timeshift said oops waited for the permission box so to shut it and click on the correct icon uhh
Timeshift authentication box didn’t show up at all tried to open with the main menu nop no go tried several times,
so now I have/had a catfish AND timeshift that wont open,
Know enough to know to use live session and had to restore with Timeshift to restore Timeshift itself.
What is going on to cause these things to happen ? ((or not happen (open))
What to we need to do to not have this happen to our machines ?
My VS Code installation does not work anymore after doing this stable update.
What can I do to make it work again?
VS Code is in the repositories, can you try using the non-snap version?
sudo pacman -S code
(No idea how the snap and native versions may conflict, would suggest uninstalling snap first)
2 Likes
this update was fast, I think the last update was a week ago 
(VS) Code in the repositories and in flatpak (flathub) work well, but how can I migrate the settings and extensions from the previous installation that does not work anymore?
Normally all snaps configurations are stored in your ~/Snap folder in your home folder,you may have to activate “show hidden files and folders” to enter vscode folder in there (I don’t use snaps so I may be wrong)
But VS Code is in the official repositories.