[Desktop-packages] [Bug 1936261] Re: Session creation inhibited when trying to connect to VNC server after Ubuntu 21.04 upgrade
Seeing this bug, checking the logs I see: Jun 07 17:22:27 pjds-ubuntu gnome-remote-desktop-daemon[30361]: [17:22:27:525] [30361:2971765] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_COMPLETE_NEEDED [0x00090313] Jun 07 17:22:27 pjds-ubuntu gnome-remote-de[30361]: [RDP.RDPGFX] CapsAdvertise: Accepting capability set with version RDPGFX_CAPVERSION_104, Client cap flags: H264 (AVC444): true, H264 (AVC420):> Jun 07 17:22:28 pjds-ubuntu gnome-remote-de[30361]: Failed to start remote desktop session: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Session creation inhibited Just checking google for related issues I came across this upstream bug: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/16. Maybe it's not the same issue though, as I am using RDP. Cheers, Peter ** Bug watch added: gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues #16 https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/16 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1936261 Title: Session creation inhibited when trying to connect to VNC server after Ubuntu 21.04 upgrade Status in gnome-remote-desktop package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 21.04 from 20.10, connecting to VNC server will not work from some clients. Prompts for password, then the client gives the error message "The connection closed unexpectedly." Gnome- remote-desktop package gives the following error message in syslog: > gnome-remote-de[111245]: Failed to start remote desktop session: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Session creation inhibited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1936261/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798790] Re: Ubuntu login screen sometimes doesn't appear on a single GPU Nvidia system (and setting WaylandEnable=false fixes it)
I also have this issue, but I discovered if I pressed Alt+F{N>2} then
Alt+F1 gdm boots immediatly.
I opemed a bug here,
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1834568 but I will
close it now that I found this one.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1798790
Title:
Ubuntu login screen sometimes doesn't appear on a single GPU Nvidia
system (and setting WaylandEnable=false fixes it)
Status in gdm:
Fix Released
Status in gdm3 package in Ubuntu:
In Progress
Status in gnome-session package in Ubuntu:
In Progress
Status in gnome-shell package in Ubuntu:
In Progress
Status in mutter package in Ubuntu:
Invalid
Status in gdm3 source package in Eoan:
In Progress
Status in gnome-session source package in Eoan:
In Progress
Status in gnome-shell source package in Eoan:
In Progress
Status in mutter source package in Eoan:
Invalid
Bug description:
https://gitlab.gnome.org/GNOME/gdm/issues/483
formerly https://gitlab.gnome.org/GNOME/gdm/issues/435
---
The boot process hangs with the last message being "started bpfilter".
There is unusual Network activity during that time. The light of the
WiFi adapter is blinking a lot.
I am not sure the problem is with the gdm3 package. As a matter of
fact, I would remove it and let someone more experienced to set it.
I'm afraid I might break something, though.
The specific steps or actions you took that caused you to encounter the
problem: 1. Boot Ubuntu 18.10 with the Nvidia proprietary drivers
installed.
The behavior you expected: I expected Ubuntu 18.10 to boot normally.
The behavior you actually encountered: The computer gets stuck in a
command-like environment with the last message being "started
bpfilter". You can't type any commands.
I have found that uninstalling the Nvidia proprietary drivers by going
into recovery mode fixes the issue.
Booting with the earlier kernel doesn't fix the issue. Installing the
earlier v.340 driver also doesn't fix the issue.
This (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in-
boot-after-starting-gnome-display-manager-on-intel-graphic) seems
relevant. This is where I found the "solution".
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1798790/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1834568] [NEW] gdm fails to start on nvidia based systems on cosmic
Public bug reported:
Hello,
After upgrading to Cosmic Cuttlefish yesterday when I came to reboot gdm
seemingly was unable to start. There was not much in the logs, and after
much tinkering I discovered that after the Ubuntu splash screen if I
pressed Alt + F{N>1} then pressed Alt+F1 gdm would immediatly start up.
But if I left it to load as normal, it would fall into a stalled state
where I am forced to reboot.
If you need any diagnostics please don't hisitate to ask.
Prior to discovering this work around I checked the logs using
`journalctl -xb` but was unable to see anything related to GDM, so it
may not be that but this is the configuration I have:
- Nvidia RTX 2080Ti
- Nvidia 430 drivers from nvidia ppa
- Wayland enabled
- Cosmic Cuttlefish 18.10
This bug is not present when I disable wayland.
** Affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Hello,
After upgrading to Cosmic Cuttlefish yesterday when I came to reboot gdm
seemingly was unable to start. There was not much in the logs, and after
much tinkering I discovered that after the Ubuntu splash screen if I
- pressed Alt + F{N<1} then pressed F1 gdm would immediatly start up.
+ pressed Alt + F{N>1} then pressed F1 gdm would immediatly start up.
But if I left it to load as normal, it would fall into a stalled state
where I am forced to reboot.
If you need any diagnostics please don't hisitate to ask.
Prior to discovering this work around I checked the logs using
`journalctl -xe` but was unable to see anything related to GDM, so it
may not be that but this is the configuration I have:
- Nvidia RTX 2080Ti
- Nvidia 430 drivers from nvidia ppa
- Wayland enabled
- Cosmic Cuttlefish 18.10
This bug is not present when I disable wayland.
** Description changed:
Hello,
After upgrading to Cosmic Cuttlefish yesterday when I came to reboot gdm
seemingly was unable to start. There was not much in the logs, and after
much tinkering I discovered that after the Ubuntu splash screen if I
- pressed Alt + F{N>1} then pressed F1 gdm would immediatly start up.
+ pressed Alt + F{N>1} then pressed Alt+F1 gdm would immediatly start up.
But if I left it to load as normal, it would fall into a stalled state
where I am forced to reboot.
If you need any diagnostics please don't hisitate to ask.
Prior to discovering this work around I checked the logs using
`journalctl -xe` but was unable to see anything related to GDM, so it
may not be that but this is the configuration I have:
- Nvidia RTX 2080Ti
- Nvidia 430 drivers from nvidia ppa
- Wayland enabled
- Cosmic Cuttlefish 18.10
This bug is not present when I disable wayland.
** Description changed:
Hello,
After upgrading to Cosmic Cuttlefish yesterday when I came to reboot gdm
seemingly was unable to start. There was not much in the logs, and after
much tinkering I discovered that after the Ubuntu splash screen if I
pressed Alt + F{N>1} then pressed Alt+F1 gdm would immediatly start up.
But if I left it to load as normal, it would fall into a stalled state
where I am forced to reboot.
If you need any diagnostics please don't hisitate to ask.
Prior to discovering this work around I checked the logs using
- `journalctl -xe` but was unable to see anything related to GDM, so it
+ `journalctl -xb` but was unable to see anything related to GDM, so it
may not be that but this is the configuration I have:
- Nvidia RTX 2080Ti
- Nvidia 430 drivers from nvidia ppa
- Wayland enabled
- Cosmic Cuttlefish 18.10
This bug is not present when I disable wayland.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1834568
Title:
gdm fails to start on nvidia based systems on cosmic
Status in gdm3 package in Ubuntu:
New
Bug description:
Hello,
After upgrading to Cosmic Cuttlefish yesterday when I came to reboot
gdm seemingly was unable to start. There was not much in the logs, and
after much tinkering I discovered that after the Ubuntu splash screen
if I pressed Alt + F{N>1} then pressed Alt+F1 gdm would immediatly
start up.
But if I left it to load as normal, it would fall into a stalled state
where I am forced to reboot.
If you need any diagnostics please don't hisitate to ask.
Prior to discovering this work around I checked the logs using
`journalctl -xb` but was unable to see anything related to GDM, so it
may not be that but this is the configuration I have:
- Nvidia RTX 2080Ti
- Nvidia 430 drivers from nvidia ppa
- Wayland enabled
- Cosmic Cuttlefish 18.10
This bug is not present when I disable wayland.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1834568/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to
