[Touch-packages] [Bug 1815172] Re: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa

[Timo Aaltonen]

Alkis, could you double-check if your setup is fine now with the current
4.15 kernel and mesa from proposed? Mine is, but I'd rather not rely on
that test alone.

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

Title:
  [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Won't Fix
Status in mesa source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Several schools reported black screens after normally updating their Ubuntu 
boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

  This is caused by mesa assuming that soft-pinning on GEN8+ is working
  since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So
  a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT
  sizes/pin flags, but that's left for future.

  [Test case]
  install fixed mesa or kernel, check that the regression is fixed

  [Regression potential]
  mesa: shouldn't be any, it just reverts the change to always soft-pin
  (TODO kernel: adds commits from upstream stable, which have been well tested 
upstream by now)

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

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

[Touch-packages] [Bug 1829364] Re: Will not play sound via HDMI using 48000 Hz sample rate

[Jarno Suni]

** Summary changed:

- Will not play sound via HDMI unless you run pavucontrol first
+ Will not play sound via HDMI using 48000 Hz sample rate

** Description changed:

- Does not play sound via sink output:iec958-stereo unless I start
- pavucontrol before running the player such as paplay. Player does not
- show any error and takes its time to play, but there is no sound.
+ Does not play sound when playing file that has 48000 Hz sample rate via
+ sink output:iec958-stereo
  
  Workaround:
  Set
  alternate-sample-rate = 44100
  in /etc/pulse/daemon.conf and restart pulseaudio
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jarnos 1283 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu May 16 12:39:15 2019
  InstallationDate: Installed on 2019-05-08 (7 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MVD Ver. F.20
  dmi.board.name: 30C5
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard

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

Title:
  Will not play sound via HDMI using 48000 Hz sample rate

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Does not play sound when playing file that has 48000 Hz sample rate
  via sink output:iec958-stereo

  Workaround:
  Set
  alternate-sample-rate = 44100
  in /etc/pulse/daemon.conf and restart pulseaudio

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jarnos 1283 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu May 16 12:39:15 2019
  InstallationDate: Installed on 2019-05-08 (7 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MVD Ver. F.20
  dmi.board.name: 30C5
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1844100] [NEW] evolution-calendar-factory crashed with SIGSEGV in tcache_get()

[Jean-Baptiste Lallement]

Public bug reported:

it crashed

ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: evolution-data-server 3.33.91-3
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 16 09:53:33 2019
ExecutablePath: /usr/libexec/evolution-calendar-factory
InstallationDate: Installed on 2013-09-03 (2203 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcCmdline: /usr/libexec/evolution-calendar-factory
ProcEnviron:
 LANG=fr_FR.UTF-8
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SegvAnalysis:
 Segfault happened at: 0x7f7b13f583ae <__GI___libc_malloc+286>: mov
(%r8),%rsi
 PC (0x7f7b13f583ae) ok
 source "(%r8)" (0x7f7a0002) not located in a known VMA region (needed 
readable region)!
 destination "%rsi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: evolution-data-server
StacktraceTop:
 tcache_get (tc_idx=) at malloc.c:2937
 __GI___libc_malloc (bytes=40) at malloc.c:3051
 pvl_newlist () at /usr/lib/x86_64-linux-gnu/libical.so.3
 () at /usr/lib/x86_64-linux-gnu/libical.so.3
 i_cal_component_new () at /usr/lib/x86_64-linux-gnu/libical-glib.so.3
Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get()
UpgradeStatus: Upgraded to eoan on 2018-01-26 (597 days ago)
UserGroups: adm autopilot cdrom dip docker libvirt lpadmin lxd plugdev 
sambashare stapdev stapsys stapusr sudo
separator:

** Affects: evolution-data-server (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash eoan need-amd64-retrace

** Information type changed from Private to Public

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

Title:
  evolution-calendar-factory crashed with SIGSEGV in tcache_get()

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  it crashed

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: evolution-data-server 3.33.91-3
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 16 09:53:33 2019
  ExecutablePath: /usr/libexec/evolution-calendar-factory
  InstallationDate: Installed on 2013-09-03 (2203 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcCmdline: /usr/libexec/evolution-calendar-factory
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f7b13f583ae <__GI___libc_malloc+286>:   mov
(%r8),%rsi
   PC (0x7f7b13f583ae) ok
   source "(%r8)" (0x7f7a0002) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   tcache_get (tc_idx=) at malloc.c:2937
   __GI___libc_malloc (bytes=40) at malloc.c:3051
   pvl_newlist () at /usr/lib/x86_64-linux-gnu/libical.so.3
   () at /usr/lib/x86_64-linux-gnu/libical.so.3
   i_cal_component_new () at /usr/lib/x86_64-linux-gnu/libical-glib.so.3
  Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get()
  UpgradeStatus: Upgraded to eoan on 2018-01-26 (597 days ago)
  UserGroups: adm autopilot cdrom dip docker libvirt lpadmin lxd plugdev 
sambashare stapdev stapsys stapusr sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1844100/+subscriptions

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

[Touch-packages] [Bug 1843743] Re: klibc ftbfs in eoan

[Brian Murray]

** Also affects: klibc (Ubuntu Eoan)
   Importance: High
   Status: Confirmed

** Tags removed: rls-ee-incoming

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

Title:
  klibc ftbfs in eoan

Status in klibc package in Ubuntu:
  Confirmed
Status in klibc source package in Eoan:
  Confirmed

Bug description:
  https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan-
  amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz

  gcc -Wp,-MD,usr/klibc/.sigsuspend.o.d  -nostdinc -iwithprefix include 
-I/<>/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 
-I/<>/usr/include/bits64 -Iusr/include/bits64 
-I/<>/usr/klibc/../include -Iusr/klibc/../include 
-I/<>/usr/include -Iusr/include -I/<>/linux/include 
-Ilinux/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 
-fno-stack-protector -fwrapv -fno-PIE -ggdb -m64 -Os -fomit-frame-pointer 
-mno-sse -falign-functions=1 -falign-jumps=1 -falign-loops=1 
-fno-asynchronous-unwind-tables -W -Wall -Wno-sign-compare 
-Wno-unused-parameter -c -o usr/klibc/sigsuspend.o usr/klibc/sigsuspend.c
  usr/klibc/sigsuspend.c:8:10: fatal error: klibc/havesyscall.h: No such file 
or directory
  8 | #include 
|  ^
  compilation terminated.
  make[4]: *** [/<>/scripts/Kbuild.klibc:252: 
usr/klibc/sigsuspend.o] Error 1
  make[3]: *** [/<>/./Kbuild:9: all] Error 2
  make[2]: *** [Makefile:118: klibc] Error 2

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

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

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

[Apport retracing service]

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

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

Title:
  evolution-calendar-factory crashed with SIGSEGV in tcache_get()

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  it crashed

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: evolution-data-server 3.33.91-3
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 16 09:53:33 2019
  ExecutablePath: /usr/libexec/evolution-calendar-factory
  InstallationDate: Installed on 2013-09-03 (2203 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcCmdline: /usr/libexec/evolution-calendar-factory
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f7b13f583ae <__GI___libc_malloc+286>:   mov
(%r8),%rsi
   PC (0x7f7b13f583ae) ok
   source "(%r8)" (0x7f7a0002) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   tcache_get (tc_idx=) at malloc.c:2937
   __GI___libc_malloc (bytes=40) at malloc.c:3051
   pvl_newlist () at /usr/lib/x86_64-linux-gnu/libical.so.3
   () at /usr/lib/x86_64-linux-gnu/libical.so.3
   i_cal_component_new () at /usr/lib/x86_64-linux-gnu/libical-glib.so.3
  Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get()
  UpgradeStatus: Upgraded to eoan on 2018-01-26 (597 days ago)
  UserGroups: adm autopilot cdrom dip docker libvirt lpadmin lxd plugdev 
sambashare stapdev stapsys stapusr sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1844100/+subscriptions

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

[Touch-packages] [Bug 1844100] evolution-calendar-factory crashed with SIGSEGV in tcache_get()

[Apport retracing service]

StacktraceTop:
 tcache_get (tc_idx=) at malloc.c:2937
 __GI___libc_malloc (bytes=bytes@entry=40) at malloc.c:3051
 pvl_newlist () at ./src/libical/pvl.c:65
 icalcomponent_new_impl (kind=kind@entry=ICAL_VEVENT_COMPONENT) at 
./src/libical/icalcomponent.c:104
 icalcomponent_new (kind=kind@entry=ICAL_VEVENT_COMPONENT) at 
./src/libical/icalcomponent.c:114

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

Title:
  evolution-calendar-factory crashed with SIGSEGV in tcache_get()

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  it crashed

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: evolution-data-server 3.33.91-3
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 16 09:53:33 2019
  ExecutablePath: /usr/libexec/evolution-calendar-factory
  InstallationDate: Installed on 2013-09-03 (2203 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcCmdline: /usr/libexec/evolution-calendar-factory
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f7b13f583ae <__GI___libc_malloc+286>:   mov
(%r8),%rsi
   PC (0x7f7b13f583ae) ok
   source "(%r8)" (0x7f7a0002) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   tcache_get (tc_idx=) at malloc.c:2937
   __GI___libc_malloc (bytes=40) at malloc.c:3051
   pvl_newlist () at /usr/lib/x86_64-linux-gnu/libical.so.3
   () at /usr/lib/x86_64-linux-gnu/libical.so.3
   i_cal_component_new () at /usr/lib/x86_64-linux-gnu/libical-glib.so.3
  Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get()
  UpgradeStatus: Upgraded to eoan on 2018-01-26 (597 days ago)
  UserGroups: adm autopilot cdrom dip docker libvirt lpadmin lxd plugdev 
sambashare stapdev stapsys stapusr sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1844100/+subscriptions

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

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

[Apport retracing service]

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

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

Title:
  evolution-calendar-factory crashed with SIGSEGV in tcache_get()

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  it crashed

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: evolution-data-server 3.33.91-3
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 16 09:53:33 2019
  ExecutablePath: /usr/libexec/evolution-calendar-factory
  InstallationDate: Installed on 2013-09-03 (2203 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcCmdline: /usr/libexec/evolution-calendar-factory
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f7b13f583ae <__GI___libc_malloc+286>:   mov
(%r8),%rsi
   PC (0x7f7b13f583ae) ok
   source "(%r8)" (0x7f7a0002) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   tcache_get (tc_idx=) at malloc.c:2937
   __GI___libc_malloc (bytes=40) at malloc.c:3051
   pvl_newlist () at /usr/lib/x86_64-linux-gnu/libical.so.3
   () at /usr/lib/x86_64-linux-gnu/libical.so.3
   i_cal_component_new () at /usr/lib/x86_64-linux-gnu/libical-glib.so.3
  Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get()
  UpgradeStatus: Upgraded to eoan on 2018-01-26 (597 days ago)
  UserGroups: adm autopilot cdrom dip docker libvirt lpadmin lxd plugdev 
sambashare stapdev stapsys stapusr sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1844100/+subscriptions

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

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

[Apport retracing service]

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

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

** Changed in: evolution-data-server (Ubuntu)
   Importance: Undecided => Medium

** Tags removed: need-amd64-retrace

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

Title:
  evolution-calendar-factory crashed with SIGSEGV in tcache_get()

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  it crashed

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: evolution-data-server 3.33.91-3
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 16 09:53:33 2019
  ExecutablePath: /usr/libexec/evolution-calendar-factory
  InstallationDate: Installed on 2013-09-03 (2203 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcCmdline: /usr/libexec/evolution-calendar-factory
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f7b13f583ae <__GI___libc_malloc+286>:   mov
(%r8),%rsi
   PC (0x7f7b13f583ae) ok
   source "(%r8)" (0x7f7a0002) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   tcache_get (tc_idx=) at malloc.c:2937
   __GI___libc_malloc (bytes=40) at malloc.c:3051
   pvl_newlist () at /usr/lib/x86_64-linux-gnu/libical.so.3
   () at /usr/lib/x86_64-linux-gnu/libical.so.3
   i_cal_component_new () at /usr/lib/x86_64-linux-gnu/libical-glib.so.3
  Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get()
  UpgradeStatus: Upgraded to eoan on 2018-01-26 (597 days ago)
  UserGroups: adm autopilot cdrom dip docker libvirt lpadmin lxd plugdev 
sambashare stapdev stapsys stapusr sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1844100/+subscriptions

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

[Touch-packages] [Bug 1843927] [NEW] Missing graphics drivers for AMD Ryzen 5 with Radeon Vega 8

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I have recently installed Ubuntu 19.04 on an ASUS TUF Gaming FX505DY
laptop.  The laptop has a AMD Ryzen 5 with Radeon Vega 8 processor.

No warnings where raised during the installation process regarding
problems with the graphics driver.  When I connected a HDMI connected
monitor I found it did not work.

I have attached the graphics driver logs

==
cat /var/log/gpu-manager.log

log_file: /var/log/gpu-manager.log
last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
can't access /run/u-d-c-nvidia-was-loaded file
can't access /opt/amdgpu-pro/bin/amdgpu-pro-px
Looking for nvidia modules in /lib/modules/5.0.0-27-generic/updates/dkms
Looking for amdgpu modules in /lib/modules/5.0.0-27-generic/updates/dkms
Is nvidia loaded? no
Was nvidia unloaded? no
Is nvidia blacklisted? no
Is intel loaded? no
Is radeon loaded? no
Is radeon blacklisted? no
Is amdgpu loaded? no
Is amdgpu blacklisted? no
Is amdgpu versioned? no
Is amdgpu pro stack? no
Is nouveau loaded? no
Is nouveau blacklisted? no
Is nvidia kernel module available? no
Is amdgpu kernel module available? no
Vendor/Device Id: 1002:67ef
BusID "PCI:1@0:0:0"
Is boot vga? no
Error: can't access /sys/bus/pci/devices/:01:00.0/driver
The device is not bound to any driver.
Vendor/Device Id: 1002:15d8
BusID "PCI:5@0:0:0"
Is boot vga? yes
Error: can't access /sys/bus/pci/devices/:05:00.0/driver
The device is not bound to any driver.
Error : Failed to open /dev/dri
Error : Failed to open /dev/dri
Error : Failed to open /dev/dri
Error : Failed to open /dev/dri
Does it require offloading? no
last cards number = 2
Has amd? yes
Has intel? no
Has nvidia? no
How many cards? 2
Has the system changed? No
Unsupported discrete card vendor: 1002
Nothing to do

==  
sudo lshw -C display
  *-display UNCLAIMED   
   description: Display controller
   product: Baffin [Radeon RX 460/560D / Pro 450/455/460/555/560]
   vendor: Advanced Micro Devices, Inc. [AMD/ATI]
   physical id: 0
   bus info: pci@:01:00.0
   version: e5
   width: 64 bits
   clock: 33MHz
   capabilities: pm pciexpress msi cap_list
   configuration: latency=0
   resources: memory:e000-efff memory:f000-f01f 
ioport:f000(size=256) memory:fea0-fea3 memory:fea4-fea5
  *-display UNCLAIMED
   description: VGA compatible controller
   product: Picasso
   vendor: Advanced Micro Devices, Inc. [AMD/ATI]
   physical id: 0
   bus info: pci@:05:00.0
   version: c2
   width: 64 bits
   clock: 33MHz
   capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
   configuration: latency=0
   resources: memory:c000-cfff memory:d000-d01f 
ioport:c000(size=256) memory:fe50-fe57


*
  QUESTIONS

1.  Why is the problem with unsupported drivers not flagged during the
installation process?  The default driver does work for the laptop's
monitor, but will not drive a second monitor attached to the HDMI port

2.  I have seen reference to a general purpose AMD graphics driver, but
there is no reference to this driver being supported on Ubuntu 19.04.
If I went ahead and attempted to install the general purpose graphics
driver, how would I back it out if it did not work.

I have raised this issue as a "question", but I think it is probably a
bug but I could not find out how to raise a bug associated with a lack
of device drivers.

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


** Tags: bot-comment
-- 
Missing graphics drivers for AMD Ryzen 5 with Radeon Vega 8
https://bugs.launchpad.net/bugs/1843927
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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

[Touch-packages] [Bug 1843927] Re: Missing graphics drivers for AMD Ryzen 5 with Radeon Vega 8

[Brian Murray]

** Package changed: ubuntu => xorg (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/1843927

Title:
  Missing graphics drivers for AMD Ryzen 5 with Radeon Vega 8

Status in xorg package in Ubuntu:
  New

Bug description:
  I have recently installed Ubuntu 19.04 on an ASUS TUF Gaming FX505DY
  laptop.  The laptop has a AMD Ryzen 5 with Radeon Vega 8 processor.

  No warnings where raised during the installation process regarding
  problems with the graphics driver.  When I connected a HDMI connected
  monitor I found it did not work.

  I have attached the graphics driver logs

  ==
  cat /var/log/gpu-manager.log

  log_file: /var/log/gpu-manager.log
  last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
  new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
  can't access /run/u-d-c-nvidia-was-loaded file
  can't access /opt/amdgpu-pro/bin/amdgpu-pro-px
  Looking for nvidia modules in /lib/modules/5.0.0-27-generic/updates/dkms
  Looking for amdgpu modules in /lib/modules/5.0.0-27-generic/updates/dkms
  Is nvidia loaded? no
  Was nvidia unloaded? no
  Is nvidia blacklisted? no
  Is intel loaded? no
  Is radeon loaded? no
  Is radeon blacklisted? no
  Is amdgpu loaded? no
  Is amdgpu blacklisted? no
  Is amdgpu versioned? no
  Is amdgpu pro stack? no
  Is nouveau loaded? no
  Is nouveau blacklisted? no
  Is nvidia kernel module available? no
  Is amdgpu kernel module available? no
  Vendor/Device Id: 1002:67ef
  BusID "PCI:1@0:0:0"
  Is boot vga? no
  Error: can't access /sys/bus/pci/devices/:01:00.0/driver
  The device is not bound to any driver.
  Vendor/Device Id: 1002:15d8
  BusID "PCI:5@0:0:0"
  Is boot vga? yes
  Error: can't access /sys/bus/pci/devices/:05:00.0/driver
  The device is not bound to any driver.
  Error : Failed to open /dev/dri
  Error : Failed to open /dev/dri
  Error : Failed to open /dev/dri
  Error : Failed to open /dev/dri
  Does it require offloading? no
  last cards number = 2
  Has amd? yes
  Has intel? no
  Has nvidia? no
  How many cards? 2
  Has the system changed? No
  Unsupported discrete card vendor: 1002
  Nothing to do

  
==  
sudo lshw -C display
*-display UNCLAIMED   
 description: Display controller
 product: Baffin [Radeon RX 460/560D / Pro 450/455/460/555/560]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:01:00.0
 version: e5
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi cap_list
 configuration: latency=0
 resources: memory:e000-efff memory:f000-f01f 
ioport:f000(size=256) memory:fea0-fea3 memory:fea4-fea5
*-display UNCLAIMED
 description: VGA compatible controller
 product: Picasso
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:05:00.0
 version: c2
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
 configuration: latency=0
 resources: memory:c000-cfff memory:d000-d01f 
ioport:c000(size=256) memory:fe50-fe57

  
  
*
  QUESTIONS

  1.  Why is the problem with unsupported drivers not flagged during the
  installation process?  The default driver does work for the laptop's
  monitor, but will not drive a second monitor attached to the HDMI port

  2.  I have seen reference to a general purpose AMD graphics driver,
  but there is no reference to this driver being supported on Ubuntu
  19.04.  If I went ahead and attempted to install the general purpose
  graphics driver, how would I back it out if it did not work.

  I have raised this issue as a "question", but I think it is probably a
  bug but I could not find out how to raise a bug associated with a lack
  of device drivers.

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

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

[Touch-packages] [Bug 1844100] Re: evolution-calendar-factory crashed with SIGSEGV in tcache_get()

[Launchpad Bug Tracker]

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

** Changed in: evolution-data-server (Ubuntu)
   Status: New => Confirmed

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

Title:
  evolution-calendar-factory crashed with SIGSEGV in tcache_get()

Status in evolution-data-server package in Ubuntu:
  Confirmed

Bug description:
  it crashed

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: evolution-data-server 3.33.91-3
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 16 09:53:33 2019
  ExecutablePath: /usr/libexec/evolution-calendar-factory
  InstallationDate: Installed on 2013-09-03 (2203 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcCmdline: /usr/libexec/evolution-calendar-factory
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f7b13f583ae <__GI___libc_malloc+286>:   mov
(%r8),%rsi
   PC (0x7f7b13f583ae) ok
   source "(%r8)" (0x7f7a0002) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   tcache_get (tc_idx=) at malloc.c:2937
   __GI___libc_malloc (bytes=40) at malloc.c:3051
   pvl_newlist () at /usr/lib/x86_64-linux-gnu/libical.so.3
   () at /usr/lib/x86_64-linux-gnu/libical.so.3
   i_cal_component_new () at /usr/lib/x86_64-linux-gnu/libical-glib.so.3
  Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get()
  UpgradeStatus: Upgraded to eoan on 2018-01-26 (597 days ago)
  UserGroups: adm autopilot cdrom dip docker libvirt lpadmin lxd plugdev 
sambashare stapdev stapsys stapusr sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1844100/+subscriptions

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

[Touch-packages] [Bug 1844107] Re: evolution-calendar-factory crashed with SIGSEGV in tcache_get()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1844100, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

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

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1844107/+attachment/5288964/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1844107/+attachment/5288968/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1844107/+attachment/5288969/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1844107/+attachment/5288970/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1844107/+attachment/5288971/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1844107/+attachment/5288972/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1844100
   evolution-calendar-factory crashed with SIGSEGV in tcache_get()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  evolution-calendar-factory crashed with SIGSEGV in tcache_get()

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  upgraded eoan, this came up after login

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: evolution-data-server 3.33.91-3
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 16 12:06:49 2019
  ExecutablePath: /usr/libexec/evolution-calendar-factory
  InstallationDate: Installed on 2018-02-06 (586 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180206)
  ProcCmdline: /usr/libexec/evolution-calendar-factory
  SegvAnalysis:
   Segfault happened at: 0x7f8d3593c3ae <__GI___libc_malloc+286>:   mov
(%r8),%rsi
   PC (0x7f8d3593c3ae) ok
   source "(%r8)" (0x7f8c0002) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   tcache_get (tc_idx=) at malloc.c:2937
   __GI___libc_malloc (bytes=40) at malloc.c:3051
   pvl_newlist () from /usr/lib/x86_64-linux-gnu/libical.so.3
   ?? () from /usr/lib/x86_64-linux-gnu/libical.so.3
   i_cal_component_new () from /usr/lib/x86_64-linux-gnu/libical-glib.so.3
  Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sbuild sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1844107/+subscriptions

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

[Touch-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones

[Daniel van Vugt]

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

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

Title:
  Fails to pair with Bose QC35 headphones

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

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

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

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

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

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

  With Linux kernel 4.8.0 and bluez 4.52:
  ---

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

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

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

[Touch-packages] [Bug 1508656] Re: Build with multiarch support

[Gianfranco Costamagna]

Done in eoan!


** Changed in: pocketsphinx (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Build with multiarch support

Status in pocketsphinx package in Ubuntu:
  Fix Released

Bug description:
  Build with multiarch support

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

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

[Touch-packages] [Bug 854762] Re: pocketsphinx_batch throws ERROR

[Gianfranco Costamagna]

I uploaded in Ubuntu eoan a new version, please try again if the problem
persists

** Changed in: pocketsphinx (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  pocketsphinx_batch throws ERROR

Status in pocketsphinx package in Ubuntu:
  Incomplete

Bug description:
  ERROR: "cmd_ln.c", line 644: cmd_ln_parse_r failed

  there are no man pages
  tarvid@tarvid-Dimension-8300:~$ lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04

  tarvid@tarvid-Dimension-8300:~$ apt-cache policy pocketsphinx-utils
  pocketsphinx-utils:
Installed: 0.5.1+dfsg1-0ubuntu2
Candidate: 0.5.1+dfsg1-0ubuntu2
Version table:
   *** 0.5.1+dfsg1-0ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages
  100 /var/lib/dpkg/status
  I expected it to run without errors

  -and -

  I expected man pages.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: pocketsphinx-utils 0.5.1+dfsg1-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Tue Sep 20 10:43:36 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pocketsphinx
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1318103] Re: Error importing Python module pocketsphinx

[Gianfranco Costamagna]

The package in eoan is now Python3, please try again and set back to
"new" if you still have this issue


** Changed in: pocketsphinx (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Error importing Python module pocketsphinx

Status in pocketsphinx package in Ubuntu:
  Incomplete

Bug description:
  Pretty much stock standard Ubuntu 14.04 AMD64 with no manually
  compiled software and no manually installed python modules.

  $ python
  Python 2.7.6 (default, Mar 22 2014, 22:59:56) 
  [GCC 4.8.2] on linux2
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import pocketsphinx
  Traceback (most recent call last):
File "", line 1, in 
File "sphinxbase.pxd", line 150, in init pocketsphinx (pocketsphinx.c:7935)
  ValueError: PyCapsule_GetPointer called with invalid PyCapsule object
  >>>

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

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

[Touch-packages] [Bug 863533] Re: PocketSphinx Segmentation Fault

[Gianfranco Costamagna]

The package in eoan is now Python3, please try again and set back to
"new" if you still have this issue

** Changed in: pocketsphinx (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  PocketSphinx Segmentation Fault

Status in pocketsphinx package in Ubuntu:
  Incomplete

Bug description:
  The ps_test.py file included in the python-pocketsphinx doesn't work
  out of the box since it refers to paths ../model/hmm/wsj1,
  ../test/data/wsj/wlist5o.nvp.lm.DMP, and ../model/lm/cmudict.0.6d,
  which don't seem to exist anywhere in the other pocketsphinx packages.

  The most similar paths I could find, provided by the pocketsphinx-hmm-
  wsj1 and pocketsphinx-lm-wsj packages, are
  /usr/share/pocketsphinx/model/hmm/wsj1,
  /usr/share/pocketsphinx/model/lm/wsj/wlist5o.3e-7.vp.tg.lm.DMP,
  /usr/share/pocketsphinx/model/lm/wsj/wlist5o.dic.

  However, replacing the paths in ps_test.py with those results in the
  error:

  
  INFO: cmd_ln.c(506): Parsing command line:
  \
-hmm /usr/share/pocketsphinx/model/hmm/wsj1 \
-fwdtree yes \
-dict /usr/share/pocketsphinx/model/lm/wsj/wlist5o.dic \
-lm /usr/share/pocketsphinx/model/lm/wsj/wlist5o.3e-7.vp.tg.lm.DMP \
-fwdflat yes \
-bestpath no 

  Current configuration:
  [NAME][DEFLT] [VALUE]
  -agc  nonenone
  -agcthresh2.0 2.00e+00
  -alpha0.979.70e-01
  -ascale   20.02.00e+01
  -backtraceno  no
  -beam 1e-48   1.00e-48
  -bestpath yes no
  -bestpathlw   9.5 9.50e+00
  -cep2spec no  no
  -ceplen   13  13
  -cmn  current current
  -cmninit  8.0 8.0
  -compallsen   no  no
  -dict /usr/share/pocketsphinx/model/lm/wsj/wlist5o.dic
  -dictcase no  no
  -dither   no  no
  -doublebw no  no
  -ds   1   1
  -fdict
  -feat 1s_c_d_dd   1s_c_d_dd
  -featparams   
  -fillprob 1e-81.00e-08
  -frate100 100
  -fsg  
  -fsgusealtpronyes yes
  -fsgusefiller yes yes
  -fwdflat  yes yes
  -fwdflatbeam  1e-64   1.00e-64
  -fwdflatefwid 4   4
  -fwdflatlw8.5 8.50e+00
  -fwdflatsfwin 25  25
  -fwdflatwbeam 7e-29   7.00e-29
  -fwdtree  yes yes
  -hmm  /usr/share/pocketsphinx/model/hmm/wsj1
  -input_endian little  little
  -jsgf 
  -kdmaxbbi -1  -1
  -kdmaxdepth   0   0
  -kdtree   
  -latsize  50005000
  -lda  
  -ldadim   0   0
  -lifter   0   0
  -lm   
/usr/share/pocketsphinx/model/lm/wsj/wlist5o.3e-7.vp.tg.lm.DMP
  -lmctl
  -lmname   default default
  -logbase  1.0001  1.000100e+00
  -logfn
  -logspec  no  no
  -lowerf   133.4   1.33e+02
  -lpbeam   1e-40   1.00e-40
  -lponlybeam   7e-29   7.00e-29
  -lw   6.5 6.50e+00
  -maxhistpf100 100
  -maxhmmpf -1  -1
  -maxnewoov20  20
  -maxwpf   -1  -1
  -mdef 
  -mean 
  -mfclogdir
  -mixw 
  -mixwfloor0.001   1.00e-07
  -mmap yes yes
  -ncep 13  13
  -nfft 512 512
  -nfilt40  40
  -nwpen1.0 1.00e+00
  -pbeam1e-48   1.00e-48
  -pip  1.0 1.00e+00
  -rawlogdir
  -remove_dcno  no
  -round_filtersyes yes
  -samprate 16000   1.60e+04
  -sdmap
  -seed -1  -1
  -sendump  
  -silprob  0.005   5.00e-03
  -smoothspec   no  no
  -spec2cep no  no
  -svspec   
  -tmat 
  -tmatfloor0.0001  1.00e-04
  -topn 4   4
  -toprule  
  -transformlegacy 

[Touch-packages] [Bug 147551] Re: cups-pdf fails to generate file when user does not print to default ~/PDF (apparmor vs.cups-pdf inconsistency)

[Zenaan Harkness]

For reference, just steamrolled through this same saga, and finally
figoured out that Geany and Mousepad each use the same print dialog
(gnome?) which provides a "print to file" option, which provides to
choose both a save location and the output/save format (PDF, PS, SVG).
That might help some who missed the obvious...

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

Title:
  cups-pdf fails to generate file when user does not print to default
  ~/PDF (apparmor vs.cups-pdf inconsistency)

Status in apparmor package in Ubuntu:
  Invalid
Status in cups-pdf package in Ubuntu:
  Invalid
Status in cupsys package in Ubuntu:
  Won't Fix

Bug description:
  I had a working cups-pdf setup in Feisty, but after the upgrade to
  Gutsy it doesn't work anymore.

  The log file says:

  Mon Oct  1 10:05:49 2007  [STATUS] PDF creation successfully finished (nobody)
  Mon Oct  1 10:14:51 2007  [ERROR] failed to set file mode for PDF file (non 
fatal) (/home/hunzikea/Desktop/Report_a_bug.pdf)
  Mon Oct  1 10:14:51 2007  [STATUS] PDF creation successfully finished 
(hunzikea)

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

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

[Touch-packages] [Bug 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports

[Sebastien Bacher]

@Brian, it has been reuploaded with the previous changelog entry
included

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

Title:
  PA: Don't restore the streams to sinks/sources with only unavailable
  ports

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Incomplete
Status in pulseaudio source package in Disco:
  Fix Committed
Status in pulseaudio source package in Eoan:
  Fix Released

Bug description:
  SRU Document:

  [Impact]

  The Lenovo P520 machine has dual analogue codecs, so there are two
  sinks and two sources in the PA, one has the front headphone and front
  microphone, the other has the rear lineout, linein and rear
  microphone, and the rear microphone always shows up in the gnome-
  sound-setting, When we plug a microphone to front audio jack, there
  are two input devices: rear mic and front mic in the gnome-sound-
  setting, and suppose users select the the front mic to record sound
  via audio app like arecord, the front mic will be bond the arecord,
  after the front mic is unplugged, there is only one rear mic left in
  the gnome-sound-setting, but the binding will not be changed, the
  arecrod still bind to front mic, under this situation if users record
  sound via arecord, they will find they can't record any sound from any
  other input devices even they are listed in the gnome-sound-setting.
  This problem also happens to output devices too.

  [Test Case]

  After applying this patch, I did the same test: unplug the front mic,
  then use the arecord to record sound, the app can record sound from
  rear mic now. After I plug the front mic back, the arecord still
  record from front mic. Also did the similar test for output devices,
  it worked as expected too.

  [Regression Potential]

  Low, Just make a simple check when creating new streams
  (sink_input/source_output), If the restored device (sink/source) has
  ports and all ports are unavialble, it will not restore the binding,
  otherwise it will work as before.

  For the Bionic, This SRU also includes the fix of LP: #1556439, this
  fix is safe and is very low possible to introduce any regression too,
  because it just adds a sink-input/source-output state checking, if the
  sink-input/source-output is unlinking or unlinked, it is useless to
  move it to a new sink/source, furthermore it will trigger an assertion
  that make the pulseaudio crash, adding this check can fix this problem
  (LP: #1556439).

  [Other Info]

  No more info here

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1834138/+subscriptions

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

[Touch-packages] [Bug 1843565] Re: External USB mouse middle button SCROLL stoped work since kernel x86_64 Linux 4.15.0-60-generic

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

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

Title:
  External USB mouse middle button SCROLL stoped work since kernel
  x86_64 Linux 4.15.0-60-generic

Status in linux package in Ubuntu:
  New

Bug description:
  Hello, Devs!

  I found since kernel x86_64 Linux 4.15.0-60-generic at Ubuntu 18.04 my
  external USB mouse in Samsung ultrabook (NP900X4C) scroll not working!
  (with weel at middle mouse button)

  With touchpad scroll works fine.

  This is cat /proc/bus/input/devices info from 3 latest kernels (I have
  managed to boot different kernels thru Grub2 menu):

  Case - kernel: x86_64 Linux 4.15.0-58-generic
  (external USB mouse middle scroll button works well)

  # cat /proc/bus/input/devices
  [...]
  I: Bus=0003 Vendor=09da Product=000a Version=0110
  N: Name="A4Tech PS/2+USB Mouse"
  P: Phys=usb-:00:1d.0-1.2/input0
  S: 
Sysfs=/devices/pci:00/:00:1d.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:09DA:000A.0002/input/input12
  U: Uniq=
  H: Handlers=mouse1 event6
  B: PROP=0
  B: EV=17
  B: KEY=ff 0 0 0 0
  B: REL=343
  B: MSC=10

  Kernel: x86_64 Linux 4.15.0-60-generic
  (scroll not working with external mouse; touchpad scroll ok)

  # cat /proc/bus/input/devices
  [...]
  I: Bus=0003 Vendor=09da Product=000a Version=0110
  N: Name="A4Tech PS/2+USB Mouse"
  P: Phys=usb-:00:1d.0-1.2/input0
  S: 
Sysfs=/devices/pci:00/:00:1d.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:09DA:000A.0002/input/input12
  U: Uniq=
  H: Handlers=mouse1 event5
  B: PROP=0
  B: EV=17
  B: KEY=ff 0 0 0 0
  B: REL=143
  B: MSC=10

  Kernel: x86_64 Linux 4.15.0-62-generic
  (scroll not working with external mouse; touchpad scroll ok)

  # cat /proc/bus/input/devices
  [...]
  I: Bus=0003 Vendor=09da Product=000a Version=0110
  N: Name="A4Tech PS/2+USB Mouse"
  P: Phys=usb-:00:1d.0-1.2/input0
  S: 
Sysfs=/devices/pci:00/:00:1d.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:09DA:000A.0002/input/input12
  U: Uniq=
  H: Handlers=mouse1 event6
  B: PROP=0
  B: EV=17
  B: KEY=ff 0 0 0 0
  B: REL=143
  B: MSC=10

  And evtest /dev/input/event6 not shows any mouse scroll events (If I
  don't move mouse)

  But just PRESSING middle mouse button is OK:

  # evtest /dev/input/event6
  [...]
  Event: time 1568199190.499958, -- SYN_REPORT 
  Event: time 1568199190.587896, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90003
  Event: time 1568199190.587896, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 0

  This is my first bugreport, I hope additional info of my system setup
  is attached...

  I forgot to mention that if I log into fresh Ubuntu account in case of
  booting  x86_64 Linux 4.15.0-62-generic it doesn't helps - mouse
  scroll still not work.

  Scroll works only on x86_64 Linux 4.15.0-58-generic ;(


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
  Uname: Linux 4.15.0-62-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 11 13:20:43 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.32, 4.15.0-58-generic, x86_64: installed
   virtualbox, 5.2.32, 4.15.0-60-generic, x86_64: installed
   virtualbox, 5.2.32, 4.15.0-62-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0d3]
  InstallationDate: Installed on 2018-08-08 (398 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic 
root=UUID=6a8333d8-3e2a-4733-8f27-919b24d7586e ro
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P07AAC
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP07AAC:bd11/18/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONI

[Touch-packages] [Bug 1843600] Re: system became too slow and some applications may crash during work

[Daniel van Vugt]

Can you provide more specific details about the problem? There doesn't
seem to be enough information here for us to tell which component the
bug, if any, is in.

If something is crashing then please start by following these instructions:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

** Package changed: xorg (Ubuntu) => ubuntu

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

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

Title:
  system became too slow and some applications may crash during work

Status in Ubuntu:
  Incomplete

Bug description:
  am working on you tube channel and creating a video is a big task with
  this system. its too slow and working performance is not great since i
  have installed

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
  Uname: Linux 4.15.0-58-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Sep 11 20:24:15 2019
  DistUpgraded: 2019-04-13 17:46:44,751 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0597]
  InstallationDate: Installed on 2019-04-07 (157 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  MachineType: Dell Inc. Inspiron 3521
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic 
root=UUID=df0b088a-b8bd-4a72-a111-5f3fd1798a2e ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-04-13 (151 days ago)
  dmi.bios.date: 07/31/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 06RYX8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A14
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd07/31/2015:svnDellInc.:pnInspiron3521:pvrA14:rvnDellInc.:rn06RYX8:rvrA02:cvnDellInc.:ct8:cvrA14:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Inspiron 3521
  dmi.product.version: A14
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1844067] Re: Merge ibus 1.5.21-1~exp2 (main) from Debian experimental (main)

[Sebastien Bacher]

Thanks for the update Gunnar!

** Changed in: ibus (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Merge ibus 1.5.21-1~exp2 (main) from Debian experimental (main)

Status in ibus package in Ubuntu:
  Fix Committed

Bug description:
  Upstream released ibus 1.5.21 on 2019-08-23, and it's available in
  Debian experimental. It would be good if this could make it into eoan,
  so a recent IBus version gets 'tested' in 19.10 as a preparation for
  next LTS.

  Please see  for an overview of
  the changes in 1.5.20 and 1.5.21. They are both micro releases and
  don't introduce new features.

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

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

[Touch-packages] [Bug 1776381] Re: lxc-test-api-reboot will hang with autopkgtest

[Po-Hsu Lin]

** Tags added: ubuntu-lxc

** Tags added: bionic

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

Title:
  lxc-test-api-reboot will hang with autopkgtest

Status in ubuntu-kernel-tests:
  Confirmed
Status in lxc package in Ubuntu:
  New

Bug description:
  Steps:
    1. Deploy Bionic on a bare-metal system.
    2. Enable deb-src, install the autopkgtest package
    3. sudo autopkgtest lxc -- null

  Result:
    * The test will hang, a "reboot" lxc container will be created. The last 
message on the screen will be:
  make[1]: Entering directory '/tmp/autopkgtest.JxRLRE/build.bSQ/src'
  make[1]: Nothing to be done for 'all-am'.
  make[1]: Leaving directory '/tmp/autopkgtest.JxRLRE/build.bSQ/src'
    * Tried to connect to the "reboot" container with "sudo lxc-console 
reboot", but nothing there:
  Connected to tty 1
  Type  to exit the console,  to enter Ctrl+a 
itself
    * If you kill the job and run it again, this time the test will go on (fail 
with the lxc-test-api-reboot test, as the container has already been created)

  This issue can be reproduced on an amd64 box and a s390x zKVM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1776381/+subscriptions

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

[Touch-packages] [Bug 1844119] Re: readelf crash on 32bit, leading to abi-monitor testsuite regression

[Gianfranco Costamagna]

it works fine with binutils_2.32.51.20190821-1ubuntu1_i386.deb

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

Title:
  readelf crash on 32bit, leading to abi-monitor testsuite regression

Status in binutils package in Ubuntu:
  Confirmed

Bug description:
  readelf --debug-dump=info libjsoncpp.so.1.8.1
  to reproduce
  dpkg -l |grep binut
  ii  binutils2.32.51.20190905-0ubuntu1   i386 GNU 
assembler, linker and binary utilities
  ii  binutils-common:i3862.32.51.20190905-0ubuntu1   i386 Common 
files for the GNU assembler, linker and binary utilities
  ii  binutils-i686-linux-gnu 2.32.51.20190905-0ubuntu1   i386 GNU 
binary utilities, for i686-linux-gnu target
  ii  libbinutils:i3862.32.51.20190905-0ubuntu1   i386 GNU 
binary utilities (private shared library)

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

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

[Touch-packages] [Bug 1844119] [NEW] readelf crash on 32bit, leading to abi-monitor testsuite regression

[Gianfranco Costamagna]

Public bug reported:

readelf --debug-dump=info libjsoncpp.so.1.8.1
to reproduce
dpkg -l |grep binut
ii  binutils2.32.51.20190905-0ubuntu1   i386 GNU 
assembler, linker and binary utilities
ii  binutils-common:i3862.32.51.20190905-0ubuntu1   i386 Common 
files for the GNU assembler, linker and binary utilities
ii  binutils-i686-linux-gnu 2.32.51.20190905-0ubuntu1   i386 GNU binary 
utilities, for i686-linux-gnu target
ii  libbinutils:i3862.32.51.20190905-0ubuntu1   i386 GNU binary 
utilities (private shared library)

** Affects: binutils (Ubuntu)
 Importance: High
 Assignee: Matthias Klose (doko)
 Status: Confirmed

** Attachment added: "libjsoncpp.so.1.8.1"
   
https://bugs.launchpad.net/bugs/1844119/+attachment/5288980/+files/libjsoncpp.so.1.8.1

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

** Changed in: binutils (Ubuntu)
 Assignee: (unassigned) => Matthias Klose (doko)

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

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

Title:
  readelf crash on 32bit, leading to abi-monitor testsuite regression

Status in binutils package in Ubuntu:
  Confirmed

Bug description:
  readelf --debug-dump=info libjsoncpp.so.1.8.1
  to reproduce
  dpkg -l |grep binut
  ii  binutils2.32.51.20190905-0ubuntu1   i386 GNU 
assembler, linker and binary utilities
  ii  binutils-common:i3862.32.51.20190905-0ubuntu1   i386 Common 
files for the GNU assembler, linker and binary utilities
  ii  binutils-i686-linux-gnu 2.32.51.20190905-0ubuntu1   i386 GNU 
binary utilities, for i686-linux-gnu target
  ii  libbinutils:i3862.32.51.20190905-0ubuntu1   i386 GNU 
binary utilities (private shared library)

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

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

[Touch-packages] [Bug 1844119] Re: readelf crash on 32bit, leading to abi-monitor testsuite regression

[Gianfranco Costamagna]

Something in this diff regressed it and makes it crash.
http://launchpadlibrarian.net/440335350/binutils_2.32.51.20190821-1ubuntu1_2.32.51.20190905-0ubuntu1.diff.gz

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

Title:
  readelf crash on 32bit, leading to abi-monitor testsuite regression

Status in binutils package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  New

Bug description:
  readelf --debug-dump=info libjsoncpp.so.1.8.1
  to reproduce
  dpkg -l |grep binut
  ii  binutils2.32.51.20190905-0ubuntu1   i386 GNU 
assembler, linker and binary utilities
  ii  binutils-common:i3862.32.51.20190905-0ubuntu1   i386 Common 
files for the GNU assembler, linker and binary utilities
  ii  binutils-i686-linux-gnu 2.32.51.20190905-0ubuntu1   i386 GNU 
binary utilities, for i686-linux-gnu target
  ii  libbinutils:i3862.32.51.20190905-0ubuntu1   i386 GNU 
binary utilities (private shared library)

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

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

[Touch-packages] [Bug 1844119] Re: readelf crash on 32bit, leading to abi-monitor testsuite regression

[Gianfranco Costamagna]

manually downgrading glibc to 2.29 on i386, with newer binutils fails, so back 
to a binutils bug
ii  libc-bin  2.29-0ubuntu3   i386 GNU C 
Library: Binaries
ii  libc-dev-bin  2.29-0ubuntu3   i386 GNU C 
Library: Development binaries
ii  libc6:i3862.29-0ubuntu3   i386 GNU C 
Library: Shared libraries
ii  libc6-dev:i3862.29-0ubuntu3   i386 GNU C 
Library: Development Libraries and Header Files


G.

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

Title:
  readelf crash on 32bit, leading to abi-monitor testsuite regression

Status in binutils package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Invalid

Bug description:
  readelf --debug-dump=info libjsoncpp.so.1.8.1
  to reproduce
  dpkg -l |grep binut
  ii  binutils2.32.51.20190905-0ubuntu1   i386 GNU 
assembler, linker and binary utilities
  ii  binutils-common:i3862.32.51.20190905-0ubuntu1   i386 Common 
files for the GNU assembler, linker and binary utilities
  ii  binutils-i686-linux-gnu 2.32.51.20190905-0ubuntu1   i386 GNU 
binary utilities, for i686-linux-gnu target
  ii  libbinutils:i3862.32.51.20190905-0ubuntu1   i386 GNU 
binary utilities (private shared library)

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

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

[Touch-packages] [Bug 1844119] Re: readelf crash on 32bit, leading to abi-monitor testsuite regression

[Gianfranco Costamagna]

For some reasons, gdb seems to make me suspect of glibc 2.30...

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

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

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

Title:
  readelf crash on 32bit, leading to abi-monitor testsuite regression

Status in binutils package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Invalid

Bug description:
  readelf --debug-dump=info libjsoncpp.so.1.8.1
  to reproduce
  dpkg -l |grep binut
  ii  binutils2.32.51.20190905-0ubuntu1   i386 GNU 
assembler, linker and binary utilities
  ii  binutils-common:i3862.32.51.20190905-0ubuntu1   i386 Common 
files for the GNU assembler, linker and binary utilities
  ii  binutils-i686-linux-gnu 2.32.51.20190905-0ubuntu1   i386 GNU 
binary utilities, for i686-linux-gnu target
  ii  libbinutils:i3862.32.51.20190905-0ubuntu1   i386 GNU 
binary utilities (private shared library)

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/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 1844119] Re: readelf crash on 32bit, leading to abi-monitor testsuite regression

[Gianfranco Costamagna]

<65c00>   DW_AT_external: 1
<65c00>   DW_AT_name: (indirect string, offset: 0x1d277): 
_M_get_allocator
<65c04>   DW_AT_decl_file   : 2
<65c05>   DW_AT_decl_line   : 290
<65c07>   DW_AT_decl_column : 7
<65c08>   DW_AT_linkage_name: (indirect string, offset: 0xdb15): 
_ZNKSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE16_M_get_allocatorEv

Program received signal SIGSEGV, Segmentation fault.
0x56596128 in read_leb128 (data=0x87a81712 , length_return=0xd014, sign=0, end=0xf7dbecef "") at 
../../binutils/dwarf.c:336
336 ../../binutils/dwarf.c: No such file or directory.
(gdb) bt full
#0  0x56596128 in read_leb128 (data=0x87a81712 , length_return=0xd014, sign=0, end=0xf7dbecef "") at 
../../binutils/dwarf.c:336
result = 0
num_read = 0
shift = 0
byte = 0 '\000'
#1  0x56599e50 in read_uleb128 (end=0xf7dbecef "", length_return=, data=0x87a81711 ) at 
../../binutils/dwarf.c:2005
No locals.
#2  get_type_signedness (start=start@entry=0xf7cd1010 "\266X\006", 
data=0x87a81711 , 
end=end@entry=0xf7dbecef "", pointer_size=4, offset_size=4, 
dwarf_version=4, is_signed=0xd190, is_nested=1) at 
../../binutils/dwarf.c:2005
abbrev_number = 
bytes_read = 0
entry = 
attr = 
#3  0x56599f50 in get_type_signedness (start=start@entry=0xf7cd1010 
"\266X\006", data=0xf7ce1238 "", end=end@entry=0xf7dbecef "", pointer_size=4, 
offset_size=4, dwarf_version=4, is_signed=0xd190, 
is_nested=0) at ../../binutils/dwarf.c:2045
uvalue = 
abbrev_number = 
bytes_read = 1
entry = 
attr = 0x56640530
#4  0x5659b968 in read_and_display_attr_value (attribute=attribute@entry=73, 
form=form@entry=19, implicit_const=-1, start=0xf7cd1010 "\266X\006", 
data=, end=0xf7dbecef "", 
cu_offset=415930, pointer_size=4, offset_size=4, dwarf_version=, debug_info_p=0x0, do_loc=, section=0x56617880 
, this_set=0x0, 
delimiter=, level=) at 
../../binutils/dwarf.c:2732
is_signed = 0
uvalue = 66082
block_start = 
orig_data = 0xf7d36c1c "\"\002\001"
bytes_read = 4160392480
__PRETTY_FUNCTION__ = "read_and_display_attr_value"
#5  0x5659efb4 in read_and_display_attr (level=, this_set=0x0, 
section=0x56617880 , do_loc=0, debug_info_p=0x0, 
dwarf_version=4, offset_size=, 
pointer_size=4, cu_offset=415930, end=0xf7dbecef "", data=0xf7d36c1c 
"\"\002\001", start=0xf7cd1010 "\266X\006", implicit_const=, 
form=19, attribute=)
at ../../binutils/dwarf.c:3119
No locals.
#6  process_debug_info (section=0x56617880 , 
file=, abbrev_sec=abbrev, do_loc=0, do_types=) at 
../../binutils/dwarf.c:3646
bytes_read = 1
die_offset = 
do_printing = 1
abbrev_number = 
entry = 0x5663e9b0
attr = 
debug_info_p = 
hdrptr = 
sec_off = 
offset_size = 4
signature_low = 0
tags = 0xf7d36c1c "\"\002\001"
signature_high = 0
this_set = 0x0
abbrev_base = 
abbrev_size = 
initial_length_size = 
compunit = {cu_length = , cu_version = 4, 
cu_abbrev_offset = , cu_pointer_size = , 
cu_unit_type = }
level = 
last_level = 4
saved_level = -1
cu_offset = 415930
type_offset = 
start = 
end = 0xf7dbecef ""
section_begin = 
unit = 1
num_units = 
__PRETTY_FUNCTION__ = "process_debug_info"
#7  0x5658b464 in display_debug_section (filedata=, 
section=0x566202b0, shndx=30) at ../../binutils/readelf.c:14291
secondary = 
id = info
display = 0x56617880 
sec = 0x56617880 
length = 
i = 3
name = 
print_name = 
result = 1
name = 
print_name = 
length = 
result = 
i = 
id = 
display = 
sec = 
secondary = 
#8  process_section_contents (filedata=) at 
../../binutils/readelf.c:14382
dump = 4 '\004'
section = 0x566202b0
i = 30
res = 1
#9  0x5658c915 in process_section_contents (filedata=0x5661e1d0) at 
../../binutils/readelf.c:1
section = 
i = 
res = 1
section = 
i = 
res = 
dump = 
#10 process_object (filedata=) at ../../binutils/readelf.c:1
have_separate_files = 0
i = 
res = 1
have_separate_files = 
i = 
res = 
__PRETTY_FUNCTION__ = "process_object"
d = 
g = 
next = 
#11 process_object (filedata=) at ../../binutils/readelf.c:19915
have_separate_files = 
i = 
__PRETTY_FUNCTION__ = "process_object"
d = 
g = 
next = 
#12 0x5655a2a5 in process_file (file_name=0xdae6 "libjsoncpp.so.1.8.1") at 
../../binutils/readelf.c:20429
filedata = 0x5661e1d0
statbuf = {st_dev = 66306, __pad1 = 1, __st_ino = 2393533, 

[Touch-packages] [Bug 1829364] Re: Will not play sound via HDMI using 48000 Hz sample rate

[Jarno Suni]

** Description changed:

  Does not play sound when playing file that has 48000 Hz sample rate via
  sink output:iec958-stereo
+ 
+ Note that the device (HP 8510w, having NVIDIA Quadro FX 570M graphics
+ adapter) does not have real HDMI audio, but audio is somehow wired from
+ motherboard's S/PDIF to HDMI explaining the sink name. Anyway, in the
+ attached AlsaInfo.txt there is a device "Node 0x02 [Audio Output] wcaps
+ 0x30311: Stereo Digital" that has "rates [0x60]: 44100 48000".
  
  Workaround:
  Set
  alternate-sample-rate = 44100
  in /etc/pulse/daemon.conf and restart pulseaudio
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jarnos 1283 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu May 16 12:39:15 2019
  InstallationDate: Installed on 2019-05-08 (7 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MVD Ver. F.20
  dmi.board.name: 30C5
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard

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

Title:
  Will not play sound via HDMI using 48000 Hz sample rate

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Does not play sound when playing file that has 48000 Hz sample rate
  via sink output:iec958-stereo

  Note that the device (HP 8510w, having NVIDIA Quadro FX 570M graphics
  adapter) does not have real HDMI audio, but audio is somehow wired
  from motherboard's S/PDIF to HDMI explaining the sink name. Anyway, in
  the attached AlsaInfo.txt there is a device "Node 0x02 [Audio Output]
  wcaps 0x30311: Stereo Digital" that has "rates [0x60]: 44100 48000".

  Workaround:
  Set
  alternate-sample-rate = 44100
  in /etc/pulse/daemon.conf and restart pulseaudio

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jarnos 1283 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu May 16 12:39:15 2019
  InstallationDate: Installed on 2019-05-08 (7 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MVD Ver. F.20
  dmi.board.name: 30C5
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1843819] Re: Volume scaling is incorrect for Logitech H600 (046d:0a29): alsamixer @ 0% where pulse volume @ 50%

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1843819

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

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

Title:
  Volume scaling is incorrect for Logitech H600 (046d:0a29): alsamixer @
  0% where pulse volume @ 50%

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When the volume is set to around 50% in PulseAudio (using the Ubuntu
  Sound preferences screen but cross-checked by simply viewing with
  pavucontrol) the alsamixer volume is set to 0%. I can see the volume
  rise quickly as the volume is raised past 50% in the Sound preferences
  screen.

  This occurs at least for the Logitech H600 USB device:
  Bus 001 Device 011: ID 046d:0a29 Logitech, Inc. H600 [Wireless Headset]

  The other audio devices behave "correctly" where 0% is silent and 100%
  is maximum volume.

  This confused me because the volume was set to 50% (I'll frequently
  reset headset volume to 30-50% to protect my ears) and thought audio
  was broken at first because I wasn't getting any sound at all.

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

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

[Touch-packages] [Bug 1843869] Re: System crashes randomly each time with different application

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

** Package changed: xorg (Ubuntu) => ubuntu

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

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

Title:
  System crashes randomly each time with different application

Status in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 16.04.6 LTS
  Release:  16.04

  Package version: 7.7+13ubuntu3.1

  Fresh system install with Ubuntu 16.04 crashes the system after some
  time. We are running high CPU intensive jobs, but CPU usage never
  crosses 80%.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.15.0-62-generic 4.15.0-62.69~16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-62.69~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-62-generic x86_64
  NonfreeKernelModules: snapapi26
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  Date: Fri Sep 13 11:46:12 2019
  InstallationDate: Installed on 2019-09-11 (1 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1841295] Re: Update to 2.3.0?

[Sebastien Bacher]

** Tags added: version-blocked-ff

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

Title:
  Update to 2.3.0?

Status in cups package in Ubuntu:
  Triaged

Bug description:
  There is a new cups version out, likely not for this cycle though?

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

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

[Touch-packages] [Bug 1843927] Re: Missing graphics drivers for AMD Ryzen 5 with Radeon Vega 8

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1843927

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Tags added: disco

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

** Summary changed:

- Missing graphics drivers for AMD Ryzen 5 with Radeon Vega 8
+ HDMI monitor not detected [AMD Ryzen 5 with Radeon Vega 8]

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

Title:
  HDMI monitor not detected [AMD Ryzen 5 with Radeon Vega 8]

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I have recently installed Ubuntu 19.04 on an ASUS TUF Gaming FX505DY
  laptop.  The laptop has a AMD Ryzen 5 with Radeon Vega 8 processor.

  No warnings where raised during the installation process regarding
  problems with the graphics driver.  When I connected a HDMI connected
  monitor I found it did not work.

  I have attached the graphics driver logs

  ==
  cat /var/log/gpu-manager.log

  log_file: /var/log/gpu-manager.log
  last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
  new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
  can't access /run/u-d-c-nvidia-was-loaded file
  can't access /opt/amdgpu-pro/bin/amdgpu-pro-px
  Looking for nvidia modules in /lib/modules/5.0.0-27-generic/updates/dkms
  Looking for amdgpu modules in /lib/modules/5.0.0-27-generic/updates/dkms
  Is nvidia loaded? no
  Was nvidia unloaded? no
  Is nvidia blacklisted? no
  Is intel loaded? no
  Is radeon loaded? no
  Is radeon blacklisted? no
  Is amdgpu loaded? no
  Is amdgpu blacklisted? no
  Is amdgpu versioned? no
  Is amdgpu pro stack? no
  Is nouveau loaded? no
  Is nouveau blacklisted? no
  Is nvidia kernel module available? no
  Is amdgpu kernel module available? no
  Vendor/Device Id: 1002:67ef
  BusID "PCI:1@0:0:0"
  Is boot vga? no
  Error: can't access /sys/bus/pci/devices/:01:00.0/driver
  The device is not bound to any driver.
  Vendor/Device Id: 1002:15d8
  BusID "PCI:5@0:0:0"
  Is boot vga? yes
  Error: can't access /sys/bus/pci/devices/:05:00.0/driver
  The device is not bound to any driver.
  Error : Failed to open /dev/dri
  Error : Failed to open /dev/dri
  Error : Failed to open /dev/dri
  Error : Failed to open /dev/dri
  Does it require offloading? no
  last cards number = 2
  Has amd? yes
  Has intel? no
  Has nvidia? no
  How many cards? 2
  Has the system changed? No
  Unsupported discrete card vendor: 1002
  Nothing to do

  
==  
sudo lshw -C display
*-display UNCLAIMED   
 description: Display controller
 product: Baffin [Radeon RX 460/560D / Pro 450/455/460/555/560]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:01:00.0
 version: e5
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi cap_list
 configuration: latency=0
 resources: memory:e000-efff memory:f000-f01f 
ioport:f000(size=256) memory:fea0-fea3 memory:fea4-fea5
*-display UNCLAIMED
 description: VGA compatible controller
 product: Picasso
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:05:00.0
 version: c2
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
 configuration: latency=0
 resources: memory:c000-cfff memory:d000-d01f 
ioport:c000(size=256) memory:fe50-fe57

  
  
*
  QUESTIONS

  1.  Why is the problem with unsupported drivers not flagged during the
  installation process?  The default driver does work for the laptop's
  monitor, but will not drive a second monitor attached to the HDMI port

  2.  I have seen reference to a general purpose AMD graphics driver,
  but there is no reference to this driver being supported on Ubuntu
  19.04.  If I went ahead and attempted to install the general purpose
  graphics driver, how would I back it out if it did not work.

  I have raised this issue as a "question", but I think it is probably a
  bug but I could not find out how to raise a bug associated with a lack
  of device drivers.

To manage notifications about this bug go to:
https://bugs

[Touch-packages] [Bug 1843743] Re: klibc ftbfs in eoan

[Francis Ginther]

** Tags added: id-5d7f798147e05c832903635b

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

Title:
  klibc ftbfs in eoan

Status in klibc package in Ubuntu:
  Confirmed
Status in klibc source package in Eoan:
  Confirmed

Bug description:
  https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan-
  amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz

  gcc -Wp,-MD,usr/klibc/.sigsuspend.o.d  -nostdinc -iwithprefix include 
-I/<>/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 
-I/<>/usr/include/bits64 -Iusr/include/bits64 
-I/<>/usr/klibc/../include -Iusr/klibc/../include 
-I/<>/usr/include -Iusr/include -I/<>/linux/include 
-Ilinux/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 
-fno-stack-protector -fwrapv -fno-PIE -ggdb -m64 -Os -fomit-frame-pointer 
-mno-sse -falign-functions=1 -falign-jumps=1 -falign-loops=1 
-fno-asynchronous-unwind-tables -W -Wall -Wno-sign-compare 
-Wno-unused-parameter -c -o usr/klibc/sigsuspend.o usr/klibc/sigsuspend.c
  usr/klibc/sigsuspend.c:8:10: fatal error: klibc/havesyscall.h: No such file 
or directory
  8 | #include 
|  ^
  compilation terminated.
  make[4]: *** [/<>/scripts/Kbuild.klibc:252: 
usr/klibc/sigsuspend.o] Error 1
  make[3]: *** [/<>/./Kbuild:9: all] Error 2
  make[2]: *** [Makefile:118: klibc] Error 2

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

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

[Touch-packages] [Bug 1844045] Re: Screen flickering during boot and doesn't boot in for a log time

[Daniel van Vugt]

Could you please provide a video of the flickering?

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

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

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

Title:
  Screen flickering during boot and doesn't boot in for a log time

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The Wifi sudddenly stopped detecting which made me restart the system
  but at boot time the screen started flickering with ubuntu load screen
  and is taking long time to boot. Used recovery mode to get into the
  system but the same issue occurs everytime I restart or switch on the
  system. The system doesn't seem to suspend on lid close anymore.

  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
  Uname: Linux 4.15.0-62-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 15 14:51:05 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:0794]
  InstallationDate: Installed on 2018-12-30 (258 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Vostro 15-3568
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic 
root=UUID=f6ce104c-4c98-4ee1-ba1b-68a51cd38131 ro recovery nomodeset
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.01
  dmi.board.name: 01Y1RD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.01:bd08/03/2016:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn01Y1RD:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Vostro 15-3568
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1829364] Re: Will not play sound via HDMI using 48000 Hz sample rate

[Jarno Suni]

** Description changed:

  Does not play sound when playing file that has 48000 Hz sample rate via
- sink output:iec958-stereo
+ sink output:iec958-stereo. This is when using proprietary nvidia-340
+ driver; when using nouveau driver, HDMI is not even recognized (Bug
+ #1844129).
  
  Note that the device (HP 8510w, having NVIDIA Quadro FX 570M graphics
  adapter) does not have real HDMI audio, but audio is somehow wired from
  motherboard's S/PDIF to HDMI explaining the sink name. Anyway, in the
  attached AlsaInfo.txt there is a device "Node 0x02 [Audio Output] wcaps
  0x30311: Stereo Digital" that has "rates [0x60]: 44100 48000".
  
  Workaround:
  Set
  alternate-sample-rate = 44100
  in /etc/pulse/daemon.conf and restart pulseaudio
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jarnos 1283 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu May 16 12:39:15 2019
  InstallationDate: Installed on 2019-05-08 (7 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MVD Ver. F.20
  dmi.board.name: 30C5
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard

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

Title:
  Will not play sound via HDMI using 48000 Hz sample rate

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Does not play sound when playing file that has 48000 Hz sample rate
  via sink output:iec958-stereo. This is when using proprietary
  nvidia-340 driver; when using nouveau driver, HDMI is not even
  recognized (Bug #1844129).

  Note that the device (HP 8510w, having NVIDIA Quadro FX 570M graphics
  adapter) does not have real HDMI audio, but audio is somehow wired
  from motherboard's S/PDIF to HDMI explaining the sink name. Anyway, in
  the attached AlsaInfo.txt there is a device "Node 0x02 [Audio Output]
  wcaps 0x30311: Stereo Digital" that has "rates [0x60]: 44100 48000".

  Workaround:
  Set
  alternate-sample-rate = 44100
  in /etc/pulse/daemon.conf and restart pulseaudio

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jarnos 1283 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu May 16 12:39:15 2019
  InstallationDate: Installed on 2019-05-08 (7 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MVD Ver. F.20
  dmi.board.name: 30C5
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1844132] [NEW] FFe: Mesa 19.2.0

[Timo Aaltonen]

Public bug reported:

It would be great to get 19.2.0 in eoan, though it's release cycle has
slipped. It's working fine on a typical desktop use here on i915 (Kaby
Lake). It would also migrate to llvm-9.

It is currently at rc3, and final version is expected to arrive next
week (week 39).

New features:

Support for AMD Navi

GL_ARB_post_depth_coverage on radeonsi (Navi)
GL_ARB_seamless_cubemap_per_texture on etnaviv (if GPU supports 
SEAMLESS_CUBE_MAP)
GL_EXT_shader_image_load_store on radeonsi (with LLVM >= 10)
GL_EXT_shader_samples_identical on iris and radeonsi (if using NIR)
GL_EXT_texture_shadow_lod on i965, iris
EGL_EXT_platform_device
VK_AMD_buffer_marker on radv
VK_EXT_index_type_uint8 on radv
VK_EXT_post_depth_coverage on radv
VK_EXT_queue_family_foreign on radv
VK_EXT_sample_locations on radv
VK_EXT_shader_demote_to_helper_invocation on Intel.
VK_KHR_depth_stencil_resolve on radv
VK_KHR_imageless_framebuffer on radv
VK_KHR_shader_atomic_int64 on radv
VK_KHR_uniform_buffer_standard_layout on radv

(note: iris is the new DRI driver for newer Intel, not enabled by
default yet)

** Affects: mesa (Ubuntu)
 Importance: Undecided
 Assignee: Timo Aaltonen (tjaalton)
 Status: Confirmed

** Affects: mesa (Ubuntu Eoan)
 Importance: Undecided
 Assignee: Timo Aaltonen (tjaalton)
 Status: Confirmed

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

Title:
  FFe: Mesa 19.2.0

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Eoan:
  Confirmed

Bug description:
  It would be great to get 19.2.0 in eoan, though it's release cycle has
  slipped. It's working fine on a typical desktop use here on i915 (Kaby
  Lake). It would also migrate to llvm-9.

  It is currently at rc3, and final version is expected to arrive next
  week (week 39).

  New features:

  Support for AMD Navi

  GL_ARB_post_depth_coverage on radeonsi (Navi)
  GL_ARB_seamless_cubemap_per_texture on etnaviv (if GPU supports 
SEAMLESS_CUBE_MAP)
  GL_EXT_shader_image_load_store on radeonsi (with LLVM >= 10)
  GL_EXT_shader_samples_identical on iris and radeonsi (if using NIR)
  GL_EXT_texture_shadow_lod on i965, iris
  EGL_EXT_platform_device
  VK_AMD_buffer_marker on radv
  VK_EXT_index_type_uint8 on radv
  VK_EXT_post_depth_coverage on radv
  VK_EXT_queue_family_foreign on radv
  VK_EXT_sample_locations on radv
  VK_EXT_shader_demote_to_helper_invocation on Intel.
  VK_KHR_depth_stencil_resolve on radv
  VK_KHR_imageless_framebuffer on radv
  VK_KHR_shader_atomic_int64 on radv
  VK_KHR_uniform_buffer_standard_layout on radv

  (note: iris is the new DRI driver for newer Intel, not enabled by
  default yet)

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

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

[Touch-packages] [Bug 1844132] Re: FFe: Mesa 19.2.0

[Timo Aaltonen]

packages for testing: ppa:canonical-x/x-staging

** Changed in: mesa (Ubuntu)
   Status: New => In Progress

** Changed in: mesa (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

** Description changed:

  It would be great to get 19.2.0 in eoan, though it's release cycle has
  slipped. It's working fine on a typical desktop use here on i915 (Kaby
  Lake). It would also migrate to llvm-9.
  
  New features:
+ 
+ Support for AMD Navi
  
  GL_ARB_post_depth_coverage on radeonsi (Navi)
  GL_ARB_seamless_cubemap_per_texture on etnaviv (if GPU supports 
SEAMLESS_CUBE_MAP)
  GL_EXT_shader_image_load_store on radeonsi (with LLVM >= 10)
  GL_EXT_shader_samples_identical on iris and radeonsi (if using NIR)
  GL_EXT_texture_shadow_lod on i965, iris
  EGL_EXT_platform_device
  VK_AMD_buffer_marker on radv
  VK_EXT_index_type_uint8 on radv
  VK_EXT_post_depth_coverage on radv
  VK_EXT_queue_family_foreign on radv
  VK_EXT_sample_locations on radv
  VK_EXT_shader_demote_to_helper_invocation on Intel.
  VK_KHR_depth_stencil_resolve on radv
  VK_KHR_imageless_framebuffer on radv
  VK_KHR_shader_atomic_int64 on radv
  VK_KHR_uniform_buffer_standard_layout on radv
  
  (note: iris is the new DRI driver for newer Intel, not enabled by
  default yet)

** Description changed:

  It would be great to get 19.2.0 in eoan, though it's release cycle has
  slipped. It's working fine on a typical desktop use here on i915 (Kaby
  Lake). It would also migrate to llvm-9.
+ 
+ It is currently at rc3, and final version is expected to arrive next
+ week (week 39).
  
  New features:
  
  Support for AMD Navi
  
  GL_ARB_post_depth_coverage on radeonsi (Navi)
  GL_ARB_seamless_cubemap_per_texture on etnaviv (if GPU supports 
SEAMLESS_CUBE_MAP)
  GL_EXT_shader_image_load_store on radeonsi (with LLVM >= 10)
  GL_EXT_shader_samples_identical on iris and radeonsi (if using NIR)
  GL_EXT_texture_shadow_lod on i965, iris
  EGL_EXT_platform_device
  VK_AMD_buffer_marker on radv
  VK_EXT_index_type_uint8 on radv
  VK_EXT_post_depth_coverage on radv
  VK_EXT_queue_family_foreign on radv
  VK_EXT_sample_locations on radv
  VK_EXT_shader_demote_to_helper_invocation on Intel.
  VK_KHR_depth_stencil_resolve on radv
  VK_KHR_imageless_framebuffer on radv
  VK_KHR_shader_atomic_int64 on radv
  VK_KHR_uniform_buffer_standard_layout on radv
  
  (note: iris is the new DRI driver for newer Intel, not enabled by
  default yet)

** Also affects: mesa (Ubuntu Eoan)
   Importance: Undecided
 Assignee: Timo Aaltonen (tjaalton)
   Status: Confirmed

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

Title:
  FFe: Mesa 19.2.0

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Eoan:
  Confirmed

Bug description:
  It would be great to get 19.2.0 in eoan, though it's release cycle has
  slipped. It's working fine on a typical desktop use here on i915 (Kaby
  Lake). It would also migrate to llvm-9.

  It is currently at rc3, and final version is expected to arrive next
  week (week 39).

  New features:

  Support for AMD Navi

  GL_ARB_post_depth_coverage on radeonsi (Navi)
  GL_ARB_seamless_cubemap_per_texture on etnaviv (if GPU supports 
SEAMLESS_CUBE_MAP)
  GL_EXT_shader_image_load_store on radeonsi (with LLVM >= 10)
  GL_EXT_shader_samples_identical on iris and radeonsi (if using NIR)
  GL_EXT_texture_shadow_lod on i965, iris
  EGL_EXT_platform_device
  VK_AMD_buffer_marker on radv
  VK_EXT_index_type_uint8 on radv
  VK_EXT_post_depth_coverage on radv
  VK_EXT_queue_family_foreign on radv
  VK_EXT_sample_locations on radv
  VK_EXT_shader_demote_to_helper_invocation on Intel.
  VK_KHR_depth_stencil_resolve on radv
  VK_KHR_imageless_framebuffer on radv
  VK_KHR_shader_atomic_int64 on radv
  VK_KHR_uniform_buffer_standard_layout on radv

  (note: iris is the new DRI driver for newer Intel, not enabled by
  default yet)

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

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

[Touch-packages] [Bug 1801540]

[jg.staffel]

(In reply to Takashi Iwai from comment #271)

(In reply to Takashi Iwai from comment #249)
> (In reply to al from comment #248)
> > Thanks that did it works great now!
> 
> OK, I'll add the entry for 1022:1487 in the upstream, too.

The patch was backported to the 4.19.67 kernel.

With this and latest Gentoo stable kernel 4.19.72 and net-im/telegram-
desktop-bin-1.8.8 my companion hear myself while audio call. No echo
cancellation.

ASRock Fatal1ty B450 Gaming K4
ALC892, [1022:1457] subsys [1849:9893]

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

Title:
  Microphone distorted sound on ALC892/1220 on AMD chipsets

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  Not sure if I'll report this upstream but there is definitely an issue
  with microphone recording on my desktop, this is not happening on my
  laptop which has a different codec.

  Already tried all workarounds possible, no luck. Only with my desktop
  with this particular motherboard. No issues in Windows, the sound
  recorded in there is distorted and has some static and robotic tone on
  high-pitch.

  alsa-info on the attachments

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

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

[Touch-packages] [Bug 1843999] Re: Printing fails since last update

[Adrian Midgley]

Removed and recreated printer.  No change.
Removed plugins - not Gutenprint of coure - no change.

Starting gimp in a terminal with --verbose leads to

Initializing plug-in: 
'/usr/lib/gimp/2.0/plug-ins/file-rawtherapee/file-rawtherapee'
Initializing plug-in: '/usr/lib/gimp/2.0/plug-ins/file-darktable/file-darktable'
Starting extension: 'extension-script-fu'
INIT: gui_restore_after_callback
Parsing '/home/akm/.config/GIMP/2.10/menurc'
Parsing '/home/akm/.config/GIMP/2.10/action-history'
Parsing '/home/akm/.config/GIMP/2.10/devicerc'
Parsing '/home/akm/.config/GIMP/2.10/controllerrc'
loading menu '/usr/share/gimp/2.0/menus/image-menu.xml' for /image-menubar
/usr/lib/gimp/2.0/plug-ins/gutenprint: fatal error: Segmentation fault

The last line is the one which appears after an effort to print.

I'm stuck so far.

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

Title:
  Printing fails since last update

Status in cups package in Ubuntu:
  New

Bug description:
  I use Gimp-gutenprint to print photographs via CUPS to an Epson R2400
  It fails each time, reporting filter failure.
  I forget what the last update was, yesterday or day before, but it is only 
since then.

  ESC/P utility can print a nozzle check from the printer, that's
  working.

  CUPS seems to be telling me that a filter failed, due to a mismatch
  between device colour model and profile.

  I've tried with no profile in the setup:printer dialogue, no
  different.

  Where should I look?
  Is it likely to be a change in the last update?

  
  I'm on 18.04 LTS on an AMD processor with multiple screens on an Nvidia card.


  W [14/Sep/2019:00:10:31 +0100] AddProfile failed:
  org.freedesktop.ColorManager.Device.ProfileAlreadyAdded:profile object
  path \'/org/freedesktop/ColorManager/profiles/Stylus_Photo_R2400_RGB__\'
  has already been added
  E [14/Sep/2019:00:13:12 +0100] [Job 347] Aborting job because it has no files.
  E [14/Sep/2019:00:22:11 +0100] [Job 348] Aborting job because it has no files.
  E [14/Sep/2019:00:29:51 +0100] [Job 350] Job stopped due to filter
  errors; please consult the error_log file for details.
  D [14/Sep/2019:00:29:51 +0100] [Job 350] The following messages were
  recorded from 00:29:51 to 00:29:51
  D [14/Sep/2019:00:29:51 +0100] [Job 350] Applying default options...
  D [14/Sep/2019:00:29:51 +0100] [Job 350] Adding start banner page "none".
  D [14/Sep/2019:00:29:51 +0100] [Job 350] Adding end banner page "none".
  D [14/Sep/2019:00:29:51 +0100] [Job 350] File of type application/pdf
  queued by "akm".
  D [14/Sep/2019:00:29:51 +0100] [Job 350] hold_until=0
  D [14/Sep/2019:00:29:51 +0100] [Job 350] Queued on
  "Stylus-Photo-R2400" by "akm".
  D [14/Sep/2019:00:29:51 +0100] [Job 350] time-at-processing=1568417391
  D [14/Sep/2019:00:29:51 +0100] [Job 350] 3 filters for job:
  D [14/Sep/2019:00:29:51 +0100] [Job 350] pdftopdf (application/pdf to
  application/vnd.cups-pdf, cost 66)
  D [14/Sep/2019:00:29:51 +0100] [Job 350] gstoraster
  (application/vnd.cups-pdf to application/vnd.cups-raster, cost 99)
  D [14/Sep/2019:00:29:51 +0100] [Job 350] rastertogutenprint.5.2
  (application/vnd.cups-raster to printer/Stylus-Photo-R2400, cost 100)
  D [14/Sep/2019:00:29:51 +0100] [Job 350] job-sheets=none,none
  D [14/Sep/2019:00:29:51 +0100] [Job 350] argv[0]="Stylus-Photo-R2400"
  D [14/Sep/2019:00:29:51 +0100] [Job 350] argv[1]="350"
  D [14/Sep/2019:00:29:51 +0100] [Job 350] argv[2]="akm"
  D [14/Sep/2019:00:29:51 +0100] [Job 350]
  argv[3]="[8-channel-printer-a] (imported)"
  D [14/Sep/2019:00:29:51 +0100] [Job 350] argv[4]="1"
  D [14/Sep/2019:00:29:51 +0100] [Job 350] argv[5]="StpMagentaGamma=None
  StpFineMagentaBalance=None StpFineHGray5Trans=None StpPlatenGap=1
  ColorModel=Gray StpCyanBalance=None StpFineBlackGamma=None
  StpLightMagentaValue=None StpHGray4Scale=None StpBlackDensity=None
  StpMagentaDensity=None StpHGray3Value=None StpHGray1Trans=None
  StpFineLightCyanTrans=None StpInkLimit=None StpFineHGray4Trans=None
  StpColorCorrection=None StpLightMagentaScale=None
  Resolution=1444x720dpi StpHGray3Scale=None StpPrintMethod=None
  StpQuality=Best StpHGray2Value=None StpMagentaBalance=None
  StpFineGamma=None StpFineHGray5Value=None StpBandEnhancement=0
  StpBrightness=None StpFineHGray3Trans=None StpFineCyanGamma=None
  StpDropSize1=None StpDropSize2=None StpFineCyanDensity=None
  StpDropSize3=None StpHGray2Scale=None StpLightCyanTrans=None
  StpHGray1Value=None StpFineHGray5Scale=None StpFineLightCyanValue=None
  StpFineContrast=None StpFineHGray4Value=None StpFineBrightness=None
  StpFineYellowDensity=None StpFineHGray2Trans=None
  StpYellowDensity=None StpGamma=None StpFineCyanBalance=None
  StpFineBlackTrans=None StpFineLightCyanScale=None StpHGray1Scale=None
  StpFineHGray4Scale=None StpFineYellowBalance=None
  StpFineSubchannelCutoff=None StpFineHGray3Value=None StpFullBle

[Touch-packages] [Bug 1830796] Re: [Bionic][ARM64]Failure debugging linux kernel

[Manoj Iyer]

== Proposed testing results ==

ubuntu@recht:~$ apt policy gdb
gdb:
  Installed: 8.1-0ubuntu3.1
  Candidate: 8.1-0ubuntu3.1
  Version table:
 *** 8.1-0ubuntu3.1 500
500 http://ports.ubuntu.com/ubuntu-ports bionic-proposed/main arm64 
Packages
100 /var/lib/dpkg/status
 8.1-0ubuntu3 500
500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages
ubuntu@recht:~$

ubuntu@recht:~$ sudo gdb /usr/lib/debug/boot/vmlinux-4.15.0-62-generic 
/proc/kcore
GNU gdb (Ubuntu 8.1-0ubuntu3.1) 8.1.0.20180409-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "aarch64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/debug/boot/vmlinux-4.15.0-62-generic...done.

warning: core file may not match specified executable file.
[New process 1]
Core was generated by `BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic 
root=UUID=4e57d549-7669-4f93-82d9-8c'.
#0  0x in ?? ()
(gdb) p jiffies_64
$1 = 4295689599
(gdb)

** Tags removed: verification-needed
** Tags added: verification-done-bionic

** Tags removed: verification-needed-bionic
** Tags added: verification-done

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

Title:
  [Bionic][ARM64]Failure debugging linux kernel

Status in gdb package in Ubuntu:
  Fix Released
Status in gdb source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  GDB fails to debug ARM64 vmlinux debug image with proc/kcore information. For 
example it is unable to print values of variables like 'jiffies_64'.

  [Test]
  # gdb /usr/lib/debug/boot/vmlinux-4.18.0-20-generic  /proc/kcore
  [New process 1]
  Core was generated by `BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic 
root=UUID=edb5e5a7-8272-4e13-aa25-37'.
  #0  0x in ?? ()
  (gdb) p jiffies_64
  Cannot access memory at address 0x09616980
  (gdb)

  [Fix]
  This issue was fixed upstream (git://sourceware.org/git/binutils-gdb.git) by 
the following patch:
  8727de56b0  Fix tagged pointer support

  [Regression Potential]
  The risk of regression after applying this patch could be to architectures 
other than ARM64 due to changes to gdb/util.c. Please see comment #2 where I 
have tested the PPA package on a ppc64el system and found it does not introduce 
any regressions.

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

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

[Touch-packages] [Bug 1842383] Re: openssl 1.1.1 memory overuse/leak

[Sergey]

** Attachment added: "1.1.0g"
   
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1842383/+attachment/5289013/+files/1.1.0g.png

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

Title:
  openssl 1.1.1 memory overuse/leak

Status in openssl package in Ubuntu:
  New

Bug description:
  [Impact]

  At some point in the past do_ssl3_write() used to return the number of
  bytes written, or a value <= 0 on error.

  With libssl1.11 it now just returns a success/
  error code and writes the number of bytes written to |tmpwrit|.

  The SSL_MODE_RELEASE_BUFFERS code was still looking at the return code
  for the number of bytes written rather than |tmpwrit|. This has the effect
  that the buffers are not released when they are supposed to be.

  Thus such software as nginx currenty use significantly more memory
  compared to libssl1.0.

  [Test Case]

  Use 'top' to measure the memory usage by nginx with ssl configured.

  Example:

  No memory overuse:
  ii libssl1.1:amd64 1.1.0g-2ubuntu4 amd64 Secure Sockets Layer toolkit - 
shared libraries
  https://launchpadlibrarian.net/442818951/1.1.0g.png

  2,5x memory overuse:
  ii libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.4 amd64 Secure Sockets Layer 
toolkit - shared libraries
  https://launchpadlibrarian.net/442819146/1.1.1.png

  [Regression Potential]

  Low. This particular fix is tiny
  (https://git.openssl.org/?p=openssl.git;a=commitdiff;h=f2bb79a) and
  has been released and used in a couple of upstream openssl versions
  already without issue.

  [Other Info]
   
  The fix has been tested by nginx team and it solved the memory overuse issue.

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

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

[Touch-packages] [Bug 1842383] Re: openssl 1.1.1 memory overuse/leak

[Sergey]

** Attachment added: "1.1.1"
   
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1842383/+attachment/5289014/+files/1.1.1.png

** Description changed:

- Hi,
+ [Impact]
  
- DISTRIB_ID=Ubuntu
- DISTRIB_RELEASE=18.04
- DISTRIB_CODENAME=bionic
- DISTRIB_DESCRIPTION="Ubuntu 18.04.3 LTS"
+ At some point in the past do_ssl3_write() used to return the number of
+ bytes written, or a value <= 0 on error.
  
- With dynamic linking libssl1.1 in nginx we see a lot memory use compared
- to libssl1.0.
+ With libssl1.11 it now just returns a success/
+ error code and writes the number of bytes written to |tmpwrit|.
+ 
+ The SSL_MODE_RELEASE_BUFFERS code was still looking at the return code
+ for the number of bytes written rather than |tmpwrit|. This has the effect
+ that the buffers are not released when they are supposed to be.
+ 
+ Thus such software as nginx currenty use significantly more memory
+ compared to libssl1.0.
+ 
+ [Test Case]
+ 
+ Use 'top' to measure the memory usage by nginx with ssl configured.
+ 
+ Example:
  
  No memory overuse:
- ii  libssl1.1:amd64   1.1.0g-2ubuntu4   
amd64Secure Sockets Layer toolkit - shared libraries
+ ii libssl1.1:amd64 1.1.0g-2ubuntu4 amd64 Secure Sockets Layer toolkit - 
shared libraries
+ https://launchpadlibrarian.net/442818951/1.1.0g.png
  
  2,5x memory overuse:
- ii  libssl1.1:amd64   1.1.1-1ubuntu2.1~18.04.4  
amd64Secure Sockets Layer toolkit - shared libraries
+ ii libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.4 amd64 Secure Sockets Layer 
toolkit - shared libraries
+ https://launchpadlibrarian.net/442819146/1.1.1.png
  
- After some investigation from nginx team, they build nginx with static
- linking openssl with this patch, and this solved memory overuse issue
- https://git.openssl.org/?p=openssl.git;a=commitdiff;h=f2bb79a
+ [Regression Potential]
  
- Can you please fix and rebuild openssl with this patch?
+ Low. This particular fix is tiny
+ (https://git.openssl.org/?p=openssl.git;a=commitdiff;h=f2bb79a) and has
+ been released and used in a couple of upstream openssl versions already
+ without issue.
  
- Thanks!
+ [Other Info]
+  
+ The fix has been tested by nginx team and it solved the memory overuse issue.

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

Title:
  openssl 1.1.1 memory overuse/leak

Status in openssl package in Ubuntu:
  New

Bug description:
  [Impact]

  At some point in the past do_ssl3_write() used to return the number of
  bytes written, or a value <= 0 on error.

  With libssl1.11 it now just returns a success/
  error code and writes the number of bytes written to |tmpwrit|.

  The SSL_MODE_RELEASE_BUFFERS code was still looking at the return code
  for the number of bytes written rather than |tmpwrit|. This has the effect
  that the buffers are not released when they are supposed to be.

  Thus such software as nginx currenty use significantly more memory
  compared to libssl1.0.

  [Test Case]

  Use 'top' to measure the memory usage by nginx with ssl configured.

  Example:

  No memory overuse:
  ii libssl1.1:amd64 1.1.0g-2ubuntu4 amd64 Secure Sockets Layer toolkit - 
shared libraries
  https://launchpadlibrarian.net/442818951/1.1.0g.png

  2,5x memory overuse:
  ii libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.4 amd64 Secure Sockets Layer 
toolkit - shared libraries
  https://launchpadlibrarian.net/442819146/1.1.1.png

  [Regression Potential]

  Low. This particular fix is tiny
  (https://git.openssl.org/?p=openssl.git;a=commitdiff;h=f2bb79a) and
  has been released and used in a couple of upstream openssl versions
  already without issue.

  [Other Info]
   
  The fix has been tested by nginx team and it solved the memory overuse issue.

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

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

[Touch-packages] [Bug 1844067] Re: Merge ibus 1.5.21-1~exp2 (main) from Debian experimental (main)

[Gunnar Hjalmarsson]

Not uploaded yet, and I have added a security fix to the proposed upload
in the PPA.

As regards the test failures I submitted an upstream issue:

https://github.com/ibus/ibus/issues/2135

** Bug watch added: github.com/ibus/ibus/issues #2135
   https://github.com/ibus/ibus/issues/2135

** Changed in: ibus (Ubuntu)
   Status: Fix Committed => In Progress

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

Title:
  Merge ibus 1.5.21-1~exp2 (main) from Debian experimental (main)

Status in ibus package in Ubuntu:
  In Progress

Bug description:
  Upstream released ibus 1.5.21 on 2019-08-23, and it's available in
  Debian experimental. It would be good if this could make it into eoan,
  so a recent IBus version gets 'tested' in 19.10 as a preparation for
  next LTS.

  Please see  for an overview of
  the changes in 1.5.20 and 1.5.21. They are both micro releases and
  don't introduce new features.

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

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

[Touch-packages] [Bug 1817627] Re: systemd-analyze verify reports failure

[Bryant Finney]

I am also very interested in this fix; it is currently preventing
integration with a CI/CD pipeline for deploying my company's web app to
AWS cloud-based Ubuntu 18.04 servers.

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

Title:
  systemd-analyze verify reports failure

Status in Ubuntu Manpage Repository:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Version 237 and 238 of systemd-analyze have a known issue:
  https://github.com/systemd/systemd/issues/8592

  When will a fix be posted?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-manpage-repository/+bug/1817627/+subscriptions

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

[Touch-packages] [Bug 1815172] Re: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa

[Alkis Georgopoulos]

Hi Timo,

if I remember correctly, there were some schools that were affected by this 
issue, but I wasn't able to reproduce it in the office due to lack of similar 
hardware.
Unfortunately it's not easy to check which were those schools; but I can keep 
an eye on this issue, in case I hear about black screens in the near future

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

Title:
  [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Won't Fix
Status in mesa source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Several schools reported black screens after normally updating their Ubuntu 
boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

  This is caused by mesa assuming that soft-pinning on GEN8+ is working
  since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So
  a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT
  sizes/pin flags, but that's left for future.

  [Test case]
  install fixed mesa or kernel, check that the regression is fixed

  [Regression potential]
  mesa: shouldn't be any, it just reverts the change to always soft-pin
  (TODO kernel: adds commits from upstream stable, which have been well tested 
upstream by now)

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

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

[Touch-packages] [Bug 1843982] Re: gnome-shell crashed with SIGSEGV in g_str_hash()

[Gunnar Hjalmarsson]

** Information type changed from Private to Public

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

Title:
  gnome-shell crashed with SIGSEGV in g_str_hash()

Status in accountsservice package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Touch-packages] [Bug 1785629] Re: [MIR] gupnp-av

[Sebastien Bacher]

** Changed in: gupnp-av (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [MIR] gupnp-av

Status in gupnp-av package in Ubuntu:
  Fix Released

Bug description:
  * Availability

  Builds on all supported architectures in Ubuntu and on sync from
  Debian

  * Rationale

  We would like to enable dlna sharing of media files, which is a GNOME
  upstream feature and relying on rygel which depends on the gupnp
  libraries, including the gupnp-dlna one

  * Security

  No CVE/known security issue

  * Quality assurance

  - the desktop-packages team is subscribed to the package
  - the bug lists in upstream, the Debian PTS and launchpad are empty
  - upstream has a testsuit which is not being used during build, we are going 
to look at changing that

  * Dependendies

  The package uses standard desktop libraries that are already in main
  (gstreamer, glib)

  * Standards compliance

  the package is using standard packaging (dh10), the standards-version
  is 3.9.8, the package is in sync from Debian

  * Maintainance

  Upstream is active and the desktop team is going to look after the
  package in ubuntu

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

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

[Touch-packages] [Bug 1844158] [NEW] FTBFS using vala-0.46.1

[Rex Dieter]

Public bug reported:

Trying to build on/for fedora 31+ fails with the following errors:

make[2]: Entering directory '/builddir/build/BUILD/libunity-7.1.4/src'
/usr/bin/valac -C -H unity.h -d . --gir=Unity-7.0.gir --library unity 
--internal-vapi=unity-internal.vapi --internal-header=unity-internal.h 
--target-glib=2.32 --thread --use-header --vapidir ../vapi --vapidir 
../protocol --vapidir . --pkg unity-protocol --pkg config --pkg unity-trace 
--pkg glib-2.0 --pkg gmodule-2.0 --pkg gobject-2.0 --pkg gio-2.0 --pkg 
gio-unix-2.0 --pkg dee-1.0 --pkg Dbusmenu-0.4  unity-appinfo-manager.vala 
unity-icon.vala unity-inspector.vala unity-io.vala unity-launcher.vala 
unity-category.vala unity-filters.vala unity-preferences-manager.vala 
unity-merge-strategy.vala unity-models.vala unity-search.vala 
unity-synchronizer.vala unity-previews.vala unity-result-activation.vala 
unity-scope-interface.vala unity-scope-dbus-connector.vala 
unity-scope-dbus-impl.vala unity-scope-channel.vala unity-deprecated-scope.vala 
unity-deprecated-scope-impl.vala unity-aggregator-scope.vala 
unity-aggregator-scope-private.vala unity-master-scope.vala 
unity-simple-scope.vala unity-scope-loader.vala unity-scope-tracker.vala 
unity-sound-menu.vala unity-sound-menu-mpris.vala unity-utils.vala
Command-line option `--thread` is deprecated and will be ignored
Compilation failed: 2 error(s), 0 warning(s)
BUILDSTDERR: unity-deprecated-scope.vala:64.3-64.28: error: Creation method of 
abstract class cannot be public.
BUILDSTDERR:   public DeprecatedScopeBase (string dbus_path_, string id_)
BUILDSTDERR:   ^^
BUILDSTDERR: unity-aggregator-scope.vala:54.3-54.24: error: Creation method of 
abstract class cannot be public.
BUILDSTDERR:   public AggregatorScope (string dbus_path_, string id_, MergeMode 
merge_mode = AggregatorScope.MergeMode.OWNER_SCOPE, bool proxy_filter_hints = 
false)
BUILDSTDERR:   ^^
BUILDSTDERR: make[2]: *** [Makefile:1389: libunity_la_vala.stamp] Error 1

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

** Affects: libunity (Fedora)
 Importance: Unknown
 Status: Unknown

** Bug watch added: Red Hat Bugzilla #1736053
   https://bugzilla.redhat.com/show_bug.cgi?id=1736053

** Also affects: libunity via
   https://bugzilla.redhat.com/show_bug.cgi?id=1736053
   Importance: Unknown
   Status: Unknown

** Also affects: libunity (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1736053
   Importance: Unknown
   Status: Unknown

** No longer affects: libunity

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

Title:
  FTBFS using vala-0.46.1

Status in libunity package in Ubuntu:
  New
Status in libunity package in Fedora:
  Unknown

Bug description:
  Trying to build on/for fedora 31+ fails with the following errors:

  make[2]: Entering directory '/builddir/build/BUILD/libunity-7.1.4/src'
  /usr/bin/valac -C -H unity.h -d . --gir=Unity-7.0.gir --library unity 
--internal-vapi=unity-internal.vapi --internal-header=unity-internal.h 
--target-glib=2.32 --thread --use-header --vapidir ../vapi --vapidir 
../protocol --vapidir . --pkg unity-protocol --pkg config --pkg unity-trace 
--pkg glib-2.0 --pkg gmodule-2.0 --pkg gobject-2.0 --pkg gio-2.0 --pkg 
gio-unix-2.0 --pkg dee-1.0 --pkg Dbusmenu-0.4  unity-appinfo-manager.vala 
unity-icon.vala unity-inspector.vala unity-io.vala unity-launcher.vala 
unity-category.vala unity-filters.vala unity-preferences-manager.vala 
unity-merge-strategy.vala unity-models.vala unity-search.vala 
unity-synchronizer.vala unity-previews.vala unity-result-activation.vala 
unity-scope-interface.vala unity-scope-dbus-connector.vala 
unity-scope-dbus-impl.vala unity-scope-channel.vala unity-deprecated-scope.vala 
unity-deprecated-scope-impl.vala unity-aggregator-scope.vala 
unity-aggregator-scope-private.vala unity-master-scope.vala 
unity-simple-scope.vala unity-scope-loader.vala unity-scope-tracker.vala 
unity-sound-menu.vala unity-sound-menu-mpris.vala unity-utils.vala
  Command-line option `--thread` is deprecated and will be ignored
  Compilation failed: 2 error(s), 0 warning(s)
  BUILDSTDERR: unity-deprecated-scope.vala:64.3-64.28: error: Creation method 
of abstract class cannot be public.
  BUILDSTDERR:   public DeprecatedScopeBase (string dbus_path_, string id_)
  BUILDSTDERR:   ^^
  BUILDSTDERR: unity-aggregator-scope.vala:54.3-54.24: error: Creation method 
of abstract class cannot be public.
  BUILDSTDERR:   public AggregatorScope (string dbus_path_, string id_, 
MergeMode merge_mode = AggregatorScope.MergeMode.OWNER_SCOPE, bool 
proxy_filter_hints = false)
  BUILDSTDERR:   ^^
  BUILDSTDERR: make[2]: *** [Makefile:1389: libunity_la_vala.stamp] Error 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ub

[Touch-packages] [Bug 1843468] Re: nftables based iptables wrapper break userspace

[Launchpad Bug Tracker]

This bug was fixed in the package iptables - 1.8.3-2ubuntu4

---
iptables (1.8.3-2ubuntu4) eoan; urgency=medium

  * autopkgtest: allow-stderr on command9 to fix regression

 -- Julian Andres Klode   Mon, 16 Sep 2019 13:48:52
+0200

** Changed in: iptables (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  nftables based iptables wrapper break userspace

Status in iptables package in Ubuntu:
  Fix Released

Bug description:
  iptables just got replaced by the nftables wrappers, effectively
  changing all Ubuntu systems to using nftables rather than regular
  iptables/ip6tables/ebtables.

  Unfortunately those wrappers aren't perfect and don't convert every
  option properly, nor know about some of the available plugins for
  those commands.

  This means that unless the software using those commands are aware
  that those are wrappers and adapt their use, they may break at some
  random point in time.

  
  While nftables is clearly the way forward, just silently switching the 
existing native tools with the compat wrappers will lead to widespread breakage 
both from packages in the archive, snaps and a variety of scripts our users may 
be running.

  So far, looking around, known breakages post-nft are expected with at
  least Docker, Kubernetes and LXD but the same may be true with the
  many other packages we have that call iptables, ip6tables, ebtables or
  arptables today.

  A migration should include a proper audit of all in-archive users, see
  if they have a plan/patch for native nft interaction and if not,
  validate their use of the tools is compatible with the wrappers.

  We should also extend that to popular snaps / those we ship by
  default. Snaps make things worse as they use the tools from their base
  snap, which in LXD's case is currently 16.04 (soon to switch to
  18.04).

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

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

[Touch-packages] [Bug 1841654] Re: Consider replacing mawk with gawk in main

[Launchpad Bug Tracker]

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

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

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

Title:
  Consider replacing mawk with gawk in main

Status in mawk package in Ubuntu:
  Confirmed

Bug description:
  For POSIX compatibility reasons Ubuntu ships with mawk ("Mike's awk" =
  mawk) in main. There is an awk-symlink to mawk, thus mawk is the
  official awk implementation in Ubuntu.

  == Reasons against keeping mawk ==

  *The mawk package is synced from debian and it is heavily
  undermaintained: Debian (and thus Ubuntu) still ships version
  1.3.3-17, the same version at least since oldoldstable:
  https://packages.debian.org/search?searchon=names&keywords=mawk

  *maintainer Thomas E. Dickey (https://invisible-island.net/mawk/)
  called officially out that Debian "neglected" mawk in 2014 ("As noted,
  mawk has been neglected by some packagers (see for example this
  http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=mawk)". And
  Debian (and Ubuntu) still ship the same version five years later

  *Most other distributions ship mawk at least in its last official
  incarnation 1.3.4 in their repositories. Dickey lists AIX, Fedora,
  FinkPorts (Mac OS X), FreeBSD port, Gentoo, HPUX, MacPorts (Mac OS X),
  NetBSD pkgsrc/lang, OpenCSW (Solaris). That version is from 2014 but
  updated snapshots are released in regular intervals. The current
  snapshot is from February 2019: https://github.com/ThomasDickey/mawk-
  snapshots/blob/ab13a164013940e90c0b1ad36a039feae06a0b65/CHANGES

  *A planned rewrite mawk2 was planned by original author Mike Brennan
  in 2016 but obviously came to nothing:
  https://github.com/ploxiln/mawk-2/commits/master

  *Thus mawk sits in Ubuntu main in a version published upstream in 2009
  and celebrates its 10th anniversary of negligence. In a state that
  Debian was called out for 5 years ago.

  *This year it is 10 years unmaintained and largely untouched. At the
  end of the next LTS-support-cycle we can celebrate 15 years of not
  supporting it.

  *awk is included in Linux for POSIX standard compliance. Mawk is known
  to be fast and small but it is the implementation that is farthest
  from being POSIX compliant, missing things like named character
  classes like [[:space:]] within its EREs.

  == Reasons for gawk as a replacement ==

  *It is the official GNU awk implementation and known to work well with
  the rest of the GNU userland.

  *It is actively maintained with the last version 5.01 shipping in
  June, 2019 (even if Ubuntu will obviously still ship 4.2 for Eoan).

  *It is mostly compliant with the POSIX standard.

  *Most other distributions ship it as the standard POSIX
  implementation, with a awk symlink. So it had security reviews already
  by Red Hat and others.

  == Possible problems with switching to gawk in time for Ubuntu 20.4 ==

  - It might need to be MIRed by the Ubuntu security team and a review
  might take some time. So I filed this bug early with Eoan not yet out
  of the door.

  - It is much larger than mawk, the Ubuntu package is 1600 kB in size,
  while mawk is only about 190KB. Thus some might want to split out some
  basic functionality to save size. Like what is vim-tiny to vim. To
  start gawk in --traditional or --posix mode and disable the extensions
  at compile time might be a good start to reduce the size. See:
  https://www.gnu.org/software/gawk/manual/html_node/Additional-
  Configuration-Options.html#Additional-Configuration-Options

  =

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: mawk 1.3.3-17ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 27 20:12:11 2019
  Dependencies:
   gcc-9-base 9.1.0-2ubuntu2~19.04
   libc6 2.29-0ubuntu2
   libgcc1 1:9.1.0-2ubuntu2~19.04
   libidn2-0 2.0.5-1
   libunistring2 0.9.10-1ubuntu2
  InstallationDate: Installed on 2018-02-23 (550 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcEnviron:
   LANGUAGE=de_AT:de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  SourcePackage: mawk
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1841654] Re: Consider replacing mawk with gawk in main

[Dave Chiluk]

We (Indeed) were recently hit by mawk posix non-compliance as well.  For
all the reasons stated above, I would also like to see mawk replaced
with gawk in main.  I'd also like to see the mawk dependencies in the
ubuntu-meta packages replaced with gawk.  For that reason I'm opening a
separate target for this bug in ubuntu-meta.

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

** Tags added: indeed

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

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

Title:
  Consider replacing mawk with gawk in main

Status in mawk package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  For POSIX compatibility reasons Ubuntu ships with mawk ("Mike's awk" =
  mawk) in main. There is an awk-symlink to mawk, thus mawk is the
  official awk implementation in Ubuntu.

  == Reasons against keeping mawk ==

  *The mawk package is synced from debian and it is heavily
  undermaintained: Debian (and thus Ubuntu) still ships version
  1.3.3-17, the same version at least since oldoldstable:
  https://packages.debian.org/search?searchon=names&keywords=mawk

  *maintainer Thomas E. Dickey (https://invisible-island.net/mawk/)
  called officially out that Debian "neglected" mawk in 2014 ("As noted,
  mawk has been neglected by some packagers (see for example this
  http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=mawk)". And
  Debian (and Ubuntu) still ship the same version five years later

  *Most other distributions ship mawk at least in its last official
  incarnation 1.3.4 in their repositories. Dickey lists AIX, Fedora,
  FinkPorts (Mac OS X), FreeBSD port, Gentoo, HPUX, MacPorts (Mac OS X),
  NetBSD pkgsrc/lang, OpenCSW (Solaris). That version is from 2014 but
  updated snapshots are released in regular intervals. The current
  snapshot is from February 2019: https://github.com/ThomasDickey/mawk-
  snapshots/blob/ab13a164013940e90c0b1ad36a039feae06a0b65/CHANGES

  *A planned rewrite mawk2 was planned by original author Mike Brennan
  in 2016 but obviously came to nothing:
  https://github.com/ploxiln/mawk-2/commits/master

  *Thus mawk sits in Ubuntu main in a version published upstream in 2009
  and celebrates its 10th anniversary of negligence. In a state that
  Debian was called out for 5 years ago.

  *This year it is 10 years unmaintained and largely untouched. At the
  end of the next LTS-support-cycle we can celebrate 15 years of not
  supporting it.

  *awk is included in Linux for POSIX standard compliance. Mawk is known
  to be fast and small but it is the implementation that is farthest
  from being POSIX compliant, missing things like named character
  classes like [[:space:]] within its EREs.

  == Reasons for gawk as a replacement ==

  *It is the official GNU awk implementation and known to work well with
  the rest of the GNU userland.

  *It is actively maintained with the last version 5.01 shipping in
  June, 2019 (even if Ubuntu will obviously still ship 4.2 for Eoan).

  *It is mostly compliant with the POSIX standard.

  *Most other distributions ship it as the standard POSIX
  implementation, with a awk symlink. So it had security reviews already
  by Red Hat and others.

  == Possible problems with switching to gawk in time for Ubuntu 20.4 ==

  - It might need to be MIRed by the Ubuntu security team and a review
  might take some time. So I filed this bug early with Eoan not yet out
  of the door.

  - It is much larger than mawk, the Ubuntu package is 1600 kB in size,
  while mawk is only about 190KB. Thus some might want to split out some
  basic functionality to save size. Like what is vim-tiny to vim. To
  start gawk in --traditional or --posix mode and disable the extensions
  at compile time might be a good start to reduce the size. See:
  https://www.gnu.org/software/gawk/manual/html_node/Additional-
  Configuration-Options.html#Additional-Configuration-Options

  =

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: mawk 1.3.3-17ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 27 20:12:11 2019
  Dependencies:
   gcc-9-base 9.1.0-2ubuntu2~19.04
   libc6 2.29-0ubuntu2
   libgcc1 1:9.1.0-2ubuntu2~19.04
   libidn2-0 2.0.5-1
   libunistring2 0.9.10-1ubuntu2
  InstallationDate: Installed on 2018-02-23 (550 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcEnviron:
   LANGUAGE=de_AT:de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  SourcePackage: mawk
  UpgradeStatus: No upgrade log present (probably fresh 

[Touch-packages] [Bug 1713136] Re: package passwd 1:4.2-3.1ubuntu5.3 failed to install/upgrade: package passwd is not ready for configuration cannot configure (current status 'half-installed')

[Launchpad Bug Tracker]

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

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

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

Title:
  package passwd 1:4.2-3.1ubuntu5.3 failed to install/upgrade: package
  passwd is not ready for configuration  cannot configure (current
  status 'half-installed')

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  This error occurs while upgrading

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: passwd 1:4.2-3.1ubuntu5.3
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sat Aug 26 06:10:53 2017
  DpkgTerminalLog:
   dpkg: error processing package passwd (--configure):
package passwd is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package passwd is not ready for configuration  cannot configure 
(current status 'half-installed')
  InstallationDate: Installed on 2017-08-02 (23 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: shadow
  Title: package passwd 1:4.2-3.1ubuntu5.3 failed to install/upgrade: package 
passwd is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1843755] Re: [FFe] Please accept systemd 242 to Eoan

[Steve Langasek]

as commented in person, I'm approving the v242 FFe, but if the target is
v243 it is better to not upload 242 to the archive and wait for 243
instead.

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  [FFe] Please accept systemd 242 to Eoan

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Eoan currently has 241-7ubuntu1, Debian stable has 241 and Debian testing 
moved to 242 last week.
  While version 241 is the safer choice for Eoan (from v241 and v242) since it 
is widely tested updating to v242 will allow us to carry fewer patches in Eoan 
and makes moving to the next release easier.

  The proposed package is tested in Bileto and all tests are passing (except 
for a few unrelated failures):
  https://bileto.ubuntu.com/#/ticket/3797

  The final version will be 242-6ubuntu1 and I'm tidying up the
  changelog, too.

  I plan merging 242-7, too, going forward but this will not need an
  FFe.

  CHANGES WITH 242:

  * In .link files, MACAddressPolicy=persistent (the default) is changed
    to cover more devices. For devices like bridges, tun, tap, bond, and
    similar interfaces that do not have other identifying information,
    the interface name is used as the basis for persistent seed for MAC
    and IPv4LL addresses. The way that devices that were handled
    previously is not changed, and this change is about covering more
    devices then previously by the "persistent" policy.

    MACAddressPolicy=random may be used to force randomized MACs and
    IPv4LL addresses for a device if desired.

    Hint: the log output from udev (at debug level) was enhanced to
    clarify what policy is followed and which attributes are used.
    `SYSTEMD_LOG_LEVEL=debug udevadm test-builtin net_setup_link 
/sys/class/net/`
    may be used to view this.

    Hint: if a bridge interface is created without any slaves, and gains
    a slave later, then now the bridge does not inherit slave's MAC.
    To inherit slave's MAC, for example, create the following file:
    ```
    # /etc/systemd/network/98-bridge-inherit-mac.link
    [Match]
    Type=bridge

    [Link]
    MACAddressPolicy=none
    ```

  * The .device units generated by systemd-fstab-generator and other
    generators do not automatically pull in the corresponding .mount 
unit
    as a Wants= dependency. This means that simply plugging in the 
device
    will not cause the mount unit to be started automatically. But 
please
    note that the mount unit may be started for other reasons, in
    particular if it is part of local-fs.target, and any unit which
    (transitively) depends on local-fs.target is started.

  * networkctl list/status/lldp now accept globbing wildcards for 
network
    interface names to match against all existing interfaces.

  * The $PIDFILE environment variable is set to point the absolute path
    configured with PIDFile= for processes of that service.

  * The fallback DNS server list was augmented with Cloudflare public 
DNS
    servers. Use `-Ddns-servers=` to set a different fallback.

  * A new special target usb-gadget.target will be started automatically
    when a USB Device Controller is detected (which means that the 
system
    is a USB peripheral).

  * A new unit setting CPUQuotaPeriodSec= assigns the time period
    relatively to which the CPU time quota specified by CPUQuota= is
    measured.

  * A new unit setting ProtectHostname= may be used to prevent services
    from modifying hostname information (even if they otherwise would
    have privileges to do so).

  * A new unit setting NetworkNamespacePath= may be used to specify a
    namespace for service or socket units through a path referring to a
    Linux network namespace pseudo-file.

  * The PrivateNetwork= setting and JoinsNamespaceOf= dependencies now
    have an effect on .socket units: when used the listening socket is
    created within the configured network namespace instead of the host
    namespace.

  * ExecStart= command lines in unit files may now be prefixed with ':'
    in which case environment variable substitution is
    disabled. (Supported for the other ExecXYZ= settings, too.)

  * .timer units gained two new boolean settings OnClockChange= and
    OnTimezoneChange= which may be used to also trigger a unit when the
    system clock is changed or the local

[Touch-packages] [Bug 1547589] Re: rtkit-daemon flooding syslog

[Kai Kasurinen]

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

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

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

Title:
  rtkit-daemon flooding syslog

Status in rtkit package in Ubuntu:
  Confirmed
Status in rtkit package in Debian:
  Unknown

Bug description:
  rtkit is flooding syslog with the following:

  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.

  This may be related to but #1547585

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: rtkit 0.11-4
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:42:58 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: rtkit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Xenial that was purported
to fix this bug report has been removed because one or more bugs that
were to be fixed by the upload have failed verification and been in this
state for more than 10 days.

** Changed in: kbd (Ubuntu Xenial)
   Status: Fix Committed => Won't Fix

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

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to be safe, too.

  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The

[Touch-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Xenial that was purported
to fix this bug report has been removed because one or more bugs that
were to be fixed by the upload have failed verification and been in this
state for more than 10 days.

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

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to be safe, too.

  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in

[Touch-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Xenial that was purported
to fix this bug report has been removed because one or more bugs that
were to be fixed by the upload have failed verification and been in this
state for more than 10 days.

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

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to be safe, too.

  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in

[Touch-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Xenial that was purported
to fix this bug report has been removed because one or more bugs that
were to be fixed by the upload have failed verification and been in this
state for more than 10 days.

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

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to be safe, too.

  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in

[Touch-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Xenial that was purported
to fix this bug report has been removed because one or more bugs that
were to be fixed by the upload have failed verification and been in this
state for more than 10 days.

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

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to be safe, too.

  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in

[Touch-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Bionic that was purported
to fix this bug report has been removed because one or more bugs that
were to be fixed by the upload have failed verification and been in this
state for more than 10 days.

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

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to be safe, too.

  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in

[Touch-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Xenial that was purported
to fix this bug report has been removed because one or more bugs that
were to be fixed by the upload have failed verification and been in this
state for more than 10 days.

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

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to be safe, too.

  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in

[Touch-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Bionic that was purported
to fix this bug report has been removed because one or more bugs that
were to be fixed by the upload have failed verification and been in this
state for more than 10 days.

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

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to be safe, too.

  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in

[Touch-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Bionic that was purported
to fix this bug report has been removed because one or more bugs that
were to be fixed by the upload have failed verification and been in this
state for more than 10 days.

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

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to be safe, too.

  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in

[Touch-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Bionic that was purported
to fix this bug report has been removed because one or more bugs that
were to be fixed by the upload have failed verification and been in this
state for more than 10 days.

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

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to be safe, too.

  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in

[Touch-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Disco that was purported to
fix this bug report has been removed because one or more bugs that were
to be fixed by the upload have failed verification and been in this
state for more than 10 days.

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

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to be safe, too.

  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in 

[Touch-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Disco that was purported to
fix this bug report has been removed because one or more bugs that were
to be fixed by the upload have failed verification and been in this
state for more than 10 days.

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

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to be safe, too.

  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in 

[Touch-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Disco that was purported to
fix this bug report has been removed because one or more bugs that were
to be fixed by the upload have failed verification and been in this
state for more than 10 days.

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

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to be safe, too.

  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in 

[Touch-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Disco that was purported to
fix this bug report has been removed because one or more bugs that were
to be fixed by the upload have failed verification and been in this
state for more than 10 days.

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

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to be safe, too.

  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in 

[Touch-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Disco that was purported to
fix this bug report has been removed because one or more bugs that were
to be fixed by the upload have failed verification and been in this
state for more than 10 days.

** Changed in: kbd (Ubuntu Disco)
   Status: Fix Committed => Won't Fix

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

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to be safe, too.

  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The k

[Touch-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Bionic that was purported
to fix this bug report has been removed because one or more bugs that
were to be fixed by the upload have failed verification and been in this
state for more than 10 days.

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

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to be safe, too.

  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in

[Touch-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Disco that was purported to
fix this bug report has been removed because one or more bugs that were
to be fixed by the upload have failed verification and been in this
state for more than 10 days.

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

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to be safe, too.

  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in 

[Touch-packages] [Bug 520546] Autopkgtest regression report (kbd/2.0.4-4ubuntu1.19.04.0)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted kbd (2.0.4-4ubuntu1.19.04.0) for disco 
have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/240-6ubuntu5 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/disco/update_excuses.html#kbd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to be safe, too.

  (console-setup)
  [Impact]

   * keyboard-configuration's pos

[Touch-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Bionic that was purported
to fix this bug report has been removed because one or more bugs that
were to be fixed by the upload have failed verification and been in this
state for more than 10 days.

** Changed in: kbd (Ubuntu Bionic)
   Status: Fix Committed => Won't Fix

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

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to be safe, too.

  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The

[Touch-packages] [Bug 1789147] Re: ip conflict

[quankang]

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  ip conflict

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Connect an existing ip address, you can connect, it will cause two machines 
with the same ip address can not access the Internet.
  I have the patch.

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

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

[Touch-packages] [Bug 1843394] Re: FTBFS in Eoan - Error: operand type mismatch for `push' - gcc 9.2.1 / binutils 2.32.51.20190905-0ubuntu1

[Christian Ehrhardt ]

Note: given that this went into the archive in early July and that nothing but 
this section in IPXE broke I lean toward assuming that the ipxe code is broken 
or at least (while it worked in the past) not implemented the way it should be 
for the assembly to work.
Yet I'm not feeling experienced enough to really feel confident about my 
suggested fix without further upstream feedback or other people backing me up.

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

Title:
  FTBFS in Eoan - Error: operand type mismatch for `push' - gcc 9.2.1 /
  binutils 2.32.51.20190905-0ubuntu1

Status in binutils package in Ubuntu:
  New
Status in ipxe package in Ubuntu:
  New

Bug description:
  This might be due to new gcc-9 being more strict, but the build that
  worked before now fails with:

  arch/x86_64/core/gdbidt.S: Assembler messages:
  arch/x86_64/core/gdbidt.S:109: Error: operand type mismatch for `push'
  arch/x86_64/core/gdbidt.S:110: Error: operand type mismatch for `push'
  arch/x86_64/core/gdbidt.S:161: Error: operand type mismatch for `pop'
  arch/x86_64/core/gdbidt.S:162: Error: operand type mismatch for `pop'
  make[2]: *** [Makefile.housekeeping:937: bin-x86_64-efi/gdbidt.o] Error 1

  Full log at: https://launchpadlibrarian.net/441262285/buildlog_ubuntu-
  eoan-amd64.ipxe_1.0.0+git-20190109.133f4c4-0ubuntu2_BUILDING.txt.gz

  Now all of this is about push/pop of %fs and %gs.
  That needs to match the size of the registers which depend on the current 
running mode.

  In this particular case in ./src/arch/x86_64/core/gdbidt.S
  The failing file is in ".code64" mode.
  In that I'd expect %gs/%fs to be 64 bit.

  
  Usually we see push/pop "w" in .code16 (word), l in .code32 (long) but in 
that sense here q (quad word) seems right at first (should be what correctly 
matches the .code64).
  That matches what I see throughout the ipxe code but also throughout the 
archive 
https://codesearch.debian.net/search?q=pop%5Ba-z%5D.*%25fs&literal=0&page=2

  Maybe I misread the mode it is in, or it is actually a false positives.
  Or the sizes of FS/GS do not change - haven't touched them in a lng time.
  Was it that segment registers didn't change size?
  I'll need to do a few checks to first see what the compiler would expect 
there and from there need to understand this.

  The command used also points to AS being in 64 bit mode when this happens:
  gcc -E  -DARCH=x86_64 -DPLATFORM=efi -DSECUREBOOT=0 -fstrength-reduce 
-fomit-frame-pointer -falign-jumps=1 -falign-loops=1 -falign-functions=1 -m64 
-mno-mmx -mno-sse -fshort-wchar -Ui386 -Ulinux -DNVALGRIND -fpie -mno-red-zone 
-Iinclude -I. -Iarch/x86/include -Iarch/x86_64/include 
-Iarch/x86_64/include/efi -Os -g -ffreestanding -Wall -W -Wformat-nonliteral  
-fno-stack-protector -fno-dwarf2-cfi-asm -fno-exceptions  -fno-unwind-tables 
-fno-asynchronous-unwind-tables -Wno-address -Wno-stringop-truncation   
-ffunction-sections -fdata-sections -include include/compiler.h -DASM_TCHAR='@' 
-DASM_TCHAR_OPS='@' -DASSEMBLY  -DOBJECT=gdbidt arch/x86_64/core/gdbidt.S | as  
--64-o bin-x86_64-efi/gdbidt.o

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

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

[Touch-packages] [Bug 1547589] Re: rtkit-daemon flooding syslog

[Bug Watch Updater]

** Changed in: rtkit (Debian)
   Status: Unknown => Confirmed

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

Title:
  rtkit-daemon flooding syslog

Status in rtkit package in Ubuntu:
  Confirmed
Status in rtkit package in Debian:
  Confirmed

Bug description:
  rtkit is flooding syslog with the following:

  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.

  This may be related to but #1547585

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: rtkit 0.11-4
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:42:58 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: rtkit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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