On Mon, 10 Apr 2017 09:59:16 +0100 Mick <michaelkintz...@gmail.com> said:
> Thanks Carsten for looking into this.
>
> On Monday 10 Apr 2017 16:19:21 you wrote:
> > On Sun, 26 Mar 2017 16:03:13 +0100 Mick <michaelkintz...@gmail.com> said:
> > > Hi All,
> > >
> > > I've been launching enlightenment using SDDM for some years now without a
> > > problem. Recently I updated sddm to 0.14.0-r2 and weird things started
> > > happening. I was no longer able to mount USB sticks. A single attempt to
> >
> > something changed in sddm? :) i have no idea. never even heard of sddm... :)
>
> It's just another DM which does not bring in a tonne of big desktop
> dependencies. It was working fine here for a couple of years or so.
>
>
> > > log out brings me straight back into my e desktop. A second attempt to
> > > log out, logs me out as it should.
> > >
> > > Then I updated to sddm-0.14.0-r3 and now in addition e complains the
> > > compositor cannot run with OpenGL and will fall back on software
> > > rendering.
> > >
> > > :-/
> >
> > stop using sddm or go back to an older version? :( opengl could be due to
> > changes in LD_LIBRARY_PATH that sddm could be modifying when it launches the
> > login session. it could be due to ownership of /dev/dri/* or /dev/nvidia*
> > device nodes? i don't know.
>
> Interesting, I'll look into this.
>
>
> > mounting and unmounting could be something else entirely... i'm not sure.
> > could it be using cgroups, selinux or something else to deny access? i'm
> > not sure.
> >
> > but what you had before did work.... going back to it should be the easiest
> > path. :(
>
> Yes, this was the first thing I tried to prove the point these anomalies were
> introduced by the sddm package update alone and not something else on my
> system.
>
>
> > > Here's some errors from ~/.xession-errors:
> > > ==========================================
> > > ERR<5100>:eina_safety lib/efreet/efreet_ini.c:299 efreet_ini_string_get()
> > > safety check failed: ini->section == NULL
> > >
> > > (gkrellm:5117): Gtk-CRITICAL **: IA__gtk_box_reorder_child: assertion
> > > 'GTK_IS_WIDGET (child)' failed
> > > ERR<5141>:eldbus lib/eldbus/eldbus_proxy.c:818 _props_get_all() Error
> > > getting all properties of
> > > org.freedesktop.UDisks2/org/freedesktop/UDisks2/block_devices/s
> > > da1, error message: org.enlightenment.DBus.Canceled Canceled by user.
> > > ==========================================
> > >
> > >
> > > Strangely, I have the same access rights symptoms if I try to login
> > > without a DM, using 'startx /usr/bin/enlightenment_start' on a console.
> > >
> > > This is what I have in my ~/.xsession file:
> > > ===========================================
> > > cat ~/.xsession
> > > #!/bin/sh
> > > if [ -x /usr/bin/gpg-agent ]; then
> > >
> > > kill $(ps ux | awk '/gpg-agent/ && !/awk/ {print $2}') >/dev/null
> > > 2>&1
> > >
> > > fi
> > >
> > > if [ -x /usr/bin/gpg-agent ]; then
> > >
> > > eval "$(/usr/bin/gpg-agent --daemon)"
> > >
> > > fi
> > >
> > > if [ -x /usr/bin/urxvtd ]; then
> > >
> > > /usr/bin/urxvtd --opendisplay --fork --quiet
> > >
> > > fi
> > >
> > > /usr/bin/enlightenment_start
> > > ============================
> > >
> > > Using lightdm works as expected, I can login, OpenGL works, mounting USB
> > > sticks works and log out only need to be activated once.
> > >
> > > I tried entrance some time ago, with mixed results, especially on shut
> > > down - it would not return to a console. Also SLiM would fail to log me
> > > in whatsoever, so I abandoned it.
> > >
> > > Any idea what is missing from my set up to cause these access rights
> > > problems with sddm or using startx? What is considered a
> > > distro-independent orthodox way to start e these days?
> >
> > dunno. maybe systemd related with the user session/logind? i am unsure how
> > this might affect opengl access - it shoudn't... :/
>
> Thanks Carsten, I am using openrc, instead of systemd. As I mentioned above
> I reverted to the old sddm and it works as expected, so clearly the problem
> was introduced with later versions of the sddm.
>
> I am now running lightdm which solves these problems, but requires Gnome
> dependencies to be installed. I am still curious why sddm, or running startx
> from a console won't work as expected.
i really don't know. i might imagine something to do with the startup scripts
that may or may not have run dbus-launch but e will run this anyway if it finds
it doesnt have a dbus user session... but really i don't know what's up given
your information. it'd be interesting to find out why.
stuff used to be so much simpler 20 years abck. you just had your login manger
run ~/.xsession. this script would run your wm last without & (with exec before
if u were smart) and anything u wanted launched on login before that in the
script.
today it's a forest of services and god knows what... :)
--
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler) ras...@rasterman.com
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users
