Laptop running F34 with an "Intel Cannon Point-LP CNVi [Wireless-AC]"
controller.
Every 10 seconds I get this error message (/var/log/messages):
wpa_supplicant[78893]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-22
A websearch shows this is not an uncommon problem though most
see it every 1 second,
On 01/07/2021 05:56, Patrick O'Callaghan wrote:
Apologies for the noise and thanks to all who attempted to help.
Oh, that's OK.
Got me to start experimenting with writing user units and learning a bit about
how they work.
So, some good came of the noise. From my perspective anyway. :-)
On Wed, 2021-06-30 at 22:24 +0100, Patrick O'Callaghan wrote:
> That's actually a different service. Insync has a GUI-based app called
> 'insync' for workstations and a separate app called 'insync-headless'
> intended for servers. The two are essentially independent of each other
> and have
On Wed, 2021-06-30 at 10:16 -0400, Jonathan Billings wrote:
> On Wed, Jun 30, 2021 at 03:01:56PM +0100, Patrick O'Callaghan wrote:
> > Well I did that, but things are no better. The service still
> > doesn't
> > restart after logging out and in again. In fact it's actually worse
> > now
> > as it
On 01/07/2021 02:14, Joe Zeff wrote:
On 6/30/21 11:52 AM, Patrick O'Callaghan wrote:
Sure. On F33 I did have KillUserProcesses=yes set, but I neglected to
make that change on F34. It might make a difference.
If those settings are kept in your home directory, they should survive a clean
On Sun, 2021-06-27 at 15:37 -0500, Anil F Duggirala wrote:
> I am looking at output from dmesg on my laptop and there appears to be a
> time when a process takes longer than what might be expected and I think
> this may be reducing my startup speed.
I neglected to put the system configuration
On Sun, 2021-06-27 at 15:37 -0500, Anil F Duggirala wrote:
> I am looking at output from dmesg on my laptop and there appears to be a
> time when a process takes longer than what might be expected and I think
> this may be reducing my startup speed.
I have a similar problem, which seems to be
On 6/30/21 11:52 AM, Patrick O'Callaghan wrote:
Sure. On F33 I did have KillUserProcesses=yes set, but I neglected to
make that change on F34. It might make a difference.
If those settings are kept in your home directory, they should survive a
clean install as long as you keep your home
On 6/30/21 11:26 AM, Tim via users wrote:
The CTRL C abort sequence is more to do with aborting the running of
scripts, and the like. I'm not sure that more, less, vi, and other
such things, should be expected to abort with a CTRL C command.
I don't know about vi, as I never use it, but nano
On Wed, 2021-06-30 at 22:35 +0800, Ed Greshko wrote:
> On 30/06/2021 21:55, Patrick O'Callaghan wrote:
> > On Wed, 2021-06-30 at 21:45 +0800, Ed Greshko wrote:
> > > On 30/06/2021 21:39, Patrick O'Callaghan wrote:
> > > > On Wed, 2021-06-30 at 19:37 +0800, Ed Greshko wrote:
> > > > > On 30/06/2021
On Wed, 2021-06-30 at 12:06 -0400, Tom Horsley wrote:
> Looks like something "more" is doing.
Plenty of other things will ignore CTRL C, such as reading man pages.
The CTRL C abort sequence is more to do with aborting the running of
scripts, and the like. I'm not sure that more, less, vi, and
>
> On Wed, Jun 30, 2021, at 9:06 AM, Tom Horsley wrote:
> > On Wed, 30 Jun 2021 17:56:24 +0200
> > Patrick Dupre wrote:
> >
> > > For example
> > > ls -lt |more
> >
> > Looks like something "more" is doing. Try this:
> >
> > sleep 500
> > ^C
>
> I am on F33 (so not an F34 issue) with Xfce4 and I
> To: users@lists.fedoraproject.org
> Subject: Re: ctl C/ctl X
>
> On Wed, 30 Jun 2021 17:56:24 +0200
> Patrick Dupre wrote:
>
> > For example
> > ls -lt |more
>
> Looks like something "more" is doing. Try this:
>
> sleep 500
> ^C
> ___
OK, I can quite
On Wed, Jun 30, 2021, at 9:06 AM, Tom Horsley wrote:
> On Wed, 30 Jun 2021 17:56:24 +0200
> Patrick Dupre wrote:
>
> > For example
> > ls -lt |more
>
> Looks like something "more" is doing. Try this:
>
> sleep 500
> ^C
I am on F33 (so not an F34 issue) with Xfce4 and I see the same as Patrick
On Wed, 30 Jun 2021 17:56:24 +0200
Patrick Dupre wrote:
> For example
> ls -lt |more
Looks like something "more" is doing. Try this:
sleep 500
^C
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = ;
eol2 = ; swtch = ; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R;
werase = ^W; lnext = ^V; discard = ^O; min = 1; time = 0;
-parenb -parodd -cmspar cs8 -hupcl -cstopb cread -clocal -crtscts
-ignbrk -brkint -ignpar -parmrk -inpck -istrip
On Wed, Jun 30, 2021 at 05:23:54PM +0200, Patrick Dupre wrote:
> Before fc34 (i.e. in fc32), I used to used ctlC to interrupt any sort of
> process. In fc34, to have the same result, I need to do
> ctlC ctlX
> How can I avoid to have to make this double command?
Not sure how this happened,
Hello,
Before fc34 (i.e. in fc32), I used to used ctlC to interrupt any sort of
process. In fc34, to have the same result, I need to do
ctlC ctlX
How can I avoid to have to make this double command?
Thanks
===
Patrick
On 30/06/2021 21:55, Patrick O'Callaghan wrote:
On Wed, 2021-06-30 at 21:45 +0800, Ed Greshko wrote:
On 30/06/2021 21:39, Patrick O'Callaghan wrote:
On Wed, 2021-06-30 at 19:37 +0800, Ed Greshko wrote:
On 30/06/2021 18:41, Patrick O'Callaghan wrote:
After re-reading systemd.service(1) I
On Wed, Jun 30, 2021 at 03:01:56PM +0100, Patrick O'Callaghan wrote:
> Well I did that, but things are no better. The service still doesn't
> restart after logging out and in again. In fact it's actually worse now
> as it apparently doesn't start even the first time. I even did a clean
> boot to
On Wed, 2021-06-30 at 19:41 +0800, Ed Greshko wrote:
> > But of course there's always something else. After logging out, the
> > service is killed, which is fine, but it doesn't start again with a
> > new
> > login. I assumed that user units would do this automatically, but it
> > seems they
On Wed, 2021-06-30 at 21:45 +0800, Ed Greshko wrote:
> On 30/06/2021 21:39, Patrick O'Callaghan wrote:
> > On Wed, 2021-06-30 at 19:37 +0800, Ed Greshko wrote:
> > > On 30/06/2021 18:41, Patrick O'Callaghan wrote:
> > > > After re-reading systemd.service(1) I added the line:
> > > >
> > > >
On Wed, Jun 30, 2021 at 02:40:27PM +0100, Patrick O'Callaghan wrote:
> > >
> > > After=plasma-core.target in the [Unit] section and
> > > WantedBy=plasma-core.target in the [Install] section
> > >
> > > I don't know if there is a general way to do it for all desktops.
> >
> Right. I was looking
On 30/06/2021 21:41, Patrick O'Callaghan wrote:
On Wed, 2021-06-30 at 09:14 -0400, Jonathan Billings wrote:
On Wed, Jun 30, 2021 at 07:57:37PM +0800, Ed Greshko wrote:
I put my service file in ~/.config/systemd/user. Then I have to
disable/enable the service for the change to
take effect.
On 30/06/2021 21:39, Patrick O'Callaghan wrote:
On Wed, 2021-06-30 at 19:37 +0800, Ed Greshko wrote:
On 30/06/2021 18:41, Patrick O'Callaghan wrote:
After re-reading systemd.service(1) I added the line:
Type=forking
to the service file, and now the script is not being terminated,
which
is
On Wed, 2021-06-30 at 09:14 -0400, Jonathan Billings wrote:
> On Wed, Jun 30, 2021 at 07:57:37PM +0800, Ed Greshko wrote:
>
> > I put my service file in ~/.config/systemd/user. Then I have to
> > disable/enable the service for the change to
> > take effect. Then I see
> >
> >
On Wed, 2021-06-30 at 19:57 +0800, Ed Greshko wrote:
> On 30/06/2021 19:41, Ed Greshko wrote:
> >
> > Maybe ignore my previous question.
> >
> > I've been playing with this as well. I found that with KDE I could
> > get a service file to start at login by using
> >
> >
On Wed, 2021-06-30 at 19:37 +0800, Ed Greshko wrote:
> On 30/06/2021 18:41, Patrick O'Callaghan wrote:
> > After re-reading systemd.service(1) I added the line:
> >
> > Type=forking
> >
> > to the service file, and now the script is not being terminated,
> > which
> > is what I wanted.
> >
> >
On Wed, Jun 30, 2021 at 07:57:37PM +0800, Ed Greshko wrote:
> I put my service file in ~/.config/systemd/user. Then I have to
> disable/enable the service for the change to
> take effect. Then I see
>
> [egreshko@f34k2 ~]$ ll .config/systemd/user/
> total 4
> -rw-r--r--. 1 egreshko
On 30/06/2021 19:41, Ed Greshko wrote:
Maybe ignore my previous question.
I've been playing with this as well. I found that with KDE I could get a
service file to start at login by using
After=plasma-core.target in the [Unit] section and
WantedBy=plasma-core.target in the [Install] section
On 30/06/2021 19:35, Patrick O'Callaghan wrote:
On Wed, 2021-06-30 at 11:41 +0100, Patrick O'Callaghan wrote:
On Tue, 2021-06-29 at 19:37 +0100, Patrick O'Callaghan wrote:
On Tue, 2021-06-29 at 21:28 +0800, Qiyu Yan wrote:
在 2021-06-29星期二的 12:42 +0100，Patrick O'Callaghan写道：
I'm trying to get
On 30/06/2021 18:41, Patrick O'Callaghan wrote:
After re-reading systemd.service(1) I added the line:
Type=forking
to the service file, and now the script is not being terminated, which
is what I wanted.
IOW, this seems to be the solution, or at least*a* solution. There may
be an alternate
On Wed, 2021-06-30 at 11:41 +0100, Patrick O'Callaghan wrote:
> On Tue, 2021-06-29 at 19:37 +0100, Patrick O'Callaghan wrote:
> > On Tue, 2021-06-29 at 21:28 +0800, Qiyu Yan wrote:
> > > 在 2021-06-29星期二的 12:42 +0100，Patrick O'Callaghan写道：
> > > > I'm trying to get a specific service to start on
On Tue, 2021-06-29 at 19:37 +0100, Patrick O'Callaghan wrote:
> On Tue, 2021-06-29 at 21:28 +0800, Qiyu Yan wrote:
> > 在 2021-06-29星期二的 12:42 +0100，Patrick O'Callaghan写道：
> > > I'm trying to get a specific service to start on login, and the
> > > usual
> > > method (KDE Autostart) isn't working so
On 30/06/2021 16:19, Patrick O'Callaghan wrote:
On Wed, 2021-06-30 at 08:10 +0800, Ed Greshko wrote:
On 30/06/2021 05:22, Patrick O'Callaghan wrote:
On Tue, 2021-06-29 at 13:00 -0600, Joe Zeff wrote:
On 6/29/21 12:37 PM, Patrick O'Callaghan wrote:
This is the entire script:
$ ls -l
On Wed, 2021-06-30 at 08:10 +0800, Ed Greshko wrote:
> On 30/06/2021 05:22, Patrick O'Callaghan wrote:
> > On Tue, 2021-06-29 at 13:00 -0600, Joe Zeff wrote:
> > > On 6/29/21 12:37 PM, Patrick O'Callaghan wrote:
> > > > This is the entire script:
> > > >
> > > > $ ls -l bin/start-insync
> > > >
36 matches
Mail list logo
