Jump to content
  • 0
Sign in to follow this  
buncls

Moksha GUI will not come up

Question

After a system upgrade (apt-get update && apt-get dist-upgrade) my 4.5.0 installation will not come up with the GUI anymore. I can invoke a console by means of Alt+Fx and run apt-get from there. However the problem persists.

 

As there is no `startx` -command here's the output of ESTART invoked from the console:

ESTART: 0.00000 [0.00000] - Begin Startup
ESTART: 0.00003 [0.00002] - Signal Trap
ESTART: 0.00003 [0.00001] - Signal Trap Done
ESTART: 0.00005 [0.00002] - Eina Init
ESTART: 0.00019 [0.00014] - Eina Init Done
ESTART: 0.00019 [0.00000] - Determine Prefix
[32;1mINF<[0me[32;1m>[0me_prefix.c:25[0m =================================
[32;1mINF<[0me[32;1m>[0me_prefix.c:26[0m Moksha relocation handling
[32;1mINF<[0me[32;1m>[0me_prefix.c:27[0m =================================
[32;1mINF<[0me[32;1m>[0me_prefix.c:28[0m PREFIX:  /usr
[32;1mINF<[0me[32;1m>[0me_prefix.c:29[0m BINDIR:  /usr/bin
[32;1mINF<[0me[32;1m>[0me_prefix.c:30[0m LIBDIR:  /usr/lib/x86_64-linux-gnu
[32;1mINF<[0me[32;1m>[0me_prefix.c:31[0m DATADIR: /usr/share/enlightenment
[32;1mINF<[0me[32;1m>[0me_prefix.c:32[0m LOCALE:  /usr/share/locale
[32;1mINF<[0me[32;1m>[0me_prefix.c:33[0m =================================
ESTART: 0.00028 [0.00009] - Determine Prefix Done
ESTART: 0.00032 [0.00004] - Environment Variables
ESTART: 0.00034 [0.00002] - Environment Variables Done
ESTART: 0.00034 [0.00000] - Parse Arguments
ESTART: 0.00035 [0.00000] - Parse Arguments Done
ESTART: 0.00035 [0.00000] - Eet Init
ESTART: 0.00037 [0.00002] - Eet Init Done
ESTART: 0.00038 [0.00000] - Ecore Init
ESTART: 0.00480 [0.00442] - Ecore Init Done
ESTART: 0.00482 [0.00002] - EIO Init
ESTART: 0.05196 [0.04714] - EIO Init Done
ESTART: 0.05199 [0.00003] - Ecore Event Handlers
ESTART: 0.05200 [0.00001] - Ecore Event Handlers Done
ESTART: 0.05200 [0.00000] - Ecore_File Init
ESTART: 0.05201 [0.00001] - Ecore_File Init Done
ESTART: 0.05201 [0.00000] - Ecore_Con Init
ESTART: 0.05201 [0.00001] - Ecore_Con Init Done
ESTART: 0.05202 [0.00000] - Ecore_Ipc Init
ESTART: 0.05202 [0.00000] - Ecore_Ipc Init Done
ESTART: 0.05203 [0.00001] - Ecore_X Init
<<<< Moksha Error >>>>
Moksha cannot initialize Ecore_X!

E17: Begin Shutdown Procedure!
E - PID=1463, valgrind=0

 

My guess is that

dpkg -r PackageName.deb
or
apt-get install --reinstall PackageName

might do the trick. Can someone advise which package will provide Ecore_X?

 

Or do I need to install the startx -package? Btw, there's no ~/.xinitrc in my home directory?! /etc/X11/xinit/xinputrc only contains

run_im default

and directory /etc/X11/xinit/xinitrc.d/ is empty ....

Share this post


Link to post
Share on other sites

14 answers to this question

Recommended Posts

  • 0

bodhi is usually started from lghtdm. If you installed bodhi such that you needed to enter a password to log in to the desktop GUI, lightdm should start before moksha shows. Doing a search for "cannot initialize Ecore_X" is currently leading me to think that moksha is not being started correctly.

 

For a small bit of reference, my home dir does not contain anything in .xinitrc related to actually starting moksha, so, not having it would not seem to be a problem.

 

Many, many moons ago someone posting here had a "cannot initialize Ecore_X" error and way back then Jeff suggested two things. Make sure everything updated properly and if not try purging and reinstalling everything related to xorg.

 

Fair warning my attempt to assist may do more harm than good. :(

Share this post


Link to post
Share on other sites
  • 0

The error you are seeing there is because you can't just start Moksha directly from the command line. It needs a display server to run on first. Ecore_X is throwing an error cause there is no X server for it to run on.

 

Can you try resetting your ~/.e directory (delete or rename it) and then try to log into Moksha as normal using your display manager?

 

What happens when you try to log in if it isn't logging in properly for you? Did all the updates install properly when you ran your system updates?

  • Like 1

Share this post


Link to post
Share on other sites
  • 0

@birdmun and @Jeff:

Thank you for advising - I will give it another try tomorrow, but will avoid the "purge everything related to xorg" thingie ;)

 

~/.e directory list from another Linux shows:

bunc[~]$ ls -lasc /mnt/sda3/home/bunc/.e
insgesamt 12
4 drwxrwxr-x  3 bunc usrgrp 4096 Dez 10 15:32 .
4 drwxr-xr-x 31 bunc usrgrp 4096 Apr  1 15:43 ..
4 drwxrwxr-x 13 bunc usrgrp 4096 Dez 10 16:04 e
bunc[~]$ ls -lasc /mnt/sda3/home/bunc/.e/e
insgesamt 52
4 drwxrwxr-x 13 bunc usrgrp 4096 Dez 10 16:04 .
4 drwxrwxr-x  3 bunc usrgrp 4096 Dez 10 15:32 ..
4 drwxrwxr-x  9 bunc usrgrp 4096 Dez 10 16:04 applications
4 drwxr-xr-x  2 bunc usrgrp 4096 Dez 10 16:04 backgrounds
4 drwxr-xr-x  3 bunc usrgrp 4096 Mär 28 00:26 config
4 drwxrwxr-x  5 bunc usrgrp 4096 Dez 10 16:04 fileman
4 drwxr-xr-x  2 bunc usrgrp 4096 Dez 10 16:04 fonts
4 drwxr-xr-x  2 bunc usrgrp 4096 Dez 10 16:04 icons
4 drwxrwxr-x  2 bunc usrgrp 4096 Dez 10 15:32 images
4 drwxr-xr-x  2 bunc usrgrp 4096 Dez 10 16:04 input_methods
4 drwxr-xr-x  2 bunc usrgrp 4096 Dez 10 16:04 locale
4 drwxr-xr-x  2 bunc usrgrp 4096 Dez 10 16:04 modules
4 drwxr-xr-x  2 bunc usrgrp 4096 Dez 10 16:04 themes

 

This means all files / directories seem untouched since my initial installation, Dec 10.
 

Can you tell me what is "my" display manager? I did a standard Bodhi install, selecting password for the default user. What if I create a new user from the command line?

 

What happens is that I can see kernel & initrd loading smoothly and the system going multiuser. No GUI login from lightdm or similar! Instead I am left with a blank screen, blinking cursor on the top left. Alt+F1 (F2, F3, ...) will give me a login prompt.

 

All updates installed properly, I still can run sudo apt-get from the commandline.

Share this post


Link to post
Share on other sites
  • 0

lightdm is the default manager as of the last I knew. I am fairly sure either attempting to run lightdm from the CLI or restarting lightdm from the CLI will get you a default manager. And you could always just 

mv /home/$USER/.e /home/$USER/.e.old

and not exactly lose any data. Your desktop, if it loads, will be the default rather than any changes you have made, but, that is a matter of a handful of minutes to reset in my case anyway. :)

 

** I hope I have the $USER written correctly. If $USER doesn't work just replace $USER with your system username.

Share this post


Link to post
Share on other sites
  • 0

If you aren't getting a display manager prompting you to log in then the issue is with lightdm and not actually Moksha.

I don't have any useful suggestion off hand - sorry. Heading out of town on work this weekend. Hopefully someone else has some idea. Maybe a recent Ubuntu update to LightDM messed things up there?

Share this post


Link to post
Share on other sites
  • 0

Thanks to everybody for the help!

 

@birdmun:

I've done that - no change. As Jeff pointed out I guess it's rather an ldm (xorg?) than an enlightenment -problem.

 

@Jeff:

yes, I thinks so too - see further down ...

 

@BeGo:

I did

sudo dpkg-reconfigure ldm

It wouldn't come up with an ncurses dialogue (that's a GDM -example) as on the URL you indicated, but finished successfully after a few seconds. I still do not get into the GUI -login :(

I considered installing Ubuntu's GDM3 -package - to follow the example you gave, but it has a huge number of dependencies (160 MB additional disk space).

I also did a

sudo apt-get install --reinstall ldm

which additionally (re)installed dmz-cursor-theme and gtk2-engines.

 

Here's my /var/log/ldm.log, showing several tries today. Question: is that written during the boot -process?

Apr  8 15:23:02: [ldm] INFO: started on client with IP address: 10.0.0.11
Apr  8 15:23:02: [ldm] INFO: calling rc.d init scripts
Apr  8 15:27:06: [ldm] INFO: started on client with IP address: 10.0.0.11
Apr  8 15:27:06: [ldm] INFO: calling rc.d init scripts
Apr  8 15:31:02: [ldm] INFO: started on client with IP address: 10.0.0.11
Apr  8 15:31:02: [ldm] INFO: calling rc.d init scripts
Apr  8 15:49:45: [ldm] INFO: started on client with IP address: 10.0.0.11
Apr  8 15:49:45: [ldm] INFO: calling rc.d init scripts
Apr  8 15:53:12: [ldm] INFO: started on client with IP address: 10.0.0.11
Apr  8 15:53:12: [ldm] INFO: calling rc.d init scripts

 

Question: 10.0.0.11 - is that Bodhi's default IP address for a client installation?

 

Invoking ldm, as a regular user from the command line gives:

Error: GLib-CRITICAL **: g_strsplit: assertion ...

No such file ...

(ldmtkgreet: 1497): Gtk-Warning **: cannot open display:

segmentation fault ldm   # no core dump in my home directory, probably "ulimit -c 0" in the standard bash settings ;)

 

One reason I can think of is that I use the proprietary driver downloaded from Nvidia rather than noveau or the Ubuntu package. So far this worked out fine.

Finally I have also installed the Ubuntu xinit -package, giving me a startx command. However the latter aborts and I do not feel inclined to construct my custom .xinitrc with all those sections and an `exec enlightenment_start` -command at the end. I thought the days having to do so are over.

 

My last resorts now will be

a )   install GDM and try it instead of LDM

b )  switch to the Ubuntu -provided proprietary Nvidia -driver.

 

Thank you again!

Share this post


Link to post
Share on other sites
  • 0

Last I knew the DM was lightdm and not ldm. Maybe I have no clue what I am talking about.

  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites
  • 0

The one with no clue is me - I thought LDM is just an abbreviation for LightDM.

Thanks for the hint: I will do a reinstall of LightDM, then eventually dpkg-reconfigure lightdm and a service ... stop/start

  • Like 2

Share this post


Link to post
Share on other sites
  • 0

 

16 hours ago, buncls said:

The one with no clue is me - I thought LDM is just an abbreviation for LightDM.

Thanks for the hint: I will do a reinstall of LightDM, then eventually dpkg-reconfigure lightdm and a service ... stop/start

If I am not mistaken, ldm is Lubuntu Display Manager, which should have work. Hmm. :(

Share this post


Link to post
Share on other sites
  • 0

according to   https://en.wikipedia.org/wiki/X_display_manager_(program_type)

LDM, the (remote) Display Manager of the Linux Terminal Server Project   ;)

I guess that's where my 10.0.0.11 came from ....

Some more research, fiddling with service lightdm stop / start (after the dpkg-reconfigure):

/var/log/syslog

Apr 10 16:48:15 astrabodhi systemd[1]: Started Light Display Manager.
Apr 10 16:48:16 astrabodhi acpid: client 4612[0:0] has disconnected
Apr 10 16:48:16 astrabodhi acpid: client connected from 4674[0:0]
Apr 10 16:48:16 astrabodhi acpid: 1 client rule loaded
Apr 10 16:48:16 astrabodhi systemd[1]: Started Session c27 of user lightdm.
Apr 10 16:48:16 astrabodhi systemd[1]: lightdm.service: Main process exited, cod
e=exited, status=1/FAILURE
Apr 10 16:48:16 astrabodhi systemd[1]: lightdm.service: Unit entered failed stat
e.
Apr 10 16:48:16 astrabodhi systemd[1]: lightdm.service: Failed with result 'exit
-code'.
Apr 10 16:48:16 astrabodhi systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Apr 10 16:48:16 astrabodhi systemd[1]: Stopped Light Display Manager.
Apr 10 16:48:16 astrabodhi systemd[1]: gpu-manager.service: Start request repeated too quickly.
Apr 10 16:48:16 astrabodhi systemd[1]: Failed to start Detect the available GPUs and deal with any system changes.
Apr 10 16:48:16 astrabodhi systemd[1]: lightdm.service: Start request repeated too quickly.
Apr 10 16:48:16 astrabodhi systemd[1]: Failed to start Light Display Manager.
Apr 10 16:48:22 astrabodhi acpid: client 4674[0:0] has disconnected
Apr 10 16:49:59 astrabodhi systemd[1]: Stopped Light Display Manager.

/var/log/auth.log

Apr 10 16:48:11 astrabodhi lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so
: cannot open shared object file: No such file or directory
Apr 10 16:48:11 astrabodhi lightdm: PAM adding faulty module: pam_kwallet.so
Apr 10 16:48:11 astrabodhi lightdm: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.
so: cannot open shared object file: No such file or directory
Apr 10 16:48:11 astrabodhi lightdm: PAM adding faulty module: pam_kwallet5.so
Apr 10 16:48:11 astrabodhi lightdm: pam_unix(lightdm-greeter:session): session opened for user lightdm
 by (uid=0)
Apr 10 16:48:11 astrabodhi systemd: pam_unix(systemd-user:session): session opened for user lightdm by
 (uid=0)
Apr 10 16:48:11 astrabodhi systemd-logind[733]: New session c23 of user lightdm.
Apr 10 16:48:11 astrabodhi lightdm: pam_unix(lightdm-greeter:session): session closed for user lightdm
Apr 10 16:48:12 astrabodhi lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so
: cannot open shared object file: No such file or directory
Apr 10 16:48:12 astrabodhi lightdm: PAM adding faulty module: pam_kwallet.so
Apr 10 16:48:12 astrabodhi lightdm: PAM unable to dlopen(pam_kwallet5.so): /lib/
security/pam_kwallet5.so: cannot open shared object file: No such file or directory

So this seems to be LightDM problem indeed, nothing to do with X or Moksha. I am not sure why lightdm would want kwallet, so I might as well give SDDM a try next ...

My search for Display Managers, amongst others, pointed to LXDM, with the following remark in  an Oct. 25, 2014 Wiki:

"LXDM: Currently, Bodhi Linux uses LXDM by default. Arch Linux has packages for LXDM too."  ;)

 

 

  • Like 1

Share this post


Link to post
Share on other sites
  • 0

Thank you Jeff,

I couldn't spend much time on the issue recently, here's my progress as of now:

I decided for LXDM (25 MB disk space), beause SDDM will install > 220 MB and GDM > 165 MB.

It's been a wise :) decision because now I can log in to my Bodhi GUI again. Status is

running:

  • LXDM
  • LXTerm, Terminology
  • Midori
  • WPS office
  • Claws Mail
  • Skype (!)

not running:

  • LightDM
  • ROXTerm
  • Firefox
  • Chromium

Research is somewhat tough, because e.g.Firefox will just not come up, started by a terminal command gives no error message - like "missing xyz.so" etc.

Here's some stuff from /var/log/syslog:

Apr 10 18:18:25 astrabodhi kernel: [ 1578.808986] firefox[3730]: segfault at 0 ip 00007f6ba53134d3 sp 00007fff5a837178 error 6 in libxul.so[7f6ba18ce000+580f000]

Apr 10 19:24:26 astrabodhi org.gnome.zeitgeist.Engine[4169]: #033[31m[17:24:26.779552 WARNING]#033[0m zeitgeist-daemon.vala:329: Failed to execute child process "zeitgeist-datahub" (No such file or directory)

Apr 10 19:20:29 astrabodhi kernel: [ 5303.687588] firefox[4997]: segfault at 0 ip 00007fab6ee134d3 sp 00007ffdd3d330a8 error 6 in libxul.so[7fab6b3ce000+580f000]

Apr 10 19:48:36 astrabodhi python: pam_ecryptfs: seteuid error

and /var/log/auth.log:

Apr 10 18:13:31 astrabodhi lightdm: pam_unix(lightdm-greeter:session): session closed for u
ser lightdm
Apr 10 18:13:32 astrabodhi lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam
_kwallet.so: cannot open shared object file: No such file or directory
Apr 10 18:13:32 astrabodhi lightdm: PAM adding faulty module: pam_kwallet.so
Apr 10 18:13:32 astrabodhi lightdm: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Apr 10 18:13:32 astrabodhi lightdm: PAM adding faulty module: pam_kwallet5.so
Apr 10 18:13:32 astrabodhi lightdm: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Apr 10 18:13:32 astrabodhi systemd-logind[681]: New session c5 of user lightdm.
Apr 10 18:13:32 astrabodhi lightdm: pam_unix(lightdm-greeter:session): session closed for u
ser lightdm
Apr 10 18:15:28 astrabodhi systemd-logind[681]: Removed session c1.
Apr 10 18:15:29 astrabodhi systemd-logind[681]: Removed session c2.
Apr 10 18:15:30 astrabodhi systemd-logind[681]: Removed session c3.
Apr 10 18:15:31 astrabodhi systemd-logind[681]: Removed session c4.
Apr 10 18:15:33 astrabodhi systemd-logind[681]: Removed session c5.
Apr 10 18:15:33 astrabodhi systemd: pam_unix(systemd-user:session): session closed for user  lightdm
Apr 10 18:17:01 astrabodhi CRON[3418]: pam_unix(cron:session): session opened for user root  by (uid=0)

Apr 10 18:17:59 astrabodhi lxdm-session: pam_unix(lxdm:session): session opened for user bunc by (uid=0)
Apr 10 18:17:59 astrabodhi systemd-logind[681]: New session 5 of user bunc.
Apr 10 18:17:59 astrabodhi lxdm-session: pam_systemd(lxdm:session): Cannot create session: Already running in a session
Apr 10 19:11:06 astrabodhi lxdm-session: pam_unix(lxdm:session): session closed for user bunc
Apr 10 19:11:06 astrabodhi lxdm-session: pam_unix(lxdm:session): session closed for user bunc
Apr 10 19:11:06 astrabodhi systemd-logind[681]: Removed session 5.
Apr 10 19:11:23 astrabodhi lxdm-session: pam_unix(lxdm:session): session opened for user bunc by (uid=0)
Apr 10 19:11:23 astrabodhi lxdm-session: pam_unix(lxdm:session): session opened for user bunc by (uid=0)
Apr 10 19:11:23 astrabodhi systemd-logind[681]: New session 6 of user bunc.
Apr 10 19:11:23 astrabodhi lxdm-session: pam_systemd(lxdm:session): Cannot create session: Already running in a session
Apr 10 19:11:24 astrabodhi polkitd(authority=local): Registered Authentication Agent for unix-session:6 (system bus name :1.163 [/usr/bin/lxsession -s LXDE -e LXDE], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale de_AT.UTF-8)

My next shot will be   apt-get install --reinstall pam_auth -stuff

 

 

 

Share this post


Link to post
Share on other sites
  • 0

Does your package manager report all updates installed properly? EG: does running:

sudo apt-get -f install

Do anything for you?

Does the system in question have available hard drive space?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×