date:20170120

[Expired for Mir because there has been no activity for 60 days.]

** Changed in: mir
   Status: Incomplete => Expired

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

Title:
  Mir is just a black screen and mouse cursor on Nvidia GTX 900 when
  using nouveau

Status in Canonical System Image:
  Incomplete
Status in Mir:
  Expired
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Expired

Bug description:
  Nvidia (using nouveau not binary drivers): Mir servers freeze on
  start-up for 30 seconds, and then you get just a black screen and
  mouse cursor (which at least moves).

  Using lp:mir r3480 ...

  [2016-04-27 15:20:19.369559] mirserver: Selected driver: mir:mesa-kms 
(version 0.22.0)
  nvc0_screen_create:762 - Error allocating PGRAPH context for M2MF: -22
  [2016-04-27 15:20:51.934145] mirserver: Using hardware cursor
  [2016-04-27 15:20:51.937691] mirserver: Initial display configuration:
  [2016-04-27 15:20:51.937703] mirserver:   0.36: unused DVI-I
  [2016-04-27 15:20:51.937713] mirserver:   0.39: DVI-D 24.0" 520x320mm
  [2016-04-27 15:20:51.937722] mirserver: Current mode 1920x1200 59.95Hz
  [2016-04-27 15:20:51.937731] mirserver: Preferred mode 1920x1200 
59.95Hz
  [2016-04-27 15:20:51.937740] mirserver: Logical position +0+0
  [2016-04-27 15:20:51.937781] mirserver:   0.41: unused HDMI-A
  [2016-04-27 15:20:51.937799] mirserver:   0.43: unused DisplayPort
  [2016-04-27 15:20:51.937972] mircommon: Loading modules from: 
bin/../lib/server-modules/
  [2016-04-27 15:20:51.938015] mircommon: Loading module: 
bin/../lib/server-modules/graphics-android.so.9
  [2016-04-27 15:20:51.938107]  mircommon: Failed to load module: 
bin/../lib/server-modules/graphics-android.so.9 (error was:libhardware.so.2: 
cannot open shared object file: No such file or directory)
  [2016-04-27 15:20:51.938119] mircommon: Loading module: 
bin/../lib/server-modules/graphics-mesa-kms.so.9
  [2016-04-27 15:20:51.938142] mircommon: Loading module: 
bin/../lib/server-modules/server-mesa-x11.so.9
  [2016-04-27 15:20:51.938536] mircommon: Loading module: 
bin/../lib/server-modules/input-evdev.so.5
  [2016-04-27 15:20:51.955316] mirserver: Selected input driver: 
mir:evdev-input (version: 0.22.0)
  [2016-04-27 15:20:51.955500] mirserver: Mir version 0.22.0
  [2016-04-27 15:20:51.962627] GLRenderer: EGL vendor: Mesa Project
  [2016-04-27 15:20:51.962645] GLRenderer: EGL version: 1.4 (DRI2)
  [2016-04-27 15:20:51.962651] GLRenderer: EGL client APIs: OpenGL OpenGL_ES 
OpenGL_ES2 OpenGL_ES3
  [2016-04-27 15:20:51.962657] GLRenderer: EGL extensions: EGL_EXT_buffer_age 
EGL_EXT_image_dma_buf_import EGL_KHR_create_context 
EGL_KHR_get_all_proc_addresses EGL_KHR_gl_renderbuffer_image 
EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_image 
EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_surfaceless_context 
EGL_MESA_configless_context EGL_MESA_image_dma_buf_export
  [2016-04-27 15:20:51.962670] GLRenderer: GL vendor: VMware, Inc.
  [2016-04-27 15:20:51.962679] GLRenderer: GL renderer: Gallium 0.4 on llvmpipe 
(LLVM 3.8, 256 bits)
  [2016-04-27 15:20:51.962688] GLRenderer: GL version: OpenGL ES 3.0 Mesa 11.2.0
  [2016-04-27 15:20:51.962697] GLRenderer: GLSL version: OpenGL ES GLSL ES 3.00

  lspci:
  01:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] 
(rev a1)

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

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

[Desktop-packages] [Bug 1575516] Re: Mir is just a black screen and mouse cursor on Nvidia GTX 900 when using nouveau

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

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

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

Title:
  Mir is just a black screen and mouse cursor on Nvidia GTX 900 when
  using nouveau

Status in Canonical System Image:
  Incomplete
Status in Mir:
  Expired
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Expired

Bug description:
  Nvidia (using nouveau not binary drivers): Mir servers freeze on
  start-up for 30 seconds, and then you get just a black screen and
  mouse cursor (which at least moves).

  Using lp:mir r3480 ...

  [2016-04-27 15:20:19.369559] mirserver: Selected driver: mir:mesa-kms 
(version 0.22.0)
  nvc0_screen_create:762 - Error allocating PGRAPH context for M2MF: -22
  [2016-04-27 15:20:51.934145] mirserver: Using hardware cursor
  [2016-04-27 15:20:51.937691] mirserver: Initial display configuration:
  [2016-04-27 15:20:51.937703] mirserver:   0.36: unused DVI-I
  [2016-04-27 15:20:51.937713] mirserver:   0.39: DVI-D 24.0" 520x320mm
  [2016-04-27 15:20:51.937722] mirserver: Current mode 1920x1200 59.95Hz
  [2016-04-27 15:20:51.937731] mirserver: Preferred mode 1920x1200 
59.95Hz
  [2016-04-27 15:20:51.937740] mirserver: Logical position +0+0
  [2016-04-27 15:20:51.937781] mirserver:   0.41: unused HDMI-A
  [2016-04-27 15:20:51.937799] mirserver:   0.43: unused DisplayPort
  [2016-04-27 15:20:51.937972] mircommon: Loading modules from: 
bin/../lib/server-modules/
  [2016-04-27 15:20:51.938015] mircommon: Loading module: 
bin/../lib/server-modules/graphics-android.so.9
  [2016-04-27 15:20:51.938107]  mircommon: Failed to load module: 
bin/../lib/server-modules/graphics-android.so.9 (error was:libhardware.so.2: 
cannot open shared object file: No such file or directory)
  [2016-04-27 15:20:51.938119] mircommon: Loading module: 
bin/../lib/server-modules/graphics-mesa-kms.so.9
  [2016-04-27 15:20:51.938142] mircommon: Loading module: 
bin/../lib/server-modules/server-mesa-x11.so.9
  [2016-04-27 15:20:51.938536] mircommon: Loading module: 
bin/../lib/server-modules/input-evdev.so.5
  [2016-04-27 15:20:51.955316] mirserver: Selected input driver: 
mir:evdev-input (version: 0.22.0)
  [2016-04-27 15:20:51.955500] mirserver: Mir version 0.22.0
  [2016-04-27 15:20:51.962627] GLRenderer: EGL vendor: Mesa Project
  [2016-04-27 15:20:51.962645] GLRenderer: EGL version: 1.4 (DRI2)
  [2016-04-27 15:20:51.962651] GLRenderer: EGL client APIs: OpenGL OpenGL_ES 
OpenGL_ES2 OpenGL_ES3
  [2016-04-27 15:20:51.962657] GLRenderer: EGL extensions: EGL_EXT_buffer_age 
EGL_EXT_image_dma_buf_import EGL_KHR_create_context 
EGL_KHR_get_all_proc_addresses EGL_KHR_gl_renderbuffer_image 
EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_image 
EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_surfaceless_context 
EGL_MESA_configless_context EGL_MESA_image_dma_buf_export
  [2016-04-27 15:20:51.962670] GLRenderer: GL vendor: VMware, Inc.
  [2016-04-27 15:20:51.962679] GLRenderer: GL renderer: Gallium 0.4 on llvmpipe 
(LLVM 3.8, 256 bits)
  [2016-04-27 15:20:51.962688] GLRenderer: GL version: OpenGL ES 3.0 Mesa 11.2.0
  [2016-04-27 15:20:51.962697] GLRenderer: GLSL version: OpenGL ES GLSL ES 3.00

  lspci:
  01:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] 
(rev a1)

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

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

[Desktop-packages] [Bug 1641288] Re: TexMaths extension issue after installing libatk-adaptor

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

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

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

Title:
  TexMaths extension issue after installing libatk-adaptor

Status in libreoffice package in Ubuntu:
  Expired

Bug description:
  The TexMaths extension has an issue if the package libatk-adaptor is
  installed on Ubuntu (as a dependency of gnome-orca for example).
  TexMaths is a popular extension used to enter / edit LaTeX equations
  on LibreOffice (see http://roland65.free.fr/texmaths).

  Step to reproduce the bug:

  1. It is assumed that LibreOffice 5.1.4 (with at least the Writer and
  Draw components) is installed on Ubuntu. It is also assumed that
  libatk-adaptor is installed.

  2. Install texlive:
  sudo apt-get install texlive

  3. Download and install the TexMaths extension (version 0.42) from
  there: https://sourceforge.net/projects/texmaths/files/0.42/

  4. Create a new empty Writer document, then click on the Pi icon (this
  is the TexMaths icon) and in the window that opens, type: 'x(t)+y(t)'
  (without the quotes), then click on the LaTeX button. This generates
  an SVG image of the 'x(t)+y(t)' equation.

  5. Select the SVG image of the equation by left clicking on it. Then
  click on the Pi icon. Now, instead of editing the equation, an error
  message is displayed: "The selected object is not a TexMaths
  equation... Please unselect it and call the macro again...".

  6. Now, right click on the SVG image and select the 'Description' menu
  voice. In the window that opens, the description is empty and does not
  contain the equation text, as it should.

  7. Now purge (and not just remove) the libatk-adaptor package:

  sudo apt-get purge libatk-adaptor

  then logout and login and repeat the steps 4, 5, and 6: everything is
  OK and the equation can be edited as usual.

  Another way to remove the bug instead of purging libatk-adaptor is to
  rename the file: /etc/X11/Xsession.d/90atk-adaptor to
  /etc/X11/Xsession.d/90atk-adaptor.orig . Then logout and login.

  I don't know where the bug is so I reported this bug against the
  libreoffice and libatk-adaptor packages.

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

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

[Desktop-packages] [Bug 764253] Re: unity panel does not hide if libreoffice set to fullscreen

2017-01-20 Thread John Pye

This problem seems to have re-emerged. I am on Ubuntu 16.04 using
LibreOffice Fresh 5.2.4.2 from the LO packaging team (PPA). I will
report the issue over there.

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

Title:
  unity panel does not hide if libreoffice set to fullscreen

Status in Unity:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: unity

  If I set a libreoffice application (which is not maximized) to
  fullscreen the unity panel does not hide and obscures the application.
  This does not happen if I set it to fullscreen after it is maximized.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: unity 3.8.8-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,scale,session,unityshell]
  Date: Sun Apr 17 22:28:26 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to natty on 2011-04-12 (5 days ago)

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

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

[Desktop-packages] [Bug 1633162] Re: Files application throws an error 'Oops! Something went wrong' when clicked on 'Recents'

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

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

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

Title:
  Files application throws an error 'Oops! Something went wrong' when
  clicked on 'Recents'

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

Bug description:
  The application crashes every time I click on 'Recent' with this
  message in a pop-up window:

  "Unhandled error message: Message recipient disconnected from message
  bus without replying."

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Oct 13 22:34:57 2016
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'enable-interactive-search' b'false'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+476+24'"
  InstallationDate: Installed on 2016-10-13 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

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

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

[Desktop-packages] [Bug 1591868] Re: fwupd consuming 100% CPU

2017-01-20 Thread Jairo Andres Moreno

Hi all,
I updated too my files. But, I'm still experiencing high CPU consumption by 
fwupd and gnome-software.

Package: libappstream-glib8
Version: 0.5.13-1ubuntu4
Priority: optional
Section: libs
Source: appstream-glib
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Matthias Klumpp 
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 312 kB
Depends: libarchive13, libc6 (>= 2.14), libgcab-1.0-0 (>= 0.4), 
libgdk-pixbuf2.0-0 (>= 2.25.2), libglib2.0-0 (>= 2.46), libsoup2.4-1 (>= 2.52), 
libuuid1 (>= 2.16), libyaml-0-2
Homepage: http://people.freedesktop.org/~hughsient/appstream-glib/
Task: ubuntu-desktop, ubuntu-usb, kubuntu-desktop, edubuntu-desktop, 
edubuntu-usb, xubuntu-core, xubuntu-desktop, mythbuntu-desktop, lubuntu-core, 
ubuntustudio-desktop-core, ubuntustudio-desktop, ubuntu-gnome-desktop, 
ubuntukylin-desktop, ubuntu-mate-core, ubuntu-mate-desktop, ubuntu-mate-cloudtop
Supported: 5y
Download-Size: 101 kB
APT-Manual-Installed: no
APT-Sources: http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
Description: GNOME library to access AppStream services
 AppStream is a cross-distribution effort for creating and sharing
 metadata about software components available in the package repositories
 of a distribution.
 .
 This package contains a GObject-based library to read and write AppStream
 XML metadata and retrieve additional data such as screenshots.
 .
 As opposed to libappstream, this library does not use an on-disk cache but
 reads data directly from the XML or DEP-11 YAML files.

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

Title:
  fwupd consuming 100% CPU

Status in appstream-glib package in Ubuntu:
  Fix Released
Status in appstream-glib source package in Xenial:
  Fix Released
