date:20180403

[Expired for xkeyboard-config (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: xkeyboard-config (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Lithuanian keyboard doesn't switch on

Status in xkeyboard-config package in Ubuntu:
  Expired

Bug description:
  Lithuanian keyboard gives no Lithuanian symbols. Using SUPER+SPACE it
  does change language indicator on the upper right corner of the
  desktop, but there's no Lt symbols where they are supposed to be.

  Lt symbols should be on the keyboard's upper number line. The symbol
  map still claims they are there. In matter of fact, when I switch to
  Lt keyboard, it still uses Finnish symbols. Finnish is my main
  keyboard at the moment.

  Before that, there were Russian symbols instead of Lt. So I
  uninstalled Rus keyboard. That caused Lt keyboard to show English
  symbols. After uninstalling Eng, now Lt keyboard is sticking with Fin.
  Adding new languages doesn't change behaviour (still Fi).

  Other languages on keyboard work fine. Uninstalling all keyboards
  except Lt, still makes no Lithuanian symbols.

  I tried uninstall Lithuanian keyboard (with reboot) and install again.
  Also tried different Lithuanian keyboards.

  Ubuntu 14.04.3 LTS 64-bit on MSI GE620DX laptop.

  (That's my first bug report, hope I'm doing it as it's supposed to be
  done.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1490738/+subscriptions

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

[Touch-packages] [Bug 1761044] [NEW] xorg error

2018-04-03 Thread swaroopbigboy

Public bug reported:

when ever the system is recovered from the sleep mod due to inactivity i
get an xorg error msg ...

ProblemType: Bug
DistroRelease: elementary 0.4.1
Package: xorg 1:7.7+13ubuntu3 [origin: Ubuntu]
ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed Apr  4 09:06:22 2018
DistUpgraded: Fresh install
DistroCodename: loki
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:832b]
   Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / R5 
M330] [103c:832b]
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 1bcf:2c9b Sunplus Innovation Technology Inc.
 Bus 001 Device 002: ID 8087:0aa7 Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Laptop 15-bs0xx
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed 
root=UUID=cb67384c-374d-4721-a7b6-d21e48bc769a ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/04/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.21
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 832B
dmi.board.vendor: HP
dmi.board.version: 23.37
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd07/04/2017:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn832B:rvr23.37:cvnHP:ct10:cvrChassisVersion:
dmi.product.name: HP Laptop 15-bs0xx
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 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 08:55:42 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 loki third-party-packages ubuntu

** Attachment added: "screen shot off error msg"
   https://bugs.launchpad.net/bugs/1761044/+attachment/5100673/+files/xorg.png

** Description changed:

- 
- when ever the is recovered from the sleep mod due to inactivity i get an xorg 
error ...
+ when ever the system is recovered from the sleep mod due to inactivity i
+ get an xorg error msg ...
  
  ProblemType: Bug
  DistroRelease: elementary 0.4.1
  Package: xorg 1:7.7+13ubuntu3 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Apr  4 09:06:22 2018
  DistUpgraded: Fresh install
  DistroCodename: loki
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
-Subsystem: Hewlett-Packard Company Device [103c:832b]
-Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / 
R5 M330] [103c:832b]
+  Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
+    Subsystem: Hewlett-Packard Company Device [103c:832b]
+    Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / 
R5 M330] [103c:832b]
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 1bcf:2c9b Sunplus Innovation Technology Inc. 
-  Bus 001 Device 002: ID 8087:0aa7 Intel Corp. 
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 1bcf:2c9b Sunplus Innovation Technology Inc.
+  Bus 001 Device 002: ID 8087:0aa7 Intel Corp.
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Laptop 15-bs0xx
  ProcEnviron:
-

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

This bug was fixed in the package apparmor - 2.12-4ubuntu3

---
apparmor (2.12-4ubuntu3) bionic; urgency=medium

  * Remove old Ubuntu Touch profiles for packages removed from the archive
since they need apparmor-easyprof-ubuntu to compile, and it was also
removed from the archive (LP: #1756800)
- debian/control: Breaks on media-hub, mediascanner2.0 and webbrowser-app
- debian/postinst: on upgrade, remove profiles for usr.bin.webbrowser-app,
  usr.bin.media-hub-server, usr.lib.mediascanner-2.0.mediascanner-extractor
  and usr.bin.mediascanner-service-2.0

 -- Jamie Strandboge   Tue, 03 Apr 2018 13:12:46 +

** Changed in: apparmor (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 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 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

Some more: touching the system cache files doesn't make it work.

Binary diff on the cache files before and after running fc-cache shows
this:

63 c7 c3 5a 00 00 00 00  47 72 ce 15 00 00 00 00
63 c7 c3 5a 00 00 00 00  00 00 00 00 00 00 00 00

Before, at offset 0x38, the "bad" cache files have a non-zero 32 bit
number. The number is different in every "bad" cache file. It is always
zero in the "good" files. This is the only difference. The rest of each
file is identical.

I don't know what this field represents. Need a fontconfig expert to
look at this.

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

Another piece of the puzzle: if you run:

sudo fc-cache -fv

this will rebuild the system font cache in /var/cache/fontconfig

If you then delete the user's cache in ~/.cache/fontconfig and re-log,
there is no delay... and the user's font cache will NOT be rebuilt.

After a delayed login, user's cache and the system cache appear to
contain the same files.

So it looks as if something thinks the system cache is out of date and
wants to rebuild it. Whatever it is only has user permissions, so
rebuilds the font cache in the user's .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 1760934] Re: Sound not working on HP x2 10-p030nl - Realtek rt5640

This sounds like it might be a duplicate of bug 1720519. Please try the
workaround in comment 4 here:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1720519/comments/4

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/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 1499858] Re: bluetoothd[650]: Failed to obtain handles for "Service Changed" characteristic

** Tags added: xenial

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

Title:
  bluetoothd[650]: Failed to obtain handles for "Service Changed"
  characteristic

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Failed to obtain 
handles for "Service Changed" characteristic
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Error adding Link 
Loss service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Current Time Service 
could not be registered
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: gatt-time-server: 
Input/output error (5)
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Sap driver 
initialization failed.
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: sap-server: Operation 
not permitted (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bluez 5.34-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Sep 25 16:37:42 2015
  InstallationDate: Installed on 2015-07-26 (61 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-11-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: bluez
  UdevLog: Error: [Errno 2] No existe el archivo o el directorio: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: C4:85:08:6C:01:0A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:12620731 acl:54193 sco:0 events:799035 errors:0
TX bytes:447934374 acl:1637190 sco:0 commands:1459 errors:0

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

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

[Touch-packages] [Bug 1760366] Re: [regression] Terminal titlebars are too tall

Thanks.

I can see the bug in Wayland sessions now. Just not in Xorg sessions.

** Changed in: ubuntu-themes
   Status: Incomplete => Confirmed

** Changed in: ubuntu-themes (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: ubuntu-themes
   Importance: Undecided => Medium

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Medium

** Summary changed:

- [regression] Terminal titlebars are too tall
+ [regression] Terminal titlebars are too tall (in Wayland sessions and in 
Flashback)

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

Title:
  [regression] Terminal titlebars are too tall (in Wayland sessions and
  in Flashback)

Status in Ubuntu theme:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  It seems like change messed with the padding on the titlebar buttons
  (see attached screenshot):

  https://code.launchpad.net/~3v1n0/ubuntu-themes/windowbuttons-bg-and-
  padding

  Please go back to the way it was before.

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

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

As far as the original bug with delayed login goes... it seems that the
Bluetooth stuff is a red herring.

Since it only happens on first login, I deleted the contents of ~ and
relogged. The delay came back, so I bisected the files until I arrived
at the single file which needs to be deleted in order for the delay to
happen. And that file is:

   ~/.cache/fontconfig/9b89f8e3dae116d678bbf48e5f21f69b-le32d4.cache-7

This cache file is associated with the Noto CJK fonts at:

/usr/share/fonts/opentype/noto

(You can see this by running strings on it.)

Deleting this file while the user is not logged in causes the next login
to take 60 seconds.

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

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

seems related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845058

-- 
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 1706939] Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)"

I don't know about VMs, but it seems to happen on just about every
laptop I put bionic on.

-- 
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:
  Confirmed
Status in gdm3 source package in Bionic:
  Incomplete
Status in systemd source package in Bionic:
  Confirmed

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 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving trig

2018-04-03 Thread Chris Halse Rogers

Hello Stephen, or anyone else affected,

Accepted budgie-artwork into artful-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/budgie-
artwork/0.8.3ubuntu1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: budgie-artwork (Ubuntu Artful)
   Status: Confirmed => Fix Committed

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

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

Title:
  upgrade attempting to process triggers out of order (package plymouth-
  theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed)

Status in apt package in Ubuntu:
  Confirmed
Status in budgie-artwork package in Ubuntu:
  Fix Released
Status in kubuntu-settings package in Ubuntu:
  Fix Released
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  Fix Released
Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in budgie-artwork source package in Xenial:
  Confirmed
Status in kubuntu-settings source package in Xenial:
  Confirmed
Status in plymouth source package in Xenial:
  Fix Released
Status in ubuntu-gnome-default-settings source package in Xenial:
  Confirmed
Status in ubuntu-mate-artwork source package in Xenial:
  Confirmed
Status in apt source package in Artful:
  Confirmed
Status in budgie-artwork source package in Artful:
  Fix Committed
Status in kubuntu-settings source package in Artful:
  Confirmed
Status in plymouth source package in Artful:
  Fix Released
Status in ubuntu-gnome-default-settings source package in Artful:
  Confirmed
Status in ubuntu-mate-artwork source package in Artful:
  Confirmed

Bug description:
  [SRU Justification]
  A package manager bug can cause dist-upgrades from 17.10 to 18.04 to fail 
because of trying to process triggers out of order.  Since the trigger being 
run is that of the currently-installed plymouth package, it is not guaranteed 
to be sufficient to fix the version of the package in 18.04.

  [Test case]
  1. Install plymouth-themes-ubuntu-text from -proposed.
  2. Run a release upgrade with each of update-manager -d, do-release-upgrade 
-d, and apt-get dist-upgrade (the last after manually changing sources.list).
  3. Verify that in each case, the upgrade completes successfully, with no 
errors about out-of-order trigger configuration.

  [Regression potential]
  noawait triggers have been supported in dpkg since 1.16.1, which is older 
than the version in precise 
(https://manpages.debian.org/jessie/dpkg-dev/deb-triggers.5.en.html).  A 
noawait trigger is considered appropriate whenever the triggered package does 
not need to block the triggering package.  There is no reason for a plymouth 
theme package to need to block configuration of an essential package in this 
case.  noawait triggers are well-exercised in the distro now, so the risk of 
regression from this change should be low.

  There is unfortunately not a known reproducer for the original bug, so
  the test case, while it should guard against regressions, is not
  strong confirmation that the bug is fixed.

  [Original description]
  Failure during upgrade attempt from Xubuntu 17.10 to Xubuntu 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu17
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sun Feb 18 23:41:49 2018
  DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-10-24 (118 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp.

[Touch-packages] [Bug 1759329] Re: bionic netboot installer fails with local repository

2018-04-03 Thread Jay McCanta

Close this.  Bug 1761030 has more detailed information.

** Changed in: console-setup (Ubuntu)
   Status: New => Incomplete

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

Title:
  bionic netboot installer fails with local repository

Status in console-setup package in Ubuntu:
  Incomplete

Bug description:
  preseed file with local repositoryw fails when package from repo is
  trying to be installed.

  Bionic preseed file with:
  d-i apt-setup/local0/repository string deb 
http://example.com/PatchSet/latest/willu bionic main
  d-i apt-setup/local0/comment string This is the stuff
  d-i apt-setup/local0/key string 
http://dists.example.com/PatchSet/latest/f5-ubuntu/willu.pubkey

  This paragraph works in Precise, Trusty, and Xenial.

  Watching /target/etc/apt/source.lists, I see it's created correctly,
  then at some point after the base install, the file gets overwritten
  and the entry for the local repo(s) are commented out.

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

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

$ diff -u <(grep etc/apparmor.d Contents-xenial | awk '{print $1}') <(grep 
etc/apparmor.d Contents-bionic | awk '{print $1}')
--- /dev/fd/63  2018-04-03 17:45:57.438698038 -0700
+++ /dev/fd/62  2018-04-03 17:45:57.438698038 -0700
@@ -23,16 +23,19 @@
 etc/apparmor.d/abstractions/enchant
 etc/apparmor.d/abstractions/evince
 etc/apparmor.d/abstractions/fcitx
+etc/apparmor.d/abstractions/fcitx-strict
 etc/apparmor.d/abstractions/fonts
 etc/apparmor.d/abstractions/freedesktop.org
 etc/apparmor.d/abstractions/gnome
 etc/apparmor.d/abstractions/gnupg
 etc/apparmor.d/abstractions/gstreamer
+etc/apparmor.d/abstractions/i2p
 etc/apparmor.d/abstractions/ibus
 etc/apparmor.d/abstractions/kde
 etc/apparmor.d/abstractions/kerberosclient
 etc/apparmor.d/abstractions/launchpad-integration
 etc/apparmor.d/abstractions/ldapclient
+etc/apparmor.d/abstractions/libpam-systemd
 etc/apparmor.d/abstractions/libvirt-lxc
 etc/apparmor.d/abstractions/libvirt-qemu
 etc/apparmor.d/abstractions/lightdm
@@ -42,7 +45,8 @@
 etc/apparmor.d/abstractions/lxc/start-container
 etc/apparmor.d/abstractions/mdns
 etc/apparmor.d/abstractions/mir
-etc/apparmor.d/abstractions/mozc_server
+etc/apparmor.d/abstractions/mozc
+etc/apparmor.d/abstractions/mozc-server
 etc/apparmor.d/abstractions/mysql
 etc/apparmor.d/abstractions/nameservice
 etc/apparmor.d/abstractions/nis
@@ -51,6 +55,7 @@
 etc/apparmor.d/abstractions/orbit2
 etc/apparmor.d/abstractions/p11-kit
 etc/apparmor.d/abstractions/perl
+etc/apparmor.d/abstractions/php
 etc/apparmor.d/abstractions/php5
 etc/apparmor.d/abstractions/postfix-common
 etc/apparmor.d/abstractions/private-files
@@ -94,23 +99,25 @@
 etc/apparmor.d/abstractions/user-tmp
 etc/apparmor.d/abstractions/user-write
 etc/apparmor.d/abstractions/video
+etc/apparmor.d/abstractions/wayland
 etc/apparmor.d/abstractions/web-data
 etc/apparmor.d/abstractions/winbind
 etc/apparmor.d/abstractions/wutmp
 etc/apparmor.d/abstractions/xad
 etc/apparmor.d/abstractions/xdg-desktop
+etc/apparmor.d/apache2.d/kopano-webapp
 etc/apparmor.d/apache2.d/phpsysinfo
 etc/apparmor.d/bin.ping
-etc/apparmor.d/content-hub-testability
 etc/apparmor.d/dhcpd.d/maas
+etc/apparmor.d/firejail-default
 etc/apparmor.d/gst_plugin_scanner
 etc/apparmor.d/libvirt/TEMPLATE.lxc
 etc/apparmor.d/libvirt/TEMPLATE.qemu
 etc/apparmor.d/lightdm-guest-session
+etc/apparmor.d/lightdm-remote-session-x2go
 etc/apparmor.d/local/README
+etc/apparmor.d/local/firejail-local
 etc/apparmor.d/local/usr.sbin.apache2
-etc/apparmor.d/local/usr.sbin.libvirtd
-etc/apparmor.d/local/usr.sbin.named
 etc/apparmor.d/lxc-containers
 etc/apparmor.d/lxc/lxc-default
 etc/apparmor.d/lxc/lxc-default-cgns
@@ -118,40 +125,43 @@
 etc/apparmor.d/lxc/lxc-default-with-nesting
 etc/apparmor.d/sbin.aprx
 etc/apparmor.d/sbin.dhclient
+etc/apparmor.d/sbin.dhcpcanon
 etc/apparmor.d/sbin.klogd
 etc/apparmor.d/sbin.syslog-ng
 etc/apparmor.d/sbin.syslogd
+etc/apparmor.d/system_i2p
 etc/apparmor.d/system_tor
 etc/apparmor.d/tunables/alias
 etc/apparmor.d/tunables/apparmorfs
 etc/apparmor.d/tunables/dovecot
 etc/apparmor.d/tunables/global
 etc/apparmor.d/tunables/home
+etc/apparmor.d/tunables/home.d/site.local
 etc/apparmor.d/tunables/kernelvars
 etc/apparmor.d/tunables/multiarch
+etc/apparmor.d/tunables/multiarch.d/site.local
 etc/apparmor.d/tunables/ntpd
 etc/apparmor.d/tunables/proc
 etc/apparmor.d/tunables/securityfs
 etc/apparmor.d/tunables/sys
 etc/apparmor.d/tunables/xdg-user-dirs
+etc/apparmor.d/url-dispatcher-bad-url-helper
 etc/apparmor.d/usr.bin.chromium-browser
 etc/apparmor.d/usr.bin.evince
 etc/apparmor.d/usr.bin.firefox
 etc/apparmor.d/usr.bin.freshclam
+etc/apparmor.d/usr.bin.i2prouter
 etc/apparmor.d/usr.bin.irssi
 etc/apparmor.d/usr.bin.lxc-start
-etc/apparmor.d/usr.bin.media-hub-server
-etc/apparmor.d/usr.bin.mediascanner-service-2.0
-etc/apparmor.d/usr.bin.messaging-app
-etc/apparmor.d/usr.bin.obfsproxy
+etc/apparmor.d/usr.bin.man
+etc/apparmor.d/usr.bin.onioncircuits
 etc/apparmor.d/usr.bin.pidgin
 etc/apparmor.d/usr.bin.pollen
 etc/apparmor.d/usr.bin.quasselcore
-etc/apparmor.d/usr.bin.tlsdate
+etc/apparmor.d/usr.bin.ricochet
+etc/apparmor.d/usr.bin.surf
 etc/apparmor.d/usr.bin.totem
 etc/apparmor.d/usr.bin.totem-previewers
-etc/apparmor.d/usr.bin.ubuntu-core-launcher
-etc/apparmor.d/usr.bin.webbrowser-app
 etc/apparmor.d/usr.lib.dovecot.anvil
 etc/apparmor.d/usr.lib.dovecot.auth
 etc/apparmor.d/usr.lib.dovecot.config
@@ -168,18 +178,27 @@
 etc/apparmor.d/usr.lib.dovecot.pop3
 etc/apparmor.d/usr.lib.dovecot.pop3-login
 etc/apparmor.d/usr.lib.dovecot.ssl-params
+etc/apparmor.d/usr.lib.ioquake3.ioq3ded
+etc/apparmor.d/usr.lib.ioquake3.ioquake3
 etc/apparmor.d/usr.lib.ipsec.charon
 etc/apparmor.d/usr.lib.ipsec.lookip
 etc/apparmor.d/usr.lib.ipsec.stroke
+etc/apparmor.d/usr.lib.libreoffice.program.oosplash
+etc/apparmor.d/usr.lib.libreoffice.program.senddoc
+etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin
+etc/apparmor.d/usr.lib.libreoffice.program.xpdfimport

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

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

Thanks

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

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

Status in apparmor package in Ubuntu:
  Fix Committed
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 1756800] Re: Failed to start AppArmor initialization with status=123/n/a

** Changed in: apparmor (Ubuntu)
   Importance: Undecided => Medium

-- 
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 Committed
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 1761020] Re: AppArmor parser error for /etc/apparmor.d/usr.bin.webbrowser-app in /etc/apparmor.d/usr.bin.webbrowser-app at line 26: Could not open '/usr/share/apparmor/hardware/g

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

** This bug has been marked a duplicate of bug 1756800
   Failed to start AppArmor initialization with status=123/n/a

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

Title:
  AppArmor parser error for /etc/apparmor.d/usr.bin.webbrowser-app in
  /etc/apparmor.d/usr.bin.webbrowser-app at line 26: Could not open
  '/usr/share/apparmor/hardware/graphics.d'

Status in apparmor package in Ubuntu:
  New

Bug description:
  After upgrading to Ubuntu 18.04, the apparmor service is failed on
  boot because of unresolvable references from /etc/apparmor.d/usr.bin
  .webbrowser-app, from the removed (but not purged) webbrowser-app
  package.

  The package itself was removed from my system as part of the upgrade
  to 17.10, but the presence of the obsolete conffile did not cause
  problems until upgrading to bionic.

  I think the apparmor package needs to take care to clean up after
  these abandoned conffiles on upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apparmor 2.12-4ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  3 16:34:52 2018
  InstallationDate: Installed on 2010-09-24 (2748 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  KernLog:
   
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: Upgraded to bionic on 2018-03-21 (13 days ago)

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

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

[Touch-packages] [Bug 1761020] [NEW] AppArmor parser error for /etc/apparmor.d/usr.bin.webbrowser-app in /etc/apparmor.d/usr.bin.webbrowser-app at line 26: Could not open '/usr/share/apparmor/hardware

Public bug reported:

After upgrading to Ubuntu 18.04, the apparmor service is failed on boot
because of unresolvable references from /etc/apparmor.d/usr.bin
.webbrowser-app, from the removed (but not purged) webbrowser-app
package.

The package itself was removed from my system as part of the upgrade to
17.10, but the presence of the obsolete conffile did not cause problems
until upgrading to bionic.

I think the apparmor package needs to take care to clean up after these
abandoned conffiles on upgrade.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apparmor 2.12-4ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  3 16:34:52 2018
InstallationDate: Installed on 2010-09-24 (2748 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
KernLog:
 
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1
SourcePackage: apparmor
Syslog:
 
UpgradeStatus: Upgraded to bionic on 2018-03-21 (13 days ago)

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


** Tags: amd64 apport-bug bionic

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

Title:
  AppArmor parser error for /etc/apparmor.d/usr.bin.webbrowser-app in
  /etc/apparmor.d/usr.bin.webbrowser-app at line 26: Could not open
  '/usr/share/apparmor/hardware/graphics.d'

Status in apparmor package in Ubuntu:
  New

Bug description:
  After upgrading to Ubuntu 18.04, the apparmor service is failed on
  boot because of unresolvable references from /etc/apparmor.d/usr.bin
  .webbrowser-app, from the removed (but not purged) webbrowser-app
  package.

  The package itself was removed from my system as part of the upgrade
  to 17.10, but the presence of the obsolete conffile did not cause
  problems until upgrading to bionic.

  I think the apparmor package needs to take care to clean up after
  these abandoned conffiles on upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apparmor 2.12-4ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  3 16:34:52 2018
  InstallationDate: Installed on 2010-09-24 (2748 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  KernLog:
   
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: Upgraded to bionic on 2018-03-21 (13 days ago)

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

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

2018-04-03 Thread Jimmy Olsen

Just tried to add another PPA (from another program), same error going
on. and  I get it fixed when PPA is removed...

-- 
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 1760979] Re: apt-get dist-upgrade failed

I'm glad it's not a catastrophe due to a regression in this specific
update, but it's unfortunate that it looks like it will take a lot of
work to reliably resolve.

Thanks

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

Title:
  apt-get dist-upgrade failed

Status in apt package in Ubuntu:
  Triaged
Status in dpkg package in Ubuntu:
  Triaged

Bug description:
  Hello, something went amiss with a recent apt-get -u dist-upgrade:

  root@wopr:~# apt-get update && apt-get -u dist-upgrade
  Get:1 file:/srv/mirror/ubuntu xenial InRelease [247 kB]
  Get:1 file:/srv/mirror/ubuntu xenial InRelease [247 kB]
  Get:2 file:/srv/mirror/ubuntu xenial-updates InRelease [102 kB]   
   
  Get:2 file:/srv/mirror/ubuntu xenial-updates InRelease [102 kB]   

  Get:3 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
  
  Get:4 file:/srv/mirror/ubuntu xenial-updates/main Sources [302 kB]
 
  Get:5 file:/srv/mirror/ubuntu xenial-updates/universe Sources [199 kB]
  Get:6 file:/srv/mirror/ubuntu xenial-updates/main amd64 Packages [746 kB]
  Get:7 file:/srv/mirror/ubuntu xenial-updates/main i386 Packages [691 kB]
  Get:8 file:/srv/mirror/ubuntu xenial-updates/main Translation-en [309 kB]
  Get:9 file:/srv/mirror/ubuntu xenial-updates/universe amd64 Packages [616 kB]
  Get:10 file:/srv/mirror/ubuntu xenial-updates/universe i386 Packages [570 kB]
  Get:11 file:/srv/mirror/ubuntu xenial-updates/universe Translation-en [248 kB]
  Get:12 http://security.ubuntu.com/ubuntu xenial-security/main Sources [119 kB]
  Get:13 http://security.ubuntu.com/ubuntu xenial-security/universe Sources 
[62.4 kB]
  Get:14 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 
[467 kB]
  Get:15 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages 
[421 kB]
  Get:16 http://security.ubuntu.com/ubuntu xenial-security/main Translation-en 
[201 kB]
  Get:17 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages [340 kB]
  Get:18 http://security.ubuntu.com/ubuntu xenial-security/universe i386 
Packages [296 kB]
  Get:19 http://security.ubuntu.com/ubuntu xenial-security/universe 
Translation-en [126 kB]
  Fetched 2,135 kB in 1s (1,520 kB/s)  
  Reading package lists... Done
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following packages were automatically installed and are no longer 
required:
libzstd0 linux-headers-4.4.0-109 linux-headers-4.4.0-109-generic 
linux-image-4.4.0-109-generic
linux-image-extra-4.4.0-109-generic linux-signed-image-4.4.0-109-generic 
linux-tools-4.4.0-109
linux-tools-4.4.0-109-generic
  Use 'sudo apt autoremove' to remove them.
  The following packages will be upgraded:
apt apt-transport-https apt-utils initramfs-tools initramfs-tools-bin 
initramfs-tools-core libapt-inst2.0
libapt-pkg5.0 libpam-systemd libpci-dev libpci3 libsystemd0 libudev-dev 
libudev1 lshw makedumpfile pciutils
python-crypto systemd systemd-sysv udev
  21 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Need to get 246 kB/8,157 kB of archives.
  After this operation, 16.4 kB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  Get:1 file:/srv/mirror/ubuntu xenial-updates/main amd64 libapt-pkg5.0 amd64 
1.2.26 [706 kB]
  Get:2 file:/srv/mirror/ubuntu xenial-updates/main amd64 libapt-inst2.0 amd64 
1.2.26 [55.4 kB]
  Get:3 file:/srv/mirror/ubuntu xenial-updates/main amd64 apt amd64 1.2.26 
[1,043 kB]
  Get:4 file:/srv/mirror/ubuntu xenial-updates/main amd64 apt-utils amd64 
1.2.26 [197 kB]
  Get:5 file:/srv/mirror/ubuntu xenial-updates/main amd64 libudev-dev amd64 
229-4ubuntu21.2 [150 kB]
  Get:6 file:/srv/mirror/ubuntu xenial-updates/main amd64 libsystemd0 amd64 
229-4ubuntu21.2 [205 kB]
  Get:7 file:/srv/mirror/ubuntu xenial-updates/main amd64 libpam-systemd amd64 
229-4ubuntu21.2 [115 kB]
  Get:8 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
python-crypto amd64 2.6.1-6ubuntu0.16.04.3 [246 kB]
  Get:9 file:/srv/mirror/ubuntu xenial-updates/main amd64 systemd amd64 
229-4ubuntu21.2 [3,634 kB]
  Get:10 file:/srv/mirror/ubuntu xenial-updates/main amd64 udev amd64 
229-4ubuntu21.2 [993 kB]
  Get:11 file:/srv/mirror/ubuntu xenial-updates/main amd64 libudev1 amd64 
229-4ubuntu21.2 [54.4 kB]
  Get:12 file:/srv/mirror/ubuntu xenial-updates/main amd64 initramfs-tools all 
0.122ubuntu8.11 [8,590 B]
  Get:13 file:/srv/mirror/ubuntu xenial-updates/main amd64 initramfs-tools-core 
all 0.122ubuntu8.11 [42.9 kB]
  Get:14 file:/srv/mirror/ubuntu xenial-updates/main amd64 initramfs-tools-bin 
amd64 0.122ubuntu8.11 [9,592 B]
  Get:15 file:/srv/mirror/ubuntu xenial-updates/main amd64 systemd-sysv amd64

[Touch-packages] [Bug 1499858] Re: bluetoothd[650]: Failed to obtain handles for "Service Changed" characteristic

2018-04-03 Thread gaetano1984

the solution below to my conf doesn't work. keep needing help :**(


I temporary fixed it doing this: stop bluetooth, kill bluetoothd and obexd, 
start bluetooth:

$ sudo systemctl stop bluetooth
$ sudo killall -TERM bluetoothd
$ sudo killall -TERM obexd
$ sudo systemctl start bluetooth

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

Title:
  bluetoothd[650]: Failed to obtain handles for "Service Changed"
  characteristic

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Failed to obtain 
handles for "Service Changed" characteristic
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Error adding Link 
Loss service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Current Time Service 
could not be registered
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: gatt-time-server: 
Input/output error (5)
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Sap driver 
initialization failed.
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: sap-server: Operation 
not permitted (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bluez 5.34-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Sep 25 16:37:42 2015
  InstallationDate: Installed on 2015-07-26 (61 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-11-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: bluez
  UdevLog: Error: [Errno 2] No existe el archivo o el directorio: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: C4:85:08:6C:01:0A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:12620731 acl:54193 sco:0 events:799035 errors:0
TX bytes:447934374 acl:1637190 sco:0 commands:1459 errors:0

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

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

2018-04-03 Thread Jimmy Olsen

Hi Chistian. I tried to add the PPA and it shows me that error:

marcos@marcos:~$ sudo add-apt-repository ppa:otto-kesselgulasch/gimp -y && sudo 
apt-get update
[sudo] password for marcos: 
gpg: keybox '/tmp/tmp935_1y_p/pubring.gpg' created
gpg: key 3BDAAC08614C4B38: 1 signature not checked due to a missing key
gpg: /tmp/tmp935_1y_p/trustdb.gpg: trustdb created
gpg: key 3BDAAC08614C4B38: public key "Launchpad otto06217" imported
gpg: no ultimately trusted keys found
gpg: Total number processed: 1
gpg:   imported: 1
OK
Hit:1 http://linux.teamviewer.com/deb stable InRelease
Hit:2 http://linux.teamviewer.com/deb preview InRelease
Hit:3 http://br.archive.ubuntu.com/ubuntu bionic 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://security.ubuntu.com/ubuntu bionic-security InRelease  
Get:8 http://ppa.launchpad.net/otto-kesselgulasch/gimp/ubuntu bionic InRelease 
[15,4 kB]
Hit:9 http://ppa.launchpad.net/ubuntubudgie/backports/ubuntu bionic InRelease
Get:10 http://ppa.launchpad.net/otto-kesselgulasch/gimp/ubuntu bionic/main 
amd64 Packages [3.096 B]
83% [10 Packages store 0 B] [Connecting to ppa.launchpad.net (91.189.95.83)]
  Seccomp prevented execution of syscall 41 on architecture amd64 

Reading package lists... Done   
E: Method store has died unexpectedly!
E: Sub-process store returned an error code (31)
marcos@marcos:~$ 

As said before, once PPA is removed,it goes back to normal.

Assuming it could be something from my computer settings, I send
attached info sys about it. Hope it helps bug be fixed.

** Attachment added: "system info from my computer as from 03th April 2018"
   
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1732030/+attachment/5100499/+files/hardinfo_report.html

-- 
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 1760992] Re: systemd-journald crashed with SIGABRT in GI_pthread_timedjoin_ex()

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in systemd package in Ubuntu:
  New

Bug description:
  I haven't a clue who what where why but its' nice to be included. I
  wanna give a shout out to my homies Stryfer for his awesome gaming
  abilities. My homeboy Tuko for his spiritual guidance and myself, I'd
  like to say thank you Ubuntu for all that you are and do! Pew, pew!

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.392
  Date: Mon Apr  2 18:46:46 2018
  ExecutablePath: /lib/systemd/systemd-journald
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325)
  MachineType: MSI MS-7903
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: file=/preseed/hostname.seed noprompt persistent 
boot=casper 
iso-scan/filename=/multiboot/hostname-bionic-desktop-amd64/hostname-bionic-desktop-amd64.iso
 quiet --
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __GI___pthread_timedjoin_ex (threadid=140009756866304, thread_return=0x0, 
abstime=0x0, block=) at pthread_join_common.c:89
   ?? () from /lib/systemd/libsystemd-shared-237.so
   ?? () from /lib/systemd/libsystemd-shared-237.so
   journal_file_append_object () from /lib/systemd/libsystemd-shared-237.so
   ?? () from /lib/systemd/libsystemd-shared-237.so
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  Title: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 08/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.8
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM GAMING (MS-7903)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.8:bd08/18/2016:svnMSI:pnMS-7903:pvr1.0:rvnMSI:rnA88XMGAMING(MS-7903):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7903
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Touch-packages] [Bug 1760995] [NEW] package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: Unterprozess neues pre-removal-Skript gab den Fehlerwert 1 zurück

2018-04-03 Thread Scheuerer Severin

Public bug reported:

nothing

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Tue Apr  3 23:06:44 2018
ErrorMessage: Unterprozess neues pre-removal-Skript gab den Fehlerwert 1 zurück
InstallationDate: Installed on 2018-04-03 (0 days ago)
InstallationMedia: Ubuntu-MATE 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: avahi
Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: Unterprozess neues pre-removal-Skript gab den Fehlerwert 1 
zurück
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: avahi (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 avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1760995

Title:
  package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to
  install/upgrade: Unterprozess neues pre-removal-Skript gab den
  Fehlerwert 1 zurück

Status in avahi package in Ubuntu:
  New

Bug description:
  nothing

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Tue Apr  3 23:06:44 2018
  ErrorMessage: Unterprozess neues pre-removal-Skript gab den Fehlerwert 1 
zurück
  InstallationDate: Installed on 2018-04-03 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: Unterprozess neues pre-removal-Skript gab den Fehlerwert 1 
zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

2018-04-03 Thread TJ

This is a command-line that is useful for manually exercising the
org.bluez DBus activiation. It might reproduce the timeout or otherwise
give useful clues. Command should be all on one line (ignore Launchpad
line wrapping):

dbus-send --system --print-reply --dest=org.bluez /
org.freedesktop.DBus.ObjectManager.GetManagedObjects

I won't reproduce the entire output here but this is the initial part
when a BT hci device is available:

method return time=1522790434.404190 sender=:1.2 -> destination=:1.399 
serial=821 reply_serial=2
   array [
  dict entry(
 object path "/org/bluez"
 array [
dict entry(
   string "org.freedesktop.DBus.Introspectable"
   array [
   ]
)
dict entry(
   string "org.bluez.AgentManager1"
   array [
   ]
)
dict entry(
   string "org.bluez.ProfileManager1"
   array [
   ]
)
 ]
  )
  dict entry(
 object path "/org/bluez/hci0"

-- 
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 1504659] Re: Duplicate line for path "/var/log" warning is shown when rsyslog is installed

2018-04-03 Thread Malachi de AElfweald

They are being ignored (apparently incorrectly) in 18.04

Apr 03 13:17:58 odin systemd-tmpfiles[1033]: [/usr/lib/tmpfiles.d/var.conf:14] 
Duplicate line for path "/var/log", ignoring.
Apr 03 13:32:59 odin systemd[1]: systemd-tmpfiles-clean.service: Main process 
exited, code=dumped, status=11/SEGV
Apr 03 13:32:59 odin systemd[1]: systemd-tmpfiles-clean.service: Failed with 
result 'core-dump'.

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

Title:
  Duplicate line for path "/var/log" warning is shown when rsyslog is
  installed

Status in systemd package in Ubuntu:
  Opinion

Bug description:
  On an snappy 15.04 stable system I see in the logs:
  systemd-tmpfiles[958]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for 
path "/var/log", ignoring.

  Bug 1434295 mentions this, but reports that systemd fails to start.
  This bug is about preventing systemd from displaying this in the logs.
  Looking at the snappy system, I'm not sure why it is doing that:

  $ cat /usr/lib/tmpfiles.d/var.conf
  #  This file is part of systemd.
  #
  #  systemd is free software; you can redistribute it and/or modify it
  #  under the terms of the GNU Lesser General Public License as published by
  #  the Free Software Foundation; either version 2.1 of the License, or
  #  (at your option) any later version.

  # See tmpfiles.d(5) for details

  d /var 0755 - - -

  L /var/run - - - - ../run

  d /var/log 0755 - - -
  f /var/log/wtmp 0664 root utmp -
  f /var/log/btmp 0600 root utmp -

  d /var/cache 0755 - - -

  d /var/lib 0755 - - -
  v /var/lib/machines 0700 - - -

  d /var/spool 0755 - - -

  Perhaps this is a bug in systemd?

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

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

[Touch-packages] [Bug 1484027] Re: systemd-tmpfiles-clean warns about duplicate /var/log line

2018-04-03 Thread Malachi de AElfweald

I'm not sure about the fix.  This is in 18.04

Apr 03 13:17:58 odin systemd-tmpfiles[1033]: [/usr/lib/tmpfiles.d/var.conf:14] 
Duplicate line for path "/var/log", ignoring.
Apr 03 13:32:59 odin systemd[1]: systemd-tmpfiles-clean.service: Main process 
exited, code=dumped, status=11/SEGV
Apr 03 13:32:59 odin systemd[1]: systemd-tmpfiles-clean.service: Failed with 
result 'core-dump'.

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

Title:
  systemd-tmpfiles-clean warns about duplicate /var/log line

Status in rsyslog package in Ubuntu:
  Fix Released

Bug description:
  Triggered by the two /var/log entries that were reported in
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1434295, I get
  daily log messages from systemd-tmpfiles-clean saying:

  Aug 10 15:04:13 seraph systemd[1]: Starting Cleanup of Temporary 
Directories...
  Aug 10 15:04:13 seraph systemd-tmpfiles[5897]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
  Aug 10 15:04:13 seraph systemd[1]: Started Cleanup of Temporary Directories.

  I don't know much about systemd, so I have no ideas for how to fix it,
  sorry.

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

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

2018-04-03 Thread TJ

The Dbus bluze system config doesn't run, it has "Exec=/bin/false" --
/usr/share/dbus-1/system-services/org.bluez.service It's left to systemd
to activate it via /lib/systemd/system/bluetooth.service

[Unit]
Description=Bluetooth service
Documentation=man:bluetoothd(8)
ConditionPathIsDirectory=/sys/class/bluetooth

[Service]
Type=dbus
BusName=org.bluez
ExecStart=/usr/lib/bluetooth/bluetoothd
NotifyAccess=main
#WatchdogSec=10
#Restart=on-failure
CapabilityBoundingSet=CAP_NET_ADMIN CAP_NET_BIND_SERVICE
LimitNPROC=1
ProtectHome=true
ProtectSystem=full

[Install]
WantedBy=bluetooth.target
Alias=dbus-org.bluez.service

I would suspect if there are no BT hci devices then bluetooth.service
won't run.

So the question is, are the other flavours doing something to allow a
'dummy' BT device so bluetooth service runs and org.bluez is available
or is it that their Bluetooth tooling isn't calling the DBus interface
at all (using libbluetooth directly maybe) ?

-- 
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 1760979] Re: apt-get dist-upgrade failed

2018-04-03 Thread Julian Andres Klode

Well, yes, that happens sometimes. There is a race, because apt needs to
release the dpkg lock before starting dpkg. Guess I should poke guillem
about https://lists.debian.org/debian-dpkg/2017/01/msg00044.html again.

** Changed in: apt (Ubuntu)
   Importance: Undecided => Medium

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

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

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

** Changed in: dpkg (Ubuntu)
   Importance: Undecided => Medium

** Changed in: apt (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

** Changed in: dpkg (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

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

Title:
  apt-get dist-upgrade failed

Status in apt package in Ubuntu:
  Triaged
Status in dpkg package in Ubuntu:
  Triaged

Bug description:
  Hello, something went amiss with a recent apt-get -u dist-upgrade:

  root@wopr:~# apt-get update && apt-get -u dist-upgrade
  Get:1 file:/srv/mirror/ubuntu xenial InRelease [247 kB]
  Get:1 file:/srv/mirror/ubuntu xenial InRelease [247 kB]
  Get:2 file:/srv/mirror/ubuntu xenial-updates InRelease [102 kB]   
   
  Get:2 file:/srv/mirror/ubuntu xenial-updates InRelease [102 kB]   

  Get:3 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
  
  Get:4 file:/srv/mirror/ubuntu xenial-updates/main Sources [302 kB]
 
  Get:5 file:/srv/mirror/ubuntu xenial-updates/universe Sources [199 kB]
  Get:6 file:/srv/mirror/ubuntu xenial-updates/main amd64 Packages [746 kB]
  Get:7 file:/srv/mirror/ubuntu xenial-updates/main i386 Packages [691 kB]
  Get:8 file:/srv/mirror/ubuntu xenial-updates/main Translation-en [309 kB]
  Get:9 file:/srv/mirror/ubuntu xenial-updates/universe amd64 Packages [616 kB]
  Get:10 file:/srv/mirror/ubuntu xenial-updates/universe i386 Packages [570 kB]
  Get:11 file:/srv/mirror/ubuntu xenial-updates/universe Translation-en [248 kB]
  Get:12 http://security.ubuntu.com/ubuntu xenial-security/main Sources [119 kB]
  Get:13 http://security.ubuntu.com/ubuntu xenial-security/universe Sources 
[62.4 kB]
  Get:14 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 
[467 kB]
  Get:15 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages 
[421 kB]
  Get:16 http://security.ubuntu.com/ubuntu xenial-security/main Translation-en 
[201 kB]
  Get:17 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages [340 kB]
  Get:18 http://security.ubuntu.com/ubuntu xenial-security/universe i386 
Packages [296 kB]
  Get:19 http://security.ubuntu.com/ubuntu xenial-security/universe 
Translation-en [126 kB]
  Fetched 2,135 kB in 1s (1,520 kB/s)  
  Reading package lists... Done
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following packages were automatically installed and are no longer 
required:
libzstd0 linux-headers-4.4.0-109 linux-headers-4.4.0-109-generic 
linux-image-4.4.0-109-generic
linux-image-extra-4.4.0-109-generic linux-signed-image-4.4.0-109-generic 
linux-tools-4.4.0-109
linux-tools-4.4.0-109-generic
  Use 'sudo apt autoremove' to remove them.
  The following packages will be upgraded:
apt apt-transport-https apt-utils initramfs-tools initramfs-tools-bin 
initramfs-tools-core libapt-inst2.0
libapt-pkg5.0 libpam-systemd libpci-dev libpci3 libsystemd0 libudev-dev 
libudev1 lshw makedumpfile pciutils
python-crypto systemd systemd-sysv udev
  21 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Need to get 246 kB/8,157 kB of archives.
  After this operation, 16.4 kB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  Get:1 file:/srv/mirror/ubuntu xenial-updates/main amd64 libapt-pkg5.0 amd64 
1.2.26 [706 kB]
  Get:2 file:/srv/mirror/ubuntu xenial-updates/main amd64 libapt-inst2.0 amd64 
1.2.26 [55.4 kB]
  Get:3 file:/srv/mirror/ubuntu xenial-updates/main amd64 apt amd64 1.2.26 
[1,043 kB]
  Get:4 file:/srv/mirror/ubuntu xenial-updates/main amd64 apt-utils amd64 
1.2.26 [197 kB]
  Get:5 file:/srv/mirror/ubuntu xenial-updates/main amd64 libudev-dev amd64 
229-4ubuntu21.2 [150 kB]
  Get:6 file:/srv/mirror/ubuntu xenial-updates/main amd64 libsystemd0 amd64 
229-4ubuntu21.2 [205 kB]
  Get:7 file:/srv/mirror/ubuntu xenial-updates/main amd64 libpam-systemd amd64 
229-4ubuntu21.2 [115 kB]
  Get:8 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
python-crypto amd64 2.6.1-6ubuntu0.16.04.3 [246 kB]
  Get:9 file:/srv/mirror/ubuntu xenial-updates/main amd64 systemd amd64 
229-4ubuntu21.2 [3,634 kB]
  Get:10 file:/srv/mirror/ubuntu xenial-updates/main amd64 udev

[Touch-packages] [Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

2018-04-03 Thread Balint Reczey

@jarnos Verification is needed only for update-manager for now, thus I
think you verified that the fix worked for Xenial. Could you please
change the tag to reflect that or you would like to wait for the u-u
fix, - which may come later?

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

Status in apt package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in update-manager source package in Xenial:
  Fix Committed
Status in apt source package in Artful:
  Confirmed
Status in gnome-software source package in Artful:
  Invalid
Status in unattended-upgrades source package in Artful:
  In Progress
Status in update-manager source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.

  [Test Case]

   1. Install kernel packages to be removed, mark them auto-installed
  and run apt's kernel hook script to make apt consider them
  autoremovable:

    sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo /etc/kernel/postinst.d/apt-auto-removal

   2. Also downgrade a package to be upgraded:

     sudo apt-get install -y --allow-downgrades ca-
  certificates=20160104ubuntu1

   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.

    sudo update-manager

   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.

   3. (unattended-upgrades, the fix comes in an update of u-u) Run
  unattended-upgrades manually and observe the removal of the
  autoremovable kernel packages:

    sudo unattended-upgrade -v

  [Regression Potential]

   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.

  [Other Info]

  The unattended-upgrades fix is uploaded with many other fixes and
  those may cause regressions in other areas in unattended-upgrades.

  [Original bug text]

  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.

  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.

  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1760977] Re: evolution-calendar-factory-subprocess crashed with SIGSEGV in g_main_context_ref()

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

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 #1744818, 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/1760977/+attachment/5100292/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

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

Bug description:
  This crashed in the background.  I do not know additional details
  other than what is included in the automatic report.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: evolution-data-server 3.28.0-2ubuntu2
  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
  CurrentDesktop: MATE
  Date: Tue Apr  3 14:45:01 2018
  ExecutablePath: /usr/lib/evolution/evolution-calendar-factory-subprocess
  InstallationDate: Installed on 2018-02-22 (40 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180221)
  ProcCmdline: /usr/lib/evolution/evolution-calendar-factory-subprocess 
--factory all --bus-name 
org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx2636x2 --own-path 
/org/gnome/evolution/dataserver/Subprocess/Backend/Calendar/2636/2
  ProcEnviron:
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7fadad17d767 :lock 
addl $0x1,(%rdx)
   PC (0x7fadad17d767) ok
   source "$0x1" ok
   destination "(%rdx)" (0x7fadac0ef978) in non-writable VMA region: 
0x7fadac057000-0x7fadac124000 r-xp 
/usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1.8.0
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing VMA /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1.8.0
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   g_main_context_ref () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   soup_socket_new () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1
  Title: evolution-calendar-factory-subprocess crashed with SIGSEGV in 
g_main_context_ref()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1760979] [NEW] apt-get dist-upgrade failed

Public bug reported:

Hello, something went amiss with a recent apt-get -u dist-upgrade:

root@wopr:~# apt-get update && apt-get -u dist-upgrade
Get:1 file:/srv/mirror/ubuntu xenial InRelease [247 kB]
Get:1 file:/srv/mirror/ubuntu xenial InRelease [247 kB]
Get:2 file:/srv/mirror/ubuntu xenial-updates InRelease [102 kB] 
 
Get:2 file:/srv/mirror/ubuntu xenial-updates InRelease [102 kB] 
  
Get:3 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]  

Get:4 file:/srv/mirror/ubuntu xenial-updates/main Sources [302 kB] 
Get:5 file:/srv/mirror/ubuntu xenial-updates/universe Sources [199 kB]
Get:6 file:/srv/mirror/ubuntu xenial-updates/main amd64 Packages [746 kB]
Get:7 file:/srv/mirror/ubuntu xenial-updates/main i386 Packages [691 kB]
Get:8 file:/srv/mirror/ubuntu xenial-updates/main Translation-en [309 kB]
Get:9 file:/srv/mirror/ubuntu xenial-updates/universe amd64 Packages [616 kB]
Get:10 file:/srv/mirror/ubuntu xenial-updates/universe i386 Packages [570 kB]
Get:11 file:/srv/mirror/ubuntu xenial-updates/universe Translation-en [248 kB]
Get:12 http://security.ubuntu.com/ubuntu xenial-security/main Sources [119 kB]
Get:13 http://security.ubuntu.com/ubuntu xenial-security/universe Sources [62.4 
kB]
Get:14 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 
[467 kB]
Get:15 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages 
[421 kB]
Get:16 http://security.ubuntu.com/ubuntu xenial-security/main Translation-en 
[201 kB]
Get:17 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages [340 kB]
Get:18 http://security.ubuntu.com/ubuntu xenial-security/universe i386 Packages 
[296 kB]
Get:19 http://security.ubuntu.com/ubuntu xenial-security/universe 
Translation-en [126 kB]
Fetched 2,135 kB in 1s (1,520 kB/s)  
Reading package lists... Done
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libzstd0 linux-headers-4.4.0-109 linux-headers-4.4.0-109-generic 
linux-image-4.4.0-109-generic
  linux-image-extra-4.4.0-109-generic linux-signed-image-4.4.0-109-generic 
linux-tools-4.4.0-109
  linux-tools-4.4.0-109-generic
Use 'sudo apt autoremove' to remove them.
The following packages will be upgraded:
  apt apt-transport-https apt-utils initramfs-tools initramfs-tools-bin 
initramfs-tools-core libapt-inst2.0
  libapt-pkg5.0 libpam-systemd libpci-dev libpci3 libsystemd0 libudev-dev 
libudev1 lshw makedumpfile pciutils
  python-crypto systemd systemd-sysv udev
21 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 246 kB/8,157 kB of archives.
After this operation, 16.4 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 file:/srv/mirror/ubuntu xenial-updates/main amd64 libapt-pkg5.0 amd64 
1.2.26 [706 kB]
Get:2 file:/srv/mirror/ubuntu xenial-updates/main amd64 libapt-inst2.0 amd64 
1.2.26 [55.4 kB]
Get:3 file:/srv/mirror/ubuntu xenial-updates/main amd64 apt amd64 1.2.26 [1,043 
kB]
Get:4 file:/srv/mirror/ubuntu xenial-updates/main amd64 apt-utils amd64 1.2.26 
[197 kB]
Get:5 file:/srv/mirror/ubuntu xenial-updates/main amd64 libudev-dev amd64 
229-4ubuntu21.2 [150 kB]
Get:6 file:/srv/mirror/ubuntu xenial-updates/main amd64 libsystemd0 amd64 
229-4ubuntu21.2 [205 kB]
Get:7 file:/srv/mirror/ubuntu xenial-updates/main amd64 libpam-systemd amd64 
229-4ubuntu21.2 [115 kB]
Get:8 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
python-crypto amd64 2.6.1-6ubuntu0.16.04.3 [246 kB]
Get:9 file:/srv/mirror/ubuntu xenial-updates/main amd64 systemd amd64 
229-4ubuntu21.2 [3,634 kB]
Get:10 file:/srv/mirror/ubuntu xenial-updates/main amd64 udev amd64 
229-4ubuntu21.2 [993 kB]
Get:11 file:/srv/mirror/ubuntu xenial-updates/main amd64 libudev1 amd64 
229-4ubuntu21.2 [54.4 kB]
Get:12 file:/srv/mirror/ubuntu xenial-updates/main amd64 initramfs-tools all 
0.122ubuntu8.11 [8,590 B]
Get:13 file:/srv/mirror/ubuntu xenial-updates/main amd64 initramfs-tools-core 
all 0.122ubuntu8.11 [42.9 kB]
Get:14 file:/srv/mirror/ubuntu xenial-updates/main amd64 initramfs-tools-bin 
amd64 0.122ubuntu8.11 [9,592 B]
Get:15 file:/srv/mirror/ubuntu xenial-updates/main amd64 systemd-sysv amd64 
229-4ubuntu21.2 [11.9 kB]
Get:16 file:/srv/mirror/ubuntu xenial-updates/main amd64 apt-transport-https 
amd64 1.2.26 [26.1 kB]
Get:17 file:/srv/mirror/ubuntu xenial-updates/main amd64 pciutils amd64 
1:3.3.1-1.1ubuntu1.2 [234 kB]
Get:18 file:/srv/mirror/ubuntu xenial-updates/main amd64 libpci-dev amd64 
1:3.3.1-1.1ubuntu1.2 [42.7 kB]
Get:19 file:/srv/mirror/ubuntu xenial-updates/main amd64 libpci3 amd64 
1:3.3.1-1.1ubuntu1.2 [24.5 kB]
Get:20 file:/srv/mirror/ubuntu xenial-updates/main amd64 lshw amd64 
02.17-1.1ubuntu3.5 [215 kB]
Get:21 file:/srv/mirror/ubuntu xenial-updates/main amd64

[Touch-packages] [Bug 1760366] Re: [regression] Terminal titlebars are too tall

2018-04-03 Thread jfedor

I should have mentioned that I'm using the "GNOME Flashback (Compiz)"
desktop, sorry about that.

I don't think the apport-collect command worked correctly, as you can
see in the screenshot.

** Attachment added: "full screenshot"
   
https://bugs.launchpad.net/ubuntu-themes/+bug/1760366/+attachment/5100274/+files/Screenshot%20from%202018-04-03%2021-36-53.png

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

Title:
  [regression] Terminal titlebars are too tall

Status in Ubuntu theme:
  Incomplete
Status in ubuntu-themes package in Ubuntu:
  Incomplete

Bug description:
  It seems like change messed with the padding on the titlebar buttons
  (see attached screenshot):

  https://code.launchpad.net/~3v1n0/ubuntu-themes/windowbuttons-bg-and-
  padding

  Please go back to the way it was before.

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

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

[Touch-packages] [Bug 1760106] Re: FFe: Enable configuring resume offset via sysfs

2018-04-03 Thread Seth Forshee

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  FFe: Enable configuring resume offset via sysfs

Status in klibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  New
Status in klibc source package in Bionic:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  New

Bug description:
  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this
  attribute is important to be able to make hibernation work "out of the
  box".

  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=355064675f1c997cea017ea64c8f2c216e5425d9

  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.

  Klibc support for adopting this change is available here:
  https://www.zytor.com/pipermail/klibc/2018-March/003986.html

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

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

Re: [Touch-packages] [Bug 1717015] Re: libc resolver stops searching domain search list after getting back NSEC record

On Tue, Apr 03, 2018 at 08:59:19AM -, Dimitri John Ledkov wrote:
> 1) one should not manually adjust search domains in /etc/resolv.conf
> 2) systemd-resolved should learn about search domains
>  - for example, set search domains in /etc/systemd/resolved.conf if
> nothing sets them on per link basis vai resolved dbus api or
> networkd.network files.
> 
> 3) /etc/resolv.conf should be a symlink to
> ../run/systemd/resolve/stub-resolv.conf

> 4) ../run/systemd/resolve/stub-resolv.conf should be dynamically updated
> by resolved to contain the correct search domains

If systemd-resolved is going to publish search domain instructions to
../run/systemd/resolve/stub-resolv.conf anyway for use by the libc client, I
don't see any reason to say "one should not manually adjust search domains".

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

Title:
  libc resolver stops searching domain search list after getting back
  NSEC record

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Suppose that:

  1. you have a "search" line in your /etc/resolv.conf file;
  2. it has two domains in it; and
  3. the first of the two domains does DNSSEC, including returning NSEC records 
for nonexisting hosts.

  In this situation, when you try to look up a host name in the second
  domain without specifying the domain part of the host name, the libc
  resolver will stop after it gets back the NSEC record and report that
  the host name doesn't exist, rather than moving on to the second
  domain in the search list and searching for the host in that domain.

  See also https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1717014
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libc6 2.24-9ubuntu2.2
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Sep 13 16:00:45 2017
  Dependencies:
   gcc-6-base 6.3.0-12ubuntu2
   libc6 2.24-9ubuntu2.2
   libgcc1 1:6.3.0-12ubuntu2
  InstallationDate: Installed on 2016-08-09 (400 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: glibc
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (147 days ago)

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

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

[Touch-packages] [Bug 1760609] Re: liblxc-common missing Replaces on lxc1

This bug was fixed in the package lxc - 3.0.0-0ubuntu2

---
lxc (3.0.0-0ubuntu2) bionic; urgency=medium

  * Add missing breaks/replaces for lxc-init moving from lxc1 to
liblxc-common (LP: #1760609).

 -- Stéphane Graber   Mon, 02 Apr 2018 11:56:45
-0400

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

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

Title:
  liblxc-common missing Replaces on lxc1

Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  On upgrade from xenial to bionic:

  Selecting previously unselected package liblxc-common.
  Preparing to unpack .../liblxc-common_3.0.0-0ubuntu1_amd64.deb ...
  Unpacking liblxc-common (3.0.0-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/liblxc-common_3.0.0-0ubuntu1_amd64.deb (--unpack):
   trying to overwrite '/usr/sbin/init.lxc', which is also in package lxc1 
2.0.8-0ubuntu1~16.04.2
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

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

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

[Touch-packages] [Bug 1760952] Re: packagekitd crashed with SIGSEGV in gst_mini_object_unref()

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

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 #1720694, 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/1760952/+attachment/5100206/+files/CoreDump.gz

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

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

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

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

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

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

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

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

Title:
  packagekitd crashed with SIGSEGV in gst_mini_object_unref()

Status in packagekit package in Ubuntu:
  New

Bug description:
  I tried to install a codec with systems own internal procedure!

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: packagekit 1.1.9-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  Date: Tue Apr  3 22:46:38 2018
  ExecutablePath: /usr/lib/packagekit/packagekitd
  InstallationDate: Installed on 2018-03-17 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316)
  ProcCmdline: /usr/lib/packagekit/packagekitd
  SegvAnalysis:
   Segfault happened at: 0x7f16f66407e9 :  mov
0x8(%rdi),%edx
   PC (0x7f16f66407e9) ok
   source "0x8(%rdi)" (0x020d) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: packagekit
  StacktraceTop:
   gst_mini_object_unref () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
   GstMatcher::~GstMatcher() () from 
/usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
   AptIntf::providesCodec(PkgList&, char**) () from 
/usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
   ?? () from 
/usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
   ?? ()
  Title: packagekitd crashed with SIGSEGV in gst_mini_object_unref()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

2018-04-03 Thread franck

What happened to this bug? Is it still being addressed? I'm also experiencing 
the same problem and the solutions above don't work for me :(

Ubuntu 16.04.4 LTS
NetworkManager 1.2.6
dnsmasq 2.76

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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

[Touch-packages] [Bug 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving trig

This bug was fixed in the package plymouth - 0.9.2-3ubuntu13.3

---
plymouth (0.9.2-3ubuntu13.3) xenial; urgency=medium

  * Make the lsb-release triggers interest-noawait, so that we don't block
configuration of an Essential: yes package during upgrades.
LP: #1750465.

 -- Steve Langasek   Tue, 27 Mar 2018
12:04:31 -0700

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

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

Title:
  upgrade attempting to process triggers out of order (package plymouth-
  theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed)

Status in apt package in Ubuntu:
  Confirmed
Status in budgie-artwork package in Ubuntu:
  Fix Released
Status in kubuntu-settings package in Ubuntu:
  Fix Released
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  Fix Released
Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in budgie-artwork source package in Xenial:
  Confirmed
Status in kubuntu-settings source package in Xenial:
  Confirmed
Status in plymouth source package in Xenial:
  Fix Released
Status in ubuntu-gnome-default-settings source package in Xenial:
  Confirmed
Status in ubuntu-mate-artwork source package in Xenial:
  Confirmed
Status in apt source package in Artful:
  Confirmed
Status in budgie-artwork source package in Artful:
  Confirmed
Status in kubuntu-settings source package in Artful:
  Confirmed
Status in plymouth source package in Artful:
  Fix Released
Status in ubuntu-gnome-default-settings source package in Artful:
  Confirmed
Status in ubuntu-mate-artwork source package in Artful:
  Confirmed

Bug description:
  [SRU Justification]
  A package manager bug can cause dist-upgrades from 17.10 to 18.04 to fail 
because of trying to process triggers out of order.  Since the trigger being 
run is that of the currently-installed plymouth package, it is not guaranteed 
to be sufficient to fix the version of the package in 18.04.

  [Test case]
  1. Install plymouth-themes-ubuntu-text from -proposed.
  2. Run a release upgrade with each of update-manager -d, do-release-upgrade 
-d, and apt-get dist-upgrade (the last after manually changing sources.list).
  3. Verify that in each case, the upgrade completes successfully, with no 
errors about out-of-order trigger configuration.

  [Regression potential]
  noawait triggers have been supported in dpkg since 1.16.1, which is older 
than the version in precise 
(https://manpages.debian.org/jessie/dpkg-dev/deb-triggers.5.en.html).  A 
noawait trigger is considered appropriate whenever the triggered package does 
not need to block the triggering package.  There is no reason for a plymouth 
theme package to need to block configuration of an essential package in this 
case.  noawait triggers are well-exercised in the distro now, so the risk of 
regression from this change should be low.

  There is unfortunately not a known reproducer for the original bug, so
  the test case, while it should guard against regressions, is not
  strong confirmation that the bug is fixed.

  [Original description]
  Failure during upgrade attempt from Xubuntu 17.10 to Xubuntu 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu17
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sun Feb 18 23:41:49 2018
  DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-10-24 (118 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  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 1bcf:2c01 Sunplus Innovation Technology Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg

[Touch-packages] [Bug 1750013] Re: systemd-logind: memory leaks on session's connections (trusty-only)

2018-04-03 Thread Guilherme G. Piccoli

Dan, this is the v3 of the patch. I bumped the version to 20.28 since my
proposed 20.27 caused the regression aforementioned.

For this version, I removed the dependency of cgmanager, along with the
code that added closing sessions to garbage collector. Happens that a
similar code is present on systemd-logind already, and for some reason
(which is still a mystery for me) I was seeing a session leak in the
tool. My hypothesis is that I built one version of the tool without the
bunch of debian patches, and so that portion of code wasn't present.
Then, I started working in a fix, but in the end, the fix is useless
since a similar one is already there.

Anyway, the patch now just avoid some small memory leaks in both
session's free path and cgmanager glue code. It was tested in both
kernels 3.13 and 4.14 (with and without cgmanager), I didn't observe
leaks anymore nor high CPU utilization.

Thanks,


Guilherme

** Patch added: "lp1750013-trusty_v3.debdiff"
   
https://bugs.launchpad.net/ubuntu/artful/+source/systemd/+bug/1750013/+attachment/5100204/+files/lp1750013-trusty_v3.debdiff

** Tags removed: regression-proposed verification-done verification-done-trusty
** Tags added: sts-sru-needed

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

Title:
  systemd-logind: memory leaks on session's connections (trusty-only)

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Trusty:
  Fix Committed
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  Below the SRU request form. Please refer to the Original Description
  to a more comprehensive explanation of the problem observed.

  
  [Impact] 

   * systemd-logind tool is leaking memory at each session connected. The 
   issues happens in systemd from Trusty (14.04) only.

   * Three issues observed:
- systemd-logind is leaking entire sessions, i.e, the sessions are not 
  feeed after they're closed. In order to fix that, we proactively add 
  the sessions to systemd garbage collector (gc) when they are closed. 
  Also, part of the fix is to make cgmanager package a dependency. Refer 
  to comment #1 to a more thorough explanation of the issue and the fix.

- a small memory leak was observed in the session creation logic of 
  systemd-logind. The fix for that is the addition of an appropriate 
  free() call. Refer to comment #2 to more details on the issue and fix.

- another small memory leak was observed in the cgmanager glue code of 
  systemd-logind - this code is only present in this specific Ubuntu 
  release of the package, due to necessary compatibility layer with 
  upstart init system. The fix is to properly call free() in 2 
  functions. Refer to comment #3 to a deep exposition of the issue and 
  the fix.

  
  [Test Case]

   * The basic test-case is to run the following loop from a remote machine:
 while true; do ssh  "whoami"; done

   * It's possible to watch the increase in memory consumption from 
 "systemd-logind" process in the target machine. One can use the
 "ps uax" command to verify the RSS of the process, or count its 
 anonymous pages from /proc//smaps.

  
  [Regression Potential] 

   * Since the fixes are small and not intrusive, the potential for 
 regressions are low. More regression considerations on comments #1, #2 
 and #3 for each fix.

   * A potential small regressson is performance-wise, since now we add 
 sessions to garbage collector proactively.

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

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

[Touch-packages] [Bug 1750051] Re: cron doesn't support MAILFROM

** Tags added: bionic

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

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

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

Title:
  cron doesn't support MAILFROM

Status in cron package in Ubuntu:
  Triaged

Bug description:
  Ubuntu's cron version doesn't support setting MAILFROM to set the
  "From:" header of cron generated emails. This feature would be nice to
  have and bring parity with RHEL/CentOS which has it since RHEL 6:

  $ cat /etc/redhat-release 
  CentOS release 6.6 (Final)

  $ man 5 crontab | grep -1 FROM
 doesn´t do aliasing, and UUCP usually doesn´t read its mail.  If  MAIL-
 FROM is defined (and non-empty), it will be used as the envelope sender
 address, otherwise, ‘‘root’’ will be used.

  $ apt-cache policy cron
  cron:
Installed: 3.0pl1-128ubuntu2
Candidate: 3.0pl1-128ubuntu2
Version table:
   *** 3.0pl1-128ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cron 3.0pl1-128ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 16 15:52:54 2018
  InstallationDate: Installed on 2016-12-06 (436 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 
(20161206)
  SourcePackage: cron
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving trig

Here is the list of all blocking trigers that remain in the archive:
http://paste.ubuntu.com/p/7hP7pVqGMp/

the lsb-release ones have now been uploaded by me.

Please check if any other 'interest /' ones should be converted to
-noawait variant, and if there are any others that could become
-noawait.

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

Title:
  upgrade attempting to process triggers out of order (package plymouth-
  theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed)

Status in apt package in Ubuntu:
  Confirmed
Status in budgie-artwork package in Ubuntu:
  Fix Released
Status in kubuntu-settings package in Ubuntu:
  Fix Released
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  Fix Released
Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in budgie-artwork source package in Xenial:
  Confirmed
Status in kubuntu-settings source package in Xenial:
  Confirmed
Status in plymouth source package in Xenial:
  Fix Committed
Status in ubuntu-gnome-default-settings source package in Xenial:
  Confirmed
Status in ubuntu-mate-artwork source package in Xenial:
  Confirmed
Status in apt source package in Artful:
  Confirmed
Status in budgie-artwork source package in Artful:
  Confirmed
Status in kubuntu-settings source package in Artful:
  Confirmed
Status in plymouth source package in Artful:
  Fix Released
Status in ubuntu-gnome-default-settings source package in Artful:
  Confirmed
Status in ubuntu-mate-artwork source package in Artful:
  Confirmed

Bug description:
  [SRU Justification]
  A package manager bug can cause dist-upgrades from 17.10 to 18.04 to fail 
because of trying to process triggers out of order.  Since the trigger being 
run is that of the currently-installed plymouth package, it is not guaranteed 
to be sufficient to fix the version of the package in 18.04.

  [Test case]
  1. Install plymouth-themes-ubuntu-text from -proposed.
  2. Run a release upgrade with each of update-manager -d, do-release-upgrade 
-d, and apt-get dist-upgrade (the last after manually changing sources.list).
  3. Verify that in each case, the upgrade completes successfully, with no 
errors about out-of-order trigger configuration.

  [Regression potential]
  noawait triggers have been supported in dpkg since 1.16.1, which is older 
than the version in precise 
(https://manpages.debian.org/jessie/dpkg-dev/deb-triggers.5.en.html).  A 
noawait trigger is considered appropriate whenever the triggered package does 
not need to block the triggering package.  There is no reason for a plymouth 
theme package to need to block configuration of an essential package in this 
case.  noawait triggers are well-exercised in the distro now, so the risk of 
regression from this change should be low.

  There is unfortunately not a known reproducer for the original bug, so
  the test case, while it should guard against regressions, is not
  strong confirmation that the bug is fixed.

  [Original description]
  Failure during upgrade attempt from Xubuntu 17.10 to Xubuntu 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu17
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sun Feb 18 23:41:49 2018
  DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-10-24 (118 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  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 1bcf:2c01 Sunplus Innovation Technology Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.5.1
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth
  Title: package

[Touch-packages] [Bug 1759796] Re: Ubuntu images fail to build due to broken dh-python package

2018-04-03 Thread OpenStack Infra

Reviewed:  https://review.openstack.org/557906
Committed: 
https://git.openstack.org/cgit/openstack/kolla/commit/?id=3a26647c789ebd17064bcf63a88e673bcb0ecca0
Submitter: Zuul
Branch:stable/queens

commit 3a26647c789ebd17064bcf63a88e673bcb0ecca0
Author: Martin André 
Date:   Thu Mar 29 11:01:43 2018 +0200

Pin dh-python to earlier version to fix ubuntu gate

Let's pin the package until the dh-python from ubuntu-cloud-archive is
fixed.

Change-Id: I59f827bc7eb27a30f5d5f06628b3be535fcfabcc
Related-Bug: #1759796
(cherry picked from commit 739c51392f4244d68c023b061ce0300932db285b)


** Tags added: in-stable-queens

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

Title:
  Ubuntu images fail to build due to broken dh-python package

Status in kolla:
  New
Status in dh-python package in Ubuntu:
  New

Bug description:
  Some ubuntu images fails to build and block the gate.

  2018-03-28 15:07:13.498244 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'ovn-controller' to succeed!
  2018-03-28 15:07:13.498650 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'ovn-northd' to succeed!
  2018-03-28 15:07:13.498957 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'bifrost-base' to succeed!
  2018-03-28 15:07:13.499241 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'ovsdpdk' to succeed!
  2018-03-28 15:07:13.499559 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'ovn-sb-db-server' to succeed!
  2018-03-28 15:07:13.499867 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'ovn-nb-db-server' to succeed!

  http://logs.openstack.org/33/555733/1/check/kolla-build-ubuntu-
  source/72f9085/job-output.txt.gz#_2018-03-28_15_07_13_498244

  Looking more closely, it appears they fail to install lsb-release that
  depends on python3. Going up the dependency chain, the issue seems to
  be in dh-python that added a dependency on python3-distuils. However
  python3-distuils doesn't exist and should probably be
  python3-distutils.

  ()[root@f8bc5d1d504e bifrost-5.0.1.dev43]# apt-cache show dh-python
  Package: dh-python
  Priority: optional
  Section: python
  Installed-Size: 429
  Maintainer: Piotr Ożarowski 
  Architecture: all
  Version: 3.20180325ubuntu1~cloud0
  Replaces: python3 (<< 3.3.2-4~)
  Suggests: libdpkg-perl, dpkg-dev
  Depends: python3:any (>= 3.3.2-2~), python3-distuils
  Breaks: python3 (<< 3.3.2-4~)
  Supported: 60m
  Filename: pool/main/d/dh-python/dh-python_3.20180325ubuntu1~cloud0_all.deb
  Size: 89382
  SHA256: 5d31a348f141d7ca366eeb21b58633bed96a0b27417ce8759e1cb785cb1db8bc
  SHA1: a817acac0042ab6e22dd686376717a20e449ae03
  MD5sum: d89b5e505bbb93b57efe4bfb85fc353d
  Description: Debian helper tools for packaging Python libraries and 
applications
  Description-md5: b21cd6f99d6093fdc7e0ba30c8dd949f
  Multi-Arch: foreign
  Original-Maintainer: Piotr Ożarowski 

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

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

[Touch-packages] [Bug 1736072] Re: Encrypted swap does not work

2018-04-03 Thread dino99

That was some times ago, and i had chosen to reuse my separate swap and
home partitions, via the 'something else' install choice.

I was aware that the install design was changed to : swap file & home
dir, but was expecting that ubiquity was still understanding the user
choice. That is the main problem.

Instead i ended with cryptswap1 & 2, and i had to tweak fstab to try
booting with the good swap to avoid complaint. But that seems
impossible.

So, if the user still want to use partitions instead of file/dir, the
ubiquity proposal to encrypt is not able to follow the user choice. This
is something i have not understood when the installation was made (first
time encrypting experience).

Do you mind offering such proposal on partition ? or is only choice is
to encrypt the full disk ? (which is not my wish for future)

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

Title:
Encrypted swap does not work

Status in cryptsetup package in Ubuntu:
Incomplete
Status in systemd package in Ubuntu:
Incomplete
Status in ubiquity package in Ubuntu:
Incomplete

Bug description:
On a working system, i've added a new hdd, and decided to use it as the main
device storage.
So after doing the formatage (classic: / as ext4, swap, /home as ext4), i've
set a bionic iso installation.
Ubiquity then have proposed to set an encrypted swap dir, which i have
accepted, and then smootly terminated the installation.

Booting with that new install, i hit a cryptswap1 timeout after beeing
frozen around 1 minute.

oem@ubuntu:~$ journalctl | grep cryptswap
systemd[1]: Starting Cryptography Setup for cryptswap2...
systemd[1]: Started Cryptography Setup for cryptswap2.
systemd[1]: Found device /dev/mapper/cryptswap2.
systemd[1]: Activating swap /dev/mapper/cryptswap2...
kernel: Adding 10584572k swap on /dev/mapper/cryptswap2. Priority:-1
extents:1 across:10584572k FS
systemd[1]: Activated swap /dev/mapper/cryptswap2.
systemd[1]: Starting Cryptography Setup for cryptswap1...
systemd[1]: Started Cryptography Setup for cryptswap1.

oem@ubuntu:~$ journalctl | grep timeout
systemd[1]:
dev-disk-by\x2duuid-4c8437f6\x2d677d\x2d4740\x2dbdda\x2d072efadb49f4.device:
Job
dev-disk-by\x2duuid-4c8437f6\x2d677d\x2d4740\x2dbdda\x2d072efadb49f4.device/start
failed with result 'timeout'.

Note: cryptswap2 refer to the new hdd's swap partition, cryptswap1 refer to
the old hdd's swap partition.
/etc/fstab have been tested with only the active (mounted) disk, and with
both. In both cases the timeout happens.

oem@ubuntu:~$ swapon -s
Filename TypeSizeUsedPriority
/dev/dm-0 partition 10584572
221184 -1

Conclusion:
-ubiquity is proposing a non working feature (at least with multiple storage
devices/swap partitions
- the cryptsetup version is not well supporting the kernel/systemd
settings/configs

As Debian has more recent versions: 1.7.5-1 (sid) and 2.0.0 (experimental)
with some new features and cleanups, it should be a positive test to replace
the actual not working version with one of these.

http://metadata.ftp-master.debian.org/changelogs/main/c/cryptsetup/cryptsetup_2.0.0~rc1-1_changelog

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cryptsetup 2:1.7.3-4ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
Uname: Linux 4.13.0-18-generic x86_64
ApportVersion: 2.20.8-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Dec 4 07:26:17 2017
EcryptfsInUse: Yes
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: cryptsetup
UpgradeStatus: No upgrade log present (probably fresh install)
cmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-18-generic
root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro

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

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

[Touch-packages] [Bug 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving trig

I tested the plymouth update for xenial by enabling proposed, then
installing plymouth-theme-ubuntu-text, then modifying
/etc/apt/sources.list from xenial to bionic and finally running sudo
apt-get dist-upgrade.  The upgrade completed with no issues.

I think testing update-manager -d and do-release-upgrade -d is overly
paranoid and I'm setting this to verification-done.

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

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

Title:
  upgrade attempting to process triggers out of order (package plymouth-
  theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed)

Status in apt package in Ubuntu:
  Confirmed
Status in budgie-artwork package in Ubuntu:
  Fix Released
Status in kubuntu-settings package in Ubuntu:
  Fix Released
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  Fix Released
Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in budgie-artwork source package in Xenial:
  Confirmed
Status in kubuntu-settings source package in Xenial:
  Confirmed
Status in plymouth source package in Xenial:
  Fix Committed
Status in ubuntu-gnome-default-settings source package in Xenial:
  Confirmed
Status in ubuntu-mate-artwork source package in Xenial:
  Confirmed
Status in apt source package in Artful:
  Confirmed
Status in budgie-artwork source package in Artful:
  Confirmed
Status in kubuntu-settings source package in Artful:
  Confirmed
Status in plymouth source package in Artful:
  Fix Released
Status in ubuntu-gnome-default-settings source package in Artful:
  Confirmed
Status in ubuntu-mate-artwork source package in Artful:
  Confirmed

Bug description:
  [SRU Justification]
  A package manager bug can cause dist-upgrades from 17.10 to 18.04 to fail 
because of trying to process triggers out of order.  Since the trigger being 
run is that of the currently-installed plymouth package, it is not guaranteed 
to be sufficient to fix the version of the package in 18.04.

  [Test case]
  1. Install plymouth-themes-ubuntu-text from -proposed.
  2. Run a release upgrade with each of update-manager -d, do-release-upgrade 
-d, and apt-get dist-upgrade (the last after manually changing sources.list).
  3. Verify that in each case, the upgrade completes successfully, with no 
errors about out-of-order trigger configuration.

  [Regression potential]
  noawait triggers have been supported in dpkg since 1.16.1, which is older 
than the version in precise 
(https://manpages.debian.org/jessie/dpkg-dev/deb-triggers.5.en.html).  A 
noawait trigger is considered appropriate whenever the triggered package does 
not need to block the triggering package.  There is no reason for a plymouth 
theme package to need to block configuration of an essential package in this 
case.  noawait triggers are well-exercised in the distro now, so the risk of 
regression from this change should be low.

  There is unfortunately not a known reproducer for the original bug, so
  the test case, while it should guard against regressions, is not
  strong confirmation that the bug is fixed.

  [Original description]
  Failure during upgrade attempt from Xubuntu 17.10 to Xubuntu 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu17
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sun Feb 18 23:41:49 2018
  DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-10-24 (118 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  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 1bcf:2c01 Sunplus Innovation Technology Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4

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

2018-04-03 Thread Daniele Laudani

Public bug reported:

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

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


** Tags: amd64 apport-bug bionic wayland-session

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

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 798414] Re: update-initramfs should produce a more helpful error message when there isn't enough free space

2018-04-03 Thread M G

oh, you the correct first command is :
/boot$[sudo] rm -rf *4.13.0-36* 
(or older ones, depending on what you have **really, don't delete the ones you 
use or need**)

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

Title:
  update-initramfs should produce a more helpful error message when
  there isn't enough  free space

Status in initramfs-tools:
  Confirmed
Status in Ubuntu Software Center:
  Invalid
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: initramfs-tools

  When installing a kernel, /boot may become full during execution of
  post-installation script typically when update-initramfs is creating
  or updating an initrd.img file. This is resulting in kernel
  installation error.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  Ideal behavior:

  Give a more helpful error message when this unfortunate situation
  occurs so that user can fix the broken system and keep it going.

  Workaround:

  As the bug reporting system forwards user to this bug report, such 
instructions can be given here:
  https://help.ubuntu.com/community/RemoveOldKernels

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

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

I have added a bunch of other affected packages, whose templates I
reactivated and where there is a need to add "X-Ubuntu-Use-Langpack:
yes". I also reactivated the templates for:

indicator-appmenu
indicator-keyboard
indicator-printers

which already have "X-Ubuntu-Use-Langpack: yes".

So now I'd say that the affected packages are ready to be uploaded. Hey
Simon, are you there? ;)

-- 
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 1760435] Re: Use Ubuntu language packs for various Unity packages

** Also affects: unity-lens-files (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unity-lens-music (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unity-lens-photos (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unity-lens-video (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unity-scope-calculator (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unity-scope-devhelp (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unity-scope-home (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unity-scope-manpages (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime 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 798414] Re: update-initramfs should produce a more helpful error message when there isn't enough free space

2018-04-03 Thread M G

check /boot to see what are your old kernels that you're not necessarily
using. the system keeps two latest kernels. so if you're upgrading your
kernel to 4.13.0-38, you don't need 4.13.0-36 or older anymore( unless
you want a specific kernel for testing or something ), so you can delete
em.

/boot$[sudo] rm -rf *4.13.0-36 (or older ones, depending on what you
have **don't delete the ones you use or need**)

after that:

sudo apt-get update && sudo apt-get dist-upgrade

sudo apt-get auto remove

these should do it.

please be careful with rm -rf(it can be pretty devastating if you type
wrong things in there)

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

Title:
  update-initramfs should produce a more helpful error message when
  there isn't enough  free space

Status in initramfs-tools:
  Confirmed
Status in Ubuntu Software Center:
  Invalid
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: initramfs-tools

  When installing a kernel, /boot may become full during execution of
  post-installation script typically when update-initramfs is creating
  or updating an initrd.img file. This is resulting in kernel
  installation error.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  Ideal behavior:

  Give a more helpful error message when this unfortunate situation
  occurs so that user can fix the broken system and keep it going.

  Workaround:

  As the bug reporting system forwards user to this bug report, such 
instructions can be given here:
  https://help.ubuntu.com/community/RemoveOldKernels

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

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

[Touch-packages] [Bug 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving trig

2018-04-03 Thread Łukasz Zemczak

Can anyone perform testing of plymouth for xenial? It's blocking another
SRU that's in the queue right 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/1750465

Title:
  upgrade attempting to process triggers out of order (package plymouth-
  theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed)

Status in apt package in Ubuntu:
  Confirmed
Status in budgie-artwork package in Ubuntu:
  Fix Released
Status in kubuntu-settings package in Ubuntu:
  Fix Released
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  Fix Released
Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in budgie-artwork source package in Xenial:
  Confirmed
Status in kubuntu-settings source package in Xenial:
  Confirmed
Status in plymouth source package in Xenial:
  Fix Committed
Status in ubuntu-gnome-default-settings source package in Xenial:
  Confirmed
Status in ubuntu-mate-artwork source package in Xenial:
  Confirmed
Status in apt source package in Artful:
  Confirmed
Status in budgie-artwork source package in Artful:
  Confirmed
Status in kubuntu-settings source package in Artful:
  Confirmed
Status in plymouth source package in Artful:
  Fix Released
Status in ubuntu-gnome-default-settings source package in Artful:
  Confirmed
Status in ubuntu-mate-artwork source package in Artful:
  Confirmed

Bug description:
  [SRU Justification]
  A package manager bug can cause dist-upgrades from 17.10 to 18.04 to fail 
because of trying to process triggers out of order.  Since the trigger being 
run is that of the currently-installed plymouth package, it is not guaranteed 
to be sufficient to fix the version of the package in 18.04.

  [Test case]
  1. Install plymouth-themes-ubuntu-text from -proposed.
  2. Run a release upgrade with each of update-manager -d, do-release-upgrade 
-d, and apt-get dist-upgrade (the last after manually changing sources.list).
  3. Verify that in each case, the upgrade completes successfully, with no 
errors about out-of-order trigger configuration.

  [Regression potential]
  noawait triggers have been supported in dpkg since 1.16.1, which is older 
than the version in precise 
(https://manpages.debian.org/jessie/dpkg-dev/deb-triggers.5.en.html).  A 
noawait trigger is considered appropriate whenever the triggered package does 
not need to block the triggering package.  There is no reason for a plymouth 
theme package to need to block configuration of an essential package in this 
case.  noawait triggers are well-exercised in the distro now, so the risk of 
regression from this change should be low.

  There is unfortunately not a known reproducer for the original bug, so
  the test case, while it should guard against regressions, is not
  strong confirmation that the bug is fixed.

  [Original description]
  Failure during upgrade attempt from Xubuntu 17.10 to Xubuntu 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu17
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sun Feb 18 23:41:49 2018
  DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-10-24 (118 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  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 1bcf:2c01 Sunplus Innovation Technology Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.5.1
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth
  Title: package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-02-19 (0 days ago)
  dmi.bios.date:

[Touch-packages] [Bug 1736072] Re: Encrypted swap does not work

I am confused about the original statement "Ubiquity then have proposed
to set an encrypted swap dir" because ubiquity does not propose to do
such things at all.

By default we do not create swap partitions, in the full disk encryption
case we use LVM and encrypt the whole VG which contains swap as an LVM
volume, home directory encryption has been removed.

Please indicate the steps performed in ubiquity that yielded "an
ecrypted swap dir"?

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

** No longer affects: ubiquity (Ubuntu Bionic)

** No longer affects: systemd (Ubuntu Bionic)

** No longer affects: cryptsetup (Ubuntu Bionic)

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

Title:
  Encrypted swap does not work

Status in cryptsetup package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Incomplete

Bug description:
  On a working system, i've added a new hdd, and decided to use it as the main 
device storage.
  So after doing the formatage (classic: / as ext4, swap, /home as ext4), i've 
set a bionic iso installation.
  Ubiquity then have proposed to set an encrypted swap dir, which i have 
accepted, and then smootly terminated the installation.

  Booting with that new install, i hit a cryptswap1 timeout after beeing
  frozen around 1 minute.

  oem@ubuntu:~$ journalctl | grep cryptswap
  systemd[1]: Starting Cryptography Setup for cryptswap2...
  systemd[1]: Started Cryptography Setup for cryptswap2.
  systemd[1]: Found device /dev/mapper/cryptswap2.
  systemd[1]: Activating swap /dev/mapper/cryptswap2...
  kernel: Adding 10584572k swap on /dev/mapper/cryptswap2.  Priority:-1 
extents:1 across:10584572k FS
  systemd[1]: Activated swap /dev/mapper/cryptswap2.
  systemd[1]: Starting Cryptography Setup for cryptswap1...
  systemd[1]: Started Cryptography Setup for cryptswap1.

  oem@ubuntu:~$ journalctl | grep timeout
  systemd[1]: 
dev-disk-by\x2duuid-4c8437f6\x2d677d\x2d4740\x2dbdda\x2d072efadb49f4.device: 
Job 
dev-disk-by\x2duuid-4c8437f6\x2d677d\x2d4740\x2dbdda\x2d072efadb49f4.device/start
 failed with result 'timeout'.

  Note: cryptswap2 refer to the new hdd's swap partition, cryptswap1 refer to 
the old hdd's swap partition.
  /etc/fstab have been tested with only the active (mounted) disk, and with 
both. In both cases the timeout happens.

  oem@ubuntu:~$ swapon -s
  Filename  TypeSizeUsedPriority
  /dev/dm-0 partition   10584572
221184  -1

  
  Conclusion:
  -ubiquity is proposing a non working feature (at least with multiple storage 
devices/swap partitions
  - the cryptsetup version is not well supporting the kernel/systemd 
settings/configs

  As Debian has more recent versions: 1.7.5-1 (sid) and 2.0.0 (experimental) 
with some new features and cleanups, it should be a positive test to replace 
the actual not working version with one of these.
  
http://metadata.ftp-master.debian.org/changelogs/main/c/cryptsetup/cryptsetup_2.0.0~rc1-1_changelog

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cryptsetup 2:1.7.3-4ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
  Uname: Linux 4.13.0-18-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Dec  4 07:26:17 2017
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: cryptsetup
  UpgradeStatus: No upgrade log present (probably fresh install)
  cmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-18-generic 
root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro

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

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

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

2018-04-03 Thread Eric Desrochers

Seems like this recipe is enough to start gnome (as a potential
workaround until this get fix) :

# systemctl mask tmp.mount
# ctrl-d

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

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1758254] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned

2018-04-03 Thread Jean-Baptiste Lallement

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

** This bug is no longer a duplicate of bug 1756576
   package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers 
looping, abandoned
** This bug has been marked a duplicate of bug 1747717
   package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers 
looping, abandoned - gnome-menus -> ufw

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

Title:
  package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade:
  triggers looping, abandoned

Status in bamf package in Ubuntu:
  New
Status in desktop-file-utils package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New
Status in gnome-menus package in Ubuntu:
  New
Status in mime-support package in Ubuntu:
  New

Bug description:
  i need help

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gnome-menus 3.13.3-6ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Mar 23 12:29:05 2018
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2017-11-21 (121 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: gnome-menus
  Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2018-03-23 (0 days ago)

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

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

[Touch-packages] [Bug 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving trig

This bug was fixed in the package ubuntu-gnome-default-settings -
17.10.4

---
ubuntu-gnome-default-settings (17.10.4) bionic; urgency=medium

  * Use noawait trigger variant when tracking lsb-release. LP: #1750465

 -- Dimitri John Ledkov   Tue, 03 Apr 2018 15:18:30
+0100

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

Title:
  upgrade attempting to process triggers out of order (package plymouth-
  theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed)

Status in apt package in Ubuntu:
  Confirmed
Status in budgie-artwork package in Ubuntu:
  Fix Released
Status in kubuntu-settings package in Ubuntu:
  Fix Released
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  Fix Released
Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in budgie-artwork source package in Xenial:
  Confirmed
Status in kubuntu-settings source package in Xenial:
  Confirmed
Status in plymouth source package in Xenial:
  Fix Committed
Status in ubuntu-gnome-default-settings source package in Xenial:
  Confirmed
Status in ubuntu-mate-artwork source package in Xenial:
  Confirmed
Status in apt source package in Artful:
  Confirmed
Status in budgie-artwork source package in Artful:
  Confirmed
Status in kubuntu-settings source package in Artful:
  Confirmed
Status in plymouth source package in Artful:
  Fix Released
Status in ubuntu-gnome-default-settings source package in Artful:
  Confirmed
Status in ubuntu-mate-artwork source package in Artful:
  Confirmed

Bug description:
  [SRU Justification]
  A package manager bug can cause dist-upgrades from 17.10 to 18.04 to fail 
because of trying to process triggers out of order.  Since the trigger being 
run is that of the currently-installed plymouth package, it is not guaranteed 
to be sufficient to fix the version of the package in 18.04.

  [Test case]
  1. Install plymouth-themes-ubuntu-text from -proposed.
  2. Run a release upgrade with each of update-manager -d, do-release-upgrade 
-d, and apt-get dist-upgrade (the last after manually changing sources.list).
  3. Verify that in each case, the upgrade completes successfully, with no 
errors about out-of-order trigger configuration.

  [Regression potential]
  noawait triggers have been supported in dpkg since 1.16.1, which is older 
than the version in precise 
(https://manpages.debian.org/jessie/dpkg-dev/deb-triggers.5.en.html).  A 
noawait trigger is considered appropriate whenever the triggered package does 
not need to block the triggering package.  There is no reason for a plymouth 
theme package to need to block configuration of an essential package in this 
case.  noawait triggers are well-exercised in the distro now, so the risk of 
regression from this change should be low.

  There is unfortunately not a known reproducer for the original bug, so
  the test case, while it should guard against regressions, is not
  strong confirmation that the bug is fixed.

  [Original description]
  Failure during upgrade attempt from Xubuntu 17.10 to Xubuntu 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu17
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sun Feb 18 23:41:49 2018
  DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-10-24 (118 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  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 1bcf:2c01 Sunplus Innovation Technology Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.5.1
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth
  Title: package

[Touch-packages] [Bug 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving trig

This bug was fixed in the package kubuntu-settings - 1:18.04ubuntu10

---
kubuntu-settings (1:18.04ubuntu10) bionic; urgency=medium

  * Use noawait trigger variant when tracking lsb-release. LP: #1750465

 -- Dimitri John Ledkov   Tue, 03 Apr 2018 15:12:29
+0100

** Changed in: ubuntu-gnome-default-settings (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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1750465

Title:
  upgrade attempting to process triggers out of order (package plymouth-
  theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed)

Status in apt package in Ubuntu:
  Confirmed
Status in budgie-artwork package in Ubuntu:
  Fix Released
Status in kubuntu-settings package in Ubuntu:
  Fix Released
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  Fix Released
Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in budgie-artwork source package in Xenial:
  Confirmed
Status in kubuntu-settings source package in Xenial:
  Confirmed
Status in plymouth source package in Xenial:
  Fix Committed
Status in ubuntu-gnome-default-settings source package in Xenial:
  Confirmed
Status in ubuntu-mate-artwork source package in Xenial:
  Confirmed
Status in apt source package in Artful:
  Confirmed
Status in budgie-artwork source package in Artful:
  Confirmed
Status in kubuntu-settings source package in Artful:
  Confirmed
Status in plymouth source package in Artful:
  Fix Released
Status in ubuntu-gnome-default-settings source package in Artful:
  Confirmed
Status in ubuntu-mate-artwork source package in Artful:
  Confirmed

Bug description:
  [SRU Justification]
  A package manager bug can cause dist-upgrades from 17.10 to 18.04 to fail 
because of trying to process triggers out of order.  Since the trigger being 
run is that of the currently-installed plymouth package, it is not guaranteed 
to be sufficient to fix the version of the package in 18.04.

  [Test case]
  1. Install plymouth-themes-ubuntu-text from -proposed.
  2. Run a release upgrade with each of update-manager -d, do-release-upgrade 
-d, and apt-get dist-upgrade (the last after manually changing sources.list).
  3. Verify that in each case, the upgrade completes successfully, with no 
errors about out-of-order trigger configuration.

  [Regression potential]
  noawait triggers have been supported in dpkg since 1.16.1, which is older 
than the version in precise 
(https://manpages.debian.org/jessie/dpkg-dev/deb-triggers.5.en.html).  A 
noawait trigger is considered appropriate whenever the triggered package does 
not need to block the triggering package.  There is no reason for a plymouth 
theme package to need to block configuration of an essential package in this 
case.  noawait triggers are well-exercised in the distro now, so the risk of 
regression from this change should be low.

  There is unfortunately not a known reproducer for the original bug, so
  the test case, while it should guard against regressions, is not
  strong confirmation that the bug is fixed.

  [Original description]
  Failure during upgrade attempt from Xubuntu 17.10 to Xubuntu 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu17
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sun Feb 18 23:41:49 2018
  DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-10-24 (118 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  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 1bcf:2c01 Sunplus Innovation Technology Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.5.1
  SourcePackage: plymouth
  TextPlymouth:

[Touch-packages] [Bug 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving trig

This bug was fixed in the package ubuntu-mate-artwork - 18.04.9

---
ubuntu-mate-artwork (18.04.9) bionic; urgency=medium

  * Use noawait trigger variant when tracking lsb-release. LP: #1750465

 -- Dimitri John Ledkov   Tue, 03 Apr 2018 15:22:45
+0100

** Changed in: ubuntu-mate-artwork (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: kubuntu-settings (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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1750465

Title:
  upgrade attempting to process triggers out of order (package plymouth-
  theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed)

Status in apt package in Ubuntu:
  Confirmed
Status in budgie-artwork package in Ubuntu:
  Fix Released
Status in kubuntu-settings package in Ubuntu:
  Fix Released
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  Fix Released
Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in budgie-artwork source package in Xenial:
  Confirmed
Status in kubuntu-settings source package in Xenial:
  Confirmed
Status in plymouth source package in Xenial:
  Fix Committed
Status in ubuntu-gnome-default-settings source package in Xenial:
  Confirmed
Status in ubuntu-mate-artwork source package in Xenial:
  Confirmed
Status in apt source package in Artful:
  Confirmed
Status in budgie-artwork source package in Artful:
  Confirmed
Status in kubuntu-settings source package in Artful:
  Confirmed
Status in plymouth source package in Artful:
  Fix Released
Status in ubuntu-gnome-default-settings source package in Artful:
  Confirmed
Status in ubuntu-mate-artwork source package in Artful:
  Confirmed

Bug description:
  [SRU Justification]
  A package manager bug can cause dist-upgrades from 17.10 to 18.04 to fail 
because of trying to process triggers out of order.  Since the trigger being 
run is that of the currently-installed plymouth package, it is not guaranteed 
to be sufficient to fix the version of the package in 18.04.

  [Test case]
  1. Install plymouth-themes-ubuntu-text from -proposed.
  2. Run a release upgrade with each of update-manager -d, do-release-upgrade 
-d, and apt-get dist-upgrade (the last after manually changing sources.list).
  3. Verify that in each case, the upgrade completes successfully, with no 
errors about out-of-order trigger configuration.

  [Regression potential]
  noawait triggers have been supported in dpkg since 1.16.1, which is older 
than the version in precise 
(https://manpages.debian.org/jessie/dpkg-dev/deb-triggers.5.en.html).  A 
noawait trigger is considered appropriate whenever the triggered package does 
not need to block the triggering package.  There is no reason for a plymouth 
theme package to need to block configuration of an essential package in this 
case.  noawait triggers are well-exercised in the distro now, so the risk of 
regression from this change should be low.

  There is unfortunately not a known reproducer for the original bug, so
  the test case, while it should guard against regressions, is not
  strong confirmation that the bug is fixed.

  [Original description]
  Failure during upgrade attempt from Xubuntu 17.10 to Xubuntu 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu17
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sun Feb 18 23:41:49 2018
  DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-10-24 (118 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  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 1bcf:2c01 Sunplus Innovation Technology Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg

[Touch-packages] [Bug 1756446] Re: Include JournalErrors.txt

Both staging and production have been updated now.

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

Title:
  Include JournalErrors.txt

Status in Daisy:
  New
Status in whoopsie package in Ubuntu:
  Fix Released
Status in whoopsie source package in Bionic:
  Fix Released

Bug description:
  JournalErrors is not in the list of acceptable_fields for whoopsie,
  this is a good thing given how large it can get. That being said it
  would be useful (per seb128) to include a portion of JournalErrors in
  the crash reports in the Error Tracker.

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

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

[Touch-packages] [Bug 1760923] [NEW] watch command stack smash running nvidia-smi 384.111

2018-04-03 Thread Stefan Helmert

Public bug reported:

On Ubuntu 16.04 LTS, AMD Ryzen 7 1700, 16 GB RAM, Nvidia GTX 1050 Ti
with driver 384.111 running

watch nvidia-smi

crashes after 4 days nonstop operation with message "stack smashed"

This does NOT happen on Intel Xeon E5-2660v4, GTX 1080 Ti with Ubuntu
17.04, Nvidia driver 384.111.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: procps 2:3.3.10-4ubuntu2.3
ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Apr  3 18:07:17 2018
InstallationDate: Installed on 2018-03-23 (11 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
SourcePackage: procps
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  watch command stack smash running  nvidia-smi 384.111

Status in procps package in Ubuntu:
  New

Bug description:
  On Ubuntu 16.04 LTS, AMD Ryzen 7 1700, 16 GB RAM, Nvidia GTX 1050 Ti
  with driver 384.111 running

  watch nvidia-smi

  crashes after 4 days nonstop operation with message "stack smashed"

  This does NOT happen on Intel Xeon E5-2660v4, GTX 1080 Ti with Ubuntu
  17.04, Nvidia driver 384.111.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: procps 2:3.3.10-4ubuntu2.3
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr  3 18:07:17 2018
  InstallationDate: Installed on 2018-03-23 (11 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  SourcePackage: procps
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1634061] Re: package avahi-dnsconfd 0.6.32-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

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

** This bug has been marked a duplicate of bug 1760128
   package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1

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

Title:
  package avahi-dnsconfd 0.6.32-1ubuntu1 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  package failed when update to ubuntu mate 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: avahi-dnsconfd 0.6.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Mon Oct 17 15:04:07 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-10-06 (11 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32-1ubuntu1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to yakkety on 2016-10-17 (0 days ago)

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

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

[Touch-packages] [Bug 1699572] Re: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: underprosessen installerte pre-removal-skript returnerte feilstatus 1

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

** This bug has been marked a duplicate of bug 1760128
   package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1

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

Title:
  package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to
  install/upgrade: underprosessen installerte pre-removal-skript
  returnerte feilstatus 1

Status in avahi package in Ubuntu:
  New

Bug description:
  i was looking for additional drivers.
  then this error did appear.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Sun Jun 18 18:51:04 2017
  DpkgTerminalLog:
   Removing avahi-dnsconfd (0.6.32~rc+dfsg-1ubuntu2) ...
   Job for avahi-daemon.socket canceled.
   dpkg: error processing package avahi-dnsconfd (--purge):
underprosessen installerte pre-removal-skript returnerte feilstatus 1
  DuplicateSignature:
   package:avahi-dnsconfd:0.6.32~rc+dfsg-1ubuntu2
   Removing avahi-dnsconfd (0.6.32~rc+dfsg-1ubuntu2) ...
   Job for avahi-daemon.socket canceled.
   dpkg: error processing package avahi-dnsconfd (--purge):
underprosessen installerte pre-removal-skript returnerte feilstatus 1
  ErrorMessage: underprosessen installerte pre-removal-skript returnerte 
feilstatus 1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: underprosessen installerte pre-removal-skript returnerte 
feilstatus 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1692365] Re: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

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

** This bug has been marked a duplicate of bug 1760128
   package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1

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

Title:
  package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to
  install/upgrade: subprocess installed pre-removal script returned
  error exit status 1

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  I had installed gnome classic and also (to test it) the Mate desktop.
  I like Gnome classic best so I uninstalled the Mate desktop.
  And now this avari package is missing.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sun May 21 23:32:35 2017
  DuplicateSignature:
   package:avahi-dnsconfd:0.6.32~rc+dfsg-1ubuntu2
   Removing avahi-dnsconfd (0.6.32~rc+dfsg-1ubuntu2) ...
   Job for avahi-daemon.socket canceled.
   dpkg: error processing package avahi-dnsconfd (--remove):
subprocess installed pre-removal script returned error exit status 1
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2017-05-20 (1 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: subprocess installed pre-removal script returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1750105] Re: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: il sottoprocesso nuovo script pre-removal ha restituito lo stato di errore 1

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

** This bug has been marked a duplicate of bug 1760128
   package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1

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

Title:
  package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to
  install/upgrade: il sottoprocesso nuovo script pre-removal ha
  restituito lo stato di errore 1

Status in avahi package in Ubuntu:
  New

Bug description:
  error during booting

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Mon Feb 12 18:53:55 2018
  ErrorMessage: il sottoprocesso nuovo script pre-removal ha restituito lo 
stato di errore 1
  InstallationDate: Installed on 2018-01-24 (23 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  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:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: il sottoprocesso nuovo script pre-removal ha restituito lo 
stato di errore 1
  UpgradeStatus: Upgraded to artful on 2018-02-03 (13 days ago)

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

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

[Touch-packages] [Bug 1759408] Re: package avahi-dnsconfd 0.6.32-1ubuntu1 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1

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

** This bug has been marked a duplicate of bug 1760128
   package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1

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

Title:
  package avahi-dnsconfd 0.6.32-1ubuntu1 failed to install/upgrade: el
  subproceso script pre-removal nuevo devolvió el código de salida de
  error 1

Status in avahi package in Ubuntu:
  New

Bug description:
  Can't update the package.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: avahi-dnsconfd 0.6.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Tue Mar 27 23:58:43 2018
  ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de 
salida de error 1
  InstallationDate: Installed on 2016-10-05 (538 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  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:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32-1ubuntu1 failed to install/upgrade: el 
subproceso script pre-removal nuevo devolvió el código de salida de error 1
  UpgradeStatus: Upgraded to artful on 2018-01-18 (68 days ago)

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

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

** Also affects: unity-greeter (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unity-lens-applications (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime 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

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 1760446] Re: package avahi-dnsconfd 0.6.32-1ubuntu1 failed to install/upgrade: le sous-processus nouveau script pre-removal a retourné une erreur de sortie d'état 1

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

** This bug has been marked a duplicate of bug 1760128
   package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1

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

Title:
  package avahi-dnsconfd 0.6.32-1ubuntu1 failed to install/upgrade: le
  sous-processus nouveau script pre-removal a retourné une erreur de
  sortie d'état 1

Status in avahi package in Ubuntu:
  New

Bug description:
  This appeared during an update. Reproduced on another computer.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: avahi-dnsconfd 0.6.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sun Apr  1 16:42:43 2018
  ErrorMessage: le sous-processus nouveau script pre-removal a retourné une 
erreur de sortie d'état 1
  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:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32-1ubuntu1 failed to install/upgrade: le 
sous-processus nouveau script pre-removal a retourné une erreur de sortie 
d'état 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1750583] Re: Broken panel and launcher - all black

2018-04-03 Thread Sam_

No, that was false hope, after .cache clean up and restart no real
change.

** Attachment added: "graphics-still-broken.png"
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1750583/+attachment/5100072/+files/graphics-still-broken.png

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

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

** Description changed:

- Since latest update all symbols at the launcher and search panel are black. 
(screenshot)
+ Since latest update 2018-02-15 (apt-history attached) all symbols at the 
launcher and Unity dash are black. (screenshot)
  All other applications and menues are fine, also the menues from 
unity-panel-service are ok.
  Changing the theme didn't help, restart of desktop or computer also didn't 
help.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.5+16.04.20171201.3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,imgjpeg,decor,regex,text,move,winrules,compiztoolbox,mousepoll,vpswitch,gnomecompat,obs,imgpng,grid,cube,place,resize,commands,ring,workarounds,scale,screenshot,expo,rotate,ezoom,unitymtgrabhandles,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Feb 20 15:29:39 2018
  DistUpgraded: 2016-08-01 14:42:41,957 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4350/4550] 
[1002:954f] (prog-if 00 [VGA controller])
-Subsystem: PC Partner Limited / Sapphire Technology RV710 [Radeon HD 
4350/4550] [174b:174b]
+  Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4350/4550] 
[1002:954f] (prog-if 00 [VGA controller])
+    Subsystem: PC Partner Limited / Sapphire Technology RV710 [Radeon HD 
4350/4550] [174b:174b]
  InstallationDate: Installed on 2012-02-05 (2207 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120204)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=b3e26f93-613b-48e8-96d7-9c8854fe670c ro
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-08-01 (568 days ago)
  dmi.bios.date: 07/30/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0305
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5QLD PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0305:bd07/30/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QLDPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Feb 20 15:27:07 2018
  xserver.configfile: default
  xserver.devices:
-  inputPower Button KEYBOARD, id 6
-  inputPower Button KEYBOARD, id 7
-  inputLogitech Logitech Illuminated Keyboard KEYBOARD, id 8
-  inputLogitech Logitech Illuminated Keyboard KEYBOARD, id 9
-  inputLogitech USB-PS/2 Optical Mouse MOUSE, id 10
+  inputPower Button KEYBOARD, id 6
+  inputPower Button KEYBOARD, id 7
+  inputLogitech Logitech Illuminated Keyboard KEYBOARD, id 8
+  inputLogitech Logitech Illuminated Keyboard KEYBOARD, id 9
+  inputLogitech USB-PS/2 Optical Mouse MOUSE, id 10
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: radeon

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

Title:
  Broken panel and

[Touch-packages] [Bug 1760368] Re: package avahi-dnsconfd 0.6.32-1ubuntu1 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1

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

** This bug has been marked a duplicate of bug 1760128
   package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1

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

Title:
  package avahi-dnsconfd 0.6.32-1ubuntu1 failed to install/upgrade: el
  subproceso script pre-removal nuevo devolvió el código de salida de
  error 1

Status in avahi package in Ubuntu:
  New

Bug description:
  tried to upgrade to ubuntu 18.04 bionic beaver from ubuntu mate 17.10

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: avahi-dnsconfd 0.6.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sat Mar 31 18:43:21 2018
  ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de 
salida de error 1
  InstallationDate: Installed on 2018-01-07 (83 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Python3Details: /usr/local/bin/python3.6, Python 3.6.4, unpackaged
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32-1ubuntu1 failed to install/upgrade: el 
subproceso script pre-removal nuevo devolvió el código de salida de error 1
  UpgradeStatus: Upgraded to artful on 2018-03-28 (3 days ago)

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

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

[Touch-packages] [Bug 1760128] Re: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

This is trivial to reproduce by installing avahi-dnsconfd and then
reinstalling it.

bdmurray@clean-xenial-amd64:~$ sudo apt-get install --reinstall avahi-dnsconfd
Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/14.2 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 212825 files and directories currently installed.)
Preparing to unpack .../avahi-dnsconfd_0.6.32~rc+dfsg-1ubuntu2_amd64.deb ...
Job for avahi-daemon.socket canceled.
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
Job for avahi-daemon.socket canceled.
dpkg: error processing archive 
/var/cache/apt/archives/avahi-dnsconfd_0.6.32~rc+dfsg-1ubuntu2_amd64.deb 
(--unpack):
 subprocess new pre-removal script returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/avahi-dnsconfd_0.6.32~rc+dfsg-1ubuntu2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


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

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

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

Title:
  package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in avahi package in Ubuntu:
  Triaged

Bug description:
  Ubuntu Update 30.03.18

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Mar 30 16:32:50 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-01-31 (788 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160131)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1760415] Re: gnome-shell crashed with SIGSEGV in intel_miptree_supports_hiz() from needs_separate_stencil()

2018-04-03 Thread Andrea Azzarone

** Changed in: gnome-shell (Ubuntu)
   Status: New => Invalid

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

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

** Changed in: mesa (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gnome-shell (Ubuntu)
   Importance: Medium => Undecided

** Changed in: mesa (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

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

Title:
  gnome-shell crashed with SIGSEGV in intel_miptree_supports_hiz() from
  needs_separate_stencil()

Status in gnome-shell package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  Screen had automatically locked overnight. Bug report prompt appeared
  a few seconds after I logged in.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 31 10:24:03 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-10-23 (159 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f8c18dbc870:mov(%rdi),%eax
   PC (0x7f8c18dbc870) ok
   source "(%rdi)" (0x0074) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: Upgraded to bionic on 2018-03-17 (14 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

Ok, so the templates were not deleted, but deactivated. In addition to
those which Sebastien reactivated, I have reactivated unity-settings-
daemon and unity-control-center for now.

So packages identified so far, which need to be uploaded with "X-Ubuntu-
Use-Langpack: yes", are indicator-datetime and unity.

** No longer affects: indicator-messages (Ubuntu)

** No longer affects: indicator-power (Ubuntu)

** No longer affects: indicator-session (Ubuntu)

** No longer affects: indicator-sound (Ubuntu)

** Summary changed:

- Use Ubuntu language packs for various indicators
+ Use Ubuntu language packs for various Unity packages

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime 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

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 1757565] Re: btrfs and tar sparse truncate archives

2018-04-03 Thread Kleber Sacilotto de Souza

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

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

Title:
  btrfs and tar sparse truncate archives

Status in linux package in Ubuntu:
  Fix Released
Status in tar package in Ubuntu:
  New
Status in linux source package in Artful:
  Fix Committed
Status in tar source package in Artful:
  New

Bug description:
  
  == SRU Justification ==
  This bug causes btrfs and tar sparse to truncate archives.  This bug has been 
  fixed in v4.15-rc3 by commit e3b8a4858566, which has a prereq commit of 
f48bf66b662e.

  These commits were cc'd to upstream stable and are already in Bionic.  
However, upstream
  4.13 is EOL, so Artful never recieved the fixes, which is the reason for
  the SRU request.

  == Fixes ==
  f48bf66b662e ("Btrfs: move definition of the function 
btrfs_find_new_delalloc_bytes")
  e3b8a4858566 ("Btrfs: fix reported number of inode blocks after buffered 
append writes")

  == Regression Potential ==
  Low.  This fix was also sent and accepted to stable, so it has had additional 
upstream review.

  == Test Case ==
  A test kernel was built with these patches and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.



  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  root@ubuntu:~# apt-cache policy linux-image-virtual
  linux-image-virtual:
    Installed: 4.13.0.37.40
    Candidate: 4.13.0.37.40
    Version table:
   *** 4.13.0.37.40 500
  500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.13.0.16.17 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages

  3. Taring files into an archive are not truncated
  4. Files included in tar are filled with NULLs

  To reproduce, run an Artful system with one spare disk:

  - mkfs.btrfs -f /dev/sda
  - mount /dev/sda /mnt
  - grep sda /proc/mounts
  /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0

  Then run this script which copies a 4MB binary to a btrfs filesystem,
  tars the directory up containing the binary; then untars to stdout and
  md5sum compares, showing it's different.

  % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; 
cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz 
.; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum
  e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
  0ce8c4139740198926273853defcb12a  -

  And now without the sparse flag:

  # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; 
cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz 
.; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum
  e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
  e4121d2f3126b8c364bfa1aaa82371a3  -

  This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an 
actual fix.
  Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 
kernel appears to be fixed as well though I'm not sure what the difference is.

  References:

  https://patchwork.kernel.org/patch/10151037/
  https://www.spinics.net/lists/linux-btrfs/msg56768.html
  https://www.spinics.net/lists/linux-btrfs/msg57111.html

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-virtual 4.13.0.37.40
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 21 22:55 seq
   crw-rw 1 root audio 116, 33 Mar 21 22:55 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Mar 21 23:08:05 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-37-generic N/A
   linux-backports-modules-4.13.0-37-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

[Touch-packages] [Bug 1760910] [NEW] Gdebi crash in Ubuntu Studio 18.04

2018-04-03 Thread Phelps Scofield

Public bug reported:

Gdebi opens normal, but when you click install package, it closes.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gdebi 0.9.5.7+nmu2
ProcVersionSignature: Ubuntu 4.15.0-13.14-lowlatency 4.15.10
Uname: Linux 4.15.0-13-lowlatency x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Apr  3 12:31:17 2018
InstallationDate: Installed on 2018-03-29 (4 days ago)
InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180328)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=pt_BR:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SourcePackage: gdebi
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  Gdebi crash in Ubuntu Studio 18.04

Status in gdebi package in Ubuntu:
  New

Bug description:
  Gdebi opens normal, but when you click install package, it closes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdebi 0.9.5.7+nmu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-lowlatency 4.15.10
  Uname: Linux 4.15.0-13-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Apr  3 12:31:17 2018
  InstallationDate: Installed on 2018-03-29 (4 days ago)
  InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180328)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=pt_BR:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Uploaded 2.12-4ubuntu3 to address this.

-- 
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 Committed
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 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving trig

** Changed in: ubuntu-gnome-default-settings (Ubuntu)
   Status: Confirmed => Fix Committed

** Changed in: ubuntu-mate-artwork (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  upgrade attempting to process triggers out of order (package plymouth-
  theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed)

Status in apt package in Ubuntu:
  Confirmed
Status in budgie-artwork package in Ubuntu:
  Fix Released
Status in kubuntu-settings package in Ubuntu:
  Fix Committed
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  Fix Committed
Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Committed
Status in apt source package in Xenial:
  Confirmed
Status in budgie-artwork source package in Xenial:
  Confirmed
Status in kubuntu-settings source package in Xenial:
  Confirmed
Status in plymouth source package in Xenial:
  Fix Committed
Status in ubuntu-gnome-default-settings source package in Xenial:
  Confirmed
Status in ubuntu-mate-artwork source package in Xenial:
  Confirmed
Status in apt source package in Artful:
  Confirmed
Status in budgie-artwork source package in Artful:
  Confirmed
Status in kubuntu-settings source package in Artful:
  Confirmed
Status in plymouth source package in Artful:
  Fix Released
Status in ubuntu-gnome-default-settings source package in Artful:
  Confirmed
Status in ubuntu-mate-artwork source package in Artful:
  Confirmed

Bug description:
  [SRU Justification]
  A package manager bug can cause dist-upgrades from 17.10 to 18.04 to fail 
because of trying to process triggers out of order.  Since the trigger being 
run is that of the currently-installed plymouth package, it is not guaranteed 
to be sufficient to fix the version of the package in 18.04.

  [Test case]
  1. Install plymouth-themes-ubuntu-text from -proposed.
  2. Run a release upgrade with each of update-manager -d, do-release-upgrade 
-d, and apt-get dist-upgrade (the last after manually changing sources.list).
  3. Verify that in each case, the upgrade completes successfully, with no 
errors about out-of-order trigger configuration.

  [Regression potential]
  noawait triggers have been supported in dpkg since 1.16.1, which is older 
than the version in precise 
(https://manpages.debian.org/jessie/dpkg-dev/deb-triggers.5.en.html).  A 
noawait trigger is considered appropriate whenever the triggered package does 
not need to block the triggering package.  There is no reason for a plymouth 
theme package to need to block configuration of an essential package in this 
case.  noawait triggers are well-exercised in the distro now, so the risk of 
regression from this change should be low.

  There is unfortunately not a known reproducer for the original bug, so
  the test case, while it should guard against regressions, is not
  strong confirmation that the bug is fixed.

  [Original description]
  Failure during upgrade attempt from Xubuntu 17.10 to Xubuntu 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu17
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sun Feb 18 23:41:49 2018
  DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-10-24 (118 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  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 1bcf:2c01 Sunplus Innovation Technology Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.5.1
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth
  Title: package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed

[Touch-packages] [Bug 1735415] Re: VNC client does not exits after logout

2018-04-03 Thread Will Cooke

** Changed in: lightdm (Ubuntu Bionic)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  VNC client does not exits after logout

Status in Light Display Manager:
  Fix Committed
Status in lightdm package in Ubuntu:
  New
Status in lightdm source package in Trusty:
  New
Status in lightdm source package in Xenial:
  New
Status in lightdm source package in Zesty:
  New
Status in lightdm source package in Artful:
  New
Status in lightdm source package in Bionic:
  New

Bug description:
  I have setup the remote desktop using the "[VNCServer]" configuration section.
  When I log in using a VNC client and log out with the desktop panel menu,
  the VNC client(remmina) does not exits.

  I found that a VNC connection(TCP 5900) remains alive even though the Xvnc 
server exits.
  I also found the cause, GSocket instance is leaking in the "src/vnc-server.c".

  static gboolean
  read_cb (GSocket *socket, GIOCondition condition, VNCServer *server)
  {
  ...
  client_socket = g_socket_accept (socket, NULL, );
  ...
  if (client_socket)
  {
  ...
  g_signal_emit (server, signals[NEW_CONNECTION], 0, client_socket);
  }
  return TRUE;
  }

  I think that "g_object_unref(client_socket)" should be called after
  g_signal_emit().

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

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

[Touch-packages] [Bug 1751252] Re: ubiquity crashed with signal 5 in _XEventsQueued()

Marking Incomplete for glib per the previous comment.

** Changed in: glib2.0 (Ubuntu Bionic)
   Status: New => Incomplete

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

Title:
  ubiquity crashed with signal 5 in _XEventsQueued()

Status in glib2.0 package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Triaged
Status in glib2.0 source package in Bionic:
  Incomplete
Status in ubiquity source package in Bionic:
  Triaged

Bug description:
  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  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
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1751252/+subscriptions

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

[Touch-packages] [Bug 1746463] Re: apparmor profile load in stacked policy container fails

This bug was fixed in the package linux-gcp - 4.13.0-1012.16

---
linux-gcp (4.13.0-1012.16) xenial; urgency=medium

  * linux-gcp: 4.13.0-1012.16 -proposed tracker (LP: #1755771)

  [ Ubuntu: 4.13.0-38.43 ]

  * linux: 4.13.0-38.43 -proposed tracker (LP: #1755762)
  * Servers going OOM after updating kernel from 4.10 to 4.13 (LP: #1748408)
- i40e: Fix memory leak related filter programming status
- i40e: Add programming descriptors to cleaned_count
  * [SRU] Lenovo E41 Mic mute hotkey is not responding (LP: #1753347)
- platform/x86: ideapad-laptop: Increase timeout to wait for EC answer
  * fails to dump with latest kpti fixes (LP: #1750021)
- kdump: write correct address of mem_section into vmcoreinfo
  * headset mic can't be detected on two Dell machines (LP: #1748807)
- ALSA: hda/realtek - Support headset mode for ALC215/ALC285/ALC289
- ALSA: hda - Fix headset mic detection problem for two Dell machines
- ALSA: hda - Fix a wrong FIXUP for alc289 on Dell machines
  * CIFS SMB2/SMB3 does not work for domain based DFS (LP: #1747572)
- CIFS: make IPC a regular tcon
- CIFS: use tcon_ipc instead of use_ipc parameter of SMB2_ioctl
- CIFS: dump IPC tcon in debug proc file
  * i2c-thunderx: erroneous error message "unhandled state: 0" (LP: #1754076)
- i2c: octeon: Prevent error message on bus error
  * hisi_sas: Add disk LED support (LP: #1752695)
- scsi: hisi_sas: directly attached disk LED feature for v2 hw
  * EDAC, sb_edac: Backport 1 patch to Ubuntu 17.10 (Fix missing DIMM sysfs
entries with KNL SNC2/SNC4 mode) (LP: #1743856)
- EDAC, sb_edac: Fix missing DIMM sysfs entries with KNL SNC2/SNC4 mode
  * [regression] Colour banding and artefacts appear system-wide on an Asus
Zenbook UX303LA with Intel HD 4400 graphics (LP: #1749420)
- drm/edid: Add 6 bpc quirk for CPT panel in Asus UX303LA
  * DVB Card with SAA7146 chipset not working (LP: #1742316)
- vmalloc: fix __GFP_HIGHMEM usage for vmalloc_32 on 32b systems
  * [Asus UX360UA] battery status in unity-panel is not changing when battery is
being charged (LP: #1661876) // AC adapter status not detected on Asus
ZenBook UX410UAK (LP: #1745032)
- ACPI / battery: Add quirk for Asus UX360UA and UX410UAK
  * ASUS UX305LA - Battery state not detected correctly (LP: #1482390)
- ACPI / battery: Add quirk for Asus GL502VSK and UX305LA
  * support thunderx2 vendor pmu events (LP: #1747523)
- perf pmu: Extract function to get JSON alias map
- perf pmu: Pass pmu as a parameter to get_cpuid_str()
- perf tools arm64: Add support for get_cpuid_str function.
- perf pmu: Add helper function is_pmu_core to detect PMU CORE devices
- perf vendor events arm64: Add ThunderX2 implementation defined pmu core
  events
- perf pmu: Add check for valid cpuid in perf_pmu__find_map()
  * lpfc.ko module doesn't work (LP: #1746970)
- scsi: lpfc: Fix loop mode target discovery
  * Ubuntu 17.10 crashes on vmalloc.c (LP: #1739498)
- powerpc/mm/book3s64: Make KERN_IO_START a variable
- powerpc/mm/slb: Move comment next to the code it's referring to
- powerpc/mm/hash64: Make vmalloc 56T on hash
  * ethtool -p fails to light NIC LED on HiSilicon D05 systems (LP: #1748567)
- net: hns: add ACPI mode support for ethtool -p
  * CVE-2017-17807
- KEYS: add missing permission check for request_key() destination
  * [Artful SRU] Fix capsule update regression (LP: #1746019)
- efi/capsule-loader: Reinstate virtual capsule mapping
  * [Artful/Bionic] [Config] enable EDAC_GHES for ARM64 (LP: #1747746)
- Ubuntu: [Config] enable EDAC_GHES for ARM64
  * linux-tools: perf incorrectly linking libbfd (LP: #1748922)
- SAUCE: tools -- add ability to disable libbfd
- [Packaging] correct disablement of libbfd
  * Cherry pick c96f5471ce7d for delayacct fix (LP: #1747769)
- delayacct: Account blkio completion on the correct task
  * Error in CPU frequency reporting when nominal and min pstates are same
(cpufreq) (LP: #1746174)
- cpufreq: powernv: Dont assume distinct pstate values for nominal and pmin
  * retpoline abi files are empty on i386 (LP: #1751021)
- [Packaging] retpoline-extract -- instantiate retpoline files for i386
- [Packaging] final-checks -- sanity checking ABI contents
- [Packaging] final-checks -- check for empty retpoline files
  * [P9,Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping
different pmu events using perf fuzzer . (perf:) (LP: #1746225)
- powerpc/perf: Fix oops when grouping different pmu events
  * bnx2x_attn_int_deasserted3:4323 MC assert! (LP: #1715519) //
CVE-2018-126
- net: create skb_gso_validate_mac_len()
- bnx2x: disable GSO where gso_size is too big for hardware
  * Ubuntu16.04.03: ISAv3 initialize MMU registers before setting partition
table (LP: #1736145)
- powerpc/64s: Initialize ISAv3 MMU registers before setting partition table
  *

[Touch-packages] [Bug 1746463] Re: apparmor profile load in stacked policy container fails

This bug was fixed in the package linux-gcp - 4.13.0-1012.16

---
linux-gcp (4.13.0-1012.16) xenial; urgency=medium

  * linux-gcp: 4.13.0-1012.16 -proposed tracker (LP: #1755771)

  [ Ubuntu: 4.13.0-38.43 ]

  * linux: 4.13.0-38.43 -proposed tracker (LP: #1755762)
  * Servers going OOM after updating kernel from 4.10 to 4.13 (LP: #1748408)
- i40e: Fix memory leak related filter programming status
- i40e: Add programming descriptors to cleaned_count
  * [SRU] Lenovo E41 Mic mute hotkey is not responding (LP: #1753347)
- platform/x86: ideapad-laptop: Increase timeout to wait for EC answer
  * fails to dump with latest kpti fixes (LP: #1750021)
- kdump: write correct address of mem_section into vmcoreinfo
  * headset mic can't be detected on two Dell machines (LP: #1748807)
- ALSA: hda/realtek - Support headset mode for ALC215/ALC285/ALC289
- ALSA: hda - Fix headset mic detection problem for two Dell machines
- ALSA: hda - Fix a wrong FIXUP for alc289 on Dell machines
  * CIFS SMB2/SMB3 does not work for domain based DFS (LP: #1747572)
- CIFS: make IPC a regular tcon
- CIFS: use tcon_ipc instead of use_ipc parameter of SMB2_ioctl
- CIFS: dump IPC tcon in debug proc file
  * i2c-thunderx: erroneous error message "unhandled state: 0" (LP: #1754076)
- i2c: octeon: Prevent error message on bus error
  * hisi_sas: Add disk LED support (LP: #1752695)
- scsi: hisi_sas: directly attached disk LED feature for v2 hw
  * EDAC, sb_edac: Backport 1 patch to Ubuntu 17.10 (Fix missing DIMM sysfs
entries with KNL SNC2/SNC4 mode) (LP: #1743856)
- EDAC, sb_edac: Fix missing DIMM sysfs entries with KNL SNC2/SNC4 mode
  * [regression] Colour banding and artefacts appear system-wide on an Asus
Zenbook UX303LA with Intel HD 4400 graphics (LP: #1749420)
- drm/edid: Add 6 bpc quirk for CPT panel in Asus UX303LA
  * DVB Card with SAA7146 chipset not working (LP: #1742316)
- vmalloc: fix __GFP_HIGHMEM usage for vmalloc_32 on 32b systems
  * [Asus UX360UA] battery status in unity-panel is not changing when battery is
being charged (LP: #1661876) // AC adapter status not detected on Asus
ZenBook UX410UAK (LP: #1745032)
- ACPI / battery: Add quirk for Asus UX360UA and UX410UAK
  * ASUS UX305LA - Battery state not detected correctly (LP: #1482390)
- ACPI / battery: Add quirk for Asus GL502VSK and UX305LA
  * support thunderx2 vendor pmu events (LP: #1747523)
- perf pmu: Extract function to get JSON alias map
- perf pmu: Pass pmu as a parameter to get_cpuid_str()
- perf tools arm64: Add support for get_cpuid_str function.
- perf pmu: Add helper function is_pmu_core to detect PMU CORE devices
- perf vendor events arm64: Add ThunderX2 implementation defined pmu core
  events
- perf pmu: Add check for valid cpuid in perf_pmu__find_map()
  * lpfc.ko module doesn't work (LP: #1746970)
- scsi: lpfc: Fix loop mode target discovery
  * Ubuntu 17.10 crashes on vmalloc.c (LP: #1739498)
- powerpc/mm/book3s64: Make KERN_IO_START a variable
- powerpc/mm/slb: Move comment next to the code it's referring to
- powerpc/mm/hash64: Make vmalloc 56T on hash
  * ethtool -p fails to light NIC LED on HiSilicon D05 systems (LP: #1748567)
- net: hns: add ACPI mode support for ethtool -p
  * CVE-2017-17807
- KEYS: add missing permission check for request_key() destination
  * [Artful SRU] Fix capsule update regression (LP: #1746019)
- efi/capsule-loader: Reinstate virtual capsule mapping
  * [Artful/Bionic] [Config] enable EDAC_GHES for ARM64 (LP: #1747746)
- Ubuntu: [Config] enable EDAC_GHES for ARM64
  * linux-tools: perf incorrectly linking libbfd (LP: #1748922)
- SAUCE: tools -- add ability to disable libbfd
- [Packaging] correct disablement of libbfd
  * Cherry pick c96f5471ce7d for delayacct fix (LP: #1747769)
- delayacct: Account blkio completion on the correct task
  * Error in CPU frequency reporting when nominal and min pstates are same
(cpufreq) (LP: #1746174)
- cpufreq: powernv: Dont assume distinct pstate values for nominal and pmin
  * retpoline abi files are empty on i386 (LP: #1751021)
- [Packaging] retpoline-extract -- instantiate retpoline files for i386
- [Packaging] final-checks -- sanity checking ABI contents
- [Packaging] final-checks -- check for empty retpoline files
  * [P9,Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping
different pmu events using perf fuzzer . (perf:) (LP: #1746225)
- powerpc/perf: Fix oops when grouping different pmu events
  * bnx2x_attn_int_deasserted3:4323 MC assert! (LP: #1715519) //
CVE-2018-126
- net: create skb_gso_validate_mac_len()
- bnx2x: disable GSO where gso_size is too big for hardware
  * Ubuntu16.04.03: ISAv3 initialize MMU registers before setting partition
table (LP: #1736145)
- powerpc/64s: Initialize ISAv3 MMU registers before setting partition table
  *

[Touch-packages] [Bug 1749472] Re: mesa 18.0.0 will cause rendering errors in Qt applications

That tag means we don't track this as a desktop team commitment, please
feel free to still fix the bug though if it's still relevant.

** Tags added: rls-bb-notfixing

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

Title:
  mesa 18.0.0 will cause rendering errors in Qt applications

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

Bug description:
  From: https://bugreports.qt.io/browse/QTBUG-66348

  ** extract **

  The `QOpenGLShaderProgram` class in Qt can be used to compile and link
  OpenGL shaders. If the `GL_ARB_get_program_binary` OpenGL extension is
  available, it can cache those shaders on disk
  (~/.cache/qtshadercache). The i965 driver in Mesa supports this
  extension since version 18.0.0.

  When the shader is loaded using the `glProgramBinary` function, OpenGL
  can refuse it if for example some hardware or software component
  changed. Mesa refuses binaries that were created by any other build of
  Mesa (using among other things the build_id of the library).

  If the shader is refused, Qt should fallback to compiling it from
  sources, but it incorrectly calls glLinkProgram first. The
  glLinkProgram succeeds, because it actually links 0 shaders together.
  That is allowed in OpenGL compatibility profile and the resulting
  program works as a fixed pipeline. Which of course does not render as
  expected.

  This causes rendering errors in Qt applications every time Mesa is
  updated since version 18.0.0. For example white screen in sddm.

  This issue was originally reported in openSUSE
  (https://bugzilla.opensuse.org/show_bug.cgi?id=1080578).

  ** end extract **

  As this potentially effects Qt applications, and could even render
  display manager login unusable, this should be a blocking bug in mesa
  and Qt until Qt mitigations patches pass codereview and can be
  included in Qtbase for 18.04.

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

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

[Touch-packages] [Bug 1760308] Re: Unicode input not working on Bionic with CTRL-SHIFT-U

2018-04-03 Thread Will Cooke

** Also affects: ibus (Ubuntu Bionic)
   Importance: Undecided
   Status: Confirmed

** Changed in: ibus (Ubuntu Bionic)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

** Tags removed: rls-bb-incoming

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

Title:
  Unicode input not working on Bionic with CTRL-SHIFT-U

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

Bug description:
  I need to enter Unicode with Unicode escape codes and the Ubuntu
  prescribed way is to use CTRL-SHIFT-U and then enter some numbers to
  input.  This doesn't do anything in the Ubuntu Bionic beta.

  Potentially related the ALT-TAB window switching is delayed in
  recognizing the occurrence of the keys being pressed such that I have
  to hold ALT-TAB instead of quickly hitting both simultaneously.

  This is from a system that was upgraded from a previous Ubuntu version
  without any issues.

  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  The "Affects" package may not be accurate as I don't know what the
  cause application is for this.

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

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

[Touch-packages] [Bug 1758035] Re: [regression] gnome-shell crashed with SIGTRAP in g_realloc_n() from g_log_structured()

** Changed in: glib2.0 (Ubuntu Bionic)
 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 glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1758035

Title:
  [regression] gnome-shell crashed with SIGTRAP in g_realloc_n() from
  g_log_structured()

Status in glib2.0 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in glib2.0 source package in Bionic:
  Confirmed
Status in gnome-shell source package in Bionic:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/bf61cf0ebedaacbd48f7c12574f551fea3f706c7
  https://errors.ubuntu.com/problem/bc2bd5031309e8cf2314785805634f998452e937
  https://errors.ubuntu.com/problem/f30049f514bf17053fe0461bf2b0890e46ad32dd

  ---

  Freshly installed bionic.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Mar 22 12:22:58 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2018-03-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_realloc_n () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_structured () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
  Title: gnome-shell crashed with signal 5 in g_realloc_n()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1758035/+subscriptions

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

2018-04-03 Thread Sebastien Bacher

the templates were desactivated as well in e.g
https://translations.launchpad.net/ubuntu/bionic/+source/indicator-
power/+pots/indicator-power/+edit for some reason, I re-activated the
indicators and unity ones so those package list translations again

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

Title:
  Use Ubuntu language packs for various indicators

Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in indicator-messages package in Ubuntu:
  Invalid
Status in indicator-power package in Ubuntu:
  Invalid
Status in indicator-session package in Ubuntu:
  Invalid
Status in indicator-sound package in Ubuntu:
  Invalid
Status in unity 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 1760875] Re: systemd-journald crashed with SIGABRT in GI_pthread_timedjoin_ex()

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in systemd package in Ubuntu:
  New

Bug description:
  sudden error

  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: Tue Apr  3 15:48:02 2018
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2018-02-27 (35 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 30A9S01600
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=2737a7da-be91-4d08-94f2-d8a65fb9d133 ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __GI___pthread_timedjoin_ex (threadid=139865973106432, thread_return=0x0, 
abstime=0x0, block=) at pthread_join_common.c:89
   ?? () from /lib/systemd/libsystemd-shared-237.so
   ?? () from /lib/systemd/libsystemd-shared-237.so
   journal_file_append_object () from /lib/systemd/libsystemd-shared-237.so
   ?? () from /lib/systemd/libsystemd-shared-237.so
  Title: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()
  UpgradeStatus: Upgraded to bionic on 2018-04-02 (0 days ago)
  UserGroups:
   
  dmi.bios.date: 03/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A5KT65AUS
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN 2625054126349
  dmi.chassis.type: 7
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrA5KT65AUS:bd03/13/2015:svnLENOVO:pn30A9S01600:pvrThinkStationP700:rvnLENOVO:rnTobefilledbyO.E.M.:rvrSDK0E50510WIN2625054126349:cvnToBeFilledByO.E.M.:ct7:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 30A9S01600
  dmi.product.version: ThinkStation P700
  dmi.sys.vendor: LENOVO

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

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

media-hub is another application that was removed in bionic that is
affected.

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

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

Status in apparmor package in Ubuntu:
  Fix Committed
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 1760117] Re: software-properties-gtk installs canonical-livepatch from edge

2018-04-03 Thread Andrea Azzarone

** Branch unlinked: lp:~azzar1/software-properties/depends-on-keyring

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

Title:
  software-properties-gtk installs canonical-livepatch from edge

Status in software-properties package in Ubuntu:
  In Progress
Status in software-properties source package in Bionic:
  In Progress

Bug description:
  software-properties installs canonical-livepatch from edge. Switch to
  stable before release.

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

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

This isn't a gdm3 bug, right?

If it's a systemd or systemd unit problem and it's still happening, we
probably need to provide some more information so that xnox or someone
can help and take a look. I tried and just booting a live session in a
VM and shutting it down works for me.

Can someone give clear reproduction steps, preferably for making this
happen in a VM?

If it only happens for some people for some reason, maybe an affected
person can get a journal log for this bug report:
https://freedesktop.org/wiki/Software/systemd/Debugging/#index2h1 -
although it'll be a bit harder to get it out of the live session it
should be possible e.g. to mount a hard drive or a USB key or a 9p
shared volume using virt-manager (hopefully that last one works at late
shutdown).

** Changed in: gdm3 (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:
  Confirmed
Status in gdm3 source package in Bionic:
  Incomplete
Status in systemd source package in Bionic:
  Confirmed

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 1760435] Re: Use Ubuntu language packs for various indicators

2018-04-03 Thread Sebastien Bacher

The issue there is/was again that most indicators had translations
sharing enabled in launchpad which means the template was not imported
from the package on upload. I did unset those now but some of the
indicators might need an upload to trigger an import. I uploaded
indicator-sound and hit the build failure from bug #1737834 and
indicator-power which has its template in the import queue now.

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

Title:
  Use Ubuntu language packs for various indicators

Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in indicator-messages package in Ubuntu:
  Invalid
Status in indicator-power package in Ubuntu:
  Invalid
Status in indicator-session package in Ubuntu:
  Invalid
Status in indicator-sound package in Ubuntu:
  Invalid
Status in unity 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 1746463] Re: apparmor profile load in stacked policy container fails

This bug was fixed in the package linux - 4.13.0-38.43

---
linux (4.13.0-38.43) artful; urgency=medium

  * linux: 4.13.0-38.43 -proposed tracker (LP: #1755762)

  * Servers going OOM after updating kernel from 4.10 to 4.13 (LP: #1748408)
- i40e: Fix memory leak related filter programming status
- i40e: Add programming descriptors to cleaned_count

  * [SRU] Lenovo E41 Mic mute hotkey is not responding (LP: #1753347)
- platform/x86: ideapad-laptop: Increase timeout to wait for EC answer

  * fails to dump with latest kpti fixes (LP: #1750021)
- kdump: write correct address of mem_section into vmcoreinfo

  * headset mic can't be detected on two Dell machines (LP: #1748807)
- ALSA: hda/realtek - Support headset mode for ALC215/ALC285/ALC289
- ALSA: hda - Fix headset mic detection problem for two Dell machines
- ALSA: hda - Fix a wrong FIXUP for alc289 on Dell machines

  * CIFS SMB2/SMB3 does not work for domain based DFS (LP: #1747572)
- CIFS: make IPC a regular tcon
- CIFS: use tcon_ipc instead of use_ipc parameter of SMB2_ioctl
- CIFS: dump IPC tcon in debug proc file

  * i2c-thunderx: erroneous error message "unhandled state: 0" (LP: #1754076)
- i2c: octeon: Prevent error message on bus error

  * hisi_sas: Add disk LED support (LP: #1752695)
- scsi: hisi_sas: directly attached disk LED feature for v2 hw

  * EDAC, sb_edac: Backport 1 patch to Ubuntu 17.10 (Fix missing DIMM sysfs
entries with KNL SNC2/SNC4 mode) (LP: #1743856)
- EDAC, sb_edac: Fix missing DIMM sysfs entries with KNL SNC2/SNC4 mode

  * [regression] Colour banding and artefacts appear system-wide on an Asus
Zenbook UX303LA with Intel HD 4400 graphics (LP: #1749420)
- drm/edid: Add 6 bpc quirk for CPT panel in Asus UX303LA

  * DVB Card with SAA7146 chipset not working (LP: #1742316)
- vmalloc: fix __GFP_HIGHMEM usage for vmalloc_32 on 32b systems

  * [Asus UX360UA] battery status in unity-panel is not changing when battery is
being charged (LP: #1661876) // AC adapter status not detected on Asus
ZenBook UX410UAK (LP: #1745032)
- ACPI / battery: Add quirk for Asus UX360UA and UX410UAK

  * ASUS UX305LA - Battery state not detected correctly (LP: #1482390)
- ACPI / battery: Add quirk for Asus GL502VSK and UX305LA

  * support thunderx2 vendor pmu events (LP: #1747523)
- perf pmu: Extract function to get JSON alias map
- perf pmu: Pass pmu as a parameter to get_cpuid_str()
- perf tools arm64: Add support for get_cpuid_str function.
- perf pmu: Add helper function is_pmu_core to detect PMU CORE devices
- perf vendor events arm64: Add ThunderX2 implementation defined pmu core
  events
- perf pmu: Add check for valid cpuid in perf_pmu__find_map()

  * lpfc.ko module doesn't work (LP: #1746970)
- scsi: lpfc: Fix loop mode target discovery

  * Ubuntu 17.10 crashes on vmalloc.c (LP: #1739498)
- powerpc/mm/book3s64: Make KERN_IO_START a variable
- powerpc/mm/slb: Move comment next to the code it's referring to
- powerpc/mm/hash64: Make vmalloc 56T on hash

  * ethtool -p fails to light NIC LED on HiSilicon D05 systems (LP: #1748567)
- net: hns: add ACPI mode support for ethtool -p

  * CVE-2017-17807
- KEYS: add missing permission check for request_key() destination

  * [Artful SRU] Fix capsule update regression (LP: #1746019)
- efi/capsule-loader: Reinstate virtual capsule mapping

  * [Artful/Bionic] [Config] enable EDAC_GHES for ARM64 (LP: #1747746)
- Ubuntu: [Config] enable EDAC_GHES for ARM64

  * linux-tools: perf incorrectly linking libbfd (LP: #1748922)
- SAUCE: tools -- add ability to disable libbfd
- [Packaging] correct disablement of libbfd

  * Cherry pick c96f5471ce7d for delayacct fix (LP: #1747769)
- delayacct: Account blkio completion on the correct task

  * Error in CPU frequency reporting when nominal and min pstates are same
(cpufreq) (LP: #1746174)
- cpufreq: powernv: Dont assume distinct pstate values for nominal and pmin

  * retpoline abi files are empty on i386 (LP: #1751021)
- [Packaging] retpoline-extract -- instantiate retpoline files for i386
- [Packaging] final-checks -- sanity checking ABI contents
- [Packaging] final-checks -- check for empty retpoline files

  * [P9,Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping
different pmu events using perf fuzzer . (perf:) (LP: #1746225)
- powerpc/perf: Fix oops when grouping different pmu events

  * bnx2x_attn_int_deasserted3:4323 MC assert! (LP: #1715519) //
CVE-2018-126
- net: create skb_gso_validate_mac_len()
- bnx2x: disable GSO where gso_size is too big for hardware

  * Ubuntu16.04.03: ISAv3 initialize MMU registers before setting partition
table (LP: #1736145)
- powerpc/64s: Initialize ISAv3 MMU registers before setting partition table

  * powerpc/powernv: Flush console before platform error reboot (LP: #1735159)
-

[Touch-packages] [Bug 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving trig

** Changed in: kubuntu-settings (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  upgrade attempting to process triggers out of order (package plymouth-
  theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed)

Status in apt package in Ubuntu:
  Confirmed
Status in budgie-artwork package in Ubuntu:
  Fix Released
Status in kubuntu-settings package in Ubuntu:
  Fix Committed
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  Fix Committed
Status in ubuntu-mate-artwork package in Ubuntu:
  Confirmed
Status in apt source package in Xenial:
  Confirmed
Status in budgie-artwork source package in Xenial:
  Confirmed
Status in kubuntu-settings source package in Xenial:
  Confirmed
Status in plymouth source package in Xenial:
  Fix Committed
Status in ubuntu-gnome-default-settings source package in Xenial:
  Confirmed
Status in ubuntu-mate-artwork source package in Xenial:
  Confirmed
Status in apt source package in Artful:
  Confirmed
Status in budgie-artwork source package in Artful:
  Confirmed
Status in kubuntu-settings source package in Artful:
  Confirmed
Status in plymouth source package in Artful:
  Fix Released
Status in ubuntu-gnome-default-settings source package in Artful:
  Confirmed
Status in ubuntu-mate-artwork source package in Artful:
  Confirmed

Bug description:
  [SRU Justification]
  A package manager bug can cause dist-upgrades from 17.10 to 18.04 to fail 
because of trying to process triggers out of order.  Since the trigger being 
run is that of the currently-installed plymouth package, it is not guaranteed 
to be sufficient to fix the version of the package in 18.04.

  [Test case]
  1. Install plymouth-themes-ubuntu-text from -proposed.
  2. Run a release upgrade with each of update-manager -d, do-release-upgrade 
-d, and apt-get dist-upgrade (the last after manually changing sources.list).
  3. Verify that in each case, the upgrade completes successfully, with no 
errors about out-of-order trigger configuration.

  [Regression potential]
  noawait triggers have been supported in dpkg since 1.16.1, which is older 
than the version in precise 
(https://manpages.debian.org/jessie/dpkg-dev/deb-triggers.5.en.html).  A 
noawait trigger is considered appropriate whenever the triggered package does 
not need to block the triggering package.  There is no reason for a plymouth 
theme package to need to block configuration of an essential package in this 
case.  noawait triggers are well-exercised in the distro now, so the risk of 
regression from this change should be low.

  There is unfortunately not a known reproducer for the original bug, so
  the test case, while it should guard against regressions, is not
  strong confirmation that the bug is fixed.

  [Original description]
  Failure during upgrade attempt from Xubuntu 17.10 to Xubuntu 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu17
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sun Feb 18 23:41:49 2018
  DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-10-24 (118 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  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 1bcf:2c01 Sunplus Innovation Technology Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.5.1
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth
  Title: package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-02-19 (0 days ago)
  dmi.bios.date: 01/12/2017
  dmi.bios.vendor:

[Touch-packages] [Bug 1760117] Re: software-properties-gtk installs canonical-livepatch from edge

** Branch linked: lp:~azzar1/software-properties/depends-on-keyring

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

Title:
  software-properties-gtk installs canonical-livepatch from edge

Status in software-properties package in Ubuntu:
  In Progress
Status in software-properties source package in Bionic:
  In Progress

Bug description:
  software-properties installs canonical-livepatch from edge. Switch to
  stable before release.

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

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

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

2018-04-03 Thread ChristianEhrhardt

We have another hit of this by memory hot plug (when locked I assume).
I asked the reporters to chime in here.

But even for the former case we had given the time we wait already I want to 
bump the prio.
This is really important to some use cases.

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

-- 
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 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/+source/apparmor/+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 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :

2018-04-03 Thread Eric Desrochers

The sequence of failure seems to be the following:

-- Unit dev-mqueue.mount has failed.
-- Unit sys-kernel-debug.mount has failed.
-- Unit dev-hugepages.mount has failed.
-- Unit sys-kernel-config.mount has failed.
-- Unit sys-fs-fuse-connections.mount has failed.
-- Unit tmp.mount has failed.
-- Unit local-fs.target has failed.
-- Unit dns-clean.service has failed.
-- Unit systemd-resolved.service has failed.
-- Unit systemd-timesyncd.service has failed.
-- Unit sys-kernel-config.mount has failed.
-- Unit sys-fs-fuse-connections.mount has failed.

# journal -xb:
-- The limits controlling how much disk space is used by the journal may
-- be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=,
-- RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in
-- /etc/systemd/journald.conf. See journald.conf(5) for details.
Apr 03 12:59:15 ubuntu systemd-modules-load[758]: Inserted module 'lp'
Apr 03 12:59:15 ubuntu systemd[1]: Failed to set up mount unit: Device or 
resource busy
Apr 03 12:59:15 ubuntu systemd[1]: dev-mqueue.mount: Mount process finished, 
but there is no mount.
Apr 03 12:59:15 ubuntu systemd[1]: dev-mqueue.mount: Failed with result 
'protocol'.
Apr 03 12:59:15 ubuntu systemd[1]: Failed to mount POSIX Message Queue File 
System.
-- Subject: Unit dev-mqueue.mount has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit dev-mqueue.mount has failed.

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

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 73398] Re: crontab in /var/spool/cron/crontabs are stored by username

2018-04-03 Thread Gordon Lack

> A lot of the time, people's login name gets renamed from a central
authority...

Another solution would be to get that policy changed, as it's not a good one.
Such a policy would be a nightmare in any industry that has to track who does 
what for regulatory purposes, where user ids should be constant and unique to 
an individual.

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

Title:
  crontab in /var/spool/cron/crontabs are stored by username

Status in cron package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: cron

  File in /var/spool/cron/crontabs are created with the name of the user
  who owns it when running 'crontab -e'. Their permissions are set
  properly. However, when a user is renamed, his access to these files
  is not properly preserved by the cron system.

  There are two solutions:

  a) name the files with an assigned immutable identifier, specifically the 
POSIX uid
  b) open and locate files by enumerating the owner permission

  Either solution solves the problem. Solution (a) is easier to code and
  leads to less overall confusion on the users (why is foo a file for
  foo2, and foo a file for bar?).

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

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

[Touch-packages] [Bug 1753966] Re: apparmor interfers with saving of PDF from evince

** Package changed: apparmor (Ubuntu) => evince (Ubuntu)

** Tags added: apparmor

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

Title:
  apparmor interfers with saving of PDF from evince

Status in evince package in Ubuntu:
  New

Bug description:
  While trying to save an open PDF from evince, I clicked on the "create
  folder" button in the save dialog. Apparmor prevented directory
  creation in the respective directory. Saving within my "home"
  directory works.

  I consider this a bug. In my case, all user data resides in a separate
  data partition. With the current apparmor profiles, saving to this
  partition is hindered.

  Syslog contains:

  Mar  7 10:29:33 xxx kernel: [ 4569.159240] audit: type=1400
  audit(1520414973.202:39): apparmor="DENIED" operation="mkdir"
  profile="/usr/bin/evince" name="x" pid=5393 comm="evince"
  requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000

  More generally, this seems to apply to a whole set of apparmor
  profiles that were updated or added recently...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apparmor-profiles (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar  7 10:32:37 2018
  InstallationDate: Installed on 2017-12-01 (95 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=5c73304c-cd10-4645-99c9-2cf07aa48894 ro nosplash
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

** Changed in: apparmor (Ubuntu)
   Status: Won't Fix => In Progress

** Changed in: apparmor (Ubuntu)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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:
  In Progress
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 1758841] Re: virt-manager: Light grey menu items on light grey background are barely readable

2018-04-03 Thread ChristianEhrhardt

Setting virt-manager low, until we have a reason to assume that a fix it
would be better than a fix in the Theme (that would also fix anything
else that is affected).

This is too deep in /usr/share/themes/Ambiance for me to spot all the
right and wrong entries.

And sorry, the theme I meant obviously is Ambiance (with an a).

Since this is part of ubuntu-themes and a task already is filed against
that we can wait for the Desktop/Theme folks to comment.

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

Title:
  virt-manager: Light grey menu items on light grey background are
  barely readable

Status in Ubuntu theme:
  New
Status in ubuntu-themes package in Ubuntu:
  New
Status in virt-manager package in Ubuntu:
  Confirmed

Bug description:
  With latest update of ubuntu-theme (16.10+18.04.20180322.3-0ubuntu1) menu 
items in the toolbar are barely readable (cf screenshot)
  Background should be dark. virt-manager is the only application I found with 
this issue so far.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: virt-manager 1:1.5.0-0ubuntu1
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 26 09:50:17 2018
  InstallationDate: Installed on 2014-07-15 (1349 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  PackageArchitecture: all
  SourcePackage: virt-manager
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (1 days ago)

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

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

[Touch-packages] [Bug 1303649] Re: systemd-logind spins in cgmanager_ping_sync()

2018-04-03 Thread Guilherme G. Piccoli

Folks that are experiencing this issue: the best way to circumvent it
for now I guess it's downgrade systemd package to version
204-5ubuntu20.26 and remove cgmanager.

To remove cgmanager: "sudo apt-get remove cgmanager"

To downgrade systemd version: "sudo apt-get install systemd-
services=204-5ubuntu20.26 libsystemd-login0=204-5ubuntu20.26 libsystemd-
daemon0=204-5ubuntu20.26  libpam-systemd=204-5ubuntu20.26
libudev1=204-5ubuntu20.26 udev=204-5ubuntu20.26"

The version 204-5ubuntu20.26 is in the official repos, so no need to
download manually deb packages and whatnot; the proposed 20.27 version
should be removed for now.

Thanks,


Guilherme

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

Title:
  systemd-logind spins in cgmanager_ping_sync()

Status in cgmanager package in Ubuntu:
  Invalid
Status in libnih package in Ubuntu:
  Invalid
Status in lxc package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  systemd-logind is consuming a high level of cpu on a continual basis:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
 
676 root  20   0   43644   2144   1568 R 100.0  0.0  74:43.77 
systemd-logind

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: systemd-services 204-5ubuntu17
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr  7 09:09:37 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-04-23 (348 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to trusty on 2013-11-11 (146 days ago)

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

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

[Touch-packages] [Bug 1312267] Re: apt-add-repository, gpg, wget does not honour proxy inside sudo