The officially official Devuan Forum!

You are not logged in.

#1 2017-07-06 04:32:55

PeteGozz
Member
From: Woodside South Australia
Registered: 2017-06-21
Posts: 62

Slim and build settings

I will try to report this on git as well.

So I've noticed a few non jessie users lately, who have had a few issues with slim.
These are generally "solved" by installing lightdm instead of slim. (well so far)

Huge note here:
I have been using startx  or xinit directly to use a Window Manager rather than a Desktop.
Which means dbus is not so central or even consolekit .

In any case a simple fix is available by building slim with both pam and cksupport.
(from source of course).

I would also
    NOT require DBUS on boot (init file)
    simply launch a session dbus from the system xsession or some other default.

I know some would consider this a  GUI heresy and I really do think we should follow the "Rule Of Least Surprise" (especially for GUI only people.)

so from the source tree

mkdir build 
cd build  
cmake ../ -DUSE_PAM=yes  -DUSE_CONSOLEKIT=yes

Well it works for me with the default upstream theme at least.

OH for testing:
    this at the head of /etc/init.d/slim

#DAEMON=/usr/bin/slim
DAEMON=/usr/local/bin/slim

    and this wee quicky
    (hey I could have just skipped the test smile

 [ ! $(grep $DAEMON $DEFAULT_DISPLAY_MANAGER_FILE > /dev/null ); then
 #       [ "$(cat $DEFAULT_DISPLAY_MANAGER_FILE)" != "$DAEMON" ]; then

Now if a couple of other people would like to verify ....
git pull origin master
From https://git.devuan.org/devuan/slim
* branch            master     -> FETCH_HEAD
Already up-to-date.

I used that one as it looks like the top of the fork tree to me.

Last edited by PeteGozz (2017-07-06 04:34:42)


Own your own tools.
Break them your way.

Offline

#2 2017-07-06 05:12:53

golinux
Administrator
Registered: 2016-11-25
Posts: 551

Re: Slim and build settings

PeteGozz wrote:

Now if a couple of other people would like to verify ....
git pull origin master
From https://git.devuan.org/devuan/slim
* branch            master     -> FETCH_HEAD
Already up-to-date.

I used that one as it looks like the top of the fork tree to me.

This is the version that the current purpy slim is built off of but the font colors and positioning are not quite right:
https://git.devuan.org/hellekin/slim/tr … vuan-curve

This is the correct slim.theme but I have no idea where it currently resides on git.  Package name is devuan-curve-purpy:

#
## SLiM theme Devuan Curve
#
# Copyright 2015-2016 Dyne.org Foundation
# Created by hellekin <hellekin@dyne.org>
#
## Known issues
#
# - usernames larger than 20 characters may overflow the input box
#   SLiM limits username's length to 29 characters.  Usernames are
#   usually much shorter though.
# - ditto for passwords.  Usually a password up to 28 characters
#   should display without overflow.
#
## Changelog
#
# October 2016
#
# - Panel now indicates the F1 key and send to `man slim` for more
#   options.
# - Font changed from Fira Sans to Open Sans
# - Changed to Jessie's purpy theme

## background

# background.png is 50x50 purpy square
background_style tile
background_color #7b7691

## panel
# note: all positions are in pixels to ensure multihead support.

# place panel on the top left
# position is absolute
input_panel_x      0
input_panel_y      0

# use only one line for username and password inputs
# positions are absolute values, and relative to the panel
input_name_x     121
input_name_y     257

input_pass_x      -1
input_pass_y      -1

# place 'username:' and 'password:' prompts just above the input line
# positions are absolute values, and relative to the panel
username_x       119
username_y       231

password_x       119
password_y       231

# center feedback messages
# position is absolute
msg_x            595
msg_y            450

# center session messages
# position is absolute
session_x        595
session_y        395

# disable welcome message
# position is absolute
welcome_x         -1
welcome_y         -1


## text

username_msg              username:
password_msg              password:
passwd_feedback_msg       ACCESS DENIED
passwd_feedback_capslock  ACCESS DENIED (CapsLock is on)

input_color    #716c85
msg_color      #dad9dc
session_color  #dad9dc
username_color #dad9dc

input_font     Open Sans:medium:size=14:dpi=96
msg_font       Open Sans:medium:size=18:dpi=96
session_font   Open Sans:medium:size=14:dpi=96
username_font  Open Sans:medium:size=14:dpi=96

You might also want to look at this: https://dev1galaxy.org/viewtopic.php?id=581

Offline

#3 2017-07-06 05:27:21

PeteGozz
Member
From: Woodside South Australia
Registered: 2017-06-21
Posts: 62

Re: Slim and build settings

Thanks
I will go get that one and try again smile


Own your own tools.
Break them your way.

Offline

#4 2017-07-06 07:25:06

PeteGozz
Member
From: Woodside South Australia
Registered: 2017-06-21
Posts: 62

Re: Slim and build settings

golinux wrote:

This is the version that the current purpy slim is built off of but the font colors and positioning are not quite right:
https://git.devuan.org/hellekin/slim/tr … vuan-curve

This is the correct slim.theme but I have no idea where it currently resides on git.  Package name is devuan-curve-purpy:


So far have confirmed from two fresh builds that
The following build config lets me login from DM whereas the devuan install does not.

1/ the above init hack is broken here ;> Well of course
2/This one is neater in any case

case $1 in
    start)
  #   if [ "$HEED_DEFAULT_DISPLAY_MANAGER" = "true" ] &&
  #      [ -e $DEFAULT_DISPLAY_MANAGER_FILE ] &&
  #      [ "$(cat $DEFAULT_DISPLAY_MANAGER_FILE)" != "$DAEMON" ]; then
  #      log_daemon_msg "Not starting $DESC ($NAME); it is not the default display manager." "$NAME"
  #   else
      log_daemon_msg "Starting $NAME" "$NAME"
      start-stop-daemon --start --quiet $SSD_START_ARGS
      log_end_msg $?
#    fi
  ;;

3/ have set up my own fork
    a/ for clarity sake
    b/ guess I will have to build a package at some point
        and that is best kept away from nice people. <-.->

https://git.devuan.org/PeteGozz/slim
Which should be set up to the jessie fork as default branch

4/ Builds fine :
With this wee script. (hidden by .gitignore)

#!/bin/bash
## -*- shell-script -*-

mkdir -v ./build ;
echo "$?"
cd build
pwd
echo -e "\nConfiguring cmake for PAM and CONSOLKIT\n"
sleep 3

cmake ../ -DUSE_CONSOLEKIT=yes -DUSE_PAM=yes

echo -e "\n\nCmake says :  $?\n "

make

####&& make install  by hand 
#eof

I have sussed how to use -p /to/them/dir
But haven't done any work beyond a nod to the theme .

Best plan is to "beatup" the themes  devuan-*
under debian and test that I suppose.

I'll reread the links smile

Bridges later and all


Own your own tools.
Break them your way.

Offline

#5 2017-07-06 23:54:21

golinux
Administrator
Registered: 2016-11-25
Posts: 551

Re: Slim and build settings

Progress . . . congrats. smile  Did you build it with the d1h?   Since those with access to the resources to package properly don't come here often, you'll need to contact them on #devuan-dev once you've got it ready to package for ascii.

Offline

#6 2017-07-07 04:37:27

PeteGozz
Member
From: Woodside South Australia
Registered: 2017-06-21
Posts: 62

Re: Slim and build settings

golinux wrote:

Progress . . . congrats. smile  Did you build it with the d1h?   Since those with access to the resources to package properly don't come here often, you'll need to contact them on #devuan-dev once you've got it ready to package for ascii.

I'm just walking myself through all that now.
Its either that or / and install the ..../debian/patches myself and hope.

(which I don't think is a great idea)


However I think I have exposed some issue with the theme <=> config.
Essentially they must be kept in line with definitions for all "exposed" options.

I'm not totally sure yet, but w a l k i n g through the source seems to confirm this.

Anyway next bet is to build deb version and see how unbroken those patches make slim.
(an entire executable (screen locker) is suppressed  by those patches.)

... and C++ is not my favorite language .. must resist rewrite in C or erlang or perl or bash ;>


Also I have to merge to git.devuan as I branched here and ...  sigh ...
Its no biggy the web interface does not like it though smile

So sorry its taking a while to wrangle ME into this.

Finally I let ".ro"  badguys into my gateway box and have been sweeping that clean ....

Serves me right ! .. no never mind ...

This box quite safe and undisturbed smile

AND _this_ site was down ...
LOL

I need a lie down ! smile

Last edited by PeteGozz (2017-07-07 04:39:29)


Own your own tools.
Break them your way.

Offline

#7 2017-07-07 09:45:18

PeteGozz
Member
From: Woodside South Australia
Registered: 2017-06-21
Posts: 62

Re: Slim and build settings

golinux wrote:

Progress . . . congrats. smile  Did you build it with the d1h?   Since those with access to the resources to package properly don't come here often, you'll need to contact them on #devuan-dev once you've got it ready to package for ascii.

OK it builds with d1h ...
e  v  e  n  t  u  a  l  l  y

All works OK as installed from  dpkg -i
with _its_ confs

Notes TODO etc.

However It still needs
   better visibility on F1  not hard at all
   Testing for caps lock etc

*** I need to grok why gpg  doesn't see my key , its probably something simple. ***

slim :
My own preferences would include:
  Dropping requirement for consolekit
  or dbus
       these can be run (if available) from the system xsession / xinitrd system
       per user ... but I guess that would be a bit radical smile

i.e. It should work with or without either of them.


Higher Priority for me:

Hack until the thing runs with other instances of X running
It silently fails if I am using :0 or any other "port" for X

Work out why some apps will launch from keyboard and not others when I use it to login

In any case these "ideas" are not for jessie   !


Own your own tools.
Break them your way.

Offline

#8 2017-07-07 17:13:50

PeteGozz
Member
From: Woodside South Australia
Registered: 2017-06-21
Posts: 62

Re: Slim and build settings

The /etc/slim.conf file at the moment

https://git.devuan.org/PeteGozz/slim/bl … /slim.conf

The devuan-curve  theme file.
(which is set as default)

https://git.devuan.org/PeteGozz/slim/bl … slim.theme

This builds and installs with d1h as of now
Except for the gpg signing thing which ... later.

Tips for other new players::
  start off with d1h as soon as you can otherwise things roll back on you in all the noise.


Own your own tools.
Break them your way.

Offline

#9 2017-07-07 18:26:35

fsmithred
Administrator
Registered: 2016-11-25
Posts: 377

Re: Slim and build settings

I cloned your repo, built the package and installed it. It works! Nice job. The error regarding libpng12-0 that was preventing installation from the repo is gone.

There is a potential problem. The version number you used is already taken. Looking at the changelog, it looks like you did not use the latest version, so there might be some changes that were lost. Although it looks like those changes involved removing the devuan theme and letting desktop-base handle it. I have no idea what should be done about that.

Offline

#10 2017-07-07 21:25:02

golinux
Administrator
Registered: 2016-11-25
Posts: 551

Re: Slim and build settings

You said it didn't have anything to do with that package but I thought maybe it did.  wink   I have no idea how Centurion_Dan set slim  up at the 11th hour before the stable release. That's who has the answer though.

Offline

#11 2017-07-08 01:39:04

PeteGozz
Member
From: Woodside South Australia
Registered: 2017-06-21
Posts: 62

Re: Slim and build settings

golinux wrote:

You said it didn't have anything to do with that package but I thought maybe it did.  wink   I have no idea how Centurion_Dan set slim  up at the 11th hour before the stable release. That's who has the answer though.

fsmithred wrote:

The error regarding libpng12-0 that was preventing installation from the repo is gone.

There is a potential problem. The version number you used is already taken. Looking at the changelog, it looks like you did not use the latest version, so there might be some changes that were lost. Although it looks like those changes involved removing the devuan theme and letting desktop-base handle it. I have no idea what should be done about that.

Quite happy to start again all the way from the original source if needs be.
I think I understand the concept of having desktop-base installing  the theme.
Please read on as it _will_ break, unless you turn Devuan into a desktop distro.

Thoughts though: (way toooo many)

    1/ I'm probably not _atypical_ in usually doing a minimal install and adding "stuff" as needed.
        *I still don't have desktop-base installed.*
        Though sure, I'm not a majority but Desktops are not required (yet).
        Which explains some confusions ?       
   
   2/ Is slim the default official X Display Manager ?
        I'd vote yes, but assume it is.
        I'm usually suspect of C++ (opacity) but this is clear enough to grep..
        (though WTF most of the header files are trying to say ?)

        In which case /usr/share/slim/themes  should be installed by slim
        and then slim itself Included (required) by one of  XFCE or desktop_base ?
         (or some daisy chain)
        That way default *Desktop* installs get xfce + slim in devuan themes.
        The rest of us get a devuan themed X DM which we can break or not.

         Its not an issue to leave options disabled in the slim.conf for more minimalist users.
         I have more or less done that already.
         Importantly the THEME file has to enable features otherwise "stuff" just doesn't happen.
         Breakages _may_ lead to no login or no choice of environment, which is DM's primary purpose.

  3/ This (my) fork of slim started as an experiment really.
      I forked from helliken as it seemed to be where most of the theme works was at.
      I have no cultural memory here !
      Which is probably why it works . <==  Hellikens worked !
     
    Which leads me to:

  4/ How would one choose which fork or _reliably_ tell  which is live from the gitlab site ?
      Is there a better place to nut this out ?
      Is that what the coloured Letter symbols mean ?
      I know there is IRC but thats not everyones TZ and is an excellent adjunct.

     Perhaps I missed some memo and sailed past some docs !
     Deployed packages discuss foo: url 

     ((( If anybody tells me to trawl IRC logs  and try to guess...
     I will /dev/random their favourite USB stick ! Twice
    From my super villain base on Europa.)))
     
    Sorry I stumbled into  _all_ of this from a *github* view of *gitlab*.
    (and little experience of git going upstream!)
    I was startled when d1h stole then ate my homework !
   
   Seems to me gitlab is a good place to centre package specific discussion.
   Not BUG reports but policy / design etc.
   Its probably written some place in 72point pink letters but I can not see it .

  5/ Meantime
     What I propose I do is something like:
     

apt-get source slim -t jessie 

     Fix that here and load that on gitlab. (after it all works here)
     Then blow away my current fork.
     
     .... Use that as a base then branch (via d1h dpkg-build ) to ascii


Own your own tools.
Break them your way.

Offline

#12 2017-07-08 02:43:26

PeteGozz
Member
From: Woodside South Australia
Registered: 2017-06-21
Posts: 62

Re: Slim and build settings

In l  a  r  g  e possibly PINK letters:

https://git.devuan.org/devuan/devuan-maintainers
https://git.devuan.org/devuan-packages

So I should have forked :
https://git.devuan.org/devuan-packages/slim

Last edited by PeteGozz (2017-07-08 02:46:19)


Own your own tools.
Break them your way.

Offline

#13 2017-07-08 12:11:20

fsmithred
Administrator
Registered: 2016-11-25
Posts: 377

Re: Slim and build settings

Your gitlab-fu is better than mine. I think I've seen those pages, but I wouldn't know how to find them.

Yes, slim is the default display manager. And desktop-base is installed if you take the default desktop install, which uses a few task-* packages to fill up the installed-packages list.

It looks like the latest version of slim we have is 1.3.6-5+devuan4 in jessie. There's a newer version in stretch - 1.3.6-5.1, but I don't know if it has anything we want (plymouth patches and I forget what else). I tried building a package from the stretch sources, and it worked, but I didn't know how to put the devuan theme into it except to add it after installing slim. I only changed the changelog to give it a unique number. I did not have to change the dependencies, and I don't understand the deps. Specifically, I don't understand why apt complains that slim needs libpng12-0 when it's not listed in the control file.

I agree with you that the theme should be in the slim package. There are lots of people who don't install desktop-base but do use a dm. But I can't say anything about how desktop-base should interact with that. I know that the plan is to make it so that people can easily create and change themes for d-b that will show up at boot, login and desktop. I've avoided d-b ever since spacefun.

Offline

#14 2017-07-08 15:26:42

PeteGozz
Member
From: Woodside South Australia
Registered: 2017-06-21
Posts: 62

Re: Slim and build settings

fsmithred wrote:

I think I've seen those pages, but I wouldn't know how to find them.

I now have this one bookmarked:  https://git.devuan.org/devuan-packages

fsmithred wrote:

It looks like the latest version of slim we have is 1.3.6-5+devuan4 in jessie. There's a newer version in stretch - 1.3.6-5.1

I really think for this and probably anything before logins fully complete (!) we should be treating Debian like it has something contagious. (because it *has* )

Reference for sure, but sometimes its easier to start from proper upstream upstream or just belt what we have into health.

fsmithred wrote:

Specifically, I don't understand why apt complains that slim needs libpng12-0 when it's not listed in the control file.

Yes that is weird mine doesn't, but I have stuff from all over the place.
I will recheck this again tomorrow or something.

fsmithred wrote:

I agree with you that the theme should be in the slim package. There are lots of people who don't install desktop-base but do use a dm. ...

I think I see the objectives.
I don't see them having to be exclusive but is  be easier that way.
I change it anyway ;>

There is no longer (in the official packages version on gitlab) any themes at all in the debian directory.
The package still installs the *sources* default though.

see: /usr/share/slim/themes/default

mkdir themename
cp default/* themename/
cd themename
change to background image as a test.

find the theme line in /etc/slim.conf
add  yourname comma,separated
or just replace it...
days of fun smile
AND you get to keep the default and devuan-foo if it arrives
AND the task-thing will probably overwrite the conf file !
(but you will have a backup )
FWIW:
This task-thing is probably a sane idea.
Though it needs to be more carefully implemented !

The Devuan theme login can be assured  and consistently debugged.
The branding and art folks need only grok that world.
Users can flip or even randomise from /etc/slim.conf
(if they can admin it)

There are still issues with the config file IMHO all of them quite fixable.
e.g. The session list should be generated per install from the contents of /usr/share/xsessions
(this is not such an ask for pre-install scripts)
AND OR the "sessiondir"  should be set to that directory.
(then the user needs an easy way to set a default smile
Finally the example ~/.xsession should be tidied up and extended to catch dbus users and stuffed in doc/exampes or something, with a note in the config.

(actually it could go system wide in /etc/X11/xsession.d with a moderate amount of work.)

Today I tested the official _stable_ _jessie_ version it can be built without consolkit (or dbus) or even the screenlock thing and with pam only. I have not bothered to fight d1h and its idea of git . Geeze you name a branch zombie and it gets all toey smile

(or dpkg-buildpkg s)

It works fine here stripped down like that.

(which would reduce the deps list a little as well)
If it can't find the deps it just skips that functionality where possible.
(for consolekit and pam)

There is a toggle on pam in the CMakefile.txt that allows (1) the screenlocker.
So see the INSTALL but -DUSE_CONSOLEKIT=no -DUSE_PAM=yes  (check these)
No consolekit should mean no dbus as well.


Own your own tools.
Break them your way.

Offline

#15 2017-07-10 15:04:42

PeteGozz
Member
From: Woodside South Australia
Registered: 2017-06-21
Posts: 62

Re: Slim and build settings

So here is the state of slim as seen by me Mon July 20th 2017.
A rough report.

Devuan has diverged from Debian, both have diverged from Upstream.
_None_ of these changes are major. (Philosophies aside.)

I really do not need (or want) to care about what Debian are doing to Slim,
_other than noting_::

    that Devuan's sources came from Deb rather than upsteam.
    -  The patch set could be reduced but its not too bad. (I guess)
    - Devuan could start again from upstream at least as found on github with
      ONE patch of about 4-8 char in size ! (from memory)

Patching out debian "breakages" is a waste of this distros energy.
( So the current devuan gitLAB packages should be the one Devuans' work on until upstream wakes up.)

Upstream does not look too active, though I would be happy to be proven wrong !
I baited a line with "documentation" so far no bites.

Policy::
     Devuan devs have policed (i.e policy-ed) out the theme directories under the debian/ tree.
     slim.theme will be set by other modes.
     I know of no reason that the current slim code default theme could not be replaced / kept
     and a  Devuan default (not release aware) installed instead or as well.
     (This could be as simple as changing the background.)

The functionalities and depends list seems consistent  across all suite/stablity levels.
The Devuan devs will wrangle Branding and notably Usablility + Internationalisation .
A deduction of sorts ::
     suites/{jessie,ascii,etc,etc} are about release branding really.
     suites/unstable (or experimental) is where functionality would be worked on.

I should think a documentation branch or perhaps tag would be useful?
(though there is little need for much more beyond a how to ~/.xinitrc or some such and dbus notes)

I have yet to trip over any mention of the slimlock screen locker, but maybe I should look again.



so links:
----------

Upstream github:
https://github.com/iwamatsu/slim   (the master branch has a silly typo bug.)

There are a few forks and pull requests most of them growing old.
Including mine:
https://github.com/PeteGozz/slim/tree/docsatwork      (sans debian branch with docs mods.)

Official DEVUAN
https://git.devuan.org/devuan-packages/slim          (sans themes) do check the branch !

Finally mine which once again you will need to check branches.
The only useful thing may be the new dual format Docs  or unstable branch. e.g.
(docutils (rst) or md which just means being a little careful really)

https://git.devuan.org/PeteGozz/slim/bl … /THEMES.md

The INSTALL files has at this time instructions on how to disable consolekit / dbus
just as an experimental example you understand.

PS. Themers need to note the config  file settings !
Lest stuff wont actually work.

Did I mention that you should check the branch ?
The final (canonical)  upstream is SVN it can be found from the github master branch.
(or duckduck)


Own your own tools.
Break them your way.

Offline

#16 2017-07-10 18:45:13

greenjeans
Member
Registered: 2017-04-07
Posts: 278
Website

Re: Slim and build settings

PeteGozz wrote:

So here is the state of slim as seen by me Mon July 20th 2017.

Time machine?

wink


https://sourceforge.net/projects/vuu-do/
Vuu-do GNU/Linux, minimal 64 and 32 bit Devuan-based openbox and mate systems to build on, maximal versions if you prefer your linux fully-loaded.

Refracta and Miyolinux had too many tequila shots one night...    ....9 months later a vuu-do chile was born.....;-)

Offline

#17 2017-07-11 01:59:40

PeteGozz
Member
From: Woodside South Australia
Registered: 2017-06-21
Posts: 62

Re: Slim and build settings

Ah .. yep smile
oops .
No idea  why I did that . ..
Its my glasses !

PeteGozz wrote:

There are a few forks and pull requests most of them growing old.
Including mine:

lol
and
ME

Gunna leave it there as a reminder sad

Last edited by PeteGozz (2017-07-11 02:03:31)


Own your own tools.
Break them your way.

Offline

#18 2017-07-11 14:22:53

PeteGozz
Member
From: Woodside South Australia
Registered: 2017-06-21
Posts: 62

Re: Slim and build settings

Just for "giggles" and testing

And not for general users I have made no deb for this.

I've started a branch called debugg with
   - "modernised" docs
      docutils and markdown friendly all in one file.
  - Hopefully clearer INSTALL instructions
  - A new bugg theme to login with
  - More info in /etc/slim.conf
This all builds easily and reliably here of course.
YMMV.  cmake gives good hints.

You should not need lib-consolekit* or libdbus*
If you follow INSTALL subtle clues.
(and it don't need no task-desktop-* !)

https://git.devuan.org/PeteGozz/slim/tree/debugg

The extra g in debug is meant to make it obvious ... made sense this morning.

Last edited by PeteGozz (2017-07-11 14:31:44)


Own your own tools.
Break them your way.

Offline

#19 2017-07-11 15:01:49

fsmithred
Administrator
Registered: 2016-11-25
Posts: 377

Re: Slim and build settings

Bugs are crawling up my legs!
    -- Laurie Anderson

It builds. It installs. It runs. It frightens.

It worked on 2 out of 3 ascii systems. The third one lacks dbus, consolekit and libck-connector0, so I didn't install it on that one. I didn't look at the docs.

Offline

#20 2017-07-11 15:07:22

PeteGozz
Member
From: Woodside South Australia
Registered: 2017-06-21
Posts: 62

Re: Slim and build settings

fsmithred wrote:

Bugs are crawling up my legs!
    -- Laurie Anderson

It builds. It installs. It runs. It frightens.

It worked on 2 out of 3 ascii systems. The third one lacks dbus, consolekit and libck-connector0, so I didn't install it on that one. I didn't look at the docs.

smile

I um went a lttle further than I intended with the pretty beetles  smile

lol who ever _reads the docs _ .

So you did a default cmake ../  ?
rather than 
cmake ../ -DUSE_PAM=yes  -DUSE_CONSOLEKIT=no

?
DOH!
I can get rid of dbus, consolekit and libck-connector0 here come to think of it.
((goes away does much of that. Everything keeps working ))

OK so got rid of consolekit* libck-connector0 --purged
It removed some unneeded gnomeish  stuff.

(and one gst thing I'll get back later)
I could not remove all of the dbus libs as there was a pulse dep lockin that took out most of X ...
[[[later]]]]

However DBUS gone (no system service left) dbus: unrecognized service

Builds fine  I didn't try a default build .
(as above)
Tests fine with :

slim -p /usr/local/share/slim/themes/buggs/

NB local install.

Last edited by PeteGozz (2017-07-12 00:12:06)


Own your own tools.
Break them your way.

Offline

#21 2017-07-11 15:21:23

fsmithred
Administrator
Registered: 2016-11-25
Posts: 377

Re: Slim and build settings

git clone https://git.devuan.org/PeteGozz/slim.git
cd slim
git checkout debugg
nano debian/changelog   #bump version
fakeroot dpkg-buildpackage -us -uc -b
dpkg -i slim_1.3.6-5+devuan4~pg2_amd64.deb

Edit: doing it again after setting consolekit to NO in debian/rules

Edit2: without consolekit, I lose reboot/suspend/shutdown buttons in xfce and I also lose the bug login background. (I get the pink slim blood&guts theme.)

Offline

#22 2017-07-11 15:36:37

PeteGozz
Member
From: Woodside South Australia
Registered: 2017-06-21
Posts: 62

Re: Slim and build settings

fsmithred wrote:
dpkg -i slim_1.3.6-5+devuan4~pg2_amd64.deb

Edit: doing it again after setting consolekit to NO in debian/rules

Excellent at least your on amd64 !
Also YES you do not need to set USE_PAM

We could simply default NO  to  consolekit easily enough.
CmakeList   top level.

Could remove it all together but I am not sure what DBUS ramifications (if any) there would be.
Also would not suggest this for jessie users.


Own your own tools.
Break them your way.

Offline

#23 2017-07-11 15:39:59

fsmithred
Administrator
Registered: 2016-11-25
Posts: 377

Re: Slim and build settings

consolekit is needed for shutdown and reboot buttons to work. This has been a recurring issue since about when we started on this path a couple years ago.

Offline

#24 2017-07-11 15:47:49

PeteGozz
Member
From: Woodside South Australia
Registered: 2017-06-21
Posts: 62

Re: Slim and build settings

fsmithred wrote:

consolekit is needed for shutdown and reboot buttons to work. This has been a recurring issue since about when we started on this path a couple years ago.

OH bummer.
People shut down computers ?

I really should try the GUI things more often.

me wrote:

update:
Just tested this here from a local install
started from console under sudo.

$ sudo slim -d

Both halt and reboot worked fine.
(with roots password)
and exit dropped me back to console tty no worries.

Perhaps its the init script includes or something ?
(note for later)

/update

Still easy enough to "fix" now. Just add USE_CONSOLEKIT=yes  (or =1)
Or rather just do a default cmake ../

It does a nice job doing the Right Thing [TM] anyhow.


Hmm should be able to use a "proper" system call > pam  or at least an extern or something.
It needed root password as well ...
consolekit has been depreciated I think ???

[cogitation ]

OK I will put my hand up for this.
I have a passing familiarity with the code base now.
(I am insane)

C++ ((shudder)) OK.

Off to read the code base.

Also GIT ROCKS !!!

Last edited by PeteGozz (2017-07-11 16:12:10)


Own your own tools.
Break them your way.

Offline

#25 2017-07-11 17:13:39

fsmithred
Administrator
Registered: 2016-11-25
Posts: 377

Re: Slim and build settings

Not only do they shut them down, they do it without the root password! Big fancy desktop environments (that you've heard about ) provide buttons and/or menu entries for this. Whether those work or not in devuan seems to be somewhat of a crap shoot.

There are several threads about it here and it's come up in irc several times. Search forum for some combination of the following keywords:

consolekit policykit-1 libpam-ck-connector upower shutdown reboot suspend hibernate

I know I'm missing something again. Pretty sure there are more than four packages on that list.

If that was you volunteering to maintain slim at the end of you message, THANK YOU!  Probably you and Centurion Dan should get together and talk (while I'm asleep) and we can get an installable slim in ascii.

Edit: ...and xfce4-power-manager

Offline

Board footer