Sample Header Ad - 728x90

Unix & Linux Stack Exchange

Q&A for users of Linux, FreeBSD and other Unix-like operating systems

Latest Questions

0 votes
1 answers
2361 views
google-chrome-stable Aw, Snap?
When I start Google-chrome-stable on Centos, the browser starts successfully, but the page crashes, and shows `aw,snap!`, how to fix this error? OS: ``` CentOS Linux release 7.2 (Final) ``` chrome version: ``` Google Chrome 111.0.5563.146 ``` command: ``` google-chrome-stable --autoplay-policy=no-us...
When I start Google-chrome-stable on Centos, the browser starts successfully, but the page crashes, and shows aw,snap!, how to fix this error? OS:
CentOS Linux release 7.2 (Final)
chrome version:
Google Chrome 111.0.5563.146
command:
google-chrome-stable --autoplay-policy=no-user-gesture-required --mute-audio=false --window-size=1920,1080 http://douyin.com 
output:
google-chrome-stable --autoplay-policy=no-user-gesture-required --mute-audio=false --window-size=1920,1080 http://douyin.com 
[742794:742820:0331/103754.452327:ERROR:bus.cc(399)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[742794:742825:0331/103754.509872:ERROR:bus.cc(399)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[742794:742825:0331/103754.509920:ERROR:bus.cc(399)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[742794:742820:0331/103754.511707:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[742794:742820:0331/103754.511750:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[742794:742820:0331/103754.526791:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[742794:742820:0331/103754.526818:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[742794:742820:0331/103754.584518:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[742794:742820:0331/103754.584545:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[742794:742912:0331/103754.779461:ERROR:bus.cc(399)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[742794:742912:0331/103754.779498:ERROR:bus.cc(399)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[742794:742912:0331/103754.779570:ERROR:bus.cc(399)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[742794:742912:0331/103754.779589:ERROR:bus.cc(399)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[742794:742912:0331/103754.779604:ERROR:bus.cc(399)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[742833:742833:0331/103754.780520:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
[742916:742916:0331/103754.891348:ERROR:gpu_memory_buffer_support_x11.cc(49)] dri3 extension not supported.
[742864:7:0331/103754.892920:ERROR:command_buffer_proxy_impl.cc(128)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[0331/103755.989434:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0331/103755.996041:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2)
[0331/103755.996073:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2)
[742834:742852:0331/103804.844167:ERROR:ssl_client_socket_impl.cc(992)] handshake failed; returned -1, SSL error code 1, net_error -100
[742834:742852:0331/103814.894472:ERROR:ssl_client_socket_impl.cc(992)] handshake failed; returned -1, SSL error code 1, net_error -100
huajie sun (9 rep)
Mar 31, 2023, 02:45 AM • Last activity: Jul 17, 2025, 05:03 AM
1 votes
1 answers
2269 views
Ubuntu Unity randomly crashes, and then the command 'unity' isn't recognized
For the last bit, unity (and perhaps other things?) would crash after something like 20-30 minutes of use. First my launchbar would disappear, all of the upper right hand icons disappear and then all my programs freeze. If I press my power button, the login/shutdown/restart screen shows up but all t...
For the last bit, unity (and perhaps other things?) would crash after something like 20-30 minutes of use. First my launchbar would disappear, all of the upper right hand icons disappear and then all my programs freeze. If I press my power button, the login/shutdown/restart screen shows up but all the text is squares. Then the entire GUI freezes. If I manage to open up a terminal before everything stops and I type in 'unity', it says that the command isn't recognised. Any suggestions or help would be greatly appreciated. Thanks!
algebroic (11 rep)
May 6, 2017, 06:01 PM • Last activity: Jul 15, 2025, 07:01 AM
2 votes
0 answers
21 views
How does one retroactively debug a coredump generated from an AppImage?
When a non-reproducible crash occurs in an installed `.flatpak` package, [I can debug it with `flatpak-coredumpctl`, even if I've solely installed the relevant debug packages after the crash occurred][2]. This is a useful way to retroactive generate a backtrace. [2]: https://github.com/flatpak/flatp...
When a non-reproducible crash occurs in an installed .flatpak package, I can debug it with flatpak-coredumpctl, even if I've solely installed the relevant debug packages after the crash occurred . This is a useful way to retroactive generate a backtrace. With an .AppImage, I see (unofficial) documentation on how to proactively capture a coredump and generate a trace *there* , but that's not useful on another machine, or if unique crashes need to be captured. After all, the unexpected coredumps are the most useful. As an example: ~~~ RokeJulianLockhart@Beedell:~$ coredumpctl debug 63788 PID: 63788 (cursor) UID: 1000 (RokeJulianLockhart) GID: 1000 (RokeJulianLockhart) Signal: 5 (TRAP) Timestamp: Sat 2025-07-05 11:43:55 BST (11min ago) Command Line: /usr/share/cursor/cursor Executable: /usr/share/cursor/cursor Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-appimagelauncher@436976d275e044819cec0d32bc46e97e.service Unit: user@1000.service User Unit: app-appimagelauncher@436976d275e044819cec0d32bc46e97e.service Slice: user-1000.slice Owner UID: 1000 (RokeJulianLockhart) Boot ID: b2f81b0d22aa46928bace43988e7c488 Machine ID: b4f0bef5ffd640fba0ab31fdaa2820b8 Hostname: Beedell.RokeJulianLockhart.desktop.SSV2AY Storage: /var/lib/systemd/coredump/core.cursor.1000.b2f81b0d22aa46928bace43988e7c488.63788.1751712235000000.zst (present) Size on Disk: 1.7M Message: Process 63788 (cursor) of user 1000 dumped core. Module libbrotlicommon.so.1 from rpm brotli-1.1.0-6.fc42.x86_64 Module liblzma.so.5 from rpm xz-5.8.1-2.fc42.x86_64 Module libbrotlidec.so.1 from rpm brotli-1.1.0-6.fc42.x86_64 Module libbz2.so.1 from rpm bzip2-1.0.8-20.fc42.x86_64 Module libdatrie.so.1 from rpm libdatrie-0.2.13-11.fc42.x86_64 Module libjson-glib-1.0.so.0 from rpm json-glib-1.10.6-2.fc42.x86_64 Module libjpeg.so.62 from rpm libjpeg-turbo-3.1.0-2.fc42.x86_64 Module libxml2.so.2 from rpm libxml2-2.12.10-1.fc42.x86_64 Module libgraphite2.so.3 from rpm graphite2-1.3.14-18.fc42.x86_64 Module libXinerama.so.1 from rpm libXinerama-1.1.5-8.fc42.x86_64 Module libXcursor.so.1 from rpm libXcursor-1.2.3-2.fc42.x86_64 Module libwayland-egl.so.1 from rpm wayland-1.23.1-1.fc42.x86_64 Module libwayland-cursor.so.0 from rpm wayland-1.23.1-1.fc42.x86_64 Module libgmp.so.10 from rpm gmp-6.3.0-4.fc42.x86_64 Module libnettle.so.8 from rpm nettle-3.10.1-1.fc42.x86_64 Module libhogweed.so.6 from rpm nettle-3.10.1-1.fc42.x86_64 Module libtasn1.so.6 from rpm libtasn1-4.20.0-1.fc42.x86_64 Module libunistring.so.5 from rpm libunistring-1.1-9.fc42.x86_64 Module libidn2.so.0 from rpm libidn2-2.3.8-1.fc42.x86_64 Module libp11-kit.so.0 from rpm p11-kit-0.25.5-5.fc42.x86_64 Module libcrypto.so.3 from rpm openssl-3.2.4-3.fc42.x86_64 Module libkeyutils.so.1 from rpm keyutils-1.6.3-5.fc42.x86_64 Module libkrb5support.so.0 from rpm krb5-1.21.3-6.fc42.x86_64 Module libcom_err.so.2 from rpm e2fsprogs-1.47.2-3.fc42.x86_64 Module libk5crypto.so.3 from rpm krb5-1.21.3-6.fc42.x86_64 Module libkrb5.so.3 from rpm krb5-1.21.3-6.fc42.x86_64 Module libblkid.so.1 from rpm util-linux-2.40.4-7.fc42.x86_64 Module libcap.so.2 from rpm libcap-2.73-2.fc42.x86_64 Module libXau.so.6 from rpm libXau-1.0.12-2.fc42.x86_64 Module libdrm.so.2 from rpm libdrm-2.4.125-1.fc42.x86_64 Module libpixman-1.so.0 from rpm pixman-0.46.2-1.fc42.x86_64 Module libxcb-shm.so.0 from rpm libxcb-1.17.0-5.fc42.x86_64 Module libxcb-render.so.0 from rpm libxcb-1.17.0-5.fc42.x86_64 Module libXrender.so.1 from rpm libXrender-0.9.12-2.fc42.x86_64 Module libfreetype.so.6 from rpm freetype-2.13.3-2.fc42.x86_64 Module libpng16.so.16 from rpm libpng-1.6.44-2.fc42.x86_64 Module libthai.so.0 from rpm libthai-0.1.29-10.fc42.x86_64 Module libwayland-client.so.0 from rpm wayland-1.23.1-1.fc42.x86_64 Module libtinysparql-3.0.so.0 from rpm tinysparql-3.9.2-1.fc42.x86_64 Module libcloudproviders.so.0 from rpm libcloudproviders-0.3.6-1.fc42.x86_64 Module libXi.so.6 from rpm libXi-1.8.2-2.fc42.x86_64 Module libepoxy.so.0 from rpm libepoxy-1.5.10-9.fc42.x86_64 Module libgdk_pixbuf-2.0.so.0 from rpm gdk-pixbuf2-2.42.12-10.fc42.x86_64 Module libcairo-gobject.so.2 from rpm cairo-1.18.2-3.fc42.x86_64 Module libfribidi.so.0 from rpm fribidi-1.0.16-2.fc42.x86_64 Module libfontconfig.so.1 from rpm fontconfig-2.16.0-2.fc42.x86_64 Module libpangoft2-1.0.so.0 from rpm pango-1.56.3-1.fc42.x86_64 Module libharfbuzz.so.0 from rpm harfbuzz-10.4.0-1.fc42.x86_64 Module libpangocairo-1.0.so.0 from rpm pango-1.56.3-1.fc42.x86_64 Module libgdk-3.so.0 from rpm gtk3-3.24.49-2.fc42.x86_64 Module libgnutls.so.30 from rpm gnutls-3.8.9-3.fc42.x86_64 Module libavahi-client.so.3 from rpm avahi-0.9~rc2-2.fc42.x86_64 Module libavahi-common.so.3 from rpm avahi-0.9~rc2-2.fc42.x86_64 Module libgssapi_krb5.so.2 from rpm krb5-1.21.3-6.fc42.x86_64 Module libsystemd.so.0 from rpm systemd-257.7-1.fc42.x86_64 Module libplds4.so from rpm nss-3.112.0-1.fc42.x86_64 Module libplc4.so from rpm nss-3.112.0-1.fc42.x86_64 Module libselinux.so.1 from rpm libselinux-3.8-2.fc42.x86_64 Module libmount.so.1 from rpm util-linux-2.40.4-7.fc42.x86_64 Module libz.so.1 from rpm zlib-ng-2.2.4-3.fc42.x86_64 Module libgmodule-2.0.so.0 from rpm glib2-2.84.2-1.fc42.x86_64 Module libffi.so.8 from rpm libffi-3.4.6-5.fc42.x86_64 Module libpcre2-8.so.0 from rpm pcre2-10.45-1.fc42.x86_64 Module libatspi.so.0 from rpm at-spi2-core-2.56.2-1.fc42.x86_64 Module libasound.so.2 from rpm alsa-lib-1.2.14-3.fc42.x86_64 Module libudev.so.1 from rpm systemd-257.7-1.fc42.x86_64 Module libxkbcommon.so.0 from rpm libxkbcommon-1.8.1-1.fc42.x86_64 Module libxcb.so.1 from rpm libxcb-1.17.0-5.fc42.x86_64 Module libexpat.so.1 from rpm expat-2.7.1-1.fc42.x86_64 Module libgbm.so.1 from rpm mesa-25.0.7-2.fc42.x86_64 Module libXrandr.so.2 from rpm libXrandr-1.5.4-5.fc42.x86_64 Module libXfixes.so.3 from rpm libXfixes-6.0.1-5.fc42.x86_64 Module libXext.so.6 from rpm libXext-1.3.6-3.fc42.x86_64 Module libXdamage.so.1 from rpm libXdamage-1.1.6-5.fc42.x86_64 Module libXcomposite.so.1 from rpm libXcomposite-0.4.6-5.fc42.x86_64 Module libX11.so.6 from rpm libX11-1.8.11-1.fc42.x86_64 Module libcairo.so.2 from rpm cairo-1.18.2-3.fc42.x86_64 Module libpango-1.0.so.0 from rpm pango-1.56.3-1.fc42.x86_64 Module libgtk-3.so.0 from rpm gtk3-3.24.49-2.fc42.x86_64 Module libcups.so.2 from rpm cups-2.4.12-3.fc42.x86_64 Module libatk-bridge-2.0.so.0 from rpm at-spi2-core-2.56.2-1.fc42.x86_64 Module libatk-1.0.so.0 from rpm at-spi2-core-2.56.2-1.fc42.x86_64 Module libdbus-1.so.3 from rpm dbus-1.16.0-3.fc42.x86_64 Module libnspr4.so from rpm nss-3.112.0-1.fc42.x86_64 Module libsmime3.so from rpm nss-3.112.0-1.fc42.x86_64 Module libnssutil3.so from rpm nss-3.112.0-1.fc42.x86_64 Module libnss3.so from rpm nss-3.112.0-1.fc42.x86_64 Module libgio-2.0.so.0 from rpm glib2-2.84.2-1.fc42.x86_64 Module libgobject-2.0.so.0 from rpm glib2-2.84.2-1.fc42.x86_64 Module libglib-2.0.so.0 from rpm glib2-2.84.2-1.fc42.x86_64 Stack trace of thread 63788: #0 0x0000555b9189e4a9 n/a (/usr/share/cursor/cursor + 0x64384a9) #1 0x0000555b8dbff5ea n/a (/usr/share/cursor/cursor + 0x27995ea) #2 0x0000555b8dbfdac5 n/a (/usr/share/cursor/cursor + 0x2797ac5) #3 0x0000555b8dbfdf70 n/a (/usr/share/cursor/cursor + 0x2797f70) #4 0x0000555b8d8998f7 n/a (/usr/share/cursor/cursor + 0x24338f7) #5 0x00007f5ed2bc85f5 __libc_start_call_main (libc.so.6 + 0x35f5) #6 0x00007f5ed2bc86a8 __libc_start_main_impl (libc.so.6 + 0x36a8) #7 0x0000555b8d47102a n/a (/usr/share/cursor/cursor + 0x200b02a) ELF object binary architecture: AMD x86-64 GNU gdb (Fedora Linux) 16.3-1.fc42 Copyright (C) 2024 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... /usr/share/cursor/cursor: No such file or directory. This GDB supports auto-downloading debuginfo from the following URLs: Enable debuginfod for this session? (y or [n]) y Debuginfod has been enabled. To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit. warning: Can't open file /usr/share/cursor/libffmpeg.so during file-backed mapping note processing warning: Can't open file /usr/share/cursor/cursor during file-backed mapping note processing [New LWP 63788] Core was generated by `/tmp/.mount_Cursorco8TO2/usr/share/cursor/cursor'. Program terminated with signal SIGTRAP, Trace/breakpoint trap. #0 0x0000555b9189e4a9 in ?? () Missing file(s), try: dnf --enablerepo='*debug*' install /usr/lib/.build-id/79/bae446b9a2d28f83944da3e26fdc4738a35d86 /usr/lib/debug/.build-id/79/bae446b9a2d28f83944da3e26fdc4738a35d86.debug Missing file(s), try: dnf --enablerepo='*debug*' install /usr/lib/.build-id/60/fed38b5df7050dd9cfc6a9ff9082c863370451 /usr/lib/debug/.build-id/60/fed38b5df7050dd9cfc6a9ff9082c863370451.debug (gdb) bt full #0 0x0000555b9189e4a9 in ?? () No symbol table info available. #1 0x0000555b00000001 in ?? () No symbol table info available. #2 0xaaaaaa00ffffffff in ?? () No symbol table info available. #3 0x0000000000000000 in ?? () No symbol table info available. ~~~ ##### Rationale I've already enough information for a bug report to the developers , because I know what action caused it. However, considering the unusual signal, I'd like to be able to better confirm whether a [mis]configuration of mine is relevant, and provide *actionable* information.
RokeJulianLockhart (541 rep)
Jul 5, 2025, 11:05 AM • Last activity: Jul 5, 2025, 11:15 AM
2 votes
0 answers
905 views
Kali Linux VirtualBox browsers crash
No matter what I do, the browsers of my **Kali Linux VM** crash. I have tried **Firefox ESR** (**preinstalled**), **Firefox**, **Google Chrome**, and **Chromium**. In Firefox the whole browser crashes (max 1-2 mins after starting and using it) and on the chromium-based browsers only the Tabs crash,...
No matter what I do, the browsers of my **Kali Linux VM** crash. I have tried **Firefox ESR** (**preinstalled**), **Firefox**, **Google Chrome**, and **Chromium**. In Firefox the whole browser crashes (max 1-2 mins after starting and using it) and on the chromium-based browsers only the Tabs crash, without any error message. When I start Firefox from the command line I receive this as error message, when it crashes: ExceptionHandler::GenerateDump cloned child ExceptionHandler::WaitForContinueSignal waiting for continue signal... 8253 ExceptionHandler::SendContinueSignalToChild sent continue signal to child Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. I use **VirtualBox** and installed Kali Linux several times with these two options (each with the settings of the Documentation): - Using Kali Linux prebuilt Virtual Machines - Installing the Kali Linux with an image In the VMs I also ran: sudo apt-get update and sudo apt-get dist-upgrade and I checked the browser for updates. Furthermore, many clean installations didn't work. Of course, I have tried to look up this issue. But I didn't find anything from the last few years. My question is what am I missing? Why does the standard browser not work on a prebuilt Virtual Machine? And why are the others also crashing? Thank you for helping me!
Frederick (121 rep)
Oct 1, 2022, 03:39 PM • Last activity: Jul 1, 2025, 01:41 PM
5 votes
2 answers
4355 views
How can I debug Nautilus crashes?
Is there a log file I can peruse, or settings somewhere that might give me a clue? I'm running GNOME nautilus 3.14.3 ("Files") in Ubuntu 16.04.
Is there a log file I can peruse, or settings somewhere that might give me a clue? I'm running GNOME nautilus 3.14.3 ("Files") in Ubuntu 16.04.
jvriesem (151 rep)
Aug 8, 2016, 08:17 PM • Last activity: Jun 19, 2025, 06:08 AM
0 votes
1 answers
2639 views
Frequent crashes after update to Fedora 39
I have updated from Fedora 38 to 39 yesterday. Since then, I am having frequent crashes where the screen goes black for a couple of seconds, then goes back to the login page, and after I enter the password all applications are closed. No mention of the crash appears in the notifications. This occurs...
I have updated from Fedora 38 to 39 yesterday. Since then, I am having frequent crashes where the screen goes black for a couple of seconds, then goes back to the login page, and after I enter the password all applications are closed. No mention of the crash appears in the notifications. This occurs randomly, after maybe 5 minutes of use, not in connection to anything specific that I am doing. I tried booting both the current kernel 6.5.11-300.fc39.x86_64 and on the previous kernel, namely 6.5.10-200.fc38.x86_64, but both have this problem. I don't think that this is related to a hardware issue because Windows, in dual boot, runs ok, and the freezes only appeared after the Fedora 39 update. The computer is a Dell laptop. The graphics card is the integrated Intel one. What can I do to find the cause?
Marco (31 rep)
Nov 11, 2023, 10:59 AM • Last activity: Jun 12, 2025, 01:01 PM
3 votes
1 answers
2818 views
File system goes read-only on NVMe SSD seemingly at random
I am currently running a somewhat fresh Kubuntu 22.04 install on a relatively new M.2 NVMe drive. However, I have a problem where my computer drive (I think) turns read only, causing the system to sort of crash. When I first installed the system, this would happen very frequently until I applied the...
I am currently running a somewhat fresh Kubuntu 22.04 install on a relatively new M.2 NVMe drive. However, I have a problem where my computer drive (I think) turns read only, causing the system to sort of crash. When I first installed the system, this would happen very frequently until I applied the
=off
fix to the /etc/default/grub file:
="quiet splash pcie_aspm=off"
. This made it happen less frequently. This issue happens on all the previous systems I've tried to install on this drive, with most of the same symptoms, i.e. some icons disappearing, apps breaking, chromium tabs displaying "aw snap," and in particular, libreoffice gives a "filesystem read only" error when trying to save. One thing different from similar errors though, is that when I reboot the computer manually (holding power button) it goes back to normal for a while, while some seem to have problems booting afterwards. Then it happens again some time later. I can provide more details if needed, e.g. hardware, syslog entries, etc. Does anyone have a permanent solution to this? Not a computer whiz, but I do know some.
Lirik (31 rep)
Nov 22, 2022, 03:13 AM • Last activity: May 19, 2025, 10:09 AM
10 votes
1 answers
2945 views
Migrate Firefox profile to a new one
I reinstalled Firefox, because my profile was crashing. I backed up my `~/.mozilla` folder to some other place, uninstalled firefox and installed it again. New firefox wasn't crashing. So I copied one of my backup up old profile to new firefox, and that profile was crashing again. Now, I would like...
I reinstalled Firefox, because my profile was crashing. I backed up my ~/.mozilla folder to some other place, uninstalled firefox and installed it again. New firefox wasn't crashing. So I copied one of my backup up old profile to new firefox, and that profile was crashing again. Now, I would like to use completely fresh profile and copy only the things that I need from the old profile that is crashing. Which files need I to replace? I need bookmarks (the quick access bar with bookmarks is sufficient for me and I need all the extensions with extension data). What could I also need and forget? I want to try it, I will at least find out, if it is some extension that's causing the crashes. But, I think it is not. It starts usually when I open a new tab and the page won't load. My OS is Lubuntu 18.04.6 LTS. Firefox version is 112.0.2 32 bit
xralf (15189 rep)
May 12, 2023, 06:35 PM • Last activity: May 13, 2025, 04:25 PM
23 votes
1 answers
18503 views
Chrome crashes with subprocess module and missing CPU frequency files on Ubuntu 21.10
When I open Chrome with a Python module named `subprocess`, it crashes and gives me these errors: [1103/163807.480539:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2) [1103/163807.480673:ERROR:file_io_posix.cc(144)] open /sys/devi...
When I open Chrome with a Python module named subprocess, it crashes and gives me these errors: [1103/163807.480539:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2) [1103/163807.480673:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2) Here are my arguments
google-chrome --disable-gpu \
              --start-maximized \
              --new-window \
              -incognito http://localhost:9932/
