date:20180321

Public bug reported:

Currently Qt 4 has been dead upstream and we are starting to have
problems maintaining it, like for example in the OpenSSL 1.1 support
case.

Following in the footsteps of Debian[1], all packages directly or
indirectly depending on qt4-x11 (like this one) must either get ported
to Qt 5 and uploaded to the development release or get removed (by means
of demotion to -proposed or removal of the package) before the 19.04
release. If it is possible to port your package by the 18.10 release,
please do so.

If you have any questions about porting or this transition, please ask
in #ubuntu-qt (preferred) or directly ping me

[1] https://wiki.debian.org/Qt4Removal

** Affects: autopilot-qt (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: qt4-removal

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

Title:
  Please port your package away from Qt 4

Status in autopilot-qt package in Ubuntu:
  New

Bug description:
  Currently Qt 4 has been dead upstream and we are starting to have
  problems maintaining it, like for example in the OpenSSL 1.1 support
  case.

  Following in the footsteps of Debian[1], all packages directly or
  indirectly depending on qt4-x11 (like this one) must either get ported
  to Qt 5 and uploaded to the development release or get removed (by
  means of demotion to -proposed or removal of the package) before the
  19.04 release. If it is possible to port your package by the 18.10
  release, please do so.

  If you have any questions about porting or this transition, please ask
  in #ubuntu-qt (preferred) or directly ping me

  [1] https://wiki.debian.org/Qt4Removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopilot-qt/+bug/1757600/+subscriptions

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

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

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

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

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

Status in Mesa:
  Confirmed
Status in gdm3 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  In Progress
Status in wayland package in Ubuntu:
  Invalid
Status in gdm3 source package in Bionic:
  Invalid
Status in mesa source package in Bionic:
  In Progress
Status in wayland source package in Bionic:
  Invalid

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

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

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

[Touch-packages] [Bug 1757625] [NEW] Please port your package away from Qt 4

Public bug reported:

Currently Qt 4 has been dead upstream and we are starting to have
problems maintaining it, like for example in the OpenSSL 1.1 support
case.

Following in the footsteps of Debian[1], all packages directly or
indirectly depending on qt4-x11 (like this one) must either get ported
to Qt 5 and uploaded to the development release or get removed (by means
of demotion to -proposed or removal of the package) before the 19.04
release. If it is possible to port your package by the 18.10 release,
please do so.

If you have any questions about porting or this transition, please ask
in #ubuntu-qt (preferred) or directly ping me

[1] https://wiki.debian.org/Qt4Removal

** Affects: dee-qt (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: qt4-removal

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

Title:
  Please port your package away from Qt 4

Status in dee-qt package in Ubuntu:
  New

Bug description:
  Currently Qt 4 has been dead upstream and we are starting to have
  problems maintaining it, like for example in the OpenSSL 1.1 support
  case.

  Following in the footsteps of Debian[1], all packages directly or
  indirectly depending on qt4-x11 (like this one) must either get ported
  to Qt 5 and uploaded to the development release or get removed (by
  means of demotion to -proposed or removal of the package) before the
  19.04 release. If it is possible to port your package by the 18.10
  release, please do so.

  If you have any questions about porting or this transition, please ask
  in #ubuntu-qt (preferred) or directly ping me

  [1] https://wiki.debian.org/Qt4Removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dee-qt/+bug/1757625/+subscriptions

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

[Touch-packages] [Bug 1757467] Re: [kubuntu] No window borders around gnumeric program with wayland

It's a KDE/Kubuntu bug only. Not a bug in the Wayland protocol, and not
a bug in Gnome Shell.

** Summary changed:

- no windows arround gnumeric program with wayland
+ [kubuntu] No window borders around gnumeric program with wayland

** Package changed: wayland (Ubuntu) => kubuntu-meta (Ubuntu)

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

Title:
  [kubuntu] No window borders around gnumeric program with wayland

Status in kubuntu-meta package in Ubuntu:
  New

Bug description:
  Sorry, english is not my native langage.

  I use gnumeric on a platform with kubuntu 18.04 (beta1) ant plasma
  5.12.3.

  Using plasma session, all seems ok.

  Using plasma WAYLAND session, gnumeric have no "windows" arround the
  program. So i can't change the size and to close gnumeric, I have to
  use the main menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1757467/+subscriptions

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

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

** Changed in: kubuntu-settings (Ubuntu Artful)
   Status: New => Confirmed

-- 
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:
  Confirmed
Status in kubuntu-settings package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  Confirmed
Status in ubuntu-mate-artwork package in Ubuntu:
  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 Committed
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 artful-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: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 01W6F7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd01/12/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr:

[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

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

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

-- 
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:
  Confirmed
Status in kubuntu-settings package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  Confirmed
Status in ubuntu-mate-artwork package in Ubuntu:
  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 Committed
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 artful-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: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 01W6F7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd01/12/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr:

[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

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

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

-- 
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:
  Confirmed
Status in kubuntu-settings package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  Confirmed
Status in ubuntu-mate-artwork package in Ubuntu:
  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 Committed
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 artful-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: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 01W6F7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd01/12/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr:

[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

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

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

-- 
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:
  Confirmed
Status in kubuntu-settings package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  Confirmed
Status in ubuntu-mate-artwork package in Ubuntu:
  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 Committed
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 artful-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: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 01W6F7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd01/12/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr:

[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

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

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

-- 
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:
  Confirmed
Status in kubuntu-settings package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  Confirmed
Status in ubuntu-mate-artwork package in Ubuntu:
  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 Committed
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 artful-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: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 01W6F7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd01/12/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr:

[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

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

** Changed in: ubuntu-mate-artwork (Ubuntu Artful)
   Status: New => Confirmed

-- 
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:
  Confirmed
Status in kubuntu-settings package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  Confirmed
Status in ubuntu-mate-artwork package in Ubuntu:
  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 Committed
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 artful-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: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 01W6F7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd01/12/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr:

[Touch-packages] [Bug 1757463] Re: The "Minimize", " Maximize" and "Close" buttons are too small to click

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

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


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

** This bug has been marked a duplicate of bug 1693609
   The "Minimize", " Maximize" and "Close" buttons are too small to click

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

Title:
  The "Minimize", " Maximize" and "Close"  buttons are too small to
  click

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

Bug description:
  When using the default Ambiance theme on a 13 inch laptop with
  resolution 1920x1080. Everything looks fine except these three
  buttons.They are too small and hard to click by the mouse. I have to
  move the mouse carefully to avoid clicking the wrong place

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

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

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

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

-- 
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:
  Confirmed
Status in kubuntu-settings package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  Confirmed
Status in ubuntu-mate-artwork package in Ubuntu:
  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 Committed
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 artful-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: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 01W6F7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd01/12/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family:

[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

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

** Changed in: budgie-artwork (Ubuntu)
   Status: New => Confirmed

-- 
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:
  Confirmed
Status in kubuntu-settings package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  Confirmed
Status in ubuntu-mate-artwork package in Ubuntu:
  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 Committed
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 artful-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: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 01W6F7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd01/12/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family:

[Touch-packages] [Bug 1693609] Re: The "Minimize", " Maximize" and "Close" buttons are too small to click

** Summary changed:

- Please make window control buttons larger
+ The "Minimize", " Maximize" and "Close" buttons are too small to click

** Changed in: ubuntu-ux
   Status: New => Confirmed

** Changed in: ubuntu-themes (Ubuntu)
 Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned)

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

Title:
  The "Minimize", " Maximize" and "Close" buttons are too small to click

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

Bug description:
  The window control buttons ( _  X ) in Ambiance are noticeably
  smaller than other icon buttons in the headerbar of a "native" GNOME3
  app.

  I think this is both a visual issue and an accessibility issue since
  it is harder to click the window control buttons than the other
  buttons. Please compare with Adwaita which has a much larger click
  area for the window control buttons.

  Commentary
  --
  Remember that one of the major strengths of GNOME 3 is that it is usable on a 
touch-enabled laptop.

  And while there are many people that complain about Adwaita, I believe
  many more actually like the proportions and padding of the default
  GNOME theme!

  ubuntu-themes  16.10+17.10.20170518-0ubuntu1
  Ubuntu 17.10 Alpha

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

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

[Touch-packages] [Bug 1757320] Re: Remove Qt 4 from the archive

Instead of filing one megabug, I filed separate bugs:
https://bugs.launchpad.net/ubuntu/+bugs?field.tag=qt4-removal

Thanks.

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

Title:
  Remove Qt 4 from the archive

Status in qt4-x11 package in Ubuntu:
  New

Bug description:
  Currently Qt 4 has been dead upstream and we are starting to have
  problems maintaining it, like for example in the OpenSSL 1.1 support case.

  Following in the footsteps of Debian[1], all packages directly or
  indirectly depending on qt4-x11 must either get ported to Qt 5 and
  uploaded to the development release or get removed (by means of demotion
  to -proposed or the whole source package removal) before the 19.04
  release. If it is possible to do this by the 18.10 release, please do so.

  No new packages entering the Ubuntu archive should depend on qt4-x11 or
  any package which directly or indirectly depends on it.

  [1] https://wiki.debian.org/Qt4Removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1757320/+subscriptions

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

[Touch-packages] [Bug 1757884] [NEW] Please port your package away from Qt 4

Public bug reported:

Currently Qt 4 has been dead upstream and we are starting to have
problems maintaining it, like for example in the OpenSSL 1.1 support
case.

Following in the footsteps of Debian[1], all packages directly or
indirectly depending on qt4-x11 (like this one) must either get ported
to Qt 5 and uploaded to the development release or get removed (by means
of demotion to -proposed or removal of the package) before the 19.04
release. If it is possible to port your package by the 18.10 release,
please do so.

If you have any questions about porting or this transition, please ask
in #ubuntu-qt (preferred) or directly ping me

[1] https://wiki.debian.org/Qt4Removal

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


** Tags: qt4-removal

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

Title:
  Please port your package away from Qt 4

Status in syncevolution package in Ubuntu:
  New

Bug description:
  Currently Qt 4 has been dead upstream and we are starting to have
  problems maintaining it, like for example in the OpenSSL 1.1 support
  case.

  Following in the footsteps of Debian[1], all packages directly or
  indirectly depending on qt4-x11 (like this one) must either get ported
  to Qt 5 and uploaded to the development release or get removed (by
  means of demotion to -proposed or removal of the package) before the
  19.04 release. If it is possible to port your package by the 18.10
  release, please do so.

  If you have any questions about porting or this transition, please ask
  in #ubuntu-qt (preferred) or directly ping me

  [1] https://wiki.debian.org/Qt4Removal

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

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

[Touch-packages] [Bug 1757901] [NEW] Lubuntu 18.04 Daily: Can't configure printers

2018-03-21 Thread Bill Miller

Public bug reported:

When I try to start System Tools / Printers it spins for a while and
goes away.

When I try it from the command line it crashes with a python error

$ system-config-printer

** (system-config-printer.py:2913): WARNING **: 21:05:20.121: Error retrieving 
accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.a11y.Bus was not provided by any .service files
Traceback (most recent call last):
  File "/usr/share/system-config-printer/system-config-printer.py", line 84, in 

import jobviewer
  File "/usr/share/system-config-printer/jobviewer.py", line 76, in 
NETWORK_PASSWORD = Secret.Schema.new("org.system.config.printer.store", 
Secret.SchemaFlags.NONE,
NameError: name 'Secret' is not defined

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cups 2.2.6-5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic i686
ApportVersion: 2.20.8-0ubuntu10
Architecture: i386
CurrentDesktop: LXDE
Date: Wed Mar 21 21:04:35 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-03-21 (0 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha i386 (20180306.1)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
Papersize: letter
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=7b9a7261-d27a-4a8c-8430-e9802720ae0f ro quiet splash
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

** Affects: system-config-printer (Ubuntu)
 Importance: Undecided
 Status: New


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

** Also affects: cups
   Importance: Undecided
   Status: New

** Also affects: system-config-printer (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: cups (Ubuntu)

** No longer affects: cups

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

Title:
  Lubuntu 18.04 Daily: Can't configure printers

Status in system-config-printer package in Ubuntu:
  New

Bug description:
  When I try to start System Tools / Printers it spins for a while and
  goes away.

  When I try it from the command line it crashes with a python error

  $ system-config-printer

  ** (system-config-printer.py:2913): WARNING **: 21:05:20.121: Error 
retrieving accessibility bus address: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not 
provided by any .service files
  Traceback (most recent call last):
File "/usr/share/system-config-printer/system-config-printer.py", line 84, 
in 
  import jobviewer
File "/usr/share/system-config-printer/jobviewer.py", line 76, in 
  NETWORK_PASSWORD = Secret.Schema.new("org.system.config.printer.store", 
Secret.SchemaFlags.NONE,
  NameError: name 'Secret' is not defined

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.6-5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic i686
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Wed Mar 21 21:04:35 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-03-21 (0 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha i386 (20180306.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=7b9a7261-d27a-4a8c-8430-e9802720ae0f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias:

[Touch-packages] [Bug 1757915] [NEW] Please port your package away from Qt 4

Public bug reported:

Currently Qt 4 has been dead upstream and we are starting to have
problems maintaining it, like for example in the OpenSSL 1.1 support
case.

Following in the footsteps of Debian[1], all packages directly or
indirectly depending on qt4-x11 (like this one) must either get ported
to Qt 5 and uploaded to the development release or get removed (by means
of demotion to -proposed or removal of the package) before the 19.04
release. If it is possible to port your package by the 18.10 release,
please do so.

If you have any questions about porting or this transition, please ask
in #ubuntu-qt (preferred) or directly ping me

[1] https://wiki.debian.org/Qt4Removal

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


** Tags: qt4-removal

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

Title:
  Please port your package away from Qt 4

Status in zbar package in Ubuntu:
  New

Bug description:
  Currently Qt 4 has been dead upstream and we are starting to have
  problems maintaining it, like for example in the OpenSSL 1.1 support
  case.

  Following in the footsteps of Debian[1], all packages directly or
  indirectly depending on qt4-x11 (like this one) must either get ported
  to Qt 5 and uploaded to the development release or get removed (by
  means of demotion to -proposed or removal of the package) before the
  19.04 release. If it is possible to port your package by the 18.10
  release, please do so.

  If you have any questions about porting or this transition, please ask
  in #ubuntu-qt (preferred) or directly ping me

  [1] https://wiki.debian.org/Qt4Removal

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

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

[Touch-packages] [Bug 1757730] [NEW] Please port your package away from Qt 4

Public bug reported:

Currently Qt 4 has been dead upstream and we are starting to have
problems maintaining it, like for example in the OpenSSL 1.1 support
case.

Following in the footsteps of Debian[1], all packages directly or
indirectly depending on qt4-x11 (like this one) must either get ported
to Qt 5 and uploaded to the development release or get removed (by means
of demotion to -proposed or removal of the package) before the 19.04
release. If it is possible to port your package by the 18.10 release,
please do so.

If you have any questions about porting or this transition, please ask
in #ubuntu-qt (preferred) or directly ping me

[1] https://wiki.debian.org/Qt4Removal

** Affects: libdbusmenu-qt (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: qt4-removal

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

Title:
  Please port your package away from Qt 4

Status in libdbusmenu-qt package in Ubuntu:
  New

Bug description:
  Currently Qt 4 has been dead upstream and we are starting to have
  problems maintaining it, like for example in the OpenSSL 1.1 support
  case.

  Following in the footsteps of Debian[1], all packages directly or
  indirectly depending on qt4-x11 (like this one) must either get ported
  to Qt 5 and uploaded to the development release or get removed (by
  means of demotion to -proposed or removal of the package) before the
  19.04 release. If it is possible to port your package by the 18.10
  release, please do so.

  If you have any questions about porting or this transition, please ask
  in #ubuntu-qt (preferred) or directly ping me

  [1] https://wiki.debian.org/Qt4Removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1757730/+subscriptions

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

[Touch-packages] [Bug 1757747] [NEW] Please port your package away from Qt 4

Public bug reported:

Currently Qt 4 has been dead upstream and we are starting to have
problems maintaining it, like for example in the OpenSSL 1.1 support
case.

Following in the footsteps of Debian[1], all packages directly or
indirectly depending on qt4-x11 (like this one) must either get ported
to Qt 5 and uploaded to the development release or get removed (by means
of demotion to -proposed or removal of the package) before the 19.04
release. If it is possible to port your package by the 18.10 release,
please do so.

If you have any questions about porting or this transition, please ask
in #ubuntu-qt (preferred) or directly ping me

[1] https://wiki.debian.org/Qt4Removal

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


** Tags: qt4-removal

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

Title:
  Please port your package away from Qt 4

Status in lightdm package in Ubuntu:
  New

Bug description:
  Currently Qt 4 has been dead upstream and we are starting to have
  problems maintaining it, like for example in the OpenSSL 1.1 support
  case.

  Following in the footsteps of Debian[1], all packages directly or
  indirectly depending on qt4-x11 (like this one) must either get ported
  to Qt 5 and uploaded to the development release or get removed (by
  means of demotion to -proposed or removal of the package) before the
  19.04 release. If it is possible to port your package by the 18.10
  release, please do so.

  If you have any questions about porting or this transition, please ask
  in #ubuntu-qt (preferred) or directly ping me

  [1] https://wiki.debian.org/Qt4Removal

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

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

[Touch-packages] [Bug 1750947] Re: pulseaudio print lots of error when selecting unavailable profile

2018-03-21 Thread Hui Wang

@Robie,

Updated [Regression Potential] as shown below:

The patch will check all ports under each profile, if a profile only
contains unavailable ports, this profile will be set to unavailable as
well. Without this patch, all profiles are always available, then if a
profile includes a unusable hdmi-output, and pulseaudio choose this
profile to be active (since its priority is the highest), the kernel
audio driver will crash.

I think this patch will not introduce regression:
1) It is a correct logic to set a profile to be unavailable if it only contains 
unavailable ports.
2) pulseaudio-artful and pulseaudio-bionic already include this patch, they 
work very well
3) I tested this patch on 1 lenovo laptop, 1 lenovo desktop, 1 dell laptop and 
1 dell desktop, all worked well as before
4) tested this patch on two dell machines (LOAD5-DVT2-A2 and Dawson-JC-C 
without analogue audio) which have unusable hdmi-output profile on them, the 
kernel driver did not crash anymore and audio function worked very well.


** Description changed:

  SRU Document:
  
  [Impact]
  
  A HDMI audio device usually has several output ports, each port
  represents a profile in pulseaudio, without this patch, the puseaudio
  always choose the first profile no matter it is active or not.
  
  [Test Case]
  
  connect each port of HDMI device, and check if the profile of that port
  is active or not.
  
  [Regression Potential]
  
- no regression possibility, since this commit is already in artful and
- bionic.
+ The patch will check all ports under each profile, if a profile only
+ contains unavailable ports, this profile will be set to unavailable as
+ well. Without this patch, all profiles are always available, then if a
+ profile includes a unusable hdmi-output, and pulseaudio select this
+ profile to be active (since its priority is the highest), the kernel
+ audio driver will crash.
+ 
+ I think this patch will not introduce regression:
+ 1) It is a correct logic to set a profile to be unavailable if it only 
contains unavailable ports.
+ 2) pulseaudio-artful and pulseaudio-bionic already include this patch, they 
work very well
+ 3) I tested this patch on 1 lenovo laptop, 1 lenovo desktop, 1 dell laptop 
and 1 dell desktop, all worked well as before
+ 4) tested this patch on two dell machines (LOAD5-DVT2-A2 and Dawson-JC-C 
without analogue audio) which have unusable hdmi-output profile on them, the 
kernel driver did not crash anymore and audio function worked very well.
  
  [Other Info]
  
  Only pulseaudio-xenial has this problem.
  
  we need to backport this commit to pulseaudio-xenial.
  
  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4
  
  After printing out the error logs, the kernel crashes and system hangs.

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

Title:
  pulseaudio print lots of error when selecting unavailable profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  New

Bug description:
  SRU Document:

  [Impact]

  A HDMI audio device usually has several output ports, each port
  represents a profile in pulseaudio, without this patch, the puseaudio
  always choose the first profile no matter it is active or not.

  [Test Case]

  connect each port of HDMI device, and check if the profile of that
  port is active or not.

  [Regression Potential]

  The patch will check all ports under each profile, if a profile only
  contains unavailable ports, this profile will be set to unavailable as
  well. Without this patch, all profiles are always available, then if a
  profile includes a unusable hdmi-output, and pulseaudio select this
  profile to be active (since its priority is the highest), the kernel
  audio driver will crash.

  I think this patch will not introduce regression:
  1) It is a correct logic to set a profile to be unavailable if it only 
contains unavailable ports.
  2) pulseaudio-artful and pulseaudio-bionic already include this patch, they 
work very well
  3) I tested this patch on 1 lenovo laptop, 1 lenovo desktop, 1 dell laptop 
and 1 dell desktop, all worked well as before
  4) tested this patch on two dell machines (LOAD5-DVT2-A2 and Dawson-JC-C 
without analogue audio) which have unusable hdmi-output profile on them, the 
kernel driver did not crash anymore and audio function worked very well.

  [Other Info]

  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

  After printing out the error logs, the kernel crashes and system
  hangs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1750947/+subscriptions

-- 
Mailing

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

Alex,

You shouldn't ever have to run synclient manually again. See comment
#36:

"Once you know the synclient syntax you want you can apply it
automatically at login by running 'gnome-session-properties'."

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

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

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

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

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

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

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

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

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

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

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

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

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

This bug was fixed in the package update-manager - 1:18.04.9

---
update-manager (1:18.04.9) bionic; urgency=medium

  * Keep PEP 8 checks happy

 -- Balint Reczey   Wed, 21 Mar 2018 17:53:59 +

** Changed in: update-manager (Ubuntu)
   Status: In Progress => Fix Released

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

Bug description:
  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 : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1757577] [NEW] Unclaimed AR5416 Wireless Network Adapter

2018-03-21 Thread Michael Heuberger

Public bug reported:

On my latest Ubuntu 17.10 I am unable to use my WiFi, only Ethernet.
Didn't happen before I upgraded from 16.10.

The `sudo lshw -C network` command tells me the AR5416 Wireless Network
Adapter is UNCLAIMED:

```
└─❱❱❱ sudo lshw -C network
  *-network
   description: Ethernet interface
   product: 88E8056 PCI-E Gigabit Ethernet Controller
   vendor: Marvell Technology Group Ltd.
   physical id: 0
   bus info: pci@:05:00.0
   logical name: eth0
   version: 12
   serial: f4:6d:04:00:dc:74
   size: 100Mbit/s
   capacity: 1Gbit/s
   width: 64 bits
   clock: 33MHz
   capabilities: pm vpd msi pciexpress bus_master cap_list rom
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd
autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=sky2
driverversion=1.30 duplex=full ip=192.168.2.10 latency=0 link=yes
multicast=yes port=twisted pair speed=100Mbit/s
   resources: irq:35 memory:fbdfc000-fbdf ioport:d800(size=256)
memory:fbdc-fbdd
  *-network UNCLAIMED
   description: Network controller
   product: AR5416 Wireless Network Adapter [AR5008 802.11(a)bgn]
   vendor: Qualcomm Atheros
   physical id: 1
   bus info: pci@:07:01.0
   version: 01
   width: 32 bits
   clock: 66MHz
   capabilities: cap_list
   configuration: latency=168
```

Here few more useful info from other commands

```

└─❱❱❱ iwconfig
lono wireless extensions.
eth0  no wireless extensions.

└─❱❱❱ lspci -vnn | grep Network
07:01.0 Network controller [0280]: Qualcomm Atheros AR5416 Wireless
Network Adapter [AR5008 802.11(a)bgn] [168c:0023] (rev 01)
Subsystem: Qualcomm Atheros AR5416 Wireless Network Adapter [AR5008
802.11(a)bgn] [168c:3071]
```

and yes, dmesg tells me initialisation of that device failed during
startup:


```
└─❱❱❱ dmesg | grep ath
...
[   25.700597] ath: phy0: address test failed addr: 0x8000 -
wr:0x != rd:0x0100
[   25.758375] ath: phy0: Unable to initialize hardware; initialization
status: -19
[   25.814677] ath9k :07:01.0: Failed to initialize device
[ .517258] ath9k: ath9k: Driver unloaded
```

Any clues what this could be? Any hints very much appreciated! Thanks
guys

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

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

Title:
  Unclaimed AR5416 Wireless Network Adapter

Status in network-manager package in Ubuntu:
  New

Bug description:
  On my latest Ubuntu 17.10 I am unable to use my WiFi, only Ethernet.
  Didn't happen before I upgraded from 16.10.

  The `sudo lshw -C network` command tells me the AR5416 Wireless
  Network Adapter is UNCLAIMED:

  ```
  └─❱❱❱ sudo lshw -C network
*-network
 description: Ethernet interface
 product: 88E8056 PCI-E Gigabit Ethernet Controller
 vendor: Marvell Technology Group Ltd.
 physical id: 0
 bus info: pci@:05:00.0
 logical name: eth0
 version: 12
 serial: f4:6d:04:00:dc:74
 size: 100Mbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm vpd msi pciexpress bus_master cap_list rom
  ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd
  autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=sky2
  driverversion=1.30 duplex=full ip=192.168.2.10 latency=0 link=yes
  multicast=yes port=twisted pair speed=100Mbit/s
 resources: irq:35 memory:fbdfc000-fbdf ioport:d800(size=256)
  memory:fbdc-fbdd
*-network UNCLAIMED
 description: Network controller
 product: AR5416 Wireless Network Adapter [AR5008 802.11(a)bgn]
 vendor: Qualcomm Atheros
 physical id: 1
 bus info: pci@:07:01.0
 version: 01
 width: 32 bits
 clock: 66MHz
 capabilities: cap_list
 configuration: latency=168
  ```

  Here few more useful info from other commands

  ```

  └─❱❱❱ iwconfig
  lono wireless extensions.
  eth0  no wireless extensions.

  └─❱❱❱ lspci -vnn | grep Network
  07:01.0 Network controller [0280]: Qualcomm Atheros AR5416 Wireless
  Network Adapter [AR5008 802.11(a)bgn] [168c:0023] (rev 01)
  Subsystem: Qualcomm Atheros AR5416 Wireless Network Adapter [AR5008
  802.11(a)bgn] [168c:3071]
  ```

  and yes, dmesg tells me initialisation of that device failed during
  startup:

  
  ```
  └─❱❱❱ dmesg | grep ath
  ...
  [   25.700597] ath: phy0: address test failed addr: 0x8000 -
  wr:0x != rd:0x0100
  [   25.758375] ath: phy0: Unable to initialize hardware; initialization
  status: -19
  [   25.814677] ath9k :07:01.0: Failed to initialize device
  [

[Touch-packages] [Bug 1385709] Re: network-manager service doesn't start at boot time

2018-03-21 Thread helpdeskdan

$ sudo ls -l /usr/share/sendmail/dynamic
ls: cannot access '/usr/share/sendmail/dynamic': No such file or directory


Thank you Romain, hopefully this can be fixed.

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

Title:
  network-manager service doesn't start at boot time

Status in network-manager package in Ubuntu:
  Confirmed
Status in sendmail package in Ubuntu:
  Confirmed

Bug description:
  I just completed the upgrade from Kubuntu 14.04 to 14.10. Haven't had
  any network trouble before the upgrade. After the upgrade, the
  network-manager service does not start when the computer boots up -
  the Kubuntu splash screen says 'waiting for network configuration',
  then 'waiting another 60 seconds for network configuration' (or
  something like that), then finally boots up without a network
  connection. Also the Network Management tray icon tooltip says that
  the network-manager service is not running. However if I then manually
  open the terminal and run 'sudo service network-manager start', then
  it starts ok and the network connects within a few seconds and
  everything works ok until the next reboot. I'm on a desktop PC with a
  wired LAN connection and no wifi adapter. network-manager version is
  0.9.8.8-0ubuntu28.

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

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

[Touch-packages] [Bug 1757320] Re: Remove Qt 4 from the archive

2018-03-21 Thread William Grant

** No longer affects: adwaita-qt (Ubuntu)

** No longer affects: akonadi4 (Ubuntu)

** No longer affects: alsoft-conf (Ubuntu)

** No longer affects: alt-key (Ubuntu)

** No longer affects: amarok (Ubuntu)

** No longer affects: amora-server (Ubuntu)

** No longer affects: ams (Ubuntu)

** No longer affects: analitza4 (Ubuntu)

** No longer affects: appmenu-qt (Ubuntu)

** No longer affects: aseba (Ubuntu)

** No longer affects: attal (Ubuntu)

** No longer affects: attica (Ubuntu)

** No longer affects: auralquiz (Ubuntu)

** No longer affects: automoc (Ubuntu)

** No longer affects: autopilot-qt (Ubuntu)

** No longer affects: avogadro (Ubuntu)

** No longer affects: bacula (Ubuntu)

** No longer affects: ball (Ubuntu)

** No longer affects: baloo (Ubuntu)

** No longer affects: basket (Ubuntu)

** No longer affects: boats (Ubuntu)

** No longer affects: bodega-client (Ubuntu)

** No longer affects: bppphyview (Ubuntu)

** No longer affects: breeze (Ubuntu)

** No longer affects: cagibi (Ubuntu)

** No longer affects: cdcat (Ubuntu)

** No longer affects: chinese-calendar (Ubuntu)

** No longer affects: choreonoid (Ubuntu)

** No longer affects: clementine (Ubuntu)

** No longer affects: cmtk (Ubuntu)

** No longer affects: codelite (Ubuntu)

** No longer affects: codequery (Ubuntu)

** No longer affects: collatinus (Ubuntu)

** No longer affects: colord-kde (Ubuntu)

** No longer affects: connectome-workbench (Ubuntu)

** No longer affects: cortina (Ubuntu)

** No longer affects: cppreference-doc (Ubuntu)

** No longer affects: daemonfs (Ubuntu)

** No longer affects: dc-qt (Ubuntu)

** No longer affects: dee-qt (Ubuntu)

** No longer affects: dgedit (Ubuntu)

** No longer affects: dhcpcd-ui (Ubuntu)

** No longer affects: doomsday (Ubuntu)

** No longer affects: dssi (Ubuntu)

** No longer affects: enki-aseba (Ubuntu)

** No longer affects: eqonomize (Ubuntu)

** No longer affects: esperanza (Ubuntu)

** No longer affects: fbreader (Ubuntu)

** No longer affects: fcitx (Ubuntu)

** No longer affects: fcitx-kkc (Ubuntu)

** No longer affects: felix-latin (Ubuntu)

** No longer affects: flightcrew (Ubuntu)

** No longer affects: fmit (Ubuntu)

** No longer affects: fraqtive (Ubuntu)

** No longer affects: freecad (Ubuntu)

** No longer affects: freemat (Ubuntu)

** No longer affects: freemedforms-project (Ubuntu)

** No longer affects: freeplayer (Ubuntu)

** No longer affects: gammaray (Ubuntu)

** No longer affects: gebabbel (Ubuntu)

** No longer affects: genpo (Ubuntu)

** No longer affects: gle-graphics (Ubuntu)

** No longer affects: gmic (Ubuntu)

** No longer affects: gnash (Ubuntu)

** No longer affects: gnudoq (Ubuntu)

** No longer affects: gr-fosphor (Ubuntu)

** No longer affects: gr-radar (Ubuntu)

** No longer affects: grantlee (Ubuntu)

** No longer affects: gwenrename (Ubuntu)

** No longer affects: hamfax (Ubuntu)

** No longer affects: hedgewars (Ubuntu)

** No longer affects: heimdall-flash (Ubuntu)

** No longer affects: holdingnuts (Ubuntu)

** No longer affects: hydrogen (Ubuntu)

** No longer affects: ibus-qt (Ubuntu)

** No longer affects: ifpgui (Ubuntu)

** No longer affects: ifrit (Ubuntu)

** No longer affects: ike (Ubuntu)

** No longer affects: imagevis3d (Ubuntu)

** No longer affects: jovie (Ubuntu)

** No longer affects: jreen (Ubuntu)

** No longer affects: kaccessible (Ubuntu)

** No longer affects: kactivities (Ubuntu)

** No longer affects: kalternatives (Ubuntu)

** No longer affects: kamerka (Ubuntu)

** No longer affects: karlyriceditor (Ubuntu)

** No longer affects: kate4 (Ubuntu)

** No longer affects: kchmviewer (Ubuntu)

** No longer affects: kcm-qt-graphicssystem (Ubuntu)

** No longer affects: kcollectd (Ubuntu)

** No longer affects: kdbg (Ubuntu)

** No longer affects: kde-baseapps (Ubuntu)

** No longer affects: kde-runtime (Ubuntu)

** No longer affects: kde-thumbnailer-openoffice (Ubuntu)

** No longer affects: kde4libs (Ubuntu)

** No longer affects: kde4pimlibs (Ubuntu)

** No longer affects: kdepim4 (Ubuntu)

** No longer affects: kdesudo (Ubuntu)

** No longer affects: kdiff3 (Ubuntu)

** No longer affects: kdoctools (Ubuntu)

** No longer affects: keepassx (Ubuntu)

** No longer affects: kepas (Ubuntu)

** No longer affects: keurocalc (Ubuntu)

** No longer affects: kffmpegthumbnailer (Ubuntu)

** No longer affects: kfilemetadata (Ubuntu)

** No longer affects: kfilereplace (Ubuntu)

** No longer affects: kfritz (Ubuntu)

** No longer affects: kgmailnotifier (Ubuntu)

** No longer affects: kgrab (Ubuntu)

** No longer affects: kgraphviewer (Ubuntu)

** No longer affects: kiconedit (Ubuntu)

** No longer affects: kingston-update-notifier (Ubuntu)

** No longer affects: kitsune (Ubuntu)

** No longer affects: klinkstatus (Ubuntu)

** No longer affects: kmetronome (Ubuntu)

** No longer affects: kmidimon (Ubuntu)

** No longer affects: kmldonkey (Ubuntu)

** No longer affects: knights (Ubuntu)

** No longer affects: knutclient (Ubuntu)

** No longer

[Touch-packages] [Bug 1757538] Re: package systemd 234-2ubuntu12.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-03-21 Thread Dimitri John Ledkov

Yes, we are aware that packages, and specifically systemd, fail to
upgrade inside WSL container.

I will look into pushing out an update to the Ubuntu app in the store,
with the new systemd already installed in-place.

** Summary changed:

- package systemd 234-2ubuntu12.3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
+ Some packages, e.g. systemd, fail to upgrade in Ubuntu app on Windows WSL 
(package systemd 234-2ubuntu12.3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1)

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

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

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

Title:
  Some packages, e.g. systemd, fail to upgrade in Ubuntu app on Windows
  WSL (package systemd 234-2ubuntu12.3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1)

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  This occurred after running do-release-upgrade on Ubuntu 16.04 on the
  Linux Subsystem Windows. After the upgrade has failed, there are now
  dependency problems with udev and libudev1, but I do not know whether
  these are connected.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 234-2ubuntu12.3
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Function not implemented
  Date: Wed Mar 21 21:51:43 2018
  Dmesg:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcInterrupts:
   
  ProcKernelCmdLine: BOOT_IMAGE=/kernel init=/init ro
  ProcModules: Error: command ['sort', '/proc/modules'] failed with exit code 
2: sort: cannot read: /proc/modules: No such file or directory
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.2.26
  SourcePackage: systemd
  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: package systemd 234-2ubuntu12.3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2018-03-21 (0 days ago)

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

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

[Touch-packages] [Bug 1757320] [NEW] Remove Qt 4 from the archive

You have been subscribed to a public bug:

Currently Qt 4 has been dead upstream and we are starting to have
problems maintaining it, like for example in the OpenSSL 1.1 support case.

Following in the footsteps of Debian[1], all packages directly or
indirectly depending on qt4-x11 must either get ported to Qt 5 and
uploaded to the development release or get removed (by means of demotion
to -proposed or the whole source package removal) before the 19.04
release. If it is possible to do this by the 18.10 release, please do so.

No new packages entering the Ubuntu archive should depend on qt4-x11 or
any package which directly or indirectly depends on it.

[1] https://wiki.debian.org/Qt4Removal

** Affects: qt4-x11 (Ubuntu)
 Importance: Medium
 Status: New

-- 
Remove Qt 4 from the archive
https://bugs.launchpad.net/bugs/1757320
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to qt4-x11 in Ubuntu.

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

[Touch-packages] [Bug 1365375] Re: package libc6-dev-i386 (not installed) failed to install/upgrade: trying to overwrite '/usr/include/gnu', which is also in package libc6-dev-amd64 2.19-0ubuntu6.3

2018-03-21 Thread Fernando

I have the same issue. I corrected this problem removing first the
"libx32ncurses5-dev" package, then the others. I hope so this be useful.

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

Title:
  package libc6-dev-i386 (not installed) failed to install/upgrade:
  trying to overwrite '/usr/include/gnu', which is also in package libc6
  -dev-amd64 2.19-0ubuntu6.3

Status in eglibc package in Ubuntu:
  Confirmed

Bug description:
  apt-get install gcc-multilib broke it!

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libc6-dev-i386 (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  Date: Thu Sep  4 08:50:46 2014
  DpkgTerminalLog:
   Preparing to unpack .../libc6-dev-i386_2.19-0ubuntu6.3_amd64.deb ...
   Unpacking libc6-dev-i386 (2.19-0ubuntu6.3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libc6-dev-i386_2.19-0ubuntu6.3_amd64.deb (--unpack):
    trying to overwrite '/usr/include/gnu', which is also in package 
libc6-dev-amd64 2.19-0ubuntu6.3
  DuplicateSignature: package:libc6-dev-i386:(not installed):trying to 
overwrite '/usr/include/gnu', which is also in package libc6-dev-amd64 
2.19-0ubuntu6.3
  ErrorMessage: trying to overwrite '/usr/include/gnu', which is also in 
package libc6-dev-amd64 2.19-0ubuntu6.3
  SourcePackage: eglibc
  Title: package libc6-dev-i386 (not installed) failed to install/upgrade: 
trying to overwrite '/usr/include/gnu', which is also in package 
libc6-dev-amd64 2.19-0ubuntu6.3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1757561] [NEW] Wifi disconnects randomly under ubuntu 17.10

2018-03-21 Thread Mijail Febres Soria

Public bug reported:

Wifi connection on my Laptop Toshiba S55-A579 with UBUNTU 17.10 gets
disconnected at random intervals. I noticed this behavior 2 months ago
and still no solution available. It disconnects at home and even at
public places. The controller is:

03:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless
Network Adapter (rev 01)

I tried some solutions from internet, like setting: wifi.scan-rand-mac-
address=no and even disconnecting the energy saver feature. Installing a
firmware that I found in internet: firmware-ath9k-htc_1.4.0-81-gf206e56
+dfsg-2_all, doesn't help at all.

Sometimes, when the disconnection happens, the icon of wifi at the top
bar transform into a grey box.

It is a very annoying bug, it seems that came with some update, because
it was working just fine 2 months ago.

Best.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager 1.8.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 21 23:41:21 2018
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-11-18 (123 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
IpRoute:
 default via 192.168.1.254 dev wlp3s0 proto static metric 600 
 169.254.0.0/16 dev wlp3s0 scope link metric 1000 
 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.22 metric 600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
 [connection]
 wifi.powersave = 0
mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2018-03-21T22:57:47.465761
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   CONNECTION CON-UUID  CON-PATH

 wlp3s0 wifi  connected 
/org/freedesktop/NetworkManager/Devices/3  Bbox_Amandine  
806153c3-7543-49de-838c-9261d9f3f730  
/org/freedesktop/NetworkManager/ActiveConnection/24 
 E4:98:D1:D9:AA:FE  btdisconnected  
/org/freedesktop/NetworkManager/Devices/4  -- --
--  
 enp4s0 ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/2  -- --
--  
 lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/1  -- --
--
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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


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

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

Title:
  Wifi disconnects randomly under ubuntu 17.10

Status in network-manager package in Ubuntu:
  New

Bug description:
  Wifi connection on my Laptop Toshiba S55-A579 with UBUNTU 17.10 gets
  disconnected at random intervals. I noticed this behavior 2 months ago
  and still no solution available. It disconnects at home and even at
  public places. The controller is:

  03:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless
  Network Adapter (rev 01)

  I tried some solutions from internet, like setting: wifi.scan-rand-
  mac-address=no and even disconnecting the energy saver feature.
  Installing a firmware that I found in internet: firmware-ath9k-
  htc_1.4.0-81-gf206e56+dfsg-2_all, doesn't help at all.

  Sometimes, when the disconnection happens, the icon of wifi at the top
  bar transform into a grey box.

  It is a very annoying bug, it seems that came with some update,
  because it was working just fine 2 months ago.

  Best.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 21 23:41:21 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate:

[Touch-packages] [Bug 1567250] Re: ssh signin problem since OTA-10

2018-03-21 Thread Colin Watson

** Changed in: canonical-devices-system-image
 Assignee: HECTOR DAVID  (hektve) => (unassigned)

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

Title:
  ssh signin problem since OTA-10

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Terminal App:
  Incomplete
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in indicator-network package in Ubuntu:
  Invalid
Status in openssh package in Ubuntu:
  Invalid

Bug description:
  Not sure if this is a terminal or image issue, but here goes.

  Since the update last night to OTA-10 I cannot ssh to a server
  anymore. Error message: "Agent Admitted Failure To Sign Using The Key"

  On server side and client side nothing changed to the user settings or
  keys.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1567250/+subscriptions

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

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

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

Title:
  bridge-utils incompatible with ifupdown on bionic

Status in ifupdown package in Ubuntu:
  Fix Committed

Bug description:
  $ apt-cache policy ifupdown bridge-utils
  ifupdown:
Installed: (none)
Candidate: 0.8.16ubuntu2
Version table:
   0.8.16ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  bridge-utils:
Installed: 1.5-15ubuntu1
Candidate: 1.5-15ubuntu1
Version table:
   *** 1.5-15ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ sudo apt-get install ifupdown
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Suggested packages:
rdnssd
  The following packages will be REMOVED
bridge-utils
  The following NEW packages will be installed
ifupdown
  0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade.
  Need to get 55.2 kB of archives.
  After this operation, 119 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 ifupdown amd64 
0.8.16ubuntu2 [55.2 kB]
  Fetched 55.2 kB in 0s (1,280 kB/s)  
  (Reading database ... 251311 files and directories currently installed.)
  Removing bridge-utils (1.5-15ubuntu1) ...
  Selecting previously unselected package ifupdown.
  (Reading database ... 251286 files and directories currently installed.)
  Preparing to unpack .../ifupdown_0.8.16ubuntu2_amd64.deb ...
  Unpacking ifupdown (0.8.16ubuntu2) ...
  Setting up ifupdown (0.8.16ubuntu2) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  ureadahead will be reprofiled on next reboot
  Processing triggers for systemd (237-3ubuntu4) ...
  Processing triggers for man-db (2.8.2-1) ...

  $ sudo apt-get install bridge-utils
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Suggested packages:
ifupdown
  The following packages will be REMOVED
ifupdown
  The following NEW packages will be installed
bridge-utils
  0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade.
  Need to get 0 B/30.1 kB of archives.
  After this operation, 119 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 251318 files and directories currently installed.)
  Removing ifupdown (0.8.16ubuntu2) ...
  Selecting previously unselected package bridge-utils.
  (Reading database ... 251286 files and directories currently installed.)
  Preparing to unpack .../bridge-utils_1.5-15ubuntu1_amd64.deb ...
  Unpacking bridge-utils (1.5-15ubuntu1) ...
  Setting up bridge-utils (1.5-15ubuntu1) ...
  Processing triggers for man-db (2.8.2-1) ...

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

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

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

** Package changed: bridge-utils (Ubuntu) => ifupdown (Ubuntu)

** Changed in: ifupdown (Ubuntu)
   Importance: Undecided => Critical

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

** Changed in: ifupdown (Ubuntu)
 Assignee: (unassigned) => Steve Langasek (vorlon)

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

Title:
  bridge-utils incompatible with ifupdown on bionic

Status in ifupdown package in Ubuntu:
  In Progress

Bug description:
  $ apt-cache policy ifupdown bridge-utils
  ifupdown:
Installed: (none)
Candidate: 0.8.16ubuntu2
Version table:
   0.8.16ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  bridge-utils:
Installed: 1.5-15ubuntu1
Candidate: 1.5-15ubuntu1
Version table:
   *** 1.5-15ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ sudo apt-get install ifupdown
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Suggested packages:
rdnssd
  The following packages will be REMOVED
bridge-utils
  The following NEW packages will be installed
ifupdown
  0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade.
  Need to get 55.2 kB of archives.
  After this operation, 119 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 ifupdown amd64 
0.8.16ubuntu2 [55.2 kB]
  Fetched 55.2 kB in 0s (1,280 kB/s)  
  (Reading database ... 251311 files and directories currently installed.)
  Removing bridge-utils (1.5-15ubuntu1) ...
  Selecting previously unselected package ifupdown.
  (Reading database ... 251286 files and directories currently installed.)
  Preparing to unpack .../ifupdown_0.8.16ubuntu2_amd64.deb ...
  Unpacking ifupdown (0.8.16ubuntu2) ...
  Setting up ifupdown (0.8.16ubuntu2) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  ureadahead will be reprofiled on next reboot
  Processing triggers for systemd (237-3ubuntu4) ...
  Processing triggers for man-db (2.8.2-1) ...

  $ sudo apt-get install bridge-utils
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Suggested packages:
ifupdown
  The following packages will be REMOVED
ifupdown
  The following NEW packages will be installed
bridge-utils
  0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade.
  Need to get 0 B/30.1 kB of archives.
  After this operation, 119 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 251318 files and directories currently installed.)
  Removing ifupdown (0.8.16ubuntu2) ...
  Selecting previously unselected package bridge-utils.
  (Reading database ... 251286 files and directories currently installed.)
  Preparing to unpack .../bridge-utils_1.5-15ubuntu1_amd64.deb ...
  Unpacking bridge-utils (1.5-15ubuntu1) ...
  Setting up bridge-utils (1.5-15ubuntu1) ...
  Processing triggers for man-db (2.8.2-1) ...

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

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

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

2018-03-21 Thread ChristianEhrhardt

Yes andreas, this is the issue I mentioned on IRC.
AFAIK I think foundations is on that.

I'm subscribing the few that I've seen mentioning it for awareness.
So that they can dup it if they have another bug for that already.

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

Title:
  bridge-utils incompatible with ifupdown on bionic

Status in bridge-utils package in Ubuntu:
  Confirmed

Bug description:
  $ apt-cache policy ifupdown bridge-utils
  ifupdown:
Installed: (none)
Candidate: 0.8.16ubuntu2
Version table:
   0.8.16ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  bridge-utils:
Installed: 1.5-15ubuntu1
Candidate: 1.5-15ubuntu1
Version table:
   *** 1.5-15ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ sudo apt-get install ifupdown
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Suggested packages:
rdnssd
  The following packages will be REMOVED
bridge-utils
  The following NEW packages will be installed
ifupdown
  0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade.
  Need to get 55.2 kB of archives.
  After this operation, 119 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 ifupdown amd64 
0.8.16ubuntu2 [55.2 kB]
  Fetched 55.2 kB in 0s (1,280 kB/s)  
  (Reading database ... 251311 files and directories currently installed.)
  Removing bridge-utils (1.5-15ubuntu1) ...
  Selecting previously unselected package ifupdown.
  (Reading database ... 251286 files and directories currently installed.)
  Preparing to unpack .../ifupdown_0.8.16ubuntu2_amd64.deb ...
  Unpacking ifupdown (0.8.16ubuntu2) ...
  Setting up ifupdown (0.8.16ubuntu2) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  ureadahead will be reprofiled on next reboot
  Processing triggers for systemd (237-3ubuntu4) ...
  Processing triggers for man-db (2.8.2-1) ...

  $ sudo apt-get install bridge-utils
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Suggested packages:
ifupdown
  The following packages will be REMOVED
ifupdown
  The following NEW packages will be installed
bridge-utils
  0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade.
  Need to get 0 B/30.1 kB of archives.
  After this operation, 119 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 251318 files and directories currently installed.)
  Removing ifupdown (0.8.16ubuntu2) ...
  Selecting previously unselected package bridge-utils.
  (Reading database ... 251286 files and directories currently installed.)
  Preparing to unpack .../bridge-utils_1.5-15ubuntu1_amd64.deb ...
  Unpacking bridge-utils (1.5-15ubuntu1) ...
  Setting up bridge-utils (1.5-15ubuntu1) ...
  Processing triggers for man-db (2.8.2-1) ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1756846/+subscriptions

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

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

2018-03-21 Thread Andreas Hasenack

That conflicts was updated in this Debian change:

diff --git a/debian/changelog b/debian/changelog
index 845b518..ecc3f29 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+bridge-utils (1.5-12) unstable; urgency=medium
+
+  * Add vlan support so that old setups using vlans as ports don't break.
+
+ -- Santiago Garcia Mantinan   Sun, 22 Jan 2017 00:23:50 
+0100
+
 bridge-utils (1.5-11) unstable; urgency=low
 
   * Change /etc/default/bridge-utils to enable addition of hotplugged
diff --git a/debian/control b/debian/control
index c9b33ed..2b21fee 100644
--- a/debian/control
+++ b/debian/control
@@ -10,7 +10,7 @@ Architecture: linux-any
 Multi-Arch: foreign
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Suggests: ifupdown
-Conflicts: ifupdown (<< 0.6.0)
+Conflicts: ifupdown (<< 0.8.17)
 Description: Utilities for configuring the Linux Ethernet bridge
  This package contains utilities for configuring the Linux Ethernet
  bridge in Linux. The Linux Ethernet bridge can be used for connecting
diff --git a/debian/ifupdown.sh b/debian/ifupdown.sh
index 95dac90..517f084 100644
--- a/debian/ifupdown.sh
+++ b/debian/ifupdown.sh
@@ -66,6 +66,7 @@ do
   do
 # We attach and configure each port of the bridge
 if [ "$MODE" = "start" ] && [ ! -d /sys/class/net/$IFACE/brif/$port ]; then
+  create_vlan_port
   if [ "$IF_BRIDGE_HW" ]
   then
 KVER="$(uname -r)"
@@ -84,7 +85,7 @@ do
   brctl addif $IFACE $port && ip link set dev $port up
 # We detach each port of the bridge
 elif [ "$MODE" = "stop" ] && [ -d /sys/class/net/$IFACE/brif/$port ];  then
-  ip link set dev $port down && brctl delif $IFACE $port && \
+  ip link set dev $port down && brctl delif $IFACE $port && 
destroy_vlan_port
   if [ -f /proc/sys/net/ipv6/conf/$port/disable_ipv6 ]
   then
 echo 0 > /proc/sys/net/ipv6/conf/$port/disable_ipv6

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

Title:
  bridge-utils incompatible with ifupdown on bionic

Status in bridge-utils package in Ubuntu:
  Confirmed

Bug description:
  $ apt-cache policy ifupdown bridge-utils
  ifupdown:
Installed: (none)
Candidate: 0.8.16ubuntu2
Version table:
   0.8.16ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  bridge-utils:
Installed: 1.5-15ubuntu1
Candidate: 1.5-15ubuntu1
Version table:
   *** 1.5-15ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ sudo apt-get install ifupdown
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Suggested packages:
rdnssd
  The following packages will be REMOVED
bridge-utils
  The following NEW packages will be installed
ifupdown
  0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade.
  Need to get 55.2 kB of archives.
  After this operation, 119 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 ifupdown amd64 
0.8.16ubuntu2 [55.2 kB]
  Fetched 55.2 kB in 0s (1,280 kB/s)  
  (Reading database ... 251311 files and directories currently installed.)
  Removing bridge-utils (1.5-15ubuntu1) ...
  Selecting previously unselected package ifupdown.
  (Reading database ... 251286 files and directories currently installed.)
  Preparing to unpack .../ifupdown_0.8.16ubuntu2_amd64.deb ...
  Unpacking ifupdown (0.8.16ubuntu2) ...
  Setting up ifupdown (0.8.16ubuntu2) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  ureadahead will be reprofiled on next reboot
  Processing triggers for systemd (237-3ubuntu4) ...
  Processing triggers for man-db (2.8.2-1) ...

  $ sudo apt-get install bridge-utils
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Suggested packages:
ifupdown
  The following packages will be REMOVED
ifupdown
  The following NEW packages will be installed
bridge-utils
  0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade.
  Need to get 0 B/30.1 kB of archives.
  After this operation, 119 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 251318 files and directories currently installed.)
  Removing ifupdown (0.8.16ubuntu2) ...
  Selecting previously unselected package bridge-utils.
  (Reading database ... 251286 files and directories currently installed.)
  Preparing to unpack .../bridge-utils_1.5-15ubuntu1_amd64.deb ...
  Unpacking bridge-utils (1.5-15ubuntu1) ...
  Setting up bridge-utils (1.5-15ubuntu1) ...
  Processing triggers for man-db (2.8.2-1) ...

To manage notifications about this bug go to:

[Touch-packages] [Bug 1757538] [NEW] package systemd 234-2ubuntu12.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-03-21 Thread Der Trutinator

Public bug reported:

This occurred after running do-release-upgrade on Ubuntu 16.04 on the
Linux Subsystem Windows. After the upgrade has failed, there are now
dependency problems with udev and libudev1, but I do not know whether
these are connected.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: systemd 234-2ubuntu12.3
ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
Uname: Linux 4.4.0-43-Microsoft x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Function not implemented
Date: Wed Mar 21 21:51:43 2018
Dmesg:
 
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
Lsusb: Error: command ['lsusb'] failed with exit code 1:
ProcInterrupts:
 
ProcKernelCmdLine: BOOT_IMAGE=/kernel init=/init ro
ProcModules: Error: command ['sort', '/proc/modules'] failed with exit code 2: 
sort: cannot read: /proc/modules: No such file or directory
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.2.26
SourcePackage: systemd
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: package systemd 234-2ubuntu12.3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2018-03-21 (0 days ago)

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


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

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

Title:
  package systemd 234-2ubuntu12.3 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  This occurred after running do-release-upgrade on Ubuntu 16.04 on the
  Linux Subsystem Windows. After the upgrade has failed, there are now
  dependency problems with udev and libudev1, but I do not know whether
  these are connected.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 234-2ubuntu12.3
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Function not implemented
  Date: Wed Mar 21 21:51:43 2018
  Dmesg:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcInterrupts:
   
  ProcKernelCmdLine: BOOT_IMAGE=/kernel init=/init ro
  ProcModules: Error: command ['sort', '/proc/modules'] failed with exit code 
2: sort: cannot read: /proc/modules: No such file or directory
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.2.26
  SourcePackage: systemd
  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: package systemd 234-2ubuntu12.3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2018-03-21 (0 days ago)

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

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

[Touch-packages] [Bug 1757529] Re: apt: after reboot, still wants to keep 3 kernels when it should only keep 2

Historical context (thanks, Julian):
http://paste.ubuntu.com/p/qFfThVFChK/

The original design would have left 37 marked for autoremoval after 38
was installed.  I think that is the correct behavior which should be
restored.

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

Title:
  apt: after reboot, still wants to keep 3 kernels when it should only
  keep 2

Status in apt package in Ubuntu:
  New

Bug description:
  The apt kernel autoremoval handling should by design keep at least 2
  and at most 3 kernels on the system.

  However, on my 17.10 system, I currently have 3 kernels marked for
  retention while the kernel I have booted is the newest of these.  This
  means that I'm not able to upgrade to 18.04 without manual
  intervention, because I have a /boot that's sized just large enough to
  fit 3 kernels, not 4, apt autoremove won't remove any of the kernels.

  The sequence here is that I was running 4.13.0-36-generic; I updated,
  which pulled 4.13.0-37-generic onto the system; I ran apt autoremove
  --purge, which removed any kernels older than -36- from the system; I
  did *not* reboot; I installed 4.13.0-38-generic (from artful-
  proposed); all three kernels present are now marked for retention.  I
  rebooted, and all three kernels are still marked for retention.

  If /etc/kernel/postinst.d/apt-auto-removal were run *now*, it would
  mark 4.13.0-36-generic as autoremovable.  But there is nothing that
  reruns this script on boot.  Maybe there should be?

  $ last
  vorlon   tty2 :0   Tue Mar 20 11:14   still logged in
  reboot   system boot  4.13.0-38-generi Tue Mar 20 10:34   still running
  vorlon   tty2 :0   Tue Mar  6 23:12 - down  (13+10:21)
  reboot   system boot  4.13.0-36-generi Tue Mar  6 23:10 - 10:33 (13+10:23)

  wtmp begins Tue Mar  6 23:09:27 2018
  $

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apt 1.5.1
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 21 13:02:43 2018
  InstallationDate: Installed on 2010-09-24 (2735 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  SourcePackage: apt
  UpgradeStatus: Upgraded to artful on 2018-03-21 (0 days ago)

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

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

[Touch-packages] [Bug 1757261] Re: libindicator FTBFS on bionic

This bug was fixed in the package libindicator -
16.10.0+18.04.20180321.1-0ubuntu1

---
libindicator (16.10.0+18.04.20180321.1-0ubuntu1) bionic; urgency=medium

  [ Olivier Tilloy ]
  * Cast GtkWidget to the expected widget type to fix build failures on bionic
[-Werror=incompatible-pointer-types] (LP: #1757261)

 -- Marco Trevisan (Treviño)   Wed, 21 Mar 2018 17:40:06
+

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

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

Title:
  libindicator FTBFS on bionic

Status in libindicator package in Ubuntu:
  Fix Released

Bug description:
  ../../../libindicator/indicator-ng.c: In function ‘indicator_ng_init’:
  ../../../libindicator/indicator-ng.c:690:21: error: assignment from 
incompatible pointer type [-Werror=incompatible-pointer-types]
 self->entry.label = g_object_ref_sink (gtk_label_new (NULL));
   ^
  ../../../libindicator/indicator-ng.c:691:21: error: assignment from 
incompatible pointer type [-Werror=incompatible-pointer-types]
 self->entry.image = g_object_ref_sink (gtk_image_new ());
   ^
  ../../../libindicator/indicator-ng.c:693:20: error: assignment from 
incompatible pointer type [-Werror=incompatible-pointer-types]
 self->entry.menu = g_object_ref_sink (gtk_menu_new ());
  ^
  cc1: all warnings being treated as errors
  Makefile:759: recipe for target 'libindicator3_la-indicator-ng.lo' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libindicator3-7 16.10.0+18.04.20171205.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 20 21:47:16 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (626 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libindicator
  UpgradeStatus: Upgraded to bionic on 2018-01-29 (50 days ago)

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

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

[Touch-packages] [Bug 1757529] Re: apt: after reboot, still wants to keep 3 kernels when it should only keep 2

As an alternative to running /etc/kernel/postinst.d/apt-auto-removal on
boot, the code could be changed so that 37 is not retained once 38 is
installed.  I can't remember now if there was a rationale for marking
second-newest kernel for retention, in the case where that kernel had
never been booted.

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

Title:
  apt: after reboot, still wants to keep 3 kernels when it should only
  keep 2

Status in apt package in Ubuntu:
  New

Bug description:
  The apt kernel autoremoval handling should by design keep at least 2
  and at most 3 kernels on the system.

  However, on my 17.10 system, I currently have 3 kernels marked for
  retention while the kernel I have booted is the newest of these.  This
  means that I'm not able to upgrade to 18.04 without manual
  intervention, because I have a /boot that's sized just large enough to
  fit 3 kernels, not 4, apt autoremove won't remove any of the kernels.

  The sequence here is that I was running 4.13.0-36-generic; I updated,
  which pulled 4.13.0-37-generic onto the system; I ran apt autoremove
  --purge, which removed any kernels older than -36- from the system; I
  did *not* reboot; I installed 4.13.0-38-generic (from artful-
  proposed); all three kernels present are now marked for retention.  I
  rebooted, and all three kernels are still marked for retention.

  If /etc/kernel/postinst.d/apt-auto-removal were run *now*, it would
  mark 4.13.0-36-generic as autoremovable.  But there is nothing that
  reruns this script on boot.  Maybe there should be?

  $ last
  vorlon   tty2 :0   Tue Mar 20 11:14   still logged in
  reboot   system boot  4.13.0-38-generi Tue Mar 20 10:34   still running
  vorlon   tty2 :0   Tue Mar  6 23:12 - down  (13+10:21)
  reboot   system boot  4.13.0-36-generi Tue Mar  6 23:10 - 10:33 (13+10:23)

  wtmp begins Tue Mar  6 23:09:27 2018
  $

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apt 1.5.1
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 21 13:02:43 2018
  InstallationDate: Installed on 2010-09-24 (2735 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  SourcePackage: apt
  UpgradeStatus: Upgraded to artful on 2018-03-21 (0 days ago)

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

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

[Touch-packages] [Bug 1757529] [NEW] apt: after reboot, still wants to keep 3 kernels when it should only keep 2

Public bug reported:

The apt kernel autoremoval handling should by design keep at least 2 and
at most 3 kernels on the system.

However, on my 17.10 system, I currently have 3 kernels marked for
retention while the kernel I have booted is the newest of these.  This
means that I'm not able to upgrade to 18.04 without manual intervention,
because I have a /boot that's sized just large enough to fit 3 kernels,
not 4, apt autoremove won't remove any of the kernels.

The sequence here is that I was running 4.13.0-36-generic; I updated,
which pulled 4.13.0-37-generic onto the system; I ran apt autoremove
--purge, which removed any kernels older than -36- from the system; I
did *not* reboot; I installed 4.13.0-38-generic (from artful-proposed);
all three kernels present are now marked for retention.  I rebooted, and
all three kernels are still marked for retention.

If /etc/kernel/postinst.d/apt-auto-removal were run *now*, it would mark
4.13.0-36-generic as autoremovable.  But there is nothing that reruns
this script on boot.  Maybe there should be?

$ last
vorlon   tty2 :0   Tue Mar 20 11:14   still logged in
reboot   system boot  4.13.0-38-generi Tue Mar 20 10:34   still running
vorlon   tty2 :0   Tue Mar  6 23:12 - down  (13+10:21)
reboot   system boot  4.13.0-36-generi Tue Mar  6 23:10 - 10:33 (13+10:23)

wtmp begins Tue Mar  6 23:09:27 2018
$

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: apt 1.5.1
ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 21 13:02:43 2018
InstallationDate: Installed on 2010-09-24 (2735 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
SourcePackage: apt
UpgradeStatus: Upgraded to artful on 2018-03-21 (0 days ago)

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


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

Title:
  apt: after reboot, still wants to keep 3 kernels when it should only
  keep 2

Status in apt package in Ubuntu:
  New

Bug description:
  The apt kernel autoremoval handling should by design keep at least 2
  and at most 3 kernels on the system.

  However, on my 17.10 system, I currently have 3 kernels marked for
  retention while the kernel I have booted is the newest of these.  This
  means that I'm not able to upgrade to 18.04 without manual
  intervention, because I have a /boot that's sized just large enough to
  fit 3 kernels, not 4, apt autoremove won't remove any of the kernels.

  The sequence here is that I was running 4.13.0-36-generic; I updated,
  which pulled 4.13.0-37-generic onto the system; I ran apt autoremove
  --purge, which removed any kernels older than -36- from the system; I
  did *not* reboot; I installed 4.13.0-38-generic (from artful-
  proposed); all three kernels present are now marked for retention.  I
  rebooted, and all three kernels are still marked for retention.

  If /etc/kernel/postinst.d/apt-auto-removal were run *now*, it would
  mark 4.13.0-36-generic as autoremovable.  But there is nothing that
  reruns this script on boot.  Maybe there should be?

  $ last
  vorlon   tty2 :0   Tue Mar 20 11:14   still logged in
  reboot   system boot  4.13.0-38-generi Tue Mar 20 10:34   still running
  vorlon   tty2 :0   Tue Mar  6 23:12 - down  (13+10:21)
  reboot   system boot  4.13.0-36-generi Tue Mar  6 23:10 - 10:33 (13+10:23)

  wtmp begins Tue Mar  6 23:09:27 2018
  $

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apt 1.5.1
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 21 13:02:43 2018
  InstallationDate: Installed on 2010-09-24 (2735 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  SourcePackage: apt
  UpgradeStatus: Upgraded to artful on 2018-03-21 (0 days ago)

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

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

[Touch-packages] [Bug 1757529] Re: apt: after reboot, still wants to keep 3 kernels when it should only keep 2

Attached apt term.log shows the history:
- 36 is running
- 31 is purged
- 37 is installed
- 32 is purged
- 38 is installed
- 37 is *not* purged
- rebooted to 38
- 36 and 37 are still not purged

** Attachment added: "term.log"
   
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1757529/+attachment/5086261/+files/term.log

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

Title:
  apt: after reboot, still wants to keep 3 kernels when it should only
  keep 2

Status in apt package in Ubuntu:
  New

Bug description:
  The apt kernel autoremoval handling should by design keep at least 2
  and at most 3 kernels on the system.

  However, on my 17.10 system, I currently have 3 kernels marked for
  retention while the kernel I have booted is the newest of these.  This
  means that I'm not able to upgrade to 18.04 without manual
  intervention, because I have a /boot that's sized just large enough to
  fit 3 kernels, not 4, apt autoremove won't remove any of the kernels.

  The sequence here is that I was running 4.13.0-36-generic; I updated,
  which pulled 4.13.0-37-generic onto the system; I ran apt autoremove
  --purge, which removed any kernels older than -36- from the system; I
  did *not* reboot; I installed 4.13.0-38-generic (from artful-
  proposed); all three kernels present are now marked for retention.  I
  rebooted, and all three kernels are still marked for retention.

  If /etc/kernel/postinst.d/apt-auto-removal were run *now*, it would
  mark 4.13.0-36-generic as autoremovable.  But there is nothing that
  reruns this script on boot.  Maybe there should be?

  $ last
  vorlon   tty2 :0   Tue Mar 20 11:14   still logged in
  reboot   system boot  4.13.0-38-generi Tue Mar 20 10:34   still running
  vorlon   tty2 :0   Tue Mar  6 23:12 - down  (13+10:21)
  reboot   system boot  4.13.0-36-generi Tue Mar  6 23:10 - 10:33 (13+10:23)

  wtmp begins Tue Mar  6 23:09:27 2018
  $

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apt 1.5.1
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 21 13:02:43 2018
  InstallationDate: Installed on 2010-09-24 (2735 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  SourcePackage: apt
  UpgradeStatus: Upgraded to artful on 2018-03-21 (0 days ago)

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

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

[Touch-packages] [Bug 1757529] Re: apt: after reboot, still wants to keep 3 kernels when it should only keep 2

** Attachment added: "01autoremove-kernels"
   
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1757529/+attachment/5086252/+files/01autoremove-kernels

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

Title:
  apt: after reboot, still wants to keep 3 kernels when it should only
  keep 2

Status in apt package in Ubuntu:
  New

Bug description:
  The apt kernel autoremoval handling should by design keep at least 2
  and at most 3 kernels on the system.

  However, on my 17.10 system, I currently have 3 kernels marked for
  retention while the kernel I have booted is the newest of these.  This
  means that I'm not able to upgrade to 18.04 without manual
  intervention, because I have a /boot that's sized just large enough to
  fit 3 kernels, not 4, apt autoremove won't remove any of the kernels.

  The sequence here is that I was running 4.13.0-36-generic; I updated,
  which pulled 4.13.0-37-generic onto the system; I ran apt autoremove
  --purge, which removed any kernels older than -36- from the system; I
  did *not* reboot; I installed 4.13.0-38-generic (from artful-
  proposed); all three kernels present are now marked for retention.  I
  rebooted, and all three kernels are still marked for retention.

  If /etc/kernel/postinst.d/apt-auto-removal were run *now*, it would
  mark 4.13.0-36-generic as autoremovable.  But there is nothing that
  reruns this script on boot.  Maybe there should be?

  $ last
  vorlon   tty2 :0   Tue Mar 20 11:14   still logged in
  reboot   system boot  4.13.0-38-generi Tue Mar 20 10:34   still running
  vorlon   tty2 :0   Tue Mar  6 23:12 - down  (13+10:21)
  reboot   system boot  4.13.0-36-generi Tue Mar  6 23:10 - 10:33 (13+10:23)

  wtmp begins Tue Mar  6 23:09:27 2018
  $

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apt 1.5.1
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 21 13:02:43 2018
  InstallationDate: Installed on 2010-09-24 (2735 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  SourcePackage: apt
  UpgradeStatus: Upgraded to artful on 2018-03-21 (0 days ago)

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

-- 
Mailing list: https://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 1757256] Re: Apparmor profile gajim

2018-03-21 Thread george jetson

thank you very much it worked!


On 03/21/2018 10:09 PM, Seth Arnold wrote:
> (You will need to add it to all child subprofiles that execute in the
> other filesystem namespaces.)
>

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

Title:
  Apparmor profile gajim

Status in apparmor package in Ubuntu:
  New

Bug description:
  Followed this guide: https://gitlab.com/apparmor/apparmor/wi … with_tools and 
saved usr.bin.gajim after scanning.
  After I restart machine and run Gajim from terminal I get:

  Fatal Python error: Py_Initialize: Unable to get the locale encoding
  ModuleNotFoundError: No module named 'encodings'

  Current thread 0x6a383a1d5540 (most recent call first):
  Aborted (core dumped)

  If I delete the profile and restart machine it runs (to confirm it is
  profile causing).

  This is my current profile

  
  # vim:syntax=apparmor
  # --
  #
  #Copyright (C) 2015-2018 Mikhail Morfikov
  #
  #This program is free software; you can redistribute it and/or
  #modify it under the terms of version 2 of the GNU General Public
  #License published by the Free Software Foundation.
  #
  # --

  #include 

  /usr/bin/gajim {
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 

/usr/bin/gajim mr,

/usr/bin/ r,
/usr/local/bin/ r,

# Gajim plugins
/usr/share/gajim/plugins/ r,
/usr/share/gajim/plugins/** r,

# Gajim home files
owner @{HOME}/.config/gajim/ rw,
owner @{HOME}/.config/gajim/** rw,
owner @{HOME}/.local/share/gajim/ rw,
owner @{HOME}/.local/share/gajim/** rwk,

# User downloads
owner @{HOME}/[dD]ownload{,s}/ r,
owner @{HOME}/[dD]ownload{,s}/** rwl,
owner @{HOME}/[dD]esktop/ r,
owner @{HOME}/[dD]esktop/** rwl,

# Cache
owner /tmp/morfik_cache/.cache/gajim/ rwk,
owner /tmp/morfik_cache/.cache/gajim/** rwk,
owner @{HOME}/.cache/gajim/ rwk,
owner @{HOME}/.cache/gajim/** rwk,

# Deny access to webcam and mic
deny /dev/video0 rw,
deny /dev/v4l/by-path/ r,
deny /dev/snd/pcmC0D0c rw,

owner @{PROC}/@{pid}/mounts r,
owner @{PROC}/@{pid}/fd/ r,
owner @{PROC}/@{pid}/mountinfo r,

# External apps
/usr/lib/firefox/firefox rPUx,
/usr/bin/gpg rPUx,

/usr/share/glib-2.0/schemas/gschemas.compiled r,

owner /{,var/}run/user/[0-9]*/dconf/user rw,

# Silencer
deny /usr/lib/python3/dist-packages/** w,
deny /usr/share/gajim/plugins/** w,
deny @{HOME}/ r,

# Sounds
/usr/bin/aplay Cx -> audio,
/usr/bin/pacat Cx -> audio,
profile audio {
  #include 
  #include 

  /usr/bin/aplay mr,
  /usr/bin/pacat mr,

  owner @{HOME}/.Xauthority r,

  /etc/machine-id r,
  /var/lib/dbus/machine-id r,

}

/sbin/ldconfig Cx -> ldconfig,
profile ldconfig {
  #include 

  /sbin/ldconfig mr,

}

/bin/dash Cx -> dash,
profile dash {
  #include 

  /bin/dash mr,

  /bin/uname rix,

  /usr/bin/gpg rPUx,

}

  }

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

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

[Touch-packages] [Bug 1757256] Re: Apparmor profile gajim

2018-03-21 Thread Seth Arnold

(You will need to add it to all child subprofiles that execute in the
other filesystem namespaces.)

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

Title:
  Apparmor profile gajim

Status in apparmor package in Ubuntu:
  New

Bug description:
  Followed this guide: https://gitlab.com/apparmor/apparmor/wi … with_tools and 
saved usr.bin.gajim after scanning.
  After I restart machine and run Gajim from terminal I get:

  Fatal Python error: Py_Initialize: Unable to get the locale encoding
  ModuleNotFoundError: No module named 'encodings'

  Current thread 0x6a383a1d5540 (most recent call first):
  Aborted (core dumped)

  If I delete the profile and restart machine it runs (to confirm it is
  profile causing).

  This is my current profile

  
  # vim:syntax=apparmor
  # --
  #
  #Copyright (C) 2015-2018 Mikhail Morfikov
  #
  #This program is free software; you can redistribute it and/or
  #modify it under the terms of version 2 of the GNU General Public
  #License published by the Free Software Foundation.
  #
  # --

  #include 

  /usr/bin/gajim {
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 

/usr/bin/gajim mr,

/usr/bin/ r,
/usr/local/bin/ r,

# Gajim plugins
/usr/share/gajim/plugins/ r,
/usr/share/gajim/plugins/** r,

# Gajim home files
owner @{HOME}/.config/gajim/ rw,
owner @{HOME}/.config/gajim/** rw,
owner @{HOME}/.local/share/gajim/ rw,
owner @{HOME}/.local/share/gajim/** rwk,

# User downloads
owner @{HOME}/[dD]ownload{,s}/ r,
owner @{HOME}/[dD]ownload{,s}/** rwl,
owner @{HOME}/[dD]esktop/ r,
owner @{HOME}/[dD]esktop/** rwl,

# Cache
owner /tmp/morfik_cache/.cache/gajim/ rwk,
owner /tmp/morfik_cache/.cache/gajim/** rwk,
owner @{HOME}/.cache/gajim/ rwk,
owner @{HOME}/.cache/gajim/** rwk,

# Deny access to webcam and mic
deny /dev/video0 rw,
deny /dev/v4l/by-path/ r,
deny /dev/snd/pcmC0D0c rw,

owner @{PROC}/@{pid}/mounts r,
owner @{PROC}/@{pid}/fd/ r,
owner @{PROC}/@{pid}/mountinfo r,

# External apps
/usr/lib/firefox/firefox rPUx,
/usr/bin/gpg rPUx,

/usr/share/glib-2.0/schemas/gschemas.compiled r,

owner /{,var/}run/user/[0-9]*/dconf/user rw,

# Silencer
deny /usr/lib/python3/dist-packages/** w,
deny /usr/share/gajim/plugins/** w,
deny @{HOME}/ r,

# Sounds
/usr/bin/aplay Cx -> audio,
/usr/bin/pacat Cx -> audio,
profile audio {
  #include 
  #include 

  /usr/bin/aplay mr,
  /usr/bin/pacat mr,

  owner @{HOME}/.Xauthority r,

  /etc/machine-id r,
  /var/lib/dbus/machine-id r,

}

/sbin/ldconfig Cx -> ldconfig,
profile ldconfig {
  #include 

  /sbin/ldconfig mr,

}

/bin/dash Cx -> dash,
profile dash {
  #include 

  /bin/dash mr,

  /bin/uname rix,

  /usr/bin/gpg rPUx,

}

  }

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

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

[Touch-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) due to outdated gcc-4.8

2018-03-21 Thread Bill Miller

Christopher M. Penalver - sounds good. Thanks!  Bill

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

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

Status in gcc-4.8 package in Ubuntu:
  Fix Released

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

  Rebooted into 4.4.0-112 kernel and all was well.

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

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

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

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

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

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

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

[Touch-packages] [Bug 1757091] Re: systemctl enable lightdm

2018-03-21 Thread Fabrice ROUSSIN

I do confirm the bug, fresh ubuntu 17.10 install

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

Title:
  systemctl enable lightdm

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Synchronizing state of lightdm.service with SysV service script with 
/lib/systemd/systemd-sysv-install.
  Executing: /lib/systemd/systemd-sysv-install enable lightdm
  The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
  settings in the [Install] section, and DefaultInstance for template units).
  This means they are not meant to be enabled using systemctl.
  Possible reasons for having this kind of units are:
  1) A unit may be statically enabled by being symlinked from another unit's
 .wants/ or .requires/ directory.
  2) A unit's purpose may be to act as a helper for some other unit which has
 a requirement dependency on it.
  3) A unit may be started when needed via activation (socket, path, timer,
 D-Bus, udev, scripted systemctl call, ...).
  4) In case of template units, the unit is meant to be enabled with some
 instance name specified.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: lightdm 1.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Tue Mar 20 11:44:46 2018
  InstallationDate: Installed on 2018-01-22 (57 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1757256] Re: Apparmor profile gajim

2018-03-21 Thread Seth Arnold

Add 'attach_disconnected' to the profile's flags. Apparently this is
using files from namespaces that the processes cannot access.
'attach_disconnected' asks AppArmor to pretend that those files are
rooted at /.

Then you can name the files that are being denied.

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

Title:
  Apparmor profile gajim

Status in apparmor package in Ubuntu:
  New

Bug description:
  Followed this guide: https://gitlab.com/apparmor/apparmor/wi … with_tools and 
saved usr.bin.gajim after scanning.
  After I restart machine and run Gajim from terminal I get:

  Fatal Python error: Py_Initialize: Unable to get the locale encoding
  ModuleNotFoundError: No module named 'encodings'

  Current thread 0x6a383a1d5540 (most recent call first):
  Aborted (core dumped)

  If I delete the profile and restart machine it runs (to confirm it is
  profile causing).

  This is my current profile

  
  # vim:syntax=apparmor
  # --
  #
  #Copyright (C) 2015-2018 Mikhail Morfikov
  #
  #This program is free software; you can redistribute it and/or
  #modify it under the terms of version 2 of the GNU General Public
  #License published by the Free Software Foundation.
  #
  # --

  #include 

  /usr/bin/gajim {
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 

/usr/bin/gajim mr,

/usr/bin/ r,
/usr/local/bin/ r,

# Gajim plugins
/usr/share/gajim/plugins/ r,
/usr/share/gajim/plugins/** r,

# Gajim home files
owner @{HOME}/.config/gajim/ rw,
owner @{HOME}/.config/gajim/** rw,
owner @{HOME}/.local/share/gajim/ rw,
owner @{HOME}/.local/share/gajim/** rwk,

# User downloads
owner @{HOME}/[dD]ownload{,s}/ r,
owner @{HOME}/[dD]ownload{,s}/** rwl,
owner @{HOME}/[dD]esktop/ r,
owner @{HOME}/[dD]esktop/** rwl,

# Cache
owner /tmp/morfik_cache/.cache/gajim/ rwk,
owner /tmp/morfik_cache/.cache/gajim/** rwk,
owner @{HOME}/.cache/gajim/ rwk,
owner @{HOME}/.cache/gajim/** rwk,

# Deny access to webcam and mic
deny /dev/video0 rw,
deny /dev/v4l/by-path/ r,
deny /dev/snd/pcmC0D0c rw,

owner @{PROC}/@{pid}/mounts r,
owner @{PROC}/@{pid}/fd/ r,
owner @{PROC}/@{pid}/mountinfo r,

# External apps
/usr/lib/firefox/firefox rPUx,
/usr/bin/gpg rPUx,

/usr/share/glib-2.0/schemas/gschemas.compiled r,

owner /{,var/}run/user/[0-9]*/dconf/user rw,

# Silencer
deny /usr/lib/python3/dist-packages/** w,
deny /usr/share/gajim/plugins/** w,
deny @{HOME}/ r,

# Sounds
/usr/bin/aplay Cx -> audio,
/usr/bin/pacat Cx -> audio,
profile audio {
  #include 
  #include 

  /usr/bin/aplay mr,
  /usr/bin/pacat mr,

  owner @{HOME}/.Xauthority r,

  /etc/machine-id r,
  /var/lib/dbus/machine-id r,

}

/sbin/ldconfig Cx -> ldconfig,
profile ldconfig {
  #include 

  /sbin/ldconfig mr,

}

/bin/dash Cx -> dash,
profile dash {
  #include 

  /bin/dash mr,

  /bin/uname rix,

  /usr/bin/gpg rPUx,

}

  }

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

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

[Touch-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade

2018-03-21 Thread Janghou

Error message in syslog:
kernel: [   69.465455] compiz-config-p[2198]: segfault at 0 ip 7f3779876d6f 
sp 7fff80d63300 error 4 in libcompizconfig.so.0.0.0[7f377984e000+52000]

It's not in compiz but in compiz-config. Symptoms are nearly the same.

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Artful:
  Fix Released

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

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

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

[Touch-packages] [Bug 1757091] Re: systemctl enable lightdm

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

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

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

Title:
  systemctl enable lightdm

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Synchronizing state of lightdm.service with SysV service script with 
/lib/systemd/systemd-sysv-install.
  Executing: /lib/systemd/systemd-sysv-install enable lightdm
  The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
  settings in the [Install] section, and DefaultInstance for template units).
  This means they are not meant to be enabled using systemctl.
  Possible reasons for having this kind of units are:
  1) A unit may be statically enabled by being symlinked from another unit's
 .wants/ or .requires/ directory.
  2) A unit's purpose may be to act as a helper for some other unit which has
 a requirement dependency on it.
  3) A unit may be started when needed via activation (socket, path, timer,
 D-Bus, udev, scripted systemctl call, ...).
  4) In case of template units, the unit is meant to be enabled with some
 instance name specified.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: lightdm 1.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Tue Mar 20 11:44:46 2018
  InstallationDate: Installed on 2018-01-22 (57 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade

2018-03-21 Thread Janghou

I seems the bug returned in March. After not rebooting my laptop for 10
days, unity doesn't start and the same segfault in libcompizconfig.

My original bug-report: 1741447

https://askubuntu.com/questions/992571/gui-unity-crashing-in-16-04-lts-after-updates-2018-01-04-compiz-segfaults
See Workaround 3 on the askubuntu page.

For me returning to low graphics mode seems the best workaround for now.
It works fine now, so the bug has mutated a bit

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Artful:
  Fix Released

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

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

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

[Touch-packages] [Bug 1695618] Re: Include qt5-style-plugins into the default installation, otherwise Qt5 apps don’t pick up the GTK+ style

2018-03-21 Thread Doctor Rover

** Summary changed:

- Qt5 apps don’t pick up the GTK+ style anymore
+ Include qt5-style-plugins into the default installation, otherwise Qt5 apps 
don’t pick up the GTK+ style

** Description changed:

- Since I upgraded to Qt 5.7.1, Qt5 apps stopped picking up the Ubuntu
- (GTK+, I presume) theme, and look very Windowsy. I have qt5-gtk-
- platformtheme installed, and I tried forcing it by setting
- QT_QPA_PLATFORMTHEME, but to no avail.
+ In Artful and Bionic, Qt5 applications look alien because they don’t follow 
the GTK+ style.
+ For Qt5 applications to pick up the GTK+ style, qt5-style-plugins must be 
included into the default installation and “export QT_QPA_PLATFORMTHEME=gtk2” 
must be provided.
+ 
+ Original bug description:
+ Since I upgraded to Qt 5.7.1, Qt5 apps stopped picking up the Ubuntu (GTK+, I 
presume) theme, and look very Windowsy. I have qt5-gtk-platformtheme installed, 
and I tried forcing it by setting QT_QPA_PLATFORMTHEME, but to no avail.

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

Title:
  Include qt5-style-plugins into the default installation, otherwise Qt5
  apps don’t pick up the GTK+ style

Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  In Artful and Bionic, Qt5 applications look alien because they don’t follow 
the GTK+ style.
  For Qt5 applications to pick up the GTK+ style, qt5-style-plugins must be 
included into the default installation and “export QT_QPA_PLATFORMTHEME=gtk2” 
must be provided.

  Original bug description:
  Since I upgraded to Qt 5.7.1, Qt5 apps stopped picking up the Ubuntu (GTK+, I 
presume) theme, and look very Windowsy. I have qt5-gtk-platformtheme installed, 
and I tried forcing it by setting QT_QPA_PLATFORMTHEME, but to no avail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1695618/+subscriptions

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

[Touch-packages] [Bug 1757388] Re: bridge device is missing

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

** Changed in: bridge-utils (Ubuntu)
   Status: New => Confirmed

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

Title:
  bridge device is missing

Status in bridge-utils package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04: Since last dist-upgrade of the bridge-utils (2018-03-21)
  the bridge netwok device 'br0' is missing. A 'ls /sys/class/net'
  prints the devices 'enp3s0  lo  lxcbr0  virbr0  virbr0-nic' only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1757388/+subscriptions

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

[Touch-packages] [Bug 1757261] Re: libindicator FTBFS on bionic

** Branch linked: lp:~ci-train-bot/libindicator/libindicator-ubuntu-
bionic-3205

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

Title:
  libindicator FTBFS on bionic

Status in libindicator package in Ubuntu:
  In Progress

Bug description:
  ../../../libindicator/indicator-ng.c: In function ‘indicator_ng_init’:
  ../../../libindicator/indicator-ng.c:690:21: error: assignment from 
incompatible pointer type [-Werror=incompatible-pointer-types]
 self->entry.label = g_object_ref_sink (gtk_label_new (NULL));
   ^
  ../../../libindicator/indicator-ng.c:691:21: error: assignment from 
incompatible pointer type [-Werror=incompatible-pointer-types]
 self->entry.image = g_object_ref_sink (gtk_image_new ());
   ^
  ../../../libindicator/indicator-ng.c:693:20: error: assignment from 
incompatible pointer type [-Werror=incompatible-pointer-types]
 self->entry.menu = g_object_ref_sink (gtk_menu_new ());
  ^
  cc1: all warnings being treated as errors
  Makefile:759: recipe for target 'libindicator3_la-indicator-ng.lo' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libindicator3-7 16.10.0+18.04.20171205.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 20 21:47:16 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (626 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libindicator
  UpgradeStatus: Upgraded to bionic on 2018-01-29 (50 days ago)

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

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

[Touch-packages] [Bug 288866] Re: Unable to print, CUPS says "Can't create temporary file"

2018-03-21 Thread Jessica Meyer

Thank you very much!! I've been looking for a solution for almost a
year!! Nothing worked.

The miracle:
"sudo chmod 1777 /tmp" 

Thanks!

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

Title:
  Unable to print, CUPS says "Can't create temporary file"

Status in cups package in Ubuntu:
  Invalid

Bug description:
  Page 1 (Scheduler not running?):
  {'cups_connection_failure': False}
  Page 2 (Choose printer):
  {'cups_dest': ,
   'cups_instance': None,
   'cups_queue': 'SP1-ML-1210',
   'cups_queue_listed': True}
  Page 3 (Check printer sanity):
  {'cups_device_uri_scheme': u'lpd',
   'cups_printer_dict': {'device-uri': u'lpd://192.168.1.10/PS1',
 'printer-info': u'',
 'printer-is-shared': True,
 'printer-location': u'',
 'printer-make-and-model': u'Samsung ML-1210 
Foomatic/gdi (recommended)',
 'printer-state': 3,
 'printer-state-message': u"Can't create temporary 
file",
 'printer-state-reasons': [u'none'],
 'printer-type': 4100,
 'printer-uri-supported': 
u'ipp://localhost:631/printers/SP1-ML-1210'},
   'cups_printer_remote': False,
   'is_cups_class': False}
  Page 4 (Check PPD sanity):
  {'cups_printer_ppd_defaults': {u'Adjustment': {u'Density': u'3',
 u'HalftoningAlgorithm': 
u'Standard'},
 u'General': {u'Copies': u'1',
  u'Economode': u'Off',
  u'Manualfeed': u'Off',
  u'MediaType': u'Normal',
  u'PageRegion': u'A4',
  u'PageSize': u'A4',
  u'Resolution': u'600x600dpi'},
 u'Miscellaneous': {u'AllowReprint': u'Yes',
u'Altitude': u'Low',
u'JamRecovery': u'Yes',
u'PageTimeout': u'15',
u'PowerSaveTime': u'5',
u'PowerSaving': u'On'}},
   'cups_printer_ppd_valid': True,
   'missing_pkgs_and_exes': ([], [])}
  Page 5 (Local or remote?):
  {'printer_is_remote': False}
  Page 6 (Printer state reasons):
  {'printer-state-message': u"Can't create temporary file",
   'printer-state-reasons': [u'none']}
  Page 7 (Error log checkpoint):
  {'cups_server_settings': {'DefaultAuthType': 'Basic',
'SystemGroup': 'lpadmin',
'_debug_logging': '0',
'_remote_admin': '0',
'_remote_any': '0',
'_remote_printers': '0',
'_share_printers': '0',
'_user_cancel_any': '0'},
   'error_log_checkpoint': 2170L,
   'error_log_debug_logging_set': True}
  Page 8 (Print test page):
  {'test_page_attempted': True,
   'test_page_completions': [(2,
  u'Job stopped due to filter errors; please 
consult the error_log file for details.')],
   'test_page_job_id': [2],
   'test_page_job_status': [(False,
 1,
 'SP1-ML-1210',
 'Test Page',
 'Stopped',
 None),
(True,
 2,
 'SP1-ML-1210',
 'Test Page',
 'Stopped',
 {'attributes-charset': u'utf-8',
  'attributes-natural-language': u'en-us',
  'document-format': u'application/postscript',
  'job-hold-until': u'no-hold',
  'job-id': 2,
  'job-k-octets': 17,
  'job-media-sheets-completed': 0,
  'job-more-info': u'ipp://localhost:631/jobs/2',
  'job-name': u'Test Page',
  'job-originating-host-name': u'localhost',
  'job-originating-user-name': u'vds',
  'job-preserved': True,
  'job-printer-state-message': u"Can't create 
temporary file",
  'job-printer-state-reasons': [u'none'],
  'job-printer-up-time': 1224875942,

[Touch-packages] [Bug 1757493] [NEW] Login loop using virtualbox with 3D acceleration

2018-03-21 Thread BertN45

Public bug reported:

Since Tuesday 20-3-2018 Ubuntu Budgie 18.04 has a login loop. Before
that date everything worked fine. The login loop occurs in a Virtualbox
guest while 3D is enabled for the display.

On the same data Ubuntu 18.04 refused to show the login screen, but I
will file a seperate bug report for it. In its last display it said it
started the Display Manager, but no login screen was displayed. Maybe
the bugs are related.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu5
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: Wed Mar 21 12:47:33 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
InstallationDate: Installed on 2018-03-11 (10 days ago)
InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180310)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: innotek GmbH VirtualBox
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=77e5d5cc-4af0-4fdf-9387-d7db159bbc1e ro quiet splash zram.enabled=1
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic has-workaround regression reproducible 
single-occurrence ubuntu

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

Title:
  Login loop using virtualbox with 3D acceleration

Status in xorg package in Ubuntu:
  New

Bug description:
  Since Tuesday 20-3-2018 Ubuntu Budgie 18.04 has a login loop. Before
  that date everything worked fine. The login loop occurs in a
  Virtualbox guest while 3D is enabled for the display.

  On the same data Ubuntu 18.04 refused to show the login screen, but I
  will file a seperate bug report for it. In its last display it said it
  started the Display Manager, but no login screen was displayed. Maybe
  the bugs are related.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  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: Wed Mar 21 12:47:33 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2018-03-11 (10 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180310)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=77e5d5cc-4af0-4fdf-9387-d7db159bbc1e ro quiet splash zram.enabled=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias:

[Touch-packages] [Bug 1708409] Re: kdump service does not start after configure/reboot

2018-03-21 Thread Andrew Cloke

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

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

Title:
  kdump service does not start after configure/reboot

Status in The Ubuntu-power-systems project:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Artful:
  Invalid
Status in systemd source package in Artful:
  Fix Released
Status in makedumpfile source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-02 01:45:01 ==
  kdump service does not start after configure/reboot

  --Problem Description---
  kdump service does not start after configure/reboot. It has to be 
started/loaded manually, everytime after reboot.

  # kdump-config status
  current state   : Not ready to kdump

  
  ---uname output---
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux 
   
  Machine Type/Model = Power 8/8247-22L 

  Additional Info-
  # cat /proc/cmdline
  root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 
console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
   
  ---Steps to Reproduce---
  1. installed linux-crashdump
  2. edited the kdump-tools.cfg crashkernel cmdline to above
  3. update-grub
  4. reboot

  Expected:
  kdump-config to be loaded by default after reboot

  # kdump-config status
  current state   : Not ready to kdump

  # service kdump-tools status
  * kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: inactive (dead)

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

  systemd in artful is not properly picking up the unit files in 
  /etc/systemd/system/default.target.wants

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

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

[Touch-packages] [Bug 1754186] Re: Night Light only affects a single monitor now

2018-03-21 Thread Paul White

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

** This bug has been marked a duplicate of bug 1757280
   Night Light only works on one Monitor

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

Title:
  Night Light only affects a single monitor now

Status in xorg package in Ubuntu:
  New

Bug description:
  The Display settings have a "Night Light" option which allows reducing blue 
light at night.
  In Ubuntu 17.10, this worked great, and the setting took effect on all 3 of 
my monitors.
  In Bionic, only the 1st monitor is affected; the other 2 remain at the 
default color temperature.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Mar  7 17:51:02 2018
  DistUpgraded: 2018-03-07 12:52:16,474 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / 
R9 280X] [1002:6798] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Double D HD 7970 Black Edition [1682:3211]
  InstallationDate: Installed on 2014-08-21 (1294 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=98fea0b5-8fa6-4625-bae5-b85a70783a13 ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-03-07 (0 days ago)
  dmi.bios.date: 04/18/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1208
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1208:bd04/18/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Oct  7 12:18:20 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1.1
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1755885] Re: Night Light won't turn on after start on display #1

2018-03-21 Thread Paul White

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

** This bug has been marked a duplicate of bug 1757280
   Night Light only works on one Monitor

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

Title:
  Night Light won't turn on after start on display #1

Status in xorg package in Ubuntu:
  New

Bug description:
  I have two displays and have Night Light mode enabled with Sunset to
  Sunrise setting (tried to change it into Manual, but this didn't make
  any difference).

  It was perfectly OK some time before, but now only display #2 is
  started with the Night Light mode switched on.

  I can work around it: go to the Display Settings, try to switch into
  non-native mode for Display #1 and it switched into it with Night
  Light enabled. Then choose not to keep settings and it returns into
  native resolution with Night Light on.

  Not all changes help to switch the mode on though. For instance,
  mirroring screen doesn't switch it on.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.42  Sat Mar  3 04:10:22 
PST 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Mar 14 21:31:45 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.15.0-10-generic, x86_64: installed
   nvidia, 390.42, 4.15.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e5]
  InstallationDate: Installed on 2018-02-05 (37 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=68661197-00b4-4652-9c8f-2ef606012d2d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/17/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-K/USB 3.1
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0702:bd03/17/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-K/USB3.1:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 997483] Re: VT_WAITACTIVE does not work well with a multiseat setup

2018-03-21 Thread dino99

** Changed in: lightdm
   Status: Incomplete => Invalid

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

Title:
  VT_WAITACTIVE does not work well with a multiseat setup

Status in Light Display Manager:
  Invalid
Status in lightdm package in Ubuntu:
  Expired

Bug description:
  Related to the fix introduced in bug #851612 .

  Saw this in lightdm.log (system call interrupted because of ctrl-alt-del 
pressed):
  [+2.97s] DEBUG: New display ready, switching to it
  [+2.97s] DEBUG: Activating VT 8
  [+77.56s] WARNING: Error using VT_WAITACTIVE 8 on /dev/console: Interrupted 
system call
  [+77.56s] DEBUG: Got signal 15 from process 1
  [+77.56s] DEBUG: Caught Terminated signal, shutting down

  And in x-1-greeter.log:
  [+0.48s] DEBUG: Loading users from org.freedesktop.Accounts
  [+0.48s] DEBUG: Loading user /org/freedesktop/Accounts/User1001
  [+0.50s] DEBUG: Loading user /org/freedesktop/Accounts/User1000
  [+50.56s] WARNING: Error getting session list from 
org.freedesktop.DisplayManager: Timeout was reached

  On vt7, unity-greeter would get stuck after password input.
  On vt8, unity-greeter appears after that "getting session list timeout", 
which is about a minute later than vt7, and does not have a password input 
field.

  lightdm blocked by VT_WAITACTIVE may be the cause...

  Tested with lightdm 1.2.0-0ubuntu2 in precise.

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

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

[Touch-packages] [Bug 1757444] Re: [Ubuntu SSO] When a second opt is required, text entry should be empty.

2018-03-21 Thread Ubuntu Foundations Team Bug Bot

The attachment "goa.debidff" seems to be a debdiff.  The ubuntu-sponsors
team has been subscribed to the bug report so that they can review and
hopefully sponsor the debdiff.  If the attachment isn't a patch, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  [Ubuntu SSO] When a second opt is required, text entry should be
  empty.

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

Bug description:
  When a second otp is required the text entry should be cleared.

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

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

[Touch-packages] [Bug 1757470] Re: apport autopkgtests broken (valgrind error) LXC regression?

2018-03-21 Thread LocutusOfBorg

** No longer affects: lxc (Ubuntu)

** Summary changed:

- apport autopkgtests broken (valgrind error) LXC regression?
+ apport autopkgtests broken (valgrind error) toolchain regression?

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

Title:
  apport autopkgtests broken (valgrind error) toolchain regression?

Status in apport package in Ubuntu:
  New

Bug description:
  --- Testing apport_valgrind ---
  test_help_display (__main__.T)
  help display ... ok
  test_intentional_mem_leak_detection (__main__.T)
  apport-valgrind log reports intentional memory leak ... ok
  test_invalid_args (__main__.T)
  return code is not 0 when invalid args are passed ... ok
  test_sandbox_cache_options (__main__.T)
  apport-valgrind creates a user specified sandbox and cache ... WARNING: 
/lib/x86_64-linux-gnu/libc.so.6 is needed, but cannot be mapped to a package
  ERROR: Cannot find package which ships ExecutablePath /bin/true

  Interrupted while creating sandbox
  ERROR
  test_unpackaged_exe (__main__.T)
  apport-valgrind creates valgrind log on unpackaged executable ... 
/tmp/autopkgtest.aOT0xm/autopkgtest_tmp/apport-tests
  ok
  test_valgrind_min_installed (__main__.T)
  valgrind is installed and recent enough ... ok
  test_vlog_created (__main__.T)
  apport-valgrind creates valgrind.log with expected content ... ok

  ==
  ERROR: test_sandbox_cache_options (__main__.T)
  apport-valgrind creates a user specified sandbox and cache
  --
  Traceback (most recent call last):
File "./test_apport_valgrind.py", line 143, in test_sandbox_cache_options
  subprocess.check_call(cmd)
File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['apport-valgrind', '--sandbox-dir', 
'/tmp/tmpbvxep0y2/test-sandbox', '--cache', '/tmp/tmpbvxep0y2/test-cache', 
'true']' returned non-zero exit status 1.

  --
  Ran 7 tests in 30.319s

  FAILED (errors=1)
  --- Testing backend_apt_dpkg ---

  the regression seems to indicate a coreutils installation issue
  apport-valgrind creates a user specified sandbox and cache ... Installing 
extra package coreutils to get ExecutablePath
  Sandbox directory: /tmp/tmpoytew5vn/test-sandbox
  Cache directory: /tmp/tmpoytew5vn/test-cache
  ok

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

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

[Touch-packages] [Bug 1756987] Re: chrony install does not stop systemd-timesyncd

2018-03-21 Thread ChristianEhrhardt

The way the newer versions solve this is to have a native systemd
service and in there there is:

Conflicts=systemd-timesyncd.service openntpd.service

That ensures only one of these can be started.

Xenial has no systemd service at all, it has sysV and uses the systemd 
generator.
So there is no "just add the line" fix available.

Xenial as-is
$ timedatectl status
 Network time on: yes
NTP synchronized: yes
 RTC in local TZ: no
systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
   Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
  Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
   └─disable-with-time-daemon.conf
   Active: active (running) since Wed 2018-03-21 16:00:19 UTC; 1min 30s ago

This isn't even fully protected if you install ntp (not chrony) as it
was the ntp server back in Xenial. (Right after install it still runs).

What stops it there for NTPd is that this uses a config dir which pulls in:
  /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

So any further starts will be blocked:
# don't run timesyncd if we have another NTP daemon installed
ConditionFileIsExecutable=!/usr/sbin/ntpd
ConditionFileIsExecutable=!/usr/sbin/openntpd
ConditionFileIsExecutable=!/usr/sbin/chronyd
ConditionFileIsExecutable=!/usr/sbin/VBoxService

You see that if you check systemd-timesyncd.service:
$ systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
   Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
  Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
   └─disable-with-time-daemon.conf
   Active: inactive (dead)
Condition: start condition failed at Wed 2018-03-21 16:06:42 UTC; 44s ago
   ConditionFileIsExecutable=!/usr/sbin/ntpd was not met

After installing Chrony this is the same:

Condition: start condition failed at Wed 2018-03-21 16:11:37 UTC; 1s ago
   ConditionFileIsExecutable=!/usr/sbin/chronyd was not met

That is good (no special issue to chrony) and bad (actually all
timeservers "collide" right after install).

A reboot or restart will pick that up.
OTOH it is discouraged to start/stop/restart other packages services form a 
postinst - as the first thought would be to do refresh for that condition after 
installing any of these.

Given that there was not a single complaint about it in 2 years of
Xenial other than us now looking for it in detail I'd rate it low, but
it is a valid issue.

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

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

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

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

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

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

Title:
  chrony install does not stop systemd-timesyncd

Status in chrony package in Ubuntu:
  Fix Released
Status in ntp package in Ubuntu:
  New
Status in openntpd package in Ubuntu:
  New
Status in chrony source package in Xenial:
  New
Status in ntp source package in Xenial:
  Confirmed
Status in openntpd source package in Xenial:
  New
Status in chrony source package in Artful:
  New
Status in ntp source package in Artful:
  New
Status in openntpd source package in Artful:
  New
Status in chrony source package in Bionic:
  Fix Released
Status in ntp source package in Bionic:
  New
Status in openntpd source package in Bionic:
  New

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  root@ubuntu:~# uname -a
  Linux ubuntu 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  2. 
  root@ubuntu:~# apt-cache policy systemd
  systemd:
Installed: 229-4ubuntu21.1
Candidate: 229-4ubuntu21.1
Version table:
   *** 229-4ubuntu21.1 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  root@ubuntu:~# apt-cache policy chrony
  chrony:
Installed: 2.1.1-1
Candidate: 2.1.1-1
Version table:
   *** 2.1.1-1 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  3. installing chrony should stop systemd-timesyncd so they both don't
  try to adjust time

  4. after chrony is installed both systemd-timesyncd and chronyd are
  running.

  root@ubuntu:~# ps aux | egrep "(chrony|timesync)"
  systemd+  1086

[Touch-packages] [Bug 1757280] Re: Night Light only on one Monitor

2018-03-21 Thread Paul White

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

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

** Also affects: gnome-control-center via
   https://bugzilla.gnome.org/show_bug.cgi?id=780167
   Importance: Unknown
   Status: Unknown

** Summary changed:

- Night Light only on one Monitor
+ Night Light only works on one Monitor

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

Title:
  Night Light only works on one Monitor

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  
  Hi

  If I activate the Night Light mode with an external monitor connected,
  the mode is only on the external monitor activated.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  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
  CompositorRunning: None
  Date: Tue Mar 20 23:12:36 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:224b]
  InstallationDate: Installed on 2018-03-19 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319)
  MachineType: LENOVO 20HF0016MZ
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET45W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HF0016MZ
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET45W(1.24):bd02/26/2018:svnLENOVO:pn20HF0016MZ:pvrThinkPadT470s:rvnLENOVO:rn20HF0016MZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HF0016MZ
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1755144] Re: No audio on vlc or videos sound or video files

Apologies. I forgot to attach the log. I'm so used to Thunderbird where
it reminds you if you forget to make an attachment identified as needing
one from the email.

** Attachment added: "vlc-ffplay Verbose Terminal.txt"

https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1755144/+attachment/5085988/+files/vlc-ffplay%20Verbose%20Terminal.txt

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

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

Status in ffmpeg package in Ubuntu:
New
Status in pulseaudio package in Ubuntu:
Invalid

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

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

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

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

[Touch-packages] [Bug 1755144] Re: No audio on vlc or videos sound or video files

I ran the vlc & ffplay commands suggested above to give a log which is
attached. Is "mpgatofixed32 audio converter error: libmad error: bad
main_data_begin pointer" in the vlc significant as it's not in the ffplay log?
ffmpeg version 3.2.6-1~backport1.1~xenial package is part of the get-iplayer
ppa, which as I said before causes no problems in my other 2 Xenial PCs..

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

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

Status in ffmpeg package in Ubuntu:
New
Status in pulseaudio package in Ubuntu:
Invalid

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

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

[Touch-packages] [Bug 1757467] Re: no windows arround gnumeric program with wayland

2018-03-21 Thread tortosa

gnumeric's version is 1.12.35

** Project changed: yarock => gnumeric (Ubuntu)

** Package changed: gnumeric (Ubuntu) => wayland (Ubuntu)

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

Title:
  no windows arround gnumeric program with wayland

Status in wayland package in Ubuntu:
  New

Bug description:
  Sorry, english is not my native langage.

  I use gnumeric on a platform with kubuntu 18.04 (beta1) ant plasma
  5.12.3.

  Using plasma session, all seems ok.

  Using plasma WAYLAND session, gnumeric have no "windows" arround the
  program. So i can't change the size and to close gnumeric, I have to
  use the main menu.

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

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

[Touch-packages] [Bug 1757467] [NEW] no windows arround gnumeric program with wayland

You have been subscribed to a public bug:

Sorry, english is not my native langage.

I use gnumeric on a platform with kubuntu 18.04 (beta1) ant plasma
5.12.3.

Using plasma session, all seems ok.

Using plasma WAYLAND session, gnumeric have no "windows" arround the
program. So i can't change the size and to close gnumeric, I have to use
the main menu.

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

-- 
no windows arround gnumeric program with wayland
https://bugs.launchpad.net/bugs/1757467
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to wayland in Ubuntu.

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

[Touch-packages] [Bug 1757470] Re: apport autopkgtests broken (valgrind error) LXC regression?

2018-03-21 Thread Christian Brauner

Can we get some logs for the LXC containers that created and fail?
Otherwise this is very much a black box.

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

Title:
  apport autopkgtests broken (valgrind error) LXC regression?

Status in apport package in Ubuntu:
  New
Status in lxc package in Ubuntu:
  New

Bug description:
  --- Testing apport_valgrind ---
  test_help_display (__main__.T)
  help display ... ok
  test_intentional_mem_leak_detection (__main__.T)
  apport-valgrind log reports intentional memory leak ... ok
  test_invalid_args (__main__.T)
  return code is not 0 when invalid args are passed ... ok
  test_sandbox_cache_options (__main__.T)
  apport-valgrind creates a user specified sandbox and cache ... WARNING: 
/lib/x86_64-linux-gnu/libc.so.6 is needed, but cannot be mapped to a package
  ERROR: Cannot find package which ships ExecutablePath /bin/true

  Interrupted while creating sandbox
  ERROR
  test_unpackaged_exe (__main__.T)
  apport-valgrind creates valgrind log on unpackaged executable ... 
/tmp/autopkgtest.aOT0xm/autopkgtest_tmp/apport-tests
  ok
  test_valgrind_min_installed (__main__.T)
  valgrind is installed and recent enough ... ok
  test_vlog_created (__main__.T)
  apport-valgrind creates valgrind.log with expected content ... ok

  ==
  ERROR: test_sandbox_cache_options (__main__.T)
  apport-valgrind creates a user specified sandbox and cache
  --
  Traceback (most recent call last):
File "./test_apport_valgrind.py", line 143, in test_sandbox_cache_options
  subprocess.check_call(cmd)
File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['apport-valgrind', '--sandbox-dir', 
'/tmp/tmpbvxep0y2/test-sandbox', '--cache', '/tmp/tmpbvxep0y2/test-cache', 
'true']' returned non-zero exit status 1.

  --
  Ran 7 tests in 30.319s

  FAILED (errors=1)
  --- Testing backend_apt_dpkg ---

  the regression seems to indicate a coreutils installation issue
  apport-valgrind creates a user specified sandbox and cache ... Installing 
extra package coreutils to get ExecutablePath
  Sandbox directory: /tmp/tmpoytew5vn/test-sandbox
  Cache directory: /tmp/tmpoytew5vn/test-cache
  ok

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

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

[Touch-packages] [Bug 1020048] Re: after certain time printing to cups stops working

2018-03-21 Thread Raúl Vidal

I have to confirm this bug. 300 seconds timeout. CUPS does not reopen 
connections again. Notifiers are shutdown.
The workaround is to enable the web interface. But this should not be 
necessary. CUPS should work without the web interface, as that is the default 
behaviour defined by upstream.

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

Title:
  after certain time printing to cups stops working

Status in LibreOffice:
  Invalid
Status in cups package in Ubuntu:
  Fix Released
Status in libreoffice package in Ubuntu:
  Invalid
Status in cups source package in Precise:
  Fix Released
Status in libreoffice source package in Precise:
  Invalid

Bug description:
  SRU justification:

  [Impact]

  * When the CUPS client connects to a remote cupsd over TCP, the server 
closes an idle connection after 5 minutes and the client does not reconnect.

  * LibreOffice is affected because it keeps a CUPS connection open. The 
effect is that printing to a remote cupsd is no longer possible after 
LibreOffice has been open for 5 minutes.

  [Test Case]

  * This can be reproduced on a desktop system. You don't need a separate 
CUPS server.

  * You need at least one print queue in CUPS. If you don't have a 
printer, install "cups-pdf".

  * Optional, configure CUPS with a shorter timeout for testing:

sudo cupsctl Timeout=30 # seconds
sudo restart cups

  * Configure the CUPS client to use a TCP socket:

mkdir ~/.cups
echo ServerName 127.0.0.1 > ~/.cups/client.conf

  * Open LibreOffice. Press Ctrl-P to open the Print dialog. Press Esc to 
dismiss the dialog. Wait long enough for the timout to elapse (5 
minutes by default, or as per the Timeout setting).

  * Try to print. With cups in precise, the job simply vanishes and is 
never seen by the server. With the proposed patch, printing works 
normally.

  [Regression Potential]

  * The patch changes a library linked by many programs. An incorrect 
change might result in those programs misbehaving or crashing.

  * The patch is minimal, only adding a branch to handle a case that was 
previously not handled. The behaviour in other cases should be 
unchanged.

  [Other Info]

  * A workaround is to set the cupsd Timeout to a high value such as 8 
hours. This works on a server with few users, but on a busy server 
more and more connections are opened and eventually cupsd isn't able 
to accept new clients.

  Original description:

  == Problem ==
  In our institution we are running only printers through a cups server. while 
freshly opened document prints well, after some time (few minutes) clicking 
"print file directly" and menu item "print" do not work any more. after close 
and open again, thing prints correctly. i have checked what exactly is going on 
in such cases and logs on the cups server don't show any submissions and/or 
errors so that the thing is obviously stopped at the level of libreoffice.

  == Analysis ==
  LibreOffice loses it's TCP connection to CUPS after exactly 5 minutes of 
inactivity and does not manage to reconnect. To reproduce: print something (to 
a real printer or cups-pdf), wait 6 minutes not printing anything, and print 
again. Then, nothing is printed. You can watch the TCP connection using
  netstat -tpn | grep soffice
  While it's working, it looks like this:
  tcp0  0 127.0.0.1:48810 127.0.0.1:631   
ESTABLISHED 13976/soffice.bin
  After 5 minutes, that connection is gone permanently.

  WORKAROUND: To set the timeout to 24 hours add this line to the top of 
/etc/cups/cupsd.conf :
  Timeout 62400

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1020048/+subscriptions

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

[Touch-packages] [Bug 1757388] Re: bridge device is missing

2018-03-21 Thread Marco

I have the same problem after a dist-upgrade on Ubuntu 18.04 server. All
my bridges are not found anymore. There was an update from .5-9ubuntu2
to 1.5-15ubuntu1, however downgrading does NOT fix the problem. Manually
setting the bridges works, but this is not a permanent solution.

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

Title:
  bridge device is missing

Status in bridge-utils package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04: Since last dist-upgrade of the bridge-utils (2018-03-21)
  the bridge netwok device 'br0' is missing. A 'ls /sys/class/net'
  prints the devices 'enp3s0  lo  lxcbr0  virbr0  virbr0-nic' only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1757388/+subscriptions

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

[Touch-packages] [Bug 1757470] Re: apport autopkgtests broken (valgrind error) LXC regression?

2018-03-21 Thread LocutusOfBorg

Timing and artifacts indicates an lxc regression:

liblxc-common   3.0.0~beta2-0ubuntu2 BAD
liblxc-common   3.0.0~beta1-0ubuntu3 GOOD

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

Title:
  apport autopkgtests broken (valgrind error) LXC regression?

Status in apport package in Ubuntu:
  New
Status in lxc package in Ubuntu:
  New

Bug description:
  --- Testing apport_valgrind ---
  test_help_display (__main__.T)
  help display ... ok
  test_intentional_mem_leak_detection (__main__.T)
  apport-valgrind log reports intentional memory leak ... ok
  test_invalid_args (__main__.T)
  return code is not 0 when invalid args are passed ... ok
  test_sandbox_cache_options (__main__.T)
  apport-valgrind creates a user specified sandbox and cache ... WARNING: 
/lib/x86_64-linux-gnu/libc.so.6 is needed, but cannot be mapped to a package
  ERROR: Cannot find package which ships ExecutablePath /bin/true

  Interrupted while creating sandbox
  ERROR
  test_unpackaged_exe (__main__.T)
  apport-valgrind creates valgrind log on unpackaged executable ... 
/tmp/autopkgtest.aOT0xm/autopkgtest_tmp/apport-tests
  ok
  test_valgrind_min_installed (__main__.T)
  valgrind is installed and recent enough ... ok
  test_vlog_created (__main__.T)
  apport-valgrind creates valgrind.log with expected content ... ok

  ==
  ERROR: test_sandbox_cache_options (__main__.T)
  apport-valgrind creates a user specified sandbox and cache
  --
  Traceback (most recent call last):
File "./test_apport_valgrind.py", line 143, in test_sandbox_cache_options
  subprocess.check_call(cmd)
File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['apport-valgrind', '--sandbox-dir', 
'/tmp/tmpbvxep0y2/test-sandbox', '--cache', '/tmp/tmpbvxep0y2/test-cache', 
'true']' returned non-zero exit status 1.

  --
  Ran 7 tests in 30.319s

  FAILED (errors=1)
  --- Testing backend_apt_dpkg ---

  the regression seems to indicate a coreutils installation issue
  apport-valgrind creates a user specified sandbox and cache ... Installing 
extra package coreutils to get ExecutablePath
  Sandbox directory: /tmp/tmpoytew5vn/test-sandbox
  Cache directory: /tmp/tmpoytew5vn/test-cache
  ok

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

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

[Touch-packages] [Bug 1757470] [NEW] apport autopkgtests broken (valgrind error) LXC regression?

2018-03-21 Thread LocutusOfBorg

Public bug reported:

--- Testing apport_valgrind ---
test_help_display (__main__.T)
help display ... ok
test_intentional_mem_leak_detection (__main__.T)
apport-valgrind log reports intentional memory leak ... ok
test_invalid_args (__main__.T)
return code is not 0 when invalid args are passed ... ok
test_sandbox_cache_options (__main__.T)
apport-valgrind creates a user specified sandbox and cache ... WARNING: 
/lib/x86_64-linux-gnu/libc.so.6 is needed, but cannot be mapped to a package
ERROR: Cannot find package which ships ExecutablePath /bin/true

Interrupted while creating sandbox
ERROR
test_unpackaged_exe (__main__.T)
apport-valgrind creates valgrind log on unpackaged executable ... 
/tmp/autopkgtest.aOT0xm/autopkgtest_tmp/apport-tests
ok
test_valgrind_min_installed (__main__.T)
valgrind is installed and recent enough ... ok
test_vlog_created (__main__.T)
apport-valgrind creates valgrind.log with expected content ... ok

==
ERROR: test_sandbox_cache_options (__main__.T)
apport-valgrind creates a user specified sandbox and cache
--
Traceback (most recent call last):
  File "./test_apport_valgrind.py", line 143, in test_sandbox_cache_options
subprocess.check_call(cmd)
  File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apport-valgrind', '--sandbox-dir', 
'/tmp/tmpbvxep0y2/test-sandbox', '--cache', '/tmp/tmpbvxep0y2/test-cache', 
'true']' returned non-zero exit status 1.

--
Ran 7 tests in 30.319s

FAILED (errors=1)
--- Testing backend_apt_dpkg ---

the regression seems to indicate a coreutils installation issue
apport-valgrind creates a user specified sandbox and cache ... Installing extra 
package coreutils to get ExecutablePath
Sandbox directory: /tmp/tmpoytew5vn/test-sandbox
Cache directory: /tmp/tmpoytew5vn/test-cache
ok

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

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

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

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

Title:
  apport autopkgtests broken (valgrind error) LXC regression?

Status in apport package in Ubuntu:
  New
Status in lxc package in Ubuntu:
  New

Bug description:
  --- Testing apport_valgrind ---
  test_help_display (__main__.T)
  help display ... ok
  test_intentional_mem_leak_detection (__main__.T)
  apport-valgrind log reports intentional memory leak ... ok
  test_invalid_args (__main__.T)
  return code is not 0 when invalid args are passed ... ok
  test_sandbox_cache_options (__main__.T)
  apport-valgrind creates a user specified sandbox and cache ... WARNING: 
/lib/x86_64-linux-gnu/libc.so.6 is needed, but cannot be mapped to a package
  ERROR: Cannot find package which ships ExecutablePath /bin/true

  Interrupted while creating sandbox
  ERROR
  test_unpackaged_exe (__main__.T)
  apport-valgrind creates valgrind log on unpackaged executable ... 
/tmp/autopkgtest.aOT0xm/autopkgtest_tmp/apport-tests
  ok
  test_valgrind_min_installed (__main__.T)
  valgrind is installed and recent enough ... ok
  test_vlog_created (__main__.T)
  apport-valgrind creates valgrind.log with expected content ... ok

  ==
  ERROR: test_sandbox_cache_options (__main__.T)
  apport-valgrind creates a user specified sandbox and cache
  --
  Traceback (most recent call last):
File "./test_apport_valgrind.py", line 143, in test_sandbox_cache_options
  subprocess.check_call(cmd)
File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['apport-valgrind', '--sandbox-dir', 
'/tmp/tmpbvxep0y2/test-sandbox', '--cache', '/tmp/tmpbvxep0y2/test-cache', 
'true']' returned non-zero exit status 1.

  --
  Ran 7 tests in 30.319s

  FAILED (errors=1)
  --- Testing backend_apt_dpkg ---

  the regression seems to indicate a coreutils installation issue
  apport-valgrind creates a user specified sandbox and cache ... Installing 
extra package coreutils to get ExecutablePath
  Sandbox directory: /tmp/tmpoytew5vn/test-sandbox
  Cache directory: /tmp/tmpoytew5vn/test-cache
  ok

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

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

[Touch-packages] [Bug 1755144] Re: No audio on vlc or videos sound or video files

Another piece of information. Looking at the documentation for ffmpeg,
it mentioned ffplay. So I tried that in Terminal (attached) and the
sound was working. So what's so different between ffmpeg a& ffplay? BTW
I reverted back to the get_iplayer ppa for ffmpeg as that ppa (using
ffmpeg) works Ok on my other barebones PC and laptop.

** Attachment added: "ffplay Terminal.txt"

https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1755144/+attachment/5085986/+files/ffplay%20Terminal.txt

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

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

Status in ffmpeg package in Ubuntu:
New
Status in pulseaudio package in Ubuntu:
Invalid

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

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

[Touch-packages] [Bug 1755144] Re: No audio on vlc or videos sound or video files

2018-03-21 Thread James Cowgill

To get more logs you can run:
 mplayer -v 
 ffplay -loglevel verbose 
 vlc --verbose=2 

To play files with ffmpeg you want to run "ffplay" not "ffmpeg".

Also I notice:
 ffmpeg version 3.2.6-1~backport1.1~xenial
This is another different version of ffmpeg you tried to install?

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

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

Status in ffmpeg package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Invalid

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

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

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

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

[Touch-packages] [Bug 559331] Re: Permanent "Printer-out-of-paper" message.

2018-03-21 Thread Paul Abraham

Any answers to this?

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

Title:
  Permanent "Printer-out-of-paper" message.

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: cups

  This probably has to do with CUPS. Version: 1.4.1- 4ubuntu2.4 (latest
  on Karmic).

  I was printing a document when the printer was out of paper and got a
  message that "The printer is out of paper". I went to reload it and
  clicked resume on the printer and printing carried on normally.

  From this point on, the message "The printer is out of paper" is permanently 
stuck on the printer. 
  - Every time i print, i get the message "The printer is out of paper", but 
the printing occurs without errors. 
  - The configuration tool (system-config-printer 1.1.12) shows the printer 
with the red error sign. When viewing the properties of said printer, in the 
"Ink/Toner Levels" section, i have the "Status Message":  "Printer 
HP-Officejet-Pro-k550 is out of paper". If i click refresh then i get a "CUPS 
server error": "There was an error during the CUPS operation: 
'client-error-document-format-not-supported'." (Not sure this is relevant). 

  
  Removing and reinstalling the printer fixes this.

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

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

[Touch-packages] [Bug 980519] Re: Random log off in Ubuntu 12.04 LTS

2018-03-21 Thread pun

My Lenovo logs me off when Android device plugged out from PC

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

Title:
  Random log off in Ubuntu 12.04 LTS

Status in Unity:
  Fix Released
Status in gnome-desktop package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Fix Released
Status in Fedora:
  New

Bug description:
  I get logged off from Ubuntu sometimes. There is no error message or
  any indication that it is going to log off. The screen goes black, and
  after 2-4 seconds, i get presented with the Ubuntu Log On Screen.

  There is no clear pattern (or at least if have not noticed any). One
  time i am working with Netbeans, another time i am using firefox. This
  also means that at present i can not clearly say what package might be
  causing this behaviour.

  I am fairly sure the problem lies in 12.04 (or more precise - the
  combination of 12.04 and the hardware i am using). I do not have the
  same problem running 11.04 or 11.10.

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

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

14:04  juliank: based on https://bugs.launchpad.net/ubuntu/+source/apt/+
bug/1750465/comments/10, are you suggesting I should hold on processing slangase
k's SRU upload? 
14:04  Launchpad bug 1750465 in plymouth (Ubuntu Artful) "upgrade attemp
ting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-
3ubuntu17 failed to install/upgrade: dependency problems - leaving triggers unpr
ocessed)" [Undecided,In progress]
14:05  rbasak: I'm not sure what he did precisely, I only saw the bug m
essages.
14:06  juliank: http://launchpadlibrarian.net/361447927/plymouth_0.9.2-3
ubuntu17_0.9.2-3ubuntu18.diff.gz is his artful SRU upload. 
14:06  That should be correct anyway.
14:06  And it probably fixes the bug even if we don't know the exact 
reason yet...
14:07  OK. If you and slangasek both agree on what we should land, I'm 
happy :) 
14:07  I'll accept assuming all the other SRU bits look OK.


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

** 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:
  New
Status in kubuntu-settings package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  New
Status in ubuntu-mate-artwork package in Ubuntu:
  New
Status in apt source package in Artful:
  New
Status in budgie-artwork source package in Artful:
  New
Status in kubuntu-settings source package in Artful:
  New
Status in plymouth source package in Artful:
  Fix Committed
Status in ubuntu-gnome-default-settings source package in Artful:
  New
Status in ubuntu-mate-artwork source package in Artful:
  New

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

[Touch-packages] [Bug 1755144] Re: No audio on vlc or videos sound or video files

Here is something really interesting. mplayer (from CLI) plays mp3 Ok. mplayer
has libav/ffmpeg dependencies of libavcodec-ffmpeg56, libavutil-ffmpeg &
libavformat-ffmpeg56. vlc only has the first 2 of those packages as
libav/ffmpeg dependencies. So my deduction is that this problem has nothing to
do with libav/ffmpeg.
However, attached Terminal output for running mplayer, ffmpeg & vlc doesn't
offer real clues to me: as mplayer seems to use libavformat, ffmpeg doesn't
tell me anything (thoughit might to you) & vlc says nothing to me.
Could you take a look at the output, particularly of the ffmpeg one?

** Attachment added: "mplayer-ffmpeg-vlc Terminal.txt"

https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1755144/+attachment/5085963/+files/mplayer-ffmpeg-vlc%20Terminal.txt

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

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

Status in ffmpeg package in Ubuntu:
New
Status in pulseaudio package in Ubuntu:
Invalid

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

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

[Touch-packages] [Bug 1750465] Please test proposed package

Hello Stephen, or anyone else affected,

Accepted plymouth into artful-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/plymouth/0.9.2-3ubuntu18 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, details of your
testing will help us make a better decision.

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

-- 
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:
  New
Status in kubuntu-settings package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  New
Status in ubuntu-mate-artwork package in Ubuntu:
  New
Status in apt source package in Artful:
  New
Status in budgie-artwork source package in Artful:
  New
Status in kubuntu-settings source package in Artful:
  New
Status in plymouth source package in Artful:
  Fix Committed
Status in ubuntu-gnome-default-settings source package in Artful:
  New
Status in ubuntu-mate-artwork source package in Artful:
  New

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

[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.3-1ubuntu2

---
plymouth (0.9.3-1ubuntu2) bionic; 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, 20 Mar 2018
23:15:58 -0700

** Changed in: plymouth (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:
  New
Status in kubuntu-settings package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  New
Status in ubuntu-mate-artwork package in Ubuntu:
  New
Status in apt source package in Artful:
  New
Status in budgie-artwork source package in Artful:
  New
Status in kubuntu-settings source package in Artful:
  New
Status in plymouth source package in Artful:
  In Progress
Status in ubuntu-gnome-default-settings source package in Artful:
  New
Status in ubuntu-mate-artwork source package in Artful:
  New

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 artful-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: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 01W6F7
  dmi.board.vendor:

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

2018-03-21 Thread Andre Tomt

systemd upgrades are now failing in my build chroots, and I suspect it
is related to this change.

Setting up systemd (234-2ubuntu12.3) ...
addgroup: The group `systemd-journal' already exists as a system group. Exiting.
[/usr/lib/tmpfiles.d/tmp.conf:15] Failed to replace specifiers: 
/tmp/systemd-private-%b-*
[/usr/lib/tmpfiles.d/tmp.conf:16] Failed to replace specifiers: 
/tmp/systemd-private-%b-*/tmp
[/usr/lib/tmpfiles.d/tmp.conf:17] Failed to replace specifiers: 
/var/tmp/systemd-private-%b-*
[/usr/lib/tmpfiles.d/tmp.conf:18] Failed to replace specifiers: 
/var/tmp/systemd-private-%b-*/tmp
ACL operation on "/var/log/journal" failed: No such file or directory
ACL operation on "/var/log/journal" failed: No such file or directory
chmod() of /var/log/journal via /proc/self/fd/3 failed: No such file or 
directory
dpkg: error processing package systemd (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 systemd
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

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

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

Bug description:
  [Impact]

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

  [Test Case]

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

  [Regression Potential]

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

  [Other Info]
   
   * Original bug report

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

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

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

  ## Related reference

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

  ## Recommended fix

  Restoring persistent logging as the default is recommended.

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

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

[Touch-packages] [Bug 1757444] Re: [Ubuntu SSO] When a second opt is required, text entry should be empty.

2018-03-21 Thread Andrea Azzarone

Please find attached a debdiff that addresses this issue.

** Attachment added: "goa.debidff"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1757444/+attachment/5085912/+files/goa.debidff

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

Title:
  [Ubuntu SSO] When a second opt is required, text entry should be
  empty.

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

Bug description:
  When a second otp is required the text entry should be cleared.

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

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

[Touch-packages] [Bug 1757444] [NEW] [Ubuntu SSO] When a second opt is required, text entry should be empty.

2018-03-21 Thread Andrea Azzarone

Public bug reported:

When a second otp is required the text entry should be cleared.

** Affects: gnome-online-accounts (Ubuntu)
 Importance: Medium
 Assignee: Andrea Azzarone (azzar1)
 Status: In Progress

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

** Changed in: gnome-online-accounts (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

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

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

Title:
  [Ubuntu SSO] When a second opt is required, text entry should be
  empty.

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

Bug description:
  When a second otp is required the text entry should be cleared.

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

-- 
Mailing list: https://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 1757256] Re: Apparmor profile gajim

2018-03-21 Thread george jetson

I'm getting the following error in my journal.


systemd-coredump[1101]: Process 1099 (gajim) of user 1000 dumped core.
 
  Stack trace of thread 2:
  #0  0x611ea4d9a860
raise (libc.so.6)
  #1  0x611ea4d9bec9
abort (libc.so.6)
  #2  0x611ea488bcee
Py_FatalError (libpython3.6m.so.1.0)
  #3  0x611ea488c168
n/a (libpython3.6m.so.1.0)
  #4  0x611ea49f624d
_Py_InitializeEx_Private (libpython3.6m.so.1.0)
  #5  0x611ea49ec34a
Py_Main (libpython3.6m.so.1.0)
  #6  0x029f72942c39
main (python3.6)
  #7  0x611ea4d86f4a
__libc_start_main (libc.so.6)
  #8  0x029f72942dba
_start (python3.6)


On 03/21/2018 01:00 PM, Mike Miller wrote:
> Still not working. Please help.
>
> the audit logs when launching gajim are:
>
> 
>
> type=SYSCALL msg=audit(1521623303.636:86): arch=c03e syscall=2
> success=no exit=-13 a0=659281e35d38 a1=90800 a2=6592816e73f0
> a3=659281e49000 items=1 ppid=1053 pid=1119 auid=1000 uid=0 gid=0 euid=0
> suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts0 ses=2 comm="gajim"
> exe="/usr/bin/python3.6" key=(null)
> type=CWD msg=audit(1521623303.636:86): cwd="/home/user"
> type=PATH msg=audit(1521623303.636:86): item=0 name="/usr/lib/python3.6"
> inode=19437 dev=00:17 mode=040755 ouid=0 ogid=0 rdev=00:00
> nametype=NORMAL cap_fp= cap_fi= cap_fe=0
> cap_fver=0
> type=PROCTITLE msg=audit(1521623303.636:86):
> proctitle=2F7573722F62696E2F707974686F6E002F7573722F62696E2F67616A696D
> type=AVC msg=audit(1521623303.637:87): apparmor="ALLOWED"
> operation="open" info="Failed name lookup - disconnected path" error=-13
> profile="/usr/bin/gajim" name="usr/lib/python3.6/lib-dynload" pid=1119
> comm="gajim" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
> type=SYSCALL msg=audit(1521623303.637:87): arch=c03e syscall=2
> success=no exit=-13 a0=659281e424d0 a1=90800 a2=6592816e73f0
> a3=659281e09000 items=1 ppid=1053 pid=1119 auid=1000 uid=0 gid=0 euid=0
> suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts0 ses=2 comm="gajim"
> exe="/usr/bin/python3.6" key=(null)
> type=CWD msg=audit(1521623303.637:87): cwd="/home/user"
> type=PATH msg=audit(1521623303.637:87): item=0
> name="/usr/lib/python3.6/lib-dynload" inode=17086 dev=00:17 mode=040755
> ouid=0 ogid=0 rdev=00:00 nametype=NORMAL cap_fp=
> cap_fi= cap_fe=0 cap_fver=0
> type=PROCTITLE msg=audit(1521623303.637:87):
> proctitle=2F7573722F62696E2F707974686F6E002F7573722F62696E2F67616A696D
> type=ANOM_ABEND msg=audit(1521623303.637:88): auid=1000 uid=0 gid=0
> ses=2 pid=1119 comm="gajim" exe="/usr/bin/python3.6" sig=6 res=1
>
> 
>
> The profile I used:
>
> # Last Modified: Wed Mar 21 00:06:33 2018
> #include 
>
> /usr/bin/gajim flags=(complain) {
>   #include 
>   #include 
>   #include 
>   /** rwk,
>   /home/user/** r,
>   /home/user/.local/share/gajim/** rwk,
>   /home/user/.cache/gajim/** rwk,
>   /usr/lib/python3.6/** rk,
>   /home/user/.local/lib/** rk,
>   /proc/*/net/arp rk,
>   owner "/home/*/.mozilla/firefox/Crash Reports/**" rk,
>   owner /home/*/ rk,
>   owner /home/*/.ICEauthority rk,
>   owner /home/*/.Xauthority rk,
>   owner /home/*/.cache/fontconfig/** rwk,
>   owner /home/*/.cache/gajim/** rwk,
>   owner /home/*/.config/** rwk,
>   owner /home/*/.local/lib/python2.7/site-packages/ rk,
>   owner /home/*/.local/lib/python3.6/site-packages/ rk,
>   owner /home/*/.local/share/applications/ rk,
>   owner /home/*/.local/share/gajim/* rwk,
>   owner /home/*/.local/share/* rwk,
>   owner /home/*/.mozilla/firefox/* rk,
>   owner /proc/*/fd/ rk,
>   owner /proc/*/mounts rk,
>
> On 03/21/2018 02:40 AM, Seth Arnold wrote:
>> Hello,
>>
>>  open("/home/user", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 EACCES 
>> (Permission denied)
>> ...
>>  open("/usr/lib/python3.6", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 
>> EACCES (Permission denied)
>> etc
>>
>> Probably these all generated DENIED lines in your logs.
>>
>> And probably running aa-logprof would prompt you about them. Allow them
>> as appropriate and probably you'll be good to go.
>>
>> 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/1757256

Title:
  Apparmor profile gajim

Status in apparmor package in Ubuntu:
  New

Bug description:
  Followed this guide:

[Touch-packages] [Bug 1750947] Re: pulseaudio print lots of error when selecting unavailable profile

> [Regression Potential]

> no regression possibility, since this commit is already in artful and
bionic.

No. Please review https://wiki.ubuntu.com/StableReleaseUpdates#Why and
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure and update the
bug description accordingly.

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

Title:
  pulseaudio print lots of error when selecting unavailable profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  New

Bug description:
  SRU Document:

  [Impact]

  A HDMI audio device usually has several output ports, each port
  represents a profile in pulseaudio, without this patch, the puseaudio
  always choose the first profile no matter it is active or not.

  [Test Case]

  connect each port of HDMI device, and check if the profile of that
  port is active or not.

  [Regression Potential]

  no regression possibility, since this commit is already in artful and
  bionic.

  [Other Info]

  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

  After printing out the error logs, the kernel crashes and system
  hangs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1750947/+subscriptions

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

[Touch-packages] [Bug 1661869] Please test proposed package

Hello Dustin, or anyone else affected,

Accepted avahi into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/avahi/0.6.32-1ubuntu1.1 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, details of your
testing will help us make a better decision.

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

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

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

Status in MAAS:
  Invalid
Status in avahi package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Invalid
Status in avahi source package in Trusty:
  Fix Committed
Status in lxd source package in Trusty:
  Invalid
Status in avahi source package in Xenial:
  Fix Committed
Status in lxd source package in Xenial:
  Invalid
Status in avahi source package in Artful:
  Fix Committed
Status in lxd source package in Artful:
  Invalid

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

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

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

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

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

  [Impact]

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

  [Test Case]

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

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

  [Regression Potential]

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

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

  [Other Info]

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

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

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

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

Hello Dustin, or anyone else affected,

Accepted avahi into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/avahi/0.6.31-4ubuntu1.2 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-trusty to verification-done-trusty. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-trusty. In either case, details of your
testing will help us make a better decision.

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

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

** Tags added: verification-needed verification-needed-trusty

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

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

Status in MAAS:
  Invalid
Status in avahi package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Invalid
Status in avahi source package in Trusty:
  Fix Committed
Status in lxd source package in Trusty:
  Invalid
Status in avahi source package in Xenial:
  Fix Committed
Status in lxd source package in Xenial:
  Invalid
Status in avahi source package in Artful:
  Fix Committed
Status in lxd source package in Artful:
  Invalid

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

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

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

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

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

  [Impact]

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

  [Test Case]

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

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

  [Regression Potential]

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

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

  [Other Info]

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

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

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

[Touch-packages] [Bug 1661869] Please test proposed package

Hello Dustin, or anyone else affected,

Accepted avahi into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/avahi/0.6.32~rc+dfsg-
1ubuntu2.1 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

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

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

** Tags added: verification-needed-artful

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

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

Status in MAAS:
  Invalid
Status in avahi package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Invalid
Status in avahi source package in Trusty:
  Fix Committed
Status in lxd source package in Trusty:
  Invalid
Status in avahi source package in Xenial:
  Fix Committed
Status in lxd source package in Xenial:
  Invalid
Status in avahi source package in Artful:
  Fix Committed
Status in lxd source package in Artful:
  Invalid

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

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

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

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

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

  [Impact]

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

  [Test Case]

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

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

  [Regression Potential]

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

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

  [Other Info]

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

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

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

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

Unsubscribed ~ubuntu-sponsors as there is nothing left to sponsor.

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

** Tags added: verification-needed-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/1661869

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

Status in MAAS:
  Invalid
Status in avahi package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Invalid
Status in avahi source package in Trusty:
  Fix Committed
Status in lxd source package in Trusty:
  Invalid
Status in avahi source package in Xenial:
  Fix Committed
Status in lxd source package in Xenial:
  Invalid
Status in avahi source package in Artful:
  Fix Committed
Status in lxd source package in Artful:
  Invalid

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

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

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

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

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

  [Impact]

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

  [Test Case]

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

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

  [Regression Potential]

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

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

  [Other Info]

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

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

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

[Touch-packages] [Bug 1754265] Re: packagekitd crashed with SIGSEGV in utilBuildPackageId()

This bug was fixed in the package packagekit - 1.1.9-1ubuntu1

---
packagekit (1.1.9-1ubuntu1) bionic; urgency=medium

  * Add might-fetch-non-archive.diff to prevent PackageKit from crashing
when using the mirror method (LP: #1754265)

 -- Julian Andres Klode   Wed, 21 Mar 2018 12:32:34
+0100

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

Title:
  packagekitd crashed with SIGSEGV in utilBuildPackageId()

Status in packagekit package in Ubuntu:
  Fix Released

Bug description:
  PackageKit seems to be crashing randomly on bionic, not sure why, did
  not investigate further yet.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: packagekit 1.1.7-1
  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
  Date: Thu Mar  8 08:35:34 2018
  ExecutablePath: /usr/lib/packagekit/packagekitd
  InstallationDate: Installed on 2017-12-08 (89 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/lib/packagekit/packagekitd
  SegvAnalysis:
   Segfault happened at: 0x7fca622a9ecc 
<_Z18utilBuildPackageIdRKN8pkgCache11VerIteratorE+124>: cmpb   $0x6,0x22(%rax)
   PC (0x7fca622a9ecc) ok
   source "$0x6" ok
   destination "0x22(%rax)" (0x0015f6da) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: packagekit
  StacktraceTop:
   utilBuildPackageId(pkgCache::VerIterator const&) () at 
/usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
   AptIntf::emitPackage(pkgCache::VerIterator const&, PkInfoEnum) () at 
/usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
   AcqPackageKitStatus::updateStatus(pkgAcquire::ItemDesc&, int) () at 
/usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
   pkgAcquire::Worker::RunMessages() () at 
/usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
   pkgAcquire::Worker::InFdReady() () at 
/usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
  Title: packagekitd crashed with SIGSEGV in utilBuildPackageId()
  UpgradeStatus: Upgraded to bionic on 2017-12-08 (89 days ago)
  UserGroups:

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

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

[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu

This bug was fixed in the package systemd - 229-4ubuntu21.2

---
systemd (229-4ubuntu21.2) xenial; urgency=medium

  [ Dimitri John Ledkov ]
  * udev: Mark ndb devices as inactive until connected. (LP: #696435)
  * networkd: in dhcp, change UseMTU default to true, to accept DHCP provided 
MTU by default.
(LP: #1717471)
  * sysctl: apply parameters in-order, instead of randomly. (LP: #1718444)
  * networkd: apply promote_secondaries, to make DHCP lease changes work.
(LP: #1721223)
  * shutdown: sync filesystems, before going into a killing spree.
(LP: #1722481)
  * sysctl: do not fail, when cannot apply sysctl changes due to read-only 
sysfs in containers.
(LP: #1734409)
  * networkd,wait-online: add RequiredForOnline to mark mandatory/optional 
links for boot.
(LP: #1737570)

  [ David Glasser ]
  * journald: don't reduce BurstRateLimit on low disk space (LP: #1732803)

 -- Dimitri John Ledkov   Wed, 21 Feb 2018 13:46:37
+

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

Title:
  networkd does not accept / set advertised mtu

Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in nplan source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Hosts may require a specific MTU to be set as passed by DHCP options. We 
should honor these settings to ensure proper communication of the host with the 
rest of the network.

  [Test case]
  1) Run netplan on a system that should receive MTU settings from DHCP.
  2) Validate that the MTU configuration provided by DHCP is applied to the 
right interface.

  [Regression Potential]
  If DHCP settings specify an invalid MTU setting which is currently being 
ignored and letting the systems communicate correctly with the network, then 
these systems would regress.

  ---

   Right, so as far as I can tell the neutron-api on lcy01 is
  configured to advertise an instance interface MTU of 1400, though
  that's lower than it has to be, and the new DHCP setup with networkd
  just doesn't respect that DHCP option.

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

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

[Touch-packages] [Bug 1734409] Re: systemd-sysctl: exit gracefully on EPERM/EACCESS

This bug was fixed in the package systemd - 229-4ubuntu21.2

---
systemd (229-4ubuntu21.2) xenial; urgency=medium

  [ Dimitri John Ledkov ]
  * udev: Mark ndb devices as inactive until connected. (LP: #696435)
  * networkd: in dhcp, change UseMTU default to true, to accept DHCP provided 
MTU by default.
(LP: #1717471)
  * sysctl: apply parameters in-order, instead of randomly. (LP: #1718444)
  * networkd: apply promote_secondaries, to make DHCP lease changes work.
(LP: #1721223)
  * shutdown: sync filesystems, before going into a killing spree.
(LP: #1722481)
  * sysctl: do not fail, when cannot apply sysctl changes due to read-only 
sysfs in containers.
(LP: #1734409)
  * networkd,wait-online: add RequiredForOnline to mark mandatory/optional 
links for boot.
(LP: #1737570)

  [ David Glasser ]
  * journald: don't reduce BurstRateLimit on low disk space (LP: #1732803)

 -- Dimitri John Ledkov   Wed, 21 Feb 2018 13:46:37
+

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

Title:
  systemd-sysctl: exit gracefully on EPERM/EACCESS

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * systemd-sysctl service fails in containers, due to read-only sysfs,
  which is normal.

  [Test Case]

   * Ensure systemd-sysctl is successful in containers, e.g. lxc & lxd

  [Regression Potential]

   * The application of sysctls fails anyway, but at least in this case
  false-errors are not reported and the container doesn't enter
  "degraded" state without a good reason.

  [Other Info]
   
   * Original bug report

  Hi everyone,

  systemd-sysctl in systemd versions prior to 232 will exit with FAILED
  when not being able to apply kernel variables. In containers it should
  simply move on and exit with SUCCESS. Upstream systemd carries
  appropriate patches for this already. The relevant commits are:

  411e869f497c7c7bd0688f1e3500f9043bc56e48
  39540de8abe24886693ca29a9caeea85c88089aa

  these should be backported to xenial's systemd.

  Christian

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

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

[Touch-packages] [Bug 1718444] Re: systemd-sysctl in Xenial is not obeying the order of the sysctls

This bug was fixed in the package systemd - 229-4ubuntu21.2

---
systemd (229-4ubuntu21.2) xenial; urgency=medium

  [ Dimitri John Ledkov ]
  * udev: Mark ndb devices as inactive until connected. (LP: #696435)
  * networkd: in dhcp, change UseMTU default to true, to accept DHCP provided 
MTU by default.
(LP: #1717471)
  * sysctl: apply parameters in-order, instead of randomly. (LP: #1718444)
  * networkd: apply promote_secondaries, to make DHCP lease changes work.
(LP: #1721223)
  * shutdown: sync filesystems, before going into a killing spree.
(LP: #1722481)
  * sysctl: do not fail, when cannot apply sysctl changes due to read-only 
sysfs in containers.
(LP: #1734409)
  * networkd,wait-online: add RequiredForOnline to mark mandatory/optional 
links for boot.
(LP: #1737570)

  [ David Glasser ]
  * journald: don't reduce BurstRateLimit on low disk space (LP: #1732803)

 -- Dimitri John Ledkov   Wed, 21 Feb 2018 13:46:37
+

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

Title:
  systemd-sysctl in Xenial is not obeying the order of the sysctls

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * sysctls are applied out of order

  [Test Case]

   * Monitor that sysctls are applied in-order, instead of out of order
  / random order.

  [Regression Potential]

   * Cherrypick of an upstream patch which is present in v232+ and in
  use in Ubuntu in later releases. The code changes are minimal,
  updating s/Hashmap/OrderedHashmap/ which is implemented and available
  in xenial's systemd.

  
https://github.com/systemd/systemd/commit/886cf982d3018f7451f0548dadbc05bd2d583bb6

  [Other Info]
   
   * Original bug report.

  systemd-sysctl in Xenial forces itself over procps by shipping a link
  for procps.service to systemd-sysctl.service. However, it does not
  obey the order both of the files and also of the sysctls within the
  files. Instead it uses a simple hashmap. As it turns out that's fixed
  upstream and systemd master uses an ordered hashmap because of this,
  which at least preserves order within single files. Traditionally
  files in sysctl.d have been prefixed with numbers to ensure an order
  and that's now completely non-deterministic on Xenial.

  Relevant upstream commit:
  
https://github.com/systemd/systemd/commit/886cf982d3018f7451f0548dadbc05bd2d583bb6

  Note that conf_files_list_nulstr in master sorts the configuration
  files using strcmp, so even order of configuration files should be
  obeyed.

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

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

[Touch-packages] [Bug 1734409] Update Released

2018-03-21 Thread Łukasz Zemczak

The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  systemd-sysctl: exit gracefully on EPERM/EACCESS

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * systemd-sysctl service fails in containers, due to read-only sysfs,
  which is normal.

  [Test Case]

   * Ensure systemd-sysctl is successful in containers, e.g. lxc & lxd

  [Regression Potential]

   * The application of sysctls fails anyway, but at least in this case
  false-errors are not reported and the container doesn't enter
  "degraded" state without a good reason.

  [Other Info]
   
   * Original bug report

  Hi everyone,

  systemd-sysctl in systemd versions prior to 232 will exit with FAILED
  when not being able to apply kernel variables. In containers it should
  simply move on and exit with SUCCESS. Upstream systemd carries
  appropriate patches for this already. The relevant commits are:

  411e869f497c7c7bd0688f1e3500f9043bc56e48
  39540de8abe24886693ca29a9caeea85c88089aa

  these should be backported to xenial's systemd.

  Christian

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

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

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

This bug was fixed in the package systemd - 229-4ubuntu21.2

---
systemd (229-4ubuntu21.2) xenial; urgency=medium

  [ Dimitri John Ledkov ]
  * udev: Mark ndb devices as inactive until connected. (LP: #696435)
  * networkd: in dhcp, change UseMTU default to true, to accept DHCP provided 
MTU by default.
(LP: #1717471)
  * sysctl: apply parameters in-order, instead of randomly. (LP: #1718444)
  * networkd: apply promote_secondaries, to make DHCP lease changes work.
(LP: #1721223)
  * shutdown: sync filesystems, before going into a killing spree.
(LP: #1722481)
  * sysctl: do not fail, when cannot apply sysctl changes due to read-only 
sysfs in containers.
(LP: #1734409)
  * networkd,wait-online: add RequiredForOnline to mark mandatory/optional 
links for boot.
(LP: #1737570)

  [ David Glasser ]
  * journald: don't reduce BurstRateLimit on low disk space (LP: #1732803)

 -- Dimitri John Ledkov   Wed, 21 Feb 2018 13:46:37
+

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

Title:
  Add support for RequiredForOnline in networkd

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

Bug description:
  [Impact]

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

  [Test Case]

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

  [Regression Potential]

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

  [Other Info]
   
   * Original bug report

  Add support for RequiredForOnline in networkd

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

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

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

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

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