date:20161220

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

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

Title:
  Black screen at startup

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Problem description:
  The laptop starts up fine but the screen is black; even though the screen is 
black I can hear the drum sound prompting me to log in. After rebooting laptop 
all is well with the screen and I have a fully functional system. Sometimes, 
though, I have to restart twice.

  After some search I found people reporting the same issue:
  https://ubuntuforums.org/showthread.php?t=2337274

  or similar issues:
  
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1577074?comments=all

  Additional information:

  1) Ubuntu release:
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2) Package version:
  xorg:
Instalados: 1:7.7+13ubuntu3
Candidato:  1:7.7+13ubuntu3
Tabla de versión:
   *** 1:7.7+13ubuntu3 500
  500 http://co.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3) Computer information:
  Processor: AMD A10-8700 Radeon R6
  Graphic card: Gallium 0.4 on AMD Carrizo (DRM 3.1.0, LLVM 3.8.0)

  Kind regards,
  Victor

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Nov 15 17:56:57 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c5) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Carrizo [103c:8246]
  InstallationDate: Installed on 2016-11-10 (5 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP Pavilion Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/03/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.03
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8246
  dmi.board.vendor: HP
  dmi.board.version: 98.11
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.03:bd05/03/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn8246:rvr98.11:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Nov 15 17:21:18 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.2
  xserver.video_driver: amdgpu

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

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

[Desktop-packages] [Bug 1647187] Re: gnome-software crashed with signal 5 in g_main_context_new()

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

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

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

Title:
  gnome-software crashed with signal 5 in g_main_context_new()

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  when I start ubuntu 16.04 32bit system, it always comes across the
  problem , the system gives an internal problem, as follows:

  Executablepath
   /usr/bin/gnome-software

  Pachage
   gnome-software 3.20.1 +git20160426.1.a976114-ubuntu-xenial-0ubuntu1

  ProblemType
   crash

  Title
   gnome-software crashed with signal 5 in g_main_context_new()

  Architechure
i386

  
  .
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-08-17 (109 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160720)
  Package: gnome-software 
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
  PackageArchitecture: i386
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Tags:  xenial
  Uname: Linux 4.4.0-47-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1641912] Re: Please backport two recent-manager patches

** Changed in: gtk+2.0 (Ubuntu)
   Importance: Undecided => Critical

** Changed in: gtk+2.0 (Ubuntu Xenial)
   Importance: Undecided => Critical

** Changed in: gtk+2.0 (Ubuntu Yakkety)
   Importance: Undecided => Critical

** Changed in: gtk+2.0 (Ubuntu)
   Importance: Critical => High

** Changed in: gtk+2.0 (Ubuntu Xenial)
   Importance: Critical => High

** Changed in: gtk+2.0 (Ubuntu Xenial)
   Importance: High => Critical

** Changed in: gtk+2.0 (Ubuntu)
   Importance: High => Critical

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

Title:
  Please backport two recent-manager patches

Status in GTK+:
  Fix Released
Status in gtk+2.0 package in Ubuntu:
  Confirmed
Status in gtk+2.0 source package in Xenial:
  Confirmed
Status in gtk+2.0 source package in Yakkety:
  Confirmed

Bug description:
  
https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24=a3b2d6a65be9f592de9570c227df00f910167e9e
  
https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24=35871edb318083b2d7e4758cbdaad6109eed60ca

  Please apply/backport these two patches from the 2.24 branch. They fix a 
memory DOS, originally reported against mate-panel here:
  https://github.com/mate-desktop/mate-panel/issues/479

  For the GTK3 version of this bug, see bug 1641914
  Note that MATE is GTK2 only for Ubuntu 16.04 LTS.

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

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

[Desktop-packages] [Bug 1647550] Re: Wifi-SSID List vanishes after a few wakeups; LAN icons instead of wifi a

Doesn't require suspending, but disabling and re-enabling wi-fi is just
enough.

** Changed in: network-manager-applet (Ubuntu)
   Importance: Undecided => High

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

Title:
  Wifi-SSID List vanishes after a few wakeups;LAN icons instead of wifi
  a

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

Bug description:
  when I continue to put on the laptop for 2-3 days without shutting
  down, then the list of wifi-SSID goes away and I see no wifi icon in
  right-corner of menubar. Instead I see LAN icon[you know what I mean].
  After sometime, internet stops working and when I try to stop the wifi
  using "Enable Wifi" and put back on, I can not. I then have to restart
  my laptop to use internet.

  I though its my responsibility to report this bug. Thanks :)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160801.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Uname: Linux 4.4.0-51-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Dec  6 12:03:55 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0674]
  InstallationDate: Installed on 2016-09-08 (89 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 7347
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-51-generic.efi.signed 
root=UUID=6e68a730-3d6f-437a-a31a-f9d4479f2ba4 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0R6C7N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A04
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd01/21/2015:svnDellInc.:pnInspiron7347:pvr00h:rvnDellInc.:rn0R6C7N:rvrA00:cvnDellInc.:ct8:cvrA04:
  dmi.product.name: Inspiron 7347
  dmi.product.version: 00h
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Dec  5 11:35:31 2016
  xserver.configfile: default
  xserver.errors: SynPS/2 Synaptics TouchPad: Read error 19
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   19528 
   vendor SDC
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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

[Desktop-packages] [Bug 1634802] Re: Could not insert module

2016-12-20 Thread Jonathan Neufeld

Confirmed I was unsuccessful with 304.131 and 304.132 but I just
finished installing 304.134 on my 4.8.0-30-generic kernel, no more login
loop and I can get back onto NetFlix.

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

Title:
  Could not insert module

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Yakkety:
  Triaged

Bug description:
  Ubuntu release: 16.10 Yakkety Yak
  Kernel version: 4.8.0-22-generic x86_64
  Package version: 304.132-0ubuntu1

  The nvidia module cannot be loaded. The following errors are reported:
  Could not insert module Unknown symbol in module

  and:

  nvidia: Unknown symbol mtrr_del (err 0)
  nvidia: Unknown symbol mtrr_add (err 0)

  It looks like the buildfix_kernel_4.3.patch, which is supposed to be
  dealing with those calls, is not applied in this release of the
  package.

  The package was working fine with the previous fully updated Ubuntu
  version 16.04 prior to the upgrade to 16.10.

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

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

[Desktop-packages] [Bug 1611745] Re: OpenGL not working through ssh -X

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

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

Title:
  OpenGL not working through ssh -X

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I need to run several OpenGL-depending programs through ssh -x, like
  tecplot, mayavi or paraview. I connect to the remote machine with ssh
  -X (or ssh -Y, doesn't matter). Then I test opengl using e.g. glxinfo.

  The output of glxinfo on the remote machine says that it was unable to
  create the OpenGL context. In the other remote programs I receive the
  same error message. On the local machine, it works fine. See the
  logfiles attached (local_glxinfo.log, remote_glxinfo.log).

  I configured my Xorg according to the attached xorg.conf. The
  configuration was produced with nvidia-settings and two manual tweaks,
  lines 54 and 74. I added those lines because I could not (and still
  can't) enforce indirect rendering of my graphics card. Indirect
  rendering is still switched off, see lines 102 and 167 in Xorg.0.log.

  The issue does also occur when no manually generated xorg.conf is
  present.

  I'm using the latest drivers from the package nvidia-361.

  The issue occurs with and without my graphics card (Intel HD 4600, or
  GeForce 605). Before I switched to ubuntu-gnome 16.04 I had a xubuntu
  14.04 LTS running. There some applications would work, other would
  not. Now nothing works at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia_uvm 
nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:

  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Aug 10 13:32:00 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-34-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-34-generic, x86_64: installed
   virtualbox, 5.0.24, 4.4.0-34-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GF119 [GeForce 605] [10de:1048] (rev a1) (prog-if 00 [VGA 
controller])
     Subsystem: LeadTek Research Inc. GF119 [GeForce 605] [107d:5afd]
  InstallationDate: Installed on 2016-08-09 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: FUJITSU ESPRIMO P720
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=7b7bc513-0076-48db-a71b-28299a8a30e3 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2013
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V4.6.5.4 R1.3.0 for D3221-A1x
  dmi.board.name: D3221-A1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3221-A1
  dmi.chassis.type: 6
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: C$WX02
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.5.4R1.3.0forD3221-A1x:bd05/28/2013:svnFUJITSU:pnESPRIMOP720:pvr:rvnFUJITSU:rnD3221-A1:rvrS26361-D3221-A1:cvnFUJITSU:ct6:cvrC$WX02:
  dmi.product.name: ESPRIMO P720
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Aug 10 11:27:40 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2.3

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1644916] Re: missing fonts after suspend

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Importance: Undecided => High

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

Title:
  missing fonts after suspend

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

Bug description:
  Similar bugs were reported earlier:
  https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1432194
  https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1596698

  Every 4-5 days, after suspend the system fonts are missing and system becomes 
unusable, as shown in attached screenshot.
  As suggested in forums, playing with font size or scaling factor provides 
temporary relief but after one more suspend the situation gets worse. 
Restarting genome-shell does not help the situation. Only solution is to log 
out or to reboot. 

  
  Additional requested info:
  1. Release: Ubuntu 16.04.1 LTS
  2. Package version: xserver-xorg-video-intel: Installed: 
2:2.99.917+git20160325-1ubuntu1.1

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Nov 25 23:29:14 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-45-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-47-generic, x86_64: installed
   vboxhost, 5.0.22, 4.4.0-45-generic, x86_64: installed
   vboxhost, 5.0.22, 4.4.0-47-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:11cd]
  InstallationDate: Installed on 2016-06-15 (163 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. N550JV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed 
root=UUID=cbaa9129-3d72-47a5-9b00-151ad15c7536 ro quiet splash acpi_osi= 
vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N550JV.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N550JV
  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.:bvrN550JV.208:bd11/19/2013:svnASUSTeKCOMPUTERINC.:pnN550JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N550JV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Nov 25 23:10:45 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 803
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Desktop-packages] [Bug 1646706] Re: package libcuda1-340 340.96-0ubuntu3.16.04.1 failed to install/upgrade: there is no script in the new version of the package - giving up

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

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

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

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

Bug description:
  failled install

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libcuda1-340 340.96-0ubuntu3.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Uname: Linux 4.4.0-51-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] È una directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  304.132  Fri Sep 16 11:22:35 
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.1
  Architecture: i386
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Dec  2 08:14:24 2016
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu4
   libgcc1 1:6.0.1-0ubuntu1
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ErrorMessage: there is no script in the new version of the package - giving up
  GraphicsCard:
   NVIDIA Corporation G96M [GeForce 9600M GT] [10de:0649] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company G96M [GeForce 9600M GT] [103c:30f4]
  InstallationDate: Installed on 2011-06-15 (1996 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-51-generic 
root=UUID=df47aabd-4975-43d0-847e-c681ee20576f ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: nvidia-graphics-drivers-340
  Title: package libcuda1-340 340.96-0ubuntu3.16.04.1 failed to 
install/upgrade: there is no script in the new version of the package - giving 
up
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.0A
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 30F4
  dmi.board.vendor: Compal
  dmi.board.version: 99.55
  dmi.chassis.type: 10
  dmi.chassis.vendor: Compal
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.0A:bd07/17/2008:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrF.0A:rvnCompal:rn30F4:rvr99.55:cvnCompal:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: F.0A
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Dec  2 08:19:28 2016
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Desktop-packages] [Bug 991471] Re: multi-device btrfs filesystem automatically mounted once for each device

** Changed in: btrfs-tools (Ubuntu)
   Importance: Undecided => Medium

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

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

Title:
  multi-device btrfs filesystem automatically mounted once for each
  device

Status in btrfs package in Ubuntu:
  Invalid
Status in btrfs-tools package in Ubuntu:
  Confirmed
Status in udev package in Ubuntu:
  Confirmed
Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  If I have a multi-device btrfs filesystem, and I plug it in via some
  removable interface (for example, USB3), it will automatically mount
  on the desktop multiple times.  For example, if I have a filesystem
  labeled FooBar on /dev/sdb /dev/sdc /dev/sdd and /dev/sde, it will be
  mounted as /media/FooBar, /media/FooBar1, /media/FooBar2, and
  /media/FooBar3.  It should show up only once.

  It seems like everything still basically works, but I didn't test
  writing to said filesystem under the different aliases.

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

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

[Desktop-packages] [Bug 1643345] Re: nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to build [Makefile:81: recipe for target 'modules' failed]

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

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

Title:
  nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to
  build [Makefile:81: recipe for target 'modules' failed]

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

