Firefox locking up almost everyday since last update - [ Monitoring after Kernel update to 5.13 ]

Questions about applications and software
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
HaveaMint
Level 6
Level 6
Posts: 1085
Joined: Fri Feb 02, 2018 9:56 pm

Re: Firefox locking up almost everyday since last update

Post by HaveaMint »

Since I have disabled acceleration in FF I haven't had any lockups. Mines seems to have occurred with auto play or as such, even though I disabled it. Some news sites love to auto play.
"Tune for maximum Smoke and then read the Instructions".
HaveaMint
Level 6
Level 6
Posts: 1085
Joined: Fri Feb 02, 2018 9:56 pm

Re: Firefox locking up almost everyday since last update

Post by HaveaMint »

The newer versions of FF have changed the "disable" settings which I read and set, I however didn't bookmark those settings.
"Tune for maximum Smoke and then read the Instructions".
User avatar
smurphos
Level 18
Level 18
Posts: 8498
Joined: Fri Sep 05, 2014 12:18 am
Location: Irish Brit in Portugal
Contact:

Re: Firefox locking up almost everyday since last update

Post by smurphos »

AZgl1800 wrote: Thu Apr 07, 2022 12:52 am I sure wish I knew what the hell is going on, so it can be banned and never occur again.
So check the logs and see what is going on.

After a lock up and freeze on next boot up in a terminal run

Code: Select all

journalctl -b -1 -r | less
This will list in reverse order the last entries in the system journal before your lock up which might provide a clue to the issue. Share the last 20 or so entries here as a start.
For custom Nemo actions, useful scripts for the Cinnamon desktop, and Cinnamox themes visit my Github pages.
User avatar
AZgl1800
Level 20
Level 20
Posts: 11173
Joined: Thu Dec 31, 2015 3:20 am
Location: Oklahoma where the wind comes Sweeping down the Plains
Contact:

Re: Firefox locking up almost everyday since last update

Post by AZgl1800 »

I can only highlight one page at a time,
so this is the last page.

I have been doing a lot of YouTubes since I posted the above.

Code: Select all

pr 06 19:27:53 FX705 kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Apr 06 19:27:53 FX705 kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Apr 06 19:27:53 FX705 kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
Apr 06 19:27:53 FX705 kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Apr 06 19:27:53 FX705 kernel: BIOS-e820: [mem 0x000000007ac0f000-0x000000007fffffff] reserved
Apr 06 19:27:53 FX705 kernel: BIOS-e820: [mem 0x000000007ac0e000-0x000000007ac0efff] usable
Apr 06 19:27:53 FX705 kernel: BIOS-e820: [mem 0x000000007a527000-0x000000007ac0dfff] reserved
Apr 06 19:27:53 FX705 kernel: BIOS-e820: [mem 0x000000007a408000-0x000000007a526fff] ACPI NVS
Apr 06 19:27:53 FX705 kernel: BIOS-e820: [mem 0x000000007a38b000-0x000000007a407fff] ACPI data
Apr 06 19:27:53 FX705 kernel: BIOS-e820: [mem 0x0000000078b14000-0x000000007a38afff] reserved
Apr 06 19:27:53 FX705 kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000078b13fff] usable
Apr 06 19:27:53 FX705 kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
Apr 06 19:27:53 FX705 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Apr 06 19:27:53 FX705 kernel: BIOS-provided physical RAM map:
Apr 06 19:27:53 FX705 kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
Apr 06 19:27:53 FX705 kernel: x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
Apr 06 19:27:53 FX705 kernel: x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
Apr 06 19:27:53 FX705 kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Apr 06 19:27:53 FX705 kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
Apr 06 19:27:53 FX705 kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
Apr 06 19:27:53 FX705 kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Apr 06 19:27:53 FX705 kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Apr 06 19:27:53 FX705 kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Apr 06 19:27:53 FX705 kernel:   zhaoxin   Shanghai  
Apr 06 19:27:53 FX705 kernel:   Centaur CentaurHauls
Apr 06 19:27:53 FX705 kernel:   Hygon HygonGenuine
Apr 06 19:27:53 FX705 kernel:   AMD AuthenticAMD
Apr 06 19:27:53 FX705 kernel:   Intel GenuineIntel
Apr 06 19:27:53 FX705 kernel: KERNEL supported cpus:
Apr 06 19:27:53 FX705 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-107-generic root=UUID=d5abc9c8-da96-4c47-bd8b-16b256ff7034 ro
Apr 06 19:27:53 FX705 kernel: Linux version 5.4.0-107-generic (buildd@lcy02-amd64-058) (gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1)) #121-Ubuntu SMP Thu Mar 24 16:04:27 UTC 2022 (Ubuntu 5.4.0-107.121-generic 5.4.174)
Apr 06 19:27:53 FX705 kernel: microcode: microcode updated early to revision 0xea, date = 2021-01-05
(END)
LM21.3 Cinnamon ASUS FX705GM | Donate to Mint https://www.patreon.com/linux_mint
Image
User avatar
AZgl1800
Level 20
Level 20
Posts: 11173
Joined: Thu Dec 31, 2015 3:20 am
Location: Oklahoma where the wind comes Sweeping down the Plains
Contact:

Re: Firefox locking up almost everyday since last update

Post by AZgl1800 »

I presume that file is located in /bin/journalctl

what if I just delete it so it only contains the last day or three?
it has info dating back months ago

Code: Select all

-- Logs begin at Mon 2022-01-17 03:34:15 CST, end at Thu 2022-04-07 02:35:29 CDT. --
Apr 06 21:40:31 FX705 sudo[9798]: pam_unix(sudo:session): session closed for user root
LM21.3 Cinnamon ASUS FX705GM | Donate to Mint https://www.patreon.com/linux_mint
Image
User avatar
AZgl1800
Level 20
Level 20
Posts: 11173
Joined: Thu Dec 31, 2015 3:20 am
Location: Oklahoma where the wind comes Sweeping down the Plains
Contact:

Re: Firefox locking up almost everyday since last update

Post by AZgl1800 »

smurphos wrote: Thu Apr 07, 2022 2:09 am
So check the logs and see what is going on.

After a lock up and freeze on next boot up in a terminal run

Code: Select all

journalctl -b -1 -r | less
This will list in reverse order the last entries in the system journal before your lock up which might provide a clue to the issue. Share the last 20 or so entries here as a start.
I saw this post way too late for it to be useful right now.
but, I will make a Desktop note to do just that next time it crashes.
LM21.3 Cinnamon ASUS FX705GM | Donate to Mint https://www.patreon.com/linux_mint
Image
plasticbertrand
Level 1
Level 1
Posts: 33
Joined: Fri Nov 19, 2021 5:30 am

Re: Firefox locking up almost everyday since last update

Post by plasticbertrand »

After yeserday's FF update, FF crashed about 20 times in just one hour. No way to work with that. I added some (polite but clear) princess to the last ten crash reports, installed Chrome and could at least do my work:
Today, several updates happened. After that being installed, I gave FF a try and - BANG! it just works as if never anything had happened.
Sometimes patience pays!
User avatar
AZgl1800
Level 20
Level 20
Posts: 11173
Joined: Thu Dec 31, 2015 3:20 am
Location: Oklahoma where the wind comes Sweeping down the Plains
Contact:

Re: Firefox locking up almost everyday since last update

Post by AZgl1800 »

OkieDokie in OkieLand, here we are again.
First instance of a crash.

I was watching a YouTube video, it ended, and Clicked on the NEXT button to see the next video.
Not sure, but I think the laptop overheated?

It was laying across my knees w/o the spacer "a Kindle eReader" that lifts it up off my legs, so the air slots are NOT blocked.

Anyhoo, the bottom of it was very warm to the touch, 1st thing I thought of when Firefox Locked up the entire PC. Was it really Firefox?

I am not good at reading this script, but it seems that Timeshift was started?
But if so, it is 3 hours before it normally runs, as can be seen in this window, Timeshift has not run today, and I don't expect it to until 22:00 hours later on today, the PC locked up at 19:08:10


TS today.jpg


Here are the results of the Journal message;

18:33:58 is just about exactly when I started the video, the timing is right on.

Code: Select all

-- Logs begin at Mon 2022-01-17 03:34:15 CST, end at Sun 2022-04-10 19:08:10 CDT. --
Apr 10 19:00:01 FX705 CRON[12632]: pam_unix(cron:session): session closed for user root
Apr 10 19:00:01 FX705 crontab[12668]: (root) LIST (root)
Apr 10 19:00:01 FX705 crontab[12667]: (root) LIST (root)
Apr 10 19:00:01 FX705 CRON[12633]: (root) CMD (timeshift --check --scripted)
Apr 10 19:00:01 FX705 CRON[12632]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 10 18:33:58 FX705 systemd[1]: anacron.service: Succeeded.
Apr 10 18:33:58 FX705 anacron[12509]: Normal exit (0 jobs run)
Apr 10 18:33:58 FX705 anacron[12509]: Anacron 2.3 started on 2022-04-10
Apr 10 18:33:58 FX705 systemd[1]: Started Run anacron jobs.
Apr 10 18:30:01 FX705 CRON[12478]: pam_unix(cron:session): session closed for user root
Apr 10 18:30:01 FX705 CRON[12479]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
Apr 10 18:30:01 FX705 CRON[12478]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 10 18:27:48 FX705 rtkit-daemon[1278]: Supervising 9 threads of 3 processes of 1 users.
Apr 10 18:27:48 FX705 rtkit-daemon[1278]: Supervising 9 threads of 3 processes of 1 users.
Apr 10 18:22:21 FX705 rtkit-daemon[1278]: Supervising 9 threads of 3 processes of 1 users.
Apr 10 18:22:21 FX705 rtkit-daemon[1278]: Supervising 9 threads of 3 processes of 1 users.
Apr 10 18:22:21 FX705 rtkit-daemon[1278]: Supervising 9 threads of 3 processes of 1 users.
Apr 10 18:22:21 FX705 rtkit-daemon[1278]: Successfully made thread 12334 of process 11150 owned by '1000' RT at priority 10.
Apr 10 18:22:21 FX705 rtkit-daemon[1278]: Supervising 8 threads of 2 processes of 1 users.
Apr 10 18:22:21 FX705 rtkit-daemon[1278]: Supervising 8 threads of 2 processes of 1 users.
Apr 10 18:22:21 FX705 rtkit-daemon[1278]: Supervising 8 threads of 2 processes of 1 users.
Apr 10 18:22:21 FX705 rtkit-daemon[1278]: Supervising 8 threads of 2 processes of 1 users.
Apr 10 18:22:19 FX705 rtkit-daemon[1278]: Supervising 8 threads of 2 processes of 1 users.
Apr 10 18:22:19 FX705 rtkit-daemon[1278]: Supervising 8 threads of 2 processes of 1 users.
Apr 10 18:17:01 FX705 CRON[12224]: pam_unix(cron:session): session closed for user root
Apr 10 18:17:01 FX705 CRON[12225]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Apr 10 18:17:01 FX705 CRON[12224]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 10 18:09:12 FX705 rtkit-daemon[1278]: Supervising 8 threads of 2 processes of 1 users.
Apr 10 18:09:12 FX705 rtkit-daemon[1278]: Supervising 8 threads of 2 processes of 1 users.
Apr 10 18:09:06 FX705 rtkit-daemon[1278]: Supervising 8 threads of 2 processes of 1 users.
Apr 10 18:09:06 FX705 rtkit-daemon[1278]: Supervising 8 threads of 2 processes of 1 users.
Apr 10 18:09:04 FX705 rtkit-daemon[1278]: Supervising 8 threads of 2 processes of 1 users.
Apr 10 18:09:04 FX705 rtkit-daemon[1278]: Supervising 8 threads of 2 processes of 1 users.
Apr 10 18:09:04 FX705 rtkit-daemon[1278]: Supervising 8 threads of 2 processes of 1 users.
Apr 10 18:09:04 FX705 rtkit-daemon[1278]: Supervising 8 threads of 2 processes of 1 users.
Apr 10 18:09:04 FX705 rtkit-daemon[1278]: Supervising 8 threads of 2 processes of 1 users.
Apr 10 18:09:04 FX705 rtkit-daemon[1278]: Supervising 8 threads of 2 processes of 1 users.
Apr 10 18:09:03 FX705 rtkit-daemon[1278]: Supervising 8 threads of 2 processes of 1 users.
Apr 10 18:09:03 FX705 rtkit-daemon[1278]: Supervising 8 threads of 2 processes of 1 users.
Apr 10 18:09:03 FX705 rtkit-daemon[1278]: Supervising 8 threads of 2 processes of 1 users.
Apr 10 18:09:03 FX705 rtkit-daemon[1278]: Successfully made thread 11037 of process 10930 owned by '1000' RT at priority 10.
Apr 10 18:09:03 FX705 rtkit-daemon[1278]: Supervising 7 threads of 1 processes of 1 users.
Apr 10 18:09:03 FX705 rtkit-daemon[1278]: Supervising 7 threads of 1 processes of 1 users.
Apr 10 18:09:03 FX705 rtkit-daemon[1278]: Supervising 7 threads of 1 processes of 1 users.
Apr 10 18:09:03 FX705 rtkit-daemon[1278]: Supervising 7 threads of 1 processes of 1 users.
Apr 10 18:09:03 FX705 rtkit-daemon[1278]: Supervising 7 threads of 1 processes of 1 users.
Apr 10 18:09:03 FX705 rtkit-daemon[1278]: Supervising 7 threads of 1 processes of 1 users.
Apr 10 18:09:00 FX705 systemd-logind[797]: Lid opened.
Apr 10 18:00:01 FX705 CRON[10885]: pam_unix(cron:session): session closed for user root
Apr 10 18:00:01 FX705 crontab[10921]: (root) LIST (root)
Apr 10 18:00:01 FX705 crontab[10920]: (root) LIST (root)
Apr 10 18:00:01 FX705 CRON[10886]: (root) CMD (timeshift --check --scripted)

I can't determine what caused the Lockup?

Can you?
LM21.3 Cinnamon ASUS FX705GM | Donate to Mint https://www.patreon.com/linux_mint
Image
User avatar
AZgl1800
Level 20
Level 20
Posts: 11173
Joined: Thu Dec 31, 2015 3:20 am
Location: Oklahoma where the wind comes Sweeping down the Plains
Contact:

Re: Firefox locking up almost everyday since last update

Post by AZgl1800 »

How do I clear out that journal log, so that is only records from a time that I select,
like right now.
LM21.3 Cinnamon ASUS FX705GM | Donate to Mint https://www.patreon.com/linux_mint
Image
User avatar
SMG
Level 25
Level 25
Posts: 31813
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Firefox locking up almost everyday since last update

Post by SMG »

AZgl1800 wrote: Sun Apr 10, 2022 8:35 pm How do I clear out that journal log, so that is only records from a time that I select,
like right now.
There is no need to clear it out. You can select a specific time with parameters.

I've gone through this entire topic and I do not see any inxi output. Please supply the output of inxi -Fxxxrz. You titled this FF locking up, but it sounds like your entire system is freezing.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
User avatar
AZgl1800
Level 20
Level 20
Posts: 11173
Joined: Thu Dec 31, 2015 3:20 am
Location: Oklahoma where the wind comes Sweeping down the Plains
Contact:

