Open Regressor opened 4 years ago
Provide some logging and a sfack trace.
.xsession-errors contain only one string related this problem:
(csd-power:3456810): power-plugin-CRITICAL **: 11:48:19.530: abs_to_percentage: assertion 'max > min' failed
syslog contain nothing about this problem
Coredump stacktrace: Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `cinnamon'. Program terminated with signal SIGABRT, Aborted.
50 ../sysdeps/unix/sysv/linux/raise.c: Нет такого файла или каталога. [Current thread is 1 (Thread 0x7f91717e9ac0 (LWP 1984779))] (gdb) bt
file=0x7f91763bb1f0 "../../../../src/cairo-arc.c", line=189, function=<optimized out>) at assert.c:92
function=0x7f91763bb230 "_cairo_arc_in_direction") at assert.c:101
from /lib/x86_64-linux-gnu/libmozjs-52.so.0
--Type
I believe I have a similar problem involving Applets. It seems that Applet 1 + Applet 2 + screensaver screen lock leads to crash, where Applet 1 = Weather, and Applet 2 = CPU temp indicator. Applet 1 or 2 only + screensaver screen lock does not seem to result in crash. The thread number varies, I have included syslog and stack trace for the most recent event. If there is any other info that could be helpful, please let me know, I am a newbie to Linux and GitHub.
EDIT: Several additional crashes have occurred with just CPU Temp Monitor but not Weather applet. I forgot to mention above that I am also running the Clock and CPU Load desklets.
EDIT 2: Running overnight 12+ hours without CPU Temp Monitor and with Weather applet, Clock desklet and CPU Load desklet, resulted in no crash. Suggests CPU Temp Monitor applet may be the cause.
Message: Process 1487 (cinnamon) of user 1000 dumped core.
Stack trace of thread 1487:
Provide some logging and a sfack trace.
I have a .crash report file but gdb from extracted coredump generates a junk with ?? () in it. Is there any way to get normal stacktrace from it ? Crash report is 25Mb size and I think it is not good idea to attach it here.
@LinuxLightning Please try replacing CPU temp indicator by Sensors Monitor: https://cinnamon-spices.linuxmint.com/applets/view/337
cinnamon keeps crashing every time screen locked and powered off. Today I tried to run it in gdb and got same ?? () backtraces.
@Regressor are you still experiencing this issue?
I disabled monitor timed switch-off and now problem gone. But after enabling it problem allways return.
I'm experiencing exactly the same issue with the same error message in log.
I'm having this as well, and it's pretty bad-- cinnamon crashes in a way where I can't do alt + f2 + r or any other keyboard shortcut to reset it. .xsession-errors
:
** Message: 15:32:30.875: nemo-desktop: session is cinnamon, establishing proxy
cinnamon-session[950]: WARNING: t+4.71905s: Detected that screensaver has appeared on the bus
Gjs-Message: 15:32:31.318: JS LOG: [LookingGlass/info] Loaded applet show-desktop@cinnamon.org in 659 ms
Gjs-Message: 15:32:31.322: JS LOG: [LookingGlass/info] Role locked: tray
Gjs-Message: 15:32:31.323: JS LOG: [LookingGlass/info] Loaded applet systray@cinnamon.org in 5 ms
Gjs-Message: 15:32:31.327: JS LOG: [LookingGlass/info] Role locked: notifications
Gjs-Message: 15:32:31.334: JS LOG: [LookingGlass/info] Loaded applet notifications@cinnamon.org in 11 ms
Gjs-Message: 15:32:31.338: JS LOG: [LookingGlass/info] Loaded applet removable-drives@cinnamon.org in 4 ms
Gjs-Message: 15:32:31.385: JS LOG: [LookingGlass/info] Loaded applet keyboard@cinnamon.org in 47 ms
Gjs-Message: 15:32:31.389: JS LOG: [LookingGlass/info] Loaded applet favorites@cinnamon.org in 4 ms
Gjs-Message: 15:32:31.407: JS LOG: [LookingGlass/info] Loaded applet calendar@cinnamon.org in 18 ms
Gjs-Message: 15:32:31.411: JS LOG: [LookingGlass/info] Loaded applet xapp-status@cinnamon.org in 4 ms
Gjs-Message: 15:32:31.419: JS LOG: [LookingGlass/info] Loaded applet power@cinnamon.org in 8 ms
Gjs-Message: 15:32:31.435: JS LOG: [LookingGlass/info] Role locked: panellauncher
Gjs-Message: 15:32:31.744: JS LOG: [LookingGlass/info] Loaded applet panel-launchers@cinnamon.org in 324 ms
** (csd-power:1002): CRITICAL **: 15:32:31.760: abs_to_percentage: assertion 'max > min' failed
Gjs-Message: 15:32:31.770: JS LOG: [LookingGlass/info] Loaded applet sound@cinnamon.org in 26 ms
Gjs-Message: 15:32:31.773: JS LOG: [LookingGlass/info] Role locked: windowattentionhandler
Gjs-Message: 15:32:31.781: JS LOG: [LookingGlass/info] Loaded applet window-list@cinnamon.org in 11 ms
Gjs-Message: 15:32:31.781: JS LOG: [LookingGlass/info] Loaded applet window-list@cinnamon.org in 0 ms
Gjs-Message: 15:32:31.796: JS LOG: [LookingGlass/info] Loaded applet network@cinnamon.org in 15 ms
Gjs-Message: 15:32:31.856: JS LOG: [LookingGlass/info] Loaded applet menu@cinnamon.org in 60 ms
Gjs-Message: 15:32:31.856: JS LOG: [LookingGlass/info] AppletManager started in 1286 ms
Gjs-Message: 15:32:31.858: JS LOG: [LookingGlass/info] Cinnamon took 1433 ms to start
Gjs-Message: 15:32:31.864: JS LOG: Unknown network device type, is 14
Gjs-Message: 15:32:31.870: JS LOG: [LookingGlass/info] Hiding systray: network
(I'm running Arch + Cinnamon 5.4.12)
@agalakhov, did you ever find a fix or workaround?
@NathanC It seems to be caused by certain applet, possibly the hardware monitor. As a workaround one can use different applet or completely disable it.
Issue I have an ubuntu with cinnamon installed. Every time screen is locked cinnamon crashes:
cinnamon: ../../../../src/cairo-arc.c:189: _cairo_arc_in_direction: Проверочное утверждение «angle_max >= angle_min» не выполнено. [1] 1984779 abort (core dumped) cinnamon
Steps to reproduce Install ubuntu 20, install cinnamon, set screen off 5 minutes, lock screen, wait to screen off, unlock it and see cinnamon crashed
Expected behaviour Not crash after lock and screen off
Configuration info, if applicable If this bug report is related to an Applet, Desklet or Extension, please paste (or use a pastebin service) the offending extension's settings, if it has any. You can obtain this by opening its configuration, clicking the 'hamburger' button in the upper-right corner of the window, and selecting "Export to a file". Please be sure to review the contents and remove any personal data it may contain.