[Desktop-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[Khurshid Alam]

I don't know if this is related but  now it simply could not resolve
https://www.aviationweather.gov and www.noaa.gov. The result is the same
through ping and wget.

However when I try ip address of www.aviationweather.gov in browser it
works.

---
$ systemd-resolve 140.90.101.207
140.90.101.207: resolve call failed: Address '140.90.101.207' does not have any 
RR of requested type


$ wget "https://140.90.101.207/adds/dataserver_current/httpparam;

Connecting to 140.90.101.207:443... connected.
ERROR: certificate common name ‘ncep.noaa.gov’ doesn't match requested host 
name ‘140.90.101.207’
---


I have libnssresolve installed. systemd-232-19, Ubuntu 17.04

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in Nextcloud:
  Unknown
Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in systemd source package in Yakkety:
  Triaged

Bug description:
  [SRU Justification]
  Ubuntu 16.10 server uses systemd-resolved by default, configured both as a 
DNS stub resolver on 127.0.0.53 and as an NSS module via libnss-resolved 
talking to the dbus service.  The DNS stub resolver has a bug that causes it to 
fail to resolve CNAME records.  This went unnoticed before release because by 
default the NSS module is used.  But a chroot or container on the system that 
does not include libnss-resolved and is configured to use the stub resolver 
will experience DNS failures.

  [Test case]
  1. On a yakkety server system, create a xenial chroot with mk-sbuild (or 
equivalent).
  2. Make sure that the host system has /etc/resolv.conf pointed at 127.0.0.53.
  2. Enter the chroot with 'sudo schroot -c xenial-amd64' or such.
  3. Install the iputils-ping package.
  4. ping www.freedesktop.org
  5. Confirm that the hostname does not resolve.
  6. Install the systemd package from yakkety-proposed onto the host system.
  7. ping www.freedesktop.org
  8. Confirm that the hostname does now resolve.

  [Regression potential]
  With a 247-line patch to a key service, there is some risk of regression.  
Regression risk is mitigated because this patch is already present in zesty and 
upstream, where no regressions have been reported, and because it only touches 
the DNS stub resolver which is not the code path used by default on host 
systems.

  
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nextcloud-snap/+bug/1647031/+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 1023277] Re: Please provide option to make NetworkManager verify only the root certificate of the signed cert chain (WPA2-Enterprise)

[Launchpad Bug Tracker]

[Expired for network-manager (Ubuntu) because there has been no activity
for 60 days.]

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

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

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 1657925] Re: nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to build

[Launchpad Bug Tracker]

[Expired for nvidia-graphics-drivers-367 (Ubuntu) because there has been
no activity for 60 days.]

** Changed in: nvidia-graphics-drivers-367 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to
  build

Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Expired

Bug description:
  The file at "/var/lib/dpkg/updates/0015" had multiple rows of the
  following: the word "#padding" followed by a line break.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-367 367.57-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-59-generic
  Date: Thu Jan 19 16:01:03 2017
  InstallationDate: Installed on 2016-06-02 (231 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageVersion: 367.57-0ubuntu0.16.04.1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: nvidia-graphics-drivers-367
  Title: nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1657925/+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 1657857] Re: package language-selector-common 0.165.4 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

[Launchpad Bug Tracker]

[Expired for language-selector (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: language-selector (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package language-selector-common 0.165.4 failed to install/upgrade:
  sub-processo script post-installation instalado retornou estado de
  saída de erro 1

Status in language-selector package in Ubuntu:
  Expired

Bug description:
  bug

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: language-selector-common 0.165.4
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Thu Jan 19 16:12:42 2017
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: language-selector
  Title: package language-selector-common 0.165.4 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1657857/+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 1674529] [NEW] Credentials expired on all accounts.

[Cristhian Steven Echeverry Z.]

Public bug reported:

Hello!
I can not synchronize any account, I already tried eliminating each one, 
removed the key from the "Passwords" app, restarting and nothing.
Any solution?
Pd: Some have two-step verification enabled, some do not.
GNOME Shell 3.20.4
Ubuntu GNOME 16.10

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: gnome-online-accounts 3.20.5-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
Uname: Linux 4.8.0-41-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Mar 20 22:10:02 2017
InstallationDate: Installed on 2017-03-18 (2 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
SourcePackage: gnome-online-accounts
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug third-party-packages yakkety

** Attachment added: "screensht"
   
https://bugs.launchpad.net/bugs/1674529/+attachment/4841324/+files/Captura%20de%20pantalla%20de%202017-03-20%2011-46-44.png

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

Title:
   Credentials expired on all accounts.

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Hello!
  I can not synchronize any account, I already tried eliminating each one, 
removed the key from the "Passwords" app, restarting and nothing.
  Any solution?
  Pd: Some have two-step verification enabled, some do not.
  GNOME Shell 3.20.4
  Ubuntu GNOME 16.10

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-online-accounts 3.20.5-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Mar 20 22:10:02 2017
  InstallationDate: Installed on 2017-03-18 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1674529/+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 1673942] Re: pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog

[john nunnington]

comparing pulseaudio configuration, some rtp modules were uncommented in
the failing environment so these were commented back out; result,
pulseaudio ran for about 26 minutes before failing. Daemon restarted (as
configured) and sound settings retained the selected output device...but
spotify is unable to restart or play.

...just failed after 3-4 minutes

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

Title:
  pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  this only happens when sound is through the PCI sound card. When i
  connect speakers to the motherboard output (I lose the 5.1 component),
  pulseaudio never dies.

  I have switched and replaced the sound card to no effect but I never
  really thought that was the issue.

  There seems to be no evidence of the failure unless I run it from the
  command line with -, when eventually I see a 'killed' message.

  The pulseaudio log collects initial messages, but nothing else is
  echoed to the log - which could be anything from 3-20 minutes
  [typically].

  I'm more than happy to assist in getting whatever logs are required, but 
nothing I've seen documented seems to help.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  julie 30342 F pulseaudio
   /dev/snd/controlC1:  julie 30342 F pulseaudio
   /dev/snd/controlC2:  julie 30342 F pulseaudio
   /dev/snd/controlC0:  julie 30342 F pulseaudio
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2015-05-19 (670 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Package: pulseaudio 1:9.0-2ubuntu2.1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_NZ:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  Tags:  yakkety
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-USB3 6.0
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3 6.0
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-03-18T20:58:01.387562
  mtime.conffile..etc.pulse.default.pa: 2015-12-20T08:49:47.368322

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1673942/+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 1674477] Re: gnome screenshot gtk-mir crashes on taking the shot

[Daniel van Vugt]

If we really want to support gnome-screenshot at all, it might be easier
to implement a Mir backend right inside it (perhaps after fixing bug
1660269).

** Tags added: gtk-mir

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

** Summary changed:

- gnome screenshot gtk-mir crashes on taking the shot
+ gnome screenshot gtk-mir crashes on taking the shot under Mir

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

Title:
  gnome screenshot gtk-mir crashes on taking the shot under Mir

Status in Canonical System Image:
  New
Status in gnome-screenshot package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Tried this with (updated) Zesty plus ppa:attente/gtk-mir-staging
  then export GDK_BACKEND=mir
  launch from command line: gnome-screenshot -- 
--desktop_file_hint=org.gnome.Screenshot.desktop

  Attempt to take a screen shot in any form and it will crash (see
  attached log)

  
  according to attente: 
  gnome-screenshot crashes is because it delegates the screenshotting to 
org.gnome.Shell, and falls back to using x11 if that fails
  so i think the solution is to have u8 implement that interface...
  
https://git.gnome.org/browse/gnome-shell/tree/data/org.gnome.Shell.Screenshot.xml

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1674477/+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 1637959] Re: Gnome Character Map (gucharmap) displays characters white-on-white when global dark theme is on

[Launchpad Bug Tracker]

This bug was fixed in the package gucharmap - 1:9.0.3-0ubuntu1

---
gucharmap (1:9.0.3-0ubuntu1) zesty; urgency=medium

  * New upstream release.
- Allow Dark Theme (Closes: #808386) (LP: #1637959)
  * debian/gucharmap.install:
- Update appstream metadata install directory
  * debian/libgucharmap-2-90-7.docs:
- README has been dropped

 -- Jeremy Bicha   Mon, 20 Mar 2017 19:55:00 -0400

** Changed in: gucharmap (Ubuntu)
   Status: New => Fix Released

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

Title:
  Gnome Character Map (gucharmap)  displays characters white-on-white
  when global dark theme is on

Status in gucharmap package in Ubuntu:
  Fix Released

Bug description:
  I use a dark theme globally, and gucharmap has a problem with dark
  themes. The problem is that in the character table, only the currently
  selected character is visible, whereas all other characters are
  displayed as white glyphs on white background, therefore, are
  invisible.

  I'm attaching a screenshot with this effect visible. You can observe
  that U+0034 DIGIT FOUR is the character currently selected, and it is
  the only one that can be seen in the table.

  I'm running Xubuntu 16.04.1 LTS. The theme I'm using is called Add-
  Waiter (which is basically a dark-by-default version of Adwaita), and
  the version number of gucharmap is visible in the About dialog (exact
  version of the package is 1:3.18.2-1ubuntu1).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gucharmap/+bug/1637959/+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 1671731] Re: [xmir] closing an app while a child window is opened leaves an Xmir process opened eating 100% CPU

[Daniel van Vugt]

I spent a little time on this bug last week.

Was able to reproduce it, yes, but the spinning thread was apparently
the libmirclient input thread, and not in any Xmir code. I didn't have
sufficient libmirclient symbols to debug it further before running out
of time. I had assumed this was an Xmir bug but it looks like it might
actually be a Mir bug.

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

Title:
  [xmir] closing an app while a child window is opened leaves an Xmir
  process opened eating 100% CPU

Status in Canonical System Image:
  Confirmed
Status in ubuntu-app-launch package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Ubuntu 17.04 Unity 8
  [xmir] closing an app while a child window is opened leaves an Xmir process 
opened eating 100% CPU

  launch solitaire (just click on the sol icon from launcher, it will just run 
on Xmir)
  open the about window from the menu (Help \ About)
  now close the main window 

  now top in a terminal (see attached)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671731/+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 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[Steve Langasek]

** Description changed:

+ [SRU Justification]
+ Ubuntu 16.10 server uses systemd-resolved by default, configured both as a 
DNS stub resolver on 127.0.0.53 and as an NSS module via libnss-resolved 
talking to the dbus service.  The DNS stub resolver has a bug that causes it to 
fail to resolve CNAME records.  This went unnoticed before release because by 
default the NSS module is used.  But a chroot or container on the system that 
does not include libnss-resolved and is configured to use the stub resolver 
will experience DNS failures.
+ 
+ [Test case]
+ 1. On a yakkety server system, create a xenial chroot with mk-sbuild (or 
equivalent).
+ 2. Make sure that the host system has /etc/resolv.conf pointed at 127.0.0.53.
+ 2. Enter the chroot with 'sudo schroot -c xenial-amd64' or such.
+ 3. Install the iputils-ping package.
+ 4. ping www.freedesktop.org
+ 5. Confirm that the hostname does not resolve.
+ 6. Install the systemd package from yakkety-proposed onto the host system.
+ 7. ping www.freedesktop.org
+ 8. Confirm that the hostname does now resolve.
+ 
+ [Regression potential]
+ With a 247-line patch to a key service, there is some risk of regression.  
Regression risk is mitigated because this patch is already present in zesty and 
upstream, where no regressions have been reported, and because it only touches 
the DNS stub resolver which is not the code path used by default on host 
systems.
+ 
+ 
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)
  
  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  
  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176
  
  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in Nextcloud:
  Unknown
Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in systemd source package in Yakkety:
  Triaged

Bug description:
  [SRU Justification]
  Ubuntu 16.10 server uses systemd-resolved by default, configured both as a 
DNS stub resolver on 127.0.0.53 and as an NSS module via libnss-resolved 
talking to the dbus service.  The DNS stub resolver has a bug that causes it to 
fail to resolve CNAME records.  This went unnoticed before release because by 
default the NSS module is used.  But a chroot or container on the system that 
does not include libnss-resolved and is configured to use the stub resolver 
will experience DNS failures.

  [Test case]
  1. On a yakkety server system, create a xenial chroot with mk-sbuild (or 
equivalent).
  2. Make sure that the host system has /etc/resolv.conf pointed at 127.0.0.53.
  2. Enter the chroot with 'sudo schroot -c xenial-amd64' or such.
  3. Install the iputils-ping package.
  4. ping www.freedesktop.org
  5. Confirm that the hostname does not resolve.
  6. Install the systemd package from yakkety-proposed onto the host system.
  7. ping www.freedesktop.org
  8. Confirm that the hostname does now resolve.

  [Regression potential]
  With a 247-line patch to a key service, there is some risk of regression.  
Regression risk is mitigated because this patch is already present in zesty and 
upstream, where no regressions have been reported, and because it only touches 
the DNS stub resolver which is not the code path used by default on host 
systems.

  
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # 

[Desktop-packages] [Bug 1673942] Re: pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog

[john nunnington]

installed 16.04-02 onto an SSD this morning and Spotify/Pulseaudio has
been running for 2-3 hours with only a single hiccup where Spotify just
stopped - but pulseaudio daemon was still running and restarting Spotify
solved the lack of music.

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

Title:
  pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  this only happens when sound is through the PCI sound card. When i
  connect speakers to the motherboard output (I lose the 5.1 component),
  pulseaudio never dies.

  I have switched and replaced the sound card to no effect but I never
  really thought that was the issue.

  There seems to be no evidence of the failure unless I run it from the
  command line with -, when eventually I see a 'killed' message.

  The pulseaudio log collects initial messages, but nothing else is
  echoed to the log - which could be anything from 3-20 minutes
  [typically].

  I'm more than happy to assist in getting whatever logs are required, but 
nothing I've seen documented seems to help.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  julie 30342 F pulseaudio
   /dev/snd/controlC1:  julie 30342 F pulseaudio
   /dev/snd/controlC2:  julie 30342 F pulseaudio
   /dev/snd/controlC0:  julie 30342 F pulseaudio
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2015-05-19 (670 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Package: pulseaudio 1:9.0-2ubuntu2.1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_NZ:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  Tags:  yakkety
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-USB3 6.0
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3 6.0
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-03-18T20:58:01.387562
  mtime.conffile..etc.pulse.default.pa: 2015-12-20T08:49:47.368322

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1673942/+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 1674511] Re: systray.py crashed with SIGSEGV in QMetaObject::activate()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1616964, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1674511/+attachment/4841247/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1674511/+attachment/4841249/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1674511/+attachment/4841257/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1674511/+attachment/4841259/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1674511/+attachment/4841260/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1674511/+attachment/4841261/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1674511/+attachment/4841262/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1616964

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systray.py crashed with SIGSEGV in QMetaObject::activate()

Status in hplip package in Ubuntu:
  New

Bug description:
  was setting new printer.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: hplip-data 3.16.11+repack0-2
  ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
  Uname: Linux 4.9.0-12-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Mar 20 20:36:41 2017
  Dependencies:
   gcc-6-base 6.3.0-8ubuntu1
   libc6 2.24-7ubuntu2
   libgcc1 1:6.3.0-8ubuntu1
   liblzma5 5.2.2-1.2
   xz-utils 5.2.2-1.2
  ExecutablePath: /usr/share/hplip/systray.py
  InstallationDate: Installed on 2017-03-20 (0 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  InterpreterPath: /usr/bin/python3.5
  Lpstat: device for ENVY_5530: hp:/net/ENVY_5530_series?ip=10.0.0.252
  MachineType: LENOVO 20179
  PackageArchitecture: all
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/ENVY_5530.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/ENVY_5530.ppd: Permission denied
  ProcCmdline: /usr/bin/python3 /usr/bin/hp-systray --force-startup
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-12-generic 
root=UUID=bf9df82f-98d4-4342-b160-61fa1f7811b0 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f057c131ea1 
<_ZN11QMetaObject8activateEP7QObjectiiPPv+49>:  testb  $0x2,0x20(%rax)
   PC (0x7f057c131ea1) ok
   source "$0x2" ok
   destination "0x20(%rax)" (0x55890035) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: hplip
  StacktraceTop:
   QMetaObject::activate(QObject*, int, int, void**) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platformthemes/libqgtk2.so
   ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platformthemes/libqgtk2.so
   ?? () from 
/usr/lib/python3/dist-packages/PyQt5/QtWidgets.cpython-35m-x86_64-linux-gnu.so
   PyCFunction_Call ()
  Title: systray.py crashed with SIGSEGV in QMetaObject::activate()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 10/02/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6CCN93WW(V8.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo IdeaPad N585
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad N585
  dmi.modalias: 
dmi:bvnLENOVO:bvr6CCN93WW(V8.05):bd10/02/2012:svnLENOVO:pn20179:pvrLenovoIdeaPadN585:rvnLENOVO:rnLenovoIdeaPadN585:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadN585:
  dmi.product.name: 20179
  dmi.product.version: Lenovo IdeaPad N585
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: 

[Desktop-packages] [Bug 1674455] Re: Keyboard input disables when laptop is rotated

[tim474]

UPDATE: Ctrl+alt+F1 and terminal doesn't work too.

But here is a workaround with disabling accelerometer:

echo "0" > "/sys/bus/usb/devices/1-2.4/power/autosuspend"
echo "auto" > "/sys/bus/usb/devices/1-2.4/power/level"
echo 1-2.4 > /sys/bus/usb/drivers/usb/unbind


(after power on and resume from suspend).

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

Title:
  Keyboard input disables when laptop is rotated

Status in xorg package in Ubuntu:
  New

Bug description:
  I have Dell Inspirion 11-3168 with accelerometer. Now I don't want to
  use accelerometer. But if I turn the laptop to side, keyboard input
  become disabled. I can switch to console by ctrl+alt+F1 and type in
  console but I can't type in GUI when laptop is on it's side.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Mar 20 22:03:18 2017
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1674455/+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 1385572] Re: gnome-session not shutting down cleanly

[Jeremy Bicha]

Justo, this bug is closed. You'll need to open a new bug for whatever
issue you are experiencing.

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

Title:
  gnome-session not shutting down cleanly

Status in Ubuntu GNOME:
  Fix Released
Status in gnome-session package in Ubuntu:
  Fix Released
Status in gnome-session source package in Trusty:
  Fix Released
Status in gnome-session source package in Utopic:
  Fix Released
Status in gnome-session source package in Vivid:
  Fix Released

Bug description:
  [Impact]
  We have had reports going back to 13.10 that gnome-shell extensions are 
disabled after restart (LP: #1236749), this has probably been our #1 unresolved 
bug for the last few cycles. While this is the main user visible bug probably 
other bugs caused by this for example (BGO: #745707)

  The cause was tracked down to gnome-session not shutting down cleanly
  under upstart. Although the underlying issue seems to be the order in
  which upstart takes down the various components in a user session, the
  side-effects themselves appear to be caused by gnome-session
  continuing to run when it should in fact be shutdown

  The fix updates the 103_kill_the_fail_whale.patch to force shutdown of
  gnome-session. This is inline with the fix upstream for (BGO: #745707)
  also.

  [ Test Case ]
  Note: This is only reproducible under upstart init.
  1. Load gdm
  2. Login to gnome-shell using GNOME from the session list
  3. enable some extensions
  4. reboot system from user menu.
  5. login again to find extensions disabled.

  [ Regression Potential ]
  Very low, the fail whale is meant to be fatal. The upstream dialog that is 
disabled in ubuntu does in fact cause gnome-session to get shutdown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1385572/+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 1637959] Re: Gnome Character Map (gucharmap) displays characters white-on-white when global dark theme is on

[Jeremy Bicha]

The issue you described was worked around for Adwaita by forcing the
dark mode off. The workaround was removed in the new version of
gucharmap available in Ubuntu 17.04 Beta because the underlying Adwaita
issue was fixed in gtk 3.22. Ubuntu 16.04 LTS uses gtk 3.18.

I'm closing this bug since this appears to be triggered by using a theme
that is not packaged in Ubuntu so it can't be fixed by Ubuntu
developers.

Please report this problem to your theme's developers.

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

Title:
  Gnome Character Map (gucharmap)  displays characters white-on-white
  when global dark theme is on

Status in gucharmap package in Ubuntu:
  New

Bug description:
  I use a dark theme globally, and gucharmap has a problem with dark
  themes. The problem is that in the character table, only the currently
  selected character is visible, whereas all other characters are
  displayed as white glyphs on white background, therefore, are
  invisible.

  I'm attaching a screenshot with this effect visible. You can observe
  that U+0034 DIGIT FOUR is the character currently selected, and it is
  the only one that can be seen in the table.

  I'm running Xubuntu 16.04.1 LTS. The theme I'm using is called Add-
  Waiter (which is basically a dark-by-default version of Adwaita), and
  the version number of gucharmap is visible in the About dialog (exact
  version of the package is 1:3.18.2-1ubuntu1).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gucharmap/+bug/1637959/+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 1671731] Re: [xmir] closing an app while a child window is opened leaves an Xmir process opened eating 100% CPU

[Stephen M. Webb]

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

Title:
  [xmir] closing an app while a child window is opened leaves an Xmir
  process opened eating 100% CPU

Status in Canonical System Image:
  Confirmed
Status in ubuntu-app-launch package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Ubuntu 17.04 Unity 8
  [xmir] closing an app while a child window is opened leaves an Xmir process 
opened eating 100% CPU

  launch solitaire (just click on the sol icon from launcher, it will just run 
on Xmir)
  open the about window from the menu (Help \ About)
  now close the main window 

  now top in a terminal (see attached)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671731/+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 1671731] Re: [xmir] closing an app while a child window is opened leaves an Xmir process opened eating 100% CPU

[Stephen M. Webb]

This is simple to reproduce.  The application has disappeared from the
screen but continues to run.

It looks like qtmir is closing the window (as requested) but no word
gets out to the actual process (ie. there is no session management).
I'm suspecting the Unity 8 lifecycle for desktops is not in place yet.

Here's a snippet from $HOME/.cahe/upstart/unity8.log.

[2017-03-20:19:34:52.953] qtmir.sessions: TaskController::onSessionStarting - 
sessionName=sol^M
[2017-03-20:19:34:52.954] qtmir.applications: 
Application["sol"]::setSession(session=qtmir::Session(0x4ecb3290))^M
[2017-03-20:19:34:53.457] 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/1.3/Icon.qml:115:5: 
QML Image: Cannot open: file:///home/stephenw/.face^M
[2017-03-20:19:34:57.992] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::MirSurface(type=normal,state=restored,size=(480,376),parentSurface=QObject(0x0))^M
[2017-03-20:19:34:58.015] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::registerView(268052752) after=1^M
[2017-03-20:19:34:58.032] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::setKeymap("us")^M
[2017-03-20:19:34:58.467] toplevelwindowmodel: prependSurface appId=sol 
surface=qtmir::MirSurface(0x3c828f80), filling out placeholder. after: 
(index=0,appId=sol,surface=0x3c828f80,id=11),(index=1,appId=unity8-dash,surface=0x225db2f0,id=4)^M
[2017-03-20:19:34:58.468] toplevelwindowmodel: setFocusedWindow(0x0)^M
[2017-03-20:19:34:58.499] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::setFocused(true)^M
[2017-03-20:19:34:58.514] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::setReady()^M
[2017-03-20:19:34:58.520] qtmir.applications: 
Application["sol"]::setInternalState(state=Running)^M
[2017-03-20:19:34:58.537] toplevelwindowmodel: 
setFocusedWindow(Window[0x28c28060, id=11, 
MirSurface[0x3c828f80,"AisleRiot"]])^M
[2017-03-20:19:34:58.664] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::requestState(restored)^M
[2017-03-20:19:34:58.673] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::updateExposure(true)^M
[2017-03-20:19:35:19.651] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::MirSurface(type=menu,state=restored,size=(172,66),parentSurface=qtmir::MirSurface(0x3c828f80))^M
[2017-03-20:19:35:19.801] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::registerView(745266864) after=1^M
[2017-03-20:19:35:20.080] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::setFocused(false)^M
[2017-03-20:19:35:20.093] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::setFocused(true)^M
[2017-03-20:19:35:20.098] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::setReady()^M
[2017-03-20:19:35:20.123] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::updateExposure(true)^M
[2017-03-20:19:35:20.126] toplevelwindowmodel: 
setFocusedWindow(Window[0x33e53dc0, id=12, 
MirSurface[0x28beec90,"AisleRiot"]])^M
[2017-03-20:19:35:20.128] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::setKeymap("us")^M
[2017-03-20:19:35:23.549] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::setLive(false)^M
[2017-03-20:19:35:23.552] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::unregisterView(745266864) after=0 live=false^M
[2017-03-20:19:35:23.553] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::updateExposure(false)^M
[2017-03-20:19:35:23.555] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::setFocused(true)^M
[2017-03-20:19:35:23.622] toplevelwindowmodel: 
setFocusedWindow(Window[0x28c28060, id=11, MirSurface[0x3c828f80,"Klondike"]])^M
[2017-03-20:19:35:23.625] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::~MirSurface() viewCount=0^M
[2017-03-20:19:35:23.684] qtmir.surfaces: 
MirSurface[0x35577d70,"sol"]::MirSurface(type=dialog,state=restored,size=(468,353),parentSurface=qtmir::MirSurface(0x3c828f80))^M
[2017-03-20:19:35:23.711] qtmir.surfaces: 
MirSurface[0x35577d70,"sol"]::registerView(744596304) after=1^M
[2017-03-20:19:35:23.893] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::setFocused(false)^M
[2017-03-20:19:35:23.904] qtmir.surfaces: 
MirSurface[0x35577d70,"sol"]::setFocused(true)^M
[2017-03-20:19:35:23.911] qtmir.surfaces: 
MirSurface[0x35577d70,"sol"]::setReady()^M
[2017-03-20:19:35:23.921] qtmir.surfaces: 
MirSurface[0x35577d70,"sol"]::updateExposure(true)^M
[2017-03-20:19:35:23.923] toplevelwindowmodel: 
setFocusedWindow(Window[0x2e53a140, id=13, MirSurface[0x35577d70,"About 
Aisleriot"]])^M
[2017-03-20:19:35:23.924] qtmir.surfaces: 
MirSurface[0x35577d70,"sol"]::setKeymap("us")^M
[2017-03-20:19:35:26.995] qtmir.surfaces: 
MirSurface[0x35577d70,"sol"]::activate()^M
[2017-03-20:19:35:57.911] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::close()^M
[2017-03-20:19:36:00.995] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::onCloseTimedOut()^M
[2017-03-20:19:36:01.013] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::setLive(false)^M
[2017-03-20:19:36:01.018] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::unregisterView(268052752) after=0 live=false^M
[2017-03-20:19:36:01.020] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::updateExposure(false)^M
[2017-03-20:19:36:01.025] qtmir.surfaces: 

[Desktop-packages] [Bug 1385572] Re: gnome-session not shutting down cleanly

[Justo]

Hi, I run gnome 16.04 on a lenovo yoga 910 and I still get the disabled
extensions after reboot and after wake from suspend. I employed this
workaround "https://scognito.wordpress.com/2014/11/30/fix-gnome-
shell-3-12-extensions-being-disabled-at-every-startup/", but the bug is
not fixed. So far, the workaround works. Will try to disable and re-
enable via gnome-tweak-tool in comment #20 and see if it solves it
(without the workaround).

Thanks!

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

Title:
  gnome-session not shutting down cleanly

Status in Ubuntu GNOME:
  Fix Released
Status in gnome-session package in Ubuntu:
  Fix Released
Status in gnome-session source package in Trusty:
  Fix Released
Status in gnome-session source package in Utopic:
  Fix Released
Status in gnome-session source package in Vivid:
  Fix Released

Bug description:
  [Impact]
  We have had reports going back to 13.10 that gnome-shell extensions are 
disabled after restart (LP: #1236749), this has probably been our #1 unresolved 
bug for the last few cycles. While this is the main user visible bug probably 
other bugs caused by this for example (BGO: #745707)

  The cause was tracked down to gnome-session not shutting down cleanly
  under upstart. Although the underlying issue seems to be the order in
  which upstart takes down the various components in a user session, the
  side-effects themselves appear to be caused by gnome-session
  continuing to run when it should in fact be shutdown

  The fix updates the 103_kill_the_fail_whale.patch to force shutdown of
  gnome-session. This is inline with the fix upstream for (BGO: #745707)
  also.

  [ Test Case ]
  Note: This is only reproducible under upstart init.
  1. Load gdm
  2. Login to gnome-shell using GNOME from the session list
  3. enable some extensions
  4. reboot system from user menu.
  5. login again to find extensions disabled.

  [ Regression Potential ]
  Very low, the fail whale is meant to be fatal. The upstream dialog that is 
disabled in ubuntu does in fact cause gnome-session to get shutdown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1385572/+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 1232471] Re: Java apps crash under XMir trying to set a custom cursor

[Don-vip]

Confirmed, this is an OpenJDK bug: 
https://bugs.openjdk.java.net/browse/JDK-8173853
Fixed in 8u152 and 9.

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

Title:
  Java apps crash under XMir trying to set a custom cursor

Status in JOSM:
  Unknown
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Java apps crash under XMir (cannot load system cursor)

  ORIGINAL DESCRIPTION:
  When i run XMir an Unity System Compositor, java based applications JetBrains 
PyCharm and IntelliJ (those i've tested) don't work correctly.
  At this time i haven't tested Elicpse or NetBeans so i don't know if is 
general problem with OpenJDK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/josm/+bug/1232471/+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 1232471] Re: Java apps crash under XMir trying to set a custom cursor

[Don-vip]

** Changed in: josm
   Importance: Unknown => High

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

Title:
  Java apps crash under XMir trying to set a custom cursor

Status in JOSM:
  Unknown
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Java apps crash under XMir (cannot load system cursor)

  ORIGINAL DESCRIPTION:
  When i run XMir an Unity System Compositor, java based applications JetBrains 
PyCharm and IntelliJ (those i've tested) don't work correctly.
  At this time i haven't tested Elicpse or NetBeans so i don't know if is 
general problem with OpenJDK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/josm/+bug/1232471/+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 1659586] Re: NVIDIA CVE-2016-8826 and CVE-2017-0318

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-304 -
304.135-0ubuntu0.16.04.1

---
nvidia-graphics-drivers-304 (304.135-0ubuntu0.16.04.1) xenial; urgency=medium

  * SECURITY UPDATE:
- CVE-2017-0318 (LP: #1659586).
  * New upstream release.
  * debian/dkms_nvidia/patches/buildfix_kernel_4.9.patch,
debian/dkms_nvidia/patches/buildfix_kernel_4.10.patch,
debian/templates/dkms_nvidia.conf.in:
- Add support for Linux 4.9 and 4.10.

 -- Alberto Milone   Wed, 08 Mar 2017
15:02:55 +0100

** Changed in: nvidia-graphics-drivers-304 (Ubuntu Xenial)
   Status: In Progress => 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/1659586

Title:
  NVIDIA CVE-2016-8826 and CVE-2017-0318

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Precise:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Precise:
  Fix Released
Status in nvidia-graphics-drivers-367 source package in Precise:
  Invalid
Status in nvidia-graphics-drivers-304 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-367 source package in Trusty:
  In Progress
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-367 source package in Xenial:
  In Progress
Status in nvidia-graphics-drivers-304 source package in Yakkety:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Yakkety:
  Fix Released
Status in nvidia-graphics-drivers-367 source package in Yakkety:
  In Progress

Bug description:
  The following nvidia drivers series are affected by both CVE-2016-8826
  and CVE-2017-0318:

  367

  The following nvidia drivers series are affected by CVE-2017-0318
  (USN-3173-1 already fixed CVE-2016-8826):

  340, 304

  We also need to migrate users to the 375 series, as 367 is no longer
  supported by NVIDIA.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1659586/+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 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all

[Phil]

Hey Guys..noobie here so please be gentle.

I have a Asus X541U ... duel booting Ubuntu Studio 16.04 and Windows 10

Everything works fine in Windowswhen i boot up Ubuntu and sign into Skype, 
I can't get the mic working.  Same with other recording programs (Ie Audacity) 
I need to run JACK and IDJC as well with it...

Please any help would be amazing...everyone around me thinks I'm
speaking a different language

Thanks!

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

Title:
  [X555UA, Realtek ALC256, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256

  speakers work, it's just the mic not working.

  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0

  8 lines make mic working until reboot.

  thx a lot for

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: Unity
  Date: Sun Jun 26 23:56:46 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 2 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1596381/+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 1659586] Re: NVIDIA CVE-2016-8826 and CVE-2017-0318

[Tyler Hicks]

** Information type changed from Private Security to Public Security

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

Title:
  NVIDIA CVE-2016-8826 and CVE-2017-0318

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Precise:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Precise:
  Fix Released
Status in nvidia-graphics-drivers-367 source package in Precise:
  Invalid
Status in nvidia-graphics-drivers-304 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-367 source package in Trusty:
  In Progress
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-367 source package in Xenial:
  In Progress
Status in nvidia-graphics-drivers-304 source package in Yakkety:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Yakkety:
  Fix Released
Status in nvidia-graphics-drivers-367 source package in Yakkety:
  In Progress

Bug description:
  The following nvidia drivers series are affected by both CVE-2016-8826
  and CVE-2017-0318:

  367

  The following nvidia drivers series are affected by CVE-2017-0318
  (USN-3173-1 already fixed CVE-2016-8826):

  340, 304

  We also need to migrate users to the 375 series, as 367 is no longer
  supported by NVIDIA.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1659586/+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 1029289] Re: Need to authorize my google account each time I boot the computer

[Eugene Lazutkin]

This bug has started to appear for me in 16.10.

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

Title:
  Need to authorize my google account each time I boot the computer

Status in Online Accounts: Account plugins:
  Fix Released
Status in Online Accounts: Sign-on UI:
  Fix Released
Status in account-plugins package in Ubuntu:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in signon-plugin-oauth2 package in Ubuntu:
  Fix Released
Status in account-plugins source package in Quantal:
  Fix Released
Status in signon-plugin-oauth2 source package in Quantal:
  Fix Released
Status in account-plugins source package in Trusty:
  Fix Released
Status in evolution-data-server source package in Trusty:
  Fix Released
Status in signon-plugin-oauth2 source package in Trusty:
  Fix Released

Bug description:
  [Impact] Google calendar integration is broken, and users are
  requested to re-enter their Google password everytime they log in, or
  everytime they enable/disable their Google account from the System
  Settings.

  [Test Case] Disable/re-enable your Google account. When affected by
  this bug, a notification will appear and you'll be asked to enter your
  Google password in the Online Accounts panel in System Settings.

  [Regression Potential] Minimal: the fix is a backport of a patch from
  the evolution-data-server code which is already in 14.10, and which
  only touches the calendar code (which is currently broken).


  Old description
  ===

  [Test Case] Sometimes after one day, sometimes after one week, the
  system indicator will turn red and the Google account will be marked
  as needing reauthentication. Time can vary, but any period shorter
  than one month is a symptom of the bug.

  [Regression Potential] Minimal: the change to the Google plugin (in
  account-plugins) simply changes the authentication method, in a way
  that is well-documented. The change in signon-plugin-oauth2 affects
  only those accounts/providers which use the OAuth refresh tokens --
  which is only Google, at the moment -- and in a way that can't
  possibly break any existing functionality; if the new code had some
  mistake, the refresh token would be unusable and the system would
  automatically fall back to requesting a new access token (which is
  exactly what happens now, with this bug).

  I'll try to find why the account-plugins package was not uploaded;
  indeed, both are required in order to fix this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1029289/+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 1637316] Re: Screen flickering/tearing on Ubuntu 16.10 64-bit on kernel version 4.8.0-26-generic

[Dev]

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

Yes it does actually, thanks for letting me know. You can close this as
a duplicate then. Thanks!

** This bug has been marked a duplicate of bug 1663989
   Screen flickering

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

Title:
  Screen flickering/tearing on Ubuntu 16.10 64-bit on kernel version
  4.8.0-26-generic

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

Bug description:
  After upgrading to Ubuntu 16.10 and booting with kernel version
  4.8.0-26-generic, I can see screen flickering/tearing. If I boot up
  using previous kernel version 4.4.0, then this issues do not appear.
  This is an Intel GPU laptop with an nvidia graphics card. I would be
  glad to provide more debug information if needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1637316/+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 1300215] Re: Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory

[Launchpad Bug Tracker]

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

** Changed in: vdr-plugin-xineliboutput (Ubuntu)
   Status: New => Confirmed

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

Title:
  Failed to open VDPAU backend libvdpau_i965.so: cannot open shared
  object file: No such file or directory

Status in libvdpau package in Ubuntu:
  Triaged
Status in libvdpau-va-gl package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in vdr-plugin-xineliboutput package in Ubuntu:
  Confirmed
Status in vlc package in Ubuntu:
  Confirmed
Status in xine-ui package in Ubuntu:
  Confirmed
Status in libvdpau package in Debian:
  New

Bug description:
  This has been bothering me at least since precise (although there the
  missing link went to libvdpau_nvidia.so which was all the more
  mysterious since I do not own NVIDIA hardware).  In numerous cases do
  I get a warning that libvdpau_i965.so is being tried to be accessed
  but it fails.  I also can't find that file anywhere on my system or in
  the Ubuntu repository.  I tried poking around with ldd to find out
  where the call to that lib comes from but so far unsuccessful.

  $ vdpauinfo
  display: :0   screen: 0
  Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object 
file: No such file or directory
  Error creating VDPAU device: 1

  libvdpau1:i386 is version 0.7-1 and vdpauinfo is 0.1-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvdpau/+bug/1300215/+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 1674477] [NEW] gnome screenshot gtk-mir crashes on taking the shot

[kevin gunn]

Public bug reported:

Tried this with (updated) Zesty plus ppa:attente/gtk-mir-staging
then export GDK_BACKEND=mir
launch from command line: gnome-screenshot -- 
--desktop_file_hint=org.gnome.Screenshot.desktop

Attempt to take a screen shot in any form and it will crash (see
attached log)


according to attente: 
gnome-screenshot crashes is because it delegates the screenshotting to 
org.gnome.Shell, and falls back to using x11 if that fails
so i think the solution is to have u8 implement that interface...
https://git.gnome.org/browse/gnome-shell/tree/data/org.gnome.Shell.Screenshot.xml

** Affects: canonical-devices-system-image
 Importance: High
 Status: New

** Affects: gtk+3.0 (Ubuntu)
 Importance: High
 Status: New

** Affects: unity8 (Ubuntu)
 Importance: High
 Status: New


** Tags: unity8-desktop

** Attachment added: "screenshot.log"
   
https://bugs.launchpad.net/bugs/1674477/+attachment/4841196/+files/screenshot.log

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unity8 (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: unity8-desktop

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => High

** Changed in: unity8 (Ubuntu)
   Importance: Undecided => High

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

Title:
  gnome screenshot gtk-mir crashes on taking the shot

Status in Canonical System Image:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Tried this with (updated) Zesty plus ppa:attente/gtk-mir-staging
  then export GDK_BACKEND=mir
  launch from command line: gnome-screenshot -- 
--desktop_file_hint=org.gnome.Screenshot.desktop

  Attempt to take a screen shot in any form and it will crash (see
  attached log)

  
  according to attente: 
  gnome-screenshot crashes is because it delegates the screenshotting to 
org.gnome.Shell, and falls back to using x11 if that fails
  so i think the solution is to have u8 implement that interface...
  
https://git.gnome.org/browse/gnome-shell/tree/data/org.gnome.Shell.Screenshot.xml

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1674477/+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 1300215] Re: Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory

[Launchpad Bug Tracker]

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

** Changed in: vlc (Ubuntu)
   Status: New => Confirmed

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

Title:
  Failed to open VDPAU backend libvdpau_i965.so: cannot open shared
  object file: No such file or directory

Status in libvdpau package in Ubuntu:
  Triaged
Status in libvdpau-va-gl package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in vdr-plugin-xineliboutput package in Ubuntu:
  Confirmed
Status in vlc package in Ubuntu:
  Confirmed
Status in xine-ui package in Ubuntu:
  Confirmed
Status in libvdpau package in Debian:
  New

Bug description:
  This has been bothering me at least since precise (although there the
  missing link went to libvdpau_nvidia.so which was all the more
  mysterious since I do not own NVIDIA hardware).  In numerous cases do
  I get a warning that libvdpau_i965.so is being tried to be accessed
  but it fails.  I also can't find that file anywhere on my system or in
  the Ubuntu repository.  I tried poking around with ldd to find out
  where the call to that lib comes from but so far unsuccessful.

  $ vdpauinfo
  display: :0   screen: 0
  Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object 
file: No such file or directory
  Error creating VDPAU device: 1

  libvdpau1:i386 is version 0.7-1 and vdpauinfo is 0.1-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvdpau/+bug/1300215/+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 1300215] Re: Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory

[Launchpad Bug Tracker]

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

** Changed in: xine-ui (Ubuntu)
   Status: New => Confirmed

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

Title:
  Failed to open VDPAU backend libvdpau_i965.so: cannot open shared
  object file: No such file or directory

Status in libvdpau package in Ubuntu:
  Triaged
Status in libvdpau-va-gl package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in vdr-plugin-xineliboutput package in Ubuntu:
  Confirmed
Status in vlc package in Ubuntu:
  Confirmed
Status in xine-ui package in Ubuntu:
  Confirmed
Status in libvdpau package in Debian:
  New

Bug description:
  This has been bothering me at least since precise (although there the
  missing link went to libvdpau_nvidia.so which was all the more
  mysterious since I do not own NVIDIA hardware).  In numerous cases do
  I get a warning that libvdpau_i965.so is being tried to be accessed
  but it fails.  I also can't find that file anywhere on my system or in
  the Ubuntu repository.  I tried poking around with ldd to find out
  where the call to that lib comes from but so far unsuccessful.

  $ vdpauinfo
  display: :0   screen: 0
  Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object 
file: No such file or directory
  Error creating VDPAU device: 1

  libvdpau1:i386 is version 0.7-1 and vdpauinfo is 0.1-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvdpau/+bug/1300215/+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 1300215] Re: Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory

[Launchpad Bug Tracker]

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

** Changed in: linux-lts-xenial (Ubuntu)
   Status: New => Confirmed

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

Title:
  Failed to open VDPAU backend libvdpau_i965.so: cannot open shared
  object file: No such file or directory

Status in libvdpau package in Ubuntu:
  Triaged
Status in libvdpau-va-gl package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in vdr-plugin-xineliboutput package in Ubuntu:
  Confirmed
Status in vlc package in Ubuntu:
  Confirmed
Status in xine-ui package in Ubuntu:
  Confirmed
Status in libvdpau package in Debian:
  New

Bug description:
  This has been bothering me at least since precise (although there the
  missing link went to libvdpau_nvidia.so which was all the more
  mysterious since I do not own NVIDIA hardware).  In numerous cases do
  I get a warning that libvdpau_i965.so is being tried to be accessed
  but it fails.  I also can't find that file anywhere on my system or in
  the Ubuntu repository.  I tried poking around with ldd to find out
  where the call to that lib comes from but so far unsuccessful.

  $ vdpauinfo
  display: :0   screen: 0
  Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object 
file: No such file or directory
  Error creating VDPAU device: 1

  libvdpau1:i386 is version 0.7-1 and vdpauinfo is 0.1-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvdpau/+bug/1300215/+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 1674121] Re: "Restore" asks for cryptic authentication to run /bin/sh as superuser

