This bug was fixed in the package rust-dotenv - 0.15.0-2build1
---
rust-dotenv (0.15.0-2build1) groovy; urgency=high
* No change rebuild to remove /usr/.crates2.json (LP: #1868517).
-- Julian Andres Klode Wed, 06 May 2020 13:21:24
+0200
** Changed in: rust-dotenv (Ubuntu)
It is the build phase that fails.
Reproduced in armhf container on canonistack.
1. get the source and build deps
2. build that until it breaks
3. re-run via
$ cd ~/chrony-3.5/test/system
$ ./run -i 20 -m 2
In this repro environment I get two extra fails at:
005-scfilter Testing system
Public bug reported:
Was using jackd2 for ages, never had this issue. The usual limits.conf
tweaks are present. Jackd won't run in realtime even as root. It's very
easy to reproduce in Focal.
Before upgrade, was working:
Ubuntu 18.04.4 LTS
uname -r
kernel 5.3.0-51-generic
jackd --version
jackdmp
Add apport-collect 1876963 saved as a file attachment to bug report
** 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/1876963
Title:
apport-collect 1876963 saved to file - unable to send wifi too slow
** Attachment added: "apport-collect 1876963 saved to file - unable to send
wifi too slow"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876963/+attachment/5367397/+files/apport.linux.7id7fsgb.apport
--
You
** Attachment added: "intermediate gcc file - bad case"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1847361/+attachment/5367307/+files/file-posix.i.bad
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
bionic:
ubuntu@lp1839290-b:~$ dpkg -l systemd|grep systemd
ii systemd237-3ubuntu10.39 amd64system and service manager
ubuntu@lp1839290-b:~$ systemctl cat foo
# /etc/systemd/system/foo.service
[Unit]
PartOf=bar.service
[Service]
ExecStart=/bin/sleep infinity
RestartSec=0s
I was going into a bionic VM and bulding the former built .23 version.
In that environment I can compile file-posix.c.
The simplified call works in that VM:
$ gcc -Iblock -I. -I/home/ubuntu/qemu-2.11+dfsg
-I/home/ubuntu/qemu-2.11+dfsg/include -pthread -I/usr/include/glib-2.0
@vmc, I've noticed the same with nvme, or at least not slower. It slowed
after the last update for 20.04 and updating the kernel to 5.40.0-29
however. it was almost 5 seconds faster with version -28
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Good and bad system run the same
abe91699d25bc563c77de9ff5d716fb5
/usr/include/x86_64-linux-gnu/asm/bitsperlong.h
But they differ in
c6fb5761f50f398f66acd3b6cf3e2bcc /usr/include/linux/swab.h (bad)
1b3e767d11860a5eee41c8ea87b60c03 /usr/include/linux/swab.h (good)
Since this is very close to
** Summary changed:
- [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04
+ [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see comment
93)
** Tags added: fixed-in-3.34.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
There are a few offsets changed which do not matter.
What is left is:
$ diff -Naur file-posix.i.good file-posix.i.bad
--- file-posix.i.good 2020-05-06 13:42:04.936368109 +0200
+++ file-posix.i.bad2020-05-06 13:46:23.573406190 +0200
@@ -69470,6 +69470,9 @@
/* SPDX-License-Identifier:
xenial:
ubuntu@lp1839290-x:~$ dpkg -l systemd|grep systemd
ii systemd229-4ubuntu21.27 amd64system and service manager
ubuntu@lp1839290-x:~$ systemctl cat foo
# /etc/systemd/system/foo.service
# /etc/systemd/system/foo.service
[Unit]
PartOf=bar.service
[Service]
** Attachment added: "intermediate gcc file - good case"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1847361/+attachment/5367309/+files/file-posix.i.good
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It also was found that the compiler versions changed:
good build 7.4.0-1ubuntu1~18.04.1
bad build 7.5.0-3ubuntu1~18.04
Since it is easier available I first tried the one in 18.04-release.
v="7.3.0-16ubuntu3";
v2="4:7.3.0-3ubuntu2";
apt install cpp-7=$v g++-7=$v gcc-7=$v gcc-7-base=$v
** Attachment added: "intermediate gcc file - good case (improved)"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1847361/+attachment/5367319/+files/file-posix.i.good
** Attachment removed: "intermediate gcc file - good case (improved)"
It was suggested to use -save-temps (thanks danpb) and comparing the -i
files.
The following is from:
$ gcc -Iblock -I. -I/build/qemu-D0lqny/qemu-2.11+dfsg
-I/build/qemu-D0lqny/qemu-2.11+dfsg/include -pthread -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -D_GNU_SOURCE
@seppel Can you try if the patch https://lore.kernel.org/linux-
gpio/20200424091201.568-1-caizhaop...@uniontech.com/ fixes an issue?
--
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:
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: apport (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: apport (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: apport (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: apport (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: apport (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: apport (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
Changing status to new as this bug is affecting me. It's been around 6 days, I
have tried installing Ubuntu 20.04, 19.04 with no success and then I tried
16.04 in which I got this "ubi-partman crashes with exit code 141" error.
My system details:
Trying to dual boot with Windows 10
HP pavilion
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/757720
Title:
I just tested rc4, and now I can no longer log in; same as with rc2. So
to summarize, I cannot get past the login screen with versions rc2 and
rc4, whereas I could with rc3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member
Ha, that was a good red-herring
It doesn't fail at this test despite all the error messages thrown out.
It does
1. build chrony without root (works with tests skipped as it isn't root)
2. passes other tests as it ERRORs but detects that the environment is the
reason for that
The actual error
And here we have the trigger:
$ diff -Naur swab.h.4.15.0-99.100.good swab.h.4.15.0-100.101.bad
--- swab.h.4.15.0-99.100.good 2020-05-06 13:56:28.755885666 +0200
+++ swab.h.4.15.0-100.101.bad 2020-05-06 13:55:39.191681069 +0200
@@ -4,6 +4,7 @@
#include
+#include
#include
/*
@@
Public bug reported:
Issue exists on xenial in python3-paste 1.7.5.1-6ubuntu3 which throws
exception:
File "/usr/lib/python3/dist-packages/paste/httpserver.py", line 1068, in
process_request_in_thread
self.finish_request(request, client_address)
File
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: apport (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: apport (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member
> But on the other side, developers are forced to discontinue the support for a
> stable Ubuntu LTS
>like 18.04, because there are no updates which are necessary to run the
>application without the
> newest bugfixes.
It's the choice of the developer, mainstream application writers usually
don't
Thx for the reply, closing this ticket.
I'll set it to Fix Released, since I think this worked with the latest update.
** Changed in: ubuntu-z-systems
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
no worry, maybe it does fail but in more specific cases than the one
tested there? anyway, closing for now but feel free to re-open if you
get the issue again and can pin specific condition to trigger the bug
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Invalid
--
You received
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a
Updated to Ubuntu 20.04 and still this issue: very limited zoom in
Evince PDF.
Will this bug ever been fixed (15 years old) or will we have to apply
the aforementioned fix on every update?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: apport (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: apport (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: apport (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member
This problem still exists in Ubuntu 20.04 Desktop. Selecting either
"primary" or "logical" partition types works fine, but the distinction
is meaningless for GPT, and asking for the partition type could be
confusing to users who aren't expecting it -- they might not understand
the difference or
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member
Thanks for the update Rod.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1330021
Title:
custom installation on GPT partitioned disks refers to Primary &
Logical partitions
To manage
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
After i managed to reboot (REISUB). I've look at dmesg log, and at the
end of the log theres an error for the last boot
24.340774] kernel: amdgpu :04:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x address=0x4a68002a0 flags=0x0070].
So i added iommu=soft to the grub.cfg and reboot
Public bug reported:
When testing development kernels I usually rely on the installkernel
script either through the "make install" target of the Kernel source
or manually. This used to work great on Ubuntu on Z.
On Ubuntu 20.04 (freshly installed up to date) this fails however because
>From the arm qemu wiki:
https://wiki.qemu.org/Documentation/Platforms/ARM
vns seems works and require as:
virt machine graphics
Graphics is also available, but unlike x86 there is no default display
device enabled: you should select on from the Display devices section of
"-device ?". One good
After reading https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx
filed the bug under linux package instead of b43-fwcutter since suspect
the issue is with the b43 driverand not the firmware installer
** Package changed: b43-fwcutter (Ubuntu) => linux (Ubuntu)
--
You received this bug
Dear All
It would be very helpful to point out which fingerprint readers are
supported. It would also be an advantage if the relevant online
resources were referred to in the event of problems.
See attachment too.
Thank you for your help, Kind regards, Laszlo
** Attachment added:
Thanks for the detail, indeed it has the wrong bug depends on libidn, I
reported that to Debian now
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959868
I've also tested a build in a ppa, https://launchpad.net/~ubuntu-
desktop/+archive/ubuntu/ppa/+build/19267763 and indeed your testcase
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Kernel
Team (canonical-kernel-team)
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug
The commend link for qemu which created by nova compute, the vcn parameter are:
-vnc 0.0.0.0:0 -k en-us -device
virtio-gpu-pci,id=video0,max_outputs=1,bus=pci.5,addr=0x0
ubuntu@hc3:~$ ps auxww |grep -i qemu
libvirt+ 1157628 3.6 0.1 5691124 737996 ? Sl 04:34 1:21 qemu-system-aarch64
-enable-kvm
For 18.04.2 ga-kernel of Linux hc3 4.15.0-47-generic, the CONFIG_DRM=y
and CONFIG_DRM_VIRTIO_GPU=y seems already set. Test with drm virtio-gpu
modules load, it seems same. I tested by delete instance via dashboard
and create it again on the same hc3.maas host.
For the virt-manager still display
Public bug reported:
Qemu vnc console can only show "no suitable video mode" and nothing else
both on opensack dashboard (vnc) or virt-manager. This was tested on
Taishan2280 server (D05).
Please see attached screen shoot.
** Affects: ubuntu
Importance: Undecided
Status: New
--
the out put of "virsh dumpxml"
...
...
This should be OpenStack configured for VNC and qemu devices. If I
manual remove them, and the virt-manager can become normally which show
grub menu, boot message and login etc.
--
You received this bug
** Summary changed:
- installkernel script does not symlink /boot/initrd.img which is required with
the default zipl.conf
+ [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which
is required with the default zipl.conf
--
You received this bug notification because you are
Thank you for your bug report, I can't confirm that with that testcase
* create a directory 'original'
* create 3 empty files in there, a b c
* create a directory 'destination'
* create an empty file 'b' there
ctrl-X the 3 files in the original
ctrl-V to copy
select 'apply to all the action'
error screen picture
** Attachment added: "error screen picuture"
https://bugs.launchpad.net/ubuntu/+bug/1877083/+attachment/5367295/+files/qemu-vnc-error-in-dashboard.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
qemu error sceen shot via virt-manager
** Attachment added: "qemu error sceen shot via virt-manager"
https://bugs.launchpad.net/ubuntu/+bug/1877083/+attachment/5367297/+files/qemu-vn-error-via-virt-manager.png
--
You received this bug notification because you are a member of Ubuntu
Bugs,
501 - 600 of 984 matches
Mail list logo
