Something happen to Cinnamon but I can't find the logs

As the title says today I turned on my laptop and I got a notify from Cinnamon that "something bad" has happen and I should check the logs. Unfortunately the message is too cryptic to me and I don't know where to look for the logs :frowning:

It happen after I temporary switched to MS Windows for a while and after I got back to Garuda my network card was disabled, but a restart fixed that. But the next restart gave me the topic problem :frowning:

  Kernel: 5.18.12-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.1.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=6a135e81-5d37-4390-8a10-a9eef293c0d9 rw [email protected]
    quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
    systemd.unified_cgroup_hierarchy=1 loglevel=3
  Desktop: Cinnamon v: 5.4.3 tk: GTK v: 3.24.34 wm: Mutter vt: 7
    dm: LightDM v: 1.30.0 Distro: Garuda Linux base: Arch Linux
  Type: Laptop System: Acer product: Aspire A515-54G v: V1.24
    serial: <superuser required>
  Mobo: CML model: Doc_WC v: V1.24 serial: <superuser required>
    UEFI: Insyde v: 1.24 date: 07/07/2021
  ID-1: BAT1 charge: 39.1 Wh (100.0%) condition: 39.1/48.9 Wh (79.9%)
    volts: 16.2 min: 15.2 model: LGC AC14B8K type: Li-ion serial: <filter>
    status: full
  Info: model: Intel Core i5-10210U bits: 64 type: MT MCP
    arch: Comet/Whiskey Lake note: check gen: core 10 built: 2018
    process: Intel 14nm family: 6 model-id: 0x8E (142) stepping: 0xC (12)
    microcode: 0xF0
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
    L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
    L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 1128 high: 1701 min/max: 400/4200 scaling:
    driver: intel_pstate governor: powersave cores: 1: 800 2: 800 3: 800 4: 842
    5: 1021 6: 1701 7: 1700 8: 1360 bogomips: 33599
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2
    mitigation: Enhanced IBRS, IBPB: conditional, RSB filling
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
  Device-1: Intel CometLake-U GT2 [UHD Graphics]
    vendor: Acer Incorporated ALI driver: i915 v: kernel arch: Gen9.5
    process: Intel 14nm built: 2016-20 ports: active: eDP-1 empty: HDMI-A-1
    bus-ID: 0000:00:02.0 chip-ID: 8086:9b41 class-ID: 0300
  Device-2: NVIDIA GP108M [GeForce MX250] vendor: Acer Incorporated ALI
    driver: nouveau v: kernel non-free: 515.xx+ status: current (as of 2022-06)
    arch: Pascal process: TSMC 16nm built: 2016-21 bus-ID: 0000:02:00.0
    chip-ID: 10de:1d13 class-ID: 0302
  Device-3: Quanta HD User Facing type: USB driver: uvcvideo bus-ID: 1-5:3
    chip-ID: 0408:a061 class-ID: 0e02
  Display: x11 server: X.Org v: 21.1.4 driver: X: loaded: intel,nouveau
    unloaded: modesetting alternate: fbdev,nv,vesa gpu: i915 display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93")
  Monitor-1: eDP-1 mapped: eDP1 model: AU Optronics 0x61ed built: 2018
    res: 1920x1080 hz: 60 dpi: 143 gamma: 1.2 size: 340x190mm (13.39x7.48")
    diag: 395mm (15.5") ratio: 16:9 modes: 1920x1080
  Message: Unable to show GL data. Required tool glxinfo missing.
  Device-1: Intel Comet Lake PCH-LP cAVS vendor: Acer Incorporated ALI
    driver: snd_hda_intel v: kernel
    alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 0000:00:1f.3
    chip-ID: 8086:02c8 class-ID: 0403
  Sound Server-1: ALSA v: k5.18.12-zen1-1-zen running: yes
  Sound Server-2: sndio v: N/A running: no
  Sound Server-3: PulseAudio v: 16.1 running: no
  Sound Server-4: PipeWire v: 0.3.55 running: yes
  Device-1: Intel Comet Lake PCH-LP CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 0000:00:14.3 chip-ID: 8086:02f0 class-ID: 0280
  IF: wlp0s20f3 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Acer Incorporated ALI driver: r8169 v: kernel port: 3000
    bus-ID: 0000:03:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp3s0 state: down mac: <filter>
  Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode]
    driver: intel_nvme_remap v: N/A port: 5060 bus-ID: 0000:00:17.0
    chip-ID: 8086:282a rev: class-ID: 0104
  Local Storage: total: 953.87 GiB used: 116.94 GiB (12.3%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Intel model: SSDPEKNW010T8
    size: 953.87 GiB block-size: physical: 512 B logical: 512 B type: SSD
    serial: <filter> rev: 002C temp: 28.9 C scheme: GPT
  ID-1: / raw-size: 476.38 GiB size: 476.38 GiB (100.00%)
    used: 116.89 GiB (24.5%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
  ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
    used: 54.6 MiB (56.9%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 476.38 GiB size: 476.38 GiB (100.00%)
    used: 116.89 GiB (24.5%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
  ID-4: /var/log raw-size: 476.38 GiB size: 476.38 GiB (100.00%)
    used: 116.89 GiB (24.5%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
  ID-5: /var/tmp raw-size: 476.38 GiB size: 476.38 GiB (100.00%)
    used: 116.89 GiB (24.5%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 7.59 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
  System Temperatures: cpu: 42.0 C pch: 45.0 C mobo: N/A gpu: nouveau
    temp: 41.0 C
  Fan Speeds (RPM): N/A
  Processes: 264 Uptime: 6m wakeups: 1 Memory: 7.59 GiB
  used: 2.63 GiB (34.7%) Init: systemd v: 251 default: graphical
  tool: systemctl Compilers: gcc: 12.1.0 clang: 14.0.6 Packages: apt: 0
  pacman: 1726 lib: 374 Shell: Bash v: 5.1.16 running-in: gnome-terminal
  inxi: 3.3.19
Garuda (2.6.5-1):
  System install date:     2021-12-22
  Last full system update: 2022-07-19
  Is partially upgraded:   No
  Relevant software:       NetworkManager
  Windows dual boot:       Probably (Run as root to verify)
  Snapshots:               Snapper
  Failed units:  

To check the logs you should search your journal

journalctl -b -1 -p3 --no-pager --no-hostname

(-b is the current boot, -b -1 the previous boot, etc.)
In addition to that, if the error message persists rebooting, please be more specific than "something bad".


Thanks for a quick response, but unfortunately your command didn't tell me anything new. There is no any Cinnamon error in the journal, so I still can't go beyond "something bad"-type description of my problem :frowning:

So hopefully it was not so bad?
The -p parameter is the "priority":
"emerg" (0), "alert" (1), "crit" (2), "err" (3), "warning" (4), "notice" (5), "info" (6), "debug" (7)
If there was nothing in 3 (which includes 0/1/2), you could give a look at the warnings (-p4), but, if no error message appears anymore after rebooting and you don't see anything wrong with some normal system usage, I wouldn't go crazy chasing ghosts.


You know, if the notify was not appearing after every reboot then I wouldn't probably be "chasing ghost". But that's not the case >_>

Fortunately I was able this time to get read the notify more carefully before it disappeared and I can get more specific as to my problem: it says that Cinnamon was able to start "successfully" but some applet, desklet, or an extension wasn't able to load properly. It also says to check the system journal and a "Looking Glass journal" (what is that?) for looking for the problem.

Now I also have noticed that the Garuda System Maintenance icon on the panel isn't showing.

Could it be this fresh new bug (should be fixed in an upcoming 5.4.4)?

I'm not sure (not a Cinnamon user), but a quick search brought me to this (maybe old, and the path changed again, just in case...):


OK I have found that "Looking Glass" log :slight_smile:
It's a bit big, so I'm giving you this link:

I'll be waiting for this Cinnamon update, maybe it is their fault.

Just one last thing: as this icon that disappeared was giving me access to the update manager, I wish to know how to update Cinnamon from the command line. I'm still new to the Pacman and I can't yet use it well >_>

From the command line use garuda-update
The available parameters, if necessary, are described in the wiki:


Thanks! I'll be looking for this :smiley:

1 Like

OK, let's see how it goes.
That error on recordingIndicator does appear in your log, but it is really a lot of stuff, with other errors mentioned (maybe due to the one above, which does not allow to load the applet, or maybe other stuff). I'm not so technical to say.
If the release of 5.4.4 to Arch repo will not come soon enough, I see 5.4.4 had only one single line removed in one single json file (which is a text file), so it would not be difficult to test it manually.
I like to do these strange things, but I can't do it this time, so I don't want to tempt you... :wink:

1 Like

This is one of the reasons dual booting with Windows is not recommended by Garuda. Windows has the nasty habit of holding some hardware hostage and therefore disabling it in Linux.

Be sure Windows has not re-enabled fastboot in an update. Also be sure the power saving options are disabled for your wifi in the advanced properties tab in the Windows device manager.


Maybe it could be the time for a garuda-update now, since I see Cinnamon 5.4.4 reached the Arch repo.
As said, I don't know if the fix for that linked bug is all you need, but for sure updating is always a good thing to do...


Unfortunately, it didn't resolve my issue :frowning: The notify is still appearing.
If I could somehow find which module is broken... :confused:

OK it seams it do has been fixed :smiley: Whatever/whoever did it >_>

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.