Status in appstream-glib source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

   * Corrupt yaml data is causing consumers of appstream data (such as
  gnome-software or fwupd) to get stuck in a spin and consume CPU and
  battery.

  [Test Case]

   * Introduce corrupt data into /var/lib/app-info/yaml/
   * Execute sudo /usr/lib/x86_64-linux-gnu/fwupd/fwupd -v
   * Check CPU usage calms down after initialization

  [Regression Potential]

   * This patch has been backported from a newer stable release upstream.
   * Due to the nature of backporting, it doesn't directly apply to Ubuntu and 
will need some adjustments made.
   * Regressions would occur in gnome-software not displaying software or fwupd 
not running properly.

  [Other Info]
   
  Original bug report: 

  fwupd process has been consuming 100% of my CPU for several days now
  (IBM Thinkpad x250 running fully updated 16.04).

  gdb backtrace below.

  Thread 2 (Thread 0x7f3272cf5700 (LWP 4496)):
  #0  0x7f3279b79e8d in poll () at ../sysdeps/unix/syscall-template.S:84
  No locals.
  #1  0x7f327ae9331c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #2  0x7f327ae9342c in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #3  0x7f327ae93469 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #4  0x7f327aeb9b45 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #5  0x7f3279e4f6fa in start_thread (arg=0x7f3272cf5700) at 
pthread_create.c:333
  __res = 
  pd = 0x7f3272cf5700
  now = 
  unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139854651283200, 
418179942412000561, 0, 140731891236207,
  139854651283904, 0, -312637405101744847, 
-312613451844084431}, mask_was_saved = 0}}, priv = {pad = {
    0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, 
canceltype = 0}}}
  not_first_call = 
  pagesize_m1 = 
  sp = 
  freesize = 
  __PRETTY_FUNCTION__ = "start_thread"
  #6  0x7f3279b85b5d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109
  No locals.

  Thread 1 (Thread 0x7f327c926900 (LWP 4486)):
  #0  0x7f3279e542b7 in __GI___pthread_rwlock_rdlock (rwlock=0x7f3279e43920 
<__libc_setlocale_lock>)
  at pthread_rwlock_rdlock.c:135
  result = 0
  wake = false
  #1  0x7f3279aaf0e9 in __dcigettext (domainname=0x7f327aedee63 "glib20",
  msgid1=0x7f327b4ca11a "Invalid compressed data", msgid2=0x0, plural=0, 
n=0, category=5) at dcigettext.c:527
  __p = 
  domain = 
  binding = 
  categoryname = 
  categoryvalue = 
  dirname = 
  xdomainname = 
  single_locale = 
  retval = 
  retlen = 93892446493824
  saved_errno = 0
  search = {domainname = 0x7ffeb262bb00 "`\234\353\teU", category =

[Desktop-packages] [Bug 1658252] [NEW] nvidia-304 304.134-0ubuntu0.16.04.1: nvidia-304 kernel module failed to build

Public bug reported:

nvidia-367 broke my system. Now I can't get any nvidia-xxx version to
work.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: nvidia-304 304.134-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
DKMSKernelVersion: 4.4.0-62-generic
Date: Fri Jan 20 19:28:03 2017
DistUpgraded: 2016-11-19 22:58:31,519 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-53-generic, x86_64: installed
 bbswitch, 0.8, 4.4.0-57-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.4.0-53-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.4.0-57-generic, x86_64: installed
 nvidia-304, 304.134: added
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] 4th Gen Core Processor Integrated 
Graphics Controller [1025:091d]
   Subsystem: Acer Incorporated [ALI] GM107M [GeForce GTX 860M] [1025:091d]
InstallationDate: Installed on 2015-05-21 (610 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Acer Aspire VN7-791
PackageVersion: 304.134-0ubuntu0.16.04.1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=e983f70e-9e5b-4d5a-90b4-0f4025b8f2b6 ro ath9k.nohwcrypt=1 
ath9k.btcoex_enable=1 modprobe.blacklist=ath3k acpi_osi=Linux
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: nvidia-graphics-drivers-304
Title: nvidia-304 304.134-0ubuntu0.16.04.1: nvidia-304 kernel module failed to 
build
UpgradeStatus: Upgraded to xenial on 2016-11-20 (61 days ago)
dmi.bios.date: 09/05/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.07
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Aspire VN7-791
dmi.board.vendor: Acer
dmi.board.version: V1.07
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.07
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.07:bd09/05/2014:svnAcer:pnAspireVN7-791:pvrV1.07:rvnAcer:rnAspireVN7-791:rvrV1.07:cvnAcer:ct10:cvrV1.07:
dmi.product.name: Aspire VN7-791
dmi.product.version: V1.07
dmi.sys.vendor: Acer
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.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Jan 20 19:28:53 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1129 
 vendor LGD
xserver.version: 2:1.18.4-0ubuntu0.2

** Affects: nvidia-graphics-drivers-304 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package compiz-0.9 possible-manual-nvidia-install 
third-party-packages ubuntu xenial

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

Title:
  nvidia-304 304.134-0ubuntu0.16.04.1: nvidia-304 kernel module failed
  to build

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

Bug description:
  nvidia-367 broke my system. Now I can't get any nvidia-xxx version to
  work.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-304 304.134-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DKMSKernelVersion: 4.4.0-62-generic
  Date: Fri Jan 20 19:28:03 2017
  DistUpgraded: 2016-11-19 22:58:31,519 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-53-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-57-generic, x86_64: installed

[Desktop-packages] [Bug 1658112] Re: System wide proxy settings are not seen by users who didn't first initiated the proxy config

2017-01-20 Thread Mark Thomas

Confirmed.

** Changed in: unity-control-center (Ubuntu)
   Status: New => Triaged

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

** Changed in: unity-control-center (Ubuntu)
   Status: Triaged => Confirmed

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

Title:
  System wide proxy settings are not seen by users who didn't first
  initiated the proxy config

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

Bug description:
  System wide proxy settings are not seen by users who didn't first
  initiated the proxy configuration.

  If the initial configuration has been made by "user1", only this user
  will show the configuration in network applet, the other users won't
  see anything.

  Reproducer ;
  1. Set proxy with UI on user1 (without protocol in front of it (e.g. http://, 
https://,)
  Method  : Manual
  HTTP Proxy  : test.com Port : 8080
  HTTPS Proxy : test.com Port : 9090

  Click "Apply system wide"

  2. Create user user2
  3. Logout user1
  4. Login as user2
  5. Look configuration:

  - Network applet won't change, remaining set to 'none'
  - "gsettings get org.gnome.system.proxy mode" return 'none' instead of 
'manual'
  - "dconf read /system/proxy/mode" return nothing.

  The only test I found to validate was the following:

  - Check proxy variables :
  $ echo $http_proxy
  $ echo $https_proxy
  $ echo $ftp_proxy

  * You should see the value created by user1.

  - Try web browser and validate it goes through the proxy

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

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

[Desktop-packages] [Bug 1658118] Re: Network applet should warn or generate a warning/error if user tries to add protocol in front of the proxy value

2017-01-20 Thread Mark Thomas

Confirmed.

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

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

Title:
  Network applet should warn or generate a warning/error if user tries
  to add protocol in front of the proxy value

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

Bug description:
  Reproducer ;

  1. Set proxy with UI on user1
  Method : Manual
  HTTP Proxy : http://test.com Port : 8080
  HTTPS Proxy : https://test.com Port : 9090

  Click "Apply system wide"

  No warning/error will be shown, but if looking at :
  - /etc/environment
  - /etc/apt/apt.conf

  They won't be updated/created.

  The reason is because the protocol is automatically added during the
  saving process so that the configuration should look as follow :
  (without the protocol http://, https://)

  Method : Manual
  HTTP Proxy : test.com Port : 8080
  HTTPS Proxy : test.com Port : 9090

  In order to improve the user experience, it would be great to have a
  mechanism that detect if the protocol has been accidentally added to
  the field, or at least a quick message in the applet window to let the
  user know to not add the protocol.

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

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

[Desktop-packages] [Bug 1658118] Re: Network applet should warn or generate a warning/error if user tries to add protocol in front of the proxy value

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

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

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

Title:
  Network applet should warn or generate a warning/error if user tries
  to add protocol in front of the proxy value

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

Bug description:
  Reproducer ;

  1. Set proxy with UI on user1
  Method : Manual
  HTTP Proxy : http://test.com Port : 8080
  HTTPS Proxy : https://test.com Port : 9090

  Click "Apply system wide"

  No warning/error will be shown, but if looking at :
  - /etc/environment
  - /etc/apt/apt.conf

  They won't be updated/created.

  The reason is because the protocol is automatically added during the
  saving process so that the configuration should look as follow :
  (without the protocol http://, https://)

  Method : Manual
  HTTP Proxy : test.com Port : 8080
  HTTPS Proxy : test.com Port : 9090

  In order to improve the user experience, it would be great to have a
  mechanism that detect if the protocol has been accidentally added to
  the field, or at least a quick message in the applet window to let the
  user know to not add the protocol.

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

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

[Desktop-packages] [Bug 1591868] Re: fwupd consuming 100% CPU

2017-01-20 Thread Marcelo Fernandez

Hi, I'm fully updated and still having this issue. Do you know what
could be wrong?

Thankyou

marcelo@marcelo-notebook:~$ apt show libappstream-glib8
Package: libappstream-glib8
Version: 0.5.13-1ubuntu4
Priority: optional
Section: libs
Source: appstream-glib
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Matthias Klumpp 
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 312 kB
Depends: libarchive13, libc6 (>= 2.14), libgcab-1.0-0 (>= 0.4), 
libgdk-pixbuf2.0-0 (>= 2.25.2), libglib2.0-0 (>= 2.46), libsoup2.4-1 (>= 2.52), 
libuuid1 (>= 2.16), libyaml-0-2
Homepage: http://people.freedesktop.org/~hughsient/appstream-glib/
Task: ubuntu-desktop, ubuntu-usb, kubuntu-desktop, edubuntu-desktop, 
edubuntu-usb, xubuntu-core, xubuntu-desktop, mythbuntu-desktop, lubuntu-core, 
ubuntustudio-desktop-core, ubuntustudio-desktop, ubuntu-gnome-desktop, 
ubuntukylin-desktop, ubuntu-mate-core, ubuntu-mate-desktop, ubuntu-mate-cloudtop
Supported: 5y
Download-Size: 101 kB
APT-Manual-Installed: no
APT-Sources: http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
Description: GNOME library to access AppStream services
 AppStream is a cross-distribution effort for creating and sharing
 metadata about software components available in the package repositories
 of a distribution.
 .
 This package contains a GObject-based library to read and write AppStream
 XML metadata and retrieve additional data such as screenshots.
 .
 As opposed to libappstream, this library does not use an on-disk cache but
 reads data directly from the XML or DEP-11 YAML files.

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

Title:
  fwupd consuming 100% CPU

Status in appstream-glib package in Ubuntu:
  Fix Released
Status in appstream-glib source package in Xenial:
  Fix Released
Status in appstream-glib source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

   * Corrupt yaml data is causing consumers of appstream data (such as
  gnome-software or fwupd) to get stuck in a spin and consume CPU and
  battery.

  [Test Case]

   * Introduce corrupt data into /var/lib/app-info/yaml/
   * Execute sudo /usr/lib/x86_64-linux-gnu/fwupd/fwupd -v
   * Check CPU usage calms down after initialization

  [Regression Potential]

   * This patch has been backported from a newer stable release upstream.
   * Due to the nature of backporting, it doesn't directly apply to Ubuntu and 
will need some adjustments made.
   * Regressions would occur in gnome-software not displaying software or fwupd 
not running properly.

  [Other Info]
   
  Original bug report: 

  fwupd process has been consuming 100% of my CPU for several days now
  (IBM Thinkpad x250 running fully updated 16.04).

  gdb backtrace below.

  Thread 2 (Thread 0x7f3272cf5700 (LWP 4496)):
  #0  0x7f3279b79e8d in poll () at ../sysdeps/unix/syscall-template.S:84
  No locals.
  #1  0x7f327ae9331c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #2  0x7f327ae9342c in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #3  0x7f327ae93469 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #4  0x7f327aeb9b45 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #5  0x7f3279e4f6fa in start_thread (arg=0x7f3272cf5700) at 
pthread_create.c:333
  __res = 
  pd = 0x7f3272cf5700
  now = 
  unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139854651283200, 
418179942412000561, 0, 140731891236207,
  139854651283904, 0, -312637405101744847, 
-312613451844084431}, mask_was_saved = 0}}, priv = {pad = {
    0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, 
canceltype = 0}}}
  not_first_call = 
  pagesize_m1 = 
  sp = 
  freesize = 
  __PRETTY_FUNCTION__ = "start_thread"
  #6  0x7f3279b85b5d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109
  No locals.

  Thread 1 (Thread 0x7f327c926900 (LWP 4486)):
  #0  0x7f3279e542b7 in __GI___pthread_rwlock_rdlock (rwlock=0x7f3279e43920 
<__libc_setlocale_lock>)
  at pthread_rwlock_rdlock.c:135
  result = 0
  wake = false
  #1  0x7f3279aaf0e9 in __dcigettext (domainname=0x7f327aedee63 "glib20",
  msgid1=0x7f327b4ca11a "Invalid compressed data", msgid2=0x0, plural=0, 
n=0, category=5) at dcigettext.c:527
  __p = 
  domain = 
  binding = 
  categoryname = 
  categoryvalue = 
  dirname = 
  xdomainname = 
  single_locale = 
  retval = 
  retlen = 93892446493824
  saved_errno = 0
  search = {domainname = 0x7ffeb262bb00

[Desktop-packages] [Bug 1613032] Re: nvidia-340 340.96-0ubuntu3: nvidia-340 kernel module failed to build

367 broke my OS, and now the older versions don't work either.

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

Title:
  nvidia-340 340.96-0ubuntu3: nvidia-340 kernel module failed to build

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

Bug description:
  it occurred during update.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-340 340.96-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia wl
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.96  Sun Nov  8 22:33:28 
PST 2015
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1)
  .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
  DKMSKernelVersion: 4.4.0-34-generic
  Date: Sun Aug 14 02:22:29 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation G98M [Quadro NVS 160M] [10de:06eb] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell G98M [Quadro NVS 160M] [1028:0233]
  InstallationDate: Installed on 2016-05-21 (84 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  MachineType: Dell Inc. Latitude E6400
  PackageVersion: 340.96-0ubuntu3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=71f8e502-b3db-4136-be54-c6d93836994d ro
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.96-0ubuntu3: nvidia-340 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A33
  dmi.board.name: 0U695R
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA33:bd09/03/2012:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0U695R:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude E6400
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-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.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: Sun Aug 14 09:02:15 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.3-1ubuntu2.3

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

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

[Desktop-packages] [Bug 1658250] [NEW] Window positions change in nonsensical ways when a secondary display is moved above the primary

2017-01-20 Thread Ben A

Public bug reported:

Most commonly, they'll be partway on the upper monitor, but mostly on
the bottom. But sometimes, they'll be halfway off the screen on the
bottom monitor. New windows are sometimes created in slightly odd places
as well; usually, the titlebar will be on the top screen and the rest of
the window on the bottom, meaning the gnome-shell bar is obscuring part
of the window.

Windows that are maximized when the change is made aren't affected.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu2
ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
Uname: Linux 4.9.0-11-generic x86_64
ApportVersion: 2.20.4-0ubuntu1
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Fri Jan 20 18:09:51 2017
DistUpgraded: 2017-01-17 21:44:12,781 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] 
[1002:67df] (rev c7) (prog-if 00 [VGA controller])
   Subsystem: XFX Pine Group Inc. Radeon RX 480 [1682:9480]
InstallationDate: Installed on 2017-01-17 (3 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
MachineType: ASUS All Series
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic 
root=UUID=638d73c8-aa0e-423b-907c-6bbb2c237275 ro i915.modeset=0 quiet splash 
vt.handoff=7
Renderer: Software
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to zesty on 2017-01-18 (2 days ago)
dmi.bios.date: 08/07/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2004
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H87M-E
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2004:bd08/07/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.74-1
version.libgl1-mesa-dri: libgl1-mesa-dri 13.0.3-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 13.0.3-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.8.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Mon Jan 16 20:46:55 2017
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: amd64 apport-bug reproducible single-occurrence third-party-packages 
ubuntu zesty

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

Title:
  Window positions change in nonsensical ways when a secondary display
  is moved above the primary

Status in xorg package in Ubuntu:
  New

Bug description:
  Most commonly, they'll be partway on the upper monitor, but mostly on
  the bottom. But sometimes, they'll be halfway off the screen on the
  bottom monitor. New windows are sometimes created in slightly odd
  places as well; usually, the titlebar will be on the top screen and
  the rest of the window on the bottom, meaning the gnome-shell bar is
  obscuring part of the window.

  Windows that are maximized when the change is made aren't affected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Jan 20 18:09:51 2017
  DistUpgraded: 2017-01-17 21:44:12,781 DEBUG Running

[Desktop-packages] [Bug 1639471] Re: nvidia-367 broken by upgrade to .57

Why in the world is every earlier version dependent upon the 367
version? So I can't go back to a working driver? Asinine.

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

Title:
  nvidia-367 broken by upgrade to .57

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

Bug description:
  laptop with intel and Nvidia GT 860M was working fine with primusrun
  to run Steam games.  After automated update to -367.57, it is entirely
  broken.  when I run primusrun  the screen mode is changed to
  an unusable one (screens become mirrored, making content on the lower
  screen inaccessible.)  and it does segmentation fault, core dumped.

  
  00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor 
Integrated Graphics Controller (rev 06)
  0
  01:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 860M] (rev a2)

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

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

[Desktop-packages] [Bug 1639471] Re: nvidia-367 broken by upgrade to .57

`sudo apt-get install --reinstall bumblebee bumblebee-nvidia` didn't
work for me. When I try to my prime on NVIDIA performance mode it goes
back to intel power save mode on logout/login.

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

Title:
  nvidia-367 broken by upgrade to .57

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

Bug description:
  laptop with intel and Nvidia GT 860M was working fine with primusrun
  to run Steam games.  After automated update to -367.57, it is entirely
  broken.  when I run primusrun  the screen mode is changed to
  an unusable one (screens become mirrored, making content on the lower
  screen inaccessible.)  and it does segmentation fault, core dumped.

  
  00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor 
Integrated Graphics Controller (rev 06)
  0
  01:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 860M] (rev a2)

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

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

[Desktop-packages] [Bug 1639471] Re: nvidia-367 broken by upgrade to .57

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

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

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

Title:
  nvidia-367 broken by upgrade to .57

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

Bug description:
  laptop with intel and Nvidia GT 860M was working fine with primusrun
  to run Steam games.  After automated update to -367.57, it is entirely
  broken.  when I run primusrun  the screen mode is changed to
  an unusable one (screens become mirrored, making content on the lower
  screen inaccessible.)  and it does segmentation fault, core dumped.

  
  00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor 
Integrated Graphics Controller (rev 06)
  0
  01:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 860M] (rev a2)

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

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

[Desktop-packages] [Bug 1658237] [NEW] /usr/bin/gnome-software:* Error in `gnome-software': double free or corruption (fasttop): ADDR *

2017-01-20 Thread errors.ubuntu.com bug bridge

Public bug reported:

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

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


** Tags: xenial yakkety

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

Title:
  /usr/bin/gnome-software:*** Error in `gnome-software': double free or
  corruption (fasttop): ADDR ***

Status in gnome-software package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner

2017-01-20 Thread chrissy mcmanus

Juan's fix worked for me. 
I find that I cannot slow down the mouse speed through both the system menu and 
unity-tweaks, but i can get used to it i guess. It has tho given me back 
middle-mouse-button click emulation by means of using left and right click 
simultaneously, so this is a win win situation

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

Title:
  Mouse pointer occasionally jumps to the bottom-left corner

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the mouse pointer jumps directly to the bottom-left corner
  of the screen, which results in opening the trash window when
  clicking.

  This seems to be related: https://ubuntu-mate.community/t/mouse-
  pointer-jumps-on-clicking-touchpad/2932.

  Thanks,
  MZ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr 25 15:55:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
  InstallationDate: Installed on 2016-04-23 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 064e:920b Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.5
  dmi.board.name: 06CMH7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.
  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.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: Mon Apr 25 13:43:44 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1156 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Desktop-packages] [Bug 1635050] Re: Some panel icons disappear after turning display off/on

2017-01-20 Thread trikrasne

it seems this bug have been solved.

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

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

Title:
  Some panel icons disappear after turning display off/on

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  When I boot into Ubuntu all panel icons are ok, but after turning the
  screen off (closing lid) and on again some icons disappear and get
  replaced with some generic "missing" icons.

  This happens with Mega and Bitmask icons but the applications still
  work. And if i quit one of those two apps the icon of another appears
  again.

  before:
  https://drive.google.com/open?id=0B4b2sRiO8XlMUkJDWTR0a0ptcFk

  after:
  https://drive.google.com/open?id=0B4b2sRiO8XlMcHRMQzJmbm90azQ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.57  Mon Oct  3 20:37:01 
PDT 2016
   GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  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: Wed Oct 19 23:09:11 2016
  DistUpgraded: 2016-10-18 09:22:45,469 DEBUG icon theme changed, re-reading
  DistroCodename: yakkety
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:13ad]
 Subsystem: ASUSTeK Computer Inc. GeForce GT 730M [1043:13ad]
  InstallationDate: Installed on 2015-08-20 (426 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. UX302LG
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to yakkety on 2016-10-18 (1 days ago)
  dmi.bios.date: 06/16/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX302LG.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX302LG
  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.:bvrUX302LG.210:bd06/16/2014:svnASUSTeKCOMPUTERINC.:pnUX302LG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX302LG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX302LG
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Wed Oct 19 19:43:23 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6

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

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

[Desktop-packages] [Bug 1658205] [NEW] caps lock LED stopped working

2017-01-20 Thread svenmeier

Public bug reported:

Starting with 4.8.0-34 or -35 the CAPS lock LED no longer lights up when
CAPS lock is turned on.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: gnome-settings-daemon 3.22.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-36.38-generic 4.8.16
Uname: Linux 4.8.0-36-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Jan 20 22:57:31 2017
SourcePackage: gnome-settings-daemon
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug yakkety

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

Title:
  caps lock LED stopped working

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

Bug description:
  Starting with 4.8.0-34 or -35 the CAPS lock LED no longer lights up
  when CAPS lock is turned on.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-settings-daemon 3.22.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-36.38-generic 4.8.16
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jan 20 22:57:31 2017
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1619354] Re: [SRU] network-manager-applet

2017-01-20 Thread Amr Ibrahim

Parallel building is allowed in network-manager (1.2.6-0ubuntu0.16.04.1)
in Xenial Unapproved queue.

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

Title:
  [SRU] network-manager-applet

Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Xenial:
  In Progress
Status in network-manager-applet source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

  Several defects in network-manager-applet can lead to crashes under
  certain circumstance as tracked in errors.ubuntu.com, upstream stable
  bug fix release 1.2.6 should fix a big portion of the bugs while no
  feature is being added or changed.

  [Test Case]

  After upgrading to 1.2.6, crash cases should be lesser than previous,
  and no functional regression should be observed.

  [Regression Potential]

  Potential of causing regression is minimal as upstream fixes aren't
  significant in this small package during the stable branch
  maintenance.

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

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

[Desktop-packages] [Bug 1655362] Re: Brother ADS-2100e Scanner does not work out of the box in 16.04

2017-01-20 Thread Christian González

Ok, I'll check next week. Will have more time then.

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

Title:
  Brother ADS-2100e Scanner does not work out of the box in 16.04

Status in simple-scan package in Ubuntu:
  Incomplete

Bug description:
  What I expect is my Brother ADS-2100e scanner to work out of the box.
  What happens instead is it doesn't.

  But Ubuntu lacks of a proper recognition - it seems to be a missing UDEV 
rule. The scanner is recognized by lsusb as "04f9:037d":
  Bus 003 Device 005: ID 04f9:037d Brother Industries, Ltd

  And dmesg tells me:
  [ 8075.564495] usb 3-1: new high-speed USB device number 4 using xhci_hcd
  [ 8075.693751] usb 3-1: New USB device found, idVendor=04f9, idProduct=037d
  [ 8075.693760] usb 3-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [ 8075.693764] usb 3-1: Product: ADS-2100e
  [ 8075.693768] usb 3-1: Manufacturer: Brother
  [ 8075.693771] usb 3-1: SerialNumber: E74188A6G337846
  [ 8079.128671] usb 3-1: USB disconnect, device number 4
  [ 8080.644164] usb 3-1: new high-speed USB device number 5 using xhci_hcd
  [ 8080.773321] usb 3-1: New USB device found, idVendor=04f9, idProduct=037d
  [ 8080.773325] usb 3-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [ 8080.773327] usb 3-1: Product: ADS-2100e
  [ 8080.773329] usb 3-1: Manufacturer: Brother
  [ 8080.773331] usb 3-1: SerialNumber: E74188A6G337846

  WORKAROUND: Install Brother linux (deb) driver brscan4-0.4.4-1.amd64.deb from:
  
http://support.brother.com/g/b/downloadtop.aspx?c=at=de=ads2100e_eu_as_cn

  Then, create file /etc/udev/rules.d/39-brother.rules :
  ATTRS{idVendor}=="04f9", ATTRS{idProduct}=="037d", ENV{libsane_matched}="yes"

  "39" because it needs to run BEFORE the
  /lib/udev/rules.d/40-libsane.rules - there is the variable
  "libsane_matched" needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: simple-scan 3.20.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 10 15:37:14 2017
  InstallationDate: Installed on 2016-12-13 (28 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP ProDesk 600 G1 TWR
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-57-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L01 v02.21
  dmi.board.asset.tag: CZC411388T
  dmi.board.name: 18E7
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC411388T
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.21:bd12/17/2013:svnHewlett-Packard:pnHPProDesk600G1TWR:pvr:rvnHewlett-Packard:rn18E7:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP ProDesk 600 G1 TWR
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1655362/+subscriptions

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

[Desktop-packages] [Bug 1657469] Re: nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to build [In function ‘uvm8_test_range_allocator_sanity’: internal compiler error: Speicherzugr

2017-01-20 Thread Ralf Wiessner

additional infos:

~$ sudo dpkg -l | grep gcc-5
ii  gcc-5   5.4.0-6ubuntu1~16.04.4amd64 
   GNU C compiler
ii  gcc-5-base:amd645.4.0-6ubuntu1~16.04.4amd64 
   GCC, the GNU Compiler Collection (base package)
ii  libgcc-5-dev:amd64  5.4.0-6ubuntu1~16.04.4amd64 
   GCC support library (development files)
 
~$ sudo dpkg -l | grep nvidia
ii  nvidia-367 367.57-0ubuntu0.16.04.1   amd64  
  NVIDIA binary driver - version 367.57
ii  nvidia-opencl-icd-367  367.57-0ubuntu0.16.04.1   amd64  
  NVIDIA OpenCL ICD
ii  nvidia-prime   0.8.2 amd64  
  Tools to enable NVIDIA's Prime
ii  nvidia-settings361.42-0ubuntu1   amd64  
  Tool for configuring the NVIDIA graphics driver

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

Title:
  nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to
  build [In function ‘uvm8_test_range_allocator_sanity’: internal
  compiler error: Speicherzugriffsfehler]

Status in gcc-5 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Invalid

Bug description:
  after update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-367 367.57-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-59-generic
  Date: Wed Jan 18 14:52:59 2017
  InstallationDate: Installed on 2016-11-21 (58 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageVersion: 367.57-0ubuntu0.16.04.1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: nvidia-graphics-drivers-367
  Title: nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1657469/+subscriptions

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

[Desktop-packages] [Bug 1658185] [NEW] nouveau occasionally won't come back from DPMS suspend/off

2017-01-20 Thread David R. Hedges

Public bug reported:

On several occasions over the past few months, I've moved my mouse or
pressed a key to wake my monitor from power saving, but the monitor
never leaves power saving. I can still ssh into the machine. The GPU is
GK104 [GeForce GTX 770] (as reported by lshw).

On this occasion, at least, the syslog contained the following errors:
kernel: [53037.908926] nouveau :01:00.0: fifo: SCHED_ERROR 0a 
[CTXSW_TIMEOUT]
kernel: [53037.908932] nouveau :01:00.0: fifo: gr engine fault on channel 
7, recovering...
kernel: [53037.909454] nouveau :01:00.0: fifo: write fault at 001e444000 
engine 00 [GR] client 0f [GPC2/PROP_0] reason 02 [PTE] on channel 5 [00ff534000 
compiz[5762]]
kernel: [53037.909457] nouveau :01:00.0: fifo: gr engine fault on channel 
5, recovering...

Xorg.0.log.old ends with these un-timestamped errors that may or may not be 
related:
(EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
(EE) 
(EE) Backtrace:
(EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x55919392a9fa]
(EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x55919390c4b3]
(EE) 2: /usr/lib/xorg/Xorg (QueueKeyboardEvents+0x52) [0x5591937dc902]
(EE) 3: /usr/lib/xorg/Xorg (xf86PostKeyboardEvent+0x3b) [0x5591938162db]
(EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f3a1e3fe000+0x63cf) 
[0x7f3a1e4043cf]
(EE) 5: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f3a1e3fe000+0x6a8d) 
[0x7f3a1e404a8d]
(EE) 6: /usr/lib/xorg/Xorg (0x559193771000+0x95438) [0x559193806438]
(EE) 7: /usr/lib/xorg/Xorg (0x559193771000+0xba8f2) [0x55919382b8f2]
(EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3a278b8000+0x35860) 
[0x7f3a278ed860]
(EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f3a279b58b5]
(EE) 10: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7f3a28c990f8]
(EE) 11: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b) 
[0x7f3a28c9bdbb]
(EE) 12: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 (nouveau_bo_wait+0xbc) 
[0x7f3a237c403c]
(EE) 13: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f3a239c9000+0xc839) 
[0x7f3a239d5839]
(EE) 14: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f3a239c9000+0xd25d) 
[0x7f3a239d625d]
(EE) 15: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x5591938fd398]
(EE) 16: /usr/lib/xorg/Xorg (0x559193771000+0x18dc6d) [0x5591938fec6d]
(EE) 17: /usr/lib/xorg/Xorg (0x559193771000+0x533bf) [0x5591937c43bf]
(EE) 18: /usr/lib/xorg/Xorg (0x559193771000+0x57413) [0x5591937c8413]
(EE) 19: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf1) 
[0x7f3a278d83f1]
(EE) 20: /usr/lib/xorg/Xorg (_start+0x2a) [0x5591937b233a]
(EE) 
(EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
(EE) [mi] mieq is *NOT* the cause.  It is a victim.
(EE) [mi] EQ overflow continuing.  100 events have been dropped.
(EE) 
(EE) Backtrace:
(EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x55919392a9fa]
(EE) 1: /usr/lib/xorg/Xorg (QueueKeyboardEvents+0x52) [0x5591937dc902]
(EE) 2: /usr/lib/xorg/Xorg (xf86PostKeyboardEvent+0x3b) [0x5591938162db]
(EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f3a1e3fe000+0x63cf) 
[0x7f3a1e4043cf]
(EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f3a1e3fe000+0x6a8d) 
[0x7f3a1e404a8d]
(EE) 5: /usr/lib/xorg/Xorg (0x559193771000+0x95438) [0x559193806438]
(EE) 6: /usr/lib/xorg/Xorg (0x559193771000+0xba8f2) [0x55919382b8f2]
(EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3a278b8000+0x35860) 
[0x7f3a278ed860]
(EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f3a279b58b5]
(EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7f3a28c990f8]
(EE) 10: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b) 
[0x7f3a28c9bdbb]
(EE) 11: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 (nouveau_bo_wait+0xbc) 
[0x7f3a237c403c]
(EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f3a239c9000+0xc839) 
[0x7f3a239d5839]
(EE) 13: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f3a239c9000+0xd25d) 
[0x7f3a239d625d]
(EE) 14: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x5591938fd398]
(EE) 15: /usr/lib/xorg/Xorg (0x559193771000+0x18dc6d) [0x5591938fec6d]
(EE) 16: /usr/lib/xorg/Xorg (0x559193771000+0x533bf) [0x5591937c43bf]
(EE) 17: /usr/lib/xorg/Xorg (0x559193771000+0x57413) [0x5591937c8413]
(EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf1) 
[0x7f3a278d83f1]
(EE) 19: /usr/lib/xorg/Xorg (_start+0x2a) [0x5591937b233a]

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xserver-xorg-video-nouveau 1:1.0.12-2
ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
Uname: Linux 4.8.0-34-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8.2
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: Fri Jan 20 14:02:18 2017
DistUpgraded: Fresh install

[Desktop-packages] [Bug 1174694] Re: wpa_supplicant it's CPU hog and generate errors

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

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

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

Title:
  wpa_supplicant it's CPU hog and generate errors

Status in wpasupplicant package in Ubuntu:
  Confirmed

Bug description:
  wpa_supplicant eats lot of CPU resources and generate repeated errors:
  iwl3945 :03:00.0: Radio disabled by HW RF Kill switch

  This error appears even if WiFi switch is set to off.
  'sudo modprobe -r iwl3945' disables wpa_supplicant and errors stop.

  If I switch WiFi on and connect to my hotspot everything back to
  normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-19-lowlatency 3.8.0-19.13
  ProcVersionSignature: Ubuntu 3.8.0-19.13-lowlatency 3.8.8
  Uname: Linux 3.8.0-19-lowlatency i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Tue Apr 30 12:17:06 2013
  InstallationDate: Installed on 2012-04-29 (365 days ago)
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  MarkForUpload: True
  SourcePackage: linux-lowlatency
  UpgradeStatus: Upgraded to raring on 2013-04-26 (4 days ago)

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

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

[Desktop-packages] [Bug 1657882] Re: wine

2017-01-20 Thread Paul White

** Package changed: xorg (Ubuntu) => wine (Ubuntu)

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

Title:
  wine

Status in wine package in Ubuntu:
  New

Bug description:
  cant install wine

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Jan 19 21:39:58 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8330] [1002:9832] 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Kabini [Radeon HD 8330] [1025:104b]
  InstallationDate: Installed on 2016-12-01 (49 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Acer Aspire ES1-520
  ProcEnviron:
   LANGUAGE=hr
   PATH=(custom, no user)
   LANG=hr_HR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed 
root=UUID=073388fc-a929-4eae-81b3-5f775ced2d93 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Bellemere_BE
  dmi.board.vendor: Acer
  dmi.board.version: V1.06
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd08/11/2015:svnAcer:pnAspireES1-520:pvrV1.06:rvnAcer:rnBellemere_BE:rvrV1.06:cvnAcer:ct9:cvrChassisVersion:
  dmi.product.name: Aspire ES1-520
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Jan 19 21:37:31 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1656610] Re: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-01-20 Thread Paul White

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

** This bug has been marked a duplicate of bug 1514474
   package tex-common 6.04 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1

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

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

Status in tex-common package in Ubuntu:
  New

