Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
Hi Alan, On Wednesday, 12. October 2011 21:36:58 Allan Gottlieb wrote: On Wed, Oct 12 2011, Allan Gottlieb wrote: On Wed, Oct 12 2011, Canek Peláez Valdés wrote: If it is related to the video card/driver that you use, try reemerging cogl and clutter; it doesn't matter that a world upgrade don't want to reemerge it, sometimes the ebuilds change without changing versions. My versions and useflags of cogl and clutter are: # emerge -1pv clutter cogl These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ~] media-libs/cogl-1.8.0 USE=doc examples introspection pango -debug -test 0 kB [1] [ebuild R ~] media-libs/clutter-1.8.0 USE=doc introspection -debug 0 kB [1] I had remerged clutter earlier today and just did cogl. Mu use flags are basically the same as yours Calculating dependencies... done! [ebuild R] media-libs/clutter-1.8.0 USE=introspection -debug -doc 0 kB [1] [ebuild R] media-libs/cogl-1.8.0 USE=introspection pango -debug -doc -examples -test 0 kB [1] I am using the same driver as you but a different version (mine is one newer) and I don't have the sna use flag. I might not have access to the machine an longer today, but will try. thanks, allan I forgot to say that with the remerged clutter and cogl, gdm still crashes. I just rebuilt the driver downgraded to 2.15.0-r1. I specified sna in package.use but still it was merged without it. This configuration still has gdm crashing [U] x11-drivers/xf86-video-intel Available versions: 2.8.1 2.9.1 (~)2.10.0-r1 (~)2.11.0 2.13.0 2.14.0 2.15.0-r1 (~)2.16.0 {debug dri sna} Installed versions: 2.15.0-r1(09:27:44 PM 10/12/2011)(dri) Homepage:http://xorg.freedesktop.org/ to rule out the video-stack, I'd try gnome in fallback-mode. If it works, chances are your problem is video-related. If it still crashes, the problem is elsewhere. Is there something in dmesg related to the gnome-shell segfaults? allan Best, Michael
[gentoo-user] can't build gnome 3.2 (3.0 was ok)
I've catch problem like this http://www.gossamer-threads.com/lists/engine?do=post_view_flat;post=240430;page=2;sb=post_latest_reply;so=ASC;mh=25;list=gentoo gdm[-gnome-shell] gnome-fallback-3.2 work fine (x86 xf86-video-ati), gnome-shell crash. But on other machine gdm[gnome-shell] gnome-3.2 work fine (x86_64 xf86-video-nouveau)... on smartbook gdm[-gnome-shell] gnome-fallback-3.2 work fine (arm xf86-video-tegra), gnome-shell not support GLES. Anybody resolve problem with gnome-shell crash ?.. -- Best regards, Denis I. Polukarov signature.asc Description: This is a digitally signed message part
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Thu, Oct 13 2011, Michael Schreckenbauer wrote: Hi Alan, Is there something in dmesg related to the gnome-shell segfaults? Best, Michael Indeed! oldlap ~ # dmesg | grep gnome-shell gnome-shell[3325] general protection ip:b6853dc2 sp:bfdba6d4 error:0 in libmozjs185.so.1.0.0[b6819000+2ca000] gnome-shell[3479] general protection ip:b682bdc2 sp:bf882764 error:0 in libmozjs185.so.1.0.0[b67f1000+2ca000] oldlap ~ #
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Wed, Oct 12 2011, Michael Schreckenbauer wrote: gnome-shell segfaults. I remember some problems with gnome-shell and GL from the dri-devel-ML. What video-card are you using? Drivers/version? Is there any other WM you can start, execute gnome-shell --replace in a console and dump the output here? Could you try running gnome in fallback-mode? Afaik you can enable this with gsettings set org.gnome.desktop.session session-name gnome-fallback I typed that command as root (no complaints) and restarted gdm (twice). Same problem oldlap ~ # dmesg | grep gnome-shellgnome-shell[3325] general protection ip:b6853dc2 sp:bfdba6d4 error:0 in libmozjs185.so.1.0.0[b6819000+2ca000] gnome-shell[3479] general protection ip:b682bdc2 sp:bf882764 error:0 in libmozjs185.so.1.0.0[b67f1000+2ca000] gnome-shell[24424] general protection ip:b69dcdc2 sp:bfa4c494 error:0 in libmozjs185.so.1.0.0[b69a2000+2ca000] gnome-shell[24440] general protection ip:b6978dc2 sp:bfc21d84 error:0 in libmozjs185.so.1.0.0[b693e000+2ca000] gnome-shell[24563] general protection ip:b6932dc2 sp:bfb993c4 error:0 in libmozjs185.so.1.0.0[b68f8000+2ca000] gnome-shell[24579] general protection ip:b68f1dc2 sp:bf8c52d4 error:0 in libmozjs185.so.1.0.0[b68b7000+2ca000] oldlap ~ # allan
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Thu, Oct 13, 2011 at 9:29 AM, Allan Gottlieb gottl...@nyu.edu wrote: On Thu, Oct 13 2011, Michael Schreckenbauer wrote: Hi Alan, Is there something in dmesg related to the gnome-shell segfaults? Best, Michael Indeed! oldlap ~ # dmesg | grep gnome-shell gnome-shell[3325] general protection ip:b6853dc2 sp:bfdba6d4 error:0 in libmozjs185.so.1.0.0[b6819000+2ca000] gnome-shell[3479] general protection ip:b682bdc2 sp:bf882764 error:0 in libmozjs185.so.1.0.0[b67f1000+2ca000] oldlap ~ # I've skipped most of the thread, so forgive me if this was already done...try rebuilding libmozjs? Bumping its version up or down? -- :wq
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Thu, Oct 13 2011, Canek Peláez Valdés wrote: What's the output of lspci | grep VGA? oldlap ~ # lspci -v | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller]) And just to cover all the bases: what versions do you have of: xorg-server xorg-drivers mesa [I] x11-base/xorg-server Available versions: 1.9.4 1.9.5 1.10.2 (~)1.10.3 1.10.4 (~)1.11.0 (~)1.11.1 {dmx doc ipv6 kdrive minimal nptl static-libs tslib +udev xnest xorg xvfb} Installed versions: 1.11.1(02:25:02 PM 10/12/2011)(ipv6 nptl udev xorg -dmx -doc -kdrive -minimal -static-libs -tslib -xnest -xvfb) [I] x11-base/xorg-drivers Available versions: 1.9 1.10 (~)1.11 {} Installed versions: 1.11(06:38:40 AM 07/11/2011)(input_devices_evdev input_devices_keyboard input_devices_mouse video_cards_intel video_cards_vesa) [I] media-libs/mesa Available versions: 7.9.2 7.10.2 (~)7.10.2-r1 7.10.3 7.11 {} Installed versions: 7.11(09:39:15 AM 08/15/2011)(classic egl gallium llvm nptl shared-glapi video_cards_intel ) If you are using a newer version of xf86-video-intel, then you are (probably) using unstable X.org. I am not; GNOME 3.2 I had it unmasked, X.org I got it stable. Yes this machine is ~x86 allan
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Thu, Oct 13 2011, Michael Mol wrote: I've skipped most of the thread, so forgive me if this was already done...try rebuilding libmozjs? Bumping its version up or down? oldlap ~ # equery b /usr/lib/libmozjs185.so * Searching for /usr/lib/libmozjs185.so ... dev-lang/spidermonkey-1.8.5 (/usr/lib/libmozjs185.so - libmozjs185.so.1.0) dev-lang/spidermonkey-1.8.5 (/usr/lib/libmozjs185.so.1.0.0) [I] dev-lang/spidermonkey Available versions: 1.7.0 (~)1.7.0-r1 (~)1.7.0-r2 1.8.2.15 {M}(~)1.8.5 {static-libs test threadsafe unicode} Installed versions: 1.8.5(02:22:11 PM 10/12/2011)(-static-libs -test) So the installed version is the only one from gnome3. I tried Calculating dependencies... done! [ebuild UD ] dev-lang/spidermonkey-1.8.2.15 [1.8.5] USE=-threadsafe% (-static-libs%) (-test%) 50,345 kB and received a slot conflict with dev-libs/gjs. I worry trying to downgrade may lead to a string of dependencies. I can try it tonight if desired. thanks, allan
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Thu, Oct 13, 2011 at 9:47 AM, Allan Gottlieb gottl...@nyu.edu wrote: On Thu, Oct 13 2011, Michael Mol wrote: I've skipped most of the thread, so forgive me if this was already done...try rebuilding libmozjs? Bumping its version up or down? oldlap ~ # equery b /usr/lib/libmozjs185.so * Searching for /usr/lib/libmozjs185.so ... dev-lang/spidermonkey-1.8.5 (/usr/lib/libmozjs185.so - libmozjs185.so.1.0) dev-lang/spidermonkey-1.8.5 (/usr/lib/libmozjs185.so.1.0.0) [I] dev-lang/spidermonkey Available versions: 1.7.0 (~)1.7.0-r1 (~)1.7.0-r2 1.8.2.15 {M}(~)1.8.5 {static-libs test threadsafe unicode} Installed versions: 1.8.5(02:22:11 PM 10/12/2011)(-static-libs -test) So the installed version is the only one from gnome3. I tried Calculating dependencies... done! [ebuild UD ] dev-lang/spidermonkey-1.8.2.15 [1.8.5] USE=-threadsafe% (-static-libs%) (-test%) 50,345 kB and received a slot conflict with dev-libs/gjs. I worry trying to downgrade may lead to a string of dependencies. I can try it tonight if desired. Up to you; slot conflicts are outside my area of knowledge for Gentoo. The dmesg error you had suggests to me that the problem may be in libmozjs. It could also be in a badly-built data structure passed *into* libmozjs, though, so I was looking for some differential to see which had the problem. -- :wq
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Thursday, 13. October 2011 09:47:03 Allan Gottlieb wrote: On Thu, Oct 13 2011, Michael Mol wrote: I've skipped most of the thread, so forgive me if this was already done...try rebuilding libmozjs? Bumping its version up or down? oldlap ~ # equery b /usr/lib/libmozjs185.so * Searching for /usr/lib/libmozjs185.so ... dev-lang/spidermonkey-1.8.5 (/usr/lib/libmozjs185.so - libmozjs185.so.1.0) dev-lang/spidermonkey-1.8.5 (/usr/lib/libmozjs185.so.1.0.0) [I] dev-lang/spidermonkey Available versions: 1.7.0 (~)1.7.0-r1 (~)1.7.0-r2 1.8.2.15 {M}(~)1.8.5 {static-libs test threadsafe unicode} Installed versions: 1.8.5(02:22:11 PM 10/12/2011)(-static-libs -test) So the installed version is the only one from gnome3. I tried Calculating dependencies... done! [ebuild UD ] dev-lang/spidermonkey-1.8.2.15 [1.8.5] USE=-threadsafe% (-static-libs%) (-test%) 50,345 kB and received a slot conflict with dev-libs/gjs. I worry trying to downgrade may lead to a string of dependencies. I can try it tonight if desired. hmm, for sure your problem is not video-related then. gjs is the javascript-bindings for gnome... You could try keeping spidermonkey at 1.8.5 and (re-)build the latest version of gjs. google-ing your problem clearly shows: you are not alone. Sadly I was not able to find a solution for your problem yet as most others use ancient versions and updates solved it for them. thanks, allan Best, Michael
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Thu, Oct 13, 2011 at 6:34 AM, Allan Gottlieb gottl...@nyu.edu wrote: On Wed, Oct 12 2011, Michael Schreckenbauer wrote: gnome-shell segfaults. I remember some problems with gnome-shell and GL from the dri-devel-ML. What video-card are you using? Drivers/version? Is there any other WM you can start, execute gnome-shell --replace in a console and dump the output here? Could you try running gnome in fallback-mode? Afaik you can enable this with gsettings set org.gnome.desktop.session session-name gnome-fallback I typed that command as root (no complaints) and restarted gdm (twice). Same problem oldlap ~ # dmesg | grep gnome-shellgnome-shell[3325] general protection ip:b6853dc2 sp:bfdba6d4 error:0 in libmozjs185.so.1.0.0[b6819000+2ca000] gnome-shell[3479] general protection ip:b682bdc2 sp:bf882764 error:0 in libmozjs185.so.1.0.0[b67f1000+2ca000] gnome-shell[24424] general protection ip:b69dcdc2 sp:bfa4c494 error:0 in libmozjs185.so.1.0.0[b69a2000+2ca000] gnome-shell[24440] general protection ip:b6978dc2 sp:bfc21d84 error:0 in libmozjs185.so.1.0.0[b693e000+2ca000] gnome-shell[24563] general protection ip:b6932dc2 sp:bfb993c4 error:0 in libmozjs185.so.1.0.0[b68f8000+2ca000] gnome-shell[24579] general protection ip:b68f1dc2 sp:bf8c52d4 error:0 in libmozjs185.so.1.0.0[b68b7000+2ca000] oldlap ~ # Mmmh. Then the problem is probably not the video. Try reemerging spidermonkey, gjs and gnome-shell; my versions are: [ebuild R #] dev-lang/spidermonkey-1.8.5 USE=-static-libs -test 0 kB [0] [ebuild R #] dev-libs/gjs-1.30.0 USE=examples -test 0 kB [0] [ebuild R #] gnome-base/gnome-shell-3.2.0-r1 0 kB [1] Notice that gjs move to the tree, and so the latest version is outside de overlay. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Thu, Oct 13 2011, Michael Schreckenbauer wrote: hmm, for sure your problem is not video-related then. gjs is the javascript-bindings for gnome... You could try keeping spidermonkey at 1.8.5 and (re-)build the latest version of gjs. google-ing your problem clearly shows: you are not alone. Sadly I was not able to find a solution for your problem yet as most others use ancient versions and updates solved it for them. I tried this (see msg to canek) but it gnome-shell still shows a general protection msg in dmsg oldlap ~ # dmesg | grep gnome-shell gnome-shell[3302] general protection ip:b687ddc2 sp:bf8623e4 error:0 in libmozjs185.so.1.0.0[b6843000+2ca000] gnome-shell[3456] general protection ip:b68d1dc2 sp:bfdf4de4 error:0 in libmozjs185.so.1.0.0[b6897000+2ca000] oldlap ~ # thanks again for helping, allan
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Thu, Oct 13 2011, Canek Peláez Valdés wrote: On Thu, Oct 13, 2011 at 6:34 AM, Allan Gottlieb gottl...@nyu.edu wrote: I typed that command as root (no complaints) and restarted gdm (twice). Same problem oldlap ~ # dmesg | grep gnome-shell gnome-shell[3479] general protection ip:b682bdc2 sp:bf882764 error:0 in libmozjs185.so.1.0.0[b67f1000+2ca000] Mmmh. Then the problem is probably not the video. Try reemerging spidermonkey, gjs and gnome-shell; my versions are: [ebuild R #] dev-lang/spidermonkey-1.8.5 USE=-static-libs -test 0 kB [0] [ebuild R #] dev-libs/gjs-1.30.0 USE=examples -test 0 kB [0] [ebuild R #] gnome-base/gnome-shell-3.2.0-r1 0 kB [1] Notice that gjs move to the tree, and so the latest version is outside de overlay. I rebuilt all three and, as you noted only gnome-shell is from the overlay the other two are in the main tree. Sadly the result is the same: A new reboot still gives oldlap ~ # dmesg | grep gnome-shell gnome-shell[3302] general protection ip:b687ddc2 sp:bf8623e4 error:0 in libmozjs185.so.1.0.0[b6843000+2ca000] gnome-shell[3456] general protection ip:b68d1dc2 sp:bfdf4de4 error:0 in libmozjs185.so.1.0.0[b6897000+2ca000] oldlap ~ # Not sure what to do now other than wait/hope that 3.2.1 (to be released next week) makes it to the overlay and is better for me. allan PS I guess I was lucky with 3.0 since it just worked, at least to the extent that I could log in and play with it.
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Thu, Oct 13, 2011 at 6:20 PM, Allan Gottlieb gottl...@nyu.edu wrote: On Thu, Oct 13 2011, Canek Peláez Valdés wrote: On Thu, Oct 13, 2011 at 6:34 AM, Allan Gottlieb gottl...@nyu.edu wrote: I typed that command as root (no complaints) and restarted gdm (twice). Same problem oldlap ~ # dmesg | grep gnome-shell gnome-shell[3479] general protection ip:b682bdc2 sp:bf882764 error:0 in libmozjs185.so.1.0.0[b67f1000+2ca000] Mmmh. Then the problem is probably not the video. Try reemerging spidermonkey, gjs and gnome-shell; my versions are: [ebuild R #] dev-lang/spidermonkey-1.8.5 USE=-static-libs -test 0 kB [0] [ebuild R #] dev-libs/gjs-1.30.0 USE=examples -test 0 kB [0] [ebuild R #] gnome-base/gnome-shell-3.2.0-r1 0 kB [1] Notice that gjs move to the tree, and so the latest version is outside de overlay. I rebuilt all three and, as you noted only gnome-shell is from the overlay the other two are in the main tree. Sadly the result is the same: A new reboot still gives oldlap ~ # dmesg | grep gnome-shell gnome-shell[3302] general protection ip:b687ddc2 sp:bf8623e4 error:0 in libmozjs185.so.1.0.0[b6843000+2ca000] gnome-shell[3456] general protection ip:b68d1dc2 sp:bfdf4de4 error:0 in libmozjs185.so.1.0.0[b6897000+2ca000] oldlap ~ # Not sure what to do now other than wait/hope that 3.2.1 (to be released next week) makes it to the overlay and is better for me. That's an option, of course. I don't know what else you could try; maybe try the gnome-shell version? I know the crash is happening in spidermonkey, but perhaps te live version of gnome-shell avoids that code path? The code for 3.2.1 cannot be *that* different from the live version. Maybe it's worth a try. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Thu, Oct 13 2011, Canek Peláez Valdés wrote: On Thu, Oct 13, 2011 at 6:20 PM, Allan Gottlieb gottl...@nyu.edu wrote: Not sure what to do now other than wait/hope that 3.2.1 (to be released next week) makes it to the overlay and is better for me. That's an option, of course. I don't know what else you could try; maybe try the gnome-shell version? I know the crash is happening in spidermonkey, but perhaps te live version of gnome-shell avoids that code path? The code for 3.2.1 cannot be *that* different from the live version. Maybe it's worth a try. Regards. - didn't help. I still get the msg in dmesg about gnome-shell failing. I went back to 3.2.0-r1. Another difficulty has arising. I don't seem to be able to get out of fallback mode. Indeed even the command I used to get into fallback before is failing now. I think this should get me out of fallback oldlap ~ # gsettings set org.gnome.desktop.session session-name gnome ** (process:3534): WARNING **: Command line `dbus-launch --autolaunch=a80a835bfa47bbd35544058f000d --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n (msg repeated and snipped by allan) and this is just the command I successfully executed a day or two ago that now fails oldlap ~ # gsettings set org.gnome.desktop.session session-name gnome-fallback ** (process:3540): WARNING **: Command line `dbus-launch --autolaunch=a80a835bfa47bbd35544058f000d --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n (snipped) I should add that the first one above (trying to get back to straight gnome) was tried with the gnome-shell flag for gdm both set and unset. The failure is the same allan
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Tue, Oct 11, 2011 at 9:37 PM, Canek Peláez Valdés can...@gmail.com wrote: On Tue, Oct 11, 2011 at 6:18 PM, Allan Gottlieb gottl...@nyu.edu wrote: On Tue, Oct 11 2011, Canek Peláez Valdés wrote: On Tue, Oct 11, 2011 at 3:13 PM, Allan Gottlieb gottl...@nyu.edu wrote: For me, gnome 3.2 has been quite a regression over 3.0. Weird; for me it works so much better than 3.0. Summary: gdm-3.2.0-r1 crashes and when I revert to the 3.0 gdm, I get to the login screen but then gnome-shell crashes. I tried to downgrade to gnome-shell-3.0.2-r1, but that needs libgnome-menu, which is not in portage/layman. The crash of gdm is described in bug #385525. The crash of gnome-shell is described in the following .xsession-errors file (tracker-miner-fs.log and tracker-store.log are empty). any help would be appreciated. allan Are you running the updated git of gnome-overlay? I had troubles with gnome-settings-daemon until a couple of days. I am running the gnome overlay. I didn't know it had git inside. I am running git 1.7.7. The only packages that won't compile for me (caught by revdep-rebuild are gpointing-device-settings-1.5.1-r2 and totem-plparser-2-32.6). I believe these bugs are not related to the above. Here is the patch to fix totem-pl-parser with the new quvi api https://386651.bugs.gentoo.org/attachment.cgi?id=289447action=diffcollapsed=context=patchformat=rawheaders=1 HTH David
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Tue, Oct 11 2011, Canek Peláez Valdés wrote: On Tue, Oct 11, 2011 at 3:13 PM, Allan Gottlieb gottl...@nyu.edu wrote: For me, gnome 3.2 has been quite a regression over 3.0. Weird; for me it works so much better than 3.0. Summary: gdm-3.2.0-r1 crashes and when I revert to the 3.0 gdm, I get to the login screen but then gnome-shell crashes. I tried to downgrade to gnome-shell-3.0.2-r1, but that needs libgnome-menu, which is not in portage/layman. The crash of gdm is described in bug #385525. The crash of gnome-shell is described in the following .xsession-errors file (tracker-miner-fs.log and tracker-store.log are empty). any help would be appreciated. allan Are you running the updated git of gnome-overlay? I had troubles with gnome-settings-daemon until a couple of days. I believe I have been running the latest overlay. I do an eix-sync every morning and /etc/eix-sync.conf contains -C --ignore-default-opts -C --quiet gnome However, I will run layman --sync-all Can you try to start GNOME with a clean config (no ~/.config, no ~/.local, no ~/.gconf, no ~/.gnome*). I tried that this morning; no improvement Also, in my case, having gnome-shell extensions installed caused me problems when upgrading. I do not have the extensions installed. From the gentoo bug #385525 there is a report that disabling the gnome-shell USE flag for gdm, permits gdm-3.2.0-r1 to run, but does not solve the problem with gnome-shell crashing. I can confirm this behavior and am now running gdm-3.2.0-r1 with gnome-shell disabled. I just now did layman --sync-all emerge --newuse --update --with-bdeps=y world Only libraw and (of course) portage were merged. emerge --depclean found nothing redundant revdep-rebuild still wants to reinstall totem-pl-parser and gpointing-device-settings. Both fail with bugs that (I believe) are unrelated. In a fit of paranoia, I did another reboot at this point. The results were the same: gdm does NOT crash, but gnome-shell DOES Perhaps I have bad USE flags (-gnome-shell is a new change the others are as they have been for quite a while)? oldlap ~ # eix -e gdm; eix -e gnome-shell [I] gnome-base/gdm Available versions: 2.20.11 (~)2.20.11-r1 [M](~)2.32.1 [M](~)2.32.1-r1 {M}(~)3.0.4-r2[1] {M}(~)3.2.0-r1[1] {accessibility afs branding +consolekit debug dmx elibc_glibc fprint gnome-keyring +gnome-shell +introspection ipv6 pam remote selinux smartcard tcpd test xinerama +xklavier} Installed versions: 3.2.0-r1[1](10:55:08 AM 10/12/2011)(accessibility consolekit elibc_glibc introspection ipv6 tcpd xklavier -debug -fprint -gnome-keyring -gnome-shell -selinux -smartcard -test -xinerama) Homepage:http://www.gnome.org/projects/gdm/ Description: GNOME Display Manager [1] gnome /var/lib/layman/gnome [I] gnome-base/gnome-shell Available versions: {M}(~)3.0.2-r1 {M}(~)3.1.4[1] {M}(~)3.2.0-r1[1] {M}**[1] {+nm-applet} Installed versions: 3.2.0-r1[1](10:41:40 PM 10/01/2011) Homepage:http://live.gnome.org/GnomeShell Description: Provides core UI functions for the GNOME 3 desktop [1] gnome /var/lib/layman/gnome oldlap ~ # Thanks for you help and patience, allan
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Wed, Oct 12, 2011 at 8:31 AM, Allan Gottlieb gottl...@nyu.edu wrote: On Tue, Oct 11 2011, Canek Peláez Valdés wrote: On Tue, Oct 11, 2011 at 3:13 PM, Allan Gottlieb gottl...@nyu.edu wrote: For me, gnome 3.2 has been quite a regression over 3.0. Weird; for me it works so much better than 3.0. Summary: gdm-3.2.0-r1 crashes and when I revert to the 3.0 gdm, I get to the login screen but then gnome-shell crashes. I tried to downgrade to gnome-shell-3.0.2-r1, but that needs libgnome-menu, which is not in portage/layman. The crash of gdm is described in bug #385525. The crash of gnome-shell is described in the following .xsession-errors file (tracker-miner-fs.log and tracker-store.log are empty). any help would be appreciated. allan Are you running the updated git of gnome-overlay? I had troubles with gnome-settings-daemon until a couple of days. I believe I have been running the latest overlay. I do an eix-sync every morning and /etc/eix-sync.conf contains -C --ignore-default-opts -C --quiet gnome However, I will run layman --sync-all Can you try to start GNOME with a clean config (no ~/.config, no ~/.local, no ~/.gconf, no ~/.gnome*). I tried that this morning; no improvement Also, in my case, having gnome-shell extensions installed caused me problems when upgrading. I do not have the extensions installed. From the gentoo bug #385525 there is a report that disabling the gnome-shell USE flag for gdm, permits gdm-3.2.0-r1 to run, but does not solve the problem with gnome-shell crashing. I can confirm this behavior and am now running gdm-3.2.0-r1 with gnome-shell disabled. I just now did layman --sync-all emerge --newuse --update --with-bdeps=y world Only libraw and (of course) portage were merged. When you do layman --sync-all, sometimes the ebuilds are updated, but with the same version. Try to recompile every ebuild in the overlay that you have installed in your system. At least, try to recompile gdm, gnome-shell, and all of its direct dependencies, the packages in COMMON_DEPEND, RDEPEND and DEPEND) in the gnome-shell-3.2.0-r1 ebuild. Minus the use enabled where you don't set the use flag, of course. Also: modify /etc/gdm/custom.conf and in the [debug] key set Enable=true. And modify /usr/share/xsessions/gnome.desktop and replace Exec=gnome-session with Exec=gnome-session --debug. Then a lot more info will be available in ~/.xsession-errors, and we will know more. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Wed, Oct 12 2011, David Abbott wrote: Here is the patch to fix totem-pl-parser with the new quvi api https://386651.bugs.gentoo.org/attachment.cgi?id=289447action=diffcollapsed=context=patchformat=rawheaders=1 HTH David Thank you. I follow that bug and know about the patch. Since I don't need totem on that machine, at least for now, I am waiting for this or another patch to make it into the official tree. thanks again, allan
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Wed, Oct 12, 2011 at 1:58 PM, Allan Gottlieb gottl...@nyu.edu wrote: On Wed, Oct 12 2011, Canek Peláez Valdés wrote: When you do layman --sync-all, sometimes the ebuilds are updated, but with the same version. Try to recompile every ebuild in the overlay that you have installed in your system. At least, try to recompile gdm, gnome-shell, and all of its direct dependencies, the packages in COMMON_DEPEND, RDEPEND and DEPEND) in the gnome-shell-3.2.0-r1 ebuild. Minus the use enabled where you don't set the use flag, of course. Recompiles done. No change 1. If gdm maintains its gnome-shell use flag, it crashes 2. If gdm has -gnome-shell in package.use, it runs but gnome-shell (or something else invoked on login with an empty user) crashes Also: modify /etc/gdm/custom.conf and in the [debug] key set Enable=true. And modify /usr/share/xsessions/gnome.desktop and replace Exec=gnome-session with Exec=gnome-session --debug. Then a lot more info will be available in ~/.xsession-errors, and we will know more. Done. Output below (naturally this is with the gnome-shell use flag disabled. I notice that I have the default accessibility use flag on. I am tempted to turn it off to reduce the number of packages involved. Any downside? Not that I know of. Can you please backup /var/lib/gdm, and clean the directory completely? Don't erase the directory, just its contents (including *ALL* the hidden files); gdm needs this directory to start, and it's gid gdm and uid gdm. After you have cleaned it, recompile gdm with the gnome-shell and try again. I still don't see why gnome-shell is not starting, but gdm may have problems with its user config (which is stored in /var/lib/gdm), and *maybe* gnome-shell cannot start correctly if gdm is not built with the gnome-shell use flag. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Wednesday, 12. October 2011 16:58:37 Allan Gottlieb wrote: On Wed, Oct 12 2011, Canek Peláez Valdés wrote: When you do layman --sync-all, sometimes the ebuilds are updated, but with the same version. Try to recompile every ebuild in the overlay that you have installed in your system. At least, try to recompile gdm, gnome-shell, and all of its direct dependencies, the packages in COMMON_DEPEND, RDEPEND and DEPEND) in the gnome-shell-3.2.0-r1 ebuild. Minus the use enabled where you don't set the use flag, of course. Recompiles done. No change 1. If gdm maintains its gnome-shell use flag, it crashes 2. If gdm has -gnome-shell in package.use, it runs but gnome-shell (or something else invoked on login with an empty user) crashes Also: modify /etc/gdm/custom.conf and in the [debug] key set Enable=true. And modify /usr/share/xsessions/gnome.desktop and replace Exec=gnome-session with Exec=gnome-session --debug. Then a lot more info will be available in ~/.xsession-errors, and we will know more. Done. Output below (naturally this is with the gnome-shell use flag disabled. gnome-shell segfaults. I remember some problems with gnome-shell and GL from the dri-devel-ML. What video-card are you using? Drivers/version? Is there any other WM you can start, execute gnome-shell --replace in a console and dump the output here? Could you try running gnome in fallback-mode? Afaik you can enable this with gsettings set org.gnome.desktop.session session-name gnome-fallback thanks again, allan Best, Michael
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Wed, Oct 12 2011, Canek Peláez Valdés wrote: On Wed, Oct 12, 2011 at 1:58 PM, Allan Gottlieb gottl...@nyu.edu wrote: I notice that I have the default accessibility use flag on. I am tempted to turn it off to reduce the number of packages involved. Any downside? Not that I know of. Can you please backup /var/lib/gdm, and clean the directory completely? Don't erase the directory, just its contents (including *ALL* the hidden files); gdm needs this directory to start, and it's gid gdm and uid gdm. I cleaned it. Then built gdm with the gnome-shell flag. This slightly repopulated the directory (see ls -lAR below). After you have cleaned it, recompile gdm with the gnome-shell and try again. I still don't see why gnome-shell is not starting, but gdm may have problems with its user config (which is stored in /var/lib/gdm), and *maybe* gnome-shell cannot start correctly if gdm is not built with the gnome-shell use flag. Regards. gdm again failed (oh no, something has gone wrong) upon restart. To be certain, I did a reboot, gdm failed again, and then *really* cleaned the directory (including the files put there by the emerge) It again failed. I tried an emerge --newuse --update --with-bdeps=y world, this complained because qt-gui didn't have the accessibility flag. So I put back accessibility and redid the update world. As expected only gdm was rebuilt. I restarted gdm (via xdm as usual) and the same failure occurred. I can't get gdm to run with the gnome-shell use flag. What use flags do you have for gdm? Here is mine Installed versions: 3.2.0-r1[1](05:47:00 PM 10/12/2011)(accessibility consolekit elibc_glibc gnome-shell introspection ipv6 tcpd xklavier -debug -fprint -gnome-keyring -selinux -smartcard -test -xinerama) thanks for all your efforts, allan oldlap ~ # cd /var/lib/gdm oldlap gdm # ls -lRA .: total 16 drwxr-xr-x 3 root root 4096 Oct 12 17:26 .config drwxr-x--T 2 root gdm 4096 Oct 12 17:26 .gconf.mandatory -rw-r--r-- 1 root root 365 Oct 12 17:26 .gconf.path drwxr-xr-x 3 root root 4096 Oct 12 17:26 .local ./.config: total 4 drwxr-xr-x 2 gdm gdm 4096 Oct 12 17:26 dconf ./.config/dconf: total 0 ./.gconf.mandatory: total 20 -rw-rT 1 root gdm 16968 Oct 12 17:26 %gconf-tree.xml ./.local: total 4 drwxr-xr-x 3 root root 4096 Oct 12 17:26 share ./.local/share: total 4 drwxr-xr-x 2 gdm gdm 4096 Oct 12 17:26 applications ./.local/share/applications: total 0 oldlap gdm #
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Wed, Oct 12 2011, Michael Schreckenbauer wrote: gnome-shell segfaults. I remember some problems with gnome-shell and GL from the dri-devel-ML. What video-card are you using? Drivers/version? Is there any other WM you can start, execute gnome-shell --replace in a console and dump the output here? Could you try running gnome in fallback-mode? Afaik you can enable this with gsettings set org.gnome.desktop.session session-name gnome-fallback Actually the gnome-shell segfault is the 2nd problem. gdm crashes with Oh no, a problem has occurred unless its gnome-shell use flag is disabled, which could possibly be the cause of gnome-shell failing. Canek has suggested we attack the gdm problem (see other msgs in this thread) and that is the current plan. Unfortunately we are still not there. In bug 385525, those who needed -gnome-shell for gdm could then not get gnome-shell to run (i.e., just like me). It does seem that many are successfully running gdm so I must have something wrong in my setup. What use flags did you build gdm with. Here is mine Installed versions: 3.2.0-r1[1](05:47:00 PM 10/12/2011)(accessibility consolekit elibc_glibc gnome-shell introspection ipv6 tcpd xklavier -debug -fprint -gnome-keyring -selinux -smartcard -test -xinerama) thanks for the help, allan
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Wed, Oct 12, 2011 at 2:53 PM, Allan Gottlieb gottl...@nyu.edu wrote: On Wed, Oct 12 2011, Canek Peláez Valdés wrote: On Wed, Oct 12, 2011 at 1:58 PM, Allan Gottlieb gottl...@nyu.edu wrote: I notice that I have the default accessibility use flag on. I am tempted to turn it off to reduce the number of packages involved. Any downside? Not that I know of. Can you please backup /var/lib/gdm, and clean the directory completely? Don't erase the directory, just its contents (including *ALL* the hidden files); gdm needs this directory to start, and it's gid gdm and uid gdm. I cleaned it. Then built gdm with the gnome-shell flag. This slightly repopulated the directory (see ls -lAR below). After you have cleaned it, recompile gdm with the gnome-shell and try again. I still don't see why gnome-shell is not starting, but gdm may have problems with its user config (which is stored in /var/lib/gdm), and *maybe* gnome-shell cannot start correctly if gdm is not built with the gnome-shell use flag. Regards. gdm again failed (oh no, something has gone wrong) upon restart. To be certain, I did a reboot, gdm failed again, and then *really* cleaned the directory (including the files put there by the emerge) It again failed. The files would reappear everytime you run gdm; they are its configuration files. I tried an emerge --newuse --update --with-bdeps=y world, this complained because qt-gui didn't have the accessibility flag. So I put back accessibility and redid the update world. As expected only gdm was rebuilt. I restarted gdm (via xdm as usual) and the same failure occurred. I can't get gdm to run with the gnome-shell use flag. What use flags do you have for gdm? Here is mine Installed versions: 3.2.0-r1[1](05:47:00 PM 10/12/2011)(accessibility consolekit elibc_glibc gnome-shell introspection ipv6 tcpd xklavier -debug -fprint -gnome-keyring -selinux -smartcard -test -xinerama) thanks for all your efforts, It's really weird; can I see /var/log/messages (or whatever logger file you have)? With Enable=true in the [debug] key on /etc/gdm/custom.conf, we should be able to see why gdm is dying. My flags are: Installed versions: 3.2.0-r1[1](05:20:40 PM 10/11/2011)(consolekit elibc_glibc gnome-keyring gnome-shell introspection ipv6 tcpd xklavier -accessibility -debug -fprint -selinux -smartcard -test -xinerama) Mmmh. I didn't even know you could remove gnome-keyring from gdm. If you are using GNOME, I don't see no reason to disable it. Maybe try it? Anyhow, the logs from gdm failing should tell us something. I don't think is the video, like Michael suggested; supposedly gnome-shell would detect that. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Wednesday, 12. October 2011 18:02:16 Allan Gottlieb wrote: On Wed, Oct 12 2011, Michael Schreckenbauer wrote: gnome-shell segfaults. I remember some problems with gnome-shell and GL from the dri-devel-ML. What video-card are you using? Drivers/version? Is there any other WM you can start, execute gnome-shell --replace in a console and dump the output here? Could you try running gnome in fallback-mode? Afaik you can enable this with gsettings set org.gnome.desktop.session session-name gnome-fallback Actually the gnome-shell segfault is the 2nd problem. gdm crashes with Oh no, a problem has occurred unless its gnome-shell use flag is disabled, which could possibly be the cause of gnome-shell failing. Couldn't it be the other way round? gdm crashes with gnome-shell use-flag set, because gnome-shell segfaults? It runs without the flag, because in this case there's no dep to the shell. Canek has suggested we attack the gdm problem (see other msgs in this thread) and that is the current plan. Unfortunately we are still not there. Imo both problems are related (see above). In bug 385525, those who needed -gnome-shell for gdm could then not get gnome-shell to run (i.e., just like me). It does seem that many are successfully running gdm so I must have something wrong in my setup. What use flags did you build gdm with. Here is mine Installed versions: 3.2.0-r1[1](05:47:00 PM 10/12/2011)(accessibility consolekit elibc_glibc gnome-shell introspection ipv6 tcpd xklavier -debug -fprint -gnome-keyring -selinux -smartcard -test -xinerama) Well, I do not use gnome :) But I am quite good in reading logs, coredumps and things like that :) thanks for the help, allan Best, Michael
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Wednesday, 12. October 2011 15:08:18 Canek Peláez Valdés wrote: Anyhow, the logs from gdm failing should tell us something. I don't think is the video, like Michael suggested; supposedly gnome-shell would detect that. Well Canek, you are wrong about that. http://forums.gentoo.org/viewtopic-p-6833430.html Boot with fallback works for him, also using nouveau instead nvidia-blobs. Regards. Best, Michael
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Wed, Oct 12, 2011 at 3:16 PM, Michael Schreckenbauer grim...@gmx.de wrote: On Wednesday, 12. October 2011 15:08:18 Canek Peláez Valdés wrote: Anyhow, the logs from gdm failing should tell us something. I don't think is the video, like Michael suggested; supposedly gnome-shell would detect that. Well Canek, you are wrong about that. http://forums.gentoo.org/viewtopic-p-6833430.html Boot with fallback works for him, also using nouveau instead nvidia-blobs. Look at that. Then it's possible that gnome-shell is failing with some drivers/cards. The logs from gdm should give us more information. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Wed, Oct 12 2011, Canek Peláez Valdés wrote: It's really weird; can I see /var/log/messages (or whatever logger file you have)? With Enable=true in the [debug] key on /etc/gdm/custom.conf, we should be able to see why gdm is dying. The output is below My flags are: Installed versions: 3.2.0-r1[1](05:20:40 PM 10/11/2011)(consolekit elibc_glibc gnome-keyring gnome-shell introspection ipv6 tcpd xklavier -accessibility -debug -fprint -selinux -smartcard -test -xinerama) Mmmh. I didn't even know you could remove gnome-keyring from gdm. If you are using GNOME, I don't see no reason to disable it. Maybe try it? OK I will add it to my use flags. That machine has profile linux/x86/10.0. My real machine has profile linux/amd64/10.0/desktop/gnome. Clearly the x86 vs amd64 is right, but I could(?) change my profile to desktop/gnome. But that sounds like a big change that could open a can of worms. My main machine (running gnome 2 not 3) has the gnome-keyring use flag for gdm) Anyhow, the logs from gdm failing should tell us something. I don't think is the video, like Michael suggested; supposedly gnome-shell would detect that. I should have said that the video is working. The blue drapery appears for a second before we get the black screen with the oh no msg. Here are the logs (update word with gnome-keyring is running now). thanks, allan Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): GdmSignalHandler: handling signal 15 Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): GdmSignalHandler: Found 1 callbacks Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): GdmSignalHandler: running 15 handler: 0x8061f11 Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): Got callback for signal 15 Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): GsmManager: Logout called Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): GsmShell: Not connected to the shell Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): GsmManager: requesting logout Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): GsmManager: ending phase RUNNING Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): GsmManager: starting phase QUERY_END_SESSION Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): GsmManager: Client /org/gnome/SessionManager/Client1 Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): GsmManager: sending query-end-session to clients (logout mode: forceful) Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): GsmDBusClient: sending QueryEndSession signal to :1.2 Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): GsmManager: adding client to query clients: /org/gnome/SessionManager/Client1 Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): Caught signal 15, shutting down normally. Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): GdmSignalHandler: Done handling signals Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client1 interface=org.gnome.SessionManager.ClientPrivate method=EndSessionResponse Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): GsmDBusClient: got EndSessionResponse is-ok:1 reason= Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): GsmManager: Response from end session request: is-ok=1 do-last=0 cancel=0 reason= Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): GsmManager: query end session complete Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): GsmShell: Not connected to the shell Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): GsmManager: ending phase QUERY_END_SESSION Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): GsmManager: starting phase END_SESSION Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): GsmManager: adding client to end-session clients: /org/gnome/SessionManager/Client1 Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client1 interface=org.gnome.SessionManager.ClientPrivate method=EndSessionResponse Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): GsmDBusClient: got EndSessionResponse is-ok:1 reason= Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): GsmManager: Response from end session request: is-ok=1 do-last=0 cancel=0 reason= Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): GsmManager: ending phase END_SESSION Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): GsmManager: starting phase EXIT Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): GsmManager: stopped client: /org/gnome/SessionManager/Client1 Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): GsmManager: disconnect client: /org/gnome/SessionManager/Client1 Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): GsmManager: in shutdown, not restarting application Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): GsmStore: Unreffing object: 0x80ae508 Oct 12 17:47:42 oldlap gnome-session[3822]: DEBUG(+): GsmClient:
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Wed, Oct 12 2011, Michael Schreckenbauer wrote: On Wednesday, 12. October 2011 18:02:16 Allan Gottlieb wrote: Actually the gnome-shell segfault is the 2nd problem. gdm crashes with Oh no, a problem has occurred unless its gnome-shell use flag is disabled, which could possibly be the cause of gnome-shell failing. Couldn't it be the other way round? gdm crashes with gnome-shell use-flag set, because gnome-shell segfaults? It runs without the flag, because in this case there's no dep to the shell. Does gnome-shell run before a user logs in? Well, I do not use gnome :) But I am quite good in reading logs, coredumps and things like that :) Indeed you are. thanks, allan
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Wed, Oct 12 2011, Allan Gottlieb wrote: Here are the logs (update word with gnome-keyring is running now). The update world (sorry for the typo above) with gnome-keyring finished and again gdm flashes the blue curtain of life before having its oh, no death. The video card is intel, build into X11 no external blob. allan
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Wed, Oct 12, 2011 at 3:27 PM, Allan Gottlieb gottl...@nyu.edu wrote: On Wed, Oct 12 2011, Canek Peláez Valdés wrote: It's really weird; can I see /var/log/messages (or whatever logger file you have)? With Enable=true in the [debug] key on /etc/gdm/custom.conf, we should be able to see why gdm is dying. The output is below My flags are: Installed versions: 3.2.0-r1[1](05:20:40 PM 10/11/2011)(consolekit elibc_glibc gnome-keyring gnome-shell introspection ipv6 tcpd xklavier -accessibility -debug -fprint -selinux -smartcard -test -xinerama) Mmmh. I didn't even know you could remove gnome-keyring from gdm. If you are using GNOME, I don't see no reason to disable it. Maybe try it? OK I will add it to my use flags. That machine has profile linux/x86/10.0. My real machine has profile linux/amd64/10.0/desktop/gnome. Clearly the x86 vs amd64 is right, but I could(?) change my profile to desktop/gnome. But that sounds like a big change that could open a can of worms. My main machine (running gnome 2 not 3) has the gnome-keyring use flag for gdm) Anyhow, the logs from gdm failing should tell us something. I don't think is the video, like Michael suggested; supposedly gnome-shell would detect that. I should have said that the video is working. The blue drapery appears for a second before we get the black screen with the oh no msg. Yeah, but Michael suggested that gnome-shell is crashing with your particular combination of card/drivers. It is possible, for the quick search I did for this problem. What it is true is that gnome-shell is dying when gdm calls it: Oct 12 17:47:48 oldlap gnome-session[15888]: DEBUG(+): GsmXSMPClient: IceProcessMessagesIOError on '0x80aa870 [gnome-shell 106560af3f298b1c44131845606491723015888]' If it is related to the video card/driver that you use, try reemerging cogl and clutter; it doesn't matter that a world upgrade don't want to reemerge it, sometimes the ebuilds change without changing versions. My versions and useflags of cogl and clutter are: # emerge -1pv clutter cogl These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ~] media-libs/cogl-1.8.0 USE=doc examples introspection pango -debug -test 0 kB [1] [ebuild R ~] media-libs/clutter-1.8.0 USE=doc introspection -debug 0 kB [1] Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Wed, Oct 12, 2011 at 3:46 PM, Allan Gottlieb gottl...@nyu.edu wrote: On Wed, Oct 12 2011, Michael Schreckenbauer wrote: On Wednesday, 12. October 2011 18:02:16 Allan Gottlieb wrote: Actually the gnome-shell segfault is the 2nd problem. gdm crashes with Oh no, a problem has occurred unless its gnome-shell use flag is disabled, which could possibly be the cause of gnome-shell failing. Couldn't it be the other way round? gdm crashes with gnome-shell use-flag set, because gnome-shell segfaults? It runs without the flag, because in this case there's no dep to the shell. Does gnome-shell run before a user logs in? Yes: that's the reason it dies on you with the +gnome-shell use flag. Well, I do not use gnome :) But I am quite good in reading logs, coredumps and things like that :) Indeed you are. thanks, allan -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Wed, Oct 12, 2011 at 3:52 PM, Allan Gottlieb gottl...@nyu.edu wrote: On Wed, Oct 12 2011, Allan Gottlieb wrote: Here are the logs (update word with gnome-keyring is running now). The update world (sorry for the typo above) with gnome-keyring finished and again gdm flashes the blue curtain of life before having its oh, no death. The video card is intel, build into X11 no external blob. OK, *that* is weird. What's your card? Mine is: # lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) driver: # eix x11-drivers/xf86-video-intel [I] x11-drivers/xf86-video-intel Available versions: 2.8.1 2.9.1 ~2.10.0-r1 ~2.11.0 2.13.0 2.14.0 2.15.0-r1 ~2.16.0 {debug dri sna} Installed versions: 2.15.0-r1(01:11:05 PM 09/05/2011)(dri) Homepage:http://xorg.freedesktop.org/ Description: X.Org driver for Intel cards Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Wed, Oct 12 2011, Canek Peláez Valdés wrote: If it is related to the video card/driver that you use, try reemerging cogl and clutter; it doesn't matter that a world upgrade don't want to reemerge it, sometimes the ebuilds change without changing versions. My versions and useflags of cogl and clutter are: # emerge -1pv clutter cogl These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ~] media-libs/cogl-1.8.0 USE=doc examples introspection pango -debug -test 0 kB [1] [ebuild R ~] media-libs/clutter-1.8.0 USE=doc introspection -debug 0 kB [1] I had remerged clutter earlier today and just did cogl. Mu use flags are basically the same as yours Calculating dependencies... done! [ebuild R] media-libs/clutter-1.8.0 USE=introspection -debug -doc 0 kB [1] [ebuild R] media-libs/cogl-1.8.0 USE=introspection pango -debug -doc -examples -test 0 kB [1] I am using the same driver as you but a different version (mine is one newer) and I don't have the sna use flag. I might not have access to the machine an longer today, but will try. thanks, allan
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Wed, Oct 12 2011, Allan Gottlieb wrote: On Wed, Oct 12 2011, Canek Peláez Valdés wrote: If it is related to the video card/driver that you use, try reemerging cogl and clutter; it doesn't matter that a world upgrade don't want to reemerge it, sometimes the ebuilds change without changing versions. My versions and useflags of cogl and clutter are: # emerge -1pv clutter cogl These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ~] media-libs/cogl-1.8.0 USE=doc examples introspection pango -debug -test 0 kB [1] [ebuild R ~] media-libs/clutter-1.8.0 USE=doc introspection -debug 0 kB [1] I had remerged clutter earlier today and just did cogl. Mu use flags are basically the same as yours Calculating dependencies... done! [ebuild R] media-libs/clutter-1.8.0 USE=introspection -debug -doc 0 kB [1] [ebuild R] media-libs/cogl-1.8.0 USE=introspection pango -debug -doc -examples -test 0 kB [1] I am using the same driver as you but a different version (mine is one newer) and I don't have the sna use flag. I might not have access to the machine an longer today, but will try. thanks, allan I forgot to say that with the remerged clutter and cogl, gdm still crashes. I just rebuilt the driver downgraded to 2.15.0-r1. I specified sna in package.use but still it was merged without it. This configuration still has gdm crashing [U] x11-drivers/xf86-video-intel Available versions: 2.8.1 2.9.1 (~)2.10.0-r1 (~)2.11.0 2.13.0 2.14.0 2.15.0-r1 (~)2.16.0 {debug dri sna} Installed versions: 2.15.0-r1(09:27:44 PM 10/12/2011)(dri) Homepage:http://xorg.freedesktop.org/ allan
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Wed, Oct 12, 2011 at 6:36 PM, Allan Gottlieb gottl...@nyu.edu wrote: On Wed, Oct 12 2011, Allan Gottlieb wrote: On Wed, Oct 12 2011, Canek Peláez Valdés wrote: If it is related to the video card/driver that you use, try reemerging cogl and clutter; it doesn't matter that a world upgrade don't want to reemerge it, sometimes the ebuilds change without changing versions. My versions and useflags of cogl and clutter are: # emerge -1pv clutter cogl These are the packages that would be merged, in order: Calculating dependencies ... done! [ebuild R ~] media-libs/cogl-1.8.0 USE=doc examples introspection pango -debug -test 0 kB [1] [ebuild R ~] media-libs/clutter-1.8.0 USE=doc introspection -debug 0 kB [1] I had remerged clutter earlier today and just did cogl. Mu use flags are basically the same as yours Calculating dependencies... done! [ebuild R ] media-libs/clutter-1.8.0 USE=introspection -debug -doc 0 kB [1] [ebuild R ] media-libs/cogl-1.8.0 USE=introspection pango -debug -doc -examples -test 0 kB [1] I am using the same driver as you but a different version (mine is one newer) and I don't have the sna use flag. I might not have access to the machine an longer today, but will try. thanks, allan I forgot to say that with the remerged clutter and cogl, gdm still crashes. I just rebuilt the driver downgraded to 2.15.0-r1. I specified sna in package.use but still it was merged without it. This configuration still has gdm crashing [U] x11-drivers/xf86-video-intel Available versions: 2.8.1 2.9.1 (~)2.10.0-r1 (~)2.11.0 2.13.0 2.14.0 2.15.0-r1 (~)2.16.0 {debug dri sna} Installed versions: 2.15.0-r1(09:27:44 PM 10/12/2011)(dri) Homepage: http://xorg.freedesktop.org/ What's the output of lspci | grep VGA? And just to cover all the bases: what versions do you have of: xorg-server xorg-drivers mesa If you are using a newer version of xf86-video-intel, then you are (probably) using unstable X.org. I am not; GNOME 3.2 I had it unmasked, X.org I got it stable. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
[gentoo-user] can't build gnome 3.2 (3.0 was ok)
For me, gnome 3.2 has been quite a regression over 3.0. Summary: gdm-3.2.0-r1 crashes and when I revert to the 3.0 gdm, I get to the login screen but then gnome-shell crashes. I tried to downgrade to gnome-shell-3.0.2-r1, but that needs libgnome-menu, which is not in portage/layman. The crash of gdm is described in bug #385525. The crash of gnome-shell is described in the following .xsession-errors file (tracker-miner-fs.log and tracker-store.log are empty). any help would be appreciated. allan oldlap tracker # cat /home/eva/.xsession-errors /etc/gdm/Xsession: Beginning session setup... which: no keychain in (/usr/local/bin:/usr/bin:/bin:/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/4.1.1:/usr/i686-pc-linux-gnu/gcc-bin/4.5.3:/usr/i686-pc-linux-gnu/gnat-gpl-bin/4.1:/usr/libexec/gnat-gpl/i686-pc-linux-gnu/4.1:/usr/games/bin) /etc/gdm/Xsession: Setup done, will execute: /usr/bin/dbus-launch --exit-with-session /usr/bin/ssh-agent -- gnome-session GNOME_KEYRING_CONTROL=/tmp/keyring-DMA2OM GNOME_KEYRING_PID=5649 GNOME_KEYRING_CONTROL=/tmp/keyring-DMA2OM GNOME_KEYRING_CONTROL=/tmp/keyring-DMA2OM GPG_AGENT_INFO=/tmp/keyring-DMA2OM/gpg:0:1 GNOME_KEYRING_CONTROL=/tmp/keyring-DMA2OM GPG_AGENT_INFO=/tmp/keyring-DMA2OM/gpg:0:1 SSH_AUTH_SOCK=/tmp/keyring-DMA2OM/ssh Initializing tracker-miner-fs... Initializing tracker-store... Tracker-Message: Setting up monitor for changes to config file:'/home/eva/.config/tracker/tracker-miner-fs.cfg' Starting log: File:'/home/eva/.local/share/tracker/tracker-miner-fs.log' Tracker-Message: Setting up monitor for changes to config file:'/home/eva/.config/tracker/tracker-store.cfg' Tracker-Message: Setting up monitor for changes to config file:'/home/eva/.config/tracker/tracker-store.cfg' Starting log: File:'/home/eva/.local/share/tracker/tracker-store.log' Failed to play sound: File or data not found (gnome-shell:5676): Bluetooth-WARNING **: Could not open RFKILL control device, please verify your installation JS LOG: GNOME Shell started at Tue Oct 11 2011 17:23:24 GMT-0400 (EDT) Window manager warning: Log level 16: get_all_cb: couldn't retrieve system settings properties: (25) Launch helper exited with unknown return code 1. gnome-shell-calendar-server[5718]: Got HUP on stdin - exiting gnome-session[5618]: WARNING: Application 'gnome-shell.desktop' killed by signal (gnome-shell:5730): Bluetooth-WARNING **: Could not open RFKILL control device, please verify your installation JS LOG: GNOME Shell started at Tue Oct 11 2011 17:23:25 GMT-0400 (EDT) Window manager warning: Log level 16: get_all_cb: couldn't retrieve system settings properties: (25) Launch helper exited with unknown return code 1. gnome-session[5618]: WARNING: App 'gnome-shell.desktop' respawning too quickly gnome-shell-calendar-server[5738]: Got HUP on stdin - exiting gnome-session[5618]: WARNING: Application 'gnome-shell.desktop' killed by signal (gnome-settings-daemon:5647): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ** Message: Got disconnected from the session message bus; retrying to reconnect every 10 seconds g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Received signal:15-'Terminated'g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. (gdu-notification-daemon:5693): Gdk-WARNING **: gdu-notification-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. OK oldlap tracker #
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Tue, Oct 11, 2011 at 3:13 PM, Allan Gottlieb gottl...@nyu.edu wrote: For me, gnome 3.2 has been quite a regression over 3.0. Weird; for me it works so much better than 3.0. Summary: gdm-3.2.0-r1 crashes and when I revert to the 3.0 gdm, I get to the login screen but then gnome-shell crashes. I tried to downgrade to gnome-shell-3.0.2-r1, but that needs libgnome-menu, which is not in portage/layman. The crash of gdm is described in bug #385525. The crash of gnome-shell is described in the following .xsession-errors file (tracker-miner-fs.log and tracker-store.log are empty). any help would be appreciated. allan Are you running the updated git of gnome-overlay? I had troubles with gnome-settings-daemon until a couple of days. Can you try to start GNOME with a clean config (no ~/.config, no ~/.local, no ~/.gconf, no ~/.gnome*). Just backup your current config and remove it from $HOME, or try to start GNOME with a dummy new user. Also, in my case, having gnome-shell extensions installed caused me problems when upgrading. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Tue, Oct 11, 2011 at 6:30 PM, Canek Peláez Valdés can...@gmail.com wrote: On Tue, Oct 11, 2011 at 3:13 PM, Allan Gottlieb gottl...@nyu.edu wrote: For me, gnome 3.2 has been quite a regression over 3.0. Weird; for me it works so much better than 3.0. Working OK here also, here is my .xsession-errors http://paste.pocoo.org/show/491299/ HTH David
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Tue, Oct 11 2011, Canek Peláez Valdés wrote: On Tue, Oct 11, 2011 at 3:13 PM, Allan Gottlieb gottl...@nyu.edu wrote: For me, gnome 3.2 has been quite a regression over 3.0. Weird; for me it works so much better than 3.0. Summary: gdm-3.2.0-r1 crashes and when I revert to the 3.0 gdm, I get to the login screen but then gnome-shell crashes. I tried to downgrade to gnome-shell-3.0.2-r1, but that needs libgnome-menu, which is not in portage/layman. The crash of gdm is described in bug #385525. The crash of gnome-shell is described in the following .xsession-errors file (tracker-miner-fs.log and tracker-store.log are empty). any help would be appreciated. allan Are you running the updated git of gnome-overlay? I had troubles with gnome-settings-daemon until a couple of days. I am running the gnome overlay. I didn't know it had git inside. I am running git 1.7.7. The only packages that won't compile for me (caught by revdep-rebuild are gpointing-device-settings-1.5.1-r2 and totem-plparser-2-32.6). I believe these bugs are not related to the above. Can you try to start GNOME with a clean config (no ~/.config, no ~/.local, no ~/.gconf, no ~/.gnome*). Just backup your current config and remove it from $HOME, or try to start GNOME with a dummy new user. I can't get to the machine tonight, but will try it tomorrow. Also, in my case, having gnome-shell extensions installed caused me problems when upgrading. I don't have the extensions installed. thanks, allan
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Tue, Oct 11 2011, David Abbott wrote: On Tue, Oct 11, 2011 at 6:30 PM, Canek Peláez Valdés can...@gmail.com wrote: On Tue, Oct 11, 2011 at 3:13 PM, Allan Gottlieb gottl...@nyu.edu wrote: For me, gnome 3.2 has been quite a regression over 3.0. Weird; for me it works so much better than 3.0. Working OK here also, here is my .xsession-errors http://paste.pocoo.org/show/491299/ HTH thanks, allan
Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
On Tue, Oct 11, 2011 at 6:18 PM, Allan Gottlieb gottl...@nyu.edu wrote: On Tue, Oct 11 2011, Canek Peláez Valdés wrote: On Tue, Oct 11, 2011 at 3:13 PM, Allan Gottlieb gottl...@nyu.edu wrote: For me, gnome 3.2 has been quite a regression over 3.0. Weird; for me it works so much better than 3.0. Summary: gdm-3.2.0-r1 crashes and when I revert to the 3.0 gdm, I get to the login screen but then gnome-shell crashes. I tried to downgrade to gnome-shell-3.0.2-r1, but that needs libgnome-menu, which is not in portage/layman. The crash of gdm is described in bug #385525. The crash of gnome-shell is described in the following .xsession-errors file (tracker-miner-fs.log and tracker-store.log are empty). any help would be appreciated. allan Are you running the updated git of gnome-overlay? I had troubles with gnome-settings-daemon until a couple of days. I am running the gnome overlay. I didn't know it had git inside. I am running git 1.7.7. The only packages that won't compile for me (caught by revdep-rebuild are gpointing-device-settings-1.5.1-r2 and totem-plparser-2-32.6). I believe these bugs are not related to the above. No, what I meant to ask was if you have the last snapshot of the overlay. The overlay is a git repository (I believe most overlays are git repositories), and they are updated when you do layman -S (if you use layman). Can you try to start GNOME with a clean config (no ~/.config, no ~/.local, no ~/.gconf, no ~/.gnome*). Just backup your current config and remove it from $HOME, or try to start GNOME with a dummy new user. I can't get to the machine tonight, but will try it tomorrow. Also, in my case, having gnome-shell extensions installed caused me problems when upgrading. I don't have the extensions installed. Then is either a config problem, or there was something funny in the snapshot of the overlay that you used. If the clean config doesn't work, update the overlay from git (or use layman -S) and reemerge all the installed ebuilds inside the overlay. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México