[Bug 2059779] Re: can't update in discover

[Keith Gibbons]

I have the same issue here

Cannot remove system package:WARNING: You are trying to
remove the following essential packages: libssl3 (due to coreutils)
libapt-pkg6.0 (due to apt) libgnutls30 (due to apt) libext2fs2 (due to
e2fsprogs) 

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059779

Title:
  can't update in discover

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1898493] Re: /dev/dri/card0 not closed when plasmashell forks

[Keith Owens]

Retested on plasma-workspace 4:5.24.7-0ubuntu0.1. xterm no longer
inherits /dev/dri/card0. Close the bug.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898493

Title:
  /dev/dri/card0 not closed when plasmashell forks

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1993081] Re: Installing samba-dev:i386 breaks Ubuntu 22.04.1.

[Keith David Bershatsky]

Understood ... please go ahead and close this bug report.  Thank you.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1993081

Title:
  Installing samba-dev:i386 breaks Ubuntu 22.04.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/1993081/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1975429] [NEW] package hddtemp 0.3-beta15-53 failed to install/upgrade: installed hddtemp package post-installation script subprocess was killed by signal (Broken pipe)

[Keith L. Foster]

Public bug reported:

just get notice every time I start computer.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: hddtemp 0.3-beta15-53
ProcVersionSignature: Ubuntu 5.4.0-110.124-generic 5.4.181
Uname: Linux 5.4.0-110-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat May 21 16:05:07 2022
DuplicateSignature:
 package:hddtemp:0.3-beta15-53
 Setting up hddtemp (0.3-beta15-53) ...
 dpkg: error processing package hddtemp (--configure):
  installed hddtemp package post-installation script subprocess was killed by 
signal (Broken pipe)
ErrorMessage: installed hddtemp package post-installation script subprocess was 
killed by signal (Broken pipe)
InstallationDate: Installed on 2022-05-21 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.8
SourcePackage: hddtemp
Title: package hddtemp 0.3-beta15-53 failed to install/upgrade: installed 
hddtemp package post-installation script subprocess was killed by signal 
(Broken pipe)
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975429

Title:
  package hddtemp 0.3-beta15-53 failed to install/upgrade: installed
  hddtemp package post-installation script subprocess was killed by
  signal (Broken pipe)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956535] [NEW] nvidia-kernel-source-495 495.46-0ubuntu0.21.10.1: nvidia kernel module failed to build

[Keith Cecere]

Public bug reported:

Errors while upgrading nvidia v495

ProblemType: Package
DistroRelease: Ubuntu 21.10
Package: nvidia-kernel-source-495 495.46-0ubuntu0.21.10.1
ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
Uname: Linux 5.13.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: unknown
DKMSKernelVersion: 5.13.0-22-generic
Date: Wed Jan  5 17:40:46 2022
Dependencies:
 
InstallationDate: Installed on 2018-08-18 (1236 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageVersion: 495.46-0ubuntu0.21.10.1
Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9
RelatedPackageVersions:
 dpkg 1.20.9ubuntu2
 apt  2.3.9
SourcePackage: nvidia-graphics-drivers-495
Title: nvidia-kernel-source-495 495.46-0ubuntu0.21.10.1: nvidia kernel module 
failed to build
UpgradeStatus: Upgraded to impish on 2021-10-14 (82 days ago)

** Affects: nvidia-graphics-drivers-495 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package impish

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956535

Title:
  nvidia-kernel-source-495 495.46-0ubuntu0.21.10.1: nvidia kernel module
  failed to build

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1950524] [NEW] package nvidia-dkms-495 495.44-0ubuntu0.21.10.1 failed to install/upgrade: installed nvidia-dkms-495 package post-installation script subprocess returned error exit status 10

[Keith Cecere]

Public bug reported:

Failed to update nvidia driver

ProblemType: Package
DistroRelease: Ubuntu 21.10
Package: nvidia-dkms-495 495.44-0ubuntu0.21.10.1
ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
Uname: Linux 5.13.0-21-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Tue Nov  9 18:10:09 2021
ErrorMessage: installed nvidia-dkms-495 package post-installation script 
subprocess returned error exit status 10
InstallationDate: Installed on 2018-08-18 (1179 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9
RelatedPackageVersions:
 dpkg 1.20.9ubuntu2
 apt  2.3.9
SourcePackage: nvidia-graphics-drivers-495
Title: package nvidia-dkms-495 495.44-0ubuntu0.21.10.1 failed to 
install/upgrade: installed nvidia-dkms-495 package post-installation script 
subprocess returned error exit status 10
UpgradeStatus: Upgraded to impish on 2021-10-14 (26 days ago)

** Affects: nvidia-graphics-drivers-495 (Ubuntu)
 Importance: Undecided
 Status: New


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950524

Title:
  package nvidia-dkms-495 495.44-0ubuntu0.21.10.1 failed to
  install/upgrade: installed nvidia-dkms-495 package post-installation
  script subprocess returned error exit status 10

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1938953] Re: virtualbox-dkms 6.1.16-dfsg-6~ubuntu1.20.04.2: virtualbox kernel module failed to build

[Keith]

For anyone who sees this, it is a RAM issue. For me, like others here,
the hardware is the cause.

Lack of RAM. I installed another 16 GB and my RAM usage went away.
Freezes and random crashes stopped. The lack of RAM will also cause
PulseAudio to distort, prompting a -k.

Hopefully this helps someone.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938953

Title:
  virtualbox-dkms 6.1.16-dfsg-6~ubuntu1.20.04.2: virtualbox kernel
  module failed to build

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1937848] [NEW] package postfix (not installed) failed to install/upgrade: installed postfix package post-installation script subprocess returned error exit status 75

[Keith Whittington]

Public bug reported:

error occurs during normal system updates

ProblemType: Package
DistroRelease: Ubuntu 21.04
Package: postfix (not installed)
ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu65.1
AptOrdering:
 ubuntu-drivers-common:amd64: Install
 libcurl3-gnutls:amd64: Install
 libcurl4:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Fri Jul 23 11:30:47 2021
