date:20170718

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

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

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

Title:
  Printer not printing even though it is installed but printing in my
  windows system

Status in cups package in Ubuntu:
  Expired

Bug description:
  Printer not printing even though it is installed but printer is
  printing in my windows system

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.8
  ProcVersionSignature: Ubuntu 3.13.0-36.63+hwe3-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 19 21:27:17 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  InstallationDate: Installed on 2015-06-09 (710 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  Lpstat: device for Canon-LBP2900: usb://Canon/LBP2900?serial=A2A3MD8h
  MachineType: Dell Inc. Latitude 3450
  PpdFiles: Canon-LBP2900: Canon LBP-3360 - CUPS+Gutenprint v5.2.10-pre2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic 
root=UUID=f8fb5d2a-2608-412d-bd82-e59860e815c2 ro quiet splash pcie_aspm=force 
radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0PW7C8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd04/15/2015:svnDellInc.:pnLatitude3450:pvr01:rvnDellInc.:rn0PW7C8:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 3450
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1692055/+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 1640139] Re: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of packag

** Tags added: trusty

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

Title:
  package libpulse0 (not installed) failed to install/upgrade: trying to
  overwrite shared '/etc/pulse/client.conf', which is different from
  other instances of package libpulse0:i386

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

Bug description:
  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial

  # uname -a
  Linux rotem-laptop 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

  tried removing pulseaudio

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpulse0 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rotemfo2383 F pulseaudio
   /dev/snd/controlC0:  rotemfo2383 F pulseaudio
  Date: Tue Nov  8 12:46:09 2016
  DuplicateSignature:
   package:libpulse0:(not installed)
   Unpacking libpulse0:i386 (1:8.0-0ubuntu3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libpulse0_1%3a8.0-0ubuntu3_i386.deb (--unpack):
trying to overwrite shared '/etc/pulse/client.conf', which is different 
from other instances of package libpulse0:i386
  ErrorMessage: trying to overwrite shared '/etc/pulse/client.conf', which is 
different from other instances of package libpulse0:i386
  InstallationDate: Installed on 2016-10-25 (14 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 127: pacmd: 
error while loading shared libraries: libpulse.so.0: cannot open shared object 
file: No such file or directory
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: pulseaudio
  Title: package libpulse0 (not installed) failed to install/upgrade: trying to 
overwrite shared '/etc/pulse/client.conf', which is different from other 
instances of package libpulse0:i386
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/17/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd05/17/2016:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1640139/+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 1704295] Re: Gnome Software titlebar is too thin during startup under Ambiance

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

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

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

Title:
  Gnome Software titlebar is too thin during startup under Ambiance

Status in gnome-software package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Gnome Software titlebar is too thin during startup under Ambiance

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1704295/+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 1704295] Re: Gnome Software titlebar is too thin during startup under Ambiance

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

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Confirmed

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

Title:
  Gnome Software titlebar is too thin during startup under Ambiance

Status in gnome-software package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Gnome Software titlebar is too thin during startup under Ambiance

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1704295/+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 1705030] Re: "Ubuntu" session starts Wayland instead of X11 after first reboot

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

** This bug has been marked a duplicate of bug 1705157
   On fresh install or fresh boot greeter always show "ubuntu" though selected 
session may be ubuntu-wayland

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

Title:
  "Ubuntu" session starts Wayland instead of X11 after first reboot

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Testing Artful 17.10 daily from 18th July 2017.

  When installed to my laptop after the first reboot, GDM shows two
  possible sessions on login: "Ubuntu" and "Ubuntu with Wayland".
  However, both will open a Wayland session for me. The issue fixes
  itself after rebooting once more.

  How to reproduce: After fresh installation and reboot, choose "Ubuntu"
  in GDM and log in.

  What I expected: An X11 GNOME session should open up.

  What actually happens: A Wayland GNOME session opens up.
  I confirmed this by Alt + F2 -> r -> Enter (giving the message "Restart is 
not available on Wayland").
  Also, 'loginctl show-session  -p Type' shows "Type=wayland" ( 
is the session number given by 'loginctl').

  I could also reproduce this behaviour on a new fresh install.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-session (not installed)
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 18 15:25:32 2017
  InstallationDate: Installed on 2017-07-18 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170718)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1705030/+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 1705157] Re: On fresh install or fresh boot greeter always show "ubuntu" though selected session may be ubuntu-wayland

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

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

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

Title:
  On fresh install or fresh boot greeter always show "ubuntu" though
  selected session may be ubuntu-wayland

Status in gdm:
  New
Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  Test case:
  Do a fresh install of current image (july 19 here
  Boot up, check selected session at the greeter - it will say "ubuntu"
  Log in, ck. env., it will actually be ubuntu-wayland

  Ex.
  $ env | grep -i wayland
  DESKTOP_SESSION=ubuntu-wayland
  WAYLAND_DISPLAY=wayland-0
  XDG_SESSION_TYPE=wayland
  XDG_SESSION_DESKTOP=ubuntu-wayland
  GDMSESSION=ubuntu-wayland

  Test 2:
  From above log out, switch session in greeter to wayland on ubuntu,, switch 
back to ubuntu, login.
  Now you'll be in an ubuntu session

  Test 3:
  log out from above ubuntu session, log into ubuntu-wayland session, reboot.
  At greeter notice it says "ubuntu" selected.
  Login, ck. session. You'll actually be in an ubuntu-wayland session

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-session 3.24.1-0ubuntu15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 18 21:48:10 2017
  InstallationDate: Installed on 2017-07-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170718)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1705157/+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 1573900] Re: package libpulse0 (not installed) failed to install/upgrade: 尝试覆盖共享的 '/etc/pulse/client.conf', 它与软件包 libpulse0:i386 中的其他实例不同

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1640139, so it 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. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1640139
   package libpulse0 (not installed) failed to install/upgrade: trying to 
overwrite shared '/etc/pulse/client.conf', which is different from other 
instances of package libpulse0:i386

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

Title:
  package libpulse0 (not installed) failed to install/upgrade: 尝试覆盖共享的
  '/etc/pulse/client.conf', 它与软件包 libpulse0:i386 中的其他实例不同

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I found this problem when I was trying to install wine-
  qqintl_0.1.3-2_i386.deb.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libpulse0 (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  AptOrdering:
   libpulse0: Install
   libasound2-plugins: Install
   libpulse0: Configure
   libasound2-plugins: Configure
  Architecture: amd64
  Date: Sat Apr 23 13:26:04 2016
  DuplicateSignature: package:libpulse0:(not installed):尝试覆盖共享的 
'/etc/pulse/client.conf', 它与软件包 libpulse0:i386 中的其他实例不同
  ErrorMessage: 尝试覆盖共享的 '/etc/pulse/client.conf', 它与软件包 libpulse0:i386 中的其他实例不同
  InstallationDate: Installed on 2016-04-16 (7 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.5
   apt  1.0.1ubuntu2.12
  SourcePackage: pulseaudio
  Title: package libpulse0 (not installed) failed to install/upgrade: 尝试覆盖共享的 
'/etc/pulse/client.conf', 它与软件包 libpulse0:i386 中的其他实例不同
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1573900/+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 1705113] Re: package libpulse0 (not installed) failed to install/upgrade: tentative de remplacement de « /etc/pulse/client.conf », qui est différent d'autres instances du paque

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1640139, so it 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. Feel free to continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1640139
   package libpulse0 (not installed) failed to install/upgrade: trying to 
overwrite shared '/etc/pulse/client.conf', which is different from other 
instances of package libpulse0:i386

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

Title:
  package libpulse0 (not installed) failed to install/upgrade: tentative
  de remplacement de « /etc/pulse/client.conf », qui est différent
  d'autres instances du paquet libpulse0:amd64

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  i installed LXPanel on my ubuntu and after i don't have sound.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpulse0 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Date: Tue Jul 18 22:47:50 2017
  ErrorMessage: tentative de remplacement de « /etc/pulse/client.conf », qui 
est différent d'autres instances du paquet libpulse0:amd64
  InstallationDate: Installed on 2016-02-11 (523 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 127: pacmd: 
error while loading shared libraries: libpulse.so.0: cannot open shared object 
file: No such file or directory
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: pulseaudio
  Title: package libpulse0 (not installed) failed to install/upgrade: tentative 
de remplacement de « /etc/pulse/client.conf », qui est différent d'autres 
instances du paquet libpulse0:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61H2-M2
  dmi.board.vendor: ECS
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: ECS
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd09/07/2012:svnECS:pnH61H2-M2:pvr1.0:rvnECS:rnH61H2-M2:rvr1.0:cvnECS:ct3:cvr1.0:
  dmi.product.name: H61H2-M2
  dmi.product.version: 1.0
  dmi.sys.vendor: ECS
  mtime.conffile..etc.pulse.client.conf: 2017-07-18T22:55:04.553785

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1705113/+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 1705157] Re: On fresh install or fresh boot greeter always show "ubuntu" though selected session may be ubuntu-wayland

In other words the greeter will always show "ubuntu" as selected even if
last session was ubuntu-wayland

** Also affects: gdm
   Importance: Undecided
   Status: New

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

Title:
  On fresh install or fresh boot greeter always show "ubuntu" though
  selected session may be ubuntu-wayland

Status in gdm:
  New
Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  Test case:
  Do a fresh install of current image (july 19 here
  Boot up, check selected session at the greeter - it will say "ubuntu"
  Log in, ck. env., it will actually be ubuntu-wayland

  Ex.
  $ env | grep -i wayland
  DESKTOP_SESSION=ubuntu-wayland
  WAYLAND_DISPLAY=wayland-0
  XDG_SESSION_TYPE=wayland
  XDG_SESSION_DESKTOP=ubuntu-wayland
  GDMSESSION=ubuntu-wayland

  Test 2:
  From above log out, switch session in greeter to wayland on ubuntu,, switch 
back to ubuntu, login.
  Now you'll be in an ubuntu session

  Test 3:
  log out from above ubuntu session, log into ubuntu-wayland session, reboot.
  At greeter notice it says "ubuntu" selected.
  Login, ck. session. You'll actually be in an ubuntu-wayland session

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-session 3.24.1-0ubuntu15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 18 21:48:10 2017
  InstallationDate: Installed on 2017-07-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170718)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1705157/+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 1654759] Re: package libpulse0 (not installed) failed to install/upgrade: Versuch, gemeinsam benutztes »/etc/pulse/client.conf« zu überschreiben, welches verschieden von andere

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1640139, so it 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. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1640139
   package libpulse0 (not installed) failed to install/upgrade: trying to 
overwrite shared '/etc/pulse/client.conf', which is different from other 
instances of package libpulse0:i386

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

Title:
  package libpulse0 (not installed) failed to install/upgrade: Versuch,
  gemeinsam benutztes »/etc/pulse/client.conf« zu überschreiben, welches
  verschieden von anderen Instanzen des Paketes libpulse0:amd64 ist

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I had also problems after new installation of LTS 16.04 with audio. With 
14.04 it worksbut not with 16.04 (same hardware)
  I found the BugTracker: 
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1643847
  and made the chages like clement describes.but it dosen't work.
  Chrash after new start. I made no reboot!

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpulse0 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Date: Sat Jan  7 17:41:24 2017
  ErrorMessage: Versuch, gemeinsam benutztes »/etc/pulse/client.conf« zu 
überschreiben, welches verschieden von anderen Instanzen des Paketes 
libpulse0:amd64 ist
  InstallationDate: Installed on 2016-12-24 (14 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 127: pacmd: 
error while loading shared libraries: libpulse.so.0: cannot open shared object 
file: No such file or directory
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: pulseaudio
  Title: package libpulse0 (not installed) failed to install/upgrade: Versuch, 
gemeinsam benutztes »/etc/pulse/client.conf« zu überschreiben, welches 
verschieden von anderen Instanzen des Paketes libpulse0:amd64 ist
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/28/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F5
  dmi.board.name: P55-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd04/28/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1654759/+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 1705024] Re: Output to BT speaker stops when laptop is unplugged from AC

I experienced similar on my desktop yesterday. No sound when BT speaker
selected. Although I didn't unplug the power from the desktop :)

I think I need to ignore that though because the BT dongle on my desktop
is super-cheap and buggy compared to laptops. It has kernel issues that
then ripple into everything else.

** Tags added: a2dp

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

Title:
  Output to BT speaker stops when laptop is unplugged from AC

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  artful desktop

  Test Case
  1. Connect a laptop to a power supply
  2. Pair a BT speaker
  3. Play some music with VLC
  4. Disconnect the laptop from AC to switch to battery

  Expected result
  The music continues playing

  Actual result
  It stops. pavucontrol shows that the output device is still the BT speaker 
and the vumeter is still alive but there is not sound on the speaker. Only 
powering off/on the speaker makes it work again.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   j-lallement   1293 F...m pulseaudio
   /dev/snd/controlC1:  j-lallement   1293 F pulseaudio
   /dev/snd/controlC0:  j-lallement   1293 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Jul 18 14:40:02 2017
  InstallationDate: Installed on 2013-09-03 (1413 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  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/pulseaudio/+bug/1705024/+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 1702794] Re: Please add module-switch-on-connect to default.pa

Thanks. I noticed it now refuses to switch more often, but not always,
and that's also not strictly a new bug. It did happen before the update
too, just less often (for me).

I'll look into this soon...

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

Title:
  Please add module-switch-on-connect to default.pa

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  This way once a user pairs & connects a bluetooth speaker device pulseaudio 
will auto switch to it. 
  As it stands now users have to open sound settings & switch manually. It's 
bad enough that auto discover & connect don't work, (can be scripted thru 
bluetoothctl), no sense adding to frustration

  In the ### Automatically load driver modules for Bluetooth hardware
  section

  
  .ifexists module-switch-on-connect.so
  load-module module-switch-on-connect
  .endif

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doug   1843 F pulseaudio
   /dev/snd/controlC0:  doug   1843 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul  6 20:02:15 2017
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 74CN44WW(V3.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIQY0Y1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y510P
  dmi.modalias: 
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
  dmi.product.name: 20217
  dmi.product.version: Lenovo IdeaPad Y510P
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2017-07-04T13:42:27.651527

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1702794/+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 1705157] Re: On fresh install or fresh boot greeter always show "ubuntu" though selected session may be ubuntu-wayland

** Description changed:

- Test case: 
+ Test case:
  Do a fresh install of current image (july 19 here
  Boot up, check selected session at the greeter - it will say "ubuntu"
  Log in, ck. env., it will actually be ubuntu-wayland
  
  Ex.
  $ env | grep -i wayland
  DESKTOP_SESSION=ubuntu-wayland
  WAYLAND_DISPLAY=wayland-0
  XDG_SESSION_TYPE=wayland
  XDG_SESSION_DESKTOP=ubuntu-wayland
  GDMSESSION=ubuntu-wayland
  
- Test 2: 
- From above log out, switch session in greeter to wayland on ubuntu,, swirch 
back to ubuntu, login.
+ Test 2:
+ From above log out, switch session in greeter to wayland on ubuntu,, switch 
back to ubuntu, login.
  Now you'll be in an ubuntu session
  
- Test 3: 
+ Test 3:
  log out from above ubuntu session, log into ubuntu-wayland session, reboot.
- At greeter notice it says "ubuntu" selected. 
+ At greeter notice it says "ubuntu" selected.
  Login, ck. session. You'll actually be in an ubuntu-wayland session
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-session 3.24.1-0ubuntu15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 18 21:48:10 2017
  InstallationDate: Installed on 2017-07-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170718)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  On fresh install or fresh boot greeter always show "ubuntu" though
  selected session may be ubuntu-wayland

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Test case:
  Do a fresh install of current image (july 19 here
  Boot up, check selected session at the greeter - it will say "ubuntu"
  Log in, ck. env., it will actually be ubuntu-wayland

  Ex.
  $ env | grep -i wayland
  DESKTOP_SESSION=ubuntu-wayland
  WAYLAND_DISPLAY=wayland-0
  XDG_SESSION_TYPE=wayland
  XDG_SESSION_DESKTOP=ubuntu-wayland
  GDMSESSION=ubuntu-wayland

  Test 2:
  From above log out, switch session in greeter to wayland on ubuntu,, switch 
back to ubuntu, login.
  Now you'll be in an ubuntu session

  Test 3:
  log out from above ubuntu session, log into ubuntu-wayland session, reboot.
  At greeter notice it says "ubuntu" selected.
  Login, ck. session. You'll actually be in an ubuntu-wayland session

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-session 3.24.1-0ubuntu15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 18 21:48:10 2017
  InstallationDate: Installed on 2017-07-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170718)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1705157/+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 1705157] [NEW] On fresh install or fresh boot greeter always show "ubuntu" though selected session may be ubuntu-wayland

Public bug reported:

Test case: 
Do a fresh install of current image (july 19 here
Boot up, check selected session at the greeter - it will say "ubuntu"
Log in, ck. env., it will actually be ubuntu-wayland

Ex.
$ env | grep -i wayland
DESKTOP_SESSION=ubuntu-wayland
WAYLAND_DISPLAY=wayland-0
XDG_SESSION_TYPE=wayland
XDG_SESSION_DESKTOP=ubuntu-wayland
GDMSESSION=ubuntu-wayland

Test 2: 
>From above log out, switch session in greeter to wayland on ubuntu,, swirch 
>back to ubuntu, login.
Now you'll be in an ubuntu session

Test 3: 
log out from above ubuntu session, log into ubuntu-wayland session, reboot.
At greeter notice it says "ubuntu" selected. 
Login, ck. session. You'll actually be in an ubuntu-wayland session

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubuntu-session 3.24.1-0ubuntu15
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Jul 18 21:48:10 2017
InstallationDate: Installed on 2017-07-19 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170718)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-session
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  On fresh install or fresh boot greeter always show "ubuntu" though
  selected session may be ubuntu-wayland

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Test case: 
  Do a fresh install of current image (july 19 here
  Boot up, check selected session at the greeter - it will say "ubuntu"
  Log in, ck. env., it will actually be ubuntu-wayland

  Ex.
  $ env | grep -i wayland
  DESKTOP_SESSION=ubuntu-wayland
  WAYLAND_DISPLAY=wayland-0
  XDG_SESSION_TYPE=wayland
  XDG_SESSION_DESKTOP=ubuntu-wayland
  GDMSESSION=ubuntu-wayland

  Test 2: 
  From above log out, switch session in greeter to wayland on ubuntu,, swirch 
back to ubuntu, login.
  Now you'll be in an ubuntu session

  Test 3: 
  log out from above ubuntu session, log into ubuntu-wayland session, reboot.
  At greeter notice it says "ubuntu" selected. 
  Login, ck. session. You'll actually be in an ubuntu-wayland session

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-session 3.24.1-0ubuntu15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 18 21:48:10 2017
  InstallationDate: Installed on 2017-07-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170718)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1705157/+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 1506704] Re: Thin font, nautilus doesn't integrate with Unity.

2017-07-18 Thread Shahbaz Youssefi

I haven't seen this problem for a long time now. Must be fixed already!

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

Title:
Thin font, nautilus doesn't integrate with Unity.

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

Bug description:
It happens frequently (around 1/2 of the time) that when I boot the
computer, font lines are only one pixel thick. This concerns watch in
the sys-tray, all item in the menu of all applications, as well as all
fonts in Nautilus. When this happens. Nautilus doesn't display menu in
the Unity menu bar, but displays an additional button showing three
horizontal lines for bringing up the menu.

This problem has been with me for years, although sometimes disappears
for months at a time when I run sudo apt-get update. This time it re-
emerged after upgrading to 15.10 beta (Wily). It happens usually on
power-up, and disappears after system restart. (To appear again on the
next power-up).

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: nautilus 1:3.14.2-0ubuntu12
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Oct 16 04:53:31 2015
GsettingsChanges:

InstallationDate: Installed on 2015-10-08 (7 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1506704/+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 1515771] Re: Occasional hiccup when opening nautilus

2017-07-18 Thread Shahbaz Youssefi

Since 16.04 (I think), where Files changed its behavior to show mounted
drives in another window (a bad choice in my opinion, but whatever) this
problem is not reproducible anymore. I marked as fixed thus.

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

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

Title:
  Occasional hiccup when opening nautilus

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Since the update to Ubuntu 14.04 a few days ago, (today is Nov 12,
  2015), there are occasional hiccups when opening nautilus. That is,
  sometimes it takes tens of seconds for a new window to open and the
  nautilus windows that are already open don't respond either.

  I unfortunately don't have a repeatable way to reproduce this.

  A relevant piece of information is that I may have a nautilus window
  open at a `smb://` address.

  

  $ lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04

  $ apt-cache policy nautilus
  nautilus:
Installed: 1:3.10.1-0ubuntu9.11
Candidate: 1:3.10.1-0ubuntu9.11
Version table:
   *** 1:3.10.1-0ubuntu9.11 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.10.1-0ubuntu8 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  $ uname -a
  Linux  3.16.0-53-generic #72~14.04.1-Ubuntu SMP Fri Nov 6 18:17:23 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1515771/+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 1550939] Re: Tab on Index makes evince go crazy

2017-07-18 Thread Shahbaz Youssefi

Not reproducible on newer evince. Marked as fixed.

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

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

Title:
  Tab on Index makes evince go crazy

Status in evince package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:

  - Open a pdf with Index
  - Click on a section in the Index
  - Press Tab

  Expected behavior:

  - I don't know. I accidentally clicked Tab instead of Alt+Tab

  Observed behavior:

  - Evince very quickly goes through the Index, section after section. I
  didn't find a way to stop the madness except closing evince and
  reopening the pdf.

  I tested this with the Vulkan specifications
  (https://www.khronos.org/registry/vulkan/specs/1.0/pdf/vkspec.pdf) and
  the C11 standard (http://www.open-
  std.org/jtc1/sc22/wg14/www/docs/n1570.pdf)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: evince 3.16.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 28 10:14:14 2016
  ExecutablePath: /usr/bin/evince
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: evince
  UpgradeStatus: Upgraded to wily on 2015-10-22 (129 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1550939/+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 1689825] Re: gnome-keyring not unlocked on boot

2017-07-18 Thread jose

Thank you, I really don't think that this is a good solution

On 07/18/2017 03:53 PM, Gunnar Hjalmarsson wrote:
> dbus-user-session is a dependency of the desktop meta packages, so
> uninstalling it means that you on Unity uninstall ubuntu-session and
> ubuntu-desktop, on GNOME Flashback you uninstall gnome-session-flashback
> etc.
>

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

Title:
  gnome-keyring not unlocked on boot

Status in D-Bus:
  New
Status in chromium-browser package in Ubuntu:
  Invalid
Status in flatpak package in Ubuntu:
  Confirmed
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus/+bug/1689825/+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 1704162] Re: Add on/off switch for network connectivity check

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

Title:
  Add on/off switch for network connectivity check

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

Bug description:
  For Ubuntu 17.10, the Desktop Team would like to enable
  NetworkManager's connectivity check (LP: #997200) to detect captive
  portals. This has been supported by other GNOME distros for a couple
  years. Fedora in particular makes it opt out which we plan to do also
  in Ubuntu.

  This bug is a feature request to add an on/off switch for this
  connectivity check to gnome-control-center. I suggest that it be added
  to the Privacy panel although it might also work in the Network panel.

  I think there are two ways the switch could work. It could either
  write directly to a config file or it could use PackageKit to install
  or uninstall the distro-specific package that contains the
  connectivity config file. The advantage of the separate binary package
  is that it's easy to install or uninstall it for people that don't use
  gnome-control-center.

  See the upstream bug for a bit more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1704162/+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 1675830] Re: nvidia 304 graphics causes Login loop in Ubuntu Budgie

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

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

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

Title:
  nvidia 304 graphics causes Login loop in Ubuntu Budgie

Status in Ubuntu Budgie:
  New
Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed

Bug description:
  Nvidia 304 graphics kills budgie-window manager process and causes
  login loop in Ubuntu Budgie.

  Steps:
  - Enter password
  - System shows top bar (half cropped)
  - Sometimes dock  appears
  - Screen goes off (with no signal in monitor)
  - Screen shows login screen again

  System description:
  - OS:  Ubuntu Budgie 17.04 (daily build)
  - GPU: Nvidia GeForce 6150SE nForce 430

  Packages:
  - Budgie Desktop 10.2.9
  - Nvidia Graphics Drivers 304

  Notes:
  The system it's updated (full-upgrade)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1675830/+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 245716] Re: file-roller puts temporary files in the home dir instead of /tmp

2017-07-18 Thread Bob Bib

I've switched to Xarchiver.

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

Title:
  file-roller puts temporary files in the home dir instead of /tmp

Status in File Roller:
  Confirmed
Status in file-roller package in Ubuntu:
  Triaged
Status in file-roller package in Arch Linux:
  New

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  2) apt-cache policy file-roller
  file-roller:
Installed: 3.12.2-0ubuntu1
Candidate: 3.12.2-0ubuntu1
Version table:
   *** 3.12.2-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen is when one opens a tarball with file-
  roller, and without extracting the file, open it (ex. open PDF file
  with evince) the file-roller utilizes /tmp for this.

  4) What happens instead is file-roller utilizes a directory ~/.cache/.fr-* , 
where * is a changing folder name. If one logs out, or kills the file-roller 
process via:
  kill PID

  the temp files are left behind.

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/245716/+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 1586528] Re: Avahi-daemon withdraws address record

2017-07-18 Thread Leen Droogendijk

Same problem. Using Mint. No VM involved.
Switched from Windows to Linux just a few days ago.
This occurred two times in three days now.
Never did anything network related, so all my settings should be the default 
ones.

$ sudo lshw -class network
  *-network   
   description: Ethernet interface
   product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
   vendor: Realtek Semiconductor Co., Ltd.
   physical id: 0
   bus info: pci@:03:00.0
   logical name: enp3s0
   version: 0c
   serial: e0:3f:49:e8:4f:66
   size: 1Gbit/s
   capacity: 1Gbit/s
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=full firmware=rtl8168g-2_0.0.1 02/06/13 
ip=192.168.2.1 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s
   resources: irq:27 ioport:d000(size=256) memory:f710-f7100fff 
memory:f210-f2103fff

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

Title:
  Avahi-daemon withdraws address record

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

Bug description:
  For some reason, if I leave my Ubuntu VM up for a prolonged period of
  time the machine will lose connection to the network.  ip addr shows
  that the nic port no longer has an address and an examination of the
  syslog shows this:

  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record 
for 10.0.2.15 on enp0s3.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast 
group on interface enp0s3.IPv4 with address 10.0.2.15.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no 
longer relevant for mDNS.

  
  for no known reason.

  The only reliable way to get the network to come back (that I have
  found) is a full reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 27 15:11:34 2016
  InstallationDate: Installed on 2015-10-22 (218 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+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 245716] Re: file-roller puts temporary files in the home dir instead of /tmp

2017-07-18 Thread Bob Bib

** Also affects: file-roller (Arch Linux)
   Importance: Undecided
   Status: New

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

Title:
  file-roller puts temporary files in the home dir instead of /tmp

Status in File Roller:
  Confirmed
Status in file-roller package in Ubuntu:
  Triaged
Status in file-roller package in Arch Linux:
  New

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  2) apt-cache policy file-roller
  file-roller:
Installed: 3.12.2-0ubuntu1
Candidate: 3.12.2-0ubuntu1
Version table:
   *** 3.12.2-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen is when one opens a tarball with file-
  roller, and without extracting the file, open it (ex. open PDF file
  with evince) the file-roller utilizes /tmp for this.

  4) What happens instead is file-roller utilizes a directory ~/.cache/.fr-* , 
where * is a changing folder name. If one logs out, or kills the file-roller 
process via:
  kill PID

  the temp files are left behind.

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/245716/+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 1705113] [NEW] package libpulse0 (not installed) failed to install/upgrade: tentative de remplacement de « /etc/pulse/client.conf », qui est différent d'autres instances du paq

2017-07-18 Thread Rakotondrasoa Nampoina Andriamalala

Public bug reported:

i installed LXPanel on my ubuntu and after i don't have sound.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libpulse0 (not installed)
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.9
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Date: Tue Jul 18 22:47:50 2017
ErrorMessage: tentative de remplacement de « /etc/pulse/client.conf », qui est 
différent d'autres instances du paquet libpulse0:amd64
InstallationDate: Installed on 2016-02-11 (523 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 127: pacmd: 
error while loading shared libraries: libpulse.so.0: cannot open shared object 
file: No such file or directory
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: pulseaudio
Title: package libpulse0 (not installed) failed to install/upgrade: tentative 
de remplacement de « /etc/pulse/client.conf », qui est différent d'autres 
instances du paquet libpulse0:amd64
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/07/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61H2-M2
dmi.board.vendor: ECS
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: ECS
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd09/07/2012:svnECS:pnH61H2-M2:pvr1.0:rvnECS:rnH61H2-M2:rvr1.0:cvnECS:ct3:cvr1.0:
dmi.product.name: H61H2-M2
dmi.product.version: 1.0
dmi.sys.vendor: ECS
mtime.conffile..etc.pulse.client.conf: 2017-07-18T22:55:04.553785

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


** Tags: amd64 apport-package xenial

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

Title:
  package libpulse0 (not installed) failed to install/upgrade: tentative
  de remplacement de « /etc/pulse/client.conf », qui est différent
  d'autres instances du paquet libpulse0:amd64

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  i installed LXPanel on my ubuntu and after i don't have sound.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpulse0 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Date: Tue Jul 18 22:47:50 2017
  ErrorMessage: tentative de remplacement de « /etc/pulse/client.conf », qui 
est différent d'autres instances du paquet libpulse0:amd64
  InstallationDate: Installed on 2016-02-11 (523 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 127: pacmd: 
error while loading shared libraries: libpulse.so.0: cannot open shared object 
file: No such file or directory
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: pulseaudio
  Title: package libpulse0 (not installed) failed to install/upgrade: tentative 
de remplacement de « /etc/pulse/client.conf », qui est différent d'autres 
instances du paquet libpulse0:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61H2-M2
  dmi.board.vendor: ECS
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: ECS
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd09/07/2012:svnECS:pnH61H2-M2:pvr1.0:rvnECS:rnH61H2-M2:rvr1.0:cvnECS:ct3:cvr1.0:
  dmi.product.name: H61H2-M2
  dmi.product.version: 1.0
  dmi.sys.vendor: ECS
  mtime.conffile..etc.pulse.client.conf: 2017-07-18T22:55:04.553785

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

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

[Desktop-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot

2017-07-18 Thread Gunnar Hjalmarsson

dbus-user-session is a dependency of the desktop meta packages, so
uninstalling it means that you on Unity uninstall ubuntu-session and
ubuntu-desktop, on GNOME Flashback you uninstall gnome-session-flashback
etc.

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

Title:
  gnome-keyring not unlocked on boot

Status in D-Bus:
  New
Status in chromium-browser package in Ubuntu:
  Invalid
Status in flatpak package in Ubuntu:
  Confirmed
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus/+bug/1689825/+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 1555569] Re: Use 'title' field for snap apps

2017-07-18 Thread Kyle Fazzari

Sergio, what is the snapcraft solution to this? I'm still under the
impression the title (and license) need to go into the snap.yaml, but
you seemed to think it was only out-of-band to the store. Did we get
that resolved?

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

Title:
  Use 'title' field for snap apps

Status in Snapcraft:
  New
Status in Software Center Agent:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Yakkety:
  Won't Fix
Status in gnome-software source package in Zesty:
  Fix Committed
Status in gnome-software source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  Snaps show using the snap 'name', which has a limited character set and is 
not translatable (e.g. 'moon-buggy'). The store contained a 'title' which is 
more appropriate (e.g. 'Moon Buggy') which was not exposed via snapd. Now snapd 
supports this field we should use it in GNOME Software.

  [Test Case]
  1. Start GNOME Software
  2. Search for 'moon'

  Expected result:
  A snap called 'Moon Buggy' is shown.

  Observed result:
  A snap called 'moon-buggy' is shown.

  [Regression Potential]
  The fix is to use the new field if it is present.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/169/+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 1689825] Re: gnome-keyring not unlocked on boot

2017-07-18 Thread jose

I've not tried it yet, but I'm sure that uninstalling dbus-user-session
works as a workaround. what concerns me is what consequences will this
have. I checked 16.10 and 17.04 and both have dbus-user-session
installed by default. When I install chrome I don't seem to get the same
issues. I haven't installed flatpak to see if that recreates the problem
on 17. So how does removing dbus-user-session solve this problem?

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

Title:
  gnome-keyring not unlocked on boot

Status in D-Bus:
  New
Status in chromium-browser package in Ubuntu:
  Invalid
Status in flatpak package in Ubuntu:
  Confirmed
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus/+bug/1689825/+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 735496] Report: Ginobili finalizing deal to return to Spurs

2017-07-18 Thread Robert Cotterman

Greetings,

Manu Ginobili still feels he has another good year of basketball left in
him at age 40. http://profmarket16.ru/dox.php?b7b6

See you around, Myra Dickson


From: Bug 735496 [mailto:735...@bugs.launchpad.net]
Sent: Tuesday, July 18, 2017 1:38 PM
To: robertc1...@yahoo.com
Subject: Eventually

This thread is such rubbish

When I used  to fight  with my  wife a  lot it was usually related to me
not paying  her  enough attention  in  the romance department
(disguised as  the toilet seat being  left up). Save yourself the  six
hour conversation about leaving the toilet seat up and  heat  it up a
little,  if you do it right  she won't give a fuck about the shit  you
left on the counter.

Source:13  years  married with 4 kids



** Attachment added: "559A1E95129263FA59226240B9DA24CF.jpg"
   
https://bugs.launchpad.net/bugs/735496/+attachment/4917056/+files/559A1E95129263FA59226240B9DA24CF.jpg

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

Title:
  package monodoc-webkit-manual 0.3-2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in webkit-sharp package in Ubuntu:
  New

Bug description:
  i don't know anything about this, the machine just asked me to file
  this report

  ProblemType: Package
  DistroRelease: Ubuntu 10.04
  Package: monodoc-webkit-manual 0.3-2
  ProcVersionSignature: Ubuntu 2.6.32-29.58-generic-pae 2.6.32.28+drm33.13
  Uname: Linux 2.6.32-29-generic-pae i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Mon Mar 14 20:23:04 2011
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Release i386 (20100429)
  PackageArchitecture: all
  SourcePackage: webkit-sharp
  Title: package monodoc-webkit-manual 0.3-2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webkit-sharp/+bug/735496/+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 1704628] Re: CUPS keeps crashing 17.04

2017-07-18 Thread Till Kamppeter

Are all the crash pop-ups actually related to cups-browsed as the one
you have talked about in you comment? Or are there also some related to
CUPS (cupsd)? Do the pop-ups all report the same problem ("crashed with
SIGSEGV in__strcasecmp_l_avx()")?

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

Title:
  CUPS keeps crashing 17.04

Status in cups-filters package in Ubuntu:
  Incomplete

Bug description:
  cupsd or cups-browser are systematically crashing at start-up. I tried to 
purge and reinstall cups without success. systemctrl status cups shows:
  cups.service - CUPS Scheduler
 Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)
 Active: failed (Result: core-dump) since Sun 2017-07-16 16:58:10 CST; 45s 
ago
   Docs: man:cupsd(8)
Process: 14474 ExecStart=/usr/sbin/cupsd -l (code=dumped, signal=SEGV)
   Main PID: 14474 (code=dumped, signal=SEGV)

  Jul 16 16:58:10 my-desktop systemd[1]: Started CUPS Scheduler.
  Jul 16 16:58:10 my-desktop systemd[1]: cups.service: Main process exited, 
code=dumped, status=11/SEGV
  Jul 16 16:58:10 my-desktop systemd[1]: cups.service: Unit entered failed 
state.
  Jul 16 16:58:10 my-desktop systemd[1]: cups.service: Failed with result 
'core-dump'.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: cups 2.2.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Jul 16 17:06:10 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-07-02 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: System manufacturer System Product Name
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=bf399cdf-9a52-46c0-9d61-daa2bc83cf2f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VPRO:rvrRev1.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-filters/+bug/1704628/+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 1704628] Re: CUPS keeps crashing 17.04

2017-07-18 Thread Till Kamppeter

cups-browsed is part of cups-filters, not of cups, therefore moving to
cups-filters.

** Package changed: cups (Ubuntu) => cups-filters (Ubuntu)

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

Title:
  CUPS keeps crashing 17.04

Status in cups-filters package in Ubuntu:
  Incomplete

Bug description:
  cupsd or cups-browser are systematically crashing at start-up. I tried to 
purge and reinstall cups without success. systemctrl status cups shows:
  cups.service - CUPS Scheduler
 Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)
 Active: failed (Result: core-dump) since Sun 2017-07-16 16:58:10 CST; 45s 
ago
   Docs: man:cupsd(8)
Process: 14474 ExecStart=/usr/sbin/cupsd -l (code=dumped, signal=SEGV)
   Main PID: 14474 (code=dumped, signal=SEGV)

  Jul 16 16:58:10 my-desktop systemd[1]: Started CUPS Scheduler.
  Jul 16 16:58:10 my-desktop systemd[1]: cups.service: Main process exited, 
code=dumped, status=11/SEGV
  Jul 16 16:58:10 my-desktop systemd[1]: cups.service: Unit entered failed 
state.
  Jul 16 16:58:10 my-desktop systemd[1]: cups.service: Failed with result 
'core-dump'.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: cups 2.2.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Jul 16 17:06:10 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-07-02 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: System manufacturer System Product Name
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=bf399cdf-9a52-46c0-9d61-daa2bc83cf2f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VPRO:rvrRev1.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-filters/+bug/1704628/+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 1704735] Re: Chromium browser closes as soon as it is opened

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

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

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

Title:
  Chromium browser closes as soon as it is opened

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Was using Chromium as a second browser when it closed down
  unexpectedly. Restarting the browser results in a brief flicker as the
  browser starts up and then immediately closes again.

  Steps to reproduce the problem:
  1. Go to this web page: http://homebrewery.naturalcrit.com/edit/S1gkEMuoE-
  Note that the above web page was the first one to crash on me, but after a 
successful restart, it seems that the web browser can crash at any point.
  2. The browser segfaults
  3. I cannot reopen the browser

  Running from a terminal produces the following:
  paulvaughan@spectre-x360:~$ chromium-browser 
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f52f5e88425 base::debug::StackTrace::StackTrace()
  #1 0x7f52f5e8880b 
  #2 0x7f52f61b3390 
  #3 0x563bd8150dc8 
  #4 0x563bd8153656 
  #5 0x563bd8153df9 
  #6 0x563bd8154143 
  #7 0x7f52f5f03821 
  #8 0x7f52f5e89eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f52f5eb2e90 base::MessageLoop::RunTask()
  #10 0x7f52f5eb497d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f52f5eb583d 
  #12 0x7f52f5eb6300 base::MessagePumpLibevent::Run()
  #13 0x7f52f5eb1f15 base::MessageLoop::RunHandler()
  #14 0x7f52f5edc628 base::RunLoop::Run()
  #15 0x7f52f5f08e36 base::Thread::ThreadMain()
  #16 0x7f52f5f03726 
  #17 0x7f52f61a96ba start_thread
  #18 0x7f52df8583dd clone
r8: 002e  r9: 563bd9ba76ec r10:  r11: 
7f52df8e5f50
   r12: 7f5252ffaff0 r13: 0008 r14: 0008 r15: 
7f5252ffaeb0
di:   si: 7f5252ffaeb0  bp: 7f5252ffaf00  bx: 
7f5252ffaeb0
dx: 0061  ax:   cx: 563bdce92c30  sp: 
7f5252ffae60
ip: 563bd8150dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]
  Calling _exit(1). Core file will not be generated.

  Chrome version: 59.0.3071.109  Channel: stable
  OS Version: Ubuntu 16.04 LTS
  Flash Version: 

  Note that I have to delete ~/.config/chromium to get the browser to
  work again, but how long it will then work for before it again crashes
  is anyone's guess.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser 59.0.3071.109-0ubuntu0.16.04.1291
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  DRM.card0-DP-1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0-HDMI-A-1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0-HDMI-A-2:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0-eDP-1:
   edid-base64: 
AP///wAw5AAXAQSgHRF4AvGVo1VSoSYPUFQBAQEBAQEBAQEBAQEBAQEBiF4AoKCgKVAwICMAJaUQAAAZBT8AoKCgKVAwICMAJaUQAAAZAgAHLf8KPKoiFDKqAFU=
   dpms: On
   modes: 2560x1440 2560x1440
   enabled: enabled
   status: connected
  Date: Mon Jul 17 08:24:12 2017
  Desktop-Session:
   'default'
   '/etc/xdg/xdg-default:/etc/xdg'
   
'/usr/share/default:/usr/share/gnome:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2016-08-10 (340 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  InstalledPlugins:
   /usr/lib/mozilla/plugins:
 => libgnome-shell-browser-plugin.so
   (size: 18920 bytes, mtime: Mon May 29 15:35:13 2017)
  Load-Avg-1min: 0.42
  Load-Processes-Running-Percent:   0.1%
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:2072 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 064e:9314 Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-83-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.35
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81A1
  dmi.board.vendor: HP

[Desktop-packages] [Bug 1705063] Re: Reset behavior settings wrongly add the "show-desktop" icon to the launcher

** Branch linked: lp:~ci-train-bot/unity-control-center/unity-control-
center-ubuntu-xenial-2841

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

Title:
  Reset behavior settings wrongly add the "show-desktop" icon to the
  launcher

Status in unity-control-center package in Ubuntu:
  In Progress

Bug description:
  [Impact]

  Show desktop launcher icon is added to the launcher after restoring
  behavior settings

  
  [Test case]
  1. Open appearnace panel
  2. Ensure that the 
  3. Press the "Restore behavior settings" button
  4. Launcher "show-desktop" icon shouldn't be there afterwards

  [Possible regressions]

  Really nothing known, we might break the launcher favorites.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1705063/+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 1705063] Re: Reset behavior settings wrongly add the "show-desktop" icon to the launcher

** Branch linked: lp:~3v1n0/unity-control-center/grouped-compiz-
gsettings-support-x

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

Title:
  Reset behavior settings wrongly add the "show-desktop" icon to the
  launcher

Status in unity-control-center package in Ubuntu:
  In Progress

Bug description:
  [Impact]

  Show desktop launcher icon is added to the launcher after restoring
  behavior settings

  
  [Test case]
  1. Open appearnace panel
  2. Ensure that the 
  3. Press the "Restore behavior settings" button
  4. Launcher "show-desktop" icon shouldn't be there afterwards

  [Possible regressions]

  Really nothing known, we might break the launcher favorites.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1705063/+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 1677327] Re: SRU request: dkms build fails with zesty hwe kernel [error: too few arguments to function ‘NV_GET_USER_PAGES’]

This bug was fixed in the package nvidia-graphics-drivers-340 -
340.102-0ubuntu0.16.04.2

---
nvidia-graphics-drivers-340 (340.102-0ubuntu0.16.04.2) xenial-proposed; 
urgency=medium

  * debian/dkms_nvidia/patches/buildfix_kernel_4.9.patch:
- Sync patch with the one in Zesty to fix build issue with
  linux-image-generic-hwe-16.04-edge (LP: #1677327).

 -- Alberto Milone   Mon, 03 Apr 2017
17:36:55 +0200

** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial)
   Status: In Progress => Fix Released

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

Title:
  SRU request: dkms build fails with zesty hwe kernel [error: too few
  arguments to function ‘NV_GET_USER_PAGES’]

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  The patch for Linux 4.9 in nvidia-340 in Ubuntu 16.04 does not match the one 
in 17.04. As a result, the module fails to build against the hwe 4.10 kernel.

  [Test Case]
  1) Enable the xenial-proposed repository, and install 
linux-headers-generic-hwe-16.04-edge, linux-image-generic-hwe-16.04-edge, and 
nvidia-340.

  2) Check that DKMS builds the module, then restart the system, and see
  if it boots correctly. If unsure, please attach your /var/log/gpu-
  manager.log and /var/log/Xorg.0.log

  [Regression Potential]
  Low, the exact same patch is already available in the package in 17.04.

  
  _
  ADT test failure against linux-hwe-edge 4.10.0-14.16~16.04.1.

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-340/20170328_225401_6519b@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-340/20170328_230514_6519b@/log.gz

  We need to backport build fixes for 4.9/4.10 kernels.

  /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c: In function 
‘os_lock_user_pages’:
  /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c:50:65: warning: passing 
argument 4 of ‘NV_GET_USER_PAGES’ makes integer from pointer without a cast 
[-Wint-conversion]
   page_count, write ? FOLL_WRITE : 0, user_pages, 
NULL);
   ^
  In file included from /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c:15:0:
  /var/lib/dkms/nvidia-340/340.102/build/nv-linux.h:2094:28: note: expected 
‘int’ but argument is of type ‘struct page **’
   static inline long NV_GET_USER_PAGES(unsigned long start,
  ^
  /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c:48:11: error: too few 
arguments to function ‘NV_GET_USER_PAGES’
   ret = NV_GET_USER_PAGES((unsigned long)address,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1677327/+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 1677327] Update Released

2017-07-18 Thread Andy Whitcroft

The verification of the Stable Release Update for nvidia-graphics-
drivers-340 has completed successfully and the package has now been
released to -updates.  Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report.  In the event that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update so we can easily find any regressions.

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

Title:
  SRU request: dkms build fails with zesty hwe kernel [error: too few
  arguments to function ‘NV_GET_USER_PAGES’]

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  The patch for Linux 4.9 in nvidia-340 in Ubuntu 16.04 does not match the one 
in 17.04. As a result, the module fails to build against the hwe 4.10 kernel.

  [Test Case]
  1) Enable the xenial-proposed repository, and install 
linux-headers-generic-hwe-16.04-edge, linux-image-generic-hwe-16.04-edge, and 
nvidia-340.

  2) Check that DKMS builds the module, then restart the system, and see
  if it boots correctly. If unsure, please attach your /var/log/gpu-
  manager.log and /var/log/Xorg.0.log

  [Regression Potential]
  Low, the exact same patch is already available in the package in 17.04.

  
  _
  ADT test failure against linux-hwe-edge 4.10.0-14.16~16.04.1.

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-340/20170328_225401_6519b@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-340/20170328_230514_6519b@/log.gz

  We need to backport build fixes for 4.9/4.10 kernels.

  /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c: In function 
‘os_lock_user_pages’:
  /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c:50:65: warning: passing 
argument 4 of ‘NV_GET_USER_PAGES’ makes integer from pointer without a cast 
[-Wint-conversion]
   page_count, write ? FOLL_WRITE : 0, user_pages, 
NULL);
   ^
  In file included from /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c:15:0:
  /var/lib/dkms/nvidia-340/340.102/build/nv-linux.h:2094:28: note: expected 
‘int’ but argument is of type ‘struct page **’
   static inline long NV_GET_USER_PAGES(unsigned long start,
  ^
  /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c:48:11: error: too few 
arguments to function ‘NV_GET_USER_PAGES’
   ret = NV_GET_USER_PAGES((unsigned long)address,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1677327/+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 1705063] Re: Reset behavior settings wrongly add the "show-desktop" icon to the launcher

** Branch linked: lp:~3v1n0/unity-control-center/lowgfx-listens-compiz-
profile

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

Title:
  Reset behavior settings wrongly add the "show-desktop" icon to the
  launcher

Status in unity-control-center package in Ubuntu:
  In Progress

Bug description:
  [Impact]

  Show desktop launcher icon is added to the launcher after restoring
  behavior settings

  
  [Test case]
  1. Open appearnace panel
  2. Ensure that the 
  3. Press the "Restore behavior settings" button
  4. Launcher "show-desktop" icon shouldn't be there afterwards

  [Possible regressions]

  Really nothing known, we might break the launcher favorites.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1705063/+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 1705063] [NEW] Reset behavior settings wrongly add the "show-desktop" icon to the launcher

2017-07-18 Thread Treviño

Public bug reported:

[Impact]

Show desktop launcher icon is added to the launcher after restoring
behavior settings

[Test case]
1. Open appearnace panel
2. Ensure that the
3. Press the "Restore behavior settings" button
4. Launcher "show-desktop" icon shouldn't be there afterwards

[Possible regressions]

Really nothing known, we might break the launcher favorites.

** Affects: unity-control-center (Ubuntu)
Importance: Medium
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: In Progress

** Changed in: unity-control-center (Ubuntu)
Importance: Undecided => Medium

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

Title:
Reset behavior settings wrongly add the "show-desktop" icon to the
launcher

Status in unity-control-center package in Ubuntu:
In Progress

Bug description:
[Impact]

Show desktop launcher icon is added to the launcher after restoring
behavior settings

[Test case]
1. Open appearnace panel
2. Ensure that the
3. Press the "Restore behavior settings" button
4. Launcher "show-desktop" icon shouldn't be there afterwards

[Possible regressions]

Really nothing known, we might break the launcher favorites.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1705063/+subscriptions

[Desktop-packages] [Bug 1670933] Re: Accessibility partly broken due to X root window being kept from login session.

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

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

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

Title:
  Accessibility partly broken due to X root window being kept from login
  session.

Status in LightDM GTK+ Greeter:
  New
Status in unity-greeter package in Ubuntu:
  Confirmed

Bug description:
   affects lightdm

  Lightdm version 1.21.5, in 17.04. Some components of the Unity and
  Mate desktops are currently not accessible when logging in using
  lightdm. So far I've tested and reproduced this problem with both
  unity-greeter, and lightdm-gtk-greeter, so I suspect it is what I
  mentioned in the title, i.e the X root window is kept around.

  At-spi gets loaded in the greeter for use with Orca. At-spi ads a
  property atom, AT_SPI_BUS, to the root X window to allow software to
  be able to find the accessibility bus. If my understanding is correct,
  this root window is kept around for the user login session. What then
  happens is software either using Qt or Gtk loads its accessibility
  support code, which in turn looks for the AT_SPI_BUS property.
  Normally on session load, this property is not present, at which point
  the support code then connects to org.a11y.bus, which in turn via
  systemd loads the at-spi bus launcher and registry to respond to the
  bus activation/request. At-spi adds the AT_SPI_BUS property to the X
  root window at load.

  However the AT_SPI_BUS property is hanging around from the greeter
  session, which is confusing software. At-spi only then gets loaded
  from /etc/xdg/autostart/at-spi-dbus-bus.desktop by the mate or gnome
  session binaries, but this happens after unity-panel-service and mate-
  panel are loaded. As such they are inaccessible for the session, or
  until the user kills them and they get reloaded.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1670933/+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 1398151] Re: Clicking the "Text"/"Photo" items in the toolbar doesn't update the selected option in the menu

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

** Changed in: simple-scan (Ubuntu)
   Status: New => Confirmed

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

Title:
  Clicking the "Text"/"Photo" items in the toolbar doesn't update the
  selected option in the menu

Status in simple-scan package in Ubuntu:
  Confirmed

Bug description:
  The Document>Scan menu has two radio buttons: "Text" and "Photo".
  The toolbar menu (arrow after the "Scan" button) also contains those radio 
buttons.

  If you select one of those buttons in the Document>Scan menu, the selected 
option in the toolbar menu is also updated.
  However, when you select one of the radio buttons in the toolbar menu, the 
selected option in the Document>Scan menu is NOT updated. The scan quality is 
successfully changed, though!

  Also, it's very difficult to see which option is selected in the
  toolbar menu, at least with the default Ubuntu theme. The menu has a
  dark background and the "selected" mark is gray.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: simple-scan 3.12.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Dec  1 19:29:26 2014
  DriverPackageVersions:
   libsane 1.0.23-3ubuntu3.1
   libsane-extras N/A
   hplip 3.14.3-0ubuntu3.2
   hpoj N/A
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (49 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Acer Aspire 5742G
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-40-generic 
root=UUID=b4482598-1b35-4927-a61c-9e0529c1c609 ro locale=pt_PT quiet splash 
video.use_native_backlight=1
  SimpleScanLog:

  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire 5742G
  dmi.board.vendor: Acer
  dmi.board.version: V1.30
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.30
  dmi.modalias: 
dmi:bvnAcer:bvrV1.30:bd08/13/2012:svnAcer:pnAspire5742G:pvrV1.30:rvnAcer:rnAspire5742G:rvrV1.30:cvnAcer:ct10:cvrV1.30:
  dmi.product.name: Aspire 5742G
  dmi.product.version: V1.30
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1398151/+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 1673416] Re: Huge calendar icon in preferences window

2017-07-18 Thread Jeremy Bicha

** Changed in: evolution (Ubuntu)
   Status: Expired => Fix Committed

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

Title:
  Huge calendar icon in preferences window

Status in evolution package in Ubuntu:
  Fix Committed

Bug description:
  The preferences window (Edit -> Preferences) shows a huge calendar icon in 
the left side section selector.
  See attached screenshot

  Running evolution 3.22.6
  On fully updated Linux arch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1673416/+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 901807] Investigators Find Car of Man Linked to Murders of His Wife and Girlfriend

2017-07-18 Thread leonid

Hi!

Sheriff’s deputies announced on Monday that they found a car belonging
to 60-year-old Gerald ‘Mike’ http://profmarket16.ru/homeworkx.php?eeef

Very truly yours, Wallace Valentine



** Attachment added: "1A01B83AD9BE624B3D454F0F4C5FF678.jpg"
   
https://bugs.launchpad.net/bugs/901807/+attachment/4916928/+files/1A01B83AD9BE624B3D454F0F4C5FF678.jpg

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

Title:
  password with @ flashes login screen

Status in unity-greeter package in Ubuntu:
  Expired

Bug description:
  Hi,

  My password has an '@' in it (as one of the last characters). When I
  login into Ubuntu 11.10 (64-bits), the screen flashes when I reach the
  '@' during entering the password. The first characters of the password
  go alright, but as soon as I press '@', the screen flashes and return
  to the login screen. After that I have to type in my complete
  password. The second time it goed alright without any problems.

  I did a fresh install of 11.10 and I'm applying all updates when they
  come available.

  If you need extra info, please let me know.

  Kind Regards,
  Marco van der Heide
  --- 
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 11.10
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  NonfreeKernelModules: nvidia
  Package: lightdm 1.0.6-0ubuntu1.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Tags:  oneiric running-unity
  Uname: Linux 3.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/901807/+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 1605896] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

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

