** Description changed:
- Steps to reproduce this bug:
+ [ Impact ]
+
+ Mouse stops working after taking an area screenshot
+
+ [ Test case ]
1. Open Chromium browser.
2. Go to the page with the form in which there is a standard browser
drop-down menu (form select)
3. Open it
4. Try
** Changed in: gnome-shell (Ubuntu)
Status: In Progress => Fix Committed
--
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/1915570
Title:
Login screen password entry not
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => In Progress
--
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/1915570
Title:
Login screen password entry not
Ok it's handled in https://gitlab.gnome.org/GNOME/gnome-
shell/-/merge_requests/1683
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3734
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3734
** Also affects: gnome-shell via
No need for further testing, this seems to happen when a fingerprint
reader is in the system but no prints are enrolled for the user.
So I'm working upstream to fix this to handle the unavailable-service
case in shell.
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Apologies if this is the wrong package.
Using Ubuntu Budgie
I note that GNOME Settings - Sharing is enabled by default and that
"Remote Login" is ticked to be on. This could be construed as a
security issue.
I would have expected a user to enable if sharing should be
Can you please modify your `/etc/pam.d/gdm-fingerprint` so that it will
use:
authrequiredpam_fprintd.so debug
And then provide me output from:
- grep fingerprint /var/log/auth.log
It may be useful also enable debugging for gdm into your /etc/gdm3/daemon.conf
(and provide
Public bug reported:
Problem with `gvfs-google`
Description:Ubuntu 20.10
Release:20.10
Package already exist on machine.
I want to copy a large file form google drive to my another drive. So i
logged it my drive in account. This give me access to dive in nautilus.
Now when i copy
When u copy a large file from google drive it. It takes huge sapace in
ram. May be the size of file. Like when u copy 6 gb file or more your
device will be freeze. unitll you kill it.
** Attachment added: "Screenshot from 2021-02-15 22-47-04.png"
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gvfs (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
** Description changed:
- O.k. it is an old Lenovo thinkpad T410. However, in 18.04, 19.04 and 19.10 I
did face these problems. The sometimes I have to wait 10 seconds to see if a
window reacts or not. It is hard to use.
- Installiert: 3.36.1-5ubuntu2
- Installationskandidat:
** Package changed: nautilus (Ubuntu) => nautilus-share (Ubuntu)
** Changed in: nautilus-share (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
Same as the previous comments:
* gimp has been working perfectly fine for months
Suddenly, shortcuts do not work:
* Keyboard shortcuts for tool selection like pressing "R" for rectangle select
is not working.
* Also the main menu does not open if I press ALT+F (for File menu).
* Alt shows
I downgraded to 20.04 kernel (5.4.x) and I am still getting the black
flashes.
BTW, the journal seems to expose the username, so you should warn about
that before requesting it.
** Attachment added: "journal.txt"
Hello! Please update the description to include the necessary SRU
information [1]. Thank you!
[1] https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Hello! Please update the description to include the necessary SRU
information [1]. Thank you!
[1] https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Hello! Please update the description to include the necessary SRU
information [1]. Thank you!
[1] https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Hello! Please update the description to include the necessary SRU
information [1]. Thank you!
[1] https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
I believe the crash happened at roughly Feb 11 19:42:41.
--
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/1915481
Title:
gnome crashes after running `apt upgrade`
To manage
Reproducing the crash exactly is basically impossible -- I have no idea
what I was doing to trigger it on January 6. The crashes I've been
experiencing happen seemingly at random while running `apt update`. It
may well happen again in the future, but based on past experiences it
will be with a
Out from running
journalctl -b-1 > prevjournal.txt
** Attachment added: "prevjournal.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915481/+attachment/5463784/+files/prevjournal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
this was also addressed in snapd in
https://github.com/snapcore/snapd/pull/9530 in 2.48
** Changed in: snapd
Status: In Progress => Won't Fix
** Changed in: snapd
Status: Won't Fix => Fix Committed
** Changed in: snapd
Status: Fix Committed => Fix Released
--
You received
** Package changed: gdm3 (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/1915570
Title:
Login screen password entry not working on systems with
It's translatable now
https://translations.launchpad.net/snap-store-desktop/trunk/+pots/snap-
store/cs/979/+translate
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1909591
Title:
gnome-shell (3.38.3-2ubuntu1) hirsute; urgency=medium
* Merge with debian, containing new upstream release (LP: #1915089)
* debian/patches: Correctly handle login cancellation and failures.
Ensure the GDM workers are terminated before restarting a new auth
request, allowing
** Changed in: gdm3 (Ubuntu)
Importance: Undecided => Critical
--
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/1915570
Title:
Login screen password entry not working on systems
** Summary changed:
- Login screen password entry not working
+ Login screen password entry not working on systems with fingerprint support
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
Seems to be fingerprinting linked.
You can’t type any characters (regular or special):
- you type a "a"
- the password prompt shows up a first character being input
- then, the password prompt is immediately reset to empty.
--
You received this bug notification because you are a member of
I’m getting a lot of pam failures due to fingerprints in my logs:
févr. 12 08:21:51 casanier gdm-password][6277]: pam_unix(gdm-password:auth):
Couldn't open /etc/securetty: Aucun fichier ou dossier de ce type
févr. 12 08:21:51 casanier gdm-fingerprint][6278]: gkr-pam: no password is
available
I still can't reproduce this on my hirsute desktop, fully updated.
Please check if the problem is unique to:
* Some special characters in your password; or
* Other authentication methods being available, like fingerprint.
** No longer affects: gnome-shell (Ubuntu)
--
You received this bug
** Attachment added: "Log of upgrade list between a working and faulty reboot"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1915570/+attachment/5463728/+files/apt-upgrade-list
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Is the password box misinterpreting some special character that's
causing this?
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gdm3 (Ubuntu)
Status: New => Confirmed
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
@vanvugt i'll fix that myself ^_^
--
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/1914230
Title:
On-screen keyboard for Japanese doesn't display Japanese characters,
only
Automated login is disabled here and I’m affecting by this bug too.
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => New
** Tags added: tracking-hh
** Tags removed: tracking-hh
** Tags added: rls-hh-bugs
--
You received this bug notification because you are a member of Ubuntu
Desktop
34 matches
Mail list logo
