#Mint system freezing and crashing (maybe cause of inkscape?)

11 messages · Page 1 of 1 (latest)

solid hedge
#

It's been freezing ever since I started using Inkscape, it doesn't freeze instantly as you open inkscape, but it's happened after having inkscape up for a long time. I don't know how to recover from crash and I can't get the "reisub" sequence to work. What can I do to see what might have gone wrong?
very similar to:
https://www.reddit.com/r/archlinux/comments/1hdm6gq/inkscape_freezes_my_pc/

System:
  Kernel: 6.8.0-63-generic arch: x86_64 bits: 64 compiler: gcc v: 13.3.0
    clocksource: tsc
  Desktop: Cinnamon v: 6.4.8 tk: GTK v: 3.24.41 wm: Muffin v: 6.4.1 vt: 7
    dm: LightDM v: 1.30.0 Distro: Linux Mint 22.1 Xia base: Ubuntu 24.04 noble
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME B360M-A v: Rev X.0x
    serial: <superuser required> part-nu: ASUS_MB_CNL uuid: <superuser required>
    UEFI: American Megatrends v: 2602 date: 07/24/2019
CPU:
  Info: 6-core model: Intel Core i5-9400F bits: 64 type: MCP
    smt: <unsupported> arch: Coffee Lake rev: A cache: L1: 384 KiB L2: 1.5 MiB
    L3: 9 MiB
  Speed (MHz): avg: 800 high: 801 min/max: 800/4100 cores: 1: 800 2: 800
    3: 801 4: 800 5: 800 6: 800 bogomips: 34798
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: NVIDIA TU106 [GeForce RTX 2060 Rev. A] vendor: Micro-Star MSI
    driver: nvidia v: 570.133.07 arch: Turing pcie: speed: 2.5 GT/s lanes: 16
    ports: active: none off: DP-1,HDMI-A-1 empty: DP-2,DP-3 bus-ID: 01:00.0
    chip-ID: 10de:1f08 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 driver: X:
    loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa
    gpu: nvidia,nvidia-nvswitch display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3840x1080 s-dpi: 92 s-size: 1060x301mm (41.73x11.85")
    s-diag: 1102mm (43.38")
  [...]
#

This has happened 3-4 times now

solid hedge
#

Crashed again without inkscape

solid hedge
mental pelican
#

nice

mint axle
#

Can you give the output of mokutil --sb-state?

#

If secureboot is enabled go to your BIOS and disable it completely.

#

If still does not work go into software manager -> View -> Linux kernels and install one from 6.11 series.

frosty jetty
#

I can't get the "reisub" sequence to work

It might be disabled in configuration file. You can set the kernel.sysrq to 1 to enable every key combo. As far as I remember, the change will apply after reboot.

[22:53][1]silence@silence-1991:~$ cat /etc/sysctl.d/10-magic-sysrq.conf 
# The magic SysRq key enables certain keyboard combinations to be
# interpreted by the kernel to help with debugging. The kernel will respond
# to these keys regardless of the current running applications.
#
# In general, the magic SysRq key is not needed for the average Ubuntu
# system, and having it enabled by default can lead to security issues on
# the console such as being able to dump memory or to kill arbitrary
# processes including the running screen lock.
#
# Here is the list of possible values:
#   0 - disable sysrq completely
#   1 - enable all functions of sysrq
#  >1 - enable certain functions by adding up the following values:
#          2 - enable control of console logging level
#          4 - enable control of keyboard (SAK, unraw)
#          8 - enable debugging dumps of processes etc.
#         16 - enable sync command
#         32 - enable remount read-only
#         64 - enable signalling of processes (term, kill, oom-kill)
#        128 - allow reboot/poweroff
#        256 - allow nicing of all RT tasks
#
#   For example, to enable both control of console logging level and
#   debugging dumps of processes: kernel.sysrq = 10
#
kernel.sysrq = 176
[22:53][0]silence@silence-1991:~$
solid hedge
solid hedge