Bug description:
  The default selected nvidia driver 367 does not work in Ubuntu 16.04
  64-bit.  Hangs on build.  Ran killall make in order to get updates to
  complete.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-367 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-45-generic
  Date: Sun Nov 20 08:45:49 2016
  InstallationDate: Installed on 2014-09-28 (784 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageVersion: 367.57-0ubuntu0.16.04.1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: nvidia-graphics-drivers-367
  Title: nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to 
build
  UpgradeStatus: Upgraded to xenial on 2016-10-20 (31 days ago)
  modified.conffile..etc.modprobe.d.nvidia-367_hybrid.conf: [deleted]

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

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

[Desktop-packages] [Bug 1638990] Re: nvidia-367 with kernel 4.4.0-45-generic won't boot

Since this bug renders the system broken, it should have an importance
of "critical".

** Changed in: nvidia-graphics-drivers-367 (Ubuntu)
   Importance: Undecided => Critical

** Changed in: linux (Ubuntu)
   Importance: High => Critical

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

Title:
  nvidia-367 with kernel 4.4.0-45-generic won't boot

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Confirmed

Bug description:
  After I upgraded the nvidia drivers, I could no longer boot via kernel
  4.4.0-45-generic. I can boot with kernel 4.4.0-31-generic.

  WORKAROUND: Use nouveau.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-45-generic 4.4.0-45.66
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  lost   2248 F pulseaudio
   /dev/snd/controlC0:  lost   2248 F pulseaudio
   /dev/snd/controlC1:  lost   2248 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Nov  3 12:12:55 2016
  HibernationDevice: RESUME=UUID=cf59c168-54d0-45b9-b633-240bd76bbaa6
  InstallationDate: Installed on 2016-11-01 (1 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 11361Q0
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic 
root=/dev/mapper/xubuntu--vg-root ro nomodeset quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.157.4
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A3KT57AUS
  dmi.board.name: LENOVO
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: 573921
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvrA3KT57AUS:bd09/29/2016:svnLENOVO:pn11361Q0:pvrThinkStationC30:rvnLENOVO:rnLENOVO:rvrNODPK:cvnLENOVO:ct7:cvrNONE:
  dmi.product.name: 11361Q0
  dmi.product.version: ThinkStation C30
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

2016-12-20 Thread bagl0312

Confirmed that the patch works also on dell latitude E7370 with kernel version
4.4.0-57-generic #78-Ubuntu SMP

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

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1349338] Re: Sync libxkbcommon 0.4.1-2 (main) from Debian unstable (main)

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

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

Title:
  Sync libxkbcommon 0.4.1-2 (main) from Debian unstable (main)

Status in libxkbcommon package in Ubuntu:
  Fix Released

Bug description:
  Please sync libxkbcommon 0.4.1-2 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Sync from debian git. (LP: #1303706)
* New upstream release.
* libxkbcommon0.symbols: Added three new symbol
  Fixed in debian

  Changelog entries since current utopic version 0.4.1-0ubuntu1:

  libxkbcommon (0.4.1-2) unstable; urgency=medium

* Make libxkbcommon-x11 depend on the same version of libxkbcommon0
  (Closes: #755724)

   -- Michael Stapelberg   Wed, 23 Jul 2014
  08:35:57 +0200

  libxkbcommon (0.4.1-1) unstable; urgency=medium

[ Timo Aaltonen ]
* New upstream release.
* libxkbcommon0.symbols: Added three new symbols.

[ Michael Stapelberg ]
* Make libxkbcommon-x11-dev depend on libxcb1-dev and libxcb-xkb-dev which
  it specifies in Requires.private. This is necessary for static builds.

   -- Michael Stapelberg   Fri, 18 Jul 2014
  21:16:31 +0200

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

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

[Desktop-packages] [Bug 1293099] Re: Password needs to be entered twice after switching users

2016-12-20 Thread James Tunnell

This is still an issue, for me anyway, on Ubuntu 16.10

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

Title:
  Password needs to be entered twice after switching users

Status in unity-greeter package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu 13.10 to Ubuntu 14.04 I have to enter my
  password twice after switching users. The problem can be solved by
  uninstalling gnome-screensaver - however, this breaks locking the
  screen by using "Strg+Alt+L" or by clicking "Lock screen" in the Unity
  menu.

  Maybe gnome-screensaver should be replaced by light-locker? After
  installing light-locker (with no gnome-screensaver installed) locking
  works fine from the command line, but does not work in Unity.

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

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

[Desktop-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

2016-12-20 Thread Kyle Vedder

I just received the patch and my touchpad now works as expected.

This is for my Dell Latitude E5470, which, before this update, had the
generic mouse drivers which did not recognize it as a touchpad.

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

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

2016-12-20 Thread Sabin Iacob

in my case I have to do rmmod btusb; modprobe btusb


it looks to me like every new release of Ubuntu manages to break Bluetooth 
audio in some way that is new and creative and ever-increasingly difficult to 
automate away: 
 * 14.10 and before - volume wouldn't be restored, sink wouldn't switch; solved 
by having a script listen to dbus for a headphone connection event and tell 
pulseaudio to set the default sink and restore volume
 * 15.04 - no sound unless I disconnected and reconnected again; put that in a 
script
 * 15.10 - needed to connect manually, but at least the rest worked; solved by 
having a script look if the phones are connected, do a l2ping to see if they 
are available and connect; occasionally I'd have to rmmod btusb; modprobe btusb
 * 16.04 - this issue; I only managed to upgrade yesterday, I still haven't 
found a pattern to this madness


-- 
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:
  Confirmed
Status in indicator-sound package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

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 :

[Desktop-packages] [Bug 1607684] Re: wifi networks not remembered correctly (ubuntu touch, bq M10)

2016-12-20 Thread Samuel Walladge

This can probably be closed. After receiving my tablet back from BQ with
the s/n, mac addresses, etc. reset, I haven't had this problem since.

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

Title:
  wifi networks not remembered correctly (ubuntu touch, bq M10)

Status in Canonical System Image:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  I have a M10, on ubuntu touch OTA-12 (and same issue previously on
  OTA-11).

  The issue is that it doesn't remember wifi networks properly. To
  explain:

  1. turn on tablet
  2. select my wifi network from the list
  3. enter password and click connect
  4. reboot device
  5. select my wifi network from the list
  6. enter password and click connect
  .
  .
  .
  30. go to wifi settings -> previous networks
  31. view long list that looks like:

  MyWifinetwork1
  MyWifinetwork2
  MyWifinetwork3
  MyWifinetwork4
  ...

  What it should do (and did some time ago), is see that MyWifinetwork
  was saved in previous networks and automatically connect using the
  saved password/settings.

  So, I'm wondering is this a bug, something badly configured in my wifi
  network (although other devices remember it fine), or something else?

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607684/+subscriptions

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

[Desktop-packages] [Bug 1645522] Re: [SRU] libopencc2: missing files cause librime fail to work

This bug was fixed in the package opencc - 1.0.4-1ubuntu0.16.10.1

---
opencc (1.0.4-1ubuntu0.16.10.1) yakkety; urgency=medium

  [ Aron Xu ]
  * Install data files to libopencc2-data, drop -dbg package
(LP: #1645522)

  [ Boyuan Yang ]
  * Add BSD-3-clause license in d/copyright

 -- Aron Xu   Tue, 29 Nov 2016 02:06:48 +

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

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

Title:
  [SRU] libopencc2: missing files cause librime fail to work

Status in opencc package in Ubuntu:
  Fix Released
Status in opencc source package in Yakkety:
  Fix Released
Status in opencc source package in Zesty:
  Fix Released
Status in opencc package in Debian:
  Fix Released

Bug description:
  [Impact]

  A list of missing files from opencc package makes opencc and libopencc2 does 
not work correctly for its consumers (fcitx-rime, ibus-rime). For example, when 
using fcitx-rime, fcitx would print the
  following error message onto stderr once the user tries to switch to
  input Simplified Chinese in Rime (Selecting *月拼音：简化字):

  [Test Case]

  After installing the updated package, fcitx-rime would not print error
  messages when user tries to switch to input Simplified Chinese in
  Rime.

  [Regression Potential]

  This updated package would introduce an additional binary call
  librime-data, which is actually a backport of version 1.0.4-2 in
  Debian and Ubuntu Zesty, potential of regression is low.

  == Description from Debian bug ==

  In Debian unstable, when using fcitx-rime, fcitx would print the
  following error message onto stderr once the user tries to switch to
  input Simplified Chinese in rime (Selecting *月拼音：简化字):

  E0902 23:45:44.494884 6107 simplifier.cc:126] Error initializing
  opencc: t2s.json not found or not accessible.

  The t2s.json is supposed to be in /usr/share/opencc. To be concrete,
  the following missing files may be needed for opencc to work
  correctly:

  usr/share/
  usr/share/opencc/
  usr/share/opencc/HKVariants.ocd
  usr/share/opencc/HKVariantsPhrases.ocd
  usr/share/opencc/HKVariantsRev.ocd
  usr/share/opencc/HKVariantsRevPhrases.ocd
  usr/share/opencc/JPVariants.ocd
  usr/share/opencc/STCharacters.ocd
  usr/share/opencc/STPhrases.ocd
  usr/share/opencc/TSCharacters.ocd
  usr/share/opencc/TSPhrases.ocd
  usr/share/opencc/TWPhrases.ocd
  usr/share/opencc/TWPhrasesRev.ocd
  usr/share/opencc/TWVariants.ocd
  usr/share/opencc/TWVariantsRev.ocd
  usr/share/opencc/TWVariantsRevPhrases.ocd
  usr/share/opencc/hk2s.json
  usr/share/opencc/s2hk.json
  usr/share/opencc/s2t.json
  usr/share/opencc/s2tw.json
  usr/share/opencc/s2twp.json
  usr/share/opencc/t2hk.json
  usr/share/opencc/t2s.json
  usr/share/opencc/t2tw.json
  usr/share/opencc/tw2s.json
  usr/share/opencc/tw2sp.json

  However, they do not exist in any opencc-related packages
  (libopencc-dev, libopencc-dbg (Oh, BTW, please migrate to -dbgsym
  package), libopencc2 and opencc).

  The solution may be either include those files in a library package,
  or pack those files into another separate package.

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

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

[Desktop-packages] [Bug 1645522] Update Released

2016-12-20 Thread Chris Halse Rogers

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

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

Title:
  [SRU] libopencc2: missing files cause librime fail to work

Status in opencc package in Ubuntu:
  Fix Released
Status in opencc source package in Yakkety:
  Fix Released
Status in opencc source package in Zesty:
  Fix Released
Status in opencc package in Debian:
  Fix Released

Bug description:
  [Impact]

  A list of missing files from opencc package makes opencc and libopencc2 does 
not work correctly for its consumers (fcitx-rime, ibus-rime). For example, when 
using fcitx-rime, fcitx would print the
  following error message onto stderr once the user tries to switch to
  input Simplified Chinese in Rime (Selecting *月拼音：简化字):

  [Test Case]

  After installing the updated package, fcitx-rime would not print error
  messages when user tries to switch to input Simplified Chinese in
  Rime.

  [Regression Potential]

  This updated package would introduce an additional binary call
  librime-data, which is actually a backport of version 1.0.4-2 in
  Debian and Ubuntu Zesty, potential of regression is low.

  == Description from Debian bug ==

  In Debian unstable, when using fcitx-rime, fcitx would print the
  following error message onto stderr once the user tries to switch to
  input Simplified Chinese in rime (Selecting *月拼音：简化字):

  E0902 23:45:44.494884 6107 simplifier.cc:126] Error initializing
  opencc: t2s.json not found or not accessible.

  The t2s.json is supposed to be in /usr/share/opencc. To be concrete,
  the following missing files may be needed for opencc to work
  correctly:

  usr/share/
  usr/share/opencc/
  usr/share/opencc/HKVariants.ocd
  usr/share/opencc/HKVariantsPhrases.ocd
  usr/share/opencc/HKVariantsRev.ocd
  usr/share/opencc/HKVariantsRevPhrases.ocd
  usr/share/opencc/JPVariants.ocd
  usr/share/opencc/STCharacters.ocd
  usr/share/opencc/STPhrases.ocd
  usr/share/opencc/TSCharacters.ocd
  usr/share/opencc/TSPhrases.ocd
  usr/share/opencc/TWPhrases.ocd
  usr/share/opencc/TWPhrasesRev.ocd
  usr/share/opencc/TWVariants.ocd
  usr/share/opencc/TWVariantsRev.ocd
  usr/share/opencc/TWVariantsRevPhrases.ocd
  usr/share/opencc/hk2s.json
  usr/share/opencc/s2hk.json
  usr/share/opencc/s2t.json
  usr/share/opencc/s2tw.json
  usr/share/opencc/s2twp.json
  usr/share/opencc/t2hk.json
  usr/share/opencc/t2s.json
  usr/share/opencc/t2tw.json
  usr/share/opencc/tw2s.json
  usr/share/opencc/tw2sp.json

  However, they do not exist in any opencc-related packages
  (libopencc-dev, libopencc-dbg (Oh, BTW, please migrate to -dbgsym
  package), libopencc2 and opencc).

  The solution may be either include those files in a library package,
  or pack those files into another separate package.

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

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

[Desktop-packages] [Bug 1247528] Update Released

2016-12-20 Thread Chris Halse Rogers

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

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

Title:
  [SRU] Build and distribute intel-virtual-output

Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel source package in Trusty:
  Fix Released
Status in xserver-xorg-video-intel package in Debian:
  Fix Released

Bug description:
  [Impact]

  xserver-xorg-video-intel 2.99.904 adds support for virtual displays
  that can be used to clone to discrete outputs. The tool to do this is
  included with the xserver-xorg-video-intel source (with not-so-great
  man page and all), but the binary is currently not shipped by Ubuntu
  trusty, despite being built. It is shipped in utopic and later.

  The tool will allocate a virtual output for the specified outputs on a
  different X server (or for all outputs with the -a parameter). It will
  also copy over resolution information etc from xrandr. You can then
  use your desktop environment's display tool to configure these
  external displays the way you would normally do in a non-hybrid
  situation.

  Since the trusty release is LTS, this bug qualifies for SRU status "to
  enable new hardware," or rather, newly supported at the time of the
  trusty release.

  [Test Case]

  1) Install the package.
  2) Attempt to execute /usr/bin/intel-virtual-output in a shell.

  [Regression Potential]

  Absolutely none.

  [Other Info]

  The intel-gpu-tools package is the only reverse dependency, and that
  package has no reverse dependencies in turn.

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

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

[Desktop-packages] [Bug 1247528] Re: [SRU] Build and distribute intel-virtual-output

This bug was fixed in the package xserver-xorg-video-intel -
2:2.99.910-0ubuntu1.7

---
xserver-xorg-video-intel (2:2.99.910-0ubuntu1.7) trusty-proposed; urgency=medium

  * Package intel-virtual-output (LP: #1247528)
- debian/xserver-xorg-video-intel.install: Install it
- debian/control: Additional build dependencies: libxinerama-dev,
  libxrandr-dev, libxdamage-dev, libxcursor-dev, libxtst-dev,
  libxrender-dev, libpixman-1-dev

 -- Daniel Gimpelevich   Wed, 17
Aug 2016 18:57:05 -0700

** Changed in: xserver-xorg-video-intel (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] Build and distribute intel-virtual-output

Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel source package in Trusty:
  Fix Released
Status in xserver-xorg-video-intel package in Debian:
  Fix Released

Bug description:
  [Impact]

  xserver-xorg-video-intel 2.99.904 adds support for virtual displays
  that can be used to clone to discrete outputs. The tool to do this is
  included with the xserver-xorg-video-intel source (with not-so-great
  man page and all), but the binary is currently not shipped by Ubuntu
  trusty, despite being built. It is shipped in utopic and later.

  The tool will allocate a virtual output for the specified outputs on a
  different X server (or for all outputs with the -a parameter). It will
  also copy over resolution information etc from xrandr. You can then
  use your desktop environment's display tool to configure these
  external displays the way you would normally do in a non-hybrid
  situation.

  Since the trusty release is LTS, this bug qualifies for SRU status "to
  enable new hardware," or rather, newly supported at the time of the
  trusty release.

  [Test Case]

  1) Install the package.
  2) Attempt to execute /usr/bin/intel-virtual-output in a shell.

  [Regression Potential]

  Absolutely none.

  [Other Info]

  The intel-gpu-tools package is the only reverse dependency, and that
  package has no reverse dependencies in turn.

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

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

[Desktop-packages] [Bug 1619600] Re: [SRU] New stable release 1.8.3

2016-12-20 Thread Mathew Hodson

** No longer affects: gst-plugins-bad1.0 (Ubuntu Yakkety)

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

Title:
  [SRU] New stable release 1.8.3

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-bad1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-base1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-good1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-ugly1.0 source package in Xenial:
  Fix Committed
Status in gstreamer-vaapi source package in Xenial:
  Fix Committed
Status in gstreamer1.0 source package in Xenial:
  Fix Committed

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.8 series
  that 16.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1619600/+subscriptions

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

[Desktop-packages] [Bug 1639180] Re: no login possible after update to nvidia 304.132

Thanks for suggestions - don't know if I will get a chance to try in
next few days.

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Triaged
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

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

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

[Desktop-packages] [Bug 1621207] Re: gnome-software crashed with SIGSEGV in gs_plugin_loader_get_updates_async()

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

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

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

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

Title:
  gnome-software crashed with SIGSEGV in
  gs_plugin_loader_get_updates_async()

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Crash after suspend.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: gnome-software 3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1
  ProcVersionSignature: Ubuntu 4.6.0-10.12-generic 4.6.5
  Uname: Linux 4.6.0-10-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Wed Sep  7 19:32:04 2016
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2016-07-21 (47 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160718)
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x562eb9ce797f 
:cmp(%rdx),%rax
   PC (0x562eb9ce797f) ok
   source "(%rdx)" (0x2e66001f0fc3f889) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-software
  StacktraceTop:
   gs_plugin_loader_get_updates_async ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-software crashed with SIGSEGV in 
gs_plugin_loader_get_updates_async()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1634802] Re: Could not insert module

2016-12-20 Thread Ben Coleman

Ah.  Apparently 304.134 release I got was from the graphics-drivers PPA.

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

Title:
  Could not insert module

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Yakkety:
  Triaged

Bug description:
  Ubuntu release: 16.10 Yakkety Yak
  Kernel version: 4.8.0-22-generic x86_64
  Package version: 304.132-0ubuntu1

  The nvidia module cannot be loaded. The following errors are reported:
  Could not insert module Unknown symbol in module

  and:

  nvidia: Unknown symbol mtrr_del (err 0)
  nvidia: Unknown symbol mtrr_add (err 0)

  It looks like the buildfix_kernel_4.3.patch, which is supposed to be
  dealing with those calls, is not applied in this release of the
  package.

  The package was working fine with the previous fully updated Ubuntu
  version 16.04 prior to the upgrade to 16.10.

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

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

[Desktop-packages] [Bug 1651575] Re: goa-daemon starts broken

2016-12-20 Thread Paul White

** Also affects: gnome-online-accounts (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1350678
   Importance: Unknown
   Status: Unknown

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

Title:
  goa-daemon starts broken

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

Bug description:
  goa-daemon, that is started with GNOME Shell/Wayland on login, on
  16.10 launches in a corrupt state where all authentication fails.

  This can be seen by launching Evolution which fails to use credential
  from goa.

  GETAROUND
  restart goa

  killall goa-daemon

  - goa-daemon retarts by itself
  - authentication now works

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-online-accounts 3.22.2-1~ubuntu16.10.1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Dec 20 12:17:37 2016
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to yakkety on 2016-11-16 (34 days ago)

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

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

[Desktop-packages] [Bug 1634802] Re: Could not insert module

2016-12-20 Thread Ben Coleman

Apparently, there was a nvidia-304-304.134 release in the past week.  I
still had to uncomment the "#PATCH[1]="buildfix_kernel_4.3.patch" line
in dkms.conf and run 'dpkg-reconfigure nvidia-304' to get rid of the
mtrr-add and mtrr-del references so it would load, but the speed problem
that others have noted appears to have been dealt with.   At least
watching Netflix on this particular machine is back to where it was on
16.04.

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

Title:
  Could not insert module

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Yakkety:
  Triaged

Bug description:
  Ubuntu release: 16.10 Yakkety Yak
  Kernel version: 4.8.0-22-generic x86_64
  Package version: 304.132-0ubuntu1

  The nvidia module cannot be loaded. The following errors are reported:
  Could not insert module Unknown symbol in module

  and:

  nvidia: Unknown symbol mtrr_del (err 0)
  nvidia: Unknown symbol mtrr_add (err 0)

  It looks like the buildfix_kernel_4.3.patch, which is supposed to be
  dealing with those calls, is not applied in this release of the
  package.

  The package was working fine with the previous fully updated Ubuntu
  version 16.04 prior to the upgrade to 16.10.

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

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

[Desktop-packages] [Bug 1644320] Re: [SRU] New upstream release 2.50.1

2016-12-20 Thread Nikita Yerenkov-Scott

This update fixes the issues for me and there are currently no
noticeable regressions on my Ubuntu GNOME 16.10 GNOME 3.22 64-bit
system.

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

** Tags added: yakkety

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

Title:
  [SRU] New upstream release 2.50.1

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

Bug description:
  [ Description ]

  Upstream have released a new bugfix release.

  [ Changes ]

  From NEWS:

  Overview of changes in GLib 2.50.2
  ==

  * Bugs fixed:
   767882 Bit shift overflow (-Wshift-overflow) warning in gparam.h
   769135 External control for g_test_add/g_test_run
   769630 gfile: G_FILE_MONITOR_WATCH_MOVES was actually introduced in 2.46
   772054 Patch for glib/gspawn-win32-helper.c: unexpected behavior re 
CommandLineToArgvW()
   773303 GApplication leaks option_strings
   773344 glib-compile-resources: Fix creating depfile with other targets
  
  * Translation updates:
   French
   Galician
   German
   Lithuanian
   Norwegian bokmål
   Occitan
   Serbian
   Slovak

  
  Overview of changes in GLib 2.50.1
  ==

  * Update Unicode support to Unicode 9.0.0

  * Bugs fixed:
   662946 gunixmounts monitoring doesn't work correctly with libmount
   771591 Update to Unicode 9.0.0
   772054 glib/gspawn-win32-helper.c: unexpected behavior re 
CommandLineToArgvW()
   772255 gresolver: Mark GResolver as an abstract class
   772269 Add --version options to glib-compile-resources and 
glib-compile-schemas
   772297 completion: Complete gsettings describe
   772511 g_log_default_handler crashes windows apps with "Unspecified fatal 
err...

  * Translation updates: 
   Brazilian Portuguese
   Catalan
   Croatian
   Czech
   Danish
   Hungarian
   Italian
   Latvian 
   Polish
   Swedish

  
  [ QA, testing, regression potential ]

  Under the GNOME MRE, you can believe all bugs upstream says are fixed
  are really fixed. Just test the system and make sure there are no
  regressions (e.g. look at errors.ubuntu.com).

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

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

[Desktop-packages] [Bug 1650684] Re: Position of gnome-system-monitor is not remembered on screen when under Wayland

2016-12-20 Thread Bug Watch Updater

** Changed in: gnome-shell
   Status: Unknown => Confirmed

** Changed in: gnome-shell
   Importance: Unknown => Medium

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

Title:
  Position of gnome-system-monitor is not remembered on screen when
  under Wayland

Status in gnome-shell:
  Confirmed
Status in Ubuntu GNOME:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in gnome-system-monitor package in Ubuntu:
  New

Bug description:
  I am running Ubuntu GNOME 16.10 with GNOME 3.22 and since switching
  from Xorg to Wayland via the login screen I have noticed that with the
  gnome-system-monitor that it always starts off on the left hand side
  of the screen, and I like to have it on the right hand side, so that
  is where I always put it. However, if I restart it, it always goes
  back to the left side rather than remembering where it was before like
  it does if I close it when it is fullscreen.

  So far it seems that this issue only affects the gnome-system-monitor,
  all other applications behave as expected in regards to this matter.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-shell 3.22.2-1ubuntu1~ubuntu16.10.1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec 16 22:26:09 2016
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-05-15 (215 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to yakkety on 2016-10-19 (58 days ago)

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

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

[Desktop-packages] [Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2016-12-20 Thread Till Kamppeter

xnox, it seems that the suggested fix of comment #52 is the solution for
this bug, and I could at any time add a patch to the CUPS package and
issue it as an SRU. Only problem is, if I do only this, will the SRU
smoothly install? Or are additional measures required?

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  Confirmed
Status in init-system-helpers package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  This is in xenial-proposed, please block release to -updates
  accordingly :)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2016-12-20 Thread Till Kamppeter

Reported the suggested solution of comment #52 to CUPS upstream as

https://github.com/apple/cups/issues/4935

The change will get applied in the next release of CUPS (2.2.2, in
January).

** Bug watch added: github.com/apple/cups/issues #4935
   https://github.com/apple/cups/issues/4935

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  Confirmed
Status in init-system-helpers package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  This is in xenial-proposed, please block release to -updates
  accordingly :)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2016-12-20 Thread Lonnie Lee Best

Bryn, thank for the suggested work around. However, it is not a workaround for 
me. My issue is that I have over 100 Remmina RDP desktop configurations saved 
that connect to numerous computers on different VPNs by computer name (not by 
ip address). However, I cannot ping those computers by name when I'm connected 
to their respective VPNs anymore like I could before recent Network Manger 
updates. My issue is described in detail here:
https://bugs.launchpad.net/network-manager-applet/+bug/1633874

When you are connected to a VPN, your computer is suppose to check that
virtual private network's DNS servers too, when it cannot find (on your
local network) the computer-name you are you are trying to reach by
name.

Network Manger gives you the opportunity to specify "Additional DNS
Servers" for each connection you set up whether it be LAN, WiFi, or VPN.
Yet Network manager now fails to queries those DNS servers in the proper
order. It seems to just give up at the local DNS level when the other
DNSs you've configured could certainly tell you the ip address of the
computer name you are trying to reach if it were simply asked. It is not
being ASKED.

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

Title:
  dns server priority broken

Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  network-manager: 1.2.4-0ubuntu1

  
  Yakkety appears to have switched back from resolved to dnsmasq, but it seems 
server priority/order is broken.

  Example: In split DNS setups, connecting to VPN will not cause us to
  query the DNS provided by the VPN first (or only), which should be the
  proper way to resolve names in that case.

  Say server.example.com in the public DNS resolves to a.a.a.a and in
  the private DNS resolves to b.b.b.b.

  Stuff would work from my normal internet-connection, but connection to
  VPN would cause stuff to misbehave. I expect to hit the b.b.b.b
  address but since my normal LAN DNS is being used first, I'm really
  hitting a.a.a.a.

  Please let me know how to proceed - Hopefully this can be fixed in
  time for release.

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

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

[Desktop-packages] [Bug 1642413] RelatedPackageVersions.txt

apport information

** Attachment added: "RelatedPackageVersions.txt"
   
https://bugs.launchpad.net/bugs/1642413/+attachment/4794438/+files/RelatedPackageVersions.txt

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

Title:
  Chromium uses ~100% of all cores, locks up, and does not exit
  correctly

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  whether or not extensions are enabled, after an indeterminate amount
  of time chromium locks up(tabs are still rendered but browser cannot
  create new tabs, or navigate in existing ones) and the main process
  begins using 200-270% of my three cores, chrome task manager shows
  that no tab is using any memory and when chromium is exited the main
  thread does not quit and must be killed.

  I have reinstalled, disabled extensions/plugins, etc... nothing seems
  to remedy this issue.

  I memtested my memory and it was fine.

  This issue seems to be triggered every time by paypal virtual
  terminal(paypal.com/vt) mostly, but it happens on other sites randomly
  as well

  It started happening 30-40 days ago
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAi8A4mACANAQOAIht46gyVolZMliUaUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4TB5TDgAKICAgICAg/ABocCBMMTczMAogICAg/wBDTlAzMzJTMFJICiAgALo=
   modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 
800x600 800x600 800x600 640x480 640x480 640x480 720x400
  DRM.card0-VGA-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wA6kwcAAQoRAQMIKxt4CrU0pVZKmiUQUFSvzwCBgIGPlQCVDwEBAQEBAQEBHDmQMGIaJ0BosDYAsQ8RAAAY/gAKICAgICAgICAgICAg/ABNQVctU0VSSUFMCiAg/wAKICAgICAgICAgICAgAHk=
   modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 
1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400
  Desktop-Session:
   'mate'
   '/etc/xdg/xdg-mate:/etc/xdg'
   '/usr/share/mate:/usr/local/share/:/usr/share/:/usr/share/mdm/'
  DistroRelease: Linux 18.1
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2016-07-13 (159 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Load-Avg-1min: 3.87
  Load-Processes-Running-Percent:   0.7%
  MachineType: MSI MS-7786
  Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=5c8e46d1-e26c-4bba-b87b-f092a8a3d7ad ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  Tags: serena third-party-packages
  ThirdParty: True
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev 
sambashare scanner sudo tape vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A55M-P33 (MS-7786)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.0:bd02/04/2013:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P33(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7786
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]
  mtime.conffile..etc.chromium-browser.default: 2016-07-13T18:03:09.849211

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

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

[Desktop-packages] [Bug 1642413] gconf-keys.txt

apport information

** Attachment added: "gconf-keys.txt"
   
https://bugs.launchpad.net/bugs/1642413/+attachment/4794443/+files/gconf-keys.txt

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

Title:
  Chromium uses ~100% of all cores, locks up, and does not exit
  correctly

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  whether or not extensions are enabled, after an indeterminate amount
  of time chromium locks up(tabs are still rendered but browser cannot
  create new tabs, or navigate in existing ones) and the main process
  begins using 200-270% of my three cores, chrome task manager shows
  that no tab is using any memory and when chromium is exited the main
  thread does not quit and must be killed.

  I have reinstalled, disabled extensions/plugins, etc... nothing seems
  to remedy this issue.

  I memtested my memory and it was fine.

  This issue seems to be triggered every time by paypal virtual
  terminal(paypal.com/vt) mostly, but it happens on other sites randomly
  as well

  It started happening 30-40 days ago
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAi8A4mACANAQOAIht46gyVolZMliUaUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4TB5TDgAKICAgICAg/ABocCBMMTczMAogICAg/wBDTlAzMzJTMFJICiAgALo=
   modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 
800x600 800x600 800x600 640x480 640x480 640x480 720x400
  DRM.card0-VGA-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wA6kwcAAQoRAQMIKxt4CrU0pVZKmiUQUFSvzwCBgIGPlQCVDwEBAQEBAQEBHDmQMGIaJ0BosDYAsQ8RAAAY/gAKICAgICAgICAgICAg/ABNQVctU0VSSUFMCiAg/wAKICAgICAgICAgICAgAHk=
   modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 
1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400
  Desktop-Session:
   'mate'
   '/etc/xdg/xdg-mate:/etc/xdg'
   '/usr/share/mate:/usr/local/share/:/usr/share/:/usr/share/mdm/'
  DistroRelease: Linux 18.1
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2016-07-13 (159 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Load-Avg-1min: 3.87
  Load-Processes-Running-Percent:   0.7%
  MachineType: MSI MS-7786
  Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=5c8e46d1-e26c-4bba-b87b-f092a8a3d7ad ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  Tags: serena third-party-packages
  ThirdParty: True
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev 
sambashare scanner sudo tape vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A55M-P33 (MS-7786)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.0:bd02/04/2013:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P33(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7786
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]
  mtime.conffile..etc.chromium-browser.default: 2016-07-13T18:03:09.849211

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

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

[Desktop-packages] [Bug 1642413] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1642413/+attachment/4794435/+files/ProcCpuinfo.txt

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

Title:
  Chromium uses ~100% of all cores, locks up, and does not exit
  correctly

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  whether or not extensions are enabled, after an indeterminate amount
  of time chromium locks up(tabs are still rendered but browser cannot
  create new tabs, or navigate in existing ones) and the main process
  begins using 200-270% of my three cores, chrome task manager shows
  that no tab is using any memory and when chromium is exited the main
  thread does not quit and must be killed.

  I have reinstalled, disabled extensions/plugins, etc... nothing seems
  to remedy this issue.

  I memtested my memory and it was fine.

  This issue seems to be triggered every time by paypal virtual
  terminal(paypal.com/vt) mostly, but it happens on other sites randomly
  as well

  It started happening 30-40 days ago
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAi8A4mACANAQOAIht46gyVolZMliUaUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4TB5TDgAKICAgICAg/ABocCBMMTczMAogICAg/wBDTlAzMzJTMFJICiAgALo=
   modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 
800x600 800x600 800x600 640x480 640x480 640x480 720x400
  DRM.card0-VGA-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wA6kwcAAQoRAQMIKxt4CrU0pVZKmiUQUFSvzwCBgIGPlQCVDwEBAQEBAQEBHDmQMGIaJ0BosDYAsQ8RAAAY/gAKICAgICAgICAgICAg/ABNQVctU0VSSUFMCiAg/wAKICAgICAgICAgICAgAHk=
   modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 
1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400
  Desktop-Session:
   'mate'
   '/etc/xdg/xdg-mate:/etc/xdg'
   '/usr/share/mate:/usr/local/share/:/usr/share/:/usr/share/mdm/'
  DistroRelease: Linux 18.1
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2016-07-13 (159 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Load-Avg-1min: 3.87
  Load-Processes-Running-Percent:   0.7%
  MachineType: MSI MS-7786
  Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=5c8e46d1-e26c-4bba-b87b-f092a8a3d7ad ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  Tags: serena third-party-packages
  ThirdParty: True
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev 
sambashare scanner sudo tape vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A55M-P33 (MS-7786)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.0:bd02/04/2013:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P33(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7786
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]
  mtime.conffile..etc.chromium-browser.default: 2016-07-13T18:03:09.849211

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

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

[Desktop-packages] [Bug 1642413] modified.conffile..etc.chromium-browser.default.txt

apport information

** Attachment added: "modified.conffile..etc.chromium-browser.default.txt"
   
https://bugs.launchpad.net/bugs/1642413/+attachment/479/+files/modified.conffile..etc.chromium-browser.default.txt

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

** Summary changed:

- Chromium uses 100% of all cores, locks up, and does not exit correctly
+ Chromium uses ~100% of all cores, locks up, and does not exit correctly

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

Title:
  Chromium uses ~100% of all cores, locks up, and does not exit
  correctly

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  whether or not extensions are enabled, after an indeterminate amount
  of time chromium locks up(tabs are still rendered but browser cannot
  create new tabs, or navigate in existing ones) and the main process
  begins using 200-270% of my three cores, chrome task manager shows
  that no tab is using any memory and when chromium is exited the main
  thread does not quit and must be killed.

  I have reinstalled, disabled extensions/plugins, etc... nothing seems
  to remedy this issue.

  I memtested my memory and it was fine.

  This issue seems to be triggered every time by paypal virtual
  terminal(paypal.com/vt) mostly, but it happens on other sites randomly
  as well

  It started happening 30-40 days ago
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAi8A4mACANAQOAIht46gyVolZMliUaUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4TB5TDgAKICAgICAg/ABocCBMMTczMAogICAg/wBDTlAzMzJTMFJICiAgALo=
   modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 
800x600 800x600 800x600 640x480 640x480 640x480 720x400
  DRM.card0-VGA-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wA6kwcAAQoRAQMIKxt4CrU0pVZKmiUQUFSvzwCBgIGPlQCVDwEBAQEBAQEBHDmQMGIaJ0BosDYAsQ8RAAAY/gAKICAgICAgICAgICAg/ABNQVctU0VSSUFMCiAg/wAKICAgICAgICAgICAgAHk=
   modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 
1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400
  Desktop-Session:
   'mate'
   '/etc/xdg/xdg-mate:/etc/xdg'
   '/usr/share/mate:/usr/local/share/:/usr/share/:/usr/share/mdm/'
  DistroRelease: Linux 18.1
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2016-07-13 (159 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Load-Avg-1min: 3.87
  Load-Processes-Running-Percent:   0.7%
  MachineType: MSI MS-7786
  Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=5c8e46d1-e26c-4bba-b87b-f092a8a3d7ad ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  Tags: serena third-party-packages
  ThirdParty: True
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev 
sambashare scanner sudo tape vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A55M-P33 (MS-7786)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.0:bd02/04/2013:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P33(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7786
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]
  mtime.conffile..etc.chromium-browser.default: 2016-07-13T18:03:09.849211

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

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

[Desktop-packages] [Bug 1642413] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1642413/+attachment/4794436/+files/ProcInterrupts.txt

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

Title:
  Chromium uses ~100% of all cores, locks up, and does not exit
  correctly

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  whether or not extensions are enabled, after an indeterminate amount
  of time chromium locks up(tabs are still rendered but browser cannot
  create new tabs, or navigate in existing ones) and the main process
  begins using 200-270% of my three cores, chrome task manager shows
  that no tab is using any memory and when chromium is exited the main
  thread does not quit and must be killed.

  I have reinstalled, disabled extensions/plugins, etc... nothing seems
  to remedy this issue.

  I memtested my memory and it was fine.

  This issue seems to be triggered every time by paypal virtual
  terminal(paypal.com/vt) mostly, but it happens on other sites randomly
  as well

  It started happening 30-40 days ago
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAi8A4mACANAQOAIht46gyVolZMliUaUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4TB5TDgAKICAgICAg/ABocCBMMTczMAogICAg/wBDTlAzMzJTMFJICiAgALo=
   modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 
800x600 800x600 800x600 640x480 640x480 640x480 720x400
  DRM.card0-VGA-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wA6kwcAAQoRAQMIKxt4CrU0pVZKmiUQUFSvzwCBgIGPlQCVDwEBAQEBAQEBHDmQMGIaJ0BosDYAsQ8RAAAY/gAKICAgICAgICAgICAg/ABNQVctU0VSSUFMCiAg/wAKICAgICAgICAgICAgAHk=
   modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 
1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400
  Desktop-Session:
   'mate'
   '/etc/xdg/xdg-mate:/etc/xdg'
   '/usr/share/mate:/usr/local/share/:/usr/share/:/usr/share/mdm/'
  DistroRelease: Linux 18.1
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2016-07-13 (159 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Load-Avg-1min: 3.87
  Load-Processes-Running-Percent:   0.7%
  MachineType: MSI MS-7786
  Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=5c8e46d1-e26c-4bba-b87b-f092a8a3d7ad ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  Tags: serena third-party-packages
  ThirdParty: True
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev 
sambashare scanner sudo tape vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A55M-P33 (MS-7786)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.0:bd02/04/2013:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P33(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7786
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]
  mtime.conffile..etc.chromium-browser.default: 2016-07-13T18:03:09.849211

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

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

[Desktop-packages] [Bug 1642413] RelatedPackagesPolicy.txt

apport information

** Attachment added: "RelatedPackagesPolicy.txt"
   
https://bugs.launchpad.net/bugs/1642413/+attachment/4794439/+files/RelatedPackagesPolicy.txt

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

Title:
  Chromium uses ~100% of all cores, locks up, and does not exit
  correctly

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  whether or not extensions are enabled, after an indeterminate amount
  of time chromium locks up(tabs are still rendered but browser cannot
  create new tabs, or navigate in existing ones) and the main process
  begins using 200-270% of my three cores, chrome task manager shows
  that no tab is using any memory and when chromium is exited the main
  thread does not quit and must be killed.

  I have reinstalled, disabled extensions/plugins, etc... nothing seems
  to remedy this issue.

  I memtested my memory and it was fine.

  This issue seems to be triggered every time by paypal virtual
  terminal(paypal.com/vt) mostly, but it happens on other sites randomly
  as well

  It started happening 30-40 days ago
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAi8A4mACANAQOAIht46gyVolZMliUaUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4TB5TDgAKICAgICAg/ABocCBMMTczMAogICAg/wBDTlAzMzJTMFJICiAgALo=
   modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 
800x600 800x600 800x600 640x480 640x480 640x480 720x400
  DRM.card0-VGA-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wA6kwcAAQoRAQMIKxt4CrU0pVZKmiUQUFSvzwCBgIGPlQCVDwEBAQEBAQEBHDmQMGIaJ0BosDYAsQ8RAAAY/gAKICAgICAgICAgICAg/ABNQVctU0VSSUFMCiAg/wAKICAgICAgICAgICAgAHk=
   modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 
1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400
  Desktop-Session:
   'mate'
   '/etc/xdg/xdg-mate:/etc/xdg'
   '/usr/share/mate:/usr/local/share/:/usr/share/:/usr/share/mdm/'
  DistroRelease: Linux 18.1
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2016-07-13 (159 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Load-Avg-1min: 3.87
  Load-Processes-Running-Percent:   0.7%
  MachineType: MSI MS-7786
  Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=5c8e46d1-e26c-4bba-b87b-f092a8a3d7ad ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  Tags: serena third-party-packages
  ThirdParty: True
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev 
sambashare scanner sudo tape vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A55M-P33 (MS-7786)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.0:bd02/04/2013:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P33(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7786
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]
  mtime.conffile..etc.chromium-browser.default: 2016-07-13T18:03:09.849211

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

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

[Desktop-packages] [Bug 1642413] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1642413/+attachment/4794440/+files/UdevDb.txt

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

Title:
  Chromium uses ~100% of all cores, locks up, and does not exit
  correctly

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  whether or not extensions are enabled, after an indeterminate amount
  of time chromium locks up(tabs are still rendered but browser cannot
  create new tabs, or navigate in existing ones) and the main process
  begins using 200-270% of my three cores, chrome task manager shows
  that no tab is using any memory and when chromium is exited the main
  thread does not quit and must be killed.

  I have reinstalled, disabled extensions/plugins, etc... nothing seems
  to remedy this issue.

  I memtested my memory and it was fine.

  This issue seems to be triggered every time by paypal virtual
  terminal(paypal.com/vt) mostly, but it happens on other sites randomly
  as well

  It started happening 30-40 days ago
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAi8A4mACANAQOAIht46gyVolZMliUaUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4TB5TDgAKICAgICAg/ABocCBMMTczMAogICAg/wBDTlAzMzJTMFJICiAgALo=
   modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 
800x600 800x600 800x600 640x480 640x480 640x480 720x400
  DRM.card0-VGA-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wA6kwcAAQoRAQMIKxt4CrU0pVZKmiUQUFSvzwCBgIGPlQCVDwEBAQEBAQEBHDmQMGIaJ0BosDYAsQ8RAAAY/gAKICAgICAgICAgICAg/ABNQVctU0VSSUFMCiAg/wAKICAgICAgICAgICAgAHk=
   modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 
1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400
  Desktop-Session:
   'mate'
   '/etc/xdg/xdg-mate:/etc/xdg'
   '/usr/share/mate:/usr/local/share/:/usr/share/:/usr/share/mdm/'
  DistroRelease: Linux 18.1
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2016-07-13 (159 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Load-Avg-1min: 3.87
  Load-Processes-Running-Percent:   0.7%
  MachineType: MSI MS-7786
  Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=5c8e46d1-e26c-4bba-b87b-f092a8a3d7ad ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  Tags: serena third-party-packages
  ThirdParty: True
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev 
sambashare scanner sudo tape vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A55M-P33 (MS-7786)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.0:bd02/04/2013:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P33(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7786
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]
  mtime.conffile..etc.chromium-browser.default: 2016-07-13T18:03:09.849211

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

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

[Desktop-packages] [Bug 1642413] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1642413/+attachment/4794437/+files/ProcModules.txt

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

Title:
  Chromium uses ~100% of all cores, locks up, and does not exit
  correctly

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  whether or not extensions are enabled, after an indeterminate amount
  of time chromium locks up(tabs are still rendered but browser cannot
  create new tabs, or navigate in existing ones) and the main process
  begins using 200-270% of my three cores, chrome task manager shows
  that no tab is using any memory and when chromium is exited the main
  thread does not quit and must be killed.

  I have reinstalled, disabled extensions/plugins, etc... nothing seems
  to remedy this issue.

  I memtested my memory and it was fine.

  This issue seems to be triggered every time by paypal virtual
  terminal(paypal.com/vt) mostly, but it happens on other sites randomly
  as well

  It started happening 30-40 days ago
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAi8A4mACANAQOAIht46gyVolZMliUaUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4TB5TDgAKICAgICAg/ABocCBMMTczMAogICAg/wBDTlAzMzJTMFJICiAgALo=
   modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 
800x600 800x600 800x600 640x480 640x480 640x480 720x400
  DRM.card0-VGA-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wA6kwcAAQoRAQMIKxt4CrU0pVZKmiUQUFSvzwCBgIGPlQCVDwEBAQEBAQEBHDmQMGIaJ0BosDYAsQ8RAAAY/gAKICAgICAgICAgICAg/ABNQVctU0VSSUFMCiAg/wAKICAgICAgICAgICAgAHk=
   modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 
1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400
  Desktop-Session:
   'mate'
   '/etc/xdg/xdg-mate:/etc/xdg'
   '/usr/share/mate:/usr/local/share/:/usr/share/:/usr/share/mdm/'
  DistroRelease: Linux 18.1
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2016-07-13 (159 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Load-Avg-1min: 3.87
  Load-Processes-Running-Percent:   0.7%
  MachineType: MSI MS-7786
  Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=5c8e46d1-e26c-4bba-b87b-f092a8a3d7ad ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  Tags: serena third-party-packages
  ThirdParty: True
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev 
sambashare scanner sudo tape vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A55M-P33 (MS-7786)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.0:bd02/04/2013:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P33(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7786
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]
  mtime.conffile..etc.chromium-browser.default: 2016-07-13T18:03:09.849211

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

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

[Desktop-packages] [Bug 1642413] etcconfigc10flash.txt

apport information

** Attachment added: "etcconfigc10flash.txt"
   
https://bugs.launchpad.net/bugs/1642413/+attachment/4794442/+files/etcconfigc10flash.txt

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

Title:
  Chromium uses ~100% of all cores, locks up, and does not exit
  correctly

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  whether or not extensions are enabled, after an indeterminate amount
  of time chromium locks up(tabs are still rendered but browser cannot
  create new tabs, or navigate in existing ones) and the main process
  begins using 200-270% of my three cores, chrome task manager shows
  that no tab is using any memory and when chromium is exited the main
  thread does not quit and must be killed.

  I have reinstalled, disabled extensions/plugins, etc... nothing seems
  to remedy this issue.

  I memtested my memory and it was fine.

  This issue seems to be triggered every time by paypal virtual
  terminal(paypal.com/vt) mostly, but it happens on other sites randomly
  as well

  It started happening 30-40 days ago
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAi8A4mACANAQOAIht46gyVolZMliUaUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4TB5TDgAKICAgICAg/ABocCBMMTczMAogICAg/wBDTlAzMzJTMFJICiAgALo=
   modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 
800x600 800x600 800x600 640x480 640x480 640x480 720x400
  DRM.card0-VGA-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wA6kwcAAQoRAQMIKxt4CrU0pVZKmiUQUFSvzwCBgIGPlQCVDwEBAQEBAQEBHDmQMGIaJ0BosDYAsQ8RAAAY/gAKICAgICAgICAgICAg/ABNQVctU0VSSUFMCiAg/wAKICAgICAgICAgICAgAHk=
   modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 
1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400
  Desktop-Session:
   'mate'
   '/etc/xdg/xdg-mate:/etc/xdg'
   '/usr/share/mate:/usr/local/share/:/usr/share/:/usr/share/mdm/'
  DistroRelease: Linux 18.1
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2016-07-13 (159 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Load-Avg-1min: 3.87
  Load-Processes-Running-Percent:   0.7%
  MachineType: MSI MS-7786
  Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=5c8e46d1-e26c-4bba-b87b-f092a8a3d7ad ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  Tags: serena third-party-packages
  ThirdParty: True
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev 
sambashare scanner sudo tape vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A55M-P33 (MS-7786)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.0:bd02/04/2013:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P33(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7786
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]
  mtime.conffile..etc.chromium-browser.default: 2016-07-13T18:03:09.849211

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

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

[Desktop-packages] [Bug 1642413] etcconfigc00example.txt

apport information

** Attachment added: "etcconfigc00example.txt"
   
https://bugs.launchpad.net/bugs/1642413/+attachment/4794441/+files/etcconfigc00example.txt

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

Title:
  Chromium uses ~100% of all cores, locks up, and does not exit
  correctly

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  whether or not extensions are enabled, after an indeterminate amount
  of time chromium locks up(tabs are still rendered but browser cannot
  create new tabs, or navigate in existing ones) and the main process
  begins using 200-270% of my three cores, chrome task manager shows
  that no tab is using any memory and when chromium is exited the main
  thread does not quit and must be killed.

  I have reinstalled, disabled extensions/plugins, etc... nothing seems
  to remedy this issue.

  I memtested my memory and it was fine.

  This issue seems to be triggered every time by paypal virtual
  terminal(paypal.com/vt) mostly, but it happens on other sites randomly
  as well

  It started happening 30-40 days ago
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAi8A4mACANAQOAIht46gyVolZMliUaUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4TB5TDgAKICAgICAg/ABocCBMMTczMAogICAg/wBDTlAzMzJTMFJICiAgALo=
   modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 
800x600 800x600 800x600 640x480 640x480 640x480 720x400
  DRM.card0-VGA-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wA6kwcAAQoRAQMIKxt4CrU0pVZKmiUQUFSvzwCBgIGPlQCVDwEBAQEBAQEBHDmQMGIaJ0BosDYAsQ8RAAAY/gAKICAgICAgICAgICAg/ABNQVctU0VSSUFMCiAg/wAKICAgICAgICAgICAgAHk=
   modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 
1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400
  Desktop-Session:
   'mate'
   '/etc/xdg/xdg-mate:/etc/xdg'
   '/usr/share/mate:/usr/local/share/:/usr/share/:/usr/share/mdm/'
  DistroRelease: Linux 18.1
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2016-07-13 (159 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Load-Avg-1min: 3.87
  Load-Processes-Running-Percent:   0.7%
  MachineType: MSI MS-7786
  Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=5c8e46d1-e26c-4bba-b87b-f092a8a3d7ad ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  Tags: serena third-party-packages
  ThirdParty: True
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev 
sambashare scanner sudo tape vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A55M-P33 (MS-7786)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.0:bd02/04/2013:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P33(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7786
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]
  mtime.conffile..etc.chromium-browser.default: 2016-07-13T18:03:09.849211

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

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

[Desktop-packages] [Bug 1642413] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1642413/+attachment/4794433/+files/Lspci.txt

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

Title:
  Chromium uses ~100% of all cores, locks up, and does not exit
  correctly

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  whether or not extensions are enabled, after an indeterminate amount
  of time chromium locks up(tabs are still rendered but browser cannot
  create new tabs, or navigate in existing ones) and the main process
  begins using 200-270% of my three cores, chrome task manager shows
  that no tab is using any memory and when chromium is exited the main
  thread does not quit and must be killed.

  I have reinstalled, disabled extensions/plugins, etc... nothing seems
  to remedy this issue.

  I memtested my memory and it was fine.

  This issue seems to be triggered every time by paypal virtual
  terminal(paypal.com/vt) mostly, but it happens on other sites randomly
  as well

  It started happening 30-40 days ago
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAi8A4mACANAQOAIht46gyVolZMliUaUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4TB5TDgAKICAgICAg/ABocCBMMTczMAogICAg/wBDTlAzMzJTMFJICiAgALo=
   modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 
800x600 800x600 800x600 640x480 640x480 640x480 720x400
  DRM.card0-VGA-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wA6kwcAAQoRAQMIKxt4CrU0pVZKmiUQUFSvzwCBgIGPlQCVDwEBAQEBAQEBHDmQMGIaJ0BosDYAsQ8RAAAY/gAKICAgICAgICAgICAg/ABNQVctU0VSSUFMCiAg/wAKICAgICAgICAgICAgAHk=
   modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 
1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400
  Desktop-Session:
   'mate'
   '/etc/xdg/xdg-mate:/etc/xdg'
   '/usr/share/mate:/usr/local/share/:/usr/share/:/usr/share/mdm/'
  DistroRelease: Linux 18.1
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2016-07-13 (159 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Load-Avg-1min: 3.87
  Load-Processes-Running-Percent:   0.7%
  MachineType: MSI MS-7786
  Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=5c8e46d1-e26c-4bba-b87b-f092a8a3d7ad ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  Tags: serena third-party-packages
  ThirdParty: True
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev 
sambashare scanner sudo tape vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A55M-P33 (MS-7786)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.0:bd02/04/2013:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P33(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7786
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]
  mtime.conffile..etc.chromium-browser.default: 2016-07-13T18:03:09.849211

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

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

[Desktop-packages] [Bug 1642413] DetectedPlugins.txt

apport information

** Attachment added: "DetectedPlugins.txt"
   
https://bugs.launchpad.net/bugs/1642413/+attachment/4794429/+files/DetectedPlugins.txt

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

Title:
  Chromium uses ~100% of all cores, locks up, and does not exit
  correctly

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  whether or not extensions are enabled, after an indeterminate amount
  of time chromium locks up(tabs are still rendered but browser cannot
  create new tabs, or navigate in existing ones) and the main process
  begins using 200-270% of my three cores, chrome task manager shows
  that no tab is using any memory and when chromium is exited the main
  thread does not quit and must be killed.

  I have reinstalled, disabled extensions/plugins, etc... nothing seems
  to remedy this issue.

  I memtested my memory and it was fine.

  This issue seems to be triggered every time by paypal virtual
  terminal(paypal.com/vt) mostly, but it happens on other sites randomly
  as well

  It started happening 30-40 days ago
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAi8A4mACANAQOAIht46gyVolZMliUaUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4TB5TDgAKICAgICAg/ABocCBMMTczMAogICAg/wBDTlAzMzJTMFJICiAgALo=
   modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 
800x600 800x600 800x600 640x480 640x480 640x480 720x400
  DRM.card0-VGA-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wA6kwcAAQoRAQMIKxt4CrU0pVZKmiUQUFSvzwCBgIGPlQCVDwEBAQEBAQEBHDmQMGIaJ0BosDYAsQ8RAAAY/gAKICAgICAgICAgICAg/ABNQVctU0VSSUFMCiAg/wAKICAgICAgICAgICAgAHk=
   modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 
1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400
  Desktop-Session:
   'mate'
   '/etc/xdg/xdg-mate:/etc/xdg'
   '/usr/share/mate:/usr/local/share/:/usr/share/:/usr/share/mdm/'
  DistroRelease: Linux 18.1
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2016-07-13 (159 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Load-Avg-1min: 3.87
  Load-Processes-Running-Percent:   0.7%
  MachineType: MSI MS-7786
  Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=5c8e46d1-e26c-4bba-b87b-f092a8a3d7ad ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  Tags: serena third-party-packages
  ThirdParty: True
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev 
sambashare scanner sudo tape vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A55M-P33 (MS-7786)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.0:bd02/04/2013:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P33(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7786
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]
  mtime.conffile..etc.chromium-browser.default: 2016-07-13T18:03:09.849211

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

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

[Desktop-packages] [Bug 1642413] JournalErrors.txt

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1642413/+attachment/4794432/+files/JournalErrors.txt

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

Title:
  Chromium uses ~100% of all cores, locks up, and does not exit
  correctly

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  whether or not extensions are enabled, after an indeterminate amount
  of time chromium locks up(tabs are still rendered but browser cannot
  create new tabs, or navigate in existing ones) and the main process
  begins using 200-270% of my three cores, chrome task manager shows
  that no tab is using any memory and when chromium is exited the main
  thread does not quit and must be killed.

  I have reinstalled, disabled extensions/plugins, etc... nothing seems
  to remedy this issue.

  I memtested my memory and it was fine.

  This issue seems to be triggered every time by paypal virtual
  terminal(paypal.com/vt) mostly, but it happens on other sites randomly
  as well

  It started happening 30-40 days ago
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAi8A4mACANAQOAIht46gyVolZMliUaUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4TB5TDgAKICAgICAg/ABocCBMMTczMAogICAg/wBDTlAzMzJTMFJICiAgALo=
   modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 
800x600 800x600 800x600 640x480 640x480 640x480 720x400
  DRM.card0-VGA-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wA6kwcAAQoRAQMIKxt4CrU0pVZKmiUQUFSvzwCBgIGPlQCVDwEBAQEBAQEBHDmQMGIaJ0BosDYAsQ8RAAAY/gAKICAgICAgICAgICAg/ABNQVctU0VSSUFMCiAg/wAKICAgICAgICAgICAgAHk=
   modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 
1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400
  Desktop-Session:
   'mate'
   '/etc/xdg/xdg-mate:/etc/xdg'
   '/usr/share/mate:/usr/local/share/:/usr/share/:/usr/share/mdm/'
  DistroRelease: Linux 18.1
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2016-07-13 (159 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Load-Avg-1min: 3.87
  Load-Processes-Running-Percent:   0.7%
  MachineType: MSI MS-7786
  Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=5c8e46d1-e26c-4bba-b87b-f092a8a3d7ad ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  Tags: serena third-party-packages
  ThirdParty: True
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev 
sambashare scanner sudo tape vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A55M-P33 (MS-7786)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.0:bd02/04/2013:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P33(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7786
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]
  mtime.conffile..etc.chromium-browser.default: 2016-07-13T18:03:09.849211

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

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

[Desktop-packages] [Bug 1642413] Dependencies.txt

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1642413/+attachment/4794428/+files/Dependencies.txt

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

Title:
  Chromium uses ~100% of all cores, locks up, and does not exit
  correctly

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  whether or not extensions are enabled, after an indeterminate amount
  of time chromium locks up(tabs are still rendered but browser cannot
  create new tabs, or navigate in existing ones) and the main process
  begins using 200-270% of my three cores, chrome task manager shows
  that no tab is using any memory and when chromium is exited the main
  thread does not quit and must be killed.

  I have reinstalled, disabled extensions/plugins, etc... nothing seems
  to remedy this issue.

  I memtested my memory and it was fine.

  This issue seems to be triggered every time by paypal virtual
  terminal(paypal.com/vt) mostly, but it happens on other sites randomly
  as well

  It started happening 30-40 days ago
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAi8A4mACANAQOAIht46gyVolZMliUaUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4TB5TDgAKICAgICAg/ABocCBMMTczMAogICAg/wBDTlAzMzJTMFJICiAgALo=
   modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 
800x600 800x600 800x600 640x480 640x480 640x480 720x400
  DRM.card0-VGA-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wA6kwcAAQoRAQMIKxt4CrU0pVZKmiUQUFSvzwCBgIGPlQCVDwEBAQEBAQEBHDmQMGIaJ0BosDYAsQ8RAAAY/gAKICAgICAgICAgICAg/ABNQVctU0VSSUFMCiAg/wAKICAgICAgICAgICAgAHk=
   modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 
1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400
  Desktop-Session:
   'mate'
   '/etc/xdg/xdg-mate:/etc/xdg'
   '/usr/share/mate:/usr/local/share/:/usr/share/:/usr/share/mdm/'
  DistroRelease: Linux 18.1
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2016-07-13 (159 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Load-Avg-1min: 3.87
  Load-Processes-Running-Percent:   0.7%
  MachineType: MSI MS-7786
  Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=5c8e46d1-e26c-4bba-b87b-f092a8a3d7ad ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  Tags: serena third-party-packages
  ThirdParty: True
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev 
sambashare scanner sudo tape vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A55M-P33 (MS-7786)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.0:bd02/04/2013:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P33(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7786
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]
  mtime.conffile..etc.chromium-browser.default: 2016-07-13T18:03:09.849211

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

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

[Desktop-packages] [Bug 1642413] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1642413/+attachment/4794434/+files/Lsusb.txt

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

Title:
  Chromium uses ~100% of all cores, locks up, and does not exit
  correctly

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  whether or not extensions are enabled, after an indeterminate amount
  of time chromium locks up(tabs are still rendered but browser cannot
  create new tabs, or navigate in existing ones) and the main process
  begins using 200-270% of my three cores, chrome task manager shows
  that no tab is using any memory and when chromium is exited the main
  thread does not quit and must be killed.

  I have reinstalled, disabled extensions/plugins, etc... nothing seems
  to remedy this issue.

  I memtested my memory and it was fine.

  This issue seems to be triggered every time by paypal virtual
  terminal(paypal.com/vt) mostly, but it happens on other sites randomly
  as well

  It started happening 30-40 days ago
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAi8A4mACANAQOAIht46gyVolZMliUaUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4TB5TDgAKICAgICAg/ABocCBMMTczMAogICAg/wBDTlAzMzJTMFJICiAgALo=
   modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 
800x600 800x600 800x600 640x480 640x480 640x480 720x400
  DRM.card0-VGA-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wA6kwcAAQoRAQMIKxt4CrU0pVZKmiUQUFSvzwCBgIGPlQCVDwEBAQEBAQEBHDmQMGIaJ0BosDYAsQ8RAAAY/gAKICAgICAgICAgICAg/ABNQVctU0VSSUFMCiAg/wAKICAgICAgICAgICAgAHk=
   modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 
1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400
  Desktop-Session:
   'mate'
   '/etc/xdg/xdg-mate:/etc/xdg'
   '/usr/share/mate:/usr/local/share/:/usr/share/:/usr/share/mdm/'
  DistroRelease: Linux 18.1
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2016-07-13 (159 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Load-Avg-1min: 3.87
  Load-Processes-Running-Percent:   0.7%
  MachineType: MSI MS-7786
  Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=5c8e46d1-e26c-4bba-b87b-f092a8a3d7ad ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  Tags: serena third-party-packages
  ThirdParty: True
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev 
sambashare scanner sudo tape vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A55M-P33 (MS-7786)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.0:bd02/04/2013:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P33(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7786
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]
  mtime.conffile..etc.chromium-browser.default: 2016-07-13T18:03:09.849211

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

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

[Desktop-packages] [Bug 1642413] InstalledPlugins.txt

apport information

** Attachment added: "InstalledPlugins.txt"
   
https://bugs.launchpad.net/bugs/1642413/+attachment/4794431/+files/InstalledPlugins.txt

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

Title:
  Chromium uses ~100% of all cores, locks up, and does not exit
  correctly

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  whether or not extensions are enabled, after an indeterminate amount
  of time chromium locks up(tabs are still rendered but browser cannot
  create new tabs, or navigate in existing ones) and the main process
  begins using 200-270% of my three cores, chrome task manager shows
  that no tab is using any memory and when chromium is exited the main
  thread does not quit and must be killed.

  I have reinstalled, disabled extensions/plugins, etc... nothing seems
  to remedy this issue.

  I memtested my memory and it was fine.

  This issue seems to be triggered every time by paypal virtual
  terminal(paypal.com/vt) mostly, but it happens on other sites randomly
  as well

  It started happening 30-40 days ago
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAi8A4mACANAQOAIht46gyVolZMliUaUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4TB5TDgAKICAgICAg/ABocCBMMTczMAogICAg/wBDTlAzMzJTMFJICiAgALo=
   modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 
800x600 800x600 800x600 640x480 640x480 640x480 720x400
  DRM.card0-VGA-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wA6kwcAAQoRAQMIKxt4CrU0pVZKmiUQUFSvzwCBgIGPlQCVDwEBAQEBAQEBHDmQMGIaJ0BosDYAsQ8RAAAY/gAKICAgICAgICAgICAg/ABNQVctU0VSSUFMCiAg/wAKICAgICAgICAgICAgAHk=
   modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 
1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400
  Desktop-Session:
   'mate'
   '/etc/xdg/xdg-mate:/etc/xdg'
   '/usr/share/mate:/usr/local/share/:/usr/share/:/usr/share/mdm/'
  DistroRelease: Linux 18.1
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2016-07-13 (159 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Load-Avg-1min: 3.87
  Load-Processes-Running-Percent:   0.7%
  MachineType: MSI MS-7786
  Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=5c8e46d1-e26c-4bba-b87b-f092a8a3d7ad ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  Tags: serena third-party-packages
  ThirdParty: True
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev 
sambashare scanner sudo tape vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A55M-P33 (MS-7786)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.0:bd02/04/2013:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P33(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7786
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]
  mtime.conffile..etc.chromium-browser.default: 2016-07-13T18:03:09.849211

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

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

[Desktop-packages] [Bug 1642413] DiskUsage.txt

apport information

** Attachment added: "DiskUsage.txt"
   
https://bugs.launchpad.net/bugs/1642413/+attachment/4794430/+files/DiskUsage.txt

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

Title:
  Chromium uses ~100% of all cores, locks up, and does not exit
  correctly

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  whether or not extensions are enabled, after an indeterminate amount
  of time chromium locks up(tabs are still rendered but browser cannot
  create new tabs, or navigate in existing ones) and the main process
  begins using 200-270% of my three cores, chrome task manager shows
  that no tab is using any memory and when chromium is exited the main
  thread does not quit and must be killed.

  I have reinstalled, disabled extensions/plugins, etc... nothing seems
  to remedy this issue.

  I memtested my memory and it was fine.

  This issue seems to be triggered every time by paypal virtual
  terminal(paypal.com/vt) mostly, but it happens on other sites randomly
  as well

  It started happening 30-40 days ago
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAi8A4mACANAQOAIht46gyVolZMliUaUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4TB5TDgAKICAgICAg/ABocCBMMTczMAogICAg/wBDTlAzMzJTMFJICiAgALo=
   modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 
800x600 800x600 800x600 640x480 640x480 640x480 720x400
  DRM.card0-VGA-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wA6kwcAAQoRAQMIKxt4CrU0pVZKmiUQUFSvzwCBgIGPlQCVDwEBAQEBAQEBHDmQMGIaJ0BosDYAsQ8RAAAY/gAKICAgICAgICAgICAg/ABNQVctU0VSSUFMCiAg/wAKICAgICAgICAgICAgAHk=
   modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 
1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400
  Desktop-Session:
   'mate'
   '/etc/xdg/xdg-mate:/etc/xdg'
   '/usr/share/mate:/usr/local/share/:/usr/share/:/usr/share/mdm/'
  DistroRelease: Linux 18.1
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2016-07-13 (159 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Load-Avg-1min: 3.87
  Load-Processes-Running-Percent:   0.7%
  MachineType: MSI MS-7786
  Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=5c8e46d1-e26c-4bba-b87b-f092a8a3d7ad ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  Tags: serena third-party-packages
  ThirdParty: True
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev 
sambashare scanner sudo tape vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A55M-P33 (MS-7786)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.0:bd02/04/2013:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P33(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7786
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]
  mtime.conffile..etc.chromium-browser.default: 2016-07-13T18:03:09.849211

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

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

[Desktop-packages] [Bug 1642413] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1642413/+attachment/4794427/+files/CurrentDmesg.txt

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

Title:
  Chromium uses ~100% of all cores, locks up, and does not exit
  correctly

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  whether or not extensions are enabled, after an indeterminate amount
  of time chromium locks up(tabs are still rendered but browser cannot
  create new tabs, or navigate in existing ones) and the main process
  begins using 200-270% of my three cores, chrome task manager shows
  that no tab is using any memory and when chromium is exited the main
  thread does not quit and must be killed.

  I have reinstalled, disabled extensions/plugins, etc... nothing seems
  to remedy this issue.

  I memtested my memory and it was fine.

  This issue seems to be triggered every time by paypal virtual
  terminal(paypal.com/vt) mostly, but it happens on other sites randomly
  as well

  It started happening 30-40 days ago
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAi8A4mACANAQOAIht46gyVolZMliUaUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4TB5TDgAKICAgICAg/ABocCBMMTczMAogICAg/wBDTlAzMzJTMFJICiAgALo=
   modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 
800x600 800x600 800x600 640x480 640x480 640x480 720x400
  DRM.card0-VGA-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wA6kwcAAQoRAQMIKxt4CrU0pVZKmiUQUFSvzwCBgIGPlQCVDwEBAQEBAQEBHDmQMGIaJ0BosDYAsQ8RAAAY/gAKICAgICAgICAgICAg/ABNQVctU0VSSUFMCiAg/wAKICAgICAgICAgICAgAHk=
   modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 
1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400
  Desktop-Session:
   'mate'
   '/etc/xdg/xdg-mate:/etc/xdg'
   '/usr/share/mate:/usr/local/share/:/usr/share/:/usr/share/mdm/'
  DistroRelease: Linux 18.1
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2016-07-13 (159 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Load-Avg-1min: 3.87
  Load-Processes-Running-Percent:   0.7%
  MachineType: MSI MS-7786
  Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=5c8e46d1-e26c-4bba-b87b-f092a8a3d7ad ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  Tags: serena third-party-packages
  ThirdParty: True
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev 
sambashare scanner sudo tape vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A55M-P33 (MS-7786)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.0:bd02/04/2013:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P33(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7786
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]
  mtime.conffile..etc.chromium-browser.default: 2016-07-13T18:03:09.849211

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

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

[Desktop-packages] [Bug 1642413] Re: Chromium uses 100% of all cores, locks up, and does not exit correctly

apport information

** Attachment removed: "ChromiumPrefs.txt"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1642413/+attachment/4778841/+files/ChromiumPrefs.txt

** Attachment removed: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1642413/+attachment/4778842/+files/CurrentDmesg.txt

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1642413/+attachment/4778843/+files/Dependencies.txt

** Attachment removed: "DiskUsage.txt"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1642413/+attachment/4778845/+files/DiskUsage.txt

** Attachment removed: "DetectedPlugins.txt"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1642413/+attachment/4778844/+files/DetectedPlugins.txt

** Attachment removed: "InstalledPlugins.txt"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1642413/+attachment/4778846/+files/InstalledPlugins.txt

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1642413/+attachment/4778847/+files/JournalErrors.txt

** Attachment removed: "Lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1642413/+attachment/4778848/+files/Lspci.txt

** Attachment removed: "Lsusb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1642413/+attachment/4778849/+files/Lsusb.txt

** Attachment removed: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1642413/+attachment/4778850/+files/ProcCpuinfo.txt

** Attachment removed: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1642413/+attachment/4778851/+files/ProcInterrupts.txt

** Attachment removed: "ProcModules.txt"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1642413/+attachment/4778852/+files/ProcModules.txt

** Attachment removed: "RelatedPackageVersions.txt"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1642413/+attachment/4778853/+files/RelatedPackageVersions.txt

** Attachment removed: "RelatedPackagesPolicy.txt"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1642413/+attachment/4778854/+files/RelatedPackagesPolicy.txt

** Attachment removed: "UdevDb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1642413/+attachment/4778855/+files/UdevDb.txt

** Attachment removed: "etcconfigc00example.txt"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1642413/+attachment/4778856/+files/etcconfigc00example.txt

** Attachment removed: "etcconfigc10flash.txt"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1642413/+attachment/4778857/+files/etcconfigc10flash.txt

** Attachment removed: "gconf-keys.txt"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1642413/+attachment/4778858/+files/gconf-keys.txt

** Attachment removed: "modified.conffile..etc.chromium-browser.default.txt"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1642413/+attachment/4778859/+files/modified.conffile..etc.chromium-browser.default.txt

** Description changed:

  whether or not extensions are enabled, after an indeterminate amount of
  time chromium locks up(tabs are still rendered but browser cannot create
  new tabs, or navigate in existing ones) and the main process begins
  using 200-270% of my three cores, chrome task manager shows that no tab
  is using any memory and when chromium is exited the main thread does not
  quit and must be killed.
  
  I have reinstalled, disabled extensions/plugins, etc... nothing seems to
  remedy this issue.
  
+ I memtested my memory and it was fine.
+ 
+ This issue seems to be triggered every time by paypal virtual
+ terminal(paypal.com/vt) mostly, but it happens on other sites randomly
+ as well
+ 
  It started happening 30-40 days ago
- --- 
- ApportVersion: 2.20.1-0ubuntu2.1
- Architecture: amd64
- CrashDB: ubuntu
- CurrentDesktop: MATE
- DRM.card0-HDMI-A-1:
-  edid-base64: 
AP///wAi8A4mACANAQOAIht46gyVolZMliUaUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4TB5TDgAKICAgICAg/ABocCBMMTczMAogICAg/wBDTlAzMzJTMFJICiAgALo=
-  dpms: On
-  modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 
800x600 800x600 800x600 640x480 640x480 640x480 720x400
-  enabled: enabled
-  status: connected
- DRM.card0-VGA-1:
-  edid-base64: 
AP///wA6kwcAAQoRAQMIKxt4CrU0pVZKmiUQUFSvzwCBgIGPlQCVDwEBAQEBAQEBHDmQMGIaJ0BosDYAsQ8RAAAY/gAKICAgICAgICAgICAg/ABNQVctU0VSSUFMCiAg/wAKICAgICAgICAgICAgAHk=
-  dpms: On
-  modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 
1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400
-  enabled: enabled
-  status: connected
- Desktop-Session:
-  'mate'
-  '/etc/xdg/xdg-mate:/etc/xdg'
-

[Desktop-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

2016-12-20 Thread Mohamed A.

I updated to 4.9.0 kernel. Bug still persisting.

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

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

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1396378] Re: evince does not follow Xubuntu scroll direction

2016-12-20 Thread Aaron

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

For me, all applications (chromium, gnucash, perhaps a couple others)
scroll in a certain way: when I put two fingers on the touch pad and go
up, they scroll up. Evince does the opposite, and it is the only
application I have found that does that.

This is marked as a duplicate of another issue that speaks of "all gtk3
apps", but for me, evince is the only one acting differently from the
others. I don't know which way is "natural scrolling", but perhaps
Evince has "fixed" the problem where it doesn't "naturally scroll" by
always naturally scrolling regardless of other settings?

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

Title:
  evince does not follow Xubuntu scroll direction

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  Setting Scroll direction to reverse (Natural scrolling) in xfce4
  -mouse-settings works great for all applications except for evince.
  Same effect for both USB mouse and Touchpad.

  The same effect is observed when using this method:
  xinput set-button-map 11 1 2 3 5 4 7 6 8 9 10 11 12

  I was able to kind of get a workaround using Option
  "ZAxisMapping"  "5 4" in xorg.conf but it messed up my mouse speed
  pretty bad and xfce4-mouse-settings stopped working. (duplicate
  entries, settings did not take effect).

  On Xubuntu 14.04, evince 3.10.3, xfce4-mouse-settings 4.11.2 (Xfce
  4.10). Have not tested other distributions.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evince 3.10.3-0ubuntu10.1
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Nov 25 17:56:35 2014
  InstallationDate: Installed on 2014-09-07 (79 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140723)
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1573755] Re: Compose and dead keys stopped working with XIM after upgrade to 16.04

2016-12-20 Thread Bas Roufs

Hello Everybody.

At this dead keys problem, I stumble upon now - however, so far, just in
LibreOffice. Ever since a few weeks, I work at a fresh install of
Kubuntu 16.04 - along with KDE Plasma 5.6.5, installed via the Kubuntu
ppa backports. Dead keys work in all applications except LibreOffice -
version 5.1.4.2. I am using the keyboard "USA International". A
character like ä is no problem in most of the applications. They same
applies for e.g. the double quotation mark (") - the key that needs to
be pressed first in order to get ä. However, in Libreoffice in my
configuration as summarised here, signs like " and ä do not show up. I
have similar problems with characters like à, é, ë, ñ. č, etc. Also
signs like `, ~ or ' do not show up in Writer or any other Libreoffice
application. It does not matter whether I work in Dutch, English,
Italian, French, German or whatever - the problem remains the same -
however, as I said, just in LibreOffice.


The only workaround I have found so far is editing a text in another 
application (Kate, BlueFish or whatever) and copy-pasting it into LibreOffice.  
The workaround mentioned in comment 6 does not work here. I DO manage to invoke 
libreoffice from the command line -  "libreoffice" does end up in the following 
sequence:



bas@Viaconsensus-transit:~$ unset XMODIFIERS && libreoffice &
[1] 5908
bas@Viaconsensus-transit:~$ W: Unknown node under /registry/extlang: deprecated
W: Unknown node under /registry/grandfathered: comments
W: Unknown node under /registry/grandfathered: comments
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode: 42 (X_SetInputFocus)
  Resource id:  0x7c02342




However, the problem is not being fixed like this.

Variants like "libreoffice4.2" or "libreoffice5" do not produce any result.
On the other hand - the simple command line command "libreoffice", without 
anything else, is already enough to invoke that application. During my main 
working session of today, Tuesday 20 December 2016, I have done so by purpose. 
Here is the report I get from this working session. 

===

bas@Viaconsensus-transit:~$ libreoffice
W: Unknown node under /registry/extlang: deprecated
W: Unknown node under /registry/grandfathered: comments
W: Unknown node under /registry/grandfathered: comments
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode: 42 (X_SetInputFocus)
  Resource id:  0x7404614
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode: 42 (X_SetInputFocus)
  Resource id:  0x7406fbd
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode: 42 (X_SetInputFocus)
  Resource id:  0x74079cf
Connecting to deprecated signal 
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QDBusConnection: session D-Bus connection created before QCoreApplication. 
Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. 
Application may misbehave.
kbuildsycoca4 running...
LibreOffice(2110) KSambaSharePrivate::findSmbConf: KSambaShare: Could not find 
smb.conf! 
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode: 42 (X_SetInputFocus)
  Resource id:  0x741bbd6
bas@Viaconsensus-transit:~$ libreoffice
W: Unknown node under /registry/extlang: deprecated
W: Unknown node under /registry/grandfathered: comments
W: Unknown node under /registry/grandfathered: comments
LibreOffice(3111) KSambaSharePrivate::findSmbConf: KSambaShare: Could not find 
smb.conf! 
bas@Viaconsensus-transit:~$ 


=

Does someone know any other fix or effective workaround, apart from
copy-paste?

Yours.

Bas G. Roufs.

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

Title:
  Compose and dead keys stopped working with XIM after upgrade to 16.04

Status in firefox package in Ubuntu:
  Invalid
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in ibus package in Ubuntu:
  Confirmed
Status in libx11 package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Invalid
Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.04, entering characters using dead keys and
  using the Compose key stopped working in Gnome Terminal, acting like
  they are normal (non-dead) keys.

  Other applications, even those who use the same libvte (e.g. ROXTerm),
  don't have this issue.

  This happens with both the "Belgian" and "English international with
  AltGr dead keys" layouts.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-terminal 3.18.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64

[Desktop-packages] [Bug 1651575] Re: goa-daemon starts broken

https://bugzilla.redhat.com/show_bug.cgi?id=1350678

** Project changed: ubuntu-gnome => gnome-online-accounts (Ubuntu)

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

Title:
  goa-daemon starts broken

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

Bug description:
  goa-daemon, that is started with GNOME Shell/Wayland on login, on
  16.10 launches in a corrupt state where all authentication fails.

  This can be seen by launching Evolution which fails to use credential
  from goa.

  GETAROUND
  restart goa

  killall goa-daemon

  - goa-daemon retarts by itself
  - authentication now works

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-online-accounts 3.22.2-1~ubuntu16.10.1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Dec 20 12:17:37 2016
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to yakkety on 2016-11-16 (34 days ago)

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

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

[Desktop-packages] [Bug 1651575] [NEW] goa-daemon starts broken

You have been subscribed to a public bug:

goa-daemon, that is started with GNOME Shell/Wayland on login, on 16.10
launches in a corrupt state where all authentication fails.

This can be seen by launching Evolution which fails to use credential
from goa.

GETAROUND
restart goa

killall goa-daemon

- goa-daemon retarts by itself
- authentication now works

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: gnome-online-accounts 3.22.2-1~ubuntu16.10.1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
Uname: Linux 4.8.0-30-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Dec 20 12:17:37 2016
SourcePackage: gnome-online-accounts
UpgradeStatus: Upgraded to yakkety on 2016-11-16 (34 days ago)

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


** Tags: amd64 apport-bug gnome3-ppa gnome3-staging third-party-packages 
wayland-session yakkety
-- 
goa-daemon starts broken
https://bugs.launchpad.net/bugs/1651575
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-online-accounts in Ubuntu.

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

[Desktop-packages] [Bug 1650730] Re: streaming, H.264 doesn't work in Chromium codecs

Here is the youtube test page that indicates if h.264 is working

https://www.youtube.com/html5
- if Chromium is broken, H.264 and MSE & H.264 are red.


And here is a test of the video tag capabilities:

http://www.quirksmode.org/html5/tests/video.html
- if Chromium is broken, the H.264/MP4 video is not playing

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

Title:
  streaming, H.264 doesn't work in Chromium codecs

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  After upgrading chromium from 53.0.2785.143-0ubuntu1.1307 to 
55.0.2883.87-0ubuntu0.16.10.1328 google music 
(https://play.google.com/music/listen#/home) does not work and show me this:
  Missing Flash Player
  You need the latest Adobe Flash Player to listen to music.

  Note: I have never had adobe flash installed:
  $ dpkg -l | grep "adobe\|flash"
  ii  kwordquiz   4:16.04.3-0ubuntu1   amd64   flashcard learning program
  $

  and it worked an hour ago (before updating)!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: chromium-browser 55.0.2883.87-0ubuntu0.16.10.1328
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Dec 17 12:26:57 2016
  Desktop-Session:
   '/usr/share/xsessions/plasma'
   
'/etc/xdg/xdg-/usr/share/xsessions/plasma:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings'
   
'/usr/share//usr/share/xsessions/plasma:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2014-07-05 (895 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.1)
  Load-Avg-1min: 1.36
  Load-Processes-Running-Percent:   0.3%
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic.efi.signed 
root=UUID=6cdd6da7-49a5-4892-8a76-48d290860bcf ro acpi=force apm=power_off 
quiet splash vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to yakkety on 2016-10-09 (68 days ago)
  dmi.bios.date: 01/07/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0701
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X79-DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0701:bd01/07/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX79-DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1650796] Re: Black image (no video) with Live! Cam Connect HD VF0750 with some exceptions

2016-12-20 Thread Vincas Dargis

OK I'll try that on this weekend.

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

Title:
  Black image (no video) with Live! Cam Connect HD VF0750 with some
  exceptions

Status in cheese package in Ubuntu:
  Incomplete

Bug description:
  After upgrading my Inspiron 6400 laptop (32-bit) from 14.04 to 16.04,
  launching Cheese with  Live! Cam Connect HD VF0750 webcam *sometimes*
  (randomly) gives no video, only black image. No errors are reported on
  GUI, console, or syslog.

  You can start Cheese again and it might start video, but sometimes
  not, randomly. In case when there is no image, opening Settings and
  changing resolution makes video appear!

  Tried to downgrade libv4l-0, libv4lconvert0 to 14.04 version (1.0.1 I
  believe) but it did not helped. Upgrading to Linux 4.8 (from hwe
  package) did not helped either.

  On other laptop with Ubuntu 14.04 (with same 4.4 kernel from hwe
  package) there is no issues as such, so I assume it's bug with Cheese
  itself.

  Interestingly, on yet other laptop (Asus N551JM) with Kubuntu 16.04
  Cheese does not show video on launch always (tested with many restarts
  of Cheese app). If I change resolution in Settings, it does start to
  show video thought. That computer is faster than Dell 6400 one, so I'm
  guessing it could be some kind race condition..?

  I cannot reproduce this issue with Camorama for example, it seems it
  always starts video successfully for this webcam.

  ---
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  petras 2060 F pulseaudio
   /dev/snd/controlC0:  petras 2060 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2011-11-23 (1851 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  MachineType: Dell Inc. MM061
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=b57d1858-e7f3-42a3-a7ef-5e7ab8dd5ae4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-30-generic N/A
   linux-backports-modules-4.8.0-30-generic  N/A
   linux-firmware1.157.6
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.8.0-30-generic i686
  UpgradeStatus: Upgraded to xenial on 2016-11-19 (28 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare uucp
  _MarkForUpload: True
  dmi.bios.date: 06/09/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0KD882
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd06/09/2006:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0KD882:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: MM061
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1323594] Re: vpn auto-connect works, but doesn't connect automatically when network is available.

2016-12-20 Thread johnnynobody

I'm having this problem with an ethernet connection and openvpn on
Ubuntu 16.04.01 LTS. When booting or rebooting, the network won't come
up at all. But, if I select "Disconnect VPN" the network comes up. After
the network comes up, I can enable the VPN and the client connects to
the server.

network-manager 1.2.2-0ubuntu0.16.04.3
network-manager-openvpn 1.1.93-1ubuntu1
openvpn 2.3.10-1ubuntu2

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

Title:
  vpn auto-connect works, but doesn't connect automatically when network
  is available.

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  I'm having a bug in Ubuntu Trusty Tahr 14.04 LTS. The issue I'm having
  is that with a connection set to auto-connect to a PPTP-vpn, it does
  not auto-connect when (wireless)-network becomes available.

  Syslog returns this error:

   [1401130450.367538] [nm-vpn-connection.c:1374]
  get_secrets_cb(): Failed to request VPN secrets #2: (6) No agents were
  available for this request.

  However it does connect when when connecting to the particular
  connection manually. e.g. I select the wireless network in the
  network-manager.

  This bug seems related to bugs:
  #280571
  #1297849
  #1247682 
  #1298047

  The difference between my situation and the others is that vpn-
  autoconnect does work, it just doesn't work automatically.

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

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

[Desktop-packages] [Bug 1649307] Re: LibreOffice Does Not Bring Windows to Front on GNOME/Wayland

This might be fixed by one of the mutter commits since 3.22.2

https://git.gnome.org//browse/mutter/log?h=gnome-3-22

I'll go ahead and assign this one to mutter for now.

** Package changed: libreoffice (Ubuntu) => mutter (Ubuntu)

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

Title:
  LibreOffice  Does Not Bring Windows to Front on GNOME/Wayland

Status in mutter package in Ubuntu:
  New

Bug description:
  SYMPTOM 1:
  Have two Writer windows open
  In one of the Writer windows:
  LibreOffice Writer - Window - select the other Window

  BUG1
  The other Window is not brought to front.
  LibreOffice cannot do this anymore, it worked in 16.04

  GETAROUND1
  Use GNOME Overview (Super key) to pick the LibreOffice window

  SYMPTOM 2:
  In a Writer window, select LibreOffice - Styles - Styles and Formatting F11
  click on a non-LibreOffice window
  click back on the LibreOffice window
  BUG
  Styles and formatting is no longer shown, the dialog is gone

  GTEAROUND2
  Click on another LibreOffice window
  click back on the LibreOffice window
  - Styles and Formatti gdialog appears

  SYMPTOM 3
  In STyles and Formatting dialog, elect New Style… - Load Styles…
  BUG
  Load Styles dialog is a popunder appearing below Styles and Formatting

  GETAROUND3
  Click on a non-LibreOffice window
  Click back on the LibreOffice window
  - Load Styles is now at tnhe front
  (this is using BUG2 to hide Styles and Formatting dialog)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libreoffice 1:5.2.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Dec 12 06:54:51 2016
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to yakkety on 2016-11-16 (25 days ago)

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

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

[Desktop-packages] [Bug 1650730] Re: streaming, H.264 doesn't work in Chromium codecs

The GETAROUND is to downgrade:

apt-get install chromium-browser=53.0.2785.143-0ubuntu1.1307 
chromium-codecs-ffmpeg-extra=53.0.2785.143-0ubuntu1.1307
apt-mark hold chromium-browser

- and then remember to do
apt-mark unhold chromium-browser
once the problem is fixed

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

Title:
  streaming, H.264 doesn't work in Chromium codecs

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  After upgrading chromium from 53.0.2785.143-0ubuntu1.1307 to 
55.0.2883.87-0ubuntu0.16.10.1328 google music 
(https://play.google.com/music/listen#/home) does not work and show me this:
  Missing Flash Player
  You need the latest Adobe Flash Player to listen to music.

  Note: I have never had adobe flash installed:
  $ dpkg -l | grep "adobe\|flash"
  ii  kwordquiz   4:16.04.3-0ubuntu1   amd64   flashcard learning program
  $

  and it worked an hour ago (before updating)!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: chromium-browser 55.0.2883.87-0ubuntu0.16.10.1328
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Dec 17 12:26:57 2016
  Desktop-Session:
   '/usr/share/xsessions/plasma'
   
'/etc/xdg/xdg-/usr/share/xsessions/plasma:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings'
   
'/usr/share//usr/share/xsessions/plasma:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2014-07-05 (895 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.1)
  Load-Avg-1min: 1.36
  Load-Processes-Running-Percent:   0.3%
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic.efi.signed 
root=UUID=6cdd6da7-49a5-4892-8a76-48d290860bcf ro acpi=force apm=power_off 
quiet splash vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to yakkety on 2016-10-09 (68 days ago)
  dmi.bios.date: 01/07/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0701
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X79-DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0701:bd01/07/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX79-DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 237819] Re: Transfer of focus to Find/Replace dialog in Eclipse is considered focus stealing by Compiz

2016-12-20 Thread Bug Watch Updater

Launchpad has imported 7 comments from the remote bug at
https://bugs.eclipse.org/bugs/show_bug.cgi?id=235965.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-06-06T04:31:07+00:00 Tristan Schmelcher wrote:

Build ID: M20071023-1652

Steps To Reproduce:
1. On a Linux machine that uses Compiz (in my case Ubuntu Hardy 32-bit), turn 
on focus stealing prevention with any strength. (Install 
compizconfig-settings-manager, then go to System -> Preferences -> Advanced 
Desktop Effects Settings -> General Options -> Focus & Raise Behaviour.)
2. Open an editor window in Eclipse.
3. Press Ctrl+F to show the Find/Replace dialog.
  => The dialog gets focus, as expected.
4. Click on the editor to transfer focus back to it.
5. Press Ctrl+F again with the Find/Replace dialog already open.
  => Although the "Find:" text field gets focus, the actual Find/Replace window 
does not, so that if you try to type then the keypresses go nowhere.

Expected:

When Ctrl+F is pressed, the Find/Replace window should always get focus.

More information:

The bug does not occur if Compiz's focus stealing prevention is turned
off.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/237819/comments/0


On 2008-06-06T05:04:44+00:00 Tristan Schmelcher wrote:

Also opened with Ubuntu at
https://bugs.launchpad.net/eclipse/+bug/237819.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/237819/comments/2


On 2008-06-08T19:41:59+00:00 Daniel-megert wrote:

Moving to SWT as this works on other known platforms. Might be
NON_ECLIPSE.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/237819/comments/3


On 2008-12-22T18:59:24+00:00 Gheorghe-ca wrote:

Praveen to investigate on his Ubunutu.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/237819/comments/8


On 2009-02-06T20:09:04+00:00 Pinnamur wrote:

I had turned ON the compiz focus stealing prevention, but couldn't notice the 
reported behavior against the latest level (GTK 2.14.x). The Find dialog always 
gets focus after repeated attempts.
This can be closed if the reported problem no longer appears. 
If you are still seeing the problem, Can you please provide the GTK version 
against which the problem is noticed?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/237819/comments/9


On 2009-06-24T02:51:29+00:00 Tristan Schmelcher wrote:

The problem now only occurs if the focus stealing prevention level is
set to Very High, which I would say is not a bug. However, when set to
that level, the issue with keypresses going nowhere is still present,
which _is_ a bug.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/237819/comments/12


On 2016-12-20T17:44:34+00:00 Ericwill wrote:

Behavior is fixed from a GTK2 version that is now out of date, as per
comment 4.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/237819/comments/15


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

** Changed in: eclipse
   Importance: Unknown => Low

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

Title:
  Transfer of focus to Find/Replace dialog in Eclipse is considered
  focus stealing by Compiz

Status in Eclipse:
  Invalid
Status in compiz package in Ubuntu:
  Fix Released
Status in eclipse package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: compiz

  In Eclipse, the Find/Replace dialog automatically gains focus when it
  is opened, or when you press Ctrl+F while it is already open. However,
  Compiz considers this latter case to be focus stealing (even when
  focus stealing prevention is set to "Low"), despite the fact that both
  windows are part of the same app and the transfer is in response to a
  user action.

  Repro steps:

  1) Enable Compiz, then install compizconfig-settings-manager and enable focus 
stealing prevention in System -> Preferences -> Advanced
  Desktop Effects Settings -> General Options -> Focus & Raise Behaviour.
  2) Install Eclipse, open it, and open an editor window.
  3) Press Ctrl+F to show the Find/Replace dialog.
=> The dialog gets focus, as expected.
  4) Click on the editor to transfer focus back to it.
  5) Press Ctrl+F again with the Find/Replace

[Desktop-packages] [Bug 1649307] Re: LibreOffice Does Not Bring Windows to Front on GNOME/Wayland

with mutter version 3.22.2-2ubuntu1~ubuntu16.10.1 from
http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu

This is now a freeze:

If you try to close a pop-under dialog, lik the Load Styles dialog,
GNOME Shell freezes

GETAROUND
If you instead select Writer - Styles - Load Styles… it works, because there is 
only one level of dialogs
With two levels of dialogs, the second level is a popunder that
a. cannot be accessed because it is below the first dialog
b. freezes GNOME Shell on attempt to close it

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

Title:
  LibreOffice  Does Not Bring Windows to Front on GNOME/Wayland

Status in libreoffice package in Ubuntu:
  New

Bug description:
  SYMPTOM 1:
  Have two Writer windows open
  In one of the Writer windows:
  LibreOffice Writer - Window - select the other Window

  BUG1
  The other Window is not brought to front.
  LibreOffice cannot do this anymore, it worked in 16.04

  GETAROUND1
  Use GNOME Overview (Super key) to pick the LibreOffice window

  SYMPTOM 2:
  In a Writer window, select LibreOffice - Styles - Styles and Formatting F11
  click on a non-LibreOffice window
  click back on the LibreOffice window
  BUG
  Styles and formatting is no longer shown, the dialog is gone

  GTEAROUND2
  Click on another LibreOffice window
  click back on the LibreOffice window
  - Styles and Formatti gdialog appears

  SYMPTOM 3
  In STyles and Formatting dialog, elect New Style… - Load Styles…
  BUG
  Load Styles dialog is a popunder appearing below Styles and Formatting

  GETAROUND3
  Click on a non-LibreOffice window
  Click back on the LibreOffice window
  - Load Styles is now at tnhe front
  (this is using BUG2 to hide Styles and Formatting dialog)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libreoffice 1:5.2.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Dec 12 06:54:51 2016
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to yakkety on 2016-11-16 (25 days ago)

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

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

[Desktop-packages] [Bug 1650684] Re: Position of gnome-system-monitor is not remembered on screen when under Wayland

2016-12-20 Thread Nikita Yerenkov-Scott

** Bug watch added: GNOME Bug Tracker #776321
   https://bugzilla.gnome.org/show_bug.cgi?id=776321

** Also affects: gnome-shell via
   https://bugzilla.gnome.org/show_bug.cgi?id=776321
   Importance: Unknown
   Status: Unknown

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

Title:
  Position of gnome-system-monitor is not remembered on screen when
  under Wayland

Status in gnome-shell:
  Unknown
Status in Ubuntu GNOME:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in gnome-system-monitor package in Ubuntu:
  New

Bug description:
  I am running Ubuntu GNOME 16.10 with GNOME 3.22 and since switching
  from Xorg to Wayland via the login screen I have noticed that with the
  gnome-system-monitor that it always starts off on the left hand side
  of the screen, and I like to have it on the right hand side, so that
  is where I always put it. However, if I restart it, it always goes
  back to the left side rather than remembering where it was before like
  it does if I close it when it is fullscreen.

  So far it seems that this issue only affects the gnome-system-monitor,
  all other applications behave as expected in regards to this matter.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-shell 3.22.2-1ubuntu1~ubuntu16.10.1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec 16 22:26:09 2016
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-05-15 (215 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to yakkety on 2016-10-19 (58 days ago)

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

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

[Desktop-packages] [Bug 1606078] Re: No sound with Ubuntu 16.04

2016-12-20 Thread Al Thomason

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

Luke Yelavich (themuso) wrote on 2016-09-16:
"Could anybody affected by this bug please try upgrading the HDA audio driver, 
as outlined here. https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS.

If you have made changes to files in /etc/modprobe.d as suggested above,
please undo those changes prior to updating."

==

Today I tried this, and no change.  Currently sound will come from headphones, 
but not speakers.
Dell 5510 - OEM 14.04lts upgraded to 16.04lts.

Edit in step #5 did not help (I have backed it out).   Not sure what
else I can do to help solve this issue, please ask (trying to make run
at Linux again)

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

Title:
  No sound with Ubuntu 16.04

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  After a fresh install of Ubuntu 16.04.1 on an LG S1 Express Dual
  laptop there was no sound from the speakers unless external speakers
  where hooked to the headphones socket. This applies to the Ubuntu
  Mate, Xubuntu and Lubuntu variants. This laptop was working fine for
  all previous releases up to 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bashar 3263 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul 25 01:51:19 2016
  InstallationDate: Installed on 2016-07-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bashar 3263 F pulseaudio
  Symptom_Jack: Line Out, Internal
  Symptom_Type: No sound at all
  Title: [S1-M401E1, Realtek ALC880, Line Out, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/16/2006
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: RKYWSF0B
  dmi.board.name: ROCKY
  dmi.board.vendor: LG Electronics
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LG Electronics
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrRKYWSF0B:bd02/16/2006:svnLGElectronics:pnS1-M401E1:pvrNotApplicable:rvnLGElectronics:rnROCKY:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A:
  dmi.product.name: S1-M401E1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: LG Electronics

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

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

[Desktop-packages] [Bug 1480123] Re: LibreOffice doesn't support HiDPI well.

also
chromium-browser --force-device-scale-factor=0.5

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

Title:
  LibreOffice doesn't support HiDPI well.

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 14.04.2

  Reproducible Steps:

  1. Login Unity desktop environment.
  2. Change the scale factor to 2 in Displays of System Settings.
  3. Open any application of LibreOffice.

  Expected Result:

  * The icons and toolbar will be scaled up by 2.

  Actual Result:

  * There is no change for icons and toolbar.

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

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

[Desktop-packages] [Bug 1480123] Re: LibreOffice doesn't support HiDPI well.

At least on GNOME/X one can control LibreOffice scaling likeso:

GDK_DPI_SCALE=0.5 libreoffice --writer

- this would reduce the vertical size of fonts to 50%

X does not support different dpi per display, so in a mixed e vironment
you could decide which window goes on which display and scale
accordingly

Wayland supports per-display dpi

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

Title:
  LibreOffice doesn't support HiDPI well.

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 14.04.2

  Reproducible Steps:

  1. Login Unity desktop environment.
  2. Change the scale factor to 2 in Displays of System Settings.
  3. Open any application of LibreOffice.

  Expected Result:

  * The icons and toolbar will be scaled up by 2.

  Actual Result:

  * There is no change for icons and toolbar.

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

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

[Desktop-packages] [Bug 1651548] [NEW] package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: utlösare i slinga, avbryts

2016-12-20 Thread Erik Linder

Public bug reported:

Tried to upgrade from 16.04 to 16.10. Installation halted (stopped) half
way.

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: gnome-menus 3.13.3-6ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
Date: Tue Dec 20 19:25:54 2016
Dependencies:
 
ErrorMessage: utlösare i slinga, avbryts
InstallationDate: Installed on 2015-07-03 (536 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.2.15ubuntu0.2
SourcePackage: gnome-menus
Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: 
utlösare i slinga, avbryts
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package yakkety

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

Title:
  package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade:
  utlösare i slinga, avbryts

Status in gnome-menus package in Ubuntu:
  New

Bug description:
  Tried to upgrade from 16.04 to 16.10. Installation halted (stopped)
  half way.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gnome-menus 3.13.3-6ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Tue Dec 20 19:25:54 2016
  Dependencies:
   
  ErrorMessage: utlösare i slinga, avbryts
  InstallationDate: Installed on 2015-07-03 (536 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.2.15ubuntu0.2
  SourcePackage: gnome-menus
  Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: 
utlösare i slinga, avbryts
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1584279] Re: Duplicate icons appear on the desktop, these icons cannot be clicked, moved, or selected and they appear as long as an icon is present on the desktop, they essenti

2016-12-20 Thread TenLeftFingers

@seb123, I'm not the OP, but I do use an external display via VGA
sometimes. I'm experiencing the issue now without the display attached
(and it won't be available for two weeks to test with).

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

Title:
  Duplicate icons appear on the desktop, these icons cannot be clicked,
  moved, or selected and they appear as long as an icon is present on
  the desktop, they essentially behave as if they were part of the
  desktop background image.

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Please contact me at william123...@gmail.com if anything more is
  needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:03:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.96  Sun Nov  8 22:33:28 
PST 2015
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat May 21 00:07:36 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-22-generic, x86_64: installed
   nvidia-340, 340.96, 4.4.0-22-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GK104 [GeForce GTX 760] [3842:3768]
  InstallationDate: Installed on 2016-05-17 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: MSI MS-7760
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=ba9a7a99-4377-4f58-b32a-398cdd574f95 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V17.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X79A-GD45 Plus (MS-7760)
  dmi.board.vendor: MSI
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 3.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV17.9:bd12/08/2014:svnMSI:pnMS-7760:pvr3.0:rvnMSI:rnX79A-GD45Plus(MS-7760):rvr3.0:cvnMSI:ct3:cvr3.0:
  dmi.product.name: MS-7760
  dmi.product.version: 3.0
  dmi.sys.vendor: MSI
  upstart.unity-panel-service-lockscreen.log: (unity-panel-service:8027): 
GLib-CRITICAL **: Source ID 4294967295 was not found when attempting to remove 
it
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri May 20 20:31:57 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Desktop-packages] [Bug 1533343] Re: No sound from internal speakers after boot with connected headphones

2016-12-20 Thread Al Thomason

Same issue, same machine as Peter.  Dell 5510, upgraded to 16.04 --  at
1st the speakers worked, but the headphone would not.   Now the
headphones work, but the internal speakers don't.


 HEADPHONE PLUGGED IN 

$ pactl list sinks
Sink #0
State: SUSPENDED
Name: alsa_output.pci-_00_1f.3.analog-stereo
Description: Built-in Audio Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 48000Hz
Channel Map: front-left,front-right
Owner Module: 6
Mute: no
Volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% 
/ 0.00 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor Source: alsa_output.pci-_00_1f.3.analog-stereo.monitor
Latency: 0 usec, configured 0 usec
Flags: HARDWARE DECIBEL_VOLUME LATENCY 
Properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "ALC3266 Analog"
alsa.id = "ALC3266 Analog"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "0"
alsa.card_name = "HDA Intel PCH"
alsa.long_card_name = "HDA Intel PCH at 0xddd28000 irq 137"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:00:1f.3"
sysfs.path = "/devices/pci:00/:00:1f.3/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "a170"
device.product.name = "Sunrise Point-H HD Audio"
device.form_factor = "internal"
device.string = "front:0"
device.buffering.buffer_size = "65536"
device.buffering.fragment_size = "32768"
device.access_mode = "mmap+timer"
device.profile.name = "analog-stereo"
device.profile.description = "Analog Stereo"
device.description = "Built-in Audio Analog Stereo"
alsa.mixer_name = "Realtek ALC3266"
alsa.components = "HDA:10ec0298,102806e5,00100103 
HDA:80862809,80860101,0010"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
Formats:
pcm


==   HEADPHONES UNPLUGGED =
$ pactl list sinks
Sink #0
State: SUSPENDED
Name: alsa_output.pci-_00_1f.3.analog-stereo
Description: Built-in Audio Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 48000Hz
Channel Map: front-left,front-right
Owner Module: 6
Mute: no
Volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% 
/ 0.00 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor Source: alsa_output.pci-_00_1f.3.analog-stereo.monitor
Latency: 0 usec, configured 0 usec
Flags: HARDWARE DECIBEL_VOLUME LATENCY 
Properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "ALC3266 Analog"
alsa.id = "ALC3266 Analog"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "0"
alsa.card_name = "HDA Intel PCH"
alsa.long_card_name = "HDA Intel PCH at 0xddd28000 irq 137"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:00:1f.3"
sysfs.path = "/devices/pci:00/:00:1f.3/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "a170"
device.product.name = "Sunrise Point-H HD Audio"
device.form_factor = "internal"
device.string = "front:0"
device.buffering.buffer_size = "65536"
device.buffering.fragment_size = "32768"
device.access_mode = "mmap+timer"
device.profile.name = "analog-stereo"
device.profile.description = "Analog Stereo"
device.description = "Built-in Audio Analog Stereo"
alsa.mixer_name = "Realtek ALC3266"
alsa.components = "HDA:10ec0298,102806e5,00100103 
HDA:80862809,80860101,0010"

[Desktop-packages] [Bug 1606078] Re: No sound with Ubuntu 16.04

2016-12-20 Thread Al Thomason

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

** This bug has been marked a duplicate of bug 1533343
   No sound from internal speakers after boot with connected headphones

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

Title:
  No sound with Ubuntu 16.04

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  After a fresh install of Ubuntu 16.04.1 on an LG S1 Express Dual
  laptop there was no sound from the speakers unless external speakers
  where hooked to the headphones socket. This applies to the Ubuntu
  Mate, Xubuntu and Lubuntu variants. This laptop was working fine for
  all previous releases up to 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bashar 3263 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul 25 01:51:19 2016
  InstallationDate: Installed on 2016-07-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bashar 3263 F pulseaudio
  Symptom_Jack: Line Out, Internal
  Symptom_Type: No sound at all
  Title: [S1-M401E1, Realtek ALC880, Line Out, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/16/2006
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: RKYWSF0B
  dmi.board.name: ROCKY
  dmi.board.vendor: LG Electronics
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LG Electronics
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrRKYWSF0B:bd02/16/2006:svnLGElectronics:pnS1-M401E1:pvrNotApplicable:rvnLGElectronics:rnROCKY:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A:
  dmi.product.name: S1-M401E1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: LG Electronics

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

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

[Desktop-packages] [Bug 1639180] Re: no login possible after update to nvidia 304.132

@skgary, as for `1`, as I've said, just do:

sudo apt-get install nvidia-304=304.134-0ubuntu0.16.10.1

Or:

sudo apt-get install nvidia-304

(it'll do the same as 304.134-0ubuntu0.16.10.1 is the newest version
available to you).

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Triaged
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

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

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

[Desktop-packages] [Bug 1639180] Re: no login possible after update to nvidia 304.132

@skgary, so, after you upgraded to 16.10, you now have two ways:

1. Either to install the newest version (134) from PPA. It's ok to try
it. (Although, you said it doesn't work for you? Or it's just because
wrong command line?)

2. Or to try quite dirty way of installing packages-for-16.04 into your
16.10 manually through `dpkg` to have the old stable version (131). Not
sure it's good idea. Anyway, don't even try it unless you: (a) tried the
`1` and it didn't work; (b) need it very much; (c) know how to revert
it.

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Triaged
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

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

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

[Desktop-packages] [Bug 1639180] Re: no login possible after update to nvidia 304.132

@skgary, yes, within 16.10 package versions are different.

You have:

(1) Either `sudo apt-get install nvidia-304=304.134-0ubuntu0.16.10.1`
(or just `sudo apt-get install nvidia-304` as it's currently newest
version available to you) to install the newest version (134).

(2) Or try manually installing version `131-0ubuntu3` dedicated for
16.04 (not your 16.10) using `dpkg`. Not sure if it's good idea: (a)
whether it'll install at all (missing dependencies?); (b) whether it'll
work ok. Old (131) version packages may be located in your
`/var/cache/apt/archives` directory (they may remain there since were
used before upgrade); if no, they can be downloaded here:
http://archive.ubuntu.com/ubuntu/pool/restricted/n/nvidia-graphics-
drivers-304/. Again, I'm not sure, it's good idea to try installing
16.04-dedicated packages into 16.10.

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Triaged
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

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

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

[Desktop-packages] [Bug 1639180] Re: no login possible after update to nvidia 304.132

2016-12-20 Thread dino99

@Gary

Please takes time to read the thread to find the 'howto', it has been
given.

https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Triaged
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

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

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

[Desktop-packages] [Bug 1639180] Re: no login possible after update to nvidia 304.132

dino99

If you are referring to doing

sudo add-apt-repository ppa:graphics-drivers/ppa

then

sudo apt-get update

I did that a few times

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Triaged
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

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

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

[Desktop-packages] [Bug 1650796] Re: Black image (no video) with Live! Cam Connect HD VF0750 with some exceptions

2016-12-20 Thread Christopher M. Penalver

Vincas Dargis, to see if this is already resolved in Ubuntu, could you
please test http://cdimage.ubuntu.com/daily-live/current/ and advise to
the results?

** Tags added: bios-outdated-a17 regression-release

** Description changed:

- Problem was discovered on Dell 6400 laptop (32-bit) after upgrading Ubuntu 
14.04 to 16.40.
- Launching Cheese with  Live! Cam Connect HD VF0750 webcam *sometimes* 
(randomly) gives no video, only black image. No errors are reported on GUI, 
console and syslog.
+ After upgrading my Inspiron 6400 laptop (32-bit) from 14.04 to 16.04,
+ launching Cheese with  Live! Cam Connect HD VF0750 webcam *sometimes*
+ (randomly) gives no video, only black image. No errors are reported on
+ GUI, console, or syslog.
  
  You can start Cheese again and it might start video, but sometimes not,
  randomly. In case when there is no image, opening Settings and changing
  resolution makes video appear!
  
  Tried to downgrade libv4l-0, libv4lconvert0 to 14.04 version (1.0.1 I
  believe) but it did not helped. Upgrading to Linux 4.8 (from hwe
  package) did not helped either.
  
  On other laptop with Ubuntu 14.04 (with same 4.4 kernel from hwe
  package) there is no issues as such, so I assume it's bug with Cheese
  itself.
  
  Interestingly, on yet other laptop (Asus N551JM) with Kubuntu 16.04
  Cheese does not show video on launch always (tested with many restarts
  of Cheese app). If I change resolution in Settings, it does start to
  show video thought. That computer is faster than Dell 6400 one, so I'm
  guessing it could be some kind race condition..?
  
  I cannot reproduce this issue with Camorama for example, it seems it
  always starts video successfully for this webcam.
  
- ProblemType: Bug
- DistroRelease: Ubuntu 16.04
- Package: cheese 3.18.1-2ubuntu3
- ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
- Uname: Linux 4.4.0-53-generic x86_64
- ApportVersion: 2.20.1-0ubuntu2.4
- Architecture: amd64
- Date: Sat Dec 17 21:15:27 2016
- InstallationDate: Installed on 2015-06-25 (541 days ago)
- InstallationMedia: Kubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150219.1)
- MachineType: ASUSTeK COMPUTER INC. N551JM
- ProcEnviron:
-  LANGUAGE=lt
-  TERM=screen-256color
-  PATH=(custom, no user)
-  LANG=lt_LT.UTF-8
-  SHELL=/bin/bash
- RelatedPackageVersions:
-  cheese3.18.1-2ubuntu3
-  cheese-common 3.18.1-2ubuntu3
- SourcePackage: linux
- UpgradeStatus: Upgraded to xenial on 2016-07-30 (139 days ago)
- dmi.bios.date: 02/13/2015
- dmi.bios.vendor: American Megatrends Inc.
- dmi.bios.version: N551JM.205
- dmi.board.asset.tag: ATN12345678901234567
- dmi.board.name: N551JM
- dmi.board.vendor: ASUSTeK COMPUTER INC.
- dmi.board.version: 1.0
- dmi.chassis.type: 10
- dmi.chassis.vendor: ASUSTeK COMPUTER INC.
- dmi.chassis.version: 1.0
- dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN551JM.205:bd02/13/2015:svnASUSTeKCOMPUTERINC.:pnN551JM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551JM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
- dmi.product.name: N551JM
- dmi.product.version: 1.0
- dmi.sys.vendor: ASUSTeK COMPUTER INC.
- --- 
+ ---
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: i386
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  petras 2060 F pulseaudio
-  /dev/snd/controlC0:  petras 2060 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  petras 2060 F pulseaudio
+  /dev/snd/controlC0:  petras 2060 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2011-11-23 (1851 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  MachineType: Dell Inc. MM061
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=b57d1858-e7f3-42a3-a7ef-5e7ab8dd5ae4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  RelatedPackageVersions:
-  linux-restricted-modules-4.8.0-30-generic N/A
-  linux-backports-modules-4.8.0-30-generic  N/A
-  linux-firmware1.157.6
+  linux-restricted-modules-4.8.0-30-generic N/A
+  linux-backports-modules-4.8.0-30-generic  N/A
+  linux-firmware1.157.6
  RfKill:
-  0: phy0: Wireless LAN
-   Soft blocked: no
-   Hard blocked: no
+  0: phy0: Wireless LAN
+   Soft blocked: no
+   Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.8.0-30-generic i686
  UpgradeStatus: Upgraded to xenial on 2016-11-19 (28 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare uucp
  _MarkForUpload: True
  dmi.bios.date: 06/09/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0KD882
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd06/09/2006:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0KD882:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: MM061

[Desktop-packages] [Bug 1650796] [NEW] Black image (no video) with Live! Cam Connect HD VF0750 with some exceptions

You have been subscribed to a public bug:

After upgrading my Inspiron 6400 laptop (32-bit) from 14.04 to 16.04,
launching Cheese with  Live! Cam Connect HD VF0750 webcam *sometimes*
(randomly) gives no video, only black image. No errors are reported on
GUI, console, or syslog.

You can start Cheese again and it might start video, but sometimes not,
randomly. In case when there is no image, opening Settings and changing
resolution makes video appear!

Tried to downgrade libv4l-0, libv4lconvert0 to 14.04 version (1.0.1 I
believe) but it did not helped. Upgrading to Linux 4.8 (from hwe
package) did not helped either.

On other laptop with Ubuntu 14.04 (with same 4.4 kernel from hwe
package) there is no issues as such, so I assume it's bug with Cheese
itself.

Interestingly, on yet other laptop (Asus N551JM) with Kubuntu 16.04
Cheese does not show video on launch always (tested with many restarts
of Cheese app). If I change resolution in Settings, it does start to
show video thought. That computer is faster than Dell 6400 one, so I'm
guessing it could be some kind race condition..?

I cannot reproduce this issue with Camorama for example, it seems it
always starts video successfully for this webcam.

---
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  petras 2060 F pulseaudio
 /dev/snd/controlC0:  petras 2060 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
InstallationDate: Installed on 2011-11-23 (1851 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MachineType: Dell Inc. MM061
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=b57d1858-e7f3-42a3-a7ef-5e7ab8dd5ae4 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-30-generic N/A
 linux-backports-modules-4.8.0-30-generic  N/A
 linux-firmware1.157.6
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags:  xenial
Uname: Linux 4.8.0-30-generic i686
UpgradeStatus: Upgraded to xenial on 2016-11-19 (28 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare uucp
_MarkForUpload: True
dmi.bios.date: 06/09/2006
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0KD882
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd06/09/2006:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0KD882:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: MM061
dmi.sys.vendor: Dell Inc.

** Affects: cheese (Ubuntu)
 Importance: Medium
 Status: Incomplete


** Tags: amd64 apport-bug apport-collected bios-outdated-a17 gstreamer-error 
regression-release xenial
-- 
Black image (no video) with Live! Cam Connect HD VF0750 with some exceptions
https://bugs.launchpad.net/bugs/1650796
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to cheese in Ubuntu.

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

[Desktop-packages] [Bug 1647187] Re: gnome-software crashed with signal 5 in g_main_context_new()

2016-12-20 Thread simon

I got the same error "gnome-software crashed with signal 5 in
g_main_context_new()" on startup and solved it with:

sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade

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

Title:
  gnome-software crashed with signal 5 in g_main_context_new()

Status in gnome-software package in Ubuntu:
  New

Bug description:
  when I start ubuntu 16.04 32bit system, it always comes across the
  problem , the system gives an internal problem, as follows:

  Executablepath
   /usr/bin/gnome-software

  Pachage
   gnome-software 3.20.1 +git20160426.1.a976114-ubuntu-xenial-0ubuntu1

  ProblemType
   crash

  Title
   gnome-software crashed with signal 5 in g_main_context_new()

  Architechure
i386

  
  .
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-08-17 (109 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160720)
  Package: gnome-software 
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
  PackageArchitecture: i386
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Tags:  xenial
  Uname: Linux 4.4.0-47-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1651425] Re: Adjust area of screenshot

2016-12-20 Thread Hans Joachim Desserud

** Tags added: xenial

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

Title:
  Adjust area of screenshot

Status in gnome-screenshot package in Ubuntu:
  New

Bug description:
  ** This is a feature request. **

  Please enable to adjust the area of screenshot after that it was
  chosen.

  For example when I take a screenshot using keyboard shortcut: "CTRL" + 
"SHIFT" + "Print Screen" , then I have only one chance to choose the right 
coordinates/area for the screenshot.
  But sometimes I wish to further adjust the area of the screenshot.

  Using Ubuntu 16.04.

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

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

[Desktop-packages] [Bug 1639180] Re: no login possible after update to nvidia 304.132

I wonder if it's because I upgraded to 16.10 on Saturday?

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Triaged
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

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

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

[Desktop-packages] [Bug 1639180] Re: no login possible after update to nvidia 304.132

If I do sudo apt-get install nvidia-304=304.131-0ubuntu3
I get
Version '304.131-0ubuntu3' for 'nvidia-304' was not found

If I try sudo apt-get install nvidia-304=304.134-0ubuntu1

I get
Version '304.134-0ubuntu1' for 'nvidia-304' was not found

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Triaged
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

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

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

[Desktop-packages] [Bug 1639180] Re: no login possible after update to nvidia 304.132

Oleksandr

yes I put = after nvidia-304

Here's the outup

nvidia-304:
  Installed: (none)
  Candidate: 304.134-0ubuntu0.16.10.1
  Version table:
 304.134-0ubuntu0.16.10.1 500
500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu yakkety/main 
amd64 Packages
100 /var/lib/dpkg/status
 304.132-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu yakkety/restricted amd64 Packages
N: Ignoring file 'local-nvidia-quirks.bk' in directory 
'/etc/apt/preferences.d/' as it has an invalid filename extension

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Triaged
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

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

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

[Desktop-packages] [Bug 1639180] Re: no login possible after update to nvidia 304.132

@skgary:

1. Have you put "=" after "nvidia-304" as suggested in Jan Herold
(yzle)'s and my comments?

2. What it output of `apt-cache policy nvidia-304` (list of available
versions)?

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Triaged
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

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

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

[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2016-12-20 Thread Thomas M Steenholdt

That is certainly a possibility, but unfortunately returns us to a state
where applications have to be restarted when nameservers change (glibc
resolved.conf issue). That's probably even worse in my situation at
least.

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

Title:
  dns server priority broken

Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  network-manager: 1.2.4-0ubuntu1

  
  Yakkety appears to have switched back from resolved to dnsmasq, but it seems 
server priority/order is broken.

  Example: In split DNS setups, connecting to VPN will not cause us to
  query the DNS provided by the VPN first (or only), which should be the
  proper way to resolve names in that case.

  Say server.example.com in the public DNS resolves to a.a.a.a and in
  the private DNS resolves to b.b.b.b.

  Stuff would work from my normal internet-connection, but connection to
  VPN would cause stuff to misbehave. I expect to hit the b.b.b.b
  address but since my normal LAN DNS is being used first, I'm really
  hitting a.a.a.a.

  Please let me know how to proceed - Hopefully this can be fixed in
  time for release.

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

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

[Desktop-packages] [Bug 1577093] Re: libreoffice-gtk conflicts with large lo-writer file

2016-12-20 Thread Christopher M. Penalver

Jurgen Schellaert, thanks for the clarification. I'll re-close this
report as your issue has long been resolved.

** Changed in: libreoffice (Ubuntu)
   Importance: Low => Undecided

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

** Attachment removed: "valgrind.log"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1577093/+attachment/4758232/+files/valgrind.log

** Attachment removed: "Test.odt"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1577093/+attachment/4738362/+files/Test.odt

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

Title:
  libreoffice-gtk conflicts with large lo-writer file

Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  After opening 
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1577093/+attachment/4652522/+files/wlst.odt
 , LibreOffice becomes  unresponsive, graying out from a few minutes to a 
quarter of an hour at a time. During this, the interface has various 
presentation issues:
  - Two overlapping status bars
  - Duplicated vertical scrollbars at the right side
  - The title bar covering up the menu bar as well as part of the upper toolbar
  - The horizontal ruler shifted to the right, causing the "comments" column to 
appear on the left rather than the right

  When the file eventually gets loaded and the interface is restored,
  the menus turns out to be unusable: the drop-downs are narrow blacks
  slabs without any entries and without any responsiveness.

  Newly created files or existing smaller files are fine.

  WORKAROUND: Uninstall packages:
  libreoffice-gnome
  libreoffice-gtk

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-writer 1:5.1.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun May  1 05:28:07 2016
  InstallationDate: Installed on 2016-04-07 (23 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160405)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1651500] [NEW] [X441SA, Realtek ALC3236, Speaker, Internal] No sound at all

2016-12-20 Thread W.R. Irsyad Hamda

Public bug reported:

1. Release of ubuntu
Description:Ubuntu 16.04.1 LTS
Release:16.04

2. version of the package
AlsaMixer v1.1.0


3. I expect to hear sound from speaker

4. I can not any sound from speaker

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  hamda  1627 F pulseaudio
CurrentDesktop: Unity
Date: Tue Dec 20 22:51:08 2016
InstallationDate: Installed on 2016-12-15 (5 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  hamda  1627 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [X441SA, Realtek ALC3236, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/08/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X441SA.301
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X441SA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX441SA.301:bd08/08/2016:svnASUSTeKCOMPUTERINC.:pnX441SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX441SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X441SA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

Title:
  [X441SA, Realtek ALC3236, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  1. Release of ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2. version of the package
  AlsaMixer v1.1.0

  
  3. I expect to hear sound from speaker

  4. I can not any sound from speaker

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hamda  1627 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Dec 20 22:51:08 2016
  InstallationDate: Installed on 2016-12-15 (5 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hamda  1627 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [X441SA, Realtek ALC3236, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X441SA.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X441SA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX441SA.301:bd08/08/2016:svnASUSTeKCOMPUTERINC.:pnX441SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX441SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X441SA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1639180] Re: no login possible after update to nvidia 304.132

OK I did
sudo add-apt-repository ppa:graphics-drivers/ppa 
sudo apt-get update.

Now I have nvidia-304 304.1343-0ubuntu0 showing up in Synaptic

I don't have
nvidia-304 304.1343-0ubuntu1

nor is version 131 showing up

In Software and Updates I selected Main Server and reloaded

Maybe I just have to wait until nvidia-304 304.1343-0ubuntu1 becomes
available here?

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Triaged
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

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

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

[Desktop-packages] [Bug 1639180] Re: no login possible after update to nvidia 304.132

Correction

I have
I don't have
nvidia-304 304.134-0ubuntu0 available

I don't have
nvidia-304 304.134-0ubuntu1

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Triaged
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

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

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

[Desktop-packages] [Bug 991481] Re: Constant dns traffic for daisy.ubuntu.com

2016-12-20 Thread Aron Xu

** Tags added: nm-improvements

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

Title:
  Constant dns traffic for daisy.ubuntu.com

Status in Whoopsie:
  Confirmed
Status in glib2.0 package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Triaged
Status in whoopsie package in Ubuntu:
  Triaged

Bug description:
  Watching GNetworkMonitor's network-changed signal causes constant DNS
  traffic.

  Andy Whitcroft points out that the NETLINK_ROUTE socket set up by
  GNetworkMonitor will fire events every time an ARP entry appears or
  disappears.

  Unfortunately, we currently need an additional layer of connectivity
  checking because checking NetworkManager's state for CONNECTED_GLOBAL
  is not enough to know whether we're really online. Ubuntu does not yet
  use the NetworkManager connectivity check [1].

  The likely solution to this bug is a replacement for GNetworkMonitor
  in whoopsie.

  1: http://bazaar.launchpad.net/~daisy-
  pluckers/whoopsie/trunk/view/head:/src/connectivity.c#L326

  Original report follows:

  Every few seconds, I see a dns query for daisy.ubuntu.com. After
  removing whoopsie, the traffic goes away.

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

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

[Desktop-packages] [Bug 1639926] Re: Update evolution-data-server to 3.22.3

I confirm that evolution-data-server 3.22.3-0ubuntu0.1 works fine here
on Ubuntu GNOME 16.10. (I do most of my email via a web browser
though.). Because of how important it is to fix the broken Google
authentication, I also backported the proposed evolution and evolution-
data-server 3.22.3 to the GNOME3 Staging PPA. I've not seen any bugs or
heard any complaints from the new update yet.

I tested evolution and gnome-calendar with my configured Google account.

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

Title:
Update evolution-data-server to 3.22.3

Status in evolution-data-server package in Ubuntu:
Fix Released
Status in evolution-data-server source package in Yakkety:
Fix Committed

Bug description:
Impact
==
This is the second evolution SRU for yakkety. This update includes the new
bugfix releases 3.22.2 and 3.22.3. Updating e-d-s is required to update
evolution to 3.22.3 (LP: #1639942)

https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-22
https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-22

Test Case
=
After installing the update, restart your computer. (Is there a flag
evolution-data-server should set to prompt the user to do this?)

Run several eds-using apps like Evolution, GNOME Calendar and verify
that they continue to run at least as well as before this update.

Regression Potential

Low. There are a fair amount of changes in this update, but they are all
targeted towards fixing bugs. This is the same release that other GNOME 3.22
distros ship. This may be the last official 3.22 release for the Evolution
stack.

Other Info
==
Note that there is an issue with Google authentication affecting at least
3.20 and 3.22.0. The underlying issue should be fixed with this update (it was
partially fixed with 3.22.1 already in yakkety-updates). Unfortunately, anyone
anywhere using older still-broken versions of e-d-s still break authentication
for everyone else using the same API key!

Because of this, GNOME is updating the key used by GNOME Online
Accounts (LP: #1649995). The key used by e-d-s might need to be
updated too. And maybe the key used by Ubuntu Online Accounts (LP:
#1650007). This is because there are 2 or 3 different ways to use a
Google account with Evolution. You only need to update the key for the
Google authentication method you use.

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

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

[Desktop-packages] [Bug 978604] Re: Banshee/Rhythmbox regularly stop playing audio when left on in the background

2016-12-20 Thread HX_unbanned

Issue happening on Fedora 26 x64 with latest available Rythmbox version.

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

Title:
  Banshee/Rhythmbox regularly stop playing audio when left on in the
  background

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio source package in Precise:
  Confirmed

Bug description:
  If Banshee or Rhythmbox is left playing in the background they will
  randomly stop playing in the latest builds of Ubuntu 12.04. Starting a
  new piece of music usually fixes the problem. If left to its own
  devices, the music will start playing again at some random time, at
  some random position. This problem exists on both my desktop machine
  (custom built Intel machine) and my laptop (Macbook 5,1). It has been
  happening for several months now.

  I became frustrated enough to load up pulseaudio in debugging mode.
  The log shows that when the music player just finishes playing one
  piece, and tries to start the next piece, you see something like this:

  ---
  ( 335.399|  34.388) D: [alsa-sink] sink-input.c: Requesting rewind due to 
corking
  ( 335.400|   0.001) D: [alsa-sink] alsa-sink.c: Requested to rewind 65536 
bytes.
  ( 335.400|   0.000) D: [alsa-sink] alsa-sink.c: Limited to 14820 bytes.
  ( 335.400|   0.000) D: [alsa-sink] alsa-sink.c: before: 3705
  ( 335.400|   0.000) D: [alsa-sink] alsa-sink.c: after: 3705
  ( 335.400|   0.000) D: [alsa-sink] alsa-sink.c: Rewound 14820 bytes.
  ( 335.400|   0.000) D: [alsa-sink] sink.c: Processing rewind...
  ( 335.400|   0.000) D: [alsa-sink] sink.c: latency = 1643
  ( 335.400|   0.000) D: [alsa-sink] sink-input.c: Have to rewind 14820 bytes 
on render memblockq.
  ( 335.400|   0.000) D: [alsa-sink] sink-input.c: Have to rewind 14820 bytes 
on implementor.
  ( 335.400|   0.000) D: [alsa-sink] source.c: Processing rewind...
  ( 335.400|   0.000) D: [pulseaudio] module-suspend-on-idle.c: Sink 
alsa_output.pci-_00_1b.0.analog-stereo becomes idle, timeout in 5 seconds.
  ( 335.402|   0.001) D: [alsa-sink] alsa-sink.c: hwbuf_unused=0
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15502
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Requested volume: 0:  34% 1:  
34%
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c:in dB: 0: -28.11 
dB 1: -28.11 dB
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Got hardware volume: 0:  34% 
1:  34%
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c:   in dB: 0: 
-28.00 dB 1: -28.00 dB
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Calculated software volume: 
0: 100% 1: 100% (accurate-enough=yes)
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c:  in dB: 
0: -0.11 dB 1: -0.11 dB
  ( 335.402|   0.000) D: [alsa-sink] sink.c: Volume not changing
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Requested to rewind 65536 
bytes.
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Limited to 15300 bytes.
  ( 335.402|   0.000) D: [pulseaudio] module-suspend-on-idle.c: Sink 
alsa_output.pci-_00_1b.0.analog-stereo becomes idle, timeout in 5 seconds.
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: before: 3825
  ( 335.402|   0.000) D: [pulseaudio] core.c: Hmm, no streams around, trying to 
vacuum.
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: after: 3825
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Rewound 15300 bytes.
  ( 335.402|   0.000) D: [alsa-sink] sink.c: Processing rewind...
  ( 335.402|   0.000) D: [alsa-sink] sink.c: latency = 1402
  ( 335.402|   0.000) D: [alsa-sink] source.c: Processing rewind...
  ( 335.402|   0.000) I: [pulseaudio] sink-input.c: Freeing input 3 
"'zero-project - 05 - Forest of the unicorns' by 'zero-project'"
  ( 335.402|   0.000) D: [pulseaudio] module-stream-restore.c: Not restoring 
device for stream sink-input-by-media-role:music, because already set to 
'alsa_output.pci-_00_1b.0.analog-stereo'.
  ( 335.403|   0.000) D: [pulseaudio] module-intended-roles.c: Not setting 
device for stream Playback Stream, because already set.
  ( 335.403|   0.000) I: [pulseaudio] module-stream-restore.c: Restoring volume 
for sink input sink-input-by-media-role:music.
  ( 335.403|   0.000) I: [pulseaudio] module-stream-restore.c: Restoring mute 
state for sink input sink-input-by-media-role:music.
  ( 335.403|   0.000) D: [pulseaudio] module-suspend-on-idle.c: Sink 
alsa_output.pci-_00_1b.0.analog-stereo becomes busy.
  ( 335.403|   0.000) I: [pulseaudio] resampler.c: Forcing resampler 'copy', 
because of fixed, identical sample rates.
  ( 335.403|   0.000) I: [pulseaudio] resampler.c: Using resampler 'copy'
  ( 335.403|   0.000) I: [pulseaudio] resampler.c: Using float32le as working 
format.
  ( 335.403|   0.000) D: [pulseaudio] memblockq.c: memblockq requested: 
maxlength=33554432, tlength=0, base=4, prebuf=0, minreq=1 maxrewind=0

[Desktop-packages] [Bug 1639180] Re: no login possible after update to nvidia 304.132

No I just typed it wrong in the message.

As I said even synapthic can't find it.

It can't find 304.134 now either.

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

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

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

[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2016-12-20 Thread Bryn Cooke

This workaround worked for me in 16.10:

In /etc/NetworkManager/NetworkManager.conf

Comment out:
dns=dnsmasq

The run:
sudo service NetworkManager restart

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

Title:
  dns server priority broken

Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  network-manager: 1.2.4-0ubuntu1

  
  Yakkety appears to have switched back from resolved to dnsmasq, but it seems 
server priority/order is broken.

  Example: In split DNS setups, connecting to VPN will not cause us to
  query the DNS provided by the VPN first (or only), which should be the
  proper way to resolve names in that case.

  Say server.example.com in the public DNS resolves to a.a.a.a and in
  the private DNS resolves to b.b.b.b.

  Stuff would work from my normal internet-connection, but connection to
  VPN would cause stuff to misbehave. I expect to hit the b.b.b.b
  address but since my normal LAN DNS is being used first, I'm really
  hitting a.a.a.a.

  Please let me know how to proceed - Hopefully this can be fixed in
  time for release.

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

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

[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2016-12-20 Thread Aron Xu

** Tags added: nm-improvements

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

Title:
  dns server priority broken

Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  network-manager: 1.2.4-0ubuntu1

  
  Yakkety appears to have switched back from resolved to dnsmasq, but it seems 
server priority/order is broken.

  Example: In split DNS setups, connecting to VPN will not cause us to
  query the DNS provided by the VPN first (or only), which should be the
  proper way to resolve names in that case.

  Say server.example.com in the public DNS resolves to a.a.a.a and in
  the private DNS resolves to b.b.b.b.

  Stuff would work from my normal internet-connection, but connection to
  VPN would cause stuff to misbehave. I expect to hit the b.b.b.b
  address but since my normal LAN DNS is being used first, I'm really
  hitting a.a.a.a.

  Please let me know how to proceed - Hopefully this can be fixed in
  time for release.

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

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

[Desktop-packages] [Bug 508740] Re: PPTP VPN "no valid VPN secrets"

2016-12-20 Thread Frindli

I have same error message on ubuntu touch if I tried connect to VPN
server with OPENVPN or PPTP.

The error message if I type "sudo nmcli con up THENAME":
Password is required but not given in 'passwd-file' (I don't no while) and 
nmcli cannot ask without --ask option

So that's worked for me on ubuntu touch:
sudo nmcli --ask con up "VPNCONNECTIONNAME"

But VPN worked without terminal before OTA-14.

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

Title:
  PPTP VPN "no valid VPN secrets"

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

Bug description:
  Binary package hint: network-manager-pptp

  When trying to connect I immediately get a notification stating:
  "The VPN connection '' failed. because there were no valid VPN secrets."

  I'm quite positive I've not made an error in setting it up.

  My syslog spits out this:
  Jan 17 13:51:26 lena NetworkManager:   Starting VPN service 
'org.freedesktop.NetworkManager.pptp'...
  Jan 17 13:51:26 lena NetworkManager:   VPN service 
'org.freedesktop.NetworkManager.pptp' started 
(org.freedesktop.NetworkManager.pptp), PID 8900
  Jan 17 13:51:26 lena NetworkManager:   VPN service 
'org.freedesktop.NetworkManager.pptp' just appeared, activating connections
  Jan 17 13:51:26 lena NetworkManager: nm-vpn-connection.c.828: NeedSecrets 
failed: dbus-glib-error-quark Rejected send message, 1 matched rules; 
type="method_call", sender=":1.2" (uid=0 pid=1051 comm="NetworkManager) 
interface="org.freedesktop.NetworkManager.VPN.Plugin" member="NeedSecrets" 
error name="(unset)" requested_reply=0 
destination="org.freedesktop.NetworkManager.pptp" (uid=0 pid=8900 
comm="/usr/lib/network-manager-pptp/nm-pptp-service))
  Jan 17 13:51:26 lena NetworkManager:   connection_state_changed(): 
Rejected send message, 1 matched rules; type="method_call", sender=":1.2" 
(uid=0 pid=1051 comm="NetworkManager) 
interface="org.freedesktop.NetworkManager.VPN.Plugin" member="Disconnect" error 
name="(unset)" requested_reply=0 
destination="org.freedesktop.NetworkManager.pptp" (uid=0 pid=8900 
comm="/usr/lib/network-manager-pptp/nm-pptp-service))
  Jan 17 13:51:26 lena NetworkManager:   Policy set 'Auto netgear' (eth1) 
as default for routing and DNS.
  Jan 17 13:51:38 lena NetworkManager:  [1263732698.001156] 
ensure_killed(): waiting for vpn service pid 8900 to exit
  Jan 17 13:51:38 lena NetworkManager:  [1263732698.001284] 
ensure_killed(): vpn service pid 8900 cleaned up

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

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

[Desktop-packages] [Bug 1643467] Re: Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec

2016-12-20 Thread louis romano

** Changed in: firefox (Ubuntu Precise)
 Assignee: (unassigned) => louis romano (troubleshooter1961)

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

Title:
  Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec

Status in libav:
  Unknown
Status in firefox package in Ubuntu:
  Confirmed
Status in libav package in Ubuntu:
  Invalid
Status in firefox source package in Precise:
  Fix Released
Status in libav source package in Precise:
  Confirmed
Status in firefox source package in Trusty:
  Fix Released
Status in libav source package in Trusty:
  Fix Released

Bug description:
  Whenever it tries to play a video, Firefox 50 displays this message at the 
top of every page:
  "libavcodec may be vulnerable or is not supported, and should be updated to 
play video"

  https://dxr.mozilla.org/mozilla-central/source/browser/locales/en-
  
US/chrome/browser/browser.properties?q=%22libavcodec+may+be+vulnerable%22_type=single#742

  Firefox refuses any libavcodec version prior to 54.35.1 (unless
  media.libavcodec.allow-obsolete==true).

  https://dxr.mozilla.org/mozilla-
  central/source/dom/media/platforms/ffmpeg/FFmpegLibWrapper.cpp#60

  Users should not be subjected to this warning, as it is vague (does not 
instruct them how to fix it).
  Ubuntu 14.04 LTS should ship with an updated version of libavcodec.

  DistroRelease: Ubuntu 14.04
  Package: firefox 50.0+build2-0ubuntu0.14.04.2

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

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

[Desktop-packages] [Bug 1639926] Re: Update evolution-data-server to 3.22.3

Brian, so I could use something like this:

https://sources.debian.net/src/connman/unstable/debian/connman.postinst/

I'm not sure that it's important enough to delay this update another
week or so, but we can do it next time.

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

Title:
Update evolution-data-server to 3.22.3

Status in evolution-data-server package in Ubuntu:
Fix Released
Status in evolution-data-server source package in Yakkety:
Fix Committed

https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-22
https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-22

Test Case
=
After installing the update, restart your computer. (Is there a flag
evolution-data-server should set to prompt the user to do this?)

Run several eds-using apps like Evolution, GNOME Calendar and verify
that they continue to run at least as well as before this update.

Regression Potential

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

[Desktop-packages] [Bug 1639180] Re: no login possible after update to nvidia 304.132