Zero crashes since 20.10 so consider this fixed.
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Great, thanks for the explanation. So blaming just the nvidia-drm kernel
module seems most reasonable right now. It is what's crashing after all.
Most likely the fix will come in the form of a new Nvidia driver. Please
try apt install nvidia-driver-510 or via the 'Additional Drivers' app.
You
I am guessing the problem will be bug 1960387.
--
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/1960336
Title:
No login screen when fprintd crashes
To manage notifications about this
Bug 1933633 is a clean exit whereas this bug 1960336 is a segfault. So
the two bugs should be kept separate.
We can make this bug about both your issues though:
(a) fprintd crashes with SIGSEGV; and
(b) login screen can't survive fprintd failure.
Next please follow the steps in
** Also affects: gjs (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gjs (Ubuntu)
Importance: Undecided => Medium
** Changed in: gjs (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: gjs (Ubuntu)
Status: New => In Progress
--
** Information type changed from Private to Public
--
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/1961041
Title:
gnome-shell crashed with SIGSEGV in
** Summary changed:
- No login screen when fprintd is installed
+ No login screen when fprintd is installed and not starting
--
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/1960336
hi, it seems it does not start.
output from terminal:
ubuntu@ubuntu-inspiron-5482:~$ sudo apt install fprintd
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
fprintd
0 upgraded, 1 newly installed, 0
The bug is reproduced on Eclipse IDE (screenshot
https://disk.yandex.ru/i/z7kqQV47z8xeFQ). Left click always closes the
popup window instead of set focus on it. Pressing the "F2" buttons leads
to the same result.
Ubuntu 20.04.3 LTS
GNOME Shell 3.36.9
Eclipse 2021-12 (4.22.0)
--
You received
I'll reproduce later today after hours.
Will also try to install 22.04 to see if it helps.
--
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/1960865
Title:
System freeze when
@vanvugt - USB-C port seems to be wired to NVIDIA GPU on this laptop. I
cannot use the monitor, if I switch to Intel GPU (`prime-select intel`)
- it doesn't even identify that a monitor was connected.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
> The strange thing to me is that Nvidia shouldn't be involved here. A USB-C
> port is likely to be
> wired to the Intel chips only. As a DisplayPort the USB-C is wired to the
> Intel GPU. And gnome-
> shell by default will use the integrated Intel GPU only for the desktop.
FWIW, but I'm also
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.
Upgrade to evolution 3.36.5-0ubuntu2 on Ubuntu 20.04.03 (focal) did not
fix the bug for me either. I am wondering if anyone has gotten it to
work on focal.
To fix the bug on Ubuntu 18.04 (bionic), I had to compile the source
(master branch), largely following the instructions at
I face the same issue that Legendary Nacar has described in his comment
#160. The workaround is to use Alt+F2 and type single letter r in the
textbox and hit enter as described by Axel Kittenberger in his comment
#16.
--
You received this bug notification because you are a member of Ubuntu
Just do "apt install libpam-krb5"
and then it obeys "User must change password at next logon" policy from
windows AD
Thanks
Babu
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Possibly related: the user graphical-session.target unit is never
reached in Jammy. From Impish and Jammy we have for `systemctl --user
is-active graphical-session.target`:
- Impish clean install: active
- Jammy clean install: inactive
Note that this means that the .service units under
*** This bug is a duplicate of bug 1961041 ***
https://bugs.launchpad.net/bugs/1961041
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 #1961041, so is being marked as such.
The fix is in gnome-control-center version 41 and later. So that's in
Ubuntu 22.04 only right now. And in fact it was only released to Ubuntu
22.04 in November/December.
This doesn't appear to be a severe bug. I'm not sure if such a design
change is appropriate for some future 20.04.x release. If
It says above fix released in August, however I still have the bad
wording and it has caught me out today. I'm running Ubuntu 20.04.03
gnome 3.36.8. Why has the fix not reached me yet please?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
21 matches
Mail list logo
