Thank you for your quick responce.
I figure out problem and now it is solved., using newest kernel now :)
I use combinations of different solutions on the net.
Regards
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5408948/+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/1873895
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5408943/+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/1873895
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5408942/+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/1873895
Title:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5408945/+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/1873895
Title:
** Attachment added: "apt.log"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1894962/+attachment/5408935/+files/apt.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "LightdmLog.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5408941/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873895
** Attachment added: "apt.log"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1894962/+attachment/5408937/+files/apt.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5408939/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873895
Title:
apport information
** Attachment added: "LightdmDisplayLog.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5408940/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5408938/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: MATE
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5408944/+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/1873895
Title:
Sorry, I had to finish failed upgrader before sending attachments.
** Attachment added: "main.log"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1894962/+attachment/5408936/+files/main.log
--
You received this bug notification because you are a member of Ubuntu
I think I found out what's happening.
When the machine boots, and the login screen is displayed
The sound is not immediatly initialized and working
If, when it's not yet ready, I press the cut volume/volume up/volume down
It puts the sound card and/or Pulse into a state where it gets stuck...
If
Sorry to bother, but does "fix released" mean, after updating my ubuntu
20.04 the touchpad should work? Or do I still have to install a patched
Kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Reponse to Daniel Letzeisen (dtl131)
Yes, doing that helped
And not tounching the 3 buttons immediatly after login to let Pulse and
the sound card be "ready" also avoids the problem :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Reviewed: https://review.opendev.org/750444
Committed:
https://git.openstack.org/cgit/openstack/os-brick/commit/?id=c54c41a1fd69b5c191b12a8da0eb12f2ee561f10
Submitter: Zuul
Branch:master
commit c54c41a1fd69b5c191b12a8da0eb12f2ee561f10
Author: Brian Rosmaita
Date: Tue Sep 8 11:16:52 2020
Looks to me like the systemd-fsckd test is just busted on focal since
2020-08-13 :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894874
Title:
[SRU] New upstream release 3.36.3
To manage
Extremely annoying bug. I need to set "Fonts"/"Scaling Factor" in Gnome
Tweaks to 0.99 and back to 1.00 every time I re-/start my P52
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892440
Title:
*** This bug is a duplicate of bug 1893729 ***
https://bugs.launchpad.net/bugs/1893729
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of
I uploaded fwts 20.08.00-0ubuntu2 with this fix, so it's now in Groovy.
** Changed in: fwts (Ubuntu)
Status: Fix Committed => 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/1894202
I don't know if this helps, but I have experienced similar issue. Might
be a different reason, though.
1. connect phone (Oneplus 6) to computer and start large file transfer from
there (~10GB or so).
2. Insert memory card to memory card reader on the computer
3. The system is really unresponsive
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
it has nothing to do with the installation media - the system was setup
with 1910 and upgraded to 2004 - was running fine ever since, the
problem is with the mentioned kernels: not booting, no real error
message
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Running the autopkgtests for neutron and neutron-fwaas, on s390x, with a
mix of proposed and updates pockets, I have been unable to reproduce the
autopketest failure listed above. I suspect that it is a transient
failure and would retry it:
$ autopkgtest --shell-fail -U --apt-pocket=proposed
Can be found on Focal OEM 5.6 as well.
** Tags added: 5.8 focal
** Tags removed: 5.8
** Tags added: 5.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892860
Title:
af_alg07 in crypto /
If they removed a dconf hidden setting, I think it's unlikely they will go out
of their way to build it into the GUI, especially with the GNOME trend of
removing configuration/options. You'll probably get the same answer if the bug
is not considered a duplicate (i.e. "I don't think it's super
I think either of the patches is probably fine, no idea what any
upstream reviewer will prefer.
I guess it would be good to upload one of them sooner rather than later
though, to (1) unbreak dnsmasq, (2) unblock network-manager.
--
You received this bug notification because you are a member of
I was pretty much following this simple tutorial:
http://prashplus.blogspot.com/2018/01/ceph-single-node-setup-ubuntu.html
I'll try to add docker and ceph-ansible to the equation and see if I can
reproduce it.
** Changed in: zfs-linux (Ubuntu)
Status: New => In Progress
--
You received
BTW, how did you install ceph-ansible? I can't find a 20.04 package in
the ansible ppa.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881747
Title:
cephadm does not work with zfs root
To manage
** Changed in: fwts (Ubuntu)
Status: In Progress => 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/1894202
Title:
fwts 20.08.00 segmetation fault
To manage notifications about
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Hsuan-Yu Lin (shanelin)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
below commits are in v5.9-rc1, we have to backport those commits to
groovy.
09eac8277262 drm/i915/tgl+: Fix TBT DPLL fractional divider for 38.4MHz ref
clock
f153478de4b2 drm/i915/tgl+: Use the correct DP_TP_* register instances in MST
encoders
9fa6769952ee drm/i915/tgl: Add HBR and HBR2+
Thank you for the links, Sebastian and Daniel.
I've resubmitted a bug report, because the one that was turned down was
specifically about max-recents in dconf, rather than about the
functionality.
https://gitlab.gnome.org/GNOME/gedit/-/issues/357
** Bug watch added:
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
** Changed in: xorg-server (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/1894903
Title:
Thanks for the quick answer!
Any particular uperf profile that was found to be more likely/reliably to
trigger it?
I assume with driver=qemu you actually mean something like:
https://libvirt.org/formatdomain.html#network-interfaces
--
You received this bug notification because
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/openldap/+git/openldap/+merge/390398
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894838
Title:
FFe: update to
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: hwe-next
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/1874685
Title:
Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW),
All autopkgtests for the newly accepted gdm3 (3.36.3-0ubuntu0.20.04.1) for
focal have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/245.4-4ubuntu3.2 (amd64, s390x, ppc64el)
Please visit the excuses page listed below and investigate
All autopkgtests for the newly accepted gdm3 (3.36.3-0ubuntu0.20.04.1) for
focal have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/245.4-4ubuntu3.2 (amd64, s390x, ppc64el)
Please visit the excuses page listed below and investigate
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/390440
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894942
Title:
[UBUNTU 20.04] Lost virtio
At least for Groovy that seems pretty trivial.
PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4257/+packages
MP:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/390440
For consideration on SRUs for other releases please answer the questions
of comment
--- Comment From cborn...@de.ibm.com 2020-09-09 02:50 EDT---
> Hi,
> the patches LGTM and I'll make it part of the Ubuntu builds.
>
> One question thou: on one hand "occasionally end up with" sounds like this
> is almost impossible to explicitly test, but then the attached debug patch
>
Daniel, thanks for your reply.
As per your instruction, yes selecting 'Ubuntu on Wayland' solves the
issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894903
Title:
Changing orientation to
*** This bug is a duplicate of bug 1857187 ***
https://bugs.launchpad.net/bugs/1857187
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: blueman (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of
** Changed in: ubuntu-z-systems
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894942
Title:
[UBUNTU 20.04] Lost virtio host --> guest notifications cause devices
to
Public bug reported:
grub-install /dev/zd0 - failed
grub-install /dev/sda - failed
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubiquity 20.10.9
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp
I believe I just observed the same issue again, and now have a log from that
See below.
I've also come accross a simular issue here
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1699520
"plymouth --ping" is also hanging for me, I will attach a strace
First the log which happoned as I
Hi,
the patches LGTM and I'll make it part of the Ubuntu builds.
One question thou: on one hand "occasionally end up with" sounds like this is
almost impossible to explicitly test, but then the attached debug patch
suggests there might be a way to trigger this through protvirt.
But even if that
** Changed in: oem-priority
Status: In Progress => 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/1888352
Title:
use builtin dump_acpi_tables.py in hookutils
To manage
vervelover is honestly right, this is pretty embarrassing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892440
Title:
Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2
To manage
Not fixing this bug for so long, really means ubuntu doesn't care about
the desktop anymore
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892440
Title:
Shell text is too small in mutter
Hi,
you'd want to compare the lsmod and lspci output of the case that worked, you
said "If I bring up the guest using a generic image (not the kvm specific
kernal) the interface appears for SRIOV VF".
Now in this guest I'd expect the following section:
00:06.0 Ethernet controller: Intel
hey paelzer,
ah sorry
libvirt on Bionic was 4.0.0
I installed them libvirt-bin but I missed it is changed to libvirt-
daemon-system
I re-installed libvirt-daemon-system and it is 6.0.0 now,
then M -> M -> Q -> U migration is working fine.
--
You received this bug notification because you
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: alsa-driver (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/1868330
Title:
On Wed, Sep 9, 2020 at 3:20 AM Seyeong Kim <1894...@bugs.launchpad.net> wrote:
...
> but Q -> U has issue below.
>
> error: internal error: qemu unexpectedly closed the monitor:
> qemu-system-x86_64: -realtime mlock=off: warning: '-realtime mlock=...' is
> deprecated, please use '-overcommit
401 - 460 of 460 matches
Mail list logo
