Logout - When I want move a app

As soon as I try to move an icon in the overview to put it in a folder or move an application from one desktop to another, Gnome sends me a crash message and logout.

Why have you created 3 topics with the same subject?

I’m sorry, I didn’t mean to, I tried to delete them but I can’t

Please provide information about what version of Fedora and Gnome, and try to find some logs (gnome-logs). Also check if ABRT has captured the crash - you may want to report it, if possible.

Hardware Information:

  • Hardware Model: ASUS PRIME H670-PLUS D4
  • Memory: 32.0 GiB
  • Processor: 12th Gen Intel® Core™ i7-12700KF × 20
  • Graphics: NV167
  • Disk Capacity: 2.9 TB

Software Information:

  • Firmware Version: 1620
  • OS Name: Fedora Linux 39 (Workstation Edition)
  • OS Build: (null)
  • OS Type: 64-bit
  • GNOME Version: 45.1
  • Windowing System: X11
  • Kernel Version: Linux 6.5.6-300.fc39.x86_64

Log messages :
13:46:20 gdm-session-wor: gkr-pam: unable to locate daemon control file
13:46:12 gnome-session-b: Unrecoverable failure in required component org.gnome.Shell.desktop
13:46:07 reporter-system: Process 2482 (gnome-shell) crashed in dump_gjs_stack_on_signal_handler()
13:46:03 gnome-shell: Received an X Window System error.
This probably reflects a bug in the program.
The error was ‘BadCursor (invalid Cursor parameter)’.
(Details: serial 215438 error_code 6 request_code 95 (core protocol) minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the MUTTER_SYNC environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the mtk_x_error() function.)
13:44:22 kernel: nouveau 0000:01:00.0: fifo:000000:0004:0004:[gnome-logs[9637]] errored - disabling channel
13:14:56 systemd: Failed to start app-gnome-vmware\x2duser-2612.scope - Application launched by gnome-session-binary.
13:14:52 gdm-session-wor: gkr-pam: unable to locate daemon control file
13:14:45 gnome-session-b: Unrecoverable failure in required component org.gnome.Shell.desktop
13:14:35 (udev-worker): event10: Failed to call EVIOCSKEYCODE with scan code 0x7c, and key code 190: Invalid argument

I’m looking to use the ABRT client.
I’m starting with fedora

1 Like

:arrow_forward: abrt
bf9ae07 2x xorg-x11-xauth 2023-11-12 07:44:29
09e12fd 1x gnome-shell 2023-11-12 09:47:40
10026de 20x gnome-shell 2023-11-11 14:05:40
d3cb908 1x gnome-control-center 2023-11-11 11:02:13

:arrow_forward: abrt info
Id 09e12fd
Component gnome-shell
Count 1
Time 2023-11-12 09:47:40
Command line /usr/bin/gnome-shell
Package gnome-shell-45.1-1.fc39
User id 1000 (gg)
Path /var/spool/abrt/ccpp-2023-11-12-09:47:40.268368-9618

1 Like

:arrow_forward: journalctl _PID=7816
Nov 13 18:46:23 fedora gnome-session[7816]: gnome-session-binary[7816]: WARNING: Could not check if unit gnome-session-wayland@gnome-login.target is active: Error calling StartServiceByName f>
Nov 13 18:46:23 fedora gnome-session-binary[7816]: WARNING: Could not check if unit gnome-session-wayland@gnome-login.target is active: Error calling StartServiceByName for org.freedesktop.sy>
Nov 13 18:46:24 fedora gnome-session[7816]: gnome-session-binary[7816]: WARNING: Application ‘org.gnome.Shell.desktop’ killed by signal 9
Nov 13 18:46:24 fedora gnome-session-binary[7816]: WARNING: Application ‘org.gnome.Shell.desktop’ killed by signal 9
Nov 13 18:46:24 fedora gnome-session-binary[7816]: Unrecoverable failure in required component org.gnome.Shell.desktop

Check the journal for the oom killer running.
Also have a look at dmesg output for kernel reported issues.
I see you have 32GiB but wonder if you are running something that uses up all of memory.

I don’t understand the oom killer.
I don’t have anything using all my memory, it’s 7% usaged

