[SOLVED] MATE really slow after update.

kanarok · 2015-04-27 21:52:02

Good evening fellow Archers,

after my last system update I have serveral issues with my system.

I really tried to narrow down the possible reason and also did a lot
of research but still can not put my finger on anything.

-Oddly the first thing I noticed is, that mate is now missing
the menu entry to shut down my computer.

-Also every time I login mate takes ages to show up.
-Then I got the background first and the panels take some
extra time.

-The whole system needs more time to boot than my old debian.
(Was really fast in the beginning)

Maybe someone has experienced the same problem and can help me out.

For information:
I am using LightDM and MATE (both recent versions)

Thanks a lot

Last edited by kanarok (2015-05-19 21:04:37)

mouseman · 2015-05-13 09:05:35

For someone who claims to have done a lot of research you post stunningly little detail.

Post the output of:

$ systemd-analyze blame

and:

$ systemd-analyze critical-chain

Browse through

$ journalctl -b

and look for obvious errors, warnings, suspicious jumps in timestamps and use the output of blame and critical chain to look up specific unit logging.

Also, you should be able to compare to previous bootlogs (-b1, -b2, etc).

For your missing menu item, have you tried to clear MATE config from your home directory? You could create a new user and login with it to see if some of your problems disappear.

thoffmeyer · 2015-05-16 03:56:56

To add on to mouseman's post, with your recent update, was there a kernel update, video drivers, mate, xorg etc? You're thread is very vague and without more details, we really aren't going to do much for you.

kanarok · 2015-05-18 20:01:24

Hi,

thanks a lot for your replies.

My apologies for the vague post.
I can not really remember, which package I updated
before this happened. I definately did a complete update
a couple of days ago. (And another -Syu today)
Also this one of my first two posts considering Linux related problems.

Your supplied commands made me think there is something up with udisks2.
So I will do some investigation.

Output of systemd-analyze blame:

25.086s udisks2.service
2.557s man-db.service
2.241s netctl@wifi_hammertime.service
1.801s systemd-cryptsetup@cryptodisk.service
651ms dev-mapper-root.device
309ms rtkit-daemon.service
238ms lvm2-pvscan@254:1.service
224ms home-dfly-rootfs.mount
205ms home-dfly-Code.mount
171ms systemd-vconsole-setup.service
159ms systemd-journal-flush.service
129ms lightdm.service
128ms systemd-modules-load.service
123ms systemd-journald.service
122ms alsa-restore.service
117ms systemd-logind.service
115ms systemd-user-sessions.service
114ms systemd-remount-fs.service
92ms systemd-udev-trigger.service
55ms var.mount
55ms mnt-harddisk.mount
49ms dev-hugepages.mount
48ms systemd-udevd.service
46ms dev-mqueue.mount
46ms dev-mqueue.mount
45ms tmp.mount
42ms home.mount
40ms shadow.service
39ms kmod-static-nodes.service
36ms sys-kernel-debug.mount
33ms logrotate.service
22ms boot.mount
21ms systemd-sysctl.service
21ms user@1000.service
20ms systemd-fsck@dev-sda1.service
19ms user@620.service
14ms systemd-tmpfiles-setup.service
14ms systemd-tmpfiles-setup-dev.service
12ms upower.service
10ms systemd-tmpfiles-clean.service
9ms systemd-update-utmp.service
8ms sys-kernel-config.mount
7ms polkit.service
7ms systemd-rfkill@rfkill0.service
6ms sys-fs-fuse-connections.mount
3ms udisks.service
2ms systemd-rfkill@rfkill1.service
1ms colord.service
1ms systemd-random-seed.service

Output of systemd-analyze critical-chain

graphical.target @5.725s
└─multi-user.target @5.725s
└─distccd.service @5.725s
└─network.target @5.717s
└─netctl@wifi_hammertime.service @3.475s +2.241s
└─basic.target @3.474s
└─sockets.target @3.471s
└─dbus.socket @3.471s
└─sysinit.target @3.466s
└─systemd-update-utmp.service @3.456s +9ms
└─var.mount @713ms +55ms
└─dev-mapper-root.device @61ms +651ms

mouseman · 2015-05-18 20:05:35

Pacman log should go back at least a couple of days. Search /var/log/pacman.log for a lead to which packages have updated at the time before you posted.

jasonwryan · 2015-05-18 20:53:06

Not a Sysadmin issue, moving to NC...

kanarok · 2015-05-18 21:13:08

Thanks a lot for your help.

5 minutes ago I fell over an Bugtracker issue,
which was related to one of my error messages.

The solution was a simple reinstall of polkit and a reboot.

Now anything is almost as it has been.

mouseman · 2015-05-18 21:48:38

Excellent. Don't forget to edit the title and mark it solved.

Arch Linux

#1 2015-04-27 21:52:02

[SOLVED] MATE really slow after update.

#2 2015-05-13 09:05:35

Re: [SOLVED] MATE really slow after update.

#3 2015-05-16 03:56:56

Re: [SOLVED] MATE really slow after update.

#4 2015-05-18 20:01:24

Re: [SOLVED] MATE really slow after update.

#5 2015-05-18 20:05:35

Re: [SOLVED] MATE really slow after update.

#6 2015-05-18 20:53:06

Re: [SOLVED] MATE really slow after update.

#7 2015-05-18 21:13:08

Re: [SOLVED] MATE really slow after update.

#8 2015-05-18 21:48:38

Re: [SOLVED] MATE really slow after update.

Board footer