I cannot launch any QT application from gnome-shell because they segfault. e.g. torbrowser-launcher

Jun 28 12:25:43 arch-xps systemd: Started Application launched by gnome-shell.
Jun 28 12:25:43 arch-xps python: Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
Jun 28 12:25:43 arch-xps python: qt.qpa.xcb: could not connect to display
Jun 28 12:25:43 arch-xps python: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
Jun 28 12:25:43 arch-xps python: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
                                       
                                       Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
Jun 28 12:25:43 arch-xps systemd-coredump: Process 4287 (torbrowser-laun) of user 1000 terminated abnormally with signal 6/ABRT, processing...
Jun 28 12:25:43 arch-xps systemd[1] : Created slice Slice /system/systemd-coredump.
Jun 28 12:25:43 arch-xps systemd[1] : Started Process Core Dump (PID 4303/UID 0).
Jun 28 12:25:43 arch-xps systemd-coredump: [🡕] Process 4287 (torbrowser-laun) of user 1000 dumped core.
                                                 
                                                 Stack trace of thread 4287:
                                                 #0  0x00007f33c34a774c n/a (libc.so.6 + 0x9774c)
                                                 #1  0x00007f33c344ddc0 raise (libc.so.6 + 0x3ddc0)
                                                 #2  0x00007f33c343557a abort (libc.so.6 + 0x2557a)
                                                 #3  0x00007f33c22982e0 _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5 + 0x982e0)
                                                 #4  0x00007f33be1368c6 _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt5Gui.so.5 + 0x1368c6)
                                                 #5  0x00007f33be136f99 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5 + 0x136f99)
                                                 #6  0x00007f33c24c9525 _ZN23QCoreApplicationPrivate4initEv (libQt5Core.so.5 + 0x2c9525)
                                                 #7  0x00007f33be13704e _ZN22QGuiApplicationPrivate4initEv (libQt5Gui.so.5 + 0x13704e)
                                                 #8  0x00007f33be954d36 _ZN19QApplicationPrivate4initEv (libQt5Widgets.so.5 + 0x154d36)
                                                 #9  0x00007f33bf2d9133 n/a (QtWidgets.abi3.so + 0x2d9133)
                                                 #10 0x00007f33c2c60af7 n/a (sip.cpython-313-x86_64-linux-gnu.so + 0x1aaf7)
                                                 #11 0x00007f33c3863250 n/a (libpython3.13.so.1.0 + 0x263250)
                                                 #12 0x00007f33c37dbc83 n/a (libpython3.13.so.1.0 + 0x1dbc83)
                                                 #13 0x00007f33c3760e3b _PyObject_MakeTpCall (libpython3.13.so.1.0 + 0x160e3b)
                                                 #14 0x00007f33c37752be _PyEval_EvalFrameDefault (libpython3.13.so.1.0 + 0x1752be)
                                                 #15 0x00007f33c37a8dda n/a (libpython3.13.so.1.0 + 0x1a8dda)
                                                 #16 0x00007f33c3760d9d _PyObject_MakeTpCall (libpython3.13.so.1.0 + 0x160d9d)
                                                 #17 0x00007f33c37752be _PyEval_EvalFrameDefault (libpython3.13.so.1.0 + 0x1752be)
                                                 #18 0x00007f33c384c8b9 PyEval_EvalCode (libpython3.13.so.1.0 + 0x24c8b9)
                                                 #19 0x00007f33c388af5c n/a (libpython3.13.so.1.0 + 0x28af5c)
                                                 #20 0x00007f33c388801b n/a (libpython3.13.so.1.0 + 0x28801b)
                                                 #21 0x00007f33c3885718 n/a (libpython3.13.so.1.0 + 0x285718)
                                                 #22 0x00007f33c38849d2 n/a (libpython3.13.so.1.0 + 0x2849d2)
                                                 #23 0x00007f33c3884343 n/a (libpython3.13.so.1.0 + 0x284343)
                                                 #24 0x00007f33c388248b Py_RunMain (libpython3.13.so.1.0 + 0x28248b)
                                                 #25 0x00007f33c3839dcb Py_BytesMain (libpython3.13.so.1.0 + 0x239dcb)
                                                 #26 0x00007f33c34376b5 n/a (libc.so.6 + 0x276b5)
                                                 #27 0x00007f33c3437769 __libc_start_main (libc.so.6 + 0x27769)
                                                 #28 0x0000564d96d2a045 _start (/usr/bin/python3.13 + 0x1045)
                                                 
                                                 Stack trace of thread 4302:
                                                 #0  0x00007f33c34ade22 n/a (libc.so.6 + 0x9de22)
                                                 #1  0x00007f33c34a1fda n/a (libc.so.6 + 0x91fda)
                                                 #2  0x00007f33c34a2024 n/a (libc.so.6 + 0x92024)
                                                 #3  0x00007f33c351c5a6 ppoll (libc.so.6 + 0x10c5a6)
                                                 #4  0x00007f33c1909e04 n/a (libglib-2.0.so.0 + 0x5fe04)
                                                 #5  0x00007f33c1909ee5 g_main_context_iteration (libglib-2.0.so.0 + 0x5fee5)
                                                 #6  0x00007f33c2521489 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x321489)
                                                 #7  0x00007f33c24c807b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2c807b)
                                                 #8  0x00007f33c22f531b _ZN7QThread4execEv (libQt5Core.so.5 + 0xf531b)
                                                 #9  0x00007f33bc8f4d2e n/a (libQt5DBus.so.5 + 0x17d2e)
                                                 #10 0x00007f33c22f1859 n/a (libQt5Core.so.5 + 0xf1859)
                                                 #11 0x00007f33c34a57eb n/a (libc.so.6 + 0x957eb)
                                                 #12 0x00007f33c352918c n/a (libc.so.6 + 0x11918c)
                                                 ELF object binary architecture: AMD x86-64

while launching it from terminal, it starts successfully! and I get:

$ torbrowser-launcher 
Tor Browser Launcher
By Micah Lee & Tor Project, licensed under MIT
version 0.3.7
https://gitlab.torproject.org/tpo/applications/torbrowser-launcher/ 
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
Launching Tor Browser.
Running /home/mattia/.local/share/torbrowser/tbb/x86_64/tor-browser/start-tor-browser.desktop
Launching './Browser/start-tor-browser --detach'...

same happens with picard, torbrowser or masterpdfeditor instead GPXSee starts fine! It looks like **gnome-shell** ignores customized variable **QT_QPA_PLATFORM** (which I defined in *.bashrc*), so I tried launching torbrowser forcing that variable as empty, and it segfaults, as well:

$ QT_QPA_PLATFORM= torbrowser-launcher 
Tor Browser Launcher
By Micah Lee & Tor Project, licensed under MIT
version 0.3.7
https://gitlab.torproject.org/tpo/applications/torbrowser-launcher/ 
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
qt.qpa.xcb: could not connect to display 
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

Aborted (core dumped)

Any help is welcome! **EDIT-1:** system does not have XWayland, or better, I disabled it from gnome-shell[[1] ]; --- Arch Linux, GNOME 48 under Wayland, qt{5,6}-wayland packages installed

When a segmentation fault occurs in Linux, the error message Segmentation fault (core dumped) will be printed to the terminal (if any), and the program will be terminated. As a C/C++ dev, this happens to me quite often, and I usually ignore it and move onto gdb, recreating my previous action in order to trigger the invalid memory reference again. Instead, I thought I might be able to perhaps use this "core" instead, as running gdb all the time is rather tedious, and I cannot always recreate the segmentation fault. My questions are three: * Where is this elusive "core" dumped? * What does it contain? * What can I do with it?

Noob here ! I have archlabs which runs on archlinux. After normal upgrade, most apps do not run (texmaker, qt5ct ...), when running them from terminal they give the error : "Segmentation fault (core dumped)". I examined most core dumps, couldn't figure out what is the problem, when I tried to run a backtrace, I found this answer to be describing this matter really well (second part of the answer), but does not provide steps for noobs to solve it. here are 1st lines from the backtrace :

Thread 2 (Thread 0x7ffff3684700 (LWP 2439)):
#0  0x00007ffff6a1405f in poll () from /usr/lib/libc.so.6
No symbol table info available.
#1  0x00007ffff3d4063b in ?? () from /usr/lib/libxcb.so.1
No symbol table info available.
#2  0x00007ffff3d4237b in xcb_wait_for_event () from /usr/lib/libxcb.so.1
No symbol table info available.
#3  0x00007ffff3932c51 in ?? () from /usr/lib/libQt5XcbQpa.so.5
No symbol table info available.
#4  0x00007ffff6dabe0f in ?? () from /usr/lib/libQt5Core.so.5
No symbol table info available.
#5  0x00007ffff67bf422 in start_thread () from /usr/lib/libpthread.so.0
No symbol table info available.
#6  0x00007ffff6a1ebf3 in clone () from /usr/lib/libc.so.6
No symbol table info available.

Thread 1 (Thread 0x7ffff3d20800 (LWP 2433)):
#0  0x00007ffff69dd640 in __tzfile_compute () from /usr/lib/libc.so.6
No symbol table info available.
#1  0x00007ffff69dc57d in __tz_convert () from /usr/lib/libc.so.6
No symbol table info available.
#2  0x00007ffff69daa61 in ranged_convert () from /usr/lib/libc.so.6
No symbol table info available.
#3  0x00007ffff69dadac in __mktime_internal () from /usr/lib/libc.so.6
No symbol table info available.
#4  0x00007ffff6d9fd30 in qMkTime(tm*) () from /usr/lib/libQt5Core.so.5
No symbol table info available.
#5  0x00007ffff6e749ce in ?? () from /usr/lib/libQt5Core.so.5
No symbol table info available.
#6  0x00007ffff6e75068 in ?? () from /usr/lib/libQt5Core.so.5
No symbol table info available.
#7  0x00007ffff6e7516d in ?? () from /usr/lib/libQt5Core.so.5
No symbol table info available.
#8  0x00007ffff6e75620 in ?? () from /usr/lib/libQt5Core.so.5
No symbol table info available.
#9  0x00007ffff6e7784c in QDateTime::setMSecsSinceEpoch(long long) () from /usr/lib/libQt5Core.so.5
No symbol table info available.
#10 0x00007ffff6e79c81 in QDateTime::fromMSecsSinceEpoch(long long, Qt::TimeSpec, int) () from /usr/lib/libQt5Core.so.5

