date:20170925

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

** Changed in: gtk+3.0 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  GTK file chooser shows entries from /sys, /dev, etc.

Status in gtk+3.0 package in Ubuntu:
  Expired

Bug description:
  On Kubuntu 17.10 Alpha 1, the GTK file chooser shows several unwanted
  entries from /sys, /dev, etc. For me, this occurs in the GTK3 file
  chooser opened from Firefox, GNOME Disks, etc. At the time of writing,
  I haven't tested whether it occurs in the GTK2 chooser as well. I have
  attached a screenshot showing the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1701780/+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 1705835] Re: I cant turn the volume.

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

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

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

Title:
  I cant turn the volume.

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  I checked all of the listed commands on the official ubuntu site but
  nothing works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-27-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  Date: Sat Jul 22 20:38:46 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-07-02 (20 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 085X6F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd12/27/2011:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn085X6F:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L321X
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1705835/+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 1717309] Re: 17.10 Artful Aardvark Mascot

This bug was fixed in the package ubiquity-slideshow-ubuntu - 131

---
ubiquity-slideshow-ubuntu (131) artful; urgency=medium

  * po/ubuntukylin/en_GB.po: Manually fix up syntax error.

 -- Iain Lane   Mon, 25 Sep 2017 21:45:22 +0100

** Changed in: ubiquity-slideshow-ubuntu (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  17.10 Artful Aardvark Mascot

Status in Ubuntu theme:
  New
Status in ubiquity-slideshow-ubuntu package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Aardvark attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1717309/+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 1672171] Re: pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles() from pa_bluetooth_transport_set_state() from profile_new_connection() from profile_handler

2017-09-25 Thread bikram tuladhar

Thanks!

On Sep 26, 2017 12:17 AM, "Launchpad Bug Tracker" <
1672...@bugs.launchpad.net> wrote:

> This bug was fixed in the package pulseaudio - 1:8.0-0ubuntu3.4
>
> ---
> pulseaudio (1:8.0-0ubuntu3.4) xenial; urgency=medium
>
>   * debian/control: Update Vcs fields to launchpad git.
>   * Cherrypick fixes for common crashes from upstream:
> - cb78d6f5: SIGABRT in device_start_waiting_for_profiles (LP:
> #1690028,
>   LP: #1672171)
> - d985276c: SIGABRT in pa_alsa_path_set_volume (LP: #1539209, LP:
> #1562817)
>
>  -- Daniel van Vugt   Fri, 11 Aug 2017
> 15:16:57 +0800
>
> ** Changed in: pulseaudio (Ubuntu Xenial)
>Status: Fix Committed => Fix Released
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1672171
>
> Title:
>   pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles()
>   from pa_bluetooth_transport_set_state() from profile_new_connection()
>   from profile_handler() from _dbus_object_tree_dispatch_and_unlock()
>
> Status in PulseAudio:
>   Fix Released
> Status in pulseaudio package in Ubuntu:
>   Fix Released
> Status in pulseaudio source package in Xenial:
>   Fix Released
>
> Bug description:
>   [Impact]
>   pulseaudio daemon crashes, interrupting sound output/input.
>
>   [Test Case]
>   Theoretical test case (crash does not happen for all users):
>   1. Get a Bluetooth audio device capable of multiple profiles (e.g. high
>  fidelity A2DP and the lower quality headset profiles).
>   2. Pair it with your machine and select the device in sound settings.
>   3. Turn the Bluetooth audio device off and on again, making sure it is
>  set to active if not automatically so.
>   4. Select the device in sound settings.
>   5. Check that that pulseaudio process is still running, with a start
>  time older than when you began this test case.
>
>   [Regression Potential]
>   Low. This SRU affects the pulseaudio daemon only so the worst case would
>   be loss of sound output/input. The same patches have been released to
>   17.10 for a month already and zero regressions of the crashes have
>   occurred worldwide since then.
>
>   [Other Info]
>   Debdiff patch is attached to the most prolific bug 1539209.
>
>   [Original Description]
>
>   Bluetooth device keep disconnect and audio output tab is empty
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 17.04
>   Package: pulseaudio 1:10.0-1ubuntu1
>   ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
>   Uname: Linux 4.10.0-11-generic x86_64
>   NonfreeKernelModules: nvidia_uvm nvidia
>   ApportVersion: 2.20.4-0ubuntu2
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC1:  bikram14994 F pulseaudio
>/dev/snd/controlC0:  bikram14994 F pulseaudio
>   CrashCounter: 1
>   CurrentDesktop: Unity:Unity7
>   Date: Sun Mar 12 21:52:24 2017
>   ExecutablePath: /usr/bin/pulseaudio
>   ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
>   Signal: 6
>   SourcePackage: pulseaudio
>   StacktraceTop:
>pa_bluetooth_transport_set_state () from /usr/lib/pulse-10.0/modules/
> libbluez5-util.so
>?? () from /usr/lib/pulse-10.0/modules/libbluez5-util.so
>?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
>dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
>?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so
>   Title: pulseaudio crashed with SIGABRT in pa_bluetooth_transport_set_
> state()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
>   dmi.bios.date: 11/14/2013
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: A07
>   dmi.board.name: 0Y004V
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A07
>   dmi.chassis.type: 8
>   dmi.chassis.vendor: Dell Inc.
>   dmi.chassis.version: Not Specified
>   dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/14/2013:svnDellInc.:
> pnInspiron3437:pvrNotSpecified:rvnDellInc.:rn0Y004V:rvrA07:cvnDellInc.:
> ct8:cvrNotSpecified:
>   dmi.product.name: Inspiron 3437
>   dmi.product.version: Not Specified
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/pulseaudio/+bug/1672171/+subscriptions
>

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

Title:
  pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles()
  from pa_bluetooth_transport_set_state() from profile_new_connection()
  from profile_handler() from _dbus_object_tree_dispatch_and_unlock()

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

Bug description:
  [Impact]
  pulseaudio daemon

[Touch-packages] [Bug 1716976] Re: DNS resolver silently switches to an unknown DNS server

2017-09-25 Thread gpothier

Sorry, sorry, it does still happen.

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

Title:
  DNS resolver silently switches to an unknown DNS server

Status in systemd package in Ubuntu:
  New

Bug description:
  In our network we have a DNS server that resolves some names to local
  addresses, while the same names are resolved to our public IP when
  public DNSs are used. For instance (using fictitious names and IPs),
  xyz.mydomain.com resolves to the public IP 65.254.242.180 when using
  an external DNS server, but resolves to 192.168.0.14 when using our
  internal DNS server (which all our computers are told to use via
  DHCP).

  This used to work fine until a somewhat recent update in Ubuntu 17.10.
  Now, xyz.domain.com almost always resolves to the public IP instead of
  the internal IP. Interestingly, restarting the systemd-resolved
  service fixes the problem for a while (from a few seconds to a few
  minutes). Right after restarting the service, the dig command reports
  the expected internal IP, but after a while it gets back to reporting
  the public IP. Forcing the dig command to query our DNS server instead
  of the local resolver returns the correct IP.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 13 13:34:50 2017
  InstallationDate: Installed on 2015-01-23 (963 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 20266
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic.efi.signed 
root=UUID=eecad38d-4fff-462c-92bc-357fa12e5515 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-06-15 (90 days ago)
  dmi.bios.date: 03/30/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN43WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN43WW:bd03/30/2015:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1716976/+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 1716976] Re: DNS resolver silently switches to an unknown DNS server

2017-09-25 Thread gpothier

It looks like this has been fixed, it is not occurring anymore.

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

Title:
  DNS resolver silently switches to an unknown DNS server

Status in systemd package in Ubuntu:
  New

Bug description:
  In our network we have a DNS server that resolves some names to local
  addresses, while the same names are resolved to our public IP when
  public DNSs are used. For instance (using fictitious names and IPs),
  xyz.mydomain.com resolves to the public IP 65.254.242.180 when using
  an external DNS server, but resolves to 192.168.0.14 when using our
  internal DNS server (which all our computers are told to use via
  DHCP).

  This used to work fine until a somewhat recent update in Ubuntu 17.10.
  Now, xyz.domain.com almost always resolves to the public IP instead of
  the internal IP. Interestingly, restarting the systemd-resolved
  service fixes the problem for a while (from a few seconds to a few
  minutes). Right after restarting the service, the dig command reports
  the expected internal IP, but after a while it gets back to reporting
  the public IP. Forcing the dig command to query our DNS server instead
  of the local resolver returns the correct IP.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 13 13:34:50 2017
  InstallationDate: Installed on 2015-01-23 (963 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 20266
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic.efi.signed 
root=UUID=eecad38d-4fff-462c-92bc-357fa12e5515 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-06-15 (90 days ago)
  dmi.bios.date: 03/30/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN43WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN43WW:bd03/30/2015:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1716976/+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 1719471] [NEW] ptrace doesnt't trigger/work as expected

2017-09-25 Thread ChristianEhrhardt

Public bug reported:

Hi,
we looked into a discussion [1] which was triggered by [2].
For Ubunutu all these features existed for quite a while, so since [3] we had 
[4].

So I was looking into dropping [4] later on in favor of the fix in [1].
But while doing so I was puzzles why things even work.

I discussed with jjohansen and ptrace rules should have a traced and trace 
"end" of the rule.
Our old change was not as restrictive as the better change now suggested, but 
it had both ends.
While quickly trying to check on this we found that it actually works with just 
one side of the rules, but it shouldn't.

Jjohansen said he will look into that and get back to us, this bug is to
allow everybody involved to track this.


[1]: https://www.redhat.com/archives/libvir-list/2017-September/msg00844.html
[2]: https://bugzilla.suse.com/show_bug.cgi?id=1058847
[3]: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1298611
[4]: 
https://git.launchpad.net/~libvirt-maintainers/ubuntu/+source/libvirt/commit/?h=ubuntu/artful-3.6=f614b472657d93e1f6c62afaf6a887bd38384a97

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

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

Title:
  ptrace doesnt't trigger/work as expected

Status in apparmor package in Ubuntu:
  New

Bug description:
  Hi,
  we looked into a discussion [1] which was triggered by [2].
  For Ubunutu all these features existed for quite a while, so since [3] we had 
[4].

  So I was looking into dropping [4] later on in favor of the fix in [1].
  But while doing so I was puzzles why things even work.

  I discussed with jjohansen and ptrace rules should have a traced and trace 
"end" of the rule.
  Our old change was not as restrictive as the better change now suggested, but 
it had both ends.
  While quickly trying to check on this we found that it actually works with 
just one side of the rules, but it shouldn't.

  Jjohansen said he will look into that and get back to us, this bug is
  to allow everybody involved to track this.

  
  [1]: https://www.redhat.com/archives/libvir-list/2017-September/msg00844.html
  [2]: https://bugzilla.suse.com/show_bug.cgi?id=1058847
  [3]: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1298611
  [4]: 
https://git.launchpad.net/~libvirt-maintainers/ubuntu/+source/libvirt/commit/?h=ubuntu/artful-3.6=f614b472657d93e1f6c62afaf6a887bd38384a97

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1719471/+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 1684233] Re: package ntp 1:4.2.8p4+dfsg-3ubuntu5.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

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

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

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

Title:
  package ntp 1:4.2.8p4+dfsg-3ubuntu5.4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 2

Status in ntp package in Ubuntu:
  Confirmed

Bug description:
  no idea how to explain or fix the issue, but it is causing me to not
  be able to access the school network or internet from the school
  network ethernet switch.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.4
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Apr 19 11:02:59 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2017-02-14 (63 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  NtpStatus: ntpq: read: Connection refused
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=28cffc81-a318-4788-996b-6ba760b5a61d ro priority=low quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: ntp
  Title: package ntp 1:4.2.8p4+dfsg-3ubuntu5.4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1684233/+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 1718238] Re: Giant terminal icon is blocking own the Terminal window buttons

** Summary changed:

- Problema do ícones do menu no terminal na sessão Xorg
+ Giant terminal icon is blocking own the Terminal window buttons

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- Giant terminal icon is blocking own the Terminal window buttons
+ Giant terminal icon is blocking out the Terminal window buttons

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

Title:
  Giant terminal icon is blocking out the Terminal window buttons

Status in gnome-shell package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  
file:///home/castilhos/Imagens/Captura%20de%20tela%20de%202017-09-19%2012-43-54.png

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 12:47:51 2017
  InstallationDate: Installed on 2017-09-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  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/1718238/+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 1717796] Re: Bluetoothd fills 100% CPU when bluetooth keyboard goes in idle

Thanks. Unfortunately it appears bluetoothd is a single-threaded program
spinning its g_main_loop without actually doing any heavy work on each
iteration. This makes it hard to identify the cause of the problem
without running it through a profiler.

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

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

Title:
  Bluetoothd fills 100% CPU when bluetooth keyboard goes in idle

Status in bluez package in Ubuntu:
  New

Bug description:
  When bluetooth keyboard goes in idle bluetoothd fills 100% CPU. At
  this point you have to press any key to reconnect the device and let
  bluetoothd to return to work normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5.1
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sun Sep 17 19:02:40 2017
  ExecutablePath: /usr/lib/bluetooth/bluetoothd
  InstallationDate: Installed on 2016-08-06 (406 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: GIGABYTE GB-BXBT-2807
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic.efi.signed 
root=UUID=8931ead4-8d43-4aef-8946-c7845c63c7d3 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F8
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MZBAYAP-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF8:bd10/22/2015:svnGIGABYTE:pnGB-BXBT-2807:pvr1.x:rvnGIGABYTE:rnMZBAYAP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: GB-BXBT-2807
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: DC:85:DE:FD:2F:BC  ACL MTU: 820:8  SCO MTU: 255:16
UP RUNNING PSCAN ISCAN 
RX bytes:528225 acl:32183 sco:0 events:1134 errors:0
TX bytes:33849 acl:338 sco:0 commands:388 errors:1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1717796/+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 1716092] Re: Enabling Auto switching streams on new active output causes pulseaudio to crash

Since this is crash however...

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

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

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

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

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

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

Title:
  Enabling Auto switching streams on new active output causes pulseaudio
  to crash

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Not sure if this is a plasma-pa bug or a pulseaudio bug.  In plasma-pa
  -> Audio Volumue -> Advanced tab checking the "Automatically
  switch all running streams when a new output becomes available" cause
  PA to crash.  If the /etc/pulse/default.pa file is modified by
  commenting out following line:

load-module module-switch-on-connect

  PA will start as expected.  I have not checked to see if the auto
  switching works when the default.pa line is commented out.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: plasma-pa 4:5.10.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Sep  8 23:07:29 2017
  InstallationDate: Installed on 2016-11-15 (298 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  SourcePackage: plasma-pa
  UpgradeStatus: Upgraded to artful on 2017-08-27 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1716092/+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 1716092] Re: Enabling Auto switching streams on new active output causes pulseaudio to crash

