Rather than being a graphics driver problem it looks like it could be
caused by one of the extensions:
'system_moni...@bghome.gmail.com',
'clipboard-indica...@tudmotu.com',
'topic...@phocean.net'
Please disable/uninstall those and retest.
--
You received this bug notification because you
apport information
** Attachment added: "monitors.xml.txt"
https://bugs.launchpad.net/bugs/1882415/+attachment/5382754/+files/monitors.xml.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
Ubuntu 20.04, Gnome 3.36.2, Nvidia
Small gray line in top-right corner.
More precisely, it happens to be in the corner in 1920x1080 resolution. Not
present in smaller resolutions. In panning mode it's fixed to
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1882415/+attachment/5382750/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1882415/+attachment/5382751/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1882415/+attachment/5382752/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/1882415/+attachment/5382753/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
*** This bug is a duplicate of bug 1872268 ***
https://bugs.launchpad.net/bugs/1872268
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 1872268, so it is being marked as such. Please
** Tags added: focal
--
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/1883013
Title:
gnome-shell-extensions-prefs does not show any updates
To manage notifications about this
*** This bug is a duplicate of bug 1856838 ***
https://bugs.launchpad.net/bugs/1856838
The attachment 'GsettingsChanges.txt' is showing two extensions were
enabled, so please make sure they are both removed.
If the problem still happens then it sounds like it's already covered by
bug
** Summary changed:
- gnome-shell using a lot of RAM after repeatedly pressing Super+A
+ gnome-shell using a lot of RAM after repeatedly opening the overview
** Tags added: focal
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
You have been subscribed to a public bug:
This bug have been happing on my PC, in the applications when i open
some application folder and after click out of it, to close it. The
screen just freeze and i have to reboot my notebook (Lenovo-
ideapad-310).
ProblemType: Bug
DistroRelease: Ubuntu
There's a discrepancy between the screenshot in comment #1 and that in
comment #3. The screenshot in comment #1 shows extensions clearly
running, and the screenshot in comment #3 suggests there are none.
After you have disabled all extensions, please:
1. Log out and in again.
2. Tell us if the
*** This bug is a duplicate of bug 1877288 ***
https://bugs.launchpad.net/bugs/1877288
This sounds like bug 1877288. Please also try disabling the 'ubuntu-
dock' extension.
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
** This bug has been marked a duplicate of bug
Daniel, please use these instructions:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
*** This bug is a duplicate of bug 1866044 ***
https://bugs.launchpad.net/bugs/1866044
More recent crashes during locking are generally bug 184.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Yes that's what the upstream bug for this bug says:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2709
But I expect Ubuntu 20.04 will get the fix soon.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
1. That is bug 1832407 you are describing. Although you don't actually
need to be able to remove the extension package in order to replace it.
Installing any extension locally for your own account will override the
system version.
2. Canonical does contribute to desktop-icons when we have time.
** Changed in: gnome-terminal (Ubuntu Groovy)
Status: New => Fix Released
** Changed in: vte2.91 (Ubuntu Groovy)
Status: New => Fix Released
** Changed in: gnome-terminal (Ubuntu Focal)
Importance: Undecided => Low
** Changed in: vte2.91 (Ubuntu Focal)
Importance: Undecided
This bug is closed. If you experience any ongoing problems then please
open a new bug by running:
ubuntu-bug gnome-shell
--
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/1760399
I think I have this issue, but I'm not 100% sure. I tried to find the
crash log in /var/crash, but it looks slightly different. There's no
segvanalysis or stacktrace, though I can find a signal 11 crash in
/var/log/apport.log. How can I go about confirming this is the bug I'm
experiencing?
--
*** This bug is a duplicate of bug 1866044 ***
https://bugs.launchpad.net/bugs/1866044
Previous bug #1866044 reports being fixed in 3.36.0-2ubuntu1
I'm seeing crashes during lock screen with 3.36.1-5ubuntu2 often it's
returning from suspend, but not sure if this is the only trigger.
after
*** This bug is a duplicate of bug 1866044 ***
https://bugs.launchpad.net/bugs/1866044
Ok, maybe Original Poster was seeing same bug, perhaps Ishould file
another based upon the problem I'm seeing.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Same crap in Ubuntu 20. GNOME's OSK is useless crap, it doesn't appear
automatically when I need to type something. It only appears when you
search for applications in application's menu. Here is no button to call
OSK or run it manually, wtf?
--
You received this bug notification because you are
The picture in the other issue does indeed look identical to the screen
I had however it is a very different issue.
1. I update my system daily by hand. So my system was up to date and the
fix of the other issue was installed days ago when my issue occurred.
2. The referenced bug happened after
Public bug reported:
[ Description ]
Update as part of the GNOME 3.36 stable release series
[ QA ]
Check you can launch the terminal and use it. Maybe check that different
themes, launching a custom command, custom terminal launchers, etc work.
There is a standing SRU exception for GNOME:
Public bug reported:
One of the touted features of the GNOME 3.36 release was being able to
update extensions directly from the Extensions app. This doesn't seem
to be working at all on Ubuntu 20.04, however. I regularly receive
update notifications from the Firefox extension, but the only way
** Tags added: focal
** Package changed: ubuntu => gnome-shell (Ubuntu)
--
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/1882464
Title:
menu icons in top bars exceed their
You have been subscribed to a public bug:
Sometimes the top bar icons (battery icon, wifi, sound etc...) are going out of
their boundary at the top bar. when doing so they take over any maximized
window top bar (e.g. browser, file explorer or any other app). By doing so it
prevents the user
for me the two workaround doesn't work
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1845801
Title:
[nvidia] Automatic login fails and then all subsequent logins fail.
Ah! I see why we have a discrepancy. I'm sorry, I was not explicit
enough with my repro steps. Following your steps, it works for me as
well.
What I am doing is the following:
- ctrl+alt+T
- $ gedit
- first line is highlighted by default
- *** open the "Ln1, Col 1" menu in the bottom right corner
The verification of the Stable Release Update for desktop-file-utils has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package desktop-file-utils - 0.24-1ubuntu3
---
desktop-file-utils (0.24-1ubuntu3) focal; urgency=medium
* debian/defaults.list
- Updated for the transition to snap-store (LP: #1873658)
-- Ken VanDine Tue, 21 Apr 2020 09:38:59
-0400
** Changed in:
Could you do a screencast/video of the issue?
Yes I just tried with a fresh ISO
- downloaded a focal desktop amd64 iso
- started it in VM on the live session
- ctrl-alt-T
$ gedit
- opened the popdown menu
- selected preferences
- unselected the checkbox for the 'highlight selected line'
Will the update be back-ported to 18.04 and/or 18.10 of Ubuntu
automatically as well? Not sure how the process works...
Stephen Holden
Ontario, Canada
On Wednesday, June 10, 2020, 9:11:28 a.m. EDT, Sebastien Bacher
<1876...@bugs.launchpad.net> wrote:
The issue has been fixed in the
It happened to me too. Then, I discovered that my login to my google
acct had "expired" (how does that happen?). I logged in again and then
created a test event which got synced within one minute.
If you are looking at an Android phone/tablet that is not receiving the
event that you created on
Using 1:3.36.3-0ubuntu1 nautilus works correctly and verified to fix the
search focal regression reported in bug #1874972
** Tags removed: verification-needed verification-needed-focal
** Tags added: focal verification-done verification-done-focal
--
You received this bug notification because
I've tested on xubuntu now
- start a new focal xubuntu image
- download the eog focal deb from focal
- clicked on it from the file manager
-> gnome-software is opened
then after installing desktop-file-utils 0.24-1ubuntu3 trying the same steps
gave the same result
after restarting the session
Thanks Jens, indeed that's unfortunate but we should probably take the
update to be compliant with the service anyway. I've updated the SRU
description to mention the issue now
** Description changed:
* Impact
The update is an upstream bugfix one, including translations updates and
The issue is fixed in this update
https://bugs.launchpad.net/ubuntu/+source/nautilus/1:3.36.3-0ubuntu1
** Changed in: nautilus (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Please not that this will lose you most of the translations for the
Google-related log-in screens (Photos and YouTube). but making them
compliant with Google's requirements is one of the major points of that
update
--
You received this bug notification because you are a member of Ubuntu
Desktop
Thank you for your bug report, the fact that it's possible to enroll the
same finger is bug #1882878. If that bug is fixed then it wouldn't be
possible to enroll more than 10 fingers then it would solve that issue
as well right? In which case it's a duplicate of the other report?
** Changed in:
https://bugs.launchpad.net/ubuntu/+source/shotwell/0.30.10-0ubuntu1
** Changed in: shotwell (Ubuntu)
Importance: Undecided => Low
** Changed in: shotwell (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Public bug reported:
* Impact
The update is an upstream bugfix one, including translations updates and
fixes to youtube's publishing
* Test case
Import photos, make sure than browsing and tagging works as expected
* Regression potential
Check that publishing content to a youtube account
** Changed in: shotwell (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/1882799
Title:
SRU the current 0.30.10 stable version
> We are somewhat trapped. It's a choice between using the old version
of nautilus forever with bugs and incompatibilities, or the new version
of nautilus without desktop support. Those are not good choices but they
are all we have now. This is not a problem created by, or unique to
Ubuntu.
That
Hello Sebastien, or anyone else affected,
Accepted nautilus into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/nautilus/1:3.36.3-0ubuntu1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
*** This bug is a duplicate of bug 1865838 ***
https://bugs.launchpad.net/bugs/1865838
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 1865838, so it is being marked as such. Please
Thank you for your bug report, does it create any issue in practice or any
buggy situation? It would probably be nicer if the UI was warning you about
that but it seems pretty minor. I've forwarded it upstream anyway
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1023
** Summary
Thank you for your bug report, the description is not really clear,
Do you mean that if you have user A and B then
- log into user A
- close the session
- auth user A with a fingepritn works
but
- log into user A
- close the session
- auth user B with a fingerprint doesn't work
?
** Package
The issue has been fixed in the current serie now
https://launchpad.net/ubuntu/+source/gnutls28/3.6.13-4ubuntu1
** Changed in: gnutls28 (Ubuntu Groovy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
This issue has sat incomplete for over 5 years without any response to
comment #4. The report was raised against a very old release of Ubuntu
and did not expire due to the bug watch so I'm closing it as "Invalid".
Please feel free to re-open this bug report if this still an issue for
you.
**
So with your tip, I disabled all my extensions until I found Dash To panel
extension:
https://extensions.gnome.org/extension/1160/dash-to-panel/
When disabling it doesn't crash.
** Bug watch added: github.com/home-sweet-gnome/dash-to-panel/issues #1026
https://github.com/home-sweet-gnome/dash-to-panel/issues/1026
--
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/184
Title:
gnome-shell crashed with SIGSEGV in
This issue has sat incomplete for more than a year without any response.
The report was raised against a release of Ubuntu that is now EOL and
did not expire due to the bug watch so I'm closing it as "Invalid".
Please feel free to re-open this bug report if this still an issue.
** Changed in:
We are somewhat trapped. It's a choice between using the old version of
nautilus forever with bugs and incompatibilities, or the new version of
nautilus without desktop support. Those are not good choices but they
are all we have now. This is not a problem created by, or unique to
Ubuntu.
Indeed
Marcello, your workaround does indeed work because Xu and Lu flavours
use a window manager other than Mutter in Gnome. I myself had to revert
back to Unity.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Try removing your extensions. The crash generally seems to happen for
people who are using non-Ubuntu extensions.
--
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/184
Title:
I agree with Carlos Garcia.
This is a functionality that everyone expects to work out of the box
today.
It is frustrating to see that in every Ubuntu release something like
this comes up. Another example making ubuntu look bad: I also had to add
the "show desktop" icon manually to the system
NOK: 20.04, i1Display3:
gnome-control-c[22782]: calibration failed with code 1: no sensor->get_sample
workaround: using https://displaycal.net/ -> deb from 19.10 (no 20.04 up top
now)
selecting the profile ~/.local/share/icc/DELL U2711 #1 2020-06-09 23-26 2.2 F-S
XYZLUT+MTX.icc
--
You
When it gets into focal? Today I'cant lock my screen, it always crash :(
--
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/184
Title:
gnome-shell crashed with SIGSEGV in
This is still relevant - why not putting in the fix?
* metadata: Prevent usage of NULL if GUdevDevice is not found
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1780199
Title:
** Summary changed:
- no error displayed on failed fingerprint authentification
+ no error displayed on failed fingerprint authentication
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
** Changed in: oem-priority
Status: New => Fix Released
--
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 more than 10
@seb128, yes. It is still in issue on 20.04 (focal).
--
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/1766230
Title:
Strange window matching behaviour between Slack and Chrome
** Summary changed:
- Desktop is blank after logging in without a monitor attached
+ Desktop is blank after logging in (remotely) without a monitor attached
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
> gnome-shell-extension-desktop-icons has no relation to the Nautilus
code
Well, for moving files to trash it uses
org.gnome.Nautilus.FileOperations D-Bus interface, see dbusUtils.js. So
it should either implement the deletion itself, or use the new D-Bus
interface added in Nautilus 3.37.x.
--
gnome-shell-extension-desktop-icons has no relation to the Nautilus
code, so that will be fixable.
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
Importance: Low => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
For GNOME Flashback, this is fixed in version 3.37.1, available in
Ubuntu development release (Groovy).
It cannot be backported to 20.04 (Focal) because it needs changes in
Nautilus that are only available in Nautilus 3.37.1.1.
I guess a fix for gnome-shell-extension-desktop-icons in 20.04 will
How can i figure out if nautilus or any other desktop handler is used in
flashback to push the bug there?
Btw. Last state was also for gnome-extension-desktop-icons because in
ubuntu-session there is only delete (proposed package), shift+delete
moves to trash too (without dialog).
--
You
** Tags added: focal
--
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/1882880
Title:
FP Auth enroll screen issue: Max limit not defined
To manage notifications about
** Tags added: focal
--
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/1882881
Title:
FP Auth login Screen issue: failed attempts
To manage notifications about this bug
** Tags added: focal
--
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/1882885
Title:
FP Auth enroll for Multi user Scenario
To manage notifications about this bug go
** Tags added: focal
--
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/1882884
Title:
FP Auth : Multi user Scenario
To manage notifications about this bug go to:
Public bug reported:
FP authentication doesn't work after 3 failed attempts.
The behavior is the same in Windows OS as well.
But in windows the GUI shows an alert like Max attempts are reached and try to
login with PIN or password.
So there is no failure report of the failed authentication for
** Tags added: focal
--
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/1882878
Title:
FP Auth enroll screen issue
To manage notifications about this bug go to:
Public bug reported:
We are able to enroll FP's even after Max limit is reached (10). (No
error like 'Max limit is reached' is observed). So we are able to enroll
the same fingers again and again with any number of times.
The release of Ubuntu : Ubuntu 20.04 LTS
** Affects: gnome-control-center
Public bug reported:
FP authentication doesn't work from the login screen when there is another user.
You have to login into any user with a password for first time, then we can use
FP authentication for our next login attempts.
Ubuntu version : 20.04 LTS
** Affects: gnome-control-center
Public bug reported:
It is observed 'Couldn't access any fingerprint reader message' while trying to
enroll FP's for the first time for a newly created user.
Looks like fprintd daemon is not responding for any new user other than root?
Ubuntu version : 20.04 LTS
** Affects:
Public bug reported:
We are able to enroll the same finger for all 10 available options. (No
error like 'Fingerprint is already enrolled' is observed). In windows it
doesn’t allow to enroll the same finger, it has a duplicate check API.
Here we have all 10 finger options are shown in GUI itself,
80 matches
Mail list logo
