Allegedly, on or about 15 February 2016, Les Howell sent:
> I have a problem with touchpads in general. My finger tips are
> normally quite dry, so they skip and jump when dragging across the
> pads. I always have to turn double click off, multitouch off, and
> sensitivity down a bit to get them
Allegedly, on or about 15 February 2016, Mike Wright sent:
> I have several large disks filled with experiments and multiboots. I
> need to make changes to the current /boot/grub/grub.cfg but I have no
> idea which one I'm using or which one of the systems' grub config
> tools were used so I don
Tim:
>> It's not a new problem
Tom Horsley:
> Actually it is a new problem. Yum was fine with multiple
> rpms defining the same directory till somewhere around
> fedora 19 or 20, then it suddenly became an error.
I don't think relying on the updating software not caring that you're
trying to own
On 2/15/16, Tim wrote:
> What's more mind-boggling is why those (in Google) who created the
> problem haven't pulled their fingers out and fixed it. It's not a new
> problem, the fault is entirely theirs, and they should know better.
> Don't make the users jump through hoops to fix things that y
Tom Horsley wrote:
On Tue, 16 Feb 2016 05:47:23 +1030 Tim wrote:
It's not a new problem
Actually it is a new problem. Yum was fine with multiple rpms
defining the same directory till somewhere around fedora 19 or 20,
then it suddenly became an error.
I don't think the problem is multiple
On Mon, Feb 15, 2016 at 7:02 PM, SternData
wrote:
> I just got one of these to replace one that was dropping sectors:
>
> http://www.amazon.com/gp/product/B005T3GRN2?psc=1&redirect=true&ref_=oh_aui_detailpage_o01_s00
Yeah, I shopped around a bit and decided to give a referb with 1 year
warranty
On 02/15/2016 04:21 PM, Rick Stevens wrote:
On 02/15/2016 03:42 PM, Mike Wright wrote:
Does the boot process leave any footprints behind telling where it
booted from?
So you can see my boot partition is a plain-old partition on /dev/sda1
and the root filesystem (block device 253:1) is a Linux
On 02/15/2016 04:21 PM, Rick Stevens wrote:
On 02/15/2016 03:42 PM, Mike Wright wrote:
Does the boot process leave any footprints behind telling where it
booted from?
You can always "cat /proc/cmdline" to see what the boot command line
was. In my case:
[root@prophead ~]# cat /proc/cmdli
On 02/15/2016 04:47 PM, Richard Shaw wrote:
> Um I'm not sure what the threshold should be for this drive (2TB)
> but I would think that having over 7000 bad sectors it would not be
> considered OK.
>
> In either case I plan on replacing the drive as soon as funds allow.
>
> Thanks,
> Richard
On 02/15/2016 04:10 PM, doug wrote:
On 02/15/2016 06:42 PM, Mike Wright wrote:
Does the boot process leave any footprints behind telling where it
booted from?
Don't know if you have legacy grub or not. With legacy grub, you can
change the names in menu.lst--put a 1 or 2 or whatever after
the d
On 02/15/2016 03:42 PM, Mike Wright wrote:
Hi everybody,
I have several large disks filled with experiments and multiboots. I
need to make changes to the current /boot/grub/grub.cfg but I have no
idea which one I'm using or which one of the systems' grub config tools
were used so I don't dare j
On 02/15/2016 06:42 PM, Mike Wright wrote:
Hi everybody,
I have several large disks filled with experiments and multiboots. I
need to make changes to the current /boot/grub/grub.cfg but I have no
idea which one I'm using or which one of the systems' grub config
tools were used so I don't da
Hi everybody,
I have several large disks filled with experiments and multiboots. I
need to make changes to the current /boot/grub/grub.cfg but I have no
idea which one I'm using or which one of the systems' grub config tools
were used so I don't dare just grab any old one and use it
I've se
Um I'm not sure what the threshold should be for this drive (2TB) but I
would think that having over 7000 bad sectors it would not be considered OK.
In either case I plan on replacing the drive as soon as funds allow.
Thanks,
Richard
--
users mailing list
users@lists.fedoraproject.org
To uns
On Mon, 2016-02-15 at 22:37 +0200, Mihuleac Sergiu wrote:
Very happy to hear I'm not the only one. Same issue with my
touch-pad -- Lenovo E540
>
> On 02/15/2016 10:33 PM, Go Canes wrote:
> > Thanks for the suggestion - the problem manifests without touching
> > the trackpad (other than the c
Very happy to hear I'm not the only one. Same issue with my touch-pad
-- Lenovo E540
On 02/15/2016 10:33 PM, Go Canes wrote:
> Thanks for the suggestion - the problem manifests without touching the
> trackpad (other than the click to load the web page). I tried
> adjusting sensitivity, switching
Thanks for the suggestion - the problem manifests without touching the
trackpad (other than the click to load the web page). I tried adjusting
sensitivity, switching from libinput to the legacy driver, etc. No change.
On Sun, Feb 14, 2016 at 1:18 PM, Martin Skjöldebrand wrote:
>
>
> On 12/02/1
Thanks for the suggestion - I have not tried google chrome - since the
problem manifested with Konquerer, I am thinking it is unlikely to be a
Firefox issue. But seeing what chrome does may be useful.
On Sat, Feb 13, 2016 at 6:53 AM, Morne Snyman wrote:
> Hi,
>
> Have you tried using google chr
On 02/15/2016 11:44 AM, Tom Horsley wrote:
Actually it is a new problem. Yum was fine with multiple
rpms defining the same directory till somewhere around
fedora 19 or 20, then it suddenly became an error.
I first ran into it when I upgraded from Fedora 19 to 20, suggesting
that it started wit
On Tue, 16 Feb 2016 05:47:23 +1030
Tim wrote:
> It's not a new
> problem
Actually it is a new problem. Yum was fine with multiple
rpms defining the same directory till somewhere around
fedora 19 or 20, then it suddenly became an error.
--
users mailing list
users@lists.fedoraproject.org
To unsub
jd1008:
>> And the fix is so totally simple. Just remove one line from the spec file:
>> %dir %attr(0755, root, root) "/usr/bin"
>> which is line 341
Dave Stevens:
> that's very useful and leaves me totally agog wondering how you found
> it - exhaustive search?? or what??
What's more mind-bogg
Quoting jd1008 :
On 02/15/2016 07:04 AM, Rex Dieter wrote:
jd1008 wrote:
Downloaded google-earth-stable_current_x86_64.rpm from google
and tried to install it, got
Error: Transaction check error:
file /usr/bin from install of google-earth-stable-7.1.4.1529-0.x86_64
conflicts with file f
On 02/15/2016 07:04 AM, Rex Dieter wrote:
jd1008 wrote:
Downloaded google-earth-stable_current_x86_64.rpm from google
and tried to install it, got
Error: Transaction check error:
file /usr/bin from install of google-earth-stable-7.1.4.1529-0.x86_64
conflicts with file from package filesy
jd1008 wrote:
> Downloaded google-earth-stable_current_x86_64.rpm from google
> and tried to install it, got
> Error: Transaction check error:
>file /usr/bin from install of google-earth-stable-7.1.4.1529-0.x86_64
> conflicts with file from package filesystem-3.2-32.fc22.x86_64
google has b
24 matches
Mail list logo
