Gnome does not start desktop

[polonius]

Fresh Mageia 1 installation of standard Gnome (marked "Gnome" in the desktop selection and let the system install the defaults.
Installation from x86_64 DVD.

After reboot I configured WiFi and set the package media to Cauldron.
Did an upgrade with 'urpmi --auto-update' which worked without problems. After reboot the system told me that it falls back to standard Gnome desktop because I had not installed the proprietary driver of my nvidia. Desktop and applications worked fine. I installed the proprietary driver via MCC->Hardware->Set up graphical server. After reboot I saw the nvidia splash screen and gdm showed.

Here comes the problem:
After login I see the blue striped background, the hd led flickers for 20-25 seconds. Done. No bar, not even hidden (moving mouse to the upper left and right does not do anything).

I checked ~/.xsession-errors and saw lots of warnings and error messages but I can't find out what really causes the problem. I'd like to attach the file .xsession-errors but the forum says, that this extension is not allowed. I changed to "xsession-errors.txt" but this is not allowed either

I guess I can't get help without showing the file, so what can I do?

[doktor5000]

I checked ~/.xsession-errors and saw lots of warnings and error messages but I can't find out what really causes the problem.

The cause of the problem is switching to Cauldron when you're not up to it.
Please read my signature. And if you really want to go on with Cauldron, there
are already forum threads about this problem. FWIW: viewtopic.php?f=15&t=695

[polonius]

The cause of the problem is switching to Cauldron when you're not up to it.
Please read my signature. And if you really want to go on with Cauldron, there
are already forum threads about this problem. FWIW: viewtopic.php?f=15&t=695

I already read that thread, if you read that thread yourself you will see that it is not related. I do not get any message on the screen as described there.
Furthermore you can read that the solution of winstonteacox did not work with latest updates. The symptoms are different, too.

And how is my ability (or lack of) to run cauldron related with the problem to attach the relevant log file to this thread?

[wobo]

I have exactly the same problem here on my laptop as polonius describes.
Maybe I should not use cauldron.

The last messages in ~/.xsession-errors are:

Code: Select all

Cannot open /dev/input/eventX: Permission denied

I can't upload my .xsession-errors neither (why are .txt files not allowed to upload? such files are important for finding solutions!). So I post it in code tags:

Code: Select all

/etc/X11/gdm/Xsession: Beginning session setup...
/etc/X11/gdm/Xsession: ssh-agent not found!
/etc/X11/gdm/Xsession: Setup done, will execute: /usr/share/X11/xdm/Xsession GNOME
localhost being added to access control list
** Message: couldn't connect to dbus session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GNOME_KEYRING_CONTROL=/tmp/keyring-LauEj7
GPG_AGENT_INFO=/tmp/keyring-LauEj7/gpg:0:1
GNOME_KEYRING_PID=2997
** Message: couldn't connect to dbus session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
** Message: couldn't connect to dbus session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
** Message: couldn't connect to dbus session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GNOME_KEYRING_CONTROL=/tmp/keyring-XvmYc7
GNOME_KEYRING_PID=2999
GNOME_KEYRING_CONTROL=/tmp/keyring-RvmYc7
GNOME_KEYRING_PID=3000
GNOME_KEYRING_CONTROL=/tmp/keyring-u7hWb7
SSH_AUTH_SOCK=/tmp/keyring-u7hWb7/ssh
GNOME_KEYRING_PID=3004
Gtk-Message: Failed to load module "pk-gtk-module"

(gnome-settings-daemon:2981): common-plugin-WARNING **: Key 0x1008ffa9 (keycodes:  199)  with state 0x0 (resolved to 0x0)  has no usable modifiers (usable modifiers are 0x140000ed)

(gnome-settings-daemon:2981): common-plugin-WARNING **: Key 0x1008ffb0 (keycodes:  200)  with state 0x0 (resolved to 0x0)  has no usable modifiers (usable modifiers are 0x140000ed)

(gnome-settings-daemon:2981): common-plugin-WARNING **: Key 0x1008ffb1 (keycodes:  201)  with state 0x0 (resolved to 0x0)  has no usable modifiers (usable modifiers are 0x140000ed)

(gnome-settings-daemon:2981): common-plugin-WARNING **: Key 0x1008ff12 (keycodes:  121)  with state 0x0 (resolved to 0x0)  has no usable modifiers (usable modifiers are 0x140000ed)

(gnome-settings-daemon:2981): common-plugin-WARNING **: Key 0x1008ff11 (keycodes:  122)  with state 0x0 (resolved to 0x0)  has no usable modifiers (usable modifiers are 0x140000ed)

(gnome-settings-daemon:2981): common-plugin-WARNING **: Key 0x1008ff13 (keycodes:  123)  with state 0x0 (resolved to 0x0)  has no usable modifiers (usable modifiers are 0x140000ed)

(gnome-settings-daemon:2981): common-plugin-WARNING **: Key 0x1008ff2c (keycodes:  170)  with state 0x0 (resolved to 0x0)  has no usable modifiers (usable modifiers are 0x140000ed)

(gnome-settings-daemon:2981): common-plugin-WARNING **: Key 0x1008ff5d (keycodes:  152)  with state 0x0 (resolved to 0x0)  has no usable modifiers (usable modifiers are 0x140000ed)

(gnome-settings-daemon:2981): common-plugin-WARNING **: Key 0x1008ff32 (keycodes:  234)  with state 0x0 (resolved to 0x0)  has no usable modifiers (usable modifiers are 0x140000ed)

(gnome-settings-daemon:2981): common-plugin-WARNING **: Key 0x1008ff1d (keycodes:  148)  with state 0x0 (resolved to 0x0)  has no usable modifiers (usable modifiers are 0x140000ed)

(gnome-settings-daemon:2981): common-plugin-WARNING **: Key 0x1008ff1b (keycodes:  225)  with state 0x0 (resolved to 0x0)  has no usable modifiers (usable modifiers are 0x140000ed)

(gnome-settings-daemon:2981): common-plugin-WARNING **: Key 0x1008ff19 (keycodes:  223)  with state 0x0 (resolved to 0x0)  has no usable modifiers (usable modifiers are 0x140000ed)

(gnome-settings-daemon:2981): common-plugin-WARNING **: Key 0x1008ff2e (keycodes:  158)  with state 0x0 (resolved to 0x0)  has no usable modifiers (usable modifiers are 0x140000ed)

(gnome-settings-daemon:2981): common-plugin-WARNING **: Key 0x1008ff14 (keycodes:  215)  with state 0x0 (resolved to 0x0)  has no usable modifiers (usable modifiers are 0x140000ed)

(gnome-settings-daemon:2981): common-plugin-WARNING **: Key 0x1008ff31 (keycodes:  209)  with state 0x0 (resolved to 0x0)  has no usable modifiers (usable modifiers are 0x140000ed)

(gnome-settings-daemon:2981): common-plugin-WARNING **: Key 0x1008ff15 (keycodes:  174)  with state 0x0 (resolved to 0x0)  has no usable modifiers (usable modifiers are 0x140000ed)

(gnome-settings-daemon:2981): common-plugin-WARNING **: Key 0x1008ff16 (keycodes:  173)  with state 0x0 (resolved to 0x0)  has no usable modifiers (usable modifiers are 0x140000ed)

(gnome-settings-daemon:2981): common-plugin-WARNING **: Key 0x1008ff17 (keycodes:  171)  with state 0x0 (resolved to 0x0)  has no usable modifiers (usable modifiers are 0x140000ed)

(gnome-settings-daemon:2981): common-plugin-WARNING **: Key 0x1008ff3e (keycodes:  176)  with state 0x0 (resolved to 0x0)  has no usable modifiers (usable modifiers are 0x140000ed)

(gnome-settings-daemon:2981): common-plugin-WARNING **: Key 0x1008ff97 (keycodes:  216)  with state 0x0 (resolved to 0x0)  has no usable modifiers (usable modifiers are 0x140000ed)

(gnome-settings-daemon:2981): common-plugin-WARNING **: Key 0x1008ff59 (keycodes:  235)  with state 0x0 (resolved to 0x0)  has no usable modifiers (usable modifiers are 0x140000ed)

(gnome-settings-daemon:2981): common-plugin-WARNING **: Key 0x1008ff74 (keycodes:  162)  with state 0x0 (resolved to 0x0)  has no usable modifiers (usable modifiers are 0x140000ed)

(gnome-settings-daemon:2981): color-plugin-WARNING **: failed to get edid: unable to get EDID for output

(gnome-settings-daemon:2981): color-plugin-WARNING **: failed to enumerate directory /home/wobo/.color/icc: No such file or directory
Gtk-Message: Failed to load module "pk-gtk-module"
    JS ERROR: !!!   Exception was: Error: Requiring Clutter, version 1.0: Typelib file for namespace 'Atk', version '1.0' not found
    JS ERROR: !!!     lineNumber = '0'
    JS ERROR: !!!     fileName = '"gjs_throw"'
    JS ERROR: !!!     stack = '"("Requiring Clutter, version 1.0: Typelib file for namespace 'Atk', version '1.0' not found")@gjs_throw:0
@/usr/share/gnome-shell/js/ui/environment.js:9
@<main>:1
"'
    JS ERROR: !!!     message = '"Requiring Clutter, version 1.0: Typelib file for namespace 'Atk', version '1.0' not found"'
    JS ERROR: !!!   Exception was: Error: Requiring Clutter, version 1.0: Typelib file for namespace 'Atk', version '1.0' not found
    JS ERROR: !!!     lineNumber = '0'
    JS ERROR: !!!     fileName = '"gjs_throw"'
    JS ERROR: !!!     stack = '"("Requiring Clutter, version 1.0: Typelib file for namespace 'Atk', version '1.0' not found")@gjs_throw:0
@/usr/share/gnome-shell/js/ui/environment.js:9
@<main>:1
"'
    JS ERROR: !!!     message = '"Requiring Clutter, version 1.0: Typelib file for namespace 'Atk', version '1.0' not found"'
Window manager warning: Log level 32: Execution of main.js threw exception: Error: Requiring Clutter, version 1.0: Typelib file for namespace 'Atk', version '1.0' not found
Gtk-Message: Failed to load module "pk-gtk-module"
Gtk-Message: Failed to load module "pk-gtk-module"
Gtk-Message: Failed to load module "pk-gtk-module"
Gtk-Message: Failed to load module "pk-gtk-module"
Failed to play sound: File or data not found
Gtk-Message: Failed to load module "pk-gtk-module"
Gtk-Message: Failed to load module "pk-gtk-module"

(evolution-alarm-notify:3058): GLib-GIO-WARNING **: Your application does not implement g_application_activate() and has no handlers connected to the 'activate' signal.  It should do one of these.
Initializing tracker-store...
Tracker-Message: Checking XDG_DATA_HOME is writable and exists
Tracker-Message:   XDG_DATA_HOME is '(null)'
Initializing tracker-miner-fs...
Tracker-Message: Checking XDG_DATA_HOME is writable and exists
Tracker-Message:   XDG_DATA_HOME is '(null)'
Tracker-Message:   Path is OK
Tracker-Message:   XDG_DATA_HOME set to '/home/wobo/.local/share'
Tracker-Message:   Path is OK
Tracker-Message: Setting up monitor for changes to config file:'/home/wobo/.config/tracker/tracker-store.cfg'
Tracker-Message:   Path is OK
Tracker-Message:   XDG_DATA_HOME set to '/home/wobo/.local/share'
Tracker-Message:   Path is OK
Tracker-Message: Setting process priority
Tracker-Message: Setting up monitor for changes to config file:'/home/wobo/.config/tracker/tracker-miner-fs.cfg'
Deprecated use of my() in false conditional at /usr/bin/mgaapplet line 712.
Deprecated use of my() in false conditional at /usr/bin/mgaapplet line 918.
Tracker-Message: Loading defaults into GKeyFile...
Tracker-Message: Loading defaults into GKeyFile...
Tracker-Message: Setting up monitor for changes to config file:'/home/wobo/.config/tracker/tracker-db.cfg'
Tracker-Message: Loading defaults into GKeyFile...
Tracker-Message: Log verbosity is set to 0, disabling D-Bus client lookup
Starting log:
  File:'/home/wobo/.local/share/tracker/tracker-miner-fs.log'
Starting log:
  File:'/home/wobo/.local/share/tracker/tracker-store.log'
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied

[wobo]

I can't upload my .xsession-errors neither (why are .txt files not allowed to upload? such files are important for finding solutions!).

Found out about this: The only file types allowed are umages and archives - no .txt, no .log nor any plain text format.
I post a follow-up in the forum requests section.

[doktor5000]

Regarding the contents of your .xsession-error, seems many thing are broken.
No dbus, policykit seems missing/not started, ATK not found and some more.
Seems a bigger GNOME update is in progress or something like that.

But there are still other deskop environments as fallback, no?
If you really want to know the cause, ask on mageia-dev ML or on IRC
or search bugzilla. There was an important post in the thread polonius missed maybe:
viewtopic.php?p=4667#p4667

[wobo]

Yes, you know I am following the -dev list, did not read anything related.
Nevertheless I'd have posted this problem here first sooner or later in case somebody knows something that could help. This is a support forum (besides everything else), right? IMHO polonius did not do anything wrong by posting his problem here. (1. search in the forum, 2. ask in the forum, 3. search/ask in the -dev list, 4. report a bug)

I've read all the warnings about the missing things - and I was quite stunned. dbus, policy-kit, should be there in a fresh install, even if this was upgraded to cauldron. And I did not read about anything similar in this forum here.

[polonius]

But there are still other deskop environments as fallback, no?

Not that I know of for someone who is interested in testing Gnome.

(1. search in the forum, 2. ask in the forum, 3. search/ask in the -dev list, 4. report a bug)

This is exactly what I have been doing for a couple of years testing Mandriva Cooker. I may say that IMVVVHO doctor5000 was a bit fast in his assumption that the "cause of the problem is switching to Cauldron when you're not up to it". Although I admit that there are some people where this would be true.

[doktor5000]

Well, maybe that was a fast shot, didn't want to insult anybody.
But we had several occasions where this warning was needed recently.

So i can't help you further, you can only try a "gnome classic" session in GDM.
If you want definitive help or informations, ask on mageia-dev ML or in #mageia-dev or #mageia IRC.

I've done that and it seems at least gnome-shell needs a rebuild.
So with a little bit of luck and patience it'll be fixed in the next few days.

[polonius]

But we had several occasions where this warning was needed recently.

Yes, so I learned while reading some threads No offense taken, I understand that certain people make it hard for you to remain composed all the time.

So i can't help you further, you can only try a "gnome classic" session in GDM.
If you want definitive help or informations, ask on mageia-dev ML or in #mageia-dev or #mageia IRC.
I've done that and it seems at least gnome-shell needs a rebuild.
So with a little bit of luck and patience it'll be fixed in the next few days.

Yes, I'm using gnome classic at the moment, I don't have much time, so I will just watch for gnome related threads in the mageia-dev mailing list and do my daily update dance.

Thx for your efforts

[jkerr82508]

I haven't experienced this problem - the ancient video card in my cauldron box results in Gnome always logging me into the fall-back mode (Gnome Classic). However, when I updated today, there were a number of packages not installed because of file conflicts. When this happens it's usually because there are some updates that have not yet reached the mirrors. I usually just wait a day or two before getting concerned about it.

Jim

[polonius]

I haven't experienced this problem - the ancient video card in my cauldron box results in Gnome always logging me into the fall-back mode (Gnome Classic). However, when I updated today, there were a number of packages not installed because of file conflicts. When this happens it's usually because there are some updates that have not yet reached the mirrors. I usually just wait a day or two before getting concerned about it.

Yes, that's what I'm used to in Cooker as well.
But this specific problem has been on my computer for 3 days before I started to look here. And from the Gnome3 thread in the mageia-dev mailing list I read that wobo had the same problem 2 weeks ago - seems he still has not solved it. So, this seems a bit more than a usual will-be-fixed-later-today.

I'll look at the xsession-errors more closely and try to install what is missing (if it is really missing and not just 'not found').

[wobo]

And from the Gnome3 thread in the mageia-dev mailing list I read that wobo had the same problem 2 weeks ago - seems he still has not solved it.

That is right. I even reinstalled from scratch (Mageia 1 Gnome -> upgrade to Cauldron) but the problem persists. I just did not have the time to really dig into that - gnome is not on top of my priority list.

[wobo]

With todays updates the desktop comes up fine with gnome-shell! I still get the fullscreen error message ("Oh no!...") but closing this message with Alt+F4 lets the system go on.

The downside of it: now wifi does not work anymore (it worked out of the box until today). But this is another problem, asking for another tread.

[am2605]

With todays updates the desktop comes up fine with gnome-shell! I still get the fullscreen error message ("Oh no!...") but closing this message with Alt+F4 lets the system go on.

The downside of it: now wifi does not work anymore (it worked out of the box until today). But this is another problem, asking for another tread.

Did you ever get a solution to the "Oh no!" error? Other than the Alt+F4 one? I am observing the same thing (Gnome 3 on Cauldron installed as a guest OS on VirtualBox under Windows 7).

My .xsession-errors also contains the /dev/input/eventX: Permission denied you were seeing:

Code: Select all

(gnome-shell:8483): Clutter-CRITICAL **: clutter_actor_queue_relayout: assertion `CLUTTER_IS_ACTOR (self)' failed
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied


[ahmad]

The "Cannot open /dev/input/eventX: Permission denied" errors come from net_applet, I don't think they're related to those crashes though.

You can easily test by temporarily stopping it from auto-starting, as user in terminal:

Code: Select all

echo "AUTOSTART=FALSE" >> ~/.net_applet

to make it auto-start again, just delete ~/.net_applet.

Or by right clicking the net_applet icon in the system tray -> Settings, uncheck Always lauch on startup.