In Ubuntu we always prefer whichever device connected most recently,
which is probably your wireless headset. To disable this feature try
editing /etc/pulse/default.pa and commenting out some or all of these:
### Should be after module-*-restore but before module-*-detect
load-module
I also hit this again in focal on 2020-06-25, with an update to systemd
245.4-4ubuntu3.1; I had previously updated dbus to 1.12.16-2ubuntu2.1 on
2020-06-17 without event. It's still an issue at least with updates to
systemd in focal.
Similar messages end up in the journal:
Jun 25 13:04:55 kryten
Issues like this are often model or vendor specific. What is the model
of headset?
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887977
** Summary changed:
- Pairing with bluetooth mice fails
+ Pairing with Bluetooth LE mice fails on a Huawei Matebook 13 AMD laptop with
Realtek RTL8822CE Wifi/Bluetooth combo adapter
** Changed in: bluez (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because
*** This bug is a duplicate of bug 1532508 ***
https://bugs.launchpad.net/bugs/1532508
I think bug 1532508 has been around for so long that it's now about any
case in which the lock screen is used.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1887914
When reporting bugs in the future please use apport by using 'ubuntu-
Sorry I failed to notice you can't replace the graphics card as it's a
laptop...
If that error is some other PCIe device then it might be just the wifi
card which is easy to disable or replace.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The only explanation for a freeze I can see in the log of comment #4 is
this recurring kernel/hardware problem:
Jul 16 12:06:21 bmariner-Inspiron-7375 kernel: pcieport :00:01.1: AER:
Corrected error received: :00:01.0
Jul 16 12:06:21 bmariner-Inspiron-7375 kernel: pcieport :00:01.1:
This change was made by a bot.
** Changed in: linux (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/1879402
Title:
[amdgpu] Proper monitor resolution/refresh
Thank you for taking the time to report this issue and helping to make
Ubuntu better.
I didn't look for your actual issue, but I saw a number of things that
would have me checking your hardware.
I would suggest doing a `fsck` of your partition(s) (esp. sda5), after
you evaluate the health of
** Changed in: pango1.0 (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/1887271
Title:
Square rectangles instead of system fonts after upgrade
Public bug reported:
Server: Debian 10 (buster), nagios-nrpe-plugin-3.2.1-2
Node: Linux Mint 20 (Ulyana), using Ubuntu Focal,
nagios-nrpe-server-4.0.0-2ubuntu1
Icinga1 server on Debian monitoring a bunch of LinuxMint-19.3, using protocol
v3, and working just fine since last year. I just built
Tracking in:
https://errors.ubuntu.com/problem/adfb298b28830385f505496bdcbaa7e96af702b4
** Changed in: gnome-control-center (Ubuntu)
Status: Expired => Confirmed
** Description changed:
+ https://errors.ubuntu.com/problem/adfb298b28830385f505496bdcbaa7e96af702b4
+
+ --
+
Software &
*** This bug is a duplicate of bug 1873075 ***
https://bugs.launchpad.net/bugs/1873075
** This bug has been marked a duplicate of bug 1873075
gnome-control-center crashed with SIGSEGV in
_cogl_renderer_handle_native_event()
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1873075 ***
https://bugs.launchpad.net/bugs/1873075
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-control-center. This problem was most recently seen with package version
1:3.34.1-1ubuntu2, the
** Changed in: linux (Ubuntu)
Status: Expired => New
** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879402
This is fixed in Ubuntu 20.04 with nss-mdns 0.14 and later which does
proper split horizon handling.
** Changed in: avahi (Ubuntu)
Status: Triaged => Fix Released
** Changed in: nss-mdns (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you
Rumen,
When you use 'nslookup' it should go directly to using the DNS server
(127.0.0.53 [which is systemd-resolved]) which typically bypasses
libnss-mdns but also typically doesn't have this 5 second delay (which
avahi can have in some configurations). Seems most likely the 5 second
delay is
** Changed in: kunpeng920/ubuntu-18.04
Milestone: None => ubuntu-18.04.5-sru-1
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Ike Panhc (ikepanhc)
** Changed in: kunpeng920/ubuntu-18.04
Assignee: (unassigned) => Ike Panhc (ikepanhc)
--
You received this bug
** Changed in: kunpeng920/ubuntu-20.04
Milestone: None => ubuntu-20.04.1-sru-1
** Changed in: kunpeng920/ubuntu-18.04-hwe
Milestone: None => ubuntu-18.04.5-sru-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I made a new transparent layer, then made a circle with the oval
selection tool. Then I hit X to put white as my foreground color. Then
used bucket fill tool to fill the circle in white, but instead, it
crashed the gimp.
KUbuntu 18.04.4 LTS
Bug information is in a text file
7GB in my case. I am the only user, but what I do in a rare case is put the
computer into Suspend mode.
Truly stupid behavior, to fill up a log with 7GB+++ of same error, without ever
showing an on-screen notification to a user (ONLY ONCE PLEASE, NOT SEVEN
BILLION NOTIFICATIONS), ASSUMING this
Public bug reported:
I cannot connect to Bluetooth devices.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-release-upgrader (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:
I'm working on Ubuntu 18.04 x86_64 fully patched. I'm trying to use
patchelf to fix runpaths in Perl built from sources. Perl is mishandling
runpath options in LDFLAGS but refuses to fix it; see
https://github.com/Perl/perl5/issues/17534.
When patchelf runs I see a lot of:
The attachment "muffin_4.4.3-1ubuntu0.1.debdiff" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff. If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch"
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870995
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]
** Changed in: firefox (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878315
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for dbus (Ubuntu) because there has been no activity for 60
days.]
** Changed in: dbus (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871538
[Expired for dbus (Ubuntu Focal) because there has been no activity for
60 days.]
** Changed in: dbus (Ubuntu Focal)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for libinput (Ubuntu) because there has been no activity for 60
days.]
** Changed in: libinput (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for network-manager (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878495
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877655
[Expired for im-config (Ubuntu) because there has been no activity for
60 days.]
** Changed in: im-config (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for i3-wm (Ubuntu) because there has been no activity for 60
days.]
** Changed in: i3-wm (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879352
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879432
[Expired for xserver-xorg-video-amdgpu (Ubuntu) because there has been
no activity for 60 days.]
** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879402
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879689
Public bug reported:
Do not know what is the problem
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15 [modified:
lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
** Tags added: sru-20200629
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813878
Title:
lxc test failed on Azure T-4.15
To manage notifications about this bug go to:
Public bug reported:
Grub installer package did not install during a fresh ubuntu
installation
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887909
*** This bug is a duplicate of bug 1532508 ***
https://bugs.launchpad.net/bugs/1532508
I do not think this is the same problem.
1532508 is supsend issue.
This does not require supsend.
Just do nothing for the amount of time it takes to cause the screen to lock
because of being idle.
then
** Description changed:
This is an upstream issue-read the following bug reports.
https://github.com/linuxmint/cinnamon/issues/9401
https://github.com/linuxmint/cinnamon/issues/9468
I will shortly publish a patch/debdiff to allow for possible SRU.
This is a REGRESSION of a
*** This bug is a duplicate of bug 1532508 ***
https://bugs.launchpad.net/bugs/1532508
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1532508, so it is being marked as such. Please
** Tags added: focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532508
Title:
Screen contents revealed briefly on resume, before even unlocking
To manage notifications about this bug go to:
Thanks. Can you also provide a screenshot or photo of the problem?
Also when the problem is happening please run:
free -h > free.txt
ps auxw > ps.txt
and attach the resulting text files here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Brendan_P, Please try to reword this bug into a simple description of a
_single_ problem.
David, Please open a new bug by running: ubuntu-bug gnome-shell
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Installed the linux-firmware 1.187.2, ls /lib/firmware/intel/sof and
/lib/firmware/intel/sof-tplg, verfied the files are reverted.
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Also affects: dash-to-dock via
https://github.com/micheleg/dash-to-dock/issues/1274
Importance: Unknown
Status: Unknown
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of
** Also affects: plymouth via
https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/118
Importance: Unknown
Status: Unknown
** Changed in: plymouth (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: plymouth (Ubuntu)
Status: Confirmed => Triaged
--
You
Marco, that doesn't make sense. You have the bug fix committed in focal
but not in groovy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885346
Title:
gnome-shell-calendar-server leaks GBs of
That doesn't make sense. Fixed in focal but not groovy?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871868
Title:
Shell dialog text is truncated and ellipsized
To manage notifications about
** Changed in: gnome-control-center (Ubuntu)
Status: Triaged => Fix Committed
** Tags added: fixed-in-3.37.4 fixed-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857340
Title:
** Changed in: plymouth (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872669
Title:
BIOS logo reappears after the Lubuntu dots
To manage notifications
Test on Tiger Lake platfrom.
codename: focal
CID: 202006-28008
BIOS: 0.5.2
kernel: 5.6.0-1020-oem
Steps:
1. $ sudo apt update
2. $ sudo apt dist-upgrade
3. check audio, "Dummy output"
4. Add proposed developer option
5. $ sudo apt install linux-firmware => update to 1.187.2
6. $ sudo reboot
BTW the fix first appeared in 5.50 (commit
f1b8cdef95d6b51cab122f2be0694521f47092d0).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887910
Title:
[bionic]blutoothd segfault when you cancel the
Test on Tiger Lake platfrom.
codename: focal
CID: 202006-28008
BIOS: 0.5.2
kernel: 5.6.0-1020-oem
Steps:
1. $ sudo apt update
2. $ sudo apt dist-upgrade
3. check audio, "Dummy output"
4. Add proposed developer option
5. $ sudo apt install linux-firmware => update to 1.187.2
6. sudo reboot
I'm going to remove Ubuntu Sponsors from this briefly, until the
following are fixed:
1. The issue mentioned in comment #7 - The Bug Description on this page
needs improving.
2. The email address used in the patch needs replacing
with your real email.
3. Need to mention the bug ID and the
Oh, I can't remove Ubuntu Sponsors. Still, please fix all of the above.
** Also affects: bluez (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: bluez (Ubuntu Groovy)
Importance: High
Status: In Progress
** Also affects: bluez (Ubuntu Bionic)
Importance:
Also, please try changing the profile of your headset to HSP/HFP in
Settings.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887898
Title:
Bluetooth sound card not detected
To manage notifications
This bug *is* about the proprietary nvidia driver. Are you saying it
doesn't happen anymore?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874217
Title:
[nvidia] Dual monitor setup with secondary
Public bug reported:
This is an upstream issue-read the following bug reports.
https://github.com/linuxmint/cinnamon/issues/9401
https://github.com/linuxmint/cinnamon/issues/9468
I will shortly publish a patch/debdiff to allow for possible SRU.
This is a REGRESSION of a commit in Cinnamon
Hey, does this relate to you?
https://github.com/linuxmint/cinnamon/issues/9468
https://github.com/linuxmint/cinnamon/issues/9401
** Bug watch added: github.com/linuxmint/cinnamon/issues #9468
https://github.com/linuxmint/cinnamon/issues/9468
** Bug watch added:
** Description changed:
- For focal and oem-5.6 kernel, these all 5 patches are needed, for
- groovy kernel, since the 1st patch is already in the 5.8 kernel, the
- groovy kernel only needs the last 3 patches [3/5, 4/5 and 5/5].
+ Groovy kernel already merged the patchset
[Impact]
- the alsa
I am seeing this again on the latest stable release on Ubuntu 20.04 on a
Dell Precision with attached displays.
Linux bdp 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64
x86_64 x86_64 GNU/Linux
TU117GLM [Quadro T1000 Mobile]
nvidia-driver-440
** Summary changed:
- soc/amd/renoir: improve the amd renoir audio driver to prepare to work with
ucm3
+ soc/amd/renoir: detect dmic from acpi table
** Changed in: linux (Ubuntu Groovy)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member
** Description changed:
[Impact]
the alsa upstream worte the ucm3 files for amd renoir audio, but to
load the ucm3, it depends on the kernel module name, and the upstream
- ucm3 needs the name snd-xxx, so we need to backport the patches
+ ucm3 needs the name snd-xxx, so we need to backport
After a bit more troubleshooting, working with xrandr and the xorg.conf
doesn't seem to have any effect when on the tty, and xrandr throws a
cannot connect to display error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Currently I'm using a 4K AOC monitor on 20.04 LTS with a DisplayPort
cable.
Normally, there is a gear widget in the lower right corner of the screen
that allows me to select between XServer and Wayland. This gear is
missing. Switching to an HDMI cable corrects the issue but
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1888166
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
[Impact]
the alsa upstream worte the ucm3 files for amd renoir audio, but to
load the ucm3, it depends on the kernel module name, and the upstream
ucm3 needs the name snd-xxx, so we need to backport the patches
from mainline kernel to change the kernel module name to meet
** Changed in: libsimpleini (Ubuntu)
Status: Confirmed => 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/1871790
Title:
Missing dependency on libicu-dev for libsimpleini-dev
To
I'm attaching the captured btsnoop logs
** Description changed:
Expected behavior:
1.Pressing the “Cancel” button during device pairing should close the
pairing code prompt
2.Re-pairing BT keyboard after cancelling initial pairing should re-open
the pairing code prompt
I'm attaching the dmesg result
** Attachment added: "dmesg logs"
https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1888164/+attachment/5394188/+files/dmesg%20result%20for%20Ubuntu.txt
** Description changed:
Expected behavior:
1.Pressing the “Cancel” button during
I ran into this today. So annoying. I kept getting "Please check that
the PPA name or format is correct." This error message is so
misleading... The Internet is littered with people working around the
"add-apt-repository" script since no one can really figure out the real
reason for this error
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: software-properties (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/1364176
Public bug reported:
Expected behavior:
1. Pressing the “Cancel” button during device pairing should close the
pairing code prompt
2. Re-pairing BT keyboard after cancelling initial pairing should re-open
the pairing code prompt
Problem:
1. Pressing the “Cancel” button during
I have a Ryzen 5 3600x and I have the same issue. I get freezes where I
can't move the cursor and the only fix is manually rebooting the PC.
Data corruption is something that I'm already experiencing here. Not
sure what to do. I'm not using Ubuntu, though. It is also reproducible
on Ubuntu,
You're welcome. I will mark as Fix Released. Reopen it if you experience
the no boot issue again.
** Changed in: xorg (Ubuntu)
Status: Incomplete => Fix Released
--
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.
Apparently issue still exists because today I updated from Linux Mint
18.3 to 20.04 (Ulyana) and received this exact error which was resolved
by David Lechner's fix in post #3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Apparently issue still exists because today I updated from Linux Mint
19.3 to 20.04 (Ulyana) and received this exact error which was resolved
by David Lechner's fix in post #3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Success!
Thank you very much !
On Sun, Jul 19, 2020 at 2:15 PM Steve Daigle wrote:
> Sounds good - going for walk with my wife - Will follow those steps and
> get back to you in a few hours.
>
> Thanks for your help
>
> Steve
>
>
> On Sun, Jul 19, 2020 at 2:05 PM Daniel Letzeisen <
>
Gnome team have fixed this upstream, see fix
https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/42
v3.18.2 will not be fixed.
I have manually compiled and installed v3.18.3 with my own API key but
it still does not work. Gnome team have advised that 3.18 is now
unsupported and latest
Unfortunately, I'm not sure how best to reproduce this. I can tell you
that we were seeing this on really busy units.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565744
Title:
"Mutex
Doesn't seem to be happening with 20.04, for now at least.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873093
Title:
Gnome-terminal tab bar steals keyboard focus
To manage notifications about
The bug does not occure with proprietary nvidia driver
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874217
Title:
[nvidia] Dual monitor setup with secondary monitor in portrait-right
mode cause
Hello. Is there any movements toward this bug extinction?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874217
Title:
[nvidia] Dual monitor setup with secondary monitor in portrait-right
mode
Public bug reported:
Description: Ubuntu 18.04.4 LTS
Release: 18.04
apt-cache policy clamav
clamav:
Installed: 0.102.3+dfsg-0ubuntu0.18.04.1
Candidate: 0.102.3+dfsg-0ubuntu0.18.04.1
The current version of ClamAV for 18.04.4 LTS is 0.102.3+dfsg-
0ubuntu0.18.04.1. The current stable version
I've packaged the fix for xenial in this branch:
https://code.launchpad.net/~bryce/ubuntu/+source/apache2/+git/apache2/+ref/ubuntu
/xenial-devel/
However I've not been able to construct a configuration+workload to
reproduce the error message. Can someone describe a way to trigger the
messages
1 - 100 of 241 matches
Mail list logo
