[Touch-packages] [Bug 2046624] Re: apparmor breaks surfshark vpn

[Rick S]

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

Late for the party, But>>> Verified on KVM install
   
"Active apt repos in: 
/etc/apt/sources.list.d/apparmor-dev-ubuntu-unprivileged-userns-noble.sources
1: deb 
https://ppa.launchpadcontent.net/apparmor-dev/unprivileged-userns/ubuntu/ noble 
main
"
And 
"sudo aa-status |grep Surfshark*
   /opt/Surfshark/surfshark (2399) surfshark
   /opt/Surfshark/surfshark (2636) surfshark
   /opt/Surfshark/surfshark (2637) surfshark
   /opt/Surfshark/surfshark (2668) surfshark
   /opt/Surfshark/chrome_crashpad_handler (2720) surfshark
   /opt/Surfshark/surfshark (2770) surfshark
   /opt/Surfshark/surfshark (2777) surfshark
   /opt/Surfshark/surfshark (2793) surfshark
"

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

Title:
  apparmor breaks surfshark vpn

Status in apparmor package in Ubuntu:
  New

Bug description:
  with the new   apparmor Candidate: 4.0.0~alpha2-0ubuntu7
  Breaks my VPN

 *surfshark
  [33104:1216/072144.904027:FATAL:credentials.cc(127)] Check failed: . : 
Permission denied (13)
  Trace/breakpoint trap

  It will work with --no-sandbox "surfshark --no-sandbox" not ideal.
  I removed apparmor for proof

  *apt policy apparmor
  apparmor:
Installed: (none)
Candidate: 4.0.0~alpha2-0ubuntu7
Version table:
   4.0.0~alpha2-0ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu noble/main amd64 Packages
  Now my VPN works as expected, spent 2 hrs this morning with surfshark 
support, they will get back to me in a day or two, but they can't find anything 
wrong on their end.

  So far it points to apparmor

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: apparmor (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Sat Dec 16 10:40:00 2023
  InstallationDate: Installed on 2023-12-10 (6 days ago)
  InstallationMedia: Xubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
  SourcePackage: apparmor
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-12-12T09:43:48.905263

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046624/+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 2046624] Re: apparmor breaks surfshark vpn

[Rick S]

@jjohansen that link come in pretty handy.
I will link to it when helping others

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

Title:
  apparmor breaks surfshark vpn

Status in apparmor package in Ubuntu:
  New

Bug description:
  with the new   apparmor Candidate: 4.0.0~alpha2-0ubuntu7
  Breaks my VPN

 *surfshark
  [33104:1216/072144.904027:FATAL:credentials.cc(127)] Check failed: . : 
Permission denied (13)
  Trace/breakpoint trap

  It will work with --no-sandbox "surfshark --no-sandbox" not ideal.
  I removed apparmor for proof

  *apt policy apparmor
  apparmor:
Installed: (none)
Candidate: 4.0.0~alpha2-0ubuntu7
Version table:
   4.0.0~alpha2-0ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu noble/main amd64 Packages
  Now my VPN works as expected, spent 2 hrs this morning with surfshark 
support, they will get back to me in a day or two, but they can't find anything 
wrong on their end.

  So far it points to apparmor

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: apparmor (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Sat Dec 16 10:40:00 2023
  InstallationDate: Installed on 2023-12-10 (6 days ago)
  InstallationMedia: Xubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
  SourcePackage: apparmor
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-12-12T09:43:48.905263

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046624/+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 2046624] Re: apparmor breaks surfshark vpn

[Rick S]

Sure thing

nano /etc/apparmor.d/surfshark

   *abi ,
include 

profile surfshark /opt/Surfshark/surfshark flags=(unconfined) {
  userns,

  # Site-specific additions and overrides. See local/README for details.
  include if exists 
}
Reload apparmor and presto.
Reboots are golden

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

Title:
  apparmor breaks surfshark vpn

Status in apparmor package in Ubuntu:
  New

Bug description:
  with the new   apparmor Candidate: 4.0.0~alpha2-0ubuntu7
  Breaks my VPN

 *surfshark
  [33104:1216/072144.904027:FATAL:credentials.cc(127)] Check failed: . : 
Permission denied (13)
  Trace/breakpoint trap

  It will work with --no-sandbox "surfshark --no-sandbox" not ideal.
  I removed apparmor for proof

  *apt policy apparmor
  apparmor:
Installed: (none)
Candidate: 4.0.0~alpha2-0ubuntu7
Version table:
   4.0.0~alpha2-0ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu noble/main amd64 Packages
  Now my VPN works as expected, spent 2 hrs this morning with surfshark 
support, they will get back to me in a day or two, but they can't find anything 
wrong on their end.

  So far it points to apparmor

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: apparmor (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Sat Dec 16 10:40:00 2023
  InstallationDate: Installed on 2023-12-10 (6 days ago)
  InstallationMedia: Xubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
  SourcePackage: apparmor
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-12-12T09:43:48.905263

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046624/+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 2046624] Re: apparmor breaks surfshark vpn

[Rick S]

Bingo, it worked, and this is new but spot on

*"programs using userns (often used for sandboxing) now _must have_ an
AppArmor profile."

**Thanks cboltz :-)

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

Title:
  apparmor breaks surfshark vpn

Status in apparmor package in Ubuntu:
  New

Bug description:
  with the new   apparmor Candidate: 4.0.0~alpha2-0ubuntu7
  Breaks my VPN

 *surfshark
  [33104:1216/072144.904027:FATAL:credentials.cc(127)] Check failed: . : 
Permission denied (13)
  Trace/breakpoint trap

  It will work with --no-sandbox "surfshark --no-sandbox" not ideal.
  I removed apparmor for proof

  *apt policy apparmor
  apparmor:
Installed: (none)
Candidate: 4.0.0~alpha2-0ubuntu7
Version table:
   4.0.0~alpha2-0ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu noble/main amd64 Packages
  Now my VPN works as expected, spent 2 hrs this morning with surfshark 
support, they will get back to me in a day or two, but they can't find anything 
wrong on their end.

  So far it points to apparmor

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: apparmor (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Sat Dec 16 10:40:00 2023
  InstallationDate: Installed on 2023-12-10 (6 days ago)
  InstallationMedia: Xubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
  SourcePackage: apparmor
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-12-12T09:43:48.905263

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046624/+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 2046624] Re: apparmor breaks surfshark vpn

[Rick S]

sudo aa-status |grep surfshark
   surfshark

will reboot to see

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

Title:
  apparmor breaks surfshark vpn

Status in apparmor package in Ubuntu:
  New

Bug description:
  with the new   apparmor Candidate: 4.0.0~alpha2-0ubuntu7
  Breaks my VPN

 *surfshark
  [33104:1216/072144.904027:FATAL:credentials.cc(127)] Check failed: . : 
Permission denied (13)
  Trace/breakpoint trap

  It will work with --no-sandbox "surfshark --no-sandbox" not ideal.
  I removed apparmor for proof

  *apt policy apparmor
  apparmor:
Installed: (none)
Candidate: 4.0.0~alpha2-0ubuntu7
Version table:
   4.0.0~alpha2-0ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu noble/main amd64 Packages
  Now my VPN works as expected, spent 2 hrs this morning with surfshark 
support, they will get back to me in a day or two, but they can't find anything 
wrong on their end.

  So far it points to apparmor

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: apparmor (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Sat Dec 16 10:40:00 2023
  InstallationDate: Installed on 2023-12-10 (6 days ago)
  InstallationMedia: Xubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
  SourcePackage: apparmor
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-12-12T09:43:48.905263

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046624/+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 2046624] Re: apparmor breaks surfshark vpn

[Rick S]

Here
  *└─> sudo dmesg | grep DENIED
[sudo] password for me: 
┌───>
│~ 
└─>

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

Title:
  apparmor breaks surfshark vpn

Status in apparmor package in Ubuntu:
  New

Bug description:
  with the new   apparmor Candidate: 4.0.0~alpha2-0ubuntu7
  Breaks my VPN

 *surfshark
  [33104:1216/072144.904027:FATAL:credentials.cc(127)] Check failed: . : 
Permission denied (13)
  Trace/breakpoint trap

  It will work with --no-sandbox "surfshark --no-sandbox" not ideal.
  I removed apparmor for proof

  *apt policy apparmor
  apparmor:
Installed: (none)
Candidate: 4.0.0~alpha2-0ubuntu7
Version table:
   4.0.0~alpha2-0ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu noble/main amd64 Packages
  Now my VPN works as expected, spent 2 hrs this morning with surfshark 
support, they will get back to me in a day or two, but they can't find anything 
wrong on their end.

  So far it points to apparmor

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: apparmor (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Sat Dec 16 10:40:00 2023
  InstallationDate: Installed on 2023-12-10 (6 days ago)
  InstallationMedia: Xubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
  SourcePackage: apparmor
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-12-12T09:43:48.905263

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046624/+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 2046624] Re: apparmor breaks surfshark vpn

[Rick S]

journalctl -b -1 -g DENIED --no-pager
-- No entries --
┌───>
│~ 
└─> journalctl -b -1 -g ALLOWED --no-pager
-- No entries --

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

Title:
  apparmor breaks surfshark vpn

Status in apparmor package in Ubuntu:
  New

Bug description:
  with the new   apparmor Candidate: 4.0.0~alpha2-0ubuntu7
  Breaks my VPN

 *surfshark
  [33104:1216/072144.904027:FATAL:credentials.cc(127)] Check failed: . : 
Permission denied (13)
  Trace/breakpoint trap

  It will work with --no-sandbox "surfshark --no-sandbox" not ideal.
  I removed apparmor for proof

  *apt policy apparmor
  apparmor:
Installed: (none)
Candidate: 4.0.0~alpha2-0ubuntu7
Version table:
   4.0.0~alpha2-0ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu noble/main amd64 Packages
  Now my VPN works as expected, spent 2 hrs this morning with surfshark 
support, they will get back to me in a day or two, but they can't find anything 
wrong on their end.

  So far it points to apparmor

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: apparmor (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Sat Dec 16 10:40:00 2023
  InstallationDate: Installed on 2023-12-10 (6 days ago)
  InstallationMedia: Xubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
  SourcePackage: apparmor
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-12-12T09:43:48.905263

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046624/+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 2046624] Re: apparmor breaks surfshark vpn

[Rick S]

After reboot with apparmor active

   * systemctl status surfsharkd2.service 
● surfsharkd2.service - Surfshark Daemon2
 Loaded: loaded (/lib/systemd/system/surfsharkd2.service; enabled; preset: 
enabled)
 Active: active (running) since Sat 2023-12-16 13:30:24 MST; 1min 12s ago
   Main PID: 1742 (surfsharkd2.js)
  Tasks: 12 (limit: 18861)
 Memory: 14.0M
CPU: 156ms
 CGroup: /system.slice/surfsharkd2.service
 └─1742 /usr/bin/gjs 
/opt/Surfshark/resources/dist/resources/surfsharkd2.js

Dec 16 13:30:24 me-Legion-5-zfs systemd[1]: Started surfsharkd2.service - 
Surfshark Daem>
┌───>
│~ 
└─> surfshark
[5927:1216/133159.791330:FATAL:credentials.cc(127)] Check failed: . : 
Permission denied (13)
Trace/breakpoint trap

With --no-sandbox
 
   *surfshark --no-sandbox
[6392:1216/133222.506292:ERROR:object_proxy.cc(590)] Failed to call method: 
org.freedesktop.portal.Settings.Read: object_path= 
/org/freedesktop/portal/desktop: org.freedesktop.DBus.Error.UnknownMethod: No 
such interface “org.freedesktop.portal.Settings” on object at path 
/org/freedesktop/portal/desktop

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

Title:
  apparmor breaks surfshark vpn

Status in apparmor package in Ubuntu:
  New

Bug description:
  with the new   apparmor Candidate: 4.0.0~alpha2-0ubuntu7
  Breaks my VPN

 *surfshark
  [33104:1216/072144.904027:FATAL:credentials.cc(127)] Check failed: . : 
Permission denied (13)
  Trace/breakpoint trap

  It will work with --no-sandbox "surfshark --no-sandbox" not ideal.
  I removed apparmor for proof

  *apt policy apparmor
  apparmor:
Installed: (none)
Candidate: 4.0.0~alpha2-0ubuntu7
Version table:
   4.0.0~alpha2-0ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu noble/main amd64 Packages
  Now my VPN works as expected, spent 2 hrs this morning with surfshark 
support, they will get back to me in a day or two, but they can't find anything 
wrong on their end.

  So far it points to apparmor

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: apparmor (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Sat Dec 16 10:40:00 2023
  InstallationDate: Installed on 2023-12-10 (6 days ago)
  InstallationMedia: Xubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
  SourcePackage: apparmor
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-12-12T09:43:48.905263

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046624/+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 2046624] Re: apparmor breaks surfshark vpn

[Rick S]

aa-status
apparmor module is loaded.
100 profiles are loaded.
31 profiles are in enforce mode.
   /usr/bin/man
   /usr/lib/NetworkManager/nm-dhcp-client.action
   /usr/lib/NetworkManager/nm-dhcp-helper
   /usr/lib/connman/scripts/dhclient-script
   /usr/lib/cups/backend/cups-pdf
   /usr/lib/lightdm/lightdm-guest-session
   /usr/lib/lightdm/lightdm-guest-session//chromium
   /usr/sbin/cups-browsed
   /usr/sbin/cupsd
   /usr/sbin/cupsd//third_party
   /{,usr/}sbin/dhclient
   firefox
   firefox//browser_java
   firefox//browser_openjdk
   firefox//lsb_release
   firefox//sanitized_helper
   firejail-default
   libreoffice-senddoc
   libreoffice-soffice//gpg
   libreoffice-xpdfimport
   libvirtd
   libvirtd//qemu_bridge_helper
   lsb_release
   man_filter
   man_groff
   nvidia_modprobe
   nvidia_modprobe//kmod
   rsyslogd
   swtpm
   tcpdump
   virt-aa-helper
2 profiles are in complain mode.
   libreoffice-oosplash
   libreoffice-soffice
0 profiles are in prompt mode.
0 profiles are in kill mode.
67 profiles are in unconfined mode.
   /bin/toybox
   /opt/brave.com/brave/brave
   /opt/google/chrome/chrome
   /opt/microsoft/msedge/msedge
   /opt/vivaldi/vivaldi-bin
   /usr/bin/buildah
   /usr/bin/busybox
   /usr/bin/cam
   /usr/bin/ch-checkns
   /usr/bin/ch-run
   /usr/bin/crun
   /usr/bin/flatpak
   /usr/bin/ipa_verify
   /usr/bin/lc-compliance
   /usr/bin/libcamerify
   /usr/bin/lxc-attach
   /usr/bin/lxc-create
   /usr/bin/lxc-destroy
   /usr/bin/lxc-execute
   /usr/bin/lxc-stop
   /usr/bin/lxc-unshare
   /usr/bin/lxc-usernsexec
   /usr/bin/mmdebstrap
   /usr/bin/podman
   /usr/bin/qcam
   /usr/bin/rootlesskit
   /usr/bin/rpm
   /usr/bin/sbuild
   /usr/bin/sbuild-abort
   /usr/bin/sbuild-apt
   /usr/bin/sbuild-checkpackages
   /usr/bin/sbuild-clean
   /usr/bin/sbuild-createchroot
   /usr/bin/sbuild-distupgrade
   /usr/bin/sbuild-hold
   /usr/bin/sbuild-shell
   /usr/bin/sbuild-unhold
   /usr/bin/sbuild-update
   /usr/bin/sbuild-upgrade
   /usr/bin/slirp4netns
   /usr/bin/stress-ng
   /usr/bin/thunderbird
   /usr/bin/trinity
   /usr/bin/tup
   /usr/bin/userbindmount
   /usr/bin/uwsgi-core
   /usr/bin/vdens
   /usr/bin/vpnns
   /usr/lib/*-linux-gnu*/qt5/libexec/QtWebEngineProcess
   /usr/lib/qt6/libexec/QtWebEngineProcess
   /usr/libexec/*-linux-gnu*/bazel/linux-sandbox
   /usr/libexec/virtiofsd
   /usr/sbin/runc
   /usr/sbin/sbuild-adduser
   /usr/sbin/sbuild-destroychroot
   1password
   Discord
   MongoDB Compass
   code
   github-desktop
   obsidian
   opera
   polypane
   signal-desktop
   slack
   steam
   wpcom
2 processes have profiles defined.
0 processes are in enforce mode.
0 processes are in complain mode.
0 processes are in prompt mode.
0 processes are in kill mode.
2 processes are unconfined but have a profile defined.
   /usr/sbin/cups-browsed (2749) 
   /usr/sbin/cupsd (1929) 
0 processes are in mixed mode.

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

Title:
  apparmor breaks surfshark vpn

Status in apparmor package in Ubuntu:
  New

Bug description:
  with the new   apparmor Candidate: 4.0.0~alpha2-0ubuntu7
  Breaks my VPN

 *surfshark
  [33104:1216/072144.904027:FATAL:credentials.cc(127)] Check failed: . : 
Permission denied (13)
  Trace/breakpoint trap

  It will work with --no-sandbox "surfshark --no-sandbox" not ideal.
  I removed apparmor for proof

  *apt policy apparmor
  apparmor:
Installed: (none)
Candidate: 4.0.0~alpha2-0ubuntu7
Version table:
   4.0.0~alpha2-0ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu noble/main amd64 Packages
  Now my VPN works as expected, spent 2 hrs this morning with surfshark 
support, they will get back to me in a day or two, but they can't find anything 
wrong on their end.

  So far it points to apparmor

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: apparmor (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Sat Dec 16 10:40:00 2023
  InstallationDate: Installed on 2023-12-10 (6 days ago)
  InstallationMedia: Xubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
  SourcePackage: apparmor
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-12-12T09:43:48.905263

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


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

[Touch-packages] [Bug 2046624] Re: apparmor breaks surfshark vpn

[Rick S]

With apparmor

   *grep 'network' /etc/apparmor.d/ab*/*
/etc/apparmor.d/abi/3.0:network {af_unix {yes
/etc/apparmor.d/abi/3.0:network_v8 {af_mask {unspec unix inet ax25 ipx 
appletalk netrom bridge atmpvc x25 inet6 rose netbeui security key netlink 
packet ash econet atmsvc rds sna irda pppox wanpipe llc ib mpls can tipc 
bluetooth iucv rxrpc isdn phonet ieee802154 caif alg nfc vsock kcm qipcrtr smc 
xdp
/etc/apparmor.d/abi/4.0:network {af_mask {unspec unix inet ax25 ipx appletalk 
netrom bridge atmpvc x25 inet6 rose netbeui security key netlink packet ash 
econet atmsvc rds sna irda pppox wanpipe llc ib mpls can tipc bluetooth iucv 
rxrpc isdn phonet ieee802154 caif alg nfc vsock kcm qipcrtr smc xdp mctp
/etc/apparmor.d/abi/4.0:network_v8 {af_mask {unspec unix inet ax25 ipx 
appletalk netrom bridge atmpvc x25 inet6 rose netbeui security key netlink 
packet ash econet atmsvc rds sna irda pppox wanpipe llc ib mpls can tipc 
bluetooth iucv rxrpc isdn phonet ieee802154 caif alg nfc vsock kcm qipcrtr smc 
xdp mctp
/etc/apparmor.d/abi/kernel-5.4-outoftree-network:network {af_unix {yes
/etc/apparmor.d/abstractions/apache2-common:  network inet stream,
/etc/apparmor.d/abstractions/apache2-common:  network inet6 stream,
grep: /etc/apparmor.d/abstractions/apparmor_api: Is a directory
grep: /etc/apparmor.d/abstractions/base.d: Is a directory
/etc/apparmor.d/abstractions/dbus-network-manager-strict:  include if exists 

/etc/apparmor.d/abstractions/kde-open5:  include 

/etc/apparmor.d/abstractions/libvirt-qemu:  network inet stream,
/etc/apparmor.d/abstractions/libvirt-qemu:  network inet6 stream,
/etc/apparmor.d/abstractions/libvirt-qemu:  # support for passt network back-end
/etc/apparmor.d/abstractions/nameservice:  # to vast speed increases when 
working with network-based lookups.
/etc/apparmor.d/abstractions/nameservice:  # TCP/UDP network access
/etc/apparmor.d/abstractions/nameservice:  network inet  stream,
/etc/apparmor.d/abstractions/nameservice:  network inet6 stream,
/etc/apparmor.d/abstractions/nameservice:  network inet  dgram,
/etc/apparmor.d/abstractions/nameservice:  network inet6 dgram,
/etc/apparmor.d/abstractions/nameservice:  network netlink raw,
grep: /etc/apparmor.d/abstractions/ubuntu-browsers.d: Is a directory
/etc/apparmor.d/abstractions/ubuntu-helpers:  # Allow all networking
/etc/apparmor.d/abstractions/ubuntu-helpers:  network inet,
/etc/apparmor.d/abstractions/ubuntu-helpers:  network inet6,

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

Title:
  apparmor breaks surfshark vpn

Status in apparmor package in Ubuntu:
  New

Bug description:
  with the new   apparmor Candidate: 4.0.0~alpha2-0ubuntu7
  Breaks my VPN

 *surfshark
  [33104:1216/072144.904027:FATAL:credentials.cc(127)] Check failed: . : 
Permission denied (13)
  Trace/breakpoint trap

  It will work with --no-sandbox "surfshark --no-sandbox" not ideal.
  I removed apparmor for proof

  *apt policy apparmor
  apparmor:
Installed: (none)
Candidate: 4.0.0~alpha2-0ubuntu7
Version table:
   4.0.0~alpha2-0ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu noble/main amd64 Packages
  Now my VPN works as expected, spent 2 hrs this morning with surfshark 
support, they will get back to me in a day or two, but they can't find anything 
wrong on their end.

  So far it points to apparmor

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: apparmor (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Sat Dec 16 10:40:00 2023
  InstallationDate: Installed on 2023-12-10 (6 days ago)
  InstallationMedia: Xubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
  SourcePackage: apparmor
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-12-12T09:43:48.905263

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046624/+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 2046624] Re: apparmor breaks surfshark vpn

[Rick S]

No apparmor still but i will include
  *grep 'network' /etc/apparmor.d/ab*/*
grep: /etc/apparmor.d/abstractions/base.d: Is a directory
/etc/apparmor.d/abstractions/libvirt-qemu:  network inet stream,
/etc/apparmor.d/abstractions/libvirt-qemu:  network inet6 stream,
/etc/apparmor.d/abstractions/libvirt-qemu:  # support for passt network back-end
grep: /etc/apparmor.d/abstractions/ubuntu-browsers.d: Is a directory

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

Title:
  apparmor breaks surfshark vpn

Status in apparmor package in Ubuntu:
  New

Bug description:
  with the new   apparmor Candidate: 4.0.0~alpha2-0ubuntu7
  Breaks my VPN

 *surfshark
  [33104:1216/072144.904027:FATAL:credentials.cc(127)] Check failed: . : 
Permission denied (13)
  Trace/breakpoint trap

  It will work with --no-sandbox "surfshark --no-sandbox" not ideal.
  I removed apparmor for proof

  *apt policy apparmor
  apparmor:
Installed: (none)
Candidate: 4.0.0~alpha2-0ubuntu7
Version table:
   4.0.0~alpha2-0ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu noble/main amd64 Packages
  Now my VPN works as expected, spent 2 hrs this morning with surfshark 
support, they will get back to me in a day or two, but they can't find anything 
wrong on their end.

  So far it points to apparmor

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: apparmor (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Sat Dec 16 10:40:00 2023
  InstallationDate: Installed on 2023-12-10 (6 days ago)
  InstallationMedia: Xubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
  SourcePackage: apparmor
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-12-12T09:43:48.905263

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046624/+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 2046624] Re: apparmor breaks surfshark vpn

[Rick S]

** Information type changed from Private Security to Public Security

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

Title:
  apparmor breaks surfshark vpn

Status in apparmor package in Ubuntu:
  New

Bug description:
  with the new   apparmor Candidate: 4.0.0~alpha2-0ubuntu7
  Breaks my VPN

 *surfshark
  [33104:1216/072144.904027:FATAL:credentials.cc(127)] Check failed: . : 
Permission denied (13)
  Trace/breakpoint trap

  It will work with --no-sandbox "surfshark --no-sandbox" not ideal.
  I removed apparmor for proof

  *apt policy apparmor
  apparmor:
Installed: (none)
Candidate: 4.0.0~alpha2-0ubuntu7
Version table:
   4.0.0~alpha2-0ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu noble/main amd64 Packages
  Now my VPN works as expected, spent 2 hrs this morning with surfshark 
support, they will get back to me in a day or two, but they can't find anything 
wrong on their end.

  So far it points to apparmor

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: apparmor (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Sat Dec 16 10:40:00 2023
  InstallationDate: Installed on 2023-12-10 (6 days ago)
  InstallationMedia: Xubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
  SourcePackage: apparmor
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-12-12T09:43:48.905263

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046624/+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 2042767] [NEW] Crackling sound at random intervals while Virtualbox is running

[Rick van den Bergh]

Public bug reported:

Recently I'm having an issue where the audio playback from my HDMI
output starts crackling at random intervals in Ubuntu 22.04. It is not
sure if Virtualbox is causing this issue, but it's a possible cause. I
dug up a forum post from 2 years ago on AskUbuntu where someone implies
Virtualbox causes their issue. Since Virtualbox runs in the background
all the time for me, I cannot be certain about this. I run my Home
Asisstant server inside Virtualbox.

If any audio playback starts crackling,  executing pulseaudio -k always
fixes it. Then the applications producing sound need to be restarted in
order to get any sound out of them. After that the crackling will take
hours to show up again.

In that AskUbuntu forum post that I referred to earlier, the user fixed
this by setting resample-method = speex-float-10 in
/etc/pulse/daemon.conf. So I did the same thing just before filling this
bug report to see if that would fix it. I do not have enough data yet to
draw any conclusions.

I can be sure that the crackling is from the HDMI sound output and not
from malfunctioning speakers, since no other devices connected to the
same speakers/TV have this issue.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1
ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-36-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  rick  90340 F pulseaudio
 /dev/snd/controlC0:  rick  90340 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov  5 14:01:41 2023
InstallationDate: Installed on 2023-10-28 (8 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/13/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 1.H0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MAG B550M MORTAR WIFI (MS-7C94)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.H0:bd10/13/2023:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C94:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGB550MMORTARWIFI(MS-7C94):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7C94
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
modified.conffile..etc.pulse.daemon.conf: [modified]
mtime.conffile..etc.pulse.daemon.conf: 2023-11-05T11:50:19.891182

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

Title:
  Crackling sound at random intervals while Virtualbox is running

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Recently I'm having an issue where the audio playback from my HDMI
  output starts crackling at random intervals in Ubuntu 22.04. It is not
  sure if Virtualbox is causing this issue, but it's a possible cause. I
  dug up a forum post from 2 years ago on AskUbuntu where someone
  implies Virtualbox causes their issue. Since Virtualbox runs in the
  background all the time for me, I cannot be certain about this. I run
  my Home Asisstant server inside Virtualbox.

  If any audio playback starts crackling,  executing pulseaudio -k
  always fixes it. Then the applications producing sound need to be
  restarted in order to get any sound out of them. After that the
  crackling will take hours to show up again.

  In that AskUbuntu forum post that I referred to earlier, the user
  fixed this by setting resample-method = speex-float-10 in
  /etc/pulse/daemon.conf. So I did the same thing just before filling
  this bug report to see if that would fix it. I do not have enough data
  yet to draw any conclusions.

  I can be sure that the crackling is from the HDMI sound output and not
  from malfunctioning speakers, since no other devices connected to the
  same speakers/TV have this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rick  90340 F pulseaudio
   /dev/snd/contro

[Touch-packages] [Bug 1965691] [NEW] No Epson Stylus Photo R220 or R200 drivers

[Rick O'Sullivan]

Public bug reported:

The gutenprint website says that they still support the earlier "Epson
Stylus Photo" models, but the Ubuntu printer settings tool only shows
drivers for the R240 and up. Is this a regression, or purposeful? See
http://gimp-print.sourceforge.net/p_Supported_Printers.php

The gutenprint site shows this sub-list of similarly supported drivers,
including the R220:

  Epson Stylus Photo R200  escp2-r200   
  Epson Stylus Photo R210  escp2-r210   
  Epson Stylus Photo R220  escp2-r220   
  Epson Stylus Photo R230  escp2-r230

What you expected to happen?

  I expected the Ubuntu printer settings utility to offer the "Epson
Stylus Photo R220" printer driver.

What happened instead?

  The Ubuntu printer settings utility only offered the series R240 and
above.

System Info:

  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

Cups Info:
  Installed: 2.3.1-9ubuntu1.1
  Candidate: 2.3.1-9ubuntu1.1
  Version table:
  *** 2.3.1-9ubuntu1.1 500
500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 
Packages
100 /var/lib/dpkg/status
  2.3.1-9ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages

Note: Manually, I was able to successfully install openprinting-
gutenprint_5.2.7-1lsb3.2_amd64.deb from the OpenPrinting site (which
includes R220) but it would be better to find the R220 driver in the
list of available print drivers through the automated Ubuntu printer
settings utility.

See https://www.openprinting.org/printer/Epson/Epson-Stylus_Photo_R220
for the Debian package(s).

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

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

Title:
  No Epson Stylus Photo R220 or R200 drivers

Status in cups package in Ubuntu:
  New

Bug description:
  The gutenprint website says that they still support the earlier "Epson
  Stylus Photo" models, but the Ubuntu printer settings tool only shows
  drivers for the R240 and up. Is this a regression, or purposeful? See
  http://gimp-print.sourceforge.net/p_Supported_Printers.php

  The gutenprint site shows this sub-list of similarly supported
  drivers, including the R220:

Epson Stylus Photo R200  escp2-r200 
Epson Stylus Photo R210  escp2-r210 
Epson Stylus Photo R220  escp2-r220 
Epson Stylus Photo R230  escp2-r230

  What you expected to happen?

I expected the Ubuntu printer settings utility to offer the "Epson
  Stylus Photo R220" printer driver.

  What happened instead?

The Ubuntu printer settings utility only offered the series R240 and
  above.

  System Info:

Description:Ubuntu 20.04.4 LTS
Release:20.04

  Cups Info:
Installed: 2.3.1-9ubuntu1.1
Candidate: 2.3.1-9ubuntu1.1
Version table:
*** 2.3.1-9ubuntu1.1 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
2.3.1-9ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Note: Manually, I was able to successfully install openprinting-
  gutenprint_5.2.7-1lsb3.2_amd64.deb from the OpenPrinting site (which
  includes R220) but it would be better to find the R220 driver in the
  list of available print drivers through the automated Ubuntu printer
  settings utility.

  See https://www.openprinting.org/printer/Epson/Epson-Stylus_Photo_R220
  for the Debian package(s).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1965691/+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 1928488] [NEW] Receiving error for /var/cache/apt/archives/fonts-noto-cjk compressed data is corrupt

[Rick]

Public bug reported:

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
 ???@???-OMEN:~$ lsb_release -rd
 Description:   Ubuntu 21.04
 Release:   21.04

2) The version of the package you are using, via 'apt-cache policy pkgname' or 
by checking inSoftware Center
  ???-OMEN:~$ apt-cache policy fonts-noto-cjk
  fonts-noto-cjk:
   Installed: 1:20190410+repack1-2
Candidate: 1:20201206-cjk+repack1-1
Version table:
   1:20201206-cjk+repack1-1 500
  500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu hirsute/main i386 Packages
   *** 1:20190410+repack1-2 100
 100 /var/lib/dpkg/status

 ???@???-OMEN:~$ apt-cache policy fonts-noto-extra
 fonts-noto-extra:
   Installed: 20200323-1build1
   Candidate: 20201225-1build1
   Version table:
  20201225-1build1 500
 500 http://us.archive.ubuntu.com/ubuntu hirsute/universe amd64 
Packages
 500 http://us.archive.ubuntu.com/ubuntu hirsute/universe i386 
Packages
   *** 20200323-1build1 100
 100 /var/lib/dpkg/status

3) What you expected to happen
 I went to execute the upgrade from Ubuntu 21.03 to 21.04 and now 
cosistently receiving this error.

4) What happened instead
  Continually reciving this error whenever I run Software Update or APT 
UPGRADE

???@???-OMEN:~$ sudo apt upgrade -y
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  fonts-noto-cjk fonts-noto-extra
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/128 MB of archives.
After this operation, 11.3 MB of additional disk space will be used.
(Reading database ... 235767 files and directories currently installed.)
Preparing to unpack .../fonts-noto-cjk_1%3a20201206-cjk+repack1-1_all.deb ...
Unpacking fonts-noto-cjk (1:20201206-cjk+repack1-1) over (1:20190410+repack1-2)
...
dpkg-deb (subprocess): decompressing archive '/var/cache/apt/archives/fonts-noto
-cjk_1%3a20201206-cjk+repack1-1_all.deb' (size=55140504) member 'data.tar': lzma
 error: compressed data is corrupt

dpkg-deb: error:  subprocess returned error exit status 2
dpkg: error processing archive /var/cache/apt/archives/fonts-noto-cjk_1%3a202012
06-cjk+repack1-1_all.deb (--unpack):
 cannot copy extracted data for './usr/share/fonts/opentype/noto/NotoSerifCJK-Bo
ld.ttc' to '/usr/share/fonts/opentype/noto/NotoSerifCJK-Bold.ttc.dpkg-new': unex
pected end of file or stream

Preparing to unpack .../fonts-noto-extra_20201225-1build1_all.deb ...
Unpacking fonts-noto-extra (20201225-1build1) over (20200323-1build1) ...
dpkg-deb (subprocess): decompressing archive '/var/cache/apt/archives/fonts-noto
-extra_20201225-1build1_all.deb' (size=72415620) member 'data.tar': lzma error:
compressed data is corrupt

dpkg-deb: error:  subprocess returned error exit status 2
dpkg: error processing archive /var/cache/apt/archives/fonts-noto-extra_20201225
-1build1_all.deb (--unpack):
 cannot copy extracted data for './usr/share/fonts/truetype/noto/NotoSerifGeorgi
an-ExtraCondensed.ttf' to '/usr/share/fonts/truetype/noto/NotoSerifGeorgian-Extr
aCondensed.ttf.dpkg-new': unexpected end of file or stream
Errors were encountered while processing:
 /var/cache/apt/archives/fonts-noto-cjk_1%3a20201206-cjk+repack1-1_all.deb
 /var/cache/apt/archives/fonts-noto-extra_20201225-1build1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: apt 2.2.3
ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
Uname: Linux 5.11.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri May 14 11:11:23 2021
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: apt
UpgradeStatus: Upgraded to hirsute on 2021-05-14 (0 days ago)

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


** Tags: amd64 apport-bug hirsute

** Description changed:

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
-  rvinger@rvinger-OMEN:~$ lsb_release -rd
-  Description: Ubuntu 21.04
-  Release: 21.04
+  ???@???-OMEN:~$ lsb_release -rd
+  Description: Ubuntu 21.04
+  Release: 21.04
  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking inSoftware Center
-   rvinger@rvinger-OMEN:~$ apt-cache policy fonts-noto-cjk 
-   fonts-noto-cjk:
-Installed: 1:20190410+repack1-2
- Candidate: 1:20201206-cjk+repack1-1
- Version table:
-1:20201206-cjk+repack1-1 500
-

[Touch-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[Rick]

20.04 beta still has this issue for me

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete
Status in gdm3 source package in Eoan:
  Confirmed
Status in gnome-session source package in Eoan:
  Confirmed
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-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.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-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

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

[rick beldin]

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

Same problem on 18.04 with Sony headset:

s
[WI-1000X]# info 38:18:4C:04:C7:2A
Device 38:18:4C:04:C7:2A (public)
Name: WI-1000X
Alias: WI-1000X
Class: 0x00240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Vendor specific   (-deca-fade-deca-deafdecacaff)
 >>>UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: Vendor specific   (7b265b0e-2232-4d45-bef4-bb8ae62f813d)
UUID: Vendor specific   (81c2e72a-0591-443e-a1ff-05f988593351)
UUID: Vendor specific   (931c7e8a-540f-4686-b798-e8df0a2ad9f7)
UUID: Vendor specific   (96cc203e-5068-46ad-b32d-e316f5e069ba)
UUID: Vendor specific   (b9b213ce-eeab-49e4-8fd9-aa478ed1b26b)
UUID: Vendor specific   (f8d1fbe4-7966-4334-8024-ff96c9330e15)
Modalias: usb:v054Cp0C63d0411

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

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

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  There is a previous bug with almost the same title, but for Xenial
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1549163). I
  have had this issue in Artful, and when commented on the old bug, I
  was asked to raise a new one instead. I waited to see if Bionic fixed
  it for me, but it does not seem to work still. So!

  Steps to reproduce:
  1. enable bluetooth on computer and switch on the headset.
  2. pair and connect the headset
  3. go to settings to switch headset to HSP/HFP mode to enable mic
  4. save and close window.

  Expected behaviour:
  1. mic should be enabled and headset should be usable to attend calls on 
laptop.

  Behaviour in error:
  1. Headset profile switches back to A2DP and mic is not enabled.

  I am using a generic bluetooth headset on a fresh updated Kubuntu
  18.04 bionic with plasma DE.

  Software versions:
  Kernel: 4.15.0-20-generic
  Bluez version: 5.48-0ubuntu3
  pulseaudio: 1:11.1-1ubuntu7
  pulseaudio-module-bluetooth: 1:11.1-1ubuntu7

  
  Additional information:
  Running "pacmd list-cards" says that HSF/HFP is 'not available' on the 
headset:

  Output from Headset section:
  profiles:
  a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, 
available: unknown)
  headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, 
available: no)
  off: Off (priority 0, available: yes)
  active profile: 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768625/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[Rick]

@albertomilone: That does not work. I still cannot auto-login after
adding

needs_root_rights = yes
in /etc/X11/Xwrapper.config

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in gdm3 source package in Eoan:
  Confirmed
Status in gnome-session source package in Eoan:
  Confirmed
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-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.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+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 1860736] [NEW] Driver load at boot

[Rick]

Public bug reported:

At normal boot

If use xorg driver display remain black after boot
If use nvidia driver display and keyboard backlight flickers

At recovery mode
Boots normally

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
Uname: Linux 4.15.0-74-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: i386
CompositorRunning: None
Date: Thu Jan 23 19:32:44 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.15.0-65-generic, i686: installed
 bcmwl, 6.30.223.271+bdcom, 4.15.0-74-generic, i686: installed
 virtualbox, 5.2.34, 4.15.0-65-generic, i686: installed
 virtualbox, 5.2.34, 4.15.0-74-generic, i686: installed
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 NVIDIA Corporation MCP89 [GeForce 320M] [10de:08a0] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: Apple Inc. MCP89 [GeForce 320M] [106b:00c2]
InstallationDate: Installed on 2018-08-13 (528 days ago)
InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release i386 (20180725)
MachineType: Apple Inc. MacBookPro7,1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic 
root=UUID=c9b3b341-3777-4a4a-b9dd-d5bb2d942cbf ro recovery nomodeset
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLogOld:
 
dmi.bios.date: 02/02/18
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP71.88Z.003F.B00.1802021458
dmi.board.name: Mac-F222BEC8
dmi.board.vendor: Apple Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F222BEC8
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP71.88Z.003F.B00.1802021458:bd02/02/18:svnAppleInc.:pnMacBookPro7,1:pvr1.0:rvnAppleInc.:rnMac-F222BEC8:rvr:cvnAppleInc.:ct10:cvrMac-F222BEC8:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro7,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Thu Jan 23 19:29:35 2020
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4.3

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


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

Title:
  Driver load at boot

Status in xorg package in Ubuntu:
  New

Bug description:
  At normal boot

  If use xorg driver display remain black after boot
  If use nvidia driver display and keyboard backlight flickers

  At recovery mode
  Boots normally

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: i386
  CompositorRunning: None
  Date: Thu Jan 23 19:32:44 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-65-generic, i686: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-74-generic, i686: installed
   virtualbox, 5.2.34, 4.15.0-65-generic, i686: installed
   virtualbox, 5.2.34, 4.15.0-74-generic, i686: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   NVIDIA Corporation MCP89 [GeForce 320M] [10de:08a0] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Apple Inc. MCP89 [GeForce 320M] [106b:00c2]
  InstallationDate: Installed on 2018-08-13 (528 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release i386 
(20180725)
  MachineType: Apple Inc. MacBookPro7,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic 
root=UUID=c9b3b341-3777-4a4a-b9dd-d5bb2d942cbf ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 02/02/18
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP71.88Z.003F.B00.1802021458
  dmi.board.name: Mac-F222BEC8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F222BEC8
  dmi.modalias: 

[Touch-packages] [Bug 1830495] [NEW] tzdata noninteractive mode is being ignored

[Rick Spencer]

Public bug reported:

This bug is related to Bug #1773687

I am trying to automate the build of an AMI with a package that requires
tzdata. I am blocked from automation because tzdata will not install
non-interactively. This is despite setting
DEBIAN_FRONTEND=noninteractive.

Here is an interactive session that shows the same problem.


```
ubuntu@ip-172-31-95-248:~$ env
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
SSH_CONNECTION=172.58.185.180 50092 172.31.95.248 22
LANG=C.UTF-8
XDG_SESSION_ID=3
USER=ubuntu
PWD=/home/ubuntu
HOME=/home/ubuntu
SSH_CLIENT=172.58.185.180 50092 22
XDG_DATA_DIRS=/usr/local/share:/usr/share:/var/lib/snapd/desktop
DEBIAN_FRONTEND=noninteractive
SSH_TTY=/dev/pts/0
MAIL=/var/mail/ubuntu
TERM=xterm-256color
SHELL=/bin/bash
SHLVL=1
LOGNAME=ubuntu
XDG_RUNTIME_DIR=/run/user/1000
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
_=/usr/bin/env
ubuntu@ip-172-31-95-248:~$ sudo apt-get install -y tzdata
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following NEW packages will be installed:
  tzdata
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/189 kB of archives.
After this operation, 3105 kB of additional disk space will be used.
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package tzdata.
(Reading database ... 47149 files and directories currently installed.)
Preparing to unpack .../tzdata_2019a-0ubuntu0.18.04_all.deb ...
Unpacking tzdata (2019a-0ubuntu0.18.04) ...
Setting up tzdata (2019a-0ubuntu0.18.04) ...
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based 
frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 
76.)
debconf: falling back to frontend: Readline
Configuring tzdata
--

Please select the geographic area in which you live. Subsequent configuration 
questions will narrow this down by presenting a list of
cities, representing the time zones in which they are located.

  1. Africa   3. Antarctica  5. Arctic  7. Atlantic  9. Indian11. SystemV  
13. Etc
  2. America  4. Australia   6. Asia8. Europe10. Pacific  12. US
Geographic area: 

```

This is based on minimal version:

```
$ lsb_release -a 
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.2 LTS
Release:18.04
Codename:   bionic
```

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

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

Title:
  tzdata noninteractive mode is being ignored

Status in tzdata package in Ubuntu:
  New

Bug description:
  This bug is related to Bug #1773687

  I am trying to automate the build of an AMI with a package that
  requires tzdata. I am blocked from automation because tzdata will not
  install non-interactively. This is despite setting
  DEBIAN_FRONTEND=noninteractive.

  Here is an interactive session that shows the same problem.

  
  ```
  ubuntu@ip-172-31-95-248:~$ env
  

[Touch-packages] [Bug 1813408] [NEW] package systemd 237-3ubuntu10.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

[Rick Arabian]

Public bug reported:

Attempting upgrade from 16.04 LTS

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: systemd 237-3ubuntu10.11
ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
Uname: Linux 4.4.0-127-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
AptOrdering:
 systemd: Configure
 initramfs-tools: Configure
 libnss-systemd: Configure
 libpam-systemd: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Sat Jan 26 07:52:16 2019
DpkgTerminalLog:
 Setting up systemd (237-3ubuntu10.11) ...
 systemd-machine-id-setup: error while loading shared libraries: 
libcryptsetup.so.12: cannot open shared object file: No such file or directory
 dpkg: error processing package systemd (--configure):
  subprocess installed post-installation script returned error exit status 127
 Setting up initramfs-tools (0.130ubuntu3.6) ...
DuplicateSignature:
 package:systemd:237-3ubuntu10.11
 Setting up systemd (237-3ubuntu10.11) ...
 systemd-machine-id-setup: error while loading shared libraries: 
libcryptsetup.so.12: cannot open shared object file: No such file or directory
 dpkg: error processing package systemd (--configure):
  subprocess installed post-installation script returned error exit status 127
ErrorMessage: subprocess installed post-installation script returned error exit 
status 127
InstallationDate: Installed on 2016-09-15 (863 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
Lspci: Error: command ['lspci', '-vvnn'] failed with exit code 1: lspci: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by 
/lib/x86_64-linux-gnu/libudev.so.1)
Lsusb: Error: command ['lsusb'] failed with exit code 1: lsusb: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by 
/lib/x86_64-linux-gnu/libudev.so.1)
MachineType: VMware, Inc. VMware Virtual Platform
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-127-generic 
root=/dev/mapper/ubuntu--vg-root ro
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: systemd
SystemdDelta: Error: command ['systemd-delta'] failed with exit code 127: 
systemd-delta: error while loading shared libraries: libcryptsetup.so.12: 
cannot open shared object file: No such file or directory
SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', 'Error:'] 
failed with exit code 127: systemctl: error while loading shared libraries: 
libcryptsetup.so.12: cannot open shared object file: No such file or directory
Title: package systemd 237-3ubuntu10.11 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 127
UdevDb:
 Error: command ['udevadm', 'info', '--export-db'] failed with exit code 1: 
udevadm: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found 
(required by udevadm)
 udevadm: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.27' not found 
(required by udevadm)
 udevadm: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found 
(required by /lib/x86_64-linux-gnu/libblkid.so.1)
 udevadm: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found 
(required by /lib/x86_64-linux-gnu/libuuid.so.1)
UpgradeStatus: Upgraded to xenial on 2019-01-26 (0 days ago)
dmi.bios.date: 07/28/2017
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/28/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
modified.conffile..etc.dhcp.dhclient-enter-hooks.d.resolved: [deleted]
mtime.conffile..etc.pam.d.systemd-user: 2016-04-12T03:34:03
mtime.conffile..etc.systemd.journald.conf: 2016-04-12T03:34:03
mtime.conffile..etc.systemd.logind.conf: 2016-04-12T03:34:03
mtime.conffile..etc.systemd.resolved.conf: 2016-04-12T03:34:04
mtime.conffile..etc.systemd.system.conf: 2016-09-07T02:32:47
mtime.conffile..etc.systemd.timesyncd.conf: 2016-04-12T03:34:04
mtime.conffile..etc.systemd.user.conf: 2016-04-12T03:34:03

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

Title:
  package systemd 237-3ubuntu10.11 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 127

Status in systemd package in Ubuntu:
  New

Bug description:
  Attempting upgrade from 16.04 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 237-3ubuntu10.11
  

[Touch-packages] [Bug 1777010] Re: ip token set, results in: Invalid argument

[Rick Wagner]

Daniel Borkmann's contact information seems to be available at
http://borkmann.ch .

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

Title:
  ip token set, results in: Invalid argument

Status in iproute2 package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I can't set any ipv6 token with ip command. It seems that it has a bug.
  Also it is not possible to set it with netplan (see bug #1737976)

  ~# ip token list
  token :: dev enp1s0
  token :: dev enp2s0
  token :: dev ovpn0
  token :: dev br0

  ~# ip token set ::2a:2a:2a:2a/64 dev br0
  RTNETLINK answers: Invalid argument

  ~# ip token set ::2a/64 dev br0
  RTNETLINK answers: Invalid argument

  ~# ip token set ::beef dev br0
  RTNETLINK answers: Invalid argument

  It seems, that this Bug is really old?!
  https://bbs.archlinux.org/viewtopic.php?id=202757

  This is really fatal, because I cant set a static ip. My prefix get
  mixed from my provider every x days.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: iproute2 4.15.0-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Fri Jun 15 01:26:04 2018
  InstallationDate: Installed on 2018-06-12 (2 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: iproute2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1777010/+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 1782135] [NEW] package cups-daemon 2.2.7-1ubuntu2.1 failed to install/upgrade: installed cups-daemon package post-installation script subprocess returned error exit status 1

[Rick Asadorian]

Public bug reported:

na

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: cups-daemon 2.2.7-1ubuntu2.1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Mon Jul 16 16:34:07 2018
ErrorMessage: installed cups-daemon package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2018-07-16 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
Lsusb:
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
Papersize: letter
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=94749527-c5d4-44b0-a72a-3b0c9dba3cc4 ro quiet splash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=94749527-c5d4-44b0-a72a-3b0c9dba3cc4 ro quiet splash
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.2
SourcePackage: cups
Title: package cups-daemon 2.2.7-1ubuntu2.1 failed to install/upgrade: 
installed cups-daemon package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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

Title:
  package cups-daemon 2.2.7-1ubuntu2.1 failed to install/upgrade:
  installed cups-daemon package post-installation script subprocess
  returned error exit status 1

Status in cups package in Ubuntu:
  New

Bug description:
  na

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: cups-daemon 2.2.7-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Mon Jul 16 16:34:07 2018
  ErrorMessage: installed cups-daemon package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-07-16 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=94749527-c5d4-44b0-a72a-3b0c9dba3cc4 ro quiet splash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=94749527-c5d4-44b0-a72a-3b0c9dba3cc4 ro quiet splash
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.2
  SourcePackage: cups
  Title: package cups-daemon 2.2.7-1ubuntu2.1 failed to install/upgrade: 
installed cups-daemon package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1782135/+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 1759836] Re: systemd-udevd consumes 100% of CPU

[Rick Harris]

As per https://patchwork.kernel.org/patch/10384111/ message from Bluez
mailing list, editing 97-hid2hci.rules as follows works around the new
uevents added to the kernel in
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1455cf8dbfd06aa7651dcfccbadb7a093944ca65

-ACTION=="remove", GOTO="hid2hci_end"
+ACTION!="add", GOTO="hid2hci_end"

Bluetooth now works with kernels above and below 4.14.

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

Title:
  systemd-udevd consumes 100% of CPU

Status in Bluez Utilities:
  Unknown
Status in linux:
  Unknown
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1759836/+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 1759836] Re: systemd-udevd consumes 100% of CPU

[Rick Harris]

It's a known kernel bug that Dell bluetooth is broken in kernels >=4.14,
so sticking with the old kernel that works for now.

Kernel bluetooth bug causes bluez 97-hid2hci.rules udev rule to fail.
systemd-udevd has always consumed 100% whenever a udev rule fails (could be 
argued that's also a bug but at least you become immediately aware there's a 
problem).

Possibly no coincidence that the break was introduced at the same time
kernel tree commits were made to btusb.c wrt. Dell 'features' being
addded.

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

Title:
  systemd-udevd consumes 100% of CPU

Status in Bluez Utilities:
  Unknown
Status in linux:
  Unknown
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1759836/+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 1761063] [NEW] package linux-image-4.13.0-38-generic 4.13.0-38.43~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[rick stthomas]

Public bug reported:

run on dell 2 in 1 tablet pc. off of usbstick

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.13.0-38-generic 4.13.0-38.43~16.04.1
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Wed Apr  4 01:38:08 2018
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: initramfs-tools
Title: package linux-image-4.13.0-38-generic 4.13.0-38.43~16.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package linux-image-4.13.0-38-generic 4.13.0-38.43~16.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  run on dell 2 in 1 tablet pc. off of usbstick

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-38-generic 4.13.0-38.43~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Wed Apr  4 01:38:08 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: initramfs-tools
  Title: package linux-image-4.13.0-38-generic 4.13.0-38.43~16.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 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/1761063/+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 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries

[Rick Timmis]

Today I discovered some additional information in regard to this issue.

I am using Virt-Manager and KVM, I have a Br0 bridge configured to start
onboot. When this is the case name resolution as above fails.

If I delete the bridge using VMM name resolution starts working ( after
a reboot ). Put the bridge back in and it fails.

I do have 3 network interfaces, 1 wlan, 1 ethernet, and and additional
usb ethernet configured as eth1.

I've configured the 3 interfaces using a persistent-rules file in
/etc/udev/rules.d/ so that they bind to eth0, wlan0 and eth1.

By configuring my VMM Br0 interface to Hotplug, so that it does not
start onboot, this has resolved the issue. However, on Ubuntu 16.04
everything worked as expected including having the Br0 bridge start
onboot.

Can't say I understand what magic SystemD witchcraft is going up here,
but I hope the above info provides some useful clues.

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

Title:
  systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing
  entries

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd-resolved, or more precisely the hook script
  /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes
  resolvconf to add 127.0.0.53 to the set of nameservers in
  /etc/resolv.conf alongside the other nameservers.  That makes no sense
  because systemd-resolved sets up 127.0.0.53 as a proxy for those other
  nameservers.  The effect is similar to bug 1624071 but for
  applications doing their own DNS lookups.  It breaks any DNSSEC
  validation that systemd-resolved tries to do; applications will
  failover to the other nameservers, bypassing validation failures.  And
  it makes failing queries take twice as long.

  /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is
  active.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/+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 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries

[Rick Timmis]

Here is my use case experience, after running a clean install of Kubuntu
17.10.

Initially everything was perfect, and for at least 10 days my machine
booted perfectly fine and DNS working without issue.

However, after installing virt manage Virtual Machine Manager, like so

sudo apt-get install qemu-system qemu-kvm virt-manager wireshark

I configured some additional Virbr networks ( see below ) The following
day after a reboot, I had no DNS resolution, I hacked /etc/resolv.conf
to add a nameserver. All good until reboot, and then back to square one.

Once I discovered this bug things became clearer, and I have applied fix
at post #8 above

I figure that my use of virt-manager might be an interesting edge case
that break things with systemd-resolve. Below is the output from status,
which highlights the issue, there are no DNS servers listed.

Hope this info is useful


ricktimmis@ricktimmis-Latitude-E6430:~$ systemd-resolve --status
Global
  DNSSEC NTA: 10.in-addr.arpa
  16.172.in-addr.arpa
  168.192.in-addr.arpa
  17.172.in-addr.arpa
  18.172.in-addr.arpa
  19.172.in-addr.arpa
  20.172.in-addr.arpa
  21.172.in-addr.arpa
  22.172.in-addr.arpa
  23.172.in-addr.arpa
  24.172.in-addr.arpa
  25.172.in-addr.arpa
  26.172.in-addr.arpa
  27.172.in-addr.arpa
  28.172.in-addr.arpa
  29.172.in-addr.arpa
  30.172.in-addr.arpa
  31.172.in-addr.arpa
  corp
  d.f.ip6.arpa
  home
  internal
  intranet
  lan
  local
  private
  test

Link 23 (vnet1)
  Current Scopes: LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

Link 17 (vnet0)
  Current Scopes: LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

Link 15 (vnet5)
  Current Scopes: none
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

Link 14 (vnet4)
  Current Scopes: none
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

Link 13 (vnet3)
  Current Scopes: LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

Link 9 (virbr0-nic)
  Current Scopes: none
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

Link 8 (virbr0)
  Current Scopes: LLMNR/IPv4
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

Link 7 (virbr1-nic)
  Current Scopes: none
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

Link 6 (virbr1)
  Current Scopes: LLMNR/IPv4
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

Link 5 (br0)
  Current Scopes: LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

Link 4 (eth1)
  Current Scopes: none
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

Link 3 (wlan0)
  Current Scopes: none
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

Link 2 (eth0)
  Current Scopes: LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

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

Title:
  systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing
  entries

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd-resolved, or more precisely the hook script
  /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes
  resolvconf to add 127.0.0.53 to the set of nameservers in
  /etc/resolv.conf alongside the other nameservers.  That makes no sense
  because systemd-resolved sets up 127.0.0.53 as a proxy for those other
  nameservers.  The effect is similar to bug 1624071 but for
  applications doing their own DNS lookups.  It breaks any DNSSEC
  validation that systemd-resolved tries to do; applications will
  failover to the other nameservers, bypassing validation failures.  And
  it makes failing queries take twice as long.

  /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is
  active.

To manage 

[Touch-packages] [Bug 1731073] [NEW] package lsb-invalid-mta 9.20160110ubuntu0.2 failed to install/upgrade: package lsb-invalid-mta is not ready for configuration cannot configure (current status 'hal

[Rick]

Public bug reported:

Received error while attempting to install update after downloading from
Ubuntu Software.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: lsb-invalid-mta 9.20160110ubuntu0.2
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.10
AptOrdering:
 resolvconf: Install
 lsb-invalid-mta: Configure
 resolvconf: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Wed Nov  8 18:41:06 2017
Dependencies:
 
DuplicateSignature:
 package:lsb-invalid-mta:9.20160110ubuntu0.2
 Processing triggers for systemd (229-4ubuntu21) ...
 dpkg: error processing package lsb-invalid-mta (--configure):
  package lsb-invalid-mta is not ready for configuration
ErrorMessage: package lsb-invalid-mta is not ready for configuration  cannot 
configure (current status 'half-installed')
InstallationDate: Installed on 2017-10-03 (36 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: lsb
Title: package lsb-invalid-mta 9.20160110ubuntu0.2 failed to install/upgrade: 
package lsb-invalid-mta is not ready for configuration  cannot configure 
(current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package lsb-invalid-mta 9.20160110ubuntu0.2 failed to install/upgrade:
  package lsb-invalid-mta is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in lsb package in Ubuntu:
  New

Bug description:
  Received error while attempting to install update after downloading
  from Ubuntu Software.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lsb-invalid-mta 9.20160110ubuntu0.2
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  AptOrdering:
   resolvconf: Install
   lsb-invalid-mta: Configure
   resolvconf: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Nov  8 18:41:06 2017
  Dependencies:
   
  DuplicateSignature:
   package:lsb-invalid-mta:9.20160110ubuntu0.2
   Processing triggers for systemd (229-4ubuntu21) ...
   dpkg: error processing package lsb-invalid-mta (--configure):
package lsb-invalid-mta is not ready for configuration
  ErrorMessage: package lsb-invalid-mta is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-10-03 (36 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: lsb
  Title: package lsb-invalid-mta 9.20160110ubuntu0.2 failed to install/upgrade: 
package lsb-invalid-mta 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/lsb/+bug/1731073/+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 1245287] Re: upower showing keyboard at 0% charge

[Rick Ucker]

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

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

Title:
  upower showing keyboard at 0% charge

Status in Upower:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released

Bug description:
  This bug is new upon upgrading to 13.10; bug did not exist on 13.04,
  12.10 or 12.04.

  I'm using an apple wireless keyboard. I have replaced the batteries
  and confirmed they are fully charged with voltmeter.

  Keyboard is working fine but indicator says it's 0% and is red
  indicating some problem. Also upower says "keyboard not present";
  bluetooth shows keyboards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/upower/+bug/1245287/+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 1651735] Re: $ mir_demo_server --help fails with an exception

[Rick Harris]

Also occurs on Zesty installations that have been upgraded from Yakkety.

Unity8 fails to launch (classic black screen) and unity8.log shows the error:
"character conversion failed"

This is due to incorrect multiple versions of boost being present on the
system because they aren't removed when upgrading.

Counted 6(six) different boost versions installed in Zesty because of taking 
the upgrade route through multiple Ubuntu versions.
'apt-get remove --auto-remove --purge' does not remove them so looks like a 
genuine dependency resolution problem when upgrading.

Manually removing all the old boost versions works around the problem
and allows Unity8 to work again.

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

Title:
  $ mir_demo_server --help fails with an exception

Status in Mir:
  Invalid
Status in mir package in Ubuntu:
  Invalid

Bug description:
  $ mir_demo_server --help
  [2016-12-21 11:49:00.068655] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.25.0)
  [2016-12-21 11:49:00.069710] mirplatform: Found graphics driver: mir:mesa-x11 
(version 0.25.0)
  [2016-12-21 11:49:00.069935] mirplatform: Found graphics driver: 
mir:stub-graphics (version 0.25.0)
  [2016-12-21 11:49:00.069954] mirplatform: Found graphics driver: 
throw-on-creation (version 0.25.0)
  ERROR: Throw location unknown (consider using BOOST_THROW_EXCEPTION)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: character conversion failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1651735/+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 1678291] Re: kernel panic while updating

[Rick Hermans]

thanks that fixed it

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

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

Title:
  kernel panic while updating

Status in apparmor package in Ubuntu:
  Invalid

Bug description:
  While updating apparmor i get:

  
  Mar 31 21:08:11 vps kernel: [ 2118.814239] audit: type=1400 
audit(1490987291.543:58): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="docker-default" pid=4918 comm="apparmor_parser"
  Mar 31 21:08:11 vps kernel: [ 2118.848093] audit: type=1400 
audit(1490987291.579:59): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/{usr/,}bin/ping" pid=4917 comm="apparmor_parser"
  Mar 31 21:08:11 vps kernel: [ 2118.878367] audit: type=1400 
audit(1490987291.607:60): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="klogd" pid=4922 comm="apparmor_parser"
  Mar 31 21:08:11 vps kernel: [ 2118.957963] audit: type=1400 
audit(1490987291.687:61): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="syslogd" pid=4924 comm="apparmor_parser"
  Mar 31 21:08:11 vps kernel: [ 2118.986644] audit: type=1400 
audit(1490987291.719:62): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/sbin/dhclient" pid=4920 comm="apparmor_parser"
  Mar 31 21:08:11 vps kernel: [ 2118.987066] audit: type=1400 
audit(1490987291.719:63): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" 
pid=4920 comm="apparmor_parser"
  Mar 31 21:08:11 vps kernel: [ 2118.987383] audit: type=1400 
audit(1490987291.719:64): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=4920 
comm="apparmor_parser"
  Mar 31 21:08:11 vps kernel: [ 2118.987667] audit: type=1400 
audit(1490987291.719:65): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=4920 
comm="apparmor_parser"
  Mar 31 21:08:11 vps kernel: [ 2119.062817] audit: type=1400 
audit(1490987291.795:66): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="syslog-ng" pid=4926 comm="apparmor_parser"
  Mar 31 21:08:11 vps kernel: [ 2119.096288] audit: type=1400 
audit(1490987291.827:67): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/dovecot/anvil" pid=4930 
comm="apparmor_parser"
  Mar 31 21:08:11 vps kernel: [ 2119.096416] [ cut here 
]
  Mar 31 21:08:11 vps kernel: [ 2119.096446] WARNING: CPU: 0 PID: 4930 at 
/build/linux-Ay7j_C/linux-4.4.0/security/apparmor/label.c:142 
profile_cmp+0xed/0x180()
  Mar 31 21:08:11 vps kernel: [ 2119.096447] AppArmor WARN profile_cmp: ((!b)):
  Mar 31 21:08:11 vps kernel: [ 2119.096449] Modules linked in: ipt_REJECT 
nf_reject_ipv4 veth xt_multiport xt_nat xt_tcpudp ipt_MASQUERADE 
nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack 
x_tables nf_nat nf_conntrack br_netfilter bridge stp llc aufs ppdev kvm_intel 
kvm irqbypass joydev input_leds serio_raw i2c_piix4 8250_fintek parport_pc 
parport mac_hid autofs4 hid_generic usbhid hid cirrus ttm drm_kms_helper 
syscopyarea psmouse sysfillrect sysimgblt fb_sys_fops floppy drm pata_acpi
  Mar 31 21:08:11 vps kernel: [ 2119.096563] CPU: 0 PID: 4930 Comm: 
apparmor_parser Not tainted 4.4.0-21-generic #37-Ubuntu
  Mar 31 21:08:11 vps kernel: [ 2119.096567] Hardware name: Apache Software 
Foundation CloudStack KVM Hypervisor, BIOS Bochs 01/01/2007
  Mar 31 21:08:11 vps kernel: [ 2119.096570]  0086 7e65d053 
88007abafc00 813e93c3
  Mar 31 21:08:11 vps kernel: [ 2119.096573]  88007abafc48 81cebfd0 
88007abafc38 81080f62
  Mar 31 21:08:11 vps kernel: [ 2119.096574]  880079e49400  
0008 
  Mar 31 21:08:11 vps kernel: [ 2119.096576] Call Trace:
  Mar 31 21:08:11 vps kernel: [ 2119.096593]  [] 
dump_stack+0x63/0x90
  Mar 31 21:08:11 vps kernel: [ 2119.096605]  [] 
warn_slowpath_common+0x82/0xc0
  Mar 31 21:08:11 vps kernel: [ 2119.096607]  [] 
warn_slowpath_fmt+0x5c/0x80
  Mar 31 21:08:11 vps kernel: [ 2119.096612]  [] ? 
u32_swap+0x10/0x10
  Mar 31 21:08:11 vps kernel: [ 2119.096615]  [] 
profile_cmp+0xed/0x180
  Mar 31 21:08:11 vps kernel: [ 2119.096619]  [] 
aa_vec_unique+0x163/0x240
  Mar 31 21:08:11 vps kernel: [ 2119.096621]  [] 
__aa_labelset_update_subtree+0x687/0x820
  Mar 31 21:08:11 vps kernel: [ 2119.096625]  [] 
aa_replace_profiles+0x59b/0xb70
  Mar 31 21:08:11 vps kernel: [ 2119.096638]  [] ? 
__kmalloc+0x22e/0x250
  Mar 31 21:08:11 vps kernel: [ 2119.096640]  [] 
policy_update+0x9f/0x1f0
  Mar 31 21:08:11 vps kernel: [ 2119.096642]  

[Touch-packages] [Bug 1678291] [NEW] kernel panic while updating

[Rick Hermans]

Public bug reported:

While updating apparmor i get:


Mar 31 21:08:11 vps kernel: [ 2118.814239] audit: type=1400 
audit(1490987291.543:58): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="docker-default" pid=4918 comm="apparmor_parser"
Mar 31 21:08:11 vps kernel: [ 2118.848093] audit: type=1400 
audit(1490987291.579:59): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/{usr/,}bin/ping" pid=4917 comm="apparmor_parser"
Mar 31 21:08:11 vps kernel: [ 2118.878367] audit: type=1400 
audit(1490987291.607:60): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="klogd" pid=4922 comm="apparmor_parser"
Mar 31 21:08:11 vps kernel: [ 2118.957963] audit: type=1400 
audit(1490987291.687:61): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="syslogd" pid=4924 comm="apparmor_parser"
Mar 31 21:08:11 vps kernel: [ 2118.986644] audit: type=1400 
audit(1490987291.719:62): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/sbin/dhclient" pid=4920 comm="apparmor_parser"
Mar 31 21:08:11 vps kernel: [ 2118.987066] audit: type=1400 
audit(1490987291.719:63): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" 
pid=4920 comm="apparmor_parser"
Mar 31 21:08:11 vps kernel: [ 2118.987383] audit: type=1400 
audit(1490987291.719:64): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=4920 
comm="apparmor_parser"
Mar 31 21:08:11 vps kernel: [ 2118.987667] audit: type=1400 
audit(1490987291.719:65): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=4920 
comm="apparmor_parser"
Mar 31 21:08:11 vps kernel: [ 2119.062817] audit: type=1400 
audit(1490987291.795:66): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="syslog-ng" pid=4926 comm="apparmor_parser"
Mar 31 21:08:11 vps kernel: [ 2119.096288] audit: type=1400 
audit(1490987291.827:67): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/dovecot/anvil" pid=4930 
comm="apparmor_parser"
Mar 31 21:08:11 vps kernel: [ 2119.096416] [ cut here ]
Mar 31 21:08:11 vps kernel: [ 2119.096446] WARNING: CPU: 0 PID: 4930 at 
/build/linux-Ay7j_C/linux-4.4.0/security/apparmor/label.c:142 
profile_cmp+0xed/0x180()
Mar 31 21:08:11 vps kernel: [ 2119.096447] AppArmor WARN profile_cmp: ((!b)):
Mar 31 21:08:11 vps kernel: [ 2119.096449] Modules linked in: ipt_REJECT 
nf_reject_ipv4 veth xt_multiport xt_nat xt_tcpudp ipt_MASQUERADE 
nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack 
x_tables nf_nat nf_conntrack br_netfilter bridge stp llc aufs ppdev kvm_intel 
kvm irqbypass joydev input_leds serio_raw i2c_piix4 8250_fintek parport_pc 
parport mac_hid autofs4 hid_generic usbhid hid cirrus ttm drm_kms_helper 
syscopyarea psmouse sysfillrect sysimgblt fb_sys_fops floppy drm pata_acpi
Mar 31 21:08:11 vps kernel: [ 2119.096563] CPU: 0 PID: 4930 Comm: 
apparmor_parser Not tainted 4.4.0-21-generic #37-Ubuntu
Mar 31 21:08:11 vps kernel: [ 2119.096567] Hardware name: Apache Software 
Foundation CloudStack KVM Hypervisor, BIOS Bochs 01/01/2007
Mar 31 21:08:11 vps kernel: [ 2119.096570]  0086 7e65d053 
88007abafc00 813e93c3
Mar 31 21:08:11 vps kernel: [ 2119.096573]  88007abafc48 81cebfd0 
88007abafc38 81080f62
Mar 31 21:08:11 vps kernel: [ 2119.096574]  880079e49400  
0008 
Mar 31 21:08:11 vps kernel: [ 2119.096576] Call Trace:
Mar 31 21:08:11 vps kernel: [ 2119.096593]  [] 
dump_stack+0x63/0x90
Mar 31 21:08:11 vps kernel: [ 2119.096605]  [] 
warn_slowpath_common+0x82/0xc0
Mar 31 21:08:11 vps kernel: [ 2119.096607]  [] 
warn_slowpath_fmt+0x5c/0x80
Mar 31 21:08:11 vps kernel: [ 2119.096612]  [] ? 
u32_swap+0x10/0x10
Mar 31 21:08:11 vps kernel: [ 2119.096615]  [] 
profile_cmp+0xed/0x180
Mar 31 21:08:11 vps kernel: [ 2119.096619]  [] 
aa_vec_unique+0x163/0x240
Mar 31 21:08:11 vps kernel: [ 2119.096621]  [] 
__aa_labelset_update_subtree+0x687/0x820
Mar 31 21:08:11 vps kernel: [ 2119.096625]  [] 
aa_replace_profiles+0x59b/0xb70
Mar 31 21:08:11 vps kernel: [ 2119.096638]  [] ? 
__kmalloc+0x22e/0x250
Mar 31 21:08:11 vps kernel: [ 2119.096640]  [] 
policy_update+0x9f/0x1f0
Mar 31 21:08:11 vps kernel: [ 2119.096642]  [] 
profile_replace+0x13/0x20
Mar 31 21:08:11 vps kernel: [ 2119.096648]  [] 
__vfs_write+0x18/0x40
Mar 31 21:08:11 vps kernel: [ 2119.096649]  [] 
vfs_write+0xa9/0x1a0
Mar 31 21:08:11 vps kernel: [ 2119.096651]  [] ? 
do_sys_open+0x1bf/0x2a0
Mar 31 21:08:11 vps kernel: [ 2119.096653]  [] 
SyS_write+0x55/0xc0
Mar 31 21:08:11 vps kernel: [ 2119.096668]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71
Mar 31 21:08:11 vps 

[Touch-packages] [Bug 1673727] [NEW] package slapd 2.4.31-1+nmu2ubuntu8.3 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

[Rick Bosscha]

Public bug reported:

Error message while upgrading.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: slapd 2.4.31-1+nmu2ubuntu8.3
ProcVersionSignature: Ubuntu 3.13.0-112.159-generic 3.13.11-ckt39
Uname: Linux 3.13.0-112-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
Date: Fri Mar 17 10:57:23 2017
ErrorMessage: subprocess new pre-installation script returned error exit status 
1
InstallationDate: Installed on 2014-05-09 (1042 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.0.1ubuntu2.17
SourcePackage: openldap
Title: package slapd 2.4.31-1+nmu2ubuntu8.3 failed to install/upgrade: 
subprocess new pre-installation script returned error exit status 1
UpgradeStatus: Upgraded to trusty on 2017-03-17 (0 days ago)

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


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

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

Title:
  package slapd 2.4.31-1+nmu2ubuntu8.3 failed to install/upgrade:
  subprocess new pre-installation script returned error exit status 1

Status in openldap package in Ubuntu:
  New

Bug description:
  Error message while upgrading.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: slapd 2.4.31-1+nmu2ubuntu8.3
  ProcVersionSignature: Ubuntu 3.13.0-112.159-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-112-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Fri Mar 17 10:57:23 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  InstallationDate: Installed on 2014-05-09 (1042 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.0.1ubuntu2.17
  SourcePackage: openldap
  Title: package slapd 2.4.31-1+nmu2ubuntu8.3 failed to install/upgrade: 
subprocess new pre-installation script returned error exit status 1
  UpgradeStatus: Upgraded to trusty on 2017-03-17 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1673727/+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 1577596] Re: ntpd not started when using ntpdate

[Rick Frey]

Thanks for the update Robie.  I was not aware of ntpdate being
deprecated (appears to have been deprecated years ago).

For those like myself that require ntpd (the suggested alternative
systemd-timesyncd uses sntp which may not suffice in all use cases), I
think the best fix/workaround is to merely remove the ntpdate package. I
didn't really use ntpdate anymore and suspect it was still installed
from an earlier version of Ubuntu in my case (I've performed a fair
number of inline upgrades on system).

Historically, ntpdate was run prior to starting ntpd in case the clock
was too far off for ntpd to sync.  In looking at the ntp package
further, I see that /etc/default/ntp includes the '-g' option which
allows ntpd to perform a one time sync that would accommodate a clock
with any delta.  This in itself makes ntpdate unneeded for those running
ntp service.  Additionally, ntpd can also be run with arguments to
simulate behavior of ntpdate if needed.

So, if I understand correctly, the ntp package really has no bug (at
least related to starting at boot).  Issue was really due to bug with
deprecated ntpdate package which should be removed if running ntp
anyway.

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

Title:
  ntpd not started when using ntpdate

Status in init-system-helpers package in Ubuntu:
  Confirmed
Status in ntp package in Ubuntu:
  Won't Fix

Bug description:
  After updating from 14.04 to 16.04 on a number of my systems, ntpd no
  longer starts at boot on any of those systems.

  `systemctl status ntp` shows:
 ntp.service - LSB: Start NTP daemon
 Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
 Active: inactive (dead)
   Docs: man:systemd-sysv-generator(8)
  May 02 19:10:14 host systemd[1]: Stopped LSB: Start NTP daemon.
  May 02 19:10:17 host systemd[1]: Stopped LSB: Start NTP daemon.

  Manually starting it using `systemctl start ntp` works fine.  However,
  systemd does not seem to want to start it automatically at boot time.


  As best as I can tell based on trial and error, there is something
  special about the combination of the service being named "ntp.service"
  and the service depending on network.target.  However, I haven't been
  able to identify exactly what is causing this.

  If I copy the init script to any other name, everything works fine:
  cp /etc/init.d/ntp /etc/init.d/ntpd
  Edit /etc/init.d/ntpd and change "Provides: ntp" to "Provides: ntpd"
  systemctl enable ntpd
  # After a reboot, ntpd.service is started, but ntp.service is not.

  If I remove "$network" from the "# Required-Start: $network $remote_fs
  $syslog" line in /etc/init.d/ntp, then systemd starts it automatically
  ... But of course it is started before the network comes up, so it
  fails.

  If I replace /etc/init.d/ntp with a file containing only the following, 
systemd won't try to start it automatically at boot:
  #!/bin/sh
  ### BEGIN INIT INFO
  # Provides: ntp
  # Required-Start: $network
  # Required-Stop: $network
  # Default-Start: 2 3 4 5
  # Default-Stop: 1
  # Short-Description: Start NTP daemon
  ### END INIT INFO
  echo "script was run" >> /ntp.log

  If I rename that same dummy script to /etc/init.d/ntp2, it is started
  automatically at boot.

  However, grepping the systemd source code and my systemd config files for ntp 
doesn't seem to find anything that might cause this behavior:
  /etc/systemd# grep -iR ntp *
  timesyncd.conf:#NTP=
  timesyncd.conf:#FallbackNTP=ntp.ubuntu.com
  /lib/systemd# grep -R ntp *
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/ntpd
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/openntpd
  Binary file systemd-networkd matches
  Binary file systemd-timedated matches
  Binary file systemd-timesyncd matches

  What else can I do to debug this further?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1577596/+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 1577596] Re: ntpd not started when using ntpdate

[Rick Frey]

I'm seeing same behavior as Alex where failure of ntpdate is preventing
ntpd from starting.  ntpdate is logging same message indicating failure
due to name resolution (Bind not running yet at boot):

Sep 16 10:40:09 scorpion ntpdate[1033]: name server cannot be used:
Temporary failure in name resolution (-3)

The script /etc/network/if-up.d/ntpdate does attempt to stop any running
ntp service prior to running ntpdate but then exits without restarting
ntp if ntpdate-debian fails.

I modified /etc/network/if-up.d/ntpdate to only log a message and exit
as a workaround and ntpd now starts at boot.

I'm still a bit puzzled why ntpd doesn't attempt to start after
/etc/network/if-up.d/ntpdate fails (multiple times in my case due to
multiple interfaces on host).  When /etc/network/if-up.d/ntpdate
runs/fails, there is no log message from ntp indicating it tried to
start (neither before nor after ntpdate fails).  However, after applying
my workaround, the log message for ntp service is one second after last
run of /etc/network/if-up.d/ntpdate.  I would have thought that the
failure of ntpdate would not prevent the later startup of ntp.  I'm
guessing that /etc/network/if-up.d/ntpdate initiates a stop in parallel
to systemd start of ntpd before it logs anything to syslog.

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

Title:
  ntpd not started when using ntpdate

Status in init-system-helpers package in Ubuntu:
  Confirmed
Status in ntp package in Ubuntu:
  Confirmed

Bug description:
  After updating from 14.04 to 16.04 on a number of my systems, ntpd no
  longer starts at boot on any of those systems.

  `systemctl status ntp` shows:
 ntp.service - LSB: Start NTP daemon
 Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
 Active: inactive (dead)
   Docs: man:systemd-sysv-generator(8)
  May 02 19:10:14 host systemd[1]: Stopped LSB: Start NTP daemon.
  May 02 19:10:17 host systemd[1]: Stopped LSB: Start NTP daemon.

  Manually starting it using `systemctl start ntp` works fine.  However,
  systemd does not seem to want to start it automatically at boot time.


  As best as I can tell based on trial and error, there is something
  special about the combination of the service being named "ntp.service"
  and the service depending on network.target.  However, I haven't been
  able to identify exactly what is causing this.

  If I copy the init script to any other name, everything works fine:
  cp /etc/init.d/ntp /etc/init.d/ntpd
  Edit /etc/init.d/ntpd and change "Provides: ntp" to "Provides: ntpd"
  systemctl enable ntpd
  # After a reboot, ntpd.service is started, but ntp.service is not.

  If I remove "$network" from the "# Required-Start: $network $remote_fs
  $syslog" line in /etc/init.d/ntp, then systemd starts it automatically
  ... But of course it is started before the network comes up, so it
  fails.

  If I replace /etc/init.d/ntp with a file containing only the following, 
systemd won't try to start it automatically at boot:
  #!/bin/sh
  ### BEGIN INIT INFO
  # Provides: ntp
  # Required-Start: $network
  # Required-Stop: $network
  # Default-Start: 2 3 4 5
  # Default-Stop: 1
  # Short-Description: Start NTP daemon
  ### END INIT INFO
  echo "script was run" >> /ntp.log

  If I rename that same dummy script to /etc/init.d/ntp2, it is started
  automatically at boot.

  However, grepping the systemd source code and my systemd config files for ntp 
doesn't seem to find anything that might cause this behavior:
  /etc/systemd# grep -iR ntp *
  timesyncd.conf:#NTP=
  timesyncd.conf:#FallbackNTP=ntp.ubuntu.com
  /lib/systemd# grep -R ntp *
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/ntpd
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/openntpd
  Binary file systemd-networkd matches
  Binary file systemd-timedated matches
  Binary file systemd-timesyncd matches

  What else can I do to debug this further?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1577596/+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 1618322] Re: Bluetooth switcher remians off if turn on and off fight mode

[Rick Timmis]

I have this issue on BQ M10 running OTA-12 in my case I see this bug
when connecting Bluetoothdevices, such as headphones.

How to replicate.

1 drag down context menu and goto bluetooth. 
2 Set Bluetooth switched off
3 Click Bluetooth settings which will open system settings
4 From the open system settings switch bluetooth on
5 Now drag down context menu and notice Bluetooth is still off

You end up in a state where System settings and Context menu Bluetooth
states are opposite, and you can not get Bluetooth to activate.

** Summary changed:

- Bluetooth switcher remians off if turn on and off fight mode
+ Bluetooth switcher remains off if turn on and off fight mode

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

Title:
  Bluetooth switcher remains off if turn on and off fight mode

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Running unity8 session on 16.04

  steps:
  1.Ensure bluetooth switch is on
  2.Turn on Flight Mode
  3.Turn off Flight Mode

  Expected:
  Bluetooth switch turns off after step2, and it turns back on after step3

  Actual:
  Bluetooth switch remains off

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1618322/+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 1600658] Re: package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

[Rick Bradshaw]

I got this error when doing a dist-upgrade from 14.4 LTS to the new
16.04

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

Title:
  package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 139

Status in shared-mime-info package in Ubuntu:
  Confirmed

Bug description:
  The errors keep popping up when I start the computer that system
  programs have crashed.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shared-mime-info 1.5-2ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Jul 11 00:14:17 2016
  DuplicateSignature:
   package:shared-mime-info:1.5-2ubuntu0.1
   Processing triggers for shared-mime-info (1.5-2ubuntu0.1) ...
   Segmentation fault (core dumped)
   dpkg: error processing package shared-mime-info (--unpack):
subprocess installed post-installation script returned error exit status 139
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 139
  InstallationDate: Installed on 2016-05-14 (57 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 139
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1600658/+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 1594768] [NEW] package libexpat1-dev 2.1.0-7ubuntu0.16.04.2 failed to install/upgrade: subproces dpkg-deb --fsys-tarfile gaf een foutwaarde 2 terug

[Rick]

Public bug reported:

When Ubuntu starts I've got this message.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libexpat1-dev 2.1.0-7ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Tue Jun 21 10:42:05 2016
DpkgTerminalLog:
 Uitpakken van .../libexpat1-dev_2.1.0-7ubuntu0.16.04.2_amd64.deb wordt 
voorbereid...
 Bezig met uitpakken van libexpat1-dev:amd64 (2.1.0-7ubuntu0.16.04.2) over 
(2.1.0-7ubuntu0.16.04.1) ...
 dpkg-deb: fout: kan niet lezen uit archief 
'/var/cache/apt/archives/libexpat1-dev_2.1.0-7ubuntu0.16.04.2_amd64.deb': 
Bestand of map bestaat niet
 dpkg: fout bij verwerken van archief 
/var/cache/apt/archives/libexpat1-dev_2.1.0-7ubuntu0.16.04.2_amd64.deb 
(--unpack):
  subproces dpkg-deb --fsys-tarfile gaf een foutwaarde 2 terug
ErrorMessage: subproces dpkg-deb --fsys-tarfile gaf een foutwaarde 2 terug
InstallationDate: Installed on 2016-04-23 (59 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: expat
Title: package libexpat1-dev 2.1.0-7ubuntu0.16.04.2 failed to install/upgrade: 
subproces dpkg-deb --fsys-tarfile gaf een foutwaarde 2 terug
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package libexpat1-dev 2.1.0-7ubuntu0.16.04.2 failed to
  install/upgrade: subproces dpkg-deb --fsys-tarfile gaf een foutwaarde
  2 terug

Status in expat package in Ubuntu:
  New

Bug description:
  When Ubuntu starts I've got this message.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libexpat1-dev 2.1.0-7ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Jun 21 10:42:05 2016
  DpkgTerminalLog:
   Uitpakken van .../libexpat1-dev_2.1.0-7ubuntu0.16.04.2_amd64.deb wordt 
voorbereid...
   Bezig met uitpakken van libexpat1-dev:amd64 (2.1.0-7ubuntu0.16.04.2) over 
(2.1.0-7ubuntu0.16.04.1) ...
   dpkg-deb: fout: kan niet lezen uit archief 
'/var/cache/apt/archives/libexpat1-dev_2.1.0-7ubuntu0.16.04.2_amd64.deb': 
Bestand of map bestaat niet
   dpkg: fout bij verwerken van archief 
/var/cache/apt/archives/libexpat1-dev_2.1.0-7ubuntu0.16.04.2_amd64.deb 
(--unpack):
subproces dpkg-deb --fsys-tarfile gaf een foutwaarde 2 terug
  ErrorMessage: subproces dpkg-deb --fsys-tarfile gaf een foutwaarde 2 terug
  InstallationDate: Installed on 2016-04-23 (59 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: expat
  Title: package libexpat1-dev 2.1.0-7ubuntu0.16.04.2 failed to 
install/upgrade: subproces dpkg-deb --fsys-tarfile gaf een foutwaarde 2 terug
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1594768/+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 1589836] [NEW] package libxml2-utils 2.9.3+dfsg1-1 failed to install/upgrade: krijg geen toegang tot archief: Bestand of map bestaat niet

[Rick]

Public bug reported:

The package failed to upgrade in the terminal.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libxml2-utils 2.9.3+dfsg1-1
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Tue Jun  7 09:40:41 2016
ErrorMessage: krijg geen toegang tot archief: Bestand of map bestaat niet
InstallationDate: Installed on 2016-04-23 (44 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: libxml2
Title: package libxml2-utils 2.9.3+dfsg1-1 failed to install/upgrade: krijg 
geen toegang tot archief: Bestand of map bestaat niet
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package libxml2-utils 2.9.3+dfsg1-1 failed to install/upgrade: krijg
  geen toegang tot archief: Bestand of map bestaat niet

Status in libxml2 package in Ubuntu:
  New

Bug description:
  The package failed to upgrade in the terminal.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libxml2-utils 2.9.3+dfsg1-1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Jun  7 09:40:41 2016
  ErrorMessage: krijg geen toegang tot archief: Bestand of map bestaat niet
  InstallationDate: Installed on 2016-04-23 (44 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: libxml2
  Title: package libxml2-utils 2.9.3+dfsg1-1 failed to install/upgrade: krijg 
geen toegang tot archief: Bestand of map bestaat niet
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1589836/+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 1546641] Re: unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed()

[Rick Harris]

Many thanks Martin.

Trawling through the linux-usb and distro kernel mailing list archives
shows that the kernel blocking problem has been around for some time and
discussed at length.

What it seems to boil down to is this:
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tree/drivers/usb/core/hub.c#n67

The fact that parameters exist to force or fallback to the old
initialisation scheme indicates the kernel devs. are aware there could
be problems with the way USB devices are initialised, depending on the
USB device.

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

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

Status in Upower:
  Unknown
Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in upower package in Ubuntu:
  Fix Committed
Status in unity-settings-daemon source package in Xenial:
  Triaged
Status in upower source package in Xenial:
  Confirmed
Status in unity-settings-daemon source package in Yakkety:
  Triaged
Status in upower source package in Yakkety:
  Fix Committed

Bug description:
  https://errors.ubuntu.com/problem/8ca9c548fc4e2fc1d4bf827bbd85c72df59313f8

  Ubuntu 16.04 crashes immediately on login. Default settings not
  applied and appearance is a bit ugly (incorrect font hinting, in-
  window menus etc).

  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Feb 17 13:52:13 2016
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2016-02-08 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x3aae60fe69 : 
mov(%rbx),%rdi
   PC (0x3aae60fe69) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   up_exported_daemon_get_lid_is_closed () from 
/usr/lib/x86_64-linux-gnu/libupower-glib.so.3
   gsd_power_manager_start () from 
/usr/lib/unity-settings-daemon-1.0/libpower.so
   ?? () from /usr/lib/unity-settings-daemon-1.0/libpower.so
   gnome_settings_plugin_info_activate ()
   ?? ()
  Title: unity-settings-daemon crashed with SIGSEGV in 
up_exported_daemon_get_lid_is_closed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/upower/+bug/1546641/+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 1546641] Re: unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed()

[Rick Harris]

So whether it be broken/missing libs or bad USB device enumeration
causing upowerd to be either not available or slow to start, it would
seem unity-settings-daemon could at least be improved to be robust
enough not to segfault if upowerd is not present.

In the meantime, I was able to solve the USB device problem to work
around upower.service slow start by adding the kernel commandline
parameters 'usbcore.use_both_schemes=y usbcore.old_scheme_first=y'.

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

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

Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in upower package in Ubuntu:
  Confirmed
Status in unity-settings-daemon source package in Xenial:
  Triaged
Status in upower source package in Xenial:
  Confirmed
Status in unity-settings-daemon source package in Yakkety:
  Triaged
Status in upower source package in Yakkety:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/8ca9c548fc4e2fc1d4bf827bbd85c72df59313f8

  Ubuntu 16.04 crashes immediately on login. Default settings not
  applied and appearance is a bit ugly (incorrect font hinting, in-
  window menus etc).

  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Feb 17 13:52:13 2016
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2016-02-08 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x3aae60fe69 : 
mov(%rbx),%rdi
   PC (0x3aae60fe69) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   up_exported_daemon_get_lid_is_closed () from 
/usr/lib/x86_64-linux-gnu/libupower-glib.so.3
   gsd_power_manager_start () from 
/usr/lib/unity-settings-daemon-1.0/libpower.so
   ?? () from /usr/lib/unity-settings-daemon-1.0/libpower.so
   gnome_settings_plugin_info_activate ()
   ?? ()
  Title: unity-settings-daemon crashed with SIGSEGV in 
up_exported_daemon_get_lid_is_closed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1546641/+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 1552371] Re: Unexpected display on

[Rick Timmis]

Aquaris M10, running first update after purchase. Screen comes on to
lock prompt, stays on and even pressing power button it goes off for 1
second then back on again.

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

Title:
  Unexpected display on

Status in Canonical System Image:
  Confirmed
Status in Mir:
  New
Status in Unity System Compositor:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed

Bug description:
  NOTE: kgunn suggests this bug be about 1) not 2) here

  1)
  I have been noticing my phone and tablet occasionally turning on without 
interaction. Several times with my phone in my pocket I found it in the 
emergency call UI
  I also see the tablet display turn on while lying idle on the desk. Freiza & 
Arale

  2)
  I have reproduced one case such that turning on a BT device (headset) causes 
the phone to light up and display the volume slider. Similarly turning on the 
BT keyboard while the tablet screen is off caused the display to turn on.These 
may be as intended.

  I suspect other BT events can similarly resume the device and/or turn on the 
display if it happens to be awake due to the 5 min polling timer.
  The proximity sensor is also not honored when this happens, if its covered 
the screen still comes on.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552371/+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 1546641] Re: unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed()

[Rick Harris]

One last thing...ice in comment #12 said:
"Some people say it has to do with a ASMedia USB Controller"

Have found that USB enumeration failure can cause a bottleneck in
systemd getting the upower.service unit to finally start.

You'll know if the system is hit with this as it'll be much slower to boot and 
the kernel will spew errors of the type:
kernel: usb 2-1.1: device descriptor read/64, error -110
kernel: usb 2-1-port1: unable to enumerate USB device

Occasionally after several suspend/resumes, I have a USB device
(wireless game controller) that must be unplugged/replugged to stop this
error (simply rebooting does not fix).

Have found on my laptop, if the USB enumeration boots through without
any error then it's quick enough to have systemd start  upower.service
in time before u-s-d is started, otherwise the u-s-d segfault occurs as
above.

Thanks :)

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

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

Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in upower package in Ubuntu:
  Confirmed
Status in unity-settings-daemon source package in Xenial:
  Triaged
Status in upower source package in Xenial:
  Confirmed
Status in unity-settings-daemon source package in Yakkety:
  Triaged
Status in upower source package in Yakkety:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/8ca9c548fc4e2fc1d4bf827bbd85c72df59313f8

  Ubuntu 16.04 crashes immediately on login. Default settings not
  applied and appearance is a bit ugly (incorrect font hinting, in-
  window menus etc).

  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Feb 17 13:52:13 2016
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2016-02-08 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x3aae60fe69 : 
mov(%rbx),%rdi
   PC (0x3aae60fe69) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   up_exported_daemon_get_lid_is_closed () from 
/usr/lib/x86_64-linux-gnu/libupower-glib.so.3
   gsd_power_manager_start () from 
/usr/lib/unity-settings-daemon-1.0/libpower.so
   ?? () from /usr/lib/unity-settings-daemon-1.0/libpower.so
   gnome_settings_plugin_info_activate ()
   ?? ()
  Title: unity-settings-daemon crashed with SIGSEGV in 
up_exported_daemon_get_lid_is_closed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1546641/+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 1546641] Re: unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed()

[Rick Harris]

Looks to be a race condition where the session (and so unity-settings-daemon) 
is started before systemd has finished starting the upower.service unit.
u-s-d tries to query the state of power and segfaults when upowerd hasn't 
finished initialising to be able respond.

>From syslog:
17:14:31 kernel: unity-settings-[1722]: segfault at 0 ip 7fe3799805a9 sp 
7ffec6513af0 error 4 in libupower-glib.so.3.0.1[7fe37996f000+25000]

17:14:50 dbus-daemon[460]: [system] Successfully activated service 
'org.freedesktop.UPower'

Confirmed this by doing the following:
1. Disabling lightdm from autostarting: systemctl disable lightdm

2. Reboot and wait until systemd starts upower.service

3. Start lightdm: systemctl start lightdm

4. u-s-d starts without issue and so default settings and themes are
applied, media keys work, etc.

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

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

Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in upower package in Ubuntu:
  Confirmed
Status in unity-settings-daemon source package in Xenial:
  Triaged
Status in upower source package in Xenial:
  Confirmed
Status in unity-settings-daemon source package in Yakkety:
  Triaged
Status in upower source package in Yakkety:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/8ca9c548fc4e2fc1d4bf827bbd85c72df59313f8

  Ubuntu 16.04 crashes immediately on login. Default settings not
  applied and appearance is a bit ugly (incorrect font hinting, in-
  window menus etc).

  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Feb 17 13:52:13 2016
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2016-02-08 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x3aae60fe69 : 
mov(%rbx),%rdi
   PC (0x3aae60fe69) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   up_exported_daemon_get_lid_is_closed () from 
/usr/lib/x86_64-linux-gnu/libupower-glib.so.3
   gsd_power_manager_start () from 
/usr/lib/unity-settings-daemon-1.0/libpower.so
   ?? () from /usr/lib/unity-settings-daemon-1.0/libpower.so
   gnome_settings_plugin_info_activate ()
   ?? ()
  Title: unity-settings-daemon crashed with SIGSEGV in 
up_exported_daemon_get_lid_is_closed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1546641/+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 1251915] Re: Dash + zeitgeist does not log use of KDE applications for 'Recently used'

[Rick Harris]

Bug still present in Xenial.

Creating symlinks as suggested in comment #2 has the unwanted side
effect of creating duplicate entries for KDE applications in the Search
and Applications lense.

So it would seem the proper fix would instead be for Unity to grab the
path of where the konsole.desktop file resides, and if it is found to be
in /usr/share/applications/kde4, then the desktop filename presented to
zeitgeist should be changed from konsole.desktop to kde4-konsole.desktop

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

Title:
  Dash + zeitgeist does not log use of KDE applications for 'Recently
  used'

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in zeitgeist package in Ubuntu:
  New

Bug description:
  Using Saucy 13.10 and Trusty 14.04, when using KDE applications
  launched from the Dash, they do not show up as 'Recently used' neither
  in the Home or Applications lenses.

  Seems zeitgeist or the information presented to it cannot get the path
  to the KDE application's *.desktop file.

  Using 'konsole' as a KDE application example:

  ~ $ /usr/libexec/zeitgeist-fts --log-level=DEBUG
  ** (zeitgeist-fts:28799): DEBUG: zeitgeist-fts.vala:106: got insertion 
notification
  ** (zeitgeist-fts:28799): DEBUG: Indexing event with ID: 6382
  ** (zeitgeist-fts:28799): WARNING **: Unable to get info on 
application://konsole.desktop

  This happens because 'konsole.desktop' resides in
  /usr/share/applications/kde4/konsole.desktop

  If I symlink or copy 'konsole.desktop' to
  /usr/share/applications/konsole.desktop, then everything works as it
  should, zeitgeist index's the event correctly and Konsole shows under
  'Recently used' for Home and Applications lenses.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1251915/+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 1325142] Re: failure to update libpam-systemd in 14.04 due to missing logind init script

[Rick R]

I confirm that this is still an issue in Trusty. However, in #1326412,
Dimitri John Ledkov wrote

> This is fixed in utopic, and will not be fixed in trusty. 
> One will have to boot under upstart to dist-upgrade reliable within trusty.

https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/+bug/1326412

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

Title:
  failure to update libpam-systemd in 14.04 due to missing logind init
  script

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Trusty:
  Fix Released
Status in systemd source package in Utopic:
  Fix Released

Bug description:
  Hi,

  while running inside an i386 lubuntu 14.04 chroot, upgrading libpam-
  systemd to version 204-5ubuntu20.2 fails leaving dpkg in a broken
  state. 'apt-get -f install' from within the chroot will not fix it,
  but if the build is made bootable and put into a iso/VM you can
  recover that way in a live session.

  the problem seems to be the /var/lib/dpkg/info/libpam-systemd:i386.prerm 
script failing to bring down the logind daemon with 'invoke-rc.d systemd-logind 
stop', because invoke-rd.d is only looking for the /etc/init.d/ script (doesn't 
exist) and not /etc/init/systemd-logind.conf (does exist).
  ?

  
  Reading package lists...
  Building dependency tree...
  Reading state information...
  The following packages will be upgraded:
libpam-systemd
  1 upgraded, 0 newly installed, 0 to remove and 113 not upgraded.
  3 not fully installed or removed.
  Need to get 0 B/25.2 kB of archives.
  After this operation, 1024 B of additional disk space will be used.
  (Reading database ... 113986 files and directories currently installed.)
  Preparing to unpack .../libpam-systemd_204-5ubuntu20.2_i386.deb ...
  invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
  dpkg: warning: subprocess old pre-removal script returned error exit status 
100
  dpkg: trying script from the new package instead ...
  invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
  dpkg: error processing archive 
/var/cache/apt/archives/libpam-systemd_204-5ubuntu20.2_i386.deb (--unpack):
   subprocess new pre-removal script returned error exit status 100
  invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
  dpkg: error while cleaning up:
   subprocess installed post-installation script returned error exit status 100
  Errors were encountered while processing:
   /var/cache/apt/archives/libpam-systemd_204-5ubuntu20.2_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  Our build logs available upon request, but the scripts to setup the chroot to 
recreate it are here:

https://trac.osgeo.org/osgeo/browser/livedvd/gisvm/trunk/bin/build_chroot_nightly.sh

https://trac.osgeo.org/osgeo/browser/livedvd/gisvm/trunk/bin/inchroot_nightly.sh

  
  In a web-search I notice a few others running into the same bug,

  chatter on irc at [18:10], http://irclogs.ubuntu.com/2013/05/28
  /%23ubuntu-devel.txt

  someone else's build log:
  https://launchpad.net/~qutim/+archive/qutim/+build/6039800

  launchpad bug #1323575 seems to be a duplicate of this one.

  
  perhaps related to older launchpad bug #1305395 ?

  note we are also suffering from a failure with update-initramfs, not sure of 
the root cause of that one but I thought I'd mention it in case they were 
related, since they both started happening about the same time, a couple weeks 
ago. (launchpad bug #1317602)
  It all worked ok after the inital releases of 14.04, so something to do with 
a package update since then.

  
  thanks,
  Hamish

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1325142/+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 1534756] [NEW] package libc6-dev 2.19-0ubuntu6 failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libc.a' to '/usr/lib/x86_64-linux-gnu/libc.a.

[Rick Martel]

Public bug reported:

can't instal Google Chrome

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libc6-dev 2.19-0ubuntu6
ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
Uname: Linux 3.13.0-66-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
Date: Fri Jan 15 11:29:42 2016
DpkgHistoryLog:
 Start-Date: 2016-01-15  11:29:23
 Commandline: aptdaemon role='role-fix-broken-depends' sender=':1.61'
 Install: libc6-i386:amd64 (2.19-0ubuntu6.6, automatic)
 Upgrade: libc6-dbg:amd64 (2.19-0ubuntu6, 2.19-0ubuntu6.6), libc6-dev:amd64 
(2.19-0ubuntu6, 2.19-0ubuntu6.6)
DuplicateSignature: package:libc6-dev:2.19-0ubuntu6:cannot copy extracted data 
for './usr/lib/x86_64-linux-gnu/libc.a' to 
'/usr/lib/x86_64-linux-gnu/libc.a.dpkg-new': unexpected end of file or stream
ErrorMessage: cannot copy extracted data for 
'./usr/lib/x86_64-linux-gnu/libc.a' to 
'/usr/lib/x86_64-linux-gnu/libc.a.dpkg-new': unexpected end of file or stream
InstallationDate: Installed on 2015-10-30 (76 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
SourcePackage: eglibc
Title: package libc6-dev 2.19-0ubuntu6 failed to install/upgrade: cannot copy 
extracted data for './usr/lib/x86_64-linux-gnu/libc.a' to 
'/usr/lib/x86_64-linux-gnu/libc.a.dpkg-new': unexpected end of file or stream
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package trusty

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

Title:
  package libc6-dev 2.19-0ubuntu6 failed to install/upgrade: cannot copy
  extracted data for './usr/lib/x86_64-linux-gnu/libc.a' to
  '/usr/lib/x86_64-linux-gnu/libc.a.dpkg-new': unexpected end of file or
  stream

Status in eglibc package in Ubuntu:
  New

Bug description:
  can't instal Google Chrome

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libc6-dev 2.19-0ubuntu6
  ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-66-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Fri Jan 15 11:29:42 2016
  DpkgHistoryLog:
   Start-Date: 2016-01-15  11:29:23
   Commandline: aptdaemon role='role-fix-broken-depends' sender=':1.61'
   Install: libc6-i386:amd64 (2.19-0ubuntu6.6, automatic)
   Upgrade: libc6-dbg:amd64 (2.19-0ubuntu6, 2.19-0ubuntu6.6), libc6-dev:amd64 
(2.19-0ubuntu6, 2.19-0ubuntu6.6)
  DuplicateSignature: package:libc6-dev:2.19-0ubuntu6:cannot copy extracted 
data for './usr/lib/x86_64-linux-gnu/libc.a' to 
'/usr/lib/x86_64-linux-gnu/libc.a.dpkg-new': unexpected end of file or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/x86_64-linux-gnu/libc.a' to 
'/usr/lib/x86_64-linux-gnu/libc.a.dpkg-new': unexpected end of file or stream
  InstallationDate: Installed on 2015-10-30 (76 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: eglibc
  Title: package libc6-dev 2.19-0ubuntu6 failed to install/upgrade: cannot copy 
extracted data for './usr/lib/x86_64-linux-gnu/libc.a' to 
'/usr/lib/x86_64-linux-gnu/libc.a.dpkg-new': unexpected end of file or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1534756/+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 1512033] [NEW] package libc6-dbg 2.19-0ubuntu6 failed to install/upgrade: cannot copy extracted data for './usr/lib/debug/usr/lib/x86_64-linux-gnu/gconv/SHIFT_JISX0213.so' to '/u

[Rick Martel]

Public bug reported:

ubuntu 14.04 
driver for nvidia won't install

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libc6-dbg 2.19-0ubuntu6
ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
Uname: Linux 3.13.0-66-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
Date: Sat Oct 31 18:48:48 2015
Dependencies:
 gcc-4.9-base 4.9.1-0ubuntu1
 libc6 2.19-0ubuntu6.6
 libgcc1 1:4.9.1-0ubuntu1
 multiarch-support 2.19-0ubuntu6
DuplicateSignature: package:libc6-dbg:2.19-0ubuntu6:cannot copy extracted data 
for './usr/lib/debug/usr/lib/x86_64-linux-gnu/gconv/SHIFT_JISX0213.so' to 
'/usr/lib/debug/usr/lib/x86_64-linux-gnu/gconv/SHIFT_JISX0213.so.dpkg-new': 
unexpected end of file or stream
ErrorMessage: cannot copy extracted data for 
'./usr/lib/debug/usr/lib/x86_64-linux-gnu/gconv/SHIFT_JISX0213.so' to 
'/usr/lib/debug/usr/lib/x86_64-linux-gnu/gconv/SHIFT_JISX0213.so.dpkg-new': 
unexpected end of file or stream
InstallationDate: Installed on 2015-10-30 (1 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
SourcePackage: eglibc
Title: package libc6-dbg 2.19-0ubuntu6 failed to install/upgrade: cannot copy 
extracted data for 
'./usr/lib/debug/usr/lib/x86_64-linux-gnu/gconv/SHIFT_JISX0213.so' to 
'/usr/lib/debug/usr/lib/x86_64-linux-gnu/gconv/SHIFT_JISX0213.so.dpkg-new': 
unexpected end of file or stream
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  package libc6-dbg 2.19-0ubuntu6 failed to install/upgrade: cannot copy
  extracted data for './usr/lib/debug/usr/lib/x86_64-linux-
  gnu/gconv/SHIFT_JISX0213.so' to '/usr/lib/debug/usr/lib/x86_64-linux-
  gnu/gconv/SHIFT_JISX0213.so.dpkg-new': unexpected end of file or
  stream

Status in eglibc package in Ubuntu:
  New

Bug description:
  ubuntu 14.04 
  driver for nvidia won't install

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libc6-dbg 2.19-0ubuntu6
  ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-66-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Sat Oct 31 18:48:48 2015
  Dependencies:
   gcc-4.9-base 4.9.1-0ubuntu1
   libc6 2.19-0ubuntu6.6
   libgcc1 1:4.9.1-0ubuntu1
   multiarch-support 2.19-0ubuntu6
  DuplicateSignature: package:libc6-dbg:2.19-0ubuntu6:cannot copy extracted 
data for './usr/lib/debug/usr/lib/x86_64-linux-gnu/gconv/SHIFT_JISX0213.so' to 
'/usr/lib/debug/usr/lib/x86_64-linux-gnu/gconv/SHIFT_JISX0213.so.dpkg-new': 
unexpected end of file or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/debug/usr/lib/x86_64-linux-gnu/gconv/SHIFT_JISX0213.so' to 
'/usr/lib/debug/usr/lib/x86_64-linux-gnu/gconv/SHIFT_JISX0213.so.dpkg-new': 
unexpected end of file or stream
  InstallationDate: Installed on 2015-10-30 (1 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: eglibc
  Title: package libc6-dbg 2.19-0ubuntu6 failed to install/upgrade: cannot copy 
extracted data for 
'./usr/lib/debug/usr/lib/x86_64-linux-gnu/gconv/SHIFT_JISX0213.so' to 
'/usr/lib/debug/usr/lib/x86_64-linux-gnu/gconv/SHIFT_JISX0213.so.dpkg-new': 
unexpected end of file or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1512033/+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 1494478] Re: Messenger app shows an mms as being from a group

[Rick Spencer]

Note that I have t-mobile

To whoever made mms start working with t-mobile in the US: thanks! ;)

** Attachment added: "screen shot showing issue"
   
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1494478/+attachment/4460789/+files/double.png

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

Title:
  Messenger app shows an mms as being from a group

Status in messaging-app package in Ubuntu:
  New

Bug description:
  Steps:

  1. Receive a message with an attached picture
  2. Note that the message is sent to a group
  3. Click on the little contacts icon in the top right

  Result:
  It shows two contacts, the sender and also your phone number

  Expected:
  It only shows the sender

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1494478/+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 1494478] [NEW] Messenger app shows an mms as being from a group

[Rick Spencer]

Public bug reported:

Steps:

1. Receive a message with an attached picture
2. Note that the message is sent to a group
3. Click on the little contacts icon in the top right

Result:
It shows two contacts, the sender and also your phone number

Expected:
It only shows the sender

** Affects: messaging-app (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Messenger app shows an mms as being from a group

Status in messaging-app package in Ubuntu:
  New

Bug description:
  Steps:

  1. Receive a message with an attached picture
  2. Note that the message is sent to a group
  3. Click on the little contacts icon in the top right

  Result:
  It shows two contacts, the sender and also your phone number

  Expected:
  It only shows the sender

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1494478/+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 1474958] [NEW] bind mount produces incorrect entry in mtab

[Rick Foos]

Public bug reported:

Ubuntu 15.04
mount:
  Installed: 2.25.2-4ubuntu2
  Candidate: 2.25.2-4ubuntu2
  Version table:
 *** 2.25.2-4ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
100 /var/lib/dpkg/status

System has LVM on SSD standard install ext4 filesystem. 
(/dev/mapper/ubuntu--vg-root)
mdadm RAID5 3 disks, btrfs filesystem (/dev/md127p1)
RAID5 is mounted at /mnt/raid at boot.
---
Bind mounts only display the device mount, not the from directory.
The mount works, but the mtab entry is incorrect.

# From LVM device, to LVM device.
mount -o bind /home/rfoos /srv/nfs4/homes
# From Raid device, to LVM device
mount -o bind /mnt/raid/var/lib/libvirt /var/lib/libvirt
# With corrected fstab entries (below) mount -a does work
mount -a

--- /etc/mtab entries
/dev/mapper/ubuntu--vg-root /srv/nfs4/homes ext4 
rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/md127p1 /var/lib/libvirt btrfs rw,nosuid,nodev,relatime,space_cache 0 0
/dev/md127p1 /srv/nfs4/share btrfs rw,nosuid,nodev,relatime,space_cache 0 0

--- mount list of mounts
/dev/md127p1 on /mnt/raid type btrfs (rw,nosuid,nodev,relatime,space_cache)
/dev/md127p1 on /var/lib/libvirt type btrfs 
(rw,nosuid,nodev,relatime,space_cache)
/dev/mapper/ubuntu--vg-root on /srv/nfs4/homes type ext4 
(rw,relatime,errors=remount-ro,data=ordered)

--- corrected fstab entries.
# mount raid device
/dev/md127p1 /mnt/raid btrfs rw,nosuid,nodev,relatime,space_cache 0 0
# corrected entries
/mnt/raid/var/lib/libvirt /var/lib/libvirt none bind 0 0
/home/rfoos /srv/nfs4/homes none bind 0 0

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

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

Title:
  bind mount produces incorrect entry in mtab

Status in util-linux package in Ubuntu:
  New

Bug description:
  Ubuntu 15.04
  mount:
Installed: 2.25.2-4ubuntu2
Candidate: 2.25.2-4ubuntu2
Version table:
   *** 2.25.2-4ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  System has LVM on SSD standard install ext4 filesystem. 
(/dev/mapper/ubuntu--vg-root)
  mdadm RAID5 3 disks, btrfs filesystem (/dev/md127p1)
  RAID5 is mounted at /mnt/raid at boot.
  ---
  Bind mounts only display the device mount, not the from directory.
  The mount works, but the mtab entry is incorrect.

  # From LVM device, to LVM device.
  mount -o bind /home/rfoos /srv/nfs4/homes
  # From Raid device, to LVM device
  mount -o bind /mnt/raid/var/lib/libvirt /var/lib/libvirt
  # With corrected fstab entries (below) mount -a does work
  mount -a

  --- /etc/mtab entries
  /dev/mapper/ubuntu--vg-root /srv/nfs4/homes ext4 
rw,relatime,errors=remount-ro,data=ordered 0 0
  /dev/md127p1 /var/lib/libvirt btrfs rw,nosuid,nodev,relatime,space_cache 0 0
  /dev/md127p1 /srv/nfs4/share btrfs rw,nosuid,nodev,relatime,space_cache 0 0

  --- mount list of mounts
  /dev/md127p1 on /mnt/raid type btrfs (rw,nosuid,nodev,relatime,space_cache)
  /dev/md127p1 on /var/lib/libvirt type btrfs 
(rw,nosuid,nodev,relatime,space_cache)
  /dev/mapper/ubuntu--vg-root on /srv/nfs4/homes type ext4 
(rw,relatime,errors=remount-ro,data=ordered)

  --- corrected fstab entries.
  # mount raid device
  /dev/md127p1 /mnt/raid btrfs rw,nosuid,nodev,relatime,space_cache 0 0
  # corrected entries
  /mnt/raid/var/lib/libvirt /var/lib/libvirt none bind 0 0
  /home/rfoos /srv/nfs4/homes none bind 0 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1474958/+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 1474280] [NEW] including a page inside a dialog breaks headers in a mainview

[Rick Spencer]

Public bug reported:

observe the following code available here: https://code.launchpad.net
/~rick-rickspencer3/+junk/pagesindialogs

When you run the app, click on the red rectangle. This causes a dialog
to appear. When you click close on the dialog, not that the header in
the mainview is gone. If you remove the Page{} from the dialog, this no
longer happens. As a result, you cannot reuse pages inside a dialog.

import QtQuick 2.0
import Ubuntu.Components 1.1
import Ubuntu.Components.Popups 1.0

MainView {
objectName: mainView

applicationName: reproducer.rick-rickspencer3
useDeprecatedToolbar: false

width: units.gu(40)
height: units.gu(75)

Page {
title: i18n.tr(app)
MouseArea {
anchors.fill: parent
Rectangle {
color: red
anchors.fill: parent
}
onClicked: PopupUtils.open(fakeComponent)
}
}
Component {
id: fakeComponent

Dialog {
id: fakeDialog

title: Fake Dialog
Page{
Button {
text: i18n.tr(Close)
onTriggered: {
PopupUtils.close(fakeDialog)
}
}
 }
}
 }
}

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

** Description changed:

  observe the following code available here: https://code.launchpad.net
  /~rick-rickspencer3/+junk/pagesindialogs
  
  When you run the app, click on the red rectangle. This causes a dialog
  to appear. When you click close on the dialog, not that the header in
  the mainview is gone. If you remove the Page{} from the dialog, this no
  longer happens. As a result, you cannot reuse pages inside a dialog.
  
  import QtQuick 2.0
  import Ubuntu.Components 1.1
  import Ubuntu.Components.Popups 1.0
  
- /*!
- \brief MainView with a Label and Button elements.
- */
- 
  MainView {
- // objectName for functional testing purposes (autopilot-qt5)
  objectName: mainView
  
- // Note! applicationName needs to match the name field of the click 
manifest
  applicationName: reproducer.rick-rickspencer3
- 
- /*
-  This property enables the application to change orientation
-  when the device is rotated. The default is false.
- */
- //automaticOrientation: true
- 
- // Removes the old toolbar and enables new features of the new header.
  useDeprecatedToolbar: false
  
  width: units.gu(40)
  height: units.gu(75)
  
  Page {
  title: i18n.tr(app)
  MouseArea {
  anchors.fill: parent
  Rectangle {
  color: red
  anchors.fill: parent
  }
  onClicked: PopupUtils.open(fakeComponent)
  }
  }
  Component {
  id: fakeComponent
  
  Dialog {
  id: fakeDialog
  
  title: Fake Dialog
+ Page{
  Button {
  text: i18n.tr(Close)
  onTriggered: {
  PopupUtils.close(fakeDialog)
  }
  }
- 
+  }
  }
   }
  }

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

Title:
  including a page inside a dialog breaks headers in a mainview

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  observe the following code available here: https://code.launchpad.net
  /~rick-rickspencer3/+junk/pagesindialogs

  When you run the app, click on the red rectangle. This causes a dialog
  to appear. When you click close on the dialog, not that the header in
  the mainview is gone. If you remove the Page{} from the dialog, this
  no longer happens. As a result, you cannot reuse pages inside a
  dialog.

  import QtQuick 2.0
  import Ubuntu.Components 1.1
  import Ubuntu.Components.Popups 1.0

  MainView {
  objectName: mainView

  applicationName: reproducer.rick-rickspencer3
  useDeprecatedToolbar: false

  width: units.gu(40)
  height: units.gu(75)

  Page {
  title: i18n.tr(app)
  MouseArea {
  anchors.fill: parent
  Rectangle {
  color: red
  anchors.fill: parent
  }
  onClicked: PopupUtils.open(fakeComponent)
  }
  }
  Component {
  id: fakeComponent

  Dialog {
  id: fakeDialog

  title: Fake Dialog
  Page{
  Button {
  text: i18n.tr(Close)
  onTriggered: {
  PopupUtils.close(fakeDialog)
  }
  }
   }
  }
   }
  }

To manage notifications about this bug go

[Touch-packages] [Bug 1245287] Re: upower showing keyboard at 0% charge

[Rick Ucker]

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

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

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

Title:
  upower showing keyboard at 0% charge

Status in Upower:
  Unknown
Status in upower package in Ubuntu:
  Confirmed

Bug description:
  This bug is new upon upgrading to 13.10; bug did not exist on 13.04,
  12.10 or 12.04.

  I'm using an apple wireless keyboard. I have replaced the batteries
  and confirmed they are fully charged with voltmeter.

  Keyboard is working fine but indicator says it's 0% and is red
  indicating some problem. Also upower says keyboard not present;
  bluetooth shows keyboards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/upower/+bug/1245287/+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 1319626] Re: Ubuntu One Captcha too hard to enter correctly

[Rick Ames]

How has this not been fixed yet? this problem has existed for years...

The captcha's almost always have some string of illegible r,n,u and m's.
It's so stupid.

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

Title:
  Ubuntu One Captcha too hard to enter correctly

Status in ubuntuone-client-data package in Ubuntu:
  Confirmed

Bug description:
  I tried to create a new Ubuntu One while setting up the Sofware Center
  suggested apps  (which required an Ubuntu One account) and ended
  frustated.

  The Captcha is really hard, I gave up on the account creation after 10
  tries, I'm a male on my twentys with normal vision and could not
  decipher the Captcha.

  Not even 4***.org captchas gives me troubles as those on the Ubuntu
  One register page.

  I suggest to improve the captchas so they're not so difficult to read,
  I can just imagie my dad would just close that window if he saw such a
  hard captcha.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntuone-client-data 13.05-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May 14 21:29:17 2014
  Dependencies:
   
  InstallationDate: Installed on 2014-05-15 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: ubuntuone-client-data
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntuone-client-data/+bug/1319626/+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 1442340] Re: telephony-service-indicator crash on an incoming sms

[Rick Spencer]

** Attachment added: _usr_bin_messaging-app.32011.crash
   
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1442340/+attachment/4370882/+files/_usr_bin_messaging-app.32011.crash

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

Title:
  telephony-service-indicator crash on an incoming sms

Status in telephony-service package in Ubuntu:
  New

Bug description:
  Sent an sms
  phone was awake and sitting in the messaging app
  I heard something to make me look at the phone but not a notification sound, 
maybe vibration
  unity restarted and when it came back up there was an SMS notification
  Crash file created at that time

  mako running rtm build 219
  Rick has reported this occurring on Vivid arale as well

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1442340/+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 1442340] Re: telephony-service-indicator crash on an incoming sms

[Rick Spencer]

** Attachment added: _usr_bin_unity8.32011.crash
   
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1442340/+attachment/4370881/+files/_usr_bin_unity8.32011.crash

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

Title:
  telephony-service-indicator crash on an incoming sms

Status in telephony-service package in Ubuntu:
  New

Bug description:
  Sent an sms
  phone was awake and sitting in the messaging app
  I heard something to make me look at the phone but not a notification sound, 
maybe vibration
  unity restarted and when it came back up there was an SMS notification
  Crash file created at that time

  mako running rtm build 219
  Rick has reported this occurring on Vivid arale as well

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1442340/+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 1442340] Re: telephony-service-indicator crash on an incoming sms

[Rick Spencer]

Attached two files which might possibly be related

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

Title:
  telephony-service-indicator crash on an incoming sms

Status in telephony-service package in Ubuntu:
  New

Bug description:
  Sent an sms
  phone was awake and sitting in the messaging app
  I heard something to make me look at the phone but not a notification sound, 
maybe vibration
  unity restarted and when it came back up there was an SMS notification
  Crash file created at that time

  mako running rtm build 219
  Rick has reported this occurring on Vivid arale as well

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1442340/+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 513644] Re: Does not log fsck invocations in /var/log/fsck/

[Rick Weinberger]

Can confirm still present in 14.04 - NOT Triaged.

** Changed in: mountall (Ubuntu)
   Status: Triaged = Confirmed

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

Title:
  Does not log fsck invocations in /var/log/fsck/

Status in mountall package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: mountall

  This concerns mountall 1.0 in Karmic.

  After fsck is invoked at boot time, the two log files in
  /var/log/fsck/ remain empty. In Jaunty, the
  /etc/init.d/check{fs,root}.sh scripts saved the output of the commands
  to that directory (A log is being saved in ${FSCK_LOGFILE} if that
  location is writable) but mountall has yet to do this.

  As this would have to be newly implemented, I'd like to request a
  slight change from the Jaunty behavior, and have entries be appended
  to the log files rather than the files being overwritten each time
  with the latest (single) entry. Log rotation on these files may be
  good, too, although I'm not sure which package would/should be
  responsible for that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/513644/+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 1003950] Re: launcher does not show minimized update manager while clicked

[Rick]

The command below reserrects the hidden Software Updater window when
issued. It does not fix the underlying coding issues however it makes it
possibly to continue the update process without killing/quitting -
restarting the app.

sudo apt-get install wmctrl # if necessary
wmctrl -R 'Software Updater'

after issuing the command the window should appear and respond to its
controls as normal.

Hope this help... I take no credit as this is a repeat from one of the
posts higher up in this thread

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

Title:
  launcher does not show minimized update manager while clicked

Status in Compiz:
  New
Status in Accelerated Xorg driver for nVidia cards:
  New
Status in Unity:
  Fix Released
Status in Unity 5.0 series:
  Fix Released
Status in Unity 6.0 series:
  Fix Released
Status in binary-driver-fglrx package in Ubuntu:
  New
Status in intel-linux-graphics-installer package in Ubuntu:
  New
Status in unity package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New
Status in binary-driver-fglrx source package in Precise:
  New
Status in intel-linux-graphics-installer source package in Precise:
  New
Status in unity source package in Precise:
  Fix Released
Status in update-manager source package in Precise:
  Confirmed
Status in xserver-xorg-video-nouveau source package in Precise:
  New
Status in binary-driver-fglrx source package in Quantal:
  Invalid
Status in intel-linux-graphics-installer source package in Quantal:
  Invalid
Status in unity source package in Quantal:
  Fix Released
Status in update-manager source package in Quantal:
  Won't Fix
Status in xserver-xorg-video-nouveau source package in Quantal:
  Invalid

Bug description:
  Found an easy way to reproduce it during brussels sprint:
  1. start deja-dup or update-manager
  2. kill -9 compiz; metacity
  3. compiz --replace

  
  ===

  Update manager is showing up in the dock but I can click on the icon
  all day and nothing happens. Similarly if I do Super-S or Super-W it
  doesn't show up anywhere.

  Even if I alt-tab to the application nothing shows up. This happens
  only when update manager runs on its own. If I kill it and then launch
  it myself it comes to the foreground just fine.

  I'm not 100% sure whether this is a unity, compiz, or update-manager
  bug but so far my bet is on unity.

  =Original Report=
  Bug #877444 is showing again in latest updates, please re-open it. This is 
the exact same problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1003950/+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 987060] Re: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04

[Rick Simmons]

Same issue here. If I close Chrome, CPU on hud-service drops, but memory 
doesn't reclaim.
  PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND 
 3706 ricks 20   0 18.172g 0.017t   2500 R  97.1 55.5 249:42.52 hud-service

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

Title:
  massive memory leak in unity-panel-service and hud-service when
  invoking the hud on Firefox profiles with large amounts of bookmarks
  LTS 12.04 14.04

Status in Unity HUD:
  Confirmed
Status in The Application Menu:
  Confirmed
Status in Unity:
  Won't Fix
Status in firefox package in Ubuntu:
  Confirmed
Status in hud package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Invalid

Bug description:
  unity-panel-service and hud-service quickly racks up memory and CPU
  usage until I kill it when invoking the HUD on Firefox. It's taking
  anywhere from a few minutes to half an hour, but it sometimes makes
  the system completely unusable.

  1. run Firefox 12.0 in the foreground
  2. hit Alt to bring up HUD
  3. type any text
  4. select one proposal from HUD
  5. wait for unity-panel-service and hud-service to fill up the remaining RAM 
and swap space.

  This is due to a high number of bookmarks in a user profile
  (hundreds).

To manage notifications about this bug go to:
https://bugs.launchpad.net/hud/+bug/987060/+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 1394777] Re: dbus daemon running at 100%

[Rick Spencer]

I followed the instructions here - https://wiki.ubuntu.com/DebuggingDBus
to add debugging info to dbus. I was out and experienced the bug. When I
got back I ran sudo dbus-monitor --system for few minutes and collected
the attached output.

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

Title:
  dbus daemon running at 100%

Status in “dbus” package in Ubuntu:
  New

Bug description:
  This is on krillin r166.

  dbus-daemon was running at 100% for a few hours today. I noticed that
  when I launch System Settings, it causes dbus-daemon to run at  lose
  to 100% until it opens. I also noticed that when I launched Systen
  Settings, after it finally opened, dbus-daemon settled down.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1394777/+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 1394777] Re: dbus daemon running at 100%

[Rick Spencer]

** Attachment added: sudo dbus-monitor --system
   
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1394777/+attachment/4265454/+files/dbuslog.txt

** Changed in: dbus (Ubuntu)
 Assignee: (unassigned) = Thomas Voß (thomas-voss)

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

Title:
  dbus daemon running at 100%

Status in “dbus” package in Ubuntu:
  New

Bug description:
  This is on krillin r166.

  dbus-daemon was running at 100% for a few hours today. I noticed that
  when I launch System Settings, it causes dbus-daemon to run at  lose
  to 100% until it opens. I also noticed that when I launched Systen
  Settings, after it finally opened, dbus-daemon settled down.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1394777/+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 1387708] Re: [TOPBLOCKER] Location services not getting location

[Rick Spencer]

** Attachment added: attaching various log files as requested
   
https://bugs.launchpad.net/location-service/+bug/1387708/+attachment/4253842/+files/location-logs.tar.gz

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

Title:
  [TOPBLOCKER] Location services not getting location

Status in Location Service:
  New
Status in “location-service” package in Ubuntu:
  Confirmed
Status in “location-service” package in Ubuntu RTM:
  Confirmed
Status in “location-service” source package in 14.09:
  Confirmed

Bug description:
  Failing to get location fix from application.
  Neither network based nor gps location works.
  Bug has now been seen on 3 phones with and without SIM installed.
  HERE service seems to be running, but no reasonable location is reported.
  GPS is failing to get fix, tested with phone placed for 2 hours outside.

  On two of those phones location was working fine, but with OTA update to ~135 
stopped working.
  hard to guess working image but somewhere around 129~131

  
  Problem is now reproducible on RTM release 137

To manage notifications about this bug go to:
https://bugs.launchpad.net/location-service/+bug/1387708/+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 1387708] Re: [TOPBLOCKER] Location services not getting location

[Rick Spencer]

If I'm seeing this, does that mean I am experiencing the issue on my
phone?

phablet@ubuntu-phablet:~$ sudo cat /userdata/android-data/misc/GPS_CHIP.cfg
[sudo] password for phablet: 
0x6582%s

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

Title:
  [TOPBLOCKER] Location services not getting location

Status in Location Service:
  New
Status in “location-service” package in Ubuntu:
  Confirmed
Status in “location-service” package in Ubuntu RTM:
  Confirmed
Status in “location-service” source package in 14.09:
  Confirmed

Bug description:
  Failing to get location fix from application.
  Neither network based nor gps location works.
  Bug has now been seen on 3 phones with and without SIM installed.
  HERE service seems to be running, but no reasonable location is reported.
  GPS is failing to get fix, tested with phone placed for 2 hours outside.

  On two of those phones location was working fine, but with OTA update to ~135 
stopped working.
  hard to guess working image but somewhere around 129~131

  
  Problem is now reproducible on RTM release 137

To manage notifications about this bug go to:
https://bugs.launchpad.net/location-service/+bug/1387708/+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 1389874] [NEW] Location detection is not working

[Rick Spencer]

Public bug reported:

this is krillin r142

My phone stopped getting location updates.  This does not seem to be bug
#1387708 because my nvram does appear corrupted.

phablet@ubuntu-phablet:/var/log/upstart$ sudo cat 
/var/log/upstart/ubuntu-location-service.log
Attempted to unregister path (path[0] = ril_1 path[1] = null) which isn't 
registered
Attempted to unregister path (path[0] = ril_0 path[1] = null) which isn't 
registered
name - com.ubuntu.espoo.Service.Provider
path - /com/ubuntu/espoo/Service/Provider
Instantiating and configuring: gps::Provider
Instantiating and configuring: remote::Provider
name - com.ubuntu.espoo.Service.Provider
path - /com/ubuntu/espoo/Service/Provider
Instantiating and configuring: gps::Provider
Instantiating and configuring: remote::Provider
Attempted to unregister path (path[0] = ril_1 path[1] = null) which isn't 
registered
Attempted to unregister path (path[0] = ril_0 path[1] = null) which isn't 
registered
name - com.ubuntu.espoo.Service.Provider
path - /com/ubuntu/espoo/Service/Provider
Instantiating and configuring: gps::Provider
Instantiating and configuring: remote::Provider
name - com.ubuntu.espoo.Service.Provider
path - /com/ubuntu/espoo/Service/Provider
Instantiating and configuring: gps::Provider
Instantiating and configuring: remote::Provider
Attempted to unregister path (path[0] = ril_1 path[1] = null) which isn't 
registered
Attempted to unregister path (path[0] = ril_0 path[1] = null) which isn't 
registered
name - com.ubuntu.espoo.Service.Provider
path - /com/ubuntu/espoo/Service/Provider
Instantiating and configuring: gps::Provider
Instantiating and configuring: remote::Provider


phablet@ubuntu-phablet:/var/log/upstart$ sudo cat  
/var/log/upstart/ubuntu-espoo-service.log
[sudo] password for phablet: 
WARNING: Logging before InitGoogleLogging() is written to STDERR
I1105 07:02:02.664535  1666 provider.cpp:122] Successfully started position 
updates.
pure virtual method called
terminate called without an active exception
WARNING: Logging before InitGoogleLogging() is written to STDERR
I1105 08:25:01.957183  1699 provider.cpp:122] Successfully started position 
updates.
I1105 08:32:30.442076  1699 provider.cpp:122] Successfully started position 
updates.
WARNING: Logging before InitGoogleLogging() is written to STDERR
I1105 16:04:37.255589  1713 provider.cpp:122] Successfully started position 
updates.
WARNING: Logging before InitGoogleLogging() is written to STDERR
I1105 16:09:58.814582  1700 provider.cpp:122] Successfully started position 
updates.
WARNING: Logging before InitGoogleLogging() is written to STDERR
I1105 16:29:45.673939  1626 provider.cpp:568] StartPositionUpdates
I1105 16:29:45.678083  1626 provider.cpp:122] Successfully started position 
updates.
I1105 16:29:45.680830  1626 provider.cpp:596] StartVelocityUpdates

** Affects: location-service (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Location detection is not working

Status in “location-service” package in Ubuntu:
  New

Bug description:
  this is krillin r142

  My phone stopped getting location updates.  This does not seem to be
  bug #1387708 because my nvram does appear corrupted.

  phablet@ubuntu-phablet:/var/log/upstart$ sudo cat 
/var/log/upstart/ubuntu-location-service.log
  Attempted to unregister path (path[0] = ril_1 path[1] = null) which isn't 
registered
  Attempted to unregister path (path[0] = ril_0 path[1] = null) which isn't 
registered
name - com.ubuntu.espoo.Service.Provider
path - /com/ubuntu/espoo/Service/Provider
  Instantiating and configuring: gps::Provider
  Instantiating and configuring: remote::Provider
name - com.ubuntu.espoo.Service.Provider
path - /com/ubuntu/espoo/Service/Provider
  Instantiating and configuring: gps::Provider
  Instantiating and configuring: remote::Provider
  Attempted to unregister path (path[0] = ril_1 path[1] = null) which isn't 
registered
  Attempted to unregister path (path[0] = ril_0 path[1] = null) which isn't 
registered
name - com.ubuntu.espoo.Service.Provider
path - /com/ubuntu/espoo/Service/Provider
  Instantiating and configuring: gps::Provider
  Instantiating and configuring: remote::Provider
name - com.ubuntu.espoo.Service.Provider
path - /com/ubuntu/espoo/Service/Provider
  Instantiating and configuring: gps::Provider
  Instantiating and configuring: remote::Provider
  Attempted to unregister path (path[0] = ril_1 path[1] = null) which isn't 
registered
  Attempted to unregister path (path[0] = ril_0 path[1] = null) which isn't 
registered
name - com.ubuntu.espoo.Service.Provider
path - /com/ubuntu/espoo/Service/Provider
  Instantiating and configuring: 

[Touch-packages] [Bug 1374481] Re: Nearby and News scope do not load on reboot

[Rick Spencer]

I just reproduced this on My Photos scope. Starting and not completing a
search caused it to start loading.

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

Title:
  Nearby and News scope do not load on reboot

Status in The Savilerow project:
  Confirmed
Status in QML plugin for Scopes:
  New
Status in “unity-scopes-api” package in Ubuntu:
  Confirmed

Bug description:
  reporduce:
  1- favourite nearby and/or news
  2- reboot the phone
  3 - unlock and swipe to nearby/news

  result:
  Scope is blank, not even departments are loaded in nearby

  expected result:
  scope load, to see what they look like, search for something and then cancel 
search. This triggers a refresh and the scopes then load ok.

To manage notifications about this bug go to:
https://bugs.launchpad.net/savilerow/+bug/1374481/+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 1381041] [NEW] Network indicator is sometimes blank

[Rick Spencer]

Public bug reported:

This is on krillin r103, but it has been happening for a while.

See attached photo. I am not certain what triggers it. but I think it
may happen when wifi APs become in and out of range while walking around
town (as if the list does not refresh reliably).

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


** Tags: avengers

** Attachment added: Screenshot showing blank network indicator
   https://bugs.launchpad.net/bugs/1381041/+attachment/4235692/+files/ni.png

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

Title:
  Network indicator is sometimes blank

Status in “indicator-network” package in Ubuntu:
  New

Bug description:
  This is on krillin r103, but it has been happening for a while.

  See attached photo. I am not certain what triggers it. but I think it
  may happen when wifi APs become in and out of range while walking
  around town (as if the list does not refresh reliably).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1381041/+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 1381069] [NEW] We should hide the player controls in the sound indicator until the music player is fixed to work with them

[Rick Spencer]

Public bug reported:

see these two bugs:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1378048
 https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1361232

Essentially, the music player does not work with the sound menu, and the
fix is involved. Until the default experience works, I suggest that we
do not show these controls.

** Affects: indicator-sound (Ubuntu)
 Importance: Undecided
 Assignee: Thomas Strehl (strehl-t)
 Status: New


** Tags: avengers rtm14

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

Title:
  We should hide the player controls in the sound indicator until the
  music player is fixed to work with them

Status in “indicator-sound” package in Ubuntu:
  New

Bug description:
  see these two bugs:
  https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1378048
   
https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1361232

  Essentially, the music player does not work with the sound menu, and
  the fix is involved. Until the default experience works, I suggest
  that we do not show these controls.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1381069/+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 1381069] Re: We should hide the player controls in the sound indicator until the music player is fixed to work with them

[Rick Spencer]

Setting to Critical on behalf of JoeO

** Changed in: indicator-sound (Ubuntu)
   Importance: Undecided = Critical

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

Title:
  We should hide the player controls in the sound indicator until the
  music player is fixed to work with them

Status in “indicator-sound” package in Ubuntu:
  In Progress

Bug description:
  see these two bugs:
  https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1378048
   
https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1361232

  Essentially, the music player does not work with the sound menu, and
  the fix is involved. Until the default experience works, I suggest
  that we do not show these controls.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1381069/+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 1380120] Re: Manage Scopes - All Is Unusable

[Rick Spencer]

I upgrade to r101 and after reboot could still reproduce the image. In order to 
test ogra's solution:
I ran phablet@ubuntu-phablet:~$ rm -R .cache/QML/*
 and rebooted.  After the reboot, I could no longer reproduce the issue.

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

Title:
  Manage Scopes - All Is Unusable

Status in “unity8” package in Ubuntu:
  Incomplete
Status in “qtdeclarative-opensource-src” package in Ubuntu RTM:
  New

Bug description:
  This only happens when upgraded with deltas:

  $ ubuntu-device-flash --channel=ubuntu-touch/ubuntu-rtm/14.09-proposed 
--revision=96
  and OTA to r100

  Steps:
  1. Got to manage scopes
  2. Click all

  Observed: The UI is unusable as in attached picture

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1380120/+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 1380120] Re: Manage Scopes - All Is Unusable

[Rick Spencer]

** Changed in: unity8 (Ubuntu)
   Status: Incomplete = Invalid

** Changed in: qtdeclarative-opensource-src (Ubuntu RTM)
   Status: New = Confirmed

** Changed in: qtdeclarative-opensource-src (Ubuntu RTM)
   Importance: Undecided = Critical

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

Title:
  Manage Scopes - All Is Unusable

Status in “unity8” package in Ubuntu:
  Invalid
Status in “qtdeclarative-opensource-src” package in Ubuntu RTM:
  Confirmed

Bug description:
  This only happens when upgraded with deltas:

  $ ubuntu-device-flash --channel=ubuntu-touch/ubuntu-rtm/14.09-proposed 
--revision=96
  and OTA to r100

  Steps:
  1. Got to manage scopes
  2. Click all

  Observed: The UI is unusable as in attached picture

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1380120/+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 1380120] [NEW] Manage Scopes - All Is Unusable

[Rick Spencer]

Public bug reported:

This is in krillin r99 rtm-proposed

Steps:
1. Got to manage scopes
2. Click all

Observed: The UI is unusable as in attached picture

** Affects: unity8 (Ubuntu)
 Importance: Critical
 Status: Confirmed


** Tags: avengers rtm14

** Attachment added: broken manage scopes UI
   
https://bugs.launchpad.net/bugs/1380120/+attachment/4231688/+files/manage-scopes.png

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

Title:
  Manage Scopes - All Is Unusable

Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  This is in krillin r99 rtm-proposed

  Steps:
  1. Got to manage scopes
  2. Click all

  Observed: The UI is unusable as in attached picture

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1380120/+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 1380120] Re: Manage Scopes - All Is Unusable

[Rick Spencer]

** Summary changed:

- Manage Scopes - Is Unusable
+ Manage Scopes - All Is Unusable

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

Title:
  Manage Scopes - All Is Unusable

Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  This is in krillin r99 rtm-proposed

  Steps:
  1. Got to manage scopes
  2. Click all

  Observed: The UI is unusable as in attached picture

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1380120/+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 1380120] Re: Manage Scopes - All Is Unusable

[Rick Spencer]

I have done a lot of favoriting and unfavoritng of scopes. That's the
only thing that I can think of that would be at all relevant.

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

Title:
  Manage Scopes - All Is Unusable

Status in “unity8” package in Ubuntu:
  Incomplete

Bug description:
  This is in krillin r99 rtm-proposed

  Steps:
  1. Got to manage scopes
  2. Click all

  Observed: The UI is unusable as in attached picture

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1380120/+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 1378958] Re: music scope showing mini music scope on activation of artist and anything on video scope

[Rick Spencer]

= after upgrade =
1. use the power button to blank the screen
2. use the power button to turn on the screen
3. swipe away the welcome screen to the left
4. enter pin code
5. put finger in center of screen on app scope and swipe to the left
6. wait for video scope to finish (note that no videos are visible, it only 
says My Videos 
7. Click My Videos
8. mini-scope appears for local videos 
9. click on home button to return to apps scope
10. with finger in middel of apps scope, scroll over to Video scope
11. click settings button
12. enable Dislay results from Youtube
13. Click back chevron
14. click star to unfavorite, the music scope (which was the next scope to 
right) slides in
15. click star to unfavorite music scope, My photos slides in
16. flick from the bottom to bring up manage dash
17. click all
18. Click My Music
19. click on an arist (note that artists are now arragned in a grid insteda of 
in cover flow
20. click back 
21. click the start to favorite
22. click the home button, the whole dash dissapears and then reappears after 
some time ( I assume the dash crashed)
22.use your fingers to move over the music scope, now the third one, it behaves 
normally

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

Title:
  music scope showing mini music scope on activation of artist and
  anything on video scope

Status in “unity-scope-mediascanner” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  Steps:
  1. Have music on your phone
  2. Go to the music scope
  3. Click on an artist

  Expected:
  You get the normal list

  Observed:
  You get a little mini music scope inside the scope (see attached image)

  
  This is on krillin rtm r91

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1378958/+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 1378958] [NEW] music scope showing mini music scope on activation of artist

[Rick Spencer]

Public bug reported:

Steps:
1. Have music on your phone
2. Go to the music scope
3. Click on an artist

Expected:
You get the normal list

Observed:
You get a little mini music scope inside the scope (see attached image)

** Affects: unity-scope-mediascanner (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: avengers

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

Title:
  music scope showing mini music scope on activation of artist

Status in “unity-scope-mediascanner” package in Ubuntu:
  New

Bug description:
  Steps:
  1. Have music on your phone
  2. Go to the music scope
  3. Click on an artist

  Expected:
  You get the normal list

  Observed:
  You get a little mini music scope inside the scope (see attached image)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1378958/+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 1378958] Re: music scope showing mini music scope on activation of artist

[Rick Spencer]

** Attachment added: mini-scope.png
   
https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1378958/+attachment/4228745/+files/mini-scope.png

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

Title:
  music scope showing mini music scope on activation of artist

Status in “unity-scope-mediascanner” package in Ubuntu:
  New

Bug description:
  Steps:
  1. Have music on your phone
  2. Go to the music scope
  3. Click on an artist

  Expected:
  You get the normal list

  Observed:
  You get a little mini music scope inside the scope (see attached image)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1378958/+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 1378958] Re: music scope showing mini music scope on activation of artist

[Rick Spencer]

** Description changed:

  Steps:
  1. Have music on your phone
  2. Go to the music scope
  3. Click on an artist
  
  Expected:
  You get the normal list
  
  Observed:
  You get a little mini music scope inside the scope (see attached image)
+ 
+ 
+ This is on krillin rtm r91

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

Title:
  music scope showing mini music scope on activation of artist

Status in “unity-scope-mediascanner” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  Steps:
  1. Have music on your phone
  2. Go to the music scope
  3. Click on an artist

  Expected:
  You get the normal list

  Observed:
  You get a little mini music scope inside the scope (see attached image)

  
  This is on krillin rtm r91

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1378958/+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 1378958] Re: music scope showing mini music scope on activation of artist and anything on video scope

[Rick Spencer]

I  just realized that on the video scope, I only have local content
displayed (no youtube). So the scope appears blank. When I click on My
Videos I get a mini scope for videos. See attached.

** Attachment added: screenshot of mini videos
   
https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1378958/+attachment/4228822/+files/mini-videos.png

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

Title:
  music scope showing mini music scope on activation of artist and
  anything on video scope

Status in “unity-scope-mediascanner” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  Steps:
  1. Have music on your phone
  2. Go to the music scope
  3. Click on an artist

  Expected:
  You get the normal list

  Observed:
  You get a little mini music scope inside the scope (see attached image)

  
  This is on krillin rtm r91

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1378958/+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 1378958] Re: music scope showing mini music scope on activation of artist and anything on video scope

[Rick Spencer]

I  just realized that on the video scope, I only have local content
displayed (no youtube). So the scope appears blank. When I click on My
Videos I get a mini scope for videos. See attached.

** Summary changed:

- music scope showing mini music scope on activation of artist
+ music scope showing mini music scope on activation of artist and anything on 
video scope

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

Title:
  music scope showing mini music scope on activation of artist and
  anything on video scope

Status in “unity-scope-mediascanner” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  Steps:
  1. Have music on your phone
  2. Go to the music scope
  3. Click on an artist

  Expected:
  You get the normal list

  Observed:
  You get a little mini music scope inside the scope (see attached image)

  
  This is on krillin rtm r91

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1378958/+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 1378958] Re: music scope showing mini music scope on activation of artist and anything on video scope

[Rick Spencer]

A little more info after a chat with cimi

1.  most of my content is on my SD card, and there ias a lot of it, about 30 
gigs. 
2. I have favorited and unfavorited both  the music and video scope many times
3. this is in the My Music and My Video scopes

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

Title:
  music scope showing mini music scope on activation of artist and
  anything on video scope

Status in “unity-scope-mediascanner” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  Steps:
  1. Have music on your phone
  2. Go to the music scope
  3. Click on an artist

  Expected:
  You get the normal list

  Observed:
  You get a little mini music scope inside the scope (see attached image)

  
  This is on krillin rtm r91

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1378958/+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 1378958] Re: music scope showing mini music scope on activation of artist and anything on video scope

[Rick Spencer]

I enabled the online sources and those work normally. So this is only
the My Music and My Video scopes.

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

Title:
  music scope showing mini music scope on activation of artist and
  anything on video scope

Status in “unity-scope-mediascanner” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  Steps:
  1. Have music on your phone
  2. Go to the music scope
  3. Click on an artist

  Expected:
  You get the normal list

  Observed:
  You get a little mini music scope inside the scope (see attached image)

  
  This is on krillin rtm r91

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1378958/+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 1378044] [NEW] No Album art on Audio Controls

[Rick Spencer]

Public bug reported:

Steps:
1. have music on your phone
2. Make sure that album art appears in the music scope
3. Play the album in the music player
4. Click the power button to blank the screen
5. turn on the power button button
6. pull down the sound indicator

Observed: there is no album art in the indicator, the window is blank
Expected:  there is album art

** Affects: indicator-sound (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: avengers

** Description changed:

  Steps:
  1. have music on your phone
- 2. Make sure that album art appears in the mysic scope
+ 2. Make sure that album art appears in the music scope
  3. Play the album in the music player
  4. Click the power button to blank the screen
  5. turn on the power button button
  6. pull down the sound indicator
  
  Observed: there is no album art in the indicator, the window is blank
  Expected:  there is album art

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

Title:
  No Album art on Audio Controls

Status in “indicator-sound” package in Ubuntu:
  New

Bug description:
  Steps:
  1. have music on your phone
  2. Make sure that album art appears in the music scope
  3. Play the album in the music player
  4. Click the power button to blank the screen
  5. turn on the power button button
  6. pull down the sound indicator

  Observed: there is no album art in the indicator, the window is blank
  Expected:  there is album art

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1378044/+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] [NEW] Forward button does not work

[Rick Spencer]

Public bug reported:

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

** Affects: indicator-sound (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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:
  Forward button does not work

Status in “indicator-sound” package in Ubuntu:
  New

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/ubuntu/+source/indicator-sound/+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 1378103] [NEW] Indicator does not display message and there is no notification when screen is locked and message is in messaging app

[Rick Spencer]

Public bug reported:

Steps:
I used skype for this to make it easy to repro

0. Set your phone by opening the messaging app to a thread for a conversation 
that you are not about to test then use the power button to blank the screen
1. Open skype you on your desktop
2. Use skype to send a text to your phone
3. Wait a few seconds for the alert
4. Click on the notification to open it as a conversation in the messaging app
5. use the power button to blank your screen again
6. use skype to send another text

Result:
The alert sounds plays, and the screen turns on, but there is no notification 
and the message is not in the messaging menu. If you unlock the phone you see 
the message in the conversation.

Expected:
The notification shows and the message is in the indicator.

This is krillin, r84

** Affects: indicator-messages (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: avengers

** Summary changed:

- Indicator does not display message when screen is locked and message is in 
messaging app
+ Indicator does not display message and there is no notification when screen 
is locked and message is in messaging app

** Description changed:

  Steps:
  I used skype for this to make it easy to repro
  
  0. Set your phone by opening the messaging app to a thread for a conversation 
that you are not about to test then use the power button to blank the screen
  1. Open skype you on your desktop
  2. Use skype to send a text to your phone
  3. Wait a few seconds for the alert
  4. Click on the notification to open it as a conversation in the messaging app
  5. use the power button to blank your screen again
  6. use skype to send another text
  
  Result:
  The alert sounds plays, and the screen turns on, but there is no notification 
and the message is not in the messaging menu. If you unlock the phone you see 
the message in the conversation.
  
  Expected:
  The notification shows and the message is in the indicator.
+ 
+ This is krillin, r84

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

Title:
  Indicator does not display message and there is no notification when
  screen is locked and message is in messaging app

Status in “indicator-messages” package in Ubuntu:
  New

Bug description:
  Steps:
  I used skype for this to make it easy to repro

  0. Set your phone by opening the messaging app to a thread for a conversation 
that you are not about to test then use the power button to blank the screen
  1. Open skype you on your desktop
  2. Use skype to send a text to your phone
  3. Wait a few seconds for the alert
  4. Click on the notification to open it as a conversation in the messaging app
  5. use the power button to blank your screen again
  6. use skype to send another text

  Result:
  The alert sounds plays, and the screen turns on, but there is no notification 
and the message is not in the messaging menu. If you unlock the phone you see 
the message in the conversation.

  Expected:
  The notification shows and the message is in the indicator.

  This is krillin, r84

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1378103/+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 1338430] Re: Slow loading/showing of images in the dash

[Rick Spencer]

This does not happen to me only after reboot. When I scroll up and down
in the apps scope there is a delay in loading icons.

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

Title:
  Slow loading/showing of images in the dash

Status in “unity8” package in Ubuntu:
  In Progress

Bug description:
  Installed app icons (when expanding the category) show very slowly
  after reboot. It actually makes the impression that those are being
  downloaded.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1338430/+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 1369644] [NEW] Should be possible to take a screen shot on the phone from the phone itself

[Rick Spencer]

Public bug reported:

Currently, the only way to take a screenshot is to attach the phone to a
computer via USB and use phablet-screenshot.

There should be a way to take a screenshot from the phone. Otherwise, it
will be hard for people to share how great their phone is on social
media, as well as other functions.

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


** Tags: avengers

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

Title:
  Should be possible to take a screen shot on the phone from the phone
  itself

Status in “mir” package in Ubuntu:
  New

Bug description:
  Currently, the only way to take a screenshot is to attach the phone to
  a computer via USB and use phablet-screenshot.

  There should be a way to take a screenshot from the phone. Otherwise,
  it will be hard for people to share how great their phone is on social
  media, as well as other functions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1369644/+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 1367341] [NEW] proximity sensor blanks screen when dialer is not active app

[Rick Spencer]

Public bug reported:

Steps:
1. Make a phone call with BT so that you are not holding the phone to hear and 
talk
2. Push the power button to blank the screen
3. Push the power button again, observe that you are at the welcome screen
4. Wave a finger over the proximity sensor

Effect:
The screen blanks while finger is over the sensor

Expected:
The sensor only blanks the screen while the dialer app is being used

this is kirllin r23

** Affects: dialer-app (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: avengers

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

Title:
  proximity sensor blanks screen when dialer is not active app

Status in “dialer-app” package in Ubuntu:
  New

Bug description:
  Steps:
  1. Make a phone call with BT so that you are not holding the phone to hear 
and talk
  2. Push the power button to blank the screen
  3. Push the power button again, observe that you are at the welcome screen
  4. Wave a finger over the proximity sensor

  Effect:
  The screen blanks while finger is over the sensor

  Expected:
  The sensor only blanks the screen while the dialer app is being used

  this is kirllin r23

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1367341/+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 1362307] [NEW] Tapping on an SMS does not open the messaging app

[Rick Spencer]

Public bug reported:

Steps:

1. Receive an SMS
2. Pull down the indicator
3. Click on the message in the indicator

Effect:
Nothing happens

Expected:
The messaging app opens to the message

this is krillin r9 (on rtm branch)

** Affects: indicator-messages (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: avengers

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

Title:
  Tapping on an SMS does not open the messaging app

Status in “indicator-messages” package in Ubuntu:
  New

Bug description:
  Steps:

  1. Receive an SMS
  2. Pull down the indicator
  3. Click on the message in the indicator

  Effect:
  Nothing happens

  Expected:
  The messaging app opens to the message

  this is krillin r9 (on rtm branch)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1362307/+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 1361181] [NEW] dragging files in nautilus onto an SD card does not work

[Rick Spencer]

Public bug reported:

Steps:

1. Have an sd card into the phone
2. Plug the phone into your ubuntu desktop (I am on Utopic)
3. Note that the sd card is not visible under the krillin folder in nautilus
4. Drag some video files over

Result:
There was an error copying the file into mtp://[usb:002,010]/BEB5-7A9F.
libmtp error:  Could not send object info.

Expected:
The files are copied over


This is on krillin r207

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

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

Title:
  dragging files in nautilus onto an SD card does not work

Status in “mtp” package in Ubuntu:
  New

Bug description:
  Steps:

  1. Have an sd card into the phone
  2. Plug the phone into your ubuntu desktop (I am on Utopic)
  3. Note that the sd card is not visible under the krillin folder in nautilus
  4. Drag some video files over

  Result:
  There was an error copying the file into mtp://[usb:002,010]/BEB5-7A9F.
  libmtp error:  Could not send object info.

  Expected:
  The files are copied over

  
  This is on krillin r207

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1361181/+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 1361227] [NEW] Artist artwork does not fit in space in artist details

[Rick Spencer]

Public bug reported:

See screen shot

** Affects: unity-scope-mediascanner (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: avengers

** Attachment added: fit.png
   https://bugs.launchpad.net/bugs/1361227/+attachment/4186704/+files/fit.png

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

Title:
  Artist artwork does not fit in space in artist details

Status in “unity-scope-mediascanner” package in Ubuntu:
  New

Bug description:
  See screen shot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1361227/+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 1361232] Re: No album artist artwork for local music on music scope

[Rick Spencer]

** Attachment added: noart.png
   
https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1361232/+attachment/4186706/+files/noart.png

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

Title:
  No album artist artwork for local music on music scope

Status in “unity-scope-mediascanner” package in Ubuntu:
  New

Bug description:
  See attached screenshot. This is from music on an SD card.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1361232/+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 1361232] [NEW] No album artist artwork for local music on music scope

[Rick Spencer]

Public bug reported:

See attached screenshot. This is from music on an SD card.

** Affects: unity-scope-mediascanner (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  No album artist artwork for local music on music scope

Status in “unity-scope-mediascanner” package in Ubuntu:
  New

Bug description:
  See attached screenshot. This is from music on an SD card.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1361232/+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 1361229] [NEW] Art work for album details is grainy

[Rick Spencer]

Public bug reported:

See attached screenshot.

Note also that there is album art in the directory with the music, it
does not appear that that is being used.

This is on krillin r207

** Affects: unity-scope-mediascanner (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: grainy.png
   https://bugs.launchpad.net/bugs/1361229/+attachment/4186705/+files/grainy.png

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

Title:
  Art work for album details is grainy

Status in “unity-scope-mediascanner” package in Ubuntu:
  New

Bug description:
  See attached screenshot.

  Note also that there is album art in the directory with the music, it
  does not appear that that is being used.

  This is on krillin r207

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1361229/+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 1361234] [NEW] When not logged in, users should be navigated directly to Ubuntu One account page

[Rick Spencer]

Public bug reported:

1. Be not logged into Ubuntu SSO
2. Go the Ubuntu store in the dash and search for something
3. click on the app to get to app details
4. Click Install
5. You will end up with Login Error and Go to Accounts button
6. click Go to Accounts

Results:
You are presented with a list of possible accounts to sign into, but only 
Ubuntu One will work

Expected:
You go directly to the Ubuntu One sign in page

** Affects: unity-scope-click (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: avengers

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

Title:
  When not logged in, users should be navigated directly to Ubuntu One
  account page

Status in “unity-scope-click” package in Ubuntu:
  New

Bug description:
  1. Be not logged into Ubuntu SSO
  2. Go the Ubuntu store in the dash and search for something
  3. click on the app to get to app details
  4. Click Install
  5. You will end up with Login Error and Go to Accounts button
  6. click Go to Accounts

  Results:
  You are presented with a list of possible accounts to sign into, but only 
Ubuntu One will work

  Expected:
  You go directly to the Ubuntu One sign in page

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1361234/+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 1023734] Re: [GA-78LMT-S2P, Realtek ALC887-VD, Green Headphone Out, Front] No sound at all

[Rick NIcoletti]

Same problem here.  Any luck with this?

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

Title:
  [GA-78LMT-S2P, Realtek ALC887-VD, Green Headphone Out, Front] No sound
  at all

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  New install on new hardware, only a few days old. Have never heard any
  sound on it at all. :(

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
  Uname: Linux 3.2.0-26-generic x86_64
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snail 16741 F pulseaudio
   /dev/snd/controlC0:  snail 16741 F pulseaudio
   /dev/snd/pcmC0D0p:   snail 16741 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16'
     Mixer name : 'Realtek ALC887-VD'
     Components : 'HDA:10ec0887,1458a002,00100302'
     Controls  : 39
     Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'Generic'/'HD-Audio Generic at 0xfdffc000 irq 42'
     Mixer name : 'ATI R6xx HDMI'
     Components : 'HDA:1002aa01,00aa0100,00100200'
     Controls  : 6
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined penum
     Playback channels: Mono
     Mono: Playback [on]
  Date: Wed Jul 11 22:47:41 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed
  Symptom_Card: Built-in Audio - HDA ATI SB
  Symptom_DevicesInUse:
   16741 16741 16741  snail F pulseaudio
   /dev/snd/controlC0:  snail F pulseaudio
   /dev/snd/pcmC0D0p:   snail F...m pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [GA-78LMT-S2P, Realtek ALC887-VD, Green Headphone Out, Front] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/20/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-S2P
  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:bd03/20/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-S2P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1023734/+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 1359846] [NEW] unity8 crashed with SIGABRT in raise()

[Rick Spencer]

Public bug reported:

recent crash

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: unity8 8.00+14.10.20140817-0ubuntu1
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.14.6-0ubuntu2
Architecture: armhf
CurrentDesktop: Unity
Date: Thu Aug 21 12:11:36 2014
ExecutablePath: /usr/bin/unity8
InstallationDate: Installed on 2014-08-20 (1 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140820-020204)
ProcCmdline: unity8
Signal: 6
SourcePackage: unity8
StacktraceTop:
 ?? () from /lib/arm-linux-gnueabihf/libc.so.6
 raise () from /lib/arm-linux-gnueabihf/libc.so.6
 abort () from /lib/arm-linux-gnueabihf/libc.so.6
 __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/arm-linux-gnueabihf/libstdc++.so.6
 ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
Title: unity8 crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip plugdev sudo tty video

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


** Tags: apport-crash armhf local-libs need-armhf-retrace utopic

** Information type changed from Private to Public

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

Title:
  unity8 crashed with SIGABRT in raise()

Status in “unity8” package in Ubuntu:
  New

Bug description:
  recent crash

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: unity8 8.00+14.10.20140817-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: armhf
  CurrentDesktop: Unity
  Date: Thu Aug 21 12:11:36 2014
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2014-08-20 (1 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140820-020204)
  ProcCmdline: unity8
  Signal: 6
  SourcePackage: unity8
  StacktraceTop:
   ?? () from /lib/arm-linux-gnueabihf/libc.so.6
   raise () from /lib/arm-linux-gnueabihf/libc.so.6
   abort () from /lib/arm-linux-gnueabihf/libc.so.6
   __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/arm-linux-gnueabihf/libstdc++.so.6
   ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  Title: unity8 crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip plugdev sudo tty video

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1359846/+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 1359856] [NEW] unity-system-compositor crashed with SIGSEGV

[Rick Spencer]

Public bug reported:

the other crash

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: unity-system-compositor 0.0.5+14.10.20140814-0ubuntu1
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.14.6-0ubuntu2
Architecture: armhf
Date: Thu Aug 21 12:11:23 2014
Disassembly: = 0xb464a00c: Cannot access memory at address 0xb464a00c
ExecutablePath: /usr/sbin/unity-system-compositor
ExecutableTimestamp: 1408047202
InstallationDate: Installed on 2014-08-20 (1 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140820-020204)
ProcCmdline: unity-system-compositor --disable-overlays=false 
--spinner=/usr/bin/unity-system-compositor-spinner --file /run/mir_socket 
--from-dm-fd 10 --to-dm-fd 13 --vt 1
ProcCwd: /
ProcEnviron:
 
SegvAnalysis: Skipped: missing required field Disassembly
Signal: 11
SourcePackage: unity-system-compositor
Stacktrace:
 #0  0xb464a00c in ?? ()
 No symbol table info available.
 #1  0xb464557c in ?? ()
 No symbol table info available.
 Backtrace stopped: previous frame identical to this frame (corrupt stack?)
StacktraceTop:
 ?? ()
 ?? ()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

** Affects: unity-system-compositor (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-crash armhf need-armhf-retrace utopic

** Information type changed from Private to Public

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

Title:
  unity-system-compositor crashed with SIGSEGV

Status in “unity-system-compositor” package in Ubuntu:
  New

Bug description:
  the other crash

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: unity-system-compositor 0.0.5+14.10.20140814-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: armhf
  Date: Thu Aug 21 12:11:23 2014
  Disassembly: = 0xb464a00c:   Cannot access memory at address 0xb464a00c
  ExecutablePath: /usr/sbin/unity-system-compositor
  ExecutableTimestamp: 1408047202
  InstallationDate: Installed on 2014-08-20 (1 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140820-020204)
  ProcCmdline: unity-system-compositor --disable-overlays=false 
--spinner=/usr/bin/unity-system-compositor-spinner --file /run/mir_socket 
--from-dm-fd 10 --to-dm-fd 13 --vt 1
  ProcCwd: /
  ProcEnviron:
   
  SegvAnalysis: Skipped: missing required field Disassembly
  Signal: 11
  SourcePackage: unity-system-compositor
  Stacktrace:
   #0  0xb464a00c in ?? ()
   No symbol table info available.
   #1  0xb464557c in ?? ()
   No symbol table info available.
   Backtrace stopped: previous frame identical to this frame (corrupt stack?)
  StacktraceTop:
   ?? ()
   ?? ()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1359856/+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 1359856] Re: unity-system-compositor crashed with SIGSEGV

[Rick Spencer]

** Attachment added: last_kmsg
   
https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1359856/+attachment/4183750/+files/last_kmsg

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

Title:
  unity-system-compositor crashed with SIGSEGV

Status in “unity-system-compositor” package in Ubuntu:
  New

Bug description:
  the other crash

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: unity-system-compositor 0.0.5+14.10.20140814-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: armhf
  Date: Thu Aug 21 12:11:23 2014
  Disassembly: = 0xb464a00c:   Cannot access memory at address 0xb464a00c
  ExecutablePath: /usr/sbin/unity-system-compositor
  ExecutableTimestamp: 1408047202
  InstallationDate: Installed on 2014-08-20 (1 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140820-020204)
  ProcCmdline: unity-system-compositor --disable-overlays=false 
--spinner=/usr/bin/unity-system-compositor-spinner --file /run/mir_socket 
--from-dm-fd 10 --to-dm-fd 13 --vt 1
  ProcCwd: /
  ProcEnviron:
   
  SegvAnalysis: Skipped: missing required field Disassembly
  Signal: 11
  SourcePackage: unity-system-compositor
  Stacktrace:
   #0  0xb464a00c in ?? ()
   No symbol table info available.
   #1  0xb464557c in ?? ()
   No symbol table info available.
   Backtrace stopped: previous frame identical to this frame (corrupt stack?)
  StacktraceTop:
   ?? ()
   ?? ()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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