| View previous topic :: View next topic |
| Author |
Message |
augustin_meaulnes
Tux's lil' helper
Joined: 21 Oct 2010
Posts: 97
Location: France
|
 Posted: Mon Oct 25, 2010 5:19 am Post subject: [closed] Problem with X and gnome configuration |
 |
|
I was born to Gentoo yesterday and to Gentoo-Gnome this morning. But I am still unable to walk my way alone.
I followed the Installation Gnome Configuration How to and arriving at the "first impression" section | Quote: | First Impressions
Let us first take a look at what we just built. Exit your root shell and log on as a regular user. We will configure our session to run GNOME when we issue the startx command (see also Using startx in the X Server Configuration Howto):
Code Listing 2.7: Having GNOME as default desktop environment
$ echo "exec gnome-session" > ~/.xinitrc
Starting with gnome-base/gnome-session-2.26.2, you will need to prepend the XDG_MENU_PREFIX variable to get the Gnome menus if you're using the ~/.xinitrc method to start your desktop. (If you're not using ~/.xinitrc, it will be handled automatically for you; no additional configuration is needed.)
Code Listing 2.8: Prepending XDG_MENU_PREFIX to ~/.xinitrc
$ sed -i '1i\export XDG_MENU_PREFIX=gnome-' ~/.xinitrc
Now start your graphical environment by running startx:
Code Listing 2.9: Starting GNOME
$ startx
If all goes well, you should be greeted by GNOME. Congratulations. Now let us take a look at how you can configure GNOME to suit your needs. |
I did what I understood as being required
| Quote: | 1- I logged as a regular user
2- Did | Code: | | echo "exec gnome-session" > ~/.xinitrc |
3 - Did | Code: | | sed -i '1i\export XDG_MENU_PREFIX=gnome-' ~/.xinitrc |
4- Did |
After a while I got my first Gnome screen. Marvellous.
Then I went into the next section of the How To and did:
| Code: | 1 -rc-update add xdm default
2- Altered /etc/conf.d/xdm with DISPLAYMANAGER="gdm" |
Remark: to do this I was asked to be root. I tried to enter the root terminal but it refused to display after I entered my root passwd. Thus I exited the graphical session and logged as root to enter the previous commands.
After that i asked for reboot
After the reboot and the display of textual output of the boot sequence I could see a textual log in invite for a short while, then the same again then a message box appeared
| Quote: | | Failed to start the X server (your graphical interface). It is likely that it is not set up correctly. Would you like to view the X server output to diagnose the problem |
the reported troubles are:
| Quote: | (EE) Failed to load module "vesa" (module does not exist,0)
(EE) Failed to load module "fbdev" (module does not exist,0)
(II) [KMS] drm report modesetting isn't supported
FATAL: Module radeon not found
(EE) RADEON(0): [dri] RADEONDRIGetVersion failed to open the DRM
[dri] Disabling DRI |
After that logging as regular user and starting X is OK! I have a graphical environment that seems to be perfect.
But what is the trouble at reboot?
Last edited by augustin_meaulnes on Sun Oct 31, 2010 6:38 pm; edited 2 times in total |
|
| Back to top |
|
 |
DONAHUE
Watchman
Joined: 09 Dec 2006
Posts: 7651
Location: Goose Creek SC
|
| Posted: Mon Oct 25, 2010 5:42 am Post subject: |
|
|
| Code: | | echo 'XSESSION="Gnome"' > /etc/env.d/90xsession |
If gdm not installed, either or try DISPLAYMANAGER="xdm" in /etc/conf.d/xdm[/code] after . IIRC neither xdm nor gdm are installed with the parent packages. |
|
| Back to top |
|
|
cwr
Veteran
Joined: 17 Dec 2005
Posts: 1969
|
| Posted: Mon Oct 25, 2010 7:42 am Post subject: |
|
|
You'll need to run env-update after change /etc/env.d, just to get everything set up right.
I shouldn't worry about the "failure to load" messages as long as you know those modules
are built into the kernel - as for the KMS setting, check /usr/src/linux/.config and see if
there's anything relevant missing ("grep KMS .config" would be a start).
Will |
|
| Back to top |
|
|
augustin_meaulnes
Tux's lil' helper
Joined: 21 Oct 2010
Posts: 97
Location: France
|
| Posted: Mon Oct 25, 2010 9:16 am Post subject: |
|
|
@DONAHUE
Thank you. I remember something like that in one of your message yesterday. Since that moment I have switched from Virtualbox on my Desktop to my laptop.
At the moment, I am waiting for my laptop emerging Openoffice. After that I will try what you suggest.
@cwr
The same to you. |
|
| Back to top |
|
|
augustin_meaulnes
Tux's lil' helper
Joined: 21 Oct 2010
Posts: 97
Location: France
|
| Posted: Mon Oct 25, 2010 4:13 pm Post subject: |
|
|
Hi again,
I did
| Code: | | echo 'XSESSION="Gnome"' > /etc/env.d/90xsession |
then checked that gdm was installed
The problem didn't change at all. Same behavior. |
|
| Back to top |
|
|
DONAHUE
Watchman
Joined: 09 Dec 2006
Posts: 7651
Location: Goose Creek SC
|
| Posted: Mon Oct 25, 2010 4:18 pm Post subject: |
|
|
at the CLI, after gnome has failed to start automatically at boot, first | Code: | | nano .xsession-errors |
see if any interesting items appear, then Let's see if gdm is working.
have you emerged policykit and consolekit?
| Code: | | emerge --info | grep -i USE= |
Are policykit and consolekit in your USE flags?
Is consolekit in the default run level? |
|
| Back to top |
|
|
augustin_meaulnes
Tux's lil' helper
Joined: 21 Oct 2010
Posts: 97
Location: France
|
| Posted: Mon Oct 25, 2010 5:38 pm Post subject: |
|
|
| Quote: | at the CLI, after gnome has failed to start automatically at boot, first
Code:
nano .xsession-errors |
I get the prompt to login. If I log as root | Code: | | nano .xsession-errors |
New file. Idem if I log as regular user.
Already running
| Quote: | | see if any interesting items appear, then |
xserver output still give the messages I had the first time: | Quote: | EE) Failed to load module "vesa" (module does not exist,0)
(EE) Failed to load module "fbdev" (module does not exist,0)
(II) [KMS] drm report modesetting isn't supported
FATAL: Module radeon not found
(EE) RADEON(0): [dri] RADEONDRIGetVersion failed to open the DRM
[dri] Disabling DRI |
| Quote: | | have you emerged policykit and consolekit? |
No. Now I have done.
| Quote: | | Are policykit and consolekit in your USE flags? |
No. Now they are. After that no change.
| Quote: | | Is consolekit in the default run level? |
I don't know how to check and to set that. |
|
| Back to top |
|
|
DONAHUE
Watchman
Joined: 09 Dec 2006
Posts: 7651
Location: Goose Creek SC
|
| Posted: Mon Oct 25, 2010 6:19 pm Post subject: |
|
|
| Code: | | rc-update add consolekit default |
to add consolekit to default run level
to add consolekit and policykit support to packages that can use it. |
|
| Back to top |
|
|
augustin_meaulnes
Tux's lil' helper
Joined: 21 Oct 2010
Posts: 97
Location: France
|
| Posted: Tue Oct 26, 2010 5:28 am Post subject: |
|
|
Hi,
Did | Code: | | rc-update add consolekit default |
andNothing has changed.
BTW should I really ignore the xserver-output messages like | Quote: | EE) Failed to load module "vesa" (module does not exist,0)
(EE) Failed to load module "fbdev" (module does not exist,0)
(II) [KMS] drm report modesetting isn't supported
FATAL: Module radeon not found
(EE) RADEON(0): [dri] RADEONDRIGetVersion failed to open the DRM
[dri] Disabling DRI |
An other point I wonder about:
All the commands you advised me to do have been done logged as root. When I log as regular user I cannot enter them and I cannot use su or sudo (as I come from Ubuntu ,I am used to employing sudo) |
|
| Back to top |
|
|
DONAHUE
Watchman
Joined: 09 Dec 2006
Posts: 7651
Location: Goose Creek SC
|
| Posted: Tue Oct 26, 2010 5:58 am Post subject: |
|
|
| Code: | rc-update del xdm default
reboot |
login as root
login as regular user
did gdm work properly in both cases
Last edited by DONAHUE on Thu Oct 28, 2010 1:25 am; edited 1 time in total |
|
| Back to top |
|
|
augustin_meaulnes
Tux's lil' helper
Joined: 21 Oct 2010
Posts: 97
Location: France
|
| Posted: Tue Oct 26, 2010 6:11 am Post subject: |
|
|
I'll do that as soon as I finish emerging thunderbird.
In the meantime where to read about acquiring superuser rights when logged as regular? |
|
| Back to top |
|
|
DONAHUE
Watchman
Joined: 09 Dec 2006
Posts: 7651
Location: Goose Creek SC
|
|
| Back to top |
|
|
augustin_meaulnes
Tux's lil' helper
Joined: 21 Oct 2010
Posts: 97
Location: France
|
| Posted: Tue Oct 26, 2010 7:09 am Post subject: |
|
|
Thank you for the su link.
I did
| Code: | rc-update del xdm default
reboot |
then logged as "root" and did | Code: | | jaaf-laptop ~ # gdm |
there were 2 attempts then the xserver-message box with the messages I transmitted before appeared , then after closing the box only the jaaf-laptop ~ # prompt.
After that I did and logged as "jaff" (regular), did | Code: | | jaaf@jaaf-laptop ~$ gdm |
I got the following message (repetition) | Quote: | jaaf@jaaf-laptop ~$ gdm
gdm [12587] GDM file gdm-daemon-config.c line 2041 (); Cannot run seteuid to 0: operation not permitted
gdm gdm [12587] GDM file gdm-daemon-config.c line 2041 (); Cannot run seteuid to 0: operation not permitted
jaaf@jaaf-laptop ~$ |
|
|
| Back to top |
|
|
DONAHUE
Watchman
Joined: 09 Dec 2006
Posts: 7651
Location: Goose Creek SC
|
| Posted: Wed Oct 27, 2010 4:20 am Post subject: |
|
|
looking like some sort of gdm configuration problem.
this should not occur. out of the box gdm works fine here.
you might confirm problem location by , change to DISPLAYMANAGER="xdm" in /etc/conf.d/xdm, | Code: | rc-update add xdm default
reboot |
a defaults.conf file is at /usr/share/gdm/defaults.conf |
|
| Back to top |
|
|
augustin_meaulnes
Tux's lil' helper
Joined: 21 Oct 2010
Posts: 97
Location: France
|
| Posted: Wed Oct 27, 2010 6:31 am Post subject: |
|
|
I did what you say just before receiving your mail but also changing | Code: | | DISPLAYMANAGER="xdm" |
in /etc/conf.d/xdm and rebooting I got a good xdm screen the a normal start of the Gnome graphical session. There was only a problem with the keyboard which was US instead of French (anoying when you must enter a password).
After that I restored | Code: | | XDISPLAYMANAGER="gdm" |
and I retreived the previous problem.
Here is a copy of /usr/share/gdm/defaults.conf
| Quote: |
[daemon]
AutomaticLoginEnable=false
AutomaticLogin=
TimedLoginEnable=false
TimedLogin=
TimedLoginDelay=30
Greeter=/usr/libexec/gdmgreeter
User=gdm
Group=gdm
LogDir=/var/log/gdm
PostLoginScriptDir=/etc/X11/gdm/PostLogin/
PreSessionScriptDir=/etc/X11/gdm/PreSession/
PostSessionScriptDir=/etc/X11/gdm/PostSession/
DisplayInitDir=/etc/X11/gdm/Init
XKeepsCrashing=/etc/X11/gdm/XKeepsCrashing
RebootCommand=/usr/bin/reboot;/sbin/reboot;/sbin/shutdown -r now;/usr/sbin/shutdown -r now
HaltCommand=/usr/bin/poweroff;/sbin/poweroff;/sbin/shutdown -h now;/usr/sbin/shutdown -h now
SuspendCommand=
SystemCommandsInMenu=HALT;REBOOT;SUSPEND;CUSTOM_CMD
AllowLogoutActions=HALT;REBOOT;SUSPEND;CUSTOM_CMD
RBACSystemCommandKeys=
ServAuthDir=/var/gdm
BaseXsession=/etc/X11/gdm/Xsession
UserAuthDir=
UserAuthFBDir=/tmp
UserAuthFile=.Xauthority
StandardXServer=/usr/bin/X
Xnest=/usr/bin/Xephyr -audit 0
XnestUnscaledFontPath=true
GdmXserverTimeout=10
[security]
AllowRoot=true
AllowRemoteRoot=false
AllowRemoteAutoLogin=false
RelaxPermissions=0
CheckDirOwner=true
SupportAutomount=false
PamStack=gdm
UtmpLineAttached=/dev/console
UtmpLineRemote=
UtmpPseudoDevice=false
[xdmcp]
Enable=false
[gui]
GtkTheme=Clearlooks
[greeter]
Browser=false
MinimalUID=1000
IncludeAll=true
DefaultWelcome=true
DefaultRemoteWelcome=true
BackgroundColor=#76848F
GraphicalThemedColor=#76848F
GraphicalThemeDir=/usr/share/gdm/themes/
GraphicalThemeRand=false
PreFetchProgram=/usr/lib/gdmprefetch @/etc/X11/gdm/gdmprefetchlist
[chooser]
HostImageDir=/usr/share/hosts/
Hosts=
Broadcast=true
Multicast=false
[debug]
Enable=false
Gestures=false
[servers]
0=Standard device=/dev/console
[server-Standard]
name=Standard server
command=/usr/bin/X -audit 0
flexible=true
[server-Terminal]
name=Terminal server
command=/usr/bin/X -audit 0 -terminate
flexible=false
handled=false
[server-Chooser]
name=Chooser server
command=/usr/bin/X -audit 0
flexible=false
chooser=true
[customcommand]
|
|
|
| Back to top |
|
|
DONAHUE
Watchman
Joined: 09 Dec 2006
Posts: 7651
Location: Goose Creek SC
|
| Posted: Wed Oct 27, 2010 12:53 pm Post subject: |
|
|
Looks relevant:
yours: AutomaticLoginEnable=false
mine: #AutomaticLoginEnable=false
relevance ?
yours:[servers]
0=Standard device=/dev/console
Mine:[servers]
irrelevant:
yours:PreFetchProgram=/usr/lib/gdmprefetch @/etc/X11/gdm/gdmprefetchlist
mine:PreFetchProgram=/usr/lib64/gdmprefetch @/etc/X11/gdm/gdmprefetchlist
There is also /etc/X11/gdm/custom.conf; mine is all comments or section titles. |
|
| Back to top |
|
|
augustin_meaulnes
Tux's lil' helper
Joined: 21 Oct 2010
Posts: 97
Location: France
|
| Posted: Wed Oct 27, 2010 3:07 pm Post subject: |
|
|
Tried the first 2 items separately then together. The result is no change at all.
Difference in /etc/X11/gdm/custom.conf
| Quote: | | GraphicalTheme=gentoo-emergence. |
|
|
| Back to top |
|
|
DONAHUE
Watchman
Joined: 09 Dec 2006
Posts: 7651
Location: Goose Creek SC
|
| Posted: Thu Oct 28, 2010 3:01 am Post subject: |
|
|
try running the following as root: You may not have a /home/root directory, if so skip those lines. You may have added more than one username, repeat as necessary to do them all.
| Code: | rm /home/root/.serverauth*
rm /home/root/.ICEauthority
rm /home/root/.Xauthority
rm /root/.serverauth*
rm /root/.ICEauthority
rm /root/.Xauthority
rm /home/yourusername/.serverauth*
rm /home/yourusername/.ICEauthority
rm /home/yourusername/.Xauthority |
Then |
|
| Back to top |
|
|
augustin_meaulnes
Tux's lil' helper
Joined: 21 Oct 2010
Posts: 97
Location: France
|
| Posted: Thu Oct 28, 2010 11:06 am Post subject: |
|
|
I did:
Only the last 2 lines removed some file; the for the others there was no such file or directory
Problem remains the same after reboot. |
|
| Back to top |
|
|
DONAHUE
Watchman
Joined: 09 Dec 2006
Posts: 7651
Location: Goose Creek SC
|
| Posted: Fri Oct 29, 2010 1:36 am Post subject: |
|
|
Hail mary: unmerge gnome and gdm, if in gui, view->hidden files, delete everything that appears connected in any way to gnome or gdm in /root and /home/username
if at cli, to identify gnome and/or gdm related files and directories, then rm them
| Code: | rm -rf /usr/share/gdm
rm -rf /usr/share/gnome*
reboot |
back up at CLI, as root, stay as root, |
|
| Back to top |
|
|
augustin_meaulnes
Tux's lil' helper
Joined: 21 Oct 2010
Posts: 97
Location: France
|
| Posted: Fri Oct 29, 2010 4:33 am Post subject: |
|
|
Did all what you told me but now emerge gnome gdm fails.
Here is screen output . Is it normal that I still have access to a graphical session with Gome?
| Quote: | Calculating dependencies .... done!
>>> Verifying ebuild manifests
>>> Starting parallel fetch
>>> Emerging (1 of 2) gnome-base/gdm-2.20.11
* gdm-2.20.11.tar.bz2 RMD160 SHA1 SHA256 size  ... [ ok ]
* gdm-2.20.9-gentoo-files-r1.tar.bz2 RMD160 SHA1 SHA256 size ... [ ok ]
* gentoo-gdm-theme-r3.tar.bz2 RMD160 SHA1 SHA256 size ... [ ok ]
* checking ebuild checksums ... [ ok ]
* checking auxfile checksums ... [ ok ]
* checking miscfile checksums ... [ ok ]
* CPV: gnome-base/gdm-2.20.11
* REPO: gentoo
* USE: branding consolekit elibc_glibc gnome-keyring ipv6 kernel_linux pam tcpd userland_GNU x86
>>> Unpacking source...
>>> Unpacking gdm-2.20.11.tar.bz2 to /var/tmp/portage/gnome-base/gdm-2.20.11/work
>>> Unpacking gdm-2.20.9-gentoo-files-r1.tar.bz2 to /var/tmp/portage/gnome-base/gdm-2.20.11/work
>>> Unpacking gentoo-gdm-theme-r3.tar.bz2 to /var/tmp/portage/gnome-base/gdm-2.20.11/work
>>> Source unpacked in /var/tmp/portage/gnome-base/gdm-2.20.11/work
>>> Preparing source in /var/tmp/portage/gnome-base/gdm-2.20.11/work/gdm-2.20.11 ...
* Fixing OMF Makefiles ...
[ ok ]
* Running elibtoolize in: gdm-2.20.11/
* Applying portage-1.5.10.patch ...
* Applying max_cmd_len-1.5.20.patch ...
* Applying sed-1.5.6.patch ...
* Applying as-needed-1.5.patch ...
* Applying gdm-2.13.0.1-selinux-remove-attr.patch ...
[ ok ]
* Applying gdm-2.20.2-gksu.patch ...
[ ok ]
* Applying gdm-2.20.9-parallel-make.patch ...
[ ok ]
* Applying gdm-2.20.10-custom-session.patch ...
[ ok ]
* Applying gdm-2.20.10-xinitrc-ssh-agent.patch ...
[ ok ]
* Applying gdm-2.20.10-desktop-session-dmrc-autologin.patch ...
[ ok ]
* Applying gdm-2.20.10-gdmsetup-24hr-combo.patch ...
[ ok ]
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/gnome-base/gdm-2.20.11/work/gdm-2.20.11 ...
* econf: updating gdm-2.20.11/config.sub with /usr/share/gnuconfig/config.sub
* econf: updating gdm-2.20.11/config.guess with /usr/share/gnuconfig/config.guess
./configure --prefix=/usr --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --with-prefetch --sysconfdir=/etc/X11 --localstatedir=/var --with-xdmcp=yes --with-pam-prefix=/etc SOUND_PROGRAM=/usr/bin/gdmplay --disable-xevie --enable-ipv6 --disable-secureremote --with-console-kit --without-dmx --without-selinux --with-tcp-wrappers --without-xinerama --enable-authentication-scheme=pam
configure: WARNING: unrecognized options: --disable-xevie
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for style of include used by make... GNU
checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether i686-pc-linux-gnu-gcc accepts -g... yes
checking for i686-pc-linux-gnu-gcc option to accept ISO C89... none needed
checking dependency style of i686-pc-linux-gnu-gcc... gcc3
checking how to run the C preprocessor... i686-pc-linux-gnu-gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking whether NLS is requested... yes
checking for intltool >= 0.35.0... 0.41.1 found
checking for intltool-update... /usr/bin/intltool-update
checking for intltool-merge... /usr/bin/intltool-merge
checking for intltool-extract... /usr/bin/intltool-extract
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/gmsgfmt
checking for perl... /usr/bin/perl
checking for perl >= 5.8.1... 5.12.2
checking for XML::Parser... configure: error: XML::Parser perl module is required for intltool
!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/gnome-base/gdm-2.20.11/work/gdm-2.20.11/config.log
* ERROR: gnome-base/gdm-2.20.11 failed:
* econf failed
*
* Call stack:
* ebuild.sh, line 54: Called src_configure
* environment, line 3158: Called gnome2_src_configure
* environment, line 2347: Called econf '--with-prefetch' '--sysconfdir=/etc/X11' '--localstatedir=/var' '--with-xdmcp=yes' '--with-pam-prefix=/etc' 'SOUND_PROGRAM=/usr/bin/gdmplay' '--disable-xevie' '--enable-ipv6' '--disable-secureremote' '--with-console-kit' '--without-dmx' '--without-selinux' '--with-tcp-wrappers' '--without-xinerama' '--enable-authentication-scheme=pam'
* ebuild.sh, line 544: Called die
* The specific snippet of code:
* die "econf failed"
*
* If you need support, post the output of 'emerge --info =gnome-base/gdm-2.20.11',
* the complete build log and the output of 'emerge -pqv =gnome-base/gdm-2.20.11'.
* The complete build log is located at '/var/tmp/portage/gnome-base/gdm-2.20.11/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/gnome-base/gdm-2.20.11/temp/environment'.
* S: '/var/tmp/portage/gnome-base/gdm-2.20.11/work/gdm-2.20.11'
>>> Failed to emerge gnome-base/gdm-2.20.11, Log file:
>>> '/var/tmp/portage/gnome-base/gdm-2.20.11/temp/build.log'
* Messages for package gnome-base/gdm-2.20.11:
|
|
|
| Back to top |
|
|
DONAHUE
Watchman
Joined: 09 Dec 2006
Posts: 7651
Location: Goose Creek SC
|
| Posted: Fri Oct 29, 2010 5:37 am Post subject: |
|
|
I have gotten you caught by the peculiar way perl updates are handled. Got me 2 days ago.
Gather some tools:
| Code: | | emerge perl-cleaner python-updater lafilefixer gentoolkit portage-utils |
then apply the tools:
| Code: | perl-cleaner --all
python-updater
lafilefixer --justfixit
revdep-rebuild |
Try again:
| Code: | emerge gnome gdm
reboot |
|
|
| Back to top |
|
|
augustin_meaulnes
Tux's lil' helper
Joined: 21 Oct 2010
Posts: 97
Location: France
|
| Posted: Fri Oct 29, 2010 8:44 am Post subject: |
|
|
Did all the stuff.
No change. |
|
| Back to top |
|
|
DONAHUE
Watchman
Joined: 09 Dec 2006
Posts: 7651
Location: Goose Creek SC
|
| Posted: Sat Oct 30, 2010 2:01 am Post subject: |
|
|
| Code: | perl-cleaner --reallyall
emerge -1 XML-Parser
emerge -1 intltool
emerge gdm |
assuming emerge gdm goes, note at the end says:
| Quote: | * To make GDM start at boot, edit /etc/conf.d/xdm
* and then execute 'rc-update add xdm default'.
* GDM has changed the location of its configuration file. Please
* edit /etc/X11/gdm/custom.conf. The factory defaults are located
* at /usr/share/gdm/{defaults.conf,factory-defaults.conf}
* See README.install for more information about the change.
* For autologin to unlock your keyring, you need to set an empty
* password on your keyring. Use app-crypt/seahorse for that.
|
I would swear I never had to do this, but it sounds like a very possible cause of your original problem. |
|
| Back to top |
|
|
augustin_meaulnes
Tux's lil' helper
Joined: 21 Oct 2010
Posts: 97
Location: France
|
| Posted: Sat Oct 30, 2010 7:54 am Post subject: |
|
|
Hi Donahue,
I would like to thank you very much for you patient help.
I apologize but your patience is more strong than mine.
I"ll probably will read you messages again a lot of time in my future attempts to install Gentoo correctly. But at the moment, I feel there is so huge a gap between your cleverness and mine that I am just applying your advices without understanding what I am actually doing.
So I have decided to restart from scratch paying more attention to some aspects I was not aware at all when I started this first attempt. I also need a deep and careful reading of the documentation on the various tools you suggested me to make use of.
I am sure you understand, it is more important for a beginner to have a clear vision of what happens than to setup a functional system without understanding how he could manage to get it. I already have one with Ubuntu thus it's not my target.
So, I will take time to read and understand more. Be aware, in that respect, that all what you told me, already forced me to investigate into the documentation on the Gentoo site as well as in other resources. Light is coming at it's own pace but it's coming.
I will assuredly start other threads on this forum but probably on more basic things like configuring and compiling a kernel and incrementally modify it or using the basic tools.
I hope I didn't fail to meet your expectations as a teacher and that we will meet again soon.
With kind regards |
|
| Back to top |
|
|
|
Installing Gentoo
