Date: Fri, 6 Aug 2010 21:24:38 +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: <AANLkTimV73ynnP_wV26RH1PUuC_O2H_zkUh=fzN1uD4K@mail.gmail.com> In-Reply-To: <4C5C5F19.8070800@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> <AANLkTik=VK1VMC8UKNZwedv9PgyGUsJJ4hUOBfPz9mM8@mail.gmail.com> <4C5C5F19.8070800@freebsd.org>
index | next in thread | previous in thread | raw e-mail
2010/8/6 Joe Marcus Clarke <marcus@freebsd.org>: > On 8/6/10 3:07 PM, Fernando Apesteguía wrote: >> 2010/8/6 Joe Marcus Clarke <marcus@freebsd.org>: >>> On 8/6/10 2:32 PM, Fernando Apesteguía wrote: >>>> 2010/8/6 Joe Marcus Clarke <marcus@freebsd.org>: >>>>> On 8/6/10 1:46 PM, Fernando Apesteguía wrote: >>>>>> 2010/8/6 Joe Marcus Clarke <marcus@freebsd.org>: >>>>>>> On 8/6/10 1:08 PM, Fernando Apesteguía wrote: >>>>>>>> 2010/8/6 Joe Marcus Clarke <marcus@freebsd.org>: >>>>>>>>> On 8/6/10 12:52 PM, Fernando Apesteguía wrote: >>>>>>>>>> 2010/8/6 Joe Marcus Clarke <marcus@freebsd.org>: >>>>>>>>>>> On 8/6/10 12:38 PM, Fernando Apesteguía wrote: >>>>>>>>>>>> 2010/8/6 Joe Marcus Clarke <marcus@freebsd.org>: >>>>>>>>>>>>> On 8/6/10 11:25 AM, Fernando Apesteguía wrote: >>>>>>>>>>>>>> 2010/8/5 Joe Marcus Clarke <marcus@freebsd.org>: >>>>>>>>>>>>>>> On 8/5/10 12:38 PM, Fernando Apesteguía 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. How are >>>>>>>>>>>>>>> you starting GNOME? What 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 message >>>>>>>>>>>> "Could not ask session manager if shut down is available" >>>>>>>>>>> >>>>>>>>>>> What does ck-list-sessions show? >>>>>>>>>> >>>>>>>>>> Session1: >>>>>>>>>> unix-user = '1001' >>>>>>>>>> realname = 'Fernando Apesteguia Santiago' >>>>>>>>>> seat = 'Seat1' >>>>>>>>>> session-type = '' >>>>>>>>>> active = FALSE >>>>>>>>>> x11-display = '' >>>>>>>>>> x11-display-device = '' >>>>>>>>>> display-device = 'ttyv0' >>>>>>>>>> remote-host-name = '' >>>>>>>>>> is-local = TRUE >>>>>>>>>> on-since = '2010-08-06T16:24:10.991764Z' >>>>>>>>>> login-session-id = '' >>>>>>>>> >>>>>>>>> Post the output of /usr/local/libexec/ck-get-x11-display-device, and the >>>>>>>>> output of: >>>>>>>> $ /usr/local/libexec/ck-get-x11-display-device >>>>>>>> /dev/ttyv8 >>>>>>>> >>>>>>>>> >>>>>>>>> fstat -p `cat "/tmp/.X${dispnum}-lock"` >>>>>>>> >>>>>>>> fstat -p `cat "/tmp/.X0-lock"` >>>>>>>> USER CMD PID FD MOUNT INUM MODE SZ|DV R/W >>>>>>>> root Xorg 1434 root / 2 drwxr-xr-x 512 r >>>>>>>> root Xorg 1434 wd / 31889777 drwxr-xr-x 3072 r >>>>>>>> root Xorg 1434 text / 31727588 -r-sr-xr-x 1760848 r >>>>>>>> root Xorg 1434 0 / 5346936 -rw-r--r-- 57765 w >>>>>>>> root Xorg 1434 1* internet6 stream tcp ffffff00066ee000 >>>>>>>> root Xorg 1434 2 /dev 45 crw------- ttyv0 rw >>>>>>>> root Xorg 1434 3* internet stream tcp ffffff00066eda50 >>>>>>>> root Xorg 1434 4* local stream ffffff00066a1000 >>>>>>>> root Xorg 1434 5 / 848023 -r--r--r-- 31246 r >>>>>>>> root Xorg 1434 6 /dev 53 crw------- ttyv8 rw >>>>>>>> root Xorg 1434 7 /dev 34 crw-r--r-- pci rw >>>>>>>> root Xorg 1434 8 /dev 27 crw-r----- mem rw >>>>>>>> root Xorg 1434 9 /dev 29 crw------- io rw >>>>>>>> root Xorg 1434 10* local stream ffffff0006189b40 <-> >>>>>>>> ffffff000617cd20 >>>>>>>> root Xorg 1434 11 /dev 13 crw------- sysmouse rw >>>>>>>> root Xorg 1434 12* local stream ffffff00065a7d20 <-> >>>>>>>> ffffff00065a7e10 >>>>>>>> root Xorg 1434 13* local stream ffffff00065a7960 <-> >>>>>>>> ffffff00065a7a50 >>>>>>>> root Xorg 1434 14* local stream ffffff000617c1e0 <-> >>>>>>>> ffffff000617c000 >>>>>>>> root Xorg 1434 15* local stream ffffff00065a7690 <-> >>>>>>>> ffffff00065a7780 >>>>>>>> root Xorg 1434 16* local stream ffffff0006188960 <-> >>>>>>>> ffffff0006188b40 >>>>>>>> root Xorg 1434 17* local stream ffffff012a0f8d20 <-> >>>>>>>> ffffff012a0f8e10 >>>>>>>> root Xorg 1434 18* local stream ffffff012a2eda50 <-> >>>>>>>> ffffff012a2edb40 >>>>>>>> root Xorg 1434 19* local stream ffffff012a2ed000 <-> >>>>>>>> ffffff012a2ed0f0 >>>>>>>> root Xorg 1434 20* local stream ffffff012a0f8000 <-> >>>>>>>> ffffff012a163c30 >>>>>>>> root Xorg 1434 21* local stream ffffff012a0e2b40 <-> >>>>>>>> ffffff012a0e2c30 >>>>>>>> root Xorg 1434 22* local stream ffffff012a6294b0 <-> >>>>>>>> ffffff012a6295a0 >>>>>>>> root Xorg 1434 23* local stream ffffff012a741780 <-> >>>>>>>> ffffff012a741870 >>>>>>>> root Xorg 1434 24* local stream ffffff012a62a960 <-> >>>>>>>> ffffff012a62aa50 >>>>>>>> root Xorg 1434 25* local stream ffffff012a7612d0 <-> >>>>>>>> ffffff012a62a690 >>>>>>>> root Xorg 1434 26* local stream ffffff012a761780 <-> >>>>>>>> ffffff012a761690 >>>>>>>> root Xorg 1434 27* local stream ffffff012a865960 <-> >>>>>>>> ffffff012a875960 >>>>>>>> root Xorg 1434 28* local stream ffffff012aa7a0f0 <-> >>>>>>>> ffffff012aa7b4b0 >>>>>>>> root Xorg 1434 29* local stream ffffff012a8653c0 <-> >>>>>>>> ffffff012a8654b0 >>>>>>>> root Xorg 1434 30* local stream ffffff012ac3e690 <-> >>>>>>>> ffffff012ac3e780 >>>>>>>> root Xorg 1434 31* local stream ffffff012aa7a960 <-> >>>>>>>> ffffff012a865e10 >>>>>>> >>>>>>> All of this looks good. I can't see why consolekit doesn't show that >>>>>>> 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 process. >>>> >>>> $ ps ax | grep gnome-session >>>> 1436 v0 I 0:00.00 ck-launch-session gnome-session >>>> 1438 v0 I 0:00.20 gnome-session >>>> 1441 v0 I 0:00.00 dbus-launch --exit-with-session gnome-session >>>> 2110 0 S+ 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 = 1001 >>>> display-device = ttyv0 >>>> is-local = 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? > > No. It's been a requirement for the past few GNOME releases. > >> 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? > > It is documented in the FAQ as being required for GNOME. It has not > been fully purged at this point. > Good to know. Thank you very much for helping me out. Cheers! > Joe > > -- > Joe Marcus Clarke > FreeBSD GNOME Team :: gnome@FreeBSD.org > FreeNode / #freebsd-gnome > http://www.FreeBSD.org/gnome >home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimV73ynnP_wV26RH1PUuC_O2H_zkUh=fzN1uD4K>