[Touch-packages] [Bug 1766480] [NEW] Touchpad scroll and middle/right click not working as expected

[Misaki]

Public bug reported:

This could probably fixed through configuration, but it should work
automatically. Testing Ubuntu 18.04 beta, the touchpad has no special
regions for scrolling or anything.

By default in Xorg-based Ubuntu, top right corner of touchpad is middle-
click (mouse button 2), bottom right is right-click (mouse button 3),
and right side is vertical scrolling. For a while the bottom edge
defaulted to horizontal scrolling, but that changed in 17.10 or
something.

I'm aware that new touchpad interaction methods have developed, like
dragging with two fingers anywhere on the touchpad to scroll or
something. But people may not know this, or their touchpad might not
support multitouch.

(The Xorg-based settings for touchpad remain when switching back to Xorg
like with the Metacity Flashback login option.)

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

** Description changed:

  This could probably fixed through configuration, but it should work
  automatically. Testing Ubuntu 18.04 beta, the touchpad has no special
  regions for scrolling or anything.
  
  By default in Xorg-based Ubuntu, top right corner of touchpad is middle-
  click (mouse button 2), bottom right is right-click (mouse button 3),
  and right side is vertical scrolling. For a while the bottom edge
  defaulted to horizontal scrolling, but that changed in 17.10 or
  something.
  
  I'm aware that new touchpad interaction methods have developed, like
  dragging with two fingers anywhere on the touchpad to scroll or
  something. But people may not know this, or their touchpad might not
  support multitouch.
+ 
+ (The Xorg-based settings for touchpad remain when switching back to Xorg
+ like with the Metacity Flashback login option.)

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

Title:
  Touchpad scroll and middle/right click not working as expected

Status in wayland package in Ubuntu:
  New

Bug description:
  This could probably fixed through configuration, but it should work
  automatically. Testing Ubuntu 18.04 beta, the touchpad has no special
  regions for scrolling or anything.

  By default in Xorg-based Ubuntu, top right corner of touchpad is
  middle-click (mouse button 2), bottom right is right-click (mouse
  button 3), and right side is vertical scrolling. For a while the
  bottom edge defaulted to horizontal scrolling, but that changed in
  17.10 or something.

  I'm aware that new touchpad interaction methods have developed, like
  dragging with two fingers anywhere on the touchpad to scroll or
  something. But people may not know this, or their touchpad might not
  support multitouch.

  (The Xorg-based settings for touchpad remain when switching back to
  Xorg like with the Metacity Flashback login option.)

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

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

[Touch-packages] [Bug 1766479] [NEW] Resizing a window's left border to the right can cause it to scoot right

[Misaki]

Public bug reported:

Tested with 18.04 beta.

Created a small window, ffmpeg or ffplay showing a 2x2 pixel video. When
trying to move it, instead selected left border. Dragging right caused
the window to scoot away faster than the pointer was moving, vanishing
in less than a second.

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

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

Title:
  Resizing a window's left border to the right can cause it to scoot
  right

Status in wayland package in Ubuntu:
  New

Bug description:
  Tested with 18.04 beta.

  Created a small window, ffmpeg or ffplay showing a 2x2 pixel video.
  When trying to move it, instead selected left border. Dragging right
  caused the window to scoot away faster than the pointer was moving,
  vanishing in less than a second.

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

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

[Touch-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

[Kai-Heng Feng]

Can you try latest mainline kernel in [0]?

You need these two binaries:
linux-image-unsigned*generic*.deb
linux-modules*generic*.deb

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc2/

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

Title:
  kernel panic in Radeon driver while screen blank

Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I maintain a set of older kiosks running a mix of stock Ubuntu 14.04
  LTS and 16.04.  As we have gradually transitioned them to 16.04, we
  have noticed that the machines running 16.04.1 now regularly exhibit
  problems restoring from the blank screen which appears after a period
  of inactivity.

  This only occurs on the machines where we've installed 16.04.  All of
  the 16.04.1 installations are "fresh", that is, complete re-installs
  from scratch, and we install all security and other updates on a
  regular basis.  This problem has persisted right from the beginning
  when we started using 16.04.

  Following a period of user inactivity, the screen goes blank; this is,
  of course, expected.  When the user tries to restore the session by
  typing a key or moving the mouse, one of three outcomes occurs.

  Sometimes, the session restores normally.  Other times, the screen
  remains blank regardless of all normal keyboard input, until a magic
  SysRq  sequence is performed.  After Alt-SysRq-k, either the virtual
  console resets to a login screen (as expected after this SysRq
  sequence), or we get a kernel panic text screen (see attached screen
  photo) and can only restore via a hard power-cycle reboot.

  I will continue to try to capture a better trace output from one of
  these conditions, perhaps from /var/log/kern.log or by installing
  linux-crashdump (although these old machines may not have enough
  memory for the stock package).  But in the meantime, I'm attaching a
  photo of the kernel panic we see, which suggests a problem may reside
  in the Radeon driver ... which would seem possible, given the general
  blank-screen no-resume problem on these systems.

  Any advice on how to further capture any other needed details would be
  appreciated.  Thanks very much!

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

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

[Touch-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

[Chris Darroch]

Hit another kernel panic this weekend, again after having the screen go
blank and be unblankable via any normal method, then trying Alt-SysRq-k
and getting this panic (with a different stacktrace than the other, but
also going through the radeon driver and radeon_crtc_handle_flip).

I'll try to get the kern.log file matching this panic next weekend.

** Attachment added: "radeon_kernel_panic2.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5126315/+files/radeon_kernel_panic2.jpg

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

Title:
  kernel panic in Radeon driver while screen blank

Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I maintain a set of older kiosks running a mix of stock Ubuntu 14.04
  LTS and 16.04.  As we have gradually transitioned them to 16.04, we
  have noticed that the machines running 16.04.1 now regularly exhibit
  problems restoring from the blank screen which appears after a period
  of inactivity.

  This only occurs on the machines where we've installed 16.04.  All of
  the 16.04.1 installations are "fresh", that is, complete re-installs
  from scratch, and we install all security and other updates on a
  regular basis.  This problem has persisted right from the beginning
  when we started using 16.04.

  Following a period of user inactivity, the screen goes blank; this is,
  of course, expected.  When the user tries to restore the session by
  typing a key or moving the mouse, one of three outcomes occurs.

  Sometimes, the session restores normally.  Other times, the screen
  remains blank regardless of all normal keyboard input, until a magic
  SysRq  sequence is performed.  After Alt-SysRq-k, either the virtual
  console resets to a login screen (as expected after this SysRq
  sequence), or we get a kernel panic text screen (see attached screen
  photo) and can only restore via a hard power-cycle reboot.

  I will continue to try to capture a better trace output from one of
  these conditions, perhaps from /var/log/kern.log or by installing
  linux-crashdump (although these old machines may not have enough
  memory for the stock package).  But in the meantime, I'm attaching a
  photo of the kernel panic we see, which suggests a problem may reside
  in the Radeon driver ... which would seem possible, given the general
  blank-screen no-resume problem on these systems.

  Any advice on how to further capture any other needed details would be
  appreciated.  Thanks very much!

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

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

[Touch-packages] [Bug 1766440] [NEW] GDM does not default to primary monitor

[Michael DeFrancesco]

Public bug reported:

I have my monitor in the hdmi port of my gtx780 and my tv in the displayport.
Something about X seems to have a bias towards the dp output.

During the installer I had to unplug the tv (displayport) and continue
the installation. When I plug it in I have to use super + p to switch to
'extend' instead of duplicate. This has a high probability to make the
mouse unable to click anywhere in gnome.

>From this point I am able to set my monitor as the primary monitor and gnome 
>works as expected.
I rebooted and gdm still defaulted to my secondary (dp) monitor. I blindly 
logged in (enter + password + enter) and the desktop switched a few times 
between tv as default and monitor as default. It finally settled on the monitor 
as default however I could not click anywhere in gnome.

I was able to get control again by pressing the window button, typing
and opening a program, from here I was able to alt-tab to the program
and was able to click on the desktop again. From here I went to settings
to verify my settings and saw that my setting of the monitor (hdmi) as
the primary monitor was still there.

I suspect grub is defaulting to displayport, passing this default to
gdm, then once gdm exits and gnome is loaded the proper default is
restored. However Gnome is not in 'focus' for some reason and it takes
work to fix this.

A separate effort should probably be crated around the super + p display
switching dialog as it has a high probability of locking a user out of
the session.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: wl 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.48  Thu Mar 22 00:42:57 
PDT 2018
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
.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.9-0ubuntu6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: communitheme:ubuntu:GNOME
Date: Tue Apr 24 00:25:36 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.15.0-15-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.15.0-19-generic, x86_64: installed
 nvidia, 390.48, 4.15.0-15-generic, x86_64: installed
 nvidia, 390.48, 4.15.0-19-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GK110 [GeForce GTX 780] [10de:1004] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. GK110 [GeForce GTX 780] [3842:0783]
InstallationDate: Installed on 2018-04-22 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=559e0f30-0db2-4199-9f55-98c68bfee444 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/20/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1201
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z77-I DELUXE
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.:bvr1201:bd06/20/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-IDELUXE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: 

[Touch-packages] [Bug 1762465] Re: Nautilus sidebar theming is confusing

[Daniel van Vugt]

I think that would be OK as a solution, but not ideal.

I don't know anything about Ambiance-RW's motivations but it seems like
poor UI design to have two separate background colours. Each row is a
single object made up of an icon and a label. It's visually confusing
that each object is split across two columns.

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

Title:
  Nautilus sidebar theming is confusing

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

Bug description:
  The new theming of the Nautilus sidebar is confusing to users.  The icons and 
the icon labels have a different background colour, and when a specific 
location is selected the background colour of the selected icon changes to be 
the same as the background colour of the labels, while the other icons have a 
darker background colour.
  This is giving the impression that the text labels are a hierarchy of the 
icon, rather than simply being labels associated with each icon.

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

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

[Touch-packages] [Bug 1766317] Re: package rsyslog 8.32.0-1ubuntu3 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 1

[Daniel Richard G.]

I am seeing this same error in Bionic. Some further telemetry:

# /usr/sbin/rsyslogd -n
rsyslog internal message (3,-2066): could not load module 
'/usr/lib/x86_64-linux-gnu/rsyslog/lmnet.so', dlopen: 
/usr/lib/x86_64-linux-gnu/rsyslog/lmnet.so: failed to map segment from shared 
object
 [v8.32.0 try http://www.rsyslog.com/e/2066 ]
Error during class init for object 'conf' - failing...
rsyslogd initializiation failed - global classes could not be initialized.
Did you do a "make install"?
Suggested action: run rsyslogd with -d -n options to see what exactly fails.
rsyslogd: run failed with error -2066 (see rsyslog.h or try 
http://www.rsyslog.com/e/2066 to learn what that number means)

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

Title:
  package rsyslog 8.32.0-1ubuntu3 failed to install/upgrade: installed
  rsyslog package post-installation script subprocess returned error
  exit status 1

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  Setting up rsyslog (8.32.0-1ubuntu3) ...
  Installing new version of config file /etc/init.d/rsyslog ...
  Installing new version of config file /etc/logrotate.d/rsyslog ...
  Installing new version of config file /etc/rsyslog.conf ...
  The user `syslog' is already a member of `adm'.
  Job for rsyslog.service failed because the control process exited with error 
code.
  See "systemctl status rsyslog.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript rsyslog, action "restart" failed.
  ● rsyslog.service - System Logging Service
 Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor 
preset: enabled)
 Active: activating (auto-restart) (Result: exit-code) since Mon 2018-04-23 
19:40:06 CEST; 8ms ago
   Docs: man:rsyslogd(8)
 http://www.rsyslog.com/doc/
Process: 31888 ExecStart=/usr/sbin/rsyslogd -n (code=exited, 
status=1/FAILURE)
   Main PID: 31888 (code=exited, status=1/FAILURE)
  dpkg: error processing package rsyslog (--configure):
   installed rsyslog package post-installation script subprocess returned error 
exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: rsyslog 8.32.0-1ubuntu3
  Uname: Linux 4.16.3-041603-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Mon Apr 23 19:40:06 2018
  ErrorMessage: installed rsyslog package post-installation script subprocess 
returned error exit status 1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: rsyslog
  Title: package rsyslog 8.32.0-1ubuntu3 failed to install/upgrade: installed 
rsyslog package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1766317] Re: package rsyslog 8.32.0-1ubuntu3 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package rsyslog 8.32.0-1ubuntu3 failed to install/upgrade: installed
  rsyslog package post-installation script subprocess returned error
  exit status 1

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  Setting up rsyslog (8.32.0-1ubuntu3) ...
  Installing new version of config file /etc/init.d/rsyslog ...
  Installing new version of config file /etc/logrotate.d/rsyslog ...
  Installing new version of config file /etc/rsyslog.conf ...
  The user `syslog' is already a member of `adm'.
  Job for rsyslog.service failed because the control process exited with error 
code.
  See "systemctl status rsyslog.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript rsyslog, action "restart" failed.
  ● rsyslog.service - System Logging Service
 Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor 
preset: enabled)
 Active: activating (auto-restart) (Result: exit-code) since Mon 2018-04-23 
19:40:06 CEST; 8ms ago
   Docs: man:rsyslogd(8)
 http://www.rsyslog.com/doc/
Process: 31888 ExecStart=/usr/sbin/rsyslogd -n (code=exited, 
status=1/FAILURE)
   Main PID: 31888 (code=exited, status=1/FAILURE)
  dpkg: error processing package rsyslog (--configure):
   installed rsyslog package post-installation script subprocess returned error 
exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: rsyslog 8.32.0-1ubuntu3
  Uname: Linux 4.16.3-041603-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Mon Apr 23 19:40:06 2018
  ErrorMessage: installed rsyslog package post-installation script subprocess 
returned error exit status 1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: rsyslog
  Title: package rsyslog 8.32.0-1ubuntu3 failed to install/upgrade: installed 
rsyslog package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1766390] Re: /usr/bin/totem:5:__glXSendError:MakeContextCurrent:InternalMakeCurrentVendor:CommonMakeCurrent:destroy_objects

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1758287
   totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()

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

Title:
  
/usr/bin/totem:5:__glXSendError:MakeContextCurrent:InternalMakeCurrentVendor:CommonMakeCurrent:destroy_objects

Status in gstreamer1.0 package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1766390] [NEW] /usr/bin/totem:5:__glXSendError:MakeContextCurrent:InternalMakeCurrentVendor:CommonMakeCurrent:destroy_objects

[errors.ubuntu.com bug bridge]

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

Public bug reported:

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

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bionic

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

Title:
  
/usr/bin/totem:5:__glXSendError:MakeContextCurrent:InternalMakeCurrentVendor:CommonMakeCurrent:destroy_objects

Status in gstreamer1.0 package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1664979] Re: EQ overflowing. Additional events will be discarded until existing events are processed.

[Michael Truog]

The only time this occurs for me, is when I try to close a java
application (https://www.interactivebrokers.com/en/index.php?f=16045).
With this particular java application, it appears to happen more often,
if I use the window close button instead of the menu close item when
closing windows (but always it occurs when attempting to quit, so it
appears to be related to releasing memory).

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

Title:
  EQ overflowing. Additional events will be discarded until existing
  events are processed.

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I was on 14.04 and had no problem, but I started to have EQ overflow after 
upgrading to 14.04.3.
  Then I did fresh install of 16.04 on the same PC, but still EQ overflow 
occurs after closing SMPlayer.

  [640410.566] (WW) NVIDIA(0): WAIT (2, 8, 0x8000, 0x3d14, 0x4078)
  [640417.566] (WW) NVIDIA(0): WAIT (1, 8, 0x8000, 0x3d14, 0x4078)
  [640421.680] (WW) NVIDIA(0): WAIT (2, 8, 0x8000, 0x3d14, 0xf5d4)
  [640428.680] (WW) NVIDIA(0): WAIT (1, 8, 0x8000, 0x3d14, 0xf5d4)
  [640439.704] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc1, 0x3d14, 0xf680)
  [640446.704] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc1, 0x3d14, 0xf680)
  [640449.705] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cf7, 0x3d14, 0xf680)
  [640456.705] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cf7, 0x3d14, 0xf680)
  [640459.706] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc2, 0x3d14, 0xf724)
  [640466.706] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc2, 0x3d14, 0xf724)
  [640469.707] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cf8, 0x3d14, 0xf724)
  [640476.707] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cf8, 0x3d14, 0xf724)
  [640479.708] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc3, 0x3d14, 0xf7c8)
  [640486.708] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc3, 0x3d14, 0xf7c8)
  [640489.709] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cf9, 0x3d14, 0xf7c8)
  [640496.709] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cf9, 0x3d14, 0xf7c8)
  [640499.710] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc4, 0x3d14, 0xf86c)
  [640506.710] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc4, 0x3d14, 0xf86c)
  [640509.711] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cfa, 0x3d14, 0xf86c)
  [640516.711] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cfa, 0x3d14, 0xf86c)
  [640519.712] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc5, 0x3d14, 0xf910)
  [640526.712] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc5, 0x3d14, 0xf910)
  [640529.713] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cfb, 0x3d14, 0xf910)
  [640536.713] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cfb, 0x3d14, 0xf910)
  [640539.714] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc6, 0x3d14, 0xf9b4)
  [640546.714] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc6, 0x3d14, 0xf9b4)
  [640549.715] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cfc, 0x3d14, 0xf9b4)
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55b19d068ade]
  (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x55b19d04a583]
  (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x55b19cf22862]
  (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdc68ed+0x61f3) 
[0x7fdc68ed61f3]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdc68ed+0x6a5d) 
[0x7fdc68ed6a5d]
  (EE) 5: /usr/lib/xorg/Xorg (0x55b19ceb6000+0x94538) [0x55b19cf4a538]
  (EE) 6: /usr/lib/xorg/Xorg (0x55b19ceb6000+0xb9922) [0x55b19cf6f922]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7fdc6faec000+0x354b0) 
[0x7fdc6fb214b0]
  (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (__sched_yield+0x7) [0x7fdc6fbd5c47]
  (EE) 9: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so 
(0x7fdc6ab5d000+0xa7c61) [0x7fdc6ac04c61]
  (EE) 10: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so 
(0x7fdc6ab5d000+0xbb7bc) [0x7fdc6ac187bc]
  (EE) 11: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so 
(0x7fdc6ab5d000+0x5b1ec2) [0x7fdc6b10eec2]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55b19d068ade]
  (EE) 1: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x55b19cf22862]
  (EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdc68ed+0x61f3) 
[0x7fdc68ed61f3]
  (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdc68ed+0x6a5d) 
[0x7fdc68ed6a5d]
  (EE) 4: /usr/lib/xorg/Xorg (0x55b19ceb6000+0x94538) [0x55b19cf4a538]
  (EE) 5: /usr/lib/xorg/Xorg (0x55b19ceb6000+0xb9922) [0x55b19cf6f922]
  (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 

[Touch-packages] [Bug 1751813] syslog

[bugproxy]

--- Comment (attachment only) From vaish...@in.ibm.com 2018-03-29 06:38 
EDT---


** Attachment added: "syslog"
   
https://bugs.launchpad.net/bugs/1751813/+attachment/5126163/+files/file_164932.txt

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

Title:
  Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array
  [S822L] [ipr]

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in debian-installer package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  ---Problem Description---
  Ubuntu 18.04 ppc64el installer does detect IPR (IBM Power RAID) based 
HDD/RAID arrays

  Tried with current bionic and current bionic-proposed installers
  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/vmlinux
  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/initrd.gz
  kexec -l vmlinux -i initrd.gz
  kexec -e

  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/bionic-proposed/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/vmlinux
  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/bionic-proposed/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/initrd.gz
   kexec -l vmlinux -i initrd.gz
  kexec -e

  ---uname output---
  uname -a
  Linux ltciofvtr-s822l2-lp1 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 
09:05:20 UTC 2018 ppc64le GNU/Linux

  Machine Type = 8247-22L (S822L)
   
  ---boot type---
  Network boot
   
  ---bootloader---
  petitboot shell
   
  ---Kernel cmdline used to launch install---
  #cat /proc/cmdline

  ---Bootloader protocol---
  http
   
  ---Install repository type---
  Internet repository
   
  ---Install repository Location---
  US
   
  ---Point of failure---
  Problem during post-install (stage 2) configuration or other problem seen 
after reboot

  ===console error log===


?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
? SCSI1 (0,0,0) (sda) - 2.0 GB SMART USB-IBM  ?
? SCSI2 (0,0,0) (sdb) - 1.0 TB IBM T RDX-USB3 ?
? ?
??
? ?
???



   moves;  selects;  activates buttons

  
  ~ # lsmod | grep -i ipr
  ipr   148677  0
  ~ # modinfo ipr
  filename:   /lib/modules/4.13.0-32-generic/kernel/drivers/scsi/ipr.ko
  version:2.6.4
  license:GPL
  description:IBM Power RAID SCSI Adapter Driver
  author: Brian King 
  srcversion: 05BB872A11F65B3A73AB352
  alias:  pci:v1014d04DAsv1014sd04FBbc*sc*i*
  alias:  pci:v1014d04DAsv1014sd04FCbc*sc*i*
  alias:  pci:v1014d034Asv1014sd04C9bc*sc*i*
  alias:  pci:v1014d034Asv1014sd04C8bc*sc*i*
  alias:  pci:v1014d034Asv1014sd04C7bc*sc*i*
  alias:  pci:v1014d034Asv1014sd049Cbc*sc*i*
  alias:  pci:v1014d034Asv1014sd049Bbc*sc*i*
  alias:  pci:v1014d034Asv1014sd049Abc*sc*i*
  alias:  pci:v1014d034Asv1014sd0499bc*sc*i*
  alias:  pci:v1014d034Asv1014sd0475bc*sc*i*
  alias:  pci:v1014d034Asv1014sd0474bc*sc*i*
  alias:  pci:v1014d034Asv1014sd04CAbc*sc*i*
  alias:  pci:v1014d034Asv1014sd046Dbc*sc*i*
  alias:  pci:v1014d034Asv1014sd03FEbc*sc*i*
  alias:  pci:v1014d034Asv1014sd03FFbc*sc*i*
  alias:  pci:v1014d034Asv1014sd03FCbc*sc*i*
  alias:  pci:v1014d034Asv1014sd03FBbc*sc*i*
  alias:  pci:v1014d034Asv1014sd035Ebc*sc*i*
  alias:  pci:v1014d034Asv1014sd035Dbc*sc*i*
  alias:  pci:v1014d034Asv1014sd0357bc*sc*i*
  alias:   

[Touch-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)

[Daniel Holbert]

As noted on the github issue, Fedora doesn't seem to be affected at all
(when testing the same ibus/mutter/Firefox versions as in Ubuntu).  So
this is seeming to be Ubuntu-specific, fortunately/unfortunately...

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

Title:
  Ubuntu 18.04's ibus package breaks password fields in Firefox (by
  lowering & raising window whenever they're focused)

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise
  Firefox, whenever the user tries to focus an 
  field on a web page.  This is not a regression in Firefox, as the same
  Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug
  in ibus, because it only happens (in 18.04) when the environmental
  variable GTK_IM_MODULE is at its default value (which is "ibus").  It
  had this same value in 17.10 but the bug didn't happen there; hence,
  I'm guessing there was a change in ibus (or a related package) that
  caused this breakage / lowering+raising.

  This is pretty bad, because in some cases, the focus-loss can mean users are 
simply unable to fill in password fields that previously were working fine. 
(see "ACTUAL RESULTS" below)
   
  STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension:
  =
   1. Start Firefox. (fresh profile if you like)
   2. Install BitWarden from 
https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/
   3. Click the BitWarden toolbar icon to spawn a menu-pane.
   4. Click "Log in" at the bottom of that pane.
   5. Click the "Master Password" field.

  ACTUAL RESULTS:
   The menu pane disappears as soon as the Master Password field receives focus.
  EXPECTED RESULTS:
   I should be able to type in a password; pane shouldn't disappear.

  
  STEPS TO REPRODUCE #2, via Reddit:
  =
   1. Visit https://www.reddit.com/r/firefox/ (or any reddit page)
   2. Click "Log in or sign up in seconds" at the extreme upper right of the 
page.
(click the "Log in" part of that sentence)
   3. Try to click the password field (or "tab" into it) and type in some text.

  ACTUAL RESULTS:
   Try as you might, the password field never receives focus.
  EXPECTED RESULTS:
   Password field should accept focus & let me type text into it.

  If I run firefox from the command line with env var GTK_IM_MODULE="",
  then I get "expected results".  But with the default value of that env
  var, I get "actual results" (broken behavior, unable to enter
  passwords).


  I initially reported this in Firefox, here:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few
  dependent bugs for the usage-specific STR quoted above).  But I think
  it's a bug in ibus, hence filing here now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 18 23:22:05 2018
  InstallationDate: Installed on 2018-04-17 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1751813] partman

[bugproxy]

--- Comment (attachment only) From vaish...@in.ibm.com 2018-03-29 06:37 
EDT---


** Attachment added: "partman"
   
https://bugs.launchpad.net/bugs/1751813/+attachment/5126162/+files/file_164932.txt

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

Title:
  Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array
  [S822L] [ipr]

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in debian-installer package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  ---Problem Description---
  Ubuntu 18.04 ppc64el installer does detect IPR (IBM Power RAID) based 
HDD/RAID arrays

  Tried with current bionic and current bionic-proposed installers
  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/vmlinux
  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/initrd.gz
  kexec -l vmlinux -i initrd.gz
  kexec -e

  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/bionic-proposed/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/vmlinux
  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/bionic-proposed/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/initrd.gz
   kexec -l vmlinux -i initrd.gz
  kexec -e

  ---uname output---
  uname -a
  Linux ltciofvtr-s822l2-lp1 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 
09:05:20 UTC 2018 ppc64le GNU/Linux

  Machine Type = 8247-22L (S822L)
   
  ---boot type---
  Network boot
   
  ---bootloader---
  petitboot shell
   
  ---Kernel cmdline used to launch install---
  #cat /proc/cmdline

  ---Bootloader protocol---
  http
   
  ---Install repository type---
  Internet repository
   
  ---Install repository Location---
  US
   
  ---Point of failure---
  Problem during post-install (stage 2) configuration or other problem seen 
after reboot

  ===console error log===


?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
? SCSI1 (0,0,0) (sda) - 2.0 GB SMART USB-IBM  ?
? SCSI2 (0,0,0) (sdb) - 1.0 TB IBM T RDX-USB3 ?
? ?
??
? ?
???



   moves;  selects;  activates buttons

  
  ~ # lsmod | grep -i ipr
  ipr   148677  0
  ~ # modinfo ipr
  filename:   /lib/modules/4.13.0-32-generic/kernel/drivers/scsi/ipr.ko
  version:2.6.4
  license:GPL
  description:IBM Power RAID SCSI Adapter Driver
  author: Brian King 
  srcversion: 05BB872A11F65B3A73AB352
  alias:  pci:v1014d04DAsv1014sd04FBbc*sc*i*
  alias:  pci:v1014d04DAsv1014sd04FCbc*sc*i*
  alias:  pci:v1014d034Asv1014sd04C9bc*sc*i*
  alias:  pci:v1014d034Asv1014sd04C8bc*sc*i*
  alias:  pci:v1014d034Asv1014sd04C7bc*sc*i*
  alias:  pci:v1014d034Asv1014sd049Cbc*sc*i*
  alias:  pci:v1014d034Asv1014sd049Bbc*sc*i*
  alias:  pci:v1014d034Asv1014sd049Abc*sc*i*
  alias:  pci:v1014d034Asv1014sd0499bc*sc*i*
  alias:  pci:v1014d034Asv1014sd0475bc*sc*i*
  alias:  pci:v1014d034Asv1014sd0474bc*sc*i*
  alias:  pci:v1014d034Asv1014sd04CAbc*sc*i*
  alias:  pci:v1014d034Asv1014sd046Dbc*sc*i*
  alias:  pci:v1014d034Asv1014sd03FEbc*sc*i*
  alias:  pci:v1014d034Asv1014sd03FFbc*sc*i*
  alias:  pci:v1014d034Asv1014sd03FCbc*sc*i*
  alias:  pci:v1014d034Asv1014sd03FBbc*sc*i*
  alias:  pci:v1014d034Asv1014sd035Ebc*sc*i*
  alias:  pci:v1014d034Asv1014sd035Dbc*sc*i*
  alias:  pci:v1014d034Asv1014sd0357bc*sc*i*
  alias:  

[Touch-packages] [Bug 1751813] Re: Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array [S822L] [ipr]

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.15.0-19.20

---
linux (4.15.0-19.20) bionic; urgency=medium

  * linux: 4.15.0-19.20 -proposed tracker (LP: #1766021)

  * Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers (LP: #1765232)
- Revert "blk-mq: simplify queue mapping & schedule with each possisble CPU"
- Revert "genirq/affinity: assign vectors to all possible CPUs"

linux (4.15.0-18.19) bionic; urgency=medium

  * linux: 4.15.0-18.19 -proposed tracker (LP: #1765490)

  * [regression] Ubuntu 18.04:[4.15.0-17-generic #18] KVM Guest Kernel:
meltdown: rfi/fallback displacement flush not enabled bydefault (kvm)
(LP: #1765429)
- powerpc/pseries: Fix clearing of security feature flags

  * signing: only install a signed kernel (LP: #1764794)
- [Packaging] update to Debian like control scripts
- [Packaging] switch to triggers for postinst.d postrm.d handling
- [Packaging] signing -- switch to raw-signing tarballs
- [Packaging] signing -- switch to linux-image as signed when available
- [Config] signing -- enable Opal signing for ppc64el
- [Packaging] printenv -- add signing options

  * [18.04 FEAT] Sign POWER host/NV kernels (LP: #1696154)
- [Packaging] signing -- add support for signing Opal kernel binaries

  * Please cherrypick s390 unwind fix (LP: #1765083)
- s390/compat: fix setup_frame32

  * Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array [S822L]
[ipr] (LP: #1751813)
- d-i: move ipr to storage-core-modules on ppc64el

  * drivers/gpu/drm/bridge/adv7511/adv7511.ko missing (LP: #1764816)
- SAUCE: (no-up) rename the adv7511 drm driver to adv7511_drm

  * Miscellaneous Ubuntu changes
- [Packaging] Add linux-oem to rebuild test blacklist.

linux (4.15.0-17.18) bionic; urgency=medium

  * linux: 4.15.0-17.18 -proposed tracker (LP: #1764498)

  * Eventual OOM with profile reloads (LP: #1750594)
- SAUCE: apparmor: fix memory leak when duplicate profile load

linux (4.15.0-16.17) bionic; urgency=medium

  * linux: 4.15.0-16.17 -proposed tracker (LP: #1763785)

  * [18.04] [bug] CFL-S(CNP)/CNL GPIO testing failed (LP: #1757346)
- [Config]: Set CONFIG_PINCTRL_CANNONLAKE=y

  * [Ubuntu 18.04] USB Type-C test failed on GLK (LP: #1758797)
- SAUCE: usb: typec: ucsi: Increase command completion timeout value

  * Fix trying to "push" an already active pool VP (LP: #1763386)
- SAUCE: powerpc/xive: Fix trying to "push" an already active pool VP

  * hisi_sas: Revert and replace SAUCE patches w/ upstream (LP: #1762824)
- Revert "UBUNTU: SAUCE: scsi: hisi_sas: export device table of v3 hw to
  userspace"
- Revert "UBUNTU: SAUCE: scsi: hisi_sas: config for hip08 ES"
- scsi: hisi_sas: modify some register config for hip08
- scsi: hisi_sas: add v3 hw MODULE_DEVICE_TABLE()

  * Realtek card reader - RTS5243 [VEN_10EC_5260] (LP: #1737673)
- misc: rtsx: Move Realtek Card Reader Driver to misc
- updateconfigs for Realtek Card Reader Driver
- misc: rtsx: Add support for RTS5260
- misc: rtsx: Fix symbol clashes

  * Mellanox [mlx5] [bionic] UBSAN: Undefined behaviour in
./include/linux/net_dim.h (LP: #1763269)
- net/mlx5e: Fix int overflow

  * apparmor bug fixes for bionic (LP: #1763427)
- apparmor: fix logging of the existence test for signals
- apparmor: make signal label match work when matching stacked labels
- apparmor: audit unknown signal numbers
- apparmor: fix memory leak on buffer on error exit path
- apparmor: fix mediation of prlimit

  * dangling symlinks to loaded apparmor policy (LP: #1755563) // apparmor bug
fixes for bionic (LP: #1763427)
- apparmor: fix dangling symlinks to policy rawdata after replacement

  * [OPAL] Assert fail:
core/mem_region.c:447:lock_held_by_me(>free_list_lock)
(LP: #1762913)
- powerpc/watchdog: remove arch_trigger_cpumask_backtrace

  * [LTC Test] Ubuntu 18.04: tm_trap_test failed on P8 compat mode guest
(LP: #1762928)
- powerpc/tm: Fix endianness flip on trap

  * Add support for RT5660 codec based sound cards on Baytrail (LP: #1657674)
- SAUCE: (no-up) ASoC: Intel: Support machine driver for RT5660 on Baytrail
- SAUCE: (no-up) ASoC: rt5660: Add ACPI support
- SAUCE: (no-up): ASoC: Intel: bytcr-rt5660: Add MCLK, quirks
- [Config] CONFIG_SND_SOC_INTEL_BYTCR_RT5660_MACH=m, CONFIG_SND_SOC_RT5660=m

  * /dev/ipmi enumeration flaky on Cavium Sabre nodes (LP: #1762812)
- i2c: xlp9xx: return ENXIO on slave address NACK
- i2c: xlp9xx: Handle transactions with I2C_M_RECV_LEN properly
- i2c: xlp9xx: Check for Bus state before every transfer
- i2c: xlp9xx: Handle NACK on DATA properly

  * [18.04 FEAT] Add kvm_stat from kernel tree (LP: #1734130)
- tools/kvm_stat: simplify the sortkey function
- tools/kvm_stat: use a namedtuple for storing the values
- tools/kvm_stat: use a more pythonic way to iterate over dictionaries
- tools/kvm_stat: 

[Touch-packages] [Bug 1751813] ipr debug log

[bugproxy]

--- Comment (attachment only) From bren...@br.ibm.com 2018-04-16 13:36 
EDT---


** Attachment added: "ipr debug log"
   
https://bugs.launchpad.net/bugs/1751813/+attachment/5126164/+files/ipr_debug.txt

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

Title:
  Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array
  [S822L] [ipr]

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in debian-installer package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  ---Problem Description---
  Ubuntu 18.04 ppc64el installer does detect IPR (IBM Power RAID) based 
HDD/RAID arrays

  Tried with current bionic and current bionic-proposed installers
  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/vmlinux
  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/initrd.gz
  kexec -l vmlinux -i initrd.gz
  kexec -e

  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/bionic-proposed/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/vmlinux
  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/bionic-proposed/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/initrd.gz
   kexec -l vmlinux -i initrd.gz
  kexec -e

  ---uname output---
  uname -a
  Linux ltciofvtr-s822l2-lp1 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 
09:05:20 UTC 2018 ppc64le GNU/Linux

  Machine Type = 8247-22L (S822L)
   
  ---boot type---
  Network boot
   
  ---bootloader---
  petitboot shell
   
  ---Kernel cmdline used to launch install---
  #cat /proc/cmdline

  ---Bootloader protocol---
  http
   
  ---Install repository type---
  Internet repository
   
  ---Install repository Location---
  US
   
  ---Point of failure---
  Problem during post-install (stage 2) configuration or other problem seen 
after reboot

  ===console error log===


?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
? SCSI1 (0,0,0) (sda) - 2.0 GB SMART USB-IBM  ?
? SCSI2 (0,0,0) (sdb) - 1.0 TB IBM T RDX-USB3 ?
? ?
??
? ?
???



   moves;  selects;  activates buttons

  
  ~ # lsmod | grep -i ipr
  ipr   148677  0
  ~ # modinfo ipr
  filename:   /lib/modules/4.13.0-32-generic/kernel/drivers/scsi/ipr.ko
  version:2.6.4
  license:GPL
  description:IBM Power RAID SCSI Adapter Driver
  author: Brian King 
  srcversion: 05BB872A11F65B3A73AB352
  alias:  pci:v1014d04DAsv1014sd04FBbc*sc*i*
  alias:  pci:v1014d04DAsv1014sd04FCbc*sc*i*
  alias:  pci:v1014d034Asv1014sd04C9bc*sc*i*
  alias:  pci:v1014d034Asv1014sd04C8bc*sc*i*
  alias:  pci:v1014d034Asv1014sd04C7bc*sc*i*
  alias:  pci:v1014d034Asv1014sd049Cbc*sc*i*
  alias:  pci:v1014d034Asv1014sd049Bbc*sc*i*
  alias:  pci:v1014d034Asv1014sd049Abc*sc*i*
  alias:  pci:v1014d034Asv1014sd0499bc*sc*i*
  alias:  pci:v1014d034Asv1014sd0475bc*sc*i*
  alias:  pci:v1014d034Asv1014sd0474bc*sc*i*
  alias:  pci:v1014d034Asv1014sd04CAbc*sc*i*
  alias:  pci:v1014d034Asv1014sd046Dbc*sc*i*
  alias:  pci:v1014d034Asv1014sd03FEbc*sc*i*
  alias:  pci:v1014d034Asv1014sd03FFbc*sc*i*
  alias:  pci:v1014d034Asv1014sd03FCbc*sc*i*
  alias:  pci:v1014d034Asv1014sd03FBbc*sc*i*
  alias:  pci:v1014d034Asv1014sd035Ebc*sc*i*
  alias:  pci:v1014d034Asv1014sd035Dbc*sc*i*
  alias:  pci:v1014d034Asv1014sd0357bc*sc*i*
  alias:   

[Touch-packages] [Bug 1751813] hardware-summary

[bugproxy]

--- Comment (attachment only) From vaish...@in.ibm.com 2018-03-29 06:37 
EDT---


** Attachment added: "hardware-summary"
   
https://bugs.launchpad.net/bugs/1751813/+attachment/5126161/+files/file_164932.txt

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

Title:
  Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array
  [S822L] [ipr]

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in debian-installer package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  ---Problem Description---
  Ubuntu 18.04 ppc64el installer does detect IPR (IBM Power RAID) based 
HDD/RAID arrays

  Tried with current bionic and current bionic-proposed installers
  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/vmlinux
  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/initrd.gz
  kexec -l vmlinux -i initrd.gz
  kexec -e

  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/bionic-proposed/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/vmlinux
  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/bionic-proposed/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/initrd.gz
   kexec -l vmlinux -i initrd.gz
  kexec -e

  ---uname output---
  uname -a
  Linux ltciofvtr-s822l2-lp1 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 
09:05:20 UTC 2018 ppc64le GNU/Linux

  Machine Type = 8247-22L (S822L)
   
  ---boot type---
  Network boot
   
  ---bootloader---
  petitboot shell
   
  ---Kernel cmdline used to launch install---
  #cat /proc/cmdline

  ---Bootloader protocol---
  http
   
  ---Install repository type---
  Internet repository
   
  ---Install repository Location---
  US
   
  ---Point of failure---
  Problem during post-install (stage 2) configuration or other problem seen 
after reboot

  ===console error log===


?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
? SCSI1 (0,0,0) (sda) - 2.0 GB SMART USB-IBM  ?
? SCSI2 (0,0,0) (sdb) - 1.0 TB IBM T RDX-USB3 ?
? ?
??
? ?
???



   moves;  selects;  activates buttons

  
  ~ # lsmod | grep -i ipr
  ipr   148677  0
  ~ # modinfo ipr
  filename:   /lib/modules/4.13.0-32-generic/kernel/drivers/scsi/ipr.ko
  version:2.6.4
  license:GPL
  description:IBM Power RAID SCSI Adapter Driver
  author: Brian King 
  srcversion: 05BB872A11F65B3A73AB352
  alias:  pci:v1014d04DAsv1014sd04FBbc*sc*i*
  alias:  pci:v1014d04DAsv1014sd04FCbc*sc*i*
  alias:  pci:v1014d034Asv1014sd04C9bc*sc*i*
  alias:  pci:v1014d034Asv1014sd04C8bc*sc*i*
  alias:  pci:v1014d034Asv1014sd04C7bc*sc*i*
  alias:  pci:v1014d034Asv1014sd049Cbc*sc*i*
  alias:  pci:v1014d034Asv1014sd049Bbc*sc*i*
  alias:  pci:v1014d034Asv1014sd049Abc*sc*i*
  alias:  pci:v1014d034Asv1014sd0499bc*sc*i*
  alias:  pci:v1014d034Asv1014sd0475bc*sc*i*
  alias:  pci:v1014d034Asv1014sd0474bc*sc*i*
  alias:  pci:v1014d034Asv1014sd04CAbc*sc*i*
  alias:  pci:v1014d034Asv1014sd046Dbc*sc*i*
  alias:  pci:v1014d034Asv1014sd03FEbc*sc*i*
  alias:  pci:v1014d034Asv1014sd03FFbc*sc*i*
  alias:  pci:v1014d034Asv1014sd03FCbc*sc*i*
  alias:  pci:v1014d034Asv1014sd03FBbc*sc*i*
  alias:  pci:v1014d034Asv1014sd035Ebc*sc*i*
  alias:  pci:v1014d034Asv1014sd035Dbc*sc*i*
  alias:  pci:v1014d034Asv1014sd0357bc*sc*i*
  

[Touch-packages] [Bug 1676918] Re: Kernel 4.10+ regression: blackscreen when trying to resume from suspend

[Ubuntu QA Website]

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

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

** Tags added: iso-testing

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

Title:
  Kernel 4.10+ regression: blackscreen when trying to resume from
  suspend

Status in gnome-power-manager package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  When trying to resume after suspending my Lenovo Yoga 3 11, sometimes
  the screen remains black. The power LED switches from blinking to
  continuous light like it should but nothing else happens. The system
  does not react to anything. I tried to find something in the logs, but
  at least kern.log syslog and xorg.log never have any entries from this
  event.

  This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and
  Wayland.

  I'm currently testing Kernel 4.8 from the mainline ppa because of this
  other suspend resume bug, that appeared only with 17.04:

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912

  Update: So far I did not encounter any issues with suspend/resume with
  Kernel 4.8 and 4.9. This seems to be a regression in 4.10.

  ---
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-24 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  Package: systemd 232-19
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Tags:  zesty wayland-session
  Uname: Linux 4.8.17-040817-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1765646] Re: Ubuntu 16.04 - issue with bsdtar package installation

[Tomas Lipensky]

Thank you for your reply. In fact this is what I'm failing to. Only
manual installation helps. Maybe apt cannot distinguish what is higher
version or it is not in repo. I redo the excercises once again:

apt update
Hit:1 http://repo.steampowered.com/steam precise InRelease
Ign:2 http://cz.archive.ubuntu.com/ubuntu trusty InRelease  

Hit:3 http://ppa.launchpad.net/3v1n0/libfprint-vfs0090/ubuntu xenial InRelease  

Hit:4 http://archive.ubuntu.com/ubuntu xenial InRelease 

Hit:5 http://cz.archive.ubuntu.com/ubuntu trusty Release

Ign:6 http://repo.vivaldi.com/stable/deb stable InRelease   

Hit:7 http://ppa.launchpad.net/alessandro-strada/ppa/ubuntu xenial InRelease

Hit:8 http://security.ubuntu.com/ubuntu precise-security InRelease  

Get:9 http://repo.vivaldi.com/stable/deb stable Release [3 829 B]   

Hit:10 http://linux.teamviewer.com/deb stable InRelease 

Hit:11 http://linux.teamviewer.com/deb preview InRelease

Get:12 http://repo.vivaldi.com/stable/deb stable Release.gpg [819 B]

Hit:13 https://repo.skype.com/deb stable InRelease  

Hit:14 http://ppa.launchpad.net/jonathonf/firefox-esr/ubuntu xenial InRelease   
   
Hit:15 https://packages.microsoft.com/ubuntu/16.04/prod xenial InRelease
 
Hit:16 http://ppa.launchpad.net/libreoffice/libreoffice-5-4/ubuntu xenial 
InRelease 
Hit:18 http://ppa.launchpad.net/samoilov-lex/aftl-stable/ubuntu xenial 
InRelease
Hit:19 http://ocdc.hursley.ibm.com/ocdc xenial-safe InRelease   

Get:20 http://repo.vivaldi.com/stable/deb stable/main amd64 Packages [1 372 B]
Get:21 http://repo.vivaldi.com/stable/deb stable/main i386 Packages [1 373 B]
Fetched 7 393 B in 1s (6 197 B/s)   
Reading package lists... Done
Building dependency tree   
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.
W: http://security.ubuntu.com/ubuntu/dists/precise-security/InRelease: 
Signature by key 630239CC130E1A7FD81A27B140976EAF437D05B5 uses weak digest 
algorithm (SHA1)


apt search bsdtar
Sorting... Done
Full Text Search... Done
bsdtar/now 3.1.2-11ubuntu0.16.04.3 amd64 [installed,local]
  Implementation of the 'tar' program from FreeBSD

node-tar/xenial,xenial,now 1.0.3-2 all [installed,automatic]
  read and write portable tar archives module for Node.js


dpkg -r bsdtar
(Reading database ... 461573 files and directories currently installed.)
Removing bsdtar (3.1.2-11ubuntu0.16.04.3) ...
Processing triggers for man-db (2.7.5-1) ...



apt install bsdtar
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 bsdtar : Depends: libarchive13 (= 3.1.2-11build1) but 3.1.2-11ubuntu0.16.04.3 
is to be installed
E: Unable to correct problems, you have held broken packages.


wget 
http://security.ubuntu.com/ubuntu/pool/universe/liba/libarchive/bsdtar_3.1.2-11ubuntu0.16.04.3_amd64.deb
--2018-04-24 01:39:05--  
http://security.ubuntu.com/ubuntu/pool/universe/liba/libarchive/bsdtar_3.1.2-11ubuntu0.16.04.3_amd64.deb
Resolving security.ubuntu.com (security.ubuntu.com)... 91.189.91.26, 
91.189.91.23, 91.189.88.162, ...
Connecting to security.ubuntu.com (security.ubuntu.com)|91.189.91.26|:80... 
connected.
HTTP request sent, awaiting response... 200 OK
Length: 47878 (47K) [application/x-debian-package]
Saving to: ‘bsdtar_3.1.2-11ubuntu0.16.04.3_amd64.deb’

bsdtar_3.1.2-11ubuntu0.16.04.3_a
100%[===>]  46,76K
167KB/sin 0,3s

2018-04-24 01:39:06 (167 KB/s) -
‘bsdtar_3.1.2-11ubuntu0.16.04.3_amd64.deb’ saved [47878/47878]


apt install ./bsdtar_3.1.2-11ubuntu0.16.04.3_amd64.deb
Reading package lists... Done
Building dependency tree   
Reading state 

[Touch-packages] [Bug 1677924] Re: Local privilege escalation via guest user login

[Tyler Hicks]

@ogra it isn't obvious how the fix for this bug could have caused bug
1733557. Can you elaborate?

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

Title:
  Local privilege escalation via guest user login

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.18 series:
  Fix Released
Status in Light Display Manager 1.20 series:
  Fix Released
Status in Light Display Manager 1.22 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Xenial:
  Fix Released
Status in lightdm source package in Yakkety:
  Fix Released
Status in lightdm source package in Zesty:
  Fix Released

Bug description:
  It was discovered that a local attacker could watch for lightdm's
  guest-account script to create a /tmp/guest-XX file and then quickly 
create
  the lowercase representation of the guest user's home directory before lightdm
  could. This allowed the attacker to have control of the guest user's home
  directory and, subsequently, gain control of an arbitrary directory in the
  filesystem which could lead to privilege escalation.

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

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

[Touch-packages] [Bug 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion

[Dan Streetman]

> @ddstreet tested with the latest version of ifupdown and vlan from your PPA 
> with
> my 4 testscenario's and can confirm it works as expected. Interfaces come up
> correctly both when doing an "ifup -a" and during boot.

Excellent, thanks.

> One small thing I've noticed is a variation in the number of "Set name-type 
> for
> VLAN subsystem. Should be visible in /proc/net/vlan/config" messages in the
> ifup output depending on the different scenario, even though the number of
> vlans is the same in all 4 tests

That's because in your config tests with vlans on bonds, your call to
ifup -a doesn't actually process the bond or its vlans.  Your ifup -a
starts processing one of the bond slaves, and that causes the bond
interface to by created.  The bond creation is detected by udev, and
udev tells systemd, and systemd then invokes ifup directly on the bond
interface.  By the time your ifup -a has gotten to trying to bring up
the bond (or its vlans), they are already up because of udev detection
which invokes the 'hotplug' ifup that logs to systemd logs, not your
stdout.

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

Title:
  (on trusty) version 1.9-3ubuntu10.4 regression blocking boot
  completion

Status in ifupdown package in Ubuntu:
  In Progress
Status in vlan package in Ubuntu:
  In Progress
Status in ifupdown source package in Trusty:
  In Progress
Status in vlan source package in Trusty:
  In Progress
Status in ifupdown source package in Xenial:
  In Progress
Status in vlan source package in Xenial:
  In Progress
Status in ifupdown source package in Artful:
  In Progress
Status in vlan source package in Artful:
  In Progress
Status in ifupdown source package in Bionic:
  In Progress
Status in vlan source package in Bionic:
  In Progress
Status in ifupdown package in Debian:
  New
Status in vlan package in Debian:
  New

Bug description:
  When upgrading from version 1.9-3ubuntu10.1, a previously working
  machine can't successfully reboot completely.

  ifup is hanging indefinitely, with this process structure (from
  "pstree -a 1299"):

  ifup,1299 -a
└─run-parts,1501 /etc/network/if-pre-up.d
└─bridge,1502 /etc/network/if-pre-up.d/bridge
└─bridge,1508 /etc/network/if-pre-up.d/bridge
└─vlan,1511 /etc/network/if-pre-up.d/vlan
└─ifup,1532 eth0

  
  
  auto lo
  iface lo inet loopback

  auto eth0
  iface eth0 inet static
address 192.168.10.65
netmask 255.255.255.192
gateway 192.168.10.66

  auto eth0.11
address 192.168.11.1
netmask 255.255.255.0

  auto br1134
  iface br1134 inet manual
bridge_ports eth0.1134
bridge_stp off
bridge_fd 0
  

  The underlying interface eth0.1134 is not explicitly defined, but was
  previously auto-created during "ifup -a" execution. This apparently
  fails now.

  Reverting back to the 10.1 version re-establishes old behavior.

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

-- 
Mailing list: https://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 1764060] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

[Seth Arnold]

On Mon, Apr 23, 2018 at 01:20:26PM -, derisolde wrote:
> i have tested your answer, but:
> 
> isolde@isolde-MS-7817:~$ sudo apt-get remove python-ubuntu-sso-client
> [sudo] Passwort für isolde:
> Paketlisten werden gelesen... Fertig

Wow, that looks *realy* unhappy.

But this requires a *purge*, not a *remove*. Try again with:

sudo apt-get purge python-ubuntu-sso-client

and see if this gets you further along.

Thanks

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 1

Status in ca-certificates package in Ubuntu:
  Incomplete

Bug description:
  upgrading ca-certificates fails with:
  Updating certificates in /etc/ssl/certs...
  rehash: skipping duplicate certificate in Go_Daddy_Class_2_CA.pem
  dpkg: error processing package ca-certificates (--configure):
   installed ca-certificates package post-installation script subprocess 
returned error exit status 1

  or

  rehash: skipping duplicate certificate in UbuntuOne-Go_Daddy_Class_2_CA.pem
  dpkg: error processing package ca-certificates (--configure):
   installed ca-certificates package post-installation script subprocess 
returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Sun Apr 15 08:32:40 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2015-03-19 (1122 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1764060/+subscriptions

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

[Touch-packages] [Bug 1677924] Re: Local privilege escalation via guest user login

[Seth Arnold]

Noam, ogra's comment on bug 1733557 is for:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1733557

It automatically gets hyperlinked when viewing
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1677924 directly.

Thanks

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

Title:
  Local privilege escalation via guest user login

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.18 series:
  Fix Released
Status in Light Display Manager 1.20 series:
  Fix Released
Status in Light Display Manager 1.22 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Xenial:
  Fix Released
Status in lightdm source package in Yakkety:
  Fix Released
Status in lightdm source package in Zesty:
  Fix Released

Bug description:
  It was discovered that a local attacker could watch for lightdm's
  guest-account script to create a /tmp/guest-XX file and then quickly 
create
  the lowercase representation of the guest user's home directory before lightdm
  could. This allowed the attacker to have control of the guest user's home
  directory and, subsequently, gain control of an arbitrary directory in the
  filesystem which could lead to privilege escalation.

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

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

[Touch-packages] [Bug 1766337] [NEW] uncaught python exception : UnicodeDecodeError: 'utf-8' codec can't decode byte; invalid continuation byte

[Laurent Bonnaud]

Public bug reported:

Hi,

here is a python exception I got while reporting a bug:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in _run_hook
symb['add_info'](report, ui)
  File "/usr/share/apport/general-hooks/ubuntu.py", line 89, in add_info
check_attachment_for_errors(report, attachment)
  File "/usr/share/apport/general-hooks/ubuntu.py", line 208, in 
check_attachment_for_errors
trim_dpkg_log(report)
  File "/usr/share/apport/general-hooks/ubuntu.py", line 508, in trim_dpkg_log
report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line 
in lines])
  File "/usr/share/apport/general-hooks/ubuntu.py", line 508, in 
report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line 
in lines])
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe2 in position 3070: 
invalid continuation byte

It can also be seen here:

  https://launchpadlibrarian.net/367002573/HookError_ubuntu.txt

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apport 2.20.9-0ubuntu6
Uname: Linux 4.16.3-041603-generic x86_64
ApportLog:
 
ApportVersion: 2.20.9-0ubuntu6
Architecture: amd64
CurrentDesktop: MATE
Date: Mon Apr 23 20:13:24 2018
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  uncaught python exception : UnicodeDecodeError: 'utf-8' codec can't
  decode byte; invalid continuation byte

Status in apport package in Ubuntu:
  New

Bug description:
  Hi,

  here is a python exception I got while reporting a bug:

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in 
_run_hook
  symb['add_info'](report, ui)
File "/usr/share/apport/general-hooks/ubuntu.py", line 89, in add_info
  check_attachment_for_errors(report, attachment)
File "/usr/share/apport/general-hooks/ubuntu.py", line 208, in 
check_attachment_for_errors
  trim_dpkg_log(report)
File "/usr/share/apport/general-hooks/ubuntu.py", line 508, in trim_dpkg_log
  report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line 
in lines])
File "/usr/share/apport/general-hooks/ubuntu.py", line 508, in 
  report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line 
in lines])
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe2 in position 3070: 
invalid continuation byte

  It can also be seen here:

https://launchpadlibrarian.net/367002573/HookError_ubuntu.txt

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu6
  Uname: Linux 4.16.3-041603-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Apr 23 20:13:24 2018
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1766310] Re: apt-get install memtest86+ fails to create /etc/grub.d/20_memtest86+

[David Kastrup]

I haven't removed /etc/grub.d/memtest86+ myself: maybe it has been
declared a configuration file at some point of time and/or some
intermediate version of memtest86+ decided to remove it.  The
independent askubuntu experience would suggest something like that.

I have to admit that _now_ purging memtest86+ and reinstalling it via
apt-get install also installs the memtest+ program.

So while I really had to put up a fight until I got
/etc/grub.d/memtest86+ back into my system, I cannot at the current
point offer a recipe for how it got lost originally.  The anecdotal
report from the linked Askubuntu question would suggest that I am not
alone in this particular respect but I am currently not able to state
how to get there.  The system in question might have been changed from
an i386 system to an amd64 system without installing from scratch.  I'd
not rule out that the procedure changing the packages and architecture
to amd64 might have been involved.

At the point of time of reporting the problem, I thought I had a better
grasp of the situation.

Maybe a removed conffile should be treated differently from a changed
(like empty) conffile?

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

Title:
  apt-get install memtest86+ fails to create /etc/grub.d/20_memtest86+

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  Removing/purging the file and/or using --reinstall options do not
  help.  Removing the file and installing it with

  dpkg -i /var/cache/apt/archives/memtest86+_5.01-3ubuntu2_amd64.deb

  works.

  When calling dpkg --verify on the apt-installed package, the missing
  file is flagged.

  I have no idea what causes this.  The file name ending in + maybe?
  But wouldn't apt call dpkg for installation anyway?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6.1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
  Uname: Linux 4.15.0-15-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Mon Apr 23 19:15:11 2018
  InstallationDate: Installed on 2011-10-14 (2383 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2018-01-23 (90 days ago)

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

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

[Touch-packages] [Bug 1766332] [NEW] need help

[jawad ali]

Public bug reported:

my graphics not working

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg (not installed)
ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Apr 24 00:24:37 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.13.0-38-generic, x86_64: installed
 nvidia-384, 384.130, 4.13.0-38-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo Skylake Integrated Graphics [17aa:3808]
InstallationDate: Installed on 2018-04-17 (5 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
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 174f:14e9 Syntek 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80Q7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=UUID=ec0e44e0-f209-4a9f-908f-c907644c99a3 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/03/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: D5CN31WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Paris 5A8
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 300-15ISK
dmi.modalias: 
dmi:bvnLENOVO:bvrD5CN31WW:bd12/03/2015:svnLENOVO:pn80Q7:pvrLenovoideapad300-15ISK:rvnLENOVO:rnParis5A8:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad300-15ISK:
dmi.product.family: IDEAPAD
dmi.product.name: 80Q7
dmi.product.version: Lenovo ideapad 300-15ISK
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Mon Apr 23 23:56:44 2018
xserver.configfile: default
xserver.errors:
 /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
 /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: modeset

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


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

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

Title:
  need help

Status in xorg package in Ubuntu:
  New

Bug description:
  my graphics not working

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 24 00:24:37 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-38-generic, x86_64: installed
   nvidia-384, 384.130, 4.13.0-38-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:3808]
  InstallationDate: Installed on 2018-04-17 (5 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  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
 

[Touch-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

[Chris Darroch]

I think I've filled in all the necessary info -- and I have another
screenshot to upload too, once I get it off my phone, from another
kernel panic in the same context.

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

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

Title:
  kernel panic in Radeon driver while screen blank

Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I maintain a set of older kiosks running a mix of stock Ubuntu 14.04
  LTS and 16.04.  As we have gradually transitioned them to 16.04, we
  have noticed that the machines running 16.04.1 now regularly exhibit
  problems restoring from the blank screen which appears after a period
  of inactivity.

  This only occurs on the machines where we've installed 16.04.  All of
  the 16.04.1 installations are "fresh", that is, complete re-installs
  from scratch, and we install all security and other updates on a
  regular basis.  This problem has persisted right from the beginning
  when we started using 16.04.

  Following a period of user inactivity, the screen goes blank; this is,
  of course, expected.  When the user tries to restore the session by
  typing a key or moving the mouse, one of three outcomes occurs.

  Sometimes, the session restores normally.  Other times, the screen
  remains blank regardless of all normal keyboard input, until a magic
  SysRq  sequence is performed.  After Alt-SysRq-k, either the virtual
  console resets to a login screen (as expected after this SysRq
  sequence), or we get a kernel panic text screen (see attached screen
  photo) and can only restore via a hard power-cycle reboot.

  I will continue to try to capture a better trace output from one of
  these conditions, perhaps from /var/log/kern.log or by installing
  linux-crashdump (although these old machines may not have enough
  memory for the stock package).  But in the meantime, I'm attaching a
  photo of the kernel panic we see, which suggests a problem may reside
  in the Radeon driver ... which would seem possible, given the general
  blank-screen no-resume problem on these systems.

  Any advice on how to further capture any other needed details would be
  appreciated.  Thanks very much!

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

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

[Touch-packages] [Bug 1766325] [NEW] sudo: pam_unix(sudo:auth): conversation failed

[Jonas]

Public bug reported:

Hello.

I experience a bug after upgrading from Ubuntu 17.10 to 18.04.

The bug seems to be a regression because what I am trying to do was
working with Ubuntu 17.10 and stopped working after the upgrade.

Here is the problem:

I have 2 users on my system. One is the user that is created during
installation, named zzz. The other user I added later, named abc. Both
users have passwords set. According to passwd the password for user abc
is a locked password (L) (whatever that means).

Now I am logged into user zzz and want to execute a program as user abc
without entering the password of user abc.

Until Ubuntu 17.10 this was done like this: "sudo -i -u abc /usr/bin/java 
-version".
To get that working I had to add this via visudo: "zzz ALL=(abc) NOPASSWD: 
/usr/bin/java"

Now this seems to be ignored. Instead the terminal is asking for the
password of user abc. I see this in /var/log/auth.log: "sudo:
pam_unix(sudo:auth): conversation failed".

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


** Tags: pam sudo

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

Title:
  sudo: pam_unix(sudo:auth): conversation failed

Status in sudo package in Ubuntu:
  New

Bug description:
  Hello.

  I experience a bug after upgrading from Ubuntu 17.10 to 18.04.

  The bug seems to be a regression because what I am trying to do was
  working with Ubuntu 17.10 and stopped working after the upgrade.

  Here is the problem:

  I have 2 users on my system. One is the user that is created during
  installation, named zzz. The other user I added later, named abc. Both
  users have passwords set. According to passwd the password for user
  abc is a locked password (L) (whatever that means).

  Now I am logged into user zzz and want to execute a program as user
  abc without entering the password of user abc.

  Until Ubuntu 17.10 this was done like this: "sudo -i -u abc /usr/bin/java 
-version".
  To get that working I had to add this via visudo: "zzz ALL=(abc) NOPASSWD: 
/usr/bin/java"

  Now this seems to be ignored. Instead the terminal is asking for the
  password of user abc. I see this in /var/log/auth.log: "sudo:
  pam_unix(sudo:auth): conversation failed".

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

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

[Touch-packages] [Bug 1766310] Re: apt-get install memtest86+ fails to create /etc/grub.d/20_memtest86+

[Julian Andres Klode]

I'm not entirely sure what you're experiencing here. Note that this file
is a conffile, so removing it is a local configuration choice that will
be preserved during upgrades or reinstalls. The only way to restore a
removed conffile from my understanding is purging and reinstalling the
package.

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

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

Title:
  apt-get install memtest86+ fails to create /etc/grub.d/20_memtest86+

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  Removing/purging the file and/or using --reinstall options do not
  help.  Removing the file and installing it with

  dpkg -i /var/cache/apt/archives/memtest86+_5.01-3ubuntu2_amd64.deb

  works.

  When calling dpkg --verify on the apt-installed package, the missing
  file is flagged.

  I have no idea what causes this.  The file name ending in + maybe?
  But wouldn't apt call dpkg for installation anyway?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6.1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
  Uname: Linux 4.15.0-15-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Mon Apr 23 19:15:11 2018
  InstallationDate: Installed on 2011-10-14 (2383 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2018-01-23 (90 days ago)

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

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

[Touch-packages] [Bug 1766317] [NEW] package rsyslog 8.32.0-1ubuntu3 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 1

[Laurent Bonnaud]

Public bug reported:

Setting up rsyslog (8.32.0-1ubuntu3) ...
Installing new version of config file /etc/init.d/rsyslog ...
Installing new version of config file /etc/logrotate.d/rsyslog ...
Installing new version of config file /etc/rsyslog.conf ...
The user `syslog' is already a member of `adm'.
Job for rsyslog.service failed because the control process exited with error 
code.
See "systemctl status rsyslog.service" and "journalctl -xe" for details.
invoke-rc.d: initscript rsyslog, action "restart" failed.
● rsyslog.service - System Logging Service
   Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor preset: 
enabled)
   Active: activating (auto-restart) (Result: exit-code) since Mon 2018-04-23 
19:40:06 CEST; 8ms ago
 Docs: man:rsyslogd(8)
   http://www.rsyslog.com/doc/
  Process: 31888 ExecStart=/usr/sbin/rsyslogd -n (code=exited, status=1/FAILURE)
 Main PID: 31888 (code=exited, status=1/FAILURE)
dpkg: error processing package rsyslog (--configure):
 installed rsyslog package post-installation script subprocess returned error 
exit status 1

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: rsyslog 8.32.0-1ubuntu3
Uname: Linux 4.16.3-041603-generic x86_64
ApportVersion: 2.20.9-0ubuntu6
Architecture: amd64
Date: Mon Apr 23 19:40:06 2018
ErrorMessage: installed rsyslog package post-installation script subprocess 
returned error exit status 1
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: rsyslog
Title: package rsyslog 8.32.0-1ubuntu3 failed to install/upgrade: installed 
rsyslog package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package rsyslog 8.32.0-1ubuntu3 failed to install/upgrade: installed
  rsyslog package post-installation script subprocess returned error
  exit status 1

Status in rsyslog package in Ubuntu:
  New

Bug description:
  Setting up rsyslog (8.32.0-1ubuntu3) ...
  Installing new version of config file /etc/init.d/rsyslog ...
  Installing new version of config file /etc/logrotate.d/rsyslog ...
  Installing new version of config file /etc/rsyslog.conf ...
  The user `syslog' is already a member of `adm'.
  Job for rsyslog.service failed because the control process exited with error 
code.
  See "systemctl status rsyslog.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript rsyslog, action "restart" failed.
  ● rsyslog.service - System Logging Service
 Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor 
preset: enabled)
 Active: activating (auto-restart) (Result: exit-code) since Mon 2018-04-23 
19:40:06 CEST; 8ms ago
   Docs: man:rsyslogd(8)
 http://www.rsyslog.com/doc/
Process: 31888 ExecStart=/usr/sbin/rsyslogd -n (code=exited, 
status=1/FAILURE)
   Main PID: 31888 (code=exited, status=1/FAILURE)
  dpkg: error processing package rsyslog (--configure):
   installed rsyslog package post-installation script subprocess returned error 
exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: rsyslog 8.32.0-1ubuntu3
  Uname: Linux 4.16.3-041603-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Mon Apr 23 19:40:06 2018
  ErrorMessage: installed rsyslog package post-installation script subprocess 
returned error exit status 1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: rsyslog
  Title: package rsyslog 8.32.0-1ubuntu3 failed to install/upgrade: installed 
rsyslog package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1754686] Re: libcurl4 Conflicts: libcurl3 - prevents install of 3rd party apps like slack-desktop

[Nowell Morris]

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

I am also affected by this.  both Virtualbox and Slack need 3, and Cairo
and others need 4.

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

Title:
  libcurl4 Conflicts: libcurl3 - prevents install of 3rd party apps like
  slack-desktop

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Updating the curl package pulls in libcurl4, which for some reason
  forces libcurl3 to be removed. This prevents 3rd party apps that still
  build against libcurl3 from being installed. Isn't there a more
  graceful way to effect the transition from libcurl3 to libcurl4?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libcurl4 7.58.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar  9 10:10:10 2018
  EcryptfsInUse: Yes
  SourcePackage: curl
  UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago)

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

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

[Touch-packages] [Bug 1766310] Re: apt-get install memtest86+ fails to create /etc/grub.d/20_memtest86+

[David Kastrup]

Note that

https://askubuntu.com/questions/126160/how-can-i-add-the-memtest86
-options-back-to-the-grub-menu

would suggest that this strange situation has been subsisting for years
by now so it would not appear that many packages apart from memtest86+
are affected by this bug.

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

Title:
  apt-get install memtest86+ fails to create /etc/grub.d/20_memtest86+

Status in apt package in Ubuntu:
  New

Bug description:
  Removing/purging the file and/or using --reinstall options do not
  help.  Removing the file and installing it with

  dpkg -i /var/cache/apt/archives/memtest86+_5.01-3ubuntu2_amd64.deb

  works.

  When calling dpkg --verify on the apt-installed package, the missing
  file is flagged.

  I have no idea what causes this.  The file name ending in + maybe?
  But wouldn't apt call dpkg for installation anyway?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6.1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
  Uname: Linux 4.15.0-15-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Mon Apr 23 19:15:11 2018
  InstallationDate: Installed on 2011-10-14 (2383 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2018-01-23 (90 days ago)

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

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

[Touch-packages] [Bug 1766310] [NEW] apt-get install memtest86+ fails to create /etc/grub.d/20_memtest86+

[David Kastrup]

Public bug reported:

Removing/purging the file and/or using --reinstall options do not help.
Removing the file and installing it with

dpkg -i /var/cache/apt/archives/memtest86+_5.01-3ubuntu2_amd64.deb

works.

When calling dpkg --verify on the apt-installed package, the missing
file is flagged.

I have no idea what causes this.  The file name ending in + maybe?  But
wouldn't apt call dpkg for installation anyway?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apt 1.6.1
ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
Uname: Linux 4.15.0-15-lowlatency x86_64
ApportVersion: 2.20.9-0ubuntu6
Architecture: amd64
Date: Mon Apr 23 19:15:11 2018
InstallationDate: Installed on 2011-10-14 (2383 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
SourcePackage: apt
UpgradeStatus: Upgraded to bionic on 2018-01-23 (90 days ago)

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


** Tags: amd64 apport-bug bionic

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

Title:
  apt-get install memtest86+ fails to create /etc/grub.d/20_memtest86+

Status in apt package in Ubuntu:
  New

Bug description:
  Removing/purging the file and/or using --reinstall options do not
  help.  Removing the file and installing it with

  dpkg -i /var/cache/apt/archives/memtest86+_5.01-3ubuntu2_amd64.deb

  works.

  When calling dpkg --verify on the apt-installed package, the missing
  file is flagged.

  I have no idea what causes this.  The file name ending in + maybe?
  But wouldn't apt call dpkg for installation anyway?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6.1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
  Uname: Linux 4.15.0-15-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Mon Apr 23 19:15:11 2018
  InstallationDate: Installed on 2011-10-14 (2383 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2018-01-23 (90 days ago)

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

-- 
Mailing list: https://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 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

[Balint Reczey]

On Mon, Apr 23, 2018 at 5:48 PM, luca moscato  wrote:
> Sorry guys to bother you, I'm the reporter of
> https://bugs.launchpad.net/ubuntu/+bug/1744045

Thank you for reporting bugs!

>
> Having this bug fixed exactly what does it means on Ubuntu 16.04 and on the 
> upcoming 18.04?

Unattended-upgrades and update-manager will remove old unused kernels
with the default configuration.
This is already happening in 18.04 and will be back-ported to 16.04.

> With a clean installation (on an encrypted disk) the boot partition will be 
> removed automatically? Or do I have to upgrade manually 
> /etc/apt/apt.conf.d/50unattended-upgrades
> uncommenting this parameter?
> //Unattended-Upgrade::Remove-Unused-Dependencies "true";

No, the /boot partition will be kept, but unused old kernel files will
be cleaned up. Without changing the configuration files from the
shipped default values.

> I'm asking since some of my colleagues doesn't use command line (so they
> don't use autoremove) and they rely on Software update Application.

I hope they will be pleased to see that obsolete kernels are removed
without starting terminals. :-)

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

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+subscriptions

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

[Touch-packages] [Bug 1766307] [NEW] Crash low-graphics mode

[Rogério Nunes Wolff]

Public bug reported:

Since friday, 4/20/2018, when I did an upgrade in Ubuntu, I receive an
error message:

The system is running in low-graphics mode

Your screen, graphics cards, and input device settings could not be
detected correctly. You will need to configure these yourself.

Then, using tab key, I press OK, then I choose try the default, and
everything works fine after this. But this is very annoying.

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

ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Apr 23 13:54:49 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 nvidia-304, 304.135, 4.13.0-38-generic, x86_64: installed
 nvidia-304, 304.135, 4.13.0-39-generic, x86_64: installed
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] 2nd Generation Core 
Processor Family Integrated Graphics Controller [1462:7788]
InstallationDate: Installed on 2017-09-14 (221 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Lsusb:
 Bus 002 Device 003: ID 04b3:310c IBM Corp. Wheel Mouse
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: MSI MS-7788
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic 
root=UUID=2f8e3cb0-6af1-44b7-b3fa-ea29171c708d ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/18/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V2.3
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61M-P31 (G3) (MS-7788)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.3:bd01/18/2012:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31(G3)(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7788
dmi.product.version: 1.0
dmi.sys.vendor: MSI
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 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: Mon Apr 23 12:51:59 2018
xserver.configfile: default
xserver.devices:

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

xserver.version: 2:1.19.5-0ubuntu2~16.04.1

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


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

** Description changed:

- Since friday, 4/23/2018, when I did an upgrade in Ubuntu, I receive an
+ Since friday, 4/20/2018, when I did an upgrade in Ubuntu, I receive an
  error message:
  
- The system is running in low-graphics mode
+ The system is running in low-graphics mode
  
- Your screen, graphics cards, and input device settings could not be
+ Your screen, graphics cards, and input device settings could not be
  detected correctly. You will need to configure these yourself.
  
  Then, using tab key, I press OK, then I choose try the default, and
  everything works fine after this. But this is very annoying.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Apr 23 13:54:49 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
-  nvidia-304, 304.135, 

[Touch-packages] [Bug 1754092] Re: firefox esr loading bookmark limbo

[Galen Thurber]

** Package changed: apt (Ubuntu) => firefox (Ubuntu)

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

Title:
  firefox esr loading bookmark limbo

Status in firefox package in Ubuntu:
  New

Bug description:
  on three computers I use Firefox ESR
  which all have the odd behaviour of not loading a bookmark.
  I'll select a bookmark ex: youtube.com and the tab icon will rotate but the 
page never loads & never times out. The limbo will happen with various 
bookmarks, cache has been cleared.
  To fix the limbo problem I'll hit enter once in the address bar.
  The limbo happens on 
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04
  and
  Ubuntu 14.04.5LTS
  and MX Linux 17

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

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

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

[Jeffry Johnston]

Ran into this problem today on 16.04. Here's a brute-force hack that got
me past the problem. Attempt at your own risk:

# First, try to update:
sudo apt-get upgrade
# STOP if you don't see the following messages:
# Job for avahi-daemon.socket canceled.
# dpkg: warning: subprocess old pre-removal script returned error exit status 1

# Here's the hack:
sudo sed -i.backup 's:deb-systemd-invoke stop avahi-daemon.socket 
>/dev/null:echo:' /var/lib/dpkg/info/avahi-dnsconfd.prerm

# Try to update again
sudo apt-get upgrade
# avahi-daemon should now install without the pre-removal script error message. 
If it doesn't, you should restore the backup:
sudo mv /var/lib/dpkg/info/avahi-dnsconfd.prerm.backup 
/var/lib/dpkg/info/avahi-dnsconfd.prerm

HTH

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

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

Status in avahi package in Ubuntu:
  Fix Released

Bug description:
  interesting issues while updating packages this morning...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Wed Mar 30 09:33:28 2016
  DpkgTerminalLog:
   Removing avahi-discover (0.6.32~rc+dfsg-1ubuntu2) ...
   Removing avahi-dnsconfd (0.6.32~rc+dfsg-1ubuntu2) ...
   Job for avahi-daemon.socket canceled.
   dpkg: error processing package avahi-dnsconfd (--remove):
subprocess installed pre-removal script returned error exit status 1
  DuplicateSignature:
   Removing avahi-dnsconfd (0.6.32~rc+dfsg-1ubuntu2) ...
   Job for avahi-daemon.socket canceled.
   dpkg: error processing package avahi-dnsconfd (--remove):
subprocess installed pre-removal script returned error exit status 1
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2016-01-06 (83 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.9
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: subprocess installed pre-removal script returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1754075] Re: apt-setup uses apt-key but probably should not anymore

[Lars Kollstedt]

Of course only if they're inheriting special repositories this way. But
the bugs referenced here IMHO are showing lot's of examples representing
different reasons and ways to do this. ;-)

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

Title:
  apt-setup uses apt-key but probably should not anymore

Status in apt-setup package in Ubuntu:
  Confirmed
Status in gnupg package in Ubuntu:
  Confirmed
Status in gnupg2 package in Ubuntu:
  Confirmed

Bug description:
  In di if the kernel is in a private PPA we seed di using

  d-i apt-setup/local0/key string
  http://keyserver.ubuntu.com:11371/pks/lookup?op=get=

  this used to work in xenial, but in bionic this fails and therefore
  apt update fails in base-installer. May be because add-apt-key is not
  installed.

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

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

[Touch-packages] [Bug 1754075] Re: apt-setup uses apt-key but probably should not anymore

[Lars Kollstedt]

Hello again,

I don't really have an opinion if this should be solved by 
  - changing the priority of gnupg or gnupg2 (if that wasn't only another 
unrelated side effect of the change described in Comment #7)
  - adding a dependency to gnupg2 | gnupg to apt-setup-udeb if that would be 
possible.
  - using the patch from Comment #12

As far as I can see there was no progress in the upstream bug (
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851774 ), yet. But
they're not releasing on April 26th 2018. ;-)

This might be a bug affecting only advanced admins using depoyment via
preseed, but it will IMHO affect everyone of them. If they haven't
deactivated key verification at all. ;-)

Kind regards
   Lars

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

Title:
  apt-setup uses apt-key but probably should not anymore

Status in apt-setup package in Ubuntu:
  Confirmed
Status in gnupg package in Ubuntu:
  Confirmed
Status in gnupg2 package in Ubuntu:
  Confirmed

Bug description:
  In di if the kernel is in a private PPA we seed di using

  d-i apt-setup/local0/key string
  http://keyserver.ubuntu.com:11371/pks/lookup?op=get=

  this used to work in xenial, but in bionic this fails and therefore
  apt update fails in base-installer. May be because add-apt-key is not
  installed.

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

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

[Touch-packages] [Bug 1766286] Re: curtin.util.ProcessExecutionError: Unexpected error while running command. Command: ['sh', '-c', 'exec "$0" "$@" 2>&1', 'install-grub', '--uefi', '--update-nvram', '

[Ubuntu QA Website]

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

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

** Tags added: iso-testing

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

Title:
  curtin.util.ProcessExecutionError: Unexpected error while
  running command. Command: ['sh', '-c', 'exec "$0" "$@" 2>&1',
  'install-grub', '--uefi', '--update-nvram', '/target', '/dev/sda']

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  It works in the same computer running in BIOS mode, but failed in UEFI
  mode

 Running command ['umount', '/target/dev'] with allowed return codes 
[0] (capture=False)
  finish: cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: 
curtin command curthooks
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/curtin/commands/main.py", line 
201, in main
  ret = args.func(args)
File "/usr/lib/python3/dist-packages/curtin/commands/curthooks.py", 
line 1103, in curthooks
  setup_grub(cfg, target)
File "/usr/lib/python3/dist-packages/curtin/commands/curthooks.py", 
line 407, in setup_grub
  join_stdout_err + args + instdevs, env=env, capture=True)
File "/usr/lib/python3/dist-packages/curtin/util.py", line 263, in 
subp
  return _subp(*args, **kwargs)
File "/usr/lib/python3/dist-packages/curtin/util.py", line 131, in 
_subp
  cmd=args)
  curtin.util.ProcessExecutionError: Unexpected error while running 
command.
  Command: ['sh', '-c', 'exec "$0" "$@" 2>&1', 'install-grub', 
'--uefi', '--update-nvram', '/target', '/dev/sda']
  Exit code: 1
  Reason: -
  Stdout: carryover command line params: 
  curtin uefi: installing grub-efi-amd64 to: /boot/efi
  + echo before grub-install efiboot settings
  before grub-install efiboot settings
  + efibootmgr
  BootCurrent: 
  Timeout: 0 seconds
  BootOrder: 2001,2003,2002
  Boot* EFI USB Device (JetFlashTranscend 32GB)
  Boot0001* EFI Network 0 for IPv6 (70-54-D2-31-33-2D) 
  Boot0002* EFI Network 0 for IPv4 (70-54-D2-31-33-2D) 
  Boot2001* EFI USB Device
  Boot2002* EFI DVD/CDROM
  Boot2003* EFI Network
  + dpkg-reconfigure grub-efi-amd64
  Replacing config file /etc/default/grub with new version
  Processing triggers for shim-signed (1.34.4+13-0ubuntu2) ...
  No MOK found.
  dpkg: error processing package shim-signed (--configure):
   installed shim-signed package post-installation script 
subprocess returned error exit status 1
  Errors were encountered while processing:
   shim-signed
  failed to install grub!
  
  Stderr: ''
  Unexpected error while running command.
  Command: ['sh', '-c', 'exec "$0" "$@" 2>&1', 'install-grub', 
'--uefi', '--update-nvram', '/target', '/dev/sda']
  Exit code: 1
  Reason: -

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-server 1.417
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CasperVersion: 1.393
  Date: Mon Apr 23 15:31:41 2018
  LiveMediaBuild: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180421.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1766293] [NEW] package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

[A.K.Karthikeyan]

Public bug reported:

This happened while I tried to upgrade to 18.04 from 17.10 , on 23rd
April, 3 days prior to official launch.

Though this kind of bug had been reported here #366433 , i think this
might be a new one as its hppening in a recent version of OS.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: ca-certificates 20180409
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu6
Architecture: amd64
Date: Mon Apr 23 20:59:30 2018
ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2014-08-31 (1331 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: ca-certificates
Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
UpgradeStatus: Upgraded to bionic on 2018-04-23 (0 days ago)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic need-duplicate-check

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 1

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  This happened while I tried to upgrade to 18.04 from 17.10 , on 23rd
  April, 3 days prior to official launch.

  Though this kind of bug had been reported here #366433 , i think this
  might be a new one as its hppening in a recent version of OS.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Mon Apr 23 20:59:30 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2014-08-31 (1331 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to bionic on 2018-04-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1766293/+subscriptions

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

[Touch-packages] [Bug 1762465] Re: Nautilus sidebar theming is confusing

[Treviño]

Something like this, to be more clear: https://usercontent.irccloud-
cdn.com/file/DwPJt7na/image.png

(maybe with a darker bg in the icon area to keep some consistency)

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

Title:
  Nautilus sidebar theming is confusing

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

Bug description:
  The new theming of the Nautilus sidebar is confusing to users.  The icons and 
the icon labels have a different background colour, and when a specific 
location is selected the background colour of the selected icon changes to be 
the same as the background colour of the labels, while the other icons have a 
darker background colour.
  This is giving the impression that the text labels are a hierarchy of the 
icon, rather than simply being labels associated with each icon.

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

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

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

[luca moscato]

Sorry guys to bother you, I'm the reporter of
https://bugs.launchpad.net/ubuntu/+bug/1744045

Having this bug fixed exactly what does it means on Ubuntu 16.04 and on the 
upcoming 18.04?
With a clean installation (on an encrypted disk) the boot partition will be 
removed automatically? Or do I have to upgrade manually 
/etc/apt/apt.conf.d/50unattended-upgrades
uncommenting this parameter?
//Unattended-Upgrade::Remove-Unused-Dependencies "true"; 

I'm asking since some of my colleagues doesn't use command line (so they
don't use autoremove) and they rely on Software update Application.

Thanks for understanding

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

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+subscriptions

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

[Touch-packages] [Bug 1764087] Re: Wrongly boots into low graphics mode

[Dave Goldsbrough]

You could well be right Chris that
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764445 raise one
day later appears to be having the same effect, although the ubuntu
version, and the architecture is different.

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

Title:
  Wrongly boots into low graphics mode

Status in xorg package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  Lenovo T410 with VGA compatible controller [0300]: Intel Corporation
  Core Processor Integrated Graphics Controller [8086:0046] (rev 02)

  Booting from latest kernel ThinkPad-T410 4.13.0-38-generic
  #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 x86_64 x86_64
  x86_64 GNU/Linux goes into low graphics mode and also effects wi-fi
  connection insofar as it does not connect to my router.

  Whereas booting from 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar
  7 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux works most of the
  time but occasionally has the same effects.

  I have had to submit this report after booting from 4.13.0.37 in order
  to submit bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Apr 15 10:40:31 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
  InstallationDate: Installed on 2016-09-24 (567 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2519Y11
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=UUID=58d362c2-ed1e-479b-84f5-e5d8a782b08f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET85WW (1.45 )
  dmi.board.name: 2519Y11
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T410
  dmi.product.name: 2519Y11
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 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: Sun Apr 15 08:52:27 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1754075] Re: apt-setup uses apt-key but probably should not anymore

[Lars Kollstedt]

Hello,

Bug #1761030 indeed describes the same issues.

I've also a modified udeb in use, now. And it's working for me, but the
setup is almost the same.

d-i apt-setup/local0/source boolean false
d-i apt-setup/local0/key string 
http://software.ubuntu.man-da.de/software/key.gpg
d-i apt-setup/local0/repository string deb 
http://software.ubuntu.man-da.de/software bionic extras
d-i apt-setup/local0/comment string local server

After the installation completed the key was in
/etc/apt/trusted.gpg.d/local_server.asc since our internal repository
key was also ASCII-Armored.

But I used the overlay_host configuration to get the udeb in:
apt-mirror-setupapt-setup/overlay_host  string  
software.ubuntu.man-da.de
apt-mirror-setupapt-setup/overlay_directory string  /software/
apt-mirror-setupapt-setup/overlay   boolean true

The repository key was also integrated into our modified initrd to get
this working, but this alone didn't resolve the issues. With the patched
udeb in http://software.ubuntu.man-da.de/software/dists/bionic/main
/debian-installer/binary-amd64/Packages it works for me.

Kind regards
Lars

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

Title:
  apt-setup uses apt-key but probably should not anymore

Status in apt-setup package in Ubuntu:
  Confirmed
Status in gnupg package in Ubuntu:
  Confirmed
Status in gnupg2 package in Ubuntu:
  Confirmed

Bug description:
  In di if the kernel is in a private PPA we seed di using

  d-i apt-setup/local0/key string
  http://keyserver.ubuntu.com:11371/pks/lookup?op=get=

  this used to work in xenial, but in bionic this fails and therefore
  apt update fails in base-installer. May be because add-apt-key is not
  installed.

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

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

[Touch-packages] [Bug 1766286] [NEW] curtin.util.ProcessExecutionError: Unexpected error while running command. Command: ['sh', '-c', 'exec "$0" "$@" 2>&1', 'install-grub', '--uefi', '--update-nvram',

[sudodus]

Public bug reported:

It works in the same computer running in BIOS mode, but failed in UEFI
mode

   Running command ['umount', '/target/dev'] with allowed return codes [0] 
(capture=False)
finish: cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: curtin 
command curthooks
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/curtin/commands/main.py", line 
201, in main
ret = args.func(args)
  File "/usr/lib/python3/dist-packages/curtin/commands/curthooks.py", 
line 1103, in curthooks
setup_grub(cfg, target)
  File "/usr/lib/python3/dist-packages/curtin/commands/curthooks.py", 
line 407, in setup_grub
join_stdout_err + args + instdevs, env=env, capture=True)
  File "/usr/lib/python3/dist-packages/curtin/util.py", line 263, in 
subp
return _subp(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/curtin/util.py", line 131, in 
_subp
cmd=args)
curtin.util.ProcessExecutionError: Unexpected error while running 
command.
Command: ['sh', '-c', 'exec "$0" "$@" 2>&1', 'install-grub', '--uefi', 
'--update-nvram', '/target', '/dev/sda']
Exit code: 1
Reason: -
Stdout: carryover command line params: 
curtin uefi: installing grub-efi-amd64 to: /boot/efi
+ echo before grub-install efiboot settings
before grub-install efiboot settings
+ efibootmgr
BootCurrent: 
Timeout: 0 seconds
BootOrder: 2001,2003,2002
Boot* EFI USB Device (JetFlashTranscend 32GB)
Boot0001* EFI Network 0 for IPv6 (70-54-D2-31-33-2D) 
Boot0002* EFI Network 0 for IPv4 (70-54-D2-31-33-2D) 
Boot2001* EFI USB Device
Boot2002* EFI DVD/CDROM
Boot2003* EFI Network
+ dpkg-reconfigure grub-efi-amd64
Replacing config file /etc/default/grub with new version
Processing triggers for shim-signed (1.34.4+13-0ubuntu2) ...
No MOK found.
dpkg: error processing package shim-signed (--configure):
 installed shim-signed package post-installation script 
subprocess returned error exit status 1
Errors were encountered while processing:
 shim-signed
failed to install grub!

Stderr: ''
Unexpected error while running command.
Command: ['sh', '-c', 'exec "$0" "$@" 2>&1', 'install-grub', '--uefi', 
'--update-nvram', '/target', '/dev/sda']
Exit code: 1
Reason: -

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-server 1.417
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu6
Architecture: amd64
CasperVersion: 1.393
Date: Mon Apr 23 15:31:41 2018
LiveMediaBuild: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180421.1)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-meta
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic uec-images

** Attachment added: "curtin-error-logs.tar"
   
https://bugs.launchpad.net/bugs/1766286/+attachment/5125898/+files/curtin-error-logs.tar

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

Title:
  curtin.util.ProcessExecutionError: Unexpected error while
  running command. Command: ['sh', '-c', 'exec "$0" "$@" 2>&1',
  'install-grub', '--uefi', '--update-nvram', '/target', '/dev/sda']

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  It works in the same computer running in BIOS mode, but failed in UEFI
  mode

 Running command ['umount', '/target/dev'] with allowed return codes 
[0] (capture=False)
  finish: cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: 
curtin command curthooks
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/curtin/commands/main.py", line 
201, in main
  ret = args.func(args)
File "/usr/lib/python3/dist-packages/curtin/commands/curthooks.py", 
line 1103, in curthooks
  setup_grub(cfg, target)
File "/usr/lib/python3/dist-packages/curtin/commands/curthooks.py", 
line 407, in setup_grub
  join_stdout_err + args + instdevs, env=env, capture=True)
File "/usr/lib/python3/dist-packages/curtin/util.py", line 263, in 
subp
  return _subp(*args, **kwargs)
File 

[Touch-packages] [Bug 1762465] Re: Nautilus sidebar theming is confusing

[Treviño]

I think that's a too big change, and Ambiance-RW that was ack'ed by
design had this two color situation.

One thing we could do however, which won't involve much change nor break
visual, could be just leaving the item selected with orange background,
so although there are two colors, it should be pretty visible what they
refer to.

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

Title:
  Nautilus sidebar theming is confusing

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

Bug description:
  The new theming of the Nautilus sidebar is confusing to users.  The icons and 
the icon labels have a different background colour, and when a specific 
location is selected the background colour of the selected icon changes to be 
the same as the background colour of the labels, while the other icons have a 
darker background colour.
  This is giving the impression that the text labels are a hierarchy of the 
icon, rather than simply being labels associated with each icon.

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

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

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

[Jordan]

Same problem.

x1 carbon gen6 like Thorsten, Ubuntu 18.04. Kernel 4.15.

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

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

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

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

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

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

  Output and logs:
  -

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

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

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

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

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

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

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

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

  HuC status 0x6000:

  dmesg

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

[Touch-packages] [Bug 1754075] Re: apt-setup uses apt-key but probably should not anymore

[Launchpad Bug Tracker]

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

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

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

Title:
  apt-setup uses apt-key but probably should not anymore

Status in apt-setup package in Ubuntu:
  Confirmed
Status in gnupg package in Ubuntu:
  Confirmed
Status in gnupg2 package in Ubuntu:
  Confirmed

Bug description:
  In di if the kernel is in a private PPA we seed di using

  d-i apt-setup/local0/key string
  http://keyserver.ubuntu.com:11371/pks/lookup?op=get=

  this used to work in xenial, but in bionic this fails and therefore
  apt update fails in base-installer. May be because add-apt-key is not
  installed.

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

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

[Touch-packages] [Bug 1754075] Re: apt-setup uses apt-key but probably should not anymore

[Launchpad Bug Tracker]

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

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

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

Title:
  apt-setup uses apt-key but probably should not anymore

Status in apt-setup package in Ubuntu:
  Confirmed
Status in gnupg package in Ubuntu:
  Confirmed
Status in gnupg2 package in Ubuntu:
  Confirmed

Bug description:
  In di if the kernel is in a private PPA we seed di using

  d-i apt-setup/local0/key string
  http://keyserver.ubuntu.com:11371/pks/lookup?op=get=

  this used to work in xenial, but in bionic this fails and therefore
  apt update fails in base-installer. May be because add-apt-key is not
  installed.

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

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

[Touch-packages] [Bug 1751813] Re: Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array [S822L] [ipr]

[Manoj Iyer]

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

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

Title:
  Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array
  [S822L] [ipr]

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in debian-installer package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  ---Problem Description---
  Ubuntu 18.04 ppc64el installer does detect IPR (IBM Power RAID) based 
HDD/RAID arrays

  Tried with current bionic and current bionic-proposed installers
  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/vmlinux
  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/initrd.gz
  kexec -l vmlinux -i initrd.gz
  kexec -e

  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/bionic-proposed/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/vmlinux
  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/bionic-proposed/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/initrd.gz
   kexec -l vmlinux -i initrd.gz
  kexec -e

  ---uname output---
  uname -a
  Linux ltciofvtr-s822l2-lp1 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 
09:05:20 UTC 2018 ppc64le GNU/Linux

  Machine Type = 8247-22L (S822L)
   
  ---boot type---
  Network boot
   
  ---bootloader---
  petitboot shell
   
  ---Kernel cmdline used to launch install---
  #cat /proc/cmdline

  ---Bootloader protocol---
  http
   
  ---Install repository type---
  Internet repository
   
  ---Install repository Location---
  US
   
  ---Point of failure---
  Problem during post-install (stage 2) configuration or other problem seen 
after reboot

  ===console error log===


?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
? SCSI1 (0,0,0) (sda) - 2.0 GB SMART USB-IBM  ?
? SCSI2 (0,0,0) (sdb) - 1.0 TB IBM T RDX-USB3 ?
? ?
??
? ?
???



   moves;  selects;  activates buttons

  
  ~ # lsmod | grep -i ipr
  ipr   148677  0
  ~ # modinfo ipr
  filename:   /lib/modules/4.13.0-32-generic/kernel/drivers/scsi/ipr.ko
  version:2.6.4
  license:GPL
  description:IBM Power RAID SCSI Adapter Driver
  author: Brian King 
  srcversion: 05BB872A11F65B3A73AB352
  alias:  pci:v1014d04DAsv1014sd04FBbc*sc*i*
  alias:  pci:v1014d04DAsv1014sd04FCbc*sc*i*
  alias:  pci:v1014d034Asv1014sd04C9bc*sc*i*
  alias:  pci:v1014d034Asv1014sd04C8bc*sc*i*
  alias:  pci:v1014d034Asv1014sd04C7bc*sc*i*
  alias:  pci:v1014d034Asv1014sd049Cbc*sc*i*
  alias:  pci:v1014d034Asv1014sd049Bbc*sc*i*
  alias:  pci:v1014d034Asv1014sd049Abc*sc*i*
  alias:  pci:v1014d034Asv1014sd0499bc*sc*i*
  alias:  pci:v1014d034Asv1014sd0475bc*sc*i*
  alias:  pci:v1014d034Asv1014sd0474bc*sc*i*
  alias:  pci:v1014d034Asv1014sd04CAbc*sc*i*
  alias:  pci:v1014d034Asv1014sd046Dbc*sc*i*
  alias:  pci:v1014d034Asv1014sd03FEbc*sc*i*
  alias:  pci:v1014d034Asv1014sd03FFbc*sc*i*
  alias:  pci:v1014d034Asv1014sd03FCbc*sc*i*
  alias:  pci:v1014d034Asv1014sd03FBbc*sc*i*
  alias:  pci:v1014d034Asv1014sd035Ebc*sc*i*
  alias:  pci:v1014d034Asv1014sd035Dbc*sc*i*
  alias:  pci:v1014d034Asv1014sd0357bc*sc*i*
  alias:  pci:v1014d034Asv1014sd0355bc*sc*i*
  alias:  pci:v1014d034Asv1014sd033Bbc*sc*i*
  

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

[Frank Heimes]

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

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

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

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

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in apparmor package in Ubuntu:
  Fix Committed

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

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

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

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

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

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

[Touch-packages] [Bug 1748659] Re: Windows 10 Ubuntu 16.04 upgrade to 18.04: package systemd 235-3ubuntu3 failed to install/upgrade: installed systemd package post-installation script subprocess retur

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 237-3ubuntu10

---
systemd (237-3ubuntu10) bionic; urgency=medium

  * Create tmpfiles for persistent journal in postinst only when running
systemd (LP: #1748659)

 -- Balint Reczey   Fri, 20 Apr 2018 18:55:56 +0200

** Changed in: systemd (Ubuntu)
   Status: Triaged => 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/1748659

Title:
  Windows 10 Ubuntu 16.04 upgrade to 18.04: package systemd 235-3ubuntu3
  failed to install/upgrade: installed systemd package post-installation
  script subprocess returned error exit status 1

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  This was fresh Ubuntu 16.04 instance on Windows 10, running inside a
  Virtual Box on an iMac. I did an apt-get dist-upgrade before
  attempting to upgrade to 18.04.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 235-3ubuntu3
  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: Sat Feb 10 18:59:28 2018
  Dmesg:
   
  ErrorMessage: installed systemd package post-installation script subprocess 
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.19.0.5ubuntu1
   apt  1.2.24
  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 235-3ubuntu3 failed to install/upgrade: installed 
systemd package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2018-02-10 (0 days ago)

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

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

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

[Norbert]

This problem prevented `sudo apt-get dist-upgrade` on clean installation
of Ubuntu 16.04.4 LTS MATE.

Enabling xenial-proposed and installing single package fixed issue.

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

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

Status in avahi package in Ubuntu:
  Fix Released
Status in avahi source package in Xenial:
  Fix Committed

Bug description:
  Ubuntu Update 30.03.18

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

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

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

[Touch-packages] [Bug 1751813] Re: Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array [S822L] [ipr]

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 237-3ubuntu10

---
systemd (237-3ubuntu10) bionic; urgency=medium

  * Create tmpfiles for persistent journal in postinst only when running
systemd (LP: #1748659)

 -- Balint Reczey   Fri, 20 Apr 2018 18:55:56 +0200

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

Title:
  Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array
  [S822L] [ipr]

Status in The Ubuntu-power-systems project:
  In Progress
Status in debian-installer package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  ---Problem Description---
  Ubuntu 18.04 ppc64el installer does detect IPR (IBM Power RAID) based 
HDD/RAID arrays

  Tried with current bionic and current bionic-proposed installers
  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/vmlinux
  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/initrd.gz
  kexec -l vmlinux -i initrd.gz
  kexec -e

  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/bionic-proposed/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/vmlinux
  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/bionic-proposed/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/initrd.gz
   kexec -l vmlinux -i initrd.gz
  kexec -e

  ---uname output---
  uname -a
  Linux ltciofvtr-s822l2-lp1 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 
09:05:20 UTC 2018 ppc64le GNU/Linux

  Machine Type = 8247-22L (S822L)
   
  ---boot type---
  Network boot
   
  ---bootloader---
  petitboot shell
   
  ---Kernel cmdline used to launch install---
  #cat /proc/cmdline

  ---Bootloader protocol---
  http
   
  ---Install repository type---
  Internet repository
   
  ---Install repository Location---
  US
   
  ---Point of failure---
  Problem during post-install (stage 2) configuration or other problem seen 
after reboot

  ===console error log===


?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
? SCSI1 (0,0,0) (sda) - 2.0 GB SMART USB-IBM  ?
? SCSI2 (0,0,0) (sdb) - 1.0 TB IBM T RDX-USB3 ?
? ?
??
? ?
???



   moves;  selects;  activates buttons

  
  ~ # lsmod | grep -i ipr
  ipr   148677  0
  ~ # modinfo ipr
  filename:   /lib/modules/4.13.0-32-generic/kernel/drivers/scsi/ipr.ko
  version:2.6.4
  license:GPL
  description:IBM Power RAID SCSI Adapter Driver
  author: Brian King 
  srcversion: 05BB872A11F65B3A73AB352
  alias:  pci:v1014d04DAsv1014sd04FBbc*sc*i*
  alias:  pci:v1014d04DAsv1014sd04FCbc*sc*i*
  alias:  pci:v1014d034Asv1014sd04C9bc*sc*i*
  alias:  pci:v1014d034Asv1014sd04C8bc*sc*i*
  alias:  pci:v1014d034Asv1014sd04C7bc*sc*i*
  alias:  pci:v1014d034Asv1014sd049Cbc*sc*i*
  alias:  pci:v1014d034Asv1014sd049Bbc*sc*i*
  alias:  pci:v1014d034Asv1014sd049Abc*sc*i*
  alias:  pci:v1014d034Asv1014sd0499bc*sc*i*
  alias:  pci:v1014d034Asv1014sd0475bc*sc*i*
  alias:  pci:v1014d034Asv1014sd0474bc*sc*i*
  alias:  pci:v1014d034Asv1014sd04CAbc*sc*i*
  alias:  pci:v1014d034Asv1014sd046Dbc*sc*i*
  alias:  pci:v1014d034Asv1014sd03FEbc*sc*i*
  alias:  pci:v1014d034Asv1014sd03FFbc*sc*i*
  alias:  pci:v1014d034Asv1014sd03FCbc*sc*i*
  alias:  pci:v1014d034Asv1014sd03FBbc*sc*i*
  alias:  

[Touch-packages] [Bug 1765173] Re: networkd waits 10 seconds for ipv6 network discovery by default

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 237-3ubuntu10

---
systemd (237-3ubuntu10) bionic; urgency=medium

  * Create tmpfiles for persistent journal in postinst only when running
systemd (LP: #1748659)

 -- Balint Reczey   Fri, 20 Apr 2018 18:55:56 +0200

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

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

Title:
  networkd waits 10 seconds for ipv6 network discovery by default

Status in cloud-init package in Ubuntu:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

   * On ipv6 less hosts, boot stalls for 10s
   * This is due to implicit RA being on, and wait-online awaiting for RA to 
timeout
   * Expectation is, that since explicit request for RA was not done, it should 
not block network-online.target, whilst all other aspects of 
network-online.target should be honored.

  [Test Case]

   * lxc network set lxdbr0 ipv6.address none
   * lxc launch ubuntu-daily:bionic lp1765173
   * sleep 20 && lxc exec lp1765173 systemd-analyze blame | head

  Bad result is:
   12.157s systemd-networkd-wait-online.service
  Good result is:
 739ms systemd-networkd-wait-online.service

  [Regression Potential]

   * If explicit IPv6 dhcp/ra was enabled in .network file, the boot
  will be blocked awaiting RA response

   * Only kernel implicit RA configuration will now become "async"

   * This is inline with behaviour of xenial systems

  [Other Info]

   * Original bug report

  1.
  $ lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2.
  $ apt-cache policy systemd
  systemd:
    Installed: 237-3ubuntu8
    Candidate: 237-3ubuntu8
    Version table:
   *** 237-3ubuntu8 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3. systemd-networkd-wait-online doesn't block for 10 seconds waiting
  on an IPV6 Router Advertisement

  4. systemd-networkd sends at least two RA solicitation packets waiting
  for a response before setting the link to configured.  This blocks the
  boot for every Ubuntu system where it does not have a IPV6 router
  responding to solicitations.  THis includes bionic containers, cloud
  instances, vms and physical machines.

  --

  We can see that we're spending 13 seconds waiting  for networkd to say
  the network is up.

  % systemd-analyze blame
   13.326s systemd-networkd-wait-online.service
     999ms cloud-init-local.service
     954ms cloud-init.service
     887ms cloud-config.service
     749ms dev-vda1.device
     666ms cloud-final.service
     248ms keyboard-setup.service
     175ms systemd-udev-trigger.service
     171ms lxd-containers.service
     165ms snapd.service
     154ms apparmor.service
     147ms ssh.service
     144ms systemd-timesyncd.service
     133ms grub-common.service
     130ms systemd-journald.service
     130ms accounts-daemon.service
  99ms systemd-modules-load.service
  98ms systemd-resolved.service
  94ms apport.service
  92ms rsyslog.service
  88ms systemd-logind.service
  80ms lvm2-monitor.service
  75ms iscsid.service
  64ms ebtables.service
  62ms user@1000.service
  54ms dev-mqueue.mount
  53ms ufw.service
  52ms systemd-remount-fs.service
  52ms kmod-static-nodes.service
  34ms systemd-journal-flush.service
  34ms polkit.service
  32ms systemd-tmpfiles-setup-dev.service
  27ms systemd-udevd.service
  26ms systemd-networkd.service
  26ms systemd-sysctl.service
  25ms systemd-tmpfiles-setup.service
  21ms dev-hugepages.mount
  17ms sys-kernel-debug.mount
  16ms console-setup.service
  15ms plymouth-read-write.service
  15ms snapd.socket
  15ms plymouth-quit.service
  14ms systemd-update-utmp.service
  10ms systemd-user-sessions.service
   9ms boot-efi.mount
   8ms sys-fs-fuse-connections.mount
   8ms systemd-update-utmp-runlevel.service
   8ms lxd.socket
   7ms blk-availability.service
   5ms systemd-random-seed.service
   3ms setvtrgb.service
   3ms plymouth-quit-wait.service
   3ms sys-kernel-config.mount

  Here we can see that we start networking at 18:30:51.69, and then IPv6 NDISC 
runs for 10 seconds
  and then the link 

[Touch-packages] [Bug 1765724] Re: Xenial -> Bionic - System fails to boot after upgrade - systemd-cryptsetup@cryptswap1.service fails to start

[Jean-Baptiste Lallement]

and /etc

** Attachment added: "etc.tgz"
   
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1765724/+attachment/5125865/+files/etc.tgz

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

Title:
  Xenial -> Bionic - System fails to boot after upgrade - systemd-
  cryptsetup@cryptswap1.service fails to start

Status in cryptsetup package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Test Case:
  1. Install Xenial Desktop with encrypted home
  2. Upgrade to bionic
  3. Reboot

  Actual Result
  The system hangs on boot when it activates the encrypted swap. There are the 
following entries in the journal:
  $ journalctl -b-1 -o short-monotonic |grep crypt
  [1.535326] ubuntu kernel: Key type encrypted registered
  [  125.637205] ubuntu systemd[1]: Dependency failed for Cryptography Setup 
for cryptswap1.
  [  125.637789] ubuntu systemd[1]: Dependency failed for 
dev-mapper-cryptswap1.device.
  [  125.638311] ubuntu systemd[1]: Dependency failed for 
/dev/mapper/cryptswap1.
  [  125.639351] ubuntu systemd[1]: dev-mapper-cryptswap1.swap: Job 
dev-mapper-cryptswap1.swap/start failed with result 'dependency'.
  [  125.639478] ubuntu systemd[1]: dev-mapper-cryptswap1.device: Job 
dev-mapper-cryptswap1.device/start failed with result 'dependency'.
  [  125.639594] ubuntu systemd[1]: Dependency failed for Local Encrypted 
Volumes.
  [  125.640128] ubuntu systemd[1]: cryptsetup.target: Job 
cryptsetup.target/start failed with result 'dependency'.
  [  125.640266] ubuntu systemd[1]: systemd-cryptsetup@cryptswap1.service: Job 
systemd-cryptsetup@cryptswap1.service/start failed with result 'dependency'.
  [  383.902153] ubuntu systemd[1]: Starting Cryptography Setup for 
cryptswap1...
  [  383.913899] ubuntu systemd-cryptsetup[672]: Set cipher aes, mode 
xts-plain64, key size 256 bits for device 
/dev/disk/by-uuid/34ea85fd-854b-4892-95b9-7073dd2dbf7b.
  [  384.138596] ubuntu systemd[1]: Started Cryptography Setup for cryptswap1.
  [  384.143845] ubuntu systemd[1]: Reached target Local Encrypted Volumes.
  [  384.167475] ubuntu systemd[1]: Found device /dev/mapper/cryptswap1.
  [  384.171327] ubuntu systemd[1]: Activating swap /dev/mapper/cryptswap1...
  [  384.184639] ubuntu kernel: Adding 2093564k swap on /dev/mapper/cryptswap1. 
 Priority:-2 extents:1 across:2093564k FS
  [  384.191435] ubuntu systemd[1]: Activated swap /dev/mapper/cryptswap1.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cryptsetup 2:2.0.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 20 15:56:52 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-04-18 (2 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: cryptsetup
  UpgradeStatus: Upgraded to bionic on 2018-04-20 (0 days ago)
  cmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=ba774fed-a987-4070-9571-0e4790b08680 ro recovery nomodeset
  crypttab: cryptswap1 UUID=34ea85fd-854b-4892-95b9-7073dd2dbf7b /dev/urandom 
swap,offset=1024,cipher=aes-xts-plain64

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

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

[Touch-packages] [Bug 1765724] Re: Xenial -> Bionic - System fails to boot after upgrade - systemd-cryptsetup@cryptswap1.service fails to start

[Jean-Baptiste Lallement]

tarball of /run after enabling swap and running systemctl daemon-reload

** Attachment added: "run.tgz"
   
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1765724/+attachment/5125864/+files/run.tgz

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

Title:
  Xenial -> Bionic - System fails to boot after upgrade - systemd-
  cryptsetup@cryptswap1.service fails to start

Status in cryptsetup package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Test Case:
  1. Install Xenial Desktop with encrypted home
  2. Upgrade to bionic
  3. Reboot

  Actual Result
  The system hangs on boot when it activates the encrypted swap. There are the 
following entries in the journal:
  $ journalctl -b-1 -o short-monotonic |grep crypt
  [1.535326] ubuntu kernel: Key type encrypted registered
  [  125.637205] ubuntu systemd[1]: Dependency failed for Cryptography Setup 
for cryptswap1.
  [  125.637789] ubuntu systemd[1]: Dependency failed for 
dev-mapper-cryptswap1.device.
  [  125.638311] ubuntu systemd[1]: Dependency failed for 
/dev/mapper/cryptswap1.
  [  125.639351] ubuntu systemd[1]: dev-mapper-cryptswap1.swap: Job 
dev-mapper-cryptswap1.swap/start failed with result 'dependency'.
  [  125.639478] ubuntu systemd[1]: dev-mapper-cryptswap1.device: Job 
dev-mapper-cryptswap1.device/start failed with result 'dependency'.
  [  125.639594] ubuntu systemd[1]: Dependency failed for Local Encrypted 
Volumes.
  [  125.640128] ubuntu systemd[1]: cryptsetup.target: Job 
cryptsetup.target/start failed with result 'dependency'.
  [  125.640266] ubuntu systemd[1]: systemd-cryptsetup@cryptswap1.service: Job 
systemd-cryptsetup@cryptswap1.service/start failed with result 'dependency'.
  [  383.902153] ubuntu systemd[1]: Starting Cryptography Setup for 
cryptswap1...
  [  383.913899] ubuntu systemd-cryptsetup[672]: Set cipher aes, mode 
xts-plain64, key size 256 bits for device 
/dev/disk/by-uuid/34ea85fd-854b-4892-95b9-7073dd2dbf7b.
  [  384.138596] ubuntu systemd[1]: Started Cryptography Setup for cryptswap1.
  [  384.143845] ubuntu systemd[1]: Reached target Local Encrypted Volumes.
  [  384.167475] ubuntu systemd[1]: Found device /dev/mapper/cryptswap1.
  [  384.171327] ubuntu systemd[1]: Activating swap /dev/mapper/cryptswap1...
  [  384.184639] ubuntu kernel: Adding 2093564k swap on /dev/mapper/cryptswap1. 
 Priority:-2 extents:1 across:2093564k FS
  [  384.191435] ubuntu systemd[1]: Activated swap /dev/mapper/cryptswap1.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cryptsetup 2:2.0.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 20 15:56:52 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-04-18 (2 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: cryptsetup
  UpgradeStatus: Upgraded to bionic on 2018-04-20 (0 days ago)
  cmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=ba774fed-a987-4070-9571-0e4790b08680 ro recovery nomodeset
  crypttab: cryptswap1 UUID=34ea85fd-854b-4892-95b9-7073dd2dbf7b /dev/urandom 
swap,offset=1024,cipher=aes-xts-plain64

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

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

[Touch-packages] [Bug 1765724] Re: Xenial -> Bionic - System fails to boot after upgrade - systemd-cryptsetup@cryptswap1.service fails to start

[Jean-Baptiste Lallement]

$ sudo blkid 
[sudo] password for ubuntu: 
/dev/vda1: UUID="b3ffe16f-0cd1-4cf1-b886-528cc4fd6f3e" TYPE="ext4" 
PARTUUID="47db2999-01"
/dev/vda5: UUID="387abb3c-c278-4c33-9573-39481a177c8b" TYPE="swap" 
PARTUUID="47db2999-05"
/dev/mapper/cryptswap1: UUID="1d5f641c-047c-497e-bd9b-163c9d10a3e4" TYPE="swap"

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

Title:
  Xenial -> Bionic - System fails to boot after upgrade - systemd-
  cryptsetup@cryptswap1.service fails to start

Status in cryptsetup package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Test Case:
  1. Install Xenial Desktop with encrypted home
  2. Upgrade to bionic
  3. Reboot

  Actual Result
  The system hangs on boot when it activates the encrypted swap. There are the 
following entries in the journal:
  $ journalctl -b-1 -o short-monotonic |grep crypt
  [1.535326] ubuntu kernel: Key type encrypted registered
  [  125.637205] ubuntu systemd[1]: Dependency failed for Cryptography Setup 
for cryptswap1.
  [  125.637789] ubuntu systemd[1]: Dependency failed for 
dev-mapper-cryptswap1.device.
  [  125.638311] ubuntu systemd[1]: Dependency failed for 
/dev/mapper/cryptswap1.
  [  125.639351] ubuntu systemd[1]: dev-mapper-cryptswap1.swap: Job 
dev-mapper-cryptswap1.swap/start failed with result 'dependency'.
  [  125.639478] ubuntu systemd[1]: dev-mapper-cryptswap1.device: Job 
dev-mapper-cryptswap1.device/start failed with result 'dependency'.
  [  125.639594] ubuntu systemd[1]: Dependency failed for Local Encrypted 
Volumes.
  [  125.640128] ubuntu systemd[1]: cryptsetup.target: Job 
cryptsetup.target/start failed with result 'dependency'.
  [  125.640266] ubuntu systemd[1]: systemd-cryptsetup@cryptswap1.service: Job 
systemd-cryptsetup@cryptswap1.service/start failed with result 'dependency'.
  [  383.902153] ubuntu systemd[1]: Starting Cryptography Setup for 
cryptswap1...
  [  383.913899] ubuntu systemd-cryptsetup[672]: Set cipher aes, mode 
xts-plain64, key size 256 bits for device 
/dev/disk/by-uuid/34ea85fd-854b-4892-95b9-7073dd2dbf7b.
  [  384.138596] ubuntu systemd[1]: Started Cryptography Setup for cryptswap1.
  [  384.143845] ubuntu systemd[1]: Reached target Local Encrypted Volumes.
  [  384.167475] ubuntu systemd[1]: Found device /dev/mapper/cryptswap1.
  [  384.171327] ubuntu systemd[1]: Activating swap /dev/mapper/cryptswap1...
  [  384.184639] ubuntu kernel: Adding 2093564k swap on /dev/mapper/cryptswap1. 
 Priority:-2 extents:1 across:2093564k FS
  [  384.191435] ubuntu systemd[1]: Activated swap /dev/mapper/cryptswap1.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cryptsetup 2:2.0.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 20 15:56:52 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-04-18 (2 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: cryptsetup
  UpgradeStatus: Upgraded to bionic on 2018-04-20 (0 days ago)
  cmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=ba774fed-a987-4070-9571-0e4790b08680 ro recovery nomodeset
  crypttab: cryptswap1 UUID=34ea85fd-854b-4892-95b9-7073dd2dbf7b /dev/urandom 
swap,offset=1024,cipher=aes-xts-plain64

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

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

[Touch-packages] [Bug 1766129] Re: Clicking any checkbox freezes the program

[Ads20000]

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

OK so this only happens when clicking Cancel on the authentication,
marking this as a duplicate of bug 1765353 cheers Sebastien! :)

** This bug has been marked a duplicate of bug 1765353
   gnome-control-center crashed with SIGSEGV in acquire_cb() from 
g_simple_async_result_complete()

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

Title:
  Clicking any checkbox freezes the program

Status in software-properties package in Ubuntu:
  New

Bug description:
  Upgraded to 18.04 today and clicking any checkbox in Software &
  Updates freezes the program (at least, in the Communitheme Wayland
  session (`snap install communitheme --edge` 0.1 (73))).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sun Apr 22 23:52:47 2018
  InstallationDate: Installed on 2017-08-03 (262 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to bionic on 2018-04-22 (0 days ago)

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

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

[Touch-packages] [Bug 1766256] [NEW] package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

[Serenak]

Public bug reported:

update failed

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: ca-certificates 20180409
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu6
Architecture: amd64
Date: Mon Apr 23 14:20:06 2018
ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2015-12-02 (872 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: ca-certificates
Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
UpgradeStatus: Upgraded to bionic on 2018-03-22 (32 days ago)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic need-duplicate-check

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 1

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  update failed

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Mon Apr 23 14:20:06 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2015-12-02 (872 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to bionic on 2018-03-22 (32 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1766256/+subscriptions

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

[Touch-packages] [Bug 1765724] Re: Xenial -> Bionic - System fails to boot after upgrade - systemd-cryptsetup@cryptswap1.service fails to start

[Jean-Baptiste Lallement]

/var/log with a failed boot.

** Attachment added: "var_log.tgz"
   
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1765724/+attachment/5125848/+files/var_log.tgz

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

Title:
  Xenial -> Bionic - System fails to boot after upgrade - systemd-
  cryptsetup@cryptswap1.service fails to start

Status in cryptsetup package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Test Case:
  1. Install Xenial Desktop with encrypted home
  2. Upgrade to bionic
  3. Reboot

  Actual Result
  The system hangs on boot when it activates the encrypted swap. There are the 
following entries in the journal:
  $ journalctl -b-1 -o short-monotonic |grep crypt
  [1.535326] ubuntu kernel: Key type encrypted registered
  [  125.637205] ubuntu systemd[1]: Dependency failed for Cryptography Setup 
for cryptswap1.
  [  125.637789] ubuntu systemd[1]: Dependency failed for 
dev-mapper-cryptswap1.device.
  [  125.638311] ubuntu systemd[1]: Dependency failed for 
/dev/mapper/cryptswap1.
  [  125.639351] ubuntu systemd[1]: dev-mapper-cryptswap1.swap: Job 
dev-mapper-cryptswap1.swap/start failed with result 'dependency'.
  [  125.639478] ubuntu systemd[1]: dev-mapper-cryptswap1.device: Job 
dev-mapper-cryptswap1.device/start failed with result 'dependency'.
  [  125.639594] ubuntu systemd[1]: Dependency failed for Local Encrypted 
Volumes.
  [  125.640128] ubuntu systemd[1]: cryptsetup.target: Job 
cryptsetup.target/start failed with result 'dependency'.
  [  125.640266] ubuntu systemd[1]: systemd-cryptsetup@cryptswap1.service: Job 
systemd-cryptsetup@cryptswap1.service/start failed with result 'dependency'.
  [  383.902153] ubuntu systemd[1]: Starting Cryptography Setup for 
cryptswap1...
  [  383.913899] ubuntu systemd-cryptsetup[672]: Set cipher aes, mode 
xts-plain64, key size 256 bits for device 
/dev/disk/by-uuid/34ea85fd-854b-4892-95b9-7073dd2dbf7b.
  [  384.138596] ubuntu systemd[1]: Started Cryptography Setup for cryptswap1.
  [  384.143845] ubuntu systemd[1]: Reached target Local Encrypted Volumes.
  [  384.167475] ubuntu systemd[1]: Found device /dev/mapper/cryptswap1.
  [  384.171327] ubuntu systemd[1]: Activating swap /dev/mapper/cryptswap1...
  [  384.184639] ubuntu kernel: Adding 2093564k swap on /dev/mapper/cryptswap1. 
 Priority:-2 extents:1 across:2093564k FS
  [  384.191435] ubuntu systemd[1]: Activated swap /dev/mapper/cryptswap1.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cryptsetup 2:2.0.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 20 15:56:52 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-04-18 (2 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: cryptsetup
  UpgradeStatus: Upgraded to bionic on 2018-04-20 (0 days ago)
  cmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=ba774fed-a987-4070-9571-0e4790b08680 ro recovery nomodeset
  crypttab: cryptswap1 UUID=34ea85fd-854b-4892-95b9-7073dd2dbf7b /dev/urandom 
swap,offset=1024,cipher=aes-xts-plain64

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

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

[Touch-packages] [Bug 1732030] Re: 'apt update' dies with seccomp error

[Roger Light]

I've been hit by this problem as well, but for the pread64 syscall. It's
working for me now after playing with my apt conf, getting the bug fix
and then reverting my apt conf, but thought it was worth mentioning
anyway.

I'm on a system with nfs/autofs home directories and nis for logins,
which I bet is the contributing factor.

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

Title:
  'apt update' dies with seccomp error

Status in apt package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Released

Bug description:
  $ apt-get update
  0% [Working]
    Seccomp prevented execution of syscall 78 on architecture amd64 

  Reading package lists... Done
  E: Method mirror has died unexpectedly!
  E: Sub-process mirror returned an error code (31)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6~alpha5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Mon Nov 13 23:10:57 2017
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2017-05-20 (177 days ago)

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

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

Re: [Touch-packages] [Bug 1764060] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

[derisolde]

i have tested your answer, but:

isolde@isolde-MS-7817:~$ sudo apt-get remove python-ubuntu-sso-client
[sudo] Passwort für isolde:
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen Fertig
Paket »python-ubuntu-sso-client« ist nicht installiert, wird also auch 
nicht entfernt.
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
54 nicht vollständig installiert oder entfernt.
Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt.
python3 (3.6.5-3) wird eingerichtet ...
running python rtupdate hooks for python3.6...
E: py3compile:183: cannot create directory 
/usr/share/hplip/ui5/__pycache__: FileNotFoundError(2, 'No such file or 
directory')
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/aboutdialog.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/aboutdialog_base.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/aligndialog.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/aligndialog_base.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/cleandialog.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/cleandialog_base.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/colorcaldialog.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/colorcaldialog_base.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/devicesetupdialog.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/devicesetupdialog_base.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/deviceuricombobox.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/devmgr5.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/devmgr5_base.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/devmgr_ext.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/fabgrouptable.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/fabnametable.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/fabwindow.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/fabwindow_base.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/faxsetupdialog.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/faxsetupdialog_base.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/filetable.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/firmwaredialog.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/firmwaredialog_base.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/infodialog.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/infodialog_base.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/linefeedcaldialog.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/linefeedcaldialog_base.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/loadpapergroupbox.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/makecopiesdialog.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/makecopiesdialog_base.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/mimetypesdialog.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/mimetypesdialog_base.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/nodevicesdialog.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/nodevicesdialog_base.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/plugindiagnose.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/plugindiagnose_base.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/plugindialog.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/plugindialog_base.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/pluginlicensedialog.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/pluginlicensedialog_base.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/pqdiagdialog.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/pqdiagdialog_base.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/printdialog.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/printdialog_base.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/printernamecombobox.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/printsettings_base.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/printsettingsdialog.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/printsettingsdialog_base.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/printsettingstoolbox.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/printtestpagedialog.py'
[Errno 2] No such file or directory: 
'/usr/share/hplip/ui5/printtestpagedialog_base.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/queuesconf.py'
[Errno 2] No such file or directory: 

[Touch-packages] [Bug 1766129] Re: Clicking any checkbox freezes the program

[Ads20000]

OK, actually interactions with the app do seem to have an effect (e.g.
clicking an item in Other Software or clicking a checkbox) but only
after 25 seconds or so! So I think I can still count this as a freeze of
sorts?

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

Title:
  Clicking any checkbox freezes the program

Status in software-properties package in Ubuntu:
  New

Bug description:
  Upgraded to 18.04 today and clicking any checkbox in Software &
  Updates freezes the program (at least, in the Communitheme Wayland
  session (`snap install communitheme --edge` 0.1 (73))).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sun Apr 22 23:52:47 2018
  InstallationDate: Installed on 2017-08-03 (262 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to bionic on 2018-04-22 (0 days ago)

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

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

[Touch-packages] [Bug 1766129] Re: Clicking any checkbox freezes the program

[Ads20000]

Alright, `journalctl -f` gets me the info you want! There's no output to
that when the freeze happen.

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

Title:
  Clicking any checkbox freezes the program

Status in software-properties package in Ubuntu:
  New

Bug description:
  Upgraded to 18.04 today and clicking any checkbox in Software &
  Updates freezes the program (at least, in the Communitheme Wayland
  session (`snap install communitheme --edge` 0.1 (73))).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sun Apr 22 23:52:47 2018
  InstallationDate: Installed on 2017-08-03 (262 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to bionic on 2018-04-22 (0 days ago)

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

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

[Touch-packages] [Bug 1766229] [NEW] package python-gi 3.24.1-2build1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 139

[Cyprien Aubry]

Public bug reported:

Tried to install pulseaudio-equalizer

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: python-gi 3.24.1-2build1
ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
Date: Mon Apr 23 13:41:28 2018
ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 139
InstallationDate: Installed on 2018-04-23 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: pygobject
Title: package python-gi 3.24.1-2build1 failed to install/upgrade: le 
sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 139
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  package python-gi 3.24.1-2build1 failed to install/upgrade: le sous-
  processus script post-installation installé a retourné une erreur de
  sortie d'état 139

Status in pygobject package in Ubuntu:
  New

Bug description:
  Tried to install pulseaudio-equalizer

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: python-gi 3.24.1-2build1
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Mon Apr 23 13:41:28 2018
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 139
  InstallationDate: Installed on 2018-04-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: pygobject
  Title: package python-gi 3.24.1-2build1 failed to install/upgrade: le 
sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 139
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1766129] Re: Clicking any checkbox freezes the program

[Ads20000]

OK, scratch that, Text Editor eventually opened (and the bug screen
opened). I think it wasn't working because system.journal is so big and
thus Text Editor really struggled with it (should it handle big files
better, maybe?)! My bad. Nano can't seem to read it either though
(gobbledygook again).

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

Title:
  Clicking any checkbox freezes the program

Status in software-properties package in Ubuntu:
  New

Bug description:
  Upgraded to 18.04 today and clicking any checkbox in Software &
  Updates freezes the program (at least, in the Communitheme Wayland
  session (`snap install communitheme --edge` 0.1 (73))).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sun Apr 22 23:52:47 2018
  InstallationDate: Installed on 2017-08-03 (262 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to bionic on 2018-04-22 (0 days ago)

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

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

[Touch-packages] [Bug 1753333] Re: Using "Software and Updates -> Additional Drivers" to Switch Fails

[Alberto Milone]

** Also affects: software-properties (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: software-properties (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

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

Title:
  Using "Software and Updates -> Additional Drivers" to Switch Fails

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Triaged
Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  When you are in the initial install state, you can easily switch from
  the Nouvea drivers to the Nvidia drivers by choosing the option in
  "Software and Updates -> Additional Drivers".  However, when you
  attempt to switch back (by selecting the nouveau option and clicking
  Apply), and subsequently reboot, your system will still come up using
  the Nvidia drivers, and you will WTF.

  And then, if you visit Additional Drivers, you will be presented with
  grayed out options for both nvidia and nouvea, and the only selectable
  option will be "continue using manually installed driver".

  The reason for this is that the tool, when reselecting nvidia in the
  GUI, uninstalls the nvidia-drivers-390 package, but because it's a
  metapackage (or at least I presume this is the reason), it doesn't
  uninstall its dependencies, which causes the Additional Drivers tool
  to believe it's in a non-automanaged state, and the nvidia drivers
  never actually get uninstalled.

  You can fix it by doing an apt autoremove and rerunning the Additional
  Drivers tool.  But obviously there is no real way for inexperienced
  users to know this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/175/+subscriptions

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

[Touch-packages] [Bug 1765923] Re: Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug?

[Rik Mills]

Is this a machine with hybrid graphics?

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

Title:
  Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug?

Status in apt package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in sddm package in Ubuntu:
  New

Bug description:
  Using the April 19th daily build of Kubuntu 18.04 I installed the
  Nvidia drivers via the following command.

  sudo ubuntu-drivers autoinstall

  The install process proceeds fine and after a logout process I get a
  black screen.  I tried this on the April 17th daily build of bionic
  and a reboot also results in a black screen.

  The following is a question which was submitted by a Ubuntu 17.10 user: QUOTE
  After I installed latest Nvidia driver-390 and tried to boot after shutting 
down once I faced a black screen problem. since, I'm a noob but something 
related to nvidia drivers couldn't be started. Then I followed 
https://askubuntu.com/a/968692/802490
  While following these instructions re-installing of nvidia drivers failed. 
The only things that worked is purging the drivers and changing 
"WaylandEnable=false" in (/etc/gdm3/custom.conf). Now, I want to re-install 
nvidia drivers again but I'm afraid that this will lead to that problem again. 
Can anyone help in re-installing the driver such that I won't face that 
problem?  END QUOTE

  THE WORK AROUND

  Use Ctrl-Alt-f6 to get to a login prompt.
  Login
  run  "startx"

  The x server will start and Nvidia drivers will function.

  THE PROBLEM
  When I try to run SDDM I get an error (Which I will try to copy down to add 
to this bug when I am on a different computer than the one I am reporting the 
bug about.).

  Installing lightDM does not work... it installs but is either will not
  run or will not actually start a x session.

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

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

[Touch-packages] [Bug 1766129] Re: Clicking any checkbox freezes the program

[Ads20000]

`cat /var/log/journal/b0a7fe29cb42426a87b70467f02ead86/system.journal`
produces gobbledygook (another bug that I should report?!)

Stuff like 
��_�M>��˜X���/�.d`�8��!:��A��8�!��ʼ�h�8�V�@�fF��8�]M�Bn��9�Q
z4J�h
9`U@9��a��u�9�ב��x�p9jʸ��~9�՟��9��g�^0�`9���K��^M9%��{��@ͨ9�֗Su�x9��sA�9��xË�89M
_�j��"�92jɛQI��H9��z�5[�b�9���9�fO���P9�@۠�:҂�9B�ةO\@�
-V�f��j2�Aa

  
��_�M>��˜X���/�.d`�8��!:��A��8�!��ʼ�h�8�V�@�fF��8�]M�Bn��9�Q
z4J�h
9`U@9��a��u�9�ב��x�p9jʸ��~9�՟��9��g�^0�`9���K��^M9%��{��@ͨ9�֗Su�x9��sA�9��xË�89M
_�j��"�92jɛQI��H9��z�5[�b�9���9�fO���P9�@۠�:҂�9B�ةO\

Cat seems to read other text files fine...idk what stuff that file would
have in it so not sure I want to attach it without my being able to read
it?

I know I upgraded early so I have to accept the possibility that I've
simply ruined my computer somehow, but equally it's in Final Freeze and
many will be manually upgrading soon...

I can't open anything with Text Editor, which I'm trying to report,
Launchpad keeps refreshing on the +filebug page (after running `ubuntu-
bug gedit`).

I'm on IRC if you'd rather do things quickfire there :)

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

Title:
  Clicking any checkbox freezes the program

Status in software-properties package in Ubuntu:
  New

Bug description:
  Upgraded to 18.04 today and clicking any checkbox in Software &
  Updates freezes the program (at least, in the Communitheme Wayland
  session (`snap install communitheme --edge` 0.1 (73))).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sun Apr 22 23:52:47 2018
  InstallationDate: Installed on 2017-08-03 (262 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to bionic on 2018-04-22 (0 days ago)

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

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

[Łukasz Zemczak]

The verification of the Stable Release Update for pulseaudio 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 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:
  Fix Committed

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 list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1721955] Re: Human and Human-Clearlooks themes have incorrect gray window title color

[Norbert]

** Description changed:

  Steps to reproduce:
  1. Install Ubuntu 17.10 MATE or 18.04 LTS MATE
  2. Install Human theme from `human-theme` package
  3. Select Human theme from `mate-control-center` Appearance
  
  Expected results:
- window title color is set to Ubuntu's orange (#cf8a31)
+ window title color is set to Ubuntu's orange (#FFBE6B)
  
  Actual results:
  window title color is set to different gray/silver color (#a5a5a2)
+ 
+ Note:
+ other themes are affected too.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: human-theme 0.39.2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic i686
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: i386
  CurrentDesktop: MATE
  Date: Sat Oct  7 15:43:03 2017
  InstallationDate: Installed on 2017-10-07 (0 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 
(20170925.1)
  PackageArchitecture: all
  SourcePackage: human-theme
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

** Also affects: gtk+2.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- Human and Human-Clearlooks themes have incorrect gray window title color
+ Human, Human-Clearlooks and other themes have incorrect gray window title 
color

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

Title:
  Human, Human-Clearlooks and other themes have incorrect gray window
  title color

Status in community-themes package in Ubuntu:
  New
Status in compiz package in Ubuntu:
  Confirmed
Status in gtk+2.0 package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in human-theme package in Ubuntu:
  Confirmed
Status in marco package in Ubuntu:
  New
Status in mate-themes package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 17.10 MATE or 18.04 LTS MATE
  2. Install Human theme from `human-theme` package
  3. Select Human theme from `mate-control-center` Appearance

  Expected results:
  window title color is set to Ubuntu's orange (#FFBE6B)

  Actual results:
  window title color is set to different gray/silver color (#a5a5a2)

  Note:
  other themes are affected too.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: human-theme 0.39.2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic i686
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: i386
  CurrentDesktop: MATE
  Date: Sat Oct  7 15:43:03 2017
  InstallationDate: Installed on 2017-10-07 (0 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 
(20170925.1)
  PackageArchitecture: all
  SourcePackage: human-theme
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1746012] Re: please disable xconsole configuration in 50-default.conf to fix "rsyslogd-2007: action 'action 10' suspended, next retry is ..."

[Launchpad Bug Tracker]

This bug was fixed in the package rsyslog - 8.32.0-1ubuntu3

---
rsyslog (8.32.0-1ubuntu3) bionic; urgency=medium

  * tmpfiles.d: Let var.conf to create /var/log with 'd' directive, and
only adjust the permissions of /var/log with 'z' directive, thus
avoiding warnings about duplicate lines for path /var/log. LP:
#1730028

rsyslog (8.32.0-1ubuntu2) bionic; urgency=medium

  * Ensure correct permissions on files that rsyslog writes to. LP:
#1761630
  * Drop upgrade scripts from pre-xenial.

 -- Dimitri John Ledkov   Mon, 09 Apr 2018 14:44:54
+0100

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

Title:
  please disable xconsole configuration in 50-default.conf to fix
  "rsyslogd-2007: action 'action 10' suspended, next retry is ..."

Status in rsyslog package in Ubuntu:
  Fix Released

Bug description:
  I've noticed this for a long time but never looked into it. My logs
  have a bunch of entries of the form:

  rsyslogd-2007: action 'action 10' suspended, next retry is Mon Jan 29
  04:08:13 2018 [v8.16.0 try http://www.rsyslog.com/e/2007 ]

  This is caused by these lines in /etc/rsyslog.d/50-default.conf:

  # The named pipe /dev/xconsole is for the `xconsole' utility.  To use it,
  # you must invoke `xconsole' with the `-file' option:
  # 
  #$ xconsole -file /dev/xconsole [...]
  #
  # NOTE: adjust the list below, or you'll go crazy if you have a reasonably
  #  busy site..
  #
  daemon.*;mail.*;\
news.err;\
*.=debug;*.=info;\
*.=notice;*.=warn   |/dev/xconsole

  /dev/xconsole is not setup by default in Ubuntu. Commenting out the
  above and restarting rsyslog resolves the issue.

  This issue was reported to Debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745492

  and they disabled xconsole configuration by default in 8.14.0-2,
  however subsequent Ubuntu merges left the configuration in
  debian/50-default.conf.

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

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

[Touch-packages] [Bug 1761630] Re: journald takes over /dev/log in bionic, impacts usability of syslog querying

[Launchpad Bug Tracker]

This bug was fixed in the package rsyslog - 8.32.0-1ubuntu3

---
rsyslog (8.32.0-1ubuntu3) bionic; urgency=medium

  * tmpfiles.d: Let var.conf to create /var/log with 'd' directive, and
only adjust the permissions of /var/log with 'z' directive, thus
avoiding warnings about duplicate lines for path /var/log. LP:
#1730028

rsyslog (8.32.0-1ubuntu2) bionic; urgency=medium

  * Ensure correct permissions on files that rsyslog writes to. LP:
#1761630
  * Drop upgrade scripts from pre-xenial.

 -- Dimitri John Ledkov   Mon, 09 Apr 2018 14:44:54
+0100

** Changed in: rsyslog (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  journald takes over /dev/log in bionic, impacts usability of syslog
  querying

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog source package in Bionic:
  Fix Released

Bug description:
  In bionic, /dev/log is now owned by systemd-journald.

  $ sudo fuser -v /dev/log 
   USERPID ACCESS COMMAND
  /run/systemd/journal/dev-log:
   root  1 F systemd
   root628 F systemd-journal
  $

  This is ok; there are good reasons to want to do this.  (Timestamp
  precision that's not dependent on the syslog protocol; logging
  available earlier in boot and later at shutdown; unified queriability
  of logs around services.)

  The logfiles previously populated by rsyslog under /var/log are now
  empty (no longer being updated, and the previous files logrotated
  away):

  $ ls -l /var/log/auth.log
  -rw-r- 1 syslog adm 0 Mar 25 00:06 /var/log/auth.log
  $

  This is also ok, we don't really want log data duplicated in two
  places on the system; so since we now have persistent journal under
  /var/log/journal, we don't want to also create these plaintext files
  by default.

  However, it's not clear that this is by design, rather than by
  accident.  rsyslog is still /configured/ to log to these files; it
  just isn't receiving any data because it no longer controls the
  socket.

  $ sudo lsof -p 852|grep DGRAM
  rsyslogd 852 syslog3u  unix 0x8e5680435000  0t0351 
/run/systemd/journal/syslog type=DGRAM
  $

  Dimitri and I have discussed that rsyslog should continue to function,
  so that users who have remote syslogging configured can still make use
  of this.  It looks like currently this is not the case, because
  journald is not forwarding to rsyslog.

  That is not ok.

  What is also not ok is that, now that logs are only being written to
  the journal by default instead of to syslog files, querying these logs
  by syslog priority only works if you know the syslog facility by
  number (and, afaics, you can only filter by one syslog facility at a
  time).  So whereas before, you could find mail logs by looking in
  /var/log/mail.log by default, you now have to know to run 'journalctl
  SYSLOG_FACILITY=2'; and if you want a view of what was previously in
  /var/log/syslog (i.e. filtering out non-syslog systemd logs, it seems
  the most compact way to express this is 'journalctl --system
  SYSLOG_FACILITY={0,1,2,3,5,6,7,8,9,11,12,13,14,15,16,17,18,19,20,21,22,23}'.

  This is really not good.  Admins have never needed to know the mapping
  of symbolic names to facility numbers to work with syslog; this throws
  away 30 years of convention with log handling.

  If we are going to store the logs in the journal by default, I think
  there needs to be a way to query the logs using symbolic names
  consistent with syslog(3) and /etc/rsyslog.d/50-default.conf.

  I don't think we can release with things in the current state.

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

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

[Touch-packages] [Bug 1730028] Re: logspam about Duplicate line for path "/var/log"

[Launchpad Bug Tracker]

This bug was fixed in the package rsyslog - 8.32.0-1ubuntu3

---
rsyslog (8.32.0-1ubuntu3) bionic; urgency=medium

  * tmpfiles.d: Let var.conf to create /var/log with 'd' directive, and
only adjust the permissions of /var/log with 'z' directive, thus
avoiding warnings about duplicate lines for path /var/log. LP:
#1730028

rsyslog (8.32.0-1ubuntu2) bionic; urgency=medium

  * Ensure correct permissions on files that rsyslog writes to. LP:
#1761630
  * Drop upgrade scripts from pre-xenial.

 -- Dimitri John Ledkov   Mon, 09 Apr 2018 14:44:54
+0100

** Changed in: rsyslog (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  logspam about Duplicate line for path "/var/log"

Status in rsyslog package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in rsyslog source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Invalid

Bug description:
  Similar to bug 1484027, but that's marked 'Fix released', so something
  must have regressed in the meantime.

  $ journalctl | grep "Duplicate line" | wc -l
  58

  $ grep "/var/log " /usr/lib/tmpfiles.d/*
  /usr/lib/tmpfiles.d/00rsyslog.conf:# Override systemd's default 
tmpfiles.d/var.conf to make /var/log writable by
  /usr/lib/tmpfiles.d/00rsyslog.conf:d /var/log 0775 root syslog -
  /usr/lib/tmpfiles.d/var.conf:d /var/log 0755 - - -

  
  Ideally I'd see at most one line about this in my logs.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu20
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Nov  3 19:42:41 2017
  InstallationDate: Installed on 2016-04-04 (578 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160325)
  MachineType: Supermicro SSG-6038R-E1CR16L
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-87-generic.efi.signed 
root=UUID=d1ab8bd8-41d5-4142-92d6-d0926539807b ro
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/systemd-resolved.service → 
/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.0
  dmi.board.asset.tag: Default string
  dmi.board.name: X10DRH-iT
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.0:bd12/17/2015:svnSupermicro:pnSSG-6038R-E1CR16L:pvr123456789:rvnSupermicro:rnX10DRH-iT:rvr1.01:cvnSupermicro:ct1:cvrDefaultstring:
  dmi.product.name: SSG-6038R-E1CR16L
  dmi.product.version: 123456789
  dmi.sys.vendor: Supermicro

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

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

[Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.13.0-39.44

---
linux (4.13.0-39.44) artful; urgency=medium

  * linux: 4.13.0-39.44 -proposed tracker (LP: #1761456)

  * intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) // CVE-2017-5715 (Spectre v2
Intel) // CVE-2017-5754
- x86/mm: Reinitialize TLB state on hotplug and resume

  * intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) // CVE-2017-5715 (Spectre v2 Intel)
- Revert "x86/mm: Only set IBPB when the new thread cannot ptrace current
  thread"
- x86/speculation: Use Indirect Branch Prediction Barrier in context switch

  * DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please
install libelf-dev, libelf-devel or elfutils-libelf-devel (LP: #1760876)
- [Packaging] include the retpoline extractor in the headers

  * retpoline hints: primary infrastructure and initial hints (LP: #1758856)
- [Packaging] retpoline-extract: flag *0xNNN(%reg) branches
- x86/speculation, objtool: Annotate indirect calls/jumps for objtool
- x86/speculation, objtool: Annotate indirect calls/jumps for objtool on 
32bit
- x86/paravirt, objtool: Annotate indirect calls
- [Packaging] retpoline -- add safe usage hint support
- [Packaging] retpoline-check -- only report additions
- [Packaging] retpoline -- widen indirect call/jmp detection
- [Packaging] retpoline -- elide %rip relative indirections
- [Packaging] retpoline -- clear hint information from packages
- KVM: x86: Make indirect calls in emulator speculation safe
- KVM: VMX: Make indirect call speculation safe
- x86/boot, objtool: Annotate indirect jump in secondary_startup_64()
- SAUCE: early/late -- annotate indirect calls in early/late initialisation
  code
- SAUCE: vga_set_mode -- avoid jump tables
- [Config] retpoline -- switch to new format
- [Packaging] retpoline hints -- handle missing files when RETPOLINE not
  enabled
- [Packaging] final-checks -- remove check for empty retpoline files

  * retpoline: ignore %cs:0xNNN constant indirections (LP: #1752655)
- [Packaging] retpoline -- elide %cs:0x constants on i386

  * zfs system process hung on container stop/delete (LP: #1754584)
- SAUCE: Fix non-prefaulted page deadlock (LP: #1754584)

  * zfs-linux 0.6.5.11-1ubuntu5 ADT test failure with linux 4.15.0-1.2
(LP: #1737761)
- SAUCE: (noup) Update zfs to 0.6.5.11-1ubuntu3.2

  * AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10
(LP: #1759312)
- powerpc/64s: Fix NULL AT_BASE_PLATFORM when using DT CPU features

  * btrfs and tar sparse truncate archives (LP: #1757565)
- Btrfs: move definition of the function btrfs_find_new_delalloc_bytes
- Btrfs: fix reported number of inode blocks after buffered append writes

  * efifb broken on ThunderX-based Gigabyte nodes (LP: #1758375)
- drivers/fbdev/efifb: Allow BAR to be moved instead of claiming it

  * Intel i40e PF reset due to incorrect MDD detection (continues...)
(LP: #1723127)
- i40e/i40evf: Account for frags split over multiple descriptors in check
  linearize

  * Fix an issue that when system in S3, USB keyboard can't wake up the system.
(LP: #1759511)
- ACPI / PM: Allow deeper wakeup power states with no _SxD nor _SxW

  * [8086:3e92] display becomes blank after S3 (LP: #1759188)
- drm/i915: Apply Display WA #1183 on skl, kbl, and cfl

  * add audio kernel patches for Raven (LP: #1758364)
- ALSA: hda: Add Raven PCI ID
- ALSA: hda/realtek - Fix ALC700 family no sound issue

  * Cpu utilization showing system time for kvm guests (performance) (sysstat)
(LP: #1755979)
- KVM: PPC: Book3S HV: Fix guest time accounting with 
VIRT_CPU_ACCOUNTING_GEN

  * Kernel panic on a nfsroot system (LP: #1734327)
- Revert "UBUNTU: SAUCE: LSM stacking: add stacking support to apparmor
  network hooks"
- Revert "UBUNTU: SAUCE: LSM stacking: LSM: Infrastructure management of the
  remaining blobs"

  * can't record sound via front headset port on the Dell Precision 3630
(LP: #1759088)
- ALSA: hda/realtek - Fix Dell headset Mic can't record

  * speaker can't output sound anymore after system resumes from S3 on a lenovo
machine with alc257 (LP: #1758829)
- ALSA: hda/realtek - Fix speaker no sound after system resume

  * hda driver initialization takes too much time on the machine with coffeelake
audio controller [8086:a348] (LP: #1758800)
- ALSA: hda - Force polling mode on CFL for fixing codec communication

  * Let headset-mode initialization be called on Dell Precision 3930
(LP: #1757584)
- ALSA: hda/realtek - Add headset mode support for Dell laptop

  * ubuntu_zram_smoke test will cause soft lockup on Artful ThunderX ARM64
(LP: #1755073)
- SAUCE: crypto: thunderx_zip: Fix 

[Touch-packages] [Bug 1761630] Re: journald takes over /dev/log in bionic, impacts usability of syslog querying

[Dimitri John Ledkov]

The current rsyslog does not store logs properly, nor accept remote logs
(well accepts, but they end up nowhere). This update solves all that.

** Tags removed: block-proposed

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

Title:
  journald takes over /dev/log in bionic, impacts usability of syslog
  querying

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog source package in Bionic:
  Fix Released

Bug description:
  In bionic, /dev/log is now owned by systemd-journald.

  $ sudo fuser -v /dev/log 
   USERPID ACCESS COMMAND
  /run/systemd/journal/dev-log:
   root  1 F systemd
   root628 F systemd-journal
  $

  This is ok; there are good reasons to want to do this.  (Timestamp
  precision that's not dependent on the syslog protocol; logging
  available earlier in boot and later at shutdown; unified queriability
  of logs around services.)

  The logfiles previously populated by rsyslog under /var/log are now
  empty (no longer being updated, and the previous files logrotated
  away):

  $ ls -l /var/log/auth.log
  -rw-r- 1 syslog adm 0 Mar 25 00:06 /var/log/auth.log
  $

  This is also ok, we don't really want log data duplicated in two
  places on the system; so since we now have persistent journal under
  /var/log/journal, we don't want to also create these plaintext files
  by default.

  However, it's not clear that this is by design, rather than by
  accident.  rsyslog is still /configured/ to log to these files; it
  just isn't receiving any data because it no longer controls the
  socket.

  $ sudo lsof -p 852|grep DGRAM
  rsyslogd 852 syslog3u  unix 0x8e5680435000  0t0351 
/run/systemd/journal/syslog type=DGRAM
  $

  Dimitri and I have discussed that rsyslog should continue to function,
  so that users who have remote syslogging configured can still make use
  of this.  It looks like currently this is not the case, because
  journald is not forwarding to rsyslog.

  That is not ok.

  What is also not ok is that, now that logs are only being written to
  the journal by default instead of to syslog files, querying these logs
  by syslog priority only works if you know the syslog facility by
  number (and, afaics, you can only filter by one syslog facility at a
  time).  So whereas before, you could find mail logs by looking in
  /var/log/mail.log by default, you now have to know to run 'journalctl
  SYSLOG_FACILITY=2'; and if you want a view of what was previously in
  /var/log/syslog (i.e. filtering out non-syslog systemd logs, it seems
  the most compact way to express this is 'journalctl --system
  SYSLOG_FACILITY={0,1,2,3,5,6,7,8,9,11,12,13,14,15,16,17,18,19,20,21,22,23}'.

  This is really not good.  Admins have never needed to know the mapping
  of symbolic names to facility numbers to work with syslog; this throws
  away 30 years of convention with log handling.

  If we are going to store the logs in the journal by default, I think
  there needs to be a way to query the logs using symbolic names
  consistent with syslog(3) and /etc/rsyslog.d/50-default.conf.

  I don't think we can release with things in the current state.

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

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

[Touch-packages] [Bug 1764445] Re: the system is running in low-graphics mode

[Chris Perry]

This might be the same bug as #1764087

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

Title:
  the system is running in low-graphics mode

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu probably not recognizing installed Intel graphics driver

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr 16 17:38:17 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor 
Graphics Controller [1043:844d]
  InstallationDate: Installed on 2016-06-01 (684 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-119-generic 
root=UUID=108b2d66-e751-447b-8aed-a462e8ece73b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-M LX2 R2.0
  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.:bvr1501:bd09/02/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2R2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Apr 16 16:59:16 2018
  xserver.configfile: default
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Touch-packages] [Bug 1764087] Re: Wrongly boots into low graphics mode

[Chris Perry]

This might be the same bug as #1764445

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

Title:
  Wrongly boots into low graphics mode

Status in xorg package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  Lenovo T410 with VGA compatible controller [0300]: Intel Corporation
  Core Processor Integrated Graphics Controller [8086:0046] (rev 02)

  Booting from latest kernel ThinkPad-T410 4.13.0-38-generic
  #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 x86_64 x86_64
  x86_64 GNU/Linux goes into low graphics mode and also effects wi-fi
  connection insofar as it does not connect to my router.

  Whereas booting from 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar
  7 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux works most of the
  time but occasionally has the same effects.

  I have had to submit this report after booting from 4.13.0.37 in order
  to submit bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Apr 15 10:40:31 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
  InstallationDate: Installed on 2016-09-24 (567 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2519Y11
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=UUID=58d362c2-ed1e-479b-84f5-e5d8a782b08f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET85WW (1.45 )
  dmi.board.name: 2519Y11
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T410
  dmi.product.name: 2519Y11
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 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: Sun Apr 15 08:52:27 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1765972] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

[Launchpad Bug Tracker]

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

** Changed in: ca-certificates (Ubuntu)
   Status: New => Confirmed

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 1

Status in ca-certificates package in Ubuntu:
  Confirmed

Bug description:
  sudo apt -y dist-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Sat Apr 21 09:46:12 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2014-05-08 (1443 days ago)
  InstallationMedia: Linux Mint 16 "petra" - Release amd64 20131126
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to bionic on 2018-03-17 (35 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1765972/+subscriptions

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

[Touch-packages] [Bug 1766129] Re: Clicking any checkbox freezes the program

[Sebastien Bacher]

Could you add the stdout from when getting the issue or the journal log
around that time?

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

Title:
  Clicking any checkbox freezes the program

Status in software-properties package in Ubuntu:
  New

Bug description:
  Upgraded to 18.04 today and clicking any checkbox in Software &
  Updates freezes the program (at least, in the Communitheme Wayland
  session (`snap install communitheme --edge` 0.1 (73))).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sun Apr 22 23:52:47 2018
  InstallationDate: Installed on 2017-08-03 (262 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to bionic on 2018-04-22 (0 days ago)

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

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

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

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in systemd package in Ubuntu:
  New

Bug description:
  non-tech person - no further info

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu8
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Apr 23 06:52:09 2018
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2018-03-28 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  MachineType: LENOVO 20KHCTO1WW
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __GI___pthread_timedjoin_ex (threadid=13976813136, thread_return=0x0, 
abstime=0x0, block=) at pthread_join_common.c:89
   ?? () from /lib/systemd/libsystemd-shared-237.so
   ?? () from /lib/systemd/libsystemd-shared-237.so
   journal_file_append_object () from /lib/systemd/libsystemd-shared-237.so
   ?? () from /lib/systemd/libsystemd-shared-237.so
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  Title: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 02/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET37W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  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:bvrN23ET37W(1.12):bd02/27/2018:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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