[Desktop-packages] [Bug 1694595] [NEW] Bug with graphic carts

2017-05-30 Thread Charmasson
Public bug reported:

no driver with graphic carts

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 i686
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.6
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: Wed May 31 07:15:49 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Radeon HD 5450 [1043:0386]
InstallationDate: Installed on 2017-05-21 (9 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
MachineType: System manufacturer System Product Name
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=58213a0b-ae70-4cbf-92f9-7f61e83b1926 ro nomodeset nopat 
plymouth:debug vesafb.invalid=1 drm.debug=0xe
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/11/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0602
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5KPL-AM SE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0602:bd09/11/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-AMSE:rvrX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.libdrm2: libdrm2 2.4.80-0~x~padoka0
version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.1.1-1~x~padoka0
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.1.1-1~x~padoka0
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed May 31 06:51:42 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputLITEON Technology USB Keyboard KEYBOARD, id 8
 inputLITEON Technology USB Keyboard KEYBOARD, id 9
 inputLogitech Optical USB Mouse MOUSE, id 10
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: apport-bug compiz-0.9 i386 third-party-packages ubuntu 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/1694595

Title:
  Bug with graphic carts

Status in xorg package in Ubuntu:
  New

Bug description:
  no driver with graphic carts

  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 i686
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  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: Wed May 31 07:15:49 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Radeon HD 5450 [1043:0386]
  InstallationDate: Installed on 2017-05-21 (9 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=58213a0b-ae70-4cbf-92f9-7f61e83b1926 ro nomodeset nopat 
plymouth:debug vesafb.invalid=1 drm.debug=0xe
  Renderer: 

[Desktop-packages] [Bug 1683080] Re: package libcuda1-352 361.45.11-0ubuntu0.16.04.1 failed to install/upgrade: there is no script in the new version of the package - giving up

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

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

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

Title:
  package libcuda1-352 361.45.11-0ubuntu0.16.04.1 failed to
  install/upgrade: there is no script in the new version of the package
  - giving up

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

Bug description:
  failed during 'sudo aptitude dist-upgrade'

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libcuda1-352 361.45.11-0ubuntu0.16.04.1
  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
  Date: Sat Apr 15 15:37:45 2017
  ErrorMessage: there is no script in the new version of the package - giving up
  InstallationDate: Installed on 2015-03-23 (754 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: nvidia-graphics-drivers-361
  Title: package libcuda1-352 361.45.11-0ubuntu0.16.04.1 failed to 
install/upgrade: there is no script in the new version of the package - giving 
up
  UpgradeStatus: Upgraded to zesty on 2017-04-15 (0 days ago)

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

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


[Desktop-packages] [Bug 1694587] [NEW] package libsamplerate0:i386 0.1.8-8 failed to install/upgrade: Paket libsamplerate0:i386 ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (mome

2017-05-30 Thread Olaf Jensen
Public bug reported:

i try to install Gimp via Terminal. Doesnt work

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libsamplerate0:i386 0.1.8-8
ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-53-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Wed May 31 06:12:20 2017
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu7
 libgcc1 1:6.0.1-0ubuntu1
 multiarch-support 2.23-0ubuntu7
ErrorMessage: Paket libsamplerate0:i386 ist nicht bereit zur Konfiguration  
kann nicht konfiguriert werden (momentaner Status »half-installed«)
InstallationDate: Installed on 2017-05-25 (5 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: libsamplerate
Title: package libsamplerate0:i386 0.1.8-8 failed to install/upgrade: Paket 
libsamplerate0:i386 ist nicht bereit zur Konfiguration  kann nicht konfiguriert 
werden (momentaner Status »half-installed«)
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package libsamplerate0:i386 0.1.8-8 failed to install/upgrade: Paket
  libsamplerate0:i386 ist nicht bereit zur Konfiguration  kann nicht
  konfiguriert werden (momentaner Status »half-installed«)

Status in libsamplerate package in Ubuntu:
  New

Bug description:
  i try to install Gimp via Terminal. Doesnt work

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libsamplerate0:i386 0.1.8-8
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Wed May 31 06:12:20 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu7
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu7
  ErrorMessage: Paket libsamplerate0:i386 ist nicht bereit zur Konfiguration  
kann nicht konfiguriert werden (momentaner Status »half-installed«)
  InstallationDate: Installed on 2017-05-25 (5 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: libsamplerate
  Title: package libsamplerate0:i386 0.1.8-8 failed to install/upgrade: Paket 
libsamplerate0:i386 ist nicht bereit zur Konfiguration  kann nicht konfiguriert 
werden (momentaner Status »half-installed«)
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1694580] [NEW] While reading the news, and then sharing a post to FB, the comment window that opens is not formated correctly and does not show the post comment button. Some re

2017-05-30 Thread Bill Owsley
Public bug reported:

So I just shift over to chrome, no prob !  It works fine.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 53.0.3+build1-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   bill   6395 F...m pulseaudio
 /dev/snd/controlC0:  bill   6395 F pulseaudio
 /dev/snd/controlC1:  bill   6395 F pulseaudio
BuildID: 20170524180630
Channel: Unavailable
CurrentDesktop: Unity
Date: Tue May 30 23:00:50 2017
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2017-05-13 (18 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IpRoute:
 default via 192.168.1.1 dev wlo2  proto static  metric 600 
 169.254.0.0/16 dev wlo2  scope link  metric 1000 
 192.168.1.0/24 dev wlo2  proto kernel  scope link  src 192.168.1.10  metric 600
Locales: extensions.sqlite corrupt or missing
PrefSources: prefs.js
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=53.0.3/20170524180630 (In use)
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/28/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.26
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1444
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 69.37
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.26:bd01/28/2011:svnHewlett-Packard:pnHPG62NotebookPC:pvr0592110003242710010020100:rvnHewlett-Packard:rn1444:rvr69.37:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: HP G62 Notebook PC
dmi.product.version: 0592110003242710010020100
dmi.sys.vendor: Hewlett-Packard

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

Title:
  While reading the news, and then sharing a post to FB, the comment
  window that opens is not formated correctly and does not show the post
  comment button.  Some re-sizing, or full screen attempts, sometimes
  gets it to show, but then it is flickers.  It seems to take the click
  on it and sometimes settles down to the expected steady state.  But
  another click says something about a missing URL.

Status in firefox package in Ubuntu:
  New

Bug description:
  So I just shift over to chrome, no prob !  It works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 53.0.3+build1-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   bill   6395 F...m pulseaudio
   /dev/snd/controlC0:  bill   6395 F pulseaudio
   /dev/snd/controlC1:  bill   6395 F pulseaudio
  BuildID: 20170524180630
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Tue May 30 23:00:50 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2017-05-13 (18 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.1 dev wlo2  proto static  metric 600 
   169.254.0.0/16 dev wlo2  scope link  metric 1000 
   192.168.1.0/24 dev wlo2  proto kernel  scope link  src 192.168.1.10  metric 
600
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=53.0.3/20170524180630 (In use)
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2011

[Desktop-packages] [Bug 1690759] Re: dns leak

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

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

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

Title:
  dns leak

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

Bug description:
  Using the network manager to set my OpenVPN I have a DNS leak after
  connecting to my secured network which also provides Internet
  connection.

  I think solution is here: http://www.ubuntubuzz.com/2015/09/how-to-
  fix-openvpn-dns-leak-in-linux.html

  However, I didn't find in the network manager windows any place to set
  those scripts.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager-openvpn-gnome 1.2.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon May 15 10:32:38 2017
  InstallationDate: Installed on 2015-04-02 (773 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: Upgraded to zesty on 2017-04-18 (26 days ago)

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

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


[Desktop-packages] [Bug 1693756] Re: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication.

2017-05-30 Thread Alex Tu
** Description changed:

  # issue:
-  * wwan card DW5816e[413c:81cc] couldn't be recognized by modemmanager 
1.4.12-1ubuntu1 on xenial.
-   - but works well on on Yakkety.
+  * wwan card DW5816e[413c:81cc] couldn't be recognized by modemmanager 
1.4.12-1ubuntu1 on xenial.
+   - but works well on on Yakkety.
  
  # investgation:
-  * in failed case, mmcli -L shows nothing on Xenial with DW5816. Then tried 
install followed packages from Yakkety ppa on Xenial and wwan card works on 1st 
boot but failed after 2nd boot sometimes.
-   - libmbim-glib4_1.14.0-1_amd64.deb
-   - libmbim-glib-dev_1.14.0-1_amd64.deb
-   - libmbim-proxy_1.14.0-1_amd64.deb
-   - libmbim-utils_1.14.0-1_amd64.deb
-   - libqmi-glib5_1.16.0-1_amd64.deb
-   - libqmi-proxy_1.16.0-1_amd64.deb
+  * in failed case, mmcli -L shows nothing on Xenial with DW5816. Then tried 
install followed packages from Yakkety ppa on Xenial and wwan card works on 1st 
boot but failed after 2nd boot sometimes.
+   - libmbim-glib4_1.14.0-1_amd64.deb
+   - libmbim-glib-dev_1.14.0-1_amd64.deb
+   - libmbim-proxy_1.14.0-1_amd64.deb
+   - libmbim-utils_1.14.0-1_amd64.deb
+   - libqmi-glib5_1.16.0-1_amd64.deb
+   - libqmi-proxy_1.16.0-1_amd64.deb
  
-  * different from ModemManager --debug
-- In passed case, it received message from /dev/cdc-wdm1 after send "Read 
max control message size from descriptors file: 4096" , but not happens to 
failed case. So, it prints "[mm-port-probe.c:261] 
mm_port_probe_set_result_qcdm(): (tty/ttyS4) port is not QCDM-capable" in 
failed case.
-  - passed case: http://paste.ubuntu.com/24664908/
-  - failed case: http://paste.ubuntu.com/24664910/
+  * different from ModemManager --debug
+    - In passed case, it received message from /dev/cdc-wdm1 after send "Read 
max control message size from descriptors file: 4096" , but not happens to 
failed case. So, it prints "[mm-port-probe.c:261] 
mm_port_probe_set_result_qcdm(): (tty/ttyS4) port is not QCDM-capable" in 
failed case.
+  - passed case: http://paste.ubuntu.com/24664908/
+  - failed case: http://paste.ubuntu.com/24664910/
  
  # Plan:
-  * let the newer version packages could also works well on Xenial.
-  * find out needed patches on newer version packages.
-  * packport needed patches to older version packages on Xenial.
+  * let the newer version packages could also works well on Xenial.
+  * find out needed patches on newer version packages.
+  * packport needed patches to older version packages on Xenial.
  
  # environment information:
  
-  * modinfo cdc_mbim for original kernel module: 
http://paste.ubuntu.com/24662359/
-   - the code /driver/net/usb/cdc_mbim.c is the same between xenial kernel 
4.4.0 and yakkety kernel 4.8.0.
+  * modinfo cdc_mbim for original kernel module: 
http://paste.ubuntu.com/24662359/
+   - the code /driver/net/usb/cdc_mbim.c is the same between xenial kernel 
4.4.0 and yakkety kernel 4.8.0.
  
-  * uname -r: 4.4.0-73-generic
+  * uname -r: 4.4.0-73-generic
  
-  * lsusb -v: http://paste.ubuntu.com/24662332/
+  * lsusb -v: http://paste.ubuntu.com/24662332/
+ 
+ FCC authentication reference:
+  * http://lists.infradead.org/pipermail/lede-dev/2016-August/002332.html
+  * 
https://lists.freedesktop.org/archives/libmbim-devel/2016-April/thread.html#704

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

Title:
  [Xenial][ DW5816e] to support qmi over mbim which needed for FCC
  authentication.

Status in modemmanager package in Ubuntu:
  New

Bug description:
  # issue:
   * wwan card DW5816e[413c:81cc] couldn't be recognized by modemmanager 
1.4.12-1ubuntu1 on xenial.
    - but works well on on Yakkety.

  # investgation:
   * in failed case, mmcli -L shows nothing on Xenial with DW5816. Then tried 
install followed packages from Yakkety ppa on Xenial and wwan card works on 1st 
boot but failed after 2nd boot sometimes.
    - libmbim-glib4_1.14.0-1_amd64.deb
    - libmbim-glib-dev_1.14.0-1_amd64.deb
    - libmbim-proxy_1.14.0-1_amd64.deb
    - libmbim-utils_1.14.0-1_amd64.deb
    - libqmi-glib5_1.16.0-1_amd64.deb
    - libqmi-proxy_1.16.0-1_amd64.deb

   * different from ModemManager --debug
     - In passed case, it received message from /dev/cdc-wdm1 after send "Read 
max control message size from descriptors file: 4096" , but not happens to 
failed case. So, it prints "[mm-port-probe.c:261] 
mm_port_probe_set_result_qcdm(): (tty/ttyS4) port is not QCDM-capable" in 
failed case.
   - passed case: http://paste.ubuntu.com/24664908/
   - failed case: http://paste.ubuntu.com/24664910/

  # Plan:
   * let the newer version packages could also works well on Xenial.
   * find out needed patches on newer version packages.
   * packport needed patches to older version packages on Xenial.

  # environment information:

   * modinfo cdc_mbim for original kernel module: 
http://paste.ubuntu.com/24662359/
    - 

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

2017-05-30 Thread Daniel van Vugt
OK, thanks for testing that. The bug is then Fix Released for current
Ubuntu. As soon as we know /what/ fixed it, we can start thinking about
getting that fix into 16.04 too.

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Fix Released

-- 
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:
  Fix Released

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 1694565] [NEW] llvm-toolchain-3.8 FTBFS in Artful due to gcc-6 ICE

2017-05-30 Thread Balint Reczey
Public bug reported:

Rebuilding llvm-toolchain-3.8 1:3.8.1-23ubuntu3 failed on i386:

...
[ 54%] Building CXX object tools/clang/lib/Sema/CMakeFiles/clangSema.dir/SemaEx
prCXX.cpp.o
cd /<>/build-llvm/tools/clang/lib/Sema && /usr/bin/g++-6   -DCLANG
_ENABLE_ARCMT -DCLANG_ENABLE_OBJC_REWRITER -DCLANG_ENABLE_STATIC_ANALYZER -D_GN
U_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS 
-I/<>/build-llvm/tools/clang/lib/Sema -I/<>/tools/cla
ng/lib/Sema -I/<>/tools/clang/include -I/<>/build-llv
m/tools/clang/include -I/<>/build-llvm/include -I/<>/
include  -std=c++0x -gsplit-dwarf -Wl,-fuse-ld=gold -fPIC -fvisibility-inlines-
hidden -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-
field-initializers -pedantic -Wno-long-long -Wno-maybe-uninitialized -Wdelete-n
on-virtual-dtor -Wno-comment -std=c++11 -ffunction-sections -fdata-sections -fn
o-common -Woverloaded-virtual -fno-strict-aliasing -O2 -g -DNDEBUG-fno-exce
ptions -o CMakeFiles/clangSema.dir/SemaExprCXX.cpp.o -c /<>/tools/
clang/lib/Sema/SemaExprCXX.cpp
...
g++-6: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.
tools/clang/lib/Sema/CMakeFiles/clangSema.dir/build.make:689: recipe for target
 'tools/clang/lib/Sema/CMakeFiles/clangSema.dir/SemaExprCXX.cpp.o' failed
make[4]: *** [tools/clang/lib/Sema/CMakeFiles/clangSema.dir/SemaExprCXX.cpp.o] 
Error 4
make[4]: *** Waiting for unfinished jobs
make[4]: Leaving directory '/<>/build-llvm'
CMakeFiles/Makefile2:24600: recipe for target 'tools/clang/lib/Sema/CMakeFiles/
clangSema.dir/all' failed
make[3]: *** [tools/clang/lib/Sema/CMakeFiles/clangSema.dir/all] Error 2
make[3]: Leaving directory '/<>/build-llvm'
Makefile:152: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/<>/build-llvm'
debian/rules:269: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
debian/rules:150: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

** Affects: gcc-6 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: llvm-toolchain-3.8 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: ftbfs

** Attachment added: "build log"
   
https://bugs.launchpad.net/bugs/1694565/+attachment/4886406/+files/llvm-toolchain-3.8_i386.build

** Also affects: gcc-6 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  llvm-toolchain-3.8 FTBFS in Artful due to gcc-6 ICE

Status in gcc-6 package in Ubuntu:
  New
Status in llvm-toolchain-3.8 package in Ubuntu:
  New

Bug description:
  Rebuilding llvm-toolchain-3.8 1:3.8.1-23ubuntu3 failed on i386:

  ...
  [ 54%] Building CXX object 
tools/clang/lib/Sema/CMakeFiles/clangSema.dir/SemaEx
  prCXX.cpp.o
  cd /<>/build-llvm/tools/clang/lib/Sema && /usr/bin/g++-6   
-DCLANG
  _ENABLE_ARCMT -DCLANG_ENABLE_OBJC_REWRITER -DCLANG_ENABLE_STATIC_ANALYZER 
-D_GN
  U_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS 
-D__STDC_LIMIT_MACROS 
  -I/<>/build-llvm/tools/clang/lib/Sema 
-I/<>/tools/cla
  ng/lib/Sema -I/<>/tools/clang/include 
-I/<>/build-llv
  m/tools/clang/include -I/<>/build-llvm/include 
-I/<>/
  include  -std=c++0x -gsplit-dwarf -Wl,-fuse-ld=gold -fPIC 
-fvisibility-inlines-
  hidden -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual 
-Wno-missing-
  field-initializers -pedantic -Wno-long-long -Wno-maybe-uninitialized 
-Wdelete-n
  on-virtual-dtor -Wno-comment -std=c++11 -ffunction-sections -fdata-sections 
-fn
  o-common -Woverloaded-virtual -fno-strict-aliasing -O2 -g -DNDEBUG
-fno-exce
  ptions -o CMakeFiles/clangSema.dir/SemaExprCXX.cpp.o -c 
/<>/tools/
  clang/lib/Sema/SemaExprCXX.cpp
  ...
  g++-6: internal compiler error: Killed (program cc1plus)
  Please submit a full bug report,
  with preprocessed source if appropriate.
  See  for instructions.
  tools/clang/lib/Sema/CMakeFiles/clangSema.dir/build.make:689: recipe for 
target
   'tools/clang/lib/Sema/CMakeFiles/clangSema.dir/SemaExprCXX.cpp.o' failed
  make[4]: *** 
[tools/clang/lib/Sema/CMakeFiles/clangSema.dir/SemaExprCXX.cpp.o] 
  Error 4
  make[4]: *** Waiting for unfinished jobs
  make[4]: Leaving directory '/<>/build-llvm'
  CMakeFiles/Makefile2:24600: recipe for target 
'tools/clang/lib/Sema/CMakeFiles/
  clangSema.dir/all' failed
  make[3]: *** [tools/clang/lib/Sema/CMakeFiles/clangSema.dir/all] Error 2
  make[3]: Leaving directory '/<>/build-llvm'
  Makefile:152: recipe for target 'all' failed
  make[2]: *** [all] Error 2
  make[2]: Leaving directory '/<>/build-llvm'
  debian/rules:269: recipe for target 'override_dh_auto_build' failed
  make[1]: *** 

[Desktop-packages] [Bug 1694566] [NEW] black screen white pointer

2017-05-30 Thread themusicgod1
Public bug reported:

gnome-screenshot by dash results in spinning cursor and then nothing

gnome-screenshot by commandline ...results in black screen with white
pointer and nothing else.  Have to alt-f1 to log into a new shell to
find & kill gnome-screenshot process which gets unity back.

once i kill the process further instances of gnome-screenshot work fine.

errors in the meanwhile: 
Error creating proxy: GDBus.Error:org.freedesktop.DBus.Error.LimitsExceeded: 
Failed to determine seats of user "1001": Too many open files 
(g-dbus-error-quark, 8)

desktop environment: unity 7.5.0+17.04.20170407.1-0ubuntu1
xorg : 1:7.7+16ubuntu3
ubuntu: 17.04 zesty
Linux eva1 4.10.0-21-generic #23-Ubuntu SMP Fri Apr 28 16:14:22 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux

   *-display
 description: VGA compatible controller
 product: Intel Corporation
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 04
 width: 64 bits
 clock: 33MHz
 capabilities: pciexpress msi pm vga_controller bus_master cap_list 
rom
 configuration: driver=i915 latency=0
 resources: irq:128 memory:de00-deff 
memory:c000-cfff ioport:f000(size=64) memory:c-d

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-screenshot 3.22.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Tue May 30 19:48:41 2017
InstallationDate: Installed on 2017-04-18 (42 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
SourcePackage: gnome-screenshot
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  black screen white pointer

Status in gnome-screenshot package in Ubuntu:
  New

Bug description:
  gnome-screenshot by dash results in spinning cursor and then nothing

  gnome-screenshot by commandline ...results in black screen with white
  pointer and nothing else.  Have to alt-f1 to log into a new shell to
  find & kill gnome-screenshot process which gets unity back.

  once i kill the process further instances of gnome-screenshot work
  fine.

  errors in the meanwhile: 
  Error creating proxy: GDBus.Error:org.freedesktop.DBus.Error.LimitsExceeded: 
Failed to determine seats of user "1001": Too many open files 
(g-dbus-error-quark, 8)

  desktop environment: unity 7.5.0+17.04.20170407.1-0ubuntu1
  xorg : 1:7.7+16ubuntu3
  ubuntu: 17.04 zesty
  Linux eva1 4.10.0-21-generic #23-Ubuntu SMP Fri Apr 28 16:14:22 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

 *-display
   description: VGA compatible controller
   product: Intel Corporation
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 04
   width: 64 bits
   clock: 33MHz
   capabilities: pciexpress msi pm vga_controller bus_master 
cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:128 memory:de00-deff 
memory:c000-cfff ioport:f000(size=64) memory:c-d

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-screenshot 3.22.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Tue May 30 19:48:41 2017
  InstallationDate: Installed on 2017-04-18 (42 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1694367] Re: Screen tearing in 16.10 onwards

2017-05-30 Thread Bug Watch Updater
** Changed in: mesa
   Status: Unknown => Confirmed

** Changed in: mesa
   Importance: Unknown => Medium

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

Title:
  Screen tearing in 16.10 onwards

Status in Mesa:
  Confirmed
Status in kernel-package package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  In 16.10 onwards my laptop has always shown screen tearing globally,
  additionally GL applications will not v-sync despite attempting to,
  they appear to sync slightly off from the [integrated] display.

  This occurs with kernels 4.8 to 4.11 and mesa 12 to 17, so not
  entirely sure if it's a bug with either or a default miss-
  configuration in ubuntu...

  ubuntu-bug also appears to be broken...

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

-- 
Mailing list: https://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 1565772] Re: [SRU] Allow plugins to decide which username to set on new accounts

2017-05-30 Thread Philipp von der Linden
Hello, Hans!

I am sorry for not being more helpful, but I really do not have anything 
more to say than: If you think, it is covered, it is covered. If you 
think, it is all duplicates, then it will be the case, I trust.

HG, PvdL

-- 
Philipp von der Linden, M.A.
OsloerStr.93 D-13359 Wedding
eMail: "PvdL" 

On 30.05.2017 21:01, Hans Joachim Desserud wrote:
> I've read through this now, but just to double-check:
> There's various bug reports with package-conflicts for files in 
> '/etc/signon-ui/webkit-options.d/*' between account-plugins and 
> kaccounts-providers. (For instance bug 1617564)
> 
>>From what I see, this issue will remove the conflicting files from the
> account-plugins side and thus fix the issue. Does that mean that these
> other issues should all be marked as duplicates of this one?
>

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

Title:
  [SRU] Allow plugins to decide which username to set on new accounts

Status in Online Accounts: Account plugins:
  Fix Released
Status in Canonical System Image:
  Fix Released
Status in Online Accounts: GNOME Control Center:
  Fix Released
Status in webapps-sprint:
  Fix Committed
Status in account-plugins package in Ubuntu:
  Fix Released
Status in gnome-control-center-signon package in Ubuntu:
  Fix Released
Status in account-plugins source package in Xenial:
  Fix Committed
Status in gnome-control-center-signon source package in Xenial:
  Fix Committed
Status in account-plugins source package in Yakkety:
  Fix Released
Status in gnome-control-center-signon source package in Yakkety:
  Fix Released

Bug description:
  This bug is related to bug 1547647, even though it makes sense in any
  case.

  Currently, the ApOAuthPlugin class in libaccount-plugin gets the
  username from the SignonIdentity, which in turn gets it from signon-
  ui, which in the current WebKit1 implementation gets it from the DOM
  of the login webpage. This is a hack, it's fragile, not trivial to
  port to the Oxide web engine, and possibly against some providers'
  guidelines.

  We should retrieve the username using some REST API provided by the
  service, and in order to do so we need to extend libaccounts-plugin
  with some hooks which subclasses can use to get the username.

  Once we fix this we can also get rid of the files /etc/signon-ui
  /webkit-options.d/, which are conflicting with those installed by the
  KDE account plugins packages.


  SRU information
  ===

  [Impact] The same file /etc/signon-ui/webkit-
  options.d/www.facebook.com.conf is installed by the account-plugin-
  facebook package (used by Unity) and by kaccount-providers (used by
  KDE). See this bug's duplicates to see actual bug reports.

  [Test Case] Install both account-plugin-facebook and kaccount-
  providers and you'll get the conflict.

  [Regression Potential] Users running KDE will be completely unaffected
  by this. Users running Unity might see a change when creating accounts
  in System Settings->Online Accounts: with this bugfix, the account's
  display name is obtained by making a REST API call to the remote
  service, rather than by scrapping the DOM of the server webpages
  (which is a hack, and prone to errors if the providers' webpage
  changes). The new way of retrieving the username is the proper one,
  and it's been tested to work reliably. In any case, the worst thing
  that might happen is that accounts get created with an empty display
  name, which is mostly an aesthetic problem (the display name is used
  only for UI purposes).

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1565772/+subscriptions

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


[Desktop-packages] [Bug 1694367] Re: Screen tearing in 16.10 onwards

2017-05-30 Thread Paul
** Bug watch added: freedesktop.org Bugzilla #101229
   https://bugs.freedesktop.org/show_bug.cgi?id=101229

** Also affects: mesa via
   https://bugs.freedesktop.org/show_bug.cgi?id=101229
   Importance: Unknown
   Status: Unknown

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

Title:
  Screen tearing in 16.10 onwards

Status in Mesa:
  Unknown
Status in kernel-package package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  In 16.10 onwards my laptop has always shown screen tearing globally,
  additionally GL applications will not v-sync despite attempting to,
  they appear to sync slightly off from the [integrated] display.

  This occurs with kernels 4.8 to 4.11 and mesa 12 to 17, so not
  entirely sure if it's a bug with either or a default miss-
  configuration in ubuntu...

  ubuntu-bug also appears to be broken...

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

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


[Desktop-packages] [Bug 1694542] [NEW] can't get print to work

2017-05-30 Thread Fred Hooper
Public bug reported:

i have a samsung m2070fw printer it will not respond

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 i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: i386
BootLog:
 [FAILED] Failed to start Automatic USB/Bluetooth printer setup 
(-devices-pci:00-:00:1d.7-usb2-2\x2d8-2\x2d8.2).
 See 'systemctl status 
"udev-configure-printer@-devices-pci:00-:00:1d.7-usb2-2\\x2d8-2\\x2d8.2.service"'
 for details.
 [  OK  ] Started Network Manager Script Dispatcher Service.
 [  OK  ] Started Modem Manager.
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue May 30 17:32:56 2017
DistUpgraded: 2016-08-03 21:03:22,827 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 82G33/G31 Express Integrated Graphics 
Controller [103c:2a6f]
InstallationDate: Installed on 2014-11-25 (917 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
MachineType: HP-Pavilion NC839AA-ABA a6838f
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=8c58f378-744f-466b-8075-ce338c5307b9 ro quiet splash
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-08-04 (299 days ago)
dmi.bios.date: 02/23/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.37
dmi.board.name: Benicia
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.01
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.37:bd02/23/2009:svnHP-Pavilion:pnNC839AA-ABAa6838f:pvr:rvnPEGATRONCORPORATION:rnBenicia:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion:
dmi.product.name: NC839AA-ABA a6838f
dmi.sys.vendor: HP-Pavilion
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue May 30 21:16:22 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputMicrosoft Microsoft Wheel Mouse Optical® MOUSE, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   44416 
 vendor ACR
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: apport-bug compiz-0.9 i386 ubuntu 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/1694542

Title:
  can't get print to work

Status in xorg package in Ubuntu:
  New

Bug description:
  i have a samsung m2070fw printer it will not respond

  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 i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  BootLog:
   [FAILED] Failed to start Automatic USB/Bluetooth printer setup 
(-devices-pci:00-:00:1d.7-usb2-2\x2d8-2\x2d8.2).
   See 'systemctl status 
"udev-configure-printer@-devices-pci:00-:00:1d.7-usb2-2\\x2d8-2\\x2d8.2.service"'
 for details.
   [  OK  ] Started Network Manager Script Dispatcher Service.
   [  OK  ] Started Modem Manager.
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue May 30 17:32:56 2017
  DistUpgraded: 2016-08-03 21:03:22,827 

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

2017-05-30 Thread dualshock3nerd
@vanvugt

I tested 17.04 in a live USB environment all day. This bug never showed up.
In 16.04 LTS this annoying bug pops up at least once in a couple of minutes so 
I assume it's fixed in Zesty at least.
Thanks for looking into 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/1585084

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

Status in pulseaudio package in Ubuntu:
  Incomplete

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 1688418] Re: Missing keyboard-key-*.svg icons

2017-05-30 Thread Jeremy Bicha
This was fixed in https://launchpad.net/ubuntu/+source/gnome-user-
docs/3.24.2-0ubuntu1

** Changed in: gnome-user-docs (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Missing keyboard-key-*.svg icons

Status in Gnome Documentation:
  Fix Released
Status in gnome-user-docs package in Ubuntu:
  Fix Released
Status in gnome-user-docs package in Debian:
  New

Bug description:
  This page:

  https://help.gnome.org/users/gnome-help/stable/keyboard-shortcuts-
  set.html

  links to a bunch of keyboard-key-*.svg icons which don't exist. The
  icons are not present in the gnome-user-guide package either.

  (Noticed it when running the "yelp-build html" command. Apparently an
  upstream issue.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-user-docs/+bug/1688418/+subscriptions

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


[Desktop-packages] [Bug 1686726] Re: [MIR] gnome-getting-started-docs

2017-05-30 Thread Jeremy Bicha
gnome-getting-started-docs is now in main for artful.

** Changed in: gnome-getting-started-docs (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [MIR] gnome-getting-started-docs

Status in gnome-getting-started-docs package in Ubuntu:
  Fix Released

Bug description:
  Availability
  
  Co-maintained with Debian GNOME. Built for all supported architectures.

  Changes from Debian:
  - Updated to 3.24
  - Split translations into separate packages. The appropriate one is installed 
by language-selector.
  - Run dh_install --fail-missing to make sure we don't miss new translations
  - Don't run dh_scour since it somehow breaks the video 'thumbnail' svgs.
  Although Ubuntu's cdbs runs dh-scour only for packages in main, Ubuntu's 
gnome-pkg-tools currently runs dh-scour for all packages using dh --with gnome
  - Add alternate dependency of ubuntu-docs instead of just gnome-user-guide. 
(This change will be reverted later since ubuntu-docs now is an addon for 
gnome-user-guide.)

  Rationale
  =
  Addon for GNOME User Help. It adds an extra Getting Started section to the 
User Help. The section includes some short animated videos and simpler quick 
start help.

  If installed, GNOME's Initial Setup utility runs the first time a user
  logs in. When they finish answering the set up questions, Initial
  Setup exist and opens the Getting Started Help.

  Even if Ubuntu doesn't use GNOME Initial Setup, it might be worth
  showing the Getting Started help on first login. (Ubuntu GNOME 16.04
  LTS does this, because gnome-initial-setup isn't available in 16.04.)

  Security
  
  Not a security concern. It's just some videos and some Mallard help files 
(Mallard is an XML format).

  http://projectmallard.org/

  Quality assurance
  =
  - The Desktop Bugs and Desktop Packages are subscribed to this package.

  https://bugs.launchpad.net/ubuntu/+source/gnome-getting-started-docs
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=gnome-getting-started-docs
  
https://bugzilla.gnome.org/buglist.cgi?quicksearch=product%3A"gnome-getting-started;

  No tests.

  Dependencies
  
  All runtime dependencies are in main.

  Standards compliance
  
  3.9.8

  Maintenance
  ===
  - Actively developed upstream
  https://git.gnome.org/browse/gnome-getting-started-docs/

  Debian packaging uses svn, but we're hoping to convert to git this year 
(which will allow for Ubuntu branches):
  https://sources.debian.net/src/gnome-getting-started-docs/unstable/debian/

  Background information
  ==
  N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-getting-started-docs/+bug/1686726/+subscriptions

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


[Desktop-packages] [Bug 444744] Re: Evolution should allow addition of unknown PGP keys

2017-05-30 Thread Bug Watch Updater
** Changed in: evolution
   Status: Confirmed => Fix Released

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

Title:
  Evolution should allow addition of unknown PGP keys

Status in Evolution:
  Fix Released
Status in evolution package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: evolution

  It would be fairly simple to implement a simple "add this key to PGP
  keyring" when a message is signed by a key not in the keyring. This
  would allow a user to simply expand their keyring, perhaps with a
  brief note about unverified keys and the web of trust.

  ProblemType: Bug
  Architecture: i386
  Date: Tue Oct  6 18:26:48 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/evolution
  Package: evolution 2.28.0-0ubuntu3
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
  SourcePackage: evolution
  Uname: Linux 2.6.31-11-generic i686

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

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


[Desktop-packages] [Bug 1693502] Re: Update to 53.0.3

2017-05-30 Thread Jeremy Bicha
** Changed in: firefox (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Update to 53.0.3

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  See https://www.mozilla.org/en-US/firefox/53.0.3/releasenotes/

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

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


[Desktop-packages] [Bug 1694331] Re: "internal error" popup on login

2017-05-30 Thread Christopher M. Penalver
Andreas Fritiofson, to keep this report manageable, let us avoid
discussing other computers, other colleagues computers, etc. and instead
remain focused here in this report on the Asus UX32VD.

One problem, per computer setup, per report.

If you have an issue with a different computer, file a new bug report
while using that different computer.

Remaining focused on the Asus UX32VD, as per
https://wiki.ubuntu.com/Releases Ubuntu 16.10 will be EoL'ing in a
month. Hence, could you please upgrade to 17.04 and advise if Xorg
crashes still from time to time?

** Description changed:

- Sometimes (not very often), Ubuntu shows an error popup immediately
- after login (after power-on) that says Xorg has crashed. No other ill
- effects have been noticed, everything works normally after that.
- 
- The automatic error reporting does not go through because of
- "UnreportableReason: Invalid core dump: BFD: Warning
- /tmp/apport_core_5n7s8i3d is truncated: expected core file size >=
- 40902656, found: 21037056."
- 
- I was asked by Christopher M. Penalver in Bug 1426596 to submit a new
- bug using "ubuntu-bug xorg" when the error appeared. This is that
- report, although the computer I used now to generate the report is not
- the same as I mentioned in the original bug (I've seen the same issue on
- more or less all computers I've used and IIRC from at least 16.04 to
- 17.04).
+ My Asus UX32VD shows an Xorg crash from time to time (but not nearly at
+ every boot).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-53.56-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.3-0ubuntu8.3
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon May 29 22:31:18 2017
  DistUpgraded: 2017-04-15 01:32:04,429 DEBUG /openCache(), new cache size 85680
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
-  bbswitch, 0.8, 4.8.0-52-generic, x86_64: installed
-  bbswitch, 0.8, 4.8.0-53-generic, x86_64: installed
+  bbswitch, 0.8, 4.8.0-52-generic, x86_64: installed
+  bbswitch, 0.8, 4.8.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:1507]
+  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:1507]
  InstallationDate: Installed on 2014-04-18 (1137 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-53-generic.efi.signed 
root=UUID=959fa127-2d15-48a5-9fa0-70f918fab2ad ro rootflags=subvol=@ quiet 
splash pcie_aspm=force nmi_watchdog=0 vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to yakkety on 2017-04-14 (44 days ago)
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.10.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Mon May 29 22:28:30 2017
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 

[Desktop-packages] [Bug 1676829] Re: Mic input volume always resets (to middle/low value) on resume or restart

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

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

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

Title:
  Mic input volume always resets (to middle/low value) on resume or
  restart

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Sound card: CA0106/CA0111

  Each time I start PC - mic input volume resets to some "default" value.
  This happens from 16.04 (maybe earlier). Now I have 17.04, still have it.

  Each time I run:

  1) alsamixer
  2) select input device, "Line In"
  3) set it to max.

  (Or same actions in Ubuntu GUI)

  Then (after restart or suspend) the volume goes back to some middle
  value (low for me).

  I'm pissed off setting it back again and again. Does someone else have
  this problem?

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

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


[Desktop-packages] [Bug 1621753] Re: Google Cast no longer finds Chromecast device

2017-05-30 Thread Olivier Tilloy
** Changed in: chromium-browser (Ubuntu)
 Assignee: Chad Miller (cmiller) => Olivier Tilloy (osomon)

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

Title:
  Google Cast no longer finds Chromecast device

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to latest chromium-browser version
  (52.0.2743.116-0ubuntu0.16.04.1.1250), the Google Cast extension no
  longer finds the Chromecast (v2) device. This used to work with the
  previous chromium version.

  Also, google-chrome-stable 53.0.2785.101-1 works fine on the same box,
  so the issue is with the chromium update.

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

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


[Desktop-packages] [Bug 1631782] Re: Volume and Mic controls grayed out and not working

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

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

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

Title:
  Volume and Mic controls grayed out and not working

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Hallo
  testing Yakkety 08-10 buld on live session i have the controls of the volume 
locked and not working as shown in the attached screenshot. Even in sound 
setting I can-t set the desired volume, anyway it play sounds correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: pulseaudio 1:9.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.379
  CurrentDesktop: Unity
  Date: Sun Oct  9 17:53:10 2016
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F7
  dmi.board.name: H55M-S2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd08/20/2010:svnGigabyteTechnologyCo.,Ltd.:pnH55M-S2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH55M-S2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: H55M-S2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Desktop-packages] [Bug 1694329] Re: oversized "characters" when Noto Color Emoji font is used on a page

2017-05-30 Thread Václav Haisman
** Attachment removed: "CRDA.txt"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1694329/+attachment/4885851/+files/CRDA.txt

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

Title:
  oversized "characters" when Noto Color Emoji font is used on a page

Status in firefox package in Ubuntu:
  New

Bug description:
  I am seeing oversized emoji characters. See a duck in attached
  screenshot. This duck is from Noto Color Emoji font. In previous
  releases of Firefox it worked fine. It also works fine on Firefox for
  Windows. You can test it yourself if you have the font by visiting
  this URL:
  http://chat.stackexchange.com/transcript/message/37722474#37722474

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-lowlatency 4.10.0-21.23
  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.1
  Architecture: amd64
  Date: Mon May 29 22:07:30 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cf2fd7df-da6e-4e8b-876e-c91fa967ae41
  InstallationDate: Installed on 2011-11-13 (2024 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-790XTA-UD4
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-lowlatency 
root=UUID=503b3cdd-770e-4354-bf3d-c917a2ebe292 ro nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw elevator=cfq nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  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.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-21-lowlatency N/A
   linux-backports-modules-4.10.0-21-lowlatency  N/A
   linux-firmware1.164.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (43 days ago)
  dmi.bios.date: 12/03/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-790XTA-UD4
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd12/03/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-790XTA-UD4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-790XTA-UD4:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-790XTA-UD4
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Desktop-packages] [Bug 1694517] [NEW] Kernel crashes, task wpa_supplicant blocked for more than 120 seconds

2017-05-30 Thread Cerin
Public bug reported:

When using Gnome-Shell on Ubuntu 16.04, the Internet connection will
suddenly drop off, even though the network connection icon will still
indicate a connection.

Attempting to run `sudo service network-manager restart` will hang
indefinitely.

Attempting to restart Gnome-Shell via alt+F2+r, will cause Gnome-Shell
to hang indefinitely.

Switching to a terminal, I inspecting `dmesg` and found several messages
like:

[178443.199324] INFO: task wpa_supplicant:1708 blocked for more than 120 
seconds.
[178443.199332]   Tainted: G   OE   4.4.0-78-generic #99-Ubuntu
[178443.199335] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
[178443.199337] wpa_supplicant  D 88085849ba38 0  1708  1 
0x
[178443.199345]  88085849ba38 88087f516e30 88001cd2da00 
880853c35a00
[178443.199350]  88085849c000 81ef8184 880853c35a00 

[178443.199354]  81ef8188 88085849ba50 8183c8f5 
81ef8180
[178443.199358] Call Trace:
[178443.199369]  [] schedule+0x35/0x80
[178443.199374]  [] schedule_preempt_disabled+0xe/0x10
[178443.199378]  [] __mutex_lock_slowpath+0xb9/0x130
[178443.199386]  [] mutex_lock+0x1f/0x30
[178443.199393]  [] rtnl_lock+0x15/0x20
[178443.199422]  [] nl80211_pre_doit+0xeb/0x180 [cfg80211]
[178443.199429]  [] genl_family_rcv_msg+0x1ad/0x3e0
[178443.199435]  [] ? __wake_up_common+0x52/0x90
[178443.199441]  [] ? genl_family_rcv_msg+0x3e0/0x3e0
[178443.199446]  [] genl_rcv_msg+0x76/0xb0
[178443.199450]  [] netlink_rcv_skb+0xa4/0xc0
[178443.199455]  [] genl_rcv+0x28/0x40
[178443.199459]  [] netlink_unicast+0x18a/0x240
[178443.199464]  [] netlink_sendmsg+0x2fb/0x3a0
[178443.199470]  [] ? aa_sock_msg_perm+0x61/0x150
[178443.199477]  [] sock_sendmsg+0x38/0x50
[178443.199480]  [] ___sys_sendmsg+0x281/0x290
[178443.199487]  [] ? __fpu__restore_sig+0xa1/0x480
[178443.199491]  [] __sys_sendmsg+0x51/0x90
[178443.199496]  [] SyS_sendmsg+0x12/0x20
[178443.199501]  [] entry_SYSCALL_64_fastpath+0x16/0x71

I see similar errors for other programs other than wpa_supplicant, so it
might not be isolated to it, but I'm not sure where else to submit this
error to.

All other `sudo` commands hung, even after 15 minutes of waiting,
leaving me no choice but to reboot. However, this has happened several
times after a recent update, and the symptoms always manifest exactly
the same. No Internet, then Gnome-Shell hangs, then all sudo commands
hang.

I managed to copy my dmesg log before the reboot, which I have attached.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: wpasupplicant 2.4-0ubuntu6
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
CurrentDesktop: GNOME
Date: Tue May 30 14:56:58 2017
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
InstallationDate: Installed on 2017-03-09 (81 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
SourcePackage: wpa
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

** Attachment added: "dmesg log just after system begun to hang"
   https://bugs.launchpad.net/bugs/1694517/+attachment/4886316/+files/dmesg.txt

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

Title:
  Kernel crashes, task wpa_supplicant blocked for more than 120 seconds

Status in wpa package in Ubuntu:
  New

Bug description:
  When using Gnome-Shell on Ubuntu 16.04, the Internet connection will
  suddenly drop off, even though the network connection icon will still
  indicate a connection.

  Attempting to run `sudo service network-manager restart` will hang
  indefinitely.

  Attempting to restart Gnome-Shell via alt+F2+r, will cause Gnome-Shell
  to hang indefinitely.

  Switching to a terminal, I inspecting `dmesg` and found several
  messages like:

  [178443.199324] INFO: task wpa_supplicant:1708 blocked for more than 120 
seconds.
  [178443.199332]   Tainted: G   OE   4.4.0-78-generic 
#99-Ubuntu
  [178443.199335] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
  [178443.199337] wpa_supplicant  D 88085849ba38 0  1708  1 
0x
  [178443.199345]  88085849ba38 88087f516e30 88001cd2da00 
880853c35a00
  [178443.199350]  88085849c000 81ef8184 880853c35a00 

  [178443.199354]  81ef8188 88085849ba50 

[Desktop-packages] [Bug 1565772] Re: [SRU] Allow plugins to decide which username to set on new accounts

2017-05-30 Thread Hans Joachim Desserud
I've read through this now, but just to double-check:
There's various bug reports with package-conflicts for files in 
'/etc/signon-ui/webkit-options.d/*' between account-plugins and 
kaccounts-providers. (For instance bug 1617564)

>From what I see, this issue will remove the conflicting files from the
account-plugins side and thus fix the issue. Does that mean that these
other issues should all be marked as duplicates of this one?

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

Title:
  [SRU] Allow plugins to decide which username to set on new accounts

Status in Online Accounts: Account plugins:
  Fix Released
Status in Canonical System Image:
  Fix Released
Status in Online Accounts: GNOME Control Center:
  Fix Released
Status in webapps-sprint:
  Fix Committed
Status in account-plugins package in Ubuntu:
  Fix Released
Status in gnome-control-center-signon package in Ubuntu:
  Fix Released
Status in account-plugins source package in Xenial:
  Fix Committed
Status in gnome-control-center-signon source package in Xenial:
  Fix Committed
Status in account-plugins source package in Yakkety:
  Fix Released
Status in gnome-control-center-signon source package in Yakkety:
  Fix Released

Bug description:
  This bug is related to bug 1547647, even though it makes sense in any
  case.

  Currently, the ApOAuthPlugin class in libaccount-plugin gets the
  username from the SignonIdentity, which in turn gets it from signon-
  ui, which in the current WebKit1 implementation gets it from the DOM
  of the login webpage. This is a hack, it's fragile, not trivial to
  port to the Oxide web engine, and possibly against some providers'
  guidelines.

  We should retrieve the username using some REST API provided by the
  service, and in order to do so we need to extend libaccounts-plugin
  with some hooks which subclasses can use to get the username.

  Once we fix this we can also get rid of the files /etc/signon-ui
  /webkit-options.d/, which are conflicting with those installed by the
  KDE account plugins packages.


  SRU information
  ===

  [Impact] The same file /etc/signon-ui/webkit-
  options.d/www.facebook.com.conf is installed by the account-plugin-
  facebook package (used by Unity) and by kaccount-providers (used by
  KDE). See this bug's duplicates to see actual bug reports.

  [Test Case] Install both account-plugin-facebook and kaccount-
  providers and you'll get the conflict.

  [Regression Potential] Users running KDE will be completely unaffected
  by this. Users running Unity might see a change when creating accounts
  in System Settings->Online Accounts: with this bugfix, the account's
  display name is obtained by making a REST API call to the remote
  service, rather than by scrapping the DOM of the server webpages
  (which is a hack, and prone to errors if the providers' webpage
  changes). The new way of retrieving the username is the proper one,
  and it's been tested to work reliably. In any case, the worst thing
  that might happen is that accounts get created with an empty display
  name, which is mostly an aesthetic problem (the display name is used
  only for UI purposes).

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1565772/+subscriptions

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


[Desktop-packages] [Bug 1428121] Re: Intel HDMI Audio not working with IOMMU enabled

2017-05-30 Thread Zeke Laschinski
I've now tested the patch myself by patching kernel 4.10.0.21.23.
Unfortunately, it does not fix the problem.

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

Title:
  Intel HDMI Audio not working with IOMMU enabled

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  New ASRock Z97 Extreme 6 motherboard with an Intel i7 4790S and an
  Nvidia GTX 650.

  Host uses Intel IGD for video and HDMI audio out.

  When I pass kernel flags 'intel_iommu=on' or 'intel_iommu=on,igfx_on'
  HDMI audio no longer functions although the device and modules seem to
  load and I cannot locate any error messages.  In this configuration
  IOMMU functions as expected and I can successfully pass the Nvidia
  card through to a KVM guest using VFIO.

  As per this
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1223840) bug
  report and the linked bugzilla thread I attempted to use kernel flag
  'intel_iommu=on,igfx_off'.  This resolves the HDMI audio out but
  breaks IOMMU as in VGA pass through generates DMA errors.

  I'm running from a clean installation of 14.10 with no modifications
  to the kernel or kvm, qemu, libvirt or virt-manager.

  In either scenario above the analogue audio out continues to function,
  I haven't tested the optical out as I have no hardware to do so.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-31-generic 3.16.0-31.41
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kelvin 3468 F pulseaudio
   /dev/snd/controlC3:  kelvin 3468 F pulseaudio
   /dev/snd/controlC0:  kelvin 3468 F pulseaudio
   /dev/snd/controlC1:  kelvin 3468 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Mar  4 12:53:17 2015
  HibernationDevice: RESUME=UUID=4d35060a-85c4-45fd-9f8e-530491588931
  InstallationDate: Installed on 2015-02-26 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 
(20141022.2)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic.efi.signed 
root=UUID=4914f227-6bb0-40bb-a781-9ad7111a996f ro intremap=no_x2apic_optout 
intel_iommu=on,forcedac pci-stub.ids=10de:11c8,10de:0e0b nomdmonddf nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-31-generic N/A
   linux-backports-modules-3.16.0-31-generic  N/A
   linux-firmware 1.138.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: Z97 Extreme6
  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.:bvrP1.70:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6: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.

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

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


[Desktop-packages] [Bug 549627] Re: Image containing EXIF orientation does not display properly as wallpaper

2017-05-30 Thread Bug Watch Updater
** Changed in: nautilus
   Status: Confirmed => Fix Released

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

Title:
  Image containing EXIF orientation does not display properly as
  wallpaper

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gnome-control-center

  An image that contains EXIF orientation data displays correctly as a
  thumbnail in gnome-appearance-properties i.e gnome-appearance-
  properties reads the EXIF and rotates the image.  However, when the
  thumbnail is selected and applied as wallpaper the orientation is not
  read and the wallpaper image is displayed with the wrong orientation.

  When bug #278332 (https://bugs.launchpad.net/ubuntu/+source/gnome-
  control-center/+bug/278332) was fixed to show the previews correctly
  is it possible the preview was actually correct as that was what you
  would see if applied ?

  Using Karmic Beta1 upgraded from 9.10.
  gnome-control-center 1:2.29.92-0ubuntu3

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

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


[Desktop-packages] [Bug 1316873] Re: Left mouse button stops working

2017-05-30 Thread Guilden_NL - Joop deBruin
Never had it until a recent Mint Linux Mint 18.1 Serena update.
However.. I installed OpenSuSE KDE Plasma and it exists there.

I dropped kernel version back to 4.4.0-21 and it occurs much less than
with new kernels, if it is of any help.

Note that all mouse debugging tools result in the left click not
recognized, nothing in the logs at all.  All other keys, including mouse
wheel and right click work fine.

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

Title:
  Left mouse button stops working

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  This  problem has plagued me for a few years across different laptops
  and Ubuntu versions. Current I am experiencing this on a Dell Inspiron
  15z running Ubuntu 14.04 LTS.

  It typically starts after I have used the chat or call feature in
  gmail, by clicking on the phone icon in the left chat margin. I am a
  Firefox user and have not tested this with chrome etc. It has not
  happened if i dont install google-talkplugin so it is quite possible
  that the plugin is to blame.

  Symptom
  ===
  The left mouse button on all attached mice - USB , Trackpad and touch - will 
not do anything  however the right mouse button continues to work.  This 
happens to all applications and also to the desktop. The keyboard continues to 
function as normal.

  When this occurs , my solution is to Alt-F4 close all windows and log
  out of the X session. When I re-login the left mouse button works as
  normal.

  
  This is an irritant and work disruptor as I have to save all browser and 
desktop applications to  safe state before I logout to reset the mouse. I will 
appreciate any soltion or workaround.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-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
  CurrentDesktop: Unity
  Date: Tue May  6 21:41:29 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:058f]
  InstallationDate: Installed on 2014-04-17 (19 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 5523
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=f5004b03-b37f-4733-88a8-51c6f3bd0a4d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0GKGJG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/18/2013:svnDellInc.:pnInspiron5523:pvrNotSpecified:rvnDellInc.:rn0GKGJG:rvrA05:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5523
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue May  6 21:20:40 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5558 
   vendor CMN
  xserver.version: 2:1.15.1-0ubuntu2

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

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


[Desktop-packages] [Bug 1694225] Re: [Thinkpad T450s] Click lock effect on trackpoint left button when touchpad is disabled

2017-05-30 Thread Rashi
Found out it's kernel issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1313939#c86

Kernel v4.12 would fix the issue. I hope ubuntu will get the kernel fix
too.


** Bug watch added: Red Hat Bugzilla #1313939
   https://bugzilla.redhat.com/show_bug.cgi?id=1313939

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

Title:
  [Thinkpad T450s] Click lock effect on trackpoint left button when
  touchpad is disabled

Status in xserver-xorg-input-synaptics package in Ubuntu:
  New

Bug description:
  Click lock is a behavior where you do a button click once, the system
  will register the click as "holding the button".

  In laptop Thinkpad T450s I have an issue where the disabled touchpad
  sometimes could trigger the click lock when clicking the trackpoint
  (red pointing stick)'s left button.

  Basically it happens randomly when my palm is touching the touchpad
  while I'm clicking the trackpoint left button.

  But I found a way to make the bug occurs easily:
  1. Disable the touchpad first. You can do this from ubuntu's "Mouse & 
Touchpad" setting.

  2. Put your two fingers on the touchpad (whether your two fingers are
  tapping or pressing the clickpad, it doesn't matter). You could use
  your left hand's index and middle finger for this.

  3. While your left hand's two fingers are on the touchpad, use your
  right hand to click the trackpoint's left button once (don't hold it)
  on the desktop area, then immediately move the cursor with the
  pointing stick.

  4. If the click lock effect gets triggered, you would see you make a
  selection drag on the desktop area. If the click lock doesn't happen,
  repeat again the step 3.

  
  The evtest log on the trackpoint:

  $evtest /dev/input/event15

  Input driver version is 1.0.1
  Input device ID: bus 0x11 vendor 0x2 product 0xa version 0x0
  Input device name: "TPPS/2 IBM TrackPoint"
  Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
  Event code 272 (BTN_LEFT)
  Event code 273 (BTN_RIGHT)
  Event code 274 (BTN_MIDDLE)
Event type 2 (EV_REL)
  Event code 0 (REL_X)
  Event code 1 (REL_Y)
  Properties:
Property type 0 (INPUT_PROP_POINTER)
Property type 5 (INPUT_PROP_POINTING_STICK)
  Testing ... (interrupt to exit)
  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.720823, -- SYN_REPORT 
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
  Event: time 1496047216.778898, -- SYN_REPORT 
  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047220.234518, -- SYN_REPORT 

  
  If the click lock is not triggered, you would see BTN_LEFT's value 1 & 0:

  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0

  But if the click lock is triggered, you would only see value 1:

  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT),
  value 1

  I am guessing "value 0" means release the button. So when click lock
  is happening, the button left is not released at all, thus it's
  producing "hold the button" effect.

  More Informations:
  This issue doesn't happen on other OS like Windows, but I can confirm it 
happens on most modern linux distro and DE I've tried (e.g. ubuntu v17/v16, 
kubuntu, ubuntu mate, xubuntu, lubuntu, linux mint, fedora, open suse, etc). So 
this issue must be coming from the synaptic touchpad driver, or maybe from the 
kernel (?)

  Also, the issue doesn't occur on older thinkpad models which doesn't
  use same clickpad type touchpad, e.g. T430 or X230. For newer thinkpad
  models (e.g. T460, X260, etc) which uses same clickpad design, same
  issue might exists too (need confirmation though).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1694225/+subscriptions

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


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

2017-05-30 Thread Richard
Perhaps this may be a regression?
I'm seeing this in 17-04 Zesty.
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 17.04
Release:17.04
Codename:   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/1694083

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:
  i stuck in ubuntu sofware center for downloading aplication

  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.1
  Architecture: amd64
  Date: Sun May 28 06:28:38 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-23 (4 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/1694083/+subscriptions

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


[Desktop-packages] [Bug 1605798] Re: Unity + Skylake + Hyper-V xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)

2017-05-30 Thread Joseph Salisbury
Thanks for the update, Mark.  Would you say this bug is resolved?

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Unity + Skylake + Hyper-V xf86EnableIOPorts: failed to set IOPL for
  I/O (Operation not permitted)

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Customer using Lenovo P50 (Skylake) and Surface Book (Skylake) laptops
  tried to start unity in a guest VM on Hyper-V. Kernel 4.4.0-31 started
  as expected, Hyper-V drivers loaded as expected including the
  framebuffer driver, plenty of memory and vCPUs allocated, but x.org
  fails with xf86EnableIOPorts: failed to set IOPL for I/O (Operation
  not permitted), resulting in "no screens found".

  However, when customer used KDE (kubuntu 16.04 with similar kernel) on
  these same systems got a UI as expected. Customer also has no issues
  on non-skylake laptop.

  No unexpected messages seen in dmesg and syslog.

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

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


[Desktop-packages] [Bug 1694472] [NEW] /usr/bin/remmina:11:freerdp_channels_find_by_open_handle:FreeRDP_VirtualChannelWrite:svc_plugin_send:cliprdr_packet_send:cliprdr_process_event

2017-05-30 Thread errors.ubuntu.com bug bridge
Public bug reported:

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

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


** Tags: vivid xenial yakkety

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

Title:
  
/usr/bin/remmina:11:freerdp_channels_find_by_open_handle:FreeRDP_VirtualChannelWrite:svc_plugin_send:cliprdr_packet_send:cliprdr_process_event

Status in remmina package in Ubuntu:
  New

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

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

-- 
Mailing list: https://launchpad.net/~desktop-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-30 Thread redman
Same problem here:

Google-chrome is affected.
Skypeforlinux doesn't remember the password anymore
UnityMail is affected

-- 
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
Status in libgnome-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 1694457] [NEW] Unable to Open Files With Totem After Upgrade to 17.04

2017-05-30 Thread Plamen
Public bug reported:

I can't open .mkv and .mp3 files with Totem. This behavior appeared after 
upgrade to 17.04.
After I double click a file a loading indication in the title bar appears. 
After a few seconds it simply disappears and the player is not showing.

If I start a Terminal and type "totem " the file is opened
normally.


>> lsb_release -rd
Description:Ubuntu 17.04
Release:17.04

>> apt-cache policy totem
totem:
  Installed: 3.24.0-0ubuntu1
  Candidate: 3.24.0-0ubuntu1
  Version table:
 *** 3.24.0-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: libgstreamer1.0-0 1.10.4-1
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue May 30 17:33:05 2017
InstallationDate: Installed on 2015-06-17 (713 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: gstreamer1.0
UpgradeStatus: Upgraded to zesty on 2017-04-17 (42 days ago)

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

Title:
  Unable to Open Files With Totem After Upgrade to 17.04

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  I can't open .mkv and .mp3 files with Totem. This behavior appeared after 
upgrade to 17.04.
  After I double click a file a loading indication in the title bar appears. 
After a few seconds it simply disappears and the player is not showing.

  If I start a Terminal and type "totem " the file is
  opened normally.

  
  >> lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  >> apt-cache policy totem
  totem:
Installed: 3.24.0-0ubuntu1
Candidate: 3.24.0-0ubuntu1
Version table:
   *** 3.24.0-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libgstreamer1.0-0 1.10.4-1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue May 30 17:33:05 2017
  InstallationDate: Installed on 2015-06-17 (713 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: gstreamer1.0
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (42 days ago)

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

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


[Desktop-packages] [Bug 1694454] [NEW] Can't open gnome terminal

2017-05-30 Thread Plamen
Public bug reported:

Selecting gnome terminal after search(winkey->type "term"->select
Terminal), results in loading terminal for a few seconds and simply
disappearing of the loading indication from the title bar.

Nothing else happens. No error and no terminal shown.

This behavior appeared after upgrade to 17.04
I don't have such a problem when opening MATE Terminal.
Also when I run "gnome-terminal" in the mate terminal it outputs this:
"Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: 
Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached"


>> lsb_release -rd

Description:Ubuntu 17.04
Release:17.04


>> apt-cache policy gnome-terminal 

gnome-terminal:
  Installed: 3.20.2-1ubuntu8
  Candidate: 3.20.2-1ubuntu8
  Version table:
 *** 3.20.2-1ubuntu8 500
500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-terminal 3.20.2-1ubuntu8
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue May 30 17:15:09 2017
InstallationDate: Installed on 2015-06-17 (713 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: gnome-terminal
UpgradeStatus: Upgraded to zesty on 2017-04-17 (42 days ago)

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

Title:
  Can't open gnome terminal

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Selecting gnome terminal after search(winkey->type "term"->select
  Terminal), results in loading terminal for a few seconds and simply
  disappearing of the loading indication from the title bar.

  Nothing else happens. No error and no terminal shown.

  This behavior appeared after upgrade to 17.04
  I don't have such a problem when opening MATE Terminal.
  Also when I run "gnome-terminal" in the mate terminal it outputs this:
  "Error constructing proxy for 
org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling 
StartServiceByName for org.gnome.Terminal: Timeout was reached"


  >> lsb_release -rd

  Description:  Ubuntu 17.04
  Release:  17.04

  
  >> apt-cache policy gnome-terminal 

  gnome-terminal:
Installed: 3.20.2-1ubuntu8
Candidate: 3.20.2-1ubuntu8
Version table:
   *** 3.20.2-1ubuntu8 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-terminal 3.20.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue May 30 17:15:09 2017
  InstallationDate: Installed on 2015-06-17 (713 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (42 days ago)

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

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


[Desktop-packages] [Bug 1670036] Re: Misapplied patches in 4.0.6-2ubuntu0.1 break reading and writing JPEG compressed files

2017-05-30 Thread Launchpad Bug Tracker
This bug was fixed in the package tiff - 4.0.3-7ubuntu0.7

---
tiff (4.0.3-7ubuntu0.7) trusty-security; urgency=medium

  * SECURITY REGRESSION: JPEG tiff read and write issue due to misapplied
patches (LP: #1670036)
- debian/patches/CVE-2016-9297_and_CVE-2016-9448_correct.patch: replace
  two previous patches with one that applies fix to correct location.
- Thanks to John Cupitt and Even Rouault

 -- Marc Deslauriers   Mon, 29 May 2017
07:35:17 -0400

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

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

Title:
  Misapplied patches in 4.0.6-2ubuntu0.1 break reading and writing JPEG
  compressed files

Status in LibTIFF:
  New
Status in tiff package in Ubuntu:
  Invalid
Status in tiff source package in Trusty:
  Fix Released
Status in tiff source package in Xenial:
  Fix Released
Status in tiff source package in Yakkety:
  Fix Released

Bug description:
  The patches applied to libtiff 4.0.6 in 4.0.6-2ubuntu01 seem to break
  JPEG tiff read and write.

  To reproduce:

  $ tiffcp -c jpeg k2a.tif x.tif

  (where k2a.tif is a simple uncompressed RGB strip tiff) appears to
  work. However, x.tif, the output, will now not read without warnings:

  $ tiffcp x.tif y.tif
  TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in 
null byte. Forcing it to be null.
  JPEGLib: Warning, Premature end of JPEG file.

  This was working fine until a couple of days ago, so I guess it's one
  of the most recent patches.

  Some packages using libtiff seem to be broken too. For example,
  openslide, which uses libtiff to load jp2k-compressed slide images, is
  no longer working:

  $ openslide-write-png CMU-1-Small-Region.svs 0 0 0 100 100 x.png
  TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in 
null byte. Forcing it to be null.
  TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in 
null byte. Forcing it ... repeats 8 more times
  openslide-write-png: Premature end of JPEG file

  and x.png is not a valid PNG image.  The test .svs image may be
  downloaded here:

  http://openslide.cs.cmu.edu/download/openslide-testdata/Aperio/

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

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


[Desktop-packages] [Bug 1670036] Re: Misapplied patches in 4.0.6-2ubuntu0.1 break reading and writing JPEG compressed files

2017-05-30 Thread Launchpad Bug Tracker
This bug was fixed in the package tiff - 4.0.6-2ubuntu0.2

---
tiff (4.0.6-2ubuntu0.2) yakkety-security; urgency=medium

  * SECURITY REGRESSION: JPEG tiff read and write issue due to misapplied
patches (LP: #1670036)
- debian/patches/CVE-2016-9297_and_CVE-2016-9448_correct.patch: replace
  two previous patches with one that applies fix to correct location.
- Thanks to John Cupitt and Even Rouault

 -- Marc Deslauriers   Mon, 29 May 2017
07:29:06 -0400

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

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

Title:
  Misapplied patches in 4.0.6-2ubuntu0.1 break reading and writing JPEG
  compressed files

Status in LibTIFF:
  New
Status in tiff package in Ubuntu:
  Invalid
Status in tiff source package in Trusty:
  Fix Released
Status in tiff source package in Xenial:
  Fix Released
Status in tiff source package in Yakkety:
  Fix Released

Bug description:
  The patches applied to libtiff 4.0.6 in 4.0.6-2ubuntu01 seem to break
  JPEG tiff read and write.

  To reproduce:

  $ tiffcp -c jpeg k2a.tif x.tif

  (where k2a.tif is a simple uncompressed RGB strip tiff) appears to
  work. However, x.tif, the output, will now not read without warnings:

  $ tiffcp x.tif y.tif
  TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in 
null byte. Forcing it to be null.
  JPEGLib: Warning, Premature end of JPEG file.

  This was working fine until a couple of days ago, so I guess it's one
  of the most recent patches.

  Some packages using libtiff seem to be broken too. For example,
  openslide, which uses libtiff to load jp2k-compressed slide images, is
  no longer working:

  $ openslide-write-png CMU-1-Small-Region.svs 0 0 0 100 100 x.png
  TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in 
null byte. Forcing it to be null.
  TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in 
null byte. Forcing it ... repeats 8 more times
  openslide-write-png: Premature end of JPEG file

  and x.png is not a valid PNG image.  The test .svs image may be
  downloaded here:

  http://openslide.cs.cmu.edu/download/openslide-testdata/Aperio/

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

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


[Desktop-packages] [Bug 1670036] Re: Misapplied patches in 4.0.6-2ubuntu0.1 break reading and writing JPEG compressed files

2017-05-30 Thread Launchpad Bug Tracker
This bug was fixed in the package tiff - 4.0.6-1ubuntu0.2

---
tiff (4.0.6-1ubuntu0.2) xenial-security; urgency=medium

  * SECURITY REGRESSION: JPEG tiff read and write issue due to misapplied
patches (LP: #1670036)
- debian/patches/CVE-2016-9297_and_CVE-2016-9448_correct.patch: replace
  two previous patches with one that applies fix to correct location.
- Thanks to John Cupitt and Even Rouault

 -- Marc Deslauriers   Mon, 29 May 2017
07:33:56 -0400

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

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

Title:
  Misapplied patches in 4.0.6-2ubuntu0.1 break reading and writing JPEG
  compressed files

Status in LibTIFF:
  New
Status in tiff package in Ubuntu:
  Invalid
Status in tiff source package in Trusty:
  Confirmed
Status in tiff source package in Xenial:
  Fix Released
Status in tiff source package in Yakkety:
  Confirmed

Bug description:
  The patches applied to libtiff 4.0.6 in 4.0.6-2ubuntu01 seem to break
  JPEG tiff read and write.

  To reproduce:

  $ tiffcp -c jpeg k2a.tif x.tif

  (where k2a.tif is a simple uncompressed RGB strip tiff) appears to
  work. However, x.tif, the output, will now not read without warnings:

  $ tiffcp x.tif y.tif
  TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in 
null byte. Forcing it to be null.
  JPEGLib: Warning, Premature end of JPEG file.

  This was working fine until a couple of days ago, so I guess it's one
  of the most recent patches.

  Some packages using libtiff seem to be broken too. For example,
  openslide, which uses libtiff to load jp2k-compressed slide images, is
  no longer working:

  $ openslide-write-png CMU-1-Small-Region.svs 0 0 0 100 100 x.png
  TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in 
null byte. Forcing it to be null.
  TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in 
null byte. Forcing it ... repeats 8 more times
  openslide-write-png: Premature end of JPEG file

  and x.png is not a valid PNG image.  The test .svs image may be
  downloaded here:

  http://openslide.cs.cmu.edu/download/openslide-testdata/Aperio/

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

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


[Desktop-packages] [Bug 1627808] Re: Please enable e10s (multi-core CPU processing) support

2017-05-30 Thread Shih-Yuan Lee
Hi, I just made an unsigned ubufox xpi to fix the problem.
Would you like to follow 
https://support.mozilla.org/en-US/kb/add-on-signing-in-firefox to manually 
install this xpi to see if there is any regression?

** Attachment added: "ubufox.xpi"
   
https://bugs.launchpad.net/ubuntu/+source/ubufox/+bug/1627808/+attachment/4886187/+files/ubufox.xpi

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

Title:
  Please enable e10s (multi-core CPU processing) support

Status in Ubufox Extension:
  Confirmed
Status in Ubuntu:
  Confirmed
Status in ubufox package in Ubuntu:
  Confirmed

Bug description:
  Would it be possible to determine whether this add-on is compatible
  with the e10s "electrolysis" feature of Firefox[1]?

  If it is, the manifest should say so: [2]

  This link may help when determining support: [3]

  Compatibility of this addon with e10s is required to enable the e10s
  feature, which brings many speedups and enhancements, on default
  configured ubuntu installations.

  Thank you!

  [1]: https://wiki.mozilla.org/Electrolysis
  [2]: 
https://developer.mozilla.org/en-US/Add-ons/Install_Manifests#multiprocessCompatible
  [3]: 
https://developer.mozilla.org/en-US/Add-ons/Working_with_multiprocess_Firefox

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

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


[Desktop-packages] [Bug 1694425] Re: performance critical libyuv built with Os

2017-05-30 Thread Bug Watch Updater
** Changed in: firefox (Debian)
   Importance: Undecided => Unknown

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

Title:
  performance critical libyuv built with Os

Status in firefox package in Ubuntu:
  New
Status in firefox package in Debian:
  New

Bug description:
  Imported from Debian bug http://bugs.debian.org/863672:

  This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
  --aN5BOcfPQ1wkI3kOWF0Bpe7cmio8VfIEp
  Content-Type: multipart/mixed; boundary="SrbvOHijIbL538GHuOsAk6jhGEBxW5ENR";
   protected-headers="v1"
  From: Julian Taylor 
  To: Debian Bug Tracking System 
  Message-ID: <009ef781-1692-0d59-4b28-1742166ba...@googlemail.com>
  Subject: performance critical libyuv built with Os

  --SrbvOHijIbL538GHuOsAk6jhGEBxW5ENR
  Content-Type: text/plain; charset=utf-8
  Content-Language: en-GB
  Content-Transfer-Encoding: quoted-printable

  Package: firefox
  Version:  53.0.is.52.0.2-1
  Severity: normal

  
  libyuv which is a performance critical library for firefix is built with
  -Os which is horrible for performance for it.
  In particular row_common.cc which contains the generic parts of the
  color transformation code:

  See:
  https://buildd.debian.org/status/fetch.php?pkg=3Dfirefox=3Damd64=
  =3D53.0.is.52.0.2-1=3D1492644908=3D0

  /usr/bin/g++ -std=3Dgnu++11 -o row_common.o -c  ...   -fPIC
  -DMOZILLA_CLIENT -include
  /PKGBUILDDIR/build-browser/mozilla-config.h -MD -MP -MF
  =2Edeps/row_common.o.pp -Wdate-time -D_FORTIFY_SOURCE=3D2 -Wall
  -Wc++11-compat -Wempty-body -Wignored-qualifiers -Woverloaded-virtual
  -Wpointer-arith -Wsign-compare -Wtype-limits -Wunreachable-code
  -Wwrite-strings -Wno-invalid-offsetof -Wc++14-compat
  -Wno-error=3Dmaybe-uninitialized -Wno-error=3Ddeprecated-declarations
  -Wno-error=3Darray-bounds -fno-lifetime-dse -fstack-protector-strong
  -Wformat -Werror=3Dformat-security -fno-schedule-insns2 -fno-lifetime-dse=

  -fno-delete-null-pointer-checks -fno-exceptions -fno-strict-aliasing
  -fno-rtti -ffunction-sections -fdata-sections -fno-exceptions
  -fno-math-errno -pthread -pipe  -g -freorder-blocks -Os
  -fomit-frame-pointer
  /PKGBUILDDIR/media/libyuv/source/row_common.cc

  
  The problematic part is the YuvPixel function which is called in loops
  and in turn calls tiny clamp functions.
  Os disables inlining so this causes massive overhead.
  This is the top cpu profile on sites which e.g. display videos.
17.25%  libxul.so   [.] YuvPixel=E2=96=92
 6.58%  libxul.so   [.] Clamp   =E2=96=92
 6.46%  libxul.so   [.] clamp255

  The problem is not as bad as it looks as this generic code is only
  executed on machines that do not have SSSE3, AVX2 or NEON (see
  convert_argb.cc)
  But there are still plenty useful cpus that do not have these
  instruction sets and are crippled by the compiler flags used.

  Is it possible to compile this library with O3 to allow the compiler to
  vectorize it with the best available generic instruction set (e.g. SSE2
  on x64).

  cheers,
  Julian Taylor

  
  --SrbvOHijIbL538GHuOsAk6jhGEBxW5ENR--

  --aN5BOcfPQ1wkI3kOWF0Bpe7cmio8VfIEp
  Content-Type: application/pgp-signature; name="signature.asc"
  Content-Description: OpenPGP digital signature
  Content-Disposition: attachment; filename="signature.asc"

  -BEGIN PGP SIGNATURE-

  iQI7BAEBCAAlBQJZLI9HHhxqdGF5bG9yLmRlYmlhbkBnb29nbGVtYWlsLmNvbQAK
  CRAyzEqsAodW/yfHD/0ZBE3JGMGPM/yD3HNR4EslXMGKHxoT6JowG5TWI9UHy+5U
  utj6vgrZ3hDEefGbI+UCDPehDK8tAlSTCI/wFxuqOO4+AB7EQia4bA2Agt7f3xfV
  Y458uBPG860j7AEhgAtLHGN5TAZUwN5jegXj12qBtR1wCrk5gBCRDC6+wy+cqiE6
  tApXdeM+3XsdYBS7udezJkw6NyhzMhiRebEwnB9wpztBIz/GSDxaftF0zLmrN4b8
  CYNVPH426/YAbDkzzAphKJnlcLoELxeU42xVd2G34rPA8NoDbuw2J3ZV4oIGi+/v
  S2XZsLkmcxFRb8JndfuayQtuGyMziPs4W2QDn3sZsh350hg77+V9/hYosxfnQc5d
  Eetuu4rX4dGLdGFmq2fkrsB08G37Z6kl31B1TtvenZ2ejSGWoxc1gkHVmFfSDmCk
  nfzuM5m+T518+7WZJ1HbEzI3ISQz1KtrKRPHLQi73N0qMRk6JZe4u3FVAOdxJYx9
  QYqEKYaGLVMa3A3Nuwtn3QI4bXC3OoJSdHEl5wxDUV/zvruAsFhWYKl9QjqNo8Zn
  2UWbr/hd3+2Lv/vVJLBr41AISi/6Ybs47FnloIqvEMlQDxlf1d4e2fLoqmal0oFv
  QT3mIXWjBmf0f52tsYSRGNw4OiYPx/6iaMET9WhQm8K5lKSTgkjv04s9cad90A==
  =P1R4
  -END PGP SIGNATURE-

  --aN5BOcfPQ1wkI3kOWF0Bpe7cmio8VfIEp--

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

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


[Desktop-packages] [Bug 1694331] Re: "internal error" popup on login

2017-05-30 Thread Andreas Fritiofson
Christopher, I have since upgraded that Dell Precision to 17.04 and
while I still often get the error popup on that computer I cannot
confirm that it is actually Xorg that crashed, because now that I
looked, the crash popup on 17.04 today was about some unrelated software
(unity-settings-something) so I can't really be sure if I have ever seen
Xorg crash on 17.04. It used to be Xorg when the Dell computer had
16.10, though.

The UX32VD that still runs 16.10 continues to show the Xorg crash from
time to time (but not nearly at every boot).

Also I checked with my co-workers and those (2) who run 16.10 all
regularly see an error popup but none can verify that it's still
actually about Xorg (it happens frequently enough that no-one bothers to
look anymore). A co-worker who's still on 16.04 says he hasn't seen the
error.

So in summary I can only definitely say that 16.10 shows that Xorg crash
and that it has happened on more or less every computer I or my co-
workers have used with 16.10.

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

Title:
  "internal error" popup on login

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes (not very often), Ubuntu shows an error popup immediately
  after login (after power-on) that says Xorg has crashed. No other ill
  effects have been noticed, everything works normally after that.

  The automatic error reporting does not go through because of
  "UnreportableReason: Invalid core dump: BFD: Warning
  /tmp/apport_core_5n7s8i3d is truncated: expected core file size >=
  40902656, found: 21037056."

  I was asked by Christopher M. Penalver in Bug 1426596 to submit a new
  bug using "ubuntu-bug xorg" when the error appeared. This is that
  report, although the computer I used now to generate the report is not
  the same as I mentioned in the original bug (I've seen the same issue
  on more or less all computers I've used and IIRC from at least 16.04
  to 17.04).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-53.56-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.3
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon May 29 22:31:18 2017
  DistUpgraded: 2017-04-15 01:32:04,429 DEBUG /openCache(), new cache size 85680
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-52-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:1507]
  InstallationDate: Installed on 2014-04-18 (1137 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-53-generic.efi.signed 
root=UUID=959fa127-2d15-48a5-9fa0-70f918fab2ad ro rootflags=subvol=@ quiet 
splash pcie_aspm=force nmi_watchdog=0 vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to yakkety on 2017-04-14 (44 days ago)
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.10.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 

[Desktop-packages] [Bug 1627808] Re: Please enable e10s (multi-core CPU processing) support

2017-05-30 Thread Launchpad Bug Tracker
** Branch linked: lp:~fourdollars/ubufox/trunk

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

Title:
  Please enable e10s (multi-core CPU processing) support

Status in Ubufox Extension:
  Confirmed
Status in Ubuntu:
  Confirmed
Status in ubufox package in Ubuntu:
  Confirmed

Bug description:
  Would it be possible to determine whether this add-on is compatible
  with the e10s "electrolysis" feature of Firefox[1]?

  If it is, the manifest should say so: [2]

  This link may help when determining support: [3]

  Compatibility of this addon with e10s is required to enable the e10s
  feature, which brings many speedups and enhancements, on default
  configured ubuntu installations.

  Thank you!

  [1]: https://wiki.mozilla.org/Electrolysis
  [2]: 
https://developer.mozilla.org/en-US/Add-ons/Install_Manifests#multiprocessCompatible
  [3]: 
https://developer.mozilla.org/en-US/Add-ons/Working_with_multiprocess_Firefox

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

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


[Desktop-packages] [Bug 1694425] [NEW] performance critical libyuv built with Os

2017-05-30 Thread Julian Taylor
Public bug reported:

Imported from Debian bug http://bugs.debian.org/863672:

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--aN5BOcfPQ1wkI3kOWF0Bpe7cmio8VfIEp
Content-Type: multipart/mixed; boundary="SrbvOHijIbL538GHuOsAk6jhGEBxW5ENR";
 protected-headers="v1"
From: Julian Taylor 
To: Debian Bug Tracking System 
Message-ID: <009ef781-1692-0d59-4b28-1742166ba...@googlemail.com>
Subject: performance critical libyuv built with Os

--SrbvOHijIbL538GHuOsAk6jhGEBxW5ENR
Content-Type: text/plain; charset=utf-8
Content-Language: en-GB
Content-Transfer-Encoding: quoted-printable

Package: firefox
Version:  53.0.is.52.0.2-1
Severity: normal


libyuv which is a performance critical library for firefix is built with
-Os which is horrible for performance for it.
In particular row_common.cc which contains the generic parts of the
color transformation code:

See:
https://buildd.debian.org/status/fetch.php?pkg=3Dfirefox=3Damd64=
=3D53.0.is.52.0.2-1=3D1492644908=3D0

/usr/bin/g++ -std=3Dgnu++11 -o row_common.o -c  ...   -fPIC
-DMOZILLA_CLIENT -include
/PKGBUILDDIR/build-browser/mozilla-config.h -MD -MP -MF
=2Edeps/row_common.o.pp -Wdate-time -D_FORTIFY_SOURCE=3D2 -Wall
-Wc++11-compat -Wempty-body -Wignored-qualifiers -Woverloaded-virtual
-Wpointer-arith -Wsign-compare -Wtype-limits -Wunreachable-code
-Wwrite-strings -Wno-invalid-offsetof -Wc++14-compat
-Wno-error=3Dmaybe-uninitialized -Wno-error=3Ddeprecated-declarations
-Wno-error=3Darray-bounds -fno-lifetime-dse -fstack-protector-strong
-Wformat -Werror=3Dformat-security -fno-schedule-insns2 -fno-lifetime-dse=

-fno-delete-null-pointer-checks -fno-exceptions -fno-strict-aliasing
-fno-rtti -ffunction-sections -fdata-sections -fno-exceptions
-fno-math-errno -pthread -pipe  -g -freorder-blocks -Os
-fomit-frame-pointer
/PKGBUILDDIR/media/libyuv/source/row_common.cc


The problematic part is the YuvPixel function which is called in loops
and in turn calls tiny clamp functions.
Os disables inlining so this causes massive overhead.
This is the top cpu profile on sites which e.g. display videos.
  17.25%  libxul.so   [.] YuvPixel=E2=96=92
   6.58%  libxul.so   [.] Clamp   =E2=96=92
   6.46%  libxul.so   [.] clamp255

The problem is not as bad as it looks as this generic code is only
executed on machines that do not have SSSE3, AVX2 or NEON (see
convert_argb.cc)
But there are still plenty useful cpus that do not have these
instruction sets and are crippled by the compiler flags used.

Is it possible to compile this library with O3 to allow the compiler to
vectorize it with the best available generic instruction set (e.g. SSE2
on x64).

cheers,
Julian Taylor


--SrbvOHijIbL538GHuOsAk6jhGEBxW5ENR--

--aN5BOcfPQ1wkI3kOWF0Bpe7cmio8VfIEp
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-BEGIN PGP SIGNATURE-

iQI7BAEBCAAlBQJZLI9HHhxqdGF5bG9yLmRlYmlhbkBnb29nbGVtYWlsLmNvbQAK
CRAyzEqsAodW/yfHD/0ZBE3JGMGPM/yD3HNR4EslXMGKHxoT6JowG5TWI9UHy+5U
utj6vgrZ3hDEefGbI+UCDPehDK8tAlSTCI/wFxuqOO4+AB7EQia4bA2Agt7f3xfV
Y458uBPG860j7AEhgAtLHGN5TAZUwN5jegXj12qBtR1wCrk5gBCRDC6+wy+cqiE6
tApXdeM+3XsdYBS7udezJkw6NyhzMhiRebEwnB9wpztBIz/GSDxaftF0zLmrN4b8
CYNVPH426/YAbDkzzAphKJnlcLoELxeU42xVd2G34rPA8NoDbuw2J3ZV4oIGi+/v
S2XZsLkmcxFRb8JndfuayQtuGyMziPs4W2QDn3sZsh350hg77+V9/hYosxfnQc5d
Eetuu4rX4dGLdGFmq2fkrsB08G37Z6kl31B1TtvenZ2ejSGWoxc1gkHVmFfSDmCk
nfzuM5m+T518+7WZJ1HbEzI3ISQz1KtrKRPHLQi73N0qMRk6JZe4u3FVAOdxJYx9
QYqEKYaGLVMa3A3Nuwtn3QI4bXC3OoJSdHEl5wxDUV/zvruAsFhWYKl9QjqNo8Zn
2UWbr/hd3+2Lv/vVJLBr41AISi/6Ybs47FnloIqvEMlQDxlf1d4e2fLoqmal0oFv
QT3mIXWjBmf0f52tsYSRGNw4OiYPx/6iaMET9WhQm8K5lKSTgkjv04s9cad90A==
=P1R4
-END PGP SIGNATURE-

--aN5BOcfPQ1wkI3kOWF0Bpe7cmio8VfIEp--

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

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

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

** Changed in: firefox (Debian)
 Remote watch: None => Debian Bug tracker #863672

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

Title:
  performance critical libyuv built with Os

Status in firefox package in Ubuntu:
  New
Status in firefox package in Debian:
  New

Bug description:
  Imported from Debian bug http://bugs.debian.org/863672:

  This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
  --aN5BOcfPQ1wkI3kOWF0Bpe7cmio8VfIEp
  Content-Type: multipart/mixed; boundary="SrbvOHijIbL538GHuOsAk6jhGEBxW5ENR";
   protected-headers="v1"
  From: Julian Taylor 
  To: Debian Bug Tracking System 
  Message-ID: 

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

2017-05-30 Thread Zhanglei Mao
For the mainline kernel (general kernel from Ubuntu 16.04.02 AM64) was
not tested in case we are not supported for Hisilicon D05 board.

We also do some basic fbdev and modesetting testing on this kerenl by
pass Xserver, it seems works well and so we tend to think this is caused
by Xorg or driver of Xorg.

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

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

Status in xorg package in Ubuntu:
  New

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

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

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

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


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

2017-05-30 Thread Zhanglei Mao
The below is testing after remove of "xserver-xorg-video-fbdev package"

ubuntu@ubuntu:/usr/lib/xorg/modules/drivers$ sudo /usr/lib/xorg/Xorg

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

ubuntu@ubuntu:/usr/lib/xorg/modules/drivers$ less /var/log/Xorg.0.log
[1029553.709] 
X.Org X Server 1.18.4
Release Date: 2016-07-19
[1029553.709] X Protocol Version 11, Revision 0
[1029553.709] Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
[1029553.709] Current Operating System: Linux ubuntu 4.10.0-20.22-generic 
#22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
[1029553.709] Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic 
root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug 
earlycon=pl011,mmio,0x602B console=tty0
[1029553.709] Build Date: 02 November 2016  10:05:28PM
[1029553.709] xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see 
http://www.ubuntu.com/support) 
[1029553.709] Current version of pixman: 0.33.6
[1029553.709]   Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[1029553.709] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[1029553.709] (==) Log file: "/var/log/Xorg.0.log", Time: Tue May 30 17:45:40 
2017
[1029553.709] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[1029553.710] (==) No Layout section.  Using the first Screen section.
[1029553.710] (==) No screen section available. Using defaults.
[1029553.710] (**) |-->Screen "Default Screen Section" (0)
[1029553.710] (**) |   |-->Monitor ""
[1029553.710] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[1029553.710] (==) Automatically adding devices
[1029553.710] (==) Automatically enabling devices
[1029553.710] (==) Automatically adding GPU devices
[1029553.710] (==) Max clients allowed: 256, resource mask: 0x1f
[1029553.710] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[1029553.710]   Entry deleted from font path.
[1029553.710] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[1029553.710]   Entry deleted from font path.
[1029553.710] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[1029553.710]   Entry deleted from font path.
[1029553.710] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[1029553.710]   Entry deleted from font path.
[1029553.710] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[1029553.710]   Entry deleted from font path.
[1029553.710] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/Type1,
built-ins
les,/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules"
s.
es.
[1029553.710] (II) Loader magic: 0xb1d99d80
[1029553.710] (II) Module ABI versions:
[1029553.710]   X.Org ANSI C Emulation: 0.4
[1029553.710]   X.Org Video Driver: 20.0
[1029553.710]   X.Org XInput driver : 22.1
[1029553.710]   X.Org Server Extension : 9.0
[1029553.711] (--) using VT number 3

ptty was not provided, disabling logind integration
[1029553.712] (II) xfree86: Adding drm device (/dev/dri/card0)
/33554432, 0x8ab00/2097152
[1029553.713] (II) LoadModule: "glx"
[1029553.713] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[1029553.714] (II) Module glx: vendor="X.Org Foundation"
[1029553.714]   compiled for 1.18.4, module version = 1.0.0
[1029553.714]   ABI class: X.Org Server Extension, version 9.0
[1029553.714] (==) AIGLX enabled

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

2017-05-30 Thread Daniel Axtens
Hi,

What happens if you remove the fb driver - uninstall the xserver-xorg-
video-fbdev package?

Also, I'm not sure what (if any) changes have been made in the kernel
version you're running - the 'pearl' version - but are you able to try
against a mainline kernel?

Regards,
Daniel

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

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

Status in xorg package in Ubuntu:
  New

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

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

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

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


[Desktop-packages] [Bug 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized

2017-05-30 Thread Daniel van Vugt
I suggest looking at the bugs tagged 'a2dp':

https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bugs?field.tag=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/1577197

Title:
  Pulseaudio bluez5-util.c: TryAcquire() failed  - Operation Not
  Authorized

Status in bluez package in Ubuntu:
  Incomplete
Status in indicator-sound package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period 
of time. Only restart fixes the issue. This started early 2016 in 15.10.
  Issue is discussed here as well 
http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04
 and mentioned in other unrelated bugs.

  Ubuntu Xenial 16.04 LTS

  The log below:

  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] 
module-bluez5-device.c: Default profile not connected, selecting off profile
  May  1 17:18:07 jalexoidmobile bluetoothd[7349]: 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 
10967 of process 2884 (n/a) owned by '1000' RT at priority 5.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: 
Transport TryAcquire() failed for transport 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized)
  May  1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 
00:02:3C:05:99:F2 as /devices/virtual/input/input24
  May  1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.


  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s 
camera
  Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 
[ThinkPad]
  Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF 
advanced mode)
  Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6
  [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [20389.070122] usb 1-1.4: Product: BCM20702A0
  [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp
  [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD
  [20389.076232] Bluetooth: hci0: BCM: chip id 63
  [20389.092220] Bluetooth: hci0: BCM20702A
  [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed
  [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3)
  [20389.557790] wlan0: authenticated
  [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3)
  [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 
status=0 aid=2)
  [20389.581260] wlan0: associated
  [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669
  [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device
  [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23
  [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24

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

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


[Desktop-packages] [Bug 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized

2017-05-30 Thread Frandeboeuf Nicolas
I am sorry, I just checked by launching "tail -f /var/log/syslog" and
then switching on my bluetooth headset, here is what appears:


May 30 08:15:21 desktop pulseaudio[1504]: [pulseaudio] module-bluez5-device.c: 
Default profile not connected, selecting off profile

So I guess I have another issue. I know this is not the place, but if
you happen to know where I should start looking for, I have no idea…

Thanks

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

Title:
  Pulseaudio bluez5-util.c: TryAcquire() failed  - Operation Not
  Authorized

Status in bluez package in Ubuntu:
  Incomplete
Status in indicator-sound package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period 
of time. Only restart fixes the issue. This started early 2016 in 15.10.
  Issue is discussed here as well 
http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04
 and mentioned in other unrelated bugs.

  Ubuntu Xenial 16.04 LTS

  The log below:

  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] 
module-bluez5-device.c: Default profile not connected, selecting off profile
  May  1 17:18:07 jalexoidmobile bluetoothd[7349]: 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 
10967 of process 2884 (n/a) owned by '1000' RT at priority 5.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: 
Transport TryAcquire() failed for transport 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized)
  May  1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 
00:02:3C:05:99:F2 as /devices/virtual/input/input24
  May  1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.


  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s 
camera
  Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 
[ThinkPad]
  Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF 
advanced mode)
  Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6
  [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [20389.070122] usb 1-1.4: Product: BCM20702A0
  [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp
  [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD
  [20389.076232] Bluetooth: hci0: BCM: chip id 63
  [20389.092220] Bluetooth: hci0: BCM20702A
  [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed
  [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3)
  [20389.557790] wlan0: authenticated
  [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3)
  [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 
status=0 aid=2)
  [20389.581260] wlan0: associated
  [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669
  [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device
  [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23
  [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24

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

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


[Desktop-packages] [Bug 1694379] [NEW] Crash with multi-screen

2017-05-30 Thread Manuel
Public bug reported:

XORG crash if I plug a second screen with the DVI input on my laptop.

The bug appear after a recent update of Ubuntu 16.04

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
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:02:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  364.19  Tue Apr 19 14:44:55 
PDT 2016
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue May 30 08:25:47 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:221d]
 NVIDIA Corporation GK208M [GeForce GT 730M] [10de:1290] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo GK208M [GeForce GT 730M] [17aa:221d]
InstallationDate: Installed on 2016-06-20 (343 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: LENOVO 20AWS5H500
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=3598049e-4f06-494b-82cc-d5a007b0e461 ro quiet splash "acpi=Windows 
2013" vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/19/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: GLET82WW (2.36 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AWS5H500
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGLET82WW(2.36):bd01/19/2016:svnLENOVO:pn20AWS5H500:pvrThinkPadT440p:rvnLENOVO:rn20AWS5H500:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20AWS5H500
dmi.product.version: ThinkPad T440p
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue May 30 08:18:29 2017
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu 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/1694379

Title:
  Crash with multi-screen

Status in xorg package in Ubuntu:
  New

Bug description:
  XORG crash if I plug a second screen with the DVI input on my laptop.

  The bug appear after a recent update of Ubuntu 16.04

  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
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  364.19  Tue Apr 19 14:44:55 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue May 30 08:25:47 2017
  DistUpgraded: Fresh install
  

[Desktop-packages] [Bug 1694367] [NEW] Screen tearing in 16.10 onwards

2017-05-30 Thread Paul
Public bug reported:

In 16.10 onwards my laptop has always shown screen tearing globally,
additionally GL applications will not v-sync despite attempting to, they
appear to sync slightly off from the [integrated] display.

This occurs with kernels 4.8 to 4.11 and mesa 12 to 17, so not entirely
sure if it's a bug with either or a default miss-configuration in
ubuntu...

ubuntu-bug also appears to be broken...

** Affects: kernel-package (Ubuntu)
 Importance: Undecided
 Status: New

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

** Also affects: kernel-package (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Screen tearing in 16.10 onwards

Status in kernel-package package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  In 16.10 onwards my laptop has always shown screen tearing globally,
  additionally GL applications will not v-sync despite attempting to,
  they appear to sync slightly off from the [integrated] display.

  This occurs with kernels 4.8 to 4.11 and mesa 12 to 17, so not
  entirely sure if it's a bug with either or a default miss-
  configuration in ubuntu...

  ubuntu-bug also appears to be broken...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1694367/+subscriptions

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