On Fri, 22 Jun 2018 14:22:13 -0700, Rick Stevens wrote:
[]
> And just a warning: The lightdm display manager has issues with
> pam_kwallet and pam_kwallet5 if they're installed. If you decide to use
> lightdm, edit the /etc/pam.d/lightdm file and comment out any lines that
> reference
On 06/22/2018 01:57 PM, Beartooth wrote:
> On Mon, 21 May 2018 05:48:24 +0800, Ed Greshko wrote:
>
>> In actuality you just need one command.
>>
>> systemctl -f enable sddm (or whatever new dm you want)
>>
>> -f = force which means "When used with enable, overwrite any existing
>> conflicting
On Mon, 21 May 2018 05:48:24 +0800, Ed Greshko wrote:
> In actuality you just need one command.
>
> systemctl -f enable sddm (or whatever new dm you want)
>
> -f = force which means "When used with enable, overwrite any existing
> conflicting symlinks."
>
> and no need to use ".service"
On Tue, 22 May 2018 17:35:04 +0100, Patrick O'Callaghan wrote:
[]
> Never mind. I have actually brought it up before now (can't be bothered
> to track down the post though it's probably on the KDE list) but no-one
> else reacted so it doesn't appear to be common.
Fwiw, the pan
On 05/28/2018 11:34 AM, Martín Marqués wrote:
> 2018-05-22 13:56 GMT-03:00 Rick Stevens :
>>
>> And I just had lightdm screw up royally. First, upon login I got an
>> XFCE polkit error popup, which is singularly useless in telling you
>> anything you can troubleshoot with. Then, I had no access to
2018-05-22 13:56 GMT-03:00 Rick Stevens :
>
> And I just had lightdm screw up royally. First, upon login I got an
> XFCE polkit error popup, which is singularly useless in telling you
> anything you can troubleshoot with. Then, I had no access to the sound
> hardware on my machine, nor could I enab
francis.montag...@inria.fr wrote:
>
> On Tue, 22 May 2018 09:56:25 -0700 Rick Stevens wrote:
>
>> And I just had lightdm screw up royally. First, upon login I got an
>> XFCE polkit error popup, which is singularly useless in telling you
>> anything you can troubleshoot with. Then, I had no acces
Hi
On Tue, 22 May 2018 16:07:22 -0700 Rick Stevens wrote:
> On 05/22/2018 03:48 PM, Ed Greshko wrote:
>> On 05/23/18 06:45, Rick Stevens wrote:
>>> On 05/22/2018 03:38 PM, Ed Greshko wrote:
On 05/23/18 04:24, Rick Stevens wrote:
> On 05/22/2018 10:32 AM, francis.montag...@inria.fr wrote:
On 05/22/2018 03:48 PM, Ed Greshko wrote:
> On 05/23/18 06:45, Rick Stevens wrote:
>> On 05/22/2018 03:38 PM, Ed Greshko wrote:
>>> On 05/23/18 04:24, Rick Stevens wrote:
On 05/22/2018 10:32 AM, francis.montag...@inria.fr wrote:
> On Tue, 22 May 2018 09:56:25 -0700 Rick Stevens wrote:
On 05/23/18 06:45, Rick Stevens wrote:
> On 05/22/2018 03:38 PM, Ed Greshko wrote:
>> On 05/23/18 04:24, Rick Stevens wrote:
>>> On 05/22/2018 10:32 AM, francis.montag...@inria.fr wrote:
On Tue, 22 May 2018 09:56:25 -0700 Rick Stevens wrote:
> And I just had lightdm screw up royally.
On 05/22/2018 03:38 PM, Ed Greshko wrote:
> On 05/23/18 04:24, Rick Stevens wrote:
>> On 05/22/2018 10:32 AM, francis.montag...@inria.fr wrote:
>>> On Tue, 22 May 2018 09:56:25 -0700 Rick Stevens wrote:
>>>
And I just had lightdm screw up royally. First, upon login I got an
XFCE polkit er
On 05/23/18 04:24, Rick Stevens wrote:
> On 05/22/2018 10:32 AM, francis.montag...@inria.fr wrote:
>> On Tue, 22 May 2018 09:56:25 -0700 Rick Stevens wrote:
>>
>>> And I just had lightdm screw up royally. First, upon login I got an
>>> XFCE polkit error popup, which is singularly useless in telling
On 05/22/2018 01:24 PM, Rick Stevens wrote:
> On 05/22/2018 10:32 AM, francis.montag...@inria.fr wrote:
>>
>> On Tue, 22 May 2018 09:56:25 -0700 Rick Stevens wrote:
>>
>>> And I just had lightdm screw up royally. First, upon login I got an
>>> XFCE polkit error popup, which is singularly useless in
On 05/22/2018 10:32 AM, francis.montag...@inria.fr wrote:
>
> On Tue, 22 May 2018 09:56:25 -0700 Rick Stevens wrote:
>
>> And I just had lightdm screw up royally. First, upon login I got an
>> XFCE polkit error popup, which is singularly useless in telling you
>> anything you can troubleshoot wit
.
Thought of creating a start up process to automatically do this on login.
On 22 May 2018 at 19:32, francis.montag...@inria.fr wrote:
From: francis.montag...@inria.fr
To: Community support for Fedora users
Subject: Re: Could LightDM be b
On Tue, 22 May 2018 09:56:25 -0700 Rick Stevens wrote:
> And I just had lightdm screw up royally. First, upon login I got an
> XFCE polkit error popup, which is singularly useless in telling you
> anything you can troubleshoot with. Then, I had no access to the sound
> hardware on my machine, nor
On 05/22/2018 09:33 AM, Patrick O'Callaghan wrote:
> On Tue, 2018-05-22 at 23:00 +0800, Ed Greshko wrote:
So, those processes may potentially keep copies of libraries that have
been updated
and (guessing) clashes happen with new processes with new libraries.
>>> Yes, I'm aware of th
On Tue, 2018-05-22 at 23:02 +0800, Ed Greshko wrote:
> On 05/22/18 22:51, Patrick O'Callaghan wrote:
> > On Tue, 2018-05-22 at 06:28 -0500, Rex Dieter wrote:
> > > Ed Greshko wrote:
> > >
> > >
> > > > I was considering asking on the KDE list if there is anyway to tell the
> > > > system to end a
On Tue, 2018-05-22 at 23:00 +0800, Ed Greshko wrote:
> >> So, those processes may potentially keep copies of libraries that have
> >> been updated
> >> and (guessing) clashes happen with new processes with new libraries.
> > Yes, I'm aware of that. However 'tracer' supposed to detect this,
> > eit
On 05/22/18 22:51, Patrick O'Callaghan wrote:
> On Tue, 2018-05-22 at 06:28 -0500, Rex Dieter wrote:
>> Ed Greshko wrote:
>>
>>
>>> I was considering asking on the KDE list if there is anyway to tell the
>>> system to end all users processes after logout.
>> Set in /etc/systemd/logind.conf:
>>
>> K
Allegedly, on or about 22 May 2018, Tom Horsley sent:
> Of course I'll still need my reboot script to umount -l nfs
> filesystems to keep systemd from spending 5 hours timing out trying
> to talk to systems that have gone down :-).
That's why I went with autofs, rather than fstab entries. They're
On 05/22/18 19:12, Patrick O'Callaghan wrote:
> On Tue, 2018-05-22 at 15:16 +0800, Ed Greshko wrote:
>> On 05/21/18 23:09, Patrick O'Callaghan wrote:
>>> On Mon, 2018-05-21 at 10:06 +0930, Tim via users wrote:
There are
programs that just don't terminate every time when I log out. Variou
On Tue, 2018-05-22 at 06:28 -0500, Rex Dieter wrote:
> Ed Greshko wrote:
>
>
> > I was considering asking on the KDE list if there is anyway to tell the
> > system to end all users processes after logout.
>
> Set in /etc/systemd/logind.conf:
>
> KillUserProcesses=yes
I already have that set, a
On Tue, 22 May 2018 20:42:30 +0800
Ed Greshko wrote:
> Well, like any good tech, I just tried it and it did kill all of those. No
> traces of
> the logged-out user remain.
Cool. I'll have to configure my system with that.
Of course I'll still need my reboot script to umount -l nfs filesystems
On 05/22/18 20:26, Tom Horsley wrote:
> On Tue, 22 May 2018 06:28:21 -0500
> Rex Dieter wrote:
>
>> Set in /etc/systemd/logind.conf:
>>
>> KillUserProcesses=yes
> Does that get all the "user mode daemon" stuff that runs under the
> "/usr/lib/systemd/systemd --user" process?
Well, like any good tec
On Tue, 22 May 2018 06:28:21 -0500
Rex Dieter wrote:
> Set in /etc/systemd/logind.conf:
>
> KillUserProcesses=yes
Does that get all the "user mode daemon" stuff that runs under the
"/usr/lib/systemd/systemd --user" process?
Those hanging around forever always seemed to make a reboot take
foreve
On 05/22/18 19:28, Rex Dieter wrote:
> Ed Greshko wrote:
>
>
>> I was considering asking on the KDE list if there is anyway to tell the
>> system to end all users processes after logout.
> Set in /etc/systemd/logind.conf:
>
> KillUserProcesses=yes
>
Thanks
--
Conjecture is just a conclusion
Ed Greshko wrote:
> I was considering asking on the KDE list if there is anyway to tell the
> system to end all users processes after logout.
Set in /etc/systemd/logind.conf:
KillUserProcesses=yes
-- Rex
___
users mailing list -- users@lists.fedorapr
On Tue, 2018-05-22 at 15:16 +0800, Ed Greshko wrote:
> On 05/21/18 23:09, Patrick O'Callaghan wrote:
> > On Mon, 2018-05-21 at 10:06 +0930, Tim via users wrote:
> > > There are
> > > programs that just don't terminate every time when I log out. Various
> > > system/desktop daemons, sometimes web b
On Tue, 2018-05-22 at 07:22 +0930, Tim via users wrote:
> Tim:
> > > There are programs that just don't terminate every time when I log
> > > out. Various system/desktop daemons, sometimes web browsers.
>
> Patrick O'Callaghan:
> > Possibly unrelated, but I sometimes - not always - find that after
Allegedly, on or about 22 May 2018, Ed Greshko sent:
> FWIW, if you investigate a little I think you'd find that for every
> user that logs-in for a GUI session there will be about 9+ processes
> that are left running and remain running. It seems these processes
> are then reused on subsequent log
On 05/21/18 23:09, Patrick O'Callaghan wrote:
> On Mon, 2018-05-21 at 10:06 +0930, Tim via users wrote:
>> There are
>> programs that just don't terminate every time when I log out. Various
>> system/desktop daemons, sometimes web browsers.
> Possibly unrelated, but I sometimes - not always - find
Tim:
>> There are programs that just don't terminate every time when I log
>> out. Various system/desktop daemons, sometimes web browsers.
Patrick O'Callaghan:
> Possibly unrelated, but I sometimes - not always - find that after
> updating (using dnf with the tracer plugin) I'm advised to restart
On Mon, 2018-05-21 at 16:09 +0100, Patrick O'Callaghan wrote:
> On Mon, 2018-05-21 at 10:06 +0930, Tim via users wrote:
> > There are
> > programs that just don't terminate every time when I log out. Various
> > system/desktop daemons, sometimes web browsers.
>
> Possibly unrelated, but I sometim
On Mon, 2018-05-21 at 10:06 +0930, Tim via users wrote:
> There are
> programs that just don't terminate every time when I log out. Various
> system/desktop daemons, sometimes web browsers.
Possibly unrelated, but I sometimes - not always - find that after
updating (using dnf with the tracer plug
Allegedly, on or about 20 May 2018, Beartooth sent:
>
> Under F27, they kept filling up with some sort of cruft, to the
> point of refusing dnf upgrade; but when I found any of the cruft, it
> was in places where I dared not lay about me with a cyber-battleaxe.
> I jumped to F28 the day of r
On 05/21/18 04:02, Tom Horsley wrote:
> Pretty simple really. Just do something like:
>
> systemctl disable gdm.service
> systemctl enable kdm.service
In actuality you just need one command.
systemctl -f enable sddm (or whatever new dm you want)
-f = force which means "When used with enable
On Sun, 20 May 2018 22:33:59 +0100
Patrick O'Callaghan wrote:
> IIRC KDM is deprecated, so SDDM (now the default for KDE/Plasma) would
> probably be better.
No doubt so they could prevent me from changing any X server
options :-). That's why I switched to kdm in the first place:
https://bugzilla
On Sun, 2018-05-20 at 16:02 -0400, Tom Horsley wrote:
> On Sun, 20 May 2018 12:46:22 -0700
> stan wrote:
>
> > switch desktop managers.
> > I ignored it since it didn't apply to me.
>
> Pretty simple really. Just do something like:
>
> systemctl disable gdm.service
> systemctl enable kdm.service
On Sun, 20 May 2018 12:46:22 -0700
stan wrote:
> switch desktop managers.
> I ignored it since it didn't apply to me.
Pretty simple really. Just do something like:
systemctl disable gdm.service
systemctl enable kdm.service
If you don't have the one you want installed, you
can do something like:
On Sun, 20 May 2018 13:58:36 -0400
Beartooth wrote:
Forgot this:
> Finally, #1 has two F28 kernels -- which do no better than on
> #2 nor #3 -- and a rescue kernel from F26. Sic. Twenty-six, not 27
> nor 28. But that rescue kernel does support almost my whole GUI (I
> miss Pan badly.), and
On Sun, 20 May 2018 13:58:36 -0400
Beartooth wrote:
> I'd like to try replacing LDM with something else; how do I
> do that?? (I like Mate well, and would prefer not to swap it out,too)
I use openbox (it's in the Fedora repositories) with lxde. I usually
use startx from multiuser, but ope
I use SLiM. I read somewhere that there is no further development and it will
stop working eventually but happily Fedora still packages it so as long as that
holds, I guess I am fine.
https://github.com/iwamatsu/slim
Ranjan
On Sun, 20 May 2018 13:58:36 -0400 Beartooth wrote:
>
> I kee
43 matches
Mail list logo