[Vej]

Hello Christopher!

Could you please provide us with the file /tmp/deja-dup.gsettings after running 
the following line (you may want to scrub the file of any incriminating file 
names or details):
gsettings list-recursively org.gnome.DejaDup > /tmp/deja-dup.gsettings

** Changed in: deja-dup (Ubuntu)
   Status: New => Incomplete

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

Title:
  "Restore" asks for cryptic authentication to run /bin/sh as superuser

Status in deja-dup package in Ubuntu:
  Incomplete

Bug description:
  I am trying to restore a full backup to an external hard drive.
  After 20 minutes or so, a cryptic gui popup arises which says that "some 
process" wants sudo authentication to run /bin/sh

  It is surely a bug to generate such a vague request for sudo use.

  I note it has been this way since 2013
  (https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1079553 which
  has been unaddressed, so the outcome of denying this request is still
  a great pain), but I am pointing out that this kind of permission
  request is itself a bug, if not a security risk because it teaches
  users to give that kind of permission to an unknown script.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: deja-dup 34.2-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17
  Uname: Linux 4.8.0-42-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Mar 19 12:35:43 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-02-12 (400 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to yakkety on 2017-01-21 (56 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1674121/+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 1028115] Re: Gdk.cairo_region_create_from_surface() raises an error in GI

[Bug Watch Updater]

** Changed in: pygobject
   Status: Confirmed => Fix Released

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

Title:
  Gdk.cairo_region_create_from_surface() raises an error in GI

Status in pygobject:
  Fix Released
Status in py3cairo package in Ubuntu:
  Fix Released
Status in pygobject package in Ubuntu:
  Fix Released
Status in py3cairo package in Debian:
  Fix Released

Bug description:
  This happens on current 12.10 daily:

  >>> from gi.repository import Gdk
  >>> import cairo
  >>> surface = cairo.ImageSurface(0, 100, 100)
  >>> Gdk.cairo_region_create_from_surface(surface)
  Traceback (most recent call last):
File "", line 1, in 
File "/usr/lib/python2.7/dist-packages/gi/types.py", line 47, in function
  return info.invoke(*args, **kwargs)
  TypeError: Couldn't find conversion for foreign struct 'cairo.Region'

  Upstream has some additional info and a couple of patches for this:
  https://bugzilla.gnome.org/show_bug.cgi?id=667959
  https://bugs.freedesktop.org/show_bug.cgi?id=44336

To manage notifications about this bug go to:
https://bugs.launchpad.net/pygobject/+bug/1028115/+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 1674462] Re: !

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1671316, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1674462/+attachment/4841159/+files/CoreDump.gz

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1674462/+attachment/4841163/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1674462/+attachment/4841164/+files/ProcStatus.txt

** This bug has been marked a duplicate of bug 1671316
   bamfdaemon crashed with SIGSEGV in sn_xcb_display_new()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  !

Status in bamf package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: bamfdaemon 0.5.3+16.10.20160929-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Mar 20 22:30:56 2017
  ExecutablePath: /usr/lib/x86_64-linux-gnu/bamf/bamfdaemon
  InstallationDate: Installed on 2017-03-14 (6 days ago)
  InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/bamf/bamfdaemon
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: bamf
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1674462/+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 1674455] [NEW] Keyboard input disables when laptop is rotated

[tim474]

Public bug reported:

I have Dell Inspirion 11-3168 with accelerometer. Now I don't want to
use accelerometer. But if I turn the laptop to side, keyboard input
become disabled. I can switch to console by ctrl+alt+F1 and type in
console but I can't type in GUI when laptop is on it's side.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
Uname: Linux 4.8.0-41-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Mar 20 22:03:18 2017
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug yakkety

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

Title:
  Keyboard input disables when laptop is rotated

Status in xorg package in Ubuntu:
  New

Bug description:
  I have Dell Inspirion 11-3168 with accelerometer. Now I don't want to
  use accelerometer. But if I turn the laptop to side, keyboard input
  become disabled. I can switch to console by ctrl+alt+F1 and type in
  console but I can't type in GUI when laptop is on it's side.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Mar 20 22:03:18 2017
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1674455/+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 1669643] Re: Wifi WPA2-PSK 4-Way Handshake Faliure

[Dhruv Ramdev]

I am facing issue almost similar to your. I have ubuntu gnome 17.04 .I
can connect to wifi but the wifi does not seem to work even though it
shows connected. I dont have much knowledge of troubleshooting . What
file will be needed?

Chrome Shows : DNS PROBE BAD CONFIG .

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

Title:
  Wifi WPA2-PSK 4-Way Handshake Faliure

Status in network-manager package in Ubuntu:
  New

Bug description:
  After I upgraded to Ubuntu 17.04 yesterday, I started having this
  problem. My device will only connect to unsecured (public) WiFi
  networks. I tried booting into an older series kernel (4.8.0) and the
  issue persisted.

  I ran `sudo systemctl status network-manager` and got this:

  device (wlx501ac505fcbc): supplicant interface state: associating -> 4-way 
handshake
  sup-iface[0x55eb41e5bc20,wlx501ac505fcbc]: connection disconnected (reason 15)
  device (wlx501ac505fcbc): supplicant interface state: 4-way handshake -> 
disconnected
  device (wlx501ac505fcbc): Activation: (wifi) disconnected during association, 
asking for new key
  device (wlx501ac505fcbc): state change: config -> need-auth (reason 
'supplicant-disconnect') [50 60 8]
  device (wlx501ac505fcbc): supplicant interface state: disconnected -> inactive

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar  2 20:55:59 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-01-04 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  IpRoute:
   default via 192.168.42.129 dev enp0s20u2 proto static metric 100 
   169.254.0.0/16 dev enp0s20u2 scope link metric 1000 
   192.168.42.0/24 dev enp0s20u2 proto kernel scope link src 192.168.42.246 
metric 100
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH 
  
   enp0s20u2  ethernet  connected 
/org/freedesktop/NetworkManager/Devices/4  Wired connection 1  
474aac38-e4d8-4102-b2eb-c5cc6bdb17aa  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   AC:37:43:7C:B4:57  btdisconnected  
/org/freedesktop/NetworkManager/Devices/3  --  --   
 -- 
   wlx501ac505fcbcwifi  disconnected  
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/0  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.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/1669643/+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 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)

[Denys Vitali]

Same problem here, Acer Aspire VN7-792G

00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
HD Audio (rev 31)

dvitali@denvit-ws1:~ $ aplay -L 
  -1-
null
Discard all samples (playback) or generate zero samples (capture)
pulse
PulseAudio Sound Server
sysdefault:CARD=PCH
HDA Intel PCH, ALC255 Analog
Default Audio Device
front:CARD=PCH,DEV=0
HDA Intel PCH, ALC255 Analog
Front speakers
surround21:CARD=PCH,DEV=0
HDA Intel PCH, ALC255 Analog
2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=PCH,DEV=0
HDA Intel PCH, ALC255 Analog
4.0 Surround output to Front and Rear speakers
surround41:CARD=PCH,DEV=0
HDA Intel PCH, ALC255 Analog
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=PCH,DEV=0
HDA Intel PCH, ALC255 Analog
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=PCH,DEV=0
HDA Intel PCH, ALC255 Analog
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=PCH,DEV=0
HDA Intel PCH, ALC255 Analog
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=PCH,DEV=0
HDA Intel PCH, ALC255 Digital
IEC958 (S/PDIF) Digital Audio Output
hdmi:CARD=PCH,DEV=0
HDA Intel PCH, HDMI 0
HDMI Audio Output
hdmi:CARD=PCH,DEV=1
HDA Intel PCH, HDMI 1
HDMI Audio Output
hdmi:CARD=PCH,DEV=2
HDA Intel PCH, HDMI 2
HDMI Audio Output

--
Linux denvit-ws1 4.10.3-1-ARCH #1 SMP PREEMPT Wed Mar 15 09:17:17 CET 2017 
x86_64 GNU/Linux
--
dvitali@denvit-ws1:~ $ cat /proc/asound/cards   
  -1-
 0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 129
-
pacman -Q | grep ^alsa
alsa-lib 1.1.3-1
alsa-plugins 1.1.1-1
alsa-utils 1.1.3-2
alsaequal 0.6-16

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

Title:
  Alsa not detecting internal microphone [ALC255] (Realtek)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present 

[Desktop-packages] [Bug 1636564] Re: Segfault from libX11.so.6.3.0

[Jan Lachnitt]

Another report and some thoughts below

HW: Asus Vivobook (touchscreen, Intel graphics), external monitor attached.
OS: Linux Mint 18 Cinnamon x64.
State before crash: Running X session using both displays ("big desktop"), 
several applications, Vivaldi browser active.
My aim: Lock the computer.
Course of action, the USUAL part: Pressed Ctrl+Alt+L, not locked - Vivaldi 
displayed its menu (to be displayed upon pressing Alt), tapped the touchscreen 
to get rid of the menu and thus actually lock the computer.
Course of action, the UNUSUAL part: Black screen for a few seconds, then login 
screen, old X session gone.

syslog:
Mar 20 14:43:20 VivoBook org.a11y.atspi.Registry[1729]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0"
Mar 20 14:43:20 VivoBook org.a11y.atspi.Registry[1729]:   after 2925 
requests (2925 known processed) with 0 events remaining.
Mar 20 14:43:20 VivoBook cinnamon-session[1640]: Gdk-WARNING: t+4492,79569s: 
cinnamon-session: Fatal IO error 11 (Prostředek je dočasně nepřístupný) on X 
server :0.
Mar 20 14:43:20 VivoBook org.gtk.vfs.Daemon[1711]: A connection to the bus 
can't be made
Mar 20 14:43:20 VivoBook org.gtk.vfs.Daemon[1711]: A connection to the bus 
can't be made
Mar 20 14:43:20 VivoBook mdm[1212]: WARNING: mdm_slave_xioerror_handler: 
Kritická chyba X - Restartování :0
Mar 20 14:43:20 VivoBook kernel: [ 4538.677519] vivaldi-bin[4100]: segfault at 
968 ip 7f61ac384643 sp 7ffc09f25b50 error 4 in 
libX11.so.6.3.0[7f61ac35c000+135000]
Mar 20 14:43:20 VivoBook ag[4118]: mdm-superpost Starting...
Mar 20 14:43:20 VivoBook ag[4122]: mdm-superpost Finished
Mar 20 14:43:20 VivoBook console-kit-daemon[1566]: (process:4128): 
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
Mar 20 14:43:21 VivoBook acpid: client 1219[0:0] has disconnected
Mar 20 14:43:21 VivoBook acpid: client connected from 4131[0:0]
Mar 20 14:43:21 VivoBook acpid: 1 client rule loaded
Mar 20 14:43:22 VivoBook ag[4139]: mdm-superinit Starting...
Mar 20 14:43:22 VivoBook ag[4140]: mdm-superinit Finished

Xorg.0.log covers the new session, Xorg.0.log.old has no record of the
event.

The segfault really seems to affect multiple users, especially with 
Chromium-based browsers, e.g.:
https://bbs.archlinux.org/viewtopic.php?id=131328 - from 2011 already
https://bbs.archlinux.org/viewtopic.php?id=221888 - solution?

I don't know if syslog preserves the order of events (within a second), but if 
yes, then the segfault is just a consequence of another problem, e.g.:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/999191

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

Title:
  Segfault from libX11.so.6.3.0

Status in libx11 package in Ubuntu:
  Confirmed

Bug description:
  Something went wrong with my Ubuntu 16.04 LTS desktop today.  When I
  got back to the system Mattermost and a Chrome were indicating that
  the network was not working.  I started to look about and it seemed
  that my main ethernet network connection had lost its IPv4 address
  somehow.  ifconfig and the GUI network manager confirmed this.

  To try and resolve this I physically removed the connector and the
  plugged it back in.  Shortly after I did this my GUI seemed to die out
  and I ended up back at the login screen.

  Once everything had calmed down I logged back in.  After some digging
  about in the logs I noticed the following in /var/log/kern.log

  Oct 25 13:01:09 thorne-ul-dt kernel: [694321.877561] Mattermost[744]: 
segfault at 968 ip 7f8a9e257643 sp 7ffe72a3b510 error 4 in 
libX11.so.6.3.0[7f8a9e22f000+135000]
  Oct 25 13:01:09 thorne-ul-dt kernel: [694322.029362] chrome[745]: segfault at 
968 ip 7fd4b5c73643 sp 7fff94f78d90 error 4 in 
libX11.so.6.3.0[7fd4b5c4b000+135000]

  That seemed to be the correct time for the problem I noticed.   What
  exactly caused it I am not sure.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libx11-6 2:1.6.3-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Oct 25 17:07:28 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
  InstallationDate: Installed on 2015-03-12 (592 

[Desktop-packages] [Bug 1673790] Re: bump LibreOffice to 5.3.1 on zesty and fix autpkgtest dependencies

[Bug Watch Updater]

** Changed in: libreoffice (Debian)
   Status: Unknown => Fix Released

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

Title:
  bump LibreOffice to 5.3.1 on zesty and fix autpkgtest dependencies

Status in libreoffice package in Ubuntu:
  Fix Committed
Status in libreoffice package in Debian:
  Fix Released

Bug description:
  Please sponsor LibreOffice 1:5.3.1-0ubuntu1 and the corresponding
  -l10n package to zesty (use dget):

   
http://people.canonical.com/~bjoern/zesty/5.3.1/libreoffice-l10n_5.3.1-0ubuntu1_source.changes
   
http://people.canonical.com/~bjoern/zesty/5.3.1/libreoffice_5.3.1-0ubuntu1_source.changes

  The few changes vs. version 1:5.3.0~rc3-0ubuntu2 are best viewed on
  git:

   
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?h=ubuntu-zesty-5.3=f4b5ece6b1783202ed286e1f149ab60c3471f180
   
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?h=ubuntu-zesty-5.3=af8b1b6e9d4f00d1d6d31063e56bd4ca5d70b910
   
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?h=ubuntu-zesty-5.3=c525f97bab587d69ce56cf81f2edbfb7ae685cd7
   
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?h=ubuntu-zesty-5.3=af39ca70101b069b214b01a197aa48ffc59820b8

  A zesty build with all but the the last change is available in the
  LibreOffice ppas at:

   https://launchpad.net/~libreoffice/+archive/ubuntu/ppa
   https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-5-3

  Note the last change is not substancial as LibreOffice 5.3.1 rc2 is
  equal to 5.3.1 final in everything but the version.

  NB: The LibreOffice package has some generated files in ./debian (e.g.
  control) so there might be more changes (in generated files) in the
  debdiff than the above.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1673790/+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 1673491] Re: [Zesty] libnl3 Segmentation fault in sriov environments

[Talat Batheesh]

Thank you ,
The update is passed and libnl updated to libnl-3-200:amd64 (3.2.29-0ubuntu2).

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

Title:
  [Zesty] libnl3 Segmentation fault in sriov environments

Status in libnl3 package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  New

Bug description:
  in Ubuntu 17.04 we can't open a virt-manager, we see sefault

  This issue happen when we update from kernel 4.10.0-9-generic to
  4.10.0-11-generic

  root@:~# /usr/sbin/libvirtd
  Segmentation fault (core dumped)   

  root@:~# gdb /usr/sbin/libvirtd ./core 
  GNU gdb (Ubuntu 7.12.50.20170314-0ubuntu1) 7.12.50.20170314-git
  Copyright (C) 2017 Free Software Foundation, Inc.  
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.   
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"   
  and "show warranty" for details. 
  This GDB was configured as "x86_64-linux-gnu".   
  Type "show configuration" for configuration details. 
  For bug reporting instructions, please see:  
  . 
  Find the GDB manual and other documentation resources online at: 
  .
  For help, type "help".   
  Type "apropos word" to search for commands related to "word"...  
  Reading symbols from /usr/sbin/libvirtd...(no debugging symbols found)...done.
  [New LWP 4232]
  [New LWP 4216]
  [New LWP 4219]
  [New LWP 4218]
  [New LWP 4231]
  [New LWP 4215]
  [New LWP 4220]
  [New LWP 4224]
  [New LWP 4221]
  [New LWP 4223]
  [New LWP 4222]
  [New LWP 4217]
  [New LWP 4225]
  [New LWP 4227]
  [New LWP 4230]
  [New LWP 4229]
  [New LWP 4228]
  [Thread debugging using libthread_db enabled] 
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/usr/sbin/libvirtd'.   
  Program terminated with signal SIGSEGV, Segmentation fault.   
  #0  0x7f97fa93367f in rtnl_link_sriov_parse_vflist () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200
  [Current thread is 1 (Thread 0x7f97dff94700 (LWP 4232))]  
   
  (gdb) where   
   
  #0  0x7f97fa93367f in rtnl_link_sriov_parse_vflist () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200
  #1  0x7f97fa927fad in ?? () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200  
  #2  0x7f980bfb76c3 in nl_cache_parse () from 
/lib/x86_64-linux-gnu/libnl-3.so.200
  #3  0x7f980bfb770b in ?? () from /lib/x86_64-linux-gnu/libnl-3.so.200 
   
  #4  0x7f980bfbdc1c in nl_recvmsgs_report () from 
/lib/x86_64-linux-gnu/libnl-3.so.200
  #5  0x7f980bfbe049 in nl_recvmsgs () from 
/lib/x86_64-linux-gnu/libnl-3.so.200   
  #6  0x7f980bfb6aab in ?? () from /lib/x86_64-linux-gnu/libnl-3.so.200 
   
  #7  0x7f980bfb763d in nl_cache_pickup () from 
/lib/x86_64-linux-gnu/libnl-3.so.200   
  #8  0x7f980bfb7871 in nl_cache_refill () from 
/lib/x86_64-linux-gnu/libnl-3.so.200   
  #9  0x7f97fa926975 in 

[Desktop-packages] [Bug 1668428] Re: gnome screen shot behaves strange on zesty unity8

[kevin gunn]

retested, overhauled description based on the latest findings (at least
I no longer see the u8 lockup now)

** Summary changed:

- gnome screen shot full lock up on zesty unity8
+ gnome screen shot behaves strange on zesty unity8

** Changed in: canonical-devices-system-image
   Status: Incomplete => New

** Changed in: gtk+3.0 (Ubuntu)
   Status: Incomplete => New

** No longer affects: unity8 (Ubuntu)

** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => High

** Changed in: xorg-server (Ubuntu)
   Importance: Undecided => High

** Description changed:

- Feb 27 iso build of zesty, clean u8 exploration
+ Updated Mar 20 zesty, clean u8 exploration
  
- gnome screenshot completely locks up the shell and eventually unity8 just 
restarts
+ gnome screenshot will seemingly quit, and will not capture the desired screen
  to repro:
  1) launch screenshot app from the app drawer
  2) make indications to take a screenshot ( i selected custom area to select)
  3) "take screenshot"
- result: complete lock up along with windowing oddity, frozen until unity8 res
+ result: application bail out, in the instance of "select area" case, it will 
take a screen shot in the instance of "full screen".
+ expected: get a screen shot of desired and the application should remain on 
screen.
+ 
+ I suspect this is due to screenshot's reliance on X and our use of Xmir
+ not being completely worked out in terms of what the applications
+ perception of the screen vs it's own window is.

** Changed in: canonical-devices-system-image
 Assignee: kevin gunn (kgunn72) => Stephen M. Webb (bregma)

** Changed in: gtk+3.0 (Ubuntu)
 Assignee: (unassigned) => William Hua (attente)

** Changed in: xorg-server (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

Title:
  gnome screen shot behaves strange on zesty unity8

Status in Canonical System Image:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Updated Mar 20 zesty, clean u8 exploration

  gnome screenshot will seemingly quit, and will not capture the desired screen
  to repro:
  1) launch screenshot app from the app drawer
  2) make indications to take a screenshot ( i selected custom area to select)
  3) "take screenshot"
  result: application bail out, in the instance of "select area" case, it will 
take a screen shot in the instance of "full screen".
  expected: get a screen shot of desired and the application should remain on 
screen.

  I suspect this is due to screenshot's reliance on X and our use of
  Xmir not being completely worked out in terms of what the applications
  perception of the screen vs it's own window is.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668428/+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 1428972] Re: Unmet dependencies for libcheese-gtk23 and libcheese7 on 14.04.2

[Karthik Radhakrishna]

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


I tried installing CUDA but ended with below error

sudo apt-get install nvidia-cuda-toolkit
--- Terminal Output 
--- 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 unity-control-center : Depends: libcheese-gtk23 (>= 3.4.0) but it is not going 
to be installed
Depends: libcheese7 (>= 3.0.1) but it is not going to 
be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

--- Terminal Output
---

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

Title:
  Unmet dependencies for libcheese-gtk23 and libcheese7 on 14.04.2

Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  I bumped into this issue while trying to install canonical-
  certification-client from our PPA [1]

  ubuntu@201307-13942:~$ sudo apt-get install canonical-certification-client
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   unity-control-center : Depends: libcheese-gtk23 (>= 3.4.0) but it is not 
going to be installed
  Depends: libcheese7 (>= 3.0.1) but it is not going to 
be installed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

  However, the version number for these two packages are bigger than the
  required version number:

  ubuntu@201307-13942:~$ dpkg -l | grep libcheese-gtk23
  ii  libcheese-gtk23:amd64 3.10.2-0ubuntu2 
amd64tool to take pictures and videos 
from your webcam - widgets
  ubuntu@201307-13942:~$ dpkg -l | grep libcheese7
  ii  libcheese7:amd64  3.10.2-0ubuntu2 
amd64tool to take pictures and videos 
from your webcam - base library
  ubuntu@201307-13942:~$

  I have no clue for how this happens. I thought it was a problem to our
  PPA (bug 1427524), but I think we're not alone [2]

  [1] http://ppa.launchpad.net/checkbox-dev/ppa/ubuntu/
  [2] http://askubuntu.com/questions/593369/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1428972/+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 1434986] Re: Not working network connection after boot

[Erwin van Diermen]

Above comment is partly true... after reboot it doesn't work anymore.

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

Title:
  Not working network connection after boot

Status in NetworkManager:
  Expired
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Directly after boot the network connections are not working. I am
  connected and have an IP address, but I cannot establish a connection
  with any Internet server.

  I have the impression it is related to thee DNS lookup, which waits
  forever for a result.

  Cycling the connection (disconnect->reconnect) seems to fix the
  problem for some time.

  I am reporting this against network-manager, but I am not sure if it is 
directly in network manager or if it is systemd related.
  With 14.10 everything worked perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 22 12:38:26 2015
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-01-30 (50 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static  metric 1024 
   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.26 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.29
  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-03-19 (3 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-02-16T00:14:50.662693
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Kabelnetzwerkverbindung 1  4a581685-6002-4401-a993-49aa649667eb  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   wlan0   wifi  connected  /org/freedesktop/NetworkManager/Devices/1  
4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   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/network-manager/+bug/1434986/+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 1627534] Re: Keeps resetting homepage to start.ubuntu-mate.org

[Luke Horwell]

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

It's a duplicate of https://bugs.launchpad.net/ubuntu/+source/ubuntu-
mate-settings/+bug/1605887

The configuration that causes Firefox to set the default home page
resides in the "ubuntu-mate-default-settings" package. You can install
the MATE Desktop on its own, but Ubuntu MATE desktop packages will
require this package too.

** This bug has been marked a duplicate of bug 1605887
   Ubuntu MATE Start page are overriding users' preferences.

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

Title:
  Keeps resetting homepage to start.ubuntu-mate.org

Status in firefox package in Ubuntu:
  Confirmed
Status in ubuntu-mate-settings package in Ubuntu:
  Confirmed

Bug description:
  Since the Xenial -> Yakkety beta upgrade, firefox resets its homepage
  to https://start.ubuntu-mate.org/ upon each start.

  I use the default Unity 7 desktop, no Mate whatsoever. (I might have
  started up Mate once or twice for a very short period, way before even
  upgrading to Xenial.)

  Happened both with firefox-49 package as shipped by Xenial, as well as
  firefox-48 that's currently in Yakkety beta (I purged and then
  reinstalled the package to get the one matching the distro, rather
  than the latest).

  No startup wrapper script or something like that should mess with my
  preferred homepage, let alone set it to something that is about a
  different desktop than the one I'm using.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: firefox 48.0+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-16-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  egmont 2339 F pulseaudio
  BuildID: 20160728202151
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Sun Sep 25 21:34:07 2016
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2012-05-30 (1579 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  IpRoute:
   default via 192.168.0.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.11  metric 
600
  MostRecentCrashID: bp-02582fc4-8633-4d4a-86cb-814af2140429
  PrefSources:
   /usr/lib/firefox/defaults/pref/all-ubuntumate.js
   prefs.js
  Profiles: Profile0 (Default) - LastVersion=48.0/20160728202151 (In use)
  RelatedPackageVersions:
   google-talkplugin 5.41.0.0-1
   icedtea-8-plugin  1.6.2-3ubuntu1
   gnome-shell   3.20.3-1ubuntu2
   rhythmbox-mozilla 3.4.1-1ubuntu1
   browser-plugin-evince 3.22.0-0ubuntu1
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  SubmittedCrashIDs: bp-02582fc4-8633-4d4a-86cb-814af2140429
  UpgradeStatus: Upgraded to yakkety on 2016-09-23 (2 days ago)
  dmi.bios.date: 12/14/2011
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 03QB
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 300E4Z/300E5Z/300E7Z
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr03QB:bd12/14/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E4Z/300E5Z/300E7Z:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn300E4Z/300E5Z/300E7Z:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 300E4Z/300E5Z/300E7Z
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1627534/+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 1673790] Re: bump LibreOffice to 5.3.1 on zesty and fix autpkgtest dependencies

[Jeremy Bicha]

Thanks! I have uploaded -0ubuntu2.

I have unsubscribed ubuntu-sponsor. Feel free to resubscribe if there is
anything else you need sponsored.

** Changed in: libreoffice (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  bump LibreOffice to 5.3.1 on zesty and fix autpkgtest dependencies

Status in libreoffice package in Ubuntu:
  Fix Committed
Status in libreoffice package in Debian:
  Unknown

Bug description:
  Please sponsor LibreOffice 1:5.3.1-0ubuntu1 and the corresponding
  -l10n package to zesty (use dget):

   
http://people.canonical.com/~bjoern/zesty/5.3.1/libreoffice-l10n_5.3.1-0ubuntu1_source.changes
   
http://people.canonical.com/~bjoern/zesty/5.3.1/libreoffice_5.3.1-0ubuntu1_source.changes

  The few changes vs. version 1:5.3.0~rc3-0ubuntu2 are best viewed on
  git:

   
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?h=ubuntu-zesty-5.3=f4b5ece6b1783202ed286e1f149ab60c3471f180
   
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?h=ubuntu-zesty-5.3=af8b1b6e9d4f00d1d6d31063e56bd4ca5d70b910
   
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?h=ubuntu-zesty-5.3=c525f97bab587d69ce56cf81f2edbfb7ae685cd7
   
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?h=ubuntu-zesty-5.3=af39ca70101b069b214b01a197aa48ffc59820b8

  A zesty build with all but the the last change is available in the
  LibreOffice ppas at:

   https://launchpad.net/~libreoffice/+archive/ubuntu/ppa
   https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-5-3

  Note the last change is not substancial as LibreOffice 5.3.1 rc2 is
  equal to 5.3.1 final in everything but the version.

  NB: The LibreOffice package has some generated files in ./debian (e.g.
  control) so there might be more changes (in generated files) in the
  debdiff than the above.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1673790/+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 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[Kyle Fazzari]

** Changed in: nextcloud-snap
   Importance: Unknown => High

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in Nextcloud:
  Unknown
Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in systemd source package in Yakkety:
  Triaged

Bug description:
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nextcloud-snap/+bug/1647031/+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 1673625] Re: 10-globally-managed-devices.conf contained in wrong package

[Brian Murray]

I upgraded from 16.04 to 16.10 recently and ran into an issue where
networking did not work until I created an empty file in
/run/NetworkManager/conf.d/10-globally-managed-devices.conf.

nplan was installed after the upgrade:

 $ apt-cache policy nplan
nplan:
  Installed: 0.12
  Candidate: 0.12
  Version table:
 *** 0.12 500
500 http://192.168.10.7/ubuntu yakkety/main amd64 Packages
100 /var/lib/dpkg/status

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

Title:
  10-globally-managed-devices.conf contained in wrong package

Status in network-manager package in Ubuntu:
  Confirmed
Status in nplan package in Ubuntu:
  Incomplete

Bug description:
  /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf is
  installed from network-manager but without nplan it has no benefit,
  and breaks networking until you override it.  Since the config is
  there to change how NetworkManager behaves in the presence of nplan,
  the configuration file itself should actually be contained in the
  nplan package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1673625/+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 1673625] Re: 10-globally-managed-devices.conf contained in wrong package

[Launchpad Bug Tracker]

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

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

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

Title:
  10-globally-managed-devices.conf contained in wrong package

Status in network-manager package in Ubuntu:
  Confirmed
Status in nplan package in Ubuntu:
  Incomplete

Bug description:
  /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf is
  installed from network-manager but without nplan it has no benefit,
  and breaks networking until you override it.  Since the config is
  there to change how NetworkManager behaves in the presence of nplan,
  the configuration file itself should actually be contained in the
  nplan package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1673625/+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 1673790] Re: bump LibreOffice to 5.3.1 on zesty and fix autpkgtest dependencies

[Björn Michaelsen]

So the 1:5.3.1-0ubuntu1 upload stuck on an autopkgtest fail on i386:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-
zesty/zesty/i386/libr/libreoffice/20170319_020124_b1ad7@/log.gz

the root cause was analysed and let to debian bug 858199:

 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858199

The fixes by Debian have been cherry-picked as:

 
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?id=dad502be3258ede5e21393a90a4682607f3369bd
 
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?id=0f96dce6f2a623d22ffc858b2edd7518c94b0903

because of
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?id=c525f97bab587d69ce56cf81f2edbfb7ae685cd7
we need an (re-)upload for libreoffice and for libreoffice-l10n this
time around. This should be fixed for the future with:

https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?id=485e71dffdaf408d17b51a8118d9bda303b914e3

So kindly requesting an upload of 1:5.3.1-0ubuntu2 for both libreoffice
and libreoffice-l10n as published here:

 
http://people.canonical.com/~bjoern/zesty/5.3.1/libreoffice-l10n_5.3.1-0ubuntu2_source.changes
 
http://people.canonical.com/~bjoern/zesty/5.3.1/libreoffice_5.3.1-0ubuntu2_source.changes

The diff should only be the three changes linked above (plus generated
changes).

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

** Changed in: libreoffice (Ubuntu)
   Status: Fix Committed => Confirmed

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

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

Title:
  bump LibreOffice to 5.3.1 on zesty and fix autpkgtest dependencies

Status in libreoffice package in Ubuntu:
  Confirmed
Status in libreoffice package in Debian:
  Unknown

Bug description:
  Please sponsor LibreOffice 1:5.3.1-0ubuntu1 and the corresponding
  -l10n package to zesty (use dget):

   
http://people.canonical.com/~bjoern/zesty/5.3.1/libreoffice-l10n_5.3.1-0ubuntu1_source.changes
   
http://people.canonical.com/~bjoern/zesty/5.3.1/libreoffice_5.3.1-0ubuntu1_source.changes

  The few changes vs. version 1:5.3.0~rc3-0ubuntu2 are best viewed on
  git:

   
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?h=ubuntu-zesty-5.3=f4b5ece6b1783202ed286e1f149ab60c3471f180
   
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?h=ubuntu-zesty-5.3=af8b1b6e9d4f00d1d6d31063e56bd4ca5d70b910
   
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?h=ubuntu-zesty-5.3=c525f97bab587d69ce56cf81f2edbfb7ae685cd7
   
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?h=ubuntu-zesty-5.3=af39ca70101b069b214b01a197aa48ffc59820b8

  A zesty build with all but the the last change is available in the
  LibreOffice ppas at:

   https://launchpad.net/~libreoffice/+archive/ubuntu/ppa
   https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-5-3

  Note the last change is not substancial as LibreOffice 5.3.1 rc2 is
  equal to 5.3.1 final in everything but the version.

  NB: The LibreOffice package has some generated files in ./debian (e.g.
  control) so there might be more changes (in generated files) in the
  debdiff than the above.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1673790/+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 1673625] Re: 10-globally-managed-devices.conf contained in wrong package

[Mathieu Trudel-Lapierre]

Don't get me wrong, the upgrade issue this causes has to get fixed.

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

Title:
  10-globally-managed-devices.conf contained in wrong package

Status in network-manager package in Ubuntu:
  Confirmed
Status in nplan package in Ubuntu:
  Incomplete

Bug description:
  /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf is
  installed from network-manager but without nplan it has no benefit,
  and breaks networking until you override it.  Since the config is
  there to change how NetworkManager behaves in the presence of nplan,
  the configuration file itself should actually be contained in the
  nplan package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1673625/+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 1589005] Re: After update DNS work unstable

[Alexander Skwar]

See https://gist.github.com/alexs77/85de4198016b5a6c6b40548b9aa71867 for
a better readable version.

And I also forgot to add, that I do NOT have the "normal" full blown
dnsmasq package installed; only dnsmasq-base.

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

Title:
  After update DNS work unstable

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Today I have updated network-manager from update repo and chrome have
  started get err_name_resolution_failed apt started get network errors.

  W: Failed to fetch 
http://by.archive.ubuntu.com/ubuntu/pool/main/n/network-manager/network-manager_1.1.93-0ubuntu4_amd64.deb
    Temporary failure resolving 'by.archive.ubuntu.com'

  I got same error when  previously update network-manager from ubuntu-
  proposed, so I think this packet with regression moved to normal
  update.

  workaround: download old network-manager_1.1.93-0ubuntu4_amd64.deb and 
install it using
  sudo dpkg -i network-manager_1.1.93-0ubuntu4_amd64.deb
  and lock version 
  echo "network-manager hold" | sudo dpkg --set-selections

  "apt update" going to show network-manager as upgradable but "apt
  upgrage" going to ignore it

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun  4 01:39:17 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-01 (33 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.100.1 dev enp8s0  proto static  metric 100
   169.254.0.0/16 dev enp8s0  scope link  metric 1000
   192.168.100.0/24 dev enp8s0  proto kernel  scope link  src 192.168.100.9  
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   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
   Проводное соединение 1  34318290-4c71-4b1f-9154-d0f134b91440  802-3-ethernet 
  1464993435  Sat 04 Jun 2016 01:37:15 MSK  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  yes enp8s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/0
   HUAWEI-KpW2 1   8087b7e0-51dc-43c4-8928-4d03c85a5762  
802-11-wireless  1464546384  Sun 29 May 2016 21:26:24 MSK  yes  0   
  no/org/freedesktop/NetworkManager/Settings/1  no  --  
-- --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   enp8s0  ethernet  connected/org/freedesktop/NetworkManager/Devices/1  
Проводное соединение 1  34318290-4c71-4b1f-9154-d0f134b91440  
/org/freedesktop/NetworkManager/ActiveConnection/0
   wlp9s0  wifi  unavailable  /org/freedesktop/NetworkManager/Devices/0  -- 
 ----
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
 ----
  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/1589005/+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 1589005] Re: After update DNS work unstable

[Alexander Skwar]

I also seem to experience the same (or similar) issue. When I connect to
my companies Cisco ASA VPN using OpenConnect (in NetworkManager), it
seems that with network-manager after v1.2.2, the previously configured
DNS servers aren't overwritten with what VPN sends. Instead, those VPN
servers get appended to the list.

So, at first, before I connect to VPN, I only have one DNS server configured: 
192.168.42.129
Next, I connect to the VPN.

To see the effective list of DNS servers, I created the file
/etc/NetworkManager/dnsmasq.d/dnsmasq.conf, containing:

log-queries=extra
log-async=7

After a reboot, dnsmasq uses this settings. Now, when a USR1 signal is
send to dnsmasq, it'll print information to syslog.


With v1.2.2 (network-manager_1.2.2-0ubuntu0.16.04.4_amd64.deb):
$ tail -F /var/log/syslog &
# => Connect to Cisco VPN with OpenConnect
$ sudo pkill -USR1 dnsmasq

Mar 20 15:52:40 dns-issue-test dnsmasq[992]: time 1490021560
Mar 20 15:52:40 dns-issue-test dnsmasq[992]: cache size 0, 0/0 cache insertions 
re-used unexpired cache entries.
Mar 20 15:52:40 dns-issue-test dnsmasq[992]: queries forwarded 14, queries 
answered locally 1
Mar 20 15:52:40 dns-issue-test dnsmasq[992]: queries for authoritative zones 0
Mar 20 15:52:40 dns-issue-test dnsmasq[992]: server 192.168.251.6#53: queries 
sent 1, retried or failed 0
Mar 20 15:52:40 dns-issue-test dnsmasq[992]: server 192.168.251.7#53: queries 
sent 7, retried or failed 0
Mar 20 15:52:40 dns-issue-test dnsmasq[992]: Host   
  AddressFlags  Expires


With v1.2.4 (network-manager_1.2.4-0ubuntu0.16.04.1_amd64.deb), I get
this:

$ sudo dpkg -i Downloads/network-manager_1.2.4-0ubuntu0.16.04.1_amd64.deb
$ sudo reboot

...

$ tail -F /var/log/syslog &
# => Connect to Cisco VPN with OpenConnect
$ sudo pkill -USR1 dnsmasq

Mar 20 15:56:42 dns-issue-test dnsmasq[976]: time 1490021802
Mar 20 15:56:42 dns-issue-test dnsmasq[976]: cache size 0, 0/0 cache insertions 
re-used unexpired cache entries.
Mar 20 15:56:42 dns-issue-test dnsmasq[976]: queries forwarded 14, queries 
answered locally 1
Mar 20 15:56:42 dns-issue-test dnsmasq[976]: queries for authoritative zones 0
Mar 20 15:56:42 dns-issue-test dnsmasq[976]: server 192.168.42.129#53: queries 
sent 5, retried or failed 0
Mar 20 15:56:42 dns-issue-test dnsmasq[976]: server 192.168.251.6#53: queries 
sent 0, retried or failed 0
Mar 20 15:56:42 dns-issue-test dnsmasq[976]: server 192.168.251.7#53: queries 
sent 0, retried or failed 0
Mar 20 15:56:42 dns-issue-test dnsmasq[976]: Host   
  AddressFlags  Expires


So, as can be seen, the two additional DNS servers 192.168.251.6 and 
192.168.251.7 just got added to the list of effective DNS servers. 
192.168.42.129 is still in the list.

With v1.2.2, the old DNS server (=> 192.168.42.129) was removed.

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

Title:
  After update DNS work unstable

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Today I have updated network-manager from update repo and chrome have
  started get err_name_resolution_failed apt started get network errors.

  W: Failed to fetch 
http://by.archive.ubuntu.com/ubuntu/pool/main/n/network-manager/network-manager_1.1.93-0ubuntu4_amd64.deb
    Temporary failure resolving 'by.archive.ubuntu.com'

  I got same error when  previously update network-manager from ubuntu-
  proposed, so I think this packet with regression moved to normal
  update.

  workaround: download old network-manager_1.1.93-0ubuntu4_amd64.deb and 
