Re: slock stops working after update

2016-12-02 Thread Ranjan Maitra
> >> On 12/03/16 07:34, Ranjan Maitra wrote: > >>> Running F25 here, I get the following, after this morning's update for > >>> slock: > >>> > >>> > >>> $ slock > >>> slock: getgrnam nogroup: group entry not found > >>> > >>> How does one get around this? > >> Use "groupadd" to add the group call

Re: slock stops working after update

2016-12-02 Thread Ed Greshko
On 12/03/16 08:57, Ranjan Maitra wrote: > On Sat, 3 Dec 2016 08:01:27 +0800 Ed Greshko wrote: > >> >> On 12/03/16 07:34, Ranjan Maitra wrote: >>> Running F25 here, I get the following, after this morning's update for >>> slock: >>> >>> >>> $ slock >>> slock: getgrnam nogroup: group entry not f

Re: slock stops working after update

2016-12-02 Thread Ranjan Maitra
On Sat, 3 Dec 2016 08:01:27 +0800 Ed Greshko wrote: > > > On 12/03/16 07:34, Ranjan Maitra wrote: > > Running F25 here, I get the following, after this morning's update for > > slock: > > > > > > $ slock > > slock: getgrnam nogroup: group entry not found > > > > How does one get around this?

Re: slock stops working after update

2016-12-02 Thread Ed Greshko
On 12/03/16 07:34, Ranjan Maitra wrote: > Running F25 here, I get the following, after this morning's update for slock: > > > $ slock > slock: getgrnam nogroup: group entry not found > > How does one get around this? Use "groupadd" to add the group called "nogroup" and then add yourself to that

slock stops working after update

2016-12-02 Thread Ranjan Maitra
Hi, Running F25 here, I get the following, after this morning's update for slock: $ slock slock: getgrnam nogroup: group entry not found How does one get around this? Thanks, Ranjan -- Important Notice: This mailbox is ignored: e-mails are set to be deleted on receipt. Please respond to th