date:20161220

** Summary changed:

- update-manager can't handle hotel web access pages
+ Test for captive portal before putting applications in online mode

** Changed in: network-manager (Ubuntu Raring)
 Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned)

** Tags removed: amd64 apport-bug precise
** Tags added: nm-features

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

Title:
  Test for captive portal before putting applications in online mode

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged
Status in update-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Precise:
  Won't Fix
Status in update-manager source package in Precise:
  Won't Fix
Status in network-manager source package in Quantal:
  Won't Fix
Status in update-manager source package in Quantal:
  Won't Fix
Status in network-manager source package in Raring:
  Won't Fix
Status in update-manager source package in Raring:
  Won't Fix

Bug description:
  When in a hotel there is a often a T&Cs page that is delivered when
  connecting to the network.  Some combination of network manager and
  update manager (or something else entirely) doesn't seem to be able to
  handle this, and update are left in a non-working state after not
  being able to read package headers file.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.4.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Wed May  9 17:27:02 2012
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  IpRoute:
   default via 10.155.32.1 dev wlan0  proto static 
   10.155.32.0/19 dev wlan0  proto kernel  scope link  src 10.155.38.82  metric 
2 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to precise on 2012-03-07 (63 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.4.0connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/997200/+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 1577093] Re: libreoffice-gtk conflicts with large lo-writer file

2016-12-20 Thread Jurgen Schellaert

1) No, previous versions were fine.
2) My issue got solved through an August update (comment #4 above) so I have 
not seen any reason to test other versions since. All I can say is that I did 
try launchpad at the time I was experiencing the bug - no 5.2.x was available 
yet - and that did not help at all. I will try a later version as soon as I 
find the time.

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

Title:
  libreoffice-gtk conflicts with large lo-writer file

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  After opening 
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1577093/+attachment/4652522/+files/wlst.odt
 , LibreOffice becomes  unresponsive, graying out from a few minutes to a 
quarter of an hour at a time. During this, the interface has various 
presentation issues:
  - Two overlapping status bars
  - Duplicated vertical scrollbars at the right side
  - The title bar covering up the menu bar as well as part of the upper toolbar
  - The horizontal ruler shifted to the right, causing the "comments" column to 
appear on the left rather than the right

  When the file eventually gets loaded and the interface is restored,
  the menus turns out to be unusable: the drop-downs are narrow blacks
  slabs without any entries and without any responsiveness.

  Newly created files or existing smaller files are fine.

  WORKAROUND: Uninstall packages:
  libreoffice-gnome
  libreoffice-gtk

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-writer 1:5.1.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun May  1 05:28:07 2016
  InstallationDate: Installed on 2016-04-07 (23 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160405)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1577093/+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 824998] Re: NM puts up "Authentication required by Wireless Network" dialogue even if previous identical dialogue was cancelled

Leave to

** Changed in: network-manager (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  NM puts up "Authentication required by Wireless Network" dialogue even
  if previous identical dialogue was cancelled

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  Oneiric annoys me sending messages "Authentication required by Wireless 
Network" ad infinitum.
  I did not aks Oneiric to connect to a wireless access point. 
  Lucid was more intelligent and stopped annoying me after a while after I had 
told it not to connect to this wireless network.
  I expect that Oneiric GNOME 3 learns at least after the third denied message 
that I am connected via Ethernet and do not wish a wireless connection.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: network-manager 0.8.9997+git.20110721t045648.36db194-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-7.9-server 3.0.0
  Uname: Linux 3.0.0-7-server x86_64
  Architecture: amd64
  CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
  Date: Fri Aug 12 08:16:31 2011
  Gconf:
   
  InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 
(20110426)
  IpRoute:
   default via 192.168.178.1 dev eth0  metric 100 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.178.0/24 dev eth0  proto kernel  scope link  src 192.168.178.32
  Keyfiles: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to oneiric on 2011-08-07 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/824998/+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 1638245] Re: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package

2016-12-20 Thread Sadi Yumuşak

Hi Nikita, what you call gobbledygook is partition UUID it seems, which is 
strange. Could it be because those partitions have no label?
 
I see only partition labels as expected (for both internal and external, 
mounted and unmounted, drives) under Ubuntu 16.10 64-bit ( I tend to make sure 
that everyone is labelled properly ;-)

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

Title:
  Files in the root of a folder on another partition symlinked to user's
  home cannot be moved to trash because of a patch in this package

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Xenial:
  Confirmed
Status in glib2.0 source package in Yakkety:
  Fix Committed

Bug description:
  [ Description ]

  Can't trash files if the directory they are in is a symlink to another
  device

  [ QA ]

  Steps:
  1. Install system and partition disk into root and data partitions
  2. create ~/Data folder, and mount data partition on it
  3. create symlinks for ~/whatever/ to ~/Data/something/
  4. delete files directly inside ~/whatever/

  What happen:
  Then Nautilus says: "File can't be put in the trash. Do you want to delete it 
immediately?".

  What should happen:
  The files moved into Trash.

  [ Regression potential ]

  The proposed fix uses g_stat instead of g_stat to follow symlinks, so
  we know where to place the trash (you can't rename() across
  filesystems). If that is wrong, then it could regress trashing other
  kinds of files.

  [ Original ]

  I'm on Ubuntu 16.10 64-bit with libglib2.0-0 version 2.50.0-1.

  I've reported this bug (or marked as "it affects me") in a couple of
  other places before I've finally discovered that this is the package
  that's causing this problem, which unfortunately has been around for a
  couple of years now.

  This bug has been reported upstream as well, but it's just taking very
  very long to arrive at a decision and take action it seems.

  Apparently one of the patches
  (https://sources.debian.net/patches/glib2.0/2.50.1-1/0001-Fix-
  trashing-on-overlayfs.patch/) which is here
  
(https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0-1.debian.tar.xz)
  to the original package which is here
  
(https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0.orig.tar.xz)
  is the root cause of this annoying problem.

  As I prefer keeping one patition for the root filesystem (/), one
  partition for user settings (/home) and one partition for user data
  (Documents, Downloads, Drive, Music, Pictures, Public, Videos) which
  are simply symlinked to my home folder for ease of use, I cannot move
  any file to the trash in the root of these folders when I access them
  from my home folder or nautilus sidebar.

  This problem doesn't affect folders at all, nor any other files in
  subfolders, etc.

  So I was wondering if Ubuntu devs can leave out that particular patch
  when building this package for Ubuntu - if it doesn't cause more harm,
  which I doubt.

  Otherwise, I would appreciate if I could learn how to do it myself:
  how can I (as an end-user) compile the contents of
  "glib2.0_2.50.0.orig.tar.xz" with all the patches, etc. in
  "glib2.0_2.50.0-1.debian.tar.xz" except "0001-Fix-trashing-on-
  overlayfs.patch"?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1638245/+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 1167019] Re: wifi packet loss on intel Centrino Wireless-N 1000

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  wifi packet loss on intel Centrino Wireless-N 1000

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  Sat on a wifi network with another non-Linux machine nearby on the
  same access point. The Linux machine (Ubuntu 13.04 up to date) drops
  off the network repeatedly. Network manager shows a constant
  connection. mtr shows packet loss.

   My traceroute  [v0.82]
  deep-thought (0.0.0.0) Tue Apr  9 22:27:30 
2013
  Keys:  Help   Display mode   Restart statistics   Order of fields   quit
 Packets   Pings
   HostLoss%   Snt   Last   Avg  Best  Wrst 
StDev
   1. 192.168.1.1  41.5%   3167.1   7.2   4.8  23.5   
1.7
   2. cpc8-farn5-2-0-gw.6-2.cable.virg 41.3%   315   59.9  32.5  13.0 302.8  
34.4
   3. glfd-core-2b-ae3-4033.network.vi 41.3%   315   18.0  26.2  12.9 146.1  
20.3
   4. glfd-bb-1b-ae6-0.network.virginm 41.3%   315   18.0  22.3  13.0 133.9  
16.0
   5. glfd-bb-1a-ae0-0.network.virginm 41.3%   315   24.3  24.4  11.8 131.7  
18.5
   6. nrth-bb-1b-ae4-0.network.virginm 41.6%   315   18.3  28.8  15.7 177.1  
21.2
   7. tele-ic-4-ae0-0.network.virginme 41.6%   315   27.7  29.2  17.2 146.9  
18.5
   8. linx-gw-a.jump.net.uk41.6%   315   21.0  27.6  18.4 128.6  
15.7
   9. dunkel.bitfolk.com   41.3%   315   20.9  25.9  18.4 132.7  
13.1
  10. popey.com41.6%   315   22.6  27.2  17.4 149.9  
17.3

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-17-generic 3.8.0-17.27
  ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
  Uname: Linux 3.8.0-17-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   2823 F pulseaudio
  Date: Tue Apr  9 22:22:16 2013
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=4de844e6-b3a9-4309-bc26-739bea6b4146
  InstallationDate: Installed on 2012-06-29 (284 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: LENOVO 4287CTO
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-17-generic 
root=UUID=c8438547-b9fb-46af-8012-4663c77c70e7 ro quiet splash 
i915.semaphores=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-17-generic N/A
   linux-backports-modules-3.8.0-17-generic  N/A
   linux-firmware1.104
  SourcePackage: linux
  UpgradeStatus: Upgraded to raring on 2013-01-18 (81 days ago)
  dmi.bios.date: 12/05/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET67WW (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4287CTO
  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:bvr8DET67WW(1.37):bd12/05/2012:svnLENOVO:pn4287CTO:pvrThinkPadX220:rvnLENOVO:rn4287CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4287CTO
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1167019/+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 1330471] Re: connects to far away access points since #83 mako & flo

** Summary changed:

- nm connects to far away access points since #83 mako & flo
+ connects to far away access points since #83 mako & flo

** Package changed: network-manager (Ubuntu) => linux (Ubuntu)

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

Title:
  connects to far away access points since #83 mako & flo

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  For a few images now, on mako and flo my devices seem to cling onto
  access points which are far away rather than nearby ones.

  At home I have two access points named such that I know which is which
  (popey_2.4_bed & popey_2.4_den).

  When I boot up an Ubuntu device (phone/tablet) they always seem to
  attach to the far away access point and stay on it until I forcibly
  choose the other access point.

  I notice this a lot because I find using the phone slow because it's
  using the 'bed' AP which is at the other end of the house and through
  a few walls, whereas the 'den' one is right next to me in the office.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu18
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.3-0ubuntu1
  Architecture: armhf
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Mon Jun 16 13:41:12 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  InstallationDate: Installed on 2014-06-16 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140616)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   10.144.147.0/24 dev rmnet_usb0  proto kernel  scope link  src 10.144.147.88  
metric 13 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.105  
metric 9
  PciNetwork:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.dbus.1.system.d.org.freedesktop.NetworkManager.conf: 
2014-06-11T20:47:57
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   /ril_0 gsm   connected 
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1330471/+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 1157332] Re: /etc/dnsmasq.d-available/lxc circular link

We're dropping dnsmasq from default, marking as Won't Fix in network-
manager.

** Changed in: network-manager (Ubuntu)
   Status: Triaged => Won't Fix

** Changed in: network-manager (Ubuntu)
 Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned)

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

Title:
  /etc/dnsmasq.d-available/lxc circular link

Status in libvirt package in Ubuntu:
  Fix Released
Status in lxc package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Won't Fix
Status in libvirt source package in Quantal:
  Fix Released
Status in lxc source package in Quantal:
  Fix Released
Status in network-manager source package in Quantal:
  Won't Fix
Status in libvirt source package in Raring:
  Fix Released
Status in lxc source package in Raring:
  Fix Released
Status in network-manager source package in Raring:
  Won't Fix

Bug description:
  = Rational =
  We pushed a custom dnsmasq hook to precise, quantal and raring over the past 
few months to avoid conflicts for people running the dnsmasq system daemon 
(non-default).
  However because we introduced this change as SRU, it's causing problems when 
then upgrading to the next release by having the migration code get executed 
multiple times.
  We need to fix this and repare broken systems in the process.

  = Test case =
   - Install any of the current  lxc, libvirt-bin or network-manager on Ubuntu 
12.04 or 12.10
   - Dist-upgrade to the next version of Ubuntu
   - You'll notice /etc/dnsmasq.d-available/FILE is now a circular link, 
/etc/dnsmasq.d/FILE no longer exists and the old content is moved to 
/etc/dnsmasq.d-available/FILE.dpkg-new (where FILE is lxc, dnsmasq or 
network-manager)
   - Updating to a fixed package will move everything back into place (assuming 
the user hasn't done any local change in between, in which case, nothing will 
be done)

  = Regression potential =
  I have tested the change doing precise -> quantal -> raring and quantal -> 
raring and I'm confident the new postinst hook will fix any breakage. It's also 
specific enough to only trigger in the specific case we know how to repair. In 
all other cases, we keep the system as-is and let the user deal with it. As a 
result, it's not impossible that some weird corner cases (for example when 
removing/purging the package in between dist-upgrades) may go unfixed but I'm 
confident we'll cover at least 99% of the cases with the fix and that this fix 
is safe.

  
  --- Original bug report ---
  In today's Raring apt-get dist-upgrade:

  Setting up lxc (0.9.0~rc1-0ubuntu1) ...
  Installing new version of config file 
/etc/apparmor.d/lxc/lxc-default-with-nesting ...
  dpkg: warning: lxc: config file '/etc/dnsmasq.d-available/lxc' is a circular 
link
   (= '/etc/dnsmasq.d-available/lxc')

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1157332/+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 1651396] [NEW] Backup fails every time after one incremental file is possibly corrupted

2016-12-20 Thread Eero

Public bug reported:

The backup location is on a NAS mounted with NFS. I get this message
every time I try to make a new backup:

Backup Failed

Invalid data - SHA1 hash mismatch for file:
 duplicity-inc.20161219T001458Z.to.20161220T001456Z.vol1.difftar.gpg
 Calculated hash: 3dde403f81e36268ce9b7f53478d9dd8301a439c
 Manifest hash: b46782fb799c7c5a543ac88d9bfb7cc1df25d38c


Can someone recommend a better backup software for personal use?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: deja-dup 34.2-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Dec 20 12:36:15 2016
InstallationDate: Installed on 2014-05-16 (949 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: deja-dup
UpgradeStatus: Upgraded to xenial on 2016-08-02 (139 days ago)

** Affects: deja-dup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  Backup fails every time after one incremental file is possibly
  corrupted

Status in deja-dup package in Ubuntu:
  New

Bug description:
  The backup location is on a NAS mounted with NFS. I get this message
  every time I try to make a new backup:

  Backup Failed

  Invalid data - SHA1 hash mismatch for file:
   duplicity-inc.20161219T001458Z.to.20161220T001456Z.vol1.difftar.gpg
   Calculated hash: 3dde403f81e36268ce9b7f53478d9dd8301a439c
   Manifest hash: b46782fb799c7c5a543ac88d9bfb7cc1df25d38c


  Can someone recommend a better backup software for personal use?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: deja-dup 34.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec 20 12:36:15 2016
  InstallationDate: Installed on 2014-05-16 (949 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to xenial on 2016-08-02 (139 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1651396/+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 1407928] Re: [phone] Does not auto-switch to available, known WiFi

** Tags added: nm-touch

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

Title:
  [phone] Does not auto-switch to available, known WiFi

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  This might not be the place for this bug, please reassign as
  appropriate.

  I was only able to reproduce this on mako/rtm, krillin/vivid seems to
  behave better (but I do remember the same issue there).

  Steps:
  * connect to a password-protected WiFi network
  * go out of range
  * make sure a GSM connection is established
  * go back in the WiFi range

  Expected:
  * phone connects to the known WiFi automatically

  Current:
  * phone does not connect to WiFi

  Please find attached network-test-session logs from when I toggled
  WiFi and Plane mode to get some data on the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: indicator-network 0.5.1+15.04.20141215~rtm-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Tue Jan  6 12:01:55 2015
  InstallationDate: Installed on 2014-12-18 (18 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141218-163635)
  SourcePackage: indicator-network
  UpgradeStatus: No upgrade log present (probably fresh install)
  indicator-network.log:
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered
  upstart.indicator-network.log:
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1407928/+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 1183981] Re: Random wireless stalling using wl driver, chipset broadcom 4313 [14e4:4727], on a Lenovo S206

Raring reached EOL on January 27, 2014.
See this document for currently supported Ubuntu releases: 
https://wiki.ubuntu.com/Releases

If you are having a problem in a supported release, please file a new report 
via a terminal:
ubuntu-bug bcmwl

Do feel free to report any other bugs you may find.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

** Changed in: network-manager (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  Random wireless stalling using wl driver, chipset broadcom 4313
  [14e4:4727], on a Lenovo S206

Status in network-manager package in Ubuntu:
  Won't Fix

Bug description:
  I am randomly losing connectivity to the Internet. I cannot ping
  anything, DNS resolving does not work and i cannot view any web pages,
  apt-get and such.

  I am seeing this issue on the liveCD, a fresh install of Saucy (daily
  build 23/5/2013) and also on an upgrade from Raring to Saucy.

  Network manager still thinks i am connected.

  I have disabled network manager and connected using a wpa_passphrase
  file and i still get the same issue.

  Interestingly enough, if i disconnect and reconnect to the wireless
  access point using nm_applet, i can get connectivity again until it
  stops again.

  route and arp -a were taking an age to return so i added a static
  entry to the arp cache. That made no difference.

  I have increased the debugging level from wpa_supplicant but i could
  not see any obvious failure in there. I'm not 100% sure what to look
  for though.

  I could see nothing in syslog or dmesg that would point to any obvious
  failure.

  I have uploaded this bug report after booting into the fresh problem
  install, waiting for the connection problem, reconnecting and raising
  this bug report.

  I am willing to help with any diagnostic information i can supply. The
  only connectivity this netbook has is wireless so this will be an
  issue when Saucy is released.

  I have lost connectivity while typing up this bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager 0.9.8.0-0ubuntu8
  ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3
  Uname: Linux 3.9.0-2-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  Date: Fri May 24 20:17:14 2013
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-05-22 (1 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130520)
  IpRoute:
   default via 192.168.0.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.100  metric 
9
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   whitehousead5fc2ff-a272-404c-acb9-ff55fa8188c9   
802-11-wireless   1369423172   Fri 24 May 2013 20:19:32 BST   yes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.0connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1183981/+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 1241986] Re: Cannot connect to WPA/WPA2, EAP-PEAP, MSCHAPV2 network

** Tags added: nm-touch

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

Title:
  Cannot connect to WPA/WPA2, EAP-PEAP, MSCHAPV2 network

Status in Canonical System Image:
  Fix Released
Status in indicator-network package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu for Phones final image on mako I can see a network but
  cannot connect because I never get prompted for the username/password.

  :
  "In both the ‘Connect to “{network name}”’ and “Connect to Hidden
  Network” dialogs, the contents of the dialog, and the behavior of the
  “Connect” button, should vary depending on the security and
  authentication methods..."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1241986/+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 1651399] [NEW] LPR command to use PDF page size while printing

2016-12-20 Thread Purnima C Naik

Public bug reported:

I am doing receipt printing by creating PDF file.

The size of my receipt PDF is dynamic.

Currently, the LPR command which I am using for getting this printed is
as follows:

lpr -P "ReceiptPrinter" -o PageSize=Custom.20x6cm 
"/home/ubuntu/Desktop/Punu1/iText123.pdf"
I am required to pass custom size, as LPR command is not taking PDF page size 
during printing.

But passing of custom size, is not helpful to me, as size of my receipt
keeps on changing.

Can someone please tell me, how can I set printer page size to PDF page
size in LPR command?

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

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

Title:
  LPR command to use PDF page size while printing

Status in cups package in Ubuntu:
  New

Bug description:
  I am doing receipt printing by creating PDF file.

  The size of my receipt PDF is dynamic.

  Currently, the LPR command which I am using for getting this printed
  is as follows:

  lpr -P "ReceiptPrinter" -o PageSize=Custom.20x6cm 
"/home/ubuntu/Desktop/Punu1/iText123.pdf"
  I am required to pass custom size, as LPR command is not taking PDF page size 
during printing.

  But passing of custom size, is not helpful to me, as size of my
  receipt keeps on changing.

  Can someone please tell me, how can I set printer page size to PDF
  page size in LPR command?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1651399/+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 1055068] Re: Guest user can use arbitrary MAC addresses

** Tags removed: amd64 apport-bug quantal running-unity
** Tags added: nm-improvements

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

Title:
  Guest user can use arbitrary MAC addresses

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  In Quantal, as a guest user you can create a network connection with an 
arbitrary mac address - I take
  that as a security hole (being able to break another machine on the network).

  (actually in this case the guest user you get to register a remote
  desktop account, you can get a terminal in it - that might be another
  security issue)

  Go to the network manager icon and edit connections
Wired network
 Add connection
 Choose the eth0/deault device mac address
  Type in a MAC address of your own evil making in the 'cloned mac 
address' box
   Untick 'available to all users'

  and Save

  Now, you have a new connection, but it's not up

  Open a terminal and use

nmcli con

  to list the network connections, and note the UUID of your new one.
  Now do

nmcli con up uuid .where . is the UUID you just got.

  You're now spoofing someone elses MAC address.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: network-manager 0.9.6.0-0ubuntu7
  ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
  Uname: Linux 3.5.0-15-generic x86_64
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: amd64
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Sun Sep 23 16:41:47 2012
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64+mac 
(20120905.2)
  IpRoute:
   default via 192.168.122.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.122.0/24 dev eth0  proto kernel  scope link  src 192.168.122.34  
metric 1
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Wired connection 190a0ede6-43a8-4ad1-a26c-b17a52146725   
802-3-ethernet1348414780   Sun 23 Sep 2012 16:39:40 BST   yes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.6.0connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1055068/+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 1565717] Re: No connection after returning from area without coverage

** Tags added: nm-touch

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

Title:
  No connection after returning from area without coverage

Status in Canonical System Image:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  After moving in an out of my own "faraday cage" an ubuntu phone, NM
  got into an state where *both* WiFi and cellular data were
  disconnected and NM was not able to recover.

  
  * This still happens with network-manager 1.1.93-0ubuntu1~vivid3, in

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 336
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-05-17 09:19:51
  version version: 336
  version ubuntu: 20160517
  version device: 20160329-a9bacdb
  version custom: 20160505-975-38-9
  

  Originally reported for:

  NM version:
  network-manager  0.9.10.0-4ubuntu15.1.11

  root@ubuntu-phablet:/home/phablet# system-image-cli -i
  current build number: 298
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-03-30 16:58:21
  version version: 298
  version ubuntu: 20160330
  version device: 20160323-1467d3c
  version custom: 20160324--36-54-vivid

  phablet@ubuntu-phablet:~$ nmcli d
  DEVICE   TYPE  STATE CONNECTION
  ril_0gsm   connecting (prepare)  /214050030479893/context1
  wlan0wifi  disconnected  --
  ril_1gsm   unavailable   --
  ifb0 ifb   unmanaged --
  ifb1 ifb   unmanaged --
  lo   loopback  unmanaged --
  ip6tnl0  unknown   unmanaged --
  sit0 unknown   unmanaged --
  tunl0unknown   unmanaged --

  phablet@ubuntu-phablet:~$ nmcli c
  NAME   UUID  TYPE 
DEVICE
  WLAN_1609  fe9b17ad-88fa-43b7-bcab-8fbc1985ce42  
802-11-wireless  --
  Wireless   98ff5b6f-b0d9-471a-b867-8a7be51e12c2  
802-11-wireless  --
  Ubuntu 549c352f-8a2b-4e48-b8c8-eb7ab0e53089  
802-11-wireless  --
  /234304107917083/context1  1f192cdc-ccea-2dc3-fa13-619ed3053828  gsm  
--
  /214321010036211/context1  0992421f-2369-0765-ceaa-ba2a3091e111  gsm  
--
  /214050030479893/context1  d30e4f19-9d00-ab1f-ab43-6d9c1b628556  gsm  
ril_0
  /214019301737411/context1  88b28978-e2fc-6336-8665-b0ae78d321ae  gsm  
--

  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
  [ /ril_1 ]
  [ /ril_0 ]
  [ /ril_0/context1 ]
  Settings = { Gateway=10.50.83.25 
DomainNameServers=80.58.61.250,80.58.61.254, Interface=ccmni0 
Address=10.50.83.25 Method=static Netmask=255.255.255.0 }
  Name = Pepephone
  Type = internet
  AccessPointName = gprs.pepephone.com
  Active = 1
  Protocol = ip
  AuthenticationMethod = chap
  Password =
  Preferred = 0
  Username =
  IPv6.Settings = { }

  [ /ril_0/context2 ]
  Name = MMS Pepephone
  Type = mms
  Active = 0
  Settings = { }
  MessageCenter = http://www.pepephone.com
  MessageProxy = 10.138.255.43:8080
  Preferred = 0
  Password =
  AccessPointName = gprs.pepephone.com
  Protocol = ip
  AuthenticationMethod = chap
  Username =
  IPv6.Settings = { }

  phablet@ubuntu-phablet:~$ ifconfig
  ccmni0Link encap:Ethernet  HWaddr 46:23:7c:fb:73:cb
    inet addr:10.50.83.25  Mask:255.0.0.0
    UP RUNNING NOARP  MTU:1500  Metric:1
    RX packets:1995 errors:0 dropped:0 overruns:0 frame:0
    TX packets:2299 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:603432 (603.4 KB)  TX bytes:193513 (193.5 KB)

  loLink encap:Local Loopback
    inet addr:127.0.0.1  Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING  MTU:16436  Metric:1
    RX packets:11189 errors:0 dropped:0 overruns:0 frame:0
    TX packets:11189 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:1733281 (1.7 MB)  TX bytes:1733281 (1.7 MB)

  wlan0 Link encap:Ethernet  HWaddr b8:64:91:47:21:b6
    UP BROADCAST MULTICAST  MTU:1500  Metric:1
    RX packets:3184 errors:0 dropped:0 overruns:0 frame:0
    TX packets:1626 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:308130 (308.1 KB)  TX bytes:172906 (172.9 KB)

  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-modems
  [ /ril_1 ]
  Ser

[Desktop-packages] [Bug 1450790] Re: Phone with an APN specifying Username/Password, not re-connecting to mobile data until rebooting

** Tags added: nm-touch

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

Title:
  Phone with an APN specifying Username/Password, not re-connecting to
  mobile data until rebooting

Status in Canonical System Image:
  Fix Released
Status in network-manager package in Ubuntu:
  In Progress
Status in ofono package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu RTM:
  Fix Released

Bug description:
  Whenever I walk out of WiFi range, my phone does not connect to mobile
  data. Toggling flight mode does not help. I have to reboot the phone.
  When then I finally manage to connect after rebooting, if the signal
  strength drops and the phone would want to switch from 3G to 2G, it
  disconnects and I have to reboot again to get mobile data.

  $ system-image-cli -i
  current build number: 200
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-04-30 11:07:21
  version version: 200
  version ubuntu: 20150429
  version device: 20150326-f0c5ba5
  version custom: 20150429

  Attached you'll find the output of the forensics script

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1450790/+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 997200] Re: Test for captive portal before putting applications in online mode

** Tags removed: nm-features
** Tags added: nm-improvements

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

Title:
  Test for captive portal before putting applications in online mode

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged
Status in update-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Precise:
  Won't Fix
Status in update-manager source package in Precise:
  Won't Fix
Status in network-manager source package in Quantal:
  Won't Fix
Status in update-manager source package in Quantal:
  Won't Fix
Status in network-manager source package in Raring:
  Won't Fix
Status in update-manager source package in Raring:
  Won't Fix

Bug description:
  When in a hotel there is a often a T&Cs page that is delivered when
  connecting to the network.  Some combination of network manager and
  update manager (or something else entirely) doesn't seem to be able to
  handle this, and update are left in a non-working state after not
  being able to read package headers file.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.4.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Wed May  9 17:27:02 2012
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  IpRoute:
   default via 10.155.32.1 dev wlan0  proto static 
   10.155.32.0/19 dev wlan0  proto kernel  scope link  src 10.155.38.82  metric 
2 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to precise on 2012-03-07 (63 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.4.0connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/997200/+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 1349871] Re: 3G gets enabled on returning from Flight mode

** Tags added: nm-touch

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

Title:
  3G gets enabled on returning from Flight mode

Status in network-manager package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  Most probably I have selected the wrong package.

  1. disable 3G
  2. switch to flight mode
  3. switch off flight mode

  What happens:
  3G gets enabled automatically

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubuntu-system-settings 0.3+14.10.20140725.4-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: armhf
  Date: Tue Jul 29 19:08:28 2014
  InstallationDate: Installed on 2014-07-29 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140729-052958)
  SourcePackage: ubuntu-system-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1349871/+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 957857] Re: No way to change password for a backup set

2016-12-20 Thread Eero

Better way of encrypting backups would be something like this:
1. Generate a random key for backup encryption.
2. Encrypt the generated key with a password provided by the user.
3. Save the encrypted key with backups.

Now if the user wants to change the password, only the key file needs to
be re-encrypted. That is more or less how LUKS works. As an added bonus
better key derivation functions for step two can be easily added over
time with a scheme like this.

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

Title:
  No way to change password for a backup set

Status in Déjà Dup:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  In deja-dup-preferences, there is no way to change a password for a
  backup set - without starting the backups again from 0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/957857/+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 1297286] Re: Wireless connection keeps disconnecting

** Package changed: network-manager (Ubuntu) => linux (Ubuntu)

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

Title:
  Wireless connection keeps disconnecting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have a wireless access point that is at most 2 meters away. It keeps
  disconnecting with no apparent reason. I read somewhere that setting a
  static ip should help with the problem, but the problem seems pretty
  persistent.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-19.39-lowlatency 3.13.6
  Uname: Linux 3.13.0-19-lowlatency x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 25 15:20:15 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-03-20 (5 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140319)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.245  
metric 9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-03-23T16:50:07.398742
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   NETGEAR   74dc69be-e44f-4e15-a614-6c284d83d16b   
802-11-wireless   1395737193   Tue 25 Mar 2014 10:46:33 AM EETyes   
no /org/freedesktop/NetworkManager/Settings/2
   Wired connection 17ac79166-e72e-455b-ad9e-34574ee5d94e   
802-3-ethernet1395571025   Sun 23 Mar 2014 12:37:05 PM EETyes   
no /org/freedesktop/NetworkManager/Settings/1
   Egy Cloud 05f6b118-d332-4196-a7b0-810bba89bbf7   
802-11-wireless   1395753542   Tue 25 Mar 2014 03:19:02 PM EETyes   
no /org/freedesktop/NetworkManager/Settings/0
   AndroidAP 46037856-999f-4b3b-878d-13243f4ae958   
802-11-wireless   1395592043   Sun 23 Mar 2014 06:27:23 PM EETyes   
no /org/freedesktop/NetworkManager/Settings/3
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1297286/+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 1380480] Re: network disabled after suspend - resume

Original report of this bug suggests it is a kernel bug - later comment
about restart network manager is related to another report.

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  network disabled after suspend - resume

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  Background: 
  this started to happen after the upgrade to Utopic Beta 1

  3) When I close the laptop's lid and open, the wifi should reconnect
  4) Wifi does not reconnect. It says "Wi-Fi networks" - "disconnected" when I 
left-click on NM icon in notif area. However the context menu (right-click) has 
items "Enable networking" and "Enable Wi-Fi" both with checkmarks.

  Workarounds: 
  switch off - on the physical switch on laptop OR  two times go and select 
"Enable networking" in the NM context menu (after first time it removes 
checkmark and the  "Enable Wi-Fi" item - visual feedback of being disabled).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu27
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Oct 11 22:33:06 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-07-21 (447 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  IpRoute:
   default via 192.168.10.1 dev wlan0  proto static 
   10.9.9.0/24 dev vboxnet0  proto kernel  scope link  src 10.9.9.1 
   192.168.10.0/24 dev wlan0  proto kernel  scope link  src 192.168.10.239  
metric 9
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to utopic on 2014-09-25 (16 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-07-19T15:03:44.847279
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1380480/+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 1375191] Re: utopic: network-manager not started automatically on boot

Utopic is not supported anymore, if you still have this problem in a
supported release please open another report, thanks!

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  utopic: network-manager not started automatically on boot

Status in network-manager package in Ubuntu:
  Won't Fix

Bug description:
  After upgrading to utopic (around the time of when the final beta was
  out), network manager caesed to auto start on boot. I can however
  start it manually using "sudo service network-manager start". When
  this happended iI also noticed the automatic addition of 2 mins
  waiting time for network interfaces on each boot. Please, can the auto
  start behaviour be restored?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1375191/+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 1371481] Re: Network Manager's Upstart configuration is wrong - Network Manager doesn't start in case of faulty ifupdown configuration

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

** This bug has been marked a duplicate of bug 1375191
   utopic: network-manager not started automatically on boot

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

Title:
  Network Manager's Upstart configuration is wrong - Network Manager
  doesn't start in case of faulty ifupdown configuration

Status in One Hundred Papercuts:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hi everyone,

  If you add a faulty entry to ifupdown's configuration
  (/etc/network/interfaces or sourced in files) then Network Manager
  doesn't get started by Upstart.

  
  As an example add this block for a non-existent network interface to 
/etc/network/interfaces:
  auto bogus0
  iface bogus0 inet dhcp

  If you reboot your machine then Network Manager won't be started by
  Upstart.

  
  The issue with Network Manager's Upstart configuration is that it starts on 
the following condition:
  start on (local-filesystems
  and started dbus
  and static-network-up)

  This is wrong as the static-network-up event is never emitted in case the 
ifupdown configuration is (partially) invalid.
  In order to fix this issue please use the following start on condition:
  start on (local-filesystems
  and started dbus
  and started networking)

  
  This is an issue in all currently supported Ubuntu releases.
  Please let me know if you have any further questions.

  Best,

  Michael Schaller

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1371481/+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 1231964] Re: NetworkManager crashes in ofono plugin with phonesim [crashed with SIGSEGV in in ??()]

** Tags added: nm-touch

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

Title:
  NetworkManager crashes in ofono plugin with phonesim [crashed with
  SIGSEGV in  in ??()]

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  When I run ofono-phonesim on the G4 (mako), NetworkManager goes into
  an eternal crash/restart loop with this crash. After "sudo stop
  network-manager" and running it manually with "sudo
  /usr/sbin/NetworkManager --no-daemon" I see:

  
  NetworkManager[31290]:  /sys/devices/virtual/net/sit0: couldn't 
determine device driver; ignoring...
  NetworkManager[31290]:  (/phonesim): failed to look up interface index
  NetworkManager[31290]:  (/phonesim): new Ofono device (driver: 'ofono' 
ifindex: 0)
  NetworkManager[31290]:  (/phonesim): exported as 
/org/freedesktop/NetworkManager/Devices/1
  NetworkManager[31290]:  (/phonesim): device state change: unmanaged -> 
unavailable (reason 'managed') [10 20 2]
  NetworkManager[31290]:  (/phonesim): deactivating device (reason 
'managed') [2]
  NetworkManager[31290]:  (/phonesim) updated available interfaces
  NetworkManager[31290]:  WWAN now enabled by management service
  NetworkManager[31290]:  (/phonesim) marked enabled: 1
  NetworkManager[31290]:SCPlugin-Ofono: reading configuration for IMSI 
246813579
  NetworkManager[31290]:SCPlugin-Ofono: add context for 246813579
  NetworkManager[31290]:SCPlugin-Ofono: add property 'Name': Internet
  NetworkManager[31290]:SCPlugin-Ofono: add property 'AccessPointName': 
  NetworkManager[31290]:SCPlugin-Ofono: add property 'Username': 
  NetworkManager[31290]:SCPlugin-Ofono: add property 'Password': 
  NetworkManager[31290]:SCPlugin-Ofono: add property 'Type': internet
  NetworkManager[31290]:SCPlugin-Ofono: add property 'Protocol': ip
  NetworkManager[31290]:SCPlugin-Ofono: found internet context 'Internet' 
(context1)
  NetworkManager[31290]:  (wlan0) supports 5 scan SSIDs
  NetworkManager[31290]:  Trying to remove a non-existant call id.
  NetworkManager[31290]:  (wlan0): supplicant interface state: starting 
-> ready
  NetworkManager[31290]:  (wlan0): device state change: unavailable -> 
disconnected (reason 'supplicant-available') [20 30 42]
  NetworkManager[31290]:  (/phonesim): device state change: unavailable 
-> disconnected (reason 'none') [20 30 0]
  NetworkManager[31290]:  Auto-activating connection 
'/262026260068068/context1'.
  NetworkManager[31290]:  Activation (/phonesim) starting connection 
'/262026260068068/context1'
  NetworkManager[31290]:  (/phonesim): device state change: disconnected 
-> prepare (reason 'none') [30 40 0]
  NetworkManager[31290]:  Activation (/phonesim) Stage 1 of 5 (Device 
Prepare) scheduled...
  NetworkManager[31290]:  Activation (/phonesim) Stage 1 of 5 (Device 
Prepare) started...
  NetworkManager[31290]:  Activation (/phonesim) Stage 1 of 5 (Device 
Prepare) complete.
  NetworkManager[31290]:  (wlan0): supplicant interface state: ready -> 
inactive
  NetworkManager[31290]:  (wlan0) supports 5 scan SSIDs
  NetworkManager[31290]:  Activation (/phonesim) Stage 2 of 5 (Device 
Configure) scheduled...
  NetworkManager[31290]:  Activation (/phonesim) Stage 2 of 5 (Device 
Configure) starting...
  NetworkManager[31290]:  (/phonesim): device state change: prepare -> 
config (reason 'none') [40 50 0]
  NetworkManager[31290]:  Activation (/phonesim) Stage 2 of 5 (Device 
Configure) successful.
  NetworkManager[31290]:  Activation (/phonesim) Stage 3 of 5 (IP 
Configure Start) scheduled.
  NetworkManager[31290]:  Activation (/phonesim) Stage 2 of 5 (Device 
Configure) complete.
  NetworkManager[31290]:  Activation (/phonesim) Stage 3 of 5 (IP 
Configure Start) started...
  NetworkManager[31290]:  (/phonesim): device state change: config -> 
ip-config (reason 'none') [50 70 0]
  NetworkManager[31290]:  Activation (/phonesim) Stage 4 of 5 (IPv6 
Configure Timeout) scheduled...
  NetworkManager[31290]:  Activation (/phonesim) Stage 3 of 5 (IP 
Configure Start) complete.
  NetworkManager[31290]:  (/phonesim): IPv4 static configuration:

  (NetworkManager:31290): GLib-GObject-CRITICAL **: g_value_get_string:
  assertion 'G_VALUE_HOLDS_STRING (value)' failed

  Reproducer:
  - Take current phone build and put it into write mode
  - Install ofono-phonesim xvfb-run 
  - Edit /etc/ofono/phonesim.conf and enable the commented out phonesim stanza
  - sudo stop ofono
  - In ssh/terminal 1, start ofono (in the foreground): sudo ofonod -P ril -n
  - In ssh/terminal 2:
* start the simulator: xvfb-run -a ofono-phonesim -p 12345 
/usr/share/phonesim/default.xml &
* start the modem: /usr/share/ofono/scripts/enable-modem
* run NM: sudo /usr/sbin/NetworkManager --no-daemon

  This reproduces the crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: network-manager 0.9.8.0-0ubu

[Desktop-packages] [Bug 1391842] Re: Mobile broadband doesn't work in utopic (worked in trusty)

** Tags added: nm-touch

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

Title:
  Mobile broadband doesn't work in utopic (worked in trusty)

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I realized today that I can no longer use the 3G adapter in my laptop
  since upgrading to utopic. Please find attached a screenshot of the
  nm-applet menu - you'll notice that my adapter appears to be listed
  twice ("Mobile Broadband (Dell DW5560)" and "Mobile Broadband ()").

  Trying to enable mobile broadband and then clicking on
  "/234308387636800/context1" (what does that even mean?) results in a
  rather unhelpful error dialog (see the second screenshot).

  Trying to enable mobile broadband and then clicking on "New Mobile
  Broadband connection..." results in nothing happening except for that
  menu entry becoming checked. But no internet.

  I can't add a connection via "Edit Connections..." because no 3G
  devices are listed.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu28
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov 12 11:38:30 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-03-27 (594 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130326)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static 
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.6  metric 1 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.4  metric 
9 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to utopic on 2014-10-16 (26 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-11-10T11:46:12.030144
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   ttyACM1Unknown   disconnected  
/org/freedesktop/NetworkManager/Devices/3  
   /mbm_0 gsm   disconnected  
/org/freedesktop/NetworkManager/Devices/2  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1391842/+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 1650997] Re: h.264 video does not work though ffmpeg-extra is installed

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

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: chromium-browser (Ubuntu)
   Status: New => Confirmed

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

Title:
  h.264 video does not work though ffmpeg-extra is installed

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  I have the chromium-browser/chromium-codecs-ffmpeg-extra packages
  installed on Yakkety. As of the recent upgrade to Chromium version 55
  which fixed HTTPS issues, H.264 video is no longer working. Indeed
  https://www.youtube.com/html5 reports that it is not supported. I've
  tried installing the x264 and ubuntu-restricted-extras packages, but
  that did not solve the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1650997/+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 1448567] Re: Ubuntu 15.04 - Macbook Pro Early 2015 (12, 1) no 5 GHz wireless

** Package changed: network-manager (Ubuntu) => linux (Ubuntu)

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

Title:
  Ubuntu 15.04 - Macbook Pro Early 2015 (12,1) no 5 GHz wireless

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of 15.04 on a Macbook Pro 12,1.

  >Network controller [0280]: Broadcom Corporation BCM43602 802.11ac
  Wireless LAN SoC [14e4:43ba] (rev 01)

  I copied brcmfmac43602-pcie.bin
  (https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-
  firmware.git/plain/brcm/) into /lib/firmware/brcm which enabled the
  wireless to pick up some SSIDs, but not all (almost positive the only
  ones seen are 2.4GHz).

  ---

  I was referred to this document:
  https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx

  Then I ran:

  $ lspci -vvnn | grep -A 9 Network
  03:00.0 Network controller [0280]: Broadcom Corporation BCM43602 802.11ac 
Wireless LAN SoC [14e4:43ba] (rev 01)
   Subsystem: Apple Inc. Device [106b:0133]
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: brcmfmac

  I find the PCI device ID here:
  https://wireless.wiki.kernel.org/en/users/Drivers/brcm80211#brcmfmac
  (Chipset BCM43602, ID: 14e4:43ba)

  I dropped the relevant firmware files from the repo given a bit
  further down that page (repo:
  https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-
  firmware.git/tree/brcm) into /lib/firmware/brcm/

  ...still no 5 GHz.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1448567/+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 1444311] Re: Problems switching between WiFi and Mobile Data on Nexus 5 (vivid-proposed)

** Tags added: nm-touch

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

Title:
  Problems switching between WiFi and Mobile Data on Nexus 5 (vivid-
  proposed)

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I suppose this bug is very similar to 
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1426122 , but I 
can't give such kind of technical information.
  I just can repeat from that bug:

  On recent vivid images running on Nexus 5 switching between WiFi and
  mobile-data and back leads to broken networking where  device can't
  establish a network connection.

  This bug was discovered on ubuntu-touch/vivid-proposed #169-172.
  And this bug is absent on ubuntu-touch/ubuntu-rtm/14.09 #17.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1444311/+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 1407907] Re: [phone] Leaving WiFi coverage often leads to the password dialog being displayed indefinitely

** Tags added: nm-touch

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

Title:
  [phone] Leaving WiFi coverage often leads to the password dialog being
  displayed indefinitely

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Steps:
  * connect to a password-protected WiFi network
  * suspend the phone
  * turn the WiFi off or leave the network's covered area
  * resume the phone

  Expected:
  * phone is connected via a GSM data connection

  Current:
  * phone is connected via a GSM data connection
  * there is a WiFi password dialog displayed for a network that isn't in range 
any more (and for which the password is known)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-network 0.5.1+15.04.20141216-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.15-0ubuntu3
  Architecture: armhf
  Date: Tue Jan  6 10:19:05 2015
  InstallationDate: Installed on 2014-12-18 (19 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20141218-020204)
  SourcePackage: indicator-network
  UpgradeStatus: No upgrade log present (probably fresh install)

  : "If the
  network stops being available while the dialog is still open — for
  example, if the network is no longer in range, or if you switch into
  Flight Mode — the commit buttons should be replaced by the centered
  text “Network no longer available”, all the dialog’s controls should
  become insensitive, and two seconds later, the dialog should close."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1407907/+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 1450066] Re: IPv6 hop limit set to 0

Vivid is not supported anymore, closing as Won't Fix. However this bug
should be fixed in later Ubuntu releases already.

** Bug watch added: GNOME Bug Tracker #737252
   https://bugzilla.gnome.org/show_bug.cgi?id=737252

** Also affects: network-manager via
   https://bugzilla.gnome.org/show_bug.cgi?id=737252
   Importance: Unknown
   Status: Unknown

** Bug watch added: Debian Bug tracker #756534
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756534

** Also affects: network-manager (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756534
   Importance: Unknown
   Status: Unknown

** Changed in: network-manager (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: network-manager (Ubuntu Vivid)
   Status: Triaged => Won't Fix

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

Title:
  IPv6 hop limit set to 0

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Vivid:
  Won't Fix
Status in network-manager package in Debian:
  Unknown

Bug description:
  On upgrading from Ubuntu 14.10 to 15.04 I found that my IPv6
  networking no longer worked. It turned out that this was because my
  hop limit was set to zero:

  # sysctl -a | fgrep eth0.hop_limit
  net.ipv6.conf.eth0.hop_limit = 0

  which in turn seems to have been cause by a known problem in the
  network manager:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756534
  https://bugzilla.gnome.org/show_bug.cgi?id=737252

  Since this has already been fixed in the GNOME project, can Ubuntu
  15.04 please take the upstream fix?

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1450066/+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 1467457] Re: setting for automatic connection can't be saved

Vivid is no longer supported, thus closing as Won't Fix, however this
bug should be fixed in later Ubuntu releases.

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  setting for automatic connection can't be saved

Status in network-manager package in Ubuntu:
  Won't Fix

Bug description:
  The "Save" button is disabled. There's no reason to prevent saving the
  setting for automatic connection to a network regardless whether the
  network is used or not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  Uname: Linux 4.0.5-040005-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jun 22 12:14:15 2015
  InstallationDate: Installed on 2015-06-08 (13 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.43.1 dev wlan0  proto static  metric 1024 
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.43.0/24 dev wlan0  proto kernel  scope link  src 192.168.43.102
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-06-09 (13 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-06-08T14:26:05.824491
  nmcli-dev:
   GERÄT  TYP   STATUS   DBUS-PFAD 
 VERBINDUNG CON-UUID  CON-PFAD  
 
   wlan0  wifi  verbunden/org/freedesktop/NetworkManager/Devices/2  
STYLUS iDroid SP 1001  ca4ffca3-362b-4e6e-8847-6bb85b090be1  
/org/freedesktop/NetworkManager/ActiveConnection/8 
   eth0   ethernet  nicht verfügbar  /org/freedesktop/NetworkManager/Devices/1  
-- ---- 

   lo loopback  nicht verwaltet  /org/freedesktop/NetworkManager/Devices/0  
-- ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Fehler: Objekt »nm« ist unbekannt, versuchen Sie »nmcli help«.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1467457/+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 1580146] Re: [touch] Internet connection stops working while WiFi is still connected

** Tags added: nm-touch

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

Title:
  [touch] Internet connection stops working while WiFi is still
  connected

Status in Canonical System Image:
  Incomplete
Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  krillin, rc-proposed, r329

  Description:
  It often happens that the internet connection stops working while the device 
is still connected to a (working) WiFi AP.
  The indicator shows that the phone is connected to the AP, here's the ouput 
of "nmcli d" and "nmcli c" http://pastebin.ubuntu.com/16344985/

  Tapping on the AP in the network indicator resets the connection and
  fixes the issue, which however reappears after a while.

  Here's also a "grep NetworkManager" from syslog
  http://pastebin.ubuntu.com/16344990/

  How to reproduce:
  I don't have a recipe, but here's what usually happens on my phone
  1) I connect to the office WiFi (Canonical's HQ, BlueFin office)
  2) Use browser, perform random google searches to check internet is working
  3) After a while (sometimes I put the phone to sleep, sometimes I checked the 
Updates from system settings a few times), I go back to the browser, and it 
starts returning "Network Error". NM, as you can see from the logs, says WiFi 
is "connected"
  4) At this point I use Terminal app and discover that "ping 8.8.8.8" is 
working correctly, "ping google.com" immediately returns "unkown host", i.e. it 
doesn't seem to be waiting for a timeout, it returns pretty fast.

  There are no related crash files in /var/crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580146/+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 1571886] Re: NM 1.1.93 in xenial silently loses wifi connection (no GUI feedback)

Should be fixed in 1.2.2 SRU.

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  NM 1.1.93 in xenial silently loses wifi connection (no GUI feedback)

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  Twice today, NM 1.1.93 has dropped my wifi connection.  I don't know
  why and haven't looked; the connection is usually stable since the AP
  is in the room with my laptop, but perhaps there's something up with
  the kernel I'm currently running.

  However, the serious bug that I'm reporting is that when the wifi
  connection dropped, nothing told me that this had happened.  nm-
  applet's display did not update; there was no automatic reconnect
  attempt; even the VPN process, which was no longer operational because
  it had lost its route to the VPN endpoint, was still running (and the
  lock icon still shown on nm-applet).

  Only when I looked at my routing table to see what was going on did
  the problem become apparent.

  Since this has already happened twice today, I can probably get more
  debugging information "soon" if needed - just ask.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 18 15:39:18 2016
  InstallationDate: Installed on 2010-09-24 (2033 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WWanEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to xenial on 2016-04-15 (3 days ago)
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1571886/+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 1644813] Re: Simple Scan uses a headerbar in Cinnamon

2016-12-20 Thread Clement Lefebvre

Thanks Robert.

It would be useful in Xenial if possible.

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

Title:
  Simple Scan uses a headerbar in Cinnamon

Status in Simple Scan:
  Fix Released
Status in simple-scan package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  Please add Cinnamon to the list of DEs where a headerbar shouldn't be
  used. It doesn't fit that environment.

  In src/ui.vala's load() function:

  if (is_desktop ("Unity") || is_desktop ("XFCE") || is_desktop ("MATE")
  || is_desktop ("LXDE"))

  should be:

  if (is_desktop ("Unity") || is_desktop ("XFCE") || is_desktop ("MATE")
  || is_desktop ("LXDE") || is_desktop ("X-Cinnamon") || is_desktop
  ("Cinnamon"))

  To reproduce, run:

  XDG_CURRENT_DESKTOP="X-Cinnamon" simple-scan

  The expected result is a traditional titlebar+menubar, not a
  headerbar.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/simple-scan/+bug/1644813/+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 1584970] Re: Ubuntu tries to set up my USB wireless device on a wired connection

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

** Bug watch added: GNOME Bug Tracker #764803
   https://bugzilla.gnome.org/show_bug.cgi?id=764803

** Also affects: network-manager via
   https://bugzilla.gnome.org/show_bug.cgi?id=764803
   Importance: Unknown
   Status: Unknown

** This bug has been marked a duplicate of bug 1574347
   [SRU] Re-read the link type if the name changed

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

Title:
  Ubuntu tries to set up my USB wireless device on a wired connection

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  New

Bug description:
  When I start up from a Ubuntu 16.04 Live CD, I do not get a wireless
  network connection, instead it seems to see my USB device (a Belkin
  F5D8053 N Wireless USB Adapter) as a "wired connection".

  If I do 'service network-manager restart', or unplug and replug the
  device, then it sets it up with the rt2800usb driver, gives it a
  wireless connection, and allows me to connect to wifi routers as
  normal.

  A potentially similar issue has been reported with a GB-WB867D-I card
  at http://askubuntu.com/questions/758422/ubuntu-16-04-seeing-my-
  wireless-card-as-wired

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.376
  CurrentDesktop: Unity
  Date: Mon May 23 22:02:27 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   10.42.0.0/24 dev enp0s25  proto kernel  scope link  src 10.42.0.1  metric 
100 
   169.254.0.0/16 dev enp0s25  scope link  metric 1000
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH
   Wired connection 1  d553ccd9-63fb-494a-8ec6-59adc51a67f6  802-3-ethernet  
1464040759  Mon 23 May 2016 09:59:19 PM UTC  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  yes enp0s25  
activated  /org/freedesktop/NetworkManager/ActiveConnection/3 
   Wired connection 2  b35063c3-365d-4287-85b2-882e449f4d13  802-3-ethernet  
