how to diagnose unexpected shutdowns

All Gurus once were Newbies
Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Please stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions prefer the other forums within the support section.
Before you post please read how to get help
Post Reply
User avatar
DarrenG
Level 1
Level 1
Posts: 46
Joined: Mon Jun 23, 2014 9:12 pm
Location: New Zealand

how to diagnose unexpected shutdowns

Post by DarrenG » Fri Nov 09, 2018 5:21 pm

Hi, I have been using linux mint 19 Tara 64bit with Cinnamon happily since it came out. Yesterday and just now my computer unexpectedly turned off without any warning. Everything is up-to-date and I haven't made any changes recently. I've been looking around for how-to's on diagnosing causes for this and most of the guides seem to be from back in the days of mint 12.
1) Can someone point me in the direction of a more recent guide to diagnosing shutdowns with no warning?
2) Has anyone else experienced the same problem in the last couple of days or is it just me?

I'll probably do a clean install of 19.1 when it comes out, but for all I know this could also be a hardware issue. Where do I start?
“People shouldn't be afraid of their government. Governments should be afraid of their people.”

User avatar
Pjotr
Level 20
Level 20
Posts: 11053
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland)
Contact:

Re: how to diagnose unexpected shutdowns

Post by Pjotr » Fri Nov 09, 2018 5:53 pm

You might find this thread interesting:
viewtopic.php?f=49&t=281275
Tip: 10 things to do after installing Linux Mint 19 Tara
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.

User avatar
DarrenG
Level 1
Level 1
Posts: 46
Joined: Mon Jun 23, 2014 9:12 pm
Location: New Zealand

Re: how to diagnose unexpected shutdowns

Post by DarrenG » Sun Nov 11, 2018 7:52 am

Thank you Pjotr, I have applied your advice at https://sites.google.com/site/easylinux ... -computers and will see if that helps.

Code: Select all

System:    Host: desktop Kernel: 4.15.0-38-generic x86_64 bits: 64 gcc: 7.3.0
           Desktop: Cinnamon 3.8.9 (Gtk 3.22.30-1ubuntu1)
           Distro: Linux Mint 19 Tara
Machine:   Device: desktop Mobo: ASRock model: H110M-DGS serial: N/A
           UEFI [Legacy]: American Megatrends v: L1.71 date: 06/16/2016
CPU:       Dual core Intel Pentium G4400 (-MCP-) 
           arch: Skylake-S rev.3 cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 13248
           clock speeds: max: 3300 MHz 1: 800 MHz 2: 800 MHz
Graphics:  Card: Intel HD Graphics 510 bus-ID: 00:02.0
           Display Server: x11 (X.Org 1.19.6 )
           drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1680x1050@59.88hz
           OpenGL: renderer: Mesa DRI Intel HD Graphics 510 (Skylake GT1)
           version: 4.5 Mesa 18.0.5 Direct Render: Yes
Audio:     Card Intel Sunrise Point-H HD Audio
           driver: snd_hda_intel bus-ID: 00:1f.3
           Sound: Advanced Linux Sound Architecture v: k4.15.0-38-generic
Network:   Card: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: e000 bus-ID: 02:00.0
           IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 620.1GB (78.6% used)
           ID-1: /dev/sdb model: ST3500413AS size: 500.1GB temp: 33C
           ID-2: /dev/sda model: SanDisk_SDSSDA12 size: 120.0GB temp: 28C
Partition: ID-1: / size: 19G used: 8.7G (49%) fs: ext4 dev: /dev/sda2
           ID-2: /home size: 75G used: 51G (73%) fs: ext4 dev: /dev/sda3
           ID-3: /boot size: 976M used: 151M (17%) fs: ext4 dev: /dev/sda1
           ID-4: swap-1 size: 17.18GB used: 0.00GB (0%)
           fs: swap dev: /dev/sda4
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 35.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 183 Uptime: 1:21 Memory: 2697.9/7677.6MB
           Init: systemd runlevel: 5 Gcc sys: 7.3.0
           Client: Shell (bash 4.4.191) inxi: 2.3.56 
“People shouldn't be afraid of their government. Governments should be afraid of their people.”

User avatar
trytip
Level 8
Level 8
Posts: 2475
Joined: Tue Jul 05, 2016 1:20 pm

Re: how to diagnose unexpected shutdowns

Post by trytip » Sun Nov 11, 2018 10:59 am

open Logs and check the Important tab. after a "crash" when you reboot check the .xsession-errors.old
Image

User avatar
DarrenG
Level 1
Level 1
Posts: 46
Joined: Mon Jun 23, 2014 9:12 pm
Location: New Zealand

Re: how to diagnose unexpected shutdowns

Post by DarrenG » Fri Nov 16, 2018 9:45 pm

After six days without a crash I was thinking of marking this solved, but then it happened again this morning. My Daughter was using chrome. I prefer waterfox so I very seldom use chrome so I don't think that is the problem. She told me it happened around 11:30 and this is the output from logs/important

Code: Select all

11:22:42 pulseaudio: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
11:22:16 hpfax: [1385]: error: Failed to create /var/spool/cups/tmp/.hplip
11:22:12 lightdm: PAM adding faulty module: pam_kwallet5.so
11:22:08 systemd-udevd: Invalid rule /etc/udev/rules.d/60-brother-libsane-type1-inst.rules:14: unknown key 'SYSFS{idVendor}'
11:22:07 kernel: ACPI Error: 1 table load failures, 4 successful (20170831/tbxfload-246)
11:22:07 kernel: ACPI Error: 1 table load failures, 4 successful (20170831/tbxfload-246)
11:22:07 kernel: ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp08) while loading table (20170831/tbxfload-228)
11:22:07 kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170831/psobject-252)
11:22:07 kernel: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload-210)
and this is the output of .xsession-errors.old

Code: Select all

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/darren/.Xauthority
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting LANG=en_NZ.UTF-8
dbus-update-activation-environment: setting GDM_LANG=en_US
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting MANDATORY_PATH=/usr/share/gconf/cinnamon.mandatory.path
dbus-update-activation-environment: setting XDG_GREETER_DATA_DIR=/var/lib/lightdm-data/darren
dbus-update-activation-environment: setting USER=darren
dbus-update-activation-environment: setting DESKTOP_SESSION=cinnamon
dbus-update-activation-environment: setting DEFAULTS_PATH=/usr/share/gconf/cinnamon.default.path
dbus-update-activation-environment: setting PWD=/home/darren
dbus-update-activation-environment: setting HOME=/home/darren
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/cinnamon:/usr/share/gnome:/home/darren/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share
dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=cinnamon
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting SHELL=/bin/bash
dbus-update-activation-environment: setting XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
dbus-update-activation-environment: setting IM_CONFIG_PHASE=1
dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting SHLVL=1
dbus-update-activation-environment: setting LANGUAGE=en_NZ:en
dbus-update-activation-environment: setting GDMSESSION=cinnamon
dbus-update-activation-environment: setting LOGNAME=darren
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000
dbus-update-activation-environment: setting XAUTHORITY=/home/darren/.Xauthority
dbus-update-activation-environment: setting XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session2
dbus-update-activation-environment: setting XDG_CONFIG_DIRS=/etc/xdg/xdg-cinnamon:/etc/xdg
dbus-update-activation-environment: setting PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
dbus-update-activation-environment: setting _=/usr/bin/dbus-update-activation-environment
[cinnamon-settings-daemon-smartcard] Failed to start: no suitable smartcard driver could be found
cinnamon-session[6142]: WARNING: t+1.09931s: Failed to start app: Unable to start application: Failed to execute child process (No such file or directory)