Re: Firefox locking up almost everyday since last update

Post by AZgl1800 »

yup,
the entire OS freezes up, but it only happens when I am using Firefox.

no mouse action, no alt-tab action, no Keyboard response at all.
I have mentioned this in posts somewhere, but maybe not this thread.

I normally include the inxi info, don't know why I didn't this thread.

Code: Select all

inxi -Fxxxrz
System:
  Kernel: 5.4.0-107-generic x86_64 bits: 64 compiler: gcc v: 9.4.0 
  Desktop: Cinnamon 5.2.7 wm: muffin 5.2.1 dm: LightDM 1.30.0 
  Distro: Linux Mint 20.3 Una base: Ubuntu 20.04 focal 
Machine:
  Type: Laptop System: ASUSTeK product: TUF Gaming FX705GM_FX705GM v: 1.0 
  serial: <filter> 
  Mobo: ASUSTeK model: FX705GM v: 1.0 serial: <filter> 
  UEFI: American Megatrends v: FX705GM.307 date: 05/25/2020 
Battery:
  ID-1: BAT0 charge: 50.0 Wh condition: 50.0/64.1 Wh (78%) volts: 15.2/15.6 
  model: Simplo SDI ICR18650 type: Li-ion serial: <filter> status: Full 
  cycles: 41 
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M510 
  serial: <filter> charge: 55% (should be ignored) rechargeable: yes 
  status: Discharging 
CPU:
  Topology: 6-Core model: Intel Core i7-8750H bits: 64 type: MT MCP 
  arch: Kaby Lake rev: A L2 cache: 9216 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 52799 
  Speed: 800 MHz min/max: 800/4100 MHz Core speeds (MHz): 1: 800 2: 800 
  3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800 
Graphics:
  Device-1: Intel UHD Graphics 630 vendor: ASUSTeK driver: i915 v: kernel 
  bus ID: 00:02.0 chip ID: 8086:3e9b 
  Device-2: NVIDIA GP106M [GeForce GTX 1060 Mobile] vendor: ASUSTeK 
  driver: nvidia v: 470.103.01 bus ID: 01:00.0 chip ID: 10de:1c20 
  Display: x11 server: X.Org 1.20.13 driver: modesetting,nvidia 
  unloaded: fbdev,nouveau,vesa resolution: 1920x1080~60Hz 
  OpenGL: renderer: NVIDIA GeForce GTX 1060/PCIe/SSE2 
  v: 4.6.0 NVIDIA 470.103.01 direct render: Yes 
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: ASUSTeK driver: sof-audio-pci 
  bus ID: 00:1f.3 chip ID: 8086:a348 
  Device-2: NVIDIA GP106 High Definition Audio driver: snd_hda_intel 
  v: kernel bus ID: 01:00.1 chip ID: 10de:10f1 
  Sound Server: ALSA v: k5.4.0-107-generic 
Network:
  Device-1: Intel Wireless-AC 9560 [Jefferson Peak] driver: iwlwifi 
  v: kernel port: 5000 bus ID: 00:14.3 chip ID: 8086:a370 
  IF: wlo1 state: up mac: <filter> 
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: ASUSTeK driver: r8169 v: kernel port: 3000 bus ID: 03:00.0 
  chip ID: 10ec:8168 
  IF: enp3s0 state: down mac: <filter> 
Drives:
  Local Storage: total: 1.38 TiB used: 460.25 GiB (32.7%) 
  ID-1: /dev/nvme0n1 vendor: Intel model: SSDPEKNW512G8 size: 476.94 GiB 
  speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: 002C scheme: GPT 
  ID-2: /dev/sda vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB 
  speed: 6.0 Gb/s serial: <filter> rev: 3B6Q scheme: GPT 
Partition:
  ID-1: / size: 43.38 GiB used: 20.26 GiB (46.7%) fs: ext4 dev: /dev/sda2 
  ID-2: /home size: 409.90 GiB used: 124.89 GiB (30.5%) fs: ext4 
  dev: /dev/sda4 
Sensors:
  System Temperatures: cpu: 51.0 C mobo: 27.8 C gpu: nvidia temp: 46 C 
  Fan Speeds (RPM): cpu: 0 
Repos:
  Active apt repos in: /etc/apt/sources.list 
  1: deb [arch=amd64] https://download.virtualbox.org/virtualbox/debian focal contrib
  Active apt repos in: /etc/apt/sources.list.d/megasync.list 
  1: deb [signed-by=/usr/share/keyrings/meganz-archive-keyring.gpg] https://mega.nz/linux/repo/xUbuntu_20.04/ ./
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://packages.linuxmint.com una main upstream import backport
  2: deb https://dal.mirrors.clouvider.net/ubuntu focal main restricted universe multiverse
  3: deb https://dal.mirrors.clouvider.net/ubuntu focal-updates main restricted universe multiverse
  4: deb https://dal.mirrors.clouvider.net/ubuntu focal-backports main restricted universe multiverse
  5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
  6: deb http://archive.canonical.com/ubuntu/ focal partner
  Active apt repos in: /etc/apt/sources.list.d/official-source-repositories.list 
  1: deb-src http://packages.linuxmint.com una main upstream import backport
  2: deb-src https://dal.mirrors.clouvider.net/ubuntu focal main restricted universe multiverse
  3: deb-src https://dal.mirrors.clouvider.net/ubuntu focal-updates main restricted universe multiverse
  4: deb-src https://dal.mirrors.clouvider.net/ubuntu focal-backports main restricted universe multiverse
  5: deb-src http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
  6: deb-src http://archive.canonical.com/ubuntu/ focal partner
  Active apt repos in: /etc/apt/sources.list.d/playonlinux.list 
  1: deb http://deb.playonlinux.com/ bionic main
  Active apt repos in: /etc/apt/sources.list.d/teejeetech-aptik.list 
  1: deb [arch=amd64 signed-by=/usr/share/keyrings/teejeetech-aptik-keyring.gpg] https://packages.teejeetech.com/aptik/0/JcbCJmMm7k/ubuntu/focal/amd64 stable main
  Active apt repos in: /etc/apt/sources.list.d/vivaldi.list 
  1: deb [arch=amd64] https://repo.vivaldi.com/stable/deb/ stable main
Info:
  Processes: 347 Uptime: 1h 17m Memory: 15.49 GiB used: 2.09 GiB (13.5%) 
  Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.4.0 alt: 9 Shell: bash 
  v: 5.0.17 running in: gnome-terminal inxi: 3.0.38 
  
LM21.3 Cinnamon ASUS FX705GM | Donate to Mint https://www.patreon.com/linux_mint
Image
User avatar
SMG
Level 25
Level 25
Posts: 31813
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Firefox locking up almost everyday since last update

Post by SMG »

AZgl1800 wrote: Sun Apr 10, 2022 9:56 pm yup,
the entire OS freezes up,
We've seen this quite a bit with 8th-gen Intel (which you have) and newer. It usually is resolved by upgrading to a newer kernel.

Instructions for upgrading to the 5.13 kernel:
  • Open Update Manager.
  • Select View > Linux Kernels and click Continue.
  • Make sure 5.13 is selected on the left panel and then click the top-most option on the right panel. An "Install" button will appear.
  • Install the kernel and then reboot for it to become active.
Let's see if that helps.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
User avatar
AZgl1800
Level 20
Level 20
Posts: 11173
Joined: Thu Dec 31, 2015 3:20 am
Location: Oklahoma where the wind comes Sweeping down the Plains
Contact:

Re: Firefox locking up almost everyday since last update

Post by AZgl1800 »

Okay,
I thought the kernel I was using was the latest?
5.4 is a higher number than 5.1.....
oh well,

time to reboot now.

5.13 kernel.jpg
LM21.3 Cinnamon ASUS FX705GM | Donate to Mint https://www.patreon.com/linux_mint
Image
User avatar
SMG
Level 25
Level 25
Posts: 31813
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Firefox locking up almost everyday since last update

Post by SMG »

AZgl1800 wrote: Sun Apr 10, 2022 10:10 pm Okay,
I thought the kernel I was using was the latest?
5.4 is a higher number than 5.1.....
oh well,

time to reboot now.
You are using the latest 5.4 kernel, but that is not the newest kernel available in Linux Mint.

A lot of people want to use decimal math with the kernel numbering convention, but it's a naming convention. One compares the number to the right of the decimal point when both numbers to the left of the decimal point are the same. 13 is a higher number than 4 so 5.13 is newer than 5.4.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
User avatar
AZgl1800
Level 20
Level 20
Posts: 11173
Joined: Thu Dec 31, 2015 3:20 am
Location: Oklahoma where the wind comes Sweeping down the Plains
Contact:

Re: Firefox locking up almost everyday since last update

Post by AZgl1800 »

SMG wrote: Sun Apr 10, 2022 10:20 pm
AZgl1800 wrote: Sun Apr 10, 2022 10:10 pm Okay,
I thought the kernel I was using was the latest?
5.4 is a higher number than 5.1.....
oh well,

time to reboot now.
You are using the latest 5.4 kernel, but that is not the newest kernel available in Linux Mint.

A lot of people want to use decimal math with the kernel numbering convention, but it's a naming convention. One compares the number to the right of the decimal point when both numbers to the left of the decimal point are the same. 13 is a higher number than 4 so 5.13 is newer than 5.4.
I've been reading this forum since LM17, and that point has never been explained like that.

Had I known that, I would have installed the newer version long ago.

got it fixed now:
System:
Host: FX705 Kernel: 5.13.0-39-generic x86_64 bits: 64
Last edited by AZgl1800 on Mon Apr 11, 2022 12:02 am, edited 1 time in total.
LM21.3 Cinnamon ASUS FX705GM | Donate to Mint https://www.patreon.com/linux_mint
Image
User avatar
AZgl1800
Level 20
Level 20
Posts: 11173
Joined: Thu Dec 31, 2015 3:20 am
Location: Oklahoma where the wind comes Sweeping down the Plains
Contact:

Re: Firefox locking up almost everyday since last update - [ Monitoring after Kernel update to 5.13 ]

Post by AZgl1800 »

Code: Select all

System:
Host: FX705 Kernel: 5.13.0-39-generic x86_64 bits: 64 
Well, it didn't stay fixed.
Again, I was watching a YouTube video that ended, I clicked on the hamburger menu and selected "Subscriptions" and that is where the entire PC just locked up.
BIOS long press removed power :(

Doesn't seem to corrupt anything, just aggravating.
Here is the Journal entries of note.
you will this message twice, that is where I had to copy paste twice into XED to get it down to where the time of the crash occurred. just wanted to clear that I did not leave anything out.
Apr 19 00:04:50 FX705 systemd[1]: NetworkManager-dispatcher.service: Succeeded.

Code: Select all


-- Logs begin at Thu 2022-03-03 16:13:09 CST, end at Tue 2022-04-19 00:45:36 CDT. --
Apr 19 00:42:55 FX705 rtkit-daemon[1396]: Supervising 9 threads of 3 processes of 1 users.
Apr 19 00:42:55 FX705 rtkit-daemon[1396]: Supervising 9 threads of 3 processes of 1 users.
Apr 19 00:30:03 FX705 rtkit-daemon[1396]: Supervising 9 threads of 3 processes of 1 users.
Apr 19 00:30:03 FX705 rtkit-daemon[1396]: Supervising 9 threads of 3 processes of 1 users.
Apr 19 00:20:13 FX705 systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Apr 19 00:20:03 FX705 NetworkManager[819]: <info>  [1650345603.2007] manager: NetworkManager state is now CONNECTED_GLOBAL
Apr 19 00:19:56 FX705 systemd[1]: Started Network Manager Script Dispatcher Service.
Apr 19 00:19:56 FX705 dbus-daemon[818]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Apr 19 00:19:56 FX705 systemd[1]: Starting Network Manager Script Dispatcher Service...
Apr 19 00:19:56 FX705 dbus-daemon[818]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.f
reedesktop.nm-dispatcher.service' requested by ':1.6' (uid=0 pid=819 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Apr 19 00:19:56 FX705 NetworkManager[819]: <info>  [1650345596.8787] manager: NetworkManager state is now CONNECTED_SITE
Apr 19 00:17:18 FX705 rtkit-daemon[1396]: Supervising 9 threads of 3 processes of 1 users.
Apr 19 00:17:18 FX705 rtkit-daemon[1396]: Supervising 9 threads of 3 processes of 1 users.
Apr 19 00:17:01 FX705 CRON[16292]: pam_unix(cron:session): session closed for user root
Apr 19 00:17:01 FX705 CRON[16293]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Apr 19 00:17:01 FX705 CRON[16292]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 19 00:07:50 FX705 rtkit-daemon[1396]: Supervising 9 threads of 3 processes of 1 users.
Apr 19 00:07:50 FX705 rtkit-daemon[1396]: Supervising 9 threads of 3 processes of 1 users.
Apr 19 00:06:39 FX705 rtkit-daemon[1396]: Supervising 9 threads of 3 processes of 1 users.
Apr 19 00:06:39 FX705 rtkit-daemon[1396]: Successfully made thread 16170 of process 15232 owned by '1000' RT at priority 10.
Apr 19 00:06:39 FX705 rtkit-daemon[1396]: Supervising 8 threads of 2 processes of 1 users.
Apr 19 00:06:39 FX705 rtkit-daemon[1396]: Supervising 8 threads of 2 processes of 1 users.
Apr 19 00:06:39 FX705 rtkit-daemon[1396]: Supervising 8 threads of 2 processes of 1 users.
Apr 19 00:06:39 FX705 rtkit-daemon[1396]: Supervising 8 threads of 2 processes of 1 users.
Apr 19 00:06:38 FX705 rtkit-daemon[1396]: Supervising 8 threads of 2 processes of 1 users.
Apr 19 00:06:38 FX705 rtkit-daemon[1396]: Supervising 8 threads of 2 processes of 1 users.
Apr 19 00:06:38 FX705 rtkit-daemon[1396]: Supervising 8 threads of 2 processes of 1 users.
Apr 19 00:06:38 FX705 rtkit-daemon[1396]: Supervising 8 threads of 2 processes of 1 users.
Apr 19 00:06:38 FX705 rtkit-daemon[1396]: Supervising 8 threads of 2 processes of 1 users.
Apr 19 00:06:38 FX705 rtkit-daemon[1396]: Supervising 8 threads of 2 processes of 1 users.
Apr 19 00:04:50 FX705 systemd[1]: NetworkManager-dispatcher.service: Succeeded.

Apr 19 00:04:50 FX705 systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Apr 19 00:04:40 FX705 kernel: iwlwifi 0000:00:14.3: iwl_trans_send_cmd bad state = 0
Apr 19 00:04:40 FX705 wpa_supplicant[880]: nl80211: deinit ifname=wlo1 disabled_11b_rates=0
Apr 19 00:04:40 FX705 nm-dispatcher[15951]: run-parts: failed to stat component /etc/network/if-post-down.d/avahi-daemon: No such file or directory
Apr 19 00:04:40 FX705 NetworkManager[819]: <info>  [1650344680.8096] device (p2p-dev-wlo1): state change: disconnected -> unavailable (reason 'supplicant-failed', sys-iface-state: 'managed')
Apr 19 00:04:40 FX705 NetworkManager[819]: <info>  [1650344680.8088] manager: rfkill: Wi-Fi now disabled by radio killswitch
Apr 19 00:04:40 FX705 wpa_supplicant[880]: nl80211: deinit ifname=p2p-dev-wlo1 disabled_11b_rates=0
Apr 19 00:04:40 FX705 NetworkManager[819]: <info>  [1650344680.8086] audit: op="radio-control" arg="wireless-enabled" pid=1723 uid=1000 result="success"
Apr 19 00:04:40 FX705 wpa_supplicant[880]: wlo1: PMKSA-CACHE-REMOVED 28:80:a2:d9:4b:16 0
Apr 19 00:04:40 FX705 NetworkManager[819]: <info>  [1650344680.8004] dhcp4 (wlo1): state changed bound -> done
Apr 19 00:04:40 FX705 NetworkManager[819]: <info>  [1650344680.8003] dhcp4 (wlo1): canceled DHCP transaction
Apr 19 00:04:40 FX705 wpa_supplicant[880]: rfkill: WLAN soft blocked
Apr 19 00:04:40 FX705 wpa_supplicant[880]: rfkill: WLAN soft blocked
Apr 19 00:04:40 FX705 avahi-daemon[813]: Withdrawing address record for 192.168.1.12 on wlo1.
Apr 19 00:04:40 FX705 avahi-daemon[813]: Withdrawing address record for fe80::d4fb:2b63:b53e:c489 on wlo1.
Apr 19 00:04:40 FX705 wpa_supplicant[880]: wlo1: CTRL-EVENT-DISCONNECTED bssid=28:80:a2:d9:4b:16 reason=3 locally_generated=1
Apr 19 00:04:40 FX705 avahi-daemon[813]: Leaving mDNS multicast group on interface wlo1.IPv4 with address 192.168.1.12.
Apr 19 00:04:40 FX705 avahi-daemon[813]: Interface wlo1.IPv4 no longer relevant for mDNS.
Apr 19 00:04:40 FX705 NetworkManager[819]: <info>  [1650344680.7755] device (wlo1): state change: activated -> unavailable (reason 'none', sys-iface-state: 'managed')
Apr 19 00:04:40 FX705 wpa_supplicant[880]: wlo1: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=0 noise=9999 txrate=0
Apr 19 00:04:40 FX705 NetworkManager[819]: <info>  [1650344680.7754] manager: rfkill: Wi-Fi hardware radio set disabled
Apr 19 00:04:40 FX705 avahi-daemon[813]: Leaving mDNS multicast group on interface wlo1.IPv6 with address fe80::d4fb:2b63:b53e:c489.
Apr 19 00:04:40 FX705 avahi-daemon[813]: Interface wlo1.IPv6 no longer relevant for mDNS.
Apr 19 00:04:40 FX705 kernel: wlo1: deauthenticating from 28:80:a2:d9:4b:16 by local choice (Reason: 3=DEAUTH_LEAVING)
Apr 19 00:04:36 FX705 NetworkManager[819]: <info>  [1650344676.6837] policy: set 'Wired connection 1' (enp3s0) as default for IPv4 routing and DNS

Code: Select all

john@FX705:~$ inxi -F
System:
  Host: FX705 Kernel: 5.13.0-39-generic x86_64 bits: 64 
  Desktop: Cinnamon 5.2.7 Distro: Linux Mint 20.3 Una 
Machine:
  Type: Laptop System: ASUSTeK product: TUF Gaming FX705GM_FX705GM v: 1.0 
  serial: <superuser/root required> 
  Mobo: ASUSTeK model: FX705GM v: 1.0 serial: <superuser/root required> 
  UEFI: American Megatrends v: FX705GM.307 date: 05/25/2020 
Battery:
  ID-1: BAT0 charge: 50.2 Wh condition: 50.2/64.1 Wh (78%) 
CPU:
  Topology: 6-Core model: Intel Core i7-8750H bits: 64 type: MT MCP 
  L2 cache: 9216 KiB 
  Speed: 800 MHz min/max: 800/4100 MHz Core speeds (MHz): 1: 810 2: 4017 
  3: 1002 4: 2627 5: 1160 6: 800 7: 800 8: 1056 9: 800 10: 800 11: 800 
  12: 800 
Graphics:
  Device-1: Intel UHD Graphics 630 driver: i915 v: kernel 
  Device-2: NVIDIA GP106M [GeForce GTX 1060 Mobile] driver: nvidia 
  v: 470.103.01 
  Display: x11 server: X.Org 1.20.13 driver: modesetting,nvidia 
  unloaded: fbdev,nouveau,vesa resolution: 1920x1080~60Hz 
  OpenGL: renderer: NVIDIA GeForce GTX 1060/PCIe/SSE2 
  v: 4.6.0 NVIDIA 470.103.01 
Audio:
  Device-1: Intel Cannon Lake PCH cAVS driver: sof-audio-pci-intel-cnl 
  Device-2: NVIDIA GP106 High Definition Audio driver: snd_hda_intel 
  Sound Server: ALSA v: k5.13.0-39-generic 
Network:
  Device-1: Intel Wireless-AC 9560 [Jefferson Peak] driver: iwlwifi 
  IF: wlo1 state: down mac: b4:69:21:c6:ba:97 
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  driver: r8169 
  IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: 04:92:26:09:82:4c 
Drives:
  Local Storage: total: 1.38 TiB used: 464.39 GiB (33.0%) 
  ID-1: /dev/nvme0n1 vendor: Intel model: SSDPEKNW512G8 size: 476.94 GiB 
  ID-2: /dev/sda vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB 
Partition:
  ID-1: / size: 43.38 GiB used: 21.53 GiB (49.6%) fs: ext4 dev: /dev/sda2 
  ID-2: /home size: 409.90 GiB used: 124.92 GiB (30.5%) fs: ext4 
  dev: /dev/sda4 
Sensors:
  System Temperatures: cpu: 53.0 C mobo: 27.8 C gpu: nvidia temp: 49 C 
  Fan Speeds (RPM): cpu: 0 
Info:
  Processes: 320 Uptime: 13m Memory: 15.48 GiB used: 1.72 GiB (11.1%) 
  Shell: bash inxi: 3.0.38 
john@FX705:~$ 
LM21.3 Cinnamon ASUS FX705GM | Donate to Mint https://www.patreon.com/linux_mint
Image
User avatar
smurphos
Level 18
Level 18
Posts: 8498
Joined: Fri Sep 05, 2014 12:18 am
Location: Irish Brit in Portugal
Contact:

Re: Firefox locking up almost everyday since last update - [ Monitoring after Kernel update to 5.13 ]

Post by smurphos »

There's nothing there that helps

How about output of cat ~/.xsession-errors.old - any relevant lines will be at the end of the output.
For custom Nemo actions, useful scripts for the Cinnamon desktop, and Cinnamox themes visit my Github pages.
User avatar
AZgl1800
Level 20
Level 20
Posts: 11173
Joined: Thu Dec 31, 2015 3:20 am
Location: Oklahoma where the wind comes Sweeping down the Plains
Contact:

Re: Firefox locking up almost everyday since last update - [ Monitoring after Kernel update to 5.13 ]

Post by AZgl1800 »

This looks like a normal "startup" session, and then it all goes to hell with warnings


Code: Select all

john@FX705:~$ cat ~/.xsession-errors.old
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting XAUTHORITY=/home/john/.Xauthority
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting SHELL=/bin/bash
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting XDG_CONFIG_DIRS=/etc/xdg/xdg-cinnamon:/etc/xdg
dbus-update-activation-environment: setting XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
dbus-update-activation-environment: setting LANGUAGE=en_US
dbus-update-activation-environment: setting MANDATORY_PATH=/usr/share/gconf/cinnamon.mandatory.path
dbus-update-activation-environment: setting DESKTOP_SESSION=cinnamon
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting PWD=/home/john
dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=cinnamon
dbus-update-activation-environment: setting LOGNAME=john
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting XAUTHORITY=/home/john/.Xauthority
dbus-update-activation-environment: setting XDG_GREETER_DATA_DIR=/var/lib/lightdm-data/john
dbus-update-activation-environment: setting GDM_LANG=en_US
dbus-update-activation-environment: setting HOME=/home/john
dbus-update-activation-environment: setting IM_CONFIG_PHASE=1
dbus-update-activation-environment: setting LANG=en_US.UTF-8
dbus-update-activation-environment: setting XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
dbus-update-activation-environment: setting XDG_SESSION_CLASS=user
dbus-update-activation-environment: setting DEFAULTS_PATH=/usr/share/gconf/cinnamon.default.path
dbus-update-activation-environment: setting USER=john
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting SHLVL=1
dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000
dbus-update-activation-environment: setting GTK3_MODULES=xapp-gtk3-module
dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/cinnamon:/usr/share/gnome:/home/john/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share
dbus-update-activation-environment: setting PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
dbus-update-activation-environment: setting GDMSESSION=cinnamon
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting _=/usr/bin/dbus-update-activation-environment
** Message: 19:08:45.091: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
** Message: 19:08:45.091: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
** Message: 19:08:45.201: Existing monitor config (/home/john/.config/cinnamon-monitors.xml) not found at startup. Looking for legacy configuration (monitors.xml)
[cinnamon-settings-daemon-smartcard] Failed to start: no suitable smartcard driver could be found
[cinnamon-settings-daemon-smartcard] Failed to start: no suitable smartcard driver could be found
Cjs-Message: 19:08:45.666: Profiler is disabled. Not setting up signals.
Clutter-Message: 19:08:45.716: Sync method: PRESENTATION TIME
Cjs-Message: 19:08:45.880: JS LOG: About to start Cinnamon
Cjs-Message: 19:08:45.998: JS LOG: [LookingGlass/info] Cinnamon.AppSystem.get_default() started in 115 ms
Cjs-Message: 19:08:46.004: JS LOG: [LookingGlass/info] loading user theme: /usr/share/themes/Mint-Y-Dark/cinnamon/cinnamon.css
Cjs-Message: 19:08:46.020: JS LOG: [LookingGlass/info] added icon directory: /usr/share/themes/Mint-Y-Dark/cinnamon
Cjs-Message: 19:08:46.131: JS LOG: [LookingGlass/info] loaded at Mon Apr 18 2022 19:08:46 GMT-0500 (Central Daylight Time)
Cjs-Message: 19:08:46.131: JS LOG: Cinnamon started at Mon Apr 18 2022 19:08:46 GMT-0500 (Central Daylight Time)
Cjs-Message: 19:08:46.143: JS LOG: [LookingGlass/info] ExtensionSystem started in 1 ms
Cjs-Message: 19:08:46.143: JS LOG: [LookingGlass/info] SearchProviderManager started in 0 ms
openGL version 3.1 detected (GL3 Cogl Driver)
cinnamon-session[1387]: WARNING: t+1.10696s: Detected that screensaver has appeared on the bus
** Message: 19:08:46.162: nemo-desktop: session is cinnamon, establishing proxy
Cjs-Message: 19:08:46.183: JS LOG: [LookingGlass/info] Role locked: tray
Cjs-Message: 19:08:46.186: JS LOG: [LookingGlass/info] Loaded applet systray@cinnamon.org in 15 ms
Cjs-Message: 19:08:46.203: JS LOG: [LookingGlass/info] Loaded applet removable-drives@cinnamon.org in 17 ms
Cjs-Message: 19:08:46.213: JS LOG: [LookingGlass/info] Loaded desklet clock@cinnamon.org in 10 ms
Cjs-Message: 19:08:46.214: JS LOG: [LookingGlass/info] NaNms
St-Message: 19:08:46.214: cogl npot texture sizes SUPPORTED
Cjs-Message: 19:08:46.229: JS LOG: [LookingGlass/info] Loaded applet keyboard@cinnamon.org in 16 ms
Cjs-Message: 19:08:46.241: JS LOG: [LookingGlass/info] Loaded applet xapp-status@cinnamon.org in 12 ms
Cjs-Message: 19:08:46.264: JS LOG: [LookingGlass/info] Loaded applet printers@cinnamon.org in 23 ms
Cjs-Message: 19:08:46.271: JS LOG: [LookingGlass/info] Role locked: notifications
Cjs-Message: 19:08:46.275: JS LOG: [LookingGlass/info] Loaded applet notifications@cinnamon.org in 11 ms
Cjs-Message: 19:08:46.304: JS LOG: [LookingGlass/info] Loaded applet calendar@cinnamon.org in 29 ms
Cjs-Message: 19:08:46.332: JS LOG: [LookingGlass/warning] 
QRedshift: Created
Cjs-Message: 19:08:46.348: JS LOG: [LookingGlass/warning] 
QRedshift: ADDED TO PANEL
Cjs-Message: 19:08:46.348: JS LOG: [LookingGlass/info] Loaded applet qredshift@quintao in 44 ms
Cjs-Message: 19:08:46.359: JS LOG: [LookingGlass/info] Loaded applet power@cinnamon.org in 11 ms
Cjs-Message: 19:08:46.373: JS LOG: [LookingGlass/info] Role locked: panellauncher
Cjs-Message: 19:08:46.375: JS LOG: [LookingGlass/info] Loaded applet grouped-window-list@cinnamon.org in 16 ms
Cjs-Message: 19:08:46.395: JS LOG: [LookingGlass/info] Adding XAppStatusIcon: nm-applet (:1.88/org/x/StatusIcon/Icon)

(cinnamon:1723): Gtk-WARNING **: 19:08:46.449: Could not load a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.
Cjs-Message: 19:08:46.470: JS LOG: [LookingGlass/info] Loaded applet sound@cinnamon.org in 95 ms
Cjs-Message: 19:08:46.536: JS LOG: [LookingGlass/info] Hiding XAppStatusIcon (we have an applet): nm-applet (:1.88/org/x/StatusIcon/Icon)
Cjs-Message: 19:08:46.541: JS LOG: [LookingGlass/info] Loaded applet network@cinnamon.org in 71 ms
Cjs-Message: 19:08:46.657: JS LOG: [LookingGlass/info] Loaded applet menu@cinnamon.org in 116 ms
Cjs-Message: 19:08:46.657: JS LOG: [LookingGlass/info] AppletManager started in 525 ms
Cjs-Message: 19:08:46.659: JS LOG: [LookingGlass/info] Cinnamon took 779 ms to start
Cjs-Message: 19:08:46.668: JS LOG: Unknown network device type, is 14
Cjs-Message: 19:08:46.680: JS LOG: Unknown network device type, is 30
Cjs-Message: 19:08:46.987: JS LOG: [LookingGlass/info] Adding XAppStatusIcon: nvidia-prime (:1.96/org/x/StatusIcon/Icon)
Cjs-Message: 19:08:51.490: JS LOG: [LookingGlass/info] Adding XAppStatusIcon: blueberry (:1.130/org/x/StatusIcon/Icon)
Cjs-Message: 19:09:07.406: JS LOG: [LookingGlass/info] Adding XAppStatusIcon: mintUpdate.py (:1.158/org/x/StatusIcon/Icon)
cinnamon-session[1387]: WARNING: t+31.11496s: Detected that screensaver has left the bus
Cjs-Message: 19:09:26.779: JS LOG: [LookingGlass/info] Adding XAppStatusIcon: mintreport (:1.167/org/x/StatusIcon/Icon)
qt5ct: using qt5ct plugin
Error unsetting QT_QPA_PLATFORMTHEME vble
Cjs-Message: 19:09:46.661: JS LOG: [LookingGlass/info] Adding XAppStatusIcon: org.kde.statusnotifieritem-3439-1 (:1.80/org/x/StatusIcon/Icon)

(cinnamon:1723): Clutter-WARNING **: 19:09:57.571: clutter-actor.c:10052: Actor 'StBin' tried to allocate a size of -75.00 x 20.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.571: clutter-actor.c:10052: Actor 'StBin' tried to allocate a size of -75.00 x 20.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.572: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.572: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.572: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.572: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.572: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.572: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.572: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.572: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.573: clutter-actor.c:10052: Actor 'StBin' tried to allocate a size of -75.00 x 20.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.576: clutter-actor.c:10052: Actor 'StBin' tried to allocate a size of -75.00 x 20.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.576: clutter-actor.c:10052: Actor 'StBin' tried to allocate a size of -75.00 x 20.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.576: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.576: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.576: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.576: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.576: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.577: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.577: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.577: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.577: clutter-actor.c:10052: Actor 'StBin' tried to allocate a size of -75.00 x 20.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.579: clutter-actor.c:10052: Actor 'StBin' tried to allocate a size of -75.00 x 20.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.579: clutter-actor.c:10052: Actor 'StBin' tried to allocate a size of -75.00 x 20.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.579: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.579: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.579: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.579: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.579: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.579: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.579: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.580: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.580: clutter-actor.c:10052: Actor 'StBin' tried to allocate a size of -75.00 x 20.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.582: clutter-actor.c:10052: Actor 'StBin' tried to allocate a size of -75.00 x 20.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.582: clutter-actor.c:10052: Actor 'StBin' tried to allocate a size of -75.00 x 20.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.582: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.582: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.582: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.582: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.582: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.582: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.582: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.582: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.582: clutter-actor.c:10052: Actor 'StBin' tried to allocate a size of -75.00 x 20.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.585: clutter-actor.c:10052: Actor 'StBin' tried to allocate a size of -75.00 x 20.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.585: clutter-actor.c:10052: Actor 'StBin' tried to allocate a size of -75.00 x 20.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.585: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.585: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.585: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.585: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.585: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.585: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.585: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.585: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.585: clutter-actor.c:10052: Actor 'StBin' tried to allocate a size of -75.00 x 20.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.587: clutter-actor.c:10052: Actor 'StBin' tried to allocate a size of -75.00 x 20.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.588: clutter-actor.c:10052: Actor 'StBin' tried to allocate a size of -75.00 x 20.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.588: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.588: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.588: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.588: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.588: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.588: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.588: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.588: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.588: clutter-actor.c:10052: Actor 'StBin' tried to allocate a size of -75.00 x 20.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.590: clutter-actor.c:10052: Actor 'StBin' tried to allocate a size of -75.00 x 20.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.590: clutter-actor.c:10052: Actor 'StBin' tried to allocate a size of -75.00 x 20.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.590: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.591: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.591: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.591: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.591: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.591: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.591: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.591: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.591: clutter-actor.c:10052: Actor 'StBin' tried to allocate a size of -75.00 x 20.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.593: clutter-actor.c:10052: Actor 'StBin' tried to allocate a size of -75.00 x 20.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.593: clutter-actor.c:10052: Actor 'StBin' tried to allocate a size of -75.00 x 20.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.593: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.593: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.593: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.594: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.594: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.594: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.594: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.594: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.594: clutter-actor.c:10052: Actor 'StBin' tried to allocate a size of -75.00 x 20.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.596: clutter-actor.c:10052: Actor 'StBin' tried to allocate a size of -75.00 x 20.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.596: clutter-actor.c:10052: Actor 'StBin' tried to allocate a size of -75.00 x 20.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.596: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.596: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.597: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.597: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.597: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.597: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.597: clutter-actor.c:10052: Actor 'StLabel' tried to allocate a size of -1.00 x 29.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.597: clutter-actor.c:10052: Actor 'StBoxLayout' tried to allocate a size of -109.00 x 16.00

(cinnamon:1723): Clutter-WARNING **: 19:09:57.597: clutter-actor.c:10052: Actor 'StBin' tried to allocate a size of -75.00 x 20.00

(cinnamon:1723): Clutter-CRITICAL **: 19:26:38.870: clutter_actor_iter_next: assertion 'ri->age == ri->root->priv->age' failed

(xapp-sn-watcher:1745): LIBDBUSMENU-GLIB-WARNING **: 19:30:18.420: Unable to replace properties on 0: Error getting properties for ID
** Message: 19:50:02.529: Existing monitor config (/home/john/.config/cinnamon-monitors.xml) not found during hotplug or laptop lid event. Looking for legacy configuration (monitors.xml)
** Message: 20:00:23.159: Existing monitor config (/home/john/.config/cinnamon-monitors.xml) not found during hotplug or laptop lid event. Looking for legacy configuration (monitors.xml)

(nemo:8908): Gtk-WARNING **: 20:19:35.701: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_num_locks
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_id_callback
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_locking_callback
qt.network.ssl: QSslSocket: cannot resolve ERR_free_strings
qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_cleanup
qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_init
qt.network.ssl: QSslSocket: cannot resolve sk_new_null
qt.network.ssl: QSslSocket: cannot resolve sk_push
qt.network.ssl: QSslSocket: cannot resolve sk_free
qt.network.ssl: QSslSocket: cannot resolve sk_num
qt.network.ssl: QSslSocket: cannot resolve sk_pop_free
qt.network.ssl: QSslSocket: cannot resolve sk_value
qt.network.ssl: QSslSocket: cannot resolve SSL_library_init
qt.network.ssl: QSslSocket: cannot resolve SSL_load_error_strings
qt.network.ssl: QSslSocket: cannot resolve SSL_get_ex_new_index
qt.network.ssl: QSslSocket: cannot resolve SSLv3_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv23_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv3_server_method
qt.network.ssl: QSslSocket: cannot resolve SSLv23_server_method
qt.network.ssl: QSslSocket: cannot resolve X509_STORE_CTX_get_chain
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf
qt.network.ssl: QSslSocket: cannot resolve SSLeay
qt.network.ssl: QSslSocket: cannot resolve SSLeay_version
qt.network.ssl: QSslSocket: cannot call unresolved function SSLeay
qt.network.ssl: Incompatible version of OpenSSL

(cinnamon:1723): Clutter-CRITICAL **: 20:22:56.433: clutter_actor_iter_next: assertion 'ri->age == ri->root->priv->age' failed

(cinnamon:1723): Clutter-CRITICAL **: 20:23:12.812: clutter_actor_iter_next: assertion 'ri->age == ri->root->priv->age' failed

(cinnamon:1723): Clutter-CRITICAL **: 20:23:42.058: clutter_actor_iter_next: assertion 'ri->age == ri->root->priv->age' failed

(cinnamon:1723): Clutter-CRITICAL **: 20:26:40.381: clutter_actor_iter_next: assertion 'ri->age == ri->root->priv->age' failed

(cinnamon:1723): Clutter-CRITICAL **: 20:26:58.079: clutter_actor_iter_next: assertion 'ri->age == ri->root->priv->age' failed

(cinnamon:1723): Clutter-CRITICAL **: 20:31:30.989: clutter_actor_iter_next: assertion 'ri->age == ri->root->priv->age' failed

(cinnamon:1723): Clutter-CRITICAL **: 20:31:44.013: clutter_actor_iter_next: assertion 'ri->age == ri->root->priv->age' failed

(cinnamon:1723): Clutter-CRITICAL **: 20:31:44.540: clutter_actor_iter_next: assertion 'ri->age == ri->root->priv->age' failed
** Message: 20:44:09.025: Existing monitor config (/home/john/.config/cinnamon-monitors.xml) not found during hotplug or laptop lid event. Looking for legacy configuration (monitors.xml)
** Message: 21:09:42.215: Existing monitor config (/home/john/.config/cinnamon-monitors.xml) not found during hotplug or laptop lid event. Looking for legacy configuration (monitors.xml)

(cinnamon:1723): Clutter-CRITICAL **: 21:19:07.516: clutter_actor_iter_next: assertion 'ri->age == ri->root->priv->age' failed

###!!! [Parent][PBackgroundParent] Error: RunMessage(msgname=PMessagePort::Msg_Close) Channel closing: too late to send/recv, messages will be lost


###!!! [Parent][PBackgroundParent] Error: RunMessage(msgname=PMessagePort::Msg_Close) Channel closing: too late to send/recv, messages will be lost


###!!! [Parent][PBackgroundParent] Error: RunMessage(msgname=PMessagePort::Msg_Close) Channel closing: too late to send/recv, messages will be lost


###!!! [Parent][PBackgroundParent] Error: RunMessage(msgname=PMessagePort::Msg_Close) Channel closing: too late to send/recv, messages will be lost


###!!! [Parent][PBackgroundParent] Error: RunMessage(msgname=PMessagePort::Msg_Close) Channel closing: too late to send/recv, messages will be lost


###!!! [Parent][PBackgroundParent] Error: RunMessage(msgname=PMessagePort::Msg_Close) Channel closing: too late to send/recv, messages will be lost


###!!! [Parent][PBackgroundParent] Error: RunMessage(msgname=PMessagePort::Msg_Close) Channel closing: too late to send/recv, messages will be lost


###!!! [Parent][PBackgroundParent] Error: RunMessage(msgname=PMessagePort::Msg_Close) Channel closing: too late to send/recv, messages will be lost


###!!! [Parent][PBackgroundParent] Error: RunMessage(msgname=PMessagePort::Msg_Close) Channel closing: too late to send/recv, messages will be lost


###!!! [Parent][PBackgroundParent] Error: RunMessage(msgname=PMessagePort::Msg_Close) Channel closing: too late to send/recv, messages will be lost


###!!! [Parent][PBackgroundParent] Error: RunMessage(msgname=PBackgroundIDBDatabase::Msg_Close) Channel closing: too late to send/recv, messages will be lost

Cinnamon warning: Invalid WM_TRANSIENT_FOR window 0x600009b specified for 0x60000c8 (Text Impor).

###!!! [Parent][PContentParent] Error: Send(msgname=PContent::Msg_DestroyBrowsingContextGroup) Closed channel: cannot send/recv


(cinnamon:1723): Clutter-CRITICAL **: 22:00:34.698: clutter_actor_iter_next: assertion 'ri->age == ri->root->priv->age' failed

(cinnamon:1723): Clutter-CRITICAL **: 22:00:43.744: clutter_actor_iter_next: assertion 'ri->age == ri->root->priv->age' failed

(cinnamon:1723): Clutter-CRITICAL **: 22:00:44.107: clutter_actor_iter_next: assertion 'ri->age == ri->root->priv->age' failed

###!!! [Parent][PImageBridgeParent] Error: RunMessage(msgname=PImageBridge::Msg_WillClose) Channel closing: too late to send/recv, messages will be lost

** Message: 22:49:05.373: Existing monitor config (/home/john/.config/cinnamon-monitors.xml) not found during hotplug or laptop lid event. Looking for legacy configuration (monitors.xml)
** Message: 23:38:03.901: Existing monitor config (/home/john/.config/cinnamon-monitors.xml) not found during hotplug or laptop lid event. Looking for legacy configuration (monitors.xml)

(cinnamon:1723): Clutter-CRITICAL **: 23:54:14.395: clutter_actor_iter_next: assertion 'ri->age == ri->root->priv->age' failed
Cjs-Message: 23:54:16.559: JS LOG: [LookingGlass/info] Adding XAppStatusIcon:  (:1.80/org/x/StatusIcon/Icon_1)

(cinnamon:1723): Clutter-CRITICAL **: 23:58:47.503: clutter_actor_iter_next: assertion 'ri->age == ri->root->priv->age' failed
nm-applet-Message: 00:00:48.119: No keyring secrets found for Auto TP-LINK_Extender_5GHz/802-11-wireless-security; asking user.
john@FX705:~$ 
LM21.3 Cinnamon ASUS FX705GM | Donate to Mint https://www.patreon.com/linux_mint
Image
User avatar
SMG
Level 25
Level 25
Posts: 31813
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Firefox locking up almost everyday since last update - [ Monitoring after Kernel update to 5.13 ]

Post by SMG »

AZgl1800 wrote: Tue Apr 19, 2022 8:53 am This looks like a normal "startup" session, and then it all goes to hell with warnings
Seems you might have a KDE app using qt5ct plugin that might be causing the warnings, but there is only one message around the time you indicate the freeze happened and it happened about three minutes prior.

Code: Select all

nm-applet-Message: 00:00:48.119: No keyring secrets found for Auto TP-LINK_Extender_5GHz/802-11-wireless-security; asking user.
The hamberger button you mention is a button on the Youtube webpage, correct?
Image
A woman typing on a laptop with LM20.3 Cinnamon.
User avatar
AZgl1800
Level 20
Level 20
Posts: 11173
Joined: Thu Dec 31, 2015 3:20 am
Location: Oklahoma where the wind comes Sweeping down the Plains
Contact:

Re: Firefox locking up almost everyday since last update - [ Monitoring after Kernel update to 5.13 ]

Post by AZgl1800 »

SMG wrote: Tue Apr 19, 2022 9:50 am
AZgl1800 wrote: Tue Apr 19, 2022 8:53 am This looks like a normal "startup" session, and then it all goes to hell with warnings
Seems you might have a KDE app using qt5ct plugin that might be causing the warnings, but there is only one message around the time you indicate the freeze happened and it happened about three minutes prior.

Code: Select all

nm-applet-Message: 00:00:48.119: No keyring secrets found for Auto TP-LINK_Extender_5GHz/802-11-wireless-security; asking user.
The hamburger button you mention is a button on the Youtube webpage, correct?
Yes, it was the menu in YouTube.

the Auto TP-LINK is a brand new WiFi bridge to LAN that I just purchased and was using for the first time yesterday, it has not been part of the system ever before, so is an isolated one time thing as of this instance.

I got it because my daughter is looking for @Home Work, and what she has discovered is that all of those Employers provide a Laptop w/o WiFi period, they will only accept a LAN connection.... rather dumb IMO, but hey... it is their PC.
I needed to find out how well it works, and it works BETTER than my Laptop's internal WiFi setup :!: :!: :!:

We have two (2) Wireless Hotspots on T-Mobile, so I setup the TP-LINK to use one channel from each of them.
That way, her @Home PC will have a "Fail Over" Internet connection.

I may be old, but I haven't forgotten how to do some things to get around having a Fiber LAN connection :mrgreen:
LM21.3 Cinnamon ASUS FX705GM | Donate to Mint https://www.patreon.com/linux_mint
Image
Locked

Return to “Software & Applications”