Slow initialization of something during boot

[Frank McCormick]

Since I made the switch to a 64 bit machine (still using 32 bit Fedora 
19) there is a long delay just before lightdm comes up with the login 
screen.
Can someone take a look at this output and perhaps point out why and
where it's occurring ? By the way I don't use LVM or raid...can I disable
these services? What;s the best way to do that. Even so the time they 
take doesn't account for the 6-7 second delay after booting before 
lightdm comes up.

Thanks for any help


[frank@localhost ~]$ sudo systemd-analyze blame
          19.698s NetworkManager.service
          19.597s accounts-daemon.service
          18.723s chronyd.service
          18.567s lightdm.service
           2.406s lvm2-monitor.service
           2.317s dmraid-activation.service
           1.487s systemd-udev-settle.service
           1.467s systemd-tmpfiles-setup-dev.service
           1.152s fedora-loadmodules.service
           1.074s systemd-fsck-root.service
            706ms polkit.service
            656ms systemd-sysctl.service
            581ms fedora-readonly.service
            537ms systemd-logind.service
            510ms sys-kernel-debug.mount
            508ms dev-mqueue.mount
            508ms rtkit-daemon.service
            505ms dev-hugepages.mount
            500ms media-debian.mount
            485ms tmp.mount
            353ms systemd-udev-trigger.service
            294ms plymouth-start.service
            265ms systemd-readahead-replay.service
            243ms lvm2-lvmetad.service
            216ms systemd-random-seed-load.service
            165ms sys-kernel-config.mount
            156ms systemd-readahead-collect.service
            152ms systemd-remount-fs.service
            138ms systemd-tmpfiles-setup.service
             89ms plymouth-read-write.service
             88ms plymouth-quit.service
             86ms plymouth-quit-wait.service
             70ms systemd-udevd.service
             34ms systemd-user-sessions.service
             32ms livesys.service
             27ms home-frank-external.mount
             25ms livesys-late.service
             21ms systemd-vconsole-setup.service
             13ms auditd.service
             10ms systemd-journal-flush.service
              3ms rpcbind.service
              3ms systemd-update-utmp-runlevel.service
              1ms systemd-readahead-done.service

[Frank McCormick]

On 08/13/2013 01:24 PM, poma wrote:
>  On 13.08.2013 18:49, Frank wrote:
> > Since I made the switch to a 64 bit machine (still using 32 bit Fedora
> > 19) there is a long delay just before lightdm comes up with the login
> > screen. 
///snip///

> >
> > [frank@localhost ~]$ sudo systemd-analyze blame
> >           19.698s NetworkManager.service
> >           19.597s accounts-daemon.service
> >           18.723s chronyd.service
> >           18.567s lightdm.service
>  …
>
>              638ms NetworkManager.service
>              135ms avahi-daemon.service
>              127ms lightdm.service
>  …
>  - lightdm 1.7.4
>  - lightdm-gtk 1.6.0 

     I have lightdm 1.6.0
            lightdm-gtk 1.5.1-3
YUM says they are the latest

>  alternatives --display lightdm-greeter 
Tells me its ok.
>  grep -v '^#\|^$\|^\[' /etc/lightdm/lightdm.conf
minimum-vt=1
user-authority-in-system-dir=true
xserver-command=X -background none
greeter-session=lightdm-greeter
session-wrapper=/etc/X11/xinit/Xsession


>  cat /var/log/lightdm/lightdm.log 
[+0.01s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.01s] DEBUG: Starting Light Display Manager 1.6.0, UID=0 PID=296
[+0.01s] DEBUG: Loaded configuration from /etc/lightdm/lightdm.conf
[+0.01s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: Registered seat module xlocal
[+0.01s] DEBUG: Registered seat module xremote
[+0.01s] DEBUG: Adding default seat
[+0.01s] DEBUG: Starting seat
[+0.01s] DEBUG: Starting new display for greeter
[+0.01s] DEBUG: Starting local X display
[+0.01s] DEBUG: Using VT 1
[+0.01s] DEBUG: Logging to /var/log/lightdm/x-0.log
[+0.03s] DEBUG: Writing X server authority to /var/run/lightdm/root/:0
[+0.03s] DEBUG: Launching X Server
[+0.03s] DEBUG: Launching process 306: /usr/bin/X -background none :0 
-auth /var/run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch
[+0.03s] DEBUG: Waiting for ready signal from X server :0
[+0.94s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.94s] DEBUG: Registering seat with bus path 
/org/freedesktop/DisplayManager/Seat0
[+1.39s] DEBUG: Got signal 10 from process 306
[+1.39s] DEBUG: Got signal from X server :0
[+1.39s] DEBUG: Connecting to XServer :0
[+1.39s] DEBUG: Starting greeter
[+1.39s] DEBUG: Started session 315 with service 'lightdm-greeter', 
username 'lightdm'

What is going on here ???

[+18.87s] DEBUG: Session 315 authentication complete with return value 
0: Success
[+18.87s] DEBUG: Greeter authorized
[+18.87s] DEBUG: Logging to /var/log/lightdm/x-0-greeter.log
[+18.87s] DEBUG: Session 315 running command /usr/sbin/lightdm-gtk-greeter
[+19.18s] DEBUG: Greeter connected version=1.6.0
[+19.18s] DEBUG: Greeter connected, display is ready
[+19.18s] DEBUG: New display ready, switching to it
[+19.18s] DEBUG: Activating VT 1
[+19.89s] DEBUG: Greeter start authentication for frank
[+19.89s] DEBUG: Started session 365 with service 'lightdm', username 
'frank'
[+19.91s] DEBUG: Session 365 got 1 message(s) from PAM
[+19.91s] DEBUG: Prompt greeter with 1 message(s)
[+30.51s] DEBUG: Continue authentication
[+30.56s] DEBUG: Session 365 authentication complete with return value 
0: Success
[+30.56s] DEBUG: Authenticate result for user frank: Success
[+30.57s] DEBUG: User frank authorized
[+30.62s] DEBUG: Greeter requests session icewm
[+30.62s] DEBUG: Using session icewm
[+30.62s] DEBUG: Stopping greeter
[+30.62s] DEBUG: Session 315: Sending SIGTERM
[+30.62s] DEBUG: Greeter closed communication channel
[+30.62s] DEBUG: Session 315 exited with return value 0
[+30.62s] DEBUG: Greeter quit
[+30.64s] DEBUG: Dropping privileges to uid 1000
[+30.64s] DEBUG: Calling setresgid
[+30.64s] DEBUG: Calling setresuid
[+30.64s] DEBUG: Restoring privileges
[+30.64s] DEBUG: Calling setresuid
[+30.64s] DEBUG: Calling setresgid
[+30.65s] DEBUG: Starting session icewm as user frank
[+30.65s] DEBUG: Session 365 running command /etc/X11/xinit/Xsession 
icewm-session
[+30.72s] DEBUG: Registering session with bus path 
/org/freedesktop/DisplayManager/Session0



>  grep -v ^$ /var/log/lightdm/x-0-greeter.log 
** (process:315):
WARNING **: Failed to open CK session: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.ConsoleKit was not provided by any .service files
** (lightdm-gtk-greeter:334): WARNING **: Failed to load user image: 
Failed to open file '/home/frank/.face': No such file or directory
** (lightdm-gtk-greeter:334): WARNING **: Could not get accounts 
property XKeyboardLayouts
** (lightdm-gtk-greeter:334): WARNING **: Could not get accounts 
property XHasMessages
(lightdm-gtk-greeter:334): GLib-CRITICAL **: g_variant_get_type: 
assertion `value != NULL' failed
(lightdm-gtk-greeter:334): GLib-CRITICAL **: 
g_variant_type_is_subtype_of: assertion `g_variant_type_check (type)' failed
(lightdm-gtk-greeter:334): GLib-CRITICAL **: g_variant_get_type_string: 
assertion `value != NULL' failed
** (lightdm-gtk-greeter:334): WARNING **: Unexpected accounts property 
type for XHasMessages: (null)
(lightdm-gtk-greeter:334): GLib-CRITICAL **: g_variant_unref: assertion 
`value != NULL' failed
** (lightdm-gtk-greeter:334): WARNING **: Could not get accounts 
property XKeyboardLayouts
** (lightdm-gtk-greeter:334): WARNING **: Could not get accounts 
property XHasMessages
(lightdm-gtk-greeter:334): GLib-CRITICAL **: g_variant_get_type: 
assertion `value != NULL' failed
(lightdm-gtk-greeter:334): GLib-CRITICAL **: 
g_variant_type_is_subtype_of: assertion `g_variant_type_check (type)' failed
(lightdm-gtk-greeter:334): GLib-CRITICAL **: g_variant_get_type_string: 
assertion `value != NULL' failed
** (lightdm-gtk-greeter:334): WARNING **: Unexpected accounts property 
type for XHasMessages: (null)
(lightdm-gtk-greeter:334): GLib-CRITICAL **: g_variant_unref: assertion 
`value != NULL' failed

>  /boot/extlinux/extlinux.conf 
No such file

>  append … rd.dm=0 rd.luks=0 rd.lvm=0 rd.md=0
>
>  /boot/grub2/grub.cfg
>  linux …	rd.dm=0 rd.luks=0 rd.lvm=0 rd.md=0 
   Parameters already there


>  man 7 dracut.cmdline 
Didn't understand very much ( I'm a refugee from Debian)
>  man 1 systemctl
>  
   That I sort of understood :)

  Any comments...other than why lightdm starting session 315 takes 17 
