date:20170522

Using the purge technique I can also reproduce in Xenial. I suspect this
problem isn't being seen much pre-Zesty because gconf is already
installed (pulled in by aisleriot and probably other older pacakges).

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

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

Status in gconf package in Ubuntu:
  New
Status in gnome-software package in Ubuntu:
  New
Status in gconf source package in Xenial:
  New
Status in gnome-software source package in Xenial:
  New
Status in gconf source package in Yakkety:
  New
Status in gnome-software source package in Yakkety:
  New
Status in gconf source package in Zesty:
  New
Status in gnome-software source package in Zesty:
  New
Status in gconf source package in Artful:
  New
Status in gnome-software source package in Artful:
  New

Bug description:
  = Test Case =
  1. Download the debian package of Chrome from google
  2. Open nautilus and double-click on the file to launch ubuntu software
  3. Install the package and proceed with the installation

  = Expected result = 
  Chrome installs correctly

  = Actual result =
  The installation hangs on the following command in gconf2-common.postinst

  ucf /usr/share/gconf/default.path /etc/gconf/2/path


  = Original Report =
  I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
  This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
  The same file was successfully installed with gdebi.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  6 13:56:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

By purging gconf2-common, I can reproduce in Artful.

i.e.
$ sudo apt purge gconf2-common
$ gnome-software --local-filename 
~/Downloads/google-chrome-stable_current_amd64.deb 


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

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

** Also affects: gconf (Ubuntu Artful)
   Importance: High
   Status: New

** Also affects: gnome-software (Ubuntu Artful)
   Importance: High
 Assignee: Robert Ancell (robert-ancell)
   Status: New

