[Desktop-packages] [Bug 1728862] [NEW] ping waits forever with -W flag

[atimonin]

Public bug reported:


 ping -c 3 -n -W 0.3 -i 0.3 10.70.14.48
doesn't finish (hangs until ctrl-c):

PING 10.70.14.48 (10.70.14.48) 56(84) bytes of data.
>From 10.70.14.7 icmp_seq=1 Destination Host Unreachable
^C


while
 ping -c 3 -n -i 0.3 10.70.14.48
finished succesfully:

PING 10.70.14.48 (10.70.14.48) 56(84) bytes of data.
>From 10.70.14.7 icmp_seq=1 Destination Host Unreachable

--- 10.70.14.48 ping statistics ---
3 packets transmitted, 0 received, +1 errors, 100% packet loss, time 641ms
pipe 3


Version:
ping -V
ping utility, iputils-s20160308

** Affects: iputils (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to iputils in Ubuntu.
https://bugs.launchpad.net/bugs/1728862

Title:
  ping waits forever with -W flag

Status in iputils package in Ubuntu:
  New

Bug description:

   ping -c 3 -n -W 0.3 -i 0.3 10.70.14.48
  doesn't finish (hangs until ctrl-c):

  PING 10.70.14.48 (10.70.14.48) 56(84) bytes of data.
  From 10.70.14.7 icmp_seq=1 Destination Host Unreachable
  ^C

  
  while
   ping -c 3 -n -i 0.3 10.70.14.48
  finished succesfully:

  PING 10.70.14.48 (10.70.14.48) 56(84) bytes of data.
  From 10.70.14.7 icmp_seq=1 Destination Host Unreachable

  --- 10.70.14.48 ping statistics ---
  3 packets transmitted, 0 received, +1 errors, 100% packet loss, time 641ms
  pipe 3

  
  Version:
  ping -V
  ping utility, iputils-s20160308

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1728862/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 175316] Re: no IDN in nslookup and host

[atimonin]

I also vote for this.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to iputils in Ubuntu.
https://bugs.launchpad.net/bugs/175316

Title:
  no IDN in nslookup and host

Status in BIND:
  New
Status in bind9 package in Ubuntu:
  Confirmed
Status in iputils package in Ubuntu:
  Confirmed
Status in bind9 package in Debian:
  New

Bug description:
  Binary package hint: bind9

  Neither nslookup or host supports IDN. If you try , for example, to
  get the IP for "registrera-domän.se" it fails every time. As the use
  of IDN is increasing I think it would be a good thing if these tools
  supported this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bind/+bug/175316/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1244548] Re: Keyboard shortcut for changing keyboard layout does not work on lock and login screen

[atimonin]

Confirm!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1244548

Title:
  Keyboard shortcut for changing keyboard layout does not work on lock
  and login screen

Status in GNOME Screensaver:
  New
Status in gnome-screensaver package in Ubuntu:
  Confirmed

Bug description:
  Shortcut for changing keyboard layout does not work on lock screen (to
  change keyboard layout for entering password).

  - Switch to some non-english layout (otherwise lock screen will not have 
layout indicator at all)
  - Lock the screen
  - Press your shortcut for changing keyboard layout (i.e. ctrl+shift) -- it 
will not change layout
  - Clicking layout indicator near password entry box works
  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-screensaver 3.6.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Fri Oct 25 11:01:10 2013
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session idle-delay uint32 300
   org.gnome.desktop.session session-name 'ubuntu'
  InstallationDate: Installed on 2013-10-23 (1 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-screensaver/+bug/1244548/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1290310] Re: nautilus does not start

[atimonin]

I've found a workaround: umount all  GVFS remote mounts
gvfs-mount -s sftp && gvfs-mount -s smb && gvfs-mount -s ftp

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1290310

Title:
  nautilus does not start

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  I tried to launch nautilus but it did not start so i tried from alt+f2
  and terminal but it did not start I got following message


  j0053@j0053-hp-probook-4420s:~$ nautilus
  Could not register the application: Timeout was reached

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Mon Mar 10 14:42:18 2014
  GsettingsChanges:
   b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 
'size', 'type', 'date_modified', 'where']"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'group', 'where', 'mime_type', 'owner', 'permissions']"
  InstallationDate: Installed on 2012-03-24 (715 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120324)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to trusty on 2014-01-30 (39 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1290310/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1431179] Re: usb_modeswitch@.service fails

[atimonin]

