The officially official Devuan Forum!

You are not logged in.

#1 Re: Installation » Installation without Session management and policykit backends » 2018-08-20 14:11:37

@golinux ... If I act this way, it is because I have my reasons.

#2 Re: Installation » Installation without Session management and policykit backends » 2018-08-20 06:08:22

One more answer for fsmithred:

I appreciate your efforts to find a permanent solution to have a desktop working without consolekit and policykit-1 and I thank you for your desire to do everything possible so that the problem does not recur in the next release.

It seems to me that this topic has not had much participation in the forum. I do not have understand if the topic affects most users. So I will not add anything else.

Since I would like to share some other useful information with you, I will send you an e-mail as soon as possible.

I thank all those who have somehow participated in the discussion.

#3 Re: Installation » Installation without Session management and policykit backends » 2018-08-19 05:51:10

An attempt to answer fsmithred:

In a modern Desktop "to allow the [normal] user to perform several typical tasks without requiring administrator privileges, including suspending/rebooting shutting down the system, mounting external devices, configuring networking, and so on" (I cite from Ascii Release_notes), a lot of software was created (mainly by freedesktop.org), in my opinion, very complicated and difficult to manage.

I refer to slim/lightdm (DM), policykit-1, consolekit, gvfs, udisks2, pulseaudio, et cetera.

This software, if properly installed and configured appropriately, allows even to an user with a very poor knowledge of Linux, to perform with a few mice clicks the operations listed above (but only in a standard way!).

I am convinced that for users who have sufficient OS experience (such as the majority of Devuan users), this software offers no advantages.

This is because if you want things go as you like, you have to master it very well. It is better to perform the above operations from a root terminal with scripts or with a few commands. In the Unix-like OS these operations are root prerogatives and these programs are designed to make them accessible to a normal user.

This is the idea that I have done in recent years. It's a personal opinion that I practice daily. So I avoid installing software that I don't I feel the need.

To respond more directly I say that consolekit is an important part (not the only) of the software that allows a user to perform operations related to management of the hardware: all together, consolekit, policykit-1 and the DM, not just one of them! gvfs, policykit-1 and udisks2 allow to manage the devices mounting to the simple user. These operations are performad by programs started by the login manager (root) and communicating via dbus with the DE. It is a complicated "mechanism" difficult to understand and control!

I do not have the right knowledge to comment on the other statement:

A simple solution would be to move those dependencies to Recommends. Then anyone who wanted a minimalist xfce could install without recommends.

Consolekit, policykit-1 ed il login manager are dependent on each other and all togheter communicate via dbus. In post # 16 I wrote:

In my opinion, however, the DE functionalities (requiring administrative privilegies)  that depend on consolekit are more related to DM (slim/lightm) than to the session manager. So consolekit/elogind must be mandatorily installed with the display manager and not with the session manager.

Nothing would change for those who use an DE with all its features, but would allow use of the DE, with some limitations, even with startx, without a DM.

We need to know in detail how this software is built to propose an appropriate solution. Only those who know and manage these packages can find the better answer.

Unfortunately my English is poor and doesn't allow me to express myself adequately. I hope that what I wrote is understandable!

#4 Re: Installation » Installation without Session management and policykit backends » 2018-08-18 10:04:19

I inform interested parties how I solved the problem submitted to the forum a few weeks ago. It seems to me that the solution found is acceptable as well as the one proposed by fsmithred a few days ago.

After installing the XFCE4 components that interest us and that do not contain dependencies from consolekit/elogind, proceed as follows for "xfce4-session" package (that depends on consolekit/elogind):

  • Download the packages (or altenatively the i386 version):
           a) xfce4-session_4.12.1-3+devuan1_amd64.deb
           b) libpolkit-gobject-consolekit-1-0_0.105-18+devuan2.11_amd64.deb

  • Edit the xfce4-session package above downloaded, remove the dependency from libpolkit-gobject-1-0 and save it with the same name.

  • Edit the libpolkit-gobject-consolekit-1-0 above downloaded, remove the dependency from consolekit and save it with the same name.

  • Install the two packages modified with the command: dpkg -i .

Now it is possible to start XFCE4 with the "startxfce4" command. The desktop works normally like in Jessie, obviously without the features provided by consolekit and policykit-1.

There is an inconvenience: Because the two packages do not conform to the contents of apt-cache, if you upgrade the system them will be updated with those of the Devuan depository (which contain consolekit).

To remedy this problem: before upgrading, remove them (dpkg -r) and install them again after the upgrade (dpkg -i).

There is certainly a better and more elegant solution. But we need to have some knowledge and experience that, unfortunately, I do not have!

Who is capable, wants and can, signals to the developers of Devuan the impossibility for how the libpolkit-gobject-1-0 package is built, to use XFCE4 without installing consolekit/elogind. It is against the software freedom principle: we must not force anyone to use unwanted software! I hope they take this into account and that the next release (beowulf) no longer presents the problem!

That's all folks!

#5 Re: Installation » Installation without Session management and policykit backends » 2018-08-16 16:08:22

Thank you very much, fsmithred, for you reply.

You did a great job to help me, but it was enough to tell me that it was possible to start the XFCE desktop using the instructions:

xfwm4 &
xfce4-panel &
xfdesktop

instead of "xfce4-session". I put these instructions in  ~/.Xsession file and the desktop starts without problems. Unfortunately some features are not present due to the absence of the session manager (xfce4-session).

These days I'm learning to edit .deb packages because it's my intention edit the Ascii xfce4-session.deb package to make it identical to Jessie's package, eliminating consolekit/elogind dependencies.

Yesterday, instead of XFCE4, I installed openbox and lxpanel: everything works fine. Although consolekit/elogind is installed with lxpanel, then it can be removed because, for lxpanel, it is a recommended not mandatory package.

So, in my opinion, it is sufficient to make the consolekit/elogind package recommended for "xfce4-session" instead of mandatory. I hope I can do it.

I will keep you informed of the result.

Still many thanks for your help.

#6 Re: Installation » Installation without Session management and policykit backends » 2018-08-13 06:28:36

Thank you, fsmithred, for your post. I really appreciate your desire to help me but it seems you have not read all the previous posts.

Since I have not installed a DM, of course I use "startx" to start X server, but to start the desktop, in the .Xsession file there must be "startxfce4". That I know, this is the only method to start xfce. Unfortunately, "startxfce4" is installed with xfce4-session.

I know very well Openbox and lxpanel, I used them for a long time before moving to xfce4.

I'm in no hurry to migrate to Ascii. In Jessie Xfce it works great without consolekit, policykit-1 and even gvfs and udisks2. There are still two years before jessie is no longer supported. I hope that during these two years, the installation of consolekit/elogin will be modified and/or that it is possible to remove it. Software freedom is one of the principles for which Devuan was born.

I take this opportunity to thank you for creating refractasnapshot/installer. I use it for a long time (I still keep and use an Ubuntu-12.04 snapshot!). In these years it was really very helpful and saved me so much effort! really many thanks!

#7 Re: Installation » Installation without Session management and policykit backends » 2018-08-10 05:55:18

I am very amazed at the statements in the last posts of fsmithred and golinux.I report what I wrote in the past days.
In post #13 I wrote:

Yesterday I tried to follow the suggestions of fsmithred and install its components instead of xfce4. I started with installing "xfce4-session" because it is the only one that depends on consolekit. After installing it I tried to remove consolekit, but unfortunately the usual problem came back: apt-get purge consolekit, once again, before removing consolekit files it automatically installs elogind and its dependencies.

and yestrerday:

And, though XFCE4 is modular, "xfce4-session" is essential because it installs "startxfce4" which
serves to start the desktop itself.

I add today: xfconf xfdesktop4 xfwm4 xfce4-panel packages can be installed without problem and not contain dependencies from consolekit/elogind. But "xfce4-session" is essential because the desktop is started with "startxfce4" which is installed with "xfce4-session". Since I do not know, nor did I find anywhere else, another method to start the desktop, I wrote that the only solution possible is to modify the "xfce4-session" package.

The statement of golinux:

Indeed, that 'should' work.  I suggested it - more than once IIRC - but don't think (s)he ever tried it.

is unjustified and the result of his imagination.

I thank Ogis1975 for his suggestion.

#8 Re: Installation » Installation without Session management and policykit backends » 2018-08-09 16:38:44

I opened this post weeks ago with the wish to have the necessary suggestions for to be able to migrate from jessie to the new release and continue to use Devuan without Session management and policykit backends.

I seem to have understood, in these weeks, that in releasing Ascii the main concern of the developers was to provide desktops with all the functionality.
As is well explained in the Release Notes, this requires the simultaneous use of a Display/Login Manager (DM) and a Session Manager, i.e. slim/lightdm and consolekit/elogind.

The desktop packages I'm interested in (XFCE4) are built so that a Session manager is always installed. Among the automatic dependencies of "xfce4-session" is present consolekit/elogind which can not be removed. And, though XFCE4 is modular, "xfce4-session" is essential because it installs "startxfce4" which serves to start the desktop itself.

