[opensuse-gnome] Profiling Login? & .xsession-errors
Logging into openSUSE 12.2 x86_64 GNOME 3.6 can be a bit slow. The hard-drive activity light is on solid for quite some time. Is is possible to somehow profile login? To record that is happening and some estimate of how long it takes? Also, related, the .xsession-errors log file doesn't contain any timestamps. That makes it difficult to go back and relate a message to an event. Is there any way to enable timestamps in .xsession-error messages? -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-gnome+owner@opensuse.org
Quoting Adam Tauno Williams <awilliam@whitemice.org>:
Logging into openSUSE 12.2 x86_64 GNOME 3.6 can be a bit slow. The hard-drive activity light is on solid for quite some time.
Seen similar things but had no time to dig into this yet :(
Also, related, the .xsession-errors log file doesn't contain any timestamps. That makes it difficult to go back and relate a message to an event. Is there any way to enable timestamps in .xsession-error messages?
This part is a long standing feature request: https://bugzilla.gnome.org/show_bug.cgi?id=516879 Dominique -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-gnome+owner@opensuse.org
On Tue, 2012-10-23 at 08:25 -0400, Adam Tauno Williams wrote:
Logging into openSUSE 12.2 x86_64 GNOME 3.6 can be a bit slow. The hard-drive activity light is on solid for quite some time. I might have stumbled onto something interesting.
I recently had a log-in that took significantly longer than usual, so I decided to check my gdm logs to see if anything was suspicious. I found this repeated many times over in the log: The XKEYBOARD keymap compiler (xkbcomp) reports:
Warning: Compat map for group 2 redefined Using new definition Warning: Compat map for group 3 redefined Using new definition Warning: Compat map for group 4 redefined Using new definition Errors from xkbcomp are not fatal to the X server
(Can someone smart shed some light on that?) Now maybe I'm crazy, but the time it takes me to log in seems to be related to the length of the log, i.e. the number of times that error message was repeated in the log. After restarting my computer, my next log-in went much faster, and checking the gdm logs shows that error message far fewer times. Note :0.log.1 corresponds to the particularly long log-in, the log is 6x bigger than usual, and the only difference I noticed was the above error message is printed many many more times in the bigger log. suse-envy:/var/log/gdm # ls -hal total 2.1M drwxrwx--T 2 root gdm 4.0K Oct 28 21:02 . drwxr-xr-x 15 root root 4.0K Oct 28 21:02 .. -rw-r--r-- 1 root gdm 1.9K Oct 28 21:03 :0-greeter.log -rw-r--r-- 1 root gdm 2.8K Oct 28 20:51 :0-greeter.log.1 -rw-r--r-- 1 root gdm 1.7K Oct 28 20:37 :0-greeter.log.2 -rw-r--r-- 1 root gdm 1.7K Oct 28 16:34 :0-greeter.log.3 -rw-r--r-- 1 root gdm 1.2K Oct 28 14:50 :0-greeter.log.4 -rw-r--r-- 1 root root 30K Oct 28 21:03 :0.log -rw-r--r-- 1 root root 175K Oct 28 21:01 :0.log.1 -rw-r--r-- 1 root root 30K Oct 28 20:49 :0.log.2 -rw-r--r-- 1 root root 55K Oct 28 20:36 :0.log.3 -rw-r--r-- 1 root root 30K Oct 28 16:32 :0.log.4 -rw-r--r-- 1 root root 401 Oct 28 21:03 :0-slave.log -rw-r--r-- 1 root root 689 Oct 28 21:01 :0-slave.log.1 -rw-r--r-- 1 root root 689 Oct 28 20:49 :0-slave.log.2 -rw-r--r-- 1 root root 742 Oct 28 20:36 :0-slave.log.3 -rw-r--r-- 1 root root 689 Oct 28 16:32 :0-slave.log.4 <snip> Could this error be our culprit? I'd guess so, but maybe something else causing the log-in to go slow and the slower log-in results in the error being printed more? Michael
participants (3)
-
Adam Tauno Williams -
Dominique Leuenberger a.k.a DimStar -
Michael Catanzaro