BTW,
usb_modeswitch@3-3-3-3:1.0.service seems to me erroneus
The propper should look like 
usb_modeswitch@3-3:1.0.service

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1431179

Title:
  usb_modeswitch@.service fails

Status in usb-modeswitch package in Ubuntu:
  Fix Released

Bug description:
  I lack the technical knowledge to know if this is a bug in udev,
  systemd or another component.

  After the switch to systemd, my 4G Huawei USB modem  no longer
  functions as a modem unless I run usb_modeswitch to flip its state
  from USB mass storage. The command I issue and its output is below,
  which also show the Vendor and Product ID.

  Strangely, it does not do this every time. Yesterday when I updated
  using apt-get dist-upgrade upon reboot the modem worked as expected.
  But from a cold boot this morning it did not.

  $ sudo usb_modeswitch -v 0x12d1 -p 0x1f01 -J
  [sudo] password for damon: 
  Look for default devices ...
 product ID matched
   Found devices in default mode (1)
  Access device 003 on bus 003
  Current configuration number is 1
  Use interface number 0
  Use endpoints 0x01 (out) and 0x81 (in)

  USB description data (for identification)
  -
  Manufacturer: HUAWEI Technology
   Product: HUAWEI Mobile
Serial No.: 
  -
  Using standard Huawei switching message
  Looking for active driver ...
   OK, driver detached
  Set up interface 0
  Use endpoint 0x01 for message sending ...
  Trying to send message 1 to endpoint 0x01 ...
   OK, message successfully sent
  Reset response endpoint 0x81
   Could not reset endpoint (probably harmless): -99
  Reset message endpoint 0x01
   Could not reset endpoint (probably harmless): -99
   Device is gone, skip any further commands
  - Run lsusb to note any changes. Bye!

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udev 219-4ubuntu5
  ProcVersionSignature: Ubuntu 3.19.0-8.8-generic 3.19.1
  Uname: Linux 3.19.0-8-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  CustomUdevRuleFiles: 60-ssd-scheduler.rules
  Date: Thu Mar 12 11:37:06 2015
  InstallationDate: Installed on 2015-02-05 (34 days ago)
  InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20150205)
  MachineType: LENOVO 427637U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-8-generic 
root=UUID=eb18ef51-a2d0-4372-8eb9-ae009a05d4f6 ro quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8BET62WW (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 427637U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8BET62WW(1.42):bd07/26/2013:svnLENOVO:pn427637U:pvrThinkPadW520:rvnLENOVO:rn427637U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 427637U
  dmi.product.version: ThinkPad W520
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1431179/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1431179] Re: usb_modeswitch@.service fails

[atimonin]

Still not working with Huawei E3372:

Jul 30 16:35:11 m-api2 kernel: [ 1472.901499] usb 3-3: new high-speed USB 
device number 4 using ehci-pci
Jul 30 16:35:11 m-api2 kernel: [ 1473.034553] usb 3-3: New USB device found, 
idVendor=12d1, idProduct=1f01
Jul 30 16:35:11 m-api2 kernel: [ 1473.034564] usb 3-3: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
Jul 30 16:35:11 m-api2 kernel: [ 1473.034569] usb 3-3: Product: HUAWEI_MOBILE
Jul 30 16:35:11 m-api2 kernel: [ 1473.034573] usb 3-3: Manufacturer: 
HUAWEI_MOBILE
Jul 30 16:35:11 m-api2 kernel: [ 1473.034577] usb 3-3: SerialNumber: 
0123456789ABCDEF
Jul 30 16:35:11 m-api2 kernel: [ 1473.035513] usb-storage 3-3:1.0: USB Mass 
Storage device detected
Jul 30 16:35:11 m-api2 kernel: [ 1473.038949] scsi host8: usb-storage 3-3:1.0
Jul 30 16:35:11 m-api2 systemd[1]: Starting USB_ModeSwitch...
Jul 30 16:35:11 m-api2 systemd[1]: usb_modeswitch@3-3-3-3:1.0.service: main 
process exited, code=exited, status=1/FAILURE
Jul 30 16:35:11 m-api2 systemd[1]: Failed to start USB_ModeSwitch.
Jul 30 16:35:11 m-api2 systemd[1]: Unit usb_modeswitch@3-3-3-3:1.0.service 
entered failed state.
Jul 30 16:35:11 m-api2 systemd[1]: usb_modeswitch@3-3-3-3:1.0.service failed.
Jul 30 16:35:12 m-api2 kernel: [ 1474.037905] scsi 8:0:0:0: CD-ROM
HUAWEI   Mass Storage 2.31 PQ: 0 ANSI: 2
Jul 30 16:35:12 m-api2 kernel: [ 1474.038365] scsi 8:0:0:1: Direct-Access 
HUAWEI   TF CARD Storage  2.31 PQ: 0 ANSI: 2
Jul 30 16:35:12 m-api2 kernel: [ 1474.044459] sr 8:0:0:0: [sr0] scsi-1 drive
Jul 30 16:35:12 m-api2 kernel: [ 1474.045757] sr 8:0:0:0: Attached scsi CD-ROM 
sr0
Jul 30 16:35:12 m-api2 kernel: [ 1474.045987] sr 8:0:0:0: Attached scsi generic 
sg1 type 5
Jul 30 16:35:12 m-api2 kernel: [ 1474.046975] sd 8:0:0:1: Attached scsi generic 
sg2 type 0
Jul 30 16:35:12 m-api2 kernel: [ 1474.053341] sd 8:0:0:1: [sdb] Attached SCSI 
removable disk
Jul 30 16:35:12 m-api2 systemd-udevd[258]: error: /dev/sdb: No medium found
Jul 30 16:35:12 m-api2 kernel: [ 1474.763724] sr 8:0:0:0: [sr0] FAILED Result: 
hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 30 16:35:12 m-api2 kernel: [ 1474.763746] sr 8:0:0:0: [sr0] Sense Key : 
Medium Error [current]
Jul 30 16:35:12 m-api2 kernel: [ 1474.763757] sr 8:0:0:0: [sr0] Add. Sense: 
Unrecovered read error
Jul 30 16:35:12 m-api2 kernel: [ 1474.763765] sr 8:0:0:0: [sr0] CDB: 
Jul 30 16:35:12 m-api2 kernel: [ 1474.763772] Read(10): 28 00 00 00 0f fe 00 00 
02 00
Jul 30 16:35:12 m-api2 kernel: [ 1474.763798] blk_update_request: critical 
medium error, dev sr0, sector 16376
Jul 30 16:35:12 m-api2 kernel: [ 1474.774706] sr 8:0:0:0: [sr0] FAILED Result: 
hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 30 16:35:12 m-api2 kernel: [ 1474.774721] sr 8:0:0:0: [sr0] Sense Key : 
Medium Error [current]
Jul 30 16:35:12 m-api2 kernel: [ 1474.774727] sr 8:0:0:0: [sr0] Add. Sense: 
Unrecovered read error
Jul 30 16:35:12 m-api2 kernel: [ 1474.774730] sr 8:0:0:0: [sr0] CDB: 
Jul 30 16:35:12 m-api2 kernel: [ 1474.774735] Read(10): 28 00 00 00 0f fe 00 00 
02 00
Jul 30 16:35:12 m-api2 kernel: [ 1474.774749] blk_update_request: critical 
medium error, dev sr0, sector 16376
Jul 30 16:35:12 m-api2 kernel: [ 1474.774838] Buffer I/O error on dev sr0, 
logical block 2047, async page read
Jul 30 16:35:13 m-api2 kernel: [ 1474.857014] sr 8:0:0:0: [sr0] FAILED Result: 
hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 30 16:35:13 m-api2 kernel: [ 1474.857036] sr 8:0:0:0: [sr0] Sense Key : 
Medium Error [current]
Jul 30 16:35:13 m-api2 kernel: [ 1474.857047] sr 8:0:0:0: [sr0] Add. Sense: 
Unrecovered read error
Jul 30 16:35:13 m-api2 kernel: [ 1474.857054] sr 8:0:0:0: [sr0] CDB: 
Jul 30 16:35:13 m-api2 kernel: [ 1474.857062] Read(10): 28 00 00 00 0f fc 00 00 
02 00
Jul 30 16:35:13 m-api2 kernel: [ 1474.857089] blk_update_request: critical 
medium error, dev sr0, sector 16368
Jul 30 16:35:13 m-api2 kernel: [ 1474.858249] sr 8:0:0:0: [sr0] FAILED Result: 
hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 30 16:35:13 m-api2 kernel: [ 1474.858260] sr 8:0:0:0: [sr0] Sense Key : 
Medium Error [current]
Jul 30 16:35:13 m-api2 kernel: [ 1474.858269] sr 8:0:0:0: [sr0] Add. Sense: 
Unrecovered read error
Jul 30 16:35:13 m-api2 kernel: [ 1474.858276] sr 8:0:0:0: [sr0] CDB: 
Jul 30 16:35:13 m-api2 kernel: [ 1474.858280] Read(10): 28 00 00 00 0f fc 00 00 
02 00
Jul 30 16:35:13 m-api2 kernel: [ 1474.858303] blk_update_request: critical 
medium error, dev sr0, sector 16368
Jul 30 16:35:13 m-api2 kernel: [ 1474.858447] Buffer I/O error on dev sr0, 
logical block 2046, async page read


But manually calling usb_modeswitch works:

root@m-api2:~# usb_modeswitch -v 0x12d1 -p 0x1f01 -J
Look for default devices ...
   product ID matched
 Found devices in default mode (1)
Access device 004 on bus 003
Current configuration number is 1
Use interface number 0
Use endpoints 0x01 (out) and 0x81 (in)

USB description data (for identification)
-
Manufacturer: HUAWEI_MOBILE
 Product: HUAWEI_MOBILE

[Desktop-packages] [Bug 1431179] Re: usb_modeswitch@.service fails

[atimonin]

usb-modeswitch version^
root@m-api2:~# dpkg -s usb-modeswitch
Package: usb-modeswitch
Status: install ok installed
Priority: extra
Section: comm
Installed-Size: 202
Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com
Architecture: amd64
Version: 2.2.0+repack0-2ubuntu2
Depends: libc6 (= 2.14), libpipeline1 (= 1.0.0), libusb-1.0-0 (= 2:1.0.8), 
usb-modeswitch-data (= 20140529)
Suggests: comgt, wvdial
Breaks: usb-modeswitch-data ( 20100127)
Conffiles:
 /etc/init/usb-modeswitch-upstart.conf 8972963f876f7717c4c0f267de97b278
 /etc/usb_modeswitch.conf b8fcd7f4e9e0173139b36cb56469377f
Description: mode switching tool for controlling flip flop USB devices
 Several new USB devices have their proprietary Windows drivers onboard,
 especially WAN dongles. When plugged in for the first time, they act
 like a flash storage and start installing the driver from there. If
 the driver is already installed, the storage device vanishes and
 a new device, such as an USB modem, shows up. This is called the
 ZeroCD feature.
 .
 On Debian, this is not needed, since the driver is included as a
 Linux kernel module, such as usbserial. However, the device still
 shows up as usb-storage by default. usb-modeswitch solves that
 issue by sending the command which actually performs the switching
 of the device from usb-storage to usbserial.
 .
 This package contains the binaries and the brother scripts.
Homepage: http://www.draisberghof.de/usb_modeswitch/
Original-Maintainer: Didier Raboud o...@debian.org

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1431179

Title:
  usb_modeswitch@.service fails

Status in usb-modeswitch package in Ubuntu:
  Fix Released

Bug description:
  I lack the technical knowledge to know if this is a bug in udev,
  systemd or another component.

  After the switch to systemd, my 4G Huawei USB modem  no longer
  functions as a modem unless I run usb_modeswitch to flip its state
  from USB mass storage. The command I issue and its output is below,
  which also show the Vendor and Product ID.

  Strangely, it does not do this every time. Yesterday when I updated
  using apt-get dist-upgrade upon reboot the modem worked as expected.
  But from a cold boot this morning it did not.

  $ sudo usb_modeswitch -v 0x12d1 -p 0x1f01 -J
  [sudo] password for damon: 
  Look for default devices ...
 product ID matched
   Found devices in default mode (1)
  Access device 003 on bus 003
  Current configuration number is 1
  Use interface number 0
  Use endpoints 0x01 (out) and 0x81 (in)

  USB description data (for identification)
  -
  Manufacturer: HUAWEI Technology
   Product: HUAWEI Mobile
Serial No.: 
  -
  Using standard Huawei switching message
  Looking for active driver ...
   OK, driver detached
  Set up interface 0
  Use endpoint 0x01 for message sending ...
  Trying to send message 1 to endpoint 0x01 ...
   OK, message successfully sent
  Reset response endpoint 0x81
   Could not reset endpoint (probably harmless): -99
  Reset message endpoint 0x01
   Could not reset endpoint (probably harmless): -99
   Device is gone, skip any further commands
  - Run lsusb to note any changes. Bye!

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udev 219-4ubuntu5
  ProcVersionSignature: Ubuntu 3.19.0-8.8-generic 3.19.1
  Uname: Linux 3.19.0-8-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  CustomUdevRuleFiles: 60-ssd-scheduler.rules
  Date: Thu Mar 12 11:37:06 2015
  InstallationDate: Installed on 2015-02-05 (34 days ago)
  InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20150205)
  MachineType: LENOVO 427637U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-8-generic 