seconds before it returns ??
I am used to seeing similar GTK errors in my .xsessions log.
Much of this is beyond me.

>  poma
>
>

[poma]

…
>  
>  5th:
>  cp /usr/lib/systemd/system/lightdm.service /etc/systemd/system
>  - add 10s delay in
>  /etc/systemd/system/lightdm.service
>  i.e.
>  …
>  [Service]
>  ExecStartPre=/usr/bin/sleep 10
>  ExecStart=/usr/sbin/lightdm
>  …
>  
>  - enable it
>  i.e.
>  systemctl enable lightdm.service --force
>  
>  
>  If it works, and those 10s show as the only delay, you can try to lower
>  the value of it.
>   
I've managed to produce a lag via NetworkManager disabled,

systemctl status NetworkManager
NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled)
   Active: inactive (dead)

These are the results of the application of the 'ExecStartPre' directive
in the 'lightdm.service'

====================================================
- default - no sleep
----------------------------------------------------
systemd-analyze blame
…
         30.903s lightdm.service
…
----------------------------------------------------
/var/log/lightdm/lightdm.log
…
[+0.04s] DEBUG: Launching X Server
…
[+30.87s] DEBUG: Greeter connected, display is ready
[+30.87s] DEBUG: New display ready, switching to it
[+30.87s] DEBUG: Activating VT 1
…
====================================================
- 10s sleep
/etc/systemd/system/lightdm.service
…
ExecStartPre=/usr/bin/sleep 10
…
----------------------------------------------------
systemd-analyze blame
…
         10.058s lightdm.service
…
----------------------------------------------------
/var/log/lightdm/lightdm.log
…
[+0.04s] DEBUG: Launching X Server
…
[+1.23s] DEBUG: Greeter connected, display is ready
[+1.23s] DEBUG: New display ready, switching to it
[+1.23s] DEBUG: Activating VT 1
…
====================================================
- 2s sleep
/etc/systemd/system/lightdm.service
…
ExecStartPre=/usr/bin/sleep 2
…
----------------------------------------------------
systemd-analyze blame
…
          2.146s lightdm.service
…
----------------------------------------------------
/var/log/lightdm/lightdm.log
…
[+0.12s] DEBUG: Launching X Server
…
[+2.88s] DEBUG: Greeter connected, display is ready
[+2.88s] DEBUG: New display ready, switching to it
[+2.88s] DEBUG: Activating VT 1
…
====================================================


poma

[Frank McCormick]

On 08/15/2013 08:46 PM, poma wrote:
>  On 15.08.2013 20:10, Frank wrote:
>
> >     With all due respect, I don't understand what's going on here---my
> > network manager is not disabled. What effect does adding sleep to
> > lightdm.service produce ?? I think I am missing the point :)
> >
> > Regards
> >
> >
> > Frank
>
>  It is a famous the dodge by braking maneuver. ;)
>
>
>  poma
>
>  

   Well in this case it didn't work - I tried adding 10 sec sleep...5 
sec sleep and 2 sec sleep...same 20-25 sec delay before lightdm greeter 
appears. Maybe I'll go back to lxdm..or learn patience :)

Regards


Frank

[poma]

>  
>  Looks like you're not as skilled as Maverick. ;)
>   
Neither am I. :)
Bummer!


poma

[poma]

On 16.08.2013 06:36, Roger wrote:
>  <snip>
>       Didn't work - put me into Vesa mode I guess but the delay remains
>  </snip>
>  None of those worked for me either
>  Roger 
Now you have more than enough informations for a solid bug report.
- upstream:
  https://bugs.launchpad.net/lightdm
- downstream:
  https://bugzilla.redhat.com/
- ml:
  http://lists.freedesktop.org/mailman/listinfo/lightdm
- master chief:
  Robert Ancell


poma

[Frank McCormick]

On 08/14/2013 10:33 AM, T.C. Hollingsworth wrote:
>  On Tue, Aug 13, 2013 at 10:51 AM, আনন্দ কুমার সমাদ্দার
>  <asamaddar(a)myopera.com&gt; wrote:
> > Can you not use bootchart to visualise this and find the culprit?
>
>  To expand upon this, just add the following to your kernel command
>  line before booting:
>
>  init=/usr/lib/systemd/systemd-bootchart
>
>  Then, after you system has booted, check /run/log for a pretty SVG
>  file that should indicate exactly where your system is getting stuck.
>
>  For more info, see:
>  http://www.freedesktop.org/software/systemd/man/systemd-bootchart.html
>
>  -T.C.
>  

   In my continuing attempts to track down slow loading of lightdm....I 
tried bootchart from the kernel command line. The problem is it hard 
locks-up lightdm when its loaded. Next boot I find nothing in /run/log. 
I tried changing the output directory to $HOME...still nothing there.
Any bootchart experts here ??

Regards


Frank

[Frank McCormick]

On 08/15/2013 01:58 PM, poma wrote:
>  …
> >
> > 5th:
> > cp /usr/lib/systemd/system/lightdm.service /etc/systemd/system
> > - add 10s delay in
> > /etc/systemd/system/lightdm.service
> > i.e.
> > …
> > [Service]
> > ExecStartPre=/usr/bin/sleep 10
> > ExecStart=/usr/sbin/lightdm
> > …
> >
> > - enable it
> > i.e.
> > systemctl enable lightdm.service --force
> >
> >
> > If it works, and those 10s show as the only delay, you can try to lower
> > the value of it.
> >
>
>  I've managed to produce a lag via NetworkManager disabled,
>
>  systemctl status NetworkManager
>  NetworkManager.service - Network Manager
>      Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled)
>      Active: inactive (dead)
>
>  These are the results of the application of the 'ExecStartPre' directive
>  in the 'lightdm.service'
>
>  ====================================================
>  - default - no sleep
>  ----------------------------------------------------
>  systemd-analyze blame
>  …
>            30.903s lightdm.service
>  …
>  ----------------------------------------------------
>  /var/log/lightdm/lightdm.log
>  …
>  [+0.04s] DEBUG: Launching X Server
>  …
>  [+30.87s] DEBUG: Greeter connected, display is ready
>  [+30.87s] DEBUG: New display ready, switching to it
>  [+30.87s] DEBUG: Activating VT 1
>  …
>  ====================================================
>  - 10s sleep
>  /etc/systemd/system/lightdm.service
>  …
>  ExecStartPre=/usr/bin/sleep 10
>  …
>  ----------------------------------------------------
>  systemd-analyze blame
>  …
>            10.058s lightdm.service
>  …
>  ----------------------------------------------------
>  /var/log/lightdm/lightdm.log
>  …
>  [+0.04s] DEBUG: Launching X Server
>  …
>  [+1.23s] DEBUG: Greeter connected, display is ready
>  [+1.23s] DEBUG: New display ready, switching to it
>  [+1.23s] DEBUG: Activating VT 1
>  …
>  ====================================================
>  - 2s sleep
>  /etc/systemd/system/lightdm.service
>  …
>  ExecStartPre=/usr/bin/sleep 2
>  …
>  ----------------------------------------------------
>  systemd-analyze blame
>  …
>             2.146s lightdm.service
>  …
>  ----------------------------------------------------
>  /var/log/lightdm/lightdm.log
>  …
>  [+0.12s] DEBUG: Launching X Server
>  …
>  [+2.88s] DEBUG: Greeter connected, display is ready
>  [+2.88s] DEBUG: New display ready, switching to it
>  [+2.88s] DEBUG: Activating VT 1
>  …
>  ==================================================== 


    With all due respect, I don't understand what's going on here---my 
network manager is not disabled. What effect does adding sleep to
lightdm.service produce ?? I think I am missing the point :)

Regards


Frank

[Frank McCormick]