after this, really long repetitive sections are listed. Thanks in advance.

Debian Sid. With nouveau all working good. But after installing legacy 340.108 nvidia driver for my gf9800 i have Segmentation Fault at launching all Qt GUI software. And opposite, Qt works again after uninstalling nvidia driver. But very strange that if i run Qt soft via debugging tools such gdb or strace i have no errors.

gdb ./doomseeker
strace ./doomseeker

Same is with Qbittorrent and 2048-Qt Only one Qt application starting normally - CMake GUI and Audacious Qt theme Segmentation fault

#include 
int main(int argc, char **argv)
{
  QApplication app(argc, argv);
  return 0;
}

Is where any solution to fix this?

- Problem: After doing a pacman -Syu on a system I'm now experiencing that VirtualBox VMs are capable of crashing X11 and dropping me into a console shell. I see this in dmesg: [ 590.841154] VirtualBoxVM: segfault at 0 ip 00007758ecae9444 sp 00007ffd452514f0 error 4 in libQt6Gui.so.6.9. 0[e9444,7758ecae0000+6b0000] likely on CPU 27 (core 43, socket 0) The VM is always able to get booted and started. The guest VM boots into its GUI and then the problem can happen seemingly randomly in an interval I'd estimate to be from a few seconds to 15-20 minutes. - Temporary downgrade "fix": Downgrading (everything, through a custom script to enumerate all recently upgraded packages through pacman.log and downgrading) to packages from December 2024 resolves the issue. However, this is not a viable solution, I cannot run packages that are this old. Moreover, there are many dependencies here, I cannot selectively keep some packages of such an old nature. This appears to happen on all VMs. An example of such a VM is a Linux guest that runs VMSVGA with 3D acceleration disabled. - What system is this? Arch Linux x86-lga1700 6.14.2-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 10 Apr 2025 18:43:59 +0000 x86_64 GNU/Linux ldd (GNU libc) 2.41 VirtualBox Version : 7.1.8-1 - What I've tried: Tried using VBoxSVGA. Same issue. Using virtualbox-bin instead. Same issue, except then it crashes in libQt6GuiVBox.so not libQt6Gui.so.6.9.0 Came across https://bbs.archlinux.org/viewtopic.php?id=299392 and tried creating the symlinks they mention as a "solution", didn't do anything in my case. Running VirtualBox like this: LIBGL_ALWAYS_SOFTWARE=1 virtualbox, crashes in the same manner, segfault in libQt6Gui.so.6.9.0.

Self answered question for people with same problem. After an upgrade of my kali (debian based) I was able to log in and find "**ksplashqml signal segmentation fault**" error crash in a black screen (was the desktop without desktop theme and was able to use win key to open a konsole, settings or whatever software). Similar errors i find but no success: https://www.reddit.com/r/kde/comments/hprunv/bug_ksplashqml_crash_on_boot/ https://askubuntu.com/questions/1393943/ksplashqml-crash-on-startup Kali 6.11 Display manager: sddm (to check try systemctl status display-manager) So every time I try to restart sddm i was getting the same error. I tried to change kde theme (from other posts) with no success cause it was not displayed in the System Settings or not applied editing from config files. Tried dpkg-reconfigure sddm but did nothing (cause i haven't got desktop environment). Last resource was to reinstall kde-plasma-desktop but get the error "**dpkg unsatisfied dependencies**" and tried to fix it with no success (lot of stuff like apt update & apt upgrade apt --fix-broken install and apt clean)

I was going to install my NVIDIA driver of NVIDIA-Linux-x86_64-565.77.run, and it showed > Unable to find the kernel source tree for the currently running kernel. Please make sure you have installed the kernel source files for your kernel and that they are properly configured; on Red Hat Linux systems, for example, be sure you have the 'kernel-source' or 'kernel-devel' RPM installed. If you know the correct kernel source files are installed, you may specify the kernel source path with the '--kernel-source-path' command line option. just like what happened in https://blog.csdn.net/chris_pei/article/details/79203033 . Following the instruction, I tried a simple yum install kernel-devel:

...
  Installing : 1:perl-parent-0.225-244.el7.noarch                                                                                                                                                              45/72 
  Installing : perl-HTTP-Tiny-0.033-3.el7.noarch                                                                                                                                                               46/72 
  Installing : perl-podlators-2.5.1-3.el7.noarch                                                                                                                                                               47/72 
  Installing : perl-Pod-Perldoc-3.20-4.el7.noarch                                                                                                                                                              48/72 
  Installing : 1:perl-Pod-Escapes-1.04-293.el7.noarch                                                                                                                                                          49/72 
  Installing : perl-Encode-2.51-7.el7.x86_64                                                                                                                                                                   50/72 
  Installing : perl-Text-ParseWords-3.29-4.el7.noarch                                                                                                                                                          51/72 
  Installing : perl-Pod-Usage-1.63-3.el7.noarch                                                                                                                                                                52/72 
  Installing : 4:perl-macros-5.16.3-293.el7.x86_64                                                                                                                                                             53/72 
  Installing : perl-Storable-2.45-3.el7.x86_64                                                                                                                                                                 54/72 
  Installing : perl-Exporter-5.68-3.el7.noarch                                                                                                                                                                 55/72 
  Installing : perl-constant-1.27-2.el7.noarch                                                                                                                                                                 56/72 
  Installing : perl-Time-Local-1.2300-2.el7.noarch                                                                                                                                                             57/72 
  Installing : perl-Socket-2.010-4.el7.x86_64                                                                                                                                                                  58/72 
  Installing : perl-Carp-1.26-244.el7.noarch                                                                                                                                                                   59/72 
  Installing : 4:perl-Time-HiRes-1.9725-3.el7.x86_64                                                                                                                                                           60/72 
  Installing : perl-PathTools-3.40-5.el7.x86_64                                                                                                                                                                61/72 
  Installing : perl-Scalar-List-Utils-1.27-248.el7.x86_64                                                                                                                                                      62/72 
  Installing : 1:perl-Pod-Simple-3.28-4.el7.noarch                                                                                                                                                             63/72 
  Installing : perl-File-Temp-0.23.01-3.el7.noarch                                                                                                                                                             64/72 
  Installing : perl-File-Path-2.09-2.el7.noarch                                                                                                                                                                65/72 
  Installing : perl-threads-shared-1.43-6.el7.x86_64                                                                                                                                                           66/72 
  Installing : perl-threads-1.87-4.el7.x86_64                                                                                                                                                                  67/72 
  Installing : perl-Filter-1.49-3.el7.x86_64                                                                                                                                                                   68/72 
  Installing : 4:perl-libs-5.16.3-293.el7.x86_64                                                                                                                                                               69/72 
  Installing : perl-Getopt-Long-2.40-3.el7.noarch                                                                                                                                                              70/72 
  Installing : 4:perl-5.16.3-293.el7.x86_64                                                                                                                                                                    71/72 
  Installing : kernel-devel-3.10.0-957.el7.x86_64                                                                                                                                                              72/72 
Non-fatal POSTIN scriptlet failure in rpm package kernel-devel-3.10.0-957.el7.x86_64
Non-fatal POSTTRANS scriptlet failure in rpm package p11-kit-trust-0.23.5-3.el7.x86_64
Non-fatal POSTTRANS scriptlet failure in rpm package centos-release-7-6.1810.2.el7.centos.x86_64

Installed:
  kernel-devel.x86_64 0:3.10.0-957.el7                                                                                                                                                                               

Dependency Installed:
  basesystem.noarch 0:10.0-7.el7.centos                bash.x86_64 0:4.2.46-31.el7                        centos-release.x86_64 0:7-6.1810.2.el7.centos         findutils.x86_64 1:4.5.11-6.el7                    
  gawk.x86_64 0:4.0.2-4.el7_3.1                        gdbm.x86_64 0:1.10-8.el7                           glibc.x86_64 0:2.17-260.el7                           glibc-common.x86_64 0:2.17-260.el7                 
  gmp.x86_64 1:6.0.0-15.el7                            grep.x86_64 0:2.20-3.el7                           groff-base.x86_64 0:1.22.2-8.el7                      info.x86_64 0:5.1-5.el7                            
  keyutils-libs.x86_64 0:1.5.8-3.el7                   krb5-libs.x86_64 0:1.15.1-34.el7                   libacl.x86_64 0:2.2.51-14.el7                         libattr.x86_64 0:2.4.46-13.el7                     
  libcap.x86_64 0:2.22-9.el7                           libcom_err.x86_64 0:1.42.9-13.el7                  libffi.x86_64 0:3.0.13-18.el7                         libgcc.x86_64 0:4.8.5-36.el7                       
  libselinux.x86_64 0:2.5-14.1.el7                     libsepol.x86_64 0:2.5-10.el7                       libstdc++.x86_64 0:4.8.5-36.el7                       libtasn1.x86_64 0:4.10-1.el7                       
  libverto.x86_64 0:0.2.5-4.el7                        ncurses.x86_64 0:5.9-14.20130511.el7_4             ncurses-base.noarch 0:5.9-14.20130511.el7_4           ncurses-libs.x86_64 0:5.9-14.20130511.el7_4        
  nspr.x86_64 0:4.19.0-1.el7_5                         nss-softokn-freebl.x86_64 0:3.36.0-5.el7_5         nss-util.x86_64 0:3.36.0-1.el7_5                      p11-kit.x86_64 0:0.23.5-3.el7                      
  p11-kit-trust.x86_64 0:0.23.5-3.el7                  pcre.x86_64 0:8.32-17.el7                          perl.x86_64 4:5.16.3-293.el7                          perl-Carp.noarch 0:1.26-244.el7                    
  perl-Encode.x86_64 0:2.51-7.el7                      perl-Exporter.noarch 0:5.68-3.el7                  perl-File-Path.noarch 0:2.09-2.el7                    perl-File-Temp.noarch 0:0.23.01-3.el7              
  perl-Filter.x86_64 0:1.49-3.el7                      perl-Getopt-Long.noarch 0:2.40-3.el7               perl-HTTP-Tiny.noarch 0:0.033-3.el7                   perl-PathTools.x86_64 0:3.40-5.el7                 
  perl-Pod-Escapes.noarch 1:1.04-293.el7               perl-Pod-Perldoc.noarch 0:3.20-4.el7               perl-Pod-Simple.noarch 1:3.28-4.el7                   perl-Pod-Usage.noarch 0:1.63-3.el7                 
  perl-Scalar-List-Utils.x86_64 0:1.27-248.el7         perl-Socket.x86_64 0:2.010-4.el7                   perl-Storable.x86_64 0:2.45-3.el7                     perl-Text-ParseWords.noarch 0:3.29-4.el7           
  perl-Time-HiRes.x86_64 4:1.9725-3.el7                perl-Time-Local.noarch 0:1.2300-2.el7              perl-constant.noarch 0:1.27-2.el7                     perl-libs.x86_64 4:5.16.3-293.el7                  
  perl-macros.x86_64 4:5.16.3-293.el7                  perl-parent.noarch 1:0.225-244.el7                 perl-podlators.noarch 0:2.5.1-3.el7                   perl-threads.x86_64 0:1.87-4.el7                   
  perl-threads-shared.x86_64 0:1.43-6.el7              popt.x86_64 0:1.13-16.el7                          sed.x86_64 0:4.2.2-5.el7                              setup.noarch 0:2.8.71-10.el7                       
  tzdata.noarch 0:2018e-3.el7                          zlib.x86_64 0:1.2.7-18.el7                        

