You are not logged in.

#1 2024-05-04 09:08:20

therealcatman
Member
Registered: 2024-02-16
Posts: 11

cannot open gnome settings

i cannot open Gnome settings with the hardened kernel. This did not happen in the non hardened kernel, both 6.8.9-arch1-1 #1

When i try, this is what i get in the Journallog:

Mai 04 11:03:25 archpc systemd[1107]: Started Application launched by gnome-shell.
Mai 04 11:03:25 archpc gnome-shell[1263]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e00004
Mai 04 11:03:26 archpc kernel: traps: vqueue:src[3372] trap invalid opcode ip:6516a0083009 sp:6515a7dfd488 error:0 in orcexec.OoFhZV (deleted)[6516a0083000+10000]
Mai 04 11:03:26 archpc systemd[1]: Started Process Core Dump (PID 3409/UID 0).
Mai 04 11:03:28 archpc systemd-coredump[3410]: [?] Process 3228 (gnome-control-c) of user 1000 dumped core.

and this is the console output whenn i start gnome-control-center in a terminal:

[user@archpc ~]$ gnome-control-center
Ungültiger Maschinenbefehl (Speicherabzug geschrieben)

Offline

#2 2024-05-04 13:01:40

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,892

Re: cannot open gnome settings

The hardened kernel disables some AVX function on older CPUs (what do you have? Afaik this mostly affected sandybridge and co) that software might use and some software use an incorrect method of querying for support of AVX, assume it is possible, and on trying to use it it gets shut down.

Cross ref: https://bbs.archlinux.org/viewtopic.php?id=293869

Offline

#3 2024-05-05 20:00:19

therealcatman
Member
Registered: 2024-02-16
Posts: 11

Re: cannot open gnome settings

model name    : Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz

Offline

#4 2024-05-05 21:36:55

seth
Member
Registered: 2012-09-03
Posts: 52,269

Offline

#5 2024-05-06 18:16:10

therealcatman
Member
Registered: 2024-02-16
Posts: 11

Re: cannot open gnome settings

what can i do?

Offline

#6 2024-05-06 18:49:32

loqs
Member
Registered: 2014-03-06
Posts: 17,581

Re: cannot open gnome settings

What version of orc is installed on your system? I believe 0.4.38 contains https://gitlab.freedesktop.org/gstreame … f961e9ed6a
Edit:
https://gitlab.freedesktop.org/gstreame … /issues/65 I think the fix applied is wrong in that checking the CPU supports XSAVE is not enough as it does not check the CPU supports OSXSAVE or SSE and AVX state bits of XCR0 are set.
Edit2:
If you disable AVX/AVX2 detection in orc can you reproduce the issue?

diff --git a/orc/orccpu-x86.c b/orc/orccpu-x86.c
index defa101..4fbe188 100644
--- a/orc/orccpu-x86.c
+++ b/orc/orccpu-x86.c
@@ -329,6 +329,7 @@ orc_x86_cpuid_handle_standard_flags (void)
     orc_x86_sse_flags |= ORC_TARGET_SSE_SSE4_2;
   }
 
+#if 0
   // Linux mitigation for GDS requires checking for XSAVE too.
   // https://bugzilla.mozilla.org/show_bug.cgi?id=1854795
   // https://gitlab.freedesktop.org/gstreamer/orc/-/issues/65
@@ -343,6 +344,7 @@ orc_x86_cpuid_handle_standard_flags (void)
   if (ebx & (1 << 5) && xsave_enabled) {
     orc_x86_sse_flags |= ORC_TARGET_AVX_AVX2;
   }
+#endif
 }
 
 static void

orc-0.4.38 with the above diff applied:
https://drive.google.com/file/d/1v_EnKx … sp=sharing orc-0.4.38-1.1-x86_64.pkg.tar.zst

Last edited by loqs (2024-05-06 21:13:48)

Offline

Board footer

Powered by FluxBB