OS: Ubuntu 21.10 x86_64 User : root Chrome Version : Chrome crashes when I open it
atkn (331 rep)
Nov 3, 2021, 04:43 PM • Last activity: May 10, 2025, 03:03 PM
0 votes
0 answers
21 views
Crash utility cannot resolve "p2m_top" when analyzing VMware dump (VMEM) on AlmaLinux guest
I am trying to analyze a VMware memory dump from an AlmaLinux guest. I converted the snapshot to a core dump using vmss2core: ``` vmss2core-sb-8456865.exe -N vSRV1_Snapshot815.vmsn vSRV1_Snapshot815.vmem ``` Then, I installed the necessary tools for crash dump analysis: ``` sudo dnf install yum-util...
I am trying to analyze a VMware memory dump from an AlmaLinux guest. I converted the snapshot to a core dump using vmss2core:
vmss2core-sb-8456865.exe -N vSRV1_Snapshot815.vmsn vSRV1_Snapshot815.vmem
Then, I installed the necessary tools for crash dump analysis:
sudo dnf install yum-utils -y
sudo dnf install kexec-tools crash gdb -y
sudo dnf debuginfo-install kernel-debuginfo-$(uname -r) -y
However, when I try to analyze the dump with crash, I get an error:
crash /usr/lib/debug/lib/modules/4.18.0-553.34.1.el8_10.x86_64/vmlinux /home2/memdump/vmss.core
crash: cannot resolve "p2m_top"
Any advice on how to properly analyze this dump or work around the p2m_top error? Thanks.
supmethods (561 rep)
Apr 1, 2025, 02:55 AM
0 votes
0 answers
62 views
Repeated server shutdown with same command - Unable to diagnose
**Problem** I have an unknow critical issue with my personal server, that causes shutdown (server turn off) I tried to watch severals elements, that i'll try to summarize here, with still no clues about the crash reason. As a (forced) beginner in server crash analysis, I am having difficulty finding...
**Problem** I have an unknow critical issue with my personal server, that causes shutdown (server turn off) I tried to watch severals elements, that i'll try to summarize here, with still no clues about the crash reason. As a (forced) beginner in server crash analysis, I am having difficulty finding other relevant test to investigate **Context** I'm working with crewai python librarie, and running the main command uv run crewai run causes me a systematic server complete shutdown. The time between executing the command and the crash varies but is mostly less than 10 seconds. In the longest cases, it can be a few minutes. I have also previously hosted a game server and experienced shutdowns even though the service was running with Docker with RAM/CPU limits. I cannot be certain that the cause is the same, but it seems probable. **My configuration** BMAX-Processeur B5A Pro AMD Ryzen 7 5825U, AMD Radeon vec, 16 Go, DDR4, 512 Go, SSD NVMe. Linux with Ubuntu server; Ubuntu 24.04.2 LTS release 24.04 (codename noble) **What I tried** - GPU / CPU / RAM
stress-ng --cpu 16 --vm 2 --vm-bytes 15G --gpu 16 --timeout 600s
--> No crash -
observation during crash command --> Far from max values (~33% RAM, some cores used, low swap usage) - Temperature sensors watch
-n 0.5 sensors
--> Temperature after stress test are higher than last moment before the crash ( Nothing apparent about the crash reason - Last boot logs
-b-1
--> Nothing apparent about the crash reason - Observation of
--> Nothing apparent about the crash reason - RAM test with
--> Test passed Don't hesitate to ask me for more details, information, logs, ... if needed, and thanks in advance for any help.
AnchorInk (1 rep)
Feb 15, 2025, 11:23 PM • Last activity: Feb 15, 2025, 11:42 PM
18 votes
3 answers
14255 views
How can I recover after Kate crashes?
I use Kate for coding and note-taking. Sometimes it crashes - often when I've got a lot open. Unsaved 'real' documents (eg, ones backed by files, that have been saved at some point) usually have a backup/autosave type recovery file, that more-or-less works. Unfortunately, I've gotten in the habit of...
I use Kate for coding and note-taking. Sometimes it crashes - often when I've got a lot open. Unsaved 'real' documents (eg, ones backed by files, that have been saved at some point) usually have a backup/autosave type recovery file, that more-or-less works. Unfortunately, I've gotten in the habit of using untitled buffers (eg, pressing Ctrln in Kate) to store temporary notes. Kate just crashed and I lost half a dozen of these. Does Kate store backups for 'new' files anywhere? I checked, ~/.kde/share/apps/kate/ and didn't see anything obvious ...
kate-editor 3.8.5
KDE 4.8.5
Ubuntu 12.04 (Don't remember if Kubuntu or Ubuntu + KDE, in case that makes a difference)
hunter2 (417 rep)
Mar 25, 2013, 07:49 AM • Last activity: Jan 6, 2025, 07:39 AM
-1 votes
1 answers
73 views
How can I invoke Steam for Linux in GDB *via its `.desktop` file*?
**Problem** [`steam-1.0.0.82-1.fc41.i686` from RPMFusion](https://fedora.pkgs.org/41/rpmfusion-nonfree-updates-x86_64/steam-devices-1.0.0.82-1.fc41.i686.rpm.html) is crashing for me upon startup (when invoked from $HOME/.local/share/applications/steam.desktop ). An example of this is visible at [`yo...
**Problem** [steam-1.0.0.82-1.fc41.i686 from RPMFusion](https://fedora.pkgs.org/41/rpmfusion-nonfree-updates-x86_64/steam-devices-1.0.0.82-1.fc41.i686.rpm.html) is crashing for me upon startup (when invoked from $HOME/.local/share/applications/steam.desktop). An example of this is visible at [youtu.be/jZQqvgGneSc](https://www.youtube.com/watch?v=jZQqvgGneSc#:~:text=0:06%20/%200:15-,+2024%2D12%2D04T00:24:48+00:00%5BEurope/London%5D%5Bca%2Diso8601%5D,-Unlisted) . As the undermentioned .KCrash file demonstrates drkonqi-coredump-gui doesn't produce a useful trace for it: ~~~YAML PID: 160667 (steamwebhelper) UID: 1000 (RokeJulianLockhart) GID: 1000 (RokeJulianLockhart) Signal: 11 (SEGV) Timestamp: Tue 2024-12-03 17:56:53 GMT (3h 37min ago) Command Line: ./steamwebhelper -lang=en_US -cachedir=/home/RokeJulianLockhart/.local/share/Steam/config/htmlcache -steampid=159838 -buildid=1731433018 -steamid=76561198832168690 -logdir=/home/RokeJulianLockhart/.local/share/Steam/logs -uimode=7 -startcount=1 -steamuniverse=Public -realm=Global -clientui=/home/RokeJulianLockhart/.local/share/Steam/clientui -steampath=/home/RokeJulianLockhart/.local/share/Steam/ubuntu12_32/steam -launcher=0 -no-restart-on-ui-mode-change --valve-enable-site-isolation --enable-smooth-scrolling --password-store=basic --log-file=/home/RokeJulianLockhart/.local/share/Steam/logs/cef_log.txt --disable-quick-menu --enable-features=PlatformHEVCDecoderSupport --disable-features=SpareRendererForSitePerProcess,DcheckIsFatal,ValveFFmpegAllowLowDelayHEVC Executable: /home/RokeJulianLockhart/.local/share/Steam/ubuntu12_64/steamwebhelper Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-steam@16d13b83ca27431bab21f6fb66833e8e.service Unit: user@1000.service User Unit: app-steam@16d13b83ca27431bab21f6fb66833e8e.service Slice: user-1000.slice Owner UID: 1000 (RokeJulianLockhart) Boot ID: c12448e213c144b18ffc5a0816158a6a Machine ID: 8962ec69d8de46f6b8ebc778a4ca76cb Hostname: SNRW3Q Storage: /var/lib/systemd/coredump/core.steamwebhelper.1000.c12448e213c144b18ffc5a0816158a6a.160667.1733248613000000.zst (present) Size on Disk: 6.6M Message: Process 160667 (steamwebhelper) of user 1000 dumped core. Module /run/host/usr/lib64/libxcb-glx.so.0.0.0 from rpm libxcb-1.17.0-3.fc41.x86_64 Module /run/host/usr/lib64/libGLX_mesa.so.0.0.0 from rpm mesa-24.2.8-1.fc41.x86_64 Module /run/host/usr/lib64/libXxf86vm.so.1.0.0 from rpm libXxf86vm-1.1.5-7.fc41.x86_64 Module /run/host/usr/lib64/libudev.so.1.7.9 from rpm systemd-256.9-2.fc41.x86_64 Module /run/host/usr/lib64/libcap.so.2.70 from rpm libcap-2.70-4.fc41.x86_64 Module /run/host/usr/lib64/libwayland-client.so.0.23.0 from rpm wayland-1.23.0-2.fc41.x86_64 Module /run/host/usr/lib64/libxml2.so.2.12.8 from rpm libxml2-2.12.8-2.fc41.x86_64 Module /run/host/usr/lib64/libunistring.so.5.0.0 from rpm libunistring-1.1-8.fc41.x86_64 Module /run/host/usr/lib64/libedit.so.0.0.74 from rpm libedit-3.1-53.20240808cvs.fc41.x86_64 Module /run/host/usr/lib64/libpciaccess.so.0.11.1 from rpm libpciaccess-0.16-13.fc41.x86_64 Module /run/host/usr/lib64/libffi.so.8.1.4 from rpm libffi-3.4.6-3.fc41.x86_64 Module /run/host/usr/lib64/libxcb-dri2.so.0.0.0 from rpm libxcb-1.17.0-3.fc41.x86_64 Module /run/host/usr/lib64/libdrm_intel.so.1.123.0 from rpm libdrm-2.4.123-1.fc41.x86_64 Module /run/host/usr/lib64/libdrm_amdgpu.so.1.123.0 from rpm libdrm-2.4.123-1.fc41.x86_64 Module /run/host/usr/lib64/libelf-0.192.so from rpm elfutils-0.192-6.fc41.x86_64 Module /run/host/usr/lib64/libdrm_radeon.so.1.123.0 from rpm libdrm-2.4.123-1.fc41.x86_64 Module /run/host/usr/lib64/libsensors.so.4.5.0 from rpm lm_sensors-3.6.0-20.fc41.x86_64 Module /run/host/usr/lib64/libxshmfence.so.1.0.0 from rpm libxshmfence-1.3.2-5.fc41.x86_64 Module /run/host/usr/lib64/libxcb-sync.so.1.0.0 from rpm libxcb-1.17.0-3.fc41.x86_64 Module /run/host/usr/lib64/libxcb-xfixes.so.0.0.0 from rpm libxcb-1.17.0-3.fc41.x86_64 Module /run/host/usr/lib64/libxcb-present.so.0.0.0 from rpm libxcb-1.17.0-3.fc41.x86_64 Module /run/host/usr/lib64/libxcb-dri3.so.0.1.0 from rpm libxcb-1.17.0-3.fc41.x86_64 Module /run/host/usr/lib64/libX11-xcb.so.1.0.0 from rpm libX11-1.8.10-2.fc41.x86_64 Module /run/host/usr/lib64/libglapi.so.0.0.0 from rpm mesa-24.2.8-1.fc41.x86_64 Module /run/host/usr/lib64/libidn2.so.0.4.0 from rpm libidn2-2.3.7-2.fc41.x86_64 Module /run/host/usr/lib64/libzstd.so.1.5.6 from rpm zstd-1.5.6-2.fc41.x86_64 Module /run/host/usr/lib64/liblzma.so.5.6.2 from rpm xz-5.6.2-2.fc41.x86_64 Module /run/host/usr/lib64/libgallium-24.2.8.so from rpm mesa-24.2.8-1.fc41.x86_64 Module /run/host/usr/lib64/libxcb-shm.so.0.0.0 from rpm libxcb-1.17.0-3.fc41.x86_64 Module /run/host/usr/lib64/libxcb-randr.so.0.1.0 from rpm libxcb-1.17.0-3.fc41.x86_64 Module /run/host/usr/lib64/libwayland-server.so.0.23.0 from rpm wayland-1.23.0-2.fc41.x86_64 Module /run/host/usr/lib64/libXau.so.6.0.0 from rpm libXau-1.0.11-7.fc41.x86_64 Module /run/host/usr/lib64/libGLdispatch.so.0.0.0 from rpm libglvnd-1.7.0-5.fc41.x86_64 Module /run/host/usr/lib64/libGLX.so.0.0.0 from rpm libglvnd-1.7.0-5.fc41.x86_64 Module /run/host/usr/lib64/libz.so.1.3.1.zlib-ng from rpm zlib-ng-2.1.7-3.fc41.x86_64 Module /run/host/usr/lib64/libgbm.so.1.0.0 from rpm mesa-24.2.8-1.fc41.x86_64 Module /run/host/usr/lib64/libxcb.so.1.1.0 from rpm libxcb-1.17.0-3.fc41.x86_64 Module /run/host/usr/lib64/libexpat.so.1.10.0 from rpm expat-2.6.4-1.fc41.x86_64 Module /run/host/usr/lib64/libXfixes.so.3.1.0 from rpm libXfixes-6.0.1-4.fc41.x86_64 Module /run/host/usr/lib64/libdrm.so.2.123.0 from rpm libdrm-2.4.123-1.fc41.x86_64 Module /run/host/usr/lib64/libGL.so.1.7.0 from rpm libglvnd-1.7.0-5.fc41.x86_64 Module /run/host/usr/lib64/libX11.so.6.4.0 from rpm libX11-1.8.10-2.fc41.x86_64 Module /run/host/usr/lib64/libXext.so.6.4.0 from rpm libXext-1.3.6-2.fc41.x86_64 Stack trace of thread 160771: #0 0x0000000000000000 n/a (n/a + 0x0) ELF object binary architecture: AMD x86-64 ~~~ I presume that this is due to the undermentioned:
RokeJulianLockhart@SNRW3Q:~$ file /usr/bin/steam
/usr/bin/steam: symbolic link to /usr/lib/steam/bin_steam.sh
RokeJulianLockhart@SNRW3Q:~$ file /usr/lib/steam/bin_steam.sh
/usr/lib/steam/bin_steam.sh: Bourne-Again shell script, ASCII text executable
Consequently, I want to capture a stack trace (using gdb), so that I can report this crash to [bugzilla.rpmfusion.org/enter_bug.cgi?product=Fedora](https://bugzilla.rpmfusion.org/enter_bug.cgi?product=Fedora) . (It's not a duplicate of [/show_bug.cgi?id=6900#c6](https://bugzilla.rpmfusion.org/show_bug.cgi?id=6900#c6).) Preventing me doing is so, is that, incredibly, it does not crash when invoked via bash (in konsole): ~~~bash #!/usr/bin/env -S bash steam ~~~ That inability to make it crash in the shell is why I'm unable to debug the source of it crashing, because the undermentioned is of no use: ~~~bash #!/usr/bin/env -S bash DEBUGGER=gdb steam ~~~ **Attempted Solutions** Consequently, I have attempted to add the diagnostic information to its .desktop file. To demonstrate what I have modified, by default, its content is the undermentioned: ~~~desktop [Desktop Action BigPicture] Exec=steam steam://open/bigpicture Name=Big Picture [Desktop Action Community] Exec=steam steam://url/SteamIDControlPage Name=Community Name[bg]=Общност Name[cs]=Komunita Name[da]=Fællesskab Name[de]=Community Name[el]=Κοινότητα Name[es]=Comunidad Name[fi]=Yhteisö Name[fr]=Communauté Name[hu]=Közösség Name[it]=Comunità Name[ja]=コミュニティ Name[ko]=커뮤니티 Name[nl]=Community Name[no]=Samfunn Name[pl]=Społeczność Name[pt_BR]=Comunidade Name[pt_PT]=Comunidade Name[ro]=Comunitate Name[ru]=Сообщество Name[sv]=Gemenskap Name[th]=ชุมชน Name[tr]=Topluluk Name[uk]=Спільнота Name[vi]=Cộng đồng Name[zh_CN]=社区 Name[zh_TW]=社群 [Desktop Action Friends] Exec=steam steam://open/friends Name=Friends Name[bg]=Приятели Name[cs]=Přátelé Name[da]=Venner Name[de]=Freunde Name[el]=Φίλοι Name[es]=Amigos Name[fi]=Kaverit Name[fr]=Amis Name[hu]=Barátok Name[it]=Amici Name[ja]=フレンド Name[ko]=친구 Name[nl]=Vrienden Name[no]=Venner Name[pl]=Znajomi Name[pt_BR]=Amigos Name[pt_PT]=Amigos Name[ro]=Prieteni Name[ru]=Друзья Name[sv]=Vänner Name[th]=เพื่อน Name[tr]=Arkadaşlar Name[uk]=Друзі Name[vi]=Bạn bè Name[zh_CN]=好友 Name[zh_TW]=好友 [Desktop Action Library] Exec=steam steam://open/games Name=Library Name[bg]=Библиотека Name[cs]=Knihovna Name[da]=Bibliotek Name[de]=Bibliothek Name[el]=Συλλογή Name[es]=Biblioteca Name[fi]=Kokoelma Name[fr]=Bibliothèque Name[hu]=Könyvtár Name[it]=Libreria Name[ja]=ライブラリ Name[ko]=라이브러리 Name[nl]=Bibliotheek Name[no]=Bibliotek Name[pl]=Biblioteka Name[pt_BR]=Biblioteca Name[pt_PT]=Biblioteca Name[ro]=Colecţie Name[ru]=Библиотека Name[sv]=Bibliotek Name[th]=คลัง Name[tr]=Kütüphane Name[uk]=Бібліотека Name[vi]=Thư viện Name[zh_CN]=库 Name[zh_TW]=收藏庫 [Desktop Action News] Exec=steam steam://open/news Name=News Name[bg]=Новини Name[cs]=Zprávy Name[da]=Nyheder Name[de]=Neuigkeiten Name[el]=Νέα Name[es]=Noticias Name[fi]=Uutiset Name[fr]=Actualités Name[hu]=Hírek Name[it]=Notizie Name[ja]=ニュース Name[ko]=뉴스 Name[nl]=Nieuws Name[no]=Nyheter Name[pl]=Aktualności Name[pt_BR]=Notícias Name[pt_PT]=Novidades Name[ro]=Știri Name[ru]=Новости Name[sv]=Nyheter Name[th]=ข่าวสาร Name[tr]=Haberler Name[uk]=Новини Name[vi]=Tin tức Name[zh_CN]=新闻 Name[zh_TW]=新聞 [Desktop Action Screenshots] Exec=steam steam://open/screenshots Name=Screenshots Name[bg]=Снимки Name[cs]=Snímky obrazovky Name[da]=Skærmbilleder Name[de]=Screenshots Name[el]=Φωτογραφίες Name[es]=Capturas Name[fi]=Kuvankaappaukset Name[fr]=Captures d'écran Name[hu]=Képernyőmentések Name[it]=Screenshot Name[ja]=スクリーンショット Name[ko]=스크린샷 Name[nl]=Screenshots Name[no]=Skjermbilder Name[pl]=Zrzuty ekranu Name[pt_BR]=Capturas de tela Name[pt_PT]=Capturas de ecrã Name[ro]=Capturi de ecran Name[ru]=Скриншоты Name[sv]=Skärmdumpar Name[th]=ภาพหน้าจอ Name[tr]=Ekran Görüntüleri Name[uk]=Скріншоти Name[vi]=Ảnh chụp Name[zh_CN]=截图 Name[zh_TW]=螢幕擷圖 [Desktop Action Servers] Exec=steam steam://open/servers Name=Servers Name[bg]=Сървъри Name[cs]=Servery Name[da]=Servere Name[de]=Server Name[el]=Διακομιστές Name[es]=Servidores Name[fi]=Palvelimet Name[fr]=Serveurs Name[hu]=Szerverek Name[it]=Server Name[ja]=サーバー Name[ko]=서버 Name[nl]=Servers Name[no]=Tjenere Name[pl]=Serwery Name[pt_BR]=Servidores Name[pt_PT]=Servidores Name[ro]=Servere Name[ru]=Серверы Name[sv]=Servrar Name[th]=เซิร์ฟเวอร์ Name[tr]=Sunucular Name[uk]=Сервери Name[vi]=Máy chủ Name[zh_CN]=服务器 Name[zh_TW]=伺服器 [Desktop Action Settings] Exec=steam steam://open/settings Name=Settings Name[bg]=Настройки Name[cs]=Nastavení Name[da]=Indstillinger Name[de]=Einstellungen Name[el]=Ρυθμίσεις Name[es]=Parámetros Name[fi]=Asetukset Name[fr]=Paramètres Name[hu]=Beállítások Name[it]=Impostazioni Name[ja]=設定 Name[ko]=설정 Name[nl]=Instellingen Name[no]=Innstillinger Name[pl]=Ustawienia Name[pt_BR]=Configurações Name[pt_PT]=Definições Name[ro]=Setări Name[ru]=Настройки Name[sv]=Inställningar Name[th]=การตั้งค่า Name[tr]=Ayarlar Name[uk]=Налаштування Name[vi]=Thiết lập Name[zh_CN]=设置 Name[zh_TW]=設定 [Desktop Action Store] Exec=steam steam://store Name=Store Name[bg]=Магазин Name[cs]=Obchod Name[da]=Butik Name[de]=Shop Name[el]=ΚΑΤΑΣΤΗΜΑ Name[es]=Tienda Name[fi]=Kauppa Name[fr]=Magasin Name[hu]=Áruház Name[it]=Negozio Name[ja]=ストア Name[ko]=상점 Name[nl]=Winkel Name[no]=Butikk Name[pl]=Sklep Name[pt_BR]=Loja Name[pt_PT]=Loja Name[ro]=Magazin Name[ru]=Магазин Name[sv]=Butik Name[th]=ร้านค้า Name[tr]=Mağaza Name[uk]=Крамниця Name[vi]=Cửa hàng Name[zh_CN]=商店 Name[zh_TW]=商店 [Desktop Entry] Actions=Store;Community;Library;Servers;Screenshots;News;Settings;BigPicture;Friends; Categories=Network;FileTransfer;Game; Comment[en_GB]=Application for managing and playing games on Steam Comment=Application for managing and playing games on Steam Comment[bg]=Приложение за ръководене и пускане на игри в Steam Comment[cs]=Aplikace pro spravování a hraní her ve službě Steam Comment[da]=Applikation til at håndtere og spille spil på Steam Comment[de]=Anwendung zum Verwalten und Spielen von Spielen auf Steam Comment[el]=Εφαρμογή διαχείρισης παιχνιδιών στο Steam Comment[es]=Aplicación para administrar y ejecutar juegos en Steam Comment[fi]=Steamin pelien hallintaan ja pelaamiseen tarkoitettu sovellus Comment[fr]=Application de gestion et d'utilisation des jeux sur Steam Comment[hu]=Alkalmazás a Steames játékok futtatásához és kezeléséhez Comment[it]=Applicazione per la gestione e l'esecuzione di giochi su Steam Comment[ja]=Steam 上でゲームを管理&プレイするためのアプリケーション Comment[ko]=Steam에 있는 게임을 관리하고 플레이할 수 있는 응용 프로그램 Comment[nl]=Applicatie voor het beheer en het spelen van games op Steam Comment[no]=Program for å administrere og spille spill på Steam Comment[pl]=Aplikacja do zarządzania i uruchamiania gier na platformie Steam Comment[pt_BR]=Aplicativo para jogar e gerenciar jogos no Steam Comment[pt_PT]=Aplicação para organizar e executar jogos no Steam Comment[ro]=Aplicație pentru administrarea și jucatul jocurilor pe Steam Comment[ru]=Приложение для игр и управления играми в Steam Comment[sv]=Ett program för att hantera samt spela spel på Steam Comment[th]=โปรแกรมสำหรับจัดการและเล่นเกมบน Steam Comment[tr]=Steam üzerinden oyun oynama ve düzenleme uygulaması Comment[uk]=Програма для керування іграми та запуску ігор у Steam Comment[vi]=Ứng dụng để quản lý và chơi trò chơi trên Steam Comment[zh_CN]=管理和进行 Steam 游戏的应用程序 Comment[zh_TW]=管理並執行 Steam 遊戲的應用程式 Exec=env /usr/bin/steam %U GenericName[en_GB]= GenericName= Icon=steam MimeType= Name[en_GB]=Steam Name=Steam Path= PrefersNonDefaultGPU=true StartupNotify=true Terminal=false TerminalOptions=\s--noclose Type=Application X-KDE-RunOnDiscreteGpu=true X-KDE-SubstituteUID=false X-KDE-Username= ~~~ I then modify it as the undermentioned demonstrate: 1. ~~~diff - Exec=env /usr/bin/steam %U + Exec=env 'DEBUGGER=gdb --args /usr/bin/steam' %U ~~~ 2. ~~~diff - Terminal=false + Terminal=true ~~~ This becomes the undermentioned: ~~~desktop [Desktop Action BigPicture] Exec=steam steam://open/bigpicture Name=Big Picture [Desktop Action Community] Exec=steam steam://url/SteamIDControlPage Name=Community Name[bg]=Общност Name[cs]=Komunita Name[da]=Fællesskab Name[de]=Community Name[el]=Κοινότητα Name[es]=Comunidad Name[fi]=Yhteisö Name[fr]=Communauté Name[hu]=Közösség Name[it]=Comunità Name[ja]=コミュニティ Name[ko]=커뮤니티 Name[nl]=Community Name[no]=Samfunn Name[pl]=Społeczność Name[pt_BR]=Comunidade Name[pt_PT]=Comunidade Name[ro]=Comunitate Name[ru]=Сообщество Name[sv]=Gemenskap Name[th]=ชุมชน Name[tr]=Topluluk Name[uk]=Спільнота Name[vi]=Cộng đồng Name[zh_CN]=社区 Name[zh_TW]=社群 [Desktop Action Friends] Exec=steam steam://open/friends Name=Friends Name[bg]=Приятели Name[cs]=Přátelé Name[da]=Venner Name[de]=Freunde Name[el]=Φίλοι Name[es]=Amigos Name[fi]=Kaverit Name[fr]=Amis Name[hu]=Barátok Name[it]=Amici Name[ja]=フレンド Name[ko]=친구 Name[nl]=Vrienden Name[no]=Venner Name[pl]=Znajomi Name[pt_BR]=Amigos Name[pt_PT]=Amigos Name[ro]=Prieteni Name[ru]=Друзья Name[sv]=Vänner Name[th]=เพื่อน Name[tr]=Arkadaşlar Name[uk]=Друзі Name[vi]=Bạn bè Name[zh_CN]=好友 Name[zh_TW]=好友 [Desktop Action Library] Exec=steam steam://open/games Name=Library Name[bg]=Библиотека Name[cs]=Knihovna Name[da]=Bibliotek Name[de]=Bibliothek Name[el]=Συλλογή Name[es]=Biblioteca Name[fi]=Kokoelma Name[fr]=Bibliothèque Name[hu]=Könyvtár Name[it]=Libreria Name[ja]=ライブラリ Name[ko]=라이브러리 Name[nl]=Bibliotheek Name[no]=Bibliotek Name[pl]=Biblioteka Name[pt_BR]=Biblioteca Name[pt_PT]=Biblioteca Name[ro]=Colecţie Name[ru]=Библиотека Name[sv]=Bibliotek Name[th]=คลัง Name[tr]=Kütüphane Name[uk]=Бібліотека Name[vi]=Thư viện Name[zh_CN]=库 Name[zh_TW]=收藏庫 [Desktop Action News] Exec=steam steam://open/news Name=News Name[bg]=Новини Name[cs]=Zprávy Name[da]=Nyheder Name[de]=Neuigkeiten Name[el]=Νέα Name[es]=Noticias Name[fi]=Uutiset Name[fr]=Actualités Name[hu]=Hírek Name[it]=Notizie Name[ja]=ニュース Name[ko]=뉴스 Name[nl]=Nieuws Name[no]=Nyheter Name[pl]=Aktualności Name[pt_BR]=Notícias Name[pt_PT]=Novidades Name[ro]=Știri Name[ru]=Новости Name[sv]=Nyheter Name[th]=ข่าวสาร Name[tr]=Haberler Name[uk]=Новини Name[vi]=Tin tức Name[zh_CN]=新闻 Name[zh_TW]=新聞 [Desktop Action Screenshots] Exec=steam steam://open/screenshots Name=Screenshots Name[bg]=Снимки Name[cs]=Snímky obrazovky Name[da]=Skærmbilleder Name[de]=Screenshots Name[el]=Φωτογραφίες Name[es]=Capturas Name[fi]=Kuvankaappaukset Name[fr]=Captures d'écran Name[hu]=Képernyőmentések Name[it]=Screenshot Name[ja]=スクリーンショット Name[ko]=스크린샷 Name[nl]=Screenshots Name[no]=Skjermbilder Name[pl]=Zrzuty ekranu Name[pt_BR]=Capturas de tela Name[pt_PT]=Capturas de ecrã Name[ro]=Capturi de ecran Name[ru]=Скриншоты Name[sv]=Skärmdumpar Name[th]=ภาพหน้าจอ Name[tr]=Ekran Görüntüleri Name[uk]=Скріншоти Name[vi]=Ảnh chụp Name[zh_CN]=截图 Name[zh_TW]=螢幕擷圖 [Desktop Action Servers] Exec=steam steam://open/servers Name=Servers Name[bg]=Сървъри Name[cs]=Servery Name[da]=Servere Name[de]=Server Name[el]=Διακομιστές Name[es]=Servidores Name[fi]=Palvelimet Name[fr]=Serveurs Name[hu]=Szerverek Name[it]=Server Name[ja]=サーバー Name[ko]=서버 Name[nl]=Servers Name[no]=Tjenere Name[pl]=Serwery Name[pt_BR]=Servidores Name[pt_PT]=Servidores Name[ro]=Servere Name[ru]=Серверы Name[sv]=Servrar Name[th]=เซิร์ฟเวอร์ Name[tr]=Sunucular Name[uk]=Сервери Name[vi]=Máy chủ Name[zh_CN]=服务器 Name[zh_TW]=伺服器 [Desktop Action Settings] Exec=steam steam://open/settings Name=Settings Name[bg]=Настройки Name[cs]=Nastavení Name[da]=Indstillinger Name[de]=Einstellungen Name[el]=Ρυθμίσεις Name[es]=Parámetros Name[fi]=Asetukset Name[fr]=Paramètres Name[hu]=Beállítások Name[it]=Impostazioni Name[ja]=設定 Name[ko]=설정 Name[nl]=Instellingen Name[no]=Innstillinger Name[pl]=Ustawienia Name[pt_BR]=Configurações Name[pt_PT]=Definições Name[ro]=Setări Name[ru]=Настройки Name[sv]=Inställningar Name[th]=การตั้งค่า Name[tr]=Ayarlar Name[uk]=Налаштування Name[vi]=Thiết lập Name[zh_CN]=设置 Name[zh_TW]=設定 [Desktop Action Store] Exec=steam steam://store Name=Store Name[bg]=Магазин Name[cs]=Obchod Name[da]=Butik Name[de]=Shop Name[el]=ΚΑΤΑΣΤΗΜΑ Name[es]=Tienda Name[fi]=Kauppa Name[fr]=Magasin Name[hu]=Áruház Name[it]=Negozio Name[ja]=ストア Name[ko]=상점 Name[nl]=Winkel Name[no]=Butikk Name[pl]=Sklep Name[pt_BR]=Loja Name[pt_PT]=Loja Name[ro]=Magazin Name[ru]=Магазин Name[sv]=Butik Name[th]=ร้านค้า Name[tr]=Mağaza Name[uk]=Крамниця Name[vi]=Cửa hàng Name[zh_CN]=商店 Name[zh_TW]=商店 [Desktop Entry] Actions=Store;Community;Library;Servers;Screenshots;News;Settings;BigPicture;Friends; Categories=Network;FileTransfer;Game; Comment[en_GB]=Application for managing and playing games on Steam Comment=Application for managing and playing games on Steam Comment[bg]=Приложение за ръководене и пускане на игри в Steam Comment[cs]=Aplikace pro spravování a hraní her ve službě Steam Comment[da]=Applikation til at håndtere og spille spil på Steam Comment[de]=Anwendung zum Verwalten und Spielen von Spielen auf Steam Comment[el]=Εφαρμογή διαχείρισης παιχνιδιών στο Steam Comment[es]=Aplicación para administrar y ejecutar juegos en Steam Comment[fi]=Steamin pelien hallintaan ja pelaamiseen tarkoitettu sovellus Comment[fr]=Application de gestion et d'utilisation des jeux sur Steam Comment[hu]=Alkalmazás a Steames játékok futtatásához és kezeléséhez Comment[it]=Applicazione per la gestione e l'esecuzione di giochi su Steam Comment[ja]=Steam 上でゲームを管理&プレイするためのアプリケーション Comment[ko]=Steam에 있는 게임을 관리하고 플레이할 수 있는 응용 프로그램 Comment[nl]=Applicatie voor het beheer en het spelen van games op Steam Comment[no]=Program for å administrere og spille spill på Steam Comment[pl]=Aplikacja do zarządzania i uruchamiania gier na platformie Steam Comment[pt_BR]=Aplicativo para jogar e gerenciar jogos no Steam Comment[pt_PT]=Aplicação para organizar e executar jogos no Steam Comment[ro]=Aplicație pentru administrarea și jucatul jocurilor pe Steam Comment[ru]=Приложение для игр и управления играми в Steam Comment[sv]=Ett program för att hantera samt spela spel på Steam Comment[th]=โปรแกรมสำหรับจัดการและเล่นเกมบน Steam Comment[tr]=Steam üzerinden oyun oynama ve düzenleme uygulaması Comment[uk]=Програма для керування іграми та запуску ігор у Steam Comment[vi]=Ứng dụng để quản lý và chơi trò chơi trên Steam Comment[zh_CN]=管理和进行 Steam 游戏的应用程序 Comment[zh_TW]=管理並執行 Steam 遊戲的應用程式 Exec=env 'DEBUGGER=gdb --args /usr/bin/steam' %U GenericName[en_GB]= GenericName= Icon=steam MimeType= Name[en_GB]=Steam Name=Steam Path= PrefersNonDefaultGPU=true StartupNotify=true Terminal=true TerminalOptions=\s--noclose Type=Application X-KDE-RunOnDiscreteGpu=true X-KDE-SubstituteUID=false X-KDE-Username= ~~~ The aforementioned doesn't work, for although Terminal=true makes me see that the variable has been passed, I do not see the gdb CLI: Screenshot **Potential Solutions** I may be able to spawn an interactive shell by using the instructions in [/revisions/682872/4](https://superuser.com/revisions/682872/4) . However, I don't much understand them; much less so, how to implement them in a .desktop file. **Corroborations** This situation appears to be similar to [bbs.archlinux.org/viewtopic.php?id=295425](https://bbs.archlinux.org/viewtopic.php?id=295425) . However, their solution is irrelevant to mine, because I've no NVIDIA hardware.
RokeJulianLockhart (541 rep)
Dec 3, 2024, 09:50 PM • Last activity: Dec 9, 2024, 11:33 PM
6 votes
1 answers
771 views
bash pipe loses data when command crashed
Consider this simple program (`abort.py`) that writes some text to `stdout` and `stderr` and then crashed (`abort()`). ```python import os import sys print("end stdout") print("end stderr", file=sys.stderr) os.abort() ``` When I run it in terminal, both output to `stdout` and `stderr` are correctly...
Consider this simple program (abort.py) that writes some text to stdout and stderr and then crashed (abort()).
import os
import sys

print("end stdout")
print("end stderr", file=sys.stderr)
os.abort()
When I run it in terminal, both output to stdout and stderr are correctly produced.
$ python3 abort.py 
end stdout
end stderr
Aborted (core dumped)
However, if I were to redirect stdout and/or stderr to another program (perhaps for logging purpose), it doesn't work any more.
$ python3 abort.py | cat
end stderr

$ python3 abort.py |& cat

$ python3 abort.py | tee -a logs
end stderr

$ python3 abort.py |& tee -a logs

# file logs is unchanged
In fact, if the program (abort.py) produce a lot of texts to stdout and stderr, **only the last section of them is lost** from the perspective of the receiving program on the other end of the pipe. I also tried running the program in a bash script and run that script, but the result is the same. Why is this happening and how should I fix it? ### Background The example above is obviously contrived. The real world scenario is that I was debugging a large program that occasionally crash (segfault or aborted) after running for days. It produces a lot of logs to both stdout and stderr, but the most important piece of information regarding its crash (such as stack trace) is printed in the end right before the crash happens. I have a logging pipeline setup in a bash script (involves some tee and gzip for example), but I found that last section of the log saved is always missing, which is frustrating.
lewisxy (171 rep)
Dec 3, 2024, 08:48 AM • Last activity: Dec 3, 2024, 03:48 PM
0 votes
0 answers
149 views
Rocky Linux 9.4 constant crashes with new GPU
I do 3d art and was excited to get a new GPU, 7900XT. Week Before getting it, my grub corrupted because I resized my lvm partitions and moved them around, so now I have to manually boot through grub>. After installing the new GPU, my system has become very unstable. Here are some observations I made...
I do 3d art and was excited to get a new GPU, 7900XT. Week Before getting it, my grub corrupted because I resized my lvm partitions and moved them around, so now I have to manually boot through grub>. After installing the new GPU, my system has become very unstable. Here are some observations I made(all of these apply to both Wayland and X11 KDE plasma): - if I boot and log into either Wayland or X11, and don't move my mouse, the mouse will freeze within 3 minutes, then screen turns black, and my system will reboot on it's own. - if I boot and log, then asap open a browser and start a YouTube video, I know the system won't hang as long as the video is playing.(??) If I pause it, the system might or might not hang and reboot. It's a gamble. If it doesn't hang a few mins after pausing, then I can go for hours without issue. - Journalctl reports nothing that could explain these crashes. - the pc works fine if I stay in ctrl-alt-f3 or other (I think it's called tty?) any nongraphical session is stable. I tried the following: - updating motherboard bios - updating amd drivers manually (amdgpu_install from their proprietary repo) - changing session types (x11) My current boot process: 1. Fail at bios cause my usb keyboard fails to detect. 2. Reboot 3. Get to GRUB cli cause my grub/efi broke and I can't fix it for a week now, so I have to manualy type: 3.1. set root=(hd0,gpt4) 3.2. linux /vmlinuz-5....7..... root=/dev/mapper/rl-root 3.3. initrd /initramfs-5...7.... 3.4. boot 4. Log into Linux, wait 1 min for it to crash. 4.1. MAYBE if I immediately start browser and yt video on boot, the system seems to crash way less likely on first/second boot?! 5. Redo everything above except 4, cause now there's a 50/50 chance it will stay working. 6. Repeat five, chances it stays stable increase every reboot 7. Profit (10min later?) From what I saw online, Wayland and kernel weren't saying nicely with the 7900xt till recently, so the only solution I can think of is to compile a custom kernel with latest version and use that (then what's the point of using rhel9...) or maybe only latest Wayland (GCC is outdated on rhel9, so I can't.) Please give me some ideas how to fix it. I really don't want to reinstall. It would take me a week to get all the programs I need set up again, and many of them don't work on other distros(davinci resolve only works on rhel7-9, even provide a custom distro just for their program...) inxi:
djkato@djkato-vfx ~> inxi -I -G
Graphics:
  Device-1: AMD Navi 31 [Radeon RX 7900 XT/7900 XTX/7900 GRE/7900M]
    driver: amdgpu v: 6.8.5
  Device-2: AMD Raphael driver: amdgpu v: 6.8.5
  Display: wayland server: X.org v: 1.20.11 with: Xwayland v: 22.1.9
    compositor: kwin_wayland driver: X: loaded: amdgpu unloaded: modesetting
    dri: radeonsi gpu: amdgpu,amdgpu resolution: 1: 3072x1728 2: 2560x1440
  API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast
    platforms: gbm,wayland,x11,surfaceless,device
  API: OpenGL v: 4.6 vendor: amd mesa v: 24.2.0-devel renderer: Radeon RX
    7900 XT (radeonsi navi31 LLVM 18.1.7 DRM 3.58
    5.14.0-427.37.1.el9_4.x86_64)
  API: Vulkan v: 1.3.268 drivers: radv,llvmpipe surfaces: xcb,xlib,wayland
Info:
  Memory: total: 32 GiB note: est. available: 30.5 GiB used: 3.62 GiB (11.9%)
  Processes: 366 Uptime: 26m Shell: fish inxi: 3.3.33
djkato (101 rep)
Oct 16, 2024, 02:06 PM • Last activity: Nov 4, 2024, 09:53 AM
0 votes
0 answers
75 views
Where is vmlinux file for crash dump
I have setup kdump to help me diagnose a kernel crash (per redhat docs). I've gotten as far as creating the dump file, and now want to examine the crash dump file. The instructions say to execute (for example): crash /usr/lib/debug/lib/modules/4.18.0-5.el8.x86_64/vmlinux /var/crash/127.0.0.1-2018-10...
I have setup kdump to help me diagnose a kernel crash (per redhat docs). I've gotten as far as creating the dump file, and now want to examine the crash dump file. The instructions say to execute (for example): crash /usr/lib/debug/lib/modules/4.18.0-5.el8.x86_64/vmlinux /var/crash/127.0.0.1-2018-10-06-14:05:33/vmcore But I don't have a vmlinux file. I looked int the directory matching my kernel **( /usr/lib/modules/5.14.0-427.37.1.el9_4.x86_64+debug)** and it contains the content shown below. But no vmlinux file! I have a vmlinuz but the crash program didn't like it. Where do I find this vmlinux file, or do I have to create it? lrwxrwxrwx. 1 root root 51 Sep 24 17:25 build -> /usr/src/kernels/5.14.0-427.37.1.el9_4.x86_64+debug -rw-r--r--. 1 root root 224287 Sep 24 17:25 config drwxr-xr-x. 14 root root 156 Oct 5 08:18 kernel -rw-r--r--. 1 root root 879087 Oct 5 08:19 modules.alias -rw-r--r--. 1 root root 834103 Oct 5 08:19 modules.alias.bin -rw-r--r--. 1 root root 461 Sep 24 17:25 modules.block -rw-r--r--. 1 root root 9236 Sep 24 17:25 modules.builtin -rw-r--r--. 1 root root 0 Oct 5 08:19 modules.builtin.alias.bin -rw-r--r--. 1 root root 11585 Oct 5 08:19 modules.builtin.bin -rw-r--r--. 1 root root 75121 Sep 24 17:25 modules.builtin.modinfo -rw-r--r--. 1 root root 307245 Oct 5 08:19 modules.dep -rw-r--r--. 1 root root 400740 Oct 5 08:19 modules.dep.bin -rw-r--r--. 1 root root 387 Oct 5 08:19 modules.devname -rw-r--r--. 1 root root 155 Sep 24 17:25 modules.drm -rw-r--r--. 1 root root 20 Sep 24 17:25 modules.modesetting -rw-r--r--. 1 root root 1648 Sep 24 17:25 modules.networking -rw-r--r--. 1 root root 93145 Sep 24 17:25 modules.order -rw-r--r--. 1 root root 862 Oct 5 08:19 modules.softdep -rw-r--r--. 1 root root 499371 Oct 5 08:19 modules.symbols -rw-r--r--. 1 root root 591632 Oct 5 08:19 modules.symbols.bin lrwxrwxrwx. 1 root root 5 Sep 24 17:25 source -> build -rw-r--r--. 1 root root 404401 Sep 24 17:25 symvers.gz -rw-------. 1 root root 9446409 Sep 24 17:25 System.map drwxr-xr-x. 2 root root 6 Sep 24 17:24 systemtap drwxr-xr-x. 2 root root 6 Sep 24 17:25 updates drwxr-xr-x. 2 root root 40 Oct 5 08:18 vdso -rwxr-xr-x. 1 root root 27304248 Sep 24 17:25 vmlinuz drwxr-xr-x. 2 root root 6 Oct 5 08:19 weak-updates
TSG (1983 rep)
Oct 5, 2024, 12:26 PM
0 votes
0 answers
42 views
Ubuntu Server 18.04 automatically rebooted but no logs per se
I have a hypervisor with Ubuntu Server 18.04, on which several virtual machines are installed, running on VirtualBox. At 23:45, the physical server automatically restarted. I tried to look in syslog and kern.log, but I did not find anything about the system restart Part of syslog at the moment of re...
I have a hypervisor with Ubuntu Server 18.04, on which several virtual machines are installed, running on VirtualBox. At 23:45, the physical server automatically restarted. I tried to look in syslog and kern.log, but I did not find anything about the system restart Part of syslog at the moment of restart
Aug 29 23:38:27 hypervisor dhcpd: DHCPREQUEST for 12.34.56.78 from 08:00:27:75:09:8d via vboxnet0
Aug 29 23:38:27 hypervisor dhcpd: DHCPACK on 12.34.56.78 to 08:00:27:75:09:8d via vboxnet0
Aug 29 23:38:39 hypervisor named: resolver priming query complete
Aug 29 23:39:01 hypervisor CRON: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
Aug 29 23:39:07 hypervisor dhcpd: DHCPREQUEST for 123.234.123.12 from 08:00:27:c3:0c:28 via vboxnet2
Aug 29 23:39:07 hypervisor dhcpd: DHCPACK on 123.234.123.12 to 08:00:27:c3:0c:28 via vboxnet2
Aug 29 23:39:17 hypervisor systemd: Starting Clean php session files...
Aug 29 23:39:18 hypervisor systemd: Started Clean php session files.
Aug 29 23:39:33 hypervisor named: resolver priming query complete
Aug 29 23:40:57 hypervisor dhcpd: DHCPREQUEST for 12.34.56.78 from 08:00:27:75:09:8d via vboxnet0
Aug 29 23:40:57 hypervisor dhcpd: DHCPACK on 12.34.56.78 to 08:00:27:75:09:8d via vboxnet0
Aug 29 23:41:37 hypervisor dhcpd: DHCPREQUEST for 123.234.123.12 from 08:00:27:c3:0c:28 via vboxnet2
Aug 29 23:41:37 hypervisor dhcpd: DHCPACK on 123.234.123.12 to 08:00:27:c3:0c:28 via vboxnet2
Aug 29 23:41:37 hypervisor named: resolver priming query complete
Aug 29 23:43:19 hypervisor named: message repeated 3 times: [ resolver priming query complete]
Aug 29 23:43:27 hypervisor dhcpd: DHCPREQUEST for 12.34.56.78 from 08:00:27:75:09:8d via vboxnet0
Aug 29 23:43:27 hypervisor dhcpd: DHCPACK on 12.34.56.78 to 08:00:27:75:09:8d via vboxnet0
Aug 29 23:43:33 hypervisor named: resolver priming query complete
Aug 29 23:44:07 hypervisor dhcpd: DHCPREQUEST for 123.234.123.12 from 08:00:27:c3:0c:28 via vboxnet2
Aug 29 23:44:07 hypervisor dhcpd: DHCPACK on 123.234.123.12 to 08:00:27:c3:0c:28 via vboxnet2
Aug 29 23:46:03 hypervisor systemd-modules-load: Inserted module 'coretemp'
Aug 29 23:46:03 hypervisor kernel: [    0.000000] microcode: microcode updated early to revision 0xf4, date = 2022-07-31
Aug 29 23:46:03 hypervisor kernel: [    0.000000] Linux version 4.15.0-213-generic (buildd@lcy02-amd64-079) (gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)) #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 (Ubuntu 4.15.0-213.224-generic 4.15.18)
Aug 29 23:46:03 hypervisor kernel: [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-213-generic root=UUID=60a0068c-dde5-4583-8574-98c0a03bb007 ro net.ifnames=0
Aug 29 23:46:03 hypervisor systemd: Started Uncomplicated firewall.
Aug 29 23:46:03 hypervisor kernel: [    0.000000] KERNEL supported cpus:
Aug 29 23:46:03 hypervisor systemd: Starting Flush Journal to Persistent Storage...
Aug 29 23:46:03 hypervisor kernel: [    0.000000]   Intel GenuineIntel
Aug 29 23:46:03 hypervisor kernel: [    0.000000]   AMD AuthenticAMD
Aug 29 23:46:03 hypervisor kernel: [    0.000000]   Centaur CentaurHauls
Aug 29 23:46:03 hypervisor kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Aug 29 23:46:03 hypervisor systemd: Started Set the console keyboard layout.
Aug 29 23:46:03 hypervisor kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Aug 29 23:46:03 hypervisor kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Aug 29 23:46:03 hypervisor kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
Aug 29 23:46:03 hypervisor kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
Aug 29 23:46:03 hypervisor kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User registers'
Aug 29 23:46:03 hypervisor kernel: [    0.000000] x86/fpu: xstate_offset:  576, xstate_sizes:  256
Aug 29 23:46:03 hypervisor kernel: [    0.000000] x86/fpu: xstate_offset:  832, xstate_sizes:   64
Aug 29 23:46:03 hypervisor kernel: [    0.000000] x86/fpu: xstate_offset:  896, xstate_sizes:   64
Aug 29 23:46:03 hypervisor kernel: [    0.000000] x86/fpu: xstate_offset:  960, xstate_sizes:    8
Aug 29 23:46:03 hypervisor systemd: Started Load/Save Random Seed.
Aug 29 23:46:03 hypervisor kernel: [    0.000000] x86/fpu: Enabled xstate features 0x21f, context size is 968 bytes, using 'compacted' format.
kern.log
Aug 26 17:24:07 hypervisor kernel: [4048716.348358] device vboxnet0 left promiscuous mode
Aug 26 17:24:07 hypervisor kernel: [4048716.348379] device vboxnet3 left promiscuous mode
Aug 26 17:24:07 hypervisor kernel: [4048716.418638] vboxnetflt: 8265681 out of 8655381 packets were not sent (directed to host)
Aug 26 17:24:07 hypervisor kernel: [4048716.470636] vboxnetflt: 388 out of 534983 packets were not sent (directed to host)
Aug 26 22:36:39 hypervisor kernel: [4067468.933959] VBoxNetFlt: attached to 'vboxnet0' / 0a:00:27:00:00:00
Aug 26 22:36:39 hypervisor kernel: [4067468.934478] VBoxNetFlt: attached to 'vboxnet3' / 0a:00:27:00:00:03
Aug 26 22:36:39 hypervisor kernel: [4067468.935191] VMMR0InitVM: eflags=246 fKernelFeatures=0x0 (SUPKERNELFEATURES_SMAP=0)
Aug 26 22:36:39 hypervisor kernel: [4067468.936917] device vboxnet0 entered promiscuous mode
Aug 26 22:36:39 hypervisor kernel: [4067468.936929] device vboxnet3 entered promiscuous mode
Aug 26 22:37:11 hypervisor kernel: [4067500.476672] VMMR0InitVM: eflags=246 fKernelFeatures=0x0 (SUPKERNELFEATURES_SMAP=0)
Aug 26 22:39:59 hypervisor kernel: [4067668.448094] device vboxnet0 left promiscuous mode
Aug 26 22:39:59 hypervisor kernel: [4067668.487732] vboxnetflt: 3543 out of 3649 packets were not sent (directed to host)
Aug 26 22:40:25 hypervisor kernel: [4067694.334590] VBoxNetFlt: attached to 'vboxnet0' / 0a:00:27:00:00:00
Aug 26 22:40:25 hypervisor kernel: [4067694.335071] device vboxnet0 entered promiscuous mode
Aug 26 22:42:31 hypervisor kernel: [4067820.931694] device vboxnet3 left promiscuous mode
Aug 26 22:42:31 hypervisor kernel: [4067821.036953] vboxnetflt: 0 out of 529 packets were not sent (directed to host)
Aug 29 23:46:03 hypervisor kernel: [    0.000000] microcode: microcode updated early to revision 0xf4, date = 2022-07-31
Aug 29 23:46:03 hypervisor kernel: [    0.000000] Linux version 4.15.0-213-generic (buildd@lcy02-amd64-079) (gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)) #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 (Ubuntu 4.15.0-213.224-generic 4.15.18)
Aug 29 23:46:03 hypervisor kernel: [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-213-generic root=UUID=60a0068c-dde5-4583-8574-98c0a03bb007 ro net.ifnames=0
Aug 29 23:46:03 hypervisor kernel: [    0.000000] KERNEL supported cpus:
Aug 29 23:46:03 hypervisor kernel: [    0.000000]   Intel GenuineIntel
Aug 29 23:46:03 hypervisor kernel: [    0.000000]   AMD AuthenticAMD
Aug 29 23:46:03 hypervisor kernel: [    0.000000]   Centaur CentaurHauls
Aug 29 23:46:03 hypervisor kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Aug 29 23:46:03 hypervisor kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Aug 29 23:46:03 hypervisor kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Aug 29 23:46:03 hypervisor kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
Aug 29 23:46:03 hypervisor kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
Aug 29 23:46:03 hypervisor kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User registers'
Aug 29 23:46:03 hypervisor kernel: [    0.000000] x86/fpu: xstate_offset:  576, xstate_sizes:  256
Aug 29 23:46:03 hypervisor kernel: [    0.000000] x86/fpu: xstate_offset:  832, xstate_sizes:   64
Aug 29 23:46:03 hypervisor kernel: [    0.000000] x86/fpu: xstate_offset:  896, xstate_sizes:   64
Aug 29 23:46:03 hypervisor kernel: [    0.000000] x86/fpu: xstate_offset:  960, xstate_sizes:    8
Aug 29 23:46:03 hypervisor kernel: [    0.000000] x86/fpu: Enabled xstate features 0x21f, context size is 968 bytes, using 'compacted' format.
Aug 29 23:46:03 hypervisor kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Aug 29 23:46:03 hypervisor kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009dfff] usable
Aug 29 23:46:03 hypervisor kernel: [    0.000000] BIOS-e820: [mem 0x000000000009e000-0x000000000009efff] reserved
Aug 29 23:46:03 hypervisor kernel: [    0.000000] BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] usable
last reboot says (after an unscheduled restart, I rebooted myself once):
reboot   system boot  4.15.0-213-gener Fri Aug 30 00:03   still running
reboot   system boot  4.15.0-213-gener Thu Aug 29 23:45 - 00:03  (00:17)

wtmp begins Thu Aug  1 13:43:08 2024
cat /proc/sys/kernel/panic is 0 The physical server has been running for about 40 days without rebooting. How can I find out the reason for the reboot and prevent this from happening in the future?
Semyon Bayandin (105 rep)
Aug 29, 2024, 09:12 PM
0 votes
0 answers
189 views
FortiClient VPN keeps crashing my computer (Linux)
FortiClient VPN that I use at work keeps crashing/freezing my computer, forcing me to hold down the power button and restart. If I click SAML Login to connect to the VPN via FortiClient GUI, it will work for 3-4 minutes before my whole system freezes. When i'm back in the PC doesn't recognize any ne...
FortiClient VPN that I use at work keeps crashing/freezing my computer, forcing me to hold down the power button and restart. If I click SAML Login to connect to the VPN via FortiClient GUI, it will work for 3-4 minutes before my whole system freezes. When i'm back in the PC doesn't recognize any networks (even though I use an ethernet cable), and I'll have to manually delete all connections before I restart again and everything works like normal. I get no error logs. I am using Ubuntu 24.04 LTS, even though FortiNet doesn't officially support this. The workaround: remove two dependencies (libappindicator1 and libayatana-appindicator1) in the .deb when installing using apt. My FortiClient VPN version is 7.4.0.1636. Any ideas/solutions? Thanks in advance :)
Mats Nerhagen (1 rep)
Aug 15, 2024, 12:54 PM
0 votes
2 answers
113 views
Why is Webex crashing at application startup in AlmaLinux?
I have a fresh install of AlmaLinux and I need Webex for org chat rooms. I've installed Webex through the `Webex.rpm` file provided on their official website. After successfully installing, I tried to sign in with my Webex email and password. After entering my password and clicking "Connect", the We...
I have a fresh install of AlmaLinux and I need Webex for org chat rooms. I've installed Webex through the Webex.rpm file provided on their official website. After successfully installing, I tried to sign in with my Webex email and password. After entering my password and clicking "Connect", the Webex window briefly opens and shows a "loading" spinner, and then immediately closes. Every time I try to relaunch, the same issue happens. I have tried uninstalling & reinstalling the program to no avail. I have found a log file that gets updated with every launch: ~/home/.share/Webex/logArchive/last_run_current_log.txt, but I don't see an error on the last line that tells me what caused the sudden process termination. If I run ps -ax | grep cisco I see a single Cisco process but the PID keeps changing, so it's almost like it's in a non-terminating loop of trying to boot, failing, trying to boot, failing, etc. What the heck is going on? Does anyone have any ideas for ways to figure out what's causing this, or - even better - has anyone gone through this issue and successfully resolved it?
dmcoding (111 rep)
Jul 23, 2024, 06:18 PM • Last activity: Jul 31, 2024, 10:52 PM
0 votes
1 answers
187 views
Missing symbols for libraries when attempting to perform analysing of core dump
I'm trying to analyze core dump files of the systemd process, but encountering errors due to missing symbols. Can anyone advise what debug symbols need to be installed to successfully analyze these core dumps? ``` gdb -e /usr/lib/systemd/systemd-journald -c core-systemd-journal--0-0-657-1718434887 G...
I'm trying to analyze core dump files of the systemd process, but encountering errors due to missing symbols. Can anyone advise what debug symbols need to be installed to successfully analyze these core dumps?
gdb  -e /usr/lib/systemd/systemd-journald -c core-systemd-journal--0-0-657-1718434887
GNU gdb (GDB) Red Hat Enterprise Linux 8.2-20.el8
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
    .

For help, type "help".
Type "apropos word" to search for commands related to "word".

warning: core file may not match specified executable file.
[New LWP 657]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Missing separate debuginfo for /lib64/libuuid.so.1
Try: yum --enablerepo='*debug*' install /usr/lib/debug/.build-id/d0/43572678e11cfb56aecb4ec534bc016de8d0d5.debug
Missing separate debuginfo for /lib64/libudev.so.1
Try: yum --enablerepo='*debug*' install /usr/lib/debug/.build-id/94/5e15d6b231fc346823186cd70e886dede771ca.debug
Core was generated by `/usr/lib/systemd/systemd-journald'.
Program terminated with signal SIGABRT, Aborted.
supmethods (561 rep)
Jul 1, 2024, 02:27 AM • Last activity: Jul 12, 2024, 12:56 AM
Showing page 1 of 20 total questions