Proposed version working fine :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879741
Title:
Unable to read system logs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubu
I can echo Eric's observation above but with Firefox 75 (released with
20.04) and Firefox 76 (latest version).
If geo.provider.network.url is set to the Google service then it doesn't
work, but the mozilla one does. If you download Firefox from mozilla
then geolocation with Google works fine, so i
Possibly fixed here: https://gitlab.gnome.org/GNOME/gnome-
logs/-/issues/52
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879741
Title:
Unable to read system logs
To manage notifications about thi
journalctl at the command line works fine for all users.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-logs/-/issues #52
https://gitlab.gnome.org/GNOME/gnome-logs/-/issues/52
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Public bug reported:
1) Ubuntu 20.04 LTS
2) Gnome Logs 3.34.0-1
3) Open Gnome Logs and expect to be able to read all logs from the system
4) Gnome Logs opens and at the top there is an error message "Unable to read
system logs" - screenshot attached.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Public bug reported:
Description:Ubuntu 20.04 LTS
Release:20.04
gnome-tweak-tool:
Installed: 3.34.0-2ubuntu1
Candidate: 3.34.0-2ubuntu1
Version table:
*** 3.34.0-2ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
500 http://gb.arch
sudo update-apt-xapian-index works on 19.10 before launching Driver
Manager. From Googling around, it would appear that this bug has existed
in one form or another for years and years. Hopefully fairly simple to
resolve now that somebody has identified a solution?
--
You received this bug notific
So, this is simple to solve as it is a group issue.
1. Add group=kvm in /etc/libvirt/qemu.conf
2. Add yourself to the kvm group - sudo usermod -a -G kvm userName
Works after this. but shouldn't need this fix out of the box.
JT
--
You received this bug notification because you are a member of U
Whilst this might have expired, it is still not fixed.
** Changed in: mate-control-center (Ubuntu)
Status: Expired => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718396
Title:
This bug has now been resolved upstream in the latest bluetooth
firmware. Ubuntu firmware (when linux-firmware is updated) will carry
this fix.
Please see:
https://bugzilla.kernel.org/show_bug.cgi?id=197147
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Installing **vanilla-gnome-desktop** should provide the option of a
vanilla Gnome desktop. However, dynamic transparency of the top bar
remains; this is not vanilla Gnome.
This package should remove dynamic transparency for the vanilla Gnome
desktop, and allow it for the defa
Exists in the final release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720375
Title:
3x Language Support icons
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+
I have a feeling that this is related to bluetooth and wifi coexistence.
https://wireless.wiki.kernel.org/en/users/Drivers/iwlwifi#wi-
fibluetooth_coexistence
In essence, bleutooth and wifi operate on similar (the same) frequencies
and will interfere. Normally this is handled in the firmware/kern
Bug opened on bugzilla.kernel.org as I couldn't figure out the website
that you linked to (mostly an incomplete wiki).
Cheers.
** Tags added: kernel-bug-reported-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Checked latest upstream kernel...bug exists
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721271
Title:
Bluetooth and Wifi: coexistence Problem
To manage
Further digging suggests that this bus is not present in kernel 4.12.14
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721271
Title:
Bluetooth and Wifi: coexistence Problem
To manage notifications
Public bug reported:
I'm currently running kernel 4.13.0-12 on Ubuntu 17.10 (daily) and have
noticed that with my Intel Corporation Wireless 8260 (rev 3a) there
appears to be a problem with buetooth and wifi coexistence.
Unless I disable bluetooth and/or wifi I am unable to connect to the
opposit
This appears to be a problem with either the kernel or the firmware for
intel wifi/bluetooth chipsets. I've found that adding the following to
/etc/modprobe.d/iwlwifi.conf and then rebooting seems to solve my
problems:
options bt_coex_active=0
I've got no idea where this radio conflict is coming
Confirmed on Ubuntu Gnome 17.04 along with workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1687194
Title:
Bluetooth file send stopped after 17.04
To manage notifications about this bug go
19 matches
Mail list logo
