[Touch-packages] [Bug 1908063] Re: gdb-multiarch 8.1.1-0ubuntu1 regression: assertion failure or internal error when connecting to QEMU aarch64 gdbstub

[Peter Maydell]

It looks like the reason QEMU's test suite passed was that the older
Ubuntu gdb didn't have a fix for LP:1901026 (support remote connection
over UNIX domain socket), so the test suite would simply skip the
offending test and never get as far as falling over the assertion
failure. After pulling various old binaries out of my backups to test
I'm forced to conclude that I was simply misremembering by-hand use of
the gdbstub working and I must not have used it as recently as I'd
thought. So this is a bug, but not a regression.

A possible set of commits for a cherry-picked fix would be
c8ec2f334c3751c28d5f and 4ef0bef68cfc777e59156fce1 (which together
remove the hard-coded limit on register size and thus also the
assertion), but the former is not a completely trivial patch. I haven't
attempted such a cherry-pick to see if it works.

A workaround is to tell QEMU not to emulate SVE (eg with "-cpu
max,sve=off" -- it is the large SVE vector registers which trigger the
problem.


** Summary changed:

- gdb-multiarch 8.1.1-0ubuntu1 regression: assertion failure or internal error 
when connecting to QEMU aarch64 gdbstub
+ gdb-multiarch 8.1.1-0ubuntu1: assertion failure or internal error when 
connecting to QEMU aarch64 gdbstub

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

Title:
  gdb-multiarch 8.1.1-0ubuntu1: assertion failure or internal error when
  connecting to QEMU aarch64 gdbstub

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

Bug description:
  This bug is a regression introduced in 8.1.1-0ubuntu1 for Bionic --
  the previous 8.1-0ubuntu3.2 gdb works fine with QEMU's gdbstub.

  Reproduce:
  Get the sources for QEMU 5.2.0, and build the aarch64-linux-user target. (It 
looks like Bionic's QEMU is old enough that it doesn't provoke this gdb error.)

  Run
   qemu-aarch64 -g 1234 path/to/some/aarch64/binary

  In another terminal, start gdb-multiarch. At the (gdb) prompt, type
  "target remote :1234". GDB will dump core:

  (gdb) target remote :1234
  Remote debugging using :1234
  Recursive internal problem.
  Aborted (core dumped)

  You can see a variant of this also in the QEMU test suite with "make
  -C your-qemu-build-dir check-tcg", where the error message includes an
  assertion failure:

  [...]

  timeout 60  
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/guest-debug/run-test.py --gdb 
/usr/bin/gdb-multiarch --qemu 
/home/petmay01/linaro/qemu-from-laptop/qemu/build/aarch64-linux/qemu-aarch64 
--qargs "" --bin sha1 --test 
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/tcg/multiarch/gdbstub/sha1.py 
>  run-gdbstub-sha1.out
  /build/gdb-veKdC1/gdb-8.1.1/gdb/regcache.c:122: internal-error: void* 
init_regcache_descr(gdbarch*): Assertion `MAX_REGISTER_SIZE >= 
descr->sizeof_register[i]' failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.

  This is a bug, please report it.  For instructions, see:
  .

  Aborted (core dumped)
  
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/tcg/multiarch/Makefile.target:51:
 recipe for target 'run-gdbstub-sha1' failed

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

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

[Touch-packages] [Bug 1908063] Re: gdb-multiarch 8.1.1-0ubuntu1 regression: assertion failure or internal error when connecting to QEMU aarch64 gdbstub

[Peter Maydell]

Further testing with the old gdb-8.1-0ubuntu3 package shows that this
isn't a regression since then, as that version fails too. I must have
been misled by the apt history.log somehow; sorry for the confusion
there.

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

Title:
  gdb-multiarch 8.1.1-0ubuntu1 regression: assertion failure or internal
  error when connecting to QEMU aarch64 gdbstub

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

Bug description:
  This bug is a regression introduced in 8.1.1-0ubuntu1 for Bionic --
  the previous 8.1-0ubuntu3.2 gdb works fine with QEMU's gdbstub.

  Reproduce:
  Get the sources for QEMU 5.2.0, and build the aarch64-linux-user target. (It 
looks like Bionic's QEMU is old enough that it doesn't provoke this gdb error.)

  Run
   qemu-aarch64 -g 1234 path/to/some/aarch64/binary

  In another terminal, start gdb-multiarch. At the (gdb) prompt, type
  "target remote :1234". GDB will dump core:

  (gdb) target remote :1234
  Remote debugging using :1234
  Recursive internal problem.
  Aborted (core dumped)

  You can see a variant of this also in the QEMU test suite with "make
  -C your-qemu-build-dir check-tcg", where the error message includes an
  assertion failure:

  [...]

  timeout 60  
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/guest-debug/run-test.py --gdb 
/usr/bin/gdb-multiarch --qemu 
/home/petmay01/linaro/qemu-from-laptop/qemu/build/aarch64-linux/qemu-aarch64 
--qargs "" --bin sha1 --test 
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/tcg/multiarch/gdbstub/sha1.py 
>  run-gdbstub-sha1.out
  /build/gdb-veKdC1/gdb-8.1.1/gdb/regcache.c:122: internal-error: void* 
init_regcache_descr(gdbarch*): Assertion `MAX_REGISTER_SIZE >= 
descr->sizeof_register[i]' failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.

  This is a bug, please report it.  For instructions, see:
  .

  Aborted (core dumped)
  
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/tcg/multiarch/Makefile.target:51:
 recipe for target 'run-gdbstub-sha1' failed

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

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

[Touch-packages] [Bug 1908063] [NEW] gdb-multiarch 8.1.1-0ubuntu1 regression: assertion failure or internal error when connecting to QEMU aarch64 gdbstub

[Peter Maydell]

Public bug reported:

This bug is a regression introduced in 8.1.1-0ubuntu1 for Bionic -- the
previous 8.1-0ubuntu3.2 gdb works fine with QEMU's gdbstub.

Reproduce:
Get the sources for QEMU 5.2.0, and build the aarch64-linux-user target. (It 
looks like Bionic's QEMU is old enough that it doesn't provoke this gdb error.)

Run
 qemu-aarch64 -g 1234 path/to/some/aarch64/binary

In another terminal, start gdb-multiarch. At the (gdb) prompt, type
"target remote :1234". GDB will dump core:

(gdb) target remote :1234
Remote debugging using :1234
Recursive internal problem.
Aborted (core dumped)

You can see a variant of this also in the QEMU test suite with "make -C
your-qemu-build-dir check-tcg", where the error message includes an
assertion failure:

[...]

timeout 60  
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/guest-debug/run-test.py --gdb 
/usr/bin/gdb-multiarch --qemu 
/home/petmay01/linaro/qemu-from-laptop/qemu/build/aarch64-linux/qemu-aarch64 
--qargs "" --bin sha1 --test 
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/tcg/multiarch/gdbstub/sha1.py 
>  run-gdbstub-sha1.out
/build/gdb-veKdC1/gdb-8.1.1/gdb/regcache.c:122: internal-error: void* 
init_regcache_descr(gdbarch*): Assertion `MAX_REGISTER_SIZE >= 
descr->sizeof_register[i]' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.

This is a bug, please report it.  For instructions, see:
.

Aborted (core dumped)
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/tcg/multiarch/Makefile.target:51:
 recipe for target 'run-gdbstub-sha1' failed

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

** Affects: gdb (Ubuntu Bionic)
 Importance: Undecided
 Status: New

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

Title:
  gdb-multiarch 8.1.1-0ubuntu1 regression: assertion failure or internal
  error when connecting to QEMU aarch64 gdbstub

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

Bug description:
  This bug is a regression introduced in 8.1.1-0ubuntu1 for Bionic --
  the previous 8.1-0ubuntu3.2 gdb works fine with QEMU's gdbstub.

  Reproduce:
  Get the sources for QEMU 5.2.0, and build the aarch64-linux-user target. (It 
looks like Bionic's QEMU is old enough that it doesn't provoke this gdb error.)

  Run
   qemu-aarch64 -g 1234 path/to/some/aarch64/binary

  In another terminal, start gdb-multiarch. At the (gdb) prompt, type
  "target remote :1234". GDB will dump core:

  (gdb) target remote :1234
  Remote debugging using :1234
  Recursive internal problem.
  Aborted (core dumped)

  You can see a variant of this also in the QEMU test suite with "make
  -C your-qemu-build-dir check-tcg", where the error message includes an
  assertion failure:

  [...]

  timeout 60  
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/guest-debug/run-test.py --gdb 
/usr/bin/gdb-multiarch --qemu 
/home/petmay01/linaro/qemu-from-laptop/qemu/build/aarch64-linux/qemu-aarch64 
--qargs "" --bin sha1 --test 
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/tcg/multiarch/gdbstub/sha1.py 
>  run-gdbstub-sha1.out
  /build/gdb-veKdC1/gdb-8.1.1/gdb/regcache.c:122: internal-error: void* 
init_regcache_descr(gdbarch*): Assertion `MAX_REGISTER_SIZE >= 
descr->sizeof_register[i]' failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.

  This is a bug, please report it.  For instructions, see:
  .

  Aborted (core dumped)
  
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/tcg/multiarch/Makefile.target:51:
 recipe for target 'run-gdbstub-sha1' failed

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

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

[Touch-packages] [Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs

[Peter Maydell]

Just a note that the udev rules change from comment 6 seems to be
necessary to reliably get an image booted under QEMU to bring up a getty
on the serial console. What seems to happen without it is that udevd
spends all its time running copies of 'readlink', and it doesn't get
around to telling systemd about the presence of ttyAMA0 until after
systemd's 1m30 timeout has expired and it gives up, reporting "Timed out
waiting for device dev-ttyAMA0.device". (This happens most of the time
on an emulated QEMU CPU and at least occasionally on one running with
single-vcpu KVM, probably dependent on speed of the host hardware.)

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

Title:
  Unable to network boot Ubuntu 16.04 installer normally on Briggs

Status in busybox package in Ubuntu:
  Fix Released
Status in debian-installer package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in busybox source package in Xenial:
  Won't Fix
Status in debian-installer source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  Fix Released
Status in busybox source package in Yakkety:
  Fix Released
Status in debian-installer source package in Yakkety:
  Invalid
Status in systemd source package in Yakkety:
  Fix Released

Bug description:
  == Comment: #7 - Guilherme Guaglianoni Piccoli  - 
2016-08-19 10:08:07 ==
  The normal procedure to perform a Netboot installation of Ubuntu 16.04 is to 
download the latest vmlinux and initrd.gz files available, and kexec them with 
no parameters (at least in ppc64el).

  We're experiencing a strange issue in which the installer freezes
  before menus are showed. The system hangs in the point specified
  below, right after the i40e driver initialization:

  [   11.052832] i40e 0002:01:00.0 enP2p1s0f0: renamed from eth0
  [   11.073976] i40e 0002:01:00.1 enP2p1s0f1: renamed from eth1
  [   11.117799] i40e 0002:01:00.2 enP2p1s0f2: renamed from eth2
  [   11.225745] i40e 0002:01:00.3 enP2p1s0f3: renamed from eth3
  ***HANG***

  The most difficult part in this issue is that it seems to be a timing
  issue/race condition, and many debug trials end up by avoiding the
  issue reproduction (heisenbug).

  We were successful though in getting logs by booting the kernel with
  the command-line "BOOT_DEBUG=2" and by changing the initrd in order to
  enable systemd debug; only the files "init" and "start-udev" were
  changed in initrd, both attached here.

  We've attached here a saved screen session that shows the entire boot
  process until it gets flooded with lots of messages like:

  "starting '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
  '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'(err) 'failed to 
execute '/bin/readlink' '/bin/readlink /etc/
  udev/rules.d/80-net-setup-link.rules': No such file or directory'

  seq 3244 queued, 'add' 'pci_bus'
  starting '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
  passed 408 byte device to netlink monitor 0x1003cfe8020seq 3236 
running'/bin/readlink /etc/udev/rules.d/80-net-setup-l
  ink.rules'(err) 'failed to execute '/bin/readlink' '/bin/readlink 
/etc/udev/rules.d/80-net-setup-link.rules': No such
  file or directory'
  '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'(err) 'failed to 
execute '/bin/readlink' '/bin/readlink /etc/
  udev/rules.d/80-net-setup-link.rules': No such file or directory'
  Process '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' failed with 
exit code 2.
  PROGRAM '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' 
/lib/udev/rules.d/73-usb-net-by-mac.rules:6
  passed device to netlink monitor 0x1003d01f730
  "

  Then it keeps hanged in this stage. We re-tested it by changing the
  file 73-usb-net-by-mac.rules in initrd, replacing "
  /etc/udev/rules.d/80-net-setup-link.rules" to  "/lib/udev/rules.d/80
  -net-setup-link.rules", since the former does not exist whereas the
  latter does. Same issue were observed!

  Notice that if we boot the installer with command-line "net.ifnames=0"
  or "net.ifnames=1", the problem does not reproduces anymore.

  We want to ask Canonical's help in investigating this issue.
  Thanks,

  Guilherme

  
  SRU INFORMATION for systemd
  ===

  Test case:
   * Check what happens for uevents on devices which are not USB network 
interfaces:
 udevadm test /sys/devices/virtual/mem/null
 udevadm test /sys/class/net/lo

   With the current version these will run

PROGRAM '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
  /lib/udev/rules.d/73-usb-net-by-mac.rules:6

   which is pointless. With the proposed version these should be gone.

   * Ensure that the rule still works as intended by connecting an USB
  network device that has a permanent MAC address (e. g. Android
  tethering uses a 

[Touch-packages] [Bug 1543185] Re: Malformed query causing timeouts due to ignored upstream queries

[Peter Maydell]

This post to the dnsmasq-discuss list:
http://lists.thekelleys.org.uk/pipermail/dnsmasq-
discuss/2015q2/009575.html  suggests that the bug has been fixed in a
later version of dnsmasq and should be fairly easy to backport.

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

Title:
  Malformed query causing timeouts due to ignored upstream queries

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  In some situations dnsmasq makes malformed upstream queries resulting
  in servfail being returned after the 5s timeout built in to dnsmask.

  For example asking for

  foo

  with athing.bar.com and bar.com in the search path and two servers
  dns1.bar.com and dns1.bar.com results in

  System asks both dns1 and dns2 about: 
 foo.athing.bar.com => immediate NXDomain from both;
  asks  dns1 about:
foo.  => Servfail;
  asks both about:
   foo. with what tcpdump transcribes as '[b2&3=0x182] A?  => no 
response from either [5 sec timeout];
  retries:
   simple "A? foo." query to both, immediate Servfail from both

  The query giving the time out appear to be malformed and the upstream
  servers are completely ignoring it leading to the time out.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: dnsmasq-base 2.68-1ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
  Uname: Linux 3.13.0-77-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Feb  8 15:38:26 2016
  InstallationDate: Installed on 2014-05-07 (642 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1543185] Re: Malformed query causing timeouts due to ignored upstream queries

[Peter Maydell]

Ah, it looks like Colin did just cherry pick the fix for this bug; from
the backport .deb's changelog:

+dnsmasq (2.68-1ubuntu0.1ppa1) trusty; urgency=medium
+
+  * Cherry-pick from 2.73:
+- Correctly sanitise DNS header bits in answer when recreating query for
+  retry.
+
+ -- Colin Watson   Mon, 08 Feb 2016 15:46:48 +

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

Title:
  Malformed query causing timeouts due to ignored upstream queries

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  In some situations dnsmasq makes malformed upstream queries resulting
  in servfail being returned after the 5s timeout built in to dnsmask.

  For example asking for

  foo

  with athing.bar.com and bar.com in the search path and two servers
  dns1.bar.com and dns1.bar.com results in

  System asks both dns1 and dns2 about: 
 foo.athing.bar.com => immediate NXDomain from both;
  asks  dns1 about:
foo.  => Servfail;
  asks both about:
   foo. with what tcpdump transcribes as '[b2&3=0x182] A?  => no 
response from either [5 sec timeout];
  retries:
   simple "A? foo." query to both, immediate Servfail from both

  The query giving the time out appear to be malformed and the upstream
  servers are completely ignoring it leading to the time out.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: dnsmasq-base 2.68-1ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
  Uname: Linux 3.13.0-77-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Feb  8 15:38:26 2016
  InstallationDate: Installed on 2014-05-07 (642 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1478035] [NEW] pkg-config --static --libs gnutls includes an option that gcc doesn't recognize (-R)

[Peter Maydell]

Public bug reported:

The output of pkg-config --static --libs gnutls is the following:

-R/usr/lib/x86_64-linux-gnu -lgnutls -lgcrypt -lgpg-error -ltasn1 -lz
-lp11-kit

However, gcc doesn't understand the -R option, so you can't pass the
pkg-config output as a set of gcc command line options the way that pkg-
config says you are supposed to be able to.

It seems likely to me that this -R option is an error and should be
removed.

(The pkg-config output for a non-static build is fine.)

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libgnutls-dev 2.12.23-12ubuntu2.2
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
Date: Fri Jul 24 15:49:47 2015
InstallationDate: Installed on 2014-05-22 (428 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
SourcePackage: gnutls26
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  pkg-config --static --libs gnutls includes an option that gcc
  doesn't recognize (-R)

Status in gnutls26 package in Ubuntu:
  New

Bug description:
  The output of pkg-config --static --libs gnutls is the following:

  -R/usr/lib/x86_64-linux-gnu -lgnutls -lgcrypt -lgpg-error -ltasn1 -lz
  -lp11-kit

  However, gcc doesn't understand the -R option, so you can't pass the
  pkg-config output as a set of gcc command line options the way that
  pkg-config says you are supposed to be able to.

  It seems likely to me that this -R option is an error and should be
  removed.

  (The pkg-config output for a non-static build is fine.)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libgnutls-dev 2.12.23-12ubuntu2.2
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  Date: Fri Jul 24 15:49:47 2015
  InstallationDate: Installed on 2014-05-22 (428 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: gnutls26
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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