:arrow_forward: dmesg -k
[ 1680.059953] nouveau 0000:01:00.0: fifo:PBDMA0: CTXNOTVALID chid:7
[ 1680.059960] nouveau 0000:01:00.0: fifo:000000:0007:0007:[mutter-x11-fram[7327]] errored -
I don’t understand the oom killer.
I don’t have anything using all my memory, it’s 7% usage

disabling channel
[ 1680.059965] nouveau 0000:01:00.0: Xorg[4692]: channel 7 killed!
[ 1680.351268] nouveau 0000:01:00.0: fifo:PBDMA0: CTXNOTVALID chid:8
[ 1680.351274] nouveau 0000:01:00.0: fifo:000000:0008:0008:[gjs[7398]] errored - disabling channel
[ 1680.351280] nouveau 0000:01:00.0: Xorg[4692]: channel 8 killed!

[ 3679.536571] nouveau 0000:01:00.0: fifo:PBDMA0: CTXNOTVALID chid:7
[ 3679.536587] nouveau 0000:01:00.0: fifo:000000:0007:0007:[gjs[10908]] errored - disabling channel
[ 3679.536592] nouveau 0000:01:00.0: Xorg[8458]: channel 7 killed!

[14816.852027] nouveau 0000:01:00.0: fifo:PBDMA0: CTXNOTVALID chid:3
[14816.852042] nouveau 0000:01:00.0: fifo:000000:0003:0003:[mutter-x11-fram[16966]] errored - disabling channel
[14816.852047] nouveau 0000:01:00.0: Xorg[11956]: channel 3 killed!

Archlinux : nvidia-{open,settings,utils} + opencl-nvidia for my T 600 Nvidia

Not sure what you mean. Baeldung.com may clarify what OOM does. “killed by signal 9” is how OOM terminates a process. Some bugs fill memory quickly, so

may have missed a transient event.

After a crash

▶ journalctl --since "5 min ago"
Nov 14 00:21:35 fedora gnome-shell[21854]: invalid (NULL) pointer instance
Nov 14 00:21:35 fedora gnome-shell[21854]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Nov 14 00:21:35 fedora gnome-shell[21854]: invalid (NULL) pointer instance
Nov 14 00:21:35 fedora gnome-shell[21854]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Nov 14 00:21:39 fedora gnome-shell[21854]: invalid (NULL) pointer instance
Nov 14 00:21:39 fedora gnome-shell[21854]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Nov 14 00:21:39 fedora gnome-shell[21854]: invalid (NULL) pointer instance
Nov 14 00:21:39 fedora gnome-shell[21854]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Nov 14 00:23:06 fedora /usr/libexec/gdm-x-session[21711]: (EE) event3  - Logitech MX Ergo: client bug: event processing lagging behind by 21ms, your system is too slow
Nov 14 00:23:16 fedora systemd[2199]: app-gnome-google\x2dchrome-22852.scope: Consumed 10min 35.730s CPU time.
Nov 14 00:23:16 fedora systemd[2199]: Stopping cgroupify@app-gnome-google\x2dchrome-22852.scope.service...
Nov 14 00:23:16 fedora systemd[2199]: Stopped cgroupify@app-gnome-google\x2dchrome-22852.scope.service.
Nov 14 00:23:17 fedora gnome-shell[21854]: invalid (NULL) pointer instance
Nov 14 00:23:17 fedora gnome-shell[21854]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Nov 14 00:23:17 fedora gnome-shell[21854]: invalid (NULL) pointer instance
Nov 14 00:23:17 fedora gnome-shell[21854]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Nov 14 00:23:19 fedora /usr/libexec/gdm-x-session[21711]: (EE) event3  - Logitech MX Ergo: client bug: event processing lagging behind by 24ms, your system is too slow
Nov 14 00:23:20 fedora gnome-shell[21854]: invalid (NULL) pointer instance
Nov 14 00:23:20 fedora gnome-shell[21854]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Nov 14 00:23:20 fedora gnome-shell[21854]: invalid (NULL) pointer instance
Nov 14 00:23:20 fedora gnome-shell[21854]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Nov 14 00:23:26 fedora gnome-shell[21854]: invalid (NULL) pointer instance
Nov 14 00:23:26 fedora gnome-shell[21854]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Nov 14 00:23:26 fedora gnome-shell[21854]: invalid (NULL) pointer instance
Nov 14 00:23:26 fedora gnome-shell[21854]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Nov 14 00:23:33 fedora systemd[2199]: app-gnome-Alacritty-23280.scope: Consumed 2.538s CPU time.
Nov 14 00:23:46 fedora gnome-shell[21854]: Received an X Window System error.
                                           This probably reflects a bug in the program.
                                           The error was 'BadCursor (invalid Cursor parameter)'.
                                             (Details: serial 283563 error_code 6 request_code 95 (core protocol) minor_code 0)
                                             (Note to programmers: normally, X errors are reported asynchronously;
                                              that is, you will receive the error a while after causing it.
                                              To debug your program, run it with the MUTTER_SYNC environment
                                              variable to change this behavior. You can then get a meaningful
                                              backtrace from your debugger if you break on the mtk_x_error() function.)