install it using
  sudo dpkg -i network-manager_1.1.93-0ubuntu4_amd64.deb
  and lock version 
  echo "network-manager hold" | sudo dpkg --set-selections

  "apt update" going to show network-manager as upgradable but "apt
  upgrage" going to ignore it

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun  4 01:39:17 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-01 (33 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.100.1 dev enp8s0  proto static  metric 100
   169.254.0.0/16 dev enp8s0  scope link  metric 1000
   192.168.100.0/24 dev enp8s0  proto kernel  scope link  src 192.168.100.9  
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:

[Desktop-packages] [Bug 1671079] Re: Firefox crashes instantly after update from 51.0.1 to 52 on Ubuntu 16.04

[Launchpad Bug Tracker]

This bug was fixed in the package firefox -
52.0.1+build2-0ubuntu0.12.04.1

---
firefox (52.0.1+build2-0ubuntu0.12.04.1) precise-security; urgency=medium

  * New upstream stable release (52.0.1build2)
- Fix LP: #1671079 - Don't crash if LOGNAME is not set in the environment

 -- Chris Coulson   Wed, 08 Mar 2017
16:00:56 +

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

** Changed in: firefox (Ubuntu)
   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/1671079

Title:
  Firefox crashes instantly after update from 51.0.1 to 52 on Ubuntu
  16.04

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  After the update from

  firefox:amd64 51.0.1+build2-0ubuntu0.16.04.2 to
  52.0+build2-0ubuntu0.16.04.1

  on Ubuntu 16.04 LTS Firefox doesn't start anymore but shows the crash
  report dialog instead. On the terminal we get

  ExceptionHandler::GenerateDump cloned child 8129
  ExceptionHandler::SendContinueSignalToChild sent continue signal to child
  ExceptionHandler::WaitForContinueSignal waiting for continue signal...
  Speicherzugriffsfehler (Speicherabzug geschrieben)

  This is mozilla's crash report:
  
https://crash-stats.mozilla.com/report/index/50b93881-7cf2-493d-a495-fc7b42170308


  
  This happens to all users and also after removing ~/.mozilla

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1671079/+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 1671079] Re: Firefox crashes instantly after update from 51.0.1 to 52 on Ubuntu 16.04

[Launchpad Bug Tracker]

This bug was fixed in the package firefox -
52.0.1+build2-0ubuntu0.16.10.1

---
firefox (52.0.1+build2-0ubuntu0.16.10.1) yakkety-security; urgency=medium

  * New upstream stable release (52.0.1build2)
- Fix LP: #1671079 - Don't crash if LOGNAME is not set in the environment

 -- Chris Coulson   Wed, 08 Mar 2017
15:35:53 +

** Changed in: firefox (Ubuntu)
   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/1671079

Title:
  Firefox crashes instantly after update from 51.0.1 to 52 on Ubuntu
  16.04

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  After the update from

  firefox:amd64 51.0.1+build2-0ubuntu0.16.04.2 to
  52.0+build2-0ubuntu0.16.04.1

  on Ubuntu 16.04 LTS Firefox doesn't start anymore but shows the crash
  report dialog instead. On the terminal we get

  ExceptionHandler::GenerateDump cloned child 8129
  ExceptionHandler::SendContinueSignalToChild sent continue signal to child
  ExceptionHandler::WaitForContinueSignal waiting for continue signal...
  Speicherzugriffsfehler (Speicherabzug geschrieben)

  This is mozilla's crash report:
  
https://crash-stats.mozilla.com/report/index/50b93881-7cf2-493d-a495-fc7b42170308


  
  This happens to all users and also after removing ~/.mozilla

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1671079/+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 1672033] Re: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME)

[Igor]

xrandr output in rootless session:


igor:~% ps aux | grep Xorg
igor  3779  3.2  0.0 199348 51332 tty3 S+   15:49   0:00 
/usr/lib/xorg/Xorg vt3 -displayfd 3 -auth /run/user/1000/gdm/Xauthority 
-background none -noreset -keeptty -verbose 3


igor:~% xrandr -q
Screen 0: minimum 8 x 8, current 1920 x 1200, maximum 32767 x 32767
DVI-D-0 connected primary 1920x1200+0+0 (normal left inverted right x axis y 
axis) 518mm x 324mm
   1920x1200 59.95*+
   1920x1080 60.00  
   1680x1050 59.95  
   1600x1200 60.00  
   1280x1024 60.02  
   1280x960  60.00  
   1024x768  60.00  
   800x600   60.32  
   640x480   59.94  
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)
DP-4 disconnected (normal left inverted right x axis y axis)
DP-5 disconnected (normal left inverted right x axis y axis)

lightdm works, because it starts Xorg as root for itself, which causes
monitor initialization and consequently later started rootless session
work fine.

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

Title:
  Xorg does not detect displays in rootless mode on nvidia proprietary
  drivers (GNOME)

Status in NVIDIA Drivers Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  There are two bug reports in LP: #1559576, LP: #1632322 and also LP:
  #164, where GDM does not start on proprietary nvidia drivers. As
  it turned out, the reason for that was Xorg starting in rootless mode
  and apparently not initializing everything properly, which was causing
  gnome-shell/libmutter to crash.

  Installing xserver-xorg-legacy did partially fix those issues.

  Enabling modesetting for nvidia driver however still causes the
  problem.

  
  Here are some parts from log:
  Xorg startup:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (--) Log file 
renamed from "/var/lib/gdm3/.local/share/xorg/Xorg.pid-2027.log" to 
"/var/lib/gdm3/.local/share/xorg/Xorg.0.log"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X.Org X Server 
1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Release Date: 
2016-07-19
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X Protocol Version 
11, Revision 0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Build Operating 
System: Linux 4.4.0-53-generic x86_64 Ubuntu

  glx loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"glx"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/libglx.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module glx: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Server Extension
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA GLX 
Module  375.39  Tue Jan 31 19:37:12 PST 2017

  nvidia loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"nvidia"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module nvidia: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver

  modesetting loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"modesetting"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/xorg/modules/drivers/modesetting_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module 
modesetting: vendor="X.Org Foundation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 1.18.4, module version = 1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: ABI class: 
X.Org Video Driver, version 20.0

  
  gnome-shell fails to run:
  Mär 11 00:43:20 arvlin kernel: gnome-shell[2067]: segfault at 28 ip 
7fedba8da7c4 sp 7ffd2fb5f5a0 error 4 in 
libmutter-0.so.0.0.0[7fedba893000+12f000]

  xorg stops:
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin 

[Desktop-packages] [Bug 1671079] Re: Firefox crashes instantly after update from 51.0.1 to 52 on Ubuntu 16.04

[Launchpad Bug Tracker]

This bug was fixed in the package firefox -
52.0.1+build2-0ubuntu0.14.04.1

---
firefox (52.0.1+build2-0ubuntu0.14.04.1) trusty-security; urgency=medium

  * New upstream stable release (52.0.1build2)
- Fix LP: #1671079 - Don't crash if LOGNAME is not set in the environment

 -- Chris Coulson   Wed, 08 Mar 2017
15:50:13 +

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

Title:
  Firefox crashes instantly after update from 51.0.1 to 52 on Ubuntu
  16.04

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  After the update from

  firefox:amd64 51.0.1+build2-0ubuntu0.16.04.2 to
  52.0+build2-0ubuntu0.16.04.1

  on Ubuntu 16.04 LTS Firefox doesn't start anymore but shows the crash
  report dialog instead. On the terminal we get

  ExceptionHandler::GenerateDump cloned child 8129
  ExceptionHandler::SendContinueSignalToChild sent continue signal to child
  ExceptionHandler::WaitForContinueSignal waiting for continue signal...
  Speicherzugriffsfehler (Speicherabzug geschrieben)

  This is mozilla's crash report:
  
https://crash-stats.mozilla.com/report/index/50b93881-7cf2-493d-a495-fc7b42170308


  
  This happens to all users and also after removing ~/.mozilla

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1671079/+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 1672033] Re: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME)

[Igor]

I don't have hybrid graphics. It's a normal desktop.

Yes, lightdm is working with KMS enabled and it is possible to log in
into gnome-shell Xorg session.

But lightdm is started as root:
root 10867  0.0  0.0 361724  6620 ?SLsl 15:41   0:00 
/usr/sbin/lightdm

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

Title:
  Xorg does not detect displays in rootless mode on nvidia proprietary
  drivers (GNOME)

Status in NVIDIA Drivers Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  There are two bug reports in LP: #1559576, LP: #1632322 and also LP:
  #164, where GDM does not start on proprietary nvidia drivers. As
  it turned out, the reason for that was Xorg starting in rootless mode
  and apparently not initializing everything properly, which was causing
  gnome-shell/libmutter to crash.

  Installing xserver-xorg-legacy did partially fix those issues.

  Enabling modesetting for nvidia driver however still causes the
  problem.

  
  Here are some parts from log:
  Xorg startup:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (--) Log file 
renamed from "/var/lib/gdm3/.local/share/xorg/Xorg.pid-2027.log" to 
"/var/lib/gdm3/.local/share/xorg/Xorg.0.log"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X.Org X Server 
1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Release Date: 
2016-07-19
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X Protocol Version 
11, Revision 0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Build Operating 
System: Linux 4.4.0-53-generic x86_64 Ubuntu

  glx loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"glx"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/libglx.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module glx: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Server Extension
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA GLX 
Module  375.39  Tue Jan 31 19:37:12 PST 2017

  nvidia loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"nvidia"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module nvidia: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver

  modesetting loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"modesetting"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/xorg/modules/drivers/modesetting_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module 
modesetting: vendor="X.Org Foundation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 1.18.4, module version = 1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: ABI class: 
X.Org Video Driver, version 20.0

  
  gnome-shell fails to run:
  Mär 11 00:43:20 arvlin kernel: gnome-shell[2067]: segfault at 28 ip 
7fedba8da7c4 sp 7ffd2fb5f5a0 error 4 in 
libmutter-0.so.0.0.0[7fedba893000+12f000]

  xorg stops:
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:66
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:67
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:64
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:65
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA(GPU-0): 
Deleting GPU-0
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Server 
terminated successfully (0). Closing log file.
  Mär 11 00:43:21 arvlin gdm-launch-environment][2009]: 
pam_unix(gdm-launch-environment:session): session 

[Desktop-packages] [Bug 1674367] [NEW] /usr/bin/evolution:5:doGetScreenResources:XRRGetScreenResources:update_outputs:_cogl_xlib_renderer_connect:_cogl_winsys_renderer_connect

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
evolution.  This problem was most recently seen with package version 
3.22.3-0ubuntu0.1, the problem page at 
https://errors.ubuntu.com/problem/d8db569aef3ae061f3aa8c6e46efa61f5d7fe5e5 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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


** Tags: xenial yakkety

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

Title:
  
/usr/bin/evolution:5:doGetScreenResources:XRRGetScreenResources:update_outputs:_cogl_xlib_renderer_connect:_cogl_winsys_renderer_connect

Status in evolution package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
evolution.  This problem was most recently seen with package version 
3.22.3-0ubuntu0.1, the problem page at 
https://errors.ubuntu.com/problem/d8db569aef3ae061f3aa8c6e46efa61f5d7fe5e5 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1674367/+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 1118903] Re: [enhancement] Mir lacks a software rendering backend (and doesn't work in virtual machines)

[kevin gunn]

if so many caveats, then lets not target u8c-1

** Changed in: canonical-devices-system-image
Milestone: u8c-1 => u8c-2

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

Title:
  [enhancement] Mir lacks a software rendering backend (and doesn't work
  in virtual machines)

Status in Canonical System Image:
  Triaged
Status in Mir:
  Triaged
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Triaged

Bug description:
  As always, it's a critical requirement for Ubuntu to be able to render
  the same thing on any machine (metal or virtual), regardless of the
  availability of hardware acceleration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1118903/+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 1671799] Re: FFe: xserver 1.19.3

[Timo Aaltonen]

** Description changed:

  xserver 1.19 has been out for quite some time now. Debian Stretch will
  release with it, and xmir has been recently ported so we can push 1.19
  to zesty now. It's currently being staged on a ppa:
  
  https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging
  
  The main features of this release are:
  - PRIME synchronization support, should reduce tearing on hybrid setups
  - GLAMOR (2D accel over OpenGL) improvements
  - threaded input
  
  This bugreport is also for gathering testing feedback.
  
  Tested to be working fine on:
  - Intel Kabylake
  - Intel Broadwell
  - Intel+NVIDIA hybrid (Skylake + 930MX, with OSS and blob drivers)
  - Intel+NVIDIA hybrid (Haswell + NVIDIA GK107M [GeForce GT 755M])
  - Intel+NVIDIA hybrid (Ivybridge + NVIDIA GK107M [GeForce GT 660M])
  - Radeon SI (radeon & amdgpu drivers)
+ - qemu (QXL)

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

Title:
  FFe: xserver 1.19.3

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  xserver 1.19 has been out for quite some time now. Debian Stretch will
  release with it, and xmir has been recently ported so we can push 1.19
  to zesty now. It's currently being staged on a ppa:

  https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging

  The main features of this release are:
  - PRIME synchronization support, should reduce tearing on hybrid setups
  - GLAMOR (2D accel over OpenGL) improvements
  - threaded input

  This bugreport is also for gathering testing feedback.

  Tested to be working fine on:
  - Intel Kabylake
  - Intel Broadwell
  - Intel+NVIDIA hybrid (Skylake + 930MX, with OSS and blob drivers)
  - Intel+NVIDIA hybrid (Haswell + NVIDIA GK107M [GeForce GT 755M])
  - Intel+NVIDIA hybrid (Ivybridge + NVIDIA GK107M [GeForce GT 660M])
  - Radeon SI (radeon & amdgpu drivers)
  - qemu (QXL)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799/+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 1528735] Missing required logs.

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1528735

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

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

Title:
  Suspend fails every second time on some laptops in UEFI mode

Status in kernel-package package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of Xubuntu 14.04.3, replacing existing OEM Windows 10.
  Install detected UEFI, and installed in UEFI mode. (I have attempted
  to change to legacy boot, and got it to a state where it was booting
  without /sys/firmware/efi/ being present, but behaviour persisted.)

  Suspending the laptop, whether by closing the lid, choosing the
  suspend option from the menu, or directly typing "sudo pm-suspend"
  works perfectly well... once.

  The second attempt to suspend, whether immediately or hours later,
  suspends the laptop (I can see the screen turn off, and hear the disk
  and fans stop, but a moment later the screen shows bright yellow
  console text declaring "Warning!!! Boot script table modified!!!
  Please contact your vendor.", and then it hard reboots.

  This appears to be a weird interaction between suspend and UEFI
  protection, but others have reported that they have had working
  suspend when installed alone (and presumably in legacy from the
  start), but this behaviour appeared when reinstalled as dual-boot
  (when presumably UEFI would have had to be on).
  (http://askubuntu.com/questions/675683/suspend-does-not-work-more-
  than-once-after-reboot-ubuntu-15-04-dual-boot/712232 and earlier
  http://askubuntu.com/questions/651481/boot-script-table-modified-
  please-contact-vendor, from different people.)

  Beyond the investigations I have done, I know next to nothing about
  UEFI, or how Suspend might be interacting with it. Much less why it
  appears to work perfectly exactly once.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.1
  ProcVersionSignature: Ubuntu 4.2.0-22.27~14.04.1-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Dec 23 13:27:11 2015
  InstallationDate: Installed on 2015-12-19 (3 days ago)
  InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1528735/+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 1528735] Re: Suspend fails every second time on some laptops in UEFI mode

[ChristianEhrhardt]

So far the only kernel tag with that fix is v4.11-rc1, I haven't seen it being 
sent to stable trees.
Neither were there other platforms added - I see the G70 and S435 in the bug 
here.
You might want to follow the kernel bug link and mention your platoform showing 
the issue there as recommended by Carloslp in comment #23.

Adding a task for the kernel Team to consider a fix.

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Suspend fails every second time on some laptops in UEFI mode

Status in kernel-package package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of Xubuntu 14.04.3, replacing existing OEM Windows 10.
  Install detected UEFI, and installed in UEFI mode. (I have attempted
  to change to legacy boot, and got it to a state where it was booting
  without /sys/firmware/efi/ being present, but behaviour persisted.)

  Suspending the laptop, whether by closing the lid, choosing the
  suspend option from the menu, or directly typing "sudo pm-suspend"
  works perfectly well... once.

  The second attempt to suspend, whether immediately or hours later,
  suspends the laptop (I can see the screen turn off, and hear the disk
  and fans stop, but a moment later the screen shows bright yellow
  console text declaring "Warning!!! Boot script table modified!!!
  Please contact your vendor.", and then it hard reboots.

  This appears to be a weird interaction between suspend and UEFI
  protection, but others have reported that they have had working
  suspend when installed alone (and presumably in legacy from the
  start), but this behaviour appeared when reinstalled as dual-boot
  (when presumably UEFI would have had to be on).
  (http://askubuntu.com/questions/675683/suspend-does-not-work-more-
  than-once-after-reboot-ubuntu-15-04-dual-boot/712232 and earlier
  http://askubuntu.com/questions/651481/boot-script-table-modified-
  please-contact-vendor, from different people.)

  Beyond the investigations I have done, I know next to nothing about
  UEFI, or how Suspend might be interacting with it. Much less why it
  appears to work perfectly exactly once.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.1
  ProcVersionSignature: Ubuntu 4.2.0-22.27~14.04.1-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Dec 23 13:27:11 2015
  InstallationDate: Installed on 2015-12-19 (3 days ago)
  InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1528735/+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 1658921] Re: NetworkManager does not manage wired connection

[Raphaël Jakse]

Bug #1638842 has been marked as a duplicate of this one, and also has
been marked Won't Fix (before this bug was reported). So if we want the
current behavior to be changed, we need to discuss.

Reason of the current behavior is given in Comment 7 of Bug #1638842:
“On desktop images we want NM to manage everything, thus the installer
creates /etc/NetworkManager/conf.d/10-globally-managed-devices.conf. But
on a server, container, or similar environment we do NOT want NM to
suddenly take over existing connections from netplan, networkd, or
ifupdown -- there it should be restricted to wifi and 3G.”

I agree with the idea and I can imagine that even if I cannot think of a
case where NM is installed in a container / on a server without wanting
it to manage connections, the current behavior works around a real
problem that as been encountered and that chroot installation of Ubuntu
Desktops might have been forgotten in the process.

Now, installing Ubuntu using chroot is convenient and the easiest method
is some cases, and as we can see in the comments here, people really do
it so this should work as expected. In this setting, the current
behavior is confusing. By default, nothing shows that NM is configured
not to manage wired and Bluetooth connection. I lost almost a day
because of this. It should at least be explicit in the configuration and
in the logs. And NM changing its behavior because an empty configuration
file exists at /etc/NetworkManager/conf.d/10-globally-managed-
devices.conf seems weird to me.

I agree that solving the initial problem is probably important, but I
think that breaking things so badly for people installing Ubuntu using
chroot is wrong and that the installation of Ubuntu should be a process
that remains simple and intuitive. Making the Ubuntu installer create
/etc/NetworkManager/conf.d/10-globally-managed-devices.conf and make NM
work as expected when this file exists looks like a hack to me, and a
fragile behavior.

A better solution might be to make network-manager manage connections as
expected when *-desktop packages are installed. But it is not sufficient
as some people don't install these packages in their desktop setup to
avoid installing things they don't use.

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

Title:
  NetworkManager does not manage wired connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager does not manage my wired eth0 connection, no matter how
  I set /etc/network/interfaces or
  /etc/NetworkManager/NetworkManager.conf

  Using ubuntu 16.04, /etc/network/interfaces only managed lo, and
  [ifupdown] section of NetworkManager.conf had set managed=false.

  With these same settings, after upgrading to ubuntu 16.10, eth0
  appears as unmanaged in nm-applet.

  If I modify /etc/network/interfaces and add

  auto eth0
  iface eth0 inet dhcp

  And set managed=true in NetworkManager.conf [ifupdown] section, eth0
  is still unmanaged despite it does get an IP from DHCP server.

  This is happening in my five computers (two laptops and three
  desktops).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1658921/+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 1598300] Re: CUPS web interface stops responding after a while

[Patrick Domack]

The -proposed 2.1.3-4buntu0.2 fixes this issue for me.

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

Title:
  CUPS web interface stops responding after a while

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Committed

Bug description:
  after 6 minutes or so, cups is not responding.
  it do not produce error on the log, just stop working, worse, it exit with 0

  
⌌—⌍
  |root@cupsmachine :~# systemctl status cups   
|
  |● cups.service - CUPS Scheduler  
|
  |   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)|
  |   Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago 
|
  | Docs: man:cupsd(8)  
|
  |  Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, 
status=0/SUCCESS)|
  | Main PID: 28686 (code=exited, status=0/SUCCESS) 
|
  | 
|
  |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler.   
|
  
⌎—⌏

  I got to launch it again, so I have finish with a cron job like
  */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && 
systemctl start cups

  but it is a dirty solution. I have no idea of what make it stop.
  NB: I have seen problems related to apparmor, this machine has no apparmor 
package.

  [Impact]

  If you want to use the CUPS web interface in Xenial and therefore set
  "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown
  when it is idle and then an attempt to access http://localhost:631/
  via a web browser fails. People get confused as other access to CUPS

  [Testcase]

  Take a CUPS setup on Xenial with no shared print queues and CUPS only
  listening on the domain socket. Activate the web interface via

  cupsctl WebInterface=Yes

  Now you are able to access the web interface via
  http://localhost:631/. Wait for some minutes without accessing CUPS
  until the CUPS daemon shuts down automatically. Try to open the web
  interface again and it will not work.

  With the fixed CUPS package CUPS will not auto-shutdown when the web
  interface is activated.

  [Regression Potential]

  Low, as we are removing a simple distro patch to get back to the
  original, upstream behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+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 1671799] Re: FFe: xserver 1.19.3

