After upgrading, Sabayon can not start gdm

[wxjeacen]

My Sabayon version is Sabayon 7 with Gnome as desktop.

After fresh installation with CD image, I just could not access X window for login.

And I accessed console and found that there is an error in file /var/log/messages/

Unable to open '/etc/dconf/db/gdm', specified in dconf profile

Any suggestion for work round?

Thanks in a great deal.

[albfneto]

try re-installing the GDM package,

[Eisenhorn]

I had a similar problem, that after updating with entropy gdm wouldn't start with the same error message.
The following command solved this problem

Code: Select all

equo update && equo upgrade

BR

[Revolver]

Same problem but after update and upgrade the problem still remains...

i try to use equo libtest and deptest but without success...

i have already tried to update to new kernel 3.1 but i'm still stuck..

any ideas?

[wolfden]

Same problem but after update and upgrade the problem still remains...

i try to use equo libtest and deptest but without success...

i have already tried to update to new kernel 3.1 but i'm still stuck..

any ideas?

tried to update to new kernel? did or didn't you? did you use the kernel-switcher so all deps of kernel pulled too? What the log files say?

[Revolver]

i've installed kernel 3.1-r2.

i've reinstalled intel graphics drivers. I've got a dell Inspiron 1510.

this is the error that i have when i try to start gdm

Code: Select all

failed to acquire org.gnome.displaymanager

i googoled to find some help and seems like that there is some bug in gnome 3.2.

Now i try to install limbo repo and sabayon.com repo and make an upgrade.

Wolf tell me what log file you need to read.

And where i can find how to use kernel-switcher, or can you tell me what commands i have to use?

Thnx!

[wolfden]

upgrading kernel via entropy is in our wiki

there should also be a gdm log file

how did you upgrade kernel? did you also install the needed kernel modules/drivers? is the correct opengl setting set?

When you upgrade kernels you always need to make sure the corresponding modules/drivers get installed with it and to make sure you graphics driver is properly set.

[Revolver]

yes i know it!

The problem is that the problem is the same with the 2.9.39 kernel (that is always worked for me).

The problem is due to the updates that I have done 2 days ago!

So i try to switch to new kernel (i will check the wiki).

To upgrade to new kernel i've used the following command:

Code: Select all

equo install sys-kernel/sabayon-kernel-3.1.0-r2

And it has installed ONLY the kernel files (no module or other).

But the problem is not the kernel but the upgrades (actually after the updates with .39 kernel the laptop didn't log into gnome session).

i try to check the gdm log files this evening.

[sabayonino]

yes i know it!

The problem is that the problem is the same with the 2.9.39 kernel (that is always worked for me).

The problem is due to the updates that I have done 2 days ago!

So i try to switch to new kernel (i will check the wiki).

To upgrade to new kernel i've used the following command:

Code: Select all

equo install sys-kernel/sabayon-kernel-3.1.0-r2

And it has installed ONLY the kernel files (no module or other).

But the problem is not the kernel but the upgrades (actually after the updates with .39 kernel the laptop didn't log into gnome session).

i try to check the gdm log files this evening.

You had installed kernel package only without its modules. please run kernel-switcher to upgrade kernel and modules and updating grub line

Code: Select all

# kernel-switcher switch sys-kernel/sabayon-kernel-3.1.0-r2

reboot and Good Luck

[wolfden]

Yea, see that is the problem, the problem is the user not knowing how to upgrade the kernels nor use the package manager properly. By the sounds of it you have a mix match kernel/package system. Not to sound mean or anything, but when a user is going to touch the kernel, they should know what they are doing. We had to remove the automatic updating of kernels as people were fubaring their systems and going on riots. Now it takes user intervention to do it, so a user should know about the kernel before touching it.

Always remember your kernel version has to match your modules/drivers, otherwise stuff don't work. All a learning process I guess. I just wish people would check documentation more.