On 08/15/2013 04:19 AM, poma wrote:
>  On 15.08.2013 01:53, Frank wrote:
> > On 08/14/2013 07:02 PM, poma wrote:
> >>
> >>> To opt out of the equation an Xorg driver for Intel integrated graphics
> >>> chipsets - man 4 intel, you can try the following:
> >>>
> >>> /boot/grub2/grub.cfg
> >>> linux …    nomodeset
> >
> >
> >      Didn't work - put me into Vesa mode I guess but the delay remains
> >
> >>>
> >>
> >> For further testing, you can also try the following:
> >>
> >> systemctl mask accounts-daemon.service
> >
> >
> >     Ditto. Delay remains
> >>
> >> And of course, perform tests gradually s'il vous plaît, so can be seen
> >> where the bunny is - 1st intel, 2nd accountsservice, …
> >
> >
> >     You must be running out of ideas by now :)
> >
> > Regards
> >
> > Frank
> >
>
>  :)
>
>  3rd:
>  - without "-background none" in
>  /etc/lightdm/lightdm.conf
>  i.e.
>  xserver-command=X
>
>  - comment all directives in
>  /etc/lightdm/lightdm-gtk-greeter.conf
>  i.e.
>  # background=…
>  # theme-name=…
>  # icon-theme-name=…
>  # font-name=…
>  etc.
>
>
>  4th:
>  - remove "rhgb quiet" and
>  - add "plymouth.enable=0" in
>  /boot/grub2/grub.cfg
>  i.e.
>  linux …	plymouth.enable=0
>  


   Up to here nothing worked.

>  5th:
>  cp /usr/lib/systemd/system/lightdm.service /etc/systemd/system
>  - add 10s delay in
>  /etc/systemd/system/lightdm.service
>  i.e.
>  …
>  [Service]
>  ExecStartPre=/usr/bin/sleep 10
>  ExecStart=/usr/sbin/lightdm
>  …
>
>  - enable it
>  i.e.
>  systemctl enable lightdm.service --force
>  

    Haven't done these yet.


>  If it works, and those 10s show as the only delay, you can try to lower
>  the value of it. 

Regards

Frank

[Roger]

<snip>
      Didn't work - put me into Vesa mode I guess but the delay remains
</snip>
None of those worked for me either
Roger

[poma]

On 16.08.2013 02:55, Frank wrote:
>  On 08/15/2013 08:46 PM, poma wrote:
> > On 15.08.2013 20:10, Frank wrote:
> >
> >>     With all due respect, I don't understand what's going on here---my
> >> network manager is not disabled. What effect does adding sleep to
> >> lightdm.service produce ?? I think I am missing the point :)
> >>
> >> Regards
> >>
> >>
> >> Frank
> >
> > It is a famous the dodge by braking maneuver. ;)
> >
> >
> > poma
> >
> >
>  
>  
>    Well in this case it didn't work - I tried adding 10 sec sleep...5 sec
>  sleep and 2 sec sleep...same 20-25 sec delay before lightdm greeter
>  appears. Maybe I'll go back to lxdm..or learn patience :)
>  
>  Regards
>  
>  
>  Frank 

Looks like you're not as skilled as Maverick. ;)

https://bugs.launchpad.net/lightdm


poma

[poma]

On 15.08.2013 20:10, Frank wrote:

>     With all due respect, I don't understand what's going on
> here---my
>  network manager is not disabled. What effect does adding sleep to
>  lightdm.service produce ?? I think I am missing the point :)
>  
>  Regards
>  
>  
>  Frank 
It is a famous the dodge by braking maneuver. ;)


poma

[poma]

On 15.08.2013 01:53, Frank wrote:
>  On 08/14/2013 07:02 PM, poma wrote:
> >
> >> To opt out of the equation an Xorg driver for Intel integrated graphics
> >> chipsets - man 4 intel, you can try the following:
> >>
> >> /boot/grub2/grub.cfg
> >> linux …    nomodeset
>  
>  
>      Didn't work - put me into Vesa mode I guess but the delay remains
>  
> >>
> >
> > For further testing, you can also try the following:
> >
> > systemctl mask accounts-daemon.service
>  
>  
>     Ditto. Delay remains
> >
> > And of course, perform tests gradually s'il vous plaît, so can be seen
> > where the bunny is - 1st intel, 2nd accountsservice, …
>  
>  
>     You must be running out of ideas by now :)
>  
>  Regards
>  
>  Frank
>   
:)

3rd:
- without "-background none" in
/etc/lightdm/lightdm.conf
i.e.
xserver-command=X

- comment all directives in
/etc/lightdm/lightdm-gtk-greeter.conf
i.e.
# background=…
# theme-name=…
# icon-theme-name=…
# font-name=…
etc.


4th:
- remove "rhgb quiet" and
- add "plymouth.enable=0" in
/boot/grub2/grub.cfg
i.e.
linux …	plymouth.enable=0


5th:
cp /usr/lib/systemd/system/lightdm.service /etc/systemd/system
- add 10s delay in
/etc/systemd/system/lightdm.service
i.e.
…
[Service]
ExecStartPre=/usr/bin/sleep 10
ExecStart=/usr/sbin/lightdm
…

- enable it
i.e.
systemctl enable lightdm.service --force


If it works, and those 10s show as the only delay, you can try to lower
the value of it.


poma

[Frank McCormick]

On 08/14/2013 08:27 PM, Joe Zeff wrote:
>  On 08/14/2013 04:55 PM, Frank wrote:
> > Only took a minute..but it didn't solve the problem.
>
>  Even cutting down the delay is better than nothing.  After moving from
>  F17 to F19 lightdm had a long delay, both in coming up and in getting to
>  a responsive desktop after login.  (Only on my laptop, however.)  I got
>  this idea from fedorafourm.org, although it came from a bugzilla about
>  F19 being slow coming back from suspend, and just happened to work for me.
>
>  Just a wild idea, but do you have any peripherals attached at boot that
>  might be causing a delay?  If so, see what happens if they're
>  disconnected until after boot. 

   Already tried that...there's a scanner attached via usb and an 
external backup drive...but it gets mounted during the boot and
that happens very quickly. The bizarre thing is I have Debian Jessie
on another partition..almost the identical setup and lightdm comes up 
within a few seconds after boot. And if you've been following along, I 
installed lxdm on Poma's suggestion and it comes up instantly..but I 
don't like the interface. I have even tried lightdm and it's greeter 
from fedora 20...with no change. There is something strange going on.

[Joe Zeff]

On 08/14/2013 04:55 PM, Frank wrote:
>  Only took a minute..but it didn't solve the problem. 
Even cutting down the delay is better than nothing.  After moving from 
F17 to F19 lightdm had a long delay, both in coming up and in getting to 
a responsive desktop after login.  (Only on my laptop, however.)  I got 
this idea from fedorafourm.org, although it came from a bugzilla about 
F19 being slow coming back from suspend, and just happened to work for me.

Just a wild idea, but do you have any peripherals attached at boot that 
might be causing a delay?  If so, see what happens if they're 
disconnected until after boot.

[Frank McCormick]

On 08/14/2013 03:24 PM, Joe Zeff wrote:
>  On 08/14/2013 09:07 AM, Frank wrote:
> >     Re-enabled lightdm, and we are back to a 25 sec delay before it comes
> > up.
> > I really don't know what to do next.I can "solve" my problem by going
> > back to lxdm, but I really prefer the lightdm interface.
>
>  I had a similar issue on my laptop after upgrading to F19.  Try running
>  this as root:
>
>  restorecon -R -v /usr/sbin 

    Done.
>  Then re-enable SELinux and reboot. 

   Done..but I set it to permissive. It was disabled.

  As I recall, there's one file with
>  the wrong context that needs fixing.  If it works, great; if not,
> all
>  that's lost is a little bit of time. 
   Only took a minute..but it didn't solve the problem.


It was worth a try again


Regards


Frank

[Frank McCormick]

On 08/14/2013 07:02 PM, poma wrote:
> > To opt out of the equation an Xorg driver for Intel integrated graphics
> > chipsets - man 4 intel, you can try the following:
> >
> > /boot/grub2/grub.cfg
> > linux …	nomodeset 

     Didn't work - put me into Vesa mode I guess but the delay remains

> >
>
>  For further testing, you can also try the following:
>
>  systemctl mask accounts-daemon.service 

    Ditto. Delay remains
>  And of course, perform tests gradually s'il vous plaît, so can be seen
>  where the bunny is - 1st intel, 2nd accountsservice, … 

    You must be running out of ideas by now :)

Regards

Frank

[poma]

>  To opt out of the equation an Xorg driver for Intel integrated
> graphics
>  chipsets - man 4 intel, you can try the following:
>  
>  /boot/grub2/grub.cfg
>  linux …	nomodeset
>   
For further testing, you can also try the following:

systemctl mask accounts-daemon.service

'lightdm' can work without it.
less /etc/lightdm/users.conf

And of course, perform tests gradually s'il vous plaît, so can be seen
where the bunny is - 1st intel, 2nd accountsservice, …


poma

[poma]

On 14.08.2013 20:49, Frank wrote:
…
>  No change at all - still a long delay. Either I will
>  just put up with it (I like the interface) or  I'll go back to
>  lxdm. If I am still curious in a day or two, I'll run bootchart.
>  Right now I am just frustrated.
>  
>  
>  
>  Thanks Poma
>  
>  
>  Regards
>  
>  Frank
>   
To opt out of the equation an Xorg driver for Intel integrated graphics
chipsets - man 4 intel, you can try the following:

/boot/grub2/grub.cfg
linux …	nomodeset


poma

[Frank McCormick]

On 08/14/2013 11:33 AM, Ahmad Samir wrote:
>  On 13 August 2013 18:49, Frank <beacon(a)videotron.ca
>  <mailto:[e-mail]>> wrote:
>
>      Since I made the switch to a 64 bit machine (still using 32 bit
>      Fedora 19) there is a long delay just before lightdm comes up with
>      the login screen.
>      Can someone take a look at this output and perhaps point out why and
>      where it's occurring ? By the way I don't use LVM or raid...can I
>      disable
>      these services? What;s the best way to do that. Even so the time
>      they take doesn't account for the 6-7 second delay after booting
>      before lightdm comes up.
>
>
>  This could be the same issue discussed in this thread in the forum
>  http://forums.fedoraforum.org/showthread.php?p=1661767
>  [...]
>  

   As a matter of fact that appears to be almost exactly the problem 
here. The only difference is that I have selinux disabled, not set to
permissive.

Installing lxdm has "solved" my problem - the system boots quickly to
the login manager. Now I have to re-enable lightdm to see if the delay 
returns. If so, I'll implement the bootchart as suggested by TC 
Hollingsworth on this list.


Thanks for pointing this out


Regards


Frank

[Frank McCormick]

On 08/14/2013 10:14 AM, poma wrote:
>  On 14.08.2013 15:11, Frank wrote:
> > On 08/14/2013 05:02 AM, poma wrote:
> >> On 14.08.2013 01:13, Frank wrote:
> >> …
> >>> Is this worth submitting a bug ??
> >>
> >> First check whether it's a 'lightdm-gtk-greeter' issue,
> >>
> >> yum install lightdm-razorqt
> >> alternatives --config lightdm-greeter
> >> systemctl restart lightdm
> >
> >
> >    No...it's some other problem. The delay is the same after
> > the QT greeter is installed.
> > If installing GDM didn't pull in megs and megs of gnome
> > stuff I'd try that. But it simply not worth it.
> >
> > Regards
> >
> > Frank
> >
>
>  yum install lxdm
>  systemctl enable lxdm --force
>  systemctl restart lxdm.service 

  Did this. See my other message. Sorry
>  lspci -nnk | grep VGA -A2
>  cat /var/log/Xorg.0.log
>  
   I'll repeat the link

http://pastebin.com/2kumBw0H

There doesn't appear to be any problem with xorg.log.
I will add that there is now NO DELAY getting to lxdm, only a slight 2-3 
sec delay getting to my desktop.
Something is fundamentally different between lightdm and lxdm.


Regards

Frank

[Ahmad Samir]

On 13 August 2013 18:49, Frank <beacon(a)videotron.ca&gt; wrote:

>  Since I made the switch to a 64 bit machine (still using 32 bit
> Fedora 19)
>  there is a long delay just before lightdm comes up with the login screen.
>  Can someone take a look at this output and perhaps point out why and
>  where it's occurring ? By the way I don't use LVM or raid...can I disable
>  these services? What;s the best way to do that. Even so the time they take
>  doesn't account for the 6-7 second delay after booting before lightdm comes
>  up.
>
>  
This could be the same issue discussed in this thread in the forum
http://forums.fedoraforum.org/showthread.php?p=1661767
[...]

-- 
Ahmad Samir

[Frank McCormick]

On 08/14/2013 10:14 AM, poma wrote:
>  lspci -nnk | grep VGA -A2 
[frank@localhost ~]$ lspci -nnk | grep VGA -A2
00:02.0 VGA compatible controller [0300]: Intel Corporation 82Q963/Q965 
Integrated Graphics Controller [8086:2992] (rev 02)
         Subsystem: Dell Device [1028:01da]
         Kernel driver in use: i915
[frank@localhost ~]$


xorg.log


http://pastebin.com/2kumBw0H

[T.C. Hollingsworth]

On Tue, Aug 13, 2013 at 10:51 AM, আনন্দ কুমার সমাদ্দার
<asamaddar(a)myopera.com&gt; wrote:
>  Can you not use bootchart to visualise this and find the culprit?
To expand upon this, just add the following to your kernel command
line before booting:

init=/usr/lib/systemd/systemd-bootchart

Then, after you system has booted, check /run/log for a pretty SVG
file that should indicate exactly where your system is getting stuck.

For more info, see:
http://www.freedesktop.org/software/systemd/man/systemd-bootchart.html

-T.C.

[poma]

On 14.08.2013 15:11, Frank wrote:
>  On 08/14/2013 05:02 AM, poma wrote:
> > On 14.08.2013 01:13, Frank wrote:
> > …
> >> Is this worth submitting a bug ??
> >
> > First check whether it's a 'lightdm-gtk-greeter' issue,
> >
> > yum install lightdm-razorqt
> > alternatives --config lightdm-greeter
> > systemctl restart lightdm
>  
>  
>    No...it's some other problem. The delay is the same after
>  the QT greeter is installed.
>  If installing GDM didn't pull in megs and megs of gnome
>  stuff I'd try that. But it simply not worth it.
>  
>  Regards
>  
>  Frank
>   
yum install lxdm
systemctl enable lxdm --force
systemctl restart lxdm.service

lspci -nnk | grep VGA -A2
cat /var/log/Xorg.0.log


poma

[Frank McCormick]

On 08/14/2013 05:02 AM, poma wrote:
>  On 14.08.2013 01:13, Frank wrote:
>  …
> > Is this worth submitting a bug ??
>
>  First check whether it's a 'lightdm-gtk-greeter' issue,
>
>  yum install lightdm-razorqt
>  alternatives --config lightdm-greeter
>  systemctl restart lightdm 

   No...it's some other problem. The delay is the same after
the QT greeter is installed.
If installing GDM didn't pull in megs and megs of gnome
stuff I'd try that. But it simply not worth it.

Regards

Frank

[Frank McCormick]

On 08/14/2013 02:15 PM, poma wrote:
>  On 14.08.2013 17:35, Frank wrote:
> > On 08/14/2013 10:14 AM, poma wrote:
> >> On 14.08.2013 15:11, Frank wrote:
> >>> On 08/14/2013 05:02 AM, poma wrote:
> >>>> On 14.08.2013 01:13, Frank wrote:
> >>>> …
> >>>>> Is this worth submitting a bug ??
> >>>>
> >>>> First check whether it's a 'lightdm-gtk-greeter' issue,
> >>>>
> >>>> yum install lightdm-razorqt
> >>>> alternatives --config lightdm-greeter
> >>>> systemctl restart lightdm
> >>>
> >>>
> >>>     No...it's some other problem. The delay is the same after
> >>> the QT greeter is installed.
> >>> If installing GDM didn't pull in megs and megs of gnome
> >>> stuff I'd try that. But it simply not worth it.
> >>>
> >>> Regards
> >>>
> >>> Frank
> >>>
> >>
> >> yum install lxdm
> >> systemctl enable lxdm --force
> >> systemctl restart lxdm.service
> >
> >
> >   Did this. See my other message. Sorry
> >>
> >> lspci -nnk | grep VGA -A2
> >> cat /var/log/Xorg.0.log
> >>
> >
> >    I'll repeat the link
> >
> > http://pastebin.com/2kumBw0H
> >
> > There doesn't appear to be any problem with xorg.log.
> > I will add that there is now NO DELAY getting to lxdm, only a slight 2-3
> > sec delay getting to my desktop.
> > Something is fundamentally different between lightdm and lxdm.
> >
> >
> > Regards
> >
> > Frank
> >
>
>  OK.
>  If you're eager to continue with a 'lightdm' you can try the following:
>
>  - before:
>  rpm -qa lightdm\*
>  lightdm-1.6.0-10.fc19.i686
>  lightdm-gobject-1.6.0-10.fc19.i686
>  lightdm-gtk-1.5.1-3.fc19.i686
>
>  - download:
>  http://koji.fedoraproject.org/koji/buildinfo?buildID=455290
>  http://kojipkgs.fedoraproject.org/packages/lightdm/1.7.9/2.fc20/i686/
>  http://koji.fedoraproject.org/koji/buildinfo?buildID=444454
>  http://kojipkgs.fedoraproject.org/packages/lightdm-gtk/1.6.0/1.fc19/i686/
>
>  - install:
>  rpm -Uvh lightdm-1.7.9-2.fc20.i686.rpm \
>  lightdm-gobject-1.7.9-2.fc20.i686.rpm \
>  lightdm-gtk-1.6.0-1.fc19.i686.rpm
>
>  - after:
>  rpm -qa lightdm\*
>  lightdm-1.7.9-2.fc20.i686
>  lightdm-gobject-1.7.9-2.fc20.i686
>  lightdm-gtk-1.6.0-1.fc19.i686
>
>
>  poma
>  

[root@localhost frank]# rpm -qa lightdm\*
lightdm-1.7.9-2.fc20.i686
lightdm-gobject-1.7.9-2.fc20.i686
lightdm-gtk-1.6.0-1.fc19.i686
[root@localhost frank]#

No change at all - still a long delay. Either I will
just put up with it (I like the interface) or  I'll go back to
lxdm. If I am still curious in a day or two, I'll run bootchart.
Right now I am just frustrated.



Thanks Poma


Regards

Frank

[poma]

On 14.08.2013 17:35, Frank wrote:
>  On 08/14/2013 10:14 AM, poma wrote:
> > On 14.08.2013 15:11, Frank wrote:
> >> On 08/14/2013 05:02 AM, poma wrote:
> >>> On 14.08.2013 01:13, Frank wrote:
> >>> …
> >>>> Is this worth submitting a bug ??
> >>>
> >>> First check whether it's a 'lightdm-gtk-greeter' issue,
> >>>
> >>> yum install lightdm-razorqt
> >>> alternatives --config lightdm-greeter
> >>> systemctl restart lightdm
> >>
> >>
> >>    No...it's some other problem. The delay is the same after
> >> the QT greeter is installed.
> >> If installing GDM didn't pull in megs and megs of gnome
> >> stuff I'd try that. But it simply not worth it.
> >>
> >> Regards
> >>
> >> Frank
> >>
> >
> > yum install lxdm
> > systemctl enable lxdm --force
> > systemctl restart lxdm.service
>  
>  
>   Did this. See my other message. Sorry
> >
> > lspci -nnk | grep VGA -A2
> > cat /var/log/Xorg.0.log
> >
>  
>    I'll repeat the link
>  
>  http://pastebin.com/2kumBw0H
>  
>  There doesn't appear to be any problem with xorg.log.
>  I will add that there is now NO DELAY getting to lxdm, only a slight 2-3
>  sec delay getting to my desktop.
>  Something is fundamentally different between lightdm and lxdm.
>  
>  
>  Regards
>  
>  Frank
>   
OK.
If you're eager to continue with a 'lightdm' you can try the following:

- before:
rpm -qa lightdm\*
lightdm-1.6.0-10.fc19.i686
lightdm-gobject-1.6.0-10.fc19.i686
lightdm-gtk-1.5.1-3.fc19.i686

- download:
http://koji.fedoraproject.org/koji/buildinfo?buildID=455290
http://kojipkgs.fedoraproject.org/packages/lightdm/1.7.9/2.fc20/i686/
http://koji.fedoraproject.org/koji/buildinfo?buildID=444454
http://kojipkgs.fedoraproject.org/packages/lightdm-gtk/1.6.0/1.fc19/i686/

- install:
rpm -Uvh lightdm-1.7.9-2.fc20.i686.rpm \
lightdm-gobject-1.7.9-2.fc20.i686.rpm \
lightdm-gtk-1.6.0-1.fc19.i686.rpm

- after:
rpm -qa lightdm\*
lightdm-1.7.9-2.fc20.i686
lightdm-gobject-1.7.9-2.fc20.i686
lightdm-gtk-1.6.0-1.fc19.i686


poma

[poma]

On 14.08.2013 01:13, Frank wrote:
…
>  Is this worth submitting a bug ?? 
First check whether it's a 'lightdm-gtk-greeter' issue,

yum install lightdm-razorqt
alternatives --config lightdm-greeter
systemctl restart lightdm


poma

[Frank McCormick]

On 08/13/2013 10:07 PM, Frank wrote:
>  On 13/08/13 08:40 PM, Roger wrote:
> >
> >> So....32-bit software on a 64-bit CPU sometimes may not be all it's
> >> cracked up to be :)
> >>    Boy, Poma, if you can't figure it out....I doubt anyone here can -
> >> I've been following your various and sundry suggestions to users
> >> closely and you are usually close to, if not on the mark.
> >>
> >> Is this worth submitting a bug ??
> >>
> >>
> >>> I recommend that you begin to sing
> >>> http://www.youtube.com/watch?v=qAzqSYQ9X9U :)
> >>
> > I don't particularly like that version,  been singing it for weeks, on
> > 3  different Fedora 19  64 bit systems, the problem remains, Boot either
> > hangs for 30 seconds or fails completely, stops dead at lightdm.service,
> > have to restart.
> > Nothing in the logs, no hints.
> > Roger
> >
> >
>
>
>     Well at least I am not alone :)  I am writing this on my Debian Sid
>  system because Fedora now won't get past the login. My fault I guess as
>  I thought I'd try SLIM as a login manager. Couldn't get it to take
>  effect, so in a moment of madness I tried "systemctl enable
>  slim.service"...even though I had no indication that's what it needed. I
>  had already changed the /etc/systemcfg/display-manager file to slim but
>  that didn't work. But now I have a system that won't run any login
>  manager. Is it possible I can revert the changes from my Debian system ? 

    Fixed it...sort of. From my Debian install I chroot'ed to 
Fedora...disabled slim.service (which I think doesn't exist), enabled 
lightdm.service and it now is happy again..sort of. I still get a 20-25 
sec delay before lightdm decides it's time to start. I still don't think 
it's a 32 vs 64 bit problem as my Debian install also uses 32=bit 
lightdm on the same 64-bit system and it loads quickly. It's some 
problem which is tied to Fedora. The whole login manager system is 
fubarred as far as I am concerned...as in addition to 
/etc/systemconfig/desktop file, there is the alternatives system. I am 
not sure how that fits in to the mess.

Regards
Frank

[Gregory Hosler]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/14/2013 12:49 AM, Frank wrote:
>  Since I made the switch to a 64 bit machine (still using 32 bit
> Fedora 19)
>  there is a long delay just before lightdm comes up with the login screen. 
>  Can someone take a look at this output and perhaps point out why and where
>  it's occurring ? By the way I don't use LVM or raid...can I disable these
>  services? What;s the best way to do that. Even so the time they take 
>  doesn't account for the 6-7 second delay after booting before lightdm comes
>  up.
>  
>  Thanks for any help
>  
>  
>  [frank@localhost ~]$ sudo systemd-analyze blame 19.698s
>  NetworkManager.service 19.597s accounts-daemon.service 18.723s
>  chronyd.service 18.567s lightdm.service 2.406s lvm2-monitor.service 
NOTE: the time stamp is as the start of the service, not at the end.

so, right here. LVM startup

16 secs for lvm startup is nothing. :-)

How many VG and LV you have ?

I have 32 lv's spread across 3 VG's and 5 GB spread across 3 PV's (one for
each VG).

It takes me between 2 to 3 minutes (about 150 to 180 secs) to do the lvm
initialization.

What I have found to help was to do the LV initialization as part of the
initial boot stage.

On my kernel boot line in grub.conf, I have the following:

	rd.lvm.vg=INSTALLATION rd.lvm.vg=VM rd.lvm.vg=ClassRoom
	rd.lvm.lv=INSTALLATION/F19

The rd.lvm.vg's are my multiple (3) VG's
The rd.lvm.lv is the /

There will STILL be a delay. In my case, the delay is about 3 minutes (as I
noted above). w/o the rd.lvm.vg it would take noticeably longer.

Hope that helps, your mileage may vary.

All the best,

- -Greg

>  2.317s dmraid-activation.service 1.487s systemd-udev-settle.service
> 1.467s
>  systemd-tmpfiles-setup-dev.service 1.152s fedora-loadmodules.service 1.074s
>  systemd-fsck-root.service 706ms polkit.service 656ms
>  systemd-sysctl.service 581ms fedora-readonly.service 537ms
>  systemd-logind.service 510ms sys-kernel-debug.mount 508ms dev-mqueue.mount 
>  508ms rtkit-daemon.service 505ms dev-hugepages.mount 500ms
>  media-debian.mount 485ms tmp.mount 353ms systemd-udev-trigger.service 294ms
>  plymouth-start.service 265ms systemd-readahead-replay.service 243ms
>  lvm2-lvmetad.service 216ms systemd-random-seed-load.service 165ms
>  sys-kernel-config.mount 156ms systemd-readahead-collect.service 152ms
>  systemd-remount-fs.service 138ms systemd-tmpfiles-setup.service 89ms
>  plymouth-read-write.service 88ms plymouth-quit.service 86ms
>  plymouth-quit-wait.service 70ms systemd-udevd.service 34ms
>  systemd-user-sessions.service 32ms livesys.service 27ms
>  home-frank-external.mount 25ms livesys-late.service 21ms
>  systemd-vconsole-setup.service 13ms auditd.service 10ms
>  systemd-journal-flush.service 3ms rpcbind.service 3ms
>  systemd-update-utmp-runlevel.service 1ms systemd-readahead-done.service 

- -- 
+---------------------------------------------------------------------+

Please also check the log file at "/dev/null" for additional information.
                (from /var/log/Xorg.setup.log)

| Greg Hosler                                   ghosler(a)redhat.com    |
+---------------------------------------------------------------------+
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.14 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iEYEARECAAYFAlIK9v0ACgkQ404fl/0CV/QwJgCg4TntRJSFz/G/irI7F0HjVf1O
> u5MAoKmc0DwM7Vw5XLbvKjOdYvEpxwKc
> =btkw
> -----END PGP SIGNATURE-----

[Frank McCormick]

On 13/08/13 08:40 PM, Roger wrote:
> > So....32-bit software on a 64-bit CPU sometimes may not be all it's
> > cracked up to be :)
> >    Boy, Poma, if you can't figure it out....I doubt anyone here can -
> > I've been following your various and sundry suggestions to users
> > closely and you are usually close to, if not on the mark.
> >
> > Is this worth submitting a bug ??
> >
> >
> >> I recommend that you begin to sing
> >> http://www.youtube.com/watch?v=qAzqSYQ9X9U :)
> >
>  I don't particularly like that version,  been singing it for weeks, on
>  3  different Fedora 19  64 bit systems, the problem remains, Boot either
>  hangs for 30 seconds or fails completely, stops dead at lightdm.service,
>  have to restart.
>  Nothing in the logs, no hints.
>  Roger
>
>  

   Well at least I am not alone :)  I am writing this on my Debian Sid
system because Fedora now won't get past the login. My fault I guess as
I thought I'd try SLIM as a login manager. Couldn't get it to take 
effect, so in a moment of madness I tried "systemctl enable 
slim.service"...even though I had no indication that's what it needed. I 
had already changed the /etc/systemcfg/display-manager file to slim but 
that didn't work. But now I have a system that won't run any login
manager. Is it possible I can revert the changes from my Debian system ? 
Fedora is mounted...I'm thinking of chroot..can someone hold my hand
through this ?

Thanks

[Roger]

>  So....32-bit software on a 64-bit CPU sometimes may not be all
> it's 
>  cracked up to be :)
>     Boy, Poma, if you can't figure it out....I doubt anyone here can - 
>  I've been following your various and sundry suggestions to users 
>  closely and you are usually close to, if not on the mark.
>
>  Is this worth submitting a bug ??
>
>
> > I recommend that you begin to sing
> > http://www.youtube.com/watch?v=qAzqSYQ9X9U :)
>  
I don't particularly like that version,  been singing it for weeks, on 
3  different Fedora 19  64 bit systems, the problem remains, Boot either 
hangs for 30 seconds or fails completely, stops dead at lightdm.service, 
have to restart.
Nothing in the logs, no hints.
Roger

[Frank McCormick]

On 08/13/2013 05:28 PM, poma wrote:
>  Dana 13.08.2013 20:00, Frank je napisao:
> > On 08/13/2013 01:24 PM, poma wrote:
> >> On 13.08.2013 18:49, Frank wrote:
> >>> Since I made the switch to a 64 bit machine (still using 32 bit Fedora
> >>> 19) there is a long delay just before lightdm comes up with the login
> >>> screen.
> >
>  …
>
> >>> [frank@localhost ~]$ sudo systemd-analyze blame
> >>>            19.698s NetworkManager.service
> >>>            19.597s accounts-daemon.service
> >>>            18.723s chronyd.service
> >>>            18.567s lightdm.service
> >> …
> >>
> >>              638ms NetworkManager.service
> >>              135ms avahi-daemon.service
> >>              127ms lightdm.service
>  …
>  
>  I installed
>  - lightdm-1.6.0-10.fc19.x86_64
>  - lightdm-gtk-1.5.1-3.fc19.x86_64
>  - icewm-1.3.7-9.fc19.x86_64
>  - ConsoleKit-0.4.5-5.fc19.x86_64
>  - ConsoleKit-x11-0.4.5-5.fc19.x86_64
>  - ConsoleKit-libs-0.4.5-5.fc19.x86_64
>
>  - rm /usr/share/dbus-1/system-services/org.freedesktop.ConsoleKit.service
>  - rm /var/lib/AccountsService/users/$USER
>     to produce the following warnings within /var/log/lightdm/x-0-greeter.log:
>  ** (process:3229): WARNING **: Failed to open CK session:
>  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
>  org.freedesktop.ConsoleKit was not provided by any .service files
>  ** (lightdm-gtk-greeter:3231): WARNING **: Failed to load user image:
>  Failed to open file '/home/$USER/.face': Permission denied
>  …
>     which are more or less the same as in your readings.
>
>  However didn't manage to produce a lag you mentioned and startup is even
>  faster,
>               99ms lightdm.service
>
>  What can I say. :)
>  Take into account that you are using 32-bits which can be problematic in
>  some cases comparing with a lot more tested 64-bits.
>  This doesn't have to be exactly the case, but. 
   So....32-bit software on a 64-bit CPU sometimes may not be all it's 
cracked up to be :)
    Boy, Poma, if you can't figure it out....I doubt anyone here can - 
I've been following your various and sundry suggestions to users closely 
and you are usually close to, if not on the mark.

Is this worth submitting a bug ??



>  I recommend that you begin to sing
>  http://www.youtube.com/watch?v=qAzqSYQ9X9U :) 

   Practicing now.....listen............
>  poma
>

[poma]

Dana 13.08.2013 20:00, Frank je napisao:
>  On 08/13/2013 01:24 PM, poma wrote:
> > On 13.08.2013 18:49, Frank wrote:
> >> Since I made the switch to a 64 bit machine (still using 32 bit Fedora
> >> 19) there is a long delay just before lightdm comes up with the login
> >> screen.
>   
…

> >> [frank@localhost ~]$ sudo systemd-analyze blame
> >>           19.698s NetworkManager.service
> >>           19.597s accounts-daemon.service
> >>           18.723s chronyd.service
> >>           18.567s lightdm.service
> > …
> >
> >             638ms NetworkManager.service
> >             135ms avahi-daemon.service
> >             127ms lightdm.service 
…

> > cat /var/log/lightdm/lightdm.log
>   
…

>  [+1.39s] DEBUG: Connecting to XServer :0
>  [+1.39s] DEBUG: Starting greeter
>  [+1.39s] DEBUG: Started session 315 with service 'lightdm-greeter',
>  username 'lightdm'
>  
>  What is going on here ???
>  
>  [+18.87s] DEBUG: Session 315 authentication complete with return value
>  0: Success
>  [+18.87s] DEBUG: Greeter authorized
>  [+18.87s] DEBUG: Logging to /var/log/lightdm/x-0-greeter.log
>  [+18.87s] DEBUG: Session 315 running command /usr/sbin/lightdm-gtk-greeter
>  
…

> > grep -v ^$ /var/log/lightdm/x-0-greeter.log
>  ** (process:315): WARNING **: Failed to open CK session:
>  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
>  org.freedesktop.ConsoleKit was not provided by any .service files
>  ** (lightdm-gtk-greeter:334): WARNING **: Failed to load user image:
>  Failed to open file '/home/frank/.face': No such file or directory
>   
…
>   Any comments...other than why lightdm starting session 315 takes 17
>  seconds before it returns ??
>  I am used to seeing similar GTK errors in my .xsessions log.
>  Much of this is beyond me.
>   
I installed
- lightdm-1.6.0-10.fc19.x86_64
- lightdm-gtk-1.5.1-3.fc19.x86_64
- icewm-1.3.7-9.fc19.x86_64
- ConsoleKit-0.4.5-5.fc19.x86_64
- ConsoleKit-x11-0.4.5-5.fc19.x86_64
- ConsoleKit-libs-0.4.5-5.fc19.x86_64

- rm /usr/share/dbus-1/system-services/org.freedesktop.ConsoleKit.service
- rm /var/lib/AccountsService/users/$USER
  to produce the following warnings within /var/log/lightdm/x-0-greeter.log:
** (process:3229): WARNING **: Failed to open CK session:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.ConsoleKit was not provided by any .service files
** (lightdm-gtk-greeter:3231): WARNING **: Failed to load user image:
Failed to open file '/home/$USER/.face': Permission denied
…
  which are more or less the same as in your readings.

However didn't manage to produce a lag you mentioned and startup is even
faster,
            99ms lightdm.service

What can I say. :)
Take into account that you are using 32-bits which can be problematic in
some cases comparing with a lot more tested 64-bits.
This doesn't have to be exactly the case, but.
I recommend that you begin to sing
http://www.youtube.com/watch?v=qAzqSYQ9X9U :)


poma

[Frank McCormick]

On 08/13/2013 02:50 PM, Fred Smith wrote:
>  On Tue, Aug 13, 2013 at 02:00:33PM -0400, Frank wrote:
> > On 08/13/2013 01:24 PM, poma wrote:
> >> On 13.08.2013 18:49, Frank wrote:
> >>> Since I made the switch to a 64 bit machine (still using 32 bit Fedora
> >>> 19) there is a long delay just before lightdm comes up with the login
> >>> screen.
> >
> > ///snip///
> >
> >>>
> >>> [frank@localhost ~]$ sudo systemd-analyze blame
> >>>           19.698s NetworkManager.service
> >>>           19.597s accounts-daemon.service
> >>>           18.723s chronyd.service
> >>>           18.567s lightdm.service
> >> …
> >>
> >>             638ms NetworkManager.service
> >>             135ms avahi-daemon.service
> >>             127ms lightdm.service
> >> …
> >> - lightdm 1.7.4
> >> - lightdm-gtk 1.6.0
> >
> >
> >      I have lightdm 1.6.0
> >             lightdm-gtk 1.5.1-3
> > YUM says they are the latest
> >
> >>
> >> alternatives --display lightdm-greeter
> >
> > Tells me its ok.
> >> grep -v '^#\|^$\|^\[' /etc/lightdm/lightdm.conf
> > minimum-vt=1
> > user-authority-in-system-dir=true
> > xserver-command=X -background none
> > greeter-session=lightdm-greeter
> > session-wrapper=/etc/X11/xinit/Xsession
> >
> >
> >> cat /var/log/lightdm/lightdm.log
> >
> > [+0.01s] DEBUG: Logging to /var/log/lightdm/lightdm.log
> > [+0.01s] DEBUG: Starting Light Display Manager 1.6.0, UID=0 PID=296
> > [+0.01s] DEBUG: Loaded configuration from /etc/lightdm/lightdm.conf
> > [+0.01s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
> > [+0.01s] DEBUG: Registered seat module xlocal
> > [+0.01s] DEBUG: Registered seat module xremote
> > [+0.01s] DEBUG: Adding default seat
> > [+0.01s] DEBUG: Starting seat
> > [+0.01s] DEBUG: Starting new display for greeter
> > [+0.01s] DEBUG: Starting local X display
> > [+0.01s] DEBUG: Using VT 1
> > [+0.01s] DEBUG: Logging to /var/log/lightdm/x-0.log
> > [+0.03s] DEBUG: Writing X server authority to /var/run/lightdm/root/:0
> > [+0.03s] DEBUG: Launching X Server
> > [+0.03s] DEBUG: Launching process 306: /usr/bin/X -background none
> > :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch
> > [+0.03s] DEBUG: Waiting for ready signal from X server :0
> > [+0.94s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
> > [+0.94s] DEBUG: Registering seat with bus path
> > /org/freedesktop/DisplayManager/Seat0
> > [+1.39s] DEBUG: Got signal 10 from process 306
> > [+1.39s] DEBUG: Got signal from X server :0
> > [+1.39s] DEBUG: Connecting to XServer :0
> > [+1.39s] DEBUG: Starting greeter
> > [+1.39s] DEBUG: Started session 315 with service 'lightdm-greeter',
> > username 'lightdm'
> >
> > What is going on here ???
>
>  Dunno. Might it be waiting for a network to come up?
>  
    Nope. At this point the network is up.

[Ananda Samaddar]

On Tue, 13 Aug 2013 12:49:13 -0400
Frank <beacon(a)videotron.ca&gt; wrote:

>  Since I made the switch to a 64 bit machine (still using 32 bit
>  Fedora 19) there is a long delay just before lightdm comes up with
>  the login screen.
>  Can someone take a look at this output and perhaps point out why and
>  where it's occurring ? By the way I don't use LVM or raid...can I
>  disable these services? What;s the best way to do that. Even so the
>  time they take doesn't account for the 6-7 second delay after booting
>  before lightdm comes up.
>  
>  Thanks for any help
>  
>  
>  [frank@localhost ~]$ sudo systemd-analyze blame
>            19.698s NetworkManager.service
>            19.597s accounts-daemon.service
>            18.723s chronyd.service
>            18.567s lightdm.service
>             2.406s lvm2-monitor.service
>             2.317s dmraid-activation.service
>             1.487s systemd-udev-settle.service
>             1.467s systemd-tmpfiles-setup-dev.service
>             1.152s fedora-loadmodules.service
>             1.074s systemd-fsck-root.service
>              706ms polkit.service
>              656ms systemd-sysctl.service
>              581ms fedora-readonly.service
>              537ms systemd-logind.service
>              510ms sys-kernel-debug.mount
>              508ms dev-mqueue.mount
>              508ms rtkit-daemon.service
>              505ms dev-hugepages.mount
>              500ms media-debian.mount
>              485ms tmp.mount
>              353ms systemd-udev-trigger.service
>              294ms plymouth-start.service
>              265ms systemd-readahead-replay.service
>              243ms lvm2-lvmetad.service
>              216ms systemd-random-seed-load.service
>              165ms sys-kernel-config.mount
>              156ms systemd-readahead-collect.service
>              152ms systemd-remount-fs.service
>              138ms systemd-tmpfiles-setup.service
>               89ms plymouth-read-write.service
>               88ms plymouth-quit.service
>               86ms plymouth-quit-wait.service
>               70ms systemd-udevd.service
>               34ms systemd-user-sessions.service
>               32ms livesys.service
>               27ms home-frank-external.mount
>               25ms livesys-late.service
>               21ms systemd-vconsole-setup.service
>               13ms auditd.service
>               10ms systemd-journal-flush.service
>                3ms rpcbind.service
>                3ms systemd-update-utmp-runlevel.service
>                1ms systemd-readahead-done.service 
Can you not use bootchart to visualise this and find the culprit?

Ananda

[poma]

On 13.08.2013 18:49, Frank wrote:
>  Since I made the switch to a 64 bit machine (still using 32 bit
> Fedora
>  19) there is a long delay just before lightdm comes up with the login
>  screen.
>  Can someone take a look at this output and perhaps point out why and
>  where it's occurring ? By the way I don't use LVM or raid...can I disable
>  these services? What;s the best way to do that. Even so the time they
>  take doesn't account for the 6-7 second delay after booting before
>  lightdm comes up.
>  
>  Thanks for any help
>  
>  
>  [frank@localhost ~]$ sudo systemd-analyze blame
>           19.698s NetworkManager.service
>           19.597s accounts-daemon.service
>           18.723s chronyd.service
>           18.567s lightdm.service 
…

           638ms NetworkManager.service
           135ms avahi-daemon.service
           127ms lightdm.service
…
- lightdm 1.7.4
- lightdm-gtk 1.6.0

alternatives --display lightdm-greeter
grep -v '^#\|^$\|^\[' /etc/lightdm/lightdm.conf
cat /var/log/lightdm/lightdm.log
grep -v ^$ /var/log/lightdm/x-0-greeter.log

/boot/extlinux/extlinux.conf
append … rd.dm=0 rd.luks=0 rd.lvm=0 rd.md=0

/boot/grub2/grub.cfg
linux …	rd.dm=0 rd.luks=0 rd.lvm=0 rd.md=0

man 7 dracut.cmdline
man 1 systemctl


poma

[Fred Smith]

On Tue, Aug 13, 2013 at 02:00:33PM -0400, Frank wrote:
>  On 08/13/2013 01:24 PM, poma wrote:
>  >On 13.08.2013 18:49, Frank wrote:
>  >>Since I made the switch to a 64 bit machine (still using 32 bit Fedora
>  >>19) there is a long delay just before lightdm comes up with the login
>  >>screen.
>  
>  ///snip///
>  
>  >>
>  >>[frank@localhost ~]$ sudo systemd-analyze blame
>  >>          19.698s NetworkManager.service
>  >>          19.597s accounts-daemon.service
>  >>          18.723s chronyd.service
>  >>          18.567s lightdm.service
>  >…
>  >
>  >            638ms NetworkManager.service
>  >            135ms avahi-daemon.service
>  >            127ms lightdm.service
>  >…
>  >- lightdm 1.7.4
>  >- lightdm-gtk 1.6.0
>  
>  
>      I have lightdm 1.6.0
>             lightdm-gtk 1.5.1-3
>  YUM says they are the latest
>  
>  >
>  >alternatives --display lightdm-greeter
>  
>  Tells me its ok.
>  >grep -v '^#\|^$\|^\[' /etc/lightdm/lightdm.conf
>  minimum-vt=1
>  user-authority-in-system-dir=true
>  xserver-command=X -background none
>  greeter-session=lightdm-greeter
>  session-wrapper=/etc/X11/xinit/Xsession
>  
>  
>  >cat /var/log/lightdm/lightdm.log
>  
>  [+0.01s] DEBUG: Logging to /var/log/lightdm/lightdm.log
>  [+0.01s] DEBUG: Starting Light Display Manager 1.6.0, UID=0 PID=296
>  [+0.01s] DEBUG: Loaded configuration from /etc/lightdm/lightdm.conf
>  [+0.01s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
>  [+0.01s] DEBUG: Registered seat module xlocal
>  [+0.01s] DEBUG: Registered seat module xremote
>  [+0.01s] DEBUG: Adding default seat
>  [+0.01s] DEBUG: Starting seat
>  [+0.01s] DEBUG: Starting new display for greeter
>  [+0.01s] DEBUG: Starting local X display
>  [+0.01s] DEBUG: Using VT 1
>  [+0.01s] DEBUG: Logging to /var/log/lightdm/x-0.log
>  [+0.03s] DEBUG: Writing X server authority to /var/run/lightdm/root/:0
>  [+0.03s] DEBUG: Launching X Server
>  [+0.03s] DEBUG: Launching process 306: /usr/bin/X -background none
>  :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch
>  [+0.03s] DEBUG: Waiting for ready signal from X server :0
>  [+0.94s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
>  [+0.94s] DEBUG: Registering seat with bus path
>  /org/freedesktop/DisplayManager/Seat0
>  [+1.39s] DEBUG: Got signal 10 from process 306
>  [+1.39s] DEBUG: Got signal from X server :0
>  [+1.39s] DEBUG: Connecting to XServer :0
>  [+1.39s] DEBUG: Starting greeter
>  [+1.39s] DEBUG: Started session 315 with service 'lightdm-greeter',
>  username 'lightdm'
>  
>  What is going on here ??? 
Dunno. Might it be waiting for a network to come up?

>  
>  [+18.87s] DEBUG: Session 315 authentication complete with return
>  value 0: Success
>  [+18.87s] DEBUG: Greeter authorized
>  [+18.87s] DEBUG: Logging to /var/log/lightdm/x-0-greeter.log
>  [+18.87s] DEBUG: Session 315 running command /usr/sbin/lightdm-gtk-greeter
>  [+19.18s] DEBUG: Greeter connected version=1.6.0
>  [+19.18s] DEBUG: Greeter connected, display is ready
>  [+19.18s] DEBUG: New display ready, switching to it
>  [+19.18s] DEBUG: Activating VT 1
>  [+19.89s] DEBUG: Greeter start authentication for frank
>  [+19.89s] DEBUG: Started session 365 with service 'lightdm',
>  username 'frank'
>  [+19.91s] DEBUG: Session 365 got 1 message(s) from PAM
>  [+19.91s] DEBUG: Prompt greeter with 1 message(s)
>  [+30.51s] DEBUG: Continue authentication
>  [+30.56s] DEBUG: Session 365 authentication complete with return
>  value 0: Success
>  [+30.56s] DEBUG: Authenticate result for user frank: Success
>  [+30.57s] DEBUG: User frank authorized
>  [+30.62s] DEBUG: Greeter requests session icewm
>  [+30.62s] DEBUG: Using session icewm
>  [+30.62s] DEBUG: Stopping greeter
>  [+30.62s] DEBUG: Session 315: Sending SIGTERM
>  [+30.62s] DEBUG: Greeter closed communication channel
>  [+30.62s] DEBUG: Session 315 exited with return value 0
>  [+30.62s] DEBUG: Greeter quit
>  [+30.64s] DEBUG: Dropping privileges to uid 1000
>  [+30.64s] DEBUG: Calling setresgid
>  [+30.64s] DEBUG: Calling setresuid
>  [+30.64s] DEBUG: Restoring privileges
>  [+30.64s] DEBUG: Calling setresuid
>  [+30.64s] DEBUG: Calling setresgid
>  [+30.65s] DEBUG: Starting session icewm as user frank
>  [+30.65s] DEBUG: Session 365 running command /etc/X11/xinit/Xsession
>  icewm-session
>  [+30.72s] DEBUG: Registering session with bus path
>  /org/freedesktop/DisplayManager/Session0
>  
>  
>  
>  >grep -v ^$ /var/log/lightdm/x-0-greeter.log
>  ** (process:315): WARNING **: Failed to open CK session:
>  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
>  org.freedesktop.ConsoleKit was not provided by any .service files
>  ** (lightdm-gtk-greeter:334): WARNING **: Failed to load user image:
>  Failed to open file '/home/frank/.face': No such file or directory
>  ** (lightdm-gtk-greeter:334): WARNING **: Could not get accounts
>  property XKeyboardLayouts
>  ** (lightdm-gtk-greeter:334): WARNING **: Could not get accounts
>  property XHasMessages
>  (lightdm-gtk-greeter:334): GLib-CRITICAL **: g_variant_get_type:
>  assertion `value != NULL' failed
>  (lightdm-gtk-greeter:334): GLib-CRITICAL **:
>  g_variant_type_is_subtype_of: assertion `g_variant_type_check
>  (type)' failed
>  (lightdm-gtk-greeter:334): GLib-CRITICAL **:
>  g_variant_get_type_string: assertion `value != NULL' failed
>  ** (lightdm-gtk-greeter:334): WARNING **: Unexpected accounts
>  property type for XHasMessages: (null)
>  (lightdm-gtk-greeter:334): GLib-CRITICAL **: g_variant_unref:
>  assertion `value != NULL' failed
>  ** (lightdm-gtk-greeter:334): WARNING **: Could not get accounts
>  property XKeyboardLayouts
>  ** (lightdm-gtk-greeter:334): WARNING **: Could not get accounts
>  property XHasMessages
>  (lightdm-gtk-greeter:334): GLib-CRITICAL **: g_variant_get_type:
>  assertion `value != NULL' failed
>  (lightdm-gtk-greeter:334): GLib-CRITICAL **:
>  g_variant_type_is_subtype_of: assertion `g_variant_type_check
>  (type)' failed
>  (lightdm-gtk-greeter:334): GLib-CRITICAL **:
>  g_variant_get_type_string: assertion `value != NULL' failed
>  ** (lightdm-gtk-greeter:334): WARNING **: Unexpected accounts
>  property type for XHasMessages: (null)
>  (lightdm-gtk-greeter:334): GLib-CRITICAL **: g_variant_unref:
>  assertion `value != NULL' failed
>  
>  >
>  >/boot/extlinux/extlinux.conf
>  
>  No such file
>  
>  >append … rd.dm=0 rd.luks=0 rd.lvm=0 rd.md=0
>  >
>  >/boot/grub2/grub.cfg
>  >linux …	rd.dm=0 rd.luks=0 rd.lvm=0 rd.md=0
>  
>    Parameters already there
>  
>  
>  >
>  >man 7 dracut.cmdline
>  
>  Didn't understand very much ( I'm a refugee from Debian)
>  >man 1 systemctl
>  >
>  
>    That I sort of understood :)
>  
>   Any comments...other than why lightdm starting session 315 takes 17
>  seconds before it returns ??
>  I am used to seeing similar GTK errors in my .xsessions log.
>  Much of this is beyond me.
>  
>  >
>  >poma
>  >
>  >
>  
>  -- 
>  users mailing list
>  users(a)lists.fedoraproject.org
>  To unsubscribe or change subscription options:
>  https://admin.fedoraproject.org/mailman/listinfo/users
>  Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>  Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
>  Have a question? Ask away: http://ask.fedoraproject.org 
-- 
-------------------------------------------------------------------------------
 .----    Fred Smith   /              
( /__  ,__.   __   __ /  __   : /     
 /    /  /   /__) /  /  /__) .+'           Home: fredex(a)fcshome.stoneham.ma.us 
/    /  (__ (___ (__(_ (___ / :__                                 781-438-5471 
-------------------------------- Jude 1:24,25 ---------------------------------

[Frank McCormick]

On 08/14/2013 11:51 AM, Frank wrote:
>  On 08/14/2013 11:33 AM, Ahmad Samir wrote:
> > On 13 August 2013 18:49, Frank <beacon(a)videotron.ca
> > <mailto:[e-mail]>> wrote:
> >
> >     Since I made the switch to a 64 bit machine (still using 32 bit
> >     Fedora 19) there is a long delay just before lightdm comes up with
> >     the login screen.
> >     Can someone take a look at this output and perhaps point out why and
> >     where it's occurring ? By the way I don't use LVM or raid...can I
> >     disable
> >     these services? What;s the best way to do that. Even so the time
> >     they take doesn't account for the 6-7 second delay after booting
> >     before lightdm comes up.
> >
> >
> > This could be the same issue discussed in this thread in the forum
> > http://forums.fedoraforum.org/showthread.php?p=1661767
> > [...]
> >
>
>
>     As a matter of fact that appears to be almost exactly the problem
>  here. The only difference is that I have selinux disabled, not set to
>  permissive.
>
>  Installing lxdm has "solved" my problem - the system boots quickly to
>  the login manager. Now I have to re-enable lightdm to see if the delay
>  returns. If so, I'll implement the bootchart as suggested by TC
>  Hollingsworth on this list.
>  

    Re-enabled lightdm, and we are back to a 25 sec delay before it comes
up.
I really don't know what to do next.I can "solve" my problem by going 
back to lxdm, but I really prefer the lightdm interface.

I could use the bootchart, but I can't edit the kernel command line with 
this USB keyboard as for some unknown reason it creates double
characters when at that level...same thing in the BIOS screen. It works
fine once the system is booted. I'd have to edit the grub default line 
and redo grub.cfg.

Regards

Frank

[Joe Zeff]

On 08/14/2013 09:07 AM, Frank wrote:
>      Re-enabled lightdm, and we are back to a 25 sec delay before it
> comes
>  up.
>  I really don't know what to do next.I can "solve" my problem by going
>  back to lxdm, but I really prefer the lightdm interface. 
I had a similar issue on my laptop after upgrading to F19.  Try running 
this as root:

restorecon -R -v /usr/sbin

Then re-enable SELinux and reboot.  As I recall, there's one file with 
the wrong context that needs fixing.  If it works, great; if not, all 
that's lost is a little bit of time.