[gentoo-user] LXDE startup error

[Peter Humphrey]

Hello list,

I've just finished (well, you know) installing Gentoo on a new box and given
it an LXDE desktop. Every time I start the desktop, whether by startx or via
lxdm, I immediately get an error box saying "Could not connect: No such file
or directory." Does anyone here recognise this? Google hasn't helped me.

--
Regards
Peter

[Miroslav Rovis]

Look up what you get in /var/log/messages at the time of the error.

--
Miroslav Rovis
Zagreb, Croatia
https://www.CroatiaFidelis.hr

[Raffaele Belardi]

Miroslav Rovis wrote:
> On 170316-21:35+0000, Peter Humphrey wrote:
>>
>> I've just finished (well, you know) installing Gentoo on a new box and given
>> it an LXDE desktop. Every time I start the desktop, whether by startx or via
>> lxdm, I immediately get an error box saying "Could not connect: No such file
>> or directory." Does anyone here recognise this? Google hasn't helped me.
>
> Look up what you get in /var/log/messages at the time of the error.
>

Also .cache/lxsession/LXDE/run.log

Does the desktop show up regularly besides showing the error message?

raffaele

[Peter Humphrey]

On Friday 17 Mar 2017 08:56:18 Raffaele Belardi wrote:
> Miroslav Rovis wrote:
> > On 170316-21:35+0000, Peter Humphrey wrote:
> >> I've just finished (well, you know) installing Gentoo on a new box and
> >> given it an LXDE desktop. Every time I start the desktop, whether by
> >> startx or via lxdm, I immediately get an error box saying "Could not
> >> connect: No such file or directory." Does anyone here recognise this?
> >> Google hasn't helped me.
> >>
> > Look up what you get in /var/log/messages at the time of the error.

Mar 17 09:11:10 webs lxdm-binary[1804]: PAM unable to dlopen(/lib64/security/pam_gnome_keyring.so): /lib64/security/pam_gnome_keyring.so: cannot open shared object file: No such file or directory
Mar 17 09:11:10 webs lxdm-binary[1804]: PAM adding faulty module: /lib64/security/pam_gnome_keyring.so
Mar 17 09:11:10 webs lxdm-binary[1804]: PAM unable to dlopen(/lib64/security/pam_selinux.so): /lib64/security/pam_selinux.so: cannot open shared object file: No such file or directory
Mar 17 09:11:10 webs lxdm-binary[1804]: PAM adding faulty module: /lib64/security/pam_selinux.so
Mar 17 09:11:10 webs lxdm-binary[1804]: pam_unix(lxdm:session): session opened for user prh by (uid=0)
Mar 17 09:11:10 webs ck-launch-session[1860]: error connecting to ConsoleKit

> Also .cache/lxsession/LXDE/run.log

A lot of stuff from vala. No timestamps though - do I get a new run.log each
time LXDE starts, or are new entries appended? I guess it's the former.

> Does the desktop show up regularly besides showing the error message?

I don't know, as I've never used LXDE before. The screen is plain black,
which doesn't seem right.

Thanks for the clues, gents. I'll go away and poke around a bit. Maybe run
an emerge -e world.

--
Regards
Peter

[Mick]

I don't have a fix for you, but from the errors it seems pam is not happy.
Display Managers and various services install pam modules in /etc/pam.d/ to
manage user authentication. It seems something is amiss there, or some kind
of conflict between gnome-keyring and LXDE.
--
Regards,
Mick

[Peter Humphrey]

On Friday 17 Mar 2017 09:49:14 Mick wrote:

> I don't have a fix for you, but from the errors it seems pam is not happy.
> Display Managers and various services install pam modules in /etc/pam.d/
> to manage user authentication. It seems something is amiss there, or
> some kind of conflict between gnome-keyring and LXDE.

Yes, I see that. I also see a lot of stuff that may be causing it. I deleted
.cache/lxsessions/LXDE/run.log, ran startx and immediately logged out, and
this is what I found (sorry, it's 110 lines):

$ cat run.log
** Message: environement.vala:58: Exporting primary_variable
** Message: environement.vala:59: desktop_environnement XDG_CURRENT_DESKTOP
** Message: environement.vala:176: custom_config :
** Message: environement.vala:177: config_dirs :/etc/xdg
** Message: environement.vala:178: confir_dirs not null, export : /etc/xdg
** Message: environement.vala:183: Exporting XDG_CONFIG_DIRS
** Message: environement.vala:217: custom_data :/usr/share/gdm:/var/lib/menu-xdg:
** Message: environement.vala:218: data_dirs :/usr/local/share:/usr/share
** Message: environement.vala:219: data_dirs not null, export : /usr/share/gdm:/var/lib/menu-xdg:/usr/local/share:/usr/share
** Message: environement.vala:224: Exporting XDG_DATA_DIRS
** Message: utils.vala:68: User config used : /home/prh/.config/lxsession/LXDE/desktop.conf
** Message: utils.vala:89: Final file used : /home/prh/.config/lxsession/LXDE/desktop.conf
** Message: settings.vala:531: Key file does not have key 'iGtk/ColorScheme' in group 'GTK'
** Message: settings.vala:531: Key file does not have key 'windows_manager/extras' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'panel/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'dock/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'file_manager/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'desktop_manager/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'launcher_manager/autostart' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'composite_manager/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'im1/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'im2/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'widget1/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'keybindings/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'screensaver/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'power_manager/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'audio_manager/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'workspace_manager/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'screenshot_manager/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'message_manager/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'upgrade_manager/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'upstart_user_session' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'proxy_manager/http' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'a11y/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'xrandr/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'network_gui/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'webbrowser/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'email/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'pdf_reader/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'video_player/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'audio_player/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'images_display/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'text_editor/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'archive/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'charmap/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'calculator/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'spreadsheet/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'bittorent/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'document/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'webcam/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'burn/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'notes/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'disk_utility/command' in group 'Session'
** Message: settings.vala:531: Key file does not have key 'tasks/command' in group 'Session'
** Message: settings.vala:531: Key file does not have group 'Keymap'
** Message: settings.vala:531: Key file does not have key 'laptop_mode' in group 'State'
** Message: settings.vala:531: Key file does not have key 'gnome' in group 'Dbus'
** Message: settings.vala:531: Key file does not have group 'Updates'
** Message: settings.vala:531: Key file does not have key 'type' in group 'Environment'
** Message: settings.vala:453: Monitoring: /home/prh/.config/lxsession/LXDE/desktop.conf
** Message: settings.vala:457: Desktop file is already in config home, do nothing
** Message: environement.vala:79: Exporting variable
** Message: environement.vala:80: desktop_environnement XDG_CURRENT_DESKTOP
** Message: environement.vala:176: custom_config :
** Message: environement.vala:177: config_dirs :/etc/xdg
** Message: environement.vala:178: confir_dirs not null, export : /etc/xdg
** Message: environement.vala:183: Exporting XDG_CONFIG_DIRS
** Message: environement.vala:217: custom_data :
** Message: environement.vala:218: data_dirs :/usr/share/gdm:/var/lib/menu-xdg:/usr/local/share:/usr/share
** Message: environement.vala:219: data_dirs not null, export : /usr/share/gdm:/var/lib/menu-xdg:/usr/local/share:/usr/share
** Message: environement.vala:224: Exporting XDG_DATA_DIRS
** Message: utils.vala:79: Config system location : /etc/xdg/lxsession/LXDE
** Message: utils.vala:85: System system path location : /etc/xdg/lxsession/LXDE/conffiles.conf
** Message: utils.vala:89: Final file used : /etc/xdg/lxsession/LXDE/conffiles.conf
** Message: options.vala:164: Activate xsettings_manager build-in
** Message: utils.vala:68: User config used : /home/prh/.config/lxsession/LXDE/desktop.conf
** Message: utils.vala:89: Final file used : /home/prh/.config/lxsession/LXDE/desktop.conf
xprop: no such property "_NET_NUMBER_OF_DESKTOPS"
xprop: no such property "_NET_DESKTOP_NAMES"
xprop: no such property "_NET_CURRENT_DESKTOP"
** Message: app.vala:717: polkit separate
** Message: app.vala:717: polkit separate
** Message: app.vala:76: Launching lxpolkit

** (lxsession:21920): WARNING **: app.vala:86: Failed to execute child process "/usr/libexec/notification-daemon" (No such file or directory)

** (lxsession:21920): WARNING **: app.vala:87: Error when launching /usr/libexec/notification-daemon
** Message: utils.vala:68: User config used : /home/prh/.config/lxsession/LXDE/autostart
** Message: utils.vala:89: Final file used : /home/prh/.config/lxsession/LXDE/autostart
** Message: autostart.vala:42: Autostart path : /home/prh/.config/lxsession/LXDE/autostart
** Message: app.vala:76: Launching lxpanel
** Message: app.vala:76: Launching pcmanfm
** Message: options.vala:110: Create Option Clipboard
** Message: options.vala:44: Options - Launch command lxclipboard
** Message: main.vala:440: Check keymap_mode (null)
** Message: app.vala:76: Launching /usr/bin/ssh-agent SSH_AUTH_SOCK=/tmp/ssh-IPKVEEdaJxrF/agent.21962; export SSH_AUTH_SOCK; SSH_AGENT_PID=21964; export SSH_AGENT_PID;
echo Agent pid 21964;
** Message: app.vala:130: /usr/bin/ssh-agent exit with this type of exit: 0

** (pcmanfm:21956): WARNING **: The directory '~/Templates' doesn't exist, ignoring it

** (lxpanel:21955): WARNING **: The directory '~/Templates' doesn't exist, ignoring it

(lxpanel:21955): Wnck-WARNING **: Unhandled action type _OB_WM_ACTION_UNDECORATE
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
after 3409 requests (3409 known processed) with 0 events remaining.
pcmanfm: Fatal IO error 0 (Success) on X server :0.

------------------------------------

So it looks as though something hasn't been installed right. I'm running an
emerge -e world at the moment to see if I can pick something up from it.

--
Regards
Peter

[Peter Humphrey]

On Friday 17 Mar 2017 15:57:14 I wrote:

> So it looks as though something hasn't been installed right. I'm running
> an emerge -e world at the moment to see if I can pick something up from
> it.

Hasn't made the slightest difference, so I've decided to show LXDE the door:
it clearly isn't ready for use by mere mortals such as I'm fast decaying
into ;0

A pity, because I wanted a lightweight desktop via which to manage a web
development server, one with as few opportunities for being hacked as
practicable.

Maybe XFCE will do better. Or maybe the panel can offer other suggestions...

--
Regards
Peter

[Peter Humphrey]

On Friday 17 Mar 2017 20:30:46 Dale wrote:

> I use Fluxbox as a backup desktop. It's very, extremely, fast last I
> ran it. It's tiny last I checked too. I'm not sure how it compares to
> XFCE tho. It may be smaller.
>
> Just thought I would throw out one more idea, in case you end up needing
> it.

Thanks Dale. In fact I've decided to give LXDE a reprieve, this time setting
a desktop profile first, as instructed. You see what I mean about decay.

--
Regards
Peter

[Dale]

I use Fluxbox as a backup desktop. It's very, extremely, fast last I
ran it. It's tiny last I checked too. I'm not sure how it compares to
XFCE tho. It may be smaller.

Just thought I would throw out one more idea, in case you end up needing it.

Dale

:-) :-)

[Dale]

I do. It hits me all the time too. Sometimes, it is the simple stuff
that gets me.

At least you have options, just in case.

Dale

:-) :-)

[Raffaele Belardi]

Peter Humphrey wrote:
> On Friday 17 Mar 2017 09:49:14 Mick wrote:
>
>> I don't have a fix for you, but from the errors it seems pam is not happy.
>> Display Managers and various services install pam modules in /etc/pam.d/
>> to manage user authentication. It seems something is amiss there, or
>> some kind of conflict between gnome-keyring and LXDE.
>
> Yes, I see that. I also see a lot of stuff that may be causing it. I deleted
> .cache/lxsessions/LXDE/run.log, ran startx and immediately logged out, and
> this is what I found (sorry, it's 110 lines):
>
> $ cat run.log

....

>
> ------------------------------------
>
> So it looks as though something hasn't been installed right. I'm running an
> emerge -e world at the moment to see if I can pick something up from it.
>

I don't see anything strange in your log; LXDE should start even without
notification-deamon installed.
Is there anything strange in /var/log/X.org.0.log?
"ran startx and immediately logged out": do you use a login manager?

raffaele

[Peter Humphrey]

Even after all my digging and rebuilding, I was still getting an error on
startup - not the one I was asking about, but I don't remember just what it
was now.

In the end I ditched LXDE and went for Fluxbox.

--
Regards
Peter