(nm-applet:6396): Gtk-WARNING **: 19:19:25.435: Can't set a parent on widget which has a parent
Cjs-Message: 19:19:25.549: JS LOG: About to start Cinnamon
** Message: 19:19:25.589: nemo-desktop: session is cinnamon, establishing proxy
Cjs-Message: 19:19:25.625: JS LOG: [LookingGlass/info] Cinnamon.AppSystem.get_default() started in 74 ms
Cjs-Message: 19:19:25.629: JS LOG: [LookingGlass/info] loading user theme: /usr/share/themes/Linux Mint/cinnamon/cinnamon.css
Cjs-Message: 19:19:25.641: JS LOG: [LookingGlass/info] added icon directory: /usr/share/themes/Linux Mint/cinnamon
Cjs-Message: 19:19:25.704: JS LOG: [LookingGlass/info] PlacesManager: Updating devices
St-Message: 19:19:25.715: cogl npot texture sizes SUPPORTED
Cjs-Message: 19:19:25.723: JS LOG: [LookingGlass/info] loaded at Fri Nov 16 2018 19:19:25 GMT+1300 (NZDT)
Cjs-Message: 19:19:25.723: JS LOG: Cinnamon started at Fri Nov 16 2018 19:19:25 GMT+1300 (NZDT)
Cjs-Message: 19:19:25.740: JS LOG: [LookingGlass/info] ExtensionSystem started in 2 ms
Cjs-Message: 19:19:25.740: JS LOG: [LookingGlass/info] DeskletManager started in 2 ms
Cjs-Message: 19:19:25.740: JS LOG: [LookingGlass/info] SearchProviderManager started in 0 ms
openGL version 4.5 detected (GL3 Cogl Driver)
MetaSyncRing disabled: couldn't find required GL extensions, or the minimum safe openGL version was not met
Cjs-Message: 19:19:25.780: JS LOG: [LookingGlass/info] Adding indicator: nm-applet
Cjs-Message: 19:19:25.877: JS LOG: [LookingGlass/info] Loaded applet show-desktop@cinnamon.org in 28 ms
Cjs-Message: 19:19:25.884: JS LOG: [LookingGlass/info] Loaded applet removable-drives@cinnamon.org in 8 ms
Cjs-Message: 19:19:25.907: JS LOG: [LookingGlass/info] Loaded applet calendar@cinnamon.org in 22 ms
Cjs-Message: 19:19:25.920: JS LOG: [LookingGlass/info] Loaded applet systray@cinnamon.org in 14 ms
Cjs-Message: 19:19:25.934: JS LOG: [LookingGlass/info] Loaded applet keyboard@cinnamon.org in 14 ms
Cjs-Message: 19:19:26.012: JS LOG: [LookingGlass/info] Role locked: panellauncher
Cjs-Message: 19:19:26.026: JS LOG: [LookingGlass/info] Loaded applet panel-launchers@cinnamon.org in 92 ms
Cjs-Message: 19:19:26.067: JS LOG: [LookingGlass/info] Loaded applet window-list@cinnamon.org in 40 ms
Cjs-Message: 19:19:26.102: JS LOG: [LookingGlass/info] Loaded applet sound@cinnamon.org in 36 ms
Cjs-Message: 19:19:26.531: JS LOG: [LookingGlass/info] Loaded applet menu@cinnamon.org in 428 ms
Cjs-Message: 19:19:26.531: JS LOG: [LookingGlass/info] AppletManager started in 806 ms
Cjs-Message: 19:19:26.533: JS LOG: [LookingGlass/info] Cinnamon took 984 ms to start
Reading profile /etc/firejail/google-chrome-stable.profile
Reading profile /etc/firejail/google-chrome.profile
Reading profile /etc/firejail/disable-common.inc
Reading profile /etc/firejail/disable-devel.inc
Reading profile /etc/firejail/disable-programs.inc
Reading profile /etc/firejail/whitelist-common.inc
Reading profile /etc/firejail/whitelist-var-common.inc
/usr/bin/google-chrome-stable: line 45: /dev/fd/62: No such file or directory
/usr/bin/google-chrome-stable: line 46: /dev/fd/62: No such file or directory
[50:50:1116/192321.571011:ERROR:buffer_manager.cc(491)] [.BrowserCompositor-0x2ee662a95700]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command
Cinnamon warning: Log level 16: STACK_OP_RAISE_ABOVE: sibling window 0x4400001 not in stack
[6:6:1116/212629.695440:ERROR:http_bridge.cc(126)] Not implemented reached in virtual void syncer::HttpBridgeFactory::OnSignalReceived()
Gtk-Message: 21:26:33.660: GtkDialog mapped without a transient parent. This is discouraged.
sys:1: Warning: ../../../../gobject/gsignal.c:2641: instance '0x55588e4e3ee0' has no handler with id '330'
cinnamon-session[6142]: GLib-GIO-CRITICAL: t+7630.68963s: g_dbus_connection_call_sync_internal: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Gdk-Message: 21:26:34.828: csd-power: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.829: csd-automount: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.829: csd-a11y-settings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.832: csd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.832: csd-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.832: mintUpdate.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.832: nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.832: csd-screensaver-proxy: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.832: csd-a11y-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.832: csd-orientation: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.832: csd-xrandr: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.832: csd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.833: csd-background: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.835: cinnamon-killer-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.835: csd-clipboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.835: csd-print-notifications: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.836: csd-sound: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.836: csd-mouse: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.836: csd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.836: csd-cursor: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.843: csd-housekeeping: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.844: csd-color: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.847: cinnamon-screensaver-main.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.855: cinnamon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.911: cinnamon-launcher: Fatal IO error 2 (No such file or directory) on X server :0.


(metacity:8975): metacity-CRITICAL **: 21:26:35.001: Unable to open X display :0
Unable to init server: Could not connect: Connection refused

(mate-panel:8977): Gtk-WARNING **: 21:26:35.006: cannot open display: :0
Last edited by DarrenG on Sat Nov 17, 2018 5:13 am, edited 1 time in total.
“People shouldn't be afraid of their government. Governments should be afraid of their people.”

User avatar
DarrenG
Level 1
Level 1
Posts: 46
Joined: Mon Jun 23, 2014 9:12 pm
Location: New Zealand

Re: how to diagnose unexpected shutdowns

Post by DarrenG » Fri Nov 16, 2018 9:47 pm

DarrenG wrote:
Fri Nov 16, 2018 9:45 pm
After six days without a crash I was thinking of marking this solved, but then it happened again this morning. My Daughter was using chrome. I prefer waterfox so I very seldom use chrome so I don't think that is the problem. This is the output from logs/important

Code: Select all

11:22:42 pulseaudio: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
11:22:16 hpfax: [1385]: error: Failed to create /var/spool/cups/tmp/.hplip
11:22:12 lightdm: PAM adding faulty module: pam_kwallet5.so
11:22:08 systemd-udevd: Invalid rule /etc/udev/rules.d/60-brother-libsane-type1-inst.rules:14: unknown key 'SYSFS{idVendor}'
11:22:07 kernel: ACPI Error: 1 table load failures, 4 successful (20170831/tbxfload-246)
11:22:07 kernel: ACPI Error: 1 table load failures, 4 successful (20170831/tbxfload-246)
11:22:07 kernel: ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp08) while loading table (20170831/tbxfload-228)
11:22:07 kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170831/psobject-252)
11:22:07 kernel: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload-210)
and this is the output of .xsession-errors.old

Code: Select all

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/darren/.Xauthority
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting LANG=en_NZ.UTF-8
dbus-update-activation-environment: setting GDM_LANG=en_US
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting MANDATORY_PATH=/usr/share/gconf/cinnamon.mandatory.path
dbus-update-activation-environment: setting XDG_GREETER_DATA_DIR=/var/lib/lightdm-data/darren
dbus-update-activation-environment: setting USER=darren
dbus-update-activation-environment: setting DESKTOP_SESSION=cinnamon
dbus-update-activation-environment: setting DEFAULTS_PATH=/usr/share/gconf/cinnamon.default.path
dbus-update-activation-environment: setting PWD=/home/darren
dbus-update-activation-environment: setting HOME=/home/darren
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/cinnamon:/usr/share/gnome:/home/darren/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share
dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=cinnamon
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting SHELL=/bin/bash
dbus-update-activation-environment: setting XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
dbus-update-activation-environment: setting IM_CONFIG_PHASE=1
dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting SHLVL=1
dbus-update-activation-environment: setting LANGUAGE=en_NZ:en
dbus-update-activation-environment: setting GDMSESSION=cinnamon
dbus-update-activation-environment: setting LOGNAME=darren
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000
dbus-update-activation-environment: setting XAUTHORITY=/home/darren/.Xauthority
dbus-update-activation-environment: setting XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session2
dbus-update-activation-environment: setting XDG_CONFIG_DIRS=/etc/xdg/xdg-cinnamon:/etc/xdg
dbus-update-activation-environment: setting PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
dbus-update-activation-environment: setting _=/usr/bin/dbus-update-activation-environment
[cinnamon-settings-daemon-smartcard] Failed to start: no suitable smartcard driver could be found
cinnamon-session[6142]: WARNING: t+1.09931s: Failed to start app: Unable to start application: Failed to execute child process (No such file or directory)

(nm-applet:6396): Gtk-WARNING **: 19:19:25.435: Can't set a parent on widget which has a parent
Cjs-Message: 19:19:25.549: JS LOG: About to start Cinnamon
** Message: 19:19:25.589: nemo-desktop: session is cinnamon, establishing proxy
Cjs-Message: 19:19:25.625: JS LOG: [LookingGlass/info] Cinnamon.AppSystem.get_default() started in 74 ms
Cjs-Message: 19:19:25.629: JS LOG: [LookingGlass/info] loading user theme: /usr/share/themes/Linux Mint/cinnamon/cinnamon.css
Cjs-Message: 19:19:25.641: JS LOG: [LookingGlass/info] added icon directory: /usr/share/themes/Linux Mint/cinnamon
Cjs-Message: 19:19:25.704: JS LOG: [LookingGlass/info] PlacesManager: Updating devices
St-Message: 19:19:25.715: cogl npot texture sizes SUPPORTED
Cjs-Message: 19:19:25.723: JS LOG: [LookingGlass/info] loaded at Fri Nov 16 2018 19:19:25 GMT+1300 (NZDT)
Cjs-Message: 19:19:25.723: JS LOG: Cinnamon started at Fri Nov 16 2018 19:19:25 GMT+1300 (NZDT)
Cjs-Message: 19:19:25.740: JS LOG: [LookingGlass/info] ExtensionSystem started in 2 ms
Cjs-Message: 19:19:25.740: JS LOG: [LookingGlass/info] DeskletManager started in 2 ms
Cjs-Message: 19:19:25.740: JS LOG: [LookingGlass/info] SearchProviderManager started in 0 ms
openGL version 4.5 detected (GL3 Cogl Driver)
MetaSyncRing disabled: couldn't find required GL extensions, or the minimum safe openGL version was not met
Cjs-Message: 19:19:25.780: JS LOG: [LookingGlass/info] Adding indicator: nm-applet
Cjs-Message: 19:19:25.877: JS LOG: [LookingGlass/info] Loaded applet show-desktop@cinnamon.org in 28 ms
Cjs-Message: 19:19:25.884: JS LOG: [LookingGlass/info] Loaded applet removable-drives@cinnamon.org in 8 ms
Cjs-Message: 19:19:25.907: JS LOG: [LookingGlass/info] Loaded applet calendar@cinnamon.org in 22 ms
Cjs-Message: 19:19:25.920: JS LOG: [LookingGlass/info] Loaded applet systray@cinnamon.org in 14 ms
Cjs-Message: 19:19:25.934: JS LOG: [LookingGlass/info] Loaded applet keyboard@cinnamon.org in 14 ms
Cjs-Message: 19:19:26.012: JS LOG: [LookingGlass/info] Role locked: panellauncher
Cjs-Message: 19:19:26.026: JS LOG: [LookingGlass/info] Loaded applet panel-launchers@cinnamon.org in 92 ms
Cjs-Message: 19:19:26.067: JS LOG: [LookingGlass/info] Loaded applet window-list@cinnamon.org in 40 ms
Cjs-Message: 19:19:26.102: JS LOG: [LookingGlass/info] Loaded applet sound@cinnamon.org in 36 ms
Cjs-Message: 19:19:26.531: JS LOG: [LookingGlass/info] Loaded applet menu@cinnamon.org in 428 ms
Cjs-Message: 19:19:26.531: JS LOG: [LookingGlass/info] AppletManager started in 806 ms
Cjs-Message: 19:19:26.533: JS LOG: [LookingGlass/info] Cinnamon took 984 ms to start
Reading profile /etc/firejail/google-chrome-stable.profile
Reading profile /etc/firejail/google-chrome.profile
Reading profile /etc/firejail/disable-common.inc
Reading profile /etc/firejail/disable-devel.inc
Reading profile /etc/firejail/disable-programs.inc
Reading profile /etc/firejail/whitelist-common.inc
Reading profile /etc/firejail/whitelist-var-common.inc
/usr/bin/google-chrome-stable: line 45: /dev/fd/62: No such file or directory
/usr/bin/google-chrome-stable: line 46: /dev/fd/62: No such file or directory
[50:50:1116/192321.571011:ERROR:buffer_manager.cc(491)] [.BrowserCompositor-0x2ee662a95700]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command
Cinnamon warning: Log level 16: STACK_OP_RAISE_ABOVE: sibling window 0x4400001 not in stack
[6:6:1116/212629.695440:ERROR:http_bridge.cc(126)] Not implemented reached in virtual void syncer::HttpBridgeFactory::OnSignalReceived()
Gtk-Message: 21:26:33.660: GtkDialog mapped without a transient parent. This is discouraged.
sys:1: Warning: ../../../../gobject/gsignal.c:2641: instance '0x55588e4e3ee0' has no handler with id '330'
cinnamon-session[6142]: GLib-GIO-CRITICAL: t+7630.68963s: g_dbus_connection_call_sync_internal: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Gdk-Message: 21:26:34.828: csd-power: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.829: csd-automount: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.829: csd-a11y-settings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.832: csd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.832: csd-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.832: mintUpdate.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.832: nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.832: csd-screensaver-proxy: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.832: csd-a11y-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.832: csd-orientation: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.832: csd-xrandr: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.832: csd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.833: csd-background: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.835: cinnamon-killer-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.835: csd-clipboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.835: csd-print-notifications: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.836: csd-sound: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.836: csd-mouse: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.836: csd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.836: csd-cursor: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.843: csd-housekeeping: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.844: csd-color: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.847: cinnamon-screensaver-main.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.855: cinnamon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:26:34.911: cinnamon-launcher: Fatal IO error 2 (No such file or directory) on X server :0.


(metacity:8975): metacity-CRITICAL **: 21:26:35.001: Unable to open X display :0
Unable to init server: Could not connect: Connection refused

(mate-panel:8977): Gtk-WARNING **: 21:26:35.006: cannot open display: :0[/quote]
Last edited by DarrenG on Sat Nov 17, 2018 5:07 am, edited 1 time in total.
“People shouldn't be afraid of their government. Governments should be afraid of their people.”

User avatar
all41
Level 13
Level 13
Posts: 4944
Joined: Tue Dec 31, 2013 9:12 am
Location: Computer, Car, Cage

Re: how to diagnose unexpected shutdowns

Post by all41 » Fri Nov 16, 2018 10:46 pm

Use code </> tags for such long results.

Intermittent shutdown reports are typical for a defective psu.
Only way to know for sure is substitution.

Unplug and reseat all your mb connectors even swapping ends with your drive cables.
Proud to be a supporter and monthly contributor to Mint.

User avatar
trytip
Level 8
Level 8
Posts: 2475
Joined: Tue Jul 05, 2016 1:20 pm

Re: how to diagnose unexpected shutdowns

Post by trytip » Fri Nov 16, 2018 11:24 pm

do you have anything in Terminal for find $HOME ! -user $USER -type f
Last edited by trytip on Sat Nov 17, 2018 12:38 pm, edited 1 time in total.
Image

rbmorse
Level 3
Level 3
Posts: 179
Joined: Mon Mar 07, 2011 11:56 pm
Location: Albuquerque, New Mexico USA

Re: how to diagnose unexpected shutdowns

Post by rbmorse » Fri Nov 16, 2018 11:28 pm

+1 on starting with the power supply. It's the most likely culprit.

There are, however, some other things you can check. Make sure the memory modules and video card/other plug-in peripherals are fully seated in their respective slots.

Pin spacing on memory and expansion cards is very tight. It doesn't take much to cause a contact to make contact with the adjacent pin and cause a short circuit which in turn will cause the PSU to shut down or reset. Thermal expansion may play a role, too.

You have a fairly recent motherboard, so I wouldn't think you would have a problem with degraded capacitors or voltage regulators which degrade with age and can short circuit internally to cause spontaneous reboots. But, just for fun, you might check the components in the vicinity of the CPU for signs of leakage or internal failure. Capitators look like little beer cans and may have a vinyl jacket...the tops should be flat to slightly concave and the sides straight. If the top or sides of one or more capacitors are bulged out the component may be defective. Leakage looks like brown goo or white crystalline "feathers" around the bottom of the component.

Voltage regulators may emit a very sharp, distinctive, pungent odor when they fail, So look for signs of overheated or burned components on the motherboard in the vicinity of the CPU and if you see something that doesn't look right, give it a sniff. You'll know if there's a problem there.
Hope is not a plan

User avatar
DarrenG
Level 1
Level 1
Posts: 46
Joined: Mon Jun 23, 2014 9:12 pm
Location: New Zealand

Re: how to diagnose unexpected shutdowns

Post by DarrenG » Sat Nov 17, 2018 5:17 am

Thanks everyone, I'll pull it apart and reseat everything.

Code: Select all

darren@desktop ~ $ sudo find $HOME ! -user $USER -type f
[sudo] password for darren: 
/home/darren/hl1210wlpr-3.0.1-1.i386.deb
/home/darren/.cache/dconf/user
/home/darren/hl1210wcupswrapper-3.0.1-1.i386.deb
/home/darren/.local/share/Trash/files/hl1210wcupswrapper-3.0.1-1a.i386.deb
/home/darren/.local/share/Trash/files/hl1210wlpr-3.0.1-1a.i386.deb
/home/darren/uninstaller_HL1210W
/home/darren/uninstaller_
“People shouldn't be afraid of their government. Governments should be afraid of their people.”

User avatar
trytip
Level 8
Level 8
Posts: 2475
Joined: Tue Jul 05, 2016 1:20 pm

Re: how to diagnose unexpected shutdowns

Post by trytip » Sat Nov 17, 2018 12:44 pm

DarrenG wrote:
Sat Nov 17, 2018 5:17 am
Thanks everyone, I'll pull it apart and reseat everything.

Code: Select all

darren@desktop ~ $ sudo find $HOME ! -user $USER -type f
[sudo] password for darren: 
/home/darren/hl1210wlpr-3.0.1-1.i386.deb
/home/darren/.cache/dconf/user
/home/darren/hl1210wcupswrapper-3.0.1-1.i386.deb
/home/darren/.local/share/Trash/files/hl1210wcupswrapper-3.0.1-1a.i386.deb
/home/darren/.local/share/Trash/files/hl1210wlpr-3.0.1-1a.i386.deb
/home/darren/uninstaller_HL1210W
/home/darren/uninstaller_
the files listed here have root permissions . you can delete them with a file manager as root. start with /home/darren/.cache/dconf/user in fact open up .cache folder with your root file manager and delete everything in .cache
and it looks like you tried to build something and things were leftover. can't say why these packages have different permissions do you know why?
Image

Post Reply

Return to “Newbie Questions”