I can confirm 3.35.92-1 fixed it too.
** Changed in: gnome-system-monitor (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu.
I see a lot of comments about Libre and just wanted to add that it is
not an office issue.
This is for sure a copy issue. It just brings a lot of comments about
office stuff because there is text being copied and pasted.
Truth is the copy function only seems to work every other time after the
On Ubuntu 20.04 gnome-system-monitor (3.35.92-1) solved the problem.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu.
https://bugs.launchpad.net/bugs/1862478
Title:
gnome-system-monitor can't measure
Public bug reported:
The software updater keeps interrupting me with "updates available" and
then shows me a blank screen.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-software 3.30.6-2ubuntu10.19.10.0
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
Uname: Linux
Please file an upstream bug at intel graphics upstream:
https://gitlab.freedesktop.org/drm/intel/wikis/How-to-file-i915-bugs
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Symptom unreproducible after glib upgraded to proposed libglib2.0-0
/focal-proposed,now 2.64.0-1 amd64 [installed].
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1865907
Title:
Public bug reported:
If I have a folder window open, and drag a file from it into the desktop
area, that is somehow forbidden and the icon just moves back to the
folder where it came from, in a "moving" animation. It's almost as if I
didn't have filesystem permissions to move it to the desktop.
Public bug reported:
When I select an icon in my desktop, be it a folder or file, the
"delete" key doesn't do anything with it anymore. I was expecting it to
be moved to the trash folder.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.35.91-1ubuntu2
ProcVersionSignature:
> It appears we would need a new upstream bug to track this because the
old one didn't go anywhere.
This is not true. The old one did go somewhere: It examined the behavior
and clearly concluded that upstream gnome-terminal is NOT buggy here, it
never was. It's one of the Ubuntu patches that
The only crashes I can find on my system have all been uploaded already.
There also, doesn't seem to be anything related to firefox (the browser
in use at the time of the crash) or gnome-shell.
However, there are some recent crashes: (all on 2020-02-27)
-
Public bug reported:
Hello -- This is a clean Ubuntu 10.10 install onto a new disk. For many
days now I've been clicking on the calculator. It just doesn't work.
No message or error report. I am looking for an alternative caclulator
to install.
Today I tried to run the calculator from the
I confirm the bug
The bug applies to all the distros I have tried:
Ubuntu; Linux Mint; Manjaro; Fedora; Opensuse etc.
I also tried various DEs: Kde, Gnome, Cinnamon, Xfce, Mate etc.
It's a general problem, not just of mutter and Gnome
The bug exists only with Mesa and Modesetting, if you install
Thanks for your report! I could reproduce the problem, which is a bit
weird because IBus was updated yesterday and the IBus input methods I
tested worked fine then...
Anyway, I see in the error message: "GLib version too old". So I
upgraded the libglib2.0-* packages to version 2.64.0-1 (from
** Changed in: gnome-shell (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => Marco Trevisan (Treviño) (3v1n0)
--
You received this bug notification because
This bug was fixed in the package gnome-control-center -
1:3.35.91-0ubuntu3
---
gnome-control-center (1:3.35.91-0ubuntu3) focal; urgency=medium
* debian/patches/0003-info-overview-Use-the-Ubuntu-logo-prominently.patch:
- Fix Ubuntu logo not showing in about panel (LP: #1864577)
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
In Ubuntu 18.04 LTS this is still an issue, the described behaviour still
occurs exactly as described.
Probably this is expected with your smartphone but absolutely not from your
Laptop!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
Public bug reported:
Totem crashes on launch along with the desktop/Xorg. BTW I am not using
any dm but only managing my desktop with openbox wm.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu6.2
ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
Uname: Linux
@Marc: Please see my short conversation with Alex on IRC:
https://irclogs.ubuntu.com/2020/02/11/%23ubuntu-desktop.html
I will ask Laney about the current status.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
Okay after some experimenting
I found switching to Wayland brings up both monitors after login
But no mouse pointer
--
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/bugs/1865444
Is anyone actively working on the glib2.0 SRUs? We are blocked on them
for our ibus security update...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1844853
Title:
IBus no longer
It appears we would need a new upstream bug to track this because the
old one didn't go anywhere. Please create one in:
https://gitlab.gnome.org/GNOME/gnome-terminal/issues
or
https://gitlab.gnome.org/GNOME/gtk/issues
and then tell us the URL.
--
You received this bug notification
What's the current status of this bug? Where is the fix? One of my
report is made duplicate to this bug but I think this is much older. I'm
using 19.10
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
** Changed in: gnome-control-center (Ubuntu Focal)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1864577
Title:
Ubuntu logo
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-control-center (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
** Changed in: gnome-control-center (Ubuntu)
Assignee: (unassigned) => Robert Ancell (robert-ancell)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1865871
Title:
Public bug reported:
Appearance setting seems to have a double border in the separation from
the sidebar
steps to reproduce
1. open gnome-control-center
2. click on appearance tab
3. compare the border-from-sidebar with another setting page
lsb_release -rd
Description:Ubuntu Focal Fossa
I had the same issue today, and I remember the last thing I done yesterday
before failing was installing the MegaSync extension. I have just removed that
package and restarted and Nautilus is working again.
I hope this would be useful.
--
You received this bug notification because you are a
Periodically, after working for a few hours, evolution may suddenly
throw up a "timeout was reached" when sending a message. Then
connections to imap folders also stops. I have to reboot in order to get
things going again. After a reboot, the same message in the outbox,
which was showing the
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
*** This bug is a duplicate of bug 1864153 ***
https://bugs.launchpad.net/bugs/1864153
** This bug is no longer a duplicate of private bug 1864556
** This bug has been marked a duplicate of bug 1864153
tracker-extract crashed with signal 5 in start_thread()
--
You received this bug
Public bug reported:
Icon spring animation starts/ends in the wrong location (near the top of
the dock).
This only seems to happen using the Ubuntu Dock with Gnome Shell 3.35.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.2
Thanks Alex, you assigned the bug to yourself, does it mean you are
working on fixing the issue?
I've sent it upstream as well now
https://gitlab.gnome.org/GNOME/gdm/issues/567
** Summary changed:
- no error popup while exceed maximal fingerprint retry during login
+ no error displayed on
Public bug reported:
I have two actual audio devices plugged in: 1. speaker under my monitor
plugged into the 3.5mm headphone jack, 2. a set of USB headphones.
The 'Sound' settings panel shows three devices:
1. Headphones - built in audio
2. Digital output (s/pdif) - Jambra UC Voice 750 MS
3.
** Changed in: gnome-shell (Ubuntu)
Status: Fix Committed => Invalid
--
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/bugs/1865563
Title:
password box not centered
To manage
Hi.
This is fixed in the latest Yaru master :) Thanks for taking the time to report
this
** Changed in: yaru-theme (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1865845
Title:
No UI indication for fingerprint enrolling progress
To manage
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1865838
Title:
no error popup while exceed maximal fingerprint retry during login
To manage
** Summary changed:
- no fingerprint enrolling progress information
+ No UI indication for fingerprint enrolling progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
** Tags added: champagne
--
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/1864052
Title:
gnome-shell crashed with SIGABRT in
src/core/window.c:1591:meta_window_unmanage: assertion
** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu)
** Also affects: yaru-theme (Ubuntu)
Importance: Undecided
Status: New
** Changed in: yaru-theme (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdm3 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
after user click 'Next', there is no message remind user the progress of
fingerprint enrollment.
And also no reminder for the necessary of 12 times finger pressing.
** Attachment added: "Screenshot from 2020-03-03 11-13-25.png"
user page in setting failed forever after fingerprint enrolling time
out.
** Attachment added: "Screenshot from 2020-03-03 16-49-54.png"
https://bugs.launchpad.net/oem-priority/+bug/1865845/+attachment/5332968/+files/Screenshot%20from%202020-03-03%2016-49-54.png
--
You received this bug
Public bug reported:
there is no progress information shows to user while enrolling fingerprint.
It might confuse user thinking it as freeze failure.
steps:
1. enroll fingerprint in gnome-control-center
2. click 'Next' on the enrolling page
3. There is no message tell user that it need at least
Thanks. The only relevant error I can find in there is strange:
Mar 02 11:49:30 mel-Aspire-M5600-AM3600 gnome-shell[3916]: gnome-shell:
Fatal IO error 0 (Success) on X server :0.
and
Feb 29 20:58:53 mel-Aspire-M5600-AM3600 gnome-shell[3068]: gnome-shell:
Fatal IO error 11 (Resource temporarily
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
** Tags added: radeon
** Summary changed:
- Dual monitor loop login
+ [radeon] Dual monitor loop login
--
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/bugs/1865444
Title:
[radeon]
the message in journalctl shows that fprintd and gdm-fingerprint know
user is trying on incorrect finger.
https://paste.ubuntu.com/p/QkySMYzVmC/
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
You have been subscribed to a public bug:
My Nvidia GPU is set to on-demand mode, so it uses the integrated intel
iGPU for most of the every day tasks.
This hang seems to happen when watching media (1080p @ 11605 kbps in
H.264 in MKV container with EAC3 5.1 sound) and then switching to a
Public bug reported:
from journalctl, gdm-fingerprint shows error there after retried 5 times
of fingerprint login failed, so I open this issue here.
Steps to reproduce issue:
1. enroll fingerprint for your right index finger.
2. logout
3. login and try login by incorrect finger e.g. middle
Happened again.
Bug did not seem to submit report once more.
Screenshot as per comment #2
Report was produced which I managed to see the details but sending report did
not return a bug ID.
See this from terminal where I carried out action 1a in comment #3.
Still no bug ID.
52 matches
Mail list logo
