Re: [Dorset] Very slow Desktop startup problem
Hi Clive, > + grep -w swap /etc/fstab > # swap was on /dev/sda2 during installation > UUID=66b0460e-9393-4743-a751-787c8108c4f0 noneswapsw > 0 0 The edit went fine. > + swapon -s > Filename TypeSizeUsedPriority > /dev/sda4 partition 5062652 0 > -2 > + free -m > totalusedfree shared buff/cache > available > Mem: 2992 5991509 128 882 > 2086 > Swap: 4943 04943 Swap space is now being found and used, though there's ample free memory after booting so it hasn't been needed yet. Is it a 3 GiB RAM machine? > + systemd-analyze > Startup finished in 12.108s (kernel) + 21.402s (userspace) = 33.510s > + systemd-analyze blame > 9.847s dev-sda1.device > 7.400s systemd-tmpfiles-setup-dev.service > 6.308s > udev-configure-printer@-devices-pci:00-:00:1d.7-usb1-1\x2d2.service > 2.931s lvm2-monitor.service > 2.229s thermald.service > 2.003s accounts-daemon.service > 1.986s loadcpufreq.service > 1.904s NetworkManager.service > 1.740s ntp.service > ... > > Start up appears to be quicker (56 secs from button to log-in) so that > may have cleared the problem as it's two old Pentium CPUs. That looks a reasonable boot time to me. You could see if ‘systemd-analyze blame’ still shows a long ~10 second time for dev-sda1.device after you reboot without cutting the power. It might just be slow to spin up on power on. > Will bring printouts tonight for info. Don't think they're needed if you haven't already committed paper. :-) -- Cheers, Ralph. -- Next meeting: BEC, Bournemouth, Tuesday, 2019-08-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Very slow Desktop startup problem
Hi Clive, > + grep -w swap /etc/fstab > # swap was on /dev/sda2 during installation > UUID=830fffc7-e2cb-4b0a-b7fa-1b65198ce0c5 noneswapsw > 0 0 That line in /etc/fstab matches the time-out message when booting due to a swap area with that UUID not being found. > + lsblk -o type,name,fstype,label,uuid,mountpoint,size,partuuid > TYPE NAME FSTYPE LABEL UUID MOUNTPOINT > SIZE PARTUUID > disk sdb > 298.1G > part ├─sdb4 ext4 move 5853322d-2d9d-4f95-94c4-b5ccec4a660f > 95.6G 0007e4a2-04 > part ├─sdb2 ext4 Linux_30150ffe2-94b8-4385-8f8f-9831be8a6165 > 105.2G 0007e4a2-02 > part ├─sdb3 vfat MSDOS DF83-27FE > 37.3G 0007e4a2-03 > part └─sdb1 ext4 Linux_2e1b1b42e-c985-4a51-989c-d4b247ce401b > 60.1G 0007e4a2-01 > rom sr0 > 1024M > disk sda > 298.1G > part ├─sda4 swap 66b0460e-9393-4743-a751-787c8108c4f0 > 4.8G 00099971-04 > part ├─sda2 ext4 HomeBackup 8dfb5549-95bf-42d6-bcf5-1d4f9d8de40f > 72.2G 00099971-02 > part ├─sda3 ext4 /home 4fe28afb-f9e5-4a9c-897f-691c777a183f /home > 196.6G 00099971-03 > part └─sda1 ext4 bba353ae-f00e-49a5-b51e-3ec0f8b8453e / > 24.5G 00099971-01 The only swap-type partition is /dev/sda4, not the /dev/sda2 mentioned in /etc/fstab's comment above. So two choices to improve things are - Edit /etc/fstab and change 830fffc7-e2cb-4b0a-b7fa-1b65198ce0c5 to 66b0460e-9393-4743-a751-787c8108c4f0 - Alter /dev/sda4's UUID to be the value in /etc/fstab. I won't say how because the other method has less chance of severely breaking things if a mistake is made. :-) To do the first suggestion, paste these lines. old=UUID=830fffc7-e2cb-4b0a-b7fa-1b65198ce0c5 new=UUID=66b0460e-9393-4743-a751-787c8108c4f0 sudo -i sed -i.$(/bin/date -Is) "s/^$old/$new/" /etc/fstab This command that you ran before should now show the new UUID in place. grep -w swap /etc/fstab Reboot and judge if booting is quicker. Once booted, capture the output of these commands and tell us the URL. ( set -x grep -w swap /etc/fstab swapon -s free -m systemd-analyze systemd-analyze blame ) |& curl -sSF 'f:1=<-' ix.io -- Cheers, Ralph. -- Next meeting: BEC, Bournemouth, Tuesday, 2019-08-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Very slow Desktop startup problem
On Sat, 06 Jul 2019 07:54:08 +0100, ra...@inputplus.co.uk said: > Having an unnoticed option can be the cause of awkward bugs Try this: $ ls [directory listing] $ ls * [same directory listing] $ touch -- -l # make a file called '-l' $ ls * [long directory listing as file '-l' is interpreted as an option Now, imagine a file called ' -rf' and how that might impact an 'rm' command. -- Linux Tips: https://www.tiger-computing.co.uk/category/techtips/ -- Next meeting: BEC, Bournemouth, Tuesday, 2019-08-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Very slow Desktop startup problem
Hi Victor, > > > Saying 'do_something_interesting 2>&1 > something_interesting.log' > > > > Or, the alternative action of ‘foo >bar 2>&1’. :-) > > Now to me, it's more logical to tinker with the file descriptors of > the command first and then say where they are going rather than vice > versa. But the order is significant. :-) $ >foo $ $ ls foo missing >out 2>&1 $ cat out ls: cannot access 'missing': No such file or directory foo $ $ rm out $ ls foo missing 2>&1 >out ls: cannot access 'missing': No such file or directory $ cat out foo $ > On a related note I recall early *nixes where the command switches had > to precede all the other arguments. That's also the POSIX standard today; see getopt(3p). > Took me years to get used to the fact that in later versions you could > say 'ls foo* -l' This is a GNU extension and a bad idea. The Unix way is ‘ls -l -t foo bar xyzzy’ that matches ‘verb adverbs nouns’. It means the reader can stop on reaching the first non-option argument, knowing the rest are data rather than options. And code can do that same, e.g. getopt(). Having an unnoticed option can be the cause of awkward bugs, even dangerous ones depending on the command, and can come about through command-line editing. If that option is treating as an argument, a filename say, then that tends to have a lot less impact. -- Cheers, Ralph. -- Next meeting: BEC, Bournemouth, Tuesday, 2019-08-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Very slow Desktop startup problem
:) Now to me, it's more logical to tinker with the file descriptors of the command first and then say where they are going rather than vice versa. On a related note I recall early *nixes where the command switches had to precede all the other arguments. Took me years to get used to the fact that in later versions you could say 'ls foo* -l' best regards, 웃 Victor Churchill, Netley Abbey, Southampton 07970 844083 On Fri, 5 Jul 2019 at 13:35, Ralph Corderoy wrote: > Hi Victor, > > > Saying 'do_something_interesting 2>&1 > something_interesting.log' > > Or, the alternative action of ‘foo >bar 2>&1’. :-) > > -- > Cheers, Ralph. > > -- > Next meeting: BEC, Bournemouth, Tuesday, 2019-08-06 20:00 > Check to whom you are replying > Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ > New thread, don't hijack: mailto:dorset@mailman.lug.org.uk > -- Next meeting: BEC, Bournemouth, Tuesday, 2019-08-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Very slow Desktop startup problem
Hi Victor, > Saying 'do_something_interesting 2>&1 > something_interesting.log' Or, the alternative action of ‘foo >bar 2>&1’. :-) -- Cheers, Ralph. -- Next meeting: BEC, Bournemouth, Tuesday, 2019-08-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Very slow Desktop startup problem
Thanks Ralph and Patrick. > it [ |& ] is shorthand for 2>&1 ...bash also adds ‘&>foo’ meaning ‘>foo 2>&1’. Likewise ‘&>>’. Well we live and learn. I'm going to add this to my catalogue of scenarios where I have developed a muscle-memory for doing things an 'old' way, and then a new and usually better better way has come along while I wasn't looking. Saying 'do_something_interesting 2>&1 > something_interesting.log' or 'do_something 2>&1 | grep -i whoopsie' have been in my mental toolbox so long I can find them in the dark. So I never thought of looking for newer shinier versions. I must find my way back to Bournemouth sometime for one of the monthly meetups. best regards, 웃 Victor Churchill, Netley Abbey, Southampton 07970 844083 On Fri, 5 Jul 2019 at 12:55, Ralph Corderoy wrote: > Hi Victor, > > Hope life's treating you well since you moved ‘abroad’. > > Patrick wrote: > > > > (yada yada) |& curl -sSF 'f:1=<-' ix.io > > > > > > I was puzzled to see the '&' in your command above. > > Patrick's answered that ‘|&’ is a bash shorthand for ‘2>&1 |’. > > > > I'd have thought that saying > > > (yada yada) | curl -sSF 'f:1=<-' ix.io > > > would do the trick > > If the sub-shell in parenthesis produced any stderr for Clive, which > would probably be interesting to us, then it would appear on his TTY and > not be piped to curl so we see it. Redirecting stderr to the same place > as stdout, the pipe, avoids this. > > > In bash(1), |& is one operator, not two. > > bash also adds ‘&>foo’ meaning ‘>foo 2>&1’. Likewise ‘&>>’. > > -- > Cheers, Ralph. > > -- > Next meeting: BEC, Bournemouth, Tuesday, 2019-08-06 20:00 > Check to whom you are replying > Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ > New thread, don't hijack: mailto:dorset@mailman.lug.org.uk > -- Next meeting: BEC, Bournemouth, Tuesday, 2019-08-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Very slow Desktop startup problem
Hi Victor, Hope life's treating you well since you moved ‘abroad’. Patrick wrote: > > > (yada yada) |& curl -sSF 'f:1=<-' ix.io > > > > I was puzzled to see the '&' in your command above. Patrick's answered that ‘|&’ is a bash shorthand for ‘2>&1 |’. > > I'd have thought that saying > > (yada yada) | curl -sSF 'f:1=<-' ix.io > > would do the trick If the sub-shell in parenthesis produced any stderr for Clive, which would probably be interesting to us, then it would appear on his TTY and not be piped to curl so we see it. Redirecting stderr to the same place as stdout, the pipe, avoids this. > In bash(1), |& is one operator, not two. bash also adds ‘&>foo’ meaning ‘>foo 2>&1’. Likewise ‘&>>’. -- Cheers, Ralph. -- Next meeting: BEC, Bournemouth, Tuesday, 2019-08-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Very slow Desktop startup problem
On Fri, 5 Jul 2019 at 08:44, Ralph Corderoy wrote: > (yada yada) |& curl -sSF 'f:1=<-' ix.io On Fri, 05 Jul 2019 11:42:22 +0100, Victor Churchill wrote: > I was puzzled to see the '&' in your command above. I'd have thought that > saying > (yada yada) | curl -sSF 'f:1=<-' ix.io > would do the trick In bash(1), |& is one operator, not two. From the manual: > If |& is used, command's standard error, in addition to its standard > output, is connected to command2's standard input through the pipe; it > is shorthand for 2>&1 |. On Fri, 05 Jul 2019 11:42:22 +0100, Victor Churchill wrote: > [I'd have thought that] adding the ampersand would, if anything, cause > it to break: "pipe this lot to nothing, and while you're about it > run this curl with no stdin" I think that would be the meaning if you were to put a space between | and &: (yada yada) | & curl -sSF 'f:1=<-' ix.io But that form produces a syntax error. $ echo "dogs" | & cat bash: syntax error near unexpected token `&' Patrick -- Next meeting: BEC, Bournemouth, Tuesday, 2019-08-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Very slow Desktop startup problem
Hi Ralph, Neat trick with ix.io; I hadn't met that before. A pastebin for one-liners! I was puzzled to see the '&' in your command above. I'd have thought that saying (yada yada) | curl -sSF 'f:1=<-' ix.io would do the trick, and that adding the ampersand would, if anything, cause it to break: "pipe this lot to nothing, and while you're about it run this curl with no stdin". Obviously I'm mistaken, but I don't know why: can you enlighten? best regards, 웃 Victor Churchill, Netley Abbey, Southampton 07970 844083 On Fri, 5 Jul 2019 at 08:44, Ralph Corderoy wrote: > Hi Clive, > > > Should the swap show a mount point and if so where? (/?) > > No, a mount point is a directory where the filesystem's root directory > appears, e.g. /home is a common one. Whilst it's mounted, the contents > of the original /home directory are inaccessible as accesses pass across > to the mounted filesystem instead. > > > probably won't get the time to run other commands till weekend > > Well when you do, here's an updated version that tells us similar > information to above, and more. > > ( > set -x > grep -w swap /etc/fstab > lsblk -o type,name,fstype,label,uuid,mountpoint,size,partuuid > sudo -i blkid > ls -l /dev/disk/* > ) |& > curl -sSF 'f:1=<-' ix.io > > -- > Cheers, Ralph. > > -- > Next meeting: BEC, Bournemouth, Tuesday, 2019-08-06 20:00 > Check to whom you are replying > Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ > New thread, don't hijack: mailto:dorset@mailman.lug.org.uk > -- Next meeting: BEC, Bournemouth, Tuesday, 2019-08-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Very slow Desktop startup problem
Hi Clive, > Should the swap show a mount point and if so where? (/?) No, a mount point is a directory where the filesystem's root directory appears, e.g. /home is a common one. Whilst it's mounted, the contents of the original /home directory are inaccessible as accesses pass across to the mounted filesystem instead. > probably won't get the time to run other commands till weekend Well when you do, here's an updated version that tells us similar information to above, and more. ( set -x grep -w swap /etc/fstab lsblk -o type,name,fstype,label,uuid,mountpoint,size,partuuid sudo -i blkid ls -l /dev/disk/* ) |& curl -sSF 'f:1=<-' ix.io -- Cheers, Ralph. -- Next meeting: BEC, Bournemouth, Tuesday, 2019-08-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Very slow Desktop startup problem
Hi Ralph Had a few minutes earlier so looked at the partions on the PC, details are:- sda1 Ext4 Mount= / size 25GB flag= boot sda2 " -- size 72GB label= Homebackup sda3 " Mount= /Home size 196GB sda4 swap no mount point size 5GB swap UUID = 66b0460e-9393-4743-a751-787c8108c410 Should the swap show a mount point and if so where? (/?) Not checked the UUID against what was shown in your earlier commands. probably won't get the time to run other commands till weekend (possibly Sunday) C A Wills On 03/07/2019 00:05, Ralph Corderoy wrote: Hi, Keith wrote: swapon -s You might need that to be /sbin/swapon I think it worked for Clive as it stood. I saw some output this evening that he brought along and the summary is /etc/fstab names a UUID for swap, free(1) and swapon(1) confirm there's no swap configured, the UUID is the same as the partition mentioned in the journal as not available after a time-out, and over all userspace takes a bit more than three minutes to become ready. Clive, the command I mentioned to show all the drives and partitions by their various names is ‘ls -l /dev/disk/*’. It would also be useful to have the lines from /etc/fstab again that mentioned swap: ‘grep -w swap /etc/fstab’. So paste this on the troublesome desktop machine: ( set -x grep -w swap /etc/fstab ls -l /dev/disk/* ) |& curl -sSF 'f:1=<-' ix.io -- Next meeting: BEC, Bournemouth, Tuesday, 2019-08-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Very slow Desktop startup problem
Thanks Ralph. Will try those commands when I've got the time to work on the desktop machine wiyh no interruptions. Painting the porch while we have the good weather! Lily is not worried as much now as she's got used to switching on and doing something else before going back; only gets annoyed when time is pushed for a particular email reply. Several high profile exhibitions coming up in the next 2 months, one in Christchurch and the other in London, but nearly there, only the mounting of the lace (my job!) to finish off. C A Wills On 03/07/2019 00:05, Ralph Corderoy wrote: Hi, Keith wrote: swapon -s You might need that to be /sbin/swapon I think it worked for Clive as it stood. I saw some output this evening that he brought along and the summary is /etc/fstab names a UUID for swap, free(1) and swapon(1) confirm there's no swap configured, the UUID is the same as the partition mentioned in the journal as not available after a time-out, and over all userspace takes a bit more than three minutes to become ready. Clive, the command I mentioned to show all the drives and partitions by their various names is ‘ls -l /dev/disk/*’. It would also be useful to have the lines from /etc/fstab again that mentioned swap: ‘grep -w swap /etc/fstab’. So paste this on the troublesome desktop machine: ( set -x grep -w swap /etc/fstab ls -l /dev/disk/* ) |& curl -sSF 'f:1=<-' ix.io -- Next meeting: BEC, Bournemouth, Tuesday, 2019-08-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Very slow Desktop startup problem
Hi, Keith wrote: > > swapon -s > > You might need that to be /sbin/swapon I think it worked for Clive as it stood. I saw some output this evening that he brought along and the summary is /etc/fstab names a UUID for swap, free(1) and swapon(1) confirm there's no swap configured, the UUID is the same as the partition mentioned in the journal as not available after a time-out, and over all userspace takes a bit more than three minutes to become ready. Clive, the command I mentioned to show all the drives and partitions by their various names is ‘ls -l /dev/disk/*’. It would also be useful to have the lines from /etc/fstab again that mentioned swap: ‘grep -w swap /etc/fstab’. So paste this on the troublesome desktop machine: ( set -x grep -w swap /etc/fstab ls -l /dev/disk/* ) |& curl -sSF 'f:1=<-' ix.io -- Cheers, Ralph. -- Next meeting: BEC, Bournemouth, Tuesday, 2019-07-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Very slow Desktop startup problem
On Tue, 02 Jul 2019 16:48:43 +0100, ra...@inputplus.co.uk said: > swapon -s You might need that to be /sbin/swapon unless you run as root the lines Ralph posted (and we don't run things as root unless we have to, right?) Neat trick though, Ralph! -- Linux Tips: https://www.tiger-computing.co.uk/category/techtips/ -- Next meeting: BEC, Bournemouth, Tuesday, 2019-07-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Very slow Desktop startup problem
Hi Clive, > > What's the output of these commands? > > Will try and give info tonight if I can copy to a doc. Paste into a terminal window these lines. ( set -x systemd-analyze swapon -s free -m grep -w swap /etc/fstab ) |& curl -F 'f:1=<-' ix.io A short URL will be printed; tell us what it is. :-) -- Cheers, Ralph. -- Next meeting: BEC, Bournemouth, Tuesday, 2019-07-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Very slow Desktop startup problem
Hi Ralph (& Victor) Answers to some of the questions below. It's not the laptop but the PC we're concerned about. See you tonight. C A Wills On 02/07/2019 14:53, Ralph Corderoy wrote: Hi Victor, Has anything changed recently regarding your Internet setup? Yes but only last week and the problem started well before then. New router as now on Fibre. If SOmetimes a lo.o.o.ong delay at bootup is associated with a DNS timeout. If something is trying to get a connection, and waiting for a minute before failing, that should show up in the system logs too. You're right. Clive sent me some lines from journalctl(1)'s output off-list. They include, cutting out some of the fields, 14:01:05 systemd-journald[328]: Runtime journal (/run/log/journal/) is 3.7M, max 29.9M, 26.1M 14:01:05 kernel: microcode: microcode updated early to revision 0xa0b, date = 2010-09-28 ... 14:01:15 ntpdate[797]: name server cannot be used: Temporary failure in name resolution (-3) ... 14:02:35 systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-830fffc7\x2de2cb\x2d4b0 ... 14:02:35 systemd[1]: Dependency failed for /dev/disk/by-uuid/830fffc7-e2cb-4b0a-b7fa-1b65198c 14:02:35 systemd[1]: Dependency failed for Swap. 14:02:35 systemd[1]: swap.target: Job swap.target/start failed with result 'dependency'. ... 14:02:38 lightdm[1112]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_k 14:02:38 lightdm[1112]: PAM adding faulty module: pam_gnome_keyring.so 14:02:38 lightdm[1112]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: c 14:02:38 lightdm[1112]: PAM adding faulty module: pam_kwallet.so 14:02:38 lightdm[1112]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: 14:02:38 lightdm[1112]: PAM adding faulty module: pam_kwallet5.so Clive, once the laptop is up and running, albeit slow, does network access work? Desktop - Yes How do IP addresses get dished out on your network? Does your modem/router act as a DHCP server? Yes, they used to be 'reserved' for each main device but now they're not. Problem started while having 'reserved' address's. Is it configured to only give IP addresses to particular MAC addresses rather than all comers? originaly Yes but not now. Do you know why it might be trying to configure a missing partition a swap space? No, will check with Gparted for tonight. What's the output of these commands? Will try and give info tonight if I can copy to a doc. systemd-analyze swapon -s free -m grep -w swap /etc/fstab -- Next meeting: BEC, Bournemouth, Tuesday, 2019-07-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Very slow Desktop startup problem
Hi Victor, > Has anything changed recently regarding your Internet setup? If > SOmetimes a lo.o.o.ong delay at bootup is associated with a DNS > timeout. If something is trying to get a connection, and waiting for a > minute before failing, that should show up in the system logs too. You're right. Clive sent me some lines from journalctl(1)'s output off-list. They include, cutting out some of the fields, 14:01:05 systemd-journald[328]: Runtime journal (/run/log/journal/) is 3.7M, max 29.9M, 26.1M 14:01:05 kernel: microcode: microcode updated early to revision 0xa0b, date = 2010-09-28 ... 14:01:15 ntpdate[797]: name server cannot be used: Temporary failure in name resolution (-3) ... 14:02:35 systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-830fffc7\x2de2cb\x2d4b0 ... 14:02:35 systemd[1]: Dependency failed for /dev/disk/by-uuid/830fffc7-e2cb-4b0a-b7fa-1b65198c 14:02:35 systemd[1]: Dependency failed for Swap. 14:02:35 systemd[1]: swap.target: Job swap.target/start failed with result 'dependency'. ... 14:02:38 lightdm[1112]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_k 14:02:38 lightdm[1112]: PAM adding faulty module: pam_gnome_keyring.so 14:02:38 lightdm[1112]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: c 14:02:38 lightdm[1112]: PAM adding faulty module: pam_kwallet.so 14:02:38 lightdm[1112]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: 14:02:38 lightdm[1112]: PAM adding faulty module: pam_kwallet5.so Clive, once the laptop is up and running, albeit slow, does network access work? How do IP addresses get dished out on your network? Does your modem/router act as a DHCP server? Is it configured to only give IP addresses to particular MAC addresses rather than all comers? Do you know why it might be trying to configure a missing partition as swap space? What's the output of these commands? systemd-analyze swapon -s free -m grep -w swap /etc/fstab -- Cheers, Ralph. -- Next meeting: BEC, Bournemouth, Tuesday, 2019-07-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Very slow Desktop startup problem
Has anything changed recently regarding your Internet setup? If SOmetimes a lo.o.o.ong delay at bootup is associated with a DNS timeout. If something is trying to get a connection, and waiting for a minute before failing, that should show up in the system logs too. best regards, 웃 Victor Churchill, Netley Abbey, Southampton 07970 844083 On Mon, 1 Jul 2019 at 09:31, John Carlyle-Clarke wrote: > You could try using systemd-analyze [1] to see how the boot time breaks > down. > > [1] > > https://wiki.archlinux.org/index.php/Improving_performance/Boot_process#Using_systemd-analyze > > On Sun, 30 Jun 2019 at 18:46, C Wills wrote: > > > Hi All > > > > My wife's desktop PC running Mint 18.10 takes a very long time in > > starting approx 4-5mins, (it used to start in less than 1min). It's also > > slow in 'logging in' and if trying to copy pictures from a USB stick to > > her /Pictures/ folder it takes ages at each operation. > > It would appear that something is happening in start up that loops round > > and hogs memory. > > > > How can I find out what's happening during the start up process please? > > > > -- > > C A Wills > > -- > > Next meeting: BEC, Bournemouth, Tuesday, 2019-07-02 20:00 > > Check to whom you are replying > > Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ > > New thread, don't hijack: mailto:dorset@mailman.lug.org.uk > > > -- > Next meeting: BEC, Bournemouth, Tuesday, 2019-07-02 20:00 > Check to whom you are replying > Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ > New thread, don't hijack: mailto:dorset@mailman.lug.org.uk > -- Next meeting: BEC, Bournemouth, Tuesday, 2019-07-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Very slow Desktop startup problem
You could try using systemd-analyze [1] to see how the boot time breaks down. [1] https://wiki.archlinux.org/index.php/Improving_performance/Boot_process#Using_systemd-analyze On Sun, 30 Jun 2019 at 18:46, C Wills wrote: > Hi All > > My wife's desktop PC running Mint 18.10 takes a very long time in > starting approx 4-5mins, (it used to start in less than 1min). It's also > slow in 'logging in' and if trying to copy pictures from a USB stick to > her /Pictures/ folder it takes ages at each operation. > It would appear that something is happening in start up that loops round > and hogs memory. > > How can I find out what's happening during the start up process please? > > -- > C A Wills > -- > Next meeting: BEC, Bournemouth, Tuesday, 2019-07-02 20:00 > Check to whom you are replying > Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ > New thread, don't hijack: mailto:dorset@mailman.lug.org.uk > -- Next meeting: BEC, Bournemouth, Tuesday, 2019-07-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Very slow Desktop startup problem
Further to Keith's suggestion, 'dmesg' may also hold some clues. You would be surprised what shows in there. On Sun, 30 Jun 2019 at 22:07, Keith Edmunds wrote: > My first move would be to check /var/log/syslog or /var/log/messages for > any disk errors. > -- > Linux Tips: https://www.tiger-computing.co.uk/category/techtips/ > > -- > Next meeting: BEC, Bournemouth, Tuesday, 2019-07-02 20:00 > Check to whom you are replying > Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ > New thread, don't hijack: mailto:dorset@mailman.lug.org.uk > -- Next meeting: BEC, Bournemouth, Tuesday, 2019-07-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Very slow Desktop startup problem
On Sun, 30 Jun 2019 21:34:40 +0100 PeterMerchant via dorset wrote: > On 30/06/2019 18:46, C Wills wrote: > > Hi All > > > > My wife's desktop PC running Mint 18.10 takes a very long time in starting > > approx 4-5mins, (it > > used to start in less than 1min). It's also slow in 'logging in' and if > > trying to copy pictures > > from a USB stick to her /Pictures/ folder it takes ages at each operation. > > It would appear that > > something is happening in start up that loops round and hogs memory. > > > > How can I find out what's happening during the start up process please? > > > My KDE has in it's setting a 'startup and shutdown' that says what > applications are to start on > startup, in my case dropbox and Gkrellm. > > Peter > > Like wise XFCE has a startup section which list the auto start applications Also check your /etc/fstab to make sure that all your partition have the correct UUID and are being mounted This link might help https://www.tecmint.com/find-and-fix-linux-boot-issues/ Hope it helps Tim H -- Next meeting: BEC, Bournemouth, Tuesday, 2019-07-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Very slow Desktop startup problem
On 30/06/2019 18:46, C Wills wrote: Hi All My wife's desktop PC running Mint 18.10 takes a very long time in starting approx 4-5mins, (it used to start in less than 1min). It's also slow in 'logging in' and if trying to copy pictures from a USB stick to her /Pictures/ folder it takes ages at each operation. It would appear that something is happening in start up that loops round and hogs memory. How can I find out what's happening during the start up process please? My KDE has in it's setting a 'startup and shutdown' that says what applications are to start on startup, in my case dropbox and Gkrellm. Peter -- Next meeting: BEC, Bournemouth, Tuesday, 2019-07-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
[Dorset] Very slow Desktop startup problem
Hi All My wife's desktop PC running Mint 18.10 takes a very long time in starting approx 4-5mins, (it used to start in less than 1min). It's also slow in 'logging in' and if trying to copy pictures from a USB stick to her /Pictures/ folder it takes ages at each operation. It would appear that something is happening in start up that loops round and hogs memory. How can I find out what's happening during the start up process please? -- C A Wills -- Next meeting: BEC, Bournemouth, Tuesday, 2019-07-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
