Separate Slick Xsession

[Lucazade]

It would be nice to have a 'Slick' session available in login-manager.

[Lucazade (lucazade)]

First attempt to get something working..

At the moment I need to open an app before loading slickpanel otherwise I get only a black rectangle instead of slickpanel at top of the screen. I'll try to find a solution asap.

In the next comments I'll attach these files needed to get a separate xsession:

/usr/share/xsessions/slick.desktop
/usr/share/gnome-session/sessions/slick.session
/usr/share/applications/slickpanel-session.desktop
/usr/bin/slickpanel-session

[Lucazade (lucazade)]

a screenshot of the loaded Slick session

[Lucazade (lucazade)]

These files are better, purged gnome-terminal.. anyway I still have to use a 'slickpanel-session' bash script to call 'slickpanel' at session startup otherwise there is a long delay before gnome-settings-daemon loads up.
Next trial will be to purge 'slickpanel-session' and call directly 'slickpanel' from /usr/share/gnome-session/sessions/slick.session and set notify-osd as default notifications provider.

[Lucazade (lucazade)]

after some other trials (with and w/o autologin) these files seem enough to kickstart a slick session:

/usr/share/xsessions/slick.desktop
/usr/share/gnome-session/sessions/slick.session
/usr/share/applications/slickpanel.desktop
(attached inside the new .tar.gz)

sometimes at session startup there is a blank panel with no indicators or only a part of them, when this happens in .xsessionerrors there is this warning from slickpanel:
Error getting primary device

I haven't looked inside slickpanel code because I don't know vala, so I can't go further.

[Andrew (and471)]

Hmm, "Error getting primary device" normally appears when I run in the terminal so the fact it is not appearing is nothing to do with that.

I feel this may be solved by some of configuration work going on so I would prefer to wait until that has landed before I take a deeper look at this.

Thanks for your work so far Lucazade!