[Touch-packages] [Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :

[beta-tester]

"toram" works to me and will also fix the hanging at shutdown/reboot.
but "toram" takes more that twice as long to boot into the desktop (~3minutes 
instead of ~1minute).

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

Title:
  netbooting the bionic live CD over NFS goes straight to maintenance
  mode :

Status in casper package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  netbooting the bionic live CD[1] over NFS goes straight to maintenance
  mode :

  [1] http://cdimage.ubuntu.com/daily-live/current/

  # casper.log
  Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 
pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' 
(uid=999 pid=569 comm="" label="unconfined")
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Daemon'
  dbus-daemon[568]: [session uid=999 pid=568] Activating service 
name='org.gtk.vfs.Metadata' requested by ':1.0' (uid=999 pid=569 comm="" 
label="unconfined")
  fuse: device not found, try 'modprobe fuse' first
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Metadata'

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270:
  g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)'
  failed

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: 
g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
  A connection to the bus can't be made
  done.
  Begin: Setting up init... ... done.

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

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

[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.

[Daniel Mehrmann]

@Steve I'm using another LVM setup, which i created manual while using Ubunuts 
live system ;-)
I wrote this in my first comment already. But basicly i was the same problem 
with the "30 seconds" problem and my system falls back twice to scanning 
devices :-(.

But to be honest, yes, i  don't in this case and you can ignore me.

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

Title:
  Long time booting : Failed to connect to lvmetad. Falling back to
  device scanning.

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Fix Committed

Bug description:
  [SRU Justification]
  A regression in initramfs-tools causes it to autogenerate config in the 
initramfs saying to resume from any available swap devices, but references the 
swap device by UUID, which is not a canonical form for referring to LVM volumes 
(because of snapshotting, they are not unique).  Ubiquity also generates a file 
in /etc at install time which references the swap partition in the same way.  
Since the lvm2 initramfs hooks also only activate precisely those LVs that are 
detected as needed at boot, this adds an inappropriate 30-second boot delay to 
any system with swap on LVM, which includes any desktop system that was 
configured with LVM (but not full-disk encryption) at install time.

  [Test case]
  1. Install using the "Use LVM" option in the desktop installer.
  4. Reboot.
  5. Verify that dmesg shows a 30-second delay before mounting the root 
filesystem.
  6. Install initramfs-tools from bionic-proposed.
  7. Reboot.
  8. Verify that dmesg no longer shows a 30-second delay before mounting the 
root filesystem.
  9. Install using the bionic daily image that contains the ubiquity from 
bionic-proposed.
  10. Reboot.
  11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that 
there is no delay before mounting the root filesystem.

  [Regression potential]
  This makes changes to shell scripts, and shell is a perilous language. An 
unnoticed bug could cause all initramfs generation, and thus all kernel 
installation, to fail for some users. A regression could also cause a user to 
lose hiberation support that they currently have.

  [Original description]
  After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu 
installation", the
  system is very slow to reboot.

  It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to 
device scanning.",
  then waits 32 seconds, then continues as it should.

  I think this is a ubiquity bug, since the d-i based installer is not affected.
   - ubuntu-18.04-desktop-amd64.iso 
(a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected
   - xubuntu-18.04-desktop-amd64.iso 
(7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected
   - ubuntu-18.04-server-amd64.iso 
(a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not 
affected

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

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

[Touch-packages] [Bug 1778140] Re: resize2fs hoses a filesystem on lvm after resizing

[Theodore Ts'o]

OK so it looks like you were trying to shrink a file system from 59G to
30G (using an off-line resize, since on-line resizing only supports
growing a file system).

Hmm are you willing to send me (probably off-line) a metadata-only
dump of the "before" file system?   See the e2image page, and read the
section "QCOW2 IMAGE FILES".   I can use the metadata-only file system
to reproduce the problem on my end, by running resize2fs on the raw
metadat-only file system.

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

Title:
  resize2fs hoses a filesystem on lvm after resizing

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  Resized an ext4 filesystem on LVM. Before resizing, I confirmed
  filesystem was clean with e2fsck. After resizing, three errors were
  found.

  root@ubuntu:~# e2fsck -f /dev/ubuntu-vg/root
  e2fsck 1.44.1 (24-Mar-2018)
  Pass 1: Checking inodes, blocks, and sizes
  Inode 21110 extent block passes checks, but checksum does not match extent
(logical block 18432, physical block 503808, len 3813)
  Fix? no
  Inode 26807 extent block passes checks, but checksum does not match extent
(logical block 34816, physical block 768000, len 896)
  Fix? no
  Inode 28306 extent block passes checks, but checksum does not match extent
(logical block 30720, physical block 430080, len 5130)
  Fix? no
  Pass 2: Checking directory structure
  Pass 3: Checking directory connectivity
  Pass 4: Checking reference counts
  Pass 5: Checking group summary information

  
  This setup is currently in a virtual machine with a snapshot, so I can revert 
back and retest. The resize2fs is coming from the 18.04 Ubuntu CD.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: e2fsprogs 1.44.1-1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 21 21:03:56 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: e2fsprogs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1574746] Re: Enable support for libsoxr

[Daniel van Vugt]

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

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

Title:
  Enable support for libsoxr

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  I'd like to ask to enable support for libsoxr-based resamplers in the 
official Ubuntu packages for pulseaudio. The upstream already supports libsoxr 
and automatically detects its availability, so the only change really needed is 
to add the build dependency to debian/control.
   
  The resamplers based in libsoxr offer better quality and better performace 
while introducing more delay compared to the speex resamplers that are used by 
default. The resamplers are documented in the man pages of pulseaudio in Ubuntu 
16.04 but unfortunately are not enabled at build time ('pulseaudio 
--dump-resample-methods' doesn't list them). I've built local packages with 
libsoxr and verified that the resampler works as expected.

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

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

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

[Daniel van Vugt]

The error report (comment #10) confirms this crash only occurs in Ubuntu
18.04. However it's also not that common (only 137 reports globally).
It's pretty unlucky if this is blocking you :(

** Summary changed:

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

** Tags added: regression-release

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

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

Status in systemd package in Ubuntu:
  Confirmed

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

  ---

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

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 235-3ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Fri Jan 26 13:45:06 2018
  ExecutablePath: /lib/systemd/systemd-logind
  InstallationDate: Installed on 2018-01-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180126)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. Z370 HD3
  ProcCmdline: /lib/systemd/systemd-logind
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __libc_connect (fd=39, addr=addr@entry=..., len=len@entry=16) at 
../sysdeps/unix/sysv/linux/connect.c:26
   __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, 
prog=prog@entry=10, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27301efc, 
sendsz=sendsz@entry=400, recvsz=recvsz@entry=400) at clnt_tcp.c:153
   __GI___libc_rpc_getport (tottimeout_sec=60, timeout_sec=5, protocol=6, 
version=2, program=17, address=0x7ffc27302060) at pm_getport.c:106
   __GI_pmap_getport (address=address@entry=0x7ffc27302060, 
program=program@entry=17, version=version@entry=2, 
protocol=protocol@entry=6) at pm_getport.c:154
   __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, 
prog=prog@entry=17, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27302050, 
sendsz=sendsz@entry=0, recvsz=recvsz@entry=0) at clnt_tcp.c:136
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  Title: systemd-logind crashed with SIGABRT in __libc_connect()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: Software adm bin daemon lp mail nuucp root scswebadmin sys 
sysdesign tty uucp
  dmi.bios.date: 09/22/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: Z370 HD3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd09/22/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z370 HD3
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

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

[Daniel van Vugt]

All,

If this bug is affecting you, please help to get it fixed by reporting
it to the systemd developers here:

  https://github.com/systemd/systemd/issues

When done, please tell us the ID of the new issue.

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

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

Status in systemd package in Ubuntu:
  Confirmed

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

  ---

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

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 235-3ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Fri Jan 26 13:45:06 2018
  ExecutablePath: /lib/systemd/systemd-logind
  InstallationDate: Installed on 2018-01-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180126)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. Z370 HD3
  ProcCmdline: /lib/systemd/systemd-logind
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __libc_connect (fd=39, addr=addr@entry=..., len=len@entry=16) at 
../sysdeps/unix/sysv/linux/connect.c:26
   __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, 
prog=prog@entry=10, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27301efc, 
sendsz=sendsz@entry=400, recvsz=recvsz@entry=400) at clnt_tcp.c:153
   __GI___libc_rpc_getport (tottimeout_sec=60, timeout_sec=5, protocol=6, 
version=2, program=17, address=0x7ffc27302060) at pm_getport.c:106
   __GI_pmap_getport (address=address@entry=0x7ffc27302060, 
program=program@entry=17, version=version@entry=2, 
protocol=protocol@entry=6) at pm_getport.c:154
   __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, 
prog=prog@entry=17, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27302050, 
sendsz=sendsz@entry=0, recvsz=recvsz@entry=0) at clnt_tcp.c:136
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  Title: systemd-logind crashed with SIGABRT in __libc_connect()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: Software adm bin daemon lp mail nuucp root scswebadmin sys 
sysdesign tty uucp
  dmi.bios.date: 09/22/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: Z370 HD3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd09/22/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z370 HD3
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1778496] Re: resolution not incresing

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

** Package changed: xorg (Ubuntu) => 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/1778496

Title:
  resolution not incresing

Status in Ubuntu:
  Incomplete

Bug description:
  resolution not incresing

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 25 16:09:50 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: bbswitch, 0.8, 4.15.0-23-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems Xeon E3-1200 v2/3rd Gen Core 
processor Graphics Controller [1019:3149]
  InstallationDate: Installed on 2018-06-08 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Acer Veriton Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=5b575a7c-4097-49ef-865d-6dae0d73237b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2013
  dmi.bios.vendor: Acer
  dmi.bios.version: P21-A1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61H2-M6
  dmi.board.vendor: Acer
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAcer:bvrP21-A1:bd07/18/2013:svnAcer:pnVeritonSeries:pvrP21-A1:rvnAcer:rnH61H2-M6:rvr2.0:cvnAcer:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Veriton Series
  dmi.product.version: P21-A1
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  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/+bug/1778496/+subscriptions

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

[Touch-packages] [Bug 1778506] Re: Have to restart the bluetooth after sleeping to connect to headphones

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1759628, so it 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. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1759628
bluez regression: Bluetooth audio fails to reconnect after resume

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

Title:
  Have to restart the bluetooth after sleeping to connect to headphones

Status in bluez package in Ubuntu:
  New

Bug description:
  Linux Ubuntu 18-04 X1-18 4.15.0-23-generic

  After suspend my bose bluetooth headphones keep connecting /
  disconnecting / connecting ... until failure.

  After 
  marvin@X1-18:~$ sudo service bluetooth restart

  everything works fine again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 25 14:06:50 2018
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20FRS2M600
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=fb013004-2044-405c-946d-4da9f7e757e5 ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/23/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET41W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FRS2M600
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 1st
  dmi.product.name: 20FRS2M600
  dmi.product.version: ThinkPad X1 Yoga 1st
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:A7:A0:36:99:9D  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:358790 acl:11101 sco:0 events:25202 errors:0
TX bytes:14298744 acl:22439 sco:0 commands:2586 errors:0

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

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

[Touch-packages] [Bug 1772844] Re: snapd didn't initialize all the seeded snaps

[Yuan-Chen Cheng]

** Changed in: oem-priority
   Importance: High => Medium

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

Title:
  snapd didn't initialize all the seeded snaps

Status in OEM Priority Project:
  Confirmed
Status in snapd:
  New
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  snapd didn't initialize all the seeded snaps

  bionic-desktop-amd64.iso (20180522)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: snapd 2.32.9+18.04
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 22 22:59:18 2018
  InstallationDate: Installed on 2018-05-23 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180522)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772844/+subscriptions

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

[Touch-packages] [Bug 263369] Re: Save file reverts to last location used. If not available, error is displayed.

[gf]

Hello Komputes. 
Thanks for submitting this bug and reporting a problem with Thunderbird and 
GIMP.

You made this bug report in 2008 and there have been several versions of
both Thunderbird and GIMP since then.

Could you confirm that this is no longer a problem and that we can close
the ticket? Or, if it is still a problem, could you come to Launchpad
and make a comment to that effect?

Thank you again for helping make Ubuntu, Thunderbird and GIMP better.

G

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

Title:
  Save file reverts to last location used. If not available, error is
  displayed.

Status in The Gimp:
  Invalid
Status in gtk+2.0 package in Ubuntu:
  Triaged
Status in thunderbird package in Ubuntu:
  New

Bug description:
  Binary package hint: gimp

  If saving a file, some programs (such as GIMP and Thunderbird) will
  try to revert to the last location used when saving. If that location
  no longer exists (disk off line, path name changed, etc.), it warns
  you that it could not be found.

  Steps to reproduce:
  1) Insert USB key
  2) Create file, then save file
  3) Unmount USB key
  4) Create a new file then save file
  -ERROR- (Screenshot attached)
  "Error stating file: No such file or directory"

  What is expected: Ignore the error, do not display error to user as it
  is not productive, instead show the user's home directory as the
  default path to save if the last path used is not available.

  I will report if this happens under any other applications as well. If
  anyone has experienced this using another application please report it
  below.

  Version Information:
  Ubuntu Hardy (2.6.24-19-generic)
  gimp 2.4.5-1ubuntu2
  thunderbird 2.0.0.16+nobinonly-0ubuntu0.8.04.1

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

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

[Touch-packages] [Bug 1756800] Re: Failed to start AppArmor initialization with status=123/n/a

[Seth Arnold]

Ron, you look at the profiles that failed to compile/load in the
journalctl -u apparmor output, and decide what to do with those profiles
-- if they are for programs that no longer exist because the package has
since been removed, you can just delete the profile file. If they are
for programs that you use, then you should fix whatever error is in the
profile.

More details would require more details. Consider filing a new bug if
you've got this error with profiles that were provided by a package.

Thanks

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

Title:
  Failed to start AppArmor initialization with status=123/n/a

Status in apparmor package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Won't Fix

Bug description:
  AppArmor in Ubuntu 18.04 fails to start every time:

  $ systemctl status apparmor.service 
  ● apparmor.service - AppArmor initialization
 Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Mon 2018-03-19 13:47:22 AWST; 56s 
ago
   Docs: man:apparmor(7)
 http://wiki.apparmor.net/
Process: 773 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)
   Main PID: 773 (code=exited, status=123)

  Mar 19 13:47:21 xps15-9560 apparmor[773]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor in /e
  Mar 19 13:47:21 xps15-9560 apparmor[773]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Mar 19 13:47:22 xps15-9560 apparmor[773]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Mar 19 13:47:22 xps15-9560 apparmor[773]: AppArmor parser error for 
/etc/apparmor.d/usr.bin.webbrowser-app in /etc/apparmor.d/usr.bin.web
  Mar 19 13:47:22 xps15-9560 apparmor[773]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor in /e
  Mar 19 13:47:22 xps15-9560 apparmor[773]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Mar 19 13:47:22 xps15-9560 apparmor[773]:...fail!
  Mar 19 13:47:22 xps15-9560 systemd[1]: apparmor.service: Main process exited, 
code=exited, status=123/n/a
  Mar 19 13:47:22 xps15-9560 systemd[1]: apparmor.service: Failed with result 
'exit-code'.
  Mar 19 13:47:22 xps15-9560 systemd[1]: Failed to start AppArmor 
initialization.

  
  journalctl -xe gives essentially the same lack of information issued after a 
systemctl restart apparmor.service.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apparmor 2.11.0-2ubuntu19
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Mon Mar 19 13:50:42 2018
  InstallationDate: Installed on 2017-08-16 (214 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-12-generic 
root=UUID=0eb64261-6dff-464a-8373-596794c1fafe ro rootflags=subvol=@ quiet 
splash acpi_rev_override=5 scsi_mod.use_blk_mq=1 vt.handoff=1
  SourcePackage: apparmor
  Syslog:
   Mar 19 13:47:22 xps15-9560 dbus-daemon[1252]: [system] AppArmor D-Bus 
mediation is enabled
   Mar 19 13:47:23 xps15-9560 dbus-daemon[1491]: [session uid=125 pid=1491] 
AppArmor D-Bus mediation is enabled
   Mar 19 13:47:39 xps15-9560 dbus-daemon[2160]: [session uid=1001 pid=2160] 
AppArmor D-Bus mediation is enabled
  UpgradeStatus: Upgraded to bionic on 2017-11-17 (121 days ago)
  mtime.conffile..etc.apparmor.d.abstractions.nameservice: 
2017-10-24T16:47:24.395996

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

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

[Touch-packages] [Bug 1778140] Re: resize2fs hoses a filesystem on lvm after resizing

[Maurice Volaski]

Here is the output after the resize. The original was 59.02 GB and I am
resizing to 30G.

** Attachment added: "after.txt"
   
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1778140/+attachment/5156598/+files/after.txt

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

Title:
  resize2fs hoses a filesystem on lvm after resizing

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  Resized an ext4 filesystem on LVM. Before resizing, I confirmed
  filesystem was clean with e2fsck. After resizing, three errors were
  found.

  root@ubuntu:~# e2fsck -f /dev/ubuntu-vg/root
  e2fsck 1.44.1 (24-Mar-2018)
  Pass 1: Checking inodes, blocks, and sizes
  Inode 21110 extent block passes checks, but checksum does not match extent
(logical block 18432, physical block 503808, len 3813)
  Fix? no
  Inode 26807 extent block passes checks, but checksum does not match extent
(logical block 34816, physical block 768000, len 896)
  Fix? no
  Inode 28306 extent block passes checks, but checksum does not match extent
(logical block 30720, physical block 430080, len 5130)
  Fix? no
  Pass 2: Checking directory structure
  Pass 3: Checking directory connectivity
  Pass 4: Checking reference counts
  Pass 5: Checking group summary information

  
  This setup is currently in a virtual machine with a snapshot, so I can revert 
back and retest. The resize2fs is coming from the 18.04 Ubuntu CD.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: e2fsprogs 1.44.1-1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 21 21:03:56 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: e2fsprogs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1777711] Re: modemmanager 1.7.990-1ubuntu1 does not see my usb dongle

[Ivan Denkov]

Looks like the same bug to me.
Ubuntu 18.04
Package: modemmanager
Version: 1.6.8-2ubuntu1

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

Title:
  modemmanager 1.7.990-1ubuntu1 does not see my usb dongle

Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  modemmanager 1.7.990-1ubuntu1 on my Ubuntu Cosmic does not see my usb dongles 
while 1.6.8-2ubuntu1 on Ubunty Bionic and Artful (same PC, different partition) 
is ok. Same problem on my laptop. 
  Problem happens with different dongle of different factories.

  corrado@corrado-p7-cc-0527:~$ apt policy modemmanager
  modemmanager:
Installed: 1.7.990-1ubuntu1
Candidate: 1.7.990-1ubuntu1
Version table:
   *** 1.7.990-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p7-cc-0527:~$ lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
  Bus 001 Device 003: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
  Bus 001 Device 002: ID 19d2:0037 ZTE WCDMA Technologies MSM 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  corrado@corrado-p7-cc-0527:~$ mmcli -L

  No modems were found

  corrado@corrado-p7-cc-0527:~$ lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
  Bus 001 Device 003: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
  Bus 001 Device 006: ID 19d2:0037 ZTE WCDMA Technologies MSM 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  corrado@corrado-p7-cc-0527:~$ mmcli -L

  No modems were found

  corrado@corrado-p7-cc-0527:~$ lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
  Bus 001 Device 003: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
  Bus 001 Device 008: ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA 
Modem / E230/E270/E870 HSDPA/HSUPA Modem
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  corrado@corrado-p7-cc-0527:~$ mmcli -L

  No modems were found

  corrado@corrado-p7-cc-0527:~$ inxi -Fx
  System:
Host: corrado-p7-cc-0527 Kernel: 4.15.0-23-generic x86_64 bits: 64 
compiler: gcc v: 7.3.0 Desktop: Gnome 3.28.1 
Distro: Ubuntu Cosmic Cuttlefish (development branch) 
  Machine:
Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial:  
UEFI: American Megatrends v: P1.10 date: 05/11/2017 
  CPU:
Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP 
arch: Skylake rev: 9 L2 cache: 3072 KiB 
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31296 
Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 801 2: 800 
3: 800 4: 801 
  Graphics:
Card-1: Intel HD Graphics 630 driver: i915 v: kernel bus ID: 00:02.0 
Display: x11 server: X.Org 1.19.6 driver: i915 resolution: 1920x1080~60Hz 
OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) 
v: 4.5 Mesa 18.1.1 direct render: Yes 
  Audio:
Card-1: Intel Sunrise Point-H HD Audio driver: snd_hda_intel v: kernel 
bus ID: 00:1f.3 
Sound Server: ALSA v: k4.15.0-23-generic 
  Network:
Card-1: Intel Ethernet Connection I219-V driver: e1000e v: 3.2.6-k 
port: N/A bus ID: 00:1f.6 
IF: enp0s31f6 state: up speed: 100 Mbps duplex: full 
mac: 70:85:c2:44:7b:86 
  Drives:
HDD Total Size: 931.51 GiB used: 8.48 GiB (0.9%) 
ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB 
  Partition:
ID-1: / size: 31.25 GiB used: 8.47 GiB (27.1%) fs: ext4 dev: /dev/sda7 
ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 
  Sensors:
System Temperatures: cpu: 44.5 C mobo: N/A 
Fan Speeds (RPM): N/A 
  Info:
Processes: 236 Uptime: 26m Memory: 7.50 GiB used: 1.12 GiB (14.9%) 
Init: systemd runlevel: 5 Compilers: gcc: N/A Shell: bash v: 4.4.19 
inxi: 3.0.12 
  corrado@corrado-p7-cc-0527:~$ 

  
  corrado@corrado-p8-bionic:~$ apt policy modemmanager
  modemmanager:
Installed: 1.6.8-2ubuntu1
Candidate: 1.6.8-2ubuntu1
Version table:
   *** 1.6.8-2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p8-bionic:~$ lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
  Bus 001 Device 003: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
  Bus 001 Device 002: ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA 
Modem / E230/E270/E870 HSDPA/HSUPA Modem
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  corrado@corrado-p8-bionic:~$ mmcli -L

  

[Touch-packages] [Bug 1778140] Re: resize2fs hoses a filesystem on lvm after resizing

[Maurice Volaski]

Here is the dump2efs before the filesystem resize was attempted.

** Attachment added: "before.txt"
   
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1778140/+attachment/5156597/+files/before.txt

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

Title:
  resize2fs hoses a filesystem on lvm after resizing

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  Resized an ext4 filesystem on LVM. Before resizing, I confirmed
  filesystem was clean with e2fsck. After resizing, three errors were
  found.

  root@ubuntu:~# e2fsck -f /dev/ubuntu-vg/root
  e2fsck 1.44.1 (24-Mar-2018)
  Pass 1: Checking inodes, blocks, and sizes
  Inode 21110 extent block passes checks, but checksum does not match extent
(logical block 18432, physical block 503808, len 3813)
  Fix? no
  Inode 26807 extent block passes checks, but checksum does not match extent
(logical block 34816, physical block 768000, len 896)
  Fix? no
  Inode 28306 extent block passes checks, but checksum does not match extent
(logical block 30720, physical block 430080, len 5130)
  Fix? no
  Pass 2: Checking directory structure
  Pass 3: Checking directory connectivity
  Pass 4: Checking reference counts
  Pass 5: Checking group summary information

  
  This setup is currently in a virtual machine with a snapshot, so I can revert 
back and retest. The resize2fs is coming from the 18.04 Ubuntu CD.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: e2fsprogs 1.44.1-1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 21 21:03:56 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: e2fsprogs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 718635] Re: Error message "Your computer does not have enough free memory" when core dump or stacktrace failed to be created is misleading

[themusicgod1]

** Tags added: bionic

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

Title:
  Error message "Your computer does not have enough free memory" when
  core dump or stacktrace failed to be created is misleading

Status in apport package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: apport

  On Unity fully updated, when I login there is a X crash (attached), an apport 
dialog is displayed but complains about:
  ---
  Sorry, the program "Xorg" closed unexpectedly

  Your computer does not have enough free memory to automatically analyze the 
problem and send a report to the developers.
  ---

  You can only close and the report is canceled.

  Of course there's enough memory

  This message is displayed when the core dump or stacktrace can't be
  attached to the report. This should be changed to something closer to
  the real issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: apport 1.17.2-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-3.30-generic 2.6.38-rc4
  Uname: Linux 2.6.38-3-generic i686
  ApportLog:
   ERROR: apport (pid 8213) Mon Feb 14 10:17:49 2011: called for pid 741, 
signal 6
   ERROR: apport (pid 8213) Mon Feb 14 10:17:49 2011: executable: /usr/bin/Xorg 
(command line "/usr/bin/X :0 -br -verbose -auth 
/var/run/gdm/auth-for-gdm-ics1IG/database -nolisten tcp vt7")
  Architecture: i386
  Date: Mon Feb 14 10:54:38 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110209)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US.UTF-8:en
   LANG=en_US.UTF-8
   LC_MESSAGES=en_AG.utf8
   SHELL=/bin/bash
  SourcePackage: apport

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

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

[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.

[Launchpad Bug Tracker]

This bug was fixed in the package ubiquity - 18.10.4

---
ubiquity (18.10.4) cosmic; urgency=medium

  [ Chen-Han Hsiao (Stanley) ]
  * Add efivars to mountpoints loaded at bootloader install time.
(LP: #1772374)

  [ Steve Langasek ]
  * scripts/plugininstall.py: don't hard-code a resume partition in
/etc/initramfs-tools/conf.d/resume at install time.  In bionic and later,
initramfs-tools will autodetect an appropriate resume partition at
initramfs generation time, so ubiquity's resume setting is redundant and
possibly wrong.  LP: #1768230.

  [ Łukasz 'sil2100' Zemczak ]
  * Make sure that grub-pc is not removed after installation for both EFI and
legacy BIOS cases as we now technically need it even for EFI installs.
(LP: #1775743)

  [ Mathieu Trudel-Lapierre ]
  * Automatic update of included source packages: grub-installer
1.128ubuntu9.

 -- Mathieu Trudel-Lapierre   Mon, 25 Jun 2018
13:57:40 -0400

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

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

Title:
  Long time booting : Failed to connect to lvmetad. Falling back to
  device scanning.

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Fix Committed

Bug description:
  [SRU Justification]
  A regression in initramfs-tools causes it to autogenerate config in the 
initramfs saying to resume from any available swap devices, but references the 
swap device by UUID, which is not a canonical form for referring to LVM volumes 
(because of snapshotting, they are not unique).  Ubiquity also generates a file 
in /etc at install time which references the swap partition in the same way.  
Since the lvm2 initramfs hooks also only activate precisely those LVs that are 
detected as needed at boot, this adds an inappropriate 30-second boot delay to 
any system with swap on LVM, which includes any desktop system that was 
configured with LVM (but not full-disk encryption) at install time.

  [Test case]
  1. Install using the "Use LVM" option in the desktop installer.
  4. Reboot.
  5. Verify that dmesg shows a 30-second delay before mounting the root 
filesystem.
  6. Install initramfs-tools from bionic-proposed.
  7. Reboot.
  8. Verify that dmesg no longer shows a 30-second delay before mounting the 
root filesystem.
  9. Install using the bionic daily image that contains the ubiquity from 
bionic-proposed.
  10. Reboot.
  11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that 
there is no delay before mounting the root filesystem.

  [Regression potential]
  This makes changes to shell scripts, and shell is a perilous language. An 
unnoticed bug could cause all initramfs generation, and thus all kernel 
installation, to fail for some users. A regression could also cause a user to 
lose hiberation support that they currently have.

  [Original description]
  After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu 
installation", the
  system is very slow to reboot.

  It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to 
device scanning.",
  then waits 32 seconds, then continues as it should.

  I think this is a ubiquity bug, since the d-i based installer is not affected.
   - ubuntu-18.04-desktop-amd64.iso 
(a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected
   - xubuntu-18.04-desktop-amd64.iso 
(7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected
   - ubuntu-18.04-server-amd64.iso 
(a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not 
affected

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

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

[Touch-packages] [Bug 1773167]

[RussianNeuroMancer]

> What does the EDID contain when there is an HDMI output but cable is
not plugged in?

On devices with physical HDMI output get-edid return nothing (because no 
devices HDMI is attached).
On devices without HDMI output, such as Lenovo Miix2 8, EDID contain this:

[5.431895] i915 :00:02.0: HDMI-A-2: EDID is invalid:
[5.431902]  [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[5.431904]  [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[5.431906]  [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[5.431908]  [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[5.431910]  [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[5.431912]  [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[5.431914]  [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[5.431916]  [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

> It would seem more appropriate to do that already in the kernel,
though.

So I should fill separate report here, at freedesktop, or at kernel's
bugzilla? Which component I should choice?

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

Title:
  [Intel HDMI LPE driver] Audio is not working; pulseaudio consumes 100%
  of a single CPU core

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  On a krez ninja 1103 laptop audio is not working; pulseaudio consumes
  100% of a single CPU core. Pulseaudio log atached.

  According to perf, most CPU is consumed at __memset_erms.

  Below is the GDB stacktrace of pulseaudio.

  # gdb -p 1009 -batch -eval-command="thread apply all bt"
  [New LWP 1028]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  0x7fe2abb7e6d6 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, 
expected=0, futex_word=0x56318e574a30) at 
../sysdeps/unix/sysv/linux/futex-internal.h:205
  205   ../sysdeps/unix/sysv/linux/futex-internal.h: No such file or directory.

  Thread 2 (Thread 0x7fe2a7458700 (LWP 1028)):
  #0  0x7fe2ab063339 in _IO_str_init_static_internal 
(sf=sf@entry=0x7fe2a7453700, ptr=ptr@entry=0x7fe2a7453b80 "", 
size=size@entry=255, pstart=pstart@entry=0x7fe2a7453b80 "") at strops.c:36
  #1  0x7fe2ab10515b in ___vsnprintf_chk (s=0x7fe2a7453b80 "", 
maxlen=, flags=1, slen=, format=0x7fe2ac698e8d 
"%s%c: %s", args=0x7fe2a74538a0) at vsnprintf_chk.c:62
  #2  0x7fe2ac6601ca in pa_vsnprintf () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #3  0x7fe2ac660366 in pa_snprintf () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #4  0x7fe2ac66bda8 in pa_log_levelv_meta () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #5  0x7fe2ac66b655 in pa_log_level_meta () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #6  0x7fe2a52b36ae in ?? () from 
/usr/lib/pulse-11.1/modules/libalsa-util.so
  #7  0x7fe2ac68c2a8 in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #8  0x7fe2abb756db in start_thread (arg=0x7fe2a7458700) at 
pthread_create.c:463
  #9  0x7fe2ab0f488f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

  Thread 1 (Thread 0x7fe2acfe7500 (LWP 1009)):
  #0  0x7fe2abb7e6d6 in futex_abstimed_wait_cancelable (private=0, 
abstime=0x0, expected=0, futex_word=0x56318e574a30) at 
../sysdeps/unix/sysv/linux/futex-internal.h:205
  #1  do_futex_wait (sem=sem@entry=0x56318e574a30, abstime=0x0) at 
sem_waitcommon.c:111
  #2  0x7fe2abb7e7c8 in __new_sem_wait_slow (sem=0x56318e574a30, 
abstime=0x0) at sem_waitcommon.c:181
  #3  0x7fe2ac68c502 in pa_semaphore_wait () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #4  0x7fe2ac8cca24 in pa_asyncmsgq_send () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-11.1.so
  #5  0x7fe2a6841119 in ?? () from 
/usr/lib/pulse-11.1/modules/libprotocol-native.so
  #6  0x7fe2ac675ee2 in pa_pdispatch_run () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #7  0x7fe2a6844695 in ?? () from 
/usr/lib/pulse-11.1/modules/libprotocol-native.so
  #8  0x7fe2ac678bef in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #9  0x7fe2ac67b6ab in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #10 0x7fe2ac67ba49 in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #11 0x7fe2ac67c2cf in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #12 0x7fe2ac40e0d8 in pa_mainloop_dispatch () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
  #13 0x7fe2ac40e4ae in pa_mainloop_iterate () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
  #14 0x7fe2ac40e530 in pa_mainloop_run () from 

[Touch-packages] [Bug 1778551] Re: Add linux-modules* packages to VersionedKernelPackages

[Julian Andres Klode]

Yeah, probably. I have another two fixes queued, so I'll do a 1.2.27
tomorrow with all of them:

https://salsa.debian.org/apt-team/apt/compare/1.2.26...1.2.y

apt (1.2.27) UNRELEASED; urgency=medium

  [ David Kalnischkies ]
  * don't hang if multiple sources use unavailable method (Closes: 870675)
(LP: #1762766)

  [ Julian Andres Klode ]
  * Fix lock counting in debSystem (LP: #1778547)
  * apt.conf.autoremove: Catch some new Ubuntu module packages (LP: #1778551)

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

Title:
  Add linux-modules* packages to VersionedKernelPackages

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Triaged

Bug description:
  == SRU Justification ==

  Impact: The 4.15 hwe kernel includes some package shuffling, so the
  VersionedKernelPackages list in /etc/apt/apt.conf.d/01autoremove needs
  to be updated to include linux-modules* packages.

  Fix: Backport the conf file changes from bionic.

  Test Case: Confirm that linux-modules* packages are autoremoved
  according to the same rules used for linux-image* packages.

  Regression Potential: Minimal. Probably the worst case is that some
  packages that should be autoremoved are not, but since these changes
  have been in use in bionic for a while now no regressions are
  expected.

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

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

[Touch-packages] [Bug 1747023] Re: [P95_HR, Realtek ALC1220, Black Headphone Out, Right] No sound at all

[Casper]

Thanks, fix worked for me (related:
https://bugs.launchpad.net/bugs/1721074 )

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

Title:
  [P95_HR, Realtek ALC1220, Black Headphone Out, Right] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  External headphones don't work any more. Not sure if realted to the
  internal speakers problem: https://bugs.launchpad.net/ubuntu/+source
  /alsa-driver/+bug/1721074

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC0:  cc16   2550 F pulseaudio
   /dev/snd/controlC1:  cc16   2550 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Feb  2 14:51:06 2018
  InstallationDate: Installed on 2017-08-22 (164 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC0:  cc16   2550 F pulseaudio
   /dev/snd/controlC1:  cc16   2550 F pulseaudio
  Symptom_Jack: Black Headphone Out, Right
  Symptom_Type: No sound at all
  Title: [P95_HR, Realtek ALC1220, Black Headphone Out, Right] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P95_HR
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02:bd06/29/2017:svnPCSpecialistLimited:pnP95_HR:pvrNotApplicable:rvnCLEVO:rnP95_HR:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P95_HR
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

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

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

[Touch-packages] [Bug 1721074] Re: [P95_HR, Realtek Generic, Speaker, Internal] No sound at all

[Casper]

Thanks, fix worked for me (related:
https://bugs.launchpad.net/bugs/1747023 )

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

Title:
  [P95_HR, Realtek Generic, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  no sound at all. used to work a few weeks ago.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-36.40~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC1:  cc16   2656 F pulseaudio
   /dev/snd/pcmC0D0c:   cc16   2656 F...m pulseaudio
   /dev/snd/controlC0:  cc16   2656 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Oct  3 17:23:32 2017
  InstallationDate: Installed on 2017-08-22 (42 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC1:  cc16   2656 F pulseaudio
   /dev/snd/controlC0:  cc16   2656 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [P95_HR, Realtek Generic, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P95_HR
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02:bd06/29/2017:svnPCSpecialistLimited:pnP95_HR:pvrNotApplicable:rvnCLEVO:rnP95_HR:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: P95_HR
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

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

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

[Touch-packages] [Bug 1778551] Re: Add linux-modules* packages to VersionedKernelPackages

[Seth Forshee]

Other than simply checking the patterns in the file, I can't think of an
easier way to test. If you know of one please let me know. I do
currently have a vm set up to let me test it.

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

Title:
  Add linux-modules* packages to VersionedKernelPackages

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Triaged

Bug description:
  == SRU Justification ==

  Impact: The 4.15 hwe kernel includes some package shuffling, so the
  VersionedKernelPackages list in /etc/apt/apt.conf.d/01autoremove needs
  to be updated to include linux-modules* packages.

  Fix: Backport the conf file changes from bionic.

  Test Case: Confirm that linux-modules* packages are autoremoved
  according to the same rules used for linux-image* packages.

  Regression Potential: Minimal. Probably the worst case is that some
  packages that should be autoremoved are not, but since these changes
  have been in use in bionic for a while now no regressions are
  expected.

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

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

[Touch-packages] [Bug 1778551] Re: Add linux-modules* packages to VersionedKernelPackages

[Seth Forshee]

Hmm, now that I actually look at how the file is used, I guess we could
verify the list generated by /etc/kernel/postinst.d/apt-auto-removal,
couldn't we?

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

Title:
  Add linux-modules* packages to VersionedKernelPackages

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Triaged

Bug description:
  == SRU Justification ==

  Impact: The 4.15 hwe kernel includes some package shuffling, so the
  VersionedKernelPackages list in /etc/apt/apt.conf.d/01autoremove needs
  to be updated to include linux-modules* packages.

  Fix: Backport the conf file changes from bionic.

  Test Case: Confirm that linux-modules* packages are autoremoved
  according to the same rules used for linux-image* packages.

  Regression Potential: Minimal. Probably the worst case is that some
  packages that should be autoremoved are not, but since these changes
  have been in use in bionic for a while now no regressions are
  expected.

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

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

Re: [Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.

[Steve Langasek]

Daniel, Silvio, can you please confirm that your disk configuration matches
that of Marc, with full-disk LVM selected at install time?  It's possible
you have boot delays due to some other cause.

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

Title:
  Long time booting : Failed to connect to lvmetad. Falling back to
  device scanning.

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Bionic:
  Fix Committed

Bug description:
  [SRU Justification]
  A regression in initramfs-tools causes it to autogenerate config in the 
initramfs saying to resume from any available swap devices, but references the 
swap device by UUID, which is not a canonical form for referring to LVM volumes 
(because of snapshotting, they are not unique).  Ubiquity also generates a file 
in /etc at install time which references the swap partition in the same way.  
Since the lvm2 initramfs hooks also only activate precisely those LVs that are 
detected as needed at boot, this adds an inappropriate 30-second boot delay to 
any system with swap on LVM, which includes any desktop system that was 
configured with LVM (but not full-disk encryption) at install time.

  [Test case]
  1. Install using the "Use LVM" option in the desktop installer.
  4. Reboot.
  5. Verify that dmesg shows a 30-second delay before mounting the root 
filesystem.
  6. Install initramfs-tools from bionic-proposed.
  7. Reboot.
  8. Verify that dmesg no longer shows a 30-second delay before mounting the 
root filesystem.
  9. Install using the bionic daily image that contains the ubiquity from 
bionic-proposed.
  10. Reboot.
  11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that 
there is no delay before mounting the root filesystem.

  [Regression potential]
  This makes changes to shell scripts, and shell is a perilous language. An 
unnoticed bug could cause all initramfs generation, and thus all kernel 
installation, to fail for some users. A regression could also cause a user to 
lose hiberation support that they currently have.

  [Original description]
  After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu 
installation", the
  system is very slow to reboot.

  It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to 
device scanning.",
  then waits 32 seconds, then continues as it should.

  I think this is a ubiquity bug, since the d-i based installer is not affected.
   - ubuntu-18.04-desktop-amd64.iso 
(a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected
   - xubuntu-18.04-desktop-amd64.iso 
(7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected
   - ubuntu-18.04-server-amd64.iso 
(a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not 
affected

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

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

[Touch-packages] [Bug 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers with DVD

[Jerry Clement]

** Summary changed:

- Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers
+ Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers 
with DVD

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

Title:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers with DVD

Status in dellserver:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New
Status in linux source package in Bionic:
  Incomplete
Status in systemd source package in Bionic:
  New

Bug description:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers when under graceful reboot stress for 12hrs.

  * This hand is observed only when Onboard SATA DVD Drive is connected.

  * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13)

  * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic)

  Steps:
  Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and 
start reboot stress
  After a few reboots, observe that the machine hangs at "kvm: exiting hardware 
virtualization" and does not proceed with reboot cycles.

  Only physical reset helps in continuing the reboot test.

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

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

[Touch-packages] [Bug 1778497] Re: Add a remember option to whoopsie so that users can diminish crash interactions

[Didier Roche]

** Branch linked: lp:~didrocks/apport/whoopsie-auto-ui

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

Title:
  Add a remember option to whoopsie so that users can diminish crash
  interactions

Status in apport package in Ubuntu:
  New
Status in apport source package in Bionic:
  New

Bug description:
  [ Impact ]
  A lot of users are bother by the number of whoopsie dialog. We introduced on 
"G-C-C privacy option don't allow sending manual report" bug 
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1774597) a 
way for users to change from always reporting manually (prompting an UI) to 
auto reporting or never reporting, via a "Remember this in future".

  This only impacts the apport gtk UI, still offering the underlying
  capability to other UIs type without changing them.

  This was a goal for 18.04, but due to a lack of time, we want to
  introduce this in 18.04.1

  [ Test Case ]
   * There are multiples dialog forms (a good 20 of them), but they are all 
covered by unit tests which have been updates. One use case would be:
   * Install the new version and trigger a crash
   * Check that the dialog has a "Remember this in future" option, check it, 
and click send.
   * Check in g-c-c UI, privacy option, that the crash reporting is now in auto 
mode, always send.
   * Revert in g-c-c to manual
   * Create another crash, check "Remember this…" and click don't send
   * Check in g-c-c UI that crash reporting is now disabled.

  [ Regression potential ]
   * The impacted code is both UI and fileutils. It's covered by an extensive 
testsuite, and checking under KDE has also been done to not trigger a crash.

  

  We introduce 5 enw strings to translate:
  "Can't remember send report status settings"
  "Saving crash reporting state failed. Can't set auto or never reporting mode."
  "Remember this in future"
  "Relaunch this application"
  "Don't send"

  We are reusing an existing transalted string "Send problem report to
  the developers?"

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

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

[Touch-packages] [Bug 1778551] Re: Add linux-modules* packages to VersionedKernelPackages

[Julian Andres Klode]

Yup. We probably want an easier test case, though?

** Also affects: apt (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: apt (Ubuntu Xenial)
   Status: New => Triaged

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

Title:
  Add linux-modules* packages to VersionedKernelPackages

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Triaged

Bug description:
  == SRU Justification ==

  Impact: The 4.15 hwe kernel includes some package shuffling, so the
  VersionedKernelPackages list in /etc/apt/apt.conf.d/01autoremove needs
  to be updated to include linux-modules* packages.

  Fix: Backport the conf file changes from bionic.

  Test Case: Confirm that linux-modules* packages are autoremoved
  according to the same rules used for linux-image* packages.

  Regression Potential: Minimal. Probably the worst case is that some
  packages that should be autoremoved are not, but since these changes
  have been in use in bionic for a while now no regressions are
  expected.

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

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

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

[Dimitri John Ledkov ]

The v239 merge for cosmic is in progress at the moment. There are a few
regressions that need to be worked around.

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

Title:
  networkd should allow configuring IPV6 MTU

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  1) Zesty
  2) systemd-232-19
  3) I need to configure the IPV6 MTU for tunneling by adding an 
IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 
static address in the [Network] section
  4) networkd does not parse or read the value and does not apply this 
configuration to the interface.

  Upstream has discussed this issue here:

  https://github.com/systemd/systemd/pull/1533

  But it's been closed in favor of only setting via RA.

  However, we know of multiple use-case which are currently supported in
  ifdupdown where we want to retain control over IPV6 MTU values outside
  of PMTU Discovery configurations.

  
  Some context from those discussions

  
  >> Client systems that route their ipv6 packets to a 6in4 router also
  >> have to have their ipv6 mtu lowered.  They could lower their link mtu,
  >> so their ipv6 packets are small enough, but that reduces performance
  >> of their ipv4 network.

  Yes.  Anything that creates a PMTUD black hole can result in
  situations where the higher header overhead of IPv6 will cause IPv4 to
  pass but IPv6 traffic to be dropped.

  One example here is egress from an ipsec tunnel wherein the next
  hop MTU is too low for IPv6 datagrams to pass.  Another is VM ->
  whatever -> host bridge -> tunnel ingress.  If the datagram cannot enter
  the tunnel due to size, it is dropped, and an ICMP response uses the
  tunnel address as a source, which may not be routable back to the
  origin.  This one is an issue with IPv4 as well, and is one case where
  manually setting the IPv6 MTU lower than the (also manually set) device
  MTU is of benefit.

  In essence, any of these sort of cases that require an explicit
  setting of the device MTU will likely require a setting of the IPv6 mtu
  as well to account for its larger header overhead.

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

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

[Touch-packages] [Bug 1778497] Re: Add a remember option to whoopsie so that users can diminish crash interactions

[Didier Roche]

** Description changed:

  [ Impact ]
  A lot of users are bother by the number of whoopsie dialog. We introduced on 
"G-C-C privacy option don't allow sending manual report" bug 
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1774597) a 
way for users to change from always reporting manually (prompting an UI) to 
auto reporting or never reporting, via a "Remember this in future".
  
  This only impacts the apport gtk UI, still offering the underlying
  capability to other UIs type without changing them.
  
  This was a goal for 18.04, but due to a lack of time, we want to
  introduce this in 18.04.1
  
  [ Test Case ]
-  * There are multiples dialog forms (a good 20 of them), but they are all 
covered by unit tests which have been updates. One use case would be:
-  * Install the new version and trigger a crash
-  * Check that the dialog has a "Remember this in future" option, check it, 
and click send.
-  * Check in g-c-c UI, privacy option, that the crash reporting is now in auto 
mode, always send.
-  * Revert in g-c-c to manual
-  * Create another crash, check "Remember this…" and click don't send
-  * Check in g-c-c UI that crash reporting is now disabled.
+  * There are multiples dialog forms (a good 20 of them), but they are all 
covered by unit tests which have been updates. One use case would be:
+  * Install the new version and trigger a crash
+  * Check that the dialog has a "Remember this in future" option, check it, 
and click send.
+  * Check in g-c-c UI, privacy option, that the crash reporting is now in auto 
mode, always send.
+  * Revert in g-c-c to manual
+  * Create another crash, check "Remember this…" and click don't send
+  * Check in g-c-c UI that crash reporting is now disabled.
  
  [ Regression potential ]
-  * The impacted code is both UI and fileutils. It's covered by an extensive 
testsuite, and checking under KDE has also been done to not trigger a crash.
+  * The impacted code is both UI and fileutils. It's covered by an extensive 
testsuite, and checking under KDE has also been done to not trigger a crash.
+ 
+ 
+ 
+ We introduce 5 enw strings to translate:
+ "Can't remember send report status settings"
+ "Saving crash reporting state failed. Can't set auto or never reporting mode."
+ "Remember this in future"
+ "Relaunch this application"
+ "Don't send"
+ 
+ We are reusing an existing transalted string "Send problem report to the
+ developers?"

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

Title:
  Add a remember option to whoopsie so that users can diminish crash
  interactions

Status in apport package in Ubuntu:
  New
Status in apport source package in Bionic:
  New

Bug description:
  [ Impact ]
  A lot of users are bother by the number of whoopsie dialog. We introduced on 
"G-C-C privacy option don't allow sending manual report" bug 
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1774597) a 
way for users to change from always reporting manually (prompting an UI) to 
auto reporting or never reporting, via a "Remember this in future".

  This only impacts the apport gtk UI, still offering the underlying
  capability to other UIs type without changing them.

  This was a goal for 18.04, but due to a lack of time, we want to
  introduce this in 18.04.1

  [ Test Case ]
   * There are multiples dialog forms (a good 20 of them), but they are all 
covered by unit tests which have been updates. One use case would be:
   * Install the new version and trigger a crash
   * Check that the dialog has a "Remember this in future" option, check it, 
and click send.
   * Check in g-c-c UI, privacy option, that the crash reporting is now in auto 
mode, always send.
   * Revert in g-c-c to manual
   * Create another crash, check "Remember this…" and click don't send
   * Check in g-c-c UI that crash reporting is now disabled.

  [ Regression potential ]
   * The impacted code is both UI and fileutils. It's covered by an extensive 
testsuite, and checking under KDE has also been done to not trigger a crash.

  

  We introduce 5 enw strings to translate:
  "Can't remember send report status settings"
  "Saving crash reporting state failed. Can't set auto or never reporting mode."
  "Remember this in future"
  "Relaunch this application"
  "Don't send"

  We are reusing an existing transalted string "Send problem report to
  the developers?"

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

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

[Touch-packages] [Bug 1778557] [NEW] ubuntu-bug works properly only if we are in $HOME dir

[Victor Porton]

Public bug reported:

Chdir to any dir except $HOME.

Run

ubuntu-bug cheese

(You probably should install cheese before doing this.)

Answer the questions and press Send button.

A dialog says:

[Errno 2] No such file or directory: '.cache/CheeseDebug.txt'

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apport 2.20.9-0ubuntu7.2
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 25 19:19:36 2018
InstallationDate: Installed on 2018-06-23 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IL
 SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  ubuntu-bug works properly only if we are in $HOME dir

Status in apport package in Ubuntu:
  New

Bug description:
  Chdir to any dir except $HOME.

  Run

  ubuntu-bug cheese

  (You probably should install cheese before doing this.)

  Answer the questions and press Send button.

  A dialog says:

  [Errno 2] No such file or directory: '.cache/CheeseDebug.txt'

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.2
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 25 19:19:36 2018
  InstallationDate: Installed on 2018-06-23 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IL
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1408092] Re: sysconfig.get_path('purelib') points to site-packages directory

[tripzero]

The issue is that /usr/lib/python3/sysconfig.py is hardcoded to 'site-
packages' (see _INSTALL_SCHEMES variable in the code).  If your code
uses sysconfig.get_path() to get the python3 site dir, it will fail on
ubuntu.

So either the fix needs to change /usr/lib/python3/sysconfig.py or
packages need to be fixed to use distutils

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

Title:
  sysconfig.get_path('purelib') points to site-packages directory

Status in python3-defaults package in Ubuntu:
  Confirmed
Status in python3.5 package in Ubuntu:
  Confirmed

Bug description:
  purelib and platlib paths in Python 3 sysconfig module point to site-
  packages directory:

  $ python3 -m sysconfig

  Platform: "linux-x86_64"
  Python version: "3.4"
  Current installation scheme: "posix_prefix"

  Paths: 
data = "/usr"
include = "/usr/include/python3.4m"
platinclude = "/usr/include/python3.4m"
platlib = "/usr/lib/python3.4/site-packages"
platstdlib = "/usr/lib/python3.4"
purelib = "/usr/lib/python3.4/site-packages"
scripts = "/usr/bin"
stdlib = "/usr/lib/python3.4"
  ...

  whereas Python 2 points to dist-packages:

  Platform: "linux-x86_64"
  Python version: "2.7"
  Current installation scheme: "posix_local"

  Paths: 
data = "/usr/local"
include = "/usr/local/include/python2.7"
platinclude = "/usr/local/include/python2.7"
platlib = "/usr/local/lib/python2.7/dist-packages"
platstdlib = "/usr/lib/python2.7"
purelib = "/usr/local/lib/python2.7/dist-packages"
scripts = "/usr/local/bin"
stdlib = "/usr/lib/python2.7"
  ...

  One severe consequence of this is that automake is installing Python
  modules to a location which is not in sys.path, namely site-packages
  directory.

  When one uses automake to create a Makefile that installs a Python
  module to the system, it is installed into /usr/local/lib/python3.4
  /site-packages since automake/aclocal uses sysconfig to determine
  where the package will be installed.

  From /usr/share/aclocal-1.14/python.m4 file:

AC_CACHE_CHECK([for $am_display_PYTHON script directory],
  [am_cv_python_pythondir],
  [if test "x$prefix" = xNONE
   then
 am_py_prefix=$ac_default_prefix
   else
 am_py_prefix=$prefix
   fi
   am_cv_python_pythondir=`$PYTHON -c "
  $am_python_setup_sysconfig
  if can_use_sysconfig:
  sitedir = sysconfig.get_path('purelib', vars={'base':'$am_py_prefix'})
  <---
  else:
  from distutils import sysconfig
  ...

  Here, it can be seen that automake uses purelib path defined by the
  sysconfig module of Python. However, since this path is not included
  in sys.path, and thus the installed package cannot be used:

  $ python3 -c "import sys; print(sys.path)"
  ['', '/usr/lib/python3.4', '/usr/lib/python3.4/plat-x86_64-linux-gnu', 
'/usr/lib/python3.4/lib-dynload', '/usr/local/lib/python3.4/dist-packages', 
'/usr/lib/python3/dist-packages']

  
  Ubuntu version:14.10

  $ apt-cache policy python3-minimal 
  python3-minimal:
Installed: 3.4.2-1
Candidate: 3.4.2-1
Version table:
   *** 3.4.2-1 0
  500 http://mirror.23media.de/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1778551] [NEW] Add linux-modules* packages to VersionedKernelPackages

[Seth Forshee]

Public bug reported:

== SRU Justification ==

Impact: The 4.15 hwe kernel includes some package shuffling, so the
VersionedKernelPackages list in /etc/apt/apt.conf.d/01autoremove needs
to be updated to include linux-modules* packages.

Fix: Backport the conf file changes from bionic.

Test Case: Confirm that linux-modules* packages are autoremoved
according to the same rules used for linux-image* packages.

Regression Potential: Minimal. Probably the worst case is that some
packages that should be autoremoved are not, but since these changes
have been in use in bionic for a while now no regressions are expected.

** Affects: apt (Ubuntu)
 Importance: Undecided
 Status: Fix Released

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

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

Title:
  Add linux-modules* packages to VersionedKernelPackages

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  == SRU Justification ==

  Impact: The 4.15 hwe kernel includes some package shuffling, so the
  VersionedKernelPackages list in /etc/apt/apt.conf.d/01autoremove needs
  to be updated to include linux-modules* packages.

  Fix: Backport the conf file changes from bionic.

  Test Case: Confirm that linux-modules* packages are autoremoved
  according to the same rules used for linux-image* packages.

  Regression Potential: Minimal. Probably the worst case is that some
  packages that should be autoremoved are not, but since these changes
  have been in use in bionic for a while now no regressions are
  expected.

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

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

[Touch-packages] [Bug 1175608] Re: Thumbnails too small in 'open file' dialog nautilus

[xl_cheese]

Is there ever going to be a fix for this?  Everytime I have to attached
a picture from a file full of pictures I have to go to my file browser
first and make a mental note of the file name.  Then when I attached or
upload the picture I have to choose based on remembering the filename.

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

Title:
  Thumbnails too small in 'open file' dialog nautilus

Status in Nautilus:
  Expired
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  When trying to upload image files to e.g. websites like marktplaats.nl
  (kind of ebay) I get  very, very small image thumbnails. There seems
  no way to enlarge these thumbnails. All options only work if Nautilus
  is used stand alone, but not with the open file dialog that is being
  used to upload files.

  I have attached a screen dump just to show what I mean.

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

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

[Touch-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

[Iain Lane]

They're all uploaded now. To the SRU team - these are quite delicate
SRUs. I think they're right, but more eyes would be appreciated.

The essence is that when nux-tools is removed-not-purged at a buggy
version, the leftover conffile is harmful. So we picked a core package,
x11-common, and made it stash the conffile away. Then nux-tools will
pick it up if it's reinstalled and upgrade it to the fixed version in
the normal way.

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

Title:
  leftover conffile forces GNOME is software rendering

Status in nux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  In Progress
Status in nux source package in Xenial:
  Fix Committed
Status in xorg source package in Xenial:
  In Progress
Status in nux source package in Artful:
  Fix Committed
Status in xorg source package in Artful:
  In Progress
Status in nux source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  In Progress

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case - FOR WHO UPGRADES TO BIONIC/ARTFUL ]

  · Install xenial
  · Upgrade (nux-tools) and ensure that unity is still properly running after
a logout/login cycle.
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
    printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
    in an environment with no 3d support (VMs are easy tests)

  [ Test case - FOR WHO HAS ALREADY UPGRADED TO BIONIC/ARTFUL AND
  REMOVED UNITY ]

   · remove nux-tools from artful/bionic-release (pre-sru), upgrade,
 reinstall nux-tools (no prompt)
   · remove nux-tools from bionic-proposed/updates (sru), upgrade, reinstall
 nux-tools (nothing should be prompted)
   · modify config file, remove nux-tools, upgrade, reinstall nux-tools (should 
prompt)
   · install nux-tools, upgrade, no prompt

  You end up with either no /etc/X11/Xsession.d/50_check_unity_support,
  its new contents or you are asked what to do if you've changed it
  before. Never the old content.

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

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

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

[Touch-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

[Iain Lane]

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

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

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

Title:
  leftover conffile forces GNOME is software rendering

Status in nux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  In Progress
Status in nux source package in Xenial:
  Fix Committed
Status in xorg source package in Xenial:
  In Progress
Status in nux source package in Artful:
  Fix Committed
Status in xorg source package in Artful:
  In Progress
Status in nux source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  In Progress

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case - FOR WHO UPGRADES TO BIONIC/ARTFUL ]

  · Install xenial
  · Upgrade (nux-tools) and ensure that unity is still properly running after
a logout/login cycle.
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
    printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
    in an environment with no 3d support (VMs are easy tests)

  [ Test case - FOR WHO HAS ALREADY UPGRADED TO BIONIC/ARTFUL AND
  REMOVED UNITY ]

   · remove nux-tools from artful/bionic-release (pre-sru), upgrade,
 reinstall nux-tools (no prompt)
   · remove nux-tools from bionic-proposed/updates (sru), upgrade, reinstall
 nux-tools (nothing should be prompted)
   · modify config file, remove nux-tools, upgrade, reinstall nux-tools (should 
prompt)
   · install nux-tools, upgrade, no prompt

  You end up with either no /etc/X11/Xsession.d/50_check_unity_support,
  its new contents or you are asked what to do if you've changed it
  before. Never the old content.

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

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

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

[Touch-packages] [Bug 1756800] Re: Failed to start AppArmor initialization with status=123/n/a

[Ron]

This may be a dumb question, but once we *have* this bug, how do we fix
it?  I'm not that practiced at apparmor.

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

Title:
  Failed to start AppArmor initialization with status=123/n/a

Status in apparmor package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Won't Fix

Bug description:
  AppArmor in Ubuntu 18.04 fails to start every time:

  $ systemctl status apparmor.service 
  ● apparmor.service - AppArmor initialization
 Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Mon 2018-03-19 13:47:22 AWST; 56s 
ago
   Docs: man:apparmor(7)
 http://wiki.apparmor.net/
Process: 773 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)
   Main PID: 773 (code=exited, status=123)

  Mar 19 13:47:21 xps15-9560 apparmor[773]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor in /e
  Mar 19 13:47:21 xps15-9560 apparmor[773]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Mar 19 13:47:22 xps15-9560 apparmor[773]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Mar 19 13:47:22 xps15-9560 apparmor[773]: AppArmor parser error for 
/etc/apparmor.d/usr.bin.webbrowser-app in /etc/apparmor.d/usr.bin.web
  Mar 19 13:47:22 xps15-9560 apparmor[773]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor in /e
  Mar 19 13:47:22 xps15-9560 apparmor[773]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Mar 19 13:47:22 xps15-9560 apparmor[773]:...fail!
  Mar 19 13:47:22 xps15-9560 systemd[1]: apparmor.service: Main process exited, 
code=exited, status=123/n/a
  Mar 19 13:47:22 xps15-9560 systemd[1]: apparmor.service: Failed with result 
'exit-code'.
  Mar 19 13:47:22 xps15-9560 systemd[1]: Failed to start AppArmor 
initialization.

  
  journalctl -xe gives essentially the same lack of information issued after a 
systemctl restart apparmor.service.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apparmor 2.11.0-2ubuntu19
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Mon Mar 19 13:50:42 2018
  InstallationDate: Installed on 2017-08-16 (214 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-12-generic 
root=UUID=0eb64261-6dff-464a-8373-596794c1fafe ro rootflags=subvol=@ quiet 
splash acpi_rev_override=5 scsi_mod.use_blk_mq=1 vt.handoff=1
  SourcePackage: apparmor
  Syslog:
   Mar 19 13:47:22 xps15-9560 dbus-daemon[1252]: [system] AppArmor D-Bus 
mediation is enabled
   Mar 19 13:47:23 xps15-9560 dbus-daemon[1491]: [session uid=125 pid=1491] 
AppArmor D-Bus mediation is enabled
   Mar 19 13:47:39 xps15-9560 dbus-daemon[2160]: [session uid=1001 pid=2160] 
AppArmor D-Bus mediation is enabled
  UpgradeStatus: Upgraded to bionic on 2017-11-17 (121 days ago)
  mtime.conffile..etc.apparmor.d.abstractions.nameservice: 
2017-10-24T16:47:24.395996

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

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

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

[Ryan Harper]

I've just seen that upstream systemd v239 claims to support IPV6MtuBytes

https://lwn.net/Articles/758128/


* networkd's .network files now support a new IPv6MTUBytes= option for
setting the MTU used by IPv6 explicitly as well as a new MTUBytes=
option in the [Route] section to configure the MTU to use for
specific routes. It also gained support for configuration of the DHCP
"UserClass" option through the new UserClass= setting. It gained
three new options in the new [CAN] section for configuring CAN
networks. The MULTICAST and ALLMULTI interface flags may now be
controlled explicitly with the new Multicast= and AllMulticast=
settings.

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

Title:
  networkd should allow configuring IPV6 MTU

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  1) Zesty
  2) systemd-232-19
  3) I need to configure the IPV6 MTU for tunneling by adding an 
IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 
static address in the [Network] section
  4) networkd does not parse or read the value and does not apply this 
configuration to the interface.

  Upstream has discussed this issue here:

  https://github.com/systemd/systemd/pull/1533

  But it's been closed in favor of only setting via RA.

  However, we know of multiple use-case which are currently supported in
  ifdupdown where we want to retain control over IPV6 MTU values outside
  of PMTU Discovery configurations.

  
  Some context from those discussions

  
  >> Client systems that route their ipv6 packets to a 6in4 router also
  >> have to have their ipv6 mtu lowered.  They could lower their link mtu,
  >> so their ipv6 packets are small enough, but that reduces performance
  >> of their ipv4 network.

  Yes.  Anything that creates a PMTUD black hole can result in
  situations where the higher header overhead of IPv6 will cause IPv4 to
  pass but IPv6 traffic to be dropped.

  One example here is egress from an ipsec tunnel wherein the next
  hop MTU is too low for IPv6 datagrams to pass.  Another is VM ->
  whatever -> host bridge -> tunnel ingress.  If the datagram cannot enter
  the tunnel due to size, it is dropped, and an ICMP response uses the
  tunnel address as a source, which may not be routable back to the
  origin.  This one is an issue with IPv4 as well, and is one case where
  manually setting the IPv6 MTU lower than the (also manually set) device
  MTU is of benefit.

  In essence, any of these sort of cases that require an explicit
  setting of the device MTU will likely require a setting of the IPv6 mtu
  as well to account for its larger header overhead.

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

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

[Touch-packages] [Bug 1778547] [NEW] Broken system lock counting

[Julian Andres Klode]

Public bug reported:

[Impact]
System lock unrefing is broken, off-by-one error. Locking twice opens a second 
fd for the lock file, and the old fd gets lost and remains open for the 
remaining duration of the program

[Test case]
TODO

[Regression potential]
TODO

** Affects: apt (Ubuntu)
 Importance: Undecided
 Status: Fix Committed

** Affects: apt (Ubuntu Xenial)
 Importance: Undecided
 Status: Confirmed

** Affects: apt (Ubuntu Artful)
 Importance: Undecided
 Status: Confirmed

** Affects: apt (Ubuntu Bionic)
 Importance: Undecided
 Status: Triaged

** Changed in: apt (Ubuntu)
   Status: New => Fix Committed

** Also affects: apt (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: apt (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: apt (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: apt (Ubuntu Bionic)
   Status: New => Triaged

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

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

** Description changed:

- System lock unrefing is broken, off-by-one error.
+ [Impact]
+ System lock unrefing is broken, off-by-one error. Locking twice opens a 
second fd for the lock file, and the old fd gets lost and remains open for the 
remaining duration of the program
+ 
+ [Test case]
+ TODO
+ 
+ [Regression potential]
+ TODO

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

Title:
  Broken system lock counting

Status in apt package in Ubuntu:
  Fix Committed
Status in apt source package in Xenial:
  Confirmed
Status in apt source package in Artful:
  Confirmed
Status in apt source package in Bionic:
  Triaged

Bug description:
  [Impact]
  System lock unrefing is broken, off-by-one error. Locking twice opens a 
second fd for the lock file, and the old fd gets lost and remains open for the 
remaining duration of the program

  [Test case]
  TODO

  [Regression potential]
  TODO

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

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

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

[Jonathan]

Installed ubuntu 17.10 and so far no crashes (almost a week).  Really
wish someone would help determine whats going wrong in 18.04.

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

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

Status in systemd package in Ubuntu:
  Confirmed

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

  ---

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

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 235-3ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Fri Jan 26 13:45:06 2018
  ExecutablePath: /lib/systemd/systemd-logind
  InstallationDate: Installed on 2018-01-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180126)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. Z370 HD3
  ProcCmdline: /lib/systemd/systemd-logind
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __libc_connect (fd=39, addr=addr@entry=..., len=len@entry=16) at 
../sysdeps/unix/sysv/linux/connect.c:26
   __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, 
prog=prog@entry=10, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27301efc, 
sendsz=sendsz@entry=400, recvsz=recvsz@entry=400) at clnt_tcp.c:153
   __GI___libc_rpc_getport (tottimeout_sec=60, timeout_sec=5, protocol=6, 
version=2, program=17, address=0x7ffc27302060) at pm_getport.c:106
   __GI_pmap_getport (address=address@entry=0x7ffc27302060, 
program=program@entry=17, version=version@entry=2, 
protocol=protocol@entry=6) at pm_getport.c:154
   __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, 
prog=prog@entry=17, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27302050, 
sendsz=sendsz@entry=0, recvsz=recvsz@entry=0) at clnt_tcp.c:136
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  Title: systemd-logind crashed with SIGABRT in __libc_connect()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: Software adm bin daemon lp mail nuucp root scswebadmin sys 
sysdesign tty uucp
  dmi.bios.date: 09/22/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: Z370 HD3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd09/22/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z370 HD3
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

[Treviño]

** Description changed:

  [ Impact ]
  
  GNOME shell and other 3D programs run using software rendering after
  unity removal.
  
  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.
  
- [ Test case ]
+ [ Test case - FOR WHO UPGRADES TO BIONIC/ARTFUL ]
  
  · Install xenial
+ · Upgrade (nux-tools) and ensure that unity is still properly running after
+   a logout/login cycle.
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)
  
  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.
  
  · If running Unity session instead, ensure that
-   printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
-   in an environment with no 3d support (VMs are easy tests)
+   printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
+   in an environment with no 3d support (VMs are easy tests)
+ 
+ [ Test case - FOR WHO HAS ALREADY UPGRADED TO BIONIC/ARTFUL AND REMOVED
+ UNITY ]
+ 
+  · remove nux-tools from artful/bionic-release (pre-sru), upgrade,
+reinstall nux-tools (no prompt)
+  · remove nux-tools from bionic-proposed/updates (sru), upgrade, reinstall
+nux-tools (nothing should be prompted)
+  · modify config file, remove nux-tools, upgrade, reinstall nux-tools (should 
prompt)
+  · install nux-tools, upgrade, no prompt
+ 
+ You end up with either no /etc/X11/Xsession.d/50_check_unity_support,
+ its new contents or you are asked what to do if you've changed it
+ before. Never the old content.
  
  [ Regression Potential ]
  
  Unity desktops with no 3d support could not start anymore.
  
  ===
  
  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).
  
  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.
  
  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.
  
  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).
  
  mesa-utils and mesa-utils-extra are both installed.
  
  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?
  
  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.
  
  I have attached the log of 'journalctl -b0'
  
  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

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

Title:
  leftover conffile forces GNOME is software rendering

Status in nux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  In Progress
Status in nux source package in Xenial:
  Fix Committed
Status in xorg source package in Xenial:
  Confirmed
Status in nux source package in Artful:
  Fix Committed
Status in xorg source package in Artful:
  Confirmed
Status in nux source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  In Progress

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case - FOR WHO UPGRADES TO BIONIC/ARTFUL ]

  · Install xenial
  · Upgrade (nux-tools) and ensure that unity is still properly running after
a logout/login cycle.
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv 

[Touch-packages] [Bug 1764628] Re: incorrect hypervisor and virtualization type reported in compat mode guest

[Manoj Iyer]

** Changed in: util-linux (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Canonical Foundations Team (canonical-foundations)

** Changed in: util-linux (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  incorrect hypervisor and virtualization type reported in compat mode
  guest

Status in The Ubuntu-power-systems project:
  Incomplete
Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  ---uname output---
  Linux guest 4.15.0-13-generic #14~16.04.1-Ubuntu SMP Sat Mar 17 03:03:53 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = boston-LC 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Incorrect hypervisor and virtualization type reported in ubuntu 16.04.04 
guest running in P8compat mode on P9 boston-LC:

  root@guest:/tmp# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):2
  On-line CPU(s) list:   0,1
  Thread(s) per core:2
  Core(s) per socket:1
  Socket(s): 1
  NUMA node(s):  1
  Model: 2.2 (pvr 004e 1202)
  Model name:POWER8 (architected), altivec supported
  >> Hypervisor vendor: horizontal
  >> Virtualization type:   full
  L1d cache: 32K
  L1i cache: 32K
  NUMA node0 CPU(s): 0,1


   
  Stack trace output:
   no
   
  Oops output:
   no
   

  
  We test what is coming along with distro. If you are not able to see issue 
with : https://launchpad.net/ubuntu/+source/util-linux/2.27.1-6ubuntu3.5 .. can 
we get this included in 16.04.x train ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1764628/+subscriptions

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

[Touch-packages] [Bug 984390] Re: $PATH is taken from login.defs not /etc/environment

[Michael Vogt]

Fwiw, I looked at the code of "su.c" from util-linux (because
debian/ubuntu may switch to it, see https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=833256) and it looks like the bug is not present
there. The su-common.c:modify_environment() code will first
setenv_path() from login.defs and then do the supam_export_environment()
which will override the existing PATH if /etc/environment also defines
it.

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

Title:
  $PATH is taken from login.defs not /etc/environment

Status in shadow package in Ubuntu:
  Triaged
Status in shadow source package in Precise:
  Triaged

Bug description:
  $PATH isn't sourced from /etc/environment, instead the version in
  /etc/login.defs is used.  (The example below comes from a precise install.)

  | james@panlong:~$ echo $PATH
  | /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
  | james@panlong:~$ sudo su - buildd
  | buildd@panlong:~$ echo $PATH
  | /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
  | buildd@panlong:~$ cat /etc/environment 
  | 
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"
  | buildd@panlong:~$ grep PATH /etc/login.defs 
  | # Three items must be defined:  MAIL_DIR, ENV_SUPATH, and ENV_PATH.
  | # *REQUIRED*  The default PATH settings, for superuser and normal users.
  | ENV_SUPATH  
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  | ENV_PATH
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
  | #CRACKLIB_DICTPATH
  | buildd@panlong:~$ sudo sed -i -e "s#^ENV_PATH.*#ENV_PATH
PATH=/wtf:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games#" 
/etc/login.defs  
  | buildd@panlong:~$ logout
  | james@panlong:~$ sudo su - buildd
  | buildd@panlong:~$ echo $PATH
  | /wtf:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
  | buildd@panlong:~$

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

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

[Touch-packages] [Bug 984390] Re: $PATH is taken from login.defs not /etc/environment

[Michael Vogt]

I pushed a slightly modified version of this to https://github.com
/shadow-maint/shadow/pull/119

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

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

Title:
  $PATH is taken from login.defs not /etc/environment

Status in shadow package in Ubuntu:
  Triaged
Status in shadow source package in Precise:
  Triaged

Bug description:
  $PATH isn't sourced from /etc/environment, instead the version in
  /etc/login.defs is used.  (The example below comes from a precise install.)

  | james@panlong:~$ echo $PATH
  | /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
  | james@panlong:~$ sudo su - buildd
  | buildd@panlong:~$ echo $PATH
  | /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
  | buildd@panlong:~$ cat /etc/environment 
  | 
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"
  | buildd@panlong:~$ grep PATH /etc/login.defs 
  | # Three items must be defined:  MAIL_DIR, ENV_SUPATH, and ENV_PATH.
  | # *REQUIRED*  The default PATH settings, for superuser and normal users.
  | ENV_SUPATH  
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  | ENV_PATH
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
  | #CRACKLIB_DICTPATH
  | buildd@panlong:~$ sudo sed -i -e "s#^ENV_PATH.*#ENV_PATH
PATH=/wtf:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games#" 
/etc/login.defs  
  | buildd@panlong:~$ logout
  | james@panlong:~$ sudo su - buildd
  | buildd@panlong:~$ echo $PATH
  | /wtf:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
  | buildd@panlong:~$

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

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

[Touch-packages] [Bug 1093365] Re: apport doesn't send crash reports to Launchpad for stable releases like some people expect

[Brian Murray]

** Summary changed:

- apport annoyingly and silently refuses to upload a crash report
+ apport doesn't send crash reports to Launchpad for stable releases like some 
people expect

** Changed in: apport (Ubuntu)
   Importance: Undecided => Low

** Changed in: apport (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  apport doesn't send crash reports to Launchpad for stable releases
  like some people expect

Status in apport package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 12.10 amd64
  apport - 2.6.1-0ubuntu9

  gwibber and unity-gwibber-daemon have been crashing (segfault) over
  the past few days. When apport-gtk fires up, I see the error and click
  continue and then nothing happens. So next I run it from the command-
  line, same behavior and no output and an exit code of 0. I try again
  with apport-cli, same behavior. So next I spend 10 minutes with pdb to
  find out why you're refusing to upload my crash. A normal user will
  not bother with this.

  I traced down the refusal to upload to the accepts() function in the
  CrashDatabase class inside the file /usr/lib/python3/dist-
  packages/apport/crashdb.py.  The problem type is Crash and
  self.options will only upload Bug and Package types:

  (Pdb) p self.options
  {'problem_types': ['Bug', 'Package'], 'bug_pattern_url': 
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml', 
'escalated_tag': 'bugpattern-written', 'dupdb_url': 
'http://people.canonical.com/~ubuntu-archive/apport-duplicates', 
'escalation_tag': 'bugpattern-needed', 'impl': 'launchpad', 'distro': 'ubuntu'}
  (Pdb) p report.get('ProblemType')
  'Crash'

  With that info in hand, I modified /etc/apport/crashdb.conf to add
  'Crash' as a supported type and now I can upload the crash report.

  I claim that if you're going to refuse to upload my crash report, you
  owe me, the user, an exit code or error message that explains why, any
  other behavior is not user friendly. In fact why even pop-up apport-
  gtk at all with a continue button?

  In addition, I don't understand why you're setting the upload and
  uploaded file flags in this scenario, that may also be incorrect since
  you never uploaded anything:

  -rw-r- 1 mfisch   whoopsie 2113776 Dec 23 16:31 
/var/crash/_usr_bin_gwibber.1001.crash
  -rw-rw-r-- 1 mfisch   whoopsie   0 Dec 23 17:10 
/var/crash/_usr_bin_gwibber.1001.upload
  -rw--- 1 whoopsie whoopsie   0 Dec 23 17:10 
/var/crash/_usr_bin_gwibber.1001.uploaded

  I am attaching a crash report for twistd that it refuses to upload and
  hopefully that can be useful for testing.

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

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

[Touch-packages] [Bug 1778512] Re: PCI/internal sound card not detected. System Sound settings shows dummy output

[Roshni Pande]

** Description changed:

  aplay -l gives out aplay: device_list:268: no soundcards found...
  System settings says Dummy output
  
  cat /proc/asound/card0/codec* | grep Codec
  gives out:
  cat: '/proc/asound/card0/codec*': No such file or directory
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Mon Jun 25 17:53:06 2018
  InstallationDate: Installed on 2017-02-09 (501 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 036R0F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd11/18/2016:svnDellInc.:pnInspiron7560:pvr:rvnDellInc.:rn036R0F:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Inspiron 7560
  dmi.sys.vendor: Dell Inc.
+ 
+ !!
+ !!ALSA Information Script v 0.4.64
+ !!
+ 
+ !!Script ran on: Mon Jun 25 12:51:47 UTC 2018
+ 
+ 
+ !!Linux Distribution
+ !!--
+ 
+ Ubuntu 16.04.4 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu
+ 16.04.4 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu
+ 16.04.4 LTS" HOME_URL="http://www.ubuntu.com/;
+ SUPPORT_URL="http://help.ubuntu.com/;
+ BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
+ UBUNTU_CODENAME=xenial
+ 
+ 
+ !!DMI Information
+ !!---
+ 
+ Manufacturer:  Dell Inc.
+ Product Name:  Inspiron 7560
+ Product Version:   
+ Firmware Version:  1.0.7
+ Board Vendor:  Dell Inc.
+ Board Name:036R0F
+ 
+ 
+ !!ACPI Device Status Information
+ !!---
+ 
+ /sys/bus/acpi/devices/ACPI0003:00/status   15
+ /sys/bus/acpi/devices/ACPI000C:00/status   15
+ /sys/bus/acpi/devices/DELL0782:00/status   15
+ /sys/bus/acpi/devices/DELLABCE:00/status   15
+ /sys/bus/acpi/devices/DLLK0782:00/status   15
+ /sys/bus/acpi/devices/INT33A1:00/status15
+ /sys/bus/acpi/devices/INT33D0:00/status15
+ /sys/bus/acpi/devices/INT3400:00/status15
+ /sys/bus/acpi/devices/INT3402:00/status15
+ /sys/bus/acpi/devices/INT3403:00/status15
+ /sys/bus/acpi/devices/INT3403:01/status15
+ /sys/bus/acpi/devices/INT340E:00/status15
+ /sys/bus/acpi/devices/INT344B:00/status15
+ /sys/bus/acpi/devices/INT3F0D:00/status15
+ /sys/bus/acpi/devices/LNXPOWER:00/status   1
+ /sys/bus/acpi/devices/LNXPOWER:01/status   1
+ /sys/bus/acpi/devices/LNXPOWER:02/status   1
+ /sys/bus/acpi/devices/LNXPOWER:03/status   1
+ /sys/bus/acpi/devices/LNXPOWER:04/status   1
+ /sys/bus/acpi/devices/LNXPOWER:05/status   1
+ /sys/bus/acpi/devices/LNXPOWER:06/status   1
+ /sys/bus/acpi/devices/LNXPOWER:07/status   1
+ /sys/bus/acpi/devices/LNXPOWER:08/status   1
+ /sys/bus/acpi/devices/LNXPOWER:09/status   1
+ /sys/bus/acpi/devices/LNXPOWER:0a/status   1
+ /sys/bus/acpi/devices/LNXPOWER:0b/status   1
+ /sys/bus/acpi/devices/LNXPOWER:0c/status   1
+ /sys/bus/acpi/devices/LNXPOWER:0d/status   1
+ /sys/bus/acpi/devices/LNXPOWER:0e/status   1
+ /sys/bus/acpi/devices/LNXPOWER:0f/status   1
+ /sys/bus/acpi/devices/LNXPOWER:10/status   1
+ /sys/bus/acpi/devices/LNXPOWER:11/status   1
+ /sys/bus/acpi/devices/LNXPOWER:12/status   1
+ /sys/bus/acpi/devices/LNXPOWER:13/status   1
+ /sys/bus/acpi/devices/LNXVIDEO:01/status   15
+ /sys/bus/acpi/devices/MSFT0101:00/status   15
+ /sys/bus/acpi/devices/PNP0103:00/status15
+ /sys/bus/acpi/devices/PNP0C02:03/status3
+ /sys/bus/acpi/devices/PNP0C02:05/status3
+ /sys/bus/acpi/devices/PNP0C09:00/status15
+ /sys/bus/acpi/devices/PNP0C0A:00/status31
+ /sys/bus/acpi/devices/PNP0C0C:00/status15
+ /sys/bus/acpi/devices/PNP0C0F:00/status9
+ /sys/bus/acpi/devices/PNP0C0F:01/status9
+ /sys/bus/acpi/devices/PNP0C0F:02/status9
+ /sys/bus/acpi/devices/PNP0C0F:03/status9
+ /sys/bus/acpi/devices/PNP0C0F:04/status9
+ /sys/bus/acpi/devices/PNP0C0F:05/status9
+ /sys/bus/acpi/devices/PNP0C0F:06/status9
+ /sys/bus/acpi/devices/PNP0C0F:07/status9
+ /sys/bus/acpi/devices/device:09/status 15
+ /sys/bus/acpi/devices/device:59/status 15
+ /sys/bus/acpi/devices/device:6f/status 11
+ 
+ 
+ !!Kernel Information
+ 

[Touch-packages] [Bug 1778512] Re: PCI/internal sound card not detected. sometimes after running many terminal command lines it gets fixed temporarily but once the laptop goes into sleep mode, then th

[Roshni Pande]

"sudo alsa force-reload" command also doesn't help

** Attachment added: "sound_problem.png"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1778512/+attachment/5156390/+files/sound_problem.png

** Summary changed:

- PCI/internal sound card not detected.  sometimes after running many terminal 
command  lines  it gets fixed temporarily but once the laptop goes into sleep 
mode, then the sound doesnt work again. right now even trying all the command 
lines that I tried earlier also do not work
+ PCI/internal sound card not detected.

** Summary changed:

- PCI/internal sound card not detected.
+ PCI/internal sound card not detected. System Sound settings shows Dummy output

** Summary changed:

- PCI/internal sound card not detected. System Sound settings shows Dummy output
+ PCI/internal sound card not detected. System Sound settings shows dummy output

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

Title:
  PCI/internal sound card not detected. System Sound settings shows
  dummy output

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  aplay -l gives out aplay: device_list:268: no soundcards found...
  System settings says Dummy output

  cat /proc/asound/card0/codec* | grep Codec
  gives out:
  cat: '/proc/asound/card0/codec*': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Mon Jun 25 17:53:06 2018
  InstallationDate: Installed on 2017-02-09 (501 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 036R0F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd11/18/2016:svnDellInc.:pnInspiron7560:pvr:rvnDellInc.:rn036R0F:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Inspiron 7560
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1778512] Re: PCI/internal sound card not detected. sometimes after running many terminal command lines it gets fixed temporarily but once the laptop goes into sleep mode, then th

[Roshni Pande]

"sudo alsa force-reload" command also doesn't help

** Attachment added: "sound_problem.png"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1778512/+attachment/5156389/+files/sound_problem.png

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

Title:
  PCI/internal sound card not detected. System Sound settings shows
  dummy output

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  aplay -l gives out aplay: device_list:268: no soundcards found...
  System settings says Dummy output

  cat /proc/asound/card0/codec* | grep Codec
  gives out:
  cat: '/proc/asound/card0/codec*': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Mon Jun 25 17:53:06 2018
  InstallationDate: Installed on 2017-02-09 (501 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 036R0F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd11/18/2016:svnDellInc.:pnInspiron7560:pvr:rvnDellInc.:rn036R0F:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Inspiron 7560
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1778512] [NEW] PCI/internal sound card not detected. System Sound settings shows dummy output

[Roshni Pande]

Public bug reported:

aplay -l gives out aplay: device_list:268: no soundcards found...
System settings says Dummy output

cat /proc/asound/card0/codec* | grep Codec
gives out:
cat: '/proc/asound/card0/codec*': No such file or directory

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
Uname: Linux 4.4.0-128-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
Date: Mon Jun 25 17:53:06 2018
InstallationDate: Installed on 2017-02-09 (501 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/18/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.7
dmi.board.name: 036R0F
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd11/18/2016:svnDellInc.:pnInspiron7560:pvr:rvnDellInc.:rn036R0F:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.name: Inspiron 7560
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug xenial

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

Title:
  PCI/internal sound card not detected. System Sound settings shows
  dummy output

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  aplay -l gives out aplay: device_list:268: no soundcards found...
  System settings says Dummy output

  cat /proc/asound/card0/codec* | grep Codec
  gives out:
  cat: '/proc/asound/card0/codec*': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Mon Jun 25 17:53:06 2018
  InstallationDate: Installed on 2017-02-09 (501 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 036R0F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd11/18/2016:svnDellInc.:pnInspiron7560:pvr:rvnDellInc.:rn036R0F:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Inspiron 7560
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1773992] Re: apt-key adv should gpgconf --kill all the things after execution

[Julian Andres Klode]

** Also affects: apt (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Changed in: apt (Ubuntu Bionic)
   Status: In Progress => Triaged

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

Title:
  apt-key adv should gpgconf --kill all the things after execution

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Triaged

Bug description:
  apt-key adv should gpgconf --kill all the things after execution

  to ensure that e.g. dirmngr processes are not left hanging around

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

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

[Touch-packages] [Bug 1778506] [NEW] Have to restart the bluetooth after sleeping to connect to headphones

[marvin]

Public bug reported:

Linux Ubuntu 18-04 X1-18 4.15.0-23-generic

After suspend my bose bluetooth headphones keep connecting /
disconnecting / connecting ... until failure.

After 
marvin@X1-18:~$ sudo service bluetooth restart

everything works fine again.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluez 5.48-0ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 25 14:06:50 2018
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 20FRS2M600
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=fb013004-2044-405c-946d-4da9f7e757e5 ro quiet splash
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/23/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: N1FET41W (1.15 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FRS2M600
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Yoga 1st
dmi.product.name: 20FRS2M600
dmi.product.version: ThinkPad X1 Yoga 1st
dmi.sys.vendor: LENOVO
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: E4:A7:A0:36:99:9D  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:358790 acl:11101 sco:0 events:25202 errors:0
TX bytes:14298744 acl:22439 sco:0 commands:2586 errors:0

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


** Tags: amd64 apport-bug bionic

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

Title:
  Have to restart the bluetooth after sleeping to connect to headphones

Status in bluez package in Ubuntu:
  New

Bug description:
  Linux Ubuntu 18-04 X1-18 4.15.0-23-generic

  After suspend my bose bluetooth headphones keep connecting /
  disconnecting / connecting ... until failure.

  After 
  marvin@X1-18:~$ sudo service bluetooth restart

  everything works fine again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 25 14:06:50 2018
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20FRS2M600
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=fb013004-2044-405c-946d-4da9f7e757e5 ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/23/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET41W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FRS2M600
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 1st
  dmi.product.name: 20FRS2M600
  dmi.product.version: ThinkPad X1 Yoga 1st
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:A7:A0:36:99:9D  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:358790 acl:11101 sco:0 events:25202 errors:0
TX bytes:14298744 acl:22439 sco:0 commands:2586 errors:0

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

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

[Touch-packages] [Bug 1674605] Re: resolving short local hostnames doesn't work, fqdn are fine

[Danilo Bargen]

I assume I'm affected by the same issue.

I also use my router (Mikrotik) to set up short aliases for hosts.

This works generally:

$ dig +short anton @10.0.0.1
10.0.0.12

In my /etc/resolv.conf, systemd-resolved is enabled:

$ tail -n 1 /etc/resolv.conf 
nameserver 127.0.0.53

When running "systemd-resolve --status", I can see that the DNS server
is correctly set up for the interface via DHCP:

  Link 4 (wlx0013ef8b0189)
Current Scopes: DNS
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: no
  DNSSEC supported: no
   DNS Servers: 10.0.0.1

However, it is not being used to resolve the shortnames:

$ dig +short anton @10.0.0.1
10.0.0.12
$ dig +short anton @127.0.0.53

$ dig +short anton


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

Title:
  resolving short local hostnames doesn't work, fqdn are fine

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hi, I have a local "dummy" DNS server on my router which registers
  DHCP clients with the hostnames that they have. But resolving these
  hostnames doesn't work on zesty unless fqdn is used, otherwise there's
  a timeout that says:

  root@zesty:# host deckard
  ;; connection timed out; no servers could be reached

  but

  root@zesty:/mnt# host deckard.tyrell
  deckard.tyrell has address 192.168.1.239

  Yesterday I had a resolv.conf with "search tyrell" and shortnames
  worked then, but today it's gone again. Besides right after a reboot
  it fails like this:

  u@zesty:~$ host deckard
  Host deckard not found: 2(SERVFAIL)

  and after restarting systemd-resolved I get the timeout.

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

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

[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.

[Daniel Mehrmann]

Thanks! Now tested with versuion 3.2 and the bug is still there. :-(

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

Title:
  Long time booting : Failed to connect to lvmetad. Falling back to
  device scanning.

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Bionic:
  Fix Committed

Bug description:
  [SRU Justification]
  A regression in initramfs-tools causes it to autogenerate config in the 
initramfs saying to resume from any available swap devices, but references the 
swap device by UUID, which is not a canonical form for referring to LVM volumes 
(because of snapshotting, they are not unique).  Ubiquity also generates a file 
in /etc at install time which references the swap partition in the same way.  
Since the lvm2 initramfs hooks also only activate precisely those LVs that are 
detected as needed at boot, this adds an inappropriate 30-second boot delay to 
any system with swap on LVM, which includes any desktop system that was 
configured with LVM (but not full-disk encryption) at install time.

  [Test case]
  1. Install using the "Use LVM" option in the desktop installer.
  4. Reboot.
  5. Verify that dmesg shows a 30-second delay before mounting the root 
filesystem.
  6. Install initramfs-tools from bionic-proposed.
  7. Reboot.
  8. Verify that dmesg no longer shows a 30-second delay before mounting the 
root filesystem.
  9. Install using the bionic daily image that contains the ubiquity from 
bionic-proposed.
  10. Reboot.
  11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that 
there is no delay before mounting the root filesystem.

  [Regression potential]
  This makes changes to shell scripts, and shell is a perilous language. An 
unnoticed bug could cause all initramfs generation, and thus all kernel 
installation, to fail for some users. A regression could also cause a user to 
lose hiberation support that they currently have.

  [Original description]
  After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu 
installation", the
  system is very slow to reboot.

  It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to 
device scanning.",
  then waits 32 seconds, then continues as it should.

  I think this is a ubiquity bug, since the d-i based installer is not affected.
   - ubuntu-18.04-desktop-amd64.iso 
(a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected
   - xubuntu-18.04-desktop-amd64.iso 
(7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected
   - ubuntu-18.04-server-amd64.iso 
(a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not 
affected

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

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

[Touch-packages] [Bug 1171047] Re: update-manager times out checking for updates

[Julian Andres Klode]

This should be fixed in apt since some time as well, so closing.

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

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

Title:
  update-manager times out checking for updates

Status in Launchpad itself:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released

Bug description:
  I've bought a number of humble bundle games that were activated
  through the software centre, so I have quite a lot of sources in apt.
  The server that they come from is so terribly slow to fetch from that
  it causes the update manager to time out when checking for updates.

  See the attached file for the timestamped output from apt-get update,
  and you'll see that while it's generally slow (multiple seconds
  between requests once the normal speed ones are dealt with) there is
  one that takes about 12 minutes to respond at all (13:21:48 to
  13:34:12)

  This means that I can't update through the ubuntu update manager, nor
  does it tell me when updates are available.

  My internet is quite good, the first lot of sources complete in ~10
  seconds, the problem seems to be at the private-ppa.launchpad.net
  server end. However, this wouldn't be such an issue if the update
  manager didn't time out (but really the solution is to fix the apt
  servers.)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: update-manager 1:0.185
  ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
  Uname: Linux 3.8.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Aptdaemon:
   
  Architecture: amd64
  Date: Sun Apr 21 13:39:54 2013
  GsettingsChanges:
   b'com.ubuntu.update-manager' b'first-run' b'false'
   b'com.ubuntu.update-manager' b'launch-time' b'1366195146'
   b'com.ubuntu.update-manager' b'show-details' b'true'
   b'com.ubuntu.update-manager' b'window-height' b'470'
   b'com.ubuntu.update-manager' b'window-width' b'583'
  InstallationDate: Installed on 2011-04-26 (725 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: update-manager
  UpgradeStatus: Upgraded to raring on 2013-04-13 (7 days ago)

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

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

[Touch-packages] [Bug 1373598] Re: apt-get update fails, hash sum mismatches with de.archive.ubuntu.com

[Julian Andres Klode]

Closing this, as that's been fixed with by-hash repository support in
apt.

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

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

Title:
  apt-get update fails, hash sum mismatches with de.archive.ubuntu.com

Status in apt package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  1. Release: 
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  2.  not a package. The whole distro is broken.

  3. I always expect apt-get update to work, at least with Ubuntu's own
  repositories.

  4. "apt-get update" failed, and later "apt-get dist upgrade"

  
  It started with this when doing a normal "apt-get update"

  W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty-
  updates/main/source/Sources  Hash Sum mismatch

  W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty-
  updates/main/binary-amd64/Packages  Hash Sum mismatch

  W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty-
  updates/universe/binary-i386/Packages  Hash Sum mismatch

  E: Some index files failed to download. They have been ignored, or old
  ones used instead.

  
  When doing a dist-upgrade, I then got this:
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-3.13.0-36-generic with 1.
  run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
  Failed to process /etc/kernel/postinst.d at 
/var/lib/dpkg/info/linux-image-extra-3.13.0-36-generic.postinst line 1025.
  No apport report written because the error message indicates its a followup 
error from a previous failure.

dpkg: error processing package 
linux-image-extra-3.13.0-36-generic (--configure):
   subprocess installed post-installation script returned error exit status 2
  dpkg: dependency problems prevent configuration of linux-image-generic:
   linux-image-generic depends on linux-image-extra-3.13.0-36-generic; however:
Package linux-image-extra-3.13.0-36-generic is not configured yet.

  dpkg: error processing package linux-image-generic (--configure):
   dependency problems - leaving unconfigured
  Setting up linux-headers-3.13.0-36 (3.13.0-36.63) ...
  Setting up linux-headers-3.13.0-36-generic (3.13.0-36.63) ...
  Examining /etc/kernel/header_postinst.d.
  run-parts: executing /etc/kernel/header_postinst.d/dkms 3.13.0-36-generic 
/boot/vmlinuz-3.13.0-36-generic
  Setting up linux-headers-generic (3.13.0.36.43) ...
  No apport report written because the error message indicates its a followup 
error from a previous failure.

dpkg: dependency problems prevent configuration of 
linux-generic:
   linux-generic depends on linux-image-generic (= 3.13.0.36.43); however:
Package linux-image-generic is not configured yet.

  dpkg: error processing package linux-generic (--configure):
   dependency problems - leaving unconfigured

  
  And later this at the end:
  Processing triggers for libc-bin (2.19-0ubuntu6.3) ...
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-release-upgrader-core 1:0.220.5
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Wed Sep 24 21:57:55 2014
  InstallationDate: Installed on 2013-05-09 (503 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to trusty on 2014-05-04 (142 days ago)
  VarLogDistupgradeTermlog:

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

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

[Touch-packages] [Bug 1723761] Re: unattended-upgrade hangs on shutdown when network is required for updates

[Julian Andres Klode]

** Changed in: apt (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  unattended-upgrade hangs on shutdown when network is required for
  updates

Status in apt package in Ubuntu:
  In Progress
Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Recently an update for flashplugin-installer on xenial was available
  in the ubuntu repositories.

  During the installation of this package a blob is downloaded from
  Adobe servers, which requires network connectivity/internet access.

  Because the network interface(s) have already stopped when this
  package is installed, the server cannot be reached, thus blocking the
  shutdown process until a timeout kills the unattended-upgrades
  process.

  On my machines the shutdown takes about 30 minutes in this case. The
  systemd configuration is standard here, except for a few additional
  services.

  A possible fix could be adding After=network-online.target
  NetworkManager-wait-online.service to After= in the systemd unit file.

  As a workaround I pinned the flashplugin-installer to -1:
  #echo >/etc/apt/preferences.d/forbid_flashplugin "\
  Package: flashplugin-installer
  Pin: release *
  Pin-Priority: -1";

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

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

[Touch-packages] [Bug 1768797] Re: LivePatch in Software & Updates shows that LP is not enabled when the U1 account has expired in g-o-a

[Andrea Azzarone]

mtp replied by email:

That is a strange situation. But since there’s no reason to stop you
from turning Livepatch off, the checkbox should still be enabled. The
only thing we can’t do, that we normally would, is tell you what account
you’re signed in as. Instead we can just reassure you that “Livepatch is
active.”

** Branch linked: lp:~azzar1/software-properties/fix-1768797

** Changed in: gnome-online-accounts (Ubuntu)
   Status: Incomplete => In Progress

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

Title:
  LivePatch in Software & Updates shows that LP is not enabled when the
  U1 account has expired in g-o-a

Status in gnome-online-accounts package in Ubuntu:
  In Progress

Bug description:
  I enabled LivePatch via gnome-initial-setup and added my U1 account to
  g-o-a.

  My U1 account gets marked as expired quite often.  When it's expired
  the LP entry in Software & Updates is not ticked to show that LP is
  running.  When my u1 account is re-authenticated then everything shows
  correctly.

  This could make it seem that LivePatch does not run if your account
  expires, which is not the case.

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

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

[Touch-packages] [Bug 1778497] [NEW] Add a remember option to whoopsie so that users can diminish crash interactions

[Didier Roche]

Public bug reported:

[ Impact ]
A lot of users are bother by the number of whoopsie dialog. We introduced on 
"G-C-C privacy option don't allow sending manual report" bug 
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1774597) a 
way for users to change from always reporting manually (prompting an UI) to 
auto reporting or never reporting, via a "Remember this in future".

This only impacts the apport gtk UI, still offering the underlying
capability to other UIs type without changing them.

This was a goal for 18.04, but due to a lack of time, we want to
introduce this in 18.04.1

[ Test Case ]
 * There are multiples dialog forms (a good 20 of them), but they are all 
covered by unit tests which have been updates. One use case would be:
 * Install the new version and trigger a crash
 * Check that the dialog has a "Remember this in future" option, check it, and 
click send.
 * Check in g-c-c UI, privacy option, that the crash reporting is now in auto 
mode, always send.
 * Revert in g-c-c to manual
 * Create another crash, check "Remember this…" and click don't send
 * Check in g-c-c UI that crash reporting is now disabled.

[ Regression potential ]
 * The impacted code is both UI and fileutils. It's covered by an extensive 
testsuite, and checking under KDE has also been done to not trigger a crash.

** Affects: apport (Ubuntu)
 Importance: High
 Assignee: Didier Roche (didrocks)
 Status: New

** Affects: apport (Ubuntu Bionic)
 Importance: High
 Assignee: Didier Roche (didrocks)
 Status: New

** Also affects: apport (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: apport (Ubuntu)
 Assignee: (unassigned) => Didier Roche (didrocks)

** Changed in: apport (Ubuntu Bionic)
 Assignee: (unassigned) => Didier Roche (didrocks)

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

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

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

Title:
  Add a remember option to whoopsie so that users can diminish crash
  interactions

Status in apport package in Ubuntu:
  New
Status in apport source package in Bionic:
  New

Bug description:
  [ Impact ]
  A lot of users are bother by the number of whoopsie dialog. We introduced on 
"G-C-C privacy option don't allow sending manual report" bug 
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1774597) a 
way for users to change from always reporting manually (prompting an UI) to 
auto reporting or never reporting, via a "Remember this in future".

  This only impacts the apport gtk UI, still offering the underlying
  capability to other UIs type without changing them.

  This was a goal for 18.04, but due to a lack of time, we want to
  introduce this in 18.04.1

  [ Test Case ]
   * There are multiples dialog forms (a good 20 of them), but they are all 
covered by unit tests which have been updates. One use case would be:
   * Install the new version and trigger a crash
   * Check that the dialog has a "Remember this in future" option, check it, 
and click send.
   * Check in g-c-c UI, privacy option, that the crash reporting is now in auto 
mode, always send.
   * Revert in g-c-c to manual
   * Create another crash, check "Remember this…" and click don't send
   * Check in g-c-c UI that crash reporting is now disabled.

  [ Regression potential ]
   * The impacted code is both UI and fileutils. It's covered by an extensive 
testsuite, and checking under KDE has also been done to not trigger a crash.

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

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

[Touch-packages] [Bug 710144] Re: Xsession: unable to launch "" X session --- "" not found; falling back to default session.

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.
Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: xorg (Ubuntu)
   Status: Triaged => 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/710144

Title:
  Xsession: unable to launch "" X session --- "" not found; falling back
  to default session.

Status in xorg package in Ubuntu:
  Incomplete
Status in xorg package in Debian:
  New

Bug description:
  Binary package hint: xorg

  I recently both got an upgrade for Xorg and went to KDE 4.6 (via the
  PPA), so I don't know who caused this message to appear. But now
  everytime I logon I get an xmessage telling me "Xsession: unable to
  launch "" X session --- "" not found; falling back to default
  session."

  This is from /etc/X11/Xsession.d/20x11-common_process-args but I don't
  know where the session name comes from. Anyway, I think an empty
  session name should be special cased with something like the following
  (untested) patch:

  --- 20x11-common_process-args.orig  2010-03-02 17:33:01.0 +0100
  +++ 20x11-common_process-args   2011-01-30 13:57:18.073443001 +0100
  @@ -40,7 +40,7 @@
 fi
   fi
   ;;
  -  default)
  +  default|"")
   # Default behavior was requested.
   ;;
 *)

  Apart from that it would be nice if that message gave me a hint on how
  to fix this.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: x11-common 1:7.5+6ubuntu3
  ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
  Uname: Linux 2.6.35-25-generic x86_64
  Architecture: amd64
  DRM.card0.HDMI_Type_A.1:
   status: connected
   enabled: enabled
   dpms: On
   modes: 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1280x960 
1152x864 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 
800x600 720x576 720x480 640x480 640x480 640x480 640x480 720x400
   edid-base64: 
AP///wAmzQxWuAkAACYUAQOANB14KmBBplZKnCUSUFS/7wBxT4FAgYCVAJUPswABAQEBAjqAGHE4LUBYLEUACSUhAAAe/QA4TB5TEQAKICAgICAg/ABQTDI0MDlIRAogICAg/wAxMTAwNU0wOTAyNDg4AaQCAx/xTAECAwQFEBESExQeHyMJBwGDAQAAZQMMABAAjArQiiDgLRAQPpYACSUhAAAYAR0AclHQHiBuKFUACSUhAAAejArQkCBAMSAMQFUACSUhAAAYTw==
  Date: Sun Jan 30 13:50:23 2011
  DkmsStatus:
   
  MachineType: Acer AL 5100 / VL410
  PackageArchitecture: all
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-25-generic root=/dev/mapper/lvm-sys 
ro rootfstype=ext4 iommu=noaperture quiet splash
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  dmi.bios.date: 04/14/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: R02-A1
  dmi.board.name: FRS690L
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrR02-A1:bd04/14/2008:svnAcer:pnAL5100/VL410:pvrR02-A1:rvnAcer:rnFRS690L:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: AL 5100 / VL410
  dmi.product.version: R02-A1
  dmi.sys.vendor: Acer
  system:
   distro: Ubuntu
   codename:   maverick
   architecture:   x86_64
   kernel: 2.6.35-25-generic

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

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

[Touch-packages] [Bug 1778178] Re: Upgrade to PulseAudio 12.0

[Daniel van Vugt]

** Tags added: upgrade-software-version

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

Title:
  Upgrade to PulseAudio 12.0

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Upgrade to PulseAudio 12.0

  https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/12.0/

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

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

[Touch-packages] [Bug 666441] Re: Upgraded to ubuntu 10.10 - screen flickers

[Daniel van Vugt]

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

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

Title:
  Upgraded to ubuntu 10.10 - screen flickers

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I was running fine on ubuntu 10.04 and decided to take the plunge and
  upgrade to ubuntu 10.10.

  Ever since I have upgraded, I am getting a screen flicker every 6-7
  seconds. This is MOST annoying.

  I have tried installing the AMD proprietary video driver and using the
  default driver.

  Both have the same problem:

  mike@ubuntu:~$ sudo lshw -C display
  [sudo] password for mike: 
*-display:0 
 description: VGA compatible controller
 product: R520 [Radeon X1800]
 vendor: ATI Technologies Inc
 physical id: 0
 bus info: pci@:01:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:46 memory:d000-dfff memory:e010-e010 
ioport:2000(size=256) memory:e012-e013
*-display:1 UNCLAIMED
 description: Display controller
 product: R520 [Radeon X1800] (Secondary)
 vendor: ATI Technologies Inc
 physical id: 0.1
 bus info: pci@:01:00.1
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress bus_master cap_list
 configuration: latency=0
 resources: memory:e011-e011
  mike@ubuntu:~$ 

  Can someone please help me?

  If not, is there a way to go back to 10.04 without doing a complete
  re-install?

  Thanks,
  Mike

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

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

[Touch-packages] [Bug 1778496] [NEW] resolution not incresing

[Jayesh]

Public bug reported:

resolution not incresing

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 25 16:09:50 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: bbswitch, 0.8, 4.15.0-23-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Elitegroup Computer Systems Xeon E3-1200 v2/3rd Gen Core 
processor Graphics Controller [1019:3149]
InstallationDate: Installed on 2018-06-08 (17 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Acer Veriton Series
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=5b575a7c-4097-49ef-865d-6dae0d73237b ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/18/2013
dmi.bios.vendor: Acer
dmi.bios.version: P21-A1
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61H2-M6
dmi.board.vendor: Acer
dmi.board.version: 2.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.chassis.version: 2.0
dmi.modalias: 
dmi:bvnAcer:bvrP21-A1:bd07/18/2013:svnAcer:pnVeritonSeries:pvrP21-A1:rvnAcer:rnH61H2-M6:rvr2.0:cvnAcer:ct3:cvr2.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Veriton Series
dmi.product.version: P21-A1
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
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

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


** Tags: amd64 apport-bug bionic 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/1778496

Title:
  resolution not incresing

Status in xorg package in Ubuntu:
  New

Bug description:
  resolution not incresing

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 25 16:09:50 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: bbswitch, 0.8, 4.15.0-23-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems Xeon E3-1200 v2/3rd Gen Core 
processor Graphics Controller [1019:3149]
  InstallationDate: Installed on 2018-06-08 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Acer Veriton Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=5b575a7c-4097-49ef-865d-6dae0d73237b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2013
  dmi.bios.vendor: Acer
  dmi.bios.version: P21-A1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61H2-M6
  dmi.board.vendor: Acer
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAcer:bvrP21-A1:bd07/18/2013:svnAcer:pnVeritonSeries:pvrP21-A1:rvnAcer:rnH61H2-M6:rvr2.0:cvnAcer:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Veriton Series
  dmi.product.version: P21-A1
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  

[Touch-packages] [Bug 806120] Re: ~/.xsession does not get run but Xsession(5) still says it does

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: xorg (Ubuntu)
   Status: Triaged => 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/806120

Title:
  ~/.xsession does not get run but Xsession(5) still says it does

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Xsession(5) still says that $HOME/.xsession can contain commands for
  invoking X clients. But in natty $HOME/.xsession does not get run.

  (/etc/X11/Xsession sources all the scripts in /etc/X11/Xsession.d/ and
  /etc/X11/Xsession.d/50x11-common_determine-startup only sources the
  user's .xsession if the STARTUP variable has not been set. But it has
  been set, to "gnome-session --session=ubuntu".)

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: xorg 1:7.6+4ubuntu3.1
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
  Uname: Linux 2.6.38-8-generic-pae i686
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,move,regex,mousepoll,place,gnomecompat,imgpng,animation,wall,resize,workarounds,wobbly,unitymtgrabhandles,session,expo,ezoom,staticswitcher,fade,scale,unityshell]
  CompositorRunning: compiz
  Date: Tue Jul  5 20:43:40 2011
  DistUpgraded: Log time: 2010-10-12 10:35:08.860007
  DistroCodename: natty
  DistroVariant: ubuntu
  DkmsStatus: virtualbox-ose, 4.0.4, 2.6.38-8-generic-pae, i686: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Lenovo T61 [17aa:20b5]
 Subsystem: Lenovo T61 [17aa:20b5]
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  MachineType: LENOVO 7673CTO
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_IE:en
   PATH=(custom, user)
   LANG=en_IE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic-pae 
root=UUID=07f57763-4d3a-4045-8f1a-e5224fa61703 ro mem=4096M quiet splash 
vt.handoff=7
  Renderer: Unknown
  SourcePackage: xorg
  UpgradeStatus: Upgraded to natty on 2011-03-24 (103 days ago)
  dmi.bios.date: 11/27/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7NETB9WW (2.19 )
  dmi.board.name: 7673CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7NETB9WW(2.19):bd11/27/2008:svnLENOVO:pn7673CTO:pvrThinkPadX61:rvnLENOVO:rn7673CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 7673CTO
  dmi.product.version: ThinkPad X61
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.4+bzr20110606-0ubuntu1~natty1
  version.libdrm2: libdrm2 2.4.23-1ubuntu6
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2
  version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110107+b795ca6e-0ubuntu7

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

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

[Touch-packages] [Bug 1085541] Re: Regression: Latest updates break X [HP dv6 laptop]

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

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

Title:
  Regression: Latest updates break X [HP dv6 laptop]

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Hey guys,

  I don't which update caused my Ubuntu not to show anything, not even
  the starting screen, all I get is a black screen, I can see that it's
  loading because I see my HDD light blinking and my WiFi light turn on,
  but nothing on the screen itself.

  It may be X or the drivers for the following Video cards (this is what
  my laptop has):

  AMD Radeon HD 7690M
  AMD Radeon HD 6620G

  I know the screen is fine because I just re-installed Windows to send
  this bug report.

  Thanks

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

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

[Touch-packages] [Bug 1046505] Re: 8086:0116 i915_hangcheck_hung

[Daniel van Vugt]

Closed due to no response. But also:

Thank you for reporting this bug to Ubuntu.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

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

Title:
  8086:0116 i915_hangcheck_hung

Status in X.Org X server:
  Invalid
Status in xorg package in Ubuntu:
  Invalid

Bug description:
  While I was surfing to a site (firefox www.hln.be) my system locked
  up.

  dmesg showed the following error:
  [ 9560.052783] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [ 9560.052788] [drm] capturing error event; look for more information in 
/debug/dri/0/i915_error_state

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xorg 1:7.7+1ubuntu3
  Uname: Linux 3.6.0-999-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.5.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,resize,move,gnomecompat,place,imgpng,session,compiztoolbox,vpswitch,grid,regex,mousepoll,snap,animation,wall,unitymtgrabhandles,workarounds,fade,expo,ezoom,scale,unityshell]
  CompositorRunning: compiz
  Date: Wed Sep  5 21:34:49 2012
  DistUpgraded: 2012-06-20 00:41:53,886 DEBUG enabling apt cron job
  DistroCodename: quantal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:050e]
   NVIDIA Corporation GF108 [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell Device [1028:050e]
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
  MachineType: Dell Inc. Dell System XPS L502X
  ProcEnviron:
   LANGUAGE=nl:en_AU:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=nl_BE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.0-999-generic 
root=UUID=af3a67b1-5cbf-48f1-b0b7-0848ae3017b4 ro quiet splash modeset=1 
pcie_aspm=force i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 
i915.lvds_downclock=1 vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to quantal on 2012-06-19 (77 days ago)
  dmi.bios.date: 02/20/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd02/20/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.8.0-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.38-0ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120821.c1114c61-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120821.c1114c61-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.99.99~git20120713.6ef1ad6a-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.3-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.1-4~ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1046505/+subscriptions

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

[Touch-packages] [Bug 1011207] Re: Xsession ERRFILE .xsession-errors should move to /tmp/ to enhance HDD power saving

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

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

Title:
  Xsession ERRFILE .xsession-errors should move to /tmp/ to enhance HDD
  power saving

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  /etc/X11/Xsession places ERRFILE into users home directory which
  conflicts with possible HDD power saving settings by causing
  occasional writes done by logging misbehaving apps/drivers. The
  Xsession has provisions for placing it into /tmp but that path is only
  taken if users home directory is unwritable. This slight oversight is
  easily fixed by relocating the default ERRFILE into /tmp.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: x11-common 1:7.6+12ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Sun Jun 10 19:05:57 2012
  InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  PackageArchitecture: all
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.X11.Xsession: [modified]
  mtime.conffile..etc.X11.Xsession: 2012-06-06T15:12:36.927296

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

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

[Touch-packages] [Bug 842424] Re: Don't remember keyboard layout settings

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


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

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

Title:
  Don't remember keyboard layout settings

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I want to have only this two keyboards layers:
  1. USA Alternative international
  2. Slovensko qwerty <-this is a default

  But, its here a bug, because on start i have:
  1. USA Alternative international
  2. Slovensko qwerty rozsirena spatna lomka <-this is a default
  The second I change to Slovensko qwerty, and old one i remove.

  All works fine, until every next start i have 3 keyboard layers:
  1. USA Alternative international
  2. Slovensko qwerty rozsirena spatna lomka <-this is a default
  3. Slovensko qwerty
  --- 
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  DistroRelease: Ubuntu 11.10
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  Package: xorg 1:7.6+7ubuntu7
  PackageArchitecture: i386
  ProcEnviron:
   PATH=(custom, no user)
   LANG=sk_SK.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Tags:  oneiric
  Uname: Linux 3.0.0-14-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Touch-packages] [Bug 1006156] Re: Mute button on USB headset steals and holds on to mouse focus

[Daniel van Vugt]

Closed due to lack of response.

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

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

Title:
  Mute button on USB headset steals and holds on to mouse focus

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  When I press the mute button on my USB headset (Plantronics .Audio 626
  DSP), it steals the "mouse focus" and holds onto it until I press the
  mute button again.

  Expected:

  - microphone is muted
  - nothing else happens

  Actual:

  - microphone is muted
  - mouse can still move but is unresponsive to clicks
  - pressing the keyboard doesn't do anything (except for Ctrl+Alt+F1 which 
does work and switch to virtual console)

  I'm not sure this is filed against the right package, please reassign
  if it's not. Also, I'm happy to provide more info, but I wasn't sure
  what I could provide (even after reading
  https://wiki.ubuntu.com/Hotkeys/Troubleshooting/).

  This is on a fully up-to-date Precise 12.04 system.

  WORKAROUND: 1. Put this in /etc/udev/rules.d/70-plantronics.rules:
  ACTION!="add|change", GOTO="xorg_plantronics_end"
  KERNEL!="event*", GOTO="xorg_plantronics_end"
  ENV{ID_VENDOR_ID}=="047f", ENV{ID_MODEL_ID}=="c006", ENV{ID_INPUT_KEY}="1"
  ENV{ID_VENDOR_ID}=="047f", ENV{ID_MODEL_ID}=="c006", RUN+="keymap $name 
0xc00e9 volumeup 0xc00ea volumedown 0xb002f micmute"
  LABEL="xorg_plantronics_end"

  2. Reload udev:
  sudo udevadm control --reload

  3. Unplug the headset and plug it back in

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

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

[Touch-packages] [Bug 879559] Re: X sesssion freeze at screensaver - mouse and ssh still works

[Daniel van Vugt]

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

** Changed in: lightdm
   Status: Confirmed => Invalid

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

Title:
  X sesssion freeze at screensaver - mouse and ssh still works

Status in Light Display Manager:
  Invalid
Status in X.Org X server:
  Invalid
Status in xorg package in Ubuntu:
  Invalid

Bug description:
  dmesg 
  ---
  [   34.605997] [drm] nouveau :01:00.0: PGRAPH - ERROR nsource: DATA_ERROR 
nstatus: BAD_ARGUMENT
  [   34.606009] [drm] nouveau :01:00.0: PGRAPH - ch 1 (0x000ed000) subc 2 
class 0x004a mthd 0x0300 data 0x
  [   34.606016] [drm] nouveau :01:00.0: PGRAPH - ERROR nsource: DATA_ERROR 
nstatus: BAD_ARGUMENT
  [   34.606024] [drm] nouveau :01:00.0: PGRAPH - ch 1 (0x000ed000) subc 2 
class 0x004a mthd 0x0304 data 0x
  [   34.606033] [drm] nouveau :01:00.0: PGRAPH - ERROR nsource: 
ILLEGAL_MTHD nstatus: BAD_ARGUMENT PROTECTION_FAULT
  [   34.606042] [drm] nouveau :01:00.0: PGRAPH - ch 1 (0x000ed000) subc 2 
class 0x004a mthd 0x0308 data 0x03600480
  [   34.606049] [drm] nouveau :01:00.0: PGRAPH - ERROR nsource: DATA_ERROR 
nstatus: BAD_ARGUMENT PROTECTION_FAULT
  [   34.606058] [drm] nouveau :01:00.0: PGRAPH - ch 1 (0x000ed000) subc 2 
class 0x004a mthd 0x0300 data 0x
  [   34.606064] [drm] nouveau :01:00.0: PGRAPH - ERROR nsource: DATA_ERROR 
nstatus: BAD_ARGUMENT PROTECTION_FAULT
  [   34.606073] [drm] nouveau :01:00.0: PGRAPH - ch 1 (0x000ed000) subc 2 
class 0x004a mthd 0x0304 data 0x0480
  [   34.606080] [drm] nouveau :01:00.0: PGRAPH - ERROR nsource: 
ILLEGAL_MTHD nstatus: BAD_ARGUMENT PROTECTION_FAULT
  [   34.606089] [drm] nouveau :01:00.0: PGRAPH - ch 1 (0x000ed000) subc 2 
class 0x004a mthd 0x0308 data 0x03600480
  [   34.606096] [drm] nouveau :01:00.0: PGRAPH - ERROR nsource: DATA_ERROR 
nstatus: BAD_ARGUMENT PROTECTION_FAULT
  [   34.606104] [drm] nouveau :01:00.0: PGRAPH - ch 1 (0x000ed000) subc 2 
class 0x004a mthd 0x0300 data 0x
  [   34.606111] [drm] nouveau :01:00.0: PGRAPH - ERROR nsource: DATA_ERROR 
nstatus: BAD_ARGUMENT PROTECTION_FAULT
  [   34.606120] [drm] nouveau :01:00.0: PGRAPH - ch 1 (0x000ed000) subc 2 
class 0x004a mthd 0x0304 data 0x0900
  [   34.606127] [drm] nouveau :01:00.0: PGRAPH - ERROR nsource: 
ILLEGAL_MTHD nstatus: BAD_ARGUMENT PROTECTION_FAULT
  [   34.606136] [drm] nouveau :01:00.0: PGRAPH - ch 1 (0x000ed000) subc 2 
class 0x004a mthd 0x0308 data 0x036000ba
  [   34.606142] [drm] nouveau :01:00.0: PGRAPH - ERROR nsource: DATA_ERROR 
nstatus: BAD_ARGUMENT PROTECTION_FAULT
  [   34.606151] [drm] nouveau :01:00.0: PGRAPH - ch 1 (0x000ed000) subc 2 
class 0x004a mthd 0x0300 data 0x
  [   34.606158] [drm] nouveau :01:00.0: PGRAPH - ERROR nsource: DATA_ERROR 
nstatus: BAD_ARGUMENT PROTECTION_FAULT
  [   34.606167] [drm] nouveau :01:00.0: PGRAPH - ch 1 (0x000ed000) subc 2 
class 0x004a mthd 0x0304 data 0x0360
  [   34.606173] [drm] nouveau :01:00.0: PGRAPH - ERROR nsource: 
ILLEGAL_MTHD nstatus: BAD_ARGUMENT PROTECTION_FAULT
  [   34.606182] [drm] nouveau :01:00.0: PGRAPH - ch 1 (0x000ed000) subc 2 
class 0x004a mthd 0x0308 data 0x033009ba
  [   34.614601] [drm] nouveau :01:00.0: Setting dpms mode 3 on vga encoder 
(output 1)
  [   34.634634] [drm] nouveau :01:00.0: Setting dpms mode 0 on vga encoder 
(output 1)
  [   34.634639] [drm] nouveau :01:00.0: Output VGA-1 is running on CRTC 1 
using output A
  [   34.639243] [drm] nouveau :01:00.0: Setting dpms mode 3 on lvds 
encoder (output 0)
  [   34.639247] [drm] nouveau :01:00.0: Calling LVDS script 6:
  [   34.639252] [drm] nouveau :01:00.0: 0xCDA1: Parsing digital output 
script table
  [   34.699020] [drm] nouveau :01:00.0: Calling LVDS script 2:
  [   34.699024] [drm] nouveau :01:00.0: 0xCE17: Parsing digital output 
script table
  [   34.846053] [drm] nouveau :01:00.0: Setting dpms mode 0 on lvds 
encoder (output 0)
  [   34.846057] [drm] nouveau :01:00.0: Calling LVDS script 5:
  [   34.846060] [drm] nouveau :01:00.0: 0xCD92: Parsing digital output 
script table
  [   34.846068] [drm] nouveau :01:00.0: Output LVDS-1 is running on CRTC 0 
using output A
  [   36.413281] [drm] nouveau :01:00.0: PGRAPH - ERROR nsource: 
ILLEGAL_MTHD nstatus: BAD_ARGUMENT PROTECTION_FAULT
  [   36.413295] [drm] nouveau :01:00.0: PGRAPH - ch 1 (0x000ed000) subc 6 
class 0x009f mthd 0x03fc data 0x
  [   36.413302] [drm] nouveau :01:00.0: PGRAPH - ERROR nsource: 
ILLEGAL_MTHD nstatus: BAD_ARGUMENT PROTECTION_FAULT
  [   36.413311] [drm] nouveau :01:00.0: PGRAPH - ch 1 (0x000ed000) subc 6 
class 0x009f mthd 0x0400 data 0x
  [   36.413318] [drm] nouveau :01:00.0: PGRAPH - ERROR nsource: 

[Touch-packages] [Bug 1057120] Re: Ubiquity screen problem during install.

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


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

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

Title:
  Ubiquity screen problem during install.

Status in X.Org X server:
  Won't Fix
Status in xorg package in Ubuntu:
  Invalid

Bug description:
  1) Lubuntu 12.10 i386 Beta2 26 September 2012
  2) Ubiquity 2.12.5
  3) I did not expect during install for the screen to as is the photo I have 
attached to this bug report.
  4) The Ubiquity screen bug is displayed in the photo image I have attached to 
this bug report. I have encountered this problem during September 25th and 26th 
Beta2 install testcases.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
  Uname: Linux 3.5.0-15-generic i686
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: i386
  Date: Wed Sep 26 14:29:55 2012
  InstallCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/lubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash --
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Beta i386 (20120926)
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1057120/+subscriptions

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

[Touch-packages] [Bug 1069064] Re: Screen keeps blinking after boot up

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

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

Title:
  Screen keeps blinking after boot up

Status in xorg package in Ubuntu:
  Invalid
Status in xorg package in openSUSE:
  Won't Fix

Bug description:
  Hi,

  I tried installing ubuntu quantal on my acer 5002 laptop with sis
  card. But on boot from usb screen keeps flickering with only mouse
  pointer shows up on whole screen.

  I tried xubuntu as well and result is same.
  --- 
  ApportVersion: 2.0.1-0ubuntu14
  Architecture: i386
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  Package: xorg 1:7.6+12ubuntu1
  PackageArchitecture: i386
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.2.0-32.51-generic-pae 3.2.30
  Tags:  precise ubuntu
  Uname: Linux 3.2.0-32-generic-pae i686
  UnreportableReason: Please work this issue through technical support channels 
first.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1778178] Re: Upgrade to PulseAudio 12.0

[Daniel van Vugt]

** Attachment added: "pulseaudio_12.0.orig.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1778178/+attachment/5156307/+files/pulseaudio_12.0.orig.tar.xz

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

Title:
  Upgrade to PulseAudio 12.0

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Upgrade to PulseAudio 12.0

  https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/12.0/

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

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

[Touch-packages] [Bug 1778178] Re: Upgrade to PulseAudio 12.0

[Daniel van Vugt]

** Attachment added: "pulseaudio_12.0-1ubuntu1.debian.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1778178/+attachment/5156308/+files/pulseaudio_12.0-1ubuntu1.debian.tar.xz

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

Title:
  Upgrade to PulseAudio 12.0

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Upgrade to PulseAudio 12.0

  https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/12.0/

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

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

[Touch-packages] [Bug 1775016] Re: Ubuntu/Xubuntu 18.04 bug: Keyboard stops working in the middle of typing when running firefox and when running the terminal (sudo su) and similar programs until rebo

[Daniel van Vugt]

Please open a terminal window and run 'dmesg -w', ensuring the window is
always visible. Now continue using the system until the keyboard stops
working. Finally, take a photo of the terminal window and attach it
here.

It looks like you might be using a wireless "RAPOO" keyboard. Is that
right? You may also want to test a wired keyboard.

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

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

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

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

Title:
  Ubuntu/Xubuntu 18.04 bug: Keyboard stops working in the middle of
  typing when running firefox and when running the terminal (sudo su)
  and similar programs until reboot.

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu/Xubuntu 18.04 LTS bug

  What should have happened: Keyboard should have been working no matter
  the processes

  What happened instead: Keyboard stops working in the middle of typing
  when running firefox and when running the terminal as (sudo su) and
  similar programs. I cannot even type a password. Keyboard only works
  again after a reboot.

  xserver-xorg:
    Installed: 1:7.7+19ubuntu7
    Candidate: 1:7.7+19ubuntu7
    Version table:
   *** 1:7.7+19ubuntu7 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  xserver-xorg-input-all:
    Installed: 1:7.7+19ubuntu7
    Candidate: 1:7.7+19ubuntu7
    Version table:
   *** 1:7.7+19ubuntu7 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Jun  4 22:13:35 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0493]
  InstallationDate: Installed on 2018-06-04 (0 days ago)
  InstallationMedia: Moment Plus OS amd64 2.5.6 "Aethereal"
  MachineType: Dell Inc. Latitude E6420
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=13c4faa3-4e88-42db-b523-8ac6c7a793f8 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/18/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0X8R3Y
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0X8R3Y:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  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/1775016/+subscriptions

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

[Touch-packages] [Bug 1772898] Re: [SRU] New stable release 1.14.1

[Launchpad Bug Tracker]

This bug was fixed in the package gst-libav1.0 - 1.14.1-1~ubuntu18.04.1

---
gst-libav1.0 (1.14.1-1~ubuntu18.04.1) bionic; urgency=medium

  * No-change backport to bionic (LP: #1772898)

gst-libav1.0 (1.14.1-1) unstable; urgency=medium

  * New upstream bugfix release

 -- Iain Lane   Wed, 23 May 2018 13:55:48
+0100

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

Title:
  [SRU] New stable release 1.14.1

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  In Progress
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  In Progress
Status in gst-python1.0 package in Ubuntu:
  In Progress
Status in gst-rtsp-server1.0 package in Ubuntu:
  In Progress
Status in gstreamer-editing-services1.0 package in Ubuntu:
  In Progress
Status in gstreamer-vaapi package in Ubuntu:
  In Progress
Status in gstreamer1.0 package in Ubuntu:
  Fix Committed
Status in gst-libav1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-bad1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-base1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-good1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-ugly1.0 source package in Bionic:
  Fix Released
Status in gst-python1.0 source package in Bionic:
  Fix Released
Status in gst-rtsp-server1.0 source package in Bionic:
  Fix Released
Status in gstreamer-editing-services1.0 source package in Bionic:
  Fix Released
Status in gstreamer-vaapi source package in Bionic:
  Fix Released
Status in gstreamer1.0 source package in Bionic:
  Fix Released

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.14 series
  that 18.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1772898/+subscriptions

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

[Touch-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

[Daniel van Vugt]

** Tags added: patch

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  [Impact]

  Users of Bluetooth audio have no sound after they suspend and resume
  the system.

  [Test Case]

   1. Connect to Bluetooth audio device
   2. Suspend & Resume
   3. Reconnect to Bluetooth device.

  [Regression Potential]

  Low. Although common Bluetooth code is modified in the fix, it has
  been released as a patch in other distros for some time already.

  [Other Info]

  Already released to cosmic as part of bluez version 5.50.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
    UP RUNNING PSCAN
    RX bytes:5025 acl:32 sco:0 events:202 errors:0
    TX bytes:5785 acl:32 sco:0 commands:103 errors:0

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

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

[Touch-packages] [Bug 1768905] Re: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Julian Andres Klode]

OK, so let's roll out xenial as well. We waited our week.

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

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

Title:
  package menu 2.1.47ubuntu2 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Incomplete
Status in menu package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in menu source package in Xenial:
  Fix Committed
Status in apt source package in Artful:
  Confirmed
Status in menu source package in Artful:
  Fix Released
Status in apt source package in Bionic:
  Confirmed
Status in menu source package in Bionic:
  Fix Released
Status in menu package in Debian:
  New

Bug description:
  [Impact]
  Breaks some upgrades, depending on install order.

  [Test case]
  N/A. After consultation with the dpkg maintainer and investigating the 
situation, it's reasonably safe to assume that noawait is the right thing to do:

  * the intended use for the trigger is to run _after_ packages with .menu 
  files are configured, not before; therefore
  * the file trigger is triggered manually from the postinst again, discussion 
has been that the file trigger is not actually needed.

  [Regression potential]
  Menu might not be updated correctly

  [Original bug report]
  I get this error when I update to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: menu 2.1.47ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu May  3 16:51:28 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
   libstdc++6 8-20180414-1ubuntu2
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2018-04-11 (22 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: menu
  Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago)

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

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

[Touch-packages] [Bug 1772898] Re: [SRU] New stable release 1.14.1

[Launchpad Bug Tracker]

This bug was fixed in the package gst-plugins-base1.0 -
1.14.1-1ubuntu1~ubuntu18.04.1

---
gst-plugins-base1.0 (1.14.1-1ubuntu1~ubuntu18.04.1) bionic; urgency=medium

  * No-change backport to bionic.

gst-plugins-base1.0 (1.14.1-1ubuntu1) cosmic; urgency=medium

  * Merge with Debian (LP: #1772898). Remaining change:
+ debian/rules: Build for GLES only on arm. We build OpenGL support, which
  conflicts with Qt's OpenGL support - used in gst-good - if built for a
  different implementation. This fixes an FTBFS of gst-plugins-good1.0 due
  to conflicting typedefs being dragged in by gst and Qt. This might be a
  bug in mesa - if the headers are supposed to be includable simultaneously.
  See FDO #105328 for that.

gst-plugins-base1.0 (1.14.1-1) unstable; urgency=medium

  * New upstream bugfix release

 -- Iain Lane   Wed, 23 May 2018 13:59:01 +0100

** Changed in: gst-rtsp-server1.0 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] New stable release 1.14.1

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  In Progress
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  In Progress
Status in gst-python1.0 package in Ubuntu:
  In Progress
Status in gst-rtsp-server1.0 package in Ubuntu:
  In Progress
Status in gstreamer-editing-services1.0 package in Ubuntu:
  In Progress
Status in gstreamer-vaapi package in Ubuntu:
  In Progress
Status in gstreamer1.0 package in Ubuntu:
  Fix Committed
Status in gst-libav1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-bad1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-base1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-good1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-ugly1.0 source package in Bionic:
  Fix Released
Status in gst-python1.0 source package in Bionic:
  Fix Released
Status in gst-rtsp-server1.0 source package in Bionic:
  Fix Released
Status in gstreamer-editing-services1.0 source package in Bionic:
  Fix Released
Status in gstreamer-vaapi source package in Bionic:
  Fix Released
Status in gstreamer1.0 source package in Bionic:
  Fix Released

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.14 series
  that 18.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1772898/+subscriptions

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

[Touch-packages] [Bug 1772898] Re: [SRU] New stable release 1.14.1

[Launchpad Bug Tracker]

This bug was fixed in the package gst-plugins-good1.0 -
1.14.1-1ubuntu1~ubuntu18.04.1

---
gst-plugins-good1.0 (1.14.1-1ubuntu1~ubuntu18.04.1) bionic; urgency=medium

  * No-change backport to bionic.

gst-plugins-good1.0 (1.14.1-1ubuntu1) cosmic; urgency=medium

  * Merge with Debian unstable (LP: #1772898); remaining changes:
+ Import plugins from -bad that are needed for main applications.
  - jpegformat
  - camerabin (+ basecamerabinsrc + photography)
+ Break and Replace -bad versions which contained these plugins.
+ Add a library package containing the shared library and a -dev package for
  compiling against it. Add Breaks and Replaces against the plugins packages
  which formerly contained files shipped here.
+ Add 'pluginsdir' variable to our added pcfile for compatibility with
  some external software
+ debian/control{,.in}: Update Vcs-* for Ubuntu
  * Revert 1.14.0-{2,3,4}. We've worked around this issue in -base instead, so
we don't need to disable Qt5 here.

gst-plugins-good1.0 (1.14.1-1) unstable; urgency=medium

  * New upstream bugfix release

gst-plugins-good1.0 (1.14.0-4) unstable; urgency=medium

  * debian/control.in:
+ Let the -dbg package only depend on the qt5 package on non-armel/hf.

gst-plugins-good1.0 (1.14.0-3) unstable; urgency=medium

  * debian/rules:
+ Use DEB_HOST_ARCH instead of DEB_HOST_ARCH_CPU.

gst-plugins-good1.0 (1.14.0-2) unstable; urgency=medium

  * debian/control.in,
debian/rules:
+ Disable Qt5 plugin on armhf/armel due to mesa headers being broken so
  that this package can move to testing (see #894076).

 -- Iain Lane   Wed, 23 May 2018 14:05:30 +0100

** Changed in: gst-plugins-base1.0 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] New stable release 1.14.1

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  In Progress
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  In Progress
Status in gst-python1.0 package in Ubuntu:
  In Progress
Status in gst-rtsp-server1.0 package in Ubuntu:
  In Progress
Status in gstreamer-editing-services1.0 package in Ubuntu:
  In Progress
Status in gstreamer-vaapi package in Ubuntu:
  In Progress
Status in gstreamer1.0 package in Ubuntu:
  Fix Committed
Status in gst-libav1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-bad1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-base1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-good1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-ugly1.0 source package in Bionic:
  Fix Released
Status in gst-python1.0 source package in Bionic:
  Fix Released
Status in gst-rtsp-server1.0 source package in Bionic:
  Fix Released
Status in gstreamer-editing-services1.0 source package in Bionic:
  Fix Released
Status in gstreamer-vaapi source package in Bionic:
  Fix Released
Status in gstreamer1.0 source package in Bionic:
  Fix Released

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.14 series
  that 18.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1772898/+subscriptions

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

[Touch-packages] [Bug 1772898] Re: [SRU] New stable release 1.14.1

[Launchpad Bug Tracker]

This bug was fixed in the package gst-rtsp-server1.0 -
1.14.1-1~ubuntu18.04.1

---
gst-rtsp-server1.0 (1.14.1-1~ubuntu18.04.1) bionic; urgency=medium

  * No-change backport to bionic (LP: #1772898)

gst-rtsp-server1.0 (1.14.1-1) unstable; urgency=medium

  * New upstream bugfix release

 -- Iain Lane   Wed, 23 May 2018 13:56:07
+0100

** Changed in: gst-libav1.0 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] New stable release 1.14.1

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  In Progress
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  In Progress
Status in gst-python1.0 package in Ubuntu:
  In Progress
Status in gst-rtsp-server1.0 package in Ubuntu:
  In Progress
Status in gstreamer-editing-services1.0 package in Ubuntu:
  In Progress
Status in gstreamer-vaapi package in Ubuntu:
  In Progress
Status in gstreamer1.0 package in Ubuntu:
  Fix Committed
Status in gst-libav1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-bad1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-base1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-good1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-ugly1.0 source package in Bionic:
  Fix Released
Status in gst-python1.0 source package in Bionic:
  Fix Released
Status in gst-rtsp-server1.0 source package in Bionic:
  Fix Released
Status in gstreamer-editing-services1.0 source package in Bionic:
  Fix Released
Status in gstreamer-vaapi source package in Bionic:
  Fix Released
Status in gstreamer1.0 source package in Bionic:
  Fix Released

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.14 series
  that 18.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1772898/+subscriptions

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

[Touch-packages] [Bug 1772898] Re: [SRU] New stable release 1.14.1

[Launchpad Bug Tracker]

This bug was fixed in the package gst-python1.0 - 1.14.1-1~ubuntu18.04.1

---
gst-python1.0 (1.14.1-1~ubuntu18.04.1) bionic; urgency=medium

  * No-change backport to bionic (LP: #1772898)

gst-python1.0 (1.14.1-1) unstable; urgency=medium

  * New upstream bugfix release

gst-python1.0 (1.14.0-2) unstable; urgency=medium

  * debian/patches/0001-overrides-use-get_introspection_module.patch,
debian/control:
+ Fix importing of GI overrides (Closes: #896241, #896222).

 -- Iain Lane   Wed, 23 May 2018 13:56:01
+0100

** Changed in: gst-plugins-good1.0 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] New stable release 1.14.1

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  In Progress
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  In Progress
Status in gst-python1.0 package in Ubuntu:
  In Progress
Status in gst-rtsp-server1.0 package in Ubuntu:
  In Progress
Status in gstreamer-editing-services1.0 package in Ubuntu:
  In Progress
Status in gstreamer-vaapi package in Ubuntu:
  In Progress
Status in gstreamer1.0 package in Ubuntu:
  Fix Committed
Status in gst-libav1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-bad1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-base1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-good1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-ugly1.0 source package in Bionic:
  Fix Released
Status in gst-python1.0 source package in Bionic:
  Fix Released
Status in gst-rtsp-server1.0 source package in Bionic:
  Fix Released
Status in gstreamer-editing-services1.0 source package in Bionic:
  Fix Released
Status in gstreamer-vaapi source package in Bionic:
  Fix Released
Status in gstreamer1.0 source package in Bionic:
  Fix Released

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.14 series
  that 18.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1772898/+subscriptions

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

[Touch-packages] [Bug 1772898] Re: [SRU] New stable release 1.14.1

[Launchpad Bug Tracker]

This bug was fixed in the package gstreamer-editing-services1.0 -
1.14.1-1~ubuntu18.04.1

---
gstreamer-editing-services1.0 (1.14.1-1~ubuntu18.04.1) bionic; urgency=medium

  * No-change backport to bionic (LP: #1772898)

gstreamer-editing-services1.0 (1.14.1-1) unstable; urgency=medium

  * New upstream bugfix release

 -- Iain Lane   Wed, 23 May 2018 13:56:13
+0100

** Changed in: gst-python1.0 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] New stable release 1.14.1

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  In Progress
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  In Progress
Status in gst-python1.0 package in Ubuntu:
  In Progress
Status in gst-rtsp-server1.0 package in Ubuntu:
  In Progress
Status in gstreamer-editing-services1.0 package in Ubuntu:
  In Progress
Status in gstreamer-vaapi package in Ubuntu:
  In Progress
Status in gstreamer1.0 package in Ubuntu:
  Fix Committed
Status in gst-libav1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-bad1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-base1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-good1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-ugly1.0 source package in Bionic:
  Fix Released
Status in gst-python1.0 source package in Bionic:
  Fix Released
Status in gst-rtsp-server1.0 source package in Bionic:
  Fix Released
Status in gstreamer-editing-services1.0 source package in Bionic:
  Fix Released
Status in gstreamer-vaapi source package in Bionic:
  Fix Released
Status in gstreamer1.0 source package in Bionic:
  Fix Released

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.14 series
  that 18.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1772898/+subscriptions

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

[Touch-packages] [Bug 1772898] Re: [SRU] New stable release 1.14.1

[Launchpad Bug Tracker]

This bug was fixed in the package gstreamer-vaapi -
1.14.1-1~ubuntu18.04.1

---
gstreamer-vaapi (1.14.1-1~ubuntu18.04.1) bionic; urgency=medium

  * No-change backport to bionic (LP: #1772898)

gstreamer-vaapi (1.14.1-1) unstable; urgency=medium

  * New upstream bugfix release

 -- Iain Lane   Wed, 23 May 2018 13:56:20
+0100

** Changed in: gstreamer-vaapi (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

** Changed in: gst-plugins-ugly1.0 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] New stable release 1.14.1

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  In Progress
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  In Progress
Status in gst-python1.0 package in Ubuntu:
  In Progress
Status in gst-rtsp-server1.0 package in Ubuntu:
  In Progress
Status in gstreamer-editing-services1.0 package in Ubuntu:
  In Progress
Status in gstreamer-vaapi package in Ubuntu:
  In Progress
Status in gstreamer1.0 package in Ubuntu:
  Fix Committed
Status in gst-libav1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-bad1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-base1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-good1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-ugly1.0 source package in Bionic:
  Fix Released
Status in gst-python1.0 source package in Bionic:
  Fix Released
Status in gst-rtsp-server1.0 source package in Bionic:
  Fix Released
Status in gstreamer-editing-services1.0 source package in Bionic:
  Fix Released
Status in gstreamer-vaapi source package in Bionic:
  Fix Released
Status in gstreamer1.0 source package in Bionic:
  Fix Released

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.14 series
  that 18.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1772898/+subscriptions

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

[Touch-packages] [Bug 1772898] Update Released

[Łukasz Zemczak]

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

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

Title:
  [SRU] New stable release 1.14.1

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  In Progress
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  In Progress
Status in gst-python1.0 package in Ubuntu:
  In Progress
Status in gst-rtsp-server1.0 package in Ubuntu:
  In Progress
Status in gstreamer-editing-services1.0 package in Ubuntu:
  In Progress
Status in gstreamer-vaapi package in Ubuntu:
  In Progress
Status in gstreamer1.0 package in Ubuntu:
  Fix Committed
Status in gst-libav1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-bad1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-base1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-good1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-ugly1.0 source package in Bionic:
  Fix Released
Status in gst-python1.0 source package in Bionic:
  Fix Released
Status in gst-rtsp-server1.0 source package in Bionic:
  Fix Released
Status in gstreamer-editing-services1.0 source package in Bionic:
  Fix Released
Status in gstreamer-vaapi source package in Bionic:
  Fix Released
Status in gstreamer1.0 source package in Bionic:
  Fix Released

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.14 series
  that 18.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1772898/+subscriptions

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

[Touch-packages] [Bug 1772898] Re: [SRU] New stable release 1.14.1

[Launchpad Bug Tracker]

This bug was fixed in the package gst-plugins-bad1.0 -
1.14.1-1ubuntu1~ubuntu18.04.1

---
gst-plugins-bad1.0 (1.14.1-1ubuntu1~ubuntu18.04.1) bionic; urgency=medium

  * No-change backport to bionic.

gst-plugins-bad1.0 (1.14.1-1ubuntu1) cosmic; urgency=medium

  * Merge with Debian unstable (LP: #1772898); remaining changes:
+ Stop installing camerabin2 basecamerabin jpegformat - plugins which have
  moved to -good.
+ Provide gstreamer-plugins-bad-1.0.pc with Requires on
  gstreamer-plugins-good-1.0 - the package we've moved the referenced
  library to. This maintains compatibility with upstream software and
  other distributions.
+ debian/control{,.in}: Update Vcs-* for Ubuntu

gst-plugins-bad1.0 (1.14.1-1) unstable; urgency=medium

  * New upstream bugfix release

 -- Iain Lane   Wed, 23 May 2018 14:02:04 +0100

** Changed in: gstreamer-editing-services1.0 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] New stable release 1.14.1

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  In Progress
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  In Progress
Status in gst-python1.0 package in Ubuntu:
  In Progress
Status in gst-rtsp-server1.0 package in Ubuntu:
  In Progress
Status in gstreamer-editing-services1.0 package in Ubuntu:
  In Progress
Status in gstreamer-vaapi package in Ubuntu:
  In Progress
Status in gstreamer1.0 package in Ubuntu:
  Fix Committed
Status in gst-libav1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-bad1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-base1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-good1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-ugly1.0 source package in Bionic:
  Fix Released
Status in gst-python1.0 source package in Bionic:
  Fix Released
Status in gst-rtsp-server1.0 source package in Bionic:
  Fix Released
Status in gstreamer-editing-services1.0 source package in Bionic:
  Fix Released
Status in gstreamer-vaapi source package in Bionic:
  Fix Released
Status in gstreamer1.0 source package in Bionic:
  Fix Released

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.14 series
  that 18.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1772898/+subscriptions

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

[Touch-packages] [Bug 1772898] Re: [SRU] New stable release 1.14.1

[Launchpad Bug Tracker]

This bug was fixed in the package gst-plugins-ugly1.0 -
1.14.1-1~ubuntu18.04.1

---
gst-plugins-ugly1.0 (1.14.1-1~ubuntu18.04.1) bionic; urgency=medium

  * No-change backport to bionic (LP: #1772898)

gst-plugins-ugly1.0 (1.14.1-1) unstable; urgency=medium

  * New upstream bugfix release

 -- Iain Lane   Wed, 23 May 2018 13:55:56
+0100

** Changed in: gst-plugins-bad1.0 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] New stable release 1.14.1

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  In Progress
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  In Progress
Status in gst-python1.0 package in Ubuntu:
  In Progress
Status in gst-rtsp-server1.0 package in Ubuntu:
  In Progress
Status in gstreamer-editing-services1.0 package in Ubuntu:
  In Progress
Status in gstreamer-vaapi package in Ubuntu:
  In Progress
Status in gstreamer1.0 package in Ubuntu:
  Fix Committed
Status in gst-libav1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-bad1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-base1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-good1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-ugly1.0 source package in Bionic:
  Fix Released
Status in gst-python1.0 source package in Bionic:
  Fix Released
Status in gst-rtsp-server1.0 source package in Bionic:
  Fix Released
Status in gstreamer-editing-services1.0 source package in Bionic:
  Fix Released
Status in gstreamer-vaapi source package in Bionic:
  Fix Released
Status in gstreamer1.0 source package in Bionic:
  Fix Released

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.14 series
  that 18.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1772898/+subscriptions

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

[Touch-packages] [Bug 1772898] Re: [SRU] New stable release 1.14.1

[Launchpad Bug Tracker]

This bug was fixed in the package gstreamer1.0 - 1.14.1-1~ubuntu18.04.1

---
gstreamer1.0 (1.14.1-1~ubuntu18.04.1) bionic; urgency=medium

  * No-change backport to bionic (LP: #1772898)

gstreamer1.0 (1.14.1-1) unstable; urgency=medium

  * New upstream bugfix release.

 -- Iain Lane   Wed, 23 May 2018 13:54:22
+0100

** Changed in: gstreamer1.0 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] New stable release 1.14.1

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  In Progress
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  In Progress
Status in gst-python1.0 package in Ubuntu:
  In Progress
Status in gst-rtsp-server1.0 package in Ubuntu:
  In Progress
Status in gstreamer-editing-services1.0 package in Ubuntu:
  In Progress
Status in gstreamer-vaapi package in Ubuntu:
  In Progress
Status in gstreamer1.0 package in Ubuntu:
  Fix Committed
Status in gst-libav1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-bad1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-base1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-good1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-ugly1.0 source package in Bionic:
  Fix Released
Status in gst-python1.0 source package in Bionic:
  Fix Released
Status in gst-rtsp-server1.0 source package in Bionic:
  Fix Released
Status in gstreamer-editing-services1.0 source package in Bionic:
  Fix Released
Status in gstreamer-vaapi source package in Bionic:
  Fix Released
Status in gstreamer1.0 source package in Bionic:
  Fix Released

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.14 series
  that 18.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1772898/+subscriptions

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

[Touch-packages] [Bug 1778178] Re: Upgrade to PulseAudio 12.0

[Daniel van Vugt]

** Attachment added: "pulseaudio_12.0-1ubuntu1.dsc"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1778178/+attachment/5156309/+files/pulseaudio_12.0-1ubuntu1.dsc

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

Title:
  Upgrade to PulseAudio 12.0

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Upgrade to PulseAudio 12.0

  https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/12.0/

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

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

[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.

[Marc Pignat]

https://wiki.ubuntu.com/Testing/EnableProposed

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

Title:
  Long time booting : Failed to connect to lvmetad. Falling back to
  device scanning.

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Bionic:
  Fix Committed

Bug description:
  [SRU Justification]
  A regression in initramfs-tools causes it to autogenerate config in the 
initramfs saying to resume from any available swap devices, but references the 
swap device by UUID, which is not a canonical form for referring to LVM volumes 
(because of snapshotting, they are not unique).  Ubiquity also generates a file 
in /etc at install time which references the swap partition in the same way.  
Since the lvm2 initramfs hooks also only activate precisely those LVs that are 
detected as needed at boot, this adds an inappropriate 30-second boot delay to 
any system with swap on LVM, which includes any desktop system that was 
configured with LVM (but not full-disk encryption) at install time.

  [Test case]
  1. Install using the "Use LVM" option in the desktop installer.
  4. Reboot.
  5. Verify that dmesg shows a 30-second delay before mounting the root 
filesystem.
  6. Install initramfs-tools from bionic-proposed.
  7. Reboot.
  8. Verify that dmesg no longer shows a 30-second delay before mounting the 
root filesystem.
  9. Install using the bionic daily image that contains the ubiquity from 
bionic-proposed.
  10. Reboot.
  11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that 
there is no delay before mounting the root filesystem.

  [Regression potential]
  This makes changes to shell scripts, and shell is a perilous language. An 
unnoticed bug could cause all initramfs generation, and thus all kernel 
installation, to fail for some users. A regression could also cause a user to 
lose hiberation support that they currently have.

  [Original description]
  After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu 
installation", the
  system is very slow to reboot.

  It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to 
device scanning.",
  then waits 32 seconds, then continues as it should.

  I think this is a ubiquity bug, since the d-i based installer is not affected.
   - ubuntu-18.04-desktop-amd64.iso 
(a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected
   - xubuntu-18.04-desktop-amd64.iso 
(7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected
   - ubuntu-18.04-server-amd64.iso 
(a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not 
affected

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

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

[Touch-packages] [Bug 1778178] Re: Upgrade to PulseAudio 12.0

[Daniel van Vugt]

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: pulseaudio (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Upgrade to PulseAudio 12.0

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Upgrade to PulseAudio 12.0

  https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/12.0/

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

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

[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.

[Daniel Mehrmann]

Ooops, i was testing with version 3.1! Where can i get version 3.2? It's
still not in the update channel

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

Title:
  Long time booting : Failed to connect to lvmetad. Falling back to
  device scanning.

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Bionic:
  Fix Committed

Bug description:
  [SRU Justification]
  A regression in initramfs-tools causes it to autogenerate config in the 
initramfs saying to resume from any available swap devices, but references the 
swap device by UUID, which is not a canonical form for referring to LVM volumes 
(because of snapshotting, they are not unique).  Ubiquity also generates a file 
in /etc at install time which references the swap partition in the same way.  
Since the lvm2 initramfs hooks also only activate precisely those LVs that are 
detected as needed at boot, this adds an inappropriate 30-second boot delay to 
any system with swap on LVM, which includes any desktop system that was 
configured with LVM (but not full-disk encryption) at install time.

  [Test case]
  1. Install using the "Use LVM" option in the desktop installer.
  4. Reboot.
  5. Verify that dmesg shows a 30-second delay before mounting the root 
filesystem.
  6. Install initramfs-tools from bionic-proposed.
  7. Reboot.
  8. Verify that dmesg no longer shows a 30-second delay before mounting the 
root filesystem.
  9. Install using the bionic daily image that contains the ubiquity from 
bionic-proposed.
  10. Reboot.
  11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that 
there is no delay before mounting the root filesystem.

  [Regression potential]
  This makes changes to shell scripts, and shell is a perilous language. An 
unnoticed bug could cause all initramfs generation, and thus all kernel 
installation, to fail for some users. A regression could also cause a user to 
lose hiberation support that they currently have.

  [Original description]
  After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu 
installation", the
  system is very slow to reboot.

  It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to 
device scanning.",
  then waits 32 seconds, then continues as it should.

  I think this is a ubiquity bug, since the d-i based installer is not affected.
   - ubuntu-18.04-desktop-amd64.iso 
(a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected
   - xubuntu-18.04-desktop-amd64.iso 
(7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected
   - ubuntu-18.04-server-amd64.iso 
(a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not 
affected

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

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

[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.

[Daniel Mehrmann]

I can confirm that the bug is still there with version 3.2! :-( I did
"update-initramfs -u".

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

Title:
  Long time booting : Failed to connect to lvmetad. Falling back to
  device scanning.

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Bionic:
  Fix Committed

Bug description:
  [SRU Justification]
  A regression in initramfs-tools causes it to autogenerate config in the 
initramfs saying to resume from any available swap devices, but references the 
swap device by UUID, which is not a canonical form for referring to LVM volumes 
(because of snapshotting, they are not unique).  Ubiquity also generates a file 
in /etc at install time which references the swap partition in the same way.  
Since the lvm2 initramfs hooks also only activate precisely those LVs that are 
detected as needed at boot, this adds an inappropriate 30-second boot delay to 
any system with swap on LVM, which includes any desktop system that was 
configured with LVM (but not full-disk encryption) at install time.

  [Test case]
  1. Install using the "Use LVM" option in the desktop installer.
  4. Reboot.
  5. Verify that dmesg shows a 30-second delay before mounting the root 
filesystem.
  6. Install initramfs-tools from bionic-proposed.
  7. Reboot.
  8. Verify that dmesg no longer shows a 30-second delay before mounting the 
root filesystem.
  9. Install using the bionic daily image that contains the ubiquity from 
bionic-proposed.
  10. Reboot.
  11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that 
there is no delay before mounting the root filesystem.

  [Regression potential]
  This makes changes to shell scripts, and shell is a perilous language. An 
unnoticed bug could cause all initramfs generation, and thus all kernel 
installation, to fail for some users. A regression could also cause a user to 
lose hiberation support that they currently have.

  [Original description]
  After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu 
installation", the
  system is very slow to reboot.

  It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to 
device scanning.",
  then waits 32 seconds, then continues as it should.

  I think this is a ubiquity bug, since the d-i based installer is not affected.
   - ubuntu-18.04-desktop-amd64.iso 
(a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected
   - xubuntu-18.04-desktop-amd64.iso 
(7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected
   - ubuntu-18.04-server-amd64.iso 
(a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not 
affected

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

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

Re: [Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.

[Marc Pignat]

On 06/25/2018 07:56 AM, Silvio Moioli wrote:
> I can still reproduce the problem after upgrading to 3.2 and manually
> deleting /etc/initramfs-tool/conf.d/resume. Help appreciated!
> 

Did you run "initrams -u" after deleting the file?

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

Title:
  Long time booting : Failed to connect to lvmetad. Falling back to
  device scanning.

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Bionic:
  Fix Committed

Bug description:
  [SRU Justification]
  A regression in initramfs-tools causes it to autogenerate config in the 
initramfs saying to resume from any available swap devices, but references the 
swap device by UUID, which is not a canonical form for referring to LVM volumes 
(because of snapshotting, they are not unique).  Ubiquity also generates a file 
in /etc at install time which references the swap partition in the same way.  
Since the lvm2 initramfs hooks also only activate precisely those LVs that are 
detected as needed at boot, this adds an inappropriate 30-second boot delay to 
any system with swap on LVM, which includes any desktop system that was 
configured with LVM (but not full-disk encryption) at install time.

  [Test case]
  1. Install using the "Use LVM" option in the desktop installer.
  4. Reboot.
  5. Verify that dmesg shows a 30-second delay before mounting the root 
filesystem.
  6. Install initramfs-tools from bionic-proposed.
  7. Reboot.
  8. Verify that dmesg no longer shows a 30-second delay before mounting the 
root filesystem.
  9. Install using the bionic daily image that contains the ubiquity from 
bionic-proposed.
  10. Reboot.
  11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that 
there is no delay before mounting the root filesystem.

  [Regression potential]
  This makes changes to shell scripts, and shell is a perilous language. An 
unnoticed bug could cause all initramfs generation, and thus all kernel 
installation, to fail for some users. A regression could also cause a user to 
lose hiberation support that they currently have.

  [Original description]
  After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu 
installation", the
  system is very slow to reboot.

  It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to 
device scanning.",
  then waits 32 seconds, then continues as it should.

  I think this is a ubiquity bug, since the d-i based installer is not affected.
   - ubuntu-18.04-desktop-amd64.iso 
(a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected
   - xubuntu-18.04-desktop-amd64.iso 
(7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected
   - ubuntu-18.04-server-amd64.iso 
(a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not 
affected

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

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

[Touch-packages] [Bug 1714178] Re: Triple 4K monitor display failed (modesetting driver)

[Timo Aaltonen]

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

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

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

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

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

Title:
  Triple 4K monitor display failed (modesetting driver)

Status in X.Org X server:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Title: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Summary: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Steps:
  1. a laptop with Built-in 4K LCD
  2. Cold boot system with Dell Dock connected
  3. Connect a 4K monitor to Dock
  4. Connect 2nd 4K monitor to Dock
  5. Go to [All Settings]=>[Displays] to have the following configuration.
  Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors)
  Mirror displays: disable

  Expected results: Triple monitor display should works without issues
  Actual results: Triple monitor display failed with Dell Dock

  Additional information:
  1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04
  2. Laptop: Dell Precision 5520
  3. Dell Business Thunderbolt Dock - TB16
  https://goo.gl/vFDjpi

  WORKAROUND (UBUNTU 18.04+):
  Log in to "Ubuntu on Wayland" instead of "Ubuntu".

  ---
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:07bf]
     Subsystem: Dell Device [1028:07bf]
  InstallationDate: Installed on 2017-08-29 (2 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Precision 5520
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed 
root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1714178/+subscriptions

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

[Touch-packages] [Bug 1778464] Re: package ifupdown 0.8.17ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package ifupdown 0.8.17ubuntu1.1 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in ifupdown package in Ubuntu:
  New

Bug description:
  This came about while attempting to insstall VLC from Ubuntu software.
  The process returned the error and the above summary.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ifupdown 0.8.17ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Mon Jun 25 01:19:12 2018
  DuplicateSignature:
   package:ifupdown:0.8.17ubuntu1.1
   Setting up ubuntu-software (3.28.1-0ubuntu4.18.04.1) ...
   dpkg: error processing package ifupdown (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-06-24 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ifupdown
  Title: package ifupdown 0.8.17ubuntu1.1 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1778464] [NEW] package ifupdown 0.8.17ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Bob MacKnight]

Public bug reported:

This came about while attempting to insstall VLC from Ubuntu software.
The process returned the error and the above summary.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: ifupdown 0.8.17ubuntu1.1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Mon Jun 25 01:19:12 2018
DuplicateSignature:
 package:ifupdown:0.8.17ubuntu1.1
 Setting up ubuntu-software (3.28.1-0ubuntu4.18.04.1) ...
 dpkg: error processing package ifupdown (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2018-06-24 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: ifupdown
Title: package ifupdown 0.8.17ubuntu1.1 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package ifupdown 0.8.17ubuntu1.1 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in ifupdown package in Ubuntu:
  New

Bug description:
  This came about while attempting to insstall VLC from Ubuntu software.
  The process returned the error and the above summary.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ifupdown 0.8.17ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Mon Jun 25 01:19:12 2018
  DuplicateSignature:
   package:ifupdown:0.8.17ubuntu1.1
   Setting up ubuntu-software (3.28.1-0ubuntu4.18.04.1) ...
   dpkg: error processing package ifupdown (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-06-24 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ifupdown
  Title: package ifupdown 0.8.17ubuntu1.1 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.

[Silvio Moioli]

I can still reproduce the problem after upgrading to 3.2 and manually
deleting /etc/initramfs-tool/conf.d/resume. Help appreciated!

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

Title:
  Long time booting : Failed to connect to lvmetad. Falling back to
  device scanning.

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Bionic:
  Fix Committed

Bug description:
  [SRU Justification]
  A regression in initramfs-tools causes it to autogenerate config in the 
initramfs saying to resume from any available swap devices, but references the 
swap device by UUID, which is not a canonical form for referring to LVM volumes 
(because of snapshotting, they are not unique).  Ubiquity also generates a file 
in /etc at install time which references the swap partition in the same way.  
Since the lvm2 initramfs hooks also only activate precisely those LVs that are 
detected as needed at boot, this adds an inappropriate 30-second boot delay to 
any system with swap on LVM, which includes any desktop system that was 
configured with LVM (but not full-disk encryption) at install time.

  [Test case]
  1. Install using the "Use LVM" option in the desktop installer.
  4. Reboot.
  5. Verify that dmesg shows a 30-second delay before mounting the root 
filesystem.
  6. Install initramfs-tools from bionic-proposed.
  7. Reboot.
  8. Verify that dmesg no longer shows a 30-second delay before mounting the 
root filesystem.
  9. Install using the bionic daily image that contains the ubiquity from 
bionic-proposed.
  10. Reboot.
  11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that 
there is no delay before mounting the root filesystem.

  [Regression potential]
  This makes changes to shell scripts, and shell is a perilous language. An 
unnoticed bug could cause all initramfs generation, and thus all kernel 
installation, to fail for some users. A regression could also cause a user to 
lose hiberation support that they currently have.

  [Original description]
  After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu 
installation", the
  system is very slow to reboot.

  It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to 
device scanning.",
  then waits 32 seconds, then continues as it should.

  I think this is a ubiquity bug, since the d-i based installer is not affected.
   - ubuntu-18.04-desktop-amd64.iso 
(a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected
   - xubuntu-18.04-desktop-amd64.iso 
(7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected
   - ubuntu-18.04-server-amd64.iso 
(a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not 
affected

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

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