Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

SOLVED Buster XFCE: How to find the cause of random crashes?

If none of the specific sub-forums seem right for your thread, ask here.
Message
Author
User avatar
efrpcabo
Posts: 108
Joined: 2013-08-08 06:36

SOLVED Buster XFCE: How to find the cause of random crashes?

#1 Post by efrpcabo »

Hi,

How can I find the cause of random crashes?

I don't really know if this technically is called a crash.

What I am experiencing is this:
- I am working normally at the computer
- and suddenly all windows close
- and the login screen appears (when we introduce the username and password)
- there is no freeze whatsoever
- this happens when I am using apps like Firefox, Thunar, Virtualbox, etc
- but the only app that I was always using in every ocasion was Thunar
- however, I don't know if Thunar is the cause because I am using it almost all the time
- so it could happen without it being the cause also

Before I was on Debian 8 Jessie XFCE and this never happened.

Now, I'm on Debian 10 Buster XFCE for a couple of weeks.
And since then I have experienced multiple crashes.
Here are just a few from the last days.

20190827-110234
20190827-143625
20190827-194612
20190827-195104
20190827-203955
20190827-204106
20190827-215204
20190827-231419
20190827-235152

20190828-001438
20190828-001805
20190828-001852
20190828-003114
20190828-010440
20190828-020430

How can I investigate this?

I have googled and found out that there are many cases of crashes, in a multitude of distros: Debian, Fedora, Arch, etc.

But almost every case reports "freezes", i.e, the system freezing, and in my case that doesn't happen; never did, not even once.

What happens is I am just logged out of my session and the login screen appears (when we introduce the username and password), like I said above.

From my google searches, I've seen people advising to analyse this files:
/home/user/.xsession-errors.old
/var/log/lightdm/"various logs"

and analyse the result of this commands:
# inxi -Fz
# journalctl

=============================================
# inxi -Fz
System: Host: princ-20190810 Kernel: 4.19.0-5-amd64 x86_64 bits: 64 Desktop: Xfce 4.14.1
Distro: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop System: LENOVO product: 10AHS0LH00 v: ThinkCentre M83 serial: <filter>
Mobo: LENOVO model: SHARKBAY v: NOK serial: N/A BIOS: LENOVO v: FBKTA6AUS date: 01/28/2015
CPU: Topology: Quad Core model: Intel Core i5-4670S bits: 64 type: MCP L2 cache: 6144 KiB
Speed: 2954 MHz min/max: 800/3800 MHz Core speeds (MHz): 1: 2149 2: 2856 3: 2749 4: 2236
Graphics: Device-1: NVIDIA GT218 [GeForce 210] driver: nouveau v: kernel
Display: server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa resolution: 1600x1200~60Hz
OpenGL: renderer: NVA8 v: 3.3 Mesa 18.3.6
Audio: Device-1: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel
Device-2: NVIDIA High Definition Audio driver: snd_hda_intel
Sound Server: ALSA v: k4.19.0-5-amd64
Network: Device-1: Intel Ethernet I217-LM driver: e1000e
IF: eno1 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 5.91 TiB used: 4.76 TiB (80.6%)
ID-1: /dev/sda vendor: Toshiba model: HDWD130 size: 2.73 TiB
ID-2: /dev/sdb vendor: Samsung model: HD154UI size: 1.36 TiB
ID-3: /dev/sdc vendor: Seagate model: ST31500341AS size: 1.36 TiB
ID-4: /dev/sdd vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB
Partition: ID-1: / size: 20.03 GiB used: 8.64 GiB (43.1%) fs: ext4 dev: /dev/dm-0
ID-2: /boot size: 922.0 MiB used: 63.9 MiB (6.9%) fs: ext4 dev: /dev/sdd1
ID-3: swap-1 size: 4.64 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-1
Sensors: System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nouveau temp: 51 C
Fan Speeds (RPM): N/A
Info: Processes: 220 Uptime: 3h 45m Memory: 7.71 GiB used: 1.26 GiB (16.4%) Shell: bash inxi: 3.0.32

=============================================
=============================================
=============================================
Here ao some of the contents of some .xsession-errors.old:

=============================================

Gdk-Message: 11:32:01.627: mousepad: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

Gdk-Message: 11:32:01.627: thunar: Fatal IO error 104 (Connection reset by peer) on X server :0.0.

Gdk-Message: 11:32:01.627: /usr/lib/firefox-esr/firefox-esr: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

gigolo: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
Gdk-Message: 11:32:01.628: wrapper-2.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

Gdk-Message: 11:32:01.628: nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

Gdk-Message: 11:32:01.628: xfce4-terminal: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

wrapper-1.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
Gdk-Message: 11:32:01.629: wrapper-2.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

Gdk-Message: 11:32:01.629: polkit-gnome-authentication-agent-1: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

Gdk-Message: 11:32:01.629: synaptic: Fatal IO error 2 (No such file or directory) on X server :0.0.

xfsettingsd: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
Gdk-Message: 11:32:01.629: firefox-esr: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

Gdk-Message: 11:32:01.629: light-locker: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

=============================================
(VirtualBox:27937): Gtk-WARNING **: 19:09:29.432: Theme parsing error: gtk.css:6:32: Invalid character in string. Must be escaped.
Qt WARNING: QXcbConnection: XCB error: 3 (BadWindow), sequence: 24860, resource id: 11858764, major code: 40 (TranslateCoords), minor code: 0
Qt WARNING: QXcbConnection: XCB error: 3 (BadWindow), sequence: 44356, resource id: 11868674, major code: 40 (TranslateCoords), minor code: 0
Qt WARNING: QXcbConnection: XCB error: 3 (BadWindow), sequence: 63936, resource id: 11906422, major code: 40 (TranslateCoords), minor code: 0
Qt WARNING: QXcbConnection: XCB error: 3 (BadWindow), sequence: 60636, resource id: 11962297, major code: 40 (TranslateCoords), minor code: 0
Gdk-Message: 19:23:45.047: VirtualBox: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

gigolo: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
wrapper-1.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
wrapper-1.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
Gdk-Message: 19:23:45.071: Thunar: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

Gdk-Message: 19:23:45.071: wrapper-2.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

Gdk-Message: 19:23:45.072: polkit-gnome-authentication-agent-1: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

xfwm4: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
Gdk-Message: 19:23:45.076: light-locker: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

xfce4-panel: Fatal IO error 4 (Interrupted system call) on X server :0.0.
xfsettingsd: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
xfdesktop: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
Gdk-Message: 19:23:45.082: nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

xfce4-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

=============================================
Gdk-Message: 19:27:26.804: VirtualBox: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

Gdk-Message: 19:27:26.804: nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

wrapper-1.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
Gdk-Message: 19:27:26.805: wrapper-2.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

wrapper-1.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
xfce4-panel: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
xfdesktop: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
Gdk-Message: 19:27:26.805: polkit-gnome-authentication-agent-1: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

xfce4-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
xfwm4: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
xfsettingsd: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
Gdk-Message: 19:27:26.812: light-locker: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

Gdk-Message: 19:27:26.814: Thunar: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

=============================================
(VirtualBox:6567): Gtk-WARNING **: 12:26:55.736: Theme parsing error: gtk.css:6:32: Invalid character in string. Must be escaped.
Qt WARNING: QXcbConnection: XCB error: 3 (BadWindow), sequence: 24637, resource id: 12127279, major code: 40 (TranslateCoords), minor code: 0
gigolo: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
Gdk-Message: 12:31:19.850: /usr/lib/firefox-esr/firefox-esr: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

Gdk-Message: 12:31:19.850: /usr/lib/firefox-esr/firefox-esr: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.


###!!! [Parent][MessageChannel] Error: (msgtype=0x160080,name=PBrowser::Msg_Destroy) Channel error: cannot send/recv

Gdk-Message: 12:31:19.866: VirtualBox: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

Gdk-Message: 12:31:19.866: /usr/lib/firefox-esr/firefox-esr: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

wrapper-1.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
Gdk-Message: 12:31:19.866: polkit-gnome-authentication-agent-1: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

Gdk-Message: 12:31:19.867: light-locker: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

xfce4-panel: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
wrapper-1.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
Gdk-Message: 12:31:19.866: /usr/lib/firefox-esr/firefox-esr: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

Gdk-Message: 12:31:19.870: wrapper-2.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

xfdesktop: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
xfwm4: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
xfsettingsd: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
Gdk-Message: 12:31:19.877: nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

xfce4-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Gdk-Message: 12:31:19.885: Thunar: Fatal IO error 0 (Success) on X server :0.0.


###!!! [Parent][MessageChannel] Error: (msgtype=0x160080,name=PBrowser::Msg_Destroy) Channel error: cannot send/recv


###!!! [Parent][MessageChannel] Error: (msgtype=0x160080,name=PBrowser::Msg_Destroy) Channel error: cannot send/recv

Gdk-Message: 12:31:19.942: firefox-esr: Fatal IO error 104 (Connection reset by peer) on X server :0.0.

=============================================
UUID changed to: 12345678-1234-1234-1234-190823124640
wrapper-1.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
Gdk-Message: 12:48:56.504: polkit-gnome-authentication-agent-1: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

wrapper-1.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
xfce4-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Gdk-Message: 12:48:56.506: wrapper-2.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

xfwm4: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
Gdk-Message: 12:48:56.508: Thunar: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

Gdk-Message: 12:48:56.508: light-locker: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

xfsettingsd: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
xfdesktop: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
xfce4-panel: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
Gdk-Message: 12:48:56.512: nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

=============================================

How can I investigate this?
Am I looking at the right files?
Has someone else having the same issue?
Last edited by efrpcabo on 2019-09-02 00:11, edited 1 time in total.

Segfault
Posts: 993
Joined: 2005-09-24 12:24
Has thanked: 5 times
Been thanked: 17 times

Re: Buste XFCE: How can I find the cause of random crashes?

#2 Post by Segfault »

Every time I see IO errors I start with checking the health of hard drive.

User avatar
efrpcabo
Posts: 108
Joined: 2013-08-08 06:36

Re: Buste XFCE: How can I find the cause of random crashes?

#3 Post by efrpcabo »

Segfault wrote:Every time I see IO errors I start with checking the health of hard drive.
Ok, that's a good idea.
I can move my system to another disk for some days and see if the crashes stop.

Other ideas are also welcome.

User avatar
efrpcabo
Posts: 108
Joined: 2013-08-08 06:36

Re: Buste XFCE: How can I find the cause of random crashes?

#4 Post by efrpcabo »

I just had another crash some minutes ago.
I was gathering all the information I could about this last one.

The crash occurred before 21:01:05.

There are 3 IO errors at 21:00:48, but they don't seem the cause; or do they?

# journalctl -r
-- Logs begin at Wed 2019-08-28 16:47:08 WEST, end at Wed 2019-08-28 21:03:54 WEST. --
Aug 28 21:03:54 princ-20190810 pkexec[5750]: user1: Executing command [USER=root] [TTY=unknown] [CWD=/home/user1] [COMMAND=/usr/bin/env DISPLAY=:0.0 XAUTHOR
Aug 28 21:03:54 princ-20190810 pkexec[5750]: pam_unix(polkit-1:session): session opened for user root by (uid=1000)
Aug 28 21:03:54 princ-20190810 polkitd(authority=local)[913]: Operator of unix-session:38 successfully authenticated as unix-user:root to gain ONE-SHOT auth
Aug 28 21:02:45 princ-20190810 dbus-daemon[5463]: [session uid=0 pid=5461] Successfully activated service 'org.freedesktop.thumbnails.Thumbnailer1'
Aug 28 21:02:45 princ-20190810 dbus-daemon[5463]: [session uid=0 pid=5461] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
Aug 28 21:02:45 princ-20190810 dbus-daemon[5463]: [session uid=0 pid=5461] Activating service name='org.gtk.vfs.MTPVolumeMonitor' requested by ':1.7' (uid=0
Aug 28 21:02:45 princ-20190810 dbus-daemon[5463]: [session uid=0 pid=5461] Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor'
Aug 28 21:02:45 princ-20190810 org.gtk.vfs.AfcVolumeMonitor[5463]: Volume monitor alive
Aug 28 21:02:45 princ-20190810 dbus-daemon[5463]: [session uid=0 pid=5461] Activating service name='org.gtk.vfs.AfcVolumeMonitor' requested by ':1.7' (uid=0
Aug 28 21:02:45 princ-20190810 dbus-daemon[5463]: [session uid=0 pid=5461] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
Aug 28 21:02:45 princ-20190810 dbus-daemon[5463]: [session uid=0 pid=5461] Activating service name='org.gtk.vfs.GPhoto2VolumeMonitor' requested by ':1.7' (u
Aug 28 21:02:45 princ-20190810 dbus-daemon[5463]: [session uid=0 pid=5461] Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'
Aug 28 21:02:45 princ-20190810 dbus-daemon[5463]: [session uid=0 pid=5461] Activating service name='org.gtk.vfs.GoaVolumeMonitor' requested by ':1.7' (uid=0
Aug 28 21:02:45 princ-20190810 dbus-daemon[5463]: [session uid=0 pid=5461] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
Aug 28 21:02:45 princ-20190810 dbus-daemon[5463]: [session uid=0 pid=5461] Activating service name='org.gtk.vfs.UDisks2VolumeMonitor' requested by ':1.7' (u
Aug 28 21:02:45 princ-20190810 org.freedesktop.thumbnails.Thumbnailer1[5463]: Registered thumbnailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o
Aug 28 21:02:45 princ-20190810 org.freedesktop.thumbnails.Thumbnailer1[5463]: Registered thumbnailer atril-thumbnailer -s %s %u %o
Aug 28 21:02:45 princ-20190810 org.freedesktop.thumbnails.Thumbnailer1[5463]: Registered thumbnailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o
Aug 28 21:02:45 princ-20190810 dbus-daemon[5463]: [session uid=0 pid=5461] Successfully activated service 'org.gtk.vfs.Daemon'
Aug 28 21:02:45 princ-20190810 dbus-daemon[5463]: [session uid=0 pid=5461] Activating service name='org.gtk.vfs.Daemon' requested by ':1.7' (uid=0 pid=5640
Aug 28 21:02:45 princ-20190810 dbus-daemon[5463]: [session uid=0 pid=5461] Activating service name='org.freedesktop.thumbnails.Thumbnailer1' requested by ':
Aug 28 21:02:45 princ-20190810 dbus-daemon[5463]: [session uid=0 pid=5461] Successfully activated service 'org.xfce.Xfconf'
Aug 28 21:02:45 princ-20190810 dbus-daemon[5463]: [session uid=0 pid=5461] Activating service name='org.xfce.Xfconf' requested by ':1.5' (uid=0 pid=5615 com
Aug 28 21:02:45 princ-20190810 pkexec[5615]: user1: Executing command [USER=root] [TTY=unknown] [CWD=/home/user1] [COMMAND=/usr/bin/env DISPLAY=:0.0 XAUTHOR
Aug 28 21:02:45 princ-20190810 pkexec[5615]: pam_unix(polkit-1:session): session opened for user root by (uid=1000)
Aug 28 21:02:45 princ-20190810 polkitd(authority=local)[913]: Operator of unix-session:38 successfully authenticated as unix-user:root to gain ONE-SHOT auth
Aug 28 21:01:05 princ-20190810 systemd[1]: Removed slice User Slice of UID 115.
Aug 28 21:01:05 princ-20190810 systemd[1]: Stopped User Runtime Directory /run/user/115.
Aug 28 21:01:05 princ-20190810 systemd[1]: user-runtime-dir@115.service: Succeeded.
Aug 28 21:01:05 princ-20190810 systemd[1]: run-user-115.mount: Succeeded.
Aug 28 21:01:05 princ-20190810 systemd[1323]: run-user-115.mount: Succeeded.
Aug 28 21:01:05 princ-20190810 systemd[1]: Stopping User Runtime Directory /run/user/115...
Aug 28 21:01:05 princ-20190810 systemd[1]: Stopped User Manager for UID 115.
Aug 28 21:01:05 princ-20190810 systemd[1]: user@115.service: Succeeded.
Aug 28 21:01:05 princ-20190810 systemd[5263]: Reached target Exit the Session.
Aug 28 21:01:05 princ-20190810 systemd[5263]: Started Exit the Session.
Aug 28 21:01:05 princ-20190810 systemd[5263]: systemd-exit.service: Succeeded.
Aug 28 21:01:05 princ-20190810 systemd[5263]: Reached target Shutdown.
Aug 28 21:01:05 princ-20190810 systemd[5263]: Closed D-Bus User Message Bus Socket.
Aug 28 21:01:05 princ-20190810 systemd[5263]: dbus.socket: Succeeded.
Aug 28 21:01:05 princ-20190810 systemd[5263]: Stopped target Paths.
Aug 28 21:01:05 princ-20190810 systemd[5263]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Aug 28 21:01:05 princ-20190810 systemd[5263]: gpg-agent-extra.socket: Succeeded.
Aug 28 21:01:05 princ-20190810 systemd[5263]: Closed GnuPG cryptographic agent and passphrase cache.
Aug 28 21:01:05 princ-20190810 systemd[5263]: gpg-agent.socket: Succeeded.
Aug 28 21:01:05 princ-20190810 systemd[5263]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Aug 28 21:01:05 princ-20190810 systemd[5263]: gpg-agent-ssh.socket: Succeeded.
Aug 28 21:01:05 princ-20190810 systemd[5263]: Closed Sound System.
Aug 28 21:01:05 princ-20190810 systemd[5263]: pulseaudio.socket: Succeeded.
Aug 28 21:01:05 princ-20190810 systemd[5263]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Aug 28 21:01:05 princ-20190810 systemd[5263]: gpg-agent-browser.socket: Succeeded.
Aug 28 21:01:05 princ-20190810 systemd[5263]: Closed GnuPG network certificate management daemon.
Aug 28 21:01:05 princ-20190810 systemd[5263]: dirmngr.socket: Succeeded.
Aug 28 21:01:05 princ-20190810 systemd[5263]: Stopped target Sockets.
Aug 28 21:01:05 princ-20190810 systemd[5263]: Stopped target Timers.
Aug 28 21:01:05 princ-20190810 systemd[5263]: Stopped target Basic System.
Aug 28 21:01:05 princ-20190810 systemd[5263]: Stopped Virtual filesystem service.
Aug 28 21:01:05 princ-20190810 systemd[5263]: gvfs-daemon.service: Succeeded.
Aug 28 21:01:05 princ-20190810 systemd[1323]: run-user-115-gvfs.mount: Succeeded.
Aug 28 21:01:05 princ-20190810 systemd[5263]: run-user-115-gvfs.mount: Succeeded.
Aug 28 21:01:05 princ-20190810 systemd[1]: run-user-115-gvfs.mount: Succeeded.
Aug 28 21:01:05 princ-20190810 systemd[5263]: Stopped Accessibility services bus.
Aug 28 21:01:05 princ-20190810 systemd[5263]: at-spi-dbus-bus.service: Succeeded.
Aug 28 21:01:05 princ-20190810 systemd[5263]: Stopped D-Bus User Message Bus.
Aug 28 21:01:05 princ-20190810 systemd[5263]: dbus.service: Succeeded.
Aug 28 21:01:05 princ-20190810 systemd[5263]: gvfs-daemon.service: Main process exited, code=killed, status=15/TERM
Aug 28 21:01:05 princ-20190810 systemd[5263]: Stopping Virtual filesystem service...
Aug 28 21:01:05 princ-20190810 systemd[5263]: Stopping Accessibility services bus...
Aug 28 21:01:05 princ-20190810 systemd[5263]: Stopped target Default.
Aug 28 21:01:05 princ-20190810 systemd[5263]: Stopping D-Bus User Message Bus...
Aug 28 21:01:05 princ-20190810 systemd[1]: Stopping User Manager for UID 115...
Aug 28 21:01:05 princ-20190810 org.a11y.Bus[5463]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Aug 28 21:01:05 princ-20190810 org.a11y.Bus[5463]: dbus-daemon[5472]: Successfully activated service 'org.a11y.atspi.Registry'
Aug 28 21:01:05 princ-20190810 org.a11y.Bus[5463]: dbus-daemon[5472]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=0 pid=5452
Aug 28 21:01:05 princ-20190810 dbus-daemon[5463]: [session uid=0 pid=5461] Successfully activated service 'org.a11y.Bus'
Aug 28 21:01:05 princ-20190810 dbus-daemon[5463]: [session uid=0 pid=5461] Activating service name='org.a11y.Bus' requested by ':1.1' (uid=0 pid=5452 comm="
Aug 28 21:01:05 princ-20190810 pkexec[5452]: user1: Executing command [USER=root] [TTY=unknown] [CWD=/home/user1] [COMMAND=/usr/bin/env DISPLAY=:0.0 XAUTHOR
Aug 28 21:01:05 princ-20190810 pkexec[5452]: pam_unix(polkit-1:session): session opened for user root by (uid=1000)
Aug 28 21:01:05 princ-20190810 polkitd(authority=local)[913]: Operator of unix-session:38 successfully authenticated as unix-user:root to gain ONE-SHOT auth
Aug 28 21:00:59 princ-20190810 pkexec[5444]: user1: Error executing command as another user: Request dismissed [USER=root] [TTY=unknown] [CWD=/home/user1] [
Aug 28 21:00:59 princ-20190810 polkitd(authority=local)[913]: Operator of unix-session:38 FAILED to authenticate to gain authorization for action org.freede
Aug 28 21:00:57 princ-20190810 NetworkManager[892]: <info> [1567022457.2824] agent-manager: req[0x560ca0caf200, :1.397/org.freedesktop.nm-applet/1000]: age
Aug 28 21:00:57 princ-20190810 systemd[1323]: Started XFCE notifications service.
Aug 28 21:00:57 princ-20190810 dbus-daemon[1342]: [session uid=1000 pid=1342] Successfully activated service 'org.freedesktop.Notifications'
Aug 28 21:00:57 princ-20190810 polkitd(authority=local)[913]: Registered Authentication Agent for unix-session:38 (system bus name :1.384 [/usr/lib/policyki
Aug 28 21:00:57 princ-20190810 systemd[1323]: Starting XFCE notifications service...
Aug 28 21:00:57 princ-20190810 dbus-daemon[1342]: [session uid=1000 pid=1342] Activating via systemd: service name='org.freedesktop.Notifications' unit='xfc
Aug 28 21:00:55 princ-20190810 at-spi-bus-launcher[1376]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Aug 28 21:00:55 princ-20190810 at-spi-bus-launcher[1376]: dbus-daemon[1381]: Successfully activated service 'org.a11y.atspi.Registry'
Aug 28 21:00:55 princ-20190810 at-spi-bus-launcher[1376]: dbus-daemon[1381]: Activating service name='org.a11y.atspi.Registry' requested by ':1.73' (uid=100
Aug 28 21:00:55 princ-20190810 systemd-logind[879]: New session 38 of user user1.
Aug 28 21:00:55 princ-20190810 systemd[1]: Started Session 38 of user user1.
Aug 28 21:00:55 princ-20190810 lightdm[5314]: pam_unix(lightdm:session): session opened for user user1 by (uid=0)
Aug 28 21:00:55 princ-20190810 systemd-logind[879]: Removed session c2.
Aug 28 21:00:55 princ-20190810 systemd[1]: Stopped Session c2 of user lightdm.
Aug 28 21:00:55 princ-20190810 systemd[1]: session-c2.scope: Succeeded.
Aug 28 21:00:55 princ-20190810 lightdm[5259]: pam_unix(lightdm-greeter:session): session closed for user lightdm
Aug 28 21:00:55 princ-20190810 systemd[1]: Stopping Session c2 of user lightdm.
Aug 28 21:00:55 princ-20190810 systemd[1]: session-c2.scope: Killing process 5274 (lightdm-gtk-gre) with signal SIGTERM.
Aug 28 21:00:55 princ-20190810 systemd[1]: session-c2.scope: Killing process 5259 (lightdm) with signal SIGTERM.
Aug 28 21:00:55 princ-20190810 lightdm[5314]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown:
Aug 28 21:00:51 princ-20190810 systemd[1323]: Started Sound Service.
Aug 28 21:00:49 princ-20190810 systemd[5263]: Started Virtual filesystem service.
Aug 28 21:00:49 princ-20190810 dbus-daemon[5277]: [session uid=115 pid=5277] Successfully activated service 'org.gtk.vfs.Daemon'
Aug 28 21:00:49 princ-20190810 at-spi-bus-launcher[5278]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Aug 28 21:00:49 princ-20190810 at-spi-bus-launcher[5278]: dbus-daemon[5283]: Successfully activated service 'org.a11y.atspi.Registry'
Aug 28 21:00:49 princ-20190810 systemd[5263]: Starting Virtual filesystem service...
Aug 28 21:00:49 princ-20190810 dbus-daemon[5277]: [session uid=115 pid=5277] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.ser
Aug 28 21:00:49 princ-20190810 at-spi-bus-launcher[5278]: dbus-daemon[5283]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=115
Aug 28 21:00:49 princ-20190810 systemd[5263]: Started Accessibility services bus.
Aug 28 21:00:49 princ-20190810 dbus-daemon[5277]: [session uid=115 pid=5277] Successfully activated service 'org.a11y.Bus'
Aug 28 21:00:49 princ-20190810 systemd[5263]: Starting Accessibility services bus...
Aug 28 21:00:49 princ-20190810 dbus-daemon[5277]: [session uid=115 pid=5277] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.servi
Aug 28 21:00:49 princ-20190810 systemd[5263]: Started D-Bus User Message Bus.
Aug 28 21:00:49 princ-20190810 systemd[1]: Started Session c2 of user lightdm.
Aug 28 21:00:49 princ-20190810 systemd[1]: Started User Manager for UID 115.
Aug 28 21:00:49 princ-20190810 systemd[5263]: Startup finished in 46ms.
Aug 28 21:00:49 princ-20190810 systemd[5263]: Reached target Default.
Aug 28 21:00:49 princ-20190810 systemd[5263]: Reached target Basic System.
Aug 28 21:00:49 princ-20190810 systemd[5263]: Reached target Sockets.
Aug 28 21:00:49 princ-20190810 systemd[5263]: Listening on D-Bus User Message Bus Socket.
Aug 28 21:00:49 princ-20190810 systemd[5263]: Listening on GnuPG network certificate management daemon.
Aug 28 21:00:49 princ-20190810 systemd[5263]: Reached target Timers.
Aug 28 21:00:49 princ-20190810 systemd[5263]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Aug 28 21:00:49 princ-20190810 systemd[5263]: Listening on Sound System.
Aug 28 21:00:49 princ-20190810 systemd[5263]: Listening on GnuPG cryptographic agent and passphrase cache.
Aug 28 21:00:49 princ-20190810 systemd[5263]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Aug 28 21:00:49 princ-20190810 systemd[5263]: Starting D-Bus User Message Bus Socket.
Aug 28 21:00:49 princ-20190810 systemd[5263]: Reached target Paths.
Aug 28 21:00:49 princ-20190810 systemd[5263]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Aug 28 21:00:49 princ-20190810 systemd[5263]: pam_unix(systemd-user:session): session opened for user lightdm by (uid=0)
Aug 28 21:00:49 princ-20190810 systemd[1]: Starting User Manager for UID 115...
Aug 28 21:00:49 princ-20190810 systemd[1]: Started User Runtime Directory /run/user/115.
Aug 28 21:00:49 princ-20190810 systemd-logind[879]: New session c2 of user lightdm.
Aug 28 21:00:49 princ-20190810 systemd[1]: Starting User Runtime Directory /run/user/115...
Aug 28 21:00:49 princ-20190810 systemd[1]: Created slice User Slice of UID 115.
Aug 28 21:00:49 princ-20190810 lightdm[5259]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Aug 28 21:00:49 princ-20190810 lightdm[5259]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown:
Aug 28 21:00:49 princ-20190810 rtkit-daemon[1493]: Supervising 3 threads of 1 processes of 1 users.
Aug 28 21:00:49 princ-20190810 rtkit-daemon[1493]: Successfully made thread 5252 of process 5248 (n/a) owned by '1000' RT at priority 5.
Aug 28 21:00:49 princ-20190810 rtkit-daemon[1493]: Supervising 2 threads of 1 processes of 1 users.
Aug 28 21:00:49 princ-20190810 rtkit-daemon[1493]: Supervising 2 threads of 1 processes of 1 users.
Aug 28 21:00:49 princ-20190810 rtkit-daemon[1493]: Successfully made thread 5251 of process 5248 (n/a) owned by '1000' RT at priority 5.
Aug 28 21:00:49 princ-20190810 rtkit-daemon[1493]: Supervising 1 threads of 1 processes of 1 users.
Aug 28 21:00:48 princ-20190810 pulseaudio[5248]: W: [pulseaudio] pid.c: Stale PID file, overwriting.
Aug 28 21:00:48 princ-20190810 rtkit-daemon[1493]: Supervising 1 threads of 1 processes of 1 users.
Aug 28 21:00:48 princ-20190810 rtkit-daemon[1493]: Successfully made thread 5248 of process 5248 (n/a) owned by '1000' high priority at nice level -11.
Aug 28 21:00:48 princ-20190810 systemd[1323]: Starting Sound Service...
Aug 28 21:00:48 princ-20190810 systemd[1323]: Stopped Sound Service.
Aug 28 21:00:48 princ-20190810 systemd[1323]: pulseaudio.service: Scheduled restart job, restart counter is at 1.
Aug 28 21:00:48 princ-20190810 systemd[1323]: pulseaudio.service: Service RestartSec=100ms expired, scheduling restart.
Aug 28 21:00:48 princ-20190810 systemd-logind[879]: Session 1 logged out. Waiting for processes to exit.
Aug 28 21:00:48 princ-20190810 lightdm[1318]: pam_unix(lightdm-autologin:session): session closed for user user1
Aug 28 21:00:48 princ-20190810 systemd[1323]: pulseaudio.service: Failed with result 'exit-code'.
Aug 28 21:00:48 princ-20190810 systemd[1323]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE
Aug 28 21:00:48 princ-20190810 polkitd(authority=local)[913]: Unregistered Authentication Agent for unix-session:1 (system bus name :1.50, object path /org/
Aug 28 21:00:48 princ-20190810 tumblerd[5098]: Name org.freedesktop.thumbnails.Thumbnailer1 lost on the message dbus, exiting.
Aug 28 21:00:48 princ-20190810 tumblerd[5098]: Name org.freedesktop.thumbnails.Manager1 lost on the message dbus, exiting.
Aug 28 21:00:48 princ-20190810 tumblerd[5098]: Name org.freedesktop.thumbnails.Cache1 lost on the message dbus, exiting.
Aug 28 21:00:48 princ-20190810 tumblerd[5098]: Owner of volume monitor org.gtk.vfs.MTPVolumeMonitor disconnected from the bus; removing drives/volumes/mount
Aug 28 21:00:48 princ-20190810 tumblerd[5098]: Owner of volume monitor org.gtk.vfs.AfcVolumeMonitor disconnected from the bus; removing drives/volumes/mount
Aug 28 21:00:48 princ-20190810 tumblerd[5098]: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/m
Aug 28 21:00:48 princ-20190810 tumblerd[5098]: Owner of volume monitor org.gtk.vfs.GoaVolumeMonitor disconnected from the bus; removing drives/volumes/mount
Aug 28 21:00:48 princ-20190810 tumblerd[5098]: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/m
Aug 28 21:00:48 princ-20190810 systemd[1323]: xfce4-notifyd.service: Failed with result 'exit-code'.
Aug 28 21:00:48 princ-20190810 systemd[1323]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE
Aug 28 21:00:48 princ-20190810 unknown[1489]: xfce4-notifyd: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Aug 28 21:00:48 princ-20190810 systemd[1]: root-.gvfs.mount: Succeeded.
Aug 28 21:00:48 princ-20190810 at-spi-bus-launcher[1376]: after 10529 requests (10529 known processed) with 0 events remaining.
Aug 28 21:00:48 princ-20190810 at-spi-bus-launcher[1376]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Aug 28 21:00:48 princ-20190810 org.gtk.vfs.Daemon[1979]: A connection to the bus can't be made
Aug 28 21:00:48 princ-20190810 pulseaudio[1488]: after 17 requests (17 known processed) with 0 events remaining.
Aug 28 21:00:48 princ-20190810 pulseaudio[1488]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
Aug 28 21:00:48 princ-20190810 systemd[1323]: root-.gvfs.mount: Succeeded.
Aug 28 21:00:48 princ-20190810 xfconfd[1982]: Name org.xfce.Xfconf lost on the message dbus, exiting.
Aug 28 20:57:13 princ-20190810 dbus-daemon[1979]: [session uid=0 pid=1977] Successfully activated service 'org.freedesktop.thumbnails.Thumbnailer1'
Aug 28 20:57:13 princ-20190810 org.freedesktop.thumbnails.Thumbnailer1[1979]: Registered thumbnailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o
Aug 28 20:57:13

===========================
xsession-errors.old:

(mousepad:5154): Gtk-WARNING **: 20:58:10.639: Theme parsing error: gtk.css:14:0: Expected semicolon

(mousepad:5154): Gtk-WARNING **: 20:58:10.639: Theme parsing error: gtk.css:27:0: Expected semicolon

(mousepad:5154): Gtk-WARNING **: 20:58:10.639: Theme parsing error: gtk.css:29:0: Expected semicolon
ThunarThumbnailCache: failed to call Copy(): Timeout was reached
ThunarThumbnailCache: failed to call Move(): Timeout was reached

(xfce4-appearance-settings:5218): Gtk-WARNING **: 20:59:52.611: Theme parsing error: gtk.css:11:1: '/*' in comment block

(xfce4-appearance-settings:5218): Gtk-WARNING **: 20:59:52.611: Theme parsing error: gtk.css:14:0: Expected semicolon

(xfce4-appearance-settings:5218): Gtk-WARNING **: 20:59:52.612: Theme parsing error: gtk.css:27:0: Expected semicolon

(xfce4-appearance-settings:5218): Gtk-WARNING **: 20:59:52.612: Theme parsing error: gtk.css:29:0: Expected semicolon

(xfce4-appearance-settings:5225): Gtk-WARNING **: 21:00:10.978: Theme parsing error: gtk.css:11:1: '/*' in comment block

(xfce4-appearance-settings:5225): Gtk-WARNING **: 21:00:10.978: Theme parsing error: gtk.css:14:0: Expected semicolon

(xfce4-appearance-settings:5225): Gtk-WARNING **: 21:00:10.979: Theme parsing error: gtk.css:27:0: Expected semicolon

(xfce4-appearance-settings:5225): Gtk-WARNING **: 21:00:10.979: Theme parsing error: gtk.css:29:0: Expected semicolon
ThunarThumbnailCache: failed to call Move(): Timeout was reached
ThunarThumbnailCache: failed to call Move(): Timeout was reached
cp: -r not specified; omitting directory '/home/user1/.PA_links/link to .themes/PA_Windows_XP_Embedded_gtk-3.0'
Gdk-Message: 21:00:48.798: /usr/lib/firefox-esr/firefox-esr: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

Gdk-Message: 21:00:48.799: polkit-gnome-authentication-agent-1: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

Gdk-Message: 21:00:48.799: wrapper-2.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:00:48.799: wrapper-2.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:00:48.799: xfce4-panel: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:00:48.799: xfsettingsd: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:00:48.799: Thunar: Fatal IO error 104 (Connection reset by peer) on X server :0.

Gdk-Message: 21:00:48.800: firefox-esr: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

Gdk-Message: 21:00:48.802: xfce4-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:00:48.803: xfwm4: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:00:48.799: /usr/lib/firefox-esr/firefox-esr: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

Gdk-Message: 21:00:48.798: /usr/lib/firefox-esr/firefox-esr: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

Gdk-Message: 21:00:48.798: /usr/lib/firefox-esr/firefox-esr: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

Gdk-Message: 21:00:48.805: wrapper-2.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 21:00:48.806: light-locker: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

Gdk-Message: 21:00:48.807: nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

Gdk-Message: 21:00:48.818: xfdesktop: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Last edited by efrpcabo on 2019-08-28 19:33, edited 1 time in total.

Segfault
Posts: 993
Joined: 2005-09-24 12:24
Has thanked: 5 times
Been thanked: 17 times

Re: Buste XFCE: How can I find the cause of random crashes?

#5 Post by Segfault »

You can run lots of tests on your hard drive without removing or replacing it. Also I suggest you learn how mcelog can serve you.

User avatar
efrpcabo
Posts: 108
Joined: 2013-08-08 06:36

Re: Buste XFCE: How can I find the cause of random crashes?

#6 Post by efrpcabo »

Segfault wrote:You can run lots of tests on your hard drive without removing or replacing it. Also I suggest you learn how mcelog can serve you.
Thank you!
I will learn about mcelog.

User avatar
efrpcabo
Posts: 108
Joined: 2013-08-08 06:36

Re: Buste XFCE: How can I find the cause of random crashes?

#7 Post by efrpcabo »

It appeards "mcelog" was replaced in Debian Buster by "rasdaemon".

Also, when I try to install "mcelog" in Synaptic, it doesn't appear.
But instead it appears "collectd-core".

What should I do now?

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 72 times

Re: Buste XFCE: How can I find the cause of random crashes?

#8 Post by stevepusser »

If you have no overriding objections to proprietary software, you could test the Nvidia graphics driver from the non-free section to see if that makes any difference. Follow the directions in the Debian wiki, though I prefer using module-assistant to set up the build environment:

Code: Select all

# apt install module-assistant
# m-a prepare
MX Linux packager and developer

User avatar
efrpcabo
Posts: 108
Joined: 2013-08-08 06:36

Re: Buste XFCE: How can I find the cause of random crashes?

#9 Post by efrpcabo »

stevepusser wrote:If you have no overriding objections to proprietary software, you could test the Nvidia graphics driver from the non-free section to see if that makes any difference. Follow the directions in the Debian wiki, though I prefer using module-assistant to set up the build environment:

Code: Select all

# apt install module-assistant
# m-a prepare
Thank you!

User avatar
efrpcabo
Posts: 108
Joined: 2013-08-08 06:36

Re: Buste XFCE: How can I find the cause of random crashes?

#10 Post by efrpcabo »

Segfault wrote:Every time I see IO errors I start with checking the health of hard drive.
This comment of yours made me expand my observations into the hardware realm.

And after some hours I remembered that I had changed the sata port of my system hard drive some time after installing Buster.

That happened when I decided to disconnect the DVD drive and use to connect another disk.
When I did that, I had disconnected all the sata cables and then connected them all again, but not exactly the same.

So, my system hard drive got connected to the sata port that was used by the DVD drive.
At the time, I didn't worry about that, but after this comment, I started thinking and investigated.

This port happens to have another color (black), while the other 3 ports are red.
Also, in BIOS is shows up as eSata instead of just Sata.

So, I connected my main drive to another red sata port, and one of the other disks to the black one.
And until now I hadn't another crash, and I am working a couple of hours.

It's still early to take conclusions, but this is the point of situation for me now.

User avatar
NFT5
df -h | grep > 20TiB
df -h | grep > 20TiB
Posts: 598
Joined: 2014-10-10 11:38
Location: Canberra, Australia
Has thanked: 10 times
Been thanked: 43 times

Re: Buste XFCE: How can I find the cause of random crashes?

#11 Post by NFT5 »

Hmmm. Sounds very much like what I was experiencing here. Although the thread related to KDE I have a parallel installation with XFCE and it does the same thing. Jessie and Stretch installations are rock solid.

in terms of hardware the only common factor between my machine and OP's is the same video card and nouveau driver.

One Google search result I read suggested changing USB connections to different ports. I've done that and frequency of the problem has dropped substantially, but not stopped altogether.. To be honest, I can't see that it could be hardware, simply because the problem simply does not occur when I run Jessie or Stretch. However, that doesn't eliminate a kernel or driver change interacting differently with the graphics card and killing X?

User avatar
efrpcabo
Posts: 108
Joined: 2013-08-08 06:36

Re: Buste XFCE: How can I find the cause of random crashes?

#12 Post by efrpcabo »

As the crashes came back, the cause wasn't the eSata port :(

User avatar
efrpcabo
Posts: 108
Joined: 2013-08-08 06:36

Re: Buste XFCE: How can I find the cause of random crashes?

#13 Post by efrpcabo »

NFT5 wrote:Hmmm. Sounds very much like what I was experiencing here. Although the thread related to KDE I have a parallel installation with XFCE and it does the same thing. Jessie and Stretch installations are rock solid.

in terms of hardware the only common factor between my machine and OP's is the same video card and nouveau driver.

One Google search result I read suggested changing USB connections to different ports. I've done that and frequency of the problem has dropped substantially, but not stopped altogether.. To be honest, I can't see that it could be hardware, simply because the problem simply does not occur when I run Jessie or Stretch. However, that doesn't eliminate a kernel or driver change interacting differently with the graphics card and killing X?
Thank you.
I have read the thread and it seems similar.
I've asked there if the OP had found the cause.

If I can't solve this soon, I think I'm going to Stretch.

User avatar
efrpcabo
Posts: 108
Joined: 2013-08-08 06:36

Re: Buste XFCE: How can I find the cause of random crashes?

#14 Post by efrpcabo »

stevepusser wrote:If you have no overriding objections to proprietary software, you could test the Nvidia graphics driver from the non-free section to see if that makes any difference. Follow the directions in the Debian wiki, though I prefer using module-assistant to set up the build environment:

Code: Select all

# apt install module-assistant
# m-a prepare
The directions on Debian Wiki say this:
----------------------------
Identification
The NVIDIA graphics processing unit (GPU) series/codename of an installed video card can usually be identified using the lspci command. For example:
$ lspci -nn | egrep -i "3d|display|vga"
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G80 [GeForce 8800 GTS] [10de:0193] (rev a2)

if this lspci command returns more than one line of output, you have an Optimus (hybrid) graphics chipset:
https://developer.nvidia.com/optimus
and the instructions on this page do not apply to you
Check the Bumblebee page instead:
https://wiki.debian.org/Bumblebee
----------------------------

So, I ran the command:
# lspci -nn | egrep -i "3d|display|vga"
And my outuput is:
00:16.3 Serial controller [0700]: Intel Corporation 8 Series/C220 Series Chipset Family KT Controller [8086:8c3d] (rev 04)
02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2)

Does this mean I have a Optimus (hybrid) graphics chipset?

The reason I ask is because the "3d" appears only in the last field: [8086:8c3d]

Also, I am experiencing this on a Lenovo ThinkCenter Desktop and Bumblebee seem aimed at laptops, like stated on Debian Wiki here:
https://wiki.debian.org/Bumblebee

"Bumblebee aims to provide support for NVIDIA Optimus laptops for GNU/Linux distributions. Using Bumblebee, you can use your NVIDIA card for rendering graphics which will be displayed using the Intel card."

The answer to my question is important because the the procedure is different for "yes" or "no":
Yes:
https://wiki.debian.org/Bumblebee
No:
https://wiki.debian.org/NvidiaGraphicsDrivers

User avatar
ruwolf
Posts: 641
Joined: 2008-02-18 05:04
Location: Banovce nad Bebravou
Has thanked: 40 times
Been thanked: 29 times

Re: Buste XFCE: How can I find the cause of random crashes?

#15 Post by ruwolf »

Fields on the end (in your case [8086:8c3d] and [10de:0a65]) are not word/abbreviation/acronym descriptions of devices. They are hexadecimal numbers, identifiers in format vendor:device.

User avatar
efrpcabo
Posts: 108
Joined: 2013-08-08 06:36

Re: Buste XFCE: How can I find the cause of random crashes?

#16 Post by efrpcabo »

ruwolf wrote:Fields on the end (in your case [8086:8c3d] and [10de:0a65]) are not word/abbreviation/acronym descriptions of devices. They are hexadecimal numbers, identifiers in format vendor:device.
Thanks.
That means that indeed I have a Optimus (hybrid) graphics chipset.
So I have to go with the Bumblebee.

User avatar
sunrat
Administrator
Administrator
Posts: 6497
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 118 times
Been thanked: 476 times

Re: Buste XFCE: How can I find the cause of random crashes?

#17 Post by sunrat »

efrpcabo wrote: Thanks.
That means that indeed I have a Optimus (hybrid) graphics chipset.
So I have to go with the Bumblebee.
No it doesn't mean that at all. As this is a desktop it most likely is NOT Optimus. You may be able to disable the Intel graphics in UEFI/BIOS setup menu and use just the Nvidia graphics, or pull the Nvidia card out and use the Intel graphics. As this is a low spec Nvidia card you may find it works well with the default nouveau driver which saves you the hassle of installing Nvidia.
It also may work fine without the Nvidia card at all, just using the onboard graphics.
Either way you should install firmware-misc-nonfree and intel-microcode.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 72 times

Re: Buste XFCE: How can I find the cause of random crashes?

#18 Post by stevepusser »

You have described an Intel serial device, just as it says. That is not a video device. You only have the Nivdia GPU.

Install and run nvidia-detect. That will tell you which of the different Nvidia drivers in the Debian non-free section is right for your card. You don't have to research the hexadecimal IDs. It's right in the wiki.

You can install gsmartcontrol and have it run some diagnostics on your hard drive to check its health, too. I'd do that as part of regular maintenance, anyway.
MX Linux packager and developer

User avatar
efrpcabo
Posts: 108
Joined: 2013-08-08 06:36

Re: Buste XFCE: How can I find the cause of random crashes?

#19 Post by efrpcabo »

sunrat wrote:
efrpcabo wrote: Thanks.
That means that indeed I have a Optimus (hybrid) graphics chipset.
So I have to go with the Bumblebee.
No it doesn't mean that at all. As this is a desktop it most likely is NOT Optimus. You may be able to disable the Intel graphics in UEFI/BIOS setup menu and use just the Nvidia graphics, or pull the Nvidia card out and use the Intel graphics. As this is a low spec Nvidia card you may find it works well with the default nouveau driver which saves you the hassle of installing Nvidia.
It also may work fine without the Nvidia card at all, just using the onboard graphics.
Either way you should install firmware-misc-nonfree and intel-microcode.
Thank you!

I want to use the Nvidia card because its output digital and the Intel is analogic, but I will try to disable Intel in BIOS.

intel-microcode:
I already had installed it because of another issue

firmware-misc-nonfree:
thanks for the tip!

User avatar
efrpcabo
Posts: 108
Joined: 2013-08-08 06:36

Re: Buste XFCE: How can I find the cause of random crashes?

#20 Post by efrpcabo »

stevepusser wrote:You have described an Intel serial device, just as it says. That is not a video device. You only have the Nivdia GPU.

Install and run nvidia-detect. That will tell you which of the different Nvidia drivers in the Debian non-free section is right for your card. You don't have to research the hexadecimal IDs. It's right in the wiki.

You can install gsmartcontrol and have it run some diagnostics on your hard drive to check its health, too. I'd do that as part of regular maintenance, anyway.
Thank you!

nvidia-detect:
Detected NVIDIA GPUs:
02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2)
Checking card: NVIDIA Corporation GT218 [GeForce 210] (rev a2)
Your card is only supported up to the 340 legacy drivers series.
It is recommended to install the
nvidia-legacy-340xx-driver
package.

So, I will install:
nvidia-legacy-340xx-driver

gsmartcontrol:
thanks for the tip!

Post Reply