On Mon, Apr 06, 2020 at 02:23:20PM +0200, Riccardo Mottola wrote:
> Hi Marcus,
>
> Marcus MERIGHI wrote:
> > Hello Riccardo,
> >
> > startx(1) had it's setuid bit removed. I think in the timeframe you are
> > upgrading over. The canonical advice is to use xenodm(1).
> >
> > Marcus
> >
>
>
Hi Marcus,
Marcus MERIGHI wrote:
> Hello Riccardo,
>
> startx(1) had it's setuid bit removed. I think in the timeframe you are
> upgrading over. The canonical advice is to use xenodm(1).
>
> Marcus
>
exactly, that was it... the error message wasn't that helpful.
xenodm works.. but since I
Hello Riccardo,
startx(1) had it's setuid bit removed. I think in the timeframe you are
upgrading over. The canonical advice is to use xenodm(1).
Marcus
riccardo.mott...@libero.it (Riccardo Mottola), 2020.04.06 (Mon) 11:57 (CEST):
> Hi,
>
> lockdown times gave me finally times to update my
Hi,
lockdown times gave me finally times to update my workstation/home
server to 6.6 too, after my successful laptop upgrades.
I was a moment scared when fw_update told me to reboot due to microcode
update :-P But it went fine.
I followed 6.5 -> 6.6 upgrade. All packages are upgraded too
4 matches
Mail list logo