Date: Fri, 6 Aug 2010 21:07:16 +0200 From: =?ISO-8859-1?Q?Fernando_Apestegu=EDa?= <fernando.apesteguia@gmail.com> To: Joe Marcus Clarke <marcus@freebsd.org> Cc: freebsd-gnome@freebsd.org Subject: Re: gnome slow startup Message-ID: <AANLkTik=VK1VMC8UKNZwedv9PgyGUsJJ4hUOBfPz9mM8@mail.gmail.com> In-Reply-To: <4C5C573C.7070304@freebsd.org> References: <AANLkTinDsN1hNiW8B75UHtfVKByA4EQUxqMWP9Prm14R@mail.gmail.com> <4C5B09FC.4010902@freebsd.org> <AANLkTinXeEZywLy02mEjg4PL7S8X3ppGQTJZTyBZJZyx@mail.gmail.com> <4C5C2FEF.2030903@freebsd.org> <AANLkTimEGt%2BisfMYvSTGDM7hB0vXDDuCArrNVZYOLk3h@mail.gmail.com> <4C5C3C87.7060105@freebsd.org> <AANLkTinx6qgipmT4RU2H7ZncGHQHgcQg0uUt6tiZcUdY@mail.gmail.com> <4C5C405B.70806@freebsd.org> <AANLkTi=0utzU=_vy3veGxMCtfbPMu3ZiOPbb2dfXFPcS@mail.gmail.com> <4C5C47C1.2000206@freebsd.org> <AANLkTikQFNnGTfwGuG2-8PfbLYMOQ1m%2Bg-CTFA-vf9Ba@mail.gmail.com> <4C5C5434.70606@freebsd.org> <AANLkTim4NJ0Z8tHrDLYVc2eeTy-Afci8V5evfkHFSdzK@mail.gmail.com> <4C5C573C.7070304@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
2010/8/6 Joe Marcus Clarke <marcus@freebsd.org>: > On 8/6/10 2:32 PM, Fernando Apestegu=EDa wrote: >> 2010/8/6 Joe Marcus Clarke <marcus@freebsd.org>: >>> On 8/6/10 1:46 PM, Fernando Apestegu=EDa wrote: >>>> 2010/8/6 Joe Marcus Clarke <marcus@freebsd.org>: >>>>> On 8/6/10 1:08 PM, Fernando Apestegu=EDa wrote: >>>>>> 2010/8/6 Joe Marcus Clarke <marcus@freebsd.org>: >>>>>>> On 8/6/10 12:52 PM, Fernando Apestegu=EDa wrote: >>>>>>>> 2010/8/6 Joe Marcus Clarke <marcus@freebsd.org>: >>>>>>>>> On 8/6/10 12:38 PM, Fernando Apestegu=EDa wrote: >>>>>>>>>> 2010/8/6 Joe Marcus Clarke <marcus@freebsd.org>: >>>>>>>>>>> On 8/6/10 11:25 AM, Fernando Apestegu=EDa wrote: >>>>>>>>>>>> 2010/8/5 Joe Marcus Clarke <marcus@freebsd.org>: >>>>>>>>>>>>> On 8/5/10 12:38 PM, Fernando Apestegu=EDa wrote: >>>>>>>>>>>>>> Hi all, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Recently I updated to 8.1-RELEASE and since then gnome-panel= takes up >>>>>>>>>>>>>> to 1 minute to show up. >>>>>>>>>>>>>> >>>>>>>>>>>>>> I read about a problem with consolekit. I'm using consolekit= -0.4.1_4. >>>>>>>>>>>>>> Is there going to be and update >>>>>>>>>>>>>> for this soon? >>>>>>>>>>>>> >>>>>>>>>>>>> That is the latest version of consolekit, and it has the fix.= =A0How are >>>>>>>>>>>>> you starting GNOME? =A0What is the output of ck-list-sessions= ? >>>>>>>>>>>> >>>>>>>>>>>> I'm launching GNOME with "startx" >>>>>>>>>>>> My .xinitrc looks like this: >>>>>>>>>>>> >>>>>>>>>>>> exec /usr/local/bin/gnome-session >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> ck-list-sessions doesn't show anything. >>>>>>>>>>> >>>>>>>>>>> See http://www.freebsd.org/gnome/docs/faq2.html#full-gnome . >>>>>>>>>> >>>>>>>>>> HAL and DBus are run at boot in my system. I don't run avahi as = I >>>>>>>>>> don't think it is really necessary, is it?. >>>>>>>>>> I used "exec ck-launch-session gnome-session" in my .xinitrc but >>>>>>>>>> nothing changes. I still have the same delay and the same messag= e >>>>>>>>>> "Could not ask session manager if shut down is available" >>>>>>>>> >>>>>>>>> What does ck-list-sessions show? >>>>>>>> >>>>>>>> Session1: >>>>>>>> =A0 =A0 =A0 unix-user =3D '1001' >>>>>>>> =A0 =A0 =A0 realname =3D 'Fernando Apesteguia Santiago' >>>>>>>> =A0 =A0 =A0 seat =3D 'Seat1' >>>>>>>> =A0 =A0 =A0 session-type =3D '' >>>>>>>> =A0 =A0 =A0 active =3D FALSE >>>>>>>> =A0 =A0 =A0 x11-display =3D '' >>>>>>>> =A0 =A0 =A0 x11-display-device =3D '' >>>>>>>> =A0 =A0 =A0 display-device =3D 'ttyv0' >>>>>>>> =A0 =A0 =A0 remote-host-name =3D '' >>>>>>>> =A0 =A0 =A0 is-local =3D TRUE >>>>>>>> =A0 =A0 =A0 on-since =3D '2010-08-06T16:24:10.991764Z' >>>>>>>> =A0 =A0 =A0 login-session-id =3D '' >>>>>>> >>>>>>> Post the output of /usr/local/libexec/ck-get-x11-display-device, an= d the >>>>>>> output of: >>>>>> $ /usr/local/libexec/ck-get-x11-display-device >>>>>> /dev/ttyv8 >>>>>> >>>>>>> >>>>>>> fstat -p `cat "/tmp/.X${dispnum}-lock"` >>>>>> >>>>>> =A0fstat -p `cat "/tmp/.X0-lock"` >>>>>> USER =A0 =A0 CMD =A0 =A0 =A0 =A0 =A0PID =A0 FD MOUNT =A0 =A0 =A0INUM= MODE =A0 =A0 =A0 =A0 SZ|DV R/W >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 root / =A0 =A0 =A0 =A0 =A0 =A0= 2 drwxr-xr-x =A0 =A0 512 =A0r >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 wd / =A0 =A0 =A0 =A0318897= 77 drwxr-xr-x =A0 =A03072 =A0r >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 text / =A0 =A0 =A0 =A031727588= -r-sr-xr-x =A01760848 =A0r >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 =A00 / =A0 =A0 =A0 =A05346= 936 -rw-r--r-- =A0 57765 =A0w >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 =A01* internet6 stream tcp= ffffff00066ee000 >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 =A02 /dev =A0 =A0 =A0 =A0 = 45 crw------- =A0 ttyv0 rw >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 =A03* internet stream tcp = ffffff00066eda50 >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 =A04* local stream ffffff0= 0066a1000 >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 =A05 / =A0 =A0 =A0 =A08480= 23 -r--r--r-- =A0 31246 =A0r >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 =A06 /dev =A0 =A0 =A0 =A0 = 53 crw------- =A0 ttyv8 rw >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 =A07 /dev =A0 =A0 =A0 =A0 = 34 crw-r--r-- =A0 =A0 pci rw >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 =A08 /dev =A0 =A0 =A0 =A0 = 27 crw-r----- =A0 =A0 mem rw >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 =A09 /dev =A0 =A0 =A0 =A0 = 29 crw------- =A0 =A0 =A0io rw >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 10* local stream ffffff000= 6189b40 <-> >>>>>> ffffff000617cd20 >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 11 /dev =A0 =A0 =A0 =A0 13= crw------- =A0sysmouse rw >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 12* local stream ffffff000= 65a7d20 <-> >>>>>> ffffff00065a7e10 >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 13* local stream ffffff000= 65a7960 <-> >>>>>> ffffff00065a7a50 >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 14* local stream ffffff000= 617c1e0 <-> >>>>>> ffffff000617c000 >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 15* local stream ffffff000= 65a7690 <-> >>>>>> ffffff00065a7780 >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 16* local stream ffffff000= 6188960 <-> >>>>>> ffffff0006188b40 >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 17* local stream ffffff012= a0f8d20 <-> >>>>>> ffffff012a0f8e10 >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 18* local stream ffffff012= a2eda50 <-> >>>>>> ffffff012a2edb40 >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 19* local stream ffffff012= a2ed000 <-> >>>>>> ffffff012a2ed0f0 >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 20* local stream ffffff012= a0f8000 <-> >>>>>> ffffff012a163c30 >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 21* local stream ffffff012= a0e2b40 <-> >>>>>> ffffff012a0e2c30 >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 22* local stream ffffff012= a6294b0 <-> >>>>>> ffffff012a6295a0 >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 23* local stream ffffff012= a741780 <-> >>>>>> ffffff012a741870 >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 24* local stream ffffff012= a62a960 <-> >>>>>> ffffff012a62aa50 >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 25* local stream ffffff012= a7612d0 <-> >>>>>> ffffff012a62a690 >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 26* local stream ffffff012= a761780 <-> >>>>>> ffffff012a761690 >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 27* local stream ffffff012= a865960 <-> >>>>>> ffffff012a875960 >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 28* local stream ffffff012= aa7a0f0 <-> >>>>>> ffffff012aa7b4b0 >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 29* local stream ffffff012= a8653c0 <-> >>>>>> ffffff012a8654b0 >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 30* local stream ffffff012= ac3e690 <-> >>>>>> ffffff012ac3e780 >>>>>> root =A0 =A0 Xorg =A0 =A0 =A0 =A01434 =A0 31* local stream ffffff012= aa7a960 <-> >>>>>> ffffff012a865e10 >>>>> >>>>> All of this looks good. =A0I can't see why consolekit doesn't show th= at >>>>> the session is active. >>>>> >>>>> As root, while in X, run /usr/local/libexec/ck-collect-session-info, = and >>>>> post the output. >>>> >>>> OK, as root (sudo su -), while being in the offending X session, I got= this: >>>> >>>> ** (ck-collect-session-info:1942): WARNING **: Invalid UID >>> >>> Try: >>> >>> /usr/local/libexec/ck-collect-session-info --uid 1001 --pid >>> PID_OF_GNOME-SESSION >>> >>> Where PID_OF_GNOME-SESSION is the PID of the running gnome-session proc= ess. >> >> $ ps ax | grep gnome-session >> 1436 =A0v0 =A0I =A0 =A0 =A00:00.00 ck-launch-session gnome-session >> 1438 =A0v0 =A0I =A0 =A0 =A00:00.20 gnome-session >> 1441 =A0v0 =A0I =A0 =A0 =A00:00.00 dbus-launch --exit-with-session gnome= -session >> 2110 =A0 0 =A0S+ =A0 =A0 0:00.00 grep gnome-session >> >> $ /usr/local/libexec/ck-collect-session-info --uid 1001 --pid 1438 >> ** (ck-collect-session-info:2111): WARNING **: kvm_getenvv failed: >> cannot open /proc/1438/mem >> unix-user =3D 1001 >> display-device =3D ttyv0 >> is-local =3D true > > Is procfs mounted? Hey! That did it! Thank you very much. Just two more questions: 1 - I don't remember having procfs mounted by default previously. Is this something that has changed recently? 2 - Is a requirement to have procfs(5) mounted to run GNOME? I thought procfs(5) was marked as deprecated in FreeBSD (or at least it shouldn't be used if other options are available). Am I right? Thanks in advance. > > Joe > > -- > Joe Marcus Clarke > FreeBSD GNOME Team =A0 =A0 =A0:: =A0 =A0 =A0gnome@FreeBSD.org > FreeNode / #freebsd-gnome > http://www.FreeBSD.org/gnome >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTik=VK1VMC8UKNZwedv9PgyGUsJJ4hUOBfPz9mM8>