Bug description:
  Im not literate enough to advise further. Basically while installing
  16.04 a message appeared on screen something about Tex-common 6.04
  failed to instal. How this manifests its self i`m not quite sure but
  startup sees a DOS like screen appear with lines of text something
  either didnt load or there is a problem but eventually it starts up as
  normal.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic i686
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: i386
  Date: Sun Jan 15 14:26:34 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2012-10-14 (1553 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-01-15 (0 days ago)

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

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

[Desktop-packages] [Bug 1658149] Re: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-01-20 Thread Paul White

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

** This bug has been marked a duplicate of bug 1514474
   package tex-common 6.04 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1

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

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

Status in tex-common package in Ubuntu:
  New

Bug description:
  this is the message

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  Date: Fri Jan 20 17:17:56 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2012-11-07 (1534 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build i386 LIVE Binary 
20120426-12:41
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-01-20 (0 days ago)

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

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

[Desktop-packages] [Bug 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time

Let's wait for Mathieu's opinion.

This seems like a good candidate for 16.04.2 if we can get it fixed in
time.

** Changed in: network-manager (Ubuntu)
Milestone: None => ubuntu-16.04.2

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

Title:
  Wifi "device not ready" after booting into OS for the 1st time

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  * Steps to reproduce:
  1. Install image
  2. Boot into OS
  3. Check the wifi status in network-manager applet

  * Expected result:
  Available APs listed in network-manager applet, wifi connection can be 
established

  * Actual result:
  AP list replaced by a greyed-out "device not ready" wording
  Reboot system or do "$ sudo service network-manager restart" and wifi will 
then start working correctly.

  * OS: Xenial
  * Network-manager: 1.1.93-0ubuntu4
  * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac 
Wireless [11ab:2b38]

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

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

[Desktop-packages] [Bug 1658149] Re: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-01-20 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

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

Status in tex-common package in Ubuntu:
  New

Bug description:
  this is the message

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  Date: Fri Jan 20 17:17:56 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2012-11-07 (1534 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build i386 LIVE Binary 
20120426-12:41
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-01-20 (0 days ago)

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

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

[Desktop-packages] [Bug 1658149] [NEW] package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-01-20 Thread will

Public bug reported:

this is the message

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tex-common 6.04
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic i686
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: i386
Date: Fri Jan 20 17:17:56 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2012-11-07 (1534 days ago)
InstallationMedia: Ubuntu 12.04 "Precise" - Build i386 LIVE Binary 
20120426-12:41
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.18
SourcePackage: tex-common
Title: package tex-common 6.04 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2017-01-20 (0 days ago)

** Affects: tex-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

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

Status in tex-common package in Ubuntu:
  New

Bug description:
  this is the message

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  Date: Fri Jan 20 17:17:56 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2012-11-07 (1534 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build i386 LIVE Binary 
20120426-12:41
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-01-20 (0 days ago)

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

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

[Desktop-packages] [Bug 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time

2017-01-20 Thread Jeremy Soller

Yes, I am. I just need to know what is permissible - we can add
IgnoreOnIsolate in a ubuntu patch but it seems like the source of the
issue is in network manager - it should detect that wpa supplicant is
not running and restart it dynamically.

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

Title:
  Wifi "device not ready" after booting into OS for the 1st time

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  * Steps to reproduce:
  1. Install image
  2. Boot into OS
  3. Check the wifi status in network-manager applet

  * Expected result:
  Available APs listed in network-manager applet, wifi connection can be 
established

  * Actual result:
  AP list replaced by a greyed-out "device not ready" wording
  Reboot system or do "$ sudo service network-manager restart" and wifi will 
then start working correctly.

  * OS: Xenial
  * Network-manager: 1.1.93-0ubuntu4
  * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac 
Wireless [11ab:2b38]

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

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

[Desktop-packages] [Bug 1571640] Re: unity-greeter scaling factor changes after a delay

2017-01-20 Thread Steve McKay

** Branch linked: lp:~smmckay/unity-greeter/1571640

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

Title:
  unity-greeter scaling factor changes after a delay

Status in unity-greeter package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-greeter source package in Xenial:
  Confirmed
Status in unity-settings-daemon source package in Xenial:
  Fix Released
Status in unity-greeter source package in Yakkety:
  Fix Released
Status in unity-settings-daemon source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

   * Unity Greeter does not have the right scale at the beginning, after
  a short delay, it changes to the right scale.

  [Test Case]

   * It can be easily observed on HiDPI display, when Unity Greeter is
  starting.

  [Regression Potential]

   * If u-s-d failed to launch, Unity Greeter stuck at waiting u-s-d's
  signal and failed to proceed. But it's not likely to happen.

  

  Just after the upgrade to ubuntu 16.04, when lightdm starts the
  resolution is 2560x1600. Then, after about half a second it is
  automatically changed to 1280x800. This happens systematically at each
  boot. No external monitor is connected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  Uname: Linux 4.5.0-040500-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 18 14:39:03 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-09 (525 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-18 (0 days ago)

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

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

[Desktop-packages] [Bug 1506704] Re: Thin font, nautilus doesn't integrate with Unity.

2017-01-20 Thread Rui Neto

Seems fixed to me with the following steps:

1. Clean install ubuntu 16.04.1
2. sudo apt-get update -y
3. sudo apt-get upgrade -y
4. reboot
5. sudo apt-get dist-upgrade -y
6. reboot
7. sudo apt-get install linux-generic-hwe-16.04-edge
8. reboot

Rebooted about ten times, no error so far.

* OBS: The only font i installed is Microsoft Consolas in home/.fonts/.

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1637957] Re: Chromium not working with SAML authentication

2017-01-20 Thread Alberto Donato

Sync is now working again with SAML.

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

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

Title:
  Chromium not working with SAML authentication

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Sync login is failing with SAML authentication. See

  https://bugs.chromium.org/p/chromium/issues/detail?id=677154

  for details.

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

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

[Desktop-packages] [Bug 1657875] Re: Google Chrome flickers badly on web pages

2017-01-20 Thread Brandon MacEachern

I can now officially confirm, that simply doing as you mentioned:

sudo nano /usr/share/X11/xorg.conf.d/20-intel.conf

Section "Device"
   Identifier  "Intel Graphics"
   Driver  "intel"
   Option  "AccelMethod"  "sna"
   Option  "TearFree""true"
   Option  "DRI""3"
EndSection

Has FIXED the issue entirely.  I feel that this change should be made
permanent in 16.04 LTS to fix any Intel issues regarding sandy-bridge
GPU's or higher.

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

Title:
  Google Chrome flickers badly on web pages

Status in xorg package in Ubuntu:
  New

Bug description:
  In reference to: https://bugs.launchpad.net/ubuntu/+source/xserver-
  xorg-video-intel/+bug/1586539

  Was asked by Christopher M. Penalver (penalvch) to make this new bug
  report.

  Google chrome intermittently flickers (sometimes even Firefox I found,
  but very very rarely), and can cause a seizure in some people as it
  can flash between black and white 60 times a second.  This is a major
  issue that needs to be resolved as I'm sure many who are suffering
  this bug, feel as well.

  Please refer to the other bug report which is no "Incomplete" as it
  goes into more detail than I have time to honestly type out over
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan 19 14:42:57 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:221e]
   NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GK107GLM [Quadro K1100M] [17aa:221e]
  InstallationDate: Installed on 2016-10-10 (101 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20EFCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed 
root=UUID=df32e7f0-11aa-4e43-98d8-fcd5bbeb2c05 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET79WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20EFCTO1WW:pvrThinkPadW541:rvnLENOVO:rn20EFCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20EFCTO1WW
  dmi.product.version: ThinkPad W541
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Jan 19 10:52:11 2017
  xserver.configfile: default
  xserver.errors: open /dev/dri/card0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5571 
   vendor CMN
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Desktop-packages] [Bug 1650865] Re: libavcodec may be vunerable or is not supported, and should be updatd to play video

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

** This bug has been marked a duplicate of bug 1643467
   Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec

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

Title:
  libavcodec may be vunerable or is not supported, and should be updatd
  to play video

Status in firefox package in Ubuntu:
  New

Bug description:
  Unable to play videos in firefox browser

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 50.1.0+build2-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.13.0-105.152~precise1-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-105-generic x86_64
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-105-generic.
  ApportVersion: 2.0.1-0ubuntu17.15
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: PCH [HDA Intel PCH], device 0: ALC3234 Analog [ALC3234 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nren   2141 F pulseaudio
   /dev/snd/controlC0:  nren   2141 F pulseaudio
  BuildID: 20161209094312
  Card0.Amixer.info:
   Card hw:0 'HDMI'/'HDA Intel HDMI at 0xf7e14000 irq 62'
 Mixer name : 'Intel Haswell HDMI'
 Components : 'HDA:80862807,80860101,0010'
 Controls  : 21
 Simple ctrls  : 3
  Card1.Amixer.info:
   Card hw:1 'PCH'/'HDA Intel PCH at 0xf7e1 irq 61'
 Mixer name : 'Realtek ALC3234'
 Components : 'HDA:10ec0255,10280651,0012'
 Controls  : 26
 Simple ctrls  : 13
  Channel: Unavailable
  Date: Sun Dec 18 15:10:12 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   Global Menu Bar integration - globalm...@ubuntu.com
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
  IpRoute:
   default via 192.168.0.1 dev wlan0  proto static 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.9  metric 2
  MarkForUpload: True
  MostRecentCrashID: bp-7e23075f-55d5-40ee-9978-3ac432161108
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=50.1.0/20161209094312 (In use)
  RelatedPackageVersions:
   totem-mozilla 3.0.1-0ubuntu21.1
   adobe-flashplugin 11.2.202.261-0precise1
   rhythmbox-mozilla 2.96-0ubuntu4.3
   icedtea-6-plugin  1.2.3-0ubuntu0.12.04.4
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0KHNVP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A07
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd05/21/2015:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0KHNVP:rvrA07:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1652835] Re: [MUST FIX]package kde-config-telepathy-accounts (not installed) failed to install/upgrade: Package System Critical and Wrecked from previous issues encountered

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

** Information type changed from Public Security to Public

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

Title:
  [MUST FIX]package kde-config-telepathy-accounts (not installed) failed
  to install/upgrade: Package System Critical and Wrecked from previous
  issues encountered

Status in account-plugins package in Ubuntu:
  New
Status in ktp-accounts-kcm package in Ubuntu:
  New
Status in telepathy-accounts-signon package in Ubuntu:
  Incomplete

Bug description:
  Worse Besides this, my entire package system is broken, and I've tried
  every command in terminal to fix this. PLEASE HELP FIX THIS

  NOTE: Tried every resource to help me.
  Please set Importance to critical...Package System/System itself
  HAS BEEN BREACHED!!!

  ProblemType: ENTIRE/WHOLE Package System
  DistroRelease: Ubuntu 16.04 (With or without LTS)
  Package: kde-config-telepathy-accounts (not installed)/ Any kind of package 
avalible for installtion, including anything from the Ubuntu Software Center!
  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.2
  AptOrdering:
   kde-config-telepathy-accounts: Install
   kde-config-telepathy-accounts: Configure
   kde-telepathy-minimal: Configure
   kde-telepathy: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Dec 27 12:57:53 2016
  DpkgTerminalLog:
   Preparing to unpack 
.../kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb ...
   Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb
 (--unpack)
  DuplicateSignature:
   package:kde-config-telepathy-accounts:(not installed)
   Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb
 (--unpack):
  ErrorMessage: E: Sub-process /usr/bin/dpkg returned an error code (1)
  InstallationDate: Installed on 2016-12-08 (18 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: ktp-accounts-kcm
  Title: [MUST FIX]package kde-config-telepathy-accounts (not installed) failed 
to install/upgrade: Package System Critical and Wrecked from previous issues 
encountered
  UpgradeStatus: N/A Permanent

  Issue related to this on launchpad.net, click below...(Photo Only)
  
https://launchpadlibrarian.net/300380104/Screenshot%20from%202016-12-27%2016-38-18.png

  Link to Issue on website:
  https://bugs.launchpad.net/ubuntu/+source/scilab/+bug/1013856

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

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

[Desktop-packages] [Bug 1649428] Re: Cannot open file from https location (URL)

** Information type changed from Public Security to Public

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

Title:
  Cannot open file from https location (URL)

Status in gimp package in Ubuntu:
  New

Bug description:
  If I try, I get this GIMP message:

Opening 'https://[...]' failed:

Could not load 'https://[...]': Failed to open file 'https://[...]':
  open() failed: No such file or directory

  Most of the time, I can manually edit the URL to read http://[...] and
  I can open the document as expected.

  The bug is a security vulnerability because it forces users to use
  unsecure communication.

  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  $ apt-cache policy gimp
  gimp:
Installed: 2.8.16-1ubuntu1.1
Candidate: 2.8.16-1ubuntu1.1
Version table:
   *** 2.8.16-1ubuntu1.1 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   2.8.16-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

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

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

[Desktop-packages] [Bug 1656610] Re: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-01-20 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

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

Status in tex-common package in Ubuntu:
  New

Bug description:
  Im not literate enough to advise further. Basically while installing
  16.04 a message appeared on screen something about Tex-common 6.04
  failed to instal. How this manifests its self i`m not quite sure but
  startup sees a DOS like screen appear with lines of text something
  either didnt load or there is a problem but eventually it starts up as
  normal.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic i686
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: i386
  Date: Sun Jan 15 14:26:34 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2012-10-14 (1553 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-01-15 (0 days ago)

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

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

[Desktop-packages] [Bug 1656610] Re: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

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

** Information type changed from Private Security to Public

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

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

Status in tex-common package in Ubuntu:
  New

Bug description:
  Im not literate enough to advise further. Basically while installing
  16.04 a message appeared on screen something about Tex-common 6.04
  failed to instal. How this manifests its self i`m not quite sure but
  startup sees a DOS like screen appear with lines of text something
  either didnt load or there is a problem but eventually it starts up as
  normal.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic i686
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: i386
  Date: Sun Jan 15 14:26:34 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2012-10-14 (1553 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-01-15 (0 days ago)

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

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

[Desktop-packages] [Bug 1658112] Re: System wide proxy settings are not seen by users who didn't first initiated the proxy config

2017-01-20 Thread Eric Desrochers

** Description changed:

  System wide proxy settings are not seen by users who didn't first
  initiated the proxy configuration.
  
  If the initial configuration has been made by "user1", only this user
  will show the configuration in network applet, the other users won't see
  anything.
  
  Reproducer ;
  1. Set proxy with UI on user1 (without protocol in front of it (e.g. http://, 
https://,)
  Method  : Manual
  HTTP Proxy  : test.com Port : 8080
  HTTPS Proxy : test.com Port : 9090
  
  Click "Apply system wide"
  
  2. Create user user2
  3. Logout user1
  4. Login as user2
  5. Look configuration:
  
- - Network applet won't change, remaining set to 'none' 
+ - Network applet won't change, remaining set to 'none'
  - "gsettings get org.gnome.system.proxy mode" return 'none' instead of 
'manual'
  - "dconf read /system/proxy/mode" return nothing.
  
  The only test I found to validate was the following:
  
  - Check proxy variables :
  $ echo $http_proxy
  $ echo $https_proxy
  $ echo $ftp_proxy
  
- * You should see the value set while log as user1
+ * You should see the value created by user1.
  
  - Try web browser and validate it goes through the proxy

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

Title:
  System wide proxy settings are not seen by users who didn't first
  initiated the proxy config

Status in unity-control-center package in Ubuntu:
  New

Bug description:
  System wide proxy settings are not seen by users who didn't first
  initiated the proxy configuration.

  If the initial configuration has been made by "user1", only this user
  will show the configuration in network applet, the other users won't
  see anything.

  Reproducer ;
  1. Set proxy with UI on user1 (without protocol in front of it (e.g. http://, 
https://,)
  Method  : Manual
  HTTP Proxy  : test.com Port : 8080
  HTTPS Proxy : test.com Port : 9090

  Click "Apply system wide"

  2. Create user user2
  3. Logout user1
  4. Login as user2
  5. Look configuration:

  - Network applet won't change, remaining set to 'none'
  - "gsettings get org.gnome.system.proxy mode" return 'none' instead of 
'manual'
  - "dconf read /system/proxy/mode" return nothing.

  The only test I found to validate was the following:

  - Check proxy variables :
  $ echo $http_proxy
  $ echo $https_proxy
  $ echo $ftp_proxy

  * You should see the value created by user1.

  - Try web browser and validate it goes through the proxy

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

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

[Desktop-packages] [Bug 1658118] [NEW] Network applet should warn or generate a warning/error if user tries to add protocol in front of the proxy value

2017-01-20 Thread Eric Desrochers

Public bug reported:

Reproducer ;

1. Set proxy with UI on user1
Method : Manual
HTTP Proxy : http://test.com Port : 8080
HTTPS Proxy : https://test.com Port : 9090

Click "Apply system wide"

No warning/error will be shown, but if looking at :
- /etc/environment
- /etc/apt/apt.conf

They won't be updated/created.

The reason is because the protocol is automatically added during the
saving process so that the configuration should look as follow :
(without the protocol http://, https://)

Method : Manual
HTTP Proxy : test.com Port : 8080
HTTPS Proxy : test.com Port : 9090

In order to improve the user experience, it would be great to have a
mechanism that detect if the protocol has been accidentally added to the
field, or at least a quick message in the applet window to let the user
know to not add the protocol.

** Affects: unity-control-center (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Network applet should warn or generate a warning/error if user tries
  to add protocol in front of the proxy value

Status in unity-control-center package in Ubuntu:
  New

Bug description:
  Reproducer ;

  1. Set proxy with UI on user1
  Method : Manual
  HTTP Proxy : http://test.com Port : 8080
  HTTPS Proxy : https://test.com Port : 9090

  Click "Apply system wide"

  No warning/error will be shown, but if looking at :
  - /etc/environment
  - /etc/apt/apt.conf

  They won't be updated/created.

  The reason is because the protocol is automatically added during the
  saving process so that the configuration should look as follow :
  (without the protocol http://, https://)

  Method : Manual
  HTTP Proxy : test.com Port : 8080
  HTTPS Proxy : test.com Port : 9090

  In order to improve the user experience, it would be great to have a
  mechanism that detect if the protocol has been accidentally added to
  the field, or at least a quick message in the applet window to let the
  user know to not add the protocol.

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

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

[Desktop-packages] [Bug 1656694] Re: package autoconf2.13 2.13-67 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2017-01-20 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package autoconf2.13 2.13-67 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 2

Status in autoconf2.13 package in Ubuntu:
  New

Bug description:
  i can not upgrade ubuntu 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: autoconf2.13 2.13-67
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  AptOrdering:
   intel-microcode: Remove
   autoconf2.13: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Jan 15 20:56:56 2017
  DpkgHistoryLog:
   Start-Date: 2017-01-15  20:56:23
   Commandline: aptdaemon role='role-commit-packages' sender=':1.207'
   Remove: intel-microcode:amd64 (3.20151106.1)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2015-02-19 (695 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: autoconf2.13
  Title: package autoconf2.13 2.13-67 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 2
  UpgradeStatus: Upgraded to xenial on 2016-10-12 (95 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autoconf2.13/+bug/1656694/+subscriptions

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

[Desktop-packages] [Bug 1657177] Re: Screen not locked when coming out of suspend/hibernate. Requests password later, but can be bypassed.

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

** Information type changed from Private Security to Public

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

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

Title:
  Screen not locked when coming out of suspend/hibernate. Requests
  password later, but can be bypassed.

Status in gnome-screensaver package in Ubuntu:
  Invalid

Bug description:
  I had system passworded. I removed the password to do some long work.
  I reinstated the password.
  System does not require password on reboot or coming out of suspend/hibernate.
  When it does request the password, I can bypass the request.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-screensaver 3.6.1-7ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 17 11:07:36 2017
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 300
  InstallationDate: Installed on 2013-12-27 (1117 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen not locked when coming out of suspend/hibernate
  UpgradeStatus: Upgraded to xenial on 2016-08-02 (167 days ago)

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

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

[Desktop-packages] [Bug 1656694] Re: package autoconf2.13 2.13-67 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

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

** Information type changed from Private Security to Public

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

Title:
  package autoconf2.13 2.13-67 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 2

Status in autoconf2.13 package in Ubuntu:
  New

Bug description:
  i can not upgrade ubuntu 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: autoconf2.13 2.13-67
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  AptOrdering:
   intel-microcode: Remove
   autoconf2.13: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Jan 15 20:56:56 2017
  DpkgHistoryLog:
   Start-Date: 2017-01-15  20:56:23
   Commandline: aptdaemon role='role-commit-packages' sender=':1.207'
   Remove: intel-microcode:amd64 (3.20151106.1)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2015-02-19 (695 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: autoconf2.13
  Title: package autoconf2.13 2.13-67 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 2
  UpgradeStatus: Upgraded to xenial on 2016-10-12 (95 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autoconf2.13/+bug/1656694/+subscriptions

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

[Desktop-packages] [Bug 1658112] [NEW] System wide proxy settings are not seen by users who didn't first initiated the proxy config

2017-01-20 Thread Eric Desrochers

Public bug reported:

System wide proxy settings are not seen by users who didn't first
initiated the proxy configuration.

If the initial configuration has been made by "user1", only this user
will show the configuration in network applet, the other users won't see
anything.

Reproducer ;
1. Set proxy with UI on user1 (without protocol in front of it (e.g. http://, 
https://,)
Method  : Manual
HTTP Proxy  : test.com Port : 8080
HTTPS Proxy : test.com Port : 9090

Click "Apply system wide"

2. Create user user2
3. Logout user1
4. Login as user2
5. Look configuration:

- Network applet won't change, remaining set to 'none' 
- "gsettings get org.gnome.system.proxy mode" return 'none' instead of 'manual'
- "dconf read /system/proxy/mode" return nothing.

The only test I found to validate was the following:

- Check proxy variables :
$ echo $http_proxy
$ echo $https_proxy
$ echo $ftp_proxy

* You should see the value set while log as user1

- Try web browser and validate it goes through the proxy

** Affects: unity-control-center (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  System wide proxy settings are not seen by users who didn't first
  initiated the proxy config

Status in unity-control-center package in Ubuntu:
  New

Bug description:
  System wide proxy settings are not seen by users who didn't first
  initiated the proxy configuration.

  If the initial configuration has been made by "user1", only this user
  will show the configuration in network applet, the other users won't
  see anything.

  Reproducer ;
  1. Set proxy with UI on user1 (without protocol in front of it (e.g. http://, 
https://,)
  Method  : Manual
  HTTP Proxy  : test.com Port : 8080
  HTTPS Proxy : test.com Port : 9090

  Click "Apply system wide"

  2. Create user user2
  3. Logout user1
  4. Login as user2
  5. Look configuration:

  - Network applet won't change, remaining set to 'none' 
  - "gsettings get org.gnome.system.proxy mode" return 'none' instead of 
'manual'
  - "dconf read /system/proxy/mode" return nothing.

  The only test I found to validate was the following:

  - Check proxy variables :
  $ echo $http_proxy
  $ echo $https_proxy
  $ echo $ftp_proxy

  * You should see the value set while log as user1

  - Try web browser and validate it goes through the proxy

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

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

[Desktop-packages] [Bug 1657882] Re: wine

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

** Information type changed from Private Security to Public

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

Title:
  wine

Status in xorg package in Ubuntu:
  New

Bug description:
  cant install wine

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Jan 19 21:39:58 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8330] [1002:9832] 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Kabini [Radeon HD 8330] [1025:104b]
  InstallationDate: Installed on 2016-12-01 (49 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Acer Aspire ES1-520
  ProcEnviron:
   LANGUAGE=hr
   PATH=(custom, no user)
   LANG=hr_HR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed 
root=UUID=073388fc-a929-4eae-81b3-5f775ced2d93 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Bellemere_BE
  dmi.board.vendor: Acer
  dmi.board.version: V1.06
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd08/11/2015:svnAcer:pnAspireES1-520:pvrV1.06:rvnAcer:rnBellemere_BE:rvrV1.06:cvnAcer:ct9:cvrChassisVersion:
  dmi.product.name: Aspire ES1-520
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Jan 19 21:37:31 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1658102] [NEW] going full screen locks out all other apps and system

2017-01-20 Thread ssameer ssierra

Public bug reported:

full screen on almost any app(that allows full screen) causes the entire
rest of the system to be locked out, cannot kill or force quit or alt
tab to anything else, must use kill xserver command ctrl alt backspace.

after relogging in, the same action, fullscreen on same app can be
toggled many times and works normally, but will eventually happen again.
even though i've experienced this over several releases and it's
happened many times, i can't see any pattern or cause for what will make
this happen.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Jan 20 08:46:53 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.24, 4.4.0-57-generic, x86_64: installed
 virtualbox, 5.0.24, 4.4.0-59-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:191e] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo Skylake Integrated Graphics [17aa:380e]
InstallationDate: Installed on 2016-10-30 (82 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: LENOVO 80QE
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed 
root=UUID=2bcfd691-709a-43ea-888c-049a926760ab ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/21/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: DDCN20WW(V1.04)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Lenovo YOGA 700-
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo YOGA 700-11ISK
dmi.modalias: 
dmi:bvnLENOVO:bvrDDCN20WW(V1.04):bd09/21/2015:svnLENOVO:pn80QE:pvrLenovoYOGA700-11ISK:rvnLENOVO:rnLenovoYOGA700-:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA700-11ISK:
dmi.product.name: 80QE
dmi.product.version: Lenovo YOGA 700-11ISK
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.74+git1701191830.9e4c68~gd~x
version.libgl1-mesa-dri: libgl1-mesa-dri 17.1~git1701200730.414888~gd~x
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.1~git1701200730.414888~gd~x
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.8.99+git1701071933.ea30d8~gd~x
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1701040733.028c94~gd~x
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.13+git1610280732.1516d3~gd~x
xserver.bootTime: Fri Jan 20 07:40:58 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   20573 
 vendor AUO
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial

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

Title:
  going full screen locks out all other apps and system

Status in xorg package in Ubuntu:
  New

Bug description:
  full screen on almost any app(that allows full screen) causes the
  entire rest of the system to be locked out, cannot kill or force quit
  or alt tab to anything else, must use kill xserver command ctrl alt
  backspace.

  after relogging in, the same action, fullscreen on same app can be
  toggled many times and works normally, but will eventually happen
  again. even though i've experienced this over several releases and
  it's happened many times, i can't see any pattern or cause for what
  will make this happen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist:

[Desktop-packages] [Bug 1657385] Re: libxcomposite-dev is not Multi-Arch compatible

This bug was fixed in the package libxcomposite - 1:0.4.4-2

---
libxcomposite (1:0.4.4-2) unstable; urgency=low

  [ Julien Cristau ]
  * Mark libxcomposite-dev as Multi-Arch: same (closes: #689082).  Hopefully
the docbook-generated manpage won't be too unpredictable. (LP: #1657385)

 -- Timo Aaltonen   Fri, 20 Jan 2017 07:36:39 +0200

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

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

Title:
  libxcomposite-dev is not Multi-Arch compatible

Status in libxcomposite package in Ubuntu:
  Fix Released

Bug description:
  This is an old bug since 2012, upstream bug report:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689082

  Tested on Xenial, when trying to install libxcomposite-dev:i386, the
  64bit version will be removed:

  $ sudo apt-get install libxcomposite-dev:i386
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
libxcomposite1:i386
  The following packages will be REMOVED:
libxcomposite-dev
  The following NEW packages will be installed:
libxcomposite-dev:i386 libxcomposite1:i386
  0 upgraded, 2 newly installed, 1 to remove and 0 not upgraded.
  Need to get 17.5 kB of archives.
  After this operation, 46.1 kB of additional disk space will be used.
  Do you want to continue? [Y/n]

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

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

[Desktop-packages] [Bug 1573959] Re: On-screen text disappears after suspend

2017-01-20 Thread Alvaro Uría

This happens to me on 14.04 using linux-generic-lts-xenial.

$ lspci -nn | egrep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core 
Processor Integrated Graphics Controller [8086:0416] (rev 06)

$ uname -a
Linux hostname 4.4.0-59-generic #80~14.04.1-Ubuntu SMP Fri Jan 6 18:02:02 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

Issue is not consistent, every time I suspend and resume, but happens
every week. Logging out from X session and back in solves the issue.

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

Title:
  On-screen text disappears after suspend

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

Bug description:
  After resuming from a suspend, almost all text on screen is not
  visible.  This includes menu items, text in all three boxes (list of
  folders, list of e-mails, e-mail body) in Thunderbird (with the
  curious exception of "ffl" in the File menu), top menu in Chromium
  (but not the menu obtained by pressing the hamburger button), and the
  menus produced by clicking items in the system tray.  Also, the apport
  dialog had no text except for a few capital letters.

  ADDITIONAL INFORMATION:
  * initctl restart unity-panel-service restarts the panel, but the text is 
still missing
  * suspend and resume does not fix the issue
  * Logging out fixes the issue
  * Other affected applications:
  ** Chromium file select dialog
  ** Terminal (entire window)
  ** ttys 1-6 (Ctrl+Alt+F1, etc.)
  ** Document viewer (menus)
  ** Software Updater
  ** Rhythmbox
  ** The dialog that appears when you take a screenshot with Ctrl+Alt+PrtSc
  ** ubuntu-bug
  ** Nautilus
  ** LibreOffice Calc (spreadsheet text contents)
  ** Firefox
  * Unity dash is not affected.
  * Skype is not affected.
  * Mousing over a button in a dialog correctly shows the text.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog:

  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,gnomecompat,imgpng,place,move,resize,vpswitch,snap,regex,grid,mousepoll,unitymtgrabhandles,animation,session,wall,workarounds,expo,fade,ezoom,scale,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Apr 23 12:04:57 2016
  DistUpgraded: 2016-04-22 09:22:44,147 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: COMPAL Electronics Inc Haswell-ULT Integrated Graphics 
Controller [14c0:0075]
  InstallationDate: Installed on 2015-01-21 (457 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Compal VAW70
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=8f4bd759-42d2-4828-8470-2aaf6fcb75ff ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.01T01
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Compal
  dmi.board.version: V1.01T01
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.01T01:bd07/31/2013:svnCompal:pnVAW70:pvrV1.01T01:rvnCompal:rnType2-BoardProductName1:rvrV1.01T01:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: VAW70
  dmi.product.version: V1.01T01
  dmi.sys.vendor: Compal
  upstart.unity-panel-service-lockscreen.log:
   (unity-panel-service:14416): GLib-CRITICAL **: Source ID 4294967295 was not 
found when attempting to remove it

   (unity-panel-service:26413): 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.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

[Desktop-packages] [Bug 1379480] Re: xwdtopnm generates bad pnm files

2017-01-20 Thread linuxball

Just for completeness I tested xwdtopnm of netpbm (2:10.0-15ubuntu2) in
Ubuntu 14.04.5 LTS and I confirm that it suffers from this bug, too.

** Tags added: trusty

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

Title:
  xwdtopnm generates bad pnm files

Status in netpbm-free package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to capture the screen to a png file, with the following
  command:

  xwd -root -display :0 | xwdtopnm | pnmtopng > file.png

  The output file is a valid png file, but it's a garbled picture.

  By doing the following diagnostic steps, xwdtopnm was determined to be
  the problem:

  xwd -root -display :0 > test.xwd ; gimp test.xwd   ===> picture looks good
  xwdtopnm < test.xwd > test.pnm  ; gimp test.pnm ===> gimp reports "PNM Image 
Message: Unsupported maximum value."
  pnmtopng < test.pnm > test.png ; gimp test.png ===> gimp loads a garbled 
picture

  file test.xwd  ===> file.xwd: XWD X Window Dump image data, "xwdump",
  3840x1080x24

  pnmtoxwd < test.pnm > test2.xwd ; gimp test2.xwd  ===> gimp loads a
  garbled picture

  Hopefully you can fix the glitch in xwdtopnm easily!

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: netpbm 2:10.0-15
  ProcVersionSignature: Ubuntu 3.8.0-44.66~precise1-generic 3.8.13.25
  Uname: Linux 3.8.0-44-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.7
  Architecture: amd64
  Date: Thu Oct  9 11:51:37 2014
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   SHELL=/bin/bash
  SourcePackage: netpbm-free
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netpbm-free/+bug/1379480/+subscriptions

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

[Desktop-packages] [Bug 1573959] Re: On-screen text disappears after suspend

2017-01-20 Thread Volkan Yazıcı

Count me in too:

$ lspci -nn | grep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT 
Integrated Graphics Controller [8086:0a2e] (rev 09)

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

Title:
  On-screen text disappears after suspend

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

Bug description:
  After resuming from a suspend, almost all text on screen is not
  visible.  This includes menu items, text in all three boxes (list of
  folders, list of e-mails, e-mail body) in Thunderbird (with the
  curious exception of "ffl" in the File menu), top menu in Chromium
  (but not the menu obtained by pressing the hamburger button), and the
  menus produced by clicking items in the system tray.  Also, the apport
  dialog had no text except for a few capital letters.

  ADDITIONAL INFORMATION:
  * initctl restart unity-panel-service restarts the panel, but the text is 
still missing
  * suspend and resume does not fix the issue
  * Logging out fixes the issue
  * Other affected applications:
  ** Chromium file select dialog
  ** Terminal (entire window)
  ** ttys 1-6 (Ctrl+Alt+F1, etc.)
  ** Document viewer (menus)
  ** Software Updater
  ** Rhythmbox
  ** The dialog that appears when you take a screenshot with Ctrl+Alt+PrtSc
  ** ubuntu-bug
  ** Nautilus
  ** LibreOffice Calc (spreadsheet text contents)
  ** Firefox
  * Unity dash is not affected.
  * Skype is not affected.
  * Mousing over a button in a dialog correctly shows the text.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog:

  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,gnomecompat,imgpng,place,move,resize,vpswitch,snap,regex,grid,mousepoll,unitymtgrabhandles,animation,session,wall,workarounds,expo,fade,ezoom,scale,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Apr 23 12:04:57 2016
  DistUpgraded: 2016-04-22 09:22:44,147 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: COMPAL Electronics Inc Haswell-ULT Integrated Graphics 
Controller [14c0:0075]
  InstallationDate: Installed on 2015-01-21 (457 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Compal VAW70
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=8f4bd759-42d2-4828-8470-2aaf6fcb75ff ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.01T01
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Compal
  dmi.board.version: V1.01T01
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.01T01:bd07/31/2013:svnCompal:pnVAW70:pvrV1.01T01:rvnCompal:rnType2-BoardProductName1:rvrV1.01T01:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: VAW70
  dmi.product.version: V1.01T01
  dmi.sys.vendor: Compal
  upstart.unity-panel-service-lockscreen.log:
   (unity-panel-service:14416): GLib-CRITICAL **: Source ID 4294967295 was not 
found when attempting to remove it

   (unity-panel-service:26413): 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.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 Apr 22 09:26:06 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1479
   vendor

[Desktop-packages] [Bug 1622166] Re: network manager cannot unlock the USB 3G modem

2017-01-20 Thread Krzysztof Kaczmarski

I tried to unlock the modem with mmcli and it looks like partially
worked.

mmcli -m  
returned:
'successfully connected the modem'
and the modem led blinking indicates 3G connection.
However, in the settings menu I can still see "Mobile Broadband Off" and no 
Internet works.

When I try to choose "Mobile Broadband Connect" (assuming that the modem
is now unlocked) I get nothing. I also get nothing now when I choose
"Mobile Broadband Settings"

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

Title:
  network manager cannot unlock the USB 3G modem

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

Bug description:
  After inserting USB 3G modem it is visible in the system:
  :~$ nmcli d 
  DEVICE   TYPE  STATECONNECTION 
  wlp3s0   wifi  connectedcoelinet4  
  enp0s25  ethernet  unavailable  -- 
  ttyHS1   gsm   unavailable  -- 
  lo   loopback  unmanaged-- 
   
  however no connection can be created. A short glimpse at /var/log/syslog 
  shows that the model is locked and sim pin is required.
  There are no dialogs open to enable the user to supply the pin.

  In the Broadband connection wizard there is no place to enter the pin and
  the connection creation fails. 

  Sep 10 15:27:07 octan kernel: [14235.719861] usb 2-1.2: new high-speed USB 
device number 11 using ehci-pci
  Sep 10 15:27:07 octan kernel: [14235.813800] usb 2-1.2: New USB device found, 
idVendor=0af0, idProduct=d055
  Sep 10 15:27:07 octan kernel: [14235.813810] usb 2-1.2: New USB device 
strings: Mfr=1, Product=2, SerialNumber=4
  Sep 10 15:27:07 octan kernel: [14235.813815] usb 2-1.2: Product: Globetrotter 
GI0505
  Sep 10 15:27:07 octan kernel: [14235.813819] usb 2-1.2: Manufacturer: Option 
Wireless Technology
  Sep 10 15:27:07 octan kernel: [14235.813823] usb 2-1.2: SerialNumber: Serial 
Number
  Sep 10 15:27:07 octan kernel: [14235.814865] hso 2-1.2:1.0: Not our interface
  Sep 10 15:27:07 octan kernel: [14235.814920] usb-storage 2-1.2:1.0: USB Mass 
Storage device detected
  Sep 10 15:27:07 octan kernel: [14235.818500] scsi host10: usb-storage 
2-1.2:1.0
  Sep 10 15:27:07 octan mtp-probe: checking bus 2, device 11: 
"/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.2"
  Sep 10 15:27:07 octan mtp-probe: bus: 2, device: 11 was not an MTP device
  Sep 10 15:27:07 octan systemd[1]: Starting USB_ModeSwitch_2-1.2...
  Sep 10 15:27:07 octan usb_modeswitch_dispatcher[11330]: Could not read 
attribute: No such file or directory
  Sep 10 15:27:08 octan kernel: [14236.817351] scsi 10:0:0:0: CD-ROM
ZCOption Icon CD  1.00 PQ: 0 ANSI: 4
  Sep 10 15:27:08 octan kernel: [14236.822002] sr 10:0:0:0: [sr1] scsi-1 drive
  Sep 10 15:27:08 octan kernel: [14236.824235] sr 10:0:0:0: Attached scsi 
CD-ROM sr1
  Sep 10 15:27:08 octan kernel: [14236.825367] sr 10:0:0:0: Attached scsi 
generic sg2 type 5
  Sep 10 15:27:07 octan usb_modeswitch_dispatcher[11330]: message repeated 2 
times: [ Could not read attribute: No such file or directory]
  Sep 10 15:27:08 octan usb_modeswitch: switch device 0af0:d055 on 002/011
  Sep 10 15:27:08 octan kernel: [14237.144094] usb 2-1.2: USB disconnect, 
device number 11
  Sep 10 15:27:08 octan kernel: [14237.343848] usb 2-1.2: new high-speed USB 
device number 12 using ehci-pci
  Sep 10 15:27:08 octan kernel: [14237.436757] usb 2-1.2: config 1 interface 0 
altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64
  Sep 10 15:27:08 octan kernel: [14237.436769] usb 2-1.2: config 1 interface 1 
altsetting 0 bulk endpoint 0x82 has invalid maxpacket 64
  Sep 10 15:27:08 octan kernel: [14237.436775] usb 2-1.2: config 1 interface 4 
altsetting 0 bulk endpoint 0x86 has invalid maxpacket 64
  Sep 10 15:27:08 octan kernel: [14237.437500] usb 2-1.2: New USB device found, 
idVendor=0af0, idProduct=d055
  Sep 10 15:27:08 octan kernel: [14237.437510] usb 2-1.2: New USB device 
strings: Mfr=1, Product=2, SerialNumber=0
  Sep 10 15:27:08 octan kernel: [14237.437516] usb 2-1.2: Product: Globetrotter 
GI0505
  Sep 10 15:27:08 octan kernel: [14237.437520] usb 2-1.2: Manufacturer: Option 
Wireless Technology
  Sep 10 15:27:08 octan mtp-probe: checking bus 2, device 12: 
"/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.2"
  Sep 10 15:27:08 octan mtp-probe: bus: 2, device: 12 was not an MTP device
  Sep 10 15:27:08 octan systemd[1]: Starting Load/Save RF Kill Switch Status...
  Sep 10 15:27:08 octan NetworkManager[2531]:   [1473514028.9534] 
rfkill6: found WWAN radio killswitch (at 
/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/rfkill/rfkill6) (driver usb)
  Sep 10 15:27:08 octan systemd[1]: Started Load/Save RF Kill Switch Status.
  Sep 10 15:27:08 octan ModemManager[2486]:   (ttyHS2): port attributes 
not fully set
  Sep 10 15:27:08 octan ModemManager[2486]:   (ttyHS3): port attributes 
not fully set
  Sep 10

[Desktop-packages] [Bug 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time

2017-01-20 Thread Sebastien Bacher

The call was added by Mathieu in bin/oem-config-firstboot when he added
systemd support, subscribing him to the bug

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

Title:
  Wifi "device not ready" after booting into OS for the 1st time

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  * Steps to reproduce:
  1. Install image
  2. Boot into OS
  3. Check the wifi status in network-manager applet

  * Expected result:
  Available APs listed in network-manager applet, wifi connection can be 
established

  * Actual result:
  AP list replaced by a greyed-out "device not ready" wording
  Reboot system or do "$ sudo service network-manager restart" and wifi will 
then start working correctly.

  * OS: Xenial
  * Network-manager: 1.1.93-0ubuntu4
  * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac 
Wireless [11ab:2b38]

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

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

[Desktop-packages] [Bug 1379480] Re: xwdtopnm generates bad pnm files

2017-01-20 Thread linuxball

** Tags added: xenial

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

Title:
  xwdtopnm generates bad pnm files

Status in netpbm-free package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to capture the screen to a png file, with the following
  command:

  xwd -root -display :0 | xwdtopnm | pnmtopng > file.png

  The output file is a valid png file, but it's a garbled picture.

  By doing the following diagnostic steps, xwdtopnm was determined to be
  the problem:

  xwd -root -display :0 > test.xwd ; gimp test.xwd   ===> picture looks good
  xwdtopnm < test.xwd > test.pnm  ; gimp test.pnm ===> gimp reports "PNM Image 
Message: Unsupported maximum value."
  pnmtopng < test.pnm > test.png ; gimp test.png ===> gimp loads a garbled 
picture

  file test.xwd  ===> file.xwd: XWD X Window Dump image data, "xwdump",
  3840x1080x24

  pnmtoxwd < test.pnm > test2.xwd ; gimp test2.xwd  ===> gimp loads a
  garbled picture

  Hopefully you can fix the glitch in xwdtopnm easily!

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: netpbm 2:10.0-15
  ProcVersionSignature: Ubuntu 3.8.0-44.66~precise1-generic 3.8.13.25
  Uname: Linux 3.8.0-44-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.7
  Architecture: amd64
  Date: Thu Oct  9 11:51:37 2014
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   SHELL=/bin/bash
  SourcePackage: netpbm-free
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netpbm-free/+bug/1379480/+subscriptions

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

[Desktop-packages] [Bug 1658038] Re: edit/copy selected object results in "no layers found" warning leaving clipboard empty

2017-01-20 Thread Darko Veberic

hint: the example file was created by a pdf import...

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

Title:
  edit/copy selected object results in "no layers found" warning leaving
  clipboard empty

Status in inkscape package in Ubuntu:
  New

Bug description:
  selecting the "y/m" object in the attached svg file and then trying to
  copy it to the clipboard with ctrl-c or edit|copy results in a dialog
  popping up with message "no layers found". the clipboard stays empty.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: inkscape 0.91-11 [modified: usr/share/inkscape/markers/markers.svg 
usr/share/inkscape/patterns/patterns.svg]
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jan 20 11:07:57 2017
  InstallationDate: Installed on 2014-10-21 (821 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: inkscape
  UpgradeStatus: Upgraded to yakkety on 2016-10-20 (91 days ago)

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

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

[Desktop-packages] [Bug 1658038] Re: edit/copy selected object results in "no layers found" warning leaving clipboard empty

2017-01-20 Thread Darko Veberic

this is a screenshot of the popup. manipulating the file further, the
process usually leads to inkscape crash...

** Attachment added: "screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1658038/+attachment/4806694/+files/Screenshot_2017-01-20_11-09-41.png

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

Title:
  edit/copy selected object results in "no layers found" warning leaving
  clipboard empty

Status in inkscape package in Ubuntu:
  New

Bug description:
  selecting the "y/m" object in the attached svg file and then trying to
  copy it to the clipboard with ctrl-c or edit|copy results in a dialog
  popping up with message "no layers found". the clipboard stays empty.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: inkscape 0.91-11 [modified: usr/share/inkscape/markers/markers.svg 
usr/share/inkscape/patterns/patterns.svg]
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jan 20 11:07:57 2017
  InstallationDate: Installed on 2014-10-21 (821 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: inkscape
  UpgradeStatus: Upgraded to yakkety on 2016-10-20 (91 days ago)

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

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

[Desktop-packages] [Bug 1658038] [NEW] edit/copy selected object results in "no layers found" warning leaving clipboard empty

2017-01-20 Thread Darko Veberic

Public bug reported:

selecting the "y/m" object in the attached svg file and then trying to
copy it to the clipboard with ctrl-c or edit|copy results in a dialog
popping up with message "no layers found". the clipboard stays empty.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: inkscape 0.91-11 [modified: usr/share/inkscape/markers/markers.svg 
usr/share/inkscape/patterns/patterns.svg]
ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
Uname: Linux 4.8.0-34-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Jan 20 11:07:57 2017
InstallationDate: Installed on 2014-10-21 (821 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
SourcePackage: inkscape
UpgradeStatus: Upgraded to yakkety on 2016-10-20 (91 days ago)

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


** Tags: amd64 apport-bug yakkety

** Attachment added: "file with example object"
   https://bugs.launchpad.net/bugs/1658038/+attachment/4806690/+files/0.svg

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

Title:
  edit/copy selected object results in "no layers found" warning leaving
  clipboard empty

Status in inkscape package in Ubuntu:
  New

Bug description:
  selecting the "y/m" object in the attached svg file and then trying to
  copy it to the clipboard with ctrl-c or edit|copy results in a dialog
  popping up with message "no layers found". the clipboard stays empty.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: inkscape 0.91-11 [modified: usr/share/inkscape/markers/markers.svg 
usr/share/inkscape/patterns/patterns.svg]
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jan 20 11:07:57 2017
  InstallationDate: Installed on 2014-10-21 (821 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: inkscape
  UpgradeStatus: Upgraded to yakkety on 2016-10-20 (91 days ago)

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

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

[Desktop-packages] [Bug 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time

 rbasak: I guess what you said -- find out who added that isolate c
all there

Let's set this to Triaged, as Jeremy appears to have pinned down the
cause so it's solely in the realm of "developers" now. The affected
package may need to change as we figure out where it should go.

Jeremy: are you continuing to drive this bug?

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

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

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

Title:
  Wifi "device not ready" after booting into OS for the 1st time

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  * Steps to reproduce:
  1. Install image
  2. Boot into OS
  3. Check the wifi status in network-manager applet

  * Expected result:
  Available APs listed in network-manager applet, wifi connection can be 
established

  * Actual result:
  AP list replaced by a greyed-out "device not ready" wording
  Reboot system or do "$ sudo service network-manager restart" and wifi will 
then start working correctly.

  * OS: Xenial
  * Network-manager: 1.1.93-0ubuntu4
  * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac 
Wireless [11ab:2b38]

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

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

[Desktop-packages] [Bug 1619354] Re: [SRU] network-manager-applet

2017-01-20 Thread Aron Xu

@Brian, I wonder why only  the upload to yakkety is accepted from queue,
but not the xenial upload (still in "Unapproved")?

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

Title:
  [SRU] network-manager-applet

Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Xenial:
  In Progress
Status in network-manager-applet source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

  Several defects in network-manager-applet can lead to crashes under
  certain circumstance as tracked in errors.ubuntu.com, upstream stable
  bug fix release 1.2.6 should fix a big portion of the bugs while no
  feature is being added or changed.

  [Test Case]

  After upgrading to 1.2.6, crash cases should be lesser than previous,
  and no functional regression should be observed.

  [Regression Potential]

  Potential of causing regression is minimal as upstream fixes aren't
  significant in this small package during the stable branch
  maintenance.

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

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

[Desktop-packages] [Bug 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time

I suggest talking to the person who wrote the "systemctl isolate ..."
line in the first place. Did that line come from Debian?

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

Title:
  Wifi "device not ready" after booting into OS for the 1st time

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  * Steps to reproduce:
  1. Install image
  2. Boot into OS
  3. Check the wifi status in network-manager applet

  * Expected result:
  Available APs listed in network-manager applet, wifi connection can be 
established

  * Actual result:
  AP list replaced by a greyed-out "device not ready" wording
  Reboot system or do "$ sudo service network-manager restart" and wifi will 
then start working correctly.

  * OS: Xenial
  * Network-manager: 1.1.93-0ubuntu4
  * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac 
Wireless [11ab:2b38]

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

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

[Desktop-packages] [Bug 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time

 rbasak: hmm, jackpot51 isn't here, but "isolate" is pretty much de
fined as "stop everything which is not part of the given target"

 so this sounds like a case of YAFIYGI to me -- isolate isn't somet
hing which users should ever want to actually use...

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

Title:
  Wifi "device not ready" after booting into OS for the 1st time

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  * Steps to reproduce:
  1. Install image
  2. Boot into OS
  3. Check the wifi status in network-manager applet

  * Expected result:
  Available APs listed in network-manager applet, wifi connection can be 
established

  * Actual result:
  AP list replaced by a greyed-out "device not ready" wording
  Reboot system or do "$ sudo service network-manager restart" and wifi will 
then start working correctly.

  * OS: Xenial
  * Network-manager: 1.1.93-0ubuntu4
  * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac 
Wireless [11ab:2b38]

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

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

[Desktop-packages] [Bug 1657677] Re: [SRU]fix versioned Breaks/Replaces

2017-01-20 Thread Sebastien Bacher

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

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

Title:
  [SRU]fix versioned Breaks/Replaces

Status in opencc package in Ubuntu:
  Invalid
Status in opencc source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

  Previous SRU of opencc to yakkety introduced a bug that the versioned
  Breaks/Replaces requires a higher version (1.0.4-3, the debian one)
  than the update version (1.0.4-1ubuntu0.16.10.1), this prevents
  libopencc-dev from being installed to satisfy build dependencies.

  [Test Case]
  Installing libopencc-dev using apt-get, the dependency should be satisfied 
without problem.

  [Regression Potential]

  Changing the dependency version should be safe.

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

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

[Desktop-packages] [Bug 1657677] Re: [SRU]fix versioned Breaks/Replaces

2017-01-20 Thread FanJun Kong - ( BH1SCW )

I tested in yakkety, it works well. thanks

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

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

Title:
  [SRU]fix versioned Breaks/Replaces

Status in opencc package in Ubuntu:
  Invalid
Status in opencc source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

  Previous SRU of opencc to yakkety introduced a bug that the versioned
  Breaks/Replaces requires a higher version (1.0.4-3, the debian one)
  than the update version (1.0.4-1ubuntu0.16.10.1), this prevents
  libopencc-dev from being installed to satisfy build dependencies.

  [Test Case]
  Installing libopencc-dev using apt-get, the dependency should be satisfied 
without problem.

  [Regression Potential]

  Changing the dependency version should be safe.

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

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

[Desktop-packages] [Bug 792085]

2017-01-20 Thread Swamp-a

SUSE-SU-2017:0181-1: An update that solves 13 vulnerabilities and has
127 fixes is now available.

Category: security (important)
Bug References: 
1000118,1000189,1000287,1000304,1000433,1000776,1001169,1001171,1001310,1001462,1001486,1001888,1002322,1002770,1002786,1003068,1003566,1003581,1003606,1003813,1003866,1003964,1004048,1004052,1004252,1004365,1004517,1005169,1005327,1005545,1005666,1005745,1005895,1005917,1005921,1005923,1005925,1005929,1006103,1006175,1006267,1006528,1006576,1006804,1006809,1006827,1006915,1006918,1007197,1007615,1007653,1007955,1008557,1008979,1009062,1009969,1010040,1010158,1010444,1010478,1010507,1010665,1010690,1010970,1011176,1011250,1011913,1012060,1012094,1012452,1012767,1012829,1012992,1013001,1013479,1013531,1013700,1014120,1014392,1014701,1014710,1015212,1015359,1015367,1015416,799133,914939,922634,963609,963655,963904,964462,966170,966172,966186,966191,966316,966318,966325,966471,969474,969475,969476,969477,969756,971975,971989,972993,974313,974842,974843,978907,979378,979681,981825,983087,983152,983318,985850,986255,986987,987641,987703,987805,988524,988715,990384,992555,9
 
93739,993841,993891,994881,995278,997059,997639,997807,998054,998689,07,32
CVE References: 
CVE-2015-1350,CVE-2015-8964,CVE-2016-7039,CVE-2016-7042,CVE-2016-7425,CVE-2016-7913,CVE-2016-7917,CVE-2016-8645,CVE-2016-8666,CVE-2016-9083,CVE-2016-9084,CVE-2016-9793,CVE-2016-9919
Sources used:
SUSE Linux Enterprise Workstation Extension 12-SP2 (src):
kernel-default-4.4.38-93.1
SUSE Linux Enterprise Software Development Kit 12-SP2 (src):
kernel-docs-4.4.38-93.3, kernel-obs-build-4.4.38-93.1
SUSE Linux Enterprise Server for Raspberry Pi 12-SP2 (src):
kernel-default-4.4.38-93.1, kernel-source-4.4.38-93.1, kernel-syms-4.4.38-93.1
SUSE Linux Enterprise Server 12-SP2 (src):kernel-default-4.4.38-93.1, 
kernel-source-4.4.38-93.1, kernel-syms-4.4.38-93.1
SUSE Linux Enterprise Live Patching 12 (src):
kgraft-patch-SLE12-SP2_Update_4-1-2.1
SUSE Linux Enterprise High Availability 12-SP2 (src):
kernel-default-4.4.38-93.1
SUSE Linux Enterprise Desktop 12-SP2 (src):kernel-default-4.4.38-93.1, 
kernel-source-4.4.38-93.1, kernel-syms-4.4.38-93.1

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

Title:
  Automatic remount of safely removed USB 3.0 drive

Status in Nautilus:
  New
Status in thunar:
  Unknown
Status in linux package in Ubuntu:
  In Progress
Status in nautilus package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  Confirmed
Status in udev package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in Fedora:
  Unknown
Status in openSUSE:
  Fix Released

Bug description:
  Binary package hint: nautilus

  When I choose "Safely remove drive" context menu entry for an external
  USB drive within a nautilus window or directly clicking on the desktop
  icon, after about 10 seconds the drive is automatically remounted and
  a Nautilus window showing the root folder opens.

  I have noticed that similar already happened with a very old Ubuntu
  version - Bug #110589 and as that is so long time ago I thought it is
  better to open a new bug. Reason of the problem might even be
  completely different.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: nautilus 1:2.32.2.1-0ubuntu13
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
  Uname: Linux 2.6.38-8-generic-pae i686
  Architecture: i386
  Date: Thu Jun  2 23:40:08 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 792085] Re: Automatic remount of safely removed USB 3.0 drive

2017-01-20 Thread Bug Watch Updater

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-1350

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-8964

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-7913

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-7917

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-8645

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-9083

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-9084

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-9793

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-9919

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

Title:
  Automatic remount of safely removed USB 3.0 drive

Status in Nautilus:
  New
Status in thunar:
  Unknown
Status in linux package in Ubuntu:
  In Progress
Status in nautilus package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  Confirmed
Status in udev package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in Fedora:
  Unknown
Status in openSUSE:
  Fix Released

Bug description:
  Binary package hint: nautilus

  When I choose "Safely remove drive" context menu entry for an external
  USB drive within a nautilus window or directly clicking on the desktop
  icon, after about 10 seconds the drive is automatically remounted and
  a Nautilus window showing the root folder opens.

  I have noticed that similar already happened with a very old Ubuntu
  version - Bug #110589 and as that is so long time ago I thought it is
  better to open a new bug. Reason of the problem might even be
  completely different.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: nautilus 1:2.32.2.1-0ubuntu13
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
  Uname: Linux 2.6.38-8-generic-pae i686
  Architecture: i386
  Date: Thu Jun  2 23:40:08 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1464321] Re: No sound output through docking station headphones jack for Dell Latitude E5450

2017-01-20 Thread Michael Grivas

Still an issue with 16.10. 
Computer is Lenovo P50.

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

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

Title:
  No sound output through docking station headphones jack for Dell
  Latitude E5450

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  1) Release: 15.04

  2) I do not know the package or version.

  3) Expected: I expect sound to be output from the speaker that is
  connected to the headphones jack of my docking station.

  4) Actual: No sound output at all.

  I have this problem with my new computer: Dell Latitude E5450/5450
  (Late 2014) Service Tag: 4W7RQ32. I can confirm that the docking
  station and speaker both work, as I did not have this problem on my
  older Dell Latitude E5420 (Early 2011) Service Tag: 1WW25S1 running
  Ubuntu version 14.04LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thomas 1574 F pulseaudio
   /dev/snd/controlC2:  thomas 1574 F pulseaudio
   /dev/snd/controlC1:  thomas 1574 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jun 11 11:10:28 2015
  InstallationDate: Installed on 2015-06-11 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  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:  thomas 1574 F pulseaudio
   /dev/snd/controlC2:  thomas 1574 F pulseaudio
   /dev/snd/controlC1:  thomas 1574 F pulseaudio
  Symptom_Jack: Green Line Out, Rear, Docking station
  Symptom_Type: No sound at all
  Title: [Latitude E5450, Realtek ALC3235, Green Line Out, Rear, Docking 
station] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/10/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 09X6YN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd04/10/2015:svnDellInc.:pnLatitudeE5450:pvr01:rvnDellInc.:rn09X6YN:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5450
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1567149] Re: gvfsd-dnssd crashed with SIGSEGV in avahi_service_resolver_event()