date:20180319

1. Is there any file type for which VLC can play the audio?

2. Can you provide a screenshot (Alt+PrtScn) of the dialog: VLC > Tools
> Preferences > Audio ?

3. Does this command make audio work in Totem?
sudo apt remove gstreamer1.0-libav

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

Title:
No audio on vlc or videos sound or video files

Status in ffmpeg package in Ubuntu:
Incomplete
Status in pulseaudio package in Ubuntu:
Incomplete

Bug description:
Up until a few weeks ago there was no problem with playing sound from mp3
files. I have a pair of usb speakers. Audio plays Ok on them for video clips
using Chrome (e.g. from BBC website). Using vlc 2.2.2 (from Ubuntu repos),
neither a CD nor DVD (video is Ok) nor mp3 file plays audio. mp3 files play Ok
using Rhythmbox. I've also tried vlc 3.0 with no success.
Interestingly, the standard Videos app (Totem?) also doesn't play sound on
these speakers either of an mp4 file (downloaded from YouTube, though it plays
Ok on YouTube website using Chrome) or a DVD. Clemenetine plays mp3 files Ok. I
first reported this as bug 1752267 as I thought that the problem was with vlc.
On that bug, it was suggested that the problem is with Pulseaudio.
Just now, I've tried to play sound through my monitor's built in speakers
connected by hdmi (though the monitor displays Ok) with no success even though
the built-in speakers play sound using pavucontrol when testing is invoked.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3.8
ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
Uname: Linux 4.4.0-116-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: john 2410 F pulseaudio
/dev/snd/controlC0: john 2410 F pulseaudio
CurrentDesktop: Unity
Date: Mon Mar 12 11:06:46 2018
InstallationDate: Installed on 2016-12-08 (458 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/04/2015
dmi.bios.vendor: Intel Corp.
dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904
dmi.board.name: NUC5CPYB
dmi.board.vendor: Intel Corporation
dmi.board.version: H61145-404
dmi.chassis.type: 3
dmi.modalias:
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:

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

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

[Touch-packages] [Bug 1734908] Re: systemd-rfkill service times out when a new rfkill device is added

urfkill switch autopkgtest testcases of network manager are passing with this
new systemd still.
(there are other nm regressions in other test cases however)

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

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

Title:
systemd-rfkill service times out when a new rfkill device is added

Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Artful:
Fix Committed

Bug description:
[Impact]

The following issue was observed while running network-
manager=1.8.4-1ubuntu3 autopkgtest on Artful with
systemd=234-2ubuntu12.1:

---
Nov 21 17:00:32 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch
Status...
Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Start
operation timed out. Terminating.
Nov 21 17:01:02 autopkgtest systemd[1]: Failed to start Load/Save RF Kill
Switch Status.
Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Unit entered
failed state.
Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Failed with
result 'timeout'.
---

This happens after the testcase inserts the fake-rfkill module (a
module shipped with network-manager tests that registers a new fake
device with the rfkill subsystem).

On Artful, it causes the network-manager autopkgtest killswitches-no-
urfkill to fail (see bug 1733321). The testcase reveals that when
running network-manager cli to query the status of a WiFi interface
('nmcli radio wifi') it can report the wrong state of the device after
'rfkill block/unblock' is run to change the device 'Soft blocked'
state. This can affect the state of the device presented to the user.

[Fix]

The issue is fixed by the following systemd upstream patches:

---

https://github.com/systemd/systemd/commit/8ec1a07998758f6a85f3ea5bf2ed14d87609398f#diff-275947967677827e2b72930d97f1b8ac

commit 8ec1a07998758f6a85f3ea5bf2ed14d87609398f
Author: S. Fan
Date: Mon Jul 31 05:10:10 2017 -0500

rfkill: fix erroneous behavior when polling the udev monitor
(#6489)

Comparing udev_device_get_sysname(device) and sysname will always return
true. We need to check the device received from udev monitor instead.

Also, fd_wait_for_event() sometimes never exits. Better set a timeout
here.
---

---

https://github.com/systemd/systemd/commit/c7f6ca9379279affa8f22d15fa13063491f86a49#diff-275947967677827e2b72930d97f1b8ac

commit c7f6ca9379279affa8f22d15fa13063491f86a49
Author: Xiang Fan
Date: Wed Aug 9 05:51:53 2017 -0500

rfkill: fix typo (#6574)
---

With the fixes, the output from systemd-rfkill is:

---
Nov 28 15:27:54 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch
Status...
Nov 28 15:27:59 autopkgtest systemd-rfkill[14843]: Timed out waiting for udev
monitor.
Nov 28 15:27:59 autopkgtest systemd[1]: Started Load/Save RF Kill Switch
Status.
---

The patches are needed to fix the ADT tests observed with Artful tests on
ppc64el architecture:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz

[Test Case]

2.1. Download network-manager package source code
$ apt-get source network-manager

2.2. Run killswitches-no-urfkill testcase
$ cd network-manager-1.8.4
$ sudo ./debian/tests/killswitches-no-urfkill

[Regression Potential]

Most of the network-manager and rfkill functionalities that can be
affected by this change are tested by killswitches-no-urfkill
testcase. It covers querying the WiFi device state using nmcli and the
following rfkill commands: list, block and unblock. These have been
verified to be either fixed or not having regressions.

The only rfkill command that is not covered by the testcase is
'event', which listens to rfkill events and display them. I have run
tests manually and verified that it's not affected by these changes.
These are the outputs from the unpatched and patched systemd versions
while running the killswitches-no-urfkill testcase, which adds the
rfkill device, blocks and unbloks it and removes the device (the idx
value is expected to be different):

systemd 234-2ubuntu12.1:
-

[Touch-packages] [Bug 1750973] Re: Program sub menus dark gray on black, thus illegible

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

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 1725921, 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 1725921
   [regression] Combobox menus have gray text on gray background

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

Title:
  Program sub menus dark gray on black, thus illegible

Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  When using a program, for example Libre Writer, when I click on file,
  open, then in the Open menu box I have the opportunity to change the
  file type from "All files" to a specific file type, when I click on
  "All files" the selection list appears. The font color for the
  different file types is a dark grey on a black background making the
  list items illegible. As I move the cursor, the font color and
  background change to "normal" black on a white background but only for
  the item that the cursor is hovering over at that moment. This makes
  the rest of the list impossible to read and moving the cursor slowly
  down the list, pausing to read each item, is a very cumbersome way to
  get things done.

  This doesn't just happen on Libre Writer but also Inkscape, Geeqie,
  and a variety of other programs and their sub menus. The only program
  I could find where this didn't happen was Firefox (58.02). Furthermore
  this happens on 3 different machines, each with a different processor,
  different graphics card and where the machine has multiple monitors,
  it happens on all monitors.

  All machines are running 16.04, one with the latest updates, the
  others slightly behind on updates.

  WORKAROUND: In Settings-Appearance-Theme change the theme from the
  default Ambiance to anything else.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Feb 21 20:57:30 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: sysdig, 0.20.0, 4.4.0-112-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1033]
  InstallationDate: Installed on 2014-04-20 (1404 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=8f4996c0-c2f5-449f-a35c-47f301f66803 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: 970 Extreme3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd10/12/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-x

[Touch-packages] [Bug 1736955] Re: dep8 test systemd-fsckd fails on s390

timedatedPASS
hostnamedPASS
localed-locale   PASS
localed-x11-keymap   PASS
logind   PASS
unit-config  PASS
storage  PASS
networkd-test.py PASS
build-login  PASS
boot-and-servicesPASS
udev PASS
root-unittests   PASS
upstream PASS
logind-kill-off  PASS
boot-smoke   PASS
systemd-fsckdFAIL non-zero exit status 1

ERROR: test_systemd_fsck_with_plymouth_failure (__main__.FsckdTest)
ERROR: test_fsckd_run (__main__.FsckdTest)


Above is improvement over what was previously in artful. The "regression" is 
due to s390x switching on kvm testing.

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

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

Title:
  dep8 test systemd-fsckd fails on s390

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Committed

Bug description:
  The systemd-fsckd test has a constraint of isolation-machine, among
  others. Until recently, that actually prevented it from running on
  s390 because we were using containers for it.

  About 3 weeks ago, apparently we started using VMs for s390 dep8
  tests, so that constraint was finally satisfied and systemd-fsckd
  started to run. And to fail consistently, as can be see in
  http://autopkgtest.ubuntu.com/packages/s/systemd/artful/s390x:

  Traceback (most recent call last):
    File "/tmp/autopkgtest.PrPiv9/build.iis/src/debian/tests/systemd-fsckd", 
line 267, in 
  boot_with_systemd_distro()
    File "/tmp/autopkgtest.PrPiv9/build.iis/src/debian/tests/systemd-fsckd", 
line 243, in boot_with_systemd_distro
  enable_plymouth()
    File "/tmp/autopkgtest.PrPiv9/build.iis/src/debian/tests/systemd-fsckd", 
line 224, in enable_plymouth
  plymouth_enabled = 'splash' in open('/boot/grub/grub.cfg').read()
  FileNotFoundError: [Errno 2] No such file or directory: '/boot/grub/grub.cfg'

  There is no grub for s390, so this test must be adjusted or skipped in
  that architecture.

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

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

[Touch-packages] [Bug 424215] Re: Bluetooth mouse usage makes A2DP audio stutter

This bug is closed, rightly or wrongly. And has been closed for several
years.

If you have any ongoing issues then please log a new bug by running this
command:

  ubuntu-bug bluez

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

Title:
  Bluetooth mouse usage makes A2DP audio stutter

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: bluez

  When I use my Bluetooth A2DP headset (Philips SHB7102) together with
  my mouse (Lenovo Bluetooth Laser Mouse), I notice this:

  Whenever I leave the mouse still for a few seconds (it seems to enter
  some kind of lower-power-mode) and then start to move it, my music
  most of the time skips for a second. This makes using these two
  bluetooth devices together quite annoying...

  The adapter is a Lenovo "ThinkPad Bluetooth with Enhanced Data Rate
  II" (Bus 004 Device 005: ID 0a5c:2145 Broadcom Corp.)

  I am running current karmic amd64 (linux 2.6.31-9).

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

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

[Touch-packages] [Bug 1734410] Re: systemd: handle undelegated cgroup2 hierarchy

@cbrauner

Could you please verify this bug report for me, and state the versions
of systemd used on the host / container / subcontainter?

Otherwise, I might be forced to drop this patch.

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

Title:
  systemd: handle undelegated cgroup2 hierarchy

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Confirmed
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * When a container is presented with a unified cgroup hierarchy,
  which is not properly delegated, systemd should not attempt (and fail)
  to use. This improves compatibility of xenial containers running on
  unified cgroup hierarchy hosts.

  [Test Case]

   * Xenial containers should boot, with non-writable unified cgroup
  hierarchy hosts.

  [Regression Potential]

   * unified cgroup hierarchy is not in use by default on xenial hosts,
  thus this is forward compatibility improvment with e.g. bionic hosts
  running xenial containers.

  [Other Info]
   
   * Original bug report

  Hey everyone,

  Current systemd versions all fail when the unified cgroup hierarchy is
  not-writable. This is especially problematic in containers where the
  systemd administrator might decide to not delegate the unified
  hierarchy or when running with a liblxc driver that doesn't yet know
  how to handle the unified cgroup hierarchy. I've pushed patches to
  systemd upstream that let systemd ingnore the non-delegated unified
  hierarchy. The relevant commits are:

  e07aefbd675b651f8d45b5fb458f2747b04d6e04
  2d56b80a1855836abf1d7458394c345ad9d55382
  1ff654e28b7b8e7d0a0be33522a84069ac6b07c0

  These patches will be in 236 but should be backported from xenial
  upwards.

  Christian

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

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

[Touch-packages] [Bug 696435] Re: wait-for-root fails to detect nbd root

** Branch unlinked: lp:~xnox/britney/custom-kernels-cannot-pass

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

Title:
  wait-for-root fails to detect nbd root

Status in linux package in Ubuntu:
  Fix Released
Status in nbd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  Kernel does not generate any events when ndb-client connects /dev/nbd0 
devices, therefore it is impossible to monitor/react to the state of /dev/nbd0.

  [Fix]
  Generate change uevent when size of /dev/nbd0 changes

  [Testcase]
  * Start udevadm monitor
  * modprobe nbd
  * use ndb-client to connect something to /dev/nbd0
  * observe that there are change udev events generated on /dev/nbd0 itself

  [Regression Potential]
  There is no change to existing uevents, or their ordering.
  There is now an addition change event which will cause systemd to mark ndb 
devices as ready and trigger appropriate actions

  [Original Bug Report]

  When using an nbd root, wait-for-root blocks for 30 seconds before
  booting continues successfully.

  Using Ubuntu Natty, related packages versions:
  nbd-client 1:2.9.16-6ubuntu1
  initramfs-tools 0.98.1ubuntu9

  The wait-for-root call from /usr/share/initramfs-tools/scripts/local:
   while [ -z "${FSTYPE}" ]; do
    FSTYPE=$(wait-for-root "${ROOT}" ${ROOTDELAY:-30})

    # Run failure hooks, hoping one of them can fix up the system
    # and we can restart the wait loop.  If they all fail, abort
    # and move on to the panic handler and shell.
    if [ -z "${FSTYPE}" ] && ! try_failure_hooks; then
     break
    fi
   done

  I replaced wait-for-root with a sh script that did `set >&2`, here are the 
relevant environment variables at the time wait-for-root was called:
  ROOT='/dev/nbd0'
  ROOTDELAY=''
  ROOTFLAGS=''
  ROOTFSTYPE=''
  nbdroot='192.168.0.1,2011'

  It's probably worth noting that "nbd0: unknown partition table" was
  displayed asynchronously 1-2 seconds after wait-for-root was invoked
  and while it was still waiting. But I tried adding a "sleep 5" as the
  last line of local-top/nbd, so that the nbd message was displayed a
  lot before wait-for-root was called, and it didn't make a difference.
  So I don't think a race condition is involved in this problem.

  Temporarily I'm passing rootdelay=1 in the kernel command line to work
  around the problem.

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

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

[Touch-packages] [Bug 1615685] Re: systemd-analyze stats for kernel startup time looks suspect

Systems that report more times, run systemd in the initrd.

We do not run systemd in the initrd.

To save time on the boot up, we are working on enabling more systems
boot initramfs-less, with an automatic fallback to a boot with
initramfs. In the near future most cloud instances, and some bare metal
systems will be doing that by default.

I will check if it is at all possible to fake the timings in the
Ubuntu's initramfs, to supply timings for systemd-analyze.

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

Title:
  systemd-analyze stats for kernel startup time looks suspect

Status in systemd package in Ubuntu:
  New

Bug description:
  I've instrumented a kernel so I can clearly see when processes start
  and exit, this allows me to see when exactly the kernel has handed off
  control to userspace.  The time the kernel actually takes to
  initialize compared to the time systemd-analyze reports are different.

  $ systemd-analyze 
  Startup finished in 16.878s (kernel) + 43.152s (userspace) = 1min 30ms

  For example:

  [2.286330] Freeing unused kernel memory: 1532K (b1755000 - 
b18d4000)
  [2.296300] Write protecting the kernel read-only data: 12288k
  [2.304356] Freeing unused kernel memory: 1872K (9d9c6e42c000 - 
9d9c6e60)
  [2.317659] Freeing unused kernel memory: 1208K (9d9c6e8d2000 - 
9d9c6ea0)
  [2.344896] x86/mm: Checked W+X mappings: passed, no W+X pages found.
  [2.368095] exec: 1 (swapper/0) -> /init
  [2.377284] _do_fork: 1 init
  [2.381933] exit 53 init
  [2.386444] _do_fork: 1 init
  [2.390741] exit 54 init
  [2.394899] _do_fork: 1 init

  and we have the initramfs initialization occurring, and then finally
  systemd starts:

  [   16.571630] exec: 1 (run-init) -> /sbin/init
  [   17.287342] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN)
  [   17.307892] systemd[1]: Detected virtualization microsoft.
  [   17.314765] systemd[1]: Detected architecture x86-64.
  [   17.421589] systemd[1]: Set hostname to .

  So it seems that systemd is accounting initramfs time in the kernel
  time stats.  It would be preferable to be able to report the kernel
  init time, the initramfs time and the userspace time rather just
  kernel + userspace.

  As it stands, the kernel passed off control to systemd at 16.571630
  seconds, so I have no no idea why systemd is reporting 16.878 seconds.

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

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

[Touch-packages] [Bug 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string

** Branch unlinked: lp:~xnox/britney/custom-kernels-cannot-pass

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

Title:
  fixrtc script does not catch "Last mount time: n/a" string

Status in Snappy:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools-ubuntu-core package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in initramfs-tools-ubuntu-core source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Artful:
  Fix Committed
Status in initramfs-tools-ubuntu-core source package in Artful:
  New

Bug description:
  [TEST CASE]
  * this will be tested by the snappy team
  * without this fix the dragonboard will not boot on a freshly written image

  [REGRESSION POTENTIAL]
  * low as it only fixes an invalid string

  trying to boot a new dragonboard image results in:

  error: assertion is signed with expired public key
  "-CvQKAwRQ5h3Ffn10FILJoEZUXOv6km9FwA80-Rcj-f-6jadQ89VRswHNiEB9Lxk" by
  canonical

  this is due to a clock skew that should normally be catched by the
  fixrtc script in the initrd.

  the script is supposed to check the last mount time of the writable
  disk (SD card) and if this does not exist, fall back to the filesystem
  creation time ...

  in former versions of mkfs.ext4 the last mount time filed was simply
  left empty, so this fallback worked fine ... in xenial the fields now
  look like:

  Filesystem created:   Tue Sep 13 17:32:20 2016
  Last mount time:  n/a
  Last write time:  Tue Sep 13 17:32:20 2016

  due to the script running with "set -e" it falls over on the "n/a" and
  exists before falling back to creation time, there needs to be a check
  added for the "n/a" string now.

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

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

[Touch-packages] [Bug 1736955] Re: dep8 test systemd-fsckd fails on s390

It's better, some of the unit tests for fsckd are now passing, however,
not all. This is improvement. The failing tests appear to be racy.

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

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

Title:
  dep8 test systemd-fsckd fails on s390

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Committed

Bug description:
  The systemd-fsckd test has a constraint of isolation-machine, among
  others. Until recently, that actually prevented it from running on
  s390 because we were using containers for it.

  About 3 weeks ago, apparently we started using VMs for s390 dep8
  tests, so that constraint was finally satisfied and systemd-fsckd
  started to run. And to fail consistently, as can be see in
  http://autopkgtest.ubuntu.com/packages/s/systemd/artful/s390x:

  Traceback (most recent call last):
    File "/tmp/autopkgtest.PrPiv9/build.iis/src/debian/tests/systemd-fsckd", 
line 267, in 
  boot_with_systemd_distro()
    File "/tmp/autopkgtest.PrPiv9/build.iis/src/debian/tests/systemd-fsckd", 
line 243, in boot_with_systemd_distro
  enable_plymouth()
    File "/tmp/autopkgtest.PrPiv9/build.iis/src/debian/tests/systemd-fsckd", 
line 224, in enable_plymouth
  plymouth_enabled = 'splash' in open('/boot/grub/grub.cfg').read()
  FileNotFoundError: [Errno 2] No such file or directory: '/boot/grub/grub.cfg'

  There is no grub for s390, so this test must be adjusted or skipped in
  that architecture.

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

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

[Touch-packages] [Bug 1749261] Re: Add amd64/i386 retpoline support

This bug was fixed in the package gcc-4.8 - 4.8.5-4ubuntu8

---
gcc-4.8 (4.8.5-4ubuntu8) bionic; urgency=medium

  [ Matthias Klose ]
  * Stop build gcj in current distro releases. Addresses: #892536.
  * Split off the documentation part from the retpoline patches.
  * Fix build dependency on realpath.

  [ Steve Beattie ]
  * Add retpoline support for x86 via adding -mindirect-branch=,
-mindirect-branch-register, and -mfunction-return= support
(LP: #1749261)
- 0001-i386-Move-struct-ix86_frame-to-machine_function.diff,
  0002-i386-Use-reference-of-struct-ix86_frame-to-avoid-cop.diff,
  0003-i386-Use-const-reference-of-struct-ix86_frame-to-avo.diff,
  0004-x86-Add-mindirect-branch.diff,
  0005-x86-Add-mfunction-return.diff,
  0006-x86-Add-mindirect-branch-register.diff,
  0007-x86-Add-V-register-operand-modifier.diff,
  0008-x86-Disallow-mindirect-branch-mfunction-return-with-.diff,
  0009-Use-INVALID_REGNUM-in-indirect-thunk-processing.diff:
  implement -mindirect-branch=
  with attribute support, -mindirect-branch-register, and
  -mfunction-return= with
  attribute support. Thanks to H.J. Lu.

 -- Matthias Klose   Mon, 19 Mar 2018 16:12:10 +0800

** Changed in: gcc-4.8 (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Add amd64/i386 retpoline support

Status in gcc-4.8 package in Ubuntu:
  Fix Released
Status in gcc-4.8 source package in Trusty:
  Fix Released

Bug description:
  To mitigate Spectre Variant 2, gcc needs to have retpoline support
  (-mindirect-branch and -mfunction-return arguments on amd64 and i386).

  Packages with this will go into the proposed pockets but need to be
  published in the -security pockets for their respective releases.

  Patches for gcc-4.8 were pulled from H.J. Lu's backport branch to 4.9,
  available at https://github.com/hjl-tools/gcc/tree/hjl/indirect/gcc-
  4_9-branch/master . Upstream GCC does not seem to be applying patches
  to anything older than the gcc-6-branch. H.J. Lu is the author of the
  upstream retpoline commits as well.

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

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

[Touch-packages] [Bug 1615685] Re: systemd-analyze stats for kernel startup time looks suspect

2018-03-19 Thread Chris Cheney

Note firmware and loader times only show up when using UEFI.

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

Title:
  systemd-analyze stats for kernel startup time looks suspect

Status in systemd package in Ubuntu:
  New

Bug description:
  I've instrumented a kernel so I can clearly see when processes start
  and exit, this allows me to see when exactly the kernel has handed off
  control to userspace.  The time the kernel actually takes to
  initialize compared to the time systemd-analyze reports are different.

  $ systemd-analyze 
  Startup finished in 16.878s (kernel) + 43.152s (userspace) = 1min 30ms

  For example:

  [2.286330] Freeing unused kernel memory: 1532K (b1755000 - 
b18d4000)
  [2.296300] Write protecting the kernel read-only data: 12288k
  [2.304356] Freeing unused kernel memory: 1872K (9d9c6e42c000 - 
9d9c6e60)
  [2.317659] Freeing unused kernel memory: 1208K (9d9c6e8d2000 - 
9d9c6ea0)
  [2.344896] x86/mm: Checked W+X mappings: passed, no W+X pages found.
  [2.368095] exec: 1 (swapper/0) -> /init
  [2.377284] _do_fork: 1 init
  [2.381933] exit 53 init
  [2.386444] _do_fork: 1 init
  [2.390741] exit 54 init
  [2.394899] _do_fork: 1 init

  and we have the initramfs initialization occurring, and then finally
  systemd starts:

  [   16.571630] exec: 1 (run-init) -> /sbin/init
  [   17.287342] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN)
  [   17.307892] systemd[1]: Detected virtualization microsoft.
  [   17.314765] systemd[1]: Detected architecture x86-64.
  [   17.421589] systemd[1]: Set hostname to .

  So it seems that systemd is accounting initramfs time in the kernel
  time stats.  It would be preferable to be able to report the kernel
  init time, the initramfs time and the userspace time rather just
  kernel + userspace.

  As it stands, the kernel passed off control to systemd at 16.571630
  seconds, so I have no no idea why systemd is reporting 16.878 seconds.

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

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

[Touch-packages] [Bug 1615685] Re: systemd-analyze stats for kernel startup time looks suspect

2018-03-19 Thread Chris Cheney

Its also not clear why Ubuntu's systemd-analyze doesn't report more than
just kernel + userspace times even on Ubuntu 18.04. Both CentOS 7 and
Fedora 27 report times properly, which are using older versions of
systemd.

---

CentOS 7 - systemd-219-42.el7_4.7.x86_64

$ systemd-analyze time
Startup finished in 846ms (kernel) + 2.678s (initrd) + 2min 29.307s (userspace) 
= 2min 32.832s

---

Fedora 27 - systemd-234-10.git5f8984e.fc27.x86_64

$ systemd-analyze time
Startup finished in 21.114s (firmware) + 2.086s (loader) + 1.131s (kernel) + 
8.841s (initrd) + 6.125s (userspace) = 39.298s

---

Ubuntu systemd 237-3ubuntu4

$ systemd-analyze time
Startup finished in 2.561s (kernel) + 12.868s (userspace) = 15.429s
graphical.target reached after 12.842s in userspace

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

Title:
  systemd-analyze stats for kernel startup time looks suspect

Status in systemd package in Ubuntu:
  New

Bug description:
  I've instrumented a kernel so I can clearly see when processes start
  and exit, this allows me to see when exactly the kernel has handed off
  control to userspace.  The time the kernel actually takes to
  initialize compared to the time systemd-analyze reports are different.

  $ systemd-analyze 
  Startup finished in 16.878s (kernel) + 43.152s (userspace) = 1min 30ms

  For example:

  [2.286330] Freeing unused kernel memory: 1532K (b1755000 - 
b18d4000)
  [2.296300] Write protecting the kernel read-only data: 12288k
  [2.304356] Freeing unused kernel memory: 1872K (9d9c6e42c000 - 
9d9c6e60)
  [2.317659] Freeing unused kernel memory: 1208K (9d9c6e8d2000 - 
9d9c6ea0)
  [2.344896] x86/mm: Checked W+X mappings: passed, no W+X pages found.
  [2.368095] exec: 1 (swapper/0) -> /init
  [2.377284] _do_fork: 1 init
  [2.381933] exit 53 init
  [2.386444] _do_fork: 1 init
  [2.390741] exit 54 init
  [2.394899] _do_fork: 1 init

  and we have the initramfs initialization occurring, and then finally
  systemd starts:

  [   16.571630] exec: 1 (run-init) -> /sbin/init
  [   17.287342] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN)
  [   17.307892] systemd[1]: Detected virtualization microsoft.
  [   17.314765] systemd[1]: Detected architecture x86-64.
  [   17.421589] systemd[1]: Set hostname to .

  So it seems that systemd is accounting initramfs time in the kernel
  time stats.  It would be preferable to be able to report the kernel
  init time, the initramfs time and the userspace time rather just
  kernel + userspace.

  As it stands, the kernel passed off control to systemd at 16.571630
  seconds, so I have no no idea why systemd is reporting 16.878 seconds.

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

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

[Touch-packages] [Bug 1756998] Re: GPU HANG: ecode 9:0:0x84dfbffc, in Xorg [1250], reason: Hang on rcs0, action: reset drm/i915: Resetting chip after gpu hang RC6 on

2018-03-19 Thread Grek-336

** Attachment added: "lspci-vvnn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756998/+attachment/5084481/+files/lspci-vvnn.log

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

** No longer affects: linux (Ubuntu)

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

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

Title:
  GPU HANG: ecode 9:0:0x84dfbffc, in Xorg [1250], reason: Hang on rcs0,
  action: reset  drm/i915: Resetting chip after gpu hang RC6 on

Status in libdrm package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  This error message is in syslog when the Desktop freeze before the
  Display goes black and the login screen came up.

  This apparently happens without any apparent connection. Sometimes not
  for days even though the CPU is 100% full all the time, then again
  after 20-30 minutes several times in a row.

  lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  mesa 17.2.8-0ubuntu0~16.04.1
  libdrm 2.4.83-1~16.04.1

  
  Mar 19 20:12:22 michael-ThinkPad-E470 kernel: [255789.072708] [drm] GPU HANG: 
ecode 9:0:0x84dfbffc, in Xorg [1250], reason: Hang on rcs0, action: reset
  Mar 19 20:12:22 michael-ThinkPad-E470 kernel: [255789.072763] drm/i915: 
Resetting chip after gpu hang
  Mar 19 20:12:22 michael-ThinkPad-E470 kernel: [255789.073059] [drm] RC6 on
  Mar 19 20:12:30 michael-ThinkPad-E470 kernel: [255797.047275] drm/i915: 
Resetting chip after gpu hang
  Mar 19 20:12:30 michael-ThinkPad-E470 kernel: [255797.047556] [drm] RC6 on
  Mar 19 20:12:43 michael-ThinkPad-E470 kernel: [255810.039289] drm/i915: 
Resetting chip after gpu hang
  Mar 19 20:12:43 michael-ThinkPad-E470 kernel: [255810.039429] [drm] RC6 on
  Mar 19 20:12:55 michael-ThinkPad-E470 kernel: [255822.007247] drm/i915: 
Resetting chip after gpu hang
  Mar 19 20:12:55 michael-ThinkPad-E470 kernel: [255822.007407] [drm] RC6 on
  Mar 19 20:13:03 michael-ThinkPad-E470 kernel: [255830.071164] drm/i915: 
Resetting chip after gpu hang
  Mar 19 20:13:03 michael-ThinkPad-E470 kernel: [255830.071304] [drm] RC6 on
  Mar 19 20:13:25 michael-ThinkPad-E470 gnome-session-binary[31279]: Entering 
running state

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

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

[Touch-packages] [Bug 1732002] Re: cloud images in lxc get ipv6 address

2018-03-19 Thread Ryan Harper

It would be nice for both nplan and networkd to accept a tri-state:

accept-ra: [off|on|kernel]

I think that would make it clear rather than an unset value to indicate
that it's controlled by the kernel.

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

Title:
  cloud images in lxc get ipv6 address

Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I noticed that lxd (lxc list) reports that an lxc container has an
  ipv6 address in artful or bionic.  It does not list this in xenial or
  zesty.  I suspect this change occurred in the switch over to
  netplan/networkd.

  This may at first seem harmless or even desired, but note that the
  user configuration did not request ipv6 config, so its presence is a
  bug.

  $ for rel in xenial zesty artful bionic; do
 lxc launch ubuntu-daily:$rel $rel-demo; done
  Creating xenial-demo
  Starting xenial-demo
  ..
  Creating bionic-demo
  Starting bionic-demo

  
  $ sleep 10
  $ lxc list
  $ lxc list
  
+-+-+--+++---+
  |NAME |  STATE  | IPV4 |  IPV6
  |TYPE| SNAPSHOTS |
  
+-+-+--+++---+
  | artful-demo | RUNNING | 10.75.205.208 (eth0) | 
fd42:eee5:7c43:3d62:3a42:611c:3f6f:1184 (eth0) | PERSISTENT | 0 |
  
+-+-+--+++---+
  | bionic-demo | RUNNING | 10.75.205.187 (eth0) | 
fd42:eee5:7c43:3d62:6f4:155b:39cc:fc3d (eth0)  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | xenial-demo | RUNNING | 10.75.205.143 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | zesty-demo  | RUNNING | 10.75.205.123 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+

  ## Here is the config that was provided by lxd
  $ lxc exec bionic-demo cat /var/lib/cloud/seed/nocloud-net/network-config
  version: 1
  config:
  - type: physical
name: eth0
subnets:
- type: dhcp
  control: auto

  ## Here is the config that cloud-init rendered.
  $ lxc exec bionic-demo -- grep -v '^#' /etc/netplan/50-cloud-init.yaml
  network:
  version: 2
  ethernets:
  eth0:
  dhcp4: true

  $ lxc exec bionic-demo cat /run/systemd/network/10-netplan-eth0.network
  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4

  [DHCP]
  UseMTU=true
  RouteMetric=100

  $ lxc exec bionic-demo  -- systemctl status --no-pager --full systemd-networkd
  ● systemd-networkd.service - Network Service
 Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Mon 2017-11-13 18:37:34 UTC; 8min ago
   Docs: man:systemd-networkd.service(8)
   Main PID: 118 (systemd-network)
 Status: "Processing requests..."
  Tasks: 1 (limit: 4915)
 Memory: 2.0M
CPU: 19ms
 CGroup: /system.slice/systemd-networkd.service
 └─118 /lib/systemd/systemd-networkd

  Nov 13 18:37:34 bionic-demo systemd[1]: Starting Network Service...
  Nov 13 18:37:34 bionic-demo systemd-networkd[118]: eth0: Gained IPv6LL
  Nov 13 18:37:34 bionic-demo systemd-networkd[118]: Enumeration completed
  Nov 13 18:37:34 bionic-demo systemd[1]: Started Network Service.
  Nov 13 18:37:37 bionic-demo systemd-networkd[118]: eth0: DHCPv6 address 
fd42:eee5:7c43:3d62:6f4:155b:39cc:fc3d/128 timeout preferred 3600 valid 3600
  Nov 13 18:37:37 bionic-demo systemd-networkd[118]: eth0: DHCPv4 address 
10.75.205.187/24 via 10.75.205.1
  Nov 13 18:37:37 bionic-demo systemd-networkd[118]: Not connected to system 
bus, ignoring transient hostname.
  Nov 13 18:37:39 bionic-demo systemd-networkd[118]: eth0: Configured
  Nov 13 18:38:09 bionic-demo systemd-networkd[118]: Could not set hostname: 
Method call timed out

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nplan 0.30
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Mon Nov 13 18:27:53 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: nplan
  UpgradeStatus: No upgrade log present (probably fresh

[Touch-packages] [Bug 1732002] Re: cloud images in lxc get ipv6 address

2018-03-19 Thread Ryan Harper

After some discussion, it appears that networkd is kinda of making a
boolean (on|off) for IPV6 RA, when it's really a tri-state
(on|off|kernel).

Upstream networkd indicates there is a tri-state; like so:

Enable or disable IPv6 Router Advertisement (RA) reception support for
the interface. Takes a boolean parameter. If true, RAs are accepted; if
false, RAs are ignored, independently of the local forwarding state.
When not set, the kernel default is used, and RAs are accepted only when
local forwarding is disabled for that interface. When RAs are accepted,
they may trigger the start of the DHCPv6 client if the relevant flags
are set in the RA data, or if no routers are found on the link.

While in netplan, we've only a boolean, which could be fine, except
netplan defaults to AcceptRA=True which means we have no way of allowing
the kernel configuration to work.

Netplan needs to know if the yaml includes an accept-ra key, and if so,
uses the value set (off or on); but if the yaml does not specify an
accept-ra key, it should *NOT* render a default value.

This allows hosts to defer the the kernel settings.  This key was
introduced as away to resolve a bug where "unconfigured" interfaces got
an IPV6 address due to kernel setting and an IPV6 router present.

https://bugs.launchpad.net/maas/+bug/1655440

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

Title:
  cloud images in lxc get ipv6 address

Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I noticed that lxd (lxc list) reports that an lxc container has an
  ipv6 address in artful or bionic.  It does not list this in xenial or
  zesty.  I suspect this change occurred in the switch over to
  netplan/networkd.

  This may at first seem harmless or even desired, but note that the
  user configuration did not request ipv6 config, so its presence is a
  bug.

  $ for rel in xenial zesty artful bionic; do
 lxc launch ubuntu-daily:$rel $rel-demo; done
  Creating xenial-demo
  Starting xenial-demo
  ..
  Creating bionic-demo
  Starting bionic-demo

  
  $ sleep 10
  $ lxc list
  $ lxc list
  
+-+-+--+++---+
  |NAME |  STATE  | IPV4 |  IPV6
  |TYPE| SNAPSHOTS |
  
+-+-+--+++---+
  | artful-demo | RUNNING | 10.75.205.208 (eth0) | 
fd42:eee5:7c43:3d62:3a42:611c:3f6f:1184 (eth0) | PERSISTENT | 0 |
  
+-+-+--+++---+
  | bionic-demo | RUNNING | 10.75.205.187 (eth0) | 
fd42:eee5:7c43:3d62:6f4:155b:39cc:fc3d (eth0)  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | xenial-demo | RUNNING | 10.75.205.143 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | zesty-demo  | RUNNING | 10.75.205.123 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+

  ## Here is the config that was provided by lxd
  $ lxc exec bionic-demo cat /var/lib/cloud/seed/nocloud-net/network-config
  version: 1
  config:
  - type: physical
name: eth0
subnets:
- type: dhcp
  control: auto

  ## Here is the config that cloud-init rendered.
  $ lxc exec bionic-demo -- grep -v '^#' /etc/netplan/50-cloud-init.yaml
  network:
  version: 2
  ethernets:
  eth0:
  dhcp4: true

  $ lxc exec bionic-demo cat /run/systemd/network/10-netplan-eth0.network
  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4

  [DHCP]
  UseMTU=true
  RouteMetric=100

  $ lxc exec bionic-demo  -- systemctl status --no-pager --full systemd-networkd
  ● systemd-networkd.service - Network Service
 Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Mon 2017-11-13 18:37:34 UTC; 8min ago
   Docs: man:systemd-networkd.service(8)
   Main PID: 118 (systemd-network)
 Status: "Processing requests..."
  Tasks: 1 (limit: 4915)
 Memory: 2.0M
CPU: 19ms
 CGroup: /system.slice/systemd-networkd.service
 └─118 /lib/systemd/systemd-networkd

  Nov 13 18:37:34 bionic-demo systemd[1]: Starting Network Service...
  Nov 13 18:37:34 bionic-demo systemd-networkd[118]: eth0:

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

2018-03-19 Thread Seth Arnold

Hello Rocko,

Can you try the following?

sudo apparmor_parser --replace /etc/apparmor.d/usr.bin.webbrowser-app
sudo apparmor_parser --replace 
/etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor

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:
  New

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 1756998] Re: GPU HANG: ecode 9:0:0x84dfbffc, in Xorg [1250], reason: Hang on rcs0, action: reset drm/i915: Resetting chip after gpu hang RC6 on

2018-03-19 Thread Grek-336

Setting the kernel parameter intel_iommu = off was the first attempt to
solve the problem.

The error also occurs without this kernel parameter

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

Title:
  GPU HANG: ecode 9:0:0x84dfbffc, in Xorg [1250], reason: Hang on rcs0,
  action: reset  drm/i915: Resetting chip after gpu hang RC6 on

Status in libdrm package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  This error message is in syslog when the Desktop freeze before the
  Display goes black and the login screen came up.

  This apparently happens without any apparent connection. Sometimes not
  for days even though the CPU is 100% full all the time, then again
  after 20-30 minutes several times in a row.

  lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  mesa 17.2.8-0ubuntu0~16.04.1
  libdrm 2.4.83-1~16.04.1

  
  Mar 19 20:12:22 michael-ThinkPad-E470 kernel: [255789.072708] [drm] GPU HANG: 
ecode 9:0:0x84dfbffc, in Xorg [1250], reason: Hang on rcs0, action: reset
  Mar 19 20:12:22 michael-ThinkPad-E470 kernel: [255789.072763] drm/i915: 
Resetting chip after gpu hang
  Mar 19 20:12:22 michael-ThinkPad-E470 kernel: [255789.073059] [drm] RC6 on
  Mar 19 20:12:30 michael-ThinkPad-E470 kernel: [255797.047275] drm/i915: 
Resetting chip after gpu hang
  Mar 19 20:12:30 michael-ThinkPad-E470 kernel: [255797.047556] [drm] RC6 on
  Mar 19 20:12:43 michael-ThinkPad-E470 kernel: [255810.039289] drm/i915: 
Resetting chip after gpu hang
  Mar 19 20:12:43 michael-ThinkPad-E470 kernel: [255810.039429] [drm] RC6 on
  Mar 19 20:12:55 michael-ThinkPad-E470 kernel: [255822.007247] drm/i915: 
Resetting chip after gpu hang
  Mar 19 20:12:55 michael-ThinkPad-E470 kernel: [255822.007407] [drm] RC6 on
  Mar 19 20:13:03 michael-ThinkPad-E470 kernel: [255830.071164] drm/i915: 
Resetting chip after gpu hang
  Mar 19 20:13:03 michael-ThinkPad-E470 kernel: [255830.071304] [drm] RC6 on
  Mar 19 20:13:25 michael-ThinkPad-E470 gnome-session-binary[31279]: Entering 
running state

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

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

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

2018-03-19 Thread Phelps Scofield

** Description changed:

- I start the system normally and after an hour or more the system freezes
+ Eu inicio o sistema normalmente no caso o Ubuntu Studio 16.04, e depois
+ de uma hora ou mais o sistema simplesmente congela, só me restando
+ reiniciar o Ubuntu.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-lowlatency 4.13.13
  Uname: Linux 4.13.0-37-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Mar 19 14:13:25 2018
  InstallationDate: Installed on 2018-03-05 (14 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  ProcEnviron:
-  LANGUAGE=pt_BR:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=pt_BR.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=pt_BR:
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=pt_BR.UTF-8
+  SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Eu inicio o sistema normalmente no caso o Ubuntu Studio 16.04, e
  depois de uma hora ou mais o sistema simplesmente congela, só me
  restando reiniciar o Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-lowlatency 4.13.13
  Uname: Linux 4.13.0-37-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Mar 19 14:13:25 2018
  InstallationDate: Installed on 2018-03-05 (14 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  ProcEnviron:
   LANGUAGE=pt_BR:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 40189] Re: [SRU] [xenial] autofs needs to be restarted to pick up some shares

2018-03-19 Thread Tronde

Ok, I'm lost. Today I've checked in another Xenial with autofs
5.1.1-1ubuntu3.1. Kernel is 4.4.0-116-generic as in the system of my
last post. But in this system I have to restart autofs.service each time
after a (re)boot otherwise I cannot access the shares. I really don't
get it.

Maybe some other users could try to reproduce the problem.

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

Title:
  [SRU] [xenial] autofs needs to be restarted to pick up some shares

Status in autofs package in Ubuntu:
  Fix Released
Status in autofs5 package in Ubuntu:
  Invalid
Status in upstart package in Ubuntu:
  Invalid
Status in autofs source package in Xenial:
  Incomplete

Bug description:
  I am using autofs to access shares on a Windows XP machine from a
  Kubuntu AMD64 machine.  The problems applies in both Breezy and
  Dapper.

  EDIT:  confirmed with similar configuration on Intrepid with a NetApp
  filer hosting NFS.  Server OS removed from summary.

  When I first try to access the mount point via cd or in Konqueror it
  does not exist.  However,  if I then restart autofs
  (/etc/init.d/autofs restart) everythin then works OK.  My config files
  are:

  auto.master

  #
  # $Id: auto.master,v 1.3 2003/09/29 08:22:35 raven Exp $
  #
  # Sample auto.master file
  # This is an automounter map and it has the following format
  # key [ -mount-options-separated-by-comma ] location
  # For details of the format look at autofs(5).
  #/misc/etc/auto.misc --timeout=60
  #/misc/etc/auto.misc
  #/net /etc/auto.net

  /petunia /etc/petunia.misc --timeout=60

  
  petunia.misc

  #
  # $Id: auto.misc,v 1.2 2003/09/29 08:22:35 raven Exp $
  #
  # This is an automounter map and it has the following format
  # key [ -mount-options-separated-by-comma ] location
  # Details may be found in the autofs(5) manpage

  cd  -fstype=iso9660,ro,nosuid,nodev :/dev/cdrom

  tony  -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 
://192.168.1.2/tony
  chris -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 
://192.168.1.2/chris
  shared-fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 
://192.168.1.2/SharedDocs
  linuxbackups  -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 
://192.168.1.2/linuxbackups

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

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

[Touch-packages] [Bug 1756516] Re: update libvorbis to 1.3.6

2018-03-19 Thread Seth Arnold

** Information type changed from Private Security to Public Security

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

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

Title:
  update libvorbis to 1.3.6

Status in libvorbis package in Ubuntu:
  Confirmed

Bug description:
  libvorbis 1.3.6 (2018-03-16) -- "Xiph.Org libVorbis I 20180316 (Now
  100% fewer shells)"

  * Fix CVE-2018-5146 - out-of-bounds write on codebook decoding.
  * Fix CVE-2017-14632 - free() on unitialized data
  * Fix CVE-2017-14633 - out-of-bounds read
  * Fix bitrate metadata parsing.
  * Fix out-of-bounds read in codebook parsing.
  * Fix residue vector size in Vorbis I spec.
  * Appveyor support
  * Travis CI support
  * Add secondary CMake build system.
  * Build system fixes

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

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

[Touch-packages] [Bug 1756972] [NEW] RM: gcc-4.8: no longer used

Public bug reported:

With the latest round of removals for Ubuntu Touch-related packages from
bionic, gcc-4.8 no longer has any non-alternative reverse-depends.

$ 
liblist='lib(x32|32|64|sf)?(gomp1|quadmath0|atomic1|itm1|objc4|stdc\+\+6|gfortran3|tsan0)'
$ rmadison -s bionic -S gcc-4.8 | grep -E "\b$liblist[[:space:]]"
$ reverse-depends src:gcc-4.8 | grep -vE "\b$liblist\)"
Reverse-Depends
===
* gcc-4.8-doc   (for gcc-4.8-base)
* libboost1.62-dev  (for libstdc++-4.8-dev)
* libboost1.65-dev  (for libstdc++-4.8-dev)
* nvidia-cuda-toolkit [amd64 ppc64el]  (for gcc-4.8)
* nvidia-cuda-toolkit [amd64 ppc64el]  (for g++-4.8)

Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
$

We should drop it from the archive for 18.04.

** Affects: gcc-4.8 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  RM: gcc-4.8: no longer used

Status in gcc-4.8 package in Ubuntu:
  New

Bug description:
  With the latest round of removals for Ubuntu Touch-related packages
  from bionic, gcc-4.8 no longer has any non-alternative reverse-
  depends.

  $ 
liblist='lib(x32|32|64|sf)?(gomp1|quadmath0|atomic1|itm1|objc4|stdc\+\+6|gfortran3|tsan0)'
  $ rmadison -s bionic -S gcc-4.8 | grep -E "\b$liblist[[:space:]]"
  $ reverse-depends src:gcc-4.8 | grep -vE "\b$liblist\)"
  Reverse-Depends
  ===
  * gcc-4.8-doc   (for gcc-4.8-base)
  * libboost1.62-dev  (for libstdc++-4.8-dev)
  * libboost1.65-dev  (for libstdc++-4.8-dev)
  * nvidia-cuda-toolkit [amd64 ppc64el]  (for gcc-4.8)
  * nvidia-cuda-toolkit [amd64 ppc64el]  (for g++-4.8)

  Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
  $

  We should drop it from the archive for 18.04.

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

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

[Touch-packages] [Bug 1756502] Re: package libjpeg8 8c-2ubuntu8 [modified: usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright] failed to install/upgrade: trying to overwrite s

2018-03-19 Thread 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 libjpeg8-empty in Ubuntu.
https://bugs.launchpad.net/bugs/1756502

Title:
  package libjpeg8 8c-2ubuntu8 [modified:
  usr/share/doc/libjpeg8/changelog.Debian.gz
  usr/share/doc/libjpeg8/copyright] failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libjpeg8/copyright', which is
  different from other instances of package libjpeg8:i386

Status in libjpeg8-empty package in Ubuntu:
  New

Bug description:
  dont know my system charshes for what

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjpeg8 8c-2ubuntu8 [modified: 
usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright]
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Mar 16 15:48:52 2018
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu10
   libgcc1 1:6.0.1-0ubuntu1
   libjpeg-turbo8 1.4.2-0ubuntu3
   multiarch-support 2.23-0ubuntu10
  DuplicateSignature:
   package:libjpeg8:8c-2ubuntu8 [modified: 
usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright]
   Unpacking libjpeg8:i386 (8c-2ubuntu8) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libjpeg8_8c-2ubuntu8_i386.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libjpeg8/copyright', which is 
different from other instances of package libjpeg8:i386
  ErrorMessage: trying to overwrite shared '/usr/share/doc/libjpeg8/copyright', 
which is different from other instances of package libjpeg8:i386
  InstallationDate: Installed on 2018-02-17 (27 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.25
  SourcePackage: libjpeg8-empty
  Title: package libjpeg8 8c-2ubuntu8 [modified: 
usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright] 
failed to install/upgrade: trying to overwrite shared 
'/usr/share/doc/libjpeg8/copyright', which is different from other instances of 
package libjpeg8:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1756949] Re: /usr/bin/unattended-upgrade:apt_pkg.Error:/usr/bin/unattended-upgrade@1917:main:mark_upgrade:mark_install

2018-03-19 Thread Balint Reczey

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Confirmed

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

Title:
  /usr/bin/unattended-upgrade:apt_pkg.Error:/usr/bin/unattended-
  upgrade@1917:main:mark_upgrade:mark_install

Status in apt package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/f29b4d5028eeeff1189351721fe408e6bd01fdb5 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

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

2018-03-19 Thread Phelps Scofield

Public bug reported:

I start the system normally and after an hour or more the system freezes

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-lowlatency 4.13.13
Uname: Linux 4.13.0-37-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Mar 19 14:13:25 2018
InstallationDate: Installed on 2018-03-05 (14 days ago)
InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
ProcEnviron:
 LANGUAGE=pt_BR:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug freeze xenial

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  I start the system normally and after an hour or more the system
  freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-lowlatency 4.13.13
  Uname: Linux 4.13.0-37-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Mar 19 14:13:25 2018
  InstallationDate: Installed on 2018-03-05 (14 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  ProcEnviron:
   LANGUAGE=pt_BR:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1756949] Re: /usr/bin/unattended-upgrade:apt_pkg.Error:/usr/bin/unattended-upgrade@1917:main:mark_upgrade:mark_install

2018-03-19 Thread Balint Reczey

This seems to be an apt issue:

Traceback (most recent call last):
  File "/usr/bin/unattended-upgrade", line 1917, in 
sys.exit(main(options))
  File "/usr/bin/unattended-upgrade", line 1668, in main
pkg.mark_upgrade(from_user=not pkg.is_auto_installed)
  File "/usr/lib/python3/dist-packages/apt/package.py", line 1316, in 
mark_upgrade
self.mark_install(from_user=from_user)
  File "/usr/lib/python3/dist-packages/apt/package.py", line 1309, in 
mark_install
fixer.resolve(True)
apt_pkg.Error: E:Error, pkgProblemResolver::Resolve generated breaks, this may 
be caused by held packages.

Unattended-upgrades may catch the exception, but I think it should be
fixed in apt.

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

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

Title:
  /usr/bin/unattended-upgrade:apt_pkg.Error:/usr/bin/unattended-
  upgrade@1917:main:mark_upgrade:mark_install

Status in apt package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/f29b4d5028eeeff1189351721fe408e6bd01fdb5 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1751493] Re: after update no icons in desktop

sathiya, thanks for advising the issue is resolved for you.

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

Title:
  after update no icons in desktop

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  using the ubuntu 16.04lts, after some update no icons, no menu in the
  desktop screen. please someone help to solve this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Feb 25 00:00:02 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:390c]
 Subsystem: Lenovo Radeon R5 M330 [17aa:390c]
  InstallationDate: Installed on 2018-02-04 (20 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 5986:0671 Acer, Inc 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80E5
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=ef0399a5-71eb-44c5-a6a2-82f8cc2a1e42 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0CN97WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo G50-80
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0CN97WW:bd01/08/2016:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoG50-80:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80E5
  dmi.product.version: Lenovo G50-80
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Feb 24 23:50:12 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1756502] Re: package libjpeg8 8c-2ubuntu8 [modified: usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright] failed to install/upgrade: trying to overwrite s

2018-03-19 Thread Seth Arnold

** Information type changed from Private Security to Public

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

Title:
  package libjpeg8 8c-2ubuntu8 [modified:
  usr/share/doc/libjpeg8/changelog.Debian.gz
  usr/share/doc/libjpeg8/copyright] failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libjpeg8/copyright', which is
  different from other instances of package libjpeg8:i386

Status in libjpeg8-empty package in Ubuntu:
  New

Bug description:
  dont know my system charshes for what

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjpeg8 8c-2ubuntu8 [modified: 
usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright]
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Mar 16 15:48:52 2018
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu10
   libgcc1 1:6.0.1-0ubuntu1
   libjpeg-turbo8 1.4.2-0ubuntu3
   multiarch-support 2.23-0ubuntu10
  DuplicateSignature:
   package:libjpeg8:8c-2ubuntu8 [modified: 
usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright]
   Unpacking libjpeg8:i386 (8c-2ubuntu8) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libjpeg8_8c-2ubuntu8_i386.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libjpeg8/copyright', which is 
different from other instances of package libjpeg8:i386
  ErrorMessage: trying to overwrite shared '/usr/share/doc/libjpeg8/copyright', 
which is different from other instances of package libjpeg8:i386
  InstallationDate: Installed on 2018-02-17 (27 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.25
  SourcePackage: libjpeg8-empty
  Title: package libjpeg8 8c-2ubuntu8 [modified: 
usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright] 
failed to install/upgrade: trying to overwrite shared 
'/usr/share/doc/libjpeg8/copyright', which is different from other instances of 
package libjpeg8:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1751493] Re: after update no icons in desktop

2018-03-19 Thread sathiya

Christopher sorry I don't know about the type of update.  But I'm totally
removed the version 16.04 LTS version and now I'm installed Ubuntu 17.01
version. Working fine.

On Mon 19 Mar, 2018 22:51 Christopher M. Penalver, <
christopher.m.penal...@gmail.com> wrote:

> sathiya, thank you for reporting this and helping make Ubuntu better.
>
> 1) What was updated specifically that afterwards the icons stopped
> displaying?
>
> ** Tags added: bios-outdated-b0cna0ww
>
> ** Changed in: xorg (Ubuntu)
>Importance: Undecided => Low
>
> ** Changed in: xorg (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1751493
>
> Title:
>   after update no icons in desktop
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   using the ubuntu 16.04lts, after some update no icons, no menu in the
>   desktop screen. please someone help to solve this issue.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: xorg 1:7.7+13ubuntu3
>   ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
>   Uname: Linux 4.13.0-36-generic x86_64
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.1-0ubuntu2.15
>   Architecture: amd64
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   Date: Sun Feb 25 00:00:02 2018
>   DistUpgraded: Fresh install
>   DistroCodename: xenial
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes, if not too technical
>   GraphicsCard:
>Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09)
> (prog-if 00 [VGA controller])
>  Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:390c]
>  Subsystem: Lenovo Radeon R5 M330 [17aa:390c]
>   InstallationDate: Installed on 2018-02-04 (20 days ago)
>   InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
> (20170801)
>   Lsusb:
>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>Bus 001 Device 004: ID 8087:07dc Intel Corp.
>Bus 001 Device 003: ID 5986:0671 Acer, Inc
>Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129
> Card Reader Controller
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   MachineType: LENOVO 80E5
>   ProcEnviron:
>LANGUAGE=en_IN:en
>TERM=xterm-256color
>PATH=(custom, no user)
>LANG=en_IN
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic
> root=UUID=ef0399a5-71eb-44c5-a6a2-82f8cc2a1e42 ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 01/08/2016
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: B0CN97WW
>   dmi.board.asset.tag: NO Asset Tag
>   dmi.board.name: Lenovo G50-80
>   dmi.board.vendor: LENOVO
>   dmi.board.version: SDK0J40679 WIN
>   dmi.chassis.asset.tag: NO Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Lenovo G50-80
>   dmi.modalias:
> dmi:bvnLENOVO:bvrB0CN97WW:bd01/08/2016:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoG50-80:
>   dmi.product.family: IDEAPAD
>   dmi.product.name: 80E5
>   dmi.product.version: Lenovo G50-80
>   dmi.sys.vendor: LENOVO
>   version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.83-1~16.04.1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
>   version.xserver-xorg-core: xserver-xorg-core N/A
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
>   xserver.bootTime: Sat Feb 24 23:50:12 2018
>   xserver.configfile: default
>   xserver.errors:
>
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.version: 2:1.19.5-0ubuntu2~16.04.1
>   xserver.video_driver: modeset
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1751493/+subscriptions
>

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

Title:
  after update no icons in desktop

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  using the ubuntu 16.04lts, after some update no icons, no menu in the
  desktop screen. please someone help to solve this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubun

[Touch-packages] [Bug 1756949] [NEW] /usr/bin/unattended-upgrade:apt_pkg.Error:/usr/bin/unattended-upgrade@1917:main:mark_upgrade:mark_install

2018-03-19 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/f29b4d5028eeeff1189351721fe408e6bd01fdb5 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bionic

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

Title:
  /usr/bin/unattended-upgrade:apt_pkg.Error:/usr/bin/unattended-
  upgrade@1917:main:mark_upgrade:mark_install

Status in apt package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/f29b4d5028eeeff1189351721fe408e6bd01fdb5 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1732970] Re: Remove cordova-ubuntu-3.4, qtfeedback-opensource-src, qtsystems-opensource-src from archive

Removing packages from bionic:
qtfeedback-opensource-src 5.0~git20130529-0ubuntu15~1 in bionic
libqt5feedback5 5.0~git20130529-0ubuntu15~1 in bionic amd64
libqt5feedback5 5.0~git20130529-0ubuntu15~1 in bionic arm64
libqt5feedback5 5.0~git20130529-0ubuntu15~1 in bionic armhf
libqt5feedback5 5.0~git20130529-0ubuntu15~1 in bionic i386
libqt5feedback5 5.0~git20130529-0ubuntu15~1 in bionic ppc64el
libqt5feedback5 5.0~git20130529-0ubuntu15~1 in bionic s390x
qml-module-qtfeedback 5.0~git20130529-0ubuntu15~1 in bionic 
amd64
qml-module-qtfeedback 5.0~git20130529-0ubuntu15~1 in bionic 
arm64
qml-module-qtfeedback 5.0~git20130529-0ubuntu15~1 in bionic 
armhf
qml-module-qtfeedback 5.0~git20130529-0ubuntu15~1 in bionic i386
qml-module-qtfeedback 5.0~git20130529-0ubuntu15~1 in bionic 
ppc64el
qml-module-qtfeedback 5.0~git20130529-0ubuntu15~1 in bionic 
s390x
qtdeclarative5-qtfeedback-plugin 5.0~git20130529-0ubuntu15~1 in 
bionic amd64
qtdeclarative5-qtfeedback-plugin 5.0~git20130529-0ubuntu15~1 in 
bionic arm64
qtdeclarative5-qtfeedback-plugin 5.0~git20130529-0ubuntu15~1 in 
bionic armhf
qtdeclarative5-qtfeedback-plugin 5.0~git20130529-0ubuntu15~1 in 
bionic i386
qtdeclarative5-qtfeedback-plugin 5.0~git20130529-0ubuntu15~1 in 
bionic ppc64el
qtdeclarative5-qtfeedback-plugin 5.0~git20130529-0ubuntu15~1 in 
bionic s390x
qtfeedback5-dbg 5.0~git20130529-0ubuntu15~1 in bionic amd64
qtfeedback5-dbg 5.0~git20130529-0ubuntu15~1 in bionic arm64
qtfeedback5-dbg 5.0~git20130529-0ubuntu15~1 in bionic armhf
qtfeedback5-dbg 5.0~git20130529-0ubuntu15~1 in bionic i386
qtfeedback5-dbg 5.0~git20130529-0ubuntu15~1 in bionic ppc64el
qtfeedback5-dbg 5.0~git20130529-0ubuntu15~1 in bionic s390x
qtfeedback5-dev 5.0~git20130529-0ubuntu15~1 in bionic amd64
qtfeedback5-dev 5.0~git20130529-0ubuntu15~1 in bionic arm64
qtfeedback5-dev 5.0~git20130529-0ubuntu15~1 in bionic armhf
qtfeedback5-dev 5.0~git20130529-0ubuntu15~1 in bionic i386
qtfeedback5-dev 5.0~git20130529-0ubuntu15~1 in bionic ppc64el
qtfeedback5-dev 5.0~git20130529-0ubuntu15~1 in bionic s390x
qtfeedback5-doc 5.0~git20130529-0ubuntu15~1 in bionic amd64
qtfeedback5-doc 5.0~git20130529-0ubuntu15~1 in bionic arm64
qtfeedback5-doc 5.0~git20130529-0ubuntu15~1 in bionic armhf
qtfeedback5-doc 5.0~git20130529-0ubuntu15~1 in bionic i386
qtfeedback5-doc 5.0~git20130529-0ubuntu15~1 in bionic ppc64el
qtfeedback5-doc 5.0~git20130529-0ubuntu15~1 in bionic s390x
qtfeedback5-doc-html 5.0~git20130529-0ubuntu15~1 in bionic amd64
qtfeedback5-doc-html 5.0~git20130529-0ubuntu15~1 in bionic arm64
qtfeedback5-doc-html 5.0~git20130529-0ubuntu15~1 in bionic armhf
qtfeedback5-doc-html 5.0~git20130529-0ubuntu15~1 in bionic i386
qtfeedback5-doc-html 5.0~git20130529-0ubuntu15~1 in bionic 
ppc64el
qtfeedback5-doc-html 5.0~git20130529-0ubuntu15~1 in bionic s390x
Comment: Ubuntu-specific, obsoleted product, no maintainer; LP: #1732970
1 package successfully removed.


** Changed in: qtfeedback-opensource-src (Ubuntu)
   Status: New => Fix Released

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

Title:
  Remove cordova-ubuntu-3.4, qtfeedback-opensource-src, qtsystems-
  opensource-src from archive

Status in cordova-ubuntu-3.4 package in Ubuntu:
  Fix Released
Status in qtfeedback-opensource-src package in Ubuntu:
  Fix Released
Status in qtsystems-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  cordova-ubuntu is dead upstream (https://github.com/apache/cordova-
  ubuntu had last commit in Oct 2016), Ubuntu packaging has no active
  maintainer and has not been updated since 2014.

  I have talked to Alberto Mardegan on IRC, he confirmed that it should be safe 
to remove it:
  https://irclogs.ubuntu.com/2017/11/17/%23ubuntu-devel.html#t18:43

  qtfeedback-opensource-src and qtsystems-opensource-src are libraries
  which have never become part of official Qt releases, and their only
  user in Ubuntu was cordova-ubuntu-3.4.

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

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

[Touch-packages] [Bug 1699216] Re: Encrypted home support

2018-03-19 Thread Jeremy Soller

There is no issue with that. We will be able to keep our patches in
initial setup without any effort from Ubuntu and minimal effort from
Pop. We are going to be encouraging full disk encryption, the same as
Ubuntu.

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

Title:
  Encrypted home support

Status in accountsservice package in Ubuntu:
  Won't Fix
Status in gnome-control-center package in Ubuntu:
  Won't Fix
Status in gnome-initial-setup package in Ubuntu:
  Won't Fix

Bug description:
  In the CreateUser D-bus call, allow the home directory of the new user
  to be encrypted.

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

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

[Touch-packages] [Bug 1732970] Re: Remove cordova-ubuntu-3.4, qtfeedback-opensource-src, qtsystems-opensource-src from archive

Removing packages from bionic:
qtsystems-opensource-src 5.0~git20141206~44f70d99-0ubuntu15~5 in bionic
libqt5publishsubscribe5 5.0~git20141206~44f70d99-0ubuntu15~5 in 
bionic amd64
libqt5publishsubscribe5 5.0~git20141206~44f70d99-0ubuntu15~5 in 
bionic arm64
libqt5publishsubscribe5 5.0~git20141206~44f70d99-0ubuntu15~5 in 
bionic armhf
libqt5publishsubscribe5 5.0~git20141206~44f70d99-0ubuntu15~5 in 
bionic i386
libqt5publishsubscribe5 5.0~git20141206~44f70d99-0ubuntu15~5 in 
bionic ppc64el
libqt5publishsubscribe5 5.0~git20141206~44f70d99-0ubuntu15~5 in 
bionic s390x
libqt5serviceframework5 5.0~git20141206~44f70d99-0ubuntu15~5 in 
bionic amd64
libqt5serviceframework5 5.0~git20141206~44f70d99-0ubuntu15~5 in 
bionic arm64
libqt5serviceframework5 5.0~git20141206~44f70d99-0ubuntu15~5 in 
bionic armhf
libqt5serviceframework5 5.0~git20141206~44f70d99-0ubuntu15~5 in 
bionic i386
libqt5serviceframework5 5.0~git20141206~44f70d99-0ubuntu15~5 in 
bionic ppc64el
libqt5serviceframework5 5.0~git20141206~44f70d99-0ubuntu15~5 in 
bionic s390x
libqt5systeminfo5 5.0~git20141206~44f70d99-0ubuntu15~5 in 
bionic amd64
libqt5systeminfo5 5.0~git20141206~44f70d99-0ubuntu15~5 in 
bionic arm64
libqt5systeminfo5 5.0~git20141206~44f70d99-0ubuntu15~5 in 
bionic armhf
libqt5systeminfo5 5.0~git20141206~44f70d99-0ubuntu15~5 in 
bionic i386
libqt5systeminfo5 5.0~git20141206~44f70d99-0ubuntu15~5 in 
bionic ppc64el
libqt5systeminfo5 5.0~git20141206~44f70d99-0ubuntu15~5 in 
bionic s390x
qml-module-qtpublishsubscribe 
5.0~git20141206~44f70d99-0ubuntu15~5 in bionic amd64
qml-module-qtpublishsubscribe 
5.0~git20141206~44f70d99-0ubuntu15~5 in bionic arm64
qml-module-qtpublishsubscribe 
5.0~git20141206~44f70d99-0ubuntu15~5 in bionic armhf
qml-module-qtpublishsubscribe 
5.0~git20141206~44f70d99-0ubuntu15~5 in bionic i386
qml-module-qtpublishsubscribe 
5.0~git20141206~44f70d99-0ubuntu15~5 in bionic ppc64el
qml-module-qtpublishsubscribe 
5.0~git20141206~44f70d99-0ubuntu15~5 in bionic s390x
qml-module-qtserviceframework 
5.0~git20141206~44f70d99-0ubuntu15~5 in bionic amd64
qml-module-qtserviceframework 
5.0~git20141206~44f70d99-0ubuntu15~5 in bionic arm64
qml-module-qtserviceframework 
5.0~git20141206~44f70d99-0ubuntu15~5 in bionic armhf
qml-module-qtserviceframework 
5.0~git20141206~44f70d99-0ubuntu15~5 in bionic i386
qml-module-qtserviceframework 
5.0~git20141206~44f70d99-0ubuntu15~5 in bionic ppc64el
qml-module-qtserviceframework 
5.0~git20141206~44f70d99-0ubuntu15~5 in bionic s390x
qml-module-qtsysteminfo 5.0~git20141206~44f70d99-0ubuntu15~5 in 
bionic amd64
qml-module-qtsysteminfo 5.0~git20141206~44f70d99-0ubuntu15~5 in 
bionic arm64
qml-module-qtsysteminfo 5.0~git20141206~44f70d99-0ubuntu15~5 in 
bionic armhf
qml-module-qtsysteminfo 5.0~git20141206~44f70d99-0ubuntu15~5 in 
bionic i386
qml-module-qtsysteminfo 5.0~git20141206~44f70d99-0ubuntu15~5 in 
bionic ppc64el
qml-module-qtsysteminfo 5.0~git20141206~44f70d99-0ubuntu15~5 in 
bionic s390x
qtdeclarative5-publishsubscribe-plugin 
5.0~git20141206~44f70d99-0ubuntu15~5 in bionic amd64
qtdeclarative5-publishsubscribe-plugin 
5.0~git20141206~44f70d99-0ubuntu15~5 in bionic arm64
qtdeclarative5-publishsubscribe-plugin 
5.0~git20141206~44f70d99-0ubuntu15~5 in bionic armhf
qtdeclarative5-publishsubscribe-plugin 
5.0~git20141206~44f70d99-0ubuntu15~5 in bionic i386
qtdeclarative5-publishsubscribe-plugin 
5.0~git20141206~44f70d99-0ubuntu15~5 in bionic ppc64el
qtdeclarative5-publishsubscribe-plugin 
5.0~git20141206~44f70d99-0ubuntu15~5 in bionic s390x
qtdeclarative5-serviceframework-plugin 
5.0~git20141206~44f70d99-0ubuntu15~5 in bionic amd64
qtdeclarative5-serviceframework-plugin 
5.0~git20141206~44f70d99-0ubuntu15~5 in bionic arm64
qtdeclarative5-serviceframework-plugin 
5.0~git20141206~44f70d99-0ubuntu15~5 in bionic armhf
qtdeclarative5-serviceframework-plugin 
5.0~git20141206~44f70d99-0ubuntu15~5 in bionic i386
qtdeclarative5-serviceframework-plugin 
5.0~git20141206~44f70d99-0ubuntu15~5 in bionic ppc64el
qtdeclarative5-serviceframework-plugin 
5.0~git20141206~44f70d99-0ubuntu15~5 in bionic s390x
qtdeclarative5-systeminfo-plugin 
5.0~git20141206~44f70d99-0ubuntu15~5 in bionic amd64
qtdeclarative5-systeminfo-plugin

[Touch-packages] [Bug 1732970] Re: Remove cordova-ubuntu-3.4, qtfeedback-opensource-src, qtsystems-opensource-src from archive

Removing packages from bionic:
cordova-ubuntu-3.4 3.4~pre3.r19ubuntu1 in bionic
ubuntu-html5-platform-3.4-dev 3.4~pre3.r19ubuntu1 in bionic 
amd64
ubuntu-html5-platform-3.4-dev 3.4~pre3.r19ubuntu1 in bionic 
arm64
ubuntu-html5-platform-3.4-dev 3.4~pre3.r19ubuntu1 in bionic 
armhf
ubuntu-html5-platform-3.4-dev 3.4~pre3.r19ubuntu1 in bionic i386
ubuntu-html5-platform-3.4-dev 3.4~pre3.r19ubuntu1 in bionic 
ppc64el
Comment: Ubuntu-specific, obsoleted product, no maintainer; LP: #1732970
1 package successfully removed.


** Changed in: cordova-ubuntu-3.4 (Ubuntu)
   Status: New => Fix Released

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

Title:
  Remove cordova-ubuntu-3.4, qtfeedback-opensource-src, qtsystems-
  opensource-src from archive

Status in cordova-ubuntu-3.4 package in Ubuntu:
  Fix Released
Status in qtfeedback-opensource-src package in Ubuntu:
  New
Status in qtsystems-opensource-src package in Ubuntu:
  New

Bug description:
  cordova-ubuntu is dead upstream (https://github.com/apache/cordova-
  ubuntu had last commit in Oct 2016), Ubuntu packaging has no active
  maintainer and has not been updated since 2014.

  I have talked to Alberto Mardegan on IRC, he confirmed that it should be safe 
to remove it:
  https://irclogs.ubuntu.com/2017/11/17/%23ubuntu-devel.html#t18:43

  qtfeedback-opensource-src and qtsystems-opensource-src are libraries
  which have never become part of official Qt releases, and their only
  user in Ubuntu was cordova-ubuntu-3.4.

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

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

[Touch-packages] [Bug 1751653] Re: Minecraft makes Ubuntu GNOME extremely slow

Moving to gnome-shell for GNOME folks to review and further root cause.

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

Title:
  Minecraft makes Ubuntu GNOME extremely slow

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  In Ubuntu 17.10 with GNOME, after launching Minecraft, when the
  Minecraft play window pops up Ubuntu is really slow and hardly
  responds.

  WORKAROUND: Install Unity.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 25 21:29:43 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 
[1002:9712] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company RS880M [Mobility Radeon HD 4225/4250] 
[103c:148b]
  InstallationDate: Installed on 2018-02-24 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Hewlett-Packard HP Pavilion dm1 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=b6ec7597-5a12-45d5-910b-2fb46d3cfd23 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 148B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 80.14
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.15:bd09/15/2010:svnHewlett-Packard:pnHPPaviliondm1NotebookPC:pvr049B102432032:rvnHewlett-Packard:rn148B:rvr80.14:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dm1 Notebook PC
  dmi.product.version: 049B102432032
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1756937] [NEW] report_crashes setting not written

2018-03-19 Thread Brian Murray

Public bug reported:

whoopsie was built with two settings, report_metrics (statistics like
popcon - currently unused) and report_crashes (for reporting crash
reports to the Error Tracker). However, only report_metrics gets written
to '/etc/whoopsie' while the setting for report_crashes is defined by
having whoopsie.disable. This complicates matters as there are two
places to look for whoopsie settings '/etc/whoopsie' and checking for a
.disable file. It'd be best if "report_crashes" was also written to
'/etc/whoopsie'.

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

** Affects: whoopsie-preferences (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bionic

** Also affects: whoopsie-preferences (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: bionic

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

Title:
  report_crashes setting not written

Status in whoopsie package in Ubuntu:
  New
Status in whoopsie-preferences package in Ubuntu:
  New

Bug description:
  whoopsie was built with two settings, report_metrics (statistics like
  popcon - currently unused) and report_crashes (for reporting crash
  reports to the Error Tracker). However, only report_metrics gets
  written to '/etc/whoopsie' while the setting for report_crashes is
  defined by having whoopsie.disable. This complicates matters as there
  are two places to look for whoopsie settings '/etc/whoopsie' and
  checking for a .disable file. It'd be best if "report_crashes" was
  also written to '/etc/whoopsie'.

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

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

[Touch-packages] [Bug 1737570] Re: Add support for RequiredForOnline in networkd

Mar 19 17:05:32 systemd-sru-artful systemd-networkd[311]:
/run/systemd/network/10-netplan-eth0.network:12: Unknown lvalue
'RequiredForOnline' in section 'Link'

root@systemd-sru-artful:~# /lib/systemd/systemd-networkd-wait-online --timeout=5
ignoring: lo
Event loop failed: Connection timed out

root@systemd-sru-artful:~# dpkg-query -W systemd
systemd 234-2ubuntu12.1

Upgrading to proposed:

root@systemd-sru-artful:~# dpkg-query -W systemd
systemd 234-2ubuntu12.3

root@systemd-sru-artful:~# /lib/systemd/systemd-networkd-wait-online --timeout=5
ignoring: lo
ignoring: eth0
Event loop failed: Connection timed out

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

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

Title:
  Add support for RequiredForOnline in networkd

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * netplan & networkd based systems typically await networking to be
  up on boot, without any ability to specify that an interface should be
  configured, but might not be online at boot. This is a backport of the
  RequiredForOnline= feature to match optional=true in netplan.

  [Test Case]

   * Configure a netowkring interface using .link/.network file and specify 
RequiredForOnline=False
   * Bring the interface down / offline it
   * execute systemd-networkd-wait-online, which should exit immediately since 
no interfaces are required to be online

  [Regression Potential]

   * This adds a support for an additional stanza in the network files.
  This stanza is not used by default. if the stanza is used, but older
  networkd is in use, networkd will ignore this unknown stanza. Thus
  this change is backward and forward compatible. The difference is that
  boot is not blocked awaiting systemd-networkd-wait-online to timeout.

  [Other Info]
   
   * Original bug report

  Add support for RequiredForOnline in networkd

  
https://github.com/systemd/systemd/commit/c1a3890410f043fe09af8b139eb6bfe2832089be

  RequiredForOnline= denotes a link/network that does/does not require being up
  for systemd-networkd-wait-online to consider the system online; this makes it
  possible to ignore devices without modifying parameters to wait-online.

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

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

[Touch-packages] [Bug 1751493] Re: after update no icons in desktop

sathiya, thank you for reporting this and helping make Ubuntu better.

1) What was updated specifically that afterwards the icons stopped
displaying?

** Tags added: bios-outdated-b0cna0ww

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

** Changed in: xorg (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/1751493

Title:
  after update no icons in desktop

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  using the ubuntu 16.04lts, after some update no icons, no menu in the
  desktop screen. please someone help to solve this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Feb 25 00:00:02 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:390c]
 Subsystem: Lenovo Radeon R5 M330 [17aa:390c]
  InstallationDate: Installed on 2018-02-04 (20 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 5986:0671 Acer, Inc 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80E5
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=ef0399a5-71eb-44c5-a6a2-82f8cc2a1e42 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0CN97WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo G50-80
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0CN97WW:bd01/08/2016:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoG50-80:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80E5
  dmi.product.version: Lenovo G50-80
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Feb 24 23:50:12 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1751653] Re: Minecraft makes Ubuntu GNOME extremely slow

** Description changed:

- Hi!
- I've had Ubuntu 16 with Unity on my children's older computer and Minecraft 
(downloaded and installed from Software Center) worked just fine. I then did a 
clean install to Ubuntu 17 with GNOME and downloaded and installed Minecraft in 
the same way, but when the final Minecraft playwindow pops up Ubuntu is really 
slow and hardly respond. After I installed Unity and run it instead of GNOME, 
everything worked great again. Maybe Java OpenJDK doesn't work well with GNOME?
- Is this something you can fix?
- I would prefer to run the preinstalled GNOME instead of Unity, especially 
since GNOME is the choice for Ubuntu from now on, and I'm planning on upgrading 
to the upcoming version 18 of Ubuntu.
- Thank you for a nice operating system otherwise.
- Best regards, Ken Karlsson
+ In Ubuntu 17.10 with GNOME, after launching Minecraft, when the
+ Minecraft play window pops up Ubuntu is really slow and hardly responds.
+ 
+ WORKAROUND: Install Unity.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 25 21:29:43 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 
[1002:9712] (prog-if 00 [VGA controller])
-Subsystem: Hewlett-Packard Company RS880M [Mobility Radeon HD 4225/4250] 
[103c:148b]
+  Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 
[1002:9712] (prog-if 00 [VGA controller])
+    Subsystem: Hewlett-Packard Company RS880M [Mobility Radeon HD 4225/4250] 
[103c:148b]
  InstallationDate: Installed on 2018-02-24 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Hewlett-Packard HP Pavilion dm1 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=b6ec7597-5a12-45d5-910b-2fb46d3cfd23 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 148B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 80.14
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.15:bd09/15/2010:svnHewlett-Packard:pnHPPaviliondm1NotebookPC:pvr049B102432032:rvnHewlett-Packard:rn148B:rvr80.14:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dm1 Notebook PC
  dmi.product.version: 049B102432032
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

Title:
  Minecraft makes Ubuntu GNOME extremely slow

Status in xorg package in Ubuntu:
  New

Bug description:
  In Ubuntu 17.10 with GNOME, after launching Minecraft, when the
  Minecraft play window pops up Ubuntu is really slow and hardly
  responds.

  WORKAROUND: Install Unity.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 25 21:29:43 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 
[1002:9712] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company RS880M [Mobility Radeon HD 4225/4250] 
[103c:148b]
  InstallationDate: Installed on 2018-02-24 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Hewlett-Packard HP Pavilion dm1 Notebook PC
  ProcKernelCm

[Touch-packages] [Bug 1751410] Re: xorg issue

Dahc, thank you for reporting this and helping make Ubuntu better.

1) To clarify, the issue you are having is only Firefox or Chrome will
crash?

2) How often does the crashing occur?

3) What specifically do you do that afterwards the crashing occurs?

4) After the crash, are there crash files in /var/crash?

5) Is this something that started to happen after an update? If so,
which specifically?

** Tags added: latest-bios-f2

** Description changed:

- I believe my issue is similar to this one.
- 
- https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1606774
- 
- I have no idea how to fix it at this time.  I am using this workstation
- more often these days as it provides a machine on the first floor for me
- to use.  Typically, Firefox or Chrome will crash very often.
- 
- Thanks!
+ Firefox or Chrome will crash very often.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Feb 23 22:35:25 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8470D] 
[1002:9996] (prog-if 00 [VGA controller])
-Subsystem: Gigabyte Technology Co., Ltd Richland [Radeon HD 8470D] 
[1458:d000]
+  Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8470D] 
[1002:9996] (prog-if 00 [VGA controller])
+    Subsystem: Gigabyte Technology Co., Ltd Richland [Radeon HD 8470D] 
[1458:d000]
  InstallationDate: Installed on 2016-10-29 (482 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
-  LANGUAGE=en_US
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_US
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed 
root=/dev/mapper/hostname--vg-root ro
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88X-D3HP
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88X-D3HP:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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
  xserver.bootTime: Fri Feb 23 22:30:00 2018
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: radeon

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

** Changed in: xorg (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/1751410

Title:
  xorg issue

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Firefox or Chrome will crash very often.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Feb 23 22:35:25 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant

[Touch-packages] [Bug 1726068] Re: software-properties closed, closing debconf socket, while aptdaemon is running (package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/up

2018-03-19 Thread Julian Andres Klode

I think dangling sockets to the frontend might also be a problem with 
PackageKit, but I'm not sure. My idea was to have helper have a timeout and be 
(re)launched by systemd via socket activation, but 
I don't know if that's feasible.

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

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

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

Title:
  software-properties closed, closing debconf socket, while aptdaemon is
  running (package shim-signed
  1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1)

Status in aptdaemon package in Ubuntu:
  New
Status in packagekit package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  error message on start up

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  .proc.sys.kernel.moksbstate_disabled: 0
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sun Oct 22 12:33:48 2017
  DpkgHistoryLog:
   Start-Date: 2017-10-22  12:31:01
   Commandline: aptdaemon role='role-commit-packages' sender=':1.94'
   Install: linux-image-generic:amd64 (4.4.0.97.102, automatic), 
libcuda1-387:amd64 (387.12-0ubuntu0~gpu16.04.1, automatic), 
linux-image-4.4.0-97-generic:amd64 (4.4.0-97.120, automatic), 
linux-image-extra-4.4.0-97-generic:amd64 (4.4.0-97.120, automatic), 
nvidia-prime:amd64 (0.8.2, automatic), libxnvctrl0:amd64 
(384.90-0ubuntu0~gpu16.04.1, automatic), lib32gcc1:amd64 (1:6.0.1-0ubuntu1, 
automatic), libc6-i386:amd64 (2.23-0ubuntu9, automatic), 
screen-resolution-extra:amd64 (0.17.1, automatic), ocl-icd-libopencl1:amd64 
(2.2.8-1, automatic), libjansson4:amd64 (2.7-3, automatic), bbswitch-dkms:amd64 
(0.8-3ubuntu1, automatic), linux-generic:amd64 (4.4.0.97.102), 
nvidia-opencl-icd-387:amd64 (387.12-0ubuntu0~gpu16.04.1, automatic), 
nvidia-387:amd64 (387.12-0ubuntu0~gpu16.04.1), nvidia-settings:amd64 
(384.90-0ubuntu0~gpu16.04.1, automatic)
  EFITables:
   Oct 22 12:34:32 crs-Ubuntu kernel: efi: EFI v2.40 by American Megatrends
   Oct 22 12:34:32 crs-Ubuntu kernel: efi:  ESRT=0x77e72f98  ACPI=0x77591000  
ACPI 2.0=0x77591000  SMBIOS=0x77e71000  SMBIOS 3.0=0x77e7 
   Oct 22 12:34:32 crs-Ubuntu kernel: esrt: Reserving ESRT space from 
0x77e72f98 to 0x77e72fd0.
   Oct 22 12:34:32 crs-Ubuntu kernel: Secure boot enabled
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-05-16 (159 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SecureBoot: 6   0   0   0   1
  SourcePackage: shim-signed
  Title: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 424215] Re: Bluetooth mouse usage makes A2DP audio stutter

2018-03-19 Thread PauLoX

I can confirm the bug on Ubuntu 17.10

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

Title:
  Bluetooth mouse usage makes A2DP audio stutter

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: bluez

  When I use my Bluetooth A2DP headset (Philips SHB7102) together with
  my mouse (Lenovo Bluetooth Laser Mouse), I notice this:

  Whenever I leave the mouse still for a few seconds (it seems to enter
  some kind of lower-power-mode) and then start to move it, my music
  most of the time skips for a second. This makes using these two
  bluetooth devices together quite annoying...

  The adapter is a Lenovo "ThinkPad Bluetooth with Enhanced Data Rate
  II" (Bus 004 Device 005: ID 0a5c:2145 Broadcom Corp.)

  I am running current karmic amd64 (linux 2.6.31-9).

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

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

[Touch-packages] [Bug 1751120] Re: Xorg freeze when moving a window between external/internal monitors

Dan Watkins, thank you for reporting this and helping make Ubuntu
better.

1) Is this something that started to happen after an update? If so,
which specifically?

2) After the freeze, are there crash files in /var/crash?

3) As per your logs, you are using kernel 4.13.x (not supported in
Ubuntu 18.04). Hence, if you restore your kernel to a supported version
(4.15.x) is this still reproducible?

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

** Changed in: xorg (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/1751120

Title:
  Xorg freeze when moving a window between external/internal monitors

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My mouse cursor would still move, but I couldn't do anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 22 13:44:42 2018
  DistUpgraded: 2018-01-23 11:42:22,182 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.6, 4.13.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Once a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo ThinkPad T440p [17aa:220e]
  InstallationDate: Installed on 2017-10-23 (121 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20ANCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to bionic on 2018-01-23 (30 days ago)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET70WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ANCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET70WW(2.24):bd05/21/2014:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20ANCTO1WW
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-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/xorg/+bug/1751120/+subscriptions

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

[Touch-packages] [Bug 1735981] Re: Huawei ME936 mobile broadband can't connect

2018-03-19 Thread Steffen Neumann

I can confirm that the workaround above by Philipp Hufnagl 
indeed does the job. I am writing this comment from aboard a train ;-)
The connction setup is not very robust, and sometimes 
fails at Simple connect state (4/8): Wait to get fully enabled

How to get a proper fix upstream now ? 
Yours, Steffen

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

Title:
  Huawei ME936 mobile broadband can't connect

Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  Hi, I have an Acer Travelmate P648 with a Huawei ME936
  internal USB mobile broadband card, and can't connect.
  This didn't work in 17.04, and still does not work in 17.10.

  The USB device is successfully connected, 
  ModemManager gets as far as "Simple connect state (8/8): All done"
  During the setup ModemManager complains with "Couldn't find associated 
cdc-wdm port for 'net/wwp0s20f0u9c2'"

  DHCP tries to get a configuration, but " dhcp4 (wwp0s20f0u9c2): request timed 
out".
  IP6 is set to "automatically" in the network settings for this configuration. 

  and finally connection fails with 
  "device (ttyUSB0): state change: ip-config -> failed (reason 
'ip-config-unavailable', internal state 'managed')"

  I checked that there are enough credits left in my account with the
  provider.

  Any ideas what else to check ?

  Yours,
  Steffen

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: modemmanager 1.6.8-1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  3 11:27:49 2017
  InstallationDate: Installed on 2017-04-24 (222 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: modemmanager
  UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago)

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

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

[Touch-packages] [Bug 1751191] Re: Using Vbox with 3D enabled, creates strange stuttering

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

Title:
  Using Vbox with 3D enabled, creates strange stuttering

Status in virtualbox package in Ubuntu:
  New

Bug description:
  It looks that the sequence of frames displayed at the screen is mixed
  up. The display goes back say ¼ a second and that gives a very strange
  effect. You type a letter, that letter is erased afterwards and
  reappears after ¼ of a second. See the ATTACHED video. You see the
  same type of going back a number of frames in e.g. YouTube videos,
  which gives a jittery effect.

  See also the Conky graphs going sometimes backward in both videos :)

  The problem only occurs if I have 3D acceleration enabled in
  Virtualbox and it occurred with both Ubuntu 16.04 and 17.10 hosts. It
  only occurs at Ubuntu 16.04 guests, the problem does not occur in
  Ubuntu 17.10 nor in other Linux distros including Ubuntu Mate and
  Xubuntu. I use Virtualbox 5.2.6 with Guest Additions 5.2.7 as
  recommended by Oracle on their website.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Feb 22 23:35:36 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2017-03-29 (330 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=82019235-3f7b-4b99-b622-d6bb790566d5 ro quiet splash zswap.enabled=1
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Feb 22 23:13:23 2018
  xserver.configfile: default
  xserver.errors:
   Failed to load module "vboxvideo" (module does not exist, 0)
   Failed to load module "vboxvideo" (module does not exist, 0)
   modeset(0): glamor initialization failed
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1753776] Re: Graphics corruption just before login animation to Xorg sessions (Intel gen9 GPUs only)

> /etc/gdm3/custom.conf
>   set [daemon] WaylandEnable=false to force xorg login :
>  my feeling is that should be the default now as ubuntu as made that choice 
> for the release (and
> wayland / apps still does not well together in many cases)

That will make it impossible for people to log into the Ubuntu on
Wayland session which will be provided as a Tech Preview in Ubuntu 18.04
LTS. So no, we're not going to change that setting.

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

Title:
  Graphics corruption just before login animation to Xorg sessions
  (Intel gen9 GPUs only)

Status in Mesa:
  Confirmed
Status in gdm3 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged
Status in wayland package in Ubuntu:
  Invalid

Bug description:
  Immediately after login (I enter the password and hit enter) the screen 
"crumbles" for few seconds, then all becomes normal and the system works fine. 
I have done apt update+upgrade many times, also with proposed enabled, I have 
also installed a new ISO (now i'm using the Alpha dated 20180305) but the 
problem remains. The problem happens with the x11 session but not with wayland. 
  Also problem does not show with different hardware. 

  corrado@corrado-p7-bb-0305:~$ inxi -Fx
  System:Host: corrado-p7-bb-0305 Kernel: 4.15.0-10-generic x86_64 bits: 64 
gcc: 7.3.0
 Desktop: Gnome 3.27.92 (Gtk 3.22.28-1ubuntu3) Distro: Ubuntu 
Bionic Beaver (development branch)
  Machine:   Device: desktop Mobo: ASRock model: H110M-G/M.2 serial: N/A UEFI: 
American Megatrends v: P1.10 date: 05/11/2017
  CPU:   Dual core Intel Core i3-7100 (-MT-MCP-) arch: Skylake rev.9 cache: 
3072 KB
 flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648
 clock speeds: max: 3900 MHz 1: 1018 MHz 2: 3150 MHz 3: 3153 MHz 4: 
3081 MHz
  Graphics:  Card: Intel HD Graphics 630 bus-ID: 00:02.0
 Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 
1920x1080@60.00hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2)
 version: 4.5 Mesa 18.0.0-rc4 Direct Render: Yes
  Audio: Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 
00:1f.3
 Sound: Advanced Linux Sound Architecture v: k4.15.0-10-generic
  Network:   Card: Intel Ethernet Connection (2) I219-V driver: e1000e v: 
3.2.6-k 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: 1000.2GB (1.3% used)
 ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB
  Partition: ID-1: / size: 32G used: 4.3G (15%) fs: ext4 dev: /dev/sda7
 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
  Sensors:   System Temperatures: cpu: 38.5C mobo: N/A
 Fan Speeds (in rpm): cpu: N/A
  Info:  Processes: 234 Uptime: 11 min Memory: 1144.7/7680.8MB Init: 
systemd runlevel: 5 Gcc sys: N/A
 Client: Shell (bash 4.4.181) inxi: 2.3.56 
  corrado@corrado-p7-bb-0305:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  6 15:47:50 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2018-03-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
   Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=9a36b498-59f5-4a36-81db-3046ff6bdeaa ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.

[Touch-packages] [Bug 1751120] Re: Xorg freeze when moving a window between external/internal monitors

** Tags added: bios-outdated-2.48

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

Title:
  Xorg freeze when moving a window between external/internal monitors

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My mouse cursor would still move, but I couldn't do anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 22 13:44:42 2018
  DistUpgraded: 2018-01-23 11:42:22,182 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.6, 4.13.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Once a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo ThinkPad T440p [17aa:220e]
  InstallationDate: Installed on 2017-10-23 (121 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20ANCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to bionic on 2018-01-23 (30 days ago)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET70WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ANCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET70WW(2.24):bd05/21/2014:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20ANCTO1WW
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-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/xorg/+bug/1751120/+subscriptions

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

[Touch-packages] [Bug 1751075] Re: Xorg freeze when use mpv or cheese.

Ven, thank you for reporting this and helping make Ubuntu better.

Given you are using an unsupported kernel, non-default kernel
parameters, etc. if possible, it is best to get the computer in a stable
state without WORKAROUNDs/unsupported software, and then reassess this
issue.

Hence, to see if this is already resolved in Ubuntu, could you please
test http://cdimage.ubuntu.com/daily-live/current/ and advise to the
results?

** Description changed:

- I have my new laptop, Lenovo 720s-13ARR shipped with the latest Ryzen 5 
2500U, installed Ubuntu 17.10, it seems everything works except Wifi and GPU. 
After changing the wifi card with Intel 8265 and manually upgrading kernel with 
M-bab's build from 'https://github.com/M-Bab/linux-kernel-amdgpu-binaries'. 
Wifi and Gpu are working. But if I use mpv playing a video, when I try to 
resume the window from fullscreen, the screen freezes. Same thing happens when 
I use cheese, the camera app. Nothing I can do except a hard poweroff. After 
suffering that couple of times, I started to look for solutions from Internet. 
There are many error messages I can see if I use 'dmesg -l err' in the 
terminal. I cannot solve most of them, only use pci=noaer in the grub to 
suppress the "PCIe bus error", which keep increasing my "/var/log/kern.log" 
file size hundreds MB per hour before.
- One more thing, if I start a reboot, the laptop might have a random hang on 
ubuntu logo screen. To avoid this, I have to poweroff first, then press power 
button to implement a 'reboot'. No idea for me in which part problem should be 
responsible for these failures.
+ When using mpv to play a video fullscreen, when I try to resume the
+ window from fullscreen, the screen freezes. Same thing happens when I
+ use cheese. Nothing I can do except a hard poweroff.
+ 
+ I've manually upgraded my kernel with M-bab's build from
+ 'https://github.com/M-Bab/linux-kernel-amdgpu-binaries'.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature:
-  
+ 
  Uname: Linux 4.15.4+ x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 21:53:01 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: I don't know
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
-Subsystem: Lenovo Device [17aa:380c]
+  Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
+    Subsystem: Lenovo Device [17aa:380c]
  InstallationDate: Installed on 2018-01-30 (22 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: LENOVO 81BR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.4+ 
root=UUID=399cfaf6-9c73-4786-8ef5-bd331d20aadc ro pci=noaer 
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.1 quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Tags added: latest-bios-6kcn28ww

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

** Changed in: xorg (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/1751075

Title:
  Xorg freeze when use mpv or cheese.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When using mpv to play a video fullscreen, when I try to resume the
  window from fullscreen, the screen freeze

[Touch-packages] [Bug 1488620] Re: Add LZ4 support

2018-03-19 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  Add LZ4 support

Status in initramfs-tools package in Ubuntu:
  Triaged

Bug description:
  I found that I could enable LZ4 compression for initramfs on my vivid
  machine by installing liblz4-tool package, adding one line to
  mkinitramfs and installing a kernel compiled with CONFIG_CRYPTO_LZ4=y.

  Please include support for (legacy) LZ4.

  Attached patch includes changes made to the latest version (initramfs-
  tools_0.120ubuntu3).

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

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

[Touch-packages] [Bug 1737570] Re: Add support for RequiredForOnline in networkd

Using xenial lxd container, migrating to networkd using netplan, and
updating generated .network file to include RequiredForOnline=false, i
can see that it is correctly ignored.

# dpkg-query -W systemd
systemd 229-4ubuntu21.2

# /lib/systemd/systemd-networkd-wait-online --timeout=5
ignoring: lo
ignoring: eth0
Event loop failed: Connection timed out


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

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

Title:
  Add support for RequiredForOnline in networkd

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * netplan & networkd based systems typically await networking to be
  up on boot, without any ability to specify that an interface should be
  configured, but might not be online at boot. This is a backport of the
  RequiredForOnline= feature to match optional=true in netplan.

  [Test Case]

   * Configure a netowkring interface using .link/.network file and specify 
RequiredForOnline=False
   * Bring the interface down / offline it
   * execute systemd-networkd-wait-online, which should exit immediately since 
no interfaces are required to be online

  [Regression Potential]

   * This adds a support for an additional stanza in the network files.
  This stanza is not used by default. if the stanza is used, but older
  networkd is in use, networkd will ignore this unknown stanza. Thus
  this change is backward and forward compatible. The difference is that
  boot is not blocked awaiting systemd-networkd-wait-online to timeout.

  [Other Info]
   
   * Original bug report

  Add support for RequiredForOnline in networkd

  
https://github.com/systemd/systemd/commit/c1a3890410f043fe09af8b139eb6bfe2832089be

  RequiredForOnline= denotes a link/network that does/does not require being up
  for systemd-networkd-wait-online to consider the system online; this makes it
  possible to ignore devices without modifying parameters to wait-online.

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

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

[Touch-packages] [Bug 1753776] Re: Graphics corruption just before login animation to Xorg sessions (Intel gen9 GPUs only)

2018-03-19 Thread Frederik Feichtmeier

The issue returned for me, strangely. It was gone for seferal reboots
and then returned. I can't edit my prev. comment.

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

Title:
  Graphics corruption just before login animation to Xorg sessions
  (Intel gen9 GPUs only)

Status in Mesa:
  Confirmed
Status in gdm3 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged
Status in wayland package in Ubuntu:
  Invalid

Bug description:
  Immediately after login (I enter the password and hit enter) the screen 
"crumbles" for few seconds, then all becomes normal and the system works fine. 
I have done apt update+upgrade many times, also with proposed enabled, I have 
also installed a new ISO (now i'm using the Alpha dated 20180305) but the 
problem remains. The problem happens with the x11 session but not with wayland. 
  Also problem does not show with different hardware. 

  corrado@corrado-p7-bb-0305:~$ inxi -Fx
  System:Host: corrado-p7-bb-0305 Kernel: 4.15.0-10-generic x86_64 bits: 64 
gcc: 7.3.0
 Desktop: Gnome 3.27.92 (Gtk 3.22.28-1ubuntu3) Distro: Ubuntu 
Bionic Beaver (development branch)
  Machine:   Device: desktop Mobo: ASRock model: H110M-G/M.2 serial: N/A UEFI: 
American Megatrends v: P1.10 date: 05/11/2017
  CPU:   Dual core Intel Core i3-7100 (-MT-MCP-) arch: Skylake rev.9 cache: 
3072 KB
 flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648
 clock speeds: max: 3900 MHz 1: 1018 MHz 2: 3150 MHz 3: 3153 MHz 4: 
3081 MHz
  Graphics:  Card: Intel HD Graphics 630 bus-ID: 00:02.0
 Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 
1920x1080@60.00hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2)
 version: 4.5 Mesa 18.0.0-rc4 Direct Render: Yes
  Audio: Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 
00:1f.3
 Sound: Advanced Linux Sound Architecture v: k4.15.0-10-generic
  Network:   Card: Intel Ethernet Connection (2) I219-V driver: e1000e v: 
3.2.6-k 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: 1000.2GB (1.3% used)
 ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB
  Partition: ID-1: / size: 32G used: 4.3G (15%) fs: ext4 dev: /dev/sda7
 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
  Sensors:   System Temperatures: cpu: 38.5C mobo: N/A
 Fan Speeds (in rpm): cpu: N/A
  Info:  Processes: 234 Uptime: 11 min Memory: 1144.7/7680.8MB Init: 
systemd runlevel: 5 Gcc sys: N/A
 Client: Shell (bash 4.4.181) inxi: 2.3.56 
  corrado@corrado-p7-bb-0305:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  6 15:47:50 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2018-03-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
   Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=9a36b498-59f5-4a36-81db-3046ff6bdeaa ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To

[Touch-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler!

Bill Miller, given your issue was root caused by you to having an
outdated gcc-4.8 package (now since updated), and when receiving the
update this problem is resolved, I'll mark this Fix Released.

** Changed in: gcc-4.8 (Ubuntu)
   Status: New => Fix Released

** No longer affects: linux (Ubuntu)

** Summary changed:

- 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by 
an insufficient compiler!
+ 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) 
due to outdated gcc-4.8

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04) due to outdated gcc-4.8

Status in gcc-4.8 package in Ubuntu:
  Fix Released

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  The root cause of the problem has been found to be installing the -116
  kernel without a sufficiently updated version of gcc.  In my case, my
  system received the gcc update AFTER the kernel update.

  Uninstalling the -116 kernel and reinstalling it with the updated
  version of gcc solved the problem for me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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

[Touch-packages] [Bug 1750973] Re: Program sub menus dark gray on black, thus illegible

** Description changed:

  When using a program, for example Libre Writer, when I click on file,
  open, then in the Open menu box I have the opportunity to change the
  file type from "All files" to a specific file type, when I click on "All
  files" the selection list appears. The font color for the different file
  types is a dark grey on a black background making the list items
  illegible. As I move the cursor, the font color and background change to
  "normal" black on a white background but only for the item that the
  cursor is hovering over at that moment. This makes the rest of the list
  impossible to read and moving the cursor slowly down the list, pausing
  to read each item, is a very cumbersome way to get things done.
  
  This doesn't just happen on Libre Writer but also Inkscape, Geeqie, and
  a variety of other programs and their sub menus. The only program I
  could find where this didn't happen was Firefox (58.02). Furthermore
  this happens on 3 different machines, each with a different processor,
  different graphics card and where the machine has multiple monitors, it
  happens on all monitors.
  
  All machines are running 16.04, one with the latest updates, the others
- slightly behind on updates. If I go to Settings-Appearance-Theme and
- change the theme from Ambiance to anything else, the sub menus become
- legible again.  Ambiance is the default theme.   If I switch the Theme
- back to Ambiance the problem resumes.
+ slightly behind on updates.
+ 
+ WORKAROUND: In Settings-Appearance-Theme change the theme from the
+ default Ambiance to anything else.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Feb 21 20:57:30 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: sysdig, 0.20.0, 4.4.0-112-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 
[VGA controller])
-Subsystem: NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1033]
+  NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 
[VGA controller])
+    Subsystem: NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1033]
  InstallationDate: Installed on 2014-04-20 (1404 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
-  LANGUAGE=en_US
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_US
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=8f4996c0-c2f5-449f-a35c-47f301f66803 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: 970 Extreme3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd10/12/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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
  xserver.bootTime: Wed Feb 21 19:32:42 2018
  xserver.configfile: default
  xserver.devices:

[Touch-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler!

** Project changed: gcc => gcc-4.8 (Ubuntu)

** No longer affects: nvidia-graphics-drivers-384 (Ubuntu)

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04) due to outdated gcc-4.8

Status in gcc-4.8 package in Ubuntu:
  Fix Released

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  The root cause of the problem has been found to be installing the -116
  kernel without a sufficiently updated version of gcc.  In my case, my
  system received the gcc update AFTER the kernel update.

  Uninstalling the -116 kernel and reinstalling it with the updated
  version of gcc solved the problem for me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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

[Touch-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler!

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

** Changed in: gcc-4.8 (Ubuntu)
   Status: New => Confirmed

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04) due to outdated gcc-4.8

Status in gcc-4.8 package in Ubuntu:
  Fix Released

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  The root cause of the problem has been found to be installing the -116
  kernel without a sufficiently updated version of gcc.  In my case, my
  system received the gcc update AFTER the kernel update.

  Uninstalling the -116 kernel and reinstalling it with the updated
  version of gcc solved the problem for me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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

[Touch-packages] [Bug 1750328] Re: ubuntu17.10

Steve, thank you for reporting this and helping make Ubuntu better.

Could you please run the following command once from a terminal by ensuring you 
have the package xdiagnose installed, and that you click the Yes button for 
attaching additional debugging information:
apport-collect 1750328

When reporting xorg related bugs in the future, please do so via the
above method. You can learn more about this functionality at
https://wiki.ubuntu.com/ReportingBugs.

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

** Changed in: xorg (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/1750328

Title:
  ubuntu17.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 17.10 can not see or fix screen saver or wallpaper

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-35.39~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-35-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Mon Feb 19 02:04:44 2018
  SourcePackage: xorg
  UpgradeStatus: Upgraded to artful on 2018-02-17 (1 days ago)

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

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

[Touch-packages] [Bug 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work

This bug was fixed in the package gnome-control-center -
1:3.28.0-0ubuntu1

---
gnome-control-center (1:3.28.0-0ubuntu1) bionic; urgency=medium

  [ Jeremy Bicha ]
  * New upstream release

  [ Gunnar Hjalmarsson ]
  * debian/rules:
- Add X-Ubuntu-Gettext-Domain to .desktop files and strip inline
  translations (LP: #1755473).
- Build gnome-control-center-2.0.pot.
  * Modify 71_ubuntu_dock_settings.patch:
- Drop non-existing gnome-ubuntu-panel.desktop.in from POTFILES.in.

  [ Daniel van Vugt ]
  * Add 0004-Expose-touchpad-settings-if-synaptics-is-in-use.patch
- Allow touchpad settings to work with xserver-xorg-input-synaptics
  Note that this is unneeded on GNOME on Wayland where libinput is
  always used. (LP: #1686081)

  [ Andrea Azzarone ]
  * Add auto_quit_after_goa_add.patch:
- Hide window after adding an online account from another app.
  (LP: #1754651)

 -- Jeremy Bicha   Mon, 19 Mar 2018 08:37:32 -0400

** Changed in: gnome-control-center (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't
  work

Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Invalid
Status in xubuntu-meta package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Artful:
  Confirmed
Status in mutter source package in Artful:
  Confirmed
Status in xorg source package in Artful:
  Invalid
Status in xubuntu-meta source package in Artful:
  Fix Released

Bug description:
  I'm splitting this issue off from LP: #1685542 (which made xserver-
  xorg-input-all no longer recommend xserver-xorg-input-synaptics) for
  tracking the remaining issues.

  gnome-control-center only supports libinput. If xserver-xorg-input-
  synaptics is installed (because it's used by some desktops which
  haven't been ported to libinput yet), synaptics overrides libinput.
  That makes gnome-control-center's Mouse & Touchpad settings panel only
  show basic settings and important configurations don't work.

  Questions
  -
  1. Which desktops/apps still need -synaptics?
  - Unity
  - Xfce?
  - LXDE? LXQt?
  All the other major desktops have already been ported (LP: #1417980)

  2. Can these apps be ported or removed before 18.04 LTS is released?

  3. Can the desktops be ported and how bad is it if they are not ported
  and -synaptics is no longer available?

  4. If -synaptics can't be removed completely from 18.04 LTS, does it
  make sense to have gnome-control-center Conflicts: xserver-xorg-input-
  synaptics?

  5. Is there any other way we can fix this conflict?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+subscriptions

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

[Touch-packages] [Bug 1750832] Re: xorg crash after coming from suspend

anirudha banerjee, thank you for reporting this and helping make Ubuntu
better.

1) As per your logs you are using an unsupported kernel:
4.15.3-041503-generic x86_64

If you boot into the Ubuntu kernel, is this still reproducible?

2) After the crash, are there crash files in /var/crash?

3) Did this issue start happening after an update? If so, which
specifically?

** Tags added: bios-outdated-306

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

** Changed in: xorg (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/1750832

Title:
  xorg crash after coming from suspend

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The problem i'm facing is, whenever my system revives back from
  suspended state, xorg crashes and i have restart all the applications
  that were running in the previous xorg session.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.15.3-041503-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.6)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Feb 21 19:42:44 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:15e0]
 Subsystem: ASUSTeK Computer Inc. Device [1043:15e0]
  InstallationDate: Installed on 2017-08-15 (189 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: ASUSTeK COMPUTER INC. GL553VD
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.3-041503-generic 
root=UUID=ae3afa91-6139-4a8a-a15b-39b661535c3a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL553VD.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL553VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.302:bd03/06/2017:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL553VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 19:23:46 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1

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

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

[Touch-packages] [Bug 1750608] Re: Fixup ADT tests

234-2ubuntu12.3 systemd/234-2ubuntu12.3 2018-02-23 01:39:47 UTC 1h 14m
30s  passlog   artifacts  is all green

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

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

Title:
  Fixup ADT tests

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   In artful, there are autopkgtest failures that can be improved/fixed
  with the following commits:

   * stop using ext3, and instead use ext4 as fsck.ext3 may be missing
  in the initramfs.

   * correctly parse prefixes, when parsing units and deciding which
  binaries to copy into the test image.

  
  These are changes to the setup codes of the test-suite, and no change in test 
assertions being made. Hopefully this will make adt results more green.

  [Test Case]

   * Check that autopkgtests are not failing with missing fsck.ext3
   * Check that autopkgtesta are not failing with failing to copy referenced 
binaries

  [Regression Potential]

   * No changes to the code shipped / binaries shipped

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

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

[Touch-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler!

** No longer affects: xorg (Ubuntu)

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04) by an insufficient compiler!

Status in gcc-4.8 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  The root cause of the problem has been found to be installing the -116
  kernel without a sufficiently updated version of gcc.  In my case, my
  system received the gcc update AFTER the kernel update.

  Uninstalling the -116 kernel and reinstalling it with the updated
  version of gcc solved the problem for me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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

[Touch-packages] [Bug 1750937] [NEW] 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler!

You have been subscribed to a public bug:

Running fine with nvidia-384 until this kernel update came along.  When
booted into the new kernel, got super low resolution and nvidia-settings
was missing most of its functionality - could not change resolution.

Rebooted into 4.4.0-112 kernel and all was well.

The root cause of the problem has been found to be installing the -116
kernel without a sufficiently updated version of gcc.  In my case, my
system received the gcc update AFTER the kernel update.

Uninstalling the -116 kernel and reinstalling it with the updated
version of gcc solved the problem for me.


ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
Uname: Linux 4.4.0-112-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
 GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: amd64
CurrentDesktop: LXDE
Date: Wed Feb 21 19:23:39 2018
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
 bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
 nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
 nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
GraphicsCard:
 NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: eVga.com. Corp. Device [3842:6253]
InstallationDate: Installed on 2015-03-03 (1086 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
MachineType: ASUSTeK COMPUTER INC. M11AD
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/15/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0302
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M11AD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: M11AD
dmi.product.version: System Version
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Feb 21 18:48:14 2018
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

** Affects: gcc-4.8 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: nvidia-graphics-drivers-384 (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug possible-manual-nvidia-install resolution trusty 
ubuntu
-- 
4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by 
an insufficient compiler!
https://bugs.launchpad.net/bugs/1750937
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gcc-4.8 in Ubuntu.

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

[Touch-packages] [Bug 1661869] Re: maas install fails inside of a 16.04 lxd container due to avahi problems

2018-03-19 Thread Eric Desrochers

Ok I'll sponsor the debdiff this week.

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

Title:
  maas install fails inside of a 16.04 lxd container due to avahi
  problems

Status in MAAS:
  Invalid
Status in avahi package in Ubuntu:
  In Progress
Status in lxd package in Ubuntu:
  Invalid
Status in avahi source package in Trusty:
  New
Status in lxd source package in Trusty:
  New
Status in avahi source package in Xenial:
  New
Status in lxd source package in Xenial:
  New
Status in avahi source package in Artful:
  New
Status in lxd source package in Artful:
  New

Bug description:
  [Original Description]
  The bug, and workaround, are clearly described in this mailing list thread:

  https://lists.linuxcontainers.org/pipermail/lxc-
  users/2016-January/010791.html

  I'm trying to install MAAS in a LXD container, but that's failing due
  to avahi package install problems.  I'm tagging all packages here.

  [Issue]
  Avahi sets a number of rlimits on startup including the maximum number of 
processes (nproc=2) and limits on memory usage.  These limits are hit in a 
number of cases  - specifically the maximum process limit is hit if you run lxd 
containers in 'privileged' mode such that avahi has the same uid in multiple 
containers and large networks can trigger the memory limit.

  The fix is to remove these default rlimits completely from the
  configuration file.

  [Impact]

   * Avahi is unable to start inside of containers without UID namespace 
isolation because an rlimit on the maximum number of processes is set by 
default to 2.  When a container launches Avahi, the total number of processes 
on the system in all containers exceeds this limit and Avahi is killed.  It 
also fails at install time, rather than runtime due to a failure to start the 
service.
   * Some users also have issues with the maximum memory allocation causing 
Avahi to exit on networks with a large number of services as the memory limit 
was quite small (4MB).  Refer LP #1638345

  [Test Case]

   * setup lxd (apt install lxd, lxd init, get working networking)
   * lxc launch ubuntu:16.04 avahi-test --config security.privileged=true
   * lxc exec avahi-test sudo apt install avahi-daemon

  This will fail if the parent host has avahi-daemon installed, however,
  if it does not you can setup a second container (avahi-test2) and
  install avahi there.  That should then fail (as the issue requires 2
  copies of avahi-daemon in the same uid namespace to fail)

  [Regression Potential]

   * The fix removes all rlimits configured by avahi on startup, this is
  an extra step avahi takes that most programs did not take (limiting
  memory usage, running process count, etc).  It's possible an unknown
  bug then consumes significant system resources as a result of that
  limit no longer being in place, that was previously hidden by Avahi
  crashing instead.  However I believe this risk is significantly
  reduced as this change has been shipping upstream for many months and
  have not seen any reports of new problems - however it has fixed a
  number of existing crashes/problems.

   * The main case this may not fix the issue is if they have modified
  their avahi-daemon.conf file - but it will fix new installs and most
  installs as most users don't modify the file. And users may be
  prompted on upgrade to replace the file.

  [Other Info]

   * This change already exists upstream in 0.7 which is in bionic.  SRU
  required to artful, xenial, trusty.

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

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

[Touch-packages] [Bug 1728238] Re: update-initramfs not adding i915 GuC firmware, firmware fails to load

2018-03-19 Thread Thorsten

also happens on ubuntu 18.04 on a i7-8550U

[2.084195] i915 :00:02.0: Direct firmware load for 
i915/kbl_guc_ver9_14.bin failed with error -2
[2.084196] [drm] GuC: Failed to fetch firmware i915/kbl_guc_ver9_14.bin 
(error -2)
[2.084197] [drm] GuC: Firmware can be downloaded from 
https://01.org/linuxgraphics/downloads/firmware
[2.089954] [drm] HuC: Loaded firmware i915/kbl_huc_ver02_00_1810.bin 
(version 2.0)
[2.09] [drm] GuC init failed. Firmware loading disabled.
[2.090003] [drm] Falling back from GuC submission to execlist mode
[2.090717] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0

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

Title:
  update-initramfs not adding i915 GuC firmware, firmware fails to load

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Debian:
  New

Bug description:
  The i915 Kabylake GuC firmware is failing to load on boot, and
  generating dmesg errors.  The Kabylake HuC firmware succeeds.  All
  files exist.  I've also verified the Kabylake GuC firmware matches the
  correct file size and md5 listed on 01.org.

  I then ran update-initramfs verbosely, and see that only
  /lib/firmware/i915/skl_guc_ver6_1.bin is being added.
  /lib/firmware/i915/bxt_guc_ver8_7.bin and
  /lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored.

  I'm running a Dell XPS 13 9360 w/ Kabylake on Ubuntu 17.10 and
  initramfs-tools 0.125ubuntu12.  Perhaps Broxton systems might have the
  same issue?

  Output and logs:
  -

  ls -al /lib/firmware/i915/kbl_*

  -rw-r--r-- 1 root root   8616 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1_01.bin
  lrwxrwxrwx 1 root root 19 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin
  -rw-r--r-- 1 root root 142656 Oct 20 21:12 
/lib/firmware/i915/kbl_guc_ver9_14.bin
  -rw-r--r-- 1 root root 218688 Aug 17 11:09 
/lib/firmware/i915/kbl_huc_ver02_00_1810.bin

  sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status

  GuC firmware status:
  path: i915/kbl_guc_ver9_14.bin
  fetch: FAIL
  load: NONE
  version wanted: 9.14
  version found: 0.0
  header: offset is 0; size = 0
  uCode: offset is 0; size = 0
  RSA: offset is 0; size = 0

  GuC status 0x0001:
  Bootrom status = 0x0
  uKernel status = 0x0
  MIA Core status = 0x0

  Scratch registers:
  0: 0x0
  1: 0x0
  2: 0x0
  3: 0x0
  4: 0x0
  5: 0x0
  6: 0x0
  7: 0x0
  8: 0x0
  9: 0x0
  10: 0x0
  11: 0x0
  12: 0x0
  13: 0x0
  14: 0x0
  15: 0x0

  sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status

  HuC firmware status:
  path: i915/kbl_huc_ver02_00_1810.bin
  fetch: SUCCESS
  load: SUCCESS
  version wanted: 2.0
  version found: 2.0
  header: offset is 0; size = 128
  uCode: offset is 128; size = 218304
  RSA: offset is 218432; size = 256

  HuC status 0x6000:

  dmesg

  [1.052879] hidraw: raw HID events driver (C) Jiri Kosina
  [1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control 
method not found
  [1.080320] rtsx_pci :3b:00.0: enabling device ( -> 0002)
  [1.082308] nvme nvme0: pci function :3c:00.0
  [1.095073] Setting dangerous option enable_guc_loading - tainting kernel
  [1.095075] Setting dangerous option enable_guc_submission - tainting 
kernel
  [1.097867] [drm] Memory usable by graphics device = 4078M
  [1.097869] checking generic (9000 1fb) vs hw (9000 1000)
  [1.097869] fb: switching to inteldrmfb from EFI VGA
  [1.097899] Console: switching to colour dummy device 80x25
  [1.098049] [drm] Replacing VGA console driver
  [1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [1.104157] [drm] Driver supports precise vblank timestamp query.
  [1.112506] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [1.113055] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd
  [1.298572]  nvme0n1: p1 p2
  [1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c
  [1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.433243] usb 1-1: Product: USB+PS2 Keyboard
  [1.433244] usb 1-1: Manufacturer: Generic
  [1.446460] usbcore: registered new interface driver usbhid
  [1.446461] usbhid: USB HID core driver
  [1.448067] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:0D62:001C.0001/input/input7
  [1.508451] hid-generic 0003:0D62:001C.0001: input,hidraw0: USB HID v1.10 
Keyboard [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input0
  [1.508541] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:0D62:001C.0002/input/inp

[Touch-packages] [Bug 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore

root@systemd-sru-xenial:~# dpkg-query -W systemd
systemd 229-4ubuntu21.1

Installed netplan, executed ifupdown-upgrade, rebooted:

root@systemd-sru-xenial:~# grep -e 0 -e 1 
/proc/sys/net/ipv4/conf/*/promote_secondaries
/proc/sys/net/ipv4/conf/all/promote_secondaries:0
/proc/sys/net/ipv4/conf/default/promote_secondaries:0
/proc/sys/net/ipv4/conf/eth0/promote_secondaries:0
/proc/sys/net/ipv4/conf/lo/promote_secondaries:0

Upgraded systemd to the one in proposed:

# dpkg-query -W systemd
systemd 229-4ubuntu21.2

# grep -e 0 -e 1 /proc/sys/net/ipv4/conf/*/promote_secondaries
/proc/sys/net/ipv4/conf/all/promote_secondaries:0
/proc/sys/net/ipv4/conf/default/promote_secondaries:0
/proc/sys/net/ipv4/conf/eth0/promote_secondaries:1
/proc/sys/net/ipv4/conf/lo/promote_secondaries:0

Observed change in promote_secondaries for eth0 device.

Note, when not migrating to netplan, promote_secondaries remains as 0,
preserving the current xenial behaviour under ifupdown.

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

Title:
  Networkd fail to set ip address between leases if ip address changes
  on UbuntuCore

Status in Snappy:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * networkd fails to renew a lease, specifically it fails to change IPv4 
address via DHCP renew/rebind.
   * networkd relies on a kernel feature to promote secondary IPv4 address to 
primary, upon primary address lease expiry.
   * this sysctl tunable was not enabled by default in systemd.

  [Test Case]

  Add a device, and assign two IPv4 addresses. First one, with a short
  lease time. Second one, with a different ip and a longer lease time.
  Second one should be treated as secondary ip address, and upon expiry
  of the first one, should be promoted and become primary ip address.
  The below scripted instructions simulate this:

  sudo ip link add name testleases type dummy

  sudo ip address add 192.0.2.10/27 dev testleases \
    valid_lft 5 preferred_lft 5

  sudo ip address add 192.0.2.11/27 dev testleases \
    valid_lft 11 preferred_lft 11

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.10/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global secondary dynamic testleases' \
  && echo ok || echo not ok

  sleep 6

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  sudo ip link del dev testleases

  [Regression Potential]

   * This changes the default kernel behaviour, previously upon expiry
  of the primary address, secondary addresses were removed as well.
  Which is imho silly.

  * comparing networkd renewal with isc-dhcp renewal the semantics are
  quite different. Upon acquiring new ip address, isc-dhcp would
  instantly flush existing ip address, and add a new one. Networkd add
  the new address as secondary, and waits for old one to expire first
  before promoting / switching to using the new ip address. IMHO kernel
  should have an API to promote secondary ip address to a primary one.

  * This update also applies other safe-looking options, which are
  currently also already applied via sysctls shipped in other packages

  # Source route verification
  net.ipv4.conf.default.rp_filter = 1
  net.ipv4.conf.all.rp_filter = 1

  # Do not accept source routing
  net.ipv4.conf.default.accept_source_route = 0
  net.ipv4.conf.all.accept_source_route = 0

  # Enable hard and soft link protection
  fs.protected_hardlinks = 1
  fs.protected_symlinks = 1

  * This update also applies the following upstream/bufferbloat.net
  recommended setting

  # Fair Queue CoDel packet scheduler to fight bufferbloat
  net.core.default_qdisc = fq_codel

  * [~racb] There are complex network setups out there, such as HA with
  corosync/pacemaker, OpenStack Neutron, and that kind of thing. If this
  fix were SRU'd, will all of these things in the wild cope with this
  sysctl change?

  [Other Info]

   * Original bug report

  Hi there,
  we found a replicable issue that involves the Ubuntu Core networking and 
causes complete loss of connectivity.
  We run a custom board with ubuntu core: the architecure is amrhf.
  We replicated this issue with an official Ubuntu Core image on a Raspberry 
Pi: other platform was been tested.
  It shows that it is a snap core problem which interests networkd: we use the 
default network stack based on networkd + netplan.

  Below steps to replicate the issue.

  1)S

[Touch-packages] [Bug 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore

Starting with ephemeral lxd container, on a system with
app/promote_secondaries set to 0:

root@systemd-sru-artful:~# grep -e 0 -e 1 
/proc/sys/net/ipv4/conf/*/promote_secondaries
/proc/sys/net/ipv4/conf/all/promote_secondaries:0
/proc/sys/net/ipv4/conf/default/promote_secondaries:0
/proc/sys/net/ipv4/conf/eth0/promote_secondaries:0
/proc/sys/net/ipv4/conf/lo/promote_secondaries:0
root@systemd-sru-artful:~# dpkg-query -W systemd
systemd 234-2ubuntu12.1
root@systemd-sru-artful:~# grep DHCP= 
/run/systemd/network/10-netplan-eth0.network
DHCP=ipv4

And DHCP on eth0 interface.

Upgraded systemd to:
root@systemd-sru-artful:~# dpkg-query -W systemd
systemd 234-2ubuntu12.3

Observed that promote_secondaries, got enabled on networkd DHCP managed
link:

root@systemd-sru-artful:~# grep -e 0 -e 1 
/proc/sys/net/ipv4/conf/*/promote_secondaries
/proc/sys/net/ipv4/conf/all/promote_secondaries:0
/proc/sys/net/ipv4/conf/default/promote_secondaries:0
/proc/sys/net/ipv4/conf/eth0/promote_secondaries:1
/proc/sys/net/ipv4/conf/lo/promote_secondaries:0

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

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

Title:
  Networkd fail to set ip address between leases if ip address changes
  on UbuntuCore

Status in Snappy:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * networkd fails to renew a lease, specifically it fails to change IPv4 
address via DHCP renew/rebind.
   * networkd relies on a kernel feature to promote secondary IPv4 address to 
primary, upon primary address lease expiry.
   * this sysctl tunable was not enabled by default in systemd.

  [Test Case]

  Add a device, and assign two IPv4 addresses. First one, with a short
  lease time. Second one, with a different ip and a longer lease time.
  Second one should be treated as secondary ip address, and upon expiry
  of the first one, should be promoted and become primary ip address.
  The below scripted instructions simulate this:

  sudo ip link add name testleases type dummy

  sudo ip address add 192.0.2.10/27 dev testleases \
    valid_lft 5 preferred_lft 5

  sudo ip address add 192.0.2.11/27 dev testleases \
    valid_lft 11 preferred_lft 11

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.10/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global secondary dynamic testleases' \
  && echo ok || echo not ok

  sleep 6

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  sudo ip link del dev testleases

  [Regression Potential]

   * This changes the default kernel behaviour, previously upon expiry
  of the primary address, secondary addresses were removed as well.
  Which is imho silly.

  * comparing networkd renewal with isc-dhcp renewal the semantics are
  quite different. Upon acquiring new ip address, isc-dhcp would
  instantly flush existing ip address, and add a new one. Networkd add
  the new address as secondary, and waits for old one to expire first
  before promoting / switching to using the new ip address. IMHO kernel
  should have an API to promote secondary ip address to a primary one.

  * This update also applies other safe-looking options, which are
  currently also already applied via sysctls shipped in other packages

  # Source route verification
  net.ipv4.conf.default.rp_filter = 1
  net.ipv4.conf.all.rp_filter = 1

  # Do not accept source routing
  net.ipv4.conf.default.accept_source_route = 0
  net.ipv4.conf.all.accept_source_route = 0

  # Enable hard and soft link protection
  fs.protected_hardlinks = 1
  fs.protected_symlinks = 1

  * This update also applies the following upstream/bufferbloat.net
  recommended setting

  # Fair Queue CoDel packet scheduler to fight bufferbloat
  net.core.default_qdisc = fq_codel

  * [~racb] There are complex network setups out there, such as HA with
  corosync/pacemaker, OpenStack Neutron, and that kind of thing. If this
  fix were SRU'd, will all of these things in the wild cope with this
  sysctl change?

  [Other Info]

   * Original bug report

  Hi there,
  we found a replicable issue that involves the Ubuntu Core networking and 
causes complete loss of connectivity.
  We run a custom board with ubuntu core: the architecure is amrhf.
  We replicated this issue with an official Ubuntu Core image on a Raspberry 
Pi: other platform was been tested.
  It shows that it is a snap core problem which interests networkd: we use the 
default network stack based on networkd + netplan.

  Belo

[Touch-packages] [Bug 1725861] Re: APT::AutoRemove::SuggestsImportant "false" should be the default

** Branch linked: lp:~juliank/ubuntu-release-upgrader/suggests-not-
important

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

Title:
  APT::AutoRemove::SuggestsImportant "false" should be the default

Status in apt package in Ubuntu:
  Opinion
Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged
Status in apt source package in Bionic:
  Opinion
Status in ubuntu-release-upgrader source package in Bionic:
  Triaged

Bug description:
  After an upgrade to 17.10, I took a look at how much cruft I had
  accumulated on my system, and started marking various packages 'auto'
  which I know I don't care about keeping installed.

  apt autoremove didn't remove nearly as much stuff as I expected, and
  as I dug down into some of them I found that a number of them were
  being kept because other packages on the system have Suggests:
  referencing them.

  This is asymmetric and wrong.  If Suggested packages are not
  automatically installed by default, then a Suggests should also not
  prevent a package from being automatically removed.

  After a web search led me to 'https://askubuntu.com/questions/351085
  /how-to-remove-recommended-and-suggested-dependencies-of-uninstalled-
  packages', I set 'APT::AutoRemove::SuggestsImportant "false"' in my
  apt config; apt autoremove now wants to remove 365MiB of packages from
  my system.  That is a LOT of cruft that has accumulated over the years
  of upgrades, none of which I have ever asked to be installed and all
  of which were universe or no-longer-available packages.

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

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

[Touch-packages] [Bug 1725861] Re: APT::AutoRemove::SuggestsImportant "false" should be the default

2018-03-19 Thread Julian Andres Klode

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

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

** Changed in: ubuntu-release-upgrader (Ubuntu Bionic)
   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/1725861

Title:
  APT::AutoRemove::SuggestsImportant "false" should be the default

Status in apt package in Ubuntu:
  Opinion
Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged
Status in apt source package in Bionic:
  Opinion
Status in ubuntu-release-upgrader source package in Bionic:
  Triaged

Bug description:
  After an upgrade to 17.10, I took a look at how much cruft I had
  accumulated on my system, and started marking various packages 'auto'
  which I know I don't care about keeping installed.

  apt autoremove didn't remove nearly as much stuff as I expected, and
  as I dug down into some of them I found that a number of them were
  being kept because other packages on the system have Suggests:
  referencing them.

  This is asymmetric and wrong.  If Suggested packages are not
  automatically installed by default, then a Suggests should also not
  prevent a package from being automatically removed.

  After a web search led me to 'https://askubuntu.com/questions/351085
  /how-to-remove-recommended-and-suggested-dependencies-of-uninstalled-
  packages', I set 'APT::AutoRemove::SuggestsImportant "false"' in my
  apt config; apt autoremove now wants to remove 365MiB of packages from
  my system.  That is a LOT of cruft that has accumulated over the years
  of upgrades, none of which I have ever asked to be installed and all
  of which were universe or no-longer-available packages.

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

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

[Touch-packages] [Bug 1700232] Re: aa-logprof ignores dbus access

2018-03-19 Thread Tyler Hicks

There are currently no plans to SRU this fix to Ubuntu 16.04 LTS.

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

Title:
  aa-logprof ignores dbus access

Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  [76401.788233] audit: type=1107 audit(1498111942.039:17): pid=507 uid=106 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call" bus="system" path="/org/freedesktop/DBus" 
interface="org.freedesktop.DBus" member="Hello" mask="send" 
name="org.freedesktop.DBus" pid=4955 label="/usr/sbin/ejabberdctl//su" 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=? 
terminal=?

  Is not recognized by aa-logprof .
  Ubuntu 16.04

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

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

[Touch-packages] [Bug 1488620] Re: Add LZ4 support

2018-03-19 Thread Balint Reczey

I plan uploading the attached fix in the next days after discussing this
a bit on ubuntu-devel.

** Patch added: "initramfs-tools-0.130ubuntu4.diff"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1488620/+attachment/5084004/+files/initramfs-tools-0.130ubuntu4.diff

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

Title:
  Add LZ4 support

Status in initramfs-tools package in Ubuntu:
  Triaged

Bug description:
  I found that I could enable LZ4 compression for initramfs on my vivid
  machine by installing liblz4-tool package, adding one line to
  mkinitramfs and installing a kernel compiled with CONFIG_CRYPTO_LZ4=y.

  Please include support for (legacy) LZ4.

  Attached patch includes changes made to the latest version (initramfs-
  tools_0.120ubuntu3).

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

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

[Touch-packages] [Bug 1618188] Re: systemd journal should be persistent by default: /var/log/journal should be created

Tested that systemd amd64 234-2ubuntu12.3 installed in a chroot; and
upgraded in lxd container; correctly creates /var/log/journal, with
correct group/sticky permissions set.

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

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

Title:
  systemd journal should be persistent by default: /var/log/journal
  should be created

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * System logs are lost across reboots because they are not stored
  persistently.

  [Test Case]

   * Fresh installations, or upgrades to this version of systemd, should create 
/var/log/journal and trigger automatic persistent logs.
   * Users may choose to remove said directory, or disable persistent logging 
in /etc/systemd/journald.conf

  [Regression Potential]

   * Persistent logging by default will cause logs to be flushed from
  /run to /var/log, meaning there will be less RAM used (/run is tmpfs
  backed), but increased disk usage (in /var/log). The journald daemon
  has limits set for logs, meaning they will be rotated and discarded
  and should not cause out of disk-space errors.

  [Other Info]
   
   * Original bug report

  After upgrading 14.04 -> 16.04, key services are now running on
  systemd and using the systemd journal for logging. In 14.04, key
  system logs like /var/log/messages and /var/log/syslog were
  persistent, but after the upgrade to 16.04 there has a been a
  regression of sorts: Logs sent to systemd's journald are now being
  thrown away during reboots.

  This behavior is controlled by the `Storage=` option in
  `/etc/systemd/journald.conf`. The default setting is `Storage=auto`
  which will persist logs in `/var/log/journal/`, *only if the directory
  already exists*. But the directory was not created as part of the
  14.04 -> 16.04 upgrade, so logging was being lost for a while before I
  realized what was happening.

  This issue could be solved by either creating /var/log/journal or
  changing the default Storage behavior to `Storage=persistent`, which
  would create the directory if need be.

  ## Related reference

   * `systemd` currently compounds the issue by having ["journal --disk-usage" 
report memory usage as disk 
usage](https://github.com/systemd/systemd/issues/4059), giving the impression 
that the disk is being used for logging when it isn't.
   * [User wonders where to find logs from previous boots, unaware that the 
logs were thrown 
away](http://askubuntu.com/questions/765315/how-to-find-previous-boot-log-after-ubuntu-16-04-restarts)

  ## Recommended fix

  Restoring persistent logging as the default is recommended.

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

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

[Touch-packages] [Bug 1756846] Re: bridge-utils incompatible with ifupdown on bionic

2018-03-19 Thread Alejandro Mery

thanks @albrt, I didn't know that one

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

Title:
  bridge-utils incompatible with ifupdown on bionic

Status in bridge-utils package in Ubuntu:
  Confirmed

Bug description:
  $ apt-cache policy ifupdown bridge-utils
  ifupdown:
Installed: (none)
Candidate: 0.8.16ubuntu2
Version table:
   0.8.16ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  bridge-utils:
Installed: 1.5-15ubuntu1
Candidate: 1.5-15ubuntu1
Version table:
   *** 1.5-15ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ sudo apt-get install ifupdown
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Suggested packages:
rdnssd
  The following packages will be REMOVED
bridge-utils
  The following NEW packages will be installed
ifupdown
  0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade.
  Need to get 55.2 kB of archives.
  After this operation, 119 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 ifupdown amd64 
0.8.16ubuntu2 [55.2 kB]
  Fetched 55.2 kB in 0s (1,280 kB/s)  
  (Reading database ... 251311 files and directories currently installed.)
  Removing bridge-utils (1.5-15ubuntu1) ...
  Selecting previously unselected package ifupdown.
  (Reading database ... 251286 files and directories currently installed.)
  Preparing to unpack .../ifupdown_0.8.16ubuntu2_amd64.deb ...
  Unpacking ifupdown (0.8.16ubuntu2) ...
  Setting up ifupdown (0.8.16ubuntu2) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  ureadahead will be reprofiled on next reboot
  Processing triggers for systemd (237-3ubuntu4) ...
  Processing triggers for man-db (2.8.2-1) ...

  $ sudo apt-get install bridge-utils
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Suggested packages:
ifupdown
  The following packages will be REMOVED
ifupdown
  The following NEW packages will be installed
bridge-utils
  0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade.
  Need to get 0 B/30.1 kB of archives.
  After this operation, 119 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 251318 files and directories currently installed.)
  Removing ifupdown (0.8.16ubuntu2) ...
  Selecting previously unselected package bridge-utils.
  (Reading database ... 251286 files and directories currently installed.)
  Preparing to unpack .../bridge-utils_1.5-15ubuntu1_amd64.deb ...
  Unpacking bridge-utils (1.5-15ubuntu1) ...
  Setting up bridge-utils (1.5-15ubuntu1) ...
  Processing triggers for man-db (2.8.2-1) ...

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

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

[Touch-packages] [Bug 1699216] Re: Encrypted home support

Jeremy, I apologize for the handling of this bug.

Ubuntu 18.04 no longer includes an encrypted home option in the
installer and ecryptfs-utils is being demoted to universe. See LP:
#1756840

Once ecryptfs-utils is in universe, packages in main (like
accountsservice and gnome-control-center) can't depend on it.

My understanding is that Canonical Security would eventually like to
offer ext4 based encryption for home directories, but that feature won't
be implemented in time for Ubuntu 18.04 LTS. I also understand that
Pop!_OS is switching to promoting full disk encryption in its 18.04
release.

Once again, I apologize that your patches weren't reviewed more promptly
and helpfully. I hope that we Ubuntu developers will do better next time
you propose patches. Feel free to discuss proposed desktop-related
patches with the Ubuntu Desktop team.

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

Title:
  Encrypted home support

Status in accountsservice package in Ubuntu:
  Won't Fix
Status in gnome-control-center package in Ubuntu:
  Won't Fix
Status in gnome-initial-setup package in Ubuntu:
  Won't Fix

Bug description:
  In the CreateUser D-bus call, allow the home directory of the new user
  to be encrypted.

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

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

[Touch-packages] [Bug 1699216] Re: Encrypted home support

** Changed in: accountsservice (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: gnome-initial-setup (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Encrypted home support

Status in accountsservice package in Ubuntu:
  Won't Fix
Status in gnome-control-center package in Ubuntu:
  Won't Fix
Status in gnome-initial-setup package in Ubuntu:
  Won't Fix

Bug description:
  In the CreateUser D-bus call, allow the home directory of the new user
  to be encrypted.

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

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

[Touch-packages] [Bug 1752737] Re: [2.3.0-6434] mDNS observer problems

2018-03-19 Thread Andres Rodriguez

** Changed in: maas
Milestone: None => 2.4.0beta1

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

Title:
  [2.3.0-6434] mDNS observer problems

Status in Avahi:
  Unknown
Status in MAAS:
  Triaged
Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  I see avahi-browser choking on non-utf8 characters in my rackd.log:

  ==> rackd.log <==
  2018-02-28 16:54:33 provisioningserver.utils.services: [info] mDNS 
observation process started.
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
Traceback (most recent call last):
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/maas/maas-common", line 87, in 
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
main()
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/maas/maas-common", line 83, in main
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
run()
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/maas/maas-common", line 52, in run
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
from provisioningserver.__main__ import main
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/__main__.py", line 55, 
in 
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
main()
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/utils/script.py", line 
91, in __call__
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
self.execute(argv)
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/utils/script.py", line 
86, in execute
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
args.handler.run(args)
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/utils/avahi.py", line 
221, in run
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
_observe_mdns(reader, output, args.verbose)
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/utils/avahi.py", line 
145, in _observe_mdns
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
for event in observer(events):
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/utils/avahi.py", line 
161, in _observe_resolver_found
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
for event in filter(_p_resolver_found, events):
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/utils/avahi.py", line 
125, in _extract_mdns_events
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
for event in map(parse_avahi_event, lines):
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3.5/codecs.py", line 321, in decode
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
(result, consumed) = self._buffer_decode(data, self.errors, final)
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc8 in position 240: 
invalid continuation byte
  2018-02-28 16:54:36 provisioningserver.utils.services: [critical] mDNS 
observation process failed.

  Traceback (most recent call last):
  Failure: twisted.internet.error.ProcessTerminated: A process has ended with a 
probable error condition: process ended with exit code 1.

  ==> regiond.log <==
  2018-02-28 16:54:50 regiond: [info] ::1 GET /MAAS/rpc/ HTTP/1.0 --> 200 OK 
(referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
  2018-02-28 16:55:20 regiond: [info] ::1 GET /MAAS/rpc/ HTTP/1.0 --> 200 OK 
(referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)

  ==> maas.log <==
  Feb 28 16:53:52 MAAS-RC01 maas.interface: [info] ens33 (physical) on 
MAAS-RC01: New MAC, IP binding observed: 08:eb:74:ca:d3:6f, 192.168.1.82

  Similar traceback when running from command line:

  maasuser@MAAS-RC01:~$ maas-rack observe-mdns
  {"hostname": "Apple-TV", "interface": "ens33", "address": "192.168.1.81"}
  Got SIGTERM, quitting.
  Traceback (most recent call last):
File "/usr/sbin/maas-rack", line 87, in 
  main()
File "/usr/sbin/maas-rack", line 83, in main
  run()
F

[Touch-packages] [Bug 1756846] Re: bridge-utils incompatible with ifupdown on bionic

2018-03-19 Thread Albert Damen

apt-cache show bridge-utils | grep -E "Pack|Vers|Confl"
Package: bridge-utils
Version: 1.5-15ubuntu1
Conflicts: ifupdown (<< 0.8.17)

So that conflict applies to ifupdown 0.8.16ubuntu2 in Bionic

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

Title:
  bridge-utils incompatible with ifupdown on bionic

Status in bridge-utils package in Ubuntu:
  Confirmed

Bug description:
  $ apt-cache policy ifupdown bridge-utils
  ifupdown:
Installed: (none)
Candidate: 0.8.16ubuntu2
Version table:
   0.8.16ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  bridge-utils:
Installed: 1.5-15ubuntu1
Candidate: 1.5-15ubuntu1
Version table:
   *** 1.5-15ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ sudo apt-get install ifupdown
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Suggested packages:
rdnssd
  The following packages will be REMOVED
bridge-utils
  The following NEW packages will be installed
ifupdown
  0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade.
  Need to get 55.2 kB of archives.
  After this operation, 119 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 ifupdown amd64 
0.8.16ubuntu2 [55.2 kB]
  Fetched 55.2 kB in 0s (1,280 kB/s)  
  (Reading database ... 251311 files and directories currently installed.)
  Removing bridge-utils (1.5-15ubuntu1) ...
  Selecting previously unselected package ifupdown.
  (Reading database ... 251286 files and directories currently installed.)
  Preparing to unpack .../ifupdown_0.8.16ubuntu2_amd64.deb ...
  Unpacking ifupdown (0.8.16ubuntu2) ...
  Setting up ifupdown (0.8.16ubuntu2) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  ureadahead will be reprofiled on next reboot
  Processing triggers for systemd (237-3ubuntu4) ...
  Processing triggers for man-db (2.8.2-1) ...

  $ sudo apt-get install bridge-utils
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Suggested packages:
ifupdown
  The following packages will be REMOVED
ifupdown
  The following NEW packages will be installed
bridge-utils
  0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade.
  Need to get 0 B/30.1 kB of archives.
  After this operation, 119 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 251318 files and directories currently installed.)
  Removing ifupdown (0.8.16ubuntu2) ...
  Selecting previously unselected package bridge-utils.
  (Reading database ... 251286 files and directories currently installed.)
  Preparing to unpack .../bridge-utils_1.5-15ubuntu1_amd64.deb ...
  Unpacking bridge-utils (1.5-15ubuntu1) ...
  Setting up bridge-utils (1.5-15ubuntu1) ...
  Processing triggers for man-db (2.8.2-1) ...

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

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

[Touch-packages] [Bug 1752737] Re: [2.3.0-6434] mDNS observer problems

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

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

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

Title:
  [2.3.0-6434] mDNS observer problems

Status in Avahi:
  Unknown
Status in MAAS:
  Triaged
Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  I see avahi-browser choking on non-utf8 characters in my rackd.log:

  ==> rackd.log <==
  2018-02-28 16:54:33 provisioningserver.utils.services: [info] mDNS 
observation process started.
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
Traceback (most recent call last):
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/maas/maas-common", line 87, in 
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
main()
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/maas/maas-common", line 83, in main
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
run()
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/maas/maas-common", line 52, in run
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
from provisioningserver.__main__ import main
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/__main__.py", line 55, 
in 
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
main()
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/utils/script.py", line 
91, in __call__
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
self.execute(argv)
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/utils/script.py", line 
86, in execute
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
args.handler.run(args)
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/utils/avahi.py", line 
221, in run
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
_observe_mdns(reader, output, args.verbose)
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/utils/avahi.py", line 
145, in _observe_mdns
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
for event in observer(events):
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/utils/avahi.py", line 
161, in _observe_resolver_found
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
for event in filter(_p_resolver_found, events):
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/utils/avahi.py", line 
125, in _extract_mdns_events
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
for event in map(parse_avahi_event, lines):
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3.5/codecs.py", line 321, in decode
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
(result, consumed) = self._buffer_decode(data, self.errors, final)
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc8 in position 240: 
invalid continuation byte
  2018-02-28 16:54:36 provisioningserver.utils.services: [critical] mDNS 
observation process failed.

  Traceback (most recent call last):
  Failure: twisted.internet.error.ProcessTerminated: A process has ended with a 
probable error condition: process ended with exit code 1.

  ==> regiond.log <==
  2018-02-28 16:54:50 regiond: [info] ::1 GET /MAAS/rpc/ HTTP/1.0 --> 200 OK 
(referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
  2018-02-28 16:55:20 regiond: [info] ::1 GET /MAAS/rpc/ HTTP/1.0 --> 200 OK 
(referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)

  ==> maas.log <==
  Feb 28 16:53:52 MAAS-RC01 maas.interface: [info] ens33 (physical) on 
MAAS-RC01: New MAC, IP binding observed: 08:eb:74:ca:d3:6f, 192.168.1.82

  Similar traceback when running from command line:

  maasuser@MAAS-RC01:~$ maas-rack observe-mdns
  {"hostname": "Apple-TV", "interface": "ens33", "address": "192.168.1.81"}
  Got SIGTERM, quitting.
  Traceback (most recent call last):
File "/usr/sbin/maas-rack", line 87, in

[Touch-packages] [Bug 1756846] Re: bridge-utils incompatible with ifupdown on bionic

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

** Changed in: bridge-utils (Ubuntu)
   Status: New => Confirmed

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

Title:
  bridge-utils incompatible with ifupdown on bionic

Status in bridge-utils package in Ubuntu:
  Confirmed

Bug description:
  $ apt-cache policy ifupdown bridge-utils
  ifupdown:
Installed: (none)
Candidate: 0.8.16ubuntu2
Version table:
   0.8.16ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  bridge-utils:
Installed: 1.5-15ubuntu1
Candidate: 1.5-15ubuntu1
Version table:
   *** 1.5-15ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ sudo apt-get install ifupdown
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Suggested packages:
rdnssd
  The following packages will be REMOVED
bridge-utils
  The following NEW packages will be installed
ifupdown
  0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade.
  Need to get 55.2 kB of archives.
  After this operation, 119 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 ifupdown amd64 
0.8.16ubuntu2 [55.2 kB]
  Fetched 55.2 kB in 0s (1,280 kB/s)  
  (Reading database ... 251311 files and directories currently installed.)
  Removing bridge-utils (1.5-15ubuntu1) ...
  Selecting previously unselected package ifupdown.
  (Reading database ... 251286 files and directories currently installed.)
  Preparing to unpack .../ifupdown_0.8.16ubuntu2_amd64.deb ...
  Unpacking ifupdown (0.8.16ubuntu2) ...
  Setting up ifupdown (0.8.16ubuntu2) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  ureadahead will be reprofiled on next reboot
  Processing triggers for systemd (237-3ubuntu4) ...
  Processing triggers for man-db (2.8.2-1) ...

  $ sudo apt-get install bridge-utils
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Suggested packages:
ifupdown
  The following packages will be REMOVED
ifupdown
  The following NEW packages will be installed
bridge-utils
  0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade.
  Need to get 0 B/30.1 kB of archives.
  After this operation, 119 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 251318 files and directories currently installed.)
  Removing ifupdown (0.8.16ubuntu2) ...
  Selecting previously unselected package bridge-utils.
  (Reading database ... 251286 files and directories currently installed.)
  Preparing to unpack .../bridge-utils_1.5-15ubuntu1_amd64.deb ...
  Unpacking bridge-utils (1.5-15ubuntu1) ...
  Setting up bridge-utils (1.5-15ubuntu1) ...
  Processing triggers for man-db (2.8.2-1) ...

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

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

[Touch-packages] [Bug 1756872] Re: package libfaad2:amd64 2.8.0~cvs20150510-1 failed to install/upgrade: package libfaad2:amd64 is already installed and configured

2018-03-19 Thread dino99

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

** Package changed: faad2 (Ubuntu) => dpkg (Ubuntu)

** This bug has been marked a duplicate of bug 545790
   package PACKAGE failed to install/upgrade: error writing to '': Success

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

Title:
  package libfaad2:amd64 2.8.0~cvs20150510-1 failed to install/upgrade:
  package libfaad2:amd64 is already installed and configured

Status in dpkg package in Ubuntu:
  New

Bug description:
  I had this issue at starting

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libfaad2:amd64 2.8.0~cvs20150510-1
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Sun Mar 18 17:32:28 2018
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu10
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu10
  DuplicateSignature:
   package:libfaad2:amd64:2.8.0~cvs20150510-1
   Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
   dpkg: error processing package libcrystalhd3:amd64 (--configure):
package libcrystalhd3:amd64 is already installed and configured
  ErrorMessage: package libfaad2:amd64 is already installed and configured
  InstallationDate: Installed on 2018-03-18 (0 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.25
  SourcePackage: faad2
  Title: package libfaad2:amd64 2.8.0~cvs20150510-1 failed to install/upgrade: 
package libfaad2:amd64 is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work

This bug was fixed in the package mutter - 3.28.0-2

---
mutter (3.28.0-2) unstable; urgency=medium

  [ Simon McVittie ]
  * Update Vcs-* for migration from Alioth svn to salsa.debian.org git
  * debian/gbp.conf: Add
  * Refresh patch series with gbp pq

  [ Daniel van Vugt ]
  * Add synaptics-support.patch
- Allow touchpad settings to work with xserver-xorg-input-synaptics.
  Note that this is unneeded on GNOME on Wayland where libinput is
  always used. (LP: #1686081)

  [ Jeremy Bicha ]
  * Bump debhelper compat to 11

 -- Jeremy Bicha   Sun, 18 Mar 2018 20:11:29 -0400

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

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

Title:
  If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't
  work

Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Invalid
Status in xubuntu-meta package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Artful:
  Confirmed
Status in mutter source package in Artful:
  Confirmed
Status in xorg source package in Artful:
  Invalid
Status in xubuntu-meta source package in Artful:
  Fix Released

Bug description:
  I'm splitting this issue off from LP: #1685542 (which made xserver-
  xorg-input-all no longer recommend xserver-xorg-input-synaptics) for
  tracking the remaining issues.

  gnome-control-center only supports libinput. If xserver-xorg-input-
  synaptics is installed (because it's used by some desktops which
  haven't been ported to libinput yet), synaptics overrides libinput.
  That makes gnome-control-center's Mouse & Touchpad settings panel only
  show basic settings and important configurations don't work.

  Questions
  -
  1. Which desktops/apps still need -synaptics?
  - Unity
  - Xfce?
  - LXDE? LXQt?
  All the other major desktops have already been ported (LP: #1417980)

  2. Can these apps be ported or removed before 18.04 LTS is released?

  3. Can the desktops be ported and how bad is it if they are not ported
  and -synaptics is no longer available?

  4. If -synaptics can't be removed completely from 18.04 LTS, does it
  make sense to have gnome-control-center Conflicts: xserver-xorg-input-
  synaptics?

  5. Is there any other way we can fix this conflict?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+subscriptions

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

[Touch-packages] [Bug 1756873] Re: systemd-journald crashed with SIGABRT in GI_pthread_timedjoin_ex()

2018-03-19 Thread Apport retracing service

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of private bug 1754214

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()

Status in systemd package in Ubuntu:
  New

Bug description:
  system rebooted or locked, probobly due to crypto mining process

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sat Mar 17 23:48:01 2018
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2018-03-15 (3 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  MachineType: ASUSTeK COMPUTER INC. X550LN
  ProcCmdline: /lib/systemd/systemd-journald
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __GI___pthread_timedjoin_ex (threadid=139860720314112, thread_return=0x0, 
abstime=0x0, block=) at pthread_join_common.c:89
   ?? () from /lib/systemd/libsystemd-shared-237.so
   ?? () from /lib/systemd/libsystemd-shared-237.so
   journal_file_append_object () from /lib/systemd/libsystemd-shared-237.so
   ?? () from /lib/systemd/libsystemd-shared-237.so
  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-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 05/14/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550LN.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550LN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550LN.305:bd05/14/2014:svnASUSTeKCOMPUTERINC.:pnX550LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X550LN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1756872] Re: package libfaad2:amd64 2.8.0~cvs20150510-1 failed to install/upgrade: package libfaad2:amd64 is already installed and configured

2018-03-19 Thread 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 faad2 in Ubuntu.
https://bugs.launchpad.net/bugs/1756872

Title:
  package libfaad2:amd64 2.8.0~cvs20150510-1 failed to install/upgrade:
  package libfaad2:amd64 is already installed and configured

Status in faad2 package in Ubuntu:
  New

Bug description:
  I had this issue at starting

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libfaad2:amd64 2.8.0~cvs20150510-1
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Sun Mar 18 17:32:28 2018
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu10
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu10
  DuplicateSignature:
   package:libfaad2:amd64:2.8.0~cvs20150510-1
   Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
   dpkg: error processing package libcrystalhd3:amd64 (--configure):
package libcrystalhd3:amd64 is already installed and configured
  ErrorMessage: package libfaad2:amd64 is already installed and configured
  InstallationDate: Installed on 2018-03-18 (0 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.25
  SourcePackage: faad2
  Title: package libfaad2:amd64 2.8.0~cvs20150510-1 failed to install/upgrade: 
package libfaad2:amd64 is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1756872] [NEW] package libfaad2:amd64 2.8.0~cvs20150510-1 failed to install/upgrade: package libfaad2:amd64 is already installed and configured

2018-03-19 Thread Sanjay

Public bug reported:

I had this issue at starting

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libfaad2:amd64 2.8.0~cvs20150510-1
ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
Date: Sun Mar 18 17:32:28 2018
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu10
 libgcc1 1:6.0.1-0ubuntu1
 multiarch-support 2.23-0ubuntu10
DuplicateSignature:
 package:libfaad2:amd64:2.8.0~cvs20150510-1
 Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
 dpkg: error processing package libcrystalhd3:amd64 (--configure):
  package libcrystalhd3:amd64 is already installed and configured
ErrorMessage: package libfaad2:amd64 is already installed and configured
InstallationDate: Installed on 2018-03-18 (0 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.25
SourcePackage: faad2
Title: package libfaad2:amd64 2.8.0~cvs20150510-1 failed to install/upgrade: 
package libfaad2:amd64 is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: already-installed amd64 apport-package xenial

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

Title:
  package libfaad2:amd64 2.8.0~cvs20150510-1 failed to install/upgrade:
  package libfaad2:amd64 is already installed and configured

Status in faad2 package in Ubuntu:
  New

Bug description:
  I had this issue at starting

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libfaad2:amd64 2.8.0~cvs20150510-1
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Sun Mar 18 17:32:28 2018
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu10
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu10
  DuplicateSignature:
   package:libfaad2:amd64:2.8.0~cvs20150510-1
   Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
   dpkg: error processing package libcrystalhd3:amd64 (--configure):
package libcrystalhd3:amd64 is already installed and configured
  ErrorMessage: package libfaad2:amd64 is already installed and configured
  InstallationDate: Installed on 2018-03-18 (0 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.25
  SourcePackage: faad2
  Title: package libfaad2:amd64 2.8.0~cvs20150510-1 failed to install/upgrade: 
package libfaad2:amd64 is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work

** Changed in: gnome-control-center (Ubuntu)
   Status: In Progress => Fix Committed

** Tags removed: block-proposed

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

Title:
  If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't
  work

Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  Fix Committed
Status in xorg package in Ubuntu:
  Invalid
Status in xubuntu-meta package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Artful:
  Confirmed
Status in mutter source package in Artful:
  Confirmed
Status in xorg source package in Artful:
  Invalid
Status in xubuntu-meta source package in Artful:
  Fix Released

Bug description:
  I'm splitting this issue off from LP: #1685542 (which made xserver-
  xorg-input-all no longer recommend xserver-xorg-input-synaptics) for
  tracking the remaining issues.

  gnome-control-center only supports libinput. If xserver-xorg-input-
  synaptics is installed (because it's used by some desktops which
  haven't been ported to libinput yet), synaptics overrides libinput.
  That makes gnome-control-center's Mouse & Touchpad settings panel only
  show basic settings and important configurations don't work.

  Questions
  -
  1. Which desktops/apps still need -synaptics?
  - Unity
  - Xfce?
  - LXDE? LXQt?
  All the other major desktops have already been ported (LP: #1417980)

  2. Can these apps be ported or removed before 18.04 LTS is released?

  3. Can the desktops be ported and how bad is it if they are not ported
  and -synaptics is no longer available?

  4. If -synaptics can't be removed completely from 18.04 LTS, does it
  make sense to have gnome-control-center Conflicts: xserver-xorg-input-
  synaptics?

  5. Is there any other way we can fix this conflict?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+subscriptions

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

[Touch-packages] [Bug 1572244] Re: Kubuntu requires that the WiFi password be entered twice before WiFi can be used

2018-03-19 Thread Rik Mills

Changes in #21 (debdiff) also fixed the issue in my live session tests.

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

Title:
  Kubuntu requires that the WiFi password be entered twice before WiFi
  can be used

Status in casper package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in plasma-nm package in Ubuntu:
  Confirmed
Status in casper source package in Bionic:
  Confirmed
Status in network-manager source package in Bionic:
  Fix Released
Status in plasma-nm source package in Bionic:
  Confirmed

Bug description:
  Kubuntu 16.04 ISO number 20160417.1 Xenial Final
  Bug reported against network-manager 
  Every time I tried the live Kubuntu 16.04 image on a Lenovo t420 laptop it 
requires to enter the wifi password twice before I can use the wifi. Once from 
the network icon panel, then second time a prompt on the desktop to enter the 
wifi password.

  I do not know if this is typical behavior of Kubuntu since I usually use GTK 
base desktops.
  I guess network-manager is the right package to file this report against.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.373
  CurrentDesktop: KDE
  Date: Tue Apr 19 16:48:02 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.77.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.77.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.77.128  
metric 600
  LiveMediaBuild: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160417.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  802-11-wireless  
1461084315  Tue 19 Apr 2016 04:45:15 PM UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp3s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/3 
   Wired connection 1  4957fbd0-8ffa-4de8-aa18-275e6dfdcd9e  802-3-ethernet   
1461077415  Tue 19 Apr 2016 02:50:15 PM UTC  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  no  --  --
 --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1755144] Re: No audio on vlc or videos sound or video files

2018-03-19 Thread John Rose

BTW I've also checked the versions (in Synaptic) for ffmpeg, gstreamer,
libav packages. The installed & latest versions all match.

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

Title:
No audio on vlc or videos sound or video files

Status in ffmpeg package in Ubuntu:
Incomplete
Status in pulseaudio package in Ubuntu:
Incomplete

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

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

[Touch-packages] [Bug 1756846] [NEW] bridge-utils incompatible with ifupdown on bionic

2018-03-19 Thread Alejandro Mery

Public bug reported:

$ apt-cache policy ifupdown bridge-utils
ifupdown:
  Installed: (none)
  Candidate: 0.8.16ubuntu2
  Version table:
 0.8.16ubuntu2 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
bridge-utils:
  Installed: 1.5-15ubuntu1
  Candidate: 1.5-15ubuntu1
  Version table:
 *** 1.5-15ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

$ sudo apt-get install ifupdown
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Suggested packages:
  rdnssd
The following packages will be REMOVED
  bridge-utils
The following NEW packages will be installed
  ifupdown
0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade.
Need to get 55.2 kB of archives.
After this operation, 119 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 ifupdown amd64 
0.8.16ubuntu2 [55.2 kB]
Fetched 55.2 kB in 0s (1,280 kB/s)  
(Reading database ... 251311 files and directories currently installed.)
Removing bridge-utils (1.5-15ubuntu1) ...
Selecting previously unselected package ifupdown.
(Reading database ... 251286 files and directories currently installed.)
Preparing to unpack .../ifupdown_0.8.16ubuntu2_amd64.deb ...
Unpacking ifupdown (0.8.16ubuntu2) ...
Setting up ifupdown (0.8.16ubuntu2) ...
Processing triggers for ureadahead (0.100.0-20) ...
ureadahead will be reprofiled on next reboot
Processing triggers for systemd (237-3ubuntu4) ...
Processing triggers for man-db (2.8.2-1) ...

$ sudo apt-get install bridge-utils
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Suggested packages:
  ifupdown
The following packages will be REMOVED
  ifupdown
The following NEW packages will be installed
  bridge-utils
0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade.
Need to get 0 B/30.1 kB of archives.
After this operation, 119 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 251318 files and directories currently installed.)
Removing ifupdown (0.8.16ubuntu2) ...
Selecting previously unselected package bridge-utils.
(Reading database ... 251286 files and directories currently installed.)
Preparing to unpack .../bridge-utils_1.5-15ubuntu1_amd64.deb ...
Unpacking bridge-utils (1.5-15ubuntu1) ...
Setting up bridge-utils (1.5-15ubuntu1) ...
Processing triggers for man-db (2.8.2-1) ...

** Affects: bridge-utils (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  bridge-utils incompatible with ifupdown on bionic

Status in bridge-utils package in Ubuntu:
  New

Bug description:
  $ apt-cache policy ifupdown bridge-utils
  ifupdown:
Installed: (none)
Candidate: 0.8.16ubuntu2
Version table:
   0.8.16ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  bridge-utils:
Installed: 1.5-15ubuntu1
Candidate: 1.5-15ubuntu1
Version table:
   *** 1.5-15ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ sudo apt-get install ifupdown
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Suggested packages:
rdnssd
  The following packages will be REMOVED
bridge-utils
  The following NEW packages will be installed
ifupdown
  0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade.
  Need to get 55.2 kB of archives.
  After this operation, 119 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 ifupdown amd64 
0.8.16ubuntu2 [55.2 kB]
  Fetched 55.2 kB in 0s (1,280 kB/s)  
  (Reading database ... 251311 files and directories currently installed.)
  Removing bridge-utils (1.5-15ubuntu1) ...
  Selecting previously unselected package ifupdown.
  (Reading database ... 251286 files and directories currently installed.)
  Preparing to unpack .../ifupdown_0.8.16ubuntu2_amd64.deb ...
  Unpacking ifupdown (0.8.16ubuntu2) ...
  Setting up ifupdown (0.8.16ubuntu2) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  ureadahead will be reprofiled on next reboot
  Processing triggers for systemd (237-3ubuntu4) ...
  Processing triggers for man-db (2.8.2-1) ...

  $ sudo apt-get install bridge-utils
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Suggested packages:
ifupdown
  The following packages will be REMOVED
ifupdown
  The following NEW packages will be installed
bridge-utils
  0 to upgrade, 1 to n

[Touch-packages] [Bug 1755144] Re: No audio on vlc or videos sound or video files

2018-03-19 Thread John Rose

Just tried above forced reinstalls. Still vlc won't audibly play mp3
files. all.txt (output of all packages) attached.


** Attachment added: "all.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1755144/+attachment/5083909/+files/all.txt

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

Title:
  No audio on vlc or videos sound or video files

Status in ffmpeg package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Up until a few weeks ago there was no problem with playing sound from mp3 
files. I have a pair of usb speakers. Audio plays Ok on them for video clips 
using Chrome (e.g. from BBC website). Using vlc 2.2.2 (from Ubuntu repos), 
neither a CD nor DVD (video is Ok) nor mp3 file plays audio. mp3 files play Ok 
using Rhythmbox. I've also tried vlc 3.0 with no success.
  Interestingly, the standard Videos app (Totem?) also doesn't play sound on 
these speakers either of an mp4 file (downloaded from YouTube, though it plays 
Ok on YouTube website using Chrome) or a DVD. Clemenetine plays mp3 files Ok. I 
first reported this as bug 1752267 as I thought that the problem was with vlc. 
On that bug, it was suggested that the problem is with Pulseaudio.
  Just now, I've tried to play sound through my monitor's built in speakers 
connected by hdmi (though the monitor displays Ok) with no success even though 
the built-in speakers play sound using pavucontrol when testing is invoked.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  john   2410 F pulseaudio
   /dev/snd/controlC0:  john   2410 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 12 11:06:46 2018
  InstallationDate: Installed on 2016-12-08 (458 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-404
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:

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

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

[Touch-packages] [Bug 1503762] Re: Provide systemd service

2018-03-19 Thread intrigeri

FTR a systemd unit was imported upstream:
https://gitlab.com/apparmor/apparmor/merge_requests/81

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

Title:
  Provide systemd service

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  New
Status in apparmor package in Debian:
  Confirmed
Status in apparmor package in Gentoo Linux:
  Fix Released

Bug description:
  AppArmor is in the critical path for bootup for any systems that use
  it.  Let's specify a systemd service file instead of having systemd
  use sysv compatibility mode.

  There seems to be a few bugs tracking the precursor this work, like
  https://bugs.launchpad.net/apparmor/+bug/1488179, but no actual bug
  for the systemd service itself.

  AUR has a simple service file, not sure if that would be useful -
  https://aur.archlinux.org/packages/apparmor/

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

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

[Touch-packages] [Bug 1746463] Re: apparmor profile load in stacked policy container fails

2018-03-19 Thread Stefan Bader

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verification-needed-artful' to 'verification-failed-
artful'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-artful

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

Title:
  apparmor profile load in stacked policy container fails

Status in snapd:
  Triaged
Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Won't Fix
Status in linux source package in Xenial:
  Invalid
Status in linux-gcp source package in Xenial:
  Confirmed
Status in apparmor source package in Artful:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux-gcp source package in Artful:
  Invalid
Status in apparmor source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux-gcp source package in Bionic:
  Fix Released

Bug description:
  LXD containers on an artful or bionic host with aa namespaces, should
  be able to load the lxc policies. However /lib/apparmor/profile-load
  skips that part when running in a container.

  aa-status shows 0 policies

  /lib/apparmor/profile-load is failing due to
  is_container_with_internal_policy() failing

  due to

  /sys/kernel/security/apparmor/.ns_name being empty which causes

if [ "${ns_name#lxd-*}" = "$ns_name" ] && \
   [ "${ns_name#lxc-*}" = "$ns_name" ]; then
return 1
fi

  to fail

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

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

[Touch-packages] [Bug 696435] Re: wait-for-root fails to detect nbd root

** Branch linked: lp:~xnox/britney/custom-kernels-cannot-pass

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

Title:
  wait-for-root fails to detect nbd root

Status in linux package in Ubuntu:
  Fix Released
Status in nbd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  Kernel does not generate any events when ndb-client connects /dev/nbd0 
devices, therefore it is impossible to monitor/react to the state of /dev/nbd0.

  [Fix]
  Generate change uevent when size of /dev/nbd0 changes

  [Testcase]
  * Start udevadm monitor
  * modprobe nbd
  * use ndb-client to connect something to /dev/nbd0
  * observe that there are change udev events generated on /dev/nbd0 itself

  [Regression Potential]
  There is no change to existing uevents, or their ordering.
  There is now an addition change event which will cause systemd to mark ndb 
devices as ready and trigger appropriate actions

  [Original Bug Report]

  When using an nbd root, wait-for-root blocks for 30 seconds before
  booting continues successfully.

  Using Ubuntu Natty, related packages versions:
  nbd-client 1:2.9.16-6ubuntu1
  initramfs-tools 0.98.1ubuntu9

  The wait-for-root call from /usr/share/initramfs-tools/scripts/local:
   while [ -z "${FSTYPE}" ]; do
    FSTYPE=$(wait-for-root "${ROOT}" ${ROOTDELAY:-30})

    # Run failure hooks, hoping one of them can fix up the system
    # and we can restart the wait loop.  If they all fail, abort
    # and move on to the panic handler and shell.
    if [ -z "${FSTYPE}" ] && ! try_failure_hooks; then
     break
    fi
   done

  I replaced wait-for-root with a sh script that did `set >&2`, here are the 
relevant environment variables at the time wait-for-root was called:
  ROOT='/dev/nbd0'
  ROOTDELAY=''
  ROOTFLAGS=''
  ROOTFSTYPE=''
  nbdroot='192.168.0.1,2011'

  It's probably worth noting that "nbd0: unknown partition table" was
  displayed asynchronously 1-2 seconds after wait-for-root was invoked
  and while it was still waiting. But I tried adding a "sleep 5" as the
  last line of local-top/nbd, so that the nbd message was displayed a
  lot before wait-for-root was called, and it didn't make a difference.
  So I don't think a race condition is involved in this problem.

  Temporarily I'm passing rootdelay=1 in the kernel command line to work
  around the problem.

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

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

[Touch-packages] [Bug 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string

** Branch linked: lp:~xnox/britney/custom-kernels-cannot-pass

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

Title:
  fixrtc script does not catch "Last mount time: n/a" string

Status in Snappy:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools-ubuntu-core package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in initramfs-tools-ubuntu-core source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Artful:
  Fix Committed
Status in initramfs-tools-ubuntu-core source package in Artful:
  New

Bug description:
  [TEST CASE]
  * this will be tested by the snappy team
  * without this fix the dragonboard will not boot on a freshly written image

  [REGRESSION POTENTIAL]
  * low as it only fixes an invalid string

  trying to boot a new dragonboard image results in:

  error: assertion is signed with expired public key
  "-CvQKAwRQ5h3Ffn10FILJoEZUXOv6km9FwA80-Rcj-f-6jadQ89VRswHNiEB9Lxk" by
  canonical

  this is due to a clock skew that should normally be catched by the
  fixrtc script in the initrd.

  the script is supposed to check the last mount time of the writable
  disk (SD card) and if this does not exist, fall back to the filesystem
  creation time ...

  in former versions of mkfs.ext4 the last mount time filed was simply
  left empty, so this fallback worked fine ... in xenial the fields now
  look like:

  Filesystem created:   Tue Sep 13 17:32:20 2016
  Last mount time:  n/a
  Last write time:  Tue Sep 13 17:32:20 2016

  due to the script running with "set -e" it falls over on the "n/a" and
  exists before falling back to creation time, there needs to be a check
  added for the "n/a" string now.

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

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

[Touch-packages] [Bug 1748844] Re: hud-service crash with qmessageLogger::fatal() reported at login

Occurred again today.  New report raised at +bug1756839

I raised a new report as this bug seems to happen as a pair with another
bug.  The original pair that went with this bug (+bug1753393) asked me
to raise a new bug to see if better diagnostics were included.  I have
done so and created +bug1756835.  +bug1756839 is the new copy of this
bug, created from the same login as +bug1756835

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

Title:
  hud-service crash with qmessageLogger::fatal() reported at login

Status in hud package in Ubuntu:
  New

Bug description:
  I start up my Ubuntu 16.04 machine and immediately after loginning in
  to the GUI I get a crash report about the hub-service.  Often this is
  followed by one or two other reports but not today.

  Today I followed the instructions on: 
https://help.ubuntu.com/community/ReportingBugs 
  `enabled=1` was already set in /etc/default/apport but I had not set `# 
'problem_types': ['Bug', 'Package'],` in /etc/apport/crashdb.conf until this 
morning.  This had the effect of a bug report appearing to be sent in the 
background but no launchpad page opening.  After setting both of the above I 
did `ubuntu-bug hud` on the command line to generate this report.  

  This PC was a fresh install a few months ago.  As far as I can recall
  it has been generating the crash report message for most of that time.

  It would be nice if I could at least silence the error.  Ideally I
  would like to fix the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: hud 14.10+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 12 09:11:35 2018
  InstallationDate: Installed on 2017-11-16 (87 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: hud
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.hud.log:
   This application failed to start because it could not find or load the Qt 
platform plugin "minimal"
   in "".
   
   Reinstalling the application may fix this problem.

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

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

[Touch-packages] [Bug 1753393] Re: window-stack-bridge crashed with SIGABRT in QMessageLogger::fatal()

Changing report to Public so that others can see it.

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

Title:
  window-stack-bridge crashed with SIGABRT in QMessageLogger::fatal()

Status in hud package in Ubuntu:
  Invalid

Bug description:
  After powering on my PC and logging in I was presented with two
  automated error reporting windows.  The first led me to +bug1748844
  the second prompted me to create a new error reporting message.  By
  the time this second report happened I had Google Chrome and Synergy
  running.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: hud 14.10+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Mon Mar  5 08:20:42 2018
  ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/window-stack-bridge
  InstallationDate: Installed on 2017-11-16 (108 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/window-stack-bridge
  ProcEnviron:
   PATH=(custom, user)
   SHELL=/bin/bash
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: hud
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/lib/x86_64-linux-gnu/libQt5Core.so.5
   QObjectPrivate::QObjectPrivate(int) () from 
/lib/x86_64-linux-gnu/libQt5Core.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
   QDBusAbstractInterface::QDBusAbstractInterface(QString const&, QString 
const&, char const*, QDBusConnection const&, QObject*) () from 
/usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
   QDBusConnectionInterface::QDBusConnectionInterface(QDBusConnection const&, 
QObject*) () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
  Title: window-stack-bridge crashed with SIGABRT in QMessageLogger::fatal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo
  upstart.hud.log:
   This application failed to start because it could not find or load the Qt 
platform plugin "minimal"
   in "".
   
   Reinstalling the application may fix this problem.

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

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

[Touch-packages] [Bug 1753393] Re: window-stack-bridge crashed with SIGABRT in QMessageLogger::fatal()

Would +bug1756835 work better as a link?

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

Title:
  window-stack-bridge crashed with SIGABRT in QMessageLogger::fatal()

Status in hud package in Ubuntu:
  Invalid

Bug description:
  After powering on my PC and logging in I was presented with two
  automated error reporting windows.  The first led me to +bug1748844
  the second prompted me to create a new error reporting message.  By
  the time this second report happened I had Google Chrome and Synergy
  running.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: hud 14.10+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Mon Mar  5 08:20:42 2018
  ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/window-stack-bridge
  InstallationDate: Installed on 2017-11-16 (108 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/window-stack-bridge
  ProcEnviron:
   PATH=(custom, user)
   SHELL=/bin/bash
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: hud
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/lib/x86_64-linux-gnu/libQt5Core.so.5
   QObjectPrivate::QObjectPrivate(int) () from 
/lib/x86_64-linux-gnu/libQt5Core.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
   QDBusAbstractInterface::QDBusAbstractInterface(QString const&, QString 
const&, char const*, QDBusConnection const&, QObject*) () from 
/usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
   QDBusConnectionInterface::QDBusConnectionInterface(QDBusConnection const&, 
QObject*) () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
  Title: window-stack-bridge crashed with SIGABRT in QMessageLogger::fatal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo
  upstart.hud.log:
   This application failed to start because it could not find or load the Qt 
platform plugin "minimal"
   in "".
   
   Reinstalling the application may fix this problem.

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

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

[Touch-packages] [Bug 1753393] Re: window-stack-bridge crashed with SIGABRT in QMessageLogger::fatal()

The problem happened again this morning.

As requested above I have filed a new report at #1756835.  Hopefully
this will include more useful diagnostic information.

** Information type changed from Private to Public

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

Title:
  window-stack-bridge crashed with SIGABRT in QMessageLogger::fatal()

Status in hud package in Ubuntu:
  Invalid

Bug description:
  After powering on my PC and logging in I was presented with two
  automated error reporting windows.  The first led me to +bug1748844
  the second prompted me to create a new error reporting message.  By
  the time this second report happened I had Google Chrome and Synergy
  running.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: hud 14.10+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Mon Mar  5 08:20:42 2018
  ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/window-stack-bridge
  InstallationDate: Installed on 2017-11-16 (108 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/window-stack-bridge
  ProcEnviron:
   PATH=(custom, user)
   SHELL=/bin/bash
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: hud
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/lib/x86_64-linux-gnu/libQt5Core.so.5
   QObjectPrivate::QObjectPrivate(int) () from 
/lib/x86_64-linux-gnu/libQt5Core.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
   QDBusAbstractInterface::QDBusAbstractInterface(QString const&, QString 
const&, char const*, QDBusConnection const&, QObject*) () from 
/usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
   QDBusConnectionInterface::QDBusConnectionInterface(QDBusConnection const&, 
QObject*) () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
  Title: window-stack-bridge crashed with SIGABRT in QMessageLogger::fatal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo
  upstart.hud.log:
   This application failed to start because it could not find or load the Qt 
platform plugin "minimal"
   in "".
   
   Reinstalling the application may fix this problem.

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

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

[Touch-packages] [Bug 1753776] Re: Graphics corruption just before login animation to Xorg sessions (Intel gen9 GPUs only)