root=UUID=eb18ef51-a2d0-4372-8eb9-ae009a05d4f6 ro quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8BET62WW (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 427637U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8BET62WW(1.42):bd07/26/2013:svnLENOVO:pn427637U:pvrThinkPadW520:rvnLENOVO:rn427637U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 427637U
  dmi.product.version: ThinkPad W520
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1431179/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   

[Desktop-packages] [Bug 1103064] Re: power indicator shows Logitech wireless keyboard and mouse batteries with 0%

[atimonin]

I have a similar problem:
1. before recent update mouse power indicator always show a low power (red), 
but mouse works
2. after a recent update mouse power indicator looks OK, but mouse move is not 
working.

# upower --dump
[some text skipped]
Device: /org/freedesktop/UPower/devices/mouse_hid_00o60od1o02o31o61_battery
  native-path:  hid-00:60:d1:02:31:61-battery
  model:Bluetooth Mouse
  power supply: no
  updated:  Пн. 15 дек. 2014 12:31:35 (0 seconds ago)
  has history:  yes
  has statistics:   yes
  mouse
present: yes
rechargeable:yes
state:   discharging
percentage:  100%

Daemon:
  daemon-version:  0.9.23
  can-suspend: yes
  can-hibernate:   yes
  on-battery:  no
  on-low-battery:  no
  lid-is-closed:   no
  lid-is-present:  yes
  is-docked:   yes

uname -a
 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 x86_64 x86_64 
x86_64 GNU/Linux

# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.1 LTS
Release:14.04
Codename:   trusty

Sometimes after mouse switching off and on it is working for a couple of
seconds and then stops

#grep -r . /sys/class/power_supply/*hid*
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/type:Battery
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/power/control:auto
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/power/async:disabled
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/power/wakeup_abort_count:0
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/power/wakeup_active:0
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/power/wakeup_total_time_ms:35
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/power/wakeup_active_count:1
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/power/runtime_enabled:disabled
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/power/runtime_active_kids:0
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/power/runtime_active_time:0
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/power/wakeup_max_time_ms:35
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/power/wakeup_count:1
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/power/wakeup_last_time_ms:11561014
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/power/wakeup:enabled
grep: 
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/power/autosuspend_delay_ms:
 Input/output error
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/power/runtime_status:unsupported
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/power/runtime_usage:0
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/power/wakeup_expire_count:0
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/power/runtime_suspended_time:0
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/scope:Device
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/capacity:97
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/online:1
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/status:Discharging
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/uevent:POWER_SUPPLY_NAME=hid-00:60:d1:02:31:61-battery
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/uevent:POWER_SUPPLY_PRESENT=1
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/uevent:POWER_SUPPLY_ONLINE=1
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/uevent:POWER_SUPPLY_CAPACITY=97
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/uevent:POWER_SUPPLY_MODEL_NAME=Bluetooth
 Mouse
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/uevent:POWER_SUPPLY_STATUS=Discharging
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/uevent:POWER_SUPPLY_SCOPE=Device
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/model_name:Bluetooth Mouse
/sys/class/power_supply/hid-00:60:d1:02:31:61-battery/present:1

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1103064

Title:
  power indicator shows Logitech wireless keyboard and mouse batteries
  with 0%

Status in The Power Indicator:
  Invalid
Status in Upower:
  Fix Released
Status in indicator-power package in Ubuntu:
  Invalid
Status in upower package in Ubuntu:
  Fix Released
Status in indicator-power source package in Raring:
  Invalid
Status in upower source package in Raring:
  Won't Fix

Bug description:
  I updated by raring installation and found that the power indicator
  now shows my wireless keyboard and mouse as (missing) and with
  extremely low power. Both the keyboard and mouse work (I'm using them
  to type this bug) and the low battery light on the respective devices
  do not show low power. Even switching to brand new batteries don't
  make the indicator change state.

  I've attached a screenshot of the indicator and a screen shot of the
  power setting dialog which seems to be in conflict with the indicator.

  I've 

[Desktop-packages] [Bug 1271591] Re: upstart job race prevents gnome-keyring from being ssh agent

[atimonin]

It seems a better way would be to fix  
/etc/X11/Xsession.d/90x11-common_ssh-agent
(to start ssh-agent before gnome-keyring-daemon or not start it at all)
According to man page use of initctl set-env --global is discouraged

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1271591

Title:
  upstart job race prevents gnome-keyring from being ssh agent

Status in “gnome-keyring” package in Ubuntu:
  In Progress
Status in “gnome-keyring” source package in Trusty:
  Triaged

Bug description:
  I expect gnome-keyring to be the ssh authentication agent when I am
  logged in to a graphical session.

  Because of what I suspect is a race in upstart jobs, I believe
  SSH_AUTH_SOCK is being overwritten after gnome-keyring starts.

  Perhaps the gnome-session job needs to make sure the ssh-agent job is
  finished?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-session 3.9.90-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jan 22 10:25:59 2014
  InstallationDate: Installed on 2013-11-26 (56 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to trusty on 2014-01-17 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1271591/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 508522] Re: Mic is not available with A2DP Bluetooth profile

[atimonin]

For Skype (at least) there should be a workaround using notification scripts 
and switching
profiles as in 
https://wiki.archlinux.org/index.php/Bluetooth_headset#Switch_between_HSV_and_A2DP_setting
for ex.:
pacmd set-card-profile 2 a2dp

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/508522

Title:
  Mic is not available with A2DP Bluetooth profile

Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: pulseaudio

  I'm testing a Nokia BH-905i headset (see 
http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The 
Bluetooth module correctly identifies the headset and the both audio profiles 
HSP/ HFP Telephony duplex and A2DP High Fidelity Playback. For music 
playback only A2DP is suitable (HSP/HFP sounds like listening to music played 
through an old telephone). A2DP does not have an INPUT mode, so use of the 
headset for VoiP isn't possible.
  What would be needed is a separate selection to allow to select A2DP for 
output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do 
that (or they switch on the fly?).

  Formal structure:
  1) Ubuntu 10.10
  2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1
  consisting og pluseaudio, pulseaudio-esound-compat, 
pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, 
pulseaudio-utils
  3) Select high quality audio output and still use the Bluetooth microphone
  4) Had to choose: either high quality audio or telephone quality with 
microphone

  I can change the profile without the Bluetooth connection dropping,
  but that's ridiculous. E.g. listening to music, a call comes in. Then
  I would need to switch the profile before answering. Please note that
  in Windows, Mac OS, iOS, Android, and Windows Mobile it's done
  automatically.

  Check out attached screencast.

  ProblemType: Bug
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oivasyuv   2309 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17'
     Mixer name : 'Analog Devices AD1984A'
     Components : 'HDA:11d4194a,103c30e8,00100400'
     Controls  : 22
     Simple ctrls  : 14
  Date: Sat Jan 16 22:31:41 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5)
  Package: pulseaudio 1:0.9.19-0ubuntu4
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae
  SourcePackage: pulseaudio
  Uname: Linux 2.6.31-17-generic-pae i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/508522/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1346262] [NEW] Screen jam in LibreOffice Calc

[atimonin]

Public bug reported:

When I scroll (uzing mouse wheel) I see repeated rows not really
exsisting

I also noticed that it happens when I scroll in unfocused window (if
I have 2 Calc windows and move mouse to another window without click)

Steps to reproduce:
1. open 2 calc windows
2. move pointer to another window without changing focus (without click)
3. scroll up or down several times

Current behavior: info on screen incorrect, but file is not corrupted.
If I close and then open it all looks OK

Maybe it's not LibreOffice, but Gnome bug, but I don't know how to check
it.

** Affects: libreoffice (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: screenshot
   
https://bugs.launchpad.net/bugs/1346262/+attachment/4158985/+files/Calc-ScreenJam.png

** Bug watch added: freedesktop.org Bugzilla #79400
   https://bugs.freedesktop.org/show_bug.cgi?id=79400

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1346262

Title:
  Screen jam in LibreOffice Calc

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  When I scroll (uzing mouse wheel) I see repeated rows not really
  exsisting

  I also noticed that it happens when I scroll in unfocused window (if
  I have 2 Calc windows and move mouse to another window without click)

  Steps to reproduce:
  1. open 2 calc windows
  2. move pointer to another window without changing focus (without click)
  3. scroll up or down several times

  Current behavior: info on screen incorrect, but file is not corrupted.
  If I close and then open it all looks OK

  Maybe it's not LibreOffice, but Gnome bug, but I don't know how to
  check it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1346262/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1346262] Re: Screen jam in LibreOffice Calc

[atimonin]

Freedesktop gug report:
https://bugs.freedesktop.org/show_bug.cgi?id=79400

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1346262

Title:
  Screen jam in LibreOffice Calc

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  When I scroll (uzing mouse wheel) I see repeated rows not really
  exsisting

  I also noticed that it happens when I scroll in unfocused window (if
  I have 2 Calc windows and move mouse to another window without click)

  Steps to reproduce:
  1. open 2 calc windows
  2. move pointer to another window without changing focus (without click)
  3. scroll up or down several times

  Current behavior: info on screen incorrect, but file is not corrupted.
  If I close and then open it all looks OK

  Maybe it's not LibreOffice, but Gnome bug, but I don't know how to
  check it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1346262/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1107926] Re: bamfdaemon crashed with signal 5 in _XReply()

[atimonin]

*** This bug is a duplicate of bug 1193714 ***
https://bugs.launchpad.net/bugs/1193714

I also see regular crashes of bamfdaemon

** Attachment added: .crash file
   
https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1107926/+attachment/3994036/+files/_usr_lib_x86_64-linux-gnu_bamf_bamfdaemon.1000.crash

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bamf in Ubuntu.
https://bugs.launchpad.net/bugs/1107926

Title:
  bamfdaemon crashed with signal 5 in _XReply()

Status in “bamf” package in Ubuntu:
  Confirmed

