Public bug reported:
I upgraded my Ubuntu 20.04 LTS to 22.04 LTS using do-release-upgrade -d command
on 2022/05/20
And then my external monitor, who worked well before on 20.04 LTS, was never
able to connect.
Everytime I try to connect it, set Joint Displays and press apply on the
setting
Yes, unfortunately the network work was deferred, its still a wip but is
not scheduled as a work item for the cycle. With that said we still hope
to get this fixed, I just can't promise it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I have the same issue, plus I couldn't share resource between the VMWare
and Windows. I had to update vmware-tools-desktop. The rendering did not
fix though.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qtbase-opensource-src (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mutter (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it, because your description
didn't include enough information. You may find it helpful to read 'How
to report bugs effectively'
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html.
Another thing i just tried:
I thought *maybe* this problem is because I was running a custom built
mainline kernel and the drivers GUI doesnt want to change a system with
non-original Ubuntu kernel, but I just rebooted in the standard generic
kernel and the problem persists.
--
You received
ok, sorry it took some time as I was debugging another issue...
Now i would like to go back to the state where nvidia drivers are not
installed and they do not get installed as described so i can create the
debug output, but due to this bug i just reported, I cannot change this
state currently:
oh and forgot to say: actiually the same goes for all other nvidia
driver versions that are shown in the list - its about 10 of them.
Whatever i select, the apply button is inactive.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
I want to switch back from the nvidia driver to nouveau.
In the dialog the last row lets me select the Nouveau driver, but the
"apply" button is inactive and doesnt let me apply the change.
There is also no message or anything that would allow me to understand,
why this is
(In reply to she...@liang.at from comment #603)
> Hi all,
> I'm facing the same problem with my Lenovo Legion 7. I'm running Ubuntu
> 20.04.4 LTS and am not very familiar with kernels. I tried finding the linux
> source folder/directory, open the file: sound/pci/hda/patch_realtek.c but I
> don't
Seems like this is the best way to do it (but if someone knows of a better way
for Ubuntu, let us know):
https://sleeplessbeastie.eu/2021/11/01/how-to-install-mainline-linux-kernel-on-ubuntu-based-distribution/
Seems this gets you a tool that allows you to manage and install
mainline kernels.
So maybe for all not used to build kernel modules you may give that a try:
(sorry a comment describing that was 409)
# install hda-verb
# hopefully I have found the correct one
sudo apt-get install alsa-tools
# get applyverb.py
https://github.com/ryanprescott/realtek-verb-tools
# get the verbs
According to your alsa-info, you have the already supported 16ACHg6
which is supported in the latest versions of the kernel.
There should be a repo you can add on your system to be able to pull the
latest mainline kernels. I don't have it handy at the moment as I've
been building/installing
Created attachment 301012
attachment-29335-0.html
I am currently out of the office on holiday I will be returning on
Monday June 6, I will have limited access to email.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Hi all,
I'm facing the same problem with my Lenovo Legion 7. I'm running Ubuntu 20.04.4
LTS and am not very familiar with kernels. I tried finding the linux source
folder/directory, open the file: sound/pci/hda/patch_realtek.c but I don't have
the pci folder.
Is there already a solution for
** Description changed:
[impact]
when talking to upstream nameservers, systemd-resolved limits its
advertised max packet size as 512 in its edns0 opt. However, one of the
primary benefits of edns0 is to allow using packet sizes larger than
512, which is the pre-edns0 max packet size.
** Changed in: systemd (Ubuntu Hirsute)
Status: In Progress => Won't Fix
** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Changed in: systemd (Ubuntu)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: systemd (Ubuntu Bionic)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: systemd (Ubuntu Eoan)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in:
This bug still exists in the latest Ubuntu 22.04 Live image. When I
netboot the image and apply another lower layer (NFS-based), I still
get "nfs rpc call returned error 13" in my dmesg. Intensive google
searching lead me to this thread. This bug causes the Firefox (provided
via snap) not
The input-feedback-sounds worked for me, thanks a lot Vuk, I would never
figure out that by myself.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1970047
Title:
GTK file
** Changed in: cyrus-sasl2 (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/1973760
Title:
Crash when using DIGEST-MD5 with
Can someone please tell the process of the workaround as i upgraded to
ubuntu 22.04 and can't connect to my university wifi and i can't
understand the details you guys are talking about
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
It's showing 'unknown display'.
Running this 'ubuntu-drivers devices' showed no output.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
ApportVersion:
27 matches
Mail list logo
