Attaching a backport of the upstream fix (I applied this locally and it
solved the problem).
** Patch added: "upstream fix"
https://bugs.launchpad.net/ubuntu/+source/handbrake/+bug/2070106/+attachment/5791413/+files/Fix-file-filter.patch
--
You received this bug notification because you are
Public bug reported:
The handbrake GTK dialog filters out device files, so DVDs can no longer
be selected. This issue has been fixed upstream:
https://github.com/HandBrake/HandBrake/pull/5666/
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: handbrake 1.7.2+ds1-1build2
ProcVersionSignature:
I'm upstream. I saw the removal first in the release notes. Yet I'm
not surprised by removal. The contributions to pptp and pptpd have
declined, so the release cadence has slowed as well (1.4.0 in 2013, but
a few commits in git since). Number of people asking for help has also
declined. Some
Public bug reported:
Enabling linux bridging, via netplan, whilst using an OSA card on the
s390x architecture causes large amounts of packets to be received on the
sending interface. This behaviour is not seen while using other types of
network card on a Z, and is also not seen on any other
I also noticed this issue with the latest Ubuntu 22.04 amd64 release
image (ami-09d56f8956ab235b3). It does not have "bpf" in CONFIG_LSM.
root@:/home/ubuntu# uname -a
Linux 5.15.0-1004-aws #6-Ubuntu SMP Thu Mar 31 09:44:20 UTC 2022 x86_64
x86_64 x86_64 GNU/Linux
root@:/home/ubuntu#
*** This bug is a duplicate of bug 1937056 ***
https://bugs.launchpad.net/bugs/1937056
What distribution and version are you running? Are you running a Legion
7i 16ITHg6 ? Later Ubuntu kernels have had a fix for this for some time.
Same for the vanilla Linux source.
Alas, there's still no
*** This bug is a duplicate of bug 1786822 ***
https://bugs.launchpad.net/bugs/1786822
** This bug has been marked a duplicate of bug 1786822
Pinta constantly crashes in Ubuntu fresh install [double free or corruption
(out)]
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1786822 ***
https://bugs.launchpad.net/bugs/1786822
** This bug has been marked a duplicate of bug 1786822
Pinta constantly crashes in Ubuntu fresh install [double free or corruption
(out)]
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1786822 ***
https://bugs.launchpad.net/bugs/1786822
** This bug has been marked a duplicate of bug 1786822
Pinta constantly crashes in Ubuntu fresh install [double free or corruption
(out)]
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1786822 ***
https://bugs.launchpad.net/bugs/1786822
** This bug has been marked a duplicate of bug 1786822
Pinta constantly crashes in Ubuntu fresh install [double free or corruption
(out)]
--
You received this bug notification because you are a member
This fixed with Pinta 2.0 and the upgrade to .NET 6
** Changed in: pinta
Status: Triaged => Fix Released
** Changed in: pinta
Milestone: None => 2.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
That's great! I didn't see any mention of it here, and I posted that
patch just 3 days ago.Glad to see it make it in so quickly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939052
Title:
No
Heads up that the 13s Gen2 doesn't work with this patch. A followup was
necessary:
https://www.spinics.net/lists/alsa-devel/msg132423.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939052
If a new library is required, that would be better suited for the GTK3 / .NET5
branch of Pinta (https://github.com/PintaProject/Pinta/tree/gtk3-v2).
Ideally we could load the metadata at the same time as the image data ..
--
You received this bug notification because you are a member of Ubuntu
@costamagnagianfranco I think this is incorrect. Looking at the official
script,
https://www.virtualbox.org/svn/vbox/trunk/src/VBox/Installer/linux/vboxautostart-service.sh,
I see:
- a `start()` function that runs:
- `/usr/lib/virtualbox/VBoxAutostart` with params:
- `--start --config
This solves the problem for me.
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937056
Title:
Touchpad not
My EDID doesn't seem to parse correctly... Which is probably at least
part of the problem. The fact that it works on the Nvidia driver
suggests that EDID parsing could be the problem (I'm sure Nvidia does
their own EDID parsing).
Anyway, I did attempt to play around with the EDID... I'm able to
Some info is here:
https://github.com/thiagotei/linux-realtek-alc287
You can run a VM using someone's fork of of Qemu (which just adds a bit of
logging) with PCIE passthrough of your sound card. Then you can narrow down
exactly which verbs are needed.
It seems that some of the people in your
Hello Alex,
Thanks for the info. The amount of stuff on my plate has recently ramped
up. I'll try to see if I can get started with this process at some point
during this month.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Unsure if this is related, but I'm seeing the same issue with both the
21.04 vendor kernel and 5.13.8. I have a 165 Hz screen, and the Intel
iGPU will only run it at 60 Hz. If I switch to the discrete Nvidia GPU
in the BIOS, I get 165 Hz and I'm able to switch to 60 Hz.
First I switch from "165
All patches apply against all of 5.13.x so far (with the latest being
5.13.8).
This is a duplicate of
https://bugzilla.kernel.org/show_bug.cgi?id=208555
Happy to improve these patches to a point where they could be
included.I'm posting this here, because I'm an Ubuntu user and I'd like
to see
This is the patch for the 13s gen2 with the aforementioned issue
relating to volume adjustments using the keyboard function keys.
** Patch added: "Cegion-13s-gen2-sound-0.0.9-003.patch"
This is the patch for the Lenovo Yoga 7 14ITL5.
** Patch added: "linux-5.12-legion-sound-yoga-14ITL5-0.0.9-002.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939052/+attachment/5516171/+files/linux-5.12-legion-sound-yoga-14ITL5-0.0.9-002.patch
--
You received this bug
Public bug reported:
All 3 models need the appropriate HDA verbs sent to properly initialize
the sound hardware.
Additionally, the Legion 15IMHG05 needs automute disabled otherwise
speaker output will not return after removing headphones.
The good news is that I have working patches for all 3.
I applied the diff to 5.13.8... and it worked!
Thank you!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938845
Title:
Legion 7 16ITHg6 - Touchpad undetected
To manage notifications about this
Appears to be an ELAN:
acpidump | grep ELAN
439E0: 31 00 5F 48 49 44 70 0D 45 4C 41 4E 30 30 30 31 1._HIDp.ELAN0001
Add this ID to include/linux/input/elan-i2c-ids.h did not work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I received my Lenovo Legion 7i 16ITHg6 laptop today. The touchpad seems
to be entirely undetected.
I've attached the contents of /proc/bus/input/devices as devices.txt. No
touchpad device is shown. USB mice work.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package:
Plague meant I started the update, and have only now been able to get
back to text if it worked.
It did.
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927660
Title:
Update from 18.04
*** This bug is a duplicate of bug 1931787 ***
https://bugs.launchpad.net/bugs/1931787
** This bug has been marked a duplicate of bug 1931787
Keyboard/touchpad unresponsive after 5.8/20.04 upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1931787 ***
https://bugs.launchpad.net/bugs/1931787
** This bug has been marked a duplicate of bug 1931787
Keyboard/touchpad unresponsive after 5.8/20.04 upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1931787 ***
https://bugs.launchpad.net/bugs/1931787
** This bug has been marked a duplicate of bug 1931787
Keyboard/touchpad unresponsive after 5.8/20.04 upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1931787 ***
https://bugs.launchpad.net/bugs/1931787
** This bug has been marked a duplicate of bug 1931787
Keyboard/touchpad unresponsive after 5.8/20.04 upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1931787 ***
https://bugs.launchpad.net/bugs/1931787
** This bug has been marked a duplicate of bug 1931787
Keyboard/touchpad unresponsive after 5.8/20.04 upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1931787 ***
https://bugs.launchpad.net/bugs/1931787
** This bug has been marked a duplicate of bug 1931787
Keyboard/touchpad unresponsive after 5.8/20.04 upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1931787 ***
https://bugs.launchpad.net/bugs/1931787
** This bug has been marked a duplicate of bug 1931787
Keyboard/touchpad unresponsive after 5.8/20.04 upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1931787 ***
https://bugs.launchpad.net/bugs/1931787
** This bug has been marked a duplicate of bug 1931787
Keyboard/touchpad unresponsive after 5.8/20.04 upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1931787 ***
https://bugs.launchpad.net/bugs/1931787
** This bug has been marked a duplicate of bug 1931787
Keyboard/touchpad unresponsive after 5.8/20.04 upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1931787 ***
https://bugs.launchpad.net/bugs/1931787
** This bug has been marked a duplicate of bug 1931787
Keyboard/touchpad unresponsive after 5.8/20.04 upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1931787 ***
https://bugs.launchpad.net/bugs/1931787
** This bug has been marked a duplicate of bug 1931787
Keyboard/touchpad unresponsive after 5.8/20.04 upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1931787 ***
https://bugs.launchpad.net/bugs/1931787
** This bug has been marked a duplicate of bug 1931787
Keyboard/touchpad unresponsive after 5.8/20.04 upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1931787 ***
https://bugs.launchpad.net/bugs/1931787
** This bug has been marked a duplicate of bug 1931787
Keyboard/touchpad unresponsive after 5.8/20.04 upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1931787 ***
https://bugs.launchpad.net/bugs/1931787
** This bug has been marked a duplicate of bug 1931787
Keyboard/touchpad unresponsive after 5.8/20.04 upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1931787 ***
https://bugs.launchpad.net/bugs/1931787
** This bug has been marked a duplicate of bug 1931787
Keyboard/touchpad unresponsive after 5.8/20.04 upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1931787 ***
https://bugs.launchpad.net/bugs/1931787
** This bug has been marked a duplicate of bug 1931787
Keyboard/touchpad unresponsive after 5.8/20.04 upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1931787 ***
https://bugs.launchpad.net/bugs/1931787
** This bug has been marked a duplicate of bug 1931787
Keyboard/touchpad unresponsive after 5.8/20.04 upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1931787 ***
https://bugs.launchpad.net/bugs/1931787
** This bug has been marked a duplicate of bug 1931787
Keyboard/touchpad unresponsive after 5.8/20.04 upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
- After I recently replaced broken screen on HP Spectre x360 G2, keyboard and
touchpad became irresponsive - but only after booting. Booting with old kernel
(e.g. 5.4.0-42) restored full control. Also, disabling acpi restored control
(but one wants to see battery level
** Summary changed:
- Keyboard and touchpad absent after booting, but not before
+ Keyboard/touchpad unresponsive after 5.8 upgrade
** Summary changed:
- Keyboard/touchpad unresponsive after 5.8 upgrade
+ Keyboard/touchpad unresponsive after 5.8/20.04 upgrade
--
You received this bug
*** This bug is a duplicate of bug 1931787 ***
https://bugs.launchpad.net/bugs/1931787
** This bug has been marked a duplicate of bug 1931787
Keyboard and touchpad absent after booting, but not before
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1931787 ***
https://bugs.launchpad.net/bugs/1931787
** This bug has been marked a duplicate of bug 1931787
Keyboard and touchpad absent after booting, but not before
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1931787 ***
https://bugs.launchpad.net/bugs/1931787
** This bug has been marked a duplicate of bug 1931787
Keyboard and touchpad absent after booting, but not before
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1931787 ***
https://bugs.launchpad.net/bugs/1931787
** This bug has been marked a duplicate of bug 1931787
Keyboard and touchpad absent after booting, but not before
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1931787 ***
https://bugs.launchpad.net/bugs/1931787
** This bug has been marked a duplicate of bug 1931787
Keyboard and touchpad absent after booting, but not before
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1931787 ***
https://bugs.launchpad.net/bugs/1931787
** This bug has been marked a duplicate of bug 1931787
Keyboard and touchpad absent after booting, but not before
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
- After I recently replaced broken screen on HP Spectre x360 G2, keyboard and
touchpad became irresponsive - but only after booting. Booting with old kernel
(e.g. 5.4.0-42) restored full control. Also, disabling acpi restored control
(but one wants to see battery
*** This bug is a duplicate of bug 1931787 ***
https://bugs.launchpad.net/bugs/1931787
** This bug has been marked a duplicate of bug 1931787
Keyboard and touchpad absent after booting, but not before
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1931787 ***
https://bugs.launchpad.net/bugs/1931787
** This bug has been marked a duplicate of bug 1931787
Keyboard and touchpad absent after booting, but not before
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1931787 ***
https://bugs.launchpad.net/bugs/1931787
** This bug has been marked a duplicate of bug 1931787
Keyboard and touchpad absent after booting, but not before
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1931787 ***
https://bugs.launchpad.net/bugs/1931787
** This bug has been marked a duplicate of bug 1931787
Keyboard and touchpad absent after booting, but not before
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1931787 ***
https://bugs.launchpad.net/bugs/1931787
** This bug has been marked a duplicate of bug 1931787
Keyboard and touchpad absent after booting, but not before
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1931787 ***
https://bugs.launchpad.net/bugs/1931787
** This bug has been marked a duplicate of bug 1931787
Keyboard and touchpad absent after booting, but not before
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
- After recently replaced broken screen, keyboard and touchpad became
- irresponsive - but only after booting. Booting with old kernel (e.g.
- 5.4.0-42) restored full control. Also, disabling acpi restored control
- (but one wants to see battery level...). Evidently, it is
Public bug reported:
After recently replaced broken screen, keyboard and touchpad became
irresponsive - but only after booting. Booting with old kernel (e.g.
5.4.0-42) restored full control. Also, disabling acpi restored control
(but one wants to see battery level...). Evidently, it is not
Public bug reported:
Have successfully performed this update with similar extra software
installed, and can't narrow it down to what software is blocking things.
Other bug reports talk about various other packages, many of which I've
tried removing with no improvement.
"apt-get purge
*** This bug is a duplicate of bug 1786822 ***
https://bugs.launchpad.net/bugs/1786822
** This bug has been marked a duplicate of bug 1786822
Pinta constantly crashes in Ubuntu fresh install [double free or corruption
(out)]
--
You received this bug notification because you are a member
This is probably the same issue as bug 1786822 - I'd suggest installing
a newer version of Mono from https://www.mono-
project.com/download/stable/#download-lin, or installing the Snap /
Flatpak package
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It seems to build successfully! The package should be available in the
stable & daily builds soon, it's just awaiting publication.
** Changed in: pinta
Status: New => Fix Released
** Changed in: pinta (Ubuntu)
Status: New => Fix Released
--
You received this bug notification
I don't recall if there were issues with building Pinta 1.7 on 16.04 -
the daily builds also aren't being built (the last one for 16.04 is
1.7+r1077-202004072341 whereas the latest should be
1.7+r1173-202101231612)
I've kicked off a 16.04 build for the daily builds PPA, which is more
automated /
I believe I typed in `virtualbox` in the package. I was confused when I
saw it changed. Unclear if I messed up or if website revered it on its
own.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
with
Systemd).
Was this removed intentionally? Or maybe I just broke something on my
system? I've tried re-installing virtualbox a few times.
```
cameron@uberfall:~$ lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
cameron@uberfall:~$ apt-cache policy virtualbox
virtualbox
Do you see the same results in Pinta when using the Help -> About
dialog? It looks like the window manager is dimming the background when
a modal dialog is opened, which isn't something Pinta can really control
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Testing systemd 245.4-4ubuntu3.3 on Focal, I can verify that the default
value of the "Cache" directive is "no-negative" in the man page, default
config file, and actual program behaviour.
While doing this, I was reminded that the default value of the "DNSSEC"
directive is "no" in both the
I tested on a fresh Ubuntu 18.04 virtual machine, with Pinta installed from
https://launchpad.net/~pinta-maintainers/+archive/ubuntu/pinta-stable, and the
brightness / contrast effects updated correctly.
I'm not sure what might be different in your setup - are you using the snap or
flatpak
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1901358/+attachment/5427267/+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: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1901358/+attachment/5427266/+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: "AudioDevicesInUse.txt"
https://bugs.launchpad.net/bugs/1901358/+attachment/5427265/+files/AudioDevicesInUse.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1901358/+attachment/5427269/+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/1901358
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1901358/+attachment/5427268/+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/1901358
apport information
** Tags added: apport-collected ulyana
** Description changed:
[System settings] Sound
ASUS ROG Zenith II Extreme Alpha TRX40 Motherboard
5.1 Audio outputs are only usable as stereo by selecting "Headphones USB
Audio", which means only the front right and left
Public bug reported:
[System settings] Sound
ASUS ROG Zenith II Extreme Alpha TRX40 Motherboard
5.1 Audio outputs are only usable as stereo by selecting "Headphones USB
Audio", which means only the front right and left speaker work.
When I select "Speakers USB Audio" they do not work at all,
Thanks, it is behaving as expected with my test machines, so I think
I'll need to set up an 18.04 virtual machine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900123
Title:
Pinta 1.7 Interactive
I couldn't reproduce this in Ubuntu 20.04, so I'll need to try setting up an
18.04 VM.
Could you let me know which desktop environment you're using? (Gnome, KDE, etc)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This looks like the same issue - could you try installing the latest
version of Mono from https://www.mono-project.com/download/stable
/#download-lin?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Which operating system are you using?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896306
Title:
Only Pinta does not allow me to open an image from any usb drive
"permission dennied"
To manage
Public bug reported:
Back in December, the default for systemd-resolved caching in Ubuntu
systemd was changed to "no-negative" from the upstream default "yes" [0]
In this change, the default value in the resolved.conf file was missed.
As the defaults in this file are commented, the effective
Update: After much testing, the only thing I discovered would fix the
issues (including error messages on startup) was to downgrade the kernel
to 5.3.X. Upgrading wouldn't solve it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1461162 ***
https://bugs.launchpad.net/bugs/1461162
** This bug has been marked a duplicate of bug 1461162
Rotate layer, save and crash appears
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've experienced a similar issue on boot, with a Ryzen 7 3800x and a
5700xt on GNOME 3.36.2.
It may be related to a new error message when booting:
amdgpu: [powerplay] failed to send message: NumOfDisplays (64)
$param:0x0003 response
But, contrarily, my flickering issue can be corrected by
Bugstill exists in 20.04
[14624.728999] xhci_hcd :08:00.0: ERROR Transfer event TRB DMA ptr not part
of current TD ep_index 2 comp_code 1
[14624.729000] xhci_hcd :08:00.0: Looking for event-dma ff8d8050
trb-start ff8d7fe0 trb-end ff8d7fe0 seg-start
Thank you for the advice, that fixed my issue.
** Changed in: fonts-noto-cjk (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/1877957
Title:
Package
Public bug reported:
I just upgraded to Ubuntu Budgie 20.04 from 19.10 and this package
refused to update. After uninstalling it and attempting to reinstall it
I received the following:
cameron@cameron-M14xR2:~$ sudo apt-get install fonts-noto-cjk
[sudo] password for cameron:
Reading package
Thanks for confirming, this seems to be an issue with the default Mono
version in 18.04
** Changed in: pinta
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/1786822
*** This bug is a duplicate of bug 1464855 ***
https://bugs.launchpad.net/bugs/1464855
** This bug has been marked a duplicate of bug 1464855
The zoom tool does not work
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I am using two monitors, they both are displaying the same image. In
settings, only one monitor is recognized (technically they have the same
name, though). I have tried to go into arandr to see what I could do but
only one monitor is recognized there.
ProblemType: Bug
I'm currently traveling for work, but will verify the fix this evening
hopefully.
Thanks
On Thu, Nov 14, 2019, 10:41 Dan Streetman
wrote:
> @drdabbles can you please verify the fix in systemd in proposed
>
> --
> You received this bug notification because you are subscribed to the bug
>
Public bug reported:
Let me know if you need anything else.
ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: nvidia-kernel-source-435 435.21-0ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
This happens for me on Ubuntu 19.10 only when vscode is installed as a
snap. https://github.com/snapcrafters/vscode/issues/48
** Bug watch added: github.com/snapcrafters/vscode/issues #48
https://github.com/snapcrafters/vscode/issues/48
--
You received this bug notification because you are a
@ddstreet any configuration that ships lots to a remote host will
trigger this. The server always responds with the bug, so the
configuration effectively doesn't matter. As long as one host is
attempting to send journals to another in Disco, this bug will be
triggered.
Examples configs:
For those that may try to search for this bug in the future, the error I
received was
Error 411: gth required
The issue is that libmicrohttpd exhibits a bug when Content-Length is
omitted, even if Transfer-Encoding is set to "chunked". The HTTP/1.1
spec allows Content-Length to be omitted when
Public bug reported:
I'm requesting that systemd 240 receive the fix in upstream PR 11953
found here https://github.com/systemd/systemd/pull/11953
This fixes remote journal shipping using systemd components. I believe
only Disco (19.04) is impacted by this issue.
** Affects: systemd
1 - 100 of 773 matches
Mail list logo