Failed:
  ca-certificates.noarch 0:2018.2.22-70.0.el7_5        chkconfig.x86_64 0:1.7.4-1.el7        coreutils.x86_64 0:8.22-23.el7        filesystem.x86_64 0:3.2-25.el7        openssl-libs.x86_64 1:1.0.2k-16.el7       

Complete!

(Full version in https://blog.csdn.net/Sakura_no_ame/article/details/145215254?sharetype=blogdetail&sharerId=145215254&sharerefer=PC&sharesource=Sakura_no_ame&spm=1011.2480.3001.8118) However, after that most of the commands failed with segment fault (core dumped), even like simple ls, rm, cp and mv, except for some built-in-shell commands like cd, ulimit and history. There are two important hints which I think to be possible to be the cause: 1. My Linux kernel version is 3.10.0-1160.42.2.el7.x86_64, which seems to mismatch with the version I have installed as kernel-devel.x86_64 0:3.10.0-957.el7. 2. I ran the code in a confused state following https://blog.csdn.net/chris_pei/article/details/79203033 :

wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13/linux-headers-4.13.0-041300_4.13.0-041300.201709031731_all.deb 
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13/linux-headers-4.13.0-041300-generic_4.13.0-041300.201709031731_amd64.deb 
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13/linux-image-4.13.0-041300-generic_4.13.0-041300.201709031731_amd64.deb 
sudo dpkg -i *.deb

But I have never made any settings for the boot stuff because I found it unnecessary. So I am eager to know: 1. What caused my Segment fault (core dumped). 2. What should I do to recover my computer without any tools like cp, rm and mv. **What I have tried**: I can upload or download files to /workspace because I am using Jupyter to access my computer. I have tried to upload a simple program to a catch core dumped file so that I can analyze the cause with gdb program core. Unluckily, I have no idea granting execution permissions to the program because whenever I typed a chmod command, it still showed Segment fault (core dumped). I will appreciate any help or advice because it is very important to me. Thank you very much. --- I will provide all of the commands I have typed from history: https://blog.csdn.net/Sakura_no_ame/article/details/145215241?sharetype=blogdetail&sharerId=145215241&sharerefer=PC&sharesource=Sakura_no_ame&spm=1011.2480.3001.8118

New noob here. Using MX Linux, set up Mutt with gmail. Was initially successful. Emails and all. Then at some point when trying to use again, it stuck at 4% giving a segmentation fault. Using gdb it says: Fetching message headers... 6202/132349 (4%) Program received signal SIGSEGV, Segmentation fault. 0x00007ffff7c2ea5f in ?? () from /lib/x86_64-linux-gnu/libtokyocabinet.so.9 (gdb) bt #0 0x00007ffff7c2ea5f in ?? () from /lib/x86_64-linux-gnu/libtokyocabinet.so.9 #1 0x00007ffff7c2fca8 in tcbdbput () from /lib/x86_64-linux-gnu/libtokyocabinet.so.9 #2 0x000055555561e5da in ?? () #3 0x000055555561eded in ?? () #4 0x000055555562dfe3 in ?? () #5 0x000055555562bb1c in ?? () #6 0x000055555562893d in ?? () #7 0x00005555555b774e in ?? () #8 0x000055555556c3ea in ?? () #9 0x00007ffff795cd7a in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #10 0x000055555556d44a in ?? () What do I do?

I am working in an embedded Linux system, and now I want to trigger a core dump from within kernel by using send_sig(task, SIGSEGV, 1). There is a process A having 10 threads, occasionally, there is a kernel oops occurred and at that time, one thread of A is the current process reported by kernel. So I want to dump the core of the process A to find out what happened. So I did followings. 1. Enable core dump in kernel configuration. 2. Running ulimit -c unlimited in init script. 3. echo '/mnt/core.%p.%e' > /proc/sys/kernel/core_pattern. 4. Changed the kernel oops codes to call send_sig(task_A, SIGSEGV, 1) to send SIGSEGV to the process A. Then I tried to reproduce the kernel oops, and I found the log of Segmentation Fault from process A, but I did NOT see any core dumped in /mnt/. If I changed the process A to access 0 of address, it can trigger a core dump correctly. Why it failed to dump core from my kernel codes (the process A did is killed by SIGSEGV)? And how can I trigger a core-dump to capture the user space context in the case of kernel oops???

In a remote system to which I don't have console access, which I'm connecting through ssh, I broke the sudo installation and now I'm not able to use it at all, and I'm not able to restart as a root. The command I ran was:

-sh
sudo mv /lib/x86_64-linux-gnu/libm.so.6 /lib/x86_64-linux-gnu/libm.so.6_org

Everytime I do sudo it says segmentation fault, for example:

-shellsession
~$ sudo -s
Segmentation fault (core dumped)

As specific cases, - id works: uid=1479554(s1474782) gid=100(users) groups=100(users),27(sudo),999(docker) - sh works as well - sudo id doesn't work: sudo id Segmentation fault (core dumped) - su s1474782 -c id doesn't work: sudo id Segmentation fault (core dumped) I was updating some libraries and I think I broke the libm.so.6 library, however I don't see sudo depending on it:

-shellsession
ldd $(which sudo)
    linux-vdso.so.1 =>  (0x00007ffd7ef9e000)
    libaudit.so.1 => /lib/x86_64-linux-gnu/libaudit.so.1 (0x00007f139de21000)
    libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x00007f139dbff000)
    libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x00007f139d9fc000)
    libsudo_util.so.0 => /usr/lib/sudo/libsudo_util.so.0 (0x00007f139d7e8000)
    libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f139d41e000)
    libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f139d1ae000)
    libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f139cfaa000)
    /lib64/ld-linux-x86-64.so.2 (0x00007f139e26b000)
    libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f139cd8d000)

Any advice how to solve this? I can just re-install sudo?

Using current debian release, Linux debian 6.1.0-25-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.106-3 (2024-08-26) x86_64 GNU/Linux my session aborted and returned after a while to the login screen when I was using _IntelliJ_. A look at /var/log/syslog shows this extract:

2024-09-09T04:46:35.669115+02:00 debian /usr/libexec/gdm-x-session: (EE)
2024-09-09T04:46:35.669256+02:00 debian /usr/libexec/gdm-x-session: (EE) Backtrace:
2024-09-09T04:46:35.669593+02:00 debian /usr/libexec/gdm-x-session: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x558ca2437f69]
2024-09-09T04:46:35.669987+02:00 debian /usr/libexec/gdm-x-session: (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x40) [0x7f11e885b050]
2024-09-09T04:46:35.670951+02:00 debian /usr/libexec/gdm-x-session: (EE) 2: /usr/lib/xorg/modules/drivers/nvidia_drv.so (nvidiaUnlock+0x44218c) [0x7f11e7cab06c]
2024-09-09T04:46:35.670989+02:00 debian /usr/libexec/gdm-x-session: (EE)
2024-09-09T04:46:35.671013+02:00 debian /usr/libexec/gdm-x-session: (EE) Segmentation fault at address 0xb8
2024-09-09T04:46:35.671160+02:00 debian /usr/libexec/gdm-x-session: (EE)
2024-09-09T04:46:35.671177+02:00 debian /usr/libexec/gdm-x-session: Fatal server error:
2024-09-09T04:46:35.671195+02:00 debian /usr/libexec/gdm-x-session: (EE) Caught signal 11 (Segmentation fault). Server aborting
2024-09-09T04:46:35.671213+02:00 debian /usr/libexec/gdm-x-session: (EE)
2024-09-09T04:46:35.671228+02:00 debian /usr/libexec/gdm-x-session: (EE)
2024-09-09T04:46:35.671242+02:00 debian /usr/libexec/gdm-x-session: Please consult the The X.Org Foundation support
2024-09-09T04:46:35.671267+02:00 debian /usr/libexec/gdm-x-session: #011 at http://wiki.x.org 
2024-09-09T04:46:35.671289+02:00 debian /usr/libexec/gdm-x-session:  for help.
2024-09-09T04:46:35.671307+02:00 debian /usr/libexec/gdm-x-session: (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information.
2024-09-09T04:46:35.671321+02:00 debian /usr/libexec/gdm-x-session: (EE)
2024-09-09T04:46:35.780532+02:00 debian /usr/libexec/gdm-x-session: (EE) Server terminated with error (1). Closing log file.
2024-09-09T04:46:35.785601+02:00 debian at-spi-bus-launcher: X connection to :1 broken (explicit kill or server shutdown).
2024-09-09T04:46:35.787762+02:00 debian systemd: org.gnome.SettingsDaemon.XSettings.service: Main process exited, code=exited, status=1/FAILURE
2024-09-09T04:46:35.834406+02:00 debian gnome-shell: Invalid temperature from gsd-color: 0 K
2024-09-09T04:46:35.834903+02:00 debian firefox-esr.desktop: Exiting due to channel error.
2024-09-09T04:46:35.835451+02:00 debian firefox-esr.desktop: Exiting due to channel error.
2024-09-09T04:46:35.835499+02:00 debian systemd: org.gnome.SettingsDaemon.Color.service: Main process exited, code=exited, status=1/FAILURE
2024-09-09T04:46:35.835680+02:00 debian firefox-esr.desktop: Exiting due to channel error.
2024-09-09T04:46:35.835873+02:00 debian firefox-esr.desktop: Exiting due to channel

Is that something I should report to Debian team as an issue? --- more details here:

2024-09-09T04:46:35.520671+02:00 debian jetbrains-idea.desktop: Warning: Not allowed as a service: com.jetbrains.RoundedCornersManager
2024-09-09T04:46:35.521140+02:00 debian jetbrains-idea.desktop: #011at com.jetbrains.JBR$RoundedCornersManager__Holder.(JBR.java:514)
2024-09-09T04:46:35.521167+02:00 debian jetbrains-idea.desktop: #011at com.jetbrains.JBR.isRoundedCornersManagerSupported(JBR.java:524)
2024-09-09T04:46:35.521191+02:00 debian jetbrains-idea.desktop: #011at com.intellij.ui.WindowRoundedCornersManager.isAvailable(WindowRoundedCornersManager.java:36)
2024-09-09T04:46:35.521210+02:00 debian jetbrains-idea.desktop: #011at com.intellij.ui.popup.AbstractPopup.show(AbstractPopup.java:1033)
2024-09-09T04:46:35.521228+02:00 debian jetbrains-idea.desktop: #011at com.intellij.ui.popup.AbstractPopup.show(AbstractPopup.java:654)
2024-09-09T04:46:35.521247+02:00 debian jetbrains-idea.desktop: #011at com.intellij.ui.popup.AbstractPopup.showInBestPositionFor(AbstractPopup.java:761)
2024-09-09T04:46:35.521270+02:00 debian jetbrains-idea.desktop: #011at com.intellij.openapi.editor.EditorMouseHoverPopupManager.showHintInEditor(EditorMouseHoverPopupManager.java:257)
2024-09-09T04:46:35.521289+02:00 debian jetbrains-idea.desktop: #011at com.intellij.openapi.editor.EditorMouseHoverPopupManager.lambda$scheduleProcessing$3(EditorMouseHoverPopupManager.java:194)
2024-09-09T04:46:35.521313+02:00 debian jetbrains-idea.desktop: #011at com.intellij.util.concurrency.ContextRunnable.run(ContextRunnable.java:27)
2024-09-09T04:46:35.521344+02:00 debian jetbrains-idea.desktop: #011at com.intellij.openapi.application.TransactionGuardImpl.runWithWritingAllowed(TransactionGuardImpl.java:229)
2024-09-09T04:46:35.521373+02:00 debian jetbrains-idea.desktop: #011at com.intellij.openapi.application.TransactionGuardImpl.access$100(TransactionGuardImpl.java:22)
2024-09-09T04:46:35.521395+02:00 debian jetbrains-idea.desktop: #011at com.intellij.openapi.application.TransactionGuardImpl$1.run(TransactionGuardImpl.java:191)
2024-09-09T04:46:35.521414+02:00 debian jetbrains-idea.desktop: #011at com.intellij.openapi.application.impl.AnyThreadWriteThreadingSupport.runIntendedWriteActionOnCurrentThread$lambda$1(AnyThreadWriteThreadingSupport.kt:184)
2024-09-09T04:46:35.521432+02:00 debian jetbrains-idea.desktop: #011at com.intellij.openapi.application.impl.AnyThreadWriteThreadingSupport.runWriteIntentReadAction(AnyThreadWriteThreadingSupport.kt:84)
2024-09-09T04:46:35.521455+02:00 debian jetbrains-idea.desktop: #011at com.intellij.openapi.application.impl.AnyThreadWriteThreadingSupport.runIntendedWriteActionOnCurrentThread(AnyThreadWriteThreadingSupport.kt:183)
2024-09-09T04:46:35.521473+02:00 debian jetbrains-idea.desktop: #011at com.intellij.openapi.application.impl.ApplicationImpl.runIntendedWriteActionOnCurrentThread(ApplicationImpl.java:836)
2024-09-09T04:46:35.521514+02:00 debian jetbrains-idea.desktop: #011at com.intellij.openapi.application.impl.ApplicationImpl$2.run(ApplicationImpl.java:424)
2024-09-09T04:46:35.521603+02:00 debian jetbrains-idea.desktop: #011at com.intellij.openapi.application.impl.AnyThreadWriteThreadingSupport.runWithImplicitRead(AnyThreadWriteThreadingSupport.kt:122)
2024-09-09T04:46:35.521623+02:00 debian jetbrains-idea.desktop: #011at com.intellij.openapi.application.impl.ApplicationImpl.runWithImplicitRead(ApplicationImpl.java:1162)
2024-09-09T04:46:35.521640+02:00 debian jetbrains-idea.desktop: #011at com.intellij.openapi.application.impl.FlushQueue.doRun(FlushQueue.java:78)
2024-09-09T04:46:35.521658+02:00 debian jetbrains-idea.desktop: #011at com.intellij.openapi.application.impl.FlushQueue.runNextEvent(FlushQueue.java:119)
2024-09-09T04:46:35.521676+02:00 debian jetbrains-idea.desktop: #011at com.intellij.openapi.application.impl.FlushQueue.flushNow(FlushQueue.java:41)
2024-09-09T04:46:35.521693+02:00 debian jetbrains-idea.desktop: #011at java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:318)
2024-09-09T04:46:35.521728+02:00 debian jetbrains-idea.desktop: #011at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:781)
2024-09-09T04:46:35.521746+02:00 debian jetbrains-idea.desktop: #011at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:728)
2024-09-09T04:46:35.521779+02:00 debian jetbrains-idea.desktop: #011at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:722)
2024-09-09T04:46:35.521798+02:00 debian jetbrains-idea.desktop: #011at java.base/java.security.AccessController.doPrivileged(AccessController.java:400)
2024-09-09T04:46:35.521819+02:00 debian jetbrains-idea.desktop: #011at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:87)
2024-09-09T04:46:35.521842+02:00 debian jetbrains-idea.desktop: #011at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:750)
2024-09-09T04:46:35.521877+02:00 debian jetbrains-idea.desktop: #011at com.intellij.ide.IdeEventQueue.defaultDispatchEvent(IdeEventQueue.kt:696)
2024-09-09T04:46:35.521896+02:00 debian jetbrains-idea.desktop: #011at com.intellij.ide.IdeEventQueue._dispatchEvent$lambda$16(IdeEventQueue.kt:590)
2024-09-09T04:46:35.521961+02:00 debian jetbrains-idea.desktop: #011at com.intellij.openapi.application.impl.AnyThreadWriteThreadingSupport.runWithoutImplicitRead(AnyThreadWriteThreadingSupport.kt:117)
2024-09-09T04:46:35.522004+02:00 debian jetbrains-idea.desktop: #011at com.intellij.ide.IdeEventQueue._dispatchEvent(IdeEventQueue.kt:590)
2024-09-09T04:46:35.522042+02:00 debian jetbrains-idea.desktop: #011at com.intellij.ide.IdeEventQueue.access$_dispatchEvent(IdeEventQueue.kt:73)
2024-09-09T04:46:35.522132+02:00 debian jetbrains-idea.desktop: #011at com.intellij.ide.IdeEventQueue$dispatchEvent$processEventRunnable$1$1$1$1.compute(IdeEventQueue.kt:357)
2024-09-09T04:46:35.522153+02:00 debian jetbrains-idea.desktop: #011at com.intellij.ide.IdeEventQueue$dispatchEvent$processEventRunnable$1$1$1$1.compute(IdeEventQueue.kt:356)
2024-09-09T04:46:35.522195+02:00 debian jetbrains-idea.desktop: #011at com.intellij.openapi.progress.impl.CoreProgressManager.computePrioritized(CoreProgressManager.java:843)
2024-09-09T04:46:35.522243+02:00 debian jetbrains-idea.desktop: #011at com.intellij.ide.IdeEventQueue$dispatchEvent$processEventRunnable$1$1$1.invoke(IdeEventQueue.kt:356)
2024-09-09T04:46:35.522288+02:00 debian jetbrains-idea.desktop: #011at com.intellij.ide.IdeEventQueue$dispatchEvent$processEventRunnable$1$1$1.invoke(IdeEventQueue.kt:351)
2024-09-09T04:46:35.522329+02:00 debian jetbrains-idea.desktop: #011at com.intellij.ide.IdeEventQueueKt$performActivity$runnableWithWIL$1.invoke$lambda$0(IdeEventQueue.kt:1035)
2024-09-09T04:46:35.522360+02:00 debian jetbrains-idea.desktop: #011at com.intellij.openapi.application.WriteIntentReadAction.lambda$run$0(WriteIntentReadAction.java:24)
2024-09-09T04:46:35.522396+02:00 debian jetbrains-idea.desktop: #011at com.intellij.openapi.application.impl.AnyThreadWriteThreadingSupport.runWriteIntentReadAction(AnyThreadWriteThreadingSupport.kt:84)
2024-09-09T04:46:35.522431+02:00 debian jetbrains-idea.desktop: #011at com.intellij.openapi.application.impl.ApplicationImpl.runWriteIntentReadAction(ApplicationImpl.java:910)
2024-09-09T04:46:35.522457+02:00 debian jetbrains-idea.desktop: #011at com.intellij.openapi.application.WriteIntentReadAction.compute(WriteIntentReadAction.java:55)
2024-09-09T04:46:35.522493+02:00 debian jetbrains-idea.desktop: #011at com.intellij.openapi.application.WriteIntentReadAction.run(WriteIntentReadAction.java:23)
2024-09-09T04:46:35.522554+02:00 debian jetbrains-idea.desktop: #011at com.intellij.ide.IdeEventQueueKt$performActivity$runnableWithWIL$1.invoke(IdeEventQueue.kt:1035)
2024-09-09T04:46:35.522609+02:00 debian jetbrains-idea.desktop: #011at com.intellij.ide.IdeEventQueueKt$performActivity$runnableWithWIL$1.invoke(IdeEventQueue.kt:1035)
2024-09-09T04:46:35.522649+02:00 debian jetbrains-idea.desktop: #011at com.intellij.ide.IdeEventQueueKt.performActivity$lambda$1(IdeEventQueue.kt:1036)
2024-09-09T04:46:35.522708+02:00 debian jetbrains-idea.desktop: #011at com.intellij.openapi.application.TransactionGuardImpl.performActivity(TransactionGuardImpl.java:106)
2024-09-09T04:46:35.522749+02:00 debian jetbrains-idea.desktop: #011at com.intellij.ide.IdeEventQueueKt.performActivity(IdeEventQueue.kt:1036)
2024-09-09T04:46:35.522800+02:00 debian jetbrains-idea.desktop: #011at com.intellij.ide.IdeEventQueue.dispatchEvent$lambda$10(IdeEventQueue.kt:351)
2024-09-09T04:46:35.522837+02:00 debian jetbrains-idea.desktop: #011at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.kt:397)
2024-09-09T04:46:35.522883+02:00 debian jetbrains-idea.desktop: #011at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:207)
2024-09-09T04:46:35.522926+02:00 debian jetbrains-idea.desktop: #011at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:128)
2024-09-09T04:46:35.522970+02:00 debian jetbrains-idea.desktop: #011at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:117)
2024-09-09T04:46:35.523009+02:00 debian jetbrains-idea.desktop: #011at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:113)
2024-09-09T04:46:35.523053+02:00 debian jetbrains-idea.desktop: #011at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:105)
2024-09-09T04:46:35.523121+02:00 debian jetbrains-idea.desktop: #011at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:92)
2024-09-09T04:46:35.669115+02:00 debian /usr/libexec/gdm-x-session: (EE)
2024-09-09T04:46:35.669256+02:00 debian /usr/libexec/gdm-x-session: (EE) Backtrace:
2024-09-09T04:46:35.669593+02:00 debian /usr/libexec/gdm-x-session: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x558ca2437f69]
2024-09-09T04:46:35.669987+02:00 debian /usr/libexec/gdm-x-session: (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x40) [0x7f11e885b050]
2024-09-09T04:46:35.670951+02:00 debian /usr/libexec/gdm-x-session: (EE) 2: /usr/lib/xorg/modules/drivers/nvidia_drv.so (nvidiaUnlock+0x44218c) [0x7f11e7cab06c]
2024-09-09T04:46:35.670989+02:00 debian /usr/libexec/gdm-x-session: (EE)
2024-09-09T04:46:35.671013+02:00 debian /usr/libexec/gdm-x-session: (EE) Segmentation fault at address 0xb8
2024-09-09T04:46:35.671160+02:00 debian /usr/libexec/gdm-x-session: (EE)
2024-09-09T04:46:35.671177+02:00 debian /usr/libexec/gdm-x-session: Fatal server error:
2024-09-09T04:46:35.671195+02:00 debian /usr/libexec/gdm-x-session: (EE) Caught signal 11 (Segmentation fault). Server aborting
2024-09-09T04:46:35.671213+02:00 debian /usr/libexec/gdm-x-session: (EE)
2024-09-09T04:46:35.671228+02:00 debian /usr/libexec/gdm-x-session: (EE)
2024-09-09T04:46:35.671242+02:00 debian /usr/libexec/gdm-x-session: Please consult the The X.Org Foundation support
2024-09-09T04:46:35.671267+02:00 debian /usr/libexec/gdm-x-session: #011 at http://wiki.x.org 
2024-09-09T04:46:35.671289+02:00 debian /usr/libexec/gdm-x-session:  for help.
2024-09-09T04:46:35.671307+02:00 debian /usr/libexec/gdm-x-session: (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information.
2024-09-09T04:46:35.671321+02:00 debian /usr/libexec/gdm-x-session: (EE)
2024-09-09T04:46:35.780532+02:00 debian /usr/libexec/gdm-x-session: (EE) Server terminated with error (1). Closing log file.
2024-09-09T04:46:35.785601+02:00 debian at-spi-bus-launcher: X connection to :1 broken (explicit kill or server shutdown).
2024-09-09T04:46:35.787762+02:00 debian systemd: org.gnome.SettingsDaemon.XSettings.service: Main process exited, code=exited, status=1/FAILURE
2024-09-09T04:46:35.834406+02:00 debian gnome-shell: Invalid temperature from gsd-color: 0 K
2024-09-09T04:46:35.834903+02:00 debian firefox-esr.desktop: Exiting due to channel error.
2024-09-09T04:46:35.835451+02:00 debian firefox-esr.desktop: Exiting due to channel error.
2024-09-09T04:46:35.835499+02:00 debian systemd: org.gnome.SettingsDaemon.Color.service: Main process exited, code=exited, status=1/FAILURE
2024-09-09T04:46:35.835680+02:00 debian firefox-esr.desktop: Exiting due to channel error.
2024-09-09T04:46:35.835873+02:00 debian firefox-esr.desktop: Exiting due to channel error.
2024-09-09T04:46:35.836030+02:00 debian firefox-esr.desktop: Exiting due to channel error.
2024-09-09T04:46:35.836165+02:00 debian firefox-esr.desktop: Exiting due to channel error.
2024-09-09T04:46:35.836311+02:00 debian firefox-esr.desktop: Exiting due to channel error.
2024-09-09T04:46:35.836361+02:00 debian systemd: org.gnome.SettingsDaemon.Keyboard.service: Main process exited, code=exited, status=1/FAILURE
2024-09-09T04:46:35.836538+02:00 debian firefox-esr.desktop: Exiting due to channel error.
2024-09-09T04:46:35.836760+02:00 debian firefox-esr.desktop: Exiting due to channel error.
2024-09-09T04:46:35.836911+02:00 debian firefox-esr.desktop: Exiting due to channel error.
2024-09-09T04:46:35.837319+02:00 debian systemd: org.gnome.SettingsDaemon.MediaKeys.service: Main process exited, code=exited, status=1/FAILURE
2024-09-09T04:46:35.843834+02:00 debian systemd: org.gnome.SettingsDaemon.Power.service: Main process exited, code=exited, status=1/FAILURE
2024-09-09T04:46:35.844691+02:00 debian systemd: tmp-.mount_jetbraR7wcFm.mount: Deactivated successfully.
2024-09-09T04:46:35.844845+02:00 debian systemd: org.gnome.SettingsDaemon.Wacom.service: Main process exited, code=exited, status=1/FAILURE
2024-09-09T04:46:35.845473+02:00 debian systemd: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE
2024-09-09T04:46:35.845613+02:00 debian systemd: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
2024-09-09T04:46:35.845852+02:00 debian systemd: xdg-desktop-portal-gtk.service: Consumed 4.527s CPU time.
2024-09-09T04:46:35.846233+02:00 debian systemd: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE
2024-09-09T04:46:35.846268+02:00 debian systemd: gnome-terminal-server.service: Failed with result 'exit-code'.
2024-09-09T04:46:35.846403+02:00 debian systemd: gnome-terminal-server.service: Consumed 2.869s CPU time.
2024-09-09T04:46:35.846550+02:00 debian systemd: org.gnome.SettingsDaemon.XSettings.service: Failed with result 'exit-code'.
2024-09-09T04:46:35.846690+02:00 debian systemd: org.gnome.SettingsDaemon.XSettings.service: Consumed 3.165s CPU time.
2024-09-09T04:46:35.848339+02:00 debian systemd: org.gnome.SettingsDaemon.Color.service: Failed with result 'exit-code'.
2024-09-09T04:46:35.848424+02:00 debian systemd: org.gnome.SettingsDaemon.Color.service: Consumed 3.330s CPU time.
2024-09-09T04:46:35.848580+02:00 debian systemd: org.gnome.SettingsDaemon.Keyboard.service: Failed with result 'exit-code'.
2024-09-09T04:46:35.848736+02:00 debian systemd: org.gnome.SettingsDaemon.Keyboard.service: Consumed 2.588s CPU time.
2024-09-09T04:46:35.848881+02:00 debian systemd: org.gnome.SettingsDaemon.MediaKeys.service: Failed with result 'exit-code'.
2024-09-09T04:46:35.849026+02:00 debian systemd: org.gnome.SettingsDaemon.MediaKeys.service: Consumed 4.134s CPU time.
2024-09-09T04:46:35.849171+02:00 debian systemd: org.gnome.SettingsDaemon.Power.service: Failed with result 'exit-code'.
2024-09-09T04:46:35.849316+02:00 debian systemd: org.gnome.SettingsDaemon.Power.service: Consumed 4.468s CPU time.
2024-09-09T04:46:35.849454+02:00 debian systemd: org.gnome.SettingsDaemon.Wacom.service: Failed with result 'exit-code'.

I have Linux Mint 21.3 Cinnamon running and installed Android studio including its emulator. Now a lot of people run into all sorts of problems when trying to actually emulate a device, but for me the emulator command even crashes when I just want to display the help: ./emulator -help yields: [3326:3326:20240828,191915.586852:ERROR elf_dynamic_array_reader.h:64] tag not found [3326:3326:20240828,191915.587974:WARNING process_reader_linux.cc:144] no stack mapping Segmentation fault (core dumped) The respective journalctl -f looks like this: Process 3324 (emulator) of user 1001 dumped core. Found module /home/arbeit/Android/Sdk/emulator/emulator with build-id: 4fc738dc76d85942c37e0bb2f4098472223d8afe Found module /home/arbeit/Android/Sdk/emulator/lib64/libprotobuf.so.32 without build-id. Found module /home/arbeit/Android/Sdk/emulator/lib64/libglib2_linux-x86_64.so with build-id: 4dbed67c441c1aacd68825484729a0e97fbb1d9a Found module /home/arbeit/Android/Sdk/emulator/lib64/libandroid-emu-base-logging.so with build-id: 445d7534bc1161b0704e8389cd9a91735544ba1f Found module /home/arbeit/Android/Sdk/emulator/lib64/libc++.so.1 without build-id. Found module /home/arbeit/Android/Sdk/emulator/lib64/libandroid-emu-agents.so with build-id: f0465a90155794889277a0e5b93b6cdd4696ec3e Found module /home/arbeit/Android/Sdk/emulator/lib64/libandroid-emu-curl.so with build-id: e2184f4ff3fbc97aff738a3f5a6ad34a6c913733 Found module /home/arbeit/Android/Sdk/emulator/lib64/libandroid-emu-metrics.so with build-id: 8464276cb0dad741cbaa5327329df28f77387be4 Found module /home/arbeit/Android/Sdk/emulator/lib64/libandroid-emu-protos.so with build-id: 577111c450913ff1c224ae5fe41e69869558f9cd Found module linux-vdso.so.1 with build-id: 9b79168bfbd8aeae8ff8785c33d8386d7d9df1ad Found module libmd.so.0 with build-id: cd2d2f71b3967ebde30e2aa43b8eb63339020c06 Found module libbsd.so.0 with build-id: 9a6c72469251e2feb63e175ef5cb944ce6e00df3 Found module libXext.so.6 with build-id: 9fb1880e02dfa11a8c39cd1a170109de08302059 Found module libXdmcp.so.6 with build-id: 6b60f99504aa1d3999ea02a14366d1a39d6c5dcf Found module libXau.so.6 with build-id: 7089b383cacbfc1760634a3be19a923e51fe3315 Found module libstdc++.so.6 with build-id: e37fe1a879783838de78cbc8c80621fa685d58a2 Found module libXi.so.6 with build-id: 8ff5a3ac871a90fd9d0a7917c61f748a41c6b5ee Found module libxcb.so.1 with build-id: 1bef862a339557aa16c34c7a4b27f8f3aea90517 Found module ld-linux-x86-64.so.2 with build-id: 4186944c50f8a32b47d74931e3f512b811813b64 Found module libc.so.6 with build-id: 490fef8403240c91833978d494d39e537409b92e Found module libgcc_s.so.1 with build-id: e3a44e0da9c6e835d293ed8fd2882b4c4a87130c Found module libm.so.6 with build-id: a508ec5d8bf12fb7fd08204e0f87518e5cd0b102 Found module libpthread.so.0 with build-id: 81f46d553e2f7c999e43c3eede73a822bc8d5d93 Found module librt.so.1 with build-id: fa3a0740c79389792000620954a14ee7c2126aa0 Found module libdl.so.2 with build-id: 6f6fe1a24b7b981e11c9a3373b806d3496d4d9d4 Found module libX11.so.6 with build-id: 37a5d7bbb78e3a99ea8376a7c80ea0c62fe06494 Found module libAppProtection.so with build-id: fd8d0810c960df183049686bfa56f88d1f4a481d Stack trace of thread 3324: #0 0x00007f5ebd2d5e57 _int_malloc (libc.so.6 + 0xa3e57) #1 0x00007f5ebd2d7262 __GI___libc_malloc (libc.so.6 + 0xa5262) #2 0x00007f5ebda110e5 n/a (/home/arbeit/Android/Sdk/emulator/lib64/libc++.so.1 + 0xb50e5) To be honest none of these infos help me much, which of this can I actually use to find out what's wrong and fix it? Another detail about this: the exact same installation of the emulator on the same Linux Mint installation used to work flawlessly and now it stopped, so I suspect this might have something to do with some update of Linux Mint or its libraries that happened in between. I'd be grateful for any ideas on what to try to find out what's wrong here.

I'm a chemist using a computational chemistry software called **Gaussrate**, and I'm encountering a segmentation fault that I don't know how to resolve. I have very limited knowledge of programming or debugging, so I'm seeking guidance on how to diagnose and fix this issue. Below is the error message and backtrace that I received: Program received signal SIGSEGV: Segmentation fault - invalid memory reference. Backtrace for this error: #0 0x149091fee171 in ??? #1 0x149091fed313 in ??? #2 0x14909125db4f in ??? #3 0x4c9b9a in ??? #4 0x4d9860 in ??? #5 0x4f8827 in ??? #6 0x50692d in ??? #7 0x506ac1 in ??? #8 0x149091249d84 in ??? #9 0x401a7d in ??? #10 0xffffffffffffffff in ??? Segmentation fault (core dumped) **Details:** **Operating System:** Running on a Linux environment **Context:** The segmentation fault occurs during the execution of a scientific computation in Gaussrate. **Questions**: 1. As a chemist with no programming experience, what tools or methods can I use to understand where the segmentation fault is occurring? 2. Based on the backtrace, what could be the likely causes of this segmentation fault? Are there common issues related to invalid memory references that I should check? 4. Any general advice on how to handle and debug segmentation faults on Linux, especially for someone without a programming background, would be greatly appreciated. Thank you in advance for your help!

I am working on an embedded Linux system (kernel-5.10.24), the CPU is 32bit MIPs. The applications run in the system may trigger invalid memory access, which will be shot by a SIGSEGV from kernel, and the kernel _may_ dump some logs as follows,

[    5.464129] do_page_fault(): sending SIGSEGV to testsegv for invalid read access from 0000001c
[    5.464144] epc = 0041e118 in testsegv[400000+668000]
[    5.464173] ra  = 00661010 in testsegv[400000+668000]

This log is too simple to triage the problem. So I am trying to do some backtracing in kernel by adding show_regs() into the mm/fault.c and I can got following logs when hit error.

[  185.408332] do_page_fault(): sending SIGSEGV to segv for invalid write access to 00000000
[  185.418592] epc = 0040065c in segv[400000+1000]
[  185.423642] ra  = 00400654 in segv[400000+1000]
[  185.428349] CPU: 1 PID: 1235 Comm: segv Not tainted 5.10.24 #17
[  185.434760] $ 0   : 00000000 00000001 00000000 00000063
[  185.440325] $ 4   : 77e7953c 00c8a190 ffffffff 00000000
[  185.445742] $ 8   : 00000000 00000000 00000001 68736172
[  185.451338] $12   : 0000000d 00000080 00000000 00000000
[  185.456755] $16   : 7faf6564 77ecaf10 004007a0 00000002
[  185.462340] $20   : 00000000 77ec6508 77ecb408 00400714
[  185.467748] $24   : 00000000 77d38a60
[  185.473200] $28   : 77e7ee30 7faf63d0 7faf63d0 00400654
[  185.478712] Hi    : 00000013
[  185.481717] Lo    : 00000000
[  185.484774] epc   : 0040065c 0x40065c
[  185.488555] ra    : 00400654 0x400654
[  185.492383] Status: 04001c13 USER EXL IE
[  185.496639] Cause : 0880000c (ExcCode 03)
[  185.500797] BadVA : 00000000
[  185.508620] CPU: 1 PID: 1235 Comm: segv Not tainted 5.10.24 #17
[  185.514826] Stack : 80bb0000 80092358 00000000 00000000 80a8ee08 8160f950 81deb528 80095370
[  185.523482]         00000000 00000000 00000000 7b699e72 825dbe6c 00000001 825dbe00 7b699e72
[  185.532132]         00000000 00000000 80a74f30 825dbcc0 000001cf 825dbcd4 00000000 00001388
[  185.540785]         1e50ef51 825dbcd3 ffffffff 00000030 80b90000 80000000 00000000 80a70000
[  185.549432]         00000001 00000001 8160f900 8160f950 00000000 00000000 2000e098 80c40004
[  185.558081]         ...
[  185.560613] Call Trace:
[  185.563149] [] show_stack+0x94/0x12c
[  185.567745] [] dump_stack+0xac/0xe8
[  185.572253] [] do_page_fault+0x2d4/0x510
[  185.577211] [] tlb_do_page_fault_1+0x118/0x120

It showed the backtrace in kernel space not the user space. So is there a way to get the backtrace of user space in Linux kernel in this case? (IIRC, X86 can dump something more in kernel space). ## Updated with my testing codes in kernel. I added some codes in mm/fault.c.

unsigned long user_unwind_stack(unsigned long *sp,
        unsigned long pc, unsigned long *ra)
{
    struct mips_frame_info info;
//  unsigned long size, ofs;
    int leaf;
    unsigned long stackinst[0x20] = {0xa5};

    int rc = copy_from_user(stackinst, (void *)(*sp), sizeof(stackinst));
printk("XXXXXXXXXXXXXXXXXXXXXX %s, %d, sp:%lx, rc=%d\n", __func__, __LINE__, *sp, rc);
    for (leaf = 0; leaf regs;
    unsigned long ra = regs->regs;
    unsigned long pc = regs->cp0_epc;
    int count = 0;
    printk("user thread pc%d:0x%lx, sp:0x%lx\n", count++, pc, sp);
    pc = user_unwind_stack(&sp, pc, &ra);

    return 0;
}

    if (user_mode(regs)) {
        mytest_dump_backtrace(regs); /// Call my backtrace codes.
        tsk->thread.cp0_badvaddr = address;
        tsk->thread.error_code = write;

And what I got are

[    9.484609] user thread pc0:0x40065c, sp:0x7fbd5be0
[    9.491495] XXXXXXXXXXXXXXXXXXXXXX user_unwind_stack, 238, sp:7fbd5be0, rc=0
[    9.498835] 7fbd5be0: 00000001 00000000 77E1EE30 77E62F88
[    9.504844] 7fbd5be4: 77C98080 77C6BDCC 00000000 77E64F10
[    9.510726] 7fbd5be8: 7FBD5C08 00400694 00000000 77E61508
[    9.516407] 7fbd5bec: 77E65408 00400714 7FBD5C48 77CA3B30
[    9.522269] 7fbd5bf0: 7FBD5C28 004006F8 7FBD5EB0 7FBD5D74
[    9.527947] 7fbd5bf4: 00000001 77E16BC8 77E1EE30 00400788
[    9.533702] 7fbd5bf8: 7FBD5C48 00400794 00000001 0F6B5934
[    9.539462] 7fbd5bfc: 7FBD5C4C 00000000 77E1EE30 00000000
[    9.545202] XXXXXXXXXXXXXXXXXXXXXX user_unwind_stack, 248

From the return value 0 of copy_from_user, it seemed it failed to copy/read process stack..... What is the wrong with the code?

When I open (gnome) terminal, nothing happens, no error no nothing. I've tried uninstalling it and rebooting followed by a reinstall and all the different combinations of that. I'm able to install and run 'Contour' terminal just fine but I'm not really sure what commands I could run to solve this issue. No disrespect to Contour but I'd like my gnome-terminal to work. I installed Fedora 40 a few weeks ago fresh and I haven't touched it since then. I think the only thing I did that could have potentially sparked an issue would be that I wanted to change to zsh for my terminal. I think this was the command I used chsh -s $(which zsh). If memory serves it didn't seem to do anything straight away. Fedora is the first time I've stepped outside the debian based distros but I did find the program called _logs_ and it does seem to be recording something every time I try to open the terminal.

gnome-terminal-: segfault at 7fadb2a4fa56 ip 00007faa772039b1 sp 00007ffd2cde1978 error 4 in libgobject-2.0.so.0.8000.3[7faa771d5000+38000] likely on CPU 4 (core 5, socket 0)

I'm not really sure how to proceed. Any help or advice would be greatly appreciated.

So I have a TL-MR3220v2 router, which has Openwrt installed, this device only has a 4mb flash so I'm trying to get extroot setup on a USB, to increase disk space. My first attempt I tried using a FAT32 FS, which I was able to get mounted and transfer files, but I quickly realized that this FS would not work as a linux root because of permissions, symlinks, and such. So I tried again this time with a ext4 formatted usb. So I then try to mount this partition onto my device, but every time it results in a 'segmentation fault' with the following in my dmesg log: [ 1146.920000] usb 1-1: new high-speed USB device number 3 using ehci-platform [ 1147.070000] usb-storage 1-1:1.0: USB Mass Storage device detected [ 1147.090000] scsi host1: usb-storage 1-1:1.0 [ 1148.390000] scsi 1:0:0:0: Direct-Access Lexar USB Flash Drive 1100 PQ: 0 ANSI: 4 [ 1148.400000] sd 1:0:0:0: [sda] 31258624 512-byte logical blocks: (16.0 GB/14.9 GiB) [ 1148.410000] sd 1:0:0:0: [sda] Write Protect is off [ 1148.420000] sd 1:0:0:0: [sda] Mode Sense: 43 00 00 00 [ 1148.420000] sd 1:0:0:0: [sda] No Caching mode page found [ 1148.430000] sd 1:0:0:0: [sda] Assuming drive cache: write through [ 1148.440000] sda: sda1 [ 1148.450000] sd 1:0:0:0: [sda] Attached SCSI removable disk [ 1168.550000] CPU 0 Unable to handle kernel paging request at virtual address c0676c40, epc == c0676c40, ra == c0694dd0 [ 1168.560000] Oops[#4]: [ 1168.560000] CPU: 0 PID: 1596 Comm: mount Tainted: G D 3.18.18 #1 [ 1168.560000] task: 8182a220 ti: 8155a000 task.ti: 8155a000 [ 1168.560000] $ 0 : 00000000 00000000 c0698e60 00000000 [ 1168.560000] $ 4 : c06c6b30 00008000 81578700 00000000 [ 1168.560000] $ 8 : 00003100 8157868a 00000010 00000013 [ 1168.560000] $12 : 7fb3d928 00000000 00000000 770b4000 [ 1168.560000] $16 : 80f6c780 81578700 c06c6b30 c06c6b30 [ 1168.560000] $20 : 00000000 00000000 81578c00 770b4000 [ 1168.560000] $24 : 00000010 8016c38c [ 1168.560000] $28 : 8155a000 8155be38 00000000 c0694dd0 [ 1168.560000] Hi : 00000019 [ 1168.560000] Lo : 00000000 [ 1168.560000] epc : c0676c40 0xc0676c40 [ 1168.560000] Tainted: G D [ 1168.560000] ra : c0694dd0 ext4_orphan_del+0x108c/0x1f30 [ext4] [ 1168.560000] Status: 1000fc03 KERNEL EXL IE [ 1168.560000] Cause : 10800008 [ 1168.560000] BadVA : c0676c40 [ 1168.560000] PrId : 00019374 (MIPS 24Kc) [ 1168.560000] Modules linked in: ext4 jbd2 mbcache crc16 crypto_hash usb_storage sd_mod scsi_mod ath9k ath9k_common pppoe ppp_async iptable_nat ath9k_hw ath pppox ppp_generic nf_nat_ipv4 nf_conntrack_ipv6 nf_conntrack_ipv4 mac80211 ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_id xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_CT slhc nf_reject_ipv4 nf_nat_masquerade_ipv4 nf_nat_ftp nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack_ftp nf_conntrack iptable_raw iptable_mangle iptable_filter ip_tables crc_ccitt compat ledtrig_usbdev ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_raw ip6table_mangle ip6table_filter ip6_tables x_tables ipv6 arc4 crypto_blkcipher ohci_platform ohci_hcd ehci_platform ehci_hcd gpio_button_hotplug usbcore nls_base usb_common [ 1168.560000] Process mount (pid: 1596, threadinfo=8155a000, task=8182a220, tls=770c1644) [ 1168.560000] Stack : 80400000 80f6c780 81578700 804073f0 c0698e60 80116f30 81733300 800ffc68 [ 1168.560000] 00000000 81578c00 c06c6b30 81578700 00008000 c06c6b30 80f6c780 81578700 [ 1168.560000] 00008000 80116fdc 00008000 8010a4a0 00000001 7fb3df74 c06c6b30 00000020 [ 1168.560000] 80391f70 00008000 81578700 80119de8 8182ebc0 7fb3df74 0000000a 800ddc68 [ 1168.560000] 81b1f010 8088e4c8 7fb3dc34 770b4000 00000000 0000000a 00000000 81578c00 [ 1168.560000] ... [ 1168.560000] Call Trace: [ 1168.560000] [] ext4_calculate_overhead+0x4b8/0x3238 [ext4] [ 1168.560000] [] alloc_vfsmnt+0x124/0x16c [ 1168.560000] [] mount_fs+0x20/0xd8 [ 1168.560000] [] vfs_kern_mount+0x64/0x114 [ 1168.560000] [] user_path_at+0x14/0x20 [ 1168.560000] [] do_mount+0x868/0x974 [ 1168.560000] [] memdup_user+0x28/0x90 [ 1168.560000] [] SyS_mount+0x90/0xd4 [ 1168.560000] [] handle_sys+0x11c/0x140 [ 1168.560000] [] __bzero+0xc4/0x164 [ 1168.560000] [ 1168.560000] [ 1168.560000] Code: (Bad address in epc) [ 1168.560000] [ 1168.820000] ---[ end trace 9f7c3beeded42796 ]--- df: root@OpenWrt:/# df -h Filesystem Size Used Available Use% Mounted on rootfs 640.0K 572.0K 68.0K 89% / /dev/root 2.0M 2.0M 0 100% /rom tmpfs 13.9M 656.0K 13.3M 5% /tmp /dev/mtdblock3 640.0K 572.0K 68.0K 89% /overlay overlayfs:/overlay 640.0K 572.0K 68.0K 89% / tmpfs 512.0K 0 512.0K 0% /dev free: root@OpenWrt:/# free total used free shared buffers Mem: 28508 17516 10992 656 568 -/+ buffers: 16948 11560 Swap: 0 0 0 If not sure what going on here, I dont think RAM is a problem as the free command show that half my ram is still unused, and i did try with ext2 and 3 but i just get the same output. So if anyone has any idea i would greatly appreciate it! Thanks! EDIT: So I found this page http://blog.csdn.net/u011839461/article/details/12001437 which say if BadVA == epc then it is most likely memory corruption, but Im not sure what i can do about it.

When I try to run any executable from my second (NTFS) drive, I get a segmentation fault. If I run the exact same executable from, for example, my home folder, it works just fine. For example: I compile the following C program using gcc a.c:

#include 

int main() {
    puts("Hello");
    return 0;
}

Now I run ./a.out from my second drive:

$ ./a.out
zsh: segmentation fault  ./a.out

(Also no core dump is generated, even though they are enabled and work for other things.) If I copy the exact same file, without any modifications, to e.g. /home/username/ (which is on my main/OS drive):

$ ./a.out
Hello

Everything works perfectly fine there. On the second drive however, GDB just fails during startup:

(gdb) starti
Starting program: /path/to/a.out 
During startup program terminated with signal SIGSEGV, Segmentation fault.

When I use strace, it says execve failed:

$ strace ./a.out
execve("./a.out", ["./a.out"], 0x7ffd0aa31070 /* 83 vars */) = -1 EOPNOTSUPP (Operation not supported)
+++ killed by SIGSEGV +++
zsh: segmentation fault (core dumped)  strace ./a.out

Also ldd just says not a dynamic executable on the second drive. readelf -d and objdump -p work just fine. My drive and one of its subfolders is mounted like this in /etc/fstab:

UUID=drive-uuid-123        /path/to/drive   ntfs3   defaults      0 2
/path/to/drive/some/path   /my/new/path     none    defaults,bind 0 2

The same issue occurs when I run the binary from yet another different NTFS drive. System information:

$ uname -a
Linux thomas-manjaro 6.6.25-1-MANJARO #1 SMP PREEMPT_DYNAMIC Thu Apr  4 20:32:38 UTC 2024 x86_64 GNU/Linux

This is a pretty fresh install of Manjaro and all packages are up-to-date. Does anyone know what the problem could be? Do I need to mount my drive in a different way? Do I need to set some kind of system variable?

I know there are a few Questions here which ask the same question I appear to be asking. I have tried those suggestions (https://unix.stackexchange.com/a/439342/286615) & (https://unix.stackexchange.com/a/151371/286615) , but they do not work in this case. Here's what has happened:

pi@raspberrypi0w:~ $ sudo apt -t bullseye-backports install udev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  libudev1
The following packages will be upgraded:
  libudev1 udev
2 upgraded, 0 newly installed, 0 to remove and 35 not upgraded.
Need to get 1,654 kB of archives.
After this operation, 511 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://deb.debian.org/debian  bullseye-backports/main armhf udev armhf 252.5-2~bpo11+1 [1,554 kB]
Get:2 http://deb.debian.org/debian  bullseye-backports/main armhf libudev1 armhf 252.5-2~bpo11+1 [100 kB]
Fetched 1,654 kB in 1s (1,267 kB/s)
Reading changelogs... Done
(Reading database ... 43648 files and directories currently installed.)
Preparing to unpack .../udev_252.5-2~bpo11+1_armhf.deb ...
Unpacking udev (252.5-2~bpo11+1) over (247.3-7+rpi1+deb11u2) ...
Preparing to unpack .../libudev1_252.5-2~bpo11+1_armhf.deb ...
Unpacking libudev1:armhf (252.5-2~bpo11+1) over (247.3-7+rpi1+deb11u2) ...
Setting up libudev1:armhf (252.5-2~bpo11+1) ...
Setting up udev (252.5-2~bpo11+1) ...
Segmentation fault
Job for systemd-udevd.service failed because a fatal signal was delivered to the control process.
See "systemctl status systemd-udevd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript udev, action "restart" failed.
● systemd-udevd.service - Rule-based Manager for Device Events and Files
     Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static)
     Active: activating (start) since Tue 2024-04-09 07:36:27 UTC; 130ms ago
TriggeredBy: ● systemd-udevd-control.socket
             ● systemd-udevd-kernel.socket
       Docs: man:systemd-udevd.service(8)
             man:udev(7)
   Main PID: 8773 ((md-udevd))
      Tasks: 1
        CPU: 45ms
     CGroup: /system.slice/systemd-udevd.service
             └─8773 (md-udevd)

Apr 09 07:36:28 raspberrypi0w systemd: Stopped Rule-based Manager for Device Events and Files.
Apr 09 07:36:28 raspberrypi0w systemd: Starting Rule-based Manager for Device Events and Files...
Apr 09 07:36:28 raspberrypi0w systemd: systemd-udevd.service: Main process exited, code=killed, status=11/SEGV
Apr 09 07:36:28 raspberrypi0w systemd: systemd-udevd.service: Failed with result 'signal'.
Apr 09 07:36:28 raspberrypi0w systemd: Failed to start Rule-based Manager for Device Events and Files.
Apr 09 07:36:28 raspberrypi0w systemd: systemd-udevd.service: Scheduled restart job, restart counter is at 5.
Apr 09 07:36:28 raspberrypi0w systemd: Stopped Rule-based Manager for Device Events and Files.
Apr 09 07:36:28 raspberrypi0w systemd: systemd-udevd.service: Start request repeated too quickly.
Apr 09 07:36:28 raspberrypi0w systemd: systemd-udevd.service: Failed with result 'signal'.
Apr 09 07:36:28 raspberrypi0w systemd: Failed to start Rule-based Manager for Device Events and Files.
dpkg: error processing package udev (--configure):
 installed udev package post-installation script subprocess returned error exit status 1
Processing triggers for libc-bin (2.31-13+rpt2+rpi1+deb11u8) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for initramfs-tools (0.140) ...
Errors were encountered while processing:
 udev
E: Sub-process /usr/bin/dpkg returned an error code (1)

The attempted "reversion" wasn't very interesting:

pi@raspberrypi0w:~ $ apt install ${udev}/bullseye
Illegal instruction

I attempted a few other "reversions":

pi@raspberrypi0w:~ $ sudo apt install udev
Illegal instruction
pi@raspberrypi0w:~ $ sudo apt-get install udev/stable
Illegal instruction
pi@raspberrypi0w:~ $ sudo apt-get install udev/old-stable
Illegal instruction

A 'segmentation fault' - sounds serious :). I was unsure what this meant; i.e. did the system automatically reject the udev upgrade & revert automatically? - or have I stepped in it? I waited a few minutes & tried this:

$ systemctl status systemd-udevd.service
● systemd-udevd.service - Rule-based Manager for Device Events and Files
     Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static)
     Active: failed (Result: signal) since Tue 2024-04-09 07:36:28 UTC; 28min ago
TriggeredBy: ● systemd-udevd-control.socket
             ● systemd-udevd-kernel.socket
       Docs: man:systemd-udevd.service(8)
             man:udev(7)
    Process: 8776 ExecStart=/lib/systemd/systemd-udevd (code=killed, signal=SEGV)
   Main PID: 8776 (code=killed, signal=SEGV)
        CPU: 199ms

Apr 09 07:36:28 raspberrypi0w systemd: systemd-udevd.service: Scheduled restart job, restart counter is at 5.
Apr 09 07:36:28 raspberrypi0w systemd: Stopped Rule-based Manager for Device Events and Files.
Apr 09 07:36:28 raspberrypi0w systemd: systemd-udevd.service: Start request repeated too quickly.
Apr 09 07:36:28 raspberrypi0w systemd: systemd-udevd.service: Failed with result 'signal'.
Apr 09 07:36:28 raspberrypi0w systemd: Failed to start Rule-based Manager for Device Events and Files.

I have a good (image) backup from last night, so if I've killed my OS I can recover. However, I'd prefer to fix this without resort to the backup - if that's possible. What should I do?

I am trying to implement a PCI device driver for a virtual PCI device on QEMU. The device defines a BAR region as RAM, and the driver can do ioremap() this region and access it without any issues. The next step is to assign this region (or a fraction of it) to a user application. To do this, I have also implemented an .mmap function as part of my driver file operations. This mmap is simply using remap_pfn_range, but it also passes the pfn of the memory pointer returned by the ioremap() earlier. However, upon running the user space application, the mmap is successful, but when the app tries to access the memory, it is killed and I get the following dmesg errors.

[ 1502.402970] a.out: Corrupted page table at address 7f911b79f000
[ 1502.404085] PGD 13926d067 P4D 13926d067 PUD 1317aa067 PMD 1326d9067 PTE 800026d901000227
[ 1502.404085] Bad pagetable: 000f [#1] SMP NOPTI
[ 1502.404085] Modules linked in: edu_driver(OE) ppdev kvm_amd kvm irqbypass input_leds parport_pc serio_raw parport mac_hid qemu_fw_cfg sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear psmouse pata_acpi floppy e1000 i2c_piix4
[ 1502.404085] CPU: 0 PID: 1988 Comm: a.out Tainted: G           OE    4.15.0-55-generic #60-Ubuntu
[ 1502.404085] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014
[ 1502.404085] RIP: 0033:0x55d687642811
[ 1502.404085] RSP: 002b:00007ffe16c38da0 EFLAGS: 00000213
[ 1502.404085] RAX: 00007f911b79f000 RBX: 0000000000000000 RCX: 00007f911b2a1813
[ 1502.404085] RDX: 0000000000000003 RSI: 0000000000001000 RDI: 0000000000000000
[ 1502.404085] RBP: 00007ffe16c38dc0 R08: 0000000000000003 R09: 0000000000000000
[ 1502.404085] R10: 0000000000008001 R11: 0000000000000246 R12: 000055d687642660
[ 1502.404085] R13: 00007ffe16c38ea0 R14: 0000000000000000 R15: 0000000000000000
[ 1502.404085] FS:  00007f911b7984c0(0000) GS:ffff97237fc00000(0000) knlGS:0000000000000000
[ 1502.404085] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 1502.404085] CR2: 00007f911b79f000 CR3: 0000000132cd8000 CR4: 00000000000006f0
[ 1502.404085] RIP: 0x55d687642811 RSP: 00007ffe16c38da0
[ 1502.404085] ---[ end trace 6b088b58eb816baf ]---

Does anyone know what have I done wrong? Did I missed a step? Or it could be an error specific to QEMU? I am running x86_softmmu as my QEMU configuration and my kernel is the 4.14

I've got a device with bad RAM. Running memtest overnight shows all faulting addresses to be in the 0x7d0000000 - 0x7f0000000 range. I plan to replace the RAM, but until then, I've disabled a 2GB chunk around it with memmap=:

# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-6.5.0-25-generic root=UUID=5277c53f-b2cd-4301-8fdf-0b2119430870 ro memmap=2G$0x0000000790000000 quiet splash vt.handoff=7

Those cmdline options do seem to be acknowledged by the kernel:

[    0.000000] user-defined physical RAM map:
[    0.000000] user: [mem 0x0000000000000000-0x000000000009efff] usable
[    0.000000] user: [mem 0x000000000009f000-0x00000000000fffff] reserved
[    0.000000] user: [mem 0x0000000000100000-0x0000000019e6a017] usable
[    0.000000] user: [mem 0x0000000019e6a018-0x0000000019e7ae57] usable
[    0.000000] user: [mem 0x0000000019e7ae58-0x000000002cb82fff] usable
[    0.000000] user: [mem 0x000000002cb83000-0x000000002ed2ffff] reserved
[    0.000000] user: [mem 0x000000002ed30000-0x000000002edacfff] ACPI data
[    0.000000] user: [mem 0x000000002edad000-0x000000002f29bfff] ACPI NVS
[    0.000000] user: [mem 0x000000002f29c000-0x000000002fd0efff] reserved
[    0.000000] user: [mem 0x000000002fd0f000-0x000000002fd0ffff] usable
[    0.000000] user: [mem 0x000000002fd10000-0x000000003cffffff] reserved
[    0.000000] user: [mem 0x00000000e0000000-0x00000000efffffff] reserved
[    0.000000] user: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
[    0.000000] user: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[    0.000000] user: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
[    0.000000] user: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[    0.000000] user: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[    0.000000] user: [mem 0x0000000100000000-0x000000078fffffff] usable
[    0.000000] user: [mem 0x0000000790000000-0x000000080fffffff] reserved
[    0.000000] user: [mem 0x0000000810000000-0x00000008beffffff] usable

However, I still get segfaults, ostensibly in the reserved address range:

Mar 09 20:47:40 srv0 kernel: udisksd: segfault at 7fe974786218 ip 00007fe974786218 sp 00007ffcd10d1848 error 7 in libbd_swap.so.3.0.0[7fe974785000+2000] likely on CPU 7 (core 3, socket 0)

According to this page , I should interpret that as udiskd trying to write to the reserved address 0x7fe974786218 (error 7). At first glance, the 0x7f address seems to match up with what memtest found to be bad RAM, but is off by orders of magnitude, since it points to a value of 140 TB. My machine has 32 GB. What, if not a memory address, does the segfault at X value represent?