** Also affects: gconf (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

** Also affects: gconf (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

** Changed in: gnome-software (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: gnome-software (Ubuntu Yakkety)
   Importance: Undecided => High

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

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

Status in gconf package in Ubuntu:
  New
Status in gnome-software package in Ubuntu:
  New
Status in gconf source package in Xenial:
  New
Status in gnome-software source package in Xenial:
  New
Status in gconf source package in Yakkety:
  New
Status in gnome-software source package in Yakkety:
  New
Status in gconf source package in Zesty:
  New
Status in gnome-software source package in Zesty:
  New
Status in gconf source package in Artful:
  New
Status in gnome-software source package in Artful:
  New

Bug description:
  = Test Case =
  1. Download the debian package of Chrome from google
  2. Open nautilus and double-click on the file to launch ubuntu software
  3. Install the package and proceed with the installation

  = Expected result = 
  Chrome installs correctly

  = Actual result =
  The installation hangs on the following command in gconf2-common.postinst

  ucf /usr/share/gconf/default.path /etc/gconf/2/path


  = Original Report =
  I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
  This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
  The same file was successfully installed with gdebi.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  6 13:56:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1652148] Re: I am not able to print on my new canon laser shot LBP2900B printer

[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/1652148

Title:
  I am not able to print on my new canon laser shot LBP2900B printer

Status in cups package in Ubuntu:
  Expired

Bug description:
  i am able to find the printer on the system but it is not able to print...
  in the status of printer it shows "idle:sending file to printer"
  or "sending file to printer" or "Idle - Sending data to printer. "but the 
printer doesnt prints

  output of lpusb commmand
  Bus 001 Device 002: ID 8087:8001 Intel Corp. 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 002 Device 004: ID 8087:0a2a Intel Corp. 
  Bus 002 Device 003: ID 04f2:b413 Chicony Electronics Co., Ltd 
  Bus 002 Device 012: ID 04a9:2676 Canon, Inc. CAPT Device
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  
  lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  printer :canon laser shot LBP2900B printer
   driver downloaded from : 
http://gdlp01.c-wss.com/gds/6/014596/04/Linux_CAPT_PrinterDriver_V270_uk_EN.tar.gz
   Tried x64 bit drivers

  expected: printer to print

  happened : no response from printer

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Dec 23 00:26:32 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-12-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lpstat: device for CanonLBP2900B: usb://Canon/LBP2900?serial=C1G97FQN
  MachineType: FUJITSU LIFEBOOK A555
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/CanonLBP2900B.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/CanonLBP2900B.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=94e9467b-205b-43c4-b1ca-7f285806bdba ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2016
  dmi.bios.vendor: FUJITSU // Insyde Software Corp.
  dmi.bios.version: 1.21
  dmi.board.name: FJNBB3E
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvr1.21:bd05/31/2016:svnFUJITSU:pnLIFEBOOKA555:pvr:rvnFUJITSU:rnFJNBB3E:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A555
  dmi.sys.vendor: FUJITSU

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

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

[Desktop-packages] [Bug 1660316] Re: apparmor denial of CUPS

[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/1660316

Title:
  apparmor denial of CUPS

Status in cups package in Ubuntu:
  Expired

Bug description:
  Printing is enabled when doing sudo aa-complain cupsd

  Here is an extract of /var/log/syslog:

  Jan 30 12:41:59 dag-TS-P500 kernel: [  868.929457] audit: type=1400 
audit(1485776519.269:37): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6932 
comm="apparmor_parser"
  Jan 30 12:41:59 dag-TS-P500 kernel: [  868.929744] audit: type=1400 
audit(1485776519.269:38): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=6932 comm="apparmor_parser"
  Jan 30 12:41:59 dag-TS-P500 kernel: [  868.945422] audit: type=1400 
audit(1485776519.285:39): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6932 
comm="apparmor_parser"
  Jan 30 12:42:10 dag-TS-P500 kernel: [  879.817070] audit: type=1400 
audit(1485776530.158:40): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6941 
comm="apparmor_parser"
  Jan 30 12:42:10 dag-TS-P500 kernel: [  879.817342] audit: type=1400 
audit(1485776530.158:41): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=6941 comm="apparmor_parser"
  Jan 30 12:42:10 dag-TS-P500 kernel: [  879.837254] audit: type=1400 
audit(1485776530.178:42): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6941 
comm="apparmor_parser"
  Jan 30 12:42:16 dag-TS-P500 zeitgeist-datah[3706]: 
downloads-directory-provider.vala:120: Couldn't process /home/dag/.glvndcEQzqA: 
Error when getting information for file '/home/dag/.glvndcEQzqA': No such file 
or directory
  Jan 30 12:42:23 dag-TS-P500 dbus[996]: [system] Activating via systemd: 
service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service'
  Jan 30 12:42:23 dag-TS-P500 systemd[1]: Starting Hostname Service...
  Jan 30 12:42:24 dag-TS-P500 dbus[996]: [system] Successfully activated 
service 'org.freedesktop.hostname1'
  Jan 30 12:42:24 dag-TS-P500 systemd[1]: Started Hostname Service.
  Jan 30 12:42:26 dag-TS-P500 kernel: [  895.746636] audit: type=1400 
audit(1485776546.086:43): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/cupsd" pid=6967 comm="lpd" capability=12  capname="net_admin"
  Jan 30 12:42:54 dag-TS-P500 systemd[1]: Starting Cleanup of Temporary 
Directories...
  Jan 30 12:42:54 dag-TS-P500 systemd-tmpfiles[6973]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
  Jan 30 12:42:54 dag-TS-P500 systemd[1]: Started Cleanup of Temporary 
Directories.
  Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Activating service 
name='com.ubuntu.OneConf'
  Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 
'com.ubuntu.OneConf'
  Jan 30 12:44:03 dag-TS-P500 com.ubuntu.OneConf[2707]: 
WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file 
or directory: 
'/home/dag/.cache/oneconf/d2fc3bf30c9f4976b441a8f14de53bda/other_hosts'
  Jan 30 12:44:23 dag-TS-P500 dbus-daemon[2707]: Activating service 
name='com.ubuntu.sso'
  Jan 30 12:44:24 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 
'com.ubuntu.sso'
  Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.685842] audit: type=1400 
audit(1485776751.028:44): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=7024 
comm="apparmor_parser"
  Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.686099] audit: type=1400 
audit(1485776751.028:45): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=7024 comm="apparmor_parser"
  Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.700446] audit: type=1400 
audit(1485776751.044:46): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=7024 
comm="apparmor_parser"
  Jan 30 12:45:57 dag-TS-P500 kernel: [ 1106.940891] audit: type=1400 
audit(1485776757.284:47): apparmor="ALLOWED" operation="capable" 
profile="/usr/sbin/cupsd" pid=7031 comm="lpd" capability=12  capname="net_admin"
  Jan 30 12:45:57 dag-TS-P500 kernel: [ 1106.940938] audit: type=1400 
audit(1485776757.284:48): apparmor="ALLOWED" operation="capable" 
profile="/usr/sbin/cupsd" pid=7031 comm="lpd" capability=12  capname="net_admin"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: cups 2.2.0-2
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  NonfreeKernelModules: nvidia_uvm

[Desktop-packages] [Bug 1663647] Re: cannot add printer

[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/1663647

Title:
  cannot add printer

Status in cups package in Ubuntu:
  Expired

Bug description:
  Terminal log follows

  neil@neil-Latitude-D630:~$ lsmod | grep usb
  usbhid 49152  0
  hid   118784  2 hid_generic,usbhid
  neil@neil-Latitude-D630:~$ tail -f /var/log/syslog
  Feb 10 15:02:17 neil-Latitude-D630 avahi-daemon[960]: Registering new address 
record for fe80::221:5cff:fe6f:bbe5 on wlp12s0.*.
  Feb 10 15:03:08 neil-Latitude-D630 wpa_supplicant[1147]: wlp12s0: WPA: Group 
rekeying completed with 58:98:35:15:e9:b9 [GTK=TKIP]
  Feb 10 15:03:16 neil-Latitude-D630 systemd-timesyncd[463]: Synchronized to 
time server 91.189.94.4:123 (ntp.ubuntu.com).
  Feb 10 15:03:16 neil-Latitude-D630 systemd[1581]: Time has been changed
  Feb 10 15:03:16 neil-Latitude-D630 systemd[1]: Time has been changed
  Feb 10 15:03:16 neil-Latitude-D630 systemd[1]: snapd.refresh.timer: Adding 5h 
11min 5.412159s random time.
  Feb 10 15:03:16 neil-Latitude-D630 systemd[1]: apt-daily.timer: Adding 50min 
41.219140s random time.
  Feb 10 15:13:09 neil-Latitude-D630 wpa_supplicant[1147]: wlp12s0: WPA: Group 
rekeying completed with 58:98:35:15:e9:b9 [GTK=TKIP]
  Feb 10 15:17:01 neil-Latitude-D630 CRON[15040]: (root) CMD (   cd / && 
run-parts --report /etc/cron.hourly)
  Feb 10 15:23:09 neil-Latitude-D630 wpa_supplicant[1147]: wlp12s0: WPA: Group 
rekeying completed with 58:98:35:15:e9:b9 [GTK=TKIP]
  Feb 10 15:41:10 neil-Latitude-D630 kernel: [17268.068213] usb 2-4: new 
high-speed USB device number 4 using ehci-pci
  Feb 10 15:41:10 neil-Latitude-D630 kernel: [17268.202919] usb 2-4: New USB 
device found, idVendor=04a9, idProduct=10d3
  Feb 10 15:41:10 neil-Latitude-D630 kernel: [17268.202928] usb 2-4: New USB 
device strings: Mfr=1, Product=2, SerialNumber=3
  Feb 10 15:41:10 neil-Latitude-D630 kernel: [17268.202934] usb 2-4: Product: 
iP2700 series
  Feb 10 15:41:10 neil-Latitude-D630 kernel: [17268.202938] usb 2-4: 
Manufacturer: Canon
  Feb 10 15:41:10 neil-Latitude-D630 kernel: [17268.202943] usb 2-4: 
SerialNumber: 234517
  Feb 10 15:33:09 neil-Latitude-D630 wpa_supplicant[1147]: wlp12s0: WPA: Group 
rekeying completed with 58:98:35:15:e9:b9 [GTK=TKIP]
  Feb 10 15:41:10 neil-Latitude-D630 mtp-probe: checking bus 2, device 4: 
"/sys/devices/pci:00/:00:1d.7/usb2/2-4"
  Feb 10 15:41:10 neil-Latitude-D630 mtp-probe: bus: 2, device: 4 was not an 
MTP device
  Feb 10 15:41:11 neil-Latitude-D630 systemd[1]: Created slice 
system-udev\x2dconfigure\x2dprinter.slice.
  Feb 10 15:41:11 neil-Latitude-D630 systemd[1]: Starting Automatic 
USB/Bluetooth printer setup (-devices-pci:00-:00:1d.7-usb2-2\x2d4)...
  Feb 10 15:41:11 neil-Latitude-D630 systemd[1]: Started CUPS Scheduler.
  Feb 10 15:41:11 neil-Latitude-D630 systemd[1]: Reached target Printer.
  Feb 10 15:41:11 neil-Latitude-D630 kernel: [17269.076606] usblp 2-4:1.0: 
usblp0: USB Bidirectional printer dev 4 if 0 alt 0 proto 2 vid 0x04A9 pid 0x10D3
  Feb 10 15:41:11 neil-Latitude-D630 kernel: [17269.076648] usbcore: registered 
new interface driver usblp
  Feb 10 15:41:11 neil-Latitude-D630 udev-configure-printer[15223]: add 
/devices/pci:00/:00:1d.7/usb2/2-4
  Feb 10 15:41:11 neil-Latitude-D630 udev-configure-printer[15223]: device 
devpath is /devices/pci:00/:00:1d.7/usb2/2-4
  Feb 10 15:41:11 neil-Latitude-D630 udev-configure-printer[15223]: MFG:Canon 
MDL:iP2700 series SERN:- serial:234517
  Feb 10 15:41:12 neil-Latitude-D630 kernel: [17269.577898] audit: type=1400 
audit(1486741272.103:36): apparmor="DENIED" operation="sendmsg" 
profile="/usr/sbin/cupsd" name="/run/systemd/journal/socket" pid=15225 
comm="cupsd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0
  Feb 10 15:41:12 neil-Latitude-D630 systemd[1]: cups.service: Main process 
exited, code=exited, status=1/FAILURE
  Feb 10 15:41:12 neil-Latitude-D630 systemd[1]: cups.service: Unit entered 
failed state.
  Feb 10 15:41:12 neil-Latitude-D630 systemd[1]: cups.service: Failed with 
result 'exit-code'.
  Feb 10 15:41:17 neil-Latitude-D630 udev-configure-printer[15223]: failed to 
connect to CUPS server; giving up
  Feb 10 15:41:17 neil-Latitude-D630 systemd[1]: 
udev-configure-printer@-devices-pci:00-:00:1d.7-usb2-2\x2d4.service: 
Control process exited, code=exited status=1
  Feb 10 15:41:17 neil-Latitude-D630 systemd[1]: Failed to start Automatic 
USB/Bluetooth printer setup (-devices-pci:00-:00:1d.7-usb2-2\x2d4).
  Feb 10 15:41:17 neil-Latitude-D630 systemd[1]: 
udev-configure-printer@-devices-pci:00-:00:1d.7-usb2-2\x2d4.service: 
Unit entered failed state.
  Feb 10 15:41:17 neil-Latitude-D630 systemd[1]:

[Desktop-packages] [Bug 1692782] [NEW] package libharfbuzz0b:amd64 1.0.1-1build2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting conf

2017-05-22 Thread Shardul Bankar

Public bug reported:

The error came while performing the following operation:
sudo apt-get install git-core gnupg flex bison gperf build-essential   zip curl 
zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386   lib32ncurses5-dev 
x11proto-core-dev libx11-dev lib32z-dev ccache   libgl1-mesa-dev libxml2-utils 
xsltproc unzip

This was the message on the console:

The following package was automatically installed and is no longer required:
  libpango1.0-0
Use 'sudo apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 307 not upgraded.
14 not fully installed or removed.
Need to get 140 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://in.archive.ubuntu.com/ubuntu xenial/main amd64 libharfbuzz0b amd64 
1.0.1-1build2 [140 kB]
Fetched 140 kB in 1s (111 kB/s)   
dpkg: error processing package libharfbuzz0b:amd64 (--configure):
 package is in a very bad inconsistent state; you should
 reinstall it before attempting configuration
No apport report written because the error message indicates its a followup 
error from a previous failure.
  E: Sub-process /usr/bin/dpkg returned an error code 
(1)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libharfbuzz0b:amd64 1.0.1-1build2
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: Tue May 23 09:42:55 2017
DpkgTerminalLog:
 dpkg: error processing package libharfbuzz0b:amd64 (--configure):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-05-19 (3 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15ubuntu0.2
SourcePackage: harfbuzz
Title: package libharfbuzz0b:amd64 1.0.1-1build2 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: harfbuzz (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 harfbuzz in Ubuntu.
https://bugs.launchpad.net/bugs/1692782

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

Status in harfbuzz package in Ubuntu:
  New

Bug description:
  The error came while performing the following operation:
  sudo apt-get install git-core gnupg flex bison gperf build-essential   zip 
curl zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386   lib32ncurses5-dev 
x11proto-core-dev libx11-dev lib32z-dev ccache   libgl1-mesa-dev libxml2-utils 
xsltproc unzip

  This was the message on the console:

  The following package was automatically installed and is no longer required:
libpango1.0-0
  Use 'sudo apt autoremove' to remove it.
  0 upgraded, 0 newly installed, 0 to remove and 307 not upgraded.
  14 not fully installed or removed.
  Need to get 140 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 http://in.archive.ubuntu.com/ubuntu xenial/main amd64 libharfbuzz0b 
amd64 1.0.1-1build2 [140 kB]
  Fetched 140 kB in 1s (111 kB/s)   
  dpkg: error processing package libharfbuzz0b:amd64 (--configure):
   package is in a very bad inconsistent state; you should
   reinstall it before attempting configuration
  No apport report written because the error message indicates its a followup 
error from a previous failure.
E: Sub-process /usr/bin/dpkg returned an error code 
(1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libharfbuzz0b:amd64 1.0.1-1build2
  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: Tue May 23 09:42:55 2017
  DpkgTerminalLog:
   dpkg: error processing package libharfbuzz0b:amd64 (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-19 (3 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: harfbuzz
  Title: package libharfbuzz0b:amd64 1.0.1-1build2 failed to install/upgrade: 
package is in a

[Desktop-packages] [Bug 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

All current duplicates are for Zesty, except for bug 1691599 (Artful)
and bug 1692344 (Yakkety).

** Also affects: gconf (Ubuntu Zesty)
   Importance: Undecided
   Status: New

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

** Changed in: gnome-software (Ubuntu Zesty)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

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

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

** Changed in: gnome-software (Ubuntu Zesty)
   Importance: Undecided => High

** Changed in: gnome-software (Ubuntu)
   Importance: Undecided => High

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

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

Status in gconf package in Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gconf source package in Zesty:
  New
Status in gnome-software source package in Zesty:
  New

Bug description:
  = Test Case =
  1. Download the debian package of Chrome from google
  2. Open nautilus and double-click on the file to launch ubuntu software
  3. Install the package and proceed with the installation

  = Expected result = 
  Chrome installs correctly

  = Actual result =
  The installation hangs on the following command in gconf2-common.postinst

  ucf /usr/share/gconf/default.path /etc/gconf/2/path


  = Original Report =
  I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
  This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
  The same file was successfully installed with gdebi.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  6 13:56:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

I could reproduce in Zesty, but not Artful or Xenial.

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

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

Status in gconf package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  = Test Case =
  1. Download the debian package of Chrome from google
  2. Open nautilus and double-click on the file to launch ubuntu software
  3. Install the package and proceed with the installation

  = Expected result = 
  Chrome installs correctly

  = Actual result =
  The installation hangs on the following command in gconf2-common.postinst

  ucf /usr/share/gconf/default.path /etc/gconf/2/path


  = Original Report =
  I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
  This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
  The same file was successfully installed with gdebi.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  6 13:56:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1692770] [NEW] Chromium-Browser Aw, snap error again with Raspberry Pi 3 on Ubuntu Mate 16.04.2

2017-05-22 Thread rusli

Public bug reported:

Hi

Still having the same issues with the new version of Chromium Browser...
it is still giving the same Aw Snap error with Raspberry Pi 3 on Ubuntu
mate 16.04.1.

Could you please fix this problem.

It still not working regardless of the new version upgrade.

sudo chromium-browser
[0523/104547.853872:ERROR:nss_util.cc(94)] Failed to create 
/home/kerbau/.pki/nssdb directory.
Created new window in existing browser session.
chromium-browser --type=renderer --enable-pinch --field-trial-handle=1 
--primordial-pipe-token=5284E67709FC2E0A2E6F3BF46C2841FF --lang=en-US 
--instant-process --enable-offline-auto-reload 
--enable-offline-auto-reload-visible-only 
--ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so 
--ppapi-flash-version=24.0.0.221 --enable-pinch --num-raster-threads=2 
--enable-main-frame-before-activation 
--content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;0,15,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;1,15,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;2,15,3553;3,0,3553;3,1,3553;3,2,3553;3,3,3553;3,4,3553;3,5,3553;3,6,3553;3,7,3553;3,8,3553;3,9,3553;3,10,3553;3,11,3553;3,12,35
 
53;3,13,3553;3,14,3553;3,15,3553;4,0,3553;4,1,3553;4,2,3553;4,3,3553;4,4,3553;4,5,3553;4,6,3553;4,7,3553;4,8,3553;4,9,3553;4,10,3553;4,11,3553;4,12,3553;4,13,3553;4,14,3553;4,15,3553
 --disable-accelerated-video-decode --disable-webrtc-hw-vp8-encoding 
--disable-gpu-compositing 
--service-request-channel-token=5284E67709FC2E0A2E6F3BF46C2841FF 
--renderer-client-id=6 --shared-files=v8_natives_data:100,v8_snapshot_data:101: 
pthread_getattr_np.c:71: pthread_getattr_np: Assertion `abs (thread->pid) == 
thread->tid' failed.
Received signal 4  7228f3f6
#0 0x76e9616a base::debug::StackTrace::StackTrace()
#1 0x76e95c1e base::debug::StackTrace::StackTrace()
#2 0x76e964a4 
#3 0x7228f270 
#4 0x7228f3f6 abort
[end of stack trace]
Calling _exit(1). Core file will not be generated.


Calling _exit(1). Core file will not be generated.
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
No value set for `/desktop/gnome/session/required_components/windowmanager'
No value set for `/apps/metacity/general/compositing_manager'
kerbau@kerbau-desktop:~$ Created new window in existing browser session.
chromium-browser --type=renderer --enable-pinch --field-trial-handle=1 
--primordial-pipe-token=6F0BCD786EC9D52C50C043366B038E27 --lang=en-US 
--enable-offline-auto-reload --enable-offline-auto-reload-visible-only 
--ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so 
--ppapi-flash-version=24.0.0.221 --enable-pinch --num-raster-threads=2 
--enable-main-frame-before-activation 
--content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;0,15,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;1,15,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;2,15,3553;3,0,3553;3,1,3553;3,2,3553;3,3,3553;3,4,3553;3,5,3553;3,6,3553;3,7,3553;3,8,3553;3,9,3553;3,10,3553;3,11,3553;3,12,3553;3,13,3553;3,14,
 
3553;3,15,3553;4,0,3553;4,1,3553;4,2,3553;4,3,3553;4,4,3553;4,5,3553;4,6,3553;4,7,3553;4,8,3553;4,9,3553;4,10,3553;4,11,3553;4,12,3553;4,13,3553;4,14,3553;4,15,3553
 --disable-accelerated-video-decode --disable-webrtc-hw-vp8-encoding 
--disable-gpu-compositing 
--service-request-channel-token=6F0BCD786EC9D52C50C043366B038E27 
--renderer-client-id=4 --shared-files=v8_natives_data:100,v8_snapshot_data:101: 
pthread_getattr_np.c:71: pthread_getattr_np: Assertion `abs (thread->pid) == 
thread->tid' failed.
Received signal 4  7228f3f6
#0 0x76e9616a base::debug::StackTrace::StackTrace()
#1 0x76e95c1e base::debug::StackTrace::StackTrace()
#2 0x76e964a4 
#3 0x7228f270 
#4 0x7228f3f6 abort
[end of stack trace]
Calling _exit(1). Core file will not be generated.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: chromium-browser 58.0.3029.110-0ubuntu0.16.04.1281
Uname: Linux 4.9.29-v7+ armv7l
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: armhf
Date: Tue May 23 10:34:49 2017
Desktop-Session:
 'None'
 'None'
 'None'
DetectedPlugins:
 
Env:
 'None'
 'None'
InstalledPlugins:
 
Load-Avg-1min: 1.64
Load-Processes-Running-Percent:   0.3%
Lspci:
 Error: command ['lspci', '-mmkv'] failed with exit code 1: pcilib: Cannot open 
/proc/bus/pci
 lspci: Cannot find any working access method.
Lsusb:
 Bus 001 Device 005: ID 046d:c05a Logitech, Inc. M90/M100

[Desktop-packages] [Bug 1692768] [NEW] Chromium-Browser not working with Raspberry Pi 3 on Ubuntu Mate 16.04.1

2017-05-22 Thread rusli

Public bug reported:

Hi

Still having the same issues with the new version of Chromium Browser...
it is still giving the same Aw Snap error with Raspberry Pi 3 on Ubuntu
mate 16.04.1.

Could you please fix this problem.

It still not working regardless of the new version upgrade.

sudo chromium-browser
[0523/104547.853872:ERROR:nss_util.cc(94)] Failed to create 
/home/kerbau/.pki/nssdb directory.
Created new window in existing browser session.
chromium-browser --type=renderer --enable-pinch --field-trial-handle=1 
--primordial-pipe-token=5284E67709FC2E0A2E6F3BF46C2841FF --lang=en-US 
--instant-process --enable-offline-auto-reload 
--enable-offline-auto-reload-visible-only 
--ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so 
--ppapi-flash-version=24.0.0.221 --enable-pinch --num-raster-threads=2 
--enable-main-frame-before-activation 
--content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;0,15,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;1,15,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;2,15,3553;3,0,3553;3,1,3553;3,2,3553;3,3,3553;3,4,3553;3,5,3553;3,6,3553;3,7,3553;3,8,3553;3,9,3553;3,10,3553;3,11,3553;3,12,35
 
53;3,13,3553;3,14,3553;3,15,3553;4,0,3553;4,1,3553;4,2,3553;4,3,3553;4,4,3553;4,5,3553;4,6,3553;4,7,3553;4,8,3553;4,9,3553;4,10,3553;4,11,3553;4,12,3553;4,13,3553;4,14,3553;4,15,3553
 --disable-accelerated-video-decode --disable-webrtc-hw-vp8-encoding 
--disable-gpu-compositing 
--service-request-channel-token=5284E67709FC2E0A2E6F3BF46C2841FF 
--renderer-client-id=6 --shared-files=v8_natives_data:100,v8_snapshot_data:101: 
pthread_getattr_np.c:71: pthread_getattr_np: Assertion `abs (thread->pid) == 
thread->tid' failed.
Received signal 4  7228f3f6
#0 0x76e9616a base::debug::StackTrace::StackTrace()
#1 0x76e95c1e base::debug::StackTrace::StackTrace()
#2 0x76e964a4 
#3 0x7228f270 
#4 0x7228f3f6 abort
[end of stack trace]
Calling _exit(1). Core file will not be generated.


Calling _exit(1). Core file will not be generated.
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
No value set for `/desktop/gnome/session/required_components/windowmanager'
No value set for `/apps/metacity/general/compositing_manager'
kerbau@kerbau-desktop:~$ Created new window in existing browser session.
chromium-browser --type=renderer --enable-pinch --field-trial-handle=1 
--primordial-pipe-token=6F0BCD786EC9D52C50C043366B038E27 --lang=en-US 
--enable-offline-auto-reload --enable-offline-auto-reload-visible-only 
--ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so 
--ppapi-flash-version=24.0.0.221 --enable-pinch --num-raster-threads=2 
--enable-main-frame-before-activation 
--content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;0,15,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;1,15,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;2,15,3553;3,0,3553;3,1,3553;3,2,3553;3,3,3553;3,4,3553;3,5,3553;3,6,3553;3,7,3553;3,8,3553;3,9,3553;3,10,3553;3,11,3553;3,12,3553;3,13,3553;3,14,
 
3553;3,15,3553;4,0,3553;4,1,3553;4,2,3553;4,3,3553;4,4,3553;4,5,3553;4,6,3553;4,7,3553;4,8,3553;4,9,3553;4,10,3553;4,11,3553;4,12,3553;4,13,3553;4,14,3553;4,15,3553
 --disable-accelerated-video-decode --disable-webrtc-hw-vp8-encoding 
--disable-gpu-compositing 
--service-request-channel-token=6F0BCD786EC9D52C50C043366B038E27 
--renderer-client-id=4 --shared-files=v8_natives_data:100,v8_snapshot_data:101: 
pthread_getattr_np.c:71: pthread_getattr_np: Assertion `abs (thread->pid) == 
thread->tid' failed.
Received signal 4  7228f3f6
#0 0x76e9616a base::debug::StackTrace::StackTrace()
#1 0x76e95c1e base::debug::StackTrace::StackTrace()
#2 0x76e964a4 
#3 0x7228f270 
#4 0x7228f3f6 abort
[end of stack trace]
Calling _exit(1). Core file will not be generated.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: chromium-browser 58.0.3029.110-0ubuntu0.16.04.1281
Uname: Linux 4.9.29-v7+ armv7l
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: armhf
Date: Tue May 23 10:34:49 2017
Desktop-Session:
 'None'
 'None'
 'None'
DetectedPlugins:
 
Env:
 'None'
 'None'
InstalledPlugins:
 
Load-Avg-1min: 1.64
Load-Processes-Running-Percent:   0.3%
Lspci:
 Error: command ['lspci', '-mmkv'] failed with exit code 1: pcilib: Cannot open 
/proc/bus/pci
 lspci: Cannot find any working access method.
Lsusb:
 Bus 001 Device 005: ID 046d:c05a Logitech, Inc. M90/M100

[Desktop-packages] [Bug 997331] Re: Some ALSA applications play bad sound

** Summary changed:

- Some alsa applications play bad sound
+ Some ALSA applications play bad sound

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

Title:
  Some ALSA applications play bad sound

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Some applications using ALSA plays bad sound. One is WINE
  applications. Winecfg test sound is distorted (sounds awful). Spotify
  running WINE plays songs way too fast. A flash based program play
  distorted sound. The common thing for all of them is that under
  Applications in Sound settings it says alsa-plugin and it flashes very
  rapidly between "No application is currently playing" and alsa-plugin.
  It almost looks like flickering. I've testet a normal wave file using
  aplay and that was okey, no problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  oeriksen   3299 F pulseaudio
   /dev/snd/controlC0:  oeriksen   3299 F pulseaudio
   /dev/snd/controlC1:  oeriksen   3299 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xfa40 irq 60'
 Mixer name : 'Realtek ALC892'
 Components : 'HDA:10ec0892,10438410,00100302'
 Controls  : 41
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'Socialize'/'Creative Labs VF0640 Live! Cam Socialize at 
usb-:00:1d.0-1.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB041e:4083'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 48
 Mono: Capture 45 [94%] [18.00dB] [on]
  Card2.Amixer.info:
   Card hw:2 'NVidia'/'HDA NVidia at 0xfa08 irq 17'
 Mixer name : 'Nvidia GPU 16 HDMI/DP'
 Components : 'HDA:10de0016,10de0101,00100100'
 Controls  : 24
 Simple ctrls  : 4
  Date: Wed May  9 22:41:04 2012
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [System Product Name, Realtek ALC892, Green Line Out, Rear] Playback 
problem
  UpgradeStatus: Upgraded to precise on 2012-03-02 (68 days ago)
  dmi.bios.date: 02/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8P67 REV 3.1
  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.:bvr2302:bd02/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8P67REV3.1: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/pulseaudio/+bug/997331/+subscriptions

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

[Desktop-packages] [Bug 1585084] Re: Volume notification keeps popping up constantly(the notifyosd bubble on top-right corner)

** Changed in: pulseaudio (Ubuntu)
 Assignee: Luke Yelavich (themuso) => (unassigned)

** Summary changed:

- Volume notification keeps popping up constantly(the notifyosd bubble on 
top-right corner)
+ Volume notification keeps popping up constantly (the notify-OSD bubble on 
top-right corner)

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

Title:
  Volume notification keeps popping up constantly (the notify-OSD bubble
  on top-right corner)

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I upgraded to Ubuntu 16.04 yesterday, I did a clean install while
  preserving the home directory which is mounted in a separate
  partition. Even during the installation I had constant volume
  notification bubble appearing on the top-right corner of my screen, it
  would come and go about twice every minute. I just thought it was due
  to installing hardware drivers or something but the problem persisted
  even when I booted into the freshly installed system. I did some
  searching and two users reported the exact problem. And one more
  suggested this happens because constant disconnect and reconnect of
  the sound card which makes sense as the sound settings flashes briefly
  during every popup. Someone on IRC suggested to kill pulseaudio and
  thus restart it, that does not fix the issue. I also tried the Live
  environment thinking it might be due to some old config files in home
  partition (which was preserved during upgrade), but this problem
  happens in the live environment as well, which makes sense because it
  was present during installation as well.

  Users with the same issue:
  http://ubuntuforums.org/showthread.php?t=2323815
  http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04
  
http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  sidd   1651 F pulseaudio
   /dev/snd/controlC0:  sidd   1651 F pulseaudio
   /dev/snd/controlC1:  sidd   1651 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 24 12:31:12 2016
  InstallationDate: Installed on 2016-05-23 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0705
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

[Desktop-packages] [Bug 1692454] Re: [ENS1371 - Ensoniq AudioPCI, playback] No sound at all

** Tags added: nosound vm

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

Title:
  [ENS1371 - Ensoniq AudioPCI, playback] No sound at all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  no audio at all

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hariharan   1985 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon May 22 14:08:44 2017
  InstallationDate: Installed on 2017-05-17 (4 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:AudioPCI 
successful
  Symptom_Card: ES1371/ES1373 / Creative Labs CT2518 (Audio PCI 64V/128/5200 / 
Creative CT4810/CT5803/CT5806 [Sound Blaster PCI]) - Ensoniq AudioPCI
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hariharan   1985 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [ENS1371 - Ensoniq AudioPCI, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Desktop-packages] [Bug 1692710] Re: [System Product Name, Realtek ALC1200, Green Line Out, Rear] Pulseaudio, Jack and ALSA seem to work, but there's no sound output

** Tags added: nosound

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

Title:
  [System Product Name, Realtek ALC1200, Green Line Out, Rear]
  Pulseaudio, Jack and ALSA seem to work, but there's no sound output

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I've got Ubuntu 17.04 installed with KXStudio on top of that.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-21.23-lowlatency 4.10.11
  Uname: Linux 4.10.0-21-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon May 22 22:29:46 2017
  InstallationDate: Installed on 2017-05-21 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA ATI SB
  Symptom_Jack: Green Line Out, Rear
  Title: [System Product Name, Realtek ALC1200, Green Line Out, Rear] 
Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/05/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0801
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M3A78 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.:bvr0801:bd01/05/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A78PRO: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/pulseaudio/+bug/1692710/+subscriptions

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

[Desktop-packages] [Bug 1692748] [NEW] el equipo no puede actulizarce

2017-05-22 Thread jose cordova

Public bug reported:

El equipo no puede actualizar ya que hubo un error , el sistema me dice
que active el gestor de paquetes pero tampoco puedo activarlo ya que el
sistema no me lo permite por favor necesito ayuda, saludos.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon May 22 21:07:51 2017
DistUpgraded: 2017-04-24 08:27:07,949 DEBUG icon theme changed, re-reading
DistroCodename: zesty
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [1025:0936]
InstallationDate: Installed on 2017-04-03 (50 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
MachineType: Acer Aspire ES1-512
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic 
root=UUID=e483ca57-0769-4213-9cb0-a725150eac9b ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to zesty on 2017-04-24 (28 days ago)
dmi.bios.date: 08/11/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.06
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Aspire ES1-512
dmi.board.vendor: Acer
dmi.board.version: V1.06
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.06
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd08/11/2014:svnAcer:pnAspireES1-512:pvrV1.06:rvnAcer:rnAspireES1-512:rvrV1.06:cvnAcer:ct10:cvrV1.06:
dmi.product.name: Aspire ES1-512
dmi.product.version: V1.06
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
xserver.bootTime: Mon May 22 19:57:24 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1
xserver.video_driver: modeset

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


** Tags: apport-bug compiz-0.9 i386 ubuntu zesty

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

Title:
  el equipo no puede actulizarce

Status in xorg package in Ubuntu:
  New

Bug description:
  El equipo no puede actualizar ya que hubo un error , el sistema me
  dice que active el gestor de paquetes pero tampoco puedo activarlo ya
  que el sistema no me lo permite por favor necesito ayuda, saludos.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon May 22 21:07:51 2017
  DistUpgraded: 2017-04-24 08:27:07,949 DEBUG icon theme changed, re-reading
  DistroCodename: zesty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [1025:0936]
  InstallationDate: Installed on 2017-04-03 (50 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
  MachineType: Acer Aspire ES1-512
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic 
root=UUID=e483ca57-0769-4213-9cb0-a725150eac9b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to zesty on 2017-04-24 (28 days ago)
  dmi.bios.date: 08/11/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Aspire ES1-512
  dmi.board.vendor: Acer
  dmi.board.version: V1.06
  dmi.chassis.asset.tag: No Asset

[Desktop-packages] [Bug 1686077] Re: Own org.gnome.SettingsDaemon.MediaKeys D-Bus name too

2017-05-22 Thread Jeremy Bicha

I installed gnome-settings-daemon 3.24.2-0ubuntu0.1 on Ubuntu GNOME
17.04 and successfully completed this test case with d-feet.

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

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

Title:
  Own org.gnome.SettingsDaemon.MediaKeys D-Bus name too

Status in GNOME Settings Daemon:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-settings-daemon source package in Xenial:
  Triaged
Status in unity-settings-daemon source package in Xenial:
  Triaged
Status in gnome-settings-daemon source package in Yakkety:
  Triaged
Status in unity-settings-daemon source package in Yakkety:
  Triaged
Status in gnome-settings-daemon source package in Zesty:
  Fix Committed
Status in unity-settings-daemon source package in Zesty:
  Triaged
Status in gnome-settings-daemon package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  This bugfix enabled gnome-settings-daemon's multimedia key support to work 
according to what the API has said for years (in addition to the way it's been 
commonly used).

  https://git.gnome.org/browse/gnome-settings-
  daemon/commit/?h=gnome-3-24=42f75ed4cdc86498d6e02e511a1314b8916bd4aa

  https://mail.gnome.org/archives/desktop-devel-
  list/2017-April/msg00069.html

  The SRU justification is that newer versions of apps will be switching
  to the D-Bus name in the API documentation. If someone installs the
  newer version from a PPA or a Flatpak or Snap, the multimedia key
  support should continue working.

  Test Case
  =
  Install this update on Ubuntu GNOME.
  Reboot
  Install d-feet then run d-feet
  Switch to the session tab.
  Type 'settings' into the search box.'
  In the list of results there should be both org.gnome.SettingsDaemon and 
org.gnome.SettingsDaemon.MediaKeys with cmd: 
/usr/lib/gnome-settings-daemon/gsd-media-keys

  Regression Potential
  
  This should just make gnome(unity)-settings-daemon own both the commonly used 
D-Bus name and the one actually defined in the API docs.

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

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

[Desktop-packages] [Bug 1689610] Re: Update gnome-settings-daemon to 3.24.2

2017-05-22 Thread Jeremy Bicha

I have installed gnome-settings-daemon 3.24.2-0ubuntu0.1 on Ubuntu GNOME
17.04, rebooted and things look fine.

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

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

Title:
  Update gnome-settings-daemon to 3.24.2

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

Bug description:
  Impact
  --
  gnome-settings-daemon 3.24.2 is a bugfix release in the stable 3.24 series.

  https://git.gnome.org/browse/gnome-settings-daemon/log?h=gnome-3-24
  https://git.gnome.org/browse/gnome-settings-daemon/tree/NEWS?h=gnome-3-24

  gnome-settings-daemon itself is used by Ubuntu Budgie and Ubuntu GNOME.
  The schemas are also used by Ubuntu, Ubuntu Kylin and Ubuntu MATE. And Ubuntu 
Touch.

  This also fixes Hi-DPI in GDM (LP: #1685035), the brightness control
  in some dual-GPU computers (LP: #1683445), and adds a D-Bus API to
  match the mediakeys documentation (LP: #1686077)

  Test Case
  -
  After installing the update, reboot and log into GNOME

  Regression Potential
  
  There was a minimal fix for rfkill handling (to revert GNOME's behavior back 
to how it worked in Ubuntu 16.04 LTS), but because this ends up causing 
regressions for some other people, I have reverted this commit since it's 
better not to introduce a new bug into a stable release. See 
https://bugzilla.gnome.org/760517 if you want more details.

  The other changes look like minimal bugfixes. Schemas shouldn't be
  affected in this update.

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

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

[Desktop-packages] [Bug 1692661] Re: evolution-source-registry crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

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

** Information type changed from Private Security to Public

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

Title:
  evolution-source-registry crashed with SIGABRT in
  __gnu_cxx::__verbose_terminate_handler()

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: evolution-data-server 3.22.7-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.5-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon May 22 16:51:56 2017
  ExecutablePath: /usr/lib/evolution/evolution-source-registry
  InstallationDate: Installed on 2017-03-07 (76 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  ProcCmdline: /usr/lib/evolution/evolution-source-registry
  ProcEnviron:
   LANG=en_ZA.UTF-8
   LANGUAGE=en_ZA:en
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: evolution-data-server
  StacktraceTop:
   __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   google::protobuf::internal::LogMessage::Finish() () from 
/usr/lib/x86_64-linux-gnu/libprotobuf.so.10
  Title: evolution-source-registry crashed with SIGABRT in 
__gnu_cxx::__verbose_terminate_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1692661/+subscriptions

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

[Desktop-packages] [Bug 1691839] Re: nvidia-graphics-drivers-304 304.135-0ubuntu1 ADT test failure with linux 4.11.0-3.8

2017-05-22 Thread Seth Forshee

I updated the package with fixes for 4.11:

http://people.canonical.com/~sforshee/nvidia-updates/nvidia-graphics-
drivers-304/

Test builds are available in the c-k-t/unstable ppa. 4.11 kernel builds
are available in the c-k-t ppa.

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

** 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/1691839

Title:
  nvidia-graphics-drivers-304 304.135-0ubuntu1 ADT test failure with
  linux 4.11.0-3.8

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

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-ppa/artful/amd64/n/nvidia-graphics-drivers-304/20170517_172947_fd0b4@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-ppa/artful/i386/n/nvidia-graphics-drivers-304/20170517_153741_fd0b4@/log.gz

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

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

[Desktop-packages] [Bug 1691841] Re: nvidia-graphics-drivers-340 340.102-0ubuntu3 ADT test failure with linux 4.11.0-3.8

2017-05-22 Thread Seth Forshee

I updated the package with fixes for 4.11:

http://people.canonical.com/~sforshee/nvidia-updates/nvidia-graphics-
drivers-340/

Test builds are available in the c-k-t/unstable ppa. 4.11 kernel builds
are available in the c-k-t ppa.

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Importance: Undecided => High

** 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/1691841

Title:
  nvidia-graphics-drivers-340 340.102-0ubuntu3 ADT test failure with
  linux 4.11.0-3.8

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-artful-canonical-kernel-team-ppa/artful/amd64/n/nvidia-graphics-drivers-340/20170517_172744_3d553@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-ppa/artful/i386/n/nvidia-graphics-drivers-340/20170517_152615_3d553@/log.gz

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

-- 
Mailing list: https://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 1692487] Re: package fonts-lmodern 2.004.5-1 failed to install/upgrade: package fonts-lmodern is not ready for configuration cannot configure (current status 'half-installe

2017-05-22 Thread Ma Yingchong

Thank you for your reply and kind help.


Best regards,



From: boun...@canonical.com  on behalf of Seth Arnold 
<1692...@bugs.launchpad.net>
Sent: Tuesday, May 23, 2017 2:12
To: benben...@msn.com
Subject: [Bug 1692487] Re: package fonts-lmodern 2.004.5-1 failed to 
install/upgrade: package fonts-lmodern is not ready for configuration cannot 
configure (current status 'half-installed')

Hello,

I suggest trying:

sudo apt-get -f install
sudo dpkg --configure -a

Thanks

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1692487
Bug #1692487 “package fonts-lmodern 2.004.5-1 failed to install/...” : Bugs : 
lmodern package : Ubuntu
bugs.launchpad.net
dpkg: error processing package fonts-lmodern (--configure): package 
fonts-lmodern is not ready for configuration cannot configure (current status 
'half-installed') Errors were encountered while processing: fonts-lmodern 
ProblemType: Package DistroRelease: Ubuntu 16.04 Package: fonts-lmodern 
2.004.5-1 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 
4.4.0-78-generic x86_64 NonfreeKernelModules: wl ApportVersion: 
2.20.1-0ubuntu2.5 AptOrdering: fonts-lmodern: Configure ...



Title:
  package fonts-lmodern 2.004.5-1 failed to install/upgrade: package
  fonts-lmodern is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in lmodern package in Ubuntu:
  New

Bug description:
  dpkg: error processing package fonts-lmodern (--configure):
   package fonts-lmodern is not ready for configuration
   cannot configure (current status 'half-installed')
  Errors were encountered while processing:
   fonts-lmodern

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fonts-lmodern 2.004.5-1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  AptOrdering:
   fonts-lmodern: Configure
   lmodern: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon May 22 12:44:31 2017
  DpkgTerminalLog:
   dpkg: error processing package fonts-lmodern (--configure):
package fonts-lmodern is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package fonts-lmodern is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2015-07-25 (666 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: lmodern
  Title: package fonts-lmodern 2.004.5-1 failed to install/upgrade: package 
fonts-lmodern is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: Upgraded to xenial on 2017-05-21 (0 days ago)
  modified.conffile..etc.fonts.conf.avail.65-fonts-lmodern.conf: [deleted]

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

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

Title:
  package fonts-lmodern 2.004.5-1 failed to install/upgrade: package
  fonts-lmodern is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in lmodern package in Ubuntu:
  New

Bug description:
  dpkg: error processing package fonts-lmodern (--configure):
   package fonts-lmodern is not ready for configuration
   cannot configure (current status 'half-installed')
  Errors were encountered while processing:
   fonts-lmodern

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fonts-lmodern 2.004.5-1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  AptOrdering:
   fonts-lmodern: Configure
   lmodern: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon May 22 12:44:31 2017
  DpkgTerminalLog:
   dpkg: error processing package fonts-lmodern (--configure):
package fonts-lmodern is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package fonts-lmodern is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2015-07-25 (666 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: lmodern
  Title: package fonts-lmodern 2.004.5-1 failed to install/upgrade: package 
fonts-lmodern is not ready for configuration  cannot configure (current status 
'half-installed')

[Desktop-packages] [Bug 1692487] Re: package fonts-lmodern 2.004.5-1 failed to install/upgrade: package fonts-lmodern is not ready for configuration cannot configure (current status 'half-installed')

Hello,

I suggest trying:

sudo apt-get -f install
sudo dpkg --configure -a

Thanks

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

Title:
  package fonts-lmodern 2.004.5-1 failed to install/upgrade: package
  fonts-lmodern is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in lmodern package in Ubuntu:
  New

Bug description:
  dpkg: error processing package fonts-lmodern (--configure):
   package fonts-lmodern is not ready for configuration
   cannot configure (current status 'half-installed')
  Errors were encountered while processing:
   fonts-lmodern

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fonts-lmodern 2.004.5-1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  AptOrdering:
   fonts-lmodern: Configure
   lmodern: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon May 22 12:44:31 2017
  DpkgTerminalLog:
   dpkg: error processing package fonts-lmodern (--configure):
package fonts-lmodern is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package fonts-lmodern is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2015-07-25 (666 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: lmodern
  Title: package fonts-lmodern 2.004.5-1 failed to install/upgrade: package 
fonts-lmodern is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: Upgraded to xenial on 2017-05-21 (0 days ago)
  modified.conffile..etc.fonts.conf.avail.65-fonts-lmodern.conf: [deleted]

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

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

[Desktop-packages] [Bug 1692487] Re: package fonts-lmodern 2.004.5-1 failed to install/upgrade: package fonts-lmodern is not ready for configuration cannot configure (current status 'half-installed')

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

** Information type changed from Private Security to Public

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

Title:
  package fonts-lmodern 2.004.5-1 failed to install/upgrade: package
  fonts-lmodern is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in lmodern package in Ubuntu:
  New

Bug description:
  dpkg: error processing package fonts-lmodern (--configure):
   package fonts-lmodern is not ready for configuration
   cannot configure (current status 'half-installed')
  Errors were encountered while processing:
   fonts-lmodern

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fonts-lmodern 2.004.5-1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  AptOrdering:
   fonts-lmodern: Configure
   lmodern: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon May 22 12:44:31 2017
  DpkgTerminalLog:
   dpkg: error processing package fonts-lmodern (--configure):
package fonts-lmodern is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package fonts-lmodern is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2015-07-25 (666 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: lmodern
  Title: package fonts-lmodern 2.004.5-1 failed to install/upgrade: package 
fonts-lmodern is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: Upgraded to xenial on 2017-05-21 (0 days ago)
  modified.conffile..etc.fonts.conf.avail.65-fonts-lmodern.conf: [deleted]

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

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

[Desktop-packages] [Bug 1692263] Re: amd64 apport-bug trusty ubuntu

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

** Information type changed from Private Security to Public

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

Title:
  amd64 apport-bug trusty ubuntu

Status in xorg package in Ubuntu:
  New

Bug description:
  amd64 apport-bug trusty ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-78.99~14.04.2-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun May 21 00:39:55 2017
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.36, 4.4.0-78-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:06ab]
  InstallationDate: Installed on 2017-03-20 (61 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3551
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-78-generic 
root=/dev/mapper/ubuntu--vg-root ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 04XH5N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd07/07/2015:svnDellInc.:pnInspiron3551:pvrA04:rvnDellInc.:rn04XH5N:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3551
  dmi.product.version: A04
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat May 20 19:24:16 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1156 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty1

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

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

[Desktop-packages] [Bug 1692733] [NEW] package libtxc-dxtn-s2tc:i386 1.0+git20151227-2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemptin

2017-05-22 Thread dulbirakan

Public bug reported:

Was trying to install steam. This package was left unconfigured dpkg
does not like what is going on.

dpkg: error processing package libtxc-dxtn-s2tc:i386 (--configure):
 package is in a very bad inconsistent state; you should
 reinstall it before attempting configuration
dpkg: dependency problems prevent configuration of steam:i386:
 steam:i386 depends on libtxc-dxtn0; however:
  Package libtxc-dxtn-s2tc:i386 which provides libtxc-dxtn0 is not configured 
yet.

dpkg: error processing package steam:i386 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of steam-installer:
 steam-installer depends on steam (= 1:1.0.0.54+repack-2ubuntu5); however:
  Package steam:i386 is not configured yet.

dpkg: error processing package steam-installer (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 libtxc-dxtn-s2tc:i386
 steam:i386
 steam-installer

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libtxc-dxtn-s2tc:i386 1.0+git20151227-2
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.1
AptOrdering: NULL: ConfigurePending
Architecture: amd64
Date: Mon May 22 18:24:11 2017
Dependencies:
 gcc-6-base 6.3.0-12ubuntu2
 libc6 2.24-9ubuntu2
 libgcc1 1:6.3.0-12ubuntu2
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-05-22 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: s2tc
Title: package libtxc-dxtn-s2tc:i386 1.0+git20151227-2 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: s2tc (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 zesty

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

Title:
  package libtxc-dxtn-s2tc:i386 1.0+git20151227-2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in s2tc package in Ubuntu:
  New

Bug description:
  Was trying to install steam. This package was left unconfigured dpkg
  does not like what is going on.

  dpkg: error processing package libtxc-dxtn-s2tc:i386 (--configure):
   package is in a very bad inconsistent state; you should
   reinstall it before attempting configuration
  dpkg: dependency problems prevent configuration of steam:i386:
   steam:i386 depends on libtxc-dxtn0; however:
Package libtxc-dxtn-s2tc:i386 which provides libtxc-dxtn0 is not configured 
yet.

  dpkg: error processing package steam:i386 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of steam-installer:
   steam-installer depends on steam (= 1:1.0.0.54+repack-2ubuntu5); however:
Package steam:i386 is not configured yet.

  dpkg: error processing package steam-installer (--configure):
   dependency problems - leaving unconfigured
  Errors were encountered while processing:
   libtxc-dxtn-s2tc:i386
   steam:i386
   steam-installer

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libtxc-dxtn-s2tc:i386 1.0+git20151227-2
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.1
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  Date: Mon May 22 18:24:11 2017
  Dependencies:
   gcc-6-base 6.3.0-12ubuntu2
   libc6 2.24-9ubuntu2
   libgcc1 1:6.3.0-12ubuntu2
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-22 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: s2tc
  Title: package libtxc-dxtn-s2tc:i386 1.0+git20151227-2 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/s2tc/+bug/1692733/+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 1692731] Re: package libtexluajit2:i386 2015.20160222.37495-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting

** Tags removed: need-duplicate-check

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

Title:
  package libtexluajit2:i386 2015.20160222.37495-1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in texlive-bin package in Ubuntu:
  New

Bug description:
  The package crashed and not work properly!!

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libtexluajit2:i386 2015.20160222.37495-1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  Date: Mon May 22 18:04:21 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu7
   libgcc1 1:6.0.1-0ubuntu1
  DuplicateSignature:
   package:libtexluajit2:i386:2015.20160222.37495-1
   Processing triggers for mime-support (3.59ubuntu1) ...
   dpkg: error processing package libtexluajit2:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-21 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: texlive-bin
  Title: package libtexluajit2:i386 2015.20160222.37495-1 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/texlive-bin/+bug/1692731/+subscriptions

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

[Desktop-packages] [Bug 1692731] [NEW] package libtexluajit2:i386 2015.20160222.37495-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempti

2017-05-22 Thread Yvan Cipiran

Public bug reported:

The package crashed and not work properly!!

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libtexluajit2:i386 2015.20160222.37495-1
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic i686
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: i386
Date: Mon May 22 18:04:21 2017
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu7
 libgcc1 1:6.0.1-0ubuntu1
DuplicateSignature:
 package:libtexluajit2:i386:2015.20160222.37495-1
 Processing triggers for mime-support (3.59ubuntu1) ...
 dpkg: error processing package libtexluajit2:i386 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-05-21 (1 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: texlive-bin
Title: package libtexluajit2:i386 2015.20160222.37495-1 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: texlive-bin (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package libtexluajit2:i386 2015.20160222.37495-1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in texlive-bin package in Ubuntu:
  New

Bug description:
  The package crashed and not work properly!!

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libtexluajit2:i386 2015.20160222.37495-1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  Date: Mon May 22 18:04:21 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu7
   libgcc1 1:6.0.1-0ubuntu1
  DuplicateSignature:
   package:libtexluajit2:i386:2015.20160222.37495-1
   Processing triggers for mime-support (3.59ubuntu1) ...
   dpkg: error processing package libtexluajit2:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-21 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: texlive-bin
  Title: package libtexluajit2:i386 2015.20160222.37495-1 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/texlive-bin/+bug/1692731/+subscriptions

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

[Desktop-packages] [Bug 1173648] Re: F3 side pane is gone in Nautilus 3.6+

2017-05-22 Thread Norbert

As far I can understand - it is time to drop GNOME 3. Modern Nautilus is
ugly, Evince is ugly, Gedit is ugly and so on.

I switched to MATE with its Caja and other good stuff.

** Tags added: trusty xenial yakkety zesty

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

Title:
  F3 side pane is gone in Nautilus 3.6+

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

Bug description:
  the double pane functionality that exists in older Nautilus versions is gone 
in the 3.6 version.
  that is a huge usability issue.

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

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

[Desktop-packages] [Bug 1613043] Re: package libglib2.0-dev 2.48.1-1~ubuntu16.04.1 failed to install/upgrade: подпроцесс установлен сценарий pre-removal возвратил код ошибки 1

2017-05-22 Thread Brian Murray

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

** This bug has been marked a duplicate of bug 1682934
   python3 in /usr/local/bin can cause python3 packages to fail to install

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

Title:
  package libglib2.0-dev 2.48.1-1~ubuntu16.04.1 failed to
  install/upgrade: подпроцесс установлен сценарий pre-removal возвратил
  код ошибки 1

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  I don't know.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libglib2.0-dev 2.48.1-1~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Aug 13 13:53:39 2016
  ErrorMessage: подпроцесс установлен сценарий pre-removal возвратил код ошибки 
1
  InstallationDate: Installed on 2015-08-12 (367 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: glib2.0
  Title: package libglib2.0-dev 2.48.1-1~ubuntu16.04.1 failed to 
install/upgrade: подпроцесс установлен сценарий pre-removal возвратил код 
ошибки 1
  UpgradeStatus: Upgraded to xenial on 2016-07-30 (14 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1613043/+subscriptions

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

[Desktop-packages] [Bug 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss

2017-05-22 Thread spike speigel

Here's an earlier bug report (~Dec 2015):

http://lkml.iu.edu/hypermail/linux/kernel/1512.1/02819.html

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

Title:
  XPS 13 9360, Realtek ALC3246, Headphone audio hiss

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+subscriptions

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

[Desktop-packages] [Bug 1173648] Re: F3 side pane is gone in Nautilus 3.6+

2017-05-22 Thread v1nce

Before upgrading from 14.04 to 16.04 I should have remembered I lost some hours 
tweaking my system to make it usable not just like a tablet toy.
Among those tweaks there was the complete replacement of nautilus by nemo (or 
something like this) 

After upgrading to 16.04, the compress contextual menu is gone from nemo.
Reinstalling nemo-file-roller didn't fix the problem.

So right now I'm left with two non working file browser : nautilus with
no 2nd panel and nemo with no compress menu.

I guess tweaking the nemo actions will return my compress action but question 
still remains : why the hell was the 2nd panel removed from nautilus ? 
And no two instances (one on left other on right side of screen) is NOT a 
solution

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

Title:
  F3 side pane is gone in Nautilus 3.6+

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

Bug description:
  the double pane functionality that exists in older Nautilus versions is gone 
in the 3.6 version.
  that is a huge usability issue.

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

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

[Desktop-packages] [Bug 1665785] Re: [N501VW, Realtek ALC668, Black Headphone Out, Right] Background noise or low volume

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [N501VW, Realtek ALC668, Black Headphone Out, Right] Background noise
  or low volume

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  There is a background hissing/squeaking noise in my headphones every time I 
resume suspend.
  Speakers and HDMI audio are not affected.
  I've tried many solutions to fix it (alsa force-reload etc.), but none of 
them worked well.
  More detailes you can find here:
  
http://askubuntu.com/questions/884051/constant-hissing-sound-after-suspend-asus-zenbook-ux501-vw

  
  Standard four questions:
  1) Ubuntu 16.04.1 LTS
  2) Kernel 4.8.17-040817-generic (also tried 4.4.0 and 4.3.5)
  3) When I resume suspend I hear no noise unless I play something
  4) Right after suspend resume there is a background noise

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.8.17-040817-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   firesword   3563 F...m pulseaudio
   /dev/snd/pcmC0D0p:   firesword   3563 F...m pulseaudio
   /dev/snd/controlC0:  firesword   3563 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Feb 17 23:54:52 2017
  InstallationDate: Installed on 2017-02-17 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Right
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: High background noise, or volume is too low
  Title: [N501VW, Realtek ALC668, Black Headphone Out, Right] Background noise 
or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/28/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  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.:bvrN501VW.304:bd11/28/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  modified.conffile..etc.modprobe.d.alsa-base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-02-17T21:26:16.180413

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1665785/+subscriptions

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

[Desktop-packages] [Bug 1692712] Re: language-selector-gnome should not depend on aptdaemon

2017-05-22 Thread Gunnar Hjalmarsson

I'm not sure what you mean. Currently language-selector-gnome does
depend on aptdaemon, even if it soon may be changed due to bug #1673258.

Marking this as a duplicate of that other bug. Please let me know if I
misunderstood something.

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

Title:
  language-selector-gnome should not depend on aptdaemon

Status in language-selector package in Ubuntu:
  New

Bug description:
  The language-selector-gnome should not depend on aptdaemon, but when I
  tried to remove aptdaemon, language-selector-gnome complains:

  apt-get --purge install aptdaemon- language-selector-gnome+
  The following packages have unmet dependencies:
   language-selector-gnome : Depends: aptdaemon (>= 0.40+bzr527) but it is not 
going to be installed
 Depends: python3-aptdaemon.gtk3widgets but it is 
not going to be installed
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1692712/+subscriptions

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

[Desktop-packages] [Bug 1692714] [NEW] Unstable Wifi: re-Authentication fails after wifi drops and reconnects

2017-05-22 Thread Laurens Kils-Hütten

Public bug reported:

I see frequent disconnects due to reason=4, which would be o.k. if
reconnects worked fine. However often on reconnects 4-way handshake
times out and I'm prompted to re-enter our wifi pass-phrase, sometimes
as frequent as every few minutes - a major annoyance :-(

Problem seems to depend a bit on network traffic. However only my
notebook with ubuntu 17.04. seems to be affected. Two iphones, an
android phone and a chromebook seem to have no wifi problems at all.

Also, when I set up wls2 manually in /etc/network/interfaces I haven't
seen failed reconnects so far.

I have had this problem since 16.04. Various work arounds suggested on
the web like changing wifi channel, disabling IPv6, or disabling DHCP
haven't affected this problem.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: network-manager 1.4.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon May 22 22:34:01 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-08-28 (267 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
IpRoute:
 default via 192.168.2.1 dev wls2 proto static metric 600 
 169.254.0.0/16 dev wls2 scope link metric 1000 
 192.168.2.0/24 dev wls2 proto kernel scope link src 192.168.2.129 metric 600 
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
NetworkManager.conf:
 [main]
 plugins=ifupdown,keyfile
 
 [ifupdown]
 managed=false
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to zesty on 2017-04-14 (38 days ago)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug zesty

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

Title:
  Unstable Wifi: re-Authentication fails after wifi drops and reconnects

Status in network-manager package in Ubuntu:
  New

Bug description:
  I see frequent disconnects due to reason=4, which would be o.k. if
  reconnects worked fine. However often on reconnects 4-way handshake
  times out and I'm prompted to re-enter our wifi pass-phrase, sometimes
  as frequent as every few minutes - a major annoyance :-(

  Problem seems to depend a bit on network traffic. However only my
  notebook with ubuntu 17.04. seems to be affected. Two iphones, an
  android phone and a chromebook seem to have no wifi problems at all.

  Also, when I set up wls2 manually in /etc/network/interfaces I haven't
  seen failed reconnects so far.

  I have had this problem since 16.04. Various work arounds suggested on
  the web like changing wifi channel, disabling IPv6, or disabling DHCP
  haven't affected this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon May 22 22:34:01 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-08-28 (267 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  IpRoute:
   default via 192.168.2.1 dev wls2 proto static metric 600 
   169.254.0.0/16 dev wls2 scope link metric 1000 
   192.168.2.0/24 dev wls2 proto kernel scope link src 192.168.2.129 metric 600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (38 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1632019] Re: [*buntu 16.04 / PRIME] nvidia-smi not work if iGPU as the primary display

2017-05-22 Thread José Tomás Atria

I can confirm this bug on ubuntu 17.04.

running nvidia-smi fails:

jta@rachael:~$ nvidia-smi
NVIDIA-SMI couldn't find libnvidia-ml.so library in your system. Please make 
sure that the NVIDIA Display Driver is properly installed and present in your 
system.
Please also try adding directory that contains libnvidia-ml.so to your system 
PATH.

adding LD_PRELOAD with the location of libnvidia-ml.so and running
nvidia-smi works:

jta@rachael:~$ LD_PRELOAD=/usr/lib/nvidia-375/libnvidia-ml.so nvidia-smi
Mon May 22 16:37:10 2017   
+-+
| NVIDIA-SMI 375.39 Driver Version: 375.39|
|---+--+--+
| GPU  NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap| Memory-Usage | GPU-Util  Compute M. |
|===+==+==|
|   0  Quadro K2000M   Off  | :01:00.0 Off |  N/A |
| N/A   41CP0N/A /  N/A |  0MiB /  1999MiB |  0%  Default |
+---+--+--+
   
+-+
| Processes:   GPU Memory |
|  GPU   PID  Type  Process name   Usage  |
|=|
|  No running processes found |
+-+

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

Title:
  [*buntu 16.04 / PRIME] nvidia-smi not work if iGPU as the primary
  display

Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Related links:
  
https://devtalk.nvidia.com/default/topic/876441/linux/monitoring-nvidia-gpu-when-intel-igpu-as-primary-display/

  https://devtalk.nvidia.com/default/topic/970144/linux/intel-for-
  display-nvidia-for-cuda-optimus-bug-/

  So the problem is that you can not monitor the temperature with
  nvidia-smi and also can't set the fan speed if iGPU is as a primary
  display selected from Prime profiles in Nvidia-Settings.

  In the second link it is mentioned a workaround that might give a clue
  about the cause of the problem. That is, I think 'nvidia-smi " should
  work by default without running this workaround as root.

  To make it clear, nvidia-smi works as expected if you have selected
  nvidia gpu as the primary display.

  Tested with nvidia-361 from official Ubuntu 16.04 repos. Installed libcuda1 
and nvidia-prime packages.
  

  As additional information regarding the Proprietary GPU Drivers PPA (since it 
is the only way Ubuntu users can update the drivers with .deb packages):
  https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa

  If you install the drivers from the PPA (I tested 370.28 and 367.44)
  and iGPU as the primary display using PRIME, you can not even able to
  use CUDA in applications such as Blender/Cycles (CUDA is not available
  in Blender for GPU compute). This problem (not having CUDA available)
  does not occur with drivers from official repositories of Ubuntu, for
  example 361.42 is working well in Kubuntu 16.04. So I do not know if
  it is because PPA packages are built differently from the official
  repository. It would be good you to take a look at this.

  Thanks.

  System and Hardware specs:

  i7 3770 - HD 4000
  GTX 960
  Kubuntu 16.04 64bits

  $ lspci | grep -i vga
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09)
  01:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 960] 
(rev a1)

  $ uname -r
  4.4.0-38-generic

  nvidia 361 from official Ubuntu 16.04 repos. Installed libcuda1 and
  nvidia-prime packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1632019/+subscriptions

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

[Desktop-packages] [Bug 1632019] Re: [*buntu 16.04 / PRIME] nvidia-smi not work if iGPU as the primary display

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

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

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

Title:
[*buntu 16.04 / PRIME] nvidia-smi not work if iGPU as the primary
display

Status in ubuntu-drivers-common package in Ubuntu:
Confirmed

Bug description:
Related links:

https://devtalk.nvidia.com/default/topic/876441/linux/monitoring-nvidia-gpu-when-intel-igpu-as-primary-display/

https://devtalk.nvidia.com/default/topic/970144/linux/intel-for-
display-nvidia-for-cuda-optimus-bug-/

So the problem is that you can not monitor the temperature with
nvidia-smi and also can't set the fan speed if iGPU is as a primary
display selected from Prime profiles in Nvidia-Settings.

In the second link it is mentioned a workaround that might give a clue
about the cause of the problem. That is, I think 'nvidia-smi " should
work by default without running this workaround as root.

To make it clear, nvidia-smi works as expected if you have selected
nvidia gpu as the primary display.

Tested with nvidia-361 from official Ubuntu 16.04 repos. Installed libcuda1
and nvidia-prime packages.

As additional information regarding the Proprietary GPU Drivers PPA (since it
is the only way Ubuntu users can update the drivers with .deb packages):
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa

If you install the drivers from the PPA (I tested 370.28 and 367.44)
and iGPU as the primary display using PRIME, you can not even able to
use CUDA in applications such as Blender/Cycles (CUDA is not available
in Blender for GPU compute). This problem (not having CUDA available)
does not occur with drivers from official repositories of Ubuntu, for
example 361.42 is working well in Kubuntu 16.04. So I do not know if
it is because PPA packages are built differently from the official
repository. It would be good you to take a look at this.

Thanks.

System and Hardware specs:

i7 3770 - HD 4000
GTX 960
Kubuntu 16.04 64bits

$ lspci | grep -i vga
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen
Core processor Graphics Controller (rev 09)
01:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 960]
(rev a1)

$ uname -r
4.4.0-38-generic

nvidia 361 from official Ubuntu 16.04 repos. Installed libcuda1 and
nvidia-prime packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1632019/+subscriptions

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

[Desktop-packages] [Bug 1692710] [NEW] [System Product Name, Realtek ALC1200, Green Line Out, Rear] Pulseaudio, Jack and ALSA seem to work, but there's no sound output

2017-05-22 Thread Paul van Leeuwen

Public bug reported:

I've got Ubuntu 17.04 installed with KXStudio on top of that.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: pulseaudio 1:10.0-1ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-21.23-lowlatency 4.10.11
Uname: Linux 4.10.0-21-lowlatency x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Mon May 22 22:29:46 2017
InstallationDate: Installed on 2017-05-21 (1 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: HDA-Intel - HDA ATI SB
Symptom_Jack: Green Line Out, Rear
Title: [System Product Name, Realtek ALC1200, Green Line Out, Rear] Pulseaudio 
fails to detect card
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/05/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0801
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M3A78 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.:bvr0801:bd01/05/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A78PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


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

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

Title:
  [System Product Name, Realtek ALC1200, Green Line Out, Rear]
  Pulseaudio, Jack and ALSA seem to work, but there's no sound output

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I've got Ubuntu 17.04 installed with KXStudio on top of that.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-21.23-lowlatency 4.10.11
  Uname: Linux 4.10.0-21-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon May 22 22:29:46 2017
  InstallationDate: Installed on 2017-05-21 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA ATI SB
  Symptom_Jack: Green Line Out, Rear
  Title: [System Product Name, Realtek ALC1200, Green Line Out, Rear] 
Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/05/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0801
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M3A78 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.:bvr0801:bd01/05/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A78PRO: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/pulseaudio/+bug/1692710/+subscriptions

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

[Desktop-packages] [Bug 1692712] [NEW] language-selector-gnome should not depend on aptdaemon

2017-05-22 Thread Tong Sun

Public bug reported:

The language-selector-gnome should not depend on aptdaemon, but when I
tried to remove aptdaemon, language-selector-gnome complains:

apt-get --purge install aptdaemon- language-selector-gnome+
The following packages have unmet dependencies:
 language-selector-gnome : Depends: aptdaemon (>= 0.40+bzr527) but it is not 
going to be installed
   Depends: python3-aptdaemon.gtk3widgets but it is not 
going to be installed
E: Unable to correct problems, you have held broken packages.

** Affects: language-selector (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  language-selector-gnome should not depend on aptdaemon

Status in language-selector package in Ubuntu:
  New

Bug description:
  The language-selector-gnome should not depend on aptdaemon, but when I
  tried to remove aptdaemon, language-selector-gnome complains:

  apt-get --purge install aptdaemon- language-selector-gnome+
  The following packages have unmet dependencies:
   language-selector-gnome : Depends: aptdaemon (>= 0.40+bzr527) but it is not 
going to be installed
 Depends: python3-aptdaemon.gtk3widgets but it is 
not going to be installed
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1692712/+subscriptions

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

[Desktop-packages] [Bug 1692705] Re: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned

** Tags removed: need-duplicate-check

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

Title:
  package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade:
  triggers looping, abandoned

Status in fontconfig package in Ubuntu:
  New

Bug description:
  no idea just reporting this error i get on startup

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fontconfig 2.11.94-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Tue May 23 03:51:46 2017
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-05-19 (734 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2017-05-22 (0 days ago)

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

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

[Desktop-packages] [Bug 1692705] [NEW] package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned

2017-05-22 Thread Dino

Public bug reported:

no idea just reporting this error i get on startup

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: fontconfig 2.11.94-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Tue May 23 03:51:46 2017
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2015-05-19 (734 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: fontconfig
Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
triggers looping, abandoned
UpgradeStatus: Upgraded to xenial on 2017-05-22 (0 days ago)

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

Title:
  package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade:
  triggers looping, abandoned

Status in fontconfig package in Ubuntu:
  New

Bug description:
  no idea just reporting this error i get on startup

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fontconfig 2.11.94-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Tue May 23 03:51:46 2017
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-05-19 (734 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2017-05-22 (0 days ago)

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

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

[Desktop-packages] [Bug 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

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 gconf in Ubuntu.
https://bugs.launchpad.net/bugs/1688721

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

Status in gconf package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  = Test Case =
  1. Download the debian package of Chrome from google
  2. Open nautilus and double-click on the file to launch ubuntu software
  3. Install the package and proceed with the installation

  = Expected result = 
  Chrome installs correctly

  = Actual result =
  The installation hangs on the following command in gconf2-common.postinst

  ucf /usr/share/gconf/default.path /etc/gconf/2/path


  = Original Report =
  I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
  This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
  The same file was successfully installed with gdebi.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  6 13:56:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1692671] Re: intel driver fails to reenable display

** Attachment added: "lspci -v"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1692671/+attachment/4881544/+files/lspci.txt

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

Title:
  intel driver fails to reenable display

Status in xorg package in Ubuntu:
  New

Bug description:
  if the display is sent to sleep it won't wake up. If I go to tty1 or
  tty2 I'm pulled back to tty7 (?) within seconds.

  sometimes if I ctrl-alt-del I'm sent back to the login screen and from
  there I can resume the session.

  everything was working fine with my previous (1920x1080) display, but
  since I switched to a 3840x2160 display the only reliable solution to
  get the computer back from blanking is pressing the power button. I
  can then see the shutdown "splash" and after powering it back again
  everything is back to normal. until it blanks the screen again
  obviusly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon May 22 19:16:43 2017
  InstallationDate: Installed on 2015-12-27 (512 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-27 (389 days ago)

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

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

[Desktop-packages] [Bug 1692671] Re: intel driver fails to reenable display

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1692671/+attachment/4881545/+files/dmesg.txt

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

Title:
  intel driver fails to reenable display

Status in xorg package in Ubuntu:
  New

Bug description:
  if the display is sent to sleep it won't wake up. If I go to tty1 or
  tty2 I'm pulled back to tty7 (?) within seconds.

  sometimes if I ctrl-alt-del I'm sent back to the login screen and from
  there I can resume the session.

  everything was working fine with my previous (1920x1080) display, but
  since I switched to a 3840x2160 display the only reliable solution to
  get the computer back from blanking is pressing the power button. I
  can then see the shutdown "splash" and after powering it back again
  everything is back to normal. until it blanks the screen again
  obviusly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon May 22 19:16:43 2017
  InstallationDate: Installed on 2015-12-27 (512 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-27 (389 days ago)

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

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

[Desktop-packages] [Bug 1692671] Re: intel driver fails to reenable display

** Attachment added: "sudo get-edid | parse-edid"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1692671/+attachment/4881543/+files/edid.txt

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

Title:
  intel driver fails to reenable display

Status in xorg package in Ubuntu:
  New

Bug description:
  if the display is sent to sleep it won't wake up. If I go to tty1 or
  tty2 I'm pulled back to tty7 (?) within seconds.

  sometimes if I ctrl-alt-del I'm sent back to the login screen and from
  there I can resume the session.

  everything was working fine with my previous (1920x1080) display, but
  since I switched to a 3840x2160 display the only reliable solution to
  get the computer back from blanking is pressing the power button. I
  can then see the shutdown "splash" and after powering it back again
  everything is back to normal. until it blanks the screen again
  obviusly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon May 22 19:16:43 2017
  InstallationDate: Installed on 2015-12-27 (512 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-27 (389 days ago)

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

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

[Desktop-packages] [Bug 1692671] [NEW] intel driver fails to reenable display

Public bug reported:

if the display is sent to sleep it won't wake up. If I go to tty1 or
tty2 I'm pulled back to tty7 (?) within seconds.

sometimes if I ctrl-alt-del I'm sent back to the login screen and from
there I can resume the session.

everything was working fine with my previous (1920x1080) display, but
since I switched to a 3840x2160 display the only reliable solution to
get the computer back from blanking is pressing the power button. I can
then see the shutdown "splash" and after powering it back again
everything is back to normal. until it blanks the screen again obviusly

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon May 22 19:16:43 2017
InstallationDate: Installed on 2015-12-27 (512 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-04-27 (389 days ago)

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


** Tags: amd64 apport-bug xenial

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

Title:
  intel driver fails to reenable display

Status in xorg package in Ubuntu:
  New

Bug description:
  if the display is sent to sleep it won't wake up. If I go to tty1 or
  tty2 I'm pulled back to tty7 (?) within seconds.

  sometimes if I ctrl-alt-del I'm sent back to the login screen and from
  there I can resume the session.

  everything was working fine with my previous (1920x1080) display, but
  since I switched to a 3840x2160 display the only reliable solution to
  get the computer back from blanking is pressing the power button. I
  can then see the shutdown "splash" and after powering it back again
  everything is back to normal. until it blanks the screen again
  obviusly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon May 22 19:16:43 2017
  InstallationDate: Installed on 2015-12-27 (512 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-27 (389 days ago)

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

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

[Desktop-packages] [Bug 1585084] Re: Volume notification keeps popping up constantly(the notifyosd bubble on top-right corner)

2017-05-22 Thread Brandon

Wow... Over a year with such a simple bug and no updates from anyone at
Ubuntu.. WOW... JUST WOW!!

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

Title:
Volume notification keeps popping up constantly(the notifyosd bubble
on top-right corner)

Status in pulseaudio package in Ubuntu:
Confirmed

Bug description:
I upgraded to Ubuntu 16.04 yesterday, I did a clean install while
preserving the home directory which is mounted in a separate
partition. Even during the installation I had constant volume
notification bubble appearing on the top-right corner of my screen, it
would come and go about twice every minute. I just thought it was due
to installing hardware drivers or something but the problem persisted
even when I booted into the freshly installed system. I did some
searching and two users reported the exact problem. And one more
suggested this happens because constant disconnect and reconnect of
the sound card which makes sense as the sound settings flashes briefly
during every popup. Someone on IRC suggested to kill pulseaudio and
thus restart it, that does not fix the issue. I also tried the Live
environment thinking it might be due to some old config files in home
partition (which was preserved during upgrade), but this problem
happens in the live environment as well, which makes sense because it
was present during installation as well.

Users with the same issue:
http://ubuntuforums.org/showthread.php?t=2323815
http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04

http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly

Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3
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
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: sidd 1651 F pulseaudio
/dev/snd/controlC0: sidd 1651 F pulseaudio
/dev/snd/controlC1: sidd 1651 F pulseaudio
CurrentDesktop: Unity
Date: Tue May 24 12:31:12 2016
InstallationDate: Installed on 2016-05-23 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/23/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0705
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A97 EVO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

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

[Desktop-packages] [Bug 1692437] Re: Monitors on second GPU not working after upgrade to zesty

2017-05-22 Thread Richard Eames

lspci and lshw show 2 GPUs. The builtin one, and the actual card, but
xrandr only lists one provider.

$ xrandr --listproviders 
Providers: number : 1
Provider 0: id: 0x56 cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 3 
associated providers: 0 name:KAVERI @ pci::00:01.0


Might be a bug in the radeon driver?

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

** Also affects: xserver-xorg-driver-radeonhd
   Importance: Undecided
   Status: New

** Attachment added: "lspci -vvv"
   
https://bugs.launchpad.net/xserver-xorg-driver-radeonhd/+bug/1692437/+attachment/4881502/+files/lspci.txt

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

Title:
  Monitors on second GPU not working after upgrade to zesty

Status in Light Display Manager:
  New
Status in xserver-xorg-driver-radeonhd:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  I'm not 100% sure this is the right package to file the bug against,
  but since upgrading to zesty the two monitors on my second GPU are no
  longer detected once I reach the greeter screen at login time.
  However, both of them display information during boot.

  Let me know how I can narrow down the bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: lightdm 1.22.0-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon May 22 01:42:58 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-29 (388 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to zesty on 2017-05-22 (0 days ago)

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

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

[Desktop-packages] [Bug 1692594] [NEW] package libgail-3-0:amd64 3.18.9-1ubuntu3.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting co

2017-05-22 Thread Arun Joshi

Public bug reported:

I always get system error during system start-up

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libgail-3-0:amd64 3.18.9-1ubuntu3.3
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Mon May 15 23:25:21 2017
DuplicateSignature:
 package:libgail-3-0:amd64:3.18.9-1ubuntu3.3
 Setting up libgtk-3-0:amd64 (3.18.9-1ubuntu3.3) ...
 dpkg: error processing package libgail-3-0:amd64 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2015-01-29 (844 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: gtk+3.0
Title: package libgail-3-0:amd64 3.18.9-1ubuntu3.3 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: Upgraded to xenial on 2016-07-31 (294 days ago)

** Affects: gtk+3.0 (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 gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1692594

Title:
  package libgail-3-0:amd64 3.18.9-1ubuntu3.3 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  I always get system error during system start-up

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgail-3-0:amd64 3.18.9-1ubuntu3.3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Mon May 15 23:25:21 2017
  DuplicateSignature:
   package:libgail-3-0:amd64:3.18.9-1ubuntu3.3
   Setting up libgtk-3-0:amd64 (3.18.9-1ubuntu3.3) ...
   dpkg: error processing package libgail-3-0:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2015-01-29 (844 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: gtk+3.0
  Title: package libgail-3-0:amd64 3.18.9-1ubuntu3.3 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: Upgraded to xenial on 2016-07-31 (294 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1692594/+subscriptions

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

[Desktop-packages] [Bug 1663157] Re: Guest session processes are not confined in 16.10 and newer releases

2017-05-22 Thread Balint Reczey

** Changed in: lightdm (Ubuntu Artful)
   Status: Triaged => In Progress

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

Title:
  Guest session processes are not confined in 16.10 and newer releases

Status in Light Display Manager:
  New
Status in apparmor package in Ubuntu:
  Invalid
Status in lightdm package in Ubuntu:
  In Progress
Status in lightdm source package in Yakkety:
  Fix Released
Status in lightdm source package in Zesty:
  Fix Released
Status in lightdm source package in Artful:
  In Progress

Bug description:
  Processes launched under a lightdm guest session are not confined by
  the /usr/lib/lightdm/lightdm-guest-session AppArmor profile in Ubuntu
  16.10, Ubuntu 17.04, and Ubuntu Artful (current dev release). The
  processes are unconfined.

  The simple test case is to log into a guest session, launch a terminal
  with ctrl-alt-t, and run the following command:

   $ cat /proc/self/attr/current

  Expected output, as seen in Ubuntu 16.04 LTS, is:

   /usr/lib/lightdm/lightdm-guest-session (enforce)

  Running the command inside of an Ubuntu 16.10 and newer guest session
  results in:

   unconfined

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

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

[Desktop-packages] [Bug 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-05-22 Thread Will Cooke

Added to Trello: https://trello.com/c/SbWAfmKA/12-bug-1688721-package-
gconf2-common-3-2-6-3ubuntu7-failed-to-install-upgrade-subprocess-
installed-post-installation-script-returne

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

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

Status in gconf package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  New

Bug description:
  = Test Case =
  1. Download the debian package of Chrome from google
  2. Open nautilus and double-click on the file to launch ubuntu software
  3. Install the package and proceed with the installation

  = Expected result = 
  Chrome installs correctly

  = Actual result =
  The installation hangs on the following command in gconf2-common.postinst

  ucf /usr/share/gconf/default.path /etc/gconf/2/path


  = Original Report =
  I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
  This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
  The same file was successfully installed with gdebi.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  6 13:56:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1664147] Re: Chromium on trusty too outdated; not supported by gmail

2017-05-22 Thread herrtimson

I managed to add enough swap space but unfortunatley it doesn't make any
difference, the trace is the same as printed without --debug in #8

My guess is that it is very similar problem to
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184
, but I don't get the segfault or any other crash, just weird console
ouput :-)

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

Title:
  Chromium on trusty too outdated; not supported by gmail

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  As of Feb 13 2017, the chromium version on trusty is 53.x which is at
  least a couple of versions behind chrome-stable. Gmail displays this
  message, "This version of Chrome is no longer supported. Please
  upgrade to asupported browser." Core functionality in gmail works
  fine, but I'm not sure of security ramifications of running an old
  browser, particularly when google advises against it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1664147/+subscriptions

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

[Desktop-packages] [Bug 1692562] Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

no debug symbol package found for debianutils
no debug symbol package found for perl-base
libbabeltrace-ctf1 version 1.2.1 required, but 1.5.2-1build1 is available
libbabeltrace1 version 1.2.1 required, but 1.5.2-1build1 is available
libc6 version 2.17 required, but 2.24-9ubuntu2 is available
libexpat1 version 2.0.1 required, but 2.2.0-2 is available
liblzma5 version 5.1.1alpha+20110809 required, but 5.2.2-1.2 is available
libncurses5 version 6 required, but 6.0+20160625-1ubuntu1 is available
libpython3.5 version 3.5.0~b1 required, but 3.5.3-1 is available
libreadline7 version 6.0 required, but 7.0-0ubuntu2 is available
libtinfo5 version 6 required, but 6.0+20160625-1ubuntu1 is available
zlib1g version 1:1.2.0 required, but 1:1.2.11.dfsg-0ubuntu1 is available
libdw1 version 0.126 required, but 0.168-0.2 is available
libelf1 version 0.131 required, but 0.168-0.2 is available
libglib2.0-0 version 2.31.8 required, but 2.53.1-1 is available
libuuid1 version 2.16 required, but 2.29-1ubuntu2 is available
libffi6 version 3.0.4 required, but 3.2.1-6 is available
libmount1 version 2.20.1 required, but 2.29-1ubuntu2 is available
libselinux1 version 1.32 required, but 2.6-3build1 is available
libncursesw5 version 6 required, but 6.0+20160625-1ubuntu1 is available
libsqlite3-0 version 3.5.9 required, but 3.16.2-3 is available
dpkg version 1.15.4 required, but 1.18.23ubuntu7 is available
libblkid1 version 2.17.2 required, but 2.29-1ubuntu2 is available
libaudit1 version 1:2.2.1 required, but 1:2.6.6-1ubuntu2 is available
libpam0g version 0.99.7.1 required, but 1.1.8-3.2ubuntu3 is available
libsemanage1 version 2.0.3 required, but 2.6-2build1 is available
debianutils version 2.15.2 required, but 4.8.1.1 is available
no debug symbol package found for debianutils
libssl1.0.0 version 1.0.2~beta3 required, but 1.0.2g-1ubuntu13 is available
tar version 1.28-1 required, but 1.29b-1.1 is available
debconf version 0.5 required, but 1.5.60ubuntu1 is available
libsepol1 version 2.6 required, but 2.6-2 is available
libustr-1.0-1 version 1.0.4 required, but 1.0.4-6 is available
libacl1 version 2.2.51-8 required, but 2.2.52-3build1 is available
perl-base version 5.6.1-4 required, but 5.24.1-2ubuntu1 is available
no debug symbol package found for perl-base
libattr1 version 1:2.4.46-8 required, but 1:2.4.47-2build1 is available


Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!


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

** Tags removed: need-amd64-retrace

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

Title:
  nautilus crashed with SIGSEGV

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  just logged in.doing nothing.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.24.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.5-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon May 22 15:44:10 2017
  Disassembly: No registers.
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2017-04-28 (24 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170426)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  Registers: The program has no registers now.
  SegvAnalysis: Failure: invalid literal for int() with base 16: 'program'
  Signal: 11
  SourcePackage: nautilus
  Stacktrace: No stack.
  StacktraceTop:
   
  ThreadStacktrace:
   
  Title: nautilus crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo whoopsie

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

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

[Desktop-packages] [Bug 1692562]

Stacktrace: No stack.
StacktraceSource:
 
StacktraceTop:
 
ThreadStacktrace:
 


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

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

Title:
  nautilus crashed with SIGSEGV

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  just logged in.doing nothing.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.24.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.5-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon May 22 15:44:10 2017
  Disassembly: No registers.
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2017-04-28 (24 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170426)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  Registers: The program has no registers now.
  SegvAnalysis: Failure: invalid literal for int() with base 16: 'program'
  Signal: 11
  SourcePackage: nautilus
  Stacktrace: No stack.
  StacktraceTop:
   
  ThreadStacktrace:
   
  Title: nautilus crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo whoopsie

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

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

[Desktop-packages] [Bug 1692562] [NEW] nautilus crashed with SIGSEGV

2017-05-22 Thread corrado venturini

Public bug reported:

just logged in.doing nothing.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: nautilus 1:3.24.1-0ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.5-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Mon May 22 15:44:10 2017
Disassembly: No registers.
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2017-04-28 (24 days ago)
InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170426)
ProcCmdline: /usr/bin/nautilus --gapplication-service
Registers: The program has no registers now.
SegvAnalysis: Failure: invalid literal for int() with base 16: 'program'
Signal: 11
SourcePackage: nautilus
Stacktrace: No stack.
StacktraceTop:
 
ThreadStacktrace:
 
Title: nautilus crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo whoopsie

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


** Tags: amd64 apport-crash artful need-amd64-retrace

** Information type changed from Private to Public

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

Title:
  nautilus crashed with SIGSEGV

Status in nautilus package in Ubuntu:
  New

Bug description:
  just logged in.doing nothing.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.24.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.5-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon May 22 15:44:10 2017
  Disassembly: No registers.
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2017-04-28 (24 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170426)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  Registers: The program has no registers now.
  SegvAnalysis: Failure: invalid literal for int() with base 16: 'program'
  Signal: 11
  SourcePackage: nautilus
  Stacktrace: No stack.
  StacktraceTop:
   
  ThreadStacktrace:
   
  Title: nautilus crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo whoopsie

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

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

[Desktop-packages] [Bug 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-05-22 Thread Iain Lane

Robert, can you look please? Sounds to me like it's something to do with
debconf support which you've worked on lately. The testcase in the
original report was on zesty - not sure if it's still there in artful.

** Changed in: gnome-software (Ubuntu)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

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

Status in gconf package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  New

Bug description:
  = Test Case =
  1. Download the debian package of Chrome from google
  2. Open nautilus and double-click on the file to launch ubuntu software
  3. Install the package and proceed with the installation

  = Expected result = 
  Chrome installs correctly

  = Actual result =
  The installation hangs on the following command in gconf2-common.postinst

  ucf /usr/share/gconf/default.path /etc/gconf/2/path


  = Original Report =
  I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
  This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
  The same file was successfully installed with gdebi.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  6 13:56:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1689344] Re: print of __glib_assert_msg not returning a message

This bug was fixed in the package apport - 2.20.3-0ubuntu8.3

---
apport (2.20.3-0ubuntu8.3) yakkety; urgency=medium

  * Resolve autopkgtest failures in test_backend_apt_dpkg.py due to issues
with apt key ring. Thanks to Dimitri John Ledkov for the patch.
(LP: #1651623)
  * Disable report.test_add_gdb_info_abort_glib test case for now, as the
glib assertion message is broken under current Ubuntu (LP: #1689344)
  * data/general/ubuntu.py: Collect a minimal version of /proc/cpuinfo in
every report. (LP: #1673557)

 -- Brian Murray   Wed, 10 May 2017 18:10:32 -0700

** Changed in: apport (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

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

Title:
  print of __glib_assert_msg not returning a message

Status in apport package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  New
Status in apport source package in Yakkety:
  Fix Released
Status in glib2.0 source package in Yakkety:
  New
Status in apport source package in Zesty:
  Fix Released
Status in glib2.0 source package in Zesty:
  New

Bug description:
  [Impact]
  apport's test, test_add_gdb_info_abort_glib is failing due to a change 
somewhere in glib2.0, how its built, or gdb. The test shall be disabled while 
the matter is investigated.

  [Test Case]
  Run the autopkgtest and observe the failure.
  With the version of the package in proposed the test will not be run.

  [Regression Potential]
  We are just disabling a broken test so there is none.

  apport's test test_add_gdb_info_abort_glib has been failing for a bit,
  since zesty(?), now. Digging into this matter I discovered that using
  gdb to "print __glib_assert_msg" is resulting in different behavior.

  With the generated binary, it used to return the following:

  $2 = 0x7fadc0 "ERROR::2:main: assertion failed (1 < 0): (1 <
  0)"

  However, now I am seeing:

  (gdb) print __glib_assert_msg
  $1 = 1332592064
  (gdb) print (char*) __glib_assert_msg
  $2 = 0x4f6dbdc0 

  This seems to be a regression in gdb itself, I've added an apport task
  though to track the disabling of the autopkgtest which utilizes this
  command.

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

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

[Desktop-packages] [Bug 1689344] Update Released

2017-05-22 Thread Łukasz Zemczak

The verification of the Stable Release Update for apport 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 glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1689344

Title:
  print of __glib_assert_msg not returning a message

Status in apport package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  New
Status in apport source package in Yakkety:
  Fix Committed
Status in glib2.0 source package in Yakkety:
  New
Status in apport source package in Zesty:
  Fix Released
Status in glib2.0 source package in Zesty:
  New

Bug description:
  [Impact]
  apport's test, test_add_gdb_info_abort_glib is failing due to a change 
somewhere in glib2.0, how its built, or gdb. The test shall be disabled while 
the matter is investigated.

  [Test Case]
  Run the autopkgtest and observe the failure.
  With the version of the package in proposed the test will not be run.

  [Regression Potential]
  We are just disabling a broken test so there is none.

  apport's test test_add_gdb_info_abort_glib has been failing for a bit,
  since zesty(?), now. Digging into this matter I discovered that using
  gdb to "print __glib_assert_msg" is resulting in different behavior.

  With the generated binary, it used to return the following:

  $2 = 0x7fadc0 "ERROR::2:main: assertion failed (1 < 0): (1 <
  0)"

  However, now I am seeing:

  (gdb) print __glib_assert_msg
  $1 = 1332592064
  (gdb) print (char*) __glib_assert_msg
  $2 = 0x4f6dbdc0 

  This seems to be a regression in gdb itself, I've added an apport task
  though to track the disabling of the autopkgtest which utilizes this
  command.

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

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

[Desktop-packages] [Bug 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-05-22 Thread Iain Lane

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

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

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

Status in gconf package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  New

Bug description:
  = Test Case =
  1. Download the debian package of Chrome from google
  2. Open nautilus and double-click on the file to launch ubuntu software
  3. Install the package and proceed with the installation

  = Expected result = 
  Chrome installs correctly

  = Actual result =
  The installation hangs on the following command in gconf2-common.postinst

  ucf /usr/share/gconf/default.path /etc/gconf/2/path


  = Original Report =
  I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
  This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
  The same file was successfully installed with gdebi.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  6 13:56:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1689344] Re: print of __glib_assert_msg not returning a message

This bug was fixed in the package apport - 2.20.4-0ubuntu4.1

---
apport (2.20.4-0ubuntu4.1) zesty; urgency=medium

  * Disable report.test_add_gdb_info_abort_glib test case for now, as the
glib assertion message is broken under current Ubuntu (LP: #1689344)
  * Resolve autopkgtest failures in test_backend_apt_dpkg.py due to issues
with apt key ring. Thanks to Dimitri John Ledkov for the patch.
(LP: #1651623)

 -- Brian Murray   Wed, 10 May 2017 17:05:11 -0700

** Changed in: apport (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

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

Title:
  print of __glib_assert_msg not returning a message

Status in apport package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  New
Status in apport source package in Yakkety:
  Fix Committed
Status in glib2.0 source package in Yakkety:
  New
Status in apport source package in Zesty:
  Fix Released
Status in glib2.0 source package in Zesty:
  New

Bug description:
  [Impact]
  apport's test, test_add_gdb_info_abort_glib is failing due to a change 
somewhere in glib2.0, how its built, or gdb. The test shall be disabled while 
the matter is investigated.

  [Test Case]
  Run the autopkgtest and observe the failure.
  With the version of the package in proposed the test will not be run.

  [Regression Potential]
  We are just disabling a broken test so there is none.

  apport's test test_add_gdb_info_abort_glib has been failing for a bit,
  since zesty(?), now. Digging into this matter I discovered that using
  gdb to "print __glib_assert_msg" is resulting in different behavior.

  With the generated binary, it used to return the following:

  $2 = 0x7fadc0 "ERROR::2:main: assertion failed (1 < 0): (1 <
  0)"

  However, now I am seeing:

  (gdb) print __glib_assert_msg
  $1 = 1332592064
  (gdb) print (char*) __glib_assert_msg
  $2 = 0x4f6dbdc0 

  This seems to be a regression in gdb itself, I've added an apport task
  though to track the disabling of the autopkgtest which utilizes this
  command.

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

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

[Desktop-packages] [Bug 1689678] Update Released

2017-05-22 Thread Łukasz Zemczak

The verification of the Stable Release Update for gnome-calendar 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 gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1689678

Title:
  Update gnome-calendar to 3.24.2

Status in gnome-calendar package in Ubuntu:
  Fix Released
Status in gnome-calendar source package in Zesty:
  Fix Released

Bug description:
  Impact
  --
  This is a new bugfix release in the stable 3.24 series.

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

  This should fix crash bug LP: #1688414

  gnome-calendar is in the default Ubuntu, Ubuntu Budgie, and Ubuntu
  GNOME installs.

  Test Case
  -
  Install the update.

  Run the app and make sure it works without crashing.

  Regression Potential
  
  This is a smaller update than 3.24.1 and the commits sound sensible. All 
GNOME 3.24 distros will be packaging this update.

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

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

[Desktop-packages] [Bug 1688414] Re: /usr/bin/gnome-calendar:11:get_start_of_week:update_unchanged_events:gcal_week_header_set_date:gcal_week_view_set_date:update_active_date

This bug was fixed in the package gnome-calendar - 3.24.2-0ubuntu0.1

---
gnome-calendar (3.24.2-0ubuntu0.1) zesty; urgency=medium

  * New upstream release (LP: #1689678)
- Fix crash in active-date logic (LP: #1688414)

 -- Jeremy Bicha   Wed, 10 May 2017 14:48:21 -0400

** Changed in: gnome-calendar (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

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

Title:
  /usr/bin/gnome-
  
calendar:11:get_start_of_week:update_unchanged_events:gcal_week_header_set_date:gcal_week_view_set_date:update_active_date

Status in GNOME Calendar:
  Fix Released
Status in gnome-calendar package in Ubuntu:
  Fix Released
Status in gnome-calendar source package in Zesty:
  Fix Released

Bug description:
  Impact
  --
  A crash has been reported in gnome-calendar 3.24.1.

  Test Case
  -
  Check the errors site to see if this error has been reported in 3.24.2

  Regression Potential
  
  This particular fix is a one-character logic bug fix! But it's bundled with 
3.24.2 so see LP: #1689678 for more details about that.

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

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

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

[Desktop-packages] [Bug 1689678] Re: Update gnome-calendar to 3.24.2

This bug was fixed in the package gnome-calendar - 3.24.2-0ubuntu0.1

---
gnome-calendar (3.24.2-0ubuntu0.1) zesty; urgency=medium

  * New upstream release (LP: #1689678)
- Fix crash in active-date logic (LP: #1688414)

 -- Jeremy Bicha   Wed, 10 May 2017 14:48:21 -0400

** Changed in: gnome-calendar (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

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

Title:
  Update gnome-calendar to 3.24.2

Status in gnome-calendar package in Ubuntu:
  Fix Released
Status in gnome-calendar source package in Zesty:
  Fix Released

Bug description:
  Impact
  --
  This is a new bugfix release in the stable 3.24 series.

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

  This should fix crash bug LP: #1688414

  gnome-calendar is in the default Ubuntu, Ubuntu Budgie, and Ubuntu
  GNOME installs.

  Test Case
  -
  Install the update.

  Run the app and make sure it works without crashing.

  Regression Potential
  
  This is a smaller update than 3.24.1 and the commits sound sensible. All 
GNOME 3.24 distros will be packaging this update.

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

-- 
Mailing list: https://launchpad.net/~desktop-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-05-22 Thread Mohammad Anwar Shah

Well, I mean workaround by "fix" word. This workaround is the shortest,
cleanest and working think I've seen about this bug.

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

Title:
  gnome-keyring not unlocked on boot

Status in gnome-keyring 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/ubuntu/+source/gnome-keyring/+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 1688414] Update Released

2017-05-22 Thread Łukasz Zemczak

The verification of the Stable Release Update for gnome-calendar 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 gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1688414

Title:
  /usr/bin/gnome-
  
calendar:11:get_start_of_week:update_unchanged_events:gcal_week_header_set_date:gcal_week_view_set_date:update_active_date

Status in GNOME Calendar:
  Fix Released
Status in gnome-calendar package in Ubuntu:
  Fix Released
Status in gnome-calendar source package in Zesty:
  Fix Released

Bug description:
  Impact
  --
  A crash has been reported in gnome-calendar 3.24.1.

  Test Case
  -
  Check the errors site to see if this error has been reported in 3.24.2

  Regression Potential
  
  This particular fix is a one-character logic bug fix! But it's bundled with 
3.24.2 so see LP: #1689678 for more details about that.

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

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

-- 
Mailing list: https://launchpad.net/~desktop-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-05-22 Thread Mike Rushton

That is not a fix. It is a workaround. On boot, my system has gnome-
keyring-daemon running which needs to be killed and restarted without
--login in order to function. This was working a couple weeks ago. There
should be no "fixes" the user need to do to regain this functionality.

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

Title:
  gnome-keyring not unlocked on boot

Status in gnome-keyring 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/ubuntu/+source/gnome-keyring/+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 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-05-22 Thread Jean-Baptiste Lallement

setting to high given the frequency of this defect.

** Description changed:

+ = Test Case =
+ 1. Download the debian package of Chrome from google
+ 2. Open nautilus and double-click on the file to launch ubuntu software
+ 3. Install the package and proceed with the installation
+ 
+ = Expected result = 
+ Chrome installs correctly
+ 
+ = Actual result =
+ The installation hangs on the following command in gconf2-common.postinst
+ 
+ ucf /usr/share/gconf/default.path /etc/gconf/2/path
+ 
+ 
+ = Original Report =
  I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
  This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
  The same file was successfully installed with gdebi.
  
  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  6 13:56:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  = Test Case =
  1. Download the debian package of Chrome from google
  2. Open nautilus and double-click on the file to launch ubuntu software
  3. Install the package and proceed with the installation

  = Expected result = 
  Chrome installs correctly

  = Actual result =
  The installation hangs on the following command in gconf2-common.postinst

  ucf /usr/share/gconf/default.path /etc/gconf/2/path


  = Original Report =
  I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
  This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
  The same file was successfully installed with gdebi.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  6 13:56:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-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-05-22 Thread Mohammad Anwar Shah

This askUbuntu answer actually fixed the issue cleanly
https://askubuntu.com/a/911755/61218. The solution is adding a startup
item with this commandline

gnome-keyring-daemon --replace --foreground
--components=secrets,ssh,pcks11

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

Title:
  gnome-keyring not unlocked on boot

Status in gnome-keyring 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/ubuntu/+source/gnome-keyring/+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 989750] Re: repeatedly asks for encryption password when backing up, even though "remember password" is ticked

2017-05-22 Thread Kenneth Loafman

This has long been fixed, so closing it now.

Please upgrade to the current version of duplicity.  This will assure
that any bugs fixed since your release are available and my fix your
issue.

There are three options:

* Release tarball Install - https://launchpad.net/duplicity/+download
* Daily duplicity builds - 
https://launchpad.net/~duplicity-team/+archive/ubuntu/daily
* Stable duplicity builds - 
https://launchpad.net/~duplicity-team/+archive/ubuntu/ppa

** Changed in: duplicity
   Status: New => Fix Released

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

Title:
  repeatedly asks for encryption password when backing up, even though
  "remember password" is ticked

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

Bug description:
  I've set deja-dup to back up automatically, and to encrypt files. But it 
never gets far: every few seconds, it brings up a "password needed" window 
somewhere out of sight (behind other windows; but that is another 
problem/feature), even though I've told it to remember the password.
   
  So using this backup software seems entirely impractical; it will never 
finish.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: deja-dup 20.1-0ubuntu0.2
  ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22
  Uname: Linux 3.0.0-17-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Fri Apr 27 09:50:47 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/989750/+subscriptions

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

[Desktop-packages] [Bug 1553441] Re: [Asus K55DR] When VGA plugged into laptop, only one monitor working at a time

2017-05-22 Thread lazanet

** Tags removed: kernel-bug-exists-upstream-4.11
** Tags added: kernel-bug-exists-upstream-4.12-rc2

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

Title:
  [Asus K55DR] When VGA plugged into laptop, only one monitor working at
  a time

Status in xserver-xorg-video-ati package in Ubuntu:
  Triaged

Bug description:
  Upstream bug report: https://bugs.freedesktop.org/show_bug.cgi?id=99784
  Imgur post that explains problem: http://imgur.com/a/3kwiq

  When my ASUS VW193 external monitor is connected to the VGA port of my
  laptop (AMD Radeon 7470m) internal laptop monitor stops working. Using
  the Unity Control Center I'm able to set laptop monitor as primary
  which disables external monitor (and vice-versa). Tried manual switch
  to mainline Linux 4.5 kernel, same thing. Tested on 14.04, 15.10,
  16.04, 17.04 and 17.10 (develop branch) with same results.

  However, if I plug the Asus monitor into the laptop via VGA, plug my
  Vox TV into the laptop via HDMI, and set the resolution to 1280x720,
  it displays fine on both the monitor and TV.

  Also, the internal monitor and just HDMI together show properly.

  However, if I adjust to 1080i, the above working dual screen configurations 
show a graphical glitch:
  https://launchpadlibrarian.net/302517159/IMG_20170114_225834.jpg

  WORKAROUND: Use Ubuntu 14.04 with fglrx.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.5.0-040500rc6-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.20-0ubuntu3
  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: Sat Mar  5 04:32:48 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.14, 4.4.0-10-generic, x86_64: installed
   virtualbox, 5.0.14, 4.4.0-8-generic, x86_64: installed
   virtualbox, 5.0.14, 4.5.0-040500rc6-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7640G] [1002:9903] 
(prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7640G] [1043:106b]
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2016-02-18 (15 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: ASUSTeK COMPUTER INC. K55DR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.5.0-040500rc6-generic 
root=UUID=e0064410-4660-40b7-b961-76f320a921a6 ro amdgpu.powerplay=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 217
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K55DR
  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.:bvr217:bd09/07/2012:svnASUSTeKCOMPUTERINC.:pnK55DR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55DR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K55DR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Mar  5 04:27:41 2016
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.1-1ubuntu3
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1553441/+subscriptions

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

[Desktop-packages] [Bug 1219993] Re: [sound]: gnome-control-center assert failure: * Error in `gnome-control-center': double free or corruption (fasttop): 0x0000000001683200 *

2017-05-22 Thread corrado venturini

adding .crash file

** Attachment added: "_usr_bin_gnome-control-center.1000.zip"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1219993/+attachment/4881368/+files/_usr_bin_gnome-control-center.1000.zip

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

Title:
  [sound]: gnome-control-center assert failure: *** Error in `gnome-
  control-center': double free or corruption (fasttop):
  0x01683200 ***

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

Bug description:
  -

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu33
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  AssertionMessage: *** Error in `gnome-control-center': double free or 
corruption (fasttop): 0x01683200 ***
  Date: Tue Sep  3 01:39:29 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-09-02 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 
(20130902.1)
  MarkForUpload: True
  ProcCmdline: gnome-control-center sound
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f5516f776a0 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:199
   malloc_printerr (ptr=0x1683200, str=0x7f5516f77868 "double free or 
corruption (fasttop)", action=3) at malloc.c:4902
   _int_free (av=, p=0x16831f0, have_lock=0) at malloc.c:3758
   ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libsound.so
   g_cclosure_marshal_VOID__STRINGv () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: [sound]: gnome-control-center assert failure: *** Error in 
`gnome-control-center': double free or corruption (fasttop): 0x01683200 
***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center: deja-dup 27.3.1-0ubuntu1

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

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

[Desktop-packages] [Bug 1662005] Re: /etc/modprobe.d is not a file

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

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

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

Title:
  /etc/modprobe.d is not a file

Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  /var/log/syslog tells :
  ---
  cron:  (CRON) INFO (Running @reboot jobs)
  gpu-manager:  /etc/modprobe.d is not a file
  gpu-manager:  message repeated 4 times: [ /etc/modprobe.d is not a file]
  anacron:  Normal exit (0 jobs run)
  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-drivers-common 1:0.4.17.2
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Feb  5 20:39:21 2017
  InstallationDate: Installed on 2017-02-01 (3 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: ubuntu-drivers-common
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1662005/+subscriptions

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

[Desktop-packages] [Bug 1219993] Re: [sound]: gnome-control-center assert failure: * Error in `gnome-control-center': double free or corruption (fasttop): 0x0000000001683200 *

2017-05-22 Thread corrado venturini

I have this problem in Ubuntu Gnome 17.10

corrado@corrado-HP-aGnome:~$ gnome-control-center region

** (gnome-control-center:2370): WARNING **: Ignoring launcher gufw
(missing desktop file)

** (gnome-control-center:2370): WARNING **: Ignoring launcher landscape-
client-settings (missing desktop file)

** (gnome-control-center:2370): WARNING **: Ignoring launcher language-
selector (missing desktop file)

** (gnome-control-center:2370): WARNING **: Ignoring launcher system-
config-printer (missing desktop file)

** (gnome-control-center:2370): WARNING **: Ignoring launcher ubuntuone-
installer (missing desktop file)

(gnome-control-center:2370): common-cc-panel-WARNING **: Language en_US.UTF-8 
not installed, trying to install it
*** Error in `gnome-control-center': double free or corruption (fasttop): 
0x563121443800 ***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x7908b)[0x7ff61c9f208b]
/lib/x86_64-linux-gnu/libc.so.6(+0x826fa)[0x7ff61c9fb6fa]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x4c)[0x7ff61c9ff12c]
gnome-control-center(+0x9bb83)[0x56311f5ddb83]
gnome-control-center(+0x9bd17)[0x56311f5ddd17]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x88e53)[0x7ff61d54de53]
..
7ff60ad38000-7ff60ad39000 rw-p 0005e000 08:07 1454385
/usr/lib/x86_64-linux-gnu/libwebp.so.6.0.2
7ff60ad39000-7ff60ad3a000 rw-p  00:00 0 
7ff60ad3a000-7ff60ada3000 r-xp  08:07 1453786
/usr/lib/x86_64-linux-gnu/libjpeg.so.8.1.2
7ff60ada3000-7ff60afa2000 ---p 00069000 08:07 1453786
/usr/lib/x86_64-linux-gnu/libjpeg.so.8.1.2
7ff60afa2000-7ff60afa3000 r--p 00068000 08:07 1453786
/usr/lib/x86_64-linux-gnu/libjpeg.so.8.1.2Aborted (core dumped)
corrado@corrado-HP-aGnome:~$ 
 
I can reproduce problem; let me know if I should add other info.

** Attachment added: "Region-and-language.zip"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1219993/+attachment/4881366/+files/Region-and-language.zip

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

Title:
  [sound]: gnome-control-center assert failure: *** Error in `gnome-
  control-center': double free or corruption (fasttop):
  0x01683200 ***

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

Bug description:
  -

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu33
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  AssertionMessage: *** Error in `gnome-control-center': double free or 
corruption (fasttop): 0x01683200 ***
  Date: Tue Sep  3 01:39:29 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-09-02 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 
(20130902.1)
  MarkForUpload: True
  ProcCmdline: gnome-control-center sound
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f5516f776a0 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:199
   malloc_printerr (ptr=0x1683200, str=0x7f5516f77868 "double free or 
corruption (fasttop)", action=3) at malloc.c:4902
   _int_free (av=, p=0x16831f0, have_lock=0) at malloc.c:3758
   ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libsound.so
   g_cclosure_marshal_VOID__STRINGv () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: [sound]: gnome-control-center assert failure: *** Error in 
`gnome-control-center': double free or corruption (fasttop): 0x01683200 
***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center: deja-dup 27.3.1-0ubuntu1

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

-- 
Mailing list: https://launchpad.net/~desktop-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-05-22 Thread Marc Pignat

vinagre is also affected, running gnome-keyring-daemon restores the
normal behavior.

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

Title:
  gnome-keyring not unlocked on boot

Status in gnome-keyring 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/ubuntu/+source/gnome-keyring/+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 1692496] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

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

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1688721
   package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 128

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

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

Status in gconf package in Ubuntu:
  New

Bug description:
  after cancel download

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Mon May 22 12:51:01 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-18 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1662227] Re: Error with command "apt-get update" when using versioned "Provides:" (apt is too old to support that case)

2017-05-22 Thread Amr Ibrahim

This is fixed in the PPA now.

** Changed in: libreoffice (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Error with command "apt-get update" when using versioned "Provides:"
  (apt is too old to support that case)

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  I'm getting this error every time I do "apt-get update"

  Ign http://ni.archive.ubuntu.com trusty/multiverse Translation-en_US  
 
  Ign http://ni.archive.ubuntu.com trusty/restricted Translation-en_US  
 
  Ign http://ni.archive.ubuntu.com trusty/universe Translation-en_US
 
  Reading package lists... Done 
 
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  ...
  ...
  ...
  ...
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: You may want to run apt-get update to correct these problems

  This error started to show after I upgraded LibreOffice form 5.2 to
  5.3 with the LibreOffice PPA: ppa:libreoffice/ppa.

  The thing is that everything is working fine. I can update/upgrade the
  system, I can install packages, delete packages, etc. The problem is
  just with the error.

  I tried: "apt-get autoclean". "apt-get clean", "apt-get autoremove",
  apt-get install -f", and a lot of other things and nothing removes
  that ugly error.

  If I remove all PPA packages and remove the PPA itself the error goes
  away.

  This has been reported in askubuntu.com:

  
  
http://askubuntu.com/questions/880447/ubuntu-14-04-error-with-apt-get-update-w-ignoring-provides-line-with-depcom

  http://askubuntu.com/questions/879497/apt-spewing-warnings-after-
  libreoffice-update

  
  Help please. Thank you.

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

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

[Desktop-packages] [Bug 1682819] Re: Pressing Install in Software Center does nothing when installing deb file

2017-05-22 Thread Amr Ibrahim

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

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

** This bug has been marked a duplicate of bug 1672424
   Cannot install Debian files outside of the repositories

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

Title:
  Pressing Install in Software Center does nothing when installing deb
  file

Status in gnome-software package in Ubuntu:
  Fix Released

Bug description:
  Pressing on Install button does nothing

  Steps to recreate:

  - Download a deb file (e.g. 
https://steamcdn-a.akamaihd.net/client/installer/steam.deb or 
https://go.microsoft.com/fwlink/?LinkID=760868)
  - Open it (standard program to open a deb file is Ubuntu Software)
  - Press on Install
  - Nothing happens

  Ubuntu 17.04
  Ubuntu Software 3.22.7

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-software 3.22.7-0ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Fri Apr 14 14:55:57 2017
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2017-04-13 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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/1682819/+subscriptions

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

[Desktop-packages] [Bug 1682936] Re: Installing software via the Software Center never asks the password nor an ¨sucessfully installed¨ message

2017-05-22 Thread Amr Ibrahim

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

** This bug is no longer a duplicate of bug 1682819
   Pressing Install in Software Center does nothing when installing deb file
** This bug has been marked a duplicate of bug 1672424
   Cannot install Debian files outside of the repositories

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

Title:
  Installing software via the Software Center never asks the password
  nor an ¨sucessfully installed¨ message

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I installed some .deb packages and I was never asked about the
  password, it do not show the progress or if it sucesfully installed
  the software. You will find it installed some minutes later

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ubuntu-release-upgrader-core 1:17.04.7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity:Unity7
  Date: Fri Apr 14 18:13:37 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-04-13 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  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/1682936/+subscriptions

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

[Desktop-packages] [Bug 1692496] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-05-22 Thread ali

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

Public bug reported:

after cancel download

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
Date: Mon May 22 12:51:01 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-05-18 (3 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

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

Status in gconf package in Ubuntu:
  New

Bug description:
  after cancel download

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Mon May 22 12:51:01 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-18 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-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-05-22 Thread Sandeep

About Vulkan package:

Vulkan loader (libvulkan) has moved to newer version and that is needed
to make use of all the recently proposed vulkan extensions in the
application.

The main application that doesn't work currently is with Vulkan CTS:
https://github.com/KhronosGroup/VK-GL-CTS

Vulkan CTS passing is required for a device to be called as Vulkan
compatible.

We support only LTS releases on our devices so need latest version on
16.04. Can you please upgrade the libvulkan.so version to 1.0.42 for
Xenial?

This version is already available for latest ubuntu version (17.04).

Thanks.

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

Title:
  Backport packages for 16.04.3 HWE stack

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

Bug description:
  [Impact]

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

  Revert changes to use debhelper10.

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

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

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

  [Test case]

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

  [Regression potential]

  zesty hasn't blown up

  [Other information]

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

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

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

[Desktop-packages] [Bug 997331] Re: Some alsa applications play bad sound

2017-05-22 Thread Valentin Leclere

Same bug here on a 16.04, agw3's workaround doesn't fix the issue for me.
It occurs when my browser (firefox 53.0.2 64b) display a google research with 
google translate content.

The way I fix it is:
pulseaudio -k && sudo alsa force-reload
It's a bit annoying, I would like to fix it permanently.

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

Title:
  Some alsa applications play bad sound

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Some applications using ALSA plays bad sound. One is WINE
  applications. Winecfg test sound is distorted (sounds awful). Spotify
  running WINE plays songs way too fast. A flash based program play
  distorted sound. The common thing for all of them is that under
  Applications in Sound settings it says alsa-plugin and it flashes very
  rapidly between "No application is currently playing" and alsa-plugin.
  It almost looks like flickering. I've testet a normal wave file using
  aplay and that was okey, no problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  oeriksen   3299 F pulseaudio
   /dev/snd/controlC0:  oeriksen   3299 F pulseaudio
   /dev/snd/controlC1:  oeriksen   3299 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xfa40 irq 60'
 Mixer name : 'Realtek ALC892'
 Components : 'HDA:10ec0892,10438410,00100302'
 Controls  : 41
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'Socialize'/'Creative Labs VF0640 Live! Cam Socialize at 
usb-:00:1d.0-1.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB041e:4083'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 48
 Mono: Capture 45 [94%] [18.00dB] [on]
  Card2.Amixer.info:
   Card hw:2 'NVidia'/'HDA NVidia at 0xfa08 irq 17'
 Mixer name : 'Nvidia GPU 16 HDMI/DP'
 Components : 'HDA:10de0016,10de0101,00100100'
 Controls  : 24
 Simple ctrls  : 4
  Date: Wed May  9 22:41:04 2012
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [System Product Name, Realtek ALC892, Green Line Out, Rear] Playback 
problem
  UpgradeStatus: Upgraded to precise on 2012-03-02 (68 days ago)
  dmi.bios.date: 02/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8P67 REV 3.1
  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.:bvr2302:bd02/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8P67REV3.1: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/pulseaudio/+bug/997331/+subscriptions

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

[Desktop-packages] [Bug 1339607] Re: "Unencrypted private keys are insecure" message is vague and unhelpful

2017-05-22 Thread Mircea

Kitsab, you saved me.

I can confirm that the issue has disappeared for me as well after
disabling home-folder encryption.

Thanks

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

Title:
  "Unencrypted private keys are insecure" message is vague and unhelpful

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

Bug description:
  Steps to reproduce:
  1. Set up a wireless connection with WPA security and an unencrypted private 
key.
  2. Make sure Network Manager will connect as soon as the wireless network is 
available.
  2. Reboot the computer.

  What happens:
  Network manager will connect to the network during boot. If it completes 
before login, you are presented with the following message:

  > Unencrypted private keys are insecure
  > The selected private key does not appear to be protected by a password.  
This could allow your security credentials to be compromised.  Please select a 
password-protected private key.
  > 
  > (You can password-protect your private key with openssl)

  This message is really uninformative and unhelpful for many reasons:
  * It does not tell me which program/key is the problem. Initially I though 
that the problem had to do with one of my SSH keys. I had to grep the message 
in /usr/bin in order to understand who was showing it.
  * It does not tell why exactly unencrypted keys are insecure. In fact, 
someone might say they aren't.
  * It does not tell how to encrypt them. "You can password-protect your 
private key with openssl" does not mean anything, even to a person who knows 
what OpenSSL is.

  TL;DR: you are warned about a problem which does not exist, without
  being told what it is and how to solve it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager-gnome 0.9.8.8-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.13.0-31.55-generic 3.13.11.4
  Uname: Linux 3.13.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jul  9 10:51:28 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-10-23 (258 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  IpRoute:
   default via 10.169.169.254 dev wlan0  proto static 
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
   10.169.169.0/24 dev wlan0  proto kernel  scope link  src 10.169.169.100  
metric 9 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager-applet
  UpgradeStatus: Upgraded to trusty on 2014-03-25 (105 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

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

[Desktop-packages] [Bug 1292398] Re: Second screen position isn't saved from one session to another

2017-05-22 Thread Davias

Hi guys, same problem after upgrading from 14.04 LTS to 16.04.2
LTS...Gnome fallback of course (it is called fallback becouse Unity is
supposed to be an improvement?) I had this problem in 14.04, with AMD
Catalyst Control Center not remembering monitors position. Solved using
system/monitors to set them and it was ok. After the upgrade, Catalyst
is gone for free Gallium...but I get the bug. Strange enough at login
monitors are correctly positioned...after login they get messed up. Same
system since 7.04, always worked with 3 monitors...I know there is a
script to work back the monitor config file...but is such an inelegant
solutions...c'mon this bug is old years!

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

Title:
  Second screen position isn't saved from one session to another

Status in elementary OS:
  Fix Released
Status in GNOME Settings Daemon:
  Unknown
Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in Ubuntu GNOME trusty series:
  Confirmed
Status in Ubuntu GNOME xenial series:
  Confirmed
Status in Ubuntu GNOME Flashback:
  Confirmed
Status in Unity:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  (Noticed on Ubuntu 14.04 beta 1 GNOME)
  At work I have a second screen, which I prefer to virtually put on the left 
side of my laptop screen.
  Using gnome-control-center I can change the position of the second without 
problem.
  But when I disconnect the second screen (to work on another place) and then 
connect it again
  OR if I just power off the laptop and turn it on again,
  the second screen position is set back to the default right position.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu53
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 14 08:50:00 2014
  InstallationDate: Installed on 2014-03-01 (12 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2

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

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

[Desktop-packages] [Bug 1692474] Re: Sound settings don't remember my preferred audio output device

** Package changed: gnome-control-center (Ubuntu) => unity-control-
center (Ubuntu)

** Also affects: gnome-control-center (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/1692474

Title:
  Sound settings don't remember my preferred audio output device

Status in gnome-control-center package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in unity-control-center package in Ubuntu:
  New

Bug description:
  Sound settings don't remember my preferred audio output device.

  Every time I (manage to) connect a bluetooth audio device, the default
  output remains the built-in PC speaker. Same when I connect USB audio
  devices... Ubuntu sticks to the built-in speakers until manually set
  otherwise.

  This is a bug rather than opinion because there are at least three ways that 
Ubuntu could be better prioritizing audio devices:
1. Prefer what the user manually selected last; or
2. Prefer what the user dragged to the top of the list (a missing feature, 
but nice idea); or
3. Prefer what audio device appeared in the list most recently.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-control-center (not installed)
  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
  Date: Mon May 22 17:23:59 2017
  InstallationDate: Installed on 2017-05-19 (2 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1692477] [NEW] Thunderbird 52.1.1 no longer able to see remotely mounted folders

2017-05-22 Thread juanpablo83

Public bug reported:

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


- What is happening

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

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


- What should happen

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

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


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


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

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

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

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

Status in thunderbird package in Ubuntu:
  New

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

  
  - What is happening

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

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

  
  - What should happen

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

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

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

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

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

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

[Desktop-packages] [Bug 1685035] Re: GDM login doesn't scale on Hi-DPI display

2017-05-22 Thread Sebastian 'polrus' Turzanski

installed v3.24.2 in 17.04 proposed today and it works fine, Thank you
:)


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

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

Title:
  GDM login doesn't scale on Hi-DPI display

Status in GNOME Settings Daemon:
  Fix Released
Status in Ubuntu GNOME:
  Triaged
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Zesty:
  Fix Committed

Bug description:
  Impact
  --
  GDM's login screen was being start with no gnome-settings-daemons plugins. In 
particular, this broke Hi-DPI support in the login screen

  Test Case
  -
  - Install the update on a computer running Ubuntu GNOME 17.04 with a Hi-DPI 
display (ideally one that worked well with Ubuntu GNOME 16.10).
  - Restart your computer.
  - The login screen should automatically show at the right scale.

  Regression Potential
  
  See the other 3.24.2 bugs but this commit is a simple typo fix.

  Original Bug Report
  ---
  Ubuntu gnome 17.04, gnome 3.24. On high resolution display, 3200x1800, login 
screen is too tiny to read. GDM login screen doesn't reflect changes to 
org.gnome.desktop.interface scaling-factor or text-scaling-factor.

  Eg:
  xhost +SI:localuser:gdm
  sudo su gdm -s /bin/bash
  gsettings set org.gnome.desktop.interface scaling-factor 2
  gsettings set org.gnome.desktop.interface text-scaling-factor 2.0

  no effect.

  Creating a gdm user under /etc/dconf and running dconf update has no
  effect either. Scaling-factor seems to scale the mouse cursor, but
  nothing else.

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

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

[Desktop-packages] [Bug 1692474] [NEW] Sound settings don't remember my preferred audio output device

Public bug reported:

Sound settings don't remember my preferred audio output device.

Every time I (manage to) connect a bluetooth audio device, the default
output remains the built-in PC speaker. Same when I connect USB audio
devices... Ubuntu sticks to the built-in speakers until manually set
otherwise.

This is a bug rather than opinion because there are at least three ways that 
Ubuntu could be better prioritizing audio devices:
  1. Prefer what the user manually selected last; or
  2. Prefer what the user dragged to the top of the list (a missing feature, 
but nice idea); or
  3. Prefer what audio device appeared in the list most recently.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-control-center (not installed)
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
Date: Mon May 22 17:23:59 2017
InstallationDate: Installed on 2017-05-19 (2 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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

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


** Tags: amd64 apport-bug xenial

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

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

Title:
  Sound settings don't remember my preferred audio output device

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

Bug description:
  Sound settings don't remember my preferred audio output device.

  Every time I (manage to) connect a bluetooth audio device, the default
  output remains the built-in PC speaker. Same when I connect USB audio
  devices... Ubuntu sticks to the built-in speakers until manually set
  otherwise.

  This is a bug rather than opinion because there are at least three ways that 
Ubuntu could be better prioritizing audio devices:
1. Prefer what the user manually selected last; or
2. Prefer what the user dragged to the top of the list (a missing feature, 
but nice idea); or
3. Prefer what audio device appeared in the list most recently.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-control-center (not installed)
  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
  Date: Mon May 22 17:23:59 2017
  InstallationDate: Installed on 2017-05-19 (2 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1691479] Re: can't send message

2017-05-22 Thread gerpder

I am seeing this problem on my 3 installs of Ubuntu 16.04.2.It was
introduced with upgrade to Thunderbird 52.1.1.   It was not present in
Thunderbird 45.8.0 or older

What I am seeing is I write a emails but do not send straight away,
after some time if I try to send the send dialogue stays on "sending"
and email never goes.  If I cancel this I am seeing that the "To" field
is grayed out and I can no more edit it.   I must quit thunderbird to
fix.

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

Title:
  can't send message

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  After last thunderbird update, I am not able to send a message from 
Thunderbird.
  I press the send button and nothing happens (I haven't noticed any debug log).
  The same happens with the ctrl+enter combination.
  I have tried to run Thunderbird in the safe mode (all add-ons disabled) and 
the issue is reproducible.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: thunderbird 1:52.1.1+build1-0ubuntu0.17.04.1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  NonfreeKernelModules: openafs
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  afiergol   5023 F pulseaudio
   /dev/snd/controlC1:  afiergol   5023 F pulseaudio
  BuildID: 20170510140118
  Channel: Unavailable
  CurrentDesktop: Unity:Unity7
  Date: Wed May 17 11:38:11 2017
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   Enigmail - {847b3a00-7ab1-11d4-8f02-006008948af5}
   Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Polski Language Pack - langpack...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2015-04-02 (775 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PrefSources:
   prefs.js
   
[Profile]/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/enigmail.js
   [Profile]/extensions/keefox@chris.tomlinson/defaults/preferences/prefs.js
   
[Profile]/extensions/{a62ef8ec-5fdc-40c2-873c-223b8a6925cc}/defaults/preferences/preferences.js
   
[Profile]/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
  Profiles: Profile0 (Default) - LastVersion=52.1.1/20170510140118 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to zesty on 2017-04-18 (28 days ago)
  dmi.bios.date: 04/25/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M70 Ver. 01.15
  dmi.board.name: 2253
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 03.12
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM70Ver.01.15:bd04/25/2016:svnHewlett-Packard:pnHPZBook15G2:pvrA3009CD10002:rvnHewlett-Packard:rn2253:rvrKBCVersion03.12:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ZBook 15 G2
  dmi.product.version: A3009CD10002
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1691479] Re: can't send message

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

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

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

Title:
  can't send message

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  After last thunderbird update, I am not able to send a message from 
Thunderbird.
  I press the send button and nothing happens (I haven't noticed any debug log).
  The same happens with the ctrl+enter combination.
  I have tried to run Thunderbird in the safe mode (all add-ons disabled) and 
the issue is reproducible.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: thunderbird 1:52.1.1+build1-0ubuntu0.17.04.1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  NonfreeKernelModules: openafs
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  afiergol   5023 F pulseaudio
   /dev/snd/controlC1:  afiergol   5023 F pulseaudio
  BuildID: 20170510140118
  Channel: Unavailable
  CurrentDesktop: Unity:Unity7
  Date: Wed May 17 11:38:11 2017
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   Enigmail - {847b3a00-7ab1-11d4-8f02-006008948af5}
   Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Polski Language Pack - langpack...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2015-04-02 (775 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PrefSources:
   prefs.js
   
[Profile]/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/enigmail.js
   [Profile]/extensions/keefox@chris.tomlinson/defaults/preferences/prefs.js
   
[Profile]/extensions/{a62ef8ec-5fdc-40c2-873c-223b8a6925cc}/defaults/preferences/preferences.js
   
[Profile]/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
  Profiles: Profile0 (Default) - LastVersion=52.1.1/20170510140118 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to zesty on 2017-04-18 (28 days ago)
  dmi.bios.date: 04/25/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M70 Ver. 01.15
  dmi.board.name: 2253
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 03.12
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM70Ver.01.15:bd04/25/2016:svnHewlett-Packard:pnHPZBook15G2:pvrA3009CD10002:rvnHewlett-Packard:rn2253:rvrKBCVersion03.12:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ZBook 15 G2
  dmi.product.version: A3009CD10002
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first

Confirmed on xenial, exactly how hife describes it.

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

Title:
  [xenial] Bluetooth device doesn't play any sound in A2DP mode unless
  set to HSP/HFP first

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth device doesn't play any sound in A2DP mode unless set to
  HSP/HFP first

  ---

  I have a Sennheiser MM 450-X headset.

  In 15.10, connection & playback was straightforward.

  In 16.04, the headset connects, and shows up as default playback
  device on `pavucontrol`, but there is no sound.

  A functional workaround is to, after having connected it, to go the
  `Configuration` tab, and in the `Profile` dropdown, to choose `...
  HSP/HFP`, which will make them play as expected (but in low quality),
  then switch to `... A2DP Sink` (they will play in high quality).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  myuser2936 F pulseaudio
   /dev/snd/controlC2:  myuser2936 F pulseaudio
   /dev/snd/controlC0:  myuser2936 F pulseaudio
  Date: Mon May 16 14:18:58 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-03-11 (66 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88XN-WIFI
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/22/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1692454] [NEW] [ENS1371 - Ensoniq AudioPCI, playback] No sound at all

2017-05-22 Thread hari

Public bug reported:

no audio at all

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: pulseaudio 1:10.0-1ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  hariharan   1985 F pulseaudio
CurrentDesktop: Unity:Unity7
Date: Mon May 22 14:08:44 2017
InstallationDate: Installed on 2017-05-17 (4 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:AudioPCI successful
Symptom_Card: ES1371/ES1373 / Creative Labs CT2518 (Audio PCI 64V/128/5200 / 
Creative CT4810/CT5803/CT5806 [Sound Blaster PCI]) - Ensoniq AudioPCI
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  hariharan   1985 F pulseaudio
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: No sound at all
Title: [ENS1371 - Ensoniq AudioPCI, playback] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/02/2015
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

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


** Tags: amd64 apport-bug zesty

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

Title:
  [ENS1371 - Ensoniq AudioPCI, playback] No sound at all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  no audio at all

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hariharan   1985 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon May 22 14:08:44 2017
  InstallationDate: Installed on 2017-05-17 (4 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:AudioPCI 
successful
  Symptom_Card: ES1371/ES1373 / Creative Labs CT2518 (Audio PCI 64V/128/5200 / 
Creative CT4810/CT5803/CT5806 [Sound Blaster PCI]) - Ensoniq AudioPCI
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hariharan   1985 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [ENS1371 - Ensoniq AudioPCI, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Desktop-packages] [Bug 1362313] Re: a2dp bluetooth music playback broken after bluetooth device reconnect

** Tags added: a2dp

** Summary changed:

- a2dp bluetooth music playback broken after bluetooth device reconnect
+ PulseAudio can't find Bluetooth device after reconnecting

** Also affects: pulseaudio (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/1362313

Title:
  PulseAudio can't find Bluetooth device after reconnecting

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  What happens?
  1. connct a2dp device
  2. start playback
  3. reconnect a2dp device from remote
  4. ubuntu reports device is connected
  5. a2dp device does not show up in pulseaudio nor does music playback work 
(via a2dp device). sometimes there are "timeout" error messages in kde.
  6. try to reconnect from ubuntu, restart bluetooth daemon, restart pulseaudio 
daemon. it all does not help.
  7. what does help is restarting 1. dbus 2. bluetooth and 3. pulseaudio then 
connect the device (if not already auto-connected)

  After step 3, there is the following error message in syslog (no other
  errors in syslog or dmesg):

  pulseaudio[7812]: [bluetooth] bluetooth-util.c: Failed to release
  transport /org/bluez/7791/hci0/dev_C8_84_47_10_24_A2/fd2: Method
  "Release" with signature "s" on interface "org.bluez.MediaTransport"
  doesn't exist

  What I expected to happen?
  After the device reconnect, the music playback switches playback back to the 
bluetooth device.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: bluetooth 4.101-0ubuntu13
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  Date: Wed Aug 27 21:41:34 2014
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=de_DE:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic 
root=/dev/mapper/linux64-root64 ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  SourcePackage: bluez
  UpgradeStatus: Upgraded to trusty on 2014-06-18 (70 days ago)
  dmi.bios.date: 12/06/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.00
  dmi.board.name: B85 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.00:bd12/06/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB85Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:02:72:CC:E6:D5  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:100536 acl:18 sco:0 events:14179 errors:0
TX bytes:24059553 acl:28186 sco:0 commands:77 errors:0
  syslog: Aug 27 20:46:20 charlie bluetoothd[1538]: 
/org/bluez/1538/hci0/dev_C8_84_47_10_24_A2/fd0: fd(25) ready

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

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

[Desktop-packages] [Bug 1438510] Re: [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode)

** Summary changed:

- [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 
16.10 yakkety
+ [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode)

** 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/1438510

Title:
  [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP
  mode)

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS and 16.10.

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

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

[Desktop-packages] [Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first

** 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/1582213

Title:
  [xenial] Bluetooth device doesn't play any sound in A2DP mode unless
  set to HSP/HFP first

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth device doesn't play any sound in A2DP mode unless set to
  HSP/HFP first

  ---

  I have a Sennheiser MM 450-X headset.

  In 15.10, connection & playback was straightforward.

  In 16.04, the headset connects, and shows up as default playback
  device on `pavucontrol`, but there is no sound.

  A functional workaround is to, after having connected it, to go the
  `Configuration` tab, and in the `Profile` dropdown, to choose `...
  HSP/HFP`, which will make them play as expected (but in low quality),
  then switch to `... A2DP Sink` (they will play in high quality).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  myuser2936 F pulseaudio
   /dev/snd/controlC2:  myuser2936 F pulseaudio
   /dev/snd/controlC0:  myuser2936 F pulseaudio
  Date: Mon May 16 14:18:58 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-03-11 (66 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88XN-WIFI
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/22/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1658498] Re: Date format in gnome-calendar does not match system locale

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

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

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

Title:
  Date format in gnome-calendar does not match system locale

Status in gnome-calendar package in Ubuntu:
  Confirmed

Bug description:
  On a clean install of UbuntuGNOME 16.04.1 LTS x64, after the system
  locale has been set as en-GB during the installation, the date format
  in the GNOME calendar is displayed as "January 22 2017" instead of the
  correct date format for the locale, "22 January 2017". The correct
  date format is displayed when running the "date" command from the
  terminal, and the correct date format is displayed on the GNOME lock
  screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-calendar 3.20.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Jan 22 16:58:42 2017
  ExecutablePath: /usr/bin/gnome-calendar
  InstallationDate: Installed on 2017-01-21 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety