date:20161206

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

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

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

Title:
  login password entry problem

Status in unity-greeter package in Ubuntu:
  Confirmed

Bug description:
  When I boot my laptop I reach the login screen of ubuntu 14.04.

  I have 3 login id's
  one of which is guest account.
  when I try to type the password in my regular login account the password 
field does not accept the entry. Then I chenge my language / keyboard settings 
in top right corner of the screen from english with rupee sign to english uk 
and back again to english with rupee sign it allows me to type the password in 
my password field. my password is all caps so i keep the caps lock on.
  i tried with caps lock on and off both but it allows only after tweaking the 
keybord settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: login 1:4.1.5.1-1ubuntu9
  ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
  Uname: Linux 3.13.0-14-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Tue Mar  4 15:30:36 2014
  InstallationDate: Installed on 2012-03-24 (709 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120324)
  SourcePackage: shadow
  UpgradeStatus: Upgraded to trusty on 2014-01-30 (33 days ago)

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

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

[Desktop-packages] [Bug 1641889] Re: The network indicator shows the wrong status

2016-12-06 Thread Kent Lin

** Changed in: oem-priority/xenial
   Importance: Undecided => High

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

Title:
  The network indicator shows the wrong status

Status in Network Manager Applet:
  Unknown
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager-applet package in Ubuntu:
  Triaged

Bug description:
  [Summary] The network indicator shows the wrong status

  [Reproduce Steps]
  1.Boot into Ubuntu OS , remove wireless connection
  Note : the issue can't be reproduced with wifi connection
  2.Enable/disable wifi function by hotkey the check wifi manager status

  [Results]
  Expected: "Enable Wi-Fi" option should be OFF
  Actual:"Enable Wi-Fi" option is ON

  [Additional Information]
  Product Name:Inspiron-7460
  BIOS Version:1.0.0

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

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

[Desktop-packages] [Bug 1627964] Re: fwupd assert failure: * Error in `/usr/lib/x86_64-linux-gnu/fwupd/fwupd': free(): invalid pointer: 0x000055f0c0f9f141 *

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

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

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

Title:
  fwupd assert failure: *** Error in `/usr/lib/x86_64-linux-
  gnu/fwupd/fwupd': free(): invalid pointer: 0x55f0c0f9f141 ***

Status in appstream-glib package in Ubuntu:
  Expired
Status in fwupd package in Ubuntu:
  Expired

Bug description:
  When I booted it gave the error.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: fwupd 0.7.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-16-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/lib/x86_64-linux-gnu/fwupd/fwupd': 
free(): invalid pointer: 0x55f0c0f9f141 ***
  Date: Sun Sep 25 20:26:14 2016
  ExecutablePath: /usr/lib/x86_64-linux-gnu/fwupd/fwupd
  InstallationDate: Installed on 2016-08-24 (33 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20160727.1)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/fwupd/fwupd
  ProcEnviron:
   
  Signal: 6
  SourcePackage: fwupd
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f1bd7f01358 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
   malloc_printerr (ar_ptr=, ptr=, 
str=0x7f1bd7efdeef "free(): invalid pointer", action=3) at malloc.c:5046
   _int_free (av=, p=, have_lock=) 
at malloc.c:3902
   __GI___libc_free (mem=) at malloc.c:2982
   ?? () from /usr/lib/x86_64-linux-gnu/libappstream-glib.so.8
  Title: fwupd assert failure: *** Error in 
`/usr/lib/x86_64-linux-gnu/fwupd/fwupd': free(): invalid pointer: 
0x55f0c0f9f141 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1627964/+subscriptions

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

[Desktop-packages] [Bug 1627964] Re: fwupd assert failure: * Error in `/usr/lib/x86_64-linux-gnu/fwupd/fwupd': free(): invalid pointer: 0x000055f0c0f9f141 *

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

** Changed in: appstream-glib (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  fwupd assert failure: *** Error in `/usr/lib/x86_64-linux-
  gnu/fwupd/fwupd': free(): invalid pointer: 0x55f0c0f9f141 ***

Status in appstream-glib package in Ubuntu:
  Expired
Status in fwupd package in Ubuntu:
  Expired

Bug description:
  When I booted it gave the error.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: fwupd 0.7.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-16-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/lib/x86_64-linux-gnu/fwupd/fwupd': 
free(): invalid pointer: 0x55f0c0f9f141 ***
  Date: Sun Sep 25 20:26:14 2016
  ExecutablePath: /usr/lib/x86_64-linux-gnu/fwupd/fwupd
  InstallationDate: Installed on 2016-08-24 (33 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20160727.1)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/fwupd/fwupd
  ProcEnviron:
   
  Signal: 6
  SourcePackage: fwupd
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f1bd7f01358 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
   malloc_printerr (ar_ptr=, ptr=, 
str=0x7f1bd7efdeef "free(): invalid pointer", action=3) at malloc.c:5046
   _int_free (av=, p=, have_lock=) 
at malloc.c:3902
   __GI___libc_free (mem=) at malloc.c:2982
   ?? () from /usr/lib/x86_64-linux-gnu/libappstream-glib.so.8
  Title: fwupd assert failure: *** Error in 
`/usr/lib/x86_64-linux-gnu/fwupd/fwupd': free(): invalid pointer: 
0x55f0c0f9f141 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1627964/+subscriptions

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

[Desktop-packages] [Bug 1647283] Re: WiFi being detected as ethernet when race condition on renaming for persistent name

2016-12-06 Thread Chih-Hsyuan Ho

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Importance: Undecided => Critical

** Also affects: oem-priority/xenial
   Importance: Undecided
   Status: New

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

Title:
  WiFi being detected as ethernet when race condition on renaming for
  persistent name

Status in HWE Next:
  New
Status in NetworkManager:
  Confirmed
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613

  Version: NetworkManager 1.4.2

  This bug happens after power-on with probability about 1/50.
  That means we need to reboot about 50 times to get into the buggy situation.
  "nmcli d" shows the device type is ethernet:

  DEVICE   TYPE  STATECONNECTION 
  wlp1s0   ethernet  unavailable  --
  lo   loopback  unmanaged-- 

  The bug starts from a race condition. But it is not the root cause.
  I've also attach 2 logs. One is in good situation. Another is in bad 
situation.
  This log is generated by applying a "log patch" to network-manager 1.4.2 so 
we can see more stuff.

  In the bad situation. The bug starts with race condition. But the race 
condition is not the root cause. The race condition is:
   * During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared.
   * Inside the NM, it is still using "wlan0" in "_linktype_get_type()".
   * Since /sys/class/net/wlan0/uevent is disappeared. so the type matching 
failed in _linktype_get_type().
   * Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 
disappeared.
   * And finally, devtype and kind are both NULL, so it returns 
NM_LINK_TYPE_ETHERNET for wlan0.

  Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit 
the type so it is still type ethernet.
  But from the log, I saw _linktype_get_type() is called several times later 
and return the correct type (wifi). But just, "nmcli d" still shows type 
ethernet.

  I'm wondering if we are missing to update the type in the Object
  created after renaming and re-detecting the type.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1647283/+subscriptions

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

[Desktop-packages] [Bug 1469483] Re: libgflags pkg-config file is missing in wily

This is fixed in 2.2.0-1 currently in Debian experimental.

https://tracker.debian.org/media/packages/g/gflags/changelog-2.2.0-1

** Changed in: gflags (Ubuntu)
   Status: New => Triaged

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

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

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

** Changed in: gflags (Ubuntu Xenial)
   Status: New => Triaged

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

Title:
  libgflags pkg-config file is missing in wily

Status in gflags package in Ubuntu:
  Triaged
Status in gflags source package in Xenial:
  Triaged

Bug description:
  The pkg-config file is no longer present. It is still available in
  vivid, though.

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

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

[Desktop-packages] [Bug 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while

2016-12-06 Thread Kasey Erickson

XPS 15 9550
Ubuntu 16.10
BIOS: 1.2.16

I have this same issue. Suspending and un-suspending works for me.

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

Title:
[XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a
while

Status in alsa-driver package in Ubuntu:
Confirmed

Bug description:
I'm experiencing a strange behavior with a headphone jack on my
laptop.

I have an external audio speaker connected to it. When I disconnect the
speaker and reconnect it again it stops working.
Even more, laptop audio stops working too. And after the reboot, I don't even
see any of the audio devices.

I've googled a lot and tried different fixes from forums with no luck.
After a while, I've accidentally discovered that putting the laptop to
the sleep mode and rebooting system after brings audio back to live.
Even more, if speakers were attached during this sleep-reboot
procedure, they are starting to work as well.

However, after the next reboot speakers are not working again. And if
I will plug them out and in - problem with completely missing audio
returns.

P.S. I'm using laptop-mode-tools package on my laptop. Recovery after
hibernation made me believe that it's somehow related. But after
uninstalling this package nothing really changed.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: kop3224 F...m pulseaudio
/dev/snd/controlC0: kop3224 F pulseaudio
CurrentDesktop: Unity
Date: Tue Apr 26 12:17:03 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-04-22 (3 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Встроенное аудио - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Left
Symptom_Type: Sound works for a while, then breaks
Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after
a while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/07/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.02.00
dmi.board.name: 0N7TVV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 15 9550
dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1643129] Re: Drop system-config-printer-gnome package

transitional package added.

https://launchpad.net/ubuntu/+source/system-config-
printer/1.5.7+20160812-0ubuntu5

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

Title:
  Drop system-config-printer-gnome package

Status in Ubuntu GNOME:
  Fix Released
Status in system-config-printer package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in xubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  I don't think the system-config-printer-gnome split makes sense any
  more and it would be nice to get this package closer in sync with
  Debian. In other words, let's drop system-config-printer-gnome and
  move most of its contents back to system-config-printer but a few
  files will end up in system-config-printer-common.

  The last explicit merge was almost a decade ago:
  https://launchpad.net/ubuntu/+source/system-config-printer/0.7.70-1ubuntu1 )

  The split was done in 2008 for KDE's benefit:
  
https://launchpad.net/ubuntu/+source/system-config-printer/0.7.78+svn1799-0ubuntu2

  - system-config-printer-kde no longer exists (it appears to have been
  part of the kdeadmin source package which was removed a few years ago)

  - Kubuntu only ships system-config-printer-udev so they aren't affected now
  
http://cdimage.ubuntu.com/cdimage/kubuntu/daily-live/current/zesty-desktop-amd64.manifest

  - Ubuntu GNOME does not need the files shipped in system-config-
  printer since GNOME has its own integrated Printers Settings panel.

  https://packages.debian.org/sid/all/system-config-printer/filelist

  In Ubuntu 16.10 I attempted to follow Debian's gnome-control-center
  packaging and depend on system-config-printer-common only, but it
  broke the Printers panel since Ubuntu's packaging moved the dbus
  service to the system-config-printer-gnome package (See bug 1496860 &
  bug 1623150 & bug 1637466 ).

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

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

[Desktop-packages] [Bug 1647917] Re: Invalid access when opening eps with ghostscript 9.19~dfsg+1-0ubuntu6.2 and libspectre 0.2.8

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

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

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

Title:
  Invalid access when opening eps with ghostscript
  9.19~dfsg+1-0ubuntu6.2 and libspectre 0.2.8

Status in libspectre:
  Unknown
Status in ghostscript package in Ubuntu:
  New
Status in libspectre package in Ubuntu:
  New

Bug description:
  1. Install the latest Ubuntu security update for ghostscript (since
  this does not appear to have been released for zesty, it is a bit
  easier to do this from Ubuntu 16.10 than from 17.04).

  2. Install libspectre1 0.2.8-1 (from zesty or zesty-proposed).

  3. Open a .eps with Evince, Ubuntu's default viewer for eps files.
  Here's a test file:

  
https://bugs.launchpad.net/ubuntu/+source/libspectre/+bug/1348384/+attachment/4171120/+files/countrate.eps

  What happens:
  The .eps fails to display. If run from a terminal, this is output:

  invalidaccess -7

  Earlier version of libspectre (I tested Ubuntu 14.04 and 16.10) still
  handle the test .eps file ok.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ghostscript 9.19~dfsg+1-0ubuntu6.2
  ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6
  Uname: Linux 4.8.0-28-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Dec  6 21:52:04 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-11 (117 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ghostscript
  UpgradeStatus: Upgraded to yakkety on 2016-10-27 (40 days ago)

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

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

[Desktop-packages] [Bug 1647917] [NEW] Invalid access when opening eps with ghostscript 9.19~dfsg+1-0ubuntu6.2 and libspectre 0.2.8

Public bug reported:

1. Install the latest Ubuntu security update for ghostscript (since this
does not appear to have been released for zesty, it is a bit easier to
do this from Ubuntu 16.10 than from 17.04).

2. Install libspectre1 0.2.8-1 (from zesty or zesty-proposed).

3. Open a .eps with Evince, Ubuntu's default viewer for eps files.
Here's a test file:

https://bugs.launchpad.net/ubuntu/+source/libspectre/+bug/1348384/+attachment/4171120/+files/countrate.eps

What happens:
The .eps fails to display. If run from a terminal, this is output:

invalidaccess -7

Earlier version of libspectre (I tested Ubuntu 14.04 and 16.10) still
handle the test .eps file ok.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ghostscript 9.19~dfsg+1-0ubuntu6.2
ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6
Uname: Linux 4.8.0-28-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Dec  6 21:52:04 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-08-11 (117 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ghostscript
UpgradeStatus: Upgraded to yakkety on 2016-10-27 (40 days ago)

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

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


** Tags: amd64 apport-bug block-proposed zesty

** Also affects: libspectre (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: block-proposed

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

Title:
  Invalid access when opening eps with ghostscript
  9.19~dfsg+1-0ubuntu6.2 and libspectre 0.2.8

Status in ghostscript package in Ubuntu:
  New
Status in libspectre package in Ubuntu:
  New

Bug description:
  1. Install the latest Ubuntu security update for ghostscript (since
  this does not appear to have been released for zesty, it is a bit
  easier to do this from Ubuntu 16.10 than from 17.04).

  2. Install libspectre1 0.2.8-1 (from zesty or zesty-proposed).

  3. Open a .eps with Evince, Ubuntu's default viewer for eps files.
  Here's a test file:

  
https://bugs.launchpad.net/ubuntu/+source/libspectre/+bug/1348384/+attachment/4171120/+files/countrate.eps

  What happens:
  The .eps fails to display. If run from a terminal, this is output:

  invalidaccess -7

  Earlier version of libspectre (I tested Ubuntu 14.04 and 16.10) still
  handle the test .eps file ok.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ghostscript 9.19~dfsg+1-0ubuntu6.2
  ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6
  Uname: Linux 4.8.0-28-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Dec  6 21:52:04 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-11 (117 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ghostscript
  UpgradeStatus: Upgraded to yakkety on 2016-10-27 (40 days ago)

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

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

[Desktop-packages] [Bug 1647917] Re: Invalid access when opening eps with ghostscript 9.19~dfsg+1-0ubuntu6.2 and libspectre 0.2.8

I am going to go ahead and set the 'block-proposed' tag since we don't
want zesty to break when ghostscript is updated next there.

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

Title:
  Invalid access when opening eps with ghostscript
  9.19~dfsg+1-0ubuntu6.2 and libspectre 0.2.8

Status in ghostscript package in Ubuntu:
  New
Status in libspectre package in Ubuntu:
  New

Bug description:
  1. Install the latest Ubuntu security update for ghostscript (since
  this does not appear to have been released for zesty, it is a bit
  easier to do this from Ubuntu 16.10 than from 17.04).

  2. Install libspectre1 0.2.8-1 (from zesty or zesty-proposed).

  3. Open a .eps with Evince, Ubuntu's default viewer for eps files.
  Here's a test file:

  
https://bugs.launchpad.net/ubuntu/+source/libspectre/+bug/1348384/+attachment/4171120/+files/countrate.eps

  What happens:
  The .eps fails to display. If run from a terminal, this is output:

  invalidaccess -7

  Earlier version of libspectre (I tested Ubuntu 14.04 and 16.10) still
  handle the test .eps file ok.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ghostscript 9.19~dfsg+1-0ubuntu6.2
  ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6
  Uname: Linux 4.8.0-28-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Dec  6 21:52:04 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-11 (117 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ghostscript
  UpgradeStatus: Upgraded to yakkety on 2016-10-27 (40 days ago)

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

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

[Desktop-packages] [Bug 1644695] Re: won't boot

2016-12-06 Thread Daniel van Vugt

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

** Summary changed:

- won't boot
+ Ubuntu won't boot past purple screen

** Package changed: linux (Ubuntu) => 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/1644695

Title:
  Ubuntu won't boot past purple screen

Status in Ubuntu:
  New

Bug description:
  won't boot past purple screen

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CasperVersion: 1.376
  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 Nov 25 04:19:00 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:22cd]
  LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- oem-config/enable=true
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.42
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 22CD
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 93.32
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.42:bd11/04/2015:svnHewlett-Packard:pnHP15NotebookPC:pvr097710205F1620180:rvnHewlett-Packard:rn22CD:rvr93.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 097710205F1620180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Nov 25 04:02:54 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.2
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1222221] Re: first time connection/driver download problem. printer hp 1006

2016-12-06 Thread Rodney Dawes

** Package changed: indicator-printers (Ubuntu) => hplip (Ubuntu)

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

Title:
  first time connection/driver download problem. printer hp 1006

Status in hplip package in Ubuntu:
  New

Bug description:
  After first connection of the printer to laptop via usb, we see notify in top 
right corner, something like: downloading proprietary file for hp 1006 
printer...
  And nothing happened next. I were obligated to do manually 'sudo hp-setup' 
and add printer.

  As i remember, in older versions of Ubuntu, after first plug in of the
  printer, were pop-up window, were you need to press several times
  'enter', agree with license and finally hear nice sound of the printer
  witch signalize that all is OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: indicator-printers 0.1.7daily13.03.01-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
  Uname: Linux 3.8.0-30-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Sat Sep  7 21:21:06 2013
  InstallationDate: Installed on 2013-09-01 (6 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-printers
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1647836] Re: nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to build [error: variably modified ‘transition_task’ at file scope]

2016-12-06 Thread Daniel van Vugt

** Summary changed:

- nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to build
+ nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to build 
[error: variably modified ‘transition_task’ at file scope]

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

Title:
  nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to
  build [error: variably modified ‘transition_task’ at file scope]

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

Bug description:
  crashed while trying to install linux kernel 4.4.0-53 using ``apt
  upgrade''

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-367 367.57-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Uname: Linux 4.4.0-51-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-53-generic
  Date: Tue Dec  6 14:55:08 2016
  DuplicateSignature: 
dkms:nvidia-367:367.57-0ubuntu0.16.04.1:include/linux/cpufreq.h:114:22: error: 
variably modified ‘transition_task’ at file scope
  InstallationDate: Installed on 2015-09-17 (446 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageVersion: 367.57-0ubuntu0.16.04.1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: nvidia-graphics-drivers-367
  Title: nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to 
build
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (227 days ago)

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

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

[Desktop-packages] [Bug 1222221] [NEW] first time connection/driver download problem. printer hp 1006

You have been subscribed to a public bug:

After first connection of the printer to laptop via usb, we see notify in top 
right corner, something like: downloading proprietary file for hp 1006 
printer...
And nothing happened next. I were obligated to do manually 'sudo hp-setup' and 
add printer.

As i remember, in older versions of Ubuntu, after first plug in of the
printer, were pop-up window, were you need to press several times
'enter', agree with license and finally hear nice sound of the printer
witch signalize that all is OK.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: indicator-printers 0.1.7daily13.03.01-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
Uname: Linux 3.8.0-30-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
Date: Sat Sep  7 21:21:06 2013
InstallationDate: Installed on 2013-09-01 (6 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=uk_UA.UTF-8
 SHELL=/bin/bash
SourcePackage: indicator-printers
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug raring third-party-packages
-- 
first time connection/driver download problem. printer hp 1006
https://bugs.launchpad.net/bugs/121
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to hplip in Ubuntu.

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

[Desktop-packages] [Bug 1647906] [NEW] gnome-font-viewer crashes with the 'webdings.ttf' font from the ttf-mscorefonts-installer package

2016-12-06 Thread John Pye

Public bug reported:

On updated Ubuntu 16.04 LTS with Font Viewer 3.16.2, I get the following
crash:

john@thunder:~$ gnome-font-viewer
/usr/share/fonts/truetype/msttcorefonts/webdings.ttf

(gnome-font-viewer:20485): Pango-CRITICAL **: pango_find_base_dir: assertion 
'text != NULL || length == 0' failed
Segmentation fault (core dumped)

The font in question comes from the ttf-mscorefonts-installer package.
For checking the specific font file my system downloaded,

john@thunder:~$ md5sum /usr/share/fonts/truetype/msttcorefonts/webdings.ttf 
1a56b45a66b07b4c576d5ead048ed992  
/usr/share/fonts/truetype/msttcorefonts/webdings.ttf

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

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

Title:
  gnome-font-viewer crashes with the 'webdings.ttf' font from the ttf-
  mscorefonts-installer package

Status in gnome-font-viewer package in Ubuntu:
  New

Bug description:
  On updated Ubuntu 16.04 LTS with Font Viewer 3.16.2, I get the
  following crash:

  john@thunder:~$ gnome-font-viewer
  /usr/share/fonts/truetype/msttcorefonts/webdings.ttf

  (gnome-font-viewer:20485): Pango-CRITICAL **: pango_find_base_dir: assertion 
'text != NULL || length == 0' failed
  Segmentation fault (core dumped)

  The font in question comes from the ttf-mscorefonts-installer package.
  For checking the specific font file my system downloaded,

  john@thunder:~$ md5sum /usr/share/fonts/truetype/msttcorefonts/webdings.ttf 
  1a56b45a66b07b4c576d5ead048ed992  
/usr/share/fonts/truetype/msttcorefonts/webdings.ttf

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

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

[Desktop-packages] [Bug 1643129] Re: Drop system-config-printer-gnome package

Marko, thanks for commenting and helping to make Ubuntu better.

Yes, we can add a transitional system-config-printer-gnome package to
make upgrades smoother.

** Changed in: ubuntu-meta (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: ubuntu-gnome
   Status: Triaged => Fix Released

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

Title:
  Drop system-config-printer-gnome package

Status in Ubuntu GNOME:
  Fix Released
Status in system-config-printer package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in xubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  I don't think the system-config-printer-gnome split makes sense any
  more and it would be nice to get this package closer in sync with
  Debian. In other words, let's drop system-config-printer-gnome and
  move most of its contents back to system-config-printer but a few
  files will end up in system-config-printer-common.

  The last explicit merge was almost a decade ago:
  https://launchpad.net/ubuntu/+source/system-config-printer/0.7.70-1ubuntu1 )

  The split was done in 2008 for KDE's benefit:
  
https://launchpad.net/ubuntu/+source/system-config-printer/0.7.78+svn1799-0ubuntu2

  - system-config-printer-kde no longer exists (it appears to have been
  part of the kdeadmin source package which was removed a few years ago)

  - Kubuntu only ships system-config-printer-udev so they aren't affected now
  
http://cdimage.ubuntu.com/cdimage/kubuntu/daily-live/current/zesty-desktop-amd64.manifest

  - Ubuntu GNOME does not need the files shipped in system-config-
  printer since GNOME has its own integrated Printers Settings panel.

  https://packages.debian.org/sid/all/system-config-printer/filelist

  In Ubuntu 16.10 I attempted to follow Debian's gnome-control-center
  packaging and depend on system-config-printer-common only, but it
  broke the Printers panel since Ubuntu's packaging moved the dbus
  service to the system-config-printer-gnome package (See bug 1496860 &
  bug 1623150 & bug 1637466 ).

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

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

[Desktop-packages] [Bug 1583227] Re: Rotated screen doesn't have rotated touch gestures

2016-12-06 Thread Onno

Hmm seems to be a kernel bug 
https://bugzilla.kernel.org/show_bug.cgi?id=120011

** Bug watch added: Linux Kernel Bug Tracker #120011
   http://bugzilla.kernel.org/show_bug.cgi?id=120011

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

Title:
  Rotated screen doesn't have rotated touch gestures

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When I rotate the screen on this Lenovo X230T using the button on the
  LCD, the touch input gestures do not rotate as well.  For example, if
  I rotate 90 degrees a horizontal two finger drag does a vertical
  scroll.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  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 May 18 08:32:16 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2016-05-09 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=731d521d-ab9f-4b31-9434-cb6b859fe8d1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
   Identifier  "Intel Graphics"
   Driver  "intel"
   Option  "TearFree" "true"
   EndSection
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  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: Wed May 18 08:17:52 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 728 
   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/1583227/+subscriptions

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

[Desktop-packages] [Bug 1645341] Re: Wacom serial: Screen rotation triggers pen/eraser rotation but not for finger touch

2016-12-06 Thread Onno

There is a Ticket in https://bugzilla.kernel.org/show_bug.cgi?id=120011
which sounds similar.

** Bug watch added: Linux Kernel Bug Tracker #120011
   http://bugzilla.kernel.org/show_bug.cgi?id=120011

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

Title:
  Wacom serial: Screen rotation triggers pen/eraser rotation but not for
  finger touch

Status in xf86-input-wacom package in Ubuntu:
  Confirmed

Bug description:
  After updating to xenial the finger touch was broken. With an update
  to yakkety the finger touch device came back, but it doesn't rotate
  with the screen, how it used to in former releases. Pen and eraser are
  rotated as expected.

  I discovered, that the bug occurs only with linux kernels after 4.4,
  so it depends on recent changes in the kernel.

  The 'xsetwacom list devices' command generates the output:
  Wacom Serial Penabled 2FG Touchscreen Pen stylus  id: 15  type: STYLUS
  Wacom Serial Penabled 2FG Touchscreen Finger touchid: 16  type: TOUCH 
  Wacom Serial Penabled 2FG Touchscreen Pen eraser  id: 18  type: ERASER

  ... but with the old linux kernel from utopic (4.2.0) the ids are different:
  15 for the stylus (unchanged), 17 for the eraser, 18 for finger touch

  This bug affects:
  * an updated system how described above
  * a fresh installation of yakkety (used to file this bug)
  * the zesty daily build

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xserver-xorg-input-wacom 1:0.33.0-0ubuntu1
  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: Mon Nov 28 15:10:21 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  InstallationDate: Installed on 2016-11-28 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Hewlett-Packard HP EliteBook 2760p
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=71701156-1f2c-4138-a7eb-0c16ea6b53d3 ro quiet splash
  SourcePackage: xf86-input-wacom
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SOU Ver. F.62
  dmi.board.name: 162A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 05.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SOUVer.F.62:bd05/27/2016:svnHewlett-Packard:pnHPEliteBook2760p:pvrA0005F02:rvnHewlett-Packard:rn162A:rvrKBCVersion05.41:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 2760p
  dmi.product.version: A0005F02
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.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.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: Mon Nov 28 14:32:58 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1645341/+subscriptions

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

[Desktop-packages] [Bug 1583227] Re: Rotated screen doesn't have rotated touch gestures

2016-12-06 Thread Onno

I have the same problem with Thinkpad X201t

stylus and eraser work, but touch not

root@thinkpad:/usr/bin# xsetwacom get "Serial Wacom Tablet WACf00c touch" Rotate
cw
root@thinkpad:/usr/bin# xsetwacom get "Serial Wacom Tablet WACf00c stylus" 
Rotate
cw

both touch and stylus are in the same mode.

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

Title:
  Rotated screen doesn't have rotated touch gestures

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When I rotate the screen on this Lenovo X230T using the button on the
  LCD, the touch input gestures do not rotate as well.  For example, if
  I rotate 90 degrees a horizontal two finger drag does a vertical
  scroll.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  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 May 18 08:32:16 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2016-05-09 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=731d521d-ab9f-4b31-9434-cb6b859fe8d1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
   Identifier  "Intel Graphics"
   Driver  "intel"
   Option  "TearFree" "true"
   EndSection
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  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: Wed May 18 08:17:52 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 728 
   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/1583227/+subscriptions

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

[Desktop-packages] [Bug 1583227] Re: Rotated screen doesn't have rotated touch gestures

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

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

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

Title:
  Rotated screen doesn't have rotated touch gestures

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When I rotate the screen on this Lenovo X230T using the button on the
  LCD, the touch input gestures do not rotate as well.  For example, if
  I rotate 90 degrees a horizontal two finger drag does a vertical
  scroll.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  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 May 18 08:32:16 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2016-05-09 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=731d521d-ab9f-4b31-9434-cb6b859fe8d1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
   Identifier  "Intel Graphics"
   Driver  "intel"
   Option  "TearFree" "true"
   EndSection
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  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: Wed May 18 08:17:52 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 728 
   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/1583227/+subscriptions

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

[Desktop-packages] [Bug 1647874] [NEW] ps2epsi failure after 02 December update

2016-12-06 Thread David Annetts

Public bug reported:

The program ps2epsi was working before the automatic update on 02
December, 2016. Now it is not.

>From the screen dump:-
ann019@power-kf:~/Dropbox$ ps2epsi drawing.ps
Error: /invalidaccess in --.locksafe--
Operand stack:
   --dict:1200/1684(ro)(G)--   getenv   --nostringval--
Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--   
--nostringval--   2   %stopped_push   --nostringval--   --nostringval--   
--nostringval--   false   1   %stopped_push   1977   1   4   %oparray_pop   
1976   1   4   %oparray_pop   1960   1   4   %oparray_pop   1852   1   4   
%oparray_pop   --nostringval--   %errorexec_pop   .runexec2   --nostringval--   
--nostringval--   --nostringval--   2   %stopped_push   --nostringval--   
--nostringval--   1986   0   5   %oparray_pop   1984   0   5   %oparray_pop   
--nostringval--
Dictionary stack:
   --dict:1200/1684(ro)(G)--   --dict:0/20(G)--   --dict:82/200(L)--   
--dict:5/30(L)--   --dict:20/30(L)--
Current allocation mode is local
Last OS error: No such file or directory
Current file position is 8558
GPL Ghostscript 9.18: Unrecoverable error, exit code 1

ann019@power-kf:~/Dropbox$ lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04

ann019@power-kf:~/Dropbox$ apt-cache policy ghostscript
ghostscript:
  Installed: 9.18~dfsg~0-0ubuntu2.2
  Candidate: 9.18~dfsg~0-0ubuntu2.2
  Version table:
 *** 9.18~dfsg~0-0ubuntu2.2 500
500 http://lips.csiro.au/ubuntu xenial-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
500 http://mirror.aarnet.edu.au/ubuntu xenial-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 9.18~dfsg~0-0ubuntu2 500
500 http://lips.csiro.au/ubuntu xenial/main amd64 Packages
500 http://mirror.aarnet.edu.au/ubuntu xenial/main amd64 Packages

What I expected to happen: the command ps2epsi drawing.ps should
complete without error and produce the file drawing.epsi.

What happened instead: the command ps2epsi drawing.ps threw the error above. 
The file drawing.epsi was produced. However, the file throws an error when 
opened by epstopdf:-
ann019@power-kf:~/Dropbox$ epstopdf drawing.epsi
==> Warning: BoundingBox not found

Despite the error, a pdf is produced (drawing.pdf). But it cannot be
opened by evince.

All files in the chain (drawing.ps, drawing.epsi & drawing.pdf) are
attached as.

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


** Tags: eps2pdf pstoepsi

** Attachment added: "20161202_pstoeps_bug_support.tar.gz"
   
https://bugs.launchpad.net/bugs/1647874/+attachment/4788332/+files/20161202_pstoeps_bug_support.tar.gz

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

Title:
  ps2epsi failure after 02 December update

Status in ghostscript package in Ubuntu:
  New

Bug description:
  The program ps2epsi was working before the automatic update on 02
  December, 2016. Now it is not.

  From the screen dump:-
  ann019@power-kf:~/Dropbox$ ps2epsi drawing.ps
  Error: /invalidaccess in --.locksafe--
  Operand stack:
 --dict:1200/1684(ro)(G)--   getenv   --nostringval--
  Execution stack:
 %interp_exit   .runexec2   --nostringval--   --nostringval--   
--nostringval--   2   %stopped_push   --nostringval--   --nostringval--   
--nostringval--   false   1   %stopped_push   1977   1   4   %oparray_pop   
1976   1   4   %oparray_pop   1960   1   4   %oparray_pop   1852   1   4   
%oparray_pop   --nostringval--   %errorexec_pop   .runexec2   --nostringval--   
--nostringval--   --nostringval--   2   %stopped_push   --nostringval--   
--nostringval--   1986   0   5   %oparray_pop   1984   0   5   %oparray_pop   
--nostringval--
  Dictionary stack:
 --dict:1200/1684(ro)(G)--   --dict:0/20(G)--   --dict:82/200(L)--   
--dict:5/30(L)--   --dict:20/30(L)--
  Current allocation mode is local
  Last OS error: No such file or directory
  Current file position is 8558
  GPL Ghostscript 9.18: Unrecoverable error, exit code 1

  ann019@power-kf:~/Dropbox$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  ann019@power-kf:~/Dropbox$ apt-cache policy ghostscript
  ghostscript:
Installed: 9.18~dfsg~0-0ubuntu2.2
Candidate: 9.18~dfsg~0-0ubuntu2.2
Version table:
   *** 9.18~dfsg~0-0ubuntu2.2 500
  500 http://lips.csiro.au/ubuntu xenial-updates/main amd64 Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://mirror.aarnet.edu.au/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   9.18~dfsg~0-0ubuntu2 500
  500 http://lips.csiro.au/ubuntu xenial/main amd64 Packages
  500 http://mirror.aarnet.edu.au/ubuntu xenial/main amd64 Packages

  What I expected to happen: the command ps2epsi drawing.ps should

Re: [Desktop-packages] [Bug 1647276] Re: ps2epsi fails after December 01 update

2016-12-06 Thread David Annetts

Hi Ray,

Fair enough.

But this reply does not actually solve the problem that was created by
the 02 December update.

I will file another bug report

David Annetts  Ph.D.
Senior Research Scientist
CSIRO | Mineral Resources
E david.anne...@csiro.au T +61 8 6436 8517 M 0411 756 129
26 Dick Perry Av. KENSINGTON, 6151, AUSTRALIA
www.csiro.au

PLEASE NOTE
The information contained in this email may be confidential or privileged. Any 
unauthorised use or disclosure is prohibited. If you have received this email 
in error, please delete it immediately and notify the sender by return email. 
Thank you. To the extent permitted by law, CSIRO does not represent, warrant 
and/or guarantee that the integrity of this communication has been maintained 
or that the communication is free of errors, virus, interception or 
interference.


From: boun...@canonical.com  on behalf of Ray Johnston 
<1647...@bugs.launchpad.net>
Sent: Wednesday, 7 December 2016 05:54
To: Annetts, Dave (Mineral Resources, Kensington WA)
Subject: [Bug 1647276] Re: ps2epsi fails after December 01 update

Just in case you aren't following the bug forwarded to us, we have closed the 
bug as INVALID
Basically, the bug report was incomplete, and confusing -- the title and follow 
up info to us
indicated ps2epsi, but the description comment "This means that I am unable to 
convert from a ps to a PDF and have the correct (tight) bounding box." 
indicates that a PDF was being created. ps2epsi does not create a PDF 
(ghostscript can, using ps2pdf, not ps2epsi.

We did try ps2epsi and the %%BoundingBox looks fine.

Please try and do a better job of describing bugs in the future, bu including 
the command line
and describing the "before" and "after" results in as much detail as possible, 
particularly
what you think is incorrect in the "after".

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1647276

Title:
  ps2epsi fails after December 01 update

Status in ghostscript package in Ubuntu:
  New

Bug description:
  ps2epsi conversion was working fine before the December 2 update.
  Now? Broken.


  This means that I am unable to convert from a ps to a PDF and have the
  correct (tight) bounding box.

  Start-Date: 2016-12-02  10:42:35
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libgs9:amd64 (9.18~dfsg~0-0ubuntu2, 9.18~dfsg~0-0ubuntu2.2), 
ghostscript:amd64 (9.18~dfsg~0-0ubuntu2, 9.18~df
  sg~0-0ubuntu2.2), ghostscript-x:amd64 (9.18~dfsg~0-0ubuntu2, 
9.18~dfsg~0-0ubuntu2.2), libgs9-common:amd64 (9.18~dfsg~0
  -0ubuntu2, 9.18~dfsg~0-0ubuntu2.2)
  End-Date: 2016-12-02  10:42:37

  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

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

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

Title:
  ps2epsi fails after December 01 update

Status in ghostscript package in Ubuntu:
  New

Bug description:
  ps2epsi conversion was working fine before the December 2 update.
  Now? Broken.


  This means that I am unable to convert from a ps to a PDF and have the
  correct (tight) bounding box.

  Start-Date: 2016-12-02  10:42:35
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libgs9:amd64 (9.18~dfsg~0-0ubuntu2, 9.18~dfsg~0-0ubuntu2.2), 
ghostscript:amd64 (9.18~dfsg~0-0ubuntu2, 9.18~df
  sg~0-0ubuntu2.2), ghostscript-x:amd64 (9.18~dfsg~0-0ubuntu2, 
9.18~dfsg~0-0ubuntu2.2), libgs9-common:amd64 (9.18~dfsg~0
  -0ubuntu2, 9.18~dfsg~0-0ubuntu2.2)
  End-Date: 2016-12-02  10:42:37

  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

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

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

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

2016-12-06 Thread jagdtigger

I have an HP x2 210 detachable, the problem is still there with the
4.8.12-040812-generic kernel :/ (im running kubuntu).

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

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

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

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

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

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

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

[Desktop-packages] [Bug 363293] Re: "Overscaled" desktop icons behave strange

2016-12-06 Thread Bug Watch Updater

** Changed in: nautilus
   Status: Incomplete => 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/363293

Title:
  "Overscaled" desktop icons behave strange

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

Bug description:
  Binary package hint: nautilus

  Ubuntu 9.04 [AMD64]
  Gnome 2.26.1
  Nautilus 2.26.2

  When I resizing an icon on the Gnome desktop (Nautilus?) there is a
  limit of how big it can become. When I trying to resize an icon over
  the limit and then scale it down it starting to resize only after a
  delay. And when "overscaled" some more the icon starts to move
  nonlinearly instead of resizing.

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

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

[Desktop-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2016-12-06 Thread Oleg "Nightwing" Lomakin

network-manager 1.2.2-0ubuntu0.16.04.3 and network-manager-gnome 
1.2.0-0ubuntu0.16.04.4 still had this bug. 
Only nm-applet restart help

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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

[Desktop-packages] [Bug 1642662] Re: SRU request: handle EGL alternatives and use different drivers for the LTS stacks

2016-12-06 Thread Peng

This update broke my system Dell Precision M6800 with Nvidia Quadro K3100M.
prime-select intel/nvidia shows:

Traceback (most recent call last):
  File "/usr/bin/prime-select", line 398, in 
if not switcher.enable_profile(arg):
  File "/usr/bin/prime-select", line 323, in enable_profile
egl_alternatives = self._get_current_egl_alternative()
  File "/usr/bin/prime-select", line 219, in _get_current_egl_alternative
return self._get_current_alternative(self._egl_switcher, 
self._egl_switcher_other)
  File "/usr/bin/prime-select", line 211, in _get_current_alternative
alternatives[1] = self._simplify_gl_alternative_name(raw_alternative_other)
  File "/usr/bin/prime-select", line 185, in _simplify_gl_alternative_name
return alternative.split('/')[-2]
IndexError: list index out of range

/var/log/gpu-manager.log:
log_file: /var/log/gpu-manager.log
last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
can't access /run/u-d-c-fglrx-was-loaded file
Looking for fglrx modules in /lib/modules/4.4.0-51-generic/updates/dkms
Looking for nvidia modules in /lib/modules/4.4.0-51-generic/updates/dkms
Found nvidia module: nvidia_370_modeset.ko
Is nvidia loaded? yes
Was nvidia unloaded? no
Is nvidia blacklisted? no
Is fglrx loaded? no
Was fglrx unloaded? no
Is fglrx blacklisted? no
Is intel loaded? yes
Is radeon loaded? no
Is radeon blacklisted? no
Is amdgpu loaded? no
Is amdgpu blacklisted? no
Is nouveau loaded? no
Is nouveau blacklisted? yes
Is fglrx kernel module available? no
Is nvidia kernel module available? yes
Vendor/Device Id: 8086:416
BusID "PCI:0@0:2:0"
Is boot vga? yes
Vendor/Device Id: 10de:11b6
BusID "PCI:1@0:0:0"
Is boot vga? no
Skipping "/dev/dri/card1", driven by "i915"
Skipping "/dev/dri/card0", driven by "nvidia-drm"
Skipping "/dev/dri/card1", driven by "i915"
Skipping "/dev/dri/card0", driven by "nvidia-drm"
Skipping "/dev/dri/card1", driven by "i915"
Skipping "/dev/dri/card0", driven by "nvidia-drm"
Found "/dev/dri/card1", driven by "i915"
output 0:
card1-eDP-1
Number of connected outputs for /dev/dri/card1: 1
Does it require offloading? yes
last cards number = 1
Has amd? no
Has intel? yes
Has nvidia? yes
How many cards? 2
The number of cards has changed!
Has the system changed? Yes
main_arch_path x86_64-linux-gnu, other_arch_path i386-linux-gnu
Current alternative: /usr/lib/nvidia-370-prime/ld.so.conf
Current core alternative: (null)
Current egl alternative: /usr/lib/x86_64-linux-gnu/mesa-egl/ld.so.conf
Is nvidia enabled? no
Is nvidia egl enabled? no
Is fglrx enabled? no
Is mesa enabled? no
Is mesa egl enabled? yes
Is pxpress enabled? no
Is prime enabled? yes
Is prime egl enabled? no
Is nvidia available? yes
Is nvidia egl available? no
Is fglrx available? no
Is fglrx-core available? no
Is mesa available? yes
Is mesa egl available? yes
Is pxpress available? no
Is prime available? yes
Is prime egl available? no
System configuration has changed
Intel IGP detected
Intel hybrid system
Nvidia driver version 370.28 detected
/sys/class/dmi/id/product_version="00"
/sys/class/dmi/id/product_name="Precision M6800"
1st try: bbswitch without quirks
Loading bbswitch with "load_state=-1 unload_state=1" parameters
Removing xorg.conf. Path: /etc/X11/xorg.conf
Moved /etc/X11/xorg.conf to /etc/X11/xorg.conf.12062016
Powering off the discrete card
Disabling persistence mode
Unloading nvidia-uvm with "no" parameters
Unloading nvidia-drm with "no" parameters
Unloading nvidia-modeset with "no" parameters
Unloading nvidia with "no" parameters

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

Title:
  SRU request: handle EGL alternatives and use different drivers for the
  LTS stacks

Status in HWE Next:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Trusty:
  Fix Released
Status in ubuntu-drivers-common source package in Trusty:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  A recent security update of the nvidia driver provided new EGL libraries and 
new kernel modules (such as nvidia-modeset and nvidia-drm), which are not 
handled by the current gpu-manager (ubuntu-drivers-common) and nvidia-prime in 
14.04. This problem is fixed in Xenial or newer.

  ubuntu-drivers-common also does not distinguish between the different
  LTS stacks, and this is a major problem on Intel+Nvidia hybrid
  systems, as anything running stacks older than 14.04.5 will require
  using the intel driver with SNA acceleration, whereas the rest should
  use the modesetting driver. Boot parameters can also be passed to use
  other driver combinations (for unsupported use cases).

  [Test Case]
  1) Enable the trusty-proposed repository, and install the 
ubuntu-drivers-common and the nvidia-prime

[Desktop-packages] [Bug 1643129] Re: Drop system-config-printer-gnome package

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

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

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

Title:
  Drop system-config-printer-gnome package

Status in Ubuntu GNOME:
  Triaged
Status in system-config-printer package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in xubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  I don't think the system-config-printer-gnome split makes sense any
  more and it would be nice to get this package closer in sync with
  Debian. In other words, let's drop system-config-printer-gnome and
  move most of its contents back to system-config-printer but a few
  files will end up in system-config-printer-common.

  The last explicit merge was almost a decade ago:
  https://launchpad.net/ubuntu/+source/system-config-printer/0.7.70-1ubuntu1 )

  The split was done in 2008 for KDE's benefit:
  
https://launchpad.net/ubuntu/+source/system-config-printer/0.7.78+svn1799-0ubuntu2

  - system-config-printer-kde no longer exists (it appears to have been
  part of the kdeadmin source package which was removed a few years ago)

  - Kubuntu only ships system-config-printer-udev so they aren't affected now
  
http://cdimage.ubuntu.com/cdimage/kubuntu/daily-live/current/zesty-desktop-amd64.manifest

  - Ubuntu GNOME does not need the files shipped in system-config-
  printer since GNOME has its own integrated Printers Settings panel.

  https://packages.debian.org/sid/all/system-config-printer/filelist

  In Ubuntu 16.10 I attempted to follow Debian's gnome-control-center
  packaging and depend on system-config-printer-common only, but it
  broke the Printers panel since Ubuntu's packaging moved the dbus
  service to the system-config-printer-gnome package (See bug 1496860 &
  bug 1623150 & bug 1637466 ).

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

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

[Desktop-packages] [Bug 1643129] Re: Drop system-config-printer-gnome package

2016-12-06 Thread Marko Stanković

Current state of packages in Zesty (proposed is disabled) produces a conflict 
for those with system-config-printer 1.5.7+20160812-0ubuntu2 because updating 
it to 1.5.7+20160812-0ubuntu4 breaks system-config-printer-gnome (<< 
1.5.7+20160812-0ubuntu3~) and available version of system-config-printer-gnome 
is 1.5.7+20160812-0ubuntu2
Proposed resolutions are:
1. keep system-config-printer
2. remove system-config-printer-gnome
I resolved the conflict by removing system-config-printer-gnome only after 
finding this LP bug and figuring out what's going on. I know this is a 
development version of Ubuntu, but many people will still be confused with this 
conflict.
Maybe there is a different way of making this transition that doesn't create a 
conflict?

Cheers,
Marko

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

Title:
  Drop system-config-printer-gnome package

Status in Ubuntu GNOME:
  Triaged
Status in system-config-printer package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in xubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  I don't think the system-config-printer-gnome split makes sense any
  more and it would be nice to get this package closer in sync with
  Debian. In other words, let's drop system-config-printer-gnome and
  move most of its contents back to system-config-printer but a few
  files will end up in system-config-printer-common.

  The last explicit merge was almost a decade ago:
  https://launchpad.net/ubuntu/+source/system-config-printer/0.7.70-1ubuntu1 )

  The split was done in 2008 for KDE's benefit:
  
https://launchpad.net/ubuntu/+source/system-config-printer/0.7.78+svn1799-0ubuntu2

  - system-config-printer-kde no longer exists (it appears to have been
  part of the kdeadmin source package which was removed a few years ago)

  - Kubuntu only ships system-config-printer-udev so they aren't affected now
  
http://cdimage.ubuntu.com/cdimage/kubuntu/daily-live/current/zesty-desktop-amd64.manifest

  - Ubuntu GNOME does not need the files shipped in system-config-
  printer since GNOME has its own integrated Printers Settings panel.

  https://packages.debian.org/sid/all/system-config-printer/filelist

  In Ubuntu 16.10 I attempted to follow Debian's gnome-control-center
  packaging and depend on system-config-printer-common only, but it
  broke the Printers panel since Ubuntu's packaging moved the dbus
  service to the system-config-printer-gnome package (See bug 1496860 &
  bug 1623150 & bug 1637466 ).

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

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

[Desktop-packages] [Bug 1647276] Re: ps2epsi fails after December 01 update

2016-12-06 Thread Ray Johnston

Just in case you aren't following the bug forwarded to us, we have closed the 
bug as INVALID
Basically, the bug report was incomplete, and confusing -- the title and follow 
up info to us
indicated ps2epsi, but the description comment "This means that I am unable to 
convert from a ps to a PDF and have the correct (tight) bounding box." 
indicates that a PDF was being created. ps2epsi does not create a PDF 
(ghostscript can, using ps2pdf, not ps2epsi.

We did try ps2epsi and the %%BoundingBox looks fine.

Please try and do a better job of describing bugs in the future, bu including 
the command line
and describing the "before" and "after" results in as much detail as possible, 
particularly
what you think is incorrect in the "after".

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

Title:
  ps2epsi fails after December 01 update

Status in ghostscript package in Ubuntu:
  New

Bug description:
  ps2epsi conversion was working fine before the December 2 update.
  Now? Broken.


  This means that I am unable to convert from a ps to a PDF and have the
  correct (tight) bounding box.

  Start-Date: 2016-12-02  10:42:35
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libgs9:amd64 (9.18~dfsg~0-0ubuntu2, 9.18~dfsg~0-0ubuntu2.2), 
ghostscript:amd64 (9.18~dfsg~0-0ubuntu2, 9.18~df
  sg~0-0ubuntu2.2), ghostscript-x:amd64 (9.18~dfsg~0-0ubuntu2, 
9.18~dfsg~0-0ubuntu2.2), libgs9-common:amd64 (9.18~dfsg~0
  -0ubuntu2, 9.18~dfsg~0-0ubuntu2.2)
  End-Date: 2016-12-02  10:42:37

  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

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

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

[Desktop-packages] [Bug 1625712] Re: Power button no longer opens interactive menu in Xenial

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

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

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

Title:
  Power button no longer opens interactive menu in Xenial

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

Bug description:
  In gnome-shell, the hardware power button does not open the
  interactive power menu. It sleeps the computer instead.

  The configuration backend to customize this behaviour was intentionally 
removed in commit [50564cde49ca2][1] (for [bug 753713][2]). After [some 
discussion](https://bugzilla.gnome.org/show_bug.cgi?id=755953), it's returned 
in [gnome-settings-daemon
  3.20](https://bugzilla.gnome.org/show_bug.cgi?id=755953#c29).

  Unfortunately, 3.20 is not in the [16.04 ubuntu
  repos](https://launchpad.net/ubuntu/+source/gnome-settings-daemon)
  (however there is a 3.20 release for Yakkety 16.10).

  Can 3.20 be released in xenial-updates?

  Removing this functionality is a disruptive change and it appears it
  was introduced in the Xenial LTS release (3.17 was not in Wily). While
  I understand gnome doesn't follow Ubuntu's stable release strategy and
  this is one in a large system of applications, can we get gnome-
  settings-daemon upgraded to 3.20 in Xenial?

  

  Use case scenarios for why this is disruptive:

  * [Accidentally hitting the power 
button](https://www.reddit.com/r/gnome/comments/3oddse/buttonpower_gone_in_318/cvwd2ho)
 sleeps the computer without recourse. The interactive menu gives you 60 
seconds to cancel.
  * Laptops can already suspend when the lid is closed. While the power button 
can be configured to hibernate instead of sleep, my laptop does not support 
hibernate. Now I have a nonfunctional button (when configured to hibernate) or 
two ways to do the same action.
  * Laptops with low battery life cannot last long in suspend state. (And 
again, hibernate does not always work.)
  * The initial change was made to make the media buttons do what their labels 
say, but the "power" button no longer controls powering off the machine.

  Removing "shutdown" from the list of configurations is reasonable on
  the grounds that it is destructive, but removing "interactive" doesn't
  follow since it's the least destructive. The power button was the most
  convenient way to invoke that menu.

  Thank you for your consideration.

  

  Additional information:

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

  $ apt-cache policy gnome-settings-daemon
  gnome-settings-daemon:
Installed: 3.18.2-0ubuntu3
Candidate: 3.18.2-0ubuntu3.1
Version table:
   3.18.2-0ubuntu3.1 500
  500 http://ca.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
   *** 3.18.2-0ubuntu3 500
  500 http://ca.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  
[1]: 
https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=50564cde49ca2
[2]: https://bugzilla.gnome.org/show_bug.cgi?id=753713

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

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

[Desktop-packages] [Bug 385606] Re: Print test page gives an error message "unsupported format: application/postscript"

2016-12-06 Thread stephen dumars

created an ubuntu 16.04 and attempted to install a cups printer driver
that works on earlier versions of ubuntu and when attempting to do a
test print got an  "Unsupported format 'application/postscript'! error
message

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

Title:
  Print test page gives an error message "unsupported format:
  application/postscript"

Status in cups package in Ubuntu:
  Fix Released
Status in ghostscript package in Ubuntu:
  Invalid
Status in gutenprint package in Ubuntu:
  Fix Released
Status in hplip package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Released
Status in splix package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: ghostscript

  Description:Ubuntu karmic (development branch)
  Release:9.10
  Package source: ghostscript
  Version: 8.64.dfsg.1-0ubuntu14

  Upgrading libgs8 and ghostscript from jaunty (8.64.dfsg.1-0ubuntu8) to karmic 
(8.64.dfsg.1-0ubuntu14) gave some problems: I'm no longer able to print 
anything on my printer (Samsung ML-2010) and also the test page from the cups 
web interface gives the error: 
  unsupported format: application/postscript!

  Downgrading again to 8.64.dfsg.1-0ubuntu8 solved the problem.

  Bye

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

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

[Desktop-packages] [Bug 1647836] Re: nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to build

2016-12-06 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 nvidia-graphics-drivers-367 in Ubuntu.
https://bugs.launchpad.net/bugs/1647836

Title:
  nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to
  build

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

Bug description:
  crashed while trying to install linux kernel 4.4.0-53 using ``apt
  upgrade''

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-367 367.57-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Uname: Linux 4.4.0-51-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-53-generic
  Date: Tue Dec  6 14:55:08 2016
  DuplicateSignature: 
dkms:nvidia-367:367.57-0ubuntu0.16.04.1:include/linux/cpufreq.h:114:22: error: 
variably modified ‘transition_task’ at file scope
  InstallationDate: Installed on 2015-09-17 (446 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageVersion: 367.57-0ubuntu0.16.04.1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: nvidia-graphics-drivers-367
  Title: nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to 
build
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (227 days ago)

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

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

[Desktop-packages] [Bug 1647836] [NEW] nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to build

2016-12-06 Thread Asif

Public bug reported:

crashed while trying to install linux kernel 4.4.0-53 using ``apt
upgrade''

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: nvidia-367 367.57-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
Uname: Linux 4.4.0-51-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
DKMSKernelVersion: 4.4.0-53-generic
Date: Tue Dec  6 14:55:08 2016
DuplicateSignature: 
dkms:nvidia-367:367.57-0ubuntu0.16.04.1:include/linux/cpufreq.h:114:22: error: 
variably modified ‘transition_task’ at file scope
InstallationDate: Installed on 2015-09-17 (446 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
PackageVersion: 367.57-0ubuntu0.16.04.1
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15
SourcePackage: nvidia-graphics-drivers-367
Title: nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to 
build
UpgradeStatus: Upgraded to xenial on 2016-04-23 (227 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to
  build

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

Bug description:
  crashed while trying to install linux kernel 4.4.0-53 using ``apt
  upgrade''

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-367 367.57-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Uname: Linux 4.4.0-51-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-53-generic
  Date: Tue Dec  6 14:55:08 2016
  DuplicateSignature: 
dkms:nvidia-367:367.57-0ubuntu0.16.04.1:include/linux/cpufreq.h:114:22: error: 
variably modified ‘transition_task’ at file scope
  InstallationDate: Installed on 2015-09-17 (446 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageVersion: 367.57-0ubuntu0.16.04.1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: nvidia-graphics-drivers-367
  Title: nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to 
build
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (227 days ago)

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

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

[Desktop-packages] [Bug 1647833] [NEW] package libgbm1-lts-utopic:i386 3:13 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 2

2016-12-06 Thread Octavio Sosa

Public bug reported:

update crash!

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libgbm1-lts-utopic:i386 3:13
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
Date: Tue Dec  6 13:49:42 2016
ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 2
InstallationDate: Installed on 2015-05-01 (585 days ago)
InstallationMedia: Lubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15
SourcePackage: xorg-lts-transitional
Title: package libgbm1-lts-utopic:i386 3:13 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 2
UpgradeStatus: Upgraded to xenial on 2016-09-01 (96 days ago)

** Affects: xorg-lts-transitional (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 xorg-lts-transitional in Ubuntu.
https://bugs.launchpad.net/bugs/1647833

Title:
  package libgbm1-lts-utopic:i386 3:13 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 2

Status in xorg-lts-transitional package in Ubuntu:
  New

Bug description:
  update crash!

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgbm1-lts-utopic:i386 3:13
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  Date: Tue Dec  6 13:49:42 2016
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 2
  InstallationDate: Installed on 2015-05-01 (585 days ago)
  InstallationMedia: Lubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: xorg-lts-transitional
  Title: package libgbm1-lts-utopic:i386 3:13 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 2
  UpgradeStatus: Upgraded to xenial on 2016-09-01 (96 days ago)

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

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

[Desktop-packages] [Bug 1647814] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: il sottoprocesso nuovo script pre-removal ha restituito lo stato di errore 1

2016-12-06 Thread Paul White

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

** This bug has been marked a duplicate of bug 1642966
   package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: il
  sottoprocesso nuovo script pre-removal ha restituito lo stato di
  errore 1

Status in cups package in Ubuntu:
  New

Bug description:
  Crash happened during upgrades installation.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30
  Uname: Linux 4.4.0-49-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  AptOrdering:
   cups-daemon: Install
   cups-daemon: Configure
   cups-core-drivers: Configure
   cups: Configure
   NULL: ConfigurePending
  Architecture: amd64
  CupsErrorLog:
   
  Date: Tue Dec  6 19:27:50 2016
  DpkgHistoryLog:
   Start-Date: 2016-12-06  19:27:48
   Commandline: apt-get install -f
   Requested-By: gtu (1000)
   Upgrade: cups-daemon:amd64 (2.1.3-4, 2.1.3-4ubuntu0.1)
  ErrorMessage: il sottoprocesso nuovo script pre-removal ha restituito lo 
stato di errore 1
  InstallationDate: Installed on 2016-01-24 (317 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Acer Aspire E5-573G
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic.efi.signed 
root=UUID=9a6ce903-b4c3-460c-9a5d-26a3bc5f17b2 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic.efi.signed 
root=UUID=9a6ce903-b4c3-460c-9a5d-26a3bc5f17b2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: il 
sottoprocesso nuovo script pre-removal ha restituito lo stato di errore 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.31
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZORO_BH
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.31:bd09/25/2015:svnAcer:pnAspireE5-573G:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-573G
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer

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

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

2016-12-06 Thread C K

Experience the same on a new Macbook Air running Kubuntu 16.04

-- 
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 1021375] Re: Nautilus says the USB stick is read only when it is not

2016-12-06 Thread Lifepower

Just experienced this bug in Ubuntu Yakkety 16.10 64-bit, Unity desktop,
"Files" utility version 3.20.3.

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

Title:
  Nautilus says the USB stick is read only when it is not

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

Bug description:
  First time I use an USB drive since I updated to 12.04 and I found a
  really annoying bug on Nautilus. Nautilus claims that the destination
  drive is read-only when in fact it is not.

  How to reproduce:

  1. Connect a USB stick drive to your competer.
  2. The USB will appear in the desktop.
  3. Open two Nautilus windows one in your home folder, other in the USB stick 
drive.
  4. Select any file from your home folder (small enough to fit the free space 
in the USB drive)
  5. Drag the file and drop it in the USB drive window.

  -- Nautilus will say that it cannot copy the file because the
  destination is read ony --

  If you try the copy the same file with the terminal you will see that
  the file is copied without problem, other programs like gedit or
  LibreOffice can write in the usb stick drive just fine.

  It is not a problem with the USB stick, as shown here:

  [ 6232.288064] usb 2-1: new high-speed USB device number 6 using ehci_hcd
  [ 6232.426378] scsi8 : usb-storage 2-1:1.0
  [ 6233.468489] scsi 8:0:0:0: Direct-Access Kingston DT 101 IIPMAP 
PQ: 0 ANSI: 0 CCS
  [ 6233.469862] sd 8:0:0:0: Attached scsi generic sg2 type 0
  [ 6234.178262] sd 8:0:0:0: [sdb] 3909632 512-byte logical blocks: (2.00 
GB/1.86 GiB)
  [ 6234.178735] sd 8:0:0:0: [sdb] Write Protect is off
  [ 6234.178740] sd 8:0:0:0: [sdb] Mode Sense: 23 00 00 00
  [ 6234.179251] sd 8:0:0:0: [sdb] No Caching mode page present
  [ 6234.179256] sd 8:0:0:0: [sdb] Assuming drive cache: write through
  [ 6234.183369] sd 8:0:0:0: [sdb] No Caching mode page present
  [ 6234.183376] sd 8:0:0:0: [sdb] Assuming drive cache: write through
  [ 6234.210138]  sdb: sdb1
  [ 6234.212732] sd 8:0:0:0: [sdb] No Caching mode page present
  [ 6234.212736] sd 8:0:0:0: [sdb] Assuming drive cache: write through
  [ 6234.212740] sd 8:0:0:0: [sdb] Attached SCSI removable disk

  The permisions on the removable drive are set correctly:

  sergio@shana:/media$ ls -lah
  total 12K
  drwxr-xr-x  3 root   root   4,0K jul  5 10:20 .
  drwxr-xr-x 23 root   root   4,0K jul  3 11:01 ..
  drwx--  5 sergio sergio 4,0K dic 31  1969 DESIGNPLUS

  There is enough free space in the drive:

  sergio@shana:/media/DESIGNPLUS$ df -h
  S.ficheros Tamaño Usado  Disp Uso% Montado en
  /dev/sda2 50G  5,5G   42G  12% /
  udev 1,5G  4,0K  1,5G   1% /dev
  tmpfs579M  872K  579M   1% /run
  none 5,0M 0  5,0M   0% /run/lock
  none 1,5G  1,1M  1,5G   1% /run/shm
  /dev/sda1497M  113M  360M  24% /boot
  /dev/sda5245G  111G  122G  48% /home
  /dev/sdb11,9G  681M  1,2G  36% /media/DESIGNPLUS

  A file can be copied to the USB stick using the cp command for
  example.

  sergio@shana:~/Trash$ cp wireless.txt /media/DESIGNPLUS
  sergio@shana:~/Trash$ cd /media/DESIGNPLUS
  sergio@shana:/media/DESIGNPLUS$ ls -lah
  total 204K
  drwx-- 5 sergio sergio 4,0K jul  5 10:38 .
  drwxr-xr-x 3 root   root   4,0K jul  5 10:20 ..
  -rw-r--r-- 1 sergio sergio 117K jul  5 10:14 ._Screen Shot 2012-06-30 at 
8.50.37 AM.png
  -rw-r--r-- 1 sergio sergio  55K jun 30 08:51 Screen Shot 2012-06-30 at 
8.50.37 AM.png
  drwx-- 4 sergio sergio 4,0K jul  5 10:05 .Spotlight-V100
  drwx-- 2 sergio sergio 4,0K jul  5 10:05 .Trashes
  -rw-r--r-- 1 sergio sergio 4,0K jul  5 10:05 ._.Trashes
  -rw-r--r-- 1 sergio sergio   73 jul  5 10:38 wireless.txt

  But nautilus just dennies to copy the file claming that the
  destination is read only, when it is not.

  I tested it with two different USB sticks in two different computers
  running Ubuntu 12.04 and the same result.

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

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

[Desktop-packages] [Bug 1573296] Re: obsolete conffiles not cleaned up on upgrade

2016-12-06 Thread Aaron Peromsik

pulseaudio was working fine for me in system mode until this update hit
my machine today. Now I have no sound.

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

Title:
  obsolete conffiles not cleaned up on upgrade

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released

Bug description:
  Impact:

  When upgrading to xenial from earlier releases, some files are left on
  the user's system. They are not used, but may otherwise be mistaken
  for being used by the user if they are attempting to fix a problem.

  Regression potential:

  Low to none, as the relevant files are not used, and are being removed
  when the updated version of Pulseaudio is installed. These files are
  already removed in yakkety and later.

  Test case:

  When updating from trusty to xenial, one will note the presence of the
  below listed files on the system. Updating from pulseaudio in xenial
  or pulseaudio in trusty to what is in xenial-proposed shoudl delete
  the listed files. The /etc/init.d/pulseaudio script should also be
  unregistered.

  
  Original bug report:

  The following files are marked obsolete after the upgrade to 16.04:

   /etc/init/pulseaudio.conf 6244f8d452b29be7d17219b2db34138f obsolete
   /etc/init.d/pulseaudio df2873ee4f4673d53e3562a0de6e8aa0 obsolete
   /etc/default/pulseaudio 777f75f5521eab11c647da5c55544b1b obsolete
   /etc/bash_completion.d/pulseaudio df1f94a6b961900162bd18532c3c4c22 obsolete

  
  Those files should be cleaned up and the sysv init script properly 
deregistered.

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

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

[Desktop-packages] [Bug 1647814] [NEW] package cups-daemon 2.1.3-4 failed to install/upgrade: il sottoprocesso nuovo script pre-removal ha restituito lo stato di errore 1

2016-12-06 Thread Gregorio

Public bug reported:

Crash happened during upgrades installation.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-daemon 2.1.3-4
ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30
Uname: Linux 4.4.0-49-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
AptOrdering:
 cups-daemon: Install
 cups-daemon: Configure
 cups-core-drivers: Configure
 cups: Configure
 NULL: ConfigurePending
Architecture: amd64
CupsErrorLog:
 
Date: Tue Dec  6 19:27:50 2016
DpkgHistoryLog:
 Start-Date: 2016-12-06  19:27:48
 Commandline: apt-get install -f
 Requested-By: gtu (1000)
 Upgrade: cups-daemon:amd64 (2.1.3-4, 2.1.3-4ubuntu0.1)
ErrorMessage: il sottoprocesso nuovo script pre-removal ha restituito lo stato 
di errore 1
InstallationDate: Installed on 2016-01-24 (317 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: Acer Aspire E5-573G
Papersize: a4
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic.efi.signed 
root=UUID=9a6ce903-b4c3-460c-9a5d-26a3bc5f17b2 ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic.efi.signed 
root=UUID=9a6ce903-b4c3-460c-9a5d-26a3bc5f17b2 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15
SourcePackage: cups
Title: package cups-daemon 2.1.3-4 failed to install/upgrade: il sottoprocesso 
nuovo script pre-removal ha restituito lo stato di errore 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/25/2015
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.31
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: ZORO_BH
dmi.board.vendor: Acer
dmi.board.version: Type2 - A01 Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.31:bd09/25/2015:svnAcer:pnAspireE5-573G:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire E5-573G
dmi.product.version: V3.72
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-package third-party-packages xenial

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: il
  sottoprocesso nuovo script pre-removal ha restituito lo stato di
  errore 1

Status in cups package in Ubuntu:
  New

Bug description:
  Crash happened during upgrades installation.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30
  Uname: Linux 4.4.0-49-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  AptOrdering:
   cups-daemon: Install
   cups-daemon: Configure
   cups-core-drivers: Configure
   cups: Configure
   NULL: ConfigurePending
  Architecture: amd64
  CupsErrorLog:
   
  Date: Tue Dec  6 19:27:50 2016
  DpkgHistoryLog:
   Start-Date: 2016-12-06  19:27:48
   Commandline: apt-get install -f
   Requested-By: gtu (1000)
   Upgrade: cups-daemon:amd64 (2.1.3-4, 2.1.3-4ubuntu0.1)
  ErrorMessage: il sottoprocesso nuovo script pre-removal ha restituito lo 
stato di errore 1
  InstallationDate: Installed on 2016-01-24 (317 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Acer Aspire E5-573G
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic.efi.signed 
root=UUID=9a6ce903-b4c3-460c-9a5d-26a3bc5f17b2 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic.efi.signed 
root=UUID=9a6ce903-b4c3-460c-9a5d-26a3bc5f17b2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: il 
sottoprocesso nuovo script pre-removal ha restituito lo stato di errore 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.31
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZORO_BH
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.31:bd09/25/2015:svnAcer:pnAspireE5-573G:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-573G
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1647334] Re: datetime does not autoupdate clock based on geolocation

unity-control-center is a gui not a service, it's not started with the
session so couldn't do that job, it needs to either be the indicator-
service or unity-settings-daemon, having the indicator handling that
would be better for our convergence story...

** Package changed: unity-control-center (Ubuntu) => indicator-datetime
(Ubuntu)

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

Title:
  datetime does not autoupdate clock based on geolocation

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  See attached screenshots.

  I am currently in Spain, and unity-control-center datetime is
  configurd to automatically update the timezone based on IP
  geolocation.

  This does not work (and honestly hasn't worked for quite some time,
  well before 16.04).

  In one screenshot, you can see that my timezone is set as New York,
  and the "Automatically from the Internet" button is selected for "Set
  the time".

  In the other screenshot, you can clearly see that my geolocation shows
  that I am in Spain, but the time has NOT updated to reflect that I'm
  on a different European timezone.

  This has never worked in Ubuntu that I can recall, I always have to
  manually change the location.

  Expected Behaviour:

  Timezone is updated automatically whenever I am connected to the internet in 
a different timezone.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-10-21 (410 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NonfreeKernelModules: wl
  Package: unity-control-center 15.04.0+16.04.20160705-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Tags:  xenial
  Uname: Linux 4.4.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1647334/+subscriptions

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

[Desktop-packages] [Bug 1647809] Re: package inkscape 0.91-7ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

2016-12-06 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 inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1647809

Title:
  package inkscape 0.91-7ubuntu2 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in inkscape package in Ubuntu:
  New

Bug description:
  hi

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: inkscape 0.91-7ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Uname: Linux 4.4.0-51-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Dec  6 20:46:32 2016
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2016-09-13 (84 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: inkscape
  Title: package inkscape 0.91-7ubuntu2 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1647809] [NEW] package inkscape 0.91-7ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

2016-12-06 Thread Maks

Public bug reported:

hi

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: inkscape 0.91-7ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
Uname: Linux 4.4.0-51-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Tue Dec  6 20:46:32 2016
ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
InstallationDate: Installed on 2016-09-13 (84 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15
SourcePackage: inkscape
Title: package inkscape 0.91-7ubuntu2 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package inkscape 0.91-7ubuntu2 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in inkscape package in Ubuntu:
  New

Bug description:
  hi

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: inkscape 0.91-7ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Uname: Linux 4.4.0-51-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Dec  6 20:46:32 2016
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2016-09-13 (84 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: inkscape
  Title: package inkscape 0.91-7ubuntu2 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1051625] Re: nautilus crashed with signal 5 in _XEventsQueued()

2016-12-06 Thread kg

POTENTIAL FIX:

This got too annoying and was also happening with screen resolution
changes so I looked into it further and found this:
https://github.com/opinsys/puavo-
rules/commit/b047b8058d72daea74cfaea2923cfdcad3a2a401

After setting the dconf key org/gnome/desktop/background/draw-background
to false, the problem appears to be completely resolved. I no longer get
crashes on wallpaper change, or on screen resolution change which were
happening consistently before. Setting this key back to True and
changing screen resolution produces a crash 100% of the time when I
mouse over a desktop icon; with this key set to False, the problem does
not happen.

I note that this does not actually fix the bug itself; there appears to
be a problem to do with this setting, but perhaps it should not be being
read in the first place?

The key description in dconf-editor says "DEPRECATED: This key is
deprecated and ignored." but the default is still true, and it appears
that the key is NOT ignored and in fact leads to these crashes unless
set to false.

Hope this helps somebody fix this properly.

In the meantime anybody having this problem might want to try changing
the key (install dconf-editor, then use the Find function to search for
"draw-background" or navigate manually to the key above and setting it
to false (unticked).

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

Title:
  nautilus crashed with signal 5 in _XEventsQueued()

Status in nautilus package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed

Bug description:
  Bug report prompt appeared when printing in Libreoffice Calc. Not sure
  about the actual cause.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3
  Uname: Linux 3.5.0-14-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  Date: Mon Sep 17 00:02:19 2012
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'800x550+478+220'"
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  ProcCmdline: nautilus trash://
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: nautilus crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: Upgraded to quantal on 2012-09-08 (8 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

Re: [Desktop-packages] [Bug 1451728] Re: [master] kde-config-telepathy-accounts package install error

2016-12-06 Thread Lezsák Domonkos

Sorry for the provocation, but I think, it's neccessary.

Entschuldigung, aber Sie ist nicht im Deutschland. Sie ist auf die
Weltnetz, bekannt als WWW (auch ein English wort, bedeutet Welt-Brei Netz).
Der Site, was Sie benutzen ist ein internationales Website. Sie können zum
Beispiel an die Startseite

blicken: Es ist ein internationales Webseite, wo die Amtssprache English
ist.

Ich bin zBs. Ungarisch. Die Meisten von Uns sind aus America. Viele sind
aus Europa: Deutschland, Frankreich, Ungarn, etc.. Wer diese Bug reparieren
würde, würde warscheinlich Englisch sprechen.

Wenn Sie wollen nicht internationale, sondern Deutsche Seiten suchen, bitte
passen Sie auf die TLD
:
Es muss de sein.


Short translation:

You aren't in Germany, you are in the Internet. Most of us are American,
but many are from Europa (i'm especially Hungarian). If you wanna search
for german sites, please take care about the TLD (*.de).


2016-12-06 12:49 GMT+01:00 Bernd :

> nein, das akzeptiere ich  nicht. Die Amtssprache in Deutschland ist
> DEUTSCH.
>
> Es wir keine andere Sprache zugelassen.
>
>
> Am 06.12.2016 um 04:33 schrieb Flames_in_Paradise:
> > @ bdresler:
> >
> > Bitte akzeptiere, dass die Fehlerberichterstellung mit kleinstem
> > gemeinsamer Nenner in englischer Sprache stattfindet.
> >
> > Please accept that bug-reporting takes place in english. As a unique
> > exception I did a free translation.  – (Als einmalige, ausserordentliche
> > Ausnahme habe ich Dir den Text übersetzt - für weitere Fragen nutze doch
> > bitte einfach Ubuntuusers.de , (lokales Hilfe-Forum)).
> >
> > -> https://paste.ubuntu.com/23586350/
> >
> > @ mardy: I'm not completely familiar with SRU-updates [1], but it may
> > certainly help to subscribe a sponsor as outlined there in 3.0.5 . They
> > definetly prefer to have 'debdiff'. Thanks for caring!
> >
> > [1] https://wiki.ubuntu.com/StableReleaseUpdates
> >
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1542840).
> https://bugs.launchpad.net/bugs/1451728
>
> Title:
>   [master] kde-config-telepathy-accounts package install error
>
> Status in Kubuntu PPA:
>   Fix Released
> Status in Telepathy KDE:
>   Fix Released
> Status in kaccounts-integration package in Ubuntu:
>   In Progress
> Status in kaccounts-providers package in Ubuntu:
>   Triaged
> Status in ktp-accounts-kcm package in Ubuntu:
>   Triaged
> Status in libaccounts-glib package in Ubuntu:
>   Fix Released
> Status in kaccounts-providers source package in Wily:
>   Triaged
> Status in ktp-accounts-kcm source package in Wily:
>   Triaged
>
> Bug description:
>   Installing from Kubuntu 15.04 backports:
>
>   Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1)
> over (0.9.0-0ubuntu1) ...
>   dpkg: error processing archive /var/cache/apt/archives/kde-
> config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
> (--unpack):
>trying to overwrite '/usr/share/accounts/services/facebook-im.service',
> which is also in package account-plugin-facebook
> 0.12+15.04.20150415.1-0ubuntu1
>   dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
>
>   SRU information
>   ===
>
>   [Impact] It's not possible to install KDE and Unity in co-existence
>   because of several file conflicts: many files under
>   /usr/share/accounts/{providers,services}/ are provided by both the
>   package "kaccounts-providers" and packages build from the "account-
>   plugins" source package, for example 'account-plugin-facebook'.
>
>   [Test case] Install both kaccounts-providers and
> account-plugin-facebook: you'll get file conflicts for
> /usr/share/accounts/services/facebook-im.service and
> /usr/share/accounts/providers/facebook.provider.
>   You might get other conflicts as well, but those are due to bug 1565772
> (also nominated for SRU).
>
>   [Regression potential] Minimal: the changed packages belong to the
>   default KDE installation, and have already landed in Yakkety. Things
>   appear to be working fine there: account creation is still possible
>   under KDE, even after changing the file paths as per this fix.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+subscriptions
>

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

Title:
  [master] kde-config-telepathy-accounts package install error

Status in Kubuntu PPA:
  Fix Released
Status in Telepathy KDE:
  Fix Released
Status in kaccounts-integration package in Ubuntu:
  In Progress
Status in kaccounts-providers

[Desktop-packages] [Bug 1516713] Re: gtk3 overlay scrollbars consistently show wrong behaviour

that's an upstream gtk issue and should probably be reported on
bugzilla.gnome.org

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

Title:
  gtk3 overlay scrollbars consistently show wrong behaviour

Status in gedit package in Ubuntu:
  Confirmed

Bug description:
  This is a general bug in GTK3 overlay scrolling (the new kind, not the
  old "overlay scrollbars" feature).

  When a window needs both horizontal and vertical scrolling the actual
  accessible content is reduced by the size of the scrollbars that show
  up when you move the mouse into the window.  Normally the scrollbars
  are logically outside the scrollable area and that whole are can be
  scrolled into view. With overlay scrolling this is not the case
  because the scrollbars OVERLAY the scrollable content, effectively
  making part of that content unreachable.

  In case of a text-file opened in GEDIT this means that the last text-
  line will be covered by the horizontal scrollbar and you can not
  scroll further down to scroll it above the horizontal scroll bar (see
  the attached screenshot).

  The fix would obviously be to extend the logical scroll range of both
  scrollbars with the width of the other scrollbar if that exists.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gedit 3.10.4-0ubuntu13
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov 16 17:59:46 2015
  ExecutablePath: /usr/bin/gedit
  InstallationDate: Installed on 2015-11-04 (12 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1646547] Re: nvidia-367.57 with kernel 4.4.0-51-generic won't boot

2016-12-06 Thread Brendan

Is there a specific time in boot I should be holding shift? I have tried
holding as soon as I start seeing POST messaging, and also tried once
the GRUB menu came up.

But it still doesn't get me to the screen to enter my disk encryption
password.

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

Title:
  nvidia-367.57 with kernel 4.4.0-51-generic won't boot

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

Bug description:
  Pretty much identical to bug 1642400 and bug 1638990 except that this
  behavior also happens with the most recent Xenial kernel,
  4.4.0-51-generic.

  If I boot into recovery mode on 4.4.0-51-generic, mount the filesystem as 
read/write, start networking, the resume normal boot, I can finally get into my 
window manager. But if I reboot and let
  GRUB handle boot normally, it doesn't even let me enter my encryption 
passphrase. Just sits at a blinking cursor.

  Switching back to nouveau works, but after reinstalling 367.57, the
  behavior returns and the aforementioned steps have to be followed.

  Ubuntu 4.4.0-51.72-generic 4.4.30

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

  :~$ apt-cache policy linux-image-4.4.0-51-generic
  linux-image-4.4.0-51-generic:
Installed: 4.4.0-51.72
Candidate: 4.4.0-51.72
Version table:
   *** 4.4.0-51.72 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  I expect that I should be able to boot normally with nvidia drivers,
  without any special steps to boot. But instead, I just get a blinking
  cursor before I can even unlock my encrypted drive.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-51-generic 4.4.0-51.72
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Uname: Linux 4.4.0-51-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lost   4789 F pulseaudio
   /dev/snd/controlC0:  lost   4789 F pulseaudio
   /dev/snd/controlC2:  lost   4789 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Dec  1 10:48:04 2016
  HibernationDevice: RESUME=UUID=cf59c168-54d0-45b9-b633-240bd76bbaa6
  InstallationDate: Installed on 2016-11-01 (29 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 11361Q0
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-51-generic 
root=/dev/mapper/xubuntu--vg-root ro recovery nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-51-generic N/A
   linux-backports-modules-4.4.0-51-generic  N/A
   linux-firmware1.157.5
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A3KT57AUS
  dmi.board.name: LENOVO
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: 573921
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvrA3KT57AUS:bd09/29/2016:svnLENOVO:pn11361Q0:pvrThinkStationC30:rvnLENOVO:rnLENOVO:rvrNODPK:cvnLENOVO:ct7:cvrNONE:
  dmi.product.name: 11361Q0
  dmi.product.version: ThinkStation C30
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1647217] Re: Nautilus “Open with …” context menu gone on upgrade to yakkety

The nautilus update is bringing changes and issue indeed, but we can't
really stay on an old unmaintained version for ever especially when some
users and other desktop variants would like to get the update. Having
the old version often lead to new bugs when e.g gtk is updated.

That said about that specific issue we would probably consider a patch
if it's not too complex/difficult to maintain over updates, but it might
be worth trying to convince upstream as well that the old behaviour was
better, the current maintainers are quite open to comments

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

Title:
  Nautilus “Open with …” context menu gone on upgrade to yakkety

Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Release:  16.10
  Package:nautilus, 1:3.20.3-1ubuntu3.1

  Expected behaviour:

  1. Open Files
  2. Right-click on icon, move to "Open with …", and pick suitable app from an 
immediate list
  3. File opens in selected application.

  This was standard behaviour on 16.04, and is expected behaviour from
  Windows and Mac OS.

  Actual behaviour:

  1. Open Files
  2. Right-click on icon, note lack of "Open with …" option, and select "Open 
With Other Application"
  3. "Select Application" window opens instead of immediate list. Window 
contains long list
  4. Scroll down list until application appears, select it, and file opens in 
selected application.

  This is a usability regression. No explanation is given why this is
  gone, or how to recover the (expected, standard, rational) previous
  behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6
  Uname: Linux 4.8.0-28-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Dec  4 17:01:37 2016
  InstallationDate: Installed on 2015-03-08 (637 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to yakkety on 2016-12-02 (2 days ago)
  usr_lib_nautilus:
   dropbox2015.10.28
   gnome-terminal 3.20.2-1ubuntu5

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

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

[Desktop-packages] [Bug 1643711] Re: Some autostart .desktops are needlessly? being delayed for 1-2 min after login

interesting, do you have any non-UI packages removed in that list?
things that have to do with dbus, backends, systemd, etc?

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

Title:
  Some autostart .desktops are needlessly? being delayed for 1-2 min
  after login

Status in Unity8 PolicyKit Agent:
  New
Status in Unity 8:
  New
Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  Test Case 1:
  login, try any action requiring polkit, ex. would be unlocking user accounts 
or starting synaptic from it's .desktop
  What happens: nothing

  Test case 2:
  log in to a machine using wireless (maybe also wired..
  What happens: there is no indicator for network

  In both cases after 1-2 min. policykit becomes active & the network
  indicator shows up.

  If I copy /etc/xdg/autostart/polkit-gnome-authentication-
  agent-1.desktop' & /etc/xdg/autostart/nm-applet.desktop to my desktop,
  mark as executable & d. click on both directly after login then
  policykit becomes active & the network icon shows up.

  Could be others?, for example logging out shortly after logging in
  generally fails to do anything

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ubuntu-session 3.22.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-1.2-generic 4.9.0-rc5
  Uname: Linux 4.9.0-1-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov 21 17:20:06 2016
  InstallationDate: Installed on 2016-11-09 (12 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161106)
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-unity8/+bug/1643711/+subscriptions

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

[Desktop-packages] [Bug 329610] Re: clicking Eject disk button in nautilus twice in a row ejects disk and displays error message

Could you try to see if that's still an issue with current versions?

** Changed in: nautilus (Ubuntu)
   Status: Triaged => Incomplete

** Changed in: nautilus (Ubuntu)
 Assignee: Ubuntu Desktop Bugs (desktop-bugs) => (unassigned)

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

Title:
  clicking Eject disk button in nautilus twice in a row ejects disk and
  displays error message

Status in Nautilus:
  Incomplete
Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: nautilus

  Clicking eject from the Nautilus sidebar on a mounted cd displays a
  number of errors equal to the number of times clicked - 1, and
  displays the disk.

  Can this be changed to ignore clicks for the next 3 seconds after
  the first, or something similar?

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

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

[Desktop-packages] [Bug 1476088] Re: Rhythmbox can't resume play on (m4a) podcast

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

** Changed in: rhythmbox (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Rhythmbox can't resume play on (m4a) podcast

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  I'm subscribed to a number of podcasts that are hosted and served by
  Apple iTunes. As such, the file format is m4a, which may be the root
  of this problem.

  Once the podcast is playing, I'll pause playback using either the
  controls that appear when clicking the volume control in the Unity
  system tray, or by just using the regular playback controls in
  Rhythmbox.

  To resume playback I press the play button, but play does not resume.
  I must move the scrubber to a new location before playback will
  resume.

  Ubuntu 14.04.2 LTS

  rhythmbox:
Installed: 3.0.2-0ubuntu2
Candidate: 3.0.2-0ubuntu2
Version table:
   *** 3.0.2-0ubuntu2 0
  500 http://au.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.0.2-0ubuntu1 0
  500 http://au.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

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

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

[Desktop-packages] [Bug 1647133] Re: dns=dnsmasq does not work any more

2016-12-06 Thread Harry

Martin,

OK, here goes:

cat /etc/resolv.conf

# Generated by NetworkManager
search dhcp.inet.fi
nameserver 127.0.1.1

cat /etc/NetworkManager/NetworkManager.conf
[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=false

journalctl -u NetworkManager.service -u systemd-resolved.service -b >
/tmp/nm.log

The tmp file (nm2.log) is attached.
There is one error in the log:
"Error: failed to open /run/network/ifstate"

** Attachment added: "nm2.log"

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647133/+attachment/4788208/+files/nm2.log

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

Title:
dns=dnsmasq does not work any more

Status in network-manager package in Ubuntu:
Triaged

Bug description:
Network-manager will make my network connection immediately lost after
updating to the newest version 1.4.2-2ubuntu4.
However, downgrading to the previous version 1.4.2-2ubuntu3 the network
connection is back again and fine. If, with this version, I remove the file
(link) /etc/resolv.conf the network is broken again. Rebooting solves this, as
network-manager creates a new resolv.conf file.

The newest version 1.4.2-2ubuntu4 also creates the very same kind of
file, but no network.

I have the latest (Gnome-shell DE) updates installed and of course all
packages that network-manager depends on. But not the ones it only recommends
or suggests.
Should I have resolvconf installed? I think not, as isc-dhcp-client only
suggests it.

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

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

** Package changed: unity (Ubuntu) => network-manager-applet (Ubuntu)

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

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

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

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

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

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

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

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

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

You have been subscribed to a public bug:

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

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

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

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial
-- 
Wifi-SSID List vanishes after a few wakeups;LAN icons instead of wifi a
https://bugs.launchpad.net/bugs/1647550
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to network-manager-applet in Ubuntu.

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

[Desktop-packages] [Bug 1647706] Re: Totem crashes with segmentation fault and Clutter error

Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, your crash report is either missing or
challenging to deal with as a ".crash" file. Please follow these
instructions to have apport report a new bug about your crash that can
be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable
apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the 
crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 
'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is 
the crash you would like to report. If you get an error that you aren't allowed 
to access this report you will have to file it with 'sudo ubuntu-bug 
/var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will
automatically open a new bug report which can then dealt with more
efficiently. Thanks in advance for your cooperation and understanding.

** Changed in: totem (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  Totem crashes with segmentation fault and Clutter error

Status in totem package in Ubuntu:
  Invalid

Bug description:
  On Ubuntu 16.10, Totem crashes immediately after startup with the
  following error:

  ** (totem:29792): WARNING **: Error retrieving accessibility bus
  address: org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.a11y.Bus was not provided by any .service files

  (totem:29792): Clutter-CRITICAL **: Unable to initialize Clutter:
  Unable to initialize the Clutter backend

  (totem:29792): Totem-WARNING **: gtk-clutter failed to initialise,
  expect problems from here on.

  (totem:29792): Clutter-CRITICAL **: Unable to initialize Clutter:
  Unable to initialize the Clutter backend

  (totem:29792): Clutter-WARNING **: Missing Cogl context: was Clutter 
correctly initialized?
  Segmentation fault (core dumped)

  
  I use the package “nvidia-304” as my video driver.

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

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

[Desktop-packages] [Bug 1647753] Re: "Unable to add the buddy 1 for an unknown reason" warning

2016-12-06 Thread Ubuntu Foundations Team Bug Bot

The attachment "pidgin-remove-icq-error-message.patch" seems to be a
patch.  If it isn't, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  "Unable to add the buddy 1 for an unknown reason" warning

Status in pidgin package in Ubuntu:
  New

Bug description:
  OS: Ubuntu (MATE) 16.04

  Each time I login into pidgin I get this exact warning: "Unable to add
  the buddy 1 for an unknown reason."

  I'm using ICQ only. This warning appears only once each time pidgin
  starts. Other than that warning Pidgin works fine and I have no
  issues. During the last years I've been using a radical method to get
  rid of that message: I'm removing the message entirely from
  libpurple/protocols/oscar/oscar.c (see attached patch).

  I thought that maybe you can add a little checkbox to the window to
  not make that message appear again? Or something else like an
  environment variable or a dotfile that I need touch(1) which silences
  it at my will.

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

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

[Desktop-packages] [Bug 1647782] Re: unity-settings-daemon crashed with SIGSEGV in ffi_call_unix64()

2016-12-06 Thread Apport retracing service

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  unity-settings-daemon crashed with SIGSEGV in ffi_call_unix64()

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

Bug description:
  Upon bootup.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity-settings-daemon 15.04.1+16.10.20161003-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-29.31-generic 4.8.11
  Uname: Linux 4.8.0-29-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Mon Dec  5 22:38:49 2016
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2015-07-19 (505 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  ProcEnviron:
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f40bd2954d2:mov0x10(%rax),%rdi
   PC (0x7f40bd2954d2) ok
   source "0x10(%rax)" (0x558fa7010108) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   ?? () from /usr/lib/unity-settings-daemon-1.0/libremote-display.so
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: unity-settings-daemon crashed with SIGSEGV in ffi_call_unix64()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 411688] Re: pulseaudio floods network with multicast packets

2016-12-06 Thread Anton Bochkarev

** Changed in: pulseaudio (Arch Linux)
   Importance: Undecided => Unknown

** Changed in: pulseaudio (Arch Linux)
   Status: New => Unknown

** Changed in: pulseaudio (Arch Linux)
 Remote watch: None => freedesktop.org Bugzilla #44777

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

Title:
  pulseaudio floods network with multicast packets

Status in PulseAudio:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Arch Linux:
  Unknown
Status in pulseaudio package in Debian:
  Fix Released

Bug description:
  Binary package hint: pulseaudio

  Since a karmic update last week, when pulseaudio is running it floods
  the network with multicast packets, to the point where the wireless
  interface I'm using is so flooded that no other network traffic can be
  transfered.

  Here is a snippet of tcpdump -i wlan 0 -n:
  ---8<---
  01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d0f 4000 0111 2d6d 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e
0x0020:  0071 a980 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d10 4000 0111 2d6c 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f
0x0020:  0071 aac0 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d11 4000 0111 2d6b 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f774 800a ee90
0x0020:  0071 ac00 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d12 4000 0111 2d6a 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f633 800a ee91
0x0020:  0071 ad40 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d13 4000 0111 2d69 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f4f2 800a ee92
0x0020:  0071 ae80 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d14 4000 0111 2d68 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f3b1 800a ee93
0x0020:  0071 afc0 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d15 4000 0111 2d67 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f270 800a ee94
0x0020:  0071 b100 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d16 4000 0111 2d66 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f12f 800a ee95
0x0020:  0071 b240 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.590645 IP (tos 0x10, ttl 1, id 23831, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d17 4000 0111 2d65 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 efee 800a ee96
0x0020:  0071 b380 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.605081 IP (tos 0x10, ttl 1, id 23832, offset 0, flags [DF], proto 
UDP (17),

[Desktop-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)

2016-12-06 Thread Jim Hodapp

Reply back here if anything like this comes up again and we can discuss
re-opening this bug.

** Changed in: media-hub (Ubuntu)
   Status: Incomplete => Invalid

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

** Changed in: qtmultimedia-opensource-src (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  No sound notification for new SMS (Ubuntu Touch)

Status in Canonical System Image:
  Fix Released
Status in indicator-sound package in Ubuntu:
  Invalid
Status in media-hub package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Invalid
Status in qtmultimedia-opensource-src package in Ubuntu:
  Invalid
Status in telephony-service package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  I noticed for last 2-3 days there is no sound notification for a new
  SMS, but there's a blinking green LED notification. Also in the
  indicator menu the envelope icon turns green and the new SMS is listed
  as usual. Things are working alright for Telegram, Gmail etc.
  (sound+LED+indicator menu).

  Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9)

  UPDATE: Screenshots get silent too.

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

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

[Desktop-packages] [Bug 1647780] [NEW] [XPS 8900, Realtek ALC3861, Green Headphone Out, Front] No sound at all

2016-12-06 Thread Todd

Public bug reported:

Sound does not work for any line or headphone out.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  teshler8754 F pulseaudio
 /dev/snd/controlC0:  teshler8754 F pulseaudio
CurrentDesktop: Unity
Date: Tue Dec  6 10:59:00 2016
InstallationDate: Installed on 2016-07-25 (133 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  teshler8754 F pulseaudio
 /dev/snd/controlC0:  teshler8754 F pulseaudio
Symptom_Jack: Green Headphone Out, Front
Symptom_Type: No sound at all
Title: [XPS 8900, Realtek ALC3861, Green Headphone Out, Front] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/20/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.1.3
dmi.board.name: 0XJ8C4
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.3:bd01/20/2016:svnDellInc.:pnXPS8900:pvr:rvnDellInc.:rn0XJ8C4:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.name: XPS 8900
dmi.sys.vendor: Dell Inc.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  [XPS 8900, Realtek ALC3861, Green Headphone Out, Front] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Sound does not work for any line or headphone out.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  teshler8754 F pulseaudio
   /dev/snd/controlC0:  teshler8754 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Dec  6 10:59:00 2016
  InstallationDate: Installed on 2016-07-25 (133 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  teshler8754 F pulseaudio
   /dev/snd/controlC0:  teshler8754 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [XPS 8900, Realtek ALC3861, Green Headphone Out, Front] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.3
  dmi.board.name: 0XJ8C4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.3:bd01/20/2016:svnDellInc.:pnXPS8900:pvr:rvnDellInc.:rn0XJ8C4:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: XPS 8900
  dmi.sys.vendor: Dell Inc.

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

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

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

2016-12-06 Thread FRLinux

Affected by the same issue, downgrading drivers worked.

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Confirmed

Bug description:
  Ubuntu 16.04 LTS

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

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

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

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

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

  See also bug 1634802

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

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

[Desktop-packages] [Bug 1451728] Re: [master] kde-config-telepathy-accounts package install error

2016-12-06 Thread Flames_in_Paradise

** Changed in: kubuntu-ppa
 Assignee: Greg (gcstatter) => (unassigned)

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

Title:
  [master] kde-config-telepathy-accounts package install error

Status in Kubuntu PPA:
  Fix Released
Status in Telepathy KDE:
  Fix Released
Status in kaccounts-integration package in Ubuntu:
  In Progress
Status in kaccounts-providers package in Ubuntu:
  Triaged
Status in ktp-accounts-kcm package in Ubuntu:
  Triaged
Status in libaccounts-glib package in Ubuntu:
  Fix Released
Status in kaccounts-providers source package in Wily:
  Triaged
Status in ktp-accounts-kcm source package in Wily:
  Triaged

Bug description:
  Installing from Kubuntu 15.04 backports:

  Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) 
over (0.9.0-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/services/facebook-im.service', 
which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

  SRU information
  ===

  [Impact] It's not possible to install KDE and Unity in co-existence
  because of several file conflicts: many files under
  /usr/share/accounts/{providers,services}/ are provided by both the
  package "kaccounts-providers" and packages build from the "account-
  plugins" source package, for example 'account-plugin-facebook'.

  [Test case] Install both kaccounts-providers and account-plugin-facebook: 
you'll get file conflicts for /usr/share/accounts/services/facebook-im.service 
and /usr/share/accounts/providers/facebook.provider.
  You might get other conflicts as well, but those are due to bug 1565772 (also 
nominated for SRU).

  [Regression potential] Minimal: the changed packages belong to the
  default KDE installation, and have already landed in Yakkety. Things
  appear to be working fine there: account creation is still possible
  under KDE, even after changing the file paths as per this fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+subscriptions

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

[Desktop-packages] [Bug 1647768] Re: NVidia card not properly initialized

2016-12-06 Thread Wolf Rogner

** Attachment added: "syslog.1"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1647768/+attachment/4788152/+files/syslog.1

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

Title:
  NVidia card not properly initialized

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

Bug description:
  NVidia card not properly initialized after reboot.

  After analyzing log files it seems that when updating the color
  profile, garbage is written to the syslog and the update process
  fails.

  Several reboots later, the boot process continues and completes.

  A workaround that seems to work effectively:
  boot into recovery and continue the boot without any further steps.
  (sometimes that has to be selected twice, the first time, the procedure 
returns)

  Maybe a similar bug as #1643997 (not quite sure from the description
  there)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nvidia-367 367.57-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec  6 16:23:57 2016
  InstallationDate: Installed on 2016-10-22 (45 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: nvidia-graphics-drivers-367
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia-367_hybrid.conf: [deleted]

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

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

[Desktop-packages] [Bug 1647768] [NEW] NVidia card not properly initialized

2016-12-06 Thread Wolf Rogner

Public bug reported:

NVidia card not properly initialized after reboot.

After analyzing log files it seems that when updating the color profile,
garbage is written to the syslog and the update process fails.

Several reboots later, the boot process continues and completes.

A workaround that seems to work effectively:
boot into recovery and continue the boot without any further steps.
(sometimes that has to be selected twice, the first time, the procedure returns)

Maybe a similar bug as #1643997 (not quite sure from the description
there)

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: nvidia-367 367.57-0ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
Uname: Linux 4.8.0-30-generic x86_64
NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Dec  6 16:23:57 2016
InstallationDate: Installed on 2016-10-22 (45 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: nvidia-graphics-drivers-367
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.modprobe.d.nvidia-367_hybrid.conf: [deleted]

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


** Tags: amd64 apport-bug yakkety

** Attachment added: "syslog"
   https://bugs.launchpad.net/bugs/1647768/+attachment/4788148/+files/syslog

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

Title:
  NVidia card not properly initialized

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

Bug description:
  NVidia card not properly initialized after reboot.

  After analyzing log files it seems that when updating the color
  profile, garbage is written to the syslog and the update process
  fails.

  Several reboots later, the boot process continues and completes.

  A workaround that seems to work effectively:
  boot into recovery and continue the boot without any further steps.
  (sometimes that has to be selected twice, the first time, the procedure 
returns)

  Maybe a similar bug as #1643997 (not quite sure from the description
  there)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nvidia-367 367.57-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec  6 16:23:57 2016
  InstallationDate: Installed on 2016-10-22 (45 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: nvidia-graphics-drivers-367
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia-367_hybrid.conf: [deleted]

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

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

[Desktop-packages] [Bug 1647753] [NEW] "Unable to add the buddy 1 for an unknown reason" warning

2016-12-06 Thread djcj

Public bug reported:

OS: Ubuntu (MATE) 16.04

Each time I login into pidgin I get this exact warning: "Unable to add
the buddy 1 for an unknown reason."

I'm using ICQ only. This warning appears only once each time pidgin
starts. Other than that warning Pidgin works fine and I have no issues.
During the last years I've been using a radical method to get rid of
that message: I'm removing the message entirely from
libpurple/protocols/oscar/oscar.c (see attached patch).

I thought that maybe you can add a little checkbox to the window to not
make that message appear again? Or something else like an environment
variable or a dotfile that I need touch(1) which silences it at my will.

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

** Tags: icq

** Patch added: "pidgin-remove-icq-error-message.patch"

https://bugs.launchpad.net/bugs/1647753/+attachment/4788142/+files/pidgin-remove-icq-error-message.patch

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

Title:
"Unable to add the buddy 1 for an unknown reason" warning

Status in pidgin package in Ubuntu:
New

Bug description:
OS: Ubuntu (MATE) 16.04

Each time I login into pidgin I get this exact warning: "Unable to add
the buddy 1 for an unknown reason."

I'm using ICQ only. This warning appears only once each time pidgin
starts. Other than that warning Pidgin works fine and I have no
issues. During the last years I've been using a radical method to get
rid of that message: I'm removing the message entirely from
libpurple/protocols/oscar/oscar.c (see attached patch).

I thought that maybe you can add a little checkbox to the window to
not make that message appear again? Or something else like an
environment variable or a dotfile that I need touch(1) which silences
it at my will.

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

[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth

2016-12-06 Thread Jeremy LaCroix

This is working for me now. When I import into Network Manager, it
literally tells me which line is the problem now, and whatever line that
is, I comment it out and it works. Before, it would just tell me that
there was an issue importing but it wasn't specific. But at least now,
Network Manager helps me figure out the issue. I recently switched to
Ubuntu GNOME, so I'm not sure if there's something specific with the
GNOME implementation that displays specific errors, or if Network
Manager has changed. At least it's working for me now, albeit with
manual intervention being required.

In my opinion, the real issue at this point is that even though
commenting out some lines helps, each line is valid and should be
accepted. If I export an .ovpn file and use it via the command line, it
works without issue (even without commenting out anything). In my view,
if the config file is valid enough for OpenVPN itself, it should surely
be valid for Network Manager. Perhaps the OpenVPN spec has updated and
Network Manager hasn't been updated to match?

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

Title:
  unable to import config with inlined ca, cert, key or tls-auth

Status in NetworkManager-OpenVPN:
  Fix Released
Status in network-manager-openvpn package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: network-manager-openvpn-gnome

  So a client of mine runs an OpenVPN setup. It exported a client.ovpn
  file but it fails to completely import this file using the network-
  manager (gnome) on Ubuntu 10.04.

  When I import the file, it gives me the name ("client") and gateway
  ("vpn.example.org") on the initial screen. No other fields are
  populated even though the client.ovpn file also includes a user
  certificate, server certifikate and a private key.

  When I go to advanced, some (most) of the settings obviously seem to
  import correct, others not at all. E.g. none of the TLS settings (key
  and key direction) are imported.

  From what I understand I should be able to use this without any
  additional settings.

  The following software is installed through aptitude:

   * openvpn (2.1.0)
   * openvpn-blacklist
   * network-manager-openvpn
   * network-manager-openvpn-gnome

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

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

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

2016-12-06 Thread LocutusOfBorg

** Summary changed:

- Build and distribute intel-virtual-output
+ [SRU] Build and distribute intel-virtual-output

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

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

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

Bug description:
  [Impact]

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

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

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

  [Test Case]

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

  [Regression Potential]

  Absolutely none.

  [Other Info]

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

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

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

[Desktop-packages] [Bug 1647727] [NEW] Zooming the icon view in Nautilus also resized desktop icons

2016-12-06 Thread Nikke

Public bug reported:

Steps to reproduce:
1. Open a Nautilus window
2. Set to Icon view (not list)
3. Change icon size, either by Ctrl-scroll wheel or by the icon size slider

Observed behaviour
1. Icon size changes in the Nautilus window (expected)
2. Icon size changes on the desktop (NOT expected)

The icon size does NOT change in other open nautilus windows, but
zooming any nautilus windows in icon view mode also changes the desktop
icon size.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: nautilus 1:3.20.3-1ubuntu3.1
ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
Uname: Linux 4.8.0-30-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Dec  6 14:40:10 2016
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'geometry' b"'1405x868+1985+24'"
 b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'"
 b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'larger'"
InstallationDate: Installed on 2016-11-23 (13 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

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

Title:
  Zooming the icon view in Nautilus also resized desktop icons

Status in nautilus package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Open a Nautilus window
  2. Set to Icon view (not list)
  3. Change icon size, either by Ctrl-scroll wheel or by the icon size slider

  Observed behaviour
  1. Icon size changes in the Nautilus window (expected)
  2. Icon size changes on the desktop (NOT expected)

  The icon size does NOT change in other open nautilus windows, but
  zooming any nautilus windows in icon view mode also changes the
  desktop icon size.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec  6 14:40:10 2016
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'1405x868+1985+24'"
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'"
   b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'larger'"
  InstallationDate: Installed on 2016-11-23 (13 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  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/ubuntu/+source/nautilus/+bug/1647727/+subscriptions

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

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

** Branch linked: lp:~mardy/account-plugins/webkit-files-1565772

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

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

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

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

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

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

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


  SRU information
  ===

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

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

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

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

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

[Desktop-packages] [Bug 1647721] [NEW] unavailable to delete any message

2016-12-06 Thread Morimoto Kenji

Public bug reported:

Description:Ubuntu 16.10
Release:16.10

thunderbird:
  Installed: 1:45.5.1+build1-0ubuntu0.16.10.1
  Candidate: 1:45.5.1+build1-0ubuntu0.16.10.1
  Version table:
 *** 1:45.5.1+build1-0ubuntu0.16.10.1 500
500 http://jp.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu yakkety-security/main amd64 
Packages
100 /var/lib/dpkg/status


After updating to this version, delete icon in each messages, the delete item 
in pull down menu and the item in right click to any messages are not works at 
all without any errors or warnings.

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

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

Title:
  unavailable to delete any message

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 16.10
  Release:  16.10

  thunderbird:
Installed: 1:45.5.1+build1-0ubuntu0.16.10.1
Candidate: 1:45.5.1+build1-0ubuntu0.16.10.1
Version table:
   *** 1:45.5.1+build1-0ubuntu0.16.10.1 500
  500 http://jp.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu yakkety-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  
  After updating to this version, delete icon in each messages, the delete item 
in pull down menu and the item in right click to any messages are not works at 
all without any errors or warnings.

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

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

[Desktop-packages] [Bug 1640741] Re: ubuntu 17.04 gnome-software install button not working

2016-12-06 Thread Iain Lane

There was an extremely suspicious critical being output when clicking
the button. That was the way in to fixing this bug.

Not uploading right away; g-s is stuck in proposed independently anyway.

https://git.gnome.org/browse/gnome-
software/commit/?id=acc4a0f7b02dfe61534c2de07900d4f81dcb4e1c

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

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

Title:
  ubuntu 17.04 gnome-software install button not working

Status in Ubuntu GNOME:
  Confirmed
Status in gnome-software package in Ubuntu:
  Fix Committed

Bug description:
  on ubuntu 17.04 gnome-software install button does nothing.
  try with different applications: UFRaw, Shutter, Entangle ...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-software 3.22.2+git20161108.0.a58dfc7-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov 10 11:08:48 2016
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2016-11-06 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161106)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth

2016-12-06 Thread D

I'm sorry, but im a newbie, but how does this fix get into the ubuntu
versions? Do we have to wait until network-manager-openvpn (Ubuntu) gets
assigned?

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

Title:
  unable to import config with inlined ca, cert, key or tls-auth

Status in NetworkManager-OpenVPN:
  Fix Released
Status in network-manager-openvpn package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: network-manager-openvpn-gnome

  So a client of mine runs an OpenVPN setup. It exported a client.ovpn
  file but it fails to completely import this file using the network-
  manager (gnome) on Ubuntu 10.04.

  When I import the file, it gives me the name ("client") and gateway
  ("vpn.example.org") on the initial screen. No other fields are
  populated even though the client.ovpn file also includes a user
  certificate, server certifikate and a private key.

  When I go to advanced, some (most) of the settings obviously seem to
  import correct, others not at all. E.g. none of the TLS settings (key
  and key direction) are imported.

  From what I understand I should be able to use this without any
  additional settings.

  The following software is installed through aptitude:

   * openvpn (2.1.0)
   * openvpn-blacklist
   * network-manager-openvpn
   * network-manager-openvpn-gnome

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

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

[Desktop-packages] [Bug 1647706] [NEW] Totem crashes with segmentation fault and Clutter error

2016-12-06 Thread Torsten Bronger

Public bug reported:

On Ubuntu 16.10, Totem crashes immediately after startup with the
following error:

** (totem:29792): WARNING **: Error retrieving accessibility bus
address: org.freedesktop.DBus.Error.ServiceUnknown: The name
org.a11y.Bus was not provided by any .service files

(totem:29792): Clutter-CRITICAL **: Unable to initialize Clutter: Unable
to initialize the Clutter backend

(totem:29792): Totem-WARNING **: gtk-clutter failed to initialise,
expect problems from here on.

(totem:29792): Clutter-CRITICAL **: Unable to initialize Clutter: Unable
to initialize the Clutter backend

(totem:29792): Clutter-WARNING **: Missing Cogl context: was Clutter correctly 
initialized?
Segmentation fault (core dumped)


I use the package “nvidia-304” as my video driver.

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

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

Title:
  Totem crashes with segmentation fault and Clutter error

Status in totem package in Ubuntu:
  New

Bug description:
  On Ubuntu 16.10, Totem crashes immediately after startup with the
  following error:

  ** (totem:29792): WARNING **: Error retrieving accessibility bus
  address: org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.a11y.Bus was not provided by any .service files

  (totem:29792): Clutter-CRITICAL **: Unable to initialize Clutter:
  Unable to initialize the Clutter backend

  (totem:29792): Totem-WARNING **: gtk-clutter failed to initialise,
  expect problems from here on.

  (totem:29792): Clutter-CRITICAL **: Unable to initialize Clutter:
  Unable to initialize the Clutter backend

  (totem:29792): Clutter-WARNING **: Missing Cogl context: was Clutter 
correctly initialized?
  Segmentation fault (core dumped)

  
  I use the package “nvidia-304” as my video driver.

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

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

Re: [Desktop-packages] [Bug 1451728] Re: [master] kde-config-telepathy-accounts package install error

2016-12-06 Thread Bernd

nein, das akzeptiere ich  nicht. Die Amtssprache in Deutschland ist
DEUTSCH.

Es wir keine andere Sprache zugelassen.


Am 06.12.2016 um 04:33 schrieb Flames_in_Paradise:
> @ bdresler:
>
> Bitte akzeptiere, dass die Fehlerberichterstellung mit kleinstem
> gemeinsamer Nenner in englischer Sprache stattfindet.
>
> Please accept that bug-reporting takes place in english. As a unique
> exception I did a free translation.  – (Als einmalige, ausserordentliche
> Ausnahme habe ich Dir den Text übersetzt - für weitere Fragen nutze doch
> bitte einfach Ubuntuusers.de , (lokales Hilfe-Forum)).
>
> -> https://paste.ubuntu.com/23586350/
>
> @ mardy: I'm not completely familiar with SRU-updates [1], but it may
> certainly help to subscribe a sponsor as outlined there in 3.0.5 . They
> definetly prefer to have 'debdiff'. Thanks for caring!
>
> [1] https://wiki.ubuntu.com/StableReleaseUpdates
>

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

Title:
  [master] kde-config-telepathy-accounts package install error

Status in Kubuntu PPA:
  Fix Released
Status in Telepathy KDE:
  Fix Released
Status in kaccounts-integration package in Ubuntu:
  In Progress
Status in kaccounts-providers package in Ubuntu:
  Triaged
Status in ktp-accounts-kcm package in Ubuntu:
  Triaged
Status in libaccounts-glib package in Ubuntu:
  Fix Released
Status in kaccounts-providers source package in Wily:
  Triaged
Status in ktp-accounts-kcm source package in Wily:
  Triaged

Bug description:
  Installing from Kubuntu 15.04 backports:

  Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) 
over (0.9.0-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/services/facebook-im.service', 
which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

  SRU information
  ===

  [Impact] It's not possible to install KDE and Unity in co-existence
  because of several file conflicts: many files under
  /usr/share/accounts/{providers,services}/ are provided by both the
  package "kaccounts-providers" and packages build from the "account-
  plugins" source package, for example 'account-plugin-facebook'.

  [Test case] Install both kaccounts-providers and account-plugin-facebook: 
you'll get file conflicts for /usr/share/accounts/services/facebook-im.service 
and /usr/share/accounts/providers/facebook.provider.
  You might get other conflicts as well, but those are due to bug 1565772 (also 
nominated for SRU).

  [Regression potential] Minimal: the changed packages belong to the
  default KDE installation, and have already landed in Yakkety. Things
  appear to be working fine there: account creation is still possible
  under KDE, even after changing the file paths as per this fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+subscriptions

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

[Desktop-packages] [Bug 1647133] Re: dns=dnsmasq does not work any more

2016-12-06 Thread Martin Pitt

OK, thanks. I'm afraid I need the NM log and /etc/resolv.conf with NM
1.4.2-2ubuntu4 without "dns=dnsmasq".

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

Title:
  dns=dnsmasq does not work any more

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Network-manager will make my network connection immediately lost after 
updating to the newest version 1.4.2-2ubuntu4.
  However, downgrading to the previous version 1.4.2-2ubuntu3 the network 
connection is back again and fine. If, with this version, I remove the file 
(link) /etc/resolv.conf the network is broken again. Rebooting solves this, as 
network-manager creates a new resolv.conf file.

  The newest version 1.4.2-2ubuntu4 also creates the very same kind of
  file, but no network.

  I have the latest (Gnome-shell DE) updates installed and of course all 
packages that network-manager depends on. But not the ones it only recommends 
or suggests.
  Should I have resolvconf installed? I think not, as isc-dhcp-client only 
suggests it.

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

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

[Desktop-packages] [Bug 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while

2016-12-06 Thread Mark

>From @archenroot's posts I tried the following settings which does seem
to have got the speakers and headphones working properly (no mic as yet
but I'll have a play with that later)

added the following to /etc/modprobe.d/alsa.conf
options snd-hda-intel single_cmd=1
options snd-hda-intel probe_mask=1
options snd-hda-intel model=generic

Now I only ever see one output device; speakers or headphones (when
plugged in). HDMI doesn't recognise at all (although that's not a major
issue since it doesn't output video anyway)

Setup;
PC: XPS-9360
OS: Ubuntu-16.04
BIOS: 1.0.7
Kernel: 4.4.0-53-generic

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

Title:
[XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a
while

Status in alsa-driver package in Ubuntu:
Confirmed

Bug description:
I'm experiencing a strange behavior with a headphone jack on my
laptop.

However, after the next reboot speakers are not working again. And if
I will plug them out and in - problem with completely missing audio
returns.

P.S. I'm using laptop-mode-tools package on my laptop. Recovery after
hibernation made me believe that it's somehow related. But after
uninstalling this package nothing really changed.

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

[Desktop-packages] [Bug 1647209] Re: package kaccounts-providers (not installed) failed to install/upgrade: Versuch, »/etc/signon-ui/webkit-options.d/api.twitter.com.conf« zu überschreiben, welches au

2016-12-06 Thread Rik Mills

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

** This bug has been marked a duplicate of bug 1631246
   package kaccounts-providers (not installed) failed to install/upgrade: a 
tentar sobre-escrever '/etc/signon-ui/webkit-options.d/api.twitter.com.conf', 
que também está no pacote account-plugin-twitter 0.12+16.04.20160126-0ubuntu1

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

Title:
  package kaccounts-providers (not installed) failed to install/upgrade:
  Versuch, »/etc/signon-ui/webkit-options.d/api.twitter.com.conf« zu
  überschreiben, welches auch in Paket account-plugin-twitter
  0.12+16.04.20160126-0ubuntu1 ist

Status in account-plugins package in Ubuntu:
  Invalid
Status in kaccounts-providers package in Ubuntu:
  New

Bug description:
  wurde nicht installieret

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: kaccounts-providers (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  Date: Sun Dec  4 20:27:38 2016
  ErrorMessage: Versuch, »/etc/signon-ui/webkit-options.d/api.twitter.com.conf« 
zu überschreiben, welches auch in Paket account-plugin-twitter 
0.12+16.04.20160126-0ubuntu1 ist
  InstallationDate: Installed on 2016-11-20 (14 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: kaccounts-providers
  Title: package kaccounts-providers (not installed) failed to install/upgrade: 
Versuch, »/etc/signon-ui/webkit-options.d/api.twitter.com.conf« zu 
überschreiben, welches auch in Paket account-plugin-twitter 
0.12+16.04.20160126-0ubuntu1 ist
  UpgradeStatus: Upgraded to xenial on 2016-11-20 (14 days ago)

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

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

[Desktop-packages] [Bug 421350] Re: Keyboard navigation with PgUp/PgDn doesn't move selection

2016-12-06 Thread Bug Watch Updater

** Changed in: nautilus
   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/421350

Title:
  Keyboard navigation with PgUp/PgDn doesn't move selection

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

Bug description:
  Binary package hint: nautilus

  When navigating folders containing many files, Page Up and Page Down
  keys behavior is inconsistent with arrow keys. Arrows move the
  selection to the next file, and if needed, scroll the viewport so it
  is visible. However, PgUp/PgDn simply scroll the viewport, not
  switching the selection. Therefore, if I press down arrow after
  several PgDn presses, meaning to advance the viewport one line
  further, it jumps back to where the original selected file was. This
  is inconsistent with, for example, text editors and browsers.

  ProblemType: Bug
  Architecture: i386
  Date: Sun Aug 30 09:50:18 2009
  DistroRelease: Ubuntu 9.10
  Package: nautilus 1:2.27.91-0ubuntu1
  ProcEnviron:
   PATH=(custom, user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-8.28-generic
  SourcePackage: nautilus
  Tags:  ubuntu-unr
  Uname: Linux 2.6.31-8-generic i686

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

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

[Desktop-packages] [Bug 1639215] Re: After upgrade of Nvidia 304 drivers, mythfrontend.real crashed with SIGSEGV in QGLFormat::openGLVersionFlags()

2016-12-06 Thread Brian Murray

The retracer discovered that the core dump was truncated when trying to
retrace this crash, from the retracer log file:

ERROR: Invalid core dump: BFD: Warning: /tmp/apport_core_RVHov3 is
truncated: expected core file size >= 2306977792, found: 2147479552.

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

Title:
  After upgrade of Nvidia 304 drivers, mythfrontend.real crashed with
  SIGSEGV in QGLFormat::openGLVersionFlags()

Status in Mythbuntu:
  Won't Fix
Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed

Bug description:
  The Nvidia 304 drivers were updated by an "apt update && apt upgrade"
  to 304.132-0ubuntu0.16.04.2.  On the next reboot, mythfrontend crashed
  each time it was started.  The mythfrontend.log file always shows the
  same messages - see the attached mythfrontend.log file.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: mythtv-frontend 2:0.28.0+fixes.20161023.7f8f168-0ubuntu0mythbuntu3 
[origin: LP-PPA-mythbuntu-0.28]
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  NonfreeKernelModules: tbs5922fe nvidia
  .var.log.mythtv.mythavtest.log:
   
  .var.log.mythtv.mythccextractor.log:
   
  .var.log.mythtv.mythfilldatabase.log:
   
  .var.log.mythtv.mythjobqueue.log:
   
  .var.log.mythtv.mythlcdserver.log:
   
  .var.log.mythtv.mythmediaserver.log:
   
  .var.log.mythtv.mythshutdown.log:
   
  .var.log.mythtv.mythutil.log:
   
  .var.log.mythtv.mythwelcome.log:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashDB: mythbuntu
  CurrentDesktop: XFCE
  Date: Sat Nov  5 00:30:56 2016
  ExecutablePath: /usr/bin/mythfrontend.real
  InstallationDate: Installed on 2012-08-25 (1531 days ago)
  InstallationMedia: Mythbuntu 12.04 "Precise Pangolin" - Release amd64 
(20120425)
  Installed_mythtv_dbg: 2:0.28.0+fixes.20161023.7f8f168-0ubuntu0mythbuntu3
  ProcCmdline: /usr/bin/mythfrontend.real --syslog local7
  ProcEnviron:
   LANGUAGE=en_NZ:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f33652b2f29 
<_ZN9QGLFormat18openGLVersionFlagsEv+313>:  mov(%rax),%rax
   PC (0x7f33652b2f29) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: mythtv
  StacktraceTop:
   QGLFormat::openGLVersionFlags() () from 
/usr/lib/x86_64-linux-gnu/libQt5OpenGL.so.5
   MythRenderOpenGL::Create (painter=..., device=0x0) at 
mythrender_opengl.cpp:114
   MythMainWindow::Init (this=0x19e8210, forcedpainter=...) at 
mythmainwindow.cpp:1160
   main (argc=3, argv=0x7ffd29d3e418) at main.cpp:1886
  Title: mythfrontend.real crashed with SIGSEGV in 
QGLFormat::openGLVersionFlags()
  UpgradeStatus: Upgraded to xenial on 2016-10-08 (26 days ago)
  UserGroups: adm cdrom dip lpadmin mythtv plugdev sambashare sudo syslog video

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

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

[Desktop-packages] [Bug 1644986] Re: Screen flickering since 16.10 upgrade