> On 08/15/2017 10:22 PM, wgelpi(a)redhat.com wrote:
>
>
> Those packages seem to be available only from the TLP repo and according to
> http://linrunner.de/en/tlp/docs/tlp-linux-advanced-power-management.html
> (scroll down
> to Fedora) only available for F24 and F25.
Yea. I was hoping they wo
I have been trying to run sudo dnf update -y[1] for a few days now and it
always seems to fail. I'm really not sure why this is happening as I have
"never" had this problem before. Going to keep looking for a solution but
thought I would ask this group as well. Thanks in advance!
[1]
[wgelpi
On 08/31/2017 09:35 PM, wge...@redhat.com wrote:
> I have been trying to run sudo dnf update -y[1] for a few days now and it
> always seems to fail. I'm really not sure why this is happening as I have
> "never" had this problem before. Going to keep looking for a solution but
> thought I would
Hi,
When I open vim in konsole, it shows $q q at startup. If I insert
text, $q q is replaced by the text I typed.
gvim has no issue.
vim in terminator is fine.
Frédéric
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email
When I resize a window by clicking in a corner, the windows goes in
the background during dragging and remains there after dragging, this
is very strange!
This does not depend on the "windows behaviour" settings although I
normally use "focus follow mouse" (I get the same behaviour with
"click to
> When I resize a window by clicking in a corner, the windows goes in
> the background during dragging and remains there after dragging, this
> is very strange!
>
> This does not depend on the "windows behaviour" settings although I
> normally use "focus follow mouse" (I get the same behaviour with
People,
I just bought this camera but on my F25 x86_64 XFCE workstation,
plugging the camera into a USB port does not register a device - from
Googling it appears that I might have to use gvfs to get a usable
connection? Has anyone got this working with a setup like mine?
Thanks,
Phil.
--
On Thu, 2017-08-31 at 16:43 +0200, Frédéric Bron wrote:
> Hi,
>
> When I open vim in konsole, it shows $q q at startup. If I insert
> text, $q q is replaced by the text I typed.
> gvim has no issue.
> vim in terminator is fine.
>
This has already been reported at https://github.com/vim/vim/issues/2
What version you are using?
mine are worked fine
$ vim -version
VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Aug 22 2017 12:33:17)
Plus, I found some people posted[1] about $q appearance on vim first line
when loaded a few days ago.
If you don't mind, what is your "$ env | grep TERM" output ?
[
On Thu, 2017-08-31 at 16:59 +0200, Frédéric Bron wrote:
> > When I resize a window by clicking in a corner, the windows goes in
> > the background during dragging and remains there after dragging, this
> > is very strange!
> >
> > This does not depend on the "windows behaviour" settings although I
On 08/30/17 15:16, Tony Nelson wrote:
> I have an old CentOS5 that I chroot into. On my old f20 box, PATH
> included /bin, but now on f26 it does not. I don't understand how
For a while now, /bin should be a link to /usr/bin. is /usr/bin in the
PATH?
> this could happen; I would think that PAT
> I have no such problem. The window resizes as expected.
>
> Nope. Clicking on the title bar does nothing. However, in the 'System
> settings-
>> Window behaviour->Titlebar Actions' the titlebar double-click option is set
> to 'Nothing' :-)
Tried with "nothing", same issue.
I checked that title
> What version you are using?
> mine are worked fine
>
> $ vim -version
> VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Aug 22 2017 12:33:17)
Same:
$ vim --version
VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Aug 22 2017 12:33:17)
> If you don't mind, what is your "$ env | grep TERM" output ?
xt
> This has already been reported at https://github.com/vim/vim/issues/2008
Thanks!
> I use KDE, so added 'set term=konsole-256color' to my .vimrc file.
I see that I have in my .vimrc the following:
if ($TERM!="")
:set invttybuiltin term=$TERM
endif
So I tried setting TERM to konsole-256color
On Wed, Aug 30, 2017 at 3:16 PM, Tony Nelson
wrote:
>
> I have an old CentOS5 that I chroot into. On my old f20 box, PATH
> included /bin, but now on f26 it does not. I don't understand how
> this could happen; I would think that PATH is set inside the chroot
> by the shell. How does PATH get set?
On Thu, Aug 31, 2017 at 11:34 AM, Kevin Cummings
wrote:
> On 08/30/17 15:16, Tony Nelson wrote:
>>
>> I have an old CentOS5 that I chroot into. On my old f20 box, PATH
>> included /bin, but now on f26 it does not. I don't understand how
>
> For a while now, /bin should be a link to /usr/bin. is /u
On 08/31/2017 08:34 AM, Kevin Cummings wrote:
> On 08/30/17 15:16, Tony Nelson wrote:
>> I have an old CentOS5 that I chroot into. On my old f20 box, PATH
>> included /bin, but now on f26 it does not. I don't understand how
>
> For a while now, /bin should be a link to /usr/bin. is /usr/bin in
On 08/31/2017 09:26 AM, Rick Stevens wrote:
On 08/31/2017 08:34 AM, Kevin Cummings wrote:
On 08/30/17 15:16, Tony Nelson wrote:
I have an old CentOS5 that I chroot into. On my old f20 box, PATH
included /bin, but now on f26 it does not. I don't understand how
For a while now, /bin should be
On 08/31/2017 09:41 AM, Mike Wright wrote:
> On 08/31/2017 09:26 AM, Rick Stevens wrote:
>> On 08/31/2017 08:34 AM, Kevin Cummings wrote:
>>> On 08/30/17 15:16, Tony Nelson wrote:
I have an old CentOS5 that I chroot into. On my old f20 box, PATH
included /bin, but now on f26 it does not.
OK it's fixed. I did not see that "left button" was at "place below"!
Thansk,
Frédéric
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
On 17-08-31 12:18:38, Tom H wrote:
On Wed, Aug 30, 2017 at 3:16 PM, Tony Nelson
wrote:
>
> I have an old CentOS5 that I chroot into. On my old f20 box, PATH
> included /bin, but now on f26 it does not. I don't understand how
> this could happen; I would think that PATH is set inside the chroot
>
On 17-08-31 12:41:09, Mike Wright wrote:
How about using "env": env PATH="new_path" chroot /some_dir
Wouldn't this preempt the passed PATH, profile, bashrc, and the dot
files? If so, chroot could be defined as an alias to "env ...
chroot" and thereby eliminate the problem.
Seems to work
On 08/31/2017 11:14 AM, Tony Nelson wrote:
> On 17-08-31 12:41:09, Mike Wright wrote:
>
>> How about using "env": env PATH="new_path" chroot /some_dir
>>
>> Wouldn't this preempt the passed PATH, profile, bashrc, and the dot
>> files? If so, chroot could be defined as an alias to "env ... chroot
>> I use KDE, so added 'set term=konsole-256color' to my .vimrc file.
>
> I see that I have in my .vimrc the following:
> if ($TERM!="")
> :set invttybuiltin term=$TERM
> endif
>
> So I tried setting TERM to konsole-256color and it worked.
In fact I followed this suggestion for setting TERM:
"S
have you looked at wifi connection?
On Thu, Aug 31, 2017 at 8:02 AM, Philip Rhoades wrote:
> People,
>
> I just bought this camera but on my F25 x86_64 XFCE workstation, plugging
> the camera into a USB port does not register a device - from Googling it
> appears that I might have to use gvfs to
On 08/31/2017 01:04 PM, Jack Craig wrote:
> have you looked at wifi connection?
Uhm, does the Hero use MTPFS like some cameras and cell phones? Perhaps
"simple-mtpfs" would help. First:
simple-mtpfs -l
to list the potential devices. Identify the device's ID, then
simple-mtpfs --
On Tue, Aug 29, 2017 at 8:26 AM Ed Greshko wrote:
> On 08/28/2017 05:16 PM, Ed Greshko wrote:
> > On 08/28/2017 03:27 PM, Christopher wrote:
> >> One interesting thing I noticed with this: if I hit "Backspace" a few
> times before
> >> typing the password, it seems to work on the first attempt. F
On 17-08-31 11:34:21, Kevin Cummings wrote:
On 08/30/17 15:16, Tony Nelson wrote:
> I have an old CentOS5 that I chroot into. On my old f20 box, PATH
> included /bin, but now on f26 it does not. I don't understand how
For a while now, /bin should be a link to /usr/bin. is /usr/bin in
the
P
On 17-08-31 14:43:10, Rick Stevens wrote:
On 08/31/2017 11:14 AM, Tony Nelson wrote:
> On 17-08-31 12:41:09, Mike Wright wrote:
>
>> How about using "env": env PATH="new_path" chroot /some_dir
>>
>> Wouldn't this preempt the passed PATH, profile, bashrc, and the dot
>> files? If so, chroot coul
29 matches
Mail list logo
