[Touch-packages] [Bug 1709532] [NEW] Can't get the additional resolution

[Anchal Bhargava]

Public bug reported:

Hello,

I am new to Linux, I have just installed Ubuntu 14, my problem is I am
getting only one screen resolution in display(1024x768) and that's kind
of uncomfortable to work.

I read that we do not need to install Graphics Driver then why isn't it
showing me other screen resolutions?

One more thing, when I tried to install Ubuntu, after clicking on
Install Ubuntu option, I got the time, volume option on the top right
hand but the installation didn't start. I waited for around 15 minutes
then restart the installation. I tried to install ubuntu 6-7 times with
different versions too. But same thing happened every time.

So I read in a forum and some one said to use "nomodeset" option and
after that ubuntu was installed. I hope this will help in rectifying the
problem (also I will be very grateful if you can tell me why it wasn't
working before and why it did install after that option, I am trying to
learn how Linux works)

And I think that this doesn't have to do anything with it but still. I
am using Intel XEON E5450 processor and don't have any external graphic
card installed.

Thanks,
Anchal Bhargava

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.4.0-89.112~14.04.1-generic 4.4.76
Uname: Linux 4.4.0-89-generic x86_64
.tmp.unity.support.test.1:
 
ApportVersion: 2.14.1-0ubuntu3.25
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 Aug  9 10:29:21 2017
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Mobile 4 Series Chipset Integrated Graphics 
Controller [8086:2a42]
   Subsystem: Intel Corporation Device [8086:2a42]
InstallationDate: Installed on 2017-08-09 (0 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=7dac48a4-be03-4308-9a7f-9e2e4231dcee ro nomodeset quiet splash 
vt.handoff=7
Renderer: Software
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/10/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: GM45+ICH9+775 Series
dmi.board.vendor: LORD ELECTRONICS CO.,LTD.LORD
dmi.board.version: I1T65 V0.5
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: bio...@163.com
dmi.chassis.version: Any Question, Please send mail
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd12/10/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnLORDELECTRONICSCO.,LTD.LORD:rnGM45+ICH9+775Series:rvrI1T65V0.5:cvnbio...@163.com:ct3:cvrAnyQuestion,Pleasesendmail:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Aug  9 10:27:05 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputCompx 2.4G Receiver  KEYBOARD, id 8
 inputCompx 2.4G Receiver  MOUSE, id 9
 inputCompx 2.4G Receiver  KEYBOARD, id 10
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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


** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1709532

Title:
  Can't get the additional resolution

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello,

  I am new to Linux, I have just installed Ubuntu 14, my problem is I am
  getting only one screen resolution in 

[Touch-packages] [Bug 1588917] Re: Upgrade ping to latest version that doesn't require SUID or NET_RAW capability

[Ricardo]

I think it should be up to the user to decide whether to enable this by
setting the net.ipv4.ping_group_range sysctl.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iputils in Ubuntu.
https://bugs.launchpad.net/bugs/1588917

Title:
  Upgrade ping to latest version that doesn't require SUID or NET_RAW
  capability

Status in iputils package in Ubuntu:
  Triaged

Bug description:
  The latest version of iputils have the option of using SOCK_DGRAM
  packets instead of SOCK_RAW, provided that the
  net.ipv4.ping_group_range sysctl is set to a different value.  This
  helps a lot with security in -not just- Linux containers by dropping
  support for the NET_RAW capability.

  Also, the ubuntu-minimal packages should not include this package as a
  hard dependency in case I want to uninstall iputils-ping to substitute
  it for another package like oping which just works if I turn off the
  setuid bit.

  This would help a lot with secure Linux containers with no NET_RAW
  capabilities.

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

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

[Touch-packages] [Bug 1695638] Re: package krb5-locales 1.15-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1695638

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

Status in krb5 package in Ubuntu:
  Expired

Bug description:
  sometimes the system hangs on

  and its not activating an adapter device ..

  also having a problem when trying to upload ubuntu software .

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: krb5-locales 1.15-1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   firefox:amd64: Install
   firefox-locale-ar:amd64: Install
   firefox-locale-en:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May 27 18:14:20 2017
  Dependencies:
   
  DuplicateSignature:
   package:krb5-locales:1.15-1
   Processing triggers for bamfdaemon (0.5.3+17.04.20170406-0ubuntu1) ...
   Rebuilding /usr/share/applications/bamf-2.index...
   dpkg: error processing package krb5-locales (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-03-16 (78 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: krb5
  Title: package krb5-locales 1.15-1 failed to install/upgrade: package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: Upgraded to zesty on 2017-05-16 (17 days ago)

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

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

[Touch-packages] [Bug 1692247] Re: package iproute2 4.3.0-1ubuntu3.16.04.1 failed to install/upgrade: package iproute2 is not ready for configuration cannot configure (current status 'half-installed')

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1692247

Title:
  package iproute2 4.3.0-1ubuntu3.16.04.1 failed to install/upgrade:
  package iproute2 is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in iproute2 package in Ubuntu:
  Expired

Bug description:
  I dont know anything. I just try to instal some programs on my comp,
  and when i try to start virtualbox it cant.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: iproute2 4.3.0-1ubuntu3.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  AptOrdering:
   iproute2: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May 20 16:22:19 2017
  DpkgTerminalLog:
   dpkg: error processing package iproute2 (--configure):
package iproute2 is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package iproute2 is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-02-20 (88 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: iproute2
  Title: package iproute2 4.3.0-1ubuntu3.16.04.1 failed to install/upgrade: 
package iproute2 is not ready for configuration  cannot configure (current 
status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1696735] Re: package libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1696735

Title:
  package libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in krb5 package in Ubuntu:
  Expired

Bug description:
  unknown

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun  8 08:22:46 2017
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-02-12 (481 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: krb5
  Title: package libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to xenial on 2016-05-22 (381 days ago)

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

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

[Touch-packages] [Bug 1596344] Re: pulseaudio causes long login delay waiting for bluetooth

[Jordan]

I guess I was mistaken about commenting out "load-module module-
bluetooth-policy" and "load-module module-bluetooth-discover", that did
not solve the problem for me.


A successful workaround though was to "sudo rm 
/xdg/autostart/pulseaudio.desktop" which stops gnome-session from trying to 
start start-pulseaudio-x11 (and block until it signals completion of startup, 
which takes about 30 seconds).

Even without /xdg/autostart/pulseaudio.desktop pulse is being spawned by
something, as can be seen from "pgrep pulse", and I can play sounds
fine.

I am *not* recommending this as a general solution for everyone as I do
not know what ramifications there might be to not having
/xdg/autostart/pulseaudio.desktop that I just might not have noticed. I
assume that it is there for a reason.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1596344

Title:
  pulseaudio causes long login delay waiting for bluetooth

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 16.04 --

  I was experiencing a long delay when logging in, on the order of 20+
  seconds. After entering the password on the splash screen, it would
  stay there before showing the desktop.

  journalctl revealed a timeout form pulseaudio waiting for a bluetooth
  service (I don't not use bluetooth, and it is disabled, but I believe
  I saw this even when I enabled it?)

  Jun 26 10:43:42 machinename org.kde.KScreen[1988]: kscreen: Primary output 
changed from KScreen::Output(Id: 68 , Name: "HDMI1" ) ( "HDMI1" ) to 
KScreen::Output(Id: 68 , Name: "HDMI1" ) ( "HDMI1" )
  Jun 26 10:44:02 machinename dbus[982]: [system] Failed to activate service 
'org.bluez': timed out
  Jun 26 10:44:02 machinename pulseaudio[2121]: [pulseaudio] bluez5-util.c: 
GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive 
a reply. Possible causes include: the remote application did not send a reply, 
the message bus security policy blocked the reply, the reply timeout expired, 
or the network connection was broken.

  I can fix the problem by editing /etc/pulse/default.pa and commenting
  out both bluetooth lines ("load-module module-bluetooth-policy" and
  "load-module module-bluetooth-discover" -- not sure if both are
  actually necessary.)

  I have seen other bugs relating to blocking calls to bluetooth causing
  problems. Perhaps there are a few left.

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

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

[Touch-packages] [Bug 1686470] Re: Apt updates that are uniformly spread across all timezones, with predictable application windows

[Bug Watch Updater]

** Changed in: unattended-upgrades (Debian)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1686470

Title:
  Apt updates that are uniformly spread across all timezones, with
  predictable application windows

Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Released
Status in apt source package in Yakkety:
  Won't Fix
Status in unattended-upgrades source package in Yakkety:
  Won't Fix
Status in apt source package in Zesty:
  Fix Committed
Status in unattended-upgrades source package in Zesty:
  Fix Committed
Status in apt source package in Artful:
  Fix Released
Status in unattended-upgrades source package in Artful:
  Fix Released
Status in apt package in Debian:
  Fix Released
Status in unattended-upgrades package in Debian:
  Fix Released

Bug description:
  [ Impact ]

   * unattended-upgrades are enabled by default in Ubuntu 16.04 and
  later

   * Currently the following three things happen as a monolithic event:
     - metadata updates: apt update
     - download of updates: apt upgrade --download-only
     - application of updates: apt upgrade

   * For the long running instances, all of the above happens at random
     times throughout the day.

   * If systems were poweredoff / suspended, this happens on boot /
  resume

   * End-users would like to have predictable timing, and control over when
     the updates happen.

  Considering all of the above, the following new behavior is proposed
  which should address all concerns in question. It combines all the
  desired properties from both end-user and mirror perspectives.

  [ Proposed Default Behavior ]

   * Decouple unattended-upgrades application, from apt update

   * apt update:
     - shall be a systemd timer based unit, triggered every 12h with a
   random delay of 12h, therefore executed randomly twice a day.
     - if unattened-upgrades (default on), or download-upgreadaeble-packages
   are enabled, it should result in updates being downloaded aka
   `apt upgrade --download-only`

   * unattended-upgrades:
     - shall be a separate systemd timer based unit triggered at 6am local
   time with a random delay of 1h, therefore executed between 6am and
   7am local time.

   * On boot / resume:
     - if we have missed one, or more, apt update timers,
   apt update / download upgrades / unattended-upgrade will happen in
   sequence. This may result in mirror spikes, but we do want to secure
   cold/stale-booted systems as soon as possible.

  [Test Case]

   * Run system for more than 24h, and check that apt updates were
     automatically executed twice.

   * Check that unattended upgrades were triggered to be applied at
     6am..7am window, if any.

   * Poweroff the machine over the period when apt-get update was
     scheduled, poweron and observe that apt-get update / download /
     unattended upgrade are all performed on boot.

   * Downgrade systemd to the release version of the package (from
     -security). Remove apt periodic stamp files rm /var/lib/apt/periodic/*.
 Then run 'sudo systemctl start apt-daily.service'.
     Confirm that the systemd package is downloaded, but not upgraded.

  [Regression Potential]

   * The newly proposed behavior is a mix of Pre-xenial behavior of "do
     everything at 6am..6:30am window" and the xenial+ behavior of "do
     everything at random times throughout the day". If there are specific
     deployments that rely on the previous types of behaviour they will be
     able to adjust manually the systemd timers with the overrides to be
     executed exactly as they wish; or match the .0 release behaviour that
     they prefer.

   * If timers behavior is coded wrongly the proposed behaviour might not be
     executed as intended, thus requiring further SRUs to bring us in-line
     with the great expectations.

  [Other Info]

    * Related bug reports and history:
  - bug #1615482
  - bug #1554848

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

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

[Touch-packages] [Bug 1709500] Re: Headerbar buttons that are highlighted/coloured in Adwaita are not coloured at all in Ambiance.

[Daniel van Vugt]

I'm not sure the colouring of some headerbar buttons in some windows is
a good design choice by upstream. In the example in the bug description,
the (blue in Adwaita) Extract button is no more important than the non-
blue Extract button in the dialog that came before it.

So yeah it's a theme bug that Ambiance is missing this highlighting but
also not really a noticeable problem unless you're familiar with other
themes.

** Summary changed:

- The headerbar action buttons lack contrast
+ Headerbar buttons that are highlighted/coloured in Adwaita are not coloured 
at all in Ambiance.

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Low

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1709500

Title:
  Headerbar buttons that are highlighted/coloured in Adwaita are not
  coloured at all in Ambiance.

Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Using Ambiance on artful, the "action buttons" used in GtkHeaderBar
  are using a color similar to bar background which makes them not stand
  out. One example is the file-roller extract dialog, when using Adwaita
  the "extract" button is blue which make it an obvious click target,
  that's not the case under our themes

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

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

[Touch-packages] [Bug 1709163] Re: default output changes from intel builtin to hdmi when display is turned off. yes off not on

[Daniel van Vugt]

Thanks for that. My first thought is to wait for the next pulseaudio
update where we will be removing a pile of historic patches that change
behaviour slightly, but exist neither in Debian nor upstream. If that
doesn't fix it then perhaps this is related to the switch-on-connect
module (misfiring?).

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1709163

Title:
  default output changes from intel builtin to hdmi when display is
  turned off. yes off not on

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  So if I have sound output selected to be the intel sound on the
  mainboard and turn off one of my two displays the audio out is changed
  to HDMI. YES OFF it's not a typo.

  The Display I turn off is connected to displayport and do not even
  have HDMI. The audio is switched over to the still active display.

  If I then turn the display back it's still hdmi. If I then turn off
  the display that has HDMI out connected. the audio is still connected
  to that display. since its actually off I hear no sound but pulseaudio
  still connect to it.

  I have to manually open the GUI tool and change back to the correct
  output when the display is turned off or when the display is blanked.
  or suspend/resume.

  I attache the output of "pacmd list-cards  && pacmd list-sinks"
  ok   -> ps_w1.txt
  fail -> ps_f1.txt
  --- 
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kenjo  3721 F pulseaudio
   /dev/snd/controlC1:  kenjo  3721 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2015-10-18 (659 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  Package: pulseaudio 1:10.0-2ubuntu1
  PackageArchitecture: amd64
  Tags:  artful
  Uname: Linux 4.12.1-041201-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-06-10 (59 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare 
sudo video wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.I0
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A GAMING M7 (MS-7976)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.I0:bd04/25/2017:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7976
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-04-23T00:00:29.066742

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

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

[Touch-packages] [Bug 1553328] Re: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings

[Daniel van Vugt]

Alan, that question was already answered in comment #20. Single threaded
rendering works.

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

** Changed in: mir
   Importance: Undecided => High

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1553328

Title:
  Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref()
  especially with multiple monitors, webbrowser-app or system settings

Status in Canonical System Image:
  Triaged
Status in Mir:
  Triaged
Status in Nouveau Xorg driver:
  Unknown
Status in Unity System Compositor:
  Triaged
Status in libdrm package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  In Progress
Status in qtubuntu package in Ubuntu:
  In Progress

Bug description:
  Unit8 froze up while I was trying to open system settings.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160216.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Fri Mar  4 19:12:54 2016
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2015-05-10 (299 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: unity8
  SegvAnalysis:
   Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx
   PC (0x7f58d568706c) ok
   source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  Title: unity8 crashed with SIGSEGV
  UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session

[Daniel van Vugt]

I am going to work on additional patches so that by the time 17.10 is
released all you will need is:

   mpv myvideo.mp4

** Description changed:

  The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
  Gnome Shell). But it refuses to load when in a Wayland session:
  
  $ totem bbb_sunflower_1080p_60fps_normal.mp4
  libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)
  
  $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4
  totem: intel_driver.c:112: intel_driver_init: Assertion 
`VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, 
VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed.
  Aborted (core dumped)
  
  $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4
  Press 'k' to see a list of keyboard shortcuts.
  Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  Redistribute latency...
  Redistribute latency...
  ERROR Internal error: could not render surface for 
file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0
  
  WORKAROUNDS:
  
   * Use weston instead of gnome-shell; or
   * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463
   * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 
1701463
-  * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ...
-  * $ mpv --hwdec --opengl-backend=wayland ...
+  * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ...
+  * $ env -uDISPLAY mpv --hwdec --opengl-backend=wayland ...
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: i965-va-driver 1.8.1-1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 13:40:38 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1698287

Title:
  VA-API fails to initialize in a Gnome Shell Wayland session

Status in Libva:
  New
Status in Mutter:
  Confirmed
Status in Totem:
  Confirmed
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Won't Fix
Status in intel-vaapi-driver package in Ubuntu:
  Invalid
Status in libva package in Ubuntu:
  Triaged
Status in mpv package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  Triaged
Status in totem package in Ubuntu:
  Invalid

Bug description:
  The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
  Gnome Shell). But it refuses to load when in a Wayland session:

  $ totem bbb_sunflower_1080p_60fps_normal.mp4
  libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)

  $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4
  totem: intel_driver.c:112: intel_driver_init: Assertion 
`VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, 
VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed.
  Aborted (core dumped)

  $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4
  Press 'k' to see a list of keyboard shortcuts.
  Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  Redistribute latency...
  Redistribute latency...
  ERROR Internal error: could not render surface for 
file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0

  WORKAROUNDS:

   * Use weston instead of gnome-shell; or
   * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463
   * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 
1701463
   * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ...
   * $ env -uDISPLAY mpv --hwdec --opengl-backend=wayland ...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: i965-va-driver 1.8.1-1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 13:40:38 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Touch-packages] [Bug 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session

[Daniel van Vugt]

Actually comment #16 doesn't need a new bug. This bug will do fine for
that. See comments #3 - #4.

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

** Changed in: mpv (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: gstreamer-vaapi (Ubuntu)
   Status: In Progress => Won't Fix

** Changed in: gstreamer-vaapi (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1698287

Title:
  VA-API fails to initialize in a Gnome Shell Wayland session

Status in Libva:
  New
Status in Mutter:
  Confirmed
Status in Totem:
  Confirmed
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Won't Fix
Status in intel-vaapi-driver package in Ubuntu:
  Invalid
Status in libva package in Ubuntu:
  Triaged
Status in mpv package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  Triaged
Status in totem package in Ubuntu:
  Invalid

Bug description:
  The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
  Gnome Shell). But it refuses to load when in a Wayland session:

  $ totem bbb_sunflower_1080p_60fps_normal.mp4
  libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)

  $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4
  totem: intel_driver.c:112: intel_driver_init: Assertion 
`VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, 
VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed.
  Aborted (core dumped)

  $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4
  Press 'k' to see a list of keyboard shortcuts.
  Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  Redistribute latency...
  Redistribute latency...
  ERROR Internal error: could not render surface for 
file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0

  WORKAROUNDS:

   * Use weston instead of gnome-shell; or
   * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463
   * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 
1701463
   * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ...
   * $ env -uDISPLAY mpv --hwdec --opengl-backend=wayland ...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: i965-va-driver 1.8.1-1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 13:40:38 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session

[Daniel van Vugt]

Doug,

A couple of my fixes have landed today, as well as ffmpeg 3.3 which
fixes most of mpv's acceleration problems. However your comment reminds
me there's another bug with mpv I need to open and fix... mpv will by
default try to use the X11 display provided by Xwayland and ends up with
vaapi-copy. You can work around that trivially and get hwdec=vaapi
proper working again by hiding Xwayland:

   env -uDISPLAY mpv --hwdec myvideo.mp4

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1698287

Title:
  VA-API fails to initialize in a Gnome Shell Wayland session

Status in Libva:
  New
Status in Mutter:
  Confirmed
Status in Totem:
  Confirmed
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Won't Fix
Status in intel-vaapi-driver package in Ubuntu:
  Invalid
Status in libva package in Ubuntu:
  Triaged
Status in mpv package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  Triaged
Status in totem package in Ubuntu:
  Invalid

Bug description:
  The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
  Gnome Shell). But it refuses to load when in a Wayland session:

  $ totem bbb_sunflower_1080p_60fps_normal.mp4
  libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)

  $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4
  totem: intel_driver.c:112: intel_driver_init: Assertion 
`VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, 
VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed.
  Aborted (core dumped)

  $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4
  Press 'k' to see a list of keyboard shortcuts.
  Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  Redistribute latency...
  Redistribute latency...
  ERROR Internal error: could not render surface for 
file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0

  WORKAROUNDS:

   * Use weston instead of gnome-shell; or
   * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463
   * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 
1701463
   * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ...
   * $ env -uDISPLAY mpv --hwdec --opengl-backend=wayland ...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: i965-va-driver 1.8.1-1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 13:40:38 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1686183] Re: Ship ubuntu-advantage in ubuntu-minimal

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-advantage-tools - 2

---
ubuntu-advantage-tools (2) trusty; urgency=medium

  * ubuntu-advantage & /etc/update-motd.d/99-esm now build, run and are quiet
on non-precise release. (LP: #1686183)
  * Add simple dep8 tests.
  * Also install ca-certificates (LP: #1690270)

 -- David Britton   Fri, 30 Jun 2017
15:20:00 -0600

** Changed in: ubuntu-advantage-tools (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

** Changed in: ubuntu-advantage-tools (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1686183

Title:
  Ship ubuntu-advantage in ubuntu-minimal

Status in ubuntu-advantage-tools package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-advantage-tools source package in Precise:
  Fix Released
Status in ubuntu-meta source package in Precise:
  Fix Released
Status in ubuntu-advantage-tools source package in Trusty:
  Fix Released
Status in ubuntu-meta source package in Trusty:
  New
Status in ubuntu-advantage-tools source package in Xenial:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  New
Status in ubuntu-advantage-tools source package in Yakkety:
  Won't Fix
Status in ubuntu-meta source package in Yakkety:
  Won't Fix
Status in ubuntu-advantage-tools source package in Zesty:
  Fix Released
Status in ubuntu-meta source package in Zesty:
  New
Status in ubuntu-advantage-tools source package in Artful:
  Fix Released
Status in ubuntu-meta source package in Artful:
  New

Bug description:
  The ubuntu-advantage-tools package is a bit odd as it was first landed
  in precise to support the ESM effort inside canonical. [0]  In order
  to bring this package up to date across other series in ubuntu, it has
  been recommended by the Ubuntu Foundations team to land into trusty
  next, then forward-port pocket-copy to all supported series until we
  get to the devel release.

  The version here:

  https://github.com/CanonicalLtd/ubuntu-advantage-
  script/releases/tag/v2

  ... has all on-disk bits correctly working, for all series, but no-ops
  on any release other than precise (ESM is only for "unsupported" LTS
  releases as it were).  This is a request to land ubuntu-advantage-
  tools into trusty, then pocket-copy it to supported series of ubuntu
  once that is finished.

  [Impact]

   * Allow ubuntu-advantage users to access the extended security
  maintenance script with a simple command line tool.  This script needs
  to hit precise machines and be easy for ubuntu-advantage customers to
  enable, thus basefiles was chosen as a home.

  [Test Case]

   * Run ubuntu-advantage, it should print out help

   * Run sudo ubuntu-advantage enable  (without sudo it will warn
  you), but you need to be an ubuntu-advantage customer to get that
  token.  In the end, the script simply adds and removes an
  /etc/apt/sources.list.d entry.

   * Verify that the MOTD does not contain any mention of ubuntu-
  advantage esm or precise and its end of life

   * Verify that ubuntu-advantage enable-esm  installs needed 
dependencies:
- create the following file and its contents to have apt not install 
recommended packages by default:
  $ cat /etc/apt/apt.conf.d/no-recommends
  APT::Install-Recommends "false";
- remove ca-certificates and apt-transport-https:
  $ sudo apt remove ca-certificates apt-transport-https
- run sudo ubuntu-advantage enable-esm  and verify that the two 
removed packages are reinstalled

   * you can contact me (d...@canonical.com) if you would like a token
  for test purposes.

  [Regression Potential]

   * Low, this is a new script, not included in any automated startup
  paths.

  [Other Info]

   * http://blog.dustinkirkland.com/2017/03/ubuntu-1204-esm.html

  [0] https://insights.ubuntu.com/2017/03/14/introducing-ubuntu-12-04
  -esm-extended-security-maintenance/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1686183/+subscriptions

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

[Touch-packages] [Bug 1686183] Re: Ship ubuntu-advantage in ubuntu-minimal

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-advantage-tools - 2

---
ubuntu-advantage-tools (2) trusty; urgency=medium

  * ubuntu-advantage & /etc/update-motd.d/99-esm now build, run and are quiet
on non-precise release. (LP: #1686183)
  * Add simple dep8 tests.
  * Also install ca-certificates (LP: #1690270)

 -- David Britton   Fri, 30 Jun 2017
15:20:00 -0600

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1686183

Title:
  Ship ubuntu-advantage in ubuntu-minimal

Status in ubuntu-advantage-tools package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-advantage-tools source package in Precise:
  Fix Released
Status in ubuntu-meta source package in Precise:
  Fix Released
Status in ubuntu-advantage-tools source package in Trusty:
  Fix Released
Status in ubuntu-meta source package in Trusty:
  New
Status in ubuntu-advantage-tools source package in Xenial:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  New
Status in ubuntu-advantage-tools source package in Yakkety:
  Won't Fix
Status in ubuntu-meta source package in Yakkety:
  Won't Fix
Status in ubuntu-advantage-tools source package in Zesty:
  Fix Released
Status in ubuntu-meta source package in Zesty:
  New
Status in ubuntu-advantage-tools source package in Artful:
  Fix Released
Status in ubuntu-meta source package in Artful:
  New

Bug description:
  The ubuntu-advantage-tools package is a bit odd as it was first landed
  in precise to support the ESM effort inside canonical. [0]  In order
  to bring this package up to date across other series in ubuntu, it has
  been recommended by the Ubuntu Foundations team to land into trusty
  next, then forward-port pocket-copy to all supported series until we
  get to the devel release.

  The version here:

  https://github.com/CanonicalLtd/ubuntu-advantage-
  script/releases/tag/v2

  ... has all on-disk bits correctly working, for all series, but no-ops
  on any release other than precise (ESM is only for "unsupported" LTS
  releases as it were).  This is a request to land ubuntu-advantage-
  tools into trusty, then pocket-copy it to supported series of ubuntu
  once that is finished.

  [Impact]

   * Allow ubuntu-advantage users to access the extended security
  maintenance script with a simple command line tool.  This script needs
  to hit precise machines and be easy for ubuntu-advantage customers to
  enable, thus basefiles was chosen as a home.

  [Test Case]

   * Run ubuntu-advantage, it should print out help

   * Run sudo ubuntu-advantage enable  (without sudo it will warn
  you), but you need to be an ubuntu-advantage customer to get that
  token.  In the end, the script simply adds and removes an
  /etc/apt/sources.list.d entry.

   * Verify that the MOTD does not contain any mention of ubuntu-
  advantage esm or precise and its end of life

   * Verify that ubuntu-advantage enable-esm  installs needed 
dependencies:
- create the following file and its contents to have apt not install 
recommended packages by default:
  $ cat /etc/apt/apt.conf.d/no-recommends
  APT::Install-Recommends "false";
- remove ca-certificates and apt-transport-https:
  $ sudo apt remove ca-certificates apt-transport-https
- run sudo ubuntu-advantage enable-esm  and verify that the two 
removed packages are reinstalled

   * you can contact me (d...@canonical.com) if you would like a token
  for test purposes.

  [Regression Potential]

   * Low, this is a new script, not included in any automated startup
  paths.

  [Other Info]

   * http://blog.dustinkirkland.com/2017/03/ubuntu-1204-esm.html

  [0] https://insights.ubuntu.com/2017/03/14/introducing-ubuntu-12-04
  -esm-extended-security-maintenance/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1686183/+subscriptions

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

[Touch-packages] [Bug 1686183] Re: Ship ubuntu-advantage in ubuntu-minimal

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-advantage-tools - 2

---
ubuntu-advantage-tools (2) trusty; urgency=medium

  * ubuntu-advantage & /etc/update-motd.d/99-esm now build, run and are quiet
on non-precise release. (LP: #1686183)
  * Add simple dep8 tests.
  * Also install ca-certificates (LP: #1690270)

 -- David Britton   Fri, 30 Jun 2017
15:20:00 -0600

** Changed in: ubuntu-advantage-tools (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1686183

Title:
  Ship ubuntu-advantage in ubuntu-minimal

Status in ubuntu-advantage-tools package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-advantage-tools source package in Precise:
  Fix Released
Status in ubuntu-meta source package in Precise:
  Fix Released
Status in ubuntu-advantage-tools source package in Trusty:
  Fix Released
Status in ubuntu-meta source package in Trusty:
  New
Status in ubuntu-advantage-tools source package in Xenial:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  New
Status in ubuntu-advantage-tools source package in Yakkety:
  Won't Fix
Status in ubuntu-meta source package in Yakkety:
  Won't Fix
Status in ubuntu-advantage-tools source package in Zesty:
  Fix Released
Status in ubuntu-meta source package in Zesty:
  New
Status in ubuntu-advantage-tools source package in Artful:
  Fix Released
Status in ubuntu-meta source package in Artful:
  New

Bug description:
  The ubuntu-advantage-tools package is a bit odd as it was first landed
  in precise to support the ESM effort inside canonical. [0]  In order
  to bring this package up to date across other series in ubuntu, it has
  been recommended by the Ubuntu Foundations team to land into trusty
  next, then forward-port pocket-copy to all supported series until we
  get to the devel release.

  The version here:

  https://github.com/CanonicalLtd/ubuntu-advantage-
  script/releases/tag/v2

  ... has all on-disk bits correctly working, for all series, but no-ops
  on any release other than precise (ESM is only for "unsupported" LTS
  releases as it were).  This is a request to land ubuntu-advantage-
  tools into trusty, then pocket-copy it to supported series of ubuntu
  once that is finished.

  [Impact]

   * Allow ubuntu-advantage users to access the extended security
  maintenance script with a simple command line tool.  This script needs
  to hit precise machines and be easy for ubuntu-advantage customers to
  enable, thus basefiles was chosen as a home.

  [Test Case]

   * Run ubuntu-advantage, it should print out help

   * Run sudo ubuntu-advantage enable  (without sudo it will warn
  you), but you need to be an ubuntu-advantage customer to get that
  token.  In the end, the script simply adds and removes an
  /etc/apt/sources.list.d entry.

   * Verify that the MOTD does not contain any mention of ubuntu-
  advantage esm or precise and its end of life

   * Verify that ubuntu-advantage enable-esm  installs needed 
dependencies:
- create the following file and its contents to have apt not install 
recommended packages by default:
  $ cat /etc/apt/apt.conf.d/no-recommends
  APT::Install-Recommends "false";
- remove ca-certificates and apt-transport-https:
  $ sudo apt remove ca-certificates apt-transport-https
- run sudo ubuntu-advantage enable-esm  and verify that the two 
removed packages are reinstalled

   * you can contact me (d...@canonical.com) if you would like a token
  for test purposes.

  [Regression Potential]

   * Low, this is a new script, not included in any automated startup
  paths.

  [Other Info]

   * http://blog.dustinkirkland.com/2017/03/ubuntu-1204-esm.html

  [0] https://insights.ubuntu.com/2017/03/14/introducing-ubuntu-12-04
  -esm-extended-security-maintenance/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1686183/+subscriptions

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

[Touch-packages] [Bug 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session

[Launchpad Bug Tracker]

This bug was fixed in the package gst-plugins-bad1.0 - 1.12.2-1ubuntu2

---
gst-plugins-bad1.0 (1.12.2-1ubuntu2) artful; urgency=medium

  * Prefer native Wayland over X11/Xwayland if both are available. This
fixes VA-API initialization failure in Gnome Shell Wayland sessions
(LP: #1698287).

 -- Daniel van Vugt   Tue, 08 Aug 2017
17:08:09 +0800

** Changed in: gst-plugins-bad1.0 (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1698287

Title:
  VA-API fails to initialize in a Gnome Shell Wayland session

Status in Libva:
  New
Status in Mutter:
  Confirmed
Status in Totem:
  Confirmed
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  In Progress
Status in intel-vaapi-driver package in Ubuntu:
  Invalid
Status in libva package in Ubuntu:
  Triaged
Status in mpv package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in totem package in Ubuntu:
  Invalid

Bug description:
  The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
  Gnome Shell). But it refuses to load when in a Wayland session:

  $ totem bbb_sunflower_1080p_60fps_normal.mp4
  libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)

  $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4
  totem: intel_driver.c:112: intel_driver_init: Assertion 
`VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, 
VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed.
  Aborted (core dumped)

  $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4
  Press 'k' to see a list of keyboard shortcuts.
  Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  Redistribute latency...
  Redistribute latency...
  ERROR Internal error: could not render surface for 
file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0

  WORKAROUNDS:

   * Use weston instead of gnome-shell; or
   * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463
   * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 
1701463
   * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ...
   * $ mpv --hwdec --opengl-backend=wayland ...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: i965-va-driver 1.8.1-1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 13:40:38 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session

[Doug McMahon]

Regarding the mpv in artful:
You can currently get some vaapi support in wayland session, you'd need to use
hwdec=vaapi-copy
Not as effective as hwdec=vaapi but I don't think they'll be changing that 
(commit noted), in near future.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1698287

Title:
  VA-API fails to initialize in a Gnome Shell Wayland session

Status in Libva:
  New
Status in Mutter:
  Confirmed
Status in Totem:
  Confirmed
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Committed
Status in gstreamer-vaapi package in Ubuntu:
  In Progress
Status in intel-vaapi-driver package in Ubuntu:
  Invalid
Status in libva package in Ubuntu:
  Triaged
Status in mpv package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in totem package in Ubuntu:
  Invalid

Bug description:
  The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
  Gnome Shell). But it refuses to load when in a Wayland session:

  $ totem bbb_sunflower_1080p_60fps_normal.mp4
  libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)

  $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4
  totem: intel_driver.c:112: intel_driver_init: Assertion 
`VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, 
VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed.
  Aborted (core dumped)

  $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4
  Press 'k' to see a list of keyboard shortcuts.
  Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  Redistribute latency...
  Redistribute latency...
  ERROR Internal error: could not render surface for 
file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0

  WORKAROUNDS:

   * Use weston instead of gnome-shell; or
   * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463
   * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 
1701463
   * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ...
   * $ mpv --hwdec --opengl-backend=wayland ...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: i965-va-driver 1.8.1-1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 13:40:38 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1699216] Re: Encrypted home support

[Sebastien Bacher]

Not really, it's just that sponsors are busy, you can always try to ask
on IRC though...

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1699216

Title:
  Encrypted home support

Status in accountsservice package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-initial-setup package in Ubuntu:
  Confirmed

Bug description:
  In the CreateUser D-bus call, allow the home directory of the new user
  to be encrypted.

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

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

[Touch-packages] [Bug 1709500] [NEW] The headerbar action buttons lack contrast

[Sebastien Bacher]

Public bug reported:

Using Ambiance on artful, the "action buttons" used in GtkHeaderBar are
using a color similar to bar background which makes them not stand out.
One example is the file-roller extract dialog, when using Adwaita the
"extract" button is blue which make it an obvious click target, that's
not the case under our themes

** Affects: ubuntu-themes (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: gnome-17.10

** Tags added: gnome-17.10

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1709500

Title:
  The headerbar action buttons lack contrast

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Using Ambiance on artful, the "action buttons" used in GtkHeaderBar
  are using a color similar to bar background which makes them not stand
  out. One example is the file-roller extract dialog, when using Adwaita
  the "extract" button is blue which make it an obvious click target,
  that's not the case under our themes

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

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

[Touch-packages] [Bug 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session

[Sebastien Bacher]

The simple version of the patch builds fine in a ppa, sponsoring that
one

** Changed in: gst-plugins-bad1.0 (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1698287

Title:
  VA-API fails to initialize in a Gnome Shell Wayland session

Status in Libva:
  New
Status in Mutter:
  Confirmed
Status in Totem:
  Confirmed
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Committed
Status in gstreamer-vaapi package in Ubuntu:
  In Progress
Status in intel-vaapi-driver package in Ubuntu:
  Invalid
Status in libva package in Ubuntu:
  Triaged
Status in mpv package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in totem package in Ubuntu:
  Invalid

Bug description:
  The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
  Gnome Shell). But it refuses to load when in a Wayland session:

  $ totem bbb_sunflower_1080p_60fps_normal.mp4
  libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)

  $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4
  totem: intel_driver.c:112: intel_driver_init: Assertion 
`VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, 
VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed.
  Aborted (core dumped)

  $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4
  Press 'k' to see a list of keyboard shortcuts.
  Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  Redistribute latency...
  Redistribute latency...
  ERROR Internal error: could not render surface for 
file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0

  WORKAROUNDS:

   * Use weston instead of gnome-shell; or
   * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463
   * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 
1701463
   * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ...
   * $ mpv --hwdec --opengl-backend=wayland ...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: i965-va-driver 1.8.1-1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 13:40:38 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1685934] Re: ok button duplication

[Launchpad Bug Tracker]

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

** Changed in: indicator-datetime (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1685934

Title:
  ok button duplication

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  I think redundancy is often good but not for UI elements, see the
  attached screenshot.

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

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

[Touch-packages] [Bug 1684854] Re: The default behaviour for search domains changed from 16.10 to 17.04

[Vincenzo Pii]

I struggled with this long enough and took some notes about a workaround
here: https://thealarmclocksixam.com/2017/08/08/dns-configuration-with-
vpns-and-ubuntu-17-04-working-again/

I hope that this can help someone else as well.

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

Title:
  The default behaviour for search domains changed from 16.10 to 17.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Since Ubuntu 17.04 uses systemd-resolved for DNS lookups the default
  behaviour for search domains changed. By default systemd-resolved does
  not use the domain supplied by DHCP as a search domain.

  So network-manager should at least have an option to tell systemd-
  networkd to change it's behaviour. In systemd-networkd the
  corresponding option is named "UseDomains".

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

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

[Touch-packages] [Bug 1709461] StacktraceSource.txt

[Apport retracing service]

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1709461/+attachment/4928987/+files/StacktraceSource.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/1709461

Title:
  jackd assert failure: jackd:
  src/libieee1394/IsoHandlerManager.cpp:1795: bool
  IsoHandlerManager::IsoHandler::enable(int): Assertion `m_handle ==
  NULL' failed.

Status in jackd2 package in Ubuntu:
  New

Bug description:
  Daisy-chained devices, trying to select one for operation.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: jackd2 1.9.10+20150825git1ed50c92~dfsg-2ubuntu2
  ProcVersionSignature: Ubuntu 4.11.0-10.15-lowlatency 4.11.8
  Uname: Linux 4.11.0-10-lowlatency x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AssertionMessage: jackd: src/libieee1394/IsoHandlerManager.cpp:1795: bool 
IsoHandlerManager::IsoHandler::enable(int): Assertion `m_handle == NULL' failed.
  CrashCounter: 1
  CurrentDesktop: XFCE
  Date: Tue Aug  8 20:47:34 2017
  ExecutablePath: /usr/bin/jackd
  InstallationDate: Installed on 2011-10-14 (2125 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  ProcCmdline: jackd -d firewire -d fw:0 -r 96000 -p 512 -n 3
  Signal: 6
  SourcePackage: jackd2
  StacktraceTop:
   __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7f5fe688a1b7 "m_handle == NULL", 
file=file@entry=0x7f5fe6889058 "src/libieee1394/IsoHandlerManager.cpp", 
line=line@entry=1795, function=function@entry=0x7f5fe688ada0 "bool 
IsoHandlerManager::IsoHandler::enable(int)") at assert.c:92
   __GI___assert_fail (assertion=0x7f5fe688a1b7 "m_handle == NULL", 
file=0x7f5fe6889058 "src/libieee1394/IsoHandlerManager.cpp", line=1795, 
function=0x7f5fe688ada0 "bool IsoHandlerManager::IsoHandler::enable(int)") at 
assert.c:101
   IsoHandlerManager::IsoHandler::enable(int) () at /usr/lib/libffado.so.2
   IsoHandlerManager::IsoHandler::updateState() () at /usr/lib/libffado.so.2
   IsoHandlerManager::IsoTask::updateShadowMapHelper() () at 
/usr/lib/libffado.so.2
  Title: jackd assert failure: jackd: 
src/libieee1394/IsoHandlerManager.cpp:1795: bool 
IsoHandlerManager::IsoHandler::enable(int): Assertion `m_handle == NULL' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

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

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

[Touch-packages] [Bug 1709461] Stacktrace.txt

[Apport retracing service]

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1709461/+attachment/4928986/+files/Stacktrace.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/1709461

Title:
  jackd assert failure: jackd:
  src/libieee1394/IsoHandlerManager.cpp:1795: bool
  IsoHandlerManager::IsoHandler::enable(int): Assertion `m_handle ==
  NULL' failed.

Status in jackd2 package in Ubuntu:
  New

Bug description:
  Daisy-chained devices, trying to select one for operation.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: jackd2 1.9.10+20150825git1ed50c92~dfsg-2ubuntu2
  ProcVersionSignature: Ubuntu 4.11.0-10.15-lowlatency 4.11.8
  Uname: Linux 4.11.0-10-lowlatency x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AssertionMessage: jackd: src/libieee1394/IsoHandlerManager.cpp:1795: bool 
IsoHandlerManager::IsoHandler::enable(int): Assertion `m_handle == NULL' failed.
  CrashCounter: 1
  CurrentDesktop: XFCE
  Date: Tue Aug  8 20:47:34 2017
  ExecutablePath: /usr/bin/jackd
  InstallationDate: Installed on 2011-10-14 (2125 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  ProcCmdline: jackd -d firewire -d fw:0 -r 96000 -p 512 -n 3
  Signal: 6
  SourcePackage: jackd2
  StacktraceTop:
   __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7f5fe688a1b7 "m_handle == NULL", 
file=file@entry=0x7f5fe6889058 "src/libieee1394/IsoHandlerManager.cpp", 
line=line@entry=1795, function=function@entry=0x7f5fe688ada0 "bool 
IsoHandlerManager::IsoHandler::enable(int)") at assert.c:92
   __GI___assert_fail (assertion=0x7f5fe688a1b7 "m_handle == NULL", 
file=0x7f5fe6889058 "src/libieee1394/IsoHandlerManager.cpp", line=1795, 
function=0x7f5fe688ada0 "bool IsoHandlerManager::IsoHandler::enable(int)") at 
assert.c:101
   IsoHandlerManager::IsoHandler::enable(int) () at /usr/lib/libffado.so.2
   IsoHandlerManager::IsoHandler::updateState() () at /usr/lib/libffado.so.2
   IsoHandlerManager::IsoTask::updateShadowMapHelper() () at 
/usr/lib/libffado.so.2
  Title: jackd assert failure: jackd: 
src/libieee1394/IsoHandlerManager.cpp:1795: bool 
IsoHandlerManager::IsoHandler::enable(int): Assertion `m_handle == NULL' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

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

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

[Touch-packages] [Bug 1709461] ThreadStacktrace.txt

[Apport retracing service]

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1709461/+attachment/4928988/+files/ThreadStacktrace.txt

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

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

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/1709461

Title:
  jackd assert failure: jackd:
  src/libieee1394/IsoHandlerManager.cpp:1795: bool
  IsoHandlerManager::IsoHandler::enable(int): Assertion `m_handle ==
  NULL' failed.

Status in jackd2 package in Ubuntu:
  New

Bug description:
  Daisy-chained devices, trying to select one for operation.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: jackd2 1.9.10+20150825git1ed50c92~dfsg-2ubuntu2
  ProcVersionSignature: Ubuntu 4.11.0-10.15-lowlatency 4.11.8
  Uname: Linux 4.11.0-10-lowlatency x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AssertionMessage: jackd: src/libieee1394/IsoHandlerManager.cpp:1795: bool 
IsoHandlerManager::IsoHandler::enable(int): Assertion `m_handle == NULL' failed.
  CrashCounter: 1
  CurrentDesktop: XFCE
  Date: Tue Aug  8 20:47:34 2017
  ExecutablePath: /usr/bin/jackd
  InstallationDate: Installed on 2011-10-14 (2125 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  ProcCmdline: jackd -d firewire -d fw:0 -r 96000 -p 512 -n 3
  Signal: 6
  SourcePackage: jackd2
  StacktraceTop:
   __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7f5fe688a1b7 "m_handle == NULL", 
file=file@entry=0x7f5fe6889058 "src/libieee1394/IsoHandlerManager.cpp", 
line=line@entry=1795, function=function@entry=0x7f5fe688ada0 "bool 
IsoHandlerManager::IsoHandler::enable(int)") at assert.c:92
   __GI___assert_fail (assertion=0x7f5fe688a1b7 "m_handle == NULL", 
file=0x7f5fe6889058 "src/libieee1394/IsoHandlerManager.cpp", line=1795, 
function=0x7f5fe688ada0 "bool IsoHandlerManager::IsoHandler::enable(int)") at 
assert.c:101
   IsoHandlerManager::IsoHandler::enable(int) () at /usr/lib/libffado.so.2
   IsoHandlerManager::IsoHandler::updateState() () at /usr/lib/libffado.so.2
   IsoHandlerManager::IsoTask::updateShadowMapHelper() () at 
/usr/lib/libffado.so.2
  Title: jackd assert failure: jackd: 
src/libieee1394/IsoHandlerManager.cpp:1795: bool 
IsoHandlerManager::IsoHandler::enable(int): Assertion `m_handle == NULL' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

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

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

[Touch-packages] [Bug 1709461] [NEW] jackd assert failure: jackd: src/libieee1394/IsoHandlerManager.cpp:1795: bool IsoHandlerManager::IsoHandler::enable(int): Assertion `m_handle == NULL' failed.

[David Kastrup]

Public bug reported:

Daisy-chained devices, trying to select one for operation.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: jackd2 1.9.10+20150825git1ed50c92~dfsg-2ubuntu2
ProcVersionSignature: Ubuntu 4.11.0-10.15-lowlatency 4.11.8
Uname: Linux 4.11.0-10-lowlatency x86_64
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
AssertionMessage: jackd: src/libieee1394/IsoHandlerManager.cpp:1795: bool 
IsoHandlerManager::IsoHandler::enable(int): Assertion `m_handle == NULL' failed.
CrashCounter: 1
CurrentDesktop: XFCE
Date: Tue Aug  8 20:47:34 2017
ExecutablePath: /usr/bin/jackd
InstallationDate: Installed on 2011-10-14 (2125 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: jackd -d firewire -d fw:0 -r 96000 -p 512 -n 3
Signal: 6
SourcePackage: jackd2
StacktraceTop:
 __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7f5fe688a1b7 "m_handle == NULL", 
file=file@entry=0x7f5fe6889058 "src/libieee1394/IsoHandlerManager.cpp", 
line=line@entry=1795, function=function@entry=0x7f5fe688ada0 "bool 
IsoHandlerManager::IsoHandler::enable(int)") at assert.c:92
 __GI___assert_fail (assertion=0x7f5fe688a1b7 "m_handle == NULL", 
file=0x7f5fe6889058 "src/libieee1394/IsoHandlerManager.cpp", line=1795, 
function=0x7f5fe688ada0 "bool IsoHandlerManager::IsoHandler::enable(int)") at 
assert.c:101
 IsoHandlerManager::IsoHandler::enable(int) () at /usr/lib/libffado.so.2
 IsoHandlerManager::IsoHandler::updateState() () at /usr/lib/libffado.so.2
 IsoHandlerManager::IsoTask::updateShadowMapHelper() () at 
/usr/lib/libffado.so.2
Title: jackd assert failure: jackd: src/libieee1394/IsoHandlerManager.cpp:1795: 
bool IsoHandlerManager::IsoHandler::enable(int): Assertion `m_handle == NULL' 
failed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

** Affects: jackd2 (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-crash artful

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/1709461

Title:
  jackd assert failure: jackd:
  src/libieee1394/IsoHandlerManager.cpp:1795: bool
  IsoHandlerManager::IsoHandler::enable(int): Assertion `m_handle ==
  NULL' failed.

Status in jackd2 package in Ubuntu:
  New

Bug description:
  Daisy-chained devices, trying to select one for operation.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: jackd2 1.9.10+20150825git1ed50c92~dfsg-2ubuntu2
  ProcVersionSignature: Ubuntu 4.11.0-10.15-lowlatency 4.11.8
  Uname: Linux 4.11.0-10-lowlatency x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AssertionMessage: jackd: src/libieee1394/IsoHandlerManager.cpp:1795: bool 
IsoHandlerManager::IsoHandler::enable(int): Assertion `m_handle == NULL' failed.
  CrashCounter: 1
  CurrentDesktop: XFCE
  Date: Tue Aug  8 20:47:34 2017
  ExecutablePath: /usr/bin/jackd
  InstallationDate: Installed on 2011-10-14 (2125 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  ProcCmdline: jackd -d firewire -d fw:0 -r 96000 -p 512 -n 3
  Signal: 6
  SourcePackage: jackd2
  StacktraceTop:
   __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7f5fe688a1b7 "m_handle == NULL", 
file=file@entry=0x7f5fe6889058 "src/libieee1394/IsoHandlerManager.cpp", 
line=line@entry=1795, function=function@entry=0x7f5fe688ada0 "bool 
IsoHandlerManager::IsoHandler::enable(int)") at assert.c:92
   __GI___assert_fail (assertion=0x7f5fe688a1b7 "m_handle == NULL", 
file=0x7f5fe6889058 "src/libieee1394/IsoHandlerManager.cpp", line=1795, 
function=0x7f5fe688ada0 "bool IsoHandlerManager::IsoHandler::enable(int)") at 
assert.c:101
   IsoHandlerManager::IsoHandler::enable(int) () at /usr/lib/libffado.so.2
   IsoHandlerManager::IsoHandler::updateState() () at /usr/lib/libffado.so.2
   IsoHandlerManager::IsoTask::updateShadowMapHelper() () at 
/usr/lib/libffado.so.2
  Title: jackd assert failure: jackd: 
src/libieee1394/IsoHandlerManager.cpp:1795: bool 
IsoHandlerManager::IsoHandler::enable(int): Assertion `m_handle == NULL' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

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

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

[Touch-packages] [Bug 1709461] jackd assert failure: jackd: src/libieee1394/IsoHandlerManager.cpp:1795: bool IsoHandlerManager::IsoHandler::enable(int): Assertion `m_handle == NULL' failed.

[Apport retracing service]

StacktraceTop:
 __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7f5fe688a1b7 "m_handle == NULL", 
file=file@entry=0x7f5fe6889058 "src/libieee1394/IsoHandlerManager.cpp", 
line=line@entry=1795, function=function@entry=0x7f5fe688ada0 "bool 
IsoHandlerManager::IsoHandler::enable(int)") at assert.c:92
 __GI___assert_fail (assertion=0x7f5fe688a1b7 "m_handle == NULL", 
file=0x7f5fe6889058 "src/libieee1394/IsoHandlerManager.cpp", line=1795, 
function=0x7f5fe688ada0 "bool IsoHandlerManager::IsoHandler::enable(int)") at 
assert.c:101
 IsoHandlerManager::IsoHandler::enable(int) () from 
/tmp/apport_sandbox_3_Bb6j/usr/lib/libffado.so.2
 IsoHandlerManager::IsoHandler::updateState() () from 
/tmp/apport_sandbox_3_Bb6j/usr/lib/libffado.so.2
 IsoHandlerManager::IsoTask::updateShadowMapHelper() () from 
/tmp/apport_sandbox_3_Bb6j/usr/lib/libffado.so.2

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/1709461

Title:
  jackd assert failure: jackd:
  src/libieee1394/IsoHandlerManager.cpp:1795: bool
  IsoHandlerManager::IsoHandler::enable(int): Assertion `m_handle ==
  NULL' failed.

Status in jackd2 package in Ubuntu:
  New

Bug description:
  Daisy-chained devices, trying to select one for operation.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: jackd2 1.9.10+20150825git1ed50c92~dfsg-2ubuntu2
  ProcVersionSignature: Ubuntu 4.11.0-10.15-lowlatency 4.11.8
  Uname: Linux 4.11.0-10-lowlatency x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AssertionMessage: jackd: src/libieee1394/IsoHandlerManager.cpp:1795: bool 
IsoHandlerManager::IsoHandler::enable(int): Assertion `m_handle == NULL' failed.
  CrashCounter: 1
  CurrentDesktop: XFCE
  Date: Tue Aug  8 20:47:34 2017
  ExecutablePath: /usr/bin/jackd
  InstallationDate: Installed on 2011-10-14 (2125 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  ProcCmdline: jackd -d firewire -d fw:0 -r 96000 -p 512 -n 3
  Signal: 6
  SourcePackage: jackd2
  StacktraceTop:
   __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7f5fe688a1b7 "m_handle == NULL", 
file=file@entry=0x7f5fe6889058 "src/libieee1394/IsoHandlerManager.cpp", 
line=line@entry=1795, function=function@entry=0x7f5fe688ada0 "bool 
IsoHandlerManager::IsoHandler::enable(int)") at assert.c:92
   __GI___assert_fail (assertion=0x7f5fe688a1b7 "m_handle == NULL", 
file=0x7f5fe6889058 "src/libieee1394/IsoHandlerManager.cpp", line=1795, 
function=0x7f5fe688ada0 "bool IsoHandlerManager::IsoHandler::enable(int)") at 
assert.c:101
   IsoHandlerManager::IsoHandler::enable(int) () at /usr/lib/libffado.so.2
   IsoHandlerManager::IsoHandler::updateState() () at /usr/lib/libffado.so.2
   IsoHandlerManager::IsoTask::updateShadowMapHelper() () at 
/usr/lib/libffado.so.2
  Title: jackd assert failure: jackd: 
src/libieee1394/IsoHandlerManager.cpp:1795: bool 
IsoHandlerManager::IsoHandler::enable(int): Assertion `m_handle == NULL' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

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

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

[Touch-packages] [Bug 1709452] [NEW] Intell graphics

[Agustin Samman]

Public bug reported:

The HDMI stopped working suddenly. I tried re-install Intell Graphic drivers 
and still nothing.
I have a Dell Insipiron 5010 64 bit.
I ran de apport bug as the helped stated.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
Uname: Linux 4.4.0-89-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
BootLog:
 
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Aug  8 20:33:14 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.4.0-83-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.4.0-89-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 18) (prog-if 00 [VGA controller])
   Subsystem: Dell Core Processor Integrated Graphics Controller [1028:0447]
InstallationDate: Installed on 2014-10-05 (1038 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
MachineType: Dell Inc. Inspiron N5010
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=cbde2fc0-7e9c-48f9-b588-ea7014e028ae ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/26/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0WXY9J
dmi.board.vendor: Dell Inc.
dmi.board.version: A07
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A07
dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd07/26/2010:svnDellInc.:pnInspironN5010:pvrA07:rvnDellInc.:rn0WXY9J:rvrA07:cvnDellInc.:ct8:cvrA07:
dmi.product.name: Inspiron N5010
dmi.product.version: A07
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Aug  8 20:28:05 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id8940 
 vendor AUO
xserver.version: 2:1.18.4-0ubuntu0.3

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1709452

Title:
  Intell graphics

Status in xorg package in Ubuntu:
  New

Bug description:
  The HDMI stopped working suddenly. I tried re-install Intell Graphic drivers 
and still nothing.
  I have a Dell Insipiron 5010 64 bit.
  I ran de apport bug as the helped stated.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Uname: Linux 4.4.0-89-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  BootLog:
   
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Aug  8 20:33:14 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.4.0-83-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-89-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 18) (prog-if 00 [VGA controller])
 Subsystem: Dell Core Processor Integrated Graphics Controller [1028:0447]
  InstallationDate: 

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

[Eric Desrochers]

I tried the same exact reproducer (as described by iiro) using different
scenarios such as :

- Server image inside LXC and KVM guest
- Server image inside KVM guest
- Desktop image inside a KVM guest

and every time it worked well for me without any issue.

- Eric

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

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

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Triaged
Status in cups source package in Yakkety:
  Fix Released
Status in cups source package in Zesty:
  Fix Released

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

  [Impact]
  * fail to upgrade

  [testcase]
  Root cause is believed to be reproducible with:

  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:

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

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

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

[Touch-packages] [Bug 1709207] Re: package libperl5.24 5.24.1-7ubuntu1 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libperl5.24/changelog.Debian.gz' partilhado, que é diferente de

[FranciscoLima]

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

Thank you! I already did the correction.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
https://bugs.launchpad.net/bugs/1709207

Title:
  package libperl5.24 5.24.1-7ubuntu1 failed to install/upgrade: a
  tentar sobreescrever '/usr/share/doc/libperl5.24/changelog.Debian.gz'
  partilhado, que é diferente de outras instâncias do pacote
  libperl5.24:i386

Status in perl package in Ubuntu:
  New

Bug description:
  Simple scan application. Error installing driver

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libperl5.24 5.24.1-7ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Mon Aug  7 20:35:44 2017
  ErrorMessage: a tentar sobreescrever 
'/usr/share/doc/libperl5.24/changelog.Debian.gz' partilhado, que é diferente de 
outras instâncias do pacote libperl5.24:i386
  InstallationDate: Installed on 2017-07-30 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5~beta1
  SourcePackage: perl
  Title: package libperl5.24 5.24.1-7ubuntu1 failed to install/upgrade: a 
tentar sobreescrever '/usr/share/doc/libperl5.24/changelog.Debian.gz' 
partilhado, que é diferente de outras instâncias do pacote libperl5.24:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Iiro Laiho]

Here are log entries that result from the "sudo apt -t xenial-proposed
install cups-daemon"

Preparing to unpack .../libcupsppdc1_2.1.3-4ubuntu0.2_amd64.deb ...
Unpacking libcupsppdc1:amd64 (2.1.3-4ubuntu0.2) over (2.1.3-4) ...
Preparing to unpack .../libcupsmime1_2.1.3-4ubuntu0.2_amd64.deb ...
Unpacking libcupsmime1:amd64 (2.1.3-4ubuntu0.2) over (2.1.3-4) ...
Preparing to unpack .../libcupsimage2_2.1.3-4ubuntu0.2_amd64.deb ...
Unpacking libcupsimage2:amd64 (2.1.3-4ubuntu0.2) over (2.1.3-4) ...
Preparing to unpack .../libcupscgi1_2.1.3-4ubuntu0.2_amd64.deb ...
Unpacking libcupscgi1:amd64 (2.1.3-4ubuntu0.2) over (2.1.3-4) ...
Preparing to unpack .../cups-core-drivers_2.1.3-4ubuntu0.2_amd64.deb ...
Unpacking cups-core-drivers (2.1.3-4ubuntu0.2) over (2.1.3-4) ...
Preparing to unpack .../cups-server-common_2.1.3-4ubuntu0.2_all.deb ...
Unpacking cups-server-common (2.1.3-4ubuntu0.2) over (2.1.3-4) ...
Preparing to unpack .../cups-common_2.1.3-4ubuntu0.2_all.deb ...
Unpacking cups-common (2.1.3-4ubuntu0.2) over (2.1.3-4) ...
Preparing to unpack .../cups-daemon_2.1.3-4ubuntu0.2_amd64.deb ...
Job for cups.service canceled.
invoke-rc.d: initscript cups, action "stop" failed.
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
Job for cups.service canceled.
invoke-rc.d: initscript cups, action "stop" failed.
dpkg: error processing archive 
/var/cache/apt/archives/cups-daemon_2.1.3-4ubuntu0.2_amd64.deb (--unpack):
 subprocess new pre-removal script returned error exit status 1
Preparing to unpack .../cups-bsd_2.1.3-4ubuntu0.2_amd64.deb ...
Unpacking cups-bsd (2.1.3-4ubuntu0.2) over (2.1.3-4) ...
Preparing to unpack .../cups-client_2.1.3-4ubuntu0.2_amd64.deb ...
Unpacking cups-client (2.1.3-4ubuntu0.2) over (2.1.3-4) ...
Preparing to unpack .../libcups2_2.1.3-4ubuntu0.2_amd64.deb ...
Unpacking libcups2:amd64 (2.1.3-4ubuntu0.2) over (2.1.3-4) ...
Preparing to unpack .../cups_2.1.3-4ubuntu0.2_amd64.deb ...
Unpacking cups (2.1.3-4ubuntu0.2) over (2.1.3-4) ...
Processing triggers for libc-bin (2.23-0ubuntu9) ...
Processing triggers for doc-base (0.10.7) ...
Processing 1 changed doc-base file...
Processing triggers for man-db (2.7.5-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/cups-daemon_2.1.3-4ubuntu0.2_amd64.deb
Log ended: 2017-08-08  19:32:01


And here is what happens when I try to run "apt upgrade" after that:

il@il-VirtualBox:~$ sudo apt upgrade
Reading package lists... Done
Building dependency tree  
Reading state information... Done
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
 cups : Depends: cups-daemon (>= 2.1.3-4ubuntu0.2)
 cups-core-drivers : Depends: cups-daemon (>= 2.1.3-4ubuntu0.2)
 cups-daemon : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is installed
E: Unmet dependencies. Try using -f.

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

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

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Triaged
Status in cups source package in Yakkety:
  Fix Released
Status in cups source package in Zesty:
  Fix Released

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

  [Impact]
  * fail to upgrade

  [testcase]
  Root cause is believed to be reproducible with:

  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:

  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 

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

[Iiro Laiho]

The last step in #109 is important. When doing the upgrade of cups-
daemon, it may look like it succeeded but with warnings. However, the
packaging system does break down and will became unable to successfully
do "apt upgrade".

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

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

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Triaged
Status in cups source package in Yakkety:
  Fix Released
Status in cups source package in Zesty:
  Fix Released

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

  [Impact]
  * fail to upgrade

  [testcase]
  Root cause is believed to be reproducible with:

  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:

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

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

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

[Touch-packages] [Bug 1709207] Re: package libperl5.24 5.24.1-7ubuntu1 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libperl5.24/changelog.Debian.gz' partilhado, que é diferente de

[Hans Joachim Desserud]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1574351, so it 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. Feel free to continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1574351
   package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite 
shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different 
from other instances of package libperl5.22:i386

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
https://bugs.launchpad.net/bugs/1709207

Title:
  package libperl5.24 5.24.1-7ubuntu1 failed to install/upgrade: a
  tentar sobreescrever '/usr/share/doc/libperl5.24/changelog.Debian.gz'
  partilhado, que é diferente de outras instâncias do pacote
  libperl5.24:i386

Status in perl package in Ubuntu:
  New

Bug description:
  Simple scan application. Error installing driver

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libperl5.24 5.24.1-7ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Mon Aug  7 20:35:44 2017
  ErrorMessage: a tentar sobreescrever 
'/usr/share/doc/libperl5.24/changelog.Debian.gz' partilhado, que é diferente de 
outras instâncias do pacote libperl5.24:i386
  InstallationDate: Installed on 2017-07-30 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5~beta1
  SourcePackage: perl
  Title: package libperl5.24 5.24.1-7ubuntu1 failed to install/upgrade: a 
tentar sobreescrever '/usr/share/doc/libperl5.24/changelog.Debian.gz' 
partilhado, que é diferente de outras instâncias do pacote libperl5.24:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Iiro Laiho]

Nope, the problem is still present in -proposed. Here's a more detailed
procedure of reproducing the bug:

- Do a clean Ubuntu install. I installed Ubuntu from the 16.04.3 desktop media 
to a VirtualBox VM.
- Do a "apt update && apt upgrade" as usual
- Per the instructions from , 
do what is told in the "Selective upgrading from -proposed" section.
- Add a stuck job to the CUPS queue. My way to do this is to add a network 
printer with URI "socket://0.0.0.0". As the driver I used the "Generic PCL 
Laser". Now, print a test page.
- Now we should be able to pinpoint the packages we want to upgrade to 
-proposed. Run command "sudo apt -t xenial-proposed install cups-daemon"
- Now we have a broken packaging system. The command "sudo apt upgrade" will 
fail.

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

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

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Triaged
Status in cups source package in Yakkety:
  Fix Released
Status in cups source package in Zesty:
  Fix Released

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

  [Impact]
  * fail to upgrade

  [testcase]
  Root cause is believed to be reproducible with:

  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:

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

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

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

[Touch-packages] [Bug 1709163] ProcCpuinfoMinimal.txt

[kenjo]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1709163/+attachment/4928917/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1709163

Title:
  default output changes from intel builtin to hdmi when display is
  turned off. yes off not on

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  So if I have sound output selected to be the intel sound on the
  mainboard and turn off one of my two displays the audio out is changed
  to HDMI. YES OFF it's not a typo.

  The Display I turn off is connected to displayport and do not even
  have HDMI. The audio is switched over to the still active display.

  If I then turn the display back it's still hdmi. If I then turn off
  the display that has HDMI out connected. the audio is still connected
  to that display. since its actually off I hear no sound but pulseaudio
  still connect to it.

  I have to manually open the GUI tool and change back to the correct
  output when the display is turned off or when the display is blanked.
  or suspend/resume.

  I attache the output of "pacmd list-cards  && pacmd list-sinks"
  ok   -> ps_w1.txt
  fail -> ps_f1.txt
  --- 
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kenjo  3721 F pulseaudio
   /dev/snd/controlC1:  kenjo  3721 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2015-10-18 (659 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  Package: pulseaudio 1:10.0-2ubuntu1
  PackageArchitecture: amd64
  Tags:  artful
  Uname: Linux 4.12.1-041201-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-06-10 (59 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare 
sudo video wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.I0
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A GAMING M7 (MS-7976)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.I0:bd04/25/2017:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7976
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-04-23T00:00:29.066742

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

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

[Touch-packages] [Bug 1709163] PulseList.txt

[kenjo]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1709163/+attachment/4928919/+files/PulseList.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1709163

Title:
  default output changes from intel builtin to hdmi when display is
  turned off. yes off not on

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  So if I have sound output selected to be the intel sound on the
  mainboard and turn off one of my two displays the audio out is changed
  to HDMI. YES OFF it's not a typo.

  The Display I turn off is connected to displayport and do not even
  have HDMI. The audio is switched over to the still active display.

  If I then turn the display back it's still hdmi. If I then turn off
  the display that has HDMI out connected. the audio is still connected
  to that display. since its actually off I hear no sound but pulseaudio
  still connect to it.

  I have to manually open the GUI tool and change back to the correct
  output when the display is turned off or when the display is blanked.
  or suspend/resume.

  I attache the output of "pacmd list-cards  && pacmd list-sinks"
  ok   -> ps_w1.txt
  fail -> ps_f1.txt
  --- 
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kenjo  3721 F pulseaudio
   /dev/snd/controlC1:  kenjo  3721 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2015-10-18 (659 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  Package: pulseaudio 1:10.0-2ubuntu1
  PackageArchitecture: amd64
  Tags:  artful
  Uname: Linux 4.12.1-041201-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-06-10 (59 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare 
sudo video wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.I0
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A GAMING M7 (MS-7976)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.I0:bd04/25/2017:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7976
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-04-23T00:00:29.066742

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

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

[Touch-packages] [Bug 1709163] Dependencies.txt

[kenjo]

apport information

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1709163

Title:
  default output changes from intel builtin to hdmi when display is
  turned off. yes off not on

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  So if I have sound output selected to be the intel sound on the
  mainboard and turn off one of my two displays the audio out is changed
  to HDMI. YES OFF it's not a typo.

  The Display I turn off is connected to displayport and do not even
  have HDMI. The audio is switched over to the still active display.

  If I then turn the display back it's still hdmi. If I then turn off
  the display that has HDMI out connected. the audio is still connected
  to that display. since its actually off I hear no sound but pulseaudio
  still connect to it.

  I have to manually open the GUI tool and change back to the correct
  output when the display is turned off or when the display is blanked.
  or suspend/resume.

  I attache the output of "pacmd list-cards  && pacmd list-sinks"
  ok   -> ps_w1.txt
  fail -> ps_f1.txt
  --- 
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kenjo  3721 F pulseaudio
   /dev/snd/controlC1:  kenjo  3721 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2015-10-18 (659 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  Package: pulseaudio 1:10.0-2ubuntu1
  PackageArchitecture: amd64
  Tags:  artful
  Uname: Linux 4.12.1-041201-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-06-10 (59 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare 
sudo video wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.I0
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A GAMING M7 (MS-7976)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.I0:bd04/25/2017:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7976
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-04-23T00:00:29.066742

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

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

[Touch-packages] [Bug 1709163] JournalErrors.txt

[kenjo]

apport information

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1709163

Title:
  default output changes from intel builtin to hdmi when display is
  turned off. yes off not on

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  So if I have sound output selected to be the intel sound on the
  mainboard and turn off one of my two displays the audio out is changed
  to HDMI. YES OFF it's not a typo.

  The Display I turn off is connected to displayport and do not even
  have HDMI. The audio is switched over to the still active display.

  If I then turn the display back it's still hdmi. If I then turn off
  the display that has HDMI out connected. the audio is still connected
  to that display. since its actually off I hear no sound but pulseaudio
  still connect to it.

  I have to manually open the GUI tool and change back to the correct
  output when the display is turned off or when the display is blanked.
  or suspend/resume.

  I attache the output of "pacmd list-cards  && pacmd list-sinks"
  ok   -> ps_w1.txt
  fail -> ps_f1.txt
  --- 
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kenjo  3721 F pulseaudio
   /dev/snd/controlC1:  kenjo  3721 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2015-10-18 (659 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  Package: pulseaudio 1:10.0-2ubuntu1
  PackageArchitecture: amd64
  Tags:  artful
  Uname: Linux 4.12.1-041201-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-06-10 (59 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare 
sudo video wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.I0
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A GAMING M7 (MS-7976)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.I0:bd04/25/2017:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7976
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-04-23T00:00:29.066742

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

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

[Touch-packages] [Bug 1709163] ProcEnviron.txt

[kenjo]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1709163/+attachment/4928918/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1709163

Title:
  default output changes from intel builtin to hdmi when display is
  turned off. yes off not on

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  So if I have sound output selected to be the intel sound on the
  mainboard and turn off one of my two displays the audio out is changed
  to HDMI. YES OFF it's not a typo.

  The Display I turn off is connected to displayport and do not even
  have HDMI. The audio is switched over to the still active display.

  If I then turn the display back it's still hdmi. If I then turn off
  the display that has HDMI out connected. the audio is still connected
  to that display. since its actually off I hear no sound but pulseaudio
  still connect to it.

  I have to manually open the GUI tool and change back to the correct
  output when the display is turned off or when the display is blanked.
  or suspend/resume.

  I attache the output of "pacmd list-cards  && pacmd list-sinks"
  ok   -> ps_w1.txt
  fail -> ps_f1.txt
  --- 
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kenjo  3721 F pulseaudio
   /dev/snd/controlC1:  kenjo  3721 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2015-10-18 (659 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  Package: pulseaudio 1:10.0-2ubuntu1
  PackageArchitecture: amd64
  Tags:  artful
  Uname: Linux 4.12.1-041201-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-06-10 (59 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare 
sudo video wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.I0
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A GAMING M7 (MS-7976)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.I0:bd04/25/2017:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7976
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-04-23T00:00:29.066742

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

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

[Touch-packages] [Bug 1709163] CurrentDmesg.txt

[kenjo]

apport information

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1709163

Title:
  default output changes from intel builtin to hdmi when display is
  turned off. yes off not on

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  So if I have sound output selected to be the intel sound on the
  mainboard and turn off one of my two displays the audio out is changed
  to HDMI. YES OFF it's not a typo.

  The Display I turn off is connected to displayport and do not even
  have HDMI. The audio is switched over to the still active display.

  If I then turn the display back it's still hdmi. If I then turn off
  the display that has HDMI out connected. the audio is still connected
  to that display. since its actually off I hear no sound but pulseaudio
  still connect to it.

  I have to manually open the GUI tool and change back to the correct
  output when the display is turned off or when the display is blanked.
  or suspend/resume.

  I attache the output of "pacmd list-cards  && pacmd list-sinks"
  ok   -> ps_w1.txt
  fail -> ps_f1.txt
  --- 
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kenjo  3721 F pulseaudio
   /dev/snd/controlC1:  kenjo  3721 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2015-10-18 (659 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  Package: pulseaudio 1:10.0-2ubuntu1
  PackageArchitecture: amd64
  Tags:  artful
  Uname: Linux 4.12.1-041201-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-06-10 (59 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare 
sudo video wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.I0
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A GAMING M7 (MS-7976)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.I0:bd04/25/2017:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7976
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-04-23T00:00:29.066742

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

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

[Touch-packages] [Bug 1709163] Re: default output changes from intel builtin to hdmi when display is turned off. yes off not on

[kenjo]

apport information

** Tags added: apport-collected artful

** Description changed:

  So if I have sound output selected to be the intel sound on the
  mainboard and turn off one of my two displays the audio out is changed
  to HDMI. YES OFF it's not a typo.
  
  The Display I turn off is connected to displayport and do not even have
  HDMI. The audio is switched over to the still active display.
  
  If I then turn the display back it's still hdmi. If I then turn off the
  display that has HDMI out connected. the audio is still connected to
  that display. since its actually off I hear no sound but pulseaudio
  still connect to it.
  
  I have to manually open the GUI tool and change back to the correct
  output when the display is turned off or when the display is blanked. or
  suspend/resume.
  
  I attache the output of "pacmd list-cards  && pacmd list-sinks"
  ok   -> ps_w1.txt
  fail -> ps_f1.txt
+ --- 
+ ApportVersion: 2.20.6-0ubuntu4
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  kenjo  3721 F pulseaudio
+  /dev/snd/controlC1:  kenjo  3721 F pulseaudio
+ CurrentDesktop: GNOME
+ DistroRelease: Ubuntu 17.10
+ InstallationDate: Installed on 2015-10-18 (659 days ago)
+ InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
+ Package: pulseaudio 1:10.0-2ubuntu1
+ PackageArchitecture: amd64
+ Tags:  artful
+ Uname: Linux 4.12.1-041201-generic x86_64
+ UpgradeStatus: Upgraded to artful on 2017-06-10 (59 days ago)
+ UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare 
sudo video wireshark
+ _MarkForUpload: True
+ dmi.bios.date: 04/25/2017
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 1.I0
+ dmi.board.asset.tag: Default string
+ dmi.board.name: Z170A GAMING M7 (MS-7976)
+ dmi.board.vendor: MSI
+ dmi.board.version: 1.0
+ dmi.chassis.asset.tag: Default string
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: MSI
+ dmi.chassis.version: 1.0
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.I0:bd04/25/2017:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0:
+ dmi.product.family: Default string
+ dmi.product.name: MS-7976
+ dmi.product.version: 1.0
+ dmi.sys.vendor: MSI
+ modified.conffile..etc.pulse.daemon.conf: [modified]
+ mtime.conffile..etc.pulse.daemon.conf: 2016-04-23T00:00:29.066742

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1709163/+attachment/4928913/+files/AlsaInfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1709163

Title:
  default output changes from intel builtin to hdmi when display is
  turned off. yes off not on

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  So if I have sound output selected to be the intel sound on the
  mainboard and turn off one of my two displays the audio out is changed
  to HDMI. YES OFF it's not a typo.

  The Display I turn off is connected to displayport and do not even
  have HDMI. The audio is switched over to the still active display.

  If I then turn the display back it's still hdmi. If I then turn off
  the display that has HDMI out connected. the audio is still connected
  to that display. since its actually off I hear no sound but pulseaudio
  still connect to it.

  I have to manually open the GUI tool and change back to the correct
  output when the display is turned off or when the display is blanked.
  or suspend/resume.

  I attache the output of "pacmd list-cards  && pacmd list-sinks"
  ok   -> ps_w1.txt
  fail -> ps_f1.txt
  --- 
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kenjo  3721 F pulseaudio
   /dev/snd/controlC1:  kenjo  3721 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2015-10-18 (659 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  Package: pulseaudio 1:10.0-2ubuntu1
  PackageArchitecture: amd64
  Tags:  artful
  Uname: Linux 4.12.1-041201-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-06-10 (59 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare 
sudo video wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.I0
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A GAMING M7 (MS-7976)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.I0:bd04/25/2017:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7976
  dmi.product.version: 1.0

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

[Eric Desrochers]

@iiro, yes I tried your reproducer a couple of time without success.

- Clean Ubuntu install
- Install updates
- Enable -proposed
- Make sure that cupsd is running with stuck job using an invalid printer IP

--
▼ ID ▼  NameUserSizePages   State   Control
Bug1642966-1Unknown Withheld1k  3   processing since
"The printer is not responding."
--

- Update cups-daemon.

and nothing went wrong on my side.

Am I missing something ?

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

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

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Triaged
Status in cups source package in Yakkety:
  Fix Released
Status in cups source package in Zesty:
  Fix Released

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

  [Impact]
  * fail to upgrade

  [testcase]
  Root cause is believed to be reproducible with:

  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:

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

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

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

[Touch-packages] [Bug 1709384] [NEW] failed to unmount filesystems during shutdown, reboot hangs

[ben thielsen]

Public bug reported:

i'd done a new install of 17.04, and this had been working ok.  this
morning, i did an update, and now the system complains about being
unable to unmount certain filesystems, as well as hanging during the
shutdown process upon displaying "[ ok ] reached target shutdown"

Aug  8 16:11:48 template systemd[1]: Failed unmounting /home/foo.example.com.
Aug  8 16:11:49 template systemd[1]: Failed unmounting /var/log.
Aug  8 16:11:49 template systemd[1]: Failed unmounting /tmp.
Aug  8 16:11:49 template systemd[1]: Failed unmounting /home.
Aug  8 16:11:49 template systemd[1]: Failed unmounting /var.

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

2] >apt-cache policy systemd
systemd:
  Installed: 232-21ubuntu5
  Candidate: 232-21ubuntu5
  Version table:
 *** 232-21ubuntu5 500
500 http://us.archive.ubuntu.com/ubuntu zesty-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu zesty-security/main amd64 Packages
100 /var/lib/dpkg/status
 232-21ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages

3] i expected the system to not fail when unmounting filesystems during shutdown
4] it did

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1709384

Title:
  failed to unmount filesystems during shutdown, reboot hangs

Status in systemd package in Ubuntu:
  New

Bug description:
  i'd done a new install of 17.04, and this had been working ok.  this
  morning, i did an update, and now the system complains about being
  unable to unmount certain filesystems, as well as hanging during the
  shutdown process upon displaying "[ ok ] reached target shutdown"

  Aug  8 16:11:48 template systemd[1]: Failed unmounting /home/foo.example.com.
  Aug  8 16:11:49 template systemd[1]: Failed unmounting /var/log.
  Aug  8 16:11:49 template systemd[1]: Failed unmounting /tmp.
  Aug  8 16:11:49 template systemd[1]: Failed unmounting /home.
  Aug  8 16:11:49 template systemd[1]: Failed unmounting /var.

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

  2] >apt-cache policy systemd
  systemd:
Installed: 232-21ubuntu5
Candidate: 232-21ubuntu5
Version table:
   *** 232-21ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu zesty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu zesty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   232-21ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages

  3] i expected the system to not fail when unmounting filesystems during 
shutdown
  4] it did

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

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

[Touch-packages] [Bug 1709358] [NEW] Udev android rules for manufacter id 18d1 do not includes device id 4ee7

[José Francisco Tello Ropero]

Public bug reported:

After install android-tools-adb

Udev android rules for vendor id 18d1 do not includes device id 4ee7.
For example, my Nexus 4 is identified as 18d1:4ee7 using lsusb command.

70-android-tools-adb.rules must include 4ee7 as a valid device for 18d1
vendor.

Workaround is to add that rule on custom file at /etc/udev/rules.d/
until package will fixed.

** Affects: android-tools (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to android-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1709358

Title:
  Udev android rules for manufacter id 18d1 do not includes device id
  4ee7

Status in android-tools package in Ubuntu:
  New

Bug description:
  After install android-tools-adb

  Udev android rules for vendor id 18d1 do not includes device id 4ee7.
  For example, my Nexus 4 is identified as 18d1:4ee7 using lsusb
  command.

  70-android-tools-adb.rules must include 4ee7 as a valid device for
  18d1 vendor.

  Workaround is to add that rule on custom file at /etc/udev/rules.d/
  until package will fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1709358/+subscriptions

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

[Touch-packages] [Bug 1709175] Re: remove init.d and upstart files

[Dimitri John Ledkov]

Was pending testing.
I am aware of the affect onto perl transition.
This is now good to go in.

** Tags removed: block-proposed

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

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

** Description changed:

  remove init.d and upstart files
+ 
+ update - upstart file removed, init.d file in use in the systemd service
+ file.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1709175

Title:
  remove init.d and upstart files

Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  remove init.d and upstart files

  update - upstart file removed, init.d file in use in the systemd
  service file.

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

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

[Touch-packages] [Bug 1709334] Re: package libunity9 7.1.4+16.10.20160516-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-loader', which is different from other in

[Apport retracing service]

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunity in Ubuntu.
https://bugs.launchpad.net/bugs/1709334

Title:
  package libunity9 7.1.4+16.10.20160516-0ubuntu1 failed to
  install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-
  loader', which is different from other instances of package
  libunity9:i386

Status in libunity package in Ubuntu:
  New

Bug description:
  there is just the error messagebox. nothing else.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libunity9 7.1.4+16.10.20160516-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Tue Aug  8 14:42:16 2017
  DuplicateSignature:
   package:libunity9:7.1.4+16.10.20160516-0ubuntu1
   Unpacking libunity9:i386 (7.1.4+16.10.20160516-0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-WExc8X/199-libunity9_7.1.4+16.10.20160516-0ubuntu1_i386.deb
 (--unpack):
trying to overwrite shared '/usr/bin/unity-scope-loader', which is 
different from other instances of package libunity9:i386
  ErrorMessage: trying to overwrite shared '/usr/bin/unity-scope-loader', which 
is different from other instances of package libunity9:i386
  InstallationDate: Installed on 2017-08-07 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: libunity
  Title: package libunity9 7.1.4+16.10.20160516-0ubuntu1 failed to 
install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-loader', 
which is different from other instances of package libunity9:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1628478] Re: Mir servers crash when using the Nvidia driver

[Alan Griffiths]

** Changed in: mir
 Assignee: Alberto Aguirre (albaguirre) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1628478

Title:
  Mir servers crash when using the Nvidia driver

Status in Mir:
  Triaged
Status in mir package in Ubuntu:
  Triaged

Bug description:
  I select Unity8 from the log in screen, type in my credentials and it
  just hangs.

  Intel® Core™ i7-4710HQ CPU @ 2.50GHz × 8 
  GeForce GTX 860M/PCIe/SSE2

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

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

[Touch-packages] [Bug 1709334] [NEW] package libunity9 7.1.4+16.10.20160516-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-loader', which is different from other

[Lars Niesen]

Public bug reported:

there is just the error messagebox. nothing else.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libunity9 7.1.4+16.10.20160516-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
Uname: Linux 4.10.0-30-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Date: Tue Aug  8 14:42:16 2017
DuplicateSignature:
 package:libunity9:7.1.4+16.10.20160516-0ubuntu1
 Unpacking libunity9:i386 (7.1.4+16.10.20160516-0ubuntu1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-WExc8X/199-libunity9_7.1.4+16.10.20160516-0ubuntu1_i386.deb
 (--unpack):
  trying to overwrite shared '/usr/bin/unity-scope-loader', which is different 
from other instances of package libunity9:i386
ErrorMessage: trying to overwrite shared '/usr/bin/unity-scope-loader', which 
is different from other instances of package libunity9:i386
InstallationDate: Installed on 2017-08-07 (1 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: libunity
Title: package libunity9 7.1.4+16.10.20160516-0ubuntu1 failed to 
install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-loader', 
which is different from other instances of package libunity9:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package package-conflict zesty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunity in Ubuntu.
https://bugs.launchpad.net/bugs/1709334

Title:
  package libunity9 7.1.4+16.10.20160516-0ubuntu1 failed to
  install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-
  loader', which is different from other instances of package
  libunity9:i386

Status in libunity package in Ubuntu:
  New

Bug description:
  there is just the error messagebox. nothing else.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libunity9 7.1.4+16.10.20160516-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Tue Aug  8 14:42:16 2017
  DuplicateSignature:
   package:libunity9:7.1.4+16.10.20160516-0ubuntu1
   Unpacking libunity9:i386 (7.1.4+16.10.20160516-0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-WExc8X/199-libunity9_7.1.4+16.10.20160516-0ubuntu1_i386.deb
 (--unpack):
trying to overwrite shared '/usr/bin/unity-scope-loader', which is 
different from other instances of package libunity9:i386
  ErrorMessage: trying to overwrite shared '/usr/bin/unity-scope-loader', which 
is different from other instances of package libunity9:i386
  InstallationDate: Installed on 2017-08-07 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: libunity
  Title: package libunity9 7.1.4+16.10.20160516-0ubuntu1 failed to 
install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-loader', 
which is different from other instances of package libunity9:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1704027] Re: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: package util-linux is not ready for configuration cannot configure (current status 'half-installed')

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1704027

Title:
  package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade:
  package util-linux is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in dpkg package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  1. Ubuntu 16.04.2 LTS

  2. 2.27.1-6ubuntu3.3

  3. Nothing

  4. An error message stating the package could not be installed popped
  up.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jul 13 01:33:20 2017
  DpkgTerminalLog:
   dpkg: error processing package util-linux (--configure):
package util-linux is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package util-linux is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-02-04 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: 
package util-linux is not ready for configuration  cannot configure (current 
status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1704027] Re: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: package util-linux is not ready for configuration cannot configure (current status 'half-installed')

[Launchpad Bug Tracker]

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

** Changed in: util-linux (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1704027

Title:
  package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade:
  package util-linux is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in dpkg package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  1. Ubuntu 16.04.2 LTS

  2. 2.27.1-6ubuntu3.3

  3. Nothing

  4. An error message stating the package could not be installed popped
  up.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jul 13 01:33:20 2017
  DpkgTerminalLog:
   dpkg: error processing package util-linux (--configure):
package util-linux is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package util-linux is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-02-04 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: 
package util-linux is not ready for configuration  cannot configure (current 
status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1647285] Re: SSL trust not system-wide

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to p11-kit in Ubuntu.
https://bugs.launchpad.net/bugs/1647285

Title:
  SSL trust not system-wide

Status in ca-certificates package in Ubuntu:
  Confirmed
Status in nss package in Ubuntu:
  Confirmed
Status in p11-kit package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  When I install a corporate CA trust root with update-ca-certificates,
  it doesn't seem to work everywhere. Various things like Firefox,
  Evolution, Chrome, etc. all fail to trust the newly-installed trusted
  CA.

  This ought to work, and does on other distributions. In p11-kit there
  is a module p11-kit-trust.so which can be used as a drop-in
  replacement for NSS's own libnssckbi.so trust root module, but which
  reads from the system's configured trust setup instead of the hard-
  coded version.

  This allows us to install the corporate CAs just once, and then file a
  bug against any package that *doesn't* then trust them.

  See https://fedoraproject.org/wiki/Features/SharedSystemCertificates
  for some of the historical details from when this feature was first
  implemented, but this is all now supported upstream and not at all
  distribution-specific. There shouldn't be any significant work
  required; it's mostly just a case of configuring and building it to
  make use of this functionality. (With 'alternatives' to let you
  substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+subscriptions

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

[Touch-packages] [Bug 1647285] Re: SSL trust not system-wide

[Launchpad Bug Tracker]

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

** Changed in: ca-certificates (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to p11-kit in Ubuntu.
https://bugs.launchpad.net/bugs/1647285

Title:
  SSL trust not system-wide

Status in ca-certificates package in Ubuntu:
  Confirmed
Status in nss package in Ubuntu:
  Confirmed
Status in p11-kit package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  When I install a corporate CA trust root with update-ca-certificates,
  it doesn't seem to work everywhere. Various things like Firefox,
  Evolution, Chrome, etc. all fail to trust the newly-installed trusted
  CA.

  This ought to work, and does on other distributions. In p11-kit there
  is a module p11-kit-trust.so which can be used as a drop-in
  replacement for NSS's own libnssckbi.so trust root module, but which
  reads from the system's configured trust setup instead of the hard-
  coded version.

  This allows us to install the corporate CAs just once, and then file a
  bug against any package that *doesn't* then trust them.

  See https://fedoraproject.org/wiki/Features/SharedSystemCertificates
  for some of the historical details from when this feature was first
  implemented, but this is all now supported upstream and not at all
  distribution-specific. There shouldn't be any significant work
  required; it's mostly just a case of configuring and building it to
  make use of this functionality. (With 'alternatives' to let you
  substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+subscriptions

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

[Touch-packages] [Bug 1647285] Re: SSL trust not system-wide

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to p11-kit in Ubuntu.
https://bugs.launchpad.net/bugs/1647285

Title:
  SSL trust not system-wide

Status in ca-certificates package in Ubuntu:
  Confirmed
Status in nss package in Ubuntu:
  Confirmed
Status in p11-kit package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  When I install a corporate CA trust root with update-ca-certificates,
  it doesn't seem to work everywhere. Various things like Firefox,
  Evolution, Chrome, etc. all fail to trust the newly-installed trusted
  CA.

  This ought to work, and does on other distributions. In p11-kit there
  is a module p11-kit-trust.so which can be used as a drop-in
  replacement for NSS's own libnssckbi.so trust root module, but which
  reads from the system's configured trust setup instead of the hard-
  coded version.

  This allows us to install the corporate CAs just once, and then file a
  bug against any package that *doesn't* then trust them.

  See https://fedoraproject.org/wiki/Features/SharedSystemCertificates
  for some of the historical details from when this feature was first
  implemented, but this is all now supported upstream and not at all
  distribution-specific. There shouldn't be any significant work
  required; it's mostly just a case of configuring and building it to
  make use of this functionality. (With 'alternatives' to let you
  substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+subscriptions

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

[Touch-packages] [Bug 1647285] Re: SSL trust not system-wide

[Launchpad Bug Tracker]

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

** Changed in: p11-kit (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to p11-kit in Ubuntu.
https://bugs.launchpad.net/bugs/1647285

Title:
  SSL trust not system-wide

Status in ca-certificates package in Ubuntu:
  Confirmed
Status in nss package in Ubuntu:
  Confirmed
Status in p11-kit package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  When I install a corporate CA trust root with update-ca-certificates,
  it doesn't seem to work everywhere. Various things like Firefox,
  Evolution, Chrome, etc. all fail to trust the newly-installed trusted
  CA.

  This ought to work, and does on other distributions. In p11-kit there
  is a module p11-kit-trust.so which can be used as a drop-in
  replacement for NSS's own libnssckbi.so trust root module, but which
  reads from the system's configured trust setup instead of the hard-
  coded version.

  This allows us to install the corporate CAs just once, and then file a
  bug against any package that *doesn't* then trust them.

  See https://fedoraproject.org/wiki/Features/SharedSystemCertificates
  for some of the historical details from when this feature was first
  implemented, but this is all now supported upstream and not at all
  distribution-specific. There shouldn't be any significant work
  required; it's mostly just a case of configuring and building it to
  make use of this functionality. (With 'alternatives' to let you
  substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+subscriptions

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

[Touch-packages] [Bug 1689820] Re: /usr/lib/packagekit/packagekitd:11:pkgCache::Iterator:AcqPackageKitStatus::updateStatus:AcqPackageKitStatus::Fail:pkgAcquire::Worker::RunMessages:pkgAcquire::Worker:

[Martin Pitt]

** Description changed:

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
packagekit.  This problem was most recently seen with package version 
0.8.17-4ubuntu6~gcc5.4ubuntu1.1, the problem page at 
https://errors.ubuntu.com/problem/8c37a6988b890cc46b415972ef1e2ca746f9ffcc 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.
+ 
+ SRU INFORMATION
+ ===
+  * Impact: PackageKit immediately crashes in GetUpdateDetail()..
+ 
+  * Test case:
+- Be on a system (container, VM, or real iron) with at least one 
upgradeable package. If you don't have one, downgrade tzdata:
+   sudo apt-get install tzdata=2016j-0ubuntu0.16.04
+- Run "pkcon get-updates" to see upgradeable packages.
+- Run "pkcon get-update-detail tzdata" (or for a different package).
+- Current PackageKit immediately crashes (message from pkcon and systemctl 
status packagekit), with this fix it should survive and show some data 
(changelog doesn't work though).
+ 
+  * Regression potential: Update details are currently completely broken,
+ so very little to regress there. As for dropping the browser plugin
+ package: The current package stopped working long ago with current
+ firefox; however, the package from xenial-release will still be around.
+ All in all this shouldn't change anything visible.
+ 
+  * Upstream fix: https://github.com/hughsie/PackageKit/commit/18c56fa52
+ (only the acqpkitstatus.cpp bit)
+ 
+  * Downstream packaging change to drop browser plugin:
+ https://anonscm.debian.org/git/pkg-
+ packagekit/packagekit.git/commit/?id=b98a978322

** Description changed:

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
packagekit.  This problem was most recently seen with package version 
0.8.17-4ubuntu6~gcc5.4ubuntu1.1, the problem page at 
https://errors.ubuntu.com/problem/8c37a6988b890cc46b415972ef1e2ca746f9ffcc 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.
  
  SRU INFORMATION
  ===
-  * Impact: PackageKit immediately crashes in GetUpdateDetail()..
+  * Impact: PackageKit immediately crashes in GetUpdateDetail()
  
-  * Test case:
-- Be on a system (container, VM, or real iron) with at least one 
upgradeable package. If you don't have one, downgrade tzdata:
-   sudo apt-get install tzdata=2016j-0ubuntu0.16.04
-- Run "pkcon get-updates" to see upgradeable packages.
-- Run "pkcon get-update-detail tzdata" (or for a different package).
-- Current PackageKit immediately crashes (message from pkcon and systemctl 
status packagekit), with this fix it should survive and show some data 
(changelog doesn't work though).
+  * Test case:
+    - Be on a system (container, VM, or real iron) with at least one 
upgradeable package. If you don't have one, downgrade tzdata:
+   sudo apt-get install tzdata=2016j-0ubuntu0.16.04
+    - Run "pkcon get-updates" to see upgradeable packages.
+    - Run "pkcon get-update-detail tzdata" (or for a different package).
+    - Current PackageKit immediately crashes (message from pkcon and systemctl 
status packagekit), with this fix it should survive and show some data 
(changelog doesn't work though).
  
-  * Regression potential: Update details are currently completely broken,
+  * Regression potential: Update details are currently completely broken,
  so very little to regress there. As for dropping the browser plugin
  package: The current package stopped working long ago with current
  firefox; however, the package from xenial-release will still be around.
  All in all this shouldn't change anything visible.
  
-  * Upstream fix: https://github.com/hughsie/PackageKit/commit/18c56fa52
+  * Upstream fix: https://github.com/hughsie/PackageKit/commit/18c56fa52
  (only the acqpkitstatus.cpp bit)
  
-  * Downstream packaging change to drop browser plugin:
+  * Downstream packaging change to drop browser plugin:
  https://anonscm.debian.org/git/pkg-
  packagekit/packagekit.git/commit/?id=b98a978322

** Description changed:

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
packagekit.  This problem was most recently seen with package version 
0.8.17-4ubuntu6~gcc5.4ubuntu1.1, the problem page at 
https://errors.ubuntu.com/problem/8c37a6988b890cc46b415972ef1e2ca746f9ffcc 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.
  
  SRU INFORMATION
  ===
   * Impact: PackageKit immediately crashes in 

[Touch-packages] [Bug 1689820] Re: /usr/lib/packagekit/packagekitd:11:pkgCache::Iterator:AcqPackageKitStatus::updateStatus:AcqPackageKitStatus::Fail:pkgAcquire::Worker::RunMessages:pkgAcquire::Worker:

[Martin Pitt]

I found the fix and backported it to xenial. The SRU is complicated by
the fact that packagekit is currently FTBFS due to recent firefox
dropping NPAPI, thus the browser plugin cannot be built any more. I'll
drop it.

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

** Changed in: packagekit (Ubuntu Xenial)
   Status: Confirmed => In Progress

** Changed in: packagekit (Ubuntu Xenial)
 Assignee: (unassigned) => Martin Pitt (pitti)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1689820

Title:
  
/usr/lib/packagekit/packagekitd:11:pkgCache::Iterator:AcqPackageKitStatus::updateStatus:AcqPackageKitStatus::Fail:pkgAcquire::Worker::RunMessages:pkgAcquire::Worker::InFdReady

Status in packagekit package in Ubuntu:
  Fix Released
Status in packagekit source package in Xenial:
  In Progress

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

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

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

[Touch-packages] [Bug 1674680] Re: Deprecated rfcomm.conf still mentioned in bluetooth.conf and README

[Eric Desrochers]

** Tags removed: patch

** Changed in: bluez (Ubuntu Xenial)
   Status: New => Won't Fix

** Changed in: bluez (Ubuntu Artful)
 Assignee: (unassigned) => Dariusz Gadomski (dgadomski)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1674680

Title:
  Deprecated rfcomm.conf still mentioned in bluetooth.conf and README

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Xenial:
  Won't Fix
Status in bluez source package in Yakkety:
  Won't Fix
Status in bluez source package in Artful:
  Fix Released
Status in bluez package in Debian:
  New

Bug description:
  [Impact]

   * The package contains misleading documentation mentioning the use of
  /etc/bluetooth/rfcomm.conf for rfcomm setup while the support for
  config file has been dropped after 14.04 release. I have directly
  received a question about it from a user mislead by the documentation.

  * Additionally deprecated -f option is still used in legacy upstart
  /etc/init/bluetooth.conf. Actually this does not seem longer required
  due to upstart being removed.

  [Test Case]

   * Install bluez.

   * Look for misleading rfcomm.conf mentions in
  /etc/init/bluetooth.conf, /usr/share/doc/bluez/README.Debian.gz

  [Regression Potential]

   * This is mostly a documentation correction, however if somebody
  still depends bluetooth started with Ubuntu 16.04+ by upstart (or
  possibly some kind of upstart compatibility in systemd, is that even
  possible?) he/she may end up with bluetooth not being started. This
  seems highly unlikely.

  [Other Info]

   * Original bug description:

  Support for config files has been dropped upstream in 2012 (however
  version shipped with Trusty still supports it), but the latest
  versions (including Xenial and Zesty) still mention it in the docs and
  in the legacy /etc/init/bluetooth.conf file.

  Additionally the /etc/init/bluetooth.conf don't seem necessary these
  days. In fact it has been dropped by Debian already.

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

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

[Touch-packages] [Bug 1689820] Re: /usr/lib/packagekit/packagekitd:11:pkgCache::Iterator:AcqPackageKitStatus::updateStatus:AcqPackageKitStatus::Fail:pkgAcquire::Worker::RunMessages:pkgAcquire::Worker:

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1689820

Title:
  
/usr/lib/packagekit/packagekitd:11:pkgCache::Iterator:AcqPackageKitStatus::updateStatus:AcqPackageKitStatus::Fail:pkgAcquire::Worker::RunMessages:pkgAcquire::Worker::InFdReady

Status in packagekit package in Ubuntu:
  Fix Released
Status in packagekit source package in Xenial:
  Confirmed

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

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

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

[Touch-packages] [Bug 1709163] Re: default output changes from intel builtin to hdmi when display is turned off. yes off not on

[Ubuntu Foundations Team Bug Bot]

The attachment "working aoudio" 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 Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1709163

Title:
  default output changes from intel builtin to hdmi when display is
  turned off. yes off not on

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  So if I have sound output selected to be the intel sound on the
  mainboard and turn off one of my two displays the audio out is changed
  to HDMI. YES OFF it's not a typo.

  The Display I turn off is connected to displayport and do not even
  have HDMI. The audio is switched over to the still active display.

  If I then turn the display back it's still hdmi. If I then turn off
  the display that has HDMI out connected. the audio is still connected
  to that display. since its actually off I hear no sound but pulseaudio
  still connect to it.

  I have to manually open the GUI tool and change back to the correct
  output when the display is turned off or when the display is blanked.
  or suspend/resume.

  I attache the output of "pacmd list-cards  && pacmd list-sinks"
  ok   -> ps_w1.txt
  fail -> ps_f1.txt

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

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

[Touch-packages] [Bug 1708375] Re: Add support for purple-telegram (telepathy-haze)

[Ubuntu Foundations Team Bug Bot]

The attachment "telepathy-purple.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.]

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telepathy-mission-
control-5 in Ubuntu.
https://bugs.launchpad.net/bugs/1708375

Title:
  Add support for purple-telegram (telepathy-haze)

Status in telepathy-mission-control-5 package in Ubuntu:
  Confirmed

Bug description:
  When using purple telegram through telepathy-haze, it requires
  following permissions:

  # for purple telegram
  /etc/telegram-purple/server.tglpub r,
  /usr/lib/purple-2*/   r,
  /usr/lib/purple-2/*.somr,
  /usr/share/locale/*/LC_MESSAGES/*.mo r,
  /usr/share/pixmaps/pidgin/protocols/{16,32,48}/*.png r,
  @{HOME}/.purple/telegram-purple/** rw,
  @{HOME}/.telegram-purple/**   rw,

  under /usr/lib/telepathy/telepathy-* section. See issue
  https://github.com/majn/telegram-purple/issues/346 for more details.

  I have attached the necessary patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+subscriptions

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

[Touch-packages] [Bug 1709309] [NEW] black screen

[svenudo]

Public bug reported:

happens every 3th start up

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
Uname: Linux 4.10.0-30-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Aug  8 14:21:59 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a06] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Google, Inc. Haswell-ULT Integrated Graphics Controller 
[1ae0:c000]
InstallationDate: Installed on 2016-01-17 (568 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 046d:c30e Logitech, Inc. UltraX Keyboard (Y-BL49)
 Bus 001 Device 005: ID 13d3:3393 IMC Networks 
 Bus 001 Device 002: ID 046d:c045 Logitech, Inc. Optical Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Google Panther
ProcEnviron:
 LANGUAGE=nl_NL
 PATH=(custom, no user)
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-30-generic 
root=UUID=81a08f3d-cc4b-49e7-97c4-7ef7d834a3bd ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/20/2015
dmi.bios.vendor: coreboot
dmi.bios.version: MattDevo
dmi.board.name: Panther
dmi.board.vendor: Google
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: Google
dmi.modalias: 
dmi:bvncoreboot:bvrMattDevo:bd12/20/2015:svnGoogle:pnPanther:pvr1.0:rvnGoogle:rnPanther:rvr1.0:cvnGoogle:ct3:cvr:
dmi.product.name: Panther
dmi.product.version: 1.0
dmi.sys.vendor: Google
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
xserver.bootTime: Tue Aug  8 14:02:38 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1.1
xserver.video_driver: modeset

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


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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1709309

Title:
  black screen

Status in xorg package in Ubuntu:
  New

Bug description:
  happens every 3th start up

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Aug  8 14:21:59 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a06] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Google, Inc. Haswell-ULT Integrated Graphics Controller 
[1ae0:c000]
  InstallationDate: Installed on 2016-01-17 (568 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c30e Logitech, Inc. UltraX Keyboard (Y-BL49)
   Bus 001 Device 005: ID 13d3:3393 IMC Networks 
   Bus 001 Device 002: ID 046d:c045 Logitech, Inc. Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Google Panther
  ProcEnviron:
   LANGUAGE=nl_NL
   PATH=(custom, no user)
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-30-generic 
root=UUID=81a08f3d-cc4b-49e7-97c4-7ef7d834a3bd ro quiet splash 

[Touch-packages] [Bug 1610829] Re: unity-system-compositor crashes with SIGABRT [malloc(): memory corruption] from new() from mutable_graphics_module() from mir::frontend::SessionMediator::connect()

[Alan Griffiths]

I don't see this in 17.04, we don't care about USC in 16.04 (and 16.10
where many of the errors were seen is out of support)

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

** Changed in: mir
   Importance: High => Undecided

** Changed in: unity-system-compositor
   Status: New => Won't Fix

** Changed in: unity-system-compositor
   Importance: High => Undecided

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

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

** Changed in: unity-system-compositor (Ubuntu)
   Status: New => Won't Fix

** Changed in: unity-system-compositor (Ubuntu)
   Importance: High => Undecided

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1610829

Title:
  unity-system-compositor crashes with SIGABRT [malloc(): memory
  corruption] from new() from mutable_graphics_module() from
  mir::frontend::SessionMediator::connect()

Status in Mir:
  Incomplete
Status in Unity System Compositor:
  Won't Fix
Status in mir package in Ubuntu:
  Incomplete
Status in unity-system-compositor package in Ubuntu:
  Won't Fix

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-system-compositor.  This problem was most recently
  seen with version 0.6.0+16.04.20160609-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/ff42d7ab6d4e7a23379607f8a5375a837b3a10bd
  contains more details.

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

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

[Touch-packages] [Bug 1553328] Re: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings

[Alan Griffiths]

The nouveau isn't threadsafe and the Qt renderer uses threaded GL by
default.

We don't know if Mir's default renderer would also exhibit the same
issue when running multimonitor. (The Mir renderer uses a thread per
monitor, but this is a simpler usage pattern than Qt and may not
manifest problems.)

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

** Changed in: mir
   Importance: High => Undecided

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

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

** Changed in: canonical-devices-system-image
 Assignee: Stephen M. Webb (bregma) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1553328

Title:
  Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref()
  especially with multiple monitors, webbrowser-app or system settings

Status in Canonical System Image:
  Triaged
Status in Mir:
  Incomplete
Status in Nouveau Xorg driver:
  Unknown
Status in Unity System Compositor:
  Triaged
Status in libdrm package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Incomplete
Status in qtmir package in Ubuntu:
  In Progress
Status in qtubuntu package in Ubuntu:
  In Progress

Bug description:
  Unit8 froze up while I was trying to open system settings.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160216.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Fri Mar  4 19:12:54 2016
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2015-05-10 (299 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: unity8
  SegvAnalysis:
   Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx
   PC (0x7f58d568706c) ok
   source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  Title: unity8 crashed with SIGSEGV
  UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1560382] Re: unity-system-compositor crashed with SIGSEGV in std::_Hashtable<std::shared_ptr, std::shared_ptr, std::allocator

[Alan Griffiths]

AFAIK we've not seen these crashes on zesty which includes more recent
versions of the associated projects. We're also not trying to support
USC on xenial.

** Changed in: mir
 Assignee: Andreas Pokorny (andreas-pokorny) => (unassigned)

** Changed in: unity-system-compositor
 Assignee: Andreas Pokorny (andreas-pokorny) => (unassigned)

** Changed in: mir
   Status: Confirmed => Won't Fix

** Changed in: unity-system-compositor
   Status: Confirmed => Won't Fix

** Changed in: unity-system-compositor (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1560382

Title:
  unity-system-compositor crashed with SIGSEGV in
  std::_Hashtable,
  std::__detail::_Identity,
  std::equal_to,
  std::hash,
  std::__detail::_Mod_range_hashing,
  std::__detail::_Default_ranged_hash,
  std::__detail::_Prime_rehash_policy,
  std::__detail::_Hashtable_traits >::~_Hashtable()

Status in Mir:
  Won't Fix
Status in Unity System Compositor:
  Won't Fix
Status in unity-system-compositor package in Ubuntu:
  Won't Fix

Bug description:
  Ubuntu 16.04 on a VmWare vm, using VMware-tools-linux-10.0.5

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-system-compositor 0.4.2+16.04.20160219.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Wed Mar 16 13:16:44 2016
  ExecutablePath: /usr/sbin/unity-system-compositor
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2016-02-17 (33 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160217)
  ProcCmdline: /usr/sbin/unity-system-compositor --file /run/lightdm-mir-0 
--from-dm-fd 12 --to-dm-fd 21 --vt 8
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0x7f0d1cacd471:mov0x10(%rax),%rax
   PC (0x7f0d1cacd471) ok
   source "0x10(%rax)" (0x7f0d0f616a70) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity-system-compositor
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.38
   ?? ()
   std::_Hashtable, std::__detail::_Identity, 
std::equal_to, 
std::hash, 
std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, 
std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits >::~_Hashtable() ()
   usc::MirInputConfiguration::~MirInputConfiguration() ()
   std::_Sp_counted_ptr_inplace::_M_dispose() ()
  Title: unity-system-compositor crashed with SIGSEGV in 
std::_Hashtable, std::__detail::_Identity, 
std::equal_to, 
std::hash, 
std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, 
std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits >::~_Hashtable()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  version.libdrm: libdrm2 2.4.67-1
  version.lightdm: lightdm 1.17.6-0ubuntu1
  version.mesa: libegl1-mesa-dev N/A

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

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

[Touch-packages] [Bug 1664205] Re: Copy-paste and text selection doesn't work when caps-lock is on

[Treviño]

** Description changed:

+ [Impact]
+ Text entry doesn't properly accept Ctrl+[letter] based shortcuts when Caps 
Lock is on
+ 
+ [Test case]
  0) Set Caps-Lock on in your keyboard
  1) Open dash, and write something
  2) Ctrl+A should select all the text, Ctrl+C should copy,
-Ctrl+V should paste and Ctrl+X should cut
+    Ctrl+V should paste and Ctrl+X should cut
  
  Currently they don't work unless caps-lock is turned off
+ 
+ [Possible regression]
+ Ctrl+[letter] shortcuts or Ins based shortcuts for text selection handling 
won't work anymore

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nux in Ubuntu.
https://bugs.launchpad.net/bugs/1664205

Title:
  Copy-paste and text selection doesn't work when caps-lock is on

Status in nux package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  Text entry doesn't properly accept Ctrl+[letter] based shortcuts when Caps 
Lock is on

  [Test case]
  0) Set Caps-Lock on in your keyboard
  1) Open dash, and write something
  2) Ctrl+A should select all the text, Ctrl+C should copy,
     Ctrl+V should paste and Ctrl+X should cut

  Currently they don't work unless caps-lock is turned off

  [Possible regression]
  Ctrl+[letter] shortcuts or Ins based shortcuts for text selection handling 
won't work anymore

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

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

[Touch-packages] [Bug 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session

[Daniel van Vugt]

Here is the "big" patch I used in testing (includes makefile fix that I
suspect archive doesn't need, but my machine does).

** Patch added: "gst-plugins-bad1.0_1.12.2-1ubuntu2-big.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1698287/+attachment/4928770/+files/gst-plugins-bad1.0_1.12.2-1ubuntu2-big.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1698287

Title:
  VA-API fails to initialize in a Gnome Shell Wayland session

Status in Libva:
  New
Status in Mutter:
  Confirmed
Status in Totem:
  Confirmed
Status in gst-plugins-bad1.0 package in Ubuntu:
  In Progress
Status in gstreamer-vaapi package in Ubuntu:
  In Progress
Status in intel-vaapi-driver package in Ubuntu:
  Invalid
Status in libva package in Ubuntu:
  Triaged
Status in mpv package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in totem package in Ubuntu:
  Invalid

Bug description:
  The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
  Gnome Shell). But it refuses to load when in a Wayland session:

  $ totem bbb_sunflower_1080p_60fps_normal.mp4
  libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)

  $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4
  totem: intel_driver.c:112: intel_driver_init: Assertion 
`VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, 
VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed.
  Aborted (core dumped)

  $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4
  Press 'k' to see a list of keyboard shortcuts.
  Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  Redistribute latency...
  Redistribute latency...
  ERROR Internal error: could not render surface for 
file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0

  WORKAROUNDS:

   * Use weston instead of gnome-shell; or
   * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463
   * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 
1701463
   * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ...
   * $ mpv --hwdec --opengl-backend=wayland ...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: i965-va-driver 1.8.1-1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 13:40:38 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session

[Daniel van Vugt]

Here's the preferred clean fix. Doesn't build on my machine, but I
suspect it will build in archive :S

** Patch added: "gst-plugins-bad1.0_1.12.2-1ubuntu2-small.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1698287/+attachment/4928771/+files/gst-plugins-bad1.0_1.12.2-1ubuntu2-small.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1698287

Title:
  VA-API fails to initialize in a Gnome Shell Wayland session

Status in Libva:
  New
Status in Mutter:
  Confirmed
Status in Totem:
  Confirmed
Status in gst-plugins-bad1.0 package in Ubuntu:
  In Progress
Status in gstreamer-vaapi package in Ubuntu:
  In Progress
Status in intel-vaapi-driver package in Ubuntu:
  Invalid
Status in libva package in Ubuntu:
  Triaged
Status in mpv package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in totem package in Ubuntu:
  Invalid

Bug description:
  The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
  Gnome Shell). But it refuses to load when in a Wayland session:

  $ totem bbb_sunflower_1080p_60fps_normal.mp4
  libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)

  $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4
  totem: intel_driver.c:112: intel_driver_init: Assertion 
`VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, 
VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed.
  Aborted (core dumped)

  $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4
  Press 'k' to see a list of keyboard shortcuts.
  Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  Redistribute latency...
  Redistribute latency...
  ERROR Internal error: could not render surface for 
file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0

  WORKAROUNDS:

   * Use weston instead of gnome-shell; or
   * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463
   * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 
1701463
   * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ...
   * $ mpv --hwdec --opengl-backend=wayland ...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: i965-va-driver 1.8.1-1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 13:40:38 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session

[Daniel van Vugt]

** Also affects: gst-plugins-bad1.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gst-plugins-bad1.0 (Ubuntu)
   Importance: Undecided => High

** Changed in: gst-plugins-bad1.0 (Ubuntu)
   Status: New => In Progress

** Changed in: gst-plugins-bad1.0 (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1698287

Title:
  VA-API fails to initialize in a Gnome Shell Wayland session

Status in Libva:
  New
Status in Mutter:
  Confirmed
Status in Totem:
  Confirmed
Status in gst-plugins-bad1.0 package in Ubuntu:
  In Progress
Status in gstreamer-vaapi package in Ubuntu:
  In Progress
Status in intel-vaapi-driver package in Ubuntu:
  Invalid
Status in libva package in Ubuntu:
  Triaged
Status in mpv package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in totem package in Ubuntu:
  Invalid

Bug description:
  The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
  Gnome Shell). But it refuses to load when in a Wayland session:

  $ totem bbb_sunflower_1080p_60fps_normal.mp4
  libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)

  $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4
  totem: intel_driver.c:112: intel_driver_init: Assertion 
`VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, 
VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed.
  Aborted (core dumped)

  $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4
  Press 'k' to see a list of keyboard shortcuts.
  Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  Redistribute latency...
  Redistribute latency...
  ERROR Internal error: could not render surface for 
file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0

  WORKAROUNDS:

   * Use weston instead of gnome-shell; or
   * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463
   * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 
1701463
   * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ...
   * $ mpv --hwdec --opengl-backend=wayland ...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: i965-va-driver 1.8.1-1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 13:40:38 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1697789] Re: Xorg: page allocation failure: order:0, mode:0x14210d2(GFP_HIGHUSER|__GFP_NORETRY|__GFP_RECLAIMABLE), nodemask=(null)

[Bas Zoetekouw]

I'm seeing the same, also with kernel 4.12

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1697789

Title:
  Xorg: page allocation failure: order:0,
  mode:0x14210d2(GFP_HIGHUSER|__GFP_NORETRY|__GFP_RECLAIMABLE),
  nodemask=(null)

Status in X.Org X server:
  Unknown
Status in xorg package in Ubuntu:
  Confirmed
Status in xorg-server package in Arch Linux:
  New

Bug description:
  dmesg:
  [23559.058500] Xorg: page allocation failure: order:0, 
mode:0x14210d2(GFP_HIGHUSER|__GFP_NORETRY|__GFP_RECLAIMABLE), nodemask=(null)
  [23559.058509] Xorg cpuset=/ mems_allowed=0
  [23559.058516] CPU: 1 PID: 1797 Comm: Xorg Not tainted 
4.12.0-041200rc5-generic #201706112031
  [23559.058517] Hardware name: SAMSUNG ELECTRONICS CO., LTD. 
530U3C/530U4C/SAMSUNG_NP1234567890, BIOS P14AAJ 04/15/2013
  [23559.058519] Call Trace:
  [23559.058528]  dump_stack+0x63/0x8d
  [23559.058532]  warn_alloc+0x114/0x1c0
  [23559.058535]  __alloc_pages_slowpath+0xe07/0xe10
  [23559.058539]  __alloc_pages_nodemask+0x233/0x250
  [23559.058543]  alloc_pages_vma+0xab/0x250
  [23559.058547]  shmem_alloc_page+0x70/0xc0
  [23559.058550]  ? __radix_tree_insert+0x45/0x220
  [23559.058553]  ? __vm_enough_memory+0x29/0x130
  [23559.058555]  shmem_alloc_and_acct_page+0x72/0x1b0
  [23559.058558]  ? find_get_entry+0x1e/0xc0
  [23559.058561]  shmem_getpage_gfp+0x195/0xbd0
  [23559.058564]  shmem_read_mapping_page_gfp+0x44/0x80
  [23559.058611]  i915_gem_object_get_pages_gtt+0x204/0x5a0 [i915]
  [23559.058643]  i915_gem_object_get_pages+0x20/0x60 [i915]
  [23559.058673]  __i915_gem_object_get_pages+0x5c/0x70 [i915]
  [23559.058706]  __i915_vma_do_pin+0x1c6/0x3a0 [i915]
  [23559.058737]  i915_gem_execbuffer_reserve_vma.isra.29+0x14d/0x1b0 [i915]
  [23559.058765]  i915_gem_execbuffer_reserve.isra.30+0x3b7/0x3e0 [i915]
  [23559.058794]  i915_gem_do_execbuffer.isra.36+0x577/0x16c0 [i915]
  [23559.058799]  ? unix_stream_recvmsg+0x54/0x70
  [23559.058801]  ? unix_state_double_lock+0x70/0x70
  [23559.058830]  i915_gem_execbuffer2+0x96/0x1b0 [i915]
  [23559.058849]  drm_ioctl+0x216/0x4c0 [drm]
  [23559.058877]  ? i915_gem_execbuffer+0x2f0/0x2f0 [i915]
  [23559.058881]  ? __remove_hrtimer+0x3c/0x70
  [23559.058885]  do_vfs_ioctl+0xa3/0x600
  [23559.05]  ? do_setitimer+0xe0/0x240
  [23559.058891]  ? SyS_setitimer+0xf1/0x120
  [23559.058894]  SyS_ioctl+0x79/0x90
  [23559.058897]  entry_SYSCALL_64_fastpath+0x1e/0xa9
  [23559.058900] RIP: 0033:0x7fd8c5c7e987
  [23559.058901] RSP: 002b:7ffd494ac738 EFLAGS: 0246 ORIG_RAX: 
0010
  [23559.058904] RAX: ffda RBX: 0006 RCX: 
7fd8c5c7e987
  [23559.058905] RDX: 7ffd494ac790 RSI: 40406469 RDI: 
000c
  [23559.058907] RBP: 0028 R08: 0001 R09: 
000c
  [23559.058908] R10: 0001 R11: 0246 R12: 
0040
  [23559.058909] R13: 0008 R14: 5581c086a6c0 R15: 

  [23559.058912] Mem-Info:
  [23559.058918] active_anon:1016643 inactive_anon:298858 isolated_anon:0
  active_file:395940 inactive_file:1147459 isolated_file:0
  unevictable:129 dirty:124022 writeback:21146 unstable:0
  slab_reclaimable:57926 slab_unreclaimable:23062
  mapped:283483 shmem:248113 pagetables:23247 bounce:0
  free:29069 free_pcp:245 free_cma:0
  [23559.058923] Node 0 active_anon:4066572kB inactive_anon:1195432kB 
active_file:1583760kB inactive_file:4589836kB unevictable:516kB 
isolated(anon):0kB isolated(file):0kB mapped:1133932kB dirty:496088kB 
writeback:84584kB shmem:992452kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 
976896kB writeback_tmp:0kB unstable:0kB all_unreclaimable? no
  [23559.058924] Node 0 DMA free:15360kB min:84kB low:104kB high:124kB 
active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB 
unevictable:0kB writepending:0kB present:15984kB managed:15360kB mlocked:0kB 
slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB 
bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
  [23559.058930] lowmem_reserve[]: 0 3226 11726 11726 11726
  [23559.058935] Node 0 DMA32 free:52176kB min:18568kB low:23208kB high:27848kB 
active_anon:718716kB inactive_anon:177564kB active_file:228516kB 
inactive_file:2067540kB unevictable:0kB writepending:203112kB present:3438520kB 
managed:3354852kB mlocked:0kB slab_reclaimable:98764kB 
slab_unreclaimable:3004kB kernel_stack:576kB pagetables:4384kB bounce:0kB 
free_pcp:0kB local_pcp:0kB free_cma:0kB
  [23559.058941] lowmem_reserve[]: 0 0 8500 8500 8500
  [23559.058945] Node 0 Normal free:48740kB min:48924kB low:61152kB 
high:73380kB active_anon:3347648kB inactive_anon:1017448kB 
active_file:1354180kB inactive_file:2521736kB unevictable:516kB 
writepending:377444kB present:8902656kB managed:8704148kB mlocked:516kB 

[Touch-packages] [Bug 1661629] Re: upgrade of kernel fails with mkinitramfs: failed to determine device for /

[bendikro]

The problem is the bash function dep_add_modules_mount in /usr/share
/initramfs-tools/hook-functions which doesn't handle zfs.

By adding "MODULES=most" to /usr/share/initramfs-tools/conf-hooks.d/zfs,
the error goes away.

I'm still having trouble getting kdump to actually create a crash dump
with ZFS on root.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1661629

Title:
  upgrade of kernel fails with mkinitramfs: failed to determine device
  for /

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  When upgrading packages with "apt upgrade" on Ubuntu 16.04.1 LTS with
  root on ZFS I get this error:

  Setting up linux-image-4.4.0-59-generic (4.4.0-59.80) ...
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  update-initramfs: Generating /boot/initrd.img-4.4.0-59-generic
  run-parts: executing /etc/kernel/postinst.d/kdump-tools 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  kdump-tools: Generating /var/lib/kdump/initrd.img-4.4.0-59-generic
  mkinitramfs: failed to determine device for /
  mkinitramfs: workaround is MODULES=most, check:
  grep -r MODULES /etc/initramfs-tools/

  Error please report bug on initramfs-tools
  Include the output of 'mount' and 'cat /proc/mounts'
  update-initramfs: failed for  with 1.
  run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1
  Failed to process /etc/kernel/postinst.d at 
/var/lib/dpkg/info/linux-image-4.4.0-59-generic.postinst line 1052.
  dpkg: error processing package linux-image-4.4.0-59-generic (--configure):
   subprocess installed post-installation script returned error exit status 2

  version of initramfs-tools is 0.122ubuntu8.8

  
  Output of mount is:

  sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
  proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
  udev on /dev type devtmpfs 
(rw,nosuid,relatime,size=8066020k,nr_inodes=2016505,mode=755)
  devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1623576k,mode=755)
  rpool/ROOT/ubuntu on / type zfs (rw,relatime,xattr,noacl)
  securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
  tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
  tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
  pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
  cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
  cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
  cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
  cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
  cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
  cgroup on /sys/fs/cgroup/pids type cgroup 
(rw,nosuid,nodev,noexec,relatime,pids)
  cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
  cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
  cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
  mqueue on /dev/mqueue type mqueue (rw,relatime)
  hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
  systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=31,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
  debugfs on /sys/kernel/debug type debugfs (rw,relatime)
  fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
  rpool/home on /home type zfs (rw,nosuid,noatime,xattr,noacl)
  rpool/home/fredrik on /home/fredrik type zfs (rw,nosuid,noatime,xattr,noacl)
  rpool/home/root on /root type zfs (rw,nosuid,noatime,xattr,noacl)
  rpool/srv on /srv type zfs (rw,noatime,xattr,noacl)
  rpool/var/cache on /var/cache type zfs (rw,nosuid,noexec,noatime,xattr,noacl)
  rpool/var/log on /var/log type zfs (rw,nosuid,noexec,noatime,xattr,noacl)
  rpool/var/spool on /var/spool type zfs (rw,nosuid,noexec,noatime,xattr,noacl)
  rpool/var/tmp on /var/tmp type zfs (rw,nosuid,noatime,xattr,noacl)
  tmpfs on /run/user/1000 type tmpfs 

[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to

[ethan.hsieh]

@Balint

I tried three times, and 0.95-16.04.0rbalint1 didn't work well.

Please refer to attached file for detailed log.

1) Reboot system when unattended upgrades starts to download packages.
//unattended-upgrades.log
2017-08-08 15:34:07,782 INFO Starting unattended upgrades script
2017-08-08 15:34:07,782 INFO Allowed origins are: ['o=Ubuntu,a=xenial', 
'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial']
//unattended-upgrades-shutdown.log
2017-08-08 15:36:06,358 INFO - All upgrades installed

The log shows "All upgrades installed", but there is no package
installed.

2) Reboot system after unattended upgrades downloads packages for 5mins
//unattended-upgrades.log
2017-08-08 15:55:27,907 INFO Starting unattended upgrades script
2017-08-08 15:55:27,907 INFO Allowed origins are: ['o=Ubuntu,a=xenial', 
'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial']

System reboots immediately. There is no unattended-upgrades-shutdown
log.

3) Reboot system when unattended upgrades starts to download packages.
//unattended-upgrades.log
2017-08-08 16:09:03,548 INFO Starting unattended upgrades script
2017-08-08 16:09:03,549 INFO Allowed origins are: ['o=Ubuntu,a=xenial', 
'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial']
//unattended-upgrades-shutdown.log
2017-08-08 16:10:50,573 INFO - All upgrades installed

The log shows "All upgrades installed", but there is no package
installed.

---
The installed packages:
apt_1.2.25-rbalint2_amd64.deb
apt-doc_1.2.25-rbalint2_all.deb
apt-transport-https_1.2.25-rbalint2_amd64.deb
apt-utils_1.2.25-rbalint2_amd64.deb
libapt-inst2.0_1.2.25-rbalint2_amd64.deb
libapt-pkg5.0_1.2.25-rbalint2_amd64.deb
libapt-pkg-doc_1.2.25-rbalint2_all.deb
unattended-upgrades_0.95-16.04.0rbalint1_all.deb

** Attachment added: "unattended-upgrades-shutdown.log, 
unattended-upgrades.log, apt log, and dpkg log"
   
https://bugs.launchpad.net/oem-priority/+bug/1690980/+attachment/4928762/+files/log_0808.tar.gz

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1690980

Title:
  unattended-upgrades does not block shutdown of system, as it is
  designed to

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  New
Status in apt package in Ubuntu:
  Fix Committed
Status in unattended-upgrades package in Ubuntu:
  Fix Committed

Bug description:
  Title: No pop-up window to warn users that system should not reboot or
  shutdown while installing security updates

  Summary:
  No pop-up window to warn users that system should not reboot or shutdown 
while installing security updates

  Steps:
  1. trigger unattended-upgrades
  2. reboot or shutdown system while installing packages

  Expected results: There is a pop-up window to warn users that system
  should not reboot or shutdown

  Actual results: There is no pop-up window to warn users

  Additional information:
  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
Installed: 0.90
Candidate: 0.90ubuntu0.5
  $ lsb_release -rd
  Description:Ubuntu 16.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions

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

Re: [Touch-packages] [Bug 1692981] Re: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con

[peter dirnberger]

this fixed my problem

On 5 August 2017 at 22:39, Sandra Viktoria Mueller 
wrote:

> I run the dpkg -l | awk '/^iH/ { print $2 }' command. He doesn't give me
> any result.
> But the problem remains. The update for the operating system stops at the
> half way.
>
> And I've got another update for software 3.20.5 which not even starts. Any
> idea what I could try?
>
> Thank you
>
> Sandra
>
>
> 2017-08-04 21:55 GMT+02:00 Jeremy Gabriel :
>
> > Did you run the dpkg -l | awk '/^iH/ { print $2 }' command that Seth
> posted
> > earlier in the thread? If so, you need to run the reinstall line for any
> > package listed.
> >
> > Unfortunately that's the limit to what I will be able to help with. Good
> > luck
> >
> >
> > On Fri, Aug 4, 2017 at 10:07 AM, Sandra Viktoria Mueller <
> > savi...@gmail.com>
> > wrote:
> >
> > > Hi Jeremy,
> > >
> > > Thank you very much. I tried your command. I've put the result you in
> the
> > > attachment. Unfortunately it is in part in italian, but maybe you could
> > > understand something. Please let me know.
> > >
> > > Sandra
> > >
> > > 2017-08-04 17:59 GMT+02:00 Jeremy Gabriel :
> > >
> > > > Hi Sandra,
> > > > I had to use
> > > >
> > > > sudo apt-get install --reinstall libssl1.0.0:i386
> > > >
> > > > Hope this helps,
> > > > Jeremy
> > > >
> > > > On Thu, Jul 27, 2017 at 2:28 AM, Sandra Viktoria Mueller <
> > > > savi...@gmail.com>
> > > > wrote:
> > > >
> > > > > I wrote in the terminal this: sudo apt-get install --reinstall
> > > > > libssl-dev:amd64
> > > > > 1.0.2g-1ubuntu11.2
> > > > > Unfortunately it doesn't work. The problem remains.
> > > > >
> > > > > Please If you have another command which I can try? Thank you
> > > > >
> > > > > Sandra
> > > > >
> > > > > 2017-07-25 0:09 GMT+02:00 Seth Arnold <1692...@bugs.launchpad.net
> >:
> > > > >
> > > > > > ** Changed in: dpkg (Ubuntu)
> > > > > >Status: Fix Released => Confirmed
> > > > > >
> > > > > > ** Changed in: openssl (Ubuntu)
> > > > > >Status: Fix Released => Confirmed
> > > > > >
> > > > > > --
> > > > > > You received this bug notification because you are subscribed to
> > the
> > > > bug
> > > > > > report.
> > > > > > https://bugs.launchpad.net/bugs/1692981
> > > > > >
> > > > > > Title:
> > > > > >   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to
> > > > install/upgrade:
> > > > > >   package is in a very bad inconsistent state; you should
> > reinstall
> > > it
> > > > > >   before attempting configuration
> > > > > >
> > > > > > Status in dpkg package in Ubuntu:
> > > > > >   Confirmed
> > > > > > Status in openssl package in Ubuntu:
> > > > > >   Confirmed
> > > > > >
> > > > > > Bug description:
> > > > > >   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to
> > > > install/upgrade:
> > > > > >   package is in a very bad inconsistent state; you should
> > reinstall
> > > it
> > > > > >   before attempting configuration
> > > > > >
> > > > > >   ProblemType: Package
> > > > > >   DistroRelease: Ubuntu 17.04
> > > > > >   Package: libssl-dev:amd64 1.0.2g-1ubuntu11.2
> > > > > >   ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
> > > > > >   Uname: Linux 4.10.0-21-generic x86_64
> > > > > >   ApportVersion: 2.20.4-0ubuntu4.1
> > > > > >   AptOrdering:
> > > > > >libssl1.0.0:amd64: Install
> > > > > >NULL: ConfigurePending
> > > > > >   Architecture: amd64
> > > > > >   Date: Tue May 23 21:47:55 2017
> > > > > >   DuplicateSignature:
> > > > > >package:libssl-dev:amd64:1.0.2g-1ubuntu11.2
> > > > > >Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu11.2) ...
> > > > > >dpkg: error processing package libssl-dev:amd64 (--configure):
> > > > > > package is in a very bad inconsistent state; you should
> > > > > >   ErrorMessage: package is in a very bad inconsistent state; you
> > > should
> > > > > > reinstall it before attempting configuration
> > > > > >   InstallationDate: Installed on 2017-05-15 (7 days ago)
> > > > > >   InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64
> > > > > (20170412)
> > > > > >   RelatedPackageVersions:
> > > > > >dpkg 1.18.10ubuntu2
> > > > > >apt  1.4
> > > > > >   SourcePackage: openssl
> > > > > >   Title: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to
> > > > > > install/upgrade: package is in a very bad inconsistent state; you
> > > > should
> > > > > > reinstall it before attempting configuration
> > > > > >   UpgradeStatus: No upgrade log present (probably fresh install)
> > > > > >
> > > > > > To manage notifications about this bug go to:
> > > > > > https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/
> > > > > 1692981/+subscriptions
> > > > > >
> > > > >
> > > > > --
> > > > > You received this bug notification because you are subscribed to a
> > > > > duplicate bug report (1696799).
> > > > > https://bugs.launchpad.net/bugs/1692981
> > > > >
> > > > > Title:
> > > > >   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to

[Touch-packages] [Bug 1695872] Re: GNOME on Wayland session could not be started from lightdm

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1695872

Title:
  GNOME on Wayland session could not be started from lightdm

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  GNOME on Wayland session could not be started from lightdm

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  5 11:23:22 2017
  InstallationDate: Installed on 2016-09-09 (268 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1695872] Re: GNOME on Wayland session could not be started from lightdm

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1695872

Title:
  GNOME on Wayland session could not be started from lightdm

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  GNOME on Wayland session could not be started from lightdm

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  5 11:23:22 2017
  InstallationDate: Installed on 2016-09-09 (268 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1709055] Re: Drop support for Android (Ubuntu Touch patches)

[Sebastien Bacher]

Ok, fair enough, let's handle the trust store case in another round
later

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1709055

Title:
  Drop support for Android (Ubuntu Touch patches)

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Drop support for Android (Ubuntu Touch patches)

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

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

[Touch-packages] [Bug 1706936] Re: Wrong version of libgles1-mesa in Xenial-updates

[Timo Aaltonen]

could you run 'apt-cache rdepends libgles1-mesa' and paste the output
here.. I'd like to know where the dependency is coming from

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1706936

Title:
  Wrong version of libgles1-mesa in Xenial-updates

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Xenial-updates has the following packages:

  - libgles1-mesa (12.0.6-0ubuntu0.16.04.1)
  - libglapi-mesa (17.0.7-0ubuntu0.16.04.1)

  The first one depends on libglapi-mesa (= 12.0.6-0ubuntu0.16.04.1),
  but libglapi-mesa has a higher version and so there's a conflict.

  I've had to remove libgles1-mesa for now, to avoid the conflict.

  I have Linux Mint 18.1 but I believe it affects anyone using xenial-
  updates.

  Source links I used to verify it's a xenial-updates problem:

  https://packages.ubuntu.com/xenial-updates/libs/libgles1-mesa
  https://packages.ubuntu.com/xenial-updates/libglapi-mesa

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

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

[Touch-packages] [Bug 1709175] Re: remove init.d and upstart files

[Steve Langasek]

Why is this bug marked block-proposed?  Please do not use this tag
except to describe bugs present in a -proposed version of a package that
should prevent it from migrating and breaking the release ("remaining
init.d and upstart files" are not that).

apparmor is entangled with the perl transition, so this needs to be
resolved ASAP.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1709175

Title:
  remove init.d and upstart files

Status in apparmor package in Ubuntu:
  New

Bug description:
  remove init.d and upstart files

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

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

[Touch-packages] [Bug 1639517] Re: [HP Pavilion Notebook - 17-g164ng] black screen when booting

[Timo Aaltonen]

you should add test results upstream, there's no-one here who can fix
this I'm afraid

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1639517

Title:
  [HP Pavilion Notebook - 17-g164ng] black screen when booting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When booting the screen is black – backlight on – off - on.
  When HDD is inactive
  - keyboard is not locked and I can shutdown/reboot by Alt + Print +o/b or 
Strg + Alt + Del
  - remote access e.g. using ssh is possible

  Testsystems: Ubuntu/Kubuntu 14.04, 15.10, 16.04, 16.10.

  My notebook is a HP Pavilion  17-g164ng with an AMD A10-8780P APU and
  2 graphic subsystems - Carrizo, a VGA compatible controller and Topaz.

  It seems very similar to that described in #1597079.

  The bug report was generated from a remote PC. My HP notebook was started 
without any workaround parameters.
  This apport doesn't display the second graphic subsystem Topaz R7 as an 
apport generated with nomodeset xforcevesa.

  WORKAROUND: In 14.04 and 15.10 I installed fglrx – the AMD driver.

  WORKAROUND: When booting in UEFI mode, use kernel parameters:
  nomodeset

  or:
  nomodeset xforcevesa

  Resolution without xforcevesa: 800x600
  Resolution with xforcevesa: 1600x900 – the optimal resolution

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Nov  5 23:40:19 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Carrizo [103c:80b6]
  InstallationDate: Installed on 2016-11-03 (2 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP Pavilion Notebook
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=d006dbb4-8a2a-4cfe-b38e-7d35b34bca09 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.41
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 80B6
  dmi.board.vendor: HP
  dmi.board.version: 81.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.41:bd09/19/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B6:rvr81.32:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  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: Sat Nov  5 23:32:11 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.1
  xserver.video_driver: amdgpu

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

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

[Touch-packages] [Bug 1709247] [NEW] firefox

[jayesh motilal bharadia]

Public bug reported:

crash

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
Uname: Linux 4.4.0-89-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Aug  8 11:44:31 2017
DistUpgraded: 2017-08-07 00:33:19,443 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] 
(rev 03) (prog-if 00 [VGA controller])
   Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:027f]
   Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:027f]
InstallationDate: Installed on 2017-08-06 (1 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
MachineType: Dell Inc. OptiPlex 760
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=1ada85c8-f84c-4acb-be82-8695ae22932d ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2017-08-06 (1 days ago)
dmi.bios.date: 08/06/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 0R230R
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd08/06/2013:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0R230R:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.name: OptiPlex 760
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Aug  8 08:40:49 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.3

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


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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1709247

Title:
  firefox

Status in xorg package in Ubuntu:
  New

Bug description:
  crash

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Uname: Linux 4.4.0-89-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Aug  8 11:44:31 2017
  DistUpgraded: 2017-08-07 00:33:19,443 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e12] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:027f]
 Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:027f]
  InstallationDate: Installed on 2017-08-06 (1 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  MachineType: Dell Inc. OptiPlex 760
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=1ada85c8-f84c-4acb-be82-8695ae22932d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-08-06 (1 days ago)
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0R230R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd08/06/2013:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0R230R:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 760
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2