Nov 14 00:23:46 fedora audit[21854]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=21854 comm="gnome-shell" exe="/usr/bin/gnome-s>
Nov 14 00:23:46 fedora gnome-shell[21854]: == Stack trace for context 0x55ff08815730 ==
Nov 14 00:23:46 fedora gnome-shell[21854]: #0   55ff088dfa28 i   resource:///org/gnome/shell/ui/init.js:21 (aa88bd70ba0 @ 48)
Nov 14 00:23:46 fedora audit: BPF prog-id=175 op=LOAD
Nov 14 00:23:46 fedora audit: BPF prog-id=176 op=LOAD
Nov 14 00:23:46 fedora audit: BPF prog-id=177 op=LOAD
Nov 14 00:23:46 fedora systemd[1]: Started systemd-coredump@6-32683-0.service - Process Core Dump (PID 32683/UID 0).
Nov 14 00:23:46 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@6-32683-0 comm="systemd" exe="/usr/lib/sy>
Nov 14 00:23:47 fedora systemd-coredump[32684]: [🡕] Process 21854 (gnome-shell) of user 1000 dumped core.

Archlinux? How is that involved with your Fedora system.

There is no Archlinux involved in Fedora.
Running the command “dmesg -k” and seeing “nouveau” I thought that my Nividia card had a problem and on Archlinux I need to install the named packages for it to work.

I wonder if you need to install the nvidia drivers from rpmfusion?
Personally I use the rpmfusion drivers as nouveau does not works for games.
In the past it did not work for wayland or x11 for me.

If you want try that see Howto/NVIDIA - RPM Fusion

You might also be aware that the nouveau driver seems to not support hardware acceleration on any nvidia GPU and in some cases does not support newer gpus without the ‘nomodeset’ option.
For full performance of the nvidia gpu and graphics intensive apps it is necessary to install the nvidia drivers to replace the nouveau drivers.

I tried but I don’t understand anything

How do you replace the nouveau driver?

We might be able to explain if we had details about the steps taken (including commands) and the responses to those actions.

Posting the actions with copy and paste while including that data within the preformatted text tags (the </> button on the toolbar) would provide the details.

Installing the nvidia drivers will automatically enable that driver and replace the nouveau driver. The steps shown in the link by Barry just above would be good start.

sudo dnf install akmod-nvidia

reboot

How to find out which drivers are installed and used ?
But I think that :

sudo dnf install rpmfusion-nonfree-release-tainted
sudo dnf swap akmod-nvidia akmod-nvidia-open

Several ways.
first:
lsmod | grep -iE 'nouveau|nvidia'
If that returns a list of nvidia modules then the nvidia driver is in use. If it instead returns nouveau modules then nvidia is not loaded.

Second:
dmesg | grep -iE 'nvidia|nouveau|secure'
First look at the lines containing secure. If it indicates that secure boot is enabled then the nvidia driver cannot load without performing other steps.
The remaining lines will show either the nouveau driver loading or the nvidia driver loading.

If secure boot is enabled and the nvidia drivers are not loading then there are now 2 choices.

  1. Disable secure boot within the system bios to allow unsigned modules to load.

  2. Create a user defined certificate and recompile the nvidia modules signed by that certificate so they will load with secure boot enabled.
    This involves 2 steps.
    A. create and import the key using the instructions in /usr/share/doc/akmods/README.secureboot
    B. recompile the nvidia modules with
    sudo dnf remove kmod-nvidia-\* then sudo akmods --force.
    Once the akmods command ends simply reboot and repeat the lsmod command above to ensure the nvidia drivers are now loaded.

1 Like