A few days ago I noticed that after I login in, the top panel and the dash took a bit more time to load and I noticed more disc activity than usual.

I thought that it might have been caused by some update or by the installation of pdftk. So I removed pdftk but the "problem" persists.

Is there a way to know what is using the disc (read/write operations) on startup?

If it were at a later time, I would use iotop but I can only launch iotop after I get control of the desktop.

I'm on Ubuntu 12.10 amd64.


I took a look at the logs and in the Xorg.0.log file I found the following lines:

[    36.230] (II) XKB: reuse xkmfile /var/lib/xkb/server-ED81635D9DABCAA502951B920776FB5895D92DC0.xkm
[  6683.340] (II) XKB: generating xkmfile /var/lib/xkb/server-7111F82C412662D491D0F0A3A5A74C8F62B59F29.xkm

Could this be the problematic step?

  • 1
    It seems this is a reoccurring question now that Ubuntu has become stable enough where people are updating from older LTS versions, or trying different desktop environments. We need a more elegant way to manage this without being a guru, or spending an hour looking at log files.
    – Goddard
    Dec 10, 2012 at 17:21

5 Answers 5


This is the same problem i "WAS" facing but solved it, seems like a startup application was causing that problem.

Ok here is what i did -

sudo sed -i 's/NoDisplay=true/NoDisplay=false/g' /etc/xdg/autostart/*.desktop

open startup application then uncheck - DISK NOTIFICATION (The Disk Utility notification is used to report disk failures using the SMART predictive technology). It explains your quote also

I noticed more disc activity than usual

if u like u can also shutoff (it depends on your needs) -

AT-SPI D-BUS BUS, Backup Monitor, Check for new hardware drivers, Desktop Sharing, Onboard, Ocra Screen Reader, Personal file sharing,

Before unity was taking near approx. about 20 seconds to load now it takes 3 seconds roughly.

  • How would you "shutoff" the services you mentioned? They are not in the Startup applications list. Neither is Disk notification.
    – To Do
    Dec 10, 2012 at 10:12
  • 1
    the one liner i mentioned will make hidden startup item show in STARTUP APPLICATION. Open Startup application from shutdown menu or simply type gnome-session-properties in terminal and u will understand everything afterwards Dec 10, 2012 at 10:25
  • 1
    There is no disk notification in my list.
    – To Do
    Dec 10, 2012 at 15:44
  • 1
    Try disabling anything that is not important you can take help of this to do so, restart the machine and see if anything helps. Some disk action or perhaps some network activity at login is behind this slowdown thats for sure so turning them off during startup is the best option i guess. The trick is to find it. Dec 10, 2012 at 20:23
  • 1
    @Aquarius Power The idea is not to search for disknotification. Pick any suspecious startup activity. Turn it off and see if it works. And please before you turn off any startup item please google it and learn what it does. Dec 27, 2014 at 17:05

What I would do for that is to open a console (or two) while the system starts with Ctrl+Alt+F1/F2 then use top in conjunction with iostat -x (from sysstat package) to determine what's happen.

Other useful tools you may need some time for that kind of problem are those from inotify-tools package : inotifywait and inotifywatch which permits to monitor files accesses.


Careful scrutiny of the logs should yield some information. While it might seem a bit tedious the logs can reveal some very interesting information about the machine as it is booting. For example the kernel log (/var/log/kern.log) gives a blow-by-blow description of what is happened timed down to the closest millisecond.

If kern.log doesn't reveal any useful information, try syslog and even authlog. You are looking for anything unusual such as error messages or something that gets repeated or retried many times. Most of the logs are time stamped to the millisecond, which can be really useful if you can synchronize real world problems with system time.

Try running "log file viewer" and using that as an assistant. It helps a bit by putting all available logs in front of you, and giving you the ability to only look at todays logs.

  • since the slowing down is after I log in, Which logs should I look at and is there anything particular to watch out for?
    – To Do
    Dec 8, 2012 at 9:36
  • I've added a bit more information to the answer. Dec 8, 2012 at 9:58
  • Is there a tool that visualize boot log? There are such tools for windows and they allow anyone troubleshoot such issues with ease!
    – Bucic
    Dec 10, 2012 at 10:24
  • Yes, it's called log file viewer. If you want a log file analyser, there's none that I know of. Dec 10, 2012 at 10:31

Have you ever logged in to a gnome classic session? There is a bug in compiz which causes it to start extremely slowly if you do that even once and then go back to using unity:


The workaround is to edit ~/.config-bad1/compiz-1/compizconfig/config and delete the following lines:

profile =

You could try choosing "Advanced Options for Ubuntu" In the boot loader, choose the recovery mode and It should show some information. Sometimes you have to be quick reading it

  • 2
    "Advanced Options" simply allows you to select which kernel to boot. It doesn't help find out what is actually being done during the boot operation. Dec 8, 2012 at 9:03
  • Ok because when my computer had a similar problem I used Advanced options I selected the recovery mode. Sorry I forgot to add that which i should of. It shows some information that way.
    – goeagles5
    Dec 8, 2012 at 14:40

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .