Re: [DNG] IMPORTANT! How to fix degraded session management after Devuan ASCII upgrade.

[Didier Kryn]

Le 15/02/2018 à 08:08, J. Fahrner a écrit :

Am 2018-02-14 23:51, schrieb Didier Kryn:

    The line is there in /etc/slim.conf

    And the file exists in several places:

root@apcnb98:/home/kryn# locate desktop-slim-theme
/etc/alternatives/desktop-slim-theme
/usr/share/slim/themes/desktop-slim-theme
/var/lib/dpkg/alternatives/desktop-slim-theme


Ok, now try "update-alternatives --config desktop-slim-theme" and 
select the theme devuan-curve-darkpurpy.




    Seems it was already properly configured:

 Begining of  dialog --
root@apcnb98:/home/kryn# update-alternatives --config desktop-slim-theme
There are 2 choices for the alternative desktop-slim-theme (providing 
/usr/share/slim/themes/desktop-slim-theme).


  Selection Path   Priority   
Status


  0 /usr/share/slim/themes/devuan-curve-darkpurpy   15    auto mode
  1 /usr/share/slim/themes/default  1 manual mode
* 2 /usr/share/slim/themes/devuan-curve-darkpurpy   15    manual mode

Press  to keep the current choice[*], or type selection number:2
root@apcnb98:/home/kryn#
- End of dialog -

    Still grey )-:

                        Didier
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] IMPORTANT! How to fix degraded session management after Devuan ASCII upgrade.

[J. Fahrner]

Am 2018-02-14 23:51, schrieb Didier Kryn:

    The line is there in /etc/slim.conf

    And the file exists in several places:

root@apcnb98:/home/kryn# locate desktop-slim-theme
/etc/alternatives/desktop-slim-theme
/usr/share/slim/themes/desktop-slim-theme
/var/lib/dpkg/alternatives/desktop-slim-theme


Ok, now try "update-alternatives --config desktop-slim-theme" and select 
the theme devuan-curve-darkpurpy.

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] IMPORTANT! How to fix degraded session management after Devuan ASCII upgrade.

[Didier Kryn]

Le 14/02/2018 à 17:17, J. Fahrner a écrit :

Am 2018-02-14 17:05, schrieb Didier Kryn:


Everything works fine, except slim has lost its beautifull background.
Now its background is just grey.


Yout /etc/slim.conf should have a line

current_theme desktop-slim-theme

And the theme files are in package desktop-base


    The line is there in /etc/slim.conf

    And the file exists in several places:

root@apcnb98:/home/kryn# locate desktop-slim-theme
/etc/alternatives/desktop-slim-theme
/usr/share/slim/themes/desktop-slim-theme
/var/lib/dpkg/alternatives/desktop-slim-theme


Le 14/02/2018 à 18:32, Irrwahn a écrit :

H ... you might try to (re-)install the desktop-base package from
Devuan. It has the theme for slim IIRC (among other stuff).
    Did it with no effect - I did a reboot. Probably just restarting 
slim would have sufficed.


    Still grey. BTW the file isn't found by apt-file:

root@apcnb98:/home/kryn# apt-file search desktop-slim-theme
root@apcnb98:/home/kryn#

        Didier



___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] IMPORTANT! How to fix degraded session management after Devuan ASCII upgrade.

[Irrwahn]

Hleb Valoshka wrote on 14.02.2018 21:54:
> On 2/14/18, Irrwahn  wrote:
> Fresh installations of Devuan ASCII 2.0.0 Beta should not be affected.
 Actually no, i've installed Ascii for testing purposes and systemd
 policykit backend was pulled.
>>> That's a first AFAICT. Noted.  Thanks, Hleb! :)
>>> Oh, you wouldn't have by any chance saved the package list in that state?
>>> In the unlikely case you have, could you please email it to me?
> 
> I created a ascii chroot using debootstrap and then installed
> task-xfce-desktop using interactive mode of aptitude, which showed 2
> broken packages - backend and gobject of policykit. It was the
> previous weekend, so there is tiny chance that the is issue has been
> solved already (for clean installations).

That might indeed be the case, as there were some last-minute 
changes to the policykit packages right before the beta release. 
 
>> P.S.:
>> I forgot to ask: Did you use a package mirror or did you perform a purely
>> offline install?
> 
> I used http://deb.devuan.org/merged

That's fine, then.

Thanks for the info! :)
 
Urban
-- 
Sapere aude!
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] IMPORTANT! How to fix degraded session management after Devuan ASCII upgrade.

[Irrwahn]

Dr. Nikolaus Klepp wrote on 14.02.2018 21:35:
[...]
> On my system it tried to pull in libpolkit-gobject-1-0-systemd. The reason 
> was aptitude: "twin-trinity" (which is installed) provides 
> "x-display-manager" was ignored, instead aptitude resolved by some obscure 
> reason that the not installed "cinnamon" provides "x-display-manager", so 
> "libpolkit-gobject-1-0-systemd" has to be installed (but not "cinnamon"), 
> ignoring "twin-trinity" which already provides "x-display-manager".
> 
> The second solution that aptitude resolved did not pull in 
> "libpolkit-gobject-1-0-systemd", so that was no big issue.
> 
> After I followed your advise giving in 
> https://lists.dyne.org/lurker/message/20180214.123746.e89eaef8.en.html (I 
> decided to go with elogind) aptitude did resove correctly.

Hi, 

thank you for your valuable feedback! We will definitely have to have 
a closer look at the dependency chains in that whole area. 

Best regards
Urban

-- 
Sapere aude!
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] IMPORTANT! How to fix degraded session management after Devuan ASCII upgrade.

[Hleb Valoshka]

On 2/14/18, Irrwahn  wrote:
 Fresh installations of Devuan ASCII 2.0.0 Beta should not be affected.
>>> Actually no, i've installed Ascii for testing purposes and systemd
>>> policykit backend was pulled.
>> That's a first AFAICT. Noted.  Thanks, Hleb! :)
>> Oh, you wouldn't have by any chance saved the package list in that state?
>> In the unlikely case you have, could you please email it to me?

I created a ascii chroot using debootstrap and then installed
task-xfce-desktop using interactive mode of aptitude, which showed 2
broken packages - backend and gobject of policykit. It was the
previous weekend, so there is tiny chance that the is issue has been
solved already (for clean installations).

> P.S.:
> I forgot to ask: Did you use a package mirror or did you perform a purely
> offline install?

I used http://deb.devuan.org/merged
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] IMPORTANT! How to fix degraded session management after Devuan ASCII upgrade.

[Dr. Nikolaus Klepp]

Am Mittwoch, 14. Februar 2018 schrieb Irrwahn:
> Hleb Valoshka wrote on 14.02.2018 19:20:
> > On 2/14/18, Irrwahn  wrote:
> > 
> >> Fresh installations of Devuan ASCII 2.0.0 Beta should not be affected.
> > 
> > Actually no, i've installed Ascii for testing purposes and systemd
> > policykit backend was pulled.
> 
> That's a first AFAICT. Noted.  Thanks, Hleb! :)
> 
> Oh, you wouldn't have by any chance saved the package list in that state? 
> In the unlikely case you have, could you please email it to me?
> 
> Thanks again & best regards
> Urban
> 

Hi!

On my system it tried to pull in libpolkit-gobject-1-0-systemd. The reason was 
aptitude: "twin-trinity" (which is installed) provides "x-display-manager" was 
ignored, instead aptitude resolved by some obscure reason that the not 
installed "cinnamon" provides "x-display-manager", so 
"libpolkit-gobject-1-0-systemd" has to be installed (but not "cinnamon"), 
ignoring "twin-trinity" which already provides "x-display-manager".

The second solution that aptitude resolved did not pull in 
"libpolkit-gobject-1-0-systemd", so that was no big issue.

After I followed your advise giving in 
https://lists.dyne.org/lurker/message/20180214.123746.e89eaef8.en.html (I 
decided to go with elogind) aptitude did resove correctly.


Nik





-- 
Please do not email me anything that you are not comfortable also sharing with 
the NSA, CIA ...
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] IMPORTANT! How to fix degraded session management after Devuan ASCII upgrade.

[Irrwahn]

Irrwahn wrote on 14.02.2018 19:46:
> Hleb Valoshka wrote on 14.02.2018 19:20:
>> On 2/14/18, Irrwahn  wrote:
>>
>>> Fresh installations of Devuan ASCII 2.0.0 Beta should not be affected.
>>
>> Actually no, i've installed Ascii for testing purposes and systemd
>> policykit backend was pulled.
> 
> That's a first AFAICT. Noted.  Thanks, Hleb! :)
> 
> Oh, you wouldn't have by any chance saved the package list in that state? 
> In the unlikely case you have, could you please email it to me?

P.S.:  
I forgot to ask: Did you use a package mirror or did you perform a purely 
offline install? 

Urban
-- 
Sapere aude!
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] IMPORTANT! How to fix degraded session management after Devuan ASCII upgrade.

[Irrwahn]

Hleb Valoshka wrote on 14.02.2018 19:20:
> On 2/14/18, Irrwahn  wrote:
> 
>> Fresh installations of Devuan ASCII 2.0.0 Beta should not be affected.
> 
> Actually no, i've installed Ascii for testing purposes and systemd
> policykit backend was pulled.

That's a first AFAICT. Noted.  Thanks, Hleb! :)

Oh, you wouldn't have by any chance saved the package list in that state? 
In the unlikely case you have, could you please email it to me?

Thanks again & best regards
Urban

-- 
Sapere aude!
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] IMPORTANT! How to fix degraded session management after Devuan ASCII upgrade.

[Hleb Valoshka]

On 2/14/18, Irrwahn  wrote:

> Fresh installations of Devuan ASCII 2.0.0 Beta should not be affected.

Actually no, i've installed Ascii for testing purposes and systemd
policykit backend was pulled.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] IMPORTANT! How to fix degraded session management after Devuan ASCII upgrade.

[Irrwahn]

Didier Kryn wrote on 14.02.2018 17:05:
> Le 14/02/2018 à 16:21, Irrwahn a écrit :
[...]
>> Just go ahead, have your session management of the day!;-P
> 
>      Did that, I reinstalled slim and made it the DM in charge. 
> Everything works fine, except slim has lost its beautifull background. 
> Now its background is just grey.
> 
>              Didier

H ... you might try to (re-)install the desktop-base package from 
Devuan. It has the theme for slim IIRC (among other stuff).

Urban

-- 
-- 
Sapere aude!
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] IMPORTANT! How to fix degraded session management after Devuan ASCII upgrade.

[J. Fahrner]

Am 2018-02-14 17:05, schrieb Didier Kryn:


Everything works fine, except slim has lost its beautifull background.
Now its background is just grey.


Yout /etc/slim.conf should have a line

current_theme desktop-slim-theme

And the theme files are in package desktop-base.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] IMPORTANT! How to fix degraded session management after Devuan ASCII upgrade.

[Didier Kryn]

Le 14/02/2018 à 16:21, Irrwahn a écrit :

      Sure it is possible to have both Consolekit and Elogind, but can
they be both active?

              Didier

Yes.

Oh, how I would know, you might ask.  Well, for a start, I'm typing this
message on a desktop machine where it's the case.:)

As I wrote in the OP: Which one gets the cookie, so to speak, is decided
by the choice of polkit backend. Currently elogind here, but I could just
as well swap it out for the consolekit backend library, should I decideto
start my lightdm/Xfce desktop that way.

Just go ahead, have your session management of the day!;-P


    Did that, I reinstalled slim and made it the DM in charge. 
Everything works fine, except slim has lost its beautifull background. 
Now its background is just grey.


            Didier



___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] IMPORTANT! How to fix degraded session management after Devuan ASCII upgrade.

[Irrwahn]

leloft wrote on 14.02.2018 15:46:
[...]
> I do not know anything like enough to do anything more than comment, but
> does the above indicate that the *-backend-systemd is being pulled in
> as a result of an unhelpful dependency chain.  And why does the
> installation of libpolkit-backend-1-0-consolekit pull in 
> elogind libelogind0 libpam-elogind libpolkit-gobject-1-0-systemd
> when consolekit has been installed in preference to elogind?
[...]

It would appear so, but just now it's hard to put the finger on the 
exact spot where things are wired wrong. This is but one of the kinks 
to expect in beta release, and the very reason why there is a beta 
released in the first place. I'm sure it will eventually get sorted out.

And, FWIW, the backend-systemd could IMHO easily be dropped entirely, 
as it would be rather peculiar for someone to actually try and force a 
genuine systemd package into Devuan, of all systems. ;o)

Best regards
Urban

-- 
Sapere aude!
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] IMPORTANT! How to fix degraded session management after Devuan ASCII upgrade.

[Irrwahn]

Didier Kryn wrote on 14.02.2018 15:54:
> Le 14/02/2018 à 15:32, Irrwahn a écrit :
>> Removing consolekit isn't mandatory, but yes, in doing so one causes
>> same breakage just as you described.
> 
>      Sure it is possible to have both Consolekit and Elogind, but can 
> they be both active?
> 
>              Didier

Yes. 

Oh, how I would know, you might ask.  Well, for a start, I'm typing this
message on a desktop machine where it's the case.  :)

As I wrote in the OP: Which one gets the cookie, so to speak, is decided 
by the choice of polkit backend. Currently elogind here, but I could just 
as well swap it out for the consolekit backend library, should I decide to 
start my lightdm/Xfce desktop that way. 

Just go ahead, have your session management of the day! ;-P

And kudos to the fine chaps that made it possible!

Urban

-- 
Sapere aude!
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] IMPORTANT! How to fix degraded session management after Devuan ASCII upgrade.

[Didier Kryn]

Le 14/02/2018 à 15:32, Irrwahn a écrit :

Removing consolekit isn't mandatory, but yes, in doing so one causes
same breakage just as you described.


    Sure it is possible to have both Consolekit and Elogind, but can 
they be both active?


            Didier

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] IMPORTANT! How to fix degraded session management after Devuan ASCII upgrade.

[leloft]

On Wed, 14 Feb 2018 13:37:46 +0100
Irrwahn  wrote:

>   It would appear that under certain circumstances an unsuitable
> flavor of libpolkit-backend-1-0- gets pulled in upon upgrade.
> This can lead to a temporary loss of desktop session related
> functionality, namely the ability to user-mount removable drives or
> to shutdown/restart the system using the GUI controls provided by the
> respective desktop environment. The issue was ultimately caused by
> the recent addition of elogind to the repositories, or rather the
> repackaging of policykit-1 that followed suit.
> 
> Resolution
> --
> 1. Make sure you have at least one of (traditional) consolekit
 # apt-cache policy consolekit
consolekit:
  Installed: 0.4.6-6
  Candidate: 0.4.6-6
  Version table:
 *** 0.4.6-6 500
500 http://pkgmaster.devuan.org/merged ascii/main amd64 Packages
100 /var/lib/dpkg/status
>or
> (new) elogind
# apt-cache policy elogind
elogind:
  Installed: (none)
  Candidate: 234.4-1+devuan1.5
  Version table:
 234.4-1+devuan1.5 500
500 http://pkgmaster.devuan.org/merged ascii/main amd64 Packages
>installed. 
> 3. Ensure the following packages got installed:
>  policykit-1  0.105-18+devuan2.4
>  libpolkit-agent-1-0  0.105-18+devuan2.4
> 
# apt-cache policy policykit-1
policykit-1:
  Installed: 0.105-9+devuan1
  Candidate: 0.105-18+devuan2.4
  Version table:
 0.105-18+devuan2.4 500
500 http://pkgmaster.devuan.org/merged ascii/main amd64 Packages
 *** 0.105-9+devuan1 100
100 /var/lib/dpkg/status

# apt-cache policy libpolkit-agent-1-0
libpolkit-agent-1-0:
  Installed: 0.105-9+devuan1
  Candidate: 0.105-18+devuan2.4
  Version table:
 0.105-18+devuan2.4 500
500 http://pkgmaster.devuan.org/merged ascii/main amd64 Packages
 *** 0.105-9+devuan1 100
100 /var/lib/dpkg/status

# apt-get -s upgrade policykit-1 libpolkit-agent-1-0
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages will be REMOVED:
  libpolkit-backend-1-0 libpolkit-gobject-1-0
The following NEW packages will be installed:
  elogind libelogind0 libpam-elogind libpolkit-backend-1-0-systemd
  libpolkit-gobject-1-0-systemd
The following packages have been kept back:
  boinc-client desktop-base libboinc7
The following packages will be upgraded:
  libpolkit-agent-1-0 policykit-1
2 upgraded, 5 newly installed, 2 to remove and 3 not upgraded.

> 4. Install one of the mutually exclusive policykit backend libs, i.e.
>- EITHER -
>  libpolkit-backend-1-0-elogind  0.105-18+devuan2.4  and
>  libpolkit-gobject-1-0-elogind  0.105-18+devuan2.4
> 
>- OR -apt-get 
>  libpolkit-backend-1-0-consolekit   0.105-18+devuan2.4  and
>  libpolkit-gobject-1-0-consolekit   0.105-18+devuan2.4
> 
>depending on which session manager backend you intend to use, see
> 1.
# apt-get -s install libpolkit-backend-1-0-consolekit
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  elogind libelogind0 libpam-elogind libpolkit-gobject-1-0-systemd
The following packages will be REMOVED:
  libpolkit-backend-1-0 libpolkit-gobject-1-0
The following NEW packages will be installed:
  elogind libelogind0 libpam-elogind libpolkit-backend-1-0-consolekit
  libpolkit-gobject-1-0-systemd
0 upgraded, 5 newly installed, 2 to remove and 5 not upgraded.

# apt-get -s install libpolkit-gobject-1-0-consolekit
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer
required: colord-data libcolord2 libcolorhug2 libgusb2
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  libpolkit-agent-1-0
The following packages will be REMOVED:
  colord libpolkit-backend-1-0 libpolkit-gobject-1-0 policykit-1
The following NEW packages will be installed:
  libpolkit-gobject-1-0-consolekit
The following packages will be upgraded:
  libpolkit-agent-1-0
1 upgraded, 1 newly installed, 4 to remove and 3 not upgraded.
> 
>In case you find you have a backend with -systemd in the name
> installed: that one will _not_ work, and is most likely the cause why
> things went sideways in the first place.

> 
I do not know anything like enough to do anything more than comment, but
does the above indicate that the *-backend-systemd is being pulled in
as a result of an unhelpful dependency chain.  And why does the
installation of libpolkit-backend-1-0-consolekit pull in 
elogind libelogind0 libpam-elogind libpolkit-gobject-1-0-systemd
when consolekit has been installed in preference to elogind?

My sources are these

#
deb http://linux-libre.fsfla.org/pub/linux-libre/freesh freesh main
#deb http://pkgmaster.devuan.org/devuan experimental   main
deb 

Re: [DNG] IMPORTANT! How to fix degraded session management after Devuan ASCII upgrade.

[Irrwahn]

Didier Kryn wrote on 14.02.2018 15:06:
> Le 14/02/2018 à 13:37, Irrwahn a écrit :
[...]
>> 1. Make sure you have at least one of (traditional) consolekit or (new)
>> elogind installed. (Note: You can have both installed and active; which
>> one is actually used however is decided by which libpolkit-backend you
>> choose to install, see 4.)
>      I had both elogind and consolekit.
> 
>      Removing consolekit forces removal of task-xfce-desktop and few 
> other packages including slim.

Removing consolekit isn't mandatory, but yes, in doing so one causes 
same breakage just as you described.

[...]
>> Note:  Depending on what login manager you use in conjunction with which
>> desktop environment you might have to experiment a bit to find out which
>> of consolekit or elogind works best for you (or works[TM] at all).
> 
>      Note that task-xfce-desktop requires slim and slim requires consolekit.

Correct. That however is not an accident, but more or less on purpose.

> 
>      I already had lightdm installed, but slim was the onein function. 
> Tried dpkg-reconfigure lightdm, expecting to select the DM in function, 
> but there was no dialog. After reboot, the lightdm greeting popped up. 
> Xfce pannel's buttons for exit/reboot/shutdown now work properly.

Side note: It is absolutely possible to have the consolekit/slim/xfce 
combo working. Incidentally, that is exactly the setup that gets 
installed when you go all with the defaults during a fresh ASCII BETA 
installer run.

>      Mmc devices can now be mounted from the icon on xfce desktop - 
> permission was denied before.
> 
>      Good job!

Glad that did help, you're welcome. :)

>      If elogind is to be Devuan's default, then, for consistency, 
> another DM than slim should be the default, and task-xfce-desktop should 
> be modified acordingly.

(See side note above.)

AIUI there has not even been any decision *if* there even will be a single
default in this respect, at the very least for ASCII. Different flavors 
of desktop environments work more or less well with different combinations 
of session management and login manager, and consequently the various 
task-...-desktop meta-packages each come with their distinct preferred 
(but not necessarily mandatory) set of default dependencies. But mostly (at 
least going by my own experience during a few dozen test installations I did 
in the last days) it's a matter of taste and personal preference. That's the 
up- and the downside in providing freedom of choice, in a nutshell. :)

Best regards
Urban

-- 
Sapere aude!
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] IMPORTANT! How to fix degraded session management after Devuan ASCII upgrade.

[J. Fahrner]

Am 2018-02-14 15:06, schrieb Didier Kryn:

    If elogind is to be Devuan's default, then, for consistency,
another DM than slim should be the default, and task-xfce-desktop
should be modified acordingly.


There is no default, you can use what you want (consolekit/elogind).
Since lightdm does not have a Devuan theme I use slim which has a nice 
theme.
And since slim only works with consolekit, I installed the consolekit 
backend and removed elogind* completely.


As I understand, elogind is systemd-logind repackaged as standalone 
daemon. And since I don't like poettering-ware, I decided to stay with 
consolekit. ;-)


Jochen
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] IMPORTANT! How to fix degraded session management after Devuan ASCII upgrade.

[Didier Kryn]

Le 14/02/2018 à 13:37, Irrwahn a écrit :

PLEASE NOTE:
   The following only applies to already existing ASCII systems that got
upgraded to the newest package versions as present in the repositories.
Fresh installations of Devuan ASCII 2.0.0 Beta should not be affected.

TL;DR
-
Make sure you got the correct libpolkit-backend installed!

Background
--
   It would appear that under certain circumstances an unsuitable flavor
of libpolkit-backend-1-0- gets pulled in upon upgrade. This can lead
to a temporary loss of desktop session related functionality, namely the
ability to user-mount removable drives or to shutdown/restart the system
using the GUI controls provided by the respective desktop environment. The
issue was ultimately caused by the recent addition of elogind to the
repositories, or rather the repackaging of policykit-1 that followed suit.

Resolution
--
1. Make sure you have at least one of (traditional) consolekit or (new)
elogind installed. (Note: You can have both installed and active; which
one is actually used however is decided by which libpolkit-backend you
choose to install, see 4.)

    I had both elogind and consolekit.

    Removing consolekit forces removal of task-xfce-desktop and few 
other packages including slim.

2. Make sure (at least one of) the above is activated. You may do so by
interactively running the 'pam-auth-update' command as root.

3. Ensure the following packages got installed:
  policykit-1  0.105-18+devuan2.4
  libpolkit-agent-1-0  0.105-18+devuan2.4
  
4. Install one of the mutually exclusive policykit backend libs, i.e.

- EITHER -
  libpolkit-backend-1-0-elogind  0.105-18+devuan2.4  and
  libpolkit-gobject-1-0-elogind  0.105-18+devuan2.4


    Amazingly, I had libpolkit-backend-1.0-systemd installed! See your 
explanation below...



- OR -
  libpolkit-backend-1-0-consolekit   0.105-18+devuan2.4  and
  libpolkit-gobject-1-0-consolekit   0.105-18+devuan2.4

depending on which session manager backend you intend to use, see 1.

In case you find you have a backend with -systemd in the name installed:
that one will _not_ work, and is most likely the cause why things went
sideways in the first place.

5. After making changes to the session management you should either reboot
the system or at least cycle through runlevel 1.

Note:  Depending on what login manager you use in conjunction with which
desktop environment you might have to experiment a bit to find out which
of consolekit or elogind works best for you (or works[TM] at all).


    Note that task-xfce-desktop requires slim and slim requires consolekit.

    I already had lightdm installed, but slim was the onein function. 
Tried dpkg-reconfigure lightdm, expecting to select the DM in function, 
but there was no dialog. After reboot, the lightdm greeting popped up. 
Xfce pannel's buttons for exit/reboot/shutdown now work properly.


    Mmc devices can now be mounted from the icon on xfce desktop - 
permission was denied before.


    Good job!

    If elogind is to be Devuan's default, then, for consistency, 
another DM than slim should be the default, and task-xfce-desktop should 
be modified acordingly.


            Didier


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] IMPORTANT! How to fix degraded session management after Devuan ASCII upgrade.

[Irrwahn]

PLEASE NOTE: 
  The following only applies to already existing ASCII systems that got 
upgraded to the newest package versions as present in the repositories. 
Fresh installations of Devuan ASCII 2.0.0 Beta should not be affected.

TL;DR
-
Make sure you got the correct libpolkit-backend installed!

Background
--  
  It would appear that under certain circumstances an unsuitable flavor 
of libpolkit-backend-1-0- gets pulled in upon upgrade. This can lead 
to a temporary loss of desktop session related functionality, namely the 
ability to user-mount removable drives or to shutdown/restart the system 
using the GUI controls provided by the respective desktop environment. The 
issue was ultimately caused by the recent addition of elogind to the 
repositories, or rather the repackaging of policykit-1 that followed suit.

Resolution
--
1. Make sure you have at least one of (traditional) consolekit or (new)
   elogind installed. (Note: You can have both installed and active; which 
   one is actually used however is decided by which libpolkit-backend you 
   choose to install, see 4.)

2. Make sure (at least one of) the above is activated. You may do so by
   interactively running the 'pam-auth-update' command as root.

3. Ensure the following packages got installed:
 policykit-1  0.105-18+devuan2.4
 libpolkit-agent-1-0  0.105-18+devuan2.4
 
4. Install one of the mutually exclusive policykit backend libs, i.e.
   - EITHER -
 libpolkit-backend-1-0-elogind  0.105-18+devuan2.4  and
 libpolkit-gobject-1-0-elogind  0.105-18+devuan2.4

   - OR -
 libpolkit-backend-1-0-consolekit   0.105-18+devuan2.4  and
 libpolkit-gobject-1-0-consolekit   0.105-18+devuan2.4

   depending on which session manager backend you intend to use, see 1.

   In case you find you have a backend with -systemd in the name installed:
   that one will _not_ work, and is most likely the cause why things went 
   sideways in the first place.

5. After making changes to the session management you should either reboot 
   the system or at least cycle through runlevel 1.

Note:  Depending on what login manager you use in conjunction with which 
desktop environment you might have to experiment a bit to find out which 
of consolekit or elogind works best for you (or works[TM] at all).


Bottom line: As always in life, keep your backends covered. ;-)

HTH, HANVD, and enjoy the ASCII Beta!

Best regards
Urban

-- 
Sapere aude!
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng