Computer frozen - no response to mouse or keyboard commands...

[tenfoot]

Using Sparky v5.x Mate

In case it helps, in Control Panel

Power management
Actions
Put computer to sleep when inactive for: Never
Display
Put display to sleep when inactive for: Never

Screensaver
Activate screensaver unticked
Lock screen when screensaver active unticked

Normally, if I leave the computer for a while the display turns off and a blank screen is shown, and I need to press the Enter key to get back to the Desktop.

After today's updates, things are very different. When I come back to the computer after leaving it, the Desktop is still displayed. The mouse pointer can be moved but no commands are activated.  The only way I can resume using the computer is to do a hard reboot.

I have searched for logfiles and found two:

Code Select Expand

/var/log/apt/history/log
Start-Date: 2017-11-21  07:21:23
Commandline: apt full-upgrade --no-install-recommends -y --force-yes
Requested-By: zed (1000)
Upgrade: tracker-extract:amd64 (2.0.2-1, 2.0.3-1), startpar:amd64 (0.59-3.2,
0.59-4), gvfs-backends:amd64 (1.34.1-1, 1.34.1-1+b1), gvfs-bin:amd64 (1.34.1-1, 1.34.1-1+b1),
libsystemd0:amd64 (235-2, 235-3), libtracker-sparql-2.0-0:amd64 (2.0.1-1, 2.0.2-1),
udev:amd64 (235-2, 235-3), libudev1:amd64 (235-2, 235-3), tracker-miner-fs:amd64 (2.0.2-1, 2.0.3-1),
libtracker-miner-2.0-0:amd64 (2.0.1-1, 2.0.2-1), gvfs-libs:amd64 (1.34.1-1, 1.34.1-1+b1),
gvfs-fuse:amd64 (1.34.1-1, 1.34.1-1+b1), systemd-sysv:amd64 (235-2, 235-3),
zenity:amd64 (3.24.0-1, 3.26.0-1), libpam-systemd:amd64 (235-2, 235-3),
systemd:amd64 (235-2, 235-3), rfkill:amd64 (0.5-1+b1, 0.5-2),
tracker:amd64 (2.0.1-1, 2.0.2-1), gvfs:amd64 (1.34.1-1, 1.34.1-1+b1),
libtracker-control-2.0-0:amd64 (2.0.1-1, 2.0.2-1),
gvfs-daemons:amd64 (1.34.1-1, 1.34.1-1+b1), zenity-common:amd64 (3.24.0-1, 3.26.0-1),
libfaac0:amd64 (1:1.29.8.2-dmo1, 1:1.29.9.2-dmo1), firefox-esr:amd64 (52.4.0esr-2, 52.5.0esr-1),
mplayer:amd64 (4:1.3.0~20171022.svn37997-dmo3, 4:1.3.0~20171022.svn37997-dmo4)
End-Date: 2017-11-21  07:21:56

and

Code Select Expand

