[Desktop-packages] [Bug 1680750] Re: pm-hibernate does nothing at all

2017-06-09 Thread Launchpad Bug Tracker
[Expired for pm-utils (Ubuntu) because there has been no activity for 60
days.]

** Changed in: pm-utils (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  pm-hibernate does nothing at all

Status in pm-utils package in Ubuntu:
  Expired

Bug description:
  I have run from a command line:
  # sudo pm-hibernate

  and NOTHING f***ing happens.

  Usually it works (except for lots of issues on resume), but now I have
  tried it twice and it does nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: powerman (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr  7 10:47:47 2017
  InstallationDate: Installed on 2013-10-11 (1273 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: powerman
  UpgradeStatus: Upgraded to xenial on 2016-12-11 (116 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1680750/+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 1695928] Re: Please remove obsolete UOA packages

2017-06-09 Thread Jeremy Bicha
** Description changed:

  Ubuntu Online Accounts is no longer maintained. There is an alternative,
  GNOME Online Accounts for the GNOME desktop.
  
  Also, Unity's Online Accounts settings panel does not currently work
  without oxide-qt but oxide-qt will be removed from Ubuntu 17.10.
  
  Please remove these source packages and their binaries:
  -
  gnome-control-center-signon
  account-plugins
  account-plugin-fitbit
  account-polld
  pay-service
  qt-purchasing-opensource-src
  storage-provider-webdav
  sync-monitor
  ubuntuone-credentials
  ubuntu-push
  unity-china-photo-scope
  unity-scope-gdrive
  
  ubuntu-system-settings-online-accounts
  online-accounts-api
  storage-framework
  keeper
  mcloud
  
  ubuntu-system-settings
  address-book-app
  address-book-service
  buteo-sync-plugins-contacts-google
  camera-app
  dialer-app
  indicator-transfer
  indicator-transfer-buteo
  libertine
  messaging-app
  ubuntu-experience-tests
  unity-scopes-shell
  unity8
  
  Other Notes
  ---
  The Shotwell suggests have been dropped in artful-proposed. Shotwell is 
temporarily stuck in -proposed because of an autopkgtest issue 
https://bugzilla.gnome.org/781802
  
- Kubuntu still uses signon-ui
- 
- unity still recommends unity-scope-gdrive because it FTBFS
- https://code.launchpad.net/~jbicha/unity/drop-uoa-recommends/+merge/325097
+ Kubuntu still uses signon-ui.
  
  See also https://code.launchpad.net/~xnox/ubuntu-
  seeds/unity8-removals/+merge/323615

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

Title:
  Please remove obsolete UOA packages

Status in gnome-control-center-signon package in Ubuntu:
  New

Bug description:
  Ubuntu Online Accounts is no longer maintained. There is an
  alternative, GNOME Online Accounts for the GNOME desktop.

  Also, Unity's Online Accounts settings panel does not currently work
  without oxide-qt but oxide-qt will be removed from Ubuntu 17.10.

  Please remove these source packages and their binaries:
  -
  gnome-control-center-signon
  account-plugins
  account-plugin-fitbit
  account-polld
  pay-service
  qt-purchasing-opensource-src
  storage-provider-webdav
  sync-monitor
  ubuntuone-credentials
  ubuntu-push
  unity-china-photo-scope
  unity-scope-gdrive

  ubuntu-system-settings-online-accounts
  online-accounts-api
  storage-framework
  keeper
  mcloud

  ubuntu-system-settings
  address-book-app
  address-book-service
  buteo-sync-plugins-contacts-google
  camera-app
  dialer-app
  indicator-transfer
  indicator-transfer-buteo
  libertine
  messaging-app
  ubuntu-experience-tests
  unity-scopes-shell
  unity8

  Other Notes
  ---
  The Shotwell suggests have been dropped in artful-proposed. Shotwell is 
temporarily stuck in -proposed because of an autopkgtest issue 
https://bugzilla.gnome.org/781802

  Kubuntu still uses signon-ui.

  See also https://code.launchpad.net/~xnox/ubuntu-
  seeds/unity8-removals/+merge/323615

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1695928/+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 1697131] Re: ailed tpackage gconf2-common 3.2.6-3ubuntu7 fo install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-06-09 Thread Apport retracing service
*** This bug is a duplicate of bug 1688721 ***
https://bugs.launchpad.net/bugs/1688721

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 #1688721, 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.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1688721
   Packages that trigger multiple debconf prompts fail to install

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

Title:
  ailed tpackage gconf2-common 3.2.6-3ubuntu7 fo install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  After installing Ubuntu 17.04 and updating this occurs every time.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Sat Jun 10 15:20:55 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-10 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1697131/+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 1697131] [NEW] ailed tpackage gconf2-common 3.2.6-3ubuntu7 fo install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-06-09 Thread Jacob de Lange-Hope
*** This bug is a duplicate of bug 1688721 ***
https://bugs.launchpad.net/bugs/1688721

Public bug reported:

After installing Ubuntu 17.04 and updating this occurs every time.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Sat Jun 10 15:20:55 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-06-10 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  ailed tpackage gconf2-common 3.2.6-3ubuntu7 fo install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  After installing Ubuntu 17.04 and updating this occurs every time.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Sat Jun 10 15:20:55 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-10 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1697131/+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 1697126] [NEW] Popping sound whenever a client connects / disconnects

2017-06-09 Thread Johannes H. Jensen
Public bug reported:

I'm getting an annoying popping sound whenever pulseaudio gets a new
connection or a connection dies. This is especially annoying since
google chrome seems to open new connections rather often for no apparent
reason, interrupting music playback with glitches.

Steps to reproduce:
1. Start playback of some audio with totem or similar
2. Play a silent audio file with paplay silence.wav, I got mine from audacity
3. Observe pops in the playback from totem

Interestingly there are no pops if I use paplay instead of totem for
step 1. Attaching debug output from pulseaudio - during the
reproducer above.

My sound card is a USB DAC:

card 3: DAC [UAC1 DAC], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3.2
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC3:  joh   19113 F pulseaudio
 /dev/snd/controlC2:  joh   19113 F pulseaudio
 /dev/snd/controlC1:  joh   19113 F pulseaudio
 /dev/snd/controlC0:  joh   19113 F pulseaudio
CurrentDesktop: GNOME
Date: Sat Jun 10 04:06:46 2017
InstallationDate: Installed on 2011-10-01 (2078 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to xenial on 2016-09-18 (264 days ago)
dmi.bios.date: 09/18/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.7
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97 GAMING 5 (MS-7917)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd09/18/2014:svnMSI:pnMS-7917:pvr1.0:rvnMSI:rnZ97GAMING5(MS-7917):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7917
dmi.product.version: 1.0
dmi.sys.vendor: MSI

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


** Tags: amd64 apport-bug xenial

** Attachment added: "debug output from pulseaudio - while reproducing the 
issue"
   
https://bugs.launchpad.net/bugs/1697126/+attachment/4893344/+files/pa-popping.log

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

Title:
  Popping sound whenever a client connects / disconnects

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I'm getting an annoying popping sound whenever pulseaudio gets a new
  connection or a connection dies. This is especially annoying since
  google chrome seems to open new connections rather often for no
  apparent reason, interrupting music playback with glitches.

  Steps to reproduce:
  1. Start playback of some audio with totem or similar
  2. Play a silent audio file with paplay silence.wav, I got mine from audacity
  3. Observe pops in the playback from totem

  Interestingly there are no pops if I use paplay instead of totem for
  step 1. Attaching debug output from pulseaudio - during the
  reproducer above.

  My sound card is a USB DAC:

  card 3: DAC [UAC1 DAC], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.2
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  joh   19113 F pulseaudio
   /dev/snd/controlC2:  joh   19113 F pulseaudio
   /dev/snd/controlC1:  joh   19113 F pulseaudio
   /dev/snd/controlC0:  joh   19113 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Jun 10 04:06:46 2017
  InstallationDate: Installed on 2011-10-01 (2078 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to xenial on 2016-09-18 (264 days ago)
  dmi.bios.date: 09/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97 GAMING 5 (MS-7917)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd09/18/2014:svnMSI:pnMS-7917:pvr1.0:rvnMSI:rnZ97GAMING5(MS-7917):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7917
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

To manage notificat

[Desktop-packages] [Bug 1697122] [NEW] Package Firefox with MOZ_USE_XINPUT2=1 in environment

2017-06-09 Thread Nate Graham
Public bug reported:

Ubuntu version:  Kubuntu 17.04
Firefox version: 53.0.3+build1-0ubuntu0.17.04.2

In Firefox, two-finger scroll gestures on a touchpad are interpreted as
scroll wheel rotations, and the content scrolls three lines at a time.
This is inappropriate behavior for touchpad scrolling; it should scroll
pixel-by-pixel.

Firefox already has the ability to do this, you just need to turn it on
by running the program with MOZ_USE_XINPUT2=1 in the environment: for
example, by running `MOZ_USE_XINPUT2=1 firefox`, or adding it to
/etc/environment or something like that.

Turning on this behavior yields a large usability improvement for laptop
users. Therefore, I am proposing that MOZ_USE_XINPUT2=1 be permanently
added to the packaging such that it's always present when Firefox runs.
This is what Fedora does, and it results in a much improved experience
for the laptop user.

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

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

Title:
  Package Firefox with MOZ_USE_XINPUT2=1 in environment

Status in firefox package in Ubuntu:
  New

Bug description:
  Ubuntu version:  Kubuntu 17.04
  Firefox version: 53.0.3+build1-0ubuntu0.17.04.2

  In Firefox, two-finger scroll gestures on a touchpad are interpreted
  as scroll wheel rotations, and the content scrolls three lines at a
  time. This is inappropriate behavior for touchpad scrolling; it should
  scroll pixel-by-pixel.

  Firefox already has the ability to do this, you just need to turn it
  on by running the program with MOZ_USE_XINPUT2=1 in the environment:
  for example, by running `MOZ_USE_XINPUT2=1 firefox`, or adding it to
  /etc/environment or something like that.

  Turning on this behavior yields a large usability improvement for
  laptop users. Therefore, I am proposing that MOZ_USE_XINPUT2=1 be
  permanently added to the packaging such that it's always present when
  Firefox runs. This is what Fedora does, and it results in a much
  improved experience for the laptop user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1697122/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2017-06-09 Thread Nicholas Stommel
Unfortunately my patch is not a good solution for upstream application.
I agree with what Beniamino Galvani mentioned, that "it is wrong to
assume the connection is a VPN based on the link type, since you can
have non-VPN tun/tap/gre/gretap connections as well, and they are
affected by this patch." However, it seems that this issue with DNS
leaks over NM-VPN connections and broken VPN split-horizon DNS using
systemd-resolved still exists upstream and doesn't have a good fix.

I think this issue needs some attention and work from the Gnome-
NM/systemd/Canonical devs, I've reached my limit here. :(

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in network-manager source package in Artful:
  Confirmed
Status in systemd source package in Artful:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1624317/+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 1691420] Re: package account-plugin-google (not installed) failed to install/upgrade: trying to overwrite '/usr/share/accounts/providers/google.provider', which is also in pack

2017-06-09 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: account-plugins (Ubuntu)
   Status: New => Confirmed

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

Title:
  package account-plugin-google (not installed) failed to
  install/upgrade: trying to overwrite
  '/usr/share/accounts/providers/google.provider', which is also in
  package kaccounts-providers 4:15.12.3-0ubuntu1

Status in account-plugins package in Ubuntu:
  Confirmed

Bug description:
  Not quite sure what triggered this bug

  Description:Ubuntu 16.04.2 LTS
  Release:16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-google (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-51-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sat May 13 22:35:12 2017
  DuplicateSignature:
   package:account-plugin-google:(not installed)
   Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
trying to overwrite '/usr/share/accounts/providers/google.provider', which 
is also in package kaccounts-providers 4:15.12.3-0ubuntu1
  ErrorMessage: trying to overwrite 
'/usr/share/accounts/providers/google.provider', which is also in package 
kaccounts-providers 4:15.12.3-0ubuntu1
  InstallationDate: Installed on 2017-05-13 (4 days ago)
  InstallationMedia: Kubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: account-plugins
  Title: package account-plugin-google (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/share/accounts/providers/google.provider', which is also in package 
kaccounts-providers 4:15.12.3-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1691420/+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 1048373] Re: No option to remain in one filesystem

2017-06-09 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  No option to remain in one filesystem

Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  I used "sshfs" to mount a remote filesystem in my home directory and
  it was backed up by Deja-Dup. I should, of course, have added the
  mount-point in my home directory to the exclude list, but I didn't
  realise until the backup had been running for hours and many GB had
  been downloaded on my ADSL connection from the remote SSHFS fileserver
  I was connected to. It would be useful if there was an option for
  Deja_Dup to remain in one filesystem during a backup to avoid this
  type of problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1048373/+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 1048373] Re: No option to remain in one filesystem

2017-06-09 Thread Mike Hicks
I'm running Ubuntu 16.04.2 LTS. I noticed my laptop was running slow and
discovered that it was trying to back up files over a fuse.sshfs mount
to another machine in my apartment. This should not happen.

I'm probably going to have to disable deja-dup because of this issue and
find some other way to do backups -- the machine I was sshfs'd to is
probably where I should be sending my backups!

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

Title:
  No option to remain in one filesystem

Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  I used "sshfs" to mount a remote filesystem in my home directory and
  it was backed up by Deja-Dup. I should, of course, have added the
  mount-point in my home directory to the exclude list, but I didn't
  realise until the backup had been running for hours and many GB had
  been downloaded on my ADSL connection from the remote SSHFS fileserver
  I was connected to. It would be useful if there was an option for
  Deja_Dup to remain in one filesystem during a backup to avoid this
  type of problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1048373/+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 1594296] Re: [USB-Audio - USB Sound Device, playback] Occasional audio playback blips from Sweex 7.1 external USB card

2017-06-09 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  [USB-Audio - USB Sound Device, playback] Occasional audio playback
  blips from Sweex 7.1 external USB card

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When playing audio back (from Chrome), I get occasional blips where it
  sounds like the audio is skipping forwards or backwards.  I've
  followed the instructions at https://wiki.ubuntu.com/PulseAudio/Log to
  configure a debug log and I generally see this in the log when it
  happens:

  ( 765.763|   0.194) I: [alsa-source-ALC269VC Analog] alsa-source.c: Overrun!
  ( 767.600|   1.837) I: [alsa-sink-USB Audio] alsa-sink.c: Scheduling delay of 
361.78 ms > 15.99 ms, you might want to investigate this to improve latency...
  ( 767.600|   0.000) I: [alsa-sink-USB Audio] alsa-sink.c: Increasing minimal 
latency to 36.00 ms
  ( 767.600|   0.000) D: [alsa-sink-USB Audio] alsa-sink.c: Latency set to 
36.00ms
  ( 767.600|   0.000) D: [alsa-sink-USB Audio] alsa-sink.c: hwbuf_unused=1029528
  ( 767.600|   0.000) D: [alsa-sink-USB Audio] alsa-sink.c: setting 
avail_min=86677
  ( 767.600|   0.000) D: [alsa-sink-USB Audio] protocol-native.c: max_request 
changed, trying to update from 8680 to 10444.
  ( 767.600|   0.000) D: [alsa-sink-USB Audio] protocol-native.c: Notifying 
client about increased tlength
  ( 767.600|   0.000) D: [alsa-sink-USB Audio] alsa-sink.c: Latency set to 
36.00ms
  ( 767.600|   0.000) D: [alsa-sink-USB Audio] alsa-sink.c: hwbuf_unused=1029528
  ( 767.600|   0.000) D: [alsa-sink-USB Audio] alsa-sink.c: setting 
avail_min=86677
  ( 767.601|   0.000) D: [alsa-sink-USB Audio] protocol-native.c: Implicit 
underrun of 'Playback'
  ( 767.615|   0.014) D: [alsa-sink-USB Audio] protocol-native.c: Requesting 
rewind due to end of underrun.
  ( 767.615|   0.000) D: [alsa-sink-USB Audio] alsa-sink.c: Requested to rewind 
178188 bytes.
  ( 767.615|   0.000) D: [alsa-sink-USB Audio] alsa-sink.c: Limited to 18788 
bytes.
  ( 767.615|   0.000) D: [alsa-sink-USB Audio] alsa-sink.c: before: 1565
  ( 767.615|   0.000) D: [alsa-sink-USB Audio] alsa-sink.c: after: 1565
  ( 767.615|   0.000) D: [alsa-sink-USB Audio] alsa-sink.c: Rewound 18780 bytes.
  ( 767.615|   0.000) D: [alsa-sink-USB Audio] sink.c: Processing rewind...
  ( 767.615|   0.000) D: [alsa-sink-USB Audio] sink-input.c: Have to rewind 
18780 bytes on render memblockq.
  ( 767.615|   0.000) D: [alsa-sink-USB Audio] source.c: Processing rewind...
  ( 768.855|   1.239) I: [alsa-source-ALC269VC Analog] ratelimit.c: 85 events 
suppressed

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Jun 20 10:04:42 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-27 (53 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Device successful
  Symptom_Card: CM106 Like Sound Device - USB Sound Device
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [USB-Audio - USB Sound Device, playback] Underruns, dropouts or 
crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MMLP7AP-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd02/19/2014:svnGIGABYTE:pnMMLP7AP-00:pvr1.x:rvnGIGABYTE:rnMMLP7AP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: MMLP7AP-00
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1594296/+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 1697112] Re: package sni-qt 0.2.7+15.10.20150729-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/etc/xdg/sni-qt.conf', which is different from other instances

2017-06-09 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package sni-qt 0.2.7+15.10.20150729-0ubuntu1 failed to
  install/upgrade: trying to overwrite shared '/etc/xdg/sni-qt.conf',
  which is different from other instances of package sni-qt:amd64

Status in sni-qt package in Ubuntu:
  New

Bug description:
  Showed System error while trying to install OS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sni-qt 0.2.7+15.10.20150729-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
  Uname: Linux 4.4.0-75-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Jun  9 19:23:01 2017
  DuplicateSignature:
   package:sni-qt:0.2.7+15.10.20150729-0ubuntu1
   Unpacking sni-qt:amd64 (0.2.7+16.04.20170217.1-0ubuntu1) over 
(0.2.7+15.10.20150729-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/sni-qt_0.2.7+16.04.20170217.1-0ubuntu1_amd64.deb 
(--unpack):
trying to overwrite shared '/etc/xdg/sni-qt.conf', which is different from 
other instances of package sni-qt:amd64
  ErrorMessage: trying to overwrite shared '/etc/xdg/sni-qt.conf', which is 
different from other instances of package sni-qt:amd64
  InstallationDate: Installed on 2015-04-02 (799 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: sni-qt
  Title: package sni-qt 0.2.7+15.10.20150729-0ubuntu1 failed to 
install/upgrade: trying to overwrite shared '/etc/xdg/sni-qt.conf', which is 
different from other instances of package sni-qt:amd64
  UpgradeStatus: Upgraded to xenial on 2016-04-29 (406 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sni-qt/+bug/1697112/+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 1697112] [NEW] package sni-qt 0.2.7+15.10.20150729-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/etc/xdg/sni-qt.conf', which is different from other instance

2017-06-09 Thread AJAI KUTTIYIL
Public bug reported:

Showed System error while trying to install OS

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: sni-qt 0.2.7+15.10.20150729-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
Uname: Linux 4.4.0-75-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Fri Jun  9 19:23:01 2017
DuplicateSignature:
 package:sni-qt:0.2.7+15.10.20150729-0ubuntu1
 Unpacking sni-qt:amd64 (0.2.7+16.04.20170217.1-0ubuntu1) over 
(0.2.7+15.10.20150729-0ubuntu1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/sni-qt_0.2.7+16.04.20170217.1-0ubuntu1_amd64.deb 
(--unpack):
  trying to overwrite shared '/etc/xdg/sni-qt.conf', which is different from 
other instances of package sni-qt:amd64
ErrorMessage: trying to overwrite shared '/etc/xdg/sni-qt.conf', which is 
different from other instances of package sni-qt:amd64
InstallationDate: Installed on 2015-04-02 (799 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: sni-qt
Title: package sni-qt 0.2.7+15.10.20150729-0ubuntu1 failed to install/upgrade: 
trying to overwrite shared '/etc/xdg/sni-qt.conf', which is different from 
other instances of package sni-qt:amd64
UpgradeStatus: Upgraded to xenial on 2016-04-29 (406 days ago)

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


** Tags: amd64 apport-package package-conflict xenial

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

Title:
  package sni-qt 0.2.7+15.10.20150729-0ubuntu1 failed to
  install/upgrade: trying to overwrite shared '/etc/xdg/sni-qt.conf',
  which is different from other instances of package sni-qt:amd64

Status in sni-qt package in Ubuntu:
  New

Bug description:
  Showed System error while trying to install OS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sni-qt 0.2.7+15.10.20150729-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
  Uname: Linux 4.4.0-75-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Jun  9 19:23:01 2017
  DuplicateSignature:
   package:sni-qt:0.2.7+15.10.20150729-0ubuntu1
   Unpacking sni-qt:amd64 (0.2.7+16.04.20170217.1-0ubuntu1) over 
(0.2.7+15.10.20150729-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/sni-qt_0.2.7+16.04.20170217.1-0ubuntu1_amd64.deb 
(--unpack):
trying to overwrite shared '/etc/xdg/sni-qt.conf', which is different from 
other instances of package sni-qt:amd64
  ErrorMessage: trying to overwrite shared '/etc/xdg/sni-qt.conf', which is 
different from other instances of package sni-qt:amd64
  InstallationDate: Installed on 2015-04-02 (799 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: sni-qt
  Title: package sni-qt 0.2.7+15.10.20150729-0ubuntu1 failed to 
install/upgrade: trying to overwrite shared '/etc/xdg/sni-qt.conf', which is 
different from other instances of package sni-qt:amd64
  UpgradeStatus: Upgraded to xenial on 2016-04-29 (406 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sni-qt/+bug/1697112/+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 1199460] Re: Printing a #10 envelope truncates return address

2017-06-09 Thread peter gibson
I inserted 3 spaces into the return address field on each line to work
around it.

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

Title:
  Printing a #10 envelope truncates return address

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  This bug was first reported by me to Freedesktop (bug 37733)  because
  it only showed up when printing envelopes from LibreOffice writer.
  But we determined that it was apparently a bug in cups, not
  LibreOffice.

  Note:  it is definitely not a problem with printer margins.  In fact,
  I increased that setting, but it still truncated, only further from
  the edge.

  I believe the problem is that the printer needs to be set to a larger
  paper size for a #10 envelope; 9.5 inches vs 8.5. When I print to PDF,
  I can see both the envelope and the document, and the return address
  is truncated right about at the 8.5" edge of the document.  I've
  printed to the same printer using Windows, and noticed that it sets
  the printer to "legal"; in fact, I sometimes got annoyed that it would
  stop and prompt me to "Load legal" on the printer, and I would need to
  press the continue button, whereupon it would print the envelope with
  no problems.

  Printing to a PDF file prints normally, so I think that means the
  actual printer needs to be set.  The PDF file is the correct size, but
  even trying to print from it causes truncation unless it is printed to
  an 8.5 x 11 sheet of paper.

  I first discovered this problem a few years ago, I believe, but gave
  up trying to solve it.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: cups 1.5.3-0ubuntu8
  ProcVersionSignature: Ubuntu 3.2.0-49.75-generic 3.2.46
  Uname: Linux 3.2.0-49-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.3
  Architecture: amd64
  Date: Tue Jul  9 10:14:21 2013
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120817.1)
  Lpstat: device for Deskjet-6940-series: 
dnssd://Deskjet%206940%20series%20%5B8D699B%5D._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Papersize: letter
  PpdFiles: Deskjet-6940-series: HP Deskjet 6940 Series, hpcups 3.12.2
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-49-generic 
root=UUID=7dbc17ff-1769-46e6-9470-fe975fa71ed6 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 1604
  dmi.board.name: M2A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMACPIBIOSRevision1604:bd12/19/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  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/ubuntu/+source/cups/+bug/1199460/+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 1199460] Re: Printing a #10 envelope truncates return address

2017-06-09 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Printing a #10 envelope truncates return address

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  This bug was first reported by me to Freedesktop (bug 37733)  because
  it only showed up when printing envelopes from LibreOffice writer.
  But we determined that it was apparently a bug in cups, not
  LibreOffice.

  Note:  it is definitely not a problem with printer margins.  In fact,
  I increased that setting, but it still truncated, only further from
  the edge.

  I believe the problem is that the printer needs to be set to a larger
  paper size for a #10 envelope; 9.5 inches vs 8.5. When I print to PDF,
  I can see both the envelope and the document, and the return address
  is truncated right about at the 8.5" edge of the document.  I've
  printed to the same printer using Windows, and noticed that it sets
  the printer to "legal"; in fact, I sometimes got annoyed that it would
  stop and prompt me to "Load legal" on the printer, and I would need to
  press the continue button, whereupon it would print the envelope with
  no problems.

  Printing to a PDF file prints normally, so I think that means the
  actual printer needs to be set.  The PDF file is the correct size, but
  even trying to print from it causes truncation unless it is printed to
  an 8.5 x 11 sheet of paper.

  I first discovered this problem a few years ago, I believe, but gave
  up trying to solve it.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: cups 1.5.3-0ubuntu8
  ProcVersionSignature: Ubuntu 3.2.0-49.75-generic 3.2.46
  Uname: Linux 3.2.0-49-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.3
  Architecture: amd64
  Date: Tue Jul  9 10:14:21 2013
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120817.1)
  Lpstat: device for Deskjet-6940-series: 
dnssd://Deskjet%206940%20series%20%5B8D699B%5D._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Papersize: letter
  PpdFiles: Deskjet-6940-series: HP Deskjet 6940 Series, hpcups 3.12.2
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-49-generic 
root=UUID=7dbc17ff-1769-46e6-9470-fe975fa71ed6 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 1604
  dmi.board.name: M2A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMACPIBIOSRevision1604:bd12/19/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  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/ubuntu/+source/cups/+bug/1199460/+subscriptions

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


[Desktop-packages] [Bug 997200] Re: Add NetworkManager connectivity config package

2017-06-09 Thread Bug Watch Updater
** Changed in: network-manager (Debian)
   Status: New => Fix Released

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

Title:
  Add NetworkManager connectivity config package

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

Bug description:
  Feature
  ===
  A separate network-manager-config-connectivity package that contains the 
3-line config snippet to enable NetworkManager's connectivity check. This is 
the same approach taken by Fedora since 2014 (their package is named 
config-connectivity-fedora).

  jbicha would like to have ubuntu-gnome-desktop recommend this package for 
zesty. With this config, GNOME Shell will popup a browser page when a captive 
portal is detected. The browser page is powered by webkit2gtk.
  https://help.gnome.org/misc/release-notes/3.14/#captive-portals

  By making it a separate package, it is very easy for Ubuntu flavors to
  opt in to installing it by default if they choose. And it's very easy
  for users to opt in or out without needing to mess around with system
  configuration files.

  This new feature (and how to opt out) will be mentioned in Ubuntu
  GNOME's Release Notes.

  Enabling the connectivity check by default for all of Ubuntu was discussed 
almost 5 years ago:
  https://lists.ubuntu.com/archives/ubuntu-devel/2012-July/035490.html

  Link to new discussion:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-February/039696.html

  Git merge proposal attached.

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/997200/+subscriptions

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


[Desktop-packages] [Bug 1370720] Re: unity-settings-daemon can deadlock if a modeset fails

2017-06-09 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  unity-settings-daemon can deadlock  if a modeset fails

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

Bug description:
  The system I used to reproduce this bug was a laptop with two display
  devices (one DisplayPort, one DVI) connected to a docking station.

  Dock the laptop.  unity-settings-manager triggers a display change to
  extended mode.  Then, undock the laptop.  The following sequence of
  events triggers a deadlock:

  1. The system generates an ACPI event that video.ko turns into a display 
change hotkey press.
  2. Something sees the display change hotkey event and calls 
unity-settings-manager via dbus.
  3. The X driver sees the DVI monitor go away and updates the RandR 
configuration.
  4. unity-settings-manager enters handle_fn_f7() and calls 
gnome_rr_screen_refresh().
  5. gnome_rr_screen_refresh() sees that the configuration changed and calls 
the callbacks.
  6. The X driver sees the DP monitor go away and updates the RandR 
configuration.
  7. on_randr_event() tries to reconfigure the desktop with the DVI monitor 
disabled and the DP monitor enabled.
  8. The RandR SetCrtcConfig call fails because it's trying to set a mode on a 
disconnected output.
  9. apply_configuration() calls error_message(), which tries to pop up a 
dialog box.

  Step #9 deadlocks because gnome_rr_screen_refresh() called
  XGrabServer() in step #5.

  Upstream gnome-settings-daemon fixed this with commit 
0f7cbfed5e5e76824e057ce9c570fad66ba001c6.
  
https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=0f7cbfed5e5e76824e057ce9c570fad66ba001c6

  This change cherry-picks cleanly to unity-settings-daemon.

  (as an aside, the video.ko display change hotkey events are entirely
  pointless and probably deserve their own bug)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1370720/+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 1693715] Re: Laptop flat panel show blank screen after undocking with 2 DP displays on dock

2017-06-09 Thread Aaron Plattner
*** This bug is a duplicate of bug 1370720 ***
https://bugs.launchpad.net/bugs/1370720

** This bug has been marked a duplicate of bug 1370720
   unity-settings-daemon can deadlock  if a modeset fails

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

Title:
  Laptop flat panel show blank screen after undocking with 2 DP displays
  on dock

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

Bug description:
  Taking HP laptop and dock available with me for example, laptop has NVIDIA 
discrete gpu and proprietary driver installed -
1. connect two DP-displays to dock
2. attach system on dock and make sure all 3 displays are light up
3. undock

  You can observe blank screen on laptop's flat panel. After some
  investigation it has been found that unity-setting-daemon has grabbed
  X-server and waiting for response on error dialog box, this is
  blocking other X-clients like compiz which might be also doing
  something in response of un-dock event. See following gdb log -

  Breakpoint 1, XGrabServer (dpy=0x2193550) at GrServer.c:36
  36  LockDisplay(dpy);
  #0  XGrabServer (dpy=0x2193550) at GrServer.c:36
  #1  0x7f387a918a49 in gdk_x11_display_grab () from 
/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  #2  0x7f387cbf0a42 in gnome_rr_screen_refresh () from 
/usr/lib/libgnome-desktop-3.so.7
  #3  0x7f386191359b in handle_fn_f7 (timestamp=0, mgr=0x2187d00) at 
gsd-xrandr-manager.c:1391
  #4  gsd_xrandr_manager_2_video_mode_switch (error=0x0, timestamp=0, 
manager=0x2187d00) at gsd-xrandr-manager.c:785
  #5  handle_method_call_xrandr_2 (invocation=0x7f3868003240, 
parameters=, method_name=, manager=0x2187d00) at 
gsd-xrandr-manager.c:2567
  #6  handle_method_call (connection=, sender=, 
object_path=, interface_name=, 
method_name=, parameters=, 
invocation=0x7f3868003240, user_data=0x2187d00) at gsd-xrandr-manager.c:2596
  #7  0x7f387c21a301 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #8  0x7f387bc41ce5 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #9  0x7f387bc42048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #10 0x7f387bc4230a in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #11 0x7f387c665e25 in gtk_main () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #12 0x00403714 in main ()

  Program received signal SIGINT, Interrupt.
  0x7f387b70384d in poll () at ../sysdeps/unix/syscall-template.S:81
  81  ../sysdeps/unix/syscall-template.S: No such file or directory.
  #0  0x7f387b70384d in poll () at ../sysdeps/unix/syscall-template.S:81
  #1  0x7f387bc41fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #2  0x7f387bc4230a in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #3  0x7f387c5f6970 in gtk_dialog_run () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #4  0x7f3861911d24 in error_message (primary_text=, 
error_to_display=, secondary_text=0x0, mgr=) at 
gsd-xrandr-manager.c:1361
  #5  0x7f3861911f35 in apply_configuration 
(manager=manager@entry=0x2187d00, config=config@entry=0x25580e0, 
timestamp=timestamp@entry=1158092, show_error=show_error@entry=1, 
save_configuration=save_configuration@entry=0) at gsd-xrandr-manager.c:528
  #6  0x7f3861912e11 in auto_configure_outputs (timestamp=1158092, 
manager=0x2187d00) at gsd-xrandr-manager.c:1737
  #7  use_stored_configuration_or_auto_configure_outputs 
(manager=manager@entry=0x2187d00, timestamp=1158092) at 
gsd-xrandr-manager.c:1779
  #8  0x7f3861913cdd in on_randr_event (screen=0x21fb760, data=) at gsd-xrandr-manager.c:1837
  #9  0x7f387bf113b8 in g_closure_invoke () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #10 0x7f387bf22d3d in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #11 0x7f387bf2aa29 in g_signal_emit_valist () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #12 0x7f387bf2ace2 in g_signal_emit () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #13 0x7f387cbf0964 in ?? () from /usr/lib/libgnome-desktop-3.so.7
  #14 0x7f387cbf0a59 in gnome_rr_screen_refresh () from 
/usr/lib/libgnome-desktop-3.so.7
  #15 0x7f386191359b in handle_fn_f7 (timestamp=0, mgr=0x2187d00) at 
gsd-xrandr-manager.c:1391
  #16 gsd_xrandr_manager_2_video_mode_switch (error=0x0, timestamp=0, 
manager=0x2187d00) at gsd-xrandr-manager.c:785
  #17 handle_method_call_xrandr_2 (invocation=0x7f3868003240, 
parameters=, method_name=, manager=0x2187d00) at 
gsd-xrandr-manager.c:2567
  #18 handle_method_call (connection=, sender=, 
object_path=, interface_name=, 
method_name=, parameters=, 
invocation=0x7f3868003240, user_data=0x2187d00) at gsd-xrandr-manager.c:2596
  #19 0x7f387c21a301 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #20 0x7f387bc41ce5 in g_main_context_di

[Desktop-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack

2017-06-09 Thread Olcay Korkmaz
Hi,

is llvm-toolchain-4.0 final release looks like it's rc1

llvm-toolchain-4.0_4.0.orig is not same as llvm-4.0.0.src from llvm.org

clang version 4.0.0-1ubuntu1~16.04.1 (tags/RELEASE_400/rc1)
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin

it make is trouble like when build with 4.0.0-1ubuntu1~16.04.1

terminate called after throwing an instance of 'std::runtime_error'
  what():  Verification failed (e=9): file::write

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont2 package in Ubuntu:
  Invalid
Status in llvm-toolchain-4.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in vulkan package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xfonts-utils package in Ubuntu:
  New
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  New
Status in libdrm source package in Xenial:
  New
Status in libinput source package in Xenial:
  New
Status in libwacom source package in Xenial:
  New
Status in libxfont source package in Xenial:
  Fix Committed
Status in libxfont2 source package in Xenial:
  Fix Committed
Status in llvm-toolchain-4.0 source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  New
Status in vulkan source package in Xenial:
  New
Status in wayland source package in Xenial:
  Fix Committed
Status in x11proto-core source package in Xenial:
  Fix Committed
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.3 ***

  Revert changes to use debhelper10.

  xorg-server-hwe-16.04 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the 
unity mouse config doesn't work with -libinput.
  x-x-i-libinput needs newer libinput, which in turn needs libwacom update.

  Mesa needs llvm-4.0 and libclc, libdrm, wayland updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

  [Other information]

  build order:
  1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, 
vulkan, wayland
  2. libclc, libinput, xorg-server (build-dep libxfont1-dev)
  3. mesa, xorg-server-hwe-16.04
  4. drivers
  5. xorg-hwe-16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2017-06-09 Thread Nicholas Stommel
Actually I take that back. The issue is not fixed by the commit
referenced on https://bugzilla.gnome.org/show_bug.cgi?id=783569 as it is
already present in the current version of the network-manager. So we
still have a major problem folks.

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in network-manager source package in Artful:
  Confirmed
Status in systemd source package in Artful:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1624317/+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 1697098] [NEW] PCI/internal sound card not detected, sound no possible i don't know more.

2017-06-09 Thread stefano
Public bug reported:

sorry i dont speak inglish very well
i am italian
i want only yous my ubuntu now but the audio is not possible :(

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity:Unity7
Date: Fri Jun  9 23:14:51 2017
InstallationDate: Installed on 2017-06-09 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=it
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/30/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F.11
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 827C
dmi.board.vendor: HP
dmi.board.version: 93.22
dmi.chassis.type: 32
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.11:bd09/30/2016:svnHP:pnHPx2Detachable10-p0XX:pvr:rvnHP:rn827C:rvr93.22:cvnHP:ct32:cvrChassisVersion:
dmi.product.name: HP x2 Detachable 10-p0XX
dmi.sys.vendor: HP

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug zesty

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

Title:
  PCI/internal sound card not detected, sound no possible i don't know
  more.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  sorry i dont speak inglish very well
  i am italian
  i want only yous my ubuntu now but the audio is not possible :(

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity:Unity7
  Date: Fri Jun  9 23:14:51 2017
  InstallationDate: Installed on 2017-06-09 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827C
  dmi.board.vendor: HP
  dmi.board.version: 93.22
  dmi.chassis.type: 32
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.11:bd09/30/2016:svnHP:pnHPx2Detachable10-p0XX:pvr:rvnHP:rn827C:rvr93.22:cvnHP:ct32:cvrChassisVersion:
  dmi.product.name: HP x2 Detachable 10-p0XX
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1697098/+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 1682291] Re: obsolete drivers list may be out of date

2017-06-09 Thread Brian Murray
We should investigate ubuntu-release-upgrader to see if the code which
utilizes the obsolete driver list can be removed from it.

** Tags removed: rls-aa-incoming

** Changed in: ubuntu-release-upgrader (Ubuntu)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: ubuntu-release-upgrader (Ubuntu)
Milestone: None => ubuntu-17.08

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

Title:
  obsolete drivers list may be out of date

Status in ubuntu-drivers-common package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged

Bug description:
  ubuntu-drivers-common provides a file named obsolete which is
  presumably a list of obsolete nvidia drivers. It doesn't seem to have
  been updated recently:

   $ ls -lh /usr/share/ubuntu-drivers-common/obsolete
  -rw-r--r-- 1 root root 162 Jun 24  2011 
/usr/share/ubuntu-drivers-common/obsolete
  [  3:30PM 10459 ]  [ bdmurray@impulse:/tmp/dist-upgrader ]
   $ cat /usr/share/ubuntu-drivers-common/obsolete
  nvidia-glx
  nvidia-glx-new
  nvidia-glx-legacy
  nvidia-glx-envy
  nvidia-glx-new-envy
  nvidia-glx-legacy-envy
  nvidia-glx-177
  nvidia-glx-71
  nvidia-glx-190
  nvidia-glx-195

  Does it in fact need updating?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1682291/+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 1697093] [NEW] Black Screen after boot.

2017-06-09 Thread Abhiroj
Public bug reported:

Please bear with me as This is the last place to resolve the as I have
tried different resources available for the problem already, but with no
effect.Long story short, Ubuntu 16.04 was working fine for a long time
but since recently, It is showing up the black screen after boot.By
blank screen, I mean:-

**The Problem**:-

After Boot (i.e. after purple screen),

1. There is no mouse pointer.

2. A cursor blinks for a few seconds and screen goes 100% black but
still lit, and then after another few seconds, it goes completely dark
as if it is turned off.

3. I wait and then switch to the command-line screen or tty1 to get the
logs.

**What I have done yet**:-

1. I have updated my system, with `oibaf-drivers` but still no help.
`fglrx` is officially deprecated for Ubuntu 16.04 and `amdgpu-pro`
provided by AMD does not support AMD graphic card of my
system.Currently, the system is using(I don't whether it is perfectly
working or not) `radeon driver` (The OSS driver for AMD). For more info,
here are the specs of GPU on my system:-

Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Sun LE
[Radeon HD 8550M / R5 M230]

VGA compatible controller: Intel Corporation Haswell-ULT Integrated
Graphics Controller (rev 09)

2. `dmesg | grep -i radeon` shows no error during boot-up.

3. Running the system in `nomodeset`, which is resulting in highly poor
graphics performance. It is much deflected compared to ideal.

4. Not running the system in `nomodeset` but using `startX` in tty1, the
systemUI restarts again but `mouse pointer turns to a cross` and only
folders present on my desktop are visible, but no wallpaper can be seen,
no side-dock, no launcher (after the click) and no status bar.The
desktop is completely absent though desktop folders are visible and can
be opened.

Please suggest a solution.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-54-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
BootLog: /dev/sda11: clean, 302776/3129344 files, 2203296/12499968 blocks
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: Sat Jun 10 01:39:53 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380c]
   Subsystem: Lenovo Sun LE [Radeon HD 8550M / R5 M230] [17aa:380c]
InstallationDate: Installed on 2017-05-18 (21 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: LENOVO ACLU12
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-54-generic 
root=UUID=f693a857-8102-4f79-a16a-ad0d75fb8edc ro quiet splash nomodeset 
vt.handoff=7
Renderer: Software
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/02/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: 9ACN25WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: VIUU4
dmi.board.vendor: LENOVO
dmi.board.version: 3196STD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: INVALID
dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pnACLU12:pvrINVALID:rvnLENOVO:rnVIUU4:rvr3196STD:cvnLENOVO:ct10:cvrINVALID:
dmi.product.name: ACLU12
dmi.product.version: INVALID
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.81+git1706061830.b6f450~gd~x
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2~git1706091930.d42fc6~gd~x
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2~git1706091930.d42fc6~gd~x
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.9.99+git1705240733.d80d01~gd~x
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1706071933.6babcf~gd~x
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.15+git1704220733.a7c190~gd~x
xserver.bootTime: Sat Jun 10 01:35:56 2017
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.2

** Affects: xorg (Ubuntu)
 Importance: Undecided

[Desktop-packages] [Bug 1695112] Re: GNOME creates thumbnails that leak encrypted data under default Ubuntu configuration

2017-06-09 Thread Ben Roberts
Sure, I just did it myself.

** 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 gnome-desktop3 in Ubuntu.
https://bugs.launchpad.net/bugs/1695112

Title:
  GNOME creates thumbnails that leak encrypted data under default Ubuntu
  configuration

Status in gnome-desktop3 package in Ubuntu:
  New

Bug description:
  Tested on Ubuntu 16.04.2 LTS. Bug appears to be in libgnome-
  desktop-3-12 (3.18.2-1ubuntu1). Nautilus (1:3.18.4.is.3.14.3-0ubuntu5)
  used to confirm.

  When a user does not have an encrypted home directory, the default
  Ubuntu installation offers an encrypted Private directory for each
  user using ecryptfs. The goal, I presume, is to give the user a place
  where they can protect data from being read directly off the disk.

  This entire purpose is defeated, though, because GNOME caches
  thumbnails of files in Private. These can be detailed enough to reveal
  contents of the encrypted storage.

  To reproduce:
  1. Save an image or other thumbnail-able file directly to ~/Private. It could 
be porn, a naked selfie, ... I used the Ubuntu logo 64_logo.png from Launchpad.
  2. Open Nautilus and browse to Private. Confirm that a thumbnail is shown for 
the image.
  3. Find this file's checksum: echo -n 'file:///home/xxx/Private/64_logo.png' 
| md5sum
  4. Confirm that ~/.caches/thumbnails//.png exists and is a 
scaled-down image of the original file in Private, that has been written to 
disk outside of an encrypted location.

  If this is not a bug, I don't understand why Ubuntu would provide an
  encrypted Private directory in the first place.

  Ideally, this would be fixed by improving
  gnome_desktop_thumbnail_factory_can_thumbnail so it checks the GNOME
  Activity Journal configuration for excluded directories, and include
  ~/Private in that configuration by default. If eliminating thumbnails
  entirely impacts usability, it should be possible to make more
  extensive changes that either cache thumbnails in a location on the
  same filesystem (much like the hidden Trash directories and Windows'
  thumbnail handling) or create thumbnails without caching them to disk.

  I noticed another security problem while investigating this. libgnome-
  desktop may also be leaking thumbnail data even if a user's entire
  home folder is encrypted, through the use of a temporary file here:
  https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/vivid/gnome-
  desktop3/vivid/view/head:/libgnome-desktop/gnome-desktop-
  thumbnail.c#L1369 If /tmp is not encrypted or mounted as tmpfs, there
  is a risk of encrypted data being discovered through forensic
  investigative methods on the disk. This is probably not the only way
  encrypted home directory data can leak out to /tmp though.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1695112/+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 1697079] [NEW] glib/glib-autocleanups.h missing from package

2017-06-09 Thread mike-g2
Public bug reported:

I am trying to install R 3.3.1 from source, but it fails due to a lack
of the header file

/usr/include/glib-2.0/glib/glib-autocleanups.h

This file is found in later versions of the libglib2.0-dev but not in
version libglib2.0-dev 2.40.2-0ubuntu1 for 14.04.

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  glib/glib-autocleanups.h missing from package

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  I am trying to install R 3.3.1 from source, but it fails due to a lack
  of the header file

  /usr/include/glib-2.0/glib/glib-autocleanups.h

  This file is found in later versions of the libglib2.0-dev but not in
  version libglib2.0-dev 2.40.2-0ubuntu1 for 14.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1697079/+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 1536204] Re: alsa-utils conflicts with bareos-bat

2017-06-09 Thread ChristianEhrhardt
The conflict only needs to be resolved on one side, so by alsa-utils
being fixed the others are now "invalid"

** Changed in: bacula (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: bareos (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  alsa-utils conflicts with bareos-bat

Status in alsa-utils package in Ubuntu:
  Fix Released
Status in bacula package in Ubuntu:
  Invalid
Status in bareos package in Ubuntu:
  Invalid
Status in alsa-utils package in Debian:
  Fix Released

Bug description:
  dcarbone@paperone:~$ sudo aptitude install bareos-bconsole bareos-bat 
bareos-client bareos-tools
  bareos-bconsole è già installato e si trova alla versione richiesta (14.2.6-2)
  bareos-client è già installato e si trova alla versione richiesta (14.2.6-2)
  bareos-tools è già installato e si trova alla versione richiesta (14.2.6-2)
  bareos-bconsole è già installato e si trova alla versione richiesta (14.2.6-2)
  bareos-client è già installato e si trova alla versione richiesta (14.2.6-2)
  bareos-tools è già installato e si trova alla versione richiesta (14.2.6-2)
  I seguenti pacchetti NUOVI (NEW) saranno installati:
bareos-bat 
  0 pacchetti aggiornati, 1 installati, 0 da rimuovere e 0 non aggiornati.
  È necessario prelevare 0 B/508 kB di archivi. Dopo l'estrazione, verranno 
occupati 1.554 kB.
  (Lettura del database... 214782 file e directory attualmente installati.)
  Preparativi per estrarre .../bareos-bat_14.2.6-2_amd64.deb...
  Estrazione di bareos-bat (14.2.6-2)...
  dpkg: errore nell'elaborare l'archivio 
/var/cache/apt/archives/bareos-bat_14.2.6-2_amd64.deb (--unpack):
   tentata sovrascrittura di "/usr/share/man/man1/bat.1.gz" presente anche nel 
pacchetto alsa-utils 1.1.0-0ubuntu2
  dpkg-deb: errore: il sottoprocesso paste è stato terminato dal segnale (Pipe 
interrotta)
  Elaborazione dei trigger per doc-base (0.10.6)...
  Elaborazione dei trigger per man-db (2.7.5-1)...
  Si sono verificati degli errori nell'elaborazione:
   /var/cache/apt/archives/bareos-bat_14.2.6-2_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  Failed to perform requested operation on package.  Trying to recover:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1536204/+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 1536204] Re: alsa-utils conflicts with bareos-bat

2017-06-09 Thread ChristianEhrhardt
I came by cleaning up long time dormant bugs, this is actually already
fixed in 1.1.0-2 and thereby >=Yakkety.

** Changed in: alsa-utils (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  alsa-utils conflicts with bareos-bat

Status in alsa-utils package in Ubuntu:
  Fix Released
Status in bacula package in Ubuntu:
  Invalid
Status in bareos package in Ubuntu:
  Invalid
Status in alsa-utils package in Debian:
  Fix Released

Bug description:
  dcarbone@paperone:~$ sudo aptitude install bareos-bconsole bareos-bat 
bareos-client bareos-tools
  bareos-bconsole è già installato e si trova alla versione richiesta (14.2.6-2)
  bareos-client è già installato e si trova alla versione richiesta (14.2.6-2)
  bareos-tools è già installato e si trova alla versione richiesta (14.2.6-2)
  bareos-bconsole è già installato e si trova alla versione richiesta (14.2.6-2)
  bareos-client è già installato e si trova alla versione richiesta (14.2.6-2)
  bareos-tools è già installato e si trova alla versione richiesta (14.2.6-2)
  I seguenti pacchetti NUOVI (NEW) saranno installati:
bareos-bat 
  0 pacchetti aggiornati, 1 installati, 0 da rimuovere e 0 non aggiornati.
  È necessario prelevare 0 B/508 kB di archivi. Dopo l'estrazione, verranno 
occupati 1.554 kB.
  (Lettura del database... 214782 file e directory attualmente installati.)
  Preparativi per estrarre .../bareos-bat_14.2.6-2_amd64.deb...
  Estrazione di bareos-bat (14.2.6-2)...
  dpkg: errore nell'elaborare l'archivio 
/var/cache/apt/archives/bareos-bat_14.2.6-2_amd64.deb (--unpack):
   tentata sovrascrittura di "/usr/share/man/man1/bat.1.gz" presente anche nel 
pacchetto alsa-utils 1.1.0-0ubuntu2
  dpkg-deb: errore: il sottoprocesso paste è stato terminato dal segnale (Pipe 
interrotta)
  Elaborazione dei trigger per doc-base (0.10.6)...
  Elaborazione dei trigger per man-db (2.7.5-1)...
  Si sono verificati degli errori nell'elaborazione:
   /var/cache/apt/archives/bareos-bat_14.2.6-2_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  Failed to perform requested operation on package.  Trying to recover:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1536204/+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 977744] Re: resizing gnome-terminal windows to a bigger size take a uge time

2017-06-09 Thread Dennis Carlstrom
Here is an apport file following a 4 minute period of the window manager
being unresponsive!

** Attachment added: "bug.apport2"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/977744/+attachment/4893227/+files/bug.apport2

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

Title:
  resizing gnome-terminal windows to a bigger size take a uge time

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  resizing gnome-terminal windows to a bigger size take a uge time (5 to
  10s)

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-terminal 3.4.0.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Tue Apr 10 08:03:33 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/977744/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2017-06-09 Thread Brian Murray
** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Also affects: network-manager (Ubuntu Artful)
   Importance: Undecided
   Status: Confirmed

** Also affects: systemd (Ubuntu Artful)
   Importance: High
 Assignee: Dimitri John Ledkov (xnox)
   Status: Confirmed

** Tags removed: rls-aa-incoming

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in network-manager source package in Artful:
  Confirmed
Status in systemd source package in Artful:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1624317/+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 977744] Re: resizing gnome-terminal windows to a bigger size take a uge time

2017-06-09 Thread Dennis Carlstrom
I've noticed a condition for this bug on my system.  It only happens
when the terminal window is vertically maximized.

Steps to reproduce:

1. open terminal
2. vertically maximize
3. resize horizontally (drag window edge)

Expected behaviour:

- terminal window resizes (contents re-flow live)

Actual behaviour:

- window manager becomes unresponsive for 10-60 seconds


Distro: Ubuntu 16.04.2 LTS
gnome-terminal: 3.18.3-1ubuntu1

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

Title:
  resizing gnome-terminal windows to a bigger size take a uge time

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  resizing gnome-terminal windows to a bigger size take a uge time (5 to
  10s)

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-terminal 3.4.0.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Tue Apr 10 08:03:33 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/977744/+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 977744] Re: resizing gnome-terminal windows to a bigger size take a uge time

2017-06-09 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-terminal (Ubuntu)
   Status: New => Confirmed

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

Title:
  resizing gnome-terminal windows to a bigger size take a uge time

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  resizing gnome-terminal windows to a bigger size take a uge time (5 to
  10s)

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-terminal 3.4.0.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Tue Apr 10 08:03:33 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/977744/+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 1696395] Re: gnome-control-center crashed with SIGSEGV in um_carousel_select_item()

2017-06-09 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Confirmed

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

Title:
  gnome-control-center crashed with SIGSEGV in um_carousel_select_item()

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

Bug description:
  Test Case
  1. In a live session, open system settings
  2. Click on 'Users'

  Expected result
  The 'users' panel opens (even if I think the 'users' panel should not be 
there at all)

  Actual result
  This crash

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.24.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jun  7 10:37:41 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-09-03 (1372 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x55c78b9944f8 :  mov
0x48(%rsi),%eax
   PC (0x55c78b9944f8) ok
   source "0x48(%rsi)" (0x0048) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   um_carousel_select_item ()
   ()
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in um_carousel_select_item()
  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/gnome-control-center/+bug/1696395/+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 1697052] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-06-09 Thread Chandan Kumar Rath
*** This bug is a duplicate of bug 1688721 ***
https://bugs.launchpad.net/bugs/1688721

Public bug reported:

crashed during software update

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Wed Jun  7 06:06:58 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-06-06 (3 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  crashed during software update

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Wed Jun  7 06:06:58 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-06 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1697052/+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 1697052] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-06-09 Thread Apport retracing service
*** This bug is a duplicate of bug 1688721 ***
https://bugs.launchpad.net/bugs/1688721

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 #1688721, 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.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1688721
   Packages that trigger multiple debconf prompts fail to install

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  crashed during software update

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Wed Jun  7 06:06:58 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-06 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1697052/+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 1696594] Re: gnome-font-viewer crashed with SIGSEGV

2017-06-09 Thread Adolfo Jayme
** Information type changed from Private to Public

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

Title:
  gnome-font-viewer crashed with SIGSEGV

Status in gnome-font-viewer package in Ubuntu:
  New

Bug description:
  The viewer crashes immediately after trying to open a font file from
  the file manager.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-font-viewer 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Jun  7 17:29:50 2017
  ExecutablePath: /usr/bin/gnome-font-viewer
  InstallationDate: Installed on 2017-01-29 (129 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170118)
  ProcCmdline: /usr/bin/gnome-font-viewer --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=es_MX:es
   PATH=(custom, no user)
   LANG=es_MX.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fc08bd7f6ea:mov0x50(%r12),%rdi
   PC (0x7fc08bd7f6ea) ok
   source "0x50(%r12)" (0x00f0) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-font-viewer
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ()
   ()
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-font-viewer crashed with SIGSEGV
  UpgradeStatus: Upgraded to artful on 2017-06-04 (3 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1696594/+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 1502476] Re: Totem menubar is displayed in fullscreen mode during gnome-flaskback session

2017-06-09 Thread CenterTest
same problem on Ubuntu Studio 16.10

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

Title:
  Totem menubar is displayed in fullscreen mode during gnome-flaskback
  session

Status in totem package in Ubuntu:
  Confirmed

Bug description:
  The menubar of Totem video player doesn't hide in fullscreen mode when
  I use gnome-flashback session.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1502476/+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 1689371] Re: Update gnome-desktop3 to 3.24.2

2017-06-09 Thread Łukasz Zemczak
** Tags removed: verification-done
** Tags added: verification-done-zesty

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

Title:
  Update gnome-desktop3 to 3.24.2

Status in gnome-desktop3 package in Ubuntu:
  Fix Released
Status in gnome-desktop3 source package in Zesty:
  Fix Committed

Bug description:
  Impact
  --
  The only purpose of this update is to update the reported GNOME version 
number to 3.24.2. Since this is the last scheduled project-wide point release 
for GNOME 3.24, this should be the last update like this for Ubuntu 17.04.

  https://git.gnome.org/browse/gnome-desktop/log?h=gnome-3-24

  Test Case
  -
  Install gnome-recipes (this version is a very large download; it will be a 
smaller download in 17.10)
  Open the Recipes app. In the top bar, click the Recipes app menu and select 
About.
  Switch to the System tab. The Desktop should say "GNOME 3.24.2".

  Regression Potential
  
  There shouldn't really be a regression here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1689371/+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 1690992] Re: fix for bug #1569649 left NetworkManager-wait-online disabled on some systems

2017-06-09 Thread Łukasz Zemczak
** Tags removed: verification-done
** Tags added: verification-done-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/1690992

Title:
  fix for bug #1569649 left NetworkManager-wait-online disabled on some
  systems

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Zesty:
  Fix Committed

Bug description:
  [SRU Justification]
  While attempting to verify the usage of NetworkManager-wait-online.service in 
Ubuntu, I have discovered that while the packaging says that this service 
should be enabled (LP: #1569649), it is disabled on my machine.  I believe that 
users who have continuously upgraded their systems, including over pre-releases 
of Ubuntu, may have been left in the same situation, where 
NetworkManager-wait-online.service is inactive and their boot order is 
therefore unreliable.

  This disabled NetworkManager-wait-online due to lack of upgrade fix-up
  may explain other bug reports I've seen around NFS handling, where
  users continue to report that NFS is not correctly mounted at boot.

  Though late, a one-time upgrade fix-up is warranted so that users can
  have consistent handling of the network-online target.

  [Test case]
  1. On an affected system, run 'systemctl status NetworkManager-wait-online'.  
Observe that the unit is listed as disabled.
  2. Install network-manager from -proposed.
  3. Run 'systemctl status NetworkManager-wait-online' again and verify that 
the unit is no longer marked as disabled.
  4. Reboot and verify that the system still boots correctly.

  [Regression potential]
  Since NetworkManager-wait-online uses a 30 second timeout, services that 
depend on network-online.target should see at most a 30 second delay in 
startup.  There should be no functional regressions, only regressions in the 
speed of boot and only on systems where services have explicitly declared that 
they depend on the network and the network is not available at boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1690992/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2017-06-09 Thread Nicholas Stommel
My apologies, it seems like this issue could have already been addressed 
upstream. See https://bugzilla.gnome.org/show_bug.cgi?id=783569
Anyway, I'll see if I can backport the fix provided there and whether or not it 
works. Sorry guys :/

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1624317/+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 1630156] Re: No password needed to Log in after cancel the password and then reset again

2017-06-09 Thread Łukasz Zemczak
** Tags removed: verification-done
** Tags added: verification-done-xenial

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

Title:
  No password needed to Log in after cancel the password and then reset
  again

Status in Light Display Manager:
  Invalid
Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project trusty series:
  Confirmed
Status in OEM Priority Project xenial series:
  Confirmed
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

Bug description:
  [ Description ]

  If you use unity-control-center to set the current user from "Log in
  without a password" to having a password again, the user is not
  removed from the 'nopasswdlogin' UNIX group, and so can log in without
  a password still.

  [ Test case ]

  1. Open the dash, type "User Accounts", open the user accounts panel of 
unity-control-center.
  2. Make sure the current user (which must be an admin) is selected in the 
list of user's on the left hand side.
  3. Click "Unlock" at the top right, and enter the user's password.
  4. Click the dots to the right of "Password", to open the dialog where you 
can change the password mode.
  5. In the combo box at the top, select "Log in without a password". Save the 
dialog.
  6. Open a terminal, and execute `grep nopasswdlogin /etc/group'. Note that 
the current user is present.
  7. Re-open the password dialog as in step 4.
  8. Select "Set a password now", and set a password. Save the dialog.
  9. Open a terminal, and execute `grep nopasswdlogin /etc/group'.

  At step 9, if the bug is present then the user will still be in the
  group. If it is fixed then the user will not.

  [ Fix ]

  unity-control-center's user-accounts panel contains a codepath to call
  `passwd' directly when changing the current user's password. There's
  another path when setting the password for a different user which uses
  AccountsService. In the former codepath, the AccountsService call
  required to remove the user from `nopasswdlogin' is not executed
  (act_user_set_password_mode (..., ACT_USER_PASSWORD_MODE_REGULAR)).

  The proposed fix (in the attached MP) is to always make this call when
  setting a password, even in this passwd case.

  [ QA ]

  Run the test case above. Additionally,

   - Try to use the dialog to change passwords without unlocking it.
   - Try to change both the current and another user's password.

  Make sure the nopasswdlogin membership is right at all times and the
  new password always gets applied (e.g. try logging out and in to check
  the settings).

  [ Regression potential ]

  The fix changes a couple of things

- We now call act_user_set_password_mode () after running passwd.
- We now call act_user_set_password () before act_user_set_password_mode 
(), which is the opposite of the previous order.

  AFAIK both of these changes are fine, but we should run the QA tests
  above to get confidence that they didn't break password setting.

  [ Original description ]

  1. Go to path "System Setting --> User Accounts--> Unlock" to unlock system 
setting.
  2. Click "Password --> Action --> Log in without password -->Change to clear 
Log in password. (as doing so, the user is added to group "nopasswdlogin")
  3. Check that the user is in the nopasswdlogin group
  4. Then do the similar action "Set a password now" as the same way to set Log 
in password.
  5. Check that the user is *not* in the nopasswdlogin group.

  The key problem is: it won't remove user from nopasswdlogin in step 4.
  At step 5, you are left in the group.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1630156/+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 1645308] Re: [SRU] Backport zeromq3 4.2.0 to yakkety

2017-06-09 Thread Łukasz Zemczak
Yes, it's on my plate - that's why I didn't release the SRU yet. Just,
ugh, don't have the time to actually look into that deeper.

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

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

Title:
  [SRU] Backport zeromq3 4.2.0 to yakkety

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

Bug description:
  [Impact]

  As per product requirement, we have released a git-snapshot based pre-
  release version of zeromq3 4.2.0 to yakkety
  (4.1.5+git20160811+2fc86bc) as the upstream version was not yet
  available. The agreement was that we will release the snapshot-based
  version only if, once the official update is available we will update
  and switch.

  The rationale for this would be that the snapshot-based version is
  anyway more-or-less feature compatible with the official version. It's
  also not wise to keep shipping a snapshot for long as some bugfixes
  might be missing from the cherry-pick. The generated binaries are
  binary-compatible, with only a few new symbols exported in the main
  4.2.0 version.

  [Test Case]

  No particular test-case - installing the new version and making sure
  that existing reverse-dependencies still work as intended.

  [Regression Potential]

  There is, of course, some regression potential, but as already
  mentioned: there weren't too many commits since the git snapshot that
  our previous version was based off.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1645308/+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 1631763] Re: Ubuntu needs a GPU accelerated browser

2017-06-09 Thread Michel-Ekimia
Really good news for firefox VP9+EME is really a great choice for
publishers.

But still software decoded ...

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

Title:
  Ubuntu needs a GPU accelerated browser

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  We all know the Web support of an operating system is becoming more
  and more important for users.

  The situation right now in terms of browser Performance and power
  consumption of GNU/Linux is not really in a good shape compared to the
  2 other competitors : Windows and Mac OSX.

  Windows 10 : Microsoft has shown how its integrated browser is more
  efficient and less hungry on power consumption than other browsers.

  Mac OSX: Safari is also showing a great power consumption and
  integrated features.

  SO this bug is to track progress for an integrated browser for Ubuntu
  ( can be firefox, chromium, something else ) that would out of the box
  :

  - Use GPU for video decoding

  - Use GPU for Web 3D rendering like webGL

  - integrate as much as possible EME HTML5 for DRM support (like
  firefox 49 for netflix)

  Please suggest other features in the comments

  -- Chromium --

  For chromium we track progress on
  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bug/1424201

  -- Firefox --

  Firefox video decode progress should be tracked here :
  https://bugzilla.mozilla.org/show_bug.cgi?id=563206

  Firefox overlay support here
  https://bugzilla.mozilla.org/show_bug.cgi?id=495727

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1631763/+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 1686189] Re: External monitor connecting problem on Intel graphics card

2017-06-09 Thread Shay Perlstein
NVidia setup is also including a second intel card (for power saving
mode), but yes I mainly try to use NVidia profile (kernel used to
complain about the intel card just like it is in your case).

Secondly not only 4.4.0-72-generic is working also 4.10.1-041001-generic
does very good job.

As for last, as mentioned above I also use the DELL dock.

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

Title:
  External monitor connecting problem on Intel graphics card

Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am facing a problem with Intel Graphics driver. I have external
  monitor and in display settings the second monitor is detecting but
  it's not working, so could you email me a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.25-040425-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  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 Apr 25 21:45:16 2017
  DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
  InstallationDate: Installed on 2017-04-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 03JPPR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 3537
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 25 21:37:24 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+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 560571] Re: BUG: using smp_processor_id() in preemptible [00000000] code: Xorg/1157

2017-06-09 Thread fs
Hi there!

A little bit late!
SOLUTION:


--- firegl_public.c.modified2017-06-09 16:41:29.334991812 +0200
+++ firegl_public.c 2017-06-08 18:25:25.835817920 +0200
@@ -4273,8 +4273,8 @@
 {
 unsigned long orig_level;
 
-orig_level = __get_cpu_var(kasExecutionLevel);
-__get_cpu_var(kasExecutionLevel) = level;
+orig_level = __raw_get_cpu_var(kasExecutionLevel);
+__raw_get_cpu_var(kasExecutionLevel) = level;
 
 return orig_level;
 }
@@ -4286,7 +4286,7 @@
  */
 static unsigned long kas_GetExecutionLevel(void)
 {
-return __get_cpu_var(kasExecutionLevel);
+return __raw_get_cpu_var(kasExecutionLevel);
 }
 
 /** \brief Type definition for kas_spin_lock() parameter */
@@ -4440,7 +4440,7 @@
 KCL_DEBUG5(FN_FIREGL_KAS,"0x%08X, 0x%08X\n", ih_routine, ih_context);
 
 //Prevent simultaneous entry on some SMP systems.
-if (test_and_set_bit(0, (void 
*)&(kasContext.in_interrupts[smp_processor_id()])))
+if (test_and_set_bit(0, (void 
*)&(kasContext.in_interrupts[raw_smp_processor_id()])))
 {
 KCL_DEBUG1(FN_FIREGL_KAS, "The processor is handling the interrupt\n");
 return IRQ_NONE;
@@ -4455,7 +4455,7 @@
 kasSetExecutionLevel(orig_level);
 spin_unlock(&kasContext.lock_ih); 
 
-clear_bit(0, (void *)&(kasContext.in_interrupts[smp_processor_id()]));
+clear_bit(0, (void *)&(kasContext.in_interrupts[raw_smp_processor_id()]));
 KCL_DEBUG5(FN_FIREGL_KAS,"%d\n", ret);
 
 return ret;


bye
masta

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

Title:
  BUG: using smp_processor_id() in preemptible [] code:
  Xorg/1157

Status in fglrx-installer package in Ubuntu:
  Confirmed

Bug description:
  Sorry, I do not know.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 10.04
  Package: linux-image-2.6.32-19-preempt 2.6.32-19.28
  Regression: No
  Reproducible: No
  ProcVersionSignature: Ubuntu 2.6.32-19.28-preempt 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-19-preempt x86_64
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Annotation: Your system might become unstable now and might need to be 
restarted.
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  iv 1294 F pulseaudio
   /dev/snd/pcmC0D0p:   iv 1294 F...m pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfc50 irq 22'
 Mixer name : 'IDT 92HD73C1X5'
 Components : 'HDA:111d7675,1028029f,00100103'
 Controls  : 16
 Simple ctrls  : 10
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfc01 irq 17'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,0010'
 Controls  : 4
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Fri Apr  9 22:14:26 2010
  Failure: oops
  Frequency: Once a day.
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
  MachineType: Dell Inc. Studio 1537
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-preempt 
root=UUID=41966431-d8b1-4025-8d7d-6ab3f465760e ro vga=771 quiet splash
  RelatedPackageVersions: linux-firmware 1.33
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: BUG: using smp_processor_id() in preemptible [] code: Xorg/1157
  dmi.bios.date: 05/27/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0P132H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/27/2009:svnDellInc.:pnStudio1537:pvrA09:rvnDellInc.:rn0P132H:rvrA09:cvnDellInc.:ct8:cvrA09:
  dmi.product.name: Studio 1537
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/560571/+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 1696876] Re: Epson Stylus Photo 1390 driver missing in CUPS

2017-06-09 Thread Till Kamppeter
We cannot fix anything here as the problem is simply a printer model
without driver support under Linux.

** Changed in: cups (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: gutenprint (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Epson Stylus Photo 1390 driver missing in CUPS

Status in CUPS:
  New
Status in Gutenprint:
  New
Status in cups package in Ubuntu:
  Invalid
Status in gutenprint package in Ubuntu:
  Invalid

Bug description:
  I have a Epson Stylus Photo 1390 printer and I installed Ubuntu, CUPS, 
cups-driver-gutenprint, but 
   still no PPD for this printer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1696876/+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 1696876] Re: Epson Stylus Photo 1390 driver missing in CUPS

2017-06-09 Thread Till Kamppeter
Extracting PPDs from Windows/Mac drivers does not work for non-
PostScript printers, as the drivers also contain proprietary filters.

If Epson does not provide Linux drivers for this model, as they do for
many other printers, you are out of luck.

Another possibility to get your printer to work is to check whether it
allows driverless printing. In this case a print queue would get
automatically set up in Ubuntu 17.04 (Zesty). This is usually only
available on very recent models with network (Ethernet or WiFi) support.

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

Title:
  Epson Stylus Photo 1390 driver missing in CUPS

Status in CUPS:
  New
Status in Gutenprint:
  New
Status in cups package in Ubuntu:
  Invalid
Status in gutenprint package in Ubuntu:
  Invalid

Bug description:
  I have a Epson Stylus Photo 1390 printer and I installed Ubuntu, CUPS, 
cups-driver-gutenprint, but 
   still no PPD for this printer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1696876/+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 1696876] Re: Epson Stylus Photo 1390 driver missing in CUPS

2017-06-09 Thread Yoshiba
@wgrant 
I have a Epson Stylus photo 1390 printer and I installed CUPS and 
cups-driver-gutenprint, but no PPD driver is available for this printer. 
The official Windows (x64 & X86) and Mac OS X driver is attached below.
http://www.epson.cn/resource/Download/Service/driver/Inkjet/SP1390/SP1390_x64_651CN_s.exe
http://www.epson.cn/resource/Download/Service/driver/Inkjet/SP1390/SP1390_W2K_651CN_s.exe
http://www.epson.cn/store/downloads/200987102327.dmg
Not sure how to extract the correct PPD file for this printer. Need help here.

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

Title:
  Epson Stylus Photo 1390 driver missing in CUPS

Status in CUPS:
  New
Status in Gutenprint:
  New
Status in cups package in Ubuntu:
  Incomplete
Status in gutenprint package in Ubuntu:
  Incomplete

Bug description:
  I have a Epson Stylus Photo 1390 printer and I installed Ubuntu, CUPS, 
cups-driver-gutenprint, but 
   still no PPD for this printer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1696876/+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 1696876] Re: Epson Stylus Photo 1390 driver missing in CUPS

2017-06-09 Thread Yoshiba
Maybe we can extract the PPD driver from Mac OSX driver, but I don`t
know how. Need some help here.

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

Title:
  Epson Stylus Photo 1390 driver missing in CUPS

Status in CUPS:
  New
Status in Gutenprint:
  New
Status in cups package in Ubuntu:
  Incomplete
Status in gutenprint package in Ubuntu:
  Incomplete

Bug description:
  I have a Epson Stylus Photo 1390 printer and I installed Ubuntu, CUPS, 
cups-driver-gutenprint, but 
   still no PPD for this printer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1696876/+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 1695742] Re: Fn keys recognised but not handled after 17.04 upgrade

2017-06-09 Thread Donjan Rodic
Update: the Unity session as well as the sessions from the packages 
ubuntu-mate-desktop and cinnamon-desktop correctly handle all Fn keys.
I'm stuck with Cinnamon for now.

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

Title:
  Fn keys recognised but not handled after 17.04 upgrade

Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  Ubuntu 17.04 amd64 upgraded from 16.10 on a Thinkpad T460p, gnome-
  flashback Compiz session.

  The Fn keys (media keys, brightness, XF86Search, etc.) have stopped working: 
all except XF86WLAN, which manages to toggle the wireless state, do nothing.
  They are visible in xev:

  KeyPress event, serial 62, synthetic NO, window 0x4e1,
  root 0xf8, subw 0x4e2, time 34775899, (50,45), root:(51,102),
  state 0x2010, keycode 123 (keysym 0x1008ff13, XF86AudioRaiseVolume), 
same_screen YES,
  XLookupString gives 0 bytes: 
  XmbLookupString gives 0 bytes: 
  XFilterEvent returns: False

  and others like XF86AudioMute, XF86MonBrightnessUp, etc. neither
  affect the hardware nor show a notification.

  I can change the brightness through
  /sys/class/backlight/intel_backlight/brightness
  or with the System Settings -> Power -> Screen Brightness slider, and 
changing audio with the applet works too, so the drivers/modules appear to 
function well, but the events are not handled presumably by g-s-d (?).

  In System Settings -> Keyboard the shortcut for e.g. Volume Down is
  set to "Audio lower volume", and resetting to default as well as
  setting it via the keyboard doesn't change the situation.

  dmesg and journalctl -f are coming up empty (except for the correctly
  working XF86WLAN).

  I'd rather have this work properly instead of keybinding to amixer
  (with manually sent osd) or brightness file writing...

  Any suggestions?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-settings-daemon 3.24.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Sun Jun  4 15:09:04 2017
  InstallationDate: Installed on 2016-10-25 (221 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to zesty on 2017-05-31 (3 days ago)
  mtime.conffile..etc.xdg.autostart.gnome-settings-daemon.desktop: 
2017-05-31T23:37:45.416621
  
mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.A11yKeyboard.desktop:
 2017-05-31T23:37:45.416621
  
mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.A11ySettings.desktop:
 2017-05-31T23:37:45.416621
  mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.Clipboard.desktop: 
2017-05-31T23:37:45.416621
  mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.Color.desktop: 
2017-05-31T23:37:45.416621
  mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.Datetime.desktop: 
2017-05-31T23:37:45.416621
  
mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.Housekeeping.desktop:
 2017-05-31T23:37:45.416621
  mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.Keyboard.desktop: 
2017-05-31T23:37:45.416621
  mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.MediaKeys.desktop: 
2017-05-31T23:37:45.416621
  mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.Mouse.desktop: 
2017-05-31T23:37:45.416621
  
mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.Orientation.desktop: 
2017-05-31T23:37:45.416621
  mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.Power.desktop: 
2017-05-31T23:37:45.416621
  
mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.PrintNotifications.desktop:
 2017-05-31T23:37:45.416621
  mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.Rfkill.desktop: 
2017-05-31T23:37:45.416621
  
mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.ScreensaverProxy.desktop:
 2017-05-31T23:37:45.416621
  mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.Sharing.desktop: 
2017-05-31T23:37:45.416621
  mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.Smartcard.desktop: 
2017-05-31T23:37:45.416621
  mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.Sound.desktop: 
2017-05-31T23:37:45.416621
  mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.Wacom.desktop: 
2017-05-31T23:37:45.416621
  mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.XRANDR.desktop: 
2017-05-31T23:37:45.416621
  mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.XSettings.desktop: 
2017-05-31T23:37:45.416621

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

-- 
Mailing list: https://launchpad.net/~desktop-packages

[Desktop-packages] [Bug 1695253] Re: Archive Manager hangs Mouse clicks

2017-06-09 Thread Marc Deslauriers
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  Archive Manager hangs Mouse clicks

Status in file-roller package in Ubuntu:
  New
Status in pcmanfm package in Ubuntu:
  New

Bug description:
  Lubuntu. Dragging a file out of bzipped file-roller Archive Manager 3.16.5 
zipped window into a standard directory window to unpack it into that directory 
will sometimes hang the Mouse clicking FOR ALL PROCESSES, starting with 
MouseUp, which effectively renders the computer useless.  Mouse tracks but 
cursor icon is wedged to close-fist dragging icon.  No Mouse clicks means can't 
mouse on anything else to change focus, can't run anything else.  File does not 
unpack since MouseUp never was heard. 
   Keyboard still seems to work, can at least hit Cntrl-Alt-Del to get process 
menu, but unclear what to do from there.

  Best guess is this happens when the mouse flies over one of the menu
  items on the left side of the file window (PCManFM using LibFM 1.2.4),
  thereby fumbling which process is listening for MouseUp.  Next best
  guess is it has to do with the file menu overlapping the right edge of
  the screen.

  This bug is a showstopper, as I have to reboot my machine to continue.
  Suggestions on workarounds solicited.

  This bug could in theory be used to disable someone's computer.

  This bug is at least a few years old, but still occurs in the latest
  version.

  Lubuntu version Ubuntu 16.04.2 LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: file-roller 3.16.5-0ubuntu1.2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Jun  2 06:46:29 2017
  InstallationDate: Installed on 2017-02-23 (99 days ago)
  InstallationMedia: Lubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  SourcePackage: file-roller
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1695253/+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 1695707] Re: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-06-09 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
   I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic i686
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  Date: Sun Jun  4 08:48:27 2017
  DpkgHistoryLog:
   Start-Date: 2017-06-04  08:46:29
   Commandline: aptdaemon role='role-commit-packages' sender=':1.106'
   Upgrade: libldap-2.4-2:i386 (2.4.42+dfsg-2ubuntu3.1, 
2.4.42+dfsg-2ubuntu3.2), isc-dhcp-common:i386 (4.3.3-5ubuntu12.6, 
4.3.3-5ubuntu12.7), libsndfile1:i386 (1.0.25-10, 1.0.25-10ubuntu0.16.04.1), 
isc-dhcp-client:i386 (4.3.3-5ubuntu12.6, 4.3.3-5ubuntu12.7)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2013-04-23 (1502 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-10-05 (241 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1695707/+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 1696304] Re: package libsane:amd64 1.0.25+git20150528-1ubuntu2.16.10.1 failed to install/upgrade: package libsane:amd64 1.0.25+git20150528-1ubuntu2.16.10.1 cannot be configured

2017-06-09 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libsane:amd64 1.0.25+git20150528-1ubuntu2.16.10.1 failed to
  install/upgrade: package libsane:amd64
  1.0.25+git20150528-1ubuntu2.16.10.1 cannot be configured because
  libsane:i386 is at a different version (1.0.25+git20150528-1ubuntu2)

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I don't know about this I am getting notified only about the bug
  rather than getting to know about the big

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libsane:amd64 1.0.25+git20150528-1ubuntu2.16.10.1
  ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Mon Jun  5 09:37:28 2017
  DuplicateSignature:
   package:libsane:amd64:1.0.25+git20150528-1ubuntu2.16.10.1
   Unpacking libsane-common (1.0.25+git20150528-1ubuntu2.16.10.1) over 
(1.0.25+git20150528-1ubuntu2) ...
   dpkg: error processing package libsane:amd64 (--configure):
package libsane:amd64 1.0.25+git20150528-1ubuntu2.16.10.1 cannot be 
configured because libsane:i386 is at a different version 
(1.0.25+git20150528-1ubuntu2)
  ErrorMessage: package libsane:amd64 1.0.25+git20150528-1ubuntu2.16.10.1 
cannot be configured because libsane:i386 is at a different version 
(1.0.25+git20150528-1ubuntu2)
  InstallationDate: Installed on 2017-03-29 (70 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.3
  SourcePackage: sane-backends
  Title: package libsane:amd64 1.0.25+git20150528-1ubuntu2.16.10.1 failed to 
install/upgrade: package libsane:amd64 1.0.25+git20150528-1ubuntu2.16.10.1 
cannot be configured because libsane:i386 is at a different version 
(1.0.25+git20150528-1ubuntu2)
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1696304/+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 1695769] Re: computer was hacked and now I can't reset admin password and don't know what it was changed to! I can't install or update any software. Please help. Thank you.

2017-06-09 Thread Marc Deslauriers
Thanks for your comments. This does not appear to be a bug report and we
are closing it. We appreciate the difficulties you are facing, but it
would make more sense to raise your question in the support tracker.
Please visit https://answers.launchpad.net/ubuntu/+addquestion

** Information type changed from Private Security to Public

** Changed in: firefox (Ubuntu)
   Status: New => Invalid

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

Title:
  computer was hacked and now I can't reset admin password and don't
  know what it was changed to!  I can't install or update any software.
  Please help.  Thank you.

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Hi Ubuntu,

  My computer was hacked and now I can't reset admin password and don't
  know what it was changed to!  I can't install or update any software
  because it asks for a password.

  Please help.  Thank you.

  Robin

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 53.0.3+build1-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  computer-user   1344 F pulseaudio
  BuildID: 20170524180630
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Sun Jun  4 15:34:32 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 2016-11-10 (206 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.1.1 dev enp3s0  proto static  metric 100 
   169.254.0.0/16 dev enp3s0  scope link  metric 1000 
   192.168.1.0/24 dev enp3s0  proto kernel  scope link  src 192.168.1.160  
metric 100
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=53.0.3/20170524180630 (In use)
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.6
  dmi.board.name: 0RF705
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF705:rvr:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 745
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1695769/+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 1696304] Re: package libsane:amd64 1.0.25+git20150528-1ubuntu2.16.10.1 failed to install/upgrade: package libsane:amd64 1.0.25+git20150528-1ubuntu2.16.10.1 cannot be configured

2017-06-09 Thread Marc Deslauriers
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package libsane:amd64 1.0.25+git20150528-1ubuntu2.16.10.1 failed to
  install/upgrade: package libsane:amd64
  1.0.25+git20150528-1ubuntu2.16.10.1 cannot be configured because
  libsane:i386 is at a different version (1.0.25+git20150528-1ubuntu2)

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I don't know about this I am getting notified only about the bug
  rather than getting to know about the big

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libsane:amd64 1.0.25+git20150528-1ubuntu2.16.10.1
  ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Mon Jun  5 09:37:28 2017
  DuplicateSignature:
   package:libsane:amd64:1.0.25+git20150528-1ubuntu2.16.10.1
   Unpacking libsane-common (1.0.25+git20150528-1ubuntu2.16.10.1) over 
(1.0.25+git20150528-1ubuntu2) ...
   dpkg: error processing package libsane:amd64 (--configure):
package libsane:amd64 1.0.25+git20150528-1ubuntu2.16.10.1 cannot be 
configured because libsane:i386 is at a different version 
(1.0.25+git20150528-1ubuntu2)
  ErrorMessage: package libsane:amd64 1.0.25+git20150528-1ubuntu2.16.10.1 
cannot be configured because libsane:i386 is at a different version 
(1.0.25+git20150528-1ubuntu2)
  InstallationDate: Installed on 2017-03-29 (70 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.3
  SourcePackage: sane-backends
  Title: package libsane:amd64 1.0.25+git20150528-1ubuntu2.16.10.1 failed to 
install/upgrade: package libsane:amd64 1.0.25+git20150528-1ubuntu2.16.10.1 
cannot be configured because libsane:i386 is at a different version 
(1.0.25+git20150528-1ubuntu2)
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1696304/+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 1695707] Re: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-06-09 Thread Marc Deslauriers
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
   I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic i686
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  Date: Sun Jun  4 08:48:27 2017
  DpkgHistoryLog:
   Start-Date: 2017-06-04  08:46:29
   Commandline: aptdaemon role='role-commit-packages' sender=':1.106'
   Upgrade: libldap-2.4-2:i386 (2.4.42+dfsg-2ubuntu3.1, 
2.4.42+dfsg-2ubuntu3.2), isc-dhcp-common:i386 (4.3.3-5ubuntu12.6, 
4.3.3-5ubuntu12.7), libsndfile1:i386 (1.0.25-10, 1.0.25-10ubuntu0.16.04.1), 
isc-dhcp-client:i386 (4.3.3-5ubuntu12.6, 4.3.3-5ubuntu12.7)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2013-04-23 (1502 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-10-05 (241 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1695707/+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 1696903] Re: 3d hardware problem

2017-06-09 Thread Marc Deslauriers
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  3d hardware problem

Status in xorg package in Ubuntu:
  New

Bug description:
  Requested size (3200, 1080) exceeds 3D hardware limit (2048, 2048).
  You must either rearrange the displays so that they fit within a (2048, 2048) 
square.
  
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code3: 
Requested size (3200, 1080) exceeds 3D hardware limit (2048, 2048).
  You must either rearrange the displays so that they fit within a (2048, 2048) 
square.
  this is showing when trying to connect to tv

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  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: Thu Jun  8 21:55:17 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobile 945GM/GMS, 943/940GML Express 
Integrated Graphics Controller [103c:30bb]
 Subsystem: Hewlett-Packard Company Mobile 945GM/GMS/GME, 943/940GML 
Express Integrated Graphics Controller [103c:30bb]
  InstallationDate: Installed on 2017-06-07 (1 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Hewlett-Packard HP Pavilion dv6000 (RU696UA#ABL)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=01be26e4-ea37-4e70-9440-06c51957e7bb ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.2E
  dmi.board.name: 30BB
  dmi.board.vendor: Quanta
  dmi.board.version: 66.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.2E:bd03/22/2010:svnHewlett-Packard:pnHPPaviliondv6000(RU696UA#ABL):pvrRev1:rvnQuanta:rn30BB:rvr66.42:cvnQuanta:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6000 (RU696UA#ABL)
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Jun  8 21:19:32 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13125 
   vendor SEC
  xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1696903/+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 1692477] Re: Thunderbird 52.1.1 no longer able to see remotely mounted folders

2017-06-09 Thread Jon
This looks very much like https://bugs.launchpad.net/bugs/1694129 which
I raised a week ago.

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

Title:
  Thunderbird 52.1.1 no longer able to see remotely mounted folders

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Since the upgrade of Thunderbird to 52.1.1 remotely mounted folders no
  longer show up in the attach dialog window.

  
  - What is happening

  In nautilus mount a folder ("Connect to Server") from a remote server
  - smb:// or ssh:// are the two I have tried.

  Start a new email and go to attach a file from the remote folder.  The
  shared folder is not visible in the attach file dialog but is visible
  in nautilus

  
  - What should happen

  In nautilus mount a folder ("Connect to Server") from a remote server
  - smb:// or ssh:// are the two I have tried.

  Start a new email and go to attach a file from the remote folder.  I
  can see the remote folder from the attach file dialog.

  
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  Codename: xenial

  
  $ apt-cache policy thunderbird
  thunderbird:
Installed: 1:52.1.1+build1-0ubuntu0.16.04.1
Candidate: 1:52.1.1+build1-0ubuntu0.16.04.1
Version table:
   *** 1:52.1.1+build1-0ubuntu0.16.04.1 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:38.6.0+build1-0ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1692477/+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 1694129] Re: Cannot attach Network Shares in Thunderbird

2017-06-09 Thread Ingo Haase
See also Bug #1692477, seems to be the same.

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

Title:
  Cannot attach Network Shares in Thunderbird

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Suddenly (and I'm not sure if this was after a recent Ubuntu update or
  a Thunderbird one, Thunderbird no longer shows "Network" locations in
  the 'Attach File(s)' window. Normally below "Bookmarks" is another
  section "Network" which shows my network locations, however this
  entire section is now missing.

  There is now no way of attaching a file existing anywhere on the
  network to an outgoing email. Nautilus can see and access all the
  network locations 100% fine. Drag/drop into the outgoing email from
  Nautilus will attach a network file to the email but Thunderbird
  refuses to send it and throws up a "Send Message Error":

  Sending of the message failed.
  There was an error attaching smb://mypc/my documents/myfolder/file.xls. 
Please check that you have access to the file.

  Attaching network files in Thunderbird and on Ubuntu 14.04 has worked
  fine for two years. I'm a "user" and really not that au-fait with the
  inner workings of Linux so I hope this helps.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: thunderbird 1:52.1.1+build1-0ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 3.13.0-119.166-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-119-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jon2048 F pulseaudio
  BuildID: 20170512195315
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Sun May 28 15:09:59 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 2014-12-10 (900 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.7  metric 9
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=52.1.1/20170512195315 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 08/08/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X551CA.202
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X551CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX551CA.202:bd08/08/2013:svnASUSTeKCOMPUTERINC.:pnX551CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X551CA
  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/thunderbird/+bug/1694129/+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 1656065] Re: Firefox and plugin-container (Chrome_ChildThr): segfault at 0 ip, sp error 6 in plugin-container/libxul.so

2017-06-09 Thread Walter Garcia-Fontes
Ignore my comment #12, just got the Firefox freeze using the
4.10.0-22-generic kernel.

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

Title:
  Firefox and plugin-container (Chrome_ChildThr): segfault at 0 ip, sp
  error 6 in plugin-container/libxul.so

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Hello.

  Some days ago, Firefox unexpectedly has been closed after a couple of
  hours (mostly viewed: YouTube and some other websites). Next, a dialog
  box related to the Mozilla Crash Reporter appeared - with message,
  that reporter is disabled (which I did earlier via 'about:config' and
  *datareporting.healthreport.service.enabled* key set to _false_) and
  no crash report is available even via 'about:crashes' etc.

  After this situation two entries appeared in the log files: first
  related to the AppArmor and second: plugin-container segfault. By the
  way: in the same time there was an update for flash-plugin available
  (see: 1).

  Anyway, 'LastCrash' file (which can be found in
  ~/.mozilla/firefox/Crash Reports/ directory) contains only:
  1484142985. Just like all the others files in this directory. There
  are also two folders called: 'events' and 'pending'. But they are
  completely empty. However, system log files, such as
  '/var/log/kern.log' or '/var/log/syslog', contains an interesting
  entries:

  ● Jan 11 14:56:25 t4 kernel: [ 4161.295639] type=1400
  audit(1484142985.517:46): apparmor="DENIED" operation="open"
  parent=2818 profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
  name="/proc/2818/task/" pid=3253 comm="firefox" requested_mask="r"
  denied_mask="r" fsuid=1000 ouid=1000

  ● Jan 11 14:56:25 t4 kernel: [ 4161.540727] Chrome_ChildThr[2890]:
  segfault at 0 ip b76df673 sp b1efe9f0 error 6 in plugin-
  container[b76d8000+42000]

  As we know, thanks to the plugin-container, plugins are separated from
  the browser process, making it more stable, right? So now if a plugin
  crashes, Firefox should remains unharmed. It looks like this is a
  known problem (see: 2, 3).

  By the way; on Moday, 16 January, Firefox has been closed again - no
  action from my side. Log files contain the same entries as above:

  ● Jan 16 16:39:35 t4 kernel: [14373.711834] type=1400
  audit(1484581175.931:48): apparmor="DENIED" operation="open"
  parent=2532 profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
  name="/proc/2532/task/" pid=3389 comm="firefox" requested_mask="r"
  denied_mask="r" fsuid=1000 ouid=1000

  ● Jan 16 16:39:36 t4 kernel: [14373.934394] Chrome_ChildThr[3041]:
  segfault at 0 ip b76f8673 sp b1efe9f0 error 6 in plugin-
  container[b76f1000+42000]

  Anyway, after adding these two rules to the Firefox profile,
  everything seems to be OK and there is not DENIED message for
  "/proc/*/task/" entry anymore (so the first issue is solved):

  owner @{PROC}/[0-9]*/task/ r,
  owner @{PROC}/[0-9]*/task/* r,

  NOTE: This problem occurs when adobe-flash plugin is not activated and
  is permanently disabled and also when is used/enabled. Here are some
  informations about versions etc.:

  ● Firefox: 50.1.0
  ● Flash: 24.0.0.194ubuntu0.12.04.1
  ● Linux: 3.2.0-120-generic-pae (3.2.79) i686
  ● AppArmor: 2.7.102-0ubuntu3.10
  ● Release: 12.04.5 LTS (via `lsb_release -a` command)

  Best regards.
  _
  [1] https://lists.ubuntu.com/archives/precise-changes/2017-January/026047.html
  [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1205199
  [3] https://bugzilla.redhat.com/show_bug.cgi?id=1253086

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1656065/+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 1696967] [NEW] /usr/sbin/cups-browsed:11:resolve_callback:avahi_service_resolver_event:filter_func:dbus_connection_dispatch:dispatch_timeout_callback

2017-06-09 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
cups-filters.  This problem was most recently seen with package version 
1.14.0-1, the problem page at 
https://errors.ubuntu.com/problem/abe792470802e163d7c9f9729e4b00dec9c69457 
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: cups-filters (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful

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

Title:
  /usr/sbin/cups-
  
browsed:11:resolve_callback:avahi_service_resolver_event:filter_func:dbus_connection_dispatch:dispatch_timeout_callback

Status in cups-filters package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
cups-filters.  This problem was most recently seen with package version 
1.14.0-1, the problem page at 
https://errors.ubuntu.com/problem/abe792470802e163d7c9f9729e4b00dec9c69457 
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/cups-filters/+bug/1696967/+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 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

2017-06-09 Thread Zhanglei Mao
This is mail thread we haved discussed about ARM to compliance for PCI
standard as other platform for x86, powerpc, ia64 etc. They key point
form Huawei guys are below:

"这部分ARM应该不能遵循,因为VGA
EN开辟的空间是给legacy的系统使用的,1M以下的空间划分是x86向前兼容性的做法,只有在CSM支持传统的系统才还这样做,在新的方案里能不用就不用,开辟IO空间对ARM来说更不合适,因为ARM在定义之初就没有IO这种资源类型。"

Translate: ARM would compliance this part of PCI stand (IO space, memory
address space), because VGA EN reserved spaces for only for legacy
system. The low space for 1M is to compatible X86, it only used from
CSM. In new implement, it need to avoid at best, to use IO space is also
not suitable for ARM because ARM didn't have any IO resource in its'
initial definitions.


thanks,
Mao

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

Title:
  Xorg Segmentation fault on Hisilicon D05 board (arm64)

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg 
  [sudo] password for ubuntu: 

  X.Org X Server 1.18.4
  Release Date: 2016-07-19
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
  Current Operating System: Linux ubuntu 4.10.0-20.22-generic 
#22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic 
root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug 
earlycon=pl011,mmio,0x602B console=tty0
  Build Date: 02 November 2016  10:05:28PM
  xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  pci id for fd 10: 19e5:1711, driver (null)
  EGL_MESA_drm_image required.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48]
  (EE) 
  (EE) Segmentation fault at address 0xa0
  (EE) 
  Fatal server error:
  (EE) Caught signal 11 (Segmentation fault). Server aborting
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE) 
  (EE) Server terminated with error (1). Closing log file.
  Aborted (core dumped)
  ubuntu@ubuntu:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/+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 1696965] [NEW] First renderer process doesn't render page for chromium 59.0.3071.86 in KVM

2017-06-09 Thread Olivier Tilloy
Public bug reported:

Chromium 59.0.3071.86 was promoted to the stable release channel earlier
this week, and I have built packages for all supported ubuntu releases
at https://launchpad.net/~osomon/+archive/ubuntu/chromium-stable.

While they seem to work well on bare metal and in virtualbox virtual
machines, we are seeing an issue in KVM guests (e.g. Ubuntu 16.04.2):
when launched, the page in the first tab is not rendered at all (the
contents remain blank). Refreshing the page doesn't make things any
better. But browsing to a different domain in the same tab "fixes" the
issue.

All URLs are affected: the default URL when opening the browser for the
first time is chrome://welcome, and it's not rendered, and so aren't
other http URLs when passed on the command line.

It looks like the first renderer process is not able to render to screen
correctly. The renderer process itself looks okay, it doesn't crash, and
I haven't seen anything relevant in the verbose logs.

The official google chrome release on the same configuration is not
affected, so this problem is specific to our chromium-browser packages.

** Affects: chromium-browser (Ubuntu)
 Importance: Critical
 Assignee: Olivier Tilloy (osomon)
 Status: New

** Changed in: chromium-browser (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  First renderer process doesn't render page for chromium 59.0.3071.86
  in KVM

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Chromium 59.0.3071.86 was promoted to the stable release channel
  earlier this week, and I have built packages for all supported ubuntu
  releases at https://launchpad.net/~osomon/+archive/ubuntu/chromium-
  stable.

  While they seem to work well on bare metal and in virtualbox virtual
  machines, we are seeing an issue in KVM guests (e.g. Ubuntu 16.04.2):
  when launched, the page in the first tab is not rendered at all (the
  contents remain blank). Refreshing the page doesn't make things any
  better. But browsing to a different domain in the same tab "fixes" the
  issue.

  All URLs are affected: the default URL when opening the browser for
  the first time is chrome://welcome, and it's not rendered, and so
  aren't other http URLs when passed on the command line.

  It looks like the first renderer process is not able to render to
  screen correctly. The renderer process itself looks okay, it doesn't
  crash, and I haven't seen anything relevant in the verbose logs.

  The official google chrome release on the same configuration is not
  affected, so this problem is specific to our chromium-browser
  packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1696965/+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 1634598] Re: gnome-online-accounts Problems on Wayland

2017-06-09 Thread Jeremy Bicha
I'm closing this bug since it seems to be a duplicate of bug 1610944 and
bug 1687019 and doesn't really have anything to do with GNOME on
Wayland.

** Changed in: gnome-online-accounts (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  gnome-online-accounts Problems on Wayland

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

Bug description:
  When using gnome-online-accounts + wayland.

  When tshooting [LP1610944](https://bugs.launchpad.net/bugs/1610944) I
  noticed that you can't add a google account that utilizes
  customizations from [Google's Identity
  Platform](https://developers.google.com/identity/). This is used by
  many Google Apps for Work systems (including mine). This however does
  work on gnome with X. I believe this is a wayland specific issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1634598/+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


Re: [Desktop-packages] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

2017-06-09 Thread Zhanglei Mao
hi Danniel,

This forwarded mail are from Huawei guy which to say "PCI_BRIDGE_CTL_VGA"
are only used on X86 but not for AMR64. The English line was my translated
for Chines text.

thanks,
Mao

-- Forwarded message --
From: wanghuiqiang 
Date: 2017-06-09 13:38 GMT+08:00
Subject: 答复: 答复: 答复: vga card question for D05
To: Zourongrong , Zhanglei Mao <
zhanglei@canonical.com>, "Liuxinliang (Matthew Liu)" <
z.liuxinli...@hisilicon.com>
Cc: "Xiongfanggou (James)" , caesar qiu 裘赛海 <
caesar@siliconmotion.com>, allan wang 王友朋 ,
"freeman.w...@siliconmotion.com" ,
"Xiazhongjun (Summer)" , "kongxinwei (A)" <
kong.kongxin...@hisilicon.com>, Land Lu 


不清楚你们这个问题是基于什么平台提出的。

在ARM里没有用这个PCI_BRIDGE_CTL_VGA。这是x86的架构设计里用来分配IO和memory地址空间的。而ARM世界是没有IO
空间的概念的,至于memory空间,也是x86里为了支持legacy VGA而一直沿用的技术。具体信息可以看以下的内容。


Translating:

I don't know which platform was this request based on.

In the ARM,  PCI_BRIDGE_CTL_VGA was not used. This is a x86 architecture
design using as IO and Memory address space assign or allocation. In the
ARM word, there are no any IO space concepts,  for memory address space, it
was used space technology legacy VGA supports on X86. More details can be
found from below:

Thanks!

 

On Thu, Jun 8, 2017 at 9:40 AM, Zhanglei Mao 
wrote:

> hi Daniel,
>
> Agree with you that is something they need to fix. I have sent mail to
> HiSilicon and their VGA card vendors and they replied some for confirming
> and understand questions or our requests. I will push them again.
>
> thanks,
> Mao
>
> On Thu, Jun 8, 2017 at 8:41 AM, Daniel Axtens  > wrote:
>
>> Hi Mao,
>>
>> I have installed a version of the kernel which ignores the capabilities
>> of the PCI bridge when determining whether a device can be the boot
>> device. With this patched kernel, X starts without needing a config
>> file.
>>
>> This confirms:
>>  - that the vga card is not marked as boot device because of the the PCI
>> bridge that the VGA card sits behind.
>>  - not being marked as boot vga is what is causing X not to pick it up
>> the card.
>>
>> This is a debug patch only, and not a patch we will be able to get
>> upstream, so I think we will need to discuss with the HiSilicon people
>> why their hardware is behaving this way.
>>
>> Regards,
>> Daniel
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1691991
>>
>> Title:
>>   Xorg Segmentation fault on Hisilicon D05 board (arm64)
>>
>> Status in xorg package in Ubuntu:
>>   New
>>
>> Bug description:
>>   ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg
>>   [sudo] password for ubuntu:
>>
>>   X.Org X Server 1.18.4
>>   Release Date: 2016-07-19
>>   X Protocol Version 11, Revision 0
>>   Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
>>   Current Operating System: Linux ubuntu 4.10.0-20.22-generic
>> #22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
>>   Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic
>> root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug
>> earlycon=pl011,mmio,0x602B console=tty0
>>   Build Date: 02 November 2016  10:05:28PM
>>   xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see
>> http://www.ubuntu.com/support)
>>   Current version of pixman: 0.33.6
>> Before reporting problems, check http://wiki.x.org
>> to make sure that you have the latest version.
>>   Markers: (--) probed, (**) from config file, (==) default setting,
>> (++) from command line, (!!) notice, (II) informational,
>> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
>>   (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017
>>   (==) Using system config directory "/usr/share/X11/xorg.conf.d"
>>   pci id for fd 10: 19e5:1711, driver (null)
>>   EGL_MESA_drm_image required.
>>   (EE)
>>   (EE) Backtrace:
>>   (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48]
>>   (EE)
>>   (EE) Segmentation fault at address 0xa0
>>   (EE)
>>   Fatal server error:
>>   (EE) Caught signal 11 (Segmentation fault). Server aborting
>>   (EE)
>>   (EE)
>>   Please consult the The X.Org Foundation support
>>  at http://wiki.x.org
>>for help.
>>   (EE) Please also check the log file at "/var/log/Xorg.0.log" for
>> additional information.
>>   (EE)
>>   (EE) Server terminated with error (1). Closing log file.
>>   Aborted (core dumped)
>>   ubuntu@ubuntu:~$
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/
>> +subscriptions
>>
>
>
>
> --
> Zhanglei Mao
> Solutions Architect, Sales and Business Development
> Canonical Group Ltd.
> zhanglei@canonical.com
> +86-13625010929 <+86%20136%202501%200929> (m)
> +852-6700 6026 <+852%206700%206026> (m)
> www.ubuntu.com
> www.canonical.com
>


-- 
Zhanglei Mao
Solutions Architect, Sales and Business Development
Canonical Group Ltd.
zha

[Desktop-packages] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

2017-06-09 Thread Zhanglei Mao
hi Danniel,

This forwarded mail are from Huawei guy which to say
"PCI_BRIDGE_CTL_VGA" are only used on X86 but not for AMR64. The English
line was my translated for Chines text.

thanks,
Mao

-- Forwarded message --
From: wanghuiqiang 
Date: 2017-06-09 13:38 GMT+08:00
Subject: 答复: 答复: 答复: vga card question for D05
To: Zourongrong , Zhanglei Mao 
, "Liuxinliang (Matthew Liu)" 

Cc: "Xiongfanggou (James)" , caesar qiu 裘赛海 
, allan wang 王友朋 , 
"freeman.w...@siliconmotion.com" , "Xiazhongjun 
(Summer)" , "kongxinwei (A)" 
, Land Lu 


不清楚你们这个问题是基于什么平台提出的。
在ARM里没有用这个PCI_BRIDGE_CTL_VGA。这是x86的架构设计里用来分配IO和memory地址空间的。而ARM世界是没有IO空间的概念的,至于memory空间,也是x86里为了支持legacy
 VGA而一直沿用的技术。具体信息可以看以下的内容。

Translating: 
I don't know which platform was this request based on.
In the ARM,  PCI_BRIDGE_CTL_VGA was not used. This is a x86 architecture design 
using as IO and Memory address space assign or allocation. In the ARM word, 
there are no any IO space concepts,  for memory address space, it was used 
space technology legacy VGA supports on X86. More details can be found from 
below: 

Thanks!
 

** Attachment added: "screen picture for the mail for VGA compatible addressing"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/+attachment/4892951/+files/vga-compatible-address.png

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

Title:
  Xorg Segmentation fault on Hisilicon D05 board (arm64)

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg 
  [sudo] password for ubuntu: 

  X.Org X Server 1.18.4
  Release Date: 2016-07-19
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
  Current Operating System: Linux ubuntu 4.10.0-20.22-generic 
#22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic 
root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug 
earlycon=pl011,mmio,0x602B console=tty0
  Build Date: 02 November 2016  10:05:28PM
  xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  pci id for fd 10: 19e5:1711, driver (null)
  EGL_MESA_drm_image required.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48]
  (EE) 
  (EE) Segmentation fault at address 0xa0
  (EE) 
  Fatal server error:
  (EE) Caught signal 11 (Segmentation fault). Server aborting
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE) 
  (EE) Server terminated with error (1). Closing log file.
  Aborted (core dumped)
  ubuntu@ubuntu:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/+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 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

2017-06-09 Thread Zhanglei Mao
This 4.5.1 seems form "PCI-to-PCI Bridge Architecture Specification",
the full document can be download from below link:
https://cds.cern.ch/record/551427/files/cer-2308933.pdf

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

Title:
  Xorg Segmentation fault on Hisilicon D05 board (arm64)

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg 
  [sudo] password for ubuntu: 

  X.Org X Server 1.18.4
  Release Date: 2016-07-19
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
  Current Operating System: Linux ubuntu 4.10.0-20.22-generic 
#22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic 
root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug 
earlycon=pl011,mmio,0x602B console=tty0
  Build Date: 02 November 2016  10:05:28PM
  xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  pci id for fd 10: 19e5:1711, driver (null)
  EGL_MESA_drm_image required.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48]
  (EE) 
  (EE) Segmentation fault at address 0xa0
  (EE) 
  Fatal server error:
  (EE) Caught signal 11 (Segmentation fault). Server aborting
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE) 
  (EE) Server terminated with error (1). Closing log file.
  Aborted (core dumped)
  ubuntu@ubuntu:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/+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 1434351] Re: X fonts and widgets disappear after suspend/resume cycle

2017-06-09 Thread Julien SCORDIA
This bug affected me in Ubuntu 16.04 (using Xfce), and it was very
annoying. I have installed Ubuntu 17.04 (Kernel 4.10): the problem seems
to be solved, it did not appear in more than one month.

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+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 1656065] Re: Firefox and plugin-container (Chrome_ChildThr): segfault at 0 ip, sp error 6 in plugin-container/libxul.so

2017-06-09 Thread Walter Garcia-Fontes
Since upgrading the kernel to 4.10.0-22-generic in Ubuntu 17.04 I
haven't seen this bug any more. I think Firefox was also triggering a
general system freeze through a problem in the kernel. See bug #1674838
and the many messages relating it to a firefox freeze.

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

Title:
  Firefox and plugin-container (Chrome_ChildThr): segfault at 0 ip, sp
  error 6 in plugin-container/libxul.so

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Hello.

  Some days ago, Firefox unexpectedly has been closed after a couple of
  hours (mostly viewed: YouTube and some other websites). Next, a dialog
  box related to the Mozilla Crash Reporter appeared - with message,
  that reporter is disabled (which I did earlier via 'about:config' and
  *datareporting.healthreport.service.enabled* key set to _false_) and
  no crash report is available even via 'about:crashes' etc.

  After this situation two entries appeared in the log files: first
  related to the AppArmor and second: plugin-container segfault. By the
  way: in the same time there was an update for flash-plugin available
  (see: 1).

  Anyway, 'LastCrash' file (which can be found in
  ~/.mozilla/firefox/Crash Reports/ directory) contains only:
  1484142985. Just like all the others files in this directory. There
  are also two folders called: 'events' and 'pending'. But they are
  completely empty. However, system log files, such as
  '/var/log/kern.log' or '/var/log/syslog', contains an interesting
  entries:

  ● Jan 11 14:56:25 t4 kernel: [ 4161.295639] type=1400
  audit(1484142985.517:46): apparmor="DENIED" operation="open"
  parent=2818 profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
  name="/proc/2818/task/" pid=3253 comm="firefox" requested_mask="r"
  denied_mask="r" fsuid=1000 ouid=1000

  ● Jan 11 14:56:25 t4 kernel: [ 4161.540727] Chrome_ChildThr[2890]:
  segfault at 0 ip b76df673 sp b1efe9f0 error 6 in plugin-
  container[b76d8000+42000]

  As we know, thanks to the plugin-container, plugins are separated from
  the browser process, making it more stable, right? So now if a plugin
  crashes, Firefox should remains unharmed. It looks like this is a
  known problem (see: 2, 3).

  By the way; on Moday, 16 January, Firefox has been closed again - no
  action from my side. Log files contain the same entries as above:

  ● Jan 16 16:39:35 t4 kernel: [14373.711834] type=1400
  audit(1484581175.931:48): apparmor="DENIED" operation="open"
  parent=2532 profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
  name="/proc/2532/task/" pid=3389 comm="firefox" requested_mask="r"
  denied_mask="r" fsuid=1000 ouid=1000

  ● Jan 16 16:39:36 t4 kernel: [14373.934394] Chrome_ChildThr[3041]:
  segfault at 0 ip b76f8673 sp b1efe9f0 error 6 in plugin-
  container[b76f1000+42000]

  Anyway, after adding these two rules to the Firefox profile,
  everything seems to be OK and there is not DENIED message for
  "/proc/*/task/" entry anymore (so the first issue is solved):

  owner @{PROC}/[0-9]*/task/ r,
  owner @{PROC}/[0-9]*/task/* r,

  NOTE: This problem occurs when adobe-flash plugin is not activated and
  is permanently disabled and also when is used/enabled. Here are some
  informations about versions etc.:

  ● Firefox: 50.1.0
  ● Flash: 24.0.0.194ubuntu0.12.04.1
  ● Linux: 3.2.0-120-generic-pae (3.2.79) i686
  ● AppArmor: 2.7.102-0ubuntu3.10
  ● Release: 12.04.5 LTS (via `lsb_release -a` command)

  Best regards.
  _
  [1] https://lists.ubuntu.com/archives/precise-changes/2017-January/026047.html
  [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1205199
  [3] https://bugzilla.redhat.com/show_bug.cgi?id=1253086

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1656065/+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