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

[Tim]

Allegedly, on or about 07 February 2017, upda...@fedoraproject.org sent:
> Name: nitrokey-app
> Product : Fedora 24
> Version : 0.6.3
> Release : 1.fc24
> URL : https://github.com/Nitrokey/nitrokey-app
> Summary : Nitrokey's Application
> Description :
> Nitrokey's Application. 

I just picked the above at random, as an example of crapness.  There's
no end of notifications about updates that give no actual information.
You don't know what the update is about, you don't know what the
original package is for.  Likewise, when doing YUM searches, there are
packages with crap descriptions.

I wish that sort of useless description would result in packages getting
an automatic banning.  That and URIs that don't work, or lead to
similarly un-useful websites.  I've seen plenty of packages with links
that lead to some GITHUB kind of thing with zero information about what
the package actual does or is used for, and no links anywhere on the
page that lead to something else that might explain what it is.

Maybe then, the big stick approach, might force some sanity.

-- 
[tim@localhost ~]$ uname -rsvp
Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64

Boilerplate:  All mail to my mailbox is automatically deleted, there is
no point trying to privately email me, I only get to see the messages
posted to the mailing list.

If you are not the intended recipient, why are you reading their email?
You bastard!



-- 
[tim@localhost ~]$ uname -rsvp
Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64

Boilerplate:  All mail to my mailbox is automatically deleted, there is
no point trying to privately email me, I only get to see the messages
posted to the mailing list.

Evolution keeps on telling me that it's refreshing, but I still want to
go and get a drink.


___
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

[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.

Thanks Ed, I can try that.

What I am trying to understand is, given that from the documentation, 
the message reached Networkmanager-wait-online target means that all 
network devices are up and have an IP address, how can the wait-online 
process be satisfied, given its definition, if the only network device 
Networkmanager has been told it can use is still having its driver built 
and deployed to the kernel, plus at the moment the interface on the 
device it has been told to use is still not available at boot time until 
the desktop (KDE or GNOME) actually starts.
As a side issue to this, I have also compiled the driver through DKMS in 
Ubuntu, and I think the device is not available there at boot time until 
the display manager starts (in Fedora it is still not available at 
Display Manager time, the desktop has to be started from the Display 
Manager before it becomes available), but it is a bit hard to tell at 
the moment if it is available during boot because the Ubuntu boot 
process is significantly quicker than in Fedora, but it is still slower 
than windows startups (which are really hibernation starts).
Also I don't have the same mount specifications in /etc/fstab under 
Ubuntu that I do under Fedora. For example, to mount the Ubuntu 
partitions I have to have entries in /etc/fstab, but under Ubuntu I 
don't have to put entries in /etc/fstab to mount the Fedora partitions, 
they are mounted automatically to /media/$my-userid (I'm using 
$my-userid to indicate that directory is name according to the logged in 
User). What I have checked yet is whether that auto-mount process is 
mounting the nfs and cifs interfaces on the network device).


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

[poma]

On 07.02.2017 21:54, David A. De Graaf wrote:
> The r8712u driver from the staging area has stopped working in Fedora
> 25.  This driver supports (among others) my emergency USB DLink DWA-130
> adapter that I use when the laptop's built in wireless (Qualcomm
> Atheros QCA9377 802.11ac) is "too advanced" to connect to some old
> wireless router.
> 
> The r8712u driver works just fine in Fedora 24 and it seems to be
> substantially unchanged.
> 
> I ran 'modinfo r8712u' on both F24 and F25 and diff'd them.
> The only differences are in the filesystem locations and labelling.
> There was no other substantial difference.
> 
> I've monitored dmesg while plugging the DLink adapter in and it's
> apparent that
> 1 - it is detected with proper vendor and product IDs.
> 2 - the r8712u module is selected and registered.
> 3 - the correct firmware is loaded from rtlwifi/rtl8712u.bin
> 4 - an endless stream of messages ensues:
> [  262.524809] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
> and, of course, the new interface never becomes available to
> NetworkManager.
> 
> 
> What's gone wrong?
> Why does the same driver work in Fedora 24 but not in Fedora 25?
> How do I regain operability?
> 
> 


You can try the following two options:

- Disable Pre-association / Scanning random MAC address;