/var/log/apt/term.log
Log started: 2017-11-21  07:21:23
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 268700 files and directories currently installed.)
Preparing to unpack .../systemd-sysv_235-3_amd64.deb ...
Unpacking systemd-sysv (235-3) over (235-2) ...
Preparing to unpack .../libpam-systemd_235-3_amd64.deb ...
Unpacking libpam-systemd:amd64 (235-3) over (235-2) ...
Preparing to unpack .../libsystemd0_235-3_amd64.deb ...
Unpacking libsystemd0:amd64 (235-3) over (235-2) ...
Setting up libsystemd0:amd64 (235-3) ...
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 268700 files and directories currently installed.)
Preparing to unpack .../systemd_235-3_amd64.deb ...
Unpacking systemd (235-3) over (235-2) ...
Preparing to unpack .../archives/udev_235-3_amd64.deb ...
Unpacking udev (235-3) over (235-2) ...
Preparing to unpack .../libudev1_235-3_amd64.deb ...
Unpacking libudev1:amd64 (235-3) over (235-2) ...
Setting up libudev1:amd64 (235-3) ...
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 268699 files and directories currently installed.)
Preparing to unpack .../00-firefox-esr_52.5.0esr-1_amd64.deb ...
Leaving 'diversion of /usr/bin/firefox to /usr/bin/firefox.real by firefox-esr'
Unpacking firefox-esr (52.5.0esr-1) over (52.4.0esr-2) ...
Preparing to unpack .../01-gvfs-backends_1.34.1-1+b1_amd64.deb ...
Unpacking gvfs-backends (1.34.1-1+b1) over (1.34.1-1) ...
Preparing to unpack .../02-gvfs-fuse_1.34.1-1+b1_amd64.deb ...
Unpacking gvfs-fuse (1.34.1-1+b1) over (1.34.1-1) ...
Preparing to unpack .../03-gvfs_1.34.1-1+b1_amd64.deb ...
Unpacking gvfs:amd64 (1.34.1-1+b1) over (1.34.1-1) ...
Preparing to unpack .../04-gvfs-daemons_1.34.1-1+b1_amd64.deb ...
Unpacking gvfs-daemons (1.34.1-1+b1) over (1.34.1-1) ...
Preparing to unpack .../05-gvfs-libs_1.34.1-1+b1_amd64.deb ...
Unpacking gvfs-libs:amd64 (1.34.1-1+b1) over (1.34.1-1) ...
Preparing to unpack .../06-gvfs-bin_1.34.1-1+b1_amd64.deb ...
Unpacking gvfs-bin (1.34.1-1+b1) over (1.34.1-1) ...
Preparing to unpack .../07-libfaac0_1%3a1.29.9.2-dmo1_amd64.deb ...
Unpacking libfaac0:amd64 (1:1.29.9.2-dmo1) over (1:1.29.8.2-dmo1) ...
Preparing to unpack .../08-libtracker-miner-2.0-0_2.0.2-1_amd64.deb ...
Unpacking libtracker-miner-2.0-0:amd64 (2.0.2-1) over (2.0.1-1) ...
Preparing to unpack .../09-tracker-miner-fs_2.0.3-1_amd64.deb ...
Unpacking tracker-miner-fs (2.0.3-1) over (2.0.2-1) ...
Preparing to unpack .../10-tracker-extract_2.0.3-1_amd64.deb ...
Unpacking tracker-extract (2.0.3-1) over (2.0.2-1) ...
Preparing to unpack .../11-tracker_2.0.2-1_amd64.deb ...
Unpacking tracker (2.0.2-1) over (2.0.1-1) ...
Preparing to unpack .../12-libtracker-control-2.0-0_2.0.2-1_amd64.deb ...
Unpacking libtracker-control-2.0-0:amd64 (2.0.2-1) over (2.0.1-1) ...
Preparing to unpack .../13-libtracker-sparql-2.0-0_2.0.2-1_amd64.deb ...
Unpacking libtracker-sparql-2.0-0:amd64 (2.0.2-1) over (2.0.1-1) ...
Preparing to unpack .../14-rfkill_0.5-2_amd64.deb ...
Unpacking rfkill (0.5-2) over (0.5-1+b1) ...
Preparing to unpack .../15-startpar_0.59-4_amd64.deb ...
Unpacking startpar (0.59-4) over (0.59-3.2) ...
Preparing to unpack .../16-zenity_3.26.0-1_amd64.deb ...
Unpacking zenity (3.26.0-1) over (3.24.0-1) ...
Preparing to unpack .../17-zenity-common_3.26.0-1_all.deb ...
Unpacking zenity-common (3.26.0-1) over (3.24.0-1) ...
Preparing to unpack .../18-mplayer_4%3a1.3.0~20171022.svn37997-dmo4_amd64.deb ...
Unpacking mplayer (4:1.3.0~20171022.svn37997-dmo4) over (4:1.3.0~20171022.svn37997-dmo3) ...
Setting up libfaac0:amd64 (1:1.29.9.2-dmo1) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for desktop-file-utils (0.23-2) ...
Setting up libtracker-sparql-2.0-0:amd64 (2.0.2-1) ...
Processing triggers for libglib2.0-0:amd64 (2.54.1-1) ...
Setting up gvfs-bin (1.34.1-1+b1) ...
Setting up startpar (0.59-4) ...
Installing new version of config file /etc/init/startpar-bridge.conf ...
Processing triggers for libc-bin (2.24-17) ...
Setting up udev (235-3) ...
update-initramfs: deferring update (trigger activated)
Setting up gvfs-libs:amd64 (1.34.1-1+b1) ...
Setting up firefox-esr (52.5.0esr-1) ...
Setting up systemd (235-3) ...
Removing user `systemd-bus-proxy' ...
Warning: group `systemd-bus-proxy' has no more members.
Done.
Setting up zenity-common (3.26.0-1) ...
Processing triggers for man-db (2.7.6.1-2) ...
Processing triggers for dbus (1.12.0-1) ...
Processing triggers for hicolor-icon-theme (0.17-1) ...
Setting up rfkill (0.5-2) ...
Setting up mplayer (4:1.3.0~20171022.svn37997-dmo4) ...
Setting up libtracker-miner-2.0-0:amd64 (2.0.2-1) ...
Setting up zenity (3.26.0-1) ...
Setting up gvfs-daemons (1.34.1-1+b1) ...
Setting up libtracker-control-2.0-0:amd64 (2.0.2-1) ...
Setting up systemd-sysv (235-3) ...
Setting up tracker (2.0.2-1) ...
Installing new version of config file /etc/xdg/autostart/tracker-store.desktop ...
Setting up tracker-extract (2.0.3-1) ...
Installing new version of config file /etc/xdg/autostart/tracker-extract.desktop ...
Setting up gvfs:amd64 (1.34.1-1+b1) ...
Setting up gvfs-backends (1.34.1-1+b1) ...
Setting up tracker-miner-fs (2.0.3-1) ...
Installing new version of config file /etc/xdg/autostart/tracker-miner-apps.desktop ...
Installing new version of config file /etc/xdg/autostart/tracker-miner-fs.desktop ...
Setting up libpam-systemd:amd64 (235-3) ...
Setting up gvfs-fuse (1.34.1-1+b1) ...
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.13.0-1-amd64
cryptsetup: WARNING: found more than one resume device candidate:
                     b8afe7cf-9dc5-4dea-89bb-5e1a1791a44b
                     UUID=8b69da22-b8a5-4b2c-971e-cd1d9cf3f85b
W: initramfs-tools configuration sets RESUME=UUID=UUID=8b69da22-b8a5-4b2c-971e-cd1d9cf3f85b
W: but no matching swap device is available.
I: The initramfs will attempt to resume from /dev/sda2
I: (UUID=8b69da22-b8a5-4b2c-971e-cd1d9cf3f85b)
I: Set the RESUME variable to override this.
Processing triggers for libc-bin (2.24-17) ...
Log ended: 2017-11-21  07:21:56

I think the second one listed is the process of extracting and installing those listed in the first one but I am not certain of this, which is why I have included both.

Would some kind member point me in the right direction to solve this problem, please?

Note:  After I had posted this message and returned to the Desktop, I found that I could initiate a program by clickin on the icon with the mouse button pressed but  none of my  keyboard shortcuts qorked >:(

[tenfoot]

I am rather surprised that no suggestions have bee posted regarding this problem.  However, there has been a recent development.  Now, when the computer has been left idle for a while, I return and the screen displays a login window.  Entering my username and password sometimes results in my normal desktop being displayed and at others a further screen saying that the screen is locked.  In both cases, the screen is still frozen and a restart is necessary.

So, at present. I only boot into Sparky if I need to print something (I still cannot get LinuxMint to recognise the printer :(), but see my messages regarding installing the stable version of Sparky.

And what really annoys me about the present problem, is that Sparky v5.0 still works perfectly on my laptop, a Lenovo Thinkpad T450s.

[paxmark1]

Seeing you say that printing does not work in L.mint and your prime conversation being about Sparky and mate - are you dual booting linux mint and Sparky. 

If so - do you have separate places for each boots /home   

If they share the same /home  -  It could very easily be a problem with conflicting "dot" files   Especially if you have a stable (very oldy-moldy) mate via LinuxMint on one / and a debian testing with much newer code on another / .  Not to mention the mint one using sysvinit (quite possibly from old ubuntu) and the Debian testing (Sparky's base) using systemd.

If not - for trying to debug what is the cause of it  I would recommend seeing what is going on via the logs from journalctl.  Digitalocean has some good info about systemd's journalctl, I have posted previous a few times.  journalctl -b -0    | grep ailed   might be a start.

I do have to do data input for several hours a day into 17.2 linuxmint laptops, with old mate, all to cloud and they are very locked down systems.  Not much fun and the old xorg-synaptic drives us crazy.  The web based system runs like a dream on an ancient Aspire one.  I wish you luck.

If there is a mate irc channel, it wouldn't hurt to ask around there also.  Sparky is a small distro, but I do love it. 

[tenfoot]

Seeing you say that printing does not work in L.mint and your prime conversation being about Sparky and mate - are you dual booting linux mint and Sparky.

Yes

If so - do you have separate places for each boots /home   

Yes.  They are separate installations and share nothing!

If they share the same /home  -  It could very easily be a problem with conflicting "dot" files   Especially if you have a stable (very oldy-moldy) mate via LinuxMint on one / and a debian testing with much newer code on another / .  Not to mention the mint one using sysvinit (quite possibly from old ubuntu) and the Debian testing (Sparky's base) using systemd.

Not applicable

If not - for trying to debug what is the cause of it  I would recommend seeing what is going on via the logs from journalctl.  Digitalocean has some good info about systemd's journalctl, I have posted previous a few times.  journalctl -b -0    | grep ailed   might be a start.

I will try that and report back.

I do have to do data input for several hours a day into 17.2 linuxmint laptops, with old mate, all to cloud and they are very locked down systems.  Not much fun and the old xorg-synaptic drives us crazy.  The web based system runs like a dream on an ancient Aspire one.  I wish you luck.

If there is a mate irc channel, it wouldn't hurt to ask around there also.  Sparky is a small distro, but I do love it.

Sparky is my first choice, too, and it is very annoying that I cannot fathom out what the solution is.  However, watch this space :)

[bardo]

Hi tenfoot,

i am relatively new in here and may be totally off track, but... This is an idea:
Almost every Linux installation makes use of an existing swap partition without caring, if it is meant to be used. That in itself is not a problem, as long as you just boot up every OS and properly shut it down as well. But it matters, if a "suspend" or a "hibernate" operation is involved, as that usually uses the swap partition. This could lead to the swap partition belonging to the "other linux" OS.

Not sure, if this can be your problem.
One way to check might be to disable swap and to reinitialize the partition.
But other ways come to mind as well.
In case, you could confirm this being the culprit, you could use the RESUME variable and set it to none (in initramfs-tools/conf.d/resume) and rebuild the initram (via "sudo update-initramfs -u -k all")
Alternatively, you could teach both OS to use their own swap partitions (creating a new one and reconfiguring one OS only to use it exclusively).

But keep in mind, that all this is based on a theory, that i did not check properly. YOU should, though.
Good luck,
bardo

edit: of course, i am assuming, your hardware was allright. (because hw-problems can manifest like that as well. If you want to get rid of that suspicion, i suggest to run memtest for 1 day.)

[Wombat]

Hi tenfoot

I'll only be guessing with these solutions as I'm running KDE...but if they help....

Have you updated again? Only a few seem to have later releases. Worth a try anyway!

I return and the screen displays a login window.

I changed the display manager from GDM to Lightdm after the mid-October update problems. Was the only way i could get back to KDE after installing  SparkyOpenBox. Even sddm didn't help.

[Capitain_Jack]

Hi tenfoot
I'll only be guessing with these solutions as I'm running KDE...but if they help....
I changed the display manager from GDM to Lightdm after the mid-October update problems. Was the only way i could get back to KDE after installing  SparkyOpenBox. Even sddm didn't help.

Wich window manager are you using? I found out that installing anything other than KDE messes with it, make sure to reconfigure kwin package as stated at this below post and use sddm as loguin manager.
https://askubuntu.com/questions/576340/kde-plasma-5-upgrade-has-removed-my-window-decorations