Ike, I've subscribed you since I notice you're listed as an upstream
maintainer of this module.
Are you able to get this committed in mainline and SRU-ed into Ubuntu
kernels?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811869
Title:
Alienware m15 takes very long to boot Ubuntu
To manage
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => TJ (tj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811869
Title:
Alienware m15 takes very long to boot Ubuntu
To man
unassigned) => TJ (tj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811815
Title:
Lenovo ideapad 330-15ICH Wifi rfkill hard blocked
To manage notifications about this bug go to:
https://bugs.launchp
** Summary changed:
- Ubuntu 18.10, Kernel 4.18, Intel Dual Band Wireless-AC 3165 Not Found
+ Lenovo ideapad 330-15ICH Wifi rfkill hard blocked
** Description changed:
+ The issue here is that the drivers/platform/x86/ideapad_laptop.c module
+ assumes the Lenovo Ideapad 330-15ICH has a hardware
Public bug reported:
When purging the package with
$ sudo apt purge uswsusp
...
cryptsetup: WARNING: found more than one resume device candidate:
df774d5e-c791-4e89-b8ed-fd7126486d63
I almost forgot about this; 4.17.19-041719-lowlatency has been running
fine now for 16 days. I'm going to switch to 4.18.0-13-lowlatency and
confirm the problem still exists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
daftykins:
Your issue is there is no handler so you won't find anything in
debug/irg for it:
[ 167.279809] do_IRQ: 1.35 No irq handler for vector
HOWEVER, you should be able to find which target device is responsible
by searching for matching Target: value, e.g. something like:
$ grep -l
Five days running on 4.16.18-041618-lowlatency and had no problems so
I'm going to try the mainline build of v4.17.19.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803960
Title:
4.18.0 kernels
Public bug reported:
Thread 1 "nm-connection-e" received signal SIGSEGV, Segmentation fault.
0x77ba6b53 in modules_initialized (object=,
res=0x56048a40, user_data=) at
src/libnma/nma-cert-chooser-button.c:98
98 src/libnma/nma-cert-chooser-button.c: No such
This hang is affecting all mainline builds (from the kernel PPA) up to
and including 4.20-rc4.
The only version that doesn't appear to be affected is
4.15.0-38-lowlatency.
I'll start working backward from the 4.18* versions to try to narrow
where the apparent regression begins so that a bisect
Just experienced the same symptom of a complete, silent, freeze with:
-- Logs begin at Sun 2018-04-01 13:42:23 BST, end at Wed 2018-11-28 10:33:23
GMT. --
Nov 20 10:48:10 T300CHI kernel: microcode: microcode updated early to revision
0x2b, date = 2018-03-22
Nov 20 10:48:10 T300CHI kernel: Linux
I've been helping a user on IRC #ubuntu reporting this problem using the
18.10 ISO installer. In this case during the (first) installer run the
PC crashed and rebooted before completing the install.
>From then on trying to boot the installer is failing with these error
messages:
Failed to open
I've been using the 4.18.0-12-lowlatency kernel from cosmic and not had
any freeze-ups in the last 48 hours. I'll continue monitoring and report
back after a few more days.
Because there are lots of reports of Intel Baytrail CPUs suffering
freezes due to c-states I want to make clear the CPU here
Public bug reported:
I've been using 18.04 on an Asus T300CHI without issue until I decided
to switch to the v4.18 kernels from 18.10 via linux-image-lowlatency-
hwe-18.04-edge.
Since then the system randomly but regularly completely hangs. Only a
hard power-off resolves it.
Frustratingly there
Julian - I hadn't realised there are two gpgv's!
Having found apt's own /usr/lib/methods/gpgv
I have been able to create a shell wrapper that can feed it the expected
request headers and parse the response headers to ensure a GPGVOutput:
GOODSIG ...
It's a proof of concept right now; if this
)
E: Unable to lock directory /var/lib/apt/lists/
Investigating further I discovered a 3 day old cron job is hung:
$ date
Tue 6 Nov 08:50:20 GMT 2018
$ ps -efly | grep apt
S tj 31068 8492 0 80 0 1016 5384 pipe_w 08:48 pts/400:00:00
grep --color=auto apt
S root 31280 1
I've created a shell wrapper than might be useful for this called
"gpgpv-multisig" which is a multi-call executable. Given /usr/bin/gpgv-
multisig
ln -s gpgv-multisig /usr/bin/gpgv-aptkeys
and called as 'gpgv-aptkeys' it will assume the keyring to be used is
/etc/apt/trusted.gpg (set by
There's a patch attached to the related Debian bug which works and is
included in later packages.
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=803710;filename
=nfs-utils-1.2.8_fix-avoid-dns.diff;msg=5
Can we get this into 16.04 please?
--
You received this bug notification because
Public bug reported:
A user with 18.10 reported log being spammed with:
Nov 01 16:49:50 myhostname systemd-udevd[3398]: Process '/bin/chmod 0666 '
failed with exit code 1.
Nov 01 16:49:50 myhostname systemd-udevd[3400]: Process '/bin/chmod 0666 '
failed with exit code 1.
Nov 01 16:49:50
ZdravkoG:
After the package upgrades did you reboot before testing? I've not been
able to reproduce it since whereas before the upgrade it would happen
100% of the time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
After the package upgrade to libpam-kwallet 4:5.12.7 from bionic-
proposed the issue has gone away. That seems to be due to commit
8da1a470 included in this version:
commit 8da1a47035fc92bc1496059583772bc4bd6e8ba6
Author: Maximiliano Curia
Date: Fri May 4 22:06:06 2018 +0200
Avoid giving
I added an additional log report to the function drop_privileges() since
that contains a call to setgroup(0, NULL) which, if called as the user,
would have the effect of removing all the supplementary groups.
diff --git a/pam_kwallet.c b/pam_kwallet.c
index 07b357d..147f129 100644
---
Apparently it should be fixed by
e4dcd10d648d 2018-10-01 13:51:02 -0500 N Peter Zijlstra clocksource:
Revert "Remove kthread"
contained in
ac63ef0b0a4e 2018-10-01 13:51:02 -0500 N Greg Kroah-Hartman Linux
4.18.11
which should be in
077b291605b9 2018-10-05 11:13:20 -0500 N Seth Forshee UBUNTU:
Public bug reported:
Boot fails very early in the boot with an NMI using the linux-image-
lowlatency-hwe-18.04-edge on 18.04
Falling back to linux-image-4.15.0-38-lowlatency system boots correctly.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Affects:
*** This bug is a duplicate of bug 1781418 ***
https://bugs.launchpad.net/bugs/1781418
This appears to be due to CVE patches in kwallet-pam not policykit-1.
Marking this as a duplicate of
Bug #1781418 "User not being initialized correctly on login"
It affects lightdm due to its
It was a clean install of 18.10. The mainline module doesn't have
support for this device as yet. Since the blacklist the user has gone
quite so additional testing is not possible
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because
There is a common issue on these I219-V systems which usually manifests
when used in a dual-boot scenario with Windows.
In that case the Windows driver enables various power-management
settings which, when rebooting into Linux without a cold-off, results in
network problems. Most usually the
Removing the package causes a lot of churn even on a minimal cross-build
install:
$ sudo apt remove libc6-armhf-cross
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797772
Title:
ideapad_laptop disables WiFi/BT radios on Lenovo Y530
To manage
** Changed in: linux (Ubuntu)
Assignee: Nisankh Acharjya (nisankhubuntu) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797772
Title:
ideapad_laptop disables WiFi/BT radios on
The kernel has a module for this, "hid-primax", which re-orders the
received HID reports to make them compliant.
$ modinfo hid-primax
filename:
/lib/modules/4.15.0-34-lowlatency/kernel/drivers/hid/hid-primax.ko
license:GPL
author: Terry Lambert
srcversion:
** Description changed:
I've been working with a user that has a Lenovo Legion Y530-15ICH where
booting Ubuntu 18.10 (kernel 4.18.0-8) results in the radios being
disabled by the platform driver "ideapad-laptop".
Unloading or blacklisting the module solves the issue but disables other
** Description changed:
I've been working with a user that has a Lenovo Legion Y530-15ICH where
booting Ubuntu 18.10 (kernel 4.18.0-8) results in the radios being
- disabled by the platform driver "ideapad-laptop". Unloading or
- blacklisting the module solves the issue but disables other
** Description changed:
I've been working with a user that has a Lenovo Legion Y530-15ICH where
booting Ubuntu 18.10 (kernel 4.18.0-8) results in the radios being
disabled by the platform driver "ideapad-laptop". Unloading or
blacklisting the module solves the issue but disables other
Public bug reported:
I've been working with a user that has a Lenovo Legion Y530-15ICH where
booting Ubuntu 18.10 (kernel 4.18.0-8) results in the radios being
disabled by the platform driver "ideapad-laptop". Unloading or
blacklisting the module solves the issue but disables other platform
ACPI
I'm still seeing the issue and have followed up in bug #1797557
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769657
Title:
update toolchain packages for bionic
To manage notifications about this
Public bug reported:
As I reported in comments on the end of Bug #1769657 "update toolchain
packages for bionic" on 5th October 2018 the updates have broken the
ability to upgrade package(s). Specifically, the 'dpkg --unpack' stage
breaks because, from what I can tell, some of the .dpkg-new files
An strace shows:
$ sudo strace -o /tmp/dpkg.log -f dpkg -i /var/cache/apt/archives/libc6
-dev-armhf-cross_2.27-3ubuntu1cross1.1_all.deb
$ grep -E '(Mcrt1|error processing)' /tmp/strace-dpkg.log
22528 lstat("/usr/arm-linux-gnueabihf/lib/Mcrt1.o", 0x7ffef13bf320) = -1 ENOENT
(No such file or
I suspect the recent Bionic changes have broken the install. At least
I'm seeing the following:
$ sudo apt-get upgrade
Reading package lists... 0%
Reading package lists... 100%
Reading package lists... Done
Building dependency tree... 0%
Building dependency tree... 0%
Building dependency
This issue effects a manual (debootstrap) installation of 18.04.1.
Ethernet devices are unmanaged by NetworkManager until a netplan
configuration is added.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- x11vnc on zesty terminates with **stack smashing detected** error
+ x11vnc terminates with **stack smashing detected** error
** Description changed:
+ Users report this also affects 18.04 bionic.
+
x11vnc will terminate abnormally on zesty with a **stack smashing
** Changed in: xfce4-settings (Ubuntu)
Assignee: TJ (tj) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615286
Title:
xfce - screen turns black after power off/po
** Changed in: xfce4-settings (Ubuntu)
Assignee: (unassigned) => TJ (tj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615286
Title:
xfce - screen turns black after power off/po
** Also affects: xfce4-settings (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xfce4-settings (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- Regression due to CVE-2018-1116 (processes not inheriting user's groups )
+ Regression due to CVE-2018-1116 (processes not inheriting user's
supplementary groups )
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I've just been caught out by this when the EFI -signed- packages somehow
got themselves installed - despite having been removed in the past when
they appeared due to a change in the depends - and replaced the locally
built grubx64.efi that contains the cryptodisk, luks, etc., modules,
leaving the
Just noticed in $HOME/.xsession-errors the following:
(polkit-gnome-authentication-agent-1:4029): polkit-gnome-1-WARNING **:
15:04:54.498: Failed to register client:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.gnome.SessionManager was not provided by any .service files
And this is the same output using the 'correct' scenario by logging into
the TTY console first.
cmdline: -bash
Tgid: 3516
Ngid: 0
Pid:3516
PPid: 3488
TracerPid: 0
Uid:1000100010001000
Gid:1000100010001000
Groups: 0 4 6 7 20 24 25 27 29 44 46 100 108
Just noticed the PID tree trace didn't match on the Group: from
proc/$PID/status. Here's the corrected output.
$ pid=$BASHPID; while [[ $pid -ne 0 ]]; do ids=$(grep
'^\(.*id:\|Group\)' /proc/$pid/status); echo -e "cmdline: $(cat
/proc/$pid/cmdline) \n $ids" 2>/dev/null; pid=$(echo $ids | awk
Marc:
Are you using gdm to log into the graphical session?
lightdm - this is Xubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784964
Title:
Regression due to CVE-2018-1116 (processes not
Marc: regular stand-alone install, local authentication via
passwd/shadow/group.
Here's what I see with the 'broken' sequence GUI terminal:
tj ~ id
uid=1000(tj) gid=1000(tj) groups=1000(tj)
tj ~ groups
tj
tj ~ groups $USER
tj : tj root adm disk lp dialout cdrom floppy sudo audio
I am beginning to suspect this is an systemd-logind issue. I've been
thinking it's logind but just checked the upgrade packages to/from
versions and cross-checked against the changelogs.
? systemd:amd64 (237-3ubuntu10, 237-3ubuntu10.3),
And we have a major change to logind included in that:
I think this Debian-reported bug is closely related. The description
certainly sounds very like what I've experienced so far. I'm not linking
it to this bug report until any relationship is clearer.
"policykit-1: please treat background processes (user bus) as part of
active GUI session"
** Summary changed:
- Regression due to CVE-2018-1116 (processes not inheriting user ID or groups )
+ Regression due to CVE-2018-1116 (processes not inheriting user's groups )
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Tom tried those things in a VM last night and could reproduce it. On a
suggestion by Robbie Basak but the downgrade didn't solve it, which made
me suggest something in the configuration is being permanently changed.
I'm not going to downgrade the package because I am debugging it and
don't want
I've awk-ed a list of the packages Upgraded or Installed on July 28th on
the affected PC (previous upgrade was on July 8th). I've put a ? in
front of those that could be suspect. That list is short:
grep '^?' Hacking/bug-groups-packages-updated.log
? gir1.2-polkit-1.0:amd64 (0.105-20,
It seems that /var/run/ConsoleKit directory and its database is only
created by console tty log-ins but not the GUI. There was no directory
after GUI Terminal shell started; only after switching to TTY1.
So it would seem this isn't the cause since PCs without ConsoleKit work
fine.
--
You
Looking at the diff between upstream 0.105 and Ubuntu's I happened to
notice the CKDB_PATH (ConsoleKit database path)
/var/run/ConsoleKit/database which seems to be consulted on some
occasions.
On the affected PC which was d-r-u-ed from 16.04 ConsoleKit 0.4.6-5 is
still installed and that
Looking at the diff between Ubuntu and upstream I noticed Ubuntu 0.105
code isn't adapted for "systemd --user" as described in
https://bugs.freedesktop.org/show_bug.cgi?id=76358
and in the source for the function:
polkit_backend_session_monitor_is_session_active()
** Bug watch added:
The quirk is more nuanced than I reported above.
This reports groups correctly:
1. GUI login
2. Switch to TTY, login
3. "groups"
4. Switch to GUI
5. Launch Terminal
6. "groups"
This only reports the username:
1. GUI Login
2. Launch Terminal
3. "groups"
4. Switch to TTY, login
5. "groups"
I've discovered another quirk:
If my first log-in after booting is at the TTY console (not GUI) the
groups show up correctly there *and* in a terminal in the Xorg GUI
session afterwards.
But if I first log-in to the GUI then log-in to the TTY console both
show only the user group.
--
You
journalctl shows the problem with the auid and session values being
0x (-1) when calling a sudo command:
Aug 02 01:18:20 hephaestion.lan.iam.tj audit[5094]: USER_AUTH pid=5094
uid=1000 auid=4294967295 ses=4294967295 msg='op=PAM:authentication
acct="tj" exe="/usr/bin/sudo&q
** Description changed:
This report is tracking a possible regression caused by the recent
CVE-2018-1116 patches to policykit-1.
On 18.04, since package upgrades on July 23rd, and after the first
reboot since then on Aug 1st, I hit an issue with the primary (sudo,
adm, etc...) user
Public bug reported:
This report is tracking a possible regression caused by the recent
CVE-2018-1116 patches to policykit-1.
On 18.04, since package upgrades on July 23rd, and after the first
reboot since then on Aug 1st, I hit an issue with the primary (sudo,
adm, etc...) user getting
cloudimage-configdrive is not mutated):
boxes ubuntu-VAGRANTSLASH-bionic 0 find . -ls
270462 4 drwxrwxr-x 4 tj tj 4096 Jul 29 17:43 .
270457 4 drwxrwxr-x 2 tj tj 4096 Jul 29 17:43
./libvirt
262177 1028044 -rw-r--r-- 1 tj tj
** Changed in: virtinst (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1400012
Title:
virt-xml is missing
To manage notifications about this bug go to:
Public bug reported:
Package description claims virt-image is included but it no longer is.
$ apt-file list virtinst | grep image | wc -l
0
$ apt-cache show virtinst
Package: virtinst
Architecture: all
Version: 1:1.5.1-0ubuntu1
Priority: extra
Section: universe/admin
Source: virt-manager
** Description changed:
$ vagrant up tactyle
...
==> tactyle: Creating shared folders metadata...
==> tactyle: Starting domain.
==> tactyle: Waiting for domain to get an IP address...
And it stalls there.
Using Virtual Machine Manager GUI I was able to monitor what the
Public bug reported:
$ vagrant up tactyle
...
==> tactyle: Creating shared folders metadata...
==> tactyle: Starting domain.
==> tactyle: Waiting for domain to get an IP address...
And it stalls there.
Using Virtual Machine Manager GUI I was able to monitor what the
vagrant-libvirt VM was doing
I'm currently working around it by bind-mounting the upstream source
over the Ubuntu package thus:
mkdir -p /home/all/SourceCode/vagrant
cd /home/all/Sourcecode/vagrant
git clone https://github.com/vagrant-libvirt/vagrant-libvirt.git
sudo mount --bind /home/all/SourceCode/vagrant/vagrant-libvirt
Public bug reported:
In trying to launch a standard ubuntu/bionic64 Vagrant box on 18.04 LTS
I found it fails with the report:
Call to virDomainCreateWithFlags failed: Unable to get index for
interface eth0: No such device"
which is directly from libvirt (same error in syslog).
For many hours
As Vinson said, Ubuntu kernels support MCE and mcelog source
builds/works on 18.04.
Package should be manually imported if Debian's removal is permanent.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
>From UbiquitySyslog.txt this suggests the installer image on the install
media (USB?) is corrupt:
May 27 19:11:48 ubuntu-mate kernel: [ 485.639017] SQUASHFS error: zlib
decompression failed, data probably corrupt
May 27 19:11:48 ubuntu-mate kernel: [ 485.639035] SQUASHFS error:
** Also affects: grub2-signed (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/1645075
Title:
UEFI + Secureboot + guided full disk encryption ->
** Attachment added: "fstab"
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1767527/+attachment/5129209/+files/fstab
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767527
Title:
** Attachment added: "blkid and lsblk"
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1767527/+attachment/5129208/+files/blkid_lsblk.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Correct to the final instruction of my last comment:
At this point if "ls -l /dev/mapper/" now does show the LVM ** ubuntu
--vg-root ** node for the root file-system you can try to continue the
boot by pressing Ctrl+D or typing "exit". If those don't help then re-
running the entire script might
Dylan: I've updated the bug description to describe the situation as we
left it.
There is a test I'd like you to do which involves forcing a break in
initrd processing and dropping to the shell before the cryptsetup
prompt.
Once there I'd like you to verify the NVME device is visible along with
** Description changed:
I worked with "TJ-" on Ubuntu IRC (#ubuntu) on April 27th in order to
debug this. On a new Ubuntu 18.04 installation, it is not possible to
decrypt the volume when it's installed on an NVMe device with the
encryption selected. Changing the device-m
** Also affects: cryptsetup (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cryptsetup (Ubuntu)
Status: New => In Progress
** Changed in: cryptsetup (Ubuntu)
Assignee: (unassigned) => TJ (tj)
** Changed in: cryptsetup (Ubuntu)
Importance: Undecided =>
** Changed in: avahi (Ubuntu)
Status: Confirmed => Triaged
** Changed in: avahi (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/831022
Title:
avahi
This is still affecting 18.04, I've added a link to an upstream bug
report.
** Bug watch added: github.com/lathiat/avahi/issues #176
https://github.com/lathiat/avahi/issues/176
** Also affects: avahi via
https://github.com/lathiat/avahi/issues/176
Importance: Unknown
Status:
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Status: New => Confirmed
** Changed in: qemu (Ubuntu)
Milestone: None => ubuntu-16.04.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
On 16.04 and 18.04 hosts on my LAN I've been suffering intermittent loss
of mDNS resolution after devices have been suspended and resumed.
Today I decided to investigate and noticed that on resume the hostname
being advertised is changed.
E.g.
hephaestion.local == Cold
** Changed in: systemtap (Ubuntu)
Status: New => In Progress
** Changed in: systemtap (Ubuntu)
Assignee: (unassigned) => TJ (tj)
** Changed in: systemtap (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bu
Public bug reported:
apt-cache policy apt
apt:
Installed: 1.6~beta1
Candidate: 1.6~beta1
Version table:
*** 1.6~beta1 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
Whilst trying to use virt-manager it reported requiring
It turns out when using:
apt-get install --reinstall --install-recommends virt-manager
the --install-recommends is ignored!
Reporting this as a possible bug in apt.
** Changed in: virt-manager (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you
This is still a problem on 18.04.
tj / tmp apt list virt-* --installed
Listing... Done
virt-manager/bionic,bionic,now 1:1.5.0-0ubuntu1 all [installed]
virt-viewer/bionic,now 6.0-2 amd64 [installed,automatic]
tj / tmp apt list *spice* --installed
Listing... Done
libspice-client-glib
Public bug reported:
apt-cache policy grub2-common
grub2-common:
Installed: 2.02-2ubuntu8
Candidate: 2.02-2ubuntu8
Version table:
*** 2.02-2ubuntu8 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
Setting /etc/default/grub
Public bug reported:
apt-cache policy console-setup
console-setup:
Installed: 1.178ubuntu1
Candidate: 1.178ubuntu1
Version table:
*** 1.178ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
500 http://gb.archive.ubuntu.com/ubuntu bionic/main i386
User reports the issue now occurs in GRUB too so it looks like a
hardware issue. User also reports the keyboard on the laptop has been
previously damaged due to drops.
** Changed in: linux (Ubuntu)
Assignee: TJ (tj) => (unassigned)
** Changed in: linux (Ubuntu)
Status: Tria
I've done some extensive debugging with the reporter on this.
It's important to note two things:
1. BIOS Setup isn't affected
2. GRUB shell isn't affected
Which suggests it is kernel, possibly ACPI table, related.
We've done a lot of testing with various i8042. options including
adding
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => TJ (tj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
** Also affects: ubuntu-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/1752417
Title:
Out of the box, Ubuntu Bionic offers only insecure VPN
I'd concur and suggest that as so many people use openvpn for 'Private
Internet Access' that would be a far more appropriate out-of-the-box VPN
add-on to ship.
That obviously has implications because it would require adding openvpn
to the seed.
PPTP is, I think, a hold over from the dial-up ISP
** Attachment added: "/boot/efi/EFI/ubuntu/grub.cfg"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1761336/+attachment/5102048/+files/efi_ubuntu_grub.cfg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
** Changed in: grub2 (Ubuntu)
Importance: Undecided => Low
** Attachment added: "efibootmgr -v"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1761336/+attachment/5102045/+files/efibootmgr.log
--
You received this bug
** Attachment added: "lsblk -f"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1761336/+attachment/5102046/+files/lsblk-f.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761336
Title:
** Attachment added: "find /boot/efi -ls"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1761336/+attachment/5102047/+files/find_boot_efi.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
301 - 400 of 2979 matches
Mail list logo