1464040460  Mon 23 May 2016 09:54:20 PM UTC  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/1  no  --   --   
  --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH
  CONNECTION  CON-UUID  CON-PATH
   
   enp0s25  ethernet  connected
/org/freedesktop/NetworkManager/Devices/0  Wired connection 1  
d553ccd9-63fb-494a-8ec6-59adc51a67f6  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   wlx002275911486  ethernet  unavailable  
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
   lo   loopback  unmanaged
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1584970/+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 1651418] [NEW] Qt-based application tray icons are broken on resume from suspend

2016-12-20 Thread Robert Orzanna

Public bug reported:

Dear all,

I am seeking for some assistance and clarification if I am the only one
affected by this or not.

On resume from suspend, tray icons of Qt-based applications are broken
(see attached screenshot).

Example applications that are affected: Franz, Skype, SMplayer.

Can anyone reproduce a similar issue?

Am I missing a particular package?

Yours,

-Robert

Ubuntu 16.10

sni-qt is already the newest version (0.2.7+15.10.20150729-0ubuntu1).
sni-qt:i386 is already the newest version (0.2.7+15.10.20150729-0ubuntu1).

** Affects: sni-qt (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/bugs/1651418/+attachment/4794266/+files/qt-icon.png

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

Title:
  Qt-based application tray icons are broken on resume from suspend

Status in sni-qt package in Ubuntu:
  New

Bug description:
  Dear all,

  I am seeking for some assistance and clarification if I am the only
  one affected by this or not.

  On resume from suspend, tray icons of Qt-based applications are broken
  (see attached screenshot).

  Example applications that are affected: Franz, Skype, SMplayer.

  Can anyone reproduce a similar issue?

  Am I missing a particular package?

  Yours,

  -Robert

  Ubuntu 16.10

  sni-qt is already the newest version (0.2.7+15.10.20150729-0ubuntu1).
  sni-qt:i386 is already the newest version (0.2.7+15.10.20150729-0ubuntu1).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sni-qt/+bug/1651418/+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 1647283] Re: WiFi being detected as ethernet when race condition on renaming for persistent name

The fix is included in upstream 1.4.4 release, an update will be pushed
soon.

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

** Changed in: network-manager (Ubuntu)
   Status: New => Triaged

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

Title:
  WiFi being detected as ethernet when race condition on renaming for
  persistent name

Status in HWE Next:
  New
Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  
  Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613

  Version: NetworkManager 1.4.2

  This bug happens after power-on with probability about 1/50.
  That means we need to reboot about 50 times to get into the buggy situation.
  "nmcli d" shows the device type is ethernet:

  DEVICE   TYPE  STATECONNECTION 
  wlp1s0   ethernet  unavailable  --
  lo   loopback  unmanaged-- 

  The bug starts from a race condition. But it is not the root cause.
  I've also attach 2 logs. One is in good situation. Another is in bad 
situation.
  This log is generated by applying a "log patch" to network-manager 1.4.2 so 
we can see more stuff.

  In the bad situation. The bug starts with race condition. But the race 
condition is not the root cause. The race condition is:
   * During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared.
   * Inside the NM, it is still using "wlan0" in "_linktype_get_type()".
   * Since /sys/class/net/wlan0/uevent is disappeared. so the type matching 
failed in _linktype_get_type().
   * Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 
disappeared.
   * And finally, devtype and kind are both NULL, so it returns 
NM_LINK_TYPE_ETHERNET for wlan0.

  Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit 
the type so it is still type ethernet.
  But from the log, I saw _linktype_get_type() is called several times later 
and return the correct type (wifi). But just, "nmcli d" still shows type 
ethernet.

  I'm wondering if we are missing to update the type in the Object
  created after renaming and re-detecting the type.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1647283/+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 1450066] Re: IPv6 hop limit set to 0

2016-12-20 Thread Bug Watch Updater

** Changed in: network-manager (Debian)
   Status: Unknown => New

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

Title:
  IPv6 hop limit set to 0

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Vivid:
  Won't Fix
Status in network-manager package in Debian:
  New

Bug description:
  On upgrading from Ubuntu 14.10 to 15.04 I found that my IPv6
  networking no longer worked. It turned out that this was because my
  hop limit was set to zero:

  # sysctl -a | fgrep eth0.hop_limit
  net.ipv6.conf.eth0.hop_limit = 0

  which in turn seems to have been cause by a known problem in the
  network manager:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756534
  https://bugzilla.gnome.org/show_bug.cgi?id=737252

  Since this has already been fixed in the GNOME project, can Ubuntu
  15.04 please take the upstream fix?

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1450066/+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 1450066] Re: IPv6 hop limit set to 0

2016-12-20 Thread Bug Watch Updater

** Changed in: network-manager
   Status: Unknown => Fix Released

** Changed in: network-manager
   Importance: Unknown => Critical

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

Title:
  IPv6 hop limit set to 0

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Vivid:
  Won't Fix
Status in network-manager package in Debian:
  New

Bug description:
  On upgrading from Ubuntu 14.10 to 15.04 I found that my IPv6
  networking no longer worked. It turned out that this was because my
  hop limit was set to zero:

  # sysctl -a | fgrep eth0.hop_limit
  net.ipv6.conf.eth0.hop_limit = 0

  which in turn seems to have been cause by a known problem in the
  network manager:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756534
  https://bugzilla.gnome.org/show_bug.cgi?id=737252

  Since this has already been fixed in the GNOME project, can Ubuntu
  15.04 please take the upstream fix?

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1450066/+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 1651425] [NEW] Adjust area of screenshot

2016-12-20 Thread johnmne

Public bug reported:

** This is a feature request. **

Please enable to adjust the area of screenshot after that it was chosen.

For example when I take a screenshot using keyboard shortcut: "CTRL" + "SHIFT" 
+ "Print Screen" , then I have only one chance to choose the right 
coordinates/area for the screenshot.
But sometimes I wish to further adjust the area of the screenshot.

Using Ubuntu 16.04.

** Affects: gnome-screenshot (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Adjust area of screenshot

Status in gnome-screenshot package in Ubuntu:
  New

Bug description:
  ** This is a feature request. **

  Please enable to adjust the area of screenshot after that it was
  chosen.

  For example when I take a screenshot using keyboard shortcut: "CTRL" + 
"SHIFT" + "Print Screen" , then I have only one chance to choose the right 
coordinates/area for the screenshot.
  But sometimes I wish to further adjust the area of the screenshot.

  Using Ubuntu 16.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1651425/+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 1646574] Re: Mouse cursor invisible or does not move

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: xserver-xorg-video-nouveau (Ubuntu)
   Status: New => Confirmed

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

Title:
  Mouse cursor invisible or does not move

Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  When using nouveau driver for my GTX 1070 (mobile) the mouse cursor is fixed 
in left upper corner or sometimes disappear. I actually can click or hover 
everywhere on the screen, I just don't know where the mouse is pointer at the 
moment.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroRelease: Ubuntu 16.10
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-27-generic, x86_64: installed
   bbswitch, 0.8, 4.9.0-040900rc7-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP104M [GeForce GTX 1070] [10de:1be1] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer GP104M [GeForce GTX 1070] [1558:6a04]
  InstallationDate: Installed on 2016-11-26 (5 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 002: ID ffc0:0040  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook P65_67RSRP
  Package: xserver-xorg-video-nouveau 1:1.0.12-2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed 
root=UUID=a596a1fd-2912-4a20-a48c-6b8a32078b5c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Tags:  yakkety ubuntu
  Uname: Linux 4.8.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/24/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.03
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd08/24/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1646574/+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 1370277] Re: Wrong handle of staple with multiple copies

2016-12-20 Thread Iván-Benjamín García Torà

This bug still applies, to other printers like the HP m604dn.
Check this for a workaround printing from command line in a loop
http://soc.ninja/documentation/printing-and-staple-multiple-copies-properly/

** Changed in: cups-filters (Ubuntu)
   Status: New => Confirmed

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

Title:
  Wrong handle of staple with multiple copies

Status in cups-filters package in Ubuntu:
  Confirmed

Bug description:
  Printers like the Canon iR C3220 can staple the documents after
  printing. When I print a document more than one and  it contains 10
  pages it should print the 10 pages of the document, staple it, print
  again the 10 pages of the document, staple it, and so on. Instead of
  this it prints all copies of the document correctly sorted (1-10, 1-10
  etc) and staple it at the end, if all copies are printed.

  This is with printing a PDF file from evince. Also if printing from
  Libre Office, if Libre Office' output is PDF. If the output is
  PostScript, the printer is stapling correctly after each 10 pages of
  the document. The output format from Libre Office is configured in
  /etc/libreoffice/psprint.conf.

  I assume that pstops does not do the same as pdftopdf does. But this
  is only a presumption.

  Description:  Ubuntu 12.04.5 LTS
  Release:  12.04

  cups-filters:
Installiert: 1.0.18-0ubuntu0.2
Kandidat:1.0.18-0ubuntu0.2
Versionstabelle:
   *** 1.0.18-0ubuntu0.2 0
  500 http://ch.archive.ubuntu.com/ubuntu/ precise-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.0.17-0bzr0.1 0
  500 http://ch.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1370277/+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 738063] Re: gnome-keyring-daemon assertion failures when changing password remotely

2016-12-20 Thread Damiön la Bagh

Problem still exists in Trusty:

Dec 20 13:17:37 hostname gnome-keyring-daemon[24288]: Gck: gck_module_new: 
assertion 'funcs != NULL' failed
Dec 20 13:17:37 hostname gnome-keyring-daemon[24288]: module_instances: 
assertion 'module' failed
Dec 20 13:17:37 hostname gnome-keyring-daemon[24288]: egg_error_message: 
assertion 'error' failed
Dec 20 13:17:37 hostname gnome-keyring-daemon[24288]: couldn't find secret 
store module: (unknown)
Dec 20 13:17:37 hostname gnome-keyring-daemon[24288]: lookup_login_keyring: 
assertion 'GCK_IS_SESSION (session)' failed
Dec 20 13:17:37 hostname gnome-keyring-daemon[24288]: create_credential: 
assertion 'GCK_IS_SESSION (session)' failed
Dec 20 13:17:37 hostname gnome-keyring-daemon[24288]: egg_error_message: 
assertion 'error' failed
Dec 20 13:17:37 hostname gnome-keyring-daemon[24288]: couldn't create new login 
credential: (unknown)
Dec 20 13:17:37 hostname passwd[23986]: gkr-pam: couldn't change password for 
the login keyring: the passwords didn't match.

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

Title:
  gnome-keyring-daemon assertion failures when changing password
  remotely

Status in gnome-keyring package in Ubuntu:
  Expired

Bug description:
  Binary package hint: gnome-keyring

  Changing password remotely results in the following assertion failures
  in auth.log:

  Mar 19 09:49:18 gx1 passwd[17883]: pam_unix(passwd:chauthtok): password 
changed for test123
  Mar 19 09:49:18 gx1 gnome-keyring-daemon[17886]: gp11_module_get_slots: 
assertion `data->funcs' failed
  Mar 19 09:49:18 gx1 gnome-keyring-daemon[17886]: lookup_login_session: 
assertion `slot' failed
  Mar 19 09:49:18 gx1 gnome-keyring-daemon[17886]: lookup_login_keyring: 
assertion `GP11_IS_SESSION (session)' failed
  Mar 19 09:49:18 gx1 gnome-keyring-daemon[17886]: create_credential: assertion 
`GP11_IS_SESSION (session)' failed
  Mar 19 09:49:18 gx1 gnome-keyring-daemon[17886]: egg_error_message: assertion 
`error' failed
  Mar 19 09:49:18 gx1 gnome-keyring-daemon[17886]: couldn't create new login 
credential: (unknown)
  Mar 19 09:49:18 gx1 passwd[17883]: gkr-pam: couldn't change password for the 
login keyring: the passwords didn't match.
  Mar 19 09:49:18 gx1 passwd[17883]: Passphrase file wrapped

  Mar 19 09:55:57 gx1 passwd[18305]: pam_unix(passwd:chauthtok): password 
changed for test124
  Mar 19 09:55:57 gx1 gnome-keyring-daemon[18309]: gp11_module_get_slots: 
assertion `data->funcs' failed
  Mar 19 09:55:57 gx1 gnome-keyring-daemon[18309]: lookup_login_session: 
assertion `slot' failed
  Mar 19 09:55:57 gx1 gnome-keyring-daemon[18309]: lookup_login_keyring: 
assertion `GP11_IS_SESSION (session)' failed
  Mar 19 09:55:57 gx1 gnome-keyring-daemon[18309]: create_credential: assertion 
`GP11_IS_SESSION (session)' failed
  Mar 19 09:55:57 gx1 gnome-keyring-daemon[18309]: egg_error_message: assertion 
`error' failed
  Mar 19 09:55:57 gx1 gnome-keyring-daemon[18309]: couldn't create new login 
credential: (unknown)
  Mar 19 09:55:57 gx1 passwd[18305]: gkr-pam: couldn't change password for the 
login keyring: the passwords didn't match.
  Mar 19 09:55:57 gx1 passwd[18305]: Passphrase file wrapped

  
  To reproduce:
  sudo adduser --encrypt-home test123
  sudo adduser test124

  ssh in as both users created above, run passwd and change the
  password. Have not tested behaviour without ecryptfs-utils installed,
  but it should be unrelated since both encrypted and unencrypted
  homedirs behaved the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gnome-keyring 2.92.92.is.2.30.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12
  Uname: Linux 2.6.32-28-generic i686
  Architecture: i386
  CheckboxSubmission: bc3a49cd6e76f0d54c8965120b490eef
  CheckboxSystem: abf102d6ef41328208f5c1554651535a
  Date: Sat Mar 19 09:51:57 2011
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  SourcePackage: gnome-keyring

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/738063/+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 1651428] [NEW] No sound on bluetooth headset in A2DP mode on connect

2016-12-20 Thread hife

Public bug reported:

System: Ubuntu 16.04.1 LTS
Package: pulseaudio 
Version: 1:8.0-0ubuntu3.1

I am using module-switch-on-connect to automatically connect to bluetooth 
headsets.
After connecting a bluetooth headset in A2DP mode, no sound is played (on any 
output device). If I then switch to HSP/HPF mode, it works, but switching back 
to A2DP mode fails completely (when selecting A2DP from the dropdown menu in 
the audio settings, the output sink switches to internal audio and when 
reselecting bluetooth it is again in HSP/HPF mode).

When connecting in HSP/HPF mode and then switching to A2DP mode, it
works fine, even when switching back and forth between them.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
Uname: Linux 4.4.0-57-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC1D0c:   josias 2669 F...m pulseaudio
 /dev/snd/controlC1:  josias 2669 F pulseaudio
 /dev/snd/controlC0:  josias 2669 F pulseaudio
CurrentDesktop: Unity
Date: Tue Dec 20 13:22:08 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-06-15 (553 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to xenial on 2016-08-05 (137 days ago)
dmi.bios.date: 05/05/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: J9ET99WW (2.19 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20C6A0JQGE
dmi.board.vendor: LENOVO
dmi.board.version: 0B98405 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrJ9ET99WW(2.19):bd05/05/2015:svnLENOVO:pn20C6A0JQGE:pvrThinkPadEdgeE540:rvnLENOVO:rn20C6A0JQGE:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20C6A0JQGE
dmi.product.version: ThinkPad Edge E540
dmi.sys.vendor: LENOVO
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.default.pa: 2016-09-10T08:00:05.052185

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


** Tags: amd64 apport-bug xenial

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

Title:
  No sound on bluetooth headset in A2DP mode on connect

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  System: Ubuntu 16.04.1 LTS
  Package: pulseaudio 
  Version: 1:8.0-0ubuntu3.1

  I am using module-switch-on-connect to automatically connect to bluetooth 
headsets.
  After connecting a bluetooth headset in A2DP mode, no sound is played (on any 
output device). If I then switch to HSP/HPF mode, it works, but switching back 
to A2DP mode fails completely (when selecting A2DP from the dropdown menu in 
the audio settings, the output sink switches to internal audio and when 
reselecting bluetooth it is again in HSP/HPF mode).

  When connecting in HSP/HPF mode and then switching to A2DP mode, it
  works fine, even when switching back and forth between them.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   josias 2669 F...m pulseaudio
   /dev/snd/controlC1:  josias 2669 F pulseaudio
   /dev/snd/controlC0:  josias 2669 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Dec 20 13:22:08 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-06-15 (553 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to xenial on 2016-08-05 (137 days ago)
  dmi.bios.date: 05/05/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J9ET99WW (2.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C6A0JQGE
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98405 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ9ET99WW(2.19):bd05/05/2015:svnLENOVO:pn20C6A0JQGE:pvrThinkPadEdgeE540:rvnLENOVO:rn20C6A0JQGE:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C6A0JQGE
  dmi.product.version: ThinkPad Edge E540
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2016-09-10T08:00:05.052185

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

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

[Desktop-packages] [Bug 1646574] Re: Mouse cursor invisible or does not move

2016-12-20 Thread Johan Ferner

I first see this in the installer and that makes installing Ubuntu a 
challenge... 
The cursor does move but is invisible so you can kind of guess where you are 
supposed to click.
After installing the problem is still present.

Hardware is GTX 1080 on a desktop.

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

Title:
  Mouse cursor invisible or does not move

Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  When using nouveau driver for my GTX 1070 (mobile) the mouse cursor is fixed 
in left upper corner or sometimes disappear. I actually can click or hover 
everywhere on the screen, I just don't know where the mouse is pointer at the 
moment.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroRelease: Ubuntu 16.10
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-27-generic, x86_64: installed
   bbswitch, 0.8, 4.9.0-040900rc7-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP104M [GeForce GTX 1070] [10de:1be1] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer GP104M [GeForce GTX 1070] [1558:6a04]
  InstallationDate: Installed on 2016-11-26 (5 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 002: ID ffc0:0040  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook P65_67RSRP
  Package: xserver-xorg-video-nouveau 1:1.0.12-2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed 
root=UUID=a596a1fd-2912-4a20-a48c-6b8a32078b5c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Tags:  yakkety ubuntu
  Uname: Linux 4.8.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/24/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.03
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd08/24/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1646574/+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 1489651] Re: Bluetooth audio not working (with GDM?)

2016-12-20 Thread Olivier Berger

** Bug watch added: Debian Bug tracker #805414
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805414

** Also affects: gdm3 (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805414
   Importance: Unknown
   Status: Unknown

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

Title:
  Bluetooth audio not working (with GDM?)

Status in Ubuntu GNOME:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in gdm3 package in Debian:
  Unknown

Bug description:
  I'm having problems with a Marshall Stanmore bluetooth speaker in
  Ubuntu GNOME 15.10 Beta.  It pairs fine and is listed as a bluetooth
  device but won't show up in the audio settings as a device nor will it
  show up with pactl list. I also had this problem in Ubuntu GNOME 15.04
  with the gnome-staging 3.16 ppa. It works fine with stock Ubuntu GNOME
  15.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1489651/+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 1639180] Re: no login possible after update to nvidia 304.132

2016-12-20 Thread Oleksandr Pikozh

The workaround of using nvidia-304.134 from the graphics-drivers ppa
works fo me too (Ubuntu 16.04.1 LTS, linux x86_64 4.4.0-53-generic).

@skgary, you mean that you can't do `sudo apt-get install
nvidia-304=304.131-0ubuntu3`?

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1591547] Re: Merge pcsc-lite 1.8.17-1 (main) from Debian testing (main)

2016-12-20 Thread Amr Ibrahim

Ping!

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

Title:
  Merge pcsc-lite 1.8.17-1 (main) from Debian testing (main)

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  Please merge pcsc-lite 1.8.17-1 (main) from Debian testing (main)

  1.8.17: Ludovic Rousseau
  29 May 2016
  - Fix SCardEndTransaction() issue with a SCARD_SHARE_EXCLUSIVE connection
  - Fix an issue when used with systemd (problem in signal handler)
  - SCardGetAttrib(): set pcbAttrLen when buffer is too small
  - Doxygen: SCardGetAttrib() pbAttr can be NULL
  - Doxygen: SCardGetAttrib() *pcbAttrLen contains the buffer size
  - fix compilation warnings and link errors on SunOS
  - Some other minor improvements

  
  1.8.16: Ludovic Rousseau
  20 March 2016
  - SCardCancel() was not correctly handled
When a SCardGetStatusChange() was cancelled then a next PC/SC call
after the SCardGetStatusChange() may fail with a strange error code if
the event waited in SCardGetStatusChange() occurs.
  - Doxygen: fix different documentation issues
  - SCARD_SCOPE_GLOBAL is now defined in a public header (even if never used)
  - Enable Trace and Profile features using compiler flags and without
modifying the source code
  - Some other minor improvements and bug corrections

  
  1.8.15: Ludovic Rousseau
  25 December 2015
  - Add support of remove and/or customize PC/SC reader names using
PCSCLITE_FILTER_IGNORE_READER_NAMES and PCSCLITE_FILTER_EXTEND_READER_NAMES
See 
http://ludovicrousseau.blogspot.fr/2015/12/remove-andor-customize-pcsc-reader-names.html
  - Some other minor improvements and bug corrections
  -

  Explanation of the Ubuntu delta:
* Merge new upstream release from Debian Unstable (LP: #1483750).
  - debian/rules: Move runtime libraries to /lib, for the benefit of
wpasupplicant. (See Debian #531592)

  Sorry, my packaging skills are zero, so that I can't work on this merge.
  -

  Changelog entries since current yakkety version 1.8.14-1ubuntu1:

  pcsc-lite (1.8.17-1) unstable; urgency=medium

* New upstream release
* debian/control: Standards-Version: 3.9.7 -> 3.9.8. No change needed.

   -- Ludovic Rousseau   Sun, 29 May 2016 17:30:12
  +0200

  pcsc-lite (1.8.16-1) unstable; urgency=medium

* New upstream release
* debian/control: fix lintian warning vcs-field-uses-insecure-uri 
vcs-browser
  Use https:// instead of http://
* debian/control: Standards-Version: 3.9.6 -> 3.9.7. No change needed.
* debian/rules: use "hardening=+all" to harden even more the binaries

   -- Ludovic Rousseau   Sun, 20 Mar 2016 17:28:29
  +0100

  pcsc-lite (1.8.15-1) unstable; urgency=medium

* New upstream release

   -- Ludovic Rousseau   Fri, 25 Dec 2015 21:28:30
  +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1591547/+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 1651399] Re: LPR command to use PDF page size while printing

2016-12-20 Thread Purnima C Naik

** Tags added: pdf printing

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

Title:
  LPR command to use PDF page size while printing

Status in cups package in Ubuntu:
  New

Bug description:
  I am doing receipt printing by creating PDF file.

  The size of my receipt PDF is dynamic.

  Currently, the LPR command which I am using for getting this printed
  is as follows:

  lpr -P "ReceiptPrinter" -o PageSize=Custom.20x6cm 
"/home/ubuntu/Desktop/Punu1/iText123.pdf"
  I am required to pass custom size, as LPR command is not taking PDF page size 
during printing.

  But passing of custom size, is not helpful to me, as size of my
  receipt keeps on changing.

  Can someone please tell me, how can I set printer page size to PDF
  page size in LPR command?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1651399/+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 1579505] Re: [SRU] Update to 1.28.3 in Xenial

2016-12-20 Thread Amr Ibrahim

Ping!

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

Title:
  [SRU] Update to 1.28.3 in Xenial

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  [Description]

  Upstream have released a new bugfix release 1.28.3.

  [Changes]

  https://git.gnome.org/browse/gvfs/tree/NEWS?h=gnome-3-20

  Major changes in 1.28.3
  ===
  * dnssd: Fix crashes when mount failed
  * gvfs-open: Fix spawning of applications with dashses in their app IDs
  * daemon: Fix crashes caused by NULL certificates
  * afc: Many fixes for iOS support
  * client: Fix missing mount prefix in cached fuse paths
  * dav: Fix IPv6 address handling
  * Translation updates

  [QA, testing, regression potential]

  Under the GNOME MRE, you can believe all bugs upstream says are fixed
  are really fixed. Just test the system and make sure there are no
  regressions (e.g. look at errors.ubuntu.com).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1579505/+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 1380480] Re: network disabled after suspend - resume

2016-12-20 Thread Hans Deragon

@Aron Xu, I can you be sure the problem is not Network Manager related?
I do not say you are wrong, but could you point to some evidence that
the Network Manager is not involved with this?  Searching through the
comments, the word 'kernel' does not show often and none suggest that
the problem is within the kernel per say.  I believe that you are
closing the issue on the Network Manager hastily.

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

Title:
  network disabled after suspend - resume

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  Background: 
  this started to happen after the upgrade to Utopic Beta 1

  3) When I close the laptop's lid and open, the wifi should reconnect
  4) Wifi does not reconnect. It says "Wi-Fi networks" - "disconnected" when I 
left-click on NM icon in notif area. However the context menu (right-click) has 
items "Enable networking" and "Enable Wi-Fi" both with checkmarks.

  Workarounds: 
  switch off - on the physical switch on laptop OR  two times go and select 
"Enable networking" in the NM context menu (after first time it removes 
checkmark and the  "Enable Wi-Fi" item - visual feedback of being disabled).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu27
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Oct 11 22:33:06 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-07-21 (447 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  IpRoute:
   default via 192.168.10.1 dev wlan0  proto static 
   10.9.9.0/24 dev vboxnet0  proto kernel  scope link  src 10.9.9.1 
   192.168.10.0/24 dev wlan0  proto kernel  scope link  src 192.168.10.239  
metric 9
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to utopic on 2014-09-25 (16 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-07-19T15:03:44.847279
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1380480/+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 1489651] Re: Bluetooth audio not working (with GDM?)

2016-12-20 Thread Bug Watch Updater

** Changed in: gdm3 (Debian)
   Status: Unknown => New

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

Title:
  Bluetooth audio not working (with GDM?)

Status in Ubuntu GNOME:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in gdm3 package in Debian:
  New

Bug description:
  I'm having problems with a Marshall Stanmore bluetooth speaker in
  Ubuntu GNOME 15.10 Beta.  It pairs fine and is listed as a bluetooth
  device but won't show up in the audio settings as a device nor will it
  show up with pactl list. I also had this problem in Ubuntu GNOME 15.04
  with the gnome-staging 3.16 ppa. It works fine with stock Ubuntu GNOME
  15.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1489651/+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 1651444] [NEW] package libgs9-common 9.18~dfsg~0-0ubuntu2 [modified: usr/share/ghostscript/9.18/Resource/Init/gs_init.ps] failed to install/upgrade: package libgs9-common is no

2016-12-20 Thread Daniel Graham

Public bug reported:

my command line keeps on omitting some words. I don't understand why.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libgs9-common 9.18~dfsg~0-0ubuntu2 [modified: 
usr/share/ghostscript/9.18/Resource/Init/gs_init.ps]
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic i686
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: i386
CupsErrorLog:
 
Date: Tue Dec 20 14:09:52 2016
Dependencies:
 
DuplicateSignature:
 package:libgs9-common:9.18~dfsg~0-0ubuntu2 [modified: 
usr/share/ghostscript/9.18/Resource/Init/gs_init.ps]
 Processing triggers for libc-bin (2.23-0ubuntu3) ...
 dpkg: error processing package libgs9-common (--configure):
  package libgs9-common is not ready for configuration
ErrorMessage: package libgs9-common is not ready for configuration  cannot 
configure (current status 'half-installed')
InstallationDate: Installed on 2016-12-12 (7 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: Dell Inc. Latitude D620
PackageArchitecture: all
Papersize: letter
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=f6fe196d-0e86-4c1e-953a-6b3f40dc8f3d ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15ubuntu0.2
SourcePackage: ghostscript
Title: package libgs9-common 9.18~dfsg~0-0ubuntu2 [modified: 
usr/share/ghostscript/9.18/Resource/Init/gs_init.ps] failed to install/upgrade: 
package libgs9-common is not ready for configuration  cannot configure (current 
status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/28/2006
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 0TD761
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd08/28/2006:svnDellInc.:pnLatitudeD620:pvr:rvnDellInc.:rn0TD761:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D620
dmi.sys.vendor: Dell Inc.

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


** Tags: apport-package i386 need-duplicate-check xenial

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

Title:
  package libgs9-common 9.18~dfsg~0-0ubuntu2 [modified:
  usr/share/ghostscript/9.18/Resource/Init/gs_init.ps] failed to
  install/upgrade: package libgs9-common is not ready for configuration
  cannot configure (current status 'half-installed')

Status in ghostscript package in Ubuntu:
  New

Bug description:
  my command line keeps on omitting some words. I don't understand why.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgs9-common 9.18~dfsg~0-0ubuntu2 [modified: 
usr/share/ghostscript/9.18/Resource/Init/gs_init.ps]
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: i386
  CupsErrorLog:
   
  Date: Tue Dec 20 14:09:52 2016
  Dependencies:
   
  DuplicateSignature:
   package:libgs9-common:9.18~dfsg~0-0ubuntu2 [modified: 
usr/share/ghostscript/9.18/Resource/Init/gs_init.ps]
   Processing triggers for libc-bin (2.23-0ubuntu3) ...
   dpkg: error processing package libgs9-common (--configure):
package libgs9-common is not ready for configuration
  ErrorMessage: package libgs9-common is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2016-12-12 (7 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Dell Inc. Latitude D620
  PackageArchitecture: all
  Papersize: letter
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=f6fe196d-0e86-4c1e-953a-6b3f40dc8f3d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: ghostscript
  Title: package libgs9-common 9.18~dfsg~0-0ubuntu2 [modified: 
usr/share/ghostscript/9.18/Resource/Init/gs_init.ps] failed to install/upgrade: 
package libgs9-common is not ready for configuration  cannot configure (current 
status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0TD761
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd08/28/2006:svnDellInc.:pnLatitudeD620:pvr:rvnDellInc.:rn0TD761:r

[Desktop-packages] [Bug 1617468] Re: Package contains files in /usr/@DATADIRNAME@/locale

2016-12-20 Thread Jeff Stone

Could someone provide the commands to merge the files into the share
directory properly? I think it'll be something like:

cd /usr
sudo cp -r @DATADIRNAME@/* share

But I'm not really an expert and I don't want to experiment. Thanks

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

Title:
  Package contains files in /usr/@DATADIRNAME@/locale

Status in gnome-system-tools package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  Version: 3.0.0-4ubuntu3

  The package gnome-system-tools contains files in
  /usr/@DATADIRNAME@/locale which is probably wrong. It is the only
  package that has files there. Looks like a variable name from a
  template engine.

  marc@ellen:~$ dpkg -S /usr/@DATADIRNAME@/
  gnome-system-tools: /usr/@DATADIRNAME@

  marc@ellen:~$ dpkg -L gnome-system-tools | fgrep -e DATA
  /usr/@DATADIRNAME@
  /usr/@DATADIRNAME@/locale
  /usr/@DATADIRNAME@/locale/af
  /usr/@DATADIRNAME@/locale/af/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/af/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/am
  /usr/@DATADIRNAME@/locale/am/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/am/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/ar
  /usr/@DATADIRNAME@/locale/ar/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/ar/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/as
  /usr/@DATADIRNAME@/locale/as/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/as/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/ast
  /usr/@DATADIRNAME@/locale/ast/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/ast/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/az
  /usr/@DATADIRNAME@/locale/az/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/az/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/be
  /usr/@DATADIRNAME@/locale/be/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/be/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/be@latin
  /usr/@DATADIRNAME@/locale/be@latin/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/be@latin/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/bg
  /usr/@DATADIRNAME@/locale/bg/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/bg/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/bn
  /usr/@DATADIRNAME@/locale/bn/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/bn/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/bn_IN
  /usr/@DATADIRNAME@/locale/bn_IN/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/bn_IN/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/br
  /usr/@DATADIRNAME@/locale/br/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/br/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/ca
  /usr/@DATADIRNAME@/locale/ca/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/ca/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/ca@valencia
  /usr/@DATADIRNAME@/locale/ca@valencia/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/ca@valencia/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/cs
  /usr/@DATADIRNAME@/locale/cs/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/cs/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/cy
  /usr/@DATADIRNAME@/locale/cy/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/cy/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/da
  /usr/@DATADIRNAME@/locale/da/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/da/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/de
  /usr/@DATADIRNAME@/locale/de/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/de/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/dz
  /usr/@DATADIRNAME@/locale/dz/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/dz/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/el
  /usr/@DATADIRNAME@/locale/el/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/el/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/en@shaw
  /usr/@DATADIRNAME@/locale/en@shaw/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/en@shaw/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/en_CA
  /usr/@DATADIRNAME@/locale/en_CA/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/en_CA/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/en_GB
  /usr/@DATADIRNAME@/locale/en_GB/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/en_GB/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/eo
  /usr/@DATADIRNAME@/locale/eo/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/eo/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/es
  /usr/@DATADIRNAME@/locale/es/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/es/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/et
  /usr/@DATADIRNAME@/locale/et/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/et/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/eu
  /usr/@DATADIRNAME@/locale/eu/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/eu/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/fa
  /usr/@DATADIRNAME@/locale/fa/LC_MESSAGES
  /usr/@DATADIRNAME@/loca

[Desktop-packages] [Bug 1630324] Re: Broadcom wifi dies in 60s cycles with 4.8 kernel

** Package changed: network-manager (Ubuntu) => linux (Ubuntu)

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

Title:
  Broadcom wifi dies in 60s cycles with 4.8 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell XPS 13 9350 with a Broadcom wifi adapter. Wifi connects
  fine, but dies for around 5-10s (the signal dies completely, tools
  like wavemon show "no interface data") in regular cycles of about 60s.
  dmesg logs the same brcmfmac errors every minute or so: "brcmfmac:
  brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30)".

  network-manager's icon doesn't change however (remains as if the
  adapter was connected).

  This issue started to affect me when using kernel 4.8 on Ubuntu 16.04.
  I previously used kernel 4.7 and did not experience this bug.

  I booted the 16.10 daily build and experienced exactly the same
  errors.

  $ lspci | grep BCM4350
  3a:00.0 Network controller: Broadcom Limited BCM4350 802.11ac Wireless 
Network Adapter (rev 08)

  $ dmesg | grep brcm
  [5.864558] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 
22 2015 06:16:26 version 7.35.180.119 (r594535) FWID 01-e791c176
  [5.898803] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code 
(0x30 0x30)
  [   74.991987] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code 
(0x30 0x30)
  [  142.503220] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code 
(0x30 0x30)
  ...

  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  Uname: Linux 4.8.0-040800-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct  4 14:15:02 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-26 (131 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.0.1 dev wlp58s0  proto static  metric 600 
   169.254.0.0/16 dev wlp58s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.0.29  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   wlp58s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/0  
Guava Guest 1  68ae8dc2-ab23-42ef-9e41-ac8e9d91385a  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --  
   ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630324/+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 1597681] Re: [CTA] Enable WAPI support

** Tags added: nm-touch

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

Title:
  [CTA] Enable WAPI support

Status in Canonical System Image:
  In Progress
Status in indicator-network package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  The phone does not currently support WAPI [1]

  It should do so. As part of this, support for the SMS4 [2] cipher is
  also required.

  
  [1] 
https://en.wikipedia.org/wiki/WLAN_Authentication_and_Privacy_Infrastructure
  [2]: https://en.wikipedia.org/wiki/SMS4

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1597681/+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 1591515] Re: Network manager can't disconnect from wifi or connect to another wifi

I wonder if you can reproduce this bug in an up-to-date version of
16.04? Can't reproduce here.

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Network manager can't disconnect from wifi or connect to another wifi

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  After fresh install 16.04 I can't connect to different wifi network
  and if netbook lost wifi connection I need reboot it because NM can't
  do anything to reconnect. NM don't show connected wifi name. I
  attached image that show this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CRDA:
   country BY: DFS-ETSI
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5170 - 5250 @ 80), (N/A, 20), (N/A)
(5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS
(5490 - 5710 @ 160), (N/A, 27), (0 ms), DFS
  CurrentDesktop: Unity
  Date: Sat Jun 11 16:37:25 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-14 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  IpRoute:
   default via 192.168.100.1 dev wlp2s0  proto static  metric 600 
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000 
   192.168.100.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.100.8  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   HUAWEI-KpW2 3a8b63e2-b64e-4e64-b374-4fd453ccf5ec  802-11-wireless  
1465652043  Sat 11 Jun 2016 16:34:03 MSK  yes  0 no 
   /org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   Wired connection 1  32e99c74-fafd-483a-aa6f-745655ff5e9f  802-3-ethernet   
1465650077  Sat 11 Jun 2016 16:01:17 MSK  yes  4294966297no 
   /org/freedesktop/NetworkManager/Settings/2  no  --  -- --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/2  
HUAWEI-KpW2  3a8b63e2-b64e-4e64-b374-4fd453ccf5ec  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
  ----  
   
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1591515/+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 1588126] Re: [regression] Adding new wifi networks (with long passwords) never connect at all in OTA-11 and OTA-12

** Tags added: nm-touch

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

Title:
  [regression] Adding new wifi networks (with long passwords) never
  connect at all in OTA-11 and OTA-12

Status in Canonical System Image:
  Fix Released
Status in indicator-network package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu RTM:
  Fix Committed

Bug description:
  I've just flashed clean images of OTA-11 from the stable channel onto
  a BQ Aquaris E4.5 (krillin) and a Nexus 4 (mako). In both cases the
  phones can see the wifi networks but can't connect to any of them any
  more.

  The wifi networks continue to work for non-Ubuntu devices.

  Also, forcefully flashing a device with OTA-10 fixes the problem. The
  regression began in OTA-11.

  Explanation:
  
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1593686/comments/11

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588126/+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 1609875] Re: Lenovo ThinkPad T440s has display issues after docking

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: unity-settings-daemon (Ubuntu)
   Status: New => Confirmed

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

Title:
  Lenovo ThinkPad T440s has display issues after docking

Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  When undocking the Lenovo Thinkpad T440s from a dock with an external
  monitor, all the screens move to the laptop display.  When I redock
  the laptop, all the screens stay on the laptop display and the monitor
  configurations don't reset.  The laptop display is still marked as the
  main display and is on the wrong side of the other monitor from where
  it's physically located.  I have to either restart the machine to have
  the display settings return to the way they were, or reapply them by
  hand.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-91-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu Aug  4 08:34:34 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:220c]
  InstallationDate: Installed on 2015-01-05 (576 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 20AQ006HUS
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-91-generic 
root=UUID=8f3296b0-155a-4776-a162-283095042d6b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/29/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET78WW (2.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQ006HUS
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET78WW(2.28):bd07/29/2014:svnLENOVO:pn20AQ006HUS:pvrThinkPadT440s:rvnLENOVO:rn20AQ006HUS:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AQ006HUS
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Aug  4 08:26:39 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1034 
   vendor LGD
  xserver.version: 2:1.15.1-0ubuntu2.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1609875/+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 913839] Re: tether over bluetooth - regression in precise

Fixed in trusty.

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  tether over bluetooth - regression in precise

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager package in Fedora:
  Unknown

Bug description:
  I've had dial-up networking via bluetooth working between my CR-48 and
  Blackberry 9800 for several months.

  Recent Precise update (sometime around the last couple of weeks of
  2011) appear to have broken the ability to tether over bluetooth in
  this manner.  I have completely removed the bluetooth connection and
  re-paired the devices from scratch, but it does not work.

  Other bluetooth functionality appears to work fine.  i.e. I can send
  files from the laptop to the phone without issue.

  Here's what I see in syslog:

  Jan  9 09:02:28 chrombuntu NetworkManager[516]:  Activation 
(CC:55:AD:DF:60:A9) starting connection 'AT&T MEdia Net (phones)'
  Jan  9 09:02:28 chrombuntu NetworkManager[516]:  (CC:55:AD:DF:60:A9): 
device state change: disconnected -> prepare (reason 'none') [30 40 0]
  Jan  9 09:02:28 chrombuntu NetworkManager[516]:  Activation 
(CC:55:AD:DF:60:A9) Stage 1 of 5 (Device Prepare) scheduled...
  Jan  9 09:02:28 chrombuntu NetworkManager[516]:  Activation 
(CC:55:AD:DF:60:A9) Stage 1 of 5 (Device Prepare) started...
  Jan  9 09:02:28 chrombuntu NetworkManager[516]:  Activation 
(CC:55:AD:DF:60:A9) Stage 2 of 5 (Device Configure) scheduled...
  Jan  9 09:02:28 chrombuntu NetworkManager[516]:  Activation 
(CC:55:AD:DF:60:A9) Stage 1 of 5 (Device Prepare) complete.
  Jan  9 09:02:28 chrombuntu NetworkManager[516]:  Activation 
(CC:55:AD:DF:60:A9) Stage 2 of 5 (Device Configure) starting...
  Jan  9 09:02:28 chrombuntu NetworkManager[516]:  (CC:55:AD:DF:60:A9): 
device state change: prepare -> config (reason 'none') [40 50 0]
  Jan  9 09:02:28 chrombuntu NetworkManager[516]:  Activation 
(CC:55:AD:DF:60:A9) Stage 2 of 5 (Device Configure) complete.
  Jan  9 09:02:48 chrombuntu NetworkManager[516]:  Error connecting with 
bluez: Did not receive a reply. Possible causes include: the remote application 
did not send a reply, the message bus security policy blocked the reply, the 
reply timeout expired, or the network connection was broken.
  Jan  9 09:02:48 chrombuntu NetworkManager[516]:  (CC:55:AD:DF:60:A9): 
device state change: config -> failed (reason 'bluetooth-failed') [50 120 44]
  Jan  9 09:02:48 chrombuntu NetworkManager[516]:  Activation 
(CC:55:AD:DF:60:A9) failed.
  Jan  9 09:02:48 chrombuntu NetworkManager[516]:  (CC:55:AD:DF:60:A9): 
device state change: failed -> disconnected (reason 'none') [120 30 0]
  Jan  9 09:02:48 chrombuntu NetworkManager[516]:  (CC:55:AD:DF:60:A9): 
deactivating device (reason 'none') [0]
  Jan  9 09:02:48 chrombuntu NetworkManager[516]: nm_system_iface_flush_routes: 
assertion `ifindex > 0' failed
  Jan  9 09:02:48 chrombuntu NetworkManager[516]: 
nm_system_iface_flush_addresses: assertion `ifindex > 0' failed
  Jan  9 09:03:11 chrombuntu bluetoothd[1268]: Connection refused (111)

  dmesg is devoid of any errors during the attempt to connect.  The only
  messages I see related to the device is:

  [ 6567.470098] Bluetooth: TIOCGSERIAL is not supported

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.2.0+git201112151936.6b31828-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-8.14-generic 3.2.0
  Uname: Linux 3.2.0-8-generic x86_64
  ApportVersion: 1.90-0ubuntu1
  Architecture: amd64
  Date: Mon Jan  9 09:09:39 2012
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64+mac (20110913)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.206  
metric 2
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0  
   CC:55:AD:DF:60:A9 bluetooth disconnected  
/org/freedesktop/NetworkManager/Devices/3
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.3.0connected   enabled   enabled 
enabledenabled enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+s

[Desktop-packages] [Bug 1023277] Re: Please provide option to make NetworkManager verify only the root certificate of the signed cert chain (WPA2-Enterprise)

** Tags added: nm-improvements

** Changed in: network-manager (Ubuntu)
 Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned)

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

Title:
  Please provide option to make NetworkManager verify only the root
  certificate of the signed cert chain (WPA2-Enterprise)

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  I have to use a chain certificate, that had all certificates involved
  in the verification of the AP. this seems uncomfortable and breaks
  design (of at least the eduroam networks).

  The (German) eduroam networks are all signed with a certificate of the
  corresponding university or college CA, which is signed by the DFN
  (german scientific network) which is signed by Deutsche Telekom Root
  CA (installed by default on ubuntu)

  By opting to verify the complete chain, I have to set up various
  configurations for various locations.

  The eduroam network is designed to enable students from all over the
  world to log in to worldwide higher education networks with their
  home-university's login.

  There should be an option to only verify the root certificate of the
  signed cert chain.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1023277/+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 1646859] Re: Wifi not working after suspend on 16.10

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

** This bug has been marked a duplicate of bug 1642507
   Not internet after waking from suspend

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

Title:
  Wifi not working after suspend on 16.10

Status in network-manager package in Ubuntu:
  New

Bug description:
  After waking from suspend, nm doesn't automatically connect to WiFi,
  instead nm indicator is showing RJ45 icon like it's connected on wired
  network but it's not. NM indicator panel doesn't show any WiFi
  networks and there is no connection. restarting the service or
  stopping the WiFi antenna using keyboard shortcut don't fix the
  problem. Only relogging the account or restart fixes the issue.

  OS: Ubuntu 16.10
  Device: DELL Inspiron 13" 7000

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1646859/+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 1629620] Re: DNS resolver stops accepting queries

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

** This bug has been marked a duplicate of bug 1631241
   Name resolution stops working after resume from suspend

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

Title:
  DNS resolver stops accepting queries

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After a while / after resume from suspend, the system becomes unable
  to respond to DNS queries, with the following output for example:

  $ nslookup google.com 127.0.1.1
  Server:   127.0.1.1
  Address:  127.0.1.1#53

  ** server can't find google.com: REFUSED

  
  This is on an up to date yakkety install.  Changing resolv.conf to use 
8.8.8.8, or restarting network-manager appears to fix this, at least until it 
recurs again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Oct  1 21:28:51 2016
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-08-21 (407 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  IpRoute:
   default via 192.168.1.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.1.5  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to yakkety on 2016-09-29 (2 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION   CON-UUID  CON-PATH
   
   docker0bridgeconnected 
/org/freedesktop/NetworkManager/Devices/1  docker0  
63f0b05b-f699-4a68-81ce-f62d2c1a247d  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   wlp3s0 wifi  connected 
/org/freedesktop/NetworkManager/Devices/4  HOME-1622-5  
6df3f2f0-fb86-43b5-802a-d59bc5734be3  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   24:DA:9B:B9:09:0E  btdisconnected  
/org/freedesktop/NetworkManager/Devices/3  --   --  
  -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/2  --   --  
  --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629620/+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 1633912] Re: Problem with DNS resolution after suspend

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

** This bug has been marked a duplicate of bug 1631241
   Name resolution stops working after resume from suspend

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

Title:
  Problem with DNS resolution after suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my laptop to 16.10 yesterday. Sometimes after suspend I
  have network issues, one time I was not able to connect to a wifi
  network (might report another bug if this occurees again, but maybe it
  is related, as in network-manager is in some broken state after
  suspend).

  Here is whats happening pretty often: After resume from suspend I have
  a solid network connection, no problem to ping machines in LAN or on
  the internet. But DNS resolution is broken until I restart the
  network-manager service.

  I ran ubuntu-bug while DNS was broken, so if anything gets log-ed it
  should be in there.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 21:01:09 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-09-28 (18 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.0.1 dev wlp58s0  proto static  metric 600 
   169.254.0.0/16 dev br-541a0f9bec93  scope link  metric 1000 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   172.18.0.0/16 dev br-541a0f9bec93  proto kernel  scope link  src 172.18.0.1 
   192.168.0.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.0.118  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to yakkety on 2016-10-15 (1 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633912/+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 1639568] Re: dnsmasq not updated by NetworkManager on system resume

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

** This bug has been marked a duplicate of bug 1631241
   Name resolution stops working after resume from suspend

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

Title:
  dnsmasq not updated by NetworkManager on system resume

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When the system resumes after sleep dnsmasq is either not updated with
  new dns information of never resumes operation.  Restarting the
  network-manager service will manually resolve the problem.  Everything
  else seems correct, the DHCP information is correct and shows the
  correct nameservers, resolv.conf is updated correctly.  I am unable to
  determine if the issue is with dnsmasq not resuming or if the dbus
  message with the name servers is getting lost.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov  6 07:24:44 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-11-03 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IpRoute:
   default via 192.168.1.1 dev wlp58s0  proto static  metric 600 
   169.254.0.0/16 dev wlp58s0  scope link  metric 1000 
   192.168.1.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.1.218  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   
   wlp58s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/0  
The_Magical_Mystery_Tour  4e4fe235-20a0-414a-8ec3-97f65060250e  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --  
  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1639568/+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 1627421] Re: NetworkManager crashed with SIGSEGV in dhcp6_start()

Should be fixed in 1.2.4 SRU.

** Changed in: network-manager (Ubuntu)
   Status: New => Fix Released

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

Title:
  NetworkManager crashed with SIGSEGV in dhcp6_start()

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  miked@free-yak:~$ lsb_release -rd
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  miked@free-yak:~$ apt-cache policy NetworkManager
  N: Unable to locate package NetworkManager
  miked@free-yak:~$ apt-cache policy nm_device_update_dynamic_ip_setup
  N: Unable to locate package nm_device_update_dynamic_ip_setup
  miked@free-yak:~$ 

  I don't know what was expected to happen, this crashed happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.2-0ubuntu10
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Sat Sep 24 20:06:02 2016
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-03 (174 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IpRoute:
   default via 10.0.0.1 dev enp0s17  proto static  metric 100 
   default via 10.0.0.1 dev wlp8s9  proto static  metric 600 
   10.0.0.0/24 dev enp0s17  proto kernel  scope link  src 10.0.0.84  metric 100 
   10.0.0.0/24 dev wlp8s9  proto kernel  scope link  src 10.0.0.218  metric 600 
   169.254.0.0/16 dev enp0s17  scope link  metric 1000
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile,ofono
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcCmdline: /usr/sbin/NetworkManager --no-daemon
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   ?? ()
   nm_device_update_dynamic_ip_setup ()
   ?? ()
   nm_device_set_carrier ()
   ?? ()
  Title: NetworkManager crashed with SIGSEGV in 
nm_device_update_dynamic_ip_setup()
  UpgradeStatus: Upgraded to yakkety on 2016-08-28 (28 days ago)
  UserGroups:
   
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   enp0s17  ethernet  connected/org/freedesktop/NetworkManager/Devices/1  
Wired connection 1  0a821d1a-0aa1-33eb-a8e8-d691b38de9f0  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   wlp8s9   wifi  connected/org/freedesktop/NetworkManager/Devices/3  
FREE2U2.4WI-FI  6784f99c-73d0-4d8b-8fb0-d39d3ef01313  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp0s18  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/0  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1627421/+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 1627801] Re: /usr/sbin/NetworkManager:11:set_ap_scan_cb:g_simple_async_result_complete:reply_cb:g_simple_async_result_complete:g_dbus_connection_call_done

** Tags added: nm-touch

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

Title:
  
/usr/sbin/NetworkManager:11:set_ap_scan_cb:g_simple_async_result_complete:reply_cb:g_simple_async_result_complete:g_dbus_connection_call_done

Status in network-manager package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding network-manager.  This problem was most recently seen with
  version 1.2.2-0ubuntu1~vivid3, the problem page at
  https://errors.ubuntu.com/problem/6304c615f4962c2e584f1c4af9f76ea613721fc9
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1627801/+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 1625116] Re: RT3290 not working

** Package changed: network-manager (Ubuntu) => linux (Ubuntu)

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

Title:
  RT3290 not working

Status in linux package in Ubuntu:
  New

Bug description:
  My WiFi RT3290 does not work on Ubuntu. Neither I remember it working
  on any previous version. I don't have good knowledge of command line
  or linux. But I am using ubuntu as my primary OS. Currently I am using
  usb wifi adapter to connect to internet. I have followed almost every
  guide available on internet like downloading driver from mediatek
  website or someone's dropbox folder and then compiling or changing
  linux kernels. I don't know why still I can't make it work. I want
  this device to work out of box for next ubuntu version. Let me know if
  you need any further information about collecting logs of my system.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Mon Sep 19 15:45:04 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-09-07 (12 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.0.1 dev wlxaca2131a2daf  proto static  metric 600 
   169.254.0.0/16 dev wlxaca2131a2daf  scope link  metric 1000 
   192.168.0.0/24 dev wlxaca2131a2daf  proto kernel  scope link  src 
192.168.0.109  metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH
  CONNECTION   CON-UUID  CON-PATH   

   wlxaca2131a2daf  wifi  connected
/org/freedesktop/NetworkManager/Devices/2  UnitedNepal  
ff526f85-e18b-4713-ae67-f3fbfa290c4b  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp1s0   ethernet  unavailable  
/org/freedesktop/NetworkManager/Devices/0  --   --  
  -- 
   lo   loopback  unmanaged
/org/freedesktop/NetworkManager/Devices/1  --   --  
  --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.0connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625116/+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 1617772] Re: Ubuntu Phone: Unable to connect FritzBox 7490

** Tags added: nm-touch

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

Title:
  Ubuntu Phone: Unable to connect FritzBox 7490

Status in network-manager package in Ubuntu:
  New

Bug description:
  On Ubuntu Phone (OTA-12): Unable to connect FritzBox 7490.

  Aug 28 18:13:42 ubuntu-phablet NetworkManager[1535]: ... device
  (wlan0): Activation: (wifi) access point 'FRITZ!Box 7490' has security
  but secrets are required.

  But the WPA password was applied in the previous dialog.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1617772/+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 1618839] Re: Regression: WiFi connection reconnects, but dead, after waking from standby

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

** This bug has been marked a duplicate of bug 1631241
   Name resolution stops working after resume from suspend

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

Title:
  Regression: WiFi connection reconnects, but dead, after waking from
  standby

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Bug introduced somewhere between Ubuntu 14.04.3 and 16.04.1

  If my Thinkpad T420s awakes from standby, very often the last
  connected WiFi network is reconnected immediately, but the connection
  is dysfunctional.

  ifconfig shows a valid connection with an IPv4 address assigned for
  the wlp3s0 interface.

  But there is no traffic, no success on DNS queries on the connection.

  If I reconnect by clicking the connection in the nm-applet menu, all
  is fine again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1618839/+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 1642507] Re: Not internet after waking from suspend

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

** This bug has been marked a duplicate of bug 1631241
   Name resolution stops working after resume from suspend

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

Title:
  Not internet after waking from suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Release Information:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  Package Information:
  network-manager:
Installed: 1.2.4-0ubuntu1
Candidate: 1.2.4-0ubuntu1
Version table:
   *** 1.2.4-0ubuntu1 500
  500 http://se.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
  100 /var/lib/dpkg/status

  System Information:
  Dell XPS 15 9550
  Wireless: Network controller: Broad com Limited BCM43602 802.11ac Wireless 
LAN SoC (rev 01)
  Wired: Wired Ethernet via Apple USB Ethernet Adapter (ID 05ac:1402 Apple, 
Inc. Ethernet Adapter [A1277])

  Problem Description:
  I have noticed the problem on both wired and wireless. Ever since upgrading 
to 16.10(from 16.04), the system loses internet after waking from suspend. 
Internet works fine after a reboot or when powering on normally.

  "service network-manager restart" fixes the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov 17 09:37:30 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-31 (169 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.80.1 dev enx7cc3a187f0f2  proto static  metric 100 
   default via 192.168.80.1 dev wlp2s0  proto static  metric 600 
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000 
   192.168.80.0/24 dev enx7cc3a187f0f2  proto kernel  scope link  src 
192.168.80.209  metric 100 
   192.168.80.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.80.225  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to yakkety on 2016-10-28 (19 days ago)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   enx7cc3a187f0f2  ethernet  connected  
/org/freedesktop/NetworkManager/Devices/2  Wired connection 1  
e6493319-b925-3b33-92a7-259922dccdaa  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   wlp2s0   wifi  connected  
/org/freedesktop/NetworkManager/Devices/1  whymusticry_fast 1  
b51f9098-d053-45d7-ba42-97bf2e87bda2  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   lo   loopback  unmanaged  
/org/freedesktop/NetworkManager/Devices/0  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1642507/+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 1631241] Re: Name resolution stops working after resume from suspend

** Tags added: nm-improvements

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

Title:
  Name resolution stops working after resume from suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Yakkety, when my Ubuntu GNOME laptop resumes from
  suspend DNS resolution stops working.

  After resuming, systemd-resolved is running and libnss-resolve is
  installed, but /etc/resolv.conf contains 127.0.1.1 as the the only
  name server. The dnsmasq-base package is installed since it is pulled
  in by both network-manager and lxc1, and both NM and libvirt have
  spawned instances of dnsmasq:

  >  1155 pts/2S+ 0:00 grep dnsmasq
  >  2724 ?S  0:00 dnsmasq -u lxc-dnsmasq --strict-order 
--bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --listen-address 10.0.3.1 
--dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override 
--except-interface=lo --interface=lxcbr0 
--dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative
  >  2992 ?S  0:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  >  2993 ?S  0:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  > 22879 ?S  0:00 /usr/sbin/dnsmasq --no-resolv 
--keep-in-foreground --no-hosts --bind-interfaces 
--pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 
--cache-size=0 --conf-file=/dev/null --proxy-dnssec 
--enable-dbus=org.freedesktop.NetworkManager.dnsmasq 
--conf-dir=/etc/NetworkManager/dnsmasq.d

  Let me know if you need any extra info.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libnss-resolve 231-9git1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct  7 13:52:40 2016
  InstallationDate: Installed on 2015-07-22 (443 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-10-05 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1631241/+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 1639668] Re: Webapp crashes when opening a tab

** Package changed: network-manager (Ubuntu) => canonical-devices-
system-image

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

Title:
  Webapp crashes when opening a tab

Status in Canonical System Image:
  Incomplete

Bug description:
  It's not the first time I try to report this bug.

  On Ubuntu Touch, when I open a new tab inside a webapp, when closing
  it, the webapp crashes since OTA 11. I've reset m phone but it's still
  there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1639668/+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 1639180] Re: no login possible after update to nvidia 304.132

This bug was fixed in the package nvidia-graphics-drivers-304 -
304.134-0ubuntu1

---
nvidia-graphics-drivers-304 (304.134-0ubuntu1) zesty; urgency=medium

  * New upstream release. (LP: #1639180)
  * debian/dkms_nvidia/patches/buildfix_kernel_4.9.patch:
- Refresh patch for new upstream release.
  * debian/substvars:
- Add support for X ABI 23.

 -- Robert Hooker   Thu, 15 Dec 2016 11:38:45 -0500

** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1639337] Re: Ubuntu 16.10 Abs_pressure not reported from kernel evdev to xserver-xorg-evdev

** Package changed: network-manager (Ubuntu) => xserver-xorg-input-evdev
(Ubuntu)

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

Title:
  Ubuntu 16.10 Abs_pressure not reported from kernel evdev to xserver-
  xorg-evdev

Status in xserver-xorg-input-evdev:
  Unknown
Status in xserver-xorg-input-evdev package in Ubuntu:
  Confirmed

Bug description:
  Please refer to bug filed with freedesktop.org:

  https://bugs.freedesktop.org/show_bug.cgi?id=98575

  I modified a driver for the Bosto Tablet 22HD and others, this has
  been working without problems across the last several releases and
  continues to work with 16.04.1 LTS.

  When I upgraded to 16.10, pressure readings are lost from all
  applications, X & Y data still visible.

  evtest shows correct EV_ data for ABS_X ABS_Y and ABS_PRESSURE, but
  when xinput is used.

  xinput --list --long 

  The Valuator for pressure is listed, but no changes occur as the tool
  is used. The parameters of the Valuator can still be modified using
  xinput tweaking tools, but no pressure reported.

  All X apps requiring pressure data fail.

  I made a fresh install of 16.10, loaded the driver  same issue.

  I run 16.04.1 LTS, everything fine.
  I have others users of my driver code also using 16.04.1 without issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evdev/+bug/1639337/+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 1629932] Re: /usr/bin/nmcli:11:nmc_find_connection:nmc_secrets_requested:ffi_call_VFP:ffi_call:g_cclosure_marshal_generic_va

** Tags added: nm-touch

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

Title:
  
/usr/bin/nmcli:11:nmc_find_connection:nmc_secrets_requested:ffi_call_VFP:ffi_call:g_cclosure_marshal_generic_va

Status in network-manager package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding network-manager.  This problem was most recently seen with
  version 1.2.2-0ubuntu1~vivid3, the problem page at
  https://errors.ubuntu.com/problem/b3b7dae5bf05fa65c302fd75344f7924a83e66c1
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629932/+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 1646859] Re: Wifi not working after suspend on 16.10

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

** This bug is no longer a duplicate of bug 1642507
   Not internet after waking from suspend
** This bug has been marked a duplicate of bug 1631241
   Name resolution stops working after resume from suspend

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

Title:
  Wifi not working after suspend on 16.10

Status in network-manager package in Ubuntu:
  New

Bug description:
  After waking from suspend, nm doesn't automatically connect to WiFi,
  instead nm indicator is showing RJ45 icon like it's connected on wired
  network but it's not. NM indicator panel doesn't show any WiFi
  networks and there is no connection. restarting the service or
  stopping the WiFi antenna using keyboard shortcut don't fix the
  problem. Only relogging the account or restart fixes the issue.

  OS: Ubuntu 16.10
  Device: DELL Inspiron 13" 7000

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1646859/+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 1651460] [NEW] [HP Compaq Elite 8000 CMT, Realtek ALC221, Black Headphone Out, Front] No sound at all

2016-12-20 Thread daryl armour

Public bug reported:

The headphone jack is not working.  I have tried messing with pulseaudio
and alsamixer but I can't seem to get any sound through the jack.  The
headphones do work, as I have used them on my phone and other computers.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Dec 20 09:54:42 2016
InstallationDate: Installed on 2016-12-19 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Front
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: No sound at all
Title: [HP Compaq Elite 8000 CMT, Realtek ALC221, Black Headphone Out, Front] 
No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: K01 v02.90
dmi.board.asset.tag: 2UA2380BBP
dmi.board.name: 3396
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: 2UA2380BBP
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:svnHewlett-Packard:pnHPCompaqElite8000CMT:pvr:rvnHewlett-Packard:rn3396:rvr:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: HP Compaq Elite 8000 CMT
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug xenial

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

Title:
  [HP Compaq Elite 8000 CMT, Realtek ALC221, Black Headphone Out, Front]
  No sound at all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The headphone jack is not working.  I have tried messing with
  pulseaudio and alsamixer but I can't seem to get any sound through the
  jack.  The headphones do work, as I have used them on my phone and
  other computers.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec 20 09:54:42 2016
  InstallationDate: Installed on 2016-12-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [HP Compaq Elite 8000 CMT, Realtek ALC221, Black Headphone Out, Front] 
No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: K01 v02.90
  dmi.board.asset.tag: 2UA2380BBP
  dmi.board.name: 3396
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA2380BBP
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:svnHewlett-Packard:pnHPCompaqElite8000CMT:pvr:rvnHewlett-Packard:rn3396:rvr:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HP Compaq Elite 8000 CMT
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1651460/+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 1633845] Re: network-manager does not connect to wifi

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

** This bug is no longer a duplicate of bug 1642507
   Not internet after waking from suspend
** This bug has been marked a duplicate of bug 1631241
   Name resolution stops working after resume from suspend

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

Title:
  network-manager does not connect to wifi

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When trying to connect to wifi network, network-manager remains
  blocked in waiting for authentification state then fails after cca
  1min. This started to happen after I updated to kubuntu 16.10.

  Stopping network manager from service and trying to manually connect
  with wpa_supplicant works fine.

  The only way to fix this for me was to stop network manager and/or
  networking and restart the services sometimes more than once.

  os: Kubuntu 16.10
  network-manager: 1.2.4
  hardware: dell xps 9550 
  network controller: BCM43602

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633845/+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 1610750] Re: nm-applet constantly prompts for password, leaks memory

** Package changed: network-manager (Ubuntu) => network-manager-applet
(Ubuntu)

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

Title:
  nm-applet constantly prompts for password, leaks memory

Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  Network Manager is constantly asking me for a WIFI password, as
  frequently as once a minute. I do not get this problem on my phone,
  even though it is using the same WIFI network. The problem does not
  occur on other WIFI networks, so I suspect this is a problem with the
  WIFI network itself, and is possibly not Network Manager's fault. So
  this is annoying, but liveable.

  However, np-applet is also leaking an absurd amount of memory each
  time I enter my password and click "Connect". It's ridiculous for it
  to be using up over 2 GB of resident memory, and to be constantly
  increasing that number, after running for only a few hours.

  This is a not a duplicate of https://bugs.launchpad.net/ubuntu/+source
  /network-manager-applet/+bug/684599. In that issue, which has been
  closed with a "Fix Released" status, the reports are hundreds of
  megabytes of memory, not gigabytes, so I suspect this is a
  fundamentally different problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Aug  7 19:08:52 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-08-26 (1077 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  IpRoute:
   default via 10.2.61.69 dev wlan0  proto static  metric 600 
   10.0.1.4 via 10.2.61.69 dev wlan0  proto dhcp  metric 600 
   10.2.61.68/30 dev wlan0  proto kernel  scope link  src 10.2.61.70  metric 
600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to xenial on 2016-04-26 (103 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE DBUS-PATH  
CONNECTIONCON-UUID  CON-PATH

   wlan0   wifi  connected /org/freedesktop/NetworkManager/Devices/0  
EHS New Yorker Residence  c06e0703-cd04-4294-9f99-8624c834f389  
/org/freedesktop/NetworkManager/ActiveConnection/53 
   eth0ethernet  disconnected  /org/freedesktop/NetworkManager/Devices/1  
------  

   lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/2  
------
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.0connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1610750/+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 1000419] Re: NetworkManager crashed with SIGABRT in __assert_fail_base()

** Information type changed from Private to Public

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

Title:
  NetworkManager crashed with SIGABRT in __assert_fail_base()

Status in network-manager package in Ubuntu:
  New

Bug description:
  NetworkManager crashed with SIGABRT in raise()

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.4.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16
  Uname: Linux 3.2.0-24-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  Date: Wed May 16 09:14:44 2012
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  IpRoute:
   default via 10.64.64.64 dev ppp0  proto static 
   10.64.64.64 dev ppp0  proto kernel  scope link  src 10.112.82.128 
   169.254.0.0/16 dev ppp0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WiMAXEnabled=true
  ProcCmdline: NetworkManager
  ProcEnviron:
   LANGUAGE=en_PH:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_PH.UTF-8
  Signal: 6
  SourcePackage: network-manager
  StacktraceTop:
   raise () from /lib/i386-linux-gnu/libc.so.6
   abort () from /lib/i386-linux-gnu/libc.so.6
   ?? () from /lib/i386-linux-gnu/libc.so.6
   __assert_fail () from /lib/i386-linux-gnu/libc.so.6
   rtnl_link_build_get_request () from /usr/lib/libnl-route-3.so.200
  Title: NetworkManager crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to precise on 2012-03-03 (74 days ago)
  UserGroups:
   
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   ttyUSB0gsm   connected 
/org/freedesktop/NetworkManager/Devices/2  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   disconnected  
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.4.0connected   enabled   enabled 
enabledenabled enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1000419/+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 1639180] Re: no login possible after update to nvidia 304.132

2016-12-20 Thread Oleksandr Pikozh

@skgary, you type it wrongly.

You should type:

sudo
apt-get
install
nvidia-304=304.131-0ubuntu3

I put each word on separate line. Put them into ONE line, inserting spaces 
between them. But NO OTHER spaces should be inserted.
(Don't insert spaces within "nvidia-304=304.131-0ubuntu3".)

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1639942] Re: Update evolution to 3.22.3

2016-12-20 Thread Jeremy Bicha

Thanks, Mike.

I confirm that evolution 3.22.3-0ubuntu0.1 works fine here. (I do most
of my email via a web browser though.). Because of how important it is
to fix the broken Google authentication, I also backported the proposed
evolution and evolution-data-server 3.22.3 to the GNOME3 Staging PPA.
I've not seen any bugs or heard any complaints from the new update yet.

SRU Team, be sure to accept the evolution-data-server SRU (LP: #1639926)
before or at the same time as you accept evolution.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Update evolution to 3.22.3

Status in evolution package in Ubuntu:
  Fix Released
Status in evolution source package in Yakkety:
  Fix Committed

Bug description:
  Impact
  ==
  This is the second SRU for Ubuntu 16.10 for evolution. It includes 3.22.2 and 
3.22.3.

  https://git.gnome.org/browse/evolution/tree/NEWS/?h=gnome-3-22
  https://git.gnome.org/browse/evolution/log/?h=gnome-3-22

  Test Case
  =
  After installing this update, please restart your computer.

  Verify that evolution still works as well as it did before.

  Optionally, you can even go through some of the fixed bugs to verify
  the bug and the fix but there are a lot of fixed bugs!

  Regression Potential
  
  Low to Moderate. This is a substantial update with 90 or so commits.
  On the other hand, these are focused on fixing bugs. This may be the last 
official 3.22 evolution release. This is the same version that is being shipped 
by other GNOME 3.22 distros.

  Other Info
  ==
  This update depends on evolution-data-server 3.22.3. See the note on that SRU 
bug (LP: #/1639926) for information about the persistent Google authentication 
issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1639942/+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 1629611] Re: dns server priority broken

2016-12-20 Thread Lonnie Lee Best

Why is the status of this incomplete. I've verified this issue from
numerous perspectives that probably all fundamental point directly to
the issue Thomas has reported; see post#2.

This is a terrible bug. Network-Manager updates were prematurely
released to 14.04 stable and all succeeding releases and no one caught
this. I keep waiting as patiently as possible. Please fix!

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

Title:
  dns server priority broken

Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  network-manager: 1.2.4-0ubuntu1

  
  Yakkety appears to have switched back from resolved to dnsmasq, but it seems 
server priority/order is broken.

  Example: In split DNS setups, connecting to VPN will not cause us to
  query the DNS provided by the VPN first (or only), which should be the
  proper way to resolve names in that case.

  Say server.example.com in the public DNS resolves to a.a.a.a and in
  the private DNS resolves to b.b.b.b.

  Stuff would work from my normal internet-connection, but connection to
  VPN would cause stuff to misbehave. I expect to hit the b.b.b.b
  address but since my normal LAN DNS is being used first, I'm really
  hitting a.a.a.a.

  Please let me know how to proceed - Hopefully this can be fixed in
  time for release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/1629611/+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 1607684] Re: wifi networks not remembered correctly (ubuntu touch, bq M10)

** Tags added: nm-touch

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

Title:
  wifi networks not remembered correctly (ubuntu touch, bq M10)

Status in Canonical System Image:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  I have a M10, on ubuntu touch OTA-12 (and same issue previously on
  OTA-11).

  The issue is that it doesn't remember wifi networks properly. To
  explain:

  1. turn on tablet
  2. select my wifi network from the list
  3. enter password and click connect
  4. reboot device
  5. select my wifi network from the list
  6. enter password and click connect
  .
  .
  .
  30. go to wifi settings -> previous networks
  31. view long list that looks like:

  MyWifinetwork1
  MyWifinetwork2
  MyWifinetwork3
  MyWifinetwork4
  ...

  What it should do (and did some time ago), is see that MyWifinetwork
  was saved in previous networks and automatically connect using the
  saved password/settings.

  So, I'm wondering is this a bug, something badly configured in my wifi
  network (although other devices remember it fine), or something else?

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607684/+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 1639180] Re: no login possible after update to nvidia 304.132

2016-12-20 Thread Brian Murray

** Also affects: nvidia-graphics-drivers-304 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-304 (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: nvidia-graphics-drivers-304 (Ubuntu Xenial)
   Importance: Undecided => Critical

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Triaged
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1639180] Re: no login possible after update to nvidia 304.132

Oleksandr

What I mean is I get a message saying it can't find 131-0ubuntu3 . I
tried a couple of different mirrors.

If i open Synapthic I see a few different versions of NVidea but not
that one.

I see it's supposed to be fixed now. Hopefully I will get a chance to
try it today.

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1643467] Re: Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec

2016-12-20 Thread louis romano

** Changed in: firefox (Ubuntu Precise)
 Assignee: (unassigned) => louis romano (troubleshooter1961)

** Changed in: firefox (Ubuntu Precise)
   Status: Confirmed => Fix Released

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

Title:
  Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec

Status in libav:
  Unknown
Status in firefox package in Ubuntu:
  Confirmed
Status in libav package in Ubuntu:
  Invalid
Status in firefox source package in Precise:
  Fix Released
Status in libav source package in Precise:
  Confirmed
Status in firefox source package in Trusty:
  Fix Released
Status in libav source package in Trusty:
  Fix Released

Bug description:
  Whenever it tries to play a video, Firefox 50 displays this message at the 
top of every page:
  "libavcodec may be vulnerable or is not supported, and should be updated to 
play video"

  https://dxr.mozilla.org/mozilla-central/source/browser/locales/en-
  
US/chrome/browser/browser.properties?q=%22libavcodec+may+be+vulnerable%22&redirect_type=single#742

  Firefox refuses any libavcodec version prior to 54.35.1 (unless
  media.libavcodec.allow-obsolete==true).

  https://dxr.mozilla.org/mozilla-
  central/source/dom/media/platforms/ffmpeg/FFmpegLibWrapper.cpp#60

  Users should not be subjected to this warning, as it is vague (does not 
instruct them how to fix it).
  Ubuntu 14.04 LTS should ship with an updated version of libavcodec.

  DistroRelease: Ubuntu 14.04
  Package: firefox 50.0+build2-0ubuntu0.14.04.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/libav/+bug/1643467/+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 1639926] Re: Update evolution-data-server to 3.22.3

2016-12-20 Thread Jeremy Bicha

Brian, so I could use something like this:

https://sources.debian.net/src/connman/unstable/debian/connman.postinst/

I'm not sure that it's important enough to delay this update another
week or so, but we can do it next time.

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

Title:
Update evolution-data-server to 3.22.3

Status in evolution-data-server package in Ubuntu:
Fix Released
Status in evolution-data-server source package in Yakkety:
Fix Committed

Bug description:
Impact
==
This is the second evolution SRU for yakkety. This update includes the new
bugfix releases 3.22.2 and 3.22.3. Updating e-d-s is required to update
evolution to 3.22.3 (LP: #1639942)

https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-22
https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-22

Test Case
=
After installing the update, restart your computer. (Is there a flag
evolution-data-server should set to prompt the user to do this?)

Run several eds-using apps like Evolution, GNOME Calendar and verify
that they continue to run at least as well as before this update.

Regression Potential

Low. There are a fair amount of changes in this update, but they are all
targeted towards fixing bugs. This is the same release that other GNOME 3.22
distros ship. This may be the last official 3.22 release for the Evolution
stack.

Other Info
==
Note that there is an issue with Google authentication affecting at least
3.20 and 3.22.0. The underlying issue should be fixed with this update (it was
partially fixed with 3.22.1 already in yakkety-updates). Unfortunately, anyone
anywhere using older still-broken versions of e-d-s still break authentication
for everyone else using the same API key!

Because of this, GNOME is updating the key used by GNOME Online
Accounts (LP: #1649995). The key used by e-d-s might need to be
updated too. And maybe the key used by Ubuntu Online Accounts (LP:
#1650007). This is because there are 2 or 3 different ways to use a
Google account with Evolution. You only need to update the key for the
Google authentication method you use.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1639926/+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 508740] Re: PPTP VPN "no valid VPN secrets"

2016-12-20 Thread Frindli

I have same error message on ubuntu touch if I tried connect to VPN
server with OPENVPN or PPTP.

The error message if I type "sudo nmcli con up THENAME":
Password is required but not given in 'passwd-file' (I don't no while) and 
nmcli cannot ask without --ask option

So that's worked for me on ubuntu touch:
sudo nmcli --ask con up "VPNCONNECTIONNAME"

But VPN worked without terminal before OTA-14.

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

Title:
  PPTP VPN "no valid VPN secrets"

Status in network-manager-pptp package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: network-manager-pptp

  When trying to connect I immediately get a notification stating:
  "The VPN connection '' failed. because there were no valid VPN secrets."

  I'm quite positive I've not made an error in setting it up.

  My syslog spits out this:
  Jan 17 13:51:26 lena NetworkManager:   Starting VPN service 
'org.freedesktop.NetworkManager.pptp'...
  Jan 17 13:51:26 lena NetworkManager:   VPN service 
'org.freedesktop.NetworkManager.pptp' started 
(org.freedesktop.NetworkManager.pptp), PID 8900
  Jan 17 13:51:26 lena NetworkManager:   VPN service 
'org.freedesktop.NetworkManager.pptp' just appeared, activating connections
  Jan 17 13:51:26 lena NetworkManager: nm-vpn-connection.c.828: NeedSecrets 
failed: dbus-glib-error-quark Rejected send message, 1 matched rules; 
type="method_call", sender=":1.2" (uid=0 pid=1051 comm="NetworkManager) 
interface="org.freedesktop.NetworkManager.VPN.Plugin" member="NeedSecrets" 
error name="(unset)" requested_reply=0 
destination="org.freedesktop.NetworkManager.pptp" (uid=0 pid=8900 
comm="/usr/lib/network-manager-pptp/nm-pptp-service))
  Jan 17 13:51:26 lena NetworkManager:   connection_state_changed(): 
Rejected send message, 1 matched rules; type="method_call", sender=":1.2" 
(uid=0 pid=1051 comm="NetworkManager) 
interface="org.freedesktop.NetworkManager.VPN.Plugin" member="Disconnect" error 
name="(unset)" requested_reply=0 
destination="org.freedesktop.NetworkManager.pptp" (uid=0 pid=8900 
comm="/usr/lib/network-manager-pptp/nm-pptp-service))
  Jan 17 13:51:26 lena NetworkManager:   Policy set 'Auto netgear' (eth1) 
as default for routing and DNS.
  Jan 17 13:51:38 lena NetworkManager:  [1263732698.001156] 
ensure_killed(): waiting for vpn service pid 8900 to exit
  Jan 17 13:51:38 lena NetworkManager:  [1263732698.001284] 
ensure_killed(): vpn service pid 8900 cleaned up

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-pptp/+bug/508740/+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 1629611] Re: dns server priority broken

** Tags added: nm-improvements

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

Title:
  dns server priority broken

Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  network-manager: 1.2.4-0ubuntu1

  
  Yakkety appears to have switched back from resolved to dnsmasq, but it seems 
server priority/order is broken.

  Example: In split DNS setups, connecting to VPN will not cause us to
  query the DNS provided by the VPN first (or only), which should be the
  proper way to resolve names in that case.

  Say server.example.com in the public DNS resolves to a.a.a.a and in
  the private DNS resolves to b.b.b.b.

  Stuff would work from my normal internet-connection, but connection to
  VPN would cause stuff to misbehave. I expect to hit the b.b.b.b
  address but since my normal LAN DNS is being used first, I'm really
  hitting a.a.a.a.

  Please let me know how to proceed - Hopefully this can be fixed in
  time for release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/1629611/+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 1629611] Re: dns server priority broken

2016-12-20 Thread Bryn Cooke

This workaround worked for me in 16.10:

In /etc/NetworkManager/NetworkManager.conf

Comment out:
dns=dnsmasq

The run:
sudo service NetworkManager restart

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

Title:
  dns server priority broken

Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  network-manager: 1.2.4-0ubuntu1

  
  Yakkety appears to have switched back from resolved to dnsmasq, but it seems 
server priority/order is broken.

  Example: In split DNS setups, connecting to VPN will not cause us to
  query the DNS provided by the VPN first (or only), which should be the
  proper way to resolve names in that case.

  Say server.example.com in the public DNS resolves to a.a.a.a and in
  the private DNS resolves to b.b.b.b.

  Stuff would work from my normal internet-connection, but connection to
  VPN would cause stuff to misbehave. I expect to hit the b.b.b.b
  address but since my normal LAN DNS is being used first, I'm really
  hitting a.a.a.a.

  Please let me know how to proceed - Hopefully this can be fixed in
  time for release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/1629611/+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 1639180] Re: no login possible after update to nvidia 304.132

No I just typed it wrong in the message.

As I said even synapthic can't find it.

It can't find 304.134 now either.

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 978604] Re: Banshee/Rhythmbox regularly stop playing audio when left on in the background

2016-12-20 Thread HX_unbanned

Issue happening on Fedora 26 x64 with latest available Rythmbox version.

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

Title:
  Banshee/Rhythmbox regularly stop playing audio when left on in the
  background

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio source package in Precise:
  Confirmed

Bug description:
  If Banshee or Rhythmbox is left playing in the background they will
  randomly stop playing in the latest builds of Ubuntu 12.04. Starting a
  new piece of music usually fixes the problem. If left to its own
  devices, the music will start playing again at some random time, at
  some random position. This problem exists on both my desktop machine
  (custom built Intel machine) and my laptop (Macbook 5,1). It has been
  happening for several months now.

  I became frustrated enough to load up pulseaudio in debugging mode.
  The log shows that when the music player just finishes playing one
  piece, and tries to start the next piece, you see something like this:

  ---
  ( 335.399|  34.388) D: [alsa-sink] sink-input.c: Requesting rewind due to 
corking
  ( 335.400|   0.001) D: [alsa-sink] alsa-sink.c: Requested to rewind 65536 
bytes.
  ( 335.400|   0.000) D: [alsa-sink] alsa-sink.c: Limited to 14820 bytes.
  ( 335.400|   0.000) D: [alsa-sink] alsa-sink.c: before: 3705
  ( 335.400|   0.000) D: [alsa-sink] alsa-sink.c: after: 3705
  ( 335.400|   0.000) D: [alsa-sink] alsa-sink.c: Rewound 14820 bytes.
  ( 335.400|   0.000) D: [alsa-sink] sink.c: Processing rewind...
  ( 335.400|   0.000) D: [alsa-sink] sink.c: latency = 1643
  ( 335.400|   0.000) D: [alsa-sink] sink-input.c: Have to rewind 14820 bytes 
on render memblockq.
  ( 335.400|   0.000) D: [alsa-sink] sink-input.c: Have to rewind 14820 bytes 
on implementor.
  ( 335.400|   0.000) D: [alsa-sink] source.c: Processing rewind...
  ( 335.400|   0.000) D: [pulseaudio] module-suspend-on-idle.c: Sink 
alsa_output.pci-_00_1b.0.analog-stereo becomes idle, timeout in 5 seconds.
  ( 335.402|   0.001) D: [alsa-sink] alsa-sink.c: hwbuf_unused=0
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15502
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Requested volume: 0:  34% 1:  
34%
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c:in dB: 0: -28.11 
dB 1: -28.11 dB
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Got hardware volume: 0:  34% 
1:  34%
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c:   in dB: 0: 
-28.00 dB 1: -28.00 dB
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Calculated software volume: 
0: 100% 1: 100% (accurate-enough=yes)
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c:  in dB: 
0: -0.11 dB 1: -0.11 dB
  ( 335.402|   0.000) D: [alsa-sink] sink.c: Volume not changing
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Requested to rewind 65536 
bytes.
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Limited to 15300 bytes.
  ( 335.402|   0.000) D: [pulseaudio] module-suspend-on-idle.c: Sink 
alsa_output.pci-_00_1b.0.analog-stereo becomes idle, timeout in 5 seconds.
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: before: 3825
  ( 335.402|   0.000) D: [pulseaudio] core.c: Hmm, no streams around, trying to 
vacuum.
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: after: 3825
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Rewound 15300 bytes.
  ( 335.402|   0.000) D: [alsa-sink] sink.c: Processing rewind...
  ( 335.402|   0.000) D: [alsa-sink] sink.c: latency = 1402
  ( 335.402|   0.000) D: [alsa-sink] source.c: Processing rewind...
  ( 335.402|   0.000) I: [pulseaudio] sink-input.c: Freeing input 3 
"'zero-project - 05 - Forest of the unicorns' by 'zero-project'"
  ( 335.402|   0.000) D: [pulseaudio] module-stream-restore.c: Not restoring 
device for stream sink-input-by-media-role:music, because already set to 
'alsa_output.pci-_00_1b.0.analog-stereo'.
  ( 335.403|   0.000) D: [pulseaudio] module-intended-roles.c: Not setting 
device for stream Playback Stream, because already set.
  ( 335.403|   0.000) I: [pulseaudio] module-stream-restore.c: Restoring volume 
for sink input sink-input-by-media-role:music.
  ( 335.403|   0.000) I: [pulseaudio] module-stream-restore.c: Restoring mute 
state for sink input sink-input-by-media-role:music.
  ( 335.403|   0.000) D: [pulseaudio] module-suspend-on-idle.c: Sink 
alsa_output.pci-_00_1b.0.analog-stereo becomes busy.
  ( 335.403|   0.000) I: [pulseaudio] resampler.c: Forcing resampler 'copy', 
because of fixed, identical sample rates.
  ( 335.403|   0.000) I: [pulseaudio] resampler.c: Using resampler 'copy'
  ( 335.403|   0.000) I: [pulseaudio] resampler.c: Using float32le as working 
format.
  ( 335.403|   0.000) D: [pulseaudio] memblockq.c: memblockq requested: 
maxlength=33554432, tlength=0, base=4, prebuf=0, minreq=1 maxrewind=0

[Desktop-packages] [Bug 1639926] Re: Update evolution-data-server to 3.22.3

2016-12-20 Thread Jeremy Bicha

I confirm that evolution-data-server 3.22.3-0ubuntu0.1 works fine here
on Ubuntu GNOME 16.10. (I do most of my email via a web browser
though.). Because of how important it is to fix the broken Google
authentication, I also backported the proposed evolution and evolution-
data-server 3.22.3 to the GNOME3 Staging PPA. I've not seen any bugs or
heard any complaints from the new update yet.

I tested evolution and gnome-calendar with my configured Google account.

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

Title:
Update evolution-data-server to 3.22.3

Status in evolution-data-server package in Ubuntu:
Fix Released
Status in evolution-data-server source package in Yakkety:
Fix Committed

https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-22
https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-22

Test Case
=
After installing the update, restart your computer. (Is there a flag
evolution-data-server should set to prompt the user to do this?)

Run several eds-using apps like Evolution, GNOME Calendar and verify
that they continue to run at least as well as before this update.

Regression Potential

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1639926/+subscriptions

[Desktop-packages] [Bug 991481] Re: Constant dns traffic for daisy.ubuntu.com

** Tags added: nm-improvements

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

Title:
  Constant dns traffic for daisy.ubuntu.com

Status in Whoopsie:
  Confirmed
Status in glib2.0 package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Triaged
Status in whoopsie package in Ubuntu:
  Triaged

Bug description:
  Watching GNetworkMonitor's network-changed signal causes constant DNS
  traffic.

  Andy Whitcroft points out that the NETLINK_ROUTE socket set up by
  GNetworkMonitor will fire events every time an ARP entry appears or
  disappears.

  Unfortunately, we currently need an additional layer of connectivity
  checking because checking NetworkManager's state for CONNECTED_GLOBAL
  is not enough to know whether we're really online. Ubuntu does not yet
  use the NetworkManager connectivity check [1].

  The likely solution to this bug is a replacement for GNetworkMonitor
  in whoopsie.

  1: http://bazaar.launchpad.net/~daisy-
  pluckers/whoopsie/trunk/view/head:/src/connectivity.c#L326

  Original report follows:

  Every few seconds, I see a dns query for daisy.ubuntu.com. After
  removing whoopsie, the traffic goes away.

To manage notifications about this bug go to:
https://bugs.launchpad.net/whoopsie/+bug/991481/+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 1639180] Re: no login possible after update to nvidia 304.132

OK I did
sudo add-apt-repository ppa:graphics-drivers/ppa 
sudo apt-get update.

Now I have nvidia-304 304.1343-0ubuntu0 showing up in Synaptic

I don't have
nvidia-304 304.1343-0ubuntu1

nor is version 131 showing up

In Software and Updates I selected Main Server and reloaded

Maybe I just have to wait until nvidia-304 304.1343-0ubuntu1 becomes
available here?

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Triaged
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1639180] Re: no login possible after update to nvidia 304.132