[Touch-packages] [Bug 1738581] Re: apport attachment JournalErrors should only be included for crash reports which are private

[Ricardo Dias Marques]

** Summary changed:

- apport attachment JounralErrors should only be included for crash reports 
which are private
+ apport attachment JournalErrors should only be included for crash reports 
which are private

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

Title:
  apport attachment JournalErrors should only be included for crash
  reports which are private

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Artful:
  Fix Released

Bug description:
  [Impact]
  apport includes an attachment called JournalErrors which includes warnings 
and errors in journalctl output. This can in rare circumstances include private 
information.

  [Test Case]
  1) Run ubuntu-bug apport
  2) Observe JournalErrors attachment in the .crash file

  With the version of apport from -proposed JournalErrors will only be
  included in crash reports not regular bug reports. So follow the same
  test case and ensure JournalErrors is not included then run:

  1) d-feet
  2) pkill -11 d-feet
  3) Observe JournalErrors in the d-feet .crash file

  [Regression Potential]
  Its possible my code is bad and then apport would crash when collecting 
journal errors. However, apport will just carry on and not include that 
attachment which would still be an improvement as there wouldn't be any private 
information included.

  See the bug report 
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1738564
  created with ubuntu-bug.

  Original Description
  

  Apport includes the file JournalErrors.txt
  This file includes e.g. the following line.
  Dez 16 19:11:31 hostname /usr/lib/gdm3/gdm-x-session[9679]: 
dbus-update-activation-environment: setting 
MPD_HOST=...@.xxx.org

  Normally it would be not problem that gdm-x-session write this to the
  journal, because the journal is not intended to be published on the
  internet.

  Setting confidential informations via environment is maybe not the
  best idea, but a legal procedure and for `mpc` the only way to set
  this information.

  IMHO the apport utility is here the problem, because it includes the
  file with risky information to a public visible bug report.

  Note: I manually delete the attachment in the mentioned bug report.
  But how can I sure that a web crawlser hasn't read/preserved that
  attachment?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1738581/+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 2041728] [NEW] package initramfs-tools 0.140ubuntu13.4 failed to install/upgrade: o subprocesso instalado, do pacote initramfs-tools, o script post-installation retornou erro do

[Ricardo EAA]

Public bug reported:

from the system itself
???

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: initramfs-tools 0.140ubuntu13.4
ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
Date: Sat Oct 28 14:18:03 2023
ErrorMessage: o subprocesso instalado, do pacote initramfs-tools, o script 
post-installation retornou erro do status de saída 1
InstallationDate: Installed on 2023-07-03 (116 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
PackageArchitecture: all
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.2
 apt  2.4.10
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.140ubuntu13.4 failed to install/upgrade: o 
subprocesso instalado, do pacote initramfs-tools, o script post-installation 
retornou erro do status de saída 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package jammy

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

Title:
  package initramfs-tools 0.140ubuntu13.4 failed to install/upgrade: o
  subprocesso instalado, do pacote initramfs-tools, o script post-
  installation retornou erro do status de saída 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  from the system itself
  ???

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: initramfs-tools 0.140ubuntu13.4
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat Oct 28 14:18:03 2023
  ErrorMessage: o subprocesso instalado, do pacote initramfs-tools, o script 
post-installation retornou erro do status de saída 1
  InstallationDate: Installed on 2023-07-03 (116 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.10
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.140ubuntu13.4 failed to install/upgrade: o 
subprocesso instalado, do pacote initramfs-tools, o script post-installation 
retornou erro do status de saída 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2041728/+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 1958267] Re: wpa can't connect to servers using TLS 1.1 or older

[Ricardo Pardini]

Somewhat related, using a NetworkManager Wifi Hotspot, latest Apple
devices refuse to connect unless I downgrade to Impish version of
wpa_supplicant and libssl1.1.

Other workarounds detailed here do not solve it.

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

Title:
  wpa can't connect to servers using TLS 1.1 or older

Status in wpa package in Ubuntu:
  Triaged
Status in wpa source package in Jammy:
  Confirmed
Status in wpa package in Debian:
  New

Bug description:
  wpa built with in openssl3 fails to connect to TLS 1.1 or lower server

  those uses MD5-SHA1 as digest in its signature algorithm which no
  longer meets OpenSSL default level of security of 80 bits

  http://lists.infradead.org/pipermail/hostap/2022-May/040563.html

  Workaround are described in #22 and #36 by basically using 
  CipherString = DEFAULT@SECLEVEL=0

  which lowers the security level

  ---

  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1969982] [NEW] Bluetooth sound card not detected - Bluetooth software blocked

[RICARDO DA SILVA LISBOA]

Public bug reported:

When I upgraded from ubuntu 21.10 to 22.04 the bluetooth stopped
working. I did a fresh install from scratch and bluetooth no longer
works.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ricardo3058 F pulseaudio
 /dev/snd/pcmC0D0p:   ricardo3058 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 22 15:37:34 2022
InstallationDate: Installed on 2022-04-22 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: Bluetooth sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/11/2017
dmi.bios.release: 1.11
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.11
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: T-Rex_SK
dmi.board.vendor: Acer
dmi.board.version: V1.11
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.11
dmi.ec.firmware.release: 1.8
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd08/11/2017:br1.11:efr1.8:svnAcer:pnAspireES1-572:pvrV1.11:rvnAcer:rnT-Rex_SK:rvrV1.11:cvnAcer:ct10:cvrV1.11:skuAspireES1-572_1085_V1.11:
dmi.product.family: SKL
dmi.product.name: Aspire ES1-572
dmi.product.sku: Aspire ES1-572_1085_V1.11
dmi.product.version: V1.11
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  Bluetooth sound card not detected - Bluetooth software blocked

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When I upgraded from ubuntu 21.10 to 22.04 the bluetooth stopped
  working. I did a fresh install from scratch and bluetooth no longer
  works.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ricardo3058 F pulseaudio
   /dev/snd/pcmC0D0p:   ricardo3058 F...m pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 22 15:37:34 2022
  InstallationDate: Installed on 2022-04-22 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2017
  dmi.bios.release: 1.11
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: T-Rex_SK
  dmi.board.vendor: Acer
  dmi.board.version: V1.11
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.11
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd08/11/2017:br1.11:efr1.8:svnAcer:pnAspireES1-572:pvrV1.11:rvnAcer:rnT-Rex_SK:rvrV1.11:cvnAcer:ct10:cvrV1.11:skuAspireES1-572_1085_V1.11:
  dmi.product.family: SKL
  dmi.product.name: Aspire ES1-572
  dmi.product.sku: Aspire ES1-572_1085_V1.11
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1969982/+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 1922414] Re: ssh-agent fails to start (has_option: command not found)

[Ricardo Garicano Arenas]

Same problem here,
after upgrade ubuntu studio 20.04 to 21.04 & change default plasma desktop to 
xfce:

/etc/X11/Xsession.d/30x11-common_xresources: línea 16: has_option: orden no 
encontrada
/etc/X11/Xsession.d/75dbus_dbus-launch: línea 9: has_option: orden no encontrada

Achim solution
(https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1922414/comments/7
) solve this errors.

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

Title:
  ssh-agent fails to start (has_option: command not found)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have been using ssh-agent for years and since I upgraded my system
  to Ubuntu 21.04/groovy, ssh-agent fails to start.

  Here is the error message:

  # journalctl | grep ssh-agent
  [...]
  Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: 
/etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not 
found

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: x11-common 1:7.7+22ubuntu1
  Uname: Linux 5.11.11-05-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Apr  3 09:02:46 2021
  Dependencies: lsb-base 11.1.0ubuntu2
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed
   tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed
   tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1]
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2020
  dmi.bios.release: 7.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.03RTR
  dmi.board.name: NS50MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO
  version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1922414/+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 1922414] Re: ssh-agent fails to start (has_option: command not found)

[Ricardo Garicano Arenas]

Same problem here,
after upgrade ubuntu studio 20.04 to 21.04 & change default plasma desktop to 
xfce:

/etc/X11/Xsession.d/30x11-common_xresources: línea 16: has_option: orden no 
encontrada
/etc/X11/Xsession.d/75dbus_dbus-launch: línea 9: has_option: orden no encontrada

Achim solution
(https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1922414/comments/7
) solve this errors.

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

Title:
  ssh-agent fails to start (has_option: command not found)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have been using ssh-agent for years and since I upgraded my system
  to Ubuntu 21.04/groovy, ssh-agent fails to start.

  Here is the error message:

  # journalctl | grep ssh-agent
  [...]
  Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: 
/etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not 
found

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: x11-common 1:7.7+22ubuntu1
  Uname: Linux 5.11.11-05-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Apr  3 09:02:46 2021
  Dependencies: lsb-base 11.1.0ubuntu2
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed
   tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed
   tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1]
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2020
  dmi.bios.release: 7.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.03RTR
  dmi.board.name: NS50MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO
  version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1922414/+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 1922414] Re: ssh-agent fails to start (has_option: command not found)

[Ricardo Garicano Arenas]

Same problem here,
after upgrade ubuntu studio 20.04 to 21.04 & change default plasma desktop to 
xfce:

/etc/X11/Xsession.d/30x11-common_xresources: línea 16: has_option: orden no 
encontrada
/etc/X11/Xsession.d/75dbus_dbus-launch: línea 9: has_option: orden no encontrada

Achim solution
(https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1922414/comments/7
) solve this errors.

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

Title:
  ssh-agent fails to start (has_option: command not found)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have been using ssh-agent for years and since I upgraded my system
  to Ubuntu 21.04/groovy, ssh-agent fails to start.

  Here is the error message:

  # journalctl | grep ssh-agent
  [...]
  Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: 
/etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not 
found

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: x11-common 1:7.7+22ubuntu1
  Uname: Linux 5.11.11-05-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Apr  3 09:02:46 2021
  Dependencies: lsb-base 11.1.0ubuntu2
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed
   tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed
   tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1]
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2020
  dmi.bios.release: 7.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.03RTR
  dmi.board.name: NS50MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO
  version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1922414/+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 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

[RICARDO ALEXIS RESTREPO RENGIFO]

Hello I am richard618921. I need to solve the error message debconf:
DbDriver "config": /var/cache/debconf/config.dat is locked by another
process: Resource temporarily unavailable. What can I do ???

** Changed in: aptdaemon
 Assignee: (unassigned) => RICARDO ALEXIS RESTREPO RENGIFO (richard618921)

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

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Aptdaemon:
  Fix Released
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Invalid
Status in debconf package in Ubuntu:
  Fix Released

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptdaemon/+bug/349469/+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 1899310] Re: the bluetooth headphone, although connected, the sound comes out of the notebook speakers

[RICARDO DA SILVA LISBOA]

Thank you for the feedback!  I solved reinstalling the system. As I use 
a separated home partition, everything went back fast and perfect.

Ric

Em 11/10/2020 01:02, Hui Wang escreveu:
> According to the log in the #1, the bluetooth sound card is not in the
> pulseaudio.
>
> Default Sink: alsa_output.pci-_00_1f.3.analog-stereo
>

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

Title:
  the bluetooth headphone, although connected, the sound comes out of
  the notebook speakers

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  the bluetooth headphone, although connected, the sound comes out of
  the notebook speakers. I can only use wired headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-21.22-generic 5.8.13
  Uname: Linux 5.8.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ricardo1300 F pulseaudio
   /dev/snd/pcmC0D0p:   ricardo1300 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 10 23:23:53 2020
  InstallationDate: Installed on 2020-10-11 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201009.1)
  PackageArchitecture: all
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RebootRequiredPkgs:
   linux-image-5.8.0-22-generic
   linux-base
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2017
  dmi.bios.release: 1.11
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: T-Rex_SK
  dmi.board.vendor: Acer
  dmi.board.version: V1.11
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.11
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd08/11/2017:br1.11:efr1.8:svnAcer:pnAspireES1-572:pvrV1.11:rvnAcer:rnT-Rex_SK:rvrV1.11:cvnAcer:ct10:cvrV1.11:
  dmi.product.family: SKL
  dmi.product.name: Aspire ES1-572
  dmi.product.sku: Aspire ES1-572_1085_V1.11
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1899310/+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 1899310] [NEW] the bluetooth headphone, although connected, the sound comes out of the notebook speakers

[RICARDO DA SILVA LISBOA]

Public bug reported:

the bluetooth headphone, although connected, the sound comes out of the
notebook speakers. I can only use wired headphones.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-21.22-generic 5.8.13
Uname: Linux 5.8.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu49
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ricardo1300 F pulseaudio
 /dev/snd/pcmC0D0p:   ricardo1300 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 10 23:23:53 2020
InstallationDate: Installed on 2020-10-11 (0 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201009.1)
PackageArchitecture: all
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not 
responding.
RebootRequiredPkgs:
 linux-image-5.8.0-22-generic
 linux-base
SourcePackage: alsa-driver
Symptom: audio
Title: Bluetooth sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/11/2017
dmi.bios.release: 1.11
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.11
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: T-Rex_SK
dmi.board.vendor: Acer
dmi.board.version: V1.11
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.11
dmi.ec.firmware.release: 1.8
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd08/11/2017:br1.11:efr1.8:svnAcer:pnAspireES1-572:pvrV1.11:rvnAcer:rnT-Rex_SK:rvrV1.11:cvnAcer:ct10:cvrV1.11:
dmi.product.family: SKL
dmi.product.name: Aspire ES1-572
dmi.product.sku: Aspire ES1-572_1085_V1.11
dmi.product.version: V1.11
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug groovy

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

Title:
  the bluetooth headphone, although connected, the sound comes out of
  the notebook speakers

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  the bluetooth headphone, although connected, the sound comes out of
  the notebook speakers. I can only use wired headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-21.22-generic 5.8.13
  Uname: Linux 5.8.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ricardo1300 F pulseaudio
   /dev/snd/pcmC0D0p:   ricardo1300 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 10 23:23:53 2020
  InstallationDate: Installed on 2020-10-11 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201009.1)
  PackageArchitecture: all
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RebootRequiredPkgs:
   linux-image-5.8.0-22-generic
   linux-base
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2017
  dmi.bios.release: 1.11
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: T-Rex_SK
  dmi.board.vendor: Acer
  dmi.board.version: V1.11
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.11
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd08/11/2017:br1.11:efr1.8:svnAcer:pnAspireES1-572:pvrV1.11:rvnAcer:rnT-Rex_SK:rvrV1.11:cvnAcer:ct10:cvrV1.11:
  dmi.product.family: SKL
  dmi.product.name: Aspire ES1-572
  dmi.product.sku: Aspire ES1-572_1085_V1.11
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1899310/+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 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network

[Ricardo Ortega]

Using ubuntu-20.04-live-server-amd64.iso I created an USB and did fresh
install, after fresh install I ran apt get update followed by apt get
upgrade, I then removed the existing yaml in /etc/netplan and added
99_config.yaml:

labuser@lab:~$ sudo nano /etc/netplan/99_config.yaml
labuser@lab:~$ sudo cat /etc/netplan/99_config.yaml
network:
  version: 2
  renderer: networkd
  ethernets:
enp0s25:
  dhcp4: no
  dhcp6: no
  bridges:
br0:
  interfaces: [enp0s25]
  dhcp4: no
  addresses: [10.59.2.57/24]
  gateway4: 10.59.2.1
  nameservers:
  search: [mydomain, otherdomain]
  addresses: [209.18.47.61, 209.18.47.62]
labuser@lab:~$ sudo shutdown -r
labuser@lab:~$ ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: enp0s25:  mtu 1500 qdisc fq_codel master 
br0 state UP group default qlen 1000
link/ether 3c:d9:2b:4f:01:80 brd ff:ff:ff:ff:ff:ff
3: br0:  mtu 1500 qdisc noqueue state UP group 
default qlen 1000
link/ether 3c:d9:2b:4f:01:80 brd ff:ff:ff:ff:ff:ff
inet6 fe80::ac4c::fe1b:21b7/64 scope link
   valid_lft forever preferred_lft forever
labuser@lab:~$ sudo net apply
labuser@lab:~$ ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: enp0s25:  mtu 1500 qdisc fq_codel master 
br0 state UP group default qlen 1000
link/ether 3c:d9:2b:4f:01:80 brd ff:ff:ff:ff:ff:ff
3: br0:  mtu 1500 qdisc noqueue state UP group 
default qlen 1000
link/ether 3c:d9:2b:4f:01:80 brd ff:ff:ff:ff:ff:ff
inet 10.59.2.57/24 brd 10.59.2.255 scope global br0
   valid_lft forever preferred_lft forever
inet6 fe80::ac4c::fe1b:21b7/64 scope link
   valid_lft forever preferred_lft forever
labuser@lab:~$ dpkg -l systemd
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   VersionArchitecture Description
+++-==-==--=
ii  systemd245.4-4ubuntu3 amd64system and service manager
labuser@lab:~$ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
labuser@lab:~$ sudo nano /etc/apt/sources.list
labuser@lab:~$ sudo cat /etc/apt/sources.list | grep proposed
deb http://archive.ubuntu.com/ubuntu/ focal-proposed restricted main multiverse 
universe 
labuser@lab:~$ sudo apt update
labuser@lab:~$ sudo apt install systemd
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  libnss-systemd libpam-systemd libsystemd0 systemd-sysv systemd-timesyncd
Suggested packages:
  systemd-container
The following packages will be upgraded:
  libnss-systemd libpam-systemd libsystemd0 systemd systemd-sysv
  systemd-timesyncd
6 upgraded, 0 newly installed, 0 to remove and 15 not upgraded.
Need to get 4385 kB of archives.
After this operation, 9216 B of additional disk space will be used.
Do you want to continue? [Y/n]
labuser@lab:~$ sudo shutdown -r
labuser@lab:~$ ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: enp0s25:  mtu 1500 qdisc fq_codel master 
br0 state UP group default qlen 1000
link/ether 3c:d9:2b:4f:01:80 brd ff:ff:ff:ff:ff:ff
3: br0:  mtu 1500 qdisc noqueue state UP group 
default qlen 1000
link/ether 3c:d9:2b:4f:01:80 brd ff:ff:ff:ff:ff:ff
inet 10.59.2.57/24 brd 10.59.2.255 scope global br0
   valid_lft forever preferred_lft forever
inet6 fe80::84eb:bdff:feb1:f4e2/64 scope link
   valid_lft forever preferred_lft forever
labuser@lab:~$ dpkg -l systemd
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---==>
ii  

[Touch-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths

[Ricardo Garicano Arenas]

it have reported too in 
https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/10
with that solution: 
https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/commit/0732f81a2c67354ddfa7a495bee6b0997c6ef244

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

Title:
  Regression: block staircase display with side-by-side monitors of
  different pixel widths

Status in Linux:
  Unknown
Status in libxcb package in Ubuntu:
  Confirmed
Status in xfwm4 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  Update based on further research.

  This only happens when the secondary external display is operating at
  a different pixel width to the internal. In this case eDP is 1920x1080
  whereas the external HDMI-A-0 is natively 1680x1050.

  It is caused by xfwm4's recent switch from using glx to xpresent for
  AMD GPUs.

  The underlying bug is in the AMD driver.

  I was able to reproduce on an external 1920x1200 display only when it
  was set to a non-native 1680x1050 resolution.

  ---
  Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred 
initially on the laptop that is having package upgrades applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  MachineType: LENOVO 20NECTO1WW
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal ubuntu ubuntu
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R11ET32W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NECTO1WW
  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: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E495
  dmi.product.name: 20NECTO1WW
  dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495
  dmi.product.version: ThinkPad E495
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths

[Ricardo Garicano Arenas]

I have similar problem with xubuntu & ubuntu studio (fresh install or upgrade) ,
it happen only with some resolutions & without screen rotation.
 i "solved" it increasing framebuffer in at least 1 pixel,

eg: xrandr --fb 1441x900 --output DisplayPort-0 --mode 1440x900
--panning 1440x0

try?

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

Title:
  Regression: block staircase display with side-by-side monitors of
  different pixel widths

Status in Linux:
  Unknown
Status in libxcb package in Ubuntu:
  Confirmed
Status in xfwm4 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  Update based on further research.

  This only happens when the secondary external display is operating at
  a different pixel width to the internal. In this case eDP is 1920x1080
  whereas the external HDMI-A-0 is natively 1680x1050.

  It is caused by xfwm4's recent switch from using glx to xpresent for
  AMD GPUs.

  The underlying bug is in the AMD driver.

  I was able to reproduce on an external 1920x1200 display only when it
  was set to a non-native 1680x1050 resolution.

  ---
  Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred 
initially on the laptop that is having package upgrades applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  MachineType: LENOVO 20NECTO1WW
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal ubuntu ubuntu
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R11ET32W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NECTO1WW
  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: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E495
  dmi.product.name: 20NECTO1WW
  dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495
  dmi.product.version: ThinkPad E495
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1864698] [NEW] Can't change laptop-screen brightness

[Ricardo Abreu]

Public bug reported:

I can't change the screen brightness anymore, on a Dell XPS13. Neither
the keyboard shortcuts nor gnome's sliders work. They move, but
brightness remains unchanged.

I first noticed this after disconnecting an external display, but I have
since rebooted and the problem remains.

This on Focal. I have done a series of upgrades since the original
installation and I know this used to work, but I can't be sure of when
exactly it stopped working. I noticed now, but it could have arisen
earlier. I am pretty sure it was OK on Disco.

I attach the output of lshw. Let me know what else I can provide.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 25 17:52:13 2020
DistUpgraded: 2020-02-24 18:02:48,088 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics 620 [1028:07e6]
InstallationDate: Installed on 2019-01-21 (400 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai 
 Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9370
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=ae14977c-0724-4298-9c08-80ea948af070 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-02-24 (0 days ago)
dmi.bios.date: 12/11/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.12.1
dmi.board.name: 0F6P3V
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.asset.tag: ricab-xps13
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9370
dmi.product.sku: 07E6
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal regression reproducible third-party-packages 
ubuntu

** Attachment added: "Output from lshw"
   https://bugs.launchpad.net/bugs/1864698/+attachment/5330946/+files/lshw.out

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

Title:
  Can't change laptop-screen brightness

Status in xorg package in Ubuntu:
  New

Bug description:
  I can't change the screen brightness anymore, on a Dell XPS13. Neither
  the keyboard shortcuts nor gnome's sliders work. They move, but
  brightness remains unchanged.

  I first noticed this after disconnecting an external display, but I
  have since rebooted and the problem remains.

  This on Focal. I have done a series of upgrades since the original
  installation and I know this used to work, but I can't be sure of when
  exactly it stopped working. I noticed now, but it could have arisen
  earlier. I am pretty sure it was OK on Disco.

  I attach the output of lshw. Let me know what else I can provide.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 25 17:52:13 2020
  DistUpgraded: 2020-02-24 18:02:48,088 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 

[Touch-packages] [Bug 1860394] [NEW] package lvm2 2.03.02-2ubuntu7 failed to install/upgrade: o subprocesso instalado, do pacote lvm2, o script post-installation retornou erro do status de saída 1

[Ricardo Pereira]

Public bug reported:

???

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: lvm2 2.03.02-2ubuntu7
ProcVersionSignature: Ubuntu 5.4.0-11.14-generic 5.4.8
Uname: Linux 5.4.0-11-generic x86_64
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
Date: Mon Jan 20 22:27:33 2020
ErrorMessage: o subprocesso instalado, do pacote lvm2, o script 
post-installation retornou erro do status de saída 1
InstallationDate: Installed on 2020-01-02 (18 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200102)
Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 
3.7.5-1ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.7
SourcePackage: lvm2
Title: package lvm2 2.03.02-2ubuntu7 failed to install/upgrade: o subprocesso 
instalado, do pacote lvm2, o script post-installation retornou erro do status 
de saída 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  package lvm2 2.03.02-2ubuntu7 failed to install/upgrade: o subprocesso
  instalado, do pacote lvm2, o script post-installation retornou erro do
  status de saída 1

Status in lvm2 package in Ubuntu:
  New

Bug description:
  ???

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.02-2ubuntu7
  ProcVersionSignature: Ubuntu 5.4.0-11.14-generic 5.4.8
  Uname: Linux 5.4.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Mon Jan 20 22:27:33 2020
  ErrorMessage: o subprocesso instalado, do pacote lvm2, o script 
post-installation retornou erro do status de saída 1
  InstallationDate: Installed on 2020-01-02 (18 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200102)
  Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 
3.7.5-1ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.7
  SourcePackage: lvm2
  Title: package lvm2 2.03.02-2ubuntu7 failed to install/upgrade: o subprocesso 
instalado, do pacote lvm2, o script post-installation retornou erro do status 
de saída 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1860394/+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 1827396] [NEW] package rsyslog 8.16.0-1ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Secure boot

[Ricardo Sendra]

Public bug reported:

The Log said something about this system not supporting Secure Boot.

The hardware is a iMac model A1224.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: rsyslog 8.16.0-1ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
Uname: Linux 4.4.0-145-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Thu May  2 11:52:55 2019
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-11-05 (907 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.31
SourcePackage: rsyslog
Title: package rsyslog 8.16.0-1ubuntu3.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package rsyslog 8.16.0-1ubuntu3.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1 Secure boot

Status in rsyslog package in Ubuntu:
  New

Bug description:
  The Log said something about this system not supporting Secure Boot.

  The hardware is a iMac model A1224.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: rsyslog 8.16.0-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
  Uname: Linux 4.4.0-145-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Thu May  2 11:52:55 2019
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-11-05 (907 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.31
  SourcePackage: rsyslog
  Title: package rsyslog 8.16.0-1ubuntu3.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1827396/+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 1825545] [NEW] video memory leak leak in steamplay games

[Ricardo Oliveira]

Public bug reported:

the failure occurs when going through the options menu of f1 2018 is
loading and after some time appears error message in the neon error
saying that is missing video memory and my hardware meets the
specifications where on windows can run the game.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
 GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 19 12:52:54 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
GraphicsCard:
 NVIDIA Corporation GP107 [GeForce GTX 1050] [10de:1c81] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050] [1043:85d7]
InstallationDate: Installed on 2019-04-18 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=c81d4a6c-0a07-4434-a01f-d18e087bdeac ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/25/2014
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: GA-78LMT-USB3 6.0
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-78LMT-USB3 6.0
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug disco possible-manual-nvidia-install 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/1825545

Title:
  video memory leak leak in steamplay games

Status in xorg package in Ubuntu:
  New

Bug description:
  the failure occurs when going through the options menu of f1 2018 is
  loading and after some time appears error message in the neon error
  saying that is missing video memory and my hardware meets the
  specifications where on windows can run the game.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 19 12:52:54 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP107 [GeForce GTX 1050] [10de:1c81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050] [1043:85d7]
  InstallationDate: Installed on 2019-04-18 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 

[Touch-packages] [Bug 1724919] Re: Bluetooth headphones only use A2DP when connected manually

[Ricardo Ribalda Delgado]

This workaround works for me:
https://gist.github.com/hxss/a3eadb0cc52e58ce7743dff71b92b297

Have only tried it twice now

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

Title:
  Bluetooth headphones only use A2DP when connected manually

Status in alsa-driver package in Ubuntu:
  Won't Fix

Bug description:
  Issue with Sony MDR-1ABT Bluetooth headphones:
  Once paired, the headphones will be connected automatically whenever they are 
switched on. However when connected this way, only the HSP/HFP profile will 
work and trying to change to A2DP in sound settings does nothing.
  If the headphones are then manually disconnected and reconnected from 
Bluetooth settings, they will initially use HSP/HFP but then selecting A2DP in 
sound settings will successfully make them use A2DP.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  neil   1443 F pulseaudio
   /dev/snd/pcmC0D0c:   neil   1443 F...m pulseaudio
   /dev/snd/controlC0:  neil   1443 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 19:12:59 2017
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: MDR-1ABT
  Symptom_Type: None of the above
  Title: [MDR-1ABT, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: Z270N-WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd07/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ270N-WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270N-WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z270N-WIFI
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1724919/+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 1785400] Re: Unable to locate package python3-defaults

[Ricardo Paxson]

Thanks.

However, as I wrote in the original report packages such as python-venv
also fail.

I found a fix by adding “universe” to my sources.list. Hopefully that is
the correct solution.

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

Title:
  Unable to locate package python3-defaults

Status in python3-defaults package in Ubuntu:
  Invalid

Bug description:
  Installed 18.04.1 Server AMD
  Trying to get pip3 and venv to work but I get the following:

  sudo apt install python3-defaults
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package python3-defaults

  same thing for python3-pip3, python3-venv

  have done apt update already.

  sources.list has the following (untouched after installation of OS)
  deb http://archive.ubuntu.com/ubuntu bionic main
  deb http://archive.ubuntu.com/ubuntu bionic-security main
  deb http://archive.ubuntu.com/ubuntu bionic-updates main

  I can't find this package anywhere. What do I add to sources.list to
  fix this?

  Thanks for any help and apologies if the solution is obvious.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1785400/+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 1785400] [NEW] Unable to locate package python3-defaults

[Ricardo Paxson]

Public bug reported:

Installed 18.04.1 Server AMD
Trying to get pip3 and venv to work but I get the following:

sudo apt install python3-defaults
Reading package lists... Done
Building dependency tree   
Reading state information... Done
E: Unable to locate package python3-defaults

same thing for python3-pip3, python3-venv

have done apt update already.

sources.list has the following (untouched after installation of OS)
deb http://archive.ubuntu.com/ubuntu bionic main
deb http://archive.ubuntu.com/ubuntu bionic-security main
deb http://archive.ubuntu.com/ubuntu bionic-updates main

I can't find this package anywhere. What do I add to sources.list to fix
this?

Thanks for any help and apologies if the solution is obvious.

** Affects: python3-defaults (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Unable to locate package python3-defaults

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  Installed 18.04.1 Server AMD
  Trying to get pip3 and venv to work but I get the following:

  sudo apt install python3-defaults
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package python3-defaults

  same thing for python3-pip3, python3-venv

  have done apt update already.

  sources.list has the following (untouched after installation of OS)
  deb http://archive.ubuntu.com/ubuntu bionic main
  deb http://archive.ubuntu.com/ubuntu bionic-security main
  deb http://archive.ubuntu.com/ubuntu bionic-updates main

  I can't find this package anywhere. What do I add to sources.list to
  fix this?

  Thanks for any help and apologies if the solution is obvious.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1785400/+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 1140716]

[Ricardo-vega-u]

Adding tag into "Whiteboard" field - ReadyForDev
The bug still active
*Status is correct
*Platform is included
*Feature is included
*Priority and Severity correctly set
*Logs included

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

Title:
  [regression] 3.5.0-26-generic and  3.2.0-39-generic GPU hangs on
  Sandybridge

Status in DRI:
  Won't Fix
Status in Mesa:
  Unknown
Status in linux package in Ubuntu:
  Invalid
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged
Status in linux source package in Precise:
  Fix Committed
Status in linux-lts-quantal source package in Precise:
  Fix Committed
Status in linux-lts-raring source package in Precise:
  Invalid
Status in mesa source package in Precise:
  Triaged
Status in linux source package in Quantal:
  Invalid
Status in linux-lts-quantal source package in Quantal:
  Invalid
Status in linux source package in Raring:
  Invalid
Status in linux-lts-quantal source package in Raring:
  Invalid
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Won't Fix

Bug description:
  I'm getting errors about GPU hangs every minute or so (usually only
  when using FF and scrolling a webpage or something). I also get an
  annoying ubuntu dialog saying there is a "system error".

  This didn't happen with 3.5.0-24-generic.

  Here is the dmesg:
  [15169.033709] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15169.034517] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [15628.480216] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15628.480570] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [15844.231372] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15844.231773] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [20173.232593] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [20173.233211] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26285.650393] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26285.650980] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26285.658405] [ cut here ]
  [26285.658472] WARNING: at 
/build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 
gen6_enable_rps+0x706/0x710 [i915]()
  [26285.658474] Hardware name: SATELLITE Z830
  [26285.658476] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate 
libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 
snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm 
arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_64 snd_hda_intel 
snd_hda_codec snd_hwdep uvcvideo snd_pcm videobuf2_core microcode videodev bnep 
iwlwifi videobuf2_vmalloc snd_seq_midi psmouse videobuf2_memops snd_rawmidi 
rfcomm pcspkr snd_seq_midi_event serio_raw snd_seq bluetooth mac80211 snd_timer 
snd_seq_device i915 drm_kms_helper cfg80211 drm toshiba_acpi snd sparse_keymap 
soundcore wmi i2c_algo_bit toshiba_bluetooth snd_page_alloc parport_pc mei 
video mac_hid lpc_ich ppdev nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc 
lp parport e1000e ahci libahci [last unloaded: sdhci]
  [26285.658537] Pid: 23433, comm: kworker/u:0 Not tainted 3.5.0-26-generic 
#40-Ubuntu
  [26285.658539] Call Trace:
  [26285.658549]  [] warn_slowpath_common+0x7f/0xc0
  [26285.658553]  [] warn_slowpath_null+0x1a/0x20
  [26285.658569]  [] gen6_enable_rps+0x706/0x710 [i915]
  [26285.658584]  [] intel_modeset_init_hw+0x66/0xa0 [i915]
  [26285.658595]  [] i915_reset+0x1a4/0x6e0 [i915]
  [26285.658601]  [] ? __switch_to+0x12b/0x420
  [26285.658612]  [] i915_error_work_func+0xc3/0x110 [i915]
  [26285.658618]  [] process_one_work+0x12a/0x420
  [26285.658629]  [] ? gen6_pm_rps_work+0xe0/0xe0 [i915]
  [26285.658632]  [] worker_thread+0x12e/0x2f0
  [26285.658636]  [] ? manage_workers.isra.26+0x200/0x200
  [26285.658640]  [] kthread+0x93/0xa0
  [26285.658644]  [] kernel_thread_helper+0x4/0x10
  [26285.658649]  [] ? kthread_freezable_should_stop+0x70/0x70
  [26285.658652]  [] ? gs_change+0x13/0x13
  [26285.658654] ---[ end trace 59c6162fdfcbffee ]---
  [26756.021167] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26756.021426] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26766.014093] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26766.014397] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26932.376233] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26932.376544] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26932.384285] [ cut here ]
  [26932.384354] WARNING: at 
/build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 

Re: [Touch-packages] [Bug 1774979] Re: no input and output devices detected in sound definitions

[Paulo Jorge Costa Ricardo Barroso]

I wanna thank you for the time you spent with this.

What I did was a fresh install of the Ubuntu because I needed the laptop
urgently. Everything went back to normal.

Thank you once again for your support. I want to say that I' m very pleased
with Ubuntu.

A Ter, 5/06/2018, 03:11, Daniel van Vugt 
escreveu:

> When experiencing the problem please also run:
>
>   ps auxw | grep pulse
>
> and send us the output.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1774979
>
> Title:
>   no input and output devices detected in sound definitions
>
> Status in pulseaudio package in Ubuntu:
>   Incomplete
>
> Bug description:
>   After installing pulse audio equalizer, it worked good. everything was
>   detected in Sound Definitions and there was sound in the headphone
>   out.
>
>   In the day after, every input and output devices were gone in Sound
>   Definition. I uninstalled pulse audio equalizer but nothing happened
>   in Sound Definitions, everything was gone.
>
>   I rebooted the system and nothing. No sound.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: pulseaudio 1:8.0-0ubuntu3.10
>   ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
>   Uname: Linux 4.13.0-43-generic i686
>   ApportVersion: 2.20.1-0ubuntu2.18
>   Architecture: i386
>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
> '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D6c',
> '/dev/snd/pcmC0D6p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c',
> '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq',
> '/dev/snd/timer'] failed with exit code 1:
>   CurrentDesktop: Unity
>   Date: Mon Jun  4 12:35:32 2018
>   InstallationDate: Installed on 2018-01-04 (150 days ago)
>   InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386
> (20170801)
>   ProcEnviron:
>LANGUAGE=pt:pt_BR:en
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=pt_PT.UTF-8
>SHELL=/bin/bash
>   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: 05/15/2006
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: A6FAS.212
>   dmi.board.asset.tag: To Be Filled By O.E.M.
>   dmi.board.name: A6F
>   dmi.board.vendor: ASUSTeK Computer Inc.
>   dmi.board.version: 1.0
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: ASUSTeK Computer Inc.
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrA6FAS.212:bd05/15/2006:svnASUSTeKComputerInc.:pnA6F:pvr1.0:rvnASUSTeKComputerInc.:rnA6F:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
>   dmi.product.family: To Be Filled By O.E.M.
>   dmi.product.name: A6F
>   dmi.product.version: 1.0
>   dmi.sys.vendor: ASUSTeK Computer Inc.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1774979/+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/1774979

Title:
  no input and output devices detected in sound definitions

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After installing pulse audio equalizer, it worked good. everything was
  detected in Sound Definitions and there was sound in the headphone
  out.

  In the day after, every input and output devices were gone in Sound
  Definition. I uninstalled pulse audio equalizer but nothing happened
  in Sound Definitions, everything was gone.

  I rebooted the system and nothing. No sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.10
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-43-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D6c', '/dev/snd/pcmC0D6p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Mon Jun  4 12:35:32 2018
  InstallationDate: Installed on 2018-01-04 (150 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  ProcEnviron:
   LANGUAGE=pt:pt_BR:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_PT.UTF-8
   SHELL=/bin/bash
  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: 05/15/2006
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A6FAS.212
  

[Touch-packages] [Bug 1774979] [NEW] no input and output devices detected in sound definitions

[Paulo Jorge Costa Ricardo Barroso]

Public bug reported:

After installing pulse audio equalizer, it worked good. everything was
detected in Sound Definitions and there was sound in the headphone out.

In the day after, every input and output devices were gone in Sound
Definition. I uninstalled pulse audio equalizer but nothing happened in
Sound Definitions, everything was gone.

I rebooted the system and nothing. No sound.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3.10
ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-43-generic i686
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: i386
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D6c', '/dev/snd/pcmC0D6p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
Date: Mon Jun  4 12:35:32 2018
InstallationDate: Installed on 2018-01-04 (150 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
ProcEnviron:
 LANGUAGE=pt:pt_BR:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pt_PT.UTF-8
 SHELL=/bin/bash
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: 05/15/2006
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A6FAS.212
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: A6F
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA6FAS.212:bd05/15/2006:svnASUSTeKComputerInc.:pnA6F:pvr1.0:rvnASUSTeKComputerInc.:rnA6F:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: A6F
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

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


** Tags: apport-bug i386 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/1774979

Title:
  no input and output devices detected in sound definitions

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After installing pulse audio equalizer, it worked good. everything was
  detected in Sound Definitions and there was sound in the headphone
  out.

  In the day after, every input and output devices were gone in Sound
  Definition. I uninstalled pulse audio equalizer but nothing happened
  in Sound Definitions, everything was gone.

  I rebooted the system and nothing. No sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.10
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-43-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D6c', '/dev/snd/pcmC0D6p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Mon Jun  4 12:35:32 2018
  InstallationDate: Installed on 2018-01-04 (150 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  ProcEnviron:
   LANGUAGE=pt:pt_BR:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_PT.UTF-8
   SHELL=/bin/bash
  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: 05/15/2006
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A6FAS.212
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: A6F
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA6FAS.212:bd05/15/2006:svnASUSTeKComputerInc.:pnA6F:pvr1.0:rvnASUSTeKComputerInc.:rnA6F:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: A6F
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1774979/+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 1759681] Re: package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: triggers looping, abandoned

[Ricardo Almeida]

Attached /var/log/dist-upgrade/*.* and /var/log/dist-
upgrade/20180327-1854/* (It had older updates there, probably not
useful, I would say)

** Attachment added: "dist-upgrade.tgz"
   
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1759681/+attachment/5095118/+files/dist-upgrade.tgz

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

Title:
  package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: triggers
  looping, abandoned

Status in gconf package in Ubuntu:
  Incomplete

Bug description:
  Error report showed up after doing upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gconf2 3.2.6-4ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Mar 27 22:17:52 2018
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2011-02-12 (2601 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-03-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1759681/+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 1759681] Re: package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: triggers looping, abandoned

[Ricardo Almeida]

I upgraded from Ubuntu 17.10 to 18.04 and it failed in the process
(because of cinnamon-common bug
https://bugs.launchpad.net/ubuntu/+source/cinnamon/+bug/1759127, I
think). I manage  to have all packages upgraded in the end, although
cinnamon fails to start (different issue, I would say, just letting you
know as it could be the thing that made the crash dialog showed up
later)...

When I logged in Gnome, I did some more upgrades, and I got a few
appreport crashes dialogs, so I just submit the info it asked me too...

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

Title:
  package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: triggers
  looping, abandoned

Status in gconf package in Ubuntu:
  Incomplete

Bug description:
  Error report showed up after doing upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gconf2 3.2.6-4ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Mar 27 22:17:52 2018
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2011-02-12 (2601 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-03-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1759681/+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 1759680] [NEW] package python3 3.6.4-1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4

[Ricardo Almeida]

Public bug reported:

Error report showed up after doing upgrade

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: python3 3.6.4-1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu1
Architecture: amd64
Date: Tue Mar 27 22:04:05 2018
ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
InstallationDate: Installed on 2011-02-12 (2601 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu1
 apt  1.6~beta1
SourcePackage: python3-defaults
Title: package python3 3.6.4-1 failed to install/upgrade: installed python3 
package post-installation script subprocess returned error exit status 4
UpgradeStatus: Upgraded to bionic on 2018-03-27 (0 days ago)

** Affects: python3-defaults (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package python3 3.6.4-1 failed to install/upgrade: installed python3
  package post-installation script subprocess returned error exit status
  4

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  Error report showed up after doing upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3 3.6.4-1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  Date: Tue Mar 27 22:04:05 2018
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  InstallationDate: Installed on 2011-02-12 (2601 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: python3-defaults
  Title: package python3 3.6.4-1 failed to install/upgrade: installed python3 
package post-installation script subprocess returned error exit status 4
  UpgradeStatus: Upgraded to bionic on 2018-03-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1759680/+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 1759681] [NEW] package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: triggers looping, abandoned

[Ricardo Almeida]

Public bug reported:

Error report showed up after doing upgrade

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: gconf2 3.2.6-4ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu1
AptOrdering: NULL: ConfigurePending
Architecture: amd64
Date: Tue Mar 27 22:17:52 2018
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2011-02-12 (2601 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu1
 apt  1.6~beta1
SourcePackage: gconf
Title: package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: triggers 
looping, abandoned
UpgradeStatus: Upgraded to bionic on 2018-03-27 (0 days ago)

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


** Tags: amd64 apport-package bionic

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

Title:
  package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: triggers
  looping, abandoned

Status in gconf package in Ubuntu:
  New

Bug description:
  Error report showed up after doing upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gconf2 3.2.6-4ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Mar 27 22:17:52 2018
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2011-02-12 (2601 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-03-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1759681/+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 1609211] Re: [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at all

[Ricardo Ramírez]

I uploaded this video showing how to fix the problem:

https://www.youtube.com/watch?v=Se1NDgPhteg

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

Title:
  [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  When the headphones are plugged, they are not detected. All sound
  comes from the built in speakers, and none from the headphones.

  The jack works on Windows.

  This bug seems similar to #1184838. However, I'm posting it as the
  hardware is different.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   adin   4035 F...m pulseaudio
   /dev/snd/controlC0:  adin   4035 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug  2 22:59:12 2016
  InstallationDate: Installed on 2016-07-03 (30 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   adin   4035 F...m pulseaudio
   /dev/snd/controlC0:  adin   4035 F pulseaudio
adin  32107 F alsamixer
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [Alienware 17 R3, Creative CA0132, Green Headphone Out, Front] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2016
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.2.15
  dmi.board.name: Alienware 17 R3
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.2.15:bd07/07/2016:svnAlienware:pnAlienware17R3:pvr1.2.15:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:
  dmi.product.name: Alienware 17 R3
  dmi.product.version: 1.2.15
  dmi.sys.vendor: Alienware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1609211/+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 1609211] Re: [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at all

[Ricardo Ramírez]

1. In terminal, enter the command "alsamixer".

2. An ASCI UI will open, use the right arrow key to find the item:
"HP/speaker Auto Detect". it will say "Off" next to it.

3. Press M and the "Off" tag will disappear.

4. Re-plug your headphones.

Enjoy!

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

Title:
  [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  When the headphones are plugged, they are not detected. All sound
  comes from the built in speakers, and none from the headphones.

  The jack works on Windows.

  This bug seems similar to #1184838. However, I'm posting it as the
  hardware is different.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   adin   4035 F...m pulseaudio
   /dev/snd/controlC0:  adin   4035 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug  2 22:59:12 2016
  InstallationDate: Installed on 2016-07-03 (30 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   adin   4035 F...m pulseaudio
   /dev/snd/controlC0:  adin   4035 F pulseaudio
adin  32107 F alsamixer
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [Alienware 17 R3, Creative CA0132, Green Headphone Out, Front] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2016
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.2.15
  dmi.board.name: Alienware 17 R3
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.2.15:bd07/07/2016:svnAlienware:pnAlienware17R3:pvr1.2.15:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:
  dmi.product.name: Alienware 17 R3
  dmi.product.version: 1.2.15
  dmi.sys.vendor: Alienware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1609211/+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 1749630] [NEW] package libuuid1 2.27.1-6ubuntu3.4 failed to install/upgrade: 10.4193:subprocess installed post-installation script returned error exit status 1

[Ricardo I Soto]

Public bug reported:

An error occurred while upgrading to a new version of Bash on Ubuntu on
Windows. Report was given and I decided to send the report.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libuuid1 2.27.1-6ubuntu3.4
ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
Uname: Linux 4.4.0-43-Microsoft x86_64
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
Date: Wed Feb 14 21:05:15 2018
DuplicateSignature: package:libuuid1:2.27.1-6ubuntu3.4:10.4193:subprocess 
installed post-installation script returned error exit status 1
ErrorMessage: 10.4193:subprocess installed post-installation script returned 
error exit status 1
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.0.1ubuntu2.17
SourcePackage: util-linux
Title: package libuuid1 2.27.1-6ubuntu3.4 failed to install/upgrade: 
10.4193:subprocess installed post-installation script returned error exit 
status 1
UpgradeStatus: Upgraded to xenial on 2018-02-15 (0 days ago)

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package dist-upgrade third-party-packages uec-images 
xenial

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

Title:
  package libuuid1 2.27.1-6ubuntu3.4 failed to install/upgrade:
  10.4193:subprocess installed post-installation script returned error
  exit status 1

Status in util-linux package in Ubuntu:
  New

Bug description:
  An error occurred while upgrading to a new version of Bash on Ubuntu
  on Windows. Report was given and I decided to send the report.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libuuid1 2.27.1-6ubuntu3.4
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Wed Feb 14 21:05:15 2018
  DuplicateSignature: package:libuuid1:2.27.1-6ubuntu3.4:10.4193:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: 10.4193:subprocess installed post-installation script returned 
error exit status 1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.0.1ubuntu2.17
  SourcePackage: util-linux
  Title: package libuuid1 2.27.1-6ubuntu3.4 failed to install/upgrade: 
10.4193:subprocess installed post-installation script returned error exit 
status 1
  UpgradeStatus: Upgraded to xenial on 2018-02-15 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1749630/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Ricardo]

#103 did fix it

Adding:

[ipv4]
dns-priority=-42

to system-connections config file
or runing 'sudo nmcli connection modify  ipv4.dns-priority 
-42'
and restarting networkmanager service
did fix dns leaking using ProtonVPN on openvpn for me, thanks.

But i didn't quite understand the problem! Is it the provided openvpn
config file misconfigured or a networkmanager bug? As i said, in others
distros doesn't happend!

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Zesty:
  Confirmed
Status in network-manager source package in Artful:
  Confirmed

Bug description:
  [Impact]

   * NetworkManager incorrectly handles dns-priority of the VPN-like
  connections, which leads to leaking DNS queries outside of the VPN
  into the general internet.

   * Upstream has resolved this issue in master and 1.8 to correctly
  configure any dns backends with negative dns-priority settings.

  [Test Case]

  #FIXME#

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  #FIXME#

  [Regression Potential]

   * If this issue is changed DNS resolution will change, for certain
  queries, to go via VPN rather than general internet. And therefore,
  one may get new/different results or even loose access to
  resolve/access certain parts of the interent depending on what the DNS
  server on VPN chooses to respond to.

  [Other Info]
   
   * Original bug report

  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1624317/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Ricardo]

This bug still exists in Ubuntu 17.10 (ProtonVPN). In distros as Arch, Manjaro 
and Fedora it never happened. Is this going to 18.04 LTS as well?! Why no one 
cares?

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Zesty:
  Confirmed
Status in network-manager source package in Artful:
  Confirmed

Bug description:
  [Impact]

   * NetworkManager incorrectly handles dns-priority of the VPN-like
  connections, which leads to leaking DNS queries outside of the VPN
  into the general internet.

   * Upstream has resolved this issue in master and 1.8 to correctly
  configure any dns backends with negative dns-priority settings.

  [Test Case]

  #FIXME#

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  #FIXME#

  [Regression Potential]

   * If this issue is changed DNS resolution will change, for certain
  queries, to go via VPN rather than general internet. And therefore,
  one may get new/different results or even loose access to
  resolve/access certain parts of the interent depending on what the DNS
  server on VPN chooses to respond to.

  [Other Info]
   
   * Original bug report

  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1624317/+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 1681513] Re: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue)

[Ricardo]

Same problem with a build-in laptop wifi

Device = BCM43142 802.11b/g/n
Manufacturer = Broadcom Limited
Driver = wl0
Driverversion = 6.30.223.271 (r587334)

Solved by adding:

[Device]
wifi.scan-rand-mac-address=no

to NetworkManager.conf && restart network-manager service

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

Title:
  Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi
  adapters from working (MAC Address Randomization issue)

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  According to 
  
https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/
  there is a new privacy feature in the new version of NetworkManager.
  This privacy feature can cause some USB WiFi adapters to stop working
  while they used to work with older versions of NetworkManager (Ubuntu 16.10 
or older).

  The purpose of this privacy feature is to get your computer to report a new 
random MAC address whenever you connect to a WiFi network.
  This privacy feature is especially useful when you connect to public WiFi 
networks, so that the operators cannot identify you when you connect multiple 
times.

  The downside of this privacy feature is that some USB WiFi adapters misbehave 
when NetworkManager tries to change their MAC address repeatedly. 
  The result is that those USB WiFi adapters cannot connect anymore to the WiFi 
 network.

  Original report follows:

  My Panda USB wi-fi adapter works just fine on 16.10, but when I try to
  connect to my wi-fi router in 17.04, GNOME network manager reports
  "Connection failed." I did some tinkering, and noticed that my MAC
  address for my wifi adapter, according to GNOME, is DIFFERENT every
  time I make it forget my wifi settings and try to reconnect. Weird,
  right? Any leads on a possible fix or work-around?

  I'm running the latest beta of Ubuntu GNOME 17.04, kernel
  4.10.0-19-generic, GNOME 3.24.0.

  https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-
  networkmanager-1-4-0/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513/+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 1681513] Re: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue)

[Ricardo]

Device = BCM43142 802.11b/g/n
Manufacturer = Broadcom Limited
Driver = wl0
Driverversion = 6.30.223.271 (r587334)

I have this same problem with a build-in wifi

I had to add:

[Device]
wifi.scan-rand-mac-address=no

to NetworkManager.conf to make it work

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

Title:
  Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi
  adapters from working (MAC Address Randomization issue)

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  According to 
  
https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/
  there is a new privacy feature in the new version of NetworkManager.
  This privacy feature can cause some USB WiFi adapters to stop working
  while they used to work with older versions of NetworkManager (Ubuntu 16.10 
or older).

  The purpose of this privacy feature is to get your computer to report a new 
random MAC address whenever you connect to a WiFi network.
  This privacy feature is especially useful when you connect to public WiFi 
networks, so that the operators cannot identify you when you connect multiple 
times.

  The downside of this privacy feature is that some USB WiFi adapters misbehave 
when NetworkManager tries to change their MAC address repeatedly. 
  The result is that those USB WiFi adapters cannot connect anymore to the WiFi 
 network.

  Original report follows:

  My Panda USB wi-fi adapter works just fine on 16.10, but when I try to
  connect to my wi-fi router in 17.04, GNOME network manager reports
  "Connection failed." I did some tinkering, and noticed that my MAC
  address for my wifi adapter, according to GNOME, is DIFFERENT every
  time I make it forget my wifi settings and try to reconnect. Weird,
  right? Any leads on a possible fix or work-around?

  I'm running the latest beta of Ubuntu GNOME 17.04, kernel
  4.10.0-19-generic, GNOME 3.24.0.

  https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-
  networkmanager-1-4-0/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513/+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 1710925] [NEW] package apt 1.2.24 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[ricardo filipe castro pinheiro]

Public bug reported:

don't know

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: apt 1.2.24
ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
Uname: Linux 4.4.0-89-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
AptOrdering:
 apt: Configure
 apt-utils: Install
 apt-utils: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Tue Aug 15 17:41:54 2017
DpkgTerminalLog:
 dpkg: error processing package apt (--configure):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2016-08-10 (370 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: apt
Title: package apt 1.2.24 failed to install/upgrade: package is in a very bad 
inconsistent state; you should  reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package apt 1.2.24 failed to install/upgrade: package is in a very bad
  inconsistent state; you should  reinstall it before attempting
  configuration

Status in apt package in Ubuntu:
  New

Bug description:
  don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.24
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Uname: Linux 4.4.0-89-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  AptOrdering:
   apt: Configure
   apt-utils: Install
   apt-utils: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Aug 15 17:41:54 2017
  DpkgTerminalLog:
   dpkg: error processing package apt (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-08-10 (370 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: apt
  Title: package apt 1.2.24 failed to install/upgrade: package is in a very bad 
inconsistent state; you should  reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1710925/+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 1588917] Re: Upgrade ping to latest version that doesn't require SUID or NET_RAW capability

[Ricardo]

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

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

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

Status in iputils package in Ubuntu:
  Triaged

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

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

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

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

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

[Touch-packages] [Bug 1705437] [NEW] Upstream 'column' is newer than bsdmainutils'

[Ricardo Pérez López]

Public bug reported:

The 'column' program included in upstream util-linux
(https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/tree
/text-utils/column.c) is newer than the included in the bsdmainutil
package
(https://anonscm.debian.org/cgit/bsdmainutils/bsdmainutils.git/tree/usr.bin/column/column.c).
However, debian/rules from util-linux package states the opposite, and
therefore Ubuntu now is using 'column' from bsdmainutils instead of the
util-linux one.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: util-linux 2.27.1-6ubuntu3.3
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: i3
Date: Thu Jul 20 11:41:36 2017
InstallationDate: Installed on 2016-04-23 (452 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: util-linux
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  Upstream 'column' is newer than bsdmainutils'

Status in util-linux package in Ubuntu:
  New

Bug description:
  The 'column' program included in upstream util-linux
  (https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/tree
  /text-utils/column.c) is newer than the included in the bsdmainutil
  package
  
(https://anonscm.debian.org/cgit/bsdmainutils/bsdmainutils.git/tree/usr.bin/column/column.c).
  However, debian/rules from util-linux package states the opposite, and
  therefore Ubuntu now is using 'column' from bsdmainutils instead of
  the util-linux one.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: i3
  Date: Thu Jul 20 11:41:36 2017
  InstallationDate: Installed on 2016-04-23 (452 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1705437/+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 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

[Ricardo Rodrigues]

More than a year and this bug is not yet fixed?

Is it a huge problem to solve?

Can I help with some log files or something like that?

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

Title:
  Refused to switch profile to headset_head_unit: Not connected

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to connect a bluetooth-speaker-with-microphone (Mi
  Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't
  use it as a headset with microphone.

  The device doesn't list in the "Input Devices" by default, and using
  the sound settings to change the profile of the device to HSP/HFP
  results in this log message:

  W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to
  headset_head_unit: Not connected

  
  I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10.

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1576559/+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 1549163] Re: Bluetooth headset HSP/HFP mode not working in Xenial

[Ricardo Rodrigues]

I'm also suffering from this issue.

New wireless headset with mic, can't use the mic...

But I'm using Ubuntu 16.10 (Yakkety Yak). What can I do to help debug
this issue?

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

Title:
  Bluetooth headset HSP/HFP mode not working in Xenial

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Using the 2/14 Xenial daily build, paired bluetooth headsets' do not
  work in HSP/HFP mode.

  [Steps to reproduce]
  1. Pair a bluetooth headset with laptop installed with Xenial 2/14 daily build
  2. In the laptop, go to sound settings > output tab > try switching mode to 
HSP/HFP mode
  3. Press the "test sound" button and try playing sound
  4. Go to the input tab and check if bluetooth headset mic is listed

  [Expected result]
  After step 3, a window for mono audio test should pop up
  After step 4, the input tab should list a bluetooth headset mic device

  [Actual result]
  After step 3, the window that pops up is for stereo (A2DP) audio test
  After step 4, the input tab does not list any bluetooth headset mic

  [Details]
  BT wireless module:
   * Intel 3160
  BT headset:
   * Jabra CLI
  Xenial: 2/14 daily build:
   * Kernel: 4.4.0-6
   * bluez: 5.36-0ubuntu1
   * gstreamer1.0-pulseaudio:amd64: 1.7.2-1ubuntu1
   * pulseaudio: 1:8.0-0ubuntu2
   * pulseaudio-module-bluetooth: 1:8.0-0ubuntu2

  [Note]
  Also double checked with same set of hardware, but with 15.10 installed.
  Bluetooth headset HSP/HFP mode worked correctly in 15.10.

  15.10 details:
   * kernel: 4.2.0-19
   * bluez: 5.35-0ubuntu2
   * gstreamer1.0-pulseaudio:amd64: 1.6.0-1ubuntu1
   * pulseaudio: 1:6.0-0ubuntu13
   * pulseaudio-module-bluetooth: 1:6.0-0ubuntu13

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1549163/+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 1659834] Re: HDMI port not working

[Ricardo]

Suddenly started working again three days later. No idea why. Feel free
to close this

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

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

Title:
  HDMI port not working

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Kernel version: 4.4.0-59-generic
  Laptop is MacBookPro11,4
  Graphics card: VGA compatible controller [0300]: Intel Corporation Crystal 
Well Integrated Graphics Controller [8086:0d26] (rev 08)

  Connecting an external monitor using HDMI works fine when booting up
  on macOS but not in ubuntu 16.04, kernel 4.4.0-59-generic, using same
  cable and monitor. It was working fine as recently as yesterday, not
  sure what happened... Tried booting up in previous kernel version
  (4.4.0-53-generic) but also didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jan 27 14:02:05 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   i915-4.6.3-4.4.0, 1, 4.4.0-21-generic, x86_64: installed
   i915-4.6.3-4.4.0, 1, 4.4.0-57-generic, x86_64: installed
   i915-4.6.3-4.4.0, 1, 4.4.0-59-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Crystal Well Integrated Graphics Controller [8086:0d26] 
(rev 08) (prog-if 00 [VGA controller])
     Subsystem: Apple Inc. Crystal Well Integrated Graphics Controller 
[106b:0147]
  InstallationDate: Installed on 2016-04-26 (276 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Apple Inc. MacBookPro11,4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed 
root=UUID=bba094b5-a045-4054-b44b-3024e2585537 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2016
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP114.88Z.0172.B09.1602151732
  dmi.board.name: Mac-06F11FD93F0323C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,4
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-06F11FD93F0323C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B09.1602151732:bd02/15/2016:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5:
  dmi.product.name: MacBookPro11,4
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.68-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.2-0intel1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.2-0intel1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Jan 27 12:29:24 2017
  xserver.configfile: default
  xserver.errors:

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1659834/+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 1659834] [NEW] HDMI port not working

[Ricardo]

Public bug reported:

Kernel version: 4.4.0-59-generic
Laptop is MacBookPro11,4
Graphics card: VGA compatible controller [0300]: Intel Corporation Crystal Well 
Integrated Graphics Controller [8086:0d26] (rev 08)

Connecting an external monitor using HDMI works fine when booting up on
macOS but not in ubuntu 16.04, kernel 4.4.0-59-generic, using same cable
and monitor. It was working fine as recently as yesterday, not sure what
happened... Tried booting up in previous kernel version
(4.4.0-53-generic) but also didn't work.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
.tmp.unity_support_test.0:

ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Jan 27 14:02:05 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 i915-4.6.3-4.4.0, 1, 4.4.0-21-generic, x86_64: installed
 i915-4.6.3-4.4.0, 1, 4.4.0-57-generic, x86_64: installed
 i915-4.6.3-4.4.0, 1, 4.4.0-59-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Crystal Well Integrated Graphics Controller [8086:0d26] (rev 
08) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. Crystal Well Integrated Graphics Controller [106b:0147]
InstallationDate: Installed on 2016-04-26 (276 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Apple Inc. MacBookPro11,4
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed 
root=UUID=bba094b5-a045-4054-b44b-3024e2585537 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/15/2016
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP114.88Z.0172.B09.1602151732
dmi.board.name: Mac-06F11FD93F0323C5
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,4
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-06F11FD93F0323C5
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B09.1602151732:bd02/15/2016:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5:
dmi.product.name: MacBookPro11,4
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.68-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.2-0intel1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.2-0intel1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Jan 27 12:29:24 2017
xserver.configfile: default
xserver.errors:

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

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


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

** Description changed:

  Kernel version: 4.4.0-59-generic
  Laptop is MacBookPro11,4
  Graphics card: VGA compatible controller [0300]: Intel Corporation Crystal 
Well Integrated Graphics Controller [8086:0d26] (rev 08)
  
  Connecting an external monitor using HDMI works fine when booting up on
  macOS but not in ubuntu 16.04, kernel 4.4.0-59-generic, using same cable
- and monitor. It was working fine as soon as yesterday, not sure what
+ and monitor. It was working fine as recently as yesterday, not sure what
  happened... Tried booting up in previous kernel version
  (4.4.0-53-generic) but also didn't work.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jan 27 14:02:05 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
-  i915-4.6.3-4.4.0, 1, 

[Touch-packages] [Bug 1638234] [NEW] package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: subprocesso script post-installation instalado retornou erro do status de saída 10

[Ricardo Justem]

Public bug reported:

yes

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: unattended-upgrades 0.90ubuntu0.1
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
.var.log.unattended-upgrades.unattended-upgrades.log:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Tue Nov  1 07:36:08 2016
ErrorMessage: subprocesso script post-installation instalado retornou erro do 
status de saída 10
InstallationDate: Installed on 2016-07-28 (95 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: unattended-upgrades
Title: package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: 
subprocesso script post-installation instalado retornou erro do status de saída 
10
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apt.apt.conf.d.10periodic:
 APT::Periodic::Update-Package-Lists "1";
 APT::Periodic::Download-Upgradeable-Packages "0";
 APT::Periodic::AutocleanInterval "0";
 APT::Periodic::Unattended-Upgrade "0";
mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-10-24T13:59:39.614980

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade:
  subprocesso script post-installation instalado retornou erro do status
  de saída 10

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  yes

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  .var.log.unattended-upgrades.unattended-upgrades.log:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Nov  1 07:36:08 2016
  ErrorMessage: subprocesso script post-installation instalado retornou erro do 
status de saída 10
  InstallationDate: Installed on 2016-07-28 (95 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: 
subprocesso script post-installation instalado retornou erro do status de saída 
10
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "1";
   APT::Periodic::Download-Upgradeable-Packages "0";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "0";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-10-24T13:59:39.614980

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1638234/+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 1495971] Re: Samsung ML-1250 prints only first job and then disconnects

[Ricardo Biloti]

I read this full issue report and replies and it seems I am experienced
an analogous problem. Should I report the details of my case here or
open a new issue?

Here are few initial information:

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.1 LTS
Release:16.04
Codename:   xenial

uname -a:
Linux mangue 4.4.0-42-generic #62-Ubuntu SMP Fri Oct 7 23:11:45 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux

lsusb:
Bus 005 Device 025: ID 04e8:3301 Samsung Electronics Co., Ltd ML-1660 Series

/var/log/syslog: (the block below keeps popping out continuously)

Oct 10 20:11:27 mangue kernel: [ 1594.728192] usb 5-2: reset full-speed USB 
device number 40 using uhci_hcd
Oct 10 20:11:27 mangue kernel: [ 1594.885385] usb 5-2: USB disconnect, device 
number 40
Oct 10 20:11:27 mangue kernel: [ 1594.885804] usblp1: removed
Oct 10 20:11:27 mangue udev-configure-printer[6009]: remove 
/devices/pci:00/:00:1d.0/usb5/5-2
Oct 10 20:11:27 mangue kernel: [ 1595.98] usb 5-2: new full-speed USB 
device number 41 using uhci_hcd
Oct 10 20:11:28 mangue kernel: [ 1595.169199] usb 5-2: New USB device found, 
idVendor=04e8, idProduct=3301
Oct 10 20:11:28 mangue kernel: [ 1595.169209] usb 5-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
Oct 10 20:11:28 mangue kernel: [ 1595.169216] usb 5-2: Product: ML-1660 Series
Oct 10 20:11:28 mangue kernel: [ 1595.169222] usb 5-2: Manufacturer: Samsung 
Electronics Co., Ltd.
Oct 10 20:11:28 mangue kernel: [ 1595.169227] usb 5-2: SerialNumber: 
Z5ASBDAZ809914N.
Oct 10 20:11:28 mangue kernel: [ 1595.176325] usblp 5-2:1.0: usblp1: USB 
Bidirectional printer dev 41 if 0 alt 0 proto 2 vid 0x04E8 pid 0x3301
Oct 10 20:11:28 mangue mtp-probe: checking bus 5, device 41: 
"/sys/devices/pci:00/:00:1d.0/usb5/5-2"
Oct 10 20:11:28 mangue mtp-probe: bus: 5, device: 41 was not an MTP device
Oct 10 20:11:28 mangue udev-configure-printer[5977]: no corresponding CUPS 
device found
Oct 10 20:11:28 mangue systemd[1]: Started Automatic USB/Bluetooth printer 
setup (-devices-pci:00-:00:1d.0-usb5-5\x2d2).
Oct 10 20:11:28 mangue systemd[1]: printer.target: Unit not needed anymore. 
Stopping.
Oct 10 20:11:28 mangue systemd[1]: Stopped target Printer.
Oct 10 20:11:28 mangue systemd[1]: Starting Automatic USB/Bluetooth printer 
setup (-devices-pci:00-:00:1d.0-usb5-5\x2d2)...
Oct 10 20:11:28 mangue systemd[1]: Reached target Printer.
Oct 10 20:11:28 mangue udev-configure-printer[6029]: add 
/devices/pci:00/:00:1d.0/usb5/5-2
Oct 10 20:11:28 mangue udev-configure-printer[6029]: device devpath is 
/devices/pci:00/:00:1d.0/usb5/5-2
Oct 10 20:11:28 mangue udev-configure-printer[6029]: MFG:Samsung MDL:ML-1660 
Series SERN:- serial:Z5ASBDAZ809914N.

I am using Unified Linux Driver, from Samsung's HP, since the printer
was not able to print without it. After installing it, the printer was
automatically discovered and I could print one page. After that, the
printer goes automatically to disabled state. Re-enabling it does not
work, since it is disable few seconds later.

The printer used to work normally up to last week, when my computer was
still running Ubuntu 14.04 (and Samsung Linux Driver).

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

Title:
  Samsung ML-1250 prints only first job and then disconnects

Status in cups package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We have:

  lsusb
  Bus 004 Device 009: ID 04e8:300e Samsung Electronics Co., Ltd Laser Printer

  Just connected printer and started to print first job:

  tail -f /var/log/syslog
  Sep 15 14:50:18 desktop udev-configure-printer: URI matches without serial 
number: usb://Samsung/ML-1250
  Sep 15 14:50:18 desktop udev-configure-printer: No serial number URI matches 
so using those without
  Sep 15 14:50:18 desktop udev-configure-printer: URI of detected printer: 
usb://Samsung/ML-1250, normalized: samsung ml 1250
  Sep 15 14:50:18 desktop udev-configure-printer: URI of print queue: 
usb://HP/LaserJet%201200?serial=00CNCF203187, normalized: laserjet 1200 serial 
00cncf203187
  Sep 15 14:50:18 desktop udev-configure-printer: About to add queue for 
usb://Samsung/ML-1250
  Sep 15 14:50:20 desktop udev-add-printer: add_queue: 
URIs=['usb://Samsung/ML-1250']
  Sep 15 14:50:20 desktop udev-add-printer: D-Bus method call failed: 
org.freedesktop.DBus.Error.ServiceUnknown: The name 
com.redhat.NewPrinterNotification was not provided by any .service files
  Sep 15 14:50:23 desktop udev-add-printer: PPD: 
foomatic-db-compressed-ppds:0/ppd/foomatic-ppd/Samsung-ML-1250-pxlmono.ppd; 
Status: 0
  Sep 15 14:50:24 desktop colord: Profile added: ML-1250-Gray..
  Sep 15 14:50:24 desktop colord: Device added: cups-ML-1250
  Sep 15 14:53:51 desktop kernel: [22676.268686] usblp0: removed
  Sep 15 

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

[Ricardo]

** Description changed:

  The latest version of iputils have the option of using SOCK_DGRAM
  packets instead of SOCK_RAW, provided that the net.ipv4.ping_group_range
  sysctl is set to a different value.  This helps a lot with security in
  -not just- Linux containers by dropping support for the NET_RAW
  capability.
  
  Also, the ubuntu-minimal packages should not include this package as a
  hard dependency in case I want to uninstall iputils-ping to substitute
  it for another package like oping which just works if I turn off the
  setuid bit.
+ 
+ This would help a lot with secure Linux containers with no NET_RAW
+ capabilities.

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

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

Status in iputils package in Ubuntu:
  New

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

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

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

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

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

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

[Ricardo]

Public bug reported:

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

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

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

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

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

Status in iputils package in Ubuntu:
  New

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

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

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

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

[Touch-packages] [Bug 1586496] [NEW] Upgrade libseccomp library in main

[Ricardo]

Public bug reported:

We need to move the version in trusty-backports to main for Docker to
support libseccomp:

https://github.com/docker/docker/issues/22870

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

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

Title:
  Upgrade libseccomp library in main

Status in libseccomp package in Ubuntu:
  New

Bug description:
  We need to move the version in trusty-backports to main for Docker to
  support libseccomp:

  https://github.com/docker/docker/issues/22870

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1586496/+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 1580558] Re: Upgrade libseccomp from 2.2.3 ->2.3.1

[Ricardo]

This package should be moved from backports to updates to allow Docker
support for seccomp:

https://github.com/docker/docker/issues/22870#

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

Title:
  Upgrade libseccomp from 2.2.3 ->2.3.1

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in libseccomp package in Ubuntu:
  Confirmed

Bug description:
  == Comment: #1 - Heinz-Werner Seeck  - 
2016-05-11 05:09:09 ==
  Please upgrade package libseccomp.
  The new version 2.3.1 is available on github

  https://github.com/seccomp/libseccomp/releases

  == Comment: #2 - Heinz-Werner Seeck  - 
2016-05-11 05:10:59 ==
  ?Version 2.3.0 - February 29, 2016
  ?Added support for the s390 and s390x architectures
  ?Added support for the ppc, ppc64, and ppc64le architectures
  ?Update the internal syscall tables to match the Linux 4.5-rcX releases
  ?Filter generation for both multiplexed and direct socket syscalls on x86
  ?Support for the musl libc implementation
  ?Additions to the API to enable runtime version checking of the library
  ?Enable the use of seccomp() instead of prctl() on supported systems
  ?Added additional tests to the regression test suite

  ?Version 2.3.1 - April 20, 2016 
  ?Fixed a problem with 32-bit x86 socket syscalls on some systems
  ?Fixed problems with ipc syscalls on 32-bit x86
  ?Fixed problems with socket and ipc syscalls on s390 and s390x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1580558/+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 1254085] Re: ssh fails to connect to VPN host - hangs at 'expecting SSH2_MSG_KEX_ECDH_REPLY'

[Ricardo Ferreira]

Lowering MTU 1200 worked for me.

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

Title:
  ssh fails to connect to VPN host - hangs at 'expecting
  SSH2_MSG_KEX_ECDH_REPLY'

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  ssh -vvv  is failing for me where  is a VPN system.

  VPN is configured and connected via network-manager. Last messages
  from ssh (hangs forever):

  debug2: kex_parse_kexinit: none,z...@openssh.com
  debug2: kex_parse_kexinit: none,z...@openssh.com
  debug2: kex_parse_kexinit: 
  debug2: kex_parse_kexinit: 
  debug2: kex_parse_kexinit: first_kex_follows 0 
  debug2: kex_parse_kexinit: reserved 0 
  debug2: mac_setup: found hmac-md5
  debug1: kex: server->client aes128-ctr hmac-md5 none
  debug2: mac_setup: found hmac-md5
  debug1: kex: client->server aes128-ctr hmac-md5 none
  debug1: sending SSH2_MSG_KEX_ECDH_INIT
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY

  
  = Workaround =

  $ sudo apt-get install putty
  $ putty 

  This works perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: openssh-client 1:6.4p1-1
  ProcVersionSignature: Ubuntu 3.12.0-3.8-generic 3.12.0
  Uname: Linux 3.12.0-3-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.7-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Fri Nov 22 15:37:18 2013
  InstallationDate: Installed on 2010-10-21 (1128 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  RelatedPackageVersions:
   ssh-askpass   1:1.2.4.1-9
   libpam-sshN/A
   keychain  2.7.1-1
   ssh-askpass-gnome 1:6.4p1-1
  SSHClientVersion: OpenSSH_6.4p1 Ubuntu-1, OpenSSL 1.0.1e 11 Feb 2013
  SourcePackage: openssh
  UpgradeStatus: Upgraded to trusty on 2013-11-01 (20 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1254085/+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 1574338] [NEW] package click 0.4.43+16.04.20160203-0ubuntu2 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

[Ricardo Muniz]

Public bug reported:

I dont know

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: click 0.4.43+16.04.20160203-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Sun Apr 24 14:19:22 2016
ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
InstallationDate: Installed on 2016-04-21 (2 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: click
Title: package click 0.4.43+16.04.20160203-0ubuntu2 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package click 0.4.43+16.04.20160203-0ubuntu2 failed to
  install/upgrade: sub-processo script post-installation instalado
  retornou estado de saída de erro 1

Status in click package in Ubuntu:
  New

Bug description:
  I dont know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: click 0.4.43+16.04.20160203-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun Apr 24 14:19:22 2016
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  InstallationDate: Installed on 2016-04-21 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: click
  Title: package click 0.4.43+16.04.20160203-0ubuntu2 failed to 
install/upgrade: sub-processo script post-installation instalado retornou 
estado de saída de erro 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1574338/+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 1537789] Re: MAAS dhcp fails to start on up-to-date Xenial with MAAS built from source

[Ricardo Bánffy]

http://paste.ubuntu.com/14665284/ is a possible solution

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

Title:
  MAAS dhcp fails to start on  up-to-date Xenial with MAAS built from
  source

Status in MAAS:
  Triaged
Status in isc-dhcp package in Ubuntu:
  New

Bug description:

  /var/log/kern.log

  Jan 25 03:54:41 autopkgtest kernel: [  598.488307] audit: type=1400
  audit(1453712081.200:20): apparmor="DENIED" operation="capable"
  profile="/usr/sbin/dhcpd" pid=13381 comm="dhcpd" capability=0
  capname="chown"

  /var/log/syslog

  Jan 25 05:21:37 autopkgtest systemd[1]: Starting MAAS instance of ISC DHCP 
server for IPv4...
  Jan 25 05:21:37 autopkgtest systemd[1]: Started MAAS instance of ISC DHCP 
server for IPv4.
  Jan 25 05:21:37 autopkgtest dhcpd[17722]: Can't chown new lease file: 
Operation not permitted
  Jan 25 05:21:37 autopkgtest dhcpd[17722]: 
  Jan 25 05:21:37 autopkgtest dhcpd[17722]: If you think you have received this 
message due to a bug rather
  Jan 25 05:21:37 autopkgtest dhcpd[17722]: than a configuration issue please 
read the section on submitting
  Jan 25 05:21:37 autopkgtest dhcpd[17722]: bugs on either our web page at 
www.isc.org or in the README file
  Jan 25 05:21:37 autopkgtest dhcpd[17722]: before submitting a bug.  These 
pages explain the proper
  Jan 25 05:21:37 autopkgtest dhcpd[17722]: process and the information we find 
helpful for debugging..
  Jan 25 05:21:37 autopkgtest dhcpd[17722]: 
  Jan 25 05:21:37 autopkgtest dhcpd[17722]: exiting.
  Jan 25 05:21:37 autopkgtest systemd[1]: maas-dhcpd.service: Main process 
exited, code=exited, status=1/FAILURE
  Jan 25 05:21:37 autopkgtest systemd[1]: maas-dhcpd.service: Unit entered 
failed state.
  Jan 25 05:21:37 autopkgtest systemd[1]: maas-dhcpd.service: Failed with 
result 'exit-code'.

  root@autopkgtest:~# ls -l /var/lib/maas/dhcp/dhcpd.leases
  -rw-r--r-- 1 maas maas 0 Jan 25 03:54 /var/lib/maas/dhcp/dhcpd.leases

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1537789/+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 1535952] Re: isc-dhcp-server.service fails on xenial with "Can't open lease database /var/lib/dhcp/dhcpd.leases: No such file or directory"

[Ricardo Bánffy]

** Attachment added: "syslog file"
   
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1535952/+attachment/4553040/+files/syslog.bz2

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

Title:
  isc-dhcp-server.service fails on xenial with "Can't open lease
  database /var/lib/dhcp/dhcpd.leases: No such file or directory"

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  While investigating a DHCP issue on MAAS, I installed a fresh xenial
  on a LXC container and installed the isc-dhcp-server package. It fails
  to start with a syslog entry like "dhcpd[8090]: Can't open lease
  database /var/lib/dhcp/dhcpd.leases: No such file or directory --.

  From the machine:

  root@xenial-dhcp-test:~# lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  root@xenial-dhcp-test:~# dpkg -l isc* | cat
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name VersionArchitecture Description
  
+++--==--=
  ii  isc-dhcp-client  4.3.3-5ubuntu1 amd64DHCP client for 
automatically obtaining an IP address
  un  isc-dhcp-client-ddns (no description 
available)
  ii  isc-dhcp-common  4.3.3-5ubuntu1 amd64common files used by all 
of the isc-dhcp packages
  ii  isc-dhcp-server  4.3.3-5ubuntu1 amd64ISC DHCP server for 
automatic IP address assignment
  un  isc-dhcp-server-ldap (no description 
available)

  root@xenial-dhcp-test:~# systemctl status isc-dhcp-server.service
  ● isc-dhcp-server.service - ISC DHCP IPv4 server
 Loaded: loaded (/lib/systemd/system/isc-dhcp-server.service; enabled; 
vendor preset: enabled)
 Active: failed (Result: exit-code) since Tue 2016-01-19 23:43:40 UTC; 6min 
ago
   Docs: man:dhcpd(8)
Process: 8090 ExecStart=/bin/sh -ec  CONFIG_FILE=/etc/dhcp/dhcpd.conf;  
if [ -f /etc/ltsp/dhcpd.conf ]; then CONFIG_FILE=/etc/ltsp/dhcpd.conf; fi;  
exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid 
-cf $CONFIG_FILE $INTERFACES (code=exited, status=1/FAILURE)
Process: 8081 ExecStartPre=/bin/chown dhcpd:dhcpd /run/dhcp-server 
(code=exited, status=0/SUCCESS)
   Main PID: 8090 (code=exited, status=1/FAILURE)

  Jan 19 23:43:40 xenial-dhcp-test sh[8090]: Can't open lease database 
/var/lib/dhcp/dhcpd.leases: No suc...y --
  Jan 19 23:43:40 xenial-dhcp-test sh[8090]: check for failed database rewrite 
attempt!
  Jan 19 23:43:40 xenial-dhcp-test sh[8090]: Please read the dhcpd.leases 
manual page if you
  Jan 19 23:43:40 xenial-dhcp-test sh[8090]: don't know what to do about this.
  Jan 19 23:43:40 xenial-dhcp-test sh[8090]: If you think you have received 
this message due to a bug rather
  Jan 19 23:43:40 xenial-dhcp-test sh[8090]: than a configuration issue please 
read the section on submitting
  Jan 19 23:43:40 xenial-dhcp-test sh[8090]: bugs on either our web page at 
www.isc.org or in the README file
  Jan 19 23:43:40 xenial-dhcp-test sh[8090]: before submitting a bug.  These 
pages explain the proper
  Jan 19 23:43:40 xenial-dhcp-test sh[8090]: process and the information we 
find helpful for debugging..
  Jan 19 23:43:40 xenial-dhcp-test sh[8090]: exiting.
  Hint: Some lines were ellipsized, use -l to show in full.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1535952/+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 1535952] Re: isc-dhcp-server.service fails on xenial with "Can't open lease database /var/lib/dhcp/dhcpd.leases: No such file or directory"

[Ricardo Bánffy]

I'm unable to attach a file to this report, so I'll transcribe the
relevant lines from syslog:

Jan 20 00:25:08 xenial-dhcp-test systemd[1]: Starting ISC DHCP IPv4 server...
Jan 20 00:25:08 xenial-dhcp-test systemd[1]: Started ISC DHCP IPv4 server.
Jan 20 00:25:09 xenial-dhcp-test dhcpd[8186]: Internet Systems Consortium DHCP 
Server 4.3.3
Jan 20 00:25:09 xenial-dhcp-test dhcpd[8186]: Copyright 2004-2015 Internet 
Systems Consortium.
Jan 20 00:25:09 xenial-dhcp-test dhcpd[8186]: All rights reserved.
Jan 20 00:25:09 xenial-dhcp-test dhcpd[8186]: For info, please visit 
https://www.isc.org/software/dhcp/
Jan 20 00:25:09 xenial-dhcp-test dhcpd[8186]: Config file: /etc/dhcp/dhcpd.conf
Jan 20 00:25:09 xenial-dhcp-test dhcpd[8186]: Database file: 
/var/lib/dhcp/dhcpd.leases
Jan 20 00:25:09 xenial-dhcp-test dhcpd[8186]: PID file: 
/run/dhcp-server/dhcpd.pid
Jan 20 00:25:09 xenial-dhcp-test dhcpd[8186]: Internet Systems Consortium DHCP 
Server 4.3.3
Jan 20 00:25:09 xenial-dhcp-test dhcpd[8186]: Copyright 2004-2015 Internet 
Systems Consortium.
Jan 20 00:25:09 xenial-dhcp-test dhcpd[8186]: All rights reserved.
Jan 20 00:25:09 xenial-dhcp-test dhcpd[8186]: For info, please visit 
https://www.isc.org/software/dhcp/
Jan 20 00:25:09 xenial-dhcp-test dhcpd[8186]: Can't open lease database 
/var/lib/dhcp/dhcpd.leases: No such file or directory --
Jan 20 00:25:09 xenial-dhcp-test dhcpd[8186]:   check for failed database 
rewrite attempt!
Jan 20 00:25:09 xenial-dhcp-test dhcpd[8186]: Please read the dhcpd.leases 
manual page if you
Jan 20 00:25:09 xenial-dhcp-test dhcpd[8186]: don't know what to do about this.
Jan 20 00:25:09 xenial-dhcp-test systemd[1]: isc-dhcp-server.service: Main 
process exited, code=exited, status=1/FAILURE
Jan 20 00:25:09 xenial-dhcp-test dhcpd[8186]: 
Jan 20 00:25:09 xenial-dhcp-test dhcpd[8186]: If you think you have received 
this message due to a bug rather
Jan 20 00:25:09 xenial-dhcp-test dhcpd[8186]: than a configuration issue please 
read the section on submitting
Jan 20 00:25:09 xenial-dhcp-test dhcpd[8186]: bugs on either our web page at 
www.isc.org or in the README file
Jan 20 00:25:09 xenial-dhcp-test dhcpd[8186]: before submitting a bug.  These 
pages explain the proper
Jan 20 00:25:09 xenial-dhcp-test dhcpd[8186]: process and the information we 
find helpful for debugging..
Jan 20 00:25:09 xenial-dhcp-test dhcpd[8186]: 
Jan 20 00:25:09 xenial-dhcp-test dhcpd[8186]: exiting.
Jan 20 00:25:09 xenial-dhcp-test sh[8186]: Internet Systems Consortium DHCP 
Server 4.3.3
Jan 20 00:25:09 xenial-dhcp-test sh[8186]: Copyright 2004-2015 Internet Systems 
Consortium.
Jan 20 00:25:09 xenial-dhcp-test sh[8186]: All rights reserved.
Jan 20 00:25:09 xenial-dhcp-test sh[8186]: For info, please visit 
https://www.isc.org/software/dhcp/
Jan 20 00:25:09 xenial-dhcp-test sh[8186]: Config file: /etc/dhcp/dhcpd.conf
Jan 20 00:25:09 xenial-dhcp-test sh[8186]: Database file: 
/var/lib/dhcp/dhcpd.leases
Jan 20 00:25:09 xenial-dhcp-test sh[8186]: PID file: /run/dhcp-server/dhcpd.pid
Jan 20 00:25:09 xenial-dhcp-test sh[8186]: Can't open lease database 
/var/lib/dhcp/dhcpd.leases: No such file or directory --
Jan 20 00:25:09 xenial-dhcp-test sh[8186]: check for failed database rewrite 
attempt!
Jan 20 00:25:09 xenial-dhcp-test sh[8186]: Please read the dhcpd.leases manual 
page if you
Jan 20 00:25:09 xenial-dhcp-test sh[8186]: don't know what to do about this.
Jan 20 00:25:09 xenial-dhcp-test sh[8186]: If you think you have received this 
message due to a bug rather
Jan 20 00:25:09 xenial-dhcp-test sh[8186]: than a configuration issue please 
read the section on submitting
Jan 20 00:25:09 xenial-dhcp-test sh[8186]: bugs on either our web page at 
www.isc.org or in the README file
Jan 20 00:25:09 xenial-dhcp-test sh[8186]: before submitting a bug.  These 
pages explain the proper
Jan 20 00:25:09 xenial-dhcp-test sh[8186]: process and the information we find 
helpful for debugging..
Jan 20 00:25:09 xenial-dhcp-test sh[8186]: exiting.
Jan 20 00:25:09 xenial-dhcp-test systemd[1]: isc-dhcp-server.service: Failed to 
kill control group /lxc/xenial-dhcp-test/system.slice/isc-dhcp-server.service, 
ignoring: Invalid argument
Jan 20 00:25:09 xenial-dhcp-test systemd[1]: message repeated 3 times: [ 
isc-dhcp-server.service: Failed to kill control group 
/lxc/xenial-dhcp-test/system.slice/isc-dhcp-server.service, ignoring: Invalid 
argument]
Jan 20 00:25:09 xenial-dhcp-test systemd[1]: isc-dhcp-server.service: Unit 
entered failed state.
Jan 20 00:25:09 xenial-dhcp-test systemd[1]: isc-dhcp-server.service: Failed 
with result 'exit-code'.

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

Title:
  isc-dhcp-server.service fails on xenial with "Can't open lease
  database /var/lib/dhcp/dhcpd.leases: No such file or directory"

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  While 

[Touch-packages] [Bug 1535952] [NEW] isc-dhcp-server.service fails on xenial with "Can't open lease database /var/lib/dhcp/dhcpd.leases: No such file or directory"

[Ricardo Bánffy]

Public bug reported:

While investigating a DHCP issue on MAAS, I installed a fresh xenial on
a LXC container and installed the isc-dhcp-server package. It fails to
start with a syslog entry like "dhcpd[8090]: Can't open lease database
/var/lib/dhcp/dhcpd.leases: No such file or directory --.

>From the machine:

root@xenial-dhcp-test:~# lsb_release -rd
Description:Ubuntu Xenial Xerus (development branch)
Release:16.04

root@xenial-dhcp-test:~# dpkg -l isc* | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name VersionArchitecture Description
+++--==--=
ii  isc-dhcp-client  4.3.3-5ubuntu1 amd64DHCP client for 
automatically obtaining an IP address
un  isc-dhcp-client-ddns (no description available)
ii  isc-dhcp-common  4.3.3-5ubuntu1 amd64common files used by all 
of the isc-dhcp packages
ii  isc-dhcp-server  4.3.3-5ubuntu1 amd64ISC DHCP server for 
automatic IP address assignment
un  isc-dhcp-server-ldap (no description available)

root@xenial-dhcp-test:~# systemctl status isc-dhcp-server.service
● isc-dhcp-server.service - ISC DHCP IPv4 server
   Loaded: loaded (/lib/systemd/system/isc-dhcp-server.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Tue 2016-01-19 23:43:40 UTC; 6min 
ago
 Docs: man:dhcpd(8)
  Process: 8090 ExecStart=/bin/sh -ec  CONFIG_FILE=/etc/dhcp/dhcpd.conf;
  if [ -f /etc/ltsp/dhcpd.conf ]; then CONFIG_FILE=/etc/ltsp/dhcpd.conf; fi;
  exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf 
$CONFIG_FILE $INTERFACES (code=exited, status=1/FAILURE)
  Process: 8081 ExecStartPre=/bin/chown dhcpd:dhcpd /run/dhcp-server 
(code=exited, status=0/SUCCESS)
 Main PID: 8090 (code=exited, status=1/FAILURE)

Jan 19 23:43:40 xenial-dhcp-test sh[8090]: Can't open lease database 
/var/lib/dhcp/dhcpd.leases: No suc...y --
Jan 19 23:43:40 xenial-dhcp-test sh[8090]: check for failed database rewrite 
attempt!
Jan 19 23:43:40 xenial-dhcp-test sh[8090]: Please read the dhcpd.leases manual 
page if you
Jan 19 23:43:40 xenial-dhcp-test sh[8090]: don't know what to do about this.
Jan 19 23:43:40 xenial-dhcp-test sh[8090]: If you think you have received this 
message due to a bug rather
Jan 19 23:43:40 xenial-dhcp-test sh[8090]: than a configuration issue please 
read the section on submitting
Jan 19 23:43:40 xenial-dhcp-test sh[8090]: bugs on either our web page at 
www.isc.org or in the README file
Jan 19 23:43:40 xenial-dhcp-test sh[8090]: before submitting a bug.  These 
pages explain the proper
Jan 19 23:43:40 xenial-dhcp-test sh[8090]: process and the information we find 
helpful for debugging..
Jan 19 23:43:40 xenial-dhcp-test sh[8090]: exiting.
Hint: Some lines were ellipsized, use -l to show in full.

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  isc-dhcp-server.service fails on xenial with "Can't open lease
  database /var/lib/dhcp/dhcpd.leases: No such file or directory"

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  While investigating a DHCP issue on MAAS, I installed a fresh xenial
  on a LXC container and installed the isc-dhcp-server package. It fails
  to start with a syslog entry like "dhcpd[8090]: Can't open lease
  database /var/lib/dhcp/dhcpd.leases: No such file or directory --.

  From the machine:

  root@xenial-dhcp-test:~# lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  root@xenial-dhcp-test:~# dpkg -l isc* | cat
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name VersionArchitecture Description
  
+++--==--=
  ii  isc-dhcp-client  4.3.3-5ubuntu1 amd64DHCP client for 
automatically obtaining an IP address
  un  isc-dhcp-client-ddns (no description 
available)
  ii  isc-dhcp-common  4.3.3-5ubuntu1 amd64common files used by all 
of the isc-dhcp packages
  ii  isc-dhcp-server  4.3.3-5ubuntu1 amd64ISC DHCP server for 
automatic IP address assignment
  un  isc-dhcp-server-ldap (no description 
available)

  root@xenial-dhcp-test:~# systemctl status isc-dhcp-server.service
  ● isc-dhcp-server.service - ISC DHCP IPv4 server
 Loaded: loaded 

[Touch-packages] [Bug 1509558] Re: package tzdata 2015g-0ubuntu0.14.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[ricardo cartoceti]

No actualiza Ubuntu ni permite instalar software nuevo. Siempre entrega
el mismo error de tzdata (retorno error 2) y no puedo salvar este
problema.

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

Title:
  package tzdata 2015g-0ubuntu0.14.04 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in tzdata package in Ubuntu:
  Confirmed

Bug description:
  Cannot install new softwares

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: tzdata 2015g-0ubuntu0.14.04
  ProcVersionSignature: Ubuntu 3.19.0-28.30~14.04.1-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: amd64
  Date: Fri Oct 23 17:06:56 2015
  DuplicateSignature: package:tzdata:2015g-0ubuntu0.14.04:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-08-28 (56 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.4
   apt  1.0.1ubuntu2.10
  SourcePackage: tzdata
  Title: package tzdata 2015g-0ubuntu0.14.04 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1509558/+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 1514072] [NEW] package tzdata 2015g-0ubuntu0.14.04 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 2

[ricardo cartoceti]

Public bug reported:

i tried to uninstall flashplugin.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: tzdata 2015g-0ubuntu0.14.04
ProcVersionSignature: Ubuntu 3.16.0-50.66~14.04.1-generic 3.16.7-ckt16
Uname: Linux 3.16.0-50-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.15
AptOrdering:
 tzdata: Configure
 flashplugin-installer: Purge
 libpam-systemd: Configure
 man-db: Configure
Architecture: i386
Date: Sat Nov  7 11:00:40 2015
DuplicateSignature: package:tzdata:2015g-0ubuntu0.14.04:el subproceso instalado 
el script post-installation devolvió el código de salida de error 2
ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 2
InstallationDate: Installed on 2015-09-23 (44 days ago)
InstallationMedia: It
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.4
 apt  1.0.1ubuntu2.10
SourcePackage: tzdata
Title: package tzdata 2015g-0ubuntu0.14.04 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 need-duplicate-check trusty

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

Title:
  package tzdata 2015g-0ubuntu0.14.04 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 2

Status in tzdata package in Ubuntu:
  New

Bug description:
  i tried to uninstall flashplugin.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: tzdata 2015g-0ubuntu0.14.04
  ProcVersionSignature: Ubuntu 3.16.0-50.66~14.04.1-generic 3.16.7-ckt16
  Uname: Linux 3.16.0-50-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.15
  AptOrdering:
   tzdata: Configure
   flashplugin-installer: Purge
   libpam-systemd: Configure
   man-db: Configure
  Architecture: i386
  Date: Sat Nov  7 11:00:40 2015
  DuplicateSignature: package:tzdata:2015g-0ubuntu0.14.04:el subproceso 
instalado el script post-installation devolvió el código de salida de error 2
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 2
  InstallationDate: Installed on 2015-09-23 (44 days ago)
  InstallationMedia: It
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.4
   apt  1.0.1ubuntu2.10
  SourcePackage: tzdata
  Title: package tzdata 2015g-0ubuntu0.14.04 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1514072/+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 1509742] [NEW] package systemd-sysv 219-7ubuntu6 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv

[Ricardo]

Public bug reported:

:)

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: systemd-sysv (not installed)
ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26
Uname: Linux 3.13.0-65-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
Date: Sat Oct 24 21:57:00 2015
DuplicateSignature: package:systemd-sysv:219-7ubuntu6:pre-dependency problem - 
not installing systemd-sysv
ErrorMessage: pre-dependency problem - not installing systemd-sysv
InstallationDate: Installed on 2015-09-30 (24 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt  1.0.9.7ubuntu4.2
SourcePackage: systemd
Title: package systemd-sysv 219-7ubuntu6 failed to install/upgrade: 
pre-dependency problem - not installing systemd-sysv
UpgradeStatus: Upgraded to vivid on 2015-10-25 (0 days ago)

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


** Tags: amd64 apport-package dist-upgrade need-duplicate-check

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

Title:
  package systemd-sysv 219-7ubuntu6 failed to install/upgrade: pre-
  dependency problem - not installing systemd-sysv

Status in systemd package in Ubuntu:
  New

Bug description:
  :)

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: systemd-sysv (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26
  Uname: Linux 3.13.0-65-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  Date: Sat Oct 24 21:57:00 2015
  DuplicateSignature: package:systemd-sysv:219-7ubuntu6:pre-dependency problem 
- not installing systemd-sysv
  ErrorMessage: pre-dependency problem - not installing systemd-sysv
  InstallationDate: Installed on 2015-09-30 (24 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.2
  SourcePackage: systemd
  Title: package systemd-sysv 219-7ubuntu6 failed to install/upgrade: 
pre-dependency problem - not installing systemd-sysv
  UpgradeStatus: Upgraded to vivid on 2015-10-25 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1509742/+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 1502717] [NEW] wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch()

[Ricardo Salveti]

Public bug reported:

wpa_supplicant crashed with SIGSEGV when removing kernel module
brcmfmac.

rsalveti@evapro:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Wily Werewolf (development branch)
Release:15.10
Codename:   wily

Linux evapro 4.2.0-14-generic #16-Ubuntu SMP Fri Oct 2 05:14:57 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux

MacBook Pro Retina 13' 12,1

43557 Oct  4 18:02:56 evapro kernel: [   86.406354] usbcore: deregistering 
interface driver brcmfmac
43558 Oct  4 18:02:57 evapro avahi-daemon[950]: Withdrawing workstation service 
for wlp3s0.
43559 Oct  4 18:02:57 evapro NetworkManager[936]:   devices removed 
(path: /sys/devices/pci:00/:00:1c.2/:03:00.0/net/wlp3s0, iface: 
wlp3s0)
43560 Oct  4 18:02:57 evapro NetworkManager[936]:   (wlp3s0): device 
state change: disconnected -> unmanaged (reason 'removed') [30 10 36]
43561 Oct  4 18:02:57 evapro NetworkManager[936]:   (wlp3s0): failed to 
disable userspace IPv6LL address handling
43562 Oct  4 18:02:57 evapro gnome-session[2190]: (nm-applet:2346): 
GLib-CRITICAL **: Source ID 190 was not found when attempting to remove it
43563 Oct  4 18:02:57 evapro NetworkManager[936]:   radio killswitch 
/sys/devices/pci:00/:00:1c.2/:03:00.0/ieee80211/phy0/rfkill0 
disappeared
43564 Oct  4 18:02:57 evapro kernel: [   86.947963] show_signal_msg: 39 
callbacks suppressed
43565 Oct  4 18:02:57 evapro kernel: [   86.947968] wpa_supplicant[1330]: 
segfault at 0 ip 7f835170fcba sp 7fffc00140c8 error 4 in 
libc-2.21.so[7f835167+1c]
43566 Oct  4 18:02:57 evapro NetworkManager[936]:   wpa_supplicant stopped
43567 Oct  4 18:02:57 evapro NetworkManager[936]:   (wlx048d38ab601a): 
supplicant interface state: completed -> down
43568 Oct  4 18:02:57 evapro NetworkManager[936]: (NetworkManager:936): 
GLib-CRITICAL **: Source ID 167 was not found when attempting to remove it
43569 Oct  4 18:02:57 evapro NetworkManager[936]:   Failed to 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.30 was not 
provided by any .service files: remove network.
43570 Oct  4 18:02:57 evapro dbus[969]: [system] Activating via systemd: 
service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service'
43571 Oct  4 18:02:57 evapro NetworkManager[936]:   (wlx048d38ab601a): 
device state change: activated -> unavailable (reason 'supplicant-failed') [100 
20 10]
43572 Oct  4 18:02:57 evapro systemd[1]: Started WPA supplicant.
43573 Oct  4 18:02:57 evapro NetworkManager[936]:   (wlx048d38ab601a): 
canceled DHCP transaction, DHCP client pid 1915
43574 Oct  4 18:02:57 evapro NetworkManager[936]:   (wlx048d38ab601a): 
DHCPv4 state changed bound -> done
43575 Oct  4 18:02:57 evapro avahi-daemon[950]: Withdrawing address record for 
192.168.1.17 on wlx048d38ab601a.
43576 Oct  4 18:02:57 evapro avahi-daemon[950]: Leaving mDNS multicast group on 
interface wlx048d38ab601a.IPv4 with address 192.168.1.17.
43577 Oct  4 18:02:57 evapro avahi-daemon[950]: Interface wlx048d38ab601a.IPv4 
no longer relevant for mDNS.
43578 Oct  4 18:02:57 evapro avahi-daemon[950]: Withdrawing address record for 
fe80::68d:38ff:feab:601a on wlx048d38ab601a.
43579 Oct  4 18:02:57 evapro avahi-daemon[950]: Leaving mDNS multicast group on 
interface wlx048d38ab601a.IPv6 with address fe80::68d:38ff:feab:601a.
43580 Oct  4 18:02:57 evapro avahi-daemon[950]: Interface wlx048d38ab601a.IPv6 
no longer relevant for mDNS.
43581 Oct  4 18:02:57 evapro NetworkManager[936]:   Writing DNS 
information to /sbin/resolvconf
43582 Oct  4 18:02:57 evapro dnsmasq[1607]: setting upstream servers from DBus
43583 Oct  4 18:02:57 evapro dnsmasq[1607]: using nameserver 
fe80::e6f4:c6ff:fe0b:5c4d#53
43584 Oct  4 18:02:57 evapro whoopsie[994]: [18:02:57] Cannot reach: 
https://daisy.ubuntu.com
43585 Oct  4 18:02:57 evapro whoopsie[994]: [18:02:57] offline
43586 Oct  4 18:02:57 evapro whoopsie[994]: [18:02:57] Cannot reach: 
https://daisy.ubuntu.com
43587 Oct  4 18:02:57 evapro NetworkManager[936]:   Writing DNS 
information to /sbin/resolvconf
43588 Oct  4 18:02:57 evapro dnsmasq[1607]: setting upstream servers from DBus
43589 Oct  4 18:02:57 evapro NetworkManager[936]:   NetworkManager state 
is now CONNECTED_LOCAL
43590 Oct  4 18:02:57 evapro NetworkManager[936]:   NetworkManager state 
is now DISCONNECTED
43591 Oct  4 18:02:57 evapro nm-dispatcher: Dispatching action 'down' for 
wlx048d38ab601a
43592 Oct  4 18:02:57 evapro systemd[1]: wpa_supplicant.service: Main process 
exited, code=dumped, status=11/SEGV
43593 Oct  4 18:02:57 evapro systemd[1]: wpa_supplicant.service: Unit entered 
failed state.
43594 Oct  4 18:02:57 evapro systemd[1]: wpa_supplicant.service: Failed with 
result 'core-dump'.
43595 Oct  4 18:02:58 evapro gnome-session[2190]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
43596 Oct  4 18:02:58 evapro org.freedesktop.Notifications[2012]: ** Message: 
resizing pixbuf to 44

ProblemType: Crash

Re: [Touch-packages] [Bug 1458694] Re: [vivid-overlay] unity8 fails to start on the emulator

[Ricardo Salveti]

On Fri, Aug 21, 2015 at 6:52 AM, Timo Jyrinki
timo.jyri...@canonical.com wrote:
 As per QA report:
 Needs a fix in unity8 so we can get past edges demo and confirm there are no 
 further issues with the silo before landing.

Sorry, but why do we need to disable the edge demo? It's still useful
during the first boot. If needed we could extend the flashing tool to
offer an option for that.

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

Title:
  [vivid-overlay] unity8 fails to start on the emulator

Status in Canonical System Image:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed
Status in unity8 package in Ubuntu:
  Fix Committed

Bug description:
  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 140
  device name: generic_x86
  channel: ubuntu-touch/rc-proposed/ubuntu
  last update: 2015-05-25 12:02:10
  version version: 140
  version ubuntu: 20150525
  version device: 20150210
  version custom: 20150525

  When starting unity8 (this started at image 136, probably when mir
  0.13 landed):

  phablet@ubuntu-phablet:~$ cat ./.cache/upstart/unity8.log
  ()
  [1432595001.896139] mirplatform: Found graphics driver: dummy
  [1432595001.898447] mirplatform: Found graphics driver: android
  qtmir.mir: MirServer created
  [1432595003.675225] Server: Starting
  [1432595003.679331] Loader: Loading modules from: 
/usr/lib/i386-linux-gnu/mir/server-platform
  [1432595003.679501] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/graphics-dummy.so
  [1432595003.680673] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so
  [1432595003.681107] WARNING Loader: Failed to load module: 
/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so (error 
was:/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so: undefined 
symbol: _ZN3mir6events10make_eventExx17MirKeyboardActionjij)
  [1432595003.684868] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/graphics-android.so.2
  [1432595003.685014] mirplatform: Found graphics driver: dummy
  [1432595003.685211] mirplatform: Found graphics driver: android
  [1432595003.685416] Platform Loader: Selected driver: android (version 0.13.0)
  qtmir.mir: PromptSessionListener::PromptSessionListener - this= 
PromptSessionListener(0x9679764)
  qtmir.mir: SessionListener::SessionListener - this= SessionListener(0x9676d24)
  qtmir.mir: MirShell::MirShell
  [1432595003.883766] DisplayServer: Mir version 0.13.0
  QtCompositor::setAllWindowsExposed true
  qtmir.clipboard: D-Bus registration successful.
  Mode argument was not provided or was set to an illegal value. Using default 
value of --mode= full-greeter
  Cannot create window: no screens available

  With version 135 it starts fine, but not fully functional, giving this
  error:

  QOpenGLShader::compile(Fragment): 0:2(12): warning: extension 
`GL_OES_standard_derivatives' unsupported in fragment shader
  0:2(1): error: #extension directive is not allowed in the middle of a shader

  *** Problematic Fragment shader source code ***
  #extension GL_OES_standard_derivatives : enable  // Enable dFdy() on OpenGL 
ES 2.
  #define lowp
  #define mediump
  #define highp

  // Copyright © 2015 Canonical Ltd.
  //
  // This program is free software; you can redistribute it and/or modify
  // it under the terms of the GNU Lesser General Public License as published by
  // the Free Software Foundation; version 3.
  //
  // This program is distributed in the hope that it will be useful,
  // but WITHOUT ANY WARRANTY; without even the implied warranty of
  // MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  // GNU Lesser General Public License for more details.
  //
  // You should have received a copy of the GNU Lesser General Public License
  // along with this program.  If not, see http://www.gnu.org/licenses/.
  //
  // Author: Loïc Molinari loic.molin...@canonical.com

  // Static flow control (branching on a uniform value) is fast on most GPUs 
(including ultra-low
  // power ones) because it allows to use the same shader execution path for an 
entire draw call. We
  // rely on that technique here (also known as uber-shader solution) to 
avoid the complexity of
  // dealing with a multiple shaders solution.
  // FIXME(loicm) Validate GPU behavior with regards to static flow control.

  uniform sampler2D shapeTexture;
  uniform sampler2D sourceTexture;
  uniform lowp vec2 dfdtFactors;
  uniform lowp vec2 opacityFactors;
  uniform lowp float sourceOpacity;
  uniform lowp float distanceAA;
  uniform bool textured;
  uniform mediump int aspect;

  varying mediump vec2 shapeCoord;
  varying mediump vec4 sourceCoord;
  varying lowp vec4 backgroundColor;

  const mediump int FLAT  = 0x08;  // 1  3
  const mediump int INSET = 0x10;  // 1  4

  void main(void)
  {
  lowp 

[Touch-packages] [Bug 1485942] [NEW] package openssh-client 1:6.7p1-5ubuntu1.2 failed to install/upgrade: package openssh-client is not ready for configuration cannot configure (current status `half-i

[Ricardo Maltez]

Public bug reported:

When trying to install gstreamer0.10-ffmpeg I have receive a error about 
openssh-client (Errors were encountered while processing:
 openssh-client) so I try to install openssh-client, with sudo apt-get install 
openssh-client, that's when I had receive the bug report dialog

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: openssh-client 1:6.7p1-5ubuntu1.2
ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.17.2-0ubuntu1.2
AptOrdering:
 gstreamer0.10-ffmpeg: Install
 openssh-client: Configure
 gstreamer0.10-ffmpeg: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Tue Aug 18 10:22:12 2015
DpkgTerminalLog:
 Preparing to unpack .../gstreamer0.10-ffmpeg_0.10.13-5ubuntu1~vivid_amd64.deb 
...
 Unpacking gstreamer0.10-ffmpeg:amd64 (0.10.13-5ubuntu1~vivid) ...
 dpkg: error processing package openssh-client (--configure):
  package openssh-client is not ready for configuration
  cannot configure (current status `half-installed')
DuplicateSignature: package:openssh-client:1:6.7p1-5ubuntu1.2:package 
openssh-client is not ready for configuration  cannot configure (current status 
`half-installed')
ErrorMessage: package openssh-client is not ready for configuration  cannot 
configure (current status `half-installed')
InstallationDate: Installed on 2015-05-02 (108 days ago)
InstallationMedia: It
RelatedPackageVersions:
 ssh-askpass   N/A
 libpam-sshN/A
 keychain  N/A
 ssh-askpass-gnome 1:6.7p1-5ubuntu1
SSHClientVersion: OpenSSH_6.7p1 Ubuntu-5ubuntu1.2, OpenSSL 1.0.1f 6 Jan 2014
SourcePackage: openssh
Title: package openssh-client 1:6.7p1-5ubuntu1.2 failed to install/upgrade: 
package openssh-client is not ready for configuration  cannot configure 
(current status `half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check vivid

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

Title:
  package openssh-client 1:6.7p1-5ubuntu1.2 failed to install/upgrade:
  package openssh-client is not ready for configuration  cannot
  configure (current status `half-installed')

Status in openssh package in Ubuntu:
  New

Bug description:
  When trying to install gstreamer0.10-ffmpeg I have receive a error about 
openssh-client (Errors were encountered while processing:
   openssh-client) so I try to install openssh-client, with sudo apt-get 
install openssh-client, that's when I had receive the bug report dialog

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: openssh-client 1:6.7p1-5ubuntu1.2
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.17.2-0ubuntu1.2
  AptOrdering:
   gstreamer0.10-ffmpeg: Install
   openssh-client: Configure
   gstreamer0.10-ffmpeg: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Aug 18 10:22:12 2015
  DpkgTerminalLog:
   Preparing to unpack 
.../gstreamer0.10-ffmpeg_0.10.13-5ubuntu1~vivid_amd64.deb ...
   Unpacking gstreamer0.10-ffmpeg:amd64 (0.10.13-5ubuntu1~vivid) ...
   dpkg: error processing package openssh-client (--configure):
package openssh-client is not ready for configuration
cannot configure (current status `half-installed')
  DuplicateSignature: package:openssh-client:1:6.7p1-5ubuntu1.2:package 
openssh-client is not ready for configuration  cannot configure (current status 
`half-installed')
  ErrorMessage: package openssh-client is not ready for configuration  cannot 
configure (current status `half-installed')
  InstallationDate: Installed on 2015-05-02 (108 days ago)
  InstallationMedia: It
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome 1:6.7p1-5ubuntu1
  SSHClientVersion: OpenSSH_6.7p1 Ubuntu-5ubuntu1.2, OpenSSL 1.0.1f 6 Jan 2014
  SourcePackage: openssh
  Title: package openssh-client 1:6.7p1-5ubuntu1.2 failed to install/upgrade: 
package openssh-client is not ready for configuration  cannot configure 
(current status `half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1485942/+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 1460152] Re: apparmor cache not updated when apparmor.d rules change (breaks 15.04/stable - 15.04/edge updates)

[Ricardo Salveti]

** Changed in: snappy/15.04
   Status: Fix Committed = Fix Released

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

Title:
  apparmor cache not updated when apparmor.d rules change (breaks
  15.04/stable - 15.04/edge updates)

Status in Snappy:
  Fix Released
Status in Snappy 15.04 series:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  The apparmor cache gets confused easily on upgrade.

  Here is what happens:
  - boot stable, /etc/apparmor.d/cache/usr.bin.ubuntu-core-launcher is mtime of 
now because we generate the cache on boot
  - upgrade to edge, /etc/apparmor.d/usr.bin.ubuntu-core-launcher is updated 
and has the mtime of T (yesterday) when the file was put into the package
  - on the next reboot the apparmor_parser compares the mtime of the 
cache/usr.bin.ubuntu-core-launcher (very very recent) with the mtime of the 
souce usr.bin.ubuntu-core-launcher (much older)
  - cache does is *not* re-generate

  Possible solution:
  - clear cache on upgrade
  - make apparmor_parser store mtime of the source file in the header
  - make apparmor_parser use set the cache file to the mtime of the source file 
used to generate the cache and re-generate if those get out-of-sync

  Original description:
  --

  Rick Spencer ran into the situation that he ended up with a snappy image that 
gave the following error:
  
  apparmor=DENIED operation=mkdir profile=/usr/bin/ubuntu-core-launcher 
name=/tmp/snap.0_pastebinit.mvo_em33Zz/ pid=1092 comm=ubuntu-core-lau 
requested_mask=c denied_mask=c fsuid=0 ouid=0
  

  Running:
  $ sudo apparmor_parser --skip-cache -r 
/etc/apparmor.d/usr.bin.ubuntu-core-launcher
  fixes it.

  This strongly indicates that the cache has the old content and did not
  get re-generated on upgrade or image build.

  I also managed to reproduce this via:
  15.04/stable-15.04/edge

  The image is here:
  https://drive.google.com/open?id=0B1sb5ymdUGiLa0tUR0pGV3lzR1kauthuser=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1460152/+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 1460152] Re: apparmor cache not updated when apparmor.d rules change (breaks 15.04/stable - 15.04/edge updates)

[Ricardo Salveti]

** Changed in: snappy/15.04
   Status: Fix Released = Fix Committed

** Changed in: snappy/15.04
Milestone: 15.04.1 = 15.04.2

** Changed in: snappy
   Status: Fix Committed = Fix Released

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

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

Title:
  apparmor cache not updated when apparmor.d rules change (breaks
  15.04/stable - 15.04/edge updates)

Status in Snappy Ubuntu:
  Fix Released
Status in Snappy 15.04 series:
  Fix Committed
Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  The apparmor cache gets confused easily on upgrade.

  Here is what happens:
  - boot stable, /etc/apparmor.d/cache/usr.bin.ubuntu-core-launcher is mtime of 
now because we generate the cache on boot
  - upgrade to edge, /etc/apparmor.d/usr.bin.ubuntu-core-launcher is updated 
and has the mtime of T (yesterday) when the file was put into the package
  - on the next reboot the apparmor_parser compares the mtime of the 
cache/usr.bin.ubuntu-core-launcher (very very recent) with the mtime of the 
souce usr.bin.ubuntu-core-launcher (much older)
  - cache does is *not* re-generate

  Possible solution:
  - clear cache on upgrade
  - make apparmor_parser store mtime of the source file in the header
  - make apparmor_parser use set the cache file to the mtime of the source file 
used to generate the cache and re-generate if those get out-of-sync

  Original description:
  --

  Rick Spencer ran into the situation that he ended up with a snappy image that 
gave the following error:
  
  apparmor=DENIED operation=mkdir profile=/usr/bin/ubuntu-core-launcher 
name=/tmp/snap.0_pastebinit.mvo_em33Zz/ pid=1092 comm=ubuntu-core-lau 
requested_mask=c denied_mask=c fsuid=0 ouid=0
  

  Running:
  $ sudo apparmor_parser --skip-cache -r 
/etc/apparmor.d/usr.bin.ubuntu-core-launcher
  fixes it.

  This strongly indicates that the cache has the old content and did not
  get re-generated on upgrade or image build.

  I also managed to reproduce this via:
  15.04/stable-15.04/edge

  The image is here:
  https://drive.google.com/open?id=0B1sb5ymdUGiLa0tUR0pGV3lzR1kauthuser=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1460152/+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 1458681] Re: [gst-hybris] FTBFS in wily/vivid (armhf/i386)

[Ricardo Salveti]

On Mon, Jun 15, 2015 at 11:56 AM, Iain Lane i...@orangesquash.org.uk wrote:
 Requires: mirclient on data/ubuntu-platform-api.pc.in is needed on the
 platform-api side I think

 gst-plugins-bad1.0 needs updating to use platform-api's CFLAGS and LIBS
 from pkg-config.

Right, that once we're able to build platform-api again :-)

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

Title:
  [gst-hybris] FTBFS in wily/vivid (armhf/i386)

Status in gst-plugins-bad1.0 package in Ubuntu:
  New
Status in platform-api package in Ubuntu:
  New

Bug description:
  When building gst-plugins-bad1.0 1.4.5-1ubuntu3

  ...
  /bin/bash ../../libtool  --tag=CC --tag=disable-static  --mode=compile gcc 
-std=gnu99 -DHAVE_CONFIG_H -I. -I../..   -D_FORTIFY_SOURCE=2 -I../../gst-libs 
-I../../gst-libs -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/i386-linux-gnu/glib-2.0/include  -pthread 
-I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/i386-linux-gnu/glib-2.0/include  -pthread 
-I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/i386-linux-gnu/glib-2.0/include  -pthread 
-I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/i386-linux-gnu/glib-2.0/include  -DGST_USE_UNSTABLE_API  
-DG_THREADS_MANDATORY -DG_DISABLE_CAST_CHECKS -DG_DISABLE_ASSERT -Wall 
-Wdeclaration-after-statement -Wvla -Wpointer-arith -Wmissing-declarations 
-Wmissing-prototypes -Wredundant-decls -Wwrite-strings -Wformat-security 
-Wold-style-definition -Winit-self -Wmissing-include-dirs -Waddress 
-Wno-multichar -Wnested-externs   -g-I/usr/include/gudev-1.0 
-I/usr/include/glib-2.0 -I
 /usr/lib/i386-linux-gnu/glib-2.0/include  -I/usr/include/libusb-1.0  
-DGST_USE_UNSTABLE_API -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Wno-error -c -o 
libgstuvch264_la-gstuvch264_mjpgdemux.lo `test -f 'gstuvch264_mjpgdemux.c' || 
echo './'`gstuvch264_mjpgdemux.c
  /bin/bash ../../libtool  --tag=CC --tag=disable-static  --mode=compile gcc 
-std=gnu99 -DHAVE_CONFIG_H -I. -I../..   -D_FORTIFY_SOURCE=2 -I../../gst-libs 
-I../../gst-libs -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/i386-linux-gnu/glib-2.0/include  -DGST_USE_UNSTABLE_API  
-DG_THREADS_MANDATORY -DG_DISABLE_CAST_CHECKS -DG_DISABLE_ASSERT -Wall 
-Wdeclaration-after-statement -Wvla -Wpointer-arith -Wmissing-declarations 
-Wmissing-prototypes -Wredundant-decls -Wwrite-strings -Wformat-security 
-Wold-style-definition -Winit-self -Wmissing-include-dirs -Waddress 
-Wno-multichar -Wnested-externs   -g-g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wno-error -c -o 
libgstdvb_la-gstdvbsrc.lo `test -f 'gstdvbsrc.c' || echo './'`gstdvbsrc.c
  /bin/bash ../../libtool  --tag=CC --tag=disable-static  --mode=compile gcc 
-std=gnu99 -DHAVE_CONFIG_H -I. -I../..   -D_FORTIFY_SOURCE=2 -I../../gst-libs 
-I../../gst-libs -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/i386-linux-gnu/glib-2.0/include  -DGST_USE_UNSTABLE_API  
-DG_THREADS_MANDATORY -DG_DISABLE_CAST_CHECKS -DG_DISABLE_ASSERT -Wall 
-Wdeclaration-after-statement -Wvla -Wpointer-arith -Wmissing-declarations 
-Wmissing-prototypes -Wredundant-decls -Wwrite-strings -Wformat-security 
-Wold-style-definition -Winit-self -Wmissing-include-dirs -Waddress 
-Wno-multichar -Wnested-externs   -g-g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wno-error -c -o 
libgstdvb_la-dvbbasebin.lo `test -f 'dvbbasebin.c' || echo './'`dvbbasebin.c
  In file included from /usr/include/ubuntu/application/ui/window.h:31:0,
   from gstamc.h:35,
   from gstamchybris.c:27:
  /usr/include/ubuntu/application/instance.h:28:44: fatal error: 
mir_toolkit/mir_client_library.h: No such file or directory
   #include mir_toolkit/mir_client_library.h
  ^
  compilation terminated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1458681/+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 1224756] Re: Pulseaudio should integrate with trust-store

[Ricardo Salveti]

Basically we need to change pulseaudio in a way it can ask trusty store
for the right permission when starting the recording process. Please
ping tvoss to know more about how that can be done at the trust-store
level, since there are some examples in the trust-store project.

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

Title:
  Pulseaudio should integrate with trust-store

Status in the base for Ubuntu mobile products:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  Currently the 'audio' policy group allows access to pulseaudio which
  allows apps to use the microphone and eavesdrop on the user.
  Pulseaudio needs to be modified to use trust-store, like location-
  service does. Integrating with trust-store means that when an app
  tries use the microphone via pulseaudio, pulseaudio will contact
  trust-store, the trust-store will prompt the user (Foo wants to use
  the microphone. Is this ok? Yes|No), optionally cache the result and
  return the result to pulseaudio. In this manner the user is given a
  contextual prompt at the time of access by the app. Using caching this
  decision can be remembered the next time. If caching is used, there
  should be a method to change the decision in settings.

  Targeting to T-Series for now, since the trust-store is not in a
  reusable form yet.

  Original description:
  David and the security team (inspired by an observation from Rick) discussed 
that when recording, pulseaudio should somehow unobtrusively show the user that 
it is recording. The easiest thing to do would be for pulseaudio to alert 
indicator-sound which would then turn its icon red (similar to 
indicator-message turning blue with new messages). Marking 'high' because apps 
with access to pulseaudio can currently eavedrop on users. If the app is 
allowed to do networking (the default for apps), then it can ship that 
information off to a server somewhere.

  Note 1, the alert to indicator-sound must happen via the out of
  process pulseaudio server and not the confined app itself to be
  effective.

  Note 2, we should consider how to enforce this for foreground apps
  only. Application lifecycle should probably handle this for 13.10
  (apps are suspended if not in foreground or if the screensaver is on),
  but we don't want an app on the converged device to record in the
  background when the user isn't paying attention. Example eavesdropping
  attack: start recording only when the screensaver is on (perhaps
  inhibiting the screensaver during recording would be enough).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1224756/+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 1450642] Re: seccomp missing many new syscalls

[Ricardo Salveti]

** Changed in: snappy/15.04
   Status: Fix Committed = Fix Released

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

Title:
  seccomp missing many new syscalls

Status in Snappy Ubuntu:
  Fix Released
Status in Snappy 15.04 series:
  Fix Released
Status in libseccomp package in Ubuntu:
  Fix Released
Status in libseccomp source package in Vivid:
  Fix Released
Status in libseccomp source package in Wily:
  Fix Released

Bug description:
  [Impact]
  Several syscalls were discovered to be missing when using the launcher on 
snappy. These should be added so we may properly support seccomp filtering.

  [Test Case]
  seccomp itself has a comprehensive testsuite, and while it doesn't fail the 
build, regressions can be seen by looking at the build log. Eg:

  Regression Test Summary
  tests run: 6494
  tests skipped: 52
  tests passed: 6494
  tests failed: 0
  tests errored: 0

  
  Furthermore, on a snappy system, perform:
  $ sudo snappy install hello-world
  $ hello-world.env

  It should show the environment. On an arm system with 2.1.1-1 from the 
archive, this will fail due to a seccomp denial:
  audit: type=1326 audit(1430766107.122:16): auid=1000 uid=1000 gid=1000 ses=15 
pid=1491 comm=env exe=/bin/bash sig=31 arch=4028 syscall=983045 
compat=0 ip=0xb6fb0bd6 code=0x0

  (note, snappy images have a ppa fix for this, see notes below).

  
  To test the segfault fix, do:
  $ scmp_sys_resolver 1024
  Segmentation fault

  It should return:
  $ scmp_sys_resolver 1024
  UNKNOWN

  
  For the new 3.19 syscalls:
  $ scmp_sys_resolver getrandom
  -1

  it should return something like (actual number depends on arch, this is on 
armhf):
  $ scmp_sys_resolver getrandom
  384


  autopkgtests for libseccomp have been added as part of this update to verify 
that the library recognizes all the syscalls from 3.19 and the private 
syscalls. These tests can be run like so (assuming you are in the unpacked 
source and the binaries are in ../binary):
  $ export REL=vivid
  $ adt-run `for i in ../binary/*.deb ; do echo -n -B $i  ; done` --source 
../source/*.dsc --log-file /tmp/adt.out --- adt-virt-schroot 
autopkgtest-$REL-amd64 || echo ** AUTOPKGTESTS FAILED

  Alternatively, if you don't have autopkgtest setup, you can do:
  $ apt-get install dpkg-dev build-essential linux-libc-dev libseccomp-dev 
seccomp
  $ export ADTTMP=/tmp/foo ; mkdir -p $ADTTMP ; sh ./debian/tests/test-filter
  ...
  PASS
  $ export ADTTMP=/tmp/foo ; mkdir -p $ADTTMP ; sh 
./debian/tests/test-scmp_sys_resolver
  ...
  PASS

  
  Lastly, seccomp is used by lxc. lxc can be tested by using the test case as 
outlined in step 4 of 
https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor#Desktop_only.

  
  [Regression Potential]
  If the above tests, regression potential is considered low. Unknown syscalls 
will continue to be handled as before.


  Description of changes:
  add finit_module:
  
https://github.com/seccomp/libseccomp/commit/64152018ffdf971efefd84466db4a92002bb8b15

  sync the syscall table entries - 3.16
  
https://github.com/seccomp/libseccomp/commit/9186136be7696ed63a8ddc06c9b397057abc5c75
  
https://github.com/seccomp/libseccomp/commit/3f319a9a5bc2e32f5a3c296fb0476c040b6f46c4
  
https://github.com/seccomp/libseccomp/commit/689f19e7488535c775c1db415b8d9895905ef8dd
  
https://github.com/seccomp/libseccomp/commit/ac6802b300922ef2ad3e95e2c80f89b575073aeb
  
https://github.com/seccomp/libseccomp/commit/c6205d9600983aa3fa68ca952b7624f2fec86718
  
https://github.com/seccomp/libseccomp/commit/76739812a3e23182504cde43403ddb9921e0e05a

  sync the syscall table entries - 3.17
  
https://github.com/seccomp/libseccomp/commit/6354f8cab5ac82a8d567005e58a9e7ff9dd843a9

  sync the syscall table entries - 3.19
  
https://github.com/seccomp/libseccomp/commit/7b80fb2fb683cafaf5dc9ff7692437ba86e598a3

  This should also be applied (fix a segfault for invalid syscall numbers):
  
https://github.com/seccomp/libseccomp/commit/2d09a74c7f04d29ae740db1e2187ff1a1886b2c3

  In addition, add-missing-arm-private-syscalls.patch is add to add 5
  private ARM syscalls. These are absolutely required on snappy. This
  portion of the patch has been well tested and is included by default
  in stable snappy images via the snappy image PPA.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1450642/+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 1460152] Re: apparmor cache not updated when apparmor.d rules change (breaks 15.04/stable - 15.04/edge updates)

[Ricardo Salveti]

** Changed in: snappy/15.04
   Status: Fix Committed = Fix Released

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

Title:
  apparmor cache not updated when apparmor.d rules change (breaks
  15.04/stable - 15.04/edge updates)

Status in Snappy Ubuntu:
  In Progress
Status in Snappy 15.04 series:
  Fix Released
Status in apparmor package in Ubuntu:
  New

Bug description:
  The apparmor cache gets confused easily on upgrade.

  Here is what happens:
  - boot stable, /etc/apparmor.d/cache/usr.bin.ubuntu-core-launcher is mtime of 
now because we generate the cache on boot
  - upgrade to edge, /etc/apparmor.d/usr.bin.ubuntu-core-launcher is updated 
and has the mtime of T (yesterday) when the file was put into the package
  - on the next reboot the apparmor_parser compares the mtime of the 
cache/usr.bin.ubuntu-core-launcher (very very recent) with the mtime of the 
souce usr.bin.ubuntu-core-launcher (much older)
  - cache does is *not* re-generate

  Possible solution:
  - clear cache on upgrade
  - make apparmor_parser store mtime of the source file in the header
  - make apparmor_parser use set the cache file to the mtime of the source file 
used to generate the cache and re-generate if those get out-of-sync

  Original description:
  --

  Rick Spencer ran into the situation that he ended up with a snappy image that 
gave the following error:
  
  apparmor=DENIED operation=mkdir profile=/usr/bin/ubuntu-core-launcher 
name=/tmp/snap.0_pastebinit.mvo_em33Zz/ pid=1092 comm=ubuntu-core-lau 
requested_mask=c denied_mask=c fsuid=0 ouid=0
  

  Running:
  $ sudo apparmor_parser --skip-cache -r 
/etc/apparmor.d/usr.bin.ubuntu-core-launcher
  fixes it.

  This strongly indicates that the cache has the old content and did not
  get re-generated on upgrade or image build.

  I also managed to reproduce this via:
  15.04/stable-15.04/edge

  The image is here:
  https://drive.google.com/open?id=0B1sb5ymdUGiLa0tUR0pGV3lzR1kauthuser=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1460152/+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 1460152] Re: apparmor cache not updated when apparmor.d rules change (breaks 15.04/stable - 15.04/edge updates)

[Ricardo Salveti]

Let's land on wily, test and then make push to our PPA (so we can also
test it there, and also revert the workaround), we can include this at
our next stable release :-)

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

Title:
  apparmor cache not updated when apparmor.d rules change (breaks
  15.04/stable - 15.04/edge updates)

Status in Snappy Ubuntu:
  In Progress
Status in Snappy 15.04 series:
  Fix Released
Status in apparmor package in Ubuntu:
  New

Bug description:
  The apparmor cache gets confused easily on upgrade.

  Here is what happens:
  - boot stable, /etc/apparmor.d/cache/usr.bin.ubuntu-core-launcher is mtime of 
now because we generate the cache on boot
  - upgrade to edge, /etc/apparmor.d/usr.bin.ubuntu-core-launcher is updated 
and has the mtime of T (yesterday) when the file was put into the package
  - on the next reboot the apparmor_parser compares the mtime of the 
cache/usr.bin.ubuntu-core-launcher (very very recent) with the mtime of the 
souce usr.bin.ubuntu-core-launcher (much older)
  - cache does is *not* re-generate

  Possible solution:
  - clear cache on upgrade
  - make apparmor_parser store mtime of the source file in the header
  - make apparmor_parser use set the cache file to the mtime of the source file 
used to generate the cache and re-generate if those get out-of-sync

  Original description:
  --

  Rick Spencer ran into the situation that he ended up with a snappy image that 
gave the following error:
  
  apparmor=DENIED operation=mkdir profile=/usr/bin/ubuntu-core-launcher 
name=/tmp/snap.0_pastebinit.mvo_em33Zz/ pid=1092 comm=ubuntu-core-lau 
requested_mask=c denied_mask=c fsuid=0 ouid=0
  

  Running:
  $ sudo apparmor_parser --skip-cache -r 
/etc/apparmor.d/usr.bin.ubuntu-core-launcher
  fixes it.

  This strongly indicates that the cache has the old content and did not
  get re-generated on upgrade or image build.

  I also managed to reproduce this via:
  15.04/stable-15.04/edge

  The image is here:
  https://drive.google.com/open?id=0B1sb5ymdUGiLa0tUR0pGV3lzR1kauthuser=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1460152/+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 1460152] Re: apparmor cache not updated when apparmor.d rules change (breaks 15.04/stable - 15.04/edge updates)

[Ricardo Salveti]

** Changed in: snappy
 Assignee: (unassigned) = Michael Vogt (mvo)

** Changed in: snappy/15.04
 Assignee: (unassigned) = Michael Vogt (mvo)

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

Title:
  apparmor cache not updated when apparmor.d rules change (breaks
  15.04/stable - 15.04/edge updates)

Status in Snappy Ubuntu:
  In Progress
Status in Snappy 15.04 series:
  In Progress
Status in apparmor package in Ubuntu:
  New

Bug description:
  The apparmor cache gets confused easily on upgrade.

  Here is what happens:
  - boot stable, /etc/apparmor.d/cache/usr.bin.ubuntu-core-launcher is mtime of 
now because we generate the cache on boot
  - upgrade to edge, /etc/apparmor.d/usr.bin.ubuntu-core-launcher is updated 
and has the mtime of T (yesterday) when the file was put into the package
  - on the next reboot the apparmor_parser compares the mtime of the 
cache/usr.bin.ubuntu-core-launcher (very very recent) with the mtime of the 
souce usr.bin.ubuntu-core-launcher (much older)
  - cache does is *not* re-generate

  Possible solution:
  - clear cache on upgrade
  - make apparmor_parser store mtime of the source file in the header
  - make apparmor_parser use set the cache file to the mtime of the source file 
used to generate the cache and re-generate if those get out-of-sync

  Original description:
  --

  Rick Spencer ran into the situation that he ended up with a snappy image that 
gave the following error:
  
  apparmor=DENIED operation=mkdir profile=/usr/bin/ubuntu-core-launcher 
name=/tmp/snap.0_pastebinit.mvo_em33Zz/ pid=1092 comm=ubuntu-core-lau 
requested_mask=c denied_mask=c fsuid=0 ouid=0
  

  Running:
  $ sudo apparmor_parser --skip-cache -r 
/etc/apparmor.d/usr.bin.ubuntu-core-launcher
  fixes it.

  This strongly indicates that the cache has the old content and did not
  get re-generated on upgrade or image build.

  I also managed to reproduce this via:
  15.04/stable-15.04/edge

  The image is here:
  https://drive.google.com/open?id=0B1sb5ymdUGiLa0tUR0pGV3lzR1kauthuser=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1460152/+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 1450642] Re: seccomp missing many new syscalls

[Ricardo Salveti]

** Also affects: snappy/15.04
   Importance: Undecided
   Status: New

** Changed in: snappy/15.04
Milestone: None = 15.04.1

** Changed in: snappy/15.04
 Assignee: (unassigned) = Jamie Strandboge (jdstrand)

** Changed in: snappy/15.04
   Status: New = Fix Committed

** Changed in: snappy
   Status: Fix Committed = Fix Released

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

Title:
  seccomp missing many new syscalls

Status in Snappy Ubuntu:
  Fix Released
Status in Snappy 15.04 series:
  Fix Committed
Status in libseccomp package in Ubuntu:
  Fix Released
Status in libseccomp source package in Vivid:
  Fix Released
Status in libseccomp source package in Wily:
  Fix Released

Bug description:
  [Impact]
  Several syscalls were discovered to be missing when using the launcher on 
snappy. These should be added so we may properly support seccomp filtering.

  [Test Case]
  seccomp itself has a comprehensive testsuite, and while it doesn't fail the 
build, regressions can be seen by looking at the build log. Eg:

  Regression Test Summary
  tests run: 6494
  tests skipped: 52
  tests passed: 6494
  tests failed: 0
  tests errored: 0

  
  Furthermore, on a snappy system, perform:
  $ sudo snappy install hello-world
  $ hello-world.env

  It should show the environment. On an arm system with 2.1.1-1 from the 
archive, this will fail due to a seccomp denial:
  audit: type=1326 audit(1430766107.122:16): auid=1000 uid=1000 gid=1000 ses=15 
pid=1491 comm=env exe=/bin/bash sig=31 arch=4028 syscall=983045 
compat=0 ip=0xb6fb0bd6 code=0x0

  (note, snappy images have a ppa fix for this, see notes below).

  
  To test the segfault fix, do:
  $ scmp_sys_resolver 1024
  Segmentation fault

  It should return:
  $ scmp_sys_resolver 1024
  UNKNOWN

  
  For the new 3.19 syscalls:
  $ scmp_sys_resolver getrandom
  -1

  it should return something like (actual number depends on arch, this is on 
armhf):
  $ scmp_sys_resolver getrandom
  384


  autopkgtests for libseccomp have been added as part of this update to verify 
that the library recognizes all the syscalls from 3.19 and the private 
syscalls. These tests can be run like so (assuming you are in the unpacked 
source and the binaries are in ../binary):
  $ export REL=vivid
  $ adt-run `for i in ../binary/*.deb ; do echo -n -B $i  ; done` --source 
../source/*.dsc --log-file /tmp/adt.out --- adt-virt-schroot 
autopkgtest-$REL-amd64 || echo ** AUTOPKGTESTS FAILED

  Alternatively, if you don't have autopkgtest setup, you can do:
  $ apt-get install dpkg-dev build-essential linux-libc-dev libseccomp-dev 
seccomp
  $ export ADTTMP=/tmp/foo ; mkdir -p $ADTTMP ; sh ./debian/tests/test-filter
  ...
  PASS
  $ export ADTTMP=/tmp/foo ; mkdir -p $ADTTMP ; sh 
./debian/tests/test-scmp_sys_resolver
  ...
  PASS

  
  Lastly, seccomp is used by lxc. lxc can be tested by using the test case as 
outlined in step 4 of 
https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor#Desktop_only.

  
  [Regression Potential]
  If the above tests, regression potential is considered low. Unknown syscalls 
will continue to be handled as before.


  Description of changes:
  add finit_module:
  
https://github.com/seccomp/libseccomp/commit/64152018ffdf971efefd84466db4a92002bb8b15

  sync the syscall table entries - 3.16
  
https://github.com/seccomp/libseccomp/commit/9186136be7696ed63a8ddc06c9b397057abc5c75
  
https://github.com/seccomp/libseccomp/commit/3f319a9a5bc2e32f5a3c296fb0476c040b6f46c4
  
https://github.com/seccomp/libseccomp/commit/689f19e7488535c775c1db415b8d9895905ef8dd
  
https://github.com/seccomp/libseccomp/commit/ac6802b300922ef2ad3e95e2c80f89b575073aeb
  
https://github.com/seccomp/libseccomp/commit/c6205d9600983aa3fa68ca952b7624f2fec86718
  
https://github.com/seccomp/libseccomp/commit/76739812a3e23182504cde43403ddb9921e0e05a

  sync the syscall table entries - 3.17
  
https://github.com/seccomp/libseccomp/commit/6354f8cab5ac82a8d567005e58a9e7ff9dd843a9

  sync the syscall table entries - 3.19
  
https://github.com/seccomp/libseccomp/commit/7b80fb2fb683cafaf5dc9ff7692437ba86e598a3

  This should also be applied (fix a segfault for invalid syscall numbers):
  
https://github.com/seccomp/libseccomp/commit/2d09a74c7f04d29ae740db1e2187ff1a1886b2c3

  In addition, add-missing-arm-private-syscalls.patch is add to add 5
  private ARM syscalls. These are absolutely required on snappy. This
  portion of the patch has been well tested and is included by default
  in stable snappy images via the snappy image PPA.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1450642/+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 1434143] Re: boot script should run aa-profile-hook in addition to aa-clickhook

[Ricardo Salveti]

** Changed in: snappy
   Status: Triaged = Fix Released

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

Title:
  boot script should run aa-profile-hook in addition to aa-clickhook

Status in Snappy Ubuntu:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  Summary says it all. aa-profile-hook does the same sort of thing as
  aa-clickhook and is used on snappy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1434143/+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 1458680] Re: platform-api FTBFS in wily (2.9.0+15.04.20150326-0ubuntu1)

[Ricardo Salveti]

On Tue, May 26, 2015 at 2:56 PM, Robert Carr rac...@canonical.com wrote:
 https://code.launchpad.net/~mir-team/platform-api/delete-
 deprecations/+merge/254170 needed to land

Thanks.

Can we please coordinate such landings next time we change something
on mir that breaks the reverse build-deps?

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

Title:
  platform-api FTBFS in wily (2.9.0+15.04.20150326-0ubuntu1)

Status in platform-api package in Ubuntu:
  New

Bug description:
  sbuild -A --dist=wily --arch=i386 -c wily-proposed-i386-sbuild
  platform-api_2.9.0+15.04.20150326-0ubuntu1.dsc

  [ 26%] Building CXX object 
src/ubuntu/application/common/mircommon/CMakeFiles/ubuntu_application_api_mircommon.dir/event_helpers_mir.cpp.o
  cd 
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/obj-i686-linux-gnu/src/ubuntu/application/common/mircommon
  /usr/bin/i686-linux-gnu-g++-4.9-g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -D_FORTIFY_SOURCE=2  -fvisibility=hidden -fPIC 
--std=c++11 -I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/include 
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/android/include 
-I/usr/include/mirclient -I/usr/include/mircommon 
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src 
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/obj-i686-linux-gnu/include 
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/../../bridge
 -I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common  
  -o CMakeFiles/ubuntu_application_api_mircommon.dir/event_helpers_mir.cpp.o -c 
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp
  
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:
 In function 'bool ubuntu::application::ui::mir::event_to_ubuntu_event(const 
MirEvent*, WindowEvent)':
  
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:28:22:
 error: invalid use of incomplete type 'const MirEvent {aka const union 
MirEvent}'
   switch (mir_event-type)
^
  In file included from /usr/include/mirclient/mir_toolkit/event.h:22:0,
   from 
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.h:24,
   from 
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:19:
  /usr/include/mirclient/mir_toolkit/events/event.h:57:15: error: forward 
declaration of 'const MirEvent {aka const union MirEvent}'
   typedef union MirEvent MirEvent;
 ^
  
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:32:44:
 error: invalid use of incomplete type 'const MirEvent {aka const union 
MirEvent}'
   ubuntu_ev.key.device_id = mir_event-key.device_id;
  ^
  In file included from /usr/include/mirclient/mir_toolkit/event.h:22:0,
   from 
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.h:24,
   from 
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:19:
  /usr/include/mirclient/mir_toolkit/events/event.h:57:15: error: forward 
declaration of 'const MirEvent {aka const union MirEvent}'
   typedef union MirEvent MirEvent;
 ^
  
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:33:44:
 error: invalid use of incomplete type 'const MirEvent {aka const union 
MirEvent}'
   ubuntu_ev.key.source_id = mir_event-key.source_id;
  ^
  In file included from /usr/include/mirclient/mir_toolkit/event.h:22:0,
   from 
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.h:24,
   from 
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:19:
  /usr/include/mirclient/mir_toolkit/events/event.h:57:15: error: forward 
declaration of 'const MirEvent {aka const union MirEvent}'
   typedef union MirEvent MirEvent;
 ^
  
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:34:41:
 error: invalid use of incomplete type 'const MirEvent {aka const union 
MirEvent}'
   ubuntu_ev.key.action = mir_event-key.action;
   ^
  In file included from /usr/include/mirclient/mir_toolkit/event.h:22:0,
   from 

[Touch-packages] [Bug 1458681] [NEW] [gst-hybris] FTBFS in wily/vivid (armhf/i386)

[Ricardo Salveti]

Public bug reported:

When building gst-plugins-bad1.0 1.4.5-1ubuntu3

...
/bin/bash ../../libtool  --tag=CC --tag=disable-static  --mode=compile gcc 
-std=gnu99 -DHAVE_CONFIG_H -I. -I../..   -D_FORTIFY_SOURCE=2 -I../../gst-libs 
-I../../gst-libs -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/i386-linux-gnu/glib-2.0/include  -pthread 
-I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/i386-linux-gnu/glib-2.0/include  -pthread 
-I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/i386-linux-gnu/glib-2.0/include  -pthread 
-I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/i386-linux-gnu/glib-2.0/include  -DGST_USE_UNSTABLE_API  
-DG_THREADS_MANDATORY -DG_DISABLE_CAST_CHECKS -DG_DISABLE_ASSERT -Wall 
-Wdeclaration-after-statement -Wvla -Wpointer-arith -Wmissing-declarations 
-Wmissing-prototypes -Wredundant-decls -Wwrite-strings -Wformat-security 
-Wold-style-definition -Winit-self -Wmissing-include-dirs -Waddress 
-Wno-multichar -Wnested-externs   -g-I/usr/include/gudev-1.0 
-I/usr/include/glib-2.0 -I/u
 sr/lib/i386-linux-gnu/glib-2.0/include  -I/usr/include/libusb-1.0  
-DGST_USE_UNSTABLE_API -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Wno-error -c -o 
libgstuvch264_la-gstuvch264_mjpgdemux.lo `test -f 'gstuvch264_mjpgdemux.c' || 
echo './'`gstuvch264_mjpgdemux.c
/bin/bash ../../libtool  --tag=CC --tag=disable-static  --mode=compile gcc 
-std=gnu99 -DHAVE_CONFIG_H -I. -I../..   -D_FORTIFY_SOURCE=2 -I../../gst-libs 
-I../../gst-libs -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/i386-linux-gnu/glib-2.0/include  -DGST_USE_UNSTABLE_API  
-DG_THREADS_MANDATORY -DG_DISABLE_CAST_CHECKS -DG_DISABLE_ASSERT -Wall 
-Wdeclaration-after-statement -Wvla -Wpointer-arith -Wmissing-declarations 
-Wmissing-prototypes -Wredundant-decls -Wwrite-strings -Wformat-security 
-Wold-style-definition -Winit-self -Wmissing-include-dirs -Waddress 
-Wno-multichar -Wnested-externs   -g-g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wno-error -c -o 
libgstdvb_la-gstdvbsrc.lo `test -f 'gstdvbsrc.c' || echo './'`gstdvbsrc.c
/bin/bash ../../libtool  --tag=CC --tag=disable-static  --mode=compile gcc 
-std=gnu99 -DHAVE_CONFIG_H -I. -I../..   -D_FORTIFY_SOURCE=2 -I../../gst-libs 
-I../../gst-libs -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/i386-linux-gnu/glib-2.0/include  -DGST_USE_UNSTABLE_API  
-DG_THREADS_MANDATORY -DG_DISABLE_CAST_CHECKS -DG_DISABLE_ASSERT -Wall 
-Wdeclaration-after-statement -Wvla -Wpointer-arith -Wmissing-declarations 
-Wmissing-prototypes -Wredundant-decls -Wwrite-strings -Wformat-security 
-Wold-style-definition -Winit-self -Wmissing-include-dirs -Waddress 
-Wno-multichar -Wnested-externs   -g-g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wno-error -c -o 
libgstdvb_la-dvbbasebin.lo `test -f 'dvbbasebin.c' || echo './'`dvbbasebin.c
In file included from /usr/include/ubuntu/application/ui/window.h:31:0,
 from gstamc.h:35,
 from gstamchybris.c:27:
/usr/include/ubuntu/application/instance.h:28:44: fatal error: 
mir_toolkit/mir_client_library.h: No such file or directory
 #include mir_toolkit/mir_client_library.h
^
compilation terminated.

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

** Affects: platform-api (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [gst-hybris] FTBFS in wily/vivid (armhf/i386)

Status in gst-plugins-bad1.0 package in Ubuntu:
  New
Status in platform-api package in Ubuntu:
  New

Bug description:
  When building gst-plugins-bad1.0 1.4.5-1ubuntu3

  ...
  /bin/bash ../../libtool  --tag=CC --tag=disable-static  --mode=compile gcc 
-std=gnu99 -DHAVE_CONFIG_H -I. -I../..   -D_FORTIFY_SOURCE=2 -I../../gst-libs 
-I../../gst-libs -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/i386-linux-gnu/glib-2.0/include  -pthread 
-I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/i386-linux-gnu/glib-2.0/include  -pthread 
-I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/i386-linux-gnu/glib-2.0/include  -pthread 
-I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/i386-linux-gnu/glib-2.0/include  -DGST_USE_UNSTABLE_API  
-DG_THREADS_MANDATORY -DG_DISABLE_CAST_CHECKS -DG_DISABLE_ASSERT -Wall 
-Wdeclaration-after-statement -Wvla -Wpointer-arith -Wmissing-declarations 
-Wmissing-prototypes -Wredundant-decls -Wwrite-strings -Wformat-security 
-Wold-style-definition -Winit-self -Wmissing-include-dirs -Waddress 
-Wno-multichar -Wnested-externs   -g-I/usr/include/gudev-1.0 
-I/usr/include/glib-2.0 -I
 

[Touch-packages] [Bug 1458681] Re: [gst-hybris] FTBFS in wily/vivid (armhf/i386)

[Ricardo Salveti]

gst-plugins-bad doesn't use mir directly, and the mir_toolkit header
gets included because of platform-api. I believe the right fix would be
for platform-api to export the right include path as part of the pc file
that it exports.

** Also affects: platform-api (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [gst-hybris] FTBFS in wily/vivid (armhf/i386)

Status in gst-plugins-bad1.0 package in Ubuntu:
  New
Status in platform-api package in Ubuntu:
  New

Bug description:
  When building gst-plugins-bad1.0 1.4.5-1ubuntu3

  ...
  /bin/bash ../../libtool  --tag=CC --tag=disable-static  --mode=compile gcc 
-std=gnu99 -DHAVE_CONFIG_H -I. -I../..   -D_FORTIFY_SOURCE=2 -I../../gst-libs 
-I../../gst-libs -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/i386-linux-gnu/glib-2.0/include  -pthread 
-I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/i386-linux-gnu/glib-2.0/include  -pthread 
-I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/i386-linux-gnu/glib-2.0/include  -pthread 
-I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/i386-linux-gnu/glib-2.0/include  -DGST_USE_UNSTABLE_API  
-DG_THREADS_MANDATORY -DG_DISABLE_CAST_CHECKS -DG_DISABLE_ASSERT -Wall 
-Wdeclaration-after-statement -Wvla -Wpointer-arith -Wmissing-declarations 
-Wmissing-prototypes -Wredundant-decls -Wwrite-strings -Wformat-security 
-Wold-style-definition -Winit-self -Wmissing-include-dirs -Waddress 
-Wno-multichar -Wnested-externs   -g-I/usr/include/gudev-1.0 
-I/usr/include/glib-2.0 -I
 /usr/lib/i386-linux-gnu/glib-2.0/include  -I/usr/include/libusb-1.0  
-DGST_USE_UNSTABLE_API -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Wno-error -c -o 
libgstuvch264_la-gstuvch264_mjpgdemux.lo `test -f 'gstuvch264_mjpgdemux.c' || 
echo './'`gstuvch264_mjpgdemux.c
  /bin/bash ../../libtool  --tag=CC --tag=disable-static  --mode=compile gcc 
-std=gnu99 -DHAVE_CONFIG_H -I. -I../..   -D_FORTIFY_SOURCE=2 -I../../gst-libs 
-I../../gst-libs -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/i386-linux-gnu/glib-2.0/include  -DGST_USE_UNSTABLE_API  
-DG_THREADS_MANDATORY -DG_DISABLE_CAST_CHECKS -DG_DISABLE_ASSERT -Wall 
-Wdeclaration-after-statement -Wvla -Wpointer-arith -Wmissing-declarations 
-Wmissing-prototypes -Wredundant-decls -Wwrite-strings -Wformat-security 
-Wold-style-definition -Winit-self -Wmissing-include-dirs -Waddress 
-Wno-multichar -Wnested-externs   -g-g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wno-error -c -o 
libgstdvb_la-gstdvbsrc.lo `test -f 'gstdvbsrc.c' || echo './'`gstdvbsrc.c
  /bin/bash ../../libtool  --tag=CC --tag=disable-static  --mode=compile gcc 
-std=gnu99 -DHAVE_CONFIG_H -I. -I../..   -D_FORTIFY_SOURCE=2 -I../../gst-libs 
-I../../gst-libs -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/i386-linux-gnu/glib-2.0/include  -DGST_USE_UNSTABLE_API  
-DG_THREADS_MANDATORY -DG_DISABLE_CAST_CHECKS -DG_DISABLE_ASSERT -Wall 
-Wdeclaration-after-statement -Wvla -Wpointer-arith -Wmissing-declarations 
-Wmissing-prototypes -Wredundant-decls -Wwrite-strings -Wformat-security 
-Wold-style-definition -Winit-self -Wmissing-include-dirs -Waddress 
-Wno-multichar -Wnested-externs   -g-g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wno-error -c -o 
libgstdvb_la-dvbbasebin.lo `test -f 'dvbbasebin.c' || echo './'`dvbbasebin.c
  In file included from /usr/include/ubuntu/application/ui/window.h:31:0,
   from gstamc.h:35,
   from gstamchybris.c:27:
  /usr/include/ubuntu/application/instance.h:28:44: fatal error: 
mir_toolkit/mir_client_library.h: No such file or directory
   #include mir_toolkit/mir_client_library.h
  ^
  compilation terminated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1458681/+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 1452386] Re: [gst-hybris] Support COLOR_QCOM_FormatYVU420SemiPlanar32m color format.

[Ricardo Salveti]

Tried to land this fix but then got blocked by bug 1458681

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

Title:
  [gst-hybris] Support COLOR_QCOM_FormatYVU420SemiPlanar32m color
  format.

Status in gst-plugins-bad1.0 package in Ubuntu:
  In Progress
Status in gst-plugins-bad1.0 package in Ubuntu RTM:
  New

Bug description:
  COLOR_QCOM_FormatYVU420SemiPlanar32m is essentially
  GST_VIDEO_FORMAT_NV12, but with stride and plane heights aligned to
  32. Adding support is as simple as adding android-gst color format
  mapping, and using same code as COLOR_QCOM_FormatYUV420SemiPlanar to
  handle software conversion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1452386/+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 1452386] Re: [gst-hybris] Support COLOR_QCOM_FormatYVU420SemiPlanar32m color format.

[Ricardo Salveti]

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

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

Title:
  [gst-hybris] Support COLOR_QCOM_FormatYVU420SemiPlanar32m color
  format.

Status in gst-plugins-bad1.0 package in Ubuntu:
  In Progress
Status in gst-plugins-bad1.0 package in Ubuntu RTM:
  New

Bug description:
  COLOR_QCOM_FormatYVU420SemiPlanar32m is essentially
  GST_VIDEO_FORMAT_NV12, but with stride and plane heights aligned to
  32. Adding support is as simple as adding android-gst color format
  mapping, and using same code as COLOR_QCOM_FormatYUV420SemiPlanar to
  handle software conversion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1452386/+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 1458680] [NEW] platform-api FTBFS in wily (2.9.0+15.04.20150326-0ubuntu1)

[Ricardo Salveti]

Public bug reported:

sbuild -A --dist=wily --arch=i386 -c wily-proposed-i386-sbuild platform-
api_2.9.0+15.04.20150326-0ubuntu1.dsc

[ 26%] Building CXX object 
src/ubuntu/application/common/mircommon/CMakeFiles/ubuntu_application_api_mircommon.dir/event_helpers_mir.cpp.o
cd 
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/obj-i686-linux-gnu/src/ubuntu/application/common/mircommon
  /usr/bin/i686-linux-gnu-g++-4.9-g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -D_FORTIFY_SOURCE=2  -fvisibility=hidden -fPIC 
--std=c++11 -I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/include 
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/android/include 
-I/usr/include/mirclient -I/usr/include/mircommon 
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src 
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/obj-i686-linux-gnu/include 
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/../../bridge
 -I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common  
  -o CMakeFiles/ubuntu_application_api_mircommon.dir/event_helpers_mir.cpp.o -c 
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:
 In function 'bool ubuntu::application::ui::mir::event_to_ubuntu_event(const 
MirEvent*, WindowEvent)':
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:28:22:
 error: invalid use of incomplete type 'const MirEvent {aka const union 
MirEvent}'
 switch (mir_event-type)
  ^
In file included from /usr/include/mirclient/mir_toolkit/event.h:22:0,
 from 
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.h:24,
 from 
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:19:
/usr/include/mirclient/mir_toolkit/events/event.h:57:15: error: forward 
declaration of 'const MirEvent {aka const union MirEvent}'
 typedef union MirEvent MirEvent;
   ^
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:32:44:
 error: invalid use of incomplete type 'const MirEvent {aka const union 
MirEvent}'
 ubuntu_ev.key.device_id = mir_event-key.device_id;
^
In file included from /usr/include/mirclient/mir_toolkit/event.h:22:0,
 from 
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.h:24,
 from 
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:19:
/usr/include/mirclient/mir_toolkit/events/event.h:57:15: error: forward 
declaration of 'const MirEvent {aka const union MirEvent}'
 typedef union MirEvent MirEvent;
   ^
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:33:44:
 error: invalid use of incomplete type 'const MirEvent {aka const union 
MirEvent}'
 ubuntu_ev.key.source_id = mir_event-key.source_id;
^
In file included from /usr/include/mirclient/mir_toolkit/event.h:22:0,
 from 
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.h:24,
 from 
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:19:
/usr/include/mirclient/mir_toolkit/events/event.h:57:15: error: forward 
declaration of 'const MirEvent {aka const union MirEvent}'
 typedef union MirEvent MirEvent;
   ^
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:34:41:
 error: invalid use of incomplete type 'const MirEvent {aka const union 
MirEvent}'
 ubuntu_ev.key.action = mir_event-key.action;
 ^
In file included from /usr/include/mirclient/mir_toolkit/event.h:22:0,
 from 
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.h:24,
 from 
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:19:
/usr/include/mirclient/mir_toolkit/events/event.h:57:15: error: forward 
declaration of 'const MirEvent {aka const union MirEvent}'
 typedef union MirEvent MirEvent;
   ^
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:35:40:
 error: invalid use of incomplete type 'const MirEvent {aka const union 
MirEvent}'
 ubuntu_ev.key.flags = mir_event-key.flags;
^
In file included from 

[Touch-packages] [Bug 1453163] Re: [Ubuntu Phone BQ] Wrong brightness after a few minutes with Never sleep

[Ricardo Salveti]

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

** This bug has been marked a duplicate of bug 1437510
   Screen dim is not following the lock screen timeout (always dimming after 50 
seconds)

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

Title:
  [Ubuntu Phone BQ] Wrong brightness after a few minutes with Never
  sleep

Status in Ubuntu Touch System Settings:
  New
Status in uNAV:
  New
Status in indicator-network package in Ubuntu:
  Invalid

Bug description:
  Hi!

  Steps:
  1. Set in the Battery preferences: Sleep when idle = Never
  2. Set in the Brightness preferences: Adjust automatically  = Disabled
  3. Set in the Brightness preferences: Display brightness bar = Max. brightness
  4. Leave the mobile in a web  BUG: After ~2' the brightness is changing to a 
lower brightness.

  This is annoying in special with the GPS application Here, when you're
  driving and you want the max brightness in the mobile all the time.

  Thanks in advance!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-system-settings/+bug/1453163/+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 1435088] Re: Crash of media-hub opening a .avi file

[Ricardo Salveti]

** Also affects: media-hub (Ubuntu RTM)
   Importance: Undecided
   Status: New

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

Title:
  Crash of media-hub opening a .avi file

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Media Hub:
  Fix Committed
Status in media-hub package in Ubuntu:
  Fix Released
Status in mediaplayer-app package in Ubuntu:
  Fix Released
Status in qtubuntu-media package in Ubuntu:
  Fix Released
Status in media-hub package in Ubuntu RTM:
  New

Bug description:
  I tried to open two .avi videos on BQ Aquaris E4.5 running Ubuntu Touch using 
the Media Player app: one simply prints Video format not supported while the 
second shows only a black screen. Then if I close the player I can't open any 
video and I get the error:
  Error playing video
  Fail to connect with playback backend.
  and trying to play some audio files simply doesn't do anything.
  I uploaded the second video here:
  http://uz.sns.it/~ilario/utouch-media-hub.avi

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: media-hub 2.0.0+15.04.20150120~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  CurrentDesktop: Unity
  Date: Sun Mar 22 23:32:09 2015
  InstallationDate: Installed on 2015-03-12 (10 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20150312-002053)
  SourcePackage: media-hub
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435088/+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 1458689] [NEW] [vivid-overlay] input-stub.so fails to load on i386

[Ricardo Salveti]

Public bug reported:

phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 140
device name: generic_x86
channel: ubuntu-touch/rc-proposed/ubuntu
last update: 2015-05-25 12:02:10
version version: 140
version ubuntu: 20150525
version device: 20150210
version custom: 20150525

When starting unity8:

[1432591771.427440] Server: Starting
[1432591771.427679] Loader: Loading modules from: 
/usr/lib/i386-linux-gnu/mir/server-platform
[1432591771.427824] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so
[1432591771.428143] WARNING Loader: Failed to load module: 
/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so (error 
was:/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so: undefined 
symbol: _ZN3mir6events10make_eventExx17MirKeyboardActionjij)
[1432591771.428520] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/graphics-dummy.so
[1432591771.428875] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/graphics-android.so.2
[1432591771.429008] mirplatform: Found graphics driver: dummy
[1432591771.429180] mirplatform: Found graphics driver: android
[1432591771.429324] Platform Loader: Selected driver: android (version 0.13.1)

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

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

Title:
  [vivid-overlay] input-stub.so fails to load on i386

Status in mir package in Ubuntu:
  New

Bug description:
  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 140
  device name: generic_x86
  channel: ubuntu-touch/rc-proposed/ubuntu
  last update: 2015-05-25 12:02:10
  version version: 140
  version ubuntu: 20150525
  version device: 20150210
  version custom: 20150525

  When starting unity8:

  [1432591771.427440] Server: Starting
  [1432591771.427679] Loader: Loading modules from: 
/usr/lib/i386-linux-gnu/mir/server-platform
  [1432591771.427824] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so
  [1432591771.428143] WARNING Loader: Failed to load module: 
/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so (error 
was:/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so: undefined 
symbol: _ZN3mir6events10make_eventExx17MirKeyboardActionjij)
  [1432591771.428520] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/graphics-dummy.so
  [1432591771.428875] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/graphics-android.so.2
  [1432591771.429008] mirplatform: Found graphics driver: dummy
  [1432591771.429180] mirplatform: Found graphics driver: android
  [1432591771.429324] Platform Loader: Selected driver: android (version 0.13.1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1458689/+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 1458043] Re: can't connect to adb in emulator and swipe doesn't appear to work

[Ricardo Salveti]

Adb issue fixed in wily, the other issues are bug 1458689 and bug
1458694.

** Also affects: lxc-android-config (Ubuntu)
   Importance: Undecided
   Status: New

** Package changed: goget-ubuntu-touch (Ubuntu) = lxc-android-config
(Ubuntu RTM)

** Changed in: lxc-android-config (Ubuntu)
   Status: New = Fix Released

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

Title:
  can't connect to adb in emulator and swipe doesn't appear to work

Status in lxc-android-config package in Ubuntu:
  Fix Released
Status in lxc-android-config package in Ubuntu RTM:
  New

Bug description:
  On vivid with:
  ubuntu-emulator 0.21-1+173~ubuntu15.04.1build1
  ubuntu-emulator-runtime 20141117-0039-0ubuntu11

  I generated an image like so:
  $ sudo ubuntu-emulator create --channel=ubuntu-touch/devel-proposed/ubuntu 
--arch=i386 devel-proposed.x86

  and started with:
  $ ubuntu-emulator run --scale=0.75 devel-proposed.x86

  then I see a lot of output, but some of it doesn't look right:
  [4.944791] init: ureadahead-touch main process (469) terminated with 
status 5
  [   12.865870] init: /dev/hw_random not found
  [   12.865870] init: cannot open '/initlogo.rle'
  [   12.887030] init: /dev/hw_random not found
  [   12.945132] init: cannot find '/system/etc/install-recovery.sh', disabling 
'flash_recovery'
  [   12.945132] init: cannot find '/system/bin/ubuntuappmanager.disabled', 
disabling 'ubuntuappmanager'
  [   12.945132] init: property 'sys.powerctl' doesn't exist while expanding 
'${sys.powerctl}'
  [   12.945132] init: powerctl: cannot expand '${sys.powerctl}'
  [   12.945132] init: property 'sys.sysctl.extra_free_kbytes' doesn't exist 
while expanding '${sys.sysctl.extra_free_kbytes}'
  [   12.945132] init: cannot expand '${sys.sysctl.extra_free_kbytes}' while 
writing to '/proc/sys/vm/extra_free_kbytes'
  [   12.945132] init: cannot find '/sbin/adbd', disabling 'adbd'
  [   12.945132] init: property 'persist.sys.usb.config' doesn't exist while 
expanding '${persist.sys.usb.config}'
  [   12.945132] init: cannot expand '${persist.sys.usb.config}' while 
assigning to 'sys.usb.config'
   * Setting up X socket directories...[ OK 
]
  /lib/init/init-d-script: 12: /etc/rc2.d/S02whoopsie: -c: not found
  basename: missing operand
  Try 'basename --help' for more information.
   * Starting virtual private network daemon(s)...  
  [   47.445560] systemd-logind[1146]: Failed to start user service: Unknown 
unit: user@32011.service

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1458043/+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 1458694] [NEW] [vivid-overlay] unity8 fails to start on the emulator

[Ricardo Salveti]

Public bug reported:

phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 140
device name: generic_x86
channel: ubuntu-touch/rc-proposed/ubuntu
last update: 2015-05-25 12:02:10
version version: 140
version ubuntu: 20150525
version device: 20150210
version custom: 20150525

When starting unity8 (this started at image 136, probably when mir 0.13
landed):

phablet@ubuntu-phablet:~$ cat ./.cache/upstart/unity8.log
()
[1432595001.896139] mirplatform: Found graphics driver: dummy
[1432595001.898447] mirplatform: Found graphics driver: android
qtmir.mir: MirServer created
[1432595003.675225] Server: Starting
[1432595003.679331] Loader: Loading modules from: 
/usr/lib/i386-linux-gnu/mir/server-platform
[1432595003.679501] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/graphics-dummy.so
[1432595003.680673] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so
[1432595003.681107] WARNING Loader: Failed to load module: 
/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so (error 
was:/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so: undefined 
symbol: _ZN3mir6events10make_eventExx17MirKeyboardActionjij)
[1432595003.684868] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/graphics-android.so.2
[1432595003.685014] mirplatform: Found graphics driver: dummy
[1432595003.685211] mirplatform: Found graphics driver: android
[1432595003.685416] Platform Loader: Selected driver: android (version 0.13.0)
qtmir.mir: PromptSessionListener::PromptSessionListener - this= 
PromptSessionListener(0x9679764)
qtmir.mir: SessionListener::SessionListener - this= SessionListener(0x9676d24)
qtmir.mir: MirShell::MirShell
[1432595003.883766] DisplayServer: Mir version 0.13.0
QtCompositor::setAllWindowsExposed true
qtmir.clipboard: D-Bus registration successful.
Mode argument was not provided or was set to an illegal value. Using default 
value of --mode= full-greeter
Cannot create window: no screens available

With version 135 it starts fine, but not fully functional, giving this
error:

QOpenGLShader::compile(Fragment): 0:2(12): warning: extension 
`GL_OES_standard_derivatives' unsupported in fragment shader
0:2(1): error: #extension directive is not allowed in the middle of a shader

*** Problematic Fragment shader source code ***
#extension GL_OES_standard_derivatives : enable  // Enable dFdy() on OpenGL ES 
2.
#define lowp
#define mediump
#define highp

// Copyright © 2015 Canonical Ltd.
//
// This program is free software; you can redistribute it and/or modify
// it under the terms of the GNU Lesser General Public License as published by
// the Free Software Foundation; version 3.
//
// This program is distributed in the hope that it will be useful,
// but WITHOUT ANY WARRANTY; without even the implied warranty of
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
// GNU Lesser General Public License for more details.
//
// You should have received a copy of the GNU Lesser General Public License
// along with this program.  If not, see http://www.gnu.org/licenses/.
//
// Author: Loïc Molinari loic.molin...@canonical.com

// Static flow control (branching on a uniform value) is fast on most GPUs 
(including ultra-low
// power ones) because it allows to use the same shader execution path for an 
entire draw call. We
// rely on that technique here (also known as uber-shader solution) to avoid 
the complexity of
// dealing with a multiple shaders solution.
// FIXME(loicm) Validate GPU behavior with regards to static flow control.

uniform sampler2D shapeTexture;
uniform sampler2D sourceTexture;
uniform lowp vec2 dfdtFactors;
uniform lowp vec2 opacityFactors;
uniform lowp float sourceOpacity;
uniform lowp float distanceAA;
uniform bool textured;
uniform mediump int aspect;

varying mediump vec2 shapeCoord;
varying mediump vec4 sourceCoord;
varying lowp vec4 backgroundColor;

const mediump int FLAT  = 0x08;  // 1  3
const mediump int INSET = 0x10;  // 1  4

void main(void)
{
lowp vec4 shapeData = texture2D(shapeTexture, shapeCoord);
lowp vec4 color = backgroundColor;

// FIXME(loicm) Would be better to use a bitfield but bitwise ops have only 
been integrated in
// GLSL 1.3 (OpenGL 3) and GLSL ES 3 (OpenGL ES 3).
if (textured) {
// Blend the source over the current color.
// FIXME(loicm) sign() is far from optimal. Call texture2D() at 
beginning of scope.
lowp vec2 axisMask = -sign((sourceCoord.zw * sourceCoord.zw) - 
vec2(1.0));
lowp float mask = clamp(axisMask.x + axisMask.y, 0.0, 1.0);
lowp vec4 source = texture2D(sourceTexture, sourceCoord.st) * 
vec4(sourceOpacity * mask);
color = vec4(1.0 - source.a) * color + source;
}

// Get screen-space derivative of texture coordinate t representing the 
normalized distance
// between 2 pixels. dFd*() unfortunately have to be called outside of 
branches in order to work
// correctly with VMware's 

[Touch-packages] [Bug 1455107] Re: Creating and destroying SoundEffects causes crashes

[Ricardo Salveti]

** Also affects: qtmultimedia-opensource-src (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Creating and destroying SoundEffects causes crashes

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in qtmultimedia-opensource-src package in Ubuntu:
  New

Bug description:
  I keep on receiving bug reports about Machines vs. Machines being
  crashy on Ubuntu Phones and I tracked it down to the SoundEffect item.
  When playing without sound effects enabled, the game seems very
  stable.

  To get to the bottom of this I created an app that simulates a bit how
  a game works with sound effects. It's a bit more aggressive than
  Machines-vs-Machines (still not really far fetched from a real game
  scenario) and reliably triggers some crashers in less than a minute
  here.

  So far I've seen crashes in creating SoundEffects items as well as
  removing them from the scene.

  Please find the example here: lp:~mzanetti/+junk/soundcrasher

  You should be able to run it on any vivid powered device by just
  opening the .pro file in QtCreator and hit the play button. The logs
  vary a lot between crashes. Sometimes I get some PulseAudio messages,
  sometimes it just crashes without any. Probably some raciness. Anyhow,
  this example app should be give the system a hard time and reveal most
  of the crashes eventually.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1455107/+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 1378048] Re: Make music controls work in the sound indicator

[Ricardo Salveti]

Adding task for indicator-sound again as the new UX spec requires
changes for the indicator as well.

** Changed in: indicator-sound (Ubuntu)
   Status: Invalid = Confirmed

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

Title:
  Make music controls work in the sound indicator

Status in the base for Ubuntu mobile products:
  Confirmed
Status in indicator-sound package in Ubuntu:
  Confirmed
Status in media-hub package in Ubuntu:
  Confirmed

Bug description:
  Steps:
  1. Play an album in the music player
  2. Pull down sound indicator
  3. Click forward button

  Observed: the music does not advance
  Expected: the music advances

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1378048/+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 1452300] Re: Reboot takes too long

[Ricardo Salveti]

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

** Also affects: powerd (Ubuntu RTM)
   Importance: Undecided
   Status: New

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

Title:
  Reboot takes too long

Status in the base for Ubuntu mobile products:
  New
Status in powerd package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete
Status in powerd package in Ubuntu RTM:
  New

Bug description:
  Test case.
  - In the greeter screen, long press power button to display power dialog.
  - Tap to reboot.

  Expected result.
  - Must take similar time than stable.

  Actual result.
  - Stable takes 30 seconds to show the bq white screen.
  - 274 takes bewteen than 2 and 3 minutes to show the bq screen.

  syslog:

  May  6 14:16:35 ubuntu-phablet rsyslogd: [origin software=rsyslogd 
swVersion=7.4.4 x-pid=816 x-info=http://w
  ww.rsyslog.com] exiting on signal 15.
  May  6 14:20:05 ubuntu-phablet rsyslogd: [origin software=rsyslogd 
swVersion=7.4.4 x-pid=817 x-info=http://w
  ww.rsyslog.com] start

  current build number: 274
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1452300/+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 1452300] Re: Reboot takes too long

[Ricardo Salveti]

** Description changed:

  Test case.
+ - Without usb cable connected
  - In the greeter screen, long press power button to display power dialog.
  - Tap to reboot.
  
  Expected result.
  - Must take similar time than stable.
  
  Actual result.
  - Stable takes 30 seconds to show the bq white screen.
  - 274 takes bewteen than 2 and 3 minutes to show the bq screen.
  
  syslog:
  
  May  6 14:16:35 ubuntu-phablet rsyslogd: [origin software=rsyslogd 
swVersion=7.4.4 x-pid=816 x-info=http://w
  ww.rsyslog.com] exiting on signal 15.
  May  6 14:20:05 ubuntu-phablet rsyslogd: [origin software=rsyslogd 
swVersion=7.4.4 x-pid=817 x-info=http://w
  ww.rsyslog.com] start
  
  current build number: 274
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed

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

Title:
  Reboot takes too long

Status in the base for Ubuntu mobile products:
  New
Status in powerd package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete
Status in powerd source package in Vivid:
  New
Status in powerd package in Ubuntu RTM:
  New

Bug description:
  Test case.
  - Make sure phone is not plugged in.
  - In the greeter screen, long press power button to display power dialog.
  - Tap to reboot.

  Expected result.
  - Must take similar time than stable.

  Actual result.
  - Stable takes 30 seconds to show the bq white screen.
  - 274 takes bewteen than 2 and 3 minutes to show the bq screen.

  syslog:

  May  6 14:16:35 ubuntu-phablet rsyslogd: [origin software=rsyslogd 
swVersion=7.4.4 x-pid=816 x-info=http://w
  ww.rsyslog.com] exiting on signal 15.
  May  6 14:20:05 ubuntu-phablet rsyslogd: [origin software=rsyslogd 
swVersion=7.4.4 x-pid=817 x-info=http://w
  ww.rsyslog.com] start

  current build number: 274
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1452300/+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 1452300] Re: Reboot takes too long

[Ricardo Salveti]

Problem is that we can only reproduce this issue without a usb cable, as
that makes the kernel to acquire a wakelock.

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

Title:
  Reboot takes too long

Status in the base for Ubuntu mobile products:
  New
Status in powerd package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete
Status in powerd source package in Vivid:
  New
Status in powerd package in Ubuntu RTM:
  New

Bug description:
  Test case.
  - Make sure phone is not plugged in.
  - In the greeter screen, long press power button to display power dialog.
  - Tap to reboot.

  Expected result.
  - Must take similar time than stable.

  Actual result.
  - Stable takes 30 seconds to show the bq white screen.
  - 274 takes bewteen than 2 and 3 minutes to show the bq screen.

  syslog:

  May  6 14:16:35 ubuntu-phablet rsyslogd: [origin software=rsyslogd 
swVersion=7.4.4 x-pid=816 x-info=http://w
  ww.rsyslog.com] exiting on signal 15.
  May  6 14:20:05 ubuntu-phablet rsyslogd: [origin software=rsyslogd 
swVersion=7.4.4 x-pid=817 x-info=http://w
  ww.rsyslog.com] start

  current build number: 274
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1452300/+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 1425880] Re: location settings doesn't persist upon reboot

[Ricardo Salveti]

** Changed in: lxc-android-config (Ubuntu RTM)
   Status: New = Fix Released

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

Title:
  location settings doesn't persist upon reboot

Status in the base for Ubuntu mobile products:
  Fix Released
Status in lxc-android-config package in Ubuntu:
  Fix Released
Status in lxc-android-config package in Ubuntu RTM:
  Fix Released

Bug description:
  current build number: 122
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-02-25 15:06:29
  version version: 122
  version ubuntu: 20150225
  version device: 20150210-95b6a9f
  version custom: 20150225

  Test Case
  1. Open System-Settings = Security  Privacy = Location Access
  2. Select 'Not at all' option from the list to turn the location access off
  3. Close the system settings and reboot the phone

  Verify that location settings changes are persistent after the boot

  Actual Result
  Location is enabled after reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubuntu-location-service-bin 2.1+15.04.20150126.1-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: armhf
  Date: Thu Feb 26 10:54:26 2015
  InstallationDate: Installed on 2015-02-25 (1 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150225-020204)
  SourcePackage: location-service
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.init.ubuntu.location.service.conf: 2015-02-10T21:38:59

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425880/+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 1425880] Re: location settings doesn't persist upon reboot

[Ricardo Salveti]

** Also affects: lxc-android-config (Ubuntu RTM)
   Importance: Undecided
   Status: New

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

Title:
  location settings doesn't persist upon reboot

Status in the base for Ubuntu mobile products:
  Fix Released
Status in lxc-android-config package in Ubuntu:
  Fix Released
Status in lxc-android-config package in Ubuntu RTM:
  New

Bug description:
  current build number: 122
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-02-25 15:06:29
  version version: 122
  version ubuntu: 20150225
  version device: 20150210-95b6a9f
  version custom: 20150225

  Test Case
  1. Open System-Settings = Security  Privacy = Location Access
  2. Select 'Not at all' option from the list to turn the location access off
  3. Close the system settings and reboot the phone

  Verify that location settings changes are persistent after the boot

  Actual Result
  Location is enabled after reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubuntu-location-service-bin 2.1+15.04.20150126.1-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: armhf
  Date: Thu Feb 26 10:54:26 2015
  InstallationDate: Installed on 2015-02-25 (1 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150225-020204)
  SourcePackage: location-service
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.init.ubuntu.location.service.conf: 2015-02-10T21:38:59

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425880/+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 1426923] Re: Allow ubuntu-system-settings to set a device's firmware

[Ricardo Salveti]

** Package changed: wpasupplicant (Ubuntu) = lxc-android-config
(Ubuntu)

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

Title:
  Allow ubuntu-system-settings to set a device's firmware

Status in lxc-android-config package in Ubuntu:
  In Progress

Bug description:
  Background:
  To do Wi-Fi hotspots on krillin, we need to poke wifi by doing a call to 
wpa_supplicant's (undocumented/local) SetInterfaceFirmware method. See [1] for 
details.

  Rationale:
  Ubuntu System Settings needs to do the same things as aforementioned script, 
but via dbus [2], as phablet/current non-privileged user and unconfined.

  What happens:
  If phablet runs [2], this error message [3] is produced, which I interpret to 
be equivalent with you're not welcome here.

  What should happen instead:
  Ubuntu System Settings should be able to make the call to wpa.

  [1] 
http://bazaar.launchpad.net/~mathieu-tl/+junk/touch-hotspot/view/head:/hotspot.py
  [2] gdbus call --system -d fi.w1.wpa_supplicant1 -o /fi/w1/wpa_supplicant1 -m 
fi.w1.wpa_supplicant1.SetInterfaceFirmware / ap
  [3] http://pastebin.ubuntu.com/10489519/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1426923/+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 1450568] Re: Requests are not cleared if a client dies unexpectedly and drops from the bus

[Ricardo Mendoza]

** Changed in: powerd (Ubuntu)
 Assignee: (unassigned) = Ricardo Mendoza (ricmm)

** Changed in: powerd (Ubuntu)
   Status: New = In Progress

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

Title:
  Requests are not cleared if a client dies unexpectedly and drops from
  the bus

Status in the base for Ubuntu mobile products:
  New
Status in PowerD:
  In Progress
Status in powerd package in Ubuntu:
  In Progress

Bug description:
  Power requests (wakelocks) are not released if the owner process
  unexpectedly exits and drops off the bus. This causes a stale request
  that holds the device awake, which can result in extreme battery
  drain.

  For example, the vibration sensor can unexpectedly die while holding a
  vibration/alarm lock and at the point the phone would never again
  suspend.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1450568/+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 1425880] Re: location settings doesn't persist upon reboot

[Ricardo Salveti]

** Changed in: canonical-devices-system-image
   Status: Confirmed = Fix Released

** Changed in: lxc-android-config (Ubuntu)
   Status: Confirmed = Fix Released

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

Title:
  location settings doesn't persist upon reboot

Status in the base for Ubuntu mobile products:
  Fix Released
Status in lxc-android-config package in Ubuntu:
  Fix Released

Bug description:
  current build number: 122
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-02-25 15:06:29
  version version: 122
  version ubuntu: 20150225
  version device: 20150210-95b6a9f
  version custom: 20150225

  Test Case
  1. Open System-Settings = Security  Privacy = Location Access
  2. Select 'Not at all' option from the list to turn the location access off
  3. Close the system settings and reboot the phone

  Verify that location settings changes are persistent after the boot

  Actual Result
  Location is enabled after reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubuntu-location-service-bin 2.1+15.04.20150126.1-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: armhf
  Date: Thu Feb 26 10:54:26 2015
  InstallationDate: Installed on 2015-02-25 (1 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150225-020204)
  SourcePackage: location-service
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.init.ubuntu.location.service.conf: 2015-02-10T21:38:59

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425880/+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 1449580] Re: [arale] photos taken by camera are corrupt

[Ricardo Salveti]

** Changed in: canonical-devices-system-image
   Status: In Progress = Fix Released

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

Title:
  [arale] photos taken by camera are corrupt

Status in the base for Ubuntu mobile products:
  Fix Released
Status in camera-app package in Ubuntu:
  Invalid
Status in qtubuntu-camera package in Ubuntu:
  Invalid

Bug description:
  This is arale specifc bug

  Took pictures with camera
  Go to photo roll
  Photo is black, spinner keeps spinning
  The photo is written to disk, but is corrupt when opening

  I am attaching photo

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1449580/+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 1449580] Re: photos taken by camera are corrupt

[Ricardo Salveti]

I think this is basically the same issue we had with krillin, which I
just pushed to arale. I already triggered a new build including this fix
on the device side, so next image should have it.

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: camera-app (Ubuntu)
   Status: New = Invalid

** Changed in: qtubuntu-camera (Ubuntu)
   Status: New = Invalid

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) = Ricardo Salveti (rsalveti)

** Summary changed:

- photos taken by camera are corrupt
+ [arale] photos taken by camera are corrupt

** Changed in: canonical-devices-system-image
   Status: New = In Progress

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

Title:
  [arale] photos taken by camera are corrupt

Status in the base for Ubuntu mobile products:
  In Progress
Status in camera-app package in Ubuntu:
  Invalid
Status in qtubuntu-camera package in Ubuntu:
  Invalid

Bug description:
  This is arale specifc bug

  Took pictures with camera
  Go to photo roll
  Photo is black, spinner keeps spinning
  The photo is written to disk, but is corrupt when opening

  I am attaching photo

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1449580/+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 1449576] Re: embedded thumbnails not generated correctly

[Ricardo Salveti]

I think this is basically the same issue we had with krillin, which I
just pushed to arale. I already triggered a new build including this fix
on the device side, so next image should have it.

** Package changed: qtubuntu-camera (Ubuntu) = canonical-devices-
system-image

** Changed in: canonical-devices-system-image
   Status: New = In Progress

** Summary changed:

- embedded thumbnails not generated correctly
+ [arale] embedded thumbnails not generated correctly

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

Title:
  [arale] embedded thumbnails not generated correctly

Status in the base for Ubuntu mobile products:
  In Progress

Bug description:
  This is arale only bug

  Open camera-app and take picture
  Go to photo roll
  Notice the thumbnails are not at the correct aspect ration
  use exiv2 to extract thumbnail out of jpeg and you can see the embedded 
thumbnail is not correct

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1449576/+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 1425880] Re: location settings doesn't persist upon reboot

[Ricardo Salveti]

** Package changed: location-service (Ubuntu) = lxc-android-config
(Ubuntu)

** Changed in: lxc-android-config (Ubuntu)
 Assignee: Manuel de la Peña (mandel) = Ricardo Salveti (rsalveti)

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

Title:
  location settings doesn't persist upon reboot

Status in the base for Ubuntu mobile products:
  Confirmed
Status in lxc-android-config package in Ubuntu:
  Confirmed

Bug description:
  current build number: 122
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-02-25 15:06:29
  version version: 122
  version ubuntu: 20150225
  version device: 20150210-95b6a9f
  version custom: 20150225

  Test Case
  1. Open System-Settings = Security  Privacy = Location Access
  2. Select 'Not at all' option from the list to turn the location access off
  3. Close the system settings and reboot the phone

  Verify that location settings changes are persistent after the boot

  Actual Result
  Location is enabled after reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubuntu-location-service-bin 2.1+15.04.20150126.1-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: armhf
  Date: Thu Feb 26 10:54:26 2015
  InstallationDate: Installed on 2015-02-25 (1 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150225-020204)
  SourcePackage: location-service
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.init.ubuntu.location.service.conf: 2015-02-10T21:38:59

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425880/+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 1447606] [NEW] incoming call ringtone is not played repeatedly

[Ricardo Salveti]

Public bug reported:

Mako/arale/krillin device, r196, ubuntu-touch/vivid-proposed

Steps
1. Call the ubuntu phone from another phone
2. Don't answer it

Expect
Incoming call ringtone should be played repeatedly

Result
Ringtone is only played once.

** Affects: canonical-devices-system-image
 Importance: Critical
 Assignee: Bill Filler (bfiller)
 Status: Confirmed

** Affects: telephony-service (Ubuntu)
 Importance: Critical
 Assignee: Tiago Salem Herrmann (tiagosh)
 Status: Confirmed

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

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

Title:
   incoming call ringtone is not played repeatedly

Status in the base for Ubuntu mobile products:
  Confirmed
Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  Mako/arale/krillin device, r196, ubuntu-touch/vivid-proposed

  Steps
  1. Call the ubuntu phone from another phone
  2. Don't answer it

  Expect
  Incoming call ringtone should be played repeatedly

  Result
  Ringtone is only played once.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447606/+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 1447376] Re: obexd fails to stop

[Ricardo Salveti]

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

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

Title:
  obexd fails to stop

Status in the base for Ubuntu mobile products:
  New
Status in ubuntu-touch-session package in Ubuntu:
  New

Bug description:
  Current obexd job fails to stop/restart, as the upstart job is
  expecting daemon instead of fork.

  This affect the shutdown process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447376/+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 1425625] Re: Vivid image 121: Gps tag is permanently turn off on krillin when the custom tarball is installed

[Ricardo Salveti]

We landed a change in indicator-location that should help fixing this
issue. Can you try reproducing again but using the channel ubuntu-touch
/vivid-proposed-customized-here instead?

** Changed in: indicator-location (Ubuntu)
   Status: New = Incomplete

** Changed in: canonical-devices-system-image
   Status: Confirmed = Incomplete

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

Title:
  Vivid image 121: Gps tag is permanently turn off on krillin when the
  custom tarball is installed

Status in the base for Ubuntu mobile products:
  Incomplete
Status in indicator-location package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  1. Install image 121 and install the krillin custom tarball
  2. Boot the device and use the recommend here location check box  in the 
location page
  3. Drag down the location indicator
  4. Enable gps
  5. drag down the indicator
  6. enable gps a second time
  7. reboot the device once gps stays on
  8. check the locations indicator again

  EXPECTED:
  I expect to see happen what happens on rtm

  ACTUAL:
  Gps is turned off on reboot, and doesn't function when enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425625/+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 1442166] Re: Calendar alarms rings forever if Low Battery dialog visible

[Ricardo Salveti]

** Changed in: canonical-devices-system-image
   Status: Confirmed = In Progress

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

Title:
  Calendar alarms rings forever if Low Battery dialog visible

Status in the base for Ubuntu mobile products:
  In Progress
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in usensord package in Ubuntu:
  Confirmed

Bug description:
  I'm on rtm build 258 on krillin

  Steps to reproduce:
  - let battery run down on phone (was sitting unplugged for 1 or 2 days)
  - in the morning, a calendar alarm starting ringing/vibrating and would not 
stop
  - when I looked at the phone, the screen was on and I see the Low Battery 
dialog
  - after dismissing the dialog, then I see the notification for the alarm, and 
only after 5-10 more seconds does the ringing stop

  Seems like while the Low Battery dialog is displayed it keeps the
  alarm ringing forever

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1442166/+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 1447376] [NEW] obexd fails to stop

[Ricardo Salveti]

Public bug reported:

Current obexd job fails to stop/restart, as the upstart job is expecting
daemon instead of fork.

This affect the shutdown process.

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

** Description changed:

  Current obexd job fails to stop/restart, as the upstart job is expecting
  daemon instead of fork.
+ 
+ This affect the shutdown process.

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

Title:
  obexd fails to stop

Status in ubuntu-touch-session package in Ubuntu:
  New

Bug description:
  Current obexd job fails to stop/restart, as the upstart job is
  expecting daemon instead of fork.

  This affect the shutdown process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-session/+bug/1447376/+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 1224756] Re: Pulseaudio should integrate with trust-store

[Ricardo Salveti]

Please move this to ww21.

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

Title:
  Pulseaudio should integrate with trust-store

Status in the base for Ubuntu mobile products:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  Currently the 'audio' policy group allows access to pulseaudio which
  allows apps to use the microphone and eavesdrop on the user.
  Pulseaudio needs to be modified to use trust-store, like location-
  service does. Integrating with trust-store means that when an app
  tries use the microphone via pulseaudio, pulseaudio will contact
  trust-store, the trust-store will prompt the user (Foo wants to use
  the microphone. Is this ok? Yes|No), optionally cache the result and
  return the result to pulseaudio. In this manner the user is given a
  contextual prompt at the time of access by the app. Using caching this
  decision can be remembered the next time. If caching is used, there
  should be a method to change the decision in settings.

  Targeting to T-Series for now, since the trust-store is not in a
  reusable form yet.

  Original description:
  David and the security team (inspired by an observation from Rick) discussed 
that when recording, pulseaudio should somehow unobtrusively show the user that 
it is recording. The easiest thing to do would be for pulseaudio to alert 
indicator-sound which would then turn its icon red (similar to 
indicator-message turning blue with new messages). Marking 'high' because apps 
with access to pulseaudio can currently eavedrop on users. If the app is 
allowed to do networking (the default for apps), then it can ship that 
information off to a server somewhere.

  Note 1, the alert to indicator-sound must happen via the out of
  process pulseaudio server and not the confined app itself to be
  effective.

  Note 2, we should consider how to enforce this for foreground apps
  only. Application lifecycle should probably handle this for 13.10
  (apps are suspended if not in foreground or if the screensaver is on),
  but we don't want an app on the converged device to record in the
  background when the user isn't paying attention. Example eavesdropping
  attack: start recording only when the screensaver is on (perhaps
  inhibiting the screensaver during recording would be enough).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1224756/+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