jpcneto
(Jose Camargo)
October 29, 2024, 3:49pm
1
I just updated the system and I can’t open gnome apps. I can’t access files or the app store even settings. (I can access files through other apps like Softmarker text )
Update: I change to Xorg and it’s working normally. I think it’s a Wayland problem.
1 Like
I have the same issue, I can’t even use the terminal.
Do you have an Nvidia card and just installed the proprietary drivers? I’ve just run into this issue.
jpcneto
(Jose Camargo)
October 29, 2024, 4:09pm
4
Yes, I have Nvidia drivers but I didn’t need to reinstall. The update was smooth. Should I reinstall?
If the Nvidia drivers are the problem then I think the only thing that matters is that they are installed, one way or another.
Yes I have install the proprietary drivers for Nvidia
There has been for some time issues with the nvidia drivers not being properly rebuilt when doing a system-upgrade because the automatic reboot after the upgrade completes occurs too soon for some systems.
The fix has often been sudo akmods --rebuild --force
then another reboot after that completes.
You can see the problem noted in Third-party modules (e.g. Nvidia) are not rebuilt during system upgrade
1 Like
I would like to try but i can’t even open the terminal
jpcneto
(Jose Camargo)
October 29, 2024, 4:34pm
9
I just did this and nothing changed. But thanks for your answer!
jpcneto
(Jose Camargo)
October 29, 2024, 8:04pm
10
Try to change the section to Xorg. It’s works for me
ankursinha
(FranciscoD)
October 29, 2024, 8:42pm
13
Could you please try to run an app from a terminal and see what errors you get?
alexbespik
(alex besporochni)
October 29, 2024, 8:43pm
14
Write me please name of system app that i need to write in console
alexbespik
(alex besporochni)
October 29, 2024, 8:44pm
16
FranciscoD:
gnome-control-center
alexbespik@fedora:~$ gnome-control-center
MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:763: FINISHME: support YUV colorspace with DRM format modifiers
MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:794: FINISHME: support more multi-planar formats with DRM modifiers
alexbespik@fedora:~$
ankursinha
(FranciscoD)
October 29, 2024, 8:46pm
17
That doesn’t look like bad. Did the app open?
Can you also look at your logs to see what you get? Try looking at the end of this:
journalctl -b
alexbespik
(alex besporochni)
October 29, 2024, 8:47pm
19
Oct 29 12:34:51 fedora kernel: Linux version 6.11.5-300.fc41.x86_64 (mockbuild@a0564de4e00d4277aa3a51770ad85255) (gcc (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3), GNU ld version 2.43.1-2.fc41) #1 SMP PREEMPT_DYNAMIC Tue Oct 22 20:11:15 UTC >
Oct 29 12:34:51 fedora kernel: Command line: BOOT_IMAGE=(hd1,gpt2)/vmlinuz-6.11.5-300.fc41.x86_64 root=UUID=78f862dc-9163-42c0-ab40-a47e948a7beb ro rootflags=subvol=root rd.driver.blacklist=nouveau modprobe.blacklist=nouveau rhgb quiet r>
Oct 29 12:34:51 fedora kernel: BIOS-provided physical RAM map:
Oct 29 12:34:51 fedora kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009dfff] usable
Oct 29 12:34:51 fedora kernel: BIOS-e820: [mem 0x000000000009e000-0x000000000009efff] reserved
Oct 29 12:34:51 fedora kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] usable
Oct 29 12:34:51 fedora kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Oct 29 12:34:51 fedora kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000097548fff] usable
Oct 29 12:34:51 fedora kernel: BIOS-e820: [mem 0x0000000097549000-0x0000000099145fff] reserved
Oct 29 12:34:51 fedora kernel: BIOS-e820: [mem 0x0000000099146000-0x0000000099275fff] ACPI data
Oct 29 12:34:51 fedora kernel: BIOS-e820: [mem 0x0000000099276000-0x0000000099375fff] ACPI NVS
Oct 29 12:34:51 fedora kernel: BIOS-e820: [mem 0x0000000099376000-0x0000000099c4dfff] reserved
Oct 29 12:34:51 fedora kernel: BIOS-e820: [mem 0x0000000099c4e000-0x0000000099c4efff] usable
Oct 29 12:34:51 fedora kernel: BIOS-e820: [mem 0x0000000099c4f000-0x000000009f7fffff] reserved
Oct 29 12:34:51 fedora kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Oct 29 12:34:51 fedora kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
Oct 29 12:34:51 fedora kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Oct 29 12:34:51 fedora kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Oct 29 12:34:51 fedora kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Oct 29 12:34:51 fedora kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct 29 12:34:51 fedora kernel: BIOS-e820: [mem 0x0000000100000000-0x000000085e7fffff] usable
Oct 29 12:34:51 fedora kernel: NX (Execute Disable) protection: active
Oct 29 12:34:51 fedora kernel: APIC: Static calls initialized
Oct 29 12:34:51 fedora kernel: e820: update [mem 0x8f0c2018-0x8f0d1057] usable ==> usable
Oct 29 12:34:51 fedora kernel: extended physical RAM map:
Oct 29 12:34:51 fedora kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009dfff] usable
Oct 29 12:34:51 fedora kernel: reserve setup_data: [mem 0x000000000009e000-0x000000000009efff] reserved
Oct 29 12:34:51 fedora kernel: reserve setup_data: [mem 0x000000000009f000-0x000000000009ffff] usable
Oct 29 12:34:51 fedora kernel: reserve setup_data: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Oct 29 12:34:51 fedora kernel: reserve setup_data: [mem 0x0000000000100000-0x000000008f0c2017] usable
Oct 29 12:34:51 fedora kernel: reserve setup_data: [mem 0x000000008f0c2018-0x000000008f0d1057] usable
Oct 29 12:34:51 fedora kernel: reserve setup_data: [mem 0x000000008f0d1058-0x0000000097548fff] usable
Oct 29 12:34:51 fedora kernel: reserve setup_data: [mem 0x0000000097549000-0x0000000099145fff] reserved
Oct 29 12:34:51 fedora kernel: reserve setup_data: [mem 0x0000000099146000-0x0000000099275fff] ACPI data
Oct 29 12:34:51 fedora kernel: reserve setup_data: [mem 0x0000000099276000-0x0000000099375fff] ACPI NVS
Oct 29 12:34:51 fedora kernel: reserve setup_data: [mem 0x0000000099376000-0x0000000099c4dfff] reserved
Oct 29 12:34:51 fedora kernel: reserve setup_data: [mem 0x0000000099c4e000-0x0000000099c4efff] usable
Oct 29 12:34:51 fedora kernel: reserve setup_data: [mem 0x0000000099c4f000-0x000000009f7fffff] reserved
Oct 29 12:34:51 fedora kernel: reserve setup_data: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Oct 29 12:34:51 fedora kernel: reserve setup_data: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
Oct 29 12:34:51 fedora kernel: reserve setup_data: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Oct 29 12:34:51 fedora kernel: reserve setup_data: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Oct 29 12:34:51 fedora kernel: reserve setup_data: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Oct 29 12:34:51 fedora kernel: reserve setup_data: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct 29 12:34:51 fedora kernel: reserve setup_data: [mem 0x0000000100000000-0x000000085e7fffff] usable
Oct 29 12:34:51 fedora kernel: efi: EFI v2.7 by American Megatrends
Oct 29 12:34:51 fedora kernel: efi: ACPI=0x99275000 ACPI 2.0=0x99275014 TPMFinalLog=0x99304000 SMBIOS=0x99802000 SMBIOS 3.0=0x99801000 MEMATTR=0x9127d018 ESRT=0x8f127898 MOKvar=0x99830000 RNG=0x99206018 TPMEventLog=0x991fb018
Oct 29 12:34:51 fedora kernel: random: crng init done
Oct 29 12:34:51 fedora kernel: efi: Remove mem261: MMIO range=[0xe0000000-0xefffffff] (256MB) from e820 map
Oct 29 12:34:51 fedora kernel: e820: remove [mem 0xe0000000-0xefffffff] reserved
Oct 29 12:34:51 fedora kernel: efi: Not removing mem262: MMIO range=[0xfe000000-0xfe010fff] (68KB) from e820 map
Oct 29 12:34:51 fedora kernel: efi: Not removing mem263: MMIO range=[0xfec00000-0xfec00fff] (4KB) from e820 map
Oct 29 12:34:51 fedora kernel: efi: Not removing mem264: MMIO range=[0xfed00000-0xfed03fff] (16KB) from e820 map
Oct 29 12:34:51 fedora kernel: efi: Not removing mem265: MMIO range=[0xfee00000-0xfee00fff] (4KB) from e820 map
lines 1-54
ankursinha
(FranciscoD)
October 29, 2024, 8:50pm
20
That’s the start of the log. If you keep going down, you’ll get to the bottom—that’s where the latest bits will be. So, I’d check the logs, then try running gnome-control-center
in a terminal and then check the logs again to see if any errors popped up as a result
Here’s more info on viewing system logs:
Log files contain messages about the system, including the kernel, services, and applications running on it. These contain information that helps troubleshoot issues, or simply monitor system functions. Fedora uses…