This bug is closed so please open a new bug if you have any problems at
all.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1766137
Title:
[regression] Password accepted but
This bug affected me, but got past it by adding "nouveau.modeset=0"
after the text "quiet splash" in the bootparameters for Ubuntu in the
grub menu.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
matt,
Please also note that a Core 2 Duo will suffer from bug 1727356 too.
Please apply the workaround from that bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1766137
Title:
matt,
The fix is in gdm3 version 3.28.2-0ubuntu1.1 and later.
You only have version 3.28.0-0ubuntu1 installed.
If you can't easily update then you might have more luck installing
version 18.04.1 directly (which might contain the fix if 18.04
didn't)...
9-8-018 fresh install with updates .. some user switches work, some
don't logout is also crashing with irresponsive black screen. When the
user switch fails, the description is slightly different from above. If
the mouse pointer comes in at lower right, the user switch works. If it
comes in upper
gdm3 info. for above comment
matt@Wallace:~$ apt list gdm3
Listing... Done
gdm3/bionic-updates,bionic-security,now 3.28.2-0ubuntu1.4 amd64 [installed]
N: There is 1 additional version. Please use the '-a' switch to see it
matt@Wallace:~$ apt list gdm3 -a
Listing... Done
** Changed in: gdm3 (Ubuntu Bionic)
Milestone: None => ubuntu-18.04.1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1766137
Title:
[regression] Password accepted but login
This bug was fixed in the package gdm3 - 3.28.2-0ubuntu1.2
---
gdm3 (3.28.2-0ubuntu1.2) bionic; urgency=medium
* debian/patches/libgdm-drop-support-for-serializing-multiple-opens.patch,
debian/patches/libgdm-fix-pointer-boolean-task-confusion.patch,
The policy for Stable Release Updates is to let them age a minimum of 7
days in the -proposed pocket before releasing them to the -updates
pocket. Reading the comments here I've noticed that the automated SRU
testing comment doesn't make any reference to that 7 day period nor does
it point to the
This is a blocker for deployment of 18.04 to ~200 workstations within my
company. Any ETA on a release?
My steps to reproduce:
1. Boot Machine
2. Enter username
3. Enter incorrect password
4. Enter correct password
5. Stuck on purple screen
--
You received this bug notification because you are
Release package is already unstable and isn't able to it's job.
I don't see any reasons not to deploy this excepting bureaucracy.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
3.28.2-0ubuntu1.1 did work fine for login logout to another user (critical
in our environment). It has been few days since it was supposed to be
coming and I figured that it is safe now to start installing 18.04, but
fresh install 18.04 and I am still getting 3.28.0-Oubuntu1 - will not work.
su
@Ads2 Thanks for the link. Sadly, gdm3 is neither in the
autopkgtest-list, nor update-excuses, nor update-list, so it seems
things are stuck at an earlier stage and the documentation does not
clarify where to find out at which point help could be needed.
My intention was not to spam this
The conditions for the package to move to release are here:
https://wiki.ubuntu.com/ProposedMigration#Migrating_packages_from_-
proposed_to_release
It's possible that the update breaks something in release, though I'm
not sure what. It's also possible that we _just need to be more
patient_, it's
Hi,
I'd like to test too - though being new here - can I (to avoid to switch
to proposed repo) just download and install the AMD64 .deb files listed
under proposed / 3.28.2-0ubuntu1.2 ?
thanks,
br, Koen
--
You received this bug notification because you are a member of Desktop
Packages,
Hi,
Tested the fix again - 3.28.2-0ubuntu1.2 on a fresh install of Ubuntu
18.04 LTS.
I went through all scenarios:
a) Login initially with incorrect password then correct password - Pass
b) Login by entering incorrect password multiple times then correct password -
Pass
c) Created a second
Since it's still in proposed and a day is mostly over (and Europe is
asleep again) - could somebody outline / point me to the conditions for
a package to be moved from proposed to released?
This would be good to know to understand what is missing (and
potentially help?) instead of entering a
Namely for my part to solve the connection problems via auto connection.
However, it still freezes a few more times in use
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1766137
I also have on this installation in addition to the bug described above
with the reboot... Can't reboot? Forced to do a hard reboot. Is it
related?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Yes. See "WORKAROUND" in the bug description.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1766137
Title:
[regression] Password accepted but login fails (blank purple screen
Do you know how to potentially unlock the situation even temporarily?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1766137
Title:
[regression] Password accepted but login fails
As already stated, I expect to see the release within hours (less than a
day).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1766137
Title:
[regression] Password accepted but
How long will it will be tested in "proposed"? A week? Two weeks, a
month?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1766137
Title:
[regression] Password accepted but login
That's not quite right. Fix Released means a fix has been released. The
only question is in which Ubuntu release. Presently you can see:
gdm3 (Ubuntu) Fix Released <-- Ubuntu 18.10 release completed
Bionic Fix Committed<-- Ubuntu 18.04 soon to be released
--
You received this bug
Wow! So once status is Fix Released that means, probably, usually,
hopefully, wait no more than 24 hours for the fix to hit your machine if
you sudo apt upgrade daily?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in
Nobody can predict the future exactly, but given that the fix for 18.04
has now been verified I would *expect* it to be fully released later
today. Mainly waiting for Europe to wake up...
Tip: Make sure you're using the main archive to receive updates and not
a mirror, as mirrors will take longer
Thanks Daniel!
So, my question is, how do I decipher (approximately) how many
hours/days away from release for 18.04 this fix is?
It's probably very obvious to old hands, but it's totally illegible to a
newb. Like, can I see what "branch" or "version" will have this fix? And
then, how do I see
"Fix Released" will always occur for the development release first
(Ubuntu 18.10). Then existing stable versions after that.
You can see a fix for 18.04 is in proposed (not yet released) here:
https://launchpad.net/ubuntu/+source/gdm3
So is only hours/days away from release.
** Tags removed:
Can someone take time to explain to a newb how/where to read in this bug
report when this fix will be pushed out?
Like, I see "Fix Released", but when does "sudo apt upgrade" see this
fix?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1766137
Title:
[regression] Password accepted
** Tag verification-done-bionic
tested the following:
gdm3/3.28.2-0ubuntu1.2/amd64
Tested multiple bad password followed with a good password. PASS
Tested switching from user A to user B; multiple bad password followed by good
password. PASS
Tested switching from user B back to user A; multiple
Hello Chris, or anyone else affected,
Accepted gdm3 into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/gdm3/3.28.2-0ubuntu1.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug was fixed in the package gdm3 - 3.28.2-2ubuntu1
---
gdm3 (3.28.2-2ubuntu1) cosmic; urgency=medium
[ Iain Lane ]
* Merge with Debian. Remaining changes:
+ README.Debian: update for correct paths in Ubuntu
+ control.in:
- Don't recommend desktop-base
-
In progress again. See the "Related branches" links near the top of the
bug.
** Changed in: gdm3 (Ubuntu)
Status: Fix Released => In Progress
** Changed in: gdm3 (Ubuntu Bionic)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of
** Merge proposal linked:
https://code.launchpad.net/~3v1n0/ubuntu/+source/gdm3/+git/gdm3/+merge/347420
** Merge proposal linked:
https://code.launchpad.net/~3v1n0/ubuntu/+source/gdm3/+git/gdm3/+merge/347421
--
You received this bug notification because you are a member of Desktop
gdm3_3.28.2-0ubuntu1.1_amd64.deb,
gir1.2-gdm-1.0_3.28.2-0ubuntu1.1_amd64.deb,
libgdm1-dbgsym_3.28.2-0ubuntu1.1_amd64.ddeb,
gdm3-dbgsym_3.28.2-0ubuntu1.1_amd64.ddeb,
libgdm1_3.28.2-0ubuntu1.1_amd64.deb, and libgdm-
dev_3.28.2-0ubuntu1.1_amd64.deb do not fix these issues by themselves.
on a fresh
Hi, in response to Marco's post #101,
I was wondering if a package will be released for bionic proposed so we
can test it out before it is released?
I can see that one is released for cosmic that is newer than the one for
bionic.
--
You received this bug notification because you are a member
So, the latest two commits of this branch:
-
https://gitlab.gnome.org/3v1n0/gdm/commits/client-connection-reference-fix-3-28
Should fix all the problems that I've tested so far.
Packaging will follow.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Fresh install 18.04 gdm3 did succeed occasionally, but mostly froze
completely so that power button was only way out.
There was a fix that was available in proposed repository (or something)
that made things a bit different. Failure became a rule, but it was
possible to get back with
Switching users sometimes hangs since gnome shell 3.22. The bug exists
in debian stable. But it's not 100% reproducible.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1766137
Given that the same code has now been released in 18.10
(3.28.2-1ubuntu1), we should treat it as a new bug and maybe not
complicate the discussion here.
Can someone please log a bug against 18.10?
--
You received this bug notification because you are a member of Desktop
Packages, which is
Hi,
In addition to my post #96 above, I downgraded gdm3 back to the release
version - 3.28.0-0ubuntu1 and am able to confirm that switching users
works perfectly between two users for me.
Therefore sounds like the fix for gdm3 - 3.28.2-0ubuntu1.1 - has
introduced further issues.
--
You
Hi,
Confirm that there are switching user issues.
I logged in as user A, then created a second user - user B. I clicked on
Switch User and logged in successfully as User B.
I then proceeded to switch to User A by clicking on Switch User then
clicking on User A and entering the password.
For information, I have had switching users issues since the fresh
install of 18.04 on top of not being able to login myself.
I let the gnome people continue to work on this issue and thank them for their
work. In the meantime, my workaround is to turn back to lightdm which works
very well for
Regarding gdm3 3.28.2-0ubuntu1.1; regardless of what I do I cannot make
it work. Switching between users 100% of the time results in failure.
Here is what I have done:
Someone mentioned that after rebooting their system three times
(something like that) it started working albeit slow. I have
** Tags removed: verification-done verification-done-bionic
** Tags added: regression-proposed verification-failed-bionic
** Tags removed: regression
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
I don't think you should release this because this produces more critical bug.
This bug has some kind of workaround (cancel button), but I will have to
disable updates if there is an upcoming update that will totally break an
ability to switch users without any workaround.
I believe I'm not
I think the issue is getting is there but maybe different from the one
originating this bug, so maybe to be handled in a different one...
So please, test this:
1. Create another user
2. Login with your user (or the other, as you wish)
3. Lock the session -> Switch to other user from
I had similar experience yesterday after installing 3.28.2 and I reported
that it does not work. But after couple of boots I have been testing every
now and then maybe some 15 times and every time it has logged in - very
slowly but success anyway. To me that is quite clear that any kind of
success
Did you test : 3.28.2-0ubuntu1.1 ?
I thought that is The version having The fix
ke 30. toukokuuta 2018 klo 18.51 KenWilson <1766...@bugs.launchpad.net>
kirjoitti:
> All,
> My testing indicates gdm3 3.28.0-0ubuntu1.1 fixes the incorrect password
> issue; however, it creates a new issue. As such
I installed package 3.28.2-0ubuntu1.1 and performed the testing again. I
restricted testing to only switching between accounts. Same result, it
did not work.
Listing... Done
gdm3/bionic-proposed,now 3.28.2-0ubuntu1.1 amd64 [installed]
gdm3/bionic 3.28.0-0ubuntu1 amd64
After installation I
On Wed, May 30, 2018 at 03:45:17PM -, KenWilson wrote:
> All,
> My testing indicates gdm3 3.28.0-0ubuntu1.1 fixes the incorrect
> password issue; however, it creates a new issue. As such I don’t think
> this update should be released.
That verison is superseded by 3.28.2-0ubuntu1.1. Please
All,
My testing indicates gdm3 3.28.0-0ubuntu1.1 fixes the incorrect password issue;
however, it creates a new issue. As such I don’t think this update should be
released.
I installed gdm3 3.28.0-0ubuntu1.1 and rebooted my system (Ubuntu 18.04
LTS). Making sure I typed the password correct I
This bug was fixed in the package gdm3 - 3.28.2-1ubuntu1
---
gdm3 (3.28.2-1ubuntu1) cosmic; urgency=medium
* Merge with Debian. Remaining changes:
+ README.Debian: update for correct paths in Ubuntu
+ control.in:
- Don't recommend desktop-base
- Depend on bash
** Changed in: gdm3 (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1766137
Title:
[regression] Password accepted but login
Hi I tested gdm3 - 3.28.2-0ubuntu1.1 on Ubuntu 18.04 LTS.
I ran the following tests:
a) Boot Ubuntu 18.04 LTS, attempt login with correct password - pass.
b) Log out and then log back in with correct password - pass.
c) Log out and then enter the wrong password a few times then enter the correct
Ah, thanks for saying that since I was testing in my other machine and wasn't
unable to reproduce this anymore...
My second user has no password set, but there's no much difference in terms of
the issue.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
**
Sorry I commented too quickly below after first tryout. After couple of
boots and tryouts it did finally succeed after longer wait time and now
after testing some 5 times I have managed to log with different user after
loging out. it is slow, but it will get there. So certainly I see good
heikki@ThinkPad-X301:~$ apt-cache policy gdm3
gdm3:
Asennettu: 3.28.2-0ubuntu1.1
Ehdokas: 3.28.2-0ubuntu1.1
Versiotaulukko:
*** 3.28.2-0ubuntu1.1 500
500 http://fi.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
3.28.0-0ubuntu1
Hello Chris, or anyone else affected,
Accepted gdm3 into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/gdm3/3.28.2-0ubuntu1.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Yes, a fix is coming but not released yet. Apparently the fix is in gdm3
version 3.28.1.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1766137
Title:
[regression] Password
Mostly I don't understand this discussion and probably I should not take
part in it. There has been no progress visible to me. The bug I reported
was assigned as duplicate to this, so if this is now fixed, should I report
the bug again?
Anyhow it appears to me, that to ordinary users sharing the
Marco,
It sounds like you're talking about the secondary bug. So let's reopen
the cosmic task, awaiting that second fix. Cosmic presently has gdm3
3.28.0-0ubuntu2.
** Changed in: gdm3 (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a
Ops, sorry... Pasted the wrong commit, the right one is
https://gitlab.gnome.org/GNOME/gdm/commit/4085d689
That's already included in gdm 3.28.1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
So, fix for this is actually in the upstream branch [1]. And that's
handled in gdm 3.28.1, so we should rebase on that in order to fix this.
[1]
https://gitlab.gnome.org/GNOME/gdm/commit/85a68ab14aad3d83abe1317d0c067f4d80a4dc82
** Changed in: gdm3 (Ubuntu Bionic)
Status: Fix Committed =>
Sorry for my English, I'm French, this is a google translation of what I
mean.
@ Ads2 (ads2)
The problem is more complicated than that. When we enter our password and we
validate it, we sometimes end up with a purple screen without cancel button
visible, the only possibility is to do
Oh, nothing else we can do short of ensuring others affected mark
themselves as affected so the bug heat is increased even further (which
demonstrates how serious the issue is without leaving impatient
comments!) :)
--
You received this bug notification because you are a member of Desktop
The fix was committed but 'verification-failed-bionic' which means that
it didn't work well enough. We have to wait for the developers to come
up with a better fix, and there's no ETA on that, unless you're a
developer yourself and know how to fix the issue we just have to wait.
It's not ideal but
When are you gonna fix this bug? It says "Fix committed", but the bug is
still exist. I can't login to my Xubuntu like a month already!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Does anyone feel like logging a new bug for the regression in
3.28.0-0ubuntu1.1/3.28.0-0ubuntu2 ?
It's a real bug now, since 3.28.0-0ubuntu2 was released in cosmic.
** Description changed:
[ Description ]
Due to a refcounting bug, a GDBusConnection was getting disposed when it
- was
I just found out yesterday that, if you enable auto-login, gdm never
hangs like this anymore.
This is kinda bad for security and debugging/testing but hopefully it
can still be of use to someone until this bug gets fixed.
Also this is not related to bad gnome extensions as, on my machine, gdm
Hi,
I just fix the problem uninstalling the gnome extension "Workspace to Dock".
Because i couldnt use my mouse and keyboard in the desktop i change to TTY with
ctl+alt+F3 and remove that extension.
# rm -f -r $HOME/.local/share/gnome-shell/extensions/
or
# sudo rm -f -r
It seems 3.28.0-0ubuntu1.1 isn't help to us. Now instead blank screen
with cursor we get hung after password entered and even Alt+Ctrl+F2 /
Alt+Ctrl+F1 can't help.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
** Tags removed: verification-needed-bionic
** Tags added: verification-failed-bionic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1766137
Title:
[regression] Password accepted
This is what the testing procedure is for. Marco is going to take a
further look, thanks.
** Changed in: gdm3 (Ubuntu)
Assignee: Iain Lane (laney) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: gdm3 (Ubuntu Bionic)
Assignee: Iain Lane (laney) => Marco Trevisan (Treviño) (3v1n0)
--
I am thinking that the fix has resulted in more issues than before
therefore I call it a blocker (due to increased issues). The fix needs
further testing and development.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in
Following on from post #62:
According to Bodinux's post and my testing, the login hang is
reproducible and I was able to replicate the issue every time I tested
it. It sounds like the login and logout process is working but not
processing properly.
--
You received this bug notification because
Hmm, actually it is arguably worse with version 3.28.0-0ubuntu1.1
The problem with that version is that you can't log in more than once
without encountering a new login screen freeze, that is unlike this one.
Not sure if we want to continue with version 3.28.0-0ubuntu1.1 and deal
with that
I have verified this bug is fixed on bionic using version
3.28.0-0ubuntu1.1
However I have also verified what the above comments allude to, in that
there are also other login bugs we will need to deal with later.
** Tags removed: verification-needed verification-needed-bionic
** Tags added:
I have tested the login process as follows:
a) Install gdm3 from bionic-proposed version 3.28.0-0ubuntu1.1 - in Ubuntu
18.04 LTS and reboot.
b) When login screen appears, click on my username and enter incorrect password.
c) Enter correct password and press enter or click on sign in. Login
As requested I have attached the result. Hopefully this posts in the bug
list, not sure?
Ken
On 05/18/2018 10:25 AM, Marco Trevisan (Treviño) wrote:
> Looks weird, can you attach the output of
>journalctl /usr/bin/gnome-shell
>
> ?
>
--
*Ken Wilson*
forest
** Attachment added:
Following #51 and #56 from Davide (tarski10)
I was able to reproduce. **.
gdm3/ 3.28.0-0-0ubuntu1.1
if I enter the wrong password once or twice and then I enter the correct
password now I can access,
but if I enter the wrong password three times I return to the user choice
screen and after
Really sorry about spamming, but I only now figured out how to get output
from relevenant time ( I hope)
getUniqueBusNameSync@
/usr/share/gnome-shell/extensions/
ubuntu-appindicat...@ubuntu.com/util.js:58:20
Not sure what came out but this is out come of running journalctl right
after booting after freeze.
I need clear guidance to get something else more relevant.
Logs begin at Fri 2018-04-27 22:06:06 EEST, end at Fri 2018-05-18 20:56:33
EE
huhti 27 22:06:06 ThinkPad-X301 kernel: Linux version
sorry this is the out come of journalctl /usr/bin/gnome-shell
-- Logs begin at Fri 2018-04-27 22:06:06 EEST, end at Fri 2018-05-18
21:03:51 EE
huhti 27 22:06:13 ThinkPad-X301 org.gnome.Shell.desktop[762]: glamor: EGL
versio
huhti 27 22:06:16 ThinkPad-X301 gnome-shell[762]: JS WARNING:
Bodinux
after clicking your name, wait a while before entering the correct
password.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1766137
Title:
[regression] Password accepted
Looks weird, can you attach the output of
journalctl /usr/bin/gnome-shell
?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1766137
Title:
[regression] Password accepted but
I installed proposed updates. Now it freeze a bit earlier and even more
often. Login screen remain visible and no cursor movement while before in
looked like progressing with blank screen with cursor movement until final
freeze.
pe 18. toukok. 2018 klo 19.20 KenWilson (1766...@bugs.launchpad.net)
Brian,
I attempted to install the proposed package: 3.28.0-0ubuntu1.1 but it failed.
Initially I thought it installed correct but when switching users I got a
notification of a timeout and a package not installed. In the process of
looking at the notification it went away and I don't know how
I could not reproduce what Davide (tarski10) did.
I enter the wrong password three times I return to the user choice
screen and after clicking on my username and entering the correct
password I could successfully login.
--
You received this bug notification because you are a member of Desktop
gdm3/ 3.28.0-0-0ubuntu1.1
if I enter the wrong password once or twice and then I enter the correct
password now I can access,
but if I enter the wrong password three times I return to the user choice
screen and after clicking on my username and entering the correct password the
screen freezes
Bodinux,
It sounds like maybe you hit bug 1765261. That one will be fixed
separately in gnome-shell 3.28.2.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1766137
Title:
Tested this gdm3/3.28.0-0ubuntu1.1 from bionic-proposed.
Bad password entry followed by correct password entry works correctly.
I then tried to switch user, Bad password entry followed by correct password
entry : screen with the grayed password box, nothing happening.
crtl-alt-f1, ctrl-alt-f2,
Hello Chris, or anyone else affected,
Accepted gdm3 into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/gdm3/3.28.0-0ubuntu1.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug was fixed in the package gdm3 - 3.28.0-0ubuntu2
---
gdm3 (3.28.0-0ubuntu2) cosmic; urgency=medium
* debian/patches/0001-libgdm-Don-t-unref-a-connection-that-s-in-use.patch,
debian/patches/0002-libgdm-add-weak-pointer-for-connection-object.patch:
Cherry-pick two
Packages coming your way soon. They work for me/us, but please give
confirmation/denial. There will be a message when they're accepted into
bionic for testing.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
** Branch linked: lp:~ubuntu-desktop/gdm/ubuntu
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1766137
Title:
[regression] Password accepted but login fails (blank purple screen
** Description changed:
- WORKAROUND: After typing an incorrect password, click Cancel, then click
- your name, then enter your password again.
+ [ Description ]
+
+ Due to a refcounting bug, a GDBusConnection was getting disposed when it
+ was still required. The symptom of this was that you
** Changed in: gnome-shell (Ubuntu Bionic)
Status: Confirmed => Invalid
** Changed in: gnome-shell (Ubuntu)
Status: Won't Fix => Invalid
** Changed in: gdm3 (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: gdm3 (Ubuntu Bionic)
Assignee: (unassigned) =>
** Changed in: gdm
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1766137
Title:
[regression] Password accepted but login fails (blank
1 - 100 of 142 matches
Mail list logo
