[Touch-packages] [Bug 2055776] Re: After updating ubuntu, the network to which the subnet address is assigned does not become active in KVM.

[Joe Blow]

Adding  the lines:

  listen-on port 53 { localhost; 192.168.122.0/24; };
  allow-query { localhost; 192.168.122.0/24; };

to /etc/bind/named.conf.options helped

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

Title:
  After updating ubuntu, the network to which the subnet address is
  assigned does not become active in KVM.

Status in dnsmasq package in Ubuntu:
  Invalid

Bug description:
  phenomenon:
After updating ubuntu, the network to which the subnet address is assigned 
does not become active in KVM.

  Cause:
This is because the following dnsmasq update operation performed by apt's 
automatic update causes an error. It worked properly with dnsmasq 2.80, but 
does not work properly with 2.90.

  $ cat /var/log/apt/history.log
  (snip)
  Start-Date: 2024-02-27  06:17:31
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: dnsmasq-base:amd64 (2.80-1.1ubuntu1.7, 2.90-0ubuntu0.20.04.1)
  End-Date: 2024-02-27  06:17:44
  (snip)
  $

  Cause details:
As a premise, bind-dynamic is set in the dnsmasq config file for KVM. Below 
is an example.

  $ cat default.conf 
  ##WARNING:  THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE
  ##OVERWRITTEN AND LOST.  Changes to this configuration should be made using:
  ##virsh net-edit default
  ## or other application using the libvirt API.
  ##
  ## dnsmasq conf file created by libvirt
  strict-order
  user=libvirt-dnsmasq
  pid-file=/run/libvirt/network/default.pid
  except-interface=lo
  bind-dynamic
  interface=virbr0
  dhcp-range=192.168.122.2,192.168.122.254,255.255.255.0
  dhcp-no-override
  dhcp-authoritative
  dhcp-lease-max=253
  dhcp-hostsfile=/var/lib/libvirt/dnsmasq/default.hostsfile
  addn-hosts=/var/lib/libvirt/dnsmasq/default.addnhosts
  $ 

  
  When starting the network with KVM (virsh net-start), dnsmasq started from 
KVM executes the make_sock function twice as shown below.

 $ cat network.c
 (snip)
 1087 static struct listener *create_listeners(union mysockaddr *addr, int 
do_
 1087 tftp, int dienow)
 1088 {
 1089   struct listener *l = NULL;
 1090   int fd = -1, tcpfd = -1, tftpfd = -1;
 1091 
 1092   (void)do_tftp;
 1093 
 1094   if (daemon->port != 0)
 1095 {
 1096   fd = make_sock(addr, SOCK_DGRAM, dienow);
 1097   tcpfd = make_sock(addr, SOCK_STREAM, dienow);
 1098 }
 (snip)

  The following code causes an issue with the update made in dnsmasq
  2.90.

 $ cat network.c
 (snip)
  895 static int make_sock(union mysockaddr *addr, int type, int dienow)
  896 {
  (snip)
  934   if (!option_bool(OPT_CLEVERBIND) || errno != EADDRNOTAVAIL)
  935 {
  936   if (dienow)
  937 die(s, daemon->addrbuff, EC_BADNET);
  938   else
  939 my_syslog(LOG_WARNING, s, daemon->addrbuff, 
strerror(errno))939 ;
  940 }
  (snip)

  
  function "make_sock" in network.c:1096 binds the socket to 192.168.122.1/24, 
and then make_sock in network.c:1097 tries to bind to the same address. 
However, in network.c:934, when errno==98 occurs, network.c:937 is executed, so 
dnsmasq does not cause a startup error. As a result, virsh net-start fails.

  As a temporary workaround, it will work if you try not to die.

  $ diff -u  network_c_back  network.c 
  --- network_c_back  2024-02-29 15:36:05.156467935 +
  +++ network.c 2024-02-29 15:36:38.733324350 +
  @@ -934,7 +934,8 @@
 if (!option_bool(OPT_CLEVERBIND) || errno != EADDRNOTAVAIL)
{
  if (dienow)
  - die(s, daemon->addrbuff, EC_BADNET);
  + my_syslog(LOG_WARNING, s, daemon->addrbuff, strerror(errno));
  + //die(s, daemon->addrbuff, EC_BADNET);
  else
my_syslog(LOG_WARNING, s, daemon->addrbuff, strerror(errno));
}
  $ 

  If bind-dynamic is set, it should be modified so that it works even if
  errno==98.

  For reference, in the case of dnsmasq 2.80, the code is as follows, so
  no error occurs.

  network.c
  699 static int make_sock(union mysockaddr *addr, int type, int dienow)
  700 {
  701   int family = addr->sa.sa_family;
  702   int fd, rc, opt = 1;
  (snip)
  715 err:
  716   errsave = errno;
  717   port = prettyprint_addr(addr, daemon->addrbuff);
  718   if (!option_bool(OPT_NOWILD) && !option_bool(OPT_CLEVERBIND))
  719 sprintf(daemon->addrbuff, "port %d", port);
  720   s = _("failed to create listening socket for %s: %s");
  721   
  722   if (fd != -1)
  723 close (fd);
  724 
  725   errno = errsave;
  726 
  727   if (dienow)
  728 {
  729   /* failure to bind addresses given by --listen-address at 
this
  729  point
  730  is 

[Touch-packages] [Bug 2054481] [NEW] Move "enhanced tiling" into Keyboard settings

[Joe-xenotropic]

Public bug reported:

Starting in 23.10, Ubuntu introduced "enhanced tiling", which modifies
the default behavior for Super+Right  so that it does not only moves the
window over to one side, but it also brings up a task-switcher for the
remaining space.

I wanted to turn this off, but did not know what it was called or what
program/library etc. was causing it. It was a change to the behavior of
a keyboard shortcut, so I went to "keyboard shortcuts". There it still
says Super+Right is "view split on right". This not accurate anymore, as
that is only half of what Super+Right does with Enhanced Tiling on.

I had to do like 15 different Google searches before finding this Ask
Ubuntu question

https://askubuntu.com/questions/1494628/how-can-i-disable-the-new-
superarrow-window-screen-aligning-feature

which finally relieved my confusion, told me the name of the behavior,
and allowed me to turn it off in the unexpected "Ubuntu Desktop"
location.

Please somehow make it clear from the keyboard settings that "enhanced
tiling" exists, since it does modify keyboard behavior to be other than
what keyboard settings says it is. You could do this by:

- having "View Split On Left" and "Enhanced Tiling To Left" be two separate 
actions, and Super+left/right could be assigned to one or the other
- somehow indicate the existence of Enhanced Tiling in the description of the 
keyboard action, like "View Split on left (see also Enhanced Tiling)" would 
have at least let me know I needed to search for an "Enhanced Tiling" setting

See also related bug I filed for documenting Enhanced Tiling as part of
keyboard shortcuts in ubuntu-docs
https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/2054478

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

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

Title:
  Move "enhanced tiling" into Keyboard settings

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  Starting in 23.10, Ubuntu introduced "enhanced tiling", which modifies
  the default behavior for Super+Right  so that it does not only moves
  the window over to one side, but it also brings up a task-switcher for
  the remaining space.

  I wanted to turn this off, but did not know what it was called or what
  program/library etc. was causing it. It was a change to the behavior
  of a keyboard shortcut, so I went to "keyboard shortcuts". There it
  still says Super+Right is "view split on right". This not accurate
  anymore, as that is only half of what Super+Right does with Enhanced
  Tiling on.

  I had to do like 15 different Google searches before finding this Ask
  Ubuntu question

  https://askubuntu.com/questions/1494628/how-can-i-disable-the-new-
  superarrow-window-screen-aligning-feature

  which finally relieved my confusion, told me the name of the behavior,
  and allowed me to turn it off in the unexpected "Ubuntu Desktop"
  location.

  Please somehow make it clear from the keyboard settings that "enhanced
  tiling" exists, since it does modify keyboard behavior to be other
  than what keyboard settings says it is. You could do this by:

  - having "View Split On Left" and "Enhanced Tiling To Left" be two separate 
actions, and Super+left/right could be assigned to one or the other
  - somehow indicate the existence of Enhanced Tiling in the description of the 
keyboard action, like "View Split on left (see also Enhanced Tiling)" would 
have at least let me know I needed to search for an "Enhanced Tiling" setting

  See also related bug I filed for documenting Enhanced Tiling as part
  of keyboard shortcuts in ubuntu-docs
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/2054478

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


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

[Touch-packages] [Bug 2048076] [NEW] Screen crashes in a wierd way

[Sahaya Joe Ralphin X]

ENIED" 
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=1945 
comm="snap-confine" capability=38  capname="perfmon"
[   21.245177] overlayfs: fs on 
'/home/joe/.local/share/docker/overlay2/check-overlayfs-support3971078866/lower2'
 does not support file handles, falling back to xino=off.
[   21.256807] evict_inodes inode 867da6a8, i_count = 1, was skipped!
[   21.256815] evict_inodes inode f8db770e, i_count = 1, was skipped!
[   21.256819] evict_inodes inode 5765f53f, i_count = 1, was skipped!
[   21.256822] evict_inodes inode 5458467f, i_count = 1, was skipped!
[   21.256825] evict_inodes inode 949894ec, i_count = 1, was skipped!
[   21.258540] overlayfs: fs on 
'/home/joe/.local/share/docker/overlay2/metacopy-check1382144368/l1' does not 
support file handles, falling back to xino=off.
[   21.260005] evict_inodes inode 2dc61da9, i_count = 1, was skipped!
[   21.260012] evict_inodes inode 636c7c00, i_count = 1, was skipped!
[   21.260015] evict_inodes inode 0b73d191, i_count = 1, was skipped!
[   21.260018] evict_inodes inode d8b7d0c2, i_count = 1, was skipped!
[   21.309738] rfkill: input handler enabled
[   23.079841] rfkill: input handler disabled
[   23.985541] audit: type=1400 audit(1704364434.996:128): apparmor="DENIED" 
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=2883 
comm="snap-confine" capability=12  capname="net_admin"
[   23.985565] audit: type=1400 audit(1704364434.996:129): apparmor="DENIED" 
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=2883 
comm="snap-confine" capability=38  capname="perfmon"
[   33.140391] usb 3-2.2: device descriptor read/64, error -110
[   33.328357] usb 3-2.2: new full-speed USB device number 5 using xhci_hcd
[   46.849948] warning: `ThreadPoolForeg' uses wireless extensions which will 
stop working for Wi-Fi 7 hardware; use nl80211
[   48.905109] usb 3-2.2: device descriptor read/64, error -110
[   64.564094] usb 3-2.2: device descriptor read/64, error -110
[   64.676424] usb 3-2-port2: attempt power cycle
[   65.292593] usb 3-2.2: new full-speed USB device number 6 using xhci_hcd
[   70.366477] xhci_hcd :03:00.4: Timeout while waiting for setup device 
command
[   75.732213] xhci_hcd :03:00.4: Timeout while waiting for setup device 
command
[   75.940022] usb 3-2.2: device not accepting address 6, error -62
[   76.019765] usb 3-2.2: new full-speed USB device number 7 using xhci_hcd
[   81.100524] xhci_hcd :03:00.4: Timeout while waiting for setup device 
command
[   86.470729] xhci_hcd :03:00.4: Timeout while waiting for setup device 
command
[   86.678505] usb 3-2.2: device not accepting address 7, error -62
[   86.678760] usb 3-2-port2: unable to enumerate USB device
[  988.648266] usb 3-2.2: new full-speed USB device number 8 using xhci_hcd
[ 1004.093450] usb 3-2.2: device descriptor read/64, error -110
[ 1019.713431] usb 3-2.2: device descriptor read/64, error -110
[ 1019.901387] usb 3-2.2: new full-speed USB device number 9 using xhci_hcd
[ 1035.329901] usb 3-2.2: device descriptor read/64, error -110
[ 1050.942376] usb 3-2.2: device descriptor read/64, error -110
[ 1051.054563] usb 3-2-port2: attempt power cycle
[ 1051.666360] usb 3-2.2: new full-speed USB device number 10 using xhci_hcd
[ 1056.750547] xhci_hcd :03:00.4: Timeout while waiting for setup device 
command
[ 1062.130695] xhci_hcd :03:00.4: Timeout while waiting for setup device 
command
[ 1062.338654] usb 3-2.2: device not accepting address 10, error -62
[ 1062.418667] usb 3-2.2: new full-speed USB device number 11 using xhci_hcd
[ 1067.502850] xhci_hcd :03:00.4: Timeout while waiting for setup device 
command
[ 1072.878997] xhci_hcd :03:00.4: Timeout while waiting for setup device 
command
[ 1073.086966] usb 3-2.2: device not accepting address 11, error -62
[ 1073.087137] usb 3-2-port2: unable to enumerate USB device
[ 1169.817093] usb 3-2.2: new full-speed USB device number 12 using xhci_hcd
[ 1185.349407] usb 3-2.2: device descriptor read/64, error -110
[ 1200.961721] usb 3-2.2: device descriptor read/64, error -110
[ 1201.149688] usb 3-2.2: new full-speed USB device number 13 using xhci_hcd
[ 1216.578486] usb 3-2.2: device descriptor read/64, error -110
[ 1232.194238] usb 3-2.2: device descriptor read/64, error -110
[ 1232.302402] usb 3-2-port2: attempt power cycle
[ 1232.914167] usb 3-2.2: new full-speed USB device number 14 using xhci_hcd
[ 1238.002414] xhci_hcd :03:00.4: Timeout while waiting for setup device 
command
[ 1243.377705] xhci_hcd :03:00.4: Timeout while waiting for setup device 
command
[ 1243.585638] usb 3-2.2: device not accepting address 14, error -62
[ 1243.669633] usb 3-2.2: new full-speed USB device number

[Touch-packages] [Bug 1958019] Re: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all

[joe]

Weirdly simple, but wow, this cannot be it. Hallelujah After a few
days reading and testing many things, I finally have audio! Apparently,
it was missing (some?) library required for pipewire. I have a Legion 7i
Pro running popOS on kernel 6.6.6-76060606-generic. Try running this
command:

sudo apt install libpipewire*

Two library files were installed:

libpipewire-0.3-dev:amd64 (1.0.0~1701092078~22.04~594e8f5)

libspa-0.2-dev:amd64 (1.0.0~1701092078~22.04~594e8f5, automatic)


Then, I rebooted, tested audio, and voila!

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Touch-packages] [Bug 824477] Re: sudo is remakably unhelpful when the target app is missing

[Joe Breu]

This is still present on 22.04

USER@HOSTNAME:/etc/pam.d$ sudo /usr/bin/cmd-not-found
[sudo] password for USER:
Sorry, try again.
[sudo] password for USER:


Nov 15 21:27:49 HOSTNAME sudo: pam_unix(sudo:auth): conversation failed
Nov 15 21:27:49 HOSTNAME sudo: pam_unix(sudo:auth): auth could not identify 
password for [USER]

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

Title:
  sudo is remakably unhelpful when the target app is missing

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  sudoers.d contains:

  backup ALL=NOPASSWD: /usr/bin/rsync --config=/etc/rsync-backup.conf
  --server --daemon .

  server# su backup
  server$ sudo /usr/bin/rsync --config=/etc/rsync-backup.conf --server --daemon 
.
  [sudo] password for backup:

  wtf? This setup works on all my other servers, why is it prompting for
  a password here? Let's check the auth.log

  Aug 11 11:35:19 server sudo: pam_unix(sudo:auth): conversation failed
  Aug 11 11:35:19 server sudo: pam_unix(sudo:auth): auth could not identify 
password for [backup]

  "conversation failed" means nothing to me, and backup has password-
  based login disabled, so not having a password is intentional...

  After lots of messing around, I *accidentally* stumbled across the
  fact that /usr/bin/rsync was missing. If it weren't for this accident,
  I probably never would have figured it out. Can we please have an
  error message more useful than "conversation failed"? Even now that I
  know what the problem was, I have no idea how that message was
  supposed to help me find it...

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: sudo 1.7.4p4-5ubuntu7.1
  ProcVersionSignature: Ubuntu 3.0.0-4.5-generic 3.0.0-rc6
  Uname: Linux 3.0.0-4-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Thu Aug 11 12:44:46 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: sudo
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1509587] Re: package initramfs-tools 0.120ubuntu6 failed to install/upgrade: 子程序 已安裝的 post-installation script 傳回了錯誤退出狀態 1

[Joe]

Hi, Benjamin,

This bug has been reported 8 years ago.
I even don't remember which Raspberry Pi device reported the bug.

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

Title:
  package initramfs-tools 0.120ubuntu6 failed to install/upgrade: 子程序
  已安裝的 post-installation script 傳回了錯誤退出狀態 1

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  Upgrading Ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: initramfs-tools 0.120ubuntu6
  ProcVersionSignature: Ubuntu 3.18.0-25.26-rpi2 3.18.17
  Uname: Linux 3.18.0-25-rpi2 armv7l
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: armhf
  Date: Sat Oct 24 04:48:58 2015
  ErrorMessage: 子程序 已安裝的 post-installation script 傳回了錯誤退出狀態 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5
   apt  1.0.10.2ubuntu1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.120ubuntu6 failed to install/upgrade: 子程序 
已安裝的 post-installation script 傳回了錯誤退出狀態 1
  UpgradeStatus: Upgraded to wily on 2015-10-23 (0 days ago)

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


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

[Touch-packages] [Bug 1926802] Re: qt5-default package is missed in 21.04

[Joe Smith]

The problem is that without a default package, how does one install all
the runtime libraries without installing all the dev stuff ?


So far I've found that installing this 

"sudo apt install qt5-gtk-platformtheme qttranslations5-l10n
libqt5core5a libqt5dbus5 libqt5gui5 libqt5network5 libqt5svg5
libqt5widgets5 libqt5x11extras5 libqt5sql5 libqt5sql5-sqlite libqt5test5
libqt5xml5 libqt5printsupport5 libqt5serialport5 libqt5opengl5"

So, without all the -dev packages

It would be nice to have a single package name to remember for all of
this

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

Title:
  qt5-default package is missed in 21.04

Status in qtbase-opensource-src package in Ubuntu:
  Invalid
Status in Unity Linux:
  New

Bug description:
  Previous 20.10 version has the qt5-default package in place (see
  https://packages.ubuntu.com/groovy/qt5-default ).

  Please upload the  qt5-default package for 21.04 Ubuntu version.

  What is interesting - all its dependencies can be simply installed
  with `sudo apt-get install qtbase5-dev qtchooser qt5-qmake
  qtbase5-dev-tools` .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1926802/+subscriptions


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

[Touch-packages] [Bug 2009435] [NEW] Xorg freeze

[Joe Stevenson-Pew]

Public bug reported:

Files application hangs when switched to from other application. Only
occurs when mounted to internal HDD.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-35-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar  6 08:50:17 2023
DistUpgraded: 2022-09-30 11:53:10,478 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 virtualbox/6.1.38, 5.15.0-67-generic, x86_64: installed
 virtualbox/6.1.38, 5.19.0-32-generic, x86_64: installed
 virtualbox/6.1.38, 5.19.0-35-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 
540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
   Subsystem: Sapphire Technology Limited Lexa PRO [Radeon RX 550] [1da2:e367]
InstallationDate: Installed on 2020-10-24 (862 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=9db35888-ce9e-4ddd-96ab-979cf2de8c9e ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to jammy on 2022-09-30 (156 days ago)
dmi.bios.date: 11/13/2019
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2006
dmi.board.asset.tag: Default string
dmi.board.name: PRIME B450M-K
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2006:bd11/13/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug false-gpu-hang freeze jammy 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/2009435

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Files application hangs when switched to from other application. Only
  occurs when mounted to internal HDD.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  6 08:50:17 2023
  DistUpgraded: 2022-09-30 11:53:10,478 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.38, 5.15.0-67-generic, x86_64: installed
   virtualbox/6.1.38, 5.19.0-32-generic, x86_64: installed
   virtualbox/6.1.38, 5.19.0-35-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / 
RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: Sapphire Technology Limited Lexa PRO [Radeon RX 550] [1da2:e367]
  InstallationDate: Installed on 2020-10-24 (862 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 

[Touch-packages] [Bug 1698083] Re: Maximize vertically/horizontally doesn't work (in some apps) if configured via middle-click

[Joe Barnett]

looks like https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/5070
addresses this in gtk3 apps, can it (and/or the next gtk release) be
added to the ubuntu package and the snap package that contains gtk3
(gnome-* snap?)

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

Title:
  Maximize vertically/horizontally doesn't work (in some apps) if
  configured via middle-click

Status in GTK+:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/gtk/issues/539

  In Gnome Tweak Tool you can configure vertical maximizing for:
    Windows > Titlebar Actions > Middle-Click
  However this feature seems to get ignored in Wayland sessions (it just 
maximizes fully instead). It only works correctly in Xorg Gnome sessions.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Thu Jun 15 14:46:04 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2017-05-03 (43 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1986861] [NEW] pulseaudio stops accepting connections

[Joe Barnett]

Public bug reported:

After a while, pulseaudio clients get connections refused and are unable
to play audio / receive microphone input.

journalctl shows lots of messages like:

Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] native-common.c: 
Expected 1 memfd fd to be received over pipe; got 0
Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] native-common.c: Did 
we reach our open file descriptors limit?
Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] protocol-native.c: 
protocol error, kicking client


as well as 

Aug 17 13:03:52 taplop pulseaudio[2244465]: [pulseaudio] protocol-
native.c: Warning! Too many connections (64), dropping incoming
connection.


killing the pulseaudio daemon makes audio work for a little while until the 
same thing repeats.  not sure what's triggering it though, or how to best find 
out.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
Uname: Linux 5.17.0-051700drmtip20220329-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jbarnett  2265029 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Wed Aug 17 14:13:56 2022
InstallationDate: Installed on 2019-08-17 (1096 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to jammy on 2022-03-18 (152 days ago)
dmi.bios.date: 03/25/2021
dmi.bios.release: 1.15
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.15.1
dmi.board.name: 0N338G
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D:
dmi.product.family: XPS
dmi.product.name: XPS 15 9575
dmi.product.sku: 080D
dmi.sys.vendor: Dell Inc.

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

Title:
  pulseaudio stops accepting connections

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After a while, pulseaudio clients get connections refused and are
  unable to play audio / receive microphone input.

  journalctl shows lots of messages like:

  Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] native-common.c: 
Expected 1 memfd fd to be received over pipe; got 0
  Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] native-common.c: Did 
we reach our open file descriptors limit?
  Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] protocol-native.c: 
protocol error, kicking client

  
  as well as 

  Aug 17 13:03:52 taplop pulseaudio[2244465]: [pulseaudio] protocol-
  native.c: Warning! Too many connections (64), dropping incoming
  connection.

  
  killing the pulseaudio daemon makes audio work for a little while until the 
same thing repeats.  not sure what's triggering it though, or how to best find 
out.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  Uname: Linux 5.17.0-051700drmtip20220329-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jbarnett  2265029 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Wed Aug 17 14:13:56 2022
  InstallationDate: Installed on 2019-08-17 (1096 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to jammy on 2022-03-18 (152 days ago)
  dmi.bios.date: 03/25/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.1
  dmi.board.name: 0N338G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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


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

[Touch-packages] [Bug 1974263] [NEW] online accounts crash during setup

[Joe]

Public bug reported:

Settings crash when trying to add a Google online account.

1. open settings
2. choose Google
3. crash

I'm using wayland on Ubuntu 22.04 LTS.

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

** Attachment added: "_usr_bin_gnome-control-center.1000.crash"
   
https://bugs.launchpad.net/bugs/1974263/+attachment/5591443/+files/_usr_bin_gnome-control-center.1000.crash

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

Title:
  online accounts crash during setup

Status in apport package in Ubuntu:
  New

Bug description:
  Settings crash when trying to add a Google online account.

  1. open settings
  2. choose Google
  3. crash

  I'm using wayland on Ubuntu 22.04 LTS.

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


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

[Touch-packages] [Bug 1966571] Re: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed

[Joe Barnett]

seeing the same behavior with the -non-free version too, does it need a
separate rebuild?

** Also affects: intel-media-driver-non-free (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init
  failed

Status in intel-media-driver package in Ubuntu:
  Fix Committed
Status in intel-media-driver-non-free package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Invalid

Bug description:
  I noticed that it upgraded mesa to 22.x and now video acceleration is
  not working due to:

  ❯ vainfo 
  libva info: VA-API version 1.14.0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
  libva info: Found init function __vaDriverInit_1_14
  libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
  libva info: va_openDriver() returns 1
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_10
  libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
  libva info: va_openDriver() returns -1
  vaInitialize failed with error code -1 (unknown libva error),exit
  ~/Desktop 
  ❯ inxi -G
  Graphics:
Device-1: Intel driver: i915 v: kernel
Device-2: Generalplus GENERAL WEBCAM type: USB
  driver: snd-usb-audio,uvcvideo
Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting
  unloaded: fbdev,vesa gpu: i915 resolution: 3840x2160~60Hz
OpenGL: renderer: Mesa Intel UHD Graphics P630 (CML GT2)
  v: 4.6 Mesa 22.0.0

  I tried rebuilding the i965-va-driver, and it's still the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mesa-vdpau-drivers 22.0.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 27 10:37:41 2022
  DistUpgraded: 2022-01-18 23:59:55,390 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   rtl88x2bu/5.8.7.1, 5.15.0-18-generic, x86_64: installed
   rtl88x2bu/5.8.7.1, 5.15.0-22-generic, x86_64: installed
   rtl88x2bu/5.8.7.1, 5.15.0-23-generic, x86_64: installed
   rtl88x2bu/5.8.7.1, 5.17.0-xanmod1, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9bc6] (rev 05) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
  InstallationDate: Installed on 2021-10-05 (172 days ago)
  InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Beta amd64 (20211004)
  MachineType: ASUS System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=018d5b69-accd-451b-a6f7-2027f791ea0e ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to jammy on 2022-01-18 (67 days ago)
  dmi.bios.date: 07/08/2021
  dmi.bios.release: 23.1
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2301
  dmi.board.asset.tag: Default string
  dmi.board.name: Pro WS W480-ACE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/08/2021:br23.1:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnProWSW480-ACE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 1965647] Re: pulseaudio gets stuck after launching firefox

[Joe Barnett]

seems like pulse was fighting with pipewire; not sure what I did to
clean it up but appears to be working better now

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

Title:
  pulseaudio gets stuck after launching firefox

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  after updating to jammy, pulseaudio appears to get stuck after opening
  firefox.

  I can play an audio file using mplayer fine, then I open firefox (either snap 
or deb version), then it fails to play the same audio file and prints out
  "Audio device got stuck!"

  killing pulseaudio (and having systemd user session restart it)
  restores sound in mplayer

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jbarnett   3283 F wireplumber
   /dev/snd/controlC0:  jbarnett   3283 F wireplumber
    jbarnett   7684 F pulseaudio
   /dev/snd/seq:jbarnett   3278 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sat Mar 19 15:29:11 2022
  InstallationDate: Installed on 2019-08-17 (945 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to jammy on 2022-03-18 (1 days ago)
  dmi.bios.date: 03/25/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.1
  dmi.board.name: 0N338G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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


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

[Touch-packages] [Bug 1965647] [NEW] pulseaudio gets stuck after launching firefox

[Joe Barnett]

Public bug reported:

after updating to jammy, pulseaudio appears to get stuck after opening
firefox.

I can play an audio file using mplayer fine, then I open firefox (either snap 
or deb version), then it fails to play the same audio file and prints out
"Audio device got stuck!"

killing pulseaudio (and having systemd user session restart it) restores
sound in mplayer

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  jbarnett   3283 F wireplumber
 /dev/snd/controlC0:  jbarnett   3283 F wireplumber
  jbarnett   7684 F pulseaudio
 /dev/snd/seq:jbarnett   3278 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Sat Mar 19 15:29:11 2022
InstallationDate: Installed on 2019-08-17 (945 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to jammy on 2022-03-18 (1 days ago)
dmi.bios.date: 03/25/2021
dmi.bios.release: 1.15
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.15.1
dmi.board.name: 0N338G
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D:
dmi.product.family: XPS
dmi.product.name: XPS 15 9575
dmi.product.sku: 080D
dmi.sys.vendor: Dell Inc.

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


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

** Description changed:

  after updating to jammy, pulseaudio appears to get stuck after opening
  firefox.
  
- I can play an audio file using mplayer fine, then I open firefox, then it 
fails to play the same audio file and prints out
+ I can play an audio file using mplayer fine, then I open firefox (either snap 
or deb version), then it fails to play the same audio file and prints out
  "Audio device got stuck!"
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  jbarnett   3283 F wireplumber
-  /dev/snd/controlC0:  jbarnett   3283 F wireplumber
-   jbarnett   7684 F pulseaudio
-  /dev/snd/seq:jbarnett   3278 F pipewire
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  jbarnett   3283 F wireplumber
+  /dev/snd/controlC0:  jbarnett   3283 F wireplumber
+   jbarnett   7684 F pulseaudio
+  /dev/snd/seq:jbarnett   3278 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sat Mar 19 15:29:11 2022
  InstallationDate: Installed on 2019-08-17 (945 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to jammy on 2022-03-18 (1 days ago)
  dmi.bios.date: 03/25/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.1
  dmi.board.name: 0N338G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

** Description changed:

  after updating to jammy, pulseaudio appears to get stuck after opening
  firefox.
  
- I can play an audio file using mplayer fine, then I open firefox (either snap 
or deb version), then it fails to play the same audio file and prints out
+ I can play an audio file using mplayer fine, then I open firefox, then it 
fails to play the same audio file and prints out
  "Audio device got stuck!"
+ 
+ killing pulseaudio (and having systemd user session restart it) restores
+ sound in mplayer
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jbarnett   3283 F wireplumber
   /dev/snd/controlC0:  jbarnett   3283 F wireplumber
    jbarnett   7684 F pulseaudio
   /dev/snd/seq:jbarnett   3278 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sat Mar 19 15:29:11 2022
  InstallationDate: 

[Touch-packages] [Bug 1660316] Re: apparmor denial of CUPS

[Joe Henley]

Like napsty above, I'm using LM 19.3.  I fixed the problem with printing
by adding the "net_admin caps" correction, per Jamie.  That worked fine,
but now the default media player in LM 19.3 won't play mpg4 video files.
If I remove the "net_admin caps" correction, the ability to play mpg4
files is restored.  Suggestions?  Thanks!

Joe Henley

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

Title:
  apparmor denial of CUPS

Status in cups package in Ubuntu:
  Expired

Bug description:
  Printing is enabled when doing sudo aa-complain cupsd

  Here is an extract of /var/log/syslog:

  Jan 30 12:41:59 dag-TS-P500 kernel: [  868.929457] audit: type=1400 
audit(1485776519.269:37): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6932 
comm="apparmor_parser"
  Jan 30 12:41:59 dag-TS-P500 kernel: [  868.929744] audit: type=1400 
audit(1485776519.269:38): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=6932 comm="apparmor_parser"
  Jan 30 12:41:59 dag-TS-P500 kernel: [  868.945422] audit: type=1400 
audit(1485776519.285:39): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6932 
comm="apparmor_parser"
  Jan 30 12:42:10 dag-TS-P500 kernel: [  879.817070] audit: type=1400 
audit(1485776530.158:40): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6941 
comm="apparmor_parser"
  Jan 30 12:42:10 dag-TS-P500 kernel: [  879.817342] audit: type=1400 
audit(1485776530.158:41): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=6941 comm="apparmor_parser"
  Jan 30 12:42:10 dag-TS-P500 kernel: [  879.837254] audit: type=1400 
audit(1485776530.178:42): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6941 
comm="apparmor_parser"
  Jan 30 12:42:16 dag-TS-P500 zeitgeist-datah[3706]: 
downloads-directory-provider.vala:120: Couldn't process /home/dag/.glvndcEQzqA: 
Error when getting information for file '/home/dag/.glvndcEQzqA': No such file 
or directory
  Jan 30 12:42:23 dag-TS-P500 dbus[996]: [system] Activating via systemd: 
service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service'
  Jan 30 12:42:23 dag-TS-P500 systemd[1]: Starting Hostname Service...
  Jan 30 12:42:24 dag-TS-P500 dbus[996]: [system] Successfully activated 
service 'org.freedesktop.hostname1'
  Jan 30 12:42:24 dag-TS-P500 systemd[1]: Started Hostname Service.
  Jan 30 12:42:26 dag-TS-P500 kernel: [  895.746636] audit: type=1400 
audit(1485776546.086:43): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/cupsd" pid=6967 comm="lpd" capability=12  capname="net_admin"
  Jan 30 12:42:54 dag-TS-P500 systemd[1]: Starting Cleanup of Temporary 
Directories...
  Jan 30 12:42:54 dag-TS-P500 systemd-tmpfiles[6973]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
  Jan 30 12:42:54 dag-TS-P500 systemd[1]: Started Cleanup of Temporary 
Directories.
  Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Activating service 
name='com.ubuntu.OneConf'
  Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 
'com.ubuntu.OneConf'
  Jan 30 12:44:03 dag-TS-P500 com.ubuntu.OneConf[2707]: 
WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file 
or directory: 
'/home/dag/.cache/oneconf/d2fc3bf30c9f4976b441a8f14de53bda/other_hosts'
  Jan 30 12:44:23 dag-TS-P500 dbus-daemon[2707]: Activating service 
name='com.ubuntu.sso'
  Jan 30 12:44:24 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 
'com.ubuntu.sso'
  Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.685842] audit: type=1400 
audit(1485776751.028:44): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=7024 
comm="apparmor_parser"
  Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.686099] audit: type=1400 
audit(1485776751.028:45): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=7024 comm="apparmor_parser"
  Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.700446] audit: type=1400 
audit(1485776751.044:46): apparmor="STATUS" operation="profile_replace" 
profile="unconfined

[Touch-packages] [Bug 1916651] [NEW] asks about irc user home directory during upgrade

[Joe Barnett]

Public bug reported:

Upgrading from groovy to hirsuite, base-passwd asks if the `irc` user's
home directory should be moved from `/var/run/ircd` to `/run/ircd`.
Having no IRC server installed makes this very confusing, but appears
harmless (https://askubuntu.com/questions/876975/user-irc-inside-of-
default-ubuntu-16-04-server).  Possibly caused by
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946884, but can this
not prompt the user for a decision?

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: base-passwd 3.5.49
ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Tue Feb 23 12:02:59 2021
InstallationDate: Installed on 2019-08-17 (556 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
RebootRequiredPkgs:
 libc6
 libc6
 libssl1.1
 libssl1.1
SourcePackage: base-passwd
UpgradeStatus: Upgraded to hirsute on 2021-02-23 (0 days ago)

** Affects: base-passwd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute third-party-packages wayland-session

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

Title:
  asks about irc user home directory during upgrade

Status in base-passwd package in Ubuntu:
  New

Bug description:
  Upgrading from groovy to hirsuite, base-passwd asks if the `irc`
  user's home directory should be moved from `/var/run/ircd` to
  `/run/ircd`.  Having no IRC server installed makes this very
  confusing, but appears harmless
  (https://askubuntu.com/questions/876975/user-irc-inside-of-default-
  ubuntu-16-04-server).  Possibly caused by https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=946884, but can this not prompt the user for a
  decision?

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: base-passwd 3.5.49
  ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Tue Feb 23 12:02:59 2021
  InstallationDate: Installed on 2019-08-17 (556 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  RebootRequiredPkgs:
   libc6
   libc6
   libssl1.1
   libssl1.1
  SourcePackage: base-passwd
  UpgradeStatus: Upgraded to hirsute on 2021-02-23 (0 days ago)

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

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

[Touch-packages] [Bug 1886351] [NEW] [Satellite L745, Conexant CX20585, Speaker, Internal] fails after a while

[Joe Tomanelli]

Public bug reported:

I recently installed Ubuntu 20.04 on my Toshiba Satellite-L740 laptop. I seem 
to lose audio periodically. At first I thought I hit something on the keyboard 
accidentally, but can now confirm it is a random occurrence with no input from 
me. I have tried toggling the mute/volume of the system but cannot recover the 
audio. When the audio is lost there is still audio activity shown on the VU 
meter from the source shown under the output device in sound settings. I also 
plugged in headphones and am able to hear audio in the headset. When unplugging 
headset the sound does not return to the speakers.
There was no issue with audio on the laptop prior to installing Ubuntu 20.04 
(previously Windows 10). It seems to come back on it's own sometimes but then 
gets lost again. A reboot of the machine sometimes recovers the audio but 
sometimes not.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  joe1410 F pulseaudio
 /dev/snd/pcmC0D0c:   joe1410 F...m pulseaudio
 /dev/snd/pcmC0D0p:   joe1410 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul  5 19:23:02 2020
InstallationDate: Installed on 2020-06-02 (33 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_PulseAudioLog:
 Jul 05 17:44:12 joe dbus-daemon[729]: [system] Activating via systemd: service 
name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by 
':1.26' (uid=125 pid=925 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
 Jul 05 17:44:17 joe dbus-daemon[729]: [system] Activating via systemd: service 
name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.38' (uid=125 
pid=925 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" 
label="unconfined")
 Jul 05 17:44:56 joe systemd[900]: pulseaudio.service: Succeeded.
 Jul 05 17:45:05 joe systemd[900]: pulseaudio.socket: Succeeded.
Symptom_Type: Sound works for a while, then breaks
Title: [Satellite L745, Conexant CX20585, Speaker, Internal] fails after a while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/26/2012
dmi.bios.vendor: INSYDE
dmi.bios.version: 2.60
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Base Board Product Name
dmi.board.vendor: Intel Corp.
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-01V00E:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.family: Intel_Mobile
dmi.product.name: Satellite L745
dmi.product.sku: PSK0YU-01V00E
dmi.product.version: PSK0YU-01V00E
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-bug focal

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

Title:
  [Satellite L745, Conexant CX20585, Speaker, Internal] fails after a
  while

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I recently installed Ubuntu 20.04 on my Toshiba Satellite-L740 laptop. I seem 
to lose audio periodically. At first I thought I hit something on the keyboard 
accidentally, but can now confirm it is a random occurrence with no input from 
me. I have tried toggling the mute/volume of the system but cannot recover the 
audio. When the audio is lost there is still audio activity shown on the VU 
meter from the source shown under the output device in sound settings. I also 
plugged in headphones and am able to hear audio in the headset. When unplugging 
headset the sound does not return to the speakers.
  There was no issue with audio on the laptop prior to installing Ubuntu 20.04 
(previously Windows 10). It seems to come back on it's own sometimes but then 
gets lost again. A reboot of the machine sometimes recovers the audio but 
sometimes not.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   US

[Touch-packages] [Bug 1884126] Re: Trying to add google account fails with AUTH-1140

[Joe Barnett]

** Bug watch added: gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues #126
   https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/126

** Also affects: gnome-online-accounts via
   https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/126
   Importance: Unknown
   Status: Unknown

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

Title:
  Trying to add google account fails with AUTH-1140

Status in gnome-online-accounts:
  Unknown
Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Trying to add a google account that redirects to another site for sign
  in results in a window with the following error:

  {"status":"failed", "cause":[{"code":"AUTH-1140", "message": "There is
  an invalid header value that can't be parsed."}]}

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-online-accounts 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Thu Jun 18 11:41:17 2020
  InstallationDate: Installed on 2019-08-17 (306 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to focal on 2020-03-06 (104 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1884126/+subscriptions

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

[Touch-packages] [Bug 1884126] [NEW] Trying to add google account fails with AUTH-1140

[Joe Barnett]

Public bug reported:

Trying to add a google account that redirects to another site for sign
in results in a window with the following error:

{"status":"failed", "cause":[{"code":"AUTH-1140", "message": "There is
an invalid header value that can't be parsed."}]}

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-online-accounts 3.36.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Thu Jun 18 11:41:17 2020
InstallationDate: Installed on 2019-08-17 (306 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
SourcePackage: gnome-online-accounts
UpgradeStatus: Upgraded to focal on 2020-03-06 (104 days ago)

** Affects: gnome-online-accounts (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  Trying to add google account fails with AUTH-1140

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Trying to add a google account that redirects to another site for sign
  in results in a window with the following error:

  {"status":"failed", "cause":[{"code":"AUTH-1140", "message": "There is
  an invalid header value that can't be parsed."}]}

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-online-accounts 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Thu Jun 18 11:41:17 2020
  InstallationDate: Installed on 2019-08-17 (306 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to focal on 2020-03-06 (104 days ago)

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

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

[Touch-packages] [Bug 1745664] Re: [regression] systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_cln

[joe mammino]

In /etc/systemd/system/systemd-logind.service comment out
IPAddressDeny=Any

this work around has been working for us for about a 10 months now

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

Title:
  [regression] systemd-logind crashed with SIGABRT in __libc_connect()
  from __GI_clnttcp_create() from __GI___libc_rpc_getport() from
  __GI_pmap_getport() from __GI_clnttcp_create()

Status in nis package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/54968dedd418de647365aa3f0127906ca9adbfe3

  ---

  configured system to use nis.  seems to be crashing when I attempt to
  use a NIS user account

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 235-3ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Fri Jan 26 13:45:06 2018
  ExecutablePath: /lib/systemd/systemd-logind
  InstallationDate: Installed on 2018-01-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180126)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. Z370 HD3
  ProcCmdline: /lib/systemd/systemd-logind
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __libc_connect (fd=39, addr=addr@entry=..., len=len@entry=16) at 
../sysdeps/unix/sysv/linux/connect.c:26
   __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, 
prog=prog@entry=10, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27301efc, 
sendsz=sendsz@entry=400, recvsz=recvsz@entry=400) at clnt_tcp.c:153
   __GI___libc_rpc_getport (tottimeout_sec=60, timeout_sec=5, protocol=6, 
version=2, program=17, address=0x7ffc27302060) at pm_getport.c:106
   __GI_pmap_getport (address=address@entry=0x7ffc27302060, 
program=program@entry=17, version=version@entry=2, 
protocol=protocol@entry=6) at pm_getport.c:154
   __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, 
prog=prog@entry=17, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27302050, 
sendsz=sendsz@entry=0, recvsz=recvsz@entry=0) at clnt_tcp.c:136
  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.
  Title: systemd-logind crashed with SIGABRT in __libc_connect()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: Software adm bin daemon lp mail nuucp root scswebadmin sys 
sysdesign tty uucp
  dmi.bios.date: 09/22/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: Z370 HD3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd09/22/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z370 HD3
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1851407] Re: NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS

[Joe Hohertz]

I can possibly try 19.10 later, however at the moment I only have my LTS
laptop to test with.

Just to ensure we've covered any variations, here is a redacted version
of my connection file, in case I have missed anything.

[connection]
id=Vxxx
uuid=----
type=vpn
permissions=user::;
timestamp=1572967683

[vpn]
auth=SHA512
ca=/home//.cert/nm-openvpn/xxx-ca.pem
cert=/home//.cert/nm-openvpn/xxx-cert.pem
cert-pass-flags=0
cipher=AES-256-CBC
comp-lzo=adaptive
connection-type=password-tls
dev=tun
key=/home//.cert/nm-openvpn/xxx-key.pem
password-flags=2
remote=1.vpn..xxx
remote-cert-tls=server
reneg-seconds=604800
ta=/home//.cert/nm-openvpn/xxx-tls-auth.pem
ta-dir=1
username=xx
service-type=org.freedesktop.NetworkManager.openvpn

[ipv4]
dns-priority=50
dns-search=
method=auto
never-default=true

[ipv6]
addr-gen-mode=stable-privacy
dns-search=
method=auto

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

Title:
  NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager as of 1.10.6-2ubuntu1.2 has cause a regression whereby
  a VPN connection which sets it's dns-priority to a negative value,
  which should cause the DNS server supplied by the DNS connection to be
  placed first, instead now refuses to place the DNS server into the
  resolver under any circumstance.

  Pinning the 1.10.6-2ubuntu1.1 works around the issue.

  I suspect the fix-dns-leak-lp1754671.patch has caused this regression.

  This patch should be reverted as soon as possible to restore proper
  functionality of network manager with respect to VPN servers with DNS
  resolvers.

  $ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

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

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

[Touch-packages] [Bug 1851407] Re: NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS

[Joe Hohertz]

Did you ensure that the connection was set for "use only for resources
on the connection"? (I believe this may be ipv4.never-default=yes
setting in nmcli... and only bring it up because you do not mention it.)

I also think the negative DNS priority might be historical, no longer
needed. (I just noticed mine was set to 50, which I believe is default
for VPN connections now)

I should also note that if the never-default is set to "no"... I *will*
see the DNS server, however the routing is then incorrect as the VPN
concerned doesn't provide public routes.

So to be clear... never-default needs to be set to yes... DNS we expect
is from DHCP options sent from the VPN server, and the problem is that
you will see NO DNS servers for tun0 when you run the 'systemd-resolve
--status' command

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

Title:
  NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager as of 1.10.6-2ubuntu1.2 has cause a regression whereby
  a VPN connection which sets it's dns-priority to a negative value,
  which should cause the DNS server supplied by the DNS connection to be
  placed first, instead now refuses to place the DNS server into the
  resolver under any circumstance.

  Pinning the 1.10.6-2ubuntu1.1 works around the issue.

  I suspect the fix-dns-leak-lp1754671.patch has caused this regression.

  This patch should be reverted as soon as possible to restore proper
  functionality of network manager with respect to VPN servers with DNS
  resolvers.

  $ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

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

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

[Touch-packages] [Bug 1851407] Re: NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS

[Joe Hohertz]

1) Add an openvpn connection, which emits DHCP DNS servers, and is flagged "use 
only for resources on this connection"
2) Add a negative dns_priority to the connection via CLI or editing the 
connection

Prior to the change, this worked fine, you could connect, and the
indicated DNS server would become prioritised.

After the change, this no longer works, and networkmanager will not
associate a DNS server to the connection at all.

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

Title:
  NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager as of 1.10.6-2ubuntu1.2 has cause a regression whereby
  a VPN connection which sets it's dns-priority to a negative value,
  which should cause the DNS server supplied by the DNS connection to be
  placed first, instead now refuses to place the DNS server into the
  resolver under any circumstance.

  Pinning the 1.10.6-2ubuntu1.1 works around the issue.

  I suspect the fix-dns-leak-lp1754671.patch has caused this regression.

  This patch should be reverted as soon as possible to restore proper
  functionality of network manager with respect to VPN servers with DNS
  resolvers.

  $ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

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

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

[Touch-packages] [Bug 1851407] [NEW] NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS

[Joe Hohertz]

Public bug reported:

NetworkManager as of 1.10.6-2ubuntu1.2 has cause a regression whereby a
VPN connection which sets it's dns-priority to a negative value, which
should cause the DNS server supplied by the DNS connection to be placed
first, instead now refuses to place the DNS server into the resolver
under any circumstance.

Pinning the 1.10.6-2ubuntu1.1 works around the issue.

I suspect the fix-dns-leak-lp1754671.patch has caused this regression.

This patch should be reverted as soon as possible to restore proper
functionality of network manager with respect to VPN servers with DNS
resolvers.

$ lsb_release -rd
Description:Ubuntu 18.04.3 LTS
Release:18.04

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

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

Title:
  NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS

Status in network-manager package in Ubuntu:
  New

Bug description:
  NetworkManager as of 1.10.6-2ubuntu1.2 has cause a regression whereby
  a VPN connection which sets it's dns-priority to a negative value,
  which should cause the DNS server supplied by the DNS connection to be
  placed first, instead now refuses to place the DNS server into the
  resolver under any circumstance.

  Pinning the 1.10.6-2ubuntu1.1 works around the issue.

  I suspect the fix-dns-leak-lp1754671.patch has caused this regression.

  This patch should be reverted as soon as possible to restore proper
  functionality of network manager with respect to VPN servers with DNS
  resolvers.

  $ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

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

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

[Touch-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

[Joe Hohertz]

1.10.6-2ubuntu1.2 has cause a regression in functionality.

Anyone using a "split" VPN, where there is no default route, AND wish to
have DNS services supplied by the server to be honoured, via use of the
ipv4.dns-priority parameter, will have this broken. This is a bit of a
sore point considering the hoops one has to jump through to make this
work at all.

Reverting to previous version restores functionality.

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in network-manager source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  When using a VPN the DNS requests might still be sent to a DNS server outside 
the VPN when they should not

  [Test case]
  1) Set up a VPN with split tunneling:
a) Configure VPN normally (set up remote host, any ports and options needed 
for the VPN to work)
b) Under the IPv4 tab: enable "Use this connection only for the resources 
on its network".
c) Under the IPv6 tab: enable "Use this connection only for the resources 
on its network".

  2) Connect to the VPN.

  3) Run 'systemd-resolve --status'; note the DNS servers configured:
a) For the VPN; under a separate link (probably tun0), note down the IP of 
the DNS server(s). Also note the name of the interface (link).
b) For the "main" connection; under the link for your ethernet or wireless 
devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). 
Also note the name of the interface (link).

  4) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  5) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  6) In yet another terminal, issue name resolution requests using dig:
a) For a name known to be reachable via the public network:
   'dig www.yahoo.com'
b) For a name known to be reachable only via the VPN:
   'dig '

  7) Check the output of each terminal running tcpdump. When requesting
  the public name, traffic can go through either. When requesting the
  "private" name (behind the VPN), traffic should only be going through
  the interface for the VPN. Additionally, ensure the IP receiving the
  requests for the VPN name is indeed the IP address noted above for the
  VPN's DNS server.

  If you see no traffic showing in tcpdump output when requesting a
  name, it may be because it is cached by systemd-resolved. Use a
  different name you have not tried before.

  
  [Regression potential]
  The code change the handling of DNS servers when using a VPN, we should check 
that name resolution still work whne using a VPN in different configurations

  -

  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

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

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

[Touch-packages] [Bug 1797872] Re: ntpd keeps Soliciting pool server

[Joe Henley]

Same problem on my PC running:  Linux Mint 19.2 Mate.

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

Title:
  ntpd keeps Soliciting pool server

Status in ntp package in Ubuntu:
  Confirmed

Bug description:
  ntpd keeps printing "Soliciting pool server" in the syslog (once every
  5 seconds).

  $ ntpq -c pe
   remote   refid  st t when poll reach   delay   offset  jitter
  ==
   0.ubuntu.pool.n .POOL.  16 p-   6400.0000.000   0.000
   1.ubuntu.pool.n .POOL.  16 p-   6400.0000.000   0.000
   2.ubuntu.pool.n .POOL.  16 p-   6400.0000.000   0.000
   3.ubuntu.pool.n .POOL.  16 p-   6400.0000.000   0.000
   ntp.ubuntu.com  .POOL.  16 p-   6400.0000.000   0.000

  $ sudo ntpq -c rv
  associd=0 status=c016 leap_alarm, sync_unspec, 1 event, restart,
  version="ntpd 4.2.8p4@1.3265-o Fri Jul  6 20:10:51 UTC 2018 (1)",
  processor="x86_64", system="Linux/4.15.0-33-generic", leap=11,
  stratum=16, precision=-24, rootdelay=0.000, rootdisp=0.360, refid=INIT,
  reftime=.  Thu, Feb  7 2036  6:28:16.000,
  clock=df6ee808.934d239d  Mon, Oct 15 2018 11:18:48.575, peer=0, tc=3,
  mintc=3, offset=0.00, frequency=6.224, sys_jitter=0.00,
  clk_jitter=0.000, clk_wander=0.000

  
  I have changed nothing in the default configuration of ntp or the firewall.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.9
  ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Oct 15 11:17:45 2018
  InstallationDate: Installed on 2018-04-20 (177 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1833652] Re: [SB-XFi - Creative X-Fi, playback] No sound at all

[Joe F.]

Made sure everything is on/not muted and still no sound. Also tried
under a live session of Ubuntu 16.04 which detected the card, but still
came up with no sound.

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

Title:
  [SB-XFi - Creative X-Fi, playback] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Installed a new X-Fi sound card, but no audio is being heard during
  playback on Ubuntu 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jfilingeri   1723 F pulseaudio
jfilingeri   3577 F alsamixer
   /dev/snd/controlC1:  jfilingeri   1723 F pulseaudio
  CurrentDesktop: MATE
  Date: Thu Jun 20 23:32:37 2019
  InstallationDate: Installed on 2019-06-18 (3 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:XFi failed
  Symptom_Card: Cedar HDMI Audio [Radeon HD 5400/6300/7300 Series] - HDA ATI 
HDMI
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jfilingeri   1723 F pulseaudio
jfilingeri   3577 F alsamixer
   /dev/snd/pcmC0D0p:   jfilingeri   1723 F...m pulseaudio
   /dev/snd/controlC1:  jfilingeri   1723 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SB-XFi - Creative X-Fi, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170M-D3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd09/08/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170M-D3H-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1833652] Re: [SB-XFi - Creative X-Fi, playback] No sound at all

[Joe F.]

Internal audio is disabled in the BIOS.

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

Title:
  [SB-XFi - Creative X-Fi, playback] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Installed a new X-Fi sound card, but no audio is being heard during
  playback on Ubuntu 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jfilingeri   1723 F pulseaudio
jfilingeri   3577 F alsamixer
   /dev/snd/controlC1:  jfilingeri   1723 F pulseaudio
  CurrentDesktop: MATE
  Date: Thu Jun 20 23:32:37 2019
  InstallationDate: Installed on 2019-06-18 (3 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:XFi failed
  Symptom_Card: Cedar HDMI Audio [Radeon HD 5400/6300/7300 Series] - HDA ATI 
HDMI
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jfilingeri   1723 F pulseaudio
jfilingeri   3577 F alsamixer
   /dev/snd/pcmC0D0p:   jfilingeri   1723 F...m pulseaudio
   /dev/snd/controlC1:  jfilingeri   1723 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SB-XFi - Creative X-Fi, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170M-D3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd09/08/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170M-D3H-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1833652] [NEW] [SB-XFi - Creative X-Fi, playback] No sound at all

[Joe F.]

Public bug reported:

Installed a new X-Fi sound card, but no audio is being heard during
playback on Ubuntu 18.04.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jfilingeri   1723 F pulseaudio
  jfilingeri   3577 F alsamixer
 /dev/snd/controlC1:  jfilingeri   1723 F pulseaudio
CurrentDesktop: MATE
Date: Thu Jun 20 23:32:37 2019
InstallationDate: Installed on 2019-06-18 (3 days ago)
InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:XFi failed
Symptom_Card: Cedar HDMI Audio [Radeon HD 5400/6300/7300 Series] - HDA ATI HDMI
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jfilingeri   1723 F pulseaudio
  jfilingeri   3577 F alsamixer
 /dev/snd/pcmC0D0p:   jfilingeri   1723 F...m pulseaudio
 /dev/snd/controlC1:  jfilingeri   1723 F pulseaudio
Symptom_Type: No sound at all
Title: [SB-XFi - Creative X-Fi, playback] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/08/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F3
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z170M-D3H-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd09/08/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170M-D3H-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug bionic

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

Title:
  [SB-XFi - Creative X-Fi, playback] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Installed a new X-Fi sound card, but no audio is being heard during
  playback on Ubuntu 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jfilingeri   1723 F pulseaudio
jfilingeri   3577 F alsamixer
   /dev/snd/controlC1:  jfilingeri   1723 F pulseaudio
  CurrentDesktop: MATE
  Date: Thu Jun 20 23:32:37 2019
  InstallationDate: Installed on 2019-06-18 (3 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:XFi failed
  Symptom_Card: Cedar HDMI Audio [Radeon HD 5400/6300/7300 Series] - HDA ATI 
HDMI
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jfilingeri   1723 F pulseaudio
jfilingeri   3577 F alsamixer
   /dev/snd/pcmC0D0p:   jfilingeri   1723 F...m pulseaudio
   /dev/snd/controlC1:  jfilingeri   1723 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SB-XFi - Creative X-Fi, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170M-D3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd09/08/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170M-D3H-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: To be filled by O.E.M.
  

[Touch-packages] [Bug 1829685] [NEW] [MXG071, SigmaTel STAC9228, Speaker, Internal] No sound at all

[Joe Sigrid]

Public bug reported:

I had sound before the current Ubuntu upgrade. I have no sound with the
latest upgrade Ubuntu 19.04. The soundbar seems to be working in the
sound setting but receive no output sound at all. Any help will greatly
be appreciated. Thanks

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
Uname: Linux 5.0.0-16-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  joe5605 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun May 19 22:12:48 2019
InstallationDate: Installed on 2018-01-28 (476 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
Symptom_Card: Built-in Audio - HDA Intel
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  root   1039 F pulseaudio
      joe5605 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [MXG071, SigmaTel STAC9228, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/23/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 345678
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd04/23/2010:svnDellInc.:pnMXG071:pvr:rvnDellInc.:rn345678:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: MXG071
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug disco

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

Title:
  [MXG071, SigmaTel STAC9228, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I had sound before the current Ubuntu upgrade. I have no sound with
  the latest upgrade Ubuntu 19.04. The soundbar seems to be working in
  the sound setting but receive no output sound at all. Any help will
  greatly be appreciated. Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joe5605 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 19 22:12:48 2019
  InstallationDate: Installed on 2018-01-28 (476 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  root   1039 F pulseaudio
    joe5605 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [MXG071, SigmaTel STAC9228, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 345678
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd04/23/2010:svnDellInc.:pnMXG071:pvr:rvnDellInc.:rn345678:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: MXG071
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1300382] Re: input events not being flushed in browser until pressing hardware keys

[joe]

When you see that input event not being flushed in the browser until
pressing hardware keys Edit then it might some technical glitch, so I
suggest you to go https://antiviruschatsupport.co/norton-support/ they
told you how to solve it.

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

Title:
  input events not being flushed in browser until pressing hardware keys

Status in Oxide:
  Fix Released
Status in ubuntu-keyboard:
  Fix Released
Status in The Webapps-core project:
  Invalid
Status in oxide-qt package in Ubuntu:
  Fix Released
Status in ubuntu-keyboard package in Ubuntu:
  Fix Released

Bug description:
  using webbrowser-app from Silo 9 and oxide in universe

  Log in to Facebook on the phone
  Click "comment" in someone's post
  Start typing

  Expected results:
  The comment button should become enabled so you can submit comment

  Actual results:
  The comment button always stays disabled.

  Tested this on webbrowser-app on desktop with oxide (explicilty
  loading m.facebook.com) and becomes enabled as it should after typing.
  Seems specific to device. Guessing it's a UA String issue.

  Is there a way to see the JS console to see if a JS error is occuring?

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

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

[Touch-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)

[Joe]

Install gnome-shell 3.28.3-0ubuntu0.18.04.4 from the -proposed repo
fixed the problem for me! Running Ubuntu 18.04. Thanks for the fix!

$ apt list gnome-shell
Listing... Done
gnome-shell/now 3.28.3-0ubuntu0.18.04.4 amd64 [installed,local]

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

Title:
  Ubuntu 18.04's ibus package breaks password fields in Firefox (by
  lowering & raising window whenever they're focused)

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Cosmic:
  Fix Committed
Status in ibus source package in Cosmic:
  Invalid

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/391

  ---

  tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise
  Firefox, whenever the user tries to focus an 
  field on a web page.  This is not a regression in Firefox, as the same
  Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug
  in ibus, because it only happens (in 18.04) when the environmental
  variable GTK_IM_MODULE is at its default value (which is "ibus").  It
  had this same value in 17.10 but the bug didn't happen there; hence,
  I'm guessing there was a change in ibus (or a related package) that
  caused this breakage / lowering+raising.

  This is pretty bad, because in some cases, the focus-loss can mean
  users are simply unable to fill in password fields that previously
  were working fine. (see "ACTUAL RESULTS" below)

  STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension:
  =
   1. Start Firefox. (fresh profile if you like)
   2. Install BitWarden from 
https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/
   3. Click the BitWarden toolbar icon to spawn a menu-pane.
   4. Click "Log in" at the bottom of that pane.
   5. Click the "Master Password" field.

  ACTUAL RESULTS:
   The menu pane disappears as soon as the Master Password field receives focus.
  EXPECTED RESULTS:
   I should be able to type in a password; pane shouldn't disappear.

  STEPS TO REPRODUCE #2, via Reddit:
  =
   1. Visit https://www.reddit.com/r/firefox/ (or any reddit page)
   2. Click "Log in or sign up in seconds" at the extreme upper right of the 
page.
    (click the "Log in" part of that sentence)
   3. Try to click the password field (or "tab" into it) and type in some text.

  ACTUAL RESULTS:
   Try as you might, the password field never receives focus.
  EXPECTED RESULTS:
   Password field should accept focus & let me type text into it.

  If I run firefox from the command line with env var GTK_IM_MODULE="",
  then I get "expected results".  But with the default value of that env
  var, I get "actual results" (broken behavior, unable to enter
  passwords).

  I initially reported this in Firefox, here:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few
  dependent bugs for the usage-specific STR quoted above).  But I think
  it's a bug in ibus, hence filing here now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 18 23:22:05 2018
  InstallationDate: Installed on 2018-04-17 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1805635] [NEW] package openssh-server 1:7.2p2-4ubuntu2.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Joe]

Public bug reported:

I wasn't doing anything. Bug was there when I returned to screen first
thing in the morning.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: openssh-server 1:7.2p2-4ubuntu2.6
ProcVersionSignature: Ubuntu 4.15.0-39.42~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Wed Nov 28 06:21:09 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2018-04-14 (227 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.29
SourcePackage: openssh
Title: package openssh-server 1:7.2p2-4ubuntu2.6 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.6 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  I wasn't doing anything. Bug was there when I returned to screen first
  thing in the morning.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.6
  ProcVersionSignature: Ubuntu 4.15.0-39.42~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Nov 28 06:21:09 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-04-14 (227 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.6 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1771329] Re: Can't open apps due to Too many open files

[Joe Littlejohn]

Not sure which part of this fixes the problem, but I don't have any
issues after I run the following:

echo '* hard nofile 2097152' | sudo tee -a /etc/security/limits.conf
echo '* soft nofile 2097152' | sudo tee -a /etc/security/limits.conf
echo 'root hard nofile 2097152' | sudo tee -a /etc/security/limits.conf
echo 'root soft nofile 2097152' | sudo tee -a /etc/security/limits.conf
echo 'session required pam_limits.so' | sudo tee -a /etc/pam.d/common-session
echo 'DefaultLimitNOFILE=2097152' | sudo tee -a /etc/systemd/user.conf
echo 'DefaultLimitNOFILE=2097152' | sudo tee -a /etc/systemd/system.conf

Maybe it's all needed. Maybe only the last two lines are needed.

¯\_(ツ)_/¯

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

Title:
  Can't open apps due to Too many open files

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  Occasionally I find that I can't launch a new terminal, or can't
  achieve some other desktop task. Checking journalctl I see error
  messages like this:

  May 15 12:12:15 jl-XPS-13-9360 terminator.desktop[11840]:
  dbus.exceptions.DBusException:
  org.freedesktop.DBus.Error.LimitsExceeded: Failed to determine seats
  of user "1000": Too many open files

  
  or this:

  May 15 12:12:47 jl-XPS-13-9360 google-chrome.desktop[28308]:
  [28308:28343:0515/121247.966786:ERROR:bus.cc(394)] Failed to connect
  to the bus: Failed to determine seats of user "1000": Too many open
  files

  
  At the time this happen's I'm usually running Slack, Chrome, Emacs, and a few 
Java apps.

  I'm using Ubuntu Bionic (18.04), 4.15.0-20-generic x86_64, vanilla
  gnome-shell.

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

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

[Touch-packages] [Bug 1793433] [NEW] package linux-image-4.15.0-34-generic 4.15.0-34.37 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Joe Pedro]

Public bug reported:

unable to update to any newer kernel after upgrade.  stuck on version
linux-image-4.15.0-32-generic currently.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-34-generic 4.15.0-34.37
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  viral  4203 F pulseaudio
 /dev/snd/controlC0:  viral  4203 F pulseaudio
Date: Wed Sep 19 22:56:45 2018
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=c358033e-93c3-4821-b8fd-cfe6862d5a91
InstallationDate: Installed on 2011-10-06 (2541 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
IwConfig:
 eth3  no wireless extensions.
 
 lono wireless extensions.
 
 eth1  no wireless extensions.
MachineType: To be filled by O.E.M. To be filled by O.E.M.
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=1a3abf75-9125-457a-b20c-b45dc6774fd9 ro quiet splash security=selinux 
selinux=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions: grub-pc 2.02-2ubuntu8.4
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: initramfs-tools
Title: package linux-image-4.15.0-34-generic 4.15.0-34.37 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)
dmi.bios.date: 10/16/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1604
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: SABERTOOTH 990FX
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1604:bd10/16/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

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


** Tags: amd64 apport-hook-error apport-package bionic

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

Title:
  package linux-image-4.15.0-34-generic 4.15.0-34.37 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:
  unable to update to any newer kernel after upgrade.  stuck on version
  linux-image-4.15.0-32-generic currently.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-34-generic 4.15.0-34.37
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  viral  4203 F pulseaudio
   /dev/snd/controlC0:  viral  4203 F pulseaudio
  Date: Wed Sep 19 22:56:45 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=c358033e-93c3-4821-b8fd-cfe6862d5a91
  InstallationDate: Installed on 2011-10-06 (2541 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  IwConfig:
   eth3  no wireless extensions.
   
   lono wireless extensions.
   
   eth1  no wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=1a3abf75-9125-457a-b20c-b45dc6774fd9 ro quiet splash security=selinux 
selinux=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc 2.02-2ubuntu8.4
  RfKill:
   0: hci0: Bluetooth
Soft blocked: 

[Touch-packages] [Bug 1793431] [NEW] Unable to install new kernel images after upgrade

[Joe Pedro]

Public bug reported:

all updates for new kernel versions fail.  stuck on linux-
image-4.15.0-32-generic currently.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-33-generic 4.15.0-33.36
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
AptOrdering: NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  viral  4203 F pulseaudio
 /dev/snd/controlC0:  viral  4203 F pulseaudio
Date: Wed Sep 19 22:35:56 2018
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=c358033e-93c3-4821-b8fd-cfe6862d5a91
InstallationDate: Installed on 2011-10-06 (2541 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
IwConfig:
 eth3  no wireless extensions.
 
 lono wireless extensions.
 
 eth1  no wireless extensions.
MachineType: To be filled by O.E.M. To be filled by O.E.M.
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=1a3abf75-9125-457a-b20c-b45dc6774fd9 ro quiet splash security=selinux 
selinux=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions: grub-pc 2.02-2ubuntu8.4
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: initramfs-tools
Title: package linux-image-4.15.0-33-generic 4.15.0-33.36 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)
dmi.bios.date: 10/16/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1604
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: SABERTOOTH 990FX
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1604:bd10/16/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

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


** Tags: amd64 apport-hook-error apport-package bionic

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

Title:
  Unable to install new kernel images after upgrade

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  all updates for new kernel versions fail.  stuck on linux-
  image-4.15.0-32-generic currently.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  viral  4203 F pulseaudio
   /dev/snd/controlC0:  viral  4203 F pulseaudio
  Date: Wed Sep 19 22:35:56 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=c358033e-93c3-4821-b8fd-cfe6862d5a91
  InstallationDate: Installed on 2011-10-06 (2541 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  IwConfig:
   eth3  no wireless extensions.
   
   lono wireless extensions.
   
   eth1  no wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=1a3abf75-9125-457a-b20c-b45dc6774fd9 ro quiet splash security=selinux 
selinux=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc 2.02-2ubuntu8.4
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: initramfs-tools
  

[Touch-packages] [Bug 1793432] [NEW] package initramfs-tools 0.130ubuntu3.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status

[Joe Pedro]

Public bug reported:

unable to install kernel updates.  stuck on linux-
image-4.15.0-32-generic currently.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.130ubuntu3.3
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Wed Sep 19 22:56:50 2018
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2011-10-06 (2541 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.130ubuntu3.3 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-hook-error apport-package bionic

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

Title:
  package initramfs-tools 0.130ubuntu3.3 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  unable to install kernel updates.  stuck on linux-
  image-4.15.0-32-generic currently.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3.3
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Wed Sep 19 22:56:50 2018
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2011-10-06 (2541 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.130ubuntu3.3 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1791717] [NEW] package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

[Joe Cronin]

Public bug reported:

Failed during upgrade.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: systemd-sysv 237-3ubuntu10.3
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
Date: Mon Sep 10 09:18:00 2018
ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
InstallationDate: Installed on 2015-06-19 (1179 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: systemd
Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  Failed during upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  Date: Mon Sep 10 09:18:00 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2015-06-19 (1179 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1433320] Re: systemd-journald, udev, logind crashed with SIGABRT -- get killed by 1 min watchdog timeout on longer kernel lockups

[Joe Marty]

I spoke too soon.  I'm now getting the same error in the new VM, which
was created from scratch.

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

Title:
  systemd-journald, udev, logind crashed with SIGABRT -- get killed by 1
  min watchdog timeout on longer kernel lockups

Status in apport package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Errors Bucket
  -
  
https://errors.ubuntu.com/bucket/?id=/lib/systemd/systemd-journald%3A6%3A__epoll_wait_nocancel%3Asd_event_wait%3Asd_event_run%3Amain

  
  Sometimes userspace get locked up hard: A QEMU instance sees long hangs while 
the host gets suspended, USB devices/drivers lock up for some time (like in 
this bug's dmesg), or Google hangouts in bug 1495585.
  The kernel detects that some process(es) get hard-locked up, the hardware 
watchdog (which systemd configures for some crucial services to auto-restart 
them via "WatchdogSec=1min") picks this up and restarts the process. 

  In that case, these crash reports only describe the symptom, not the
  cause. They should be suppressed since they provide no information
  that can be used to diagnose the actual root problem.


  
  ProblemType: CrashDistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-8.8-generic 3.19.1
  Uname: Linux 3.19.0-8-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  Date: Tue Mar 17 17:18:08 2015
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2014-02-24 (386 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-8-generic 
root=UUID=7f776823-8240-460b-ab2d-45c8a2b2f2b6 ro quiet splash
  Signal: 6SourcePackage: systemd
  StacktraceTop:
   __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81
   ?? ()
   ?? ()
   __libc_start_main (main=0x7f94ef54c760, argc=1, argv=0x7ffe7c6e2fa8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffe7c6e2f98) at libc-start.c:287
   ?? ()
  Title: systemd-journald crashed with SIGABRT in __epoll_wait_nocancel()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 05/20/2014
  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:bd05/20/2014: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.

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

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

[Touch-packages] [Bug 1433320] Re: systemd-journald, udev, logind crashed with SIGABRT -- get killed by 1 min watchdog timeout on longer kernel lockups

[Joe Marty]

Incidentally, I only get this bug in a virtual machine that I had
"copied" from one computer to another.  I was able to re-create the
virtual machine from scratch (using the same install image, and
installing the same software, etc) on the new computer, and did not get
the same issue in the new VM.

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

Title:
  systemd-journald, udev, logind crashed with SIGABRT -- get killed by 1
  min watchdog timeout on longer kernel lockups

Status in apport package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Errors Bucket
  -
  
https://errors.ubuntu.com/bucket/?id=/lib/systemd/systemd-journald%3A6%3A__epoll_wait_nocancel%3Asd_event_wait%3Asd_event_run%3Amain

  
  Sometimes userspace get locked up hard: A QEMU instance sees long hangs while 
the host gets suspended, USB devices/drivers lock up for some time (like in 
this bug's dmesg), or Google hangouts in bug 1495585.
  The kernel detects that some process(es) get hard-locked up, the hardware 
watchdog (which systemd configures for some crucial services to auto-restart 
them via "WatchdogSec=1min") picks this up and restarts the process. 

  In that case, these crash reports only describe the symptom, not the
  cause. They should be suppressed since they provide no information
  that can be used to diagnose the actual root problem.


  
  ProblemType: CrashDistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-8.8-generic 3.19.1
  Uname: Linux 3.19.0-8-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  Date: Tue Mar 17 17:18:08 2015
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2014-02-24 (386 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-8-generic 
root=UUID=7f776823-8240-460b-ab2d-45c8a2b2f2b6 ro quiet splash
  Signal: 6SourcePackage: systemd
  StacktraceTop:
   __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81
   ?? ()
   ?? ()
   __libc_start_main (main=0x7f94ef54c760, argc=1, argv=0x7ffe7c6e2fa8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffe7c6e2f98) at libc-start.c:287
   ?? ()
  Title: systemd-journald crashed with SIGABRT in __epoll_wait_nocancel()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 05/20/2014
  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:bd05/20/2014: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.

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

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

[Touch-packages] [Bug 1433320] Re: systemd-journald, udev, logind crashed with SIGABRT -- get killed by 1 min watchdog timeout on longer kernel lockups

[Joe Marty]

I don't know if this will help, but here's the vmware log:

** Attachment added: "VMWare log after crash and restart"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1433320/+attachment/5178236/+files/vmware.log

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

Title:
  systemd-journald, udev, logind crashed with SIGABRT -- get killed by 1
  min watchdog timeout on longer kernel lockups

Status in apport package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Errors Bucket
  -
  
https://errors.ubuntu.com/bucket/?id=/lib/systemd/systemd-journald%3A6%3A__epoll_wait_nocancel%3Asd_event_wait%3Asd_event_run%3Amain

  
  Sometimes userspace get locked up hard: A QEMU instance sees long hangs while 
the host gets suspended, USB devices/drivers lock up for some time (like in 
this bug's dmesg), or Google hangouts in bug 1495585.
  The kernel detects that some process(es) get hard-locked up, the hardware 
watchdog (which systemd configures for some crucial services to auto-restart 
them via "WatchdogSec=1min") picks this up and restarts the process. 

  In that case, these crash reports only describe the symptom, not the
  cause. They should be suppressed since they provide no information
  that can be used to diagnose the actual root problem.


  
  ProblemType: CrashDistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-8.8-generic 3.19.1
  Uname: Linux 3.19.0-8-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  Date: Tue Mar 17 17:18:08 2015
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2014-02-24 (386 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-8-generic 
root=UUID=7f776823-8240-460b-ab2d-45c8a2b2f2b6 ro quiet splash
  Signal: 6SourcePackage: systemd
  StacktraceTop:
   __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81
   ?? ()
   ?? ()
   __libc_start_main (main=0x7f94ef54c760, argc=1, argv=0x7ffe7c6e2fa8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffe7c6e2f98) at libc-start.c:287
   ?? ()
  Title: systemd-journald crashed with SIGABRT in __epoll_wait_nocancel()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 05/20/2014
  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:bd05/20/2014: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.

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

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

[Touch-packages] [Bug 1433320] Re: systemd-journald, udev, logind crashed with SIGABRT -- get killed by 1 min watchdog timeout on longer kernel lockups

[Joe Marty]

I'm having this same error occur on a new Ubuntu 18.04 VM, on VMWare
Player.  I don't understand why it was marked as "won't fix" for
systemd... ?

This is happening when I suspend my host machine (windows 10).  Upon
resuming, the VM has crashed and goes through the startup process, then
reports this error.

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

Title:
  systemd-journald, udev, logind crashed with SIGABRT -- get killed by 1
  min watchdog timeout on longer kernel lockups

Status in apport package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Errors Bucket
  -
  
https://errors.ubuntu.com/bucket/?id=/lib/systemd/systemd-journald%3A6%3A__epoll_wait_nocancel%3Asd_event_wait%3Asd_event_run%3Amain

  
  Sometimes userspace get locked up hard: A QEMU instance sees long hangs while 
the host gets suspended, USB devices/drivers lock up for some time (like in 
this bug's dmesg), or Google hangouts in bug 1495585.
  The kernel detects that some process(es) get hard-locked up, the hardware 
watchdog (which systemd configures for some crucial services to auto-restart 
them via "WatchdogSec=1min") picks this up and restarts the process. 

  In that case, these crash reports only describe the symptom, not the
  cause. They should be suppressed since they provide no information
  that can be used to diagnose the actual root problem.


  
  ProblemType: CrashDistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-8.8-generic 3.19.1
  Uname: Linux 3.19.0-8-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  Date: Tue Mar 17 17:18:08 2015
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2014-02-24 (386 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-8-generic 
root=UUID=7f776823-8240-460b-ab2d-45c8a2b2f2b6 ro quiet splash
  Signal: 6SourcePackage: systemd
  StacktraceTop:
   __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81
   ?? ()
   ?? ()
   __libc_start_main (main=0x7f94ef54c760, argc=1, argv=0x7ffe7c6e2fa8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffe7c6e2f98) at libc-start.c:287
   ?? ()
  Title: systemd-journald crashed with SIGABRT in __epoll_wait_nocancel()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 05/20/2014
  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:bd05/20/2014: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.

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

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

[Touch-packages] [Bug 1777367] Re: Output device doesn't always switch back from HDMI

[Joe Liau]

On Ubuntu 18.04 I'm still unable to switch back to the non-hdmi audio
output.

All media players still think they are using HDMI.

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

Title:
  Output device doesn't always switch back from HDMI

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When I disconnect to an HDMI output sometimes the configuration is
  left in an inconsistent state. It still shows as being connected to
  HDMI in volume up/down but there is no longer an HDMI option in the
  sound settings. After clicking the "Speakers - Built-in Audio" line in
  the Output tab of the settings (the only line available) everything is
  now correct. The same issue was also present in 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pedrocr   32004 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 17 22:54:14 2018
  InstallationDate: Installed on 2018-05-31 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET66W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FAS5TS00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460s
  dmi.product.name: 20FAS5TS00
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1745664] Re: [regression] systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_cln

[joe mammino]

Daniel - please explain what was done to resolve.

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

Title:
  [regression] systemd-logind crashed with SIGABRT in __libc_connect()
  from __GI_clnttcp_create() from __GI___libc_rpc_getport() from
  __GI_pmap_getport() from __GI_clnttcp_create()

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/54968dedd418de647365aa3f0127906ca9adbfe3

  ---

  configured system to use nis.  seems to be crashing when I attempt to
  use a NIS user account

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 235-3ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Fri Jan 26 13:45:06 2018
  ExecutablePath: /lib/systemd/systemd-logind
  InstallationDate: Installed on 2018-01-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180126)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. Z370 HD3
  ProcCmdline: /lib/systemd/systemd-logind
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __libc_connect (fd=39, addr=addr@entry=..., len=len@entry=16) at 
../sysdeps/unix/sysv/linux/connect.c:26
   __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, 
prog=prog@entry=10, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27301efc, 
sendsz=sendsz@entry=400, recvsz=recvsz@entry=400) at clnt_tcp.c:153
   __GI___libc_rpc_getport (tottimeout_sec=60, timeout_sec=5, protocol=6, 
version=2, program=17, address=0x7ffc27302060) at pm_getport.c:106
   __GI_pmap_getport (address=address@entry=0x7ffc27302060, 
program=program@entry=17, version=version@entry=2, 
protocol=protocol@entry=6) at pm_getport.c:154
   __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, 
prog=prog@entry=17, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27302050, 
sendsz=sendsz@entry=0, recvsz=recvsz@entry=0) at clnt_tcp.c:136
  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.
  Title: systemd-logind crashed with SIGABRT in __libc_connect()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: Software adm bin daemon lp mail nuucp root scswebadmin sys 
sysdesign tty uucp
  dmi.bios.date: 09/22/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: Z370 HD3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd09/22/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z370 HD3
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1778351] Re: Xorg freeze

[Joe Mau]

Did @1
@2 is enabled
@3 no /etc/gdm3/custom.conf exists
@4,5 still no crash file

-> Thanks, closeable

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Always after mid-time suspend

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-43-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Jun 23 17:51:54 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: bbswitch, 0.8, 4.13.0-43-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:837f]
 Subsystem: Hewlett-Packard Company Device [103c:8380]
  InstallationDate: Installed on 2018-02-13 (129 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: HP HP ProBook 470 G5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic.efi.signed 
root=UUID=0f2b268a-ea3c-40bf-a329-13b1447b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2017
  dmi.bios.vendor: HP
  dmi.bios.version: Q85 Ver. 01.01.07
  dmi.board.name: 837F
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 02.21.00
  dmi.chassis.asset.tag: 5CD7497QSD
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ85Ver.01.01.07:bd10/17/2017:svnHP:pnHPProBook470G5:pvr:rvnHP:rn837F:rvrKBCVersion02.21.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 470 G5
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Jun 23 17:51:31 2018
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1778351] Re: Xorg freeze

[Joe Mau]

Same as #1777021; Will try ssh

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Always after mid-time suspend

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-43-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Jun 23 17:51:54 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: bbswitch, 0.8, 4.13.0-43-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:837f]
 Subsystem: Hewlett-Packard Company Device [103c:8380]
  InstallationDate: Installed on 2018-02-13 (129 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: HP HP ProBook 470 G5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic.efi.signed 
root=UUID=0f2b268a-ea3c-40bf-a329-13b1447b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2017
  dmi.bios.vendor: HP
  dmi.bios.version: Q85 Ver. 01.01.07
  dmi.board.name: 837F
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 02.21.00
  dmi.chassis.asset.tag: 5CD7497QSD
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ85Ver.01.01.07:bd10/17/2017:svnHP:pnHPProBook470G5:pvr:rvnHP:rn837F:rvrKBCVersion02.21.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 470 G5
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Jun 23 17:51:31 2018
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1778351] [NEW] Xorg freeze

[Joe Mau]

Public bug reported:

Always after mid-time suspend

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-43-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sat Jun 23 17:51:54 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus: bbswitch, 0.8, 4.13.0-43-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Since a couple weeks or more
GraphicsCard:
 Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:837f]
   Subsystem: Hewlett-Packard Company Device [103c:8380]
InstallationDate: Installed on 2018-02-13 (129 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: HP HP ProBook 470 G5
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic.efi.signed 
root=UUID=0f2b268a-ea3c-40bf-a329-13b1447b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/17/2017
dmi.bios.vendor: HP
dmi.bios.version: Q85 Ver. 01.01.07
dmi.board.name: 837F
dmi.board.vendor: HP
dmi.board.version: KBC Version 02.21.00
dmi.chassis.asset.tag: 5CD7497QSD
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrQ85Ver.01.01.07:bd10/17/2017:svnHP:pnHPProBook470G5:pvr:rvnHP:rn837F:rvrKBCVersion02.21.00:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ProBook
dmi.product.name: HP ProBook 470 G5
dmi.sys.vendor: HP
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Sat Jun 23 17:51:31 2018
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: modeset

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


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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Always after mid-time suspend

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-43-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Jun 23 17:51:54 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: bbswitch, 0.8, 4.13.0-43-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:837f]
 Subsystem: Hewlett-Packard Company Device [103c:8380]
  InstallationDate: Installed on 2018-02-13 (129 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: HP HP ProBook 470 G5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic.efi.signed 
root=UUID=0f2b268a-ea3c-40bf-a329-13b1447b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present 

[Touch-packages] [Bug 1777021] [NEW] Xorg freeze

[Joe Mau]

Public bug reported:

Happens mostly after wakeup from hibernate

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-43-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Jun 15 03:21:59 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus: bbswitch, 0.8, 4.13.0-43-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a week
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Within the last week or two
GraphicsCard:
 Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:837f]
   Subsystem: Hewlett-Packard Company Device [103c:8380]
InstallationDate: Installed on 2018-02-13 (121 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: HP HP ProBook 470 G5
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic.efi.signed 
root=UUID=0f2b268a-ea3c-40bf-a329-13b1447b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/17/2017
dmi.bios.vendor: HP
dmi.bios.version: Q85 Ver. 01.01.07
dmi.board.name: 837F
dmi.board.vendor: HP
dmi.board.version: KBC Version 02.21.00
dmi.chassis.asset.tag: 5CD7497QSD
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrQ85Ver.01.01.07:bd10/17/2017:svnHP:pnHPProBook470G5:pvr:rvnHP:rn837F:rvrKBCVersion02.21.00:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ProBook
dmi.product.name: HP ProBook 470 G5
dmi.sys.vendor: HP
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Fri Jun 15 03:21:12 2018
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: modeset

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


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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Happens mostly after wakeup from hibernate

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-43-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jun 15 03:21:59 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: bbswitch, 0.8, 4.13.0-43-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:837f]
 Subsystem: Hewlett-Packard Company Device [103c:8380]
  InstallationDate: Installed on 2018-02-13 (121 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: HP HP ProBook 470 G5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic.efi.signed 
root=UUID=0f2b268a-ea3c-40bf-a329-13b1447b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No 

[Touch-packages] [Bug 1776680] [NEW] package linux-image-extra-4.4.0-128-generic 4.4.0-128.154 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[joe]

Public bug reported:

Description:Ubuntu 16.04.1 LTS
Release:16.04

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.4.0-128-generic 4.4.0-128.154
ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
Uname: Linux 4.4.0-128-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  hammer 1962 F pulseaudio
 /dev/snd/controlC0:  hammer 1962 F pulseaudio
Date: Wed Jun 13 12:52:07 2018
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=14ae867e-bac8-42cd-8b54-84cad8acf313
InstallationDate: Installed on 2018-06-03 (10 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Dell Inc. Latitude E6520
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-128-generic 
root=UUID=1f47ecd7-9392-426a-8b3c-1bf4eb4ffc36 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.1
SourcePackage: initramfs-tools
Title: package linux-image-extra-4.4.0-128-generic 4.4.0-128.154 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)
dmi.bios.date: 10/18/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.asset.tag: 50049724
dmi.board.name: 0J4TFW
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.asset.tag: 50049724
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6520
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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

Title:
  package linux-image-extra-4.4.0-128-generic 4.4.0-128.154 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:
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-128-generic 4.4.0-128.154
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hammer 1962 F pulseaudio
   /dev/snd/controlC0:  hammer 1962 F pulseaudio
  Date: Wed Jun 13 12:52:07 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=14ae867e-bac8-42cd-8b54-84cad8acf313
  InstallationDate: Installed on 2018-06-03 (10 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Latitude E6520
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-128-generic 
root=UUID=1f47ecd7-9392-426a-8b3c-1bf4eb4ffc36 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.1
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-128-generic 4.4.0-128.154 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)
  dmi.bios.date: 10/18/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.asset.tag: 50049724
  dmi.board.name: 0J4TFW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.asset.tag: 50049724
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1771329] Re: Can't open apps due to Too many open files

[Joe Littlejohn]

I tried the following:

echo '* hard nofile 65535' | sudo tee -a /etc/security/limits.conf
echo '* soft nofile 65535' | sudo tee -a /etc/security/limits.conf
echo 'session required pam_limits.so' | sudo tee -a /etc/pam.d/common-session

then restarted.

This did not fix the issue. So that's one 'increase limits' strategy we
can rule out - it doesn't work for this particular problem.

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

Title:
  Can't open apps due to Too many open files

Status in dbus package in Ubuntu:
  New

Bug description:
  Occasionally I find that I can't launch a new terminal, or can't
  achieve some other desktop task. Checking journalctl I see error
  messages like this:

  May 15 12:12:15 jl-XPS-13-9360 terminator.desktop[11840]:
  dbus.exceptions.DBusException:
  org.freedesktop.DBus.Error.LimitsExceeded: Failed to determine seats
  of user "1000": Too many open files

  
  or this:

  May 15 12:12:47 jl-XPS-13-9360 google-chrome.desktop[28308]:
  [28308:28343:0515/121247.966786:ERROR:bus.cc(394)] Failed to connect
  to the bus: Failed to determine seats of user "1000": Too many open
  files

  
  At the time this happen's I'm usually running Slack, Chrome, Emacs, and a few 
Java apps.

  I'm using Ubuntu Bionic (18.04), 4.15.0-20-generic x86_64, vanilla
  gnome-shell.

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

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

[Touch-packages] [Bug 1771329] Re: Can't open apps due to Too many open files

[Joe Littlejohn]

I think there's a strong argument that the default max open files for
Ubuntu Desktop should be higher than it is now. Modern apps use a lot of
file handles.

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

Title:
  Can't open apps due to Too many open files

Status in dbus package in Ubuntu:
  New

Bug description:
  Occasionally I find that I can't launch a new terminal, or can't
  achieve some other desktop task. Checking journalctl I see error
  messages like this:

  May 15 12:12:15 jl-XPS-13-9360 terminator.desktop[11840]:
  dbus.exceptions.DBusException:
  org.freedesktop.DBus.Error.LimitsExceeded: Failed to determine seats
  of user "1000": Too many open files

  
  or this:

  May 15 12:12:47 jl-XPS-13-9360 google-chrome.desktop[28308]:
  [28308:28343:0515/121247.966786:ERROR:bus.cc(394)] Failed to connect
  to the bus: Failed to determine seats of user "1000": Too many open
  files

  
  At the time this happen's I'm usually running Slack, Chrome, Emacs, and a few 
Java apps.

  I'm using Ubuntu Bionic (18.04), 4.15.0-20-generic x86_64, vanilla
  gnome-shell.

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

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

[Touch-packages] [Bug 1771329] Re: Can't open apps due to Too many open files

[Joe Littlejohn]

Thanks @dino99. I've seen a lot of different suggestions for tackling
this error, so it would be good to understand exactly which config
change is the critical one.

I think this is a major bug on a newly installed system. As an Ubuntu
Desktop user I shouldn't be experiencing an issue where the OS stops me
from launching any new app once I have a few apps open. I shouldn't need
to go hunting through logs to and start googling for a solution, then
modify open file limits, just to run a handful of desktop applications.

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

Title:
  Can't open apps due to Too many open files

Status in dbus package in Ubuntu:
  New

Bug description:
  Occasionally I find that I can't launch a new terminal, or can't
  achieve some other desktop task. Checking journalctl I see error
  messages like this:

  May 15 12:12:15 jl-XPS-13-9360 terminator.desktop[11840]:
  dbus.exceptions.DBusException:
  org.freedesktop.DBus.Error.LimitsExceeded: Failed to determine seats
  of user "1000": Too many open files

  
  or this:

  May 15 12:12:47 jl-XPS-13-9360 google-chrome.desktop[28308]:
  [28308:28343:0515/121247.966786:ERROR:bus.cc(394)] Failed to connect
  to the bus: Failed to determine seats of user "1000": Too many open
  files

  
  At the time this happen's I'm usually running Slack, Chrome, Emacs, and a few 
Java apps.

  I'm using Ubuntu Bionic (18.04), 4.15.0-20-generic x86_64, vanilla
  gnome-shell.

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

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

[Touch-packages] [Bug 1771329] [NEW] Can't open apps due to Too many open files

[Joe Littlejohn]

Public bug reported:

Occasionally I find that I can't launch a new terminal, or can't achieve
some other desktop task. Checking journalctl I see error messages like
this:

May 15 12:12:15 jl-XPS-13-9360 terminator.desktop[11840]:
dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.LimitsExceeded: Failed to determine seats of
user "1000": Too many open files


or this:

May 15 12:12:47 jl-XPS-13-9360 google-chrome.desktop[28308]:
[28308:28343:0515/121247.966786:ERROR:bus.cc(394)] Failed to connect to
the bus: Failed to determine seats of user "1000": Too many open files


At the time this happen's I'm usually running Slack, Chrome, Emacs, and a few 
Java apps.

I'm using Ubuntu Bionic (18.04), 4.15.0-20-generic x86_64, vanilla
gnome-shell.

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

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

Title:
  Can't open apps due to Too many open files

Status in dbus package in Ubuntu:
  New

Bug description:
  Occasionally I find that I can't launch a new terminal, or can't
  achieve some other desktop task. Checking journalctl I see error
  messages like this:

  May 15 12:12:15 jl-XPS-13-9360 terminator.desktop[11840]:
  dbus.exceptions.DBusException:
  org.freedesktop.DBus.Error.LimitsExceeded: Failed to determine seats
  of user "1000": Too many open files

  
  or this:

  May 15 12:12:47 jl-XPS-13-9360 google-chrome.desktop[28308]:
  [28308:28343:0515/121247.966786:ERROR:bus.cc(394)] Failed to connect
  to the bus: Failed to determine seats of user "1000": Too many open
  files

  
  At the time this happen's I'm usually running Slack, Chrome, Emacs, and a few 
Java apps.

  I'm using Ubuntu Bionic (18.04), 4.15.0-20-generic x86_64, vanilla
  gnome-shell.

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

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

[Touch-packages] [Bug 1767831] Re: package avahi-dnsconfd 0.6.32-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Joe Jepsen]

I am unable to update my system.

joe@joe-linux:~$ sudo apt-get install avahi-daemon avahi-dnsconfd avahi-utils
[sudo] password for joe: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
avahi-daemon is already the newest version (0.6.32-1ubuntu1.1).
avahi-utils is already the newest version (0.6.32-1ubuntu1.1).
The following packages will be upgraded:
  avahi-dnsconfd
1 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
Need to get 0 B/14.0 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 392091 files and directories currently installed.)
Preparing to unpack .../avahi-dnsconfd_0.6.32-1ubuntu1.1_amd64.deb ...
Job for avahi-daemon.socket canceled.
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
Job for avahi-daemon.socket canceled.
dpkg: error processing archive 
/var/cache/apt/archives/avahi-dnsconfd_0.6.32-1ubuntu1.1_amd64.deb (--unpack):
 subprocess new pre-removal script returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/avahi-dnsconfd_0.6.32-1ubuntu1.1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
joe@joe-linux:~$ sudo apt-get install avahi-daemon avahi-dnsconfd avahi-utils
Reading package lists... Done
Building dependency tree   
Reading state information... Done
avahi-daemon is already the newest version (0.6.32-1ubuntu1.1).
avahi-utils is already the newest version (0.6.32-1ubuntu1.1).
The following packages will be upgraded:
  avahi-dnsconfd
1 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
Need to get 0 B/14.0 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
(Reading database ... 392091 files and directories currently installed.)
Preparing to unpack .../avahi-dnsconfd_0.6.32-1ubuntu1.1_amd64.deb ...
Job for avahi-daemon.socket canceled.
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
Job for avahi-daemon.socket canceled.
dpkg: error processing archive 
/var/cache/apt/archives/avahi-dnsconfd_0.6.32-1ubuntu1.1_amd64.deb (--unpack):
 subprocess new pre-removal script returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/avahi-dnsconfd_0.6.32-1ubuntu1.1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


joe@joe-linux:~$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  avahi-dnsconfd libpam-systemd libsystemd0 libsystemd0:i386 libudev1 systemd
  systemd-sysv udev
8 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 4,484 kB/4,498 kB of archives.
After this operation, 10.2 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 libpam-systemd 
amd64 234-2ubuntu12.3 [111 kB]
Get:2 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 libudev1 amd64 
234-2ubuntu12.3 [52.4 kB]
Get:3 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 udev amd64 
234-2ubuntu12.3 [1,091 kB]
Get:4 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 systemd amd64 
234-2ubuntu12.3 [2,781 kB]
Get:5 http://archive.ubuntu.com/ubuntu artful-updates/main i386 libsystemd0 
i386 234-2ubuntu12.3 [227 kB]
Get:6 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 libsystemd0 
amd64 234-2ubuntu12.3 [209 kB]
Get:7 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 systemd-sysv 
amd64 234-2ubuntu12.3 [11.6 kB]
Fetched 4,484 kB in 2s (2,078 kB/s)  
(Reading database ... 392091 files and directories currently installed.)
Preparing to unpack .../libpam-systemd_234-2ubuntu12.3_amd64.deb ...
Unpacking libpam-systemd:amd64 (234-2ubuntu12.3) over (234-2ubuntu12.1) ...
Preparing to unpack .../libudev1_234-2ubuntu12.3_amd64.deb ...
Unpacking libudev1:amd64 (234-2ubuntu12.3) over (234-2ubuntu12.1) ...
Setting up libudev1:amd64 (234-2ubuntu12.3) ...
(Reading database ... 392091 files and directories currently installed.)
Preparing to unpack .../udev_234-2ubuntu12.3_amd64.deb ...
Unpacking udev (234-2ubuntu12.3) over (234-2ubuntu12.1) ...
Preparing to unpack .../systemd_234-2ubuntu12.3_amd64.deb ...
Unpacking systemd (234-2ubuntu12.3) over (234-2ubuntu12.1) ...
Preparing to unpack .../libsystemd0_234-2ubuntu12.3_amd64.deb ...
De-configuring libsystemd0:i386 (234-2ubuntu12.1) ...
Unpacking libsystemd0:amd64 (234-2ubuntu12.3) over (234-2ubuntu12.1) ...
Preparing to unpack .../libsystemd0_234-2ubuntu12.3_i386.deb ...
Unpacking libsystemd0:i386 (234-2ubuntu12.3) over (234-2ubuntu12.1) ...
Setting up libsystemd0:amd64 (234-2ubuntu12.3) ...
Setting up libsystemd0:i386 (234

[Touch-packages] [Bug 1769288] Re: indicator-datetime displays the date unnaturally in Japanese

[Joe Carey]

So, it seems the root is that Japan uses ISO dating typically, even
handwritten, and the new default uses not ISO, and there's no GUI option
to set it as such.  Not so much a bug as a design choice.

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

Title:
  indicator-datetime displays the date unnaturally in Japanese

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  The date should be (and has been in previous Ubuntu versions)
  displayed as follows (for YMD):

  2018年5月4日 (the symbols clearly mean year, month, day).

  Instead, they're displayed weirdly as "5月 4 2018" This is not the way
  a date would ever be written in Japanese. In gnome this happens on the
  lock screen as well.

  If you were writing a date without the year it would be:

  5月4日

  it doesn't make sense to leave off the 日.

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

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

[Touch-packages] [Bug 1769288] Re: indicator-datetime displays the date unnaturally in Japanese

[Joe Carey]

Hey, from https://askubuntu.com/questions/237941/how-to-configure-the-
clock-date-format-to-iso-8601-in-unity

I was able to sort this manually:

There's no easy way to do it in the GUI. One can either use dconf-editor
(which is GUI-ish), and edit two keys in
/com/canonical/indicator/datetime (time-format to custom, and custom-
time-format to the desired strftime directives, in your case %F %R (or,
equivalently, %Y-%m-%d %H:%M)), or do it directly from the terminal with
the following two commands (which, just to be clear, change the same
keys):

dconf write /com/canonical/indicator/datetime/time-format "'custom'"
dconf write /com/canonical/indicator/datetime/custom-time-format "'%F %R

I replaced %Y-%m-%d %H:%M with %Y年%m月%d日 %H:%M

However, the default remains not sane :)

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

Title:
  indicator-datetime displays the date unnaturally in Japanese

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  The date should be (and has been in previous Ubuntu versions)
  displayed as follows (for YMD):

  2018年5月4日 (the symbols clearly mean year, month, day).

  Instead, they're displayed weirdly as "5月 4 2018" This is not the way
  a date would ever be written in Japanese. In gnome this happens on the
  lock screen as well.

  If you were writing a date without the year it would be:

  5月4日

  it doesn't make sense to leave off the 日.

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

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

[Touch-packages] [Bug 1769288] [NEW] indicator-datetime displays the date unnaturally in Japanese

[Joe Carey]

Public bug reported:

The date should be (and has been in previous Ubuntu versions) displayed
as follows (for YMD):

2018年5月4日 (the symbols clearly mean year, month, day).

Instead, they're displayed weirdly as "5月 4 2018" This is not the way a
date would ever be written in Japanese. In gnome this happens on the
lock screen as well.

If you were writing a date without the year it would be:

5月4日

it doesn't make sense to leave off the 日.

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

Title:
  indicator-datetime displays the date unnaturally in Japanese

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  The date should be (and has been in previous Ubuntu versions)
  displayed as follows (for YMD):

  2018年5月4日 (the symbols clearly mean year, month, day).

  Instead, they're displayed weirdly as "5月 4 2018" This is not the way
  a date would ever be written in Japanese. In gnome this happens on the
  lock screen as well.

  If you were writing a date without the year it would be:

  5月4日

  it doesn't make sense to leave off the 日.

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

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

[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland

[Joe]

I'm experiencing this problem since months, the only "one time" fix when
it occurs I found is :

sudo sh -c 'dumpkeys |grep -v cr_Console |loadkeys'

Until the next reboot...
But it's better than nothing, right?

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

Title:
  Input falls through to gdm3 and terminates the session on Ctrl+C after
  udevadm trigger is executed under wayland

Status in Snappy:
  Won't Fix
Status in console-setup package in Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in console-setup source package in Trusty:
  New
Status in gdm3 source package in Trusty:
  New
Status in gnome-shell source package in Trusty:
  New
Status in mutter source package in Trusty:
  New
Status in systemd source package in Trusty:
  New
Status in console-setup source package in Xenial:
  New
Status in gdm3 source package in Xenial:
  New
Status in gnome-shell source package in Xenial:
  New
Status in mutter source package in Xenial:
  New
Status in systemd source package in Xenial:
  New

Bug description:
  = Test Cases =

  Test Case 1:
  - Login under Wayland (session Ubuntu)
  - Open a terminal
  - snap install gimp
  - Wait until installation finishes successfully
  - In the terminal window press CTRL+C

  Result:
  - Expected: ^C is displayed in the terminal and the prompt is at the start of 
a new line
  - Actual: The session is terminated and the login screen is displayed

  Test Case 2:
  - Login under Wayland (session Ubuntu)
  - Open a terminal and type the following command:
    $ sudo udevadm trigger
  - In the terminal window press CTRL+C

  Result
  - Expected: ^C is displayed in the terminal and the prompt is at the start of 
a new line
  - Actual: The session is terminated and the login screen is displayed

  = Original Description =

  Multiple times a day I find myself without a session after hitting
  Ctrl+C in a terminal, it seems the input falls through the
  Ubuntu/GNOME session and to gdm, which itself decides to terminate.

  Even worse, when this happens, you can briefly see your login password
  in plaintext in the virtual terminal. You can see the password however
  long you want if you stop the gdm service when this happens.

  I don't have a good way to reproduce, but it seems locking the session
  with a keyboard shortcut, subsequently unlocking it, maybe suspending,
  at some point brings this behaviour into the picture, until the
  session dies with a Ctrl+C.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.24.2-1ubuntu9
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Aug 14 15:54:34 2017
  InstallationDate: Installed on 2016-05-06 (464 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago)

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

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

[Touch-packages] [Bug 1725928] Re: package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with differing files

[Joe Ferrari]

I got it straightened out folks.  Thank you for the replies.  I had to
remove the previous version of Wine in order to install the newer
version.

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages
  with differing files

Status in sane-backends package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Confirmed
Status in sane-backends package in Debian:
  New

Bug description:
  
  From #3 comment below, to get a workaround, try:

  
  sudo apt-get -o Dpkg::Options::="--force-overwrite" install --reinstall 
libsane1:i386 (or your real package name)

  ***

  apport error this morning.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Sun Oct 22 09:37:46 2017
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-edJWJn/5-libsane1_1.0.27-1~experimental2ubuntu1_i386.deb 
(--unpack):
    trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2016-10-08 (378 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: Upgraded to artful on 2017-10-20 (1 days ago)

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

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

[Touch-packages] [Bug 569919] Re: ntpd constantly complains about being unable to create socket

[Joe Konczal]

This problem seems to be caused by a duplicate address, when another
host is trying to use the same address as the NTP server. I am using ntp
version 4.2.8p9, with two local patches applied.

In /var/log/ntp.log, the following three errors are repeated many times:

bind(20) AF_INET6 fe80::250:56ff:fe84:8834%11#123 flags 0x1 failed: Cannot 
assign requested address
unable to create socket on br1 (100384) for fe80::250:56ff:fe84:8834%11#123
failed to init interface for address fe80::250:56ff:fe84:8834%11

In /var/log/dmesg, there are a few of these:

IPv6: br1: IPv6 duplicate address fe80::250:56ff:fe84:8834 detected!

and a lot of these:

br1: received packet on tap2 with own address as source address

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

Title:
  ntpd constantly complains about being unable to create socket

Status in ntp package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: ntp

  It appears that ntpd synchronises the clock when starting, but then
  fails to continue to update the time. I've also found my syslog is
  filled with these messages from ntpd:

  Apr 25 21:11:26 nott ntpd[1121]: bind() fd 22, family 10, port 123, scope 2, 
addr fe80::230:1bff:fe80:d84b, in6_is_addr_multicast=0 flags=0x11 fails: Cannot 
assign requested address
  Apr 25 21:11:26 nott ntpd[1121]: unable to create socket on eth0 (6) for 
fe80::230:1bff:fe80:d84b#123
  Apr 25 21:11:26 nott ntpd[1121]: failed to initialize interface for address 
fe80::230:1bff:fe80:d84b
  Apr 25 21:16:26 nott ntpd[1121]: bind() fd 22, family 10, port 123, scope 2, 
addr fe80::230:1bff:fe80:d84b, in6_is_addr_multicast=0 flags=0x11 fails: Cannot 
assign requested address
  Apr 25 21:16:26 nott ntpd[1121]: unable to create socket on eth0 (7) for 
fe80::230:1bff:fe80:d84b#123
  Apr 25 21:16:26 nott ntpd[1121]: failed to initialize interface for address 
fe80::230:1bff:fe80:d84b
  Apr 25 21:21:26 nott ntpd[1121]: bind() fd 22, family 10, port 123, scope 2, 
addr fe80::230:1bff:fe80:d84b, in6_is_addr_multicast=0 flags=0x11 fails: Cannot 
assign requested address
  Apr 25 21:21:26 nott ntpd[1121]: unable to create socket on eth0 (8) for 
fe80::230:1bff:fe80:d84b#123
  Apr 25 21:21:26 nott ntpd[1121]: failed to initialize interface for address 
fe80::230:1bff:fe80:d84b
  Apr 25 21:26:26 nott ntpd[1121]: bind() fd 22, family 10, port 123, scope 2, 
addr fe80::230:1bff:fe80:d84b, in6_is_addr_multicast=0 flags=0x11 fails: Cannot 
assign requested address

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

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

[Touch-packages] [Bug 1723422] Re: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant

[joe bloggs]

Hi

I get this error when trying to run below

$gksudo bash ~/Vmware-Player-14.0.0.0-6661328.x86_64.bundle

Ideas most welcome... as right now i am back on win10 machine until i
can work out how to install player

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

Title:
  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  [Impact]

  Get that error now with each random package upgrade:

  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

  Looks like related to that change:

  * gtk2: Ambiance, Radiance: inherit style fixes from MATE themes (LP:
  #961679)

   -- Marco Trevisan (Treviño)   Thu, 12 Oct 2017
  05:19:32 +

  That installation is a default Ubuntu , no Mate installed

  [Test case]

  1. Run a gtk2 application (with ambiance/radiance set as theme) in terminal
  2. App has to run without any error

  [Possible regression]

  Different scrollbars in gtk2 apps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20171012.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct 13 14:52:43 2017
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses

[Joe Liau]

This is still an issue in Ubuntu 17.10

Though it seems to fix if  you restart NetworkManager first before
connecting to the VPN.

sudo service NetworkManager restart

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

Title:
  network manager openvpn dns push data not updating system DNS
  addresses

Status in network-manager package in Ubuntu:
  Confirmed
Status in openvpn package in Ubuntu:
  Confirmed

Bug description:
  [Triage Notes]

  Apparently fixed on Ubuntu 17.04, nobody caring about LTS versions.
  Please see wall of text on comment 50 for a long excuse.

  [Original Description]

  When IPv4 Method is set to Automatic VPN, DNS address recieved from
  OpenVPN server do not update resolv.conf.

  This can be achieved when using a standard openvpn config file by
  adding the lines:

  script-security 2
  up /etc/openvpn/update-resolv-conf
  down /etc/openvpn/update-resolv-conf

  In Network-manager there seems to be no option to run connection
  specific scripts and the DNS data from the server is ignored.

  Ubuntu 13.04
  Network-manager 0.9.8.0-0ubuntu6

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

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

[Touch-packages] [Bug 1111882] Re: GnuTLS recv error (-9): A TLS packet with unexpected length was received

[Joe Damato]

OpenSSL was recently relicensed:
https://www.openssl.org/blog/blog/2017/03/22/license/. I'm not a lawyer,
but it would be nice to get one to weigh in on how this affects the
legal issues mentioned.

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

Title:
  GnuTLS recv error (-9): A TLS packet with unexpected length was
  received

Status in apt package in Ubuntu:
  Invalid
Status in curl package in Ubuntu:
  Invalid
Status in git package in Ubuntu:
  Confirmed
Status in gnutls26 package in Ubuntu:
  Confirmed

Bug description:
  On Precise 12.04 whilst attempting:

  GIT_CURL_VERBOSE=1 git clone -v https://git01.codeplex.com/typescript

  the operation fails after the final git pack-file has been received
  and the already-created repository is deleted from the file system.

  ...
  > POST /typescript/git-upload-pack HTTP/1.1
  User-Agent: git/1.8.1.2.433.g9808ce0.dirty
  Host: git01.codeplex.com
  Accept-Encoding: gzip
  Content-Type: application/x-git-upload-pack-request
  Accept: application/x-git-upload-pack-result
  Content-Length: 611

  * upload completely sent off: 611out of 611 bytes
  < HTTP/1.1 200 OK
  < Cache-Control: no-cache, max-age=0, must-revalidate
  < Pragma: no-cache
  < Content-Type: application/x-git-upload-pack-result
  < Expires: Fri, 01 Jan 1980 00:00:00 GMT
  < Server: Microsoft-IIS/7.5
  < X-Powered-By: ASP.NET
  < Date: Thu, 31 Jan 2013 21:43:55 GMT
  < Connection: close
  < 
  remote: Counting objects: 149766, done.
  remote: Compressing objects: 100% (10580/10580), done.
  * GnuTLS recv error (-9): A TLS packet with unexpected length was received.
  * Closing connection #0
  remote: Total 149766 (delta 138201), reused 149559 (delta 138077)
  Receiving objects: 100% (149766/149766), 198.98 MiB | 361 KiB/s, done.
  error: RPC failed; result=56, HTTP code = 200
  Resolving deltas: 100% (138201/138201), done.

  git exits at this point but it deletes the entire cloned ./typescript
  directory.

  I tried building the latest git binary and included an additional
  debug option in "http.c" that allowed me to set the protocol version
  using an environment option:

  CURLOPT_SSLVERSION=1 git clone ...

  where 1 = TLSv1, 2 = SSLv2, 3 = SSLv3.

  I tried each protocol but the result was the same.

  The knock-on bug here is that git ought not to delete what it has
  fetched - in this case more than 250MB of data.

  I did try to build the latest gnutls but it needs a very recent
  version of libnettle which has the "rsa_decrypt_tr" function. I
  stopped at that point since I don't want to get into dependency and
  library version issues.

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

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

[Touch-packages] [Bug 1111882] Re: GnuTLS recv error (-9): A TLS packet with unexpected length was received

[Joe Damato]

I've changed the status for APT back to "Confirmed" - I've seen many
cases of this bug reported. I don't follow the comment about legal
reasons (#17). Ubuntu already ships apt-transport-https, which links
against gnutls and suffers from this bug; no new code causing any new
legal issues would be pulled in. Fixing this bug in gnutls would also
fix it in apt-transport-https, so IMO, APT is affected by this bug just
the same as git and curl.

** Changed in: apt (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  GnuTLS recv error (-9): A TLS packet with unexpected length was
  received

Status in apt package in Ubuntu:
  Confirmed
Status in curl package in Ubuntu:
  Confirmed
Status in git package in Ubuntu:
  Confirmed
Status in gnutls26 package in Ubuntu:
  Confirmed

Bug description:
  On Precise 12.04 whilst attempting:

  GIT_CURL_VERBOSE=1 git clone -v https://git01.codeplex.com/typescript

  the operation fails after the final git pack-file has been received
  and the already-created repository is deleted from the file system.

  ...
  > POST /typescript/git-upload-pack HTTP/1.1
  User-Agent: git/1.8.1.2.433.g9808ce0.dirty
  Host: git01.codeplex.com
  Accept-Encoding: gzip
  Content-Type: application/x-git-upload-pack-request
  Accept: application/x-git-upload-pack-result
  Content-Length: 611

  * upload completely sent off: 611out of 611 bytes
  < HTTP/1.1 200 OK
  < Cache-Control: no-cache, max-age=0, must-revalidate
  < Pragma: no-cache
  < Content-Type: application/x-git-upload-pack-result
  < Expires: Fri, 01 Jan 1980 00:00:00 GMT
  < Server: Microsoft-IIS/7.5
  < X-Powered-By: ASP.NET
  < Date: Thu, 31 Jan 2013 21:43:55 GMT
  < Connection: close
  < 
  remote: Counting objects: 149766, done.
  remote: Compressing objects: 100% (10580/10580), done.
  * GnuTLS recv error (-9): A TLS packet with unexpected length was received.
  * Closing connection #0
  remote: Total 149766 (delta 138201), reused 149559 (delta 138077)
  Receiving objects: 100% (149766/149766), 198.98 MiB | 361 KiB/s, done.
  error: RPC failed; result=56, HTTP code = 200
  Resolving deltas: 100% (138201/138201), done.

  git exits at this point but it deletes the entire cloned ./typescript
  directory.

  I tried building the latest git binary and included an additional
  debug option in "http.c" that allowed me to set the protocol version
  using an environment option:

  CURLOPT_SSLVERSION=1 git clone ...

  where 1 = TLSv1, 2 = SSLv2, 3 = SSLv3.

  I tried each protocol but the result was the same.

  The knock-on bug here is that git ought not to delete what it has
  fetched - in this case more than 250MB of data.

  I did try to build the latest gnutls but it needs a very recent
  version of libnettle which has the "rsa_decrypt_tr" function. I
  stopped at that point since I don't want to get into dependency and
  library version issues.

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

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

[Touch-packages] [Bug 1638695] Re: Python 2.7.12 performance regression

[Joe Gordon]

Any updates on this? Are there plans to release a faster python build
for Xenial?

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

Title:
  Python 2.7.12 performance regression

Status in python2.7 package in Ubuntu:
  Confirmed

Bug description:
  I work on the OpenStack-Ansible project and we've noticed that testing
  jobs on 16.04 take quite a bit longer to complete than on 14.04.  They
  complete within an hour on 14.04 but they normally take 90 minutes or
  more on 16.04.  We use the same version of Ansible with both versions
  of Ubuntu.

  After more digging, I tested python performance (using the
  'performance' module) on 14.04 (2.7.6) and on 16.04 (2.7.12).  There
  is a significant performance difference between each version of
  python.  That is detailed in a spreadsheet[0].

  I began using perf to dig into the differences when running the python
  performance module and when using Ansible playbooks.  CPU migrations
  (as measured by perf) are doubled in Ubuntu 16.04 when running the
  same python workloads.

  I tried changing some of the kerne.sched sysctl configurables but they
  had very little effect on the results.

  I compiled python 2.7.12 from source on 14.04 and found the
  performance to be unchanged there.  I'm not entirely sure where the
  problem might be now.

  We also have a bug open in OpenStack-Ansible[1] that provides
  additional detail. Thanks in advance for any help you can provide!

  [0] 
https://docs.google.com/spreadsheets/d/18MmptS_DAd1YP3OhHWQqLYVA9spC3xLt4PS3STI6tds/edit?usp=sharing
  [1] https://bugs.launchpad.net/openstack-ansible/+bug/1637494

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+subscriptions

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

[Touch-packages] [Bug 1697552] [NEW] Can't login to Unity - get in a loop back to login screen

[Joe Spurlock]

Public bug reported:

"Could not acquire name on session bus" at Unity login screen and get in
a loop back to the login screen if (correctly) entering user password
(admin level account).

Can seem to log into the MATE desktop.However when Logged into MATE
desktop there is no Terminal avaialble.

Can navigate to the command line at the Unity login screen but do not
know what to do to correct the login issue with Unity.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Jun 12 17:01:41 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Xeon E3-1200 v2/3rd Gen Core processor 
Graphics Controller [103c:3398]
InstallationDate: Installed on 2017-06-09 (3 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: Hewlett-Packard HP Compaq Elite 8300 USDT
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed 
root=UUID=ea35e559-442e-4ec2-b12a-6659b4317e63 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/05/2016
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: K01 v03.04
dmi.board.asset.tag: MXL2481GVF
dmi.board.name: 3398
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: MXL2481GVF
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v03.04:bd10/05/2016:svnHewlett-Packard:pnHPCompaqElite8300USDT:pvr:rvnHewlett-Packard:rn3398:rvr:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: HP Compaq Elite 8300 USDT
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
xserver.bootTime: Mon Jun 12 16:54:09 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug ubuntu zesty

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

Title:
  Can't login to Unity - get in a loop back to login screen

Status in xorg package in Ubuntu:
  New

Bug description:
  "Could not acquire name on session bus" at Unity login screen and get
  in a loop back to the login screen if (correctly) entering user
  password (admin level account).

  Can seem to log into the MATE desktop.However when Logged into
  MATE desktop there is no Terminal avaialble.

  Can navigate to the command line at the Unity login screen but do not
  know what to do to correct the login issue with Unity.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Jun 12 17:01:41 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Xeon E3-1200 v2/3rd Gen Core processor 
Graphics Controller [103c:3398]
  InstallationDate: Installed on 2017-06-09 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Hewlett-Packard HP Compaq Elite 8300 USDT
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no 

[Touch-packages] [Bug 1546603] Re: Bluetooth mouse connects but doesn't work ("Unable to register GATT service")

[Joe Barnett]

the workaround works.  i haven't tried newer version w/out the
workaround.

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

Title:
  Bluetooth mouse connects but doesn't work ("Unable to register GATT
  service")

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I have a bluetooth mouse that I can get to connect via the gnome
  bluetooth settings panel, but even after it's connected it doesn't
  move the pointer or register any clicks.

  the following shows up in the journal :

  $ $ journalctl -b 0 |grep bluetooth
  Feb 17 07:18:22 spiny bluetoothd[1009]: Bluetooth daemon 5.36
  Feb 17 07:18:22 spiny bluetoothd[1009]: Starting SDP server
  Feb 17 07:18:22 spiny bluetoothd[1009]: Bluetooth management interface 1.10 
initialized
  Feb 17 07:18:22 spiny bluetoothd[1009]: Failed to obtain handles for "Service 
Changed" characteristic
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Error adding Link Loss service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Current Time Service could not be 
registered
  Feb 17 07:18:22 spiny bluetoothd[1009]: gatt-time-server: Input/output error 
(5)
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Sap driver initialization failed.
  Feb 17 07:18:22 spiny bluetoothd[1009]: sap-server: Operation not permitted 
(1)
  Feb 17 07:18:22 spiny NetworkManager[1062]:   Loaded device plugin: 
NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
  Feb 17 07:18:24 spiny bluetoothd[1009]: Endpoint registered: sender=:1.42 
path=/MediaEndpoint/A2DPSource
  Feb 17 07:18:24 spiny bluetoothd[1009]: Endpoint registered: sender=:1.42 
path=/MediaEndpoint/A2DPSink
  Feb 17 07:18:42 spiny bluetoothd[1009]: Endpoint registered: sender=:1.71 
path=/MediaEndpoint/A2DPSource
  Feb 17 07:18:42 spiny bluetoothd[1009]: Endpoint registered: sender=:1.71 
path=/MediaEndpoint/A2DPSink
  Feb 17 07:18:42 spiny bluetoothd[1009]: RFCOMM server failed for Headset 
Voice gateway: rfcomm_bind: Address already in use (98)
  Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** 
(gnome-control-center.real:2717): WARNING **: Ignoring launcher gufw (missing 
desktop file)
  Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** 
(gnome-control-center.real:2717): WARNING **: Ignoring launcher 
landscape-client-settings (missing desktop file)
  Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** 
(gnome-control-center.real:2717): WARNING **: Ignoring launcher 
language-selector (missing desktop file)
  Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** 
(gnome-control-center.real:2717): WARNING **: Ignoring launcher 
ubuntuone-installer (missing desktop file)
  Feb 17 07:19:00 spiny gnome-bluetooth-panel.desktop[2717]: 
(gnome-control-center.real:2717): GLib-CRITICAL **: g_ascii_strdown: assertion 
'str != NULL' failed
  Feb 17 07:19:01 spiny bluetoothd[1009]: No cache for F2:3F:5C:A1:F9:F7
  Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with 
handle 0x000c for device F2:3F:5C:A1:F9:F7
  Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with 
handle 0x001b for device F2:3F:5C:A1:F9:F7
  Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with 
handle 0x003f for device F2:3F:5C:A1:F9:F7
  Feb 17 07:19:06 spiny bluetoothd[1009]: Report Map read failed: Attribute 
requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: Protocol Mode characteristic read 
failed: Attribute requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: HID Information read failed: 
Attribute requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor 
failed: Attribute requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor 
failed: Attribute requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor 
failed: Attribute requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor 
failed: Attribute requires authentication before read/write
  Feb 17 07:19:08 spiny gnome-bluetooth-panel.desktop[2717]: 
(gnome-control-center.real:2717): GLib-CRITICAL **: g_ascii_strdown: assertion 
'str 

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Joe Liau]

Confirmed that is still an issue on 17.04.

Comment #20 doesn't work, as that line does not exist.

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

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

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Confirmed

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

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

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

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

[Touch-packages] [Bug 1653377] Re: Web form auto fills previous field data

[Joe Liau]

Hello, the problem seems to have resolved in more recent builds (r607).

But, at the time the problem persisted regardless of the website, and on
default settings:

-English (united states)
- Spell checking on
- Auto correction OFF
- Word suggestion on
- Auto capitalization On
- Auto puctuation On
- Keyboard sound OFF 
- Keyboard vibration ON

Steps to reproduce:
- Navigate to any web form (I think I was filling out a paypal form at the 
time).
- Fill in first field
- Fill in second field <-- first field info appears in front of newly entered 
information

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

Title:
  Web form auto fills previous field data

Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04 r604
  rc proposed
  Mako

  When filling in web forms, previous field data gets automatically
  inputed into the next field when typing.

  e.g. After input of first name, when entering last name, the first
  name will show up in the field.

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

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

[Touch-packages] [Bug 1658130] [NEW] contact names disappear / not displayed in pre-existing messaging conversations

[Joe Liau]

Public bug reported:

Mako
Rc-proposed

See attached screenshot. Contact names disappear from the messaging
conversation; only phone numbers are displayed.

This seems to happen when the app/system crashes. The problem tends to
resolve with a reboot.

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

** Attachment added: "screenshot20170120_071548176.png"
   
https://bugs.launchpad.net/bugs/1658130/+attachment/4806823/+files/screenshot20170120_071548176.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/1658130

Title:
  contact names disappear / not displayed in pre-existing messaging
  conversations

Status in messaging-app package in Ubuntu:
  New

Bug description:
  Mako
  Rc-proposed

  See attached screenshot. Contact names disappear from the messaging
  conversation; only phone numbers are displayed.

  This seems to happen when the app/system crashes. The problem tends to
  resolve with a reboot.

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

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

[Touch-packages] [Bug 1653554] [NEW] Unread messages counter requires viewing actual message before decrementing

[Joe Liau]

Public bug reported:

Mako
Rc-proposed

Issue:
Viewing and responding to message from quick settings doesn't mark message as 
read.
Furthermore, if viewing message in messaging app, you must scroll up to that 
message in order to decrement the unread message counter.

This feature makes a lot of sense as is, but some people send flurries
of messages and it is often that some messages get pushed up beyond
conviences of viewing them. As a result, there is always an inread
message counter.

A few things could be considered:
- mark message(s) read if replied to from quick settings
- mark all messages read when conversation is opened in messaging app*
-* option to mark all messages as read or jump to the oldest unread message

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

Title:
  Unread messages counter requires viewing actual message before
  decrementing

Status in messaging-app package in Ubuntu:
  New

Bug description:
  Mako
  Rc-proposed

  Issue:
  Viewing and responding to message from quick settings doesn't mark message as 
read.
  Furthermore, if viewing message in messaging app, you must scroll up to that 
message in order to decrement the unread message counter.

  This feature makes a lot of sense as is, but some people send flurries
  of messages and it is often that some messages get pushed up beyond
  conviences of viewing them. As a result, there is always an inread
  message counter.

  A few things could be considered:
  - mark message(s) read if replied to from quick settings
  - mark all messages read when conversation is opened in messaging app*
  -* option to mark all messages as read or jump to the oldest unread message

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

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

[Touch-packages] [Bug 1653377] [NEW] Web form auto fills previous field data

[Joe Liau]

Public bug reported:

Ubuntu 16.04 r604
rc proposed
Mako

When filling in web forms, previous field data gets automatically
inputed into the next field when typing.

e.g. After input of first name, when entering last name, the first name
will show up in the field.

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

** Attachment added: "screenshot20161231_112450415.png"
   
https://bugs.launchpad.net/bugs/1653377/+attachment/4798605/+files/screenshot20161231_112450415.png

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

Title:
  Web form auto fills previous field data

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 r604
  rc proposed
  Mako

  When filling in web forms, previous field data gets automatically
  inputed into the next field when typing.

  e.g. After input of first name, when entering last name, the first
  name will show up in the field.

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

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

[Touch-packages] [Bug 1646178] [NEW] video problems

[joe]

Public bug reported:

Running 16.04, after update, new Nvidia driver (304.132) caused login
loop - resorted to nouveau driver and have arbitrary crashes and weird
boot issues. Have not been able to reinstall old Nvidia (304.131).  Have
been checking the forum and see similar problems, nothing seems to work.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
Uname: Linux 4.4.0-51-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Nov 30 11:19:56 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company C61 [GeForce 6150SE nForce 430] 
[103c:2a58]
InstallationDate: Installed on 2013-01-01 (1428 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
Lsusb:
 Bus 001 Device 003: ID 0bda:0111 Realtek Semiconductor Corp. RTS5111 Card 
Reader Controller
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 04fc:05d8 Sunplus Technology Co., Ltd Wireless 
keyboard/mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: HP-Pavilion GX614AA-ABA a6330f
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-51-generic 
root=UUID=1ede16fa-23c2-4f4d-8b28-b9318d2ff433 ro splash quiet
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/29/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 5.13
dmi.board.name: NARRA2
dmi.board.vendor: ASUSTek Computer INC.
dmi.board.version: 2.00
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.13:bd10/29/2007:svnHP-Pavilion:pnGX614AA-ABAa6330f:pvr:rvnASUSTekComputerINC.:rnNARRA2:rvr2.00:cvnHewlett-Packard:ct3:cvrChassisVersion:
dmi.product.name: GX614AA-ABA a6330f
dmi.sys.vendor: HP-Pavilion
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed Nov 30 10:40:59 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputMLK wireless combo   KEYBOARD, id 8
 inputMLK wireless combo   KEYBOARD, id 9
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: amd64 apport-bug compiz-0.9 possible-manual-nvidia-install ubuntu 
xenial

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

Title:
  video problems

Status in xorg package in Ubuntu:
  New

Bug description:
  Running 16.04, after update, new Nvidia driver (304.132) caused login
  loop - resorted to nouveau driver and have arbitrary crashes and weird
  boot issues. Have not been able to reinstall old Nvidia (304.131).
  Have been checking the forum and see similar problems, nothing seems
  to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Uname: Linux 4.4.0-51-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Nov 30 11:19:56 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])

[Touch-packages] [Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

[Joe Giampaoli]

I can confirm same results:

HP G240
Xubuntu 16.04 64bit

Uncommented and changed HandleLidSwitchDocked=ignore to
HandleLidSwitchDocked=suspend in /etc/systemd/logind.conf worked

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

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

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

[Touch-packages] [Bug 971018] Re: Auto-hide Unity Launcher will not reveal when mouse pushed to left side in VirtualBox or VMware

[Tuxedo Joe]

I've found that setting:

- Reveal location: Left side
- Reveal sensitivity: Highest

works pretty good. Sometimes you'll have to move the cursor twice to the
side/bottom though.

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

Title:
  Auto-hide Unity Launcher will not reveal when mouse pushed to left
  side in VirtualBox or VMware

Status in Unity:
  Opinion
Status in libxfixes package in Ubuntu:
  Incomplete
Status in unity package in Ubuntu:
  Opinion
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Precise 12.04 Beta 2 AMD64 DVD:
   
   
  I am running Ubuntu Precise 12.04 Beta 2 in a VirtualBox 4.1.8 session.  
VirtualBox Guest Additions have been installed via "jockey-gtk" from the Ubuntu 
Precise repository, and Unity is running in 3D mode with Compiz.
   
   
  When the Unity Launcher is set to "autohide," the Launcher will never reveal 
when the mouse pointer is moved to the left edge of the screen.  It does not 
matter how much "pressure" is applied; the Launcher never appears.
   
   
  I have tried the following VirtualBox window "form-factors," all with the 
same result (the Launcher never appears):
   
  -- VirtualBox session running in a non-maximized window
  -- VirtualBox session running in a maximized window
  -- VirtualBox session running full-screen
   
   
  I have attached a screen capture (OGV) with Ubuntu Precise running in a 
maximized VirtualBox window.
   
   
  Note:  This Bug may be related to the following other Bugs reported on 
LaunchPad:
   
  -- Bug 965643:  Unity 5.8: auto-hide using mouse reveals launcher 
inconsistently
  -- -- https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/965643

  -- Bug 923749:  New "push mouse offscreen" feature really difficult to get
  -- -- https://bugs.launchpad.net/unity/+bug/923749

  -- Bug 937792:  Left launcher does not revel when in autohide mode on 
multi-monitor setups
  -- -- https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/937792

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
  Uname: Linux 3.2.0-21-generic x86_64
  ApportVersion: 2.0-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Sun Apr  1 14:46:23 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
  ProcEnviron:
   TERM=xterm
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 971018] Re: Auto-hide Unity Launcher will not reveal when mouse pushed to left side in VirtualBox or VMware

[Tuxedo Joe]

I found that setting:

- Reveal location: Left side
- Reveal sensitivity: Highest

works pretty good. Sometimes you'll have to go there twice though.

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

Title:
  Auto-hide Unity Launcher will not reveal when mouse pushed to left
  side in VirtualBox or VMware

Status in Unity:
  Opinion
Status in libxfixes package in Ubuntu:
  Incomplete
Status in unity package in Ubuntu:
  Opinion
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Precise 12.04 Beta 2 AMD64 DVD:
   
   
  I am running Ubuntu Precise 12.04 Beta 2 in a VirtualBox 4.1.8 session.  
VirtualBox Guest Additions have been installed via "jockey-gtk" from the Ubuntu 
Precise repository, and Unity is running in 3D mode with Compiz.
   
   
  When the Unity Launcher is set to "autohide," the Launcher will never reveal 
when the mouse pointer is moved to the left edge of the screen.  It does not 
matter how much "pressure" is applied; the Launcher never appears.
   
   
  I have tried the following VirtualBox window "form-factors," all with the 
same result (the Launcher never appears):
   
  -- VirtualBox session running in a non-maximized window
  -- VirtualBox session running in a maximized window
  -- VirtualBox session running full-screen
   
   
  I have attached a screen capture (OGV) with Ubuntu Precise running in a 
maximized VirtualBox window.
   
   
  Note:  This Bug may be related to the following other Bugs reported on 
LaunchPad:
   
  -- Bug 965643:  Unity 5.8: auto-hide using mouse reveals launcher 
inconsistently
  -- -- https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/965643

  -- Bug 923749:  New "push mouse offscreen" feature really difficult to get
  -- -- https://bugs.launchpad.net/unity/+bug/923749

  -- Bug 937792:  Left launcher does not revel when in autohide mode on 
multi-monitor setups
  -- -- https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/937792

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
  Uname: Linux 3.2.0-21-generic x86_64
  ApportVersion: 2.0-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Sun Apr  1 14:46:23 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
  ProcEnviron:
   TERM=xterm
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1111882] Re: GnuTLS recv error (-9): A TLS packet with unexpected length was received

[Joe Damato]

This bug in gnutls also affects users of apt-transport-https which is
used by APT for accessing repositories via TLS. Fixing this bug would be
a great help for SSL-enabled APT repositories.

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

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

Title:
  GnuTLS recv error (-9): A TLS packet with unexpected length was
  received

Status in apt package in Ubuntu:
  New
Status in curl package in Ubuntu:
  Confirmed
Status in git package in Ubuntu:
  Confirmed
Status in gnutls26 package in Ubuntu:
  Confirmed

Bug description:
  On Precise 12.04 whilst attempting:

  GIT_CURL_VERBOSE=1 git clone -v https://git01.codeplex.com/typescript

  the operation fails after the final git pack-file has been received
  and the already-created repository is deleted from the file system.

  ...
  > POST /typescript/git-upload-pack HTTP/1.1
  User-Agent: git/1.8.1.2.433.g9808ce0.dirty
  Host: git01.codeplex.com
  Accept-Encoding: gzip
  Content-Type: application/x-git-upload-pack-request
  Accept: application/x-git-upload-pack-result
  Content-Length: 611

  * upload completely sent off: 611out of 611 bytes
  < HTTP/1.1 200 OK
  < Cache-Control: no-cache, max-age=0, must-revalidate
  < Pragma: no-cache
  < Content-Type: application/x-git-upload-pack-result
  < Expires: Fri, 01 Jan 1980 00:00:00 GMT
  < Server: Microsoft-IIS/7.5
  < X-Powered-By: ASP.NET
  < Date: Thu, 31 Jan 2013 21:43:55 GMT
  < Connection: close
  < 
  remote: Counting objects: 149766, done.
  remote: Compressing objects: 100% (10580/10580), done.
  * GnuTLS recv error (-9): A TLS packet with unexpected length was received.
  * Closing connection #0
  remote: Total 149766 (delta 138201), reused 149559 (delta 138077)
  Receiving objects: 100% (149766/149766), 198.98 MiB | 361 KiB/s, done.
  error: RPC failed; result=56, HTTP code = 200
  Resolving deltas: 100% (138201/138201), done.

  git exits at this point but it deletes the entire cloned ./typescript
  directory.

  I tried building the latest git binary and included an additional
  debug option in "http.c" that allowed me to set the protocol version
  using an environment option:

  CURLOPT_SSLVERSION=1 git clone ...

  where 1 = TLSv1, 2 = SSLv2, 3 = SSLv3.

  I tried each protocol but the result was the same.

  The knock-on bug here is that git ought not to delete what it has
  fetched - in this case more than 250MB of data.

  I did try to build the latest gnutls but it needs a very recent
  version of libnettle which has the "rsa_decrypt_tr" function. I
  stopped at that point since I don't want to get into dependency and
  library version issues.

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

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

[Touch-packages] [Bug 1629620] Re: DNS resolver stops accepting queries

[Joe Barnett]

this seems to be less of a problem after switching /etc/resolv.conf to
point to the systemd-resolved managed file instead of the resolvconf
managed file.  not sure exactly which package should be changed to have
this work automatically?

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

Title:
  DNS resolver stops accepting queries

Status in network-manager package in Ubuntu:
  New

Bug description:
  After a while / after resume from suspend, the system becomes unable
  to respond to DNS queries, with the following output for example:

  $ nslookup google.com 127.0.1.1
  Server:   127.0.1.1
  Address:  127.0.1.1#53

  ** server can't find google.com: REFUSED

  
  This is on an up to date yakkety install.  Changing resolv.conf to use 
8.8.8.8, or restarting network-manager appears to fix this, at least until it 
recurs again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Oct  1 21:28:51 2016
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-08-21 (407 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  IpRoute:
   default via 192.168.1.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.1.5  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to yakkety on 2016-09-29 (2 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION   CON-UUID  CON-PATH
   
   docker0bridgeconnected 
/org/freedesktop/NetworkManager/Devices/1  docker0  
63f0b05b-f699-4a68-81ce-f62d2c1a247d  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   wlp3s0 wifi  connected 
/org/freedesktop/NetworkManager/Devices/4  HOME-1622-5  
6df3f2f0-fb86-43b5-802a-d59bc5734be3  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   24:DA:9B:B9:09:0E  btdisconnected  
/org/freedesktop/NetworkManager/Devices/3  --   --  
  -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/2  --   --  
  --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1631980] Re: Steam not able to see network in yakkety

[Joe Barnett]

possibly caused by switch to systemd-resolved?

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

Title:
  Steam not able to see network in yakkety

Status in steam package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Steam is unable to see the network in yakkety.  Downloads stall and
  don't do anything; and trying to update steam results in a "Fatal
  Error: Steam needs to be online to update.  Please confirm your
  network connection and try again" dialog box.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: steam:i386 1:1.0.0.52-5ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 10 07:43:55 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-08-21 (416 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  PackageArchitecture: i386
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: steam
  UpgradeStatus: Upgraded to yakkety on 2016-09-29 (10 days ago)

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

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

[Touch-packages] [Bug 1631980] [NEW] Steam not able to see network in yakkety

[Joe Barnett]

Public bug reported:

Steam is unable to see the network in yakkety.  Downloads stall and
don't do anything; and trying to update steam results in a "Fatal Error:
Steam needs to be online to update.  Please confirm your network
connection and try again" dialog box.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: steam:i386 1:1.0.0.52-5ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
Uname: Linux 4.8.0-21-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Oct 10 07:43:55 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-08-21 (416 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
PackageArchitecture: i386
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: steam
UpgradeStatus: Upgraded to yakkety on 2016-09-29 (10 days ago)

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

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


** Tags: apport-bug i386 yakkety

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

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

Title:
  Steam not able to see network in yakkety

Status in steam package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Steam is unable to see the network in yakkety.  Downloads stall and
  don't do anything; and trying to update steam results in a "Fatal
  Error: Steam needs to be online to update.  Please confirm your
  network connection and try again" dialog box.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: steam:i386 1:1.0.0.52-5ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 10 07:43:55 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-08-21 (416 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  PackageArchitecture: i386
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: steam
  UpgradeStatus: Upgraded to yakkety on 2016-09-29 (10 days ago)

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

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

[Touch-packages] [Bug 1629620] [NEW] DNS resolver stops accepting queries

[Joe Barnett]

Public bug reported:

After a while / after resume from suspend, the system becomes unable to
respond to DNS queries, with the following output for example:

$ nslookup google.com 127.0.1.1
Server: 127.0.1.1
Address:127.0.1.1#53

** server can't find google.com: REFUSED


This is on an up to date yakkety install.  Changing resolv.conf to use 8.8.8.8, 
or restarting network-manager appears to fix this, at least until it recurs 
again.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: network-manager 1.2.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
Uname: Linux 4.8.0-17-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Oct  1 21:28:51 2016
EcryptfsInUse: Yes
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2015-08-21 (407 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
IpRoute:
 default via 192.168.1.1 dev wlp3s0  proto static  metric 600 
 169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
 172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
 192.168.1.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.1.5  metric 
600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: Upgraded to yakkety on 2016-09-29 (2 days ago)
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   CONNECTION   CON-UUID  CON-PATH  
 
 docker0bridgeconnected 
/org/freedesktop/NetworkManager/Devices/1  docker0  
63f0b05b-f699-4a68-81ce-f62d2c1a247d  
/org/freedesktop/NetworkManager/ActiveConnection/0 
 wlp3s0 wifi  connected 
/org/freedesktop/NetworkManager/Devices/4  HOME-1622-5  
6df3f2f0-fb86-43b5-802a-d59bc5734be3  
/org/freedesktop/NetworkManager/ActiveConnection/2 
 24:DA:9B:B9:09:0E  btdisconnected  
/org/freedesktop/NetworkManager/Devices/3  --   --  
  -- 
 lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/2  --   --  
  --
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug yakkety

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

Title:
  DNS resolver stops accepting queries

Status in network-manager package in Ubuntu:
  New

Bug description:
  After a while / after resume from suspend, the system becomes unable
  to respond to DNS queries, with the following output for example:

  $ nslookup google.com 127.0.1.1
  Server:   127.0.1.1
  Address:  127.0.1.1#53

  ** server can't find google.com: REFUSED

  
  This is on an up to date yakkety install.  Changing resolv.conf to use 
8.8.8.8, or restarting network-manager appears to fix this, at least until it 
recurs again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Oct  1 21:28:51 2016
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-08-21 (407 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  IpRoute:
   default via 192.168.1.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.1.5  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to yakkety on 2016-09-29 (2 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION   CON-UUID   

[Touch-packages] [Bug 1629498] [NEW] [HDA-Intel - HDA Intel, playback] No sound at all

[Joe Nobles]

Public bug reported:

this happened after I upgraded to ubuntu 16.04

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  joe1731 F pulseaudio
CurrentDesktop: X-Cinnamon
Date: Fri Sep 30 20:51:14 2016
InstallationDate: Installed on 2015-10-02 (364 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
Symptom_Card: Built-in Audio - HDA Intel
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  joe1731 F pulseaudio
Symptom_Type: No sound at all
Title: [HDA-Intel - HDA Intel, playback] No sound at all
UpgradeStatus: Upgraded to xenial on 2016-09-19 (12 days ago)
dmi.bios.date: 07/30/2010
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V1.60
dmi.board.name: PAV10 DDR2
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.00
dmi.chassis.asset.tag: *
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.60:bd07/30/2010:svnTOSHIBA:pnTOSHIBANB255:pvrPLL2PU-00901L:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: TOSHIBA NB255
dmi.product.version: PLL2PU-00901L
dmi.sys.vendor: TOSHIBA

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


** Tags: apport-bug i386 xenial

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

Title:
  [HDA-Intel - HDA Intel, playback] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  this happened after I upgraded to ubuntu 16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joe1731 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Fri Sep 30 20:51:14 2016
  InstallationDate: Installed on 2015-10-02 (364 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joe1731 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel, playback] No sound at all
  UpgradeStatus: Upgraded to xenial on 2016-09-19 (12 days ago)
  dmi.bios.date: 07/30/2010
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V1.60
  dmi.board.name: PAV10 DDR2
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.60:bd07/30/2010:svnTOSHIBA:pnTOSHIBANB255:pvrPLL2PU-00901L:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.name: TOSHIBA NB255
  dmi.product.version: PLL2PU-00901L
  dmi.sys.vendor: TOSHIBA

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

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

[Touch-packages] [Bug 1516443] Re: Wishlist: (RedShift) Night mode for Ubuntu Phones

[Joe Liau]

As mentioned in #7, this is a health issue for which there are numerous
peer-reviewed studies to support the idea. Certain spectrum of light are
harmful to people, depending on the time or individual.

Ubuntu is about being human, and so the device should always work from a
position of protecting the human.

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

Title:
  Wishlist: (RedShift) Night mode for Ubuntu Phones

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Triaged
Status in Ubuntu UX:
  Triaged
Status in mir package in Ubuntu:
  Triaged

Bug description:
  I would love to see a feature to make the backlight less agressive for
  the late hours of the day. For desktor there is the possibility to
  turn the screen 'red' and it feels really good compared to normal.

  This is a wish, I don't know where to put it else.

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

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

[Touch-packages] [Bug 1621611] [NEW] Network Error after OTA update

[Joe Borg]

Public bug reported:

This doubt a webbrowser-app issue, but there was no "Networking" option
on https://wiki.ubuntu.com/Avengers

After updating my BQ E4.5 to Ubuntu 15.04 OTA-12, I get intermittent
network errors.  This is most obvious when opening the "webbrowser-app".
I frequently get presented with "Network Error".

Is there anything I can do to debug where this is coming from?  I've
tried factory resetting, with no luck.

Please let me know if there is anything details I can get from the phone
that would help.

Thanks

** Affects: webbrowser-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 webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1621611

Title:
  Network Error after OTA update

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  This doubt a webbrowser-app issue, but there was no "Networking"
  option on https://wiki.ubuntu.com/Avengers

  After updating my BQ E4.5 to Ubuntu 15.04 OTA-12, I get intermittent
  network errors.  This is most obvious when opening the "webbrowser-
  app".  I frequently get presented with "Network Error".

  Is there anything I can do to debug where this is coming from?  I've
  tried factory resetting, with no luck.

  Please let me know if there is anything details I can get from the
  phone that would help.

  Thanks

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

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

[Touch-packages] [Bug 1613698] Re: curl: Problem with chunked encoded data

[Joe]

(Hmm, the bug tracker ate the rest of my comment?!)

# php test.php 
string(2) "OK" 
string(0) "" 

string(2) "OK" 
string(0) "" 

string(2) "OK" 
string(0) "" 

number_format(null) called

bool(false)
string(39) "Problem (2) in the Chunked-Encoded data" 

number_format(null) called

-

The updated packages actually seem to fix the problem - no more "Problem
(2) in the Chunked-Encoded data":

# curl
http://launchpadlibrarian.net/281937790/libcurl3_7.35.0-1ubuntu2.9_amd64.deb
-O

# curl
http://launchpadlibrarian.net/281937786/curl_7.35.0-1ubuntu2.9_amd64.deb
-O

# dpkg -i *deb
(Reading database ... 67243 files and directories currently installed.)
Preparing to unpack curl_7.35.0-1ubuntu2.9_amd64.deb ...
Unpacking curl (7.35.0-1ubuntu2.9) over (7.35.0-1ubuntu2.9) ...
Preparing to unpack libcurl3_7.35.0-1ubuntu2.9_amd64.deb ...
Unpacking libcurl3:amd64 (7.35.0-1ubuntu2.9) over (7.35.0-1ubuntu2.8) ...
Setting up libcurl3:amd64 (7.35.0-1ubuntu2.9) ...
Setting up curl (7.35.0-1ubuntu2.9) ...
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Processing triggers for libc-bin (2.19-0ubuntu6.9) ...

# dpkg -l |grep curl
ii  curl 7.35.0-1ubuntu2.9amd64 
   command line tool for transferring data with URL syntax
ii  libcurl3:amd64   7.35.0-1ubuntu2.9amd64 
   easy-to-use client-side URL transfer library (OpenSSL flavour)

# php test.php 
string(2) "OK" 
string(0) "" 

string(2) "OK" 
string(0) "" 

string(2) "OK" 
string(0) "" 

number_format(null) called

string(2) "OK" 
string(0) "" 

number_format(null) called

string(2) "OK" 
string(0) "" 

number_format(null) called

string(2) "OK" 
string(0) "" 

number_format(null) called

string(2) "OK" 
string(0) "" 

number_format(null) called

string(2) "OK" 
string(0) "" 

number_format(null) called

string(2) "OK" 
string(0) "" 

number_format(null) called

string(2) "OK" 
string(0) "" 

number_format(null) called

-

Thanks everyone for the quick support!

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

Title:
  curl: Problem with chunked encoded data

Status in curl package in Ubuntu:
  Fix Released
Status in curl source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  curl in Ubuntu 14.0.4 suffers from a bug ("Problem (2) in the Chunked-Encoded 
data") introduced in curl 7.35.0 
(https://github.com/curl/curl/commit/345891edba32312686e18d8ff185f4476b74e417).

  See the corresponding thread on the curl mailing list:
  * https://curl.haxx.se/mail/lib-2014-02/0100.html
  * https://curl.haxx.se/mail/lib-2014-02/0108.html

  Googling for "Problem (2) in the Chunked-Encoded data" shows that this seems 
to be a problem for other Ubuntu users, too. For example:
  * 
https://github.com/jackalope/jackalope-jackrabbit/issues/89#issuecomment-55084492
  * 
https://www.mastizada.com/blog/chunked-encoded-data-error-in-php-curl-requests/
  * https://bugs.php.net/bug.php?id=72131

  [ test case]
  * curl -v 'http://curl.haxx.se/download/' 
  (this might work on some configurations)

  
  [ fix ]

  The issue was fixed in curl 7.36.0 with
  https://github.com/curl/curl/commit/0ab97ba0090f2609760c33000181f08757336a48

  If you apply that patch to curl in Ubuntu 14.04, I'm sure you'll make
  a lot of people happy - including me. Thanks!

  [Regression Potential] 
  * none, fix comes from upstream, and is a fix of a bad commit

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

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

[Touch-packages] [Bug 1613698] Re: curl: Problem with chunked encoded data

[Joe]

Using the PHP script from https://bugs.php.net/bug.php?id=72131 we were
able to reproduce the bug with curl 7.35.0-1ubuntu2.8 (maybe there's a
simpler way to reproduce...):

-

# dpkg -l | grep curl
ii  curl 7.35.0-1ubuntu2.8amd64 
   command line tool for transferring data with URL syntax
ii  libcurl3:amd64   7.35.0-1ubuntu2.8amd64 
   easy-to-use client-side URL transfer library (OpenSSL flavour)

** Bug watch added: bugs.php.net/ #72131
   http://bugs.php.net/bug.php?id=72131

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

Title:
  curl: Problem with chunked encoded data

Status in curl package in Ubuntu:
  Fix Released
Status in curl source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  curl in Ubuntu 14.0.4 suffers from a bug ("Problem (2) in the Chunked-Encoded 
data") introduced in curl 7.35.0 
(https://github.com/curl/curl/commit/345891edba32312686e18d8ff185f4476b74e417).

  See the corresponding thread on the curl mailing list:
  * https://curl.haxx.se/mail/lib-2014-02/0100.html
  * https://curl.haxx.se/mail/lib-2014-02/0108.html

  Googling for "Problem (2) in the Chunked-Encoded data" shows that this seems 
to be a problem for other Ubuntu users, too. For example:
  * 
https://github.com/jackalope/jackalope-jackrabbit/issues/89#issuecomment-55084492
  * 
https://www.mastizada.com/blog/chunked-encoded-data-error-in-php-curl-requests/
  * https://bugs.php.net/bug.php?id=72131

  [ test case]
  * curl -v 'http://curl.haxx.se/download/' 
  (this might work on some configurations)

  
  [ fix ]

  The issue was fixed in curl 7.36.0 with
  https://github.com/curl/curl/commit/0ab97ba0090f2609760c33000181f08757336a48

  If you apply that patch to curl in Ubuntu 14.04, I'm sure you'll make
  a lot of people happy - including me. Thanks!

  [Regression Potential] 
  * none, fix comes from upstream, and is a fix of a bad commit

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

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

[Touch-packages] [Bug 1613698] Re: curl: Problem with chunked encoded data

[Joe]

** Description changed:

  curl in Ubuntu 14.0.4 suffers from a bug ("Problem (2) in the Chunked-
  Encoded data") introduced in curl 7.35.0
  
(https://github.com/curl/curl/commit/345891edba32312686e18d8ff185f4476b74e417).
  
  See the corresponding thread on the curl mailing list:
  * https://curl.haxx.se/mail/lib-2014-02/0100.html
  * https://curl.haxx.se/mail/lib-2014-02/0108.html
  
  Googling for "Problem (2) in the Chunked-Encoded data" shows that this seems 
to be a problem for other Ubuntu users, too. For example:
  * 
https://github.com/jackalope/jackalope-jackrabbit/issues/89#issuecomment-55084492
  * 
https://www.mastizada.com/blog/chunked-encoded-data-error-in-php-curl-requests/
  * https://bugs.php.net/bug.php?id=72131
  
  
  
  The issue was fixed in curl 7.36.0 with
  https://github.com/curl/curl/commit/0ab97ba0090f2609760c33000181f08757336a48
  
- If you applied that patch to curl in Ubuntu 14.04, I'm sure you'll make
- a lot of people happy - including me. Thanks!
+ If you apply that patch to curl in Ubuntu 14.04, I'm sure you'll make a
+ lot of people happy - including me. Thanks!
  
  
  
  Ubuntu 14.04.4 LTS, curl-7.35.0-1ubuntu2.7

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

Title:
  curl: Problem with chunked encoded data

Status in curl package in Ubuntu:
  New

Bug description:
  curl in Ubuntu 14.0.4 suffers from a bug ("Problem (2) in the Chunked-
  Encoded data") introduced in curl 7.35.0
  
(https://github.com/curl/curl/commit/345891edba32312686e18d8ff185f4476b74e417).

  See the corresponding thread on the curl mailing list:
  * https://curl.haxx.se/mail/lib-2014-02/0100.html
  * https://curl.haxx.se/mail/lib-2014-02/0108.html

  Googling for "Problem (2) in the Chunked-Encoded data" shows that this seems 
to be a problem for other Ubuntu users, too. For example:
  * 
https://github.com/jackalope/jackalope-jackrabbit/issues/89#issuecomment-55084492
  * 
https://www.mastizada.com/blog/chunked-encoded-data-error-in-php-curl-requests/
  * https://bugs.php.net/bug.php?id=72131

  

  The issue was fixed in curl 7.36.0 with
  https://github.com/curl/curl/commit/0ab97ba0090f2609760c33000181f08757336a48

  If you apply that patch to curl in Ubuntu 14.04, I'm sure you'll make
  a lot of people happy - including me. Thanks!

  

  Ubuntu 14.04.4 LTS, curl-7.35.0-1ubuntu2.7

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

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

[Touch-packages] [Bug 1613698] [NEW] curl: Problem with chunked encoded data

[Joe]

Public bug reported:

curl in Ubuntu 14.0.4 suffers from a bug ("Problem (2) in the Chunked-
Encoded data") introduced in curl 7.35.0
(https://github.com/curl/curl/commit/345891edba32312686e18d8ff185f4476b74e417).

See the corresponding thread on the curl mailing list:
* https://curl.haxx.se/mail/lib-2014-02/0100.html
* https://curl.haxx.se/mail/lib-2014-02/0108.html

Googling for "Problem (2) in the Chunked-Encoded data" shows that this seems to 
be a problem for other Ubuntu users, too. For example:
* 
https://github.com/jackalope/jackalope-jackrabbit/issues/89#issuecomment-55084492
* 
https://www.mastizada.com/blog/chunked-encoded-data-error-in-php-curl-requests/
* https://bugs.php.net/bug.php?id=72131



The issue was fixed in curl 7.36.0 with
https://github.com/curl/curl/commit/0ab97ba0090f2609760c33000181f08757336a48

If you applied that patch to curl in Ubuntu 14.04, I'm sure you'll make
a lot of people happy - including me. Thanks!



Ubuntu 14.04.4 LTS, curl-7.35.0-1ubuntu2.7

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

** Patch added: "Patch from 
https://github.com/curl/curl/commit/0ab97ba0090f2609760c33000181f08757336a48;
   
https://bugs.launchpad.net/bugs/1613698/+attachment/4721899/+files/curl-0ab97ba0090f2609760c33000181f08757336a48.diff

** Description changed:

  curl in Ubuntu 14.0.4 suffers from a bug ("Problem (2) in the Chunked-
  Encoded data") introduced in curl 7.35.0
  
(https://github.com/curl/curl/commit/345891edba32312686e18d8ff185f4476b74e417).
  
- See the corresponding thread on the curl mailing list: 
+ See the corresponding thread on the curl mailing list:
  * https://curl.haxx.se/mail/lib-2014-02/0100.html
- * https://curl.haxx.se/mail/lib-2014-02/0108.html 
+ * https://curl.haxx.se/mail/lib-2014-02/0108.html
  
  Googling for "Problem (2) in the Chunked-Encoded data" shows that this seems 
to be a problem for other Ubuntu users, too. For example:
  * 
https://github.com/jackalope/jackalope-jackrabbit/issues/89#issuecomment-55084492
  * 
https://www.mastizada.com/blog/chunked-encoded-data-error-in-php-curl-requests/
  * https://bugs.php.net/bug.php?id=72131
  
  
  
  The issue was fixed in curl 7.36.0 with
  https://github.com/curl/curl/commit/0ab97ba0090f2609760c33000181f08757336a48
  
  If you applied that patch to curl in Ubuntu 14.04, I'm sure you'll make
  a lot of people happy - including me. Thanks!
  
  
  
- Ubuntu 14.04.4 LTS, curl-
+ Ubuntu 14.04.4 LTS, curl-7.35.0-1ubuntu2.7

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

Title:
  curl: Problem with chunked encoded data

Status in curl package in Ubuntu:
  New

Bug description:
  curl in Ubuntu 14.0.4 suffers from a bug ("Problem (2) in the Chunked-
  Encoded data") introduced in curl 7.35.0
  
(https://github.com/curl/curl/commit/345891edba32312686e18d8ff185f4476b74e417).

  See the corresponding thread on the curl mailing list:
  * https://curl.haxx.se/mail/lib-2014-02/0100.html
  * https://curl.haxx.se/mail/lib-2014-02/0108.html

  Googling for "Problem (2) in the Chunked-Encoded data" shows that this seems 
to be a problem for other Ubuntu users, too. For example:
  * 
https://github.com/jackalope/jackalope-jackrabbit/issues/89#issuecomment-55084492
  * 
https://www.mastizada.com/blog/chunked-encoded-data-error-in-php-curl-requests/
  * https://bugs.php.net/bug.php?id=72131

  

  The issue was fixed in curl 7.36.0 with
  https://github.com/curl/curl/commit/0ab97ba0090f2609760c33000181f08757336a48

  If you applied that patch to curl in Ubuntu 14.04, I'm sure you'll
  make a lot of people happy - including me. Thanks!

  

  Ubuntu 14.04.4 LTS, curl-7.35.0-1ubuntu2.7

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

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

[Touch-packages] [Bug 1582421] Re: removing upstart breaks user login

[Joe Philipps]

I was surprised to find it running after booting my system.  Apparently
it's still used for Xorg session management, like "/sbin/upstart --user"
in the ps(1) listing.  My guess is that lightdm or something else that
initiates your X session either by default, or is configured to, run
/sbin/upstart in user mode to handle launching everything in one's
session (the panel, the window manager, etc.).

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

Title:
  removing upstart breaks user login

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  After "apt remove upstart" it's impossible to login into user's
  session via lightdm on xubuntu 16.04 - I thought we've finally ditched
  that junk, how come it still breaks the system on removal?

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

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

[Touch-packages] [Bug 1337584] Re: Support sharing of Links

[Joe Liau]

On nexus 4 mako
Rc-proposed channel

I still cannot share linka from browser to text message. Only the title
of thr webpage shows up

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

Title:
  Support sharing of Links

Status in messaging-app:
  Fix Released
Status in messaging-app package in Ubuntu:
  Fix Released

Bug description:
  modify the share handler to support the content type Links such that
  links can be shared from the browser (or other apps). They should just
  be pasted into the text message, no MMS required.

To manage notifications about this bug go to:
https://bugs.launchpad.net/messaging-app/+bug/1337584/+subscriptions

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

[Touch-packages] [Bug 1608300] [NEW] Media player makes copy of video when played

[Joe Liau]

Public bug reported:

Mako
Rc-proposed
R498

I copied a video from desktop to mobile Videos folder. It is mp4.
When I play the video in media player, it creates a copy of the video file on 
every play.

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

** Attachment added: "screenshot20160731_152136948.png"
   
https://bugs.launchpad.net/bugs/1608300/+attachment/4711184/+files/screenshot20160731_152136948.png

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

Title:
  Media player makes copy of video when played

Status in mediaplayer-app package in Ubuntu:
  New

Bug description:
  Mako
  Rc-proposed
  R498

  I copied a video from desktop to mobile Videos folder. It is mp4.
  When I play the video in media player, it creates a copy of the video file on 
every play.

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

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

[Touch-packages] [Bug 1469220] Re: [dialer] Dialer should allow me to block nuisance calls

[Joe Liau]

I don't think the experience of nuisance calling is understood if this
issue is marked as "low" or "wishlist".

Does that mean there is no one able to work on it, or that it is not
important?

Nuisance calls are very disruptive and abusive. The device should be
protective of the human or allow the human to protect itself, but right
now it is a direct line for abuse.

There is a concern of lack of resources in this project. I believe we
could recover some of those resources, if we weren't disturbed by
nuisances, such as phone calls and spam messaging.

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

Title:
  [dialer] Dialer should allow me to block nuisance calls

Status in Ubuntu UX:
  Confirmed
Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  Title says it all. I have a very old number and get a lot of
  businesses trying to get my custom (by annoying me, ironically). I had
  them block on my last phone but I'm getting them again. Please
  implement this.

  The messages app equivalent is bug 1469535.

  --- UX comment & resolution ---

  To block a number:

  1. Open dialer
  2. Carry out a bottom edge swipe to access your Recent calls
  3. Swipe towards the left on the entry/number you would like to block
  4. tap the Info icon
  5. see the revealed details about the caller and select the BLOCK option at 
the bottom of the page

  Please refer to the latest UX spec here:
  https://docs.google.com/document/d/1BRy9
  -DEXr3A1D7PHkJaXmjbe7xbRmxKkzANXuu-F6lc/edit

  Please refer to the latest visual spec here:
  
https://docs.google.com/presentation/d/1XMHRg7T3KxMizExeRTmXJGar0WOUyBQ4A8lEMnQvcqA/edit#slide=id.g34bd6a2bc_417

  Visuals attached to bug

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

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

[Touch-packages] [Bug 1598597] Re: Screen does not turn off automatically

[Joe Liau]

Whilst digging into the device settings, I discovered that the "screen
lock" was set to 10 minutes. I don't remember setting that.

When I set it back to 30 sec, it seemed to correct the behaviour.
Although I recall the device remaining active for longer than 10
minutes.

I consider this "bug" to be solved. However, it raises a new  issue:

"screen lock" and "screen dim/blank" are very different things

I would say that the screen turning off is a batter/power issue, whereas
the screen "locking" is a privacy issue.

Currently, both things are contained in one action and listed under
"privacy".  Ideally, they would be separate things under two different
areas in the settings.

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

Title:
  Screen does not turn off automatically

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Mako
  Rc-propsed
  R477

  After leaving the device idle for any time the screen does not turn off or 
blank automatically.
  Power button must be pressed to turn off the screen.

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

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

[Touch-packages] [Bug 1598597] Re: Screen does not turn off automatically

[Joe Liau]

System State Requests:
  Name: com.canonical.Unity.Screen, Owner: :1.18, State: 1
  Name: usensord, Owner: :1.27, State: 1
  Name: active, Owner: :1.60, State: 1
phablet@ubuntu-phablet:~$ 

Generally it happens regardless of what apps i have running. But
typically with podbird or the browser open.

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

Title:
  Screen does not turn off automatically

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Mako
  Rc-propsed
  R477

  After leaving the device idle for any time the screen does not turn off or 
blank automatically.
  Power button must be pressed to turn off the screen.

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

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

[Touch-packages] [Bug 1593686] Re: Wi-Fi passphrase limit introduced in OTA-11

[Joe Odukoya]

FWIW after various problems trying to get my turbo connected to a local
hotspot here it suddenly started working only to stop working during one
of the landings for OTA11 (I'm not here all the time so I did not notice
it immediately).

The password is 40 characters long and I can no longer get turbo to
connect even with a complete reflash.

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

Title:
  Wi-Fi passphrase limit introduced in OTA-11

Status in Canonical System Image:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  After installing OTA-11, connectivity to a Cisco AP1131AG AP (IOS
  12.4-25d.JA2) stopped working, possibly due to the length of the WPA
  pass-phrase, which was 29 characters long.  The pass-phrase
  requirement is from 8 to 63 characters.  After reducing the pass-
  phrase to 14 (and sometimes 15) characters connectivity is restored.

  Attempting to connect to a Cisco 1702i (IOS 15.3-3.JC1) which has both
  802.11 ac (wave 1) and 802.11n radios has similar problems: (a) it
  cannot "see" the 802.11ac radio at all (interface Dot11Radio0) and
  although it "sees" the 802.11n radio (interface Dot11Radio1) it cannot
  connect.  The pass-phrase length requirement on both radios is 18 to
  128 characters.

  In both cases the Cisco APs do not log any event.

  Prior to OTA 11 connectivity worked normally on OTA 10.1

  OS: Ubuntu 15.04 (OTA-11) on BQ Aquaris E5

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

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

[Touch-packages] [Bug 1598670] [NEW] package hicolor-icon-theme 0.13-1 failed to install/upgrade: triggers looping, abandoned

[Joe Torraca]

Public bug reported:

The error occurred while upgrading the OS version

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: hicolor-icon-theme 0.13-1
ProcVersionSignature: Ubuntu 3.13.0-87.133-generic 3.13.11-ckt39
Uname: Linux 3.13.0-87-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Mon Jul  4 00:16:12 2016
Dependencies:
 
DuplicateSignature: package:hicolor-icon-theme:0.13-1:triggers looping, 
abandoned
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2015-01-05 (546 days ago)
InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.2ubuntu5.1
 apt  1.0.1ubuntu2.14
SourcePackage: hicolor-icon-theme
Title: package hicolor-icon-theme 0.13-1 failed to install/upgrade: triggers 
looping, abandoned
UpgradeStatus: Upgraded to wily on 2016-07-04 (0 days ago)

** Affects: hicolor-icon-theme (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package wily

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

Title:
  package hicolor-icon-theme 0.13-1 failed to install/upgrade: triggers
  looping, abandoned

Status in hicolor-icon-theme package in Ubuntu:
  New

Bug description:
  The error occurred while upgrading the OS version

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: hicolor-icon-theme 0.13-1
  ProcVersionSignature: Ubuntu 3.13.0-87.133-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-87-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Mon Jul  4 00:16:12 2016
  Dependencies:
   
  DuplicateSignature: package:hicolor-icon-theme:0.13-1:triggers looping, 
abandoned
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-01-05 (546 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.1ubuntu2.14
  SourcePackage: hicolor-icon-theme
  Title: package hicolor-icon-theme 0.13-1 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to wily on 2016-07-04 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1598670/+subscriptions

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

[Touch-packages] [Bug 1598633] [NEW] Chinese input stops suggesting characters after pressing space then backspace

[Joe Liau]

Public bug reported:

Mako
rc-proposed
r477

What happens:
Pinyin Chinese keyboard will suggest characters after typing. This behavior 
stops if you press spacebar then backspace. Doing so seems to want you to 
confirm previously typed characters, but does not allow you to choose a 
different selection or edit what was typed. 

E.g. 拼音nihao

Expected:
Character suggestion should continue to popup or allow editing of adjacent 
previously typed characters. 

E.g 拼音你好

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

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

Title:
  Chinese input stops suggesting characters after pressing space then
  backspace

Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  Mako
  rc-proposed
  r477

  What happens:
  Pinyin Chinese keyboard will suggest characters after typing. This behavior 
stops if you press spacebar then backspace. Doing so seems to want you to 
confirm previously typed characters, but does not allow you to choose a 
different selection or edit what was typed. 

  E.g. 拼音nihao

  Expected:
  Character suggestion should continue to popup or allow editing of adjacent 
previously typed characters. 

  E.g 拼音你好

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

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

[Touch-packages] [Bug 1598631] [NEW] Emoji are a separate keyboard

[Joe Liau]

Public bug reported:

Mako
rc-proposed
R477

What happens:
Emoji is currently its own keyboard. Because the globe button only allows you 
to 'flip flop' between two keyboards, it makes it cumbersome to use if more 
than one language is being inputed.

Expected:
Emoji could be an extension of every keyboard rather than the keybaord itself. 
This would work similar to how numbers and symbols are inputed.

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

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

Title:
  Emoji are a separate keyboard

Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  Mako
  rc-proposed
  R477

  What happens:
  Emoji is currently its own keyboard. Because the globe button only allows you 
to 'flip flop' between two keyboards, it makes it cumbersome to use if more 
than one language is being inputed.

  Expected:
  Emoji could be an extension of every keyboard rather than the keybaord 
itself. This would work similar to how numbers and symbols are inputed.

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

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

[Touch-packages] [Bug 1598629] [NEW] Each new word reverts keyboard back to letters input

[Joe Liau]

Public bug reported:

Mako
rc-proposed
R477

When typing numbers or symbols with spaces (ie after pressing the "?123"
key) when the spaces bar is pressed, the keyboard goes back to ABC mode.

This is probably on purpose, but it does make it awkward when typing out 
numbers with spaces. 
The chance of having to type numbers in that way is not common, but something 
to consider.

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

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

Title:
  Each new word reverts keyboard back to letters input

Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  Mako
  rc-proposed
  R477

  When typing numbers or symbols with spaces (ie after pressing the
  "?123" key) when the spaces bar is pressed, the keyboard goes back to
  ABC mode.

  This is probably on purpose, but it does make it awkward when typing out 
numbers with spaces. 
  The chance of having to type numbers in that way is not common, but something 
to consider.

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

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

[Touch-packages] [Bug 1598597] [NEW] Screen does not turn off automatically

[Joe Liau]

Public bug reported:

Mako
Rc-propsed
R477

After leaving the device idle for any time the screen does not turn off or 
blank automatically.
Power button must be pressed to turn off the screen.

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

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

Title:
  Screen does not turn off automatically

Status in unity8 package in Ubuntu:
  New

Bug description:
  Mako
  Rc-propsed
  R477

  After leaving the device idle for any time the screen does not turn off or 
blank automatically.
  Power button must be pressed to turn off the screen.

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

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