** This bug is no longer a duplicate of bug 1605950
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  Varios errores durante la actualización a 16.04 a 16.0.1

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  Date: Sat Jul 23 11:09:19 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-04-26 (87 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.9ubuntu2
   apt  1.3~exp1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-07-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1605896/+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 1605950] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

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

** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  A failure with triggers left unprocessed

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  Date: Sat Jul 23 20:03:27 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-19 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.9ubuntu2
   apt  1.3~exp1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1605950/+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 1617611] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

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

** This bug is no longer a duplicate of bug 1605950
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Sat Aug 27 12:28:39 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-08-21 (6 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc2ubuntu3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-08-27 (0 days ago)
  mtime.conffile..etc.xdg.autostart.gsettings-data-convert.desktop: 
2016-08-23T20:57:41.165020

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1617611/+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 1607167] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

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

** This bug is no longer a duplicate of bug 1605950
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  Testing on the Yakkety Sax (Yak) branch

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Jul 27 23:53:29 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-05-30 (58 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.9ubuntu2
   apt  1.3~exp1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1607167/+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 1612779] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

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

** This bug is no longer a duplicate of bug 1605950
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  just updated ubuntu 16.04 to 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  Date: Fri Aug 12 18:21:37 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-05-18 (85 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.9ubuntu2
   apt  1.3~pre3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-08-12 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1612779/+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 1615052] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

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

** This bug is no longer a duplicate of bug 1605950
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Fri Aug 19 21:09:53 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-08-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc2ubuntu2
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-08-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1615052/+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 1619948] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

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

** This bug is no longer a duplicate of bug 1605950
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  after upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu6
  Uname: Linux 4.7.2-040702-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Sat Sep  3 14:51:07 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-08-28 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc4ubuntu1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-09-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1619948/+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 1448443] Re: Can't execute scripts from home

2017-07-18 Thread Bug Watch Updater

** Changed in: nautilus
   Status: Invalid => Confirmed

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

Title:
  Can't execute scripts from home

Status in Nautilus:
  Confirmed
Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  I can't execute files anymore with Ubuntu 15.04's "Files" program (GUI).
  For example, I install IHMC CmapTools to some directory inside ~/.

  It installs a file named bin/CmapTools with "sh" shebang.
  This file always opens with gedit but it has execute bit on.

  However, if I start this from the command line with "./CmapTools", the
  execution succeeds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1448443/+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 1570182] Re: Support sideloading snap packages

2017-07-18 Thread Jonatã Bolzan Loss

** Tags added: julyshakedown

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

Title:
  Support sideloading snap packages

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  You can't currently sideload a snap (i.e. install a .snap file).

  This requires gnome-software to be subscribed to the .snap mime type
  and gnome-software to be able to extract the snap metadata.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1570182/+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 1705041] [NEW] Two Amazon apps in 17.10 Activities Overview

2017-07-18 Thread Jeremy Bicha

Public bug reported:

There are 2 Amazon apps in Ubuntu 17.10's Activities Overview.

This was a temporary workaround for an upgrade issue with Unity 7.

I believe Didier was going to work on this.

** Affects: ubuntu-settings (Ubuntu)
 Importance: Medium
 Assignee: Didier Roche (didrocks)
 Status: Triaged


** Tags: artful

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

Title:
  Two Amazon apps in 17.10 Activities Overview

Status in ubuntu-settings package in Ubuntu:
  Triaged

Bug description:
  There are 2 Amazon apps in Ubuntu 17.10's Activities Overview.

  This was a temporary workaround for an upgrade issue with Unity 7.

  I believe Didier was going to work on this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1705041/+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 1705033] Re: Xorg crashed with SIGABRT in RRCrtcDetachScanoutPixmap()

2017-07-18 Thread Apport retracing service

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

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 #1705018, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  Xorg crashed with SIGABRT in RRCrtcDetachScanoutPixmap()

Status in nvidia-graphics-drivers package in Ubuntu:
  New

Bug description:
  Start-up crash

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: xserver-xorg-core 2:1.19.3-1ubuntu2
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.102  Mon Jan 16 13:06:29 
PST 2017
   GCC version:  gcc version 6.3.0 20170618 (Ubuntu 6.3.0-19ubuntu1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CrashCounter: 1
  Date: Tue Jul 18 14:47:00 2017
  DistUpgraded: 2017-07-18 11:32:48,330 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3978]
 Subsystem: Lenovo GM107M [GeForce GTX 860M] [17aa:3978]
  InstallationDate: Installed on 2017-04-21 (87 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80DU
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/126/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic.efi.signed 
root=UUID=2754b631-7c4f-4878-8607-86e3b91fdec6 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: nvidia-graphics-drivers
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
   ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
   ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
   ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
   RRCrtcDetachScanoutPixmap ()
  Title: Xorg crashed with SIGABRT in RRCrtcDetachScanoutPixmap()
  UpgradeStatus: Upgraded to artful on 2017-07-18 (0 days ago)
  UserGroups:
   
  dmi.bios.date: 01/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN36WW(V2.00)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: Lenovo Y70-70 Touch
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y70-70 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN36WW(V2.00):bd01/12/2015:svnLENOVO:pn80DU:pvrLenovoY70-70Touch:rvnLENOVO:rnLenovoY70-70Touch:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoY70-70Touch:
  dmi.product.name: 80DU
  dmi.product.version: Lenovo Y70-70 Touch
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+17.10.20170704-0ubuntu1

[Desktop-packages] [Bug 1705030] [NEW] "Ubuntu" session starts Wayland instead of X11 after first reboot

2017-07-18 Thread Ralf Morawe

Public bug reported:

Testing Artful 17.10 daily from 18th July 2017.

When installed to my laptop after the first reboot, GDM shows two
possible sessions on login: "Ubuntu" and "Ubuntu with Wayland". However,
both will open a Wayland session for me. The issue fixes itself after
rebooting once more.

How to reproduce: After fresh installation and reboot, choose "Ubuntu"
in GDM and log in.

What I expected: An X11 GNOME session should open up.

What actually happens: A Wayland GNOME session opens up.
I confirmed this by Alt + F2 -> r -> Enter (giving the message "Restart is not 
available on Wayland").
Also, 'loginctl show-session  -p Type' shows "Type=wayland" ( 
is the session number given by 'loginctl').

I could also reproduce this behaviour on a new fresh install.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-session (not installed)
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Jul 18 15:25:32 2017
InstallationDate: Installed on 2017-07-18 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170718)
SourcePackage: gnome-session
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful julyshakedown

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1705030/+attachment/4916857/+files/JournalErrors.txt

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

Title:
  "Ubuntu" session starts Wayland instead of X11 after first reboot

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Testing Artful 17.10 daily from 18th July 2017.

  When installed to my laptop after the first reboot, GDM shows two
  possible sessions on login: "Ubuntu" and "Ubuntu with Wayland".
  However, both will open a Wayland session for me. The issue fixes
  itself after rebooting once more.

  How to reproduce: After fresh installation and reboot, choose "Ubuntu"
  in GDM and log in.

  What I expected: An X11 GNOME session should open up.

  What actually happens: A Wayland GNOME session opens up.
  I confirmed this by Alt + F2 -> r -> Enter (giving the message "Restart is 
not available on Wayland").
  Also, 'loginctl show-session  -p Type' shows "Type=wayland" ( 
is the session number given by 'loginctl').

  I could also reproduce this behaviour on a new fresh install.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-session (not installed)
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 18 15:25:32 2017
  InstallationDate: Installed on 2017-07-18 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170718)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1705030/+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 1703461] Re: Update to 3.20.5

I tested gnome-software 3.20.5-0ubuntu0.16.04.5 on a fresh installation
of xenial and executed the test plan linked in the description. I didn't
find any regression and issues identified have been confirmed in version
3.20.1+git20170524.0.ea2fe2b0-0ubuntu0.16.04.1 in xenial-update.

Marking as verification-done.

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

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

Title:
  Update to 3.20.5

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  Ubuntu 16.04 is running a version of gnome-software based on 3.20.1 which is 
an older stable release (latest stable release is 3.20.5). The Ubuntu changes 
were managed in a git branch that is difficult to manage. We have not been able 
to bring in all the stable changes to this branch and it is difficult to 
modify. We have rebased our changes on 3.20.5 [1] and propose these as a Stable 
Release Update.

  [1] https://lists.ubuntu.com/archives/ubuntu-
  desktop/2017-June/005011.html

  [Test Case]
  1. Run GNOME Software
  2. Execute the test plan 
https://wiki.ubuntu.com/Process/Merges/TestPlans/gnome-software

  Expected result:
  Running latest stable release, no regressions from 3.20.1

  Observed result:
  Running older release.

  [Regression Potential]
  Due to the number of changes there is a risk of regression. These changes are 
all on a stable branch, so upstream considers them to be safe. We ran this 
version from a PPA to check for issues, and there don't seem to be any problems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1703461/+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 1246527] Re: Gnome System Monitor graphs miss their horizontal and vertical axes

2017-07-18 Thread Carlo Lobrano

Not reproducible on Xubuntu 16.04.2 i386

** Attachment added: "picture of gnome-system-monitor"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1246527/+attachment/4916855/+files/xubuntu32b-monitor.png

** Changed in: gnome-system-monitor (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1246527

Title:
  Gnome System Monitor graphs miss their horizontal and vertical axes

Status in gnome-system-monitor package in Ubuntu:
  Invalid

Bug description:
  System:

  Xubuntu 13.10, 32 bit, fully patched
  Gnome System Monitor package installed: gnome-system-monitor 3.8.2.1-2
  CPU: Intel Atom N270 (Netbook)
  Graphics (output from lspci | grep VGA): 00:02.0 VGA compatible controller: 
Intel Corporation Mobile 945GSE Express Integrated Graphics Controller (rev 03)

  Issue:

  System Monitor > Resources tab presents three graphs (one each for
  "CPU History", "Memory and Swap History", and "Network History"). Each
  of these graphs normally has a narrow border on all four edges, a
  labeled horizontal axis, a labeled vertical axis, and the graph itself
  with the moving traces on a white field with a grid.

  However, in each of the graphs, the horizontal and the vertical axes
  as well as the borders are missing. The areas where these elements
  should be positioned are instead filled with a uniform black colour.
  (The fields with the moving traces are unaffected and behave as
  expected.)

  Note: This bug appears irrespective of the chosen combination of
  settings (including varying the update interval) in the Preferences
  panel > Resources tab of System Monitor.

  Note: This same bug was also present in gnome-system-monitor under
  xubuntu 11.10. It had been patched in xubuntu 12.04, but it reappeared
  in xubuntu 13.04 and remains in xubuntu 13.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1246527/+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 1704628] Re: CUPS keeps crashing 17.04

2017-07-18 Thread Luc D.

I used the command line ubuntu-bug cups. I confirm I get the systematic
internal error pop-up at start-up and I have just submitted again a
report "cups-browsed crashed with SIGSEGV in__strcasecmp_l_avx()" but it
does not help much... . Please let me know how I can get you the "stack
trace", I am not familiar with bug reporting.

Thanks.

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

Title:
  CUPS keeps crashing 17.04

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  cupsd or cups-browser are systematically crashing at start-up. I tried to 
purge and reinstall cups without success. systemctrl status cups shows:
  cups.service - CUPS Scheduler
 Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)
 Active: failed (Result: core-dump) since Sun 2017-07-16 16:58:10 CST; 45s 
ago
   Docs: man:cupsd(8)
Process: 14474 ExecStart=/usr/sbin/cupsd -l (code=dumped, signal=SEGV)
   Main PID: 14474 (code=dumped, signal=SEGV)

  Jul 16 16:58:10 my-desktop systemd[1]: Started CUPS Scheduler.
  Jul 16 16:58:10 my-desktop systemd[1]: cups.service: Main process exited, 
code=dumped, status=11/SEGV
  Jul 16 16:58:10 my-desktop systemd[1]: cups.service: Unit entered failed 
state.
  Jul 16 16:58:10 my-desktop systemd[1]: cups.service: Failed with result 
'core-dump'.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: cups 2.2.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Jul 16 17:06:10 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-07-02 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: System manufacturer System Product Name
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=bf399cdf-9a52-46c0-9d61-daa2bc83cf2f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VPRO:rvrRev1.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/1704628/+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 1705023] [NEW] Do not promote or show classic snaps as installable or display the warning before installation

Public bug reported:

artful desktop

Test Case:
1. Search atom (or any classic snap) and install it

Actual result
It is not installable in gnome-software and fails without a user visible error 
message.

Expected result
When a classic snap is installed from the command line, there is a warning 
message that explains the risk and asks the user to repeat the installation 
with --classic if he understood the message.

In gnome-software it just fails without any message. There are several options:
1. Do not show classic snaps
2. Show the warning and the user must acknowledge before proceeding with the 
installation, in which case the snap is installed in classic mode.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-software 3.24.3-0ubuntu6
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Jul 18 14:02:36 2017
InstallationDate: Installed on 2013-09-03 (1413 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.24.3-0ubuntu6
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

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

Title:
  Do not promote or show classic snaps as installable or display the
  warning before installation

Status in gnome-software package in Ubuntu:
  New

Bug description:
  artful desktop

  Test Case:
  1. Search atom (or any classic snap) and install it

  Actual result
  It is not installable in gnome-software and fails without a user visible 
error message.

  Expected result
  When a classic snap is installed from the command line, there is a warning 
message that explains the risk and asks the user to repeat the installation 
with --classic if he understood the message.

  In gnome-software it just fails without any message. There are several 
options:
  1. Do not show classic snaps
  2. Show the warning and the user must acknowledge before proceeding with the 
installation, in which case the snap is installed in classic mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.24.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 18 14:02:36 2017
  InstallationDate: Installed on 2013-09-03 (1413 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.24.3-0ubuntu6
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1705023/+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 1705024] [NEW] Output to BT speaker stops when laptop is unplugged from AC

Public bug reported:

artful desktop

Test Case
1. Connect a laptop to a power supply
2. Pair a BT speaker
3. Play some music with VLC
4. Disconnect the laptop from AC to switch to battery

Expected result
The music continues playing

Actual result
It stops. pavucontrol shows that the output device is still the BT speaker and 
the vumeter is still alive but there is not sound on the speaker. Only powering 
off/on the speaker makes it work again.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: pulseaudio 1:10.0-2ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC1D0c:   j-lallement   1293 F...m pulseaudio
 /dev/snd/controlC1:  j-lallement   1293 F pulseaudio
 /dev/snd/controlC0:  j-lallement   1293 F pulseaudio
CurrentDesktop: GNOME
Date: Tue Jul 18 14:40:02 2017
InstallationDate: Installed on 2013-09-03 (1413 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/29/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX32VD.214
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX32VD
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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX32VD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug artful

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

Title:
  Output to BT speaker stops when laptop is unplugged from AC

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  artful desktop

  Test Case
  1. Connect a laptop to a power supply
  2. Pair a BT speaker
  3. Play some music with VLC
  4. Disconnect the laptop from AC to switch to battery

  Expected result
  The music continues playing

  Actual result
  It stops. pavucontrol shows that the output device is still the BT speaker 
and the vumeter is still alive but there is not sound on the speaker. Only 
powering off/on the speaker makes it work again.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   j-lallement   1293 F...m pulseaudio
   /dev/snd/controlC1:  j-lallement   1293 F pulseaudio
   /dev/snd/controlC0:  j-lallement   1293 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Jul 18 14:40:02 2017
  InstallationDate: Installed on 2013-09-03 (1413 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  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/pulseaudio/+bug/1705024/+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 1702794] Re: Please add module-switch-on-connect to default.pa

2017-07-18 Thread Khurshid Alam

After this my bluetooth speaker simply refuses to switch to a2dp_sink
profile. It always stays at hsp no mater what I do.

So far it wasn't enabled exactly for that reason. Read
https://bugs.freedesktop.org/show_bug.cgi?id=93898 and
https://bugs.freedesktop.org/show_bug.cgi?id=73325#c52

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

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

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

Title:
  Please add module-switch-on-connect to default.pa

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  This way once a user pairs & connects a bluetooth speaker device pulseaudio 
will auto switch to it. 
  As it stands now users have to open sound settings & switch manually. It's 
bad enough that auto discover & connect don't work, (can be scripted thru 
bluetoothctl), no sense adding to frustration

  In the ### Automatically load driver modules for Bluetooth hardware
  section

  
  .ifexists module-switch-on-connect.so
  load-module module-switch-on-connect
  .endif

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doug   1843 F pulseaudio
   /dev/snd/controlC0:  doug   1843 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul  6 20:02:15 2017
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 74CN44WW(V3.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIQY0Y1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y510P
  dmi.modalias: 
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
  dmi.product.name: 20217
  dmi.product.version: Lenovo IdeaPad Y510P
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2017-07-04T13:42:27.651527

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1702794/+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 1704750] Re: Display artefacts with Skylake i7 HD Graphics 530

2017-07-18 Thread Bogdan Harjoc

One important detail: I also had an AMD radeon video card plugged in but
the display was connected to the integrated VGA port. After removing the
radeon card, the artefacts went away.

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

Title:
  Display artefacts with Skylake i7 HD Graphics 530

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

Bug description:
  On an up-to-date ubuntu 16.04.02-amd64 I started seeing some minor
  display corruption after moving the hard disk containing the ubuntu
  installation from an older Dell Optiplex (Ivy Bridge i7) to another
  Optiplex with a Skylake i7-6700 CPU.

  I took a photo of the screen corruption which I attached here.

  Xorg.0.log lists the used driver as 'intel'.

  I am using the stable chrome release, currently at "Version
  59.0.3071.115 (Official Build) (64-bit)".

  The corruption (display artefacts) usually show up when hovering the
  mouse over the 'back/forward' browser buttons, or after navigating
  backwards/forwards and waiting a couple of seconds. Sometimes they go
  away leaving a normal browser window, other times the artefacts remain
  as shown in the attached photo.

  Browser flags I have tried include combinations of:

  --wm-window-animations-disabled 
  --disable-gpu-driver-bug-workarounds 
  --enable-native-gpu-memory-buffers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1704750/+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 1705014] Re: Kannada l10n package missing

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

** Changed in: libreoffice-l10n (Ubuntu)
   Status: New => Confirmed

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

Title:
  Kannada l10n package missing

Status in libreoffice-l10n package in Ubuntu:
  Confirmed

Bug description:
  The language pack for Kannada language is not available as part of
  libreoffice-l10n while I can see there are other Indic languages here.
  Request the maintainers to include libreoffice-l10n-kn package for
  Kannada language interface in LibreOffice. Community has been
  translating strings on Pootle.

  Thank you!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice-l10n/+bug/1705014/+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 1699772] Re: linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic Regression: many user-space apps crashing

2017-07-18 Thread Norbert

In 32-bit Zesty linux 4.10.0-28-generic still crashes LibreOffice Base.

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

Title:
  linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-
  image-4.4.0-81-generic, linux-image-3.13.0-121-generic Regression:
  many user-space apps crashing

Status in LibreOffice:
  Won't Fix
Status in commons-daemon package in Ubuntu:
  Confirmed
Status in eclipse package in Ubuntu:
  Confirmed
Status in imagej package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in octave package in Ubuntu:
  Confirmed
Status in python-jpype package in Ubuntu:
  Confirmed
Status in rustc package in Ubuntu:
  Confirmed
Status in scilab package in Ubuntu:
  Confirmed
Status in linux package in Debian:
  Confirmed

Bug description:
  Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10)

  linux-image-4.4.0-81-generic appears to contain a regression, probably
  related to the CVE-2017-1000364 fix backport / patch.

  Using this kernel, the Oracle Java browser plugin always crashes
  during stack-related actions on initialization. This means, the plugin
  completely stopped working.

  
  It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to 
CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also 
contains a fix for CVE-2017-1000364.


  uname -a:

  > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06
  UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


  I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as
  well as Iceweasel / Firefox/3.5.16 in a chroot.

  Using linux-image-4.4.0-81-generic it crashes in all combinations
  while with both other kernels it works.

  
  I was not able to obtain any detailed crash information from Firefox 51.0.1, 
but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace 
which shows the relation to stack operations performed by the plugin, even 
without proper debug symbols:

  
  > (gdb) bt full
  > #0  0x7fa06d805307 in _expand_stack_to(unsigned char*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #1  0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, 
unsigned char*) ()
  >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #2  0x7fa06d80cf0b in JVM_handle_linux_signal () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #3  0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #4  

  
  I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6.

  
  The crash will be triggered by any applet, for example the test applet at:

  * https://java.com/en/download/installed8.jsp

  
  I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow 
apparently does not allow me to use apport to report this bug:

  > $ LANG= apport-cli linux-image-4.4.0-81-generic
  > 
  > *** Collecting problem information
  > 
  > The collected information can be sent to the developers to improve the
  > application. This might take a few minutes.
  > .
  > 
  > *** Problem in linux-image-4.4.0-81-generic
  > 
  > The problem cannot be reported:
  > 
  > This is not an official KDE package. Please remove any third party package 
and try again.

  If someone can tell me how to get apport working for this package, I
  can use it to collect additional information, but (unfortunately?) the
  problem should be fairly easy to reproduce...

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1699772/+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 1705014] [NEW] Kannada l10n package missing

2017-07-18 Thread ಯೋಗೇಶ್

Public bug reported:

The language pack for Kannada language is not available as part of
libreoffice-l10n while I can see there are other Indic languages here.
Request the maintainers to include libreoffice-l10n-kn package for
Kannada language interface in LibreOffice. Community has been
translating strings on Pootle.

Thank you!

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

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

Title:
  Kannada l10n package missing

Status in libreoffice-l10n package in Ubuntu:
  New

Bug description:
  The language pack for Kannada language is not available as part of
  libreoffice-l10n while I can see there are other Indic languages here.
  Request the maintainers to include libreoffice-l10n-kn package for
  Kannada language interface in LibreOffice. Community has been
  translating strings on Pootle.

  Thank you!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice-l10n/+bug/1705014/+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 1351286] Re: colord-sane assert failure: colord-sane: simple-watch.c:454: avahi_simple_poll_prepare: Assertion `s->state == STATE_INIT || s->state == STATE_DISPATCHED || s->sta

2017-07-18 Thread fubbleskag

** Tags added: verification-done-xenial

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

Title:
  colord-sane assert failure: colord-sane: simple-watch.c:454:
  avahi_simple_poll_prepare: Assertion `s->state == STATE_INIT ||
  s->state == STATE_DISPATCHED || s->state == STATE_FAILURE' failed.

Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends source package in Trusty:
  Triaged
Status in sane-backends source package in Xenial:
  Fix Committed
Status in sane-backends source package in Yakkety:
  Fix Committed
Status in sane-backends source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  A bug in the SANE Kodak driver can cause a SANE device scan to crash the 
client that is using it (e.g. colord, simple-scan).

  [Test Case]
  1. Run a SANE client on a system that is failing Avahi scans (exact cause not 
determined).

  Expected result:
  Client works without crashing.

  Observed result:
  Client crashes.

  [Regression Potential]
  Code fix could cause a change in behaviour of successful Avahi scans for 
Kodak devices, though the fix matches the Avahi documentation for correct usage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1351286/+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 1666078] Re: package nvidia-331-updates-uvm 340.96-0ubuntu3.16.04.1 failed to install/upgrade: there is no script in the new version of the package - giving up

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

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Status: New => Confirmed

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

Title:
  package nvidia-331-updates-uvm 340.96-0ubuntu3.16.04.1 failed to
  install/upgrade: there is no script in the new version of the package
  - giving up

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  I was having the very same problem with Ubuntu 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: nvidia-331-updates-uvm 340.96-0ubuntu3.16.04.1
  ProcVersionSignature: Ubuntu 4.8.0-38.41-generic 4.8.17
  Uname: Linux 4.8.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.2
  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
  Date: Sun Feb 19 00:37:23 2017
  DistUpgraded: 2017-02-19 11:04:27,837 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Esecuzione del processo figlio 
"./xorg_fix_proprietary.py" non riuscita (No such file or directory) (8))
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-63-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-38-generic, x86_64: installed
   nvidia-340, 340.101, 4.4.0-63-generic, x86_64: installed
   nvidia-340, 340.101, 4.8.0-38-generic, x86_64: installed
  ErrorMessage: there is no script in the new version of the package - giving up
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:1858]
  InstallationDate: Installed on 2012-08-11 (1653 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  Lsusb:
   Bus 002 Device 003: ID 05c8:0223 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard Presario CQ58 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-38-generic 
root=UUID=7f94bba2-1af3-40f8-bcb0-b07de2fdd63a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-331-updates-uvm 340.96-0ubuntu3.16.04.1 failed to 
install/upgrade: there is no script in the new version of the package - giving 
up
  UpgradeStatus: Upgraded to yakkety on 2017-02-19 (0 days ago)
  dmi.bios.date: 04/19/2012
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.12
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1858
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 65.15
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.12:bd04/19/2012:svnHewlett-Packard:pnPresarioCQ58NotebookPC:pvr078310203D10002620100:rvnHewlett-Packard:rn1858:rvr65.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: Presario CQ58 Notebook PC
  dmi.product.version: 078310203D10002620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.10.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Mon Feb 20 00:00:38 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1666078/+subscriptions

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

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

2017-07-18 Thread Adam Conrad

This will need a coordinated transactional release, when we're ready,
please don't promote it.

-- 
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:
  Invalid
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:
  Fix Committed
Status in libdrm source package in Xenial:
  Fix Committed
Status in libinput source package in Xenial:
  Fix Committed
Status in libwacom source package in Xenial:
  Fix Committed
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:
  Fix Committed
Status in vulkan source package in Xenial:
  Fix Committed
Status in wayland source package in Xenial:
  Fix Committed
Status in x11proto-core source package in Xenial:
  Fix Committed
Status in xfonts-utils 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:
  Invalid
Status in xorg-server-hwe-16.04 source package in Xenial:
  Fix Committed

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 1705006] [NEW] package libvoikko1:amd64 4.1-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configur

2017-07-18 Thread ian

Public bug reported:

The Problem occurred just after I switch the desktop computer on.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libvoikko1:amd64 4.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.4
Architecture: amd64
Date: Tue Jul 18 10:15:03 2017
Dependencies:
 gcc-6-base 6.3.0-12ubuntu2
 libc6 2.24-9ubuntu2.2
 libgcc1 1:6.3.0-12ubuntu2
 libstdc++6 6.3.0-12ubuntu2
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-06-26 (22 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: libvoikko
Title: package libvoikko1:amd64 4.1-1ubuntu1 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libvoikko (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 libvoikko in Ubuntu.
https://bugs.launchpad.net/bugs/1705006

Title:
  package libvoikko1:amd64 4.1-1ubuntu1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in libvoikko package in Ubuntu:
  New

Bug description:
  The Problem occurred just after I switch the desktop computer on.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libvoikko1:amd64 4.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  Date: Tue Jul 18 10:15:03 2017
  Dependencies:
   gcc-6-base 6.3.0-12ubuntu2
   libc6 2.24-9ubuntu2.2
   libgcc1 1:6.3.0-12ubuntu2
   libstdc++6 6.3.0-12ubuntu2
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-06-26 (22 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: libvoikko
  Title: package libvoikko1:amd64 4.1-1ubuntu1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvoikko/+bug/1705006/+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 1705006] Re: package libvoikko1:amd64 4.1-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurat

2017-07-18 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 libvoikko in Ubuntu.
https://bugs.launchpad.net/bugs/1705006

Title:
  package libvoikko1:amd64 4.1-1ubuntu1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in libvoikko package in Ubuntu:
  New

Bug description:
  The Problem occurred just after I switch the desktop computer on.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libvoikko1:amd64 4.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  Date: Tue Jul 18 10:15:03 2017
  Dependencies:
   gcc-6-base 6.3.0-12ubuntu2
   libc6 2.24-9ubuntu2.2
   libgcc1 1:6.3.0-12ubuntu2
   libstdc++6 6.3.0-12ubuntu2
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-06-26 (22 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: libvoikko
  Title: package libvoikko1:amd64 4.1-1ubuntu1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvoikko/+bug/1705006/+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 1700994] Re: Installed snaps show twice in GNOME Software

SRU verification for Xenial:
I have reproduced the problem with appstream-glib 0.5.13-1ubuntu4 in 
xenial-updates and have verified that the version of appstream-glib 
0.5.13-1ubuntu5 in -proposed fixes the issue.

Marking as verification-done


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

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

Title:
  Installed snaps show twice in GNOME Software

Status in appstream-glib package in Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in appstream-glib source package in Xenial:
  Fix Committed
Status in gnome-software source package in Xenial:
  In Progress
Status in appstream-glib source package in Zesty:
  Fix Committed
Status in gnome-software source package in Zesty:
  In Progress
Status in appstream-glib source package in Artful:
  Fix Released
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Installed snaps show twice in GNOME Software. The solution is to not scan the 
installed .desktop files - there is sufficient information provided by snapd.

  [Test Case]
  1. Open GNOME Software
  2. Install a snap (e.g. ohmygiraffe)
  3. Switched to "Installed" tab

  Expected result:
  ohmygiraffe is shown once in the installed list.

  Observed result:
  ohmygiraffe is shown twice. One entry has data from the snap metadata, the 
other from the installed .desktop file.

  [Regression Potential]
  There is some risk of breaking other appstream behaviour. The risk is low 
because we only filter out the snapd specific directory that contains this data.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1700994/+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 1703461] Re: Update to 3.20.5

** Description changed:

  [Impact]
  Ubuntu 16.04 is running a version of gnome-software based on 3.20.1 which is 
an older stable release (latest stable release is 3.20.5). The Ubuntu changes 
were managed in a git branch that is difficult to manage. We have not been able 
to bring in all the stable changes to this branch and it is difficult to 
modify. We have rebased our changes on 3.20.5 [1] and propose these as a Stable 
Release Update.
  
  [1] https://lists.ubuntu.com/archives/ubuntu-
  desktop/2017-June/005011.html
  
  [Test Case]
  1. Run GNOME Software
+ 2. Execute the test plan 
https://wiki.ubuntu.com/Process/Merges/TestPlans/gnome-software
  
  Expected result:
  Running latest stable release, no regressions from 3.20.1
  
  Observed result:
  Running older release.
  
  [Regression Potential]
  Due to the number of changes there is a risk of regression. These changes are 
all on a stable branch, so upstream considers them to be safe. We ran this 
version from a PPA to check for issues, and there don't seem to be any problems.

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

Title:
  Update to 3.20.5

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  Ubuntu 16.04 is running a version of gnome-software based on 3.20.1 which is 
an older stable release (latest stable release is 3.20.5). The Ubuntu changes 
were managed in a git branch that is difficult to manage. We have not been able 
to bring in all the stable changes to this branch and it is difficult to 
modify. We have rebased our changes on 3.20.5 [1] and propose these as a Stable 
Release Update.

  [1] https://lists.ubuntu.com/archives/ubuntu-
  desktop/2017-June/005011.html

  [Test Case]
  1. Run GNOME Software
  2. Execute the test plan 
https://wiki.ubuntu.com/Process/Merges/TestPlans/gnome-software

  Expected result:
  Running latest stable release, no regressions from 3.20.1

  Observed result:
  Running older release.

  [Regression Potential]
  Due to the number of changes there is a risk of regression. These changes are 
all on a stable branch, so upstream considers them to be safe. We ran this 
version from a PPA to check for issues, and there don't seem to be any problems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1703461/+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 1704998] [NEW] Flashing LEDs (~2min interval) on Logitech Performance MX (USB Wireless) Mouse

2017-07-18 Thread rando

Public bug reported:

Hi,

Since my upgrade from Ubuntu 14.04 to 16.04.2 LTS the battery indicator
LEDs on my Logitech Performance MX Mouse light up about every 120
seconds. Depending on the charging level 1, 2 or 3 LEDs light up green.
When I boot into recovery mode or disable upower after a normal boot
this behaviour doesn't occur. The expected behaviour is that the LEDs do
not light up every 2 minutes but instead only when the charging levels
drop from "3 to 2 LEDs" and "2 to 1 LEDs" - that's how it works with
Ubuntu 14.04 (and Windows 10).

Using the usbmon module I captured the usb traffic and when the LEDs
light up the following is logged by "cat
/sys/kernel/debug/usb/usbmon/2u":

8807a16ddd80 290929349 S Co:2:009:0 s 21 09 0210 0002 0007 7 = 10018107 
00
8807a16ddd80 290929492 C Co:2:009:0 0 7 >
88074c55b180 290932022 C Ii:2:009:3 0:2 7 = 10018f81 070900
88074c55b180 290932033 S Ii:2:009:3 -115:2 32 <
8807f4332540 296834836 S Co:2:009:0 s 21 09 0210 0002 0007 7 = 10028107 
00
8807f4332540 296835012 C Co:2:009:0 0 7 >
88074c55b180 298689874 C Ii:2:009:3 0:2 7 = 10028107 05
88074c55b180 298689892 S Ii:2:009:3 -115:2 32 <

"upower --monitor-detail" shows the following when the LEDs light up:

  [10:22:41.041]device changed: 
/org/freedesktop/UPower/devices/mouse_0003o046Do101Ax0006
native-path:  
/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.8/2-1.8.4/2-1.8.4:1.2/0003:046D:C52B.0004/0003:046D:101A.0006
vendor:   Logitech, Inc.
model:Performance MX
serial:   F8A45D1F
power supply: no
updated:  Tue 18 Jul 2017 10:22:40 AM UTC (1 seconds ago)
has history:  yes
has statistics:   no
mouse
  present: yes
  rechargeable:yes
  state:   discharging
  warning-level:   none
  percentage:  55%
  icon-name:  'battery-good-symbolic'

Here is the output from "lsusb -v" for the Logitech Unifying Receiver in
use:

Bus 002 Device 009: ID 046d:c52b Logitech, Inc. Unifying Receiver
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 8
  idVendor   0x046d Logitech, Inc.
  idProduct  0xc52b Unifying Receiver
  bcdDevice   12.01
  iManufacturer   1 Logitech
  iProduct2 USB Receiver
  iSerial 0
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   84
bNumInterfaces  3
bConfigurationValue 1
iConfiguration  4 RQR12.01_B0019
bmAttributes 0xa0
  (Bus Powered)
  Remote Wakeup
MaxPower   98mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass 3 Human Interface Device
  bInterfaceSubClass  1 Boot Interface Subclass
  bInterfaceProtocol  1 Keyboard
  iInterface  0
HID Device Descriptor:
  bLength 9
  bDescriptorType33
  bcdHID   1.11
  bCountryCode0 Not supported
  bNumDescriptors 1
  bDescriptorType34 Report
  wDescriptorLength  59
 Report Descriptors:
   ** UNAVAILABLE **
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0008  1x 8 bytes
bInterval   8
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber1
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass 3 Human Interface Device
  bInterfaceSubClass  1 Boot Interface Subclass
  bInterfaceProtocol  2 Mouse
  iInterface  0
HID Device Descriptor:
  bLength 9
  bDescriptorType33
  bcdHID   1.11
  bCountryCode0 Not supported
  bNumDescriptors 1

[Desktop-packages] [Bug 1697565] Re: Snaps without icons don't show as installed

I see no improvement with 3.20.5-0ubuntu0.16.04.5 in xenial. I tried
with openscad-plars and it is not listed in the installed packages.
However moon-buggy is listed but it has an icon, so it is not a good
example for this test case.

Marking as verification-failed for xenial

** Tags removed: verification-needed-xenial
** Tags added: verification-failed-xenial

** Description changed:

  [Impact]
  Snaps without icons don't show in the installed tab. They do show in search, 
because the icon is sourced from the store.
  
  [Test Case]
  1. Open GNOME Software
- 2. Install a snap without an icon (e.g. moon-buggy)
+ 2. Install a snap without an icon (e.g. openscad-plars)
  3. Close GNOME Software
  4. Open GNOME Software
  5. Click "installed" tab
  
  Expected result:
  Installed snap is shown
  
  Observed result:
  Snap is not shown
  
  [Regression Potential]
  The code was refactored to download the store information for installed 
snaps. This means the store icon shows if the installed snap didn't have one. 
There is some risk of new bugs being caused by the refactoring.

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

Title:
  Snaps without icons don't show as installed

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Yakkety:
  Won't Fix
Status in gnome-software source package in Zesty:
  Fix Released
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Snaps without icons don't show in the installed tab. They do show in search, 
because the icon is sourced from the store.

  [Test Case]
  1. Open GNOME Software
  2. Install a snap without an icon (e.g. openscad-plars)
  3. Close GNOME Software
  4. Open GNOME Software
  5. Click "installed" tab

  Expected result:
  Installed snap is shown

  Observed result:
  Snap is not shown

  [Regression Potential]
  The code was refactored to download the store information for installed 
snaps. This means the store icon shows if the installed snap didn't have one. 
There is some risk of new bugs being caused by the refactoring.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1697565/+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 1689033] Re: A few missing icons in version 2.4.3

2017-07-18 Thread Sebastien Bacher

the issue was fixed upstream with
https://git.gnome.org/browse/gtk+/commit/?id=a6dcb80fb

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

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

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

Title:
  A few missing icons in version 2.4.3

Status in gdk-pixbuf:
  Invalid
Status in GTK+:
  Fix Released
Status in easytag package in Ubuntu:
  Confirmed
Status in gdk-pixbuf package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Fix Committed

Bug description:
  A few icons are missing in version 2.4.3 for zesty (and probably
  artful), see https://i.imgur.com/Cl4o36Sr.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdk-pixbuf/+bug/1689033/+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 1704765] Re: can't drag file from desktop to folder window on Artful

2017-07-18 Thread Adam Dingle

Yes, I see this when logged into the (default) GNOME Wayland session.

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

Title:
  can't drag file from desktop to folder window on Artful

Status in nautilus package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 17.10 (Artful).  If I create a text file on my
  desktop and then attempt to drag it into a Nautilus folder window, it
  fails: when I release the mouse cursor over the folder window nothing
  happens and the file is not moved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1704765/+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 1704650] Re: Can't uninstall Firefox in Ubuntu Mate

2017-07-18 Thread Paul White

** Package changed: firefox (Ubuntu) => ubuntu-mate-meta (Ubuntu)

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

Title:
  Can't uninstall Firefox in Ubuntu Mate

Status in ubuntu-mate-meta package in Ubuntu:
  New

Bug description:
  Does anyone know why Ubuntu MATE meta-packages require Firefox? A meta
  package for a distribution depending on a browser seems strange to me.
  For example, on Ubuntu (normal Ubuntu) removing Firefox does not
  remove the ubuntu-desktop metapackage. I'm fairly certain that other
  distributions based on Ubuntu don't have this problem either. If you
  ask me, this seems like a bug we should file and help fix. I think the
  correct action here would be for the Ubuntu MATE metapackages to set
  Firefox as a "recommended" package rather than a "required" one. I
  could be wrong on that though.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-meta/+bug/1704650/+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 1704281] Re: nvidia-graphics-drivers-340 340.102-0ubuntu0.16.04.1 ADT test failure with linux-hwe 4.10.0-27.30~16.04.2

2017-07-18 Thread Alberto Milone

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

** This bug has been marked a duplicate of bug 1677327
   SRU request: dkms build fails with zesty hwe kernel [error: too few 
arguments to function ‘NV_GET_USER_PAGES’]

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

Title:
  nvidia-graphics-drivers-340 340.102-0ubuntu0.16.04.1 ADT test failure
  with linux-hwe 4.10.0-27.30~16.04.2

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-340/20170710_033239_3a664@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-340/20170710_08_3a664@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1704281/+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 1687981] Re: Backport packages for 16.04.3 HWE stack

2017-07-18 Thread Łukasz Zemczak

So what's the final status of the SRU? It was verified before but then
got held off. Does it need another re-test?

-- 
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:
  Invalid
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:
  Fix Committed
Status in libdrm source package in Xenial:
  Fix Committed
Status in libinput source package in Xenial:
  Fix Committed
Status in libwacom source package in Xenial:
  Fix Committed
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:
  Fix Committed
Status in vulkan source package in Xenial:
  Fix Committed
Status in wayland source package in Xenial:
  Fix Committed
Status in x11proto-core source package in Xenial:
  Fix Committed
Status in xfonts-utils 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:
  Invalid
Status in xorg-server-hwe-16.04 source package in Xenial:
  Fix Committed

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 1702071] Re: Search spins forever, returns no results.

2017-07-18 Thread Colin Law

Robert - yes I think you are right. In fact the issue went away after I
rebooted (at least I think that was what did it). I need to re-install
the OS and see if it happens again.

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

Title:
  Search spins forever, returns no results.

Status in gnome-software package in Ubuntu:
  New

Bug description:
  alan@gort:~$ apt-cache policy gnome-software
  gnome-software:
Installed: 3.20.5-0ubuntu0.16.04.1.1
Candidate: 3.20.5-0ubuntu0.16.04.1.1
Version table:
   *** 3.20.5-0ubuntu0.16.04.1.1 500
  500 http://ppa.launchpad.net/ubuntu-desktop/gnome-software/ubuntu 
xenial/main amd64 Packages
  100 /var/lib/dpkg/status
   3.20.1+git20170524.0.ea2fe2b0-0ubuntu0.16.04.1 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  I mentioned to Robert last week that I keep getting the spinner and no
  results returned when searching in g-s on 16.04. He suggested I update
  to the version in the PPA and enable logging to capture what's
  happening. Log attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1702071/+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 1704946] [NEW] package emacs24 24.5+1-8ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-07-18 Thread JAVIER HURTADO

Public bug reported:

i was installing several packages, and i received an error message, but
i am not sure which package generated it.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: emacs24 24.5+1-8ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.4
Architecture: amd64
Date: Tue Jul 18 00:59:39 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-07-18 (0 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: emacs24
Title: package emacs24 24.5+1-8ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: emacs24 (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 emacs24 in Ubuntu.
https://bugs.launchpad.net/bugs/1704946

Title:
  package emacs24 24.5+1-8ubuntu2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in emacs24 package in Ubuntu:
  New

Bug description:
  i was installing several packages, and i received an error message,
  but i am not sure which package generated it.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: emacs24 24.5+1-8ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  Date: Tue Jul 18 00:59:39 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-07-18 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: emacs24
  Title: package emacs24 24.5+1-8ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/emacs24/+bug/1704946/+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 1689825] Re: gnome-keyring not unlocked on boot

2017-07-18 Thread Sébastien Tisserant

Same here. Uninstalling dbus-user-session solved the issue.

Thanks to all contributors.

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

Title:
  gnome-keyring not unlocked on boot

Status in D-Bus:
  New
Status in chromium-browser package in Ubuntu:
  Invalid
Status in flatpak package in Ubuntu:
  Confirmed
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus/+bug/1689825/+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 149519] ❤After Grisly Killings in Pennsylvania, a Quick Deal to Spare Execution

2017-07-18 Thread kappe

Dear friend!

The police had been investigating the disappearance of four men in
Pennsylvania for only a week when
http://abpconsultant.ru/doctrinex.php?aaab


My Best, MIRCO CPPELLETTI


From: Bug 149519 [mailto:149...@bugs.launchpad.net]
Sent: Tuesday, July 18, 2017 2:40 AM
To: ka...@inwind.it
Subject: it also looks great! :-)

Things off the  top of  my  head:

Large file transfers to /Public.  Could fill up all space on  his hard
drive with goat porn.

Even  better,  is there a folder  that  goes to  "Desktop"?   This
should lead to  the desktop off all user profiles.  You could some
social  engineering  here.  Put something extremely interesting  here,
and have him click on it.   Could be something  just to spook him, or
something that  executes a malicious payload.



** Attachment added: "FD0AC8F5766D3A0C79BC57148BD5DCCD.jpg"
   
https://bugs.launchpad.net/bugs/149519/+attachment/4916607/+files/FD0AC8F5766D3A0C79BC57148BD5DCCD.jpg

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

Title:
  firefox-bin crashed with SIGSEGV in __kernel_vsyscall()

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Binary package hint: firefox

  firefox-bin crashed with SIGSEGV in __kernel_vsyscall()

  ProblemType: Crash
  Architecture: i386
  CrashCounter: 1
  Date: Fri Oct  5 19:14:46 2007
  DistroRelease: Ubuntu 7.10
  ExecutablePath: /usr/lib/firefox/firefox-bin
  NonfreeKernelModules: fglrx
  Package: firefox 2.0.0.6+2-0ubuntu4
  PackageArchitecture: i386
  ProcCmdline: /usr/lib/firefox/firefox-bin
  ProcCwd: /home/alex
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: firefox
  StacktraceTop:
   __kernel_vsyscall ()
   raise () from /lib/tls/i686/cmov/libpthread.so.0
   ?? ()
   ?? ()
   ?? ()
  Title: firefox-bin crashed with SIGSEGV in __kernel_vsyscall()
  Uname: Linux alex-laptop 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 
2007 i686 GNU/Linux
  UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev 
powerdev scanner video

  SegvAnalysis:
   Segfault happened at: 0xe410 <__kernel_vsyscall+16>: pop%ebp
   PC (0xe410) ok
   source "%ebp" ok
   destination "(%esp)" (0xbfc25f80) ok
   SP (0xbfc25f80) ok
   Reason could not be automatically determined. (Unhandled exception in kernel 
code?)
  SegvReason: Reason could not be automatically determined. (Unhandled 
exception in kernel code?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/149519/+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 1663097] Re: Show featured snaps

SRU verification for Xenial:
I have reproduced the problem with gnome-software 
3.20.1+git20170524.0.ea2fe2b0-0ubuntu0.16.04.1 in xenial-updates and have 
verified that the version of gnome-software 3.20.5-0ubuntu0.16.04.5 in 
-proposed fixes the issue (there are snaps in the editor's pick section - atom, 
corebird)

Marking as verification-done


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

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

Title:
  Show featured snaps

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Yakkety:
  Won't Fix
Status in gnome-software source package in Zesty:
  Fix Released
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  GNOME Software doesn't show any snaps in the "Editor's Picks" section. snapd 
added a new feature to return snaps in the "featured" section and should be 
shown in GNOME Software.

  [Test Case]
  1. Open GNOME Software

  Expected result:
  Some of the "Editor's Picks" apps should be snaps.

  Observed result:
  There are no snaps shown.

  [Regression Potential]
  Some risk of new behaviour adversely affecting GNOME Software startup.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1663097/+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 1704942] [NEW] weather in bbc say s i need flash player

2017-07-18 Thread John Williams

Public bug reported:

on bbc site weather news says i need flash player to watch this content

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: firefox 54.0+build3-0ubuntu0.14.04.1
ProcVersionSignature: Ubuntu 3.13.0-123.172-generic 3.13.11-ckt39
Uname: Linux 3.13.0-123-generic i686
AddonCompatCheckDisabled: False
ApportVersion: 2.14.1-0ubuntu3.24
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  john   1995 F pulseaudio
 /dev/snd/controlC0:  john   1995 F pulseaudio
BuildID: 20170612122526
Channel: Unavailable
CurrentDesktop: Unity
Date: Tue Jul 18 08:39:15 2017
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2016-11-09 (250 days ago)
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
IpRoute:
 default via 192.168.0.1 dev eth0  proto static 
 192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.5  metric 1
IwConfig:
 lono wireless extensions.
 
 eth0  no wireless extensions.
Locales: extensions.sqlite corrupt or missing
MostRecentCrashID: bp-df71432e-3348-41fd-9ed8-632352170325
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefErrors: Unexpected character '' before pref @ 
[Profile]/extensions/amin.eft_bmno...@gmail.com/defaults/preferences/pref.js:1
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=54.0/20170612122526 (In use)
RfKill:
 
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to trusty on 2017-03-25 (114 days ago)
WifiSyslog:
 Jul 18 06:44:50 john-HP-Compaq-dx2420-Microtower kernel: [ 1852.643895] perf 
samples too long (2508 > 2500), lowering kernel.perf_event_max_sample_rate to 
5
 Jul 18 07:49:34 john-HP-Compaq-dx2420-Microtower kernel: [ 5735.927810] perf 
samples too long (5005 > 5000), lowering kernel.perf_event_max_sample_rate to 
25000
 Jul 18 08:15:40 john-HP-Compaq-dx2420-Microtower kernel: [ 7302.606495] 
systemd-hostnamed[6464]: Warning: nss-myhostname is not installed. Changing the 
local hostname might make it unresolveable. Please install nss-myhostname!
 Jul 18 08:25:48 john-HP-Compaq-dx2420-Microtower kernel: [ 7910.212175] 
systemd-hostnamed[6950]: Warning: nss-myhostname is not installed. Changing the 
local hostname might make it unresolveable. Please install nss-myhostname!
dmi.bios.date: 02/20/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 5.18
dmi.board.name: 2A78h
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: CZC94064H4
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.18:bd02/20/2009:svnHewlett-Packard:pnHPCompaqdx2420Microtower:pvr:rvnMSI:rn2A78h:rvr1.0:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: HP Compaq dx2420 Microtower
dmi.sys.vendor: Hewlett-Packard

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


** Tags: apport-bug i386 trusty

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

Title:
  weather in bbc say s i need flash player

Status in firefox package in Ubuntu:
  New

Bug description:
  on bbc site weather news says i need flash player to watch this
  content

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: firefox 54.0+build3-0ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 3.13.0-123.172-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-123-generic i686
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  john   1995 F pulseaudio
   /dev/snd/controlC0:  john   1995 F pulseaudio
  BuildID: 20170612122526
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Tue Jul 18 08:39:15 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2016-11-09 (250 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  IpRoute:
   default via 192.168.0.1 dev eth0  proto static 
   192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.5  metric 1
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-df71432e-3348-41fd-9ed8-632352170325
  Plugins: Shockwave Flash -

[Desktop-packages] [Bug 1704937] [NEW] generate-id() returns non-unique values

2017-07-18 Thread Dmitrj Yelizarov

Public bug reported:

It seems related to patch https://bugs.debian.org/823857.
See attachment,
The command
xsltproc generate-id.xsl pages.xml

returns:


and content



another
of xml



Expected result: all IDs should be unique.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: libxslt1.1 1.1.29-2ubuntu0.1
ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.4
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Tue Jul 18 10:55:05 2017
InstallationDate: Installed on 2017-05-31 (47 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: libxslt
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug zesty

** Attachment added: "generate-id.7z"
   
https://bugs.launchpad.net/bugs/1704937/+attachment/4916588/+files/generate-id.7z

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

Title:
  generate-id() returns non-unique values

Status in libxslt package in Ubuntu:
  New

Bug description:
  It seems related to patch https://bugs.debian.org/823857.
  See attachment,
  The command
  xsltproc generate-id.xsl pages.xml

  returns:
  

and content

  

another
of xml

  

  Expected result: all IDs should be unique.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libxslt1.1 1.1.29-2ubuntu0.1
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Tue Jul 18 10:55:05 2017
  InstallationDate: Installed on 2017-05-31 (47 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: libxslt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxslt/+bug/1704937/+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 346958] Re: Text in columns is left-aligned while language is RTL (Hebrew)

2017-07-18 Thread Bug Watch Updater

** Changed in: evolution
   Status: New => Confirmed

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

Title:
  Text in columns is left-aligned while language is RTL (Hebrew)

Status in Evolution:
  Confirmed
Status in evolution package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: evolution

  I expect the text in the columns to be right-aligned when I'm using
  Hebrew.

  Screenshot attached.

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 8.10
  ExecutablePath: /usr/bin/evolution
  NonfreeKernelModules: ath_hal
  Package: evolution 2.24.3-0ubuntu1
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=he_IL.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution
  Uname: Linux 2.6.27-11-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/346958/+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 1704807] Re: Audio doesn't switch automatically to Bluetooth speaker when hotplugged after application playback started

** Also affects: gst-plugins-good1.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Audio doesn't switch automatically to Bluetooth speaker when
  hotplugged after application playback started

Status in gst-plugins-good1.0 package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Confirmed

Bug description:
  artful desktop

  Test Case.
  1. Pair a BT Speaker and set the output channel to the speaker
  2. Play something with vlc or totem (and make sure it uses the speaker with 
pavucontrol for instance)
  3. Switch the output to another channel eg internal speaker and turn the BT 
speaker off (do not close the music player)
  4. Turn the speaker back on and wait until it connects
  5. If the speaker is not selected automatically as the output, select it in 
the sound settings
  6. Resume playing in VLC

  Expected result
  The track plays on the speaker

  Actual result
  It plays on the internal audio.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jul 17 17:09:17 2017
  InstallationDate: Installed on 2013-09-03 (1412 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  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/gst-plugins-good1.0/+bug/1704807/+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 1704807] Re: Audio doesn't switch automatically to Bluetooth speaker when hotplugged after application playback started

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

** Changed in: gst-plugins-good1.0 (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/1704807

Title:
  Audio doesn't switch automatically to Bluetooth speaker when
  hotplugged after application playback started

Status in gst-plugins-good1.0 package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Confirmed

Bug description:
  artful desktop

  Test Case.
  1. Pair a BT Speaker and set the output channel to the speaker
  2. Play something with vlc or totem (and make sure it uses the speaker with 
pavucontrol for instance)
  3. Switch the output to another channel eg internal speaker and turn the BT 
speaker off (do not close the music player)
  4. Turn the speaker back on and wait until it connects
  5. If the speaker is not selected automatically as the output, select it in 
the sound settings
  6. Resume playing in VLC

  Expected result
  The track plays on the speaker

  Actual result
  It plays on the internal audio.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jul 17 17:09:17 2017
  InstallationDate: Installed on 2013-09-03 (1412 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  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/gst-plugins-good1.0/+bug/1704807/+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 1704807] Re: Audio doesn't switch automatically to Bluetooth speaker when hotplugged after application playback started