If it still works commented out then it sounds like your definition of "when a 
new output becomes available" is covered by the similar:
  load-module module-switch-on-port-available

As for removing module-switch-on-connect, we already plan to do that in
18.04 with the introduction of PulseAudio 11 since it has better
defaults which handle all the device hotplugging cases we care about
(Bluetooth devices and USB DACs).

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

Title:
  Enabling Auto switching streams on new active output causes pulseaudio
  to crash

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Not sure if this is a plasma-pa bug or a pulseaudio bug.  In plasma-pa
  -> Audio Volumue -> Advanced tab checking the "Automatically
  switch all running streams when a new output becomes available" cause
  PA to crash.  If the /etc/pulse/default.pa file is modified by
  commenting out following line:

load-module module-switch-on-connect

  PA will start as expected.  I have not checked to see if the auto
  switching works when the default.pa line is commented out.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: plasma-pa 4:5.10.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Sep  8 23:07:29 2017
  InstallationDate: Installed on 2016-11-15 (298 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  SourcePackage: plasma-pa
  UpgradeStatus: Upgraded to artful on 2017-08-27 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1716092/+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

It appears forwarding was blocked by uncertainty around comments made by
the upstream reporter saying he would not accept it (although I'm not
sure he himself is upstream):

https://bugzilla.gnome.org/show_bug.cgi?id=783169#c7

At the time I ignored that comment because it's not a good enough reason
to reject the approach. The patch we use in comment #12 above is trivial
and perfectly solves this bug. However the upstream comment is about the
same approach not solving other issues that might arise from a user
setting his/her own *_BACKEND environment variables.

I don't think that upstream comment should be considered a blocker.
While valid, it is not pragmatic and the patch we use is perfectly safe
and closes the bug. Upstream really is asking us to solve larger
gstreamer design problems which Ubuntu isn't interested in solving right
now.

-- 
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 chromium-browser package in Ubuntu:
  Confirmed
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Won't Fix
Status in libva package in Ubuntu:
  Triaged
Status in mpv package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Triaged

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 1694303] Re: Font issues in Zesty: White text on grey background is unreadable

** Summary changed:

- Font issues in Zesty
+ Font issues in Zesty: White text on grey background is unreadable

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

Title:
  Font issues in Zesty: White text on grey background is unreadable

Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  I have a couple of font issues with gitg (version: 3.23.0-1) in Zesty:

  - commit description text is white (which is unreadable on light gray 
background in the default Ubuntu theme)
  - diffs are not in monospaced font anymore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1694303/+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 1719445] Re: package libx11-dev 2:1.6.3-1ubuntu2 [modified: usr/include/X11/Xcms.h usr/include/X11/Xlibint.h usr/include/X11/Xlocale.h usr/include/X11/Xregion.h usr/include/X11/X

2017-09-25 Thread 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 libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/1719445

Title:
  package libx11-dev 2:1.6.3-1ubuntu2 [modified: usr/include/X11/Xcms.h
  usr/include/X11/Xlibint.h usr/include/X11/Xlocale.h
  usr/include/X11/Xregion.h usr/include/X11/Xutil.h] failed to
  install/upgrade: trying to overwrite shared '/usr/include/X11/Xcms.h',
  which is different from other instances of package libx11-dev:i386

Status in libx11 package in Ubuntu:
  New

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libx11-dev 2:1.6.3-1ubuntu2 [modified: usr/include/X11/Xcms.h 
usr/include/X11/Xlibint.h usr/include/X11/Xlocale.h usr/include/X11/Xregion.h 
usr/include/X11/Xutil.h]
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.4
  AptOrdering:
   libx11-dev: Install
   libx11-dev: Configure
   libx11-dev: Configure
   NULL: ConfigurePending
  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: Mon Sep 25 22:30:49 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 4.4.0-36-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-59-generic, x86_64: installed (WARNING! 
Diff between built and installed module!)
   broadcom-sta, 6.30.223.271, 4.4.0-59-generic, x86_64: installed
  DpkgHistoryLog:
   Start-Date: 2017-09-25  22:30:48
   Commandline: apt-get -f install
   Requested-By: adrien (1000)
   Upgrade: libx11-dev:i386 (2:1.4.99.1-0ubuntu2.3, 2:1.6.3-1ubuntu2)
  DpkgLog:
   2017-09-25 22:30:48 startup archives unpack
   2017-09-25 22:30:49 upgrade libx11-dev:i386 2:1.4.99.1-0ubuntu2.3 
2:1.6.3-1ubuntu2
   2017-09-25 22:30:49 status half-installed libx11-dev:i386 
2:1.4.99.1-0ubuntu2.3
   2017-09-25 22:30:49 status unpacked libx11-dev:i386 2:1.4.99.1-0ubuntu2.3
  DpkgTerminalLog:
   Preparing to unpack .../libx11-dev_2%3a1.6.3-1ubuntu2_i386.deb ...
   Unpacking libx11-dev:i386 (2:1.6.3-1ubuntu2) over (2:1.4.99.1-0ubuntu2.3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libx11-dev_2%3a1.6.3-1ubuntu2_i386.deb (--unpack):
trying to overwrite shared '/usr/include/X11/Xcms.h', which is different 
from other instances of package libx11-dev:i386
  DuplicateSignature:
   package:libx11-dev:2:1.6.3-1ubuntu2 [modified: usr/include/X11/Xcms.h 
usr/include/X11/Xlibint.h usr/include/X11/Xlocale.h usr/include/X11/Xregion.h 
usr/include/X11/Xutil.h]
   Unpacking libx11-dev:i386 (2:1.6.3-1ubuntu2) over (2:1.4.99.1-0ubuntu2.3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libx11-dev_2%3a1.6.3-1ubuntu2_i386.deb (--unpack):
trying to overwrite shared '/usr/include/X11/Xcms.h', which is different 
from other instances of package libx11-dev:i386
  ErrorMessage: trying to overwrite shared '/usr/include/X11/Xcms.h', which is 
different from other instances of package libx11-dev:i386
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Broadwell-U Integrated Graphics 
[1179:f840]
  InstallationDate: Installed on 2016-09-03 (387 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: TOSHIBA Satellite C55-C
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed 
root=UUID=5a16cdbd-726a-45b9-944a-6b66f4f8e612 ro quiet splash radeon.audio=1 
vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: libx11
  Title: package libx11-dev 2:1.6.3-1ubuntu2 [modified: usr/include/X11/Xcms.h 
usr/include/X11/Xlibint.h usr/include/X11/Xlocale.h usr/include/X11/Xregion.h 
usr/include/X11/Xutil.h] failed to install/upgrade: trying to overwrite shared 
'/usr/include/X11/Xcms.h', which is different from other instances of package 
libx11-dev:i386
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 5.10
  dmi.board.name: 06F2
  dmi.board.vendor: FF50
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr5.10:bd09/11/2015:svnTOSHIBA:pnSatelliteC55-C:pvrPSCPJU-00R011:rvnFF50:rn06F2:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite C55-C
  dmi.product.version: PSCPJU-00R011

[Touch-packages] [Bug 1719445] [NEW] package libx11-dev 2:1.6.3-1ubuntu2 [modified: usr/include/X11/Xcms.h usr/include/X11/Xlibint.h usr/include/X11/Xlocale.h usr/include/X11/Xregion.h usr/include/X11

2017-09-25 Thread Adrien Lacroix

Public bug reported:

I don't know

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libx11-dev 2:1.6.3-1ubuntu2 [modified: usr/include/X11/Xcms.h 
usr/include/X11/Xlibint.h usr/include/X11/Xlocale.h usr/include/X11/Xregion.h 
usr/include/X11/Xutil.h]
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.4
AptOrdering:
 libx11-dev: Install
 libx11-dev: Configure
 libx11-dev: Configure
 NULL: ConfigurePending
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: Mon Sep 25 22:30:49 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.248+bdcom, 4.4.0-36-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 4.4.0-59-generic, x86_64: installed (WARNING! Diff 
between built and installed module!)
 broadcom-sta, 6.30.223.271, 4.4.0-59-generic, x86_64: installed
DpkgHistoryLog:
 Start-Date: 2017-09-25  22:30:48
 Commandline: apt-get -f install
 Requested-By: adrien (1000)
 Upgrade: libx11-dev:i386 (2:1.4.99.1-0ubuntu2.3, 2:1.6.3-1ubuntu2)
DpkgLog:
 2017-09-25 22:30:48 startup archives unpack
 2017-09-25 22:30:49 upgrade libx11-dev:i386 2:1.4.99.1-0ubuntu2.3 
2:1.6.3-1ubuntu2
 2017-09-25 22:30:49 status half-installed libx11-dev:i386 2:1.4.99.1-0ubuntu2.3
 2017-09-25 22:30:49 status unpacked libx11-dev:i386 2:1.4.99.1-0ubuntu2.3
DpkgTerminalLog:
 Preparing to unpack .../libx11-dev_2%3a1.6.3-1ubuntu2_i386.deb ...
 Unpacking libx11-dev:i386 (2:1.6.3-1ubuntu2) over (2:1.4.99.1-0ubuntu2.3) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libx11-dev_2%3a1.6.3-1ubuntu2_i386.deb (--unpack):
  trying to overwrite shared '/usr/include/X11/Xcms.h', which is different from 
other instances of package libx11-dev:i386
DuplicateSignature:
 package:libx11-dev:2:1.6.3-1ubuntu2 [modified: usr/include/X11/Xcms.h 
usr/include/X11/Xlibint.h usr/include/X11/Xlocale.h usr/include/X11/Xregion.h 
usr/include/X11/Xutil.h]
 Unpacking libx11-dev:i386 (2:1.6.3-1ubuntu2) over (2:1.4.99.1-0ubuntu2.3) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libx11-dev_2%3a1.6.3-1ubuntu2_i386.deb (--unpack):
  trying to overwrite shared '/usr/include/X11/Xcms.h', which is different from 
other instances of package libx11-dev:i386
ErrorMessage: trying to overwrite shared '/usr/include/X11/Xcms.h', which is 
different from other instances of package libx11-dev:i386
GraphicsCard:
 Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems Broadwell-U Integrated Graphics 
[1179:f840]
InstallationDate: Installed on 2016-09-03 (387 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: TOSHIBA Satellite C55-C
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed 
root=UUID=5a16cdbd-726a-45b9-944a-6b66f4f8e612 ro quiet splash radeon.audio=1 
vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15ubuntu0.2
SourcePackage: libx11
Title: package libx11-dev 2:1.6.3-1ubuntu2 [modified: usr/include/X11/Xcms.h 
usr/include/X11/Xlibint.h usr/include/X11/Xlocale.h usr/include/X11/Xregion.h 
usr/include/X11/Xutil.h] failed to install/upgrade: trying to overwrite shared 
'/usr/include/X11/Xcms.h', which is different from other instances of package 
libx11-dev:i386
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/11/2015
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 5.10
dmi.board.name: 06F2
dmi.board.vendor: FF50
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis ManuFacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr5.10:bd09/11/2015:svnTOSHIBA:pnSatelliteC55-C:pvrPSCPJU-00R011:rvnFF50:rn06F2:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite C55-C
dmi.product.version: PSCPJU-00R011
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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:

[Touch-packages] [Bug 1719077] Re: Unable to find codecs to play videos

This bug was fixed in the package packagekit - 1.1.7-1

---
packagekit (1.1.7-1) unstable; urgency=medium

  [ Matthias Klumpp ]
  * New upstream version: 1.1.7
  * Drop all patches: Applied upstream
  * Add aptcc-fix-mimetype-search.patch: Don't fail when searching for mimetypes
- See LP: #1719077
  * Bump standards and dh version
  * Fail on missing files
  * Add missing build-dependency on libappstream-dev

  [ Iain Lane ]
  * Always rebuild gtk-doc documentation

 -- Matthias Klumpp   Sun, 24 Sep 2017 19:56:12 +0200

** Changed in: packagekit (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 grilo-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1719077

Title:
  Unable to find codecs to play videos

Status in Grilo Plugins:
  Confirmed
Status in grilo-plugins package in Ubuntu:
  New
Status in packagekit package in Ubuntu:
  Fix Released

Bug description:
  There are two bugs here:
  1. packagekit was using app-install-data to search for missing codecs
  2. The Guardian Videos channel does not work

  (1) is supposedly fixed in all cases.

  To reproduce:

  1. Open Totem
  2. Go to Channels and select The Guardian Videos
  3. Select any video
  4. Totem complains about missing codecs
  5. GNOME Software then complains that app-install-data is missing

  See screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-software 3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 23 11:54:53 2017
  InstallationDate: Installed on 2017-09-21 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.0-0ubuntu2
  PackageArchitecture: all
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/grilo-plugins/+bug/1719077/+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 1132736] Re: Xorg fails to start after installing the Hardware Enablement Stack due to missing symlink after purging old xserver-xorg

2017-09-25 Thread Naël

Still affects xorg-lts-trusty for the users of releases < Trusty LTS,
but all of those releases e.g. Precise LTS are EOL now.

There is therefore no point in fixing this package, it won't be
installed by anybody any more.

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

Title:
  Xorg fails to start after installing the Hardware Enablement Stack due
  to missing symlink after purging old xserver-xorg

Status in xorg package in Ubuntu:
  Invalid
Status in xorg-lts-trusty package in Ubuntu:
  Confirmed
Status in xorg-lts-utopic package in Ubuntu:
  Won't Fix
Status in xorg-lts-vivid package in Ubuntu:
  Fix Released

Bug description:
  Bug:

  The bug happens whenever the remaining configuration files of the
  original X stack is removed, ie purging. It does not happen for users
  who do not explicitly remove those.

  Workaround:

  For example, if upgraded 14.04 LTS to the 14.04.2 HWE stack
  (=14.10/utopic):

  sudo dpkg-reconfigure xserver-xorg-lts-utopic

  This restores the symlink /etc/X11/X -> /usr/bin/Xorg

  ---

  After installing the hardware enablement stack on precise by running:
  sudo apt-get install linux-generic-lts-quantal xserver-xorg-lts-quantal

  Xorg fail to start. There is no error message or anything, just a black 
screen. Switching to a vt i possible and lightdm/x-0.log shows that a symlink 
is missing:
  X: cannot stat /etc/X11/X (No such file or directory), aborting.

  I updates two computers running precise x86_64 and both had the
  problem.

  Just recreating the symlink fixes the problem and then precise runs
  perfectly fine with the new stack (in fact, it's more stable so far).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1132736/+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 1718824] Re: The analogue audio does not work on the Dell USB Dock

Fix committed for xenial:
https://git.launchpad.net/~ubuntu-audio-dev/pulseaudio/commit/?h=ubuntu-xenial=312b9b8d36b90c6bae520722cf68e01b53832eeb

But I forgot to ask: Does the same fix exist in artful already? It's
part of the SRU process that the next release needs to have the fix
first, before xenial.

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+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 1718927] Re: No hdmi sound after suspend/resume on 16.04

At a guess, your system is probably reverting back to the default audio
device on resume.

What does it look like in Settings after resuming? Can you change the
audio playback device back to HDMI by hand?

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

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

Title:
  No hdmi sound after suspend/resume on 16.04

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When plugging in a HDMI TV to Lenovo Carbon 3rd Edition, sound works
  perfectly, but when I suspend computer and resume it there is no sound
  via HDMI in TV. However sound via built in speakers works fine. The
  only thing I can do to restore sound is to reboot the machine. Similar
  problem was discussed in following thread
  https://ubuntuforums.org/showthread.php?t=2251651 with no solution. I
  tested it on several versions of kernel 4.4.0 and on 4.4.8. Still no
  solution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1718927/+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 1718932] Re: Child windows do not have shadows

Confirmed, but I think this was by design (chosen by upstream Gnome). We
have not yet changed it, or decided to change it.

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Incomplete

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

** Summary changed:

- Child windows do not have shadows
+ Child windows do not have shadows in Gnome Shell

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

Title:
  Child windows do not have shadows in Gnome Shell

Status in Ubuntu UX:
  New
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in ubuntu-themes package in Ubuntu:
  Incomplete

Bug description:
  Some child windows do not have shadows.

  Test case:
  Open Thunderbird for the first time.
  A child window will appear to create a new account.
  It does not have shadows.

  Synaptic package manager also have the same issue.

  See screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 14:20:26 2017
  InstallationDate: Installed on 2017-09-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1718932/+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 1718932] Re: Child windows do not have shadows

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

** 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/1718932

Title:
  Child windows do not have shadows in Gnome Shell

Status in Ubuntu UX:
  New
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in ubuntu-themes package in Ubuntu:
  Incomplete

Bug description:
  Some child windows do not have shadows.

  Test case:
  Open Thunderbird for the first time.
  A child window will appear to create a new account.
  It does not have shadows.

  Synaptic package manager also have the same issue.

  See screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 14:20:26 2017
  InstallationDate: Installed on 2017-09-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1718932/+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 1718932] Re: Child windows do not have shadows

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 ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1718932

Title:
  Child windows do not have shadows in Gnome Shell

Status in Ubuntu UX:
  New
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in ubuntu-themes package in Ubuntu:
  Incomplete

Bug description:
  Some child windows do not have shadows.

  Test case:
  Open Thunderbird for the first time.
  A child window will appear to create a new account.
  It does not have shadows.

  Synaptic package manager also have the same issue.

  See screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 14:20:26 2017
  InstallationDate: Installed on 2017-09-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1718932/+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 1718932] Re: Child windows do not have shadows

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Child windows do not have shadows in Gnome Shell

Status in Ubuntu UX:
  New
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in ubuntu-themes package in Ubuntu:
  Incomplete

Bug description:
  Some child windows do not have shadows.

  Test case:
  Open Thunderbird for the first time.
  A child window will appear to create a new account.
  It does not have shadows.

  Synaptic package manager also have the same issue.

  See screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 14:20:26 2017
  InstallationDate: Installed on 2017-09-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1718932/+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 1719355] Re: Switcher widget background goes outside its border

Incomplete for ubuntu-themes, pending comments from Design.

I really can't tell if the border is an intentional feature or not.
Previously I assumed it was intentional but now you mention it, am not
sure.

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

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

** Changed in: ubuntu-themes
   Status: Confirmed => Incomplete

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

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

Title:
  Switcher widget background goes outside its border

Status in Ubuntu theme:
  Incomplete
Status in Ubuntu UX:
  New
Status in ubuntu-themes package in Ubuntu:
  Incomplete

Bug description:
  In both Ambiance and Radiance themes, the switcher background is
  visible outside the widget border when inside a headerbar.

  
  See picture from Gnome Control Settings -> Search

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1719355/+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 1719408] [NEW] Application window outside of its frame in spread mode