/etc/NetworkManager/NetworkManager.conf
...
[device]
# default:
# wifi.scan-rand-mac-address=yes
# See 'man 5 NetworkManager.conf'
# 
https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0
# Disable Pre-association / Scanning random MAC address for r8712u WEXT driver,
# it breaks wpa_supplicant
wifi.scan-rand-mac-address=no

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;

$ git clone https://github.com/chunkeey/rtl8192su.git
$ cd rtl8192su/
$ make -f Makefile.r92su 
$ su

# echo "blacklist r8712u" >> /etc/modprobe.d/wifi-blacklist.conf
# systemctl stop NetworkManager.service
# modprobe -rv r8712u

# cp r92su/r92su.ko /lib/modules/$(uname -r)/updates
# depmod 
# modinfo r92su
# modprobe -v r92su
# systemctl start NetworkManager.service
# exit

$ nm-connection-editor


Tested with:
kernel-4.9.8-1001.fc24.x86_64
NetworkManager-1.7.1-0.4.20170207gitca5f915.fc24.x86_64
nm-connection-editor-1.4.5-0.4.20170207gitd898ecf.fc24.x86_64
iperf-2.0.8-6.fc24.x86_64


  = Throughput Test =

RTL8188SU 802.11n WLAN Adapter
  
 AP(Wi-Fi == bridge == 100Mbit switch)
  
 SERVER

Server mode:
$ iperf -s -i 1

Server listening on TCP port 5001
TCP window size: 85.3 KByte (default)

[  4] local  port 5001 connected with  port 47460
[ ID] Interval   Transfer Bandwidth
[  4]  0.0- 1.0 sec  9.10 MBytes  76.3 Mbits/sec
[  4]  1.0- 2.0 sec  10.4 MBytes  87.0 Mbits/sec
[  4]  2.0- 3.0 sec  10.3 MBytes  86.4 Mbits/sec
[  4]  3.0- 4.0 sec  9.78 MBytes  82.0 Mbits/sec
[  4]  4.0- 5.0 sec  9.78 MBytes  82.0 Mbits/sec
[  4]  5.0- 6.0 sec  9.87 MBytes  82.8 Mbits/sec
[  4]  6.0- 7.0 sec  9.74 MBytes  81.7 Mbits/sec
[  4]  7.0- 8.0 sec  9.85 MBytes  82.6 Mbits/sec
[  4]  8.0- 9.0 sec  9.62 MBytes  80.7 Mbits/sec
[  4]  9.0-10.0 sec  9.14 MBytes  76.7 Mbits/sec
[  4]  0.0-10.1 sec  98.4 MBytes  81.7 Mbits/sec



Client mode:
$ iperf -c  -i 1

Client connecting to , TCP port 5001
TCP window size: 85.0 KByte (default)

[  3] local  port 47460 connected with  port 5001
[ ID] Interval   Transfer Bandwidth
[  3]  0.0- 1.0 sec  9.50 MBytes  79.7 Mbits/sec
[  3]  1.0- 2.0 sec  10.4 MBytes  87.0 Mbits/sec
[  3]  2.0- 3.0 sec  10.4 MBytes  87.0 Mbits/sec
[  3]  3.0- 4.0 sec  9.75 MBytes  81.8 Mbits/sec
[  3]  4.0- 5.0 sec  9.88 MBytes  82.8 Mbits/sec
[  3]  5.0- 6.0 sec  9.75 MBytes  81.8 Mbits/sec
[  3]  6.0- 7.0 sec  9.62 MBytes  80.7 Mbits/sec
[  3]  7.0- 8.0 sec  10.1 MBytes  84.9 Mbits/sec
[  3]  8.0- 9.0 sec  9.38 MBytes  78.6 Mbits/sec
[  3]  9.0-10.0 sec  9.62 MBytes  80.7 Mbits/sec
[  3]  0.0-10.0 sec  98.4 MBytes  82.3 Mbits/sec
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: [OT] - mail.google.com - FYI

[Tim]

Allegedly, on or about 07 February 2017, JD sent:
> I open firefox for 2 different profiles with the command:
> /usr/bin/firefox -P -no-remote %u
> 
> In each profile A, I login to my one gmail account
> and in second profile I login to my other gmail account.
> 
> Attempting to login to 2nd account fails because I am not granted
> the same login screen where you enter you email address, and then
> prompted for the password. Instead, you can only creat a new pay-for-it
> account.

That command line doesn't suggest to me that you're using two different
profiles.

What if you use two completely different browsers, that wouldn't be
talking to each other in any way?  Would that give you the chance to log
in separately?

The other thing that occurs to me is whether you're going through a
proxy, perhaps a transparent one.  It might not have the nous to keep
two connections from the same IP isolated.

-- 
[tim@localhost ~]$ uname -rsvp
Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64

Boilerplate:  All mail to my mailbox is automatically deleted, there is
no point trying to privately email me, I only get to see the messages
posted to the mailing list.

Damn, I didn't mean to press *that* button!


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

Re: Fedora on Lenovo Yoga Book?

[Jeandet Alexis]

HI,
I bought one today, I took the Android version.(Much cheaper, 100€ l
ess)Few observations first: -No regular size USB, it's micro USB
(OTG or HOST capable)   -No regular BIOS/EFI menu just android
boot menuFor 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.fedorapro
> > > > > > ject.org
> > > > > >  > > > > > >
> > > > > > 
> > > > > > 
> > > > > 
> > > > > ___
> > > > > users mailing list -- users@lists.fedoraproject.org
> > > > > 
> > > > >  > > > > >
> > > > > To unsubscribe send an email to users-leave@lists.fedoraproje
> > > > > ct.org
> > > > >  > > > > >
> > > > 
> > > > ___
> > > > users mailing list -- users@lists.fedoraproject.org
> > > > 
> > > > To unsubscribe send an email to users-leave@lists.fedoraproject
> > > > .org
> > > > 
> > > > 
> > 
> > ___
> > 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 

Re: r8712u driver fails in F25

[David A. De Graaf]

On 02/07/17 16:09, Rick Stevens wrote:

On 02/07/2017 12:54 PM, David A. De Graaf wrote:

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

I've monitored dmesg while plugging the DLink adapter in and it's
apparent that
1 - it is detected with proper vendor and product IDs.
2 - the r8712u module is selected and registered.
3 - the correct firmware is loaded from rtlwifi/rtl8712u.bin
4 - an endless stream of messages ensues:
[  262.524809] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
and, of course, the new interface never becomes available to
NetworkManager.


What's gone wrong?
Why does the same driver work in Fedora 24 but not in Fedora 25?
How do I regain operability?


Disable IPV6 in NM? The message you're getting is IPV6-specific and
that may be causing NM issues (it keeps waiting on a valid IPV6 address
to become available, never does, and NM keeps waiting).

That's just a guess.
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
-   When in doubt, mumble.   -
--


Thank you, Rick Stevens, for your very rational guess.

However, I'm at a loss how exactly to disable ipv6 in NetworkManager
because NetworkManager has not yet recognized the new interface for
the freshly plugged in DLink USB adapter.  That is, there's no ifcfg-*
file in /etc/sysconfig/network-scripts.  In fact, there is no file
anywhere in that directory tree that contains the MAC address of the
adapter.  So it appears that NetworkManager doesn't come into the
picture until AFTER  determines that the 'link is ready'.

In my retained /f24 filesystem there are several ifcfg-* files that
do contain that MAC address and had been used while Fedora 24 was
active.  I copied one to the F25 filesystem.  That was insufficient for
NetworkManager to see it and allow editing it.  However, after 
restarting NetworkManager, that new Network Connection became listed as 
editable when I right-clicked on the nm-applet icon.


First, I used it unaltered - because it had worked perfectly in F24 -
eg, I simply plugged in the DLink USB adapter and watched 'dmesg -w'.
Second, I clicked on nm-applet and graphically edited that Network
Connection to set ipv6 settings to "Ignore".
Third, I manually edited the original ifcfg file to disable all the
ipv6 settings.

The output of dmesg was the same for all three cases.
There was NO CHANGE.  To be specific and complete, here's the dmesg
output:

[82189.094547] usb 1-4: new high-speed USB device number 7 using xhci_hcd
[82189.265676] usb 1-4: New USB device found, idVendor=07d1, idProduct=3300
[82189.265686] usb 1-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3

[82189.265692] usb 1-4: Product: 11n Adapter
[82189.265697] usb 1-4: Manufacturer: Manufacturer Realtek
[82189.265702] usb 1-4: SerialNumber: 00e04c01
[82189.269827] r8712u: register rtl8712_netdev_ops to netdev_ops
[82189.269839] usb 1-4: r8712u: USB_SPEED_HIGH with 4 endpoints
[82189.271387] usb 1-4: r8712u: Boot from EFUSE: Autoload OK
[82189.635092] usb 1-4: r8712u: CustomerID = 0x0006
[82189.635100] usb 1-4: r8712u: MAC Address from efuse = 28:10:7b:c2:09:ae
[82189.635105] usb 1-4: r8712u: Loading firmware from "rtlwifi/rtl8712u.bin"
[82189.686494] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[82190.390956] r8712u 1-4:1.0 wlan1: 1 RCR=0x153f00e
[82190.391691] r8712u 1-4:1.0 wlan1: 2 RCR=0x553f00e
[82191.603127] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[82193.122927] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[82193.182252] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[82194.707205] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[82196.235123] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
   

So, the IPv6 error messages recur endlessly and the link remains not
ready.

I have two other computers with slightly unusual USB wireless adapters
that are also behaving badly with Fedora 25.  I will report these
observations when I've collected convincing data.

I cannot help but think there's a significant kernel bug...
Anyone with a plug-in USB wireless adapter should closely monitor its
behaviour.


--
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: bluetooth broken (?)

[Rick Stevens]

On 02/08/2017 01:58 AM, Frank Elsner wrote:
> Hi,
> 
> running Fedora 25 with kernel-PAE-4.9.5-200.fc25.i686
>bluez-libs-5.43-2.fc25.i686
>blueman-2.0.4-4.fc25.i686
>bluez-5.43-2.fc25.i686
>pulseaudio-module-bluetooth-10.0-2.fc25.i686
>bluez-obexd-5.43-2.fc25.i686
> 
> I cannot enable bluetooth. Clicking the bluetooth applet in my
> panel does nothing.
> 
> The log shows:
> Feb  8 10:54:09 siffux dbus-daemon[710]: [system] Activating service 
> name='org.blueman.Mechanism' requested by ':1.44' (uid=1953 pid=1178 
> comm="python3 /usr/bin/blueman-applet ") (using servicehelper)
> Feb  8 10:54:09 siffux org.blueman.Mechanism: Unable to init server: Could 
> not connect: Connection refused
> Feb  8 10:54:09 siffux org.blueman.Mechanism: Unable to init server: Could 
> not connect: Connection refused
> Feb  8 10:54:09 siffux blueman-mechanism: Starting blueman-mechanism
> Feb  8 10:54:09 siffux dbus-daemon[710]: [system] Successfully activated 
> service 'org.blueman.Mechanism'
> Feb  8 10:54:09 siffux journal: gtk_icon_theme_get_for_screen: assertion 
> 'GDK_IS_SCREEN (screen)' failed
> Feb  8 10:54:09 siffux blueman-mechanism: loading Ppp
> Feb  8 10:54:09 siffux blueman-mechanism: loading RfKill
> Feb  8 10:54:09 siffux blueman-mechanism: loading Network
> Feb  8 10:54:09 siffux blueman-mechanism: loading Rfcomm
> Feb  8 10:54:39 siffux blueman-mechanism: Exiting
> 
> How to make bluetooth working (again)?

Do you have bluetoothd running? Check by

systemctl status bluetooth.service

as root. If it's not running, as root:

systemctl start bluetooth.service
systemctl enable bluetooth.service

--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
- Real Time, adj.: Here and now, as opposed to fake time, which only -
-occurs there and then   -
--
___
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

[Rick Stevens]

On 02/08/2017 12:35 AM, Frédéric Bron wrote:
> Now that it works again:
> 
> $ traceroute www.google.com
> traceroute to www.google.com (216.58.198.68), 30 hops max, 60 byte packets
>  1  gateway (192.168.1.254)  0.864 ms  1.000 ms  0.956 ms
>  2  lyo-1-rdb.fr.eu (178.32.37.4)  32.095 ms  33.191 ms  35.603 ms
>  3  vl11.lyo-1-6k.fr.eu (178.32.37.166)  36.935 ms  36.905 ms  37.957 ms
>  4  be99-1144.gsw-1-a9.fr.eu (91.121.131.113)  45.495 ms  47.854 ms  49.063 ms
>  5  * * *
>  6  108.170.244.194 (108.170.244.194)  52.631 ms 108.170.244.195
> (108.170.244.195)  39.541 ms  38.504 ms
>  7  209.85.252.247 (209.85.252.247)  40.906 ms 108.170.232.19
> (108.170.232.19)  42.098 ms 209.85.252.247 (209.85.252.247)  43.179 ms
>  8  216.239.40.69 (216.239.40.69)  52.023 ms 209.85.240.136
> (209.85.240.136)  53.136 ms  54.239 ms
>  9  216.239.42.238 (216.239.42.238)  66.938 ms  69.968 ms  68.299 ms
> 10  64.233.174.27 (64.233.174.27)  66.753 ms  68.207 ms  69.739 ms
> 11  dub08s02-in-f68.1e100.net (216.58.198.68)  56.035 ms  56.047 ms  55.979 ms
> 
> $ host -v www.google.com
> Trying "www.google.com"
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26779
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
> 
> ;; QUESTION SECTION:
> ;www.google.com.IN  A
> 
> ;; ANSWER SECTION:
> www.google.com. 251 IN  A   216.58.198.68
> 
> Received 48 bytes from 91.121.161.184#53 in 42 ms
> Trying "www.google.com"
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26432
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
> 
> ;; QUESTION SECTION:
> ;www.google.com.IN  
> 
> ;; ANSWER SECTION:
> www.google.com. 249 IN  2a00:1450:400f:807::2004
> 
> Received 60 bytes from 91.121.161.184#53 in 42 ms
> Trying "www.google.com"
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26938
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
> 
> ;; QUESTION SECTION:
> ;www.google.com.IN  MX
> 
> ;; AUTHORITY SECTION:
> google.com. 56  IN  SOA ns3.google.com.
> dns-admin.google.com. 146876413 900 900 1800 60
> 
> Received 82 bytes from 91.121.161.184#53 in 42 ms
> 
> $ ping www.google.com
> PING www.google.com(arn09s11-in-x04.1e100.net
> (2a00:1450:400f:807::2004)) 56 data bytes
> 64 bytes from arn09s11-in-x04.1e100.net (2a00:1450:400f:807::2004):
> icmp_seq=1 ttl=48 time=82.3 ms
> 64 bytes from arn09s11-in-x04.1e100.net (2a00:1450:400f:807::2004):
> icmp_seq=2 ttl=48 time=81.0 ms
> 64 bytes from arn09s11-in-x04.1e100.net (2a00:1450:400f:807::2004):
> icmp_seq=3 ttl=48 time=81.1 ms
> 64 bytes from arn09s11-in-x04.1e100.net (2a00:1450:400f:807::2004):
> icmp_seq=4 ttl=48 time=79.8 ms
> 64 bytes from arn09s11-in-x04.1e100.net (2a00:1450:400f:807::2004):
> icmp_seq=5 ttl=48 time=81.4 ms

That's nice, but you didn't say what you did to "get it working again".
I'm assuming the DHCP lease wasn't complete--either you didn't get
a default route or a list of DNS servers.

As to a delay before things start working, that can happen if the
ARP table is corrupted. You have to wait for it to clear or force
a clear via something like "ip neigh flush dev eth0".

> 2017-02-08 9:31 GMT+01:00 Frédéric Bron :
>> This morning, here is what I have:
>> $ ping www.google.com
>> ping: www.google.com: Name or service not known
>>
>> $ traceroute www.google.com
>> www.google.com: Name or service not known
>> Cannot handle "host" cmdline arg `www.google.com' on position 1 (argc 1)
>>
>> $ host -v www.google.com
>> Trying "www.google.com"
>> ;; connection timed out; no servers could be reached
>>
>> But I can still connect to another computer connected to the same
>> internet box. By the way, same issue on this other computer (also same
>> F25).
>>
>> Sometimes, ping takes 20-30 s before showing something and then it
>> shows "normal" pings:
>> $ ping www.google.com
>> PING www.google.com (172.217.22.164) 56(84) bytes of data.
>> 64 bytes from arn09s11-in-f4.1e100.net (172.217.22.164): icmp_seq=1
>> ttl=50 time=69.1 ms
>> 64 bytes from arn09s11-in-f4.1e100.net (172.217.22.164): icmp_seq=2
>> ttl=50 time=69.8 ms
>> 64 bytes from arn09s11-in-f4.1e100.net (172.217.22.164): icmp_seq=3
>> ttl=50 time=69.1 ms
>> 64 bytes from arn09s11-in-f4.1e100.net (172.217.22.164): icmp_seq=4
>> ttl=50 time=69.2 ms
>> ...
> 
> 
> 


-- 
--
- 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 -- 

[389-users] Trac -> Pagure Migration this Friday (Feb 10)

[Mark Reynolds]

We are planning on doing the Trac to Pagure migration this Friday.  
Using Pagure is very similar to Trac, except you create "Issues" instead
of "tickets".

One change to keep in mind is that we now have separate projects for our
components like: admin server, 389-ds-console, idm-console-framework,
389-dsgw, 389-ds-base, etc.  These can all be found under the
Directory_Services group:

https://pagure.io/group/Directory_Services

If you have an Admin Server issue to report create a new issue under the
389-admin project, etc.

Please use the "389-ds-base" project for new Directory Server issues. 
Note, your previous tickets you filed, or are following, will still have
the same ticket number:

https://fedorahosted.org/389/ticket/48118

Will be:

https://pagure.io/389-ds-base/issue/48118

Once the migration is complete there will be a final announcement, and
Trac will be put into read-only mode until it is decommissioned.

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

bluetooth broken (?)

[Frank Elsner]

Hi,

running Fedora 25 with kernel-PAE-4.9.5-200.fc25.i686
   bluez-libs-5.43-2.fc25.i686
   blueman-2.0.4-4.fc25.i686
   bluez-5.43-2.fc25.i686
   pulseaudio-module-bluetooth-10.0-2.fc25.i686
   bluez-obexd-5.43-2.fc25.i686

I cannot enable bluetooth. Clicking the bluetooth applet in my
panel does nothing.

The log shows:
Feb  8 10:54:09 siffux dbus-daemon[710]: [system] Activating service 
name='org.blueman.Mechanism' requested by ':1.44' (uid=1953 pid=1178 
comm="python3 /usr/bin/blueman-applet ") (using servicehelper)
Feb  8 10:54:09 siffux org.blueman.Mechanism: Unable to init server: Could not 
connect: Connection refused
Feb  8 10:54:09 siffux org.blueman.Mechanism: Unable to init server: Could not 
connect: Connection refused
Feb  8 10:54:09 siffux blueman-mechanism: Starting blueman-mechanism
Feb  8 10:54:09 siffux dbus-daemon[710]: [system] Successfully activated 
service 'org.blueman.Mechanism'
Feb  8 10:54:09 siffux journal: gtk_icon_theme_get_for_screen: assertion 
'GDK_IS_SCREEN (screen)' failed
Feb  8 10:54:09 siffux blueman-mechanism: loading Ppp
Feb  8 10:54:09 siffux blueman-mechanism: loading RfKill
Feb  8 10:54:09 siffux blueman-mechanism: loading Network
Feb  8 10:54:09 siffux blueman-mechanism: loading Rfcomm
Feb  8 10:54:39 siffux blueman-mechanism: Exiting

How to make bluetooth working (again)?


--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

[Frédéric Bron]

Now that it works again:

$ traceroute www.google.com
traceroute to www.google.com (216.58.198.68), 30 hops max, 60 byte packets
 1  gateway (192.168.1.254)  0.864 ms  1.000 ms  0.956 ms
 2  lyo-1-rdb.fr.eu (178.32.37.4)  32.095 ms  33.191 ms  35.603 ms
 3  vl11.lyo-1-6k.fr.eu (178.32.37.166)  36.935 ms  36.905 ms  37.957 ms
 4  be99-1144.gsw-1-a9.fr.eu (91.121.131.113)  45.495 ms  47.854 ms  49.063 ms
 5  * * *
 6  108.170.244.194 (108.170.244.194)  52.631 ms 108.170.244.195
(108.170.244.195)  39.541 ms  38.504 ms
 7  209.85.252.247 (209.85.252.247)  40.906 ms 108.170.232.19
(108.170.232.19)  42.098 ms 209.85.252.247 (209.85.252.247)  43.179 ms
 8  216.239.40.69 (216.239.40.69)  52.023 ms 209.85.240.136
(209.85.240.136)  53.136 ms  54.239 ms
 9  216.239.42.238 (216.239.42.238)  66.938 ms  69.968 ms  68.299 ms
10  64.233.174.27 (64.233.174.27)  66.753 ms  68.207 ms  69.739 ms
11  dub08s02-in-f68.1e100.net (216.58.198.68)  56.035 ms  56.047 ms  55.979 ms

$ host -v www.google.com
Trying "www.google.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26779
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.google.com.IN  A

;; ANSWER SECTION:
www.google.com. 251 IN  A   216.58.198.68

Received 48 bytes from 91.121.161.184#53 in 42 ms
Trying "www.google.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26432
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.google.com.IN  

;; ANSWER SECTION:
www.google.com. 249 IN  2a00:1450:400f:807::2004

Received 60 bytes from 91.121.161.184#53 in 42 ms
Trying "www.google.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26938
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;www.google.com.IN  MX

;; AUTHORITY SECTION:
google.com. 56  IN  SOA ns3.google.com.
dns-admin.google.com. 146876413 900 900 1800 60

Received 82 bytes from 91.121.161.184#53 in 42 ms

$ ping www.google.com
PING www.google.com(arn09s11-in-x04.1e100.net
(2a00:1450:400f:807::2004)) 56 data bytes
64 bytes from arn09s11-in-x04.1e100.net (2a00:1450:400f:807::2004):
icmp_seq=1 ttl=48 time=82.3 ms
64 bytes from arn09s11-in-x04.1e100.net (2a00:1450:400f:807::2004):
icmp_seq=2 ttl=48 time=81.0 ms
64 bytes from arn09s11-in-x04.1e100.net (2a00:1450:400f:807::2004):
icmp_seq=3 ttl=48 time=81.1 ms
64 bytes from arn09s11-in-x04.1e100.net (2a00:1450:400f:807::2004):
icmp_seq=4 ttl=48 time=79.8 ms
64 bytes from arn09s11-in-x04.1e100.net (2a00:1450:400f:807::2004):
icmp_seq=5 ttl=48 time=81.4 ms



2017-02-08 9:31 GMT+01:00 Frédéric Bron :
> This morning, here is what I have:
> $ ping www.google.com
> ping: www.google.com: Name or service not known
>
> $ traceroute www.google.com
> www.google.com: Name or service not known
> Cannot handle "host" cmdline arg `www.google.com' on position 1 (argc 1)
>
> $ host -v www.google.com
> Trying "www.google.com"
> ;; connection timed out; no servers could be reached
>
> But I can still connect to another computer connected to the same
> internet box. By the way, same issue on this other computer (also same
> F25).
>
> Sometimes, ping takes 20-30 s before showing something and then it
> shows "normal" pings:
> $ ping www.google.com
> PING www.google.com (172.217.22.164) 56(84) bytes of data.
> 64 bytes from arn09s11-in-f4.1e100.net (172.217.22.164): icmp_seq=1
> ttl=50 time=69.1 ms
> 64 bytes from arn09s11-in-f4.1e100.net (172.217.22.164): icmp_seq=2
> ttl=50 time=69.8 ms
> 64 bytes from arn09s11-in-f4.1e100.net (172.217.22.164): icmp_seq=3
> ttl=50 time=69.1 ms
> 64 bytes from arn09s11-in-f4.1e100.net (172.217.22.164): icmp_seq=4
> ttl=50 time=69.2 ms
> ...



-- 
Frédéric Bron

---
Frédéric Bron (frederic.b...@m4x.org)
Villa des 4 chemins, Centre Hospitalier, BP 208
38506 Voiron Cedex
tél. fixe : +33 4 76 67 17 27, tél. port.: +33 6 67 02 77 35
___
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

[Frédéric Bron]

This morning, here is what I have:
$ ping www.google.com
ping: www.google.com: Name or service not known

$ traceroute www.google.com
www.google.com: Name or service not known
Cannot handle "host" cmdline arg `www.google.com' on position 1 (argc 1)

$ host -v www.google.com
Trying "www.google.com"
;; connection timed out; no servers could be reached

But I can still connect to another computer connected to the same
internet box. By the way, same issue on this other computer (also same
F25).

Sometimes, ping takes 20-30 s before showing something and then it
shows "normal" pings:
$ ping www.google.com
PING www.google.com (172.217.22.164) 56(84) bytes of data.
64 bytes from arn09s11-in-f4.1e100.net (172.217.22.164): icmp_seq=1
ttl=50 time=69.1 ms
64 bytes from arn09s11-in-f4.1e100.net (172.217.22.164): icmp_seq=2
ttl=50 time=69.8 ms
64 bytes from arn09s11-in-f4.1e100.net (172.217.22.164): icmp_seq=3
ttl=50 time=69.1 ms
64 bytes from arn09s11-in-f4.1e100.net (172.217.22.164): icmp_seq=4
ttl=50 time=69.2 ms
...
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org