search

linuxmint / cinnamon

A Linux desktop featuring a traditional layout, built from modern technology and introducing brand new innovative features.
GNU General Public License v2.0
4.4k stars 722 forks source link

Cinnamon desktop crashes when updating a text file #12175

Open fjrg76-com opened 2 weeks ago

fjrg76-com commented 2 weeks ago

Distribution

Mint 21.2

Package version

5.8.4

Graphics hardware in use

AMD Kaveri [Radeon R5 Graphics]

Frequency

Quite often

Bug description

When I edit a C++ source code file in a Eclipse based tool called STM32CubeIDE and then I switch to a GVim editor running instance, with the same opened file, the Cinnamon desktop crashes.

The attached image is in Spanish, but basically it says:

Cinnamon has blocked

It is running in error recovery mode ... Do you want to restart Cinnamon?

20240430_234723

Steps to reproduce

Open a C++ source code in gVim Start the STM32CubeIDE tool and open the same source code file. Edit the source code inside STM32CubeIDE. Save it. Switch to gVim and choose that you want to update the file's content. Cinnamon crashed

Expected behavior

Cinnamon desktop shouldn't crashed.

Mint 20.3 (which I have it running in another partition, doing mostly the same work, STM32CubeIDE + gVim) doesn't have this issue.

Additional information

You can find the error log (stack) in this pastebin:

https://termbin.com/f1nt

My Linux box:

System: Kernel: 5.15.0-105-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: Cinnamon 5.8.4 tk: GTK 3.24.33 info: mate-panel wm: Metacity 3.44.0 dm: LightDM 1.30.0 Distro: Linux Mint 21.2 Victoria base: Ubuntu 22.04 jammy Machine: Type: Desktop Mobo: ASRock model: FM2A68M-DG3+ serial: UEFI: American Megatrends v: P2.60 date: 01/12/2016 CPU: Info: dual core model: AMD A6-7400K Radeon R5 6 Compute Cores 2C+4G bits: 64 type: MT MCP smt: enabled arch: Steamroller rev: 1 cache: L1: 128 KiB L2: 1024 KiB Speed (MHz): avg: 3493 min/max: 1400/3500 boost: enabled cores: 1: 3493 2: 3493 bogomips: 13973 Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: AMD Kaveri [Radeon R5 Graphics] vendor: ASRock driver: radeon v: kernel ports: active: DVI-D-1,VGA-1 empty: HDMI-A-1 bus-ID: 00:01.0 chip-ID: 1002:1315 class-ID: 0300 Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: ati,radeon unloaded: fbdev,modesetting,vesa gpu: radeon display-ID: :0 screens: 1 Screen-1: 0 s-res: 4480x1080 s-dpi: 96 s-size: 1185x285mm (46.7x11.2") s-diag: 1219mm (48") Monitor-1: DVI-0 mapped: DVI-D-1 pos: primary,left model: LG (GoldStar) ULTRAWIDE serial: res: 2560x1080 hz: 60 dpi: 97 size: 673x284mm (26.5x11.2") diag: 730mm (28.8") modes: max: 2560x1080 min: 720x400 Monitor-2: VGA-0 mapped: VGA-1 pos: right model: HP 2310 serial: res: 1920x1080 hz: 60 dpi: 96 size: 510x287mm (20.1x11.3") diag: 585mm (23") modes: max: 1920x1080 min: 720x400 OpenGL: renderer: KAVERI ( LLVM 15.0.7 DRM 2.50 5.15.0-105-generic) v: 4.5 Mesa 23.2.1-1ubuntu3.1~22.04.2 direct render: Yes

fjrg76-com commented 1 week ago

Ups, I did it again!

This time the desktop crashed when I had already opened two gVim windows with the same file (Eclipse IDE wasn't involved in the issue). I edited some code in one of them, and then, when I reached the other gVim instance with the same file, the desktop crashed:

23:46:56 systemd-coredum: Process 1603 (cinnamon) of user 1000 dumped core.

This behavior reveals that the problem is related to shared documents.

I'll keep you posted.