This breaks a postfwd script I use to prevent botnets using my mail
server.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904797
Title:
geoipupdate fails with 40` HTML error
To manage
Updated to snapd-glib 1.58-0ubuntu0.20.04.0 on focal and all
dependencies are working.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Updated to snapd-glib 1.58-0ubuntu0.20.10.0 on groovy and all
dependencies are working.
** Tags removed: verification-needed-groovy
** Tags added: verification-dine-groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've looked through all the stacks of running processes and can't see
anything that looks tpg / iscsi related present that could be holding
the mutex - at least per
https://github.com/torvalds/linux/blob/818dbde78e0f4f11c9f804c36913a7ccfc2e87ad
- but perhaps the Ubuntu kernel has some patch that
Public bug reported:
I have a block device exported from zfs, and from time to time it drops
off the network, after which operations such as targetctl restore will
hang.
When it hangs it is stuck in core_tpg_del_initiator_node_acl:
```
[<0>] core_tpg_del_initiator_node_acl+0x8e/0x120
Public bug reported:
$ lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
Trying to install sabnzbdplus, which uses this version of cherrypy3:
Nov 12 20:53:09 NAS systemd[1]: Starting LSB: SABnzbd+ binary newsgrabber...
Nov 12 20:53:09 NAS sabnzbdplus[740067]: * Starting
** Changed in: snapd-glib (Ubuntu Bionic)
Status: Triaged => 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/1903936
Title:
Update to 1.58
To manage notifications about this bug
** Changed in: snapd-glib (Ubuntu Bionic)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866574
Title:
Update to 1.56
To manage notifications about this bug go
signee: (unassigned) => Robert Ancell (robert-ancell)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903936
Title:
Update to 1.58
To manage notifications about this bug go to:
https://bugs.laun
** Changed in: snapd-glib (Ubuntu Groovy)
Status: New => Fix Committed
** Changed in: snapd-glib (Ubuntu Focal)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
regression tests.
** Affects: snapd-glib (Ubuntu)
Importance: Medium
Assignee: Robert Ancell (robert-ancell)
Status: Fix Released
** Affects: snapd-glib (Ubuntu Focal)
Importance: Medium
Assignee: Robert Ancell (robert-ancell)
Status: New
** Affects: snapd-glib
Looks like the same issue kcompactd and btrfs-transaction locking up.
Can not immediately reproduce, seemingly takes ~2weeks to appear. More
problematic systems generally also have higher disk i/o, all btrfs.
%Cpu0 : 3.8 us, 1.3 sy, 0.0 ni, 0.0 id, 94.9 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu1
** Bug watch added: gitlab.gnome.org/GNOME/gnome-system-monitor/-/issues #46
https://gitlab.gnome.org/GNOME/gnome-system-monitor/-/issues/46
** Also affects: libgtop via
https://gitlab.gnome.org/GNOME/gnome-system-monitor/-/issues/46
Importance: Unknown
Status: Unknown
** Changed
This issue is a known one in GNOME System monitor, and is fixed with
3.36.1 release of GNOME System Monitor. Hence Ubuntu and Mint should
push the the 3.36.1 release to their repositories to fix this issue.
** Also affects: libgtop via
Public bug reported:
I tried to re-install Ubuntu 18.04 because I was getting a series of:
ima: Error Communicating to TPM chip
messages on start-up and then the system would loop on the dots start-up screen.
I was able to Ctrl-D to get a command line and run grub-update to refresh the
grub
Public bug reported:
Installation went well until it got to the point of installing the grub
loader.This failed. Fatal error.Have tried to report.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname:
Public bug reported:
Just trying to upgrade Ubuntu 18.04 to 20.04 on an Amazon AWS EC2
instance.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: mysql-server-8.0 8.0.22-0ubuntu0.20.04.2
ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
Public bug reported:
could not update to new version
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.28
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
Public bug reported:
This is the third time.
ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: chromium-browser (not installed)
ProcVersionSignature: Ubuntu 5.8.0-1006.9-raspi 5.8.14
Uname: Linux 5.8.0-1006-raspi aarch64
ApportVersion: 2.20.11-0ubuntu50
AptOrdering:
** Also affects: livecd-rootfs (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: open-vm-tools (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: livecd-rootfs (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects:
I can manually import the certificates into the browser, but I do not
want to do this. Especially not on a multi-user system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901586
Title:
[snap] CA
Public bug reported:
Upgrader fails with error unable to calculate size of upgrade. None of
the "Others Apply" categories apply.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.40
ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
Uname:
Public bug reported:
We have a company internal CA and placed its root CA certificate in
/usr/local/share/ca-certificates and ran update-ca-certificates. This
always worked for chromium based browsers.
With chromium-browser as snap in Ubuntu 20.04 this seems to not work any
more. Chromium
The issue occurs under both xorg and wayland sessions.
Here is the journalctl output:
$ journalctl -b 1
Hint: You are currently not seeing messages from other users and the system.
Users in groups 'adm', 'systemd-journal' can see all messages.
Pass -q to turn off this notice.
-- Logs
dev
wget
http://downloads.sourceforge.net/project/libmtp/libmtp/1.1.16/libmtp-1.1.16.tar.gz
tar xzf libmtp-1.1.16.tar.gz
cd libmtp-1.1.16
./configure
make
sudo make install
Before I reinstall mtp-tools (1.1.13-1), maybe have something to do ?
Best regards,
Robert
--
Yo
Public bug reported:
Whenever I drag a file from a desktop and move it to the nautilus folder
window, the system freezes and I can't do anything, just moving the
mouse.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: nautilus 1:3.38.1-1ubuntu1
ProcVersionSignature: Ubuntu
Public bug reported:
I have this error and other errors as a result of the loss of my HDMI
audio driver from my AMD HD Radeon 6570 video card on Ubuntu 16.04 LTS.
There are a number of kernels that can't update. I'm stuck with a
partial upgrade with many errors all because the HDMI audio driver
** Description changed:
We have a cloud-images qualification test for google startup scripts to
ensure that cloud-init customizations are available before the user
startup script is run. That test is failing and investigation shows
that we have a functional regression from
** Bug watch added: github.com/GoogleCloudPlatform/guest-agent/issues #84
https://github.com/GoogleCloudPlatform/guest-agent/issues/84
** Also affects: google-guest-agent via
https://github.com/GoogleCloudPlatform/guest-agent/issues/84
Importance: Unknown
Status: Unknown
--
You
Public bug reported:
We have a cloud-images qualification test for google startup scripts to
ensure that cloud-init customizations are available before the user
startup script is run. That test is failing and investigation shows
that we have a functional regression from
Public bug reported:
Désolé mais le texte du message d'erreur n'est plus visible. Il
semblerait de mémoire que l'erreur concerne grub
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubiquity 20.10.10
ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
Uname: Linux 5.8.0-20-generic
I am not an Ubuntu guru. I would love to but do not know how. I am
willing to waste more time in an attempt to help find the bug in Ubuntu,
but I meed instructions on HOW to do what you want.
Robert Pearson
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
/dev/snd/controlC1: robert 2340 F pulseaudio
/dev/snd/controlC0: robert 2340 F pulseaudio
CurrentDesktop: MATE
Date: Wed Oct 14 21:04:17 2020
InstallationDate: Installed on 2019-12-22 (297 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Rele
Now that the status is Confirmed, does this mean that somebody is going
to actually try and fix the broken code?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899388
Title:
Ubuntu 20.04 broke WiFi
Public bug reported:
On Ubuntu 20.04.1 LTS, glibc-2.31:
gcvt() will output no more than 17 digits of precision.
qgcvt() will output no more than 21 digits of precision.
Here is the demo :
//
#include
#include
int main(void) {
char ebuf[80];
down. When will you release a version that knows about WiFi
networks?
Robert Pearson
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-118-generic 4.15.0-118.119
ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18
Uname: Linux 4.15.0-118-generic x86_64
ApportVersion
Also click here to restore hidden windows only restores 1 window, not
all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899366
Title:
Ubuntu MATE 10.04 released prematurely
To manage
This computer currently has Ubuntu 18.04 LTS and Ubuntu 18.04.05 LTS
(18.04) on it. What would you like to do?
I did not know about the 18.04.05. !?!?!?!?!?
My second disk is partitioned as Free Space 2.1MB, UEFI System Partition
589MB FAT, Ubuntu 451GB Ext4, Swap 8.4GB Ext4, and 3.5TB NTFS with
Public bug reported:
The first time I tried to install 20.04 I noticed that the option to
update as installed was disabled. However since the ubuntu coders do NOT
BELIEVE in separating code and data, I stopped the installation and made
a backup of /home/robert. (I never place data here but Ubuntu
I guess the next step would be to confirm that upgrading to Qemu 5.0
solves the problem. I'll try that either by directly compiling 5.0, or
I'll wait until november when I will upgrade to Groovy.
However, I doubt it will really solve the problem, now I tend to stick
to the idea that the problem
Public bug reported:
When I upgraded to 20.10 beta evolution wouldn't connect to the google
calendars of any of the accounts that I setup in the settings online
accounts. I was able to add them through the evolution accounts mail
accounts options and that worked. I tried removing the accounts
** Package changed: ubuntu => sddm-kcm (Ubuntu)
** Description changed:
1) Kubuntu 20.04.1 LTS
2) ?
Steps to reproduce:
- use sddm as display manager
- start kcmshell5 user_manager
- Set autologin option for current user
- Create a new user with administrative privileges, but
Hello Christian,
I should have pointed that the log is from the Android system, not Qemu
or my host system !
I got the failure message running the following command in an Android
shell :
logcat '*:F'
(which means display log entries from all facilities (*), with the Fatal
(F) severity)
It
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: robert 2325 F pulseaudio
/dev/snd/controlC1: robert 2325 F pulseaudio
CurrentDesktop: MATE
Date: Tue Oct 6 18:39:14 2020
InstallationDate: Installed on 2019-12-22 (289 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS
Public bug reported:
Doing a global search-and-replace of
\s+
with
with regular expression (virtually useless) on and \n char off causes Pluma to
crash.
P.S. the search and replace previously reported with \1 still does not work
making the RE mode virtually useless.
ProblemType: Bug
-generic 4.15.18
Uname: Linux 4.15.0-118-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: robert 2325 F pulseaudio
/dev/snd/controlC1: robert 2325 F pulseaudio
CurrentDesktop: MATE
Date: Tue Oct
Public bug reported:
1) Kubuntu 20.04.1 LTS
2) ?
Steps to reproduce:
- use sddm as display manager
- start kcmshell5 user_manager
- Set autologin option for current user
- Create a new user with administrative privileges, but without autologin
- Login with the new user account
- Delete the user
Hi Paride,
Sorry about that, they probably block direct linking.
Try that link instead : https://www.fosshub.com/Android-x86.html
Then, choose the "Android-x86 64-bit ISO file", version "9.0-r2". If it
still doesn't work, you could try the Android-x86 project web site :
Why don't you just flag all new bugs as "ignored", since I have never
seen any activity to actually fix any bugs.
When my company bought a system with Unix System V on it, I got a book
of known bugs. There were over 500 pages with two pages/page of known
bugs. The catch is that AT never attempted
Hi Christian,
Fairly easy to reproduce. I just tried with current qemu (version 4.2.1
(Debian 1:4.2-3ubuntu6.6)).
You need to download the Android 9.0r2 ISO image from the Android-x86
project. Here's a link for the 64-bit image (I chose the non k49 one) :
Public bug reported:
if you can tell me how to get hard dives out of read only that would be very
helpful
thanks
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
Here's a novel idea:
Why not actually try to fix the bugs rather than just classifying them
as "Expired".
Or why not be honest and just flag all new bugs as "Expired" so we users
won't waste our time posting bug reports.
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
To quote "EPUB 3 Best Practices"
The specification for this is the Open Container Format (OCF) 3.0, and it is
literally a .zip file,
though it uses the .epub extension.
Apparently the coder decided checking the extension was easier than
actually looking in the file and
Ubuntu bionic affected with old
https://launchpad.net/ubuntu/+source/wget/1.19.4-1ubuntu2.2 pkg.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861440
Title:
[upstream regression] wget does not
Its fixed in https://launchpad.net/ubuntu/+source/wget/1.20.3-1ubuntu1.
Can you backport this to ubuntu bionic please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861440
Title:
[upstream
Oops, I thought it was in universe. This is not required then.
** Changed in: libselinux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892455
Title:
- libselinux is already in main, that was my mistake thinking it was in
universe.
- Only the binary package libostree-1-1 is required to be in main. The reset
can remain in universe.
** Description changed:
Many applications have Flatpak integration using libflatpak. The Ubuntu
desktop
I found the proper area to update the tags (it was not obvious, at least
to me) and have changed it to 'verification-done-focal' as requested.
If anyone else can verify this has been done correctly, that would be
much appreciated (I would hate to see this change reverted).
Thank you!
** Tags
I am trying to follow the directions in the automated comment #68 -->
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875199/comments/68
however I am unsure of how to change the status of this issue to
properly confirm the fix. If anyone else could provide some additional
guidance (or
I can confirm that when using the updated 'proposed' kernel (version
5.4.0-49-generic) that audio output works properly on my Intel NUC8CCHK
test system.
Thank you to everyone that helped identify and fix this issue, your
efforts are much appreciated.
--
You received this bug notification
I switched to Focal in May and the bug is still there. The EDID
workaround still works.
I must be the only one switching to 40Hz sometimes, or it only affects
my GPU, which I doubt (Intel HD Graphics 4600, CPU Core i7-4710MQ).
--
You received this bug notification because you are a member of
** Tags added: eoan focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848746
Title:
Refresh rate change requests to 40Hz are "adjusted" back to 60Hz
To manage notifications about this bug go
When my company first got Unix, they included a book of known errors. I
say book because it was over 200 pages, each page contained two actual
pages of known bugs. The thing is, they list the bugs but no one assumes
responsibility to actually FIX a bug. One thing Linux inherited from
Unix. DON'T
I've tried the patch, and it fixes the problem for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871308
Title:
Failed to start Notification regarding a crash report
To manage notifications
Public bug reported:
Disabling SDL support may have its reasons, but I guess that means I may
be the only one using the virglrenderer library, because it has problems
running with the GTK frontend.
I've been emulating an Android 9.0 device since Eoan, and it took me
some time to understand
Hi Paride,
I verified the crash issue does exist in core20 snap on the edge channel. To be
precise, the revisions I tried are 823 for amd64 and 826 for armhf.
So I think we can close this bug.
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Having the same problem Bug #1894125
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894017
Title:
Keyboard not working
To manage notifications about this bug go to:
i upgraded from disco to focal by changing that word in /etc/apt/sources
;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882369
Title:
package grub-pc 2.04-1ubuntu12.2 failed to install/upgrade:
@chad.smith I have used the cloud-utils in your ppa to build Xenial
maas-images on a bionic host to confirm that things are working now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1493188
Title:
Public bug reported:
changed disco to focal in /etc/apt/sources.list !!
1765 packages total in 3GB to update!!!
should I just wipe and new-install??? ;-)
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: friendly-recovery 0.2.41
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
I have btrfs! why did apt upgrade hold back 180 files when 1765 just upgraded??
Why did Aptitude suggest (and I accepted) that more upgrade?
Why include zfs ;-(
apt remove zfs?? thanks in advance. srn
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1894125/+attachment/5408376/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894125
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1894125/+attachment/5408378/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894125
Title:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1894125/+attachment/5408367/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894125
Title:
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1894125/+attachment/5408377/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894125
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1894125/+attachment/5408366/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894125
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1894125/+attachment/5408369/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894125
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1894125/+attachment/5408380/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894125
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1894125/+attachment/5408379/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894125
Title:
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1894125/+attachment/5408364/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894125
Title:
[Acer
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1894125/+attachment/5408373/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1894125/+attachment/5408371/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894125
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1894125/+attachment/5408365/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1894125/+attachment/5408375/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1894125/+attachment/5408370/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894125
Title:
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1894125/+attachment/5408374/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894125
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1894125/+attachment/5408372/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894125
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1894125/+attachment/5408368/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894125
fine
Rebooting to 5.0.4.42 mouse pad and keyboard work fine
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.8
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: robert 4597 F pulseaudio
+ CasperMD5CheckResult: skip
** Changed in: ostree (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892454
Title:
[MIR] libostree-1-1
To manage notifications about this bug go to:
With the move to Bionic host kernels on the builders, the Xenial MAAS
images fail to build. This is because cloud-utils mount-image-callback
remains unfixed in Xenial while the Bionic kernel does not have the
overlayfs kernel module. The following patch at minimum is required in
Xenial:
** Package changed: ubuntu => gdm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894125
Title:
Mousepad + Keyboard not working after update
To manage notifications about this bug go to:
Public bug reported:
Updating my Acer laptop ES511 ( Ubuntu 20.04) from 5.0.4.42 to 5.0.4.45
keyboard and mouse not working - gets to login page but cannot click on user
or type in password, if connect USB mouse and keyboard it works fine
Rebooting to 5.0.4.42 mouse pad and keyboard work
Thank you for the bug report. I have confirmed this issue and flagged
the correct project, livecd-rootfs, for this work.
** Changed in: livecd-rootfs (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-images
Status: New => Confirmed
** Changed in: livecd-rootfs (Ubuntu)
So we need to fix livecd-rootfs to correctly add the tools version field
to the vmdk header *and* add a check that it got there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893898
Title:
But that function is sed'ing the file created by python3-vmdkstream so
we'll look into it. The vmdk-stream-converter source package has had a
minor change between focal and groovy but it doesn't explain this issue.
** Also affects: cloud-images
Importance: Undecided
Status: New
--
Okay, the vmdk lacks the version in bionic, focal, and groovy. The
ddb.comment field that toolsVersion uses is missing:
# Disk Descriptor File
# Created by VMDKstream
version=1
CID=7e5b80a7
parentCID=
createType="streamOptimized"
# Extent description
RDONLY 20971520 SPARSE
The OVA we're providing[1] is built with this[2] binary hook in livecd-
rootfs which wraps up the VMDK created using the create_vmdk[3]
function. That function calls modify_vmdk_header to set the tools
version; this code is unchanged from when it was added in early 2017.
[1]
Public bug reported:
They seem to pair ok, but don't show up as sound hardware, either
microphone or speaker/headphones.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic
Ouch, sorry and thanks for that!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893021
Title:
Flash plugin symbol lookup error with firefox 80.0+build2 on xenial
(gtk_window_set_titlebar)
To
601 - 700 of 37075 matches
Mail list logo
