[Touch-packages] [Bug 1679704] Re: libvirt profile is blocking global setrlimit despite having no rlimit rule

[Frank Heimes]

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
   Importance: Undecided => Critical

** Changed in: ubuntu-power-systems
   Status: New => In Progress

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

Title:
  libvirt profile is blocking global setrlimit despite having no rlimit
  rule

Status in The Ubuntu-power-systems project:
  In Progress
Status in apparmor package in Ubuntu:
  In Progress

Bug description:
  Hi,
  while debugging bug 1678322 I was running along apparmor issues.
  Thanks to jjohansen we debugged some of it and eventually I was asked to 
report to a bug.

  Symptom:
  [ 8976.950635] audit: type=1400 audit(1491310016.224:48): apparmor="DENIED" 
operation="setrlimit" profile="/usr/sbin/libvirtd" pid=10034 comm="libvirtd" 
rlimit=memlock value=1610612736

  But none of the profiles has any rlimit statement in it:
  $ grep -Hirn limit /etc/apparmor*
  /etc/apparmor.d/sbin.dhclient:58:  # such, if the dhclient3 daemon is 
subverted, this effectively limits it to
  /etc/apparmor.d/abstractions/ubuntu-helpers:16:# Limitations:
  /etc/apparmor.d/abstractions/ubuntu-helpers:64:  # in limited libraries so 
glibc's secure execution should be enough to not
  /etc/apparmor.d/cache/.features:13:rlimit {mask {cpu fsize data stack core 
rss nproc nofile memlock as locks sigpending msgqueue nice rtprio rttime

  
  The profile contains a child profile which makes reading the dumps a bit 
painful, but I'll attach them anyway for you to take a look.
  To "recreate" if needed check out bug 1678322 - TL;DR hot-add some VFs via 
libvirt.

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

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

[Touch-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service

[Daniel van Vugt]

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

OK, let's track this in bug 1749546 unless/until the fix for that proves
to not help with this one.

** Changed in: bluez (Ubuntu)
   Importance: Critical => High

** This bug has been marked a duplicate of bug 1749546
   Booting a live session is slow - fontconfig regenerates its font cache

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

Title:
  Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut:
  Failed to activate service 'org.bluez': timed out
  (service_start_timeout=25000ms)

Status in blueman package in Ubuntu:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Also causing the long time to desktop from try/install livesession
  dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  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
  CurrentDesktop: XFCE
  Date: Sat Mar 10 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:

  rfkill:

  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: 
  [1520681416.8951] Loaded device plugin: NMBluezManager
  (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-
  bluetooth.so)

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

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

[Touch-packages] [Bug 1760435] Re: Use Ubuntu language packs for various Unity packages

[Simon Quigley]

I have uploaded these packages to Bileto, and I would like an ACK before
landing them.

https://bileto.ubuntu.com/#/ticket/3221

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

Title:
  Use Ubuntu language packs for various Unity packages

Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  New
Status in unity-greeter package in Ubuntu:
  New
Status in unity-lens-applications package in Ubuntu:
  New
Status in unity-lens-files package in Ubuntu:
  New
Status in unity-lens-music package in Ubuntu:
  New
Status in unity-lens-photos package in Ubuntu:
  New
Status in unity-lens-video package in Ubuntu:
  New
Status in unity-scope-calculator package in Ubuntu:
  New
Status in unity-scope-devhelp package in Ubuntu:
  New
Status in unity-scope-home package in Ubuntu:
  New
Status in unity-scope-manpages package in Ubuntu:
  New

Bug description:
  The Unity family of packages was previously part of standard Ubuntu.
  Thus all the translation templates were made available to the
  translators via Launchpad, and the translations were included in the
  language packs.

  Since those packages are no longer part of standard Ubuntu, they have
  been moved from main to universe. And translations are dropped.

  At the moment, it is feasible for us to keep using langpacks.

  That means adding "X-Ubuntu-Use-Langpack: yes" to their debian/control
  and doing an upload.

  See: https://community.ubuntu.com/t/translation-of-unity-packages/4919

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

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

[Touch-packages] [Bug 1744366] Re: xfce power manager shows wrong battery life information (Lbuntu 16.04.3)

[Simon Quigley]

Have you tried live CDs of other operating systems to see if this is a
Lubuntu-specific issue?

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

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

Title:
  xfce power manager shows wrong battery life information (Lbuntu
  16.04.3)

Status in upower package in Ubuntu:
  Incomplete

Bug description:
  As per title xfce power manager (version 1.4.4-4ubuntu2) on my Lubuntu
  16.04.3 shows a wrong battery life. What happens is that I plug in the
  laptop, it tells me the battery is 100% I unplug the write and I can
  see after maybe 10 minutes that the battery level lowered.

  I check and it gives me something like 80% and then, suddenly the
  laptop turns of because the battery is discharged.

  When i plug it back it shows as the battery is either charging
  correctly or charging and the percentage is over 70%.

  The battery is a few months old, so I think the problem lies in xfce
  power manager which displays the wrong information.Bug #1216594 opened
  in 2013 is very similar to my case, however that bug report was closed
  not because it was fixed but because it expired after 60 days.

  I tried 'upower -d' and it gives me the same info as the power manager.
  The output was:
  Device: /org/freedesktop/UPower/devices/line_power_ADP1
native-path:  ADP1
power supply: yes
updated:  XX XX XXX  17:58:48 GMT (815 seconds ago)
has history:  no
has statistics:   no
line-power
  warning-level:   none
  online:  yes
  icon-name:  'ac-adapter-symbolic'

  Device: /org/freedesktop/UPower/devices/battery_BAT0
native-path:  BAT0
vendor:   Hewlett-Packard
model:Primary
power supply: yes
updated:  Fri 19 Jan 2018 18:10:34 GMT (109 seconds ago)
has history:  yes
has statistics:   yes
battery
  present: yes
  rechargeable:yes
  state:   charging
  warning-level:   none
  energy:  22.2592 Wh
  energy-empty:0 Wh
  energy-full: 26.048 Wh
  energy-full-design:  26.048 Wh
  energy-rate: 20.0392 W
  voltage: 16.444 V
  time to full:11.3 minutes
  percentage:  85%
  capacity:100%
  technology:  lithium-ion
  icon-name:  'battery-full-charging-symbolic'
History (charge):
  151638543485.000  charging
History (rate):
  151638543420.039  charging

  Device: /org/freedesktop/UPower/devices/DisplayDevice
power supply: yes
updated:  XX XX XXX  18:10:34 GMT (109 seconds ago)
has history:  no
has statistics:   no
battery
  present: yes
  state:   charging
  warning-level:   none
  energy:  22.2592 Wh
  energy-full: 26.048 Wh
  energy-rate: 20.0392 W
  time to full:11.3 minutes
  percentage:  85%
  icon-name:  'battery-full-charging-symbolic'

  Daemon:
daemon-version:  0.99.4
on-battery:  no
lid-is-closed:   no
lid-is-present:  yes
critical-action: HybridSleep

  Any ideas?

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

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

[Touch-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

[Daniel van Vugt]

I can't find any fix that exists upstream yet. It sounds like Red Hat
just reverted the problematic commit.

If you can't find out where an upstream fix exists (in git.kernel.org) then 
please start by creating an upstream bug report for it here: 
https://bugzilla.kernel.org/enter_bug.cgi?product=Drivers=Bluetooth

And then let us know here what the ID of the new bug is.

** Changed in: bluez (Ubuntu)
   Status: Triaged => Incomplete

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

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  Incomplete
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  STEPS TO REPRODUCE:
  1. Connect to Bluetooth audio device
  2. Suspend & Resume
  3. Reconnect to Bluetooth device.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:5025 acl:32 sco:0 events:202 errors:0
TX bytes:5785 acl:32 sco:0 commands:103 errors:0

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

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

[Touch-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

[Daniel van Vugt]

Thanks for the info.

I think we should patch this into Ubuntu 18.04 _after_ it gets released
in 3 weeks.

The reason is that I want to prioritize 18.04 releasing with mature
bluez and pulseaudio packages that have not changed in a long time on
release day. So there can't be any last-minute surprises. Then after
release day we can patch in bug fixes like this one, but will also have
the release version to fall back on should anything go wrong.

Also, this bug is not major enough to justify patching this close to
release. Even most users of Bluetooth audio I suspect will never notice
it.

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

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  Incomplete
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  STEPS TO REPRODUCE:
  1. Connect to Bluetooth audio device
  2. Suspend & Resume
  3. Reconnect to Bluetooth device.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:5025 acl:32 sco:0 events:202 errors:0
TX bytes:5785 acl:32 sco:0 commands:103 errors:0

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

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

[Touch-packages] [Bug 1266911] Re: Lightdm hangs when switching sessions

[Simon Quigley]

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 1266911

and any other logs that are relevant for this particular issue.

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

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

Title:
  Lightdm hangs when switching sessions

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Lightdm hangs when attempting to select lx Games or Lubuntu Nexus 7
  sessions. This discovered for the Lubuntu 14.04 LTS testdrive via the
  virtual machine.

  Ubuntu Trusty Tahr (development branch)
  14.04

  lightdm:
     Installed: 1.9.5-0ubuntu1
     Candidate:  1.9.5-oubuntu1
     Version table:
   *** 1.9.5-0ubuntu1 0
     500   http://us.archive.ubuntu.com/ubuntu/ trusty/main i386 
Packages
     100   /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1706939] Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)"

[Daniel van Vugt]

My comment in #27 was current for daily images up to a few days ago.

Today I am using image 20180404 and can't reproduce the issue. So
Incomplete.

Like Doug I do find many systems still hang instead of shutting down
with 20180404, but there are different reasons for those and the error
message this bug is about does not appear. So they should be different
bugs.


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

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

Title:
  A live session can't be shut down due to "[ ***  ] (2 of 2) A start
  job is running for ... (21s / no limit)"

Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete
Status in gdm3 source package in Bionic:
  Incomplete
Status in systemd source package in Bionic:
  Incomplete

Bug description:
  Test case:
  Boot to live session using current or recent image
  Attempt to restart, shutdown or even log out.
  Hangs basically forever with:

  [ ***  ] (2 of 2) A start job is running for Hold until boot process
  finishes up (21s / no limit)

  or

  [ *** ] (2 of 2) A start job is running for Wait for Network to be
  Configured (21s / no limit)

  ---
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.24.2-1ubuntu9
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: GNOME
  Date: Thu Jul 27 10:15:57 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2017-07-27T10:13:04.127685

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

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

[Touch-packages] [Bug 282954] Re: Wish: Quiet installation option

[Simon Quigley]

I believe that Ubiquity is now quiet, and really doesn't emit any noise.

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

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

Title:
  Wish: Quiet installation option

Status in pulseaudio package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: ubiquity

  I often test new systems (alphas, betas, mockups) when the house is
  asleep. Therefore, it is essential to me that the system not beep or
  be otherwise noisy. I propose an option in the Advanced dialog (at the
  end of the installation wizard) for disabling the PC Speaker and
  desktop (Gnome/KDE) sound theme. The advanced dialog contains only two
  options at the moment, so clutter is not a worry.

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

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

[Touch-packages] [Bug 1760934] Re: Sound not working on HP x2 10-p030nl - Realtek rt5640

[Daniel van Vugt]

If pulseaudio isn't running then that's the main issue. It's hard to
declare a bug is in a program when that program isn't even running yet.

Please try:

1. Run 'journalctl -b > journal.txt' and attach the resulting file here.

2. Run 'pulseaudio -vv' and paste the output here.

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

Title:
  Sound not working on HP x2 10-p030nl - Realtek rt5640

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Audio doesn't work on every kernel I tried. I also used this
  https://github.com/plbossart/UCM, but this results in a pulseaudio
  crash. See this for more information:
  https://github.com/plbossart/UCM/issues/27

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  Uname: Linux 4.16.0-rc6+ x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer', 
'/dev/sequencer2', '/dev/sequencer'] failed with exit code 1:
  CurrentDesktop: KDE
  Date: Tue Apr  3 19:19:35 2018
  InstallationDate: Installed on 2018-03-27 (6 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827C
  dmi.board.vendor: HP
  dmi.board.version: 93.23
  dmi.chassis.type: 32
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.30:bd10/25/2017:svnHP:pnHPx2Detachable10-p0XX:pvr:rvnHP:rn827C:rvr93.23:cvnHP:ct32:cvrChassisVersion:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP x2 Detachable 10-p0XX
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable

[Daniel van Vugt]

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

Takis,

The fix for bug 1710637 is only in Ubuntu 17.10 and later, so please try
17.10 or 18.04.

Please also open a new bug if you think you have a new issue.

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

Title:
  Alt+left/right arrows switch between tty consoles (Gnome Shell
  vanishes), cannot disable

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  I'm used to using alt+left/right arrow to navigate back and forward in
  web browsers and elsewhere (nautilus)...  But on this fresh install of
  Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty
  consoles (the ctrl+alt+f1 ones).  But it's not listed as one of the
  shortcuts in the "keyboard" menu, so I don't know how to disable it...

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

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

[Touch-packages] [Bug 1187981] Re: symbol conflicts in libtimezonemap1

[Simon Quigley]

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect https://api.launchpad.net/1.0/bugs/1187981

and any other logs that are relevant for this particular issue.

** Changed in: gnome-control-center
   Status: Confirmed => Incomplete

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Incomplete

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

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

** Changed in: unity-control-center (Ubuntu)
   Status: New => Incomplete

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

Title:
  symbol conflicts in libtimezonemap1

Status in gnome-control-center:
  Incomplete
Status in gnome-control-center package in Ubuntu:
  Incomplete
Status in libtimezonemap package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Incomplete
Status in unity-control-center package in Ubuntu:
  Incomplete

Bug description:
  In gnome-control-center 3.8 all built in panels are statically linked.
  When the indicator-datetime panel loads it is picking up the symbols
  from the gnome datetime panel rather than the ones in libtimezonemap1,
  causing g-c-c to segfault.

  All public symbols in libtimezonemap1 need to renamed to avoid
  conflict. Likewise this might apply to any other g-c-c plugins that
  have code cut+paste from the built in gnome panels.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-datetime 12.10.3daily13.05.06.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3
  Uname: Linux 3.9.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  Date: Thu Jun  6 12:35:40 2013
  InstallationDate: Installed on 2012-09-23 (256 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha 
amd64(20120922)
  MarkForUpload: True
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1187981/+subscriptions

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

[Touch-packages] [Bug 1760598] Re: I/O Error after clicking "reboot now" - Ubuntu font missing from casper shutdown

[Martin Wimpress]

** Changed in: ubuntu-mate
   Status: New => Invalid

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

Title:
  I/O Error after clicking "reboot now" - Ubuntu font missing from
  casper shutdown

Status in ubuntu-mate:
  Invalid
Status in casper package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Confirmed
Status in ubuntu-mate-welcome package in Ubuntu:
  Invalid

Bug description:
  ubuntu Plymouth theme now correctly uses Ubuntu font, meaning it needs
  to be cached for display of the shutdown message.

  We really should be using shutdown initramfs on the livecd

  --

  Tested in Virtualbox VM.
  Ubuntu MATE works after force-reboot, but after I click on "restart now" 
after completing the installation, the screen shows me this:

  req_error: I/O error, dev sr0, sector 1488792

  And the above message loops a couple times, and wont turn off the
  computer to restart.

  No error happens after force reboot, and the OS boots properly, but
  I'm curious as to what's causing this.

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

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

[Touch-packages] [Bug 1739531] Re: apport-collect SHOULD NOT collect gnome-shell command history and favorites

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-core-dev/ubuntu/bionic/apport/ubuntu

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

Title:
  apport-collect SHOULD NOT collect gnome-shell command history and
  favorites

Status in apport package in Ubuntu:
  In Progress
Status in apport source package in Bionic:
  In Progress

Bug description:
  In https://bugs.launchpad.net/ubuntu/+source/gnome-
  shell/+bug/1739525/comments/4, I ran apport-collect for that bug
  report.

  To my horror, it posted "org.gnome.shell command-history" and "favorites" in 
the "GsettingsChanges.txt"!
  https://launchpadlibrarian.net/349970997/GsettingsChanges.txt

  It's _completely_ reasonable to see:
   * enabled-extensions
   * org.gnome.shell.* diffs
   * org.gnome.desktop.* diffs

  But it is _NOT_ acceptable (privacy reasons) to automatically harvest
  a user's favorites in the gnome-shell, nor their command histories.

  _IF_ we must harvest for bug-data gathering, it MUST come in a secure
  mechanism that is private only to submitter + the assigned dev.

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

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

[Touch-packages] [Bug 1739531] Re: apport-collect SHOULD NOT collect gnome-shell command history and favorites

[Brian Murray]

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

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

Title:
  apport-collect SHOULD NOT collect gnome-shell command history and
  favorites

Status in apport package in Ubuntu:
  In Progress
Status in apport source package in Bionic:
  In Progress

Bug description:
  In https://bugs.launchpad.net/ubuntu/+source/gnome-
  shell/+bug/1739525/comments/4, I ran apport-collect for that bug
  report.

  To my horror, it posted "org.gnome.shell command-history" and "favorites" in 
the "GsettingsChanges.txt"!
  https://launchpadlibrarian.net/349970997/GsettingsChanges.txt

  It's _completely_ reasonable to see:
   * enabled-extensions
   * org.gnome.shell.* diffs
   * org.gnome.desktop.* diffs

  But it is _NOT_ acceptable (privacy reasons) to automatically harvest
  a user's favorites in the gnome-shell, nor their command histories.

  _IF_ we must harvest for bug-data gathering, it MUST come in a secure
  mechanism that is private only to submitter + the assigned dev.

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

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

[Touch-packages] [Bug 1761121] Re: Latest intel ucode update halts my system during boot to graphic session

[Aalok Sathe]

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

** This bug has been marked a duplicate of bug 1759920
   intel-microcode 3.20180312.0 causes lockup at login screen(w/ 
linux-image-4.13.0-37-generic)

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

Title:
  Latest intel ucode update halts my system during boot to graphic
  session

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  It seems that this 
  iucode_tool -lS /lib/firmware/intel-ucode/
  iucode_tool: system has processor(s) with signature 0x000306a9
  selected microcodes:
  001: sig 0x000306a9, pf mask 0x12, 2018-02-07, rev 0x001f, size 13312
  microcode update prevents me to boot to graphic session on any(4.13.0.38[37]) 
kernel.
  I can successfully boot to the recovery console.
  In some of failed attempts i got "NMI deadlock detected on CPU0,1,3 in mkswap"
  I guess nvidia-384 has some issues and conflicts with updated microcode.
  I have to disable microcode update with 
IUCODE_TOOL_EXTRA_OPTIONS="--date-after=2018-02-07" to get my unity session 
back.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Это каталог: 
'/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.9)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  BootLog:
   lvmetad is not active yet, using direct activation during sysinit
   /dev/mapper/lmvg-ubunturoot: clean, 421309/1310720 files, 3715643/5242880 
blocks
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Apr  4 12:39:37 2018
  DistUpgraded: 2016-04-19 13:48:02,030 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Не удалось выполнить 
процесс-потомок «./xorg_fix_proprietary.py» (No such file or directory) (8))
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK107 [GeForce GT 640] [10de:0fc1] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GK107 [GeForce GT 640] [1458:353e]
  InstallationDate: Installed on 2012-09-26 (2015 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=/dev/mapper/lmvg-ubunturoot ro nouveau.modeset=0 
rd.driver.blacklist=nouveau video=vesa:off nvidia_drm.modeset=1 zswap.enabled=0 
quiet
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-19 (714 days ago)
  dmi.bios.date: 10/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-DS2 DVI
  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.:bvrF1:bd10/12/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-DS2DVI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.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: 

[Touch-packages] [Bug 1256201] Re: Installation xubuntu crash

[Simon Quigley]

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 1256201

and any other logs that are relevant for this particular issue.

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

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

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

Title:
  Installation xubuntu crash

Status in network-manager package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Incomplete

Bug description:
  Failed installation ... sistem installation crash

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: ubiquity 2.15.26
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.336ubuntu1
  Date: Fri Nov 29 06:29:12 2013
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash -- debian-installer/language=it 
keyboard-configuration/layoutcode?=it
  LiveMediaBuild: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=it_IT.UTF-8
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1761338] [NEW] Login screen upside down(reversed)

[roussel geoffrey]

Public bug reported:

Ubuntu 17.10, Nvidia drivers installed (official package nvidia-384).
Computer: HP laptop: HP 14-008nf (with graphics: integrated + NVidia Geforce 
940mx)

Sometimes when i reboot the Ubuntu login screen is reversed, all the
screen is upside down, then just rebooting without changing anything and
it's back to normal...but not all the time (sometimes after booting to
Windows also, cause i have dual boot)

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-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 7.2.0 (Ubuntu 7.2.0-8ubuntu3.2)
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr  5 01:55:57 2018
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.13.0-21-generic, x86_64: installed
 bbswitch, 0.8, 4.13.0-37-generic, x86_64: installed
 nvidia-384, 384.111, 4.13.0-21-generic, x86_64: installed
 nvidia-384, 384.111, 4.13.0-37-generic, x86_64: installed
 virtualbox, 5.1.34, 4.13.0-37-generic, x86_64: installed
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company HD Graphics 520 [103c:820a]
   Subsystem: Hewlett-Packard Company GM108M [GeForce 940MX] [103c:820a]
InstallationDate: Installed on 2018-03-16 (19 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. 
 Bus 001 Device 002: ID 05c8:038e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Pavilion Notebook
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic.efi.signed 
root=UUID=ce30d1fb-9d99-4019-8b24-6cd1462d771d ro quiet splash pci=noaer 
vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/04/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.08
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 820A
dmi.board.vendor: HP
dmi.board.version: 82.26
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.08:bd07/04/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn820A:rvr82.26:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
dmi.product.name: HP Pavilion Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
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

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


** Tags: amd64 apport-bug artful 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/1761338

Title:
  Login screen upside down(reversed)

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10, Nvidia drivers installed (official package nvidia-384).
  Computer: HP laptop: HP 14-008nf (with graphics: integrated + NVidia Geforce 
940mx)

  Sometimes when i reboot the Ubuntu login screen is reversed, all the
  screen is upside down, then just rebooting without changing anything
  and it's back to normal...but not all the time (sometimes after
  booting to Windows also, cause i have dual boot)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-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
   

[Touch-packages] [Bug 1752737] Re: [2.3.0-6434] mDNS observer problems

[Andres Rodriguez]

** Changed in: maas
Milestone: 2.4.0beta2 => 2.4.0beta3

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

[Touch-packages] [Bug 1761323] Re: systemd-journald crashed with SIGABRT in fsync()

[Apport retracing service]

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

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 #1750855, 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/1761323/+attachment/5101998/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of private bug 1750855

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

Title:
  systemd-journald crashed with SIGABRT in fsync()

Status in systemd package in Ubuntu:
  New

Bug description:
  no additional information

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  Date: Wed Apr  4 22:40:44 2018
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2017-06-04 (304 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57bc Realtek Semiconductor Corp. 
   Bus 001 Device 005: ID 0fce:01e5 Sony Ericsson Mobile Communications AB 
   Bus 001 Device 004: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X751LJ
  ProcCmdline: /lib/systemd/systemd-journald
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=0b9adc3a-8318-4a04-a408-4e68ff87d167 ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   fsync (fd=21) at ../sysdeps/unix/sysv/linux/fsync.c:27
   ?? () 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
   journal_file_append_entry () from /lib/systemd/libsystemd-shared-237.so
  Title: systemd-journald crashed with SIGABRT in fsync()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X751LJ.706
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X751LJ
  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.:bvrX751LJ.706:bd12/07/2015:svnASUSTeKCOMPUTERINC.:pnX751LJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX751LJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X751LJ
  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/1761323/+subscriptions

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

[Touch-packages] [Bug 1739531] Re: apport-collect SHOULD NOT collect gnome-shell command history and favorites

[Brian Murray]

** Changed in: apport (Ubuntu Bionic)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

Title:
  apport-collect SHOULD NOT collect gnome-shell command history and
  favorites

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

Bug description:
  In https://bugs.launchpad.net/ubuntu/+source/gnome-
  shell/+bug/1739525/comments/4, I ran apport-collect for that bug
  report.

  To my horror, it posted "org.gnome.shell command-history" and "favorites" in 
the "GsettingsChanges.txt"!
  https://launchpadlibrarian.net/349970997/GsettingsChanges.txt

  It's _completely_ reasonable to see:
   * enabled-extensions
   * org.gnome.shell.* diffs
   * org.gnome.desktop.* diffs

  But it is _NOT_ acceptable (privacy reasons) to automatically harvest
  a user's favorites in the gnome-shell, nor their command histories.

  _IF_ we must harvest for bug-data gathering, it MUST come in a secure
  mechanism that is private only to submitter + the assigned dev.

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

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

[Touch-packages] [Bug 1761294] Re: Network configuration doesn't survive reboots after bionic dist-upgrade

[Andres Rodriguez]

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

Thanks to the investigation from Steve, it seems that during the dist-
upgrade process ifupdown was removed due a transient conflict during the
devel cycle. This caused it to be removed. It being removed didn't
provide network. So this bug is basically a duplicate of #1756846.

17:21 < slangasek> roaksoax: according to your logs, during that upgrade the 
ifupdown package was removed (because of a transient conflict 
   during the devel cycle). you do not have the ifupdown 
package installed.
17:22 < slangasek> roaksoax: reinstalling ifupdown will fix this, and this is 
basically a duplicate of LP: #1756846


** This bug has been marked a duplicate of bug 1756846
   bridge-utils incompatible with ifupdown on bionic

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

Title:
  Network configuration doesn't survive reboots after bionic dist-
  upgrade

Status in cloud-init package in Ubuntu:
  Invalid
Status in ifupdown package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  Invalid

Bug description:
  I deployed Xenial in this machine with MAAS. After deployment i had
  re-configured interfaces manually (on /etc/network/interfaces), and
  removed /etc/network/interfaces.d. At some point, I upgraded the
  machine from Xenial to Bionic, and everything was working just fine
  with /e/n/i.

  About 2/3 weeks ago, I dist-upgraded bionic for the latest packages,
  and after reboot, networking didn't come up.


  To recover the machine, what i did is:

  1. From the console, brought up the interfaces manually (eno1)
  2. added an IP address manually (ip addr add)
  3. Configured netplan and applied the config: 

  network:
  version: 2
  renderer: networkd
  ethernets:
  eno1:
  dhcp4: no
  dhcp6: no
  addresses: [192.168.1.13/24]
  gateway4: 192.168.1.1
  nameservers:
  addresses: [8.8.8.8, 8.8.4.4]
  usb0:
  dhcp4: no
  bridges:
  br0:
  interfaces: [usb0]
  dhcp4: no
  addresses: [10.90.90.1/24]
  parameters:
  stp: false
  forward-delay: 0
  max-age: 0

  5. Interfaces dont get configured correctly:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  17: eno1:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
  link/ether ec:a8:6b:fd:ac:70 brd ff:ff:ff:ff:ff:ff
  inet 192.168.1.13/24 scope global eno1
     valid_lft forever preferred_lft forever
  inet6 fe80::eea8:6bff:fefd:ac70/64 scope link
     valid_lft forever preferred_lft forever
  19: usb0:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
  link/ether 00:0e:c6:88:b7:9f brd ff:ff:ff:ff:ff:ff
  inet6 fe80::20e:c6ff:fe88:b79f/64 scope link
     valid_lft forever preferred_lft forever
  22: wlp2s0:  mtu 1500 qdisc noop state DOWN group 
default qlen 1000
  link/ether c4:d9:87:5b:42:62 brd ff:ff:ff:ff:ff:ff

  6. on reboot, the machine goes back to have no networking again, at
  all.

  Note that I also have /e/n/i configured.

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

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

[Touch-packages] [Bug 1761294] Re: Network configuration doesn't survive reboots after bionic dist-upgrade

[Ryan Harper]

As per cloud-init networking disabled.  Please reopen task if you find
cloud-init is in the picture here.

** Changed in: cloud-init (Ubuntu)
   Status: New => Invalid

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

Title:
  Network configuration doesn't survive reboots after bionic dist-
  upgrade

Status in cloud-init package in Ubuntu:
  Invalid
Status in ifupdown package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  Invalid

Bug description:
  I deployed Xenial in this machine with MAAS. After deployment i had
  re-configured interfaces manually (on /etc/network/interfaces), and
  removed /etc/network/interfaces.d. At some point, I upgraded the
  machine from Xenial to Bionic, and everything was working just fine
  with /e/n/i.

  About 2/3 weeks ago, I dist-upgraded bionic for the latest packages,
  and after reboot, networking didn't come up.


  To recover the machine, what i did is:

  1. From the console, brought up the interfaces manually (eno1)
  2. added an IP address manually (ip addr add)
  3. Configured netplan and applied the config: 

  network:
  version: 2
  renderer: networkd
  ethernets:
  eno1:
  dhcp4: no
  dhcp6: no
  addresses: [192.168.1.13/24]
  gateway4: 192.168.1.1
  nameservers:
  addresses: [8.8.8.8, 8.8.4.4]
  usb0:
  dhcp4: no
  bridges:
  br0:
  interfaces: [usb0]
  dhcp4: no
  addresses: [10.90.90.1/24]
  parameters:
  stp: false
  forward-delay: 0
  max-age: 0

  5. Interfaces dont get configured correctly:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  17: eno1:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
  link/ether ec:a8:6b:fd:ac:70 brd ff:ff:ff:ff:ff:ff
  inet 192.168.1.13/24 scope global eno1
     valid_lft forever preferred_lft forever
  inet6 fe80::eea8:6bff:fefd:ac70/64 scope link
     valid_lft forever preferred_lft forever
  19: usb0:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
  link/ether 00:0e:c6:88:b7:9f brd ff:ff:ff:ff:ff:ff
  inet6 fe80::20e:c6ff:fe88:b79f/64 scope link
     valid_lft forever preferred_lft forever
  22: wlp2s0:  mtu 1500 qdisc noop state DOWN group 
default qlen 1000
  link/ether c4:d9:87:5b:42:62 brd ff:ff:ff:ff:ff:ff

  6. on reboot, the machine goes back to have no networking again, at
  all.

  Note that I also have /e/n/i configured.

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

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

[Touch-packages] [Bug 1761294] Re: Network configuration doesn't survive reboots after bionic dist-upgrade

[Steve Langasek]

Your config file is apparently named /etc/netplan/netplan.conf, which
does not match the required "*.yaml" pattern (which is documented in the
netplan(5) manpage and elsewhere).

** Changed in: netplan.io (Ubuntu)
   Status: New => Invalid

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

Title:
  Network configuration doesn't survive reboots after bionic dist-
  upgrade

Status in cloud-init package in Ubuntu:
  New
Status in ifupdown package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  Invalid

Bug description:
  I deployed Xenial in this machine with MAAS. After deployment i had
  re-configured interfaces manually (on /etc/network/interfaces), and
  removed /etc/network/interfaces.d. At some point, I upgraded the
  machine from Xenial to Bionic, and everything was working just fine
  with /e/n/i.

  About 2/3 weeks ago, I dist-upgraded bionic for the latest packages,
  and after reboot, networking didn't come up.


  To recover the machine, what i did is:

  1. From the console, brought up the interfaces manually (eno1)
  2. added an IP address manually (ip addr add)
  3. Configured netplan and applied the config: 

  network:
  version: 2
  renderer: networkd
  ethernets:
  eno1:
  dhcp4: no
  dhcp6: no
  addresses: [192.168.1.13/24]
  gateway4: 192.168.1.1
  nameservers:
  addresses: [8.8.8.8, 8.8.4.4]
  usb0:
  dhcp4: no
  bridges:
  br0:
  interfaces: [usb0]
  dhcp4: no
  addresses: [10.90.90.1/24]
  parameters:
  stp: false
  forward-delay: 0
  max-age: 0

  5. Interfaces dont get configured correctly:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  17: eno1:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
  link/ether ec:a8:6b:fd:ac:70 brd ff:ff:ff:ff:ff:ff
  inet 192.168.1.13/24 scope global eno1
     valid_lft forever preferred_lft forever
  inet6 fe80::eea8:6bff:fefd:ac70/64 scope link
     valid_lft forever preferred_lft forever
  19: usb0:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
  link/ether 00:0e:c6:88:b7:9f brd ff:ff:ff:ff:ff:ff
  inet6 fe80::20e:c6ff:fe88:b79f/64 scope link
     valid_lft forever preferred_lft forever
  22: wlp2s0:  mtu 1500 qdisc noop state DOWN group 
default qlen 1000
  link/ether c4:d9:87:5b:42:62 brd ff:ff:ff:ff:ff:ff

  6. on reboot, the machine goes back to have no networking again, at
  all.

  Note that I also have /e/n/i configured.

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

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

[Touch-packages] [Bug 1761294] Re: Network configuration doesn't survive reboots after bionic dist-upgrade

[Andres Rodriguez]

https://pastebin.ubuntu.com/p/YPRxSrjHZ9/

** Changed in: netplan.io (Ubuntu)
   Status: Incomplete => New

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

Title:
  Network configuration doesn't survive reboots after bionic dist-
  upgrade

Status in cloud-init package in Ubuntu:
  New
Status in ifupdown package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  Invalid

Bug description:
  I deployed Xenial in this machine with MAAS. After deployment i had
  re-configured interfaces manually (on /etc/network/interfaces), and
  removed /etc/network/interfaces.d. At some point, I upgraded the
  machine from Xenial to Bionic, and everything was working just fine
  with /e/n/i.

  About 2/3 weeks ago, I dist-upgraded bionic for the latest packages,
  and after reboot, networking didn't come up.


  To recover the machine, what i did is:

  1. From the console, brought up the interfaces manually (eno1)
  2. added an IP address manually (ip addr add)
  3. Configured netplan and applied the config: 

  network:
  version: 2
  renderer: networkd
  ethernets:
  eno1:
  dhcp4: no
  dhcp6: no
  addresses: [192.168.1.13/24]
  gateway4: 192.168.1.1
  nameservers:
  addresses: [8.8.8.8, 8.8.4.4]
  usb0:
  dhcp4: no
  bridges:
  br0:
  interfaces: [usb0]
  dhcp4: no
  addresses: [10.90.90.1/24]
  parameters:
  stp: false
  forward-delay: 0
  max-age: 0

  5. Interfaces dont get configured correctly:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  17: eno1:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
  link/ether ec:a8:6b:fd:ac:70 brd ff:ff:ff:ff:ff:ff
  inet 192.168.1.13/24 scope global eno1
     valid_lft forever preferred_lft forever
  inet6 fe80::eea8:6bff:fefd:ac70/64 scope link
     valid_lft forever preferred_lft forever
  19: usb0:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
  link/ether 00:0e:c6:88:b7:9f brd ff:ff:ff:ff:ff:ff
  inet6 fe80::20e:c6ff:fe88:b79f/64 scope link
     valid_lft forever preferred_lft forever
  22: wlp2s0:  mtu 1500 qdisc noop state DOWN group 
default qlen 1000
  link/ether c4:d9:87:5b:42:62 brd ff:ff:ff:ff:ff:ff

  6. on reboot, the machine goes back to have no networking again, at
  all.

  Note that I also have /e/n/i configured.

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

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

[Touch-packages] [Bug 1761294] Re: Network configuration doesn't survive reboots after bionic dist-upgrade

[Steve Langasek]

> 3. Configured netplan and applied the config:
> 5. Interfaces dont get configured correctly:

Not sure what happened to 4 ;)  But in any case, can you please confirm:
- what is the full set of config files under /etc/netplan after boot?
- what commands did you run to apply the config, and what was the output?
- what are the contents of eni (and /etc/network/interfaces.d) at this point?

** Changed in: netplan.io (Ubuntu)
   Status: New => Incomplete

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

Title:
  Network configuration doesn't survive reboots after bionic dist-
  upgrade

Status in cloud-init package in Ubuntu:
  New
Status in ifupdown package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  New

Bug description:
  I deployed Xenial in this machine with MAAS. After deployment i had
  re-configured interfaces manually (on /etc/network/interfaces), and
  removed /etc/network/interfaces.d. At some point, I upgraded the
  machine from Xenial to Bionic, and everything was working just fine
  with /e/n/i.

  About 2/3 weeks ago, I dist-upgraded bionic for the latest packages,
  and after reboot, networking didn't come up.


  To recover the machine, what i did is:

  1. From the console, brought up the interfaces manually (eno1)
  2. added an IP address manually (ip addr add)
  3. Configured netplan and applied the config: 

  network:
  version: 2
  renderer: networkd
  ethernets:
  eno1:
  dhcp4: no
  dhcp6: no
  addresses: [192.168.1.13/24]
  gateway4: 192.168.1.1
  nameservers:
  addresses: [8.8.8.8, 8.8.4.4]
  usb0:
  dhcp4: no
  bridges:
  br0:
  interfaces: [usb0]
  dhcp4: no
  addresses: [10.90.90.1/24]
  parameters:
  stp: false
  forward-delay: 0
  max-age: 0

  5. Interfaces dont get configured correctly:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  17: eno1:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
  link/ether ec:a8:6b:fd:ac:70 brd ff:ff:ff:ff:ff:ff
  inet 192.168.1.13/24 scope global eno1
     valid_lft forever preferred_lft forever
  inet6 fe80::eea8:6bff:fefd:ac70/64 scope link
     valid_lft forever preferred_lft forever
  19: usb0:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
  link/ether 00:0e:c6:88:b7:9f brd ff:ff:ff:ff:ff:ff
  inet6 fe80::20e:c6ff:fe88:b79f/64 scope link
     valid_lft forever preferred_lft forever
  22: wlp2s0:  mtu 1500 qdisc noop state DOWN group 
default qlen 1000
  link/ether c4:d9:87:5b:42:62 brd ff:ff:ff:ff:ff:ff

  6. on reboot, the machine goes back to have no networking again, at
  all.

  Note that I also have /e/n/i configured.

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

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

[Touch-packages] [Bug 1761080] Re: package linux-image-extra-4.13.0-38-generic 4.13.0-38.43 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

[Launchpad Bug Tracker]

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

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  package linux-image-extra-4.13.0-38-generic 4.13.0-38.43 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  This bug reproduced on startup of ubuntu.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-image-extra-4.13.0-38-generic 4.13.0-38.43
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1088 F pulseaudio
semir  1522 F pulseaudio
  Date: Wed Apr  4 09:06:10 2018
  Df:
   
  Dmesg:
   
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  InstallationDate: Installed on 2017-12-15 (109 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 80SM
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=UUID=45107a8c-91ea-4c75-86b6-10a3dc9617c3 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.13.0-38-generic 4.13.0-38.43 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN36WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 5A2
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN36WW:bd08/30/2016:svnLENOVO:pn80SM:pvrLenovoideapad310-15ISK:rvnLENOVO:rnToronto5A2:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad310-15ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80SM
  dmi.product.version: Lenovo ideapad 310-15ISK
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1761294] Re: Network configuration doesn't survive reboots

[Andres Rodriguez]

cloud-init-output.log after manually rebooting the machine.

** Changed in: cloud-init (Ubuntu)
   Status: Incomplete => New

** Attachment added: "cloud-init-output.log"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1761294/+attachment/5101804/+files/cloud-init-output.log

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

** Description changed:

  I deployed Xenial in this machine with MAAS. After deployment i had re-
  configured interfaces manually (on /etc/network/interfaces), and removed
  /etc/network/interfaces.d. At some point, I upgraded the machine from
  Xenial to Bionic, and everything was working just fine with /e/n/i.
  
  About 2/3 weeks ago, I dist-upgraded bionic for the latest packages, and
  after reboot, networking didn't come up.
  
+ 
  To recover the machine, what i did is:
  
- 1. From the console, bring up the interfaces.
- 2. Brought up eno1 manually & added an IP address manually (ip addr add)
- 3. Configured netplan interfaces
- 4. Run sudo netplan apply with the following config:
+ 1. From the console, brought up the interfaces manually (eno1)
+ 2. added an IP address manually (ip addr add)
+ 3. Configured netplan and applied the config: 
  
  network:
- version: 2
- renderer: networkd
- ethernets:
- eno1:
- dhcp4: no
- dhcp6: no
- addresses: [192.168.1.13/24]
- gateway4: 192.168.1.1
- nameservers:
- addresses: [8.8.8.8, 8.8.4.4]
- usb0:
- dhcp4: no
- bridges:
- br0:
- interfaces: [usb0]
- dhcp4: no
- addresses: [10.90.90.1/24]
- parameters:
- stp: false
- forward-delay: 0
- max-age: 0
+ version: 2
+ renderer: networkd
+ ethernets:
+ eno1:
+ dhcp4: no
+ dhcp6: no
+ addresses: [192.168.1.13/24]
+ gateway4: 192.168.1.1
+ nameservers:
+ addresses: [8.8.8.8, 8.8.4.4]
+ usb0:
+ dhcp4: no
+ bridges:
+ br0:
+ interfaces: [usb0]
+ dhcp4: no
+ addresses: [10.90.90.1/24]
+ parameters:
+ stp: false
+ forward-delay: 0
+ max-age: 0
  
  5. Interfaces dont get configured correctly:
  
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
- link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
- inet 127.0.0.1/8 scope host lo
-valid_lft forever preferred_lft forever
- inet6 ::1/128 scope host 
-valid_lft forever preferred_lft forever
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+    valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host
+    valid_lft forever preferred_lft forever
  17: eno1:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
- link/ether ec:a8:6b:fd:ac:70 brd ff:ff:ff:ff:ff:ff
- inet 192.168.1.13/24 scope global eno1
-valid_lft forever preferred_lft forever
- inet6 fe80::eea8:6bff:fefd:ac70/64 scope link 
-valid_lft forever preferred_lft forever
+ link/ether ec:a8:6b:fd:ac:70 brd ff:ff:ff:ff:ff:ff
+ inet 192.168.1.13/24 scope global eno1
+    valid_lft forever preferred_lft forever
+ inet6 fe80::eea8:6bff:fefd:ac70/64 scope link
+    valid_lft forever preferred_lft forever
  19: usb0:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
- link/ether 00:0e:c6:88:b7:9f brd ff:ff:ff:ff:ff:ff
- inet6 fe80::20e:c6ff:fe88:b79f/64 scope link 
-valid_lft forever preferred_lft forever
+ link/ether 00:0e:c6:88:b7:9f brd ff:ff:ff:ff:ff:ff
+ inet6 fe80::20e:c6ff:fe88:b79f/64 scope link
+    valid_lft forever preferred_lft forever
  22: wlp2s0:  mtu 1500 qdisc noop state DOWN group 
default qlen 1000
- link/ether c4:d9:87:5b:42:62 brd ff:ff:ff:ff:ff:ff
+ link/ether c4:d9:87:5b:42:62 brd ff:ff:ff:ff:ff:ff
  
  6. on reboot, the machine goes back to have no networking again, at all.
+ 
+ Note that I also have /e/n/i configured.

** Changed in: netplan.io (Ubuntu)
   Importance: Critical => Undecided

** Summary changed:

- Network configuration doesn't survive reboots
+ Network configuration doesn't survive reboots after bionic dist-upgrade

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

Title:
  Network configuration doesn't survive reboots after bionic dist-
  upgrade

Status in cloud-init package in Ubuntu:
  New
Status in ifupdown package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  New

Bug description:
  I deployed Xenial in 

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

[statis meles]

?

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

Title:
  package linux-image-extra-4.4.0-119-generic 4.4.0-119.143 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-119-generic 4.4.0-119.143
  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/controlC0:  pcl64c 2208 F pulseaudio
  Date: Wed Apr  4 20:45:41 2018
  DpkgHistoryLog:
   Start-Date: 2018-04-04  20:40:55
   Commandline: /usr/bin/unattended-upgrade
   Install: linux-image-4.4.0-119-generic:amd64 (4.4.0-119.143, automatic), 
linux-headers-4.4.0-119:amd64 (4.4.0-119.143, automatic), 
linux-image-extra-4.4.0-119-generic:amd64 (4.4.0-119.143, automatic), 
linux-headers-4.4.0-119-generic:amd64 (4.4.0-119.143, automatic)
   Upgrade: linux-headers-generic:amd64 (4.4.0.116.122, 4.4.0.119.125), 
linux-libc-dev:amd64 (4.4.0-116.140, 4.4.0-119.143), libvncclient1:amd64 
(0.9.10+dfsg-3ubuntu0.16.04.1, 0.9.10+dfsg-3ubuntu0.16.04.2), libraw15:amd64 
(0.17.1-1ubuntu0.1, 0.17.1-1ubuntu0.2), linux-image-generic:amd64 
(4.4.0.116.122, 4.4.0.119.125), python-crypto:amd64 (2.6.1-6ubuntu0.16.04.2, 
2.6.1-6ubuntu0.16.04.3), linux-generic:amd64 (4.4.0.116.122, 4.4.0.119.125)
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=d2092ccb-05a7-4ddb-8f09-91c6e1fbbf27
  InstallationDate: Installed on 2016-08-05 (606 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: MSI MS-7592
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=33bed9e0-545f-4c61-93d4-bd4efd8704f4 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.17
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-119-generic 4.4.0-119.143 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/09/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V26.7
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: G41M-P26 (MS-7592)
  dmi.board.vendor: MSI
  dmi.board.version: 5.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 5.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV26.7:bd08/09/2011:svnMSI:pnMS-7592:pvr5.0:rvnMSI:rnG41M-P26(MS-7592):rvr5.0:cvnMSI:ct3:cvr5.0:
  dmi.product.name: MS-7592
  dmi.product.version: 5.0
  dmi.sys.vendor: MSI

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

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

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

[statis meles]

Public bug reported:

?

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.4.0-119-generic 4.4.0-119.143
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/controlC0:  pcl64c 2208 F pulseaudio
Date: Wed Apr  4 20:45:41 2018
DpkgHistoryLog:
 Start-Date: 2018-04-04  20:40:55
 Commandline: /usr/bin/unattended-upgrade
 Install: linux-image-4.4.0-119-generic:amd64 (4.4.0-119.143, automatic), 
linux-headers-4.4.0-119:amd64 (4.4.0-119.143, automatic), 
linux-image-extra-4.4.0-119-generic:amd64 (4.4.0-119.143, automatic), 
linux-headers-4.4.0-119-generic:amd64 (4.4.0-119.143, automatic)
 Upgrade: linux-headers-generic:amd64 (4.4.0.116.122, 4.4.0.119.125), 
linux-libc-dev:amd64 (4.4.0-116.140, 4.4.0-119.143), libvncclient1:amd64 
(0.9.10+dfsg-3ubuntu0.16.04.1, 0.9.10+dfsg-3ubuntu0.16.04.2), libraw15:amd64 
(0.17.1-1ubuntu0.1, 0.17.1-1ubuntu0.2), linux-image-generic:amd64 
(4.4.0.116.122, 4.4.0.119.125), python-crypto:amd64 (2.6.1-6ubuntu0.16.04.2, 
2.6.1-6ubuntu0.16.04.3), linux-generic:amd64 (4.4.0.116.122, 4.4.0.119.125)
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=d2092ccb-05a7-4ddb-8f09-91c6e1fbbf27
InstallationDate: Installed on 2016-08-05 (606 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: MSI MS-7592
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=33bed9e0-545f-4c61-93d4-bd4efd8704f4 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.17
RfKill:
 0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
SourcePackage: initramfs-tools
Title: package linux-image-extra-4.4.0-119-generic 4.4.0-119.143 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/09/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V26.7
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: G41M-P26 (MS-7592)
dmi.board.vendor: MSI
dmi.board.version: 5.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 5.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV26.7:bd08/09/2011:svnMSI:pnMS-7592:pvr5.0:rvnMSI:rnG41M-P26(MS-7592):rvr5.0:cvnMSI:ct3:cvr5.0:
dmi.product.name: MS-7592
dmi.product.version: 5.0
dmi.sys.vendor: MSI

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


** Tags: amd64 apport-package xenial

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

Title:
  package linux-image-extra-4.4.0-119-generic 4.4.0-119.143 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-119-generic 4.4.0-119.143
  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/controlC0:  pcl64c 2208 F pulseaudio
  Date: Wed Apr  4 20:45:41 2018
  DpkgHistoryLog:
   Start-Date: 2018-04-04  20:40:55
   Commandline: /usr/bin/unattended-upgrade
   Install: linux-image-4.4.0-119-generic:amd64 (4.4.0-119.143, automatic), 
linux-headers-4.4.0-119:amd64 (4.4.0-119.143, automatic), 
linux-image-extra-4.4.0-119-generic:amd64 (4.4.0-119.143, automatic), 
linux-headers-4.4.0-119-generic:amd64 (4.4.0-119.143, automatic)
   Upgrade: linux-headers-generic:amd64 (4.4.0.116.122, 4.4.0.119.125), 
linux-libc-dev:amd64 (4.4.0-116.140, 4.4.0-119.143), libvncclient1:amd64 
(0.9.10+dfsg-3ubuntu0.16.04.1, 0.9.10+dfsg-3ubuntu0.16.04.2), libraw15:amd64 
(0.17.1-1ubuntu0.1, 0.17.1-1ubuntu0.2), linux-image-generic:amd64 
(4.4.0.116.122, 4.4.0.119.125), python-crypto:amd64 (2.6.1-6ubuntu0.16.04.2, 
2.6.1-6ubuntu0.16.04.3), linux-generic:amd64 (4.4.0.116.122, 4.4.0.119.125)
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=d2092ccb-05a7-4ddb-8f09-91c6e1fbbf27
  InstallationDate: Installed on 2016-08-05 (606 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: MSI MS-7592
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: 

[Touch-packages] [Bug 1751011] Re: bash crashes in qemu-user environments (bionic)

[Steve Langasek]

** Changed in: bash (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  bash crashes in qemu-user environments (bionic)

Status in bash package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  Confirmed
Status in bash package in Debian:
  Fix Released

Bug description:
  Attempts to launch bash in an arm64 qemu-user environment in bionic
  results in the following error message:

  bash: xmalloc: .././shell.c:1709: cannot allocate 10 bytes (0 bytes
  allocated)

  This causes any qemu/chroot based bootstrapping to fail as many
  packages invoke bash during postinst.

  Version: bash_4.4.18-1ubuntu1_arm64
  Release: 18.04 pre-release

  QEMU: 2.8.0

  This appears to have been reported and fixed in the corresponding
  Debian package (https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=889869)

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

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

[Touch-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable

[Takis Issaris]

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

I am not sure if this is a duplicate, as I'm only experiencing the bug
with Alt+left/right. I'm on 16.04.4 LTS and started experiencing this
very recently after an update and reboot probably. I think that I
noticed this in fact as of today. I am not sure, as initially I thought
I had accidentally pressed a wrong key combo, but after 10 times,
noticed that it was the key combo for going back in my browser which
triggered it.

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

Title:
  Alt+left/right arrows switch between tty consoles (Gnome Shell
  vanishes), cannot disable

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  I'm used to using alt+left/right arrow to navigate back and forward in
  web browsers and elsewhere (nautilus)...  But on this fresh install of
  Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty
  consoles (the ctrl+alt+f1 ones).  But it's not listed as one of the
  shortcuts in the "keyboard" menu, so I don't know how to disable it...

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

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

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

[Takis Issaris]

I'm experiencing the same thing on Ubuntu Xenial. I initially thought it
was only on using Alt+left/right, but did a Alt+F4 to close a window
just now, and the window did close but it switched to VT4 as well. I
think it started happening today on my system.

Linux 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux

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

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

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

Bug description:
  = Test Cases =

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

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

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

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

  = Original Description =

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

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

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

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

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

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

[Touch-packages] [Bug 1761003] Re: Bionic Beaver - not able to connect to WPA Enterprise EAP-TLS

[Kitsab]

Hello,

thank you fro taking care about this, I created a bug report at gnome
bugzilla as requested:

https://bugzilla.gnome.org/show_bug.cgi?id=794988

Additional Information:
Maybe the bug reporting tool reported a wrong package, eventually the 
wpa-supplicant package is causing this issue (not sure).
I've recognized the status info is possibly wrong:UpgradeStatus: No upgrade log 
present (probably fresh install)
I performed an upgrade from 16.04, and 16.04. was upgraded from 14.04, (and I 
think 14.04 from 12.04 - not sure)

Best regards

Kitsab

** Bug watch added: GNOME Bug Tracker #794988
   https://bugzilla.gnome.org/show_bug.cgi?id=794988

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

Title:
  Bionic Beaver - not able to connect to WPA Enterprise EAP-TLS

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hello,

  since update to Bionic Beaver I can't connect to my WPA2-Entertrise EAP TLS 
network. Running Freeradius 2.29 on a DDWRT router. In 16.04 it worked, in the 
dual boot Windows 10 environment it is still working with the same certificates.
  It is a hidden network, adding it by "connect to a hidden network" entering 
SSID, UserID, ca.pem as CA cert, user cert xxx.p12 file and user certificate 
password.
  Tried a lot not getting it working. The password entry dialog for the network 
is always popping up upon connection trials. The password is for sure the 
correct one, checked it very often.
  If I'm able to I'll attach a syslog and kern.log of error occurense.

  Thanks for investigation and inputs.

  Best regards

  Kitsab

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Apr  3 23:52:23 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2015-02-14 (1144 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1622499] Re: [master] package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which

[Hans Joachim Desserud]

** Tags removed: yakkety
** Tags added: bionic xenial2bionic

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

Title:
  [master] package kaccounts-providers (not installed) failed to
  install/upgrade: trying to overwrite '/etc/signon-ui/webkit-
  options.d/accounts.google.com.conf', which is also in package account-
  plugin-google 0.13+16.04.20160719-0ubuntu1

Status in One Hundred Papercuts:
  Confirmed
Status in account-plugins package in Ubuntu:
  Confirmed
Status in kaccounts-providers package in Ubuntu:
  Confirmed

Bug description:
  
  kaccounts-providers packagepackage kaccounts-providers (not installed) failed 
to install/upgrade: trying to overwrite 
'/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in 
package account-plugin-google 0.13+16.04.20160719-0ubuntu1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: kaccounts-providers (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Sep 12 08:14:14 2016
  DuplicateSignature:
   package:kaccounts-providers:(not installed)
   Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb
 (--unpack):
trying to overwrite '/usr/share/accounts/services/google-im.service', which 
is also in package account-plugin-google 0.13+16.04.20160719-0ubuntu1
  ErrorMessage: trying to overwrite 
'/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in 
package account-plugin-google 0.13+16.04.20160719-0ubuntu1
  InstallationDate: Installed on 2016-09-08 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.14
  SourcePackage: kaccounts-providers
  Title: package kaccounts-providers (not installed) failed to install/upgrade: 
trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', 
which is also in package account-plugin-google 0.13+16.04.20160719-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1760335] Re: cannot add account to ubuntu live update

[Sebastien Bacher]

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

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

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

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Low

** Changed in: software-properties (Ubuntu)
   Status: New => Incomplete

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

Title:
  cannot add account to ubuntu live update

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.24
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  1 01:22:05 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2017-03-04 (392 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1761267] Re: issue is regarding boot hanging between work

[Leonidas S. Barbosa]

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

Title:
  issue is regarding boot hanging between work

Status in xorg package in Ubuntu:
  New

Bug description:
  while getting started it is hanged and sometime it doesnot open the
  required folder any software downloaded from internet is not installed
  in "exe." file especially sometime keyboard stops working

  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
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  BootLog:
   Scanning for Btrfs filesystems
   UBUNTU: clean, 272012/29777920 files, 3537812/119111424 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Apr  4 23:11:32 2018
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0767]
  InstallationDate: Installed on 2018-02-22 (41 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=a581e6e4-3ec8-44a1-96df-744ef70e8b7e ro acpi_rev_override locale=en_US
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 0C6XG5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd01/12/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn0C6XG5:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Inspiron 5567
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 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 Apr  4 20:29:12 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1317 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Touch-packages] [Bug 1761275] Re: Typo when running command for uninstalled applications

[Hans Joachim Desserud]

Thanks for taking your time to report this issue and help making Ubuntu
better.

The package suggestions for not installed packages is handled by
command-not-found, so I've taken the liberty of reassigning this bug
report. This sounds a bit like bug 1753102 which was fixed a while back,
and the suggestion text has also been reworked since then. Could you
please check which version of command-not-found you have installed (for
instance with `apt policy command-not-found`)? This could be
regression, but I wasn't able to reproduce it on my bionic system...

** Package changed: apt (Ubuntu) => command-not-found (Ubuntu)

** Changed in: command-not-found (Ubuntu)
   Status: New => Incomplete

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

Title:
  Typo when running command for uninstalled applications

Status in command-not-found package in Ubuntu:
  Incomplete

Bug description:
  I tried running nodejs on Ubuntu Mate 18.04. When I ran it, it asked
  me to install it, I didn't know where to report this or where it was
  referring so I guessed it was apt.

  The command 'nodejs' can be ""intsalled"" by typing: 
  sudo apt install nodejs

  The typo is in double quotation marks. It says intsalled instead of
  installed. It should be corrected. Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6~beta1
  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
  CurrentDesktop: MATE
  Date: Wed Apr  4 14:50:48 2018
  InstallationDate: Installed on 2018-04-03 (1 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180307.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1761275/+subscriptions

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

[Touch-packages] [Bug 1757951] Re: FFE: wayland 1.15, move libwayland-egl to src:wayland

[Timo Aaltonen]

I have the packages in ppa:canonical-x/x-staging, but wayland should
bump it's breaks/replaces against the mesa packages to fix file
conflicts (because we didn't pull in this change yet). libwayland-dev
might also need to be split to have egl frontend/backend headers in
separate packages, I'll look into that first and push it to Debian, then
sync to ppa again.

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

Title:
  FFE: wayland 1.15, move libwayland-egl to src:wayland

Status in wayland package in Ubuntu:
  New

Bug description:
  libwayland-egl was moved from mesa to wayland in 1.15rc and will be
  dropped from Mesa after 18.0.0. So in order to avoid doing this as an
  SRU later when backporting newer mesa to 18.04 we should do the
  transition in bionic before release. Debian has done this now in
  experimental.

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

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

[Touch-packages] [Bug 1761275] [NEW] Typo when running command for uninstalled applications

[hyland b]

Public bug reported:

I tried running nodejs on Ubuntu Mate 18.04. When I ran it, it asked me
to install it, I didn't know where to report this or where it was
referring so I guessed it was apt.

The command 'nodejs' can be ""intsalled"" by typing: 
sudo apt install nodejs

The typo is in double quotation marks. It says intsalled instead of
installed. It should be corrected. Thanks!

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apt 1.6~beta1
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
CurrentDesktop: MATE
Date: Wed Apr  4 14:50:48 2018
InstallationDate: Installed on 2018-04-03 (1 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180307.1)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Typo when running command for uninstalled applications

Status in apt package in Ubuntu:
  New

Bug description:
  I tried running nodejs on Ubuntu Mate 18.04. When I ran it, it asked
  me to install it, I didn't know where to report this or where it was
  referring so I guessed it was apt.

  The command 'nodejs' can be ""intsalled"" by typing: 
  sudo apt install nodejs

  The typo is in double quotation marks. It says intsalled instead of
  installed. It should be corrected. Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6~beta1
  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
  CurrentDesktop: MATE
  Date: Wed Apr  4 14:50:48 2018
  InstallationDate: Installed on 2018-04-03 (1 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180307.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 520546] Re: Alt-f2 switches to virtual terminal 2

[Anders Kaseorg]

Just because DISPLAY isn’t set for the current process doesn’t mean X or
Wayland aren’t running.  For example:

pkexec env DEBIAN_FRONTEND=noninteractive dpkg-reconfigure keyboard-
configuration

still triggers this bug (because pkexec does not propagate environment
variables), and you can imagine any number of other ways this might
happen, like packagekit or unattended-upgrades.

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

Title:
  Alt-f2 switches to virtual terminal 2

Status in console-cyrillic package in Ubuntu:
  Invalid
Status in console-setup package in Ubuntu:
  Invalid

Bug description:
  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

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

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

[Touch-packages] [Bug 1760598] Re: I/O Error after clicking "reboot now" - Ubuntu font missing from casper shutdown

[Launchpad Bug Tracker]

This bug was fixed in the package casper - 1.393

---
casper (1.393) bionic; urgency=medium

  * Cache Ubuntu fonts for plymouth on shutdown. LP: #1760598

 -- Dimitri John Ledkov   Wed, 04 Apr 2018 11:55:32
+0100

** Changed in: casper (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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1760598

Title:
  I/O Error after clicking "reboot now" - Ubuntu font missing from
  casper shutdown

Status in ubuntu-mate:
  New
Status in casper package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Confirmed
Status in ubuntu-mate-welcome package in Ubuntu:
  Invalid

Bug description:
  ubuntu Plymouth theme now correctly uses Ubuntu font, meaning it needs
  to be cached for display of the shutdown message.

  We really should be using shutdown initramfs on the livecd

  --

  Tested in Virtualbox VM.
  Ubuntu MATE works after force-reboot, but after I click on "restart now" 
after completing the installation, the screen shows me this:

  req_error: I/O error, dev sr0, sector 1488792

  And the above message loops a couple times, and wont turn off the
  computer to restart.

  No error happens after force reboot, and the OS boots properly, but
  I'm curious as to what's causing this.

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

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

[Touch-packages] [Bug 1761121] Re: Latest intel ucode update halts my system during boot to graphic session

[Launchpad Bug Tracker]

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

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

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

Title:
  Latest intel ucode update halts my system during boot to graphic
  session

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  It seems that this 
  iucode_tool -lS /lib/firmware/intel-ucode/
  iucode_tool: system has processor(s) with signature 0x000306a9
  selected microcodes:
  001: sig 0x000306a9, pf mask 0x12, 2018-02-07, rev 0x001f, size 13312
  microcode update prevents me to boot to graphic session on any(4.13.0.38[37]) 
kernel.
  I can successfully boot to the recovery console.
  In some of failed attempts i got "NMI deadlock detected on CPU0,1,3 in mkswap"
  I guess nvidia-384 has some issues and conflicts with updated microcode.
  I have to disable microcode update with 
IUCODE_TOOL_EXTRA_OPTIONS="--date-after=2018-02-07" to get my unity session 
back.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Это каталог: 
'/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.9)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  BootLog:
   lvmetad is not active yet, using direct activation during sysinit
   /dev/mapper/lmvg-ubunturoot: clean, 421309/1310720 files, 3715643/5242880 
blocks
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Apr  4 12:39:37 2018
  DistUpgraded: 2016-04-19 13:48:02,030 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Не удалось выполнить 
процесс-потомок «./xorg_fix_proprietary.py» (No such file or directory) (8))
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK107 [GeForce GT 640] [10de:0fc1] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GK107 [GeForce GT 640] [1458:353e]
  InstallationDate: Installed on 2012-09-26 (2015 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=/dev/mapper/lmvg-ubunturoot ro nouveau.modeset=0 
rd.driver.blacklist=nouveau video=vesa:off nvidia_drm.modeset=1 zswap.enabled=0 
quiet
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-19 (714 days ago)
  dmi.bios.date: 10/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-DS2 DVI
  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.:bvrF1:bd10/12/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-DS2DVI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.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 Apr  4 11:56:19 2018
  xserver.configfile: default
  

Re: [Touch-packages] [Bug 520546] Re: Alt-f2 switches to virtual terminal 2

[Iain Lane]

On Wed, Apr 04, 2018 at 04:25:17PM -, Juha Sahakangas wrote:
> This bug is still happening and it absolutely certainly does not have
> anything to do with mechanical issues.
> 
> Andersk already identified the exact cause in comment #31 also - and
> it's absolutely trivial to verify that the offending "setupcon --force
> --save" command is still in the "keyboard-configuration.postinst" of the
> latest 1.178ubuntu1 version of console-setup package.

That line isn't executed in the normal case. There's some weird
formatting going on, but:

if [ "$DISPLAY" ] && which setxkbmap >/dev/null; then
setxkbmap -option '' -model "$model" "$layout" "$variant" "$options" || 
true
# setting the font corrupts X
# setting up the keyboard breaks wayland
if type setupcon >/dev/null 2>&1; then
setupcon --save-only
cat >&2 &1; then
setupcon --force --save
fi
;;
esac
fi

see the "fielse" - the first branch is taken if $DISPLAY is set and
sexkbmap and setupcon exists.

Is $DISPLAY not set for you when this runs?

You can add `set -x' to the top of
/var/lib/dpkg/info/keyboard-configuration.postinst and run something
like `sudo DEBIAN_FRONTEND=noninteractive dpkg-reconfigure
keyboard-configuration' to verify what happens when
keyboard-configuration is configured by dpkg.

I think we should consider maybe removing that case too, but I'd like to
know if that is the actual cause of your problem please.

 subscribe laney

Cheers,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  Alt-f2 switches to virtual terminal 2

Status in console-cyrillic package in Ubuntu:
  Invalid
Status in console-setup package in Ubuntu:
  Invalid

Bug description:
  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

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

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

[Touch-packages] [Bug 1761121] Re: Latest intel ucode update halts my system during boot to graphic session

[ts]

I have a very similar situation on Ubuntu mate 17.10, I suddenly can
boot 4.13.0-36 only..

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

Title:
  Latest intel ucode update halts my system during boot to graphic
  session

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  It seems that this 
  iucode_tool -lS /lib/firmware/intel-ucode/
  iucode_tool: system has processor(s) with signature 0x000306a9
  selected microcodes:
  001: sig 0x000306a9, pf mask 0x12, 2018-02-07, rev 0x001f, size 13312
  microcode update prevents me to boot to graphic session on any(4.13.0.38[37]) 
kernel.
  I can successfully boot to the recovery console.
  In some of failed attempts i got "NMI deadlock detected on CPU0,1,3 in mkswap"
  I guess nvidia-384 has some issues and conflicts with updated microcode.
  I have to disable microcode update with 
IUCODE_TOOL_EXTRA_OPTIONS="--date-after=2018-02-07" to get my unity session 
back.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Это каталог: 
'/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.9)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  BootLog:
   lvmetad is not active yet, using direct activation during sysinit
   /dev/mapper/lmvg-ubunturoot: clean, 421309/1310720 files, 3715643/5242880 
blocks
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Apr  4 12:39:37 2018
  DistUpgraded: 2016-04-19 13:48:02,030 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Не удалось выполнить 
процесс-потомок «./xorg_fix_proprietary.py» (No such file or directory) (8))
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK107 [GeForce GT 640] [10de:0fc1] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GK107 [GeForce GT 640] [1458:353e]
  InstallationDate: Installed on 2012-09-26 (2015 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=/dev/mapper/lmvg-ubunturoot ro nouveau.modeset=0 
rd.driver.blacklist=nouveau video=vesa:off nvidia_drm.modeset=1 zswap.enabled=0 
quiet
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-19 (714 days ago)
  dmi.bios.date: 10/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-DS2 DVI
  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.:bvrF1:bd10/12/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-DS2DVI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.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 Apr  4 11:56:19 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: 

[Touch-packages] [Bug 1724152] Re: ISST-LTE: pVM: aureport couldn't get the right auid from the audit log on ubuntu16.04

[Manoj Iyer]

** Changed in: audit (Ubuntu Zesty)
   Status: Fix Committed => Won't Fix

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

Title:
  ISST-LTE: pVM: aureport couldn't get the right auid from the audit log
  on ubuntu16.04

Status in The Ubuntu-power-systems project:
  Fix Released
Status in audit package in Ubuntu:
  Invalid
Status in audit source package in Xenial:
  Fix Released
Status in audit source package in Zesty:
  Won't Fix

Bug description:
  [Impact]

  The aureport command, part of the audit userspace utilities,
  incorrectly reports the user id of successful logins. "-1" is printed
  instead of the expected user id.

  [Test Case]

  As root, run `login`. Proceed as follows:

  1. Login with a blank username and any password
  2. Login with an invalid username and any password
  3. Login with a valid username and an invalid password
  4. Login with a valid username and a valid password
  5. Exit from the login shell
  6. Run `aureport -l` and examine the last for login records

  An unpatched aureport will print the following:

  
  # date time auid host term exe success event
  
  ...
  2. 10/17/2017 23:45:32 UNKNOWN ? /dev/pts/8 /bin/login no 97
  3. 10/17/2017 23:45:39 UNKNOWN ? /dev/pts/8 /bin/login no 99
  4. 10/17/2017 23:45:45 tyhicks ? /dev/pts/8 /bin/login no 101
  5. 10/17/2017 23:45:49 -1 ? /dev/pts/8 /bin/login yes 107

  A patch aureport will print the correct output:

  Login Report
  
  # date time auid host term exe success event
  
  ...
  2. 10/17/2017 23:52:44 UNKNOWN ? /dev/pts/8 /bin/login no 165
  3. 10/17/2017 23:52:52 UNKNOWN ? /dev/pts/8 /bin/login no 167
  4. 10/17/2017 23:52:58 tyhicks ? /dev/pts/8 /bin/login no 169
  5. 10/17/2017 23:53:02 1000 ? /dev/pts/8 /bin/login yes 175

  Note the "1000" in the auid column on the #5 row. It should *not* be
  "-1".

  [Regression Potential]

  The regression potential is limited due to the change only affecting a
  single line of code, the fix comes from upstream, and that the
  aureport utility is not critical.

  [Original Report]

  == Comment: #0 - Miao Tao Feng  - 2016-11-23 02:46:25 ==
  When we develop new testcase for audit, we found that command "aureport -l" 
print out wrong auid "-1"  on ubuntu16.04  and it should be 1000 according to 
the audit.log.

  The following are details:

  root@roselp2:~# aureport -l

  Login Report
  
  # date time auid host term exe success event
  
  1. 11/23/2016 02:20:12 -1 10.33.24.118 /dev/pts/0 /usr/sbin/sshd yes 18

  The auid "-1" on the above line should be "1000? according to the
  audit.log.

  root@roselp2:~# grep ":18" /var/log/audit/audit.log
  type=USER_LOGIN msg=audit(1479889212.292:18): pid=4177 uid=0 auid=1000 ses=4 
msg='op=login id=1000 exe="/usr/sbin/sshd" hostname=10.33.24.118 
addr=10.33.24.118 terminal=/dev/pts/0 res=success'

  root@roselp2:~# dpkg -s auditd
  Package: auditd
  Status: install ok installed
  Priority: extra
  Section: admin
  Installed-Size: 1051
  Maintainer: Ubuntu Developers 
  Architecture: ppc64el
  Source: audit
  Version: 1:2.4.5-1ubuntu2
  Depends: lsb-base (>= 3.0-6), mawk | gawk, init-system-helpers (>= 1.18~), 
libaudit1 (>= 1:2.4.2), libauparse0 (>= 1:2.3.1), libc6 (>= 2.17)
  Suggests: audispd-plugins

  root@roselp2:~# uname -a
  Linux roselp2 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:38:24 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  root@roselp2:~# service auditd status
  ? auditd.service - Security Auditing Service
     Loaded: loaded (/lib/systemd/system/auditd.service; enabled; vendor 
preset: e
     Active: active (running) since Wed 2016-11-23 02:19:21 CST; 19s ago
   Main PID: 4085 (auditd)
     CGroup: /system.slice/auditd.service
     ??4085 /sbin/auditd -n

  Nov 23 02:19:21 roselp2 auditctl[4086]: enabled 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: failure 1
  Nov 23 02:19:21 roselp2 auditctl[4086]: pid 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: rate_limit 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: backlog_limit 320
  Nov 23 02:19:21 roselp2 auditctl[4086]: lost 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: backlog 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: backlog_wait_time 15000
  Nov 23 02:19:21 roselp2 systemd[1]: Started Security Auditing Service.
  Nov 23 02:19:21 roselp2 auditd[4085]: Init complete, auditd 2.4.5 listening 
for

  Please cherry pick https://github.com/linux-audit/audit-
  userspace/commit/25097d64344828a80acf681da5c1dacc4ea3c069

To manage notifications about this bug go to:

[Touch-packages] [Bug 1724152] Re: ISST-LTE: pVM: aureport couldn't get the right auid from the audit log on ubuntu16.04

[Frank Heimes]

** Changed in: ubuntu-power-systems
   Status: Fix Committed => Fix Released

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

Title:
  ISST-LTE: pVM: aureport couldn't get the right auid from the audit log
  on ubuntu16.04

Status in The Ubuntu-power-systems project:
  Fix Released
Status in audit package in Ubuntu:
  Invalid
Status in audit source package in Xenial:
  Fix Released
Status in audit source package in Zesty:
  Won't Fix

Bug description:
  [Impact]

  The aureport command, part of the audit userspace utilities,
  incorrectly reports the user id of successful logins. "-1" is printed
  instead of the expected user id.

  [Test Case]

  As root, run `login`. Proceed as follows:

  1. Login with a blank username and any password
  2. Login with an invalid username and any password
  3. Login with a valid username and an invalid password
  4. Login with a valid username and a valid password
  5. Exit from the login shell
  6. Run `aureport -l` and examine the last for login records

  An unpatched aureport will print the following:

  
  # date time auid host term exe success event
  
  ...
  2. 10/17/2017 23:45:32 UNKNOWN ? /dev/pts/8 /bin/login no 97
  3. 10/17/2017 23:45:39 UNKNOWN ? /dev/pts/8 /bin/login no 99
  4. 10/17/2017 23:45:45 tyhicks ? /dev/pts/8 /bin/login no 101
  5. 10/17/2017 23:45:49 -1 ? /dev/pts/8 /bin/login yes 107

  A patch aureport will print the correct output:

  Login Report
  
  # date time auid host term exe success event
  
  ...
  2. 10/17/2017 23:52:44 UNKNOWN ? /dev/pts/8 /bin/login no 165
  3. 10/17/2017 23:52:52 UNKNOWN ? /dev/pts/8 /bin/login no 167
  4. 10/17/2017 23:52:58 tyhicks ? /dev/pts/8 /bin/login no 169
  5. 10/17/2017 23:53:02 1000 ? /dev/pts/8 /bin/login yes 175

  Note the "1000" in the auid column on the #5 row. It should *not* be
  "-1".

  [Regression Potential]

  The regression potential is limited due to the change only affecting a
  single line of code, the fix comes from upstream, and that the
  aureport utility is not critical.

  [Original Report]

  == Comment: #0 - Miao Tao Feng  - 2016-11-23 02:46:25 ==
  When we develop new testcase for audit, we found that command "aureport -l" 
print out wrong auid "-1"  on ubuntu16.04  and it should be 1000 according to 
the audit.log.

  The following are details:

  root@roselp2:~# aureport -l

  Login Report
  
  # date time auid host term exe success event
  
  1. 11/23/2016 02:20:12 -1 10.33.24.118 /dev/pts/0 /usr/sbin/sshd yes 18

  The auid "-1" on the above line should be "1000? according to the
  audit.log.

  root@roselp2:~# grep ":18" /var/log/audit/audit.log
  type=USER_LOGIN msg=audit(1479889212.292:18): pid=4177 uid=0 auid=1000 ses=4 
msg='op=login id=1000 exe="/usr/sbin/sshd" hostname=10.33.24.118 
addr=10.33.24.118 terminal=/dev/pts/0 res=success'

  root@roselp2:~# dpkg -s auditd
  Package: auditd
  Status: install ok installed
  Priority: extra
  Section: admin
  Installed-Size: 1051
  Maintainer: Ubuntu Developers 
  Architecture: ppc64el
  Source: audit
  Version: 1:2.4.5-1ubuntu2
  Depends: lsb-base (>= 3.0-6), mawk | gawk, init-system-helpers (>= 1.18~), 
libaudit1 (>= 1:2.4.2), libauparse0 (>= 1:2.3.1), libc6 (>= 2.17)
  Suggests: audispd-plugins

  root@roselp2:~# uname -a
  Linux roselp2 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:38:24 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  root@roselp2:~# service auditd status
  ? auditd.service - Security Auditing Service
     Loaded: loaded (/lib/systemd/system/auditd.service; enabled; vendor 
preset: e
     Active: active (running) since Wed 2016-11-23 02:19:21 CST; 19s ago
   Main PID: 4085 (auditd)
     CGroup: /system.slice/auditd.service
     ??4085 /sbin/auditd -n

  Nov 23 02:19:21 roselp2 auditctl[4086]: enabled 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: failure 1
  Nov 23 02:19:21 roselp2 auditctl[4086]: pid 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: rate_limit 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: backlog_limit 320
  Nov 23 02:19:21 roselp2 auditctl[4086]: lost 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: backlog 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: backlog_wait_time 15000
  Nov 23 02:19:21 roselp2 systemd[1]: Started Security Auditing Service.
  Nov 23 02:19:21 roselp2 auditd[4085]: Init complete, auditd 2.4.5 listening 
for

  Please cherry pick https://github.com/linux-audit/audit-
  userspace/commit/25097d64344828a80acf681da5c1dacc4ea3c069

To manage notifications about this bug go to:

[Touch-packages] [Bug 520546] Re: Alt-f2 switches to virtual terminal 2

[Juha Sahakangas]

This bug is still happening and it absolutely certainly does not have
anything to do with mechanical issues.

Andersk already identified the exact cause in comment #31 also - and
it's absolutely trivial to verify that the offending "setupcon --force
--save" command is still in the "keyboard-configuration.postinst" of the
latest 1.178ubuntu1 version of console-setup package.

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

Title:
  Alt-f2 switches to virtual terminal 2

Status in console-cyrillic package in Ubuntu:
  Invalid
Status in console-setup package in Ubuntu:
  Invalid

Bug description:
  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

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

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

[Touch-packages] [Bug 1729491] Re: [UIFe] ubuntu-bug says that snap packages are not installed

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-core-dev/ubuntu/bionic/apport/ubuntu

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

Title:
  [UIFe] ubuntu-bug says that snap packages are not installed

Status in apport package in Ubuntu:
  Triaged
Status in ubuntu-docs package in Ubuntu:
  New
Status in apport source package in Bionic:
  Triaged

Bug description:
  User Interface Freeze Exception Justification
  =
  The interface for ubuntu-bug/apport-bug  is super confusing if  
was installed as a snap.

  List Notifications
  ==
  https://lists.ubuntu.com/archives/ubuntu-translators/2018-April/007471.html
  

  Original Bug Description
  
  1.
  I installed the package gnome-recipes, tried to send an error report program 
in response to the received message:you cannot report a problem:
  The report belongs to a package that was not installed.

  2.
  Expected that the program will be identified as installed.

  3.
  sudo apt -f install
  [sudo] password for Alexander:
  Reading package lists... Done
  Building dependency tree
  Reading state information... Ready
  0 upgraded, 0 newly installed, for removal 0 packets are marked, and 0 
packages are not updated.
  sudo gnome-sudo recipes: gnome-recipes: command not found
  sudo apt install gnome-recipes Reading package lists... Done
  Building dependency tree
  Reading state information... Ready
  E: unable to locate package gnome-recipes

  I installed via software-center

  gnome-recipes
  snap-confine has elevated permissions and is not confined but should be. 
Refusing to continue to avoid permission escalation attacks
  ubuntu-bug gnome-recipes
  dpkg-query: template gnome-recipes no corresponding package
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  ^C^Z
  [1]+ Stopped ubuntu-bug gnome-recipes

  https://youtu.be/AXtR5m2uqUg
  ---

  1.
  произвёл установку пакета gnome-recipes, попытался отправить отчёт об ошибке 
программы, в ответ получил сообщение:Не удаётся сообщить о неполадке:
  Отчёт относится к пакету , который не был установлен.

  2.
  Ожидал что программа будет идентифицироваться как установленная.

  3.
  sudo apt -f install
  [sudo] пароль для alexandr:
  Чтение списков пакетов… Готово
  Построение дерева зависимостей
  Чтение информации о состоянии… Готово
  обновлено 0, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 
0 пакетов не обновлено.
  sudo gnome-recipes sudo: gnome-recipes: команда не найдена
  sudo apt install gnome-recipes Чтение списков пакетов… Готово
  Построение дерева зависимостей
  Чтение информации о состоянии… Готово
  E: Не удалось найти пакет gnome-recipes

  произвёл установку через software-center

  gnome-recipes
  snap-confine has elevated permissions and is not confined but should be. 
Refusing to continue to avoid permission escalation attacks
  ubuntu-bug gnome-recipes
  dpkg-query: шаблону gnome-recipes не соответствует ни один пакет
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  ^C^Z
  [1]+  Остановлено  ubuntu-bug gnome-recipes

  https://youtu.be/AXtR5m2uqUg

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: software-center (not installed)
  Uname: Linux 4.14.0-041400rc7-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov  2 08:06:48 2017
  InstallationDate: Installed on 2017-10-29 (3 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: software-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1751011] Re: bash crashes in qemu-user environments (bionic)

[Matthias Klose]

qemu patch proposed at http://lists.nongnu.org/archive/html/qemu-
devel/2018-03/msg04700.html

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

Title:
  bash crashes in qemu-user environments (bionic)

Status in bash package in Ubuntu:
  Triaged
Status in qemu package in Ubuntu:
  Confirmed
Status in bash package in Debian:
  Fix Released

Bug description:
  Attempts to launch bash in an arm64 qemu-user environment in bionic
  results in the following error message:

  bash: xmalloc: .././shell.c:1709: cannot allocate 10 bytes (0 bytes
  allocated)

  This causes any qemu/chroot based bootstrapping to fail as many
  packages invoke bash during postinst.

  Version: bash_4.4.18-1ubuntu1_arm64
  Release: 18.04 pre-release

  QEMU: 2.8.0

  This appears to have been reported and fixed in the corresponding
  Debian package (https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=889869)

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

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

[Touch-packages] [Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system

[Dimitri John Ledkov]

@rrs
> BTW, does Ubuntu have the systemd/udevd mount propagation fix included ?

yes no maybe =

Added in debian at ed16ca8690eb69c248a0a741def5324eedc9149d
Removed from debian at d529d047752d8492d43e42e8b4223d6d37fa3dd3
Meaning it was for a while, if you mean the Debian bug linked to this bug 
report.
But not since laptop-mode-tools 1.68 was fixed.

I believe the debian bug attached to this bug report is a red herring.

https://git.launchpad.net/~ubuntu-core-dev/+git/systemd/commit/?h
=ubuntu-bionic=ed16ca8690eb69c248a0a741def5324eedc9149d

https://git.launchpad.net/~ubuntu-core-
dev/+git/systemd/commit/?h=d529d047752d8492d43e42e8b4223d6d37fa3dd3

** No longer affects: systemd (Debian)

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

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

Title:
  System fails to start (boot) on battery due to read-only root file-
  system

Status in laptop-mode-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Incomplete
Status in laptop-mode-tools source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Incomplete

Bug description:
  This report is to capture the extended diagnostic efforts done on IRC
  #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was
  upgraded from 17.04 to 17.10 and since fails to complete start-up of
  services when powered on battery.

  We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'"
  workaround in case this was an ACPI DSDT issue.

  This appears to be due to a read-only root file-system. What is not
  clear is how the rootfs goes read-only.

  The file-system (sda6, ext4) is fsck-ed successfully in the initrd
  according to the /run/initramfs/fsck.log.

  From the start-up logs (with "systemd.log_level=debug") we see the
  ext4 driver report a remount operation not once but five times.

  $ grep 'EXT4-fs.*sda6' systemd-debug.log
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered 
data mode. Opts: (null)
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro
  Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600

  Those last five appear to be carrying options generated by laptop-
  mode-tools.

  User has disabled laptop-mode.service and laptop-mode.timer, and lmt-
  poll.service, but the issue remains.

  We see several reports of "read-only file-system":

  $ grep 'Read-only' systemd-debug.log
  Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open 
`/boot/grub/grubenv': Read-only file system.
  Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: 
Read-only file system
  Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to 
/var/log/gpu-manager.log failed (Read-only file system)
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: 
Read-only file system
  ...
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of 
"/var/log/cups" - Read-only file system
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file 
"/var/log/cups/access_log" - Read-only file system
  Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open 
/var/log/lastlog: Read-only file system

  We also see several problems with systemd's connection to Dbus:

  $ grep 'Transport endpoint' systemd-debug.log
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit 
change signal for systemd-logind.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit 
change signal for lmt-poll.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: 
Transport endpoint is not connected
  Oct 23 

[Touch-packages] [Bug 1757951] Re: FFE: wayland 1.15, move libwayland-egl to src:wayland

[Łukasz Zemczak]

Ok, this is a big change but I'd also prefer this happening before the
release instead of afterwards. Please perform some upgrade-testing on
the packages built in a PPA and if things look good, we can approve this
FFe.

Thanks!

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

Title:
  FFE: wayland 1.15, move libwayland-egl to src:wayland

Status in wayland package in Ubuntu:
  New

Bug description:
  libwayland-egl was moved from mesa to wayland in 1.15rc and will be
  dropped from Mesa after 18.0.0. So in order to avoid doing this as an
  SRU later when backporting newer mesa to 18.04 we should do the
  transition in bionic before release. Debian has done this now in
  experimental.

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

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

[Touch-packages] [Bug 1760335] Re: cannot add account to ubuntu live update

[Brian Murray]

** Summary changed:

- cannot add account to ubnut live update
+ cannot add account to ubuntu live update

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

Title:
  cannot add account to ubuntu live update

Status in software-properties package in Ubuntu:
  New

Bug description:
  ubuntu 18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.24
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  1 01:22:05 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2017-03-04 (392 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1756006] Re: FFe: Support suspend-then-hibernate

[Dimitri John Ledkov]

@superm1

It would have been nice to coordinate systemd uploads, this is by far,
not the only patch set that needs uploading for systemd.

** Tags added: block-proposed

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

Title:
  FFe: Support suspend-then-hibernate

Status in gnome-settings-daemon package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  Suspend to hibernate is a new feature that will put the system into
  hibernate after a period of time spent in the system's supported sleep
  state.  This mode will be used on some systems that take suspend to
  idle in the future with Ubuntu 18.04.

  This feature is available in upstream systemd from these two commits.
  
https://github.com/systemd/systemd/commit/c58493c00af97146d3b6c24da9c0371978124703
  
https://github.com/systemd/systemd/commit/9aa2e409bcb70f3952b38a35f16fc080c22dd5a5
  This is accepted upstream.

  The policy needs to be made available to gnome from this commit:
  https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/9
  As of 3/15/2018 this is not yet accepted or rejected.

  The new mode is not selected by default, but that can be changed from a 
separate policy package.
  The policy for the amount of time spent in S3/S2I can be configured by a 
separate package.

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

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

[Touch-packages] [Bug 1760739] Re: package libkrb5-26-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall

[Joshua Powers]

>From terminal log:

dpkg: error processing package libkrb5-26-heimdal:amd64 (--configure):
 package is in a very bad inconsistent state; you should
 reinstall it before attempting configuration

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

Title:
  package libkrb5-26-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1.16.04.1
  failed to install/upgrade: package is in a very bad inconsistent
  state; you should  reinstall it before attempting configuration

Status in heimdal package in Ubuntu:
  Incomplete

Bug description:
  failure on update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libkrb5-26-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1.16.04.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
  Architecture: amd64
  Date: Mon Apr  2 21:07:40 2018
  DpkgHistoryLog:
   Start-Date: 2018-04-02  21:07:38
   Commandline: aptdaemon role='role-commit-packages' sender=':1.123'
   Upgrade: lshw:amd64 (02.17-1.1ubuntu3.4, 02.17-1.1ubuntu3.5)
  DuplicateSignature:
   package:libkrb5-26-heimdal:amd64:1.7~git20150920+dfsg-4ubuntu1.16.04.1
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package libkrb5-26-heimdal:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-11-03 (150 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: heimdal
  Title: package libkrb5-26-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1.16.04.1 
failed to install/upgrade: package is in a very bad inconsistent state; you 
should  reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1760739] Re: package libkrb5-26-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall

[Joshua Powers]

Thank you for taking the time to file a bug report.

One of your packages is reporting that it is in an inconsistent state. This
needs to be solved before you continue further operations. To help you get
started please see this question and response:
https://askubuntu.com/questions/148715/how-to-fix-package-is-in-a-very-bad-inconsistent-state-error

Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'.

However, if you believe that this is really a bug in Ubuntu, then we would
be grateful if you would provide a more complete description of the problem
with steps to reproduce, explain why you believe this is a bug in Ubuntu
rather than a problem specific to your system, and then change the bug
status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

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

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

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

Title:
  package libkrb5-26-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1.16.04.1
  failed to install/upgrade: package is in a very bad inconsistent
  state; you should  reinstall it before attempting configuration

Status in heimdal package in Ubuntu:
  Incomplete

Bug description:
  failure on update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libkrb5-26-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1.16.04.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
  Architecture: amd64
  Date: Mon Apr  2 21:07:40 2018
  DpkgHistoryLog:
   Start-Date: 2018-04-02  21:07:38
   Commandline: aptdaemon role='role-commit-packages' sender=':1.123'
   Upgrade: lshw:amd64 (02.17-1.1ubuntu3.4, 02.17-1.1ubuntu3.5)
  DuplicateSignature:
   package:libkrb5-26-heimdal:amd64:1.7~git20150920+dfsg-4ubuntu1.16.04.1
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package libkrb5-26-heimdal:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-11-03 (150 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: heimdal
  Title: package libkrb5-26-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1.16.04.1 
failed to install/upgrade: package is in a very bad inconsistent state; you 
should  reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

[ChristianEhrhardt]

I heard people talk about it, but realized the tracker is missing a Task for 
openvswitch:
/etc/network/if-post-down.d/openvswitch
/etc/network/if-pre-up.d/openvswitch

IIRC all the discussions correctly that was one of the harder cases due
to "Pre" not really being a defined thing anymore.

The question is how much OVS relies on that to work as PRE, or if it can
be later (or totally ignored).

I'll ping Jamespage about this for his OVS experience.

P.S. sorry if I duplicate some work here, but I can't find it in the bug
at all, so better twice than missed.

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

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Confirmed
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  New
Status in epoptes package in Ubuntu:
  New
Status in ethtool package in Ubuntu:
  New
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  New
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Touch-packages] [Bug 1761003] Re: Bionic Beaver - not able to connect to WPA Enterprise EAP-TLS

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

** Package changed: gnome-control-center (Ubuntu) => network-manager
(Ubuntu)

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

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

Title:
  Bionic Beaver - not able to connect to WPA Enterprise EAP-TLS

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hello,

  since update to Bionic Beaver I can't connect to my WPA2-Entertrise EAP TLS 
network. Running Freeradius 2.29 on a DDWRT router. In 16.04 it worked, in the 
dual boot Windows 10 environment it is still working with the same certificates.
  It is a hidden network, adding it by "connect to a hidden network" entering 
SSID, UserID, ca.pem as CA cert, user cert xxx.p12 file and user certificate 
password.
  Tried a lot not getting it working. The password entry dialog for the network 
is always popping up upon connection trials. The password is for sure the 
correct one, checked it very often.
  If I'm able to I'll attach a syslog and kern.log of error occurense.

  Thanks for investigation and inputs.

  Best regards

  Kitsab

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Apr  3 23:52:23 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2015-02-14 (1144 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1761210] [NEW] help

[Arnold Rivera]

Public bug reported:

help

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg (not installed)
ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-37-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: Wed Apr  4 22:28:18 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Skylake Integrated Graphics [1025:110f]
InstallationDate: Installed on 2018-03-28 (6 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 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 003: ID 04f2:b573 Chicony Electronics Co., Ltd 
 Bus 001 Device 002: ID 04ca:3015 Lite-On Technology Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire E5-475
ProcEnviron:
 LANGUAGE=en_PH:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_PH.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=UUID=59957697-26e9-4c70-89af-17906e8edf33 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/29/2016
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.01
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: AntMan_SK
dmi.board.vendor: Acer
dmi.board.version: V1.01
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.01:bd03/29/2016:svnAcer:pnAspireE5-475:pvrV1.01:rvnAcer:rnAntMan_SK:rvrV1.01:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: SKL
dmi.product.name: Aspire E5-475
dmi.product.version: V1.01
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
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 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Apr  4 22:16:25 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

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


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

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

Title:
  help

Status in xorg package in Ubuntu:
  New

Bug description:
  help

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-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: Wed Apr  4 22:28:18 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Skylake Integrated Graphics [1025:110f]
  InstallationDate: Installed on 2018-03-28 (6 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 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 04f2:b573 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 04ca:3015 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire E5-475
  ProcEnviron:
   LANGUAGE=en_PH:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: 

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

[waltergross]

Public bug reported:

automatic installation

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-119-generic 4.4.0-119.143
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/controlC1:  gdm2134 F pulseaudio
  wgross 2474 F pulseaudio
 /dev/snd/controlC0:  gdm2134 F pulseaudio
  wgross 2474 F pulseaudio
Date: Wed Apr  4 15:40:24 2018
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=3640f222-dcff-4022-bc8a-d9a6fe26fa9d
InstallationDate: Installed on 2017-03-21 (378 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
IwConfig:
 lono wireless extensions.
 
 enp3s0no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic root=/dev/sda1 ro 
drm.debug=0xe plymouth:debug
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.17
RfKill:
 
SourcePackage: initramfs-tools
Title: package linux-image-4.4.0-119-generic 4.4.0-119.143 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/16/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F4
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H77-DS3H
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.:bvrF4:bd04/16/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77-DS3H: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.

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


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

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

Title:
  package linux-image-4.4.0-119-generic 4.4.0-119.143 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  automatic installation

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-119-generic 4.4.0-119.143
  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/controlC1:  gdm2134 F pulseaudio
wgross 2474 F pulseaudio
   /dev/snd/controlC0:  gdm2134 F pulseaudio
wgross 2474 F pulseaudio
  Date: Wed Apr  4 15:40:24 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=3640f222-dcff-4022-bc8a-d9a6fe26fa9d
  InstallationDate: Installed on 2017-03-21 (378 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic root=/dev/sda1 
ro drm.debug=0xe plymouth:debug
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.17
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-119-generic 4.4.0-119.143 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77-DS3H
  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: 

[Touch-packages] [Bug 1761180] Re: systemd-logind crashed with SIGABRT in log_assert_failed_realm()

[Apport retracing service]

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

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 #1710498, 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/1761180/+attachment/5101287/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of private bug 1710498

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

Title:
  systemd-logind crashed with SIGABRT in log_assert_failed_realm()

Status in systemd package in Ubuntu:
  New

Bug description:
  I did not notice the crash and cannot provide more details.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  Date: Wed Apr  4 14:57:45 2018
  ExecutablePath: /lib/systemd/systemd-logind
  InstallationDate: Installed on 2018-04-04 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  MachineType: FUJITSU LIFEBOOK E751
  ProcCmdline: /lib/systemd/systemd-logind
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=611b8a5d-acac-4bd6-a757-a6a507ba0cc9 ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   log_assert_failed_realm () from /lib/systemd/libsystemd-shared-237.so
   close_nointr () 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-logind crashed with SIGABRT in log_assert_failed_realm()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/25/2011
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.13
  dmi.board.name: FJNB223
  dmi.board.vendor: FUJITSU
  dmi.board.version: F3
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: LIFEBOOK E751
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.13:bd04/25/2011:svnFUJITSU:pnLIFEBOOKE751:pvr10601186096:rvnFUJITSU:rnFJNB223:rvrF3:cvnFUJITSU:ct10:cvrLIFEBOOKE751:
  dmi.product.name: LIFEBOOK E751
  dmi.product.version: 10601186096
  dmi.sys.vendor: FUJITSU
  mtime.conffile..etc.systemd.logind.conf: 2018-04-04T14:57:21.534906

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

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

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

[Jamie Strandboge]

https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1761176 filed
for messaging-app.

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

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1761003] [NEW] Bionic Beaver - not able to connect to WPA Enterprise EAP-TLS

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hello,

since update to Bionic Beaver I can't connect to my WPA2-Entertrise EAP TLS 
network. Running Freeradius 2.29 on a DDWRT router. In 16.04 it worked, in the 
dual boot Windows 10 environment it is still working with the same certificates.
It is a hidden network, adding it by "connect to a hidden network" entering 
SSID, UserID, ca.pem as CA cert, user cert xxx.p12 file and user certificate 
password.
Tried a lot not getting it working. The password entry dialog for the network 
is always popping up upon connection trials. The password is for sure the 
correct one, checked it very often.
If I'm able to I'll attach a syslog and kern.log of error occurense.

Thanks for investigation and inputs.

Best regards

Kitsab

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.0-0ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Apr  3 23:52:23 2018
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2015-02-14 (1144 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic
-- 
Bionic Beaver - not able to connect to WPA Enterprise EAP-TLS
https://bugs.launchpad.net/bugs/1761003
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to network-manager 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 1761176] Re: remove one more old Touch profile that causes profile compilation errors

[Jamie Strandboge]

** Summary changed:

- remove more old Touch profiles that cause profile compilation errors
+ remove one more old Touch profile that causes profile compilation errors

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

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

Title:
  remove one more old Touch profile that causes profile compilation
  errors

Status in apparmor package in Ubuntu:
  Fix Committed

Bug description:
  This is an extension of
  https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1756800 where
  we missed messaging-app.

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

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

[Touch-packages] [Bug 1761199] Re: package linux-image-4.4.0-119-generic 4.4.0-119.143 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1761199

Title:
  package linux-image-4.4.0-119-generic 4.4.0-119.143 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  automatic installation

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-119-generic 4.4.0-119.143
  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/controlC1:  gdm2134 F pulseaudio
wgross 2474 F pulseaudio
   /dev/snd/controlC0:  gdm2134 F pulseaudio
wgross 2474 F pulseaudio
  Date: Wed Apr  4 15:40:24 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=3640f222-dcff-4022-bc8a-d9a6fe26fa9d
  InstallationDate: Installed on 2017-03-21 (378 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic root=/dev/sda1 
ro drm.debug=0xe plymouth:debug
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.17
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-119-generic 4.4.0-119.143 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77-DS3H
  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.:bvrF4:bd04/16/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77-DS3H: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.

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

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

[Touch-packages] [Bug 1760934] Re: Sound not working on HP x2 10-p030nl - Realtek rt5640

[Daniele Laudani]

Interestingly, even though pulseaudio doesn't start and no sound
indicator appears on the system, if I start something using VLC, the
audio works. No sound in the browser or system, only in VLC. I guess
this is due to some bugs in pulseaudio, isn't it?

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

Title:
  Sound not working on HP x2 10-p030nl - Realtek rt5640

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Audio doesn't work on every kernel I tried. I also used this
  https://github.com/plbossart/UCM, but this results in a pulseaudio
  crash. See this for more information:
  https://github.com/plbossart/UCM/issues/27

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  Uname: Linux 4.16.0-rc6+ x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer', 
'/dev/sequencer2', '/dev/sequencer'] failed with exit code 1:
  CurrentDesktop: KDE
  Date: Tue Apr  3 19:19:35 2018
  InstallationDate: Installed on 2018-03-27 (6 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827C
  dmi.board.vendor: HP
  dmi.board.version: 93.23
  dmi.chassis.type: 32
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.30:bd10/25/2017:svnHP:pnHPx2Detachable10-p0XX:pvr:rvnHP:rn827C:rvr93.23:cvnHP:ct32:cvrChassisVersion:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP x2 Detachable 10-p0XX
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1749546] Re: Booting a live session is slow - fontconfig regenerates its font cache

[Iain Lane]

I've submitted a patch on the upstream bug - hopefully will get some
feedback quickly. I'm not super sure if it's a sensible approach.

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

Title:
  Booting a live session is slow - fontconfig regenerates its font cache

Status in Fontconfig:
  Confirmed
Status in fontconfig package in Ubuntu:
  In Progress
Status in fontconfig source package in Bionic:
  In Progress

Bug description:
  On Bionic Ubuntu Desktop booting to a live session is slow. It takes
  roughly 2 min on my test machine to boot from the "Try or Install
  Ubuntu" boot menu to a usable session.

  It also takes 1 minute to logout and 17s to log in again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: casper 1.388
  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
  CasperVersion: 1.388
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 16:43:19 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: casper
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1752145] Re: system freeze after full screen video viewing with Xorg on ultrawide monitor

[Krister]

Gnome-shell will freeze at unexpected times when using the firefox
browser.  The symptoms are the same as when watching videos with totem.
I've switched to chrome without having gnome-shell freeze on me.

Is there something particular about the way firefox 59 (Quantum)
interacts with my graphics hardware?

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

Title:
  system freeze after full screen video viewing with Xorg on ultrawide
  monitor

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  1. open a video (either youtube or totem)
  2. put it in full screen.
  3. wait

  Eventually (within minutes) the system will freeze in one of 2 ways.

  1. There will be only blackness with no response ( even
  unresponsive).

  2. There will be snow that shifts with keyboard and mouse interaction
  (see photo).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 27 19:08:13 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['workspace-g...@mathematical.coffee.gmail.com', 
'alt-tab-worksp...@kwalo.net', 'system-moni...@paradoxxx.zero.gmail.com', 
'user-th...@gnome-shell-extensions.gcampax.github.com', 
'ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']"
   b'org.gnome.shell' b'enable-hot-corners' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['googleinbox.desktop', 
'googlecalendar.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 11'"
  InstallationDate: Installed on 2018-01-05 (53 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2018-01-05 (53 days ago)

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

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

[Touch-packages] [Bug 1761084] Re: NA

[Leonidas S. Barbosa]

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

Title:
  NA

Status in xorg package in Ubuntu:
  New

Bug description:
  NA

  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
  .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: Wed Apr  4 12:48:47 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:3809]
  InstallationDate: Installed on 2018-03-04 (31 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 04f2:b50e Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80Q7
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=6443b635-7581-4cac-989d-220941f038da ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/26/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: D5CN47WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Paris 5A8
  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 ideapad 300-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrD5CN47WW:bd08/26/2016:svnLENOVO:pn80Q7:pvrLenovoideapad300-15ISK:rvnLENOVO:rnParis5A8:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad300-15ISK:
  dmi.product.name: 80Q7
  dmi.product.version: Lenovo ideapad 300-15ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 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 Apr  4 15:51:47 2018
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5574 
   vendor CMN
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Touch-packages] [Bug 1761176] [NEW] remove more old Touch profiles that cause profile compilation errors

[Jamie Strandboge]

Public bug reported:

This is an extension of
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1756800 where we
missed messaging-app.

** Affects: apparmor (Ubuntu)
 Importance: Undecided
 Assignee: Jamie Strandboge (jdstrand)
 Status: In Progress

** Description changed:

  This is an extension of
  https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1756800 where we
- missing messaging-app.
+ missed messaging-app.

** Summary changed:

- remove more old Touch profiles
+ remove more old Touch profiles that cause profile compilation errors

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

Title:
  remove more old Touch profiles that cause profile compilation errors

Status in apparmor package in Ubuntu:
  In Progress

Bug description:
  This is an extension of
  https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1756800 where
  we missed messaging-app.

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

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

[Touch-packages] [Bug 1749546] Re: Booting a live session is slow - fontconfig regenerates its font cache

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1749546

** Tags added: iso-testing

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

Title:
  Booting a live session is slow - fontconfig regenerates its font cache

Status in Fontconfig:
  Confirmed
Status in fontconfig package in Ubuntu:
  In Progress
Status in fontconfig source package in Bionic:
  In Progress

Bug description:
  On Bionic Ubuntu Desktop booting to a live session is slow. It takes
  roughly 2 min on my test machine to boot from the "Try or Install
  Ubuntu" boot menu to a usable session.

  It also takes 1 minute to logout and 17s to log in again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: casper 1.388
  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
  CasperVersion: 1.388
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 16:43:19 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: casper
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Jamie Strandboge]

Actually, only messaging-app is affected by this bug, so we don't need
to remove the other two.

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

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1732030] Re: 'apt update' dies with seccomp error

[Julian Andres Klode]

Or generally allow network and the getdents stuff, and just block more
esoteric syscalls for now.

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

Title:
  'apt update' dies with seccomp error

Status in apt package in Ubuntu:
  Confirmed
Status in libvirt package in Ubuntu:
  Fix Released

Bug description:
  $ apt-get update
  0% [Working]
    Seccomp prevented execution of syscall 78 on architecture amd64 

  Reading package lists... Done
  E: Method mirror has died unexpectedly!
  E: Sub-process mirror returned an error code (31)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6~alpha5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Mon Nov 13 23:10:57 2017
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2017-05-20 (177 days ago)

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

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

[Touch-packages] [Bug 1732030] Re: 'apt update' dies with seccomp error

[Julian Andres Klode]

I wonder if we should turn the sandbox off by default for bionic. Not
sure.

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

Title:
  'apt update' dies with seccomp error

Status in apt package in Ubuntu:
  Confirmed
Status in libvirt package in Ubuntu:
  Fix Released

Bug description:
  $ apt-get update
  0% [Working]
    Seccomp prevented execution of syscall 78 on architecture amd64 

  Reading package lists... Done
  E: Method mirror has died unexpectedly!
  E: Sub-process mirror returned an error code (31)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6~alpha5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Mon Nov 13 23:10:57 2017
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2017-05-20 (177 days ago)

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

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

[Touch-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service

[Jean-Baptiste Lallement]

For reference, the lp report tracking the fontconfig issue is bug
1749546

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

Title:
  Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut:
  Failed to activate service 'org.bluez': timed out
  (service_start_timeout=25000ms)

Status in blueman package in Ubuntu:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Also causing the long time to desktop from try/install livesession
  dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  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
  CurrentDesktop: XFCE
  Date: Sat Mar 10 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:

  rfkill:

  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: 
  [1520681416.8951] Loaded device plugin: NMBluezManager
  (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-
  bluetooth.so)

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

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

[Touch-packages] [Bug 1732030] Re: 'apt update' dies with seccomp error

[Julian Andres Klode]

No - it's the "store" method that's failing (e.g.
recompressing/decompressing files). I disallowed socket and friends for
that, so that's failing. I mean, it's a decompress/compress method, it
should not have network access.

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

Title:
  'apt update' dies with seccomp error

Status in apt package in Ubuntu:
  Confirmed
Status in libvirt package in Ubuntu:
  Fix Released

Bug description:
  $ apt-get update
  0% [Working]
    Seccomp prevented execution of syscall 78 on architecture amd64 

  Reading package lists... Done
  E: Method mirror has died unexpectedly!
  E: Sub-process mirror returned an error code (31)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6~alpha5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Mon Nov 13 23:10:57 2017
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2017-05-20 (177 days ago)

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

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

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

[Jamie Strandboge]

"Do we need to worry about:

ubuntu-download-manager: 
/etc/apparmor.d/usr.lib.ubuntu-download-manager.udm-extractor
messaging-app: /etc/apparmor.d/usr.bin.messaging-app
content-hub-testability: /etc/apparmor.d/content-hub-testability
"

Yes. I did an archive grep and found media-hub, but that grep didn't
find these since they generate the profile from debian/rules. I'm
running a new grep to catch that and will update apparmor accordingly.

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

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1729491] Re: [UIFe] ubuntu-bug says that snap packages are not installed

[Łukasz Zemczak]

UIFe approved. Please proceed.

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

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

Title:
  [UIFe] ubuntu-bug says that snap packages are not installed

Status in apport package in Ubuntu:
  Triaged
Status in ubuntu-docs package in Ubuntu:
  New
Status in apport source package in Bionic:
  Triaged

Bug description:
  User Interface Freeze Exception Justification
  =
  The interface for ubuntu-bug/apport-bug  is super confusing if  
was installed as a snap.

  List Notifications
  ==
  https://lists.ubuntu.com/archives/ubuntu-translators/2018-April/007471.html
  

  Original Bug Description
  
  1.
  I installed the package gnome-recipes, tried to send an error report program 
in response to the received message:you cannot report a problem:
  The report belongs to a package that was not installed.

  2.
  Expected that the program will be identified as installed.

  3.
  sudo apt -f install
  [sudo] password for Alexander:
  Reading package lists... Done
  Building dependency tree
  Reading state information... Ready
  0 upgraded, 0 newly installed, for removal 0 packets are marked, and 0 
packages are not updated.
  sudo gnome-sudo recipes: gnome-recipes: command not found
  sudo apt install gnome-recipes Reading package lists... Done
  Building dependency tree
  Reading state information... Ready
  E: unable to locate package gnome-recipes

  I installed via software-center

  gnome-recipes
  snap-confine has elevated permissions and is not confined but should be. 
Refusing to continue to avoid permission escalation attacks
  ubuntu-bug gnome-recipes
  dpkg-query: template gnome-recipes no corresponding package
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  ^C^Z
  [1]+ Stopped ubuntu-bug gnome-recipes

  https://youtu.be/AXtR5m2uqUg
  ---

  1.
  произвёл установку пакета gnome-recipes, попытался отправить отчёт об ошибке 
программы, в ответ получил сообщение:Не удаётся сообщить о неполадке:
  Отчёт относится к пакету , который не был установлен.

  2.
  Ожидал что программа будет идентифицироваться как установленная.

  3.
  sudo apt -f install
  [sudo] пароль для alexandr:
  Чтение списков пакетов… Готово
  Построение дерева зависимостей
  Чтение информации о состоянии… Готово
  обновлено 0, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 
0 пакетов не обновлено.
  sudo gnome-recipes sudo: gnome-recipes: команда не найдена
  sudo apt install gnome-recipes Чтение списков пакетов… Готово
  Построение дерева зависимостей
  Чтение информации о состоянии… Готово
  E: Не удалось найти пакет gnome-recipes

  произвёл установку через software-center

  gnome-recipes
  snap-confine has elevated permissions and is not confined but should be. 
Refusing to continue to avoid permission escalation attacks
  ubuntu-bug gnome-recipes
  dpkg-query: шаблону gnome-recipes не соответствует ни один пакет
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  ^C^Z
  [1]+  Остановлено  ubuntu-bug gnome-recipes

  https://youtu.be/AXtR5m2uqUg

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: software-center (not installed)
  Uname: Linux 4.14.0-041400rc7-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov  2 08:06:48 2017
  InstallationDate: Installed on 2017-10-29 (3 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: software-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1749546] Re: Booting a live session is slow - fontconfig regenerates its font cache

[Bug Watch Updater]

** Changed in: fontconfig
   Status: Unknown => Confirmed

** Changed in: fontconfig
   Importance: Unknown => Medium

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

Title:
  Booting a live session is slow - fontconfig regenerates its font cache

Status in Fontconfig:
  Confirmed
Status in fontconfig package in Ubuntu:
  In Progress
Status in fontconfig source package in Bionic:
  In Progress

Bug description:
  On Bionic Ubuntu Desktop booting to a live session is slow. It takes
  roughly 2 min on my test machine to boot from the "Try or Install
  Ubuntu" boot menu to a usable session.

  It also takes 1 minute to logout and 17s to log in again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: casper 1.388
  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
  CasperVersion: 1.388
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 16:43:19 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: casper
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1732030] Re: 'apt update' dies with seccomp error

[ChristianEhrhardt]

Something seems broken on your config, all those basic things should be
allowed IMHO (and they are, or I'd hit them as well).

You could iterate on this with [1] which for this would let you also add 
"connect".
But I doubt that will eventually resolve your issue.
The question is why does it break on you at all while it is working for others 
in general.

If you iterate adding more and more excuses you might come back with the list 
that you needed.
But I'm pretty sure connect and socket would have been allowed already if 
everything would be right.

[1]: https://filippo.io/linux-syscall-table/

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

Title:
  'apt update' dies with seccomp error

Status in apt package in Ubuntu:
  Confirmed
Status in libvirt package in Ubuntu:
  Fix Released

Bug description:
  $ apt-get update
  0% [Working]
    Seccomp prevented execution of syscall 78 on architecture amd64 

  Reading package lists... Done
  E: Method mirror has died unexpectedly!
  E: Sub-process mirror returned an error code (31)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6~alpha5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Mon Nov 13 23:10:57 2017
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2017-05-20 (177 days ago)

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

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

[Touch-packages] [Bug 1749546] Re: Booting a live session is slow - fontconfig regenerates its font cache

[Will Cooke]

** Tags removed: rls-bb-incoming

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

Title:
  Booting a live session is slow - fontconfig regenerates its font cache

Status in Fontconfig:
  Confirmed
Status in fontconfig package in Ubuntu:
  In Progress
Status in fontconfig source package in Bionic:
  In Progress

Bug description:
  On Bionic Ubuntu Desktop booting to a live session is slow. It takes
  roughly 2 min on my test machine to boot from the "Try or Install
  Ubuntu" boot menu to a usable session.

  It also takes 1 minute to logout and 17s to log in again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: casper 1.388
  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
  CasperVersion: 1.388
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 16:43:19 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: casper
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1749546] Re: Booting a live session is slow - fontconfig regenerates its font cache

[Jean-Baptiste Lallement]

** Summary changed:

- Booting a live session is slow 
+ Booting a live session is slow - fontconfig regenerates its font cache

** Also affects: fontconfig via
   https://bugs.freedesktop.org/show_bug.cgi?id=103652
   Importance: Unknown
   Status: Unknown

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

Title:
  Booting a live session is slow - fontconfig regenerates its font cache

Status in Fontconfig:
  Unknown
Status in fontconfig package in Ubuntu:
  In Progress
Status in fontconfig source package in Bionic:
  In Progress

Bug description:
  On Bionic Ubuntu Desktop booting to a live session is slow. It takes
  roughly 2 min on my test machine to boot from the "Try or Install
  Ubuntu" boot menu to a usable session.

  It also takes 1 minute to logout and 17s to log in again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: casper 1.388
  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
  CasperVersion: 1.388
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 16:43:19 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: casper
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1749546] Re: Booting a live session is slow

[Iain Lane]

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

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

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

Title:
  Booting a live session is slow

Status in fontconfig package in Ubuntu:
  In Progress
Status in fontconfig source package in Bionic:
  In Progress

Bug description:
  On Bionic Ubuntu Desktop booting to a live session is slow. It takes
  roughly 2 min on my test machine to boot from the "Try or Install
  Ubuntu" boot menu to a usable session.

  It also takes 1 minute to logout and 17s to log in again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: casper 1.388
  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
  CasperVersion: 1.388
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 16:43:19 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: casper
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1749546] Re: Booting a live session is slow

[Launchpad Bug Tracker]

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

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

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

Title:
  Booting a live session is slow

Status in fontconfig package in Ubuntu:
  In Progress
Status in fontconfig source package in Bionic:
  In Progress

Bug description:
  On Bionic Ubuntu Desktop booting to a live session is slow. It takes
  roughly 2 min on my test machine to boot from the "Try or Install
  Ubuntu" boot menu to a usable session.

  It also takes 1 minute to logout and 17s to log in again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: casper 1.388
  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
  CasperVersion: 1.388
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 16:43:19 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: casper
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1749546] Re: Booting a live session is slow

[Will Cooke]

Thanks to ali1234 this was tracked down to font-config rebuilding the
cache at the start of the live session.  Something changed in the way
fontconfig validates the caches and so they are being rebuilt at the
start of the live session.

This bug is likely related:
https://bugs.freedesktop.org/show_bug.cgi?id=103652


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

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

** Also affects: casper (Ubuntu Bionic)
   Importance: Undecided
 Assignee: Canonical Desktop Team (canonical-desktop-team)
   Status: New

** No longer affects: casper (Ubuntu)

** No longer affects: casper (Ubuntu Bionic)

** Changed in: fontconfig (Ubuntu Bionic)
 Assignee: (unassigned) => Canonical Desktop Team (canonical-desktop-team)

** Bug watch added: freedesktop.org Bugzilla #103652
   https://bugs.freedesktop.org/show_bug.cgi?id=103652

** Changed in: fontconfig (Ubuntu Bionic)
 Assignee: Canonical Desktop Team (canonical-desktop-team) => Iain Lane 
(laney)

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

Title:
  Booting a live session is slow

Status in fontconfig package in Ubuntu:
  In Progress
Status in fontconfig source package in Bionic:
  In Progress

Bug description:
  On Bionic Ubuntu Desktop booting to a live session is slow. It takes
  roughly 2 min on my test machine to boot from the "Try or Install
  Ubuntu" boot menu to a usable session.

  It also takes 1 minute to logout and 17s to log in again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: casper 1.388
  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
  CasperVersion: 1.388
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 16:43:19 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: casper
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1760934] Re: Sound not working on HP x2 10-p030nl - Realtek rt5640

[Daniele Laudani]

I tried that workaround, but it didn't work. I also purged and
reinstalled pulseaudio, still nothing.

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

Title:
  Sound not working on HP x2 10-p030nl - Realtek rt5640

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Audio doesn't work on every kernel I tried. I also used this
  https://github.com/plbossart/UCM, but this results in a pulseaudio
  crash. See this for more information:
  https://github.com/plbossart/UCM/issues/27

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  Uname: Linux 4.16.0-rc6+ x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer', 
'/dev/sequencer2', '/dev/sequencer'] failed with exit code 1:
  CurrentDesktop: KDE
  Date: Tue Apr  3 19:19:35 2018
  InstallationDate: Installed on 2018-03-27 (6 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827C
  dmi.board.vendor: HP
  dmi.board.version: 93.23
  dmi.chassis.type: 32
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.30:bd10/25/2017:svnHP:pnHPx2Detachable10-p0XX:pvr:rvnHP:rn827C:rvr93.23:cvnHP:ct32:cvrChassisVersion:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP x2 Detachable 10-p0XX
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1732030] Re: 'apt update' dies with seccomp error

[Jimmy Olsen]

Ok, tried again.. It still not working. Error is 42 though:

marcos@marcos:~$ echo 'apt::sandbox::seccomp::allow { "socket" };' | sudo tee 
/etc/apt/apt.conf.d/99seccomp
[sudo] password for marcos: 
apt::sandbox::seccomp::allow { "socket" };
marcos@marcos:~$ sudo apt update
Get:1 http://br.archive.ubuntu.com/ubuntu bionic InRelease [235 kB]
Hit:2 http://linux.teamviewer.com/deb stable InRelease 
Hit:3 http://linux.teamviewer.com/deb preview InRelease
Hit:4 http://br.archive.ubuntu.com/ubuntu bionic-updates InRelease 
Hit:5 http://br.archive.ubuntu.com/ubuntu bionic-backports InRelease   
Hit:6 http://archive.canonical.com/ubuntu bionic InRelease 
Hit:7 http://ppa.launchpad.net/ubuntubudgie/backports/ubuntu bionic InRelease  
Hit:8 http://security.ubuntu.com/ubuntu bionic-security InRelease
Get:9 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1.018 kB]
0% [9 Packages store 0 B] [4 InRelease gpgv 65,4 kB] [Waiting for headers]
  Seccomp prevented execution of syscall 42 on architecture amd64 

Reading package lists... Done 
E: Method store has died unexpectedly!
E: Sub-process store returned an error code (31)
marcos@marcos:~$

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

Title:
  'apt update' dies with seccomp error

Status in apt package in Ubuntu:
  Confirmed
Status in libvirt package in Ubuntu:
  Fix Released

Bug description:
  $ apt-get update
  0% [Working]
    Seccomp prevented execution of syscall 78 on architecture amd64 

  Reading package lists... Done
  E: Method mirror has died unexpectedly!
  E: Sub-process mirror returned an error code (31)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6~alpha5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Mon Nov 13 23:10:57 2017
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2017-05-20 (177 days ago)

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

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

[Touch-packages] [Bug 1760598] Re: I/O Error after clicking "reboot now" - Ubuntu font missing from casper shutdown

[Dimitri John Ledkov]

** Summary changed:

- I/O Error after clicking "reboot now"
+ I/O Error after clicking "reboot now" - Ubuntu font missing from casper 
shutdown

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

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

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

** Description changed:

+ ubuntu Plymouth theme now correctly uses Ubuntu font, meaning it needs
+ to be cached for display of the shutdown message.
+ 
+ We really should be using shutdown initramfs on the livecd
+ 
+ --
+ 
  Tested in Virtualbox VM.
  Ubuntu MATE works after force-reboot, but after I click on "restart now" 
after completing the installation, the screen shows me this:
  
  req_error: I/O error, dev sr0, sector 1488792
  
  And the above message loops a couple times, and wont turn off the
  computer to restart.
  
  No error happens after force reboot, and the OS boots properly, but I'm
  curious as to what's causing this.

** Changed in: casper (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  I/O Error after clicking "reboot now" - Ubuntu font missing from
  casper shutdown

Status in ubuntu-mate:
  New
Status in casper package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Confirmed
Status in ubuntu-mate-welcome package in Ubuntu:
  Invalid

Bug description:
  ubuntu Plymouth theme now correctly uses Ubuntu font, meaning it needs
  to be cached for display of the shutdown message.

  We really should be using shutdown initramfs on the livecd

  --

  Tested in Virtualbox VM.
  Ubuntu MATE works after force-reboot, but after I click on "restart now" 
after completing the installation, the screen shows me this:

  req_error: I/O error, dev sr0, sector 1488792

  And the above message loops a couple times, and wont turn off the
  computer to restart.

  No error happens after force reboot, and the OS boots properly, but
  I'm curious as to what's causing this.

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

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

[Touch-packages] [Bug 1761096] Re: dnsmasq starts with error on Ubuntu Xenial amd64 when squid installed

[Olivier Bourdon]

I works also very well with trusty

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

Title:
  dnsmasq starts with error on Ubuntu Xenial amd64 when squid installed

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  Setup to reproduce:

  Ubuntu Xenial amd64 net install iso from
  http://archive.ubuntu.com/ubuntu/dists/xenial/main/installer-
  amd64/current/images/netboot/mini.iso

  Install system with mostly defaults + LVM + OpenSSH server

  Note that this bug applies to both DHCP and static IP+DNS network
  configurations

  Once server rebooted and is available, log in and install dnsmasq + squid:
  apt-get update && apt-get install squid dnsmasq

  output of this can be found at https://pastebin.com/9Atuipju
  journalctl -xe output at https://pastebin.com/uLhfM4jN

  Furthermore at this point I can run alternating errors

  root@ubuntu-min:~# date ; service dnsmasq start ; date
  Wed Apr  4 09:18:07 CEST 2018
  Wed Apr  4 09:18:07 CEST 2018
  root@ubuntu-min:~# date ; service dnsmasq stop ; date
  Wed Apr  4 09:18:39 CEST 2018
  Wed Apr  4 09:18:39 CEST 2018
  root@ubuntu-min:~# date ; service dnsmasq start ; date
  Wed Apr  4 09:19:10 CEST 2018
  Job for dnsmasq.service failed because a timeout was exceeded. See "systemctl 
status dnsmasq.service" and "journalctl -xe" for details.
  Wed Apr  4 09:20:40 CEST 2018
  root@ubuntu-min:~# date ; service dnsmasq start ; date
  Wed Apr  4 09:42:57 CEST 2018
  Wed Apr  4 09:42:57 CEST 2018
  root@ubuntu-min:~# date ; service dnsmasq stop ; date
  Wed Apr  4 09:43:14 CEST 2018
  Wed Apr  4 09:43:14 CEST 2018
  root@ubuntu-min:~# date ; service dnsmasq start ; date
  Wed Apr  4 09:43:26 CEST 2018
  Job for dnsmasq.service failed because a timeout was exceeded. See "systemctl 
status dnsmasq.service" and "journalctl -xe" for details.
  Wed Apr  4 09:44:56 CEST 2018

  and so on... Each and every 1 out of 2 stop/start cycle fails in 1m30s
  timeout

  Complete journalctl -xe output attached

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

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

[Touch-packages] [Bug 1743873] Re: rsync version for xenial

[Bug Watch Updater]

** Changed in: rsync (Debian)
   Status: Unknown => Fix Released

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

Title:
  rsync version for xenial

Status in rsync package in Ubuntu:
  Confirmed
Status in rsync package in Debian:
  Fix Released

Bug description:
  Any chance that rsync could be updated to 3.1.2 for xenial?

  The --backup-dir option in 3.1.1 doesn't work properly - it creates
  empty directories even when no files need to be put in them.

  Thanks,
  -Jeff

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

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

[Touch-packages] [Bug 1761096] Re: dnsmasq starts with error on Ubuntu Xenial amd64 when squid installed

[Olivier Bourdon]

Note that this does not apply to bionic release nor artful for which
everything seems to be working very smoothly

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

Title:
  dnsmasq starts with error on Ubuntu Xenial amd64 when squid installed

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  Setup to reproduce:

  Ubuntu Xenial amd64 net install iso from
  http://archive.ubuntu.com/ubuntu/dists/xenial/main/installer-
  amd64/current/images/netboot/mini.iso

  Install system with mostly defaults + LVM + OpenSSH server

  Note that this bug applies to both DHCP and static IP+DNS network
  configurations

  Once server rebooted and is available, log in and install dnsmasq + squid:
  apt-get update && apt-get install squid dnsmasq

  output of this can be found at https://pastebin.com/9Atuipju
  journalctl -xe output at https://pastebin.com/uLhfM4jN

  Furthermore at this point I can run alternating errors

  root@ubuntu-min:~# date ; service dnsmasq start ; date
  Wed Apr  4 09:18:07 CEST 2018
  Wed Apr  4 09:18:07 CEST 2018
  root@ubuntu-min:~# date ; service dnsmasq stop ; date
  Wed Apr  4 09:18:39 CEST 2018
  Wed Apr  4 09:18:39 CEST 2018
  root@ubuntu-min:~# date ; service dnsmasq start ; date
  Wed Apr  4 09:19:10 CEST 2018
  Job for dnsmasq.service failed because a timeout was exceeded. See "systemctl 
status dnsmasq.service" and "journalctl -xe" for details.
  Wed Apr  4 09:20:40 CEST 2018
  root@ubuntu-min:~# date ; service dnsmasq start ; date
  Wed Apr  4 09:42:57 CEST 2018
  Wed Apr  4 09:42:57 CEST 2018
  root@ubuntu-min:~# date ; service dnsmasq stop ; date
  Wed Apr  4 09:43:14 CEST 2018
  Wed Apr  4 09:43:14 CEST 2018
  root@ubuntu-min:~# date ; service dnsmasq start ; date
  Wed Apr  4 09:43:26 CEST 2018
  Job for dnsmasq.service failed because a timeout was exceeded. See "systemctl 
status dnsmasq.service" and "journalctl -xe" for details.
  Wed Apr  4 09:44:56 CEST 2018

  and so on... Each and every 1 out of 2 stop/start cycle fails in 1m30s
  timeout

  Complete journalctl -xe output attached

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

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

[Touch-packages] [Bug 1761114] Re: systemd build error on aarch64 with "Failed to parse personality, ignoring: x86"

[Neil]

verified, build failed with version 229-4ubuntu21.2.
I was built with the command:

# dpkg-buildpackage -j4

I have passed the build with the commit mentioned on my aarch64 machine,
if build command is right, it is fine for me.

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

Title:
  systemd build error on aarch64 with "Failed to parse personality,
  ignoring: x86"

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  download source code from 
https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21,
  build with `dpkg-buildpackage` on aarch64, and build break with the following 
messages:

  ```
  + test /tmp/test-exec_workingdirectory = /tmp/test-exec_workingdirectory
2 
[/root/neil/systemd/test/systemd-229.orig/test/test-execute/exec-personality-x86.service:7]
 Failed to parse personality, ignoring: x86
3 + uname -m
4 + c=aarch64
5 + test aarch64 = i686
6 exec-personality-x86.service: Main process exited, code=exited, 
status=1/FAILURE
7 exec-personality-x86.service: Unit entered failed state.
8 exec-personality-x86.service: Failed with result 'exit-code'.
9 Assertion 'service->main_exec_status.status == status_expected' failed at 
../src/test/test-execute.c:65, function check(). Aborting.
  ```

  it should run into x86 test case with:
  ```
  87  static void test_exec_personality(Manager *m) {
  88  #if defined(__x86_64__)
  89  test(m, "exec-personality-x86-64.service", 0, CLD_EXITED);
  90  
  91  #elif defined(__s390__)
  92  test(m, "exec-personality-s390.service", 0, CLD_EXITED);
  93  
  94  #else
  95  test(m, "exec-personality-x86.service", 0, CLD_EXITED);
  96  #endif
  97  }
  ```

  after checked upstream systemd source code,
  https://github.com/systemd/systemd/commit/12591863 will fix it.

  is this patch already applied? or I get invalid build steps on
  aarch64?

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

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

[Touch-packages] [Bug 1761114] Re: systemd build error on aarch64 with "Failed to parse personality, ignoring: x86"

[Neil]

I am taking some features off on systemd, so i have to rebuild systemd package. 
Yes, I am building as root, and after pull the latest release and checked the 
source code,
I think this issue still exists.

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

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

Title:
  systemd build error on aarch64 with "Failed to parse personality,
  ignoring: x86"

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  download source code from 
https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21,
  build with `dpkg-buildpackage` on aarch64, and build break with the following 
messages:

  ```
  + test /tmp/test-exec_workingdirectory = /tmp/test-exec_workingdirectory
2 
[/root/neil/systemd/test/systemd-229.orig/test/test-execute/exec-personality-x86.service:7]
 Failed to parse personality, ignoring: x86
3 + uname -m
4 + c=aarch64
5 + test aarch64 = i686
6 exec-personality-x86.service: Main process exited, code=exited, 
status=1/FAILURE
7 exec-personality-x86.service: Unit entered failed state.
8 exec-personality-x86.service: Failed with result 'exit-code'.
9 Assertion 'service->main_exec_status.status == status_expected' failed at 
../src/test/test-execute.c:65, function check(). Aborting.
  ```

  it should run into x86 test case with:
  ```
  87  static void test_exec_personality(Manager *m) {
  88  #if defined(__x86_64__)
  89  test(m, "exec-personality-x86-64.service", 0, CLD_EXITED);
  90  
  91  #elif defined(__s390__)
  92  test(m, "exec-personality-s390.service", 0, CLD_EXITED);
  93  
  94  #else
  95  test(m, "exec-personality-x86.service", 0, CLD_EXITED);
  96  #endif
  97  }
  ```

  after checked upstream systemd source code,
  https://github.com/systemd/systemd/commit/12591863 will fix it.

  is this patch already applied? or I get invalid build steps on
  aarch64?

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

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

[Touch-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service

[Sebastien Bacher]

the issue sounds like
https://bugs.freedesktop.org/show_bug.cgi?id=103652 /
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880574

"fontconfig now requires nano second mtime precision on files in order to
validate their freshness. squashfs does not seem to support nano second
mtime precision causing any Desktop ISO's made with live-build to regenrate
the font cache at the desktop startup leading to a very slow time to desktop."

** Bug watch added: freedesktop.org Bugzilla #103652
   https://bugs.freedesktop.org/show_bug.cgi?id=103652

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

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

Title:
  Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut:
  Failed to activate service 'org.bluez': timed out
  (service_start_timeout=25000ms)

Status in blueman package in Ubuntu:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Also causing the long time to desktop from try/install livesession
  dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  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
  CurrentDesktop: XFCE
  Date: Sat Mar 10 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:

  rfkill:

  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: 
  [1520681416.8951] Loaded device plugin: NMBluezManager
  (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-
  bluetooth.so)

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

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

[Touch-packages] [Bug 1752415] Re: [patch] Please add command-not-found hints

[Matthias Klose]

** Changed in: python3-defaults (Ubuntu)
   Status: New => Fix Committed

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

Title:
  [patch] Please add command-not-found hints

Status in python3-defaults package in Ubuntu:
  Fix Committed

Bug description:
  The new command-not-found in bionic supports hints from the package
  now. To make command-not-found suggest "python3" on top if a user
  types "python" (when that is not installed) the attached debdiff is
  needed.

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

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

[Touch-packages] [Bug 1743873] Re: rsync version for xenial

[Mantas Kriaučiūnas]

Updating rsync to 3.1.2 would also fix Ubuntu bug #1707136 (Rsyncd doesn't 
start at boot in Ubuntu 16.04), to fix this problem user should run this 
manually:
systemctl enable rsync

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

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

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

Title:
  rsync version for xenial

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

Bug description:
  Any chance that rsync could be updated to 3.1.2 for xenial?

  The --backup-dir option in 3.1.1 doesn't work properly - it creates
  empty directories even when no files need to be put in them.

  Thanks,
  -Jeff

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

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

[Touch-packages] [Bug 1729491] Re: [UIFe] ubuntu-bug says that snap packages are not installed

[Gunnar Hjalmarsson]

Sounds like a well-founded change, only a few srings, and a notification
sent to the ubuntu-translators mailing list.

As regards the desktop guide, it may be motivated to adjust this page:

https://help.ubuntu.com/stable/ubuntu-help/report-ubuntu-bug.html

However, that can wait until next cycle; the current wording is generic
enough to not be incorrect, also with this change.

UIFe ok from a docs and translators POV.

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

** No longer affects: ubuntu-docs (Ubuntu Bionic)

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

Title:
  [UIFe] ubuntu-bug says that snap packages are not installed

Status in apport package in Ubuntu:
  New
Status in ubuntu-docs package in Ubuntu:
  New
Status in apport source package in Bionic:
  New

Bug description:
  User Interface Freeze Exception Justification
  =
  The interface for ubuntu-bug/apport-bug  is super confusing if  
was installed as a snap.

  List Notifications
  ==
  https://lists.ubuntu.com/archives/ubuntu-translators/2018-April/007471.html
  

  Original Bug Description
  
  1.
  I installed the package gnome-recipes, tried to send an error report program 
in response to the received message:you cannot report a problem:
  The report belongs to a package that was not installed.

  2.
  Expected that the program will be identified as installed.

  3.
  sudo apt -f install
  [sudo] password for Alexander:
  Reading package lists... Done
  Building dependency tree
  Reading state information... Ready
  0 upgraded, 0 newly installed, for removal 0 packets are marked, and 0 
packages are not updated.
  sudo gnome-sudo recipes: gnome-recipes: command not found
  sudo apt install gnome-recipes Reading package lists... Done
  Building dependency tree
  Reading state information... Ready
  E: unable to locate package gnome-recipes

  I installed via software-center

  gnome-recipes
  snap-confine has elevated permissions and is not confined but should be. 
Refusing to continue to avoid permission escalation attacks
  ubuntu-bug gnome-recipes
  dpkg-query: template gnome-recipes no corresponding package
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  ^C^Z
  [1]+ Stopped ubuntu-bug gnome-recipes

  https://youtu.be/AXtR5m2uqUg
  ---

  1.
  произвёл установку пакета gnome-recipes, попытался отправить отчёт об ошибке 
программы, в ответ получил сообщение:Не удаётся сообщить о неполадке:
  Отчёт относится к пакету , который не был установлен.

  2.
  Ожидал что программа будет идентифицироваться как установленная.

  3.
  sudo apt -f install
  [sudo] пароль для alexandr:
  Чтение списков пакетов… Готово
  Построение дерева зависимостей
  Чтение информации о состоянии… Готово
  обновлено 0, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 
0 пакетов не обновлено.
  sudo gnome-recipes sudo: gnome-recipes: команда не найдена
  sudo apt install gnome-recipes Чтение списков пакетов… Готово
  Построение дерева зависимостей
  Чтение информации о состоянии… Готово
  E: Не удалось найти пакет gnome-recipes

  произвёл установку через software-center

  gnome-recipes
  snap-confine has elevated permissions and is not confined but should be. 
Refusing to continue to avoid permission escalation attacks
  ubuntu-bug gnome-recipes
  dpkg-query: шаблону gnome-recipes не соответствует ни один пакет
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  ^C^Z
  [1]+  Остановлено  ubuntu-bug gnome-recipes

  https://youtu.be/AXtR5m2uqUg

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: software-center (not installed)
  Uname: Linux 4.14.0-041400rc7-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov  2 08:06:48 2017
  InstallationDate: Installed on 2017-10-29 (3 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: software-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1761121] [NEW] Latest intel ucode update halts my system during boot to graphic session

[Maxim Loparev]

Public bug reported:

It seems that this 
iucode_tool -lS /lib/firmware/intel-ucode/
iucode_tool: system has processor(s) with signature 0x000306a9
selected microcodes:
001: sig 0x000306a9, pf mask 0x12, 2018-02-07, rev 0x001f, size 13312
microcode update prevents me to boot to graphic session on any(4.13.0.38[37]) 
kernel.
I can successfully boot to the recovery console.
In some of failed attempts i got "NMI deadlock detected on CPU0,1,3 in mkswap"
I guess nvidia-384 has some issues and conflicts with updated microcode.
I have to disable microcode update with 
IUCODE_TOOL_EXTRA_OPTIONS="--date-after=2018-02-07" to get my unity session 
back.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Это каталог: 
'/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.9)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
BootLog:
 lvmetad is not active yet, using direct activation during sysinit
 /dev/mapper/lmvg-ubunturoot: clean, 421309/1310720 files, 3715643/5242880 
blocks
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Apr  4 12:39:37 2018
DistUpgraded: 2016-04-19 13:48:02,030 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Не удалось выполнить 
процесс-потомок «./xorg_fix_proprietary.py» (No such file or directory) (8))
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation GK107 [GeForce GT 640] [10de:0fc1] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GK107 [GeForce GT 640] [1458:353e]
InstallationDate: Installed on 2012-09-26 (2015 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=/dev/mapper/lmvg-ubunturoot ro nouveau.modeset=0 
rd.driver.blacklist=nouveau video=vesa:off nvidia_drm.modeset=1 zswap.enabled=0 
quiet
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-04-19 (714 days ago)
dmi.bios.date: 10/12/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F1
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61M-DS2 DVI
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.:bvrF1:bd10/12/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-DS2DVI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.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 Apr  4 11:56:19 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.5-0ubuntu2~16.04.1

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


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

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

Title:
  Latest intel ucode update halts my system during boot to graphic
  session

Status in xorg package in Ubuntu:
  New

Bug description:
  It seems that this 
  

[Touch-packages] [Bug 1707136] Re: ryncd does not start when RSYNC_ENABLE is specified

[Launchpad Bug Tracker]

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

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

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

Title:
  ryncd does not start when RSYNC_ENABLE is specified

Status in rsync package in Ubuntu:
  Confirmed
Status in rsync package in Debian:
  Fix Released

Bug description:
  In the good old days, all you needed to ensure rsyncd started upon
  boot was to set RSYNC_ENABLE to true in /etc/default/rsync.

  With the systemd transition, this broke, and you need to manually
  issue

 systemctl enable rsync

  in order for it to be wanted by multi-user.target, which causes it to
  start upon boot.

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

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

[Touch-packages] [Bug 1707136] Re: ryncd does not start when RSYNC_ENABLE is specified

[Mantas Kriaučiūnas]

** Tags added: xenial

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

Title:
  ryncd does not start when RSYNC_ENABLE is specified

Status in rsync package in Ubuntu:
  Confirmed
Status in rsync package in Debian:
  Fix Released

Bug description:
  In the good old days, all you needed to ensure rsyncd started upon
  boot was to set RSYNC_ENABLE to true in /etc/default/rsync.

  With the systemd transition, this broke, and you need to manually
  issue

 systemctl enable rsync

  in order for it to be wanted by multi-user.target, which causes it to
  start upon boot.

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

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