This choice for the Ascii "xfce4-session" package certainly ensures a desktop fully functional, but prevents, for those who want it, to have an OS more lightweight without consolekit/elogind, policykit-1 and a DM.

Such a choice is incomprehensible. If you want to give up "tasks requiring administrator privileges, including/suspending/rebooting/shutting down the system, mounting external devices, configuring networking, and so on" consolekit/elogind is not required! Furthermore, the sole presence of elogind, without the login manager, is insufficient to ensure the operation of the tasks listed above. So why its presence is mandatory?

It's also the first time that I can not remove a package as root. Usually root can perform any action and has no limitation. It can happen that he performs a wrong operation: the OS will stop work, but nothing is forbidden to root! So why prevent him from removing elogind? Why not preserve the freedom of everyone to decide what to install or remove?

I don't have the skills to modify the "xfce4-session" package and therefore I am forced to suspend the migration to Ascii.

I will continue to use Jessie which I am very satisfied with. I read that it is supported until 2020-06-30 ... there is plenty of time to find a solution.

If nobody has anything to add, as far as I'm concerned, the post can be considered closed!

Thank you all.

#9 Re: Installation » Installation without Session management and policykit backends » 2018-07-26 05:13:04

A partial answer to the golinux question:

In jessie, the command debfoster --show-dependents xfce4-session ensures that no package installed depends on xfce4-session; therefore it can be removed.

root@pc64-xx:~# debfoster --show-dependents xfce4-session
Packages on the keeper list do not rely on xfce4-session.
Packages kept by default rules do not rely on xfce4-session.
root@pc64-xx:~#

However it is important to evaluate what implies its removal. It may be that some DE functionality is inhibited, or at least limited. We should try and test the DE for a few days ... I hope I can do it soon on Ascii.

Even in the south, activities slow down in the summer. These days the high temperatures reached during the day invite to laze.

Thanks for the suggestion to discuss to #devuan-dev on freenode, but my poor english doesn't help me much. However, in the next days I will evaluate.

#10 Re: Installation » Installation without Session management and policykit backends » 2018-07-25 07:54:30

Quick reply:

1) for cynwulf: consolekit isn't a recommended package for xfce4-session ... it is automatic !
    with apt-get purge consolekit ... elogind is also automatic!

2) for golinux: You are right, to use an DE with all its functionalities, a session manager, policykit-1 and
    a display manager are required. I have not checked yet if xfce without the session manager is working
    correctly. These are not simple things and should be tested one at a time. Until now I have only tried
    to reproduce Jessie's situation. If it will not be possible I will try to understand the alternatives later.

thank you both

Added at 10:49 CEST for golinux:

I really appreciate the efforts of Devuan developers to make the most DE work properly. In my opinion, however, the DE functionalities (requiring administrative privilegies)  that depend on consolekit are more related to DM (slim/lightm) than to the session manager. So consolekit/elogind must be mandatorily installed with the display manager and not with the session manager.

Nothing would change for those who use an DE with all its features, but would allow use of the DE, with some limitations, even with startx, without a DM.

#11 Re: Installation » Installation without Session management and policykit backends » 2018-07-25 06:52:26

Yesterday I tried to follow the suggestions of fsmithred and install its components instead of xfce4.

I started with installing "xfce4-session" because it is the only one that depends on consolekit. After installing it I tried to remove consolekit, but unfortunately the usual problem came back: apt-get purge consolekit, once again, before removing consolekit files it automatically installs elogind and its dependencies.

Since it is the only package that depends on consolekit it can be concluded that the problem arises from there.

Unfortunately I can not follow the golinux suggestion and modify this package because I do not have the right knowledge.

Is it possible to have some suggestions from the developper who built the xfce4-session package for Ascii?

#12 Re: Installation » Installation without Session management and policykit backends » 2018-07-24 05:05:56

Thank you all, your suggestions are precious!

I add now some information that pinpoint the problem more accurately.

1) the  debfoster --show-dependents consolekit command ensures that the only installed
package that depends on consolekit is Xfce4.

root@dev-32:~# debfoster --show-dependents consolekit
The following 1 packages on the keeper list rely on consolekit:
  xfce4
Packages kept by default rules do not rely on consolekit.

2) Following are the lines of the files /var/log/apt/history.log of Jessie and Ascii, generated with the
command apt-get purge consolekit.

In Jessie
----------------------------------------------------------------------------

Start-Date: 2017-12-04  20:54:40
Commandline: apt-get -y purge gvfs policykit-1 consolekit udisks2
Purge: consolekit:i386 (0.4.6-5), policykit-1-gnome:i386 (0.105-2), gvfs:i386 (1.22.2-1), colord:i386 (1.2.1-1+devuan1), udisks2:i386 (2.1.3-5+devuan3), vfs-daemons:i386 (1.22.2-1), policykit-1:i386 (0.105-9+devuan1)
End-Date: 2017-12-04  20:54:46

In Ascii
----------------------------------------------------------------------------

Start-Date: 2018-07-22  09:24:06
Commandline: apt-get purge consolekit
Install: libpam-elogind:i386 (234.4-2, automatic), elogind:i386 (234.4-2, automatic), libelogind0:i386 (234.4-2, automatic), libpolkit-gobject-elogind-1-0:i386 0.105-18+devuan2.11, automatic)
Purge: consolekit:i386 (0.4.6-6), libpolkit-backend-consolekit-1-0:i386 (0.105-18+devuan2.11), upower:i386 (1:0.9.23-2+devuan1.3), libpam-ck-connector:i386 0.4.6-6), libpolkit-backend-1-0:i386 (0.105-18+devuan2.11), policykit-1:i386 (0.105-18+devuan2.11), libpolkit-gobject-consolekit-1-0:i386 (0.105-18+devuan2.11)
End-Date: 2018-07-22  09:24:17

How you can see, the behavior of apt-get is different: in Jessie it simply purge the required files; in Ascii, instead, before removing consolekit files it automatically installs elogind and its dependencies.

It would be interesting to understand the reasons why those who built the  consolekit package for Ascii required such behavior.

Unfortunately I don't have a thorough knowledge of apt-get nor in his man pages I have found a parameter that allows to remove consolekit without installing logind.

But, there's a way to prevent apt automatically installing elogind?

Tips and suggestions are welcome!

#13 Re: Installation » Installation without Session management and policykit backends » 2018-07-23 15:23:39

I agree, golinux: The consolekit/policykit stuff is complicated. So I do not want to install them! I do not even use a display manager and so I have not nstalled either slim or lightdm.

As I wrote in the initial post, in my opinion, this software, for the difficulties in becoming familiar with it, creates more problems than advantages!

In jessie, I use startx to launch a graphical session with XFCE and everything works fine. Obviously, without consolekit and policykit-1, the buttons to perform actions that require administrator privileges (such as hibernate, suspend and shutdown) are inhibited. Even the automatic mount of the devices is not allowed and I manually mount them from a root terminal.

Unfortunately I can not recreate this situation in ASCII because it seems that consolekit or elogind must be installed even so without a display manager is absent.

#14 Re: Installation » Installation without Session management and policykit backends » 2018-07-23 08:23:36

Thank you, golinux, for your quick reply.
I certainly do not install XFCE with netinst, but I use the command: apt-get install xfce4.
Immediately after: apt-get purge consolekit policykit-1 gvfs udisks2.

apt-get does not just remove consolekit, but automatically installs elogind. and if I remove elogind back to install consolekit !!

In my opinion, the problem is in how the xfce package is built.

It should do this only if you want a normal user to use task requiring administrator privileges,
otherwise it should simply remove consolekit ... It should be possible to choose ..

#15 Installation » Installation without Session management and policykit backends » 2018-07-23 07:15:14

campus
Replies: 37

I have been using Devuan for over a year and I am very satisfied.

Thanks to Devuan Jessie it was able to create a personal Desktop with  XFCE without being obliged to install consolekit, policykit-1, gvfs,
udisks2 and even a display manager and pulseaudio (software that in most of the cases, in my opinion, creates more problems than advantages).

A few days ago I learned that the new ASCII release was released. With enthusiasm I downloaded it with the desire to migrate to this
new release as soon as possible.

The installation with Netinst proceeds smoothly, but, unfortunately, I have not been able to rebuild my personal distribution that I have with Jessie 1.0.

The obstacle I found is the impossibility of removing consolekit afterwards installed XFCE, as was possible in Jessie, without obligatorily install elogind.

It seems that it is no longer possible to use XFCE without (I quote from Ascii release notes) "to grant processes in the unprivileged user
session access to select privileged operations ".

Instead with Jessie I was able to remove unwanted software (consolekit, policykit-1, gvfs, udisks2) with the obvious inhibition for a normal user to use "task requiring administrator privileges, including suspending / rebooting / shutting down the system, mounting external devices, configuring networking, and so on ".

I do not have enough experience and knowledge to do some hypothesis on the reasons for this new situation. I do not understand why it is no
longer possible to remove unwanted software by renouncing the use of some tasks (software freedom).

I am therefore forced to suspend the migration to Ascii.

May someone kindly clarify the situation better and give me some suggestion?

Thank you all.

Board footer

Forum Software