2017-09-25 Thread Jean-Baptiste Lallement

Public bug reported:

Test Case:
1. On a workspace with no window, toggle spread mode (super key)
2. Open a terminal with its keybinding: CTRL+ALT+T

Expected result
The terminal opens in the center of the screen with a frame around it

Actual result
The frame is displayed in the center of the screen but the application window 
is outside of the frame (cf screenshot)

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libwayland-bin 1.14.0-1
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 25 15:00:29 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.13.0-11-generic, x86_64: installed
 virtualbox, 5.1.28, 4.13.0-11-generic, x86_64: installed
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller 
[1043:1507]
InstallationDate: Installed on 2013-09-03 (1482 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
MachineType: ASUSTeK COMPUTER INC. UX32VD
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic.efi.signed 
root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force 
drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart
SourcePackage: wayland
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/29/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX32VD.214
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX32VD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: UX
dmi.product.name: UX32VD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.82-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.1-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.1-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu6
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-1
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.15-2

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


** Tags: amd64 apport-bug artful reproducible ubuntu wayland-session

** Attachment added: "Capture d’écran de 2017-09-25 14-59-10.png"
   
https://bugs.launchpad.net/bugs/1719408/+attachment/4956909/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202017-09-25%2014-59-10.png

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

Title:
  Application window outside of its frame in spread mode

Status in wayland package in Ubuntu:
  New

Bug description:
  Test Case:
  1. On a workspace with no window, toggle spread mode (super key)
  2. Open a terminal with its keybinding: CTRL+ALT+T

  Expected result
  The terminal opens in the center of the screen with a frame around it

  Actual result
  The frame is displayed in the center of the screen but the application window 
is outside of the frame (cf screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libwayland-bin 1.14.0-1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 25 15:00:29 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-11-generic, x86_64: installed
   virtualbox, 5.1.28, 4.13.0-11-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA

[Touch-packages] [Bug 1719384] Re: Sync packagekit 1.1.7-1 (main) from Debian unstable (main)

2017-09-25 Thread Iain Lane

This bug was fixed in the package packagekit - 1.1.7-1
Sponsored for Matthias Klumpp (ximion)

---
packagekit (1.1.7-1) unstable; urgency=medium

  [ Matthias Klumpp ]
  * New upstream version: 1.1.7
  * Drop all patches: Applied upstream
  * Add aptcc-fix-mimetype-search.patch: Don't fail when searching for mimetypes
- See LP: #1719077
  * Bump standards and dh version
  * Fail on missing files
  * Add missing build-dependency on libappstream-dev

  [ Iain Lane ]
  * Always rebuild gtk-doc documentation

 -- Matthias Klumpp   Sun, 24 Sep 2017 19:56:12 +0200

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

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

Title:
  Sync packagekit 1.1.7-1 (main) from Debian unstable (main)

Status in packagekit package in Ubuntu:
  Fix Released

Bug description:
  Please sync packagekit 1.1.7-1 (main) from Debian unstable (main)

  Changelog entries since current artful version 1.1.6-2:

  packagekit (1.1.7-1) unstable; urgency=medium

[ Matthias Klumpp ]
* New upstream version: 1.1.7
* Drop all patches: Applied upstream
* Add aptcc-fix-mimetype-search.patch: Don't fail when searching for 
mimetypes
  - See LP: #1719077
* Bump standards and dh version
* Fail on missing files
* Add missing build-dependency on libappstream-dev

[ Iain Lane ]
* Always rebuild gtk-doc documentation

   -- Matthias Klumpp   Sun, 24 Sep 2017 19:56:12 +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1719384/+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 1539209] Update Released

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

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

Title:
  pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from
  source_set_volume_cb() from pa_source_process_msg()

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released
Status in pulseaudio source package in Zesty:
  New
Status in pulseaudio source package in Artful:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/49276ec9f717c5268dfc99940a28fb4a56fe1b4a

  ---

  [Impact]
  pulseaudio daemon crashes, interrupting sound output/input.

  [Test Case]
  Theoretical test case (crash does not happen for all users):
  1. Find some headphones and/or microphone. Ensure you do not wear the
     headphones during the test as it may be loud.
  2. Set audio output/input volumes to maximum.
  3. Unplug and replug the headphones/microphone.
  4. Check that that pulseaudio process is still running, with a start time
     older than when you began this test case.

  [Regression Potential]
  Low. This SRU affects the pulseaudio daemon only so the worst case would be 
loss of sound output/input. The same patches have been released to
  17.10 for a month already and zero regressions of the crashes have
  occurred worldwide since then.

  [Original Description]

  Appears randomly.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:7.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   potato12883 F...m pulseaudio
   /dev/snd/controlC0:  potato12883 F pulseaudio
   /dev/snd/controlC1:  potato12883 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jan 28 22:16:03 2016
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-01-17 (11 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=ru_RU.UTF-8
   LANGUAGE=ru
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_alsa_path_set_volume () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   pa_source_process_msg () from /usr/lib/libpulsecore-7.1.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/libpulsecore-7.1.so
  Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
  UpgradeStatus: Upgraded to xenial on 2016-01-28 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.11
  dmi.board.name: JV71TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 7540
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-01-25T21:44:07.089113

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1539209/+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 1562817] Update Released

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

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

Title:
pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from
source_write_volume_cb() from source_set_port_cb() from
pa_source_process_msg() from source_process_msg()

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

Bug description:
https://errors.ubuntu.com/problem/3bb5044276ea358334e8e662559a1cbd45240cd9

---

[Impact]
pulseaudio daemon crashes, interrupting sound output/input.

[Test Case]
Theoretical test case (crash does not happen for all users):
1. Find some headphones and/or microphone. Ensure you do not wear the
headphones during the test as it may be loud.
2. Set audio output/input volumes to maximum.
3. Unplug and replug the headphones/microphone.
4. Check that that pulseaudio process is still running, with a start time
older than when you began this test case.

[Regression Potential]
Low. This SRU affects the pulseaudio daemon only so the worst case would be
loss of sound output/input. The same patches have been released to
17.10 for a month already and zero regressions of the crashes have
occurred worldwide since then.

[Other Info]
Debdiff patch is attached to the most prolific bug 1539209.

[Original Description]

This error is there when i get back to the computer after a while of
no use, and at login after restart. haven't seen this error while the
system is "active"/in use.

I have been unable to provoke the error to come.

I'm not sure it is related, but when i plug in a headset, the audio volume
goes through the roof, and a loud (painfully so) scratching sound is coming
from the headset until i press Vol+. Vol- does nothing till i have pressed up
at least once.
But the bug report thing does not pop up when the sound issue is there.

Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04

pulseaudio:
Installed: 1:8.0-0ubuntu2
Candidate: 1:8.0-0ubuntu2
Version table:
*** 1:8.0-0ubuntu2 500
500 http://dk.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: tbs 22776 F pulseaudio
CrashCounter: 1
CurrentDesktop: Unity
Date: Mon Mar 28 12:39:45 2016
ExecutablePath: /usr/bin/pulseaudio
InstallationDate: Installed on 2016-01-14 (73 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
Signal: 6
SourcePackage: pulseaudio
StacktraceTop:
pa_alsa_path_set_volume () from /usr/lib/pulse-8.0/modules/libalsa-util.so
?? () from /usr/lib/pulse-8.0/modules/libalsa-util.so
?? () from /usr/lib/pulse-8.0/modules/libalsa-util.so
pa_source_process_msg () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
?? () from /usr/lib/pulse-8.0/modules/libalsa-util.so
Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
UpgradeStatus: Upgraded to xenial on 2016-03-19 (8 days ago)
UserGroups: adm cdrom dialout dip lp lpadmin plugdev root sambashare sudo
vboxusers
dmi.bios.date: 09/18/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: G5ETA3WW (2.63 )
dmi.board.asset.tag: Not Available
dmi.board.name: 244743G
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvrG5ETA3WW(2.63):bd09/18/2015:svnLENOVO:pn244743G:pvrThinkPadW530:rvnLENOVO:rn244743G:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 244743G
dmi.product.version: ThinkPad W530
dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_set_volume_cb() from pa_source_process_msg()

This bug was fixed in the package pulseaudio - 1:8.0-0ubuntu3.4

---
pulseaudio (1:8.0-0ubuntu3.4) xenial; urgency=medium

  * debian/control: Update Vcs fields to launchpad git.
  * Cherrypick fixes for common crashes from upstream:
- cb78d6f5: SIGABRT in device_start_waiting_for_profiles (LP: #1690028,
  LP: #1672171)
- d985276c: SIGABRT in pa_alsa_path_set_volume (LP: #1539209, LP: #1562817)

 -- Daniel van Vugt   Fri, 11 Aug 2017
15:16:57 +0800

** Changed in: pulseaudio (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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1539209

Title:
  pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from
  source_set_volume_cb() from pa_source_process_msg()

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released
Status in pulseaudio source package in Zesty:
  New
Status in pulseaudio source package in Artful:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/49276ec9f717c5268dfc99940a28fb4a56fe1b4a

  ---

  [Impact]
  pulseaudio daemon crashes, interrupting sound output/input.

  [Test Case]
  Theoretical test case (crash does not happen for all users):
  1. Find some headphones and/or microphone. Ensure you do not wear the
     headphones during the test as it may be loud.
  2. Set audio output/input volumes to maximum.
  3. Unplug and replug the headphones/microphone.
  4. Check that that pulseaudio process is still running, with a start time
     older than when you began this test case.

  [Regression Potential]
  Low. This SRU affects the pulseaudio daemon only so the worst case would be 
loss of sound output/input. The same patches have been released to
  17.10 for a month already and zero regressions of the crashes have
  occurred worldwide since then.

  [Original Description]

  Appears randomly.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:7.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   potato12883 F...m pulseaudio
   /dev/snd/controlC0:  potato12883 F pulseaudio
   /dev/snd/controlC1:  potato12883 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jan 28 22:16:03 2016
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-01-17 (11 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=ru_RU.UTF-8
   LANGUAGE=ru
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_alsa_path_set_volume () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   pa_source_process_msg () from /usr/lib/libpulsecore-7.1.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/libpulsecore-7.1.so
  Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
  UpgradeStatus: Upgraded to xenial on 2016-01-28 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.11
  dmi.board.name: JV71TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 7540
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-01-25T21:44:07.089113

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1539209/+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 1562817] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_write_volume_cb() from source_set_port_cb() from pa_source_process_msg() from source_process

This bug was fixed in the package pulseaudio - 1:8.0-0ubuntu3.4

---
pulseaudio (1:8.0-0ubuntu3.4) xenial; urgency=medium

* debian/control: Update Vcs fields to launchpad git.
* Cherrypick fixes for common crashes from upstream:
- cb78d6f5: SIGABRT in device_start_waiting_for_profiles (LP: #1690028,
LP: #1672171)
- d985276c: SIGABRT in pa_alsa_path_set_volume (LP: #1539209, LP: #1562817)

-- Daniel van Vugt Fri, 11 Aug 2017
15:16:57 +0800

** Changed in: pulseaudio (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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1562817

Title:
pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from
source_write_volume_cb() from source_set_port_cb() from
pa_source_process_msg() from source_process_msg()

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

Bug description:
https://errors.ubuntu.com/problem/3bb5044276ea358334e8e662559a1cbd45240cd9

---

[Impact]
pulseaudio daemon crashes, interrupting sound output/input.

[Other Info]
Debdiff patch is attached to the most prolific bug 1539209.

[Original Description]

This error is there when i get back to the computer after a while of
no use, and at login after restart. haven't seen this error while the
system is "active"/in use.

I have been unable to provoke the error to come.

Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04

pulseaudio:
Installed: 1:8.0-0ubuntu2
Candidate: 1:8.0-0ubuntu2
Version table:
*** 1:8.0-0ubuntu2 500
500 http://dk.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

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

--
Mailing

[Touch-packages] [Bug 1672171] Update Released

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

Title:
pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles()
from pa_bluetooth_transport_set_state() from profile_new_connection()
from profile_handler() from _dbus_object_tree_dispatch_and_unlock()

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

Bug description:
[Impact]
pulseaudio daemon crashes, interrupting sound output/input.

[Test Case]
Theoretical test case (crash does not happen for all users):
1. Get a Bluetooth audio device capable of multiple profiles (e.g. high
fidelity A2DP and the lower quality headset profiles).
2. Pair it with your machine and select the device in sound settings.
3. Turn the Bluetooth audio device off and on again, making sure it is
set to active if not automatically so.
4. Select the device in sound settings.
5. Check that that pulseaudio process is still running, with a start
time older than when you began this test case.

[Regression Potential]
Low. This SRU affects the pulseaudio daemon only so the worst case would
be loss of sound output/input. The same patches have been released to
17.10 for a month already and zero regressions of the crashes have
occurred worldwide since then.

[Other Info]
Debdiff patch is attached to the most prolific bug 1539209.

[Original Description]

Bluetooth device keep disconnect and audio output tab is empty

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: pulseaudio 1:10.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
Uname: Linux 4.10.0-11-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: bikram14994 F pulseaudio
/dev/snd/controlC0: bikram14994 F pulseaudio
CrashCounter: 1
CurrentDesktop: Unity:Unity7
Date: Sun Mar 12 21:52:24 2017
ExecutablePath: /usr/bin/pulseaudio
ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
Signal: 6
SourcePackage: pulseaudio
StacktraceTop:
pa_bluetooth_transport_set_state () from
/usr/lib/pulse-10.0/modules/libbluez5-util.so
?? () from /usr/lib/pulse-10.0/modules/libbluez5-util.so
?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so
Title: pulseaudio crashed with SIGABRT in pa_bluetooth_transport_set_state()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
dmi.bios.date: 11/14/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0Y004V
dmi.board.vendor: Dell Inc.
dmi.board.version: A07
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvrA07:bd11/14/2013:svnDellInc.:pnInspiron3437:pvrNotSpecified:rvnDellInc.:rn0Y004V:rvrA07:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 3437
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1672171/+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 1672171] Re: pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles() from pa_bluetooth_transport_set_state() from profile_new_connection() from profile_handler() f

This bug was fixed in the package pulseaudio - 1:8.0-0ubuntu3.4

---
pulseaudio (1:8.0-0ubuntu3.4) xenial; urgency=medium

-- Daniel van Vugt Fri, 11 Aug 2017
15:16:57 +0800

** Changed in: pulseaudio (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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1672171

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

Bug description:
[Impact]
pulseaudio daemon crashes, interrupting sound output/input.

[Regression Potential]
Low. This SRU affects the pulseaudio daemon only so the worst case would
be loss of sound output/input. The same patches have been released to
17.10 for a month already and zero regressions of the crashes have
occurred worldwide since then.

[Other Info]
Debdiff patch is attached to the most prolific bug 1539209.

[Original Description]

Bluetooth device keep disconnect and audio output tab is empty

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1672171/+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 1690028] Update Released

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

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

Title:
  pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles()
  from pa_bluetooth_transport_set_state() from
  endpoint_set_configuration() from endpoint_handler() from
  _dbus_object_tree_dispatch_and_unlock()

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

Bug description:
  [Impact]
  pulseaudio daemon crashes, interrupting sound output/input.

  [Test Case]
  Theoretical test case (crash does not happen for all users):
  1. Get a Bluetooth audio device capable of multiple profiles (e.g. high 
 fidelity A2DP and the lower quality headset profiles).
  2. Pair it with your machine and select the device in sound settings.
  3. Turn the Bluetooth audio device off and on again, making sure it is 
 set to active if not automatically so.
  4. Select the device in sound settings.
  5. Check that that pulseaudio process is still running, with a start 
 time older than when you began this test case.

  [Regression Potential]
  Low. This SRU affects the pulseaudio daemon only so the worst case would 
  be loss of sound output/input. The same patches have been released to
  17.10 for a month already and zero regressions of the crashes have
  occurred worldwide since then.

  [Other Info]
  Debdiff patch is attached to the most prolific bug 1539209.

  [Original Description]

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:10.0-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/5a76b9eca937daf6dc05fd32a35fa50e58ccf8f5 
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/pulseaudio/+bug/1690028/+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 1690028] Re: pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles() from pa_bluetooth_transport_set_state() from endpoint_set_configuration() from endpoint_handle

This bug was fixed in the package pulseaudio - 1:8.0-0ubuntu3.4

---
pulseaudio (1:8.0-0ubuntu3.4) xenial; urgency=medium

  * debian/control: Update Vcs fields to launchpad git.
  * Cherrypick fixes for common crashes from upstream:
- cb78d6f5: SIGABRT in device_start_waiting_for_profiles (LP: #1690028,
  LP: #1672171)
- d985276c: SIGABRT in pa_alsa_path_set_volume (LP: #1539209, LP: #1562817)

 -- Daniel van Vugt   Fri, 11 Aug 2017
15:16:57 +0800

** Changed in: pulseaudio (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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1690028

Title:
  pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles()
  from pa_bluetooth_transport_set_state() from
  endpoint_set_configuration() from endpoint_handler() from
  _dbus_object_tree_dispatch_and_unlock()

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

Bug description:
  [Impact]
  pulseaudio daemon crashes, interrupting sound output/input.

  [Test Case]
  Theoretical test case (crash does not happen for all users):
  1. Get a Bluetooth audio device capable of multiple profiles (e.g. high 
 fidelity A2DP and the lower quality headset profiles).
  2. Pair it with your machine and select the device in sound settings.
  3. Turn the Bluetooth audio device off and on again, making sure it is 
 set to active if not automatically so.
  4. Select the device in sound settings.
  5. Check that that pulseaudio process is still running, with a start 
 time older than when you began this test case.

  [Regression Potential]
  Low. This SRU affects the pulseaudio daemon only so the worst case would 
  be loss of sound output/input. The same patches have been released to
  17.10 for a month already and zero regressions of the crashes have
  occurred worldwide since then.

  [Other Info]
  Debdiff patch is attached to the most prolific bug 1539209.

  [Original Description]

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:10.0-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/5a76b9eca937daf6dc05fd32a35fa50e58ccf8f5 
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/pulseaudio/+bug/1690028/+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 1562817] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_write_volume_cb() from source_set_port_cb() from pa_source_process_msg() from source_process

** Tags removed: rapport-crash
** Tags added: apport-crash

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

Title:
pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from
source_write_volume_cb() from source_set_port_cb() from
pa_source_process_msg() from source_process_msg()

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

Bug description:
https://errors.ubuntu.com/problem/3bb5044276ea358334e8e662559a1cbd45240cd9

---

[Impact]
pulseaudio daemon crashes, interrupting sound output/input.

[Other Info]
Debdiff patch is attached to the most prolific bug 1539209.

[Original Description]

This error is there when i get back to the computer after a while of
no use, and at login after restart. haven't seen this error while the
system is "active"/in use.

I have been unable to provoke the error to come.

Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04

pulseaudio:
Installed: 1:8.0-0ubuntu2
Candidate: 1:8.0-0ubuntu2
Version table:
*** 1:8.0-0ubuntu2 500
500 http://dk.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1562817/+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 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits

2017-09-25 Thread John Johansen

On 09/25/2017 12:16 PM, Vincas Dargis wrote:
> I can provide merge request, and I would like to suggest simplifying
> that ever-growing expression.
> 
> Couldn't it be just [0-9]*? Are there possibility that `/proc` will have
well it could but, its not as tight as I would like, ideally we could give
access to more than just apparmorre and make this tighter.

well actually ideally this will switch over to a kernel var, but that is
not ready yet

> some item, starting with digit, *not* being a pid?
> 

I don't know of any atm, its possible but unlikely

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

Title:
  @{pid} variable broken on systems with pid_max more than 6 digits

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  New

Bug description:
  If your kernel.pid_max sysctl is set higher than the default, say at 7
  digits, the @{pid} variable no longer matches all pids, causing some
  breakage in any profile using it.

  @{pid} is defined in /etc/apparmor.d/tunables:
  
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]}

  It only covers up to 6 digits.

  This Ubuntu 17.04 system has:
  kernel.pid_max = 4194303

  And is showing 
  type=1400 audit(1505588857.828:792): apparmor="DENIED" operation="open" 
profile="libvirt-55e9e12c-e6dc-4f56-a547-8514cf7d9bf3" 
name="/proc/2168180/task/2769256/comm" pid=2168180 comm="qemu-system-x86" 
requested_mask="wr" denied_mask="wr" fsuid=111 ouid=111

  Which should be matched by
  @{PROC}/sys/vm/overcommit_memory r,
  in /etc/apparmor.d/abstractions/libvirt-qemu

  I'm seeing similar failures on 16.04 (2.10.95-0ubuntu2.7), 17.04
  (2.11.0-2ubuntu4) and 17.10 (2.11.0-2ubuntu17)

  I am aware this is a non-default configuration, but I think this
  should work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1717714/+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 1719159] Re: 'service procps start' does nothing

2017-09-25 Thread Jean-Baptiste Lallement

** Tags removed: wayland-session

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

Title:
  'service procps start' does nothing

Status in procps package in Ubuntu:
  New

Bug description:
  /etc/sysctl.d/README says

  After making any changes, please run "service procps start" (or, from
  a Debian package maintainer script "invoke-rc.d procps start").

  however running this command does absolutely nothing on Ubuntu 17.04 (and,
  presumably, any other Ubuntu version since systemd became the main init
  system).

  To actually get your changes written into /proc/sys, you have to do

  service procps reload

  Can you please update the README?

  (This is similar to bug 1332362, but I think that one was Upstart's
  fault.)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: procps 2:3.3.12-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Sep 24 11:26:45 2017
  InstallationDate: Installed on 2016-09-10 (379 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  SourcePackage: procps
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (163 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1719159/+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 1719384] [NEW] Sync packagekit 1.1.7-1 (main) from Debian unstable (main)

2017-09-25 Thread Matthias Klumpp

Public bug reported:

Please sync packagekit 1.1.7-1 (main) from Debian unstable (main)

Changelog entries since current artful version 1.1.6-2:

packagekit (1.1.7-1) unstable; urgency=medium

  [ Matthias Klumpp ]
  * New upstream version: 1.1.7
  * Drop all patches: Applied upstream
  * Add aptcc-fix-mimetype-search.patch: Don't fail when searching for mimetypes
- See LP: #1719077
  * Bump standards and dh version
  * Fail on missing files
  * Add missing build-dependency on libappstream-dev

  [ Iain Lane ]
  * Always rebuild gtk-doc documentation

 -- Matthias Klumpp   Sun, 24 Sep 2017 19:56:12 +0200

** Affects: packagekit (Ubuntu)
 Importance: Wishlist
 Status: New

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

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

Title:
  Sync packagekit 1.1.7-1 (main) from Debian unstable (main)

Status in packagekit package in Ubuntu:
  New

Bug description:
  Please sync packagekit 1.1.7-1 (main) from Debian unstable (main)

  Changelog entries since current artful version 1.1.6-2:

  packagekit (1.1.7-1) unstable; urgency=medium

[ Matthias Klumpp ]
* New upstream version: 1.1.7
* Drop all patches: Applied upstream
* Add aptcc-fix-mimetype-search.patch: Don't fail when searching for 
mimetypes
  - See LP: #1719077
* Bump standards and dh version
* Fail on missing files
* Add missing build-dependency on libappstream-dev

[ Iain Lane ]
* Always rebuild gtk-doc documentation

   -- Matthias Klumpp   Sun, 24 Sep 2017 19:56:12 +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1719384/+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 1701222] Re: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services

2017-09-25 Thread Joseph Salisbury

It is possible.  I've added a systemd bug task.

** Also 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/1701222

Title:
  [Hyper-V] LIS daemons fail to start after disable/re-enable VM
  integration services

Status in linux package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  In Progress
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  In Progress
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  In Progress
Status in systemd source package in Artful:
  New

Bug description:
  Issue description: Hyper-V daemons fail to start after disable/re-
  enable VM integration services.

  Platform: host independent
  Affected daemons - KVP, FCOPY and VSS.

  Distribution name and release: Ubuntu 16.04, Ubuntu 17.04
  Kernel version: 4.11.0-rc7-next-20170421 (for Ubuntu 16.04), 
4.10.0-19-generic (for Ubuntu 17.04)

  Repro rate: 100%

  Steps to reproduce:
  1.Start VM with Guest Services enabled (FCopy daemon starts automatically)
  2.Go to File > Settings > Integration Services, uncheck Guest Services 
and apply (FCopy daemon will stop at this point)
  3.Re-enable Guest Services from VM Settings (Fcopy daemon is not running).
  This is the issue. systemd monitors for the service and if we have the hook 
for the Guest Service, it tries to start the daemon again.
  systemd attempt to start any of the LIS daemons will fail, but manually 
executing the daemon binary, it will start the daemon.

  Additional Info:
  - the steps above can be repro'd with KVP / Data Exchange integration service 
as well.
  - Manually starting hv_fcopy_daemon works fine.
  - other distros (RHEL) does not have this behavior, the LIS daemons are 
started automatically by systemd once we re-enable the integration service.

  On the upstream kernel and the upstream hv daemons, these messages are 
recorded in syslog, once we re-enable the Guest service:
  HV_FCOPY: pread failed: Bad file descriptor
  systemd[1]: hv-fcopy-daemon.service: Main process exited, code=exited, 
status=1/FAILURE
  systemd[1]: hv-fcopy-daemon.service: Unit entered failed state.
  systemd[1]: hv-fcopy-daemon.service: Failed with result 'exit-code'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701222/+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 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]

PulseAudio is what implements most of the Bluetooth audio logic (not
BlueZ, surprising I know). You can contact the developers a few
different ways, documented here:

https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Community/

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

Title:
  A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in
  audio stream"]

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped
  working properly. It was working fine in Jaunty.

  My headphones are detected and configured by pulse, but the audio
  skips as if it's spending half of each second paused. Music is
  buffered so that after I click stop on rhythmbox (or whatever--it
  happens with whatever player I use) the audio continues until it's
  caught up.

  syslog is full of the following lines:
  Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal 
latency to 1.00 ms
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
15128 us (= 2668 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36586 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
35593 us (= 6276 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36597 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32601 us (= 5748 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32589 us (= 5748 bytes) in audio stream

  This is with
  bluez 4.45-0ubuntu4
  pulseaudio1:0.9.15-4ubuntu2 0

  pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
  didn't help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/405294/+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 1719367] [NEW] Day button in gnome-weather is insensitive (colour does not change)

2017-09-25 Thread Amr Ibrahim

Public bug reported:

Steps:

1. Install and open gnome-weather
2. Select a location or let it find one
3. Switch between Today and Tomorrow
4. No change in the colour of the button

The colour of the button should change to indicate which day is selected.
See screenshot.
This does not happen in Adwaita.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: light-themes 16.10+17.10.20170918-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 25 18:53:20 2017
InstallationDate: Installed on 2017-09-21 (4 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

** Attachment added: "Button-insensitive-gnome-weather.png"
   
https://bugs.launchpad.net/bugs/1719367/+attachment/4956830/+files/Button-insensitive-gnome-weather.png

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

Title:
  Day button in gnome-weather is insensitive (colour does not change)

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Steps:

  1. Install and open gnome-weather
  2. Select a location or let it find one
  3. Switch between Today and Tomorrow
  4. No change in the colour of the button

  The colour of the button should change to indicate which day is selected.
  See screenshot.
  This does not happen in Adwaita.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 25 18:53:20 2017
  InstallationDate: Installed on 2017-09-21 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1719367/+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 1548480] Re: 95packagekit sleep hook weirdly installed in a subdirectory is ignored

2017-09-25 Thread Dirk F

Per the original report:

"2 owing to a bug in pm-utils, separately reported, the previous hook is
run for a second time instead."

Which might have an effect worse than just disconcerting a reader of
/var/log/pm-suspend.log.

Anyhow, even if it's not worth it for the remaining 18 months of 14.04
LTS, the means to pay off the technical debt is there.

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

Title:
  95packagekit sleep hook weirdly installed in a subdirectory is ignored

Status in packagekit package in Ubuntu:
  Fix Released

Bug description:
  The 95packagekit sleep hook provided by packagekit is installed in a 
subdirectory: 
  /usr/lib/pm-utils/sleep.d/95packagekit/95packagekit

  This has two effects:

  1the hook is not run;

  2owing to a bug in pm-utils, separately reported, the previous
  hook is run for a second time instead.

  If #1 was actually the desired effect, the hook should have been
  stored as /usr/lib/pm-utils/sleep.d/95packagekit~ or just omitted.

  If the hook is manually installed as /usr/lib/pm-
  utils/sleep.d/95packagekit, it runs as expected (although the nature
  of the hook's operation means that it may have no obvious effect).

  This issue was observed in 14.04, packagekit 0.8.12-1ubuntu5;
  apparently was OK in 12.04. A packaging bug seems to have appeared
  when 95packagekit was updated in revision 1.2.10.

  Additionally, the hook 95packagekit is incorrectly numbered according
  to the pm-utils HOWTO.hooks convention and should apparently be eg
  45packagekit.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: packagekit 0.8.12-1ubuntu5
  ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Mon Feb 22 19:12:48 2016
  InstallationDate: Installed on 2016-02-21 (0 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  SourcePackage: packagekit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1548480/+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 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]

2017-09-25 Thread JoaoH

Four or five years ago, A2DP just worked... ever since then, not ONE
device that I have tried works...tried internal/external bluetooth
modules, different brands, Dell, HP, Apple, Generic nothing works. Yet
on every device, I can switch to Windows and it works perfectly!

Now, I do not know whom to even contact to address this issue, is it
BlueZ, Pulse Audio, Alsa, or Engelbert Humperdinck... I spent $200 for a
nice pair of Sony BT Headphones, I built a custom PC to make Linux
scream, and I have to plug in the headphones by wire... This issue has
been documented, reported all over the internet, no one cares!

Joao

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

Title:
  A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in
  audio stream"]

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped
  working properly. It was working fine in Jaunty.

  My headphones are detected and configured by pulse, but the audio
  skips as if it's spending half of each second paused. Music is
  buffered so that after I click stop on rhythmbox (or whatever--it
  happens with whatever player I use) the audio continues until it's
  caught up.

  syslog is full of the following lines:
  Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal 
latency to 1.00 ms
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
15128 us (= 2668 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36586 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
35593 us (= 6276 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36597 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32601 us (= 5748 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32589 us (= 5748 bytes) in audio stream

  This is with
  bluez 4.45-0ubuntu4
  pulseaudio1:0.9.15-4ubuntu2 0

  pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
  didn't help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/405294/+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 1718394] Re: CUPS - Can't detect file type

2017-09-25 Thread Till Kamppeter

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

** This bug has been marked a duplicate of bug 1718215
   versions of cups-filters and libqpdf do not match

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

Title:
  CUPS - Can't detect file type

Status in cups package in Ubuntu:
  Invalid
Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Released

Bug description:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10
  Kernel Linux 4.12.0-13-generic x86_64

  Can't detect file type when using CUPS with Canon MG5700-series
  drivers (driverless and cups-gutenprint) - when printing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1718394/+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 1718258] Re: /boot fills up over and over and over

With which software are you performing upgrades? Are you using update-
manager or something else?

How did you go about removing the extra kernels? Did you try 'sudo apt
autoremove' and did that work or not?

** Tags added: xenial

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Incomplete

** Tags added: full-boot

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

Title:
  /boot fills up over and over and over

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  Recently whenever I perform a software update the /boot directory gets
  filled with dozens of old, worn-out kernel builds. I'm getting sick of
  having to remove them just to see them rebuilt each time a software
  update is attempted and ultimately fails due to a full partition. The
  /boot directory is of reasonable size. Here's df after my most recent
  purge:

  /dev/sda1  482922   113456344532  25% /boot

  pmeidell@eclipse:~$ lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  pmeidell@eclipse:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1718258/+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 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits

2017-09-25 Thread Vincas Dargis

I can provide merge request, and I would like to suggest simplifying
that ever-growing expression.

Couldn't it be just [0-9]*? Are there possibility that `/proc` will have
some item, starting with digit, *not* being a pid?

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

Title:
  @{pid} variable broken on systems with pid_max more than 6 digits

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  New

Bug description:
  If your kernel.pid_max sysctl is set higher than the default, say at 7
  digits, the @{pid} variable no longer matches all pids, causing some
  breakage in any profile using it.

  @{pid} is defined in /etc/apparmor.d/tunables:
  
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]}

  It only covers up to 6 digits.

  This Ubuntu 17.04 system has:
  kernel.pid_max = 4194303

  And is showing 
  type=1400 audit(1505588857.828:792): apparmor="DENIED" operation="open" 
profile="libvirt-55e9e12c-e6dc-4f56-a547-8514cf7d9bf3" 
name="/proc/2168180/task/2769256/comm" pid=2168180 comm="qemu-system-x86" 
requested_mask="wr" denied_mask="wr" fsuid=111 ouid=111

  Which should be matched by
  @{PROC}/sys/vm/overcommit_memory r,
  in /etc/apparmor.d/abstractions/libvirt-qemu

  I'm seeing similar failures on 16.04 (2.10.95-0ubuntu2.7), 17.04
  (2.11.0-2ubuntu4) and 17.10 (2.11.0-2ubuntu17)

  I am aware this is a non-default configuration, but I think this
  should work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1717714/+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 1719302] Re: Please include mlx4 and mlx5 InfiniBand modules

** Tags added: rls-aa-incoming

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

Title:
  Please include mlx4 and mlx5 InfiniBand modules

Status in initramfs-tools package in Ubuntu:
  New
Status in initramfs-tools package in Debian:
  New

Bug description:
  Mellanox ConnectX architecture is:  mlx4_core is the lower level PCI
  driver which register on the PCI id, and protocol specific drivers are
  depended on it: mlx4_en - for Ethernet and mlx4_ib for Infiniband. NIC
  could have multiple ports which can change their type dynamically. We
  use the request_module() call to load the relevant protocol driver
  when needed: on loading time or at port type change event.

  The mlx4_core and mlx5_core modules are included in the initrd, but
  not mlx4_ib and mlx5_ib. Thus the request_module() call will not find
  these modules and fail load them. The mlx*_ib module loading will not
  be retried.

  Therefore also include mlx4_ib and mlx5_ib in the initrd to make
  autoloading them work. A patch is attached to the related Debian bug
  report.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1719302/+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 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]

Indeed it is understandably disappointing, but you need to also consider
that many/most of us have never experienced any such skipping. And if
developers in particular can't reproduce the bug then it's less likely
to get fixed. That's not to say it's unimportant, but a simple matter of
nobody knows what to fix or how to test a fix when the problem isn't
reproducible.

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

Title:
  A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in
  audio stream"]

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped
  working properly. It was working fine in Jaunty.

  My headphones are detected and configured by pulse, but the audio
  skips as if it's spending half of each second paused. Music is
  buffered so that after I click stop on rhythmbox (or whatever--it
  happens with whatever player I use) the audio continues until it's
  caught up.

  syslog is full of the following lines:
  Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal 
latency to 1.00 ms
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
15128 us (= 2668 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36586 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
35593 us (= 6276 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36597 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32601 us (= 5748 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32589 us (= 5748 bytes) in audio stream

  This is with
  bluez 4.45-0ubuntu4
  pulseaudio1:0.9.15-4ubuntu2 0

  pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
  didn't help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/405294/+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 1719354] [NEW] apparmor blocking smbd which is in complain mode

2017-09-25 Thread Aravind R

Public bug reported:

apparmor blocking smbd which is in complain mode

aravind@comp:~$ tail -f /var/log/syslog | grep -i apparmor
Sep 25 21:25:36 comp kernel: [ 4535.034713] audit: type=1400 
audit(1506354936.898:275): apparmor="ALLOWED" operation="open" 
profile="/usr/sbin/smbd" name="/run/samba/msg.lock/4470" pid=5690 comm="smbd" 
requested_mask="w" denied_mask="w" fsuid=0 ouid=0
Sep 25 21:25:36 comp kernel: [ 4535.034719] audit: type=1400 
audit(1506354936.898:276): apparmor="ALLOWED" operation="file_lock" 
profile="/usr/sbin/smbd" name="/run/samba/msg.lock/4470" pid=5690 comm="smbd" 
requested_mask="w" denied_mask="w" fsuid=0 ouid=0
Sep 25 21:27:39 comp kernel: [ 4657.984668] audit: type=1400 
audit(1506355059.847:290): apparmor="ALLOWED" operation="mknod" 
profile="/usr/sbin/smbd" name="/run/samba/msg.lock/6056" pid=6056 comm="smbd" 
requested_mask="c" denied_mask="c" fsuid=0 ouid=0
Sep 25 21:27:39 comp kernel: [ 4657.984675] audit: type=1400 
audit(1506355059.847:291): apparmor="ALLOWED" operation="open" 
profile="/usr/sbin/smbd" name="/run/samba/msg.lock/6056" pid=6056 comm="smbd" 
requested_mask="wc" denied_mask="wc" fsuid=0 ouid=0
Sep 25 21:27:39 comp kernel: [ 4657.984679] audit: type=1400 
audit(1506355059.847:292): apparmor="ALLOWED" operation="file_lock" 
profile="/usr/sbin/smbd" name="/run/samba/msg.lock/6056" pid=6056 comm="smbd" 
requested_mask="w" denied_mask="w" fsuid=0 ouid=0
Sep 25 21:27:39 comp kernel: [ 4657.984684] audit: type=1400 
audit(1506355059.847:293): apparmor="ALLOWED" operation="truncate" 
profile="/usr/sbin/smbd" name="/run/samba/msg.lock/6056" pid=6056 comm="smbd" 
requested_mask="w" denied_mask="w" fsuid=0 ouid=0
Sep 25 21:27:39 comp kernel: [ 4657.991838] audit: type=1400 
audit(1506355059.855:294): apparmor="ALLOWED" operation="unlink" 
profile="/usr/sbin/smbd" name="/run/samba/msg.lock/6056" pid=6056 comm="smbd" 
requested_mask="d" denied_mask="d" fsuid=0 ouid=0
^C

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apparmor 2.10.95-0ubuntu2.7
ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Sep 25 21:27:07 2017
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=3bdb5792-d2a2-4f98-97bd-f274c3d0dde1 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
SourcePackage: apparmor
Syslog:
 Sep 25 10:34:40 comp dbus[1174]: [system] AppArmor D-Bus mediation is enabled
 Sep 25 18:34:05 comp dbus[1083]: [system] AppArmor D-Bus mediation is enabled
 Sep 25 20:10:24 comp dbus[1066]: [system] AppArmor D-Bus mediation is enabled
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  apparmor blocking smbd which is in complain mode

Status in apparmor package in Ubuntu:
  New

Bug description:
  apparmor blocking smbd which is in complain mode

  aravind@comp:~$ tail -f /var/log/syslog | grep -i apparmor
  Sep 25 21:25:36 comp kernel: [ 4535.034713] audit: type=1400 
audit(1506354936.898:275): apparmor="ALLOWED" operation="open" 
profile="/usr/sbin/smbd" name="/run/samba/msg.lock/4470" pid=5690 comm="smbd" 
requested_mask="w" denied_mask="w" fsuid=0 ouid=0
  Sep 25 21:25:36 comp kernel: [ 4535.034719] audit: type=1400 
audit(1506354936.898:276): apparmor="ALLOWED" operation="file_lock" 
profile="/usr/sbin/smbd" name="/run/samba/msg.lock/4470" pid=5690 comm="smbd" 
requested_mask="w" denied_mask="w" fsuid=0 ouid=0
  Sep 25 21:27:39 comp kernel: [ 4657.984668] audit: type=1400 
audit(1506355059.847:290): apparmor="ALLOWED" operation="mknod" 
profile="/usr/sbin/smbd" name="/run/samba/msg.lock/6056" pid=6056 comm="smbd" 
requested_mask="c" denied_mask="c" fsuid=0 ouid=0
  Sep 25 21:27:39 comp kernel: [ 4657.984675] audit: type=1400 
audit(1506355059.847:291): apparmor="ALLOWED" operation="open" 
profile="/usr/sbin/smbd" name="/run/samba/msg.lock/6056" pid=6056 comm="smbd" 
requested_mask="wc" denied_mask="wc" fsuid=0 ouid=0
  Sep 25 21:27:39 comp kernel: [ 4657.984679] audit: type=1400 
audit(1506355059.847:292): apparmor="ALLOWED" operation="file_lock" 
profile="/usr/sbin/smbd" name="/run/samba/msg.lock/6056" pid=6056 comm="smbd" 
requested_mask="w" denied_mask="w" fsuid=0 ouid=0
  Sep 25 21:27:39 comp kernel: [ 4657.984684] audit: type=1400 
audit(1506355059.847:293): apparmor="ALLOWED" operation="truncate" 
profile="/usr/sbin/smbd" name="/run/samba/msg.lock/6056" pid=6056 comm="smbd" 
requested_mask="w" denied_mask="w" fsuid=0 ouid=0
  Sep 25 21:27:39 comp kernel: [ 4657.991838] audit: type=1400 
audit(1506355059.855:294): apparmor="ALLOWED"

[Touch-packages] [Bug 1548480] Re: 95packagekit sleep hook weirdly installed in a subdirectory is ignored

2017-09-25 Thread Julian Andres Klode

Since the hook does not have any effect due to being in the wrong place,
and removing it causes it to not have any effect, doing a stable release
update seems pointless.

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

Title:
  95packagekit sleep hook weirdly installed in a subdirectory is ignored

Status in packagekit package in Ubuntu:
  Fix Released

Bug description:
  The 95packagekit sleep hook provided by packagekit is installed in a 
subdirectory: 
  /usr/lib/pm-utils/sleep.d/95packagekit/95packagekit

  This has two effects:

  1the hook is not run;

  2owing to a bug in pm-utils, separately reported, the previous
  hook is run for a second time instead.

  If #1 was actually the desired effect, the hook should have been
  stored as /usr/lib/pm-utils/sleep.d/95packagekit~ or just omitted.

  If the hook is manually installed as /usr/lib/pm-
  utils/sleep.d/95packagekit, it runs as expected (although the nature
  of the hook's operation means that it may have no obvious effect).

  This issue was observed in 14.04, packagekit 0.8.12-1ubuntu5;
  apparently was OK in 12.04. A packaging bug seems to have appeared
  when 95packagekit was updated in revision 1.2.10.

  Additionally, the hook 95packagekit is incorrectly numbered according
  to the pm-utils HOWTO.hooks convention and should apparently be eg
  45packagekit.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: packagekit 0.8.12-1ubuntu5
  ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Mon Feb 22 19:12:48 2016
  InstallationDate: Installed on 2016-02-21 (0 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  SourcePackage: packagekit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1548480/+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 1704171] Re: WiFi connections unstable

2017-09-25 Thread Lisa Nelson

Afer installing the 4.14-rc2 kernel, it appears this is fixed.  I was able to 
switch between the 3 wifi's here without issue.
Thanks!

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

Title:
  WiFi connections unstable

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have 3 WiFi signals here, and use them all without issue most of the
  time.  Since upgrading to 17.04 I have issues where my wifi will not
  connect to one of the other 2 signals, then also won't re-connect to
  the signal that was just in use.  When this happens, I can do a
  'restart' and it will connect just fine to any of the 3 signals.

  While it was failing a bit ago, I captured the syslog of whats going
  on and will include it below.

  Distributor ID:   Ubuntu
  Description:  Ubuntu 17.04
  Release:  17.04
  Codename: zesty

  Linux lisa-Inspiron-7720 4.10.0-28-generic #32-Ubuntu SMP Fri Jun 30
  05:32:18 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.2717] device (wlp2s0): Activation: starting connection 'LisaN' 
(58396782-9fe4-4ce3-b0e6-f72df56c72d5)
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.2720] audit: op="connection-activate" 
uuid="58396782-9fe4-4ce3-b0e6-f72df56c72d5" name="LisaN" pid=1962 uid=1000 
result="success"
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.2723] device (wlp2s0): state change: disconnected -> prepare 
(reason 'none') [30 40 0]
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.2725] manager: NetworkManager state is now CONNECTING
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.2779] device (wlp2s0): set-hw-addr: set-cloned MAC address to 
C4:D9:87:6E:9B:0F (permanent)
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  312.891148] iwlwifi 
:02:00.0: L1 Enabled - LTR Disabled
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  312.898132] iwlwifi 
:02:00.0: L1 Enabled - LTR Disabled
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  312.898220] iwlwifi 
:02:00.0: Radio type=0x2-0x1-0x0
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  313.183332] iwlwifi 
:02:00.0: L1 Enabled - LTR Disabled
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  313.190314] iwlwifi 
:02:00.0: L1 Enabled - LTR Disabled
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  313.190403] iwlwifi 
:02:00.0: Radio type=0x2-0x1-0x0
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  313.274573] IPv6: 
ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6644] device (wlp2s0): supplicant interface state: inactive -> 
disabled
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6649] device (wlp2s0): state change: prepare -> config (reason 
'none') [40 50 0]
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6654] device (wlp2s0): Activation: (wifi) access point 'LisaN' has 
security, but secrets are required.
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6654] device (wlp2s0): state change: config -> need-auth (reason 
'none') [50 60 0]
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6728] device (wlp2s0): state change: need-auth -> prepare (reason 
'none') [60 40 0]
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6735] device (wlp2s0): state change: prepare -> config (reason 
'none') [40 50 0]
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6738] device (wlp2s0): Activation: (wifi) connection 'LisaN' has 
security, and secrets exist.  No new secrets needed.
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6739] Config: added 'ssid' value 'LisaN'
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6740] Config: added 'scan_ssid' value '1'
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6740] Config: added 'key_mgmt' value 'WPA-PSK'
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6740] Config: added 'psk' value ''
  Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: Can't set a parent on 
widget which has a parent
  Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: Can't set a parent on 
widget which has a parent
  Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: 
assertion 'GTK_IS_WIDGET (widget)' failed

[Touch-packages] [Bug 1719077] Re: Unable to find codecs to play videos

2017-09-25 Thread Bug Watch Updater

** Changed in: grilo-plugins
   Status: Unknown => Confirmed

** Changed in: grilo-plugins
   Importance: Unknown => Medium

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

Title:
  Unable to find codecs to play videos

Status in Grilo Plugins:
  Confirmed
Status in grilo-plugins package in Ubuntu:
  New
Status in packagekit package in Ubuntu:
  Fix Committed

Bug description:
  There are two bugs here:
  1. packagekit was using app-install-data to search for missing codecs
  2. The Guardian Videos channel does not work

  (1) is supposedly fixed in all cases.

  To reproduce:

  1. Open Totem
  2. Go to Channels and select The Guardian Videos
  3. Select any video
  4. Totem complains about missing codecs
  5. GNOME Software then complains that app-install-data is missing

  See screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-software 3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 23 11:54:53 2017
  InstallationDate: Installed on 2017-09-21 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.0-0ubuntu2
  PackageArchitecture: all
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/grilo-plugins/+bug/1719077/+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 1718953] Re: Shift key not working during login

** Tags added: xenial

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

Title:
  Shift key not working during login

Status in lightdm package in Ubuntu:
  New

Bug description:
  Unable to use capital letters for login password using the shift key.
  The caps lock key works, as does the graphical keyboard input.  After
  login, the shift key seems to work.

  I am using Ubuntu 16.04.3 with the HWE kernel 4.10.0-35
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1718953/+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 1719335] [NEW] package libqt5script5:amd64 5.5.1+dfsg-2build1 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intent

2017-09-25 Thread Hector

Public bug reported:

I don't know what's going on with this system error.

package libqt5script5:amd64 5.5.1+dfsg-2build1 failed to
install/upgrade: El paquete está en un estado grave de inconsistencia -
debe reinstalarlo  antes de intentar su configuración.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libqt5script5:amd64 5.5.1+dfsg-2build1
ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Fri Sep 22 09:19:39 2017
ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
InstallationDate: Installed on 2017-05-11 (136 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: qtscript-opensource-src
Title: package libqt5script5:amd64 5.5.1+dfsg-2build1 failed to 
install/upgrade: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qtscript-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package libqt5script5:amd64 5.5.1+dfsg-2build1 failed to
  install/upgrade: El paquete está en un estado grave de inconsistencia
  - debe reinstalarlo  antes de intentar su configuración.

Status in qtscript-opensource-src package in Ubuntu:
  New

Bug description:
  I don't know what's going on with this system error.

  package libqt5script5:amd64 5.5.1+dfsg-2build1 failed to
  install/upgrade: El paquete está en un estado grave de inconsistencia
  - debe reinstalarlo  antes de intentar su configuración.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqt5script5:amd64 5.5.1+dfsg-2build1
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Sep 22 09:19:39 2017
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2017-05-11 (136 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: qtscript-opensource-src
  Title: package libqt5script5:amd64 5.5.1+dfsg-2build1 failed to 
install/upgrade: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtscript-opensource-src/+bug/1719335/+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 1704929] Re: Repeating "can't open /dev/ttyX: No such device or address" messages during installation

2017-09-25 Thread Frank Heimes

** Changed in: ubuntu-z-systems
   Status: New => Confirmed

** Changed in: console-setup (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: console-setup (Ubuntu Artful)
   Status: New => Confirmed

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

Title:
  Repeating "can't open /dev/ttyX: No such device or address" messages
  during installation

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in console-setup package in Ubuntu:
  Confirmed
Status in console-setup source package in Xenial:
  Confirmed
Status in console-setup source package in Zesty:
  New
Status in console-setup source package in Artful:
  Confirmed

Bug description:
  [Impact]

  console-setup continuously tries to open /dev/tty[1-6] on s390x, when
  such consoles do not exist on s390x.

  This can be seen on boot in the output from the initramfs, and during
  the installer.

  [Cuase]

  It seems to me that the postinst of the console-setup is incorrect for
  s390, since on s390 Linux tty[1-6] do not exist in any modes (LPAR,
  z/VM, KVM)

  [Solution]
  I do not know what ACTIVE_CONSOLES should be set as, my guess is to set it 
to... "guess". Usually it should be slcp, but that depends on which consoles 
are configured/activated in the given KVM.

  [Testcase]
  On boot, scroll all the messages and makesure there are no error messages 
about inability to open /dev/tty*

  [Original Bug Report]

  During the installation (z/VM guest and KVM virtual machine) of Ubuntu
  Server 16.04.1 (and 16.04.2) repeating messages of the form:

  "
  Select and install software ... 10% can't open /dev/tty4: No such device or 
address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 20% can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 30%... 40% can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ... 50% can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ... 60% can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ...
  Finishing the installation ... 13%... 22%... 31% can't open /dev/tty3: No 
such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty4: No such device or address
  ... 40%... 50%... 63%... 72%... 81% can't open /dev/tty4: No such device or 
address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 90% The system is going down NOW
   Sent SIGTERM to all processes
   Sent SIGKILL to all processes
   Requesting system reboot
  01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  02: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  03: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  00 Storage cleared - system reset.
  00 zIPL ..
  "

  They start to occur when the software gets installed:

  "Select and install software ... 10% can't open /dev/tty4: No such
  device or address"

  And only stop with the final system reboot at the end of the
  installation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1704929/+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 1719110] Re: gdb gets SIGSEGV before calling main()

2017-09-25 Thread Jim Starkey

apt-get upgrade reported that gdb was up to date.  However, removing and
re-installing gdb with apt-get got it working again.

The gdb packaging?  The upgrade procedure?

I have a copy of the systems with bad gdb instances if anyone would like
to take this on.

But for now, I'm out of the woods...

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

Title:
  gdb gets SIGSEGV before calling main()

Status in gdb package in Ubuntu:
  New

Bug description:
  This about covers it:

  jas@rpi3:~$ cat foo.cpp
  #include 

  int main (int argc, const char **argv)
  {
  printf("hello, world\n");

  return 0;
  }
  jas@rpi3:~$ g++ foo.cpp
  jas@rpi3:~$ gdb a.out
  GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "arm-linux-gnueabihf".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from a.out...(no debugging symbols found)...done.
  (gdb) r
  Starting program: /home/jas/a.out

  Program received signal SIGSEGV, Segmentation fault.
  0x76fd9dde in ?? () from /lib/ld-linux-armhf.so.3
  (gdb)

  
  I can't image how this can be.  It seems to happen on all images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1719110/+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 1548480] Re: 95packagekit sleep hook weirdly installed in a subdirectory is ignored

2017-09-25 Thread Dirk F

Thanks Matthias, Amr.

I reported this against Trusty LTS and the Fix would mean back-porting
or otherwise introducing 0.8.17 over 0.8.12, probably not going to
happen.

So that the unnecessary, wrongly named and wrongly located file might be
removed (though I suppose anyone who cares can actually do so
themselves), a patch is needed against the packaging of PackageKit in
Trusty.

I can't see a way to file a bug against a particular release's packaging
of a package, so I've linked this to the Trusty branches with a
suggested distribution patch for /contrib/pm-utils/Makefile.am that
should omit the redundant file and remove it if present.


** Attachment added: "Suggested change to 
"
   
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1548480/+attachment/4956761/+files/Makefile.am.dif

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

Title:
  95packagekit sleep hook weirdly installed in a subdirectory is ignored

Status in packagekit package in Ubuntu:
  Fix Released

Bug description:
  The 95packagekit sleep hook provided by packagekit is installed in a 
subdirectory: 
  /usr/lib/pm-utils/sleep.d/95packagekit/95packagekit

  This has two effects:

  1the hook is not run;

  2owing to a bug in pm-utils, separately reported, the previous
  hook is run for a second time instead.

  If #1 was actually the desired effect, the hook should have been
  stored as /usr/lib/pm-utils/sleep.d/95packagekit~ or just omitted.

  If the hook is manually installed as /usr/lib/pm-
  utils/sleep.d/95packagekit, it runs as expected (although the nature
  of the hook's operation means that it may have no obvious effect).

  This issue was observed in 14.04, packagekit 0.8.12-1ubuntu5;
  apparently was OK in 12.04. A packaging bug seems to have appeared
  when 95packagekit was updated in revision 1.2.10.

  Additionally, the hook 95packagekit is incorrectly numbered according
  to the pm-utils HOWTO.hooks convention and should apparently be eg
  45packagekit.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: packagekit 0.8.12-1ubuntu5
  ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Mon Feb 22 19:12:48 2016
  InstallationDate: Installed on 2016-02-21 (0 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  SourcePackage: packagekit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1548480/+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 1704929] Re: Repeating "can't open /dev/ttyX: No such device or address" messages during installation

2017-09-25 Thread Andrew McLeod

I'm seeing this installing 17.10 on s390x also.

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

Title:
  Repeating "can't open /dev/ttyX: No such device or address" messages
  during installation

Status in Ubuntu on IBM z Systems:
  New
Status in console-setup package in Ubuntu:
  New
Status in console-setup source package in Xenial:
  New
Status in console-setup source package in Zesty:
  New
Status in console-setup source package in Artful:
  New

Bug description:
  [Impact]

  console-setup continuously tries to open /dev/tty[1-6] on s390x, when
  such consoles do not exist on s390x.

  This can be seen on boot in the output from the initramfs, and during
  the installer.

  [Cuase]

  It seems to me that the postinst of the console-setup is incorrect for
  s390, since on s390 Linux tty[1-6] do not exist in any modes (LPAR,
  z/VM, KVM)

  [Solution]
  I do not know what ACTIVE_CONSOLES should be set as, my guess is to set it 
to... "guess". Usually it should be slcp, but that depends on which consoles 
are configured/activated in the given KVM.

  [Testcase]
  On boot, scroll all the messages and makesure there are no error messages 
about inability to open /dev/tty*

  [Original Bug Report]

  During the installation (z/VM guest and KVM virtual machine) of Ubuntu
  Server 16.04.1 (and 16.04.2) repeating messages of the form:

  "
  Select and install software ... 10% can't open /dev/tty4: No such device or 
address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 20% can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 30%... 40% can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ... 50% can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ... 60% can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ...
  Finishing the installation ... 13%... 22%... 31% can't open /dev/tty3: No 
such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty4: No such device or address
  ... 40%... 50%... 63%... 72%... 81% can't open /dev/tty4: No such device or 
address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 90% The system is going down NOW
   Sent SIGTERM to all processes
   Sent SIGKILL to all processes
   Requesting system reboot
  01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  02: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  03: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  00 Storage cleared - system reset.
  00 zIPL ..
  "

  They start to occur when the software gets installed:

  "Select and install software ... 10% can't open /dev/tty4: No such
  device or address"

  And only stop with the final system reboot at the end of the
  installation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1704929/+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 1620636] Re: Fails to pair with Bose QC35 headphones

2017-09-25 Thread Jim Hodapp

Yes I've experienced the same kind of jitter. The volume level is pretty
decent for me, but not the streaming performance. I basically need to be
doing nothing else on my laptop for it to stream without jittering.

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

Title:
  Fails to pair with Bose QC35 headphones

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  In Progress

Bug description:
  I am unable to pair the Bose QC35 BT headphones with Ubuntu, either
  Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez
  5.41 from installed from yakkety archive), nor using Ubuntu Touch rc-
  proposed build for Turbo #174. I'm trying to pair through the normal
  bluetooth control panel brought up through the bluetooth indicator.

  I've attached some logs that show it failing to pair. If I can provide
  anymore useful information about the headphones, please let me know.

  Syslog with bluetoothd debugging enabled:
  http://pastebin.ubuntu.com/23141394/

  btmon output:
  http://pastebin.ubuntu.com/23141446/

  bluetoothctl output:
  http://pastebin.ubuntu.com/23141510/

  With Linux kernel 4.8.0 and bluez 4.52:
  ---

  bluetoothctl: http://pastebin.ubuntu.com/23256457/
  btmon: http://pastebin.ubuntu.com/23256471/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620636/+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 1719313] [NEW] ubuntu crashes while accessing any multimedia

2017-09-25 Thread Aravind R

Public bug reported:

ubuntu crashes while accessing any multimedia. When it crashes I have
black color horizontal bars of 1 inch thick. I have a craking noise.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.69  Wed Aug 16 19:34:54 
PDT 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Sep 25 18:57:43 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GconfCompiz:
 /apps/compiz-1/general:
   /apps/compiz-1/general/screen0:
/apps/compiz-1/general/screen0/options:
 active_plugins = 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
GraphicsCard:
 Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:1094]
   Subsystem: Acer Incorporated [ALI] Device [1025:1094]
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0408:a030 Quanta Computer, Inc. 
 Bus 001 Device 002: ID 04ca:3015 Lite-On Technology Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire E5-575G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=3bdb5792-d2a2-4f98-97bd-f274c3d0dde1 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/03/2017
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.25
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Ironman_SK
dmi.board.vendor: Acer
dmi.board.version: V1.25
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.25:bd03/03/2017:svnAcer:pnAspireE5-575G:pvrV1.25:rvnAcer:rnIronman_SK:rvrV1.25:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire E5-575G
dmi.product.version: V1.25
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83+git1708241830.f19dbb~gd~x
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.3~git1708280730.242212~gd~x
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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: Mon Sep 25 18:34:06 2017
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1~16.04.2

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


** Tags: amd64 apport-bug compiz-0.9 possible-manual-nvidia-install 
third-party-packages 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/1719313

Title:
  ubuntu crashes while accessing any multimedia

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu crashes while accessing any multimedia. When it crashes I have
  black color horizontal bars of 1 inch thick. I have a craking noise.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.69  Wed Aug 16 19:34:54

[Touch-packages] [Bug 1717241] Re: nautilus crashed with signal 5 in _XReply() - drag and drop crash

2017-09-25 Thread Rodrigo Alconchel

** No longer affects: xorg (Ubuntu)

** No longer affects: nvidia-graphics-drivers (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/1717241

Title:
  nautilus crashed with signal 5 in _XReply() - drag and drop crash

Status in nautilus package in Ubuntu:
  New

Bug description:
  To reproduce on a fully updated Ubuntu Desktop 16.04 system with
  Unity:

  Step 1: Start nautilus

  Step 2: Drag and drop a file to any target: to a different folder in
  the same nautilus window, to another folder in a different nautilus
  window, etc. ... The target is irrelevant.

  Expected to happen: File successfully copied or moved.

  Actually happened: Mouse pointer changes to a hand with a plus sign.
  Source file moves only slightly and then freezes, never makes it to
  the target. Application locks up for a few seconds, and then the
  application window vanishes. Crash report is then generated.

  Ubuntu release: Ubuntu 16.04.3 LTS

  Nautilus package version: Installed: 1:3.18.4.is.3.14.3-0ubuntu6

  Additional (and maybe relevant) notes:

  1) Drag and drop function seems broken generally, across applications,
  not just in nautilus. For instance, same behavior appears when trying
  to drag and drop a Thunderbird message to another Thunderbird folder,
  or when trying to drag and drop a cell or a range of cells within the
  same Libreoffice Calc spreadsheet.

  2) Interestingly, application windows can be dragged and dropped
  across display monitors (3 monitor setup), without any problems.

  3) I am using proprietary NVIDIA drivers, but please do not suggest
  using nouveau drivers, because they work horribly (heavy display
  corruption, pixelated screen, and constant mouse flickering)

  4) Graphics setup: NVIDIA Quadro NVS 450 card with twin GPU and 4
  heads. NVIDIA proprietary driver version 340.102 (installed from
  ubuntu repositories, not from proprietary NVIDIA installer; this is
  the correct driver version for this card according to NVIDIA
  documentation). 3 monitors connected in a simple horizontal layout.

  5) Nautilus extension installed: nautilus-share  0.7.3-2ubuntu1

  6) Attaching a nautilus debugging log from terminal command:
  G_DEBUG="all" NAUTILUS_DEBUG ="All" nautilus

  7) Attaching X Org log file with -logverbose 6 option

  8) Attaching xorg.conf configuration file

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.10
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CrashReports: 640:1000:116:10641522:2017-09-14 12:49:07.088649823 
+0200:2017-09-14 12:27:03.381461842 
+0200:/var/crash/_usr_bin_nautilus.1000.crash
  CurrentDesktop: Unity
  Date: Thu Sep 14 11:02:40 2017
  ExecutablePath: /usr/bin/nautilus
  ExecutableTimestamp: 1481715745
  PackageArchitecture: all
  ProcCmdline: nautilus
  ProcCwd: /var/crash
  Signal: 5
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XShapeGetRectangles () from /usr/lib/x86_64-linux-gnu/libXext.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: nautilus crashed with signal 5 in _XReply()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2017-09-14T09:20:26.397971

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1717241/+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 1719302] Re: Please include mlx4 and mlx5 InfiniBand modules

2017-09-25 Thread Bug Watch Updater

** Changed in: initramfs-tools (Debian)
   Status: Unknown => New

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

Title:
  Please include mlx4 and mlx5 InfiniBand modules

Status in initramfs-tools package in Ubuntu:
  New
Status in initramfs-tools package in Debian:
  New

Bug description:
  Mellanox ConnectX architecture is:  mlx4_core is the lower level PCI
  driver which register on the PCI id, and protocol specific drivers are
  depended on it: mlx4_en - for Ethernet and mlx4_ib for Infiniband. NIC
  could have multiple ports which can change their type dynamically. We
  use the request_module() call to load the relevant protocol driver
  when needed: on loading time or at port type change event.

  The mlx4_core and mlx5_core modules are included in the initrd, but
  not mlx4_ib and mlx5_ib. Thus the request_module() call will not find
  these modules and fail load them. The mlx*_ib module loading will not
  be retried.

  Therefore also include mlx4_ib and mlx5_ib in the initrd to make
  autoloading them work. A patch is attached to the related Debian bug
  report.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1719302/+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 1719305] [NEW] booting

2017-09-25 Thread Muhammad

Public bug reported:

cant boot usb port

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-36.40-generic 4.10.17
Uname: Linux 4.10.0-36-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.5
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: Mon Sep 25 18:51:40 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:220f]
InstallationDate: Installed on 2017-09-22 (2 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
MachineType: Hewlett-Packard HP 14 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-36-generic 
root=UUID=64974ddb-c087-4ce2-9dd6-50ba20ed9531 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/28/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.32
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 220F
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 57.47
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd10/28/2014:svnHewlett-Packard:pnHP14NotebookPC:pvr098F120600087:rvnHewlett-Packard:rn220F:rvr57.47:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP 14 Notebook PC
dmi.product.version: 098F120600087
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
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 N/A
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: Mon Sep 25 18:47:17 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: apport-bug compiz-0.9 i386 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/1719305

Title:
  booting

Status in xorg package in Ubuntu:
  New

Bug description:
  cant boot usb port

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-36.40-generic 4.10.17
  Uname: Linux 4.10.0-36-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.5
  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: Mon Sep 25 18:51:40 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:220f]
  InstallationDate: Installed on 2017-09-22 (2 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  MachineType: Hewlett-Packard HP 14 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-36-generic 
root=UUID=64974ddb-c087-4ce2-9dd6-50ba20ed9531 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/28/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.32
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 220F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.47
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias:

[Touch-packages] [Bug 1718419] Re: Please merge unattended-upgrades 0.97 (main) from Debian unstable (main)

This bug was fixed in the package unattended-upgrades - 0.97ubuntu1

---
unattended-upgrades (0.97ubuntu1) artful; urgency=medium

  * Merge from Debian unstable (LP: #1718419)
- Remaining changes:
  - unattended-upgrades: Do not automatically upgrade the development
release of Ubuntu unless Unattended-Upgrade::DevRelease is true.
- Dropped changes, included in Debian:
  - Recover from broken dh_installinit override in versions < 0.93.1ubuntu3

unattended-upgrades (0.97) unstable; urgency=medium

  * Handle recovering from broken dh_installinit override on Ubuntu, too
  * Declare needs-reboot for autopkgtests
  * Clean up more test artifacts
  * Run u-u-s only when running on AC power
  * Catch SystemError from fetcher.run(), too
  * Default to MinimalSteps=True in most tests to excercise default setting
  * Check only changed packages in check_changes_for_sanity()
  * Store candidate versions to adjust in UnattendedUpgradesCache()'s 
constructor

 -- Balint Reczey   Wed, 20 Sep 2017 14:46:47 +0200

** Changed in: unattended-upgrades (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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1718419

Title:
   Please merge unattended-upgrades 0.97 (main) from Debian unstable
  (main)

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  The update fixes issues which surfaced when u-u switched installing
  updates in minimal steps, most notably the minimal-steps method being
  very slow

  0.97 speeds up u-u by ~90% which brings current worst-case (xenial
  with no security fixes -> fully updated) run-time down to tolerable
  levels.

  Changes:
   unattended-upgrades (0.97) unstable; urgency=medium
   .
     * Handle recovering from broken dh_installinit override on Ubuntu, too
     * Declare needs-reboot for autopkgtests
     * Clean up more test artifacts
     * Run u-u-s only when running on AC power
     * Catch SystemError from fetcher.run(), too
     * Default to MinimalSteps=True in most tests to excercise default setting
     * Check only changed packages in check_changes_for_sanity()
     * Store candidate versions to adjust in UnattendedUpgradesCache()'s 
constructor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1718419/+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 1719302] [NEW] Please include mlx4 and mlx5 InfiniBand modules

2017-09-25 Thread Benjamin Drung

Public bug reported:

Mellanox ConnectX architecture is:  mlx4_core is the lower level PCI
driver which register on the PCI id, and protocol specific drivers are
depended on it: mlx4_en - for Ethernet and mlx4_ib for Infiniband. NIC
could have multiple ports which can change their type dynamically. We
use the request_module() call to load the relevant protocol driver when
needed: on loading time or at port type change event.

The mlx4_core and mlx5_core modules are included in the initrd, but not
mlx4_ib and mlx5_ib. Thus the request_module() call will not find these
modules and fail load them. The mlx*_ib module loading will not be
retried.

Therefore also include mlx4_ib and mlx5_ib in the initrd to make
autoloading them work. A patch is attached to the related Debian bug
report.

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

** Affects: initramfs-tools (Debian)
 Importance: Unknown
 Status: Unknown

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

** Also affects: initramfs-tools (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871595
   Importance: Unknown
   Status: Unknown

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

Title:
  Please include mlx4 and mlx5 InfiniBand modules

Status in initramfs-tools package in Ubuntu:
  New
Status in initramfs-tools package in Debian:
  Unknown

Bug description:
  Mellanox ConnectX architecture is:  mlx4_core is the lower level PCI
  driver which register on the PCI id, and protocol specific drivers are
  depended on it: mlx4_en - for Ethernet and mlx4_ib for Infiniband. NIC
  could have multiple ports which can change their type dynamically. We
  use the request_module() call to load the relevant protocol driver
  when needed: on loading time or at port type change event.

  The mlx4_core and mlx5_core modules are included in the initrd, but
  not mlx4_ib and mlx5_ib. Thus the request_module() call will not find
  these modules and fail load them. The mlx*_ib module loading will not
  be retried.

  Therefore also include mlx4_ib and mlx5_ib in the initrd to make
  autoloading them work. A patch is attached to the related Debian bug
  report.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1719302/+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 1719110] Re: gdb gets SIGSEGV before calling main()

2017-09-25 Thread Etienne Papegnies

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

** No longer affects: ubuntu-mate

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

Title:
  gdb gets SIGSEGV before calling main()

Status in gdb package in Ubuntu:
  New

Bug description:
  This about covers it:

  jas@rpi3:~$ cat foo.cpp
  #include 

  int main (int argc, const char **argv)
  {
  printf("hello, world\n");

  return 0;
  }
  jas@rpi3:~$ g++ foo.cpp
  jas@rpi3:~$ gdb a.out
  GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "arm-linux-gnueabihf".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from a.out...(no debugging symbols found)...done.
  (gdb) r
  Starting program: /home/jas/a.out

  Program received signal SIGSEGV, Segmentation fault.
  0x76fd9dde in ?? () from /lib/ld-linux-armhf.so.3
  (gdb)

  
  I can't image how this can be.  It seems to happen on all images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1719110/+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 1718419] Re: Please merge unattended-upgrades 0.97 (main) from Debian unstable (main)

2017-09-25 Thread LocutusOfBorg

ack for me

** Changed in: unattended-upgrades (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
   Please merge unattended-upgrades 0.97 (main) from Debian unstable
  (main)

Status in unattended-upgrades package in Ubuntu:
  Fix Committed

Bug description:
  The update fixes issues which surfaced when u-u switched installing
  updates in minimal steps, most notably the minimal-steps method being
  very slow

  0.97 speeds up u-u by ~90% which brings current worst-case (xenial
  with no security fixes -> fully updated) run-time down to tolerable
  levels.

  Changes:
   unattended-upgrades (0.97) unstable; urgency=medium
   .
     * Handle recovering from broken dh_installinit override on Ubuntu, too
     * Declare needs-reboot for autopkgtests
     * Clean up more test artifacts
     * Run u-u-s only when running on AC power
     * Catch SystemError from fetcher.run(), too
     * Default to MinimalSteps=True in most tests to excercise default setting
     * Check only changed packages in check_changes_for_sanity()
     * Store candidate versions to adjust in UnattendedUpgradesCache()'s 
constructor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1718419/+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 1719283] Re: Unable to upgrade bluez to 5.37-0ubuntu5.1 - insserv: Service dbus has to be enabled to start service bluetooth

2017-09-25 Thread Norbert

The problem caused by this line:

$ grep update-rc -r /var/lib/dpkg/info/bluez*
/var/lib/dpkg/info/bluez.postinst:  update-rc.d bluetooth defaults 
>/dev/null
/var/lib/dpkg/info/bluez.postrm:update-rc.d bluetooth remove >/dev/null

If I manually run

$ sudo update-rc.d bluetooth defaults

I get

insserv: Service dbus has to be enabled to start service bluetooth
insserv: exiting now!
update-rc.d: error: insserv rejected the script header

Then I tried
$ sudo update-rc.d dbus defaults

And

$ sudo update-rc.d bluetooth defaults

and after

$ sudo apt-get install -f
$ sudo dpkg --audit

And problem is solved! It was misconfiguration issue, I think.

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

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

Title:
  Unable to upgrade bluez to 5.37-0ubuntu5.1 - insserv: Service dbus has
  to be enabled to start service bluetooth

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Use Ubuntu 16.04 LTS.
  2. Do apt-get upgrade
  3. Get error

  norbert@norbert-vaio:~$ sudo dpkg --configure -a
  Setting up bluez (5.37-0ubuntu5.1) ...
  insserv: Service dbus has to be enabled to start service bluetooth
  insserv: exiting now!
  update-rc.d: error: insserv rejected the script header
  dpkg: error processing package bluez (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   bluez

  Expected results:
  * Bluetooth is working after apt-get upgrade. User is able to install other 
packages.

  Actual results:
  * Bluetooth is not working after apt-get upgrade. User is unable to install 
other packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5.1
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Sep 25 12:51:44 2017
  InstallationDate: Installed on 2010-12-05 (2485 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Sony Corporation VPCF13Z1R
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic 
root=UUID=875ba4a2-2d66-45c8-b276-9004a4f2be04 ro init=/sbin/init -v noplymouth 
resume=UUID=347e9507-87b1-431d-b36f-538d190a517f
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2017-06-24 (92 days ago)
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0190Y9
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0190Y9:bd10/20/2010:svnSonyCorporation:pnVPCF13Z1R:pvrC607OEHZ:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCF13Z1R
  dmi.product.version: C607OEHZ
  dmi.sys.vendor: Sony Corporation
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: C0:CB:38:FA:A7:D5  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:541 acl:0 sco:0 events:28 errors:0
TX bytes:848 acl:0 sco:0 commands:28 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1719283/+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 1719287] [NEW] libnss-resolve causes gnome-shell to hang when there's a high rate of getaddrinfo() calls

2017-09-25 Thread Chow Loong Jin

Public bug reported:

I've been running a locust[1]-based web load test on my Ubuntu machine
running GNOME Shell (wayland). When starting a new test with a client
spawn rate of ~500/s, it issues a huge amount of getaddrinfo() calls.
When using libnss-resolve, this causes a huge number of NameOwnerChanged
events on the system bus:


signal time=1506335482.865950 sender=org.freedesktop.DBus -> destination=(null 
destination) serial=227290 path=/org/freedesktop/DBus; 
interface=org.freedesktop.DBus; member=NameOwnerChanged
   string ":1.190697"
   string ""
   string ":1.190697"
signal time=1506335482.868601 sender=org.freedesktop.DBus -> destination=(null 
destination) serial=227291 path=/org/freedesktop/DBus; 
interface=org.freedesktop.DBus; member=NameOwnerChanged
   string ":1.190697"
   string ":1.190697"
   string ""
signal time=1506335483.305614 sender=org.freedesktop.DBus -> destination=(null 
destination) serial=227292 path=/org/freedesktop/DBus; 
interface=org.freedesktop.DBus; member=NameOwnerChanged
   string ":1.190698"
   string ""
   string ":1.190698"
signal time=1506335483.310873 sender=org.freedesktop.DBus -> destination=(null 
destination) serial=227293 path=/org/freedesktop/DBus; 
interface=org.freedesktop.DBus; member=NameOwnerChanged
   string ":1.190698"
   string ":1.190698"
   string ""

This in turn causes gnome-shell to spend a huge amount of CPU churning
through these events, and if sufficiently starved of CPU (those load
testing scripts also consume quite a bit) when interacting with Google
Chome, it goes into key repeat runaway (similar to [2]).

I'm not completely certain, but there were quite a number of other
processes affected by this, and all of them start fighting over CPU time
to handle these NameOnwerChanged events.

As a workaround, disabling libnss-resolve in /etc/nsswitch.conf and just
using the stub resolver fixes things.


[1] https://locust.io
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1459692

** 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/1719287

Title:
  libnss-resolve causes gnome-shell to hang when there's a high rate of
  getaddrinfo() calls

Status in systemd package in Ubuntu:
  New

Bug description:
  I've been running a locust[1]-based web load test on my Ubuntu machine
  running GNOME Shell (wayland). When starting a new test with a client
  spawn rate of ~500/s, it issues a huge amount of getaddrinfo() calls.
  When using libnss-resolve, this causes a huge number of
  NameOwnerChanged events on the system bus:

  
  signal time=1506335482.865950 sender=org.freedesktop.DBus -> 
destination=(null destination) serial=227290 path=/org/freedesktop/DBus; 
interface=org.freedesktop.DBus; member=NameOwnerChanged
 string ":1.190697"
 string ""
 string ":1.190697"
  signal time=1506335482.868601 sender=org.freedesktop.DBus -> 
destination=(null destination) serial=227291 path=/org/freedesktop/DBus; 
interface=org.freedesktop.DBus; member=NameOwnerChanged
 string ":1.190697"
 string ":1.190697"
 string ""
  signal time=1506335483.305614 sender=org.freedesktop.DBus -> 
destination=(null destination) serial=227292 path=/org/freedesktop/DBus; 
interface=org.freedesktop.DBus; member=NameOwnerChanged
 string ":1.190698"
 string ""
 string ":1.190698"
  signal time=1506335483.310873 sender=org.freedesktop.DBus -> 
destination=(null destination) serial=227293 path=/org/freedesktop/DBus; 
interface=org.freedesktop.DBus; member=NameOwnerChanged
 string ":1.190698"
 string ":1.190698"
 string ""

  This in turn causes gnome-shell to spend a huge amount of CPU churning
  through these events, and if sufficiently starved of CPU (those load
  testing scripts also consume quite a bit) when interacting with Google
  Chome, it goes into key repeat runaway (similar to [2]).

  I'm not completely certain, but there were quite a number of other
  processes affected by this, and all of them start fighting over CPU
  time to handle these NameOnwerChanged events.

  As a workaround, disabling libnss-resolve in /etc/nsswitch.conf and
  just using the stub resolver fixes things.

  
  [1] https://locust.io
  [2] https://bugzilla.redhat.com/show_bug.cgi?id=1459692

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1719287/+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 1719283] [NEW] Unable to upgrade bluez to 5.37-0ubuntu5.1 - insserv: Service dbus has to be enabled to start service bluetooth

2017-09-25 Thread Norbert

Public bug reported:

Steps to reproduce:
1. Use Ubuntu 16.04 LTS.
2. Do apt-get upgrade
3. Get error

norbert@norbert-vaio:~$ sudo dpkg --configure -a
Setting up bluez (5.37-0ubuntu5.1) ...
insserv: Service dbus has to be enabled to start service bluetooth
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg: error processing package bluez (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 bluez

Expected results:
* Bluetooth is working after apt-get upgrade. User is able to install other 
packages.

Actual results:
* Bluetooth is not working after apt-get upgrade. User is unable to install 
other packages.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: bluez 5.37-0ubuntu5.1
ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
Uname: Linux 4.4.0-96-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: MATE
Date: Mon Sep 25 12:51:44 2017
InstallationDate: Installed on 2010-12-05 (2485 days ago)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Sony Corporation VPCF13Z1R
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic 
root=UUID=875ba4a2-2d66-45c8-b276-9004a4f2be04 ro init=/sbin/init -v noplymouth 
resume=UUID=347e9507-87b1-431d-b36f-538d190a517f
SourcePackage: bluez
UpgradeStatus: Upgraded to xenial on 2017-06-24 (92 days ago)
dmi.bios.date: 10/20/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R0190Y9
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0190Y9:bd10/20/2010:svnSonyCorporation:pnVPCF13Z1R:pvrC607OEHZ:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VPCF13Z1R
dmi.product.version: C607OEHZ
dmi.sys.vendor: Sony Corporation
hciconfig:
 hci0:  Type: BR/EDR  Bus: USB
BD Address: C0:CB:38:FA:A7:D5  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:541 acl:0 sco:0 events:28 errors:0
TX bytes:848 acl:0 sco:0 commands:28 errors:0

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


** Tags: apport-bug xenial

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

Title:
  Unable to upgrade bluez to 5.37-0ubuntu5.1 - insserv: Service dbus has
  to be enabled to start service bluetooth

Status in bluez package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Use Ubuntu 16.04 LTS.
  2. Do apt-get upgrade
  3. Get error

  norbert@norbert-vaio:~$ sudo dpkg --configure -a
  Setting up bluez (5.37-0ubuntu5.1) ...
  insserv: Service dbus has to be enabled to start service bluetooth
  insserv: exiting now!
  update-rc.d: error: insserv rejected the script header
  dpkg: error processing package bluez (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   bluez

  Expected results:
  * Bluetooth is working after apt-get upgrade. User is able to install other 
packages.

  Actual results:
  * Bluetooth is not working after apt-get upgrade. User is unable to install 
other packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5.1
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Sep 25 12:51:44 2017
  InstallationDate: Installed on 2010-12-05 (2485 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Sony Corporation VPCF13Z1R
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic 
root=UUID=875ba4a2-2d66-45c8-b276-9004a4f2be04 ro init=/sbin/init -v noplymouth 
resume=UUID=347e9507-87b1-431d-b36f-538d190a517f
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2017-06-24 (92 days ago)
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0190Y9
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0190Y9:bd10/20/2010:svnSonyCorporation:pnVPCF13Z1R:pvrC607OEHZ:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCF13Z1R
  dmi.product.version: C607OEHZ
  dmi.sys.vendor: Sony

[Touch-packages] [Bug 1712283] Re: Cannot resolve DNS in artful daily

2017-09-25 Thread Wouter van der Graaf

Today, I also ran into this issue. Wifi was working and I could
successfully ping Google's DNS 8.8.8.8.

However, pinging google.com didn't work: "Name or service not known"

The workaround in comment #6 does the trick for me:

sudo rm /etc/resolv.conf
sudo ln -s /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf

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

Title:
  Cannot resolve DNS in artful daily

Status in casper package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in netcfg package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

  

  
  * /etc/resolv.conf is empty file on most images built, which is not right, it 
should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in 
image generation? systemd?

  * Adding a hack, to create /etc/resolv.conf if it does not exist, or
  is empty. src:systemd

  * network-manager does not consider that dns is managed by resolved if
  .53 is present in /etc/resolv.conf or if it points to stub-
  resolv.conf. src:network-manager

  * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf.
  Needs checking / fixing

  * caster has resolvconf integration

  * livecd-rootfs has resolvconf integration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+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 1712283] Re: Cannot resolve DNS in artful daily

2017-09-25 Thread Wouter van der Graaf

Forgot to mention, I have a fresh install from the daily artful image on
21st of September 2017.

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

Title:
  Cannot resolve DNS in artful daily

Status in casper package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in netcfg package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

  

  
  * /etc/resolv.conf is empty file on most images built, which is not right, it 
should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in 
image generation? systemd?

  * Adding a hack, to create /etc/resolv.conf if it does not exist, or
  is empty. src:systemd

  * network-manager does not consider that dns is managed by resolved if
  .53 is present in /etc/resolv.conf or if it points to stub-
  resolv.conf. src:network-manager

  * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf.
  Needs checking / fixing

  * caster has resolvconf integration

  * livecd-rootfs has resolvconf integration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+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 1718595] Re: shotwell crashed with SIGSEGV