Gnome is not opening

Carl_cj · 09-12-2016, 09:48 AM

Hello there,

After completing section 33 and 34 in BLFS 7.10 systemd edition(stable)
i try to run gnome-session it goes to blank screen after that it gives me the following error :

Quote:

dbus-update-activation-environment:error : unable to connect to D-Bus:
Unable to autolaunch a dbus-daemon without a $DISPLAY for x11
gnome-session-binary[2855]:WARNING: using null backend for session tracking
gnome-session-binary[2855]:WARNING: unable to find required component
'org.gnome.Shell'unable to init server:could not connect: Connection refused
** (gnome-session-failed:2867): WARNING **:cannot open display

my .xinitrc file contains

Code:

dbus-launch --exit-with-session gnome-session

i am do

Code:

echo gnome-session > ~/.xinitrc

then again do startx but no use agian it goes to the blank and gives the above error.

however i am installing fluxbox it works fine.
but gnome is not working.
could anybody please guide me how to solve this error thanks in advance.

anak_bawang · 09-13-2016, 07:38 PM

I also have problem with gnome. Maybe this could help you.

gdm-3.18.2 screen flicker

Still not solving the problem, but probably could give you some clue.

Carl_cj · 09-14-2016, 12:08 PM

Quote:

Originally Posted by anak_bawang

I also have problem with gnome. Maybe this could help you.

gdm-3.18.2 screen flicker

Still not solving the problem, but probably could give you some clue.

Thanks for the reply,
When I tried to start gdm service I am getting the error

Quote:

Failed to start gdm.service:Launch helper exited with unknown return code 1
See system logs and 'systemctl gdm.service' for details.

anak_bawang · 09-14-2016, 08:31 PM

Quote:

Originally Posted by Carl_cj

Code:

Failed to start gdm.service:Launch helper exited with unknown return code 1
See system logs and 'systemctl gdm.service' for details.

Probably because of gnome-settings-daemon can not connect to dbus or cannot load some plugin.
Can you post the output of systemctl status gdm.service

Ratamahatta · 10-07-2016, 05:22 PM

After one month, this most likely is fixed already but:

Looks to me like the Screen might not be set. For startx you'd call something like "startx gnome-sesson -- :0" to select display 0 (typically reachable from a tty via strg-alt-f7). (You can start another one with ":1" (strg-alt-f8.))

I've had strange behaviour on the Ubuntu nonsense when the HDMI connection wasn't proper. (They were a lot less strange with Aptosid. But that distro seems to be dead.) Try removing and re-attaching the HDMI/DVI/(S)VGA cable both on the monitor and on the pc side.