Bug #1775971 is for updating gpaste to 3.28.3 in Bionic, which fixes two
crashes, one with emptying history and one with image support.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/b
** Changed in: iio-sensor-proxy (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to iio-sensor-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/1837321
Title:
Update to 2.7
To manage notifica
** Description changed:
Steps to reproduce the bug:
- 1. Add a Google or a Nextcloud account in gnome-calendar (or
gnome-online-accounts)
+ 1. Add a Google or a Nextcloud account in gnome-calendar
2. Activate the calendar component in the account
- 3. Open gnome-calendar and go to Calendar
I had this issue in VM consistently when loggin in with Xorg. No problems with
Wayland.
Tried the patch from above ppa and it appears to have solved problem.
Will do physical install on laptop to verify
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
This is still happening with version 3.12.1, under Ubuntu 18.04 LTS.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/438494
Title:
Brasero reports blank CD's free space incorrectly.
To manage notif
Why the f*** has nothing been done on this for over a year?
> Could someone having the issue record a screencast showing the bug?
Do you need a screencast because you are too lazy to read my description
of the issue which is in my original report and perfectly describes what
happens, or because
*** This bug is a duplicate of bug 1845136 ***
https://bugs.launchpad.net/bugs/1845136
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1845136, so is being marked as such.
Bug still present. In my multi-display setup a 40" display is reported
as a 7" in Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1792167
Title:
Display size detected incorre
I know I'm not running the latest LTS, but 16.04, yet I tried Etienne's
advice (because it seems to make perfect sense), but fsck wasn't allowed
to fix a FAT-mismatch:
sudo fsck.vfat /dev/sdf1
fsck.fat 3.0.28 (2015-05-16)
FATs differ but appear to be intact. Use which FAT ?
1) Use fir