Bug description:
  happened right after boot

  msg = 0x1304c80 The program 'bamfdaemon' received an X Window System
  error.\nThis probably reflects a bug in the program.\nThe error was
  'BadWindow (invalid Window parameter)'.\n  (Details: serial 2240
  error_code 3 requ...

  complete error at attachment #8

  ProblemType: CrashDistroRelease: Ubuntu 13.04
  Package: bamfdaemon 0.4.0daily13.01.11-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-2.6-generic 3.8.0-rc4
  Uname: Linux 3.8.0-2-generic x86_64
  ApportVersion: 2.8-0ubuntu2
  Architecture: amd64
  Date: Mon Jan 28 13:35:51 2013
  ExecutablePath: /usr/lib/x86_64-linux-gnu/bamf/bamfdaemon
  InstallationDate: Installed on 2013-01-24 (3 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcCmdline: /usr/lib/x86_64-linux-gnu/bamf/bamfdaemon
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=set
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8Signal: 5SourcePackage: bamf
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libwnck-3.so.0
  Title: bamfdaemon crashed with signal 5 in _XReply()
  UpgradeStatus: Upgraded to raring on 2013-01-24 (3 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XsessionErrors:
   (nautilus:1888): Nautilus-Python-WARNING **: g_module_open libpython failed: 
/usr/lib/libpython2.7.so.1.0: Ne peut ouvrir le fichier d'objet partagé: Aucun 
fichier ou dossier de ce type
   (nautilus:1888): Nautilus-Python-WARNING **: pygobject initialization failed
   (nautilus:1888): Nautilus-Python-WARNING **: nautilus_python_init_python 
failed
   (process:2145): GLib-CRITICAL **: g_slice_set_config: assertion 
`sys_page_size == 0' failed
   (process:2336): GLib-CRITICAL **: g_slice_set_config: assertion 
`sys_page_size == 0' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1107926/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1239151] Re: nmcli Segmentation fault (core dumped)

[atimonin]

Got just the same effect^

nmcli d list
GENERAL.DEVICE: 00:0C:E7:B0:3D:DD
GENERAL.TYPE:   bluetooth
GENERAL.VENDOR: --
GENERAL.PRODUCT:--
GENERAL.DRIVER: bluez
GENERAL.DRIVER-VERSION: 
GENERAL.FIRMWARE-VERSION:   
GENERAL.HWADDR: (unknown)
GENERAL.STATE:  30 (disconnected)
GENERAL.REASON: 0 (No reason given)
GENERAL.UDI:
/org/bluez/1041/hci0/dev_00_0C_E7_B0_3D_DD
GENERAL.IP-IFACE:   
GENERAL.NM-MANAGED: yes
GENERAL.AUTOCONNECT:yes
GENERAL.FIRMWARE-MISSING:   no
GENERAL.CONNECTION: not connected
CAPABILITIES.CARRIER-DETECT:no
CAPABILITIES.SPEED: unknown
CONNECTIONS.AVAILABLE-CONNECTION-PATHS: 
/org/freedesktop/NetworkManager/Settings/{0}
CONNECTIONS.AVAILABLE-CONNECTIONS[1]:   7fb41ad4-c284-4815-98d6-7c2f51b14422 | 
ThL W7 Network
GENERAL.DEVICE: wlan0
GENERAL.TYPE:   802-11-wireless
GENERAL.VENDOR: Atheros Communications Inc.
GENERAL.PRODUCT:AR9462 Wireless Network Adapter
GENERAL.DRIVER: ath9k
GENERAL.DRIVER-VERSION: 3.8.0-34-generic
GENERAL.FIRMWARE-VERSION:   N/A
GENERAL.HWADDR: 50:B7:C3:D2:C1:E2
GENERAL.STATE:  100 (connected)
GENERAL.REASON: 0 (No reason given)
GENERAL.UDI:
/sys/devices/pci:00/:00:15.0/:03:00.0/net/wlan0
GENERAL.IP-IFACE:   wlan0
GENERAL.NM-MANAGED: yes
GENERAL.AUTOCONNECT:yes
GENERAL.FIRMWARE-MISSING:   no
GENERAL.CONNECTION: 
/org/freedesktop/NetworkManager/ActiveConnection/2
CAPABILITIES.CARRIER-DETECT:no
CAPABILITIES.SPEED: 115 Mb/s
CONNECTIONS.AVAILABLE-CONNECTION-PATHS: 
/org/freedesktop/NetworkManager/Settings/{5,13,12,2,6,1}
CONNECTIONS.AVAILABLE-CONNECTIONS[1]:   9f1935ee-5531-473b-bc0d-0b5b379f477b | 
Pluto
CONNECTIONS.AVAILABLE-CONNECTIONS[2]:   379565ac-e20d-4abf-bc6b-b504d6f52623 | 
Neptun
CONNECTIONS.AVAILABLE-CONNECTIONS[3]:   173ba863-ec2c-4caa-abbb-dc07ba8f1758 | 
Neptun5
CONNECTIONS.AVAILABLE-CONNECTIONS[4]:   3e1009b7-dbb8-4291-b46d-424a382de539 | 
Pluto5
CONNECTIONS.AVAILABLE-CONNECTIONS[5]:   c6b058ff-c35c-497a-a72b-b874073081a0 | 
Neptun5 1
CONNECTIONS.AVAILABLE-CONNECTIONS[6]:   6bb903c4-ddd7-4fe6-a6dc-ecd628bb859d | 
Pluto_xt
WIFI-PROPERTIES.WEP:yes
WIFI-PROPERTIES.WPA:yes
WIFI-PROPERTIES.WPA2:   yes
WIFI-PROPERTIES.TKIP:   yes
WIFI-PROPERTIES.CCMP:   yes
WIFI-PROPERTIES.AP: yes
WIFI-PROPERTIES.ADHOC:  yes
AP[1].SSID: 'Keenetic'
AP[1].BSSID:FE:F5:28:49:0E:F0
AP[1].MODE: Infrastructure
AP[1].FREQ: 2417 MHz
AP[1].RATE: 54 MB/s
AP[1].SIGNAL:   75
AP[1].SECURITY: WPA2
AP[1].ACTIVE:   no
AP[2].SSID: 'Neptun'
AP[2].BSSID:60:A4:4C:D2:3D:68
AP[2].MODE: Infrastructure
AP[2].FREQ: 2412 MHz
AP[2].RATE: 54 MB/s
AP[2].SIGNAL:   100
AP[2].SECURITY: WPA2
AP[2].ACTIVE:   no
AP[3].SSID: 'Neptun'
AP[3].BSSID:50:46:5D:01:66:88
AP[3].MODE: Infrastructure
AP[3].FREQ: 2452 MHz
AP[3].RATE: 54 MB/s
AP[3].SIGNAL:   100
AP[3].SECURITY: WPA2
AP[3].ACTIVE:   no
AP[4].SSID: 'Neptun5'
AP[4].BSSID:50:46:5D:01:66:8C
AP[4].MODE: Infrastructure
AP[4].FREQ: 5240 MHz
AP[4].RATE: 54 MB/s
AP[4].SIGNAL:   60
AP[4].SECURITY: WPA2
AP[4].ACTIVE:   no
AP[5].SSID: 'Neptun'
AP[5].BSSID:74:D0:2B:5D:5A:20
AP[5].MODE: Infrastructure
AP[5].FREQ: 2472 MHz
AP[5].RATE: 54 MB/s
AP[5].SIGNAL:   70
AP[5].SECURITY: WPA2
AP[5].ACTIVE: