[Expired for gnome-control-center (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-c
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bu
Thanks for the bug report. The attached Xorg logs appear to be from
before the bug as they show a resolution of 1600x900. But I can also see
that your current resolution is 800x600 in Xrandr.txt. It seems Xorg now
can't even tell what kind of monitor connection it is.
Please try booting an older k
Thanks for the bug report. Please try logging into 'Ubuntu on Wayland'
using the icon in the bottom right corner of the login screen before you
enter your password. That should make it behave the same as the login
screen.
** Tags added: nvidia
** Package changed: xorg (Ubuntu) => xorg-server (Ub
Yes I can confirm the machine thinks there are no monitors connected.
Since you're using a closed source graphics driver we can't investigate
it any further than that. I would only recommend trying:
* unplugging and reconnecting the cable
* replacing the cable with a new one
* avoiding any adap
Please collect logs from the failed boots of the 470 driver by running:
journalctl -b-1 > prevboot-1.txt
journalctl -b-2 > prevboot-2.txt
journalctl -b-3 > prevboot-3.txt
journalctl -b-4 > prevboot-4.txt
journalctl -b-5 > prevboot-5.txt
and attach the resulting text files here.
** Pac
The mutter bug linked here is definitely fixed in 3.36.4 and later, so
if you still experience any problems then please open a new bug.
** Tags removed: fixed-in-3.36.5
** Tags added: fixed-in-3.36.4
--
You received this bug notification because you are a member of Desktop
Packages, which is su
Confirm this is fixed in new snap rev from Thunderbird 91.
Closing
** Changed in: thunderbird (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpa
Confirm this is fixed in the new snap rev with LO 7.2
Closing
** Changed in: libreoffice (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net
** Attachment removed: "memory-report.json.gz"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1856940/+attachment/5314605/+files/memory-report.json.gz
** Attachment removed: "HookError_source_firefox.txt"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1856940/+attachment/53
** Attachment removed: "WifiSyslog.txt"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5361003/+files/WifiSyslog.txt
** Attachment removed: "CRDA.txt"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360989/+files/CRDA.txt
** In
** Attachment removed: "Image of the Garbled Text"
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1855491/+attachment/5310318/+files/Screenshot%20from%202019-12-06%2014-58-26.png
** Information type changed from Public to Private
** Changed in: gnome-terminal (Ubuntu)
St
** Attachment removed: "ping.txt"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313410/+files/ping.txt
** Attachment removed: "Screenshot of configuring screen and terminal"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313383/+files/Sc
** Changed in: firefox (Ubuntu)
Status: New => Incomplete
** Changed in: firefox (Ubuntu)
Status: Incomplete => Invalid
** Information type changed from Public to Private
** Attachment removed: "IpAddr.txt"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1857167/+attachm
** Attachment removed: "Dependencies.txt"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310885/+files/Dependencies.txt
** Attachment removed: "NetDevice.enp4s0.txt"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310
** Attachment removed: "Screenshot of screen and instllation output."
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1870597/+attachment/5345770/+files/Screenshot%20from%202020-04-03%2014-27-25.png
--
You received this bug notification because you are a member of D
** Attachment removed: "CRDA.txt"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350596/+files/CRDA.txt
** Attachment removed: "CRDA.txt"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310884/+files/CRDA.txt
** Atta
LHS = left hand side
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1942940
Title:
Hover text in wrong place
Status in nautilus package in Ubuntu:
Incomplete
Bug description:
O
** Attachment removed: "WifiSyslog.txt"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310894/+files/WifiSyslog.txt
** Attachment removed: "IpAddr.txt"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310886/+files/IpA
** Attachment removed: "Image of the Terminal"
https://bugs.launchpad.net/nautilus/+bug/1853784/+attachment/5307577/+files/Screenshot%20from%202019-11-24%2017-29-52.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubunt
hello,
thank you for the quick reply.
my problem: until about 2 months ago I had my notebook connected to my
tv (DVI/HDMI) without problems. after an update ubuntu 20.04 no longer
recognizes other monitors.
what can i do?
greetings
volker
Am 09.09.21 um 04:04 schrieb Daniel van Vugt:
> Thanks for
lspci attached
** Attachment added: "DaveQB-lspci"
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1884850/+attachment/5524161/+files/DaveQB-lspci
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
http
Thanks Wirawan. I was contemplating digging into my driver and switching
from Nvidia to Nouveau (although I think Nouveau couldn't drive my new
monitor last I tried.
nvidia-driver-460
Gigabyte X570 AORUS MASTER
AMD Ryzen 5 3600
GP106 [GeForce GTX 1060 6GB]
lsmod attached
** Attachment added: "
Public bug reported:
0.8 is currently in Impish, but power profile persistence was only added
in 0.9
Please update the latest upstream release in Impish (21.10), otherwise
the fix will only come in 22.04.
Links:
https://gitlab.freedesktop.org/hadess/power-profiles-daemon/-/releases/0.9.0
https:
Public bug reported:
My resolution has suddenly changed from a higher resolution from to low
resolution to 800x600 and it is now showing only one resolution option
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic
Gosh, @vanvugt, I run 20.04, everything up to date, and this bug still
seems present. I wonder why people thought it was fixed. Could the fix
still not be pushed out to the repos?
--
n
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mu
Thank you for your bug report. What does 'LHS' mean? Could you add a
screenshot showing the issue?
** Changed in: nautilus (Ubuntu)
Importance: Undecided => Low
** Changed in: nautilus (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
Only since logrus commit bdb7d4c53122 ("go.mod: update golang.org/x/sys
to fix openbsd/mips64 on Go 1.16") we get a dependency which allows for
RISC-V.
It is reasonable to use current logrus master/origin of today as
dependency for ubuntu-report.
--
You received this bug notification because you
Public bug reported:
Building ubuntu-reports leads to an error related to undefined symbols
on RISC-V.
** Affects: ubuntu-report (Ubuntu)
Importance: Undecided
Status: New
** Tags: riscv64
--
You received this bug notification because you are a member of Desktop
Packages, which
Public bug reported:
I have two mice each with their own dongle. 1 is the microsoft sculpt
keyboard mouse combo and the other is a logitech master2 (using dongle
not bluetooth). Both of the mice work while in the login screen but
once you log in neither will control the cursor.
I know they are
Sending this bug after, solved by change drivers, i can change it back
to 470, and perform debug commands if needed (gather logs etc.)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1943130
Public bug reported:
After turn on mu PC, it doesn't send signal to the second monitor. (with driver
"nvidia-driver-470(proprietary tested)"
After change it to: "nvidia-driver-460(proprietary)" problem solved.
Looks like new kernel update have conflict with nvidia - 470 driver.
(because yesterda
Dave, I am suspecting a bug with the X hardware driver. Can you please
describe the machine you are using. Plus produce the output of "lspci"
and "lsmod"?
Wirawan
On Thu, Sep 9, 2021 at 6:59 AM DaveQB <1884...@bugs.launchpad.net> wrote:
>
> I have this same issue 🙋♂️
> KDE Neon (Ubuntu 20.04 bas
@Takashi Iwai
> So moving it back would break something else, too. Hmm.
Indeed, it will break whatever solutions to the original issue of
microphone input crackling your changes may have fixed for this sound
device.
My use case - capturing from the global output monitor - has never had a
crackl
(In reply to Rob McCathie from comment #292)
> I should clarify: My broken use case is capturing from the global output
> monitor while also capturing the screen, and having the audio be
> synchronised like at capture time.
>
> In some of my early tests the audio was not only un-synchronised, but
Again a correction: the current default setup for Raven corresponds to
position_fix=6 option. It's not a simple LPIB read but contains some
awkward correction that takes the FIFO size into account.
--
You received this bug notification because you are a member of Desktop
Packages, which is subsc
I should clarify: My broken use case is capturing from the global output
monitor while also capturing the screen, and having the audio be
synchronised like at capture time.
In some of my early tests the audio was not only un-synchronised, but
had other issues too (jolting, etc.), so it's possible
1487 is with the same setup as Raven (15e3), and the same workaround is
applied.
Please note that the workaround isn't actually delaying the sound
transfer. Instead, it reports the PCM delay value up to 32bytes for
FIFO size for the applications. If the application (the sound backend)
doesn't ta
(In reply to Rob McCathie from comment #296)
> Just thought i'd update on my situation, i've now tested that it is only the
> Pulse changing to batch mode that causes my issue. So i'm no longer running
> the patch i posted earlier, rather now i do this:
>
>
>
> diff -Naur a/sound/pci/hda/hda_con
Just thought i'd update on my situation, i've now tested that it is only
the Pulse changing to batch mode that causes my issue. So i'm no longer
running the patch i posted earlier, rather now i do this:
diff -Naur a/sound/pci/hda/hda_controller.c b/sound/pci/hda/hda_controller.c
--- a/sound/pci/h
Any update on this? Perhaps I have a misunderstanding, however the issue
is still here unless I do a patch -R with what is in comment #296. Even
with the latest 5.11.13...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubun
Update after the latest firmware update for the platform, called AMD
AGESA V2 PI 1.2.0.3 Patch A, released yesterday for my platform,
finally. This includes the USB patch for the drop in the USB
communication under load for too much recovery errors hitting the Pci-Ex
subsystem on the chipset, appar
I hit this issue as well on my Gentoo box (see
https://bugs.gentoo.org/779157).
After applying the patch mentioned in comment #296, the audio is back to
normal with PulseAudio, no more distortions, the audio is clean. No
perceived audio lags. Everything is in working order again.
Tested only with
OK, I'm going to submit this partial revert.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1801540
Title:
Microphone distorted sound on ALC892/1220 on AMD chipsets
Status in Linu
Indeed.
My issue relates to usage with Pulse.
PipeWire looks like an interesting up-and-coming project, but right now
Pulse is what is rolled out in the vast majority of distros and, for
now, tales of outcomes with PipeWire aren't so useful.
--
You received this bug notification because you are
Yes, that's merely an ugly workaround, and I'd happily get rid of it
once after confirming it's working fine without that!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1801540
Titl
After some gaming and streaming, I can confirm that I haven't heard
anymore pops or clicks, and a lot of performance issues completely
disappeared after applying this firmware, like microstutters in the
system under load and such. Kinda makes sense, since PciEx is basically
the main bus where every
Created attachment 295735
The partial revert patch
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1801540
Title:
Microphone distorted sound on ALC892/1220 on AMD chipsets
Status i
I have this same issue 🙋♂️
KDE Neon (Ubuntu 20.04 base).
I do have LibreOffice Writer open full-time.
libreoffice Version 1:6.4.7-0ubuntu0.20.04.1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launc
Derek - Your "Clunky workaround" can be automated:
https://www.summet.com/blog/2015/11/16/making-thunderbird-send-messages-in-the-background-like-outlook/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock i
Launchpad has imported 5 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=211853.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help
Derek - Your "Clunky workaround" can be automated:
https://www.summet.com/blog/2015/11/16/making-thunderbird-send-messages-in-the-background-like-outlook/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock i
... and looking back at the development history again, this seems too early to
be delighted. Actually the change to PRESET_AMD_SB was done as a fix for the
certain devices in the commit d2c63b7dfd06788a466d5ec8a850491f084c5fc2
ALSA: hda - Apply AMD controller workaround for Raven platform
S
That's a good discovery. This change makes sense, as the different of
PRESET_ATI_SB from PRESET_AMD_SB is about the position reporting. ATI_SB uses
the legacy LPIB register read while AMD_SB uses the position buffer table.
This could be verified by changing position_fix module option: 1 is LPIB
FYI, the 'solution' for this issue that is now in the kernel breaks
capturing screen+currrently playing audio with ffmpeg, for me at least,
on AMD Raven hardware.
I tried many things but could not achieve good audio capture that is
synchronised, not when capturing from Pulse anyway.
I'm guessing
Updates on this long endeavor as of today: I choose to give another try
for switching from PulseAudio to the PipeWire sound server.
The problems are completely gone. No audio clicking anywhere on the system.
I have tried one month ago, but on reboot I was not having any audio coming out
from the
** Changed in: pepperflashplugin-nonfree (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to flashplugin-nonfree in Ubuntu.
https://bugs.launchpad.net/bugs/1871471
Title:
flash end of life soon,
57 matches
Mail list logo
