Re: Tripp Lite PowerAlert software

2017-02-09 Thread Rick Stevens
On 02/09/2017 04:27 PM, Robert Moskowitz wrote:
> 
> 
> On 02/09/2017 07:02 PM, Rick Stevens wrote:
>> On 02/09/2017 03:15 PM, Robert Moskowitz wrote:
>>>
>>> On 02/09/2017 06:05 PM, Rick Stevens wrote:
 On 02/09/2017 02:25 PM, Robert Moskowitz wrote:
> On 02/09/2017 04:59 PM, Rick Stevens wrote:
>> On 02/09/2017 01:45 PM, Robert Moskowitz wrote:
>>> Tripp Lite has their UPS management software available for Fedora
>>>
>>> Fedora 8
>>>
>>> that is.  SHEESH!
>>>
>>> Other that squeezing the source out of them and doing a build on a
>>> more
>>> modern Fedora, does anyone know of a UPS management software that
>>> will
>>> work with Tripp Lite UPS?
>>>
>>> BTW, I have been using Tripp Lite products since '84, so please
>>> don't
>>> recommend another brand of UPS.
>>>
>> Have you looked at NUT (Network Ups Tools)? It handles Tripp Lite
>> and a
>> whole bunch of others. Here's a list of the Tripp Lite stuff it
>> manages:
>>
>>   http://networkupstools.org/ddl/Tripp_Lite/
>>
>> It's available from the standard repos:
>>
>> nut.x86_64  2.7.4-4.fc25  fedora
>> nut-cgi.x86_64  2.7.4-4.fc25  fedora
>> nut-client.x86_64   2.7.4-4.fc25  fedora
>> nut-devel.x86_642.7.4-4.fc25  fedora
>> nut-xml.x86_64  2.7.4-4.fc25  fedora
>>
> Looks like I need usbhid-ups, but can't find it.
>
> Plus little information on how to work with this interface.
 That's part of the main nut package, along with a man page:

 [root@prophead ~]# rpm -ql nut | grep usbhid
 /usr/sbin/usbhid-ups
 /usr/share/man/man8/usbhid-ups.8.gz
>>> OK.  I did not have the cable plugged in right to the UPS.
>>>
>>> I am now seeing /dev/hidraw0, but NUT wants a host/port.  I assume
>>> localhost, but what port is hidraw0 mapping to?
>> I don't use nut myself, but grazing the man pages, you'd use
>> something like this in the ups.conf file:
>>
>> [tripplite]
>> driver = usbhid-ups
>> port = auto
>> vendorid = 
>>
>> Do an "lsusb" and see what vendor ID is shown for your UPS. For example,
>> scanning my USB bus, I see this sort of thing:
>>
>> [root@prophead ups]# lsusb
>> Bus 002 Device 002: ID 8087:8001 Intel Corp.
>> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> Bus 001 Device 002: ID 8087:8009 Intel Corp.
>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> Bus 004 Device 002: ID 0bc2:ab21 Seagate RSS LLC Backup Plus Slim
>> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>> Bus 003 Device 004: ID 0411:00a2 BUFFALO INC. (formerly MelCo., Inc.)
>>
>> I do NOT have a Tripp Lite UPS, but let's just say that the "BUFFALO
>> INC." thing is my Tripp Lite. I'd set up my ups.conf thus:
>>
>> [tripplite]
>> driver = usbhid-ups
>> bus = "003"
>> port = auto
>> vendorid = 0411
>>
>> The "bus = " isn't really necessary, but it'll keep the system from
>> scanning ALL of your USB buses. I think that's all you need.
> 
> I am doing this on another system and am looking back and forth between
> screens...
> 
> So in /etc/ups/ups.conf I have added:
> 
> [SMART1000LCD]
> driver = usbhid-ups
> port = auto
> bus = "003"
> vendorid = 09ae
> 
> I start up the NUT gui and it is showing host of localhost and port of 3493
> 
> and 'error connecting to localhost'  connection refused.
> 
> so what port is auto going to?  Since this is localhost, I am not
> supposed to set a firewalld rule for whatever port it is???

I think there's several things you need to do:

1. You shouldn't need to make any holes in your firewall if you're
using "localhost". If you want a remote machine to access your upsd
stuff, then yes, you need to poke a hole in your firewall for that port
to allow the remote machine access.

2. Make sure that udev rule I mentioned is in place and udev has been
reloaded.

3. The NUT GUI needs to talk to the upsd daemon (which probably isn't
running yet). You probably need to start the drivers first via:

systemctl start nut-driver.service

then start the upsd daemon via:

systemctl start nut-server.service

At that point, the NUT GUI should be able to talk to the upsd daemon
via whichever host and port is listed in the /etc/ups/upsd.conf file's
"LISTEN" directive (by default, localhost and port 3493).

4. If it all works as you want, don't forget to set nut-driver.service
and nut-server.service to start at boot by doing:

systemctl enable nut-driver.service
systemctl enable nut-server.service

Have a good look at the steps here:

http://tedfelix.com/software/nut-network-ups-tools.html

Pretty useful.

I haven't used NUT in a LONG time, and that was back when it only spoke
to UPS devices via serial 

Re: Tripp Lite PowerAlert software

2017-02-09 Thread Rick Stevens
On 02/09/2017 04:02 PM, Rick Stevens wrote:
> On 02/09/2017 03:15 PM, Robert Moskowitz wrote:
>>
>>
>> On 02/09/2017 06:05 PM, Rick Stevens wrote:
>>> On 02/09/2017 02:25 PM, Robert Moskowitz wrote:

 On 02/09/2017 04:59 PM, Rick Stevens wrote:
> On 02/09/2017 01:45 PM, Robert Moskowitz wrote:
>> Tripp Lite has their UPS management software available for Fedora
>>
>> Fedora 8
>>
>> that is.  SHEESH!
>>
>> Other that squeezing the source out of them and doing a build on a
>> more
>> modern Fedora, does anyone know of a UPS management software that will
>> work with Tripp Lite UPS?
>>
>> BTW, I have been using Tripp Lite products since '84, so please don't
>> recommend another brand of UPS.
>>
> Have you looked at NUT (Network Ups Tools)? It handles Tripp Lite and a
> whole bunch of others. Here's a list of the Tripp Lite stuff it
> manages:
>
>  http://networkupstools.org/ddl/Tripp_Lite/
>
> It's available from the standard repos:
>
> nut.x86_64  2.7.4-4.fc25  fedora
> nut-cgi.x86_64  2.7.4-4.fc25  fedora
> nut-client.x86_64   2.7.4-4.fc25  fedora
> nut-devel.x86_642.7.4-4.fc25  fedora
> nut-xml.x86_64  2.7.4-4.fc25  fedora
>
 Looks like I need usbhid-ups, but can't find it.

 Plus little information on how to work with this interface.
>>> That's part of the main nut package, along with a man page:
>>>
>>> [root@prophead ~]# rpm -ql nut | grep usbhid
>>> /usr/sbin/usbhid-ups
>>> /usr/share/man/man8/usbhid-ups.8.gz
>>
>> OK.  I did not have the cable plugged in right to the UPS.
>>
>> I am now seeing /dev/hidraw0, but NUT wants a host/port.  I assume
>> localhost, but what port is hidraw0 mapping to?
> 
> I don't use nut myself, but grazing the man pages, you'd use
> something like this in the ups.conf file:
> 
>   [tripplite]
>   driver = usbhid-ups
>   port = auto
>   vendorid = 
> 
> Do an "lsusb" and see what vendor ID is shown for your UPS. For example,
> scanning my USB bus, I see this sort of thing:
> 
> [root@prophead ups]# lsusb
> Bus 002 Device 002: ID 8087:8001 Intel Corp.
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 002: ID 8087:8009 Intel Corp.
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 004 Device 002: ID 0bc2:ab21 Seagate RSS LLC Backup Plus Slim
> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 003 Device 004: ID 0411:00a2 BUFFALO INC. (formerly MelCo., Inc.)
> 
> I do NOT have a Tripp Lite UPS, but let's just say that the "BUFFALO
> INC." thing is my Tripp Lite. I'd set up my ups.conf thus:
> 
>   [tripplite]
>   driver = usbhid-ups
>   bus = "003"
>   port = auto
>   vendorid = 0411
> 
> The "bus = " isn't really necessary, but it'll keep the system from
> scanning ALL of your USB buses. I think that's all you need.

Oh, I forgot one thing. Make sure you add the udev rule needed. On my
system, you'd need to:

sudo cp /lib/udev/rules.d/62-nut-usbups.rules /etc/udev/rules.d
sudo udevadm -R (or reboot to make sure the new rule is used)
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
-Overweight:  When you step on your dog's tail...and it dies.-
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Tripp Lite PowerAlert software

2017-02-09 Thread Robert Moskowitz



On 02/09/2017 07:02 PM, Rick Stevens wrote:

On 02/09/2017 03:15 PM, Robert Moskowitz wrote:


On 02/09/2017 06:05 PM, Rick Stevens wrote:

On 02/09/2017 02:25 PM, Robert Moskowitz wrote:

On 02/09/2017 04:59 PM, Rick Stevens wrote:

On 02/09/2017 01:45 PM, Robert Moskowitz wrote:

Tripp Lite has their UPS management software available for Fedora

Fedora 8

that is.  SHEESH!

Other that squeezing the source out of them and doing a build on a
more
modern Fedora, does anyone know of a UPS management software that will
work with Tripp Lite UPS?

BTW, I have been using Tripp Lite products since '84, so please don't
recommend another brand of UPS.


Have you looked at NUT (Network Ups Tools)? It handles Tripp Lite and a
whole bunch of others. Here's a list of the Tripp Lite stuff it
manages:

  http://networkupstools.org/ddl/Tripp_Lite/

It's available from the standard repos:

nut.x86_64  2.7.4-4.fc25  fedora
nut-cgi.x86_64  2.7.4-4.fc25  fedora
nut-client.x86_64   2.7.4-4.fc25  fedora
nut-devel.x86_642.7.4-4.fc25  fedora
nut-xml.x86_64  2.7.4-4.fc25  fedora


Looks like I need usbhid-ups, but can't find it.

Plus little information on how to work with this interface.

That's part of the main nut package, along with a man page:

[root@prophead ~]# rpm -ql nut | grep usbhid
/usr/sbin/usbhid-ups
/usr/share/man/man8/usbhid-ups.8.gz

OK.  I did not have the cable plugged in right to the UPS.

I am now seeing /dev/hidraw0, but NUT wants a host/port.  I assume
localhost, but what port is hidraw0 mapping to?

I don't use nut myself, but grazing the man pages, you'd use
something like this in the ups.conf file:

[tripplite]
driver = usbhid-ups
port = auto
vendorid = 

Do an "lsusb" and see what vendor ID is shown for your UPS. For example,
scanning my USB bus, I see this sort of thing:

[root@prophead ups]# lsusb
Bus 002 Device 002: ID 8087:8001 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8009 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 0bc2:ab21 Seagate RSS LLC Backup Plus Slim
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 0411:00a2 BUFFALO INC. (formerly MelCo., Inc.)

I do NOT have a Tripp Lite UPS, but let's just say that the "BUFFALO
INC." thing is my Tripp Lite. I'd set up my ups.conf thus:

[tripplite]
driver = usbhid-ups
bus = "003"
port = auto
vendorid = 0411

The "bus = " isn't really necessary, but it'll keep the system from
scanning ALL of your USB buses. I think that's all you need.


I am doing this on another system and am looking back and forth between 
screens...


So in /etc/ups/ups.conf I have added:

[SMART1000LCD]
driver = usbhid-ups
port = auto
bus = "003"
vendorid = 09ae

I start up the NUT gui and it is showing host of localhost and port of 3493

and 'error connecting to localhost'  connection refused.

so what port is auto going to?  Since this is localhost, I am not 
supposed to set a firewalld rule for whatever port it is???


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Tripp Lite PowerAlert software

2017-02-09 Thread Rick Stevens
On 02/09/2017 03:15 PM, Robert Moskowitz wrote:
> 
> 
> On 02/09/2017 06:05 PM, Rick Stevens wrote:
>> On 02/09/2017 02:25 PM, Robert Moskowitz wrote:
>>>
>>> On 02/09/2017 04:59 PM, Rick Stevens wrote:
 On 02/09/2017 01:45 PM, Robert Moskowitz wrote:
> Tripp Lite has their UPS management software available for Fedora
>
> Fedora 8
>
> that is.  SHEESH!
>
> Other that squeezing the source out of them and doing a build on a
> more
> modern Fedora, does anyone know of a UPS management software that will
> work with Tripp Lite UPS?
>
> BTW, I have been using Tripp Lite products since '84, so please don't
> recommend another brand of UPS.
>
 Have you looked at NUT (Network Ups Tools)? It handles Tripp Lite and a
 whole bunch of others. Here's a list of the Tripp Lite stuff it
 manages:

  http://networkupstools.org/ddl/Tripp_Lite/

 It's available from the standard repos:

 nut.x86_64  2.7.4-4.fc25  fedora
 nut-cgi.x86_64  2.7.4-4.fc25  fedora
 nut-client.x86_64   2.7.4-4.fc25  fedora
 nut-devel.x86_642.7.4-4.fc25  fedora
 nut-xml.x86_64  2.7.4-4.fc25  fedora

>>> Looks like I need usbhid-ups, but can't find it.
>>>
>>> Plus little information on how to work with this interface.
>> That's part of the main nut package, along with a man page:
>>
>> [root@prophead ~]# rpm -ql nut | grep usbhid
>> /usr/sbin/usbhid-ups
>> /usr/share/man/man8/usbhid-ups.8.gz
> 
> OK.  I did not have the cable plugged in right to the UPS.
> 
> I am now seeing /dev/hidraw0, but NUT wants a host/port.  I assume
> localhost, but what port is hidraw0 mapping to?

I don't use nut myself, but grazing the man pages, you'd use
something like this in the ups.conf file:

[tripplite]
driver = usbhid-ups
port = auto
vendorid = 

Do an "lsusb" and see what vendor ID is shown for your UPS. For example,
scanning my USB bus, I see this sort of thing:

[root@prophead ups]# lsusb
Bus 002 Device 002: ID 8087:8001 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8009 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 0bc2:ab21 Seagate RSS LLC Backup Plus Slim
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 0411:00a2 BUFFALO INC. (formerly MelCo., Inc.)

I do NOT have a Tripp Lite UPS, but let's just say that the "BUFFALO
INC." thing is my Tripp Lite. I'd set up my ups.conf thus:

[tripplite]
driver = usbhid-ups
bus = "003"
port = auto
vendorid = 0411

The "bus = " isn't really necessary, but it'll keep the system from
scanning ALL of your USB buses. I think that's all you need.
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
-If Windows isn't a virus, then it sure as hell is a carrier!-
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: What do Network Manager / Network Messages Mean That are Shown at Boot Time

2017-02-09 Thread Ed Greshko
On 02/10/17 04:30, Stephen Morris wrote:
> Hi Ed,
> I've tried adding the two statements to the unit section of
> dkms.service and they do cause dkms to run prior reaching
> network.target, but they make no difference to the network being
> available at boot time.
> It seems to me that the issue is that Fedora is not providing
> proper functionality on 802.11ac USB devices as evidenced by the
> following situations:
>
>  * Network Manager Ethernet Definition set to "Onboot=yes", the network
>is available at boot
>  * Network Manager 2.4GHz SSID Definition set to "Onboot=yes" and
>restricted to the pci wifi device, the network is available at boot
>  * Network Manager 2.4GHz SSID Definition set to "Onboot=yes" and
>restricted to the usb adapter device, the network is available at boot
>  * Network Manager 5GHz SSID Definition set to "Onboot=yes" and
>restricted to the usb adapter device, the network is not available
>at boot and is not available until the desktop actually starts
>(unlike in Ubuntu where the same driver source code that is used in
>Fedora, is compiled and installed into the kernel with DKMS, the
>network is available at Display Manager start time) 


Well, I don't have the HW to be able to try and reproduce your issue.

I can say that the only time I've had a situation where a WAN connection
wasn't up at the end of a boot was when I forgot to check the box
"Automatically connect to this network when it is available" in the
"General Configuration" settings for the connection.


-- 
Fedora Users List - The place to go to get others to do the work for you
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Tripp Lite PowerAlert software

2017-02-09 Thread Robert Moskowitz



On 02/09/2017 06:05 PM, Rick Stevens wrote:

On 02/09/2017 02:25 PM, Robert Moskowitz wrote:


On 02/09/2017 04:59 PM, Rick Stevens wrote:

On 02/09/2017 01:45 PM, Robert Moskowitz wrote:

Tripp Lite has their UPS management software available for Fedora

Fedora 8

that is.  SHEESH!

Other that squeezing the source out of them and doing a build on a more
modern Fedora, does anyone know of a UPS management software that will
work with Tripp Lite UPS?

BTW, I have been using Tripp Lite products since '84, so please don't
recommend another brand of UPS.


Have you looked at NUT (Network Ups Tools)? It handles Tripp Lite and a
whole bunch of others. Here's a list of the Tripp Lite stuff it manages:

 http://networkupstools.org/ddl/Tripp_Lite/

It's available from the standard repos:

nut.x86_64  2.7.4-4.fc25  fedora
nut-cgi.x86_64  2.7.4-4.fc25  fedora
nut-client.x86_64   2.7.4-4.fc25  fedora
nut-devel.x86_642.7.4-4.fc25  fedora
nut-xml.x86_64  2.7.4-4.fc25  fedora


Looks like I need usbhid-ups, but can't find it.

Plus little information on how to work with this interface.

That's part of the main nut package, along with a man page:

[root@prophead ~]# rpm -ql nut | grep usbhid
/usr/sbin/usbhid-ups
/usr/share/man/man8/usbhid-ups.8.gz


OK.  I did not have the cable plugged in right to the UPS.

I am now seeing /dev/hidraw0, but NUT wants a host/port.  I assume 
localhost, but what port is hidraw0 mapping to?


thanks

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Tripp Lite PowerAlert software

2017-02-09 Thread Rick Stevens
On 02/09/2017 02:25 PM, Robert Moskowitz wrote:
> 
> 
> On 02/09/2017 04:59 PM, Rick Stevens wrote:
>> On 02/09/2017 01:45 PM, Robert Moskowitz wrote:
>>> Tripp Lite has their UPS management software available for Fedora
>>>
>>> Fedora 8
>>>
>>> that is.  SHEESH!
>>>
>>> Other that squeezing the source out of them and doing a build on a more
>>> modern Fedora, does anyone know of a UPS management software that will
>>> work with Tripp Lite UPS?
>>>
>>> BTW, I have been using Tripp Lite products since '84, so please don't
>>> recommend another brand of UPS.
>>>
>> Have you looked at NUT (Network Ups Tools)? It handles Tripp Lite and a
>> whole bunch of others. Here's a list of the Tripp Lite stuff it manages:
>>
>> http://networkupstools.org/ddl/Tripp_Lite/
>>
>> It's available from the standard repos:
>>
>> nut.x86_64  2.7.4-4.fc25  fedora
>> nut-cgi.x86_64  2.7.4-4.fc25  fedora
>> nut-client.x86_64   2.7.4-4.fc25  fedora
>> nut-devel.x86_642.7.4-4.fc25  fedora
>> nut-xml.x86_64  2.7.4-4.fc25  fedora
>>
> Looks like I need usbhid-ups, but can't find it.
> 
> Plus little information on how to work with this interface.

That's part of the main nut package, along with a man page:

[root@prophead ~]# rpm -ql nut | grep usbhid
/usr/sbin/usbhid-ups
/usr/share/man/man8/usbhid-ups.8.gz
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
-I don't suffer from insanity...I enjoy every minute of it!  -
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Tripp Lite PowerAlert software

2017-02-09 Thread Robert Moskowitz



On 02/09/2017 04:59 PM, Rick Stevens wrote:

On 02/09/2017 01:45 PM, Robert Moskowitz wrote:

Tripp Lite has their UPS management software available for Fedora

Fedora 8

that is.  SHEESH!

Other that squeezing the source out of them and doing a build on a more
modern Fedora, does anyone know of a UPS management software that will
work with Tripp Lite UPS?

BTW, I have been using Tripp Lite products since '84, so please don't
recommend another brand of UPS.


Have you looked at NUT (Network Ups Tools)? It handles Tripp Lite and a
whole bunch of others. Here's a list of the Tripp Lite stuff it manages:

http://networkupstools.org/ddl/Tripp_Lite/

It's available from the standard repos:

nut.x86_64  2.7.4-4.fc25  fedora
nut-cgi.x86_64  2.7.4-4.fc25  fedora
nut-client.x86_64   2.7.4-4.fc25  fedora
nut-devel.x86_642.7.4-4.fc25  fedora
nut-xml.x86_64  2.7.4-4.fc25  fedora


Looks like I need usbhid-ups, but can't find it.

Plus little information on how to work with this interface.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Tripp Lite PowerAlert software

2017-02-09 Thread Robert Moskowitz



On 02/09/2017 04:59 PM, Rick Stevens wrote:

On 02/09/2017 01:45 PM, Robert Moskowitz wrote:

Tripp Lite has their UPS management software available for Fedora

Fedora 8

that is.  SHEESH!

Other that squeezing the source out of them and doing a build on a more
modern Fedora, does anyone know of a UPS management software that will
work with Tripp Lite UPS?

BTW, I have been using Tripp Lite products since '84, so please don't
recommend another brand of UPS.


Have you looked at NUT (Network Ups Tools)? It handles Tripp Lite and a
whole bunch of others. Here's a list of the Tripp Lite stuff it manages:

http://networkupstools.org/ddl/Tripp_Lite/


Thanks.  I will give it a try.  My unit is listed.


It's available from the standard repos:

nut.x86_64  2.7.4-4.fc25  fedora
nut-cgi.x86_64  2.7.4-4.fc25  fedora
nut-client.x86_64   2.7.4-4.fc25  fedora
nut-devel.x86_642.7.4-4.fc25  fedora
nut-xml.x86_64  2.7.4-4.fc25  fedora
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
-   grep me no patterns and I'll tell you no lines   -
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Tripp Lite PowerAlert software

2017-02-09 Thread Rick Stevens
On 02/09/2017 01:45 PM, Robert Moskowitz wrote:
> Tripp Lite has their UPS management software available for Fedora
> 
> Fedora 8
> 
> that is.  SHEESH!
> 
> Other that squeezing the source out of them and doing a build on a more
> modern Fedora, does anyone know of a UPS management software that will
> work with Tripp Lite UPS?
> 
> BTW, I have been using Tripp Lite products since '84, so please don't
> recommend another brand of UPS.
> 

Have you looked at NUT (Network Ups Tools)? It handles Tripp Lite and a
whole bunch of others. Here's a list of the Tripp Lite stuff it manages:

http://networkupstools.org/ddl/Tripp_Lite/

It's available from the standard repos:

nut.x86_64  2.7.4-4.fc25  fedora
nut-cgi.x86_64  2.7.4-4.fc25  fedora
nut-client.x86_64   2.7.4-4.fc25  fedora
nut-devel.x86_642.7.4-4.fc25  fedora
nut-xml.x86_64  2.7.4-4.fc25  fedora
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
-   grep me no patterns and I'll tell you no lines   -
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Tripp Lite PowerAlert software

2017-02-09 Thread dsavage
> Tripp Lite has their UPS management software available for Fedora
>
> Fedora 8
>
> that is.  SHEESH!
>
> Other that squeezing the source out of them and doing a build on a more
> modern Fedora, does anyone know of a UPS management software that will
> work with Tripp Lite UPS?
>
> BTW, I have been using Tripp Lite products since '84, so please don't
> recommend another brand of UPS.
>
> thanks

I vote for squeeze. I too like Tripp Lite products and have for many
years. Maybe someone in the Fedora infrastructure could write them a
letter? Or send Luca Brasi?

--Doc Savage
  Fairview Heights, IL
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Fedora 24 Update: nitrokey-app-0.6.3-1.fc24

2017-02-09 Thread Patrick O'Callaghan
On Thu, 2017-02-09 at 00:04 -0800, Joe Zeff wrote:
> On 02/08/2017 11:56 PM, Tim wrote:
> > I wish that sort of useless description would result in packages getting
> > an automatic banning.
> 
> No, not banning.  There should be guidelines for what an acceptable 
> description consists of, and any package that doesn't meet them should 
> be rejected until it does.

I can't see the message this is in reply to. Was it perhaps cross-
posted from somewhere else?

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Tripp Lite PowerAlert software

2017-02-09 Thread Robert Moskowitz

Tripp Lite has their UPS management software available for Fedora

Fedora 8

that is.  SHEESH!

Other that squeezing the source out of them and doing a build on a more 
modern Fedora, does anyone know of a UPS management software that will 
work with Tripp Lite UPS?


BTW, I have been using Tripp Lite products since '84, so please don't 
recommend another brand of UPS.


thanks

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: What do Network Manager / Network Messages Mean That are Shown at Boot Time

2017-02-09 Thread Stephen Morris

On 08/02/2017 06:09, Ed Greshko wrote:


On 02/06/17 05:08, Stephen Morris wrote:

 From what I've read, DKMS will compile the driver after a new kernel is 
installed if
the right parameter is supplied on the make command it has been told to use.
 At boot time DKMS will run and check if the source modules it has been 
told to build
and install have been added to the running kernel and
if not it will undertake those actions.
 The situation that prompted this mail was where to test the auto
build functionality in DKMS I forced the boot time building.
 I've checked the /etc/kernel/postinst.d/dkms script and I'm not sure its 
working
properly (I will need to check what the autoinstaller is doing). It seems to me 
that the
autoinstaller is being run against the kernel identified by $kern_inst, which 
without
knowing what Fedora is doing, I would have assumed is set to the name of the 
running
kernel, which if I am correct it seems that DKMS is building the specified 
module
against the newly installed kernel headers and installing into the new kernel 
(this is
if the make parameter that identifies the kernel version to build against is 
specified,
which in my case is specified in dkms.conf).

You may want to try adding

Before=network.target
Wants=network.target

To the Unit portion of the dkms.service file.

Hi Ed,
I've tried adding the two statements to the unit section of 
dkms.service and they do cause dkms to run prior reaching 
network.target, but they make no difference to the network being 
available at boot time.
It seems to me that the issue is that Fedora is not providing 
proper functionality on 802.11ac USB devices as evidenced by the 
following situations:


 * Network Manager Ethernet Definition set to "Onboot=yes", the network
   is available at boot
 * Network Manager 2.4GHz SSID Definition set to "Onboot=yes" and
   restricted to the pci wifi device, the network is available at boot
 * Network Manager 2.4GHz SSID Definition set to "Onboot=yes" and
   restricted to the usb adapter device, the network is available at boot
 * Network Manager 5GHz SSID Definition set to "Onboot=yes" and
   restricted to the usb adapter device, the network is not available
   at boot and is not available until the desktop actually starts
   (unlike in Ubuntu where the same driver source code that is used in
   Fedora, is compiled and installed into the kernel with DKMS, the
   network is available at Display Manager start time)


What I'm not sure of at the moment is what I need to do to rectify 
the situation.


regards,
Steve




___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: r8712u driver fails in F25

2017-02-09 Thread David A. De Graaf

On 02/08/17 16:50, poma wrote:

On 07.02.2017 21:54, David A. De Graaf wrote:

The r8712u driver from the staging area has stopped working in Fedora
25.

The r8712u driver works just fine in Fedora 24 and it seems to be
substantially unchanged.




You can try the following two options:

- Disable Pre-association / Scanning random MAC address;


OR

- Switch to one of the modern version of the driver,
  r92su is easier to set up because it uses the same firmware as r8712u;



Thank you, poma.  Your answer is spot-on.

Your first suggestion attempts to push me into the swamp of
understanding the NetworkManager.  As a senior member of this august
brotherhood, I do not have enough days left to undertake this
challenge.  I'm afraid I cannot and will not attempt to make sense of
the "logic" represented there.

Your second suggestion - build and use r92su instead of r8712u -
works perfectly.  I measured bandwidth of only 28.4 Mbit/sec compared
with your ~82 Mbit/sec, but I'll leave that curiosity for another day.

This raises a number of ancillary questions:

1 - How did you discover the existence of this newer r92su driver, and
where to find it?

2 - Are there others, hidden from mere mortals, for other devices?

3 - Was Fedora 25 knowingly released with broken drivers when better
ones are available for those privileged to be aware of them?

4 - Why, exactly, has the r8712u driver become broken?  It has worked
perfectly through F24.

5 - Was any of this announced?  Will it be?


poma, thank you again for your helpful information.  I enjoy reading
your comments.  They're always helpful, although sometimes so concise
as to be incomprehensible.  This one was clear and complete.



--
David A. De GraafDATIX, Inc.Hendersonville, NC
d...@datix.us www.datix.us
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Fedora 24 Update: nitrokey-app-0.6.3-1.fc24

2017-02-09 Thread Kevin Fenzi
On Thu, 9 Feb 2017 00:04:16 -0800
Joe Zeff  wrote:

> On 02/08/2017 11:56 PM, Tim wrote:
> > I wish that sort of useless description would result in packages
> > getting an automatic banning.  
> 
> No, not banning.  There should be guidelines for what an acceptable 
> description consists of, and any package that doesn't meet them
> should be rejected until it does.

Well, the time to make sure that looks good is at initial review time. 
The packaging guidelines say this about summary and description: 

https://fedoraproject.org/wiki/Packaging:Guidelines#Summary_and_description

Unfortunately, it's kind of subjective what a good summary /
description would be. Perhaps the guideline could say "Describe what
the package is as if to someone who had no idea what it was" ? 
But in some cases there's packages  like libraries where the audience
for the package already should be someone who knows pretty well what it
does. 

Anyhow, I'd suggest: 

1) file a bug on nitrokey politely saying that the description and
summary are not useful and ask them to redo them. 

2) If you like open a dialog with the Fedora Packaging Comittee to make
the guidelines better. You can find them on the
packag...@lists.fedoraproject.org list or the
de...@lists.fedoraproject.org list. 

kevin



pgppVyvB7DZPM.pgp
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Can Thunderbird save into a local, hierarchical mailbox directory

2017-02-09 Thread William W. Austin


On 2017-02-06 17:41, William W. Austin wrote:
>
> Over the years I have used a variety of mailer GUI's (not to mention
> tty-based interfaces) and I am trying to "modernize" a bit and move to
> thunderbird.
>
> 
[SNIP]

Apologies - somehow my original email was severely truncated in
transit.  But that's irrelevant and I have found a way to solve the problem.

It isn't obvious, but it is possible to do it and if there is any
interest I can send the procedure.  (Basically it's a mixture of shell
scripts* and GUI actions.)


* if you don't like shell scripts the commands aren't that difficult to
cut and paste - I just did it that way so that I wouldn't have to type
it twice...

Thanks to anyone who sent a response off-list whom I haven't already
thanked.

 -- William Austin

-- 
william w. austin aire...@att.net
"life is just another phase i'm going through. this time, anyway ..."

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Hibernation on F25

2017-02-09 Thread Patrick O'Callaghan
On Thu, 2017-02-09 at 17:28 +, James Hogarth wrote:
> There's also still the outstanding bug where anaconda is not adding the
> resume= arguement to the kernel args to point at the swap partition so the
> system can never resume.

[Please fix reply quoting in your mail client to retain proper
attribution].

Yes, you need to edit /etc/sysconfig/grub and add
'resume=UUID=xxx' (without the quotes) to
the GRUB_CMDLINE_LINUX line, where xxx is the UUID of
the partition where swap is located. Then run grub2-mkconfig.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Hibernation on F25

2017-02-09 Thread Rick Stevens
On 02/09/2017 09:19 AM, Patrick O'Callaghan wrote:
> On Thu, 2017-02-09 at 18:07 +0100, Massimo Canonico wrote:
>> Hi all,
>> do you guys were able to hibernate your Fedora 25.
>> In my previous fedora pm-hibernate worked perfectly but now it seems 
>> much more complicate.
>> I tried to install this extension for gnome:
>> https://extensions.gnome.org/extension/755/hibernate-status-button/
>>
>> but probably I have something more to do.
>>
>> Any suggestion is more than welcome.
> 
> pm-suspend and pm-hibernate are deprecated. Now it's done via systemd
> (isn't everything?). I expect the Gnome extension just calls that but I
> use KDE so I wouldn't know (the KDE hibernate/suspend does work).
> 
> See 'man systemd-suspend.service'.
> 
> One thing to check: you must have enough free space in swap or the
> hibernation will fail (though suspend should still work). Use 'free' to
> see how much free space there is and add some more if it's not enough.
> How do you know how much is enough? It depends on your workload so you
> basically guess, which is pretty much what you do with swap space
> anyway.

The old "rule of thumb" for swap space was twice your RAM size (16GB
RAM = 32GB swap). Few people do that now, but disks are relatively
cheap. I still use the 2x rule but I've been a Unix geek for 40 years
and it's hard to teach this old dog new tricks:

[root@prophead ~]# free
  totalusedfree  shared  buff/cache
available
Mem:   16290516 7885948  974060  474628 7430508
7468044
Swap:  39047164 41239046752

--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
-   Duct Tape + Magic Marker = Label Maker!  -
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Hibernation on F25

2017-02-09 Thread James Hogarth
On 9 Feb 2017 5:26 pm, "Patrick O'Callaghan"  wrote:

On Thu, 2017-02-09 at 18:07 +0100, Massimo Canonico wrote:
> Hi all,
> do you guys were able to hibernate your Fedora 25.
> In my previous fedora pm-hibernate worked perfectly but now it seems
> much more complicate.
> I tried to install this extension for gnome:
> https://extensions.gnome.org/extension/755/hibernate-status-button/
>
> but probably I have something more to do.
>
> Any suggestion is more than welcome.

pm-suspend and pm-hibernate are deprecated. Now it's done via systemd
(isn't everything?). I expect the Gnome extension just calls that but I
use KDE so I wouldn't know (the KDE hibernate/suspend does work).

See 'man systemd-suspend.service'.

One thing to check: you must have enough free space in swap or the
hibernation will fail (though suspend should still work). Use 'free' to
see how much free space there is and add some more if it's not enough.
How do you know how much is enough? It depends on your workload so you
basically guess, which is pretty much what you do with swap space
anyway.


There's also still the outstanding bug where anaconda is not adding the
resume= arguement to the kernel args to point at the swap partition so the
system can never resume.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: [F25, KDE] very very slow internet connexion

2017-02-09 Thread Rick Stevens
On 02/09/2017 06:51 AM, Frédéric Bron wrote:
>> That's nice, but you didn't say what you did to "get it working again".
> 
> I did nothing!

Ah, you mean just removing that one Broadcom driver fixed things? Ok.
That's good!

Make sure you check your bluetooth stuff as well if you use it. Some of
the Broadcom drivers handle both wifi AND bluetooth and that new one
you're using may not do both.
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
-  Do you know how to save five drowning lawyers?  No?  GOOD!-
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Hibernation on F25

2017-02-09 Thread Patrick O'Callaghan
On Thu, 2017-02-09 at 18:07 +0100, Massimo Canonico wrote:
> Hi all,
> do you guys were able to hibernate your Fedora 25.
> In my previous fedora pm-hibernate worked perfectly but now it seems 
> much more complicate.
> I tried to install this extension for gnome:
> https://extensions.gnome.org/extension/755/hibernate-status-button/
> 
> but probably I have something more to do.
> 
> Any suggestion is more than welcome.

pm-suspend and pm-hibernate are deprecated. Now it's done via systemd
(isn't everything?). I expect the Gnome extension just calls that but I
use KDE so I wouldn't know (the KDE hibernate/suspend does work).

See 'man systemd-suspend.service'.

One thing to check: you must have enough free space in swap or the
hibernation will fail (though suspend should still work). Use 'free' to
see how much free space there is and add some more if it's not enough.
How do you know how much is enough? It depends on your workload so you
basically guess, which is pretty much what you do with swap space
anyway.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Hibernation on F25

2017-02-09 Thread Massimo Canonico

Hi all,
do you guys were able to hibernate your Fedora 25.
In my previous fedora pm-hibernate worked perfectly but now it seems 
much more complicate.

I tried to install this extension for gnome:
https://extensions.gnome.org/extension/755/hibernate-status-button/

but probably I have something more to do.

Any suggestion is more than welcome.

Thanks
M
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Mouse problems

2017-02-09 Thread Patrick O'Callaghan
On Thu, 2017-02-09 at 06:46 -0700, Lawrence E Graves wrote:
> [lawrence70@Jehovah ~]$ su -
> Password:
> [root@Jehovah ~]# xev
> Outer window is 0x181, inner window is 0x182
> 
> PropertyNotify event, serial 8, synthetic NO, window 0x181,
>  atom 0x27 (WM_NAME), time 7838966, state PropertyNewValue
> 
> PropertyNotify event, serial 9, synthetic NO, window 0x181,
>  atom 0x22 (WM_COMMAND), time 7838966, state PropertyNewValue
[...]

[Please don't top-post on this list. See the Guidelines]

I don't see any button press events in what you posted. You have to
click the mouse inside the small window (read the xev man page). Also,
it's not very useful to copy these events here. The point is to note
what happens *as you click or release each button*.

Note that xev is for X. I don't know what it does on Wayland, if
anything, or if there's a Wayland equivalent.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: bluetooth broken (?)

2017-02-09 Thread Michael Cronenworth

On 02/09/2017 09:53 AM, Frank Elsner wrote:

The "Blocked through rfkill" made me wonder.
I immediately did

# rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
 Soft blocked: no
 Hard blocked: no

And now I'm completely confused.


Your laptop may not be playing nice. Try toggling the function keys on your keyboard 
to turn bluetooth on/off. It may also be controlled through the wi-fi on/off button.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: bluetooth broken (?)

2017-02-09 Thread Frank Elsner
On Wed, 8 Feb 2017 09:42:48 -0800 Rick Stevens wrote:

  [ ... ]

> Do you have bluetoothd running? Check by
> 
>   systemctl status bluetooth.service

Yes, see 

]# systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Thu 2017-02-09 16:47:45 CET; 1min 45s ago
 Docs: man:bluetoothd(8)
 Main PID: 8126 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 4915)
   CGroup: /system.slice/bluetooth.service
   └─8126 /usr/libexec/bluetooth/bluetoothd

Feb 09 16:47:45 siffux systemd[1]: Stopped Bluetooth service.
Feb 09 16:47:45 siffux systemd[1]: Starting Bluetooth service...
Feb 09 16:47:45 siffux bluetoothd[8126]: Bluetooth daemon 5.43
Feb 09 16:47:45 siffux systemd[1]: Started Bluetooth service.
Feb 09 16:47:45 siffux bluetoothd[8126]: Starting SDP server
Feb 09 16:47:45 siffux bluetoothd[8126]: Bluetooth management interface 1.14 
initialized
Feb 09 16:47:45 siffux bluetoothd[8126]: Failed to set mode: Blocked through 
rfkill (0x12)
Feb 09 16:47:45 siffux bluetoothd[8126]: Endpoint registered: sender=:1.27 
path=/MediaEndpoint/A2DPSource
Feb 09 16:47:45 siffux bluetoothd[8126]: Endpoint registered: sender=:1.27 
path=/MediaEndpoint/A2DPSink

The "Blocked through rfkill" made me wonder.
I immediately did

# rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: no
Hard blocked: no

And now I'm completely confused.


--Frank Elsner
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: [F25, KDE] very very slow internet connexion

2017-02-09 Thread Frédéric Bron
> That's nice, but you didn't say what you did to "get it working again".

I did nothing!

Frédéric
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Mouse problems

2017-02-09 Thread Jon LaBadie
On Thu, Feb 09, 2017 at 06:49:18AM -0700, Lawrence E Graves wrote:
> If I got to my files and double click on documents, it won't work. If I go
> to settings and click on mouse and touch pad and test the double click, it
> doesn't work. I hope that makes sense.
> 
'm not having that problem in mate or gnome environ.

Isn't there a mouse setting for how rapid the clicks
must be?  Perhaps yours is set for too quick.

jl
-- 
Jon H. LaBadie  jo...@jgcomp.com
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Fedora on Lenovo Yoga Book?

2017-02-09 Thread Jeandet Alexis
Hi, 
The Yoga Book is flashed with kernel flinger as boot loader. For now I
don't really understand if I'm supposed to be able to access to a
BIOS/EFI menu or if the only firmware is kernel flinger.Does anyone has
some experience with x86 android tablets? Can I configure kernel
flinger to load GRUB, or directly another kernel? It seems most of the
tasks might be done with ADB.I'm quite lost I thought that an x86
device might always have an EFI/BIOS with at least few boot options. I
turns out that it's easier to boot linux on a Chinese no-name Allwinner
tablet :).
The good points are that the device is cool, even with Android. It has
a good finish and being able to write on real paper is really nice. I
really want to see Fedora on it!
Best regards,Alexis.Le mercredi 08 février 2017 à 21:23 +0100, Jeandet
Alexis a écrit :
> HI,
> 
> I bought one today, I took the Android version.(Much cheaper, 100€
> less)
> Few observations first:
>   -No regular size USB, it's micro USB (OTG or HOST capable)
>   -No regular BIOS/EFI menu just android boot menu
> For now I need to investigate, I have no experience with Android on
> x86 and changing OS on such devices.
> Any hints here are welcome.
> 
> Alexis.
> Le mardi 07 février 2017 à 14:08 -0800, Rick Stevens a écrit :
> > On 02/07/2017 01:44 PM, Jeandet Alexis wrote:
> > > Le mardi 07 février 2017 à 13:16 -0800, Rick Stevens a écrit :
> > > > On 02/07/2017 12:59 PM, Jeandet Alexis wrote:
> > > > > Thank you for your answer, my fear is mainly their halo
> > > > > keyboard.
> > > > 
> > > > If you already have the device, try booting a LiveCD and try to
> > > > run it.
> > > 
> > > Not yet.
> > 
> > Ah. Yeah, that makes all of it a bit more dicey. And I hadn't
> > realized
> > it was Android. I was looking at the laptops, not the "book".
> > 
> > > > Won't cost you anything except the use of a thumbdrive or blank
> > > > CD and
> > > > your time. You'll need the CD anyway if you find it works and
> > > > you decide
> > > > to install.
> > > 
> > > Yep that's the plan, but before burning 500€ I would be happy to
> > > be sure
> > > it won't be like Bay-Trail Atoms and their 32bit UEFI or
> > > something like
> > > this.
> > 
> > Uhm, dunno about that. I'd suspect it's a 64-bit UEFI BIOS, but
> > Lenovo
> > often has their own ideas about what's needed. The machine comes
> > with
> > Android Marshmallow (6) and I'm not sure what requirements that has
> > as far as UEFI is concerned.
> > 
> > > > I have read that others have installed Ubuntu onto Yogas and
> > > > beyond
> > > > some teething problems with the on-screen keyboards, gestures
> > > > and
> > > > mouse clicks (somewhat similar to what Alexis says below), it
> > > > seems to
> > > > work.
> > > 
> > > The problem with this device is that without keyboard you are
> > > really stuck.
> > 
> > I guess there's a possibility of using a USB keyboard if you have
> > issues. That being said, if this is going to be your primary
> > machine and
> > you're on a budget, you may not want to be the David on this. If
> > you
> > can afford it and have the time, I'm sure the community would LOVE
> > to
> > have someone sort this out. I'd be interested (oh, gawd, just what
> > I
> > need...another bloody computer!)
> > 
> > > > > Le mardi 07 février 2017 à 15:39 -0500, Billy Davis a écrit :
> > > > > > I just installed CentOS 7.3 on a Lenovo Twist Ultra Laptop.
> > > > > > Works fine 
> > > > > > for the most part but:
> > > > > > 
> > > > > > * Keyboard/touchpad do NOT work 'out of the box'. Small mod
> > > > > > to grub
> > > > > > file 
> > > > > > fixed keyboard and 'mouse' part of touchpad (ie, mouse
> > > > > > moves around on 
> > > > > > screenn and touchpad click works) but touchpad buttons do
> > > > > > NOT work.
> > > > > > 
> > > > > > * Wired network works fine, wireless does NOT. Fix is
> > > > > > supposedly 
> > > > > > available on line, but haven't tried it yet.
> > > > > > 
> > > > > > Runs great once you get it up.
> > > > > > 
> > > > > > Good luck,
> > > > > > Billy
> > > > > > 
> > > > > > On 2/7/2017 2:31 PM, Jeandet Alexis wrote:
> > > > > > > Hi,
> > > > > > > 
> > > > > > > Does anyone tried to install Fedora the Lenovo Yoga Book?
> > > > > > > If yes does
> > > > > > > it works well? I wonder if the keyboard/touchpad is well
> > > > > > > supported.
> > > > > > > 
> > > > > > > Best regards,
> > > > > > > Alexis.
> > > > > > > ___
> > > > > > > users mailing list -- users@lists.fedoraproject.org
> > > > > > > 
> > > > > > >  > > > > > > >
> > > > > > > To unsubscribe send an email to users-leave@lists.fedorap
> > > > > > > roject.org
> > > > > > >  > > > > > > >
> > > > > > > 
> > > > > > > 
> > > > > > 
> > > > > > 

Re: Mouse problems

2017-02-09 Thread Ed Greshko
On 02/09/17 21:49, Lawrence E Graves wrote:
> If I got to my files and double click on documents, it won't work. If
> I go to settings and click on mouse and touch pad and test the double
> click, it doesn't work. I hope that makes sense. 

The current default of GNOME is run a Wayland session and not an Xorg
session.

If you login with GNOME using Xorg does it still fail?

-- 
Fedora Users List - The place to go to get others to do the work for you
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Mouse problems

2017-02-09 Thread Lawrence E Graves
If I got to my files and double click on documents, it won't work. If I 
go to settings and click on mouse and touch pad and test the double 
click, it doesn't work. I hope that makes sense.



On 02/09/2017 06:44 AM, Ed Greshko wrote:

On 02/09/17 21:36, Ed Greshko wrote:

I don't use Gnome so I'm not going to be much help.

I just realized I had a VM with Gnome installed.

Brought up a terminal session and a double-click selected a word on a
line, and a triple-click selected the text in an entire line.

So, not sure what you're doing that isn't working.



--
All things are workable but don't all things work.
Prov. 3:5 & 6
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Mouse problems

2017-02-09 Thread Lawrence E Graves

[lawrence70@Jehovah ~]$ su -
Password:
[root@Jehovah ~]# xev
Outer window is 0x181, inner window is 0x182

PropertyNotify event, serial 8, synthetic NO, window 0x181,
atom 0x27 (WM_NAME), time 7838966, state PropertyNewValue

PropertyNotify event, serial 9, synthetic NO, window 0x181,
atom 0x22 (WM_COMMAND), time 7838966, state PropertyNewValue

PropertyNotify event, serial 10, synthetic NO, window 0x181,
atom 0x28 (WM_NORMAL_HINTS), time 7838966, state PropertyNewValue

CreateNotify event, serial 11, synthetic NO, window 0x181,
parent 0x181, window 0x182, (10,10), width 50, height 50
border_width 4, override NO

PropertyNotify event, serial 14, synthetic NO, window 0x181,
atom 0x133 (WM_PROTOCOLS), time 7838966, state PropertyNewValue

MapNotify event, serial 15, synthetic NO, window 0x181,
event 0x181, window 0x182, override NO

ConfigureNotify event, serial 28, synthetic NO, window 0x181,
event 0x181, window 0x181, (0,0), width 178, height 178,
border_width 0, above 0x601c22, override NO

PropertyNotify event, serial 28, synthetic NO, window 0x181,
atom 0x1ad (_NET_WM_ALLOWED_ACTIONS), time 7838972, state 
PropertyNewValue


ReparentNotify event, serial 29, synthetic NO, window 0x181,
event 0x181, window 0x181, parent 0x601c4b,
(0,0), override NO

PropertyNotify event, serial 29, synthetic NO, window 0x181,
atom 0x138 (_NET_FRAME_EXTENTS), time 7838981, state PropertyNewValue

ConfigureNotify event, serial 29, synthetic NO, window 0x181,
event 0x181, window 0x181, (10,41), width 178, height 178,
border_width 0, above 0x0, override NO

PropertyNotify event, serial 30, synthetic NO, window 0x181,
atom 0x13b (_NET_WM_DESKTOP), time 7838996, state PropertyNewValue

PropertyNotify event, serial 31, synthetic NO, window 0x181,
atom 0x17b (WM_STATE), time 7838997, state PropertyNewValue

PropertyNotify event, serial 31, synthetic NO, window 0x181,
atom 0x141 (_NET_WM_STATE), time 7838997, state PropertyNewValue

ConfigureNotify event, serial 33, synthetic YES, window 0x181,
event 0x181, window 0x181, (54,133), width 178, height 178,
border_width 2, above 0x0, override NO

PropertyNotify event, serial 33, synthetic NO, window 0x181,
atom 0x141 (_NET_WM_STATE), time 7839000, state PropertyNewValue

MapNotify event, serial 33, synthetic NO, window 0x181,
event 0x181, window 0x181, override NO

VisibilityNotify event, serial 33, synthetic NO, window 0x181,
state VisibilityUnobscured

Expose event, serial 33, synthetic NO, window 0x181,
(0,0), width 178, height 10, count 3

Expose event, serial 33, synthetic NO, window 0x181,
(0,10), width 10, height 58, count 2

Expose event, serial 33, synthetic NO, window 0x181,
(68,10), width 110, height 58, count 1

Expose event, serial 33, synthetic NO, window 0x181,
(0,68), width 178, height 110, count 0

FocusIn event, serial 33, synthetic NO, window 0x181,
mode NotifyNormal, detail NotifyNonlinear

KeymapNotify event, serial 33, synthetic NO, window 0x0,
keys:  68  0   0   0   16  0   0   0   0   0   0   0   0   0 0   0
   0   0   0   0   0   0   0   0   0   0   0   0   0   0 0   0

PropertyNotify event, serial 33, synthetic NO, window 0x181,
atom 0x141 (_NET_WM_STATE), time 7839005, state PropertyNewValue

PropertyNotify event, serial 33, synthetic NO, window 0x181,
atom 0x141 (_NET_WM_STATE), time 7839005, state PropertyNewValue

KeyRelease event, serial 33, synthetic NO, window 0x181,
root 0x29c, subw 0x0, time 7839067, (746,359), root:(802,494),
state 0x0, keycode 36 (keysym 0xff0d, Return), same_screen YES,
"   XLookupString gives 1 bytes: (0d) "
XFilterEvent returns: False

FocusOut event, serial 36, synthetic NO, window 0x181,
mode NotifyNormal, detail NotifyNonlinear

PropertyNotify event, serial 36, synthetic NO, window 0x181,
atom 0x141 (_NET_WM_STATE), time 7890537, state PropertyNewValue

I am using logitech wireless 550 combo.


On 02/09/2017 06:29 AM, Patrick O'Callaghan wrote:

On Thu, 2017-02-09 at 06:24 -0700, Lawrence E Graves wrote:

I use the gnome-shell. Is that what you mean?

You don't say anything about your mouse (USB, wireless dongle,
Bluetooth).

Try running xev and looking at the output. It reports each low-level
event including mouse-down and mouse-up. That way you can see if the
mouse itself is actually sending anything.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


--
All things are workable but don't all things work.
Prov. 3:5 & 6
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Mouse problems

2017-02-09 Thread Ed Greshko
On 02/09/17 21:24, Lawrence E Graves wrote:
> I use the gnome-shell. Is that what you mean?

Yes.  Along with putting replies at the bottom it is always best to
explain what Desktop you are using when reporting Desktop problems.  
Could be Gnome, KDE, xfce, etc. 

I don't use Gnome so I'm not going to be much help.

-- 
Fedora Users List - The place to go to get others to do the work for you
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Mouse problems

2017-02-09 Thread Ed Greshko
On 02/09/17 21:36, Ed Greshko wrote:
> I don't use Gnome so I'm not going to be much help.

I just realized I had a VM with Gnome installed.

Brought up a terminal session and a double-click selected a word on a
line, and a triple-click selected the text in an entire line.

So, not sure what you're doing that isn't working.

-- 
Fedora Users List - The place to go to get others to do the work for you
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Mouse problems

2017-02-09 Thread Patrick O'Callaghan
On Thu, 2017-02-09 at 06:24 -0700, Lawrence E Graves wrote:
> I use the gnome-shell. Is that what you mean?

You don't say anything about your mouse (USB, wireless dongle,
Bluetooth).

Try running xev and looking at the output. It reports each low-level
event including mouse-down and mouse-up. That way you can see if the
mouse itself is actually sending anything.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Mouse problems

2017-02-09 Thread Lawrence E Graves

I use the gnome-shell. Is that what you mean?


On 02/09/2017 06:21 AM, Ed Greshko wrote:

On 02/09/17 20:53, Lawrence E Graves wrote:

The double click option is not working on Fedora 25.



That option works just fine for me under F25/KDE.  Maybe you need to
inform folks of your environment?



--
All things are workable but don't all things work.
Prov. 3:5 & 6
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Mouse problems

2017-02-09 Thread Ed Greshko
On 02/09/17 20:53, Lawrence E Graves wrote:
> The double click option is not working on Fedora 25.
>
>
That option works just fine for me under F25/KDE.  Maybe you need to
inform folks of your environment?

-- 
Fedora Users List - The place to go to get others to do the work for you
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Mouse problems

2017-02-09 Thread Lawrence E Graves

The double click option is not working on Fedora 25.


--
All things are workable but don't all things work.
Prov. 3:5 & 6
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Fedora 24 Update: nitrokey-app-0.6.3-1.fc24

2017-02-09 Thread Joe Zeff

On 02/08/2017 11:56 PM, Tim wrote:

I wish that sort of useless description would result in packages getting
an automatic banning.


No, not banning.  There should be guidelines for what an acceptable 
description consists of, and any package that doesn't meet them should 
be rejected until it does.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org