[Timo Aaltonen]

-libinput has been the default since 16.10 where it replaced -evdev
(-input-all pulls -libinput), so I don't consider this a blocker, since
it doesn't seem to be a widespread issue (I can't reproduce it with a
mouse either). Feel free to file a bug against -libinput, upstream too
if you can.

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

Title:
  FFe: xserver 1.19.3

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  xserver 1.19 has been out for quite some time now. Debian Stretch will
  release with it, and xmir has been recently ported so we can push 1.19
  to zesty now. It's currently being staged on a ppa:

  https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging

  The main features of this release are:
  - PRIME synchronization support, should reduce tearing on hybrid setups
  - GLAMOR (2D accel over OpenGL) improvements
  - threaded input

  This bugreport is also for gathering testing feedback.

  Tested to be working fine on:
  - Intel Kabylake
  - Intel Broadwell
  - Intel+NVIDIA hybrid (Skylake + 930MX, with OSS and blob drivers)
  - Intel+NVIDIA hybrid (Haswell + NVIDIA GK107M [GeForce GT 755M])
  - Intel+NVIDIA hybrid (Ivybridge + NVIDIA GK107M [GeForce GT 660M])
  - Radeon SI (radeon & amdgpu drivers)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799/+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 1393578] Re: Subpixel order not included in Mir display information

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2609

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

Title:
  Subpixel order not included in Mir display information

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  Triaged
Status in qtubuntu package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Just capturing something mentioned by Trevinho on IRC this morning.
  MirDisplayOutput does not include subpixel ordering, it could and
  should though. The information is exposed on the drm side
  (drmModeSubPixel). Marking as wishlist in absence of other
  information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1393578/+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 1674304] Re: PRIME synchronization not working with xserver-1.19.x

[Doug McMahon]

$ inxi -G
Graphics:  Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller
   Card-2: NVIDIA GK107M [GeForce GT 755M]
   Display Server: X.Org 1.19.3 drivers: modesetting,nvidia
   Resolution: 1920x1080@59.91hz
   GLX Renderer: GeForce GT 755M/PCIe/SSE2
   GLX Version: 4.5.0 NVIDIA 375.39

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

Title:
  PRIME synchronization not working with xserver-1.19.x

Status in nvidia-prime package in Ubuntu:
  New

Bug description:
  xserver-1.19.x is being proposed for 17.04, currently available in test ppa
  https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging
  FFe - https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799

  On 2 separate Optimus laptops there is no sign of it actually working, 
tearing while using nvidia drivers (375.x) is rampart.
  Testing with both current  4.10.0-13 & previous 4.9.0-11 kernels.

  Shows this in kern.log so support is enabled

  Mar 19 08:18:47 doug-Lenovo-IdeaPad-Y510P kernel: [1.746443] [drm] 
Supports vblank timestamp caching Rev 2 (21.10.2013).
  Mar 19 08:18:47 doug-Lenovo-IdeaPad-Y510P kernel: [1.746444] [drm] Driver 
supports precise vblank timestamp

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: nvidia-prime 0.8.4
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Mar 20 07:53:12 2017
  InstallationDate: Installed on 2017-03-15 (4 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170311)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1674304/+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 1673491] Re: [Zesty] libnl3 Segmentation fault in sriov environments

[ChristianEhrhardt]

Dimitri was not available, but I found another sponsor.
Thanks APW!

@Talat if you could finally post if the version that is released is good
as well that would be nice.

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

Title:
  [Zesty] libnl3 Segmentation fault in sriov environments

Status in libnl3 package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  New

Bug description:
  in Ubuntu 17.04 we can't open a virt-manager, we see sefault

  This issue happen when we update from kernel 4.10.0-9-generic to
  4.10.0-11-generic

  root@:~# /usr/sbin/libvirtd
  Segmentation fault (core dumped)   

  root@:~# gdb /usr/sbin/libvirtd ./core 
  GNU gdb (Ubuntu 7.12.50.20170314-0ubuntu1) 7.12.50.20170314-git
  Copyright (C) 2017 Free Software Foundation, Inc.  
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.   
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"   
  and "show warranty" for details. 
  This GDB was configured as "x86_64-linux-gnu".   
  Type "show configuration" for configuration details. 
  For bug reporting instructions, please see:  
  . 
  Find the GDB manual and other documentation resources online at: 
  .
  For help, type "help".   
  Type "apropos word" to search for commands related to "word"...  
  Reading symbols from /usr/sbin/libvirtd...(no debugging symbols found)...done.
  [New LWP 4232]
  [New LWP 4216]
  [New LWP 4219]
  [New LWP 4218]
  [New LWP 4231]
  [New LWP 4215]
  [New LWP 4220]
  [New LWP 4224]
  [New LWP 4221]
  [New LWP 4223]
  [New LWP 4222]
  [New LWP 4217]
  [New LWP 4225]
  [New LWP 4227]
  [New LWP 4230]
  [New LWP 4229]
  [New LWP 4228]
  [Thread debugging using libthread_db enabled] 
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/usr/sbin/libvirtd'.   
  Program terminated with signal SIGSEGV, Segmentation fault.   
  #0  0x7f97fa93367f in rtnl_link_sriov_parse_vflist () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200
  [Current thread is 1 (Thread 0x7f97dff94700 (LWP 4232))]  
   
  (gdb) where   
   
  #0  0x7f97fa93367f in rtnl_link_sriov_parse_vflist () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200
  #1  0x7f97fa927fad in ?? () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200  
  #2  0x7f980bfb76c3 in nl_cache_parse () from 
/lib/x86_64-linux-gnu/libnl-3.so.200
  #3  0x7f980bfb770b in ?? () from /lib/x86_64-linux-gnu/libnl-3.so.200 
   
  #4  0x7f980bfbdc1c in nl_recvmsgs_report () from 
/lib/x86_64-linux-gnu/libnl-3.so.200
  #5  0x7f980bfbe049 in nl_recvmsgs () from 
/lib/x86_64-linux-gnu/libnl-3.so.200   
  #6  0x7f980bfb6aab in ?? () from /lib/x86_64-linux-gnu/libnl-3.so.200 
   
  #7  0x7f980bfb763d in nl_cache_pickup () from 
/lib/x86_64-linux-gnu/libnl-3.so.200   
  #8  0x7f980bfb7871 in nl_cache_refill () from 

[Desktop-packages] [Bug 1674304] [NEW] PRIME synchronization not working with xserver-1.19.x

[Doug McMahon]

Public bug reported:

xserver-1.19.x is being proposed for 17.04, currently available in test ppa
https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging
FFe - https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799

On 2 separate Optimus laptops there is no sign of it actually working, tearing 
while using nvidia drivers (375.x) is rampart.
Testing with both current  4.10.0-13 & previous 4.9.0-11 kernels.

Shows this in kern.log so support is enabled

Mar 19 08:18:47 doug-Lenovo-IdeaPad-Y510P kernel: [1.746443] [drm] Supports 
vblank timestamp caching Rev 2 (21.10.2013).
Mar 19 08:18:47 doug-Lenovo-IdeaPad-Y510P kernel: [1.746444] [drm] Driver 
supports precise vblank timestamp

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: nvidia-prime 0.8.4
ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
Uname: Linux 4.10.0-13-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Mon Mar 20 07:53:12 2017
InstallationDate: Installed on 2017-03-15 (4 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170311)
SourcePackage: nvidia-prime
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-prime (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages zesty

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

Title:
  PRIME synchronization not working with xserver-1.19.x

Status in nvidia-prime package in Ubuntu:
  New

Bug description:
  xserver-1.19.x is being proposed for 17.04, currently available in test ppa
  https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging
  FFe - https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799

  On 2 separate Optimus laptops there is no sign of it actually working, 
tearing while using nvidia drivers (375.x) is rampart.
  Testing with both current  4.10.0-13 & previous 4.9.0-11 kernels.

  Shows this in kern.log so support is enabled

  Mar 19 08:18:47 doug-Lenovo-IdeaPad-Y510P kernel: [1.746443] [drm] 
Supports vblank timestamp caching Rev 2 (21.10.2013).
  Mar 19 08:18:47 doug-Lenovo-IdeaPad-Y510P kernel: [1.746444] [drm] Driver 
supports precise vblank timestamp

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: nvidia-prime 0.8.4
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Mar 20 07:53:12 2017
  InstallationDate: Installed on 2017-03-15 (4 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170311)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1674304/+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 1658921] Re: NetworkManager does not manage wired connection

[gerardo]

Same problem after an upgrade from 16.04 to 16.10 via "do-release-
upgrade". However in my case the issue occurred not for a Wired
connection, but for a Mobile Broadband connection (device ttyUSB2 of
type gsm over interface ppp0). Comment 7 fixed the issue.

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

Title:
  NetworkManager does not manage wired connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager does not manage my wired eth0 connection, no matter how
  I set /etc/network/interfaces or
  /etc/NetworkManager/NetworkManager.conf

  Using ubuntu 16.04, /etc/network/interfaces only managed lo, and
  [ifupdown] section of NetworkManager.conf had set managed=false.

  With these same settings, after upgrading to ubuntu 16.10, eth0
  appears as unmanaged in nm-applet.

  If I modify /etc/network/interfaces and add

  auto eth0
  iface eth0 inet dhcp

  And set managed=true in NetworkManager.conf [ifupdown] section, eth0
  is still unmanaged despite it does get an IP from DHCP server.

  This is happening in my five computers (two laptops and three
  desktops).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1658921/+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 372132] Re: "Create Document" Templates difficult to use

[Vdragon]

Sorry for spamming you guys, but is there any updates on the ubuntu-
document-templates package?

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

Title:
  "Create Document" Templates difficult to use

Status in One Hundred Papercuts:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  The "Create Document" right-click option has only "Empty file" as an
  option and a rather puzzling "No templates installed" second option.

  I expected to find templates for the most common Openoffice file
  types.

  This is confusing for non-expert users and can lead to problems.
  Particularly to those used to the windows behaviour.

  I suggest creating a group of templates (openoffice word processor,
  spreadsheet, presentation) as the default set to ease the newcomers
  difficulties.

  As a matter of fact, a friend I introduced to Linux just realized all the 
documents she created using that method didn't have any format. She used a 
simple (although wrong) method to create Openoffice files.
  #1 Right Click inside folder - Create document - Empty File (Just as any 
windows user could do)
  #2 Rename document to whatever she wanted - Ex: Doc1.odt (this is a somehow 
advanced behaviour but still common for windows users).
  #3 Open file and ignore ASCII Filter Option message (whatever - OK)
  #4 Write in the document.
  #5 Save - Ignore warning about formating and Click on "Keep Current Format" 
instead of "Save in ODF format" (this could be seen as a huge mistake, and it 
is, but also a common behaviour if you are used to open DOC files with 
Openoffice. You end up ignoring those warnings).

  What I am proposing is to put template files for the most common
  document formats (at least openoffice ones) into the Templates folder
  by default. This way, the windows newcomers would find a Create
  Openoffice Word file option and avoid very damaging mistakes as the
  one explained before. Also, this would fill an usability gap between
  linux and windows.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/372132/+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 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method

[gerardo]

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

Same problem after an upgrade from 16.04 to 16.10 via "do-release-
upgrade". However in my case the issue occurred not for Ethernet or
Bluetooth, but for Mobile Broadband (device ttyUSB2 of type gsm over
interface ppp0). So, the changelog comment 'we definitely want NM to
manage wifi and mobile data' is not really holding. Could it be the
author erroneously supposed mobile data is only transferred over the
wwan interface? In that case, the issue should indeed be fixed.

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

Title:
  network-manager does not manage ethernet and bluetooth interfaces when
  Ubuntu 16.10 is installed using chroot/netboot method

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

Bug description:
  Hello,

  I installed Ubuntu 16.10 using a chroot. I use network-manager to
  manage connections. My system is up-to-date (so I use network-manager
  1.2.4-0ubuntu1).

  Wifi works perfectly but I cannot connect to wired networks and using
  my phone's Bluetooth connection. Corresponding devices are said to be
  unmanaged by network-manager. nmcli dev outputs:

  DEVICETYPE  STATE CONNECTION 
  enp1s0ethernet  unmanaged -- 
  wlp2s0wifi  disconnected  --
  6C:9B:02:2C:EE:2C btunmanaged -- 
  hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C  gsm   unmanaged -- 
  loloopback  unmanaged -- 

  The following command has no effect:
  sudo nmcli dev set enp1s0 managed yes

  I can connect to a wired connection by doing:
  ifconfig enp1s0 up
  dhclient enp1s0

  There is nothing in the file /etc/network/interfaces.

  Everything works perfectly if I downgrade network-manager to this
  version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb
  (http://packages.ubuntu.com/xenial-updates/amd64/network-
  manager/download). I had to install libreadline6 and downgrade nplan
  to meet dependencies.

  I don't know what to join to this bug report so please ask in case
  anything is needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842/+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 1600136] Re: App indicator does not show icon for Qt apps or with custom icons

[Launchpad Bug Tracker]

This bug was fixed in the package qtbase-opensource-src - 5.7.1+dfsg-
2ubuntu4~1

---
qtbase-opensource-src (5.7.1+dfsg-2ubuntu4~1) zesty; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * debian/patch/qdbus-tray-icon-use-runtimedir.patch:
- QDBusTrayIcon: try use runtime or cache for icons (LP: #1600136)
  * debian/patch/qdbus-tray-icon-always-save-icon-in-unity.patch:
- QDBusTrayIcon: always save the temp icon in Unity (LP: #1600136)

 -- Timo Jyrinki   Thu, 09 Feb 2017 08:42:30
+

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  App indicator does not show icon for Qt apps or with custom icons

Status in Qt:
  In Progress
Status in Snappy:
  New
Status in appmenu-qt5 package in Ubuntu:
  Fix Released
Status in libappindicator package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  In Progress
Status in sni-qt package in Ubuntu:
  Fix Released
Status in appmenu-qt5 source package in Xenial:
  Fix Released
Status in libappindicator source package in Xenial:
  Fix Released
Status in qtbase-opensource-src source package in Xenial:
  New
Status in snapd source package in Xenial:
  New
Status in sni-qt source package in Xenial:
  Fix Released

Bug description:
  Snaps that use the app indicator area via Qt can't display their icon
  there.

  Steps to reproduce and screenshot:
  https://github.com/nuttyartist/notes/pull/77

  Some research:

  - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html
  - The indicator icon is created under /tmp under a randomly generated 
directory name

  didrocks mentions also:

  1. The application says "this is my menu, and here is my icon at that 
address", the address being /tmp/blablabla
  2. appindicator receives the bus messages
  3. and says "let's have a look at this icon at that address"
  4. BUT! /tmp in the snap is different form system /tmp

  


  SRU bug for libappindicator:

  [Impact]

  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem

  [Test case]

  * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as 
snapcraft.yaml
    in any folder you want
  * Run:
    - snapcraft prime
    - sudo snap try prime
    - snap run gtk3-appindicator

  An indicator should open (with proper icon), then if you select "Set
  icon with Full Path" and/or "Enable Local Theme" from its menu, you
  should see a proper icon.

  When snaps are generated in non updated systems, the icon will be
  still missing.

  [Regression potential]

  If $SNAP is defined for an app not running in snap confinement the
  icons couldn't be properly visible

  


  SRU bug for appmenu-qt5:

  [Impact]

  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem

  [Test case]

  * Download this yaml file http://pastebin.com/raw/KeZ1udjW and save it as 
snapcraft.yaml
    in any folder you want
  * Run:
    - snapcraft prime
    - sudo snap try prime
    - snap run qt5-systray

  An indicator should open, with the proper icon showin. From the window
  you can change the icon type, and all the types should work.

  When snaps are generated in non updated systems, the icons (except the
  Themed one) will be still missing.

  [Regression potential]

  If $SNAP env variable is defined for an app not running in snap
  confinement the icons couldn't be properly visible

  


  SRU bug for sni-qt:

  [Impact]

  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem

  [Test case]

  * Download this yaml file http://pastebin.com/raw/EZjQS5CH and save it as 
snapcraft.yaml
in any folder you want
  * Run:
- snapcraft prime
- sudo snap try prime
- snap run qt4-systray

  An indicator should open, with the proper icon showin. From the window
  you can change the icon type, and all the types should work.

  When snaps are generated in non updated systems, the icons (except the
  Themed one) will be still missing.

  [Regression potential]

  If $SNAP env variable is defined for an app not running in snap
  confinement the icons couldn't be properly visible

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

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

[Desktop-packages] [Bug 1674295] [NEW] No wifi access for guest unless a user is already logged in

[Doug McMahon]

Public bug reported:

In 16.04.x guest sessions get no wifi access unless a user is already
logged in, i.e. one has to open a guest session from a user session.

In 14.04 wifi is automatically enabled for a guest session, in 17.04 a
guest needs to enter wifi password & create a keyring.

Test case: 
Boot up to a machine using wifi that's password protected, at greeter choose 
guest.
Once logged in notice nm-applet is running but no connection.
Click on icon, choose a network, click on it.

What happens: nothing

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.6-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-41-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Mar 20 07:23:48 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IpRoute:
 default via 192.168.1.1 dev wlan0  proto static  metric 600 
 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.6  metric 600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
[modified]
mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2017-01-08T20:36:09.732047
nmcli-con:
 NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATHACTIVE  DEVICE  STATE
  ACTIVE-PATH
 06F21A  1ce53caa-53f9-48d9-8bf1-0da97c1ac332  802-11-wireless  
1490008954  Mon 20 Mar 2017 07:22:34 AM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/6   yes wlan0   
activated  /org/freedesktop/NetworkManager/ActiveConnection/1 
 Wired connection 1  b2b79c5d-61cd-3fa0-a0fc-05217e735e06  802-3-ethernet   
1490006436  Mon 20 Mar 2017 06:40:36 AM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/11  no  --  --   
  --
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 wlan0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
06F21A  1ce53caa-53f9-48d9-8bf1-0da97c1ac332  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 eth0ethernet  unavailable  /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.6connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages xenial

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

Title:
  No wifi access for guest unless a user is already logged in

Status in network-manager package in Ubuntu:
  New

Bug description:
  In 16.04.x guest sessions get no wifi access unless a user is already
  logged in, i.e. one has to open a guest session from a user session.

  In 14.04 wifi is automatically enabled for a guest session, in 17.04 a
  guest needs to enter wifi password & create a keyring.

  Test case: 
  Boot up to a machine using wifi that's password protected, at greeter choose 
guest.
  Once logged in notice nm-applet is running but no connection.
  Click on icon, choose a network, click on it.

  What happens: nothing

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 20 07:23:48 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static  metric 600 
   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.6  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: 

Re: [Desktop-packages] [Bug 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies

[Thomas Leonard]

On 20 March 2017 at 02:11, Jeremy Bicha  wrote:
> fails to build :(
>
> ** Changed in: zeroinstall-injector (Ubuntu)
>Status: Fix Released => Triaged

Not sure why it builds in Debian but not Ubuntu. If you need a quick
fix, adding a build-dependency on libsha-ocaml-dev should cause it to
use that instead of openssl (the build log says "sha (ocaml-sha) not
found; using OpenSSL instead").

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

Title:
  Remove aptdaemon and drop or port its reverse-dependencies

Status in aptdaemon package in Ubuntu:
  New
Status in apturl package in Ubuntu:
  New
Status in dell-recovery package in Ubuntu:
  New
Status in gnome-software package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  New
Status in lubuntu-software-center package in Ubuntu:
  New
Status in mythbuntu-control-centre package in Ubuntu:
  New
Status in sessioninstaller package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-mate-welcome package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New
Status in update-notifier package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  Triaged
Status in aptdaemon source package in aa-series:
  New
Status in apturl source package in aa-series:
  New
Status in dell-recovery source package in aa-series:
  New
Status in gnome-software source package in aa-series:
  New
Status in language-selector source package in aa-series:
  New
Status in lubuntu-software-center source package in aa-series:
  New
Status in mythbuntu-control-centre source package in aa-series:
  New
Status in sessioninstaller source package in aa-series:
  New
Status in software-properties source package in aa-series:
  New
Status in ubiquity source package in aa-series:
  New
Status in ubuntu-mate-meta source package in aa-series:
  New
Status in ubuntu-mate-welcome source package in aa-series:
  New
Status in update-manager source package in aa-series:
  New
Status in update-notifier source package in aa-series:
  New

Bug description:
  aptdaemon is abandoned and unmaintained.  It has already been dropped
  from Debian, but there are several reverse dependencies keeping it in
  Ubuntu.  I will add bug tasks for each of those dependencies, which
  should be ported or dropped themselves.  Then we can get rid of
  aptdaemon too.

  See this mailing list thread for more details:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html

  https://bitbucket.org/ubuntu-mate/ubuntu-mate-welcome/issues/48/port-
  from-aptdaemon-to-packagekit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1673258/+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 938751] Re: jpeg images are washed out or colors are skewed

[zhy]

Bug here in Thinkpad X250 with ubuntu 16.04.
I can't imagine this is bug with such a long AGE.

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

Title:
  jpeg images are washed out or colors are skewed

Status in Eye of GNOME:
  New
Status in eog package in Ubuntu:
  Confirmed
Status in eog source package in Precise:
  Confirmed

Bug description:
  Not all images are affected but enough are. Below is a screen shot of
  the issue with the image highlighted in nautilus to show that the
  color corruption seems to be eog rather than libjpeg.

  http://ubuntuone.com/1oFONmmTFXBzlHbM436Rwd

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: eog 3.3.90-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-17.26-generic-pae 3.2.6
  Uname: Linux 3.2.0-17-generic-pae i686
  ApportVersion: 1.92-0ubuntu1
  Architecture: i386
  CheckboxSubmission: ba9c4255a69726424c6447d1c48d6601
  CheckboxSystem: d00f84de8a555815fa1c4660280da308
  Date: Wed Feb 22 09:13:48 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 
(20120201.1)
  SourcePackage: eog
  UpgradeStatus: Upgraded to precise on 2012-02-21 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/eog/+bug/938751/+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 1673491] Re: [Zesty] libnl3 Segmentation fault in sriov environments

[Launchpad Bug Tracker]

This bug was fixed in the package libnl3 - 3.2.29-0ubuntu2

---
libnl3 (3.2.29-0ubuntu2) zesty; urgency=medium

  * Fix crash in sriov environments (LP: #1673491)
Applying patches of upstream issue #126, see the link for more:
https://github.com/thom311/libnl/issues/126
- d/p/u/sriov-avoid-buffer-overrun-in-rtnl_link_sriov_parse_vflist.patch
- d/p/u/sriov-fix-crash-in-rtnl_link_sriov_parse_vflist.patch

 -- Christian Ehrhardt   Fri, 17 Mar
2017 10:12:17 +0100

** Changed in: libnl3 (Ubuntu)
   Status: New => Fix Released

** Bug watch added: github.com/thom311/libnl/issues #126
   https://github.com/thom311/libnl/issues/126

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

Title:
  [Zesty] libnl3 Segmentation fault in sriov environments

Status in libnl3 package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  New

Bug description:
  in Ubuntu 17.04 we can't open a virt-manager, we see sefault

  This issue happen when we update from kernel 4.10.0-9-generic to
  4.10.0-11-generic

  root@:~# /usr/sbin/libvirtd
  Segmentation fault (core dumped)   

  root@:~# gdb /usr/sbin/libvirtd ./core 
  GNU gdb (Ubuntu 7.12.50.20170314-0ubuntu1) 7.12.50.20170314-git
  Copyright (C) 2017 Free Software Foundation, Inc.  
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.   
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"   
  and "show warranty" for details. 
  This GDB was configured as "x86_64-linux-gnu".   
  Type "show configuration" for configuration details. 
  For bug reporting instructions, please see:  
  . 
  Find the GDB manual and other documentation resources online at: 
  .
  For help, type "help".   
  Type "apropos word" to search for commands related to "word"...  
  Reading symbols from /usr/sbin/libvirtd...(no debugging symbols found)...done.
  [New LWP 4232]
  [New LWP 4216]
  [New LWP 4219]
  [New LWP 4218]
  [New LWP 4231]
  [New LWP 4215]
  [New LWP 4220]
  [New LWP 4224]
  [New LWP 4221]
  [New LWP 4223]
  [New LWP 4222]
  [New LWP 4217]
  [New LWP 4225]
  [New LWP 4227]
  [New LWP 4230]
  [New LWP 4229]
  [New LWP 4228]
  [Thread debugging using libthread_db enabled] 
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/usr/sbin/libvirtd'.   
  Program terminated with signal SIGSEGV, Segmentation fault.   
  #0  0x7f97fa93367f in rtnl_link_sriov_parse_vflist () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200
  [Current thread is 1 (Thread 0x7f97dff94700 (LWP 4232))]  
   
  (gdb) where   
   
  #0  0x7f97fa93367f in rtnl_link_sriov_parse_vflist () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200
  #1  0x7f97fa927fad in ?? () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200  
  #2  0x7f980bfb76c3 in nl_cache_parse () from 
/lib/x86_64-linux-gnu/libnl-3.so.200
  #3  0x7f980bfb770b in ?? () from /lib/x86_64-linux-gnu/libnl-3.so.200 
   

[Desktop-packages] [Bug 1589447] Re: Xdummy cannot be used in Xenial

[Bharat Kunwar]

I have documented how I resolved this issue on my blog: 
http://brtknr.com/2017/03/15/permission-issues-with-xpra-on-ubuntu-16-04-when-tunnelling-through-SSH/

Turns out that the version of xpra (0.15.x) provided with Ubuntu 16.04
is not supported anymore and updating to 2.0.x resolved the issue.

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

Title:
  Xdummy cannot be used in Xenial

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

Bug description:
  Xdummy is used by several systems for remote display, such as xpra
  (http://xpra.org/).

  Unfortunately, since Xenial, it is completely impossible to use Xdummy
  for anything like that, because of the way in which permissions are
  set up for running X servers. This results in a serious compromise on
  the possibility of running remote displays systems on ubuntu. In fact,
  the latter can only rely on Xvfb with a less than optimal experience.

  Most important, 
  Trying to run Xdummy from a console session results in

  /usr/lib/xorg/Xorg.wrap: Only console users are allowed to run the X
  server

  It should be possible to start Xdummy from an ssh session. Xdummy is a
  'dummy' display driver. It does not touch real hardware. There is no
  need to prevent users who are not on the console from starting it. In
  fact, it is not clear what is the purpose of taking the effort of
  packaging and shipping Xdummy at all, if it cannot be used for the
  tasks it is intended for.

  See also:

  http://xpra.org/trac/ticket/1220

  The Xpra developer, whose availability to help is always excellent,
  explicitly states that:

  - it is not possible to use xdummy with almost all Ubuntu releases [in
  fact the problem is Xenial. Before xenial, xdummy required some
  tweaks, but worked]

  - xpra needs to be compiled with the --without-Xdummy on Ubuntu
  because of this

  - There is nothing that can be done in xpra, because this is an OS
  permission problem

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-video-dummy 1:0.3.7-1build5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Jun  6 11:54:50 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (906 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: xserver-xorg-video-dummy
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (45 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-dummy/+bug/1589447/+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 1671799] Re: FFe: xserver 1.19.3

[dino99]

This scrolling issue has been met also outside the ubuntu world:
https://ubuntuforums.org/showthread.php?t=2355713=13622468#post13622468

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

Title:
  FFe: xserver 1.19.3

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  xserver 1.19 has been out for quite some time now. Debian Stretch will
  release with it, and xmir has been recently ported so we can push 1.19
  to zesty now. It's currently being staged on a ppa:

  https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging

  The main features of this release are:
  - PRIME synchronization support, should reduce tearing on hybrid setups
  - GLAMOR (2D accel over OpenGL) improvements
  - threaded input

  This bugreport is also for gathering testing feedback.

  Tested to be working fine on:
  - Intel Kabylake
  - Intel Broadwell
  - Intel+NVIDIA hybrid (Skylake + 930MX, with OSS and blob drivers)
  - Intel+NVIDIA hybrid (Haswell + NVIDIA GK107M [GeForce GT 755M])
  - Intel+NVIDIA hybrid (Ivybridge + NVIDIA GK107M [GeForce GT 660M])
  - Radeon SI (radeon & amdgpu drivers)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799/+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 1671799] Re: FFe: xserver 1.19.3

[dino99]

Made some tests, with both xserver 18 & with/without input-libinput 23 ;
and xserver 19 with/without input-libinput 25

To clarify 'mouse': it's a generic usb mouse, no touchpad at all. Tests
made on two different ZZ partitions on the same desktop.

Test xserver 18
- note that comment #26 above is a bit confusing: i was talking about the 
partition using xserver 18
- xserver 18 without input-libinput 23: works well (as previouly said (#23)
- xserver 18 + input-libinput 23: no problem to select a range of calc's cells; 
but discovered an other 'scrolling' issue when trying to set the 'sort 
criteria' for keys: scrolling does not work.
That is when using Calc sorting; testing 'scrolling' inside 'nautilus' works 
well (confusing).
So i purge input-libinput hoping to get back a normal calc's sorting scrolling; 
that fails; closing calc / restating gnome-shell session / even logout/in the 
session does not set scrolling back (confusion again); Check System settings 
mouse options /gnome-tweak-tool but settings are as usual.

- xserver 19 + input-libinput 25 : problem initialy reported
- xserver 19 without input-libinput 25 (23 not installable due to abi, so cant 
test that case): selecting a cells range can be done as expected, scrolling for 
sorting also works !!!

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

Title:
  FFe: xserver 1.19.3

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  xserver 1.19 has been out for quite some time now. Debian Stretch will
  release with it, and xmir has been recently ported so we can push 1.19
  to zesty now. It's currently being staged on a ppa:

  https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging

  The main features of this release are:
  - PRIME synchronization support, should reduce tearing on hybrid setups
  - GLAMOR (2D accel over OpenGL) improvements
  - threaded input

  This bugreport is also for gathering testing feedback.

  Tested to be working fine on:
  - Intel Kabylake
  - Intel Broadwell
  - Intel+NVIDIA hybrid (Skylake + 930MX, with OSS and blob drivers)
  - Intel+NVIDIA hybrid (Haswell + NVIDIA GK107M [GeForce GT 755M])
  - Intel+NVIDIA hybrid (Ivybridge + NVIDIA GK107M [GeForce GT 660M])
  - Radeon SI (radeon & amdgpu drivers)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799/+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 1669344] Re: Received signal 4 ILL_ILLOPN

[wvengen]

Due to suspend/resume+wifi driver issues, I can't upgrade the kernel.
Downgrading Chromium works around this problem (though not very pretty).
The previous version is still available here
https://launchpad.net/ubuntu/+source/chromium-
browser/55.0.2883.87-0ubuntu2.1329/+build/12052688

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

Title:
  Received signal 4 ILL_ILLOPN

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  This morning chromium-browser upgraded to
  56.0.2924.76-0ubuntu0.16.10.1335 and promptly stopped working for me.
  When trying to load any page, it dumps this traceback:

  Received signal 4 ILL_ILLOPN 7f78b7a509e7
  #0 0x7f78d509500e base::debug::StackTrace::StackTrace()
  #1 0x7f78d5095403 
  #2 0x7f78d53aa630 
  #3 0x7f78b7a509e7 WTF::decommitSystemPages()
  #4 0x7f78c3f997b0 
  #5 0x7f78c3f99f17 
  #6 0x7f78c3f97b0e blink::NormalPageArena::allocatePage()
  #7 0x7f78c3f98560 blink::NormalPageArena::outOfLineAllocate()
  #8 0x7f78c3987678 blink::ChromeClientImpl::create()
  #9 0x7f78c3a2929a blink::WebViewImpl::WebViewImpl()
  #10 0x7f78c3a2aeb3 blink::WebViewImpl::create()
  #11 0x7f78cfcd8769 content::RenderViewImpl::Initialize()
  #12 0x7f78cfcd9443 content::RenderViewImpl::Create()
  #13 0x7f78cf5d8692 content::mojom::RendererStubDispatch::Accept()
  #14 0x7f78d4bc2671 mojo::InterfaceEndpointClient::HandleValidatedMessage()
  #15 0x7f78d0d17bd0 
  #16 0x7f78d0d18034 
  #17 0x7f78d5096543 base::debug::TaskAnnotator::RunTask()
  #18 0x7f78c3f35f4f 
blink::scheduler::TaskQueueManager::ProcessTaskFromWorkQueue()
  #19 0x7f78c3f36ab0 blink::scheduler::TaskQueueManager::DoWork()
  #20 0x7f78d5096543 base::debug::TaskAnnotator::RunTask()
  #21 0x7f78d50bc740 base::MessageLoop::RunTask()
  #22 0x7f78d50be33d base::MessageLoop::DeferOrRunPendingTask()
  #23 0x7f78d50bf19d base::MessageLoop::DoWork()
  #24 0x7f78d50bf589 base::MessagePumpDefault::Run()
  #25 0x7f78d50bbb22 base::MessageLoop::RunHandler()
  #26 0x7f78d50e44b8 base::RunLoop::Run()
  #27 0x7f78cfcf5629 
  #28 0x7f78cfde7048 
  #29 0x7f78cfde7444 
  #30 0x7f78cfde68c1 content::ContentMain()
  #31 0x55b0046e086c 
  #32 0x7f78bfec03f1 __libc_start_main
  #33 0x55b0046e073a 
r8:   r9:  r10: 0022 r11: 
0206
   r12: 16113987 r13: 0004 r14: 7f78b7c87448 r15: 

di: 3fb7e8201000  si: 0001e000  bp: 16113981c210  bx: 
16113981c218
dx: 0008  ax:   cx: ff68  sp: 
7fffa09e5f30
ip: 7f78b7a509e7 efl: 00010286 cgf: 0033 erf: 

   trp: 0006 msk:  cr2: 
  [end of stack trace]

  Being chromium, the overall processes don't die or coredump, so apport
  never sends any reports here.  That is why I am filing via ubuntu-bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: chromium-browser 56.0.2924.76-0ubuntu0.16.10.1335
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  DRM.card0-DP-1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0-DP-2:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: enabled
   status: disconnected
  DRM.card0-HDMI-A-1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0-HDMI-A-2:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0-eDP-1:
   edid-base64: 
AP///wAw5DcEAAAXAQSVHBB4Ar8FmllVjiYdUFQBAQEBAQEBAQEBAQEBAQEBFjaAunA4D0AwIDUAFJwQAAAa/gBMRyBEaXNwbGF5CiAg/gBMUDEyNVdGMi1TUEIyAN0=
   dpms: On
   modes: 1920x1080
   enabled: enabled
   status: connected
  Date: Thu Mar  2 10:18:41 2017
  Desktop-Session:
   'ubuntu'
   
'/etc/xdg/xdg-ubuntu:/usr/share/upstart/systemd-session:/usr/share/upstart/xdg:/etc/xdg'
   '/usr/share/ubuntu:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2014-05-29 (1007 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  InstalledPlugins:
   /usr/lib/mozilla/plugins:
 => librhythmbox-itms-detection-plugin.so
   (size: 6072 bytes, mtime: Sat Sep 10 19:28:55 2016)
  Load-Avg-1min: 0.95
  Load-Processes-Running-Percent:   0.2%
  MachineType: LENOVO 20ALCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to yakkety on 2016-10-01 (152 days 

[Desktop-packages] [Bug 1669344] Re: Received signal 4 ILL_ILLOPN

[d3b null]

Confirmed. Updating to 4.8 (from 4.4) fixed the problem.

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

Title:
  Received signal 4 ILL_ILLOPN

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  This morning chromium-browser upgraded to
  56.0.2924.76-0ubuntu0.16.10.1335 and promptly stopped working for me.
  When trying to load any page, it dumps this traceback:

  Received signal 4 ILL_ILLOPN 7f78b7a509e7
  #0 0x7f78d509500e base::debug::StackTrace::StackTrace()
  #1 0x7f78d5095403 
  #2 0x7f78d53aa630 
  #3 0x7f78b7a509e7 WTF::decommitSystemPages()
  #4 0x7f78c3f997b0 
  #5 0x7f78c3f99f17 
  #6 0x7f78c3f97b0e blink::NormalPageArena::allocatePage()
  #7 0x7f78c3f98560 blink::NormalPageArena::outOfLineAllocate()
  #8 0x7f78c3987678 blink::ChromeClientImpl::create()
  #9 0x7f78c3a2929a blink::WebViewImpl::WebViewImpl()
  #10 0x7f78c3a2aeb3 blink::WebViewImpl::create()
  #11 0x7f78cfcd8769 content::RenderViewImpl::Initialize()
  #12 0x7f78cfcd9443 content::RenderViewImpl::Create()
  #13 0x7f78cf5d8692 content::mojom::RendererStubDispatch::Accept()
  #14 0x7f78d4bc2671 mojo::InterfaceEndpointClient::HandleValidatedMessage()
  #15 0x7f78d0d17bd0 
  #16 0x7f78d0d18034 
  #17 0x7f78d5096543 base::debug::TaskAnnotator::RunTask()
  #18 0x7f78c3f35f4f 
blink::scheduler::TaskQueueManager::ProcessTaskFromWorkQueue()
  #19 0x7f78c3f36ab0 blink::scheduler::TaskQueueManager::DoWork()
  #20 0x7f78d5096543 base::debug::TaskAnnotator::RunTask()
  #21 0x7f78d50bc740 base::MessageLoop::RunTask()
  #22 0x7f78d50be33d base::MessageLoop::DeferOrRunPendingTask()
  #23 0x7f78d50bf19d base::MessageLoop::DoWork()
  #24 0x7f78d50bf589 base::MessagePumpDefault::Run()
  #25 0x7f78d50bbb22 base::MessageLoop::RunHandler()
  #26 0x7f78d50e44b8 base::RunLoop::Run()
  #27 0x7f78cfcf5629 
  #28 0x7f78cfde7048 
  #29 0x7f78cfde7444 
  #30 0x7f78cfde68c1 content::ContentMain()
  #31 0x55b0046e086c 
  #32 0x7f78bfec03f1 __libc_start_main
  #33 0x55b0046e073a 
r8:   r9:  r10: 0022 r11: 
0206
   r12: 16113987 r13: 0004 r14: 7f78b7c87448 r15: 

di: 3fb7e8201000  si: 0001e000  bp: 16113981c210  bx: 
16113981c218
dx: 0008  ax:   cx: ff68  sp: 
7fffa09e5f30
ip: 7f78b7a509e7 efl: 00010286 cgf: 0033 erf: 

   trp: 0006 msk:  cr2: 
  [end of stack trace]

  Being chromium, the overall processes don't die or coredump, so apport
  never sends any reports here.  That is why I am filing via ubuntu-bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: chromium-browser 56.0.2924.76-0ubuntu0.16.10.1335
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  DRM.card0-DP-1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0-DP-2:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: enabled
   status: disconnected
  DRM.card0-HDMI-A-1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0-HDMI-A-2:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0-eDP-1:
   edid-base64: 
AP///wAw5DcEAAAXAQSVHBB4Ar8FmllVjiYdUFQBAQEBAQEBAQEBAQEBAQEBFjaAunA4D0AwIDUAFJwQAAAa/gBMRyBEaXNwbGF5CiAg/gBMUDEyNVdGMi1TUEIyAN0=
   dpms: On
   modes: 1920x1080
   enabled: enabled
   status: connected
  Date: Thu Mar  2 10:18:41 2017
  Desktop-Session:
   'ubuntu'
   
'/etc/xdg/xdg-ubuntu:/usr/share/upstart/systemd-session:/usr/share/upstart/xdg:/etc/xdg'
   '/usr/share/ubuntu:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2014-05-29 (1007 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  InstalledPlugins:
   /usr/lib/mozilla/plugins:
 => librhythmbox-itms-detection-plugin.so
   (size: 6072 bytes, mtime: Sat Sep 10 19:28:55 2016)
  Load-Avg-1min: 0.95
  Load-Processes-Running-Percent:   0.2%
  MachineType: LENOVO 20ALCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to yakkety on 2016-10-01 (152 days ago)
  dmi.bios.date: 08/27/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GIET76WW (2.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ALCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  

[Desktop-packages] [Bug 1639507] Re: unity-control-center in installed software is listed with wrong icon and title

[Iain Lane]

That's automatic and you can check it by just looking at the archive. I
did not look in this case to see if it is right, but it was in the
previous case (wine?).

I think someone should see my comment #4 on
https://bugzilla.gnome.org/show_bug.cgi?id=779379

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

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

Title:
  unity-control-center in installed software is listed with wrong icon
  and title

Status in unity-control-center package in Ubuntu:
  Fix Released
Status in unity-control-center source package in Xenial:
  Fix Committed
Status in unity-control-center source package in Yakkety:
  Fix Committed
Status in unity-control-center source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  In Ubuntu Software under Installed programs the listing for 
gnome-control-center package has title "Wacom Tablet" and tablet icon.
  This is dangerously confusing, as average user can easily remove control 
center without knowing it.
  I propose disabling gnome-control-center removal from Ubuntu Software by 
moving it to "System Applications" section.

  [Test Case]
  1. From a terminal run:
  $ gnome-software --details-pkg unity-control-center

  Observed result:
  The title/description is from one of the panels inside u-c-c, e.g. "Wacom 
Tablet" or "Universal Access".

  Expected result:
  The title and description should be for unity-control-center.
  NOTE: This requires the appdata to be updated and re-downloaded before this 
can occur.

  [Regression Potential]
  Low, we now just distribute appdata information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1639507/+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 1673984] Re: Can not add google account any more (Zesty)

[Alberto Mardegan]

** Branch linked: lp:~mardy/signon-ui/unity-crash-1673984

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

Title:
  Can not add google account any more (Zesty)

Status in signon-ui package in Ubuntu:
  Confirmed

Bug description:
  After updating Unity-Control-Center to 15.04.0+17.04.20170314-0ubuntu2
  and liboxidecore to 1.20.4-0ubuntu1 on Zesty I could not able to add
  to add Google account.

  ### How to reproduce:

  1. Go online account try adding google account.

  2. Infobar will appear for a moment and the it will disappear.
  Screenshot: https://i.imgur.com/evDPZSv.png

  3. The login page doesn't load at all.

  Running online-accounts-preferences from terminal gives:
  --
  (unity-control-center:7866): credentials-cc-panel-CRITICAL **: 
cc-credentials-authorization-page.vala:182: Error completing auth session 
process: 
GDBus.Error:com.google.code.AccountsSSO.SingleSignOn.Error.UserInteraction: 
userActionFinished error: 2
  --

  Installed Packages (Ubuntu 17.04 32 bit):
  account-plugin-google: 0.13+17.04.20161206-0ubuntu1
  signon-ui-x11: 0.17+17.04.20161109-0ubuntu1
  unity-control-center: 15.04.0+17.04.20170314-0ubuntu2
  unity-control-center-signon: 0.1.9+16.10.20160825-0ubuntu1

  All other packages are up-to-date

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1673984/+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 1637652] Re: stucked in a login loop

[Sébastien Lamy]

On ubuntu 16.04-2, This bug doesn't affect me with nvidia 304.134, but I had 
other problems with this 304.134 driver, and I tried to use nvidia 304.135 from 
the ppa:graphics-drivers/ppa.
With the 304.135 installed, I got stuck in the login loop.
Same thing when trying the 331 drivers

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

Title:
  stucked in a login loop

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  after 16.10 upgrade I cannot login into the graphical interface

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  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
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Oct 28 23:40:30 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-26-generic, x86_64: installed
   nvidia-340, 340.98, 4.8.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G86 [GeForce 8500 GT] [10de:0421] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Point of View BV G86 [GeForce 8500 GT] [1acc:0857]
  InstallationDate: Installed on 2012-03-13 (1690 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: Gigabyte Technology Co., Ltd. Z68XP-UD3P
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=401cb21e-ddab-46d5-a6dd-72a53a7f0ca3 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F7
  dmi.board.name: Z68XP-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd02/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnZ68XP-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68XP-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: Z68XP-UD3P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  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
  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 N/A
  xserver.bootTime: Fri Oct 28 23:29:28 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech Gaming Keyboard G610 KEYBOARD, id 8
   inputLogitech Gaming Keyboard G610 KEYBOARD, id 9
   inputLogitech USB Optical Mouse MOUSE, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1637652/+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 1651938] Re: Owncloud Account doesn't work with Nextcloud 11

[Launchpad Bug Tracker]

This bug was fixed in the package account-plugins -
0.13+17.04.20170314-0ubuntu1

---
account-plugins (0.13+17.04.20170314-0ubuntu1) zesty; urgency=medium

  * NextCloud/OwnCloud: fix account creation on newer releases (LP:
#1651938)

 -- Alberto Mardegan   Tue, 14 Mar 2017
10:30:56 +

** Changed in: account-plugins (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Owncloud Account doesn't work with Nextcloud 11

Status in account-plugins package in Ubuntu:
  Fix Released

Bug description:
  Dear,

  Since my nextcloud server update i cannot connect anymore to my calendar.
  My contacts with syncevolution no problem. 

  I think i found why, nextcloud reduce the CRSF vulnerability

  phablet@ubuntu-phablet:~$   export OAU_LOGGING_LEVEL=2
  phablet@ubuntu-phablet:~$   export OAU_DAEMON_TIMEOUT=
  phablet@ubuntu-phablet:~$   online-accounts-service
  service.cpp 42 requestAccess Got request: QMap(("application", 
QVariant(QString, "system-settings") ) ( "pid" ,  QVariant(uint, 26947) ) ( 
"provider" ,  QVariant(QString, "owncloud") ) ( "windowId" ,  QVariant(uint, 
26947) ) ) 
  App ID: "unconfined"
  request-manager.cpp 113 runQueue Head: OnlineAccountsUi::Request(0x1d829d8)
  mir-helper.cpp 151 session_event_callback Prompt Session state updated to 1
  Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0'
  ui-server.cpp 103 onDataReady QMap(("code", QVariant(QString, "process") ) ( 
"data" ,  QVariant(QVariantMap, QMap(("application", QVariant(QString, 
"system-settings") ) ( "pid" ,  QVariant(uint, 26947) ) ( "provider" ,  
QVariant(QString, "owncloud") ) ( "windowId" ,  QVariant(uint, 26947) ) ) ) ) ( 
"id" ,  QVariant(int, 0) ) ( "interface" ,  QVariant(QString, 
"com.ubuntu.OnlineAccountsUi") ) ( "profile" ,  QVariant(QString, "unconfined") 
) ) 
  qml: Page_QMLTYPE_24(0x1973a38)"ownCloud": In Ubuntu.Components 1.3, the use 
of Page.title, Page.flickable and Page.head is deprecated. Use Page.header and 
the PageHeader component instead.
  file:///home/phablet/.local/share/accounts/qml-plugins/owncloud/Main.qml: 
File not found
  virtual void OnlineAccountsPlugin::Plugin::registerTypes(const char*) 
Ubuntu.OnlineAccounts.Plugin
  request.cpp 115 setWindow Requesting window reparenting
  QWindow::fromWinId(): platform plugin does not support foreign windows.
  APP_ID isn't set, the handler ignored
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  qml: Trying host https://server as login:password
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding loop detected for property "contentHeight"
  file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main: 
Binding 

[Desktop-packages] [Bug 1671799] Re: FFe: xserver 1.19.3

[Timo Aaltonen]

fwiw, I can't repro that bug on a touchpad using -libinput (synaptics
doesn't work right with it)

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

Title:
  FFe: xserver 1.19.3

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  xserver 1.19 has been out for quite some time now. Debian Stretch will
  release with it, and xmir has been recently ported so we can push 1.19
  to zesty now. It's currently being staged on a ppa:

  https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging

  The main features of this release are:
  - PRIME synchronization support, should reduce tearing on hybrid setups
  - GLAMOR (2D accel over OpenGL) improvements
  - threaded input

  This bugreport is also for gathering testing feedback.

  Tested to be working fine on:
  - Intel Kabylake
  - Intel Broadwell
  - Intel+NVIDIA hybrid (Skylake + 930MX, with OSS and blob drivers)
  - Intel+NVIDIA hybrid (Haswell + NVIDIA GK107M [GeForce GT 755M])
  - Intel+NVIDIA hybrid (Ivybridge + NVIDIA GK107M [GeForce GT 660M])
  - Radeon SI (radeon & amdgpu drivers)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799/+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 1671799] Re: FFe: xserver 1.19.3

[Timo Aaltonen]

By mouse do you mean touchpad or an actual mouse? Touchpads use
-synaptics which got bumped to 1.9.0. Test a real mouse too if not
already.

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

Title:
  FFe: xserver 1.19.3

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  xserver 1.19 has been out for quite some time now. Debian Stretch will
  release with it, and xmir has been recently ported so we can push 1.19
  to zesty now. It's currently being staged on a ppa:

  https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging

  The main features of this release are:
  - PRIME synchronization support, should reduce tearing on hybrid setups
  - GLAMOR (2D accel over OpenGL) improvements
  - threaded input

  This bugreport is also for gathering testing feedback.

  Tested to be working fine on:
  - Intel Kabylake
  - Intel Broadwell
  - Intel+NVIDIA hybrid (Skylake + 930MX, with OSS and blob drivers)
  - Intel+NVIDIA hybrid (Haswell + NVIDIA GK107M [GeForce GT 755M])
  - Intel+NVIDIA hybrid (Ivybridge + NVIDIA GK107M [GeForce GT 660M])
  - Radeon SI (radeon & amdgpu drivers)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799/+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 1672033] Re: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME)

[Tim]

what hardware are you running? I recall  some hybrid laptops fail to
advertise a "primary" display. what is the output of "xrandr -q" in a
working root-less X session?

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

Title:
  Xorg does not detect displays in rootless mode on nvidia proprietary
  drivers (GNOME)

Status in NVIDIA Drivers Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  There are two bug reports in LP: #1559576, LP: #1632322 and also LP:
  #164, where GDM does not start on proprietary nvidia drivers. As
  it turned out, the reason for that was Xorg starting in rootless mode
  and apparently not initializing everything properly, which was causing
  gnome-shell/libmutter to crash.

  Installing xserver-xorg-legacy did partially fix those issues.

  Enabling modesetting for nvidia driver however still causes the
  problem.

  
  Here are some parts from log:
  Xorg startup:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (--) Log file 
renamed from "/var/lib/gdm3/.local/share/xorg/Xorg.pid-2027.log" to 
"/var/lib/gdm3/.local/share/xorg/Xorg.0.log"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X.Org X Server 
1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Release Date: 
2016-07-19
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X Protocol Version 
11, Revision 0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Build Operating 
System: Linux 4.4.0-53-generic x86_64 Ubuntu

  glx loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"glx"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/libglx.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module glx: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Server Extension
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA GLX 
Module  375.39  Tue Jan 31 19:37:12 PST 2017

  nvidia loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"nvidia"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module nvidia: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver

  modesetting loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"modesetting"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/xorg/modules/drivers/modesetting_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module 
modesetting: vendor="X.Org Foundation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 1.18.4, module version = 1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: ABI class: 
X.Org Video Driver, version 20.0

  
  gnome-shell fails to run:
  Mär 11 00:43:20 arvlin kernel: gnome-shell[2067]: segfault at 28 ip 
7fedba8da7c4 sp 7ffd2fb5f5a0 error 4 in 
libmutter-0.so.0.0.0[7fedba893000+12f000]

  xorg stops:
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:66
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:67
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:64
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:65
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA(GPU-0): 
Deleting GPU-0
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Server 
terminated successfully (0). Closing log file.
  Mär 11 00:43:21 arvlin gdm-launch-environment][2009]: 
pam_unix(gdm-launch-environment:session): session closed for user gdm

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1672033] Re: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME)

[Tim]

Also does lightdm work with KMS enabled for logging into gnome-shell
session?

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

Title:
  Xorg does not detect displays in rootless mode on nvidia proprietary
  drivers (GNOME)

Status in NVIDIA Drivers Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  There are two bug reports in LP: #1559576, LP: #1632322 and also LP:
  #164, where GDM does not start on proprietary nvidia drivers. As
  it turned out, the reason for that was Xorg starting in rootless mode
  and apparently not initializing everything properly, which was causing
  gnome-shell/libmutter to crash.

  Installing xserver-xorg-legacy did partially fix those issues.

  Enabling modesetting for nvidia driver however still causes the
  problem.

  
  Here are some parts from log:
  Xorg startup:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (--) Log file 
renamed from "/var/lib/gdm3/.local/share/xorg/Xorg.pid-2027.log" to 
"/var/lib/gdm3/.local/share/xorg/Xorg.0.log"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X.Org X Server 
1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Release Date: 
2016-07-19
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X Protocol Version 
11, Revision 0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Build Operating 
System: Linux 4.4.0-53-generic x86_64 Ubuntu

  glx loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"glx"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/libglx.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module glx: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Server Extension
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA GLX 
Module  375.39  Tue Jan 31 19:37:12 PST 2017

  nvidia loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"nvidia"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module nvidia: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver

  modesetting loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"modesetting"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/xorg/modules/drivers/modesetting_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module 
modesetting: vendor="X.Org Foundation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 1.18.4, module version = 1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: ABI class: 
X.Org Video Driver, version 20.0

  
  gnome-shell fails to run:
  Mär 11 00:43:20 arvlin kernel: gnome-shell[2067]: segfault at 28 ip 
7fedba8da7c4 sp 7ffd2fb5f5a0 error 4 in 
libmutter-0.so.0.0.0[7fedba893000+12f000]

  xorg stops:
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:66
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:67
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:64
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:65
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA(GPU-0): 
Deleting GPU-0
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Server 
terminated successfully (0). Closing log file.
  Mär 11 00:43:21 arvlin gdm-launch-environment][2009]: 
pam_unix(gdm-launch-environment:session): session closed for user gdm

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1672033/+subscriptions

-- 
Mailing list: 

[Desktop-packages] [Bug 1673984] Re: Can not add google account any more (Zesty)

[Alberto Mardegan]

Thanks for the report, Alam!
I can confirm this. Here's the stack trace:


signon: browser-request.cpp 585 buildDialog Dialog was built
signon: request.cpp 137 setWindow Requesting window embedding

Thread 1 "signon-ui" received signal SIGSEGV, Segmentation fault.
QWindow::show (this=0x0) at kernel/qwindow.cpp:1851
1851kernel/qwindow.cpp: No such file or directory.
(gdb) bt
#0  0x740bf8de in QWindow::show() (this=0x0) at kernel/qwindow.cpp:1851
#1  0x5558b5e2 in SignOnUi::RequestPrivate::setWindow(QWindow*) 
(this=this@entry=0x558d0070, window=0x0) at request.cpp:139
#2  0x5558b7e0 in SignOnUi::Request::setWidget(QWidget*) 
(this=, widget=0x558d07f0) at request.cpp:308
#3  0x5556c25b in SignOnUi::BrowserRequestPrivate::start() 
(this=0x558d01f0) at browser-request.cpp:599
#4  0x5558d794 in 
SignOnUi::ServicePrivate::runQueue(QQueue&) 
(this=this@entry=0x558ba200, queue=...) at service.cpp:141
#5  0x5558da62 in SignOnUi::ServicePrivate::enqueue(SignOnUi::Request*) 
(this=this@entry=0x558ba200, request=request@entry=0x558d03a0) at 
service.cpp:126
#6  0x5558def0 in SignOnUi::Service::queryDialog(QMap const&) (this=0x558ba790, parameters=...) at service.cpp:227
#7  0x55593571 in SignOnUi::Service::qt_static_metacall(QObject*, 
QMetaObject::Call, int, void**) (_o=, _c=, 
_id=, _a=0x7fffd360) at moc_service.cpp:107
#8  0x555936d8 in SignOnUi::Service::qt_metacall(QMetaObject::Call, 
int, void**) (this=0x558ba790, _c=QMetaObject::InvokeMetaMethod, _id=1, 
_a=0x7fffd360)
at moc_service.cpp:169
#9  0x73d56650 in  () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#10 0x73d5a4fd in  () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#11 0x73d5aadc in  () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#12 0x73d5d5ae in  () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#13 0x721bb359 in QObject::event(QEvent*) () at 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7484835c in QApplicationPrivate::notify_helper(QObject*, QEvent*) 
() at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x7484fb11 in QApplication::notify(QObject*, QEvent*) () at 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x7218e8a0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) 
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7219102d in QCoreApplicationPrivate::sendPostedEvents(QObject*, 
int, QThreadData*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x721e2b03 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x72ca2377 in g_main_context_dispatch () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x72ca25e0 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x72ca268c in g_main_context_iteration () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x721e2f0f in 
QEventDispatcherGlib::processEvents(QFlags) () 
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x7218c88a in 
QEventLoop::exec(QFlags) () at 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x72194ffc in QCoreApplication::exec() () at 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x55566b03 in main(int, char**) (argc=, 
argv=) at main.cpp:99



** Package changed: account-plugins (Ubuntu) => signon-ui (Ubuntu)

** Changed in: signon-ui (Ubuntu)
   Importance: Undecided => Critical

** Changed in: signon-ui (Ubuntu)
   Status: New => Confirmed

** Changed in: signon-ui (Ubuntu)
 Assignee: (unassigned) => Alberto Mardegan (mardy)

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

Title:
  Can not add google account any more (Zesty)

Status in signon-ui package in Ubuntu:
  Confirmed

Bug description:
  After updating Unity-Control-Center to 15.04.0+17.04.20170314-0ubuntu2
  and liboxidecore to 1.20.4-0ubuntu1 on Zesty I could not able to add
  to add Google account.

  ### How to reproduce:

  1. Go online account try adding google account.

  2. Infobar will appear for a moment and the it will disappear.
  Screenshot: https://i.imgur.com/evDPZSv.png

  3. The login page doesn't load at all.

  Running online-accounts-preferences from terminal gives:
  --
  (unity-control-center:7866): credentials-cc-panel-CRITICAL **: 
cc-credentials-authorization-page.vala:182: Error completing auth session 
process: 
GDBus.Error:com.google.code.AccountsSSO.SingleSignOn.Error.UserInteraction: 
userActionFinished error: 2
  --

  Installed Packages (Ubuntu 17.04 32 bit):
  account-plugin-google: 0.13+17.04.20161206-0ubuntu1
  signon-ui-x11: 0.17+17.04.20161109-0ubuntu1
  unity-control-center: 

[Desktop-packages] [Bug 1662281] Re: Firefox shows post-crash page after reboot or logoff

[Launchpad Bug Tracker]

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

** Changed in: gnome-session (Ubuntu)
   Status: New => Confirmed

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

Title:
  Firefox shows post-crash page after reboot or logoff

Status in gnome-session:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  When rebooting or logging off, Firefox and thinks it crashed, and
  shows the post-crash session restore  page.

  See also Mozilla bug
  https://bugzilla.mozilla.org/show_bug.cgi?id=557601 and related bugs
  there.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: firefox 51.0.1+build2-0ubuntu0.16.10.2
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  reuben 1902 F pulseaudio
   /dev/snd/controlC1:  reuben 1902 F pulseaudio
  BuildID: 20170201174907
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Mon Feb  6 16:04:15 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2017-02-02 (3 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IpRoute:
   default via 192.168.2.1 dev enp0s31f6  proto static  metric 100 
   169.254.0.0/16 dev enp0s31f6  scope link  metric 1000 
   192.168.2.0/24 dev enp0s31f6  proto kernel  scope link  src 192.168.2.6  
metric 100
  IwConfig:
   enp0s31f6  no wireless extensions.
   
   lono wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=51.0.1/20170201174907 (In use)
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0225
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF Z270 MARK 2
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0225:bd10/20/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFZ270MARK2:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-session/+bug/1662281/+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 1662281] Re: Firefox shows post-crash page after reboot or logoff

[Launchpad Bug Tracker]

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

** Changed in: firefox (Ubuntu)
   Status: New => Confirmed

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

Title:
  Firefox shows post-crash page after reboot or logoff

Status in gnome-session:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  When rebooting or logging off, Firefox and thinks it crashed, and
  shows the post-crash session restore  page.

  See also Mozilla bug
  https://bugzilla.mozilla.org/show_bug.cgi?id=557601 and related bugs
  there.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: firefox 51.0.1+build2-0ubuntu0.16.10.2
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  reuben 1902 F pulseaudio
   /dev/snd/controlC1:  reuben 1902 F pulseaudio
  BuildID: 20170201174907
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Mon Feb  6 16:04:15 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2017-02-02 (3 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IpRoute:
   default via 192.168.2.1 dev enp0s31f6  proto static  metric 100 
   169.254.0.0/16 dev enp0s31f6  scope link  metric 1000 
   192.168.2.0/24 dev enp0s31f6  proto kernel  scope link  src 192.168.2.6  
metric 100
  IwConfig:
   enp0s31f6  no wireless extensions.
   
   lono wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=51.0.1/20170201174907 (In use)
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0225
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF Z270 MARK 2
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0225:bd10/20/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFZ270MARK2:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-session/+bug/1662281/+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 1625846] Re: Xmir -rootless: Firefox menus pop up then close right away

[Chris Halse Rogers]

Ah, OK. We've been arguing with different assumptions.

Symptom: Firefox's menus don't work
Bug: XMir's focus behaviour differs from a spec-compliant X11 window manager.

One solution here, which is what I've been suggesting, is to implement
spec-compliant focus behaviour in XMir.

But you're correct that simply making the popups non-focusable Mir
surfaces will make XMir behave more like a spec-compliant X11 window
manager, should make it behave *enough* like a spec-compliant WM to
resolve the symptom and may well be simpler to implement. This could be
an expedient solution for the short term.

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

Title:
  Xmir -rootless: Firefox menus pop up then close right away

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Triaged
Status in MirAL:
  Confirmed
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  To reproduce:
  1) Open firefox on a rootless Xmir
  2) Right click or attempt to open the menu on the top right

  Expected:
  Menu to open

  Result:
  Menu pops up then closes right away.

  I think this is an expected bug, but dont remember the bug# soo figure
  would make one here :)

  *NOTE*: similar cause, but different usecase to lp:1662733

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625846/+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