ErrorMessage: installed postfix package post-installation script subprocess 
returned error exit status 75
InstallationDate: Installed on 2018-04-30 (1179 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.20.9ubuntu1
 apt  2.2.4ubuntu0.1
SourcePackage: postfix
Title: package postfix (not installed) failed to install/upgrade: installed 
postfix package post-installation script subprocess returned error exit status 
75
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937848

Title:
  package postfix (not installed) failed to install/upgrade: installed
  postfix package post-installation script subprocess returned error
  exit status 75

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI

[Keith Jackson]

Excellent. I'll use the SSH option as I've got a working Ubuntu laptop
of that's more useful. Thanks for the info.

Get Outlook for Android


From: nore...@launchpad.net  on behalf of Daniel Dadap 
<1930...@bugs.launchpad.net>
Sent: Wednesday, July 21, 2021 10:01:06 PM
To: temporal-...@live.co.uk 
Subject: [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when 
using DP, but not with HDMI

> should it fail how can I get the log when my system completely locks
up and dies?

My understanding of the bug is that it occurs when the NVIDIA driver
tries to bring up the DisplayPort link on certain DisplayPort monitors.
You should be able to drive the system in text mode with a failing
driver, to capture the log. One way to do that would be to add
"systemd.unit=multi-user.target" to the kernel command line. (When the
bootloader menu comes up, edit the boot options and add this argument to
the line that starts with 'linux'.) If you happen to have another system
on the same network you can even try SSHing into the system that
reproduces the problem, then start the graphical session manually with
`sudo systemctl isolate graphical`, and if the crash doesn't take down
the SSH session, you ought to be able to generate the log file while the
problem is occurring. (Log files taken while a bug is actively being
reproduced tend to be the most useful.) Depending on the exact nature of
the crash, you may even be able to SSH into a system which has already
crashed, without having to go to the effort of starting it in text mode
first.

> In that eventuality I've only been able to recover by booting an older
kernel with the older drivers. Will that not invalidate the log content
on restart?

It may, or may not. nvidia-bug-report.sh attempts to capture logs from
the previous boot, if they have been retained. If you do find that you
are unable to capture a log file using a driver version which reproduces
the problem, just make sure to note that you captured the log file after
rebooting to a known good driver.

--
You received this bug notification because you are subscribed to the bug
report.
https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fbugs%2F1930733data=04%7C01%7C%7Ccefaf8b686a044088e3d08d94c8c0036%7C84df9e7fe9f640afb435%7C1%7C0%7C637624986447380869%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=eO8jfN5MbevXRAqp0irMe22IyOABsKE3YlvBENkoYH8%3Dreserved=0

Title:
  Kernel oops with the 460.80 and 465.27 drivers when using DP, but not
  with HDMI

Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-465 package in Ubuntu:
  Triaged

Bug description:
  I get a kernel oops with the 460.80 and 465.27 drivers on Hirsute

  Jun 03 16:26:57 willow kernel: Oops:  [#1] SMP PTI
  Jun 03 16:26:57 willow kernel: CPU: 7 PID: 2004 Comm: Xorg Tainted: P 
  OE 5.11.0-18-generic #19-Ubuntu
  Jun 03 16:26:57 willow kernel: Hardware name: System manufacturer System 
Product Name/PRIME H270M-PLUS, BIOS 1605 12/13/2019
  Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia]
  Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 
00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 
44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8>
  Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297
  Jun 03 16:26:57 willow kernel: RAX:  RBX: 0400 
RCX: 0003
  Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 
RDI: 
  Jun 03 16:26:57 willow kernel: RBP: 8e318220add0 R08: 0001 
R09: 8e318220acb8
  Jun 03 16:26:57 willow kernel: R10: 8e3182204008 R11: 1010 
R12: 0400
  Jun 03 16:26:57 willow kernel: R13: 0003 R14: 8e3186ca8010 
R15: 0800
  Jun 03 16:26:57 willow kernel: FS:  7f5807f38a40() 
GS:8e3466dc() knlGS:
  Jun 03 16:26:57 willow kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Jun 03 16:26:57 willow kernel: CR2: 0170 CR3: 000140710005 
CR4: 003706e0
  Jun 03 16:26:57 willow kernel: DR0:  DR1:  
DR2: 
  Jun 03 16:26:57 willow kernel: DR3:  DR6: fffe0ff0 
DR7: 0400
  Jun 03 16:26:57 willow kernel: Call Trace:
  Jun 03 16:26:57 willow kernel:  ? _nv015556rm+0x7fd/0x1020 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv027155rm+0x22c/0x4f0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv017787rm+0x303/0x5e0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv017789rm+0xe1/0x220 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv022829rm+0xed/0x220 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv023065rm+0x30/0x60 [nvidia]
  Jun 03 

Re: [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI

[Keith Jackson]

I'll be attempting an upgrade next week if the drivers are now in the
canonical repositories but, should it fail how can I get the log when my
system completely locks up and dies?

In that eventuality I've only been able to recover by booting an older
kernel with the older drivers. Will that not invalidate the log content
on restart?

If there's a way I can stop at a terminal and dump the files to a stick
before I restore can you provide instructions on how that can be done
then if all is in vain, then at least I can get you useful info.

I'm a fairly noobish user but happy to help as much as I can.

Get Outlook for Android


From: nore...@launchpad.net  on behalf of Daniel Dadap 
<1930...@bugs.launchpad.net>
Sent: Wednesday, July 21, 2021 5:56:48 PM
To: temporal-...@live.co.uk 
Subject: [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when 
using DP, but not with HDMI

Hello, NVIDIA employee here.

Can those who are still experiencing problems please provide the
following information?

* NVIDIA driver version installed
* NVIDIA GPU model
* Exact model of affected monitor

An nvidia-bug-report.log will capture the driver version and GPU model,
along with some other useful information, though possibly not the
monitor model since the system may be crashing before the EDID can be
read. You can generate an nvidia-bug-report.log file by running `nvidia-
bug-report.sh` as root. This will create a new file named nvidia-bug-
report.log.gz in your current directory.

As for the fix being absent from the release notes, that was an
accidental omission. The fix should be present in 460.91.03 and later,
as well as all publicly released 470 drivers. Unfortunately, the fix did
not make it into 465 before support for the 465 series was discontinued.
We will want to collect the relevant information for anybody still
experiencing problems with DP monitors so that any remaining issues can
be addressed as well.

--
You received this bug notification because you are subscribed to the bug
report.
https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fbugs%2F1930733data=04%7C01%7C%7C50e47dc149644e6a68ec08d94c69c870%7C84df9e7fe9f640afb435%7C1%7C0%7C637624839480958737%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=489S6ZVdRRW7P6PbuM6zRIKofoHn5s%2FaL4oCti18y9s%3Dreserved=0

Title:
  Kernel oops with the 460.80 and 465.27 drivers when using DP, but not
  with HDMI

Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-465 package in Ubuntu:
  Triaged

Bug description:
  I get a kernel oops with the 460.80 and 465.27 drivers on Hirsute

  Jun 03 16:26:57 willow kernel: Oops:  [#1] SMP PTI
  Jun 03 16:26:57 willow kernel: CPU: 7 PID: 2004 Comm: Xorg Tainted: P 
  OE 5.11.0-18-generic #19-Ubuntu
  Jun 03 16:26:57 willow kernel: Hardware name: System manufacturer System 
Product Name/PRIME H270M-PLUS, BIOS 1605 12/13/2019
  Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia]
  Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 
00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 
44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8>
  Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297
  Jun 03 16:26:57 willow kernel: RAX:  RBX: 0400 
RCX: 0003
  Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 
RDI: 
  Jun 03 16:26:57 willow kernel: RBP: 8e318220add0 R08: 0001 
R09: 8e318220acb8
  Jun 03 16:26:57 willow kernel: R10: 8e3182204008 R11: 1010 
R12: 0400
  Jun 03 16:26:57 willow kernel: R13: 0003 R14: 8e3186ca8010 
R15: 0800
  Jun 03 16:26:57 willow kernel: FS:  7f5807f38a40() 
GS:8e3466dc() knlGS:
  Jun 03 16:26:57 willow kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Jun 03 16:26:57 willow kernel: CR2: 0170 CR3: 000140710005 
CR4: 003706e0
  Jun 03 16:26:57 willow kernel: DR0:  DR1:  
DR2: 
  Jun 03 16:26:57 willow kernel: DR3:  DR6: fffe0ff0 
DR7: 0400
  Jun 03 16:26:57 willow kernel: Call Trace:
  Jun 03 16:26:57 willow kernel:  ? _nv015556rm+0x7fd/0x1020 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv027155rm+0x22c/0x4f0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv017787rm+0x303/0x5e0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv017789rm+0xe1/0x220 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv022829rm+0xed/0x220 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv023065rm+0x30/0x60 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv000704rm+0x16da/0x22b0 [nvidia]
  Jun 03 16:26:57 willow 

Re: [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI

[Keith Jackson]

The server driver doesn't work for my setup. I could try the beta
package but at the moment it's working as it is, updates aside. I'm just
after an idea of timescale for a proper fix with 470, not in a mad rush.

I'm not inclined to experiment at the moment due to other priorities and
I can't afford to be without my PC for an extended period.

As long as we get a post on here keeping us up to date with when the
fixed packages are in the Ubuntu upgrade repositories that's good enough
for me. Then I can just unlock everything, upgrade, cross all my fingers
and hope all is well!

Get Outlook for Android


From: boun...@canonical.com  on behalf of S?nke Lorenzen 
<1930...@bugs.launchpad.net>
Sent: Wednesday, July 14, 2021 7:15:35 PM
To: temporal-...@live.co.uk 
Subject: [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when 
using DP, but not with HDMI

You have to install another driver than nvidia-driver-460 in order to
update all your packages again. This is because nvidia-driver-460 does
have the version 460.80 in the repositories now.

Easiest is to change to nvidia-driver-460-server if that works for you,
next easiest is to enable the PPA I mentioned above to install the 470
beta driver.

--
You received this bug notification because you are subscribed to the bug
report.
https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fbugs%2F1930733data=04%7C01%7C%7Ca554b67baec7490041ec08d946f41882%7C84df9e7fe9f640afb435%7C1%7C0%7C637618836455319573%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=s3aOcRT0weNNtu723VwqY7uELxuEopJBSoxp14eX4zI%3Dreserved=0

Title:
  Kernel oops with the 460.80 and 465.27 drivers when using DP, but not
  with HDMI

Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-465 package in Ubuntu:
  Triaged

Bug description:
  I get a kernel oops with the 460.80 and 465.27 drivers on Hirsute

  Jun 03 16:26:57 willow kernel: Oops:  [#1] SMP PTI
  Jun 03 16:26:57 willow kernel: CPU: 7 PID: 2004 Comm: Xorg Tainted: P 
  OE 5.11.0-18-generic #19-Ubuntu
  Jun 03 16:26:57 willow kernel: Hardware name: System manufacturer System 
Product Name/PRIME H270M-PLUS, BIOS 1605 12/13/2019
  Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia]
  Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 
00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 
44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8>
  Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297
  Jun 03 16:26:57 willow kernel: RAX:  RBX: 0400 
RCX: 0003
  Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 
RDI: 
  Jun 03 16:26:57 willow kernel: RBP: 8e318220add0 R08: 0001 
R09: 8e318220acb8
  Jun 03 16:26:57 willow kernel: R10: 8e3182204008 R11: 1010 
R12: 0400
  Jun 03 16:26:57 willow kernel: R13: 0003 R14: 8e3186ca8010 
R15: 0800
  Jun 03 16:26:57 willow kernel: FS:  7f5807f38a40() 
GS:8e3466dc() knlGS:
  Jun 03 16:26:57 willow kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Jun 03 16:26:57 willow kernel: CR2: 0170 CR3: 000140710005 
CR4: 003706e0
  Jun 03 16:26:57 willow kernel: DR0:  DR1:  
DR2: 
  Jun 03 16:26:57 willow kernel: DR3:  DR6: fffe0ff0 
DR7: 0400
  Jun 03 16:26:57 willow kernel: Call Trace:
  Jun 03 16:26:57 willow kernel:  ? _nv015556rm+0x7fd/0x1020 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv027155rm+0x22c/0x4f0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv017787rm+0x303/0x5e0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv017789rm+0xe1/0x220 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv022829rm+0xed/0x220 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv023065rm+0x30/0x60 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv000704rm+0x16da/0x22b0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? rm_init_adapter+0xc5/0xe0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? nv_open_device+0x122/0x8e0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? nvidia_open+0x2b7/0x560 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? nvidia_frontend_open+0x58/0xa0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? chrdev_open+0xf7/0x220
  Jun 03 16:26:57 willow kernel:  ? cdev_device_add+0x90/0x90
  Jun 03 16:26:57 willow kernel:  ? do_dentry_open+0x156/0x370
  Jun 03 16:26:57 willow kernel:  ? vfs_open+0x2d/0x30
  Jun 03 16:26:57 willow kernel:  ? do_open+0x1c3/0x340
  Jun 03 16:26:57 willow kernel:  ? path_openat+0x10a/0x1d0
  Jun 03 16:26:57 willow kernel:  ? do_filp_open+0x8c/0x130
  Jun 03 16:26:57 willow kernel:  ? 

Re: [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI

[Keith Jackson]

It was only kernel related in that the update from .53 to .55 also
updated my NVidia drivers at the same time - I assume due to being a
dependency. I was unable to boot my PC in that kernel at all in order to
fix it or downgrade any driver packages so I've been locked on .53 ever
since effectively, with 460.73. I noticed today that a new kernel is out
(.58?) but if that also updates my graphics drivers then I'm still up
creek without a paddle.

Just after some info as to when I can safely unblock my updates and
upgrade safely again.

Get Outlook for Android<https://aka.ms/AAb9ysg>

From: boun...@canonical.com  on behalf of S?nke Lorenzen 
<1930...@bugs.launchpad.net>
Sent: Wednesday, July 14, 2021 5:35:19 PM
To: temporal-...@live.co.uk 
Subject: [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when 
using DP, but not with HDMI

@Keith
This does not seem to be kernel related, when I upgraded to  460.80 and 465.27 
and got hit by this bug, I first tried to boot with older kernels I had 
installed with the same problem then. And look at 
https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fforums.developer.nvidia.com%2Ft%2F465-24-02-page-fault%2F175782data=04%7C01%7C%7Cd40c289b7ac7494ecf2108d946e62a60%7C84df9e7fe9f640afb435%7C1%7C0%7C637618776640052404%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=yCd5zPkJLnn2aaO0LO7XjVtmZ8KQOYcDBhRRED9vdr0%3Dreserved=0
 there users have tried a lot of different kernels without it helping.

You can either install the nvidia-driver-460-server which is at
460.73.01, or install it manually if it gives other problems, see above.
Or use the 470 beta from
https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flaunchpad.net%2F~albertomilone%2F%2Barchive%2Fubuntu%2Fnvidia-testingdata=04%7C01%7C%7Cd40c289b7ac7494ecf2108d946e62a60%7C84df9e7fe9f640afb435%7C1%7C0%7C637618776640052404%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=pVGDfRT2eLoO3SULG6sXT3n0hRVt5PU41mneHXzxUds%3Dreserved=0

And then just update all other packages including kernels.

--
You received this bug notification because you are subscribed to the bug
report.
https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fbugs%2F1930733data=04%7C01%7C%7Cd40c289b7ac7494ecf2108d946e62a60%7C84df9e7fe9f640afb435%7C1%7C0%7C637618776640062360%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=dSSz4TkfyQz2sCFnbas%2BmEd66JJXQoAFfJA4sj%2F9OXQ%3Dreserved=0

Title:
  Kernel oops with the 460.80 and 465.27 drivers when using DP, but not
  with HDMI

Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-465 package in Ubuntu:
  Triaged

Bug description:
  I get a kernel oops with the 460.80 and 465.27 drivers on Hirsute

  Jun 03 16:26:57 willow kernel: Oops:  [#1] SMP PTI
  Jun 03 16:26:57 willow kernel: CPU: 7 PID: 2004 Comm: Xorg Tainted: P 
  OE 5.11.0-18-generic #19-Ubuntu
  Jun 03 16:26:57 willow kernel: Hardware name: System manufacturer System 
Product Name/PRIME H270M-PLUS, BIOS 1605 12/13/2019
  Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia]
  Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 
00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 
44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8>
  Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297
  Jun 03 16:26:57 willow kernel: RAX:  RBX: 0400 
RCX: 0003
  Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 
RDI: 
  Jun 03 16:26:57 willow kernel: RBP: 8e318220add0 R08: 0001 
R09: 8e318220acb8
  Jun 03 16:26:57 willow kernel: R10: 8e3182204008 R11: 1010 
R12: 0400
  Jun 03 16:26:57 willow kernel: R13: 0003 R14: 8e3186ca8010 
R15: 0800
  Jun 03 16:26:57 willow kernel: FS:  7f5807f38a40() 
GS:8e3466dc() knlGS:
  Jun 03 16:26:57 willow kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Jun 03 16:26:57 willow kernel: CR2: 0170 CR3: 000140710005 
CR4: 003706e0
  Jun 03 16:26:57 willow kernel: DR0:  DR1:  
DR2: 
  Jun 03 16:26:57 willow kernel: DR3:  DR6: fffe0ff0 
DR7: 0400
  Jun 03 16:26:57 willow kernel: Call Trace:
  Jun 03 16:26:57 willow kernel:  ? _nv015556rm+0x7fd/0x1020 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv027155rm+0x22c/0x4f0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv017787rm+0x303/0x5e0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv017789rm+0xe1/0x220 [nvid

[Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI

[Keith Jackson]

Do we have an ETA for this? I've had to essentially block any system
upgrades on my desktop since this began after having to roll back a
kernel update that forced this bug on me.

I noticed a new kernel update has just been posted and doesn't seem to
have rolled out this issue yet again.

This isn't a minor annoyance, this is a complete system fail type bug.

This NVidia forum thread has been really useful here:
https://forums.developer.nvidia.com/t/465-24-

It's looking like the bug on NVidia's side seems to have been rectified
in 470.42 - Manjaro have put that to their stable branch, yet I'm not
seeing anything in Ubuntu even in pre-release beyond 460.84.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930733

Title:
  Kernel oops with the 460.80 and 465.27 drivers when using DP, but not
  with HDMI

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1897712] Re: Ugly image output make game unusable

[Keith Trudell]

seen in current version of Ubuntu. Same visual garble.

Ubuntu version: 21.04
Gweled version: 0.9.1

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897712

Title:
  Ugly image output make game unusable

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1931295] Re: After kernel upgrade to 5.8.0.58 my system would no longer boot.

[Keith Jackson]

Apologies - It was 5.8.0.55 (Not 5.8.0.58) that's recently been
installed - sorry working from memory!

I can't seem to edit the title...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931295

Title:
  After kernel upgrade to 5.8.0.58 my system would no longer boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1931295/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1931295] [NEW] After kernel upgrade to 5.8.0.58 my system would no longer boot.

[Keith Jackson]

Public bug reported:

I have generic Ubuntu kernels 5.8.0.53 and 5.8.0.58 on my system.

After starting up following the latest update my system would not boot.
Managed to get back in via Grub manually loading the earlier kernel.

I'm running a custom Quiet PC system with SSD primary drive and data
HDDs.

I'm a bit of a noob here but happy to track down any desired logs etc.
if possible.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.8.0-53-generic 5.8.0-53.60~20.04.1
ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-53-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun  8 19:11:19 2021
InstallationDate: Installed on 2021-04-23 (46 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
SourcePackage: linux-signed-hwe-5.8
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-5.8 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931295

Title:
  After kernel upgrade to 5.8.0.58 my system would no longer boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1931295/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927136] [NEW] Canon printer will not print. Message shows it does print. I can scan

[Keith Jones]

Public bug reported:

Printer worked fine in version 18.  Does not print in version 20.  It
will scan docs back to the computer.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cups 2.3.1-9ubuntu1.1
ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
Uname: Linux 5.4.0-72-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue May  4 12:36:48 2021
InstallationDate: Installed on 2019-12-07 (514 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Lpstat:
 device for Canon-MG3200-series: 
usb://Canon/MG3200%20series?serial=120A84=1
 device for localhost: ///dev/null
MachineType: Dell Inc. Vostro 230
Papersize: letter
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Canon-MG3200-series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Canon-MG3200-series.ppd: Permission denied
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic 
root=UUID=5b75bf38-459b-47b1-95cd-d4beda9dbc47 ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: Upgraded to focal on 2021-03-08 (56 days ago)
dmi.bios.date: 07/07/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.0
dmi.board.name: 07N90W
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.0:bd07/07/2010:svnDellInc.:pnVostro230:pvr00:rvnDellInc.:rn07N90W:rvrA01:cvnDellInc.:ct3:cvrNotSpecified:
dmi.product.family: 0
dmi.product.name: Vostro 230
dmi.product.sku: 0
dmi.product.version: 00
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927136

Title:
  Canon printer will not print. Message shows it does print.  I can scan

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1914861] [NEW] Ubuntu 20.10 grub install fail on Dell R900 with single SSD

[Keith Goodwin]

Public bug reported:

I am using a Dell R900 as a test server with quad CPU configuration and 112GB 
Ram.
I have been unable to install Ubuntu 20.10 onto it and have removed everything 
from the server, down to the base hardware.
There is now only a single SSD in the first drive slot, connected to the Dell 
Perc 6, non raid.
I have tried all options and configurations with the disk configuration in the 
installer.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubiquity 20.10.13
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CasperVersion: 1.455
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb  6 11:08:04 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
 LANGUAGE=en_GB.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 LC_NUMERIC=C.UTF-8
RebootRequiredPkgs:
 linux-image-5.8.0-25-generic
 linux-base
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug groovy ubiquity-20.10.13 ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914861

Title:
  Ubuntu 20.10 grub install fail on Dell R900 with single SSD

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1909949] [NEW] SIGSEGV in x265_10bit::RateControl::rateEstimateQscale()

[Keith Helms]

Public bug reported:

Description:Ubuntu 20.04.1 LTS
Release:20.04

Package libx265-179 version 3.2.1-1build1

Happens randomly under both FFMpeg and HandBrakeCLI.  An encode of the
same file will crash one time, but work the next time.

Excerpt from the crash file:

SegvAnalysis:
 Segfault happened at: 0x7f0613a1f3a0 
<_ZN10x265_10bit11RateControl18rateEstimateQscaleEPNS_5FrameEPNS_16RateControlEntryE+112>:
mov(%r8),%rcx
 PC (0x7f0613a1f3a0) ok
 source "(%r8)" (0x) not located in a known VMA region (needed readable 
region)!
 destination "%rcx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
SourcePackage: ffmpeg
Stacktrace:
 #0  0x7f0613a1f3a0 in 
x265_10bit::RateControl::rateEstimateQscale(x265_10bit::Frame*, 
x265_10bit::RateControlEntry*) () at /lib/x86_64-linux-gnu/libx265.so.179
 #1  0x7f0613a21678 in 
x265_10bit::RateControl::rateControlStart(x265_10bit::Frame*, 
x265_10bit::RateControlEntry*, x265_10bit::Encoder*) () at 
/lib/x86_64-linux-gnu/libx265.so.179
 #2  0x7f0613a12fc1 in x265_10bit::FrameEncoder::compressFrame() () at 
/lib/x86_64-linux-gnu/libx265.so.179
 #3  0x7f0613a1592a in x265_10bit::FrameEncoder::threadMain() () at 
/lib/x86_64-linux-gnu/libx265.so.179
 #4  0x7f06139ec52e in  () at /lib/x86_64-linux-gnu/libx265.so.179
 #5  0x7f061a321609 in start_thread (arg=) at 
pthread_create.c:477
 ret = 
 pd = 
 unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139663137658624, 
8136522380067276986, 140736498594622, 140736498594623, 140736498594624, 
139663137653696, -8151220019210155846, -8149668580039915334}, mask_was_saved = 
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, 
canceltype = 0}}}
 not_first_call = 0
 #6  0x7f061a248293 in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
StacktraceAddressSignature: 
/usr/bin/ffmpeg:11:/usr/lib/x86_64-linux-gnu/libx265.so.179+4f63a0:/usr/lib/x86_64-linux-gnu/libx265.so.179+4f8678:/usr/lib/x86_64-linux-gnu/libx265.so.179+4e9fc1:/usr/lib/x86_64-linux-gnu/libx265.so.179+4ec92a:/usr/lib/x86_64-linux-gnu/libx265.so.179+4c352e:/usr/lib/x86_64-linux-gnu/libpthread-2.31.so+2609:/usr/lib/x86_64-linux-gnu/libc-2.31.so+fd293
StacktraceTop:
 x265_10bit::RateControl::rateEstimateQscale(x265_10bit::Frame*, 
x265_10bit::RateControlEntry*) () at /lib/x86_64-linux-gnu/libx265.so.179
 x265_10bit::RateControl::rateControlStart(x265_10bit::Frame*, 
x265_10bit::RateControlEntry*, x265_10bit::Encoder*) () at 
/lib/x86_64-linux-gnu/libx265.so.179
 x265_10bit::FrameEncoder::compressFrame() () at 
/lib/x86_64-linux-gnu/libx265.so.179
 x265_10bit::FrameEncoder::threadMain() () at 
/lib/x86_64-linux-gnu/libx265.so.179
 () at /lib/x86_64-linux-gnu/libx265.so.179

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: x265 3.2.1-1build1
ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
Uname: Linux 5.4.0-58-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Sun Jan  3 18:49:17 2021
InstallationDate: Installed on 2020-12-26 (8 days ago)
InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: x265
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909949

Title:
  SIGSEGV in x265_10bit::RateControl::rateEstimateQscale()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1765933] Re: Allow building livefses against a view of the archive at a fixed point in time

[Bryant Keith Upton]

** Changed in: livecd-rootfs (Ubuntu)
 Assignee: (unassigned) => Bryant Keith Upton (keithupton7496)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765933

Title:
  Allow building livefses against a view of the archive at a fixed point
  in time

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1905848] [NEW] Installer crashed during install

[Keith Clark]

Public bug reported:

During Install of Ubuntu, the installer crashed before complete.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckMismatches: ./boot/grub/efi.img ./casper/filesystem.squashfs
CasperMD5CheckResult: skip
CasperVersion: 1.445
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 27 02:44:31 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash nomodeset ---
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 LANGUAGE=en_CA.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905848

Title:
  Installer crashed during install

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1905140] [NEW] error installing nvidia 455 driver: nvidia-kernel-source-455 455.38-0ubuntu0.20.10.1: nvidia kernel module failed to build

[Keith Cecere]

Public bug reported:

Failed to upgrade to latest nvidia driver 455 from the Ubuntu Install
Additional Drivers dialog.

ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: nvidia-kernel-source-455 455.38-0ubuntu0.20.10.1
ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
Uname: Linux 5.8.0-29-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50.1
Architecture: amd64
CasperMD5CheckResult: skip
DKMSKernelVersion: 5.8.0-29-generic
Date: Sat Nov 21 12:56:14 2020
Dependencies:
 
InstallationDate: Installed on 2018-08-18 (825 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageVersion: 455.38-0ubuntu0.20.10.1
Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.20.5ubuntu2
 apt  2.1.10
SourcePackage: nvidia-graphics-drivers-455
Title: nvidia-kernel-source-455 455.38-0ubuntu0.20.10.1: nvidia kernel module 
failed to build
UpgradeStatus: Upgraded to groovy on 2020-10-23 (29 days ago)

** Affects: nvidia-graphics-drivers-455 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package groovy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905140

Title:
  error installing nvidia 455 driver: nvidia-kernel-source-455
  455.38-0ubuntu0.20.10.1: nvidia kernel module failed to build

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896608] Re: [regression-in-stable] grub-multi-install fails with exit 1 when question grub-efi/install_devices_empty is skipped

[Keith]

The fix on the proposed channel is working for me too.  Thanks guys!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896608

Title:
  [regression-in-stable] grub-multi-install fails with exit 1 when
  question grub-efi/install_devices_empty is skipped

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1899691] [NEW] upgrade to 20.04.1 fails

[Keith Driscoll]

Public bug reported:

Upgrade fails with An unresolvable problem occurred while calculating
the upgrade.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.38
ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.18
Architecture: amd64
CrashDB: ubuntu
Date: Tue Oct 13 15:41:05 2020
InstallationDate: Installed on 2015-06-04 (1958 days ago)
InstallationMedia: Ubuntu-Server 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to bionic on 2020-10-13 (0 days ago)

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


** Tags: amd64 apport-bug bionic dist-upgrade

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899691

Title:
  upgrade to 20.04.1 fails

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1898493] [NEW] /dev/dri/card0 not closed when plasmashell forks

[Keith Owens]

Public bug reported:

plasmashell forks xterm. xterm inherits /dev/dri/card0 open on fd 15.
Working as designed? Or forgot to close it/mark it as CLOEXEC?

# lsof -p 2624 | grep /dev/dri
plasmashe 2624 kaos   12u  CHR  226,0  0t0347 
/dev/dri/card0
plasmashe 2624 kaos   13u  CHR  226,0  0t0347 
/dev/dri/card0
plasmashe 2624 kaos   14u  CHR  226,0  0t0347 
/dev/dri/card0
plasmashe 2624 kaos   15u  CHR  226,0  0t0347 
/dev/dri/card0

xterm child on pid 3659

# lsof -p 3659 | grep /dev/dri
xterm   3659 kaos   15u   CHR  226,0  0t0  347 
/dev/dri/card0

strace 2624 shows no close for fd 12, 13, 14 but they are not inherited
by 3659. So they are probably marked CLOEXEC. But fd 15 is left open and
is inherited by all children of plasmashell.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: plasma-workspace 4:5.18.5-0ubuntu0.1
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Mon Oct  5 12:24:05 2020
InstallationDate: Installed on 2017-07-12 (1180 days ago)
InstallationMedia: Kubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215)
SourcePackage: plasma-workspace
UpgradeStatus: Upgraded to focal on 2020-06-21 (105 days ago)

** Affects: plasma-workspace (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898493

Title:
  /dev/dri/card0 not closed when plasmashell forks

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1875148] Re: USB ports on Raspberry Pi are deactivated when connecting a Drobo unit

[Keith Smith]

I have managed to work around this bug by doing the following:

1) Using James Chambers unofficial 64-bit build
Moving to 64 bit gets things moving, but after a several minutes the host 
controller would eventually hangup on me.  I can't help but wonder if some 
32bit ints are being blown somewhere because of the big reported sizes

2) Add the quirk 'usb-storage.quirks=[yourdrivesVID]:[yourdrivesPID]:u' to 
cmdline.txt
This limits DMA scatter-gather operations (new in Pi4) and seemes to help, but 
I've not been able to conclusively establish how

3) Connect the Drobo to the USB2 port rather than USB3
This (after the previous two steps) the finally kept the device mounted and 
working - kinda...

4) On another computer (I used a Mac with extFS added) repartition the drive to 
have a 16Tb partition (rather than the normal ~70Tb)
I found that if the OS tried to address data above some big value (never did 
manage to tie it down), perhaps while partitioning(!), formatting or fsck-ing, 
it would hang-up.  In my case I happen to have 15Tb currently loaded in my 
Drobo and so I tried a 16Tb partition, and that worked.

5) In cmdline.txt change 'fsck.mode=auto' to 'fsck.mode=force'
I have found that the drive is always perceived as dirty and potentially 
corrupt (even though it isn't) on mount, so by forcing a fsck I ensure that the 
drive will be usable on boot (although this does mean that a reboot will make 
some functions unavailable for several hours.

6) Make sure that the mount options include 'nofail' and a good device-timeout, 
I use 'x-systemd.device-timeout=15'
The nofail ensures boot can proceed even though the fsck will take hours to 
complete (I have set the services that need the drive to wait for the mount), 
and the timeout caters for a corner case.
If it helps, my mount options in fstab are: 
'rw,suid,dev,exec,auto,nouser,async,relatime,nofail,x-systemd.device-timeout=15'


And there it is.  A big Drobo workaround, stuck on USB2 speeds,
constrained to fraction of potential capacity, and that takes several
hours to become usable...  but I've got a NAS that works.


Obviously, this is far from ideal. I would love this to get fixed.  Hopefully 
this has given some hints as to where to look, and helped others in the 
meantime.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875148

Title:
  USB ports on Raspberry Pi are deactivated when connecting a Drobo unit

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887865] [NEW] Lubuntu 18.04 DVD Install to 250 GHDD SATA Cale

[Keith Miller]

Public bug reported:

Lubuntu 18.04 DVD 32 bit version-Install to 500 G SSD internal in a
Lenovo G530 laptop  Will not boot from SSD. The cursor at top left
position flashes and the computer will not boot from SSD: it just sits
flashing.   Have I somehow botched the installation to the SSD?I did all
the BIOS nonsense to have the computer boot from the 500 G SSD.  Will
the laptop boot from the DVD? Yes. Change BIOS to boot from the 500G SSD
and it fails to boot.

THIS BUG appeared when I tried to see if the installation to the old HDD
230 G connected via a USB to SATA connector ( the old HDD is now
external to the laptop.and on this cable rather than inside the laptop).
This bug  appeared  during the installation. ( I assumed that the long
list of the details is attached?) Thank You.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.14
ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
Uname: Linux 5.3.0-28-generic i686
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: i386
CasperVersion: 1.394.3
Date: Thu Jul 16 14:49:11 2020
InstallCmdLine: file=/cdrom/preseed/lubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd quiet splash ---
LiveMediaBuild: Lubuntu 18.04.4 LTS "Bionic Beaver" - Release i386 (20200203)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug bionic i386 lubuntu ubiquity-18.04.14.14

** Description changed:

-  Lubuntu 18.04 DVD 32 bit version-Install to 500 G SSD internal in a
- lenovo G530 laptop  Will not boot from SSD. The cursor at top left
+ Lubuntu 18.04 DVD 32 bit version-Install to 500 G SSD internal in a
+ Lenovo G530 laptop  Will not boot from SSD. The cursor at top left
  position flashes and the computer will not boot from SSD: it just sits
  flashing.   Have I somehow botched the installation to the SSD?I did all
- the BIOS nonsense to have the computer boot from the 500 G SSD. top
- left-hand position and flashes. Will the laptop boot from the DVD? Yes.
- Change BIOS to boot from the 500G SSD and it fails to boot.
+ the BIOS nonsense to have the computer boot from the 500 G SSD.  Will
+ the laptop boot from the DVD? Yes. Change BIOS to boot from the 500G SSD
+ and it fails to boot.
  
  THIS BUG appeared when I tried to see if the installation to the old HDD
  230 G connected via a USB to SATA connector ( the old HDD is now
  external to the laptop.and on this cable rather than inside the laptop).
- This bug to appeared  during the installation. ( I assumed that the long
+ This bug  appeared  during the installation. ( I assumed that the long
  list of the details is attached?) Thank You.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.14.14
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-28-generic i686
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: i386
  CasperVersion: 1.394.3
  Date: Thu Jul 16 14:49:11 2020
  InstallCmdLine: file=/cdrom/preseed/lubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd quiet splash ---
  LiveMediaBuild: Lubuntu 18.04.4 LTS "Bionic Beaver" - Release i386 (20200203)
  ProcEnviron:
-  LANGUAGE=en_US.UTF-8
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  LC_NUMERIC=C.UTF-8
+  LANGUAGE=en_US.UTF-8
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  LC_NUMERIC=C.UTF-8
  SourcePackage: grub-installer
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887865

Title:
  Lubuntu 18.04 DVD Install to 250 GHDD SATA Cale

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1885563] Re: Front panel audio doesn't work on Gigabyte X570 Aorus Master

[Paul Keith]

** Attachment added: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1885563/+attachment/5388310/+files/version.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885563

Title:
  Front panel audio doesn't work on Gigabyte X570 Aorus Master

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1885563] Re: Front panel audio doesn't work on Gigabyte X570 Aorus Master

[Paul Keith]

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1885563/+attachment/5388308/+files/lspci-vnvn.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885563

Title:
  Front panel audio doesn't work on Gigabyte X570 Aorus Master

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1885563] Re: Front panel audio doesn't work on Gigabyte X570 Aorus Master

[Paul Keith]

** Attachment added: "uname-a.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1885563/+attachment/5388309/+files/uname-a.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885563

Title:
  Front panel audio doesn't work on Gigabyte X570 Aorus Master

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1885563] Re: Front panel audio doesn't work on Gigabyte X570 Aorus Master

[Paul Keith]

1. Release information

foo@foo-X570-AORUS-MASTER:~$ lsb_release -rd
Description:Ubuntu 20.04 LTS
Release:20.04

2. Version of package

foo@foo-X570-AORUS-MASTER:~$ uname -a
Linux foo-X570-AORUS-MASTER 5.4.0-39-generic #43-Ubuntu SMP Fri Jun 19 10:28:31 
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

3. What I expected to happen:

Output devices plugged into front panel audio ports have audio playing
when selected as output device.

4. What happened instead:

No audio comes through output devices described in #3.

** Attachment added: "dmesg.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1885563/+attachment/5388307/+files/dmesg.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885563

Title:
  Front panel audio doesn't work on Gigabyte X570 Aorus Master

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1885565] [NEW] Gstreamer doesn't support VAAPI on amdgpu

[Paul Keith]

Public bug reported:

The version of gstreamer forked for Ubuntu 20.04 has the commit to
remove Mesa from the whitelist but doesn't have the commit merged later
to readd it to the whitelist.

Removal: https://github.com/GStreamer/gstreamer-
vaapi/commit/a90daabb84f983d2fa05ff3159f7ad59aa648b55

Reintroduction: https://github.com/GStreamer/gstreamer-
vaapi/commit/7a186975cc209f1f4d75e902144563e76ce3a14c

I have tested that readding it to the whitelist works:

Before: https://gist.github.com/99daafcff32cf650b5fe11315c01a27d

After: https://gist.github.com/e2a31779f05b706c9347bcf7277def3d

To change the whitelist, I did:
sudo sed -i -e 's/Intel i965 driver/Mesa Gallium driv/g' 
/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so 

That changes the whitelist entry for the i965 driver to the Mesa driver
for amdgpu. Picking the reintroduction patch linked above and spinning a
new version should be enough.

Release:
javelinanddart@jav-bq213cl:~$ lsb_release -rd
Description:Ubuntu 20.04 LTS
Release:20.04

Version:
javelinanddart@jav-bq213cl:~$ sudo apt-cache policy gstreamer1.0-vaapi
gstreamer1.0-vaapi:
  Installed: 1.16.2-2
  Candidate: 1.16.2-2
  Version table:
 *** 1.16.2-2 500
500 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
100 /var/lib/dpkg/status

What I expected to happen: See After gist

What happened instead: See Before gist

** Affects: gstreamer-vaapi (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885565

Title:
  Gstreamer doesn't support VAAPI on amdgpu

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1885563] Re: Front panel audio doesn't work on Gigabyte X570 Aorus Master

[Paul Keith]

I should mention - this affects Ubuntu 20.04 (and previous versions).
The patch was introduced in Linux 5.6-rc1, as far as I can tell. I can
pull uname and other things after work, but I wanted to at least get the
bug report in. I don't think patching versions below 20.04 is really
necessary, as the nature of this hardware is such that older kernels
don't have support for other parts of the board that users would like to
use.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885563

Title:
  Front panel audio doesn't work on Gigabyte X570 Aorus Master

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1885563] [NEW] Front panel audio doesn't work on Gigabyte X570 Aorus Master

[Paul Keith]

Public bug reported:

The DAC is weird on this board and needs a quirk applied for audio to be routed 
correctly. Please see https://lkml.org/lkml/2020/2/23/22 and linked bugzilla 
for more details. This also affects some other Gigabyte X570 boards, but I 
couldn't tell you exactly which. A quick search in torvalds/linux yields 
https://github.com/torvalds/linux/commit/0d45e86d2267d5bdf7bbb631499788da1c27ceb2
 and 
https://github.com/torvalds/linux/commit/d9e8fe0cffbfdd18de96fa68ee2a8b667a0b046e.

Expected behavior: Plugging headphones into front panel audio ports and
selecting those as the output device results in working audio.

Actual behavior: Device is detected, but no sound is actually played.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885563

Title:
  Front panel audio doesn't work on Gigabyte X570 Aorus Master

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1876322] Re: kazam on Focal: No audio recorded

[Keith]

can someone explain the simple solution

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876322

Title:
  kazam on Focal: No audio recorded

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874436] [NEW] I have no sound after upgrading to Eoan. I have tried reinstalling drivers. I had a wifi problem too which i solved. But the sound i cannot figure out.

[Keith A Prinkey]

Public bug reported:

After upgrading to Eoan, my sound stopped working. I have done
everything i know to do and it still doesnt work. Not sure what else i
can do besides revert to bionic.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874436

Title:
  I have no sound after upgrading to Eoan. I have tried reinstalling
  drivers. I had a wifi problem too which i solved. But the sound i
  cannot figure out.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1873238] [NEW] Deja-dup icon is missing only runs from terminal

[Keith Drummond]

Public bug reported:

This is occuring just on Ubuntu 20.04 Beta for me.

The Deja-Dup icon has gone missing from the application's menu.
Searching for it does not yield any results via the gnome shell search.

It will run if I open a terminal and type "deja-dup"

While running from the terminal instead of the description in the top
bar/panel being the expected "Backups" the description now reads
"Org.gnome.DejaDup"

All other functionality seems to work as normal when run from terminal.

I have tried uninstalling and reinstalling via synaptic and the Ubuntu
Software but the issue is persisting.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: deja-dup 40.6-1ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 16 10:59:36 2020
InstallationDate: Installed on 2019-10-20 (178 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: deja-dup
UpgradeStatus: Upgraded to focal on 2020-04-06 (9 days ago)

** Affects: deja-dup (Ubuntu)
 Importance: Undecided
 Status: New


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873238

Title:
  Deja-dup icon is missing only runs from terminal

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871804] Re: WiFi adapter doesn't work with linux kernel version 5.3.0-46

[Keith Barber]

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871804/+attachment/5353454/+files/lspci-vnvn.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871804

Title:
  WiFi adapter doesn't work with linux kernel version 5.3.0-46

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871804] Re: WiFi adapter doesn't work with linux kernel version 5.3.0-46

[Keith Barber]

** Attachment added: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871804/+attachment/5353453/+files/version.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871804

Title:
  WiFi adapter doesn't work with linux kernel version 5.3.0-46

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871804] Re: WiFi adapter doesn't work with linux kernel version 5.3.0-46

[Keith Barber]

I am also Linux Mint 19 with the same symptoms. WiFi works for a few
hours and then no connection until reboot. I found the following tell-
tale (repeated multiple times) in kern.log:

Apr 13 15:15:50 ideapad kernel: [22708.516956] ath10k_pci :02:00.0: failed 
to wake target for write32 of 0x07f3 at 0x0003543c: -110
Apr 13 15:15:51 ideapad kernel: [22709.541368] ath10k_pci :02:00.0: failed 
to wake target for write32 of 0x07f5 at 0x0003543c: -110
Apr 13 15:15:52 ideapad kernel: [22710.565103] ath10k_pci :02:00.0: failed 
to wake target for write32 of 0x07f7 at 0x0003543c: -110

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871804

Title:
  WiFi adapter doesn't work with linux kernel version 5.3.0-46

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1776044] Re: nvidia-340 crashes display in 18.04 Bionic when no Nvidia GPU present

[Keith Elliston]

I have a similar issue.  Installed Ubuntu 18.04 on a Ryzen 7 2700x with
an old Geforce 8600 GTS.  Using the built-in drivers, the video card
stalls (took me a long time to figure out it was the video card, after
going through all the Ryzen issues).  I installed the nvidia-340 as
recommended, and the system hangs on boot before the graphic login.  I
removed the nvidia drivers, and reinstall the default, and it works
again, but stalls.  I know this is the video stalling, as I can ssh into
the machine, and all is working fine on the computer, just the video on
the hardware is stalling.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776044

Title:
  nvidia-340 crashes display in 18.04 Bionic when no Nvidia GPU present

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1862261] [NEW] cannot upgrade from 19.04 to 19.10

[Keith Clark]

Public bug reported:

N/A

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubuntu-release-upgrader-core 1:19.04.16.9
ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
Uname: Linux 5.0.0-38-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.3
Architecture: amd64
CrashDB: ubuntu
Date: Thu Feb  6 17:06:35 2020
InstallationDate: Installed on 2018-06-24 (592 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to disco on 2020-02-06 (0 days ago)
VarLogDistupgradeAptlog:
 Log time: 2020-02-06 17:04:50.846319
 Log time: 2020-02-06 17:05:13.138451
 Log time: 2020-02-06 17:06:15.854561
 Log time: 2020-02-06 17:06:40.151857
VarLogDistupgradeTermlog:

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


** Tags: amd64 apport-bug disco dist-upgrade

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862261

Title:
  cannot upgrade from 19.04 to 19.10

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1859075] [NEW] internal compiler error: in replace_placeholders_r, at cp/tree.c:2804

[Keith Bennett]

Public bug reported:

$ lsb_release -rd
Description:Ubuntu 16.04.6 LTS
Release:16.04
$ apt-cache policy gcc-7
gcc-7:
  Installed: 7.4.0-1ubuntu1~16.04~ppa1
  Candidate: 7.4.0-1ubuntu1~16.04~ppa1
  Version table:
 *** 7.4.0-1ubuntu1~16.04~ppa1 500
500 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial/main 
amd64 Packages
100 /var/lib/dpkg/status
$ g++ --version
g++ (Ubuntu 7.4.0-1ubuntu1~16.04~ppa1) 7.4.0
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

$ g++ -std=c++17 bench.preprocessed.cpp 
bench.cpp: In function ‘std::vector build_matrix()’:
bench.cpp:58:18: internal compiler error: in replace_placeholders_r, at 
cp/tree.c:2804
   std::generate_n(std::back_inserter(matrix), count, generator{});
   ~~~^~~~
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.

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

** Attachment added: "g++ -std=c++17 bench.preprocessed.cpp"
   
https://bugs.launchpad.net/bugs/1859075/+attachment/5318924/+files/bench.preprocessed.cpp

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859075

Title:
  internal compiler error: in replace_placeholders_r, at cp/tree.c:2804

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 96863] Re: [apport] senddigests crashed with IOError in __write()

[Keith Brian Tomo]

** Changed in: mailman (Ubuntu)
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/96863

Title:
  [apport] senddigests crashed with IOError in __write()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1838866] Re: Mailman 2.1: hardcoded site-packages dir prefix doesn't work on some 64 bit filesystem layouts

[Keith Brian Tomo]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838866

Title:
  Mailman 2.1: hardcoded site-packages dir prefix doesn't work on some
  64 bit filesystem layouts

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1845875] [NEW] Installer crashed while installing

[Keith]

Public bug reported:

installer crashed while installing on ssd

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.12
ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 29 15:10:42 2019
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic ubiquity-18.04.14.12 ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845875

Title:
  Installer crashed while installing

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1842133] Re: findutils shows wrong version number

[Keith Thompson]

I found the upstream fix for this issue.

git://git.sv.gnu.org/findutils :

commit 1cc207f6ebddd3609c995f17756f995cf8847c32
Author: Bernhard Voelker 
Date:   2017-10-30 21:54:19 +0100

maint: make inter-release --version output more useful

Now, each snapshot has a version "number" like 4.6-131-219-gda920ee,
which indicates that it is built using the 131st change set
(in _some_ repository) following the "v4.6" tag, and that da920ee
is a prefix of the commit SHA1.

Prior to this commit, "find --version" reported "4.7.0-git".
As of that commit, it reports "4.6.0.157-1cc2"
The very latest as of today reports "4.7.0.12-6975a".

*If* this were to be addressed for Ubuntu 18.04, it could be done
by backporting this patch from upstream.  I express no opinion on
whether that would be worth doing.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842133

Title:
  findutils shows wrong version number

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1842133] Re: findutils shows wrong version number

[Keith Thompson]

> First off: Ubuntu/Debian do not ship "patched version of the GNU findutils
> package [...] based on release 4.6.0".

OK.  When I do "apt-get source findutils" I get a 
"findutils_4.6.0+git+20170828-2.debian.tar.xz"
file that does include two patches, but neither of them seems to be relevant to 
this issue.

The "findutils_4.6.0+git+20170828.orig.tar.xz" file I get from the same apt-get 
command
unpacks to a "findutils-4.7.0-gitfindutils-4.7.0-git" directory.

I just built findutils revision febde26dd0e66dda5d4060fa29b85443ddc6a865 from 
source, and
the resulting "find" command does print "find (GNU findutils) 4.7.0-git" when 
invoked with
"--version".  So it seems to be an upstream issue.  "info findutils", which 
loads
/usr/share/info/find.info.gz, also reports version 4.7.0-git.

Whatever the cause, I suggest that "4.7.0-git" is misleading, since release 
4.7.0 did not
yet exist.

I could submit a bug report against the upstream findutils component.
Should I do so?

(To be clear, I'm not saying this is a major, or even necessarily
significant, problem.)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842133

Title:
  findutils shows wrong version number

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1842133] [NEW] findutils shows wrong version number

[Keith Thompson]

Public bug reported:

This problem occurs on Ubuntu 18.04.3 LTS (bionic).
It does not occur on Ubuntu 19.04 (disco)

The "find" and "xargs" command are provided by a patched version of the
GNU findutils package. The current version is based on release 4.6.0, but
the "--version" option shows a version number of "4.7.0-git".

As you can see, the "/usr/bin/find" executable is dated Nov 5 2017.
findutils release 4.7.0 was released just yesterday, Aug 29 2017.

Ubuntu 19.04 has findutils 4.6.0+git+20190209-2, and "find --version"
shows "find (GNU findutils) 4.6.0.225-235f".

Expected: "findutils --version" shows a version number based on 4.6.0
Actual:   "findutils --version" shows a version number based on 4.7.0,
  which had not yet been released

Demonstration:

$ lsb_release -rd
Description:Ubuntu 18.04.3 LTS  
Release:18.04
$ apt-cache policy findutils
findutils:
  Installed: 4.6.0+git+20170828-2
  Candidate: 4.6.0+git+20170828-2
  Version table:
 *** 4.6.0+git+20170828-2 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
$ ls -l /usr/bin/find
-rwxr-xr-x 1 root root 238080 Nov  5  2017 /usr/bin/find
$ /usr/bin/find --version
find (GNU findutils) 4.7.0-git
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later .
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Eric B. Decker, James Youngman, and Kevin Dalley.
Features enabled: D_TYPE O_NOFOLLOW(enabled) LEAF_OPTIMISATION FTS(FTS_CWDFD) 
CBO(level=2)
$

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842133

Title:
  findutils shows wrong version number

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1739505] Re: segfault on simple script that involves eval

[Keith Thompson]

I've submitted a report for this same bug on Debian 10.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933057

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739505

Title:
  segfault on simple script that involves eval

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1739505] Re: segfault on simple script that involves eval

[Keith Thompson]

I've found the cause of the problem. It can be fixed by grabbing the
latest csh sources from OpenBSD and removing one of the Debian patches.

I've examined the csh sources obtained by running "apt-get source csh",
and the upstream OpenBSD csh sources from https://github.com/openbsd/src .

In the OpenBSD version from which the Debian/Ubuntu version was copied,
lex.c contains the following lines:

if ((evalp = *evalvec) != '\0') {
evalvec++;
goto top;
}

evalp is a pointer, so the comparison should be to NULL, not '\0'.

debian/patches/pointer_deref_comparison.patch changes the first line to:

if (*(evalp = *evalvec) != '\0') {

This fixes the compiler warning for comparing a pointer to '\0', but
it causes a segmentation fault if  is a null pointer -- which
happens whenever the "eval" command is invoked.  It's line 1330 of lex.c
in the patched csh 20110502-3 sources on Ubuntu 18.04.2 LTS package.

A later OpenBSD version of the csh sources changes that line to:

if ((evalp = *evalvec) != NULL) {

The change was made in commit bdb0dae4088 in
https://github.com/openbsd/src on 2018-09-19

The same problem occurs with csh 20110502-4 on Debian 10.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739505

Title:
  segfault on simple script that involves eval

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1574007] Re: synaptics refuses to run after upgrade to Xenial from Wily

[Keith]

I believe this is the same bug I have encountered. A workaround is described at 
https://superuser.com/a/575754/641073
(fix the DefaultDistro setting in /root/.synaptic/synaptic.conf)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574007

Title:
  synaptics refuses to run after upgrade to Xenial from Wily

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1739505] Re: segfault on simple script that involves eval

[Keith Thompson]

I've run into this myself in Ubuntu 18.04 and 18.10.

I have not found any "eval" command that does not cause bsd-csh to die
with a segmentation fault.  For example:

$ bsd-csh -f
% eval date
Segmentation fault (core dumped)

I downloaded the source tarball for csh_20110502, compiled it with "gcc
-g", and reproduced the problem under gdb:

$ gdb ./csh 
GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./csh...done.
(gdb) run -f
Starting program: /home/kst/src/csh/csh-20110502/csh -f
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
% eval date

Program received signal SIGSEGV, Segmentation fault.
0x5556e369 in readc (wanteof=0) at lex.c:1330
1330if (*(evalp = *evalvec) != '\0') {
(gdb) where
#0  0x5556e369 in readc (wanteof=0) at lex.c:1330
#1  0x5556b66f in getC1 (flag=3) at lex.c:384
#2  0x5556b440 in word () at lex.c:329
#3  0x5556ac94 in lex (hp=0x55783450 ) at lex.c:164
#4  0xa9f0 in process (catch=0) at csh.c:1046
#5  0x55567f44 in doeval (v=0x5578af60, t=0x5578ae80) at 
func.c:1396
#6  0x55564daf in func (t=0x5578ae80, bp=0x55781018 
) at func.c:113
#7  0x5557589b in execute (t=0x5578ae80, wanttty=6242, 
pipein=0x0, pipeout=0x0) at sem.c:370
#8  0x55575b78 in execute (t=0x5578ae40, wanttty=6242, 
pipein=0x0, pipeout=0x0) at sem.c:418
#9  0xab48 in process (catch=1) at csh.c:1088
#10 0x9375 in main (argc=0, argv=0x7fffe638) at csh.c:553
(gdb) quit
A debugging session is active.

Inferior 1 [process 6242] will be killed.

Quit anyway? (y or n) y
$ 

I'll note that this problem has not inconvenienced me, and I expect that
most csh users would be using tcsh, which is not affected by this bug.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739505

Title:
  segfault on simple script that involves eval

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822108] [NEW] package linux-image-4.4.0-143-generic 4.4.0-143.169 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

[Keith Rogers]

Public bug reported:

Error occurred when switching drivers for NVIDIA Corporation:
G92[GeForce 9800 GT] to NVIDIA binary driver - version 340.107 from
nvidia-340(proprietary, tested)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-143-generic 4.4.0-143.169
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Thu Mar 28 09:47:57 2019
DuplicateSignature:
 package:linux-image-4.4.0-143-generic:4.4.0-143.169
 Setting up linux-image-4.4.0-143-generic (4.4.0-143.169) ...
 /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: 
/var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 
linux-update-symlinks: not found
 dpkg: error processing package linux-image-4.4.0-143-generic (--configure):
  subprocess installed post-installation script returned error exit status 127
ErrorMessage: subprocess installed post-installation script returned error exit 
status 127
InstallationDate: Installed on 2017-05-06 (691 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: linux-signed
Title: package linux-image-4.4.0-143-generic 4.4.0-143.169 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 127
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822108

Title:
  package linux-image-4.4.0-143-generic 4.4.0-143.169 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 127

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 159356] Re: When DMA is disabled system freeze on high memory usage

[Keith Hutton]

I am running on a ~9 year laptop with 1866MiB ram and 3933MiB swap.
Lubuntu installed. Linux ub2 4.18.0-16-generic #17-Ubuntu SMP Fri Feb 8 
00:06:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
So my problem is for example, having two different browsers open with too many 
open browser tabs (4-6) on each  caused a high memory load with system freeze. 
I noticed that swap was not being used in a why that I think it should be, that 
is a general slow down as more and more swap was used. Instead I got instant 
freeze for 30 minutes or more. So I found a program called munch.c and played 
around with it. I also created different versions of munch.c so memory usage 
was different. I was able to change system vm settings (in /proc/sys/vm) so the 
freeze stopped and swap started to be used correctly so that real memory and 
virtual memory became balanced. I define "balanced" to mean as more swap is 
used the system gradually becomes slower without freezing. In fact in the 
beginning the Linux-memory-swap system was very poor (default settings) and a 
Microsoft Windows 7 machine with same memory far far better at memory-swap 
management. My conclusion (for now) is that by altering default settings the 
Linux system became much better because the freeze bug was eliminated. I turned 
on the SysRq feature to enable the (f) option.
I found I could make the SysRq (f) work straight away. Also found the automatic 
OOM now kicked in as well, if I waited a bit.
I will add more details to this at a later time.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/159356

Title:
  When DMA is disabled system freeze on high memory usage

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 159356] Re: When DMA is disabled system freeze on high memory usage

[Keith Hutton]

Further, to my comment above, if I enable swap, the program continues to
run using up all the swap, and then terminates without a system freeze.
The program pauses for about 1/3 second intervals as swap gets used. The
higher vm.min_free_kbytes the pauses are less. I have a third memory
eater and I managed to get up to 66 Gb virtual memory allocated. My old
laptop (9 years) has only 2Gb Ram.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/159356

Title:
  When DMA is disabled system freeze on high memory usage

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 159356] Re: When DMA is disabled system freeze on high memory usage

[Keith Hutton]

Try increasing vm.min_free_kbytes

I have two memory eater programs, one uses 1Mb steps and the other 1Kb steps. 
When I run the 1Mb, the oom killer cuts in. When I run the 1Kb program the oom 
does not.
If I raise the vm.min_free_kbytes = 17-25 both programs are terminated, 
no system freeze.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/159356

Title:
  When DMA is disabled system freeze on high memory usage

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04

[Keith]

Sounds like broken record here, oh no broken shutdown here actually.
Bodhi Linux 4.2 on old hardare Aspire 5000 laptop, was wooring fine till a day 
or two ago.
Hangs at shutting down several things says all stopped down to hardware clock 
something or another.
can hit Esc a couple times and it progresses but still just stops.
Will boot fine with a Power Button Hold down and restart.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594023

Title:
  Poweroff or reboot hangs. Laptop won't shutdown. 16.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 938751] Re: jpeg images are washed out or colors are skewed

[Keith Briggs]

This renders eog unusable.   I have images just a purple mess
(screenshot).   Other similar image files display correctly.   The
affected files display correctly in all other image viewers.

** Attachment added: "Screenshot from 2019-02-09 20-30-58.png"
   
https://bugs.launchpad.net/ubuntu/+source/eog/+bug/938751/+attachment/5237277/+files/Screenshot%20from%202019-02-09%2020-30-58.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/938751

Title:
  jpeg images are washed out or colors are skewed

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1810695] [NEW] g++: M_PI is visible in conforming mode

[Keith Thompson]

Public bug reported:

The macro M_PI, which expands to a constant approximating the value
of pi, is defined by POSIX, but not by ISO C or ISO C++.  It is
not a reserved identifier, so it should be available for use as a
user-defined identifier.

The problem: Including  causes M_PI to be defined, even when
the C++ compiler is invoked in what should be a conforming mode.

EXPECTED: Program compiles without error and prints "3".
OBSERVED: Program is rejected at compile time.

(The program is rejected when g++ or clang++ is invoked without
options.  That's not a bug.)

Using  rather than  doesn't change the symptom.

A similar program in C does not exhibit the problem.

I *think* the problem is in the "math.h" header, which should arrange
for M_PI and similar macros not to be defined in conforming mode.
It's also possible that a fix might involve updates to g++ and/or
clang++.  I haven't fully investigated the twisty maze of macro
definitions and nested #includes in math.h.

(I acknowledge that writing your own definition of M_PI is not a
good idea, and that the definition in this program is particularly
poor style.)

Output illustrating the problem follows:

$ lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04

$ uname -a
Linux bomb20 4.15.0-42-generic #45-Ubuntu SMP Thu Nov 15 19:32:57 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

$ dpkg -l g++ clang libc6-dev:amd64 | grep '^ii'
ii  clang   1:6.0-41~exp5~ubuntu1 amd64C, C++ and Objective-C 
compiler (LLVM based)
ii  g++ 4:7.3.0-3ubuntu2.1amd64GNU C++ compiler
ii  libc6-dev:amd64 2.27-3ubuntu1 amd64GNU C Library: 
Development Libraries and Header Files

$ g++ --version | head -1
g++ (Ubuntu 7.3.0-27ubuntu1~18.04) 7.3.0

$ clang++ --version
clang version 6.0.0-1ubuntu2 (tags/RELEASE_600/final)
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin

$ cat M_PI_bug.cpp 
#include 
#include 
int main() {
const int M_PI = 22/7;
std::cout << M_PI << '\n';
}

// This is not reasonable code.
// The issue is that a conforming C++ compiler must accept it.

// Expected output: 3

$ g++ -std=c++17 -pedantic-errors -c M_PI_bug.cpp 
In file included from /usr/include/c++/7/cmath:45:0,
 from M_PI_bug.cpp:2:
M_PI_bug.cpp: In function ‘int main()’:
M_PI_bug.cpp:4:15: error: expected unqualified-id before numeric constant
 const int M_PI = 22/7;
   ^

$ clang++ -std=c++17 -pedantic-errors -c M_PI_bug.cpp 
M_PI_bug.cpp:4:15: error: expected unqualified-id
const int M_PI = 22/7;
  ^
/usr/include/math.h:777:16: note: expanded from macro 'M_PI'
# define M_PI   3.14159265358979323846  /* pi */
^
1 error generated.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810695

Title:
  g++: M_PI is visible in conforming mode

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1809602] [NEW] Get a dialog saying there was a system problem

[Keith Dennison]

Public bug reported:

Usually happens within a minute of logging in. It may appear again but I
don't know what it is that may provoke the issue.

ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: libwayland-dev 1.16.0-1ubuntu1.1
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
 GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CompositorRunning: None
Date: Thu Oct 18 19:57:09 2018
DistUpgraded: 2018-10-18 19:48:35,002 DEBUG inhibit gnome-session idle
DistroCodename: cosmic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.87, 4.18.0-11-generic, x86_64: installed
 nvidia, 390.87, 4.18.0-13-generic, x86_64: installed
ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also in package 
libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1
GraphicsCard:
 Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:07be]
   Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be]
InstallationDate: Installed on 2018-04-26 (240 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Dell Inc. XPS 15 9560
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=8d59d9c4-3cd6-4604-b292-cba1fe59ac7c ro quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10
PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu5
 apt  1.7.0
SourcePackage: wayland
Title: package libwayland-dev 1.16.0-1ubuntu1.1 failed to install/upgrade: 
trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which 
is also in package libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1
UpgradeStatus: Upgraded to cosmic on 2018-10-18 (65 days ago)
dmi.bios.date: 07/05/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.10.1
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.1:bd07/05/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.product.sku: 07BE
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


** Tags: amd64 apport-package cosmic ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809602

Title:
  Get a dialog saying there was a system problem

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1808003] Re: ubuntu-bug

[Keith Bennett]

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

Hi @crichton:

There's a few things right and several things wrong with your statement.

First, you're correct that I've installed Cinnamon. I seem to have
forgotten that it's an unofficial package. That's rather unfortunate
because Cinnamon's user experience is generally way better than Unity's
garbage.

Second, you're wrong about 13.10 and 14.04. I have 16.04.

Third, the problem I first encountered during the upgrade process is
that `update-manager -c` reported that it could not calculate the
upgrade. While that makes sense since Cinnamon is third party, I very
much do not appreciate that the update-manager provided literally _zero
helpful information_ to move forward. It did not tell me what offending
packages I needed to remove.

I went to report that problem through `ubuntu-bug` as indicated (see
attached screenshot) and that program seemed to upload the bug report to
somewhere (where???) and then open a browser tab to here. It did *not*
create a bug report. It did *not* tell me why it did not create a bug
report. It did *not* even tell me that there was an error.

So I went to *manually* create a bug report and then, only then, was
information automatically attached.


This upgrade software is about as useful as Unity is. I'm very disappointed. 
Without an automatic way to move forward (whether keeping Cinnamon or not), I 
suppose I will need to reinstall the OS in order to upgrade. If that is the 
case, I will not continue to use Ubuntu and will migrate to Fedora instead. At 
least Fedora's bug reporting process is sane.


** Attachment added: "Screenshot from 2018-12-11 10-38-26.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1808003/+attachment/5221701/+files/Screenshot%20from%202018-12-11%2010-38-26.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808003

Title:
  ubuntu-bug

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1808003] Re: ubuntu-bug

[Keith Bennett]

And then when I went to manually create a bug report, *then* a bunch of
debug information was added. What the hell kind of garbage UX is this?!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808003

Title:
  ubuntu-bug

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1808003] [NEW] ubuntu-bug

[Keith Bennett]

Public bug reported:

`ubuntu-bug` launches the browser to Launchpad. When in Launchpad, I am
told "Please wait while bug data is processed. This page will refresh
every 10 seconds until processing is complete."

After several reloads, the page says "Extra debug information will be
added to the bug report automatically."

The page does not have any bug information displayed. My account does
not have any associated bugs.

I have no way to track the bug report. I do not see a way to verify that
the bug report was even successfully created.


1: The release of Ubuntu I am using:
```
$ lsb_release -rd
Description:Ubuntu 16.04.5 LTS
Release:16.04
```

2: The version of the package I am using: I have no idea and apparently it's 
not a package.
```
$ apt-cache policy ubuntu-bug
N: Unable to locate package ubuntu-bug
```

3: What I expected to happen:
When I open `ubuntu-bug`, I expect to be presented an interface very similar to 
the Red Hat bug reporter on Fedora which collects login information for the bug 
service, allows me to *fully* inspect the uploadable content prior to being 
uploaded, optionally select some parts to upload or not, allows me to indicate 
whether or not the uploaded information contains sensitive private information 
which I voluntarily opt-in to share, and finally to create and upload the bug 
report without ever opening a browser.

4: What happened instead:
Instead, `ubuntu-bug` appears to collect information, present a stunted view of 
what's being uploaded (stunted in that there's an ellipses indicating there's 
more information but does not provide any obvious way for me to view or inspect 
it), ask to me to either cancel or send, and then send me to a webpage to login.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.26
ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
Uname: Linux 4.4.0-112-generic x86_64
NonfreeKernelModules: sep4_1 socperf2_0 pax wl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CrashDB: ubuntu
Date: Tue Dec 11 11:04:02 2018
InstallationDate: Installed on 2016-12-14 (726 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to xenial on 2018-12-11 (0 days ago)
VarLogDistupgradeTermlog:

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


** Tags: amd64 apport-bug dist-upgrade third-party-packages xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808003

Title:
  ubuntu-bug

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1805702] Re: dnet-common - post inst script update-rc.d has error

[Keith Z-G]

My officemate just ran into this while upgrading to 18.10, and changing

update-rc.d decnet start\ 39\ S\ .\ \ stop\ 11\ 1\ . >/dev/null

to (as I saw on my 18.04 system, where installing dnet-common *did*
work)

update-rc.d decnet start 39 S .  stop 11 1 . >/dev/null

seems to have resolved it; installation then completes as follows:


Preconfiguring packages ...
dnet-common: Skipping configure of DECnet
Selecting previously unselected package dnet-common.
(Reading database ... 1140653 files and directories currently installed.)
Preparing to unpack .../dnet-common_2.65_all.deb ...
Unpacking dnet-common (2.65) ...
Processing triggers for ureadahead (0.100.0-20) ...
Processing triggers for systemd (237-3ubuntu10.9) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Setting up dnet-common (2.65) ...
dnet-common: Skipping configure of DECnet
update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
update-rc.d: warning: start runlevel arguments (S) do not match decnet 
Default-Start values (2 3 4 5)
update-rc.d: warning: stop runlevel arguments (1) do not match decnet 
Default-Stop values (0 1 6)
Processing triggers for systemd (237-3ubuntu10.9) ...
Processing triggers for ureadahead (0.100.0-20) ...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805702

Title:
  dnet-common - post inst script update-rc.d has error

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.

[Keith Myers]

No, I have never changed problem reporting from the default Automatic in
the initial installation.

If I remember correctly, this all started when for some reason when I
had a failed problem report upload notification on the screen and I
acknowledged it.

The very next reboot showed me the Failed to start Process Error
reporting message in the boot screen and in the log.  I don't use 'no
splash' so I watch for errors and notice them at every boot.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787729

Title:
  [FAILED] Failed to start Process error reports when automatic
  reporting is enabled.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.

[Keith Myers]

● whoopsie.service - crash report submission daemon
   Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Wed 2018-10-31 11:57:10 PDT; 5 days ago
 Main PID: 1457 (whoopsie)
Tasks: 3 (limit: 4915)
   CGroup: /system.slice/whoopsie.service
   └─1457 /usr/bin/whoopsie -f

Nov 05 00:22:37 Serenity whoopsie[1457]: [00:22:37] offline
Nov 05 00:27:08 Serenity whoopsie[1457]: [00:27:08] The default IPv4 route is: 
/org/freedesktop/NetworkManager/ActiveConnection/1
Nov 05 00:27:08 Serenity whoopsie[1457]: [00:27:08] Not a paid data plan: 
/org/freedesktop/NetworkManager/ActiveConnection/1
Nov 05 00:27:08 Serenity whoopsie[1457]: [00:27:08] Found usable connection: 
/org/freedesktop/NetworkManager/ActiveConnection/1
Nov 05 00:27:09 Serenity whoopsie[1457]: [00:27:09] online
Nov 06 05:12:37 Serenity whoopsie[1457]: [05:12:37] offline
Nov 06 05:17:08 Serenity whoopsie[1457]: [05:17:08] The default IPv4 route is: 
/org/freedesktop/NetworkManager/ActiveConnection/1
Nov 06 05:17:08 Serenity whoopsie[1457]: [05:17:08] Not a paid data plan: 
/org/freedesktop/NetworkManager/ActiveConnection/1
Nov 06 05:17:08 Serenity whoopsie[1457]: [05:17:08] Found usable connection: 
/org/freedesktop/NetworkManager/ActiveConnection/1
Nov 06 05:17:10 Serenity whoopsie[1457]: [05:17:10] online

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787729

Title:
  [FAILED] Failed to start Process error reports when automatic
  reporting is enabled.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.

[Keith Myers]

This is what service apport-autoreport status shows now.  I still have
the Failed status in the error log at each boot.

keith@Serenity:~$ service apport-autoreport status
● apport-autoreport.service - Process error reports when automatic reporting is 
   Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static; vendor
   Active: inactive (dead) since Fri 2018-11-02 15:11:10 PDT; 3 days ago
 Main PID: 24527 (code=exited, status=0/SUCCESS)

● apport-autoreport.service - Process error reports when automatic reporting is 
enabled
   Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static; 
vendor preset: enabled)
   Active: inactive (dead) since Fri 2018-11-02 15:11:10 PDT; 3 days ago
 Main PID: 24527 (code=exited, status=0/SUCCESS)

Nov 02 15:11:10 Serenity whoopsie-upload-all[24527]: a = os.fspath(a)
Nov 02 15:11:10 Serenity whoopsie-upload-all[24527]: TypeError: expected str, 
bytes or os.PathLike object, not NoneType
Nov 02 15:11:10 Serenity whoopsie-upload-all[24527]: ERROR: processing 
/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.cr
Nov 02 15:11:10 Serenity whoopsie-upload-all[24527]:   skipping, not a crash
Nov 02 15:11:10 Serenity whoopsie-upload-all[24527]: 
/var/crash/_usr_bin_yelp.1000.crash already marked for upload, skipping
Nov 02 15:11:10 Serenity whoopsie-upload-all[24527]:   skipping, not a crash
Nov 02 15:11:10 Serenity whoopsie-upload-all[24527]: Collecting info for 
/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.
Nov 02 15:11:10 Serenity whoopsie-upload-all[24527]:   skipping, not a crash
Nov 02 15:11:10 Serenity whoopsie-upload-all[24527]: All reports processed
Nov 02 15:11:10 Serenity systemd[1]: Started Process error reports when 
automatic reporting is enabled.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787729

Title:
  [FAILED] Failed to start Process error reports when automatic
  reporting is enabled.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1069959] Re: HP 8500 skips printing about 3/32 inch of top of document

[Keith McClelland]

GF,

As far as I can tell the problem is now gone. There is definitely no
problem using the HP driver which names the printer as
somethng-Officejet-Pro_8500-A910. The other one (which names it  as
Officejet_Pro_8500_A910_174835_ and I think is the new generic printer)
doesn't print as close to the margins but does not seem to move the image
down 3/32 which used to be the problem.

Thanks for keeping track.
Keith

On Wed, Oct 10, 2018 at 12:30 AM Launchpad Bug Tracker <
1069...@bugs.launchpad.net> wrote:

> [Expired for cups (Ubuntu) because there has been no activity for 60
> days.]
>
> ** Changed in: cups (Ubuntu)
>Status: Incomplete => Expired
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1069959
>
> Title:
>   HP 8500 skips printing about 3/32 inch of top of document
>
> Status in cups package in Ubuntu:
>   Expired
>
> Bug description:
>   The top few pixels of anything printed from Evolution, Firefox,
>   LibreOffice applications, Shotwell, and probably others are missing on
>   the printout with HP 8500A on wifi. The problem does not occur with
>   "lpr". Note that this is the logical top but could be any of the four
>   sides of the paper.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 12.10
>   Package: cups 1.6.1-0ubuntu11
>   ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
>   Uname: Linux 3.5.0-17-generic i686
>   NonfreeKernelModules: wl
>   ApportVersion: 2.6.1-0ubuntu3
>   Architecture: i386
>   CupsErrorLog:
>W [22/Oct/2012:08:43:35 -0400] CreateProfile failed:
> org.freedesktop.ColorManager.AlreadyExists:profile id 'HP-8500-Gray..'
> already exists
>W [22/Oct/2012:08:43:35 -0400] CreateProfile failed:
> org.freedesktop.ColorManager.AlreadyExists:profile id 'HP-8500-RGB..'
> already exists
>W [22/Oct/2012:08:43:35 -0400] CreateDevice failed:
> org.freedesktop.ColorManager.AlreadyExists:device id 'cups-HP-8500' already
> exists
>   Date: Mon Oct 22 14:40:33 2012
>   InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release
> i386 (20101007)
>   KernLog:
>
>   Lpstat: device for HP-8500: hp:/net/Officejet_Pro_8500_A910?zc=HPOccam
>   MachineType: Hewlett-Packard HP Mini 110-1100
>   Papersize: letter
>   PpdFiles: HP-8500: HP Officejet Pro 8500 a910, hpcups 3.12.6
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic
> root=UUID=a22204da-1373-4d36-878a-46dd58edb287 ro quiet nosplash
> resume=UUID=34000a46-658f-4470-89ac-463117af72af
>   SourcePackage: cups
>   UpgradeStatus: Upgraded to quantal on 2012-10-20 (1 days ago)
>   dmi.bios.date: 08/27/2009
>   dmi.bios.vendor: Hewlett-Packard
>   dmi.bios.version: 308F0 Ver. F.15
>   dmi.board.name: 308F
>   dmi.board.vendor: Hewlett-Packard
>   dmi.board.version: KBC Version 02.10
>   dmi.chassis.asset.tag: CNU9371TT7
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Inventec
>   dmi.modalias:
> dmi:bvnHewlett-Packard:bvr308F0Ver.F.15:bd08/27/2009:svnHewlett-Packard:pnHPMini110-1100:pvr039511001B030:rvnHewlett-Packard:rn308F:rvrKBCVersion02.10:cvnInventec:ct10:cvr:
>   dmi.product.name: HP Mini 110-1100
>   dmi.product.version: 039511001B030
>   dmi.sys.vendor: Hewlett-Packard
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1069959/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1069959

Title:
  HP 8500 skips printing about 3/32 inch of top of document

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.

[Keith Myers]

I am having this issue.  I can't get rid of the error.
● apport-autoreport.service - Process error reports when automatic reporting is 
enabled
   Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static; 
vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2018-10-03 10:55:24 PDT; 1min 
42s ago
  Process: 1007 ExecStart=/usr/share/apport/whoopsie-upload-all (code=exited, 
status=1/FAILURE)
 Main PID: 1007 (code=exited, status=1/FAILURE)

Oct 03 10:55:24 Serenity systemd[1]: Starting Process error reports when 
automatic reporting is enabled...
Oct 03 10:55:24 Serenity whoopsie-upload-all[1007]: ERROR: whoopsie is not 
running
Oct 03 10:55:24 Serenity systemd[1]: apport-autoreport.service: Main process 
exited, code=exited, status=1/FAILURE
Oct 03 10:55:24 Serenity systemd[1]: apport-autoreport.service: Failed with 
result 'exit-code'.
Oct 03 10:55:24 Serenity systemd[1]: Failed to start Process error reports when 
automatic reporting is enabled.

keith@Serenity:~$ whoopsie
keith@Serenity:~$ systemctl status apport-autoreport.service
● apport-autoreport.service - Process error reports when automatic reporting is 
enabled
   Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static; 
vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2018-10-03 10:55:24 PDT; 3min 
13s ago
  Process: 1007 ExecStart=/usr/share/apport/whoopsie-upload-all (code=exited, 
status=1/FAILURE)
 Main PID: 1007 (code=exited, status=1/FAILURE)

Oct 03 10:55:24 Serenity systemd[1]: Starting Process error reports when 
automatic reporting is enabled...
Oct 03 10:55:24 Serenity whoopsie-upload-all[1007]: ERROR: whoopsie is not 
running
Oct 03 10:55:24 Serenity systemd[1]: apport-autoreport.service: Main process 
exited, code=exited, status=1/FAILURE
Oct 03 10:55:24 Serenity systemd[1]: apport-autoreport.service: Failed with 
result 'exit-code'.
Oct 03 10:55:24 Serenity systemd[1]: Failed to start Process error reports when 
automatic reporting is enabled.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787729

Title:
  [FAILED] Failed to start Process error reports when automatic
  reporting is enabled.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1792762] [NEW] Installation crash

[Keith Bottner]

Public bug reported:

After the LVM confirmation screen an immediate error is returned.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.6
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 15 22:19:17 2018
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic ubiquity-18.04.14.6 ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792762

Title:
  Installation crash

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1791853] Re: Postfix upgrade queries about replacing /etc/postfix/makedefs.out, when it really should always do so

[Keith Z-G]

Note that I attempted to file a bug upstream with Debian too (since
that's where this packaging choice originated), but I think I might have
mucked up the reporting format as I see no indication my bug ever
reached upstream.

** Description changed:

  When upgrading Postfix, I was surprised to be asked
  
  Configuration file '/etc/postfix/makedefs.out'
-  ==> Modified (by you or by a script) since installation.
-  ==> Package distributor has shipped an updated version.
-What would you like to do about it ?  Your options are:
- Y or I  : install the package maintainer's version
- N or O  : keep your currently-installed version
-   D : show the differences between the versions
-   Z : start a shell to examine the situation
-  The default action is to keep your current version.
+  ==> Modified (by you or by a script) since installation.
+  ==> Package distributor has shipped an updated version.
+    What would you like to do about it ?  Your options are:
+ Y or I  : install the package maintainer's version
+ N or O  : keep your currently-installed version
+   D : show the differences between the versions
+   Z : start a shell to examine the situation
+  The default action is to keep your current version.
  *** makedefs.out (Y/I/N/O/D/Z) [default=N] ?
- 
  
  This would appear to have been added with version 3.1.4-1, specifically:
  
-   * Install /etc/postfix/makedefs.out so users can see how the package
+   * Install /etc/postfix/makedefs.out so users can see how the package
  was built
  
  which is a laudable and understandable goal. However, it seems quite
  unequivocal that the package-provided version of this file should always
  be used when installing the package, since the file itself opens with
  the following line:
  
-   # Do not edit -- this file documents how Postfix was built for your
+   # Do not edit -- this file documents how Postfix was built for your
  machine.
  
  There does not seem to be a valid reason for a user to have a version of
  that file that differs at all from the package-provided version, then;
  any divergence, in fact, would be misleading.
  
  Presumably then this file should be included in a way that does not
  require user intervention to update the makedefs.out file (ex. the /etc/
  copy could just be a symlink to a copy in /usr/share/postfix/, or
  perhaps there's some packaging magic that could be done?).
  
- (I suppose I should probably have filed this bug upstream with Debian,
- but I don't actually have any Debian systems running Postfix at the
- moment, only Ubuntu Server ones.)
+ Ran into this on a server running Ubuntu 18.04.

** Description changed:

  When upgrading Postfix, I was surprised to be asked
  
  Configuration file '/etc/postfix/makedefs.out'
   ==> Modified (by you or by a script) since installation.
   ==> Package distributor has shipped an updated version.
     What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
    D : show the differences between the versions
    Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** makedefs.out (Y/I/N/O/D/Z) [default=N] ?
  
  This would appear to have been added with version 3.1.4-1, specifically:
  
    * Install /etc/postfix/makedefs.out so users can see how the package
  was built
  
  which is a laudable and understandable goal. However, it seems quite
  unequivocal that the package-provided version of this file should always
  be used when installing the package, since the file itself opens with
  the following line:
  
    # Do not edit -- this file documents how Postfix was built for your
  machine.
  
  There does not seem to be a valid reason for a user to have a version of
  that file that differs at all from the package-provided version, then;
  any divergence, in fact, would be misleading.
  
  Presumably then this file should be included in a way that does not
  require user intervention to update the makedefs.out file (ex. the /etc/
  copy could just be a symlink to a copy in /usr/share/postfix/, or
  perhaps there's some packaging magic that could be done?).
  
- Ran into this on a server running Ubuntu 18.04.
+ Ran into this on a server running Ubuntu 18.04, when running upgrades
+ which pulled down Postfix version 3.3.0-1ubuntu0.1.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791853

Title:
  Postfix upgrade queries about replacing /etc/postfix/makedefs.out,
  when it really should always do so

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

-- 
ubuntu-bugs mailing list

[Bug 1791853] Re: Postfix upgrade queries about replacing /etc/postfix/makedefs.out, when it really should always do so

[Keith Z-G]

I stand corrected: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=908545

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791853

Title:
  Postfix upgrade queries about replacing /etc/postfix/makedefs.out,
  when it really should always do so

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1791853] [NEW] Postfix upgrade queries about replacing /etc/postfix/makedefs.out, when it really should always do so

[Keith Z-G]

Public bug reported:

When upgrading Postfix, I was surprised to be asked

Configuration file '/etc/postfix/makedefs.out'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
Y or I  : install the package maintainer's version
N or O  : keep your currently-installed version
  D : show the differences between the versions
  Z : start a shell to examine the situation
 The default action is to keep your current version.
*** makedefs.out (Y/I/N/O/D/Z) [default=N] ?


This would appear to have been added with version 3.1.4-1, specifically:

  * Install /etc/postfix/makedefs.out so users can see how the package
was built

which is a laudable and understandable goal. However, it seems quite
unequivocal that the package-provided version of this file should always
be used when installing the package, since the file itself opens with
the following line:

  # Do not edit -- this file documents how Postfix was built for your
machine.

There does not seem to be a valid reason for a user to have a version of
that file that differs at all from the package-provided version, then;
any divergence, in fact, would be misleading.

Presumably then this file should be included in a way that does not
require user intervention to update the makedefs.out file (ex. the /etc/
copy could just be a symlink to a copy in /usr/share/postfix/, or
perhaps there's some packaging magic that could be done?).

(I suppose I should probably have filed this bug upstream with Debian,
but I don't actually have any Debian systems running Postfix at the
moment, only Ubuntu Server ones.)

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791853

Title:
  Postfix upgrade queries about replacing /etc/postfix/makedefs.out,
  when it really should always do so

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Keith Myers]

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

All BOINC packages depend on libcurl3.  Ukuu wanted to install libcurl4
and remove libcurl3.

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

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1784152] Re: i2c_hid_get_input floods system logs

[Keith Brown]

This is happening to me too on an Acer Aspire 5 A515-51G-515J. Adding
"acpi_osi=" to GRUB_CMDLINE_LINUX_DEFAULT left me without a trackpad (it
eliminated the log messages too, of course!).

$ uname -a
Linux dev 4.15.0-33-generic #36~16.04.1-Ubuntu SMP Wed Aug 15 17:21:05 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.5 LTS
Release:16.04
Codename:   xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784152

Title:
  i2c_hid_get_input floods system logs

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.

[Keith]

Is there a way to re-create the resume file? The commands I mentioned
earlier removed it, so I can't try the edit option.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768230

Title:
  Long time booting : Failed to connect to lvmetad. Falling back to
  device scanning.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.

[Keith]

Same issue - only latest Ubunutu updates and OS (GUI based) as of today.
Did following:

> rm /etc/initramfs-tools/conf.d/resume
> sudo update-initramfs -u

Resume file is gone and issue still happens. Please help with any other
solutions to this issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768230

Title:
  Long time booting : Failed to connect to lvmetad. Falling back to
  device scanning.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1783200] Re: [Lenovo Miix 310, Ubuntu 18.04] Audio no longer working

[Keith Gaughan]

I'm also attaching the contents of /var/log/syslog for a desktop session
with 'log-level = debug' in PA's daemon.conf file, if it helps.

** Attachment added: "syslog.pa.debug.xz"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1783200/+attachment/5168664/+files/syslog.pa.debug.xz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783200

Title:
  [Lenovo Miix 310, Ubuntu 18.04] Audio no longer working

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1783200] Re: [Lenovo Miix 310, Ubuntu 18.04] Audio no longer working

[Keith Gaughan]

I can get other processes to produce core dumps, but pulseaudio is not
producing any.

Given PA stops dying when I add 'realtime-scheduling = no' to
/etc/pulse/daemon.conf, this makes me think that the process is hitting
either RLIMIT_RTTIME or RLIMIT_CPU, which would cause the kernel to send
SIGKILL to the process when PA is scheduled (as it normally is) as a
realtime process.

While this is a relatively small machine, I would expect the OOM killer
to be a factor regardless of the value assigned to realtime-scheduling,
but it _only_ dies when PA is started as a realtime process.

I did some more experiments. For whatever reason, indicator-sound wasn't
installed (and there's no reason I would've removed it, so it's a
mystery as to why it wasn't installed). Once I installed that, with
'realtime-scheduling = yes', PA would repeatedly die, but eventually
start. With 'realtime-scheduling = no', it would start immediately.
Without indicator-sound installed, PA would start if 'realtime-
scheduling = no', but fail to start if 'realtime-scheduling = yes'.

I'm attaching the contents of /var/log/syslog in the hope that it's
useful, at least to show the behaviour I'm seeing.

** Attachment added: "/var/log/syslog"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1783200/+attachment/5168646/+files/syslog.xz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783200

Title:
  [Lenovo Miix 310, Ubuntu 18.04] Audio no longer working

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1783200] Re: [Lenovo Miix 310, Ubuntu 18.04] Audio no longer working

[Keith Gaughan]

I don't believe that'll work because pulseaudio is getting a SIGKILL,
not a SIGABRT, , so apport will never receive a coredump anyway.

I did a bit more research and came across
. I updated
/etc/pulse/daemon.conf, adding 'realtime-scheduling = no', and the
daemon was able to run. I think the issue I've been having is related to
that bug. However, the odd thing is that I recall under 17.10 being able
to plug a HDMI cable in and out without causing PA to die, so I'm not
100% sure it's exactly that issue. Regardless, I've marked
 as affecting me.

** Bug watch added: freedesktop.org Bugzilla #100488
   https://bugs.freedesktop.org/show_bug.cgi?id=100488

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783200

Title:
  [Lenovo Miix 310, Ubuntu 18.04] Audio no longer working

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1783200] Re: [Lenovo Miix 310, Ubuntu 18.04] Audio no longer working

[Keith Gaughan]

Yup, pulseaudio doesn't start at all. When I run it with 'pulseaudio
-vv' to get the debug output, it ends with a SIGKILL. There's no daemon
running.

Here's a bug that I believe might be connected, and I commented on it
before: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1759942

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783200

Title:
  [Lenovo Miix 310, Ubuntu 18.04] Audio no longer working

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1783200] [NEW] [Lenovo Miix 310, Ubuntu 18.04] Audio no longer working

[Keith Gaughan]

Public bug reported:

I believe this is a pulseaudio regression, as the output of alsa-info
(http://www.alsa-
project.org/db/?f=730ab5b8f0499ef58c0e17f67f8f911ba53a011c) looks fine
as far as I can see.

I'm currently running Ubuntu 18.04, and I believe this is a regression
as audio used to work under 17.10. Since upgrading (which fixed a good
number of other incompatibilities with the machine), I've had no luck
getting audio to work at all.

I'm attaching the output of dmesg, 'aplay -l', 'aplay -L' and
'pulseaudio -vv'.

If I can provide any other information, or if there's anything you'd
like me to try, I'd be happy to help in any way possible.

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

** Attachment added: "Tarball of relevant logs, "
   https://bugs.launchpad.net/bugs/1783200/+attachment/5166847/+files/logs.tzx

** Summary changed:

- [Lenovo Miix 310, Ubuntu 18.10] Audio no longer working
+ [Lenovo Miix 310, Ubuntu 18.04] Audio no longer working

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783200

Title:
  [Lenovo Miix 310, Ubuntu 18.04] Audio no longer working

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

[Keith David Winkler]

I found that the "Workspace Indicator" was causing this problem for me.

https://extensions.gnome.org/extension/21/workspace-indicator/

Clean install of 18.04 on real hardware. Xorg session. Nvidia 1050 with
open source drivers. 2k resolution.   Problem did NOT occur for two
weeks.  Installed "Workspace Indicator" and problem occurred within 24
hours. It reoccurred once or twice every subsequent 24 hours.
Uninstalled "Workspace Indicator" and problem has not reoccurred for
four days.

The problem: gnome shell stops responding to all mouse *clicks* within
OS or on gnome shell components.  Mouse cursor movement is still
possible.  All keyboard navigation is still possible.  Mouse clicks
begin to work again after 5 to 10 minutes.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181666

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1759942] Re: [HdmiLpeAudio - Intel HDMI/DP LPE Audio, playback] No sound at all

[Keith Gaughan]

I believe I'm hitting the same issue, albeit with a Lenovo Miix 310,
which previously to upgrading to Bionic had working audio.

Attached is a log of what I get when I attempt to start pulseaudio with
"pulseaudio -vv", and the list of devices and PCMs given by "aplay -l"
and "aplay -L" respectively.

** Attachment added: "Archive of log files."
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1759942/+attachment/5155943/+files/logs.tzx

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759942

Title:
  [HdmiLpeAudio - Intel HDMI/DP LPE Audio, playback] No sound at all

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1776645] [NEW] package libgnome-bluetooth13:amd64 3.28.0-2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Keith Walter Witzel]

Public bug reported:

I am wondering if my communications card in my laptop does not have
bluetooth if this error would occur? if I turn off my bluetooth settings
would it go away?

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libgnome-bluetooth13:amd64 3.28.0-2
ProcVersionSignature: Ubuntu 4.15.0-22.24-lowlatency 4.15.17
Uname: Linux 4.15.0-22-lowlatency x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Wed Jun 13 06:53:35 2018
DuplicateSignature:
 package:libgnome-bluetooth13:amd64:3.28.0-2
 Processing triggers for desktop-file-utils (0.23-1ubuntu3) ...
 dpkg: error processing package libgnome-bluetooth13:amd64 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2018-05-23 (21 days ago)
InstallationMedia: Ubuntu-Studio 17.10 "Artful Aardvark" - Release amd64 
(20171017.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: gnome-bluetooth
Title: package libgnome-bluetooth13:amd64 3.28.0-2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-bluetooth (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776645

Title:
  package libgnome-bluetooth13:amd64 3.28.0-2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 289101] Re: Ubiquity crashed while installing grub

[Keith Withey via ubuntu-bugs]

Trying to install grub & system on SSD, data  (and existing win 7) on
separate disc.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/289101

Title:
  Ubiquity crashed while installing grub

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1774881] [NEW] package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: installed linux-image-4.15.0-20-generic package pre-removal script subprocess returned error exit stat

[Keith Gaughan]

Public bug reported:

Happened after a reboot after a kernel update.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-20-generic 4.15.0-20.21
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
Date: Sun Jun  3 17:41:51 2018
ErrorMessage: installed linux-image-4.15.0-20-generic package pre-removal 
script subprocess returned error exit status 1
InstallationDate: Installed on 2018-01-21 (132 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
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: linux-signed
Title: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to 
install/upgrade: installed linux-image-4.15.0-20-generic package pre-removal 
script subprocess returned error exit status 1
UpgradeStatus: Upgraded to bionic on 2018-04-30 (34 days ago)

** Affects: linux-signed (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774881

Title:
  package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to
  install/upgrade: installed linux-image-4.15.0-20-generic package pre-
  removal script subprocess returned error exit status 1

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1773732] [NEW] [Satellite S55D-A, IDT 92HD99BXX, Speaker, ATAPI] No sound at all

[Keith Spencilmore]

Public bug reported:

```
dan@dan-laptop:~$ lsb_release -rd
Description:Ubuntu 18.04 LTS
Release:18.04
```

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  dan1116 F pulseaudio
 /dev/snd/controlC0:  dan1116 F pulseaudio
CurrentDesktop: XFCE
Date: Mon May 28 00:33:03 2018
InstallationDate: Installed on 2018-05-02 (25 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
Symptom_Card: Built-in Audio - HD-Audio Generic
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  dan1116 F pulseaudio
 /dev/snd/controlC0:  dan1116 F pulseaudio
Symptom_Jack: Speaker, ATAPI
Symptom_Type: No sound at all
Title: [Satellite S55D-A, IDT 92HD99BXX, Speaker, ATAPI] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/19/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 1.10
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: VG10AD
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.10:bd06/19/2013:svnTOSHIBA:pnSatelliteS55D-A:pvrPSKKSU-00S006:rvnAMD:rnVG10AD:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.family: Type1Family
dmi.product.name: Satellite S55D-A
dmi.product.version: PSKKSU-00S006
dmi.sys.vendor: TOSHIBA

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773732

Title:
  [Satellite S55D-A, IDT 92HD99BXX, Speaker, ATAPI] No sound at all

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772429] [NEW] dual booting couldn't write grub boot loader during install

[Keith Greer]

Public bug reported:

No windows, existing Ubuntu mate 17 (32 bit) was to dual boot into new
Ubuntu Mate 18 (64-bit)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CasperVersion: 1.394
Date: Mon May 21 16:05:01 2018
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed 
boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 LANGUAGE=en_GB.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic ubiquity-18.04.14 ubuntu-mate

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772429

Title:
  dual booting couldn't write grub boot loader during install

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

[Keith from Ipswich]

Thank you PeterPaul. Will try again after the next Bionic kernel upgrade. In 
the meantime the brother MFC is plugged into my 16.04 PC and network connected. 
The printer cost me $20 at a garage sale and only has USB.
PS - more pieces of the puzzle: the brother-udev-rule-type1 DEB package 
mentioned above as not necessary creates a file 
/opt/brother/scanner/udev-rules/type1/NN-brother-mfp-type1.rules and this rules 
file has a comment that it should be copied to the relevant udev folder - 
/etc/udev/rules.d;
The driver name is "Brother MFC7420 for CUPS" and does not have a hyphen after 
MFC so it appears after all MFC printers in the list of drivers and is easily 
missed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728012

Title:
  Many 3rd party scanner drivers are broken by a sane change

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

[Keith from Ipswich]

https://forums.opensuse.org/showthread.php/507627-Suse-13-2-scanner-no-
longer-working-on-64-bit-
version/page2?s=ac5dc860f0f94d47d233f69afdbfc346 has similar debug
results to my prior comment. It was resolved by using a USB2 port
instead of a USB3 port. Maybe this is another piece of the puzzle as I
had to use an earlier version of libusb and my MB is recent with mainly
USB3 - will try changing bios on another day

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728012

Title:
  Many 3rd party scanner drivers are broken by a sane change

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

[Keith from Ipswich]

Brother MFC-7420 installed under fresh install of 18.04 and connected
via USB. Brother2 drivers are installed. Have created links and local
udev rules and almost have scanner working.

scanimage -L >>> device `brother2:bus2;dev4' is a Brother MFC-7420 USB scanner
scanimage --test >>> scanimage: open of device brother2:bus2;dev4 failed: 
Invalid argument

Using debug, scanimage test openned and successfully interrogated the scanner 
but failed with
[dll] sane_start(handle=0x55c29b5b7ee0)
scanimage: sane_start: Invalid argument

scanning to file was similar
[dll] sane_open: trying to open `brother2:bus2;dev1'
scanimage: open of device brother2:bus2;dev1 failed: Invalid argument

To get this far my drivers needed libusb-0.1-4 (userspace USB
programming library). 18.04 uses libusb-1 and they are not
interchangeable as I tried a simple link pointing to new version.

Is this a jigsaw puzzle with a couple of pieces missing

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728012

Title:
  Many 3rd party scanner drivers are broken by a sane change

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1768045] [NEW] Grub 2 failed to install

[Keith Whittington]

Public bug reported:

I was only trying to install update

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 30 10:45:30 2018
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic ubiquity-18.04.14 ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768045

Title:
  Grub 2 failed to install

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767552] [NEW] screen rotates if laptop tilts

[keith moore]

Public bug reported:

I have ran windows 7, 10, ubuntu 16.04, linux mint and maybe others and
i can't recall it doing this before. it is hp 450 g2 laptop. it is not a
2in1 tablet/laptop. i looked for info in forums but had no luck. i also
checked in settings because i thought it may have had a tablet setting i
could turn off.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 27 21:58:43 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:2248]
   Subsystem: Hewlett-Packard Company Topaz PRO [Radeon R5 M255] [103c:224a]
InstallationDate: Installed on 2018-04-27 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Hewlett-Packard HP ProBook 450 G2
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-20-generic 
root=UUID=d0b638ce-09f3-4d54-a78f-b7aeebaef22f ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/21/2015
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: M73 Ver. 01.09
dmi.board.name: 2248
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 59.21
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM73Ver.01.09:bd01/21/2015:svnHewlett-Packard:pnHPProBook450G2:pvrA3009DD10303:rvnHewlett-Packard:rn2248:rvrKBCVersion59.21:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
dmi.product.name: HP ProBook 450 G2
dmi.product.version: A3009DD10303
dmi.sys.vendor: Hewlett-Packard
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.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: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767552

Title:
  screen rotates if laptop tilts

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1751627] [NEW] LibreOffice 5.4.5.1/TexMaths can't find latex or divpng or dvisvgm

[Keith Clayton]

Public bug reported:

After applying daily updates, libreoffice was updated to 5.4.5.1   After
the upgrade, TexMaths ceased to function.

Would return an error of "Can't find the external program latex
Please check the paths in your TexMaths system configuration..."

Paths checked out fine (/usr/bin)   Confirmed latex is still in
/usr/bin.

Attempted to just reset the paths for latex and dvipng and dvisvgm to
/usr/bin and Save in the TexMaths dialog

Got the following errors
"The program latex is not located in /usr/bin/"...   which is not true

Would not let me save or exit the dialog box.  Tried a variety of
different mods to path (with leading / and without . .  with trailing /
and without) thinking it might be a small path parsing bug.  No effect.
Finally had to x out the dialog.  Then received

"Can't find at least one of the external programs dvipng or dvisvgm
Please check the paths in your TexMaths system configuration"   and had to go 
through the same dialog game.

Updated the TexMaths extension to 0.44 but no change.

Upon searching the bug tracker, it appears there is a FS bug that
someone ran into.  Maybe this is related?

I can open old files, edit them, etc.  But I can't modify any of my
embedded latex equations.  Given that I'm a math instructor and use this
to write my lessons quizzes and exams.  This is a really critical bug
for me.

I'm pretty much dead in the water at the moment without this
functionality.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libreoffice-writer 1:5.4.5-0ubuntu0.17.10.1
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Feb 25 10:29:16 2018
EcryptfsInUse: Yes
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: Upgraded to artful on 2018-01-02 (53 days ago)

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


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751627

Title:
  LibreOffice 5.4.5.1/TexMaths can't find latex or divpng or dvisvgm

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1748370] [NEW] package grub-common 2.02~beta3-4ubuntu7.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Keith Hayward]

Public bug reported:

Failed while installing update

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: grub-common 2.02~beta3-4ubuntu7.1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Thu Feb  8 22:58:17 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-10-21 (110 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=fc354326-20f5-40c0-820a-7e17512e2209 ro quiet splash vt.handoff=7
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: grub2
Title: package grub-common 2.02~beta3-4ubuntu7.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package artful

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748370

Title:
  package grub-common 2.02~beta3-4ubuntu7.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1739603] [NEW] Failed install.

[Keith Rothschild]

Public bug reported:

Failed install when trying to downgrade from 17.10 to 16.04 LTS.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.4
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CasperVersion: 1.376.2
Date: Thu Dec 21 12:00:37 2017
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug ubiquity-2.21.63.4 ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739603

Title:
  Failed install.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1736253] Re: Ubuntu 16.4.3 LTS update makes trackpoint erratic

[Keith Wannamaker]

Booted back to 4.10.0-37-generic and the problem seems to have gone
away.  This was 2 kernels ago.  I will try -38, the intermediate
version, and report back.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736253

Title:
  Ubuntu 16.4.3 LTS update makes trackpoint erratic

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1736253] [NEW] Ubuntu 16.4.3 LTS update makes trackpoint erratic

[Keith Wannamaker]

Public bug reported:


The latest reboot brought new software which has wrought terror on my 
Trackpoint.
The behavior is that the trackpoint begins behaving as if one is holding the 
middle trackpad button - instead of trackpoint inputs causing expected mouse 
pointer movement, windows switch, windows scroll.  I've seen erratic pasting as 
well.  Once entered into this mode, the only way to return to normal is to left 
or right click - in the trackpad (left click on the buttons above the trackpad 
don't help).  Then you are safe for the next 15-20 seconds until another 
faux-middle button press happens.  

This behavior is totally new with an update sometime in the last 2-3
weeks (I don't often reboot).

Lenovo T470

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


** Tags: trackpad trackpoint

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736253

Title:
  Ubuntu 16.4.3